Method and system for delivering short message service (SMS) messages using the session initiation protocol (SIP)

• US 9,888,368 B1
• Filed: 04/06/2017
• Issued: 02/06/2018
• Est. Priority Date: 09/24/2007
• Status: Active Grant

• Current Assignee: Sprint Spectrum LP (Deutsche Telekom AG)
• Original Assignee: Sprint Spectrum LP (Deutsche Telekom AG)
• Inventors: Bertz, Lyle T., Routt, William J., Guirguis, Ihab A., Lewis, Ronald E., Melus, Christopher R.
• Primary Examiner(s): Appiah, Charles
• Assistant Examiner(s): Holliday, Jaime
• Application Number:
  US15/481,016
• Time in Patent Office: 306 Days
• Field of Search: 4554221, 4554351, 4554321, 455445-560
• CPC Class Codes: H04L 51/066 Format adaptation, e.g. format conversion or compression
• CPC Class Codes: H04L 51/58 Message adaptation for wireless communication
• CPC Class Codes: H04L 61/4511 using domain name system [DNS]
• 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/4588 containing mobile subscriber information, e.g. home subscriber server [HSS]
• CPC Class Codes: H04L 65/1016 IP multimedia subsystem [IMS]
• CPC Class Codes: H04L 65/1033 Signalling gateways
• CPC Class Codes: H04L 65/1104 Session initiation protocol [SIP]
• CPC Class Codes: H04M 1/2535 adapted for voice communication over an Internet Protocol [IP] network Voice over Internet Protocol (VoIP) network equipment and services H04M7/006; implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP] H04L69/16
• CPC Class Codes: H04M 1/7243 with interactive means for internal management of messages
• CPC Class Codes: H04M 15/8228 Session based
• CPC Class Codes: H04M 3/42068 where the identifier is used to access a profile
• CPC Class Codes: H04M 7/0045 where the text-based messaging service is an instant messaging service
• CPC Class Codes: H04W 4/14 Short messaging services, e.g. short message services [SMS] or unstructured supplementary service data [USSD]
• CPC Class Codes: H04W 8/26 Network addressing or numbering for mobility support

Abstract

An Internet Protocol Multimedia Subsystem (IMS) network uses the Session Initiation Protocol (SIP) to provide communication services to mobile nodes. A short message service gateway (SMS-GW) in the IMS network receives a request to deliver a message to a mobile node. The SMS-GW determines whether the mobile node is IMS registered. If the mobile node is IMS registered, the SMS-GW may transmit a SIP MESSAGE request to a call session control function (CSCF) serving the mobile node in order to deliver the message to the mobile node. If the mobile node is SIP-capable but is not IMS registered, the SMS-GW may instead transmit a SIP MESSAGE request to the mobile node'"'"'s IP address. To obtain the mobile node'"'"'s IP address, the SMS-GW may query a domain name server (DNS) that stores associations between hostnames and IP addresses of mobile nodes.

Claims

1. A method comprising:

a messaging gateway receiving a request to deliver a message to a mobile node, said request including an identifier of said mobile node;

said messaging gateway determining that said mobile node is Session Initiation Protocol (SIP) capable;

said messaging gateway determining a hostname of said mobile node based on said identifier of said mobile node and a domain name of a wireless service provider of said mobile node;

said messaging gateway sending a query to a domain name server (DNS), said query including said hostname;

said messaging gateway receiving a response from said DNS, said response including a network address of said mobile node; and

said messaging gateway using SIP to transmit said message to said network address.

2. The method of claim 1, wherein said messaging gateway is a short message service gateway (SMS-GW).

3. The method of claim 1, wherein said request is a short message service delivery point-to-point (SMDPP) request.

4. The method of claim 1, wherein said identifier of said mobile node is a mobile directory number (MDN) of said mobile node.

5. The method of claim 4, wherein said hostname of said mobile node is determined by concatenating said MDN of said mobile node with said domain name of said wireless service provider of said mobile node.

6. The method of claim 1, wherein said network address is an Internet Protocol (IP) address.

7. The method of claim 1, further comprising:

registering an association between said hostname and said network address in said DNS.

8. The method of claim 1, wherein said messaging gateway using SIP to transmit said message to said network address comprises:

said messaging gateway transmitting a SIP MESSAGE request.

9. The method of claim 1, wherein said messaging gateway determining that said mobile node is Session Initiation Protocol (SIP) capable comprises:

said messaging gateway querying a capabilities server, wherein said capabilities server stores indications of capabilities of mobile nodes.

10. The method of claim 1, wherein said messaging gateway is in an Internet Protocol Multimedia Subsystem (IMS) network, further comprising:

said messaging gateway determining whether said mobile node is IMS registered.

11. A system comprising:

a domain name server (DNS) storing associations between hostnames and Internet Protocol (IP) addresses of mobile nodes; and

a messaging gateway configured to, in response to receiving a request to deliver a message to a mobile node, determine whether said mobile node is Session Initiation Protocol (SIP) capable, and in response to a determination that said mobile node is SIP capable;

(a) determine a hostname of said mobile node based on an identifier of said mobile node included in said request and a domain name of a wireless service provider of said mobile node;

(b) query said DNS to obtain an IP address associated with said hostname; and

(c) transmit a SIP request to said IP address, said SIP request containing said message to be delivered to said mobile node.

12. The system of claim 11, further comprising:

a capabilities server that stores indications of capabilities of mobile nodes, wherein said messaging gateway is configured to query said capabilities server to determine whether said mobile node is SIP capable.

13. The system of claim 12, wherein said identifier of said mobile node included in said request is a mobile directory number (MDN) of said mobile node.

14. The system of claim 13, wherein said hostname of said mobile node is determined by concatenating said MDN of said mobile node with said domain name of said wireless service provider of said mobile node.

15. A method comprising:

a messaging gateway receiving a request to deliver a message to a mobile node, said request including an identifier of said mobile node;

in response to said request, said messaging gateway determining whether to deliver said message using a packet-based protocol, wherein said messaging gateway determining whether to deliver said message using said packet-based protocol comprises said messaging gateway querying a capabilities server to determine whether said mobile node supports said packet-based protocol; and

in response to a determination to deliver said message using said packet-based protocol;

said messaging gateway determining a hostname of said mobile node based on said identifier of said mobile node and a domain name of a wireless service provider of said mobile node;

said messaging gateway sending a query to a domain name server (DNS), said query including said hostname;

said messaging gateway receiving a response from said DNS, said response including a network address of said mobile node; and

said messaging gateway using said packet-based protocol to transmit said message to said network address.

16. The method of claim 15, wherein said messaging gateway using said packet-based protocol to transmit said message to said network address comprises said messaging gateway transmitting a Session Initiation Protocol (SIP) request to said network address.

17. The method of claim 15, wherein said request is a short message service delivery point-to-point (SMDPP) request.

18. The method of claim 15, wherein said messaging gateway determining whether to deliver said message using said packet-based protocol further comprises:

said messaging gateway querying a preferences server to determine whether said mobile node has a preferred method of message delivery.

19. The method of claim 15, wherein said identifier of said mobile node is a mobile directory number (MDN) of said mobile node.

20. The method of claim 19, wherein said hostname of said mobile node is determined by concatenating said MDN of said mobile node with said domain name of said wireless service provider of said mobile node.