METHOD AND APPARATUS TO CARRY OUT RESOLUTION OF ENTITY IDENTIFIER IN CIRCUIT-SWITCHED NETWORKS BY USING A DOMAIN NAME SYSTEM

• US 20030081754A1
• Filed: 10/29/2001
• Published: 05/01/2003
• Est. Priority Date: 10/29/2001
• Status: Active Grant

• Current Assignee: Telefonaktiebolaget LM Ericsson
• Original Assignee: Telefonaktiebolaget LM Ericsson
• Inventors: Plata Andres, Isabel, Esparza, Victor Ferraro, Khello, Robert, Cobo, Miguel
• Granted Patent: US 6,839,421 B2
• Time in Patent Office: Days
• US Class Current: 379/221.01
• CPC Class Codes: H04L 61/4511 using domain name system [DNS]
• CPC Class Codes: H04L 61/4557 Directories for hybrid networks, e.g. including telephone numbers
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04W 4/16 Communication-related supplementary services, e.g. call-transfer or call-hold
• CPC Class Codes: H04W 8/28 Number portability ; Network address portability
• CPC Class Codes: H04W 88/16 Gateway arrangements
• CPC Class Codes: Y10S 379/90 Internet, e.g. Internet phone, webphone, internet-based telephony

Abstract

An efficient interface for service exchange is provided between a circuit-switched communications network and a domain naming system (DNS) in a packet-switched communications network. A node in the circuit-switched communications network receives from a first entity a request for a first service involving a second entity associated with a second entity identifier. A message is sent from the circuit-switched network node to a DNS server in the packet-switched network requesting a second service related to the second entity identifier. The result of the second service from the DNS server is used in providing the first service.

Claims

1. A method for a circuit-switched communications network to provide communication services to a subscriber, comprising:

receiving from a first entity a request over the circuit-switched network for a first service involving a second entity associated with a second entity identifier;

sending a message to a domain name system (DNS) server in a packet-switched network requesting a second service related to the second entity identifier;

receiving a result of the second service from the DNS server; and

providing the first service using the result.

2. The method in claim 1, wherein the first service is an electronic communication between first and second entities, and the second service is a resolution of the second entity identifier.

3. The method in claim 2, wherein a circuit-switched routing node in the circuit-switched communications network sends a routing request message to a number portability database in the circuit-switched network with the second entity identifier.

4. The method in claim 3, wherein the routing request further indicates that DNS resolution is needed for the second entity identifier, and wherein the DNS server returns a resolution result.

5. The method in claim 4, wherein the result of the DNS resolution indicates whether the second entity identifier has been transferred between network operators.

6. The method in claim 5, wherein if the second entity identifier has not been transferred between network operators, the method further comprises:

processing the electronic communication in a fashion that does not take into account number portability, and

wherein if the second entity identifier has been transferred between network operators, the method further comprises;

processing the electronic communication in a different fashion that takes into account number portability.

7. The method in claim 6, wherein the different fashion processing includes providing the routing node in the circuit-switched communications network with a routing number that identifies a home network of the second entity.

8. The method in claim 1, wherein the first service is an electronic communication between first and second entities, and the second service is a resolution of a number, name, or address associated with the second entity.

9. A method for providing call services to a mobile subscriber, comprising:

receiving from the mobile subscriber at a circuit-switched node in a cellular network a call setup message to a called entity including a called entity telephone number;

sending a message to a domain name system (DNS) server in a packet-switched network requesting a resolution of the called entity telephone number;

receiving a resolution result from the DNS server for the called entity telephone number; and

routing the mobile subscriber call using the resolution result.

10. The method in claim 9, wherein the circuit-switched node queries a number portability database in the circuit-switched network using the called entity telephone number and an indication that DNS resolution is needed for the called entity telephone number.

11. The method in claim 10, wherein the number portability database generates an ENUM query to the DNS server including the called entity telephone number, and the DNS server returns an NAPTR record including a universal resource locator corresponding to the called entity telephone number.

12. The method in claim 11, wherein the NAPTR record varies depending on whether the called entity telephone number has been transferred between network operators.

13. The method in claim 12, wherein if the called entity telephone number has not been transferred between network operators, the method further comprises:

processing the call setup message in a first fashion that does not take into account number portability, and

wherein if the called entity telephone number has been transferred between network operators, the method further comprises;

processing the call setup message in a second fashion that takes into account number portability.

14. The method in claim 13, wherein the second fashion includes informing the circuit-switched node of a home network of the called party.

15. The method in claim 14, wherein the first fashion includes routing the call setup message to a home location register (HLR) for the called entity, the HLR requests a routing number from a visiting location register (VLR) currently serving the called party, and provides the routing number returned by the VLR to the circuit-switched node.

16. The method in claim 9, wherein entities in the circuit-switched network employ an SS7 signaling protocol.

17. The method in claim 16, wherein the circuit-switched node is gateway mobile switching center (GMSC) which queries the number portability database using a mobile application part (MAP) protocol and a specific translation type (TT) requesting DNS resolution.

18. The method in claim 16, wherein the circuit-switched node is gateway mobile switching center (GMSC) which queries the number portability database using intelligent network application part (INAP) protocol and a specific service by requesting DNS resolution.

19. The method in claim 9, wherein the called entity has a corresponding Mobile Subscriber Integrated Services Digital network Number (MSISDN) and an International Mobile Subscriber Identity (IMSI), the method further comprising:

administering in the DNS a relationship between the mobile subscriber'"'"'s MSISDN and IMSI.

20. The method in claim 19, wherein the called entity has a corresponding Mobile Subscriber Integrated Services Digital network Number (MSISDN) and an International Mobile Subscriber Identity (IMSI), further comprising:

changing the MSISDN for the called entity to the IMSI for the called entity, and using the called entity IMSI to route the call to the called entity.

21. A method for providing a call service where a called entity has a corresponding Mobile Subscriber Integrated Services Digital network Number (MSISDN) and an International Mobile Subscriber Identity (IMSI), comprising:

administering in a domain naming system (DNS) a relationship between the mobile subscriber'"'"'s MSISDN and IMSI.

22. The method in claim 21, further comprising:

receiving a call setup message to the called entity including the called entity'"'"'s MSISDN;

sending a message to a DNS server requesting a resolution of the called entity'"'"'s MSISDN;

receiving from the DNS server the IMSI for the called entity telephone number; and

routing the call using the IMSI.

23. The method in claim 22, further comprising:

administering in the DNS a relationship between the called entity'"'"'s MSISDN and a mobile global title (MGT) associated with the called entity.

24. The method in claim 23, further comprising:

receiving a call setup message to the called entity including the called entity'"'"'s MSISDN;

sending a message to a domain name system (DNS) server requesting a resolution of the called entity MSISDN;

receiving from the DNS server the MGT for the called entity telephone number; and

routing the call using the MGT.

25. A node in a circuit-switched communications network comprising:

a circuit-switched service interface for receiving a request from a first entity in the circuit-switched communications network involving a second entity associated with a second entity identifier;

a controller for analyzing the request and deterring that the second entity identifier should be processed in a domain name system (DNS); and

a DNS service interface for generating and sending a message to a DNS server in a packet-switched network requesting DNS processing of the second entity identifier,

wherein the controller is configured to receive a DNS response via the DNS service interface and provide the DNS response to the first entity.

26. The node in claim 25, wherein the DNS processing includes a resolution of the second entity identifier.

27. The node in claim 25, wherein the circuit-switched communications network provides a number portability service and the node is a number portability node.

28. The node in claim 27, wherein the DNS response indicates whether the second entity identifier has been transferred between network operators.

29. The node in claim 28, wherein if the second entity identifier has been transferred between network operators, the controller is configured to provide a routing node in the circuit-switched communications network with a routing number that identifies a home network of the second entity.

30. The node in claim 25, wherein the DNS processing includes a resolution of a number, name, or address of the second entity identifier.

38. The number portability node in claim 29, wherein the circuit-switched node and the number portability node employ an SS7 signaling protocol.

39. The number portability node in claim 29, wherein the circuit-switched node is gateway mobile switching center (GMSC) which queries the number portability database using mobile application part (MAP) protocol and a specific translation type (TT) requesting DNS resolution.

40. The number portability node in claim 29, wherein the circuit-switched node is gateway mobile switching center (GMSC) which queries the number portability database using intelligent network application part (INAP) protocol and a specific service by requesting DNS resolution.

41. The number portability node in claim 29, wherein the called entity has a corresponding Mobile Subscriber Integrated Services Digital network Number (MSISDN) and an International Mobile Subscriber Identity (IMSI), the electronic processing circuitry being configured to administer in the DNS a relationship between the mobile subscriber'"'"'s MSISDN and IMSI.

42. The number portability node in claim 41, wherein the electronic processing circuitry is configured to change the MSISDN for the called entity to the IMSI for the called entity using so that the IMSI may be used to route the call to the called entity.

31. A number portability node in a circuit-switched communications network comprising:

a number portability database; and

electronic processing circuitry coupled to the number portability database and configured to perform the following tasks;

receive from a circuit-switched routing node a request including a called entity telephone number associated with a call setup message to the called entity,

send a message to a domain name system (DNS) server in a packet-switched communications network requesting a resolution of the called entity telephone number,

receive a resolution result from the DNS server for the called entity telephone number; and

provide the resolution result to the routing node for use in routing the call.

32. The number portability node in claim 31, wherein the request is a number portability database query indicating that DNS resolution is needed for the called entity telephone number.

33. The number portability node in claim 32, wherein the electronic data processing circuitry is configured to generate an ENUM query to the DNS server including the called entity telephone number and to receive from the DNS server an NAPTR record including a universal resource locator corresponding to the called entity telephone number.

34. The number portability node in claim 32, wherein the contents of the NAPTR record varies depending on whether the called entity telephone number has been transferred between network operators.

35. The number portability node in claim 34, wherein if the called entity telephone number has been transferred between network operators, the electronic data processing circuitry is configured to process the call setup message to take into account number portability.

36. The number portability node in claim 35, wherein the electronic data processing circuitry is configured to inform the circuit-switched node of a home network identifier of the called party.

37. The number portability node in claim 36, wherein if the called entity telephone number has been transferred between network operators, the electronic data processing circuitry is configured to route the call setup message to a home location register (HLR) for the called entity so that the HLR may obtain a routing number from a visiting location register (VLR) currently serving the called party and provide the routing number to the circuit-switched node.

43. A computer readable software product comprising:

a computer usable medium having computer readable code embodied therein including;

code to receive an E.164 type number in a signaling system number 7 (SS7) message;

code to generate and send to a domain naming system (DNS) server a DNS resolution request for the E.164 type number; and

code to return a resolution response that provides information regarding whether the E.164 number is a ported number.

44. The computer-readable product according to claim 43, wherein the DNS request is an ENUM query and the resolution response includes an NAPTR record associated with the E.164 number.

45. The computer-readable product according to claim 43, wherein the information is a prefix needed to route the E.164 number.

46. The computer-readable product according to claim 43, wherein the SS7 message is a send routing information (SRI) message which includes a DNS resolution request in a translation type (TT) field.

47. The computer-readable product according to claim 43, wherein the SS7 message is an (IDP) message which includes a DNS resolution request in a service key.