System for instant messaging the sender and recipients of an e-mail message

Information

  • Patent Grant
  • 10122658
  • Patent Number
    10,122,658
  • Date Filed
    Friday, May 1, 2015
    9 years ago
  • Date Issued
    Tuesday, November 6, 2018
    6 years ago
Abstract
Systems and techniques for transferring electronic data between users of a communications system include a host system structured and arranged to receive and deliver messages of various types between users of the communications system. The host system includes an instant messaging network; a mail gateway; and a configuring network in communication with both the instant messaging network and the mail gateway. The instant messaging network enables instant messaging communication between users of the communications system and has the capability to monitor whether a certain user is capable of receiving an instant message at a particular moment. The mail gateway receives and delivers e-mail messages to users of the communications system. The configuring network is dedicated to automatically configuring instant messaging communication between an intended recipient of an e-mail message and the sender of the e-mail message.
Description
TECHNICAL FIELD

The present invention relates generally to a communications system and more particularly to a system for instant messaging the sender and recipients of an e-mail message.


BACKGROUND

Online service providers constantly are offering new services and upgrading existing services to enhance their subscribers' online experience. Subscribers have on-demand access to news, weather, financial, sports, and entertainment services as well as 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 information on a wide variety of topics from servers located throughout the world. A server may be maintained by the service provider or by a third party provider who makes information and services available through the worldwide network of computers that make up the online service.


America Online has provided subscribers with the ability to send and receive instant messages. Instant messages are private online conversations between two or more people who have subscribed to the instant messaging service and have installed the necessary software. Because such online conversations take place virtually in real time, instant messaging can provide immediate access to desired information. Instant messaging is becoming a preferred means of communicating among online subscribers.


SUMMARY

In one general aspect, transferring electronic data between users of a communications system includes using a host system structured and arranged to receive and deliver messages of various types between users of the communications system. The host system includes an instant messaging network, a mail gateway, and a configuring network in communication with both the instant messaging network and the mail gateway. The instant messaging network enables instant messaging communication between users of the communications system and is capable of monitoring whether a certain user is capable of receiving an instant message at a particular moment. The mail gateway receives and delivers e-mail messages to users of the communications system. The configuring network is dedicated to automatically configuring instant messaging communication between an intended recipient of an e-mail message and the sender of the e-mail message.


Implementations may include one or more of the following features. For example, the configuring network may send a redirection command to the recipient based on the capability of the sender to receive an instant message and/or may send a redirection command to the recipient based on the capability of another recipient of the e-mail message to receive an instant message. The redirection command may include a uniform resource locator.


The configuring network also may establish a persistent connection to the instant messaging network, check a control port to confirm whether the sender is capable of receiving an instant message, determine whether an e-mail address is associated with a recognized domain, and/or strip recognized domains from e-mail addresses.


The configuring network may have a look-up server for associating e-mail addresses with instant messaging screen names and/or a cache. The configuring network may detect whether information associated with an e-mail message is stored in the cache.


The mail gateway may include a send mail server for delivering electronic data to users, a read mail server for accessing electronic data, and/or a processing server for processing electronic data. The mail gateway may be web-based, online-service-provider based, and/or instant-messaging-host-based. The instant messaging network may be web-based and/or online-service-provider-based.


These and other aspects may be implemented by an apparatus and/or a computer program stored on a computer readable medium. The computer readable medium may be a disc, a client device, a host device, and/or a propagated signal.





DESCRIPTION OF DRAWINGS


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



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



FIGS. 7 and 8 are flow charts of communications method that may be implemented by the systems of FIGS. 1-6.



FIGS. 9 and 10 are illustrations of different graphical user interfaces that may be provided by the systems of FIGS. 1-6.





DETAILED DESCRIPTION

For illustrative purposes, FIGS. 1-6 shows 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 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, 155 that enable communications through the one or more delivery networks 160 described above. Each of the communication pathways 150, 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, 255 enabling 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 host system 110 and 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 98™, 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, 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 (“television”) 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, 355 enabling 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 email, 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 the 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, 455 enabling 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 utilizing 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 to begin an instant messaging 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 communications system 600 is capable of delivering and exchanging information between a client system 605 and a host system 610 through a communication link 615. Client system 605 typically includes one or more client devices 620 and one or more client controllers 625 for controlling the client devices 620. Host system 610 typically includes one or more host devices 635 and one or more host controllers 640 for controlling the host devices 635. The communication link may include communication pathways 650, 655 enabling communications through the one or more delivery networks 660. The network 660 may be any known or described delivery network including, but not limited, to a telephone network and/or the Internet.


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


The client system 605 includes a client device 620 and a client controller 625. The client controller 625 is capable of establishing a connection to the host system 610 through the delivery network 615. In one implementation, the client controller 625 includes one or more applications, such as an IM application, an OSP application, and/or an Internet browser application.


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


The host device 635 includes a mail gateway 6350 having a send mail server 6352 and a read mail server 6354. The send mail server 6352 is configured to perform functions relating to transmitting electronic data. The read mail server 6354 is configured to perform functions relating to receiving and accessing electronic data. The mail gateway 6350 is in communication with one or more processing servers 6360.


The mail gateway 6350 also is in communication with the storage area 6370 and a tandem database 6380. The storage area 6370 includes electronic content databases 6372, 6374 and attachment database 6376. The tandem database 6380 includes a system of folders that store electronic data for subscribers of the host system 610.


The host device 635 also includes an IM host complex 6390. The IM host complex server 6390 typically has attributes comparable to some or all elements of IM host complexes 390, 490, and 590. The IM host complex 6390 includes an e-buddy server 6392 in communication with the client system 605, the read mail server 6352, a look-up server 6394, and an IM server 6396. The IM server 6396 is capable of supporting instant messaging services, the look-up server 6394 is capable of finding subscriber account information (e.g., screen name) from a given e-mail address, and the e-buddy server is 6392 is capable of configuring IM communication between the intended recipient of an e-mail message and the sender and/or other recipients of the e-mail message.


Referring to FIG. 7, a sender 702 and a host 704 interact according to a procedure 700 to transmit electronic data. The procedure 700 may be implemented by any type of hardware, software, device, computer, computer system, equipment, component, program, application, code, storage medium, or propagated signal.


Examples of each element of FIGS. 7 and 8 are broadly described above with respects to FIGS. 1-6. In particular, the sender 702 typically has attributes comparable to those described with respect to client devices 120, 220, 320, 420, 520, and 620 and/or client controllers 125, 225, 325, 425, 525, and 625. The host 704 typically has attributes comparable to those described above with respect to host devices 135, 235, 335, 435, 535, and 635 and/or host controllers 140, 240, 340, 440, 540, and 640. The sender 702 and/or the host 704 may be directly or indirectly interconnected through a known or described delivery network.


Initially, the sender 702 transmits electronic data to the host 704 (step 705). In one implementation, the sender 702 is a client system 605 associated with an end user of the communication system 600. In another implementation, the sender 702 aids the client system 605 in transmitting electronic data through a communications link 615 to the host system 610. In yet another implementation, the sender 702 is a processing server 6360 within the host system 610. For example, the processing server 6360 may be a web mail server arranged to store and forward electronic data transmitted between end users of the communication system 600.


The host 704 receives the electronic data from the sender 702 (step 710). In one implementation, the mail gateway 6350 receives the electronic data from the client system 605 and/or the processing server 6360. Typically, the mail gateway 6350 will receive electronic content from subscribers through a dial-up telephone network or DSL (digital subscriber line) and will receive electronic content from non-subscribers indirectly through the Internet. The mail gateway 6350 may perform protocol conversions if necessary to receive electronic content from non-subscribers.


