US20070192426A1 - Extending Functionality of Workflow applications using Instant Messaging (IM) - Google Patents

Extending Functionality of Workflow applications using Instant Messaging (IM) Download PDF

Info

Publication number
US20070192426A1
US20070192426A1 US11/737,205 US73720507A US2007192426A1 US 20070192426 A1 US20070192426 A1 US 20070192426A1 US 73720507 A US73720507 A US 73720507A US 2007192426 A1 US2007192426 A1 US 2007192426A1
Authority
US
United States
Prior art keywords
plug
workflow
im
server
response
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.)
Abandoned
Application number
US11/737,205
Inventor
Brian Daigle
W. Daniell
Joel (Hassan) Davis
Larry Kent
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Uber Technologies Inc
Original Assignee
AT&T Delaware Intellectual Property Inc
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
Priority to US41133602P priority Critical
Priority to US41691602P priority
Priority to US41961302P priority
Priority to US10/274,408 priority patent/US6976092B1/en
Priority to US27440502A priority
Priority to US10/274,478 priority patent/US7035942B2/en
Priority to US42614502P priority
Priority to US42643202P priority
Priority to US42614602P priority
Priority to US42644002P priority
Priority to US42642202P priority
Priority to US10/368,099 priority patent/US7546465B2/en
Priority to US10/408,341 priority patent/US7334043B2/en
Priority to US11/737,205 priority patent/US20070192426A1/en
Application filed by AT&T Delaware Intellectual Property Inc filed Critical AT&T Delaware Intellectual Property Inc
Publication of US20070192426A1 publication Critical patent/US20070192426A1/en
Assigned to AT&T DELAWARE INTELLECTUAL PROPERTY, INC reassignment AT&T DELAWARE INTELLECTUAL PROPERTY, INC CHANGE OF NAME (SEE DOCUMENT FOR DETAILS). Assignors: AT&T BLS INTELLECTUAL PROPERTY, INC. (CHANGED TO), AT&T INTELLECTUAL PROPERTY, INC. (CHANGED TO), BELLSOUTH INTELLECTUAL PROPERTY CORPORATON (CHANGED TO)
Assigned to AT&T INTELLECTUAL PROPERTY I, L.P. reassignment AT&T INTELLECTUAL PROPERTY I, L.P. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: AT&T DELAWARE INTELLECTUAL PROPERTY, INC.
Assigned to UBER TECHNOLOGIES, INC. reassignment UBER TECHNOLOGIES, INC. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: AT&T INTELLECTUAL PROPERTY I, LP
Application status is Abandoned legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00Application independent communication protocol aspects or techniques in packet data networks
    • H04L69/08Protocols for interworking or protocol conversion
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00Administration; Management
    • G06Q10/06Resources, workflows, human or project management, e.g. organising, planning, scheduling or allocating time, human or machine resources; Enterprise planning; Organisational models
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00Administration; Management
    • G06Q10/10Office automation, e.g. computer aided management of electronic mail or groupware; Time management, e.g. calendars, reminders, meetings or time accounting
    • G06Q10/107Computer aided management of electronic mail
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00Arrangements for user-to-user messaging in packet-switching networks, e.g. e-mail or instant messages
    • H04L51/04Real-time or near real-time messaging, e.g. instant messaging [IM]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/04Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks
    • H04L63/0428Network 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
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/04Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks
    • H04L63/0428Network 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
    • H04L63/0457Network 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 wherein the sending and receiving network entities apply dynamic encryption, e.g. stream encryption
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00Arrangements for user-to-user messaging in packet-switching networks, e.g. e-mail or instant messages
    • H04L51/06Message adaptation based on network or terminal capabilities
    • H04L51/066Message adaptation based on network or terminal capabilities with adaptation of format
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00Arrangements for user-to-user messaging in packet-switching networks, e.g. e-mail or instant messages
    • H04L51/34Arrangements for user-to-user messaging in packet-switching networks, e.g. e-mail or instant messages with provisions for tracking the progress of a message

Abstract

Plug-ins for instant messaging (IM) systems are described. By using plug-ins in conjunction with IM systems, the functionality of IM systems may be greatly extended. Specifically, in business applications, such as workflow processes, IM provides a more reliable approach to determining actual delivery of messages.

