Personalization of recent contacts list

Description

TECHNICAL FIELD

The following description relates generally to passively personalizing a user interface, such as an instant messaging user interface.

BACKGROUND

Online service providers offer new services and upgrade existing services to enhance their subscribers' online experience. Subscribers have on-demand access to news, weather, financial, sports, and entertainment services, and have the ability to transmit electronic messages and to participate in online discussion groups. For example, subscribers of online service providers such as America Online or CompuServe may view and retrieve proprietary or third party content on a wide variety of topics from servers located throughout the world.

One such service is instant messaging. Members of an instant messaging service can communicate virtually in real time with other instant messaging members. Members may manually create a list of screen names for other members, and may establish instant messaging sessions with those other members using a list of screen names, which also may be referred to as a buddy list.

SUMMARY

In one general aspect, personalizing communications for a first communication platform, such as instant messaging, includes accessing status information for communication sessions by a communication identity that leverage a first communication platform other than an instant messaging platform. A participant list associated with the communication identity and the first communication platform is passively configured to persistently reflect a list of participant identities from communication sessions in which the communication identity recently participated using the communication platform.

Implementations may include one or more of the following features. For example, the participant list may be configured without action from the communication identity. The list of participant identities from communication in which the communication identity recently participated may be maintained persistently beyond logout of the communication identity. The participant identities may be maintained on the list after a communication session between the participant identity and the communication identity is terminated.

The first communication platform may include electronic mail platform, an electronic chat platform, a voice-over-IP telephony platform, and/or a telephony platform. An electronic mail participant list, an electronic chat participant list, a voice-over-IP participant list, and/or a telephony participant list may be passively configured. The participant list associated with the communication identity and the communication platform may be passively configured. A buddy group may be passively configured.

The participant list may include contact information for at least one of the participant identities that may be used to enable a communication session with at least one participant identity using the first communication platform and/or a second communication platform. The second communication platform may include an instant message platform. In one implementation, the first communication platform may include on of an electronic mail platform, an electronic chat platform, a voice-over-IP telephony platform, and a telephony platform, and the second communication platform may include a different one of the electronic mail platform, the electronic chat platform, the voice-over-IP telephony platform, and the telephony platform.

In one implementation, the participant identities may be maintained on the list independent of a device or devices used for the communication sessions during which the list was created such that the participant list is accessible from one or more different devices. The participant list may be stored on a remote device accessible to one or more different devices.

In one implementation, a participant identity may be added to the participant list only when a communication session with the participant identity is closed. Additionally or alternatively, a participant identity may be added to the participant list only when a communication session with the participant identity is closed and the participant identity is not already included in the participant list. The participant identity may be listed as the most recently closed on the list.

In another implementation, participant identity may be added to the participant list when a communication session with the participant identity is established. Additionally or alternatively, a participant identity may be added to the participant list when a communication session with the participant identity is established and the participant identity is not already included in the participant list.

The participant list of communication sessions in which the communication identity recently participated may be limited to participant identities not otherwise included on any other list for the communication identity. The participant list may be configured to exclude participant identities from which a communication is received but not accepted. The participant list may include participant identities that are included on at least one other list for the communication identity.

The size of the participant list may be limited. A size of the participant list may be established based on a selection by the communication identity, and may be initially established based on a default value. The participant list may be sequenced using a least-recently-used methodology. Additionally or alternatively, the participant list may be sequenced using a first-in first-out methodology.

Participant identities may be arranged on the participant list such that a most recent participant identity is listed first. Participant identities may be arranged on the participant list such that a least-recently-used screen name is omitted whether or not the least recently used screen name was first-in on the list of participant identities.

The passively-configured participant list may be displayed. An online status may be displayed for each participant identity in the participant list.

A log associated with the communication identity may be updated. The log may include a chronological record of communication activity. In one implementation, the participant list may be based on the updated log. Updating the log may include deriving and recording a screen name of a participant identity. Updating the log also may include recording a time when a communication session is established.

These general and specific aspects may be implemented using a system, a method, or a computer program, or any combination of systems, methods, and computer programs.

Other features will be apparent from the description and drawings, and from the claims.

DESCRIPTION OF DRAWINGS

FIG. 1 is a block diagram of a communications system.

FIGS. 2-5 are expansions of the block diagram of FIG. 1.

FIG. 6 is a flow chart of a communications method implemented by the communications system of FIGS. 1-5.

FIGS. 7-10 are user interfaces that may be displayed by the communications system of FIGS. 1-5.

FIG. 11 is a flow chart of a communications method implemented by the communications system of FIGS. 1-5.

FIG. 12 is a flow chart of a communications method implemented by the communications system of FIGS. 1-5.

FIGS. 13a, 13b, and 14 are user interfaces that may be displayed by the communications system of FIGS. 1-5.

DETAILED DESCRIPTION

For illustrative purposes, FIGS. 1-5 show an example of a communications system for implementing techniques for transferring electronic data. For brevity, several elements in the figures described below are represented as monolithic entities. However, as would be understood by one skilled in the art, these elements each may include numerous interconnected computers and components designed to perform a set of specified operations and/or may be dedicated to a particular geographical region.

Referring to FIG. 1, a communications system 100 is capable of delivering and exchanging data between a client system 105 and a host system 110 through a communications link 115. The client system 105 typically includes one or more client devices 120 and/or client controllers 125, and the host system 110 typically includes one or more host devices 135 and/or host controllers 140. For example, the client system 105 or the host system 110 may include one or more general-purpose computers (e.g., personal computers), one or more special-purpose computers (e.g., devices specifically programmed to communicate with each other and/or the client system 105 or the host system 110), or a combination of one or more general-purpose computers and one or more special-purpose computers. The client system 105 and the host system 110 may be arranged to operate within or in concert with one or more other systems, such as, for example, one or more LANs (“Local Area Networks”) and/or one or more WANs (“Wide Area Networks”).

The client device 120 (or the host device 135) is generally capable of executing instructions under the command of a client controller 125 (or a host controller 140). The client device 120 (or the host device 135) is connected to the client controller 125 (or the host controller 140) by a wired or wireless data pathway 130 or 145 capable of delivering data.

The client device 120, the client controller 125, the host device 135, and the host controller 140 each typically include one or more hardware components and/or software components. An example of a client device 120 or a host device 135 is a general-purpose computer (e.g., a personal computer) capable of responding to and executing instructions in a defined manner. Other examples include a special-purpose computer, a workstation, a server, a device, a component, other physical or virtual equipment or some combination thereof capable of responding to and executing instructions. The client device 120 and the host device 135 may include devices that are capable of peer-to-peer communications.

An example of a client controller 125 or a host controller 140 is a software application loaded on the client device 120 or the host device 135 for commanding and directing communications enabled by the client device 120 or the host device 135. Other examples include a program, a piece of code, an instruction, a device, a computer, a computer system, or a combination thereof, for independently or collectively instructing the client device 120 or the host device 135 to interact and operate as described. The client controller 125 and the host controller 140 may be embodied permanently or temporarily in any type of machine, component, physical or virtual equipment, storage medium, or propagated signal capable of providing instructions to the client device 120 or the host device 135.

The communications link 115 typically includes a delivery network 160 making a direct or indirect communication between the client system 105 and the host system 110, irrespective of physical separation. Examples of a delivery network 160 include the Internet, the World Wide Web, WANs, LANs, analog or digital wired and wireless telephone networks (e.g. PSTN, ISDN, and xDSL), radio, television, cable, satellite, and/or any other delivery mechanism for carrying data. The communications link 115 may include communication pathways 150 and 155 that enable communications through the one or more delivery networks 160 described above. Each of the communication pathways 150 and 155 may include, for example, a wired, wireless, cable or satellite communication pathway.

FIG. 2 illustrates a communications system 200 including a client system 205 communicating with a host system 210 through a communications link 215. Client system 205 typically includes one or more client devices 220 and one or more client controllers 225 for controlling the client devices 220. Host system 210 typically includes one or more host devices 235 and one or more host controllers 240 for controlling the host devices 235. The communications link 215 may include communication pathways 250 and 255 that enable communications through the one or more delivery networks 260.

Examples of each element within the communications system of FIG. 2 are broadly described above with respect to FIG. 1. In particular, the host system 210 and communications link 215 typically have attributes comparable to those described with respect to the host system 110 and the communications link 115 of FIG. 1. Likewise, the client system 205 of FIG. 2 typically has attributes comparable to and illustrates one possible implementation of the client system 105 of FIG. 1.

The client device 220 typically includes a general-purpose computer 270 having an internal or external storage 272 for storing data and programs such as an operating system 274 (e.g., DOS, Windows™, Windows 95™, Windows 95™, Windows 2000™, Windows Me™, Windows XP™, Windows NT™, OS/2, or Linux) and one or more application programs. Examples of application programs include authoring applications 276 (e.g., word processing programs, database programs, spreadsheet programs, or graphics programs) capable of generating documents or other electronic content; client applications 278 (e.g., AOL client, CompuServe client, AIM client, AOL TV client, or ISP client) capable of communicating with other computer users, accessing various computer resources, and viewing, creating, or otherwise manipulating electronic content; and browser applications 280 (e.g., Netscape's Navigator or Microsoft's Internet Explorer) capable of rendering standard Internet content.

The general-purpose computer 270 also includes a central processing unit 282 (CPU) for executing instructions in response to commands from the client controller 225. In one implementation, the client controller 225 includes one or more of the application programs installed on the internal or external storage 272 of the general-purpose computer 270. In another implementation, the client controller 225 includes application programs externally stored in and performed by one or more device(s) external to the general-purpose computer 270.

The general-purpose computer typically will include a communication device 284 for sending and receiving data. One example of the communication device 284 is a modem. Other examples include a transceiver, a set-top box, a communication card, a satellite dish, an antenna, or another network adapter capable of transmitting and receiving data over the communications link 215 through a wired or wireless data pathway 250. The general-purpose computer 270 also may include a TV tuner 286 for receiving television programming in the form of broadcast, satellite, and/or cable TV signals. As a result, the client device 220 can selectively and/or simultaneously display network content received by communications device 284 and television programming content received by the TV tuner 286.

The general-purpose computer 270 typically will include an input/output interface 288 for wired or wireless connection to various peripheral devices 290. Examples of peripheral devices 290 include, but are not limited to, a mouse 291, a mobile phone 292, a personal digital assistant 293 (PDA), an MP3 player (not shown), a keyboard 294, a display monitor 295 with or without a touch screen input, a TV remote control 296 for receiving information from and rendering information to subscribers, and an audiovisual input device 298.

Although FIG. 2 illustrates devices such as a mobile telephone 292, a PDA 293, an MP3 player (not shown), and a TV remote control 296 as being peripheral with respect to the general-purpose computer 270, in another implementation, such devices may themselves include the functionality of the general-purpose computer 270 and operate as the client device 220. For example, the mobile phone 292 or the PDA 293 may include computing and networking capabilities and function as a client device 220 by accessing the delivery network 260 and communicating with the host system 210. Furthermore, the client system 205 may include one, some or all of the components and devices described above.

Referring to FIG. 3, a communications system 300 is capable of delivering and exchanging information between a client system 305 and a host system 310 through a communication link 315. Client system 305 typically includes one or more client devices 320 and one or more client controllers 325 for controlling the client devices 320. Host system 310 typically includes one or more host devices 335 and one or more host controllers 340 for controlling the host devices 335. The communications link 315 may include communication pathways 350 and 355 that enable communications through the one or more delivery networks 360.

Examples of each element within the communications system of FIG. 3 are broadly described above with respect to FIGS. 1 and 2. In particular, the client system 305 and the communications link 315 typically have attributes comparable to those described with respect to client systems 105 and 205 and communications links 115 and 215 of FIGS. 1 and 2. Likewise, the host system 310 of FIG. 3 may have attributes comparable to and illustrates one possible implementation of the host systems 110 and 210 shown in FIGS. 1 and 2.

The host system 310 includes a host device 335 and a host controller 340. The host controller 340 is generally capable of transmitting instructions to any or all of the elements of the host device 335. For example, in one implementation, the host controller 340 includes one or more software applications loaded on the host device 335. In other implementations, as described above, the host controller 340 may include any of several other programs, machines, and devices operating independently or collectively to control the host device 335.

The host device 335 includes a login server 370 for enabling access by subscribers and for routing communications between the client system 305 and other elements of the host device 335. The host device 335 also includes various host complexes such as the depicted OSP (“Online Service Provider”) host complex 380 and IM (“Instant Messaging”) host complex 390. To enable access to these host complexes by subscribers, the client system 305 includes communication software, for example, an OSP client application and an IM client application. The OSP and IM communication software applications are designed to facilitate the subscriber's interactions with the respective services and, in particular, may provide access to all the services available within the respective host complexes.

Typically, the OSP host complex 380 supports different services, such as e-mail, discussion groups, chat, news services, and Internet access. The OSP host complex 380 is generally designed with an architecture that enables the machines within the OSP host complex 380 to communicate with each other and employs certain protocols (i.e., standards, formats, conventions, rules, and structures) to transfer data. The OSP host complex 380 ordinarily employs one or more OSP protocols and custom dialing engines to enable access by selected client applications. The OSP host complex 380 may define one or more specific protocols for each service based on a common, underlying proprietary protocol.

The IM host complex 390 is generally independent of the OSP host complex 380, and supports instant messaging services irrespective of a subscriber's network or Internet access. Thus, the IM host complex 390 allows subscribers to send and receive instant messages, whether or not they have access to any particular ISP. The IM host complex 390 may support associated services, such as administrative matters, advertising, directory services, chat, and interest groups related to instant messaging. The IM host complex 390 has an architecture that enables all of the machines within the IM host complex to communicate with each other. To transfer data, the IM host complex 390 employs one or more standard or exclusive IM protocols.

The host device 335 may include one or more gateways that connect and therefore link complexes, such as the OSP host complex gateway 385 and the IM host complex gateway 395. The OSP host complex gateway 385 and the IM host complex gateway 395 may directly or indirectly link the OSP host complex 380 with the IM host complex 390 through a wired or wireless pathway. Ordinarily, when used to facilitate a link between complexes, the OSP host complex gateway 385 and the IM host complex gateway 395 are privy to information regarding the protocol type anticipated by a destination complex, which enables any necessary protocol conversion to be performed incident to the transfer of data from one complex to another. For instance, the OSP host complex 380 and IM host complex 390 generally use different protocols such that transferring data between the complexes requires protocol conversion by or at the request of the OSP host complex gateway 385 and/or the IM host complex gateway 395.

Referring to FIG. 4, a communications system 400 is capable of delivering and exchanging information between a client system 405 and a host system 410 through a communication link 415. Client system 405 typically includes one or more client devices 420 and one or more client controllers 425 for controlling the client devices 420. Host system 410 typically includes one or more host devices 435 and one or more host controllers 440 for controlling the host devices 435. The communications link 415 may include communication pathways 450 and 455 that enable communications through the one or more delivery networks 460. As shown, the client system 405 may access the Internet 465 through the host system 410.

Examples of each element within the communications system of FIG. 4 are broadly described above with respect to FIGS. 1-3. In particular, the client system 405 and the communications link 415 typically have attributes comparable to those described with respect to client systems 105, 205, and 305 and communications links 115, 215, and 315 of FIGS. 1-3. Likewise, the host system 410 of FIG. 4 may have attributes comparable to and illustrates one possible implementation of the host systems 110, 210, and 310 shown in FIGS. 1-3. FIG. 4 describes an aspect of the host system 410, focusing primarily on one particular implementation of OSP host complex 480.

The client system 405 includes a client device 420 and a client controller 425. The client controller 425 is generally capable of establishing a connection to the host system 410, including the OSP host complex 480, the IM host complex 490 and/or the Internet 465. In one implementation, the client controller 425 includes an OSP application for communicating with servers in the OSP host complex 480 using exclusive OSP protocols. The client controller 425 also may include applications, such as an IM client application, and/or an Internet browser application, for communicating with the IM host complex 490 and the Internet 465.

The host system 410 includes a host device 435 and a host controller 440. The host controller 440 is generally capable of transmitting instructions to any or all of the elements of the host device 435. For example, in one implementation, the host controller 440 includes one or more software applications loaded on one or more elements of the host device 435. In other implementations, as described above, the host controller 440 may include any of several other programs, machines, and devices operating independently or collectively to control the host device 435.

The host system 410 includes a login server 470 capable of enabling communications with and authorizing access by client systems 405 to various elements of the host system 410, including an OSP host complex 480 and an IM host complex 490. The login server 470 may implement one or more authorization procedures to enable simultaneous access to the OSP host complex 480 and the IM host complex 490. The OSP host complex 480 and the IM host complex 490 are connected through one or more OSP host complex gateways 485 and one or more IM host complex gateways 495. Each OSP host complex gateway 485 and IM host complex gateway 495 may perform any protocol conversions necessary to enable communications between the OSP host complex 480, the IM host complex 490, and the Internet 465.

