Patent Grant
9615225
This description relates to communicating using an instant messaging system.
Users of an instant messaging service can communicate in virtually real time with other instant messaging users. Users may manually create a buddy list of user names of other users of the instant messaging service, and may establish instant messaging sessions with those other members using the buddy list.
In one general aspect communicating using electronic devices includes receiving an electronic message and an indication of a sender-specified destination for the electronic message. A determination is made as to whether the destination is available to receive an electronic message using a first mode of communication, and a determination is made as to whether a mobile telephone number is known by the sender to be associated with the destination. A determination whether to transmit a communication based on the electronic message using the mobile telephone number is made based on a determination that the destination is not available and that the mobile telephone number is known by the sender to be associated with the destination.
Implementations may include one or more of the following features. For example, the electronic message may be an instant message, and the destination may be an instant message identity. The instant message identity may be an identity that is not signed on to an instant message service, and determining whether the destination is available to receive an electronic message using a first mode of communication may include determining whether the instant message identity is signed on to an instant message service. A determination may be made that the destination is not available if the instant message identity is not signed on to the instant message service.
The instant message identity may be an identity that is signed on to an instant message service and is associated with an idle state. Determining whether the destination is available to receive an electronic message using a first mode of communication may include determining whether the instant message identity is signed on to an instant message service and determining whether the instant message identity is associated with an idle state if the instant message identity is determined to be signed on to the instant message service. A determination may be made that the destination is not available if the instant message identity is signed on to the instant message service and the instant message identity is associated with an idle state.
Determining whether the mobile telephone number is known by the sender to be associated with the destination may include searching electronic storage for an association of the mobile telephone number and an instant message identity. Determining whether a mobile telephone number is known by the sender to be associated with the destination may include identifying, in a collection of contact information associated with the sender, a stored association of the mobile telephone number and the instant message identity. The collection of contact information may include an address book associated with the sender or a buddy list associated with the sender. Determining whether the mobile telephone number is known by the sender may include searching the collection of contact information associated with the sender for a mobile telephone number associated with an instant message identity.
The instant message identity may be associated with a screen name, and searching the collection of contact information associated with the sender for a mobile telephone number associated with an instant message identity may include searching the collection of contact information associated with the sender for a mobile telephone number associated with the screen name associated the instant message identity.
A user name associated with the instant message identity may be identified in a buddy list associated with the sender. Searching the collection of contact information associated with the sender for a mobile telephone number associated with an instant message identity may include searching the collection of contact information associated with the sender for the user name. Determining that the mobile telephone number is known by the sender to be associated with the instant message identity may include identifying, in the collection of contact information associated with the sender, a stored association of the mobile telephone number and the user name.
A host system may perform the receiving, the determining of whether the instant message identity is available, the determining of whether the mobile telephone number is known by the sender to be associated with the instant message identity, and the determining of whether to transmit the communication. A client system may perform the receiving, the determining of whether the destination is available, the determining of whether the mobile telephone number is known by the sender to be associated with the destination, and the determining of whether to transmit the communication.
A text message may be sent to the mobile telephone number such that the text message is based on text of the electronic message. A text message may be forwarded to the mobile telephone number such that the text message is based on text of the electronic message.
Confirmation from the sender to enable transmission to the mobile telephone number may be received, and a determination to transmit may be made only after receiving confirmation from the sender that the electronic message is to be transmitted to the mobile telephone number.
A determination may be made as to whether the destination prohibits transmission of communications to the mobile telephone number based on electronic messages, and a determination to transmit may be made only after a determination is made that the destination does not prohibit transmission of communications to the mobile telephone number based on electronic messages.
An indication of whether the destination prohibits transmissions of communications based on electronic messages to the mobile telephone number may be received. Determining whether the destination prohibits transmission of a communication based on the electronic message to the mobile telephone number may include accessing the indication of whether the instant message identity prohibits transmissions. Determining whether to transmit may include only determining to transmit after a determination is made, based on the accessed indication, that the destination does not prohibit transmissions of communications based on electronic messages to the mobile telephone number.
Determining whether the destination is available to receive an electronic message addressed to the destination may include determining whether the destination is signed on to an instant message service used to send the electronic message, and the determination that the destination is not available may include a determination that the destination is not signed on to the instant message service.
Determining whether the destination is available to receive an electronic message addressed to the destination may include determining whether the destination is signed on to an instant message service used to send the electronic message and determining whether the destination is away from a client system used to access the instant message service, and the determination that the destination is not available may include a determination that the destination is signed on to the instant message service and a determination that the destination is away from the client system.
Determining whether the destination is away from a client system used to access the instant message service may include determining whether a user-configurable away indication is associated with the destination, and the determination that the destination is away from the client system may include a determination that a user-configurable away indication is associated with the destination.
In another general aspect, communicating using electronic devices includes receiving an electronic message and an indication of a sender-specified destination for the electronic message. A determination is made as to whether the destination is available to receive an electronic message using a first mode of communication, and a determination is made as to whether a second destination using a second mode of communication is known by the sender to be associated with the destination. In response to a determination that the destination is not available and that a second destination using a second mode of communication is known by the sender to be associated with the destination, transmission of a communication is enabled to the second destination and using the second mode of communication where the communication is based on the electronic message.
Implementations may include one or more of the features noted above and one or more of the following features. For example, the second destination may be selected, based on a user preference, from multiple destinations. The electronic message may be an instant message, the destination may be an instant message identity, and the first mode of communication may be instant messaging.
The second destination may include a mobile telephone number, and the second mode of communication may include sending a text message. The second destination may include an electronic mail address, and the second mode of communication may include sending an electronic mail message. The second destination may include a telephone number, and the second mode of communication may include sending a voice telephone message. The second destination may include an instant message identity available through a instant messaging service that is different from the instant messaging service that is associated with the destination.
The instant message identity may be an identity that is not signed on to an instant message service, and determining whether the destination is available to receive an electronic message using a first mode of communication may include determining whether the instant message identity is signed on to an instant message service. A determination that the destination is not available may be made if the instant message identity is not signed on to the instant message service.
The instant message identity comprises an identity that is signed on to an instant message service and is associated with an idle state. Determining whether the destination is available to receive an electronic message using a first mode of communication may include determining whether the instant message identity is signed on to an instant message service, and determining whether the instant message identity is associated with an idle state if the instant message identity is determined to be signed on to the instant message service. A determination that the destination is not available may be made if the instant message identity is signed on to the instant message service and the instant message identity is associated with an idle state.
In yet another general aspect, a graphical user interface on a display device of a computer enables using a computer service to communicate. The graphical user interface includes a list of potential message recipients selected by a user as significant to the user. The graphical user interface also includes a user identifier associated with each potential message recipient and configured as a conduit for message delivery to the associated potential message recipient using the computer service. The graphical user interface also includes one or more forwarding indications that indicate whether a message addressed to a potential message recipient is to be forwarded to a mobile telephone number associated with the potential message recipient based on a determination that the mobile telephone number is known by the user to be associated with the potential message recipient.
Implementations may include one or more of the features noted above and one or more of the following features. For example, a forwarding indication may be displayed adjacent to the user identifier for the corresponding potential message recipient. A forwarding indication may include an icon.
A first type of forwarding indication may have a first presentation style that indicates that message forwarding to a mobile telephone number associated with a first potential message recipient associated with the first type of forwarding indication is enabled based on a determination that the mobile telephone number is known by the user to be associated with the potential message recipient. The graphical user interface may include one or more forwarding indications of a second type. A forwarding indication of the second type may have a second presentation style that indicates that message forwarding to a mobile telephone number associated with a second potential message recipient associated with the second type of forwarding indication is enabled such that message forwarding is enabled by the second potential message recipient.
The graphical user interface may include a control for sending a message to at least one of the potential message recipients. The list of potential message recipients may be an electronic address book or a contact list for the computer service. The computer service may include an instant messaging service, and the list of potential message recipients may be a buddy list. The user identifier may be an address for communication inspired through interaction with the graphical user interface.
The graphical user interface may include a mobile blocking indicator that indicates that message forwarding to a mobile telephone is prohibited by a potential message recipient. The graphical user interface may include a mobile forwarding indication that indicates that a mobile telephone associated with a potential message recipient is capable of receiving a text message.
The list of potential message recipients may include categories of potential message recipients such that a category is associated with one or more potential message recipients. A first category may be associated with one or more potential message recipients that are each associated with a forwarding indication, and a second category may be associated with one or more potential message recipients that are not associated with the first category.
Implementations of the techniques discussed above may include a method or process, a system or apparatus, or computer software on a computer-accessible medium. The details of one or more of the implementations are set forth in the accompanying drawings and description below. Other features will be apparent from the description and drawings, and from the claims.
Like reference symbols in the various drawings indicate like elements.
Techniques are described for forwarding an instant message addressed to an intended instant messaging recipient to the recipient's mobile telephone when the recipient's mobile telephone number is known to the instant message sender. In one example, an instant message is forwarded to the intended recipient's mobile telephone number when the instant message sender's contact information for the intended recipient includes an instant message address (e.g., a screen name or other type of instant message identifier) and a mobile telephone number, without dependence upon the intended recipient's presence on the instant message (IM) system or through actual login or registration with an IM forwarding service. In a more particular example, an address book of the instant message sender includes an entry for the intended recipient where the entry includes an instant message address and a mobile telephone number of the intended recipient.
More generally, an instant messaging user may maintain a list (a “buddy list”) of user-selected potential instant messaging recipients (“buddies”) to identify another instant messaging user with whom instant messages are to be exchanged. More specifically, with reference to one exemplary implementation, a buddy list is a user-definable list of other co-users (i.e., buddies) of an online or network communications systems that enables the user to perceive presence information and changes for the co-users in a unique graphical user interface (GUI) and to track changes to presence status for the co-users in substantially real-time automatically, where presence indicates the status of the co-user with respect to the online or network communications system. The buddy list also provides the user with a mechanism to initiate communications (e.g., instant messages electronic mail (e-mail), chat, and other communications) with the co-users. When a user signed on to a system, the set of buddies included in the user's buddy list is presented to the communications system. The communications system attempts to match co-users currently signed on to the system with the entries on the user's buddy list. Any matches are displayed to the user. As co-users sign on or sign off, a user's buddy list is updated to reflect these changes. An indication also may be added to show that a co-user has recently or is currently in the process of signing on or signing off the system. In some implementations, a user identity (e.g., a user account) may have one or more buddy lists of co-users, either with intersecting or disjoint lists of users, and the user label these buddy lists according to the user's preferences or otherwise.
Each of the client systems 105A and 105B may be implemented using, for example, a general-purpose computer capable of responding to and executing instructions in a defined manner, a personal computer, a special-purpose computer, a workstation, a server, a device, a component, or other equipment or some combination thereof capable of responding to and executing instructions. The client systems 105A and 105B may receive instructions from, for example, a software application, a program, a piece of code, a device, a computer, a computer system, or a combination thereof, which independently or collectively direct operations, as described herein. These instructions may take the form of one or more communications programs that facilitate communications between the users of client systems 105A and 105B. For instance, such communications programs may include e-mail programs, instant message programs, file transfer protocol (FTP) programs, and voice over internet protocol (VoIP) programs. The instructions may be embodied permanently or temporarily in any type of machine, component, equipment, storage medium, or propagated signal that is capable of being delivered to the client systems 105A and 105B.
The client systems 105A and 105B include a communications interface (not shown) used by the communications programs to send communications through network 115. The communications may include e-mail, audio data, video data, general binary data, or text data (e.g., encoded in American Standard Code for Information Interchange (ASCII) format). Client systems also include one or more input devices, such as a keyboard, a mouse, a stylus, or a microphone, as well as one or more output devices, such as a monitor, a touch screen, speakers, or a printer.
The network 115 typically includes a series of portals interconnected through a coherent system. Examples of the network 1020 include the Internet, Wide Area Networks (WANs), Local Area Networks (LANs), analog or digital wired and wireless telephone networks (e.g., a Public Switched Telephone Network (PSTN), an Integrated Services Digital Network (ISDN), or a Digital Subscriber Line of various types (DSL)), or any other wired or wireless network. The network 115 may include multiple networks or subnetworks, each of which may include, for example, a wired or wireless data pathway.
As with the client systems 105A and 105B, the instant message provider system 110 may be implemented using, for example, a general-purpose computer capable of responding to and executing instructions in a defined manner, a special-purpose computer, a workstation, a server, a device, a component, or other equipment or some combination thereof capable of responding to and executing instructions. The instant message provider system 110 may receive instructions from, for example, a software application, a program, a piece of code, a device, a computer, a computer system, or a combination thereof, which independently or collectively direct operations, as described herein. These instructions may take the form of one or more communications programs. Such communications programs may include, for example, e-mail programs, instant message programs, FTP programs, and VoIP programs. The instructions may be embodied permanently or temporarily in any type of machine, component, equipment, storage medium, or propagated signal that is capable of being delivered to the instant message provider system 110.
Further, the instant message provider system 110 includes a communications interface (not shown) used by the communications programs to send communications through network 115. The communications may include e-mail, audio data, video data, general binary data, or text data (e.g., encoded in American Standard Code for Information Interchange (ASCII) format).
The instant message applications 107A and 107B include buddy lists that include communications identities (“buddies”) with which instant messages are exchanged using the respective client systems 105A and 105B. More particularly, the instant message applications 107A and 107B include a buddy list for each user that uses the client systems 105A and 105B to send and receive instant messages. The instant message applications 107A and 107B enable the users to send and receive instant messages with the client systems 105A and 105B. Instant messages are sent between users of the client systems 105A and 105B through a desktop instant message server 130 on the instant message provider system 110.
The provider system 110 includes a desktop instant messaging server 130 that operates instant messaging server software configured to process communications sent from and received by users of an instant messaging service. In particular, the desktop instant messaging server 130 is configured to exchange instant messages and communications related to the instant message service between the client systems 105A and 105B and the provider system 110 over the network 115. The desktop instant message server 130 initiates a point-to-point recipient, and/or it may be sent to route instant messages sent with the instant message applications 107A and 107B.
The desktop instant messaging server 110 also includes address books 135 that are associated with instant messaging user accounts (e.g., a screen name or other type of instant message identity identifier). More particularly, an address book is associated with a particular instant message identity (e.g., a sender) and includes contact information 135A for people that are significant to the instant message identity. The people listed in the contact information may be referred to as contacts. Each contact information entry in the address book may identify a screen name 135B (or other type of instant message address or identity identifier) and a mobile telephone number 135C for a contact of the instant message identity to whom the address book applies (e.g., sender). In some implementations, the address book may include additional information, such as a name, mailing address information, and other types of telephone numbers. Some implementations may refer to an address book by other terms, such as contact information or user information.
The desktop instant messaging server 110 also includes buddy lists 136 for instant messaging user accounts. Particular buddy lists may be used by instant messaging application 107A or 107B that are associated with an instant messaging user using the client system 105A or 105B, respectively.
The desktop instant messaging server 130 also includes code segments 137 to enable a user to manage contact information 135A in the user's address book, such as by adding information for a new contact, deleting a contact, or editing information related to a contact. The code segments 137 enable a user to identify a mobile telephone and an instant messaging identity identifier or account (e.g., screen name) for a contact.
An offline mobile proxy 140 represents the online presence and/or availability of a user of the instant messaging system when the user is offline, thus enabling communications to offline users via alternative communication schemes (e.g., text messaging to a text-capable telephone), even if an instant messaging service is configured to restrict messaging to users who reflect online presence. The offline mobile proxy 140 represents to the desktop instant messaging server 130 that a user is capable of receiving an instant message when a user is actually offline. Accordingly, when a user is offline, availability of the user to communicate may be perceived by others and messages sent to them may be received using an alternative communications scheme (e.g., text messaging to a text-capable telephone). For instance, a user who is not signed on to the instant message service (i.e., an offline user) and whose mobile telephone number is included in a potential sender's address book may be perceived as available to receive messages by the potential sender—that is, the user who is offline remains listed as available for messaging on the buddy lists of users who subscribe to the user's online presence and have contact information for the user that includes the user's mobile telephone number and screen name. Moreover, an instant message intended for such an offline user is received by the desktop instant messaging server 130 and provided to the wireless server 145, which communicates a text message based on the original instant message to the mobile telephone device 170 associated with the offline user. The text message is communicated from the wireless server 145 to the mobile telephone device 170 thorough the cellular system 180. The communication of an instant message addressed to an instant message screen name to a mobile telephone as a text message may be referred to as sender-initiated mobile forwarding. Such sender-initiated mobile forwarding may be distinguished from recipient-initiated mobile forwarding in which a recipient configures, or otherwise enables, the recipient's own instant messaging account to forward an instant message as a text message to the recipient's mobile telephone. Sender-initiated mobile forwarding also may be referred to as sender-inspired mobile forwarding. Recipient-initiated also may be referred to as recipient-inspired mobile forwarding.
The offline mobile proxy 140 includes code segments 140A to manage online presence information. When the desktop instant messaging server 130 detects that a user has signed off the instant messaging service, the desktop instant messaging server 130 communicates the status of the user (e.g., offline) to the offline mobile proxy 140, which executes code segment 140A to indicate to the desktop instant messaging server 130 that the user is online. This enables a user to be perceived by the desktop instant messaging server 130 as online when the user is offline (e.g., not signed in to the instant messaging service). In one implementation, the offline mobile proxy 140 also executes code segment 140A to update, or enable the update of, the screen name associated with a user to show a mobile indicator adjacent to the user's screen name on each of the buddy lists that include the user's screen name. The mobile indicator indicates that the user is available at their mobile device to receive messages inspired through manipulation of the buddy list in the ordinary manner, indicates that the user is not signed on to the desktop instant messaging service, and also indicates that the user has invoked recipient-initiated mobile forwarding, as described more fully in
The offline mobile proxy 140 also includes code segments 140B that may be executed by the offline mobile proxy 140 to determine whether to forward an instant message addressed to an offline intended recipient to the mobile telephone device 170 associated with the intended recipient of the original instant message. In one example, the offline mobile proxy 140 executing the code segments 140B may determine to forward an instant message when a sender of the instant message knows the potential recipient's mobile telephone number (i.e., the offline mobile proxy 140 directly, or thorough the desktop instant messaging server 130, determines there is an entry in address books 135 for contact information 135A that includes a mobile telephone number associated with the potential recipient's screen name. This may be referred to as determining whether to forward an instant message based on contact information. In another example, the offline mobile proxy 140 may determine to forward the instant message based on contact information and other factors. For example, the offline mobile proxy 140 may determine whether to forward an instant message to a mobile telephone number based on a user state (e.g., only when a user is offline), based on a sender request (e.g., confirmation that the sender wants to send a message to the mobile telephone), or unconditionally (e.g., mirror all instant messages to the mobile telephone even when the user is signed on to the instant message service). Accordingly, the offline mobile proxy 140 executing the code segments 140B may determine to forward the instant message only when the user is offline or it instead may determine to forward the instant message only when the sender has indicated that the instant message should be forwarded. In yet another example, the offline mobile proxy 140 executing the code segments 140B may determine to forward the instant message when the sender has a mobile telephone number for the potential recipient and the potential recipient has not prohibited forwarding of instant messages to the potential recipient's mobile telephone. In any event, when the offline mobile proxy 140 determines that an instant message is to be forwarded to a mobile device, the offline mobile proxy 140 provides the instant message to the wireless server 145.
The wireless server 145 includes code segments 145A configured to prepare, based on an original instant message, a text message that is based on the short message service (SMS) protocol, which is particularly useful in sending and receiving short text messages to mobile devices, such as mobile telephones. The code segments 145A include addressing operations. In one example, the wireless server 145 executing code segments 145A may use contact information 135A in address books 135 to identify the mobile telephone number of the recipient identified in the instant message. To do so, the wireless server 145 executing code segments 145A may identify a contact entry in the address book of the sender of the instant message where the contact entry includes the screen name to whom the instant message is addressed and a mobile telephone number. The addressing operations also may include addressing the text message to the identified mobile telephone number. The addressing operations also may include converting the instant message to a different character set that is used by the text message. For example, an instant message may use an ASCII character set or a Unicode character set, whereas the text message may use a GSM (“Global System for Mobile Communications”) character set. In such a case, the wireless server 145 executing code segments 145A also converts the instant message from the ASCII or Unicode character set to the GSM character set.
In addition, the wireless server 145 also includes code segments 145B configured to forward a text message to a telephone number. More particularly, the wireless server 145 executing code segments 145B forwards to the cellular system 180 a text message prepared by executing code segments 145A. This may be referred to as mobile forwarding. If mobile forwarding is inspired by the sender's contact information for the intended recipient, the mobile forwarding may be referred to as sender-initiated mobile forwarding. Similarly, if mobile forwarding is performed based on action by the recipient, then the mobile forwarding may be referred to as recipient-initiated mobile forwarding.
The mobile telephone device 170 is associated with a mobile telephone number to which telephone calls may be routed over the cellular system 180. The mobile telephone device 170 also may be associated with a SMS address that typically is the same as the mobile telephone number associated with the mobile telephone device 170, though this need not necessarily be so. The mobile telephone device 170 is capable of receiving, displaying, processing, and sending text messages over the cellular system 180. The mobile telephone device 170 also may be referred to as a text-capable telephone.
The cellular system 180 may include a cellular network that is capable of transmitting and receiving digital or analog signals using cellular technologies, including Advanced Mobile Telephone System (AMPS), Narrowband Advanced Mobile Telephone Service (NAMPS), Frequency Shift Keying (FSK), Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), and Code Division Multiple Access (CDMA), or any standard, such as Global System for Mobile Communications (GSM) or Cellular Digital Packet Data (CDPD). Alternatively, the cellular system 180 may be any type of telephone network capable of transmitting text messages to any type of telephone or mobile device.
In general, the communications system 100 may be used to send an instant message sent from a client system 105A or 105B to the instant message provider system 110, which transforms the instant message to a corresponding text message that is routed over the cellular system 180 to the mobile telephone device 170. The original instant message is addressed to a screen name and forwarded to the mobile telephone device 170 based on the sender's contact information for the intended recipient—that is, based on an association, in the sender's contact information 135A of address books 135, of the screen name and the mobile telephone number of the intended recipient, and detection of offline status of the screen name identity (i.e., the user of the mobile telephone device 170).
In some implementations, forwarding an instant message to a mobile telephone may be prohibited by the user of the mobile telephone, even when the sender of the instant message knows the mobile telephone number of the intended recipient of the instant message (e.g., contact information in the sender's address book includes a mobile telephone number associated with the screen name of the intended recipient). Additionally or alternatively, forwarding of an instant message to a mobile telephone may be performed only after confirmation is received from the sender of the instant message.
In some implementations, the client system 105A or 105B may be capable of performing some or all of the operations described as being performed by the instant message provider system 110.
Sender-initiated mobile forwarding may reduce burden on sender's of instant messages to alleviate, or minimize, effort of monitoring recipient availability to receive an instant message. It may be possible to monitor recipient availability to receive, on the recipient's mobile telephone, a communication based on an instant message. For example, in some implementations, sender-initiated mobile forwarding may only occur when the intended recipient's mobile telephone is activated, within signal range, and able to receive a text message, though this need not necessarily be so. Text messaging to a mobile telephone may be implemented using store-and-forward techniques such that a text message that is sent to a deactivated (e.g., turned off) mobile telephone is delivered to the mobile telephone when the mobile telephone is activated (e.g., turned on) or becomes within receiving range of a mobile signal. In such a case, the recipient having mobile telephone may be identified as always being available to receive a text message.
In some implementations, a buddy list of potential instant messaging recipients may reflect whether one or more potential instant messaging recipients are available to receive a message forwarded to the potential recipient's mobile telephone. For example, when a potential recipient's mobile telephone is turned off, not within signal range, or is otherwise unable to receive a text message, the buddy list including the instant messaging recipient may reflect the potential recipient's unavailability to receive a message forwarded to the potential recipient's mobile telephone. A buddy list that indicates whether a potential recipient is available to receive a message forwarded to the potential recipient's mobile telephone may be applicable to sender-initiated mobile forwarding and may be applicable to recipient-controlled mobile forwarding.
The process 200 begins when a user creates an instant message addressed to a screen name, and the instant message is received by the instant messaging system (step 210). The user, who may be referred to as a sender, may do so using an instant messaging application to identify a buddy from within their buddy list and enter text or other content for the instant message. Accordingly, the instant message is addressed to a screen name of an identity listed on the sender's buddy list. Alternatively, the screen name of the intended recipient of the instant message may be a identified by the user by entering a screen name (rather than selecting a buddy from the sender's buddy list).
The instant messaging system determines whether an identity associated with the screen name is available to receive an instant message (step 220). This may be accomplished, for example, by the instant messaging system checking whether the identity associated with the screen name is signed on to the instant message system. When the identity associated with the screen name is available to receive an instant message (step 222), the instant messaging system sends the instant message to the identity associated with the screen name (step 225). For example, the instant message system may forward the instant message to the client system, such as 105A or 105B of
When the identity associated with the screen name is not available to receive an instant message (step 222), the instant messaging system determines whether a mobile telephone number is known by the sender to be associated with the identity associated with the screen name. In one example, the instant messaging system identifies a collection of contact information (i.e., an address book, a contact list, or a buddy list) that is associated with the sender of the instant message and searches the identified collection for an entry that includes a screen name that matches the screen name to which the instant message is addressed. If such a match found, the instant messaging system determines whether a mobile telephone number is included in the contact information entry, and, when so, the instant messaging system determines that a mobile telephone number is known to the sender to be associated with the identity associated with the screen name to which the instant message is addressed.
When the instant message system determines that a mobile telephone number is not known by the sender to be associated with the identity associated with the screen name (e.g., contact information for the identity is not included in the sender's address book or contact information for the identity is included in the sender's address book and the contact information does not include a mobile telephone number) (step 232), the instant message system does not send the instant message to the intended recipient and does not send a communication based on the instant message (e.g., does not forward a text message to a mobile telephone number) (step 235).
When the instant message system determines that a mobile telephone number is known by the sender to be associated with the identity associated with the screen name (e.g., contact information for the identity is included in the sender's address book, where the contact information includes a mobile telephone number and identifies a screen name) (step 232), the instant message system sends a communication based on the instant message to the mobile telephone number known to the sender to be associated with the identity (step 240). This may be accomplished, for example, by preparing and forwarding a text message based on the instant message to the mobile telephone number for the identity, directly or indirectly, thorough a cellular system, as described previously with respect to
In some implementations, the determination as to whether a identity is available may include, when the identity is signed on to the instant message system, making a determination that the identity is available only when the identity is not idle (e.g., the identity has not interacted with the client system running the instant message application program in a predetermined or user-configurable amount of time). In such a case, a communication based on the instant message may be sent to a mobile telephone number known to the sender to be associated with the identity when the identity is not signed on and/or is idle. Alternatively or additionally, an instant message account or instant message application may be configured to identify conditions when sender-initiated mobile forwarding occurs—such as, only when a recipient is not signed on to the instant message application, or when a recipient is not signed on to the instant message application or is idle.
Referring to
The graphical user interface 300 includes an instant message sender-selected list 310 of potential instant messaging recipients 320a-320g. The graphical user interface 300 may be referred to as an instant message buddy list window 300, an instant message buddy list interface 300, or, more simply, a buddy list window 300 or a buddy list interface 300, and the list 310 may be referred to as a buddy list 310. In some implementations, the buddy list also may be referred to as a participant list, a contact list or a friends list. Thus, buddies typically are contacts who are known to the potential instant message sender (here, IMSender). A buddy is identified by a screen name or other type of identity identifier, such as an account name, a user name, a user identity, or an alias of an identity identifier. In particular, the user IMSender is an instant message sender using the buddy list interface 300. The buddy list interface 300 is rendered on the display of a computing device or a communication device on which an instant messaging client program is executed, such as the client system 105A or 105B of
In the buddy list 310, the representations 320a-320g include text identifying the screen names of the buddies included in buddy list 310; however, additional or alternative information may be used to represent, and be associated with, one or more of the buddies, such as an avatar or other type of graphical image, that is reduced in size and either still or animated. In one example, a buddy icon is a small, two-dimensional graphical image that may be used for self-expression by the associated buddy (e.g., used to express an interest of the buddy), and which may be a still or animated image or graphic. For example, the representation 320a includes the screen name 321a and corresponding buddy icon 322a of the instant message recipient named SuperBuddyFan1. The buddy icon typically selected by the party identified by the screen name, but it may be selected instead by the buddy list owner. For convenience, each of the representations 320a-320g may be referred to as a screen name 320a-320g. In some implementations, one or more of the representations 320a-320g may be an alias of a screen name rather than a screen name itself. The representations 320a-320g may provide connectivity information to the instant message sender about the buddy, such as whether the buddy is online, how long the buddy has been online, whether the buddy is away from the client system executing the instant messaging client application, or whether the buddy is available through a mobile device.
Buddies may be grouped by an instant message sender into one or more user-defined or pre-selected groupings (“groups”). As shown, the instant message buddy list window 300 has three groups, Buddies 322, Co-Workers 324, and Family 326. SuperBuddyFan1320a belongs to the Buddies group 322, and ChattingChuck 320c belongs to the Co-Workers group 324. When a buddy's instant message client program is able to receive communications, the representation of the buddy in the buddy list is displayed under the name or representation of the buddy group to which the buddy belongs. As shown, at least potential instant messaging recipients 320a-320g are online. In contrast, when a buddy's instant message client program is not able to receive communications, the representation of the buddy in the buddy list may not be displayed under the group with which it is associated, but it may instead be displayed with representations of buddies from other groups under the heading Offline 328, or it may otherwise be visually distinguished from other buddies who then have available/present instant message client programs. All buddies included in the buddy list 310 that are displayed in the messaging mode are displayed either under one of the groups 322, 324, or 326, or under the heading Offline 328.
The buddy list 310 also includes a mobile indicator 310A that reflects the existence of a mobile telephone number for the identity is known to the user (i.e., IMSender) and, as such, is a means for contacting the identity associated with the screen name 320b (i.e., Boss) adjacent to the mobile indicator 310A. Thus, the mobile indicator 310A may indicate that a message addressed to the screen name 320b is to be forwarded to a mobile telephone number associated with the screen name 320b based on an association of a mobile telephone number with the screen name 320b in the user's (i.e., IMSender) contact information. The mobile indicator 310A also may be referred to as a sender-initiated forwarding indicator. Generally, the mobile indicator 310A is displayed only when the identity associated with the screen name 320b is not available to receive an instant message (e.g., is offline and/or is idle), though this need not necessarily be so. In some implementations, the mobile indicator 310A may indicate only that a mobile telephone number is associated with the screen name and not provide an indication as to whether an instant message sent to the corresponding screen name is to be forwarded to the mobile telephone number.
The buddy list 310 also includes a mobile indicator 310B that reflects that the identity associated with the screen name 320e (i.e., Mom) adjacent to the mobile indicator 310B has enabled recipient-initiated mobile forwarding of instant messages to the identity's mobile telephone. In contrast to the sender-initiated forwarding indicator 310A, the mobile telephone number of the identity need not necessarily be known to the user (i.e., IMSender). Mobile indicator 310B may be referred to as a recipient-initiated forwarding indicator. Generally, the mobile indicator 310B is displayed only when the identity associated with the screen name 320e is not available to receive an instant message (e.g., is offline and/or is idle), though this need not necessarily be so. Although the recipient-initiated forwarding indicator 310B is shown with a different presentation style from the presentation style of the sender-initiated forwarding indicator 310A, some implementations may use the same presentation style for both types of mobile indicators.
A mobile blocking indicator 310C on the buddy list 310 reflects that the identity associated with the screen name 320g (i.e., Brother) prohibits forwarding of instant messages to the identity's mobile telephone, even though the mobile telephone number associated with the identity may be known to the user. Generally, though not necessarily, the mobile blocking indicator 310C is displayed only when the identity associated with the screen name 320g is not available to receive an instant message (e.g., is offline and/or is idle). Alternatively, in contrast to displaying a mobile indicator 310C, some implementations may simply use the presence of a user's screen name to indicate their availability (by mobile forwarding or otherwise) to receive messages, and the absence of mobile indicators 310A and 310B to indicate an otherwise potential recipient's lack of availability due to either of an absence of their mobile forwarding information/registration or their expressed reluctance to receive messages at their mobile device. For example, some implementations may not display a mobile indicator 310A adjacent to a screen name when the sender has the mobile telephone number for the identity, the identity is offline, and the identity prohibits mobile forwarding. In such a case, for example, the screen name of the user may simply appear under the Offline group 328, even though the sender has their mobile forwarding information.
The mobile blocking indicator 310C may be particularly useful when applied to the Offline group 328. In such a case, the mobile blocking indicator 310C would inform sender the identities who are available to receive instant messages sent as text messages to the identities' mobile telephone. For example, when a potential recipient's mobile telephone is turned off, not within signal range, or is otherwise unable to receive a text message, the buddy list may include a mobile blocking indicator 310C to reflect the potential recipient's unavailability to receive a message forwarded to the potential recipient's mobile telephone.
A determination to display the mobile blocking indicator 310C may be made when a determination is made that the identity associated with the screen name 320g (i.e., Brother) is offline and/or is idle. For example, when the identity signs off of the host system providing the instant messaging service, the host system may determine whether the identity prohibits forwarding of instant messages to the identity's mobile telephone. To do so, for example, the host system may check configuration information associated with the screen name 320g and make a determination based on the configuration information. When the host system determines that forwarding of instant messages is prohibited by the identity, the host system may make that determination available to the client system or may make available an updated buddy list that includes the mobile blocking indicator 310C. This may be accomplished, for example, by sending the updated buddy list, sending a message that indicates the identity associated with the screen name prohibits forwarding of instant messages, or otherwise pushing the buddy list or determination to the client system that displays the buddy list 310. In another example, the host system enables the client system to access the updated buddy list with the mobile blocking indicator 310C, the determination that a mobile blocking indicator 310C is appropriate, or otherwise enabling the client system to pull the updated buddy list or determination that a mobile block indicator 310C is appropriate from the host system. The buddy list window 300 also includes controls 330 that a user may use to initiate functions related to instant messaging. In particular, a setup control 332 allows for configuration of the currently displayed buddy list. Selecting the setup control 332 enables functionality including the addition and deletion of screen names, such as screen names 320a and 320b, and groups, such as groups 322 and 324, to the buddy list 310.
When an online screen name from the buddy list 310 has been selected, activating an instant messaging control 334 displays an interface for communicating with the account corresponding to the selected screen name. Activating the instant messaging control 334 without selecting an online screen name in the buddy list 310 causes the display of an interface for communicating and allows a user to identify a instant messaging user that is not on the user's buddy list.
An info control 336 displays contact information related to a screen name selected on the buddy list 310 when contact information is available about the buddy. Such information may include, for example, a mobile telephone number, a work telephone number, and a home telephone number. In some implementations, information other than contact information may be displayed, such as, for example, name, geographic location, interests and hobbies, and occupation of the buddy. The contact information may be entered by identity (i.e., buddy) and, optionally, the identity may control whether some or all such information is displayed to other users. Additionally or alternatively, the contact information for the buddy may be entered by the user (i.e., IMSender). The contact information may be displayed, for example, in a user interface 400 of
The interface 400 identifies the screen name 410 of an identity (i.e., “Steve Clark”) with whom telephone numbers 420 are to be associated. The interface 400 enables a user to enter a mobile telephone number 425 to be associated with the screen name 410, which serves to inform the instant messaging service that the mobile telephone number associated with the screen name 410 is known to the user.
The interface 400 also includes controls. A control 432 is operable to associate the entered mobile telephone number 425 with the identified screen name 410 and remove the interface 400 from display on a computing device or communication device operating the instant messaging application. In contrast, a control 434 is operable to remove the interface 400 from display without associating the entered mobile telephone number 425 with the identified screen name 410.
In some implementations, an instant messaging user may enter the user's own mobile telephone number in the interface 400 and, in doing so, make known the user's own mobile telephone number to other instant messaging users. Thus, in doing so, the user enables instant messages sent to the user from other instant messaging users to be forwarded to the user's mobile telephone number when the user is offline. This may be a convenient method for a user to enable mobile forwarding to the user's mobile telephone.
This or a similar interface may be used to display a mobile telephone number that is associated with a screen name and, hence, known to the user displaying the interface. For example, with reference to
In contrast to the interface 400 of
As illustrated, the address card information 505 also includes other types of information, such as the name of the contact 530, a category 532 of contacts with whom the contact is associated (i.e., a Friends category), and an e-mail account identifier 535 of e-mail account other than an e-mail account associated with the screen name 510.
The interface 500 also includes a control 542 to save address card information in electronic storage, such as address books 135 of
In some implementations, the interface 500 also may include a control 550 operable to expressly prohibit sender-initiated mobile forwarding to the cellular phone number 525 associated with the screen name 510 (e.g., prohibit forwarding an instant message sent to the screen name 510 to the cellular phone number 525 when the identity associated with the screen name is not signed on to the instant messaging service) and an indicator 552 representing whether sender-initiated mobile forwarding to the cellular phone number 525 is prohibited. The ability for a user to control whether sender-initiated mobile forwarding is prohibited for a particular contact in the user's address book may be useful. For example, a user may store in the user's address book a cellular phone number for a contact for whom the user would not want to forward an instant message when the contact is offline. In one example, a user may wish to store a cellular phone number 525 for a contact where the contact owns a cellular phone corresponding to cellular phone number for emergency use only and customarily does not power on cellular phone. In such a case, the user may wish to prohibit sender-initiated mobile forwarding to the cellular phone. In some implementations, the control 550 may be operable to expressly prohibit both sender-initiated and recipient-initiated mobile forwarding (if the contact has configured the contact's instant message user account to enable recipient-initiated mobile forwarding).
In some implementations, other sender-configuration options may be provided. For example, a user may be able to select whether sender-initiated mobile forwarding based on contact information is enabled (or prohibited) for all contacts or contacts belonging to one or more contact categories. Similarly, a user may be able to select whether sender-initiated mobile forwarding based on contact information is enabled (or prohibited) as a default option for all contacts, or contacts belonging to one or more contact categories, unless overridden by user instruction. One example of such a user instruction is the control 550 operable to prohibit sender-initiated mobile forwarding to the mobile telephone number of the identified contact. Another example is the response of a user to a prompt inquiring whether the user wants to forward a particular instant message to a recipient, as described more fully later with respect to
Additionally or alternatively, recipient-configuration options may be provided for enabling a recipient to control whether an instant message is forwarded to the recipient's mobile telephone. For example, a user may configure the user's instant messaging account such that instant messages are not forwarded to the user's mobile telephone even when a sender has the user's mobile telephone number in the sender's contact information. More particularly, a user who is an intended recipient of an instant message may prohibit sender-initiated mobile forwarding from any sender, a particular sender and/or a sender that is associated with one of one or more buddy groups on the recipient's buddy list.
The interface 600A includes a message compose text box 606 that enables text to be entered for a message and displays the text of a message to be sent from the sender and to the identified recipient 602. Once specified in the message compose text box 606, the message may be sent by selecting a send button 610. In some implementations, the interface 600A may include a message transcript text box (not shown) that displays the text of messages sent between the sender and the recipient.
The interface 600A includes an available control 620 operable to display a user interface indicating whether the potential recipient is available to receive an instant message and, if not, to prompt the user to indicate whether the instant message is to be forwarded to the mobile phone number associated with the screen name (when a mobile telephone number is available for the screen name), such as user interface 600B of
More particularly, the interface 600B displays availability information 625 for the intended recipient. As illustrated, the availability information 625 indicates that the intended recipient is offline. Another example of availability information 625 is information that the intended recipient is idle (e.g., has not interacted with the client system running the instant message application program in a predetermined or user-configurable amount of time). Yet another example of availability information 625 is information that the intended recipient is away from the client system running the instant message application program (e.g., that the intended recipient has set an away indicator to be displayed when an instant message is sent to the intended recipient). Availability information 625 also may provide notification that the intended recipient is offline and has enabled recipient-initiated mobile forwarding where a text message based on the instant message is to be sent to a mobile telephone number identified by the intended recipient.
The interface 600B also includes a prompt 630 for the user to indicate whether the instant message sender wishes to forward the instant message to the intended recipient's mobile telephone number. The prompt 630 may be displayed based on the association, in the instant message sender's collection of contact information (e.g., address book), of a mobile telephone number with the screen name of the intended recipient. In some implementations, the prompt 630 also may be displayed when intended recipient is offline and has enabled recipient-initiated mobile forwarding to receive a text message on the intended recipient's mobile telephone number.
A control 635 is operable to enable mobile forwarding of a text message to a mobile telephone number associated with the intended recipient and remove the interface 600B from display. In contrast, a control 637 is operable to remove the interface 600B without sending to a mobile telephone number associated with the intended recipient a text message based on the instant message.
More particularly, the interface 600C includes a text box 650 informing the sender that the instant message is to be sent to the mobile device registered to the intended recipient and identifying the mobile telephone number to which the message is to be sent. The interface 600C also includes controls 662, 664, 666, 668 and 669 to identify the desired disposition of the message. In particular, the control 662 is operable to send the message content identified in the instant message via instant message only—that is, forwarding a text message to the mobile telephone number of the intended recipient and remove the interface 600C from the display. The control 662 is operable to send the message content identified in the instant message via instant message only—that is, forwarding a text message to the mobile telephone number of the intended recipient and remove the interface 600C from the display.
The control 664 is operable to send the message content identified in the instant message as an electronic mail (e-mail) message directed to an e-mail address associated with the intended recipient in the sender's contact information for the recipient, such as other e-mail address 535 of
Similarly, the control 666 is operable to send the message content both as a text message forwarded to a mobile telephone number of the recipient and as an e-mail message directed to the intended recipient, as well as to remove the interface 600C from the display.
The control 668 is operable to initiate a telephone call (e.g., a voice-based telephone call) to the mobile telephone number of the intended recipient and remove the interface 600C from the display.
The control 669 is operable to remove the interface 600C from the display without sending the instant message.
Like the interface 600C of
Referring to
The user interface 700 also includes a set of option buttons 740 that may be selected by the user to configure user's instant messaging account to react to requests by a sender to forward messages to the mobile telephone number 730 based on the user's mobile telephone number in the sender's contact information for the user. The option buttons 740 may include, for example, an option button 741 to prohibit sender-initiated mobile forwarding (e.g., messages are not to be forwarded to the mobile telephone number when the user is not signed on to the instant messaging system), an option button 742 to enable sender-initiated mobile forwarding only when the user is offline, and an option button 743 to enable sender-initiated mobile forwarding when the user is offline or when the user is signed on and away (e.g., the user is signed on to the instant messaging account and an away message is enabled for the account to provide an indication to potential message senders that the user is not available to receive a message).
The user interface 700 allows sender-initiated mobile forwarding of instant messages to a user's mobile telephone number to be controlled according to recipient preferences. Thus, when a user configures the user's instant message account to prohibit sender-initiated mobile forwarding, the host system does not send a communication to the user's mobile telephone number even when the sender has the user's mobile telephone number and the user is not available. In some implementations, the user's mobile telephone number 730 is informational only such, when option 741 is selected to prohibit mobile forwarding, that the absence of the user's mobile telephone number 730 enables sender-initiated mobile forwarding only when the user is offline.
In some implementations, the interface 700 also may include an indication as to the configuration of the user's account—e.g., whether sender-initiated mobile forwarding is prohibited, is enabled only when the user is offline, or is enabled when the user is offline or away.
The process 800 begins when a user identifies contact information for one or more instant message users, which is received by the instant messaging system (step 810). The user, who may be referred to as a sender, may do so using the interface 500 of
The instant messaging system presents a buddy list with a group of buddies that identifies available buddies and a group of buddies that identifies mobile buddies who are not available but for whom a mobile telephone number is known by the sender (e.g., the mobile telephone number has been entered in the sender's address book) (step 820). This may be accomplished, for example, by the instant messaging system checking whether an identity associated with each screen name on the buddy list is signed on to the instant message system and whether a mobile telephone number is known to the sender for each identity. When the identity is signed on, the identity is grouped in the available group, whereas when the identity is not signed on but a mobile telephone number is known to the sender, the identity is associated with the mobile buddies group. In some implementations, the buddy list may also present a group of buddies that are offline and for whom a mobile telephone number is not known by the sender.
In some implementations, a user may have the option of configuring a buddy list to include a buddy group that includes identities who are able to receive instant messages forwarded to a mobile device. Such a group may be referred to as a mobile buddy group or mobile buddies. For example, a user may be able to set a preference for including an identity who is able to receive instant messages forwarded to a mobile device in a mobile buddy group, or, conversely, maintaining such an identity's integration within other known buddy groups. In another example, a user may be able to configure a buddy list to include such an identity both in a mobile buddy group and another buddy group. The instant messaging system receives, from the sender, a selection of a mobile buddy to whom an instant message is to be sent (step 830). For example, the sender may select a buddy from the buddy as described previously with respect to
The instant message system received, from the sender, message content of an instant message to be sent to the identified mobile buddy (step 840). For example, the sender may identify text in the message compose text box 606 of
The instant message system sends a communication based on the instant message to the mobile telephone number known to the sender to be associated with the identity (step 850). This may be accomplished, for example, by preparing and forwarding a text message based on the instant message to the mobile telephone number for the identity, directly or indirectly, thorough a cellular system, as described previously with respect to
The techniques described related to mobile forwarding based on contact information may provide a convenient method to automatically provide mobile forwarding without requiring the text message recipient to set up or otherwise configure the recipient's instant message account to enable such mobile forwarding. This may be useful, particularly when a user may be reluctant to so enable the user's account, perhaps, on the assumption that such a configuration process is or may be complex or confusing (regardless of whether such a configuration process is complex or confusing).
Although the techniques and concepts often are described above in terms of SMS text messaging, the techniques and concepts may be applied to other types of messages, such as a Multimedia Messaging Services (MMS) message, a video message and an audio message. Similarly, the techniques and concepts have been describe in terms of receiving an instant message is received at desktop computer receive instant messages addressed to the instant message identifier. Other electronic devices configured to receive instant messages may be used, such as a laptop computer, a personal data assistant (PDA) and a telephone receiver.
Instant messaging programs typically allow instant message senders to communicate in real-time with each other in a variety of ways. For example, many instant messaging programs allow instant message senders to send text as an instant message, to transfer files, and to communicate by voice. Examples of instant messaging communication applications include AIM (America Online Instant Messenger), AOL (America Online) Buddy List and Instant Messages which is an aspect of many client communication applications provided by AOL, Yahoo Messenger, MSN Messenger, and ICQ, among others. Although discussed above primarily with respect to instant message applications, other implementations are contemplated for providing similar functionality in platforms and online applications.
The techniques and concepts generally have been described in the context of an instant messaging system that uses an instant messaging host system to facilitate the instant messaging communication between instant message senders and instant message recipients. Other instant message implementations are contemplated, such as an instant message service in which instant messages are exchanged directly between two instant message client systems (e.g., an instant message sender system and an instant message recipient system).
In addition, although the examples above are given in an instant message context, other communications systems with similar attributes may be used. For example, some or all of the techniques may be applicable to messages exchanged in a chat room or in electronic mail (e-mail) communications. Also, some or all of the described user interfaces may be a viewable interface, an audible interface, a tactile interface, or a combination of these.
In addition, the techniques and concepts describing sender-initiated forwarding of an instant message to a mobile telephone based on recipient contact information known by the sender may be applied to other contexts. For example, an e-mail message may be sent to an e-mail address known by the sender that corresponds to the recipient identified in the instant message. In other examples, sender-initiated forwarding of messages may be enabled to a voice telephone message or a second instant message address provided by another instant message service. In some implementations, a hierarchy of communication schemes may be identified. For example, an instant message may be first forwarded as a text message to a mobile telephone number known to the sender and, when the recipient is not available to receive the message at the mobile telephone, the message may be also forwarded as an e-mail message to an e-mail address of the intended recipient that is known to the sender. A hierarchy of communication schemes may be automatically applied to select among available contact criteria for a recipient of an instant message. In some implementations, a user may set a preference for the order in which available contact criteria are applies. For example, a user may prefer that a text message be forwarded to a mobile telephone number (if known) before an e-mail message is sent to an e-mail address (if known). A user may set a default preference that is applied to all contacts, unless overridden by a preference identified for a particular contact. For example, in general, a user may indicate that an instant message is forwarded to a mobile telephone number before being sent as a e-mail message; however, for a particular contact, an instant message is forwarded as an e-mail message before being a text message is forwarded to the mobile telephone number of the particular contact.
The techniques and concepts describing a buddy list that separates various identities into groups based on availability and/or communication scheme also may be applied to identity a group of buddies that are available via sending an e-mail message (and are otherwise offline and/or away).
The described systems, methods, and techniques may be implemented in digital electronic circuitry, computer hardware, firmware, software, or in combinations of these elements. Apparatus embodying these techniques may include appropriate input and output devices, a computer processor, and a computer program product tangibly embodied in a machine-readable storage device for execution by a programmable processor. A process embodying these techniques may be performed by a programmable processor executing a program of instructions to perform desired functions by operating on input data and generating appropriate output. The techniques may be implemented in one or more computer programs that are executable on a programmable system including at least one programmable processor coupled to receive data and instructions from, and to transmit data and instructions to, a data storage system, at least one input device, and at least one output device. Each computer program may be implemented in a high-level procedural or object-oriented programming language, or in assembly or machine language if desired; and in any case, the language may be a compiled or interpreted language. Suitable processors include, by way of example, both general and special purpose microprocessors. Generally, a processor will receive instructions and data from a read-only memory and/or a random access memory. Storage devices suitable for tangibly embodying computer program instructions and data include all forms of non-volatile memory, including by way of example semiconductor memory devices, such as Erasable Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM), and flash memory devices; magnetic disks such as internal hard disks and removable disks; magneto-optical disks; and Compact Disc Read-Only Memory (CD-ROM). Any of the foregoing may be supplemented by, or incorporated in, specially-designed ASICs (application-specific integrated circuits).
It will be understood that various modifications may be made without departing from the spirit and scope of the claims. For example, advantageous results still could be achieved if steps of the disclosed techniques were performed in a different order and/or if components in the disclosed systems were combined in a different manner and/or replaced or supplemented by other components. As another example, a screen name is used throughout to represent a unique identifier of an account, but any other unique identifier of an account may be used when linking accounts. Accordingly, other implementations are within the scope of the following claims.
This application is a continuation of U.S. application Ser. No. 11/017,202 filed Dec. 21, 2004, which claims the benefit of U.S. Provisional Application No. 60/631,876 filed Dec. 1, 2004, and titled AUTOMATICALLY ENABLING THE FORWARDING OF INSTANT MESSAGES, which is incorporated by reference in its entirety.
| Number | Name | Date | Kind |
|---|---|---|---|
| 4837798 | Cohen | Jun 1989 | A |
| 5086394 | Shapira | Feb 1992 | A |
| 5135636 | Yee | Aug 1992 | A |
| 5276905 | Hurst et al. | Jan 1994 | A |
| 5327486 | Wolff et al. | Jul 1994 | A |
| 5548637 | Heller et al. | Aug 1996 | A |
| 5608786 | Gordon | Mar 1997 | A |
| 5673308 | Akhavan | Sep 1997 | A |
| 5694616 | Johnson et al. | Dec 1997 | A |
| 5721906 | Siefert | Feb 1998 | A |
| 5742905 | Pepe et al. | Apr 1998 | A |
| 5774670 | Montulli | Jun 1998 | A |
| 5793365 | Tang et al. | Aug 1998 | A |
| 5802470 | Gaulke et al. | Sep 1998 | A |
| 5850594 | Cannon et al. | Dec 1998 | A |
| 5867162 | O'leary et al. | Feb 1999 | A |
| 5870744 | Sprague | Feb 1999 | A |
| 5872521 | Lopatukin et al. | Feb 1999 | A |
| 5878219 | Vance et al. | Mar 1999 | A |
| 5893091 | Hunt et al. | Apr 1999 | A |
| 5893099 | Schreiber et al. | Apr 1999 | A |
| 5913032 | Schwartz et al. | Jun 1999 | A |
| 5920692 | Nguyen et al. | Jul 1999 | A |
| 5940488 | Degrazia et al. | Aug 1999 | A |
| 5946616 | Schornack et al. | Aug 1999 | A |
| 5946617 | Portaro et al. | Aug 1999 | A |
| 5946630 | Willars et al. | Aug 1999 | A |
| 5948058 | Kudoh et al. | Sep 1999 | A |
| 5950193 | Kulkarni et al. | Sep 1999 | A |
| 5951643 | Shelton et al. | Sep 1999 | A |
| 5951652 | Ingrassia et al. | Sep 1999 | A |
| 5954798 | Shelton et al. | Sep 1999 | A |
| 5960173 | Tang et al. | Sep 1999 | A |
| 5978673 | Alperovich et al. | Nov 1999 | A |
| 5987113 | James | Nov 1999 | A |
| 5991791 | Siefert | Nov 1999 | A |
| 5995023 | Kreft | Nov 1999 | A |
| 5999932 | Paul | Dec 1999 | A |
| 6002402 | Schacher | Dec 1999 | A |
| 6009413 | Webber et al. | Dec 1999 | A |
| 6012051 | Sammon et al. | Jan 2000 | A |
| 6014135 | Fernandes | Jan 2000 | A |
| 6014638 | Burge et al. | Jan 2000 | A |
| 6026403 | Siefert | Feb 2000 | A |
| 6026429 | Jones et al. | Feb 2000 | A |
| 6038451 | Syed et al. | Mar 2000 | A |
| 6049533 | Norman et al. | Apr 2000 | A |
| 6065047 | Carpenter et al. | May 2000 | A |
| 6073138 | de l'Etraz et al. | Jun 2000 | A |
| 6081830 | Schindler | Jun 2000 | A |
| 6085223 | Carino et al. | Jul 2000 | A |
| 6088435 | Barber et al. | Jul 2000 | A |
| 6091948 | Carr et al. | Jul 2000 | A |
| 6134432 | Holmes et al. | Oct 2000 | A |
| 6141545 | Begeja et al. | Oct 2000 | A |
| 6151584 | Papierniak et al. | Nov 2000 | A |
| 6161130 | Horvitz et al. | Dec 2000 | A |
| 6166730 | Goode et al. | Dec 2000 | A |
| 6167256 | Yla-Outinen | Dec 2000 | A |
| 6175831 | Weinreich et al. | Jan 2001 | B1 |
| 6189026 | Birrell et al. | Feb 2001 | B1 |
| 6199099 | Gershman et al. | Mar 2001 | B1 |
| 6199103 | Sakaguchi et al. | Mar 2001 | B1 |
| 6212550 | Segur | Apr 2001 | B1 |
| 6247043 | Bates et al. | Jun 2001 | B1 |
| 6249740 | Ito et al. | Jun 2001 | B1 |
| 6249743 | Ohshimo | Jun 2001 | B1 |
| 6260148 | Aggarwal et al. | Jul 2001 | B1 |
| 6269369 | Robertson et al. | Jul 2001 | B1 |
| 6301609 | Aravamudan et al. | Oct 2001 | B1 |
| 6311211 | Shaw et al. | Oct 2001 | B1 |
| 6324541 | de l'Etraz et al. | Nov 2001 | B1 |
| 6330590 | Cotten | Dec 2001 | B1 |
| 6347332 | Malet et al. | Feb 2002 | B1 |
| 6349299 | Spencer et al. | Feb 2002 | B1 |
| 6351698 | Kubota et al. | Feb 2002 | B1 |
| 6360251 | Fujita et al. | Mar 2002 | B1 |
| 6363248 | Silverman | Mar 2002 | B1 |
| 6363392 | Halstead et al. | Mar 2002 | B1 |
| 6374246 | Matsuo | Apr 2002 | B1 |
| 6374290 | Scharber et al. | Apr 2002 | B1 |
| 6389127 | Vardi et al. | May 2002 | B1 |
| 6389372 | Glance et al. | May 2002 | B1 |
| 6392669 | Matoba et al. | May 2002 | B1 |
| 6400381 | Barrett et al. | Jun 2002 | B1 |
| 6415318 | Aggarwal et al. | Jul 2002 | B1 |
| 6421439 | Liffick | Jul 2002 | B1 |
| 6421675 | Ryan et al. | Jul 2002 | B1 |
| 6421709 | McCormick et al. | Jul 2002 | B1 |
| 6425012 | Trovato et al. | Jul 2002 | B1 |
| 6430604 | Ogle et al. | Aug 2002 | B1 |
| 6446112 | Bunney et al. | Sep 2002 | B1 |
| 6449344 | Goldfinger et al. | Sep 2002 | B1 |
| 6449634 | Capiel | Sep 2002 | B1 |
| 6457044 | Iwazaki | Sep 2002 | B1 |
| 6463471 | Dreke et al. | Oct 2002 | B1 |
| 6480885 | Olivier | Nov 2002 | B1 |
| 6484196 | Maurille | Nov 2002 | B1 |
| 6501834 | Milewski et al. | Dec 2002 | B1 |
| 6505167 | Horvitz et al. | Jan 2003 | B1 |
| 6507866 | Barchi | Jan 2003 | B1 |
| 6525747 | Bezos | Feb 2003 | B1 |
| 6535586 | Cloutier et al. | Mar 2003 | B1 |
| 6539421 | Appelman et al. | Mar 2003 | B1 |
| 6542750 | Hendrey et al. | Apr 2003 | B2 |
| 6549933 | Barrett et al. | Apr 2003 | B1 |
| 6549937 | Auerbach et al. | Apr 2003 | B1 |
| 6557027 | Cragun | Apr 2003 | B1 |
| 6559863 | Megiddo | May 2003 | B1 |
| 6564261 | Gudjonsson et al. | May 2003 | B1 |
| 6564264 | Creswell et al. | May 2003 | B1 |
| 6567796 | Yost et al. | May 2003 | B1 |
| 6571234 | Knight et al. | May 2003 | B1 |
| 6580790 | Henry et al. | Jun 2003 | B1 |
| 6604133 | Aggarwal et al. | Aug 2003 | B2 |
| 6606647 | Shah et al. | Aug 2003 | B2 |
| 6608637 | Beaton | Aug 2003 | B1 |
| 6615241 | Miller et al. | Sep 2003 | B1 |
| 6625423 | Wang | Sep 2003 | B1 |
| 6636733 | Helferich | Oct 2003 | B1 |
| 6639299 | Aoki | Oct 2003 | B2 |
| 6640218 | Golding et al. | Oct 2003 | B1 |
| 6640230 | Alexander et al. | Oct 2003 | B1 |
| 6643669 | Novak | Nov 2003 | B1 |
| 6647259 | Boyle | Nov 2003 | B1 |
| 6647383 | August et al. | Nov 2003 | B1 |
| 6654683 | Jin et al. | Nov 2003 | B2 |
| 6657234 | Tanizawa | Dec 2003 | B1 |
| 6658095 | Yoakum | Dec 2003 | B1 |
| 6677968 | Appelman | Jan 2004 | B1 |
| 6678719 | Stimmel | Jan 2004 | B1 |
| 6687362 | Lindquist et al. | Feb 2004 | B1 |
| 6691162 | Wick | Feb 2004 | B1 |
| 6694353 | Sommerer | Feb 2004 | B2 |
| 6697807 | McGeachie | Feb 2004 | B2 |
| 6701348 | Sommerer | Mar 2004 | B2 |
| 6714791 | Friedman | Mar 2004 | B2 |
| 6714793 | Carey | Mar 2004 | B1 |
| 6728357 | O'Neal | Apr 2004 | B2 |
| 6731308 | Tang et al. | May 2004 | B1 |
| 6732155 | Meek | May 2004 | B2 |
| 6750881 | Appelman | Jun 2004 | B1 |
| 6760580 | Robinson et al. | Jul 2004 | B2 |
| 6772188 | Cloutier et al. | Aug 2004 | B1 |
| 6781608 | Crawford | Aug 2004 | B1 |
| 6785554 | Amerga | Aug 2004 | B1 |
| 6785681 | Keskar et al. | Aug 2004 | B2 |
| 6785781 | Leenstra et al. | Aug 2004 | B2 |
| 6788769 | Waites | Sep 2004 | B1 |
| 6799039 | Wu et al. | Sep 2004 | B2 |
| 6800031 | Di Cesare | Oct 2004 | B2 |
| 6832245 | Isaacs et al. | Dec 2004 | B1 |
| 6839737 | Friskel | Jan 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 |
| 6957077 | Dehlin | Oct 2005 | B2 |
| 6968179 | De Vries | Nov 2005 | B1 |
| 6993564 | Whitten | Jan 2006 | B2 |
| 7035865 | Doss et al. | Apr 2006 | B2 |
| 7039639 | Brezin et al. | May 2006 | B2 |
| 7058036 | Yu et al. | Jun 2006 | B1 |
| 7058690 | Maehiro | Jun 2006 | B2 |
| 7065186 | Myers | Jun 2006 | B1 |
| 7082047 | Chow | Jul 2006 | B2 |
| 7117254 | Lunt et al. | Oct 2006 | B2 |
| 7120455 | Chen et al. | Oct 2006 | B1 |
| 7124123 | Roskind et al. | Oct 2006 | B1 |
| 7127232 | O'Neil et al. | Oct 2006 | B2 |
| 7177880 | Ruvolo et al. | Feb 2007 | B2 |
| 7181498 | Zhu et al. | Feb 2007 | B2 |
| 7185059 | Daniell et al. | Feb 2007 | B2 |
| 7188153 | Lunt et al. | Mar 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 |
| 7269590 | Hull et al. | Sep 2007 | B2 |
| 7269629 | Zmudzinski et al. | Sep 2007 | B2 |
| 7275215 | Werndorfer et al. | Sep 2007 | B2 |
| 7287097 | Friend et al. | Oct 2007 | B1 |
| 7298831 | Keohane | Nov 2007 | B1 |
| 7308082 | Davis | Dec 2007 | B2 |
| 7313760 | Grossman et al. | Dec 2007 | B2 |
| 7319882 | Mendiola et al. | Jan 2008 | B2 |
| 7321920 | Washburn | Jan 2008 | B2 |
| 7321921 | Malik | Jan 2008 | B2 |
| 7330713 | Zhu | Feb 2008 | B2 |
| 7353015 | Tenhunen | Apr 2008 | B1 |
| 7370278 | Malik et al. | May 2008 | B2 |
| 7373383 | Boss et al. | May 2008 | B2 |
| 7403970 | Kamble et al. | Jul 2008 | B1 |
| 7403972 | Lau et al. | Jul 2008 | B1 |
| 7409428 | Brabec et al. | Aug 2008 | B1 |
| 7412231 | Kelleher | Aug 2008 | B1 |
| 7412232 | Wilson et al. | Aug 2008 | B2 |
| 7428580 | Hullfish et al. | Sep 2008 | B2 |
| 7428590 | Miller et al. | Sep 2008 | B2 |
| 7436780 | Stephens et al. | Oct 2008 | B2 |
| 7499973 | Couts | Mar 2009 | B2 |
| 7512407 | Wu et al. | Mar 2009 | B2 |
| 7519675 | Di Giorgio et al. | Apr 2009 | B2 |
| 7555520 | Watanabe et al. | Jun 2009 | B2 |
| 7564958 | Contractor | Jul 2009 | B1 |
| 7590696 | Odell | Sep 2009 | B1 |
| 7603421 | Roche et al. | Oct 2009 | B1 |
| 7606864 | Koch | Oct 2009 | B2 |
| 7640293 | Wilson et al. | Dec 2009 | B2 |
| 7653389 | Eales et al. | Jan 2010 | B2 |
| 7657253 | Lewis | Feb 2010 | B2 |
| 7660856 | O'Brien et al. | Feb 2010 | B2 |
| 7660864 | Markki et al. | Feb 2010 | B2 |
| 7668535 | Conneely et al. | Feb 2010 | B2 |
| 7668917 | Netsch et al. | Feb 2010 | B2 |
| 7680887 | Kiss et al. | Mar 2010 | B2 |
| 7730143 | Appelman | Jun 2010 | B1 |
| 7765262 | Gross et al. | Jul 2010 | B2 |
| 7765263 | Alfke | Jul 2010 | B1 |
| 7792906 | Garcia-Martin et al. | Sep 2010 | B2 |
| 7848744 | Eason et al. | Dec 2010 | B2 |
| 7853652 | McCarty | Dec 2010 | B2 |
| 7890586 | McNamara | Feb 2011 | B1 |
| 7895263 | Kirchmeier et al. | Feb 2011 | B1 |
| 7895273 | Haldar | Feb 2011 | B1 |
| 7895314 | Russell | Feb 2011 | B1 |
| 7912899 | Beauchamp et al. | Mar 2011 | B2 |
| 7912903 | Shah et al. | Mar 2011 | B2 |
| 7924811 | Asokan | Apr 2011 | B2 |
| 7945623 | Simpson | May 2011 | B2 |
| 7961663 | Lin | Jun 2011 | B2 |
| 7975009 | Wilensky | Jul 2011 | B2 |
| 8005461 | Vander Veen et al. | Aug 2011 | B2 |
| 8046008 | Park et al. | Oct 2011 | B2 |
| 8060566 | Appleman | Nov 2011 | B2 |
| 8103722 | Lee | Jan 2012 | B2 |
| 8122084 | Beringer | Feb 2012 | B2 |
| RE43284 | Degraeve | Mar 2012 | E |
| 8131803 | Hardy et al. | Mar 2012 | B2 |
| 8150925 | Zimmers et al. | Apr 2012 | B2 |
| 8161116 | Chaddha et al. | Apr 2012 | B2 |
| 8243893 | Hayes et al. | Aug 2012 | B2 |
| 8370756 | Malik et al. | Feb 2013 | B2 |
| 8443049 | Geddes | May 2013 | B1 |
| 8483729 | Knotts | Jul 2013 | B2 |
| 8516055 | Hind et al. | Aug 2013 | B2 |
| 8706826 | Appelman | Apr 2014 | B2 |
| 8965964 | Odell | Feb 2015 | B1 |
| 9002949 | Appleman | Apr 2015 | B2 |
| 9043404 | Lonnfors | May 2015 | B2 |
| 9049569 | Appelman | Jun 2015 | B2 |
| 9088879 | Appelman | Jul 2015 | B2 |
| 9319356 | Odell | Apr 2016 | B2 |
| 20010002469 | Bates et al. | May 2001 | A1 |
| 20010003202 | Mache | Jun 2001 | A1 |
| 20010003203 | Mache | Jun 2001 | A1 |
| 20010005861 | Mousseau et al. | Jun 2001 | A1 |
| 20010013050 | Shah | Aug 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 |
| 20020042816 | Bae | Apr 2002 | A1 |
| 20020049610 | Gropper | Apr 2002 | A1 |
| 20020049751 | Chen et al. | Apr 2002 | A1 |
| 20020052921 | Morkel | May 2002 | A1 |
| 20020059201 | Work | May 2002 | A1 |
| 20020065828 | Goodspeed | May 2002 | A1 |
| 20020065856 | Kisiel | May 2002 | A1 |
| 20020065894 | Dalal et al. | May 2002 | A1 |
| 20020077080 | Greene | Jun 2002 | A1 |
| 20020083127 | Agrawal | Jun 2002 | A1 |
| 20020083136 | Whitten | Jun 2002 | A1 |
| 20020087634 | Ogle | Jul 2002 | A1 |
| 20020087704 | Chesnais et al. | Jul 2002 | A1 |
| 20020091667 | Jaipuria et al. | Jul 2002 | A1 |
| 20020097856 | Wullert | Jul 2002 | A1 |
| 20020103801 | Lyons | Aug 2002 | A1 |
| 20020112181 | Smith | Aug 2002 | A1 |
| 20020116461 | Diacakis et al. | Aug 2002 | A1 |
| 20020116463 | Hart | Aug 2002 | A1 |
| 20020116563 | Lever | Aug 2002 | A1 |
| 20020116641 | Mastrianni | Aug 2002 | A1 |
| 20020117733 | Racanelli | Aug 2002 | A1 |
| 20020120687 | Diacakis et al. | Aug 2002 | A1 |
| 20020120697 | Generous et al. | Aug 2002 | A1 |
| 20020133292 | Miyaki | Sep 2002 | A1 |
| 20020133369 | Johnson | Sep 2002 | A1 |
| 20020137530 | Karve | Sep 2002 | A1 |
| 20020147777 | Hackbarth et al. | Oct 2002 | A1 |
| 20020169748 | Macholda | Nov 2002 | A1 |
| 20020174010 | Rice, III | Nov 2002 | A1 |
| 20020175953 | Lin | Nov 2002 | A1 |
| 20020178161 | Brezin et al. | Nov 2002 | A1 |
| 20020181703 | Logan et al. | Dec 2002 | A1 |
| 20020184089 | Tsou et al. | Dec 2002 | A1 |
| 20020188688 | Bice | Dec 2002 | A1 |
| 20020193942 | Odakura et al. | Dec 2002 | A1 |
| 20020199095 | Bandini et al. | Dec 2002 | A1 |
| 20030004855 | Dutta et al. | Jan 2003 | A1 |
| 20030004872 | Gardi et al. | Jan 2003 | A1 |
| 20030009523 | Lindskog et al. | Jan 2003 | A1 |
| 20030018726 | Low | Jan 2003 | A1 |
| 20030023691 | Knauerhase | Jan 2003 | A1 |
| 20030023875 | Hursey et al. | Jan 2003 | A1 |
| 20030025824 | Ishikawa | Feb 2003 | A1 |
| 20030028524 | Keskar et al. | Feb 2003 | A1 |
| 20030028542 | Muttik 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 |
| 20030055831 | Ryan et al. | Mar 2003 | A1 |
| 20030058478 | Aoki | Mar 2003 | A1 |
| 20030065721 | Roskind | Apr 2003 | A1 |
| 20030065724 | Clark | Apr 2003 | A1 |
| 20030084103 | Weiner et al. | May 2003 | A1 |
| 20030088554 | Ryan et al. | May 2003 | A1 |
| 20030088633 | Chiu et al. | May 2003 | A1 |
| 20030093580 | Thomas et al. | May 2003 | A1 |
| 20030101226 | Quine | May 2003 | A1 |
| 20030101343 | Eaton et al. | May 2003 | A1 |
| 20030105822 | Gusler et al. | Jun 2003 | A1 |
| 20030112225 | Granberg | Jun 2003 | A1 |
| 20030131061 | Newton et al. | Jul 2003 | A1 |
| 20030135569 | Khakoo | Jul 2003 | A1 |
| 20030154257 | Hantsch et al. | Aug 2003 | A1 |
| 20030158860 | Caughey | Aug 2003 | A1 |
| 20030158864 | Samn | Aug 2003 | A1 |
| 20030167324 | Farnham et al. | Sep 2003 | A1 |
| 20030172349 | Katayama et al. | Sep 2003 | A1 |
| 20030182394 | Ryngler et al. | Sep 2003 | A1 |
| 20030187813 | Goldman et al. | Oct 2003 | A1 |
| 20030208545 | Eaton et al. | Nov 2003 | A1 |
| 20030217109 | Ordille et al. | Nov 2003 | A1 |
| 20030219104 | Malik | Nov 2003 | A1 |
| 20030219109 | Malik | Nov 2003 | A1 |
| 20030220946 | Malik | Nov 2003 | A1 |
| 20030220976 | Malik | Nov 2003 | A1 |
| 20030229722 | Beyda | Dec 2003 | A1 |
| 20040015548 | Lee | Jan 2004 | A1 |
| 20040019695 | Fellenstein | Jan 2004 | A1 |
| 20040029572 | Nerot | Feb 2004 | A1 |
| 20040039630 | Begole et al. | Feb 2004 | A1 |
| 20040044536 | Fitzpatrick et al. | Mar 2004 | A1 |
| 20040054646 | Daniell et al. | Mar 2004 | A1 |
| 20040054736 | Daniell et al. | Mar 2004 | A1 |
| 20040056901 | March et al. | Mar 2004 | A1 |
| 20040059781 | Yoakum et al. | Mar 2004 | A1 |
| 20040073643 | Hayes et al. | Apr 2004 | A1 |
| 20040078445 | Malik | Apr 2004 | A1 |
| 20040117443 | Barsness | Jun 2004 | A1 |
| 20040122681 | Ruvolo et al. | Jun 2004 | A1 |
| 20040122810 | Mayer | Jun 2004 | A1 |
| 20040122855 | Ruvolo et al. | Jun 2004 | A1 |
| 20040128310 | Zmudzinski | Jul 2004 | A1 |
| 20040128356 | Bernstein et al. | Jul 2004 | A1 |
| 20040136358 | Hind et al. | Jul 2004 | A1 |
| 20040154022 | Boss et al. | Aug 2004 | A1 |
| 20040158610 | Davis | Aug 2004 | A1 |
| 20040165705 | Cragun | Aug 2004 | A1 |
| 20040179039 | Blattner et al. | Sep 2004 | A1 |
| 20040186738 | Reisman | Sep 2004 | A1 |
| 20040199649 | Tarnanen | Oct 2004 | A1 |
| 20040201624 | Crawford | Oct 2004 | A1 |
| 20040210844 | Pettinati et al. | Oct 2004 | A1 |
| 20040215648 | Marshall et al. | Oct 2004 | A1 |
| 20040215721 | Szeto et al. | Oct 2004 | A1 |
| 20040215793 | Ryan et al. | Oct 2004 | A1 |
| 20040221309 | Zaner et al. | Nov 2004 | A1 |
| 20040254998 | Horvitz | Dec 2004 | A1 |
| 20040260762 | Fish | Dec 2004 | A1 |
| 20040267531 | Whynot | Dec 2004 | A1 |
| 20050013426 | Ooki | Jan 2005 | A1 |
| 20050015432 | Cohen | Jan 2005 | A1 |
| 20050021750 | Abrams | Jan 2005 | A1 |
| 20050027382 | Kirmse et al. | Feb 2005 | A1 |
| 20050038688 | Collins et al. | Feb 2005 | A1 |
| 20050038856 | Krishnasamy et al. | Feb 2005 | A1 |
| 20050043989 | Shifrin | Feb 2005 | A1 |
| 20050044152 | Hardy et al. | Feb 2005 | A1 |
| 20050050143 | Gusler et al. | Mar 2005 | A1 |
| 20050055416 | Heikes et al. | Mar 2005 | A1 |
| 20050060377 | Lo et al. | Mar 2005 | A1 |
| 20050076241 | Appelman | Apr 2005 | A1 |
| 20050080859 | Lake | Apr 2005 | A1 |
| 20050080863 | Daniell | Apr 2005 | A1 |
| 20050086211 | Mayer | Apr 2005 | A1 |
| 20050091311 | Lund et al. | Apr 2005 | A1 |
| 20050114229 | Ackley et al. | May 2005 | A1 |
| 20050114533 | Hullfish | May 2005 | A1 |
| 20050153681 | Hanson | Jul 2005 | A1 |
| 20050171799 | Hull et al. | Aug 2005 | A1 |
| 20050177486 | Yeager | Aug 2005 | A1 |
| 20050187781 | Christensen | Aug 2005 | A1 |
| 20050197846 | Pezaris et al. | Sep 2005 | A1 |
| 20050198268 | Chandra | Sep 2005 | A1 |
| 20050198321 | Blohm | Sep 2005 | A1 |
| 20050210148 | Kato | Sep 2005 | A1 |
| 20050216300 | Appelman et al. | Sep 2005 | A1 |
| 20050220134 | Lin | Oct 2005 | A1 |
| 20050246420 | Little | Nov 2005 | A1 |
| 20060005133 | Lyle et al. | Jan 2006 | A1 |
| 20060025164 | Wang | Feb 2006 | A1 |
| 20060041684 | Daniell et al. | Feb 2006 | A1 |
| 20060075044 | Fox et al. | Apr 2006 | A1 |
| 20060129643 | Nielson | Jun 2006 | A1 |
| 20060129678 | Morita | Jun 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 |
| 20060190117 | Weczorek et al. | Aug 2006 | A1 |
| 20060190543 | Pulver et al. | Aug 2006 | A1 |
| 20060212561 | Feng | Sep 2006 | A1 |
| 20060248573 | Pannu et al. | Nov 2006 | A1 |
| 20060277187 | Roese et al. | Dec 2006 | A1 |
| 20070156664 | Norton et al. | Jul 2007 | A1 |
| 20070250566 | Appelman et al. | Oct 2007 | A1 |
| 20080089316 | Reams | Apr 2008 | A1 |
| 20080140827 | Ma | Jun 2008 | A1 |
| 20080228598 | Leff et al. | Sep 2008 | A1 |
| 20080255989 | Altberg et al. | Oct 2008 | A1 |
| 20080256257 | Miller et al. | Oct 2008 | A1 |
| 20090006555 | Curran et al. | Jan 2009 | A1 |
| 20090016499 | Hullfish et al. | Jan 2009 | A1 |
| 20090043844 | Zimmet et al. | Feb 2009 | A1 |
| 20090044252 | Kashima et al. | Feb 2009 | A1 |
| 20090070306 | Stroe et al. | Mar 2009 | A1 |
| 20090234922 | Appelman | Sep 2009 | A1 |
| 20100005523 | Hassan et al. | Jan 2010 | A1 |
| 20110289170 | Smith et al. | Nov 2011 | A1 |
| 20120083297 | Appelman | Apr 2012 | A1 |
| 20130073653 | Heikes | Mar 2013 | A1 |
| 20130073657 | Hullfish et al. | Mar 2013 | A1 |
| 20130138752 | Guthrie et al. | May 2013 | A1 |
| 20130172026 | Odell et al. | Jul 2013 | A1 |
| 20140289249 | Davis | Sep 2014 | A1 |
| 20150032831 | Hullfish et al. | Jan 2015 | A1 |
| Number | Date | Country |
|---|---|---|
| 1176840 | Aug 2000 | EP |
| 0862304 | Jan 2002 | EP |
| 2357932 | Jan 2004 | GB |
| 2368747 | Dec 2004 | GB |
| 2000259514 | Oct 2000 | JP |
| 2000284999 | Mar 2001 | JP |
| 2001084320 | Mar 2001 | JP |
| 9710558 | Aug 1996 | WO |
| 9746955 | Dec 1997 | WO |
| 9816045 | Apr 1998 | WO |
| 9847270 | Jan 1999 | WO |
| 9908434 | Feb 1999 | WO |
| 9934628 | Jul 1999 | WO |
| 0079396 | Dec 2000 | WO |
| 0106748 | Jan 2001 | WO |
| 0122258 | Mar 2001 | WO |
| 0167622 | Sep 2001 | WO |
| 0203216 | Jan 2002 | WO |
| 02073886 | Sep 2002 | WO |
| 02101495 | Dec 2002 | WO |
| 0167787 | Mar 2003 | WO |
| Entry |
|---|
| USPTO, Final Office Action for U.S. Appl. No. 11/720,726, Mar. 15, 2011, 4 pages. |
| EPO, European Extended Search Report for European Patent Application No. 05852328.3, Jan. 7, 2014, 8 pages. |
| “Active Directory”, [online], [retrieved on May 13, 2003]. http://www.microsoft.com/windows2000/technologies/directory/AD/default.as-p, 13 pages. |
| “AOL technology: turning complicated things into engaging services”, 1996 Annual Report, 1995, 22 pages. |
| “Frequently Asked Questions About AOL Instant Messenger”, Jun. 24, 1999, 6 pages. |
| “New Features in AOL Instant Messenger for Windows v. 2.01 Beta”, http://www.aol.com/aim/winbeta.html, Apr. 28, 1999, 2 pages. |
| Gupta, Minaxi et al., “A Reputation System for Peer-to-Peer Networks”, NOSSDAV'03, Monterey California, Jun. 1-3, 2003, pp. 144-152. |
| Cerulean Studios, “Trillian Discussion Forums—How To: Import ICQ 2003a Contact List”, http://trillian.cc/forums/showthread.php?s=&threadid=36475 [retrieved Apr. 29, 2014], Apr. 29, 2004, 2 pages. |
| “A Countermeasure to Duplicate-detecting Anti-spam Techniques,” Robert J. Hall, AT&T Labs Technical Report 99.9.1, 1999, (27 pages). |
| Hattori et al., “Socialware: Multiagent systems for Supporting Network Communities,”, Mar. 1999, Association for Computing Machinery, Communications of the ACM, vol. 42, Iss. 3, pp. 55ff. |
| “Support Vector Machines,” Marti Hearst, IEEE Intelligent Systems, Jul./Aug. 1998, pp. 18-28. |
| Marino, “Hottie or Nottie? Web Site Voters Let You Know Whether You Sizzle or Fizzle”, Jul. 11, 2001, Florida Times Union, p. C.1. |
| “Technical Solutions for Controlling Spam,” Shane Hird, Proceedings of AUUG2002, Melbourne, Sep. 4-6, 2002, (17 pages). |
| “Lotus Instant Messaging Everyplace FAQ,” retrieved Apr. 29, 2004 from the World Wide Web: http://www.lotus.com/products/product4.nsf/wdocs/249c6f083166cd3e85256d73-00714407, (3 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, (5 pages). |
| Jensen et al., “Finding Others Online: Reputation Systems for Social Online Spaces”, Apr. 20-25, 2002, CHI, Minneapolis, Minnesota, vol. 4, Issue 1, pp. 447-454. |
| “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). |
| “Will You Buy a Car From This Man?,” Leander Kahney, Oct. 6, 2003, (3 pages). |
| Liener, Ron, “SWF Seeks Attractive Head Shot; To Stand Out, Online Daters Pay for Professional Photos; Cropping the Ex-Wife”, The Wall Street Journal, Nov. 19, 2003, 4 pages. |
| “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. |
| Riordan, “Idea for Online Networking Brings Two Entrepreneurs Together”, The New York Times, Dec. 1, 2003, 2 pages. |
| Tang et al., “ConNexus to Awarenex: Extending awareness to mobile users.” Sun Microsystems Laboratories. SOGCHI '01. Mar. 31-Apr. 2001, Seattle, WA, USA. ACM 1-58113-327-8/01/0003, pp. 221-228. |
| “Digital Artifacts for Remembering and Storytelling: Post History and Social Network Fragments,” Viegas et al., retrieved from the World Wide Web: http://we.media.mit.edu/.about.fviegas/papers/posthistory.sub.--snf.- pdf, 2004, (10 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). |
| Non-Final Office Action dated Mar. 13, 2013 for U.S. Appl. No. 11/017,202. |
| Final Office Action dated Aug. 21, 2013 for U.S. Appl. No. 11/072,202. |
| Non-Final Office Action dated Sep. 13, 2013 for U.S. Appl. No. 12/662,909. |
| Final Office Action dated Jan. 7, 2014 for U.S. Appl. No. 12/662,909. |
| Restriction Requirement, dated May 15, 2009, for related U.S. Appl. No. 11/618,635. |
| Leslie Walker, “Business at Cyberspeed; Brainstorm Becomes Quick Internet Hit; [Final Edition],” The Washington Post, Jan. 24, 1999, pp. A.01 (4 total pages). |
| “Instant Messaging for Garners,” 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. |
| “PieSpy—Inferring and Visualizing Social Network on IRC,” PieSpy Social Network Bot, reprinted from http://lister.linux-srv.anlx.net/piespy printed on Mar. 11, 2004 (18 pages). |
| “Plaxo,” Plaxo, reprinted from http://web.archive.org/web/20041105072256/http://www.plaxo.com/ printed on Nov. 5, 2004 (available on Feb. 14, 2004) (2 pages). |
| “Plaxo Update Your Address Book” Plaxo Contact Networks, Reprinted from http:://web.archive.org/web/20030218233638/http://www.plaxo.com/ Printed on Nov. 5, 2004 (available on Feb. 18, 2003) 1 page. |
| Resnick et al., “Reputation Systems”, Dec. 2000, Communications of the ACM, vol. 43, No. 12, Dec. 2000, pp. 45-48. |
| “RIM Road: Software: Internet & Network: Webmessenger RIM J2ME/Instant Messaging,” retrieved Apr. 29, 2004 from the World Wide Web: http://www.rimroad.com/software/rim1/Webmessenger-RIM-J2ME-Instant -Messaging-20., (4 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, (2 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). |
| Nick Wingfield; Technology Journal: Changing Chat—Instant Messaging is Taking Off, and for Some Users It's Nuzzling Out the Phone; Asian WSJ; Sep. 2000, (5 pages). |
| Telstra targets Net spammers, J. Dudley, news.com.au, Dec. 2, 2003, (2 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). |
| “Welcome to Huminity World of Connections,” Huminity-Home, reprinted from http://web.archive.org/web/20030228131435/www.huminity.com/default.php?in-ternationa . . . printed on Nov. 5, 2004 (available on Feb. 2, 2003) (1 page). |
| America Online Inc., “AOL Instant Messenger”, Aug. 29, 2000, Internet: www.aol.com/aim/ (18 pages). |
| America Online Inc., New AIM 4.7, Sep. 27, 2001, Internet: http://aim.aol.com (7 pages). |
| CNET Networks Inc., “PopUp Killer”, Sep. 13, 2001, Internet: download.cnet.com/downloads/0-10059-100-6932612.html, (3 pages). |
| Ed Bott and Ron Person, Using Windows 95 with Internet Explorer 4.0, Feb. 17, 1998, Que, Special Edition. |
| Home-tribe.net, http://washingtondc.tribe.net/message/24434d1b-817b-4580-aa42-3bffa15f26a- ?page=1, (4 pages). Reprinted on Dec. 13, 2004. |
| http://www.friendster.com, Dec. 13, 2004, (17 pages). |
| McKendrick, Joseph; “Internet Call Centers: New Era in Customer Service”, Feb. 2002; V10, n2, (4 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). |
| 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). |
| WebmasterWorld.com Inc., “HTML and Browsers”, Mar. 5, 2001, Internet: www.webmaster.com/forum21/637.htm, (2 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). |
| “Announce: Implementation of E-mail Spam Proposal,” Maurice L. Marvin, news.admin.net-abuse.misc, Aug. 3, 1996, 2 pages. |
| Non-Final Office Action, dated Jul. 22, 2009, for U.S. Appl. No. 11/618,635. |
| Office Action, dated Feb. 9, 2007, for U.S. Appl. No. 09/893,693. |
| BigBlueBall.com, How to turn off IM forwarding for AIM Mobile. http://www.bigblueball.com/forums/aim-support/15256-how-turn-off-im-forwarding-aim-mobile-3.html. May 2003. pp. 1-3. |
| Non-Final Office Action dated Mar. 20, 2012 related U.S. Appl. No. 13/274,076. |
| Trillian Pro 2.0. Cerulean Studios. http://web.archive.org/web/20031118192623/www.ceruleanstudios.com/. Nov. 2003. pp. 1-21. |
| “Trillian Pro User Manual”. Cerulean Studios., http://web.archive.org/web/20040409110818/www.ceruleanstudios.com/support/manual.php. Apr. 2004. pp. 1-70. |
| Non-Final Office Action dated Feb. 5, 2014 for U.S. Appl. No. 11/017,202. |
| Non-Final Office Action dated Jun. 5, 2014 for U.S. Appl. No. 13/770,864. |
| “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). |
| “About Internet Directory Services,” Outlook 2000 SR-1 (9.0.0. 4527) Help File, on or before Aug. 10, 2001, p. 1. |
| “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.as- p, pp. 1-4. |
| “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/addat-asheetasp>, pp. 1-5. |
| “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/adwin- 2k.asp>, pp. 1-9. |
| “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/presspas/press/1998/July98/ActivDPR.asp, pp. 1-4. |
| “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/w2ke-ims.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/adappstrasp?fraa . . . , 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.com/windows2000/server/evaluationinews/-bulletins/mmsma.asp>, p. 1. |
| “The Gordano Messaging Server,” http://www.gordano.com, Copyright 1994-2003, Gordano, 3 pages. |
| “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. |
| “Part II: Tasks and Procedures,” Active Directory Operations Guide, Microsoft Corporation, Microsoft Windows 2000, Version 1.5, Published Dec. 5, 2002, pp. 1-131. |
| “AOL Instant Messenger All New Version 2.0 Quick Tips for Getting Started,” Jun. 24, 1999, 5 pages. |
| “Set up LDAP directory services,” Outlook 2000 SR-1 (9.0.0 4527) Help File, on or before Aug. 10, 2001, p. 1. |
| “The LP Wireless Messenger,” Messenger Documentation, [online]. LP Wireless, Inc., 2002, retrieved on Nov. 2, 2002 from http://www.lpwireless.com/messengerhelp.htm, pp. 1-7. |
| “Using Active Directory Service,” from Chapter 5, Microsoft Windows 2000 Administrators Pocket Consultant, by William R Stank (1999). pp. 1-6. |
| “What is AOL Instant Messenger,” Jun. 24, 1999, 3 pages. |
| “What's new about exchanging information over the Internet,” Outlook 2000 SR-1 (9.0.0A527), 1 page. |
| “Windows 2000 Directory Services,” [online] http://www.microsoft.com/windows2000/technologies/directory/default.asp, Nov. 25, 2001, 1 page. |
| “YAHOO! Messenger Makes the World a Little Smaller, More Informed,” Jun. 21, 1999, 2 pages. |
| Alan Cohen, “Instant Messaging,” PC Magazine, PC Labs, Apr. 13, 1999, 2 pages. |
| 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. |
| 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. |
| 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.sub.--adsi-exch.asp?frame=true>, pp. 1-12. |
| Microsoft Corporation, “Comparing Microsoft Active Directory to Novell's NDS,” [online], Sep. 1998 [retrieved on May 13, 2003]. Retrieved from the Internet <http://msdn.microsoft.com/library/en-us/dnactdir/html/msdn—activedirvsnds.asp?frame=true, pp. 1-17. |
| “Microsoft Corporation, ““Introduction to Active Directory Application Mode,”” Microsoft Server 2003, Aug. 2002, pp. 1-13”. |
| “Microsoft Corporation, ““Using ADSI, LDAP, and Network Management Functions With Active Directory,”” [online], Feb. 2002 [retrieved on May 13, 2003]. Retrieved from the <http://msdn.microsoft.comilibrary/en-us/library/ms806997(d=printer) aspx 10 pages”. |
| Part I: Active Directory Operations, Active Directory Operations Guide, Microsoft Corporation, Microsoft Windows 2000, Version 1.5, Published Dec. 5, 2002, pp. 1-187. |
| Stank, William R., “Working with Active Directory Domains,” from Chapter 5, Microsoft Windows 2000 Administrators Pocket Consultant, (1999). pp. 1-10. |
| International Search Report for International Application No. PCT/US03/15715, mailed Aug. 14, 2003, 6 pages. |
| Notice of Allowance, dated Jun. 28, 2011, for related U.S. Appl. No. 11/720,726. |
| Non-Final Office Action, dated Oct. 7, 2010, for related U.S. Appl. No. 11/720,726. |
| Final Office Action, dated Aug. 13, 2009, for related U.S. Appl. No. 11/321,074. |
| Non-Final Office Action dated Jan. 22, 2009 for related U.S. Appl. No. 11/321,074. |
| Notice of Allowance dated Mar. 11, 2015 for related U.S. Appl. No. 13/770,864. |
| Notice of Allowance dated Jan. 21, 2015 for related U.S. Appl. No. 12/662,909. |
| Non-Final Office Action dated Sep. 30, 2009 for U.S. Appl. No. 11/017,202. |
| Non-Final Office Action dated Sep. 28, 2006 for U.S. Appl. No. 11/017,202. |
| Notice of Allowance dated Aug. 5, 2014 for U.S. Appl. No. 11/017,202. |
| Notice of Allowance dated Dec. 5, 2014 for U.S. Appl. No. 11/017,202. |
| Non-Final Office Action dated Mar. 12, 2013 for U.S. Appl. No. 12/662,909. |
| Final Office Action dated Sep. 5, 2012 for U.S. Appl. No. 12/662,909. |
| First Examination Report dated Nov. 25, 2014 for India App. No. 4295/DELNP/2007. |
| Notice of Allowance dated Oct. 20, 2014 for related U.S. Appl. No. 13/770,864. |
| YAHOO! Messenger, “Messenger Help,” (4 total pages) (available at least as of Aug. 9, 2004). |
| Cerulean Studios, “Trillian Pro: No Boundaries,” (Overview, New Features, Tech Specs, Corporate, Product Tour—16 pages). |
| Cerulean Studios, “Trillian: Your Freedom to Chat,” (Overview, Features, Screenshots, Tech Specs—8 Total Pages). |
| International Search Report issued in International Application No. PCT/US05/42992, dated Mar. 6, 2007, (14 pages). |
| Final Office Action dated May 4, 2007 for U.S. Appl. No. 11/017,202. |
| Non-Final Office Action dated Mar. 24, 2008 for U.S. Appl. No. 11/017,202. |
| Final Office Action dated Dec. 1, 2008 for U.S. Appl. No. 11/017,202. |
| Final Office Action dated Mar. 24, 2010 for U.S. Appl. No. 11/017,202. |
| Office Action—Restriction Requirement dated Feb. 12, 2013 for fo U.S. Appl. No. 11/017,202. |
| Androutsopoulos, “Learning to Filter Spam E-mail: A Comparison of a Naive Bayesian and a Memory-Based Approach,” University of Athens, Sep. 2000, 12 pages. |
| “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). |
| “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). |
| “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). |
| Business Wire, “BestCalls.com Announces the BestCalls Technology Index,” Business Wire, New York, Jun. 30, 1999, pp. 1 (2 total pages). |
| CrushParty.com: Help, retrieved from the Internet on Jun. 12, 2002: http://www.crushparty.com/help.jsp, 3 pages. |
| “Support Vector Machines for Spam Categorization,” Harris Drucker et al., IEEE Transactions on Neural Networks, vol. 10, No. 5, Sep. 1999, pp. 1048-1054, (7 pages). |
| “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 Nets Find Friends in VCs,” Joanna Glasner, http://www.wired.com/news , Nov. 17, 2003, (pp. 1-4). |
| “Better Bayesian Filtering,” Paul Graham, Jan. 2003, pp. 1-11, http://www.paulgraham.com/better.html. |
| “Degrees of Separation Email Spam Protection,” Halfbakery: Degrees of Separation Email Spam Protection, reprinted from http://halfbakery.com/idea/Degrees—20of—20Separation—20 Email—20Spam—20Protecti . . . printed on Mar. 1, 2004 (3 pages). |
| USPTO, Notice of Allowance for U.S. Appl. No. 14/700,100, Jul. 19, 2016, 6 pages. |
| USPTO, Non-final Office Action for U.S. Appl. No. 14/746,788, Jun. 1, 2016, 16 pages. |
| European Patent Office, Examination Report for European Patent Application No. 05852328.3, Jul. 1, 2016, 6 pages. |
| Number | Date | Country | |
|---|---|---|---|
| 20150195223 A1 | Jul 2015 | US |
| Number | Date | Country | |
|---|---|---|---|
| 60631876 | Dec 2004 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 11017202 | Dec 2004 | US |
| Child | 14664506 | US |
