Patent Grant
8762458
Instant Messaging (IM) systems allow users to communicate with each other in real-time fashion. Traditionally, an IM conversation between two IM users takes the form of text messages exchanged between the IM users. To provide a more interesting user experience, many IM systems supplement a conversation by presenting non-textual information to the IM users. For example, a first user can select a type of global sound that is presented when any other user logs into the IM system. In this case, when a second user logs into the IM system, the first user is notified of the log-in event by the presentation of the selected global sound. In this case, the first user is dictating the sound that will be later presented to himself or herself.
Functionality is described for allowing a first user to select a sound item. The first user can use a first device to send this sound item to a second device operated by a second user. Upon the occurrence of a triggering event, the sound item selected by the first user can be presented by the second device to the second user. In this manner, the first user is dictating the sound item that is played back to the second user. The first device and the second device may correspond to two devices in an Instant Messaging (IM) system.
In one illustrative case, the first device can notify the second device of a new sound item by sending presence information to the second device. The presence information includes a reference to the new sound item. Upon discovering that the presence information identifies a new sound item, the second device can request the new sound item from the first device or from some other source. In one illustrative case, the first device can send the new sound item to the second device via a peer-to-peer communication channel. The new sound item can be sent via a queuing mechanism to help smooth the use of communication bandwidth.
According to another illustrative aspect, functionality is described that allows a user to select the new sound item from a source sound item. The functionality operates by presenting a graphical depiction of the source sound item together with a graphical selection unit. The graphical selection unit is placed over a segment of the source sound item. The functionality allows a user to adjust the position and size (e.g., width) of the graphical selection unit and to play back the segment demarcated by the graphical selection unit. By repeating these operations, the functionality can allow the user to select the new sound item through a trial-and-error approach.
Additional exemplary implementations features are described in the following.
The same numbers are used throughout the disclosure and figures to reference like components and features. Series 100 numbers refer to features originally found in
This disclosure sets forth functionality for using a first device to provide a sound item to a second device. The second device presents the sound item upon the occurrence of a triggering event. This disclosure also provides functionality for selecting the sound item using a user interface presentation. The functionality can be manifested in various systems, apparatuses, modules, procedures, storage mediums, data structures, and other forms.
The term “sound item” can encompass any type of content that can be presented in audible form. Types of sound items include music content, spoken word content, various non-verbal noises (e.g., a barking dog, rushing water, etc.).
As a preliminary note, any of the functions described with reference to the figures can be implemented using software, firmware, hardware (e.g., fixed logic circuitry), manual processing, or a combination of these implementations. The term “logic, “module,” “component,” “system” or “functionality” as used herein generally represents software, firmware, hardware, or a combination of the elements. For instance, in the case of a software implementation, the term “logic,” “module,” “component,” “system,” or “functionality” represents program code that performs specified tasks when executed on a processing device or devices (e.g., CPU or CPUs). The program code can be stored in one or more computer readable memory devices.
More generally, the illustrated separation of logic, modules, components, systems, and functionality into distinct units may reflect an actual physical grouping and allocation of software, firmware, and/or hardware, or can correspond to a conceptual allocation of different tasks performed by a single software program, firmware program, and/or hardware unit. The illustrated logic, modules, components, systems, and functionality can be located at a single site (e.g., as implemented by a processing device), or can be distributed over plural locations.
The terms “machine-readable media” or the like refers to any kind of medium for retaining information in any form, including various kinds of storage devices (magnetic, optical, static, etc.). The term machine-readable media also encompasses transitory forms for representing information, including various hardwired links for transmitting the information from one point to another.
Certain features are described flow chart form. In this mode explanation, certain operations are described as constituting distinct blocks performed in a certain order. Such implementations are exemplary and non-limiting. Certain blocks described herein can be grouped together and performed in a single operation, and certain blocks can be performed in an order that differs from the order employed in the examples set forth in this disclosure. The blocks shown in the flowcharts can be implemented by software, firmware, hardware, manual processing, any combination of these implementations, and so on.
This disclosure includes two sections. Section A describes one illustrative system for propagating and playing back sound items. Section B describes the operation of the system of Section A in flowchart form.
A. Illustrative System
The system 100 includes communication-related infrastructure 102 for allowing users to communicate with each other via a network 104. The users operate respective user devices.
The communication infrastructure 102 can include various server-type computers, data stores, and/or other data processing equipment. For example, the communication infrastructure 102 can include connection-related functionality (not shown) for managing connection among user devices. The communication infrastructure 102 can also include presence-related functionality (not shown) for managing and disseminating presence information within the system 100. Presence information includes data which generally describes a user's involvement in the system 100 as a communication participant. Without limitation, presence information can convey the network-related status of the user, such as whether the user is currently online, away, busy, and so forth. The presence information can also convey personal information associated with the user. The personal information may reveal a personalized textual message associated with the user, a personalized display name, and so forth. As will be discussed, the presence information can also reference a sound item associated with the user. In one illustrative case, the presence information can be expressed using the eXtensible Markup Language (XML) format.
In operation, the presence-related functionality of the communication infrastructure 102 can propagate presence information among groups of users. For example, consider the case in which a first user operates a first user device 106 and a second user operates a second user device 108. The second user is one of the contacts of the first user. In this illustrative scenario, the presence-related functionality can forward presence information 114 associated with a first device 106 to the second device 108. In one case, this presence information 114 can alert second device 108 that the first user has just logged into the system 100, and so on.
The network 104 can represent a local area network (LAN), a wide area network (WAN) (e.g., the Internet), or some combination of LAN(s) and WAN(s). The network 104 can be implemented by any combination of wireless links, hardwired links, routers, gateways, name servers, and so forth, and can be governed by any protocol or combination of protocols. In one case, system 100 allows user devices (106, 108, 110, 112) to communicate with each other using the resources of both the network 104 and the communication infrastructure 102. In another case, the system 100 allows user device (106, 108, 110, 112) to communicate with each other using only the resources of the network 104, that is, without relying on the communication infrastructure 102 or by only minimally relying on the communication infrastructure 102; in other words, in the system 100 is configured to also allow the user devices to directly communicate with each other in peer-to-peer (P2P) fashion. One mechanism for facilitating P2P communication in an IM system is described in co-pending U.S. Ser. No. 10/611,575, filed on Jul. 1, 2003, entitled “Transport System for Instant Messaging,” naming the inventors of John Holmes, et al.
Each user device can correspond to any type of data processing device. For example, a user device may correspond to a personal computer, a laptop computer, a personal digital assistant (PDA), a mobile telephone device, a game console, a set-top box associated with a television set, and so on. In several of the examples to follow, the first device 106 is used to transmit a sound item to the second device 108. The sound item is then played back by the second device 108. As noted above, the first device 106 is operated by a user referred to as a first user. The second device 108 is operated by a user referred to as a second user. It will be appreciated that this example is merely illustrative. For instance, in another scenario, the first device 106 can act as a receiver of a sound item provided by the second device 108. Further, reference to a single pair of communication participants is merely illustrative. For instance, in another case, the first device 106 can forward a sound item to plural recipient devices corresponding to plural respective contacts.
Each device can include a content management module for managing content items in a store. For example, the first device 106 includes a content managing module 116 for managing content items stored in a store 118. The second device 108 includes a content management module 120 for managing content items stored in a store 122. As will be described more fully below, a content management module can perform various roles. According to one role, a content management module can coordinate sending a content item to another user device and receiving a content item from another user device. A content management module can also coordinate the presentation of a content item.
With the above introduction, it is now possible to discuss the application of the system 100 to the propagation of sound items among user devices. As described above, a sound item corresponds to any content item that can be audibly presented to a user. Representative types of sound items include music items, spoken-word items, non-verbal noise items, and so forth. A user may select a sound item to represent himself or herself to another user (or users), e.g., as a type of calling card or the like. For example, a user may select her sound item to correspond to a few seconds of her favorite song. Another user may select her sound item to correspond to an inspirational spoken-word quotation. Another user may select his sound item to correspond to a non-verbal sound that he considers humorous, and so on.
In a typical scenario, the first user may use his or her device 106 to provide the sound item to the second device 108. Upon the occurrence of a triggering event associated with the first user, the second device 108 can play the sound item to the second user. For example, a triggering event may occur when the first user logs into the system 100. In this manner, the first user can dictate (with certain limitations and exceptions) the sound item that is played by the second device 108 to the second user.
To function as described above, as a first task, the first user selects a sound item. To facilitate this operation, the first user may invoke a content creation module (to be discussed in detail later). The content creation module displays a user interface presentation that provides a graphical depiction of a source sound item (such as a song file). Using this user interface presentation, the first user may select a segment of the source sound item. The selected segment corresponds to the sound item that is subsequently used to represent the first user to other users. The content management module 116 of the first device can store the selected sound item in its local store 118.
More specifically, the store 118 of the first device 106 can include various items 124 associated with the first user. One type of item corresponds to the sound item selected by the first user to represent himself or herself to others. Another item may correspond to a personal text message defined by the first user. Another item may correspond to an image selected by the first user, and so on. The store 118 can also include various other items 126 associated with other users. For example, the first user may have configured the first device 106 to communicate with various contacts (e.g., “buddies”). The other items 126 may provide sound items and other content items defined by the user's contacts. For example, assume that the first user has selected the second user as a contact with whom to communicate. In this case, the store 118 can include a sound item selected by the second user, an image selected by the second user, and so on.
Assume that the first user has just selected a new sound item in the manner described above (or modified a pre-existing sound item to in effect create a new sound item). The content management module 116 is invoked at this point to notify the first user's contacts about the existence of the new sound item. The content management module 116 performs this task by preparing presence information 114 which identifies the new sound item, along with other characteristics of the user's presence as discussed above. More specifically, the presence information 114 can include reference information which provides a link to the new sound item, but the presence information 114 does not include the actual content of the sound item itself. One or more presence servers (not shown) in the communication infrastructure 102 can receive this presence information 114 and disseminate it to all of the first user's contacts that happen to be online at the moment.
Assume that the second device 108 is online when the presence information 114 is sent. The second device 108 will receive the presence information 114 and process it to determine whether it includes any new information. For example, the content management module 120 of the second device 108 can determine whether the reference information contained in the presence information 114 (which identifies a sound item) differs from previously received reference information. Or perhaps the second device 108 has never received a sound item from the first user, in which case the second device 108 will consider the reference information contained in the newly received presence information 114 as identifying a new sound item.
The second device 108 responds to a determination that a new sound item has been received by requesting the new sound item from the first device 106. The first device 106 responds to this request by supplying the new sound item to the second device 108. The second device 108 then stores the new sound item in its own store 122. In one illustrative case, the request and response exchange between the first device 106 and the second device 108 can be conducted using peer-to-peer (P2P) communication. For example,
Once the second device 108 receives and stores a sound item from the first user it can play back this sound item to the second user in response to one or more types of triggering events, as discussed below:
Still other types of triggering events may cause the playback of the sound item. The above list is representative and non-exhaustive.
The above protocol for receiving and playing back sound items can be performed by any device in the system 100. For example, the second device 108 can forward a sound item selected by the second user to the first user. Then, when the second user engages in any of the behavior described above, the first device 106 can play back the second user's sound item. Finally, it should be noted that any user will typically include multiple contacts. For example, the first user will typically have multiple contacts. In this case, the first user device 106 can send the first user's sound item to all of the devices associated with that user's contacts.
The above-described item dissemination and playback procedure corresponds to one mode of operation of the system 100. The following explanation identifies various additional and/or alternative features of the system 100
According to one feature, assume that the first user selects a new sound item while offline and then later goes online. Further assume that at the time the first user goes on online, the second user is also online. In this case, the first user device 106 will seek to announce the online presence of the first user, but the second device 108 may not have obtained the new sound item from the first user device 106. To address this situation, the second device 108 can play another sound item, such as an old sound item associated with the first user, or any type of sound item previously selected by the second user (or a default sound item). This provision is useful so as not to delay the log-in procedure. The second device 108 will eventually receive an opportunity to obtain the new sound item from the first device 106. Upon the next triggering event, the second device 108 can then play the new sound item.
According to a second feature, assume that a user operates plural user devices under a single account. For example, as illustrated in
According to a third feature, assume that the first user has a large number of contacts. When the first user creates a new sound item, presence information will be propagated to all of her contacts, notifying the contacts of the new sound item. Each of the devices operated by the contact (“contact devices”) can then be expected to request the new sound item. This, in turn, will require the first user device to provide the new sound item to all of the contact devices that request it. Such a large number of requests and responses can potentially make large bandwidth demands on the system 100. To help ameliorate this situation, the system 100 can be configured to stagger the dissemination of sound items in various ways. According to a one technique, each of the contact devices that needs the new sound item can place an action item in a queue, and then request the new sound item when the action item comes due in the queue. Communication bandwidth can be smoothed out insofar as the contact devices are not requesting the new sound item at the same time.
According to a fourth feature, according to the scenario described above: (1) the first device 106 creates a new sound item; (2) the first device 106 notifies the second device 108 of the new sound item; (3) the second device 108 asks the first device 106 for the new sound item; and (4) the first device 106 supplies the new sound item to the second device 108. In a variation of this technique: (1) the first device 106 creates a new sound item; (2) the first device 106 supplies the new sound item to the network store 130; (3) the first device 106 notifies the second device 108 of the new sound item; and (4) the second device 108 requests and obtains the new sound item from the network store 130 (rather than from the first device 106).
Advancing to
The functionality includes a content creation module 202. The content creation module 202 allows the user to create a new sound item or modify an existing sound item. The content creation module 202 can perform this task by providing a user interface presentation to the user. The user may define the sound item using the user interface presentation in the manner described more fully below in the context of the discussion of
The functionality shown in
More specifically, the content management module 204 includes a content synchronization module 208. The purpose of the content synchronization module 208 is twofold. First, the content synchronization module 208 provides presence information to the user's contacts and also receives presence information from these contacts. The presence information identifies features of a user's presence within the system 100. For instance, the presence information identifies a sound item created by a user. The content synchronization module 208 also operates by sending a content item to another device when requested by the other device. The content synchronization module 208 can also request that another device forward a content item to it. For instance, assume that the content synchronization module 208 first receives presence information from another device that identifies various content items, including a new sound item. The content synchronization module 208 can determine whether it already includes the new sound item. If not, the content synchronization module 208 can request the other device to provide the new sound item. As described above, the content synchronization module 208 can optionally apply a queue-based protocol to request a content item.
The content management module 204 also includes a content playback module 210. The content playback module 210 plays back a sound item associated with another user when a triggering event occurs that pertains to that other user. For example, the triggering event may occur when that other user logs onto the system 100. In response to this event, the content playback module 210 retrieves the sound item corresponding to the user who has logged in (e.g., the first user) and plays it (e.g., for the second user).
The content management module 204 also includes a playback setup module 212. The playback setup module 212 defines various conditions for playing back a sound item. For example, in one case, a controlling user (meaning a user who operates the user device associated with the content management module 204) can choose to override the sound item defined by one or more other users by entering an appropriate instruction via the playback setup module 212. This override instruction will prevent the sound item for another user from playing in response to a triggering event. In lieu of the sound item defined by another user, the controlling user can define other sounds to be played in response to a triggering event. In one case, the controlling user can define a custom sound to be presented when a particular other user engages in behavior which constitutes a triggering event. In another case, the controlling user can define a global sound to be presented when any of the controlling user's contact performs a triggering event. In these two override scenarios, the controlling user is the entity which is choosing sounds to be played back upon triggering events; the other users that trigger the presentation of sounds are not dictating what sounds should be played.
The content playback module 210 associated with Alice's user device will present a sound item to Alice when a triggering events occurs that is associated with any of her contacts. For example, assume that one of Alice's contacts is Bob. When Bob logs into the system, Alice's user device will be notified of Bob's online status. In response, Alice's content playback module 210 can also play a sound item that Bob himself has selected for playback on Alice's device. The graphical depiction of a speaker and music 306 indicate that Alice receives an audible presentation of a musical clip chosen by Bob to announce his online presence.
The user interface presentation 402 includes an input section 404 that allows a user to select a file folder that contains source sound items. A source sound item corresponds to a previously created audio file from which the user may select a new sound item. For example, a source sound item can correspond to a commercially-produced song. Or the source sound item may correspond to a personal recording made by the user, e.g., providing spoken word content, music, non-verbal sounds, and so forth. In any case, the user may select a small snippet from the source sound item to produce a new sound item. In one case, the user can select any portion of the source sound item, but the selected portion cannot exceed a specified maximum length of time, e.g., without limitation, five seconds. In another case, no restrictions are placed on the length of a sound item. It is assumed that the user owns the property rights to the source sound item that is to be used to select the new sound item.
Upon the user selecting a file folder (in field 404), the user interface presentation 402 can list the contents of the folder in field 408. In this representative case, a file “Music” includes two source sound items, a song named SongXYZ and a song named SongABC. As indicated by the shading in
Upon the user selecting the song SongXYZ, the user interface presentation 402 displays a graphical depiction of the SongXYZ in a graphical presentation field 410. The graphical presentation field 410 includes a depiction of part of the sound wave of SongXYZ. For example, assuming that the entire sound is three minutes long, the graphical presentation field 410 can show a sound wave associated with a ten second portion of the song. The user interface presentation 402 includes a sound navigation field 412. The user can advance to different parts of the song by activating a fast forward control 414 or a rewind control 416. These commands (414, 416) will prompt the graphical presentation field 410 to display a different part of the song. The user can also display different parts of the song using other modes of interaction, such as by clicking on the graphical depiction of the song and dragging the depiction in one direction or the other (e.g., to the right or the left).
The graphical presentation field 410 includes a graphical selection unit 418 that is presented over the graphical depiction of the song. The graphical selection unit 418 can be formed as a window. The window has a first end identified by an arrow 420 and a second end identified by an arrow 422. The first end and the second end demarcate a segment of the song having a predetermined time span. The graphical selection unit 418 includes a transparent middle section that allows a user to see the portion of the song demarcated by the first end and the second end.
The graphical selection unit 418 can be moved to a different location in the song, e.g., by clicking on and dragging the graphical selection unit 418 or by entering some of the movement instruction. The user can also adjust the width of the graphical selection unit 418. The user can perform this task by adjusting either (or both) of the arrows (420, 422) that demarcate the edges of the graphical selection unit 418. Through these operations, the user can define the portion of the song that is selected as the new sound item. In other words, the portion of the song that is demarcated by the edges of the graphical selection unit 418 corresponds to the new sound item.
To ensure that the correct portion of the song has been selected, the user interface presentation 402 allows the user to play back the sound item demarcated by the graphical selection unit 418. The user can perform this task by actuating a start/stop control 424. That is, the control 424 can be used to transition from a no-play state to a play state by actuating the control 424; the same control 424 can be used to transition from a play state to a no-play state by actuating the control 424. When an instruction is made to play the sound item, the graphical selection unit 418 can show the progress of the playback using a line 426; namely, the line 426 moves from left to right with the advance of the content that is being played back.
In a typical selection process, the user is expected to use a trial-and-error approach to select a desired portion of the song. For example, the user can select an initial position and width of the graphical selection unit 418 and then actuate the play control 424. If the user is not pleased with the portion of the song that has been selected, the user can modify the position and/or width of the graphical selection unit 418, after which the user can play the selected content again. The user can repeat this procedure any number of times until he is satisfied with the selected portion.
The user can optionally make create a more audibly pleasing sound item by adding a fade-in effect (at the beginning of the sound item) and/or a fade-out effect (at the end of the sound item). The user may add these types of transition effects by selecting a fade-in control 428 and a fade-out control 430.
Once the user is satisfied with the selected sound item, the user can activate a save control 432 to save the new sound item. The user can select the name of the sound item via field 434. Alternatively, the user can activate a cancel control to abandon the sound item selection procedure.
In one case, the user can define a sound item to be displayed for all of his or her contacts upon the occurrence of any triggering event. In another case, the user can define different sound items for different users or groups of users. Alternatively or in addition, the user can define different sound items for different triggering events.
Advancing to
The processing functionality 502 can include a processing module 504 for implementing various processing functions. The processing module 504 can include volatile and non-volatile memory, such as RAM 506 and ROM 508, as well as one or more processors 510. The processing functionality 502 can perform various operations identified above when the processor(s) 510 executes instructions that are maintained by memory (e.g., 506, 508, or elsewhere). The processing functionality 502 also optionally includes various media devices 512, such as a hard disk module, an optical disk module, and so forth.
The processing functionality 502 also includes an input/output module 514 for receiving various inputs from the user (via input module 516), and for providing various outputs to the user (via presentation module 518). The presentation module 518 can provide a graphical user interface (GUI) 520. The processing functionality 502 can also include one or more network interfaces 522 for exchanging data with other devices and systems via one or more communication conduits 524. One or more communication buses 526 communicatively couple the above-described components together.
B. Illustrative Procedures
In block 602, the content creation module 202 receives the user's selection of a source sound item. This may correspond to the user selecting a desired folder and then selecting a source sound item that is included in the folder.
In block 604, the content creation module 202 presents a graphical depiction of part of the source sound item. For instance, the content creation module 202 can present a sound wave depiction of a portion of the sound item.
In block 606, the content creation module 202 presents the graphical selection unit 418 over a portion of the source sound item. The graphical selection unit 418 has a size (e.g., width) which defines the temporal length of the sound segment that it demarcates.
In block 608, the content creation module 202 allows the user to iteratively select a desired segment of the source sound item by repeatedly moving the position and/or size of the graphical selection unit 418, in conjunction with repeatedly playing back the segment demarcated by the graphical selection unit 418.
In block 610, the content creation module 202 optionally allows the user to choose transition effects that appear at the beginning and/or end of the selected sound item. The transition effects can correspond to a fade in effect at the beginning of the segment and a fade out effect at the end of the segment.
In block 612, the content creation module 202 can save the finally selected sound item in response to a save instruction from the user.
In block 614, the content synchronization module 208 can propagate presence information to the user's contacts, which alerts the contacts to the existence of the new sound item. The contacts can then request and receive the new sound item.
The right-hand portion of
In block 702, the second device 108 determines whether it has received new presence information from the first device 106. In this example, the user of the first device 106 correspond to contact X.
If block 702 is answered in the affirmative, in block 704, the second device 108 determines whether the presence information identifies a new sound item. The second device 108 can make this determination by comparing newly received reference information with previously received reference information, or by determining that there is no previously received reference information.
If block 704 is answered in the affirmative (meaning that the presence information identifies a new sound item), in block 706, the second device 108 requests the first device 106 to supply the new sound item. In response, the second device 108 receives this new sound item. As stated above, the second device 108 can alternatively obtain the new sound item from a server-side source, such as the network store 130.
In block 802, the second device 108 determines whether it has received a triggering event associated with the first user.
If block 802 is answered in the affirmative, in block 804, the second device 108 determines whether it has a sound item created by the first user.
If block 804 is answered in the affirmative, in block 806, the second device 108 determines whether the second user (of the second device 108) has previously entered an instruction to override the sound item created by the first user.
If block 806 is answered in the negative (meaning that the user has not entered an instruction to override the sound item), then, in block 808, the second device 108 presents the first user's sound item to the second user.
If block 806 is answered in the affirmative (meaning that the second user has entered an instruction to override), then the second device 108 can optionally present another sound to the second user. In one case, the second device 108 can present a sound item specifically defined by the second user for the first user. In another case, the second device 108 can present a default sound that it presents for all users that invoke a triggering event.
Although the invention has been described in language specific to structural features and/or methodological acts, it is to be understood that the invention defined in the appended claims is not necessarily limited to the specific features or acts described. Rather, the specific features and acts are disclosed as exemplary forms of implementing the claimed invention.
| Number | Name | Date | Kind |
|---|---|---|---|
| 6185603 | Henderson et al. | Feb 2001 | B1 |
| 6760754 | Isaacs et al. | Jul 2004 | B1 |
| 20010024965 | Hayashi | Sep 2001 | A1 |
| 20020032020 | Brown et al. | Mar 2002 | A1 |
| 20020145518 | Smith et al. | Oct 2002 | A1 |
| 20030027604 | Hayashi | Feb 2003 | A1 |
| 20030218631 | Malik | Nov 2003 | A1 |
| 20030225848 | Heikes et al. | Dec 2003 | A1 |
| 20040015610 | Treadwell | Jan 2004 | A1 |
| 20040196963 | Appelman et al. | Oct 2004 | A1 |
| 20040205775 | Heikes et al. | Oct 2004 | A1 |
| 20040215728 | Isaacs et al. | Oct 2004 | A1 |
| 20050030299 | Bursill | Feb 2005 | A1 |
| 20050060161 | Rudolph | Mar 2005 | A1 |
| 20060075056 | Isaacs et al. | Apr 2006 | A1 |
| 20060248150 | Chaar et al. | Nov 2006 | A1 |
| 20060288077 | Chen | Dec 2006 | A1 |
| 20070061403 | Seaburg | Mar 2007 | A1 |
| 20070073848 | Fratti | Mar 2007 | A1 |
| 20070123234 | Kim | May 2007 | A1 |
| 20070244979 | Isaacs et al. | Oct 2007 | A1 |
| 20070260968 | Howard et al. | Nov 2007 | A1 |
| 20080107045 | Berstis et al. | May 2008 | A1 |
| 20080167995 | Cue et al. | Jul 2008 | A1 |
| Number | Date | Country |
|---|---|---|
| 2000276185 | Oct 2000 | JP |
| 200227112 | Jan 2002 | JP |
| 200251006 | Feb 2002 | JP |
| 2003216187 | Jul 2003 | JP |
| 2004312316 | Nov 2004 | JP |
| 2005175723 | Jun 2005 | JP |
| 2008530842 | Aug 2008 | JP |
| 20020036290 | May 2002 | KR |
| 20040075412 | Aug 2004 | KR |
| 20050114805 | Dec 2005 | KR |
| 2287226 | Nov 2006 | RU |
| 200701005 | Jan 2007 | TW |
| WO2004079929 | Sep 2004 | WO |
| WO2006085069 | Aug 2006 | WO |
| Entry |
|---|
| PCT International Search Report and the Written Opinion for Application No. PCT/US2008/066227, mailed on Dec. 15, 2008, 14 pgs. |
| Translated Chinese Office Action mailed Aug. 31, 2011 for Chinese patent application No. 200880022229.8, a counterpart foreign application of U.S. Appl. No. 11/772,114, 18 pages. |
| The Australian Office Action mailed Apr. 2, 2012 for Australian patent application No. 2008270833, a counterpart foreign application of U.S. Appl. No. 11/772,114, 2 pages. |
| The Extended European Search Report mailed Mar. 9, 2012 for European patent application No. 08770427.6, 10 pages. |
| The Japanese Office Action mailed Mar. 9, 2012 for Japanese patent application No. 2010-514932, a counterpart foreign application of U.S. Appl. No. 11/772,114, 3 pages. |
| The Russian Office Action mailed Apr. 11, 2012 for Russian patent application No. 2009148788, a counterpart foreign application of U.S. Appl. No. 11/772,114, 3 pages. |
| The Chinese Office Action mailed Jul. 2, 2012 for Chinese Patent Application No. 200880022229.8, a counterpart foreign application of U.S. Appl. No. 11/772,114, 7 pages. |
| The Chinese Office Action mailed Nov. 29, 2012 for Chinese patent application No. 200880022229.8, a counterpart foreign application of U.S. Appl. No. 11/772,114, 3 pages. |
| The Russian Office Action mailed Aug. 16, 2012 for Russian patent application No. 2009148788, a counterpart foreign application of U.S. Appl. No. 11/772,114, 6 pages. |
| “eMail Alert 3.0”, retrieved on May 11, 2007, at <<http://www.tucows.com/preview/203799>>, Tucows Inc., 2006, pp. 2. |
| “Eudora Email 7.1”, available at least as early as May 10, 2007, at <<http://eudora.com/download/eudora/windows/7.1/Eudora—7.1—NF.pdf>>, QUALCOMM Incorporated, 2006, pp. 13. |
| Schmandt, et al., “Everywhere Messaging”, available at least as early as May 10, 2007, at <<http://alumni.media.mit.edu/˜nmarmas/IBM39-34.pdf>>, IBM, vol. 39, No. 3&4, 2000, pp. 660-677. |
| Chinese Office Action mailed Feb. 25, 2013 for Chinse patent application No. 200880022229.8, a counterpart foreign application of U.S. Appl. No. 11/772,114, 6 pages. |
| Israeli Office Action mailed May 5, 2013 for Israel patent application No. 201817, a counterpart foreign application of U.S. Appl. No. 11/772,114, 6 pages. |
| Number | Date | Country | |
|---|---|---|---|
| 20090006567 A1 | Jan 2009 | US |
