Patent Grant
9215095
This description relates to projecting multiple personalities in communications for a communications application operator (hereinafter “sender”) and/or changing features and functionality based on the selected personality.
Online service providers facilitate access to information and services by providing interactive User Interfaces (UIs) that help users navigate to desired resources. For example, in the case of a system that enables the exchange of instant messages (IMs), a UI allows an IM sender to invoke actions, such as establishing a communications link, through the selection of screen objects such as icons, windows, and drop-down menus. The design of a UI has a significant impact on an IM sender's online experience. In particular, the icons, the windows, and the menus of a UI may be arranged to enable an IM sender to locate information and services quickly and easily.
An IM sender may send self-expression items to an IM recipient. Current implementations of self-expression in instant messaging enable a user to individually select self-expression settings, such as a Buddy Icon and Buddy Wallpaper, which settings thereafter project to everyone who sees or interacts with that person online.
A user may name and save multiple different “personas” or “personalities,” which are groups of instant messaging self-expression settings such as, for example, Buddy Icons, Buddy Sounds, Buddy Wallpaper and Emoticons (e.g., Smileys). Then, depending on the identity with whom the user communicates, they may quickly access and adopt one of their personalities in at least an instant messaging environment, and may manage the online appearance they present to others. Functionality and features of the instant messaging interface may differ based upon the personality being used in the IM conversation.
In one general aspect, a user interface on a display enables perception of communications that leverage an instant messaging platform. The user interface includes a module for identifying at least two identities within an instant messaging communications environment to whom messages may be directed, a module for associating a first persona of a user with a first functionality, a module for associating a second persona of the user with a second functionality, the second functionality differing from the first functionality, a module for rendering an instant messaging application user interface for a first instant messaging communications session involving the user and a first identity and a second instant messaging communications session involving the user and a second identity, the user interface being presented at a system display presented to the user, and a module for enabling the first person of the user to be projected to the first identity while concurrently enabling a second persona of the same user to be projected to the second identity.
Implementations may include one or more of the following features. For example, the first functionality may include encrypting messages sent by the user during the first instant messaging communications session and the second functionality may include not encrypting messages sent by the user during the second instant messaging communications session. In another example, the first functionality may include decrypting messages received by the user during the first instant messaging communications session and the second functionality may include not decrypting messages received by the user during the second instant messaging communications session. In another example, the first functionality may include logging messages sent and received by the user during the first instant messaging communications session and the second functionality may include not logging messages sent and received by the user during the second instant messaging communications session. The first functionality also may include providing a notification concerning the message logging by the user to the first of the identities and the second functionality may include not providing a notification concerning the message logging by the user to the second of the identities.
In another example, the first functionality may include determining the routing of a message received by the user during the first instant messaging communications session. Determining the routing of the message may include determining the routing of the message over a communications mode other than the communications mode over which the message was received. The message may be routed using the determined routing. Routing the message may include forwarding the message to a different user. The message may be forwarded, for example, via e-mail. In a further example, the first functionality includes providing a notification concerning the message routing to the first of the identities. The routing may be determined based upon an online presence state of the user. The second functionality may include not determining a routing of a message received by the user during the second instant messaging communications session.
In another implementation, the first persona and the second persona each include at least one shared functionality. For example, the shared functionality may include logging messages sent and received by the user during the first and the second instant messaging communications sessions. In another example, the first functionality may include encrypting messages sent by the user during the first instant messaging communications session and the second functionality may include not encrypting messages sent by the user during the second instant messaging communications session. In another example, the shared functionality may include encrypting messages sent by the user during the first and the second instant messaging communications sessions, the first functionality may include logging messages sent and received by the user during the first instant messaging communications session and the second functionality may include not logging messages sent and received by the user during the second instant messaging communications session.
The user interface also may include a module for associating the first persona with a first group of identities such that the first persona is projected to members of the first group of identities in a communications session, where the first of the identities is included within the first group of identities. The user interface also may include a module for associating the second persona with a second group of identities such that the second persona is projected to members of the second group of identities in a communications session, where the second of the identities is included within the second group of identities.
The user interface also may include a module for associating an individual persona with the first of the identities, associating a group persona with a group of the identities with which the first of the identities is associated, and associating a global persona with each of the identities, where the first persona projected to the first of the identities comprises an amalgamation of the individual persona associated with the first of the identities, the group persona associated with the group of the identities, and the global persona associated with each of the identities. In one example, the individual persona associated with the first of the identities overrides the group persona associated with the group of the identities and the group persona associated with the group of the identities overrides the global persona associated with each of the identities, to the extent a conflict exists.
The communications session may be an instant messaging communications session. The identities may be members of a buddy list, including the online presence state of the identities.
In one implementation, the user interface may include a module for projecting the functionality of the first persona of the user to the first of the identities while concurrently projecting the functionality of the second persona of the same user to the second of the identities. The user interface also may include a module for selecting among the first and second personas for projection to a particular one of the identities based on an attribute of the particular identity.
The user interface also may include a module for receiving from the user a selection of at least the first and second personas. The user interface also may include a module for selecting functionality of the first persona based upon an attribute of the first identity.
The user interface also may include a module for configuring the functionality of the first persona assigned to the first identity to change based upon the occurrence of a predetermined event. The predetermined event may be based, for example, upon a time of day, a day of the week, or the passage of a pre-determined interval of time. The predetermined event may be, for example, a weather condition at a predetermined geographic location, the communication of a predetermined word, the communication of a predetermined emoticon, a predetermined date, or the communication of a predetermined number of instant messages from the first identity.
In another general aspect, a computer implemented method for enabling perception of multiple online personas in an instant messaging communications session includes identifying at least two identities within a communications environment to whom messages may be directed, associating a first persona of a user with a first functionality, associating a second persona of the same user with a second functionality, the second functionality differing from the first functionality, and enabling the first persona of the user to be projected to a first of the identities while concurrently enabling the second persona of the same user to be projected to a second of the identities.
Implementations may include one or more of the following features. For example, the first functionality may include encrypting messages sent by the user during an instant messaging communication session with the first of the identities and the second functionality may include not encrypting messages sent by the user dining an instant messaging communication session with the second of the identities. In another example, the first functionality includes decrypting messages received by the user during an instant messaging communication session with the first of the identities and the second functionality includes not decrypting messages received by the user during an instant messaging communication session with the second of the identities. In another example, the first functionality includes logging messages sent and received by the user during an instant messaging communication session with the first of the identities and the second functionality comprises not logging messages sent and received by the user during an instant messaging communication session with the second of the identities. The first functionality may include providing a notification concerning the message logging by the user to the first of the identities and the second functionality may include not providing a notification concerning the message logging by the user to the second of the identities.
In another example, the first functionality includes determining a routing of a message received by the user during an instant messaging communications with the first of the identities. Determining the routing may include determining a routing of the message over a communications mode other than the communications mode over which the message was received. The message may be routed using the determined routing. Routing the message may include forwarding the message to a different user, for example, via e-mail. The first functionality also may include providing a notification concerning the message routing to the first of the identities. Determining the routing may include determining the routing based upon an online presence state of the user. The second functionality may include not determining a routing of a message received by the user during an instant messaging communications with the second of the identities.
In another implementation, the first persona and the second persona each include at least one shared functionality. The shared functionality may include logging messages sent and received by the user during an instant messaging communication session with the first of the identities and the second of the identities, the first functionality may include encrypting messages sent by the user during an instant messaging communication session with the first of the identities and the second functionality may include not encrypting messages sent by the user during an instant messaging communication session with the second of the identities. The shared functionality also may include encrypting messages sent by the user during an instant messaging communication session with the first of the identities and the second of the identities, the first functionality may include logging messages sent and received by the user during an instant messaging communication session with the first of the identities, and the second functionality may include not logging messages sent and received by the user during an instant messaging communication session with the second of the identities.
In another implementation, the first persona is associated with a first group of identities such that the first persona is projected to members of the first group of identities in a communications session, where the first of the identities is included within the first group of identities. The second persona may be associated with a second group of identities such that the second persona is projected to members of the second group of identities in a communications session, where the second of the identities is included within the second group of identities.
In another implementation, an individual persona is associated with the first of the identities, a group persona is associated with a group of the identities with which the first of the identities is associated, and a global persona is associated with each of the identities, where the first persona projected to the first of the identities includes an amalgamation of the individual persona associated with the first of the identities, the group persona associated with the group of the identities, and the global persona associated with each of the identities. The individual persona associated with the first of the identities may override the group persona associated with the group of the identities and the group persona associated with the group of the identities may override the global persona associated with each of the identities, to the extent a conflict exists.
In one implementation, the communications session includes an instant messaging communications session, and the identities are members of a buddy list. The buddy list may include the online presence state of the identities.
In another implementation, the functionality of the first persona of the user is projected to the first of the identities while concurrently projecting the functionality of the second persona of the same user to the second of the identities. A selection may be made among the first and second personas for projection to a particular one of the identities based on an attribute of the particular identity. A selection of at least the first and second personas may be received from the user. The functionality of the first persona may be selected based upon an attribute of the first identity.
In another implementation, the functionality of the first persona assigned to the first identity may be configured to change based upon the occurrence of a predetermined event. The predetermined event may be based, for example, upon a time of day, a day of the week, or the passage of a pre-determined interval of time. The predetermined event may be, for example, a weather condition at a predetermined geographic location, communication of a predetermined word, communication of a predetermined emoticon, a predetermined date, or communication of a predetermined number of instant messages from the first identity.
Aspects of multiple personalities may be implemented by an apparatus and/or by a computer program stored on a computer readable medium. The computer readable medium may comprise a disc, a client device, a host device, and/or a propagated signal. In addition, aspects of the multiple personalities may be implemented in a client/host context or in a standalone or offline client device. The multiple personalities may be rendered in a client/host context and may be accessed or updated through a remote device in a client/host environment. The multiple personalities also may be rendered by the standalone/offline device and may be accessed or updated through a remote device in a non-client/host environment such as, for example, a LAN server serving an end user or a mainframe serving a terminal device.
Other features will be apparent from the following description, including the drawings, and from the claims.
For brevity, several elements in the figures described below are represented as monolithic entities. However, as would be understood by one skilled in the art, these elements each may include numerous interconnected computers and components designed to perform a set of specified operations and/or may be dedicated to a particular geographic region.
It is possible, through the systems and techniques described herein, to enable users to assemble one or more self-expression items into a collective “persona” or “personality,” which may then be saved and optionally associated with one or more customized names or groups of names. Self-expression items are used to represent the IM sender or a characteristic or preference of the IM sender, and may include user-selectable binary objects. The self-expression items may be made perceivable by a potential IM recipient (“IM recipient”) before, during, or after the initiation of communications by a potential IM sender (“IM sender”). For example, self-expression items may include images, such as wallpaper, that are rendered in a location having a contextual placement on a user interface. The contextual placement typically indicates an association with the user represented by the self-expression item. For instance, the wallpaper may be rendered in an area where messages from the IM sender are displayed, or as a chrome (i.e., border) around a dialog area on a user interface. Self-expression items also include icons such as buddy icons and mini-buddy icons, sounds, animation, video clips, and emoticons (e.g., smileys).
The personality may also include a set of features or functionality associated with the personality. For example, features such as encrypted transmission, IM conversation logging, and forwarding of instant messages to an alternative communication system may be enabled for a given personality. The features or functionality for one person may differ relative to another.
Users may assign personalities to be projected when conversing with other users, either in advance of or “on-the-fly” during a communication session. This allows the user to project different personalities to different people on-line. In particular, users may save one or more personalities (e.g., where each personality typically includes groups of instant messaging self-expression items such as, for example Buddy Icons, Buddy Sounds, Buddy Wallpaper, and Smileys, and/or a set of features and functionalities) and they may name those personalities to enable their invocation, they may associate each of different personalities with different users with whom they communicate or groups of such users so as to automatically display an appropriate/selected personality during communications with such other users or groups, or they may establish each of different personalities during this process of creating, adding or customizing lists or groups of users or the individual users themselves. Thus, the personalities may be projected to others in interactive online environments (e.g., Instant Messaging and Chat) according the assignments made by the user. Moreover, personalities may be assigned, established and/or associated with other settings, such that a particular personality may be projected based on time-of-day, geographic or virtual location, or even characteristics or attributes of each (e.g., cold personality for winter in Colorado or chatting personality while participating in a chat room).
When different functions are associated with each of several different personas, selection and projection of a persona to different buddies will invoke different functions with respect to the communications involving these buddies. For example, if a work persona with encrypted IM functionality is associated with the screen name of a co-worker and a home personality without encrypted IM functionality is associated with the screen name of a neighbor, then communications involving the co-worker will invoke encrypted IM functionality and communications involving the neighbor will not.
Moreover, it is possible for the user to maintain and project a consistent perceivable persona while invoking different functionality with respect to communications between different buddies. For example, aspects of a persona other than functionality may be chosen by the user to be the same. Thus, a user may assign encrypted IM functionality to the screen name of a co-worker and not assign encrypted IM functionality to the screen name of a neighbor. The user will present a consistent perceivable persona to both the co-worker and the neighbor, however different functionality will be associated with the communications with the co-worker and the neighbor. In particular, communications involving the co-worker will invoke encrypted IM functionality and communications involving the neighbor will not.
The IM buddy list 110 includes an IM sender-selected list 115 of potential instant messaging recipients (“buddies”). Buddies typically are contacts who are known to the potential instant message sender. The IM buddy list 110 may indicate to the IM sender whether or not one or more of the IM recipients on the buddy list are present, for instance, that they are or are not online and available for instant messaging communications. Buddies may be grouped by an IM sender into a user-defined or a pre-selected grouping (“groups”). As shown, the IM buddy list 110 has three categories of groups, Buddies 111, Co-Workers 112, and Family 113. At least two potential instant messaging recipients 115a, 115b are online. GabbyGrace00 115b belongs to the Buddies group 111, and ChattingChuck 115a belongs to the Co-Workers group 112.
The first IM UI 120 is rendered to the IM sender for an IM communications session with a first IM recipient, in this case ChattingChuck 115a. The first IM UI 120 includes self-expression items chosen by the IM sender to be projected to the first IM recipient 115a, such as a first buddy icon 137 and first IM wallpaper 138. The online persona defined for any particular IM, such as IM recipient 115a, includes the collection of self-expression items and/or features and functionalities. For example, the online persona may include one or more features giving a certain functionality for the IM communications session, such as automatic logging of IM conversations, encryption of IM messages, and forwarding of IM messages to another user such as an administrative assistant.
The first IM UI 120 includes an IM display and compose area 129 for composing IM messages to be sent to the first IM recipient 115a and for displaying a transcript of the IM communication session with the first IM recipient 115a. The IM display and compose area 129 also may display wallpaper that is consistent with or independent of wallpaper 138, the wallpaper within IM display and compose area 129 being selectable by the IM sender as part of the first persona.
The first IM UI 120 also includes a set of feature controls 130 and a set of transmission controls 145. The feature controls 130 may control features such as encryption, conversation logging, conversation forwarding to a different communications mode, font size and color control, and spell checking, among others. The set of transmission controls 145 includes a control 146 to send the message that was typed into the IM display and compose section 129, and a control 148 to check whether the potential IM recipient is available for IM communications.
Font and appearance controls may be provided in the feature controls 130 of IM UI 120 and configured as part of a particular persona to control how the message being entered in the IM display and compose area 129 is displayed in the IM display and compose area 129 as a transmitted message once the composed message in the IM display and compose area 129 is sent. The appearance of sent messages in the display may differ from the appearance of messages being composed in the display, but not yet sent. The display of first self-expression items 137, 138 in the first IM UI 120 enables the IM sender to conveniently perceive the online persona being projected to the particular IM recipient with whom the IM sender is presently communicating, which in this case is the first IM recipient, ChattingChuck 115a.
The second IM UI 150 is rendered to the IM sender for an IM communications session with a second IM recipient, which in this case is GabbyGrace00 115b, and has characteristics similar to those described above with respect to the first IM UI 120. However, the online persona projected by the IM sender to the second IM recipient 115b may differ from the online persona projected by the IM sender to the first IM recipient 115a, and similarly, the features and functions employed automatically with respect to the online persona for the second IM recipient 115b may be configured to differ from those employed automatically with respect to the first IM recipient 115a. For example, the persona projected to ChattingChuck 115a (the first persona) may be based on an association between the first persona and the group to which ChattingChuck 115a belongs, which in this case is the Co-Workers group 112. Or, as one alternative, the persona projected to ChattingChuck 115a may be based on an association between the persona and the individual IM recipient, i.e., ChattingChuck 115a. Similarly, the persona projected to GabbyGrace00 115b (the second persona) may be based on an association between the second persona and the group to which GabbyGrace00 115b belongs, which in this case is the Buddies group 111. Or, as one alternative, the persona projected to GabbyGrace00 115b may be based on an association between the persona and the individual IM recipient, i.e., GabbyGrace00 115b.
The second IM UI 150 includes self-expression items chosen by the IM sender to be projected to the second IM recipient 115b, such as a second buddy icon 167 and second IM wallpaper 168. The online persona defined for any particular IM recipient, such as IM recipient 115b, typically includes the collection of self-expression items, and may differ from the online persona projected to the first IM recipient 115a in the first IM UI 120. The online persona also may include features and functionality for the IM communications session with the second IM recipient 115b, such as automatic logging of IM conversations, encryption of IM messages, and forwarding of IM messages to another user such as an administrative assistant. The second IM UI 150 also includes an IM display and compose area 159 for composing IM messages to be sent to the second IM recipient 115b and for displaying a transcript of the IM communication session. The IM display and compose area 159 also may display wallpaper that is consistent with or independent of wallpaper 168, the wallpaper within IM display and compose area 159 being selected by the IM sender as part of the second persona.
The second IM UI 150 includes a set of feature controls 160, and a set of transmission controls 175. The feature controls 160 and transmission controls 175 have similar functionality to that described above with respect to the feature controls 130 and transmission controls 145 of the first IM UI 120. Font and appearance controls may be provided in the feature controls 160 of IM UI 150 and configured as part of a particular persona to control how the message being entered in the IM display and compose area 159 is displayed before and after the message in the IM display and compose area 159 is sent. The display of second self-expression items 167, 168 in the second IM UI 150 enables the IM sender to easily keep track of the online persona being projected to the particular IM recipient with whom the IM sender is communicating, which in this case is the second IM recipient, GabbyGrace00 115b.
An IM sender may create an online persona or personality from an IM sender-selected group or a pre-selected group of self-expression items and/or features and functionality. For example, an IM sender may separately choose a Buddy Icon, Sound, Wallpaper and Smiley and save the set of self-expression items as a personality with a given name, such as “Work,” “Social,” and “Rainy Day.” The IM sender may also select certain features and functionalities to be saved under the personality. For instance, the IM sender may choose to create and save for later invocation a “Social” personality by combining a Buddy Icon of a butterfly, a Buddy Sound of laughter, a Buddy Wallpaper of musical notes, and a Smiley set of beer mugs. The IM sender may also choose not to adopt any special features or functionality for this personality. The IM sender may configure their communications system to invoke their “Social” personality for only a subset of IM recipients and that personality perhaps being defined with less than all personalization items being specified such that aspects of the Social personality are amalgamated with aspects of one or more other personalities invoked during a communication sessions with a particular IM recipient. The IM sender also may configure their communications system to invoke their “Social” personality a upon the occurrence of predetermined event at the IM sender site such as, for example, a day of the week, a holiday, or a time of day. By way of illustration, if a persona invoked for an IM recipient includes a buddy icon and a buddy sound, that persona may be modified on a Friday evening through substitution of the Social personality Buddy Sound only, maintaining the buddy icon. User-specified rules can be used as a basis for determining whether/how to amalgamate situational personalities (e.g., the Social personality) with user-based personalities.
As a second example, the IM sender may create a “Work” personality by combining a Buddy Icon of a beaver, a Buddy Sound of a clock ticking, a Buddy Wallpaper of power tools, and a Smiley set of clock faces. This Work personality may also include features and functionality such that messages sent during invocation of the Work personality are encrypted and conversations are logged/recorded, automatically or by default.
The personalities created or adopted by the IM sender may have completely different self-expression settings, or may have some overlap in self-expression settings. The personalities also may have completely different features and functionality, or may have some overlap. In the exemplary personalities described above, for example, the IM sender could change the Buddy Wallpaper so that both the “Social” and the “Work” personalities have a Buddy Wallpaper of musical notes and both send encrypted messages. In another implementation, the IM sender could choose a pre-selected set of self-expression items, which may be related by a theme. For example, the theme may relate to a favorite football team and may include a buddy icon of the team mascot, buddy wallpaper of the team colors, and a buddy sound of an excerpt of the team fight song or appropriate sound from the team mascot. In one implementation, the themed persona could be purchased or leased by the IM sender.
As a third example, the IM sender may also select certain features and functionalities to be saved under a personality and triggered upon the occurrence of an event. For instance, the IM sender may choose to create and save for later invocation a “Rainy Day” personality by combining a Buddy Icon of an umbrella, a Buddy Sound of rain falling, a Buddy Wallpaper of clouds, and a Smiley set of raindrops. The IM sender may also choose not to adopt any special features or functionality for this personality. The IM sender may configure their communications system to invoke their “Rainy Day” personality when the environmental condition experienced at the IM sender site include rain, the Rainy Day personality perhaps being invoked for only a subset of IM recipients and that personality perhaps being defined with less than all personalization items being specified such that aspects of the Rainy Day personality are amalgamated with aspects of one or more other personalities invoked during a communication sessions with a particular IM recipient. By way of illustration, if a persona invoked for an IM recipient includes a buddy icon and a buddy sound, that persona may be modified on a Rainy Day through substitution of the Rainy Day personality Buddy Sound only, maintaining the buddy icon. User-specified rules can be used as a basis for determining whether/how to amalgamate situational personalities (e.g., the Rainy Day personality) with user-based personalities.
For example, the user may invoke settings so that the Rainy Day personality is be globally applied to all other personalities based on triggers unrelated to invocation by the user of a communication session with a particular user, or it may be associated with only a subset of users if desired.
An IM sender may create multiple different personalities, one or more of which may be assigned to one or different of particular IM recipients, or groups of several IM recipients defined by the user (e.g., within the Buddy List) or otherwise. For example, the IM sender may assign her “Social” personality to one or more of her family members, who may be, for example, in a “family” group 117 of buddies but may assign her more professional and upbeat “Work” Personality to a group identified as “co-workers” in her content or Buddy list to enable future application of the Work personality to each of the constituent office colleagues forming the co-worker group 119. The particular IM recipient or recipients will see the specific personality that the IM sender has assigned them whenever they converse with the IM sender online.
As an example, if the first IM recipient 115a has been assigned the “Social” personality, then the first IM UI 120 would display a first buddy icon 137 of a butterfly, first buddy wallpaper 138 of musical notes, and a buddy sound of laughter. By contrast, if the second IM recipient 115b has been assigned the “Work” personality, then the second IM UI 150 would display a second buddy icon 167 of a beaver, second buddy wallpaper 168 of power tools, and a buddy sound of clocks ticking.
Also, an IM sender may quickly assign personalities to a specific IM recipient or group of recipients or change or modify personalities with respect to a specific IM recipient or group of recipients during an instant messaging conversation. For example, the IM sender may use a chooser that is embedded in the conversation window. An IM sender also may change personalities within a chooser interface.
This approach provides an IM sender with the ability to, among other things, save groups of expressions and/or features and functionality with custom names, assign a personality to specific IM recipients or groups of IM recipients, and access and assign the personalities quickly, for example, an interface such as the instant messaging conversation window or the chooser interface.
Personalities may be assigned on a global basis, a group basis, and/or an individual (personal) basis. Also, the self-expression items may be assigned to personalities on a per-individual basis, a per-group basis or a global basis. In one implementation, self-expression items and/or features and functionality may be assigned on a “global” basis to all individuals, a “group” basis for individuals belonging to a particular group (e.g. friends, family, or co-workers), or an “individual” basis for a single individual IM recipient.
The persona may be changed by the IM sender before, during, or after an IM communication session with an IM recipient. In one implementation, the persona may change, or the user may be prompted to change, the persona after a pre-determined period of time or upon other conditions, such as a day of the week, a time of day, a holiday, a calendar event such as a birthday or wedding, a weekday, or a weekend day. In another implementation the persona, could change upon the occurrence of an event, such as a holiday or upon detecting certain language or emoticons in the IM conversation. In yet another implementation, the persona could change randomly.
Typically, IM communications involve an instantaneous or nearly instantaneous communication between two users, where each user is able to transmit, receive and display communicated information. Additionally, IM communications generally involve the display and perception of online presence information regarding other selected IM recipients. IM communications may be machine-to-machine communications that occur without intervention by or communication through an instant messaging server after a communication session is established or authentication is performed.
For illustrative purposes,
Referring to
The client device 220 and the host device 235 are generally capable of executing instructions under the command of, respectively, a client controller 225 and a host controller 240. The client device 220 and the host device 235 are connected to, respectively, the client controller 225 and the host controller 240 by, respectively, wired or wireless data pathways 230 and 245, which are capable of delivering data.
The client device 220, the client controller 225, the host device 235, and the host controller 240 typically each include one or more hardware components and/or software components. An example of a client device 220 or a host device 235 is a general-purpose computer (e.g., a personal computer) or software on such a computer capable of responding to and executing instructions in a defined manner. Other examples include a special-purpose computer, a workstation, a server, a device, a component, other physical or virtual equipment or some combination of these capable of responding to and executing instructions. The client device 220 and the host device 235 may include devices that are capable of establishing peer-to-peer communications.
An example of client controller 225 or host controller 240 is a software application loaded on the client device 220 or the host device 235 for commanding and directing communications enabled by the client device 220 or the host device 235. Other examples include a program, a piece of code, an instruction, a device, a computer, a computer system, or a combination of these for independently or collectively instructing the client device 220 or the host device 235 to interact and operate as described. The client controller 225 and the host controller 240 may be embodied permanently or temporarily in any type of machine, component, physical or virtual equipment, storage medium, or propagated signal capable of providing instructions to the client device 220 and the host device 235.
The communications link 215 typically includes a delivery network 260 that provides direct or indirect communication between the IM sender system 205 and the host system 210, irrespective of physical separation. Examples of a delivery network 260 include the Internet, the World Wide Web, WANs, LANs, analog or digital wired and wireless telephone networks (e.g., Public Switched Telephone Network (PSTN), Integrated Services Digital Network (ISDN), and Digital Subscriber Line (xDSL)), radio, television, cable, or satellite systems, and other delivery mechanisms for carrying data. The communications link 215 may include communication pathways 250 and 255 that enable communications through the one or more delivery networks 260 described above. Each of the communication pathways 250 and 255 may include, for example, a wired, wireless, cable or satellite communication pathway.
The IM sender system 205 includes a client device 220 that typically includes a general-purpose computer 370 having an internal or external memory 372 for storing data and programs such as an operating system 374 (e.g., DOS, WINDOWS, WINDOWS 95, WINDOWS 98, WINDOWS 2000, WINDOWS ME, WINDOWS XP, WINDOWS NT, OS/2, or LINUX) and one or more application programs. Examples of application programs include authoring applications 376 (e.g., word processing programs, database programs, spreadsheet programs, or graphics programs) capable of generating documents or other electronic content; client applications 378 (e.g., AMERICA ONLINE (AOL) client, COMPUSERVE client, AOL INSTANT MESSENGER (AIM) client, interactive television (ITV) client, Internet Service Provider (ISP) client, or instant messaging (IM) client) capable of communicating with other computer users, accessing various computer resources, and viewing, creating, or otherwise manipulating electronic content; and browser applications 380 (e.g., NETSCAPE NAVIGATOR or INTERNET EXPLORER from MICROSOFT) capable of rendering standard Internet content and other content formatted according to standard protocols such as the Hypertext Transfer Protocol (HTTP).
One or more of the application programs may be installed on the internal or external storage 372 of the general-purpose computer 370. Alternatively, in another implementation, the client controller 225 may access application programs externally stored in and/or performed by one or more device(s) external to the general-purpose computer 370.
The general-purpose computer 370 also includes a central processing unit 382 (CPU) for executing instructions in response to commands from the client controller 225, and a communication device 384 for sending and receiving data. One example of the communication device 384 is a modem. Other examples include a transceiver, a set-top box, a communication card, a satellite dish, an antenna, a network adapter, or some other mechanism capable of transmitting and receiving data over the communications link 215 through a wired or wireless data pathway 250. The general-purpose computer 370 optionally includes a television (“TV”) tuner 386 for receiving television programming in the form of broadcast, satellite, and/or cable TV signals. The TV tuner 386 permits the client device 220 to selectively and/or simultaneously display network content received by communications device 384 and TV programming content received by the TV tuner 386.
The general-purpose computer 370 may include an input/output interface 388 that enables wired or wireless connection to various peripheral devices 390. Examples of peripheral devices 390 include, but are not limited to, a mouse 391, a mobile phone 392, a personal digital assistant (PDA) 393, an MP3 player (not shown), a keyboard 394, a display monitor 395 with or without a touch screen input, a TV remote control 396 for receiving information from and rendering information to users, and an audiovisual input device 398.
Although
In one implementation, the IM host system 410 may have characteristics similar to those described above with respect to the host system 210, the IM recipient system 405 may have characteristics similar to those described above with respect to the IM sender system 205, and the IM sender system 205 and the IM recipient system 405 may include communication software to enable users of the client systems to access the IM host system 410.
The IM host system 410 may support IM services irrespective of an IM sender's network or Internet access. Thus, the IM host system 410 may allow users to send and receive IMs, regardless of whether they have access to any particular ISP. The IM host system 410 also may support associated services, such as administrative matters, advertising, directory services, chat, and interest groups related to the IM. The IM host system 410 has an architecture that enables the devices (e.g., servers) within the IM host system 410 to communicate with each other. To transfer data, the IM host system 410 employs one or more standard or proprietary IM protocols.
To access the IM host system 410 to begin an IM session in the implementation of
Once connectivity is established, an IM sender who is using IM sender system 205 may view whether an IM recipient using IM recipient system 405 is online, and typically may view whether the IM recipient is able to receive IMs. If the IM recipient is online, the IM sender may exchange IMs with the IM recipient.
Furthermore, the IM sender may view or perceive certain aspects of a personality selected by a potential IM recipient prior to engaging in communications with that potential IM recipient. For example, certain aspects of an IM recipient selected personality, such as a buddy icon or a miniature buddy icon chosen by the IM recipient, may be perceivable through the buddy list itself prior to engaging in communications. Other aspects of a selected personality chosen by an IM recipient may be made perceivable upon opening of a communication window by the IM sender for a particular IM recipient but prior to initiation of communications.
In one implementation, the IMs sent between IM sender system 205 and IM recipient system 405 are routed through IM host system 410. In another implementation, the IMs sent between IM sender system 205 and IM recipient system 405 are routed through a third party server (not shown), and, in some cases, are also routed through IM host system 410. In yet another implementation, the IMs are sent directly between IM sender system 205 and IM recipient system 405.
As shown in
The procedure 500 may be implemented in a client/host context, or a standalone or offline client context. For example, while some functions of procedure 500 may be performed entirely by the IM sender system 205, other functions may be performed by host system 210, or the collective operation of the IM sender system 205 and the host system 210. In procedure 500, the online persona may be respectively selected and rendered by the standalone/offline device, and the online persona may be accessed or updated through a remote device in a non-client/host environment such as, for example, a LAN server serving an end user or a mainframe serving a terminal device. Thus, the procedure 500 described below may be implemented for an OSP, ISP, browser and/or other software program having a graphical user interface, such as programs for instant messaging, chat, electronic mail and stand-alone browsers. Moreover, procedure 500 may be implemented by hardware, software, devices, computers, computer systems, equipment, components, programs, applications, code, storage media, or propagated signals.
Procedure 500 generally involves selecting and projecting an online persona. The IM sender creates or modifies one or more online personalities (step 505). As discussed above with respect to
In
The list of IM recipients displayed in box 910 of user interface 905 typically is referred to as the buddy list. In the buddy list, IM recipients are grouped together into buddy groups. The name or representation of each buddy group is displayed in the buddy list. When a buddy's IM 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. For example, in the interface shown by
In creating personalities, the IM sender may forbid a certain personality to be shown to designated IM recipients and/or groups. For example, if the IM sender wants to ensure that the “Casual” personality is not accidentally displayed to the boss or to co-workers, the IM sender may prohibit the display of the “Casual” personality to the boss on an individual basis, and may prohibit the display of the “Casual” personality to the “Co-workers” group on a group basis. An appropriate user interface may be provided to assist the IM sender in making such a selection. Similarly, the IM sender may be provided an option to “lock” a personality to a IM recipient or a group of IM recipients to guard against accidental or unintended personality switching and/or augmenting. Thus, for example, the IM sender may choose to lock the “Work” personality to the boss on an individual basis, or to lock the “Work” personality to the “Co-workers” group on a group basis. In one example, the Casual personality will not be applied to a locked personality. A UI may be provided to assist the IM sender in making such a selection.
In another implementation, the features or functionality of the IM interface may vary based upon user-selected or pre-selected options for the personality selected or currently in use. The features or functionality may be transparent to the IM sender. For example, when using the “Work” personality, the outgoing IM messages may be encrypted, and a copy may be recorded in a log, or a copy may be forwarded to a designated contact such as an administrative assistant. A warning may be provided to an IM recipient that the IM conversation is being recorded or viewed by others, as appropriate to the situation. By comparison, if the non-professional “Casual” personality is selected, the outgoing IM messages may not be encrypted and no copy is recorded or forwarded.
As a further example, if the “Work” personality is selected and the IM sender indicates an unavailability to receive instant messages (e.g., through selection of an “away” message or by going offline), then messages received from others during periods of unavailability may be forwarded to another IM recipient such as an administrative assistant, or may be forwarded to an e-mail address for the IM sender. By comparison, if the non-professional “Casual” personality is selected, no extra measures are taken to ensure delivery of the message.
In one implementation, the features and functionality associated with the personality would be transparent to the IM sender, and may be based upon one or more pre-selected profiles types when setting up the personality. For example, the IM sender may be asked to choose from a group of personality types such as professional, management, informal, vacation, offbeat, etc. In the example above, the “Work” personality may have been be set up as a “professional” personality type and the “Casual” personality may have been set up as an “informal” personality type. In another implementation, the IM sender may individually select the features and functionalities associated with the personality.
An “enterprise mode” may be provided for use with a personality, and the features and functionality associated with the enterprise mode may be established by an employer or its agent, and may vary depending upon the requirements of the environment. For example, where a record of the IM conversation is being maintained, a legal notice may be provided to one or more of the participants in the IM conversation, where such notice is necessary or desirable. The enterprise mode may enable functionality such as encryption, recording of the IM conversation, and forwarding of the IM conversation to an administrative assistant.
In one implementation, the IM recipient and/or the IM sender may pay a subscription fee to access/use certain personalities, and the personalities may be provided by a third party. In another implementation, the personalities expire and must be replaced after a predetermined event such as a predetermined length of time, passage of a predetermined date, or a predetermined number of uses. Also, a personality may be banned if, for example, it is deemed to be offensive, inappropriate, or to otherwise violate a term of service agreement. If it is determined that the personality is expired or banned, display of such a personality will be disallowed and the IM sender typically will be required to choose a different personality.
Default global personalization items, default group personalization items, or default personal personalization items, may be provided, depending on the implementation. For example, if the Buddies buddy group is provided as a default upon installation of the instant messaging client program, a default group personalization item also may be provided for the Buddies buddy group. As another example, a default global personalization item may be provided when the instant messaging client program is installed so that a personalization item always exists for the IM recipients, regardless of whether a IM sender has selected a personality or personalization item to be presented. Similarly, a default group personalization item may be provided for any default buddy groups and newly created buddy groups, whether or not a global personalization item is provided. This enables a personality to always exist for IM recipients even when no global personalization item or personality exists, regardless of whether a IM sender has set a group personalization item (or personal personalization item, if implemented also). Features and functionality may be assigned to personalities in a similar manner as described with respect to self-expression items.
Referring again to
Next the IM sender assigns a personality to be projected during future IM sessions or when engaged in future IM conversations with an IM recipient (step 515). The IM sender may wish to display different personalities to different IM recipients and/or groups in the buddy list. The IM sender may use a user interface to assign personalization items to personalities on at least a per-buddy group basis. For example, an IM sender may assign a global buddy icon to all personalities, but assign different buddy sounds on a per-group basis to other personalities (e.g. work, family, friends), and assign buddy wallpaper and smileys on an individual basis to individual personalities corresponding to particular IM recipients within a group. The IM sender may assign other personality attributes based upon the occurrence of certain predetermined events or triggers. For example, certain potential IM recipients may be designated to see certain aspects of the Rainy Day personality if the weather indicates rain at the geographic location of the IM sender. Default priority rules may be implemented to resolve conflicts, or the user may select priority rules to resolve conflicts among personalities being projected or among self-expression items being projected for an amalgamated personality.
For example, a set of default priority rules may resolve conflicts among assigned personalities by assigning the highest Priority to personalities and self-expression items of personalities assigned on an individual basis, assigning the next highest priority to assignments of personalities and personalization items made on a group basis, and assigning the lowest priority to assignments of personalities and personalization items made on a global basis. However, the user may be given the option to override these default priority rules and assign different priority rules for resolving conflicts.
As shown in
In particular, the global or default controls 1315 may include a drop down menu 1316 to enable the IM sender to select a default persona and may include one or more self-expression drop down menus 1317 to enable the IM sender to select one or more default personalization items to be projected. The group controls 1320 may include a drop down menu 1321 to enable the IM sender to select a persona to be projected to a group and may include one or more self-expression drop down menus 1322 to enable the IM sender to select one or more personalization items to be projected to a group. Association arrows 1323 and a Group list 1324 may be used to match the selected persona and/or self-expression items with a particular group. The individual controls 1325 may include a drop down menu 1326 to enable the IM sender to select a persona to be projected to an individual and may include one or more self-expression drop down menus 1327 to enable the IM sender to select one or more personalization items to be projected to an individual. Association arrows 1328 and an Individual list 1329 may be used to match the selected persona and/or self-expression items with a particular individual. The other criteria controls 1330 may include a drop down menu 1331 to enable the IM sender to select a type of criteria or trigger, a drop down menu 1332 to enable the IM sender to select a persona to be projected based upon other criteria and may include one or more self-expression drop down menus 1333 to enable the IM sender to select one or more personalization items to be projected based on other criteria. The other criteria may include, for example, weather at the IM sender location, a day of the week, a time of day, a holiday, a calendar event, a week day or a weekend day.
The priority rules portion 1310A includes priority rule controls 1340 to enable the IM sender to select priority rules to resolve conflicts between personas or self-expression items or functionality within personas. The controls 1340 may include a drop down menu 1341 to choose pre-defined sets of rules or a UI control 1342 to enable the user to define custom priority rules.
As shown in
In particular, the global or default controls 1350 may include a drop down menu 1351 to enable the IM sender to select a default persona and may include one or more functionality menu items 1355 to enable the IM sender to select one or more default functionalities to be projected with the persona. The group controls 1360 may include a drop down menu 1361 to enable the IM sender to select a persona to be projected to a group and may include one or more functionality menu items 1365 to enable the IM sender to select one or more functionalities to be projected with the persona to a group. Association arrows 1367 and a Group list 1369 may be used to match the selected persona and/or functionalities with a particular group. The individual controls 1370 may include a drop down menu 1371 to enable the IM sender to select a persona to be projected to an individual and may include one or more functionality menu items 1375 to enable the IM sender to select one or more functionalities to be projected with the persona to an individual. Association arrows 1377 and an Individual list 1379 may be used to match the selected persona and/or functionalities with a particular individual. The other criteria controls 1380 may include a drop down menu 1381 to enable the IM sender to select a type of criteria or trigger, a drop down menu 1382 to enable the IM sender to select a persona to be projected based upon other criteria and may include one or more functionality menu items 1385 to enable the IM sender to select one or more functionalities to be projected with the persona based on other criteria. The other criteria may include, for example, weather at the IM sender location, a day of the week, a time of day, a holiday, a calendar event, a week day or a weekend day.
The priority rules portion 1310B includes priority rule controls 1390 to enable the IM sender to select priority rules to resolve conflicts between personas or functionality within personas. The controls 1390 may include a drop down menu 1391 to choose pre-defined sets of rules or a UI control 1392 to enable the user to define custom priority rules.
To set a personality for a buddy-group, the IM sender may use the interface to select the buddy group and assign the personality that will be presented to all IM recipients that belong to the selected buddy group. In other implementations, the IM sender may be able to use the interface to set a global personalization item and/or personality on a per-buddy basis. A global personalization item is typically implemented as a default personalization item sent to a buddy if no other type of personalization item (e.g., buddy icon, buddy wallpaper, buddy sound, or smiley) is set for the buddy on a group or an individual basis. A personalization item may be set for a particular group and used for members of the group, or may be set for an individual buddy and used for that buddy. Typically, an individual (personal) personalization item selection overrides a selection for a group personalization item, and a group personalization item selection overrides a selection for a global personalization item. Similarly, an individual (personal) personality selection overrides a selection for a group personality, and a group personality selection overrides a selection for a global personality.
In some implementations that allow for global personalization items, the group personalization item set for a buddy group optionally may be set by overriding the global personalization item with a new personalization item. For example, if the global buddy icon is set to a bear, and a buddy group personalization item for the “co-worker” group may be set to a beaver, the personalization item presented to IM recipients in the “co-worker” buddy group would be a beaver, while the personalization item presented to IM recipients in other groups would default to the global buddy icon, a bear. Similarly, in some implementations, an individual (personal) personalization item may be set by overriding a group personalization item or a global personalization item for particular IM recipients.
Next, an IM session between the IM sender and the IM recipient is initiated (step 520). The IM session may be initiated by either the IM sender or the IM recipient.
An IM UI is rendered to the IM recipient, configured to project the personality assigned to the IM recipient by the IM sender (step 525), as illustrated, for example, by
The appropriate personality/personalization item set for a buddy is sent to the buddy when the buddy communicates with the IM sender through the instant messaging client program. For example, in an implementation which supports global personalization items, group personalization items, and personal personalization items, a personal personalization item is sent to the buddy if set, otherwise a group personalization item is sent, if set. If neither a personal nor a group personalization item is set, then the global personalization item is sent. As another example, in an implementation that supports global personalization items and group personalization items, the group personalization item for the group to which the buddy belongs is sent, if set, otherwise the global personalization item is sent. In an implementation that only supports group personalization items, the group personalization item for the group to which the buddy belongs is sent to the buddy.
An IM session between the IM sender and another IM recipient also may be initiated (step 530) by either the IM sender or the second IM recipient.
Relative to the second IM session, a second IM UI is rendered to the second IM recipient, configured to project the personality assigned to the second IM recipient by the IM sender (step 535), as illustrated by
Referring to
Next, the updated UI for that buddy is updated based on the newly selected personality (step 610).
In system 1400, the IM host system 410 includes a login server 1470 for enabling access by IM senders and routing communications between the IM sender system 205 and other elements of the IM host system 410. The IM host system 410 also includes an IM server 1490. To enable access to and facilitate interactions with the IM host system 410, the IM sender system 205 and the IM recipient system 405 may include communication software, such as for example, an OSP client application and/or an IM client application.
As described with respect to
In one implementation, the IM sender system 205 establishes a connection to the login server 1470 in order to access the IM host system 410 and begin an IM session. The login server 1470 typically determines whether the particular IM sender is authorized to access the IM host system 410 by verifying the IM sender's identification and password. If the IM sender is authorized to access the IM host system 410, the login server 1470 usually employs a hashing technique on the IM sender's screen name to identify a particular IM server 1490 within the IM host system 410 for use during the IM sender's session. The login server 1470 provides the IM sender (e.g., IM sender system 205) with the IP address of the IM server 1490, gives the IM sender system 205 an encrypted key, and breaks the connection. The IM sender system 205 then uses the IP address to establish a connection to the particular IM server 1490 through the communications link 215, and obtains access to the IM server 1490 using the encrypted key. Typically, the IM sender system 205 will be able to establish an open TCP connection to the IM server 1490. The IM recipient system 405 establishes a connection to the IM host system 310 in a similar manner.
In one implementation, the IM sender system 205 may directly or indirectly transmit data to and access content from the IM server 1490 once a connection to the IM server 1490 has been established. By accessing the IM server, an IM sender can leverage the IM client application to determine whether particular IM senders (“buddies” or potential IM recipients) are online, exchange IMs with particular IM recipients, participate in group chat rooms, trade files such as pictures, invitations or documents, find other IM recipients with similar interests, get customized news and stock quotes, and search the Web. For example an IM sender who is using IM sender system 205 may view whether a buddy using IM recipient system 405 is online, and if so, may exchange IMs with that buddy. In one implementation, the IMs sent between IM sender system 205 and IM recipient system 405 are routed through IM host system 410. In another implementation, the IMs sent between IM sender system 205 and IM recipient system 405 are routed through a third party server (not shown) and, in some cases, are also routed through IM host system 410. In yet another implementation, the IMs are sent directly between IM sender system 205 and IM recipient system 405.
In one implementation, the IM host system 410 also includes a user profile server (not shown) connected to a database (not shown) for storing large amounts of user profile data. The user profile server may be used to enter, retrieve, edit, manipulate, or otherwise process user profile data. In one implementation, an IM sender's profile data includes, for example, the IM sender's screen name, buddy list, identified interests, and geographic location. The IM sender's profile data may also include self-expression items selected by the IM sender. The IM sender may enter, edit and/or delete profile data using an installed IM client application on the IM sender system 205 to interact with the user profile server.
Because the IM sender's data are stored in the IM host system 410, the IM sender does not have to reenter or update such information in the event that the IM sender accesses the IM host system 410 using a new or different IM sender system 205. Accordingly, when an IM sender accesses the IM host system 410, the IM server can instruct the user profile server to retrieve the IM sender's profile data from the database and to provide, for example, the IM sender's self-expression items and buddy list to the IM server. Alternatively, user profile data may be saved locally on the IM sender system 205.
Instant messaging programs typically allow IM senders to communicate in real-time with each other in a variety of ways. For example, many instant messaging programs allow IM senders to send text as an instant message, to transfer files, and to communicate by voice. Examples of IM communications exist over AIM (AMERICA ONLINE INSTANT MESSENGER), AOL (AMERICA ONLINE) BUDDY LIST and INSTANT MESSENGER, YAHOO MESSENGER, MSN MESSENGER, and ICQ, among others. Although discussed above primarily with respect to IM applications, other implementations are contemplated for providing similar functionality in platforms and online applications such as chat, e-mail, and streaming media applications.
Other implementations are within the scope of the following claims. For example, although the examples above are given in an instant message context, other communications systems with similar attributes may be used. For example, multiple personalities may be used in a chat room or in e-mail communications. Also, the user interface may be a viewable interface, an audible interface, a tactile interface, or a combination of these.
| Number | Date | Country | Kind |
|---|---|---|---|
| PCT/US03/36796 | Nov 2003 | WO | international |
This application is a continuation of U.S. application Ser. No. 10/847,463, filed May 18, 2004 (now U.S. Pat. No. 8,037,150), which is a continuation-in-part of U.S. application Ser. No. 10/715,209, filed Nov. 18, 2003 (now U.S. Pat. No. 7,636,751), and claims priority from U.S. Provisional Application No. 60/427,941, filed Nov. 21, 2002, International Application No. PCT/US03/36796, filed Nov. 18, 2003, U.S. Provisional Application No. 60/464,106, filed Apr. 21, 2003, and U.S. Provisional Application No. 60/488,399, filed Jul. 21, 2003, all of which are hereby incorporated by reference.
| Number | Name | Date | Kind |
|---|---|---|---|
| 4837798 | Cohen et al. | Jun 1989 | A |
| 5086394 | Shapira | Feb 1992 | A |
| 5276905 | Hurst et al. | Jan 1994 | A |
| 5327486 | Wolff et al. | Jul 1994 | A |
| 5388202 | Squires et al. | Feb 1995 | A |
| 5548637 | Heller et al. | Aug 1996 | A |
| 5557659 | Hyde-Thomson | Sep 1996 | A |
| 5608786 | Gordon | Mar 1997 | A |
| 5657462 | Brouwer et al. | Aug 1997 | A |
| 5659692 | Poggio et al. | Aug 1997 | A |
| 5675752 | Scott et al. | Oct 1997 | A |
| 5694616 | Johnson et al. | Dec 1997 | A |
| 5710884 | Dedrick | Jan 1998 | A |
| 5721827 | Logan et al. | Feb 1998 | A |
| 5721906 | Siefert | Feb 1998 | A |
| 5740549 | Reilly et al. | Apr 1998 | A |
| 5742905 | Pepe et al. | Apr 1998 | A |
| 5745556 | Ronen | Apr 1998 | A |
| 5761662 | Dasan | Jun 1998 | A |
| 5774670 | Montulli | Jun 1998 | A |
| 5793365 | Tang et al. | Aug 1998 | A |
| 5796948 | Cohen | Aug 1998 | A |
| 5802470 | Gaulke et al. | Sep 1998 | A |
| 5812126 | Richardson et al. | Sep 1998 | A |
| 5835722 | Bradshaw et al. | Nov 1998 | A |
| 5848396 | Gerace | Dec 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, Jr. et al. | Mar 1999 | A |
| 5880731 | Liles et al. | Mar 1999 | A |
| 5884029 | Brush et al. | Mar 1999 | A |
| 5889953 | Thebaut et al. | Mar 1999 | A |
| 5893091 | Hunt et al. | Apr 1999 | A |
| 5893099 | Schrieber et al. | Apr 1999 | A |
| 5894305 | Needham | Apr 1999 | A |
| 5920692 | Nguyen et al. | Jul 1999 | A |
| 5940488 | DeGrazia et al. | Aug 1999 | A |
| 5944780 | Chase et al. | Aug 1999 | A |
| 5946617 | Portaro et al. | Aug 1999 | A |
| 5948058 | Kudoh et al. | Sep 1999 | A |
| 5951643 | Shelton et al. | Sep 1999 | A |
| 5951652 | Ingrassia, Jr. et al. | Sep 1999 | A |
| 5954798 | Shelton et al. | Sep 1999 | A |
| 5960173 | Tang et al. | Sep 1999 | A |
| 5963217 | Grayson et al. | Oct 1999 | A |
| 5987113 | James | Nov 1999 | A |
| 5987415 | Breese et al. | Nov 1999 | A |
| 5991791 | Siefert | Nov 1999 | A |
| 5995023 | Kreft | Nov 1999 | A |
| 6002402 | Schacher | Dec 1999 | A |
| 6009413 | Webber et al. | Dec 1999 | A |
| 6012051 | Sammon, Jr. et al. | Jan 2000 | A |
| 6014135 | Fernandes | Jan 2000 | A |
| 6014638 | Burge et al. | Jan 2000 | A |
| 6026403 | Siefert | Feb 2000 | A |
| 6026429 | Jones et al. | Feb 2000 | A |
| 6049533 | Norman et al. | Apr 2000 | A |
| 6065047 | Carpenter et al. | May 2000 | A |
| 6069622 | Kurlander | May 2000 | A |
| 6073138 | de l'Etraz et al. | Jun 2000 | A |
| 6081830 | Schindler | Jun 2000 | A |
| 6085223 | Carino, Jr. et al. | Jul 2000 | A |
| 6088435 | Barber et al. | Jul 2000 | A |
| 6091410 | Lection et al. | Jul 2000 | A |
| 6115709 | Gilmour | Sep 2000 | A |
| 6128618 | Eliovson | Oct 2000 | A |
| 6128739 | Fleming | Oct 2000 | A |
| 6134432 | Holmes et al. | Oct 2000 | A |
| 6151571 | Pertrushin | Nov 2000 | A |
| 6151584 | Papiernak et al. | Nov 2000 | A |
| 6161130 | Horvitz et al. | Dec 2000 | A |
| 6166730 | Goode et al. | Dec 2000 | A |
| 6175831 | Weinreich et al. | Jan 2001 | B1 |
| 6185614 | Cuomo et al. | Feb 2001 | B1 |
| 6189790 | Walter | Feb 2001 | B1 |
| 6192396 | Kohler | Feb 2001 | B1 |
| 6199103 | Sakaguchi et al. | Mar 2001 | B1 |
| 6205432 | Gabbard et al. | Mar 2001 | B1 |
| 6205478 | Sugano et al. | Mar 2001 | B1 |
| 6212550 | Segur | Apr 2001 | B1 |
| 6219045 | Leahy et al. | Apr 2001 | B1 |
| 6227974 | Eilat et al. | May 2001 | B1 |
| 6232966 | Kurlander | May 2001 | B1 |
| 6247043 | Bates et al. | Jun 2001 | B1 |
| 6248946 | Dwek | Jun 2001 | B1 |
| 6249740 | Ito et al. | Jun 2001 | B1 |
| 6249743 | Ohshimo | Jun 2001 | B1 |
| 6252588 | Dawson | Jun 2001 | B1 |
| 6252952 | Kung et al. | Jun 2001 | B1 |
| 6253202 | Gilmour | Jun 2001 | B1 |
| 6256633 | Dharap | Jul 2001 | B1 |
| 6260148 | Aggarwal et al. | Jul 2001 | B1 |
| 6268872 | Matsuda et al. | Jul 2001 | B1 |
| 6269369 | Robertson | Jul 2001 | B1 |
| 6301609 | Aravamudan et al. | Oct 2001 | B1 |
| 6311211 | Shaw et al. | Oct 2001 | B1 |
| 6314450 | Hachiya et al. | Nov 2001 | B1 |
| 6324541 | de l'Etraz et al. | Nov 2001 | B1 |
| 6324569 | Ogilvie et al. | Nov 2001 | B1 |
| 6329986 | Cheng | Dec 2001 | B1 |
| 6330590 | Cotton | Dec 2001 | B1 |
| 6331853 | Miyashita | Dec 2001 | B1 |
| 6346952 | Shtivelman | Feb 2002 | B1 |
| 6346956 | Matsuda | Feb 2002 | B2 |
| 6347332 | Malet et al. | Feb 2002 | B1 |
| 6349327 | Tang et al. | Feb 2002 | B1 |
| 6351698 | Kubota et al. | Feb 2002 | B1 |
| 6363392 | Halstead et al. | Mar 2002 | B1 |
| 6373817 | Kung et al. | Apr 2002 | B1 |
| 6374237 | Reese | Apr 2002 | B1 |
| 6374246 | Matsuo | Apr 2002 | B1 |
| 6374290 | Scharber et al. | Apr 2002 | B1 |
| 6389028 | Bondarenko et al. | May 2002 | B1 |
| 6389127 | Vardi et al. | May 2002 | B1 |
| 6389372 | Glance et al. | May 2002 | B1 |
| 6400381 | Barrett et al. | Jun 2002 | B1 |
| 6401085 | Gershman et al. | Jun 2002 | B1 |
| 6415318 | Aggarwal et al. | Jul 2002 | B1 |
| 6421439 | Liffick | Jul 2002 | B1 |
| 6421709 | McCormick et al. | Jul 2002 | B1 |
| 6425012 | Trovato et al. | Jul 2002 | B1 |
| 6430604 | Ogle et al. | Aug 2002 | B1 |
| 6434599 | Porter | Aug 2002 | B1 |
| 6446112 | Bunney et al. | Sep 2002 | B1 |
| 6449344 | Goldfinger et al. | Sep 2002 | B1 |
| 6449634 | Capiel | Sep 2002 | B1 |
| 6453294 | Dutta et al. | Sep 2002 | B1 |
| 6466213 | Bickmore et al. | Oct 2002 | B2 |
| 6466232 | Newell et al. | Oct 2002 | B1 |
| 6480885 | Olivier | Nov 2002 | B1 |
| 6484196 | Maurille | Nov 2002 | B1 |
| 6487584 | Bunney | Nov 2002 | B1 |
| 6499021 | Abu-Hakima | Dec 2002 | B1 |
| 6501834 | Milewski et al. | Dec 2002 | B1 |
| 6507866 | Barchi | Jan 2003 | B1 |
| 6512525 | Capps et al. | Jan 2003 | B1 |
| 6525747 | Bezos | Feb 2003 | B1 |
| 6530083 | Liebenow | Mar 2003 | B1 |
| 6535586 | Cloutier et al. | Mar 2003 | B1 |
| 6539375 | Kawasaki | Mar 2003 | B2 |
| 6539421 | Appelman et al. | Mar 2003 | B1 |
| 6542750 | Hendrey et al. | Apr 2003 | B2 |
| 6545682 | Ventrella et al. | Apr 2003 | B1 |
| 6549937 | Auerbach et al. | Apr 2003 | B1 |
| 6557027 | Cragun | Apr 2003 | B1 |
| 6559863 | Megiddo | May 2003 | B1 |
| 6560588 | Minter | May 2003 | B1 |
| 6571234 | Knight et al. | May 2003 | B1 |
| 6580790 | Henry et al. | Jun 2003 | B1 |
| 6584494 | Manabe et al. | Jun 2003 | B1 |
| 6587127 | Leeke et al. | Jul 2003 | B1 |
| 6606647 | Shah et al. | Aug 2003 | B2 |
| 6615241 | Miller et al. | Sep 2003 | B1 |
| 6629793 | Miller | Oct 2003 | B1 |
| 6630944 | Kakuta et al. | Oct 2003 | B1 |
| 6633850 | Gabbard et al. | Oct 2003 | B1 |
| 6636733 | Helferich | Oct 2003 | B1 |
| 6640229 | Gilmour et al. | Oct 2003 | B1 |
| 6640230 | Alexander et al. | Oct 2003 | B1 |
| 6654683 | Jin et al. | Nov 2003 | B2 |
| 6654735 | Eichstaedt et al. | Nov 2003 | B1 |
| 6671682 | Nolte et al. | Dec 2003 | B1 |
| 6677968 | Appelman | Jan 2004 | B1 |
| 6678719 | Stimmel | Jan 2004 | B1 |
| 6691162 | Wick | Feb 2004 | B1 |
| 6694375 | Beddus et al. | Feb 2004 | B1 |
| 6697807 | McGeachie | Feb 2004 | B2 |
| 6701348 | Sommerer | Mar 2004 | B2 |
| 6708203 | Makar et al. | Mar 2004 | B1 |
| 6708205 | Sheldon et al. | Mar 2004 | B2 |
| 6714791 | Friedman | Mar 2004 | B2 |
| 6714793 | Carey et al. | Mar 2004 | B1 |
| 6725048 | Mao et al. | Apr 2004 | B2 |
| 6731307 | Strubbe et al. | May 2004 | B1 |
| 6731308 | Tang et al. | May 2004 | B1 |
| 6731323 | Doss et al. | May 2004 | B2 |
| 6732155 | Meek | May 2004 | B2 |
| 6748326 | Noma et al. | Jun 2004 | B1 |
| 6748626 | Maurer | Jun 2004 | B2 |
| 6750881 | Appelman | Jun 2004 | B1 |
| 6757365 | Bogard | Jun 2004 | B1 |
| 6772188 | Cloutier | Aug 2004 | B1 |
| 6772195 | Hatlelid et al. | Aug 2004 | B1 |
| 6781608 | Crawford | Aug 2004 | B1 |
| 6784901 | Harvey et al. | 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 |
| 6798426 | Tateishi | 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 |
| 6839797 | Calle et al. | Jan 2005 | B2 |
| 6874127 | Newell et al. | Mar 2005 | B2 |
| 6876728 | Kredo et al. | Apr 2005 | B2 |
| 6879994 | Matsliach et al. | Apr 2005 | B1 |
| 6901559 | Blum et al. | May 2005 | B1 |
| 6904026 | Tarnanen et al. | Jun 2005 | B1 |
| 6907243 | Patel | Jun 2005 | B1 |
| 6907571 | Slotznick | Jun 2005 | B2 |
| 6910186 | Kim | Jun 2005 | B2 |
| 6912563 | Parker et al. | Jun 2005 | B1 |
| 6912564 | Appelman et al. | Jun 2005 | B1 |
| 6917965 | Gupta et al. | Jul 2005 | B2 |
| 6922685 | Greene et al. | Jul 2005 | B2 |
| 6941345 | Kapil et al. | Sep 2005 | B1 |
| 6948131 | Neven et al. | Sep 2005 | B1 |
| 6954902 | Noma et al. | Oct 2005 | B2 |
| 6961755 | Matsuda | Nov 2005 | B2 |
| 6968179 | De Vries | Nov 2005 | B1 |
| 6976092 | Daniell et al. | Dec 2005 | B1 |
| 6976267 | Takano et al. | Dec 2005 | B1 |
| 6979267 | Leen et al. | Dec 2005 | B2 |
| 6981223 | Becker et al. | Dec 2005 | B2 |
| 6983305 | Danker et al. | Jan 2006 | B2 |
| 6993564 | Whitten, II | Jan 2006 | B2 |
| 7006098 | Bickmore et al. | Feb 2006 | B2 |
| 7007065 | Matsuda | Feb 2006 | B2 |
| 7035803 | Ostermann et al. | Apr 2006 | B1 |
| 7035863 | Kurapati et al. | Apr 2006 | B2 |
| 7035865 | Doss et al. | Apr 2006 | B2 |
| 7039639 | Brezin et al. | May 2006 | B2 |
| 7039676 | Day et al. | May 2006 | B1 |
| 7043530 | Isaacs et al. | May 2006 | B2 |
| 7047030 | Forsyth | May 2006 | B2 |
| 7056217 | Pelkey et al. | Jun 2006 | B1 |
| 7058036 | Yu et al. | Jun 2006 | B1 |
| 7058690 | Maehiro | Jun 2006 | B2 |
| 7065550 | Raghunandan | Jun 2006 | B2 |
| 7082047 | Chow | Jul 2006 | B2 |
| 7085259 | Wang et al. | Aug 2006 | B2 |
| 7117254 | Lunt et al. | Oct 2006 | B2 |
| 7124123 | Roskind et al. | Oct 2006 | B1 |
| 7124164 | Chemtob | Oct 2006 | B1 |
| 7127232 | O'Neil et al. | Oct 2006 | B2 |
| 7127685 | Canfield et al. | Oct 2006 | B2 |
| 7133900 | Szeto | Nov 2006 | B1 |
| 7137070 | Brown et al. | Nov 2006 | B2 |
| 7143356 | Shafrir et al. | Nov 2006 | B1 |
| 7145678 | Simpson et al. | Dec 2006 | B2 |
| 7155680 | Akazawa et al. | Dec 2006 | B2 |
| 7159008 | Wies et al. | Jan 2007 | B1 |
| 7177811 | Ostermann et al. | Feb 2007 | B1 |
| 7177880 | Ruvolo | Feb 2007 | B2 |
| 7181441 | Mandato et al. | Feb 2007 | B2 |
| 7181498 | Zhu et al. | Feb 2007 | B2 |
| 7181690 | Leahy et al. | Feb 2007 | B1 |
| 7185059 | Daniell et al. | Feb 2007 | B2 |
| 7188143 | Szeto | Mar 2007 | B2 |
| 7188153 | Lunt et al. | Mar 2007 | B2 |
| 7190956 | Dorenbosch et al. | Mar 2007 | B2 |
| 7194542 | Segan et al. | Mar 2007 | B2 |
| 7200634 | Mendiola et al. | Apr 2007 | B2 |
| 7202814 | Caspi et al. | Apr 2007 | B2 |
| 7216143 | Creamer et al. | May 2007 | B2 |
| 7222156 | Gupta et al. | May 2007 | B2 |
| 7231205 | Guyot et al. | Jun 2007 | B2 |
| 7248677 | Randall et al. | Jul 2007 | B2 |
| 7249139 | Chuah et al. | Jul 2007 | B2 |
| 7257617 | Brown et al. | Aug 2007 | B2 |
| 7269590 | Hull et al. | Sep 2007 | B2 |
| 7275215 | Werndorfer et al. | Sep 2007 | B2 |
| 7313760 | Grossman et al. | Dec 2007 | B2 |
| 7343312 | Capek et al. | Mar 2008 | B2 |
| 7363246 | Van Horn et al. | Apr 2008 | B1 |
| 7386799 | Clanton et al. | Jun 2008 | B1 |
| 7395329 | Holt et al. | Jul 2008 | B1 |
| 7436780 | Stephens et al. | Oct 2008 | B2 |
| 7468729 | Levinson | Dec 2008 | B1 |
| 7484176 | Blattner | Jan 2009 | B2 |
| 7596599 | Maghsoodnia et al. | Sep 2009 | B1 |
| 7636751 | Weaver et al. | Dec 2009 | B2 |
| 7636755 | Blattner et al. | Dec 2009 | B2 |
| 7668537 | De Vries | Feb 2010 | B2 |
| 7685237 | Weaver et al. | Mar 2010 | B1 |
| 7685518 | Matsuda | Mar 2010 | B2 |
| 7689649 | Heikes et al. | Mar 2010 | B2 |
| 7721310 | Schaffer et al. | May 2010 | B2 |
| 7779076 | Heikes et al. | Aug 2010 | B2 |
| 7908554 | Blattner | Mar 2011 | B1 |
| 7913176 | Blattner et al. | Mar 2011 | B1 |
| 8037150 | Weaver et al. | Oct 2011 | B2 |
| 8250144 | Blattner et al. | Aug 2012 | B2 |
| 8370631 | Pearson | Feb 2013 | B2 |
| 8402378 | Blattner | Mar 2013 | B2 |
| 20010005861 | Mousseau et al. | Jun 2001 | A1 |
| 20010013050 | Shah | Aug 2001 | A1 |
| 20010019330 | Bickmore et al. | Sep 2001 | A1 |
| 20010030664 | Shulman et al. | Oct 2001 | A1 |
| 20010054084 | Kosmynin | Dec 2001 | A1 |
| 20020002542 | Ando et al. | Jan 2002 | A1 |
| 20020005865 | Hayes-Roth | Jan 2002 | A1 |
| 20020015061 | Maguire | Feb 2002 | A1 |
| 20020021307 | Glenn et al. | Feb 2002 | A1 |
| 20020023132 | Tornabene et al. | Feb 2002 | A1 |
| 20020023134 | Roskowski et al. | Feb 2002 | A1 |
| 20020028595 | Higashi et al. | Mar 2002 | A1 |
| 20020042816 | Bae | Apr 2002 | A1 |
| 20020054139 | Corboy et al. | May 2002 | A1 |
| 20020059425 | Belfiore et al. | May 2002 | A1 |
| 20020065856 | Kisiel | May 2002 | A1 |
| 20020065894 | Dalal et al. | May 2002 | A1 |
| 20020075303 | Thompson et al. | Jun 2002 | A1 |
| 20020077080 | Greene | Jun 2002 | A1 |
| 20020078150 | Thompson et al. | Jun 2002 | A1 |
| 20020078153 | Chung et al. | Jun 2002 | A1 |
| 20020080192 | King et al. | Jun 2002 | A1 |
| 20020083136 | Whitten, II | Jun 2002 | A1 |
| 20020091667 | Jaipuria et al. | Jul 2002 | A1 |
| 20020094869 | Harkham | Jul 2002 | A1 |
| 20020103801 | Lyons | Aug 2002 | A1 |
| 20020104087 | Schaffer et al. | Aug 2002 | A1 |
| 20020111994 | Raghunandan | Aug 2002 | A1 |
| 20020112181 | Smith | Aug 2002 | A1 |
| 20020113809 | Akazawa | Aug 2002 | A1 |
| 20020113820 | Robinson et al. | Aug 2002 | A1 |
| 20020116458 | Bricklin et al. | Aug 2002 | A1 |
| 20020116463 | Hart | Aug 2002 | A1 |
| 20020116641 | Mastrianni | Aug 2002 | A1 |
| 20020119789 | Friedman | Aug 2002 | A1 |
| 20020128746 | Boies et al. | Sep 2002 | A1 |
| 20020133292 | Miyaki | Sep 2002 | A1 |
| 20020133369 | Johnson | Sep 2002 | A1 |
| 20020133535 | Lucovsky et al. | Sep 2002 | A1 |
| 20020138286 | Engstrom | Sep 2002 | A1 |
| 20020147777 | Hackbarth et al. | Oct 2002 | A1 |
| 20020165727 | Greene et al. | Nov 2002 | A1 |
| 20020171647 | Sterchi et al. | Nov 2002 | A1 |
| 20020174010 | Rice, III | Nov 2002 | A1 |
| 20020174026 | Pickover et al. | Nov 2002 | A1 |
| 20020175953 | Lin | Nov 2002 | A1 |
| 20020178161 | Brezin et al. | Nov 2002 | A1 |
| 20020178206 | Smith | Nov 2002 | A1 |
| 20020181009 | Fredlund et al. | Dec 2002 | A1 |
| 20020181703 | Logan et al. | Dec 2002 | A1 |
| 20020184089 | Tsou et al. | Dec 2002 | A1 |
| 20020184309 | Danker et al. | Dec 2002 | A1 |
| 20020193942 | Odakura et al. | Dec 2002 | A1 |
| 20020198882 | Linden et al. | Dec 2002 | A1 |
| 20020199095 | Bandini et al. | Dec 2002 | A1 |
| 20030004774 | Greene et al. | Jan 2003 | A1 |
| 20030004855 | Dutta et al. | Jan 2003 | A1 |
| 20030004872 | Gardi et al. | Jan 2003 | A1 |
| 20030004967 | Calderaro et al. | Jan 2003 | A1 |
| 20030005058 | Sorotzkin | Jan 2003 | A1 |
| 20030009495 | Adjaoute | Jan 2003 | A1 |
| 20030009523 | Lindskog et al. | Jan 2003 | A1 |
| 20030014274 | Chalon | Jan 2003 | A1 |
| 20030018726 | Low et al. | Jan 2003 | A1 |
| 20030020749 | Abu-Hakima et al. | Jan 2003 | A1 |
| 20030023690 | Lohtia | Jan 2003 | A1 |
| 20030023875 | Hursey et al. | Jan 2003 | A1 |
| 20030028524 | Keskar et al. | Feb 2003 | A1 |
| 20030028595 | Vogt et al. | Feb 2003 | A1 |
| 20030030670 | Duarte et al. | Feb 2003 | A1 |
| 20030037112 | Fitzpatrick | Feb 2003 | A1 |
| 20030041108 | Henrick et al. | Feb 2003 | A1 |
| 20030043201 | Abdelhadi et al. | Mar 2003 | A1 |
| 20030046198 | Knapp et al. | Mar 2003 | A1 |
| 20030050062 | Chen et al. | Mar 2003 | A1 |
| 20030050115 | Leen et al. | Mar 2003 | A1 |
| 20030050916 | Ortega et al. | Mar 2003 | A1 |
| 20030061239 | Yoon | Mar 2003 | A1 |
| 20030065721 | Roskind | Apr 2003 | A1 |
| 20030074409 | Bentley | Apr 2003 | A1 |
| 20030080989 | Matsuda et al. | May 2003 | A1 |
| 20030084103 | Weiner et al. | May 2003 | A1 |
| 20030088789 | Fenton et al. | May 2003 | A1 |
| 20030093580 | Thomas et al. | May 2003 | A1 |
| 20030101226 | Quine | May 2003 | A1 |
| 20030104830 | Norwood et al. | Jun 2003 | A1 |
| 20030105820 | Haims et al. | Jun 2003 | A1 |
| 20030105822 | Gusler et al. | Jun 2003 | A1 |
| 20030119531 | Patton et al. | Jun 2003 | A1 |
| 20030131061 | Newton et al. | Jul 2003 | A1 |
| 20030140103 | Szeto et al. | Jul 2003 | A1 |
| 20030156134 | Kim | Aug 2003 | A1 |
| 20030160815 | Muschetto | Aug 2003 | A1 |
| 20030167324 | Farnham et al. | Sep 2003 | A1 |
| 20030179222 | Noma et al. | Sep 2003 | A1 |
| 20030182375 | Zhu et al. | Sep 2003 | A1 |
| 20030182394 | Ryngler et al. | Sep 2003 | A1 |
| 20030187813 | Goldman et al. | Oct 2003 | A1 |
| 20030191682 | Shepard et al. | Oct 2003 | A1 |
| 20030193558 | Doss et al. | Oct 2003 | A1 |
| 20030204474 | Capek et al. | Oct 2003 | A1 |
| 20030206170 | Bickmore | Nov 2003 | A1 |
| 20030210265 | Haimberg | Nov 2003 | A1 |
| 20030222907 | Heikes et al. | Dec 2003 | A1 |
| 20030225846 | Heikes et al. | Dec 2003 | A1 |
| 20030225847 | Heikes et al. | Dec 2003 | A1 |
| 20030225848 | Heikes et al. | Dec 2003 | A1 |
| 20030229722 | Beyda | Dec 2003 | A1 |
| 20030231207 | Huang | Dec 2003 | A1 |
| 20030236770 | Kurapati et al. | Dec 2003 | A1 |
| 20040003041 | Moore | Jan 2004 | A1 |
| 20040015548 | Lee | Jan 2004 | A1 |
| 20040024822 | Werndorfer et al. | Feb 2004 | A1 |
| 20040034799 | Mikami | Feb 2004 | A1 |
| 20040034848 | Moore et al. | Feb 2004 | A1 |
| 20040054729 | Fukuizumi et al. | Mar 2004 | A1 |
| 20040054736 | Daniell et al. | Mar 2004 | A1 |
| 20040056901 | March et al. | Mar 2004 | A1 |
| 20040117443 | Barsness | Jun 2004 | A1 |
| 20040122681 | Ruvolo | Jun 2004 | A1 |
| 20040122810 | Mayer | Jun 2004 | A1 |
| 20040122855 | Ruvolo | Jun 2004 | A1 |
| 20040128353 | Goodman et al. | Jul 2004 | A1 |
| 20040128356 | Bernstein et al. | Jul 2004 | A1 |
| 20040137882 | Forsyth | Jul 2004 | A1 |
| 20040148346 | Weaver et al. | Jul 2004 | A1 |
| 20040179037 | Blattner | Sep 2004 | A1 |
| 20040179039 | Blattner et al. | Sep 2004 | A1 |
| 20040186738 | Reisman | Sep 2004 | A1 |
| 20040201624 | Crawford | Oct 2004 | A1 |
| 20040205480 | Moore | Oct 2004 | A1 |
| 20040210844 | Pettinati et al. | Oct 2004 | A1 |
| 20040215648 | Marshall et al. | Oct 2004 | A1 |
| 20040215721 | Szeto et al. | Oct 2004 | A1 |
| 20040215731 | Tzann-en Szeto | Oct 2004 | A1 |
| 20040215793 | Ryan et al. | Oct 2004 | A1 |
| 20040221224 | Blattner et al. | Nov 2004 | A1 |
| 20040260762 | Fish | Dec 2004 | A1 |
| 20040260781 | Shostack et al. | Dec 2004 | A1 |
| 20050015432 | Cohen | Jan 2005 | A1 |
| 20050021750 | Abrams | Jan 2005 | A1 |
| 20050027382 | Kirmse et al. | Feb 2005 | A1 |
| 20050038856 | Krishnasamy et al. | Feb 2005 | A1 |
| 20050043989 | Shifrin | Feb 2005 | A1 |
| 20050044152 | Hardy et al. | Feb 2005 | A1 |
| 20050050143 | Gusler et al. | Mar 2005 | A1 |
| 20050055416 | Heikes et al. | Mar 2005 | A1 |
| 20050060198 | Bayne | 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 |
| 20050080867 | Malik et al. | Apr 2005 | A1 |
| 20050080868 | Malik | Apr 2005 | A1 |
| 20050086211 | Mayer | Apr 2005 | A1 |
| 20050091311 | Lund et al. | Apr 2005 | A1 |
| 20050108239 | Evans et al. | May 2005 | A1 |
| 20050108329 | Weaver et al. | May 2005 | A1 |
| 20050114229 | Ackley et al. | May 2005 | A1 |
| 20050114783 | Szeto | May 2005 | A1 |
| 20050153681 | Hanson | Jul 2005 | A1 |
| 20050171799 | Hull et al. | Aug 2005 | A1 |
| 20050197846 | Pezaris | Sep 2005 | A1 |
| 20050216300 | Appelman et al. | Sep 2005 | A1 |
| 20050223328 | Ashtekar et al. | Oct 2005 | A1 |
| 20050227676 | Vries | Oct 2005 | A1 |
| 20050246420 | Little | Nov 2005 | A1 |
| 20050289147 | Khan et al. | Dec 2005 | A1 |
| 20060028475 | Tobias | Feb 2006 | A1 |
| 20060064645 | Neven et al. | Mar 2006 | A1 |
| 20060075044 | Fox et al. | Apr 2006 | A1 |
| 20060129678 | Morita | Jun 2006 | A1 |
| 20060143569 | Kinsella et al. | Jun 2006 | A1 |
| 20060167991 | Heikes et al. | Jul 2006 | A1 |
| 20060168054 | Burkhart et al. | Jul 2006 | A1 |
| 20060173824 | Bensky et al. | Aug 2006 | A1 |
| 20060173959 | McKelvie et al. | Aug 2006 | A1 |
| 20060173963 | Roseway et al. | Aug 2006 | A1 |
| 20060182248 | Smith et al. | Aug 2006 | A1 |
| 20060184886 | Chung et al. | Aug 2006 | A1 |
| 20060212561 | Feng | Sep 2006 | A1 |
| 20060227142 | Brown et al. | Oct 2006 | A1 |
| 20060248573 | Pannu et al. | Nov 2006 | A1 |
| 20060277187 | Roese et al. | Dec 2006 | A1 |
| 20070022174 | Issa | Jan 2007 | A1 |
| 20070113181 | Blattner | May 2007 | A1 |
| 20070156664 | Norton et al. | Jul 2007 | A1 |
| 20070168863 | Blattner et al. | Jul 2007 | A1 |
| 20080228598 | Leff et al. | Sep 2008 | A1 |
| 20080255989 | Altberg et al. | Oct 2008 | A1 |
| 20090043844 | Zimmet et al. | Feb 2009 | A1 |
| 20090089316 | Kogan et al. | Apr 2009 | A1 |
| 20090158184 | Blattner et al. | Jun 2009 | A1 |
| 20100174996 | Heikes et al. | Jul 2010 | A1 |
| 20110209198 | Blattner et al. | Aug 2011 | A1 |
| Number | Date | Country |
|---|---|---|
| 0 862 304 | Sep 1998 | EP |
| 1011248 | Jan 2001 | EP |
| 1 176 840 | Jan 2002 | EP |
| 1130869 | Jun 2005 | EP |
| 11355619 | Dec 1999 | JP |
| 2000-259514 | Sep 2000 | JP |
| 2000-284999 | Oct 2000 | JP |
| 2001-084320 | Mar 2001 | JP |
| WO 9710558 | Mar 1997 | WO |
| WO 9746955 | Dec 1997 | WO |
| WO 9816045 | Apr 1998 | WO |
| WO 9908434 | Feb 1999 | WO |
| WO-0068815 | Nov 2000 | WO |
| WO 0122258 | Mar 2001 | WO |
| WO-0184461 | Nov 2001 | WO |
| WO 0203216 | Jan 2002 | WO |
| 0217602 | Feb 2002 | WO |
| WO 02073886 | Sep 2002 | WO |
| Entry |
|---|
| U.S. Appl. No. 13/035,035, Non-Final Office Action mailed Mar. 31, 2014, 8 pages. |
| U.S. Appl. No. 13/035,052, Amendment and Response filed Dec. 3, 2013, 3 pages. |
| U.S. Appl. No. 12/722,755, Notice of Allowance mailed Dec. 19, 2013, 18 pages. |
| U.S. Appl. No. 12/729,797, Non-Final Office Action mailed Jan. 30, 2014, 15 pages. |
| “Advisory Action”, U.S. Appl. No. 10/305,015, (Aug. 30, 2005), 3 pages. |
| “Advisory Action”, U.S. Appl. No. 10/334,027, (Sep. 12, 2007), 4 pages. |
| “Advisory Action”, U.S. Appl. No. 10/334,027, (Nov. 21, 2007), 4 pages. |
| “Advisory Action”, U.S. Appl. No. 10/334,128, (May 20, 2008), 5 pages. |
| “Advisory Action”, U.S. Appl. No. 10/334,129, (Oct. 5, 2007), 3 pages. |
| “Advisory Action”, U.S. Appl. No. 10/747,255, (Jan. 16, 2009), 3 pages. |
| “Advisory Action”, U.S. Appl. No. 10/747,652, (Nov. 27, 2007), 3 pages. |
| “Advisory Action”, U.S. Appl. No. 10/747,696, (Mar. 5, 2009), 3 pages. |
| “Advisory Action”, U.S. Appl. No. 10/847,463, (Mar. 25, 2009), 3 pages. |
| “Advisory Action”, U.S. Appl. No. 10/847,463, (Jun. 18, 2010), 3 pages. |
| “Advisory Action”, U.S. Appl. No. 10/847,463, (Aug. 10, 2010), 5 pages. |
| “Advisory Action”, U.S. Appl. No. 11/017,633, (Jan. 12, 2010), 3 pages. |
| “Advisory Action”, U.S. Appl. No. 11/017,634, (Mar. 6, 2009), 3 pages. |
| “Advisory Action”, U.S. Appl. No. 11/023,983, (Apr. 9, 2008), 4 pages. |
| “Advisory Action”, U.S. Appl. No. 12/266,690, (Dec. 2, 2011), 3 pages. |
| “Board Decision”, U.S. Appl. No. 11/023,999, (Jun. 17, 2010), 10 pages. |
| “BPAI Decision”, U.S. Appl. No. 10/305,015, (Mar. 24, 2010), 13 pages. |
| “Examiner's Answer to Appeal Brief”, U.S. Appl. No. 10/305,015, (Jul. 5, 2006), 31 pages. |
| “Examiner's Answer to Appeal Brief”, U.S. Appl. No. 10/305,015, (Feb. 25, 2008), 28 pages. |
| “Examiner's Answer”, U.S. Appl. No. 10/334,128, (Oct. 1, 2008), 23 pages. |
| “Examiner's First Report on Australian Patent Application No. 2004216758”, (Oct. 30, 2008), 2 pages. |
| “Examiner's Response to Appeal Brief”, U.S. Appl. No. 11/023,999, (Apr. 15, 2009), 15 pages. |
| “Final Office Action”, U.S. Appl. No. 10/305,015, (Apr. 13, 2004), 14 pages. |
| “Final Office Action”, U.S. Appl. No. 10/305,015, (Jun. 4, 2007), 21 pages. |
| “Final Office Action”, U.S. Appl. No. 10/305,015, (Jun. 20, 2005), 13 pages. |
| “Final Office Action”, U.S. Appl. No. 10/334,027, (Apr. 30, 2008), 24 pages. |
| “Final Office Action”, U.S. Appl. No. 10/334,027, (Jun. 28, 2007), 22 pages. |
| “Final Office Action”, U.S. Appl. No. 10/334,128, (Jan. 11, 2008), 19 pages. |
| “Final Office Action”, U.S. Appl. No. 10/334,129, (Jul. 25, 2007), 24 pages. |
| “Final Office Action”, U.S. Appl. No. 10/715,209, (Jul. 1, 2008), 11 pages. |
| “Final Office Action”, U.S. Appl. No. 10/718,039, (Mar. 27, 2008), 31 pages. |
| “Final Office Action”, U.S. Appl. No. 10/718,039, (Aug. 19, 2009), 31 pages. |
| “Final Office Action”, U.S. Appl. No. 10/747,255, (Sep. 5, 2007), 14 pages. |
| “Final Office Action”, U.S. Appl. No. 10/747,255, (Oct. 24, 2008), 14 pages. |
| “Final Office Action”, U.S. Appl. No. 10/747,652, (Jun. 11, 2009), 19 pages. |
| “Final Office Action”, U.S. Appl. No. 10/747,652, (Jun. 28, 2010), 17 pages. |
| “Final Office Action”, U.S. Appl. No. 10/747,652, (Sep. 6, 2007), 17 pages. |
| “Final Office Action”, U.S. Appl. No. 10/747,696, (Oct. 21, 2008), 9 pages. |
| “Final Office Action”, U.S. Appl. No. 10/847,463, (Feb. 3, 2010), 56 pages. |
| “Final Office Action”, U.S. Appl. No. 10/847,463, (Nov. 14, 2008), 40 pages. |
| “Final Office Action”, U.S. Appl. No. 10/981,686, (Sep. 16, 2008), 12 pages. |
| “Final Office Action”, U.S. Appl. No. 11/017,240, (May 5, 2008), 10 pages. |
| “Final Office Action”, U.S. Appl. No. 11/017,633, (Sep. 23, 2009), 11 pages. |
| “Final Office Action”, U.S. Appl. No. 11/017,634, (Dec. 15, 2008), 14 pages. |
| “Final Office Action”, U.S. Appl. No. 11/023,983, (Jan. 7, 2010), 5 pages. |
| “Final Office Action”, U.S. Appl. No. 11/023,983, (Jan. 11, 2008), 13 pages. |
| “Final Office Action”, U.S. Appl. No. 11/023,999, (Apr. 7, 2008), 14 pages. |
| “Final Office Action”, U.S. Appl. No. 11/362,034, (Feb. 8, 2010), 27 pages. |
| “Final Office Action”, U.S. Appl. No. 11/362,034, (Dec. 12, 2008), 17 pages. |
| “Final Office Action”, U.S. Appl. No. 11/410,323, (Dec. 11, 2008), 16 pages. |
| “Final Office Action”, U.S. Appl. No. 12/266,690, (Aug. 23, 2011), 11 pages. |
| “Final Office Action”, U.S. Appl. No. 12/722,755, (Feb. 28, 2012), 21 pages. |
| “InterCom Cartoon Chat System”, http://www.nfx.com, (Dec. 1, 2003), 11 pages. |
| “International Preliminary Report on Patentability and Written Opinon”, Application No. PCT/US2004/006284, (Sep. 9, 2005), 11 pages. |
| “International Preliminary Report on Patentability and Written Opinion”, Application No. PCT/US2007/062321, (Sep. 12, 2008), 9 pages. |
| “International Preliminary Report on Patentability and Written Opinion”, Application No. PCT/US2007/066988, (Oct. 28, 2008), 7 pages. |
| “International Search Report and Written Opinion”, Application No. PCT/US2004/006284, (Sep. 1, 2004), 13 pages. |
| “International Search Report and Written Opinion”, Application No. PCT/US2007/066988, (Apr. 19, 2007), 7 pages. |
| “International Search Report and Written Opinion”, Application No. PCT/US2007/062321, (Jun. 18, 2008), 13 pages. |
| “International Search Report and Written Opinion”, PCT Application No. PCT/US2007/66988, (Jun. 18, 2008), 9 pages. |
| “International Search Report”, Application No. PCT/US03/16690, (Nov. 19, 2003), 1 page. |
| “International Search Report”, Application No. PCT/US03/16776, (Aug. 13, 2003), 1 page. |
| “International Search Report”, Application No. PCT/US03/36796, (May 24, 2004), 2 pages. |
| “Non-Final Office Action”, U.S. Appl. No. 10/305,015, (Jul. 29, 2003), 11 pages. |
| “Non-Final Office Action”, U.S. Appl. No. 10/305,015, (Dec. 6, 2006), 17 pages. |
| “Non-Final Office Action”, U.S. Appl. No. 10/305,015, (Dec. 8, 2004), 10 pages. |
| “Non-Final Office Action”, U.S. Appl. No. 10/334,027, (Sep. 30, 2008), 27 pages. |
| “Non-Final Office Action”, U.S. Appl. No. 10/334,027, (Nov. 20, 2006), 20 pages. |
| “Non-Final Office Action”, U.S. Appl. No. 10/334,128, (Aug. 16, 2006), 15 pages. |
| “Non-Final Office Action”, U.S. Appl. No. 10/334,129, (Jan. 3, 2007), 22 pages. |
| “Non-Final Office Action”, U.S. Appl. No. 10/715,209, (Jan. 26, 2009), 6 pages. |
| “Non-Final Office Action”, U.S. Appl. No. 10/715,209, (Oct. 9, 2007), 12 pages. |
| “Non-Final Office Action”, U.S. Appl. No. 10/718,039, (Jul. 30, 2007), 30 pages. |
| “Non-Final Office Action”, U.S. Appl. No. 10/718,039, (Nov. 26, 2008), 31 pages. |
| “Non-Final Office Action”, U.S. Appl. No. 10/747,255, (Mar. 15, 2007), 10 pages. |
| “Non-Final Office Action”, U.S. Appl. No. 10/747,255, (Mar. 25, 2008), 13 pages. |
| “Non-Final Office Action”, U.S. Appl. No. 10/747,652, (Feb. 13, 2008), 16 pages. |
| “Non-Final Office Action”, U.S. Appl. No. 10/747,652, (Mar. 23, 2007), 13 pages. |
| “Non-Final Office Action”, U.S. Appl. No. 10/747,652, (Oct. 20, 2008), 15 pages. |
| “Non-Final Office Action”, U.S. Appl. No. 10/747,652, (Dec. 17, 2009), 18 pages. |
| “Non-Final Office Action”, U.S. Appl. No. 10/747,696, (Mar. 18, 2008), 68 pages. |
| “Non-Final Office Action”, U.S. Appl. No. 10/747,701, (Mar. 14, 2007), 9 pages. |
| “Non-Final Office Action”, U.S. Appl. No. 10/847,463, (Apr. 10, 2008), 31 pages. |
| “Non-Final Office Action”, U.S. Appl. No. 10/847,463, (Jun. 24, 2009), 42 pages. |
| “Non-Final Office Action”, U.S. Appl. No. 10/847,463, (Dec. 29, 2010), 47 pages. |
| “Non-Final Office Action”, U.S. Appl. No. 10/981,686, (Mar. 5, 2008), 21 pages. |
| “Non-Final Office Action”, U.S. Appl. No. 11/017,240, (Sep. 18, 2008), 2 pages. |
| “Non-Final Office Action”, U.S. Appl. No. 11/017,240, (Oct. 5, 2007), 7 pages. |
| “Non-Final Office Action”, U.S. Appl. No. 11/017,633, (Mar. 6, 2008), 12 pages. |
| “Non-Final Office Action”, U.S. Appl. No. 11/017,633, (Apr. 26, 2010), 11 pages. |
| “Non-Final Office Action”, U.S. Appl. No. 11/017,633, (Sep. 10, 2008), 16 pages. |
| “Non-Final Office Action”, U.S. Appl. No. 11/017,634, (Apr. 4, 2008), 14 pages. |
| “Non-Final Office Action”, U.S. Appl. No. 11/017,634, (Aug. 10, 2007), 15 pages. |
| “Non-Final Office Action”, U.S. Appl. No. 11/023,983, (Jun. 11, 2009), 9 pages. |
| “Non-Final Office Action”, U.S. Appl. No. 11/023,983, (Jul. 27, 2007), 11 pages. |
| “Non-Final Office Action”, U.S. Appl. No. 11/023,983, (Sep. 8, 2008), 8 pages. |
| “Non-Final Office Action”, U.S. Appl. No. 11/023,999, (Aug. 24, 2007), 11 pages. |
| “Non-Final Office Action”, U.S. Appl. No. 11/362,034, (Apr. 29, 2008), 21 pages. |
| “Non-Final Office Action”, U.S. Appl. No. 11/362,034, (Jun. 25, 2009), 28 pages. |
| “Non-Final Office Action”, U.S. Appl. No. 11/410,323, (May 29, 2008), 13 pages. |
| “Non-Final Office Action”, U.S. Appl. No. 12/266,690, (Mar. 9, 2011), 11 pages. |
| “Non-Final Office Action”, U.S. Appl. No. 12/644,711, (Jan. 3, 2012), 27 pages. |
| “Non-Final Office Action”, U.S. Appl. No. 12/644,711, (Jul. 29, 2011), 6 pages. |
| “Non-Final Office Action”, U.S. Appl. No. 12/722,755, (Sep. 20, 2011), 21 pages. |
| “Non-Final Office Action”, U.S. Appl. No. 12/729,797, (Jun. 11, 2012), 13 pages. |
| “Notice of Allowance”, U.S. Appl. No. 10/305,015, (Apr. 6, 2010), 4 pages. |
| “Notice of Allowance”, U.S. Appl. No. 10/334,027, (Nov. 2, 2009), 13 pages. |
| “Notice of Allowance”, U.S. Appl. No. 10/715,209, (Aug. 11, 2009), 4 pages. |
| “Notice of Allowance”, U.S. Appl. No. 10/747,701, (Jan. 7, 2008), 7 pages. |
| “Notice of Allowance”, U.S. Appl. No. 10/747,701, (Jun. 12, 2008), 6 pages. |
| “Notice of Allowance”, U.S. Appl. No. 10/747,701, (Aug. 24, 2007), 10 pages. |
| “Notice of Allowance”, U.S. Appl. No. 10/847,463, (Jun. 10, 2011), 8 pages. |
| “Notice of Allowance”, U.S. Appl. No. 11/017,240, (Aug. 18, 2008), 6 pages. |
| “Notice of Allowance”, U.S. Appl. No. 11/017,633, (Aug. 9, 2010), 6 pages. |
| “Notice of Allowance”, U.S. Appl. No. 11/017,633, (Nov. 15, 2010), 6 pages. |
| “Notice of Allowance”, U.S. Appl. No. 11/023,983, (Apr. 12, 2010), 8 pages. |
| “Notice of Allowance”, U.S. Appl. No. 11/023,983, (Nov. 5, 2010), 4 pages. |
| “Notice of Allowance”, U.S. Appl. No. 11/252890, (Nov. 3, 2009), 8 pages. |
| “Notice of Allowance”, U.S. Appl. No. 11/362,034, (Jul. 19, 2010), 8 pages. |
| “Notice of Allowance”, U.S. Appl. No. 12/266,690, (May 11, 2012), 7 pages. |
| “Notice of Allowance”, U.S. Appl. No. 12/644,711, (Apr. 12, 2012), 9 pages. |
| “People Putty”, <http://www.haptek.com/products/peopleputty, (Dec. 30, 2003), 5 pages. |
| “Prodigy Unveils Next Generation of Instant Messaging”, Business Wire, (May 5, 1999), 4 pages. |
| “Restriction Requirement”, U.S. Appl. No. 10/747,696, (Sep. 26, 2007), 6 pages. |
| “Restriction Requirement”, U.S. Appl. No. 11/017,633, (Apr. 30, 2009), 6 pages. |
| “Restriction Requirement”, U.S. Appl. No. 11/252,890, (Jul. 20, 2009), 7 pages. |
| “The eSniff Product Overview”, eSniff: Define Your e-Boundaries, www.esniff.com/product—overview.html, (May 15, 2001), 1 page. |
| Unpublished U.S. Appl. No. 11/017,634, entitled “User Profile Information to Determine an Avatar and/or Avatar Characteristics”, (Dec. 21, 2004), 67 pages. |
| Unpublished U.S. Appl. No. 11/023,983, entitled “Modifying Avatar Behavior Based on User Action Mood”, (Dec. 29, 2004), 98 pages. |
| “Viewpoint Experience Technology Getting Started”, Viewpoint: Version 1.1, (Jun. 19, 2002), pp. 1-21. |
| “Viewpoint Technology Feature Overview”, Viewpoint: Version 2.0, (Jun. 19, 2002), pp. 1-23. |
| “What's new about exchanging information over the Interne”, Outlook 2000 SR-1 (9.0.0.4527) retrieved May 7, 2003, 1 page. |
| Appelman, Barry et al., “U.S. Appl. No. 10/718,039”, filed Nov. 21, 2003, 114 pages. |
| Arnholt, Jeff “Optimizing Linux's User Interface”, Linux Journal, Issue 19, Specialized Sys. Consultants Inc. (1995), 6 pages. |
| Chen, Julie The Early Report—The Early Show segment, “Big Brother in the Corner Office”, cbsnews.com.earlyshow/caught/techage/20001229e—sniff.shtml, Tech Age, (Dec. 28, 2000), 3 pages. |
| Kerlow, Isaac V., “The Art of 3D Computer Animation and Effects”, John Wiley & Sons, Inc., (2004), pp. 122 & 358-359 |
| Kurlander, David et al., “Comic Chat”, Proceedings of the 3rd Annual Conference on Computer Graphics and Interactive Techniques, ACM Press, New York, NY, (1996), pp. 225-236. |
| Lange, Katherine “Esniff Ferrets Out Misbehavior ‘By Reading’ E-Mail, Web Visits”, The Wall Street Journal article, interactive.wsj.com, Tech Q&A, (Apr. 27, 2001), 4 pages. |
| Mitsuoka, M et al., “Instant Messaging with Mobile Phones to Support Awareness”, IEEE ISBN 0-7695-0942, (Aug. 2001), pp. 223-230. |
| Salem, Ben et al., “Designing a Non-Verbal Language for Expressive Avatars”, Collaborative Virtual Enviroments; University of Plymouth; ISBN: 1-58113-303-0, (2000), pp. 93-101. |
| Weaver, Andrew et al., “U.S. Appl. No. 10/718,039”, filed Oct. 19, 2005, 123 pages. |
| U.S. Appl. No. 12/729,797, Amendment and Response filed Oct. 2, 2013, 12 pages. |
| “About Internet directory services,” Outlook 2000 SR-1 (9.0.0. 4527) Help File, on or before Aug. 10, 2001 (1 page). |
| “Active Directory Features,” http://www.microsoft.com/windows2000/server/evaluation/features/adlist.asp, Jun. 15, 1999 (4 pages). |
| “Active Directory Service Overview,” http://www.microsoft.com/windows2000/server/evaluation/business/addatasheet.asp, Nov. 30, 2001 (5 pages). |
| “Active Directory,” http://www.microsoft.com/windows2000/technologies/directory/AD/default.asp, May 13, 2003 (13 pages). |
| “AOL Instant Messenger All New Version 2.0,” Jun. 24, 1999 (2 pages). |
| “AOL technology: turning complicated things into engaging services,” 1996 Annual Report, 2 pages. |
| “Benefits of Active Directory in a Windows 2000 Environment,” http://www.microsoft.com/windows2000/server/evaluation/business/adwin2k.asp, Sep. 20, 2001 (9 pages). |
| “Directory Integration Can Lower Total Cost of Ownership and Increase Application Functionality,” http://www.microsoft.com/presspas/press/1998/July98/ActivDPR.asp, Jul. 27, 1998 (4 pages). |
| “Enterprise Identity Management with Windows 2000 and Active Directory,” http://www.microsoft.com/technet/prodtechnol/ad/windows2000/evaluate/w2keims.asp, 1999 (16 pages). |
| “Frequently Asked Questions About AOL Instant Messenger,” Jun. 24, 1999 (6 pages). |
| “Integrating Applications with Windows 2000 and Active Directory,” http:/www.microsoft.com/technet/prodtechnol/ad/windows2000/evaluate/adappstr.asp, Oct. 2000, (12 pages). |
| “Integrating Microsoft Metadirectory Services and Active Directory,” http://www.microsoft.com/windows2000/server/evaluation/news/bulletins/mmsma.asp, Aug. 31, 2000, (1 page). |
| “Introducing the Gordano Messaging Suite,” http://www.gordano.com, 1994-2003 (3 pages). |
| “Look up contact information from an item,” Outlook 2000 SR-1 (9.0.0 4527) Help File, Aug. 10, 2001, (1 page). |
| “New Features in AOL Instant Messenger for Windows v. 2.01 Beta,” Apr. 28, 1999 (2 pages). |
| “Part II: Tasks and Procedures,” Active Directory Operations Guide, Microsoft Corporation, Microsoft Windows 2000, Version 1.5, Dec. 5, 2002 (131 pages). |
| “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, Aug. 10, 2001 (1 page). |
| “The LP Wireless Messenger,” Messenger Documentation, LP Wireless, Inc., http://www.lpwireless.com/messengerhelp.htm, Nov. 2, 2002 (7 pages). |
| Stank, “Using Active Directory Service,” Microsoft Windows 2000 Administrator's Pocket Consultant 1999 (6 pages). |
| “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.0.4527) (1 page). |
| “Windows 2000 Directory Services,” 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). |
| Cannon, “Design Guide for Directory-Enabled Applications,” http://msdn.microsoft.com/library/en-us/dnactdir/html/deal.asp?frame=true, Apr. 2001 (18 pages). |
| 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. |
| McKendrick, “Internet Call Centers: New Era in Customer Service,” vol. 10, No. 2, Feb. 2002 (5 pages). |
| Microsoft Corporation, “Active Directory Services Interface in the Microsoft Exchange 5.5 Environment,” http://msdn.microsoft.com/library/en-us/dnactdir/html/msdn—adsiexch.asp?frame=true, Nov. 1997 (12 pages). |
| Microsoft Corporation, “Comparing Microsoft Active Directory to Novell's NDS,” http://msdn.microsoft.com/library/en-us/dnactdir/html/msdn—activedirvsnds.asp?frame=true, Sep. 1998 (17 pages). |
| Microsoft Corporation, “Introduction to Active Directory Application Mode,” Microsoft Windows Server 2003, Aug. 2002 (16 pages). |
| Microsoft Corporation, “Using ADSI, LDAP, and Network Management Functions With Active Directory,” http://msdn.microsoft.com/library/en-us/dnactdir/html/BuildingADApps.asp?frame=true, Feb. 2002 (9 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, “Working with Active Directory Domains,” Chapter 5, Microsoft Windows 2000 Administrator's Pocket Consultant, 1999 (10 pages). |
| International Search Report for International Application No. PCT/US03/15715, mailed Aug. 14, 2003, 6 pages. |
| Kurlander et al., “International Conference on Computer Graphics and Interactive Techniques—Proceedings of the 23rd annual conference on Computer graphics and interactive techniques,” Comic Chat, http://portal.acm.org/citation.cfm?id=237260&coll=portal&d1=portal&CFID=3718856&CF, Aug. 9, 2002, pp. 225-236. |
| Cerulean Studios, Trillian Help Center, Chapter 4, Section 1, http://www.trillian.cc/help/sec-1.php?hchap=4&hsub=1, Nov. 12, 2002 (2 pages). |
| Cerulean Studios, Trillian Help Center, Tutorials, Chapter 10, Section 5, http://www.trillian.cc/help/sec-1.php?hchap=10&hsub=5, Nov. 12, 2002 (1 page). |
| Cerulean Studios, Trillian Help Center, Tutorials, Chapter 10, Section 7, http://www.trillian.cc/help/sec-1.php?hchap=10&hsub=7, Nov. 12, 2002 (2 pages). |
| Pamela parker, “Oct. 22, 2001—New Yahoo! Messenger Incorporates Viral Marketing,” http://siliconvalley.internet.com/news/article.php/908221, Oct. 30, 2002 (3 pages). |
| InternetNews.com Staff, IAR Bits and Bytes, “Yahoo! Debuts Purina IM Skin, Eagles Tour Promo,” http://www.internetnews.com/IAR/article.php/1011751, Apr. 17, 2002 (3 pages). |
| Yahoo! Messenger, Yahoo! Help—IMVironments, http://help.yahoo.com/help/us/mesg/imv/index.html, Oct. 30, 2002 (1 page). |
| Yahoo! Messenger, Yahoo! Help—IMVironments, http://help.yahoo.com/help/us/mesg/imv/imv-04.html, Oct. 30, 2002 (1 page). |
| Yahoo! Messenger, Yahoo! Help—IMVironments, http://help.yahoo.com/help/us/mesg/imv/imv-01.html, Oct. 30, 2002 (1 page). |
| Making your own Yahoo! Messenger IMVironments, http://www.xcflabs.com/˜yaroslav/imvironments/instructions.html, Oct. 30, 2002 (2 pages). |
| Bob Woods, Instant Messaging Planet: Public IM: IM—The Cat's Meow, http://www.instantmessagingplanet.com/public/article/0,,10817—1011011,00.html, Oct. 30, 2002 (3 pages). |
| Santos, Tech TV/Review: Yahoo! Messenger 5.0, http://www.techtv.com/products/print/0,23102,3351041,00.html, Oct. 30, 2002 (2 pages). |
| Viksnins, First Look: Yahoo Messenger 5.0—Software Reviews—CNET.com, http://www.cnet.com/software/0-5566362-8-7787365-1.html, Oct. 30, 2002 (2 pages). |
| ZDNet: Yahoo Messenger 5.0 Review, printed from http://www.zdnetcom/supercenter/stories/review/0,12070,538313,00.html, Oct. 30, 2002 (3 pages). |
| ZDNet: Yahoo Messenger 5.0 Overview, printed from http://www.zdnetcom/supercenter/stories/overview/0,12069,538313,00.html, Oct. 30, 2002 (3 pages). |
| Screenshot Menu, Yahoo! Messenger Preferences, Nov. 12, 2002 (1 page). |
| Screenshot demonstration, karl—renner2002—Instant Message, Nov. 12, 2002 (1 page). |
| Yahoo: Messenger—IMVironment™, http://messenger.yahoo.com/messenger/imv/index.html, Nov. 12, 2002 (2 pages). |
| Yahoo! Help—IMVironments, “How do I send an IMVironment to a friend?,” http://help.yahoo.com/help/us/mesg/imv/imv-04.html, Nov. 12, 2002 (1 page). |
| Yahoo!Messenger, Instantly communicate with all of your online friends . . . , http://messenger.yahoo.com, May 24, 2002 (1 page). |
| YahoolMessenger—IMVironments™, List of Available IMVironments, http://messenger.yahoo.com/messenger/imv, May 24, 2002 (1 page). |
| Screenshot, nikebball87: AIM—nikebba11187, http://www.trillian.cc/skins/windowsxp.gif, May 14, 2002 (1 page). |
| Screenshot, Trillian 7 Skin: GoneBlue v.01, http://www.trillian.cc/skins/goneblue.jpg, May 14, 2002 (1 page). |
| Screenshot, Dream Green, http://www.trillian.cc/skins/DreamGreen.jpg, May 14, 2002 (1 page). |
| Screenshot, Trillian chosenOS, http://www.trillian.cc/skins/chosen—trill.jpg, May 14, 2002 (1 page). |
| Netscape 7.0, Preview Release 1, Reviewer's Guide, May 17, 2002, chapter 2, “Internet Messaging,” pp. 9-10 and “Instant Messaging with AIM (AOL Instant MessengersSM),” pp. 16-18. |
| iPlanet Instant Messenger Release 3.0 Quick Reference, Oct. 2001 (5 pages). |
| U.S. Appl. No. 12/722,755, Final Office Action mailed Aug. 8, 2013, 19 pages. |
| U.S. Appl. No. 12/729,797, Non-Final Office Action mailed Jul. 2, 2013, 14 pages. |
| U.S. Appl. No. 13/035,052, Notice of Allowance mailed May 28, 2013, 8 pages. |
| U.S. Appl. No. 13/035,052, Notice of Allowance mailed Jun. 26, 2013, 2 pages. |
| U.S. Appl. No. 13/035,052, Notice of Allowance mailed Aug. 19, 2013, 9 pages. |
| “Non-Final Office Action”, U.S. Appl. No. 11/023,998, (Aug. 3, 2007), 16 pages. |
| “Notice of Allowance”, U.S. Appl. No. 12/266,690, (Oct. 26, 2012), 6 pages. |
| Screenshot demonstration, Yahoo Messenger, sboalick—Instant Message, (May 14, 2002), 1 page. |
| U.S. Appl. No. 10/334,128, Amendment and Response filed Apr. 11, 2008, 6 pages. |
| U.S. Appl. No. 10/334,128, Amendment and Response filed Dec. 18, 2006, 18 pages. |
| U.S. Appl. No. 10/334,128, Appeal Brief filed Jul. 9, 2008, 23 pages. |
| U.S. Appl. No. 10/334,128, Patent Board Decision mailed Aug. 18, 2010, 10 pages. |
| U.S. Appl. No. 10/334,128, Reply Brief filed Dec. 1, 2008, 5 pages. |
| U.S. Appl. No. 10/715,209, Amendment and Response filed Mar. 10, 2008, 21 pages. |
| U.S. Appl. No. 10/715,209, Amendment and Response filed Apr. 23, 2009, 15 pages. |
| U.S. Appl. No. 10/715,209, Amendment and Response filed Nov. 3, 2008, 17 pages. |
| U.S. Appl. No. 10/747,255, Amendment and Response field Jan. 7, 2008, 19 pages. |
| U.S. Appl. No. 10/747,255, Amendment and Response filed Jun. 15, 2007, 16 pages. |
| U.S. Appl. No. 10/747,255, Amendment and Response filed Jul. 25, 2008, 20 pages. |
| U.S. Appl. No. 10/747,255, Amendment and Response filed Dec. 30, 2008, 7 pages. |
| U.S. Appl. No. 10/747,652, Amendment and Response filed Feb. 20, 2009, 20 pages. |
| U.S. Appl. No. 10/747,652, Amendment and Response filed Apr. 19, 2010, 18 pages. |
| U.S. Appl. No. 10/747,652, Amendment and Response filed Jun. 25, 2007, 22 pages. |
| U.S. Appl. No. 10/747,652, Amendment and Response filed Jul. 14, 2008, 8 pages. |
| U.S. Appl. No. 10/747,652, Amendment and Response filed Oct. 13, 2009, 6 pages. |
| U.S. Appl. No. 10/747,652, Amendment and Response filed Nov. 6, 2007, 10 pages. |
| U.S. Appl. No. 10/747,652, Amendment and Response filed Dec. 6, 2007, 27 pages. |
| U.S. Appl. No. 10/747,696, Amendment and Response filed Feb. 23, 2009, 19 pages. |
| U.S. Appl. No. 10/747,696, Amendment and Response filed Jul. 18, 2008, 18 pages. |
| U.S. Appl. No. 10/747,696, Notice of Allowance mailed Apr. 22, 2009, 9 pages. |
| U.S. Appl. No. 10/747,696, Notice of Allowance mailed Aug. 11, 2009, 4 pages. |
| U.S. Appl. No. 10/747,701, Amendment and Response filed Jun. 14, 2007, 14 pages. |
| U.S. Appl. No. 10/847,463, Amendment and Response filed Mar. 16, 2009, 23 pages. |
| U.S. Appl. No. 10/847,463, Amendment and Response filed Mar. 29, 2011, 34 pages. |
| U.S. Appl. No. 10/847,463, Amendment and Response filed Jun. 3, 2010, 7 pages. |
| U.S. Appl. No. 10/847,463, Amendment and Response filed Jul. 26, 2010, 10 pages. |
| U.S. Appl. No. 10/847,463, Amendment and Response filed Aug. 11, 2008, 24 pages. |
| U.S. Appl. No. 10/847,463, Amendment and Response filed Sep. 24, 2009, 4 pages. |
| U.S. Appl. No. 10/847,463, Amendment and Response filed Nov. 13, 2009, 23 pages. |
| U.S. Appl. No. 11/017,633, Amendment and Response filed Jan. 12, 2009, 14 pages. |
| U.S. Appl. No. 11/017,633, Amendment and Response filed Jun. 6, 2008, 14 pages. |
| U.S. Appl. No. 11/017,633, Amendment and Response filed Jul. 19, 2010, 20 pages. |
| U.S. Appl. No. 11/017,633, Amendment and Response filed Dec. 22, 2009, 13 pages. |
| U.S. Appl. No. 11/023,983, Amendment and Response Sep. 11, 2009, 9 pages. |
| U.S. Appl. No. 11/023,983, Amendment and Response filed Feb. 9, 2009, 10 pages. |
| U.S. Appl. No. 11/023,983, Amendment and Response filed Mar. 11, 2008, 10 pages. |
| U.S. Appl. No. 11/023,983, Amendment and Response filed Mar. 25, 2010, 9 pages. |
| U.S. Appl. No. 11/023,983, Amendment and Response filed Jun. 11, 2008, 9 pages. |
| U.S. Appl. No. 11/023,983, Amendment and Response filed Oct. 29, 2007, 13 pages. |
| U.S. Appl. No. 11/362,034, Amendment and Response filed Apr. 10, 2009, 10 pages. |
| U.S. Appl. No. 11/362,034, Amendment and Response filed May 7, 2010, 12 pages. |
| U.S. Appl. No. 11/362,034, Amendment and Response filed Aug. 29, 2008, 10 pages. |
| U.S. Appl. No. 11/362,034, Amendment and Response filed Sep. 25, 2009, 13 pages. |
| U.S. Appl. No. 11/410,323, Amendment and Response filed Sep. 29, 2008, 16 pages. |
| U.S. Appl. No. 12/266,690, Amendment and Response filed Jun. 9, 2011, 17 pages. |
| U.S. Appl. No. 12/266,690, Amendment and Response filed Nov. 21, 2011, 8 pages. |
| U.S. Appl. No. 12/266,690, Appeal Brief filed Feb. 22, 2012, 41 pages. |
| U.S. Appl. No. 12/644,711, Amendment and Response filed Apr. 3, 2012, 13 pages. |
| U.S. Appl. No. 12/644,711, Amendment and Response filed Oct. 31, 2011, 10 pages. |
| U.S. Appl. No. 12/722,755, Amendment and Response filed May 7, 2013, 16 pages. |
| U.S. Appl. No. 12/722,755, Amendment and Response filed Aug. 24, 2012, 20 pages. |
| U.S. Appl. No. 12/722,755, Amendment and Response filed Dec. 20, 2011, 25 pages. |
| U.S. Appl. No. 12/722,755, Non-Final Rejection mailed Feb. 7, 2013, 19 pages. |
| U.S. Appl. No. 12/729,797, Amendment and Response filed May 22, 2013, 12 pages. |
| U.S. Appl. No. 12/729,797, Amendment and Response filed Oct. 4, 2012, 10 pages. |
| U.S. Appl. No. 12/729,797, Final Rejection mailed Feb. 22, 2013, 14 pages. |
| U.S. Appl. No. 13/035,052, Amendment and Response filed May 6, 2013 (16 pages). |
| U.S. Appl. No. 13/035,052, Non-Final Rejection mailed Feb. 6, 2013 (12 pages). |
| Hoem, Torstein et al. “An Infrastructure for Community Walls,” Norwegian University of Science and Technology, Nov. 21, 2002, 84 pgs. |
| U.S. Appl. No. 12/722,755, Amendment and Response filed Nov. 8, 2013, 18 pages. |
| U.S. Appl. No. 13/035,052, Amendment After NOA filed Nov. 19, 2013, 3 pages. |
| Rosenberg, J. and Mark Day, “A Model for Presence and Instant Messaging.” (2000). |
| U.S. Appl. No. 12/722,755, Amendment and Response filed Aug. 11, 2014, 14 pages. |
| U.S. Appl. No. 13/317,023, Amendment and Response filed Aug. 5, 2014, 23 pages. |
| U.S. Appl. No. 13/547,227, Non-Final Rejection mailed Jul. 18, 2014, 17 pages. |
| Introduction to Active Directory Application Mode, Microsoft Corporation; Microsoft Windows Server 2003, (Aug. 2002),16 pages. |
| Screenshot demonstration of Yahoo Messenger Help, IMVironnments, (Nov. 12, 2002), 1 page. |
| Non-Final Office Action, U.S. Appl. No. 11/023,983, (Sep. 8, 2008), 12 pages. |
| Yahoo! Messenger Makes the World a Little Smaller, More Informed, (Jun. 21, 1999), 2 pages. |
| U.S. Appl. No. 12/729,797, Amendment and Response filed Apr. 20, 2014, 16 pages. |
| U.S. Appl. No. 13/035,035, Amendment and Response filed Jun. 26, 2014, 8 pages. |
| U.S. Appl. No. 12/722,755, Non-Final Rejection mailed Apr. 25, 2014, 18 pages. |
| U.S. Appl. No. 12/722,755, Amendment and Response filed Feb. 11, 2015, 18 pages. |
| U.S. Appl. No. 12/729,797, Non-Final Office Action mailed Feb. 26, 2015, 15 pages. |
| U.S. Appl. No. 12/729,797, Final Office Action mailed Aug. 29, 2014, 14 pages. |
| U.S. Appl. No. 13/035,035, Non-Final Office Action mailed Sep. 23, 2014, 11 pages. |
| U.S. Appl. No. 14/226,492, Non-Final Office Action mailed Sep. 16, 2014, 14 pages. |
| U.S. Appl. No. 13/317,023, Final Office Action mailed Oct. 16, 2014, 30 pages. |
| U.S. Appl. No. 12/722,755, Non-Final Office Action mailed Nov. 14, 2014, 17 pages. |
| U.S. Appl. No. 13/547,227, Amendment and Response filed Oct. 29, 2014, 11 pages. |
| U.S. Appl. No. 14/226,492, Amendment and Response filed Dec. 8, 2014, 15 pages. |
| U.S. Appl. No. 14/226,492, Final Office Action mailed Dec. 24, 2014, 16 pages. |
| U.S. Appl. No. 12/729,797, Amendment and Response filed Jan. 7, 2015, 14 pages. |
| U.S. Appl. No. 13/547,227, Final Office Action Dec. 19, 2014, 14 pages. |
| U.S. Appl. No. 13/035,035, Amendment and Response filed Jan. 20, 2015, 10 pages. |
| U.S. Appl. No. 13/547,227, Amendment and Response filed Mar. 19, 2015, 11 pages. |
| U.S. Appl. No. 12/722,755, Final Office Action mailed Apr. 9, 2015, 18 pages. |
| U.S. Appl. No. 13/035,035, Non-Final Office Action mailed Apr. 20, 2015, 10 pages. |
| U.S. Appl. No. 13/547,227, Non-Final Rejection mailed Apr. 23, 2015, 14, pages. |
| U.S. Appl. No. 14/226,492, Amendment and Response filed Jun. 19, 2015, 17 pages. |
| U.S. Appl. No. 14/226,492, Non-Final Rejection mailed Jul. 6, 2015, 17 pages. |
| U.S. Appl. No. 12/729,797, Amendment and Response filed Jun. 26, 2015, 14 pages. |
| U.S. Appl. No. 13/035,035, Amendment and Response filed Jul. 1, 2015, 8 pages. |
| U.S. Appl. No. 13/547,227, Amendment and Response filed Aug. 24, 2015, 13 pages. |
| U.S. Appl. No. 14/226,492, Amendment and Response filed Oct. 8, 2015, 15 pages. |
| U.S. Appl. No. 12/729,797, Final Rejection mailed Oct. 8, 2015, 15 pages. |
| U.S. Appl. No. 13/035,035, Notice of Allowance mailed Sep. 10, 2015, 8 pages. |
| U.S. Appl. No. 13/035,035, Notice of Allowance mailed Sep. 30, 2015, 2 pages. |
| Number | Date | Country | |
|---|---|---|---|
| 20120089924 A1 | Apr 2012 | US |
| Number | Date | Country | |
|---|---|---|---|
| 60427941 | Nov 2002 | US | |
| 60464106 | Apr 2003 | US | |
| 60488399 | Jul 2003 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 10847463 | May 2004 | US |
| Child | 13317023 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 10715209 | Nov 2003 | US |
| Child | 10847463 | US |