Description

    CROSS REFERENCE TO RELATED APPLICATIONS
  • This application is a divisional of U.S. application number Ser. No. 10/408,341, filed Apr. 7, 2003, which claims the benefit of U.S. provisional patent application Ser. Nos. 60/411,336, filed Sep. 17, 2002; 60/416,916, filed Oct. 8, 2002; 60/419,613, filed Oct. 17, 2002; 60/426,145, filed Nov. 14, 2002; 60/426,146, filed Nov. 14, 2002; 60/426,422, filed Nov. 14, 2002; 60/426,432, filed Nov. 14, 2002; and 60/426,440, filed Nov. 14, 2002. These provisional patent applications are incorporated herein by reference as if set forth in their entireties.
  • U.S. application Ser. No. 10/408,341, filed Apr. 7, 2003, is a continuation-in-part (CIP) of U.S. patent application Ser. No. 10/274,405, filed Oct. 18, 2002, which claims the benefit of U.S. provisional patent application Ser. No. 60/411,336, filed Sep. 17, 2002, and U.S. provisional patent application Ser. No. 60/419,613, filed on Oct. 17, 2002.
  • U.S. application Ser. No. 10/408,341, filed Apr. 7, 2003, is also a CIP of Ser. No. 10/274,408, filed Oct. 18, 2002, which claims the benefit of U.S. provisional patent application Ser. No. 60/411,336, filed Sep. 17, 2002, and U.S. provisional patent application Ser. No. 60/419,613, filed on Oct. 17, 2002.
  • U.S. application Ser. No. 10/408,341, filed Apr. 7, 2003, is also a CIP of Ser. No. 10/274,478, filed Oct. 18, 2002, which claims the benefit of U.S. provisional patent application Ser. No. 60/411,336, filed Sep. 17, 2002, and U.S. provisional patent application Ser. No. 60/419,613, filed on Oct. 17, 2002.
  • U.S. Application Ser. No. 10/408,341, filed Apr. 7, 2003, is also a CIP of Ser. No. 10/368,099, filed Feb. 18, 2003, which claims the benefit of U.S. provisional patent application Ser. No. 60/419,613, filed Oct. 17, 2002, which is entirely incorporated herein by reference.
  • All of these patent applications are incorporated herein by reference as if set forth in their entireties.
  • FIELD OF INVENTION
  • The present invention relates generally to the Internet and, more particularly, to instant messaging (IM).
  • BACKGROUND
  • Currently, instant messaging (IM) systems permit real-time communications between users. Typically, the real-time communications include text messaging, voice chat, and video conferencing. While the text messaging, voice chat, and video conferencing may be sufficient for certain interactions between users, these modes provide relatively limited functionality for other applications.
  • Thus, a heretofore-unaddressed need exists in the industry to extend the functionality of IM systems.
  • SUMMARY
  • The present disclosure provides systems and methods for extending functionality of instant messaging (IM) systems.
  • Briefly described, in architecture, one embodiment of the system comprises a workflow transport-protocol object (TPO) and an IM server. The workflow TPO is adapted to receive workflow requests from a workflow server and format the workflow requests to generate an IM request data stream. In one embodiment, the workflow TPO is further adapted to convey the IM request data stream to the IM server. The IM server is adapted to receive the conveyed IM request data stream from the workflow TPO and convey the IM request data stream to an IM client.
  • Another embodiment of the system comprises an IM client and a workflow plug-in. The IM client is adapted to receive a workflow request. The workflow plug-in is adapted to process the workflow request.
  • The present disclosure also provides methods for extending functionality of IM systems. In this regard, one embodiment of the method comprises the steps of receiving a workflow request, which is directed to a specified IM address, from a workflow server and formatting the received workflow request to generate an IM data stream.
  • Another embodiment of the method comprises the steps of receiving a workflow request at an IM client, determining if the IM client is registered with a workflow plug-in, and executing the workflow plug-in in response to determining that the IM client is registered with the workflow plug-in.
  • Other systems, methods, features, and advantages will be or become apparent to one with skill in the art upon examination of the following drawings and detailed description. It is intended that all such additional systems, methods, features, and advantages be included within this description.
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • Many aspects of the disclosure can be better understood with reference to the following drawings. The components in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present invention. Moreover, in the drawings, like reference numerals designate corresponding parts throughout the several views.
  • FIG. 1 is a block diagram showing a client-server environment having an instant messaging (IM) client with extended functionality residing on a workstation.
  • FIG. 2 is a block diagram showing components of the workstation of FIG. 1 in greater detail.
  • FIG. 3 is a block diagram showing one embodiment of the IM client of FIG. 1 having extended functionality.
  • FIGS. 4 through 7 are data flow diagrams showing embodiments of methods for extending IM functionality, which may be performed by the systems of FIGS. 3A or 3B.
  • FIG. 8 is a block diagram showing one embodiment of the IM client of FIG. 1 that is specifically configured to incorporate workflow functionality.
  • FIGS. 9 through 17 are data flow diagrams showing embodiments of methods for extending IM functionality, which may be performed by the system of FIG. 8.
  • DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
  • Reference is now made in detail to the description of the embodiments as illustrated in the drawings. While several embodiments are described in connection with these drawings, there is no intent to limit the invention to the embodiment or embodiments disclosed herein. On the contrary, the intent is to cover all alternatives, modifications, and equivalents.
  • FIG. 1 is a block diagram showing a client-server environment having an instant messaging (IM) client 130 with extended functionality. The IM client 130 resides on a workstation 140. As shown in FIG. 1, in one embodiment, the workstation 140 is connected to the Internet 150, which serves as a backbone for communication between the workstation 140 and server-side hardware 160. As is known, the server-side hardware 160 may be connected to the Internet through a digital subscriber line (DSL) service, an integrated services digital network (ISDN) service, an analog dial-up service, Ethernet, T-1, or any other service for transmitting data through a network. Since connections to the Internet 150 are known in the art, further discussion of such connections is omitted here. The workstation 140 may also be connected to the Internet through similar connections. In one embodiment, the server-side hardware 160 is adapted to run an IM server 170 and a plug-in server 180. Thus, in operation, when the user logs in at the IM client 130, a communication pathway is established between the IM client 130 and the IM server 170. The communication pathway permits server-mediated IM sessions or access to other IM server functions by the IM client 130, though server interaction is not necessarily included in all communications for some embodiments.
  • FIG. 2 is a block diagram showing components of the workstation 140 in greater detail. As shown in FIG. 2, one embodiment of the workstation 140 comprises a processor 210, memory 230, which may be volatile memory, nonvolatile memory, or a combination of both, a network interface 250, and a hardware interface 260, which are all interconnected through a local bus 220. The hardware interface 260 is adapted to interface external components, such as a display device 270, to the bus 220. The network interface 250 is adapted to interface the workstation 140 to the Internet 150 through connection 145 as shown in FIG. 1. The embodiment of FIG. 2 shows the IM client 130 loaded in memory 230. Thus, the workstation 140 is adapted to engage in IM communications. It should, however, be appreciated that the workstation 140 may be adapted for additional functions, such as Internet-based game playing or execution of other interactive software (not shown). The memory also includes a listing of installed plug-ins 135 and an operating system 240. In one embodiment, the listing of installed plug-ins 135 is configured as a predefined directory in which the installed plug-ins are stored. Since the IM client 130 provides greater functionality and versatility than a standard web browser, plug-ins for the IM client 130 are preferably stored in a separate listing from the plug-ins for web browsers. In an example embodiment, the IM plug-ins are component object model (COM) objects that are downloadable from the plug-in server 180 (FIG. 1). In this regard, for a Windows™-based system, a plug-in may be a COM object that registers a globally-unique identifier (e.g., a CLSID key that identifies the COM object) in the Windows™ registry under a directory in “HKEY_LOCAL_MACHINE/SOFTWARE/.” The CLSID key identifies the COM object that exports the plug-in interface for use by the IM client 130. Since COM objects and CLSID keys are known to those of skill in the art, further discussion of COM objects and CLSID keys are omitted here. It is, however, sufficient to note that, once the IM client 130 is registered with a particular plug-in, the plug-in may be launched by the IM client 130 to process incoming data associated with the plug-in. Greater details of the operation of the plug-in are discussed below. It should be appreciated that a helper application, which is a separate, free-standing software application, may be used in lieu of a plug-in. Thus, it should be appreciated that the following discussion of plug-ins is also applicable to helper applications, as well as other implementations for providing extended functionality.
  • FIG. 3A is a block diagram showing one embodiment of the IM client 130. FIG. 3A also conceptually illustrates the connection between the IM client 130, the IM server 170, the plug-in server 180, and a database 190. The plug-in server 180 comprises one or more downloadable plug-ins 390, which are adapted to extend the functionality of the IM client 130. The downloadable plug-ins 390 may include data encryption and decryption software, specifically-configured Internet web pages, workflow applications, video games (both interactive and non-interactive), digital audio recorders and players, digital video recorders and players, etc. The IM client 130 comprises a parser 310, plug-in search logic 315, an index of registered plug-ins 320, which is correlated to the plug-ins in the listing of installed plug-ins 135, plug-in download logic 325, plug-in installation logic 330, and plug-in execution logic 335.
  • In an example embodiment, when the IM client 130 is initially launched, plug-in search logic 315 in the IM client 130 searches the predefined plug-in directory 135 to determine which plug-ins are installed in the plug-in directory 135. The installed plug-ins are then registered for subsequent access. Once the IM client 130 is engaged in a server-mediated IM session, the IM client 130 may receive a data stream from the IM server 170. The parser 310 parses the received data stream for an application identifier, which, in some embodiments, is an extensible markup language (XML) tag. In one embodiment, the application identifier may be an XML tag that is correlated to a specific plug-in. For example, the XML tag may identify that the incoming data stream is a digital audio stream, which is to be processed by a digital audio player. Similarly, the XML tag may identify that the incoming data stream is an encrypted data stream, which is to be decrypted by a decryption application. In another embodiment, the application identifier may be a generic tag that has data of a specific multi-purpose Internet mail extension (MIME)-type, which is correlated to a particular application. In that embodiment, the generic tag may be parsed to locate the MIME extension and relate the MIME extension to a specific plug-in.
  • Once the parser 310 has identified the plug-in, the IM client 130 preferably determines whether or not that plug-in has been registered. If that plug-in has been registered, then the plug-in execution logic 335 launches the plug-in 350. In one embodiment, the launching of the plug-in 350 includes a loading of the plug-in into memory 230, initializing the plug-in, and creating a new instance of the plug-in at the IM client 130. In this regard, multiple instances of a plug-in may be loaded by the IM client 130. As shown in this embodiment, the life cycle of the plug-in is determined by the IM client 130. In this regard, when the IM client 130 shuts down, then the plug-in 350 also shuts down. Conversely, if a helper application is launched, then the life cycle of the helper application need not be governed by the IM client 130. Since life cycle management of plug-ins and helper applications is known to those of skill in the art, further discussion of life cycle management is omitted here.
  • If the IM client 130 determines that the plug-in has not been registered, then the plug-in download logic 325 downloads the plug-in 350 from the plug-in server 180, and the plug-in installation logic 330 installs the plug-in 350 at the predefined listing. Upon installing the plug-in 350, the IM client registers the plug-in 350 as described above. The registered plug-in 350 is then launched by the plug-in execution logic 335.
  • FIGS. 4 through 7 are data flow diagrams showing embodiments of methods for extending IM functionality. As shown in FIG. 4, one embodiment of the method begins when an IM client 130 receives (402) an IM data stream. The embodiment of FIG. 4 shows the IM data stream being received from an IM server 170. However, it should be appreciated that, in a peer-to-peer environment, the IM data stream may be directly received from another IM client (not shown). The IM client 130 parses (404) the IM data stream for an application identifier. In some embodiments, the application identifier may be a plug-in tag that specifies a particular plug-in, while, in another embodiment, the application identifier may be a generic tag that includes data of a particular MIME type, which is registered for a particular plug-in. Upon parsing (404) the IM data stream, the IM client 130 determines (406) the particular plug-in that is associated with the application identifier. For example, if the tag indicates that the data is a digital audio stream, then the IM client 130 determines a digital audio player plug-in to be the proper plug-in. Similarly, if the tag indicates that the data is an incoming workflow request, then the IM client 130 determines that a workflow application is the proper plug-in. Upon determining (406) the proper plug-in, the IM client 130 further determines (408) whether or not it is registered with the plug-in. If the IM client 130 is not registered with the plug-in, then the process continues to FIG. 5. Alternatively, if the IM client 130 is registered with the plug-in, then the process continues to FIG. 6.
  • As shown in FIG. 5, if the IM client 130 is not registered with the plug-in, then the IM client 130 issues (502) a request for the plug-in to a plug-in server 180. In one embodiment, the plug-in server 180 may be configured such that all of the plug-ins at the plug-in server 180 are publicly accessible to every IM user who requests a plug-in. In another embodiment, the IM system may be configured so that IM users have different access levels for different plug-ins. For example, a digital audio player plug-in may be accessible to all IM users while a digital video plug-in may only be accessible to specified IM users. In another example, a workflow plug-in may only be accessible to those IM users who are authorized participants designated by a workflow server. Similarly, an interactive game plug-in may only be accessible to those IM users who have subscribed to the interactive game.
  • In the embodiment where different IM users have different access levels, the issued (502) request may include an access code or an electronic certificate indicating an authorized download. Since many different approaches to restricting downloads are known to those of skill in the art, further discussion of authorized downloads is omitted here. Once the request has been issued (502) by the IM client 130, the plug-in server 180 receives (504) the request for the plug-in and determines (506) whether or not the request includes an authorization to download the plug-in. In one embodiment, this may be done by comparing a received access code with a database having a list of approved access codes. Once the plug-in server 180 has determined (506) that the download is authorized, then the plug-in server 180 conveys (508) the appropriate installable plug-in to the IM client 130. The IM client 130 receives (510) the installable plug-in and installs (512) the plug-in. The installed (512) plug-in is then registered (514). In one embodiment, the plug-in is registered as a COM object in the Windows™ registry under a directory in “HKEY_LOCAL_MACHINE/SOFTWARE/.”
  • As shown in FIG. 6, once the proper plug-in has been registered, the IM client 130 launches (602) the plug-in 350 by loading the plug-in 350 into memory, initializing the plug-in 350, and creating an instance of the plug-in 350 at the IM client 130. The IM client 130 then conveys (604) to the plug-in 350 any data that may be delineated by the application identifiers in the received data streams. The plug-in 350 receives (606) the data and executes (608) a function defined by the plug-in with the data to generate a result. For example, if the data is a digital audio stream, then the plug-in may play the digital audio stream. Similarly, if the data is part of an interactive video game, then the plug-in may provide a gaming environment.
  • If the plug-in is part of an interactive software application (e.g., workflow application, interactive video game, Internet-based conferencing, etc.), then the result may be a prompt for feedback from a user at the IM client 130. In this regard, if the plug-in is an interactive program, then the process may continue to FIG. 7, where the plug-in receives (702) input from a user. Upon receiving (702) the input, the plug-in conveys (704) data, which is indicative of the input, to the IM client 130. The IM client 130 receives (706) the data and structures (708) the data so that it may be transmitted using an IM message. The structured data is then conveyed (708) to the IM server 170. Again, while the embodiment of FIGS. 4 through 7 show a server-mediated IM process, it should be appreciated that the described methods are equally applicable in peer-to-peer IM processes.
  • FIG. 8 is a block diagram showing another embodiment of the IM client 130 of FIG. 1. The IM client 130 of FIG. 8 is specifically configured to incorporate workflow functionality. As shown in FIG. 8, one embodiment of the system includes an IM client 130 in communication with an IM server 170 through an IM transport protocol object (TPO) 830. In this regard, the IM TPO 830 is adapted to receive messages from the IM server 170 and convey the received messages to the IM client 130. Similarly, the IM TPO 830 is adapted to receive messages from the IM client 130 and convey the received messages to the IM server 170. Since the behavior of the IM TPO 830 is described in greater detail in the above-referenced applications, further discussion of the IM TPO 830 is omitted here. However, it should be appreciated that the IM TPO 830 is configured so that messages generated by the IM client 130 are reformatted for compatibility with the IM server 170, and vice versa.
  • The system of FIG. 8 also includes a workflow server 810 in communication with the IM server 170 through a workflow TPO 820. The workflow server 810 is adapted to control workflow processes 814 and manage workflow participants 812 that are associated with the various workflow processes 814. In this regard, the workflow server 170 generates workflow requests and receives responses to the requests in accordance with the workflow processes 814. Similar to the IM TPO 830, the workflow TPO 820 provides compatibility between the IM server 170 and the workflow server 810. Since the workflow server 810 may use a protocol that is incompatible with IM, the workflow TPO 820 translates messages generated by the workflow server 810 into IM-compatible messages. Similarly, the workflow TPO 820 translates IM messages generated by the IM server 170 into a protocol that is compatible with the workflow server 810.
  • The system of FIG. 8 further comprises a plug-in server 180 having various downloadable plug-ins 390 including a workflow plug-in 850. The plug-in server 180 is coupled to the IM client 130, thereby permitting the IM client 130 to download appropriate plug-ins from the plug-in server 180. The workflow server 810, the IM server 170, and the plug-in server 180 are coupled to a database 190. The database 190 may include an access code as described with reference to FIG. 5.
  • In operation, the workflow server 810 generates a workflow request identifying a particular workflow participant (e.g., an IM address of a workflow participant). The workflow request is relayed to the workflow TPO 820, which queries the IM server 170 to determine whether or not the workflow participant is present. In other words, for example, the workflow TPO 820 determines whether the IM address of the workflow participant indicates that the workflow participant is online. If the workflow participant is present, then the workflow TPO 820 reformats the workflow request into an IM-compatible message and conveys the IM-compatible message to the IM server 170. The IM server 170 relays the IM-compatible message to the IM TPO 830, which translates the IM-compatible message into a workflow request that is compatible with the IM client 130. The translated workflow request is relayed message to the IM client 130. The IM client 130 receives the translated workflow request and launches a workflow plug-in 850 to process the translated workflow request by, for example, prompting the workflow participant for a response. If the workflow participant responds to the request, then the response is conveyed from the workflow plug-in 850 to the IM client 130. The IM client 130 relays the response to the IM TPO 830, which translates the response into an IM-compatible message. The IM-compatible message is conveyed to the IM server 130, which further relays the IM-compatible message to the workflow TPO 820. The workflow TPO 820 reformats the response into the protocol of the workflow server 810 and conveys that response to the workflow server 810.
  • As seen from the embodiment of FIG. 8, employing an IM system to convey workflow requests and responses results in fewer false-delivery messages. In other words, unlike email-based workflow processes in which only delivery confirmation of the email is generally possible, the IM-based workflow process provides real-time notification as to whether or not the workflow participant received a request by delivering requests to the participant after verifying that the participant is present. Thus, by delivering a workflow request to only those workflow participants who are present, the system of FIG. 8 provides a more accurate and efficient confirmation of delivery than workflow processes that utilize email. Several embodiments of IM-based workflow processes are described with reference to FIGS. 9 through 17.
  • FIGS. 9 through 17 are data flow diagrams showing embodiments of methods for extending IM functionality. As shown in FIG. 9, one embodiment of the process begins when a workflow server 810 generates (902) a workflow request for a selected IM address for a workflow participant. The generated (902) workflow request is conveyed (904) from the workflow server 810 to a workflow TPO 820, which receives (906) the workflow request and queries (908) an IM server 170 to determine whether or not the selected IM address is present on the network. The IM server 170 receives (910) the query and returns (912) a result to the workflow TPO 820. The workflow TPO 820 receives (914) the result and evaluates (916) the result for presence of the selected IM address. If the result indicates that the selected IM address is present on the network, then the process continues to FIG. 11. If, on the other hand, the result indicates that the selected IM address is not present on the network, then the process continues to FIG. 10.
  • As shown in FIG. 10, if the selected IM address is not present, then the workflow TPO 820 generates (1002) a not-present message and conveys (1004) the not-present message to the workflow server 810. The workflow server 810 receives (1006) the not-present message and selects (1008) another IM address related to the workflow participant. Once another IM address has been selected (1008), the process returns to FIG. 9.
  • If the selected IM address is present on the network, then the workflow TPO 820 reformats (1102) and tags the workflow request, as shown in FIG. 11, so that the workflow request is IM compatible. In one embodiment, the workflow request is tagged with an extensible markup language (XML) tag, which indicates that the request is a workflow request. In another embodiment, the workflow request is tagged with a generic XML tag, which indicates that a particular workflow-related message is embedded in the workflow request. In either event, the tagged workflow request is conveyed (1104) to the IM server 170. The IM server 170 receives (1106) the tagged workflow request and relays (1108) the tagged workflow request to an IM TPO 830. The IM TPO 830 receives (1110) the tagged workflow request and translates (1112) the workflow request for an IM client 130. The translated workflow request is relayed (1114) to the IM client 130, which receives (1116) the translated workflow request.
  • The process continues to FIG. 12 where the IM client 130 parses (1202) the translated workflow request for the particular tags (e.g., XML workflow tags). Upon parsing (1202) the workflow request, the IM client 130 determines (1204) from the parsed tags that a workflow plug-in is the appropriate plug-in for processing the received workflow request. Upon determining (1204) that the workflow plug-in is the appropriate plug-in, the IM client 130 further determines (1206) whether or not the IM client 130 is registered with the workflow plug-in. Since the registering of the IM client 130 with plug-ins is described above, further discussion of registering IM clients is omitted here.
  • If the IM client 130 determines (1206) that the IM client 130 is registered with the workflow plug-in, then the process continues to FIG. 14. However, if the IM client 130 determines that the IM client 130 is not registered with the workflow plug-in, then the process continues to FIG. 13.
  • As shown in FIG. 13, if the IM client 130 is not registered with the workflow plug-in, the IM client 130 issues (1302) a request to a plug-in server 180 for the workflow plug-in. In one embodiment, the system may be configured so that only authorized users or participants may retrieve the workflow plug-in. In another embodiment, the workflow plug-in may be accessible to all users that request the workflow plug-in. If only authorized participants are permitted access to the workflow plug-in, then the plug-in server 180 receives (1304) the request and determines (1306) whether or not the request includes authorization to retrieve (or download) the workflow plug-in. If it is determined (1306) that the download is authorized, then the plug-in server 180 conveys (1308) the workflow plug-in to the IM client 130. The IM client 130 receives (1310) the workflow plug-in, installs (1312) the workflow plug-in, and registers (1314) the IM client 130 with the installed workflow plug-in.
  • As shown in FIG. 14, when the IM client 130 is registered with the workflow plug-in, the IM client 130 creates (1402) an instance of the workflow plug-in 850. Upon creating (1402) the instance of the workflow plug-in 850, the IM client conveys (1404) data that is delineated by the tags in the workflow request to the workflow plug-in 850. The workflow plug-in receives (1406) the data and processes the data. In one embodiment, the processing of the data includes the step of prompting (1408) a user for a response to the received data.
  • If a user is prompted (1408) for a response and the user provides a response, then the process continues to FIG. 15 where the workflow plug-in 850 receives (1502) the workflow response from the user and conveys (1504) the workflow response to the IM client 130. The IM client receives (1506) the workflow response and relays (1508) the workflow response to the IM TPO 830. The IM TPO 830 receives (1510) the workflow response and the process continues to FIG. 16.
  • As shown in FIG. 16, the IM TPO 830, upon receiving (1510) the workflow response from the IM client 130, translates (1602) the workflow response into an IM-compatible workflow response. The translated workflow response is conveyed (1604) to the IM server 170. The IM server 170 receives (1606) the translated workflow response and relays (1608) the translated workflow response to the workflow TPO 820. The workflow TPO 820 receives (1610) the translated workflow response and reformats (1612) the translated workflow response into the protocol of the workflow server 810.
  • The process continues to FIG. 17 where the workflow TPO 820 conveys (1702) the reformatted workflow response to the workflow server 810. The workflow server 810 receives (1704) the reformatted workflow response and determines (1706) whether or not additional workflow processes should be executed. If it is determined (1706) that additional workflow processes should be executed, then the process returns to FIG. 9. If, on the other hand, it is determined that no additional workflow processes are to be executed, then the process ends.
  • As shown with reference to FIGS. 9 through 17, by employing IM to convey workflow messages, the presence aspect of IM may be used to more accurately confirm delivery of workflow requests. Additionally, by employing IM, which is substantially a real-time mode of communication, workflow processes may be accelerated. In other words, unlike prior systems employing email in which a reply may be significantly delayed, the IM-based workflow process is a more streamlined process.
  • The IM client 130, the parser 310, the plug-in search logic 315, the plug-in download logic 325, the plug-in installation logic 330, the plug-in execution logic 335, the plug-in 350, the workflow plug-in 850, and the downloadable plug-ins 390 of the present invention can be implemented in hardware, software, firmware, or a combination thereof. In the preferred embodiment(s), the IM client 130, the parser 310, the plug-in search logic 315, the plug-in download logic 325, the plug-in installation logic 330, the plug-in execution logic 335, the plug-in 350, the workflow plug-in 850, and the downloadable plug-ins 390 are implemented in software or firmware that is stored in a memory and that is executed by a suitable instruction execution system. If implemented in hardware, as in an alternative embodiment, the IM client 130, the parser 310, the plug-in search logic 315, the plug-in download logic 325, the plug-in installation logic 330, the plug-in execution logic 335, the plug-in 350, the workflow plug-in 850, and the downloadable plug-ins 390 can be implemented with any or a combination of the following technologies, which are all well known in the art: 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.
  • Any process descriptions or blocks in flow charts should be understood as representing modules, segments, or portions of code which include one or more executable instructions for implementing specific logical functions or steps in the process, and alternate implementations are included within the scope of the preferred embodiment of the present invention in which functions may be executed out of order from that shown or discussed, including substantially concurrently or in reverse order, depending on the functionality involved, as would be understood by those reasonably skilled in the art of the present invention.
  • The processes of FIGS. 4 through 7 and FIGS. 9 through 17 may be executed by computer code comprising an ordered listing of executable instructions for implementing logical functions. In this regard, the computer code may 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. In the context of this document, 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. More specific examples (a nonexhaustive list) of 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). Note that 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.
  • Although exemplary embodiments have been shown and described, it will be clear to those of ordinary skill in the art that a number of changes, modifications, or alterations may be made, none of which depart from the spirit of the present invention. For example, while the preferred embodiments illustrate plug-ins that are created and destroyed by the IM client, it should be appreciated that IM functionality may be extended by using helper applications that are executed as separate, free-standing applications. Additionally, while a specific embodiment of a workflow plug-in is shown with reference to FIGS. 8 through 17, it should be appreciated that a video game plug-in, an audio plug-in, a video plug-in, or any number of other applications may be implemented using the systems and processes described above. Specifically, it should be appreciated that the embodiments described above are particularly conducive to interactive applications such as interactive video games or interactive business applications. In this regard, it should be appreciated that the above-described approaches may be extended to any application that is amenable to interaction by multiple users.
  • All such changes, modifications, and alterations should therefore be seen as within the scope of the present invention.