After receiving the electronic data from the sender 702 (step 710), the host 704 determines one or more attributes of the electronic data (step 715). Attributes of the electronic data may include, but are not limited to, an identification token, the author of the electronic data, the recipient(s) of the electronic data, the subject of the electronic data, the date and time of the transmission, and/or whether the electronic data contains attachments or embedded images. The host 704 typically stores the contents and attributes of the electronic data. For example, in one implementation, contents of the electronic data are stored in the storage area 6370 and the attributes of the electronic data are cached locally in the e-buddy server 6392 and also are stored in the tandem database 6380. The body of the electronic data is stored in electronic content databases 6372, 6374 and any attachments are stored in the attachment database 6376. In this example, the body of the electronic data is stored twice to assure its availability. Due to the typically large sizes of attachments, however, such objects are only stored once to conserve memory space.


The tandem database 6380 includes a system of folders corresponding to the subscribers of the host system 610. Each folder may have properties assigned by the subscriber including, for example, properties for filtering electronic content from certain sources. When electronic data are received, the folder stores the attributes of the electronic data including the location(s) of the electronic data content (i.e., body and attachments) in the storage area 6370.


The host 704 then configures an alternate communication scheme between the intended recipient and the sender 702 and/or configures an alternate communication scheme between the intended recipient and other recipients based on the detected attributes of the electronic data (step 720).



FIG. 8 illustrates one implementation of a procedure 800 for configuring an alternate communications scheme. Initially, the e-buddy server 6392 detects an identification token associated with incoming electronic data (e.g., an e-mail message) (step 805). The identification token may be intercepted by the e-buddy server 6392 and/or presented to the e-buddy server 6392 by the client system 605, the processing server 6360, and/or the read mail server 6352. By referencing the token, the e-buddy server 6392 accesses a cache (step 810) and determines whether attributes of the electronic data are stored locally (step 815). Such attributes may include, but are not limited to, a listing of the sender and all recipients associated with the electronic data.


If attributes of the electronic data are stored locally, the e-buddy server 6392 retrieves the attributes from the local cache (step 820). If, on the other hand, attributes of the electronic data are not stored locally, the e-buddy server 6392 determines the attributes of the electronic data (step 825) and then stores the attributes in a local cache (step 830). The e-buddy server 6392 may determine the attributes of the electronic data itself and/or access another server to determine the attributes. In one implementation, the e-buddy server 6392 accesses the read mail server 6354. The read mail server 6354 then determines attributes of the electronic data, including a listing of the sender and the recipients associated with the electronic data, and presents the attributes to the e-buddy server 6392. The e-buddy server 6392 receives the listing from the read mail server 6354 and stores the listing in a local cache.


The sender and the recipients listed may or may not be subscribers of the communication system 600. In one implementation, the listing includes e-mail addresses of subscribers and non-subscribers. The e-buddy server 6392 strips the domain (e.g., @aol.com) from the e-mail address of a subscriber with a recognized domain to obtain the subscriber's screen name (step 835). This step facilitates the reverse look-up process.


The e-buddy server 6392 sends the listing of e-mail addresses to the look-up server 6394. The look-up server determines the instant messaging capability of each of the e-mail addresses and/or screen names (step 840). In one implementation, the look-up server 6394 determines whether each e-mail address is associated with a subscriber of the communication system 600 and/or the IM host complex 6390. In another implementation, the look-up server 6394 checks to see whether a screen name is associated with an active account having IM capability.


The look-up server 6394 reports back to the e-buddy server 6392 and identifies to the e-buddy server 6392 which of the sender and the recipients have the capability to communicate using instant messaging.


Based on this information, the e-buddy server 6392 interacts with the IM server 6396. In one implementation, the e-buddy server 6392 instructs the IM server 6396 to send an invitation to those without instant messaging capability (step 845). The invitation may invite the sender and/or recipient to subscribe to the IM host complex 6390 and/or the host system 610. For those with instant messaging capability, the e-buddy server 6392 requests the IM server 6396 to identify the IM state of the particular user (e.g., online, offline, away, busy). As described above, the IM server 6396 may be a network of interconnected servers capable of determining the status or online presence of subscribers. The online presence of a particular subscriber can be detected, for example, from a persistent connection to an IM server and/or the activity of a specific control port.


In response to the request(s) from e-buddy server 6392, the IM server 6396 identifies the IM state of each of the sender and the recipients (e.g., online, offline, not a member) (step 850). In one implementation the IM state is given by whether each of the sender and recipients is online, offline, or does not have instant messaging capability. The IM server 6396 and/or the e-buddy server 6392 reports the IM state of each of the sender and recipients to the intended recipient (step 855). In one implementation, a particular graphical user interface is displayed to the recipient based on the IM state. For example, upon opening an e-mail message, the recipient may receive one or more redirection commands based on the IM state of the sender and any other addressees of the e-mail message. The redirection command may include a URL for navigating the recipient's browser to a particular URL associated with a graphical user interface and/or an icon corresponding to one of the IM states.


Referring to FIG. 9, a UI 900 illustrates an example of how the IM state of each of the sender and to recipients may be reported to the intended recipient. The UI 900 includes a buddy list window. In this example, the people on an e-mail message who are able to receive instant messages will appear in the buddy list window in a new group called Mail Contacts. A user may send an instant message to a person in the Mail Contacts list by clicking that person's screen name.



FIG. 10 illustrates another example of how the IM state of each of the sender and the recipients may be represented. An icon next to a person's address in an e-mail message may indicate to the recipient that the person has IM capability. By clicking on the person's address, the recipient may launch an instant message. Where an icon does not appear next to a person's address, the person does not presently have IM capability. By clicking on the person's address, the recipient may send an e-mail message to the person. If the person is not a member of any IM service, the recipient can send the person an invitation.


Other implementations are within the scope of the following claims. For example, The general aspects described above relate to instant messaging and e-mail as well as other forms of communication such as, for example, telephonic communication (e.g., mobile phones, pagers).

