|Publication number||US7272634 B2|
|Application number||US 10/964,939|
|Publication date||Sep 18, 2007|
|Filing date||Oct 14, 2004|
|Priority date||Mar 18, 2004|
|Also published as||EP1725945A2, EP1725945A4, US20050210112, WO2005089146A2, WO2005089146A3, WO2005089146A8|
|Publication number||10964939, 964939, US 7272634 B2, US 7272634B2, US-B2-7272634, US7272634 B2, US7272634B2|
|Inventors||Jason Lee Clement, Kyoko Takeda Wieck, Theodore R. Booth, III, Brian James Moon|
|Original Assignee||Sony Corporation, Sony Electronics Inc.|
|Export Citation||BiBTeX, EndNote, RefMan|
|Patent Citations (26), Non-Patent Citations (2), Referenced by (34), Classifications (20), Legal Events (3)|
|External Links: USPTO, USPTO Assignment, Espacenet|
This application claims priority from U.S. provisional application Ser. No. 60/554,755, filed Mar. 18, 2004.
The present invention relates generally to computerized messaging services.
To send a message to a recipient, the message must be addressed to the recipient using the protocol of a particular communication or messaging system. For example, a user might have to decide whether to send a particular message over email, or by instant messaging services over Internet-connected computers, or by text entry on a telephone using short message service (SMS), or by a similar telephone-enabled messaging service known as multimedia messaging service (MMS), or by other messaging systems. Each system, not surprisingly, has advantages and drawbacks, and not all intended recipients access every system that a sender might use.
Thus, when deciding how to get a message to a recipient, a sender must think about and balance a variety of considerations, including cost, recipient capabilities, recipient presence and preferences, and so on. Then, the sender must start up or invoke the selected messaging system and use it, a task made more difficult as technological messaging innovations and capabilities outpace ease-of-use innovations. Having made these critical observations, the invention described below is provided.
A communication system includes a sender computer and means at the sender computer for invoking a message input file. The message input file need not be associated with any particular messaging engine. A user of the sender computer can enter a recipient's identification and a message into the message input file. A dispatch server communicates with the sender computer and with a recipient computer associated with the recipient's identification, and the dispatch server executes logic which includes receiving the input file from the sender computer. The logic also includes determining which messaging engine to use from a plurality of messaging engines that are available to the dispatch server. The message is sent to the recipient computer using the messaging engine identified by the server.
The message input file may be presented to a user of the sender computer as a visible form for typed data entry, or it may be made accessible to a user of the sender computer for audible data entry. In any case, owing the off-loading of messaging engine technical details to the server, the sender computer can be a light client that has no messaging engines.
In non-limiting implementations the server can determine whether a messaging system has been specified in the message input file and if so, the server can invoke a messaging engine that is associated with the messaging system. Also, the determining act executed by the server may be based on recipient presence and/or preference information. A default messaging engine can be selected in the absence of other messaging engine designation information.
In another aspect, a method for enabling a sender computer to send a message to a recipient computer using a message file and one of at least two messaging systems includes receiving user-entered messaging information in the file. The method also includes sending the file to a server computer having access to plural messaging systems. At the server computer, it is determined which one of the messaging systems to use to deliver the message. The user-entered messaging information is sent to the recipient computer using the selected messaging system.
In still another aspect, a server computer is accessible to a sender computer and to a recipient computer over the Internet. The server computer includes means for selecting one of plural messaging engines for invocation, in response to receiving a message from a sender computer not designating an engine. The server also includes means for formatting the message from the sender computer as appropriate for use with the selected messaging engine, for transmission thereof to the recipient computer using the selected messaging engine.
The details of the present invention, both as to its structure and operation, can best be understood in reference to the accompanying drawings, in which like reference numerals refer to like parts, and in which:
Referring initially to
Thus, in the preferred non-limiting embodiment shown, the computers described herein may access one or more software or hardware elements to undertake the present logic. The flow charts herein illustrate the structure of the logic modules of the present invention as embodied in computer program software, in logic flow chart format, it being understood that the logic could also be represented using a state diagram or other convention. Those skilled in the art will appreciate that the flow charts illustrate the structures of logic elements, such as computer program code elements or electronic logic circuits, that function according to this invention. Manifestly, the invention is practiced in its essential embodiment by a machine component that renders the logic elements in a form that instructs a digital processing apparatus (that is, a computer or microprocessor) to perform a sequence of function steps corresponding to those shown. Internal logic could be as simple as a state machine.
In other words, the present logic may be established as a computer program that is executed by a processor within, e.g., the present computers/servers as a series of computer-executable instructions. In addition to residing on hard disk drives, these instructions may reside, for example, in RAM of the appropriate computer, or the instructions may be stored on magnetic tape, electronic read-only memory, or other appropriate data storage device.
A text input device 16 such as a keyboard or keypad can be manipulated by a user to type information into the sender computer 12. Also, if desired a voice input device such as but not limited a microphone associated with voice recognition software can be used to input information into the sender computer 12. Furthermore, multimedia data can be input into the sender computer 12 from a source or device 20 of multimedia. One or more output devices, such as a monitor 22 or audible speakers, can be used to display data, including the below-described message input form, to the user of the sender computer 12.
Owing to the below-described logic, the sender computer 12 may but need not have any commercial messaging engines, such as email programs, instant messaging programs, and the like. Instead, it need only communicate with a dispatch server 24 using a generic, common, single message file described further below, consequently permitting the use of a thin client computer as the sender computer 12. Or, the sender computer 12 need have only one commercial messaging application which can be invoked by the user without concern for the type of message or transport. Regardless of whether it is a commercial messaging engine or not, once the single-unified messaging user interface described below is invoked, the user may create a message without concern about how to send it, because the dispatch server 24 can check such things as the message content (send to address, text only, or include multi media data), receiver's presence, availability, and so on and then send the message using the “best” or most appropriate messaging engine.
The dispatch server 24 can be a Web server and the communication with the sender computer 12 can be over the Internet. The dispatch server 24 may access a logic module 26 for executing the logic below. Recipient presence information can be received from a presence database 28 over the Internet if desired. The presence database 28 may be the one set forth in co-pending U.S. patent application Ser. No. 10/892,993, incorporated herein by reference. Among other things the presence data can include contact data such as what messaging systems the system recipients possess, which ones happen to be active, which systems a recipient might prefer to receive messages on, and so on. Also, the dispatch server 24 can access a single profile associated with the user of the sender computer 12, to manage multiple messaging accounts associated with the respective messaging engines discussed below.
As shown, the dispatch server 24 can access plural messaging engines, including an email engine 30, an SMS engine 32, an MMS engine 34, and an IM engine 36. Other engines can be included. Using a server-determined one of the messaging engines 30-36, messages from the sender computer 12 are transmitted to one or more recipient computers 38.
It is to be understood that when a messaging engine is selected by the server 24, the server 24 causes the engine to construct a message in the particular format of the messaging service represented by the engine. Thus, the server 24 can also send to the selected engine authentication information pertaining to the user of the sender computer 12, public passwords of the user of the sender computer 12, digital signatures of the user of the sender computer 12, and so on as might be required for desired features, e.g., encryption and the like, using the particular messaging service selected.
Now referring to
At block 42, the user inputs at least a message and an intended recipient into the message input file made available at block 40. The file is sent to the dispatch server 24 at block 44, and at block 46, the dispatch server 24 determines which one of the plural messaging engines 30-36 shown in
Moreover, the recipient user might indicate a profile that could be sent to the presence database shown in
It may now be appreciated that the system of the present invention improves a user's messaging experience by removing an otherwise complicated messaging technology wall, making possible the use of lightweight client sender computers that are easily portable to many different operating systems. More specifically, the present invention transfers, from the sender computer 12 to the dispatch server 24, authentication, roster, presence, agents, transports, gateway, and trans-coding burdens, thus removing requirements for large amounts of processor capability and data storage in the sender computer 12. If switching is required between disparate networks that might be associated with respective messaging services, the switching is done by the server 24, transparently to the user of the sender computer 12. For example, from one message to the next from the sender computer 12, the server 24 can seamlessly switch between a Wireless Fidelity (802.11b) (Wi-Fi) network that might be used for one type of messaging service and a General Packet Radio Service (GPRS) network that might be used for another type of service. Moreover, well accepted applications such as Microsoft OutlookŪ email can be integrated into the system 10. Multiple user identities, each associated with a particular messaging service, can be managed by the server 24 through use of a single profile (mobile phone, office phone, fax, SMS, e-Mail addresses, IM, pager, device addresses, etc.), and this profile can be shared, if desired by the user, with other users in the system 10.
Still further, at block 68 custom logos of the user of the sender computer 12 may be made available to the server 24 for sending the logos for display to the recipient computer 38. Also, as another option, at block 70 the server 24 might determine the profile status of the user of the recipient computer 38, both for selecting a messaging engine as discussed above and for display of the status on the monitor of the sender computer 12. This can be based on, e.g., time of day, whether the user is in a meeting as indicated by a message the user might send to the dispatch server 24, whether the recipient computer 38 is energized, whether the user is in the user's office (and, hence, is expected to be available by phone), and so on. Likewise, if permitted by the user of the sender computer 12, similar information pertaining to the sending user can be sent to the server 24 for transmission of preselected information, if desired only to preselected recipient computers 38 at block 72. For example, the sender computer 12 can cause the server 24 to disclose an “in office” condition only to recipient computers 38 associated with co-workers and family members of the user of the sender computer 12. Likewise, whether the user of the sender computer 12 is at home might be disclosed only to recipient computers 38 associated with family members of the user of the sender computer 12, or the user of the sender computer can elect not to disclose any such information at all. The server 24 might also automatically respond to missed calls in either direction at block 74 based on the caller's presence/availability etc.
While the particular SYSTEM AND METHOD FOR INTEGRATING MULTIPLE MESSAGING SYSTEMS as herein shown and described in detail is fully capable of attaining the above-described objects of the invention, it is to be understood that it is the presently preferred embodiment of the present invention and is thus representative of the subject matter which is broadly contemplated by the present invention, that the scope of the present invention fully encompasses other embodiments which may become obvious to those skilled in the art, and that the scope of the present invention is accordingly to be limited by nothing other than the appended claims, in which reference to an element in the singular is not intended to mean “one and only one” unless explicitly so stated, but rather “one or more”. It is not necessary for a device or method to address each and every problem sought to be solved by the present invention, for it to be encompassed by the present claims. Furthermore, no element, component, or method step in the present disclosure is intended to be dedicated to the public regardless of whether the element, component, or method step is explicitly recited in the claims. Absent express definitions herein, claim terms are to be given all ordinary and accustomed meanings that are not irreconcilable with the present specification and file history.
|Cited Patent||Filing date||Publication date||Applicant||Title|
|US6697840||Feb 29, 2000||Feb 24, 2004||Lucent Technologies Inc.||Presence awareness in collaborative systems|
|US7171190 *||Oct 13, 2003||Jan 30, 2007||Oracle International Corporation||Intelligent messaging|
|US20020035605||Mar 16, 2001||Mar 21, 2002||Mcdowell Mark||Use of presence and location information concerning wireless subscribers for instant messaging and mobile commerce|
|US20020065894||Nov 30, 2000||May 30, 2002||Dalal Siddhartha R.||Local presence state and user-controlled presence and message forwarding in unified instant messaging|
|US20020078150||Dec 18, 2000||Jun 20, 2002||Nortel Networks Limited And Bell Canada||Method of team member profile selection within a virtual team environment|
|US20020126701||Oct 30, 2001||Sep 12, 2002||Nokia Corporation||System and methods for using an application layer control protocol transporting spatial location information pertaining to devices connected to wired and wireless internet protocol networks|
|US20030009511 *||Jul 5, 2001||Jan 9, 2003||Paul Giotta||Method for ensuring operation during node failures and network partitions in a clustered message passing server|
|US20030023691 *||Jul 27, 2001||Jan 30, 2003||Knauerhase Robert C.||Routing messages using presence information|
|US20030028597||Mar 13, 2002||Feb 6, 2003||Matti Salmi||Separation of instant messaging user and client identities|
|US20030041141||Oct 3, 2002||Feb 27, 2003||Abdelaziz Mohamed M.||Peer-to-peer presence detection|
|US20030046396 *||Apr 5, 2002||Mar 6, 2003||Richter Roger K.||Systems and methods for managing resource utilization in information management environments|
|US20030065788||May 10, 2002||Apr 3, 2003||Nokia Corporation||Mobile instant messaging and presence service|
|US20030131142||Jun 28, 2002||Jul 10, 2003||Horvitz Eric J.||Schema-based information preference settings|
|US20030154293||Feb 14, 2003||Aug 14, 2003||Zmolek Andrew Charles||Presence tracking and name space interconnection techniques|
|US20030158902 *||Oct 31, 2002||Aug 21, 2003||Dotan Volach||Multimedia instant communication system and method|
|US20040003042||Jun 30, 2003||Jan 1, 2004||Horvitz Eric J.||Methods and architecture for cross-device activity monitoring, reasoning, and visualization for providing status and forecasts of a users' presence and availability|
|US20040028208||Aug 6, 2002||Feb 12, 2004||Carnazza James M.||System and method for dynamically routing communications|
|US20040054735 *||Dec 19, 2002||Mar 18, 2004||Daniell W. Todd||Multi-system instant messaging (IM)|
|US20040059781||Sep 19, 2002||Mar 25, 2004||Nortel Networks Limited||Dynamic presence indicators|
|US20040064511||Aug 29, 2002||Apr 1, 2004||Abdel-Aziz Mohamed M.||Peer-to-peer email messaging|
|US20040071150||Jul 3, 2003||Apr 15, 2004||Anu Honkala||Updating presence information|
|US20040098484||Nov 19, 2002||May 20, 2004||Wuebker Carl L.||Method and system for communication between two devices by editing machine specific information at a proxy server|
|US20040098515||Sep 16, 2003||May 20, 2004||Babak Rezvani||Systems and methods for the automatic registration of devices|
|US20050009541 *||Oct 13, 2003||Jan 13, 2005||Oracle International Corporation||Intelligent messaging|
|US20050114533 *||Nov 26, 2003||May 26, 2005||Hullfish Keith C.||Electronic message forwarding|
|US20050198183 *||Feb 23, 2004||Sep 8, 2005||Nokia Corporation||Methods, apparatus and computer program products for dispatching and prioritizing communication of generic-recipient messages to recipients|
|1||*||Miao et al., Seamless messaging in a multimedia network environment, Signal processing, 2002 6th International Conference onvol. 2, Aug. 26-30, 2002, pp. 1031-1034.|
|2||U.S. Appl. No. 10/872,993, filed Jun. 21, 2004, Weick et al.|
|Citing Patent||Filing date||Publication date||Applicant||Title|
|US7689655||Jun 30, 2005||Mar 30, 2010||Aol Inc.||Managing and collaborating with digital content using a dynamic user interface|
|US7689657 *||Jun 28, 2006||Mar 30, 2010||At&T Intellectual Property I, L.P.||Forwarding IM messages to E-mail|
|US7725541||Feb 10, 2003||May 25, 2010||At&T Intellectual Property I, L.P.||Forwarding to automatically prioritized IM accounts based upon priority and presence|
|US7725542||Feb 10, 2003||May 25, 2010||At&T Intellectual Property I, L.P.||Forwarding IM messages to E-mail|
|US7904099 *||Dec 22, 2005||Mar 8, 2011||Research In Motion Limited||Unified addressing|
|US8045547||Jun 30, 2004||Oct 25, 2011||Ericsson Ab||Method and apparatus for routing and forwarding between virtual routers within a single network element|
|US8140633||Apr 6, 2010||Mar 20, 2012||At&T Intellectual Property I, Lp||Forwarding to automatically prioritized IM accounts based upon priority and presence|
|US8204526||Feb 25, 2011||Jun 19, 2012||Research In Motion Limited||Unified addressing|
|US8306809||Jul 17, 2008||Nov 6, 2012||International Business Machines Corporation||System and method for suggesting recipients in electronic messages|
|US8396922 *||Nov 20, 2006||Mar 12, 2013||Aol Inc.||Promoting interoperability of presence-based systems through the use of ubiquitous online identities|
|US8626209 *||Jun 29, 2009||Jan 7, 2014||Cellco Partnership||Systems and methods for forwarding messaging service messages|
|US8713112||Mar 22, 2010||Apr 29, 2014||Facebook, Inc.||Managing and collaborating with digital content|
|US8996620 *||Nov 20, 2006||Mar 31, 2015||Aol Inc.||Promoting interoperability of presence-based systems through the use of ubiquitous online identities|
|US9245258 *||Aug 23, 2012||Jan 26, 2016||Prophit Marketing, Inc.||System and method of electronic interpersonal communication|
|US9332080||Aug 4, 2011||May 3, 2016||Google Inc.||Systems and methods for indicating a user state in a social network|
|US9392069||Nov 20, 2006||Jul 12, 2016||Aol Inc.||Promoting interoperability of presence-based systems through the use of ubiquitous online identities|
|US20040158609 *||Feb 10, 2003||Aug 12, 2004||Daniell W. Todd||Forwarding to automatically prioritized IM accounts based upon priority and presence|
|US20040158611 *||Feb 10, 2003||Aug 12, 2004||Daniell W. Todd||Forwarding IM messages to E-mail|
|US20040240429 *||Jun 30, 2004||Dec 2, 2004||Naiming Shen||Method and apparatus for routing and forwarding between virtual routers within a single network element|
|US20060123347 *||Jun 30, 2005||Jun 8, 2006||Joe Hewitt||Managing and collaborating with digital content using a dynamic user interface|
|US20060143157 *||Mar 11, 2005||Jun 29, 2006||America Online, Inc.||Updating organizational information by parsing text files|
|US20060248157 *||Jun 28, 2006||Nov 2, 2006||Daniell W T||Forwarding IM messages to E--mail|
|US20070149223 *||Dec 22, 2005||Jun 28, 2007||Research In Motion Limited||Unified addressing|
|US20070156827 *||Nov 20, 2006||Jul 5, 2007||Aol Llc||Promoting interoperability of presence-based systems through the use of ubiquitous online identities|
|US20070162555 *||Nov 20, 2006||Jul 12, 2007||Aol Llc||Promoting interoperability of presence-based systems through the use of ubiquitous online identities|
|US20090265429 *||Apr 17, 2009||Oct 22, 2009||Amivox Limited||Communications framework using hand held devices|
|US20100017194 *||Jul 17, 2008||Jan 21, 2010||Mette Hammer||System and method for suggesting recipients in electronic messages|
|US20100174799 *||Mar 22, 2010||Jul 8, 2010||Aol Inc.||Managing and collaborating with digital content|
|US20100191820 *||Apr 6, 2010||Jul 29, 2010||At&T Intellectual Property I, L.P.||Forwarding to Automatically Prioritized IM Accounts Based Upon Priority and Presence|
|US20100205539 *||Feb 12, 2010||Aug 12, 2010||Amivox Ehf.||Instant messaging and telephony value added services|
|US20110107228 *||Jul 2, 2010||May 5, 2011||Chun-Min Huang||Method of simultaneously displaying status of a plurality of contacts in an address book and related communication device|
|US20110143788 *||Feb 25, 2011||Jun 16, 2011||Robert Liang||Unified addressing|
|US20130055110 *||Aug 23, 2012||Feb 28, 2013||Joseph M. Kiedinger||System and method of electronic interpersonal communication|
|WO2010092492A1 *||Feb 12, 2010||Aug 19, 2010||Amivox Ehf.||Instant messaging and telephony value added services|
|U.S. Classification||709/206, 709/246|
|International Classification||H04M3/42, G06F15/16, G06Q10/00, H04M3/53, H04L12/58|
|Cooperative Classification||H04M3/5307, H04L51/066, H04M3/42374, H04M3/5141, H04L12/5895, G06Q10/107, H04L12/5835, H04L12/589, H04M2203/4509|
|European Classification||H04M3/42S2, G06Q10/107, H04L51/06B, H04L12/58C2|
|Oct 14, 2004||AS||Assignment|
Owner name: SONY CORPORATION, JAPAN
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:CLEMENT, JASON LEE;WIECK, KYOKO TAKEDA;BOOTH, THEODORE R. III;AND OTHERS;REEL/FRAME:015901/0361
Effective date: 20041014
Owner name: SONY ELECTRONICS INC., NEW JERSEY
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:CLEMENT, JASON LEE;WIECK, KYOKO TAKEDA;BOOTH, THEODORE R. III;AND OTHERS;REEL/FRAME:015901/0361
Effective date: 20041014
|Mar 18, 2011||FPAY||Fee payment|
Year of fee payment: 4
|Mar 18, 2015||FPAY||Fee payment|
Year of fee payment: 8