Claims (20)

1. A communication method comprising:
receiving a workflow request at an instant messaging (IM) client;
determining if the IM client is registered with a workflow plug-in in response to receiving the workflow request; and
executing the workflow plug-in in response to determining that the IM client is registered with the workflow plug-in.
2. The method of claim 1, further comprising:
receiving an input at the IM client, the input being indicative of a response to the workflow request;
generating a workflow response from the received input; and
conveying the workflow response.
3. The method of claim 1, further comprising downloading a workflow plug-in from a plug-in server in response to determining that the IM client is not registered with the workflow plug-in.
4. The method of claim 3, further comprising storing the downloaded workflow plug-in.
5. The method of claim 3, further comprising registering the IM client with the downloaded workflow plug-in.
6. The method of claim 3, wherein downloading the workflow plug-in comprises providing authentication information to the plug-in server for authentication by the plug-in server.
7. The method of claim 6, further comprising receiving the workflow plug-in from the plug-in server in response to the plug-in server authenticating the authentication information.
8. A communication system comprising:
a first receiving component configured to receive a workflow request at an instant messaging (IM) client;
a determining component configured to determine if the IM client is registered with a workflow plug-in in response to receiving the workflow request; and
an executing component configured to execute the workflow plug-in in response to determining that the IM client is registered with the workflow plug-in.
9. The system of claim 8, further comprising:
a second receiving component configured to receive an input at the IM client, the input being indicative of a response to the workflow request;
a generating component configured to generate a workflow response from the received input; and
a conveying component configured to convey the workflow response.
10. The system of claim 8, further comprising a downloading component configured to download a workflow plug-in from a plug-in server in response to determining that the IM client is not registered with the workflow plug-in.
11. The system of claim 10, further comprising a storing component configured to store the downloaded workflow plug-in.
12. The system of claim 10, further comprising a registering component configured to register the IM client with the downloaded workflow plug-in.
13. The system of claim 10, wherein the downloading component is further configured to provide authentication information to the plug-in server for authentication by the plug-in server.
14. The method of claim 13, further comprising a third receiving component configured to receive the workflow plug-in from the plug-in server in response to the plug-in server authenticating the authentication information.
15. A computer readable storage medium for facilitating communications, comprising:
first receiving logic configured to receive a workflow request at an instant messaging (IM) client;
determining logic configured to determine if the IM client is registered with a workflow plug-in in response to receiving the workflow request; and
executing logic configured to execute the workflow plug-in in response to determining that the IM client is registered with the workflow plug-in.
16. The computer readable storage medium of claim 15, further comprising:
second receiving logic configured to receive an input at the IM client, the input being indicative of a response to the workflow request;
generating logic configured to generate a workflow response from the received input; and
conveying logic configured to convey the workflow response.
17. The computer readable storage medium of claim 15, further comprising downloading logic configured to download a workflow plug-in from a plug-in server in response to determining that the IM client is not registered with the workflow plug-in.
18. The computer readable storage medium of claim 17, further comprising storing logic configured to store the downloaded workflow plug-in.
19. The computer readable storage medium of claim 17, further comprising registering logic configured to register the IM client with the downloaded workflow plug-in.
20. The computer readable storage medium of claim 15, further comprising:
providing logic configured to provide authentication information to the plug-in server for authentication by the plug-in server; and
a third receiving component configured to receive the workflow plug-in from the plug-in server in response to the plug-in server authenticating the authentication information.
US11/737,205 2002-09-17 2007-04-19 Extending Functionality of Workflow applications using Instant Messaging (IM) Abandoned US20070192426A1 (en)

