System and method for call routing in an ip telephony network

• US 20050097222A1
• Filed: 06/12/2002
• Published: 05/05/2005
• Est. Priority Date: 06/12/2001
• Status: Abandoned Application

• Current Assignee: Trustees Of Columbia University In The City Of New York (Columbia University)
• Original Assignee: Trustees Of Columbia University In The City Of New York (Columbia University)
• Inventors: Schulzrinne, Henning, Jiang, Wenyu, Lennox, Jonathan, Singh, Kundan
• Application Number:
  US10/480,505
• Publication Number:
  US 20050097222A1
• Time in Patent Office: Days
• US Class Current: 709/245
• CPC Class Codes: H04L 2101/37 E-mail addresses
• CPC Class Codes: H04L 2101/385 Uniform resource identifier for session initiation protocol [SIP URI]
• CPC Class Codes: H04L 61/00 Network arrangements, protocols or services for addressing or naming
• CPC Class Codes: H04L 61/30 Managing network names, e.g. use of aliases or nicknames name-to-address mapping H04L61/45
• CPC Class Codes: H04L 61/301 Name conversion
• 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/4552 Lookup mechanisms between a plurality of directories; Synchronisation of directories, e.g. metadirectories
• CPC Class Codes: H04L 61/4557 Directories for hybrid networks, e.g. including telephone numbers
• CPC Class Codes: H04L 63/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• CPC Class Codes: H04L 63/104 Grouping of entities
• CPC Class Codes: H04L 65/103 in the network
• CPC Class Codes: H04L 65/104 in the network
• CPC Class Codes: H04L 65/1043 Gateway controllers, e.g. media gateway control protocol [MGCP] controllers
• CPC Class Codes: H04L 65/1069 Session establishment or de-establishment
• CPC Class Codes: H04L 65/1101 Session protocols
• CPC Class Codes: H04L 65/1104 Session initiation protocol [SIP]
• CPC Class Codes: H04L 65/1106 Call signalling protocols; H.323 and related

Abstract

A method of processing a call request to a callee in a network telephony system is provided which includes mapping a hostname portion of a callee address to a canonical form of the hostname and determining a canonical form of a username portion of a callee address. The canonical form of the user identity of the callee is then used as an index to a user database to retrieve a callee database record. The callee database record is then used to determine call routing based on the retrieved callee database record, such as user location, preferences and policy data stored in the record. The method is generally performed by a signaling server in the network, such as a SIP proxy server. The signaling server can also provide security features such as caller authentication. A scalable signaling and routing architecture is also provided.

Claims

1. A method of processing a call request to a callee in a network telephony system comprising:

mapping a hostname portion of a callee address to a canonical form of the hostname;

determining a canonical form of a username portion of the callee address;

applying the canonical form of the hostname and username as an index to a user database to retrieve a callee database record; and

determining routing of the call request based on the retrieved callee database record.

2. The method of processing a call request to a callee as defined by claim 1, wherein the hostname mapping operation includes comparing the hostname portion against a range of addresses for an associated domain.

3. The method of processing a call request to a callee as defined by claim 1, wherein the step of determining a canonical form of a username portion of a callee address includes determining whether the username portion corresponds to a known user alias.

4. The method of processing a call request to a callee as defined by claim 1, wherein the step of determining a canonical form of a username portion of a callee address includes determining whether the username portion corresponds to a known e-mail alias.

5. The method of processing a call request to a callee as defined by claim 1, wherein the step of determining a canonical form of a username portion of a callee address includes determining whether the username portion can be associated with a first name, last name combination stored in a user registration file.

6. The method of processing a call request to a callee as defined by claim 5, wherein the user registration file includes a password file.

7. The method of processing a call request to a callee as defined by claim 1, wherein the step of determining a canonical form of a username portion of a callee address includes determining whether the username portion corresponds to a telephone number recognized in a dial plan translation table.

8. The method of processing a call request to a callee as defined by claim 1, wherein the step of determining a canonical form of a username portion of a callee address includes determining whether the username portion corresponds to one of a known user alias;

a known e-mail alias, a first name-last name combination from a user registration table, and a telephone number recognized in a dial plan translation table.

9. The method of processing a call request to a callee as defined by claim 1, wherein the callee database record includes callee contact data and callee preference data for routing incoming call requests.

10. The method of processing a call request to a callee as defined by claim 1, further comprising the step of authenticating a caller prior to routing of the call request.

11. The method of processing a call request to a callee as defined by claim 10, wherein for an unknown caller, the step of authenticating a caller comprises:

rejecting the initial call request;

transmitting an authentication message to an email address corresponding to a user identity of the caller; and

if the authentication message is received by the caller, receiving the authentication message from the caller in a subsequent call request from that caller.

12. A computer based process for a signaling server for routing call requests in a network telephony system comprising:

mapping a hostname portion of a callee address to a canonical form of the hostname;

determining a canonical form of a username portion of a callee address;

applying the canonical form of the hostname and username as an index to a user database to retrieve a callee database record; and

determining routing of the call request based on the retrieved callee database record.

13. The computer based process for a signaling server for routing call requests in a network telephony system as defined by claim 12, wherein the step of determining a canonical form of a username portion of a callee address includes evaluating a plurality of database tables to determine whether the username portion corresponds to one of a known user alias;

a known e-mail alias, a first name-last name combination from a user registration table, and a telephone number recognized in a dial plan translation table.

14. The computer based process for a signaling server for routing call requests in a network telephony system as defined by claim 12, wherein the hostname mapping operation includes comparing the hostname portion against a range of addresses for an associated domain.

15. The computer based process for a signaling server for routing call requests in a network telephony system as defined by claim 12, wherein the step of determining a canonical form of a username portion of a callee address includes determining whether the username portion corresponds to a known user alias.

16. The computer based process for a signaling server for routing call requests in a network telephony system as defined by claim 12, wherein the step of determining a canonical form of a username portion of a callee address includes determining whether the username portion corresponds to a known e-mail alias.

17. The computer based process for a signaling server for routing call requests in a network telephony system as defined by claim 12, wherein the step of determining a canonical form of a username portion of a callee address includes determining whether the username portion can be associated with a first name, last name combination stored in a user registration file.

18. The computer based process for a signaling server for routing call requests in a network telephony system as defined by claim 17, wherein the user registration file includes a password file.

19. The computer based process for a signaling server for routing call requests in a network telephony system as defined by claim 12, further comprising the step of authenticating a caller prior to routing of the call request.

20. The computer based process for a signaling server for routing call requests in a network telephony system as defined by claim 13, wherein for an unknown caller, the step of authenticating a caller comprises:

rejecting the initial call request;

transmitting an authentication message to an email address corresponding to a user identity of the caller; and

if the authentication message is received by the caller, receiving the authentication message from the caller in a subsequent call request from that caller.

21. A scalable telephony network for routing call requests in an IP telephony network comprising:

at least one first stage signaling server, the at least one first stage signaling server receiving call requests from callers;

at least two second stage signaling servers, each of the at least two second stage signaling servers maintaining a database of a subset of users of the network based on a predetermined property of the user identity, the at least two second stage signaling servers being provided with a portion of the call requests from the at least one first stage signaling server in accordance with the predetermined property of the user identity of the callee.