Claims
  • 1. A computer-implemented method comprising: receiving, over a network, a first communication from a sender via a first communication system;identifying, from the first communication, users party to the first communication;determining, in response to receiving the first communication, whether the identified users party to the first communication are online on a second communication system by: extracting addresses of the identified users;removing domain information from the addresses to obtain user identifiers;performing a reverse look-up process using the user identifiers; andpresenting, based on determining that one or more identified users of the identified users party to the first communication are online on the second communication system, an option within the first communication system to initiate a second communication with the one or more identified users via the second communication system, wherein the option to initiate the second communication is provided only when the one or more identified users are online on the second communication system.
  • 2. The method of claim 1, further comprising locating one or more addresses of identified users party to the first communication within an address field of the first communication.
  • 3. The method of claim 2, wherein removing domain information from the addresses to obtain the user identifiers comprises stripping domain information from the extracted addresses of the identified users to obtain the user identifiers.
  • 4. The method of claim 1, wherein one or more user identifiers of the user identifiers comprise one or more screen names of the identified users.
  • 5. The method of claim 4, wherein performing the reverse look-up process using the user identifiers comprises looking-up, from a subscriber database utilizing the user identifiers, online statuses for the identified users on the second communication system.
  • 6. The method of claim 1, wherein the first communication system is an electronic messaging network that facilitates communication of electronic messages, and wherein the second communication system is an instant messaging network that facilitates communication of instant messages.
  • 7. The method of claim 1, wherein presenting the option within the first communication to initiate the second communication with the one or more identified users of the identified users party to the first communication via the second communication system comprises causing a messaging window to open, the messaging window allowing a user of the first communication to compose an instant message to the one or more identified users via the second communications system.
  • 8. The method of claim 1, wherein the first communication comprises an email.
  • 9. The method of claim 1, wherein the first communication comprises an instant message.
  • 10. The method of claim 1, further comprising presenting, based on determining that the one or more identified users of the identified users party to the first communication are online on the second communication system, one or more icons next to one or more identifiers of the one or more identified users in the first communication.
  • 11. 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: receive, over a network, a first communication from a sender via a first communication system;identify, from the first communication, users party to the first communication;determine, in response to receiving the first communication, whether the identified users party to the first communication are online on a second communication system by: extracting addresses of the identified users;removing domain information from the addresses to obtain user identifiers;performing a reverse look-up process using the user identifiers; andpresent, based on determining that one or more identified users of the identified user party to the first communication are online on the second communication system, an option within the first communication system to initiate a second communication with the one or more identified users via the second communication system, wherein the option to initiate the second communication is provided only when the one or more identified users are online on the second communication system.
  • 12. The system of claim 11, wherein one or more user identifiers of the user identifiers comprise one or more usernames of the identified users.
  • 13. The system of claim 12, wherein the instructions, when executed by the at least one processor, cause the system to perform the reverse look-up process using the user identifiers by looking-up, from a subscriber database utilizing the user identifiers, online statuses for the identified users on the second communication system.
  • 14. The system of claim 11, further comprising instructions that, when executed by the at least one processor, cause the system to locate one or more addresses of identified users party to the first communication within an address field of the first communication.
  • 15. The system of claim 14, wherein the instructions, when executed by the at least one processor, cause the system to remove domain information from the addresses to obtain the user identifiers by stripping domain information from the extracted addresses of the identified users to obtain the user identifiers.
  • 16. The system of claim 11, wherein the first communication system is an electronic messaging network that facilitates communication of electronic messages, and wherein the second communication system is an instant messaging network that facilitates communication of instant messages.
  • 17. The system of claim 11, wherein the instructions, when executed by the at least one processor, cause the system to present the option within the first communication to initiate the second communication with the one or more identified users of the identified users party to the first communication via the second communication system by causing a messaging window to open, the messaging window allowing a user of the first communication to compose an instant message to the one or more identified users via the second communications system.
  • 18. The system of claim 11, wherein the first communication comprises an email.
  • 19. The system of claim 11, further comprising instructions that, when executed by the at least one processor, cause the system to present, based on determining that the one or more identified users of the identified users party to the first communication are online on the second communication system, one or more icons next to one or more identifiers of the one or more identified users in the first communication.
  • 20. A non-transitory computer-readable medium storing instructions that, when executed by at least one processor, cause a client device to: receive, over a network, a first communication from a sender via a first communication system;identify, from the first communication, users party to the first communication;determine, in response to receiving the first communication, whether identified users party to the first communication are online on a second communication system by: extracting addresses of the identified users;removing domain information from the addresses to obtain user identifiers;performing a reverse look-up process using the user identifiers; andpresent, based on determining that one or more identified users of the identified users party to the first communication are online on the second communication system, an option within the first communication system to initiate a second communication with the one or more identified users via the second communication system, wherein the option to initiate the second communication is provided only when the one or more identified users are online on the second communication system.
CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No. 14/690,201 filed on Apr. 17, 2015, which is a continuation of U.S. application Ser. No. 13/616,666 filed on Sep. 14, 2012, which is a continuation of U.S. application Ser. No. 11/150,180 filed on Jun. 13, 2005 and now issued as U.S. Pat. No. 8,474,628, which is a continuation of U.S. application Ser. No. 09/848,232 filed on May 4, 2001 and now issued as U.S. Pat. No. 6,912,564, which claims the benefit of U.S. Provisional Application Nos. 60/229,331 filed on Sep. 1, 2000 and 60/201,738 filed on May 4, 2000. Each of the aforementioned applications and patents is hereby incorporated by reference in their entirety.

