USRE41848E1 - System using transport protocol objects located at agent location to generate session ID and to provide translation between different instant messaging protocols - Google Patents
System using transport protocol objects located at agent location to generate session ID and to provide translation between different instant messaging protocols Download PDFInfo
- Publication number
- USRE41848E1 USRE41848E1 US12/286,136 US28613608A USRE41848E US RE41848 E1 USRE41848 E1 US RE41848E1 US 28613608 A US28613608 A US 28613608A US RE41848 E USRE41848 E US RE41848E
- Authority
- US
- United States
- Prior art keywords
- message
- aol
- protocol
- user agent
- xml
- Prior art date
- Legal status (The legal status 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 status listed.)
- Expired - Lifetime, expires
Links
Images
Classifications
-
- 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
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/14—Session management
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/56—Provisioning of proxy services
- H04L67/565—Conversion or adaptation of application format or content
-
- 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
-
- 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. However, apart from general features associated with IM, RFC 2778 and RFC 2779 provide very little instruction for actually implementing IM by various vendors.
- the present disclosure provides systems and methods for providing interoperability between various Internet protocols.
- one embodiment of the system comprises an instant messaging (IM) user agent, and a plurality of transport protocol objects (TPOs) instantiated at an IM user agent location.
- IM instant messaging
- TPOs transport protocol objects
- each of the plurality of TPOs is adapted to provide a translation between a first IM protocol and a different IM protocol.
- the IM user agent transmits and receives IM messages using the first IM protocol.
- one embodiment of the method comprises the steps of instantiating a plurality of transport protocol objects (TPOs) at an instant messaging (IM) user agent location having an IM user agent, establishing a plurality of connections between the plurality of TPOs and a plurality of servers, and providing a communication pathway between the IM user agent and the plurality of servers through the plurality of instantiated TPOs.
- TPOs transport protocol objects
- IM instant messaging
- each of the plurality of TPOs is adapted to provide a translation between a first IM protocol and a different IM protocol.
- An IM user agent at the IM user agent location transmits and receives IM messages using the first IM protocol, while each of the plurality of servers transmits and receives IM messages using one of the different IM protocols.
- FIG. 1A is a block diagram showing one embodiment of a user agent uploading user information to a server.
- FIGS. 1B 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.
- FIG. 1A is a block diagram showing an example embodiment of a system having an instant messaging (IM) abstraction object 130 .
- a BellSouth IM user agent 115 at a BellSouth client location 110 is in 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 150 a 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.
- a BellSouth user may provide an IM login name and password for each of the user's accounts as part of the user information 150 a.
- the inputting of the user information 150 a is shown in FIGS. 1B and 1C .
- a mechanism may be provided for a user to create an account with other message services.
- FIGS. 1B and 1C show two embodiments of user interfaces 102 a, 102 b for inputting login names and passwords at the BellSouth IM user agent 115 .
- a BellSouth IM user Prior to being presented the user interfaces 102 a, 102 b, a BellSouth IM user preferably enters a BellSouth login name (e.g., username) and password.
- FIG. 1B shows a user interface 102 a for signing onto a BellSouth IM user's AOL account.
- the AOL user interface 102 a provides an input box 104 a adapted to receive the AOL login name (or screen name) of the BellSouth IM user.
- the AOL user interface 102 a provides an input box 106 a 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 108 a to the BellSouth IM user.
- the status indication 108 a indicates whether or not the BellSouth IM user is online at AOL.
- the status indication 108 a 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 103 a and sign-off 105 a options to the BellSouth IM user so that the BellSouth IM user can manually initiate and terminate a login to the AOL server.
- FIG. 1C shows a user interface 102 b for signing onto a BellSouth IM user's MSN account. Similar to the AOL user interface, the MSN user interface 102 b provides an input box 104 b adapted to receive the MSN login name of the BellSouth IM user. Also, the MSN user interface provides 102 b an input box 106 b adapted to receive the MSN password associated with the MSN login name. Upon entering the MSN login name and the MSN password, the MSN user interface provides a status indication 108 b to the BellSouth IM user. The status indication 108 b indicates whether or not the BellSouth IM user is online at MSN.
- 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 150 b to retrieve login names and passwords for each of the IM accounts of the BellSouth IM user.
- the BellSouth login user-name and password may be different from a username 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 10 .
- TPO BellSouth transport protocol object
- AOL TPO 220 AOL TPO 220
- Yahoo TPO 222 Yahoo TPO
- MSN TPO 224 MSN TPO 224
- FIG. 2 by providing a single BellSouth IM user login and password, multiple TPOs are instantiated because the information needed to instantiate the various TPOs is already stored at the IM abstraction object 130 .
- Other embodiments include transport mechanisms launched or activated in other manners.
- 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.
- 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.
- 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 .
- an add-contact user interface is provided to the BellSouth IM user.
- An example add-contact user interface 202 is shown in FIG. 4 A.
- 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 IM user may add contacts from any account for which the BellSouth LM user also has an account.
- 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 information would be stored on the Yahoo server at the user's Yahoo account.
- FIG. 4B shows an example contact list 302 .
- the various contacts are automatically grouped together by their 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 IM 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 arc shown in different colors to easily differentiate differences in presence information (e.g., not present, present, busy, etc.).
- the indication 304 for available contacts may be shown in green (shown in FIG. 4B as hashed circles)
- the indication 304 for unavailable contacts e.g., BigHat, Johnnie, Gene, etc.
- grey shown in grey
- the indication 304 for busy contacts e.g., Judy, Mitch, etc.
- the indication 304 for busy contacts may be shown in red (shown in FIG. 4B as filled circles).
- 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.
- the message router 170 receives the XML-structured presence information from the AOL TPO 220 , and correlates the XML-structured presence information to the established session using session object 190 . Using the AOL session object 190 identified by the session ID from the AOL TPO 220 , the message router 170 relays the XML-structured presence information to the BellSouth IM user agent 115 .
- the presence information of CONTACT1 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 IM user now has presence information on each of the contacts on the various servers 310 , 312 , 314 , 126 .
- the AOL TPO 220 may further modify the message by, for example, altering the header of the message.
- the AOL TPO 220 conveys the XML-structured 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 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 .
- Similar to the embodiment of FIG. 2 by inputting a single user name and password, multiple TPOs (or sessions within existing TPOs) are generated because the necessary information is stored at the abstraction server.
- 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 IM user's Yahoo account.
- the AOL TPO 221 In operation, the AOL TPO 221 generates an AOL-native presence query to determine whether or not CONTACT1 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 CONTACT1 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-structured presence information is relayed to the message router 175 by the AOL TPO 221 .
- the message router 175 receives the XML-structured presence information from the AOL TPO 221 , and correlates the XML-structured 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-structured presence information to the BellSouth IM user agent 115 .
- the AOL TPO 221 In addition to translating the XML-structured invitation, the AOL TPO 221 generates a thread ID, which is used, in one form or another, to track the thread between the BellSouth IM 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 CONTACT1 at an AOL user agent 320 at an AOL client location. Since the AOL TPO 221 provides the AOL server 310 with information related to the thread ID, each invitation may be properly delivered to CONTACT1 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 221 .
- the AOL TPO 221 receives the AOL-native acceptance and encapsulates the AOL-native acceptance to produce an XML-structured acceptance.
- the XML-structured acceptance is relayed to the message router 175 by the AOL TPO 221 . Since the XML-structured acceptance includes information related to the thread ID for that particular IM session, the message router 175 relay the XML-structured acceptance to the proper BellSouth IM user agent 115 .
- a chat session is established between the BellSouth IM user and CONTACT1.
- the BellSouth user agent 115 During the chat session, the BellSouth user agent 115 generates an XML-structured message.
- the BellSouth TPO 227 conveys the XML-structured message to the message router 175 , which subsequently routes the XML-structured message to the AOL TPO 221 based on the message ID.
- the AOL TPO 221 translates the XML-structured 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 Upon translating the message, the AOL TPO 221 conveys the AOL-native message to the AOL server 310 .
- the AOL server 310 receives the AOL-native message and relays the AOL-native message to CONTACT1 at the AOL user agent 320 .
- a chat session may be established with CONTACT1 at the Yahoo user agent 322 using the Yahoo 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.
- the AOL server 310 uses an AOL-native protocol
- the Yahoo server 312 uses the Yahoo-native protocol, etc.
- FIGS. 7 through 12 are data flow diagrams illustrating the data flow through the system of FIGS. 1A 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.
- the BellSouth IM 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 identifiers. 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 AOL TPO 220 Upon instantiating ( 522 ) the AOL TPO 220 , the AOL TPO 220 communicates ( 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 information along with the session ID as an AOL session object 190 at the IM abstraction object 130 .
- the AOL TPO 220 may not generate ( 532 ) a query. Rather, the AOL server 310 may continually update presence information and relay ( 538 ) the presence information to the AOL TPO 220 without a query for presence information. 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-structured 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-structured information is relayed ( 542 ) to the IM abstraction object, which uses the accompanying session ID in the XML-structured presence information.
- the XML-structured presence information is relayed ( 546 ) from the IM abstraction object to the BellSouth IM user agent 115 .
- the BellSouth IM user has presence information 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-structured invitation for a chat session to the IM abstraction object 130 .
- the IM abstraction object 130 relays ( 552 ) the XML-structured invitation to the AOL TPO 220 .
- the AOL TPO 220 receives the XML-structured invitation and translates ( 554 ) the XML-structured invitation into an AOL-native 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 . If the invitation is accepted by the BellSouth IM user's AOL contact, then 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 IM abstraction object 130 , which determines ( 564 ) the chat session from information in the XML-structured acceptance.
- the XML-structured 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-structured chat messages, which are translated into AOL-native chat messages at the AOL TPO 220 .
- the AOL-native chat messages are conveyed ( 570 , 572 , 574 ) 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 IM user agent 115 and the various servers 310 , 312 , 314 , 126 .
- 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 of the present invention can be implemented in hardware, software, firmware, or a combination thereof.
- 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 instructions for implementing logical functions.
- the computer program can be embodied in any 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 instructions from the instruction execution system, apparatus, or device and execute the instructions.
- 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.
- AOL server 310 a Yahoo server 312 , an MSN server 314 , and a BellSouth IM server 126 have been shown in the example embodiments, it will be clear to one of ordinary skill in the art that the systems and methods as outlined above may be extended to other Internet-based IM protocols.
- XML-structured information is chosen as a preferred embodiment, it will be clear to one of ordinary skill in the art that other languages or protocols may be used in place of XML, so long as those protocols provide for broad Internet applications.
- 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. 1A 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. Thus, the IM abstraction object 130 and the TPOs 220 , 221 , 222 , 223 , 224 , 225 , 226 , 227 may be implemented outside of the IM context.
- VoIP voice-over Internet protocol
- 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.
- the 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 foreign servers in that the servers do not use XML as their native protocol. All such changes, modifications, and alterations should therefore be seen as within the scope of the present invention.
Abstract
Description
Claims (20)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US12/286,136 USRE41848E1 (en) | 2002-09-17 | 2008-09-24 | System using transport protocol objects located at agent location to generate session ID and to provide translation between different instant messaging protocols |
Applications Claiming Priority (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US41133602P | 2002-09-17 | 2002-09-17 | |
US41961302P | 2002-10-17 | 2002-10-17 | |
US10/274,408 US6976092B1 (en) | 2002-09-17 | 2002-10-18 | System that using transport protocol objects located at agent location to generate session ID and to provide translation between different instant messaging protocols |
US12/286,136 USRE41848E1 (en) | 2002-09-17 | 2008-09-24 | System using transport protocol objects located at agent location to generate session ID and to provide translation between different instant messaging protocols |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/274,408 Reissue US6976092B1 (en) | 2002-09-17 | 2002-10-18 | System that using transport protocol objects located at agent location to generate session ID and to provide translation between different instant messaging protocols |
Publications (1)
Publication Number | Publication Date |
---|---|
USRE41848E1 true USRE41848E1 (en) | 2010-10-19 |
Family
ID=32034179
Family Applications (3)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/210,187 Expired - Lifetime US7444429B2 (en) | 2002-09-17 | 2005-08-23 | System uses transport protocol objects locate at user agent location to provide translation between different instant messaging protocols |
US12/284,273 Expired - Lifetime US7849220B2 (en) | 2002-09-17 | 2008-09-19 | System using transport protocol objects located at a user agent location to provide translation between different instant messaging protocols |
US12/286,136 Expired - Lifetime USRE41848E1 (en) | 2002-09-17 | 2008-09-24 | System using transport protocol objects located at agent location to generate session ID and to provide translation between different instant messaging protocols |
Family Applications Before (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/210,187 Expired - Lifetime US7444429B2 (en) | 2002-09-17 | 2005-08-23 | System uses transport protocol objects locate at user agent location to provide translation between different instant messaging protocols |
US12/284,273 Expired - Lifetime US7849220B2 (en) | 2002-09-17 | 2008-09-19 | System using transport protocol objects located at a user agent location to provide translation between different instant messaging protocols |
Country Status (3)
Country | Link |
---|---|
US (3) | US7444429B2 (en) |
AU (1) | AU2003272486A1 (en) |
WO (1) | WO2004027561A2 (en) |
Cited By (30)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10616151B1 (en) * | 2018-10-17 | 2020-04-07 | Asana, Inc. | Systems and methods for generating and presenting graphical user interfaces |
US10623359B1 (en) | 2018-02-28 | 2020-04-14 | Asana, Inc. | Systems and methods for generating tasks based on chat sessions between users of a collaboration environment |
US10977434B2 (en) | 2017-07-11 | 2021-04-13 | Asana, Inc. | Database model which provides management of custom fields and methods and apparatus therfor |
US11204683B1 (en) | 2019-01-09 | 2021-12-21 | Asana, Inc. | Systems and methods for generating and tracking hardcoded communications in a collaboration management platform |
US11288081B2 (en) | 2019-01-08 | 2022-03-29 | Asana, Inc. | Systems and methods for determining and presenting a graphical user interface including template metrics |
US11327645B2 (en) | 2018-04-04 | 2022-05-10 | Asana, Inc. | Systems and methods for preloading an amount of content based on user scrolling |
US11341444B2 (en) | 2018-12-06 | 2022-05-24 | Asana, Inc. | Systems and methods for generating prioritization models and predicting workflow prioritizations |
US11405435B1 (en) | 2020-12-02 | 2022-08-02 | Asana, Inc. | Systems and methods to present views of records in chat sessions between users of a collaboration environment |
US11449836B1 (en) | 2020-07-21 | 2022-09-20 | Asana, Inc. | Systems and methods to facilitate user engagement with units of work assigned within a collaboration environment |
US11553045B1 (en) | 2021-04-29 | 2023-01-10 | Asana, Inc. | Systems and methods to automatically update status of projects within a collaboration environment |
US11561996B2 (en) | 2014-11-24 | 2023-01-24 | Asana, Inc. | Continuously scrollable calendar user interface |
US11568339B2 (en) | 2020-08-18 | 2023-01-31 | Asana, Inc. | Systems and methods to characterize units of work based on business objectives |
US11620615B2 (en) | 2018-12-18 | 2023-04-04 | Asana, Inc. | Systems and methods for providing a dashboard for a collaboration work management platform |
US11632260B2 (en) | 2018-06-08 | 2023-04-18 | Asana, Inc. | Systems and methods for providing a collaboration work management platform that facilitates differentiation between users in an overarching group and one or more subsets of individual users |
US11636432B2 (en) | 2020-06-29 | 2023-04-25 | Asana, Inc. | Systems and methods to measure and visualize workload for completing individual units of work |
US11635884B1 (en) | 2021-10-11 | 2023-04-25 | Asana, Inc. | Systems and methods to provide personalized graphical user interfaces within a collaboration environment |
US11676107B1 (en) | 2021-04-14 | 2023-06-13 | Asana, Inc. | Systems and methods to facilitate interaction with a collaboration environment based on assignment of project-level roles |
US11694162B1 (en) | 2021-04-01 | 2023-07-04 | Asana, Inc. | Systems and methods to recommend templates for project-level graphical user interfaces within a collaboration environment |
US11720378B2 (en) | 2018-04-02 | 2023-08-08 | Asana, Inc. | Systems and methods to facilitate task-specific workspaces for a collaboration work management platform |
US11756000B2 (en) | 2021-09-08 | 2023-09-12 | Asana, Inc. | Systems and methods to effectuate sets of automated actions within a collaboration environment including embedded third-party content based on trigger events |
US11763259B1 (en) | 2020-02-20 | 2023-09-19 | Asana, Inc. | Systems and methods to generate units of work in a collaboration environment |
US11769115B1 (en) | 2020-11-23 | 2023-09-26 | Asana, Inc. | Systems and methods to provide measures of user workload when generating units of work based on chat sessions between users of a collaboration environment |
US11782737B2 (en) | 2019-01-08 | 2023-10-10 | Asana, Inc. | Systems and methods for determining and presenting a graphical user interface including template metrics |
US11792028B1 (en) | 2021-05-13 | 2023-10-17 | Asana, Inc. | Systems and methods to link meetings with units of work of a collaboration environment |
US11803814B1 (en) | 2021-05-07 | 2023-10-31 | Asana, Inc. | Systems and methods to facilitate nesting of portfolios within a collaboration environment |
US11809222B1 (en) | 2021-05-24 | 2023-11-07 | Asana, Inc. | Systems and methods to generate units of work within a collaboration environment based on selection of text |
US11836681B1 (en) | 2022-02-17 | 2023-12-05 | Asana, Inc. | Systems and methods to generate records within a collaboration environment |
US11847613B2 (en) | 2020-02-14 | 2023-12-19 | Asana, Inc. | Systems and methods to attribute automated actions within a collaboration environment |
US11863601B1 (en) | 2022-11-18 | 2024-01-02 | Asana, Inc. | Systems and methods to execute branching automation schemes in a collaboration environment |
US11900323B1 (en) | 2020-06-29 | 2024-02-13 | Asana, Inc. | Systems and methods to generate units of work within a collaboration environment based on video dictation |
Families Citing this family (20)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7016978B2 (en) | 2002-04-29 | 2006-03-21 | Bellsouth Intellectual Property Corporation | Instant messaging architecture and system for interoperability and presence management |
AU2003272486A1 (en) | 2002-09-17 | 2004-04-08 | Bellsouth Intellectual Property Corporation | Client-based message protocol translation |
US7035942B2 (en) | 2002-09-17 | 2006-04-25 | Bellsouth Intellectual Property Corp. | Server-based message protocol translation |
US7529853B2 (en) * | 2003-06-25 | 2009-05-05 | Oracle International Corporation | Universal IM and presence aggregation on technology-specific client |
US8028073B2 (en) | 2003-06-25 | 2011-09-27 | Oracle International Corporation | Mobile meeting and collaboration |
US9094805B2 (en) * | 2003-06-25 | 2015-07-28 | Oracle International Corporation | Mobile messaging concierge |
TWI255116B (en) * | 2004-07-09 | 2006-05-11 | Xcome Technology Co Ltd | Integrated real-time message system with gateway function, and its implementation method |
US7844675B2 (en) * | 2005-12-15 | 2010-11-30 | At&T Intellectual Property I, L.P. | Accessing web services |
US7792912B2 (en) * | 2007-03-30 | 2010-09-07 | International Business Machines Corporation | Product, method and system for managing multiple user IDS in instant messaging or email computer software applications |
US8060568B2 (en) * | 2007-05-29 | 2011-11-15 | SAP Portal Israel Ltd. | Real time messaging framework hub to intercept and retransmit messages for a messaging facility |
US9716764B2 (en) * | 2007-07-25 | 2017-07-25 | Yahoo! Inc. | Display of communication system usage statistics |
US20100088753A1 (en) * | 2008-10-03 | 2010-04-08 | Microsoft Corporation | Identity and authentication system using aliases |
KR101306134B1 (en) * | 2008-11-24 | 2013-09-09 | 삼성전자주식회사 | Method for updating presence in mobile instant messenger and mobile terminal using the same |
US20100306321A1 (en) * | 2009-05-29 | 2010-12-02 | Microsoft Corporation | Delivering messages using user-defined agents |
TWI409692B (en) * | 2009-10-29 | 2013-09-21 | Mitac Int Corp | Method of simultaneously displaying states of a plurality of internet communication software of a plurality of contacts in address books of and related communication device |
CN102404250B (en) * | 2011-12-13 | 2015-05-27 | 华为技术有限公司 | Method, device and system for transmitting files to users of instant message system |
CN102546464B (en) * | 2011-12-22 | 2015-09-09 | 华为技术有限公司 | A kind of conference method across IM system and system |
US9572020B2 (en) * | 2013-09-19 | 2017-02-14 | Honeywell International Inc. | Apparatus and method supporting wireless communications between devices using different application protocols in industrial control and automation systems |
AU2015250982A1 (en) * | 2014-04-24 | 2016-11-03 | Barclays Bank Plc | Instant messaging systems and methods |
CN108848019A (en) * | 2018-05-04 | 2018-11-20 | 毛勇 | A kind of instant communication method and system |
Citations (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5497373A (en) | 1994-03-22 | 1996-03-05 | Ericsson Messaging Systems Inc. | Multi-media interface |
US20020087704A1 (en) * | 2000-11-30 | 2002-07-04 | Pascal Chesnais | Systems and methods for routing messages to communications devices over a communications network |
US20020118809A1 (en) * | 2000-12-01 | 2002-08-29 | Alfred Eisenberg | Initiation and support of video conferencing using instant messaging |
US6463078B1 (en) | 1998-07-22 | 2002-10-08 | Microsoft Corporation | Method for switching protocols transparently in multi-user applications |
US20020163934A1 (en) * | 2001-04-30 | 2002-11-07 | Moore Todd A. | Apparatus and method for network analysis |
US6535486B1 (en) | 1998-03-20 | 2003-03-18 | 3Com Corporation | Method and apparatus for adaptive prioritization of multiple information types in highly congested communication devices |
US20030054810A1 (en) | 2000-11-15 | 2003-03-20 | Chen Yih-Farn Robin | Enterprise mobile server platform |
US6549937B1 (en) * | 1999-07-21 | 2003-04-15 | Microsoft Corporation | System and method for multi-protocol communication in a computer network |
US6629163B1 (en) | 1999-12-29 | 2003-09-30 | Implicit Networks, Inc. | Method and system for demultiplexing a first sequence of packet components to identify specific components wherein subsequent components are processed without re-identifying components |
US20040015723A1 (en) * | 2002-07-22 | 2004-01-22 | Duc Pham | Secure network file access controller implementing access control and auditing |
US6738822B2 (en) | 1997-09-30 | 2004-05-18 | Canon Kabushiki Kaisha | Relay apparatus, system and method, and storage medium |
Family Cites Families (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
IL119364A (en) | 1996-10-06 | 2000-11-21 | Icq Inc | Communications system |
US6564261B1 (en) | 1999-05-10 | 2003-05-13 | Telefonaktiebolaget Lm Ericsson (Publ) | Distributed system to intelligently establish sessions between anonymous users over various networks |
US20040193722A1 (en) | 1999-08-30 | 2004-09-30 | Donovan Kevin Remington Joseph Bartholomew | Universal instant messaging system for the internet |
US6714793B1 (en) | 2000-03-06 | 2004-03-30 | America Online, Inc. | Method and system for instant messaging across cellular networks and a public data network |
US6760580B2 (en) | 2000-03-06 | 2004-07-06 | America Online, Incorporated | Facilitating instant messaging outside of user-defined buddy group in a wireless and non-wireless environment |
US6430602B1 (en) | 2000-08-22 | 2002-08-06 | Active Buddy, Inc. | Method and system for interactively responding to instant messaging requests |
US7016978B2 (en) | 2002-04-29 | 2006-03-21 | Bellsouth Intellectual Property Corporation | Instant messaging architecture and system for interoperability and presence management |
AU2003272486A1 (en) | 2002-09-17 | 2004-04-08 | Bellsouth Intellectual Property Corporation | Client-based message protocol translation |
US7035942B2 (en) | 2002-09-17 | 2006-04-25 | Bellsouth Intellectual Property Corp. | Server-based message protocol translation |
US6976092B1 (en) | 2002-09-17 | 2005-12-13 | Bellsouth Intellectual Property Corp. | System that using transport protocol objects located at agent location to generate session ID and to provide translation between different instant messaging protocols |
WO2004027559A2 (en) | 2002-09-17 | 2004-04-01 | Bellsouth Intellectual Property Corporation | Message client with multiple message system consolidation |
-
2003
- 2003-09-15 AU AU2003272486A patent/AU2003272486A1/en not_active Abandoned
- 2003-09-15 WO PCT/US2003/029225 patent/WO2004027561A2/en not_active Application Discontinuation
-
2005
- 2005-08-23 US US11/210,187 patent/US7444429B2/en not_active Expired - Lifetime
-
2008
- 2008-09-19 US US12/284,273 patent/US7849220B2/en not_active Expired - Lifetime
- 2008-09-24 US US12/286,136 patent/USRE41848E1/en not_active Expired - Lifetime
Patent Citations (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5497373A (en) | 1994-03-22 | 1996-03-05 | Ericsson Messaging Systems Inc. | Multi-media interface |
US6738822B2 (en) | 1997-09-30 | 2004-05-18 | Canon Kabushiki Kaisha | Relay apparatus, system and method, and storage medium |
US6535486B1 (en) | 1998-03-20 | 2003-03-18 | 3Com Corporation | Method and apparatus for adaptive prioritization of multiple information types in highly congested communication devices |
US6463078B1 (en) | 1998-07-22 | 2002-10-08 | Microsoft Corporation | Method for switching protocols transparently in multi-user applications |
US6549937B1 (en) * | 1999-07-21 | 2003-04-15 | Microsoft Corporation | System and method for multi-protocol communication in a computer network |
US6629163B1 (en) | 1999-12-29 | 2003-09-30 | Implicit Networks, Inc. | Method and system for demultiplexing a first sequence of packet components to identify specific components wherein subsequent components are processed without re-identifying components |
US20030054810A1 (en) | 2000-11-15 | 2003-03-20 | Chen Yih-Farn Robin | Enterprise mobile server platform |
US20020087704A1 (en) * | 2000-11-30 | 2002-07-04 | Pascal Chesnais | Systems and methods for routing messages to communications devices over a communications network |
US20020118809A1 (en) * | 2000-12-01 | 2002-08-29 | Alfred Eisenberg | Initiation and support of video conferencing using instant messaging |
US20020163934A1 (en) * | 2001-04-30 | 2002-11-07 | Moore Todd A. | Apparatus and method for network analysis |
US20040015723A1 (en) * | 2002-07-22 | 2004-01-22 | Duc Pham | Secure network file access controller implementing access control and auditing |
Non-Patent Citations (18)
Title |
---|
A Model for Presence and Instant Messaging Day et al., Feb. 2000. |
Common Presence and Instant Messaging (CPIM) Crocker et al.; Aug. 14, 2002. |
Common Presence and Instant Messaging (CPIM) Presence Information Data Format Sugano et al.; May 2002. |
Common Presence and Instant Messaging: Message Format Atkins et al., Feb. 20, 2002. |
Common Presence and Instant Messaging: Message Format Atkins et al.; Feb. 20, 2002. |
Daniell, et al., patent application entitled "Message Client with Multiple Message System Consolidation," filed Oct. 18, 2002 (s.n. 10/274,405), 51 pages (combined spec. and figures). |
Daniell, et al., patent application entitled "Server-Based Message Protocol Translation," filed Oct. 18, 2002, (s.n. 10/274,478), 52 pages (combined spec. and figures). |
Extensible Markup Language (XML) 1.0 (Second Edition) W3C XML Core Working Group (WG); Oct. 6, 2000. |
http://download.com.com./3000-2150-10148311.html?tag=1st-0-1, entitled: C/Net Download.com; Trillian 0.74 popular, printed Mar. 2, 2004, pp. 2. |
http://www.ceruleanstudios.com/, entitled: Trillian-Communicate with Flexibility and Style, printed Mar. 2, 2004, p. 15. |
http://www.malvino.com/ep/startup.htm, entitled: Startup Programs, printed Mar. 2, 2004, pp. 7. |
Instant Messaging/Presence Protocol Requirements Day et al.; Feb. 2000. |
J.D. Ramsdell, The MITRE Corporation, entitled: Simple Instant Messaging and Presence 1.3 Protocol, dated Jun. 2001, p. 19. |
PCT International Search Report-Int'l Appl. No. PCT/US03/29226, mailed May 5, 2004, p. 6. |
PCT International Search Report-Int'l Appl. No.: PCT.US03/29225, mailed Jun. 21, 2004, p. 6. |
PCT International Search Report-Int'l Appl. No.: PCT/US03/29066, mailed May 11, 2004, p. 7. |
Peter Saint-Andre, "Jabber FAQ" May 13, 2001, jabber.org, pp. 1-36. * |
Peter Saint-Andre, "XML Messaging With Jabber" Oct. 6, 2000, O'Reilly Media, Inc. pp. 1-3. * |
Cited By (48)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US11693875B2 (en) | 2014-11-24 | 2023-07-04 | Asana, Inc. | Client side system and method for search backed calendar user interface |
US11561996B2 (en) | 2014-11-24 | 2023-01-24 | Asana, Inc. | Continuously scrollable calendar user interface |
US11775745B2 (en) | 2017-07-11 | 2023-10-03 | Asana, Inc. | Database model which provides management of custom fields and methods and apparatus therfore |
US10977434B2 (en) | 2017-07-11 | 2021-04-13 | Asana, Inc. | Database model which provides management of custom fields and methods and apparatus therfor |
US11610053B2 (en) | 2017-07-11 | 2023-03-21 | Asana, Inc. | Database model which provides management of custom fields and methods and apparatus therfor |
US11398998B2 (en) | 2018-02-28 | 2022-07-26 | Asana, Inc. | Systems and methods for generating tasks based on chat sessions between users of a collaboration environment |
US11695719B2 (en) | 2018-02-28 | 2023-07-04 | Asana, Inc. | Systems and methods for generating tasks based on chat sessions between users of a collaboration environment |
US11956193B2 (en) | 2018-02-28 | 2024-04-09 | Asana, Inc. | Systems and methods for generating tasks based on chat sessions between users of a collaboration environment |
US11082381B2 (en) | 2018-02-28 | 2021-08-03 | Asana, Inc. | Systems and methods for generating tasks based on chat sessions between users of a collaboration environment |
US10623359B1 (en) | 2018-02-28 | 2020-04-14 | Asana, Inc. | Systems and methods for generating tasks based on chat sessions between users of a collaboration environment |
US11720378B2 (en) | 2018-04-02 | 2023-08-08 | Asana, Inc. | Systems and methods to facilitate task-specific workspaces for a collaboration work management platform |
US11327645B2 (en) | 2018-04-04 | 2022-05-10 | Asana, Inc. | Systems and methods for preloading an amount of content based on user scrolling |
US11656754B2 (en) | 2018-04-04 | 2023-05-23 | Asana, Inc. | Systems and methods for preloading an amount of content based on user scrolling |
US11831457B2 (en) | 2018-06-08 | 2023-11-28 | Asana, Inc. | Systems and methods for providing a collaboration work management platform that facilitates differentiation between users in an overarching group and one or more subsets of individual users |
US11632260B2 (en) | 2018-06-08 | 2023-04-18 | Asana, Inc. | Systems and methods for providing a collaboration work management platform that facilitates differentiation between users in an overarching group and one or more subsets of individual users |
US11943179B2 (en) | 2018-10-17 | 2024-03-26 | Asana, Inc. | Systems and methods for generating and presenting graphical user interfaces |
US10616151B1 (en) * | 2018-10-17 | 2020-04-07 | Asana, Inc. | Systems and methods for generating and presenting graphical user interfaces |
US11652762B2 (en) | 2018-10-17 | 2023-05-16 | Asana, Inc. | Systems and methods for generating and presenting graphical user interfaces |
US11212242B2 (en) * | 2018-10-17 | 2021-12-28 | Asana, Inc. | Systems and methods for generating and presenting graphical user interfaces |
US11341444B2 (en) | 2018-12-06 | 2022-05-24 | Asana, Inc. | Systems and methods for generating prioritization models and predicting workflow prioritizations |
US11694140B2 (en) | 2018-12-06 | 2023-07-04 | Asana, Inc. | Systems and methods for generating prioritization models and predicting workflow prioritizations |
US11620615B2 (en) | 2018-12-18 | 2023-04-04 | Asana, Inc. | Systems and methods for providing a dashboard for a collaboration work management platform |
US11810074B2 (en) | 2018-12-18 | 2023-11-07 | Asana, Inc. | Systems and methods for providing a dashboard for a collaboration work management platform |
US11288081B2 (en) | 2019-01-08 | 2022-03-29 | Asana, Inc. | Systems and methods for determining and presenting a graphical user interface including template metrics |
US11782737B2 (en) | 2019-01-08 | 2023-10-10 | Asana, Inc. | Systems and methods for determining and presenting a graphical user interface including template metrics |
US11561677B2 (en) | 2019-01-09 | 2023-01-24 | Asana, Inc. | Systems and methods for generating and tracking hardcoded communications in a collaboration management platform |
US11204683B1 (en) | 2019-01-09 | 2021-12-21 | Asana, Inc. | Systems and methods for generating and tracking hardcoded communications in a collaboration management platform |
US11847613B2 (en) | 2020-02-14 | 2023-12-19 | Asana, Inc. | Systems and methods to attribute automated actions within a collaboration environment |
US11763259B1 (en) | 2020-02-20 | 2023-09-19 | Asana, Inc. | Systems and methods to generate units of work in a collaboration environment |
US11900323B1 (en) | 2020-06-29 | 2024-02-13 | Asana, Inc. | Systems and methods to generate units of work within a collaboration environment based on video dictation |
US11636432B2 (en) | 2020-06-29 | 2023-04-25 | Asana, Inc. | Systems and methods to measure and visualize workload for completing individual units of work |
US11720858B2 (en) | 2020-07-21 | 2023-08-08 | Asana, Inc. | Systems and methods to facilitate user engagement with units of work assigned within a collaboration environment |
US11449836B1 (en) | 2020-07-21 | 2022-09-20 | Asana, Inc. | Systems and methods to facilitate user engagement with units of work assigned within a collaboration environment |
US11734625B2 (en) | 2020-08-18 | 2023-08-22 | Asana, Inc. | Systems and methods to characterize units of work based on business objectives |
US11568339B2 (en) | 2020-08-18 | 2023-01-31 | Asana, Inc. | Systems and methods to characterize units of work based on business objectives |
US11769115B1 (en) | 2020-11-23 | 2023-09-26 | Asana, Inc. | Systems and methods to provide measures of user workload when generating units of work based on chat sessions between users of a collaboration environment |
US11902344B2 (en) | 2020-12-02 | 2024-02-13 | Asana, Inc. | Systems and methods to present views of records in chat sessions between users of a collaboration environment |
US11405435B1 (en) | 2020-12-02 | 2022-08-02 | Asana, Inc. | Systems and methods to present views of records in chat sessions between users of a collaboration environment |
US11694162B1 (en) | 2021-04-01 | 2023-07-04 | Asana, Inc. | Systems and methods to recommend templates for project-level graphical user interfaces within a collaboration environment |
US11676107B1 (en) | 2021-04-14 | 2023-06-13 | Asana, Inc. | Systems and methods to facilitate interaction with a collaboration environment based on assignment of project-level roles |
US11553045B1 (en) | 2021-04-29 | 2023-01-10 | Asana, Inc. | Systems and methods to automatically update status of projects within a collaboration environment |
US11803814B1 (en) | 2021-05-07 | 2023-10-31 | Asana, Inc. | Systems and methods to facilitate nesting of portfolios within a collaboration environment |
US11792028B1 (en) | 2021-05-13 | 2023-10-17 | Asana, Inc. | Systems and methods to link meetings with units of work of a collaboration environment |
US11809222B1 (en) | 2021-05-24 | 2023-11-07 | Asana, Inc. | Systems and methods to generate units of work within a collaboration environment based on selection of text |
US11756000B2 (en) | 2021-09-08 | 2023-09-12 | Asana, Inc. | Systems and methods to effectuate sets of automated actions within a collaboration environment including embedded third-party content based on trigger events |
US11635884B1 (en) | 2021-10-11 | 2023-04-25 | Asana, Inc. | Systems and methods to provide personalized graphical user interfaces within a collaboration environment |
US11836681B1 (en) | 2022-02-17 | 2023-12-05 | Asana, Inc. | Systems and methods to generate records within a collaboration environment |
US11863601B1 (en) | 2022-11-18 | 2024-01-02 | Asana, Inc. | Systems and methods to execute branching automation schemes in a collaboration environment |
Also Published As
Publication number | Publication date |
---|---|
US20060013205A1 (en) | 2006-01-19 |
US7444429B2 (en) | 2008-10-28 |
AU2003272486A8 (en) | 2004-04-08 |
WO2004027561A3 (en) | 2004-07-29 |
WO2004027561A2 (en) | 2004-04-01 |
US7849220B2 (en) | 2010-12-07 |
US20090024692A1 (en) | 2009-01-22 |
AU2003272486A1 (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 | |
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 | |
US7035942B2 (en) | Server-based message protocol translation | |
US9619466B2 (en) | Message translations | |
US7818375B2 (en) | Providing advanced instant messaging (IM) notification | |
US6912564B1 (en) | System for instant messaging the sender and recipients of an e-mail message | |
US7844716B2 (en) | Instant messaging architecture and system for interoperability and presence management | |
US7552172B2 (en) | Multi-windowed online application environment | |
US8959164B2 (en) | Tri-state presence indicator | |
US20070100944A1 (en) | Uniform resource identifier decoration to enable connectivity for instant messaging providers serving non-authoritative namespaces | |
EP1365553A1 (en) | Method and device for instant messaging | |
US20030125927A1 (en) | Method and system for translating instant messages | |
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 | |
US9043418B2 (en) | Systems and methods for instant messaging persons referenced in an electronic message | |
WO2004027559A2 (en) | Message client with multiple message system consolidation |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
FEPP | Fee payment procedure |
Free format text: PAYER NUMBER DE-ASSIGNED (ORIGINAL EVENT CODE: RMPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Free format text: PAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
FPAY | Fee payment |
Year of fee payment: 8 |
|
AS | Assignment |
Owner name: BELLSOUTH INTELLECTUAL PROPERTY CORPORATION, DELAW Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:DANIELL, WILLIAM TODD;FRIEDMAN, LEE G.;KENT, LARRY GRAHAM, JR.;AND OTHERS;REEL/FRAME:042445/0346 Effective date: 20021216 Owner name: AT&T BLS INTELLECTUAL PROPERTY, INC., DELAWARE Free format text: CHANGE OF NAME;ASSIGNOR:AT&T INTELLECTUAL PROPERTY, INC.;REEL/FRAME:042512/0871 Effective date: 20070727 Owner name: AT&T INTELLECTUAL PROPERTY, INC., TEXAS Free format text: CHANGE OF NAME;ASSIGNOR:BELLSOUTH INTELLECTUAL PROPERTY CORPORATION;REEL/FRAME:042512/0869 Effective date: 20070427 Owner name: AT&T DELAWARE INTELLECTUAL PROPERTY, INC., DELAWAR Free format text: CHANGE OF NAME;ASSIGNOR:AT&T BLS INTELLECTUAL PROPERTY, INC.;REEL/FRAME:042512/0873 Effective date: 20071101 |
|
FPAY | Fee payment |
Year of fee payment: 12 |
|
AS | Assignment |
Owner name: AT&T INTELLECTUAL PROPERTY I, L.P., GEORGIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:AT&T DELAWARE INTELLECTUAL PROPERTY, INC.;REEL/FRAME:042987/0741 Effective date: 20170421 |
|
AS | Assignment |
Owner name: UBER TECHNOLOGIES, INC., CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:AT&T INTELLECTUAL PROPERTY, LLC;REEL/FRAME:043549/0642 Effective date: 20170112 |
|
AS | Assignment |
Owner name: MORGAN STANLEY SENIOR FUNDING, INC., AS ADMINISTRA Free format text: SECURITY INTEREST;ASSIGNOR:UBER TECHNOLOGIES, INC.;REEL/FRAME:050767/0076 Effective date: 20191017 Owner name: MORGAN STANLEY SENIOR FUNDING, INC., AS ADMINISTRA Free format text: SECURITY INTEREST;ASSIGNOR:UBER TECHNOLOGIES, INC.;REEL/FRAME:050767/0109 Effective date: 20191017 Owner name: MORGAN STANLEY SENIOR FUNDING, INC., AS ADMINISTRATIVE AGENT, MARYLAND Free format text: SECURITY INTEREST;ASSIGNOR:UBER TECHNOLOGIES, INC.;REEL/FRAME:050767/0109 Effective date: 20191017 Owner name: MORGAN STANLEY SENIOR FUNDING, INC., AS ADMINISTRATIVE AGENT, MARYLAND Free format text: SECURITY INTEREST;ASSIGNOR:UBER TECHNOLOGIES, INC.;REEL/FRAME:050767/0076 Effective date: 20191017 |
|
AS | Assignment |
Owner name: CORTLAND CAPITAL MARKET SERVICES LLC, ILLINOIS Free format text: PATENT SECURITY AGREEMENT SUPPLEMENT;ASSIGNOR:UBER TECHNOLOGIES, INC.;REEL/FRAME:050817/0600 Effective date: 20191017 |
|
AS | Assignment |
Owner name: UBER TECHNOLOGIES, INC., CALIFORNIA Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CORTLAND CAPITAL MARKET SERVICES LLC, AS ADMINISTRATIVE AGENT;REEL/FRAME:055547/0404 Effective date: 20210225 |