Priority Applications (14)

Application Number Priority Date Filing Date Title
US41133602P true 2002-09-17 2002-09-17
US41691602P true 2002-10-08 2002-10-08
US41961302P true 2002-10-17 2002-10-17
US27440502A true 2002-10-18 2002-10-18
US10/274,478 US7035942B2 (en) 2002-09-17 2002-10-18 Server-based message protocol translation
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
US42614502P true 2002-11-14 2002-11-14
US42643202P true 2002-11-14 2002-11-14
US42614602P true 2002-11-14 2002-11-14
US42644002P true 2002-11-14 2002-11-14
US42642202P true 2002-11-14 2002-11-14
US10/368,099 US7546465B2 (en) 2002-10-17 2003-02-18 Instant messaging private tags
US10/408,341 US7334043B2 (en) 2002-09-17 2003-04-07 Extending functionality of workflow applications using instant messaging (IM)
US11/737,205 US20070192426A1 (en) 2002-09-17 2007-04-19 Extending Functionality of Workflow applications using Instant Messaging (IM)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
US11/737,205 US20070192426A1 (en) 2002-09-17 2007-04-19 Extending Functionality of Workflow applications using Instant Messaging (IM)

Related Parent Applications (2)

Application Number Title Priority Date Filing Date
US27440502A Continuation-In-Part 2002-10-18 2002-10-18
US10/408,341 Division US7334043B2 (en) 2002-09-17 2003-04-07 Extending functionality of workflow applications using instant messaging (IM)

