WO2004027559A2 - Client de message a consolidation multiple du systeme de message - Google Patents

Client de message a consolidation multiple du systeme de message Download PDF

Info

Publication number
WO2004027559A2
WO2004027559A2 PCT/US2003/029066 US0329066W WO2004027559A2 WO 2004027559 A2 WO2004027559 A2 WO 2004027559A2 US 0329066 W US0329066 W US 0329066W WO 2004027559 A2 WO2004027559 A2 WO 2004027559A2
Authority
WO
WIPO (PCT)
Prior art keywords
contact
aol
user
servers
bellsouth
Prior art date
Application number
PCT/US2003/029066
Other languages
English (en)
Other versions
WO2004027559A3 (fr
WO2004027559A8 (fr
Inventor
William Todd Daniell
Lee G. Friedman
Larry Graham Kent, Jr.
Joel A. Davis
Brian Keith Daigle
Original Assignee
Bellsouth Intellectual Property Corporation
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Bellsouth Intellectual Property Corporation filed Critical Bellsouth Intellectual Property Corporation
Priority to AU2003278822A priority Critical patent/AU2003278822A1/en
Publication of WO2004027559A2 publication Critical patent/WO2004027559A2/fr
Publication of WO2004027559A3 publication Critical patent/WO2004027559A3/fr
Publication of WO2004027559A8 publication Critical patent/WO2004027559A8/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/08—Protocols for interworking; Protocol conversion
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/10—Office automation; Time management
    • G06Q10/107—Computer-aided management of electronic mailing [e-mailing]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/04—Real-time or near real-time messaging, e.g. instant messaging [IM]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/06—Message adaptation to terminal or network requirements
    • H04L51/066—Format adaptation, e.g. format conversion or compression
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/04—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks
    • H04L63/0428—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/21—Monitoring or handling of messages
    • H04L51/234—Monitoring or handling of messages for tracking messages

Definitions

  • the present disclosure relates generally to the Internet and, more particularly, to systems and methods for providing interoperability between various Internet protocols.
  • each IM service had a translation protocol for as many other IM services to which it sought to provide interoperability.
  • all communications with a particular service was routed from server to server for this type of approach, any failure in the path resulted in loss of all messaging with a particular service. Additionally, a failure in the server often resulted in loss of all services provided by that server. Moreover, because all messages to other services were routed through the server, the server was required to process all of the messages to all of the services, thereby resulting in greater delays in all services.
  • RFC 2778 and RFC 2779 provide guidelines for presence and IM.
  • RFC 2778 and RFC 2779 provide very little instruction for actually implementing IM by various vendors. This lack of instruction resulted in further study by members of the IETF, who published several memos and recommendations for Common Presence and Instant Messaging (CPIM).
  • CPIM Common Presence and Instant Messaging
  • the IETF efforts only address a fraction of the problems dealing with interoperability.
  • the present disclosure provides systems and methods for providing interoperability between various Internet protocols.
  • one embodiment of the system comprises a user interface having a name of a contact, and an indicator associated with the name of the contact.
  • the contact has a message service account, which transmits and receives messages using a messaging protocol that is different from the protocol of the system comprising the user interface.
  • the present disclosure also provides methods for providing interoperability between various Internet protocols.
  • one embodiment of the method comprises the steps of receiving a first login' name and password, and automatically establishing a plurality of messaging sessions in response to receiving the first login name and password.
  • each of the plurality of messaging sessions have a different messaging protocol.
  • FIG. 1 A is a block diagram showing one embodiment of a user agent uploading user information to a server.
  • FIGS. IB and 1C are diagrams showing example user interfaces for providing a login name and a password.
  • FIG. 2 is a block diagram showing one embodiment of a user agent instantiating a plurality of transport protocol objects (TPOs) at a client.
  • TPOs transport protocol objects
  • FIG. 3 is a block diagram showing one embodiment of a user agent communicating with a plurality of servers through the plurality of TPOs at the client.
  • FIG. 4A is a diagram showing an example user interface for providing contact information.
  • FIG. 4B is a diagram showing an example user interface showing contact information.
  • FIG. 5 is a block diagram showing another embodiment of a user agent instantiating a plurality of transport protocol objects (TPOs) at a server.
  • TPOs transport protocol objects
  • FIG. 6 is a block diagram showing another embodiment of a user agent communicating with a plurality of servers through the plurality of TPOs at the server.
  • FIGS. 7 through 12 are data-flow diagrams outlining the relationship of various TPOs with a user agent and a server. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
  • FIG. 1A is a block diagram showing an example embodiment of a system having an instant messaging (IM) abstraction object 1 0.
  • a BellSouth IM user agent 115 at a BellSouth client location 110 is communication with a BellSouth server 120.
  • the BellSouth server 120 may comprise an IM server 126 and an abstraction server 124.
  • the IM server 126 is adapted to handle normal IM functions, while the abstraction server 124 is adapted to handle translations of IM functions from various protocols into XML-structured information.
  • the BellSouth IM user agent 115 may be a software application that assists a user in communicating with contacts via an IM session.
  • the BellSouth IM user agent 115 is located at a BellSouth client location 110, which may be a personal computer, a handheld computer, a cellular telephone having , IM capabilities, an i-pager, or any network- compatible device.
  • the user information 150a is transmitted by the BellSouth IM user agent 115 to the abstraction server 124 through a communication line 160 and other conventional mechanisms.
  • the user information is transmitted and stored on the abstraction server 124 as XML-structured information because XML provides a versatile approach that is compatible with almost any other Internet-based technology.
  • XML is a markup language for documents containing structured information, which contains both content (e.g., words, pictures, etc.) and some indication of what role that content plays (e.g., content in a section heading has a different meaning from content in a footnote, which means something different than content in a figure caption or content in a database table, etc.).
  • the XML specification titled “Extensible Markup Language (XML) 1.0 (Second Edition), W3C Recommendation 6 October 2000" (referred to herein as "the XML specification") by W3C is hereby incorporated by reference as if set forth in its entirety. If, for example, a BellSouth user has a BellSouth IM account, an America On-
  • AOL Line
  • MSN Microsoft Network
  • the BellSouth user may provide an IM login name and password for each of the user's accounts as part of the user information 150a.
  • the inputting of the user information 150a is shown in FIGS. IB and lC.
  • a mechanism may be provided for a user to create an account with other message services.
  • FIGS. IB and 1C show two embodiments of user interfaces 102 a, 102b for inputting login names and passwords at the BellSouth IM user agent 115.
  • a BellSouth IM user Prior to being presented the user interfaces 102a, 102b, a BellSouth IM user preferably enters a BellSouth login name (e.g., usernarne) and password.
  • FIG. IB shows a user interface 102a for signing onto a BellSouth IM user's AOL account.
  • the AOL user interface 102a provides an input box 104a adapted to receive the AOL login name (or screen name) of the BellSouth IM user.
  • the AOL user interface 102a provides an input box 106a adapted to receive the AOL password associated with the AOL login name.
  • the AOL user interface Upon entering the AOL login name and the AOL password, the AOL user interface provides a status indication 108a to the BellSouth IM user.
  • the status indication 108a indicates whether or not the BellSouth IM user is online at AOL.
  • the status indication 108a will only indicate that the user is online if the user has selected the sign-on option at some point.
  • the AOL user interface provides sign-on 103a and sign-off 103b options to the BellSouth Hvl user so that the BellSouth IM user can manually initiate and terminate a login to the AOL server.
  • FIG. 1C shows a user interface 102b for signing onto a BellSouth IM user's MSN account.
  • the MSN user interface 102b provides an input box 104b adapted to receive the MSN login name of the BellSouth IM user.
  • the MSN user interface provides 102b an input box 106b adapted to receive the MSN password associated with the MSN login name.
  • the MSN user interface Upon entering the MSN login name and the MSN password, the MSN user interface provides a status indication 108b to the BellSouth IM user.
  • the status indication 108b indicates whether or not the BellSouth EVl user is online at MSN.
  • the MSN user interface provides sign-on 103b and sign-off 105b options to the BellSouth IM user so that the BellSouth IM user can manually initiate and terminate a login to the MSN server.
  • sign-on 103b and sign-off 105b options to the BellSouth IM user so that the BellSouth IM user can manually initiate and terminate a login to the
  • MSN accounts may exist at different domains
  • the MSN user interface provides examples 109 of sign-in names.
  • the BellSouth user inputs a user BellSouth login name and a BellSouth password at a user interface (not shown) located at the BellSouth IM user agent 115.
  • This information is conveyed to an IM abstraction object 130 located on the abstraction server 124.
  • the IM abstraction object 130 accesses the user information 150b to retrieve login names and passwords for each of the IM accounts of the BellSouth DVI user.
  • the BellSouth login usemame and password may be different from a usemame and password for a native BellSouth IM session.
  • the IM abstraction object 130 Upon retrieving this information, the IM abstraction object 130 generates a request to the BellSouth IM user agent 115.
  • the request includes information for instantiating a variety of TPOs.
  • the BellSouth IM user agent 115 instantiates a BellSouth transport protocol object (TPO) 226, an AOL TPO 220, a Yahoo TPO 222, and an MSN TPO 224 at the BellSouth client location 110.
  • TPO BellSouth transport protocol object
  • AOL TPO 220 AOL TPO 220
  • Yahoo TPO 222 Yahoo TPO 222
  • MSN TPO 224 MSN TPO 224
  • the translation from XML to the BellSouth protocol, the translation from XML to the AOL protocol, the translation from XML to the Yahoo protocol, and the translation from XML to the MSN protocol each occurs at the client location, thereby relinquishing resources of the abstraction server 124 for other functions.
  • FIG. 3 is a block diagram showing one embodiment in which instantiated TPOs 220, 222, 224, 226 log on to their respective Evi servers 310, 312, 314, 126 to provide interoperability between the various protocols.
  • each of the TPOs 220, 222, 224, 226 communicates with its respective server 310, 312, 314 to establish a session, and upon receiving tokens or other session identifiers from its respective server 310, 312, 314, 126, each TPO 220, 222, 224 generates a session identifier (ID).
  • ID session identifier
  • the TPOs 220, 222, 224, 226 communicate with the various servers 310. 312, 314, 126 in the native protocol of the various servers.
  • the AOL TPO 220 communicates with the AOL server 310 using an AOL- native protocol
  • the Yahoo TPO 222 communicates with the Yahoo server 312 using the Yahoo-native protocol, etc.
  • each of the TPOs 220, 222, 224, 226 appears as a native client to each of the servers 310, 312, 314, 126.
  • the MSN TPO 224 appears as an MSN client to the MSN server 314
  • the AOL TPO 220 appears as an AOL client to the AOL server 310, etc.
  • none of the servers 310, 312, 314, 126 modify their respective IM protocols or IM interfaces because the servers 310, 312, 314, 126 are in communication with objects that behave as virtual native clients to those servers 310, 312, 314, 126.
  • the message router 170 stores the session information as shared session objects
  • the AOL TPO 220 generates an AOL session ID, which is conveyed to the message router 170 for storage in the AOL session object 190.
  • the Yahoo TPO 222, the MSN TPO 224, and the BellSouth TPO 226 each generates a Yahoo session ID, an MSN session ID, and a BellSouth session ID, respectively.
  • the session IDs are conveyed to the message router 170, which stores the Yahoo session ID in the Yahoo session object 192, the MSN session ID in the MSN session object 194, and the BellSouth session ID in the BellSouth session object
  • an add-contact user interface is provided to' the BellSouth IM user.
  • An example add- contact user interface 202 is shown in FIG. 4A.
  • the add-contact user interface 202 may comprise a drop down menu 201 that includes descriptions for each of the BellSouth IM user's IM accounts.
  • the BellSouth user may add contacts from any account for which the BellSouth IM user also has an account.
  • the add- contact user interface further comprises input boxes 203, 205, 206, 207 for the contact's IM logon name, the contact's first name, the contact's last name, and the contact's nickname.
  • the BellSouth EM user may enter one or more information fields related to the contact.
  • the add-contact user interface 202 comprises another drop-down menu 208 that permits the BellSouth IM user to select a group in which to categorize the contact. As a default, the AOL contact would be categorized in an AOL-contacts group.
  • the BellSouth IM user wishes to add an MSN contact, a BellSouth contact, or a Yahoo contact
  • options similar to the AOL contact would be available for the MSN contact, the BellSouth contact, and the Yahoo contact.
  • the contact information is stored on its respective server.
  • the AOL contact information would be stored on the BellSouth IM user's AOL account since the AOL TPO 220 is providing an interface to the BellSouth IM user's AOL account.
  • the Yahoo contact info ⁇ nation would be stored on the Yahoo server at the user's Yahoo account.
  • the contact information will be available to the BellSouth IM user for any subsequent IM session, including from the BellSouth IM user agent 115 at the BellSouth client location 110 and other locations. Additionally, the contact information, once it has been entered and stored, will also be available from other native clients at that native-client location and other locations.
  • the BellSouth IM user would be able to access preexisting contact information that is already stored on the various servers 310, 312, 314.
  • the various TPOs 220, 222, 224 establish a connection to their respective servers 310, 312, 314.
  • the contact information from the servers 310, 312, 314 will be displayed to the BellSouth IM user at the user interface.
  • FIG. 4B One example of this is shown in FIG. 4B.
  • FIG. 4B shows an example contact list 302.
  • the various contacts are automatically grouped together by theii respective TPOs 303, 305, 307.
  • all MSN contacts 305 are grouped together
  • all AOL 307 contacts are grouped together, etc.
  • the groupings may be changed by the BellSouth LM user according to the BellSouth IM user's preference.
  • an indication 304 appears beside the contact's name, which indicates the presence status of the contact.
  • These indications 304 in a preferred embodiment are shown in different colors to easily differentiate differences in presence information (e.g., not present, present, busy, etc.).
  • the indication 304 for available contacts (e.g., Larry, Amit, Sharon, etc.) maybe shown in green (shown in FIG. 4B as hashed circles), the indication 304 for unavailable contacts (e.g., BigHat, Johnnie, Gene, etc.) may be shown in grey (shown in FIG. 4B as clear circles), and the indication 304 for busy contacts (e.g., Judy, Mitch, etc.) may be shown in red (shown in FIG. 4B as filled circles).
  • available contacts e.g., Larry, Amit, Sharon, etc.
  • unavailable contacts e.g., BigHat, Johnnie, Gene, etc.
  • grey shown in grey
  • the indication 304 for busy contacts e.g., Judy, Mitch, etc.
  • the contact list 302 includes user options 306, which permit the user to chat with a contact, add a new contact, or send a message or file to a contact, all of which would initiate another interface area (e.g., window, screen, etc. (not shown)) for the user to accomplish those functions, as would be understood by one of ordinary skill in the art.
  • the user interface also provides the user with additional menus 308, such as an edit menu, an options menu, a sign-on menu, and a help screen.
  • a single user interface may aggregate all of the contact information from all of the servers 310, 312, 314, 126 and display them to the user on a single screen.
  • the display of all contacts on all servers 310, 312, 314, 316 on a single screen permits the user to consolidate all of the contacts in a single user interface, thereby simplifying user IM interactions.
  • presence information related to the contacts is further determined by the various TPOs 220, 222, 224, 226. This is shown with reference to FIG. 3.
  • the BellSouth IM user has added CONTACT 1 having an AOL IM address and a Yahoo IM address, and CONTACT 2 having only an MSN account
  • presence information of CONTACT 1 is determined from the AOL server 310 and the Yahoo server 312
  • presence infomiati on of CONTACT2 is determined from the MSN server 314. While the polling for presence is shown as being initiated by the TPOs 220, 222, 224, 226, the
  • the AOL TPO 220 may generate an AOL-native presence query to detemiine whether or not CONTACTl is present.
  • the AOL server 310 is polled using the AOL-native presence query.
  • the AOL server 310 receives the query and generates AOL-native presence information, which indicates whether or not CONTACTl is present.
  • the AOL-native presence information is relayed to the AOL TPO 220.
  • the AOL TPO 220 encapsulates the AOL-native presence information to generate XML-structured presence information having an appropriate session ID.
  • the XML-structured presence information is relayed to the message router 170 by the AOL TPO 220.
  • the message router 170 receives the XML-stmctured presence information from the AOL TPO 220, and correlates the XML- structured presence information to the established session using session object 190.
  • the message router 170 relays the XML-structured presence information to the BellSouth IM user agent 115.
  • the presence information of CONTACTl from the Yahoo server 312 and the presence information of CONTACT2 from the MSN server 314 are each determined in a similar fashion.
  • the respective TPOs 220, 222, 224, 226 determine the presence of the respective contacts.
  • the presence information for each of the contacts is ultimately relayed back to the BellSouth user at the BellSouth IM user agent 115.
  • the BellSouth 3M user now has presence information on each of the contacts on the
  • the BellSouth user initiates an IM chat session with CONTACTl from the BellSouth IM user agent 115.
  • the BellSouth IM user agent 115 issues an XML-structured invitation to the message router 170.
  • the message router 170 receives the XML-stmctured invitation and conveys the XML-stmctured invitation to the AOL TPO 220.
  • the AOL TPO 220 receives the XML-stmctured invitation and generates a thread ID, which is used, in one form or another, to track the thread from the BellSouth IM user agent 115 and the AOL IM agent 320. In addition to generating the thread ID, the AOL TPO 220 translates the XML-stmctured invitation into an AOL-native invitation. The AOL TPO 220 issues the AOL-native invitation to the AOL server 310, which relays the AOL-native invitation to CONTACTl at a AOL user agent 320 at an AOL client location. Since the AOL TPO 220 provides the AOL server 310 with AOL-native information related to the thread ID, each invitation may be properly delivered to CONTACTl at the AOL user agent 320.
  • the AOL user agent 320 issues an AOL-native acceptance, which is relayed to the AOL server 310.
  • the AOL server 310 further conveys the AOL-native acceptance to the AOL TPO 220.
  • the AOL TPO 220 receives the AOL-native acceptance and encapsulates the AOL-native acceptance to produce an XML-structured acceptance.
  • the XML-stmctured acceptance is relayed to the message router 170 by the AOL TPO 220.
  • the message router 170 relays the XML-stmctured acceptance to the proper BellSouth IM user agent 115. Upon receiving the BellSouth-native acceptance, a chat session is established between the BellSouth IM user and CONTACTl.
  • the BellSouth user agent 115 During the chat session, the BellSouth user agent 115 generates an XML- structured message.
  • the BellSouth TPO 226 conveys the XML-stmctured message to the message router 170, which subsequently routes the XML-stmctured message to the AOL TPO 220 based on the message ID.
  • the AOL TPO 220 translates the XML-stmctured message into an AOL-native message, and conveys the AOL-native message to the AOL server 310.
  • the message router 170 may further modify the message by, for example, adding additional XML tags or tracking information, encrypting all or sensitive portions of the message, etc.
  • the AOL server 310 5 receives the AOL-native message from the TPO 220 and relays the AOL-native message to CONTACTl at the AOL user agent 320.
  • the AOL user agent 320 generates an AOL-native message.
  • the representative native user agents 320, 322, 324 could also be replaced in part by a plurality of IM user agents similar to the BellSouth IM user agent 115 having the various
  • the AOL-native message has a message ID, or equivalent, to track the message.
  • the AOL-native message is conveyed to the AOL IM server 310, which further conveys the AOL-native message to the AOL TPO 220.
  • the AOL TPO 220 encapsulates the AOL-native message to produce an XML-staictured message.
  • the AOL TPO 220 may further
  • the AOL TPO 220 conveys the XML-stmctured message to the message router 170, which subsequently routes the XML-structured message to the BellSouth IM user at the BellSouth IM user agent 115.
  • the 20 agent 115 may engage in a chat session with the Yahoo user agent 322 and the MSN user agent 324 tlirough the Yahoo TPO 222 and the MSN TPO 224, respectively. While this process is not specifically described here, it will be clear to one of ordinary skill in the art that the Yahoo TPO 222, the MSN TPO 224, the BellSouth TPO 226, or any other TPO (not shown) performs similar functions to the AOL TPO 220. In other words, the various
  • 2.5 TPOs 222, 224, 226 each perform similarly as the AOL TPO 220 to translate between various native protocols and XML.
  • the various TPOs 220, 222, 224 located at the BellSouth client location 110 provide for translation between various non- universal protocols and a single universal protocol, such as XML. Additionally, by having the TPOs 220, 222, 224, 226 located at a client rather than a server, resources of the server are not consumed by translating the various protocols into XML. Thus, server bottlenecks associated with server processing are concomitantly reduced by having the TPOs 220, 222, 224 at the client location. Additionally, server firewall problems may be ameliorated by having the TPOs 220, 222, 224, 226 at the client location.
  • FIGS. 5 and 6 show another embodiment of a system, wherein the TPOs 221, 223,
  • TPOs 221, 223, 225, 227 are located at the abstraction server 124.
  • TPOs 221, 223, 225 are located at the abstraction server 124.
  • a single TPO may be used by multiple JJVI users, thereby reducing the number of instantiated TPOs.
  • the BellSouth user inputs a user BellSouth login name and a BellSouth password at a user interface (not shown) located at the BellSouth IM user agent 115.
  • This information is conveyed to an IM abstraction object 130 located on the abstraction server 124.
  • a message router 175 in the IM abstraction object 130 instantiates a BellSouth TPO 227, an AOL TPO 221, a Yahoo TPO 223, and an MSN TPO 225. at the abstraction server 124.
  • a single TPO can accommodate multiple users from a particular protocol.
  • a single AOL TPO 221 can accommodate multiple AOL users; a single MSN TPO 225 can accommodate multiple MSN users, etc. This reduces the number of TPOs instantiated, thereby reducing some of the processing by the server. Since multiple users can access the same TPO, the TPO generates a separate session ID for each of the multiple users.
  • the abstraction server 124 stores user information 150b, such as the various login names and passwords, as well as the various session objects 191, 193, 195, 197 associated with a particular BellSouth IM user.
  • user information 150b such as the various login names and passwords
  • the logon information is conveyed to the message router 175 at the abstraction server 124, which retrieves the user information 150b.
  • the message router 175 Upon retrieving the user information 150b and the information related to the various TPOs 221, 223, 225, 227, the message router 175 automatically instantiates the BellSouth TPO 227, the AOL TPO 221, the Yahoo TPO 223, and the MSN TPO 225, or utilizes respective existing TPOs.
  • FIG. 6 is a block diagram showing one embodiment in which instantiated TPOs 221, 223, 225, 227 logon to their respective IM servers 310, 312, 314, 126 to provide interoperability between the various protocols.
  • the contact information is stored on its respective server.
  • the AOL contact information would be stored on the BellSouth IM user's AOL account since the AOL TPO 221 is providing an interface to the BellSouth IM user's AOL account.
  • the Yahoo contact information would be stored on the BellSouth IM user's Yahoo account since the Yahoo TPO 223 is providing an interface to the BellSouth JM user's Yahoo account.
  • presence information related to the contacts is further determined by the various TPOs 221, 223, 225, 227. For example, if the BellSouth IM user has added CONTACTl having an AOL IM address and a Yahoo IM address, and CONTACT 2 having only an MSN account, then presence infomiati on of CONTACTl is determined from the AOL server 310 and the Yahoo server 312, and presence information of CONTACT2 is determined from the MSN server 314. While the polling for presence is shown as being initiated by the TPOs 221, 223, 225, 227, the polling of the various servers for presence information may also be initiated by the server or the client.
  • the presence information may be continually refreshed to the various TPOs 221, 223, 225, 227 by the servers 310, 312, 314, 126 without the polling of the servers for the presence information.
  • the AOL TPO 221 generates an AOL-native presence query to determine whether or not CONTACTl is present.
  • the AOL server 310 is polled using
  • the AOL server 310 receives the query and generates AOL-native presence information, which indicates whether or not CONTACTl is present.
  • the AOL-native presence information is relayed to the AOL TPO 221.
  • the AOL TPO 221 encapsulates the AOL-native presence information to generate XML- structured presence information.
  • the XML-stmctured presence information is relayed to the message router 175 by the AOL TPO 221.
  • the message router 175 receives the XML-stmctured presence information from the AOL TPO 221, and correlates the XML- stmctured presence information to the AOL session object 191. Using the AOL session ID from the AOL session object 191, the message router 175 relays the XML-stmctured presence information to the BellSouth IM user agent 115.
  • the Yahoo TPO 223 generates a Yahoo-native presence query to determine whether or not CONTACTl is present.
  • the MSN TPO 225 generates an MSN-native presence query to determine whether or not CONTACT2 is present.
  • the respective TPOs 221, 223, 225, 227 determine the presence of the contacts. The presence information for each of the contacts is ultimately relayed back to the BellSouth user at the BellSouth IM user agent 115. In other words, the BellSouth IM user now has presence information on each of the contacts at the various servers 310, 312, 314, 126.
  • the BellSouth user initiates an IM chat session with CONTACTl from the BellSouth IM user agent 115.
  • the BellSouth IM user agent 115 issues an XML-stmctured invitation to the message router 175.
  • the message router 175 receives the XML-stmctured invitation and conveys the XML-stmctured invitation to the AOL. TPO 221.
  • the AOL TPO 221 receives the XML-stmctured invitation and translates the XML-stmctured invitation into an AOL-native invitation. In addition to translating the XML-stmctured invitation, the AOL TPO 221 generates a thread ID, which is used, in one form or another, to track the thread between the BellSouth JJV1 user agent 115 and the AOL user agent 320. The AOL TPO 221 issues the AOL-native invitation to the AOL server 310, which relays the AOL- native invitation to CONTACTl at an AOL user agent 320 at an AOL client location.
  • each invitation may be properly delivered to CONTACTl at the AOL user agent 320. If CONTACTl at the AOL user agent 320 accepts the invitation, then the AOL user agent 320 issues an AOL-native acceptance, which is relayed to the AOL server 310.
  • the AOL server 310 further conveys the AOL-native acceptance to the AOL TPO 221.
  • the AOL TPO 221 receives the AOL-native acceptance and encapsulates the AOL-native acceptance to produce an XML-stmctured acceptance.
  • the XML-stmctured acceptance is relayed to the message router 175 by the AOL TPO 221.
  • the message router 175 relay the XML-stmctured acceptance to the proper BellSouth IM user agent 115.
  • a chat session is established between the BellSouth IM user and CONTACTl.
  • the BellSouth user agent 115 generates an XML- stmctured message.
  • the BellSouth TPO 227 conveys the XML-stmctured message to the message router 175, which subsequently routes the XML-stmctured message to the AOL TPO 221 based on the message ID.
  • the AOL TPO 221 translates the XML-stmctured message into an AOL-native message.
  • the message router 175 may further modify the message by, for example, adding additional XML tags or tracking information, encrypting all or sensitive portions of the message, etc.
  • the AOL TPO 221 conveys the AOL-native message to the A.OL server 310.
  • the AOL server 31.0 receives the AOL-native message and relays the AOL-native message to CONTACTl at the AOL user agent 320.
  • the AOL user agent 320 generates an AOL-native message.
  • the AOL- native message is conveyed to the AOL IM server 310, which further conveys the AOL- native message to the AOL TPO 221.
  • the AOL TPO 221 encapsulates the AOL-native message to produce an XML-stmctured message.
  • the AOL TPO 221 may further modify the message by, for example, modifying the message header.
  • the AOL TPO 221 conveys the XML-stmctured message to the message router 175, which subsequently routes the XML-stmctured message to the BellSouth IM user at the BellSouth IM user agent 115.
  • a chat session may be established with CONTACTl at the Yahoo user agent 322 using the Yalioo TPO 223.
  • a chat session may be established with CONTACT2 at the MSN user agent 324 using the MSN TPO 225. Since the chat sessions are established through the various TPOs 221, 223, 225, 227, each of the native servers 310, 312, 314, 126 communicate using their respective native protocols Thus, for example, the AOL server 310 uses an AOL-native protocol; the Yahoo server 312 uses the Yahoo-native protocol, etc.
  • each of the TPOs 221, 223, 225, 227 appears as a native client to each of their respective servers 310, 312, 314, 126.
  • the MSN TPO 225 appears as an MSN client to the MSN server 314;
  • the AOL TPO 221 appears as an AOL client to the AOL server 310, etc.
  • none of the servers 310, 312, 314, 126 modify their respective IM protocols or ⁇ M interfaces because the servers 310, 312, 314, 126 are in communication objects that behave as virtual native clients to those servers
  • FIGS. 7 tlirough 12 are data flow diagrams illustrating the data flow through the system of FIGS. 1 A through 4B.
  • the BellSouth IM user has accounts on only AOL and BellSouth.
  • extension of the data flow charts to other IM servers will be clear to one of ordinary skill in the art.
  • a preferred embodiment of a set up process includes the BellSouth IM user agent 115 providing (502) user information to the IM abstraction object 130.
  • the user information may include a user login name and password for various ⁇ M accounts.
  • the user information may include a list of contacts and the contacts' IM addresses. In other embodiments, contact information is not communicated during the setup process.
  • the BellSouth IM user agent 115 can log in (504) to the IM abstraction object 130 by providing a user name and a password to the IM abstraction object.
  • the IM abstraction object 130 verifies the user name and password and looks up (506) additional login information related to the user.
  • the IM abstraction object 130 uses the additional login information to request (508) instantiation of various TPOs by the BellSouth IM user agent 115. Since, in the example embodiment of FIGS.
  • the BellSouth IM user (not shown) has IM accounts on BellSouth and AOL, the IM abstraction object 130 requests (508) instantiation of the BellSouth TPO 226 and the AOL TPO 220.
  • the BellSouth IM user agent 115 instantiates a BellSouth TPO 226 at the BellSouth client location 110.
  • the BellSouth TPO 226 communicates (512) with the BellSouth IM server 126 in order to establish a session with the BellSouth IM server 126.
  • the BellSouth LVI server 126 conveys (514) tokens or other identifiers back to the BellSouth TPO 226, and the BellSouth TPO 226 generates (516) a session ID in response to the tokens or other
  • Session information including the session ID is then stored (518) as a BellSouth session object 196 at the IM abstraction object 130.
  • the BellSouth IM server 126 is co-located with the IM abstraction object 130, while in other embodiments, the BellSouth IM server 126 is located separately from the IM abstraction object 130.
  • the IM abstraction object 130 looks up (506) (again, re-shown for clarity) login information and requests (520) instantiation of an AOL TPO 220.
  • the request (520) is conveyed to the BellSouth IM user agent 115, which instantiates (522) the AOL TPO 220 at the BellSouth client location 110.
  • the AOL TPO 220 communicates 1 ⁇ 524) with the AOL IM server 310, which conveys (526) tokens or other identifiers back to the AOL TPO 220.
  • the AOL TPO 220 generates (528) a session ID using the tokens or other identifiers, and stores (530) session infomiation along with the session ID as an AOL session object 190 at the IM abstraction object 130.
  • the AOL TPO 220 generates (532) an AOL- native login request, which is also a presence query to detemiine presence information of AOL contacts of the. BellSouth IM user.
  • the AOL-native login request is thus used to poll (534) the AOL server 310 for presence infomiation.
  • the AOL server 310 logs the user in and determines (536) presence information of the BellSouth IM user's AOL contacts, and relays (538) a login acknowledgement and the AOL-native presence information to the AOL TPO 220, often in multiple steps in some embodiments.
  • the AOL TPO 220 may not generate (532) a query. Rather, the AOL server 310 may continually update presence infomiation and relay (538) the presence information to the AOL TPO 220 without a query for presence infomiation. In either event, upon receiving the AOL-native login acknowledgement and presence information from the AOL server 310, the AOL TPO 220 encapsulates (540) the presence information using XML to produce XML-stmctured presence information for the IM abstraction object 130. The AOL TPO 220 also generates a socket ID that identifies a port through which the AOL IM session is established, which is correlated with a session ID for that connection.
  • the XML-stmctured infomiation is relayed (542) to the IM abstraction object, which uses the accompanying session ID in the XML-stmctured presence information.
  • the XML-stmctured presence information is relayed (546) from the IM abstraction object to the BellSouth IM user agent 115.
  • the BellSouth IM user has presence infomiation related to all of the BellSouth IM user's AOL contacts.
  • the BellSouth IM user chooses to engage in a chat session with one of the AOL contacts, then the user inputs a session initiation at the BellSouth IM user agent 115.
  • This BellSouth IM user agent 115 receives (548) the user input and issues (550) an XML-stmctured invitation for a chat session to the IM abstraction object 130.
  • the IM abstraction object 130 relays (552) the XML-stmctured invitation to the AOL TPO 220.
  • the AOL TPO 220 receives the XML-stmctured invitation and translates (554) the XML-stmctured invitation into an AOL-native invitation hi translating (554) the XML-stmctured invitation, the AOL TPO 220 may appropriately modify headers and other aspects of the invitation to be consonant with AOL-native protocol.
  • the AOL-native invitation is relayed (556) by the AOL TPO 220 to the AOL server 310, which subsequently relays (557) the AOL-native invitation to the AOL user agent 320.
  • the AOL user agent 320 issues (558) an AOL-native acceptance to the AOL server 310.
  • the AOL-native acceptance is relayed (560) from the AOL server 310 to the AOL TPO 220.
  • the AOL TPO 220 encapsulates (562) the AOL-native acceptance using XML to produce an XML- structured acceptance.
  • the XML-structured acceptance is relayed (563) from the AOL TPO 220 to the EVl abstraction object 130, which determines (564) the chat session from information in the XML-stmctured acceptance.
  • the XML-stmctured acceptance is then properly relayed (566) to the BellSouth IM user agent 115, at which time an IM chat session is established (568).
  • the BellSouth IM user agent 115 generates XML-stmctured chat messages, which are translated into AOL-native chat messages at the AOL TPO 220.
  • the AOL-native chat messages are conveyed from the AOL TPO 220 to the AOL server 310, and subsequently to the AOL user agent 320 as an AOL-native chat message.
  • the TPOs may be instantiated at the abstraction server 124 rather than at the client location 110.
  • the IM abstraction object 130 instantiates the TPOs at the abstraction server 124.
  • the TPOs at the abstraction server 124 provide part of the interface between the BellSouth user agent 115 and the various servers 310, 312, 314, 126.
  • 195, 196, 197, the message router 170, 175, and the TPOs 220, 221, 222, 223, 224, 225, 226, 227 of the present invention can be implemented in hardware, software,
  • the The IM user agents 115, 320, 322, 324, 326, the session objects 190, 191, 192, 193, 194, 195, 196, 197, the message router 170, 175, and the TPOs 220, 221, 222, 223, 224, 225, 226, 227 are implemented in software or firmware that is stored in a memory and that is executed by a suitable instruction execution system.
  • the IM user agents 115, 320, 322, 324, 326, the session objects 190, 191, 192, 193, 194, 195, 196, 197, the message router 170, 175, and the TPOs 220, 221, 222, 223, 224, 225, 226, 227 can be implemented with any or a combination of the following technologies, which are all well known in the art: Internet Appliances, a discrete logic circuit(s) having logic gates for implementing logic functions upon data signals, an application specific integrated circuit (ASIC) having appropriate combinational logic gates, a programmable gate array(s) (PGA), a field programmable gate array (FPGA), etc.
  • ASIC application specific integrated circuit
  • PGA programmable gate array
  • FPGA field programmable gate array
  • the IM user agents 115, 320, 322, 324, 326, the session objects 190, .191, 192, 193, 194, 195, 196, 197, the message router 170, 175, and the TPOs 220, 221, 222, 223, 224, 225, 226, 227 may also be implemented as a computer program, which comprises an ordered listing of executable instmctions for implementing logical functions.
  • the computer program can be embodied in an computer-readable medium for use by or in connection with an instruction execution system, apparatus, or device, such as a computer-based system, processor-containing system, or other system that can fetch the instmctions from the instruction execution system, apparatus, or device and execute the instmctions.
  • a "computer-readable medium” can be any means that can contain, store, communicate, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device.
  • the computer-readable medium can be, for example but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, device, or propagation medium.
  • the computer- readable medium would include the following: an electrical connection (electronic) having one or more wires, a portable computer diskette (magnetic), a random access memory (RAM) (electronic), a read-only memory (ROM) (electronic), an erasable programmable read-only memory (EPROM or Flash memory) (electronic), an optical fiber (optical), and a portable compact disc read-only memory (CDROM) (optical).
  • an electrical connection having one or more wires
  • a portable computer diskette magnetic
  • RAM random access memory
  • ROM read-only memory
  • EPROM or Flash memory erasable programmable read-only memory
  • CDROM portable compact disc read-only memory
  • the computer-readable medium could even be paper or another suitable medium upon which the program is printed, as the program can be electronically captured, via for instance optical scanning of the paper or other medium, then compiled, interpreted or otherwise processed in a suitable manner if necessary, and then stored in a computer memory.
  • the IM abstraction object 130 is located on the abstraction server 124 in the various embodiments, it will be clear to one of ordinary skill in the art that the IM abstraction object 130 may be located at a client location, rather than at a server. Also, while IM has specifically been described in detail in FIGS. 1 A through 12, it will be clear to one of ordinary skill in the art that the IM implementation may easily be extended to other messaging techniques such as email, voice-over Internet protocol (VoIP), video-conferencing, etc.
  • VoIP voice-over Internet protocol
  • the IM abstraction object 130 and the TPOs 220, 221, 222, 223, 224, 225, 226, 227 may be implemented outside of the IM context, hi other words, the architecture of the IM abstraction object 130 and the TPOs 220, 221, 222, 223, 224, 225, 226, 227 is independent of the type of messaging technology, and may be adapted to translate native protocols for various messaging technologies into a universal language, thereby providing a user with similar options as those discussed herein.
  • the BellSouth client location 110 is shown with only a BellSouth IM user agent 115, it will be clear to one of ordinary skill in the art that the BellSouth client location 110 may include other conventional components.
  • BellSouth IM user agent 115 is described above as pre-existing at the BellSouth client location 110, it will be clear to one of ordinary skill in the art that the BellSouth IM user agent 115 may be downloaded from a website and installed at the BellSouth client location 110 or, alternatively, installed at the BellSouth client location 110 using other conventional techniques, Also, while specific servers are shown in the various embodiments, it will be clear to one of ordinary art that these specific servers are

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Business, Economics & Management (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Computer Security & Cryptography (AREA)
  • Human Resources & Organizations (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Computer Hardware Design (AREA)
  • Strategic Management (AREA)
  • Marketing (AREA)
  • Data Mining & Analysis (AREA)
  • Computing Systems (AREA)
  • Economics (AREA)
  • General Engineering & Computer Science (AREA)
  • Operations Research (AREA)
  • Quality & Reliability (AREA)
  • Tourism & Hospitality (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

L'invention concerne des systèmes et des procédés dans lesquels une interface utilisateur unique envoie des informations à un utilisateur via des sessions de messagerie multiple, chacune possédant un protocole de messagerie différent.
PCT/US2003/029066 2002-09-17 2003-09-15 Client de message a consolidation multiple du systeme de message WO2004027559A2 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
AU2003278822A AU2003278822A1 (en) 2002-09-17 2003-09-15 Message client with multiple message system consolidation

Applications Claiming Priority (6)

Application Number Priority Date Filing Date Title
US41133602P 2002-09-17 2002-09-17
US60/411,336 2002-09-17
US41961302P 2002-10-17 2002-10-17
US60/419,613 2002-10-17
US27440502A 2002-10-18 2002-10-18
US10/274,405 2002-10-18

Publications (3)

Publication Number Publication Date
WO2004027559A2 true WO2004027559A2 (fr) 2004-04-01
WO2004027559A3 WO2004027559A3 (fr) 2004-07-15
WO2004027559A8 WO2004027559A8 (fr) 2004-08-19

Family

ID=32034178

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2003/029066 WO2004027559A2 (fr) 2002-09-17 2003-09-15 Client de message a consolidation multiple du systeme de message

Country Status (2)

Country Link
AU (1) AU2003278822A1 (fr)
WO (1) WO2004027559A2 (fr)

Cited By (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2006014594A1 (fr) * 2004-07-07 2006-02-09 At & T Wireless Services, Inc. Systeme et procede d'organisation et d'affichage de donnees dans une interface de messagerie instantanee
WO2008001038A1 (fr) * 2006-06-28 2008-01-03 British Telecommunications Public Limited Company Procédé et appareil de conversion de messages
WO2008029224A2 (fr) * 2006-08-29 2008-03-13 Nokia Corp. Extension au repos active
US7444429B2 (en) 2002-09-17 2008-10-28 William Todd Daniell System uses transport protocol objects locate at user agent location to provide translation between different instant messaging protocols
US7469301B2 (en) 2002-09-17 2008-12-23 At&T Intellectual Property I, L.P. Server-based message protocol translation
US7603467B2 (en) 2002-04-29 2009-10-13 At&T Intellectual Property I, L.P. Instant messaging architecture and system for interoperability and presence management
US7657598B2 (en) 2002-09-17 2010-02-02 At&T Intellectual Property I, L.P. Address book for integrating email and instant messaging (IM)
KR100966504B1 (ko) * 2004-11-19 2010-06-29 노키아 코포레이션 다수의 동시 통신 세션들의 관리를 용이하게 하는 그래픽사용자 인터페이스를 제공하는 방법, 장치 및 컴퓨터프로그램 생성물
EP2234351A1 (fr) * 2009-02-26 2010-09-29 Research In Motion Limited Système et procédé de commutation entre des clients de messagerie
US7921160B2 (en) 2002-09-17 2011-04-05 At&T Intellectual Property I, L.P. Initiating instant messaging (IM) chat sessions from email messages
US7933957B2 (en) 2002-09-17 2011-04-26 At&T Intellectual Property Ii, L.P. Tracking email and instant messaging (IM) thread history
US8363794B2 (en) 2006-08-29 2013-01-29 Nokia Corporation Voice mail extension
US8385517B2 (en) 2006-08-29 2013-02-26 Nokia Corporation Replying through different channels
US20160110685A1 (en) * 2014-10-21 2016-04-21 International Business Machines Corporation Allowing a user to easily collaborate with users from outside organizations where the user has visitor status by selecting an object associated with the outside organization that is displayed on the user interface of the user's computing device
US9559867B2 (en) 2008-05-30 2017-01-31 Google Technology Holdings LLC Contact group dynamics in networked communication devices
US11475109B2 (en) 2009-09-01 2022-10-18 James J. Nicholas, III System and method for cursor-based application management

Non-Patent Citations (5)

* Cited by examiner, † Cited by third party
Title
PETER SAINT-ANDRE: 'Jabber FAQ and User guide' JABBER.ORG, [Online] 13 May 2001, pages 1 - 39, XP002976958 Retrieved from the Internet: <URL:http://www.jabber.org> *
PETER SAINT-ANDRE: 'XML messaging with jabber' OPENP2P.COM, [Online] 06 October 2000, pages 1 - 8, XP002976960 Retrieved from the Internet: <URL:http://www.openp2p.com> *
'Startup programs', [Online] 22 November 1998, pages 1 - 3, XP002976959 Retrieved from the Internet: <URL:http://www.malvino.com/ep/startup.htm> *
'Trillian 0.71', [Online] 24 January 2002, pages 1 - 15, XP002976962 Retrieved from the Internet: <URL:http://www.ceruleanstudios.com> *
'Trillian 0.74 popular', [Online] 10 September 2002, pages 1 - 2, XP002976961 Retrieved from the Internet: <URL:http://www.download.com> *

Cited By (25)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7603467B2 (en) 2002-04-29 2009-10-13 At&T Intellectual Property I, L.P. Instant messaging architecture and system for interoperability and presence management
US7844716B2 (en) 2002-04-29 2010-11-30 At&T Intellectual Property I, L.P. Instant messaging architecture and system for interoperability and presence management
US7933957B2 (en) 2002-09-17 2011-04-26 At&T Intellectual Property Ii, L.P. Tracking email and instant messaging (IM) thread history
US7921160B2 (en) 2002-09-17 2011-04-05 At&T Intellectual Property I, L.P. Initiating instant messaging (IM) chat sessions from email messages
US7469301B2 (en) 2002-09-17 2008-12-23 At&T Intellectual Property I, L.P. Server-based message protocol translation
US8224915B2 (en) 2002-09-17 2012-07-17 At&T Intellectual Property I, Lp Initiating instant messaging (IM) chat sessions from email messages
US7657598B2 (en) 2002-09-17 2010-02-02 At&T Intellectual Property I, L.P. Address book for integrating email and instant messaging (IM)
US8458274B2 (en) 2002-09-17 2013-06-04 At&T Intellectual Property I, L.P. Initiating instant messaging (IM) chat sessions from email messages
US7444429B2 (en) 2002-09-17 2008-10-28 William Todd Daniell System uses transport protocol objects locate at user agent location to provide translation between different instant messaging protocols
WO2006014594A1 (fr) * 2004-07-07 2006-02-09 At & T Wireless Services, Inc. Systeme et procede d'organisation et d'affichage de donnees dans une interface de messagerie instantanee
KR100966504B1 (ko) * 2004-11-19 2010-06-29 노키아 코포레이션 다수의 동시 통신 세션들의 관리를 용이하게 하는 그래픽사용자 인터페이스를 제공하는 방법, 장치 및 컴퓨터프로그램 생성물
US8489934B2 (en) 2006-06-28 2013-07-16 British Telecommunications Public Limited Company Messaging system
WO2008001038A1 (fr) * 2006-06-28 2008-01-03 British Telecommunications Public Limited Company Procédé et appareil de conversion de messages
US8363794B2 (en) 2006-08-29 2013-01-29 Nokia Corporation Voice mail extension
WO2008029224A3 (fr) * 2006-08-29 2008-07-10 Nokia Corp Extension au repos active
US8385517B2 (en) 2006-08-29 2013-02-26 Nokia Corporation Replying through different channels
WO2008029224A2 (fr) * 2006-08-29 2008-03-13 Nokia Corp. Extension au repos active
US9559867B2 (en) 2008-05-30 2017-01-31 Google Technology Holdings LLC Contact group dynamics in networked communication devices
EP2234351A1 (fr) * 2009-02-26 2010-09-29 Research In Motion Limited Système et procédé de commutation entre des clients de messagerie
US11960580B2 (en) 2009-09-01 2024-04-16 Transparence Llc System and method for cursor-based application management
US11475109B2 (en) 2009-09-01 2022-10-18 James J. Nicholas, III System and method for cursor-based application management
US10075433B2 (en) 2014-10-21 2018-09-11 International Business Machines Corporation Allowing a user to easily collaborate with users from outside organizations where the user has visitor status by selecting an object associated with the outside organization that is displayed on the user interface of the user's computing device
US10380549B2 (en) 2014-10-21 2019-08-13 International Business Machines Corporation Allowing a user to easily collaborate with users from outside organizations where the user has visitor status by selecting an object associated with the outside organization that is displayed on the user interface of the user's computing device
US10380550B2 (en) 2014-10-21 2019-08-13 International Business Machines Corporation Allowing a user to easily collaborate with users from outside organizations where the user has visitor status by selecting an object associated with the outside organization that is displayed on the user interface of the user's computing device
US20160110685A1 (en) * 2014-10-21 2016-04-21 International Business Machines Corporation Allowing a user to easily collaborate with users from outside organizations where the user has visitor status by selecting an object associated with the outside organization that is displayed on the user interface of the user's computing device

Also Published As

Publication number Publication date
AU2003278822A8 (en) 2004-04-08
WO2004027559A3 (fr) 2004-07-15
WO2004027559A8 (fr) 2004-08-19
AU2003278822A1 (en) 2004-04-08

Similar Documents

Publication Publication Date Title
USRE41848E1 (en) System using transport protocol objects located at agent location to generate session ID and to provide translation between different instant messaging protocols
US7469301B2 (en) Server-based message protocol translation
US6976092B1 (en) System that using transport protocol objects located at agent location to generate session ID and to provide translation between different instant messaging protocols
US9619466B2 (en) Message translations
US7818375B2 (en) Providing advanced instant messaging (IM) notification
KR100722916B1 (ko) 통신 관리자가 장치된 컴퓨터 시스템에 의한액티브티-베이스 협력 방법 및 장치
CN101815039B (zh) 好友列表的被动个性化
US20070100944A1 (en) Uniform resource identifier decoration to enable connectivity for instant messaging providers serving non-authoritative namespaces
WO2004027559A2 (fr) Client de message a consolidation multiple du systeme de message
US8959164B2 (en) Tri-state presence indicator
EP0838774A2 (fr) Système de distribution de documents électroniques
EP1365553A1 (fr) Procédé et dispositif de messagerie instantanée
US20050165933A1 (en) System and method for proxy-enabling a wireless device to an existing IP-based service
US20060045124A1 (en) Method and apparatus for providing access controls to communication services
US10122658B2 (en) System for instant messaging the sender and recipients of an e-mail message
US8082311B2 (en) Authentication of electronic data
WO2006071030A1 (fr) Systeme et procede permettant de partager des resultats de recherche au moyen d&#39;un messager
US9043418B2 (en) Systems and methods for instant messaging persons referenced in an electronic message
WO2004059417A2 (fr) Procede et systeme permettant d&#39;effectuer des transactions de messagerie instantanee entre des fournisseurs de service disparates
US8996562B2 (en) Computer-implemented method and system for enabling anonymous communication between networked users based on common search queries
CA2691879A1 (fr) Systeme, composant et procede de messagerie instantanee pour des services supplementalres
CN107483321A (zh) 一种即时通信方法
KR20030021504A (ko) 이메일을 이용한 실시간 쌍방향 통신 시스템 및 방법

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A2

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE EG ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NI NO NZ OM PG PH PL PT RO RU SC SD SE SG SK SL SY TJ TM TN TR TT TZ UA UG UZ VC VN YU ZA ZM ZW

AL Designated countries for regional patents

Kind code of ref document: A2

Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LU MC NL PT RO SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
CFP Corrected version of a pamphlet front page
CR1 Correction of entry in section i

Free format text: IN PCT GAZETTE 14/2004 UNDER (22) REPLACE "16 SEPTEMBER 2003 (16.09.03)" BY "15 SEPTEMBER 2003 (15.09.03)"

122 Ep: pct application non-entry in european phase
NENP Non-entry into the national phase

Ref country code: JP

WWW Wipo information: withdrawn in national office

Country of ref document: JP