The OSP host complex 480 supports a set of services from one or more servers located internal to and external from the OSP host complex 480. Servers external to the OSP host complex 480 generally may be viewed as existing on the Internet 465. Servers internal to the OSP complex 480 may be arranged in one or more configurations. For example, servers may be arranged in centralized or localized clusters in order to distribute servers and subscribers within the OSP host complex 480.

In one implementation of FIG. 4, the OSP host complex 480 includes a routing processor 4802. In general, the routing processor 4802 will examine an address field of a data request, use a mapping table to determine the appropriate destination for the data request, and direct the data request to the appropriate destination. In a packet-based implementation, the client system 405 may generate information requests, convert the requests into data packets, sequence the data packets, perform error checking and other packet-switching techniques, and transmit the data packets to the routing processor 4802. Upon receiving data packets from the client system 405, the routing processor 4802 may directly or indirectly route the data packets to a specified destination within or outside of the OSP host complex 480. For example, in the event that a data request from the client system 405 can be satisfied locally, the routing processor 4802 may direct the data request to a local server 4804. In the event that the data request cannot be satisfied locally, the routing processor 4802 may direct the data request externally to the Internet 465 or the IM host complex 490 through the gateway 485.

The OSP host complex 480 also includes a proxy server 4806 for directing data requests and/or otherwise facilitating communication between the client system 405 and the Internet 465. The proxy server 4806 may include an IP (“Internet Protocol”) tunnel for converting data from OSP protocol into standard Internet protocol and transmitting the data to the Internet 465. The IP tunnel also converts data received from the Internet 465 in the standard Internet protocol back into the OSP protocol and sends the converted data to the routing processor 4802 for delivery back to the client system 405.

The proxy server 4806 also may allow the client system 405 to use standard Internet protocols and formatting to access the OSP host complex 480 and the Internet 465. For example, the subscriber may use an OSP TV client application having an embedded browser application installed on the client system 405 to generate a request in standard Internet protocol, such as HTTP (“HyperText Transport Protocol”). In a packet-based implementation, data packets may be encapsulated inside a standard Internet tunneling protocol, such as, for example, UDP (“User Datagram Protocol”) and routed to the proxy server 4806. The proxy server 4806 may include an L2TP (“Layer Two Tunneling Protocol”) tunnel capable of establishing a point-to-point protocol (PPP) session with the client system 405.

The proxy server 4806 also may act as a buffer between the client system 405 and the Internet 465, and may implement content filtering and time saving techniques. For example, the proxy server 4806 can check parental controls settings of the client system 405 and request and transmit content from the Internet 465 according to the parental control settings. In addition, the proxy server 4806 may include one or more caches for storing frequently accessed information. If requested data is determined to be stored in the caches, the proxy server 4806 may send the information to the client system 405 from the caches and avoid the need to access the Internet 465.

Referring to FIG. 5, a communications system 500 is capable of delivering and exchanging information between a client system 505 and a host system 510 through a communication link 515. Client system 505 typically includes one or more client devices 520 and one or more client controllers 525 for controlling the client devices 520. Host system 510 typically includes one or more host devices 535 and one or more host controllers 540 for controlling the host devices 535. The communications link 515 may include communication pathways 550, 555 enabling communications through the one or more delivery networks 560. As shown, the client system 505 may access the Internet 565 through the host system 510.

Examples of each element within the communications system of FIG. 5 are broadly described above with respect to FIGS. 1-4. In particular, the client system 505 and the communications link 515 typically have attributes comparable to those described with respect to client systems 105, 205, 305, and 405 and communications links 115, 215, 315, and 415 of FIGS. 1-4. Likewise, the host system 510 of FIG. 5 may have attributes comparable to and illustrates one possible implementation of the host systems 110, 210, 310, and 410 shown in FIGS. 1-4. FIG. 5 describes an aspect of the host system 510, focusing primarily on one particular implementation of IM host complex 590.

The client system 505 includes a client device 520 and a client controller 525. The client controller 525 is generally capable of establishing a connection to the host system 510, including the OSP host complex 580, the IM host complex 590 and/or the Internet 565. In one implementation, the client controller 525 includes an IM application for communicating with servers in the IM host complex 590 using exclusive IM protocols. The client controller 525 also may include applications, such as an OSP client application, and/or an Internet browser application for communicating with the OSP host complex 580 and the Internet 565, respectively.

The host system 510 includes a host device 535 and a host controller 540. The host controller 540 is generally capable of transmitting instructions to any or all of the elements of the host device 535. For example, in one implementation, the host controller 540 includes one or more software applications loaded on one or more elements of the host device 535. However, in other implementations, as described above, the host controller 540 may include any of several other programs, machines, and devices operating independently or collectively to control the host device 535.

The host system 510 includes a login server 570 capable of enabling communications with and authorizing access by client systems 505 to various elements of the host system 510, including an OSP host complex 580 and an IM host complex 590. The login server 570 may implement one or more authorization procedures to enable simultaneous access to the OSP host complex 580 and the IM host complex 590. The OSP host complex 580 and the IM host complex 590 are connected through one or more OSP host complex gateways 585 and one or more IM host complex gateways 595. Each OSP host complex gateway 585 and IM host complex gateway 595 may perform any protocol conversions necessary to enable communication between the OSP host complex 580, the IM host complex 590, and the Internet 565.

To access the IM host complex 590 and begin an IM session, the client system 505 establishes a connection to the login server 570. The login server 570 typically determines whether the particular subscriber is authorized to access the IM host complex 590 by verifying a subscriber identification and password. If the subscriber is authorized to access the IM host complex 590, the login server 570 employs a hashing technique on the subscriber's screen name to identify a particular IM server 5902 for use during the subscriber's session. The login server 570 provides the client system 505 with the IP address of the particular IM server 5902, gives the client system 505 an encrypted key (i.e., a cookie), and breaks the connection. The client system 505 then uses the IP address to establish a connection to the particular IM server 5902 through the communications link 515, and obtains access to that IM server 5902 using the encrypted key. Typically, the client system 505 will be equipped with a Winsock API (“Application Programming Interface”) that enables the client system 505 to establish an open TCP connection to the IM server 5902.

Once a connection to the IM server 5902 has been established, the client system 505 may directly or indirectly transmit data to and access content from the IM server 5902 and one or more associated domain servers 5904. The IM server 5902 supports the fundamental instant messaging services and the domain servers 5904 may support associated services, such as, for example, administrative matters, directory services, chat and interest groups. In general, the purpose of the domain servers 5904 is to lighten the load placed on the IM server 5902 by assuming responsibility for some of the services within the IM host complex 590. By accessing the IM server 5902 and/or the domain server 5904, a subscriber can use the IM client application to view whether particular subscribers (“buddies”) are online, exchange instant messages with particular subscribers, participate in group chat rooms, trade files such as pictures, invitations or documents, find other subscribers with similar interests, get customized news and stock quotes, and search the World Wide Web.

In the implementation of FIG. 5, the IM server 5902 is directly or indirectly connected to a routing gateway 5906. The routing gateway 5906 facilitates the connection between the IM server 5902 and one or more alert multiplexors 5908, for example, by serving as a link minimization tool or hub to connect several IM servers 5902 to several alert multiplexors 5908. In general, an alert multiplexor 5908 maintains a record of alerts and subscribers registered to receive the alerts.

Once the client system 505 is connected to the alert multiplexor 5908, a subscriber can register for and/or receive one or more types of alerts. The connection pathway between the client system 505 and the alert multiplexor 5908 is determined by employing another hashing technique at the IM server 5902 to identify the particular alert multiplexor 5908 to be used for the subscriber's session. Once the particular multiplexor 5908 has been identified, the IM server 5902 provides the client system 505 with the IP address of the particular alert multiplexor 5908 and gives the client system 505 an encrypted key (i.e., a cookie). The client system 505 then uses the IP address to connect to the particular alert multiplexor 5908 through the communication link 515 and obtains access to the alert multiplexor 5908 using the encrypted key.

The alert multiplexor 5908 is connected to an alert gate 5910 that, like the IM host complex gateway 595, is capable of performing the necessary protocol conversions to form a bridge to the OSP host complex 580. The alert gate 5910 is the interface between the IM host complex 590 and the physical servers, such as servers in the OSP host complex 580, where state changes are occurring. In general, the information regarding state changes will be gathered and used by the IM host complex 590. However, the alert multiplexor 5908 also may communicate with the OSP host complex 580 through the IM host complex gateway 595, for example, to provide the servers and subscribers of the OSP host complex 580 with certain information gathered from the alert gate 5910.

The alert gate 5910 can detect an alert feed corresponding to a particular type of alert. The alert gate 5910 may include a piece of code (alert receive code) capable of interacting with another piece of code (alert broadcast code) on the physical server where a state change occurs. In general, the alert receive code installed on the alert gate 5910 instructs the alert broadcast code installed on the physical server to send an alert feed to the alert gate 5910 upon the occurrence of a particular state change. Upon detecting an alert feed, the alert gate 5910 contacts the alert multiplexor 5908, which in turn, informs the client system 505 of the detected alert feed.

In the implementation of FIG. 5, the IM host complex 590 also includes a subscriber profile server 5912 connected to a database 5914 for storing large amounts of subscriber profile data. The subscriber profile server 5912 may be used to enter, retrieve, edit, manipulate, or otherwise process subscriber profile data. In one implementation, a subscriber's profile data includes, for example, the subscriber's buddy list, alert preferences, designated stocks, identified interests, and geographic location. The subscriber may enter, edit and/or delete profile data using an installed IM client application on the client system 505 to interact with the subscriber profile server 5912.

Because the subscriber's data is stored in the IM host complex 590, the subscriber does not have to reenter or update such information in the event that the subscriber accesses the IM host complex 590 using a new or a different client system 505. Accordingly, when a subscriber accesses the IM host complex 590, the IM server 5902 can instruct the subscriber profile server 5912 to retrieve the subscriber's profile data from the database 5914 and to provide, for example, the subscriber's buddy list to the IM server 5902 and the subscriber's alert preferences to the alert multiplexor 5908. The subscriber profile server 5912 also may communicate with other servers in the OSP host complex 580 to share subscriber profile data with other services. Alternatively, user profile data may be saved locally on the client device 505.

Referring to FIG. 6, a sender 602a, a recipient 602b, and a host 604 exchange communications according to a procedure 600. The procedure 600 may be implemented by any suitable type of hardware (e.g., device, computer, computer system, equipment, component); software (e.g., program, application, instructions, code); storage medium (e.g., disk, external memory, internal memory, propagated signal); or combination thereof.

Examples of each element of FIG. 6 are broadly described with respect to FIGS. 1-5 above. In particular, the sender 602a and the recipient 602b may have attributes comparable to those described with respect to client devices 120, 220, 320, 420, and 520 and/or client controllers 125, 225, 325, 425, and 525. The host 604 may have attributes comparable to those described with respect to host devices 135, 235, 335, 435, and 535 and/or host controllers 140, 240, 340, 440, and 540. The sender 602a, the recipient 602b, and/or the host 604 may be directly or indirectly interconnected through a known or described delivery network, such as delivery networks 160, 260, 360, 460, and 560.

In one implementation, the sender 602a is associated with a first subscriber, the recipient 602b is associated with a second subscriber, and each of the sender 602a and the recipient 602b includes an application for accessing the host 604. A subscriber's transfer preferences may be maintained locally at the application or remotely at the host 604. Each subscriber may use the application to set individual preferences for allowing messages and/or files to be transferred to and from other subscribers. Typically, a graphical user interface (“UI”) is displayed to allow each subscriber to select among various levels of security and/or to grant (or deny) access to others subscribers. For example, transfer preferences may be set to allow all users or only certain users (e.g., users included in the subscriber's buddy list) to contact the recipient 602b. If the transfer preferences of the recipient 602b have been set to block a subscriber attempting contact, the sender 602a may display a UI indicating that instant messaging with the recipient 602b is unavailable.

More specifically, the sender 602a is a subscriber and/or a client (e.g., client system 505), and the host 604 includes one or more host complexes (e.g., OSP host complex 580 and/or IM host complex 590) for providing instant messaging capability and coordinating the transfer of electronic data between subscribers. The sender 602a may access the host 604 using any available device and/or controller.

An example of a device is a general-purpose computer capable of responding to and executing instructions in a defined manner. Other examples include a special-purpose computer, a personal computer (“PC”), a workstation, a server, a laptop, a Web-enabled telephone, a Web-enabled personal digital assistant (“PDA”), an interactive television set, a settop box, a video tape recorder (“VTR”), a DVD player, an on-board (i.e., vehicle-mounted) computer, or any other component, machine, tool, equipment, or some combination thereof capable of responding to and executing instructions.

An example of a controller is a software application (e.g., operating system, browser application, microbrowser application, server application, proxy application, gateway application, tunneling application, e-mail application, IM client, online service provider client application, interactive television client application, and/or ISP client) loaded on a device to command and direct communications enabled by the device. Other examples include a computer program, a piece of code, an instruction, another device, or some combination thereof, for independently or collectively instructing the device to interact and operate as desired. The controller may be embodied permanently or temporarily in any type of machine, component, physical or virtual equipment, storage medium, or propagated signal capable of providing instructions to a device. In particular, the controller (e.g., software application, computer Program) may be stored on a storage media or device (e.g., ROM, magnetic diskette, or propagated signal) readable by a general or special purpose programmable computer, such that if the storage media or device is read by a computer system, the functions described herein are performed.

In the following example, it is assumed that the transfer preferences are set to allow messages and files to be transferred between the sender 602a and the recipient 602b. To communicate using instant messaging, the sender 602a and the recipient 602b access the host 604 concurrently. In order to access the host 604, the sender 602a and the recipient 602b each separately request authentication or recognition by the host 604. The request identifies the associated subscriber to the host 604 for subsequent identification to other subscribers using a unique screen name. The sender 602a and the recipient 602b each may include a Winsock API for opening and establishing a TCP connection to the host 604.

The host 604 verifies a subscriber's information (e.g., screen name and password) against data stored in a subscriber database. If the subscriber's information is verified, the host 604 authorizes access and or acknowledges the subscriber. If the subscriber's information is not verified, the host 604 denies access and sends an error message.

After being authorized, a direct (i.e., socket) connection may be established through the host 604 to allow the sender 602a and the recipient 602b to communicate. The sender 602a and the recipient 602b use this connection to communicate with the host 604 and with each other. This connection remains available during the time that the sender 602a and the recipient 602b are accessing the host 604, or until either party decides to terminate.

Upon accessing the host 604, a “buddy list” is displayed to the subscriber. In general, a subscriber's buddy list is maintained with or accessible as part of a subscriber's user profile and may be made accessible using a user interface (UI) that provides the online status and capabilities of certain screen names, i.e., “buddies,” identified by the subscriber. In particular, the host 604 informs the sender 602a whether identified buddies are online, i.e., currently accessing the host 604. The host 604 also informs any subscriber who has identified the sender 602a as a buddy that the sender 602a is currently online.

A buddy list may be used to facilitate IM communications between subscribers. For example, a subscriber can activate an IM user interface that is pre-addressed to a buddy simply by selecting the screen name of an online buddy from the buddy list.

Alternatively, by way of example, if a recipient is not a “buddy,” the first subscriber generally initiates IM communications by activating a blank IM user interface and then addressing that interface to the screen name of the intended recipient. When necessary, a subscriber can look up the screen name of an intended recipient using the intended recipient's e-mail address.

In the implementation of FIG. 6, a sender 602a, a recipient 602b, and a host 604 interact according to a procedure 600 that extends the functionality of instant messaging by passively personalizing the buddy list of at least one of the sender 602a and the recipient 602b.

Initially, the sender 602a accesses the host 604 (step 606). The sender 602a designates at least one recipient 602b to receive an instant message (step 608). The instant message may be, for example, a text or non-text (e.g., audio, video) instant message created by the sender 602a.

More specifically, in one implementation of this process in which the sender 602a has previously designated a screen name associated with the intended recipient 602b as a “buddy,” a UI (e.g., buddy list) indicating the online status and capabilities of the recipient 602b is displayed to the sender 602a. Thus, the sender 602a can confirm that the recipient 602b is able to communicate (i.e., is online) and then designate the recipient 602b for receipt of an instant message by selecting (e.g., clicking) the screen name associated with the recipient 602b to open an IM interface (step 608).

After an IM recipient is selected (step 608), the host 604 detects the capabilities of the recipient (step 610) and reports the capabilities of the recipient 602b to the sender 602a (step 612). In one implementation, a network of servers (e.g., IM servers 5902) on the host 604 monitors and updates the online status, client version, and device type of connected subscribers and reports or enables access to this information by other subscribers in real time or substantially in real time. Yet, the accuracy and timeliness of information reported using an instant messaging interface may depend on factors such as a subscriber's hardware (e.g., device type), software (e.g., client version), and/or transfer preferences (e.g., blocked screen names).