Publications (1)

Publication Number Publication Date
US20070192426A1 true US20070192426A1 (en) 2007-08-16

Family

ID=38335288

Family Applications (4)

Application Number Title Priority Date Filing Date
US10/408,341 Expired - Fee Related US7334043B2 (en) 2002-09-17 2003-04-07 Extending functionality of workflow applications using instant messaging (IM)
US11/737,205 Abandoned US20070192426A1 (en) 2002-09-17 2007-04-19 Extending Functionality of Workflow applications using Instant Messaging (IM)
US11/737,212 Abandoned US20070185965A1 (en) 2002-09-17 2007-04-19 Extending Functionality of Workflow applications using Instant Messaging (IM)
US11/961,267 Active 2024-07-02 US7945690B2 (en) 2002-09-17 2007-12-20 Extending functionality of workflow applications using instant messaging (IM)

Family Applications Before (1)

Application Number Title Priority Date Filing Date
US10/408,341 Expired - Fee Related US7334043B2 (en) 2002-09-17 2003-04-07 Extending functionality of workflow applications using instant messaging (IM)

Family Applications After (2)

Application Number Title Priority Date Filing Date
US11/737,212 Abandoned US20070185965A1 (en) 2002-09-17 2007-04-19 Extending Functionality of Workflow applications using Instant Messaging (IM)
US11/961,267 Active 2024-07-02 US7945690B2 (en) 2002-09-17 2007-12-20 Extending functionality of workflow applications using instant messaging (IM)

