Patent application title: Personalization content sharing system and method
David Elliot Goldfarb (Beit Shemesh, IL)
Jonathan William Medved (Jerusalem, IL)
Jonathan William Medved (Jerusalem, IL)
IPC8 Class: AH04B138FI
Class name: Transmitter and receiver at same station (e.g., transceiver) radiotelephone equipment detail call alerting
Publication date: 2012-04-19
Patent application number: 20120094726
A method for playing video ringtones on a communication device of a user
includes a downloadable application on the communication device receiving
a video ringtone to be associated with a buddy of the user, the
communication device receiving a call-related triggering event related to
the buddy and in response to the call-related triggering event, the
communication device playing the video ringtone. A further method
includes the communication device receiving a call-related triggering
event related to a buddy of the user; and in response to the call-related
triggering event, the communication device activating a functionality of
the communication device.
1. A method for playing video ringtones on a communication device of a
user comprising: a downloadable application on said communication device
receiving a video ringtone to be associated with a buddy of said user;
said communication device receiving a call-related triggering event
related to said buddy; and in response to said call-related triggering
event, said communication device playing said video ringtone.
2. The method according to claim 1 and wherein said playing comprises: prioritizing playing of said video ringtone of said buddy for said call-related triggering event over ringtone playing by said phone application.
3. The method according to claim 1 and wherein said receiving comprises: said application receiving a download of said video ringtone and an indication that it is to be associated with said buddy; and said application providing said video ringtone to a contact list application not forming part of said application, for association with said buddy, such that upon said triggering event said contact list application initiates play of said video ringtone.
4. A method for activating a functionality on a communication device of a user comprising: said communication device receiving a call-related triggering event related to a buddy of said user; and in response to said call-related triggering event, said communication device activating said functionality.
5. The method according to claim 4 and wherein said functionality is related to said buddy of said user.
CROSS-REFERENCE TO RELATED APPLICATIONS
 This application is a continuation of U.S. Ser. No. 11/744,917, filed May 7, 2007, which is a continuation-in-part application of U.S. Ser. No. 11/544,938, filed Oct. 10, 2006, now issued as U.S. Pat. No. 7,761,816 on Jul. 20, 2010, which claims benefit from the following U.S. Provisional Patent Applications: 60/771,883, filed Feb. 10, 2006, 60/772,564, filed Feb. 13, 2006, 60/819,621, filed Jul. 11, 2006 and 60/841,233, filed Aug. 31, 2006, all of which are hereby incorporated in their entirety by reference.
FIELD OF THE INVENTION
 The present invention relates to communication devices generally and to personalization content sharing on the communication devices by a community of users in particular.
BACKGROUND OF THE INVENTION
 Cellular telephones are known in the art. Such devices were originally developed to provide mobile telephony services to users who for reasons of preference, convenience or circumstance required wireless connections to a public telephony network. The earliest cellular telephones were dedicated devices that lacked the capability to be used for other purposes.
 Recent cellular telephones have more advanced operating systems that enable users to enrich and personalize their mobile telephony experience. For example, users can display or play media content such as photos, video clips, and audio files.
 One of the most popular ways to personalize a mobile user's telephony experience is to select a unique audio ringtone to be played for incoming calls. The ringtone selected by the user overrides the default ringing sound selected by the telephone manufacturer.
 Some cellular telephones run software that supports the definition of unique ringtones for a specific contact or for groups of contacts.
 Some of these cellular telephones support user definition of a photo or video clip to display when an incoming call is received from a specific contact or group of contacts.
 The media files used for these personalization services are available from a variety of sources. A small selection of files is usually pre-loaded on the devices prior to their distribution. The devices also often come equipped with cameras and audio recorders that may be used to create such media files on the devices themselves. Files may also be transferred from other devices in the user's possession via a physical connection or a short range wireless connection technology such as Bluetooth or infra-red. Some media files are also typically downloaded "over the air" across an Internet connection via the connection supplied by the mobile network operator or other media content provider.
 Some cellular network operators have introduced "ringback" personalization services, which enable a mobile subscriber to define the audio clip that the network operator will play instead of the normal "ring" for someone calling the subscriber's phone number.
 Ringtones and Ringback tones are available in other systems as well. SIP (Session Initiation Protocol), which may be used to connect devices for a voice over IP (VoIP) connection, also provides an option for the selection of alternative tones. The alternative tone may be indicated by a URL (universal resource locator) that may be used to download the tone at the time the connection is made. The download may be performed using a different channel than the VoIP connection.
 "Endtone" personalization services may soon be offered by network operators. Endtones may include specialized disconnect tones to notify wireless device users that voice and data connections are terminated. Endtones have been announced by Endtone of the United States.
