Source: http://www.google.com/patents/US20040010808?dq=7095053
Timestamp: 2014-07-11 11:29:48
Document Index: 332682467

Matched Legal Cases: ['art 400', 'art 400', 'art 500', 'art 500', 'art 500', 'art 500', 'art 500', 'art 500']

Patent US20040010808 - System and method for notifying an instant message recipient of receipt of a ... - Google PatentsSearch Images Maps Play YouTube News Gmail Drive More »Sign in<nobr>Advanced Patent Search</nobr>PatentsIn an interactive multimedia environment, the invention includes automated presence management on an instant messaging network, a message notification priority scheme based on a message recipient's preferences, and message notification based on the results of the scheme. Presence management, the ability...http://www.google.com/patents/US20040010808?utm_source=gb-gplus-sharePatent US20040010808 - System and method for notifying an instant message recipient of receipt of a messageAdvanced Patent SearchPublication numberUS20040010808 A1Publication typeApplicationApplication numberUS 10/194,342Publication dateJan 15, 2004Filing dateJul 12, 2002Priority dateJul 12, 2002Also published asUS8577983Publication number10194342, 194342, US 2004/0010808 A1, US 2004/010808 A1, US 20040010808 A1, US 20040010808A1, US 2004010808 A1, US 2004010808A1, US-A1-20040010808, US-A1-2004010808, US2004/0010808A1, US2004/010808A1, US20040010808 A1, US20040010808A1, US2004010808 A1, US2004010808A1InventorsLinden deCarmoOriginal AssigneeDecarmo LindenExport CitationBiBTeX, EndNote, RefManReferenced by (58), Classifications (16), Legal Events (2) External Links: USPTO, USPTO Assignment, EspacenetSystem and method for notifying an instant message recipient of receipt of a messageUS 20040010808 A1Abstract In an interactive multimedia environment, the invention includes automated presence management on an instant messaging network, a message notification priority scheme based on a message recipient's preferences, and message notification based on the results of the scheme. Presence management, the ability to detect others connected to the network and to inform others connected to the network of the user's presence, may be automated based on the activity the user is engaged in, such as viewing a video stream. The user registers preferred video streams during the viewing of which the user does not want to be interrupted. When such a video stream is being viewed, the user is taken offline so that the user is not �present� on the instant messaging network. When the video stream changes, it is again determined whether the user wants his or her presence to be known during the new video stream. The message notification priority scheme may include several notification levels (e.g., low, medium, high, and urgent), one of which is assigned to a message based on the video stream being viewed, the identity of the message sender, and/or the urgency of the message. The user is then notified of the message based on the determined notification level. A user may be notified of a message having a lower notification level by an unobtrusive light being illuminated on the set-top box, whereas a message having a higher notification level may be flashed across the TV screen. Images(6) Claims(43)
DETAILED DESCRIPTION [0022] The present invention in its exemplary form automatically manages a user's (or a message recipient's) presence on an instant messaging network based on the video stream being viewed by the user. The term �video stream� can include the channel, the video program, and the type of video program being viewed. If the user's presence is divulged, the invention then automatically determines the notification level of received instant messages based on the user's preferences of video stream, sender's identity, and message urgency. Finally, based on the determined notification level, the invention notifies the user that such a message has been received. [0023] In one embodiment of the present invention, a prioritization scheme may include the following notification levels: ignore, low, medium, high, and urgent, although the invention supports more or fewer levels of notification. Messages to be ignored may be junk instant messages (akin to �junk mail�) or spam or messages from unidentified or unfamiliar senders, and these messages may be rejected out of hand. [0024]FIG. 1 is a block diagram that illustrates an embodiment of the system of the present invention. Included in such a system 100 are instant message server 110, video server 120, television (TV) 130, set-top box (STB) 140, interface 150, remote control 160, and buddies 170, 180. Instant message server 110 and video server 120 are typically computers comprising a central processing unit (CPU), memory, and input/output (I/O) means. [0025] Instant message server 110 is connected to message receiving apparatuses, such as a user's STB 140, a buddy's STB 180, and a buddy's computer 170. Such connection can be direct (e.g., hardwired), but more typically is made via a network. Such a network may be the public switched telephone network (PSTN), and the message receiving apparatuses may be connected to the PSTN via modems or T1 lines. Other networks include local area networks (LANs), wide area networks (WANs), metropolitan area networks (MANs), Intranets, and general-purpose networks, such as the Internet, and other networks running Internet protocol (IP). [0026] Video server 120 is connected to user's STB 140 to deliver a wide range of video programming such as movies, video games, television shows, sports, and other programming as is typically offered or will be offered by cable television and satellite television providers. Video server 120 may also be connected to buddy's STB 180, but it is not a requirement of the invention. Video server 120 is not a requirement of the instant messaging portion of system 100, but video programming broadcast on TV 130 is. [0027] Buddies 170, 180 are examples of a wide range of people who may be connected to message server 110 using a personal computer (170), an STB (180), or some other communication device. There may be hundreds, thousands, or even millions of people with the capability to connect to message server 110, and many of those may be simultaneously connected to message server 110. A subset of those with such capability may be on any single user's buddy list. [0028] STB 140 can be a set-top box as known generally in the art, capable of receiving video programming from video server 120 and decoding (if needed) and transmitting such programming to TV 130. As part of the present invention, STB 140 is also capable of communicating with message server 110, and transmitting such communications to TV 130, so that the messages may be viewed on TV 130. STB 140 may also include lights (such as LEDs) indicating messages waiting for the user, analogous to e-mail notification indicators prevalent in the e-mail art. TV 130 may include any type of television monitor that can broadcast video programming. This includes conventional cathode-ray tubes (CRTs), LCD monitors, plasma monitors, HDTV monitors, and other monitors. Although pictured as separate from TV 130, STB 140 may be integrated into TV 130, so long as TV 130 includes the proper means for connecting to message server 110 and video server 120. [0029] Interface 150 is used to set up the user's preferences with respect to preferred channels and programs and also to create and maintain buddy lists and priorities associated with each buddy. Generally, such interface will be displayed on TV 130, but it is within the present invention for interface 150 to include a display separate from that of TV 130. Although pictured as a separate block in FIG. 1, interface 150 is preferably integrated with STB 140. If STB 140 is integrated with TV 130, interface 150 may still be integrated with STB 140, allowing STB 140, interface 150, and TV 130 to be a single physical unit. Remote control 160 can be any conventional remote control, but is programmed to interact with interface 150 and STB 140. It is also possible for a user to interact with interface 150, STB 140, and TV 130 without using remote control 160, but such interaction may be limited. In addition to or instead of remote control 160, there may be a keyboard with a mouse for inputting a user's preferences into interface 150 or STB 140. Other means for inputting preferences and for interacting with interface 150 are within the present invention. [0030] The invention includes aspects of automatically managing a user's presence and determining the notification level of an instant message destined for a user. FIG. 2A illustrates blocks of a system for automating presence management in accordance with an embodiment of the present invention, and FIG. 2B illustrates blocks of a system for determining the notification level of a received instant message and notifying a user of the instant message in accordance with an embodiment of the present invention. FIG. 2A indicates that channel 210 and program or program type 220 are inputs to block 230 that determines whether a user desires instant messaging to be enabled, based on the user's indicated preferences. If such instant messaging is desired, block 240 indicates to others connected to message server 110 of the user's presence. If such instant messaging is not desired, block 240 takes the user's presence offline, so that the user's buddies will not think that such user is online and available for instant messaging. [0031]FIG. 2B indicates that the identity of sender 250 and message urgency 260, as well as channel 210 and program or program type 220 as in FIG. 2A, are inputs to block 270 that determines the notification level of a message, based in part on the user's indicated preferences. Once the notification level is determined, block 280 notifies the user of that message based on the notification level. [0032]FIG. 3 illustrates some of the steps involved in automatically managing the user's presence. FIG. 3 shows TV/STB 310, message server 110, and buddy computers 330. The terms used in FIG. 3 are syntax from a session-based multimedia protocol, Session-Initiation Protocol (SIP), which generally runs on top of IP (Internet Protocol). SIP is one example of a protocol that can be used with an instant messaging system. Other communication protocols known in the art may be used instead. �Registration� tells the proxy that a user is online and occurs when the STB is turned on, when the user comes online after being offline, and when the user re-registers using �keep-alive� messages sent to the proxy at set intervals (e.g., every few minutes, but the actual interval is set by the network administrator). If the proxy does not receive several consecutive �keep-alive� messages, the registration expires, and the user is considered to be offline. �Subscription� tells the proxy under what conditions the user should be notified of instant messages and occurs when the STB is turned on, when the user comes online after being offline, and when the user changes his or her notification preferences. �Notification� lets the user know when a buddy has come online. [0033] When the user turns on the set-top box, the STB registers the user in step 335, and, in step 340, the STB subscribes the user. When buddies 330 come online, they are also registered in steps 345, 350, 355, and the proxy notifies the user in step 360 of the buddies' presence. If a video program 370 comes on (because, for example, the user changes the channel or a different program starts on the same channel) during which the user does not want to be interrupted with instant messages, STB 140 deregisters the user in step 365, effectively taking the user offline. Once that video program ends, the system checks to see if the next program is one during which the user does not want to be interrupted. If not, the STB re-registers the user in step 375, re-subscribes the user in step 380, and notifies in step 385 the user's buddies who are online at that time. [0034]FIG. 4 describes this process using flowchart 400. A user turns on STB 140 in step 405 to start the flowchart. In step 410, the system determines the user's identity. If only a single user has been set up to use the system, this step assumes that the user's identity is the already-identified user and proceeds to step 430. If the system is used by a family, for example, the user chooses his or her identity from a list. The system may also require passwords for security. If the user is a new user (step 420), the system prompts to set up that new user in step 425. Such set-up may include using interface 150 and remote control 160 to specify the user's preferences with respect to favorite and preferred channels and programs and also to create and maintain buddy lists and notification levels associated with each buddy, as well as how to handle senders who are not on the buddy list. Channel and program preferences include specifying for which channels and specific programs or program types (e.g., sports, soap operas, etc.) the-user does not want to appear available for instant messaging. In addition, the system may offer a default profile that may be customized by the user on a program-by-program or channel-by-channel basis. For example, there may be buttons on remote control 160 to add the current channel or program or program type to or delete it from the user's profile. There may also be a button to delete a buddy from the user's buddy list and a button to add a buddy to the user's buddy list, which, once pressed, would prompt for the priorities associated with that added buddy. [0035] Once the user is set up and identified, step 430 asks whether a new channel or program is being selected, or a different program is coming on. If the user is turning on the STB, the answer is yes. If so, in step 440, the system retrieves the user's channel and program preferences. Once those preferences are retrieved, step 450 asks whether the user prohibits instant messaging during the currently-tuned channel and/or program. If so; step 470 asks whether the user is currently online. If not, the process loops back to step 430 to wait for a new channel or program input (or a different program). If the user is currently online, step 475 deregisters the user as in step 365, effectively taking the user offline. The process then loops back to step 430 to wait for a new channel or program input. If in step 450 the user does not prohibit instant messaging during the currently-tuned channel and/or program, step 460 asks whether the user is currently online. If so, the process loops back to step 430 to wait for a new channel or program input. If the user is currently offline, step 463 registers the user as in step 335 or 375, and step 467 subscribes the user as in steps 340 or 380. The process then loops back to step 430 to wait for a new channel or program input. [0036] Flowchart 400 is based on the user and the user's preferences and interacts with message server 110 to automatically establish or hide a user's presence and availability for instant messaging. In contrast, the flowcharts in FIGS. 5-7 are based on determining whether the user should be notified of a message received by STB 140 and, if so, how the user should be notified. [0037]FIG. 5 is a flowchart of one embodiment of an overall method for determining the notification level of an instant message and notifying a user of the instant message based on the notification level. An instant message is received in step 510. This message may be received from message server 110 because the user has indicated the preference to be available for instant messaging according to the flowchart in FIG. 4. However, it may be possible for a message to reach STB 140 without being routed through message server 110, generally as a result of spammers or other unauthorized users being able to bypass the presence management safeguards. This may happen because STB 140 will generally have its own IP (Internet Protocol) address, which, although not publicly disclosed, may be accessed randomly or discerned by others with the appropriate detection equipment. [0038] In such a case, it is again necessary to determine if the user has indicated availability for receiving instant messages. Step 520 asks whether the user permits instant messaging when tuned to the current channel. If not, step 525 may return an error to the proxy so that the proxy can report that the user is offline, or may, in the case of a spammer or an unknown party, return no response so that the sender does not attempt to access the user's IP address again. [0039] If instant messaging is permitted in step 520, step 530 asks whether the user permits instant messaging when tuned to the current program or program type. If not, the flowchart proceeds to step 525 as before. If instant messaging is permitted in step 530, the system determines the message notification level in step 540, as discussed with respect to the flowchart in FIG. 6, and then notifies the user in step 550 of the message based on the determined notification level, as discussed with respect to the flowchart in FIG. 7. [0040]FIG. 6 is a flowchart of subroutine 540 for determining the notification level of an instant message. The levels used in this example are ignore, low, medium, high, and urgent. Other embodiments of the invention could use more or fewer levels. Step 610 retrieves the user's channel and program preferences, and step 620 retrieves the user's buddy list profiles. In step 630, the variable Notify is set to the highest notification level, in this example �urgent.� Step 640 asks whether the current program or program type is �preferred.� Already discussed are most favored programs or program types for which the user has indicated he or she is unavailable for instant messaging while the program is being shown. Here, a �preferred� program or program type is generally one during which the user is available for instant messaging, but the user has restricted the way in which he or she is notified of such a message. If the program or program type is �preferred,� step 645 sets Notify to the highest notification level permitted while the program is active. For example, if the user wants to further restrict notification, Notify will be set lower, e.g., to �low,� whereas if the user wants to allow more notification, Notify will be set higher, e.g., to �high.� It is also possible for the user to have gradations of preferred programs, such as categories of �more preferred,� �preferred,� and �less preferred� programs. In such cases, the notification level of messages received during a more preferred show would likely be set to �low� or �medium,� that of messages received during a preferred show would likely be set to �medium� or �high,� and that of messages received during a less preferred show would likely be set to �high.� If the program has not been designated as preferred, step 640 returns �no� and Notify remains the same (i.e., �urgent�). [0041] Next, step 650 asks whether there are any preferences associated with the current channel. Already discussed are channels for which the user has indicated he or she is unavailable for instant messaging. Here, a user may have indicated a preference for restricting the way in which he or she is notified of an instant message while watching such a channel. If such preferences or attributes exist, step 655 determines the highest notification level permitted while the channel is on, and sets Notify to the lesser of the current Notify and such notification level. For example, if Notify is set to �urgent,� but the highest notification level permitted while the channel is on is �low,� Notify will be set to �low.� If, however, Notify is set to �medium� and the highest notification level permitted while the channel is on is �high,� Notify will remain at �medium.� As with �favorite� programs or program types, different channels may have different maximum notification levels associated with them. If the current channel has no preferences associated with it, step 650 returns �no� and Notify remains the same. [0042] Next, step 660 asks whether the message itself is marked with an �urgency� or an �importance� notification preference. Such preferences are set by the sender and may include �urgent,� �high,� �medium� or �normal,� or �low,� although most messages would either be marked �urgent� or �high� or have no preference. If such a notification preference exists, step 665 sets the notification level to the lesser of the current Notify and such notification preference. If the received message has no preferences associated with it, step 660 returns �no� and Notify remains the same. [0043] Next, step 670 asks whether the user has set any notification preferences associated with the sender (e.g., buddy) of the message. Preferences may be set up for senders who are buddies, i.e., known to the user and liked by the user, and also for senders who are known to the user and disliked, e.g., spammers, junk messengers, etc. Those who are buddies may have notification preferences of �urgent,� �high,� �medium,� or �low.� Those who are disliked will most likely have notification preferences of �ignore.� If such a preference exists, step 675 sets the notification level to the lesser of the current Notify and such notification preference. If the sender has no associated preferences, the sender is likely unknown to the user, and step 680 sets Notify to �ignore� or �low� based on buddy list user preferences. Once the final notification level is determined in steps 675 or 680, the value of Notify is returned in step 690 to flowchart 500. [0044]FIG. 7 is a flowchart of subroutine 550 for notifying a user of an instant message based on the notification level determined in subroutine 540. As before, Notify can have the value ignore, low, medium, high, or urgent. Step 710 asks if Notify is �ignore.� If so, step 715 ignores the message and returns in step 760 to flowchart 500. If not, step 720 asks if Notify is �low.� In general, the message indication for a �low� notification level should be relatively unobtrusive to the user. Thus, if Notify is �low,� step 725, for example, illuminates the IM indicator on STB 140, and then returns in step 760 to flowchart 500. [0045] If Notify is not �low,� step 730 asks whether Notify is �medium.� In general, the indication for a message with a �medium� notification level should be more visible than for one having a �low� notification level. Thus, if Notify is �medium,� step 735, for example, may display brief text, such as the sender's e-mail address and the subject of the message, on the TV screen and then returns in step 760 to flowchart 500. If Notify is not �medium,� step 740 asks whether Notify is �high.� In general, the indication for a message with a �high� notification level should be more visible than for one having a �medium� notification level. Thus, if Notify is �high,� step 745, for example, may draw an opaque banner on the TV screen (thus obscuring some of the video program), and within the banner may display brief text as before. Step 745 may also display the message itself or part of the message in an opaque window, and may also display buttons so that the user can choose an interactive display to interact with the sender by responding with an instant message. Once a message having a �high� notification level is indicated, the process returns in step 760 to flowchart 500. [0046] Finally, if Notify is not �high� in step 740, Notify is deemed to be �urgent� in step 750. In general, the indication for a message with an �urgent� notification level should be more visible than for one having a �high� notification level. Thus, if Notify is �urgent,� step 755, for example, may switch immediately to an interactive instant messaging display, displaying the full text of the message, and allowing the user to respond immediately to the message. Once a message having an �urgent� notification level is indicated, the process returns in step 760 to flowchart 500. [0047] As indicated above, the embodiments described herein use five notification levels�other embodiments of the invention may include more or fewer notification levels. [0048] Although generally illustrated in the context of a set-top box-based system, the invention is not limited to that environment. More broadly, the invention can operate on any instant messaging network, so long as that network is coupled with an interactive activity that can notify the user of a received instant message. Again, the notification may affect any sense of the recipient, not just the recipient's vision. In addition, the higher the notification level, the more sensorially obtrusive the notification. [0049] Additional advantages and modifications will readily occur to those skilled in the art. Therefore, the present invention in its broader aspects is not limited to the specific embodiments, details, and representative devices shown and described herein. Accordingly, various changes, substitutions, and alterations may be made to such embodiments without departing from the spirit or scope of the general inventive concept as defined by the appended claims. Referenced byCiting PatentFiling datePublication dateApplicantTitleUS7124370May 20, 2004Oct 17, 2006America Online, Inc.Presence and geographic location notification based on a delegation modelUS7219303 *May 20, 2004May 15, 2007Aol LlcPresence and geographic location notification based on a settingUS7237201May 20, 2004Jun 26, 2007Aol LlcGeographic location notification based on identity linkingUS7269629 *Dec 30, 2002Sep 11, 2007Intel CorporationMethod and apparatus for distributing notification among cooperating devices and device channelsUS7363345Dec 17, 2002Apr 22, 2008Aol Llc, A Delaware Limited Liability CompanyElectronic notification delivery mechanism selection based on recipient presence information and notification contentUS7412657Aug 26, 2004Aug 12, 2008International Business Machines CorporationSystems, methods, and media for updating an instant messaging systemUS7496631 *Jun 13, 2003Feb 24, 2009Aol LlcDelivery of an electronic communication using a lifespanUS7564369Sep 16, 2004Jul 21, 2009Microsoft CorporationMethods and interactions for changing a remote control modeUS7587462 *Aug 2, 2007Sep 8, 2009Intel CorporationMethod and apparatus for distributing notification among cooperating devices and device channelsUS7590998Jul 27, 2006Sep 15, 2009Sharp Laboratories Of America, Inc.Television system having internet web browsing capabilityUS7640341 *Jun 19, 2003Dec 29, 2009Microsoft CorporationInstant messaging for multi-user computersUS7711815Oct 10, 2006May 4, 2010Microsoft CorporationUser activity detection on a deviceUS7716289 *Oct 14, 2003May 11, 2010At&T Intellectual Property I, L.P.Transferring instant messaging (IM) messagesUS7730144Dec 11, 2006Jun 1, 2010Ebuddy Holding B.V.High level network layer system and methodUS7886232Sep 12, 2006Feb 8, 2011Edmund J FishPresence and geographic location notification based on a delegation modelUS7903795 *Jun 15, 2004Mar 8, 2011Avaya Inc.System and method for indicating status of an incoming transmission to a userUS7949107 *Aug 24, 2005May 24, 2011International Business Machines CorporationMethod, system, and computer program product for providing privacy measures in instant messaging systemsUS8005912 *Feb 17, 2006Aug 23, 2011Cisco Technology, Inc.System and method for presence notification for video projection statusUS8024765Dec 18, 2006Sep 20, 2011Hewlett-Packard Development Company, L.P.Method and system for communicating media program informationUS8037212Dec 11, 2006Oct 11, 2011Ebuddy Holding B. V.Event notification system and methodUS8099670May 28, 2008Jan 17, 2012International Business Machines CorporationSystems and media for updating an instant messaging systemUS8118596Mar 9, 2010Feb 21, 2012Niznick Gerald AOne-piece, screw-receiving, externally-threaded endosseous dental implants and related transfer components, comfort caps and abutmentsUS8180840Oct 14, 2003May 15, 2012At&T Intellectual Property I, L.P.Automatically replying to instant messaging (IM) messagesUS8224904Sep 29, 2006Jul 17, 2012Microsoft CorporationMissed instant message notificationUS8230135Jun 21, 2011Jul 24, 2012Ebuddy Holding B.V.Event notification system and methodUS8230465 *Aug 5, 2003Jul 24, 2012Koninklijke Philips Electronics N.V.Data network, user terminal and method for providing recommendationsUS8301701Oct 15, 2003Oct 30, 2012International Business Machines CorporationCreating dynamic interactive alert messages based on extensible document definitionsUS8339241 *Oct 16, 2006Dec 25, 2012Samsung Electronics Co., Ltd.Method of displaying messages in digital home appliances and display control deviceUS8346871Jan 7, 2005Jan 1, 2013International Business Machines CorporationMaintaining message privacy on an exposed display deviceUS8352872May 11, 2007Jan 8, 2013Facebook, Inc.Geographic location notification based on identity linkingUS8356070Mar 10, 2010Jan 15, 2013Ebuddy Holding B.V.High level network layer system and methodUS8402179Jul 20, 2012Mar 19, 2013Ebuddy Holding B.V.Event notification system and methodUS8421931 *Dec 27, 2006Apr 16, 2013Motorola Mobility LlcRemote control with user profile capabilityUS8510395May 5, 2010Aug 13, 2013Ebuddy Holding B.V.Contact list display system and methodUS8620273Sep 16, 2008Dec 31, 2013Blackberry LimitedUser interface and method of viewing unified communications events on a mobile deviceUS8682983Dec 4, 2007Mar 25, 2014At&T Intellectual Property I, L.P.Systems, methods and computer program products for the delivery of email text messages and audio video attachments to an IPTV display deviceUS8700713Dec 11, 2006Apr 15, 2014Ebuddy Holding B.V.Picture provisioning system and methodUS8711199 *Jan 13, 2009Apr 29, 2014At&T Intellectual Property I, L.P.Method and apparatus for communicationsUS8719710Sep 13, 2012May 6, 2014Facebook, Inc.Geographic location notification based on identity linkingUS8739071 *Feb 27, 2004May 27, 2014Blackberry LimitedSystem and method for message display and managementUS20040019637 *Jul 26, 2002Jan 29, 2004International Business Machines CorporaionInteractive one to many communication in a cooperating community of usersUS20100083255 *Sep 26, 2008Apr 1, 2010Microsoft CorporationNotification batching based on user stateUS20100114901 *Nov 2, 2009May 6, 2010Rhee Young-HoComputer-readable recording medium, content providing apparatus collecting user-related information, content providing method, user-related information providing method and content searching methodUS20100169917 *Dec 31, 2008Jul 1, 2010Gunnar HarboeSystem and Method for Customizing Communication in a Social Television FrameworkUS20100180313 *Jan 13, 2009Jul 15, 2010At&T Intellectual Property I, L.P.Method and apparatus for communicationsUS20120246246 *Mar 12, 2012Sep 27, 2012Sony Europe LimitedUser notificationUS20130074116 *Oct 30, 2012Mar 21, 2013At&T Intellectual Property I, L.P.System and Method of Message Notification and Access via a Video Distribution NetworkUS20130097254 *Sep 14, 2012Apr 18, 2013Facebook, Inc.Electronic message delivery based on presence notificationEP1635523A1 *Sep 13, 2004Mar 15, 2006Topseed Technology Corp.Alert for interactive users of msn messengerEP1669893A2 *Dec 8, 2005Jun 14, 2006NTT DoCoMo, Inc.Information notification system and information notification methodEP1714205A2 *Jan 12, 2005Oct 25, 2006Sony CorporationAutomatic user device presence registration systemWO2004104789A2 *May 20, 2004Dec 2, 2004America Online IncPresence and geographic location notificationWO2005081738A2Jan 12, 2005Sep 9, 2005Sony CorpAutomatic user device presence registration systemWO2005091578A1 *Mar 17, 2005Sep 29, 2005Siemens AgMethod terminal and server for transmission of service messages in fixed and/or mobile networksWO2008072028A2 *Dec 12, 2006Jun 19, 2008Ebuddy Holding B VEvent notification system and methodWO2009073310A1 *Nov 10, 2008Jun 11, 2009At & T Intellectual Property ISystems, methods, and computer program products for the delivery of email text messages and image attachments to an iptv display deviceWO2009155599A2 *Jun 22, 2009Dec 23, 2009Peter AddertonSystem for projecting user input on multiple third party viewable screens simultaneouslyWO2010066998A2 *Dec 8, 2009Jun 17, 2010France TelecomMethod for activating client software in an instant messaging system* Cited by examinerClassifications U.S. Classification725/139, 348/E07.071, 725/110, 709/219International ClassificationH04L12/58, H04N7/173Cooperative ClassificationH04N7/17318, H04L51/04, H04L51/26, H04L51/24, H04N21/4788European ClassificationH04N21/4788, H04L51/04, H04N7/173B2, H04L12/58B, H04L12/58NLegal EventsDateCodeEventDescriptionNov 13, 2008ASAssignmentOwner name: PACE PLC, UNITED KINGDOMFree format text: CHANGE OF NAME;ASSIGNOR:PACE MICRO TECHNOLOGY, PLC;REEL/FRAME:021831/0359Effective date: 20080516Jul 12, 2002ASAssignmentOwner name: PACE MICRO TECHNOLOGY, PLC, ENGLANDFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:DECARMO, LINDEN;REEL/FRAME:013122/0581Effective date: 20020712RotateOriginal ImageGoogle Home - Sitemap - USPTO Bulk Downloads - Privacy Policy - Terms of Service - About Google Patents - Send FeedbackData provided by IFI CLAIMS Patent Services©2012 Google