Country Status (1)

Country Link
US (4) US7334043B2 (en)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070005711A1 (en) * 2005-07-01 2007-01-04 Imiogic, Inc. System and method for building instant messaging applications
US20080161956A1 (en) * 2003-01-14 2008-07-03 Yamaha Corporation Musical content utilizing apparatus
US20100303873A1 (en) * 2007-12-07 2010-12-02 Estelle Marie Piron Biodegradable single-phase cohesive hydrogels
US20110016184A1 (en) * 2009-07-17 2011-01-20 Alibaba Group Holding Limited Downloading a plug-in on an instant messaging client

Families Citing this family (36)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8028023B2 (en) * 2002-09-17 2011-09-27 At&T Intellecutal Property I, L.P. Extending functionality of instant messaging (IM) systems
US7334043B2 (en) * 2002-09-17 2008-02-19 At&T Delaware Intellectual Property, Inc. Extending functionality of workflow applications using instant messaging (IM)
US7310659B1 (en) * 2003-06-27 2007-12-18 Sprint Communications Company L.P. Interface and method for extending a target application over an instant message link of a communication network
US20050210396A1 (en) * 2003-10-06 2005-09-22 Galli Marcio D S System and method for seamlessly bringing external services into instant messaging sessions and into users' authoring environment
US7870199B2 (en) * 2003-10-06 2011-01-11 Aol Inc. System and method for seamlessly bringing external services into instant messaging session
US7624149B2 (en) * 2004-09-15 2009-11-24 Microsoft Corporation Instant messaging with audio
US7587596B2 (en) * 2005-02-24 2009-09-08 International Business Machines Corporation Method and apparatus for updating information stored in multiple information handling systems
US20060190557A1 (en) * 2005-02-24 2006-08-24 Ibm Corporation Method and apparatus for forwarding user information among multiple information handling systems
US20060190547A1 (en) * 2005-02-24 2006-08-24 Ibm Corporation Method and apparatus for restricting instant messaging during a scheduled event
US20070162318A1 (en) * 2005-11-08 2007-07-12 Kaulkin Information Systems, Llc System And Method For Managing Business Processes
JP2007150846A (en) * 2005-11-29 2007-06-14 Toshiba Corp Contents reproducing system
EP2084921B1 (en) * 2006-10-19 2018-12-12 JMango IPR Holding Limited An interactive system and process
US9191793B2 (en) 2007-10-19 2015-11-17 Duc Anh Ngo Interactive system and process
US8943189B2 (en) * 2007-05-18 2015-01-27 Microsoft Corporation Standard based detection and launch of client applications
US8926435B2 (en) 2008-12-15 2015-01-06 Sony Computer Entertainment America Llc Dual-mode program execution
US8613673B2 (en) 2008-12-15 2013-12-24 Sony Computer Entertainment America Llc Intelligent game loading
US7984100B1 (en) 2008-04-16 2011-07-19 United Services Automobile Association (Usaa) Email system automatically notifying sender status and routing information during delivery
CA2669462C (en) * 2008-06-17 2014-03-18 Arquest, Inc. Hybrid stretch ear and absorbent article including the same
US8935633B2 (en) * 2008-12-10 2015-01-13 International Business Machines Corporation Providing controlled access to the use of electronic devices
US20100146499A1 (en) * 2008-12-10 2010-06-10 International Business Machines Corporation Controlling Access to Electronic Devices by Meeting Invitees
CN103442774B (en) 2010-09-13 2016-08-10 索尼电脑娱乐美国公司 Double mode program performs and loads
CN101771995B (en) 2008-12-31 2013-02-27 华为技术有限公司 Service roaming method, device and system
CN101604371B (en) 2009-07-22 2012-02-08 阿里巴巴集团控股有限公司 Control method and system plug-in privileges
US8589992B2 (en) 2010-05-27 2013-11-19 Istreamplanet Co. Video workflow automation platform for publishing a video feed in multiple formats
US8918820B2 (en) * 2010-05-27 2014-12-23 Istreamplanet Co. Video workflow automation platform
US8560331B1 (en) 2010-08-02 2013-10-15 Sony Computer Entertainment America Llc Audio acceleration
WO2012037165A2 (en) * 2010-09-13 2012-03-22 Gaikai, Inc. Add-on management
EP2780817A4 (en) * 2011-11-15 2015-03-04 Trimble Navigation Ltd Efficient distribution of functional extensions to a 3d modeling software
WO2013074547A1 (en) 2011-11-15 2013-05-23 Trimble Navigation Limited Extensible web-based 3d modeling
US9715325B1 (en) * 2012-06-21 2017-07-25 Open Text Corporation Activity stream based interaction
US9692675B1 (en) 2012-06-21 2017-06-27 Open Text Corporation Activity stream based collaboration
US8910265B2 (en) * 2012-09-28 2014-12-09 Sonos, Inc. Assisted registration of audio sources
CN102999339A (en) * 2012-11-22 2013-03-27 用友软件股份有限公司 COM (component object model) component calling device and COM component calling method
CN103023999B (en) * 2012-11-30 2015-12-02 北京奇虎科技有限公司 A kind of method, server and corresponding system issuing browser component
CA2946067A1 (en) * 2014-04-24 2015-10-29 Barclays Bank Plc Instant messaging systems and methods
US10447621B2 (en) * 2014-09-04 2019-10-15 Microsoft Technology Licensing, Llc App powered extensibility of messages on an existing messaging service