BRIEF DESCRIPTION OF THE DRAWINGS
 The subject matter regarded as the invention is particularly pointed out and distinctly claimed in the concluding portion of the specification. The invention, however, both as to organization and method of operation, together with objects, features, and advantages thereof, may best be understood by reference to the following detailed description when read with the accompanying drawings in which:
 FIG. 1 is a schematic illustration of a novel media content sharing system, constructed and operative in accordance with the present invention;
 FIG. 2 is a block diagram illustration of the method used by the system of FIG. 1;
 FIGS. 3A, 3B and 3C are illustrations of data files used by the system of FIG. 1;
 FIGS. 4A and 4B are schematic illustrations of exemplary mobile devices forming part of the system of FIG. 1;
 FIG. 5 is a schematic illustration of an alternative embodiment of the system of FIG. 1;
 FIG. 6 is a schematic illustration of a further alternative embodiment of the system of FIG. 1; and
 FIG. 7 is a schematic illustration of a multi-platform embodiment of the system of FIG. 1.
 It will be appreciated that for simplicity and clarity of illustration, elements shown in the figures have not necessarily been drawn to scale. For example, the dimensions of some of the elements may be exaggerated relative to other elements for clarity. Further, where considered appropriate, reference numerals may be repeated among the figures to indicate corresponding or analogous elements.