Next, the sender 602a receives the report from the host 604 (step 614) and displays a UI corresponding to the capabilities of the sender 602a and/or the recipient 602b (step 616). In general, if the sender 602a (e.g., client system 505) is not voice-enabled and/or video-enabled, the sender 602a displays a standard instant messaging UI. If the sender 602a is voice-enabled and/or video-enabled, then the sender 602a may be configured to display a voice-enabled and/or video-enabled UI.

The sender 602a then composes a message in the IM interface (step 618) and transmits the instant message to the host 604 (step 620). In general, the sender transmits the message by selecting a send button.

The host 604 receives the instant message from the sender 602a (step 622) and then optionally authenticates the instant message (step 624). In one implementation, the instant message includes header information identifying the message type, the screen name and/or IP address of the sender 602a and the recipient 602b, and a randomly generated security number. A server (e.g., IM server 5902) on the host 604 may authenticate the instant message by matching the screen names and/or IP addresses with those of valid subscribers stored in a reverse look-up table. In the event that either the sender 602a or the recipient 602b is not associated with a valid subscriber, the host 604 reports an error message. The host 604 then sends the instant message to the recipient 602b (step 626).

The recipient 602b receives the instant message from the host (step 628) and then accepts the instant message (step 630). Accepting the instant message may occur automatically if the subscriber that sent the instant message has been preauthorized according to the transfer preferences of the recipient 602b.