Citations (26)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5754857A (en) * 1995-12-08 1998-05-19 Sun Microsystems, Inc. Distributed asynchronous workflow on the net
US5758069A (en) * 1996-03-15 1998-05-26 Novell, Inc. Electronic licensing system
US5903728A (en) * 1997-05-05 1999-05-11 Microsoft Corporation Plug-in control including an independent plug-in process
US5903632A (en) * 1997-03-19 1999-05-11 Tmax Technologies Inc. Automated telephone directory
US6049796A (en) * 1997-02-24 2000-04-11 Nokia Mobile Phones Limited Personal digital assistant with real time search capability
US6091808A (en) * 1996-10-17 2000-07-18 Nortel Networks Corporation Methods of and apparatus for providing telephone call control and information
US6196920B1 (en) * 1998-03-31 2001-03-06 Masque Publishing, Inc. On-line game playing with advertising
US6216152B1 (en) * 1997-10-27 2001-04-10 Sun Microsystems, Inc. Method and apparatus for providing plug in media decoders
US6347398B1 (en) * 1996-12-12 2002-02-12 Microsoft Corporation Automatic software downloading from a computer network
US20020101448A1 (en) * 2000-11-29 2002-08-01 Sanderson Richard A. Generating a declarative user interface
US20020159574A1 (en) * 2001-04-27 2002-10-31 Scott Stogel Automatic telephone directory apparatus and method of operation thereof
US20030023679A1 (en) * 2001-03-13 2003-01-30 Stephen Johnson System and process for network collaboration through embedded annotation and rendering instructions
US6651084B1 (en) * 1999-11-29 2003-11-18 International Business Machines Corporation System and method for adding plug-ins to a web browser
US20030233417A1 (en) * 2002-06-17 2003-12-18 Siemens Information And Communication Networks, In System and method for signaling using instant messaging in multimedia telephony-over-lan conferences
US6766305B1 (en) * 1999-03-12 2004-07-20 Curl Corporation Licensing system and method for freely distributed information
US6785708B1 (en) * 1996-10-30 2004-08-31 Avaya Inc. Method and apparatus for synchronizing browse and chat functions on a computer network
US20040221261A1 (en) * 2002-05-01 2004-11-04 Mike Blevins Collaborative business plug-in framework
US6853634B1 (en) * 1999-12-14 2005-02-08 Nortel Networks Limited Anonymity in a presence management system
US6857124B1 (en) * 1999-01-11 2005-02-15 Eolas Technologies, Inc. Method and system for hypermedia browser API simulation to enable use of browser plug-ins and applets as embedded widgets in script-language-based interactive programs
US6988249B1 (en) * 1999-10-01 2006-01-17 Accenture Llp Presentation service architectures for netcentric computing systems
US7051071B2 (en) * 2000-02-16 2006-05-23 Bea Systems, Inc. Workflow integration system for enterprise wide electronic collaboration
US7120455B1 (en) * 2004-05-20 2006-10-10 Cellco Partnership Method and system for mobile instant messaging using multiple interfaces
US7131003B2 (en) * 2003-02-20 2006-10-31 America Online, Inc. Secure instant messaging system
US7133900B1 (en) * 2001-07-06 2006-11-07 Yahoo! Inc. Sharing and implementing instant messaging environments
US7275215B2 (en) * 2002-07-29 2007-09-25 Cerulean Studios, Llc System and method for managing contacts in an instant messaging environment
US7334043B2 (en) * 2002-09-17 2008-02-19 At&T Delaware Intellectual Property, Inc. Extending functionality of workflow applications using instant messaging (IM)

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5960404A (en) * 1997-08-28 1999-09-28 International Business Machines Corp. Mechanism for heterogeneous, peer-to-peer, and disconnected workflow operation
US7188072B2 (en) * 2000-06-13 2007-03-06 Intergraph Software Technologies Company Systems and methods for the collaborative design, construction, and maintenance of fluid processing plants
US6857125B2 (en) * 2001-12-10 2005-02-15 Akros Limited Contact member to optical disk, protecting film for optical disk and coating composition
EP1502218A4 (en) * 2002-04-15 2005-08-17 Invensys Sys Inc Methods and apparatus for process, factory-floor, environmental, computer aided manufacturing-based or other control system with real-time data distribution