DETAILED DESCRIPTION OF THE PRESENT INVENTION
 In the following detailed description, numerous specific details are set forth in order to provide a thorough understanding of the invention. However, it will be understood by those skilled in the art that the present invention may be practiced without these specific details. In other instances, well-known methods, procedures, and components have not been described in detail so as not to obscure the present invention.
 Applicants have realized that there are several barriers to the introduction and success of systems that provide voice connections concurrent with the download and play of media files. Such barriers include, for example, the inability of many current mobile networks to provide concurrent voice and data connections to a single device. Certain variations of a relatively new mobile network technology, known as "3G", are capable of providing concurrent voice and data connections. However, 3G networks may still suffer from latency that may affect the quality when attempting to synchronize the download and play of media files with a voice connection. Furthermore, the repeated downloading of media files is often prohibitively expensive.
 Applicants have realized that creating a community to define media files to be played when two friends, or "buddies", communicate may provide the illusion of real time sharing of media content between the two buddies. Such media files may be downloaded to a buddy's device prior to the conversation.
 Reference is now made to FIG. 1, which illustrates a novel media content sharing system 100 capable of providing the illusion of real time sharing of media content between a novel communication device 110, owned by, for example, Jack, and a telephone 120, owned by, for example, Jill, who are simultaneously setting up or using a voice connection 140 for a telephone conversation.
 In accordance with one preferred embodiment of the present invention, Jack and Jill may both be members of a media content personalization sharing community 150, organized through a community server 130. Community server 130 may be a web server including, for example, a media file database 132.
 Members of community 150, such as Jack and Jill, who elect to share personalization content (i.e. media files, such as photos, audio clips and video clips) with each other are said to be "buddies." Typically, the buddy sets of the members are not the same.
 In a preferred embodiment of the present invention, individual members of community 150 may select (arrow 131) media content on community server 130 that they wish some or all of their buddies to see and/or hear. For example, Jill may select a media file 134. At some other time, each member may download (arrow 133), to their own devices 110, the selected media content of his/her buddies. Thus, Jack may download a version 136 of media file 134 to his device 110, where media file 136 may be a version of the file suitable for presentation to Jack on his device. It will be appreciated that such a download may be performed as an occasional automated procedure initiated by Jack's device 110, or as one initiated by Jack, or as one initiated by server 130 in response to new selection 131.
 Novel device 110 may be any suitable "smart phone" capable at least of providing telephony services, downloading data, and of presenting a variety of media content. Novel device 110 may include a media player 112 among its standard feature set and, in accordance with a preferred embodiment of the present invention, may also comprise a personalization content manager 137 and a media file storage unit 138 capable of receiving and storing media file 136. Telephone 120 may be a novel communication device like device 110 or it may be any suitable telephone, such as a landline phone, a mobile phone, a digital phone, a VoIP phone, or an analog phone.
 On the occasion of a telephone connection between Jack and Jill over voice connection 140, personalization content manager 137 may cause media file 136 selected by Jill to be played on media player 112 of device 110 belonging to Jack. It will be appreciated that, since media file 136 may "belong" to Jill and may be downloaded to device 100 without any intervention from Jack, Jack may have the illusion that media file 136 was provided from Jill across connection 140 at the time of the telephone conversation, without any latency.
 It will further be appreciated that media file 136 was not provided concurrently by the operators of voice connection 140, even though Jack may have the illusion otherwise. It will still further be appreciated that media file 136 may be played even on pre-3G devices, as long as such devices can download and play media files.
 Reference is now made to FIG. 2, which illustrates the method performed by device 110 to play media file 136 when simultaneously involved in a voice connection operation with telephone 120.
 Personalization content manager 137 may remain (step 200) in a wait state until notification of an activating event 210 is received. Activating event 210 may be, for example, a call initiation 212, a call ringing 214, or an end of call 216. Call initiation 212 may occur when device 110 is used to initiate a call to telephone 120, at the point of dialing or connecting. Call ringing 214 may occur when device 110 detects an incoming call from telephone 120. End of call 216 may occur when a phone conversation between device 110 and telephone 120 ends and is determined by notification of a hang up or idle state.
 After activating event 210 may be received, personalization content manager 137 may retrieve (step 220) the telephone number of telephone 120 and may use it to look up (step 230) the media file 136 associated with Jill, whose telephone number was retrieved.
 Personalization content manager 137 may then launch (step 240) the associated media file 136 for play by media player 112. Media player 112 may stop at the completion of media file 136 or may continue to play media file 136 in a continuous loop until personalization content manager 137 may receive notification of an ending event 250. Ending event 250 may be, for example, a call connection 252, a call answering 254, or a call hang up 256.
 Call connection 252 may occur when telephone 120 answers a call initiated by device 110. Such a state may apply when activating event 210 was, for example, call initiation 212. Call answering 254 may occur when device 110 answers an incoming call initiated by telephone 120. Such a state may apply when activating event 210 was, for example, call ringing 214.
 Call hang up 256 may occur when the phone conversation between device 110 and telephone 120 ends, such as when either device 110 or telephone 120 hangs up. Such a state may apply when activating event 210 was, for example, either call initiation 212 or call ringing 214 and the connection may not have completed between device 110 and telephone 120.
 After personalization content manager 137 receives notification of an ending event 250, personalization content manager 137 may stop (step 260) media player 112, after which personalization content manager 137 may return to wait state 200.
 In accordance with a preferred embodiment of the present invention, Jill may have selected a different media file 134 (FIG. 1) for each activating event. Accordingly, personalization media file database 138 of device 110 may include, for example, a personalization media file 136A (FIG. 2) to be played for call initiation event 212; a second personalization media file 136B to be played for call answering event 214 and a third personalization media file 136C to be played for end of call event 216.
 It will be appreciated that more than one activating event 212 may occur during the course of a single connection between device 110 and telephone 120. For example, call initiation 212 may occur when device 110 calls device 120. Personalization content manager 137 may play associated media file 136B until, for example, call connection 252 occurs. Jack and Jill may then conduct a typical telephone conversation. When the telephone conversation ends, personalization content manager 137 may play the media file 136C associated with end of call 216.
 Similarly, for example, call ringing 214 may occur when device 110 receives an incoming call from telephone 120. Personalization content manager 137 may play associated media file 136A until, for example, call answering 254 occurs. Jack and Jill may then conduct a typical phone conversation. When the telephone conversation ends, personalization content manager 137 may play the media file 136C associated with end of call 216.
 It will be appreciated that additional examples of activating event 210 may occur at any time during the set up, execution, or end of a telephone call between device 110 and telephone 120.
 In an alternative preferred embodiment of the present invention, such additional examples of activating event 210 may also be associated with unsuccessful attempts to complete a connection and conduct a typical phone conversation. For example, activating event 210 may be a busy signal, network congestion ("fast busy" signal), or call waiting. In accordance with this embodiment, Jill may select one or more media files 134 (FIG. 1) for these activating events 210 as well.
 Reference is now made to FIG. 3A which represents an exemplary user media table 390, which may be stored on community server 130. For every user 360 in table 390, there may be one or more records indicating activating events 370 and the associated media files 380 to play for each activating event 370.
 In accordance with the embodiment of FIGS. 1 and 2, Jill may have selected the media file VID1.3GP for playing on the device of her buddies, whenever a buddy initiates a call (i.e. call initiation) to Jill. Jill may also have selected the media file VID2.3GP for playing on the device of her buddies, whenever she calls a buddy (i.e. call ringing). She may also have selected the media file VID3.3GP for playing on the devices of her buddies whenever a phone call between her and one of her buddies ends, regardless of who initiated the connection.
 Other information which may be stored in the user media table 390 may include account information for the user, the content source, such as a universal resource locator (URL) for each media file 134 and/or a record of when the file was copied from the server to media file storage unit 138. It will be appreciated that the data in FIG. 3A is exemplary in nature and does not represent an exhaustive listing of the possible events for which Jill may select media files to play. For example, in accordance with an alternative preferred embodiment of the present invention, user media table 390 may also include selections of media files 134 to be played when a caller receives a busy signal, a "fast busy" signal, or call waiting.
 In accordance with an alternative preferred embodiment of the present invention, user media table may also include selections of default media files 134 to be played when Jill is called by someone that does not meet any of the criteria for her other selections. For example, a caller may not be a member of community 150. It may also be possible that Jill's caller may be a member of community 150, but may not be Jill's buddy. Another possibility may be that Jill's caller may be indeed be her buddy, but that neither she nor such caller have previously selected a media file 134 to be played in such a situation. Jill may select one or more default media files 134 to be played in such situations.
 Different versions of user media table 390 may be located on device 110 and on community server 130. Device 110 may store a local version, which may be a small portion of table 390 having the records of only those buddies of the owner of device 110. Community server 130, on the other hand, may store the entire table, for all the members of community 150.
 Reference is now made to FIG. 3B which illustrates a user-buddy table 392 that may be used to define relevant records to be stored in each local version of user media table 390. For every user 362 in table 392, there may be one or more records listing his buddies 364. In FIG. 3B, user 1 is listed as having buddies user 2, user 3, user 4, and user 7; and user 2 is listed as having user 1 as his buddy.
 Reference is now made to FIG. 3C, which shows an alternative format for user-buddy table, here labeled 392'. Table 392' records users 362 and their buddies 364, as before. In addition, to enable users 362 to share different media files 380 with different buddies 364, buddy table 392' may record which media files 380 are to be shared with which buddy 364 for which type of activating event 370.
 In accordance with the preferred embodiment of the present invention, community server 130 may update the local version of user media table 390 from time to time, as discussed hereinabove, with data stored in the server version of user media table 390. The update process may refer to buddy table 392 to determine which records to download to the local version as well as which files to download.
 The update process may define a population of records in buddy table 392 where user 362 matches the name of the owner of device 110. The process may then download records from the server version of user media table 390 for the relevant user 362.
 It will be appreciated that tables 390 and 392 may be updated and stored in other ways and such other ways are included in the present invention. For example, and not inclusive, tables 390 and 392 may be stored locally. Additions and changes to them may be generated on community server 130 and may be downloaded to device 110 at the appropriate moment. They may be deleted thereafter from community server 130.
 Reference is now made to FIG. 4A, which details one exemplary device 412 with its personalization content manager, here labeled 416, implemented on a mobile telephone. Device 412 may comprise, as part of its feature set, an operating system 450, a media player 425 and a phone application 414, to which may be added personalization content manager 416 and a personalization storage unit 418.
 Operating system 450 may provide connectivity between the elements of device 412, typically via operating system application programming interfaces (APIs). In accordance with a preferred embodiment of the present invention, the operating system of device 412 may be Symbian OS, commercially available from Symbian Ltd. of the United Kingdom. Alternative embodiments may include, for example, BREW, commercially available from QUALCOMM Incorporated of the United States; derivatives of Microsoft Windows for mobile devices, such as Windows Mobile or MS SmartPhone, commercially available from Microsoft Corporation of the United States; or derivatives of Java such as Java Micro Edition (popularly known as JME or J2ME) and commercially available from multiple vendors.
 Phone application 414 may comprise, for example, all the functions necessary for device 412 to operate as a cellular telephone and may interface directly with operating system 450. Phone application 414 may pass phone number and caller id information to personalization content manager 416 through standard operating system APIs. Similarly, personalization content manager 416 typically may launch the media files via operating system 450, which may, in turn, start up media player 425.
 Personalization content manager 416 may be started as a resident application when device 412 may be booted up. Manager 416 may remain in a dormant wait state until the user initiates a call to another device or when an incoming call is detected.
 Personalization content manager 416 may comprise a main program 415, a line status determiner 417 and a phone number determiner 419. Line status determiner 417 may make API calls to operating system 450 to receive indications of when an activating event occurs. Line status determiner 417 may forward the status to main program 415. Main program 415 may activate phone number determiner 419 whenever line status determiner 417 may indicate that an activating event has happened and phone number determiner 419 may determine the phone number associated with the activating event. In one embodiment, phone number determiner 419 may monitor changes in a phone log (not shown) to find the currently active phone number. In another embodiment, phone number determiner 419 may register to receive the phone number whenever operating system 450 provides indications of a new event to line status determiner 417. Main program 415 may then use this phone number to look up the associated media file 136 in storage unit 418.
 For some phones, operating system 450 may accord the highest processing priority to phone application 450 to ensure that the telephony services take precedence over the execution of other operations, such as the playing of media files. Similarly, phone application 414 will typically be in a window group with the highest z-order priority, which determines precedence for the display of application data on the device screen. Such z-order priority may interfere with the display of media file 136. Therefore, in accordance with a preferred embodiment of the present invention, main program 415 may raise the priority of the window group associated with media player 425 in order to enable its display to take precedence over the displays of phone application 414. Alternatively, main program 415 may raise the process priority of the process associated with media player 425 or with personalization content manager 416.
 It will be appreciated that some cellular telephones may not gracefully handle such changes to priority of the window and/or of the process. The behavior may vary greatly in response to even minor changes in the handset model or embedded firmware. However, Applicants have realized that the properties of newer cellular telephone handsets may be utilized. Some handsets, such as the Sanyo MM-7500, allow the user to select video ringtones to be played in response to incoming calls. Certain of these handsets, such as the Sanyo MM-7500, even allow the user to specify specific video ringtones to be played in response to incoming calls from particular users.
 Applicants have realized that, for such handsets, all that needs to be manipulated is the contact list. In fact, many newer Java handsets support a contact list API through "JSR 75: PDA Optional Packages for the J2METM Platform". This specification provides a framework allowing Java programs access to the handset-maintained properties associated with contacts in the handset contact list.
 The JSR 75 API specifies a variety of "details" associated with each contact and provides a mechanism allowing handset manufacturers and other implementers to extend this list. Standard details include PHOTO and PHOTO_URL, allowing association of a photographic image either from storage or from a URL. Certain manufacturers allow the supplied photographic image to also be a slideshow animation or a video clip. Other manufacturers define custom JSR 75 "details" allowing the application to supply both an audio ringtone and a silent picture or animation. Similar APIs and capabilities may exist in other mobile operating systems, such as Symbian, Windows Mobile, BREW, and proprietary environments. Similar APIs and capabilities may also exist on a variety of other network-enabled communication devices, such as IP phones, VoIP soft phones, set-top boxes, etc.
 Reference is now made to FIG. 4B, which illustrates one exemplary such handset 461 with its personalization content manager, here labeled 466. Handset 461 may comprise an operating environment 460 which may comprise an operating system 462, a phone application 463, a media player 464 and a contact list application 465, With an associated storage unit 467. Handset 461 may additionally comprise personalization content manager, here labeled 466, and a personalization storage unit 468. In this embodiment and as discussed hereinabove, contact list application 465 may allow personalization content manager 466, through an API such as one supporting JSR 75, to select video ringtones to be played in response to incoming calls and/or in response to calls from particular users.
 In this embodiment, personalization content manager 466 may comprise an associator 470, a downloader 472 and a contact list manager 474. Similar to the operation of main program 415 (FIG. 4A), downloader 472 may download media clips 136 from community server 130 to storage unit 468, or to contact list storage unit 467 if an API exists to do so, along with an indication of which buddy to associate it with. Associator 470, through a programming API of operating environment 460 such as one supporting JSR 75, may pass the recently downloaded media clip 136 to operating environment 460 as the media content to be associated with the buddy, who is usually already a member of the contact list. If the buddy is not already in contact list 465, contact list editor 474 may first add (also through a programming API) the buddy to contact list 465, after which associator 470 may associate media clip 136 with the buddy's contact information.
 When a call comes from a buddy, phone application 463, typically in cooperation with contact list application 465, may react to the caller-id and may play the associated media content properly.
 Furthermore, in accordance with a further preferred embodiment of the present invention, operating environment 460 may also allow the registration, via a programming API, of a video ringtone that would play at other activation events, such as call initiation 212, end of call 216, or the various busy indications (regular busy, fast busy or call waiting), such as described hereinabove.
 In this embodiment, associator 470 may perform any of the following operations:
 a. specify the playing of a video clip on both incoming and outgoing calls;
 b. specify playing a silent video clip;
 c. specify playing an animation, such as an animated GIF slide show;
 d. specify showing a still photo, such as a GIF or JPG image;
 e. specify playing an audio track, together with silent video, animation, or still image; or
 f. specify playing such media content only for incoming or only during outgoing calls.
 Certain devices may support creating such associations remotely; for example using synchronization protocols that allow a server, such as community server 130, to set the details associated with each contact. Such synchronization may not require the installation of any additional software on the device.
 As detailed in the embodiments, the media file 136 played when a given member of community 150 receives an incoming call may not have been selected by that same member. Indeed, depending on the number of associated buddies, it may be likely that a large number of constantly changing media files 136 may be played for incoming calls, such that a given member of community 150 may not recognize the fact that an incoming call is on his/her device 110. Accordingly, in a preferred embodiment of the present invention, members of community 150 may also select a "self ID" media file to be played before media file 136 for all incoming calls. With this, members of community 150 may recognize the incoming call as being on their devices 110 even though they may not recognize the sounds which follow.
 Reference is now made to FIG. 5 that illustrates a preferred embodiment of the present invention in which the playing of media file 136 may be occasioned by an event other than a voice connection between devices operated by Jack and Jill.
 Playing device 510 may be owned by Jack and may be any programmable device capable of storing and playing media files. Such a device may be, for example, a desktop computer running VoIP software such as Skype, available from Skype Limited of Luxemburg, a handheld device having communication capabilities, or a soft phone. Jill's unit 520 may be any device or method by which Jill may contact, or be contacted by, playing device 510. As in the embodiment of FIG. 1, Jack and Jill, the owners of playing device 510 and unit 520, respectively, may be members of media content personalization sharing community 150 using community server 130 to select and download media files 136.
 Activating event 530 may be associated with any form of communication between playing device 510 and Jill's unit 520, including, for example, email, SMS, instant messages, or VoIP. Activating event 530 may also be associated with any detail of such communication, including, for example, the timing, length, or contents of the communication, as well as the identity or presence state of the initiating entity.
 It will be appreciated that, in addition to being a video file, an image or an audio file as discussed hereinabove, media file 136 may also be a request to invoke or launch a previously installed program or application. In the latter case, media file 136 is not necessarily played by a media player.
 In accordance with an alternative preferred embodiment of the present invention, media file 136 may be an audio file, played at the end of a call. For such an embodiment, audio file 136, which may be much smaller than a video sequence, may be downloaded from the other party to the conversation (which may or may not be a buddy) at any time, including prior to the conversation or during the conversation for devices that can perform simultaneous voice and data transfer. For devices that cannot simultaneously transfer voice and data, the download may occur just after the conversation ends. This download may occur from the community server 130 or along the voice channel. In the latter embodiment, the network operator may provide media file 136.
 Reference is now made to FIG. 6, which may describe a further alternative embodiment in which the communication channel may be an instant messaging (IM) channel between the users Jack and Jill. In this embodiment, the communication channel may include an IM server 630. Jill's device may be an IM client 620 and Jack's device 610 may include an IM client 625 in addition to media player 112, personalization content manager 137 and storage unit 138.
 As is known in the art, instant messaging, also known as "IM" or "chatting", typically comprises the sending of textual messages, emoticons and/or animated emoticons, between two users, such as between Jack and Jill. In accordance with this embodiment of the present invention, Jill may additionally send Jack a triggering event, such as an identifier 635, during their conversation. An exemplary identifier 635 may be a file name, a number or a URL of media file 136 to be played.
 Jack's IM client 625 may recognize identifier 635 and may transfer it to personalization content manager 137, along with some indication of the source of event 635 (e.g. Jill). As in the previous embodiments, manager 137 may retrieve media file 136 indicated by identifier 635 and may play it on media player 112. Prior to playing media file 136, manager 137 may additionally check to see that the source, e.g. Jill, was authorized to send identifier 635.
 As in the previous embodiments, media file 136 may have been previously downloaded to Jack's device 610 from community server 130. Alternatively, it may be downloaded the first time that Jill may send identifier 635 and may be stored for later use when Jill may again send identifier 635.
 It will be appreciated that IM server 630 may be implemented separately from or as part of community server 130. If servers 130 and 630 are implemented together, the combined server may perform part of the operation of IM client 625. Thus, the combined server may check to see that the source, e.g. Jill, was authorized to send identifier 635 and/or may download the associated file if it was not previously downloaded to device 610.
 It will be appreciated that, as shown in FIG. 7 to which reference is now briefly made, personalization content manager 137 may be implemented in many different types of devices, of which four have been discussed above and three are shown in FIG. 7. In addition to smart phones, cellular telephones, programmable devices and devices that allow instant messaging, manager 137 may be implemented on any type of device and for any type of platform which has communication ability and media playing abilities. Such other types of devices include but are not limited to, mobile handsets, Skype, IM sessions, the new outside screen on laptops, IP (Internet Protocol) phones with color screens, caller id pop ups on televisions, etc.
 For example, FIG. 7 shows four exemplary devices, a television 700 with a caller id pop up 702, a laptop computer 704 with a secondary display 706 on the back of the cover, a video telephone 710 with a screen 712, and a personal computer 720 with a IM session 722, with their elements, including a device processor to run the standard operation of the device.
 The delivery mechanisms through which communication may occur are varied and may include, but are not limited to, IP, SIP (session initiation protocol), SMS (short message system), IVR (interactive voice response), etc. It will be appreciated that the personalization content sharing may be managed through community server 130, irrespective of the delivery mechanism.
 Furthermore, while the personalization content manager may be different for each type of device and/or delivery mechanism and thus, is labeled 137A, 137B, 137C and 137D in FIG. 7, each manager may include at least main program 415 (not shown in FIG. 7), which may manage the downloading and storage of media content files 136 and may provide the media file associated with the current buddy to whatever media player, labeled 730A, 730B, 730C and 730D, the device may have. In some embodiments, main program 415 may provide media file 136 in response to receiving an identification of the current buddy from a call handler 732 or an identification handler 734 of the device. Typically, such identification is a caller ID type identification but other identifications, such as customer number, etc., may also be utilized. In other embodiments, where the device has the ability to play different media files per identification, main program 415 may provide the media file for association with a given buddy prior to its use.
 Alternatively, if call handler 732 or ID handler 734 is not capable of providing the identification, manager 137 may determine it from other information available on the device.
 While certain features of the invention have been illustrated and described herein, many modifications, substitutions, changes, and equivalents will now occur to those of ordinary skill in the art. It is, therefore, to be understood that the appended claims are intended to cover all such modifications and changes as fall within the true spirit of the invention.
Patent applications by Jonathan William Medved, Jerusalem IL
Patent applications in class Call alerting
Patent applications in all subclasses Call alerting