WO2001022258A2 - Monitoring users of a computer network - Google Patents

Monitoring users of a computer network Download PDF

Info

Publication number
WO2001022258A2
WO2001022258A2 PCT/US2000/025507 US0025507W WO0122258A2 WO 2001022258 A2 WO2001022258 A2 WO 2001022258A2 US 0025507 W US0025507 W US 0025507W WO 0122258 A2 WO0122258 A2 WO 0122258A2
Authority
WO
WIPO (PCT)
Prior art keywords
user
detecting
message
computer
instant
Prior art date
Application number
PCT/US2000/025507
Other languages
French (fr)
Other versions
WO2001022258A3 (en
Inventor
Andrew L. Wick
Original Assignee
America Online, 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
Application filed by America Online, Inc. filed Critical America Online, Inc.
Priority to CA002385436A priority Critical patent/CA2385436A1/en
Priority to JP2001525552A priority patent/JP2003510687A/en
Priority to AU74960/00A priority patent/AU7496000A/en
Priority to EP00963566A priority patent/EP1214826A2/en
Publication of WO2001022258A2 publication Critical patent/WO2001022258A2/en
Publication of WO2001022258A3 publication Critical patent/WO2001022258A3/en

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • 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
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/50Network services
    • H04L67/54Presence management, e.g. monitoring or registration for receipt of user log-on information, or the connection status of the users
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/30Definitions, standards or architectural aspects of layered protocol stacks
    • H04L69/32Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
    • H04L69/322Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
    • H04L69/329Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the application layer [OSI layer 7]

Definitions

  • This application relates to monitoring users of a computer network, for example, to facilitate messaging between users in an online computer services environment.
  • the computer system 100 illustrated in Fig. 1 represents a typical hardware setup for executing software that allows a user to perform tasks such as communicating with other computer users, accessing various computer resources, and viewing, creating, or otherwise manipulating electronic content -- that is, any combination of text, images, movies, music or other sounds, animations, 3D virtual worlds, and links to other objects.
  • the system includes various input/output (I/O) devices (mouse 103, keyboard 105, display 107) and a general purpose computer 100 having a central processor unit (CPU) 121, an I/O unit 117 and a memory 109 that stores data and various programs such as an operating system 111, and one or more application programs 113.
  • the computer system 100 also typically includes some sort of communications card or device 123 (e.g., a modem or network adapter) for exchanging data with a network 127 via a communications link 125 (e.g., a telephone line).
  • communications card or device 123 e.g., a modem or network adapt
  • a user of a computer system can access electronic content or other resources either stored locally at the user's own client system 202 (for example, a personal or laptop computer) or remotely at one or more server systems 200.
  • An example of a server system is a host computer that provides subscribers with online computer services such as e-mail, e-commerce, chat rooms, Internet access, electronic newspapers and magazines, etc. Users of a host computer's online services typically communicate with one or more central server systems 200 through client software executing on their respective client systems 202.
  • a server system 200 typically will not be a single monolithic entity but rather will be a network of interconnected server computers, possibly physically dispersed from each other, each dedicated to its own set of duties and/or to a particular geographical region. In such a case, the individual servers are interconnected by a network of communication links, in known fashion.
  • One such server system is "America Online 4.0" from America Online, Incorporated of Virginia (also known as "AOL”) .
  • An instant message is a form of electronic communication between users of a computer network in which a window pops-up on the recipient's computer screen "instantly" and without the recipient's having to access an e-mail program or otherwise check for messages.
  • An instant message appears essentially as soon as the message sender clicks the send button subject to any time or propagation delays the message may have encountered on the network.
  • instant messaging enables users to communicate with each other in a more dynamic, urgent and interactive manner.
  • Fig. 3 is a screen shot of an Instant Message (IM) window 30 as used in AOL's Instant Messenger (“AIM”) system.
  • the window 30 includes a text display area 31 and text entry area 32.
  • Both users involved in the IM under consideration i.e., sender and recipient
  • the window 30 includes a text display area 31 and text entry area 32.
  • Both users involved in the IM under consideration i.e., sender and recipient
  • the window 30 includes a text display area 31 and text entry area 32.
  • the Send button 33 or, depending on the configuration, presses the "ENTER” key on the keyboard
  • the entered text e.g., "Hey, did you see the game last night?"
  • FRsnafu enters a comment 35 in response and clicks the Send button 33, that comment 35 appears in the text display area 31 underneath the previous comment 34.
  • This exchange of comments continues indefinitely until the users decide to terminate the exchange .
  • the Buddy List is implemented as a window 40 that lists specified users, or buddies, who are signed on to the AIM system.
  • the Buddy List for user "PhillipsJC" indicates that four of PhillipsJC ' s buddies 41-44 currently are signed on to the system and thus available to receive instant messages.
  • the Buddy List is updated based on information received from a server to add or delete names of buddies as they sign on and off, respectively.
  • Such Buddy List updates can be accompanied by various audible and visual indications to help notify the user that a buddy has signed on or off.
  • a user nevertheless may fail to notice that a buddy with whom IM communication is desired has signed on to the system. For example, if the user is on the telephone or away from his or her office, one of that user's buddies may sign on and then off again unnoticed by the user. Alternatively, or in addition, even when a user notices that a buddy has signed on to the system, the user nevertheless may be unable to send the buddy an IM because the user may be otherwise engaged (e.g., in a meeting) . Other reasons exist why a user might not notice that a buddy has signed on and/or miss an opportunity to send an IM to the buddy.
  • the user might have so many buddies on his buddy list that they cannot all fit on the display screen, or in a display window, at the same time.
  • the buddy list window might be obscured by other windows or objects and thus the user might not be able to notice when the buddy has signed on.
  • the buddy may sign off of the system before the user is able to send an IM, thus missing the window of opportunity. Accordingly, the present inventor recognized that it would be desirable to provide users with mechanisms for monitoring signons by buddies and/or communicating with the buddies immediately and automatically upon their signing on to the system.
  • Summary Implementations may include various combinations of the following eatures .
  • a computer-implemented method of communicating with a user includes detecting that a previously unavailable user is available to receive messages, and automatically sending a predetermined message (e.g., an instant message) to the user upon detecting that the user has become available.
  • a predetermined message e.g., an instant message
  • notification may be provided to a monitoring user that the previously unavailable user has become available and/or that the predetermined message was sent.
  • the method may further include instantiating an instant messaging window on a computer screen of the monitoring user upon detecting that the previously unavailable user has become available.
  • the notified monitoring user may have previously specified the predetermined message.
  • a command specified by the monitoring user may be executed upon detecting the user's availability.
  • a request may have been received from the monitoring user to monitor availability of the previously unavailable user.
  • the received request may be queued until the previously unavailable user becomes available.
  • the automatic sending of the predetermined message may include instantiating a window on the user's computer screen displaying the predetermined message.
  • the operations of detecting and the automatic message sending may be repeated each time the user newly becomes available.
  • the detecting and automatic message sending operations may be performed entirely on one or more server systems, entirely on one or more client systems, or in a distributed manner among one or more server systems and one or more client systems.
  • a computer-implemented instant messaging method may include detecting that a targeted user has signed on to an instant messaging service, and upon detecting the signon, automatically sending to the targeted user an instant message previously specified by a targeting user.
  • the targeting user can receive notification that the targeted user has signed on to the instant messaging service and/or that the instant message was sent.
  • Automatically sending the instant message may include instantiating a window on the targeted user's computer screen displaying the instant message and/or instantiating an instant messaging window on a computer screen of the targeting user upon detecting that the targeted user has signed on.
  • a request may be received from the targeting user to monitor a signon by the targeted user.
  • the received request may be queued until the targeted user signs on.
  • the targeting user also may provide input specifying the instant message.
  • a computer-implemented method of monitoring users of a computer network may include receiving from a monitoring user a request to monitor availability of a monitored user, detecting that the monitored user is available
  • monitoring user e.g., has signed on
  • automatically performing a predefined operation specified by the monitoring user e.g., send an instant message, provide notification to the monitoring user or another entity, or both, and/or execute an operating system command, a script, or an executable file
  • a predefined operation specified by the monitoring user e.g., send an instant message, provide notification to the monitoring user or another entity, or both, and/or execute an operating system command, a script, or an executable file
  • a computer-implemented method, performed at a server, of communicating with a user on a computer network including a plurality of clients and at least one server may include receiving a request to detect when a currently unavailable user becomes available to receive messages, detecting that the user has become available, and automatically sending a predetermined message to the user upon detecting that the user has become available.
  • a computer-implemented method, performed at a client, of communicating with a user on a computer network including a plurality of clients and at least one server may include generating a request to detect when a currently unavailable user becomes available to receive messages, receiving notice that the user has become available, and automatically sending a predetermined message to the user.
  • an instant messaging system may include a server system and one or more client systems, each associated with a corresponding user, in communication with the server system.
  • the server system may include software instructions for (i) monitoring a targeted user's availability to receive instant messages, and (ii) sending a notification that a targeted user has become available to receive instant messages.
  • Each of the one or more client systems may include software instructions for (i) queuing a request to send an instant message to a currently unavailable targeted user, and (ii) sending the instant message to the targeted user upon receiving notification from the server system that the targeted user has become available to receive instant messages.
  • the techniques and methods described here enable users to more reliably and efficiently track the comings and goings of their buddies. As a result, the likelihood of a user's being able to communicate (e.g., by instant message) with buddies, even those who sign on to the computer service infrequently or sporadically, is enhanced dramatically.
  • communication between users is improved by providing mechanisms to automatically and instantly communicate with buddies upon their signing on to the computer service.
  • the sending user needs neither to be aware of the buddy's signing on, nor be available to send an IM, for this automatic and instant communication to occur. Rather, the sending user needs only to set up the "pounce" and the buddy at whom the pounce is targeted can receive an IM automatically and without requiring the sending user's further attention or authorization.
  • FIG. 1 is a block diagram of a computer system.
  • Fig. 2 shows a typical network computing environment.
  • Fig. 3 is a screen shot of an "Instant Message" window.
  • Fig. 4 is a screen shot of a "Buddy List” window in AOL's Instant Messenger for Windows.
  • Fig. 5 is a flowchart of pouncing on a user.
  • Fig. 6 is a screen shot of a "Buddy List" window in AOL Instant Messenger for Unix.
  • Fig. 7 is a screen shot of a "Tools" pull-down menu in the Buddy List window of Fig. 6.
  • Fig. 8 is a screen shot of a "Create New Pounce” window.
  • Fig. 9 is a screen shot of an instant message window corresponding to the Create New Pounce window of Fig. 8.
  • Fig. 10 is screen shot of a "Conversation” window.
  • Fig. 11 is a screen shot of a "Send IM” window.
  • Fig. 12 is another screen shot of a "Tools" pull -down menu in the Buddy List window of Fig. 6.
  • Fig. 13 is a screen shot of an "Edit Pounce" window. Like reference numbers and designations in the various drawings indicate like elements.
  • Fig. 5 is a flowchart of a process that allows one user to "pounce” on another user (e.g., a buddy) as soon as the buddy signs on to the computer service.
  • “Pounce” refers to the ability to take one or more specified actions (e.g., send a message, emit an audible or visual notification, execute a command, etc.) automatically upon determining that a specified event has occurred, for example, detecting that a buddy has signed on to the computer service.
  • a first user sets up the parameters of the pounce (step 50) .
  • typical parameters that could be specified by the pouncer include the identity of the pouncee
  • the event that triggers the pounce e.g., pouncee ' s signing on to system, pouncee ' s sending an IM to a specified party, detection of being added to or deleted from the pouncee ' s buddy list, etc.
  • the action or actions that are to be taken e.g., send an IM; send a chat invitation, audible or visual notification, execute a specified command, or any other arbitrary action
  • the pounce should occur only once or upon each separate detection of the specified trigger event.
  • the pouncee designated in step 50 can, but need not necessarily, be on the pouncer ' s Buddy List .
  • the pounce is queued pending occurrence of the specified event (step 51) .
  • an indication is set at the server that the pouncer ' s client application is to be notified upon detection of the specified event.
  • the queue can be maintained either locally at the pouncer ' s client system or remotely at a server system. Either a single pounce or multiple pounces can be in the queue 5 concurrently.
  • a pounce can be either a single-shot (i.e., executed only once on the first occurrence of the specified event) or persistent (i.e., executed with each occurrence of the specified event) .
  • the next step is to wait for occurrence of the specified loevent (step 52), for example, a detection that a specified user has signed on to the computer service. This detection can occur either at the client system or in conjunction with a server on the network.
  • Execution of the pounce can occur at the pouncer 's client system or at the pouncee ' s client system, or both, potentially in conjunction with one or more server systems.
  • Execution of the pounce can occur at the pouncer 's client system or at the pouncee ' s client system, or both, potentially in conjunction with one or more server systems.
  • the particular actions that can be taken upon execution of the pounce can vary with different implementations,
  • Typical actions may include one or more of the following: sounding an alarm (step 54) ; sending an IM (step 55) , opening a conversation window on the pouncer ' s client system (step 56); or executing a user- specified command (step 57) , for example, locally on the
  • each of the actions indicated in steps 54-57 is optional. Moreover, other actions beyond or in addition to those shown in steps 54- 57 may be taken.
  • step 58 determines whether or not the pounce is persistent -- that is, whether or not the pounce should be executed only once or each time upon detection of the specified event (step 58) . If the pounce is persistent, it remains in the queue and the process returns to step 52 to wait for the next specified event . On the other hand, if the pounce is a single-shot, the pounce is removed from the queue (step 59) and the process returns to step 50 to allow the pouncer to set up another pounce, as desired.
  • FIG. 5 generally represents steps that are taken for each individual pounce sequence .
  • Figs. 6-13 are screen shots illustrating an implementation of the pounce concept in a Unix-based version of the AIM application (referred to as "TiK”) .
  • Fig. 6 shows a TiK Buddy List window 60 for user "FRsnafu” displaying a list 61 of three of FRsnafu 's buddies 62 currently signed on to the AIM system.
  • the Buddy List window 60 also includes a menu bar 67 listing three drop-down menus (File, Tools, Help), a text area 66 for entering text strings for web searches, an IM button 63 for instantiating an IM window to send an IM to another user, an Info button 64 for retrieving information about another user, and a Chat button 65 for instantiating a Chat window to invite another user to participate in a chat session.
  • a menu bar 67 listing three drop-down menus (File, Tools, Help)
  • a text area 66 for entering text strings for web searches
  • an IM button 63 for instantiating an IM window to send an IM to another user
  • an Info button 64 for retrieving information about another user
  • a Chat button 65 for instantiating a Chat window to invite another user to participate in a chat session.
  • the Buddy List window 60 in Fig. 6 indicates that three of FRsnafu 's buddies 62 currently are signed on to AIM.
  • user FRsnafu desires to send an IM to another buddy, "PhillipsJC, " who is not currently signed on to the AIM system.
  • FRsnafu the pouncer in this example, decides to set up a pounce to receive notification, and to send PhillipsJC an IM, as soon as PhillipsJC signs on to AIM.
  • Fig. 7 is a screen shot of the Tools drop-down menu 70, which the pouncer accesses to set up a pounce. As shown therein, the pouncer selects menu option “Buddy Pounce” 72, which in turn brings up a sub-menu displaying a single option 73, "New Pounce,” that enables the pouncer to set up the desired pounce .
  • menu option “Buddy Pounce” 72 which in turn brings up a sub-menu displaying a single option 73, "New Pounce,” that enables the pouncer to set up the desired pounce .
  • Fig. 8 shows a "Create New Pounce” window 80 which is displayed on the pouncer ' s screen in response to selection of the "New Pounce” option 73.
  • the Create New Pounce window 80 includes a name field 81 into which the pouncer enters the name of the pouncee -- i.e., the buddy who is the subject of the pounce.
  • the window 80 also includes five checkboxes 82-86 that the pouncer can check or not to selectively activate five corresponding features.
  • a blank IM window 110 (Fig. 11) will pop up on the pouncer 's screen when the pouncee signs on to the AIM system. Under this option, an IM is not sent automatically to the pouncee, but rather the IM interface window is merely instantiated to allow the pouncer to easily and quickly enter appropriate text and send an IM to the pouncee.
  • an IM will be sent to the pouncee automatically, and will pop up on the pouncee ' s screen, as soon as the pouncee signs on to AIM.
  • This automatic sending of an IM is performed transparently as a consequence of the AIM system detecting the specified event (i.e., the pouncee ' s signing on) and without any input or response on the part of the pouncer beyond initially setting up the pounce.
  • the particular text to be included in the IM sent to the pouncee -- "Gotcha! -- is specified by the pouncer in message field 87.
  • Fig. 9 is a screen shot of the Instant Message window 90 that pops up on the pouncee ' s window upon signing on to AIM.
  • the window 90 includes a text display area 93 showing the identity 91 of the IM sender (i.e., the pouncer) and the message 92 ("Gotcha!) specified by the pouncer.
  • the Tik application When the pouncer designates by checking box 83 (Fig. 8) that an IM should sent to the pouncee automatically, the Tik application also automatically instantiates a "Conversation" window 102 on the pouncer ' s client system, as shown in Fig. 10.
  • the Conversation window 102 fulfills the same function as the Instant Message window 30 shown in Fig. 3.
  • the Conversation window 102 includes a text display area 112, a text entry area 116, and buttons 118 to allow the user to control various aspects of the IM presentation and exchange.
  • the text display area 112 in window 102 includes a single line of text corresponding to the IM automatically sent to the pouncee upon execution of the pounce.
  • This single line includes a time field 104 showing the time at which the IM was sent, a name field 106 showing the IM sender's identity, and a message field 108 showing the message.
  • Checking box 84 in window 80 causes a "Pounce Sound" (i.e., an audible notification) to be played on the pouncer 's client system upon execution of the pounce. The Pounce Sound notifies the pouncer that the pouncee has signed on to the AIM system.
  • Box 85 in window 80 determines whether the pounce should be a single-shot or persistent. In the example shown, box 85 is unchecked so the pounce being set up in Fig.
  • the pouncer can specify a command (for example, a operating system command, a script, or an executable file) that is to be executed as part of the pounce execution.
  • a command for example, a operating system command, a script, or an executable file
  • notify.exe is specified by the pouncer in text entry area 88 and can be virtually any command that is executable by the pouncer ' s client system.
  • the notify.exe command could send an IM to one or more third parties informing them that the pouncee has signed on.
  • notify.exe could launch another application (e.g., an online computer game to play with the pouncee) or initiate virtually any other arbitrarily-complex or arbitrarily-simple computer-controlled operation.
  • the pouncer clicks button 89 (Fig. 8) and the pounce is then saved in the queue of currently pending pounces .
  • a single user can have more than one pounce pending in the queue at the same time.
  • Fig. 12, for 5 example shows a Buddy List sub-menu 120 for a pouncer who has three pounces 122, 124 and 126 concurrently queued up and pending. Each of these pounces 122, 124, 126 is individually configurable as described above with regard to Fig. 8.
  • a queued pounce can be modified as desired by 0 selecting it from the sub-menu 120, which in turn brings up an "Edit Pounce" window 130 as shown in Fig. 13.
  • the Edit Pounce window 130 essentially is the same as the Create New Pounce window 80 shown in Fig. 8, except that the Edit Pounce window 130 is presented to the pouncer with the data fields and check 5 boxes selectively filled in according to the pounce's current parameter set .
  • the pouncer can modify any of these parameters by checking or unchecking boxes 132-136, and/or changing the text in fields 137-139. Once the pounce's parameters have been modified as desired, the pouncer can save the modified pounce in 0 the queue by clicking the OK button 141.
  • the pouncer can delete the pounce from the queue by clicking the Delete button 140.
  • the techniques, methods and systems described here may find applicability in any computing or processing environment in which monitoring other users and/or communicating with them is desirable.
  • the concept of pouncing on another user could be applied to other media such as internet TV, cellular telephones, pagers, two-way radios, etc.
  • a cellular telephone service provider could implement a system in which a queued-up telephone call was completed as soon as the intended recipient turned on his or her cell phone.
  • Various implementations of the systems and techniques described here may be realized in digital electronic circuitry, or in computer hardware, firmware, software, or in combinations thereof .
  • a system or other apparatus that uses one or more of the techniques and methods described here may be implemented as a computer-readable storage medium, configured with a computer program, where the storage medium so configured causes a computer system to operate on input and/or generate output in a specific and predefined manner.
  • a computer system may include one or more programmable processors that receive data and instructions from, and transmit data and instructions to, a data storage system, and suitable input and output devices .
  • Each computer program may be implemented in a high-level procedural or object-oriented programming language, or in assembly or machine language if desired; and in any case, the language may be a compiled or interpreted language.
  • Suitable processors include, by way of example, both general and special purpose microprocessors.
  • a processor will receive instructions and data from a read-only memory and/or a random access memory.
  • Storage devices suitable for tangibly embodying computer program instructions and data include all forms of non-volatile memory, including semiconductor memory devices, such as EPROM, EEPROM, and flash memory devices; magnetic disks such as internal hard disks and removable disks; magneto-optical disks; and CD-ROM disks .
  • ASICs application-specific integrated circuits

Abstract

Communicating with and/or monitoring of a targeted user in computer-network environment (e.g., an instant messaging system) involves detecting that the targeted user has signed on to the network, and upon detecting the signon, automatically communicating with the targeted user, for example, by sending an instant message previously specified by a targeting user. Alternatively, or in addition, the targeting user can receive notification that the targeted user has signed on and/or that the instant message has been sent. Instead of, or in addition to, automatically sending an instant message and/or notifying the targeting user, a predefined operation specified by the targeting user (e.g., operating system command, script or executable file) can be performed. These various operations can be performed on one or more client systems, on one or more server systems, or any combination thereof.

Description

MONITORING USERS OF A COMPUTER NETWORK
Technical Field
This application relates to monitoring users of a computer network, for example, to facilitate messaging between users in an online computer services environment.
Background
The computer system 100 illustrated in Fig. 1 represents a typical hardware setup for executing software that allows a user to perform tasks such as communicating with other computer users, accessing various computer resources, and viewing, creating, or otherwise manipulating electronic content -- that is, any combination of text, images, movies, music or other sounds, animations, 3D virtual worlds, and links to other objects. The system includes various input/output (I/O) devices (mouse 103, keyboard 105, display 107) and a general purpose computer 100 having a central processor unit (CPU) 121, an I/O unit 117 and a memory 109 that stores data and various programs such as an operating system 111, and one or more application programs 113. The computer system 100 also typically includes some sort of communications card or device 123 (e.g., a modem or network adapter) for exchanging data with a network 127 via a communications link 125 (e.g., a telephone line).
As shown in Fig. 2, a user of a computer system can access electronic content or other resources either stored locally at the user's own client system 202 (for example, a personal or laptop computer) or remotely at one or more server systems 200. An example of a server system is a host computer that provides subscribers with online computer services such as e-mail, e-commerce, chat rooms, Internet access, electronic newspapers and magazines, etc. Users of a host computer's online services typically communicate with one or more central server systems 200 through client software executing on their respective client systems 202. In practice, a server system 200 typically will not be a single monolithic entity but rather will be a network of interconnected server computers, possibly physically dispersed from each other, each dedicated to its own set of duties and/or to a particular geographical region. In such a case, the individual servers are interconnected by a network of communication links, in known fashion. One such server system is "America Online 4.0" from America Online, Incorporated of Virginia (also known as "AOL") .
One increasingly popular computer network-based activity is referred to as "instant messaging." An instant message is a form of electronic communication between users of a computer network in which a window pops-up on the recipient's computer screen "instantly" and without the recipient's having to access an e-mail program or otherwise check for messages. An instant message appears essentially as soon as the message sender clicks the send button subject to any time or propagation delays the message may have encountered on the network. In comparison to most e-mail applications, instant messaging enables users to communicate with each other in a more dynamic, urgent and interactive manner.
Fig. 3 is a screen shot of an Instant Message (IM) window 30 as used in AOL's Instant Messenger ("AIM") system. As shown therein, the window 30 includes a text display area 31 and text entry area 32. Both users involved in the IM under consideration (i.e., sender and recipient) would have a similar window displayed on his or her computer monitor. When one user (PhillipsJC) types a comment 34 in text entry area 32 and clicks the Send button 33 (or, depending on the configuration, presses the "ENTER" key on the keyboard), the entered text (e.g., "Hey, did you see the game last night?") is displayed in the text display area 31 of the window 30 such that it is visible to both users. After FRsnafu enters a comment 35 in response and clicks the Send button 33, that comment 35 appears in the text display area 31 underneath the previous comment 34. This exchange of comments continues indefinitely until the users decide to terminate the exchange .
Typically, instant messages can be sent to another user only when that user is presently signed on to the computer service. Users who are signed off are unavailable to receive instant messages. Accordingly, another popular innovation introduced by America Online is the "Buddy List," which allows users to monitor when other specified users ("buddies") are signed onto and/or off of the computer service under consideration (e.g., AOL Instant Messenger).
As shown in Fig. 4, the Buddy List is implemented as a window 40 that lists specified users, or buddies, who are signed on to the AIM system. In the example shown, the Buddy List for user "PhillipsJC" indicates that four of PhillipsJC ' s buddies 41-44 currently are signed on to the system and thus available to receive instant messages. The Buddy List is updated based on information received from a server to add or delete names of buddies as they sign on and off, respectively. Such Buddy List updates can be accompanied by various audible and visual indications to help notify the user that a buddy has signed on or off.
Despite the various notification mechanisms, a user nevertheless may fail to notice that a buddy with whom IM communication is desired has signed on to the system. For example, if the user is on the telephone or away from his or her office, one of that user's buddies may sign on and then off again unnoticed by the user. Alternatively, or in addition, even when a user notices that a buddy has signed on to the system, the user nevertheless may be unable to send the buddy an IM because the user may be otherwise engaged (e.g., in a meeting) . Other reasons exist why a user might not notice that a buddy has signed on and/or miss an opportunity to send an IM to the buddy. For example, the user might have so many buddies on his buddy list that they cannot all fit on the display screen, or in a display window, at the same time. Moreover, the buddy list window might be obscured by other windows or objects and thus the user might not be able to notice when the buddy has signed on. In any of these and possibly other situations, the buddy may sign off of the system before the user is able to send an IM, thus missing the window of opportunity. Accordingly, the present inventor recognized that it would be desirable to provide users with mechanisms for monitoring signons by buddies and/or communicating with the buddies immediately and automatically upon their signing on to the system.
Summary Implementations may include various combinations of the following eatures .
In one aspect, a computer-implemented method of communicating with a user includes detecting that a previously unavailable user is available to receive messages, and automatically sending a predetermined message (e.g., an instant message) to the user upon detecting that the user has become available. Alternatively, or in addition, notification may be provided to a monitoring user that the previously unavailable user has become available and/or that the predetermined message was sent. The method may further include instantiating an instant messaging window on a computer screen of the monitoring user upon detecting that the previously unavailable user has become available. Optionally, the notified monitoring user may have previously specified the predetermined message. Moreover, a command specified by the monitoring user (e.g., an operating system command, a script, or an executable file) may be executed upon detecting the user's availability. Prior to the detection, a request may have been received from the monitoring user to monitor availability of the previously unavailable user. The received request may be queued until the previously unavailable user becomes available. The automatic sending of the predetermined message may include instantiating a window on the user's computer screen displaying the predetermined message. The operations of detecting and the automatic message sending may be repeated each time the user newly becomes available. Moreover, the detecting and automatic message sending operations may be performed entirely on one or more server systems, entirely on one or more client systems, or in a distributed manner among one or more server systems and one or more client systems. In another aspect, a computer-implemented instant messaging method may include detecting that a targeted user has signed on to an instant messaging service, and upon detecting the signon, automatically sending to the targeted user an instant message previously specified by a targeting user. The targeting user can receive notification that the targeted user has signed on to the instant messaging service and/or that the instant message was sent.
Automatically sending the instant message may include instantiating a window on the targeted user's computer screen displaying the instant message and/or instantiating an instant messaging window on a computer screen of the targeting user upon detecting that the targeted user has signed on.
Prior to detection, a request may be received from the targeting user to monitor a signon by the targeted user. The received request may be queued until the targeted user signs on.
The targeting user also may provide input specifying the instant message.
In another aspect, a computer-implemented method of monitoring users of a computer network may include receiving from a monitoring user a request to monitor availability of a monitored user, detecting that the monitored user is available
(e.g., has signed on), and automatically performing a predefined operation specified by the monitoring user (e.g., send an instant message, provide notification to the monitoring user or another entity, or both, and/or execute an operating system command, a script, or an executable file) upon detecting that the monitored user is available.
In another aspect, a computer-implemented method, performed at a server, of communicating with a user on a computer network including a plurality of clients and at least one server, may include receiving a request to detect when a currently unavailable user becomes available to receive messages, detecting that the user has become available, and automatically sending a predetermined message to the user upon detecting that the user has become available. In another aspect, a computer-implemented method, performed at a client, of communicating with a user on a computer network including a plurality of clients and at least one server, may include generating a request to detect when a currently unavailable user becomes available to receive messages, receiving notice that the user has become available, and automatically sending a predetermined message to the user.
In another aspect, an instant messaging system may include a server system and one or more client systems, each associated with a corresponding user, in communication with the server system. The server system may include software instructions for (i) monitoring a targeted user's availability to receive instant messages, and (ii) sending a notification that a targeted user has become available to receive instant messages. Each of the one or more client systems may include software instructions for (i) queuing a request to send an instant message to a currently unavailable targeted user, and (ii) sending the instant message to the targeted user upon receiving notification from the server system that the targeted user has become available to receive instant messages. One or more of the following advantages may be provided.
The techniques and methods described here enable users to more reliably and efficiently track the comings and goings of their buddies. As a result, the likelihood of a user's being able to communicate (e.g., by instant message) with buddies, even those who sign on to the computer service infrequently or sporadically, is enhanced dramatically.
In addition, communication between users is improved by providing mechanisms to automatically and instantly communicate with buddies upon their signing on to the computer service. The sending user needs neither to be aware of the buddy's signing on, nor be available to send an IM, for this automatic and instant communication to occur. Rather, the sending user needs only to set up the "pounce" and the buddy at whom the pounce is targeted can receive an IM automatically and without requiring the sending user's further attention or authorization.
The details of one or more embodiments are set forth in the accompanying drawings and the description below. Other features, objects, and advantages of the invention will be apparent from the description and drawings, and from the claims.
Drawing Descriptions Fig. 1 is a block diagram of a computer system.
Fig. 2 shows a typical network computing environment. Fig. 3 is a screen shot of an "Instant Message" window. Fig. 4 is a screen shot of a "Buddy List" window in AOL's Instant Messenger for Windows. Fig. 5 is a flowchart of pouncing on a user.
Fig. 6 is a screen shot of a "Buddy List" window in AOL Instant Messenger for Unix.
Fig. 7 is a screen shot of a "Tools" pull-down menu in the Buddy List window of Fig. 6. Fig. 8 is a screen shot of a "Create New Pounce" window. Fig. 9 is a screen shot of an instant message window corresponding to the Create New Pounce window of Fig. 8. Fig. 10 is screen shot of a "Conversation" window. Fig. 11 is a screen shot of a "Send IM" window. Fig. 12 is another screen shot of a "Tools" pull -down menu in the Buddy List window of Fig. 6.
Fig. 13 is a screen shot of an "Edit Pounce" window. Like reference numbers and designations in the various drawings indicate like elements.
Detailed Description Fig. 5 is a flowchart of a process that allows one user to "pounce" on another user (e.g., a buddy) as soon as the buddy signs on to the computer service. "Pounce" refers to the ability to take one or more specified actions (e.g., send a message, emit an audible or visual notification, execute a command, etc.) automatically upon determining that a specified event has occurred, for example, detecting that a buddy has signed on to the computer service.
As shown in Fig. 5, as an initial step in pouncing on another user (the "pouncee" or "targeted user"), a first user (the "pouncer" or "targeting user") sets up the parameters of the pounce (step 50) . Although these parameters can vary between implementations, typical parameters that could be specified by the pouncer include the identity of the pouncee
(specified by, e.g., signon ID, name, e-mail address, etc.); the event that triggers the pounce (e.g., pouncee ' s signing on to system, pouncee ' s sending an IM to a specified party, detection of being added to or deleted from the pouncee ' s buddy list, etc.); the action or actions that are to be taken (e.g., send an IM; send a chat invitation, audible or visual notification, execute a specified command, or any other arbitrary action); and whether the pounce should occur only once or upon each separate detection of the specified trigger event. The pouncee designated in step 50 can, but need not necessarily, be on the pouncer ' s Buddy List . After being set-up by the pouncer, the pounce is queued pending occurrence of the specified event (step 51) . In effect, an indication is set at the server that the pouncer ' s client application is to be notified upon detection of the specified event. The queue can be maintained either locally at the pouncer ' s client system or remotely at a server system. Either a single pounce or multiple pounces can be in the queue 5 concurrently. In addition, a pounce can be either a single-shot (i.e., executed only once on the first occurrence of the specified event) or persistent (i.e., executed with each occurrence of the specified event) .
The next step is to wait for occurrence of the specified loevent (step 52), for example, a detection that a specified user has signed on to the computer service. This detection can occur either at the client system or in conjunction with a server on the network.
Next, upon occurrence of the specified event, the pounce
15 is executed (step 53) . Execution of the pounce can occur at the pouncer 's client system or at the pouncee ' s client system, or both, potentially in conjunction with one or more server systems. The particular actions that can be taken upon execution of the pounce can vary with different implementations,
20 and/or based on user-specified preferences. Typical actions may include one or more of the following: sounding an alarm (step 54) ; sending an IM (step 55) , opening a conversation window on the pouncer ' s client system (step 56); or executing a user- specified command (step 57) , for example, locally on the
25 pouncer 's client system. As indicated by dotted lines, each of the actions indicated in steps 54-57 is optional. Moreover, other actions beyond or in addition to those shown in steps 54- 57 may be taken.
After the pounce has been executed, it is determined
30 whether or not the pounce is persistent -- that is, whether or not the pounce should be executed only once or each time upon detection of the specified event (step 58) . If the pounce is persistent, it remains in the queue and the process returns to step 52 to wait for the next specified event . On the other hand, if the pounce is a single-shot, the pounce is removed from the queue (step 59) and the process returns to step 50 to allow the pouncer to set up another pounce, as desired.
A single user can have multiple pounces pending at the same time. The process shown in Fig. 5 generally represents steps that are taken for each individual pounce sequence .
Figs. 6-13 are screen shots illustrating an implementation of the pounce concept in a Unix-based version of the AIM application (referred to as "TiK") . Fig. 6 shows a TiK Buddy List window 60 for user "FRsnafu" displaying a list 61 of three of FRsnafu 's buddies 62 currently signed on to the AIM system. The Buddy List window 60 also includes a menu bar 67 listing three drop-down menus (File, Tools, Help), a text area 66 for entering text strings for web searches, an IM button 63 for instantiating an IM window to send an IM to another user, an Info button 64 for retrieving information about another user, and a Chat button 65 for instantiating a Chat window to invite another user to participate in a chat session.
As noted above, the Buddy List window 60 in Fig. 6 indicates that three of FRsnafu 's buddies 62 currently are signed on to AIM. However, in this example, user FRsnafu desires to send an IM to another buddy, "PhillipsJC, " who is not currently signed on to the AIM system. Accordingly, FRsnafu, the pouncer in this example, decides to set up a pounce to receive notification, and to send PhillipsJC an IM, as soon as PhillipsJC signs on to AIM.
Fig. 7 is a screen shot of the Tools drop-down menu 70, which the pouncer accesses to set up a pounce. As shown therein, the pouncer selects menu option "Buddy Pounce" 72, which in turn brings up a sub-menu displaying a single option 73, "New Pounce," that enables the pouncer to set up the desired pounce .
Fig. 8 shows a "Create New Pounce" window 80 which is displayed on the pouncer ' s screen in response to selection of the "New Pounce" option 73. As shown in Fig. 8, the Create New Pounce window 80 includes a name field 81 into which the pouncer enters the name of the pouncee -- i.e., the buddy who is the subject of the pounce. The window 80 also includes five checkboxes 82-86 that the pouncer can check or not to selectively activate five corresponding features.
If the pouncer checks box 82, a blank IM window 110 (Fig. 11) will pop up on the pouncer 's screen when the pouncee signs on to the AIM system. Under this option, an IM is not sent automatically to the pouncee, but rather the IM interface window is merely instantiated to allow the pouncer to easily and quickly enter appropriate text and send an IM to the pouncee.
In contrast, if the pouncer checks box 83 in window 80 (Fig. 8), an IM will be sent to the pouncee automatically, and will pop up on the pouncee ' s screen, as soon as the pouncee signs on to AIM. This automatic sending of an IM is performed transparently as a consequence of the AIM system detecting the specified event (i.e., the pouncee ' s signing on) and without any input or response on the part of the pouncer beyond initially setting up the pounce. The particular text to be included in the IM sent to the pouncee -- "Gotcha!" -- is specified by the pouncer in message field 87.
Fig. 9 is a screen shot of the Instant Message window 90 that pops up on the pouncee ' s window upon signing on to AIM. As shown, the window 90 includes a text display area 93 showing the identity 91 of the IM sender (i.e., the pouncer) and the message 92 ("Gotcha!") specified by the pouncer.
When the pouncer designates by checking box 83 (Fig. 8) that an IM should sent to the pouncee automatically, the Tik application also automatically instantiates a "Conversation" window 102 on the pouncer ' s client system, as shown in Fig. 10. Essentially, the Conversation window 102 fulfills the same function as the Instant Message window 30 shown in Fig. 3. Specifically, the Conversation window 102 includes a text display area 112, a text entry area 116, and buttons 118 to allow the user to control various aspects of the IM presentation and exchange. As shown in Fig. 10, the text display area 112 in window 102 includes a single line of text corresponding to the IM automatically sent to the pouncee upon execution of the pounce. This single line includes a time field 104 showing the time at which the IM was sent, a name field 106 showing the IM sender's identity, and a message field 108 showing the message. Checking box 84 in window 80 (Fig. 8) causes a "Pounce Sound" (i.e., an audible notification) to be played on the pouncer 's client system upon execution of the pounce. The Pounce Sound notifies the pouncer that the pouncee has signed on to the AIM system. Box 85 in window 80 determines whether the pounce should be a single-shot or persistent. In the example shown, box 85 is unchecked so the pounce being set up in Fig. 8 will be persistent -- that is, it will execute with each detection of a signon by the pouncee. In contrast, if box 85 was checked, the pounce would execute only once upon next detecting a signon by the pouncee and then would be deleted from the pounce queue .
By checking box 86 in window 80 (Fig. 8), the pouncer can specify a command (for example, a operating system command, a script, or an executable file) that is to be executed as part of the pounce execution. The particular command to be executed in this example, an executable file at the path
"c:\notify.exe" -- is specified by the pouncer in text entry area 88 and can be virtually any command that is executable by the pouncer ' s client system. For example, the notify.exe command could send an IM to one or more third parties informing them that the pouncee has signed on. Alternatively, or in saddition, notify.exe could launch another application (e.g., an online computer game to play with the pouncee) or initiate virtually any other arbitrarily-complex or arbitrarily-simple computer-controlled operation.
When the pouncer has set up the new pounce with the 0 desired parameters, the pouncer clicks button 89 (Fig. 8) and the pounce is then saved in the queue of currently pending pounces .
As noted above, a single user can have more than one pounce pending in the queue at the same time. Fig. 12, for 5 example, shows a Buddy List sub-menu 120 for a pouncer who has three pounces 122, 124 and 126 concurrently queued up and pending. Each of these pounces 122, 124, 126 is individually configurable as described above with regard to Fig. 8.
Moreover, a queued pounce can be modified as desired by 0 selecting it from the sub-menu 120, which in turn brings up an "Edit Pounce" window 130 as shown in Fig. 13. The Edit Pounce window 130 essentially is the same as the Create New Pounce window 80 shown in Fig. 8, except that the Edit Pounce window 130 is presented to the pouncer with the data fields and check 5 boxes selectively filled in according to the pounce's current parameter set . The pouncer can modify any of these parameters by checking or unchecking boxes 132-136, and/or changing the text in fields 137-139. Once the pounce's parameters have been modified as desired, the pouncer can save the modified pounce in 0 the queue by clicking the OK button 141. Alternatively, the pouncer can delete the pounce from the queue by clicking the Delete button 140. The techniques, methods and systems described here may find applicability in any computing or processing environment in which monitoring other users and/or communicating with them is desirable. In particular, the concept of pouncing on another user could be applied to other media such as internet TV, cellular telephones, pagers, two-way radios, etc. For example, a cellular telephone service provider could implement a system in which a queued-up telephone call was completed as soon as the intended recipient turned on his or her cell phone. Various implementations of the systems and techniques described here may be realized in digital electronic circuitry, or in computer hardware, firmware, software, or in combinations thereof . A system or other apparatus that uses one or more of the techniques and methods described here may be implemented as a computer-readable storage medium, configured with a computer program, where the storage medium so configured causes a computer system to operate on input and/or generate output in a specific and predefined manner. Such a computer system may include one or more programmable processors that receive data and instructions from, and transmit data and instructions to, a data storage system, and suitable input and output devices .
Each computer program may be implemented in a high-level procedural or object-oriented programming language, or in assembly or machine language if desired; and in any case, the language may be a compiled or interpreted language. Suitable processors include, by way of example, both general and special purpose microprocessors.
Generally, a processor will receive instructions and data from a read-only memory and/or a random access memory. Storage devices suitable for tangibly embodying computer program instructions and data include all forms of non-volatile memory, including semiconductor memory devices, such as EPROM, EEPROM, and flash memory devices; magnetic disks such as internal hard disks and removable disks; magneto-optical disks; and CD-ROM disks .
Any of the foregoing may be supplemented by, or implemented in, specially-designed ASICs (application- specific integrated circuits) .
A number of embodiments have been described.
Nevertheless, it will be understood that various modifications may be made without departing from the spirit and scope of the invention. Accordingly, other embodiments are within the scope of the following claims.

Claims

What is claimed is:
l 1. A computer-implemented method of communicating with 2a user, the method comprising:
1 detecting that a previously unavailable user is
2 available to receive messages; and
3 automatically sending a predetermined message to the
4 user upon detecting that the user has become available.
1 2. The method of claim 1 further comprising providing
2 notification to a monitoring user that the previously
3 unavailable user has become available.
1 3. The method of claim 2 wherein the notified
2 monitoring user previously specified the predetermined message.
1 4. The method of claim 1 further comprising providing
2 notification to a monitoring user that the predetermined message
3 was sen .
1 5. The method of claim 4 wherein the notified
2 monitoring user previously specified the predetermined message.
i 6. The method of claim 1 wherein the predetermined 2 message comprises an instant message.
1 7. The method of claim 1 wherein the predetermined
2 message comprises content specified by a monitoring user seeking
3 to communicate with the previously unavailable user.
1 8. The method of claim 1 wherein automatically sending
2 the predetermined message comprises instantiating a window on the user's computer screen displaying the predetermined message.
9. The method of claim 1 further comprising, prior to the detection, receiving a request from a monitoring user to monitor availability of the previously unavailable user.
10. The method of claim 9 further comprising queuing the received request until the previously unavailable user becomes available.
11. The method of claim 9 further comprising receiving input from the monitoring user specifying the predetermined message.
12. The method of claim 9 further comprising instantiating an instant messaging window on a computer screen of the monitoring user upon detecting that the previously unavailable user has become available.
13. The method of claim 9 further comprising executing a command specified by the monitoring user.
14. The method of claim 13 wherein the command comprises one or more of an operating system command, a script, or an executable file.
15. The method of claim 1 further comprising repeating the detecting and the automatic message sending each time the user newly becomes available.
16. The method of claim 1 wherein the detecting and the automatic message sending are performed entirely on one or more 3 server systems .
1 17. The method of claim 1 wherein the detecting and the
2 automatic message sending are performed entirely on one or more
3 client systems.
1 18. The method of claim 1 wherein the detecting and the
2 automatic message sending are distributed among one or more
3 server systems and one or more client systems.
1 19. A computer-implemented instant messaging method
2 comprising:
1 detecting that a targeted user has signed on to an
2 instant messaging service; and
3 upon detecting the signon, automatically sending to the
4 targeted user an instant message previously specified by a
5 targeting user.
1 20. The method of claim 19 further comprising providing
2 notification to the targeting user that the targeted user has
3 signed on to the instant messaging service.
1 21. The method of claim 19 further comprising providing
2 notification to the targeting user that the instant message was
3 sent .
1 22. The method of claim 19 wherein automatically
2 sending the instant message comprises instantiating a window on
3 the targeted user's computer screen displaying the instant
4 message.
i
23. The method of claim 19 further comprising, prior to 2 the detection, receiving a request from the targeting user to
3 monitor a signon by the targeted user.
1 24. The method of claim 23 further comprising queuing
2 the received request until the targeted user signs on.
1 25. The method of claim 23 further comprising receiving
2 input from the targeting user specifying the instant message.
i
26. The method of claim 23 further comprising
2 instantiating an instant messaging window on a computer screen
3 of the targeting user upon detecting that the targeted user has
4 signed on.
l
27. The method of claim 23 further comprising executing 2a command specified by the targeting user.
1 28. The method of claim 27 wherein the command
2 comprises one or more of an operating system command, a script,
3 or an executable file.
1 29. The method of claim 19 further comprising repeating
2 the detecting and the automatic instant message sending each
3 time the targeting user signs on.
1 30. The method of claim 19 wherein the detecting and
2 the automatic instant message sending are performed entirely on
3 one or more server systems .
1 31. The method of claim 19 wherein the detecting and
2 the automatic instant message sending are performed entirely on
3 one or more client systems.
32. The method of claim 19 wherein the detecting and the automatic instant message sending are distributed among one or more server systems and one or more client systems.
33. A computer-implemented method of monitoring users of a computer network, the method comprising: receiving from a monitoring user a request to monitor availability of a monitored user; detecting that the monitored user is available; and automatically performing a predefined operation specified by the monitoring user upon detecting that the monitored user is available.
34. The method of claim 33 wherein performing the predefined operation comprises sending an instant message to the monitored user.
35. The method of claim 33 wherein performing the predefined operation comprises executing an operating system command, a script, or an executable file specified by the monitoring user.
36. The method of claim 33 wherein performing the predefined operation comprises providing a notification that the monitoring user is available.
37. The method of claim 36 wherein the notification is provided to the monitoring user.
38. The method of claim 36 wherein the notification is provided to an entity other than the monitoring user.
39. The method of claim 33 wherein the receiving, detecting and automatically performing a predefined operation are performed entirely on one or more server systems.
40. The method of claim 33 wherein the receiving, detecting and automatically performing a predefined operation are performed entirely on one or more client systems.
41. The method of claim 33 wherein the receiving, detecting and automatically performing a predefined operation are distributed among one or more server systems and one or more client systems.
42. A computer-implemented method of communicating with a user on a computer network comprising a plurality of clients and at least one server, the method comprising at the server: receiving a request to detect when a currently unavailable user becomes available to receive messages; detecting that the user has become available; and automatically sending a predetermined message to the user upon detecting that the user has become available.
43. A computer-implemented method of communicating with a user on a computer network comprising a plurality of clients and at least one server, the method comprising at a client: generating a request to detect when a currently unavailable user becomes available to receive messages; receiving notice that the user has become available; and automatically sending a predetermined message to the user .
i
44. An instant messaging system comprising:
1 a server system comprising software instructions for (i)
2 monitoring a targeted user's availability to receive instant
3 messages, and (ii) sending a notification that a targeted user
4 has become available to receive instant messages; and
5 one or more client systems in communication with the
6 server system, each client system being associated with a
7 targeting user and comprising software instructions for (i)
8 queuing a request to send an instant message to a currently
9 unavailable targeted user, and (ii) sending the instant message 0 to the targeted user upon receiving notification from the server i system that the targeted user has become available to receive 2 instant messages.
1 45. Computer software, tangibly embodied on a computer-
2 readable medium or in a propagated carrier signal, for
3 communicating with a user of an instant messaging system, the
4 software comprising instructions to cause a computer system to
5 perform the following operations:
1 (a) detect that a previously unavailable user has become
2 available to receive instant messages; and
3 (b) automatically send a predetermined instant message
4 to the user upon detecting that the user has become available.
1 46. The computer software of claim 45 wherein the
2 software to perform operations (a) and (b) resides entirely on
3 one or more server systems .
1 47. The computer software of claim 45 wherein the
2 software to perform operations (a) and (b) resides entirely on
3 one or more client systems.
1
48. The computer software of claim 45 wherein the software to perform operations (a) and (b) is distributed among one or more server systems and one or more client systems.
PCT/US2000/025507 1999-09-21 2000-09-18 Monitoring users of a computer network WO2001022258A2 (en)

Priority Applications (4)

Application Number Priority Date Filing Date Title
CA002385436A CA2385436A1 (en) 1999-09-21 2000-09-18 Monitoring users of a computer network
JP2001525552A JP2003510687A (en) 1999-09-21 2000-09-18 Computer network user monitoring
AU74960/00A AU7496000A (en) 1999-09-21 2000-09-18 Monitoring users of a computer network
EP00963566A EP1214826A2 (en) 1999-09-21 2000-09-18 Monitoring users of a computer network

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US09/399,750 1999-09-21
US09/399,750 US6691162B1 (en) 1999-09-21 1999-09-21 Monitoring users of a computer network

Publications (2)

Publication Number Publication Date
WO2001022258A2 true WO2001022258A2 (en) 2001-03-29
WO2001022258A3 WO2001022258A3 (en) 2001-10-04

Family

ID=23580808

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2000/025507 WO2001022258A2 (en) 1999-09-21 2000-09-18 Monitoring users of a computer network

Country Status (6)

Country Link
US (2) US6691162B1 (en)
EP (1) EP1214826A2 (en)
JP (1) JP2003510687A (en)
AU (1) AU7496000A (en)
CA (1) CA2385436A1 (en)
WO (1) WO2001022258A2 (en)

Cited By (32)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2004079929A3 (en) * 2003-03-03 2005-10-06 America Online Inc Source audio identifiers for digital communications
CN1299219C (en) * 2002-05-01 2007-02-07 摩托罗拉公司 Instant message communication system for providing notification of one or more events and method therefor
US7269627B2 (en) 2001-07-27 2007-09-11 Intel Corporation Routing messages using presence information
WO2008133685A1 (en) * 2007-04-27 2008-11-06 Hewlett-Packard Development Company, L.P. Time-shifted telepresence system and method
US7512652B1 (en) 2001-09-28 2009-03-31 Aol Llc, A Delaware Limited Liability Company Passive personalization of buddy lists
US7644166B2 (en) 2003-03-03 2010-01-05 Aol Llc Source audio identifiers for digital communications
US7672439B2 (en) 2003-04-02 2010-03-02 Aol Inc. Concatenated audio messages
US7945674B2 (en) 2003-04-02 2011-05-17 Aol Inc. Degrees of separation for handling communications
US7949759B2 (en) 2003-04-02 2011-05-24 AOL, Inc. Degrees of separation for handling communications
US8037150B2 (en) 2002-11-21 2011-10-11 Aol Inc. System and methods for providing multiple personas in a communications environment
US8060566B2 (en) 2004-12-01 2011-11-15 Aol Inc. Automatically enabling the forwarding of instant messages
US8250144B2 (en) 2002-11-21 2012-08-21 Blattner Patrick D Multiple avatar personalities
US8595146B1 (en) 2004-03-15 2013-11-26 Aol Inc. Social networking permissions
US9043418B2 (en) 2000-05-04 2015-05-26 Facebook, Inc. Systems and methods for instant messaging persons referenced in an electronic message
US9049159B2 (en) 2000-03-17 2015-06-02 Facebook, Inc. Establishing audio communication sessions
US9049160B2 (en) 2005-05-11 2015-06-02 Facebook, Inc. Identifying users sharing common characteristics
US9049569B2 (en) 2004-12-01 2015-06-02 Google Inc. Prohibiting mobile forwarding
US9071725B2 (en) 2000-07-25 2015-06-30 Facebook, Inc. Methods and user interfaces for video messaging
US9088879B2 (en) 2004-12-01 2015-07-21 Google Inc. Automatically enabling the forwarding of instant messages
US9100221B2 (en) 2000-05-04 2015-08-04 Facebook, Inc. Systems for messaging senders and recipients of an electronic message
US9461950B2 (en) 2000-05-04 2016-10-04 Facebook, Inc. Providing supplemental contact information corresponding to a referenced individual
US9619575B2 (en) 1999-12-01 2017-04-11 Facebook, Inc. System and method for analyzing communications
US9628431B2 (en) 2000-06-26 2017-04-18 Facebook, Inc. E-mail integrated instant messaging
US9652809B1 (en) 2004-12-21 2017-05-16 Aol Inc. Using user profile information to determine an avatar and/or avatar characteristics
US9705996B2 (en) 2008-08-28 2017-07-11 Aol Inc. Methods and system for providing location-based communication services
US9727631B2 (en) 2004-12-20 2017-08-08 Facebook, Inc. Automatic categorization of entries in a contact list
US9736255B2 (en) 2003-03-26 2017-08-15 Facebook, Inc. Methods of providing access to messages based on degrees of separation
US10341289B2 (en) 2004-03-05 2019-07-02 Facebook, Inc. Systems and methods of calculating communications strengths
US10504266B2 (en) 2003-03-03 2019-12-10 Microsoft Technology Licensing, Llc Reactive avatars
US10616367B2 (en) 2003-03-03 2020-04-07 Microsoft Technology Licensing, Llc Modifying avatar behavior based on user action or mood
US10708202B2 (en) 2003-09-19 2020-07-07 Blackberry Limited Handheld electronic device and associated method providing time data in a messaging environment
USRE48102E1 (en) 2002-12-31 2020-07-14 Facebook, Inc. Implicit population of access control lists

Families Citing this family (155)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020065894A1 (en) * 1999-12-03 2002-05-30 Dalal Siddhartha R. Local presence state and user-controlled presence and message forwarding in unified instant messaging
US6760754B1 (en) * 2000-02-22 2004-07-06 At&T Corp. System, method and apparatus for communicating via sound messages and personal sound identifiers
US7043530B2 (en) * 2000-02-22 2006-05-09 At&T Corp. System, method and apparatus for communicating via instant messaging
US6651086B1 (en) * 2000-02-22 2003-11-18 Yahoo! Inc. Systems and methods for matching participants to a conversation
US8335994B2 (en) * 2000-02-25 2012-12-18 Salmon Alagnak Llc Method and apparatus for providing content to a computing device
US6978293B1 (en) * 2000-02-29 2005-12-20 Microsoft Corporation Methods and systems for selecting criteria for a successful acknowledgement message in instant messaging
US7240093B1 (en) * 2000-02-29 2007-07-03 Microsoft Corporation Use of online messaging to facilitate selection of participants in game play
US9736209B2 (en) 2000-03-17 2017-08-15 Facebook, Inc. State change alerts mechanism
US7624172B1 (en) * 2000-03-17 2009-11-24 Aol Llc State change alerts mechanism
US7392306B1 (en) * 2000-04-07 2008-06-24 Aol Llc Instant messaging client having an embedded browser
US8122363B1 (en) 2000-05-04 2012-02-21 Aol Inc. Presence status indicator
US8132110B1 (en) 2000-05-04 2012-03-06 Aol Inc. Intelligently enabled menu choices based on online presence state in address book
US9356894B2 (en) 2000-05-04 2016-05-31 Facebook, Inc. Enabled and disabled menu choices based on presence state
US6912564B1 (en) 2000-05-04 2005-06-28 America Online, Inc. System for instant messaging the sender and recipients of an e-mail message
US6728754B1 (en) * 2000-05-09 2004-04-27 Sbc Properties, Lp Method, system, and article for telephone notification of an online status of a user
US20020049709A1 (en) * 2000-05-10 2002-04-25 Takashi Miyasaki Status information sharing system and user terminal device for sharing status information of user handling plurality of user terminal devices, and server device for managing user terminal devices, as well as control method thereof and storage medium storing program for method
US6920478B2 (en) * 2000-05-11 2005-07-19 Chikka Pte Ltd. Method and system for tracking the online status of active users of an internet-based instant messaging system
US7056217B1 (en) 2000-05-31 2006-06-06 Nintendo Co., Ltd. Messaging service for video game systems with buddy list that displays game being played
AU2000259848A1 (en) * 2000-07-13 2002-01-30 Nokia Corporation Method and system providing a messaging service
US7146404B2 (en) * 2000-08-22 2006-12-05 Colloquis, Inc. Method for performing authenticated access to a service on behalf of a user
US6430602B1 (en) * 2000-08-22 2002-08-06 Active Buddy, Inc. Method and system for interactively responding to instant messaging requests
US7673241B2 (en) * 2002-06-26 2010-03-02 Siebel Systems, Inc. User interface for multi-media communication for the visually disabled
US7606864B2 (en) * 2000-11-10 2009-10-20 At&T Intellectual Property I, L.P. Setting and display of communication receipt preferences by users of multiple communication devices
US7020686B2 (en) * 2000-12-29 2006-03-28 International Business Machines Corporation Method and system for providing synchronous communication and person awareness in a place
US7174453B2 (en) * 2000-12-29 2007-02-06 America Online, Inc. Message screening system
US20020143869A1 (en) * 2001-01-03 2002-10-03 Hal Cohen Method and apparatus for making random introductions electronically
US7581230B2 (en) * 2001-02-06 2009-08-25 Siebel Systems, Inc. Adaptive communication application programming interface
JP2002271561A (en) * 2001-03-13 2002-09-20 Minolta Co Ltd Data transmitter, data receiver, data transmitting/ receiving system, data transmitting method, data receiving method, data transmitting/receiving method, program and recording medium
US20030206192A1 (en) * 2001-03-31 2003-11-06 Mingte Chen Asynchronous message push to web browser
US20070203797A1 (en) * 2001-03-31 2007-08-30 Annadata Anil K Configurable media-independent server
US7730204B2 (en) * 2001-03-31 2010-06-01 Siebel Systems, Inc. Extensible interface for inter-module communication
US8601492B2 (en) * 2001-03-31 2013-12-03 Siebel Systems, Inc. User interface for multi-channel communication
US20030018705A1 (en) * 2001-03-31 2003-01-23 Mingte Chen Media-independent communication server
US7315616B2 (en) * 2001-03-31 2008-01-01 Siebel Systems, Inc. System and method for maintaining real-time agent information for multi-channel communication queuing
US6907447B1 (en) * 2001-04-30 2005-06-14 Microsoft Corporation Method and apparatus for providing an instant message notification
US8315651B2 (en) * 2001-05-03 2012-11-20 Kyocera Corporation Instant messaging to a mobile device
US20020178227A1 (en) * 2001-05-25 2002-11-28 International Business Machines Corporation Routing instant messages using configurable, pluggable delivery managers
US6983305B2 (en) * 2001-05-30 2006-01-03 Microsoft Corporation Systems and methods for interfacing with a user in instant messaging
US20030009570A1 (en) * 2001-07-03 2003-01-09 International Business Machines Corporation Method and apparatus for segmented peer-to-peer computing
US7346658B2 (en) * 2001-08-08 2008-03-18 At&T Delaware Intellectual Property, Inc. System and method for notifying an offline global computer network user of an online interaction
US7349700B1 (en) 2001-08-30 2008-03-25 Aol Llc Communication system and method
US7062533B2 (en) * 2001-09-20 2006-06-13 International Business Machines Corporation Specifying monitored user participation in messaging sessions
US7765484B2 (en) * 2001-09-28 2010-07-27 Aol Inc. Passive personalization of lists
US20030078979A1 (en) * 2001-10-22 2003-04-24 Motorola, Inc. Method and apparatus for controlling an intelligent device through an instant messaging protocol over a communication network
US7870228B2 (en) 2001-10-26 2011-01-11 Research In Motion Limited System and method for remotely controlling mobile communication devices
US8091042B2 (en) 2001-11-15 2012-01-03 Siebel Systems, Inc. Apparatus and method for displaying selectable icons in a toolbar for a user interface
US7032007B2 (en) * 2001-12-05 2006-04-18 International Business Machines Corporation Apparatus and method for monitoring instant messaging accounts
US7194536B2 (en) * 2001-12-05 2007-03-20 International Business Machines Corporation Apparatus and method for monitoring and analyzing instant messaging account transcripts
JP3574106B2 (en) * 2001-12-14 2004-10-06 株式会社スクウェア・エニックス Network game system, game server device, video game device, message transmission method and display control method in network game, program, and recording medium
SE519854C2 (en) * 2002-02-15 2003-04-15 Hotsip Ab A procedure for distributing information
US7343365B2 (en) * 2002-02-20 2008-03-11 Microsoft Corporation Computer system architecture for automatic context associations
US7167910B2 (en) * 2002-02-20 2007-01-23 Microsoft Corporation Social mapping of contacts from computer communication information
US20030163525A1 (en) * 2002-02-22 2003-08-28 International Business Machines Corporation Ink instant messaging with active message annotation
US20030182391A1 (en) * 2002-03-19 2003-09-25 Mike Leber Internet based personal information manager
US7353455B2 (en) * 2002-05-21 2008-04-01 At&T Delaware Intellectual Property, Inc. Caller initiated distinctive presence alerting and auto-response messaging
WO2003105009A1 (en) * 2002-06-07 2003-12-18 Bellsouth Intellectual Property Corporation Sytems and methods for establishing electronic conferencing over a distributed network
US7464139B2 (en) * 2002-06-07 2008-12-09 At&T Intellectual Property, I, L.P. Methods for establishing an instant message conference
JP3980421B2 (en) * 2002-06-27 2007-09-26 富士通株式会社 Presence management method and apparatus
US20040024767A1 (en) * 2002-07-31 2004-02-05 Dexing Chen Method and system for managing event information in a computer network
US6891934B1 (en) * 2002-08-20 2005-05-10 Bellsouth Intellectual Property Corporation IP handset-based voice mail notification
US20040093401A1 (en) * 2002-11-13 2004-05-13 International Business Machines Corporation Client-server text messaging monitoring for remote computer management
US8122137B2 (en) 2002-11-18 2012-02-21 Aol Inc. Dynamic location of a subordinate user
US8701014B1 (en) 2002-11-18 2014-04-15 Facebook, Inc. Account linking
US7428580B2 (en) 2003-11-26 2008-09-23 Aol Llc Electronic message forwarding
CA2506585A1 (en) 2002-11-18 2004-06-03 Valerie Kucharewski People lists
US8965964B1 (en) 2002-11-18 2015-02-24 Facebook, Inc. Managing forwarded electronic messages
US7899862B2 (en) 2002-11-18 2011-03-01 Aol Inc. Dynamic identification of other users to an online user
US8005919B2 (en) 2002-11-18 2011-08-23 Aol Inc. Host-based intelligent results related to a character stream
US7590696B1 (en) 2002-11-18 2009-09-15 Aol Llc Enhanced buddy list using mobile device identifiers
US7640306B2 (en) 2002-11-18 2009-12-29 Aol Llc Reconfiguring an electronic message to effect an enhanced notification
US20040162878A1 (en) 2002-11-22 2004-08-19 Lewis Michael Pescatello System and method to facilitate real-time communications and content sharing among users over a network
US20040128391A1 (en) * 2002-12-31 2004-07-01 Robert Patzer Method and system for managing a validity period in association with a presence attribute
US8204938B2 (en) * 2003-02-14 2012-06-19 Devereux Research Ab Llc System and method for immediate and delayed real-time communication activities using availability data from and communications through an external instant messaging system
US7263545B2 (en) * 2003-02-14 2007-08-28 Convoq, Inc. System and method for immediate and delayed real-time communication activities using availability data from and communications through an external instant messaging system
US7360164B2 (en) * 2003-03-03 2008-04-15 Sap Ag Collaboration launchpad
US7769811B2 (en) 2003-03-03 2010-08-03 Aol Llc Instant messaging sound control
US7913176B1 (en) * 2003-03-03 2011-03-22 Aol Inc. Applying access controls to communications with avatars
US20040186766A1 (en) * 2003-03-19 2004-09-23 International Business Machines Corporation Apparatus and method for marketing to instant messaging service users
US20040189698A1 (en) * 2003-03-26 2004-09-30 Nortel Networks Limited Instant messaging to service bureau
US7653693B2 (en) 2003-09-05 2010-01-26 Aol Llc Method and system for capturing instant messages
US20050027839A1 (en) * 2003-07-31 2005-02-03 International Business Machiness Corporation Method, system and program product for dynamic transmission in a messaging session
US7912903B2 (en) * 2003-09-25 2011-03-22 Oracle America, Inc. Method and system for processing instant messenger operations dependent upon presence state information in an instant messaging system
US20050138062A1 (en) * 2003-11-28 2005-06-23 Infineon Technologies Ag Method, computer program, apparatus and system for the selective communication of data sets
US20050125496A1 (en) * 2003-12-03 2005-06-09 International Business Machines Corporation Automatically initiating an instant messaging action when a subscriber's availability status changes
US7493567B2 (en) * 2004-01-28 2009-02-17 Microsoft Corporation Method and system for pinning contacts and items
US20050289017A1 (en) * 2004-05-19 2005-12-29 Efraim Gershom Network transaction system and method
US20060047816A1 (en) * 2004-06-17 2006-03-02 International Business Machines Corporation Method and apparatus for generating and distributing meeting minutes from an instant messaging session
US8099395B2 (en) 2004-06-24 2012-01-17 Oracle America, Inc. System level identity object
US7797293B2 (en) * 2004-06-24 2010-09-14 Oracle America, Inc. Adaptive contact list
US8640035B2 (en) * 2004-06-24 2014-01-28 Oracle America, Inc. Identity based user interface
US7921163B1 (en) 2004-07-02 2011-04-05 Aol Inc. Routing and displaying messages for multiple concurrent instant messaging sessions involving a single online identity
US7836126B2 (en) * 2004-08-04 2010-11-16 Sap Ag Business presence system and method
US20060036703A1 (en) * 2004-08-13 2006-02-16 Microsoft Corporation System and method for integrating instant messaging in a multimedia environment
US7412657B2 (en) * 2004-08-26 2008-08-12 International Business Machines Corporation Systems, methods, and media for updating an instant messaging system
US7818379B1 (en) 2004-08-31 2010-10-19 Aol Inc. Notification and disposition of multiple concurrent instant messaging sessions involving a single online identity
US20070005752A1 (en) * 2005-06-29 2007-01-04 Jitendra Chawla Methods and apparatuses for monitoring attention of a user during a collaboration session
US7945619B1 (en) * 2004-09-20 2011-05-17 Jitendra Chawla Methods and apparatuses for reporting based on attention of a user during a collaboration session
US8341531B2 (en) * 2004-09-30 2012-12-25 Microsoft Corporation Content formatting and installation techniques
US7542761B2 (en) * 2004-10-06 2009-06-02 At&T Mobility Ii Llc Voice quality on a communication link based on customer feedback
US20060101022A1 (en) * 2004-10-25 2006-05-11 Microsoft Corporation System and process for providing an interactive, computer network-based, virtual team worksite
US7756931B2 (en) * 2004-10-28 2010-07-13 International Business Machines Corporation Method and apparatus for manager/agent communications
US7669213B1 (en) 2004-10-28 2010-02-23 Aol Llc Dynamic identification of other viewers of a television program to an online viewer
US20060168204A1 (en) * 2004-12-01 2006-07-27 Barry Appelman Mobile blocking indicators on a contact list
US7665031B2 (en) * 2004-12-08 2010-02-16 Microsoft Corporation Method and system of taskbar button interfaces
US20060167991A1 (en) * 2004-12-16 2006-07-27 Heikes Brian D Buddy list filtering
US7356567B2 (en) 2004-12-30 2008-04-08 Aol Llc, A Delaware Limited Liability Company Managing instant messaging sessions on multiple devices
US7747685B2 (en) * 2005-01-20 2010-06-29 International Business Machines Corporation Method for automatic detection of display sharing and alert generation in instant messaging
US7818350B2 (en) 2005-02-28 2010-10-19 Yahoo! Inc. System and method for creating a collaborative playlist
US8316315B2 (en) 2005-02-28 2012-11-20 Microsoft Corporation Automatically generated highlight view of electronic interactions
US20060203975A1 (en) * 2005-03-10 2006-09-14 Avaya Technology Corp. Dynamic content stream delivery to a telecommunications terminal based on the state of the terminal's transducers
US7847813B2 (en) * 2005-03-10 2010-12-07 Avaya Inc. Dynamic multimedia content stream delivery based on quality of service
US7949106B2 (en) * 2005-03-10 2011-05-24 Avaya Inc. Asynchronous event handling for video streams in interactive voice response systems
US7711095B2 (en) * 2005-03-10 2010-05-04 Avaya Inc. Coordination of content streams in interactive voice response systems
US20060210034A1 (en) * 2005-03-17 2006-09-21 Beadle Bruce A Enabling a user to store a messaging session entry for delivery when an intended recipient is next available
US7606580B2 (en) * 2005-05-11 2009-10-20 Aol Llc Personalized location information for mobile devices
US20070162862A1 (en) * 2005-07-06 2007-07-12 Gemini Mobile Technologies, Inc. Selective user monitoring in an online environment
FR2888706A1 (en) * 2005-07-12 2007-01-19 France Telecom METHOD FOR INTERPERSONAL RELATIONSHIP
US20070033607A1 (en) * 2005-08-08 2007-02-08 Bryan David A Presence and proximity responsive program display
WO2007047246A2 (en) * 2005-10-11 2007-04-26 Barry Appelman Enabling and exercising control over selected sounds associated with incoming communications
US20070124393A1 (en) * 2005-11-18 2007-05-31 Oracle International Corporation Presence based notifications
DE102006021376A1 (en) * 2006-05-08 2007-11-15 Combots Product Gmbh & Co. Kg A method and apparatus for providing customized communication windows for communicating with a communication partner in an application on a user's terminal
US8407670B2 (en) 2006-06-02 2013-03-26 Microsoft Corporation Collaborative code conflict detection, notification and resolution
US8780925B2 (en) * 2006-08-17 2014-07-15 Fonality, Inc. Mobile use of a PBX system
US20080052354A1 (en) * 2006-08-22 2008-02-28 International Business Machines Corporation Method of giving the invitee information on an instant messaging meeting prior to acceptance
US7861175B2 (en) 2006-09-29 2010-12-28 Research In Motion Limited IM contact list entry as a game in progress designate
WO2008058022A2 (en) * 2006-11-02 2008-05-15 Ripl Corp. User-generated content with instant-messaging functionality
US7694146B2 (en) * 2006-11-18 2010-04-06 3501256 Canada, Inc. Login security daemon
US20080183815A1 (en) * 2007-01-30 2008-07-31 Unger Assaf Page networking system and method
US8671146B2 (en) * 2007-02-28 2014-03-11 Microsoft Corporation Presence aware notification for information technology management
US8693659B2 (en) * 2007-03-09 2014-04-08 Fonality, Inc. System and method for centralized presence management of local and remote users
US8098810B2 (en) 2007-03-09 2012-01-17 Fonality, Inc. Intelligent presence management in a communication routing system
US8112720B2 (en) * 2007-04-05 2012-02-07 Napo Enterprises, Llc System and method for automatically and graphically associating programmatically-generated media item recommendations related to a user's socially recommended media items
US8379832B1 (en) 2007-05-03 2013-02-19 Fonality, Inc. Universal queuing for inbound communications
US7898394B2 (en) * 2007-05-10 2011-03-01 Red Hat, Inc. Systems and methods for community tagging
US8356048B2 (en) * 2007-05-31 2013-01-15 Red Hat, Inc. Systems and methods for improved forums
US8266127B2 (en) * 2007-05-31 2012-09-11 Red Hat, Inc. Systems and methods for directed forums
US7966319B2 (en) * 2007-06-07 2011-06-21 Red Hat, Inc. Systems and methods for a rating system
US10097695B2 (en) 2007-08-10 2018-10-09 Fonality, Inc. System and method for providing carrier-independent VoIP communication
US8037009B2 (en) * 2007-08-27 2011-10-11 Red Hat, Inc. Systems and methods for linking an issue with an entry in a knowledgebase
US20090172100A1 (en) * 2007-12-31 2009-07-02 International Business Machines Corporation Deriving and communicating attention spans in collaborative applications
US9412095B2 (en) 2008-01-09 2016-08-09 International Business Machines Corporation Status and time-based delivery services for instant messengers
US8214442B2 (en) * 2008-08-05 2012-07-03 International Business Machines Corporation Facilitating an extended IM session in a secure way
US8719386B2 (en) 2009-01-08 2014-05-06 Fonality, Inc. System and method for providing configuration synchronicity
US10318922B2 (en) 2009-03-16 2019-06-11 Fonality, Inc. System and method for automatic insertion of call intelligence in an information system
US9443244B2 (en) 2009-03-16 2016-09-13 Fonality, Inc. System and method for utilizing customer data in a communication system
US7958244B2 (en) * 2009-09-25 2011-06-07 International Business Machines Corporation Imposed policies for handling instant messages
US8959158B2 (en) * 2009-10-12 2015-02-17 International Business Machines Corporation Leveraging point-in-time knowledge to respond to e-mail
CA2718696C (en) 2010-06-08 2018-06-12 Merge Healthcare, Inc. Remote control of medical devices using instant messaging infrastructure
US8577974B2 (en) * 2010-07-07 2013-11-05 Oracle International Corporation Conference server simplifying management of subsequent meetings for participants of a meeting in progress
US11716392B2 (en) * 2013-04-24 2023-08-01 Blackberry Limited Updating an application at a second device based on received user input at a first device
US9417868B2 (en) * 2014-01-09 2016-08-16 Bank Of America Corporation Entity wide software tracking and maintenance reporting tool
WO2015164823A1 (en) 2014-04-25 2015-10-29 Fisher Timothy Isaac Messaging with drawn graphic input
US10471348B2 (en) 2015-07-24 2019-11-12 Activision Publishing, Inc. System and method for creating and sharing customized video game weapon configurations in multiplayer video games via one or more social networks
US11185784B2 (en) 2015-10-08 2021-11-30 Activision Publishing, Inc. System and method for generating personalized messaging campaigns for video game players
US10099140B2 (en) 2015-10-08 2018-10-16 Activision Publishing, Inc. System and method for generating personalized messaging campaigns for video game players

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5063523A (en) * 1989-11-16 1991-11-05 Racal Data Communications Inc. Network management system with event rule handling
WO1998016045A1 (en) * 1996-10-06 1998-04-16 Mirabilis Ltd. Communications system

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5828839A (en) * 1996-11-14 1998-10-27 Interactive Broadcaster Services Corp. Computer network chat room based on channel broadcast in real time
US6055570A (en) * 1997-04-03 2000-04-25 Sun Microsystems, Inc. Subscribed update monitors
US5943478A (en) * 1997-04-04 1999-08-24 Flash Communications, Inc. System for immediate popup messaging across the internet
US6260148B1 (en) * 1997-04-04 2001-07-10 Microsoft Corporation Methods and systems for message forwarding and property notifications using electronic subscriptions
US6339784B1 (en) * 1997-05-20 2002-01-15 America Online, Inc. Self-policing, rate limiting online forums
US5990887A (en) * 1997-10-30 1999-11-23 International Business Machines Corp. Method and system for efficient network desirable chat feedback over a communication network
US6148328A (en) * 1998-01-29 2000-11-14 International Business Machines Corp. Method and system for signaling presence of users in a networked environment
US6366962B1 (en) * 1998-12-18 2002-04-02 Intel Corporation Method and apparatus for a buddy list
US6301609B1 (en) * 1999-07-07 2001-10-09 Lucent Technologies Inc. Assignable associate priorities for user-definable instant messaging buddy groups

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5063523A (en) * 1989-11-16 1991-11-05 Racal Data Communications Inc. Network management system with event rule handling
WO1998016045A1 (en) * 1996-10-06 1998-04-16 Mirabilis Ltd. Communications system

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
"AWAY-MODE ACKNOWLEDGEMENT CALL BACK" IBM TECHNICAL DISCLOSURE BULLETIN,IBM CORP. NEW YORK,US, vol. 37, no. 4A, 1 April 1994 (1994-04-01), page 583 XP000446791 ISSN: 0018-8689 *
"MECHANISM TO FACILITATE SELECTIVE ACKNOWLEDGEMENT FOR OFFICE MAIL SERVICES" IBM TECHNICAL DISCLOSURE BULLETIN,IBM CORP. NEW YORK,US, vol. 36, no. 8, 1 August 1993 (1993-08-01), page 225 XP000390204 ISSN: 0018-8689 *
ESCHENBURG A: "WO LAUFEN SIE DENN? ICQ HAELT VERBINDUNG ZU BEKANNTEN" CT MAGAZIN FUER COMPUTER TECHNIK,DE,VERLAG HEINZ HEISE GMBH., HANNOVER, no. 22, 26 October 1998 (1998-10-26), pages 92-95, XP000779803 ISSN: 0724-8679 *
ICQ: "ICQ 99a, Online help" 1998 , ICQ INCORPORATED XP002163918 *

Cited By (58)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9819629B2 (en) 1999-12-01 2017-11-14 Facebook, Inc. System and method for analyzing communications
US9619575B2 (en) 1999-12-01 2017-04-11 Facebook, Inc. System and method for analyzing communications
US9705834B2 (en) 1999-12-01 2017-07-11 Facebook, Inc. System and method for analyzing communications
US9749276B2 (en) 1999-12-01 2017-08-29 Facebook, Inc. System and method for analyzing communications
US9749279B2 (en) 1999-12-01 2017-08-29 Facebook, Inc. System and method for analyzing communications
US9813370B2 (en) 1999-12-01 2017-11-07 Facebook, Inc. System and method for analyzing communications
US9049159B2 (en) 2000-03-17 2015-06-02 Facebook, Inc. Establishing audio communication sessions
US9621493B2 (en) 2000-05-04 2017-04-11 Facebook, Inc. Providing supplemental information corresponding to a referenced individual
US10122658B2 (en) 2000-05-04 2018-11-06 Facebook, Inc. System for instant messaging the sender and recipients of an e-mail message
US9100221B2 (en) 2000-05-04 2015-08-04 Facebook, Inc. Systems for messaging senders and recipients of an electronic message
US10158588B2 (en) 2000-05-04 2018-12-18 Facebook, Inc. Providing supplemental contact information corresponding to a referenced individual
US9043418B2 (en) 2000-05-04 2015-05-26 Facebook, Inc. Systems and methods for instant messaging persons referenced in an electronic message
US9461950B2 (en) 2000-05-04 2016-10-04 Facebook, Inc. Providing supplemental contact information corresponding to a referenced individual
US9699122B2 (en) 2000-05-04 2017-07-04 Facebook, Inc. User interfaces for providing supplemental contact information corresponding to a referenced individual
US9628431B2 (en) 2000-06-26 2017-04-18 Facebook, Inc. E-mail integrated instant messaging
US10313297B2 (en) 2000-06-26 2019-06-04 Facebook, Inc. E-mail integrated instant messaging
US9071725B2 (en) 2000-07-25 2015-06-30 Facebook, Inc. Methods and user interfaces for video messaging
US7269627B2 (en) 2001-07-27 2007-09-11 Intel Corporation Routing messages using presence information
US9729476B2 (en) 2001-09-28 2017-08-08 Facebook, Inc. Personalization of recent contacts list
US7512652B1 (en) 2001-09-28 2009-03-31 Aol Llc, A Delaware Limited Liability Company Passive personalization of buddy lists
US9083661B2 (en) 2001-09-28 2015-07-14 Facebook, Inc. Passive personalization of buddy lists
CN1299219C (en) * 2002-05-01 2007-02-07 摩托罗拉公司 Instant message communication system for providing notification of one or more events and method therefor
US8250144B2 (en) 2002-11-21 2012-08-21 Blattner Patrick D Multiple avatar personalities
US10291556B2 (en) 2002-11-21 2019-05-14 Microsoft Technology Licensing, Llc Multiple personalities
US8037150B2 (en) 2002-11-21 2011-10-11 Aol Inc. System and methods for providing multiple personas in a communications environment
US9807130B2 (en) 2002-11-21 2017-10-31 Microsoft Technology Licensing, Llc Multiple avatar personalities
US9215095B2 (en) 2002-11-21 2015-12-15 Microsoft Technology Licensing, Llc Multiple personalities
USRE48102E1 (en) 2002-12-31 2020-07-14 Facebook, Inc. Implicit population of access control lists
US9178992B2 (en) 2003-03-03 2015-11-03 Facebook, Inc. User interface for selecting audio identifiers for digital communications
KR100749456B1 (en) * 2003-03-03 2007-08-14 에이오엘 엘엘씨 Source Audio Identifiers for Digital Communications
US8577977B2 (en) 2003-03-03 2013-11-05 Facebook, Inc. Recipient control of source audio identifiers for digital communications
WO2004079929A3 (en) * 2003-03-03 2005-10-06 America Online Inc Source audio identifiers for digital communications
US10504266B2 (en) 2003-03-03 2019-12-10 Microsoft Technology Licensing, Llc Reactive avatars
US7644166B2 (en) 2003-03-03 2010-01-05 Aol Llc Source audio identifiers for digital communications
US10616367B2 (en) 2003-03-03 2020-04-07 Microsoft Technology Licensing, Llc Modifying avatar behavior based on user action or mood
US7987236B2 (en) 2003-03-03 2011-07-26 Aol Inc. Recipient control of source audio identifiers for digital communications
US7693944B2 (en) 2003-03-03 2010-04-06 Aol Inc. Recipient control of source audio identifiers for digital communications
US9736255B2 (en) 2003-03-26 2017-08-15 Facebook, Inc. Methods of providing access to messages based on degrees of separation
US7945674B2 (en) 2003-04-02 2011-05-17 Aol Inc. Degrees of separation for handling communications
US7924996B2 (en) 2003-04-02 2011-04-12 Aol Inc. Concatenated audio messages
US7949759B2 (en) 2003-04-02 2011-05-24 AOL, Inc. Degrees of separation for handling communications
US7672439B2 (en) 2003-04-02 2010-03-02 Aol Inc. Concatenated audio messages
US10735353B2 (en) 2003-09-19 2020-08-04 Blackberry Limited Handheld electronic device and associated method providing time data in a messaging environment
US10708202B2 (en) 2003-09-19 2020-07-07 Blackberry Limited Handheld electronic device and associated method providing time data in a messaging environment
US11888601B2 (en) 2003-09-19 2024-01-30 Blackberry Limited User interface for messaging communications on an electronic device
US10341289B2 (en) 2004-03-05 2019-07-02 Facebook, Inc. Systems and methods of calculating communications strengths
US10367860B2 (en) 2004-03-15 2019-07-30 Oath Inc. Social networking permissions
US8595146B1 (en) 2004-03-15 2013-11-26 Aol Inc. Social networking permissions
US9872157B2 (en) 2004-12-01 2018-01-16 Google Inc. Prohibiting mobile forwarding
US8060566B2 (en) 2004-12-01 2011-11-15 Aol Inc. Automatically enabling the forwarding of instant messages
US9615225B2 (en) 2004-12-01 2017-04-04 Google Inc. Automatically enabling the forwarding of instant messages
US9088879B2 (en) 2004-12-01 2015-07-21 Google Inc. Automatically enabling the forwarding of instant messages
US9049569B2 (en) 2004-12-01 2015-06-02 Google Inc. Prohibiting mobile forwarding
US9727631B2 (en) 2004-12-20 2017-08-08 Facebook, Inc. Automatic categorization of entries in a contact list
US9652809B1 (en) 2004-12-21 2017-05-16 Aol Inc. Using user profile information to determine an avatar and/or avatar characteristics
US9049160B2 (en) 2005-05-11 2015-06-02 Facebook, Inc. Identifying users sharing common characteristics
WO2008133685A1 (en) * 2007-04-27 2008-11-06 Hewlett-Packard Development Company, L.P. Time-shifted telepresence system and method
US9705996B2 (en) 2008-08-28 2017-07-11 Aol Inc. Methods and system for providing location-based communication services

Also Published As

Publication number Publication date
EP1214826A2 (en) 2002-06-19
US20040093387A1 (en) 2004-05-13
JP2003510687A (en) 2003-03-18
WO2001022258A3 (en) 2001-10-04
US6691162B1 (en) 2004-02-10
AU7496000A (en) 2001-04-24
CA2385436A1 (en) 2001-03-29

Similar Documents

Publication Publication Date Title
US6691162B1 (en) Monitoring users of a computer network
US11349786B2 (en) Instant messaging communication system and method
US7689649B2 (en) Rendering destination instant messaging personalization items before communicating with destination
US11095582B2 (en) Systems and methods for supplementing real-time exchanges of instant messages with automatically updateable content
US8332540B2 (en) Processing event notifications with an event sink
JP6501919B2 (en) Voice chat mode self-adaptation method and apparatus
US6539421B1 (en) Messaging application user interface
US7937714B2 (en) Processing event notifications with an event sink
US20070033254A1 (en) Sharing skins
US20080034038A1 (en) Sharing Application Output In Chat Environment
US20130080927A1 (en) Multiple personalities in chat communications
US20070005704A1 (en) Multi-participant online activities
EP1560363A1 (en) Instant message mass update generated from website
JP7412490B2 (en) Computer programs and electronic devices that generate, process, and manage messages and corresponding tasks
WO2004079310A2 (en) Instant messaging sound control
WO2003102799A1 (en) Sending instant messaging customization items
US20080034037A1 (en) Sharing Graphical User Interface Output In Chat Environment
US20080153464A1 (en) Methods and systems for indicating the occurrence of an event
JP2018181314A (en) Data transmitting/receiving method and system
US20060195363A1 (en) Persistent object for online activities
US20090113015A1 (en) Remote Application Processing System
JP2001265671A (en) Mailing list service system, mailing list service method, recording medium and advertisement service method

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A2

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

AL Designated countries for regional patents

Kind code of ref document: A2

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

121 Ep: the epo has been informed by wipo that ep was designated in this application
DFPE Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)
AK Designated states

Kind code of ref document: A3

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

AL Designated countries for regional patents

Kind code of ref document: A3

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

WWE Wipo information: entry into national phase

Ref document number: 2385436

Country of ref document: CA

ENP Entry into the national phase

Ref country code: JP

Ref document number: 2001 525552

Kind code of ref document: A

Format of ref document f/p: F

WWE Wipo information: entry into national phase

Ref document number: 2000963566

Country of ref document: EP

WWP Wipo information: published in national office

Ref document number: 2000963566

Country of ref document: EP

WWW Wipo information: withdrawn in national office

Ref document number: 2000963566

Country of ref document: EP