Patent Citations (27)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5754857A (en) * 1995-12-08 1998-05-19 Sun Microsystems, Inc. Distributed asynchronous workflow on the net
US5758069A (en) * 1996-03-15 1998-05-26 Novell, Inc. Electronic licensing system
US6091808A (en) * 1996-10-17 2000-07-18 Nortel Networks Corporation Methods of and apparatus for providing telephone call control and information
US6785708B1 (en) * 1996-10-30 2004-08-31 Avaya Inc. Method and apparatus for synchronizing browse and chat functions on a computer network
US6347398B1 (en) * 1996-12-12 2002-02-12 Microsoft Corporation Automatic software downloading from a computer network
US6049796A (en) * 1997-02-24 2000-04-11 Nokia Mobile Phones Limited Personal digital assistant with real time search capability
US5903632A (en) * 1997-03-19 1999-05-11 Tmax Technologies Inc. Automated telephone directory
US5903728A (en) * 1997-05-05 1999-05-11 Microsoft Corporation Plug-in control including an independent plug-in process
US6216152B1 (en) * 1997-10-27 2001-04-10 Sun Microsystems, Inc. Method and apparatus for providing plug in media decoders
US6196920B1 (en) * 1998-03-31 2001-03-06 Masque Publishing, Inc. On-line game playing with advertising
US6857124B1 (en) * 1999-01-11 2005-02-15 Eolas Technologies, Inc. Method and system for hypermedia browser API simulation to enable use of browser plug-ins and applets as embedded widgets in script-language-based interactive programs
US6766305B1 (en) * 1999-03-12 2004-07-20 Curl Corporation Licensing system and method for freely distributed information
US6988249B1 (en) * 1999-10-01 2006-01-17 Accenture Llp Presentation service architectures for netcentric computing systems
US6651084B1 (en) * 1999-11-29 2003-11-18 International Business Machines Corporation System and method for adding plug-ins to a web browser
US6853634B1 (en) * 1999-12-14 2005-02-08 Nortel Networks Limited Anonymity in a presence management system
US7249157B2 (en) * 2000-02-16 2007-07-24 Bea Systems, Inc. Collaboration system for exchanging of data between electronic participants via collaboration space by using a URL to identify a combination of both collaboration space and business protocol
US7051071B2 (en) * 2000-02-16 2006-05-23 Bea Systems, Inc. Workflow integration system for enterprise wide electronic collaboration
US20020101448A1 (en) * 2000-11-29 2002-08-01 Sanderson Richard A. Generating a declarative user interface
US20030023679A1 (en) * 2001-03-13 2003-01-30 Stephen Johnson System and process for network collaboration through embedded annotation and rendering instructions
US20020159574A1 (en) * 2001-04-27 2002-10-31 Scott Stogel Automatic telephone directory apparatus and method of operation thereof
US7133900B1 (en) * 2001-07-06 2006-11-07 Yahoo! Inc. Sharing and implementing instant messaging environments
US20040221261A1 (en) * 2002-05-01 2004-11-04 Mike Blevins Collaborative business plug-in framework
US20030233417A1 (en) * 2002-06-17 2003-12-18 Siemens Information And Communication Networks, In System and method for signaling using instant messaging in multimedia telephony-over-lan conferences
US7275215B2 (en) * 2002-07-29 2007-09-25 Cerulean Studios, Llc System and method for managing contacts in an instant messaging environment
US7334043B2 (en) * 2002-09-17 2008-02-19 At&T Delaware Intellectual Property, Inc. Extending functionality of workflow applications using instant messaging (IM)
US7131003B2 (en) * 2003-02-20 2006-10-31 America Online, Inc. Secure instant messaging system
US7120455B1 (en) * 2004-05-20 2006-10-10 Cellco Partnership Method and system for mobile instant messaging using multiple interfaces

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080161956A1 (en) * 2003-01-14 2008-07-03 Yamaha Corporation Musical content utilizing apparatus
US7985910B2 (en) * 2003-01-14 2011-07-26 Yamaha Corporation Musical content utilizing apparatus
US20070005711A1 (en) * 2005-07-01 2007-01-04 Imiogic, Inc. System and method for building instant messaging applications
US20100303873A1 (en) * 2007-12-07 2010-12-02 Estelle Marie Piron Biodegradable single-phase cohesive hydrogels
US20110016184A1 (en) * 2009-07-17 2011-01-20 Alibaba Group Holding Limited Downloading a plug-in on an instant messaging client
US8200769B2 (en) 2009-07-17 2012-06-12 Alibaba Group Holding Limited Downloading a plug-in on an instant messaging client

Also Published As

Publication number Publication date
US20040064696A1 (en) 2004-04-01
US7334043B2 (en) 2008-02-19
US20070185965A1 (en) 2007-08-09
US7945690B2 (en) 2011-05-17
US20080098080A1 (en) 2008-04-24

Similar Documents

Publication Publication Date Title
US5706349A (en) Authenticating remote users in a distributed environment
US8639843B2 (en) System and method for routing messages between applications
US9866503B2 (en) Group communications multiplexing system
US9491126B2 (en) Routing messages between applications
AU2002329730C1 (en) System and method for licensing applications on wireless devices over a wireless network
US7707641B2 (en) Method and apparatus for secure content delivery over broadband access networks
DE60119326T2 (en) Systems and methods for integrity certification and verification of content consumption environments
RU2454013C2 (en) VOICE OVER INTERNET PROTOCOL (VoIP) MANAGEMENT
US8356070B2 (en) High level network layer system and method
DE60212339T2 (en) A digital television application protocol for interactive television
Crispin Internet message access protocol-version 4rev1
US7725541B2 (en) Forwarding to automatically prioritized IM accounts based upon priority and presence
US8073916B2 (en) Managing electronic messages
US7249195B2 (en) Apparatus and methods for correlating messages sent between services
JP4902636B2 (en) Method and system for preventing software piracy in a corporate environment using machine attributes
US9641594B2 (en) Generic download and upload functionality in a client/server web application architecture
US20110145362A1 (en) Method and system for preloading resources
CN1142489C (en) Information processing method and server
US7991156B1 (en) Digital rights management negotiation for streaming media over a network
KR20080098003A (en) Automated file distribution
US20020019851A1 (en) System and method for the electronic mail based management and manipulation of stored files
JP5450354B2 (en) Method and apparatus for providing gifts via a data network
US6763370B1 (en) Method and apparatus for content protection in a secure content delivery system
CN101815039B (en) Passive personalization of buddy lists
US20030053459A1 (en) System and method for invocation of services

Legal Events

Date Code Title Description
AS Assignment

Owner name: AT&T DELAWARE INTELLECTUAL PROPERTY, INC, DELAWARE

Free format text: CHANGE OF NAME;ASSIGNORS:BELLSOUTH INTELLECTUAL PROPERTY CORPORATON (CHANGED TO);AT&T INTELLECTUAL PROPERTY, INC. (CHANGED TO);AT&T BLS INTELLECTUAL PROPERTY, INC. (CHANGED TO);REEL/FRAME:021590/0089;SIGNING DATES FROM 20070427 TO 20071101

Owner name: AT&T DELAWARE INTELLECTUAL PROPERTY, INC,DELAWARE

Free format text: CHANGE OF NAME;ASSIGNORS:BELLSOUTH INTELLECTUAL PROPERTY CORPORATON (CHANGED TO);AT&T INTELLECTUAL PROPERTY, INC. (CHANGED TO);AT&T BLS INTELLECTUAL PROPERTY, INC. (CHANGED TO);SIGNING DATES FROM 20070427 TO 20071101;REEL/FRAME:021590/0089

Owner name: AT&T DELAWARE INTELLECTUAL PROPERTY, INC, DELAWARE

Free format text: CHANGE OF NAME;ASSIGNORS:BELLSOUTH INTELLECTUAL PROPERTY CORPORATON (CHANGED TO);AT&T INTELLECTUAL PROPERTY, INC. (CHANGED TO);AT&T BLS INTELLECTUAL PROPERTY, INC. (CHANGED TO);SIGNING DATES FROM 20070427 TO 20071101;REEL/FRAME:021590/0089

AS Assignment

Owner name: AT&T INTELLECTUAL PROPERTY I, L.P., NEVADA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:AT&T DELAWARE INTELLECTUAL PROPERTY, INC.;REEL/FRAME:021691/0021

Effective date: 20080828

Owner name: AT&T INTELLECTUAL PROPERTY I, L.P.,NEVADA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:AT&T DELAWARE INTELLECTUAL PROPERTY, INC.;REEL/FRAME:021691/0021

Effective date: 20080828

STCB Information on status: application discontinuation

Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION

AS Assignment

Owner name: UBER TECHNOLOGIES, INC., CALIFORNIA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:AT&T INTELLECTUAL PROPERTY I, LP;REEL/FRAME:041660/0584

Effective date: 20170113