Source: http://www.google.com/patents/US20020097856?dq=7069184
Timestamp: 2016-06-25 20:23:44
Document Index: 521838296

Matched Legal Cases: ['arty 4', 'arty 4', 'arty 4', 'arty 2', 'arty 2', 'arty 4', 'arty 4', 'arty 2', 'arty 2', 'arty 4', 'arty 2', 'arty 4', 'arty 2', 'arty 4', 'arty 2', 'arty 4', 'arty 2', 'arty 4', 'arty 4', 'arty 4', 'arty 2', 'arty 4', 'arty 2', 'arty 2', 'arty 4', 'arty 2', 'arty 4', 'arty 2', 'arty 4', 'arty 2', 'arty 4', 'arty 4', 'arty 4', 'arty 4', 'arty 2', 'arty 2', 'arty 2', 'arty 2', 'arty 2', 'arty 2', 'arty 2', 'arty 2', 'arty 4', 'arty 4', 'arty 4', 'arty 4', 'arty 2', 'arty 2', 'arty 2', 'arty 2', 'arty 4', 'arty 2', 'arty 2', 'arty 4', 'arty 2', 'arty 2', 'arty 2', 'arty 4', 'arty 4', 'arty 2', 'arty 4', 'arty 4', 'arty 4', 'arty 4', 'arty 4', 'arty 4', 'arty 4', 'arty 4', 'arty 2', 'arty 4', 'arty 2', 'arty 2', 'arty 4', 'arty 2', 'arty 4', 'arty 2', 'arty 4', 'arty 2', 'arty 2', 'arty 2', 'arty 4', 'arty 4', 'arty 4', 'arty 4', 'arty 4', 'arty 4', 'arty 4', 'arty 4', 'arty 2', 'arty 4', 'arty 2']

