Shared DNS Domain Handling

• US 20100217856A1
• Filed: 10/18/2007
• Published: 08/26/2010
• Est. Priority Date: 10/18/2007
• Status: Active Grant

• Current Assignee: Telefonaktiebolaget LM Ericsson
• Original Assignee: Telefonaktiebolaget LM Ericsson
• Inventors: Falkena, Jonas
• Granted Patent: US 8,949,398 B2
• Time in Patent Office: Days
• US Class Current: 709/223
• CPC Class Codes: H04L 2101/385 Uniform resource identifier for session initiation protocol [SIP URI]
• 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/4511 using domain name system [DNS]
• CPC Class Codes: H04L 65/1016 IP multimedia subsystem [IMS]
• CPC Class Codes: H04L 65/1069 Session establishment or de-establishment

Abstract

Instead of rejecting an incoming request at a node of a SIP domain, e.g. an IMS domain, when a user database query has failed, it is determined whether the DNS domain name of the request is registered as a shared domain or not. If it is found that the DNS domain name is registered as a shared domain, the DNS domain name is resolved into a globally routable URI, and the request is routed towards the terminating entity. If, however, the DNS domain name is not shared, the request is rejected. Such a mechanism enables operators to allow for a DNS domain name to be utilized by more than one SIP domain.

Claims

1. A method in a node of a SIP domain for handling an incoming request for which a user database query has failed, the method comprising the following steps:

determining if the DNS domain name of said request is registered as a shared domain,

resolving said DNS domain name into a globally routable URI, and

one of routing said request towards the terminating entity if said DNS domain name is registered as a shared domain, and

rejecting said request if said DNS domain is not registered as a shared domain.

2. The method according to claim 1, wherein said determining step comprises checking configuration data.

3. The method according to claim 2, wherein said configuration data comprises all DNS domains, managed by the operator of said SIP domain, and an associated parameter, indicating whether the respective DNS domain is a shared domain or not.

4. The method according to claim 3, wherein said configuration data further comprises a post for storing one or more URIs, each indicating a SIP domain with which a respective DNS domain is shared.

5. The method according to claim 4, wherein if said configuration data comprises one or more SIP domain names, this information is used when resolving said DNS domain name into a globally routable URI.

6. The method according to claim 2, wherein if no SIP domain name is registered in said configuration data as a shared DNS domain, the respective DNS domain name is resolved after having performed a query.

7. The method according to claim 1, wherein said node is a Call Session Control Function (CSCF).

8. The method according to claim 7, wherein said CSCF is an Interrogating CSCF (I-CSCF).

9. The method according to claim 1, wherein said SIP domain is an IMS domain.

10. The method according to claim 1, wherein said query is a DNS query.

11. A node of a SIP domain for handling an incoming request for which a user database query has failed, the node comprising:

a query unit for initiating a domain checking procedure in response to said failed user database query, and

a domain checking unit for executing said domain checking procedure comprising

determining if the DNS domain of said request is registered as a shared domain or not, wherein said domain checking unit is arranged for resolving said DNS domain name into a globally routable URI and to route said request towards the terminating entity if said DNS domain is registered as a shared domain, or reject said request if said DNS domain is not registered as a shared domain.

12. The node according to claim 11, wherein said domain checking procedure comprises checking configuration data stored at or in association with said node.

13. The node according to claim 12, wherein said configuration data comprises all DNS domains, managed by the operator of said SIP domain, and an associated parameter, indicating whether the respective DNS domain is a shared domain or not.

14. The node according to claim 13, wherein said configuration data further comprises a post for storing one or more URIs, each indicating a SIP domain with which a respective DNS domain is shared.

15. The node according to claim 11, wherein said domain checking unit is arranged for resolving said DNS domain name into a globally routable URI on the basis of said configuration data in case one or more SIP domains with which the respective DNS domain is shared are registered in said configuration data.

16. The node according to claim 11, wherein said domain checking unit is arranged for resolving said DNS domain name after having performed a query if no SIP domain is registered in said configuration data.

17. The node according to claim 11, wherein said node is a Call Session Control Function (CSCF).

18. The node according to claim 17, wherein said CSCF is an Interrogating CSCF (I-CSCF).

19. The node according to claim 11, wherein said SIP domain is an IMS domain.

20. The node according to claim 11, wherein said query is a DNS query.