Recipient controlled contact directories

• US 7,162,474 B1
• Filed: 05/10/2001
• Issued: 01/09/2007
• Est. Priority Date: 05/10/2001
• Status: Expired due to Fees

• Current Assignee: RPX Clearinghouse LLC (RPX Corporation)
• Original Assignee: Nortel Networks Limited (Nortel Networks Corporation)
• Inventors: Wilkinson, Alan, Harker, Andrew N
• Primary Examiner(s): Wong, Don
• Assistant Examiner(s): Black, Linh
• Application Number:
  US09/852,995
• Time in Patent Office: 2,070 Days
• Field of Search: 707 1-1041, 709/102, 709/103, 709/200, 709/203, 709/230, 709/232, 709/340, 709/240, 709/206, 709/10, 709/320, 709/23, 370/229, 370/235, 370/329, 379/93.09, 379/93.11, 379/100.17, 379/100.171
• US Class Current: 707/694
• CPC Class Codes: H04L 61/4557 Directories for hybrid networks, e.g. including telephone numbers
• CPC Class Codes: H04L 67/306 User profiles
• CPC Class Codes: H04L 67/54 Presence management, e.g. monitoring or registration for receipt of user log-on information, or the connection status of the users
• CPC Class Codes: H04M 3/42374 where the information is provided to a monitoring entity such as a potential calling party or a call processing server
• CPC Class Codes: H04M 3/4935 Connection initiated by DAS system
• CPC Class Codes: Y10S 707/922 Communications
• CPC Class Codes: Y10S 707/99939 Privileged access

Abstract

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.

Claims

1. A presence system comprising:

(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.