Patent US20020097856 - Method and apparatus for creating a presence monitoring contact list with ... - Google PatentsSearch Images Maps Play YouTube News Gmail Drive More »Sign inPatentsMethod and apparatus to generate a dynamic contact list of contact and presence information about contact events in a communication system when a calling entity unsuccessfully attempts to communicate with a called entity. When such a contact event occurs, a routing processor or call agent generates contact...http://www.google.com/patents/US20020097856?utm_source=gb-gplus-sharePatent US20020097856 - Method and apparatus for creating a presence monitoring contact list with dynamic membershipAdvanced Patent SearchPublication numberUS20020097856 A1Publication typeApplicationApplication numberUS 09/768,417Publication dateJul 25, 2002Filing dateJan 24, 2001Priority dateJan 24, 2001Also published asUS6968052Publication number09768417, 768417, US 2002/0097856 A1, US 2002/097856 A1, US 20020097856 A1, US 20020097856A1, US 2002097856 A1, US 2002097856A1, US-A1-20020097856, US-A1-2002097856, US2002/0097856A1, US2002/097856A1, US20020097856 A1, US20020097856A1, US2002097856 A1, US2002097856A1InventorsJohn WullertOriginal AssigneeWullert John R.Export CitationBiBTeX, EndNote, RefManPatent Citations (1), Referenced by (114), Classifications (18), Legal Events (10) External Links: USPTO, USPTO Assignment, EspacenetMethod and apparatus for creating a presence monitoring contact list with dynamic membership
BRIEF DESCRIPTION OF THE DRAWINGS [0020] The foregoing and other features of the present invention will be more readily apparent from the following detailed description and drawings of illustrative embodiments of the invention in which: [0021] [0021]FIG. 1 is a block diagram of one illustrative embodiment of our invention; [0022] [0022]FIG. 2 is a block diagram of a packet-based embodiment of our invention; and [0023] [0023]FIG. 3 is a block diagram of a circuit switched embodiment of our invention. DETAILED DESCRIPTION [0024] Referring now to FIG. 1, therein is shown a system in accordance with this invention and including a plurality of calling parties 2 that are networked to a plurality of called parties 4, of which one such called party is depicted. The system also includes a call routing processor 6 that generates contact information for contact events by monitoring calls placed by the calling parties 2 to a called party 4, and a presence processor 8 that generates presence information for the calling parties 2 by monitoring and determining the presence status of the calling parties 2. The system further includes a data terminal 15 which includes a dynamic contact list display 10 for each called party 4 and a data terminal 15 which includes a dynamic contact list display 10. [0025] It should be understood that if a single entity has been the target of a contact event as a called party 4 that unsuccessfully received a call from a called party 2, and the source of a contact event as a calling party 2 that unsuccessfully initiated a call with a called party 4, then that single entity is both a called party 4 and a calling party 2, respectively. In other words, a single entity is not limited to being either a calling party 2 or a called party 4, but may be both. It should also be understood that the call routing processor 6 and presence processor 8 may simultaneously generate contact and presence information for multiple contact events and calling parties 2, respectively. It should further be understood that the functions of the call routing processor 6 and presence processor 8 may be implemented within a single processor, or implemented by a plurality of processors, servers, or agents that perform the call routing and presence functions. [0026] When a calling party 2 attempts to communicate with a called party 4, the call routing processor 6 monitors the call to determine whether or not the calling party 2 successfully communicated with the called party 4. Where the communication attempt is unsuccessful, the call routing processor 6 determines that a contact event has occurred, because the calling party 2 did not successfully communicate with the called party 4. After determining that a contact event has occurred, the call routing processor 6 determines relevant contact information about the contact event, including the calling party 2, called party 4, time of the contact event, and purpose of the call. The call routing processor 6 then sends this contact information to the called party 4, and the contact information is displayed to the called party 4 via its dynamic contact list 10 at its data terminal 15. [0027] After determining that a contact event has occurred, the call routing processor 6 also communicates with the presence processor 8 and notifies it about the contact event between the calling party 2 and the called party 4. The presence processor 8 receives this information about the contact event and begins to monitor and determine the presence status of the calling party 2 so long as the presence processor 8 has the appropriate permission to do so. As the presence processor 8 determines the presence status of the calling party 2, it sends this presence information to the called party 4, and the presence information is displayed to the called party via its data terminal 15 dynamic contact list 10. Whenever the presence processor 8 determines a change has occurred in the presence status of the calling party 2, it sends the updated presence Information to the called party 4, thereby updating it with the most recent presence information for the calling party 2. [0028] Upon examination of its dynamic contact list, the called party 4 is able to determine from the contact information included in the dynamic contact list what contact events have occurred in its absence, including the calling party 2, time of the call, and purpose of the call. Upon examination of its dynamic contact list, the called party 4 is also able to determine from the presence information included in the dynamic contact list the presence status of calling parties 2, including if, when, and for how long calling parties 2 are available for return communication by the called party 4. [0029] In accordance with an aspect of the invention, the presence processor 8 collects presence data about the calling parties, processes this presence data to determine the presence information for calling parties, and distributes this presence information to called parties. This presence information is displayed to a called party 4 via its dynamic contact list 10 at its data terminal 15, thereby enabling the called party to determine if, when, and for how long calling parties are available for return communication by the called party. [0030] The presence processor 8 performs the presence data collection, processing, and distribution functions; a plurality of network connections 12 are used to communicate with calling parties 2 and called parties 4, and connection 13 communicates with the call routing processor 6. The presence processor 8 also includes a communication module 14, which accumulates raw presence data and contact event data from calling parties and call routing processor 6 and distributes presence information to the called party 4; a status processor 16, which processes contact event data and presence data to determine what calling parties need to be monitored and the presence information for those calling parties, respectively; and a data store or database 18, which stores contact event data and presence data for processing by the status processor 16, and presence information for distribution by the communication module 14. [0031] Whenever a contact event occurs, the call routing processor 6 communicates with the presence processor 8 via its network connection 13 to send information about the contact event, including the calling party that attempted to communicate with the called party, and the called party that was the intended target of the calling party communication. This information is stored in the database 18, which records the calling and called parties for contact events. Thus, the status processor 16 is able to determine what calling parties should be monitored, and what called parties should receive presence information about specific calling parties, from the contact event data stored in the presence database 18. [0032] For each calling party included in the presence database 18, the status processor 16 collects presence data about the calling party 2 via the network connections 12, which data is received through the communication module 14. This presence data may be simple real-time presence data such as “online and available,” “online and unavailable” and “offline,” or complex non-real-time presence data such as the calling party's agenda, schedule, time limit for monitoring, and privacy limits when monitoring the calling party which can be obtained from the calling party or various utilities associated with the calling party. The status processor 16 processes this presence data to determine relevant presence information for the calling party 2. Presence data or processed presence information may also be stored in the presence database 18 for later processing by the status processor 16 and distribution by the communication module 14, respectively. [0033] After determining the presence information for the calling party 2, the presence processor 8 is able to determine those called parties 4 that should receive this information using the contact event data stored in the presence database 18. The status processor 16 then communicates the presence information for the calling party 2 to the appropriate called parties 4 via the network connections 12, thereby notifying them of the presence status of the calling party 2. The presence information communicated can once again be simple, real-time information such as “online and available,” “online but unavailable,” and “offline,” or complex non-real-time presence information such as a range of availability and unavailability times and future presence information for the calling party 2. Whenever the presence processor 8 determines that the presence information for the calling party 2 has changed, it communicates the new presence information to the appropriate called parties 4, thereby updating the presence information for the calling party 2. [0034] By displaying the presence information communicated by the presence processor 8 for a plurality of calling entities via the dynamic contact lists 10 at the called parties' data terminals 15, called parties 4 can determine the availability of calling parties 2 and prioritize if, when, and how to return communicate with calling parties. In particular, the presence information included in the dynamic contact list for those calling parties 2 that initiated contact events enable the called party 4 to determine what calling parties 2 are still available, when calling parties 2 will become available or unavailable, and how the called party 4 can communicate with the calling parties 2. For example, the dynamic contact list may display an availability schedule for each of the calling parties 2, thereby allowing the called party 4 to compare the schedules and determine which calling parties 2 will be available in a limited time span and require return communication at a particular time, versus which calling parties 2 are available for a longer period of time and are therefore of a lower priority for return communication by the called party 4. [0035] In order to ensure an appropriate level of privacy for a calling party 2, the presence processor 8 may permit each calling party 2 to opt out of monitoring by the presence processor 8. The option to opt out may be set as the default choice for a calling party 2, or the calling party 2 may opt out of presence monitoring by the presence management processor 20 based on certain factors including a call-by-call, called-party-by-called-party, or time-period basis. Thus, although there is no front-end limitation that requires a called party 4 to know the identity of each calling party 2 ahead of time in order to monitor the calling party's presence status, there is still the ability for the calling party 2 to selectively opt out in those situations where it wishes to maintain its privacy, but also the ability to allow previously unknown called parties 4 to monitor the presence status of previously unknown calling parties 2. [0036] The service available in a system in accordance with the invention can also provide various enhancements. Thus, the system may be enhanced by allowing calling parties 2 to use the text messaging capabilities of standard input messaging systems to deliver a text message to the data terminal of the called party 4; this text message could also be displayed at the called party's contact list display 10. Another enhancement of this system involves a scheduling application, wherein each data terminal 17 at a calling party 2 includes a scheduling calendar 19. This calendar 19 provides the presence processor 8 with information about how long a calling party 2 is likely to remain in its current state. Thus, for each of the calling parties 2 using a scheduling calendar 19, information is provided based on both a current status and schedule. For example, the status of calling parties 2 who are away at a scheduled event can be enhanced to indicate when they might return, and the status of calling parties 2 who are available now can be enhanced with information as to when their next scheduled event will make them unavailable. [0037] Referring now to FIG. 2, therein is shown a packet-based system illustrative of another embodiment of the present invention. A packet-based system utilizes data packets that communicate the message from the calling party to the called party, as well as data packets that are not part of the message itself, but include contact and presence information about contact events and calling parties, respectively, which are sent to the appropriate called parties by the call agent and presence management processor, respectively. [0038] The packet-based system shown in FIG. 2 includes a plurality of calling parties 2 and called parties 4 that are connected to a packet-based communication network 22 via residential gateways 24. This packet-based system also includes the plurality of data terminals 15 and 17 having the dynamic contact list displays 10. The packet-based system further includes a call agent 26 that performs the call routing functions of a call routing processor 6, and a presence management processor 28 that performs the functions of a presence processor 8. All communications, including those between user terminals 15 and 17 and the presence management processor 28, those between telephones 2 and telephone 4, those between the call agent 26 and the presence management processor 28, and those between telephones 2 and 4 and the call agent 26 are carried over the packet-based network 22. [0039] Calling parties 2 attempt to communicate with called parties 4 via the packet-based communication network 22. The calling parties 2 access the packet-based communication network 22 via their corresponding residential gateways 24, and attempt to send their messages via data packets that are routed from the calling parties 2 through the packet-based communication network 22 to the called parties 4, which also access the packet-based communication network 22 via their residential gateway 24. [0040] When a calling party 2 fails to communicate with the called party 4, the presence management processor 28 determines that a contact event has occurred, determines the appropriate contact information for the contact event, and communicates the contact information to the called party 4. The presence management processor 28 monitors and determines the presence status of the calling party 2, and communicates this presence information to the called party 4. Both the contact information and the presence information sent to the called party 4 are in the form of data packets that are routed from the presence management processor 28 to the called party 4 via the packet-based communication network 22. [0041] The dynamic contact list 10 of the called party 4 displays this contact and presence information, thereby allowing the called party 4 to determine the calling parties 2 that attempted to communicate with the called party 4 while the called party 4 was unavailable, as well as allowing the called party 4 to determine the availability status of the calling party 2. Thus, the called party 4 can determine if, when, and how to return communicate with a calling party 2. [0042] Referring now to FIG. 3, therein is shown a third, illustrative embodiment which is a circuit based system, including a switched telephone network 48 that performs the routing function and is used by calling parties 2 to communicate with called parties 4, and a separate packet-based signaling network 40 used to communicate contact and presence information to called parties 4 from the call agent and presence management processor, respectively. [0043] In a circuit based system, communications between the telephones 2 and 4 are carried over lines 42 of the switched telephone network through one or more telephone switches 48. The presence management functions in a circuit based system are performed in a telephone service control point 44, and communication between a telephone switch 48 and service control point 44 is carried out over a signaling network 46 such as a SS7 network. The communications between a service control point 44 and the calling party and called party data terminals 15 and 17 are carried over a separate packet-based network 40. In an alternative embodiment, however, the service control point 44 can also communicate with calling and called party data terminals 15 and 17 using the switched telephone network, in which case the communication is by in-band signaling methods, such as used for delivery of caller identification information. [0044] The circuit switched system shown in FIG. 3 includes a plurality of calling parties 2 that attempt to communicate with called parties 4 via the telephone switch network 48. The circuit switched system also includes a signaling network 46 such as SS7 used to setup communications between calling parties 2 and called parties 4. The circuit switched system further includes a service control point 44 that monitors calling parties 2, determines their presence information, and communicates their presence information to called parties 4, and a packet-based network 40 used by the service control point 44 to send data to the data terminals 15 and 17. [0045] When a calling party 2 attempts to communicate with a called party 4, the calling party 2 attempts to establish a communication channel via telephone switch 48 If the attempt to establish a communication channel fails, a contact event occurs, and the service control point 44 communicates the appropriate contact information to the called party 4. The service control point 44 also monitors the calling party 2 to determine its presence information and sends that presence information to the called party 4. [0046] The service control point 44 determines the presence information for the calling party 2 by retrieving presence data from the telephone switch 48 and from the data terminal 17 of the calling party 2, processes the presence data to determine the presence information for the calling party 2, and communicates the presence information to the called party 4. The contact and presence information sent to the called party 4 data terminal 15 is in the form of data packets that are routed from the service control point 44 over the packet-based network 40 to the called party 4. [0047] The dynamic contact list 10 at the called party 4 displays this contact and presence information, thereby allowing the called party 4 to determine the calling parties 2 that attempted to communicate with the called party 4 while the called party 4 was unavailable, as well as allowing the called party 4 to determine the availability status of the calling party 2. Thus, the called party 4 can determine if, when, and how to return communicate with a calling party 2. [0048] A number of features of the present invention will be apparent to one skilled in the art. One such feature is the ability to generate presence information from a source other than presence data retrieved directly from the calling party that initiated a contact event. For instance, a central server system may include the schedules and agendas for a plurality of calling parties, and the presence management processor may use this central presence data source to determine presence information for a plurality of calling parties without directly contacting the calling parties themselves. In the alternative, for a multi-stage communication process wherein an intermediate stage such as an Internet Service Provider may block the availability of a calling party, the presence management processor can determine and report that a calling party is unavailable due to a call block at an intermediate stage, rather than because the calling party itself is unavailable. [0049] Another feature of the present invention is the ability to provide the calling party with the ability to provide additional contact and presence information when a contact event occurs, thereby allowing the calling party to directly inform the called party about relevant contact and presence information. For instance, the calling party may notify the called party of other communication channels and entities where the called party can be contacted for return communication, as well as the time period for which the calling party will be available at these locations. The calling party can also notify the presence monitoring system itself of alternative entities to monitor as a substitute for the calling party so that the called party can return communicate the calling party using another channel or entity. For instance, a calling party that initiates a contact event using their office phone may notify the presence management processor to monitor the calling party's cellular phone instead of its office phone, thereby allowing the calling party to specify the entity that the presence management processor should monitor, generate presence information, and report to the called party. [0050] While the invention has been particularly shown and described with reference to preferred embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the invention. Patent CitationsCited PatentFiling datePublication dateApplicantTitleUS6311231 *Jan 29, 1999Oct 30, 2001Thomas Howard BatemanMethod and system for coordinating data and voice communications via customer contract channel changing system using voice over IP* Cited by examinerReferenced byCiting PatentFiling datePublication dateApplicantTitleUS7139806Oct 10, 2002Nov 21, 2006Motorola, Inc.Communication system for providing dynamic management of contacts and method thereforUS7277697May 24, 2004Oct 2, 2007Adesh DesaiMethod and system for establishing a teleconference over a telephony networkUS7284002 *Dec 17, 2003Oct 16, 2007International Business Machines CorporationCalendar-enhanced awareness for instant messaging systems and electronic status boardsUS7349700Aug 30, 2002Mar 25, 2008Aol LlcCommunication system and methodUS7444135 *Jul 8, 2005Oct 28, 2008Research In Motion LimitedUpdating availability of an instant messaging contactUS7474741Jan 20, 2003Jan 6, 2009Avaya Inc.Messaging advise in presence-aware networksUS7483525May 24, 2004Jan 27, 2009Navin ChaddhaMethod and system for selecting a communication channel with a recipient device over a communication networkUS7502608Mar 24, 2008Mar 10, 2009Aol Llc, A Delaware Limited Liability CompanyCommunication system and methodUS7669213Feb 23, 2010Aol LlcDynamic identification of other viewers of a television program to an online viewerUS7730143Dec 29, 2006Jun 1, 2010Aol Inc.Prohibiting mobile forwardingUS7787609Oct 6, 2005Aug 31, 2010Avaya Inc.Prioritized service delivery based on presence and availability of interruptible enterprise resources with skillsUS7899862Mar 1, 2011Aol Inc.Dynamic identification of other users to an online userUS7908327Mar 15, 2011Aol Inc.People listsUS7933588Apr 26, 2011Aol Inc.Communication system and methodUS7962504May 24, 2006Jun 14, 2011Aol Inc.Sourcing terms into a search engineUS7966003Jun 21, 2011Tegic Communications, Inc.Disambiguating ambiguous charactersUS7983148Jul 12, 2004Jul 19, 2011Avaya Inc.Disaster recovery via alternative terminals and partitioned networksUS8001199Aug 16, 2011Aol Inc.Reconfiguring an electronic message to effect an enhanced notificationUS8005919Aug 29, 2003Aug 23, 2011Aol Inc.Host-based intelligent results related to a character streamUS8009678 *Aug 30, 2011Microsoft CorporationSystem and method for generating a dynamic prioritized contact listUS8014497Oct 13, 2006Sep 6, 2011Avaya Inc.Messaging advise in presence-aware networksUS8060566Nov 30, 2005Nov 15, 2011Aol Inc.Automatically enabling the forwarding of instant messagesUS8107941Jan 31, 2012Research In Motion LimitedUpdating availability of an instant messaging contactUS8122137Sep 8, 2004Feb 21, 2012Aol Inc.Dynamic location of a subordinate userUS8156193Aug 26, 2009Apr 10, 2012Aol Inc.Enhanced buddy list using mobile device identifiersUS8161116May 24, 2004Apr 17, 2012Kirusa, Inc.Method and system for communicating a data file over a networkUS8176086 *May 8, 2012Avaya Inc.Methods and apparatus for determining a presence of a userUS8223941 *Jul 17, 2012At&T Intellectual Property I, LpSystem and method for call handlingUS8224916Jul 17, 2012Aol Inc.People listsUS8255950Feb 12, 2010Aug 28, 2012Aol Inc.Dynamic identification of other viewers of a television program to an online viewerUS8452849May 28, 2013Facebook, Inc.Host-based intelligent results related to a character streamUS8503989Oct 22, 2007Aug 6, 2013Cisco Technology, Inc.Dynamic contact listUS8548145Jun 19, 2012Oct 1, 2013At&T Intellectual Property I, L.P.System and method for call handlingUS8577972Jan 19, 2010Nov 5, 2013Facebook, Inc.Methods and systems for capturing and managing instant messagesUS8583087Sep 14, 2012Nov 12, 2013Nuance Communications, Inc.Disambiguating ambiguous charactersUS8612522 *Nov 26, 2003Dec 17, 2013Apple Inc.System and method for allowing an orginating user to use contact information in a prioritized list to contact a destination userUS8701014Nov 18, 2003Apr 15, 2014Facebook, Inc.Account linkingUS8706826Oct 14, 2011Apr 22, 2014Bright Sun TechnologiesAutomatically enabling the forwarding of instant messagesUS8775560Jan 31, 2013Jul 8, 2014Facebook, Inc.Host-based intelligent results related to a character streamUS8819176Sep 13, 2012Aug 26, 2014Facebook, Inc.Intelligent map results related to a character streamUS8856663 *Nov 5, 2004Oct 7, 2014Blackberry LimitedUser interface for integrating applications on a mobile communication deviceUS8874606May 2, 2011Oct 28, 2014Facebook, Inc.Sourcing terms into a search engineUS8874672Feb 13, 2012Oct 28, 2014Facebook, Inc.Identifying and using identities deemed to be known to a userUS8886721Apr 14, 2009Nov 11, 2014Avaya Inc.Short impromptu communications in presence-based systemsUS8954530Sep 13, 2012Feb 10, 2015Facebook, Inc.Intelligent results related to a character streamUS8954531Sep 13, 2012Feb 10, 2015Facebook, Inc.Intelligent messaging label results related to a character streamUS8954534Jan 4, 2013Feb 10, 2015Facebook, Inc.Host-based intelligent results related to a character streamUS8965964Dec 29, 2004Feb 24, 2015Facebook, Inc.Managing forwarded electronic messagesUS8996560Sep 14, 2012Mar 31, 2015Facebook, Inc.Search engine utilizing user navigated documentsUS9002949Dec 21, 2004Apr 7, 2015Google Inc.Automatically enabling the forwarding of instant messagesUS9037647Dec 29, 2008May 19, 2015T-Mobile Usa, Inc.System and method for the distribution and use of presenceUS9047364Jan 16, 2013Jun 2, 2015Facebook, Inc.Intelligent client capability-based results related to a character streamUS9049569May 11, 2010Jun 2, 2015Google Inc.Prohibiting mobile forwardingUS9053173Jan 28, 2013Jun 9, 2015Facebook, Inc.Intelligent results related to a portion of a search queryUS9053174Jan 30, 2013Jun 9, 2015Facebook, Inc.Intelligent vendor results related to a character streamUS9053175Jan 30, 2013Jun 9, 2015Facebook, Inc.Intelligent results using a spelling correction agentUS9070118Sep 14, 2012Jun 30, 2015Facebook, Inc.Methods for capturing electronic messages based on capture rules relating to user actions regarding received electronic messagesUS9075867Jan 31, 2013Jul 7, 2015Facebook, Inc.Intelligent results using an assistantUS9075868Feb 13, 2013Jul 7, 2015Facebook, Inc.Intelligent results based on database queriesUS9088879Feb 19, 2013Jul 21, 2015Google Inc.Automatically enabling the forwarding of instant messagesUS9171064Jan 31, 2013Oct 27, 2015Facebook, Inc.Intelligent community based results related to a character streamUS9203647Sep 15, 2012Dec 1, 2015Facebook, Inc.Dynamic online and geographic location of a userUS9203794Sep 14, 2012Dec 1, 2015Facebook, Inc.Systems and methods for reconfiguring electronic messagesUS9203879Sep 14, 2012Dec 1, 2015Facebook, Inc.Offline alerts mechanismUS9246975Sep 14, 2012Jan 26, 2016Facebook, Inc.State change alerts mechanismUS9253136Sep 14, 2012Feb 2, 2016Facebook, Inc.Electronic message delivery based on presence informationUS9288076 *Aug 23, 2004Mar 15, 2016Unify Gmbh & Co. KgUpdating of presence data allocated to the user of a communication serviceUS9288240Nov 12, 2013Mar 15, 2016Apple Inc.System and method for allowing an originating user device to use contact information in a prioritized list to contact a destination user deviceUS9313046Sep 15, 2012Apr 12, 2016Facebook, Inc.Presenting dynamic location of a userUS9319287Aug 5, 2013Apr 19, 2016Cisco Technology, Inc.Dynamic contact listUS9319356Sep 15, 2012Apr 19, 2016Facebook, Inc.Message delivery control settingsUS9356890Apr 9, 2012May 31, 2016Facebook, Inc.Enhanced buddy list using mobile device identifiersUS20030154293 *Feb 14, 2003Aug 14, 2003Zmolek Andrew CharlesPresence tracking and name space interconnection techniquesUS20040073643 *Oct 10, 2002Apr 15, 2004Hayes David J.Communication system for providing dynamic management of contacts and method thereforUS20040133638 *Dec 17, 2003Jul 8, 2004Doss J. SmithCalendar-enhanced awareness for instant messaging systems and electronic status boardsUS20040141594 *Jan 20, 2003Jul 22, 2004Brunson Gordon R.Messaging advise in presence-aware networksUS20040148347 *Nov 18, 2003Jul 29, 2004Barry AppelmanDynamic identification of other users to an online userUS20040186887 *Mar 19, 2003Sep 23, 2004International Business Machines CorporationReflective buddy listUS20040199581 *Nov 18, 2003Oct 7, 2004Valerie KucharewskiPeople listsUS20040199582 *Nov 18, 2003Oct 7, 2004Valerie KucharewskiPeople listsUS20040230659 *Mar 12, 2004Nov 18, 2004Chase Michael JohnSystems and methods of media messagingUS20050014490 *May 24, 2004Jan 20, 2005Adesh DesaiMethod and system for establishing a teleconference over a telephony networkUS20050018820 *May 24, 2004Jan 27, 2005Navin ChaddhaMethod and system for selecting a communication channel with a recipient device over a communication networkUS20050020250 *May 24, 2004Jan 27, 2005Navin ChaddhaMethod and system for communicating a data file over a networkUS20050204007 *Mar 12, 2004Sep 15, 2005International Business Machines CorporationApparatus method and system for automatically populating an interactive messaging contact listUS20050261011 *Nov 5, 2004Nov 24, 2005Research In Motion LimitedUser interface for integrating applications on a mobile communication deviceUS20060117050 *Nov 30, 2004Jun 1, 2006Ajita JohnMethods and apparatus for determining a presence of a userUS20060167991 *Dec 16, 2004Jul 27, 2006Heikes Brian DBuddy list filteringUS20060168204 *Dec 30, 2005Jul 27, 2006Barry AppelmanMobile blocking indicators on a contact listUS20060209690 *Mar 17, 2005Sep 21, 2006Microsoft CorporationSystem and method for generating a dynamic prioritized contact listUS20070002824 *Aug 23, 2004Jan 4, 2007Karl KlugUpdating of presence data allocated to the user of a communication serviceUS20070010232 *Jul 8, 2005Jan 11, 2007Research In Motion LimitedUpdating availability of an instant messaging contactUS20070042791 *Aug 16, 2005Feb 22, 2007Sbc Knowledge Ventures, L.P.Presence and availability management over a public communication networkUS20070288648 *Aug 29, 2003Dec 13, 2007Lara MehannaHost-based intelligent results related to a character streamUS20080133580 *Nov 30, 2007Jun 5, 2008James Andrew WanlessMethod and system for providing automated real-time contact informationUS20080147793 *Oct 31, 2006Jun 19, 2008Singh Munindar PMethod And System For Coordinating A Synchronous ActivityUS20090036101 *Sep 22, 2008Feb 5, 2009Research In Motion LimitedUpdating Availability of an Instant Messaging ContactUS20090104895 *Oct 22, 2007Apr 23, 2009Cisco Technology, Inc. (Ca Corporation)Dynamic contact listUS20090190734 *Jul 30, 2009At&T Knowledge Ventures, L.PSystem and method for call handlingUS20090213001 *Sep 8, 2004Aug 27, 2009Aol LlcDynamic Location of a Subordinate UserUS20090234927 *Dec 29, 2008Sep 17, 2009Adrian BuzescuSystem and method for the distribution and use of presence informationUS20100082693 *Sep 25, 2008Apr 1, 2010Ethan HuggOrganization of a contact list based on social network contextUS20100223350 *May 12, 2010Sep 2, 2010International Business Machines CorporationMethod for Providing an alert indicationUS20100260326 *Oct 14, 2010Avaya Inc.Short Impromptu Communications In Presence-Based SystemsUS20110167116 *Jul 7, 2011Aol Inc.People listsUS20110208768 *Aug 25, 2011Aol Inc.Sourcing terms into a search engineEP1835665A1 *Sep 19, 2006Sep 19, 2007Huawei Technologies Co., Ltd.Method for providing presence information and apparatus thereofEP2512111A1 *Apr 15, 2011Oct 17, 2012Alcatel LucentMethod and device for notifying parties to a communication in a communication networkWO2007048306A1Sep 19, 2006May 3, 2007Huawei Technologies Co., Ltd.Method for providing presence information and apparatus thereofWO2008103384A2 *Feb 20, 2008Aug 28, 2008Grape Technology Group Inc.System and method for enhanced directory assistance including commercial featuresWO2008103384A3 *Feb 20, 2008Jul 30, 2009Grape Technology Group IncSystem and method for enhanced directory assistance including commercial featuresWO2009114842A2 *Mar 14, 2009Sep 17, 2009T-Mobile Usa, Inc.System and method for the distribution and use of presence informationWO2009114842A3 *Mar 14, 2009Dec 30, 2009T-Mobile Usa, Inc.System and method for the distribution and use of presence informationWO2014059856A1 *Sep 23, 2013Apr 24, 2014Tencent Technology (Shenzhen) Company LimitedVideo call method, device, control method, control device, video call system, and storage medium* Cited by examinerClassifications U.S. Classification379/201.01International ClassificationH04M3/42, H04L29/08, H04M3/48, H04L12/58Cooperative ClassificationH04L69/329, H04L67/24, H04M3/48, H04M3/42365, H04L51/04, H04M3/42195, H04L12/581, H04M3/42093European ClassificationH04L51/04, H04L29/08A7, H04L29/08N23, H04L12/58B, H04M3/42GLegal EventsDateCodeEventDescriptionFeb 26, 2001ASAssignmentOwner name: TELCORDIA TECHNOLOGIES, INC., A CORP. OF DE, NEW JFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:WULLERT, JOHN R. II;REEL/FRAME:011573/0751Effective date: 20010118Apr 5, 2005ASAssignmentOwner name: JPMORGAN CHASE BANK, N.A., AS ADMINISTRATIVE AGENTFree format text: SECURITY AGREEMENT;ASSIGNOR:TELCORDIA TECHNOLOGIES, INC.;REEL/FRAME:015886/0001Effective date: 20050315May 2, 2006CCCertificate of correctionJul 6, 2007ASAssignmentOwner name: TELCORDIA TECHNOLOGIES, INC., NEW JERSEYFree format text: TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENT RIGHTS;ASSIGNOR:JPMORGAN CHASE BANK, N.A., AS ADMINISTRATIVE AGENT;REEL/FRAME:019520/0174Effective date: 20070629Owner name: TELCORDIA TECHNOLOGIES, INC.,NEW JERSEYFree format text: TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENT RIGHTS;ASSIGNOR:JPMORGAN CHASE BANK, N.A., AS ADMINISTRATIVE AGENT;REEL/FRAME:019520/0174Effective date: 20070629Mar 17, 2009ASAssignmentOwner name: TELCORDIA TECHNOLOGIES, INC., NEW JERSEYFree format text: RELEASE OF SECURITY INTEREST;ASSIGNOR:WILMINGTON TRUST COMPANY;REEL/FRAME:022408/0410Effective date: 20090220Owner name: TELCORDIA TECHNOLOGIES, INC.,NEW JERSEYFree format text: RELEASE OF SECURITY INTEREST;ASSIGNOR:WILMINGTON TRUST COMPANY;REEL/FRAME:022408/0410Effective date: 20090220Mar 26, 2009FPAYFee paymentYear of fee payment: 4Jun 26, 2009ASAssignmentOwner name: TELCORDIA LICENSING COMPANY LLC, NEW JERSEYFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:TELCORDIA TECHNOLOGIES, INC.;REEL/FRAME:022878/0821Effective date: 20090616Nov 12, 2010ASAssignmentOwner name: TTI INVENTIONS A LLC, DELAWAREFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:TELCORDIA LICENSING COMPANY LLC;REEL/FRAME:025356/0294Effective date: 20100128Mar 18, 2013FPAYFee paymentYear of fee payment: 8Dec 31, 2015ASAssignmentOwner name: NYTELL SOFTWARE LLC, DELAWAREFree format text: MERGER;ASSIGNOR:TTI INVENTIONS A LLC;REEL/FRAME:037407/0912Effective date: 20150826RotateOriginal ImageGoogle Home - Sitemap - USPTO Bulk Downloads - Privacy Policy - Terms of Service - About Google Patents - Send FeedbackData provided by IFI CLAIMS Patent Services