U.S. patent application number 12/722755 was filed with the patent office on 2010-07-08 for rendering destination instant messaging personalization items before communicating with destination.
This patent application is currently assigned to AOL INC.. Invention is credited to Brian Heikes, James A. Odell, Justin Uberti, Andrew L. Wick, Xiaoyan Yin, Xiaopeng Zhang.
Application Number | 20100174996 12/722755 |
Document ID | / |
Family ID | 46150260 |
Filed Date | 2010-07-08 |
United States Patent
Application |
20100174996 |
Kind Code |
A1 |
Heikes; Brian ; et
al. |
July 8, 2010 |
Rendering Destination Instant Messaging Personalization Items
Before Communicating With Destination
Abstract
Perception of a personalization item in an instant messaging
communications session may be enabled by perceiving an identifier
corresponding to an intended instant message recipient designated
by an instant message sender system, accessing personalization
items corresponding to the perceived identifier, and making
perceivable the personalization items corresponding to the received
identifier to the instant messaging sender system for rendering in
an instant messaging application running on the instant messaging
sender system, where the personalization items are made perceivable
prior to communication with the intended instant message
recipient.
Inventors: |
Heikes; Brian; (Ashburn,
VA) ; Odell; James A.; (Potomac Falls, VA) ;
Uberti; Justin; (Sterling, VA) ; Wick; Andrew L.;
(McLean, VA) ; Yin; Xiaoyan; (Fairfax Station,
VA) ; Zhang; Xiaopeng; (Oak Hill, VA) |
Correspondence
Address: |
FISH & RICHARDSON P.C.
P.O. BOX 1022
MINNEAPOLIS
MN
55440-1022
US
|
Assignee: |
AOL INC.
Dulles
VA
|
Family ID: |
46150260 |
Appl. No.: |
12/722755 |
Filed: |
March 12, 2010 |
Related U.S. Patent Documents
|
|
|
|
|
|
Application
Number |
Filing Date |
Patent Number |
|
|
10334027 |
Dec 31, 2002 |
7689649 |
|
|
12722755 |
|
|
|
|
10305015 |
Nov 27, 2002 |
|
|
|
10334027 |
|
|
|
|
60416902 |
Oct 9, 2002 |
|
|
|
60384147 |
May 31, 2002 |
|
|
|
Current U.S.
Class: |
715/745 ;
709/206; 715/752 |
Current CPC
Class: |
H04L 51/04 20130101;
G06Q 10/107 20130101; H04L 67/24 20130101; H04L 67/36 20130101 |
Class at
Publication: |
715/745 ;
715/752; 709/206 |
International
Class: |
G06F 3/01 20060101
G06F003/01 |
Claims
1. A computer-implemented method for enabling perception of a
personalization item associated with an instant messaging
communications session, the method comprising: receiving, from an
instant message sender system, information that indicates a user
identifier of an intended instant message recipient, the user
identifier of the intended instant message recipient being selected
by an instant message sender from among one or more user
identifiers of potential instant message recipients, the potential
instant message recipients being users that are perceived by the
instant message sender as being presently available to receive an
instant message from the instant message sender; accessing the user
identifier of the intended instant message recipient based upon the
received information; accessing a personalization item based on the
accessed user identifier of the intended instant message recipient
and the personalization item being designated by the intended
instant message recipient based on presence state change of the
intended instant message recipient; making perceivable the accessed
personalization item to the instant messaging sender system for
rendering in an instant messaging application user interface
running on the instant messaging sender system; and rendering of
the personalization item in the user interface, wherein the
rendering includes rendering of a window.
2. A method of claim 1, wherein the rendering of the window
includes displaying the personalization item and an input text
field for inputting a text message by the instant message sender
for delivery to the intended instant message recipient in an
instant message, the displayed personalization item includes an
image item, wherein the rendering of the window makes the
personalization item and the input text field displayed to the
instant message sender prior to communication with the intended
instant message recipient, wherein the selection by the instant
message sender of the user identifier of the intended instant
message recipient is an indication of an intention of the instant
message sender to communicate with the intended instant message
recipient, and wherein the rendering of the window at the instant
messaging sender system occurs in response to the selection by the
instant message sender of the user identifier of the intended
instant message recipient from among the one or more user
identifiers of potential instant message recipients.
3. The method of claim 1 further comprising storing personalization
items on a host system.
4. The method of claim 1 in which accessing personalization items
comprises accessing personalization items on a host system.
5. The method of claim 4 further comprising communicating the
personalization items from the host system to the instant message
sender system.
6. The method of claim 1 in which the personalization items are
made perceivable prior to communication of an instant message with
the intended instant message recipient.
7. The method of claim 1 in which the personalization items are
made perceivable before a communications session is established
with the intended instant message recipient.
8. The method of claim 1 in which the personalization items are
made perceivable before the instant message sender system sends a
message to the intended instant message recipient.
9. The method of claim 1 in which the personalization items are
made perceivable before the instant message sender system receives
a message from the intended instant message recipient.
10. The method of claim 1 in which accessing the identifiers
comprises: receiving an identity of the potential instant message
recipients; and accessing an identifier associated with each of the
individual potential instant message recipients based upon the
received identity.
11. The method of claim 1 in which accessing the one or more
identifiers comprises receiving an identifier comprising a location
of the personalization item.
12. The method of claim 11 in which the location of the
personalization item comprises a location on a host system.
13. The method of claim 1 in which accessing personalization items
comprises accessing a graphic.
14. The method of claim 13 in which the graphic comprises an
icon.
15. The method of claim 1 in which accessing personalization items
comprises accessing a sound.
16. The method of claim 1 in which accessing personalization items
comprises accessing wallpaper capable of being rendered on an
instant messaging application user interface.
17. The method of claim 1 in which accessing personalization items
comprises accessing an animation sequence.
18. The method of claim 1 in which accessing personalization items
comprises accessing a video segment.
19. The method of claim 1 in which accessing personalization items
comprises accessing a customized binary object provided by the
intended instant message recipient.
20. The method of claim 1 in which accessing personalization items
comprises accessing a personalization item provided by a party
other than the intended instant message recipient.
21. The method of claim 20 in which accessing personalization items
comprises accessing a personalization item enabled to be rendered
in consideration of a payment.
22. The method of claim 1 in which accessing personalization items
comprises accessing a personalization item configured to expire
upon the occurrence of a predetermined event.
23. The method of claim 22 in which the predetermined event
comprises passage of a predetermined length of time or passage of a
predetermined date.
24. The method of claim 22 in which the predetermined event
comprises a predetermined number of uses of the personalization
item.
25. The method of claim 22 further comprising: determining whether
the personalization item has expired, and disallowing access to the
personalization item if the personalization item has expired.
26. The method of claim 11 in which the one or more identifiers
include an item type and a data size.
27. The method of claim 11 wherein the one or more identifiers
include a flag.
28. The method of claim 27 wherein the flag includes one or more of
a custom item flag, an official item flag, a banned item flag, and
a redirect to different item flag.
29. The method of claim 1 further comprising: determining whether
the personalization items have been banned, and disallowing access
to a personalization item if the personalization item has been
banned.
30. A computer program, stored on a tangible computer readable
storage medium, the computer program comprising instructions for:
receiving, from an instant message sender system, information that
indicates a user identifier of an intended instant message
recipient, the user identifier of the intended instant message
recipient being selected by an instant message sender from among
one or more user identifiers of potential instant message
recipients, the potential instant message recipients being users
that are perceived by the instant message sender as being presently
available to receive an instant message from the instant message
sender; accessing the user identifier of the intended instant
message recipient based upon the received information; accessing a
personalization item based on the accessed user identifier of the
intended instant message recipient and the personalization item
being designated by the intended instant message recipient based on
presence state change of the intended instant message recipient;
making perceivable the accessed personalization item to the instant
messaging sender system for rendering in an instant messaging
application user interface running on the instant messaging sender
system; and rendering of the personalization item in the user
interface, wherein the rendering includes rendering of a
window.
31. The computer program of claim 30, wherein the rendering of the
window includes displaying the personalization item and an input
text field for inputting a text message by the instant message
sender for delivery to the intended instant message recipient in an
instant message, the displayed personalization item includes an
image item, wherein the rendering of the window makes the
personalization item and the input text field displayed to the
instant message sender prior to communication with the intended
instant message recipient, wherein the selection by the instant
message sender of the user identifier of the intended instant
message recipient is an indication of an intention of the instant
message sender to communicate with the intended instant message
recipient, and wherein the rendering of the window at the instant
messaging sender system occurs in response to the selection by the
instant message sender of the user identifier of the intended
instant message recipient from among the one or more user
identifiers of potential instant message recipients.
32. The computer program of claim 30 further comprising
instructions for storing personalization items.
33. The computer program of claim 30 in which the personalization
items are made perceivable prior to communication of an instant
message with the intended instant message recipient.
34. The computer program of claim 30 in which the personalization
items are made perceivable before a communications session is
established with the intended instant message recipient.
35. The computer program of claim 30 in which the personalization
items are made perceivable before the instant message sender system
sends a message to the intended instant message recipient.
36. The computer program of claim 30 in which the personalization
items are made perceivable before the instant message sender system
receives a message from the intended instant message recipient.
37. The computer program of claim 30 in which instructions for
accessing the identifier comprises instructions for: receiving an
identity of the potential instant message recipients; and accessing
an identifier associated with the potential instant message
recipient based upon the received identity.
38. The computer program of claim 30 in which instructions for
accessing personalization items comprises instructions for
accessing a personalization item configured to expire upon the
occurrence of a predetermined event.
39. The computer program of claim 38 in which the predetermined
event comprises passage of a predetermined length of time or
passage of a predetermined date.
40. The computer program of claim 38 in which the predetermined
event comprises a predetermined number of uses of the
personalization item.
Description
[0001] This application claims priority to and is a continuation of
U.S. patent application Ser. No. 10/334,027, filed Dec. 31, 2002,
and titled "Rendering Destination Instant Messaging Personalization
Items Before Communicating With Destination," which claims priority
under 35 USC .sctn.119(e) to U.S. Provisional Application No.
60/384,147, filed May 31, 2002, and U.S. Provisional Application
No. 60/416,902, filed Oct. 9, 2002, and is a continuation-in-part
of U.S. application Ser. No. 10/305,015, filed Nov. 27, 2002, all
of which are incorporated by reference.
TECHNICAL FIELD
[0002] This description relates to instant messaging communications
and more particularly to personalization of instant messaging
communications for an instant message sender.
BACKGROUND
[0003] 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 for communicating using 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.
SUMMARY
[0004] In one general aspect, perception of a personalization item
in an instant messaging communications session may be enabled by
perceiving an identifier corresponding to an intended instant
message recipient designated by an instant message sender system,
accessing personalization items corresponding to the perceived
identifier, and making perceivable the personalization items
corresponding to the received identifier to the instant messaging
sender system for rendering in an instant messaging application
running on the instant messaging sender system, where the
personalization items are made perceivable prior to communication
with the intended instant message recipient.
[0005] Implementations may include one or more of the following
features. For example, one or more personalization items may be
stored. Personalization items may be accessed on a host system, and
also may be communicated from the host system to the instant
message sender system.
[0006] The personalization items may be made perceivable at times
including prior to communication of an instant message with the
intended instant message recipient system, before a communications
session is established with the intended instant message recipient
system, before the instant message sender system sends a message to
the intended instant message recipient system, and before the
instant message sender system receives a message from the intended
instant message recipient system.
[0007] Perceiving the identifier may include receiving an identity
of the intended instant message recipient and accessing an
identifier associated with the individual intended instant message
recipient based upon the received identity. Receiving the
identifier may also include receiving a location of the
personalization item, such as, for example, a location on the host
system. The identifier may also include an item type, a data size,
a flag such as a custom item flag, an official item flag, a banned
item flag, and a redirect to different item flag.
[0008] The personalization item may include a graphic, such as an
icon, a sound, wallpaper capable of being rendered on an instant
messaging application user interface, an animation sequence, a
video segment, and a customized binary object provided by the
intended instant message recipient. The personalization item may be
provided by a party other than the intended instant message
recipient, and may be enabled to be rendered in consideration of a
payment.
[0009] The personalization item may be configured to expire upon
the occurrence of a predetermined event including the passage of a
predetermined length of time or on passage of a predetermined date
or a predetermined number of uses. If it is determined that the
personalization item has expired, access to the personalization
item may be disallowed. If it is determined that the
personalization item has been banned, access to the personalization
item may be disallowed.
[0010] In another general aspect, perception of a personalization
item in an instant messaging communications session may be enabled
by rendering, on an instant message sender system, an instant
messaging application user interface for an instant messaging
communications session involving at least an intended instant
message recipient and an instant message sender and rendering, at
the instant message sender system, a personalization item
associated with the instant message recipient prior to
communication with the intended instant message recipient
system.
[0011] Implementations may include one or more of the following
features. For example, the personalization item may be rendered at
the instant message sender system prior to communication of an
instant message with the intended instant message recipient system,
before a communications session is established with the intended
instant message recipient system, before the instant message sender
system sends a message to the intended instant message recipient
system, or before the instant message sender system receives a
message from the intended instant message recipient system.
[0012] The identifier may be associated with the personalization
item, the personalization item may be obtained from a source other
than a message used to obtain the identifier, and the
personalization item may be rendered at the instant message sender
system. The identifier may include a location of the
personalization item. The identifier also may include an item type,
a data size, and a flag such as a custom item flag, an official
item flag, a banned item flag, or a redirect to different item
flag.
[0013] Obtaining the identifier may include sending an identity of
the intended instant message recipient to an instant message host
system, where the instant message host system stores one or more
identifiers associated with one or more personalization items for
the intended instant message recipient, and receiving an identifier
associated with the individual intended instant message recipient
in a message from the instant message host system. Obtaining the
identifier also may include locating the identifier at the intended
instant message recipient system and retrieving the identifier from
a remote data store.
[0014] Obtaining the personalization item may include determining
whether the personalization item associated with the received
identifier is available at the instant message sender system,
retrieving the personalization item from the instant message sender
system if the personalization item is available at the instant
message sender system, and requesting the personalization item from
a remote source and receiving the personalization item from the
remote source at the instant message sender system if the
personalization item is not available at the instant message sender
system. The identifier may be received upon a change in a presence
state of the intended instant message recipient.
[0015] The personalization item may include a graphic, such as an
icon, a sound, wallpaper capable of being rendered on an instant
messaging application user interface, an animation sequence, a
video segment, and a customized binary object provided by the
intended instant message recipient. The personalization item may be
provided by a party other than the intended instant message
recipient and may be enabled to be rendered in consideration of a
payment. The personalization item may be updated, and may be
configured to expire upon the occurrence of a predetermined event,
including the passage of a predetermined length of time or on
passage of a predetermined date or a predetermined number of uses.
If it is determined that the personalization item has expired,
display of the personalization item may be disallowed. If it is
determined that the personalization item has been banned, display
of the personalization item may be disallowed.
[0016] Requesting the personalization item may include identifying
the remote source, requesting the personalization item from an
instant messaging host, or requesting the personalization item from
a third-party server. The third-party server includes a server
authorized as a partner to an instant messaging host. The
personalization item may include any of the items noted above. The
personalization item may be provided by a third party, and may be
enabled to be rendered in consideration of a payment. The
personalization item also may be configured to expire upon the
occurrence of a predetermined event such as, for example, the
passage of a predetermined length of time, the passage of a
predetermined date, or a predetermined number of uses.
[0017] Aspects of the IM personalization 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 IM personalization may be implemented in a
client/host context or in a standalone or offline client device.
The IM personalization items may be rendered in a client/host
context and may be accessed or updated through a remote device in a
client/host environment. The IM personalization items 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.
[0018] Other features will be apparent from the following
description, including the drawings, and from the claims.
DESCRIPTION OF DRAWINGS
[0019] FIGS. 1-4 are block diagrams of an exemplary communications
system.
[0020] FIGS. 5 and 10 are flow charts of exemplary processes that
may be implemented by systems such as those of FIGS. 1-4.
[0021] FIGS. 6-9 are illustrations of different graphical user
interfaces that may be implemented by systems such as those of
FIGS. 1-4 when executing processes such as those of FIGS. 5 and 10
and 11 and 12.
[0022] FIGS. 11 and 12 are flow charts of exemplary processes that
may be implemented by systems such as those of FIGS. 1-4.
[0023] Like reference symbols in the various drawings indicate like
elements. 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.
DETAILED DESCRIPTION
[0024] It is possible, through the systems and techniques described
herein, to make personalization items of an intended IM recipient
perceivable to an IM sender in a communications interface of the IM
sender (1) immediately upon opening the interface, (2) before
sending a message or other communication to the IM recipient,
and/or (3) before receipt of a message or other communication from
the IM recipient. As such, immediately upon opening a communication
interface and identifying a potential message recipient, an IM
sender may perceive a personalization item established for or
selected by that potential message recipient, which personalization
items may not otherwise be made available to the IM sender until
communications are sent or received with respect to that potential
message recipient.
[0025] Personalization items may represent a user or a
characteristic of the intended IM recipient, and may include
user-selectable binary objects. For example, personalization items
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 wallpaper. For example, the wallpaper may be
rendered in an area where messages from the IM recipient are to be
displayed, or as a chrome (i.e., border) around a dialog area on a
user interface. Personalization items also may include icons such
as buddy icons and mini-buddy icons, sounds, animation, video
clips, and emoticons (e.g., smileys). Personalization items for the
intended recipient may be known or unknown to the IM sender, and
they may or may not be stored at the IM sender system or be
otherwise associated with that IM sender prior to the communication
session in which they are displayed using the systems and
techniques described herein.
[0026] One or more personalization items of an intended IM
recipient may be rendered at the IM sender system. An identifier
corresponding to one or more personalization items of the IM
recipient is obtained by the IM sender. For instance, an identifier
may identify a particular personalization item, a group of
personalization items, or a user name or other identity may be
mapped to one or more personalization items or groups.
[0027] The IM sender system may use the identifier to identify one
or more personalization items associated with the IM recipient, and
to locate perceivable content corresponding to the identifier. For
instance, an identifier may be used as a basis for determining if
one or more corresponding personalization items are available
locally at the IM sender system, and, if so, the identifier may be
used to retrieve the corresponding personalization item(s). If the
personalization item(s) are not available locally at the IM sender
system, the IM sender system may use the identifier as a basis for
generating one or more requests for the personalization item(s)
from another location, such as an IM host system or another
remotely-accessible data store such as the IM recipient system, or
a remote or third-party server (e.g., a server accessible through
the Internet).
[0028] Identifiers may be retrieved before, during, or after
receipt of an instant message or other communication from the IM
recipient. For example, the identifiers may be retrieved upon the
opening of a communications user interface (UI) by the IM sender or
after opening of the UI but before receipt of an instant message or
other communication from the IM recipient.
[0029] The IM sender system may retrieve the identifiers from a
remote location such as those noted above. The identifiers may be
stored at the remote location and associated with a screen name or
other user identity of the IM recipient. The IM sender system may
send the screen name or other user identity of the IM recipient to
the remote location where it is then associated with the
corresponding identifiers of the IM recipient, and the IM sender
system may receive the corresponding identifiers from the remote
location. For instance, the IM host may store identifiers
associated with the screen name of an IM recipient. The IM sender
system passes the screen name of the IM recipient to the IM host,
and the IM host returns the identifiers associated with the passed
screen name to the IM sender system. In another implementation, a
remotely accessible data store may retrieve and send the
personalization items themselves to the IM sender rather than
sending the identifiers.
[0030] In another example, the IM sender system may locally store
the identifiers in association with a screen name or other user
identity of the IM recipient. The IM sender system may then
retrieve the locally-stored identifiers based on the screen name or
other user identity of the IM recipient. In another implementation,
the IM sender system may retrieve the personalization items
themselves rather than the identifiers.
[0031] Personalization items may be made available to the IM sender
system based on a selecting process. The personalization items to
be made perceivable to the IM sender may be selected manually by
the IM recipient or may be automatically selected for the IM
recipient. Identifiers for selected personalization items may be
associated with a screen name or other identifying information for
the IM recipient. For example, the identifiers associated with the
screen name of a potential IM recipient may be stored locally at
the IM sender system, or the IM sender system may retrieve such
identifiers from a remotely-accessible data store such as the IM
host system, the IM recipient system, or those noted above.
[0032] Personalization items of the IM recipient may be rendered to
the IM sender before correspondence is initiated or communications
are established by the recipient and without previously having
received an IM message from the IM recipient. Once the IM sender
system locates or receives the one or more personalization items
associated with a intended destination recipient, the IM sender
system renders the one or more personalization items for perception
by the IM sender. Also, the personalization items of the IM sender
may be rendered to the IM recipient in the manner described for
rendering the personalization items of the IM recipient to the IM
sender.
[0033] Typically, a personalization item is rendered upon the
occurrence of one or more particular events. For example, a
customized sound and/or a personalized icon or wallpaper selected
by an IM recipient may be made perceivable to an IM sender when the
IM sender initiates an IM communications session with the IM
recipient by, for example, opening an IM communications window. As
an example, a particular sound may be played or an icon may be
displayed at the IM sender system when changes are experienced in
presence or state of the IM recipient with whom they communicate
changes (e.g., when the IM recipient or other IM participant logs
on, logs off, becomes inactive, or enables or disables the IM
sender's ability to detect the IM recipient's presence).
[0034] In one implementation, the IM sender may not change the
personalization items of an IM recipient. An IM recipient may
choose to have different personalization items displayed for
different IM senders. Once a personalization item is designated by
an IM recipient, the personalization item is typically made
available for perception by the IM sender automatically. The
personalization items may also be selected automatically for an IM
recipient based upon a characteristic of the IM sender.
[0035] 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, although IM communications may occur in
the absence of online presence information, IM communications
generally involve the display and perception of online presence
information regarding other selected users ("buddies"). 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. Examples of IM communications exist
over AIM (America Online Instant Messenger), AOL (America Online)
Buddy List and Instant Messages, Yahoo Messenger, MSN Messenger,
and ICQ, among others. Although discussed below 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.
[0036] For illustrative purposes, FIGS. 1 and 2 show an example of
a communications system for implementing techniques for
transferring electronic data.
[0037] Referring to FIG. 1, a communications system 100 is capable
of delivering and exchanging data between an IM sender system 105
and a host system 110 through a communications link 115. The IM
sender system 105 typically includes one or more client devices 120
and/or client controllers 125, and the host system 110 typically
includes one or more host devices 135 and/or host controllers 140.
For example, the IM sender system 105 or the host system 110 may
include one or more general-purpose computers (e.g., personal
computers), one or more special-purpose computers (e.g., devices
specifically programmed to communicate with each other and/or the
IM sender system 105 or the host system 110), or a combination of
one or more general-purpose computers and one or more
special-purpose computers. The IM sender system 105 and the host
system 110 may be arranged to operate within or in concert with one
or more other systems, such as, for example, one or more LANs
("Local Area Networks") and/or one or more WANs ("Wide Area
Networks").
[0038] The client device 120 and the host device 135 are generally
capable of executing instructions under the command of,
respectively, a client controller 125 and a host controller 140.
The client device 120 and the host device 135 are connected to,
respectively, the client controller 125 and the host controller 140
by, respectively, wired or wireless data pathways 130 and 145,
which are capable of delivering data.
[0039] The client device 120, the client controller 125, the host
device 135, and the host controller 140 typically each include one
or more hardware components and/or software components. An example
of a client device 120 or a host device 135 is a general-purpose
computer (e.g., a personal computer) 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 120 and
the host device 135 may include devices that are capable of
establishing peer-to-peer communications.
[0040] An example of client controller 125 or host controller 140
is a software application loaded on the client device 120 or the
host device 135 for commanding and directing communications enabled
by the client device 120 or the host device 135. Other examples
include a program, a piece of code, an instruction, a device, a
computer, a computer system, or a combination of these for
independently or collectively instructing the client device 120 or
the host device 135 to interact and operate as described. The
client controller 125 and the host controller 140 may be embodied
permanently or temporarily in any type of machine, component,
physical or virtual equipment, storage medium, or propagated signal
capable of providing instructions to the client device 120 and the
host device 135.
[0041] The communications link 115 typically includes a delivery
network 160 that provides direct or indirect communication between
the IM sender system 105 and the host system 110, irrespective of
physical separation. Examples of a delivery network 160 include the
Internet, the World Wide Web, WANs, LANs, analog or digital wired
and wireless telephone networks (e.g., 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 115 may include communication pathways 150
and 155 that enable communications through the one or more delivery
networks 160 described above. Each of the communication pathways
150 and 155 may include, for example, a wired, wireless, cable or
satellite communication pathway.
[0042] FIG. 2 illustrates a communications system 200 including an
IM sender system 105 communicating with a host system 110 through a
communications link 115.
[0043] The IM sender system 105 includes a client device 120 that
typically includes a general-purpose computer 270 having an
internal or external memory 272 for storing data and programs such
as an operating system 274 (e.g., DOS, Windows.TM., Windows 95.TM.,
Windows 98.TM., Windows 2000.TM., Windows Me.TM., Windows XP.TM.,
Windows NT.TM., OS/2, or Linux) and one or more application
programs. Examples of application programs include authoring
applications 276 (e.g., word processing programs, database
programs, spreadsheet programs, or graphics programs) capable of
generating documents or other electronic content; client
applications 278 (e.g., 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 280 (e.g., Netscape's Navigator or Microsoft's
Internet Explorer) capable of rendering standard Internet content
and other content formatted according to standard protocols such as
the Hypertext Transfer Protocol (HTTP).
[0044] One or more of the application programs may be installed on
the internal or external storage 272 of the general-purpose
computer 270. Alternatively, in another implementation, the client
controller 125 may access application programs externally stored in
and/or performed by one or more device(s) external to the
general-purpose computer 270.
[0045] The general-purpose computer 270 also includes a central
processing unit 282 (CPU) for executing instructions in response to
commands from the client controller 125, and a communication device
284 for sending and receiving data. One example of the
communication device 284 is a modem. Other examples include a
transceiver, a set-top box, a communication card, a satellite dish,
an antenna, a network adapter, or some other mechanism capable of
transmitting and receiving data over the communications link 115
through a wired or wireless data pathway 150. The general-purpose
computer 270 optionally includes a television ("TV") tuner 286 for
receiving television programming in the form of broadcast,
satellite, and/or cable TV signals. The TV tuner 286 permits the
client device 120 to selectively and/or simultaneously display
network content received by communications device 284 and TV
programming content received by the TV tuner 286.
[0046] The general-purpose computer 270 may include an input/output
interface 288 that enables wired or wireless connection to various
peripheral devices 290. Examples of peripheral devices 290 include,
but are not limited to, a mouse 291, a mobile phone 292, a personal
digital assistant (PDA) 293, an MP3 player (not shown), a keyboard
294, a display monitor 295 with or without a touch screen input, a
TV remote control 296 for receiving information from and rendering
information to users, and an audiovisual input device 298.
[0047] Although FIG. 2 illustrates devices such as a mobile
telephone 292, a PDA 293, and a TV remote control 296 as being
peripheral with respect to the general-purpose computer 270, in
another implementation, such devices may themselves include the
functionality of the general-purpose computer 270 and operate as
the client device 120. For example, the mobile phone 292 or the PDA
293 may include computing and networking capabilities and function
as a client device 120 by accessing the delivery network 160 and
communicating with the host system 110. Furthermore, the IM sender
system 105 may include one, some or all of the components and
devices described above.
[0048] FIG. 3 illustrates a communications system 300 including an
IM sender system 105 communicating with an IM recipient system 305
and an IM host system 310 through a communication link 115. Such a
communications system may be used by users of IM service providers,
such as, for example, AIM, ICQ, Yahoo Messenger, and Microsoft
Messenger.
[0049] In one implementation, the IM host system 310 may have
characteristics similar to those described above with respect to
the host system 110, the IM recipient system 305 may have
characteristics similar to those described above with respect to
the IM sender system 105, and the IM sender system 105 and the IM
recipient system 305 may include communication software to enable
users of the client systems to access the IM host system 310.
[0050] The IM host system 310 may support IM services irrespective
of an IM sender's network or Internet access. Thus, the IM host
system 310 may allow users to send and receive IMs, regardless of
whether they have access to any particular ISP. The IM host system
310 also may support associated services, such as administrative
matters, advertising, directory services, chat, and interest groups
related to the IM. The IM host system 310 has an architecture that
enables the devices (e.g., servers) within the IM host system 310
to communicate with each other. To transfer data, the IM host
system 310 employs one or more standard or exclusive IM
protocols.
[0051] To access the IM host system 310 to begin an IM session in
the implementation of FIG. 3, the IM sender system 105 establishes
a connection to the IM host system 310. Once a connection to the IM
host system 310 has been established, the IM sender system 105 may
directly or indirectly transmit data to and access content from the
IM host system 310. By accessing the IM host system, an IM sender
can use the IM client application to view whether particular users
("buddies") are online, exchange IMs with particular buddies,
participate in group chat rooms, trade files such as pictures,
invitations or documents, find other buddies with similar
interests, get customized information such as news and stock
quotes, and search the Web. IM recipient system 305 may be
similarly manipulated to establish contemporaneous connection with
IM host system 310.
[0052] Once connectivity is established, an IM sender who is using
IM sender system 105 may view whether an IM recipient using IM
recipient system 305 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.
[0053] In one implementation, the IMs sent between IM sender system
105 and IM recipient system 305 are routed through IM host system
310. In another implementation, the IMs sent between IM sender
system 105 and IM recipient system 305 are routed through a third
party server (not shown), and, in some cases, are also routed
through IM host system 310. In yet another implementation, the IMs
are sent directly between IM sender system 105 and IM recipient
system 305.
[0054] FIG. 4 illustrates a communications system 400 including an
IM sender system 105 communicating with an IM recipient system 305
and an IM host system 310 through a communication link 115. System
400 illustrates a possible implementation of the communications
system 300 of FIG. 3.
[0055] In system 400, the IM host system 310 includes a login
server 470 for enabling access by users and routing communications
between the IM sender system 105 and other elements of the IM host
system 310. The IM host system 310 also includes an IM server 490.
To enable access to and facilitate interactions with the IM host
system 310, the IM sender system 105 and the IM recipient system
305 may include communication software, such as for example, an OSP
client application and/or an IM client application.
[0056] As described with respect to FIG. 3, the IM host system 310
may support IM services irrespective of an IM sender's network or
Internet access. Thus, the IM host system 310 may allow users to
send and receive IMs, regardless of whether they have access to any
particular ISP. The IM host system 310 also may support associated
services, such as administrative matters, advertising, directory
services, chat, and interest groups related to the IM. The IM host
system 310 has an architecture that enables the devices (e.g.,
servers) within the IM host system 310 to communicate with each
other. To transfer data, the IM host system 310 employs one or more
standard or exclusive IM protocols.
[0057] In one implementation, the IM sender system 105 establishes
a connection to the login server 470 in order to access the IM host
system 310 and begin an IM session. The login server 470 typically
determines whether the particular IM sender is authorized to access
the IM host system 310 by verifying the IM sender's identification
and password. If the IM sender is authorized to access the IM host
system 310, the login server 470 usually employs a hashing
technique on the IM sender's screen name to identify a particular
IM server 490 within the IM host system 310 for use during the IM
sender's session. The login server 470 provides the IM sender
(e.g., IM sender system 105) with the IP address of the IM server
490, gives the IM sender system 105 an encrypted key, and breaks
the connection. The IM sender system 105 then uses the IP address
to establish a connection to the particular IM server 490 through
the communications link 115, and obtains access to the IM server
490 using the encrypted key. Typically, the IM sender system 105
will be able to establish an open TCP connection to the IM server
490. The IM recipient system 305 establishes a connection to the IM
host system 310 in a similar manner.
[0058] In one implementation, the IM sender system 105 may directly
or indirectly transmit data to and access content from the IM
server 490 once a connection to the IM server 490 has been
established. By accessing the IM server, an IM sender can leverage
the IM client application to determine whether particular users
("buddies" or potential IM recipients) are online, exchange IMs
with particular buddies, participate in group chat rooms, trade
files such as pictures, invitations or documents, find other
buddies with similar interests, get customized news and stock
quotes, and search the Web. For example an IM sender who is using
IM sender system 105 may view whether a buddy using IM recipient
system 305 is online, and if so, may exchange IMs with that buddy.
In one implementation, the IMs sent between IM sender system 105
and IM recipient system 305 are routed through IM host system 310.
In another implementation, the IMs sent between IM sender system
105 and IM recipient system 305 are routed through a third party
server (not shown) and, in some cases, are also routed through IM
host system 310. In yet another implementation, the IMs are sent
directly between IM sender system 105 and IM recipient system
305.
[0059] In one implementation, the IM host system 310 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
recipient's profile data includes, for example, the IM recipient's
screen name, buddy list, identified interests, and geographic
location. The IM recipient may enter, edit and/or delete profile
data using an installed IM client application on the IM recipient
system 305 to interact with the user profile server.
[0060] FIGS. 5, 10, 11, and 12 illustrate exemplary procedures 500,
1000, 1100, and 1200 to make a personalization item selected by an
intended IM destination recipient perceivable to the IM sender
during an instant messaging communications session, and, in
particular, to render the personalization item associated with an
intended IM recipient to the IM sender prior to the communication
of an instant message with the intended recipient system.
[0061] Procedures 500, 1000, 1100, and 1200 generally involve
rendering a personalization item and may be implemented by any type
of hardware, software, device, computer, computer system,
equipment, component, program, application, code, storage medium,
or propagated signal. In one implementation, a host 110 may be used
in place of the IM host 310. Furthermore, although not shown in
FIGS. 5, 10, 11, and 12, the IM sender system 105 and the IM host
system 310 may be directly or indirectly interconnected through
known or described delivery networks, examples of which are
described with respect to network 160.
[0062] The procedures 500, 1000, 1100, and 1200 may be implemented
in a client/host context, or a standalone or offline client
context. For example, while some functions of procedures 500, 1000,
1100, and 1200 may be performed entirely by the IM sender system
105, other functions may be performed by the IM host system 310 or
the collective operation of the IM sender system 105 and the IM
host system 310. For instance, a personalization item may be
rendered entirely by the IM sender system 105, or the
personalization item may be rendered based upon information
provided to the IM sender system 105 by the IM host system 310.
[0063] The personalization item 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. Thus, the procedures 500, 1000, 1100, and 1200
described below may be implemented for any 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.
[0064] Referring to FIG. 5, in the procedure 500, the IM sender
opens an IM application on the IM sender system 105 (step 505).
FIG. 6 describes an exemplary interface available to the IM sender,
which may be used to open an IM application on the IM sender system
and which will be described below.
[0065] Next, an intended destination recipient (hereinafter "IM
recipient") is selected (step 510). FIG. 6 illustrates an exemplary
interface available to the IM sender, which will be described
below, and which may be used to select an intended destination
recipient.
[0066] Next, an IM user interface (UI) is opened to enable
selection of information to be communicated to the intended
destination (step 515). FIG. 7 describes an exemplary interface
available to the IM sender, which may be used to open an IM user
interface, and which will be described below.
[0067] Finally, the personalization items associated with the
selected IM recipient are rendered in the IM UI (step 520). FIGS. 8
and 9 describe exemplary interfaces available to the IM sender
which may be used when rendering the personalization items of the
selected IM recipient, and which will be described below.
[0068] The IM recipient may have chosen a personalization item from
a location including the IM recipient system 305, the IM host
system 310, or another host system. When the IM recipient chooses a
personalization item that is locally stored on the IM recipient
system 305, an identifier may be created for the chosen
personalization item based upon a hash of the item data. The
identifier, when sent to the a remote location such as the IM host
310, may be checked to determine if the chosen personalization item
is already known to the host system, and if so, whether the
personalization item is designated as, for example, an official
item. This allows the IM recipient to select personalization items
from the IM recipient's own client system, but prevents the host
system or other remote location from needing to store duplicate
copies of the same items. Also, the host system or other remote
location is able to determine if such items are specially
designated as, for example, official items and may be rendered to
users who desire to view only items so designated.
[0069] FIG. 6 illustrates an example of a UI 600 that may be
presented to a user of an online service provider. The UI 600
includes a toolbar 602 for quickly enabling activation of features
such as, for example, reading or writing e-mail, exchanging IM
messages with another user, entering chat areas with other users,
shopping or accessing the internet. The toolbar 602 may include one
or more general interface actionable items 620-660, each of which
is configured to enable activation of an associated user interface.
An actionable item may be, for example, a button or a tab. For
example, general actionable item 620 is configured to enable
activation of an IM application and associated Instant Message (IM)
user interface (UI) 670. A buddy list 625 is provided, and includes
a list of other potential IM recipient. As shown, the IM sender is
able to initiate and view a communications session with IM
recipient "SurfinDiane" 625a.
[0070] FIG. 7 illustrates one example of an IM UI 700 that may be
presented to an IM sender of an IM service provider. The UI 700 may
be rendered after opening an IM application. In general, the UI 700
is rendered on the IM sender system 105 using software stored on
the IM sender system 105.
[0071] The UI 700 includes an IM display area 705 to display the
messages 705a of an active IM session. In the example of FIG. 7,
the active IM session involves a conversation initiated by the IM
sender having a screen name of "ChattingChuck" with the IM sender
having a screen name of "SurfinDiane." An IM compose area 710 may
be used to compose a message to send to the IM sender in the active
IM session, and the message typically is sent by clicking on the
send control button 715 in the UI. A control button 720 may be
provided to close the active IM session.
[0072] The UI 700 includes personalization items 707 and 709 from
the IM recipient and personalization items 712 and 714 from the IM
sender. In particular, as shown in FIG. 7, the IM recipient
"SurfinDiane" has made IM wallpaper 707 and a buddy icon 709
perceivable to the IM sender "ChattingChuck."
[0073] Personalization items 707 and 709 of the IM recipient may be
made available to the IM sender upon activating UI 700 and without
having to wait to receive a communication such as an instant
message from the IM recipient. The IM sender system 105 selects the
identifiers corresponding to the personalization items 707 and 709
of the IM recipient. The identifiers may be associated with a
screen name or other identifying information of the IM recipient.
For example, the identifiers may be associated with the screen name
of the IM recipient and stored locally at the IM sender system 105,
or the IM sender system may retrieve the identifiers associated
with the screen name of the IM recipient from another location such
as the IM host system 310 or another remotely-accessible data store
such as the IM recipient system 305 or a remote or third-party
server.
[0074] The IM sender system 105 uses the identifiers to determine
if the corresponding personalization items are available locally at
the IM sender system, and if so, the IM sender system retrieves the
corresponding personalization items. If the personalization items
are not available locally at the IM sender system 105, the IM
sender system requests the personalization items from another
location such as an IM host system 310 or another
remotely-accessible data store. Once the IM sender system 105
locates or receives the personalization items of the IM recipient,
the IM sender system renders the items on UI 700 for perception by
the IM sender.
[0075] Examples of IM UN 600, 700 are shown with respect to FIGS. 6
and 7. In one implementation, the IM user interface is opened after
the IM recipient is selected. In another implementation, the IM
user interface is opened before the IM recipient is selected. In
yet another implementation, the IM user interface is opened
simultaneously with the selection of the IM recipient.
[0076] FIG. 8 illustrates yet another example of an IM UI 800 that
may be presented to an IM sender of an IM service provider. One or
more personalization items may be provided for the IM UI. The
personalization items may be rendered to the IM sender as described
above with respect to FIG. 5.
[0077] In the example of FIG. 8, personalization items of an IM
recipient "AIMUIGIRL" 805, 810, 820, and 825 may be made
perceivable to the IM sender in the manner described above with
respect to FIGS. 5, 7, and 10. In particular, the personalization
items of the IM recipient to be made perceivable to the IM sender
prior to receipt of a communication from the IM recipient include a
sidebar image 805, a background image 810, a buddy icon 820, and a
sound (not shown). The sidebar image 805 may include images and
links to content. The background image 810 may include an image,
and typically is a washed out image. The buddy icon 820 typically
is an image. The sound may be a sound or a sequence of sounds
played to the IM sender.
[0078] FIG. 9 is an example of an instant messaging buddy list UI
900 that enables an IM sender of an instant messaging service to,
among other things, perceive the presence state of other buddies
that the IM sender has added to a buddy list, and to send instant
messages to buddies on the buddy list. The buddy list rendered to
the IM sender may include personalization items of an IM recipient
such as a buddy list bar 905, a buddy list image 910, a buddy list
background image 915, and a buddy list fill pattern 920.
[0079] The buddy list bar 905 may contain personalized links 905a,
905b, 905c, and 905d to content and may have a customized
appearance. The buddy list image 910 and the buddy list background
image 915 may be, for example, image files. The buddy list
background image 915 may have a washed out appearance. The buddy
list fill pattern 920 may be a color or pattern background for the
buddy list, or may also be an image. The transmission of the buddy
list personalization items of a selected buddy for rendering on the
IM sender system may occur during machine-to-machine communications
that are not visible to the user.
[0080] As shown, the buddy list 900 includes buddies 925a, 925b,
925c that the IM sender has chosen to add to the buddy list.
Personalization items of a given IM recipient (i.e., a buddy) may
be displayed through manual selection by the IM sender, or the
personalization items of a given IM recipient may be selected
automatically for the IM sender such as, for example, when the IM
sender activates a UI to send an IM message to a selected IM
recipient.
[0081] For example, wallpaper or a different personalization item
reflective of settings established for a selected buddy may be
rendered on the buddy list 900 of the IM sender when the IM sender
rolls a mouse pointer over the name of the buddy 925a, 925b, 925c,
925d or otherwise specifies a buddy in the buddy list 900. In
another implementation, the IM sender may tie their wallpaper or
other personalization item setting to follow that of a selected
buddy on the buddy list 900. In other words, the wallpaper of the
IM sender may be set to follow that of a selected buddy, for
example buddy 925a, such that when buddy 925a makes a change to the
wallpaper or other personalization item, the resulting change is
reflected to the IM sender in the personalization items rendered
for the IM sender.
[0082] IM personalization items of the IM recipient may be rendered
by any type of hardware, software, device, computer, computer
system, equipment, component, program, application, code, storage
medium, or propagated signal. In one implementation, the IM
personalization items may be rendered in a client/host context, and
the IM personalization items may be accessed or updated through a
remote device in a client/host environment. In another
implementation, the IM personalization items may be implemented in
a standalone or offline client context. The IM personalization
items 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 (Local Area Network) server
serving an end user or a mainframe serving a terminal device.
[0083] Regarding FIG. 10, procedure 1000 shows one possible
implementation of rendering a personalization item associated with
the selected IM recipient (step 520), as described with respect to
FIG. 5. In procedure 1000, personalization items of the selected IM
recipient may be made available to the IM sender system and
rendered at the IM sender system based on identifiers corresponding
to the personalization items of the IM recipient, which may be
maintained or accessed by the IM host system 310.
[0084] In procedure 1000, the IM sender system 105 first sends the
identifier corresponding to the personalization item to the IM host
system 310 (step 1025). The identifiers may be associated with a
screen name or other identifying information of the IM recipient.
For example, the identifiers may be associated with the screen name
of the IM recipient and stored locally at the IM sender system, or
the IM sender system may retrieve the identifiers associated with
the screen name of the IM recipient from another location, such as
the IM host system or another remotely-accessible data store.
[0085] The IM host system 310 receives the identifier from the IM
sender system 105 (step 1030).
[0086] Next, the IM host system 310 looks up the personalization
item(s) associated with the identifier (step 1035), and retrieves
the personalization item(s) corresponding to the identifier (step
1040). In other words, the IM sender system uses the identifier to
determine if the corresponding personalization item is available
locally at the IM sender system, and if so, the IM sender system
retrieves the corresponding personalization item. When the
personalization item is not available locally at the IM sender
system, the IM sender system 105 requests the personalization item
by sending the selected identifier to the IM host system 310 or
another remotely-accessible data store (not shown). Alternatively,
the personalization item itself may be associated with the IM
recipient and retrieved by the IM sender system 105.
[0087] Ultimately, the personalization item(s) are returned to the
IM sender system 105 (step 1045).
[0088] The corresponding personalization item(s) are received by
the IM sender system 105 (step 1050). Receiving the corresponding
personalization item may include saving (e.g., caching) the
personalization item in a memory or other storage at the local IM
sender system 105.
[0089] Finally, the IM UI is populated with the personalization
item(s) (step 1055). That is, once the IM sender system locates or
receives the personalization item, the IM sender system renders the
item for perception by the IM sender. As shown with respect to FIG.
7, the personalization items to be populated may include a buddy
icon 709 or IM wallpaper 707.
[0090] The relative order of steps 505-530 with respect to other
steps in procedure 500, and the relative order of steps 1025-1055
with respect to other steps in procedure 1000, and also with
respect to each other, may vary. Also, certain steps may be omitted
entirely, as appropriate.
[0091] FIGS. 11 and 12 show one possible implementation of the
procedures discussed with respect to FIGS. 5 and 10. The IM sender
system 105 and the IM host system 310 interact according to
exemplary procedures 1100 and 1200 to make a personalization item
selected by the IM recipient perceivable to the IM sender during an
instant messaging communications session. FIGS. 11 and 12 differ
from FIGS. 5 and 10 in that personalization items are made
available in response to a triggering event (e.g., a detected
change in presence of a user being monitored) rather than in
response to invocation of an application or application
interface.
[0092] Referring to FIG. 11, in the procedure 1100, the IM sender
system 105 and the IM host system 310 are physically and/or
logically connected (step 1105). For instance, IM sender system 105
may connect to the IM host system 310 across a network (e.g.,
network 160) by supplying an IM sender identification and password
to a server (e.g., a login server) in order to obtain access to the
IM host system 310.
[0093] Next, the presence state or presence state change of the IM
recipient system 305, e.g., login state, is detected by the IM host
system 310 (step 1108). The IM host system 310 may detect presence
states or state changes, such as, for example, when the IM
recipient signs out, is inactive for a period of time, becomes
active after having been inactive for a period of time, indicates
an ability to receive instant messages, or indicates an inability
to receive instant messages. A pool of potential IM recipients may
be monitored and associated with the screen name of a sender
through use of a buddy list or similar mechanism. Alternatively,
the entire user base may be monitored or some intelligent method of
monitoring potential IM recipients may be used. The IM sender may
select one or more IM recipient to whom the IM sender may wish to
send an instant message.
[0094] After detecting the presence state or state change of the IM
recipient system 305, the IM host system 310 may send or otherwise
make accessible to the IM sender system 105 and other IM systems a
notification of the IM recipient presence state change or state
change (step 1114). Sending notification of the presence state
change may include sending an identifier corresponding to a
personalization item selected by the IM recipient system 305. For
example, the IM host system 310 may send an identifier
corresponding to a sound chosen by the IM recipient for the
presence state change.
[0095] In one implementation, the IM host system 310 assigns an
identifier to the personalization item. In another implementation,
the IM recipient system 305 assigns the identifier to the
personalization item. In yet another implementation, the identifier
is assigned by a host system other than the IM host system 310.
[0096] The identifier typically includes information allowing the
corresponding personalization item to be located and retrieved. For
example, the identifier may include a location of the
personalization item. The identifier also may include a type
identifier that identifies the personalization item as, for
example, an icon, an IM wallpaper, an emoticon, or a sound. The
type identifier also may include a file format of the
personalization item. Also, the identifier may include one or more
flags to indicate, for example, if the personalization item is a
custom item or an "official" item, has been banned, or has expired.
Another flag may redirect the sender to a different personalization
item. The identifier may further include information concerning the
size of the personalization item. The identifier may be in a
predetermined format and may be of a predetermined length.
[0097] The IM sender system 105 receives the notification from the
IM host system 310 (step 1116). In the above example, receiving the
notification may include receiving an identifier corresponding to a
personalization item selected by the IM recipient system 305.
[0098] Next, the IM sender system 105 determines whether the
corresponding personalization item is locally available (step
1118). For example, the IM sender system 105 may have stored the
personalization in a local memory or another local storage
location. The IM sender system uses the identifier to determine
whether the corresponding personalization item is locally
available. For instance, the identifier may contain the location at
which the corresponding personalization item is stored.
[0099] If the corresponding personalization item is available
locally, the IM sender system retrieves the corresponding
personalization item (step 1120) and renders the personalization
item (step 1130).
[0100] Otherwise, if the corresponding personalization item is not
available locally, the IM sender system 105 requests the
corresponding personalization item from the IM host system 310 or a
location otherwise specified by or inferred from the identifier
(step 1122). That is, the IM sender system 105 may request the
corresponding personalization item from another location such as
the IM recipient system 305 or a remote, third party server.
Requesting the corresponding personalization item may include
sending the identifier associated with the personalization item to
the IM host system 310 along with a request to download the
personalization item to the IM sender system 105.
[0101] When the IM host system 310 receives the request for a
personalization item from the IM sender system (step 1124), the IM
host system 310 provides the corresponding personalization item to
the IM sender system (step 1126). Receiving the request may include
having the IM host system 310 receive the identifier associated
with the personalization item along with a request to download the
personalization item to the IM sender system 105.
[0102] Next, the corresponding personalization item is received by
the IM sender system (step 1128), which may save the
personalization item in a memory or other storage at the local IM
sender system 105. Then, the personalization item is rendered (step
1130). For example, as discussed with respect to FIG. 9, the
personalization items may include personalization items for a buddy
list UI 900.
[0103] Referring to FIG. 12, in procedure 1200, an instant message
application is opened by the IM sender system 105 (step 1235), in a
similar manner to that discussed with respect to step 505 of FIG.
5. The IM sender may also open an IM UI, such as the UI 700 shown
in FIG. 7 and select an intended destination recipient, as
discussed above with respect to steps 510 and 515 of FIG. 5. In one
implementation, rather than relying on a mechanism such as a buddy
list or a state change to identify users for which personalization
items will be made available, a mechanism identifies the users for
which personalization items will be made available based on users
selected by the IM senders for communications.
[0104] To make the personalization items of the IM recipient (for
example personalization items 707 and 709) available to the IM
sender (for example, in UI 700), the IM sender system 105 selects
the identifiers corresponding to the personalization items (for
example, 707 and 709) of the IM recipient. The identifiers may be
associated with a screen name or other identifying information of
the IM recipient. As such, personalization items of the IM
recipient may be made available to the IM sender before the receipt
by the IM sender of an IM from the IM recipient.
[0105] The IM sender system 105 uses the identifiers to identify
the personalization item associated with the recipient, and to
locate perceivable content corresponding to the identifier.
[0106] Because various aspects of steps 1236-1250 are similar to
those discussed above with respect to steps 1116-1130 of procedure
1100, the following discussion of steps 1236-1250 is somewhat
abbreviated.
[0107] The IM sender system 105 obtains an identifier from the IM
host system 310 (step 1236) corresponding to the personalization
item selected by the IM sender system 105, as discussed above with
respect to step 1116.
[0108] Next, the IM sender system 105 determines whether the
corresponding personalization item is available locally (step
1238). As discussed above with respect to step 1118, the IM sender
system 105 may have stored the personalization in a local memory or
other local storage location. The IM sender system 105 uses the
identifier to determine whether the corresponding personalization
is available locally. For instance, the identifier may contain the
location at which the corresponding personalization item is
stored.
[0109] If the corresponding personalization item is available
locally, the IM sender system 105 retrieves the corresponding
personalization item (step 1240) and the personalization item is
rendered (step 1250).
[0110] Otherwise, if the corresponding personalization item is not
available locally, the IM sender system 105 requests the
corresponding personalization item from the IM host system 310
(step 1242). Alternatively, as discussed above with respect to step
1122, the IM sender system 105 may request the corresponding
personalization item from another location. In one implementation,
the personalization item may be provided by a third party, and may
be made available in consideration of a payment by the IM sender or
the IM recipient. Requesting the corresponding personalization item
may include sending to the IM host system 310 the identifier
associated with the personalization item along with a request to
download the personalization item to the IM sender system 105.
[0111] The IM host system 310 receives the request for the
personalization item from the IM sender system 105 (step 1244). As
discussed above with respect to step 1124, receiving the request
may include receiving the identifier associated with the
personalization item along with a request to download the
personalization item to the IM sender system 105. The IM host
system 310 provides the corresponding personalization item to the
IM sender system 105 (step 1246).
[0112] The corresponding personalization item is received by the IM
sender system 105 (step 1248). As discussed above with respect to
step 1128, receiving the corresponding personalization item may
include saving the personalization item in a memory or other
storage at the local IM sender system 105.
[0113] Finally, the personalization item is rendered (step 1250).
As discussed with respect to FIG. 7, the personalization item to be
rendered may include a buddy icon 709 or IM wallpaper 707.
[0114] The relative order of steps 1105-1130 with respect to other
steps in procedure 1100, and the relative order of steps 1235-1250
with respect to other steps in procedure 1200, and also with
respect to each other, may vary. Also, certain steps may be omitted
entirely, as appropriate. For example, referring to FIG. 11, if the
IM recipient has not chosen a personalization item to be sent to
the IM sender system 105 upon a presence state change, then no such
item will be sent and steps 1116-1130 may be eliminated
entirely.
[0115] In one implementation, a buddy icon of an IM recipient may
be shown in a buddy list, or other personalization items of an IM
recipient may be shown in a buddy list.
[0116] In another implementation, the IM recipient and/or the IM
sender pay a subscription fee to access/use certain personalization
items, and the personalization items may be provided by a third
party such as a server other than the IM host 310. In another
implementation, the personalization items 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 personalization item 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 personalization item is expired or banned, display of such
a personalization item will be disallowed and the user typically
will be required to choose a different personalization item.
[0117] Other implementations are within the scope of the following
claims. For example, one identifier could correspond to a group of
personalization items, or a personalization item could have more
than one identifier. As a further example, although the examples
above are given in an instant message context, other communications
systems with similar attributes may be used. For example,
personalization items 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 any
combination of these.
* * * * *