Communications network and method having accessible directory of user profile data

• US 6,694,375 B1
• Filed: 05/05/2000
• Issued: 02/17/2004
• Est. Priority Date: 12/04/1997
• Status: Expired due to Term

• Current Assignee: British Telecommunications PLC (BT Group PLC)
• Original Assignee: British Telecommunications PLC (BT Group PLC)
• Inventors: Beddus, Simon A, Bruce, Gary L
• Primary Examiner(s): Lim, Krisna
• Application Number:
  US09/530,732
• Time in Patent Office: 1,383 Days
• Field of Search: 709/203, 709/206, 709/244, 709/249, 707/10
• US Class Current: 709/249
• CPC Class Codes: H04L 61/4523 using lightweight directory access protocol [LDAP]
• CPC Class Codes: H04L 61/4535 using an address exchange platform which sets up a session between two nodes, e.g. rendezvous servers, session initiation protocols [SIP] registrars or H.323 gatekeepers
• CPC Class Codes: H04L 61/4557 Directories for hybrid networks, e.g. including telephone numbers
• CPC Class Codes: H04L 67/306 User profiles

Abstract

In a communications network, each of a number of users registers user profile data in a directory. The directory is available to other users. The user profile data includes identifiers for one or more of a plurality of call control protocols. Prior to establishing a call, a user retrieves user profile data for the called party from the directory. The call is then established using a call control protocol which was identified in the relevant user profile.

Claims

1. A method of operating a communications network, comprising;

a) for each of a plurality of users of the network, storing user profile data in a directory, which is accessible to other users of the network, the user profile data including identifiers for one or more of a plurality of different call control protocols, wherein at least one of the identifiers is for a call control protocol which is designated as being non-persistent;

b) prior to establishing a call from a calling party to a called party, determining if the called party is logged into the network and if so making available to the calling party all of said identifiers whereas if the called party is not determined to be logged into the network, making available to the calling party all of the identifiers except the at least one identifier designated as being non-per-sistent; and

c) subsequently establishing the call using a call control protocol by the identifier or identifiers made available to the calling party in step b).

2. A method according to claim 1, in which the user profile data includes at least one network address for a user terminal.

3. A method according to claim 1, in which the user profile data further comprises network call control identities for each network driver used by a user to access the network.

4. A method according to claim 1, in which in the step of storing user profile data, the user profile data is structured as a hierarchy of objects including a user profile parent object and at least one client capability child object.

5. A method according to claim 4, in which the hierarchy of objects further comprises network address objects and call control objects, the network address objects and call control objects being related to the client capability object as child objects to parent object.

6. A method according to claim 1, including making available to the calling party different user profile data for the called party depending on the time of day.

7. A communications system comprising:

a) a network;

b) a multiplicity of client terminals connected to the network, and different ones of the multiplicity of client terminals having different call control capabilities; and

c) a directory which is accessible to the multiplicity of client terminals and which is programmed with user profile data for users of the client terminals, which user profile data includes identifiers for one or more of a plurality of different call control protocols, wherein at least one of the identifiers is for a call control protocol which is designated as being non-persistent.

8. A system according to claim 7, in which the directory is located entirely on a server which is remote from the client terminals and which is accessed via the network.

9. A system according to claim 7, in which the directory comprises directory system proxies located locally at respective ones of the client terminals and a database which is located remotely from the client terminals and which is accessible via the directory system proxies.

10. A system according to claim 7, in which the directory includes both call control protocol identifiers and network addresses.

11. A system according to claim 7, further comprising:

d) a server computer which determines whether or not a called client terminal is logged into the network and providing respective identifiers of both persistent and non-persistent call control protocols to a calling client terminal based on a determination that the called client terminal is logged into the network and providing only identifiers(s) of persistent call control protocol(s) to the calling client terminal based on a determination that the called client terminal is not logged into the network.

12. A server computer connectable to a communications network, the server computer being operable to provide a directory service to client devices connected to the network, the server computer comprising:

a) a data store for storing, for each of a plurality of users of the network, user profile data which is accessible to other users of the network, the user profile data including identifiers for one or more of a plurality of different call control protocols, wherein at least one of the identifiers is for a call control protocol which is designated as being non-persistent; and

b) means for determining, prior to establishing a call from a calling party to a called party, if the called party is logged into the network and for making available to the calling party all of said identifiers if the called party is determined to be logged into the network and for making available to the calling party all of the identifiers except the at least one identifier designated as non-persistent if the called party is not determined to be logged into the network.