Source: http://www.google.com/patents/US7162474?dq=6,064,942
Timestamp: 2014-03-16 22:22:36
Document Index: 202278040

Matched Legal Cases: ['arty 6', 'arty 6', 'arty 6', 'arty 8', 'arty 6', 'arty 8', 'arty 6', 'arty 6', 'arty 6', 'arty 6', 'arty 6', 'arty 6', 'arty 8', 'arty 6', 'arty 6', 'arty 6', 'arty 8', 'arty 8', 'arty 6', 'arty 8', 'arty 8', 'arty 8', 'arty 8', 'arty 6', 'arty 8', 'arty 8', 'arty 8', 'arty 6', 'arty 8', 'arty 6', 'arty 8', 'arty 6']

Patent US7162474 - Recipient controlled contact directories - Google PatentsSearch Images Maps Play YouTube News Gmail Drive More »Sign inAdvanced Patent SearchPatentsA presence system 4 manages communications in a network 2 between initiating parties 8 and recipient parties 6. The system 4 has a database 10 storing entries each relating to recipient parties 6. Each entry is stored according to a unique identifier assigned to the corresponding recipient party 6 and...http://www.google.com/patents/US7162474?utm_source=gb-gplus-sharePatent US7162474 - Recipient controlled contact directoriesAdvanced Patent SearchPublication numberUS7162474 B1Publication typeGrantApplication numberUS 09/852,995Publication dateJan 9, 2007Filing dateMay 10, 2001Priority dateMay 10, 2001Fee statusPaidPublication number09852995, 852995, US 7162474 B1, US 7162474B1, US-B1-7162474, US7162474 B1, US7162474B1InventorsAndrew N Harker, Alan WilkinsonOriginal AssigneeNortel Networks LimitedExport CitationBiBTeX, EndNote, RefManPatent Citations (68), Non-Patent Citations (20), Referenced by (30), Classifications (23), Legal Events (3) External Links: USPTO, USPTO Assignment, EspacenetRecipient controlled contact directoriesUS 7162474 B1Abstract A presence system 4 manages communications in a network 2 between initiating parties 8 and recipient parties 6. The system 4 has a database 10 storing entries each relating to recipient parties 6. Each entry is stored according to a unique identifier assigned to the corresponding recipient party 6 and includes at least one rule specifying the manner of communications between the corresponding recipient party 6 and an initiating party 8. Images(3) Claims(25)
(a) a database storing a plurality of entries each relating to a recipient party, each entry being stored according to a unique identifier assigned to the corresponding recipient party,
(b) at least one rule included in each entry, specifying a manner of communications between the corresponding recipient party and an initiating party, and
(c) an initiating party interface arranged to cooperate with an initiating party's communications device to cause communications application software appropriate to the manner of communications specified in said rule to automatically execute at the initiating party's device,
wherein the system manages communications between an initiating party and a recipient party according to each appropriate rule and, in response to a connection request from an initiating party, the server generates data which, when processed at an initiating party device, results in the automatic execution of communications application software, the communications application software determining the manner of communication between the initiating party and the recipient party.
2. A presence system according to claim 1 wherein the presence system comprises a server hosting the database.
3. A presence system according to claim 2 wherein interaction between an initiating party and the database is in the manner of interaction with an internet web site.
4. A presence system according to claim 3 wherein the server generates data processable by an internet enabled device.
5. A presence system according to claim 2 wherein associated with the server is a data conversion module for converting data from an initiating party device into a form which the server may process, and for converting data from the server into a form which the initiating party device may process.
6. A presence system according to claim 4 wherein, in response to a request from an initiating party to communicate, the server generates data which, when processed at an initiating party device, results in at least one instruction or notification.
7. A presence system according to claim 4 wherein the data is dictated by each rule in the relevant recipient party entry for the initiating party requesting to communicate.
8. A presence system according to claim 1 wherein a security mechanism is provided for secure access by a recipient party to their entry.
9. A presence system according to claim 1 wherein, in response to a query from an initiating party, the database returns the unique identifier.
10. A presence system according to claim 1 wherein, in response to a query from an initiating party, the database returns details about a recipient party.
11. A presence system according to claim 10 the database returns details in accordance with each rule for the querying initiating party.
12. A presence system according to claim 1 wherein each entry includes details of each communication device at the disposal of the corresponding recipient party, and each rule specifies to which device communications from an initiating party should be directed.
13. A presence system according to claim 1 wherein each entry includes details of known initiating parties, and there is at least one rule specified for each known initiating party as well as a default rule for every other initiating party.
14. A method of communicating between an initiating party and a recipient party comprising:�
(a) assigning a unique identifier to the recipient party,
(b) making at least one rule specifying the manner of communications between an initiating party and the recipient party, and
(c) causing communications application software appropriate to the manner of communications specified in said rule to automatically open at an initiating party's device,
wherein the unique identifier is used to direct a request for communications from an initiating party to a system which manages communications between the initiating party and the recipient by generating data in accordance with each rule processing the data at an initiating party device results in the automatic execution of communications application software; the communications application software determining the manner of communication between the initiating party and the recipient party.
15. A method according to claim 14 wherein the initiating party queries the system for the unique identifier.
16. A method according to claim 15 wherein the initiating party queries the system using known details of the recipient party.
17. A method according to claim 14 wherein the initiating party queries the system for other details relating to a recipient party.
18. A method according to claim 14 wherein processing data at an in initiating party device results in a notification or instruction at the initiating party device.
19. A method according to claim 14 wherein the system comprises a database and the unique identifier is used to locate an entry relating to a recipient party contained in the database.
20. A method according to claim 19 wherein the recipient party enters contact details into the entry.
21. A method according to claim 19 wherein the recipient party enters details of the communications devices into the entry.
22. A method according to claim 19 wherein the recipient party enters details of known initiating parties into the entry.
23. A method according to claim 19 wherein the recipient party enters into the entry at least one rule for each known initiating party and a default rule for any other initiating parties.
24. A method according to claim 14 wherein data to and from an initiating party and a recipient party is converted from one form to another.
25. A method according to claim 14 wherein data is converted to and from a form which an initiating party and the system respectively can process.
TECHNICAL FIELD The invention relates to communications between parties, and in particular to a system and method facilitating a recipient party to control such communications. The invention also relates to a directory for use in such communications.
BACKGROUND TO THE INVENTION Many people now have various different communication devices at their disposal, such as, for example, so-called plain old telephone service (POTS) devices, mobile telephone devices, personal computers (PC) and hand-held computers. This variety of devices may complicate communications to the extent that, in order to communicate with a recipient party, an initiating party needs to know what devices the recipient party has, which of those devices is currently active and an address or location mechanism for each device. In other words, the initiating party needs to know about what is termed �the presence� of the recipient party.
Directories are available, particularly through the Internet, which provide contact details for individuals. However, the sheer number of these directories can be a problem, both from the point of view of data entry/maintenance and from the point of view of searching for a contact. Moreover, according to how widespread the contact details are to be disseminated and to whom they will be available, there may be a reluctance on the part of a contact to use a directory, or to use it to only a limited extent, because, for instance, of security concerns and the value which included details may have; for example, the addresses may be used for the purpose of compiling sales targetting lists. Allied to this is the fact that the contacts have no control over the use of details and whilst, on the one hand, they may wish to make them available in the interest of promoting communications, they may at the same time potentially expose themselves to unwanted contacts. This, as much as anything, is borne out of the fact that the contact has little if any control over existing communication routes, such as POTS or postal services. For such routes, there may be only two opposite extreme choices for the contact: either the valuable details are given out or they are withheld altogether. For example, not placing a telephone number in a telephone directory is an option, but legitimate initiating parties are then hampered from making contact. The purpose of a directory is undermined if it is not comprehensive and definitive. The problems associated with directories also apply to other instances in which someone may provide contact details, such as with a publication.
OBJECT OF THE INVENTION An object of the invention is to improve communications between parties. Another object of the invention is to give the recipient party control over such communications.
SUMMARY OF THE INVENTION According to a first aspect, the invention provides a presence system comprising a database storing a plurality of entries each relating to a recipient party, wherein each entry is stored according to a unique identifier assigned to the corresponding recipient party and each entry includes at least one rule specifying a manner of communications between the corresponding recipient party and an initiating party, wherein the system manages communications between an initiating party and a recipient party according to the or each appropriate rule.
The presence system according to the first aspect of the invention effectively acts as an intermediary between an initiating party and a recipient party. Within the system, each recipient party enters contact details, of the type typically entered into a contact directory, but access to the details is controlled by the system. According to the identity of the initiating party, the details may or may not be released, or only certain details may be released. The dissemination of details is controlled according to the or each rule entered for the initiating party concerned. Therefore, the recipient party is given control over details disclosed such that they are more inclined to include details of themselves, thereby enabling the directory to be comprehensive and definitive. Moreover, the unique identifier is issued as an address for the recipient party, but it has no value in the sense that it does not enable an initiating party to make direct contact with the corresponding recipient party, merely to direct a request to communicate to the system, which then invokes the or each relevant rule specifying the manner of communication between the initiating and recipient parties. Thus, again, control over the communications rests with the recipient party.
Typically, the presence system may be realised as a server connected to an appropriate network, with the server hosting the database. Interaction between an initiating party and the database may be in the same way as interaction with an Internet web site and the server may generate data which various different initiating party Internet enabled devices may process. Alternatively, associated closely with the server may be a data conversion module for converting data from an initiating party device into a form which the server may process, and for converting data from the server into a form which the initiating party device may process. For instance, the module may comprise an analogue to digital conversion module, say, for voice to HTML conversion. In response to a request from an initiating party to communicate, the server may generate data which, when processed at an initiating party device, results in the opening of a communications application. Alternatively, the data may result in one or more instructions or notifications at the initiating party device. The data is dictated by the or each rule in the relevant recipient party entry for the initiating party requesting to communicate.
Initially, a recipient party will access the system to request inclusion on the database. Having been accepted for inclusion, a recipient party will be provided with a security mechanism, such as password, for accessing the database entry relating to them. They can then enter and maintain contact and other details contained in their entry.
The database may be queried by an initiating party and, in response to a query, the database may return the unique identifier. The query may take the form of use of known recipient party details which the database may compare with contact details it contains. A query may take the form of use of the unique identifier to obtain other details about the corresponding recipient party. The database may return the details in accordance with the or each rule for the initiating party which may specify whether and, if so, what information should be disclosed to the recipient party.
Each entry may include details of the communication devices at the disposal of the corresponding recipient party, and the or each rule may specify to which device communications from an initiating party should be directed. The system may periodically notify known initiating parties of their status in relation to the recipient party, that is, which recipient party device is available for communicating at that time.
Each entry may include details of know initiating parties, and there may be at least one rule specified for each known initiating party as well as a default rule for every other initiating party.
According to a second aspect, the invention provides a method of communicating between an initiating party and a recipient party comprising assigning to the recipient party a unique identifier and making at least one rule specifying the manner of communications between an initiating party and the recipient party, wherein the unique identifier is used to direct a request for communications from an initiating party to a system which manages communications between the initiating party and the recipient party in accordance with the or each rule.
According to a third aspect, the invention provides a directory comprising a plurality of entries each relating to a recipient party, wherein each entry is stored according to a unique identifier assigned to the corresponding recipient party and each entry includes at least one rule specifying a manner of communications between the corresponding recipient party and an initiating party.
According to a fourth aspect, the invention provides a directory comprising a plurality of entries each relating to a recipient party, wherein each entry is stored according to a unique identifier assigned to the corresponding recipient party and each entry includes at least one rule specifying which details from the entry may be disclosed to an initiating party.
BRIEF DESCRIPTION OF THE DRAWINGS FIG. 1 is a schematic diagram of a communications network to which a presence system according to one aspect of the invention is connected.
FIG. 2 is a schematic diagram of a method of communicating using a presence system.
DESCRIPTION OF THE INVENTION With reference to FIG. 1, connected to a communications network 2 is a presence system 4. The system 4 comprises a server hosting a database 10. Also connected to the network 2 are a recipient party 6 and an initiating party 8.
The system 4 is accessible in the manner of an Internet web site. Using a suitable Internet enabled device, any recipient party 6 may apply for use of the system 4. Stored within the database 10 are a plurality of entries each relating to a recipient party. At the time of acceptance for inclusion in the database 10, the system 4 assigns to each recipient party a unique identifier typically of the form name.for.individual @ presence.system.location.address. The prefix of the identifier is used as the key field in the database 10 for each entry, that is, the entry is stored according to the prefix and, subsequently, the prefix is used to access the relevant entry. Once accepted for inclusion, a recipient party may access their entry for details entry and for maintenance and updating purposes as illustrated in Step 10 of FIG. 2.
Each entry includes details typically stored in contact directories such as name, address, telephone number, occupation, nationality, hobbies etc or any other details which enables a recipient party to be identified.
Each recipient party 6 may have several communication devices, all capable of connecting to the network 2, such as a POTS handset 14, a WAP mobile telephone 16, a PC 18 and a hand held computer 20. At any one time, primarily according to location and activity, one of more of the devices 14, 16, 18, 20 may be active for contacting the recipient party 6. Each recipient party 6 enters into their entry the details of the various devices 14, 16, 18, 20 they have available. A recipient party 6 may continually update their entry as to which device is currently active.
Each recipient party 6 may enter into their entry the identity of a number of known initiating parties 8. Against each initiating party, one or more rules may be entered, specifying the manner of communications between each known initiating party 8 and the recipient party 6, such as the device though which the initiating party may contact the recipient party, the form of the communication within the options available through the device, such as, for example, voice or text messaging, and the timeframe within which the rule is to apply. In other words, the rules enable the recipient party 6 to control how any initiating party communicates 8 with them. The recipient party 6 may also specify default rules applicable to all unknown initiating parties 8. The system 4 periodically communications to each known initiating party its status in relation to the recipient party
Individual rules may be altered at any time according to changes of circumstances affecting individual initiating parties 8 or may be globally altered, say, to account for circumstances which affect all initiating parties 8 such as unavailability due to illness.
Each initiating party 8 may have several communication devices, all capable of connecting to the network 2, such as a POTS handset 22, a WAP mobile telephone 24, a PC 26 and hand held computer 28. An initiating party 8 will fall into one of two categories: Either it will know the unique identifier for the recipient party 6, and it may use this to make contact with the recipient party as illustrated in Step 12 of FIG. 2; or it may determine the unique identifier using the contact information it has available, such as name, address occupation etc. as illustrated in Step 14 of FIG. 2.
The process of determining the unique identifier involves an initiating party 8 accessing and querying the system 4. In the event that the initiating party 8 wishes to communicate using the PC 26, a WAP mobile telephone 24, a hand held computer 28 or any other Internet enabled device, the system 4 is accessed in the manner of accessing a web site. In response, a search page is downloaded to the device 24, 26, 28. The page includes various blank boxes or input ports into which the initiating party 8 may insert query criteria, that is, what it knows of the recipient party's personal details. The system 4 will return any matches, possibly more than one according to the specificity of the query criteria. In the case of multiple matches, there will be an option to select one of the or further to hone the query criteria. One or more matches may be stored in a communications application loaded on to the device 24, 26, 28 for later use. Alternatively, a match may be used straight away. Use may be on a �click to call� basis with the unique identifier presented as a link on a further downloaded page. From information stored within the device 24, 26, and 28 the identity of the initiating party 8 is sent to the system 4. The identity is compared with the identities of known initiating parties 8 included in the recipient party's entry. If a known initiating party is determined, the communication rules applicable to that party are invoked. If the initiating party is unknown, the default rules are invoked. Data is returned to the initiating party's device 24, 26, 28 according to the invoked rules as illustrated in step 18 of FIG. 2.
The data may result in the opening at the initiating party's device 24, 26, 28 of the communications application appropriate to the manner of communication dictated by the rule. For example, if the rule applicable to that subscriber at this particular time is �communicate by e-mail�, the data may be processed at the subscriber device, resulting in an e-mail application, being opened: A message window may be automatically generated, made ready with the appropriate address. Once the message has been composed, it is sent. The recipient party 6 can, as with any other e-mail message, choose how to receive the message, that is, it could be downloaded as text or �listened to� via a text to audio conversion mechanism of the type now widely available.
Alternatively, the data may result in the opening of an SMS text managing application at the initiating party device 24, 26, 28, which enables the initiating party 8 to dispatch a text message to the recipient party.
Further alternatively, at least in the case that the initiating party is using a PC 26 or WAP mobile telephone 24, the data may result in the opening of a voice calling application. The voice call may be directed to the current voice calling device 14, 16, 18, 20 of the recipient party or may be directed to a voice mail message caching facility, for later access.
In the event that the initiating party 8 is using a POTS device 22, access to the directory server may be gained by dialling into a data conversion module 12 acting as a voice to data conversion facility. This enables the recipient party search criteria to be input verbally. This is achieved through a series of verbal prompts which the facility 12 puts to the initiating party 8. The unique identifier for the recipient party 6 is either relayed to the initiating party verbally, say for it to use with an alternative device, or the facility 12 gives verbal prompts of further actions such as �press 1 to call, press 2 to store�. A �call� response relays the identity of the initiating party 8 to the system 4. The identity is compared with the identities for the known subscribers stored in the recipient party's entry and the appropriate communication rules are invoked. If the rule is to communicate by voice, the initiating device 22 is connected to the specified voice device 14, 16, 18, 20 of the recipient party 6. If the rule is to communicate by non-voice, the voice recognition facility 12 translates a message spoken by the initiating party 8 into data and relays the data to the specified device 16, 18, 20 of the recipient party 6.
Patent CitationsCited PatentFiling datePublication dateApplicantTitleUS3816668Nov 15, 1972Jun 11, 1974Bell Telephone Labor IncArrangement for providing switched range extensionUS4602129Sep 29, 1982Jul 22, 1986Vmx, Inc.Electronic audio communications system with versatile message deliveryUS4740788Oct 6, 1986Apr 26, 1988Konneker Lloyd KMethod of providing location dependent visitor dispatching serviceUS5197092Oct 31, 1990Mar 23, 1993Mccaw Cellular Communications, Inc.Location registration system for a personal communicator such as a cellular telephoneUS5200994Aug 2, 1989Apr 6, 1993Kabushiki Kaisha ToshibaCommunication terminal apparatus and control method with party identification featuresUS5206901Dec 23, 1991Apr 27, 1993At&T Bell LaboratoriesMethod and apparatus for alerting multiple telephones for an incoming callUS5283856 *Oct 4, 1991Feb 1, 1994Beyond, Inc.Event-driven rule-based messaging systemUS5373549Dec 23, 1992Dec 13, 1994At&T Corp.Multi-level conference management and notificationUS5432841Jul 10, 1992Jul 11, 1995Rimer; Neil A.System for locating and communicating with mobile vehiclesUS5608786Feb 13, 1995Mar 4, 1997Alphanet Telecom Inc.Unified messaging system and methodUS5652789Sep 30, 1994Jul 29, 1997Wildfire Communications, Inc.Network based knowledgeable assistantUS5696900Apr 28, 1995Dec 9, 1997Fujitsu LimitedPersonal communication service distributed control system for a network communication system including a plurality of hardware resourcesUS5737011May 3, 1995Apr 7, 1998Bell Communications Research, Inc.Infinitely expandable real-time video conferencing systemUS5742668Jun 6, 1995Apr 21, 1998Bell Communications Research, Inc.Electronic massaging networkUS5742905Sep 19, 1994Apr 21, 1998Bell Communications Research, Inc.Personal communications internetworkingUS5768513Jun 27, 1996Jun 16, 1998At&T Corp.Multimedia messaging using the internetUS5802253 *Feb 26, 1996Sep 1, 1998Banyan Systems IncorporatedEvent-driven rule-based messaging systemUS5870549 *Oct 6, 1997Feb 9, 1999Bobo, Ii; Charles R.Systems and methods for storing, delivering, and managing messagesUS5896128May 3, 1995Apr 20, 1999Bell Communications Research, Inc.System and method for associating multimedia objects for use in a video conferencing systemUS5917489 *Jan 31, 1997Jun 29, 1999Microsoft CorporationSystem and method for creating, editing, and distributing rules for processing electronic messagesUS5946386Mar 11, 1996Aug 31, 1999Xantel CorporationCall management system with call control from user workstation computersUS5951638 *Mar 21, 1997Sep 14, 1999International Business Machines CorporationIntegrated multimedia messaging systemUS5974465 *Jan 21, 1998Oct 26, 19993Com CorporationMethod and apparatus for prioritizing the enqueueing of outbound data packets in a network deviceUS6006253Oct 31, 1997Dec 21, 1999Intel CorporationMethod and apparatus to provide a backchannel for receiver terminals in a loosely-coupled conferenceUS6021428 *Jan 22, 1998Feb 1, 2000Genesys Telecommunications Laboratories, Inc.Apparatus and method in improving e-mail routing in an internet protocol network telephony call-in-centerUS6023762Jul 9, 1997Feb 8, 2000Northern Telecom LimitedMulti-view personalized communications agentUS6058178Feb 20, 1996May 2, 2000Solopoint, Inc.Method for routing incoming calls to a user's premises on a POTS telephone lineUS6094681 *Mar 31, 1998Jul 25, 2000Siemens Information And Communication Networks, Inc.Apparatus and method for automated event notificationUS6101531 *Apr 15, 1998Aug 8, 2000Motorola, Inc.System for communicating user-selected criteria filter prepared at wireless client to communication server for filtering data transferred from host to said wireless clientUS6104799Oct 24, 1997Aug 15, 2000At&T Corp.Customer defined call setupUS6147977 *Dec 12, 1997Nov 14, 2000Motorola, Inc.Method and apparatus for processing messages based on originator and recipient prioritiesUS6148328Jan 29, 1998Nov 14, 2000International Business Machines Corp.Method and system for signaling presence of users in a networked environmentUS6157945 *Jul 1, 1998Dec 5, 2000Ricoh Company, Ltd.Digital communication device and method including a routing functionUS6175858 *Jul 13, 1998Jan 16, 2001At&T Corp.Intelligent network messaging agent and methodUS6185565Dec 18, 1997Feb 6, 2001Nortel Networks CorporationSystem and method for communication session disposition responsive to events in a telecommunications network and the internetUS6243398Jan 8, 1997Jun 5, 2001Vocaltec Communications Ltd.System and method for personal multimedia communication over a packet switched networkUS6243714May 1, 1998Jun 5, 2001Ubique Ltd.Co-presence data retrieval systemUS6247043 *Jun 11, 1998Jun 12, 2001International Business Machines CorporationApparatus, program products and methods utilizing intelligent contact managementUS6286029Apr 28, 1997Sep 4, 2001Sabre Inc.Kiosk controller that retrieves content from servers and then pushes the retrieved content to a kiosk in the order specified in a run listUS6301339Dec 22, 1997Oct 9, 2001Data Race, Inc.System and method for providing a remote user with a virtual presence to an officeUS6301609 *Sep 8, 1999Oct 9, 2001Lucent Technologies Inc.Assignable associate priorities for user-definable instant messaging buddy groupsUS6310947 *May 24, 2000Oct 30, 2001Intervoice Limited PartnershipOne number LAN based calendarUS6330317Nov 9, 1999Dec 11, 2001Dean GarfinkelCall blocking systemUS6333973 *Apr 23, 1997Dec 25, 2001Nortel Networks LimitedIntegrated message centerUS6350066 *Nov 5, 1998Feb 26, 2002Bobo, Ii Charles R.Systems and methods for storing, delivering, and managing messagesUS6356934Apr 28, 1997Mar 12, 2002Sabre Inc.Intermediate server having control program for storing content accessed during browsing sessions and playback program for asynchronously replaying browsing sessionsUS6360252 *Aug 31, 2000Mar 19, 2002Fusionone, Inc.Managing the transfer of e-mail attachments to rendering devices other than an original e-mail recipientUS6370233Aug 3, 1999Apr 9, 2002Ameritech CorporationSecurity system with call management functionalityUS6397259 *May 29, 1998May 28, 2002Palm, Inc.Method, system and apparatus for packet minimized communicationsUS6404762 *Jun 9, 1998Jun 11, 2002Unisys CorporationUniversal messaging system providing integrated voice, data and fax messaging services to pc/web-based clients, including a session manager for maintaining a session between a messaging platform and the web-based clientsUS6424841Feb 18, 1999Jul 23, 2002Openwave Systems Inc.Short message service with improved utilization of available bandwidthUS6430604 *Aug 3, 1999Aug 6, 2002International Business Machines CorporationTechnique for enabling messaging systems to use alternative message delivery mechanismsUS6437818 *May 5, 1998Aug 20, 2002Collaboration Properties, Inc.Video conferencing on existing UTP infrastructureUS6438583 *Jun 23, 1999Aug 20, 2002Re-Route CorporationSystem and method for re-routing of e-mail messagesUS6438585 *Jan 16, 2001Aug 20, 2002Research In Motion LimitedSystem and method for redirecting message attachments between a host system and a mobile data communication deviceUS6445694 *Mar 2, 1998Sep 3, 2002Robert SwartzInternet controlled telephone systemUS6457060Apr 30, 1998Sep 24, 2002Openwave Systems Inc.Method and apparatus for flexibly linking to remotely located content on a network server through use of aliasesUS6510461Jun 30, 1997Jan 21, 2003Sun Microsystems, Inc.System for managing and automatically deleting network address identified and stored during a network communication session when the network address is visitedUS6564321Apr 23, 2001May 13, 2003Bobo Ii Charles RSystems and methods for storing, delivering, and managing messagesUS6584314Jun 9, 2000Jun 24, 2003Nokia CorporationLocation management in a mobile telecommunication systemUS6594354Nov 5, 1999Jul 15, 2003Nortel Networks LimitedMethod and apparatus for alert control on a communications systemUS6606647 *Jan 11, 1999Aug 12, 2003Infospace, Inc.Server and method for routing messages to achieve unified communicationsUS6609128 *Jul 30, 1999Aug 19, 2003Accenture LlpCodes table framework design in an E-commerce architectureUS6628194Aug 31, 1999Sep 30, 2003At&T Wireless Services, Inc.Filtered in-box for voice mail, e-mail, pages, web-based information, and faxesUS6807423Dec 14, 1999Oct 19, 2004Nortel Networks LimitedCommunication and presence spanning multiple access networksUS20020114431Aug 1, 2001Aug 22, 2002Mcbride Mark A.Caller control systemUS20020120696 *Apr 6, 2001Aug 29, 2002Mousseau Gary P.System and method for pushing information from a host system to a mobile data communication deviceWO1999034628A1Dec 18, 1998Jul 8, 1999Ericsson Telefon Ab L MOn-line notification in a mobile communications system* Cited by examinerNon-Patent CitationsReference112 pages downloaded frorm http//:ww.icq.com on Aug. 11, 1999, "ICQ Site Guide".22 pages downloaded from http://www.lucent.com on Apr. 6, 2000 comprising a press release date Jun. 9, 1999.33 pages downloaded form http://ww.generalmagic.com on Aug. 11, 1999, "General Magre-Portico".44 pages downloaded form http://messenger.msn.com on Aug. 11, 1999, "MSM Messenger Service".55 pages downloaded from http/www.wildfire.com on Aug. 11, 1999, "Wildfire Resume".67 pages downloaded from http://www.oz.com/pulse, Aug. 1999, "iPulse".7Anthonoy D. Joseph et al., The Case for Services over Cascaded Networks, Oct. 30, 1998, 9 pages.8Bhaskaran Raman et al, The Iceberg Project: Defining the IP and Telecom Intersection, IT Pro Nov. 1999, 8 pages.9Calsyn & Dusseault, Presence Information Protocol Requirements, Feb. 9, 1998, 13 pages.10David G. Boyer et al, The Personal Presence System-A Wide Area Network Resource for the Real Time Composition of Multipoint Multimedia Communications, Oct. 1994, 8 pages, pp. 453-460.11G. Mohr et al., PIP-DEMO: An Interoperable Presence Information Protocol, Aug. 1998, 16 pages.12Guido Appenzeller et al., The Mobile People Architecture, Technical Report: CSL-TR-00000, Jan. 1999, 13 pages.13Keith Pleas, The Evolution of NT-DCOM in NT 5.0, Windows & Net Magazine Network, Sep. 1996, 2 pages.14Mark Day et al., Instant Messaging/Presence Protocol Requirements, Aug. 13, 2003, 19 pages.15Martin Calsyn, Rendezvous Protocol, Nov. 21, 1997, 21 pages.16Nortel Networks, Nortel's Leadership Drive in Wireless Internet, Nortel's Technology Perspectives, Monday, Oct. 19, 1998, 11 Pages, Corporate and Technology Communications, Ottawa, Canada.17One page photo copy of a newspaper article. Financial Times Jun. 9, 1999, "How to stay in touch and keep stress at a distance".18Rosenberg et al., SIP For Presence, Nov. 13, 1998, 18 pages.19S. Aggarwal, et al., Presence Information Protocol Requirements, Aug. 7, 1998, 4 pages.20Shingo Fujimoto et al., IDentity Infrastructure Protocol (IDIP) Aug. 6, 1998, 20 pages.Referenced byCiting PatentFiling datePublication dateApplicantTitleUS7313760Dec 19, 2002Dec 25, 2007Microsoft CorporationContact pickerUS7360172Dec 19, 2002Apr 15, 2008Microsoft CorporationContact controlsUS7360174Dec 19, 2002Apr 15, 2008Microsoft CorporationContact user interfaceUS7412522 *Aug 1, 2003Aug 12, 2008Mitel Networks CorporationSystem and method for facilitating communication using presence and communication servicesUS7418663May 13, 2004Aug 26, 2008Microsoft CorporationContact picker interfaceUS7430719 *Jul 7, 2004Sep 30, 2008Microsoft CorporationContact text boxUS7549125Oct 23, 2003Jun 16, 2009Microsoft CorporationInformation pickerUS7636719Dec 19, 2002Dec 22, 2009Microsoft CorporationContact schemaUS7660898 *Jul 29, 2003Feb 9, 2010At&T Intellectual Property I, L.P.Presence enhanced telephony service architectureUS7802191Aug 20, 2008Sep 21, 2010Microsoft CorporationContact picker interfaceUS7814438Jun 8, 2007Oct 12, 2010Microsoft CorporationContact pageUS7953759Feb 17, 2004May 31, 2011Microsoft CorporationSimplifying application access to schematized contact dataUS8005200Dec 23, 2004Aug 23, 2011Gryphon Networks Corp.System and method for control of communications connections and notificationsUS8006190 *Oct 31, 2006Aug 23, 2011Yahoo! Inc.Social namespace addressing for non-unique identifiersUS8050394Oct 3, 2005Nov 1, 2011Gryphon Networks Corp.System and method for control of communications connections and notificationsUS8099395 *Jun 24, 2004Jan 17, 2012Oracle America, Inc.System level identity objectUS8195711Mar 29, 2011Jun 5, 2012Microsoft CorporationSimplifying application access to schematized contact dataUS8249232Apr 8, 2004Aug 21, 2012Gryphon Networks Corp.System and method for control of communications connectionsUS8370349Feb 28, 2007Feb 5, 2013Yahoo! Inc.Instant contact searching and presentation by categoryUS8385524Jul 21, 2011Feb 26, 2013Gryphon Networks Corp.System and method for control of communications connections and notificationsUS8407600Sep 20, 2010Mar 26, 2013Microsoft CorporationContact picker interfaceUS8443092 *Dec 23, 2003May 14, 2013Alcatel LucentPresentity filtering for user preferencesUS8509406Dec 15, 2009Aug 13, 2013At&T Intellectual Property I, L.P.Presence enhanced telephony service architectureUS8526428Apr 21, 2005Sep 3, 2013Gryphon Networks Corp.System and method for control of communications connections and notificationsUS8572113Sep 2, 2010Oct 29, 2013Gryphon Networks Corp.Network calling privacy with recordingUS8599801Feb 1, 2007Dec 3, 2013Yahoo! Inc.Collecting implicit information for determining context of event actionsUS8612522 *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 userUS8634528May 10, 2013Jan 21, 2014Gryphon Networks Corp.System and method for control of communications connections and notificationsUS20050135240 *Dec 23, 2003Jun 23, 2005Timucin OzugurPresentity filtering for user preferencesUS20110107228 *Jul 2, 2010May 5, 2011Chun-Min HuangMethod of simultaneously displaying status of a plurality of contacts in an address book and related communication device* Cited by examinerClassifications U.S. Classification707/694, 707/922, 707/828, 707/999.009, 707/781, 707/769, 707/999.01International ClassificationG06F17/30, G06F17/00Cooperative ClassificationY10S707/922, Y10S707/99939, H04M3/42374, H04L29/1216, H04L61/157, H04M3/4935, H04L67/24, H04L67/306European ClassificationH04L61/15H, H04L29/12A2H, H04L29/08N23, H04L29/08N29U, H04M3/493D4, H04M3/42S2Legal EventsDateCodeEventDescriptionOct 28, 2011ASAssignmentOwner name: ROCKSTAR BIDCO, LP, NEW YORKEffective date: 20110729Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:NORTEL NETWORKS LIMITED;REEL/FRAME:027164/0356Jun 22, 2010FPAYFee paymentYear of fee payment: 4Aug 22, 2001ASAssignmentOwner name: NORTEL NETWORKS LIMITED, CANADAFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:HARKER, ANDREW N.;WILKINSON, ALAN;REEL/FRAME:012094/0400Effective date: 20010702RotateOriginal ImageGoogle Home - Sitemap - USPTO Bulk Downloads - Privacy Policy - Terms of Service - About Google Patents - Send FeedbackData provided by IFI CLAIMS Patent Services©2012 Google