For example, acceptance may occur automatically if the sender 602a is included on a buddy list maintained by the recipient 602b. Alternatively, accepting the instant message may include displaying a warning UI based on the transfer preferences of the recipient 602b. For example, the preferences of the recipient 602b may be set to present an “accept message” dialog before displaying messages from any users or certain users (e.g., users not included in the subscriber's buddy list).

After the instant message is accepted (step 630), the host establishes an IM session (step 632) that enables the sender 602a and the recipient 602b to communicate substantially in real time. Establishing an IM session generally involves connecting one or more communication channels for transferring data between the sender 602a and the recipient 602b. The communication channels may allow the sender 602a and the recipient 602b to transfer data directly with each other (e.g., over a peer-to-peer connection) or may require the data to pass through an intermediary (e.g., host 604).

An active IM session may use one or more communication channels, such as, for example, a generic signaling interface (GSI) channel, a control channel, and a data channel. The GSI channel may be used to establish the initial connection. During this connection, the local IP addresses are exchanged. After the initial connection phase is done, the GSI channel is no longer used. By using the GSI channel, the exchange of local IP addresses is done only when both subscribers authorize such an exchange. Thus, using the GSI channel protects subscribers from having their local IP addresses automatically obtained without their consent.

The control channel is typically a TCP/IP socket for which the IP address and port number of the remote side are obtained through the GSI channel. The control channel may be used to send/receive control attributes of an active session. For example, because some firewalls will not allow a connection to be initiated by an external device with a socket on the inside of the firewall, a connection is attempted from both sides of the session.

The data channel also is typically a TCP/IP socket, and is used to transport data packets using various protocols such as UDP and TCP. In general, UDP is used since it minimizes latency. However, because some firewalls will not allow UDP packets to pass through, the data channel may use a different protocol, such as TCP. The client may indicate a particular mode (i.e., TCP, UDP) or, alternatively, an auto mode where it attempts a UDP test, and upon failure resorts to a secondary protocol (e.g., TCP).

When an IM session has been established successfully (step 632), the sender 602a and the recipient 602b may exchange communications substantially in real time. In one implementation, the recipient 602b displays an instant message received from the sender 602a (step 634). Referring to FIG. 7, for example, a UI 700 that may be displayed by the sender 602a and/or the recipient 602b includes an IM window 705 for displaying a running transcript of an IM session and a text message area 710 for entering the text of an instant message. In this example, the IM session includes a first instant message 705 from a first subscriber having a first screen name (ProductRep) and second instant message 707 from a second subscriber having a second screen name (Subscriber). Although the first and second subscribers of this example have each sent and received instant messages, the following description is provided with reference to the first subscriber as being associated with the sender 602a and the second subscriber as being associated with the recipient 602b.

The UI 700 also includes an IM toolbar 715 for changing text or background colors, changing text size, emphasizing text (e.g., bold, italic, or underlining), and inserting objects (e.g., emoticons, hyperlinks, images). In addition, the UI 700 includes IM buttons 720 for performing IM functions such as notifying the OSP of offending conduct, blocking a subscriber, adding an IM contact (e.g., buddy), initiating an audio (or video) IM session, getting the profile of a sender, and sending instant messages.

When an IM session is closed, the sender 602a and the recipient 602b may not exchange communications until a new IM session is established between the sender 602a and the recipient 602b. An IM session may be closed when the participants close the IM window 705, when either the sender 602a or the recipient 602b disconnects from the host 604, or when a configurable period of time has passed during which no communications are exchanged between the sender 602a and the recipient 602b.

During an active IM session, the host 604 may moderate the IM session. In one implementation, a server (e.g., IM server 5902, domain server 5904) on the host 604 is configured to moderate an IM session between at least one sender 602a and at least one recipient 602b. Moderating an IM session may include managing load conditions of the host 604 by compressing, decompressing, caching, and/or allocating resources to efficiently store and forward instant messages.

Moderating the IM session also may include updating an IM log (step 636). In general, an IM log includes a chronological record of IM activity (e.g., the existence or status of separate and/or successful IM sessions, the opening or closing of an IM session, the communication of instant messages during each separate and/or successful IM session, the request or receipt of alerts, or the connection or disconnection with the host). The IM log may be stored and maintained on the host 604 (e.g., by database 5914 of IM host 590), the sender 602a (e.g., by memory 272 of the client device), and/or the recipient 602b (e.g., by memory 272 of the client device). Entries in the IM log may be ordered, deleted, edited, and/or otherwise managed by the host 604, the sender 602a, and/or the recipient 602b. For example, the host 604 may queue, order, and arrange entries in the IM log based on time, subscribers (e.g., screen names), topic, relevance, and/or any other ranking criteria.

Typically, each subscriber will have a corresponding IM log for recording IM activity of the subscriber. However, an IM log may be associated with a group of subscribers, or may simply be used to chronologically log activities of all subscribers communicating over or with the device used to maintain or store the log.

Updating the IM log may include recording the screen names of participants of an IM session. The sender 602a, the recipient 602b, and/or the host 604 may be configured to detect at least one identity (e.g., the screen names) associated with an instant message during an IM session, for example, by parsing the header information of an instant message. Typically, the screen names recorded in the IM log of a particular subscriber will be supplemented with information including the time the IM session was established and the screen names of other subscribers that participated in the IM session where several subscribers communicate using group IM. Updating the IM log also may include tracking the instant messages sent during an IM session and recording the time that each instant message was sent and received, recording the time the IM session was closed, and/or recording the time the sender 602a or the recipient 602b disconnected from the host 604.

A list of screen names for the most recent IM communications may be derived from the IM log automatically (step 638). The sender 602a, the recipient 602b, and/or the host 604 may be configured to derive such a list. For example, at any time, the last N different screen names with whom a particular subscriber has had an IM session may be determined from an updated IM log. The number N may be any predetermined number set according to preferences of the sender 602a, the recipient 602b, and/or the host 604, or it may be user-selectable.

In one implementation, the host 604 (e.g., profile server 5912 or IM server 5902) accesses an IM log associated with a particular subscriber that is stored on the host 604 (e.g., database 5914). The host 604 examines the IM log and creates a list of N different screen names based on an associated time or a relative position of each screen name. The associated time may be a time that an IM session was established, a time that an instant message was sent (or received), a time that an IM session was completed, a time that the sender 602a or the recipient 602b connected to or disconnected from the host 604, or some other time. Typically, the list of N screen names will be ordered with the most recent screen name being listed first.

The IM log (and/or the list of most recent IM contacts) may be configured to store only the last N different screen names with which a particular subscriber has had an IM session. The IM log may be maintained using a least recently used methodology. For example, when a new IM session is established, the screen name of each participant may be compared to the list of most recent IM contacts. If the screen name does not already appear in the list, the screen name is added and the least recent IM contact (i.e., oldest IM contact) is reduced in order or altogether removed from the list so that the list includes only N different screen names. If the screen name already appears in the list, the list is reordered so that the screen name appears at the top of the list. In either case, the updated list includes N different screen names listed in order of most recently used IM session. In some implementations, the list may be filtered to include only screen names that do not already appear on the subscriber's buddy list.

In another example, when an IM session is completed or when either the sender 602a or the recipient 602b disconnects from the host 604, the screen name of each participant may be compared to the list of most recent IM contacts. If the screen name does already appear in the list, the screen name is added and the least recent IM contact (i.e., oldest IM contact) is removed from the list if necessary to maintain only N different screen names on the list; otherwise, the least recent IM contact may be merely demoted. If the screen name already appears in the list, the list is reordered so that the screen name appears at the top of the list. In either case, the final list includes N different screen names listed in order of most recent IM session. In one implementation, the screen name of each participant may be compared to the list of most recent IM contacts only when an IM session is completed or only when either the sender 602a or the recipient 602b disconnects from the host 604 such that the list includes only the most recent IM contacts of the most recent closed IM sessions.

In another example, the IM log may be maintained using other methodologies, such as, for example a first-in first-out (FIFO) methodology. For example, when an new IM session is established, the screen name of each participant may be added to the list and the screen name first added to the list may be reduced in order or altogether removed from the list, whether or not it was the screen name least recently used actively in a conversation, thus maintaining the threshold number of different screen names. In some implementations, the list may be filtered to include only the screen names that do not already appear on the subscriber's list.

After a list of N different screen names is compiled, a user profile is accessed (step 640). In general, a user profile corresponds to a particular subscriber and may include, for example, the subscriber's buddy list, alert preferences, identified interests, geographic location, and user contact information (e.g., phone numbers, e-mail addresses, screen names, and mailing address). The user profile of a subscriber may be stored and maintained on the host 604 (e.g., IM host 590, database 5914), the sender 602a (e.g., client device, memory 272), and/or the recipient 602b (e.g., client device, memory 272). In one implementation, portions of the user profile may be stored and maintained in several remote locations. Typically, a subscriber actively enters, edits and/or deletes the content of the user profile, for example, by using an installed IM client application to fill out an electronic form. In this case, however, access of the user profile may occur transparently to the subscriber. That is, the user profile is accessed without requiring any user action (e.g., selection or configuration by the subscriber). In one implementation, the host 604 (e.g., profile server 5912, IM server 5902) accesses the user profile. In other implementations, an installed IM client application is configured to transparently access a local user profile.

Then, the user profile is passively configured (step 642). That is, configuration occurs transparently to the subscriber and requires no subscriber action (e.g., selection by the subscriber). Configuration of the user profile may include the creating and/or modifying of a subscriber's user preferences, such as, for example, a buddy list, address book, calendar, notification settings (e.g., alerts), or any other personalized attributes associated with the subscriber.

In one implementation, a buddy list included in a subscriber's user profile is configured based on the updated IM log. In particular, a buddy list associated with at least one of the sender 602a and the recipient 602b may be passively configured to include a list of most recent contacts (step 642).

Referring to FIG. 8, a UI 800 that may be passively configured includes a Buddy List Window 805 having a List Setup box 810 (step 644 of FIG. 6). The List Setup box 810 includes one or more IM groups, for example, a Recent Contacts group 812, a Buddies group 816, a Co-Workers group 820, and a Family group 824. Each IM group includes one or more IM group members identified by screen name, for example, Recent Contacts group members 814, Buddies group members 818, Co-Workers group members 822, and Family group members 826. The List Setup box 810 also includes List Setup buttons 828 for performing IM functions such as adding a screen name, adding a group, deleting a screen name or group, and finding a screen name of a subscriber. The Buddy List Window 805 further includes Buddy List buttons 830 for performing IM functions such as linking to an IM-related web page, entering an away message, and setting IM-related user preferences.

In one implementation, the size of the IM groups may be limited to a threshold number of screen names, which may be independent of a size limit established for the entirety of the Buddy List in which it is included. Furthermore, specific IM groups may have different size limitations. For example, the Recent Contacts group 812 may be subject to the threshold number limitation on screen names and the Buddies group 816 may be subject to a different threshold number limitation of screen names, each of which may be different from a size limit of the Buddy List.

The IM groups may be actively or passively created, as discussed below. The Buddies group 816 may be a standard (or default) group provided with every installation of an IM client. In general, when a subscriber opens an IM account, the Buddies group 816 is created automatically. Initially, the Buddies group 816 is empty. To populate the Buddies group 816, a subscriber must actively enter a screen name for each person with whom the subscriber desires to communicate. For example, using the List Setup Buttons 828, a subscriber actively entered the screen name for each of the Buddies group members 818 (e.g., Buddy, Friend, Pal). In one implementation, the host 604 (e.g., IM host 590) provides a reverse lookup function that allows subscribers to search for screen names using various criteria of subscribers (e.g., name, location, e-mail address, interests).

The Co-Workers group 820 and the Family group 824 may be personalized groups actively created by the subscriber. In general, subscribers may personalize their buddy lists by creating different group and categorizing screen names. For example, using the List Setup Buttons 828, a subscriber can actively create the Co-Workers group 820 and the Family group 824. After the Co-Workers group 820 and the Family group 824 are created, the subscriber has conventionally been required to actively enter a screen name for each of the Co-Workers group members 822 (e.g., Boss, Employee, Supervisor) and to actively enter a screen name for each of the Family group members 826 (e.g., Brother, Dad, Mom, Sister). A screen name may occupy more than one personalized group.

Like the Buddies Group 816, the Recent Contacts group 812 may be a standard (or default) group provided with every installation of an IM client. In general, when a subscriber opens an IM account, the Recent Contacts group 812 is created automatically. Initially, the Recent Contacts group 812 is empty. However, unlike the Buddies group 816, a subscriber does not have to actively enter screen names to populate the Recent Contacts group 812. That is, the Recent Contacts group 812 may be created, populated and/or modified without user action (e.g., clicks, data entry). For example, screen names are added to and removed from the Recent Contacts group 812 as IM sessions are opened and closed, and/or as membership limits are imposed on the Recent Contacts group. As such, in one implementation, screen names are added to the Recent Contacts group 812 passively, as successful IM sessions are established, used for communication, or closed with the subscriber, and these screen names may be removed from that group 812 as maximum group size is reached. In another example, the screen name of each of the Recent Contacts group members 814 (e.g., Boss, ProductRep, Supervisor, SalesRep, Employee) is passively added to the Recent Contacts group 812 as successful IM session are closed with the subscriber or when either the sender 602a or the recipient 602b disconnects from the host 604.

In one implementation, the subscriber participates in an IM session with each of the Recent Contacts group members 814 in the following order: Employee, SalesRep, Supervisor, ProductRep, and Boss. As each IM session is established, a screen name for each of the Recent Contacts group members is added in sequence to the Recent Contacts group 812 resulting in the most recent contact being listed first. In this example, the order is implied from the visual hierarchy; however, numeric or other explicit visual indicators also may be used to make clear the relative order of recent IM sessions. Furthermore, in this example, it does not matter which subscriber initiates the IM session (i.e., who sent the initial instant message) or whether a response to the initial instant message is sent. However, the screen names may be ordered, separated into different groups, or otherwise differentiated to reflect this information. A screen name of a particular person may be added whenever a successful IM session is established, used for communication, or closed between the subscriber and the particular person. Screen names included in the Recent Contacts group 812 also may occupy other groups (e.g., Co-Workers group 820), or, alternatively, the Recent Contacts group 812 may include only the screen name of persons not included in select or all other groups.

In another implementation, as each IM session is completed or when one or both of the sender 602a or the recipient 602b disconnects from the host 604, a screen name for the participant is added in sequence to the Recent Contacts group 812 resulting in the most recently closed/discontinued contact being listed first. Moreover, in this implementation, a screen name of a particular person is added whenever a successful IM session is closed between the subscriber and the particular person or when either subscriber disconnects from the host. In this example, it does not matter which subscriber closed the IM session (e.g., who closed the IM window, who disconnected from the host) or which subscriber disconnected from the host. However, the screen names may be ordered, separated into different groups, or otherwise so differentiated to reflect this information.

Referring to FIG. 9, a UI 900 that may be passively configured includes a Buddy List Window 805 having an Online box 840 (step 644 of FIG. 6). In general, the Online box 840 displays the online status and capabilities of certain screen names identified by the subscriber in the List Setup box, for example, List Setup box 810 of FIG. 8. In one implementation, the host 604 (e.g., IM host 590, IM server 5902) informs the sender 602a (e.g., client device, IM client application) whether the subscribers associated with the screen names are online, i.e., currently accessing the host 604.

The Online box 840 includes one or more online lists, with each list corresponding to an IM group. For example, the Online box 840 includes a Recent Contacts list 842, a Buddies list 846, a Co-Workers list 850, and a Family list 854. Several of these online lists (e.g., 846, 850, and 854) include one or more screen names corresponding to IM group members that currently are online. In the implementation of FIG. 9, the Recent Contacts list 842 identifies certain online Recent Contacts members 844, the Buddies list 846 identifies a certain online Buddies member 846, the Co-Workers list 850 identifies certain online Co-Workers members 852, and the Family list 854 identifies a certain online Family member 856. The Online box 840 also includes an Offline list 858 identifying offline members 860 from one or more of the IM groups separately (not shown) or collectively. The Online box 840 further includes Online buttons 862 for performing IM functions such as displaying an IM window, sending an invitation to enter a chat room, and finding profile information associated with a screen name.

The Online box 840 facilitates IM communication between subscribers. For example, a subscriber can activate a pre-addressed IM window simply by clicking the screen name of an online group member.

Referring to FIG. 10, a UI 1000 that may be invoked using the buddy list and displayed to the sender 602a and/or the recipient 602b includes an IM window 705 including a running transcript of some or all of an IM session and a text message area 710 for entering the text of an instant message, an IM toolbar 715, and IM buttons 720. In this example, the IM session includes a first instant message 708 from a first subscriber having a first screen name (Subscriber) and second instant message 709 from a second subscriber having a second screen name (ProductRep). The first subscriber may be associated with the sender 602a and the second subscriber may be associated with the recipient 602b.

Referring to FIG. 11, in one implementation, the UI 1000 is displayed to a first subscriber associated with a sender 602a as follows (step 1110). First, the first subscriber participates in an IM session with each of the Recent Contacts group members 814 in the following order: Employee, SalesRep, Supervisor, ProductRep, and Boss (step 1120). As each IM session is established, a screen name for each of the Recent Contacts group members is added in sequence to the Recent Contacts group 812 resulting in the most recent contact being listed first (step 1130a). Additionally and/or alternatively, as each IM session is closed (step 1130b), or when either the sender or the recipient disconnect from the host (step 1130c), a screen name for each of the Recent Contacts group members is added in sequence to the Recent Contacts group 812 resulting in the most recently closed/discontinued contact being listed first. Screen names included in the Recent Contacts group 812 also may occupy other groups (e.g., Co-Workers group 820).

Still further, the order of screen names within the Recent Contacts group 812 may be rearranged based on the relative time of session closure or disconnection. For instance, assume that a first IM session with Employee X is opened and closed, a second IM session with Employee Y is subsequently opened and closed, and a third IM session with Employee X is later opened and closed. In this case, before the third IM session is initiated, the Recent Contacts group 812 may order Employee Y ahead of Employee X since the second IM session opened and/or closed before the first IM session. However, after the third IM session, their order may be reversed to reflect the opening and/or closing of an IM session (the third) with Employee X, which occurred more recently than with Employee Y.

In any of these implementations, the Recent Contacts group 812 only may include the screen name of a particular person that is not included in any other group.

Next, the first subscriber views a UI 900 indicating the online status of an intended recipient of an instant message. In this example, the first subscriber intends to send an instant message to the second subscriber. Here, the screen name of the second subscriber (ProductRep) was not actively added to the UI 900 by the first subscriber. Rather, the screen name (ProductRep) was added passively to the Recent Contacts group 812 when the first subscriber and second subscriber established used, closed or disconnected a prior successful IM session. By viewing the UI 900 and, in particular, the Recent Contacts list 842, the first subscriber is notified that the second subscriber is online. Namely, the screen name of the second subscriber (ProductRep) appears as one of the online Recent Contact members 844.

The first subscriber then sends an instant message intended for the second subscriber by interacting with the UI 900. For example, the first subscriber can invoke display of an IM UI 1000 pre-addressed to the second subscriber by clicking the screen name of the second subscriber (ProductRep) in the Recent Contacts list 842. The first subscriber enters the first instant message 708 into the text message area 710 and clicks one of the IM buttons 720, namely the send button. Finally, the first subscriber displays the second instant message 709 (i.e., the reply from the second subscriber) in the IM window 705.

Passively configuring a user profile, and hence a passively configured subscriber buddy list, benefits subscribers by facilitating IM communication. For example, a subscriber can view the online status of and create pre-addressed instant messages to recent IM contacts. This feature is particularly helpful to new IM users who would otherwise have to spend time and effort setting user preferences and entering data. Additionally, it is helpful to subscribers who accidentally or intentionally close sessions with IM contacts for whom they have no other record of their screen name, only to need that screen name for later IM contact. The persistent state of the recent IM contacts list enables the list to persist through log-outs and power downs.

Additionally, a passively configured user profile, and hence a passively configured subscriber buddy list, may be made accessible through any of several different devices independent of the device that was being used at the time of the IM session that resulted in the passive addition of or status change with respect to the IM contact in the Recent Contacts group. For example, in a client-host model, the profile may be stored at the host or some other location centrally accessible to various client devices operable by the subscriber. As a result, a first subscriber may participate in an instant messaging session with a second subscriber using a personal computer. At the end of the instant messaging session, the screen name of the second subscriber may be passively added to the first subscriber's Recent Contacts group. When the first subscriber later uses a PDA to access the IM service, the first subscriber's Recent Contacts group may be presented on the PDA. In this instance, the Recent Contacts group includes the screen name of the second subscriber that was added to the group based on the IM session that the first subscriber participated in using the personal computer. This enables the first subscriber to initiate another IM session with the second subscriber by selecting the second subscriber's screen name from the Recent Contacts group presented on the PDA. Thus, the passively configured buddy list, specifically the Recent Contact Group, persists across different devices.

In one implementation, a passively configured user profile and/or a passively configured buddy list may include information from communication sessions other than IM sessions. Referring to FIG. 12, a sender 1202a, a recipient 1202b, and a host 1204 exchange communications according to a procedure 1200. The procedure 1200 may be implemented by any suitable type of hardware (e.g., device, computer, computer system, equipment, component); software (e.g., program, application, instructions, code); storage medium (e.g., disk, external memory, internal memory, progated signal); or combination thereof.

Examples of each element of FIG. 12 are broadly described with respect to FIGS. 1-5 above. In particular, the sender 1202a and the recipient 1202b may have attributes comparable to those described above with respect to client devices 120, 220, 320, 420, and 520 and/or client controllers 125, 225, 325, 425, and 525. The host 1204 may have attributes comparable to those described above with respect to host devices 135, 235, 335, 435, and 535 and/or host controllers 140, 240, 340, 440, and 540. The sender 1202a, the recipient 1202b, and/or the host 1204 may be directly or indirectly interconnected through a known or described delivery network, such as delivery networks 160, 260, 360, 460, and 560.

More specifically, the sender 1202a may include a subscriber and/or a client (e.g., client system 505), and the host 1204 may include one or more host complexes (e.g., OSP host complex 580 and/or IM host complex 590) for providing communications capabilities and coordinating the transfer of electronic and/or voice data between subscribers. The sender 1202a may access the host 1204 using any available device and/or controller. In the implementation of FIG. 12, a sender 1202a, a recipient 1202b, and a host 1204 interact according to a procedure 1200 that extends the functionality of IM by passively personalizing the buddy list of at least one of the senders 1202a and the recipient 1202b based on IM communication sessions and other types of communication sessions involving the sender 1202a and the recipient 1202b. Communication sessions other than IM sessions may include an e-mail communication session, a phone communication session (e.g., a wired or wireless phone communication session), a voice over IP (VoIP) communication session, and other types of communication sessions. Hence, the sender 1202a and/or recipient 1202b may include devices capable of enabling such alternative communication sessions (e.g., phone, VoIP, e-mail).

Initially, the sender 1202a accesses the host 1204 (step 1206). The sender 1202a designates at least one recipient 1202b with which to communicate, for example, by means other than IM (step 1208). The communication may be, for example, an e-mail, a phone conversation, or a voice over IP conversation initiated by the sender 1202a. In one implementation, when the communication is an e-mail message, the e-mail message may include header information identifying the message, the screen name and/or IP addresses of the sender 1202a and the recipient 1202b.

The sender 1202a then communicates with the recipient 1202b by transmitting a communication to the host (step 1210). The host 1204 receives the communication from the sender 1202a (step 1212) and then optionally authenticates the communication (step 1214). A server on the host 1204 may authenticate the communication by matching the screen names and/or IP addresses with those of valid subscribers stored in a look-up table (e.g., a reverse look-up table). In the event that either the sender 1202a or the recipient 1202b is not associated with a valid subscriber, the host 1204 reports an error message. The host 1204 then sends the communication to the recipient 1202b (step 1216) and the recipient 1202b receives the communication from the host (step 1218).

During a communication session, the host 1204 may moderate the communication session (step 1220). In one implementation, a server on the host 1204 is configured to moderate a communication session between at least one sender 1202a and at least one recipient 1202b. Moderating the communication session may include managing load conditions of the host 1204 by compressing, decompressing, caching, and/or allocating resources to store and forward communications.

Moderating the communication session (step 1220) also may include updating a communication log. In general, a communication log includes an organized (e.g., chronological and/or categorized) record of communication activity (e.g., the existence or status of separate and/or successful e-mail communications, phone communication sessions, voice over IP sessions, or the connection or disconnection with the host). The communication log may be stored and maintained on the host 1204 (e.g., by database 5914 of IM host 590), the sender 1202a (e.g., by memory 272 of the sender client device), and/or the recipient 1202b (e.g., by memory 272 of the recipient client device). Entries in the communication log may be ordered, deleted, edited, and/or otherwise managed by the host 1204, the sender 1202a, and/or the recipient 1202b. For example, the host 1204 may queue, order, and arrange entries in the communication log based on time, subscribers (e.g., screen names), topic, relevance, phone number, IP address, and/or other ranking criteria.

Typically, each subscriber will have a corresponding communication log for recording communication activity of the subscriber. However, the communication log may be associated with a group of subscribers, or may simply be used to chronologically log activities of all subscribers communicating over or with the device used to maintain or store the log.

Updating the communication log (step 1220) may include deriving and/or recording identifiers (e.g., screen names, aliases, or names) of participants of the communication session, whether an IM session or session type other than an IM. The sender 1202a, the recipient 1202b, and/or the host 1204 may be configured to detect at least one identity (e.g., the screen name) associated with a communication during a communication session, for example, by parsing the header information of an e-mail. For a phone communication, a phone number of the sender 1202a and/or the recipient 1202b may be detected (e.g., from ANI information accompanying communication packets or otherwise associated with the communication session) and/or reported to the host. The phone number may be used to derive the screen names of the participants of the phone conversation.

A list of screen names for the most recent communications including communications other than instant messages may be derived from the communication log automatically (step 1222). The sender 1202a, the recipient 1202b, and/or the host 1204 may be configured to derive such a list, which may be limited by various preselection criteria such as a number (N) of communications of a selected type or of all types collectively aggregated, or a proximity in the time of the communication to the time of the display. For example, at any time, the last N different screen names with whom a particular subscriber has had a communication session may be determined from an updated communication log. The number N may be any predetermined number set according to preferences of the sender 1202a, the recipient 1202b, and/or the host 1204, or it may be user-selectable. The manner for storing and ordering the communication log may be as described above with respect to the IM log of FIG. 6.

After a list of N different screen names is compiled, the user profile is accessed (step 1224) and passively configured (step 1226). That is, the configuration or reconfiguration of the user profile may occur transparently to the subscriber and may require no overt action by the subscriber (e.g., selection by the subscriber). Configuration of the user profile may include the creating and/or modifying of a subscriber's user preferences such as, for example, one or more buddy lists, address book, calendar, notification settings (e.g., alerts), or any other personalized attributes associated with the subscriber.

In one implementation, a buddy list included in a subscriber's user profile is configured based on the updated communication log. In particular, a buddy list associated with at least one of the sender 1202a and the recipient 1202b may be configured to include a list of most recent contacts from communication sessions other than IM sessions (step 1226). The passively configured list of most recent contacts may be displayed in a user interface (step 1228).

As described above with respect to UI 800 of FIG. 8 and UI 900 of FIG. 9, the user interfaces may be passively configured to include a Recent Contacts group for communication sessions. The Recent Contacts group may reflect communication sessions having a type other than an IM session. For instance, a Recent Contacts group for communication sessions other than IM sessions may be included as an integrated and/or distinct subset of the Recent Contacts group that also includes recent contacts from IM sessions, it may be a separate group unto itself, or it may be further split into one or more groups based on the type of communication session with which the recent contact occurred. For example, there may be a Recent Contacts E-mail group, a Recent Contacts Phone group, and/or a Recent Contacts for Voice Over IP group, which may be displayed as subsets of or which may be substituted for the Recent Contacts group shown by FIGS. 8 and 9.

FIG. 13a illustrates a UI 1300 that may be passively configured and includes a Buddy List Window 1305 having a List Setup box 1310. The List Setup box 1310 includes one or more IM groups, for example, a Recent Contacts group 1312. In this example, the Recent Contacts group 1312 includes subset groups of Recent Contacts groups such as, for example, a Recent IM Contacts group 1314, a Recent E-mail Contacts group 1316, a Recent Voice Over IP Contacts group 1318, and a Recent Phone Contacts group 1320. UI 1300 also may be displayed using the Online box tab.

FIG. 13b illustrates a UI 1350 that may be passively configured and includes a Buddy List window 1355 having a List Setup box 1360. The List Setup box 1360 includes one or more IM groups, for example, a Recent IM Contacts group 1362, a Recent E-mail Contacts group 1364, a Recent Voice Over IP Contacts group 1366, and a Recent Phone Contacts group 1368. In this example, the IM groups are independent of a parent Recent Contacts group and instead are separate IM groups. UI 1350 also may be displayed using the Online box tab.

Additionally, UI 1300 of FIG. 13a and UI 1350 of FIG. 13b may be configured (e.g., passively configured) to display other types of information to a user in addition to or in substitution of that described above. In one implementation, for example, UI 1300 and UI 1350 may include information for group members other than or in addition to the screen names for group members, such as, for example, contact information (e.g., phone numbers, e-mail addresses, and mailing addresses). The contact information may be obtained from a user profile that may be stored and maintained on the host 604 of FIG. 6 (e.g., IM host 590, database 5914), the sender 602a of FIG. 6 (e.g., client device, memory 272), and/or the recipient 602b of FIG. 6 (e.g., client device, memory 272).

FIG. 14 illustrates a UI 1400 that may be used to display information from the user profile and includes a Buddy List window 1405 having a List Setup box 1410. The information also may be displayed using the Online box tab. The List Setup box 1410 includes one or more groups, such as, for example, a Recent IM Contacts group 1412, a Recent E-mail Contacts group 1414, a Recent Voice Over IP Contacts group 1416, and a Recent Phone Contacts group 1418. The information displayed by each group is passively configured to include identifiers (e.g., screen names, aliases, or names) and/or other contact information (e.g., e-mail addresses, phone numbers, mailing addresses) derived from the communications log and user profile based on recent communication sessions (e.g., IM sessions, e-mail sessions, voice over IP sessions, and phone sessions).

The information displayed under each group may be based on the type of recent communication session that caused the information to be displayed. For example, with respect to an identity with whom communications were recently conducted or closed, whether by IM or otherwise, the Recent IM Contacts group 1412 may be passively configured to display an identifier (e.g., a screen name, alias, or name) reflecting information useful in establishing communications with entities with whom IM sessions were recently established or closed/discontinued. This information may include a screen name of the entity (e.g., if they are available online), or it may include other information reflecting contact information for session types other than IM (e.g., VoIP, e-mail, etc).

Similarly, for example, with respect to an identity with whom communications were recently conducted or closed, whether by e-mail or otherwise, the Recent E-mail Contacts group 1414 may be passively configured to display an identifier (e.g., screen name, alias, or name) useful in establishing communications with entities with whom e-mail sessions were recently established or closed/discontinued. This information may include an e-mail address of the entity, or it may include other information reflecting contact information for session types other than e-mail (e.g., IM, VoIP, e-mail, etc).

Similarly, for example, with respect to an identity with whom communications were recently conducted or closed, whether by VoIP or otherwise, the Recent Voice over IP Contacts group 1416 may be passively configured to display an identifier (e.g., screen name, alias, or name) useful in establishing communications with entities with whom VoIP sessions were recently established or closed/discontinued. This information may include information for establishing a VoIP session, or it may include other information reflecting contact information for session types other than VoIP (e.g., IM, VoIP, e-mail, etc).

Similarly, for example, with respect to an identity with whom communications were recently conducted or closed, whether by telephony or otherwise, the Recent Phone Contacts group 1418 may be passively configured to display an identifier (e.g., screen name, alias, or name) useful in establishing communications with entities with whom telephony sessions were recently established or closed/discontinued. This information may include a telephone number of the identity, or it may include other information reflecting contact information for session types other than telephony (e.g., IM, VoIP, e-mail, etc).

The information displayed within each Contacts group may be used to initiate a communication session using one or more particular types of communications. For example, selecting (e.g., clicking) an identifier listed in the Recent IM Contacts group 1412 may invoke a pre-addressed IM window (UI 1000 of FIG. 10) to enable an IM session. Selecting an identifier and/or an e-mail address listed in the Recent E-mail Contacts group 1414 may invoke a pre-addressed interface to send an e-mail to the recent e-mail contact and/or may invoke a pre-addressed IM window to enable an IM session. The user may be able to select the type of communication to be used or a default communication type may be selected for the user when more than one type of communication is available for an entity identified by the Recent Contacts group or one or more of the Recent Contact subgroups or substitutes.

For example, if the recent e-mail contact is detected to be online, an IM communication may be selected as the default. If the IM communication is not available, for instance, because the recent e-mail contact is not online, then another communication type may be used (e.g., an e-mail communication or a phone communication). Selecting an identifier and/or the displayed Voice over IP information listed in the Recent Voice over IP Contacts group 1416 may invoke a voice over IP interface and/or initiate a voice over IP communication session with the recent voice over IP contact, and also may invoke a pre-addressed IM window to enable an IM session. Selecting an identifier and/or a phone number listed in the Recent Phone Contacts group 1418 may invoke a phone interface and/or initiate a phone communication session with the recent phone contact, and also may invoke a pre-addressed IM window to enable an IM session. Presence information may be useful in discerning which of several alternative communication schemes is available or most appropriate, and even to chose between several non-IM communication types.

The contact information (e.g., screen name, e-mail address, phone number, or VoIP contact information) within each group may be hidden, may be explicitly displayed or may be revealed by moving a pointing device over the information that is displayed to reveal additional information. For example, when default contact information is displayed irrespective of entity availability, the cursor may be moved over information displayed in the Recent Contacts group to reveal additional contact information, such as, for example, an e-mail address or a phone number to supplement a display that is limited to screen name. Revealing the additional information is useful when a particular communication type is not available, for example, where a screen name is displayed for an entity that is not online. When this occurs, a communication session over an alternate communication type may be established using the additional information that is explicitly displayed or revealed.

In one implementation, a passively configured user profile, and, thus, a passively configured subscriber buddy list including one or more types of recent contact groups, may be made accessible through any of several different devices independent of the device that was being used at the time of the communication session that resulted in the passive addition of or status change with respect to the recent contact in one or more of the Recent Contact group types. For example, in a client-host model, the user profile and communication log may be stored at the host or at some other location centrally accessible to various client devices operable by the subscriber. Thus, the passively configured subscriber buddy list may be maintained at the host and may be made accessible to multiple different devices. Alternatively, the passively configured subscriber buddy list may be made accessible to one device and then pushed and/or pulled from device-to-device.

As a result, a subscriber may participate in an e-mail session with an e-mail contact using a personal computer. An identifier and/or e-mail address of the recent e-mail contact may be passively added to the subscriber Recent E-mail Contacts group. Concurrently, an identifier and/or e-mail address for that recent e-mail contact also may be reflected within the subscriber's Recent Contact group (e.g., Recent E-mail Contacts group) presented on another device (e.g., a PDA). The subscriber may select the identifier and/or e-mail address to initiate a communication session (e.g., an e-mail session or an IM session) with the recent e-mail contact from either device. Similarly, other recent contacts from all of the communication types may be presented to the user across multiple devices to enable different types of communication sessions to be initiated from one or more of the devices.

In one implementation, the sender 1202a may not need to transmit the communication to the host 1204 (step 1210) and instead may transmit the communication directly to the recipient 1202b without sending the communication through the host 1204. In this case, steps 1210, 1212, 1214, and 1216 may be optional. In this instance, the host 1204 may be notified by the sender 1202a, by the recipient 1202b and/or by a third-party that a communication session other than an IM session occurred between the sender 1202a and the recipient 1202b. Upon such notification, the host 1204 updates a communication log for the sender 1202a and the recipient 1202b (step 1220), derives identifiers for the sender 1202a and the recipient 1202b (step 1222), accesses the user profile for the sender 1202a and the recipient 1202b (e.g., buddy list) (step 1224), and passively configures the user profile (step 1226) based upon the received notification. Additionally or alternatively, the sender 1202a or the recipient 1202b may update a communication log for the sender 1202a and the recipient 1202b (step 1220), derive identifiers for the sender 1202a and the recipient 1202b (step 1222), access the user profile for the sender 1202a and the recipient 1202b (e.g., buddy list) (step 1224) and passively configure the user profile (step 1226).

More specifically, a phone communication may take place between the sender 1202a and the recipient 1202b without communicating the phone conversation through the host 1204. In this case, the host 1204 may be notified by the sender 1202a, by the recipient 1202b, or by a third party (e.g., a telephone carrier) that a communication session occurred between the sender 1202a and the recipient 1202b. The host 1204 then may update a communication log for the sender 1202a and the recipient 1202b (step 1220), derive screen names for the sender 1202a and the recipient 1202b (step 1222), access the user profile for the sender 1202a and the recipient 1202b (e.g., buddy list) (step 1224) and passively configure the user profile (step 1226) based upon the received notification.

A number of implementations have been described. Nevertheless, it will be understood that various modifications may be made. In other implementations, for example, other groups (e.g., Frequent Contacts, Popular Contacts) may be passively created and maintained in a persistent state in order to facilitate instant messaging. In yet other implementations, for example, other groups and lists may be passively created and maintained in a persistent state in order to facilitate instant messaging. These other groups and lists may include instant messages received; knock-knocks received (i.e., instant messages received from unknown identities), but accepted and/or declined; instant messages sent without receiving a response; instant messages sent to Buddies; instant messages sent to non-Buddies; IM sessions where at least a threshold number of messages have been exchanged; and instant messages received to the exclusion of knock-knocks.

Other implementations are within the scope of the following claims.

Claims

1. A method comprising: accessing information for communications sessions by a user of a communication system and a plurality of other users of the communication system;generating, based on one or more interactions between the user and the plurality of other users, a recent contact group having a fixed size and comprising a subset of the plurality of other users who have had recent interactions with the user;providing the recent contact group for display to the user;detecting, after generating the recent contact group, one or more additional interactions between the user and a first co-user from the plurality of other users who is not in the recent contact group;identifying, upon detecting the one or more additional interactions between the user and the first co-user, a second co-user from among the subset of the plurality of other users who have had recent interactions with the user and having had the least recent interactions with the user from among the subset of the plurality of other users;modifying, based on the one or more additional interactions between the user and the first co-user, the recent contact group by adding the first co-user to the recent contact group and removing the second co-user from the recent contact group; andproviding the modified recent contact group for display to the user.
2. The method of claim 1, further comprising persistently maintaining the recent contact group associated with the user at the communication system.
3. The method of claim 1, further comprising monitoring a communication availability of the subset of other users corresponding to an offline status or online status of the subset of other users relative to the communication system; and organizing the subset of other users within the recent contact group based on the communication availability of the subset of other users.
4. The method of claim 1, wherein modifying the recent contact group further comprises reordering the subset of other users in the recent contact group.
5. The method of claim 4, wherein reordering the subset of other users in the recent contact group comprises listing the users within the subset of other users based on recency of communication.
6. The method of claim 1, wherein modifying the recent contact group further comprises decreasing the fixed size of the recent contact group and removing a user from the recent contact group.
7. The method of claim 1, further comprising receiving, as a user preference, a predetermined number of users to include within the recent contact group.
8. The method of claim 1, further comprising storing the recent contact group at a communication server of the communication system together with a user profile associated with the user.
9. The method of claim 1, further comprising maintaining information associated with the user of the communication system.
10. The method of claim 9, wherein the information associated with the user of the communication system comprises a buddy list, the buddy list comprising a second subset of other users from the plurality of other users, wherein the buddy list is configured to allow the user to monitor a communication availability of the second subset of other users and initiate one or more communications with the second subset of other users.
11. The method of claim 10, further comprising: detecting an interaction between the user and a co-user from the second subset of other users; andpreserving the co-user from the second subset of others users in the recent contact group based on the interaction between the user and the co-user from the second subset of other users.
12. A method, comprising: generating, based on one or more interactions between a user and a plurality of other users, a recent contact group having a fixed size and comprising a subset of other users from the plurality of other users, the subset of other users having had recent interactions with the user;providing the recent contact group for display to the user;detecting, by at least one processor and after generating the recent contact group, one or more additional interactions between the user and one or more co-users from the plurality of other users who were not in the recent contact group;identifying, upon detecting the one or more additional interactions between the user and the one or more co-users, a first co-user from the one or more co-users from the plurality of other users who were not in the recent contact group and having had the most recent interactions with the user; andidentifying, upon detecting the one or more additional interactions between the user and one or more co-users, a second co-user from among the subset of the plurality of other users who have had recent interactions with the user and having had the least recent interactions with the user from among the subset of the plurality of other users;modifying the recent contact group based on the one or more additional interactions between the user and the one or more co-users by adding the first co-user to the subset of other users of the recent contact group and removing the second co-user from the recent contact group; andproviding the modified recent contact group for display to the user.
13. The method of claim 12, wherein modifying the recent contact group further comprises rearranging an order of the recent contact group.
14. The method of claim 13, wherein rearranging the order of the recent contact group comprises rearranging the order based on a recency of communications.
15. The method of claim 12, further comprising maintaining information associated with the user that comprises a buddy list, the buddy list comprising a second subset of other users from the plurality of users, wherein the buddy list is configured to allow the user to monitor a communication availability of the second subset of other users and initiate one or more communications with the second subset of other users.
16. The method of claim 15, wherein the subset of other users within the recent contact group do not overlap the second subset of other users within the buddy list.
17. A system comprising: at least one processor; andat least one non-transitory computer readable storage medium storing instructions that, when executed by the at least one processor, cause the system to:generate, based on one or more interactions between a user and a plurality of other users, a recent contact group having a fixed size and comprising a subset of other users from the plurality of other users;provide the recent contact group for display to the user;detect, after generating the recent contact group, one or more additional interactions between the user and a first co-user from the plurality of other users who is not in the recent contact group;identify, upon detecting the one or more additional interactions between the user and the first co-user, a second co-user from among the subset of the plurality of other users who have had recent interactions with the user and having had the least recent interactions with the user from among the subset of the plurality of other users;modify, based on the one or more additional interactions between the user and the co-user from the plurality of other users by adding the first co-user to the recent contact group and removing the second co-user from the recent contact group; andprovide the modified recent contact group for display to the user.
18. The system of claim 17, further comprising instructions that, when executed by the at least one processor, cause the system to, based on one or more further interactions, reorder the subset of other users within the recent contact group; remove a user from the recent contact group; and add a user to the recent contact group.
19. The system of claim 17, further comprising instructions that, when executed by the at least one processor, cause the system to maintain the fixed size of the recent contact group as a predetermined number of users within the recent contact group set according to preferences of the user.
20. The method of claim 1, further comprising providing, within the recent contact group, an indication of a communication platform associated with each co-user in the recent contact group, wherein the indication of the communication platform indicates one or more of a plurality of communication platforms through which communication with each co-user is available.
21. The method of claim 20, further comprising: receiving, from the user, a selection of a co-user from the recent contact group; andinitiating, in response to the received selection, a communication session between the user and the co-user via a communication platform corresponding to an indication of a communication platform associated with the co-user.
22. The method of claim 10, wherein providing the recent contact group for display to the user consists of enabling presentation of the recent contact group within the buddy list.

CROSS REFERENCE TO RELATED APPLICATIONS

The present application is a continuation of U.S. application Ser. No. 12/336,880, filed Dec. 17, 2008, which is a continuation of U.S. application Ser. No. 10/184,002, filed Jun. 28, 2002, which is now issued as U.S. Pat. No. 7,512,652, which is a continuation in part of U.S. application Ser. No. 10/134,437, filed Apr. 30, 2002, which is now issued as U.S. Pat. No. 7,765,484, which claims the benefit of and priority to U.S. provisional application No. 60/325,084, filed Sep. 28, 2001.

US Referenced Citations (285)

Number	Name	Date	Kind
4837798	Cohen et al.	Jun 1989	A
5086394	Shapira	Feb 1992	A
5276905	Hurst et al.	Jan 1994	A
5327486	Wolff et al.	Jul 1994	A
5533110	Pinard et al.	Jul 1996	A
5548637	Heller et al.	Aug 1996	A
5557659	Hyde-Thomson	Sep 1996	A
5583920	Wheeler, Jr.	Dec 1996	A
5608786	Gordon	Mar 1997	A
5610910	Focsaneanu et al.	Mar 1997	A
5650994	Daley	Jul 1997	A
5694616	Johnson et al.	Dec 1997	A
5721906	Siefert	Feb 1998	A
5742905	Pepe et al.	Apr 1998	A
5764916	Busey et al.	Jun 1998	A
5774670	Montulli	Jun 1998	A
5790800	Gauvin et al.	Aug 1998	A
5793365	Tang et al.	Aug 1998	A
5802470	Gaulke et al.	Sep 1998	A
5835724	Smith	Nov 1998	A
5848134	Sekiguchi et al.	Dec 1998	A
5850594	Cannon et al.	Dec 1998	A
5859979	Tung et al.	Jan 1999	A
5867162	O'Leary et al.	Feb 1999	A
5870744	Sprague	Feb 1999	A
5872521	Lopatukin et al.	Feb 1999	A
5878219	Vance, Jr. et al.	Mar 1999	A
5893091	Hunt et al.	Apr 1999	A
5893099	Schreiber et al.	Apr 1999	A
5919247	Van Hoff et al.	Jul 1999	A
5920692	Nguyen et al.	Jul 1999	A
5940488	DeGrazia et al.	Aug 1999	A
5946617	Portaro et al.	Aug 1999	A
5948058	Kudoh et al.	Sep 1999	A
5951643	Shelton et al.	Sep 1999	A
5951646	Brandon	Sep 1999	A
5951652	Ingrassia, Jr. et al.	Sep 1999	A
5954798	Shelton et al.	Sep 1999	A
5956716	Kenner et al.	Sep 1999	A
5960173	Tang et al.	Sep 1999	A
5983369	Bakoglu et al.	Nov 1999	A
5987113	James	Nov 1999	A
5987407	Wu et al.	Nov 1999	A
5991791	Siefert	Nov 1999	A
5995023	Kreft	Nov 1999	A
6002402	Schacher	Dec 1999	A
6006179	Wu et al.	Dec 1999	A
6009413	Webber et al.	Dec 1999	A
6012051	Sammon, Jr. et al.	Jan 2000	A
6014135	Fernandes	Jan 2000	A
6014638	Burge et al.	Jan 2000	A
6026403	Siefert	Feb 2000	A
6026429	Jones et al.	Feb 2000	A
6065047	Carpenter et al.	May 2000	A
6070171	Snyder et al.	May 2000	A
6073138	De l'Etraz et al.	Jun 2000	A
6081830	Schindler	Jun 2000	A
6085223	Carino, Jr. et al.	Jul 2000	A
6088435	Barber et al.	Jul 2000	A
6049533	Holmes et al.	Oct 2000	A
6134432	Holmes et al.	Oct 2000	A
6144991	England	Nov 2000	A
6151584	Papierniak et al.	Nov 2000	A
6161130	Horvitz et al.	Dec 2000	A
6166730	Goode et al.	Dec 2000	A
6175831	Weinreich et al.	Jan 2001	B1
6192395	Lemer et al.	Feb 2001	B1
6195354	Skalecki et al.	Feb 2001	B1
6199103	Sakaguchi et al.	Mar 2001	B1
6212548	DeSimone et al.	Apr 2001	B1
6212550	Segur	Apr 2001	B1
6223213	Cleron et al.	Apr 2001	B1
6233577	Ramasubramani et al.	May 2001	B1
6249740	Ito et al.	Jun 2001	B1
6260148	Aggarwal et al.	Jul 2001	B1
6269369	Robertson	Jul 2001	B1
6301609	Aravamudan et al.	Oct 2001	B1
6311211	Shaw	Oct 2001	B1
6314450	Hachiya et al.	Nov 2001	B1
6317776	Broussard et al.	Nov 2001	B1
6324541	De l'Etraz et al.	Nov 2001	B1
6330590	Cotten	Dec 2001	B1
6347332	Malet et al.	Feb 2002	B1
6351698	Kubota et al.	Feb 2002	B1
6363392	Halstead et al.	Mar 2002	B1
6374246	Matsuo	Apr 2002	B1
6374290	Scharber et al.	Apr 2002	B1
6389127	Vardi et al.	May 2002	B1
6389372	Glance et al.	May 2002	B1
6393464	Dieterman	May 2002	B1
6400381	Barrett et al.	Jun 2002	B1
6405035	Singh	Jun 2002	B1
6405249	Matsuda et al.	Jun 2002	B1
6415318	Aggarwal et al.	Jul 2002	B1
6421439	Liffick	Jul 2002	B1
6421709	McCormick et al.	Jul 2002	B1
6425012	Trovato et al.	Jul 2002	B1
6306004	Ogle et al.	Aug 2002	B1
6430344	Dixon et al.	Aug 2002	B1
6430604	Ogle et al.	Aug 2002	B1
6446112	Bunney et al.	Sep 2002	B1
6449344	Goldfinger et al.	Sep 2002	B1
6449634	Capiel	Sep 2002	B1
6480885	Olivier	Nov 2002	B1
6484196	Maurille	Nov 2002	B1
6501834	Milewski et al.	Dec 2002	B1
6507866	Barchi	Jan 2003	B1
6525747	Bezos	Feb 2003	B1
6529475	Wan et al.	Mar 2003	B1
6535586	Cloutier et al.	Mar 2003	B1
6539421	Appelman et al.	Mar 2003	B1
6549937	Auerbach et al.	Apr 2003	B1
6557027	Cragun	Apr 2003	B1
6559863	Megiddo	May 2003	B1
6564248	Budge et al.	May 2003	B1
6564261	Gudjonsson et al.	May 2003	B1
6571234	Knight et al.	May 2003	B1
6574599	Lim et al.	Jun 2003	B1
6580790	Henry et al.	Jun 2003	B1
6615241	Miller et al.	Sep 2003	B1
6636733	Helferich	Oct 2003	B1
6640230	Alexander et al.	Oct 2003	B1
6654683	Jin et al.	Nov 2003	B2
6677968	Appelman	Jan 2004	B1
6677976	Parker et al.	Jan 2004	B2
6678719	Stimmel	Jan 2004	B1
6691162	Wick	Feb 2004	B1
6697807	McGeachie	Feb 2004	B2
6701348	Sommerer	Mar 2004	B2
6714519	Luzzatti et al.	Mar 2004	B2
6714791	Friedman	Mar 2004	B2
6714793	Carey et al.	Mar 2004	B1
6731308	Tang et al.	May 2004	B1
6732155	Meek	May 2004	B2
6738822	Fukasawa et al.	May 2004	B2
6747970	Lamb et al.	Jun 2004	B1
6748421	Ozkan et al.	Jun 2004	B1
6750881	Appelman	Jun 2004	B1
6757365	Bogard	Jun 2004	B1
6757732	Sollee et al.	Jun 2004	B1
6772188	Cloutier	Aug 2004	B1
6781608	Crawford	Aug 2004	B1
6785554	Amerga	Aug 2004	B1
6785681	Keskar	Aug 2004	B2
6788769	Waites	Sep 2004	B1
6795863	Doty	Sep 2004	B1
6799039	Wu et al.	Sep 2004	B2
6800031	Di Cesare	Oct 2004	B2
6807574	Partovi et al.	Oct 2004	B1
6839737	Friskel	Jan 2005	B1
6857006	Nishizawa	Feb 2005	B1
6879665	Cook et al.	Apr 2005	B1
6901559	Blum et al.	May 2005	B1
6907243	Tarnanen et al.	Jun 2005	B1
6912563	Parker et al.	Jun 2005	B1
6912564	Appelman et al.	Jun 2005	B1
6917965	Gupta et al.	Jul 2005	B2
6920478	Mendiola et al.	Jul 2005	B2
6941345	Kapil et al.	Sep 2005	B1
6952805	Tafoya et al.	Oct 2005	B1
6968179	DeVries	Nov 2005	B1
6993564	Whitten	Jan 2006	B2
6996520	Levin	Feb 2006	B2
7035865	Doss et al.	Apr 2006	B2
7039676	Day et al.	May 2006	B1
7043530	Isaacs et al.	May 2006	B2
7058036	Yu et al.	Jun 2006	B1
7058690	Maehiro	Jun 2006	B2
7065186	Myers et al.	Jun 2006	B1
7082047	Chow	Jul 2006	B2
7082407	Bezos et al.	Jul 2006	B1
7120687	Tessman	Oct 2006	B1
7124123	Roskind et al.	Oct 2006	B1
7127232	O'Neil et al.	Oct 2006	B2
7171473	Eftis et al.	Jan 2007	B1
7177880	Ruvolo	Feb 2007	B2
7185059	Daniell et al.	Feb 2007	B2
7190956	Dorenbosch et al.	Mar 2007	B2
7200634	Mendiola et al.	Apr 2007	B2
7202814	Caspi et al.	Apr 2007	B2
7222156	Gupta et al.	May 2007	B2
7233992	Muldoon et al.	Jun 2007	B1
7275215	Werndorfer et al.	Sep 2007	B2
7313760	Grossman et al.	Dec 2007	B2
7436780	Stephens et al.	Oct 2008	B2
7437413	Okuyama et al.	Oct 2008	B2
7512652	Appelman et al.	Mar 2009	B1
7765484	Roskind	Jul 2010	B2
20010005861	Mousseau et al.	Jun 2001	A1
20010013050	Shah	Aug 2001	A1
20010032246	Fardella et al.	Oct 2001	A1
20010052019	Walters et al.	Dec 2001	A1
20020015061	Maguire	Feb 2002	A1
20020021307	Glenn et al.	Feb 2002	A1
20020023132	Tornabene et al.	Feb 2002	A1
20020023134	Roskowski et al.	Feb 2002	A1
20020028595	Higashi et al.	Mar 2002	A1
20020035605	McDowell et al.	Mar 2002	A1
20020049717	Routtenberg et al.	Apr 2002	A1
20020052816	Bae	May 2002	A1
20020056123	Liwerant et al.	May 2002	A1
20020065856	Kisiel	May 2002	A1
20020065894	Dalal et al.	May 2002	A1
20020076025	Liversidge	Jun 2002	A1
20020077080	Greene	Jun 2002	A1
20020083136	Whitten	Jun 2002	A1
20020091667	Jaipuria et al.	Jul 2002	A1
20020103801	Lysons	Aug 2002	A1
20020112181	Smith	Aug 2002	A1
20020116463	Hart	Aug 2002	A1
20020116641	Mastrianni	Aug 2002	A1
20020133292	Miyaki	Sep 2002	A1
20020133369	Johnson	Sep 2002	A1
20020147777	Hackbarth et al.	Oct 2002	A1
20020174010	Rice	Nov 2002	A1
20020175953	Lin	Nov 2002	A1
20020181703	Logan et al.	Dec 2002	A1
20020184089	Tsou et al.	Dec 2002	A1
20020193942	Odakura et al.	Dec 2002	A1
20020199095	Bandini et al.	Dec 2002	A1
20030004855	Dutta et al.	Jan 2003	A1
20030004872	Gardi et al.	Jan 2003	A1
20030009523	Lindskog et al.	Jan 2003	A1
20030018726	Low et al.	Jan 2003	A1
20030023875	Hursey et al.	Jan 2003	A1
20030028524	Keskar et al.	Feb 2003	A1
20030028595	Vogt et al.	Feb 2003	A1
20030037112	Fitzpatrick et al.	Feb 2003	A1
20030043201	Abdelhadi et al.	Mar 2003	A1
20030046198	Knapp et al.	Mar 2003	A1
20030050916	Ortega et al.	Mar 2003	A1
20030084103	Weiner et al.	May 2003	A1
20030093580	Thomas et al.	May 2003	A1
20030105822	Gusler et al.	Jun 2003	A1
20030131061	Newton et al.	Jul 2003	A1
20030140103	Szeto et al.	Jul 2003	A1
20030158855	Farnham et al.	Aug 2003	A1
20030167324	Farnham et al.	Sep 2003	A1
20030182394	Ryngler et al.	Sep 2003	A1
20030187813	Goldman et al.	Oct 2003	A1
20030212804	Hashemi	Nov 2003	A1
20030225847	Heikes et al.	Dec 2003	A1
20030236835	Levi et al.	Dec 2003	A1
20040015548	Lee	Jan 2004	A1
20040054729	Fukuizumi et al.	Mar 2004	A1
20040056901	March et al.	Mar 2004	A1
20040117443	Barsness	Jun 2004	A1
20040122681	Ruvolo	Jun 2004	A1
20040122810	Mayer	Jun 2004	A1
20040122855	Ruvolo	Jun 2004	A1
20040128356	Bernstein et al.	Jul 2004	A1
20040179039	Blattner et al.	Sep 2004	A1
20040186738	Reisman	Sep 2004	A1
20040210844	Pettinati et al.	Oct 2004	A1
20040215648	Marshall et al.	Oct 2004	A1
20040215721	Szeto et al.	Oct 2004	A1
20040260762	Fish	Dec 2004	A1
20050015432	Cohen	Jan 2005	A1
20050021750	Abrams	Jan 2005	A1
20050027382	Kirmse et al.	Feb 2005	A1
20050038856	Krishnasamy et al.	Feb 2005	A1
20050043989	Shifrin	Feb 2005	A1
20050044152	Hardy et al.	Feb 2005	A1
20050050143	Gusler et al.	Mar 2005	A1
20050060377	Lo et al.	Mar 2005	A1
20050076241	Appelman	Apr 2005	A1
20050080863	Daniell	Apr 2005	A1
20050086211	Mayer	Apr 2005	A1
20050102202	Linden et al.	May 2005	A1
20050114229	Ackley et al.	May 2005	A1
20050153681	Hanson	Jul 2005	A1
20050197846	Pezaris	Sep 2005	A1
20050198173	Evans	Sep 2005	A1
20060075044	Fox et al.	Apr 2006	A1
20060167991	Heikes et al.	Jul 2006	A1
20060168054	Burkhart et al.	Jul 2006	A1
20060173824	Bensky et al.	Aug 2006	A1
20060173963	Roseway et al.	Aug 2006	A1
20060182248	Smith et al.	Aug 2006	A1
20060212561	Feng	Sep 2006	A1
20060277187	Roese et al.	Dec 2006	A1
20070156664	Norton et al.	Jul 2007	A1
20080082620	Barsness	Apr 2008	A1
20090089316	Kogan et al.	Apr 2009	A1
20090248816	Appelman	Oct 2009	A1

Foreign Referenced Citations (49)

Number	Date	Country
2002340039	May 2007	AU
2462037	Mar 2004	CA
1285122	Feb 2001	CN
1578952	May 2010	CN
101815039	Aug 2010	CN
0862304	Feb 1998	EP
1176840	Jan 2002	EP
1430411	Jun 2004	EP
2319137	May 1998	GB
2357932	Aug 1999	GB
2357932	Jul 2001	GB
2368747	May 2002	GB
708DELNP2004	Mar 2004	IN
2008-314826	Nov 1996	JP
2000-499001	Feb 2000	JP
2000-259514	Sep 2000	JP
2000-284999	Oct 2000	JP
2001-084320	Mar 2001	JP
2005-505054	Feb 2005	JP
20010029393	Apr 2001	KR
10-2004-7004631	Mar 2004	KR
PAA2004002788	Apr 2005	MX
WO 9710558	Mar 1997	WO
WO 9714234	Apr 1997	WO
WO 9746955	Dec 1997	WO
WO 9816045	Apr 1998	WO
WO 9847270	Oct 1998	WO
WO 9908434	Feb 1999	WO
WO 9934628	Jul 1999	WO
WO 9948011	Sep 1999	WO
WO 0016201	Mar 2000	WO
WO 0024154	Apr 2000	WO
WO 0060809	Oct 2000	WO
WO 0079396	Dec 2000	WO
WO 0106748	Jan 2001	WO
WO 0122258	Mar 2001	WO
WO 0124036	Apr 2001	WO
WO 0143357	Jun 2001	WO
WO 0172020	Sep 2001	WO
WO 0167787	Sep 2001	WO
WO 0180079	Oct 2001	WO
WO 0203216	Jan 2002	WO
WO 0209437	Jan 2002	WO
WO 0235781	May 2002	WO
WO 02062039	Aug 2002	WO
WO 02073886	Sep 2002	WO
WO 03030003	Apr 2003	WO
WO 2004028178	Apr 2004	WO
WO 2005086723	Sep 2005	WO

Non-Patent Literature Citations (248)

Entry
“The LP Wireless Messenger”, Messenger Documentation, http://www.lpwireless.com/messengerhelp.htm, pp. 1-7 (Nov. 22, 2002).
“AOL technology: turning complicated things into engaging services”, 1996 Annual Report, 22 pages.
“Yahoo! Messenger Makes the World a Little Smaller, More Informed”, pp. 1-2, Jun. 21, 1999.
Alan Cohen, “Instant Messaging”, Apr. 13, 1999, PC Magazine, PC Labs, 2 pages.
“AOL Instant Messenger Windows Beta Features”, Jun. 24, 1999. 2 pages, AOL Instant Messenger All New Version 2.0, 2 pages, Jun. 24, 1999, What is AOL Instant messenger, 3 pages, Jun. 24, 1999, Quick Tips for Getting Started, 5 pages, Jun. 24, 1999, Frequently Asked Questions About AOL Instant Messenger, 6 pages, Jun. 24, 1999.
Eschenburg, Wo laufen sie denn?, Oct. 26, 1998, pp. 92-95.
Kohda et al., IMPP: A New Instant Messaging Standard and Its Impact on Internet Business, Dec. 2000, Fujitsu Sci. Tech. J., 36, 2, pp. 147-153.
International Search Report for International No. PCT/US03/15715, mailed Aug. 14, 2003.
“What new about exchanging information over the Internet,” Outlook 2000 SR-1 (9.0.04527) Help File, on or before Aug. 10, 2001, p. 1.
“About Internet directory services,” Outlook 2000 SR-1 (9.0.04527) Help File, on or before Aug. 10, 2001, p. 1.
“Set up LDAP directory services,” Outlook 2000 SR-1 (9.0.04527) Help File, on or before Aug. 10, 2001, p. 1.
“Look up contact information from an item,” Outlook 2000 SR-1 (9.0.04527) Help File, on or before Aug. 10, 2001, p. 1.
J.C. Cannon, “Design Guide for Directory-Enabled Applications,” [online], Apr. 2001 [retrieved on May 13, 2003]. Retrieved from the internet http://msdn.microsoft.com/library/enus/dnactdir/html/BuildingADApps.asp?frame=true, pp. 1-9.
Microsoft Corporation, “Using ADSI, LDAP, and Network Management Functions With Active Directory,” [online], Feb. 2002 [retreived on May 13, 2003]. Retreived from the internet http://msdn.microsoft.com/library/enus/dnactdir/html/BuildingADApps.asp?frame=true, pp. 1-9.
Microsoft Corporation, “Comparing Microsoft Active Directory to Novell's NDS,” [online], Sep. 1998 [retrieved on May 13, 2003]. Retrieved from the internet http://msdn.microsoft.com/library/enus/dnactdir/html/msdn—activedirvsnds.asp?frame=true, pp. 1-17.
Microsoft Corporation, “Active Directory Services Interface in the Microsoft Exchange 5.5 Environment,” [online], Nov. 1997 [retrieved on May 13, 2003]. Retrieved from the internet http://msdn.microsoft.com/library/enus/dnactdir/html/msdn—adsiexch.asp?frame=true, pp. 1-12.
“Active Directory Service Overview,” [online], Nov. 30, 2001 [retrieved on May 13, 2003]. Retrieved from the internet http://msdn.microsoft.com/windows2000/server/evaluation/buisiness/addatasheet.asp, pp. 105.
“Integrating Microsoft Metadirectory Services and Active Directory,”[online], Aug. 31, 2000 [retrieved on May 13, 2003]. Retrieved from the Internet http://www.microsoft.com/windows2000/-server/evaluation/business/adwin2k.asp, p. 1.
“Benefits of Active Directory in a Windows 2000 Environment,” [online], Sep. 20, 2001 [retrieved on May 13, 2003]. Retrieved from the Internet http://www.microsoft.com/windows2000/-server/evaluation/business/adwin2k.asp, pp. 1-9.
“Active Directory,” [online], retrieved on May 13, 2003. Retrieved from the Internet http://www.microsoft.com/windows2000/technologies/directory/AD/default.asp, pp. 1-13.
Microsoft Corporation, “Introduction to Active Directory Application Mode,” Microsoft Windows Server 2003, Aug. 2002, pp. 1-13.
“Active Directory Features,” [online], Jun. 15, 1999 [retrieved on May 13, 2003]. Retrieved from the Internet http://www.microsoft.com/windows2000/server/evaluation/features/adlist.asp, pp. 1-4.
“Windows 2000 Directory Services,” [online], [retrieved on May 13, 2003]. Retrieved from the Internet http://www.microsoft.com/windows2000/technologies/directory/default.asp, pp. 1-2.
“Directory Integration Can Lower Total Cost of Ownership and Increase Application Functionality,” [online], Jul. 27, 1998 [retrieved on May 13, 2003]. Retrieved from the Internet http://www.microsoft.com/presspass/press/1998/Jul98/ActivDPR.asp, pp. 1 of 4.
William R. Stanek, Microsoft Windows 2000 Administrator's Pocket Consultant [online]. Microsoft Corporation, 1999 [retrieved on May 8, 2003]. Retrieved from the Internet <http://www.microsoft.com/technet/prodtechnol/ad/windows2000/evaluate/05w2kada.asp?fr . . . >, pp. 1-6.
“Enterprise Identity Management with Windows 2000 and Active Directory,” [online], 1999 [retrieved on May 13, 2003]. Retrieved from the Internet <http://www.microsoft.com/technet/prodtechnol/ad/windows2000/evaluate/w2keims.asp?fra . . . >, pp. 1-16.
William R. Stanek, Microsoft Windows 2000 Administrator's Pocket Consultant [online]. Microsoft Corporation, 1999 retrieved on May 8, 2003}. Retrieved from the Internet <http://www.microsoft.com/technet/prodtechnol/ad/windows2000/evaluate/05w2kadb.asp?fra . . . >, pp. 1-10.
“Integrating Applications with Windows 2000 and Active Directory,” [online], Oct. 2000 [retrieved on May 8, 2003]. Retrieved from the Internet <http://www.microsoft.com/technet/prodtechnol/ad/windows2000/evaluate/adappstr.asp?fra . . . >, pp. 1-12.
“Part I: Active Directory Operations,” Active Directory Operations Guide, Microsoft Corporation, Microsoft Windows 2000, Version 1.5, pp. 1-187.
“Part II: Tasks and Procedures Appendices,” Active Directory Operations Guide, Microsoft Corporation, Microsoft Windows 2000, Version 1.5, pp. 1-131.
Mckendrick, Joseph; “Internet Call Centers: New Era in Customer Service”; Feb. 2002; V10, n2, pp. 22(4).
International Search Report for mailed Aug. 30, 2005 for European Patent Application No. 03731244.
Ed Bott and Ron Person, Using Windows 95 with Internet Explorer 4.0, Feb. 17, 1998, Que, Special Edition.
America Online Inc., New AIM 4.7, Sep. 27, 2001, Internet: http://aim.aol.com.
America Online Inc., “AOL Instant Messenger”, Aug. 29, 2000, Internet: www.aol.com/aim/.
CNET Networks Inc., “PopUp Killer”, Sep. 13, 2001, Internet: download.cnet.com/downloads/0-10059-100-6932612.html.
WebmasterWorld.com Inc., “HTML and Browswers”, Mar. 5, 2001, Internet: www.webmaster.com/forum21/367.htm.
“Internet Call Center: New Era in Customer Service”, Joseph Mckendrick, Aug. 18, 2005.
International Search Report, Application Serial No. PCT/US05/45663, dated Apr. 11, 2008, 10 pages.
“A Countermeasure to Duplicate-detecting Anti-spam Techniques,” Robert J. Hall, AT&T Labs Technical Report 99.9.1, 1999, Abst. and pp. 1-26.
“A Reputation System for Peer-to-Peer Networks,” Gupta et al., Jun. 1-3, 2003, NOSSDAV'03, Monterey, California, pp. 144-152.
“Announce: Implementation of E-mail Spam Proposal,” Maurice L. Marvin, news.admin.net-abuse.misc, Aug. 3, 1996, 2 pages.
“BestCalls.com Announces the BestCalls Technology Index,” Business Wire, Jun. 30, 1999, Business Wire, p. 1.
“Better Bayasian Filtering,” Paul Graham, Jan. 2003, pp. 1-11, http://www.paulgraham.com/better.html.
“Business at Cyberspeed; Brainstorm Becomes Quick Internet Hit,” Walker, Jan. 24, 1999, The Washington Post, p. A.01 (4 total pages).
“CrushParty.com: Help,” retrieved Jun. 23, 2002 from the World Wide Web: http://www.crushparty.com/help.jsp, 3 pages.
“Degrees of Separation Email Spam Protection,” Halfbakery: Degrees of Separation Email Spam Protection, reprinted from http://halfbakery.com/idea/Degrees-20of-20Separation-20Email-20Spam-20Protecti . . . printed on Mar. 1, 2004 (3 pages).
“Digital Artifacts for Remembering and Storytelling: Post History and Social Network Fragments,” Viegas et al., retrieved from the World Wide Web: http://we.media.mit.edu/˜fviegas/papers/posthistory-snf.pdf, 10 total pages (Jan. 2004).
“Finding Others Online: Reputation Systems for Social Online Spaces,” Jensen et al., Apr. 20-25, 2002, CHI, Minneapolis, Minnesota, vol. 4, Issue 1, pp. 447-454.
“Hottie or Nottie? Web Site Voters Let You Know Whether You Sizzle or Fizzle,” Marino, Jul. 11, 2001, Florida Times Union, p. C.1. (2 total pages).
“Icq.anywhere, Email Features-Email Center-ICQ.com,” retrieved Apr. 29, 2004 from the World Wide Web: http://www.icq.com/email/popular-features.html, pp. 1-5.
“Idea for Online Networking Brings Two Entrepreneurs Together,” Patents: Idea for Online Networking Brings Two Entrepreneurs Together, reprinted from http://www.nytimes.com/2003/12/01/technology/01patt.html?adxnnl+0&adxnnlx=107029 . . . , printed on Nov. 5, 2004 (3 pages).
“Instant Messaging for Gamers,” PC Gamer, May 2004, vol. 11, No. 5, p. 28.
“GLWebMail 2.0 is released!” http://www.gordano.com; available on Apr. 18, 2001, reprinted from http://web.archive.org/web/20010418153714//http://www.gordano.com.
“Learning Spam: Simple Techniques for Freely-Available Software,” Bart Massey et al, Computer Science Dept., Portland, OR USA, Jun. 2003, pp. 1-14.
“Learning to Filter Spam E-Mail: A Comparison of a Naïve Bayesian and a Memory-Based Approach,” Ion Adroutsopoulos et al., University of Athens, Sep. 2000, pp. 1-12.
Lotus Instant Messaging Everyplace FAQ, retrieved Apr. 29, 2004 from the World Wide Web: http://www.lotus.com/products/product4.nsf/wdocs/249c6f083166cd3e85256d7300714407, pp. 1-3.
Mary Beth Marklein, “Student have ‘away’ with words”, Mar. 28, 2004, USA Today, http://www.usatoday.com/tech/news/2004-03-28-aways-messages-usat- x.htm, all pages.
“PieSpy-Inferring and Visualizing Social Network on IRC,” PieSpy Social Network Bot, reprinted from http://lister.linux-srv.anlx.net/piespy printed on Mar. 11, 2004 (18 pages).
“Plaxo,” Plaxo, reprinted from http://web.archive.org/web/20041105072256/http://www.plaxo.com/ printed on Nov. 5, 2004 (available on Feb. 14, 2004) (2 pages).
“Plaxo-Update Your Address Book,” Plaxo Contact Networks, reprinted from http://web.archive.org/web/20030218233638/http://www.plaxo.com/ printed on Nov. 5, 2004 (available on Feb. 18, 2003) (1 page).
“Reflections on Friendster, Trust and Intimacy,” Danah Boyd. Ubicomp 2003, Workshop Application for the Intimate Ubiquitous Computing Workshop. Seattle, WA, Oct. 12-15, 2003.
“Reputation Systems,” Resnick et al., Dec. 2000, Communications of the ACM, vol. 43, No. 12, pp. 45-48.
“RIM Road: Software: Internet & Network: Webmessenger RIM J2ME/Instant Messaging,” retrieved Apr. 29, 2004 from the World Wide Web: http://www.rimrod.com/software/rim1/Webmessenger-RIM-J2ME-Instant-Messaging-20 . . . , pp. 1-4.
“Six Degrees-New Programs Help Companies ‘Mine Workers’ Relationships for Key Business Prospects,” William M. Bulkeley et al., Marketplace, The Wall Street Journal, Aug. 4, 2003, (3 pages).
“Social Nets Find Friends in VCs,” Joanna Glasner, http://www.wired.com/news, Nov. 17, 2003, pp. 1-3.
“Social Network Fragments: An Interactive Tool for Exploring Digital Social Connections.” Danah Boyd, Jeff Potter. Sketch at SIGGRAPH 2003. San Diego, California: ACM, Jul. 27-31, 2003.
“Social Networking for Business: Release 0.5,” Esther Dyson, Esther Dyson's Monthly Report, vol. 21, No. 10, Nov. 25, 2003, www.edventure.com, (36 pages).
“Social Networks: Deodorant for the Soul?,” Esther Dyson, Esther Dyson's Monthly Report, vol. 21, No. 11, Dec. 12, 2003, www.edventure.com, (36 pages).
“Social Sites Clicking With Investors,” Washingtonpost.com: Social Sites Clicking With Investors, reprinted from http://www.washingtonpost.com/ac2/wp-dyn/A32066-2003Nov12?language=printer printed on Nov. 5, 2004.
“Socialware: Multiagent Systems for Supporting Network Communities,” Hattori et al., Mar. 1999, Association for Computing Machinery, Communications of the ACM, vol. 42, Issue 3, pp. 55ff.
“Spoke Builds on Social Networking Patent Portfolio,” Spoke Builds on Social Networking Patent Portfolio, reprinted from http://www.internetnews.com/ent-news/print.php/3073621 printed on Nov. 5, 2004 (3 pages).
“Support Vector Machines for Spam Categorization,” Harris Drucker et al., IEEE Transactions on Neural Networks, vol. 10, No. 5, Sep. 1999, pp. 1048-1054.
“Support Vector Machines,” Marti Hearst, IEEE Intelligent Systems, Jul./Aug. 1998, pp. 18-28.
“SVM-based Filtering of E-mail Spam with Content-specific Misclassification Costs,” Aleksander Kolcz et al., TextDM'2001 (IEEE ICDM-2001 Workshop on Text Mining), San Jose, CA, 2001, pp. 1-14.
“SWF Seeks Attractive Head Shot; To Stand Out, Online Daters Pay for Professional Photos; Cropping out the Ex-Wife,” Leiber, Nov. 19, 2003, The Wall Street Journal, p. D.1.
“Technical Solutions for Controlling Spam,” Shane Hird, Proceedings of AUUG2002, Melbourne, Sep. 4-6, 2002, 17 pages.
“Technology Journal—Are You Satisfied? EBay's Battle Against Fraud Rests Primarily on a Simple Concept: Customer Feedback,” Wingfield, Sep. 23, 2002, Asian Wall Street Journal, p. T.8, (4 total pages).
“Telstra targets Net spammers,” J. Dudley, news.com.au, Dec. 2, 2003, 2 pages.
“Text Categorization with Support Vector Machines: Learning with Many Relevant Features,” Thorsten Joachims, University of Dortmund, Computer Science Dept., LS-8 Report 23, Apr. 1998, 18 pages.
“The first Social Software . . . a true Social Adventure,” Huminity-Social Networking, Chat Software, Create Personal Free Blogs and My Group . . . , reprinted from http://www.huminity.com/ printed on Nov. 5, 2004 (2 pages).
“Trillian Discussion Forums—HowTo: Import ICQ 2003a Contact List,” retrieved Apr. 29, 2004 from the World Wide Web: http://trillian.cc/forums/showthread.php?s+&threadid=36475, pp. 1-2.
“Using Active Directory Service”, from Chapter 5, Microsoft Windows 2000 Administrator's Pocket Consultant, by William R. Stank (1999). Retrieved from http://www.microsoft.com/technet/prodtechnol/ad/windows2000/evaluate/05w2kadb.asp?fr . . . , pp. 1-6.
“Welcome to Huminity World of Connections,” Huminity-Home, reprinted from http://web.archive.org/web/20030228131435/www.huminity.com/default.php?internationa . . . printed on Nov. 5, 2004 (available on Feb. 2, 2003) (1 page).
“Will You Buy a Car From This Man?,” Leander Kahney, Oct. 6, 2003, pp. 1-3.
“Windows 2000 Directory Services”, [online] http://www.mircrosoft.com/windows2000/technologies/directory/default.asp, as of Nov. 25, 2001 according to Internet Archive Wayback Machine, available at http://web.archive.org/web20011625224156/http://www.microsoft.com/windowns2000/technologies/directory/defalt.asp, 1 page.
“Working with Active Directory Domains”, from Chapter 5, Microsoft Windows 2000 Administrator's Pocket Consultant, by William R. Stank (1999). Retrieved from http://www.microsoft.com/technet/prodtechnol/ad/windows2000/evaluate/05w2kadb.asp?fr . . . , pp. 1-10.
Anand Ranganathan et al., “ConChat: A Context-Aware Chat Program”, Jul.-Sep. 2002, Pervasive Computing, pp. 51-57.
BuddyGopher˜About, available on Jul. 13, 2004, reprinted from http://web.archive.org/web/20040713002836/www.buddygopher.com/about.html on Sep. 28, 2005 (4 pgs).
BuddyGopher˜We Love Away Messages!, “BuddyGopher simultaneously checks the away messages of your favorite AIM® buddies.”, available on Sep. 24, 2004, reprinted from http://web.archive.org/web/20040924104001/http://www.buddygopher.com/ on Sep. 28, 2005 (2 pgs).
Supplementary European Search Report issued in European Application No. EP05728303, dated Jan. 9, 2009, (2 pages).
Dodgeball.com:: mobile social software, “help: text messaging”, available on Oct. 13, 2004, reprinted from http://web.archive.org/web/20041013034241/www.dodgeball.com/social/help-text.php on Sep. 28, 2005 (3 pgs).
Dodgeball.com:: mobile social software, “help: the basics”, available on Oct. 9, 2004, reprinted from http://web.archive.org/web/20041009200739/www.dodgeball.com/social/help-basics.php on Sep. 28, 2005 (2 pgs).
Dodgeball.com:: mobile social software, “help: use it”, available on Oct. 9, 2004, reprinted from http://web.archive.org/web/20041009201853/www.dodgeball.com/social/help-useit.php on Sep. 28, 2005 (2 pgs).
Dodgeball.com:: mobile social software, “Hook up with friends. Discover what's around you.”, available on Nov. 30, 2003, reprinted from http://web.archive.org/web/20041130034344/www.dodgeball.com/social/index.php on Sep. 28, 2005 (2 pgs).
Home-tribe.net http://washingtondc.tribe.net/message/24434d1b-817b-4580-aa42-3bffa15f26a?page=1 (4 total pages, reprinted on Dec. 13, 2004).
http://www.friendster.com (17 pages, reprinted on Dec. 13, 2004).
International Search Report, Application Serial No. PCT/US2006/018286, dated Oct. 19, 2006, 12 pages.
International Search Report and Written Opinion dated Feb. 15, 2006 for International Application No. PCT/US05/07204, 14 pages.
International Search Report dated Oct. 16, 2006, for PCT/US05/08476, 9 pages.
International Search Report and Written Opinion for PCT Application No. PCT/US2005/042992, Mar. 6, 2007 (14 pages).
Neo Mai, Ken Neo. “Buying and selling on the internet; [Computimes, 2* Edition].” New Straits Times. Kuala Lumpur: Jun. 28, 2001. p. 53.
R. Movva & W. Lai, “MSN Messenger Service 1.0 Protocol”, Aug. 1999, Internet Draft, http://tools.ietf.org/id/draft-movva-msn-messenger-protocol-oo.txt, 28 pages.
Reichard, K., “AOL, ICQ to Interoperate—But in a Limited Fashion,” Oct. 30, 2002, InstantMessagingPlanet, available at www.instantmessagingplanet.com/public/article.php/1490771.
Ryze home page, www.ryze.com, Dec. 21, 2003, available at http://web.archive.org/web/20031221010006/http://ryze.com, printed Mar. 16, 2005, 13 pages.
Takashi Yoshino et al., “Namba: Location-Aware Collaboration System for Shopping and Meeting”, Aug. 2002, IEEE Transactions on Consumer Electronics, pp. 470-477.
VisiblePath webpages, www.visiblepath.org, Dec. 3, 2003, available at http://web.archive.org/web/20031203132211/http://www.visiblepath.com, printed Mar. 16, 2005, 5 pages.
ZeroDegrees home page, www-zerodegrees.com, Jan. 24, 2004, available at http://web.archive.org/web/20040204153037/www.zerodegrees.com/home.htm, printed Mar. 16, 2005, 2 pages.
Office Action of Canadian Application No. 2,462,037, dated Feb. 12, 2009 (8 pages).
Courter et al., “Mastering Microsoft Outlook 2000 Premium Edition”, Sybex Inc., Alameda, California, Feb. 2000 pp. 167-169, ISBN 0-7821-2676-6.
“The LP Wireless Messenger”, Messenger Documentation, http://www.lpwireless.com/messengerhelp.htm, pp. 1-7, available on Dec. 9, 2002, reprinted from http://web.archive.org/web20021209025321/http://lpwireless.com/messengerhelp.htm.
Australian Office Action of Apr. 7, 2006, App. No. 2002340039 (2 pages).
European Patent Office, Communication of Aug. 30, 2005, App. No. 03731244.1-2416 (PCT/US0315715) (4 pages).
Japanese Office Action of May 12, 2008, App. No. 2003-533140 (5 pages).
Chinese Office Action of Jul. 7, 2006, App. No. 02821420.X (5 pages).
European Patent Office, Communication of Aug. 31, 2009, App. No. 02778374.5-1238 (8 pages).
PCT International Search Report of Apr. 11, 2003, App. No. PCT/US00/35160 (3 pages).
European Patent Office, Communicatino of Sep. 5, 2006, App. No. 02778374.5-1238 (4 pages).
PCT International Search Report of Jan. 9, 2003, App. No. PCT/US02/30730 (5 pages).
“About File Transfers”, AOL Instant Messenger, version 4.3, Help Documentation, available on Jul. 2, 2001, 5 pages.
“AOL Instant Messenger All New Version 2.0” Jun. 24, 1999, 6 pages.
“AOL Instant Messenger”, reprinted from http://web.archive.org/web/20010721193059/http://aim.com/ (Way Back Machine—available on Jul. 21, 2001) on Aug. 26, 2005, 7 pages.
“New Features in AOL Instant Messenger for Windows v 2.01 Beta”, 2 pages, Apr. 28, 1999.
“Quick Tips for Getting Started”, 5 pages, Jun. 24, 1999.
“What is AOL Instant Messenger”, Jun. 24, 1999, 3 pages.
“Windows NetMeeting—Features”, [Online], Jun. 17, 1999, XP002245623, Retrieved from the internet: URL:http://www.microsoft.com/windows/NetMeeting/Features/default.ASP>, 8 Pages.
Anonymous: “Push to Talk TM Services”, Internet Document, [online], Retrieved from the internet: URL:http://www.nextel.com/services/directconnect/ptt—overview.shtml [retrieved on Dec. 29, 2003, 1 page.
Anonymous: “The Internet—the Advent of New Forms of Communication”, Internet Document, [Online], Retrieved from the Internet: URL:http://journal.fujitsu.com/248e/e48now.html [retrived on Dec. 29, 2003], 3 pages.
Archive.org archived copy of the Morpheus 1.9.1 download page on c-net Download.com [online] Aug. 3, 2002, Retrieved from the Internet: URL:http://web.archive.org/web/20020803071751/downlaod.com.com/3000-2166-10057840.html> 2 pages.
Archive.org archived copy of the Morpheus 1.9.1 download page on c-net Download.com [online] Oct. 8, 2001 [from U.S. Appl. No. 09/911,799] (2 pages).
Archive.org archived copy of MusicCity Morpheus download page on c1net Download.com [online] Oct. 8, 2001 [accessed Feb. 14, 2007], Retrieved from Internet, URL:http://web.archive/org/web/20011008191757/download.cnet.com/downloads/0-18964201005590701.html>.
Canadian Office Action from Application Serial No. 2,403,520, dated Feb. 21, 2005, 2 pages.
Carlos Jensen et al., “Finding Others Online: Repuation Systems for Social Online Spaces”, Apr. 2002, Paper: Group Spaces, pp. 447-454.
International Search Report and Written Opinion dated Feb. 15, 2006 for International Application No. PCT/US05/07204, 10 pages.
Office Action mailed approximately Feb. 29, 2006 for Japanese Patent Application No. 2002-515026 (6 pages).
Dutta-Roy Amitava, “Virtual Meetings with Desktop Conferencing”, IEEE Spectrum, vol. 35, No. 7, Jul. 1, 1998, pp. 47-56 and p. 66.
European Office Action in Application No. 01954931.0-2414, mailed Jul. 14, 2008, 3 pages.
European Search Report mailed Aug. 30, 2005 for European Application No. 03731244, 4 pages.
Gupta et al., “A Reputation System for Peer-to-Peer Networks,” Jun. 1-3, 2003, NOSSDAV'03, California, pp. 144-152, Monterey.
IBM “Configuring Sametime servers in your Domino Environment” May 1, 2000 (14 pages).
Isaacs, Ellen: “Example UI Spec: Sound Instant Messages”, Internet Document, [Online], Retrieved from the Internet http://msdn.microsoft.com/library/en-us/dnactdir/html/deal.asp?frame=true> pp. 1-18, Sep. 2000.
Klaus Hartenstein et al., “xhtalk 2.9”, Nov. 1992, 6 pages.
Lotus Sametime 1.5, Jul. 27, 1999 (4 pages).
Mariano, Gwendolyn. ZDNetNews. “Morpheus 1.9 to be unleashed”, [online] Jun. 10, 2002. Retrieved from the internet URL:http://news.zdnetcom/2100-3513—22-934615.html, 6 pages.
Matsumoto, Tatsuro et al.: “Chocoa Communicator—A New Communication System Based on Awareness and Text Communications—”, Fujitsu Sci. Tech. J., 36, 2, pp. 154-161, Dec. 2000.
Maurice L. Marvin, “Announce: Implementation of E-mail Spam Proposal,” news.admin.net-abuse.misc, Aug. 3, 1996, 2 pages.
Mike Snyder, “America goes online for New Year's bash”, USA Today, p. 3D, Jan. 2, 2000.
Muller, Nathan, “Dial 1-800-Internet”; Feb. 1996, pp. 83-84, 86, 88.
Mutton, Paul, “PieSpy Social Network Bot Inferring and Visualizing Social Networks IRC,” Dec. 4, 2003, Internet Archive Wayback Machine http://web.archive.org/web/20031204185952/http://jibble.org/piespy, 11 pages.
PowWow (Mar. 1, 2000), Introduction, Retrieved Apr. 3, 2006 from website http://web.archive.org/web/20000301125635/ww2.tribal.com/help/online—docs/h205voic.html.
Pruitt, Scarlet. IDG News Service. “Morpheus Updates Peer-toPeer Client” [online] Jun. 10, 2002, Retrieved from the internet URL:http://www.pcworld.com/article/id.101736/article.html, 3 pages.
Robert J. Hall, “A Countermeasure to Duplicate-detecting Anti-spam Techniques,” AT&T Labs Technical Report 99,9.1, Dec. 1999, Abst and pp. 1-26.
Satter, Michael, excerpts from the Internet TV with CU-SeeMe, First Edition, including inside Title Page and Copyright Page; “Overview”; “Contents,” through pp. xii; Chapter 1, “Introduction to the Internet Videoconferencing and CU-SeeMe,” pp. 1-12; Chapter 4, “Hardware,” pp. 47-64; Chapter 5, “Software,” pp. 65-92: Chapter 6, “CU-SeeMe User's Guide,” pp. 93-121; Chapter 9, “Other Videoconferencing Technologies,” pp. 201-226; Chapter 10, “What the Future Holds,” pp. 227-233; Appendix A, “Troubleshooting Q&A,” pp. 235-249; published by Sams.net Publishing, 201 W. 103rd St., Indianapolis, IN 46290, International Standard Book No. 1-57521-006-1, Library of Congress Catalog Card No. 95-70178, copyright 1995.
Tribal Voice, PowWow Guided Tour—Step 6, PowWow personal communcation. Http://web.archive.org/web/2000817094516/www.tribal.com/powwow/tour/step6.cfm (Oct. 22, 1999), 2 pages.
Wayner, Peter, “Hey Baby, Call Me at My IP Address”, Apr. 1996, 3 pages.
Windows 2000 Directory Services, [online], [retrieved on May 13, 2003]. Retrieved from the internet <http://www.microsoft.com/windows2000/technologies/directory/default.asp>, 2 pages.
Wingfield, N., “Technology Journal: Changing Chat—Instant messaging Is Taking Off, and for Some Users IT's Nuzzling Out the Phone”, Asain Wall Street journal, New York, NY Sep. 25, 2000, 5 pages.
Yubing Wang, Mark Claypool, Zheng Zuo. Video: An empirical study of realvideo performance across the internet. Proceedings of the 1st ACM SIGCOMM Workshop on the internet measurement IMW'01. Nov. 2001. ACM Press. 15 pages.
U.S. Appl. No. 09/810,159, Jul. 6, 2004, Office Action.
U.S. Appl. No. 09/810,159, Feb. 11, 2005, Office Action.
U.S. Appl. No. 09/810,159, Jun. 15, 2005, Office Action.
U.S. Appl. No. 09/810,159, Dec. 2, 2005, Office Action.
U.S. Appl. No. 09/810,159, Apr. 19, 2006, Office Action.
U.S. Appl. No. 09/810,159, Jan. 10, 2008, Examiner's Answer.
U.S. Appl. No. 09/810,159, Jan. 11, 2008, Office Action.
U.S. Appl. No. 09/810,159, Jan. 29, 2010, Office Action.
U.S. Appl. No. 09/843,788, Mar. 30, 2004, Office Action.
U.S. Appl. No. 09/843,788, Dec. 2, 2004, Office Action.
U.S. Appl. No. 09/843,788, Jul. 27, 2005, Office Action.
U.S. Appl. No. 09/843,788, Mar. 28, 2006, Office Action.
U.S. Appl. No. 09/843,788, Jun. 12, 2006, Office Action.
U.S. Appl. No. 09/843,788, Apr. 19, 2007, Office Action.
U.S. Appl. No. 09/843,788, Oct. 31, 2007, Office Action.
U.S. Appl. No. 09/843,788, Sep. 15, 2008, Office Action.
U.S. Appl. No. 09/843,788, May 5, 2010, Office Action.
U.S. Appl. No. 09/911,799, Oct. 5, 2004, Office Action.
U.S. Appl. No. 09/911,799, Apr. 29, 2005, Office Action.
U.S. Appl. No. 09/911,799, Nov. 17, 2005, Office Action.
U.S. Appl. No. 09/911,799, Aug. 11, 2006, Office Action.
U.S. Appl. No. 09/911,799, Jul. 3, 2007, Office Action.
U.S. Appl. No. 09/911,799, Dec. 1, 2008, Office Action.
U.S. Appl. No. 09/911,799, Mar. 18, 2008, Office Action.
U.S. Appl. No. 10/134,437, Nov. 1, 2005, Office Action.
U.S. Appl. No. 10/134,437, May 18, 2006, Office Action.
U.S. Appl. No. 10/134,437, Aug. 21, 2006, Advisory Action.
U.S. Appl. No. 10/134,437, Sep. 6, 2007, Miscelaneous Action.
U.S. Appl. No. 10/134,437, Feb. 11, 2008, Office Action.
U.S. Appl. No. 10/134,437, Sep. 18, 2008, Office Action.
U.S. Appl. No. 10/134,437, Mar. 10, 2009, Office Action.
U.S. Appl. No. 10/134,437, Nov. 17, 2009, Notice of Allowance.
U.S. Appl. No. 10/146,814, May 17, 2002, Examiner's Answer.
U.S. Appl. No. 10/146,814, Sep. 20, 2005, Office Action.
U.S. Appl. No. 10/146,814, May 22, 2006, Office Action.
U.S. Appl. No. 10/146,814, Dec. 11, 2006, Office Action.
U.S. Appl. No. 10/146,814, Jul. 2, 2007, Office Action.
U.S. Appl. No. 10/146,814, Apr. 15, 2008, Office Action.
U.S. Appl. No. 10/146,814, Jan. 12, 2009, Office Action.
U.S. Appl. No. 10/146,814, Mar. 22, 2010, Office Action.
U.S. Appl. No. 10/184,002, Aug. 25, 2005, Office Action.
U.S. Appl. No. 10/184,002, Apr. 20, 2006, Office Action.
U.S. Appl. No. 10/184,002, Jan. 9, 2007, Office Action.
U.S. Appl. No. 10/184,002, Jan. 8, 2008, Office Action.
U.S. Appl. No. 10/184,002, Jul. 24 2008, Notice of Allowance.
U.S. Appl. No. 10/334,056, Nov. 29, 2004, Office Action.
U.S. Appl. No. 10/334,056, Jul. 6, 2005, Office Action.
U.S. Appl. No. 10/334,056, Oct. 31, 2005, Office Action.
U.S. Appl. No. 10/334,056, May 10, 2007, Office Action.
U.S. Appl. No. 10/334,056, May 21, 2007, Office Action.
U.S. Appl. No. 10/334,056, Nov. 5, 2007, Office Action.
U.S. Appl. No. 10/334,056, May 12, 2008, Office Action.
U.S. Appl. No. 10/633,636, Oct. 11, 2006, Office Action.
U.S. Appl. No. 10/747,623, Mar. 13, 2007, Office Action.
U.S. Appl. No. 10/747,623, Aug. 21, 2007, Office Action.
U.S. Appl. No. 10/747,623, Nov. 14, 2007, Office Action.
U.S. Appl. No. 10/747,623, Jun. 23, 2008, Office Action.
U.S. Appl. No. 10/747,624, Feb. 26, 2007, Office Action.
U.S. Appl. No. 10/747,624, Jul. 16, 2007, Office Action.
U.S. Appl. No. 10/747,624, Nov. 1, 2007, Office Action.
U.S. Appl. No. 10/747,679, Oct. 2, 2007, Office Action.
U.S. Appl. No. 10/747,679, Apr. 29, 2008, Office Action.
U.S. Appl. No. 10/981,460, Aug. 20, 2008, Office Action.
U.S. Appl. No. 11/015,424, Mar. 19, 2008, Office Action.
U.S. Appl. No. 11/015,424, Nov. 3, 2008, Office Action.
U.S. Appl. No. 11/015,424, May 1, 2009, Office Action.
U.S. Appl. No. 11/015,424, Oct. 19, 2009, Office Action.
U.S. Appl. No. 11/017,204, Dec. 12, 2007, Office Action.
U.S. Appl. No. 11/017,204, Jun. 23, 2008, Office Action.
U.S. Appl. No. 11/150,180, Oct. 2, 2007, Office Action.
U.S. Appl. No. 11/150,180, Apr. 7, 2008, Office Action.
U.S. Appl. No. 11/150,180, Aug. 19, 2009, Office Action.
U.S. Appl. No. 11/237,718, Apr. 2, 2009, Office Action.
U.S. Appl. No. 11/238,110, Nov. 29, 2007, Office Action.
U.S. Appl. No. 11/238,110, Jul. 9, 2008, Office Action.
U.S. Appl. No. 11/238,110, Oct. 9, 2008, Office Action.
U.S. Appl. No. 11/238,129, Nov. 14, 2007, Office Action.
U.S. Appl. No. 11/238,129, May 29, 2008, Office Action.
U.S. Appl. No. 11/238,130, Jul. 3, 2008, Office Action.
U.S. Appl. No. 11/238,130, Nov. 13, 2008, Office Action.
U.S. Appl. No. 11/238,130, Apr. 14, 2009, Office Action.
U.S. Appl. No. 11/238,130, Nov. 24, 2009, Office Action.
U.S. Appl. No. 12/336,880, Aug. 4, 2010, Office Action.
U.S. Appl. No. 12/336,880, Mar. 2, 2011, Office Action.
U.S. Appl. No. 12/336,880, Mar. 5, 2013, Office Action.
U.S. Appl. No. 12/336,880, Sep. 11, 2013, Office Action.
U.S. Appl. No. 12/336,880, Jan. 31, 2014, Office Action.
U.S. Appl. No. 12/336,880, Jul. 11, 2014, Office Action.
U.S. Appl. No. 12/336,880, Nov. 20, 2014, Office Action.
U.S. Appl. No. 12/336,880, May 8, 2015, Notice of Allowance.

Related Publications (1)

	Number	Date	Country
	20130080551 A1	Mar 2013	US

Provisional Applications (1)

	Number	Date	Country
	60325084	Sep 2001	US

Continuations (2)

	Number	Date	Country
Parent	12336880	Dec 2008	US
Child	13618683		US
Parent	10184002	Jun 2002	US
Child	12336880		US

Continuation in Parts (1)

	Number	Date	Country
Parent	10134437	Apr 2002	US
Child	10184002		US

Personalization of recent contacts list

Information

Patent Number

Date Filed

Date Issued

Inventors

Original Assignees

Examiners

Agents

CPC

Field of Search

US

International Classifications

Abstract