US Referenced Citations (407)
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
5765033 Miloslavsky 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
5838458 Tsai 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
5870549 Bobo, II Feb 1999 A
5870744 Sprague Feb 1999 A
5872521 Loptaukin 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
5974446 Sonnenreich et al. Oct 1999 A
5983369 Bakoglu et al. 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
6009462 Birrell 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
6018571 Langlois et al. Jan 2000 A
6026403 Siefert Feb 2000 A
6026429 Jones et al. Feb 2000 A
6134432 Holmes et al. Apr 2000 A
6065047 Carpenter et al. May 2000 A
6067548 Cheng 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
6122647 Horowitz et al. Sep 2000 A
6049533 Norman 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
6175859 Mohler Jan 2001 B1
6189019 Blumer et al. Feb 2001 B1
6192395 Lemer et al. Feb 2001 B1
6195354 Skalecki et al. Feb 2001 B1
6199103 Sakaguchi et al. Mar 2001 B1
6208659 Govindarajan et al. Mar 2001 B1
6212548 DeSimone et al. Apr 2001 B1
6212550 Segur Apr 2001 B1
6223213 Cleron et al. Apr 2001 B1
6233318 Picard et al. May 2001 B1
6233577 Ramasubramani et al. May 2001 B1
6240430 Deike et al. May 2001 B1
6249740 Ito et al. Jun 2001 B1
6249743 Ito et al. Jun 2001 B1
6260148 Aggarwal et al. Jul 2001 B1
6269369 Robertson Jul 2001 B1
6269405 Dutcher et al. Jul 2001 B1
6301609 Aravamudan et al. Oct 2001 B1
6311211 Shaw Oct 2001 B1
6313855 Shuping et al. Nov 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
6349327 Tang et al. Feb 2002 B1
6351698 Kubtoa et al. Feb 2002 B1
6353825 Ponte Mar 2002 B1
6356922 Schilit et al. Mar 2002 B1
6360215 Judd et al. Mar 2002 B1
6363392 Halstead et al. Mar 2002 B1
6366950 Scheussler et al. Apr 2002 B1
6370497 Knowles Apr 2002 B1
6374246 Matsuo Apr 2002 B1
6374290 Scharber et al. Apr 2002 B1
6381593 Yano 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
6400845 Volino Jun 2002 B1
6405035 Singh Jun 2002 B1
6405249 Matsuda et al. Jun 2002 B1
6408316 Himmel et al. Jun 2002 B1
6415318 Aggarwal et al. Jul 2002 B1
6421439 Liffick Jul 2002 B1
6421709 McCormick et al. Jul 2002 B1
6424828 Collins et al. Jul 2002 B1
6425012 Trovato et al. Jul 2002 B1
6430344 Dixon et al. Aug 2002 B1
6430604 Ogle et al. Aug 2002 B1
6434601 Rollins Aug 2002 B1
6442546 Biliris et al. Aug 2002 B1
6446112 Bunney et al. Sep 2002 B1
6449344 Goldfinger et al. Sep 2002 B1
6449634 Capiel Sep 2002 B1
6463461 Hanson et al. Oct 2002 B1
6467080 Devine et al. Oct 2002 B1
6480885 Olivier Nov 2002 B1
6484196 Maurille Nov 2002 B1
6493692 Kobayashi et al. Dec 2002 B1
6493705 Kobayashi et al. Dec 2002 B1
6501834 Milewski et al. Dec 2002 B1
6505197 Sundaresan et al. Jan 2003 B1
6507845 Cohen et al. Jan 2003 B1
6507866 Barchi Jan 2003 B1
6519602 Sundaresan et al. Feb 2003 B2
6525747 Bezos Feb 2003 B1
6526400 Takata et al. Feb 2003 B1
6529475 Wan et al. Mar 2003 B1
6535586 Cloutier et al. Mar 2003 B1
6539421 Appelman et al. Mar 2003 B1
6545722 Schultheiss et al. Apr 2003 B1
6546002 Kim Apr 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
6567801 Chiang 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
6584469 Chiang et al. Jun 2003 B1
6587691 Granstam et al. Jul 2003 B1
6606647 Shah et al. Aug 2003 B2
6615241 Miller et al. Sep 2003 B1
6618747 Flynn et al. Sep 2003 B1
6636733 Helferich Oct 2003 B1
6640230 Alexander et al. Oct 2003 B1
6651058 Sundaresan et al. Nov 2003 B1
6654683 Jin et al. Nov 2003 B2
6654741 Cohen et al. Nov 2003 B1
6658623 Schilit et al. Dec 2003 B1
6665665 Ponte Dec 2003 B1
6671508 Mitsuoka et al. Dec 2003 B1
6671714 Weyer Dec 2003 B1
6677968 Appelman Jan 2004 B1
6677976 Parker et al. Jan 2004 B2
6678719 Stimmel Jan 2004 B1
6685475 Maruyama et al. Feb 2004 B1
6691162 Wick Feb 2004 B1
6697807 McGeachie Feb 2004 B2
6701348 Sommerer Mar 2004 B2
6714791 Friedman Mar 2004 B2
6714793 Carey et al. Mar 2004 B1
6718313 Lent et al. Apr 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
6751777 Bates et al. Jun 2004 B2
6757365 Bogard Jun 2004 B1
6757732 Sollee et al. Jun 2004 B1
6763373 Shiigi Jul 2004 B2
6772188 Cloutier Aug 2004 B1
6772196 Kirsch et al. Aug 2004 B1
6781608 Crawford Aug 2004 B1
6785554 Amerga Aug 2004 B1
6785681 Keskar et al. Aug 2004 B2
6788769 Waites Sep 2004 B1
6795853 Snover Sep 2004 B1
6795863 Doty, Jr. Sep 2004 B1
6799039 Wu et al. Sep 2004 B2
6800031 Di Cesare Oct 2004 B2
6807574 Partovi et al. Oct 2004 B1
6834276 Jensen et al. Dec 2004 B1
6839737 Friskel Jan 2005 B1
6857006 Nishizawa Feb 2005 B1
6862710 Marchisio Mar 2005 B1
6879665 Cook et al. Apr 2005 B1
6901559 Blum et al. May 2005 B1
6904026 Tarnanen et al. Jun 2005 B1
6907243 Patel 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
6952279 Iida Oct 2005 B1
6968179 De Vries Nov 2005 B1
6975719 Gao et al. Dec 2005 B1
6976209 Storisteanu et al. Dec 2005 B1
6993564 Whitten, II Jan 2006 B2
6996520 Levin Feb 2006 B2
7003719 Rosenoff et al. Feb 2006 B1
7035865 Doss et al. Apr 2006 B2
7035923 Yoakum et al. Apr 2006 B1
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
7076546 Bates et al. Jul 2006 B1
7082047 Chow Jul 2006 B2
7082407 Bezos et al. Jul 2006 B1
7100116 Shafrir et al. Aug 2006 B1
7103846 Shafrir et al. Sep 2006 B1
7107526 Weller Sep 2006 B1
7110510 Shaffer et al. Sep 2006 B1
7120687 Tessman, Jr. et al. Oct 2006 B1
7120871 Harrington Oct 2006 B1
7124123 Roskind et al. Oct 2006 B1
7127232 O'Neil et al. Oct 2006 B2
7143356 Shafrir et al. Nov 2006 B1
7149208 Mattaway et al. Dec 2006 B2
7165213 Busey et al. Jan 2007 B1
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
7233948 Shamoon et al. Jun 2007 B1
7233992 Muldoon et al. Jun 2007 B1
7263526 Busey et al. Aug 2007 B1
7275206 Bates et al. Sep 2007 B1
7275215 Werndorfer et al. Sep 2007 B2
7277912 Corboy et al. Oct 2007 B2
7313760 Grossman et al. Dec 2007 B2
7359938 Davies et al. Apr 2008 B1
7366764 Vollebregt Apr 2008 B1
7373428 Armstrong et al. May 2008 B1
7436780 Stephens et al. Oct 2008 B2
7437413 Okuyama et al. Oct 2008 B2
7512407 Wu et al. Mar 2009 B2
7512652 Appelman et al. Mar 2009 B1
7525951 Musil et al. Apr 2009 B2
7603411 Davies et al. Oct 2009 B1
7620722 Ruparel Nov 2009 B1
7686693 Danieli et al. Mar 2010 B2
7765484 Roskind Jul 2010 B2
7949722 Ullman et al. May 2011 B1
7979802 Appelman Jul 2011 B1
8001190 Bernstein Aug 2011 B2
8122363 Appelman Feb 2012 B1
8132110 Appelman et al. Mar 2012 B1
8275661 Ponte et al. Sep 2012 B1
8474628 Appelman Jul 2013 B1
8959164 Appelman Feb 2015 B2
9043418 Appelman May 2015 B2
9100221 Appelman Aug 2015 B2
20010005861 Mousseau et al. Jun 2001 A1
20010013050 Shah Aug 2001 A1
20010044828 Kikinis Nov 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
20020042816 Bae Apr 2002 A1
20020049717 Routtenberg et al. Apr 2002 A1
20020056123 Liwerant et al. May 2002 A1
20020065856 Kisiel May 2002 A1
20020065894 Dalal et al. May 2002 A1
20020069223 Goodisman et al. Jun 2002 A1
20020077080 Greene Jun 2002 A1
20020083136 Whitten, II Jun 2002 A1
20020091667 Jaipuria et al. Jul 2002 A1
20020099779 Scheussler et al. Jul 2002 A1
20020103801 Lysons Aug 2002 A1
20020112181 Smith Aug 2002 A1
20020116336 Diacakis et al. Aug 2002 A1
20020116463 Hart Aug 2002 A1
20020116641 Mastrianni Aug 2002 A1
20020130904 Becker et al. Sep 2002 A1
20020133292 Miyaki Sep 2002 A1
20020133369 Johnson Sep 2002 A1
20020147777 Hackbarth et al. Oct 2002 A1
20020154210 Ludwig et al. Oct 2002 A1
20020174010 Rice, III 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
20030009385 Tucciarone et al. Jan 2003 A1
20030009523 Lindskog et al. Jan 2003 A1
20030012348 Skladman 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
20030069874 Hertzog et al. Apr 2003 A1
20030079024 Hough et al. Apr 2003 A1
20030084103 Weiner et al. May 2003 A1
20030093580 Thomas et al. May 2003 A1
20030097361 Huang 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
20030165219 Bedingfield et al. Sep 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
20030217073 Walther et al. Nov 2003 A1
20030225834 Lee et al. Dec 2003 A1
20030225847 Heikes et al. Dec 2003 A1
20030236835 Levi et al. Dec 2003 A1
20040015548 Lee Jan 2004 A1
20040017396 Werndorfer et al. Jan 2004 A1
20040039779 Amstrong et al. Feb 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
20040193722 Donovan Sep 2004 A1
20040210844 Pettinati et al. Oct 2004 A1
20040215648 Marshall Oct 2004 A1
20040215721 Szeto et al. Oct 2004 A1
20040249899 Shiigi Dec 2004 A1
20040260762 Fish Dec 2004 A1
20050015432 Cohen Jan 2005 A1
20050021750 Abrams Jan 2005 A1
20050027382 Kirmse et al. Feb 2005 A1
20050027716 Apfel 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
20080222533 Hankejh et al. Sep 2008 A1
20090089316 Kogan et al. Apr 2009 A1
20100184517 Danieli et al. Jul 2010 A1
20110231507 Appelman Sep 2011 A1
20120030295 Bernstein Feb 2012 A1
20120144310 Appelman Jun 2012 A1
20130067339 Appelman Mar 2013 A1
20130067340 Appelman Mar 2013 A1
20130067341 Appelman Mar 2013 A1
20130073645 Appelman Mar 2013 A1
20130073648 Appelman Mar 2013 A1
20130073651 Appelman Mar 2013 A1
20130073652 Appelman Mar 2013 A1
20130124650 Bernstein May 2013 A1
20130275526 Appelman Oct 2013 A1
20130332957 DeWeese et al. Dec 2013 A1
20150113440 Appelman Apr 2015 A1
20160294740 Bernstein Oct 2016 A1
20160301654 Bernstein Oct 2016 A1
20160380934 Appelman Dec 2016 A1
Foreign Referenced Citations (36)
Number Date Country
0862304 Sep 1998 EP
1176840 Jan 2002 EP
2319137 May 1998 GB
2357932 Jul 2001 GB
2368747 May 2002 GB
8-314826 Nov 1996 JP
2000-049901 Feb 2000 JP
2000-259514 Sep 2000 JP
2000-284999 Oct 2000 JP
2001-084320 Mar 2001 JP
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 May 2001 WO
WO 0167787 Sep 2001 WO
WO 0172020 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 04028178 Apr 2004 WO
WO 05086723 Sep 2005 WO
Non-Patent Literature Citations (369)
Entry
U.S. Appl. No. 13/616,630, Dec. 31, 2015, Office Action.
U.S. Appl. No. 13/616,707, Dec. 16, 2015, Office Action.
U.S. Appl. No. 13/616,734, Feb. 2, 2016, Office Action.
U.S. Appl. No. 13/617,413, Jan. 29, 2016, Notice of Allowance.
U.S. Appl. No. 13/617,374, Jan. 5, 2016, Office Action.
U.S. Appl. No. 13/620,985, Mar. 2, 2016, Notice of Allowance.
U.S. Appl. No. 13/617,402, Jan. 13, 2016, Office Action.
U.S. Appl. No. 13/784,647, Feb. 26, 2016, Office Action.
U.S. Appl. No. 13/396,132, Mar. 15, 2016, Notice of Allowance.
U.S. Appl. No. 13/616,630, Jul. 14, 2016, Office Action.
U.S. Appl. No. 13/616,707, Jun. 15, 2016, Office Action.
U.S. Appl. No. 13/617,374, Aug. 23, 2016, Office Action.
U.S. Appl. No. 13/617,402, Aug. 18, 2016, Notice of Allowance.
U.S. Appl. No. 14/586,793, Jun. 22, 2016, Notice of Allowance.
U.S. Appl. No. 14/690,201, Jul. 5, 2016, Office Action.
U.S. Appl. No. 13/175,410, Oct. 18, 2016, Notice of Allowance.
U.S. Appl. No. 13/616,707, Oct. 6, 2016, Office Action.
U.S. Appl. No. 13/784,647, Sep. 20, 2016, Office Action.
“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 pgs, 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.
“What's new about exchanging information over the Internet,” Outlook 2000 SR-1 (9.0.0.4527) Help File, on or before Aug. 10, 2001, p. 1.
“About Internet directory services,” Outlook 2000 SR-1 (9.0.0.4527) Help File, on or before Aug. 10, 2001, p. 1.
“Set up LDAP directory services,” Outlook 2000 SR-1 (9.0.0.4527) Help File, on or before Aug. 10, 2001, p. 1.
“Look up contact information from an item,” Outlook 2000 SR-1 (9.0.0.4527) 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/en-us/dnactdir/html/deal.asp?frame=true>, pp. 1-18.
Microsoft Corporation, “Using ADSI, LDAP, and Network Management Functions With Active Directory,” [online], Feb. 2002 [retrieved on May 13, 2003]. Retrieved from the Internet <http://msdn.microsoft.com/library/en-us/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.comllibrary/en-us/dnactdir/html/msdnactivedirvsnds.asl2?frame=true>, pp. 1-17.
Microsoft Corporation, “Active Directory Services Interface in the Microsoft Exchange 5.5 Environment,” [online], Nov. 1997 [retrieved on Mar. 13, 2003). Retrieved from the Internet <http://msdn.microsoft.com/library/en-us/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://www.microsoft.com/windows2000/server/evaluation/business/addatasheet.asp>, pp. 1-5.
“Integrating Microsoft Metadirectory Services and Active Directory,” [online], Aug. 31, 2000 [retrieved on May 13, 2003]. Retrieved from the Internet <http://www.microsoft.comlwindows2000/server/evaluation/news/bulletins/mmsma.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>, p. 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/JuI98/ActivDPR.asp>, pp. 1-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.
“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.
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 Application No. PCT/US03/15715 dated Aug. 14, 2003.
“The LP Wireless Messenger”, Messenger Documentation, [online]. LP Wireless, Inc., 2001 [retrieved on Nov. 2, 2002]. Retrieved from the Internet <http://www.lpwireless.com/messengerhelp.htm>, pp. 1-7.
European Search Report dated Aug. 30, 2005 for European Application No. 03731244.
“Introducing the Gordano Messaging Suite”; http://www.gordano.com; Copyright 1994-2003 Gordano.
McKendrick, Joseph; “Internet Call Centers: New Era in Customer Service”; Feb. 2002; V. 10, N. 2, pp. 22(4).
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 Browsers”, Mar. 5, 2001, Internet: www.webmaster.com/forum21/367.htm.
“AOL Instant Messenger All New Version 2.0”, 2 pages, Jun. 24, 1999.
“Frequently Asked Questions About AOL Instant Messenger”, 6 pages, Jun. 24, 1999.
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.
“Using Active Directory Service”, from Chapter 5, Microsoft Windows 2000 Administrator's Pocket Consultant, by William R. Stanek (1999). Retrieved from http://www.microsoft.com/technet/12rodtechnoI/ad/windows2000/evaluate/05w2kadb.asp?fr . . . , pp. 1-6.
“What is AOL Instant Messenger”, 3 pages, Jun. 24, 1999.
“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?ft . . . , pp. 1-10.
“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.
“About File Transfers”, AOL Instant Messenger, version 4.3, Help Documentation, available on Jul. 21, 2001, 5 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.
“BestCalls.com Announces the BestCalls Technology Index,” Business Wire, Jun. 30, 1999, Business Wire, p. 2.
“Better Bayesian Filtering,” Paul Graham, Jan. 2003, pp. 1-11, http://www.paulgraham.co/better.html.
“Business at Cyberspeed; Brainstorm Becomes Quick Internet Hit,” Walker, Jan. 24, 1999, The Washington Post, p. A.01 (4 total pages).
“Degrees of Separation Email Spam Protection,” Halfbakery: Degrees of Separation Email Spam Protection, reprinted from http://halfbakery.com/idea/Degrees_20of_20Separation_20Emaii_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 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,” Carlos Jensen et al., Apr. 20-25, 2002, CHI, Minneapolis, Minnesota, vol. 4, Issue 1, pp. 447-454.
“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 , 2 pages.
“Hottie or Nottie? Web Site Voters Let You Know Whether You Sizzle or Fizzle,” Marino, Jul. 11, 2001, Florida Times Union, 2 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?adxnnlx=0&adxnnlx=107029 . . . , printed on Nov. 5, 2004, 2 pages.
“Instant Messaging for Gamers,” PC Gamer, May 2004, vol. 11, No. 5, (2 pages).
“Learning Spam: Simple Techniques for Freely-Available Software,” Bart Massey et al., Computer Science Dept., Portland, OR USA, 2003, pp. 1-14.
“Learning to Filter Spam E-Mail: A Comparison of a Naive 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.
“PieSpy—Inferring and Visualizing Social Network on IRC,” PieSpy Social Network Bot, reprinted from http://lister.linux-srv.anix.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, 4 pages.
“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, (1 page).
“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 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 (3 pages).
“Socialware: Multiagent Systems for Supporting Network Communities,” Hattori et al., Mar. 1999, Association for Computing Machinery, Communications of the ACM, vol. 42, Issue 3, (6 pages).
“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 aI., 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, (1 page).
“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, 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.
“Welcome to Huminity World of Connections,” Huminity-Home, reprinted from http://web.archive.org/web/20030228131435/www.huminity.com/default.php?international . . . printed on Nov. 5, 2004 (available on Feb. 2013) (1 page).
“Will You Buy a Car From This Man?,” Leander Kahney, Oct. 6, 2003. pp. 1-3.
Windows NetMeeting—Features, [Online], Jun. 17, 1999, XP002245623, Retrieved from the Internet: URL:http://www.microsoft.com/windows/NetMeeting/Features/default.ASP>, (8 pages).
Anand Ranganalhan et al., “ConChat: A Context-Aware Chat Program”, 2002, Pervasive Computing, pp. 51-57.
Announce: Implementation of E-mail Spam Proposal, Maurice L. Marvin, news.admin.net-abuse.misc, Aug. 3, 1996,2 pages.
Anonymous: “Push to Talk™ Services”, Internet Document, [Online], p. 1, Retrieved from the Internet: URL: http://www.nextel.com/services/directconnect/pttoverview.shtml [retrieved on Dec. 29, 2003].
Anonymous: “The Internet—the Advent of New Forms of Communication”, Internet Document, [Online], pp. 1-4, Retrieved from the Internet: URL: http://journal.fujitsu.com/248e/e48now.html [retrieved on Dec. 29, 2003].
Archive.org archived copy of “AOL Instant Messenger,” [online] Jul. 21, 2001 [from file of U.S. Appl. No. 09/911,799] (7 pages).
Archive.org archived copy of the Morpheus 1.9.1 download page on CNet Download.com [online] Oct. 8, 2001 [from file of U.S. Appl. No. 09/911,799] (2 pages).
Archive.org archived copy of the MusicCity Morpheus download page on Cnet Download.com [online] Oct. 8, 2001 [from file of U.S. Appl. No. 09/911,799] (2 pages).
Australian Office Action of Apr. 7, 2006, App. No. 2002340039 (2 pages).
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/200409241 04001/http://www.buddygopher.com/ on Sep. 28, 2005 (2 pages).
Canadian Office Action from Application Serial No. 2,403,520, dated Feb. 21, 2005 (2 pages).
Chinese Office Action dated Jul. 7, 2006, App. No. 02821420X (5 pages).
International Search Report and Written Opinion dated Feb. 15, 2006 for International Application No. PCT/US05/07204, (10 pages).
European Search Report dated Aug. 30, 2005 for International Application No. EP03731244 (4 pages).
Office Action dated approximately Feb. 29, 2006 for Japanese Patent Application No. 2002-515026 (6 pages).
Supplementary European Search Report issued in European Application No. EP05728303, dated Jan. 9, 2009, (2 pages).
Courter et al., “Mastering Microsoft Outlook 2000 Premium Edition”, Sybex Inc., Alameda, California, 2000, pp. 167-169, ISBN 0-7821-2676-6.
CrushParty.com: Help, retrieved Jun. 12, 2002 from the World Wide Web: http://www.crushparty.com/help.jsp, (3 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/helptext.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/helpbasics.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.ora/web/20041009201853/www.dodgeball.com/social/helpuseit.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.phpon Sep. 28, 2005 (2 pgs).
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, dated Jul. 14, 2008, 3 pages.
European Patent Office, Communication of Aug. 30, 2005, App. No. 03731244.4-2416 (PCT/US0315715) (4 pages).
European Patent Office, Communication of Aug. 31, 2009, App. No. 02778374.5-1238 (8 pages).
European Patent Office, Communication of Sep. 5, 2006, App. No. 02778374.5-1238 (3 pages).
Examiner's Answer dated Jan. 11, 2008 by USPTO in U.S. Appl. No. 09/810,159, 11 pages.
Home-tribe.net, http://washingtondc.tribe.net/message/24434d1b-817b-4580-aa42-3bffa15f26a?page=1, reprinted on Dec. 13, 2004), (2 pages).
http://www.friendster.com (reprinted on Dec. 13, 2004) (17 pages).
IBM “Configuring Sametime servers in your Domino environment” May 1, 2000 (14 pages).
International Search Report and Written Opinion for PCT Application No. PCT/US2005/042992, dated Mar. 6, 2007 (8 pages).
International Search Report dated Oct. 16, 2006, for PCT/US05/08476, (9 pages).
International Search Report, Application No. PCT/US05/45663, dated Apr. 11, 2008, (10 pages).
Opinion of International Search Authority, Application No. PCT/US05/45663, dated Apr. 11, 2008, (6 pages).
International Search Report, Application Serial No. PCT/US2006/018286, dated Oct. 19, 2006, (10 pages).
Isaacs, Ellen: “Example UI Spec: Sound Instant Messages”, Internet Document, [Online], Retrieved from the Internet: URL: http://www.uidesigns.com/spec/d-sims.html [retrieved on Jun. 26, 2003] (2 pages).
Japanese Office Action of May 12, 2008, App. No. 2003-533140 (5 pages).
Klaus Hartenstein et al., “xhtalk 2.9”, © Nov. 1992, (6 pages).
Lotus sametime 1.5 1999 (4 pages).
Mariano, Gwendolyn. ZDNetNews. “Morpheus 1.9 to be unleashed”, [online] Jun. 10, 2002 [from file of U.S. Appl. No. 09/911,799] (6 pages).
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, 4 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.
Mike Snider, “America goes online for New Year's bash”, USA Today, Jan. 2, 2000 1 page.
Muller, Nathan, “Dial 1-800-Internet”; Feb. 1996, pp. 83-84, 86, 88.
Neo Mai, Ken Neo. “Buying and selling on the internet; [Computimes, 2* Edition].” New Straits Times. Kuala Lumpur: Jun. 28, 2001. 3 pages.
Office Action of Canadian Application No. 2,462,037, dated Feb. 12, 2009 (8 pages).
PCT International Search Report dated Apr. 11, 2003, App. No. PCT/US00/35160 (3 pages).
PCT International Search Report dated Jan. 9, 2003, App. No. PCT/US02/30730 (5 pages).
PowWow (2000, Mar. 1), Introduction, Retrieved Apr. 3, 2006 from website: http://web.archive.org/web/20000301125635/ww2.tribal.com/help/online_docs/h205voic.html. (2 pages).
Pruitt, Scarlet. IDG News Service. “Morpheus Updates Peer-to-Peer Client” [online] Jun. 10, 2002 [accessed Feb. 14, 2007], Retrieved from Internet URL: http://www.pcworld.com/article/id_101736/article.html, (3 pages).
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, Instant Messaging Planet, available at www.instantmessagingplanet.com/public/article.php/1490771, (4 pages).
Ryze home p., www.ryze.com, Dec. 21, 2003, available at http://web.archive.org/web/20031221010006/http://ryze.com, printed Mar. 16, 2005, (13 pages).
Satter, Michael, excerpts from Internet TV with CU-SeeMe, First Edition, including inside Title Page and Copyright Page; “Overview”; “Contents,” through pp. xii; Chapter 1, “Introduction to 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 O&A,” pp. 235-249; published by Sams.net Publishing, 201 W. 103rd St., Indianapolis, IN 46290, International Standard Book Number: 1-57521-006-1, Library of Congress Catalog Card No. 95-70178, copyright© 1995.
Takashi Yoshmoet al., “Namba: Location-Aware Collaboration System for Shopping and Meeting”, Aug. 2002, IEEE Transactions on Consumer Electronics, pp. 470-447.
Tribal Voice, PowWow Guided Tour—Step 6, PowWow personal communication http://web.archive.org/web/2000817094516/www.tribal.com/powwow/tour/step6.cfm (Oct. 22, 1999), (2 pages), 1998.
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).
Wayner, Peter, “Hey Baby, Call Me at My IP Address”, Apr. 1996, pp. 142-144.
WBWE (199B), PowWow 3.6 Brings the Power of Internet Community to the People, Business Wire, (2 pages), 1998.
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.
Wingfield, N., “Technology Journal: Changing Chat—Instant Messaging Is Taking Off, and for some Users It's Nuzzling Out the Phone”, Asian 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 Internet Measurement IMW'01. Nov. 2001. ACM Press. (15 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).
Dictionary.com, http://dictionary.reference/browser/dialogue, Dec. 8, 2007, 1 page.
International Search Report issued in PCT/US01/20381, dated Dec. 4, 2002.
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. 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, Advisory Action.
U.S. Appl. No. 09/843,788, Apr. 19, 2007, Office Action.
U.S. Appl. No. 09/843,788, Mar. 11, 2008, Notice of Allowance.
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/848,231, Mar. 30, 2004, Office Action.
U.S. Appl. No. 09/848,231, May 5, 2005, Office Action.
U.S. Appl. No. 09/848,231, Jun. 3, 2011, Office Action.
U.S. Appl. No. 09/848,231, Oct. 12, 2011, Notice of Allowance.
U.S. Appl. No. 09/848,232, Aug. 19, 2004, Notice of Allowance.
U.S. Appl. No. 09/848,232, Mar. 10, 2005, Notice of Allowance.
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, 2009, Office Action.
U.S. Appl. No. 09/911,799, Mar. 18, 2010, 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, Office Action.
U.S. Appl. No. 10/134,437, Sep. 6, 2007, Office 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, Oct. 2, 2009, Notice of Allowance.
U.S. Appl. No. 10/134,437, Nov. 17, 2009, Notice of Allowance.
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, Mar. 22, 2010, Office Action.
U.S. Appl. No. 10/146,814, Oct. 1, 2010, Notice of Allowance.
U.S. Appl. No. 10/146,814, Jan. 20, 2011, Notice of Allowance.
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/311,259, Jun. 26, 2006, Office Action.
U.S. Appl. No. 10/311,259, Jan. 25, 2007, Office Action.
U.S. Appl. No. 10/311,259, Apr. 16, 2007, Office Action.
U.S. Appl. No. 10/311,259, Dec. 12, 2007, Office Action.
U.S. Appl. No. 10/311,259, Mar. 19, 2008, Office Action.
U.S. Appl. No. 10/311,259, Oct. 16, 2008, Office Action.
U.S. Appl. No. 10/311,259, Apr. 27, 2009, Office Action.
U.S. Appl. No. 10/311,259, Nov. 25, 2009, Office Action.
U.S. Appl. No. 10/311,259, Mar. 18, 2010, Office Action.
U.S. Appl. No. 10/311,259, Sep. 7, 2010, Office Action.
U.S. Appl. No. 10/311,259, Dec. 22, 2010, Office Action.
U.S. Appl. No. 10/311,259, Apr. 5, 2011, 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, 2006, 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/633,636, Jun. 20, 2007, Office Action.
U.S. Appl. No. 10/633,636, May 25, 2010, Office Action.
U.S. Appl. No. 10/633,636, Nov. 9, 2010, Office Action.
U.S. Appl. No. 10/633,636, Oct. 27, 2011, Notice of Allowance.
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, Nov. 5, 2008, Office Action.
U.S. Appl. No. 11/150,180, Aug. 19, 2009, Office Action.
U.S. Appl. No. 11/150,180, Sep. 27, 2011, Notice of Allowance.
U.S. Appl. No. 11/150,180, Sep. 11, 2012, Notice of Allowance.
U.S. Appl. No. 11/150,180, Mar. 28, 2013, Notice of Allowance.
U.S. Appl. No. 11/150,180, Jun. 6, 2013, Notice of Allowance.
U.S. Appl. No. 11/237,718, Apr. 2, 2009, Office Action.
U.S. Appl. No. 11/237,718, Oct. 30, 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 28, 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. 13/149,368, Jul. 7, 2014, Office Action.
U.S. Appl. No. 13/149,368, Oct. 24, 2014, Office Action.
U.S. Appl. No. 13/149,368, Mar. 16, 2015, Office Action.
U.S. Appl. No. 13/175,410, Dec. 20, 2011, Office Action.
U.S. Appl. No. 13/175,410, Apr. 3, 2012, Office Action.
U.S. Appl. No. 13/175,410, Aug. 10, 2012, Office Action.
U.S. Appl. No. 13/175,410, Apr. 1, 2013, Office Action.
U.S. Appl. No. 13/175,410, Jul. 1, 2013, Office Action.
U.S. Appl. No. 13/175,410, Oct. 10, 2013, Office Action.
U.S. Appl. No. 13/396,132, Sep. 11, 2014, Office Action.
U.S. Appl. No. 13/396,132, Feb. 23, 2015, Office Action.
U.S. Appl. No. 13/397,568, May 9, 2013, Office Action.
U.S. Appl. No. 13/397,568, Dec. 5, 2013, Office Action.
U.S. Appl. No. 13/397,568, Jun. 6, 2014, Office Action.
U.S. Appl. No. 13/397,568, Oct. 6, 2014, Notice of Allowance.
U.S. Appl. No. 13/616,630, May 21, 2015, Office Action.
U.S. Appl. No. 13/616,707, Nov. 20, 2014, Office Action.
U.S. Appl. No. 13/616,707, Feb. 12, 2015, Office Action.
U.S. Appl. No. 13/616,734, Oct. 24, 2014, Office Action.
U.S. Appl. No. 13/616,734, Feb. 12, 2015, Office Action.
U.S. Appl. No. 13/617,413, Oct. 24, 2014, Office Action.
U.S. Appl. No. 13/617,413, Feb. 12, 2015, Office Action.
U.S. Appl. No. 13/616,666, Apr. 1, 2013, Office Action.
U.S. Appl. No. 13/616,666, Feb. 14, 2014, Office Action.
U.S. Appl. No. 13/616,666, Aug. 13, 2014, Office Action.
U.S. Appl. No. 13/616,666, Jan. 12, 2015, Notice of Allowance.
U.S. Appl. No. 13/616,666, Feb. 23, 2015, Notice of Allowance.
U.S. Appl. No. 13/616,666, Jun. 18, 2015, Notice of Allowance.
U.S. Appl. No. 13/616,678, Mar. 27, 2013, Office Action.
U.S. Appl. No. 13/616,678, Oct. 4, 2013, Office Action.
U.S. Appl. No. 13/616,678, Dec. 4, 2013, Advisory Action.
U.S. Appl. No. 13/616,678, Dec. 24, 2013, Office Action.
U.S. Appl. No. 13/616,678, Sep. 2, 2014, Office Action.
U.S. Appl. No. 13/616,678, Dec. 12, 2014, Notice of Allowance.
U.S. Appl. No. 13/616,678, Feb. 12, 2015, Notice of Allowance.
U.S. Appl. No. 13/616,692, Mar. 27, 2013, Office Action.
U.S. Appl. No. 13/617,374, May 21, 2015, Office Action.
U.S. Appl. No. 13/620,985, Jun. 17, 2013, Office Action.
U.S. Appl. No. 13/620,985, Nov. 8, 2013, Office Action.
U.S. Appl. No. 13/620,985, Mar. 12, 2014, Office Action.
U.S. Appl. No. 13/620,985, Sep. 19, 2014, Office Action.
U.S. Appl. No. 14/586,793, Jun. 19, 2015, Office Action.
U.S. Appl. No. 09/843,788, filed Apr. 30, 2001, Appelman.
U.S. Appl. No. 14/690,201, filed Apr. 17, 2015, Appelman.
Microsoft Corporation, “Comparing Microsoft Active Directory to Novell's NDS,” [online],Sep. 1998 [retrieved on May 13, 2003]. Retrieved from the Internet <http://msdn.rnicrosoft.comllibrary/en-us/dnactdir/html/msdnactivedirvsnds.asl2?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/en-us/dnactdir/html/msdn_adsiexch.asp?frame=true>, pp. 1-12.
“Integrating Microsoft Metadirectory Services and Active Directory,” [online], Aug. 31, 2000 [retrieved on May 13, 2003]. Retrieved from the Internet <http://www.microsoft.comlwindows2000/server/evaluation/news/bulletins/mmsma.asp> , p. 1.
“McKendrick, Joseph; Internet Call Centers: New Era in Customer Service”; Feb. 2002; V. 10, N. 2, pp. 22(4).
“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).
“Six Degrees—New Programs Help Companies ‘Mine Workers’ Relationships for Key Business Prospects,” William M. Bulkeley et aI., Marketplace, The Wall Street Journal, Aug. 4, 2003. (3 pages).
“Social Nets Find Friends in VCs.” Joanna Glasner. http://wwvv.wired.com/news , Nov. 17, 2003, pp. 1-3.
“Support Vector Machines for Spam Categorization,” Harris Drucker et al., IEEE Transactions on Neural Networks, vol. 10, No. 5, Sep. 1999, pp. 1048-1054.
Australian Office Action dated Apr. 7, 2006, App. No. 2002340039 (2 pages).
European Patent Office, Communication dated Aug. 30, 2005, App. No. 03731244.4-2416 (PCT/US0315715) (4 pages).
European Patent Office, Communication dated Aug. 31, 2009, App. No. 02778374.5-1238 (8 pages).
European Patent Office, Communication dated Sep. 5, 2006, App. No. 02778374.5-1238 (3 pages).
Japanese Office Action dated May 12, 2008, App. No. 2003-533140 (5 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. (2 pages).
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).
Satter, Michael, excerpts from Internet TV with CU-SeeMe, First Edition, including inside Title Page and Copyright Page; “Overview”; “Contents,” through pp. xii; Chapter 1, “Introduction to 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 O&A,” pp. 235-249; published by Sams.net Publishing, 201 W. 103rd St., Indianapolis, IN 46290, International Standard Book Number: 1-57521-006-1, Library of Congress Catalog Card Number: 95-70178, copyright © 1995.
Tribal Voice, PowWow Guided Tour—Step 6, PowWow personal communication http://web.archive.org/web/2000817094516/www.tribal.com/powwow/tour/step6.cfm (Oct. 22, 1999), (2 pages).
U.S. Appl. No. 13/149,368, Jul. 30, 2015, Office Action.
U.S. Appl. No. 13/396,132, Jul. 29, 2015, Office Action.
U.S. Appl. No. 13/616,707, Jul. 15, 2015, Office Action.
U.S. Appl. No. 13/616,734, Jul. 29, 2015, Office Action.
U.S. Appl. No. 13/620,985, Jun. 30, 2015, Office Action.
U.S. Appl. No. 13/617,402, Jul. 28, 2015, Office Action.
U.S. Appl. No. 13/784,647, Jul. 23, 2015, Office Action.
U.S. Appl. No. 14/690,201, Jul. 30, 2015, Office Action.
U.S. Appl. No. 13/617,413, Aug. 13, 2015, Office Action.
U.S. Appl. No. 14/586,793, Sep. 14, 2015, Office Action.
U.S. Appl. No. 13/175,410, Jan. 27, 2017, Notice of Allowance.
U.S. Appl. No. 13/616,630, Mar. 21, 2017, Office Action.
U.S. Appl. No. 13/616,707, Apr. 11, 2017, Office Action.
U.S. Appl. No. 13/616,734, Mar. 24, 2017, Office Action.
U.S. Appl. No. 13/617,374, Feb. 9, 2017, Notice of Allowance.
U.S. Appl. No. 15/143,111, Mar. 15, 2017, Notice of Allowance.
U.S. Appl. No. 13/784,647, Feb. 22, 2017, Notice of Allowance.
U.S. Appl. No. 13/616,630, Oct. 31, 2016, Office Action.
Haverstock, Paul, et al., “System and Method for Enabling a User to Obtain a User Status and Establish a Communication Link Using the User Status”, U.S. Appl. No. 60/137,513, filed Jun. 2, 1999; 34 pages.
U.S. Appl. No. 13/616,630, Sep. 11, 2017, Office Action.
U.S. Appl. No. 13/616,734, Jul. 21, 2017, Office Action.
U.S. Appl. No. 15/237,883, Feb. 1, 2018, Office Action.
U.S. Appl. No. 15/237,883, Jul. 26, 2018, Notice of Allowance.
Related Publications (1)
Number Date Country
20150236992 A1 Aug 2015 US
Provisional Applications (2)
Number Date Country
60229331 Sep 2000 US
60201738 May 2000 US
Continuations (4)
Number Date Country
Parent 14690201 Apr 2015 US
Child 14702516 US
Parent 13616666 Sep 2012 US
Child 14690201 US
Parent 11150180 Jun 2005 US
Child 13616666 US
Parent 09848232 May 2001 US
Child 11150180 US