KR20130114244A - Method and apparatus for delivering application-originated text messages over a packet-switched network - Google Patents

Abstract

Systems and methods are disclosed for correlating messages used to deliver application originated (AO) text messages to a user device (UE). The text message gateway is implemented between a text messaging application and a packet-switched network using the Session Initiation Protocol (SIP). The text message gateway receives a delivery request from the text message application that includes the AO text message intended for the UE. The text message gateway identifies the correlation ID for the AO text message, inserts the correlation ID in the delivery response, and sends the delivery response to the text message application (to save for later use). The text message gateway also translates the delivery request into a SIP request that compresses the AO text message, inserts a correlation ID in the SIP request, and sends the SIP request to the UE.

Description

METHODS AND APPARATUS FOR DELIVERING APPLICATION-ORIGINATED TEXT MESSAGES OVER A PACKET-SWITCHED NETWORK}

The present invention relates to the field of communications, and in particular to a method of correlating signaling messages used to convey application-originated text messages.

Text messaging has become a popular method of many mobile (or wireless) network communications. One example of text message transmission is the Short Message Service (SMS), which is a set of communication protocols that allow the exchange of short text messages (ie, 160 characters or less) between devices. While the term "text message" traditionally refers to text only messages transmitted using SMS, it has been extended to include multimedia messages, such as images, video, voice content, and the like. Multimedia messages may be sent using the Multimedia Message Service (MMS) protocol. Often, mobile users use text message transmission more often for communication than voice calls.

While text messaging is traditionally considered two end users exchanging text messages via mobile devices, there may be automatic applications (ie, not real people) exchanging text messages with the end user. have. By way of example, an External Short Messaging Entity (ESME) is a device / server that includes an application that can send and / or receive text messages (eg, SMS). ESME connects to the network through a fixed connection using protocols such as the Short Message Peer-to-Peer (SMPP) protocol, Universal Computer Protocol (UCP), RESTful, HTTP, and Parlay. Typical examples of ESMEs are voting systems that process voting via text message, servers that send automatic marketing messages to mobile devices, and the like.

To send a text message, the application encapsulates the text message into a signaling message of that protocol. The protocol may be proprietary or may be one commonly used in the industry, such as SMPP. The text message originated by the application in this manner is referred to herein as an application-originated (AO) text message. When an AO text message is sent to a Session Initiation Protocol (SIP) -based network, such as an IP Multimedia Subsystem (IMS) or Long Term Evolution (LTE) network, the AO text message passes through a gateway. This assumes that the application does not have a SIP interface. The gateway translates the text message from the signaling protocol used by the application to a SIP request (eg, SIP MESSAGE) and sends the SIP request towards the destination (referred to as the receiving side) via the SIP-based network.

The technical specifications of 3GPP and 3rd Generation Partnership Project (3GPP2) specify how text messages are exchanged over packet-switched networks using SIP, such as 3GPP Technical Specification (TS) 24.341. As part of these specifications, when a text message is delivered to the recipient, the recipient's device initiates a new SIP transaction to report back on the success / failure of delivery of the text message. Thus, the recipient's device sends a new SIP request back to the gateway indicating successful / failed delivery of the text message.

Unfortunately, it is a problem to effectively associate multiple SIP transactions for an AO MT text message.

Embodiments described herein allow for correlation of a plurality of SIP transactions using a correlation ID. When the gateway receives the text message initiated by the application, the gateway identifies the correlation ID and sends the correlation ID to the application. The gateway also embeds a correlation ID in the SIP request used to send the text message to the recipient. The recipient's device (user device) receives the SIP request and initiates a new SIP request (new SIP transaction) to report delivery success / failure for the text message. The recipient's device embeds a correlation ID in the new SIP request according to an indication of success / failure of delivery for the text message. When the gateway receives a new SIP request, the gateway locates a correlation ID and associates the new SIP request with the original forward request and the previous SIP request based on the correlation ID. By correlating the new SIP request with the original delivery request from the application, the gateway can send a delivery response to the application that includes a correlation report for the correlation ID and text message. The application may correlate the delivery response with the delivery report of the text message with the initiation delivery request for the text message based on the correlation ID. Thus, the correlation ID advantageously allows the gateway to correlate a plurality of SIP transactions. The correlation ID also allows the application to correlate the delivery request with the delivery response so that the application knows the delivery status of the text message.

One embodiment includes a text message gateway for interworking communications between a text message application and a packet-switched network using SIP. In operation, the text message gateway receives a first delivery request from a text message application that includes an Application Originated (AO) text message intended for a user equipment (UE) served by a packet-switched network. The text message gateway identifies the correlation identifier (ID) for the AO text message, inserts the correlation ID in the delivery response, and sends the delivery response to the text message application. The text message application can then store the correlation ID for later use. The text message gateway also converts the first forwarding request into a first SIP request (eg, SIP MESSAGE) that compresses the AO text message, inserts a correlation ID into the first SIP request, and sends the first SIP request to the UE. To send.

In another embodiment, the text message gateway receives a second SIP request (eg, another SIP MESSAGE) from the UE that includes a forwarding request for the AO text message and analyzes the second SIP request to identify a correlation ID. And correlating the second SIP request with the first forwarding request and the first SIP request based on the correlation ID. The text messaging system can then insert a delivery report for the AO text message into the second delivery request, insert a correlation ID into the second delivery request, and send the second delivery request to the text messaging application. The text message application may correlate the delivery report with the first delivery request originally used to send the AO text message to the UE. Thus, the gateway can provide the delivery status of the AO text message to the text message application in an effective manner so that the application can determine whether the text message was successfully received by the recipient.

In another embodiment, the signaling protocol used by the text message application includes a Short Message Peer-to-Peer (SMPP) protocol. Accordingly, the first delivery request may include an SMPP submit_sm message, and the second delivery request may include an SMPP deliver_sm message. The text message gateway may insert a correlation ID into the receipted_message_id field of the SMPP deliver_sm message.

In another embodiment, the text message gateway may insert a correlation ID of the first SIP request into the Mobile Application Part (MAP) RP-Message Reference field, and the text message gateway with the correlation ID in the MAP RP-Message Reference field. You can insert a gateway ID for.

Another embodiment includes a method of interworking communications between a text message application and a packet-switched network using SIP. The method includes receiving a first delivery request from a text message application that includes an AO text message intended for a user equipment (UE) served by a packet-switched network. The method also includes identifying a correlation identifier (ID) for the AO text message, inserting a correlation ID in the delivery response, and sending the delivery response to the text message application. The method also includes converting the first delivery request into a first SIP request that compresses an AO text message, inserting a correlation ID in the first SIP request, and sending the first SIP request to the UE.

In another embodiment, a method includes receiving a second SIP request from a UE that includes a delivery report for an AO text message, analyzing the second SIP request to identify a correlation ID, and based on the correlation ID. Correlating the 2 SIP request with the first forwarding request and the first SIP request.

In another embodiment, the method includes inserting a delivery report into the second delivery request, inserting a correlation ID into the second delivery request, and sending a second delivery request to the text messaging application so that the text message application sends the AO text message. And further comprising the sending step, which can correlate the delivery report with the first delivery request originally used to send.

In another embodiment, the signaling protocol used by the text message application includes the SMPP protocol. Accordingly, the first delivery request may include an SMPP submit_sm message, and the second delivery request may include an SMPP deliver_sm message. Inserting the correlation ID into the second delivery request includes inserting the correlation ID into the receipted_message_id field of the SMPP deliver_sm message.

In another embodiment, the method includes inserting the correlation ID of the first SIP request into the MAP RP-Message Reference field and inserting the gateway ID for the text message gateway along with the correlation ID into the MAP RP-Message Reference field. It includes.

Other example embodiments can be described below.

Some embodiments of the invention are now described by way of example only and with reference to the accompanying drawings. The same reference numerals refer to the same type or the same element of the elements of all the drawings.

1 illustrates a communication system of an exemplary embodiment.
2 is a flowchart illustrating a method of processing an AO text message in an exemplary embodiment.
3 is a flowchart illustrating a method of processing an AO text message of a user equipment (UE) in an exemplary embodiment.
4 is a flow diagram illustrating additional steps of the method of FIG. 2 for processing an AO text message of an exemplary embodiment.
5 illustrates a communication system of another exemplary embodiment.
6 is a message diagram illustrating successful delivery of an SMS message in an exemplary embodiment.

The drawings and the following description describe specific example embodiments of the invention. Thus, it will be understood by those skilled in the art that although not explicitly described or shown herein, various ways of incorporating the principles of the invention and falling within the scope of the invention may be devised. In addition, certain examples described herein are intended for the purpose of understanding the principles of the invention and are intended to be interpreted without limitation on these specifically mentioned examples and conditions. As a result, the invention is not limited to the specific embodiments or examples described below, but to the claims and their equivalents.

1 illustrates a communication system 100 of an exemplary embodiment.

Communication system 100 includes one or more external message centers 110 connected to a packet-switched network 120. System 100 may send text messages from external message center 110 to user equipment (UE) 140 served by packet-switched network 120. Text messages sent from the external message center 110 via the packet-switched network 120 to the UE 140 are referred to as Mobile Terminated (MT) text messages.

External message center 110 includes any system, server or device capable of generating text messages and capable of sending text messages to packet-switched network 120 for delivery to UE 140. One example of an external message center 110 is ESME. Typical examples of ESMEs are systems for sending automated marketing messages to mobile users, voting systems for processing text message polls, and the like. In this embodiment the external message center 110 includes a text message application 112 that generates text messages and initiates the transmission of text messages for the packet-switched network 120.

Packet-switched network 120 includes any network that exchanges communications using packets, such as IP packets. Packet-switched network 120 may comprise an IMS network, an LTE network or any other IP-based network. Packet-switched network 120 may include various elements, such as network element 122, for providing voice and / or data services to UE 140. Some examples of network element 122 include a Serving-Call Session Control Function (S-CSCF), a PDN Gateway (P-GW), and the like.

Communication system 100 also includes a text message gateway 130. Text message gateway 130 includes any system, server or device that interworks communications between external message center 110 and network element 122 of UE 140 and / or packet-switched network 120. do. Application 112 of external message center 110 may not support the protocols used for message delivery of packet-switched network 120, such as SIP. Thus, the text message gateway 130 may have other protocols (eg, APIs) for which the application 112 and various other applications are directed towards the packet-switched network 120, such as Parlay, RESTful, LDAP, XML, and SMPP. Allow sending text messages). For example, if the application 112 sends a text message intended for the UE 140, the application 112 may use a RESTful API to send the text message. Text message gateway 130 may normalize the RESTful protocol message and convert it to a SIP request. Text message gateway 130 may then send a SIP request to UE 140 via packet-switched network 120 to deliver the original text message. Some examples of text message gateway 130 include an IP-SM-GW of an IMS network or an LTE SMS gateway of an LTE network.

The text message gateway 130 may be part of a packet-switched network 120 (shown in FIG. 1) or may be part of a packet-switched network to interwork messages sent to the packet-switched network 120. 120). In addition, the communication system 100 may have a plurality of text message gateways 130 or the like to handle higher traffic loads for geo-redundancy. Accordingly, the text message gateway 130 as shown in FIG. 1 may mean a single gateway or a cluster of gateways (eg, gateway A, gateway B, gateway C, etc.).

The text message gateway 130 includes a network interface 132 and a control system 134. Network interface 132 includes any device or component that communicates with external message center 110 and other message centers through various protocols. The network interface 132 may also communicate with one or more elements 122 of the packet-switched network 120 via a protocol used within the packet-switched network 120, such as SIP. The control system 134 includes any device or component that correlates messages between the external message center 110 and the UE 140.

In the following embodiments, when the application 112 creates a text message intended for the UE 140, the application 112 sends a text message to the gateway 130 for interworking. This text message is referred to as an AO text message. Gateway 130 then sends a text message to UE 140 of the SIP request. As background, there is a set of instructions defined in SIP, referred to as SIP requests or “methods”. One such SIP request is a SIP MESSAGE used to send instant messages, text messages, and the like. SIP also defines a set of instructions referred to as SIP responses. SIP responses are used to respond to specific SIP requests. Some common SIP responses are 1xx, 2xx, 3xx, 4xx, 5xx and 6xx.

As a result, when a SIP request (which compresses a text message) is sent to the device, the receiving device does not provide a delivery report (text message transmission reply or error) of the text message of the SIP response. The receiving device provides a SIP response (reply) that the SIP request itself has been received, such as a SIP 200 OK. However, this SIP response does not indicate whether the text message in the SIP request was successfully delivered to its recipient (s); Only indicates the delivery status of the SIP request. There may be various reasons why a SIP request is successfully received, but beyond the scope of this discussion, there are text message inside and errors in the SIP request. Per the 3GPP specification, the receiving device initiates a new SIP transaction to provide a delivery report of a text message by sending a separate SIP request reporting the delivery status.

Embodiments described herein allow for correlation of a plurality of SIP transactions of gateway 130 when processing an AO text message. Correlation is possible using the correlation ID, which is also described in Figures 2-4.

2 is a flow diagram illustrating a method 200 of processing an AO text message in an example embodiment. Although the steps of the method 200 will be described with reference to the text message gateway 130 of FIG. 1, those skilled in the art will understand that the method 200 can be implemented in other networks and systems. The steps of the flowcharts described herein may not include all and may include other steps not shown. The steps may also be executed in an alternative order.

At step 202, network interface 132 receives an AO text message from application 112 of external message center 110. Text messages are probably compressed into forwarding requests for protocols other than SIP, such as Parlay, RESTful, LDAP, XML, or SMPP. One example of a SMPP delivery request is a submit_sm request. The application 112 may also request / request a delivery reply or receipt of a text message, as described below.

At step 204, control system 134 identifies a correlation identifier (ID) for the text message. The correlation ID includes any string, integer, or value defined for the text message to correlate the messages involved in the delivery of the text message. The control system 134 may generate a new and unique ID in response to receiving the text message. The control system 134 may alternatively reuse the message ID that was received with the text message from the application 112 in the delivery request.

In step 206, the control system 134 generates a delivery response of the appropriate protocol and inserts a correlation ID in the delivery response. For example, if the delivery request is an SMPP submit_sm request, the control system 134 may generate a submit_resp response as the delivery response. In step 208, the network interface 132 sends a delivery response to the application 112 of the external message center 110. Application 112 may then analyze the delivery response to identify the correlation ID and store the correlation ID for later use.

In step 210, the control system 134 converts or interworks the delivery request to SIP so that the text message is compressed into a SIP request or embedded in the SIP request. The SIP request may include SIP MESSAGE or another type of SIP request for sending text messages (eg, SMS messages). The control system 134 may embed a text message in the MAP RP-DATA field of the SIP request. At step 212, control system 134 also inserts or embeds a correlation ID in the SIP request. For example, the control system 134 may insert a correlation ID in the MAP RP-Message Reference field of the SIP request. The control system 134 may also identify the gateway ID for the gateway 130, and may insert or embed the gateway ID in the SIP request along with the correlation ID. The gateway ID includes any string, integer, or value that uniquely refers to a text message gateway, such as gateway 130. Packet-switched network 120 may have a plurality of gateways used to translate or interwork text messages from application 112 to UE 140 for redundancy and load balancing. have. The gateway ID will be used to correlate SIP requests when SIP requests arrive at other gateways.

In step 214, the network interface 132 sends a SIP request to the network element 122 for delivery to the UE 140. Upon receiving the SIP request, network element 122 attempts to forward the SIP request to UE 140.

3 is a flowchart illustrating a method 300 of processing an AO text message of a UE 140 in an exemplary embodiment. The steps of the method 300 will be described with reference to the system 100 of FIG. 1, but those skilled in the art will understand that the method 300 can be executed in other networks, systems or devices.

At step 302, UE 140 receives a SIP request from network element 122, which compresses the text message. The UE 140 sends a SIP 200 OK to the gateway 130 (via the network element 122) returning a successful receipt of the SIP request. In step 304, the UE 140 determines the processing status for the compressed text message to generate a delivery report (either in reply or error report format) of the text message. The delivery report of the text message is separated from the status of delivering the SIP request carrying the text message (which is done with a 200 OK or SIP 3xx, 4xx, 5xx response). The delivery report contains any information indicating the success or failure of the processing of the text message (such as RP-DATA). The process used to determine the delivery report of the text message is outside the scope of this application. However, in one example, the UE 140 can analyze the data for the text message to determine whether to handle errors, format the errors or any other type of errors. If one or more errors are detected in parsing the text message, the UE 140 may determine that delivery of the text message has failed. If no errors are detected in parsing the text message, the UE 140 can determine that the delivery of the text message was successful.

In step 306, the UE 140 analyzes the original SIP request to identify the correlation ID. The UE 140 may analyze the MAP RP-Message Reference field to find the correlation ID. The UE 140 then generates a new SIP request for reporting the delivery status of the text message and inserts the correlation ID into the new SIP request (see steps 308 and 310). The new SIP request may again include another type of SIP request or SIP MESSAGE sending text messages (eg, SMS messages). To insert the correlation ID into the new SIP request, the UE 140 may copy the MAP RP-Message Reference field of the original SIP request into the MAP RP-Message Reference field of the new SIP request. In step 312, the UE 140 inserts a delivery message of the text message in the new SIP request. For example, the UE 140 may set the MAP-RP-Message Type for RP-ACK or RP-ERROR of a new SIP request. In step 314, the UE 140 sends a new SIP request to the gateway 130 via the network element 122.

4 is a flowchart illustrating additional steps of a method 200 for processing an AO text message of an exemplary embodiment. In step 216, the network interface 132 (see FIG. 1) of the gateway 130 receives the new SIP request sent by the UE 140. In response to receiving the new SIP request, the gateway 130 sends a SIP 200 OK (via network element 122) to the UE 140 replying to the successful receipt of the new SIP request. At step 218, control system 134 analyzes the new SIP request to identify the correlation ID. The control system 134 may analyze the MAP RP-Message Reference field to find the correlation ID. The control system 134 then correlates the original SIP request (which sent the text message) with the new SIP request (which sent the delivery report for the text message) based on the correlation ID in step 220.

The control system 134 can also correlate the two SIP requests with the original forwarding request from the application 112. By correlating the SIP requests with the original delivery request from the application 112 based on the correlation ID, the control system 134 can provide the application 112 with a delivery report for the text message. In so doing, control system 134 inserts the delivery report for the text message into the new delivery request in step 222. One example of a new delivery request in SMPP is the deliver_sm request. The control system 134 also inserts a correlation ID in the new forwarding request at step 224. The network interface 132 then sends a new delivery request to the application 112 in step 226.

Thus, application 112 may correlate the original delivery request for the text message with the new delivery request based on the correlation ID. Thus, the application 112 may correlate the delivery report from the new delivery request with the AO text message from the original delivery request, and determine whether the text message was successfully delivered to its recipient (s). will be. The correlation ID advantageously allows the gateway 130 to correlate a plurality of SIP transactions in reporting the delivery status of the text message. The correlation ID is also forwarded back to the application 112 because the gateway 130 is surrounded by a common correlation ID that is used to send the delivery report and text message between the application 112 and the UE 140. Allow to provide a report. As a result, delivery reports / receipts can be effectively provided for AO MT text messages.

Yes

5 illustrates a communication system 500 of another example embodiment. The communication system 500 includes a plurality of wireless communication networks, shown as CDMA network 510, IMS network 520 and LTE network 530 in this embodiment. The embodiments described below illustrate the delivery of SMS messages to a UE (eg, mobile device) 550 using SIP messages.

The CDMA network 510 includes a Home Location Register (HLR) 512, a Mobile Switching Center (MSC) 514, and a Packet Data Network Gateway (PDN-GW) 516. HLR 512 is a central subscriber database that stores subscription details and other details of UEs authorized to use CDMA network 510 (eg, subscriber profiles). The MSC 514 is the serving node for the UEs and is responsible for handling voice calls, SMS and other services in the CDMA network 510. PDN-GW 516 includes any node or element in CDMA network 510 that interworks signaling between CDMA network 510 and a packet-switched network, such as IMS network 520. CDMA network 510 may include other network elements that are not shown for brevity, such as base stations, wireless network controllers, and the like.

The IMS network 520 includes a proxy-call session control function (P-CSCF) 522, a serving-call session control function (S-CSCF) 524, a home subscriber server (HSS) 526, and a packet gateway (P). -GW) 528. P-CSCF 522 is an entry point for the IMS domain and is served as an outbound proxy server for IMS devices. S-CSCF 524 is the central node of the signaling side, and performs session control for IMS devices initiating sessions via IMS network 520. S-CSCF 524 communicates with IMS devices via one or more access networks not shown in FIG. 5. HSS 526 is a subscriber server that stores subscription-related information (eg, subscriber profiles), performs authentication and approval of end users, provides information about the location of the subscriber, and the like. P-GW 528 includes any node or element of IMS network 520 that exchanges packets and external networks.

Elements of the LTE network 530 are not shown in this embodiment for clarity.

The communication system 500 may also include one or more SMS Centers (542) and an LTE gateway, an IP Short Message Gateway (IP-SM-GW) or some other gateway that handles SMS over IP. Short Message Gateways (SM-GW) 544-545. SMSC 542 includes any node for a circuit-transformed network that forwards SMS messages using store-and-transmit processing. SM-GWs 544-545 include any node that interworks signaling between a SIP-based network and a network or device using another signaling protocol. For example, if a network or device uses the SMPP protocol to exchange SMS messages, the SM-GWs 544-545 interwork the SMPP protocol messages over SIP and vice versa. Communication system 500 also includes External Short Messaging Entities (ESME) 546 and 548. The ESME is an external application coupled to the SMSC 542 or SM-GW 544-545 to engage in the sending and / or receiving of SMS messages.

Assume this embodiment where the ESME 548 generates an SMS message intended for the UE 550. The following example shows how the delivery status is provided to the SIP response.

6 is a message diagram illustrating successful delivery of an SMS message in an exemplary embodiment. For reference, the text message gateway 130 of FIG. 1 will be implemented in the SM-GWs 544 and 545 of this embodiment. After ESME 548 generates an SMS message for UE 550, ESME 548 formats the SMPP protocol submit_sm request and compresses the SMS message of the submit_sm request. The SMPP protocol submit_sm request represents a transfer request from ESME 548. One assumption at this point is that ESME 548 is available for the SMPP protocol. If not, an SMPP gateway may be implemented between ESME 548 and SM-GWs 544 and 545. Accordingly, the ESME 548 transmits a submit_sm request to the SM-GW 544.

In response to the submit_sm request, the SM-GW 544 identifies a correlation ID for the SMS message. SM-GW 544 may generate a new, unique ID in response to receiving the submit_sm request. Alternatively, SM-GW 544 may reuse the message ID that was received in the submit_sm request from ESME 548. SM-GW 544 then generates a submit_resp response and inserts the correlation ID into the submit_resp response. SM-GW 544 then sends a submit_resp response to ESME 548 with the correlation ID (CORR ID). ESME 548 analyzes the submit_resp response and stores the correlation ID for later use.

Next, the SM-GW 544 queries the HSS 526 for the registration status of the UE 550 using Diameter User Data Request (UDR). The HSS 526 determines whether the UE 550 is registered and responds to the SM-GW 544 with a Diameter User Data Answer (UDA) indicating that the UE 550 is registered. SM-GW 544 then configures SIP MESSAGE to compress the SMS message. The SMS message is embedded in the RP-DATA (eg RP-USER DATA field) of the SIP MESSAGE. SM-GW 544 also embeds the Gateway ID and Correlation ID for SM-GW 544 in SIP MESSAGE. For example, the SM-GW 544 may embed the gateway ID and the correlation ID as a combination string of RP-DATA (eg, RP-Message Reference field) compressed in the SIP MESSAGE. The SIP MESSAGE header may consist of the following:

MESSAGE tel: +19305020103 SIP / 2.0

Via: SIP / 2.0 / UDP 135.1.62.120:5060;bran=z9hG4b

To: tel: +19305020103

From: tel: +19305020106; tag = l (ESME Address-long code)

Call-ID: 689e5af4451cO170 @ livemas1

Max-Forwards: 70

CSeq: 1 MESSAGE

Route: LTE GW SIP URI

P-Charging-Vector = icid-value = "PCSF: 192.161.1.xxx-xxxxxxxx"

Content-Type: application / vnd.3gpp.sms

Content-Length: xx ( Length of Relay Layer Message )

<< Compressed RP - DATA ( SMS -Forwarding) >>

RP-DATA is in the following format for SIP MESSAGE:

SM-GW 544 then sends a SIP MESSAGE to S-CSCF 524 of IMS network 520. S-CSCF 524 in turn transmits SIP MESSAGE to UE 550, and UE 550 successfully receives SIP MESSAGE. Accordingly, the UE 550 sends a SIP 200 OK to the S-CSCF 524 which returns a successful receipt of the SIP MESSAGE. S-CSCF 524 sends a SIP 200 OK to SM-GW 544.

The UE 550 also attempts to parse the SMS message (RP-DATA) of the SIP MESSAGE to determine whether the SMS message was successfully delivered. Assume this embodiment that the SMS was successfully delivered. The UE 550 consequently determines that the delivery of the SMS message was successful and informs the SM-GW 544 of the following successful delivery. The UE 550 generates a new SIP MESSAGE for the new SIP transaction and embeds the correlation ID and the gateway ID in the RP-ACK (RP-Message Reference field) of the SIP MESSAGE. In essence, the UE 550 copies the RP-Message Reference field from the received SIP MESSAGE to the new SIP MESSAGE. UE 550 also inserts the delivery report into the new SIP MESSAGE. UE 550 then sends a new SIP MESSAGE to S-CSCF 524. The new SIP MESSAGE may be as follows:

MESSAGE tel: +19305020103 SIP / 2.0

Via: SIP / 2.0 / UDP 135.1.30.70:5080;bran=z9hG4bK287482662-1402101

Max-Forwards: 70

From: <sip: +19305020106@verizon.net; user = phone; lr>; tag = pctUA_287482662

To: LTE GW SIP URI

Call-ID: 287482662-1402079

CSeq: 1 MESSAGE

Route: LTE GW SIP URI

P- Asserted-Identity: <sip: +19305020106@somedomain.com>

P- Asserted-Identity: <tel: +19305020106>

Content-Type: application / vnd.3gpp.sms

Content-Length: xx ( Length of Relay Layer Message )

<< Compressed RP - ACK ( SMS -Forwarding-Report Message) >>

RP-DATA is in the following format for new SIP MESSAGEs:

The S-CSCF 524 resolves the VIP address from the new SIP MESSAGE and sends the SIP MESSAGE to the SM-GW 545, where the SM-GW 545 successfully receives the new SIP MESSAGE. do. Accordingly, the SM-GW 545 sends a SIP 200 OK to the S-CSCF 524 which returns a successful receipt of the new SIP MESSAGE. S-CSCF 524 sends a SIP 200 OK to UE 550.

After receiving the new SIP MESSAGE, the SM-GW 545 analyzes the RP-ACK from the RP-Message Reference field and the SIP MESSAGE to identify the correlation ID. SM-GW 545 finds that the previous RP-DATA message was sent by SM-GW 544 based on the gateway ID for SM-GW 544. Thus, the SM-GW 545 correlates the new SIP request for the original SIP request with the original SMPP request from the ESME 548. Since all payload data is completed for the SMS message, the SM-GW 545 sends an SMPP deliver_sm request to the ESME 548 with correlation ID and delivery report. SM-GW 545 sets the receipted_message_id of the SMPP deliver_sm request for the correlation ID. SM-GW 545 also notifies SM-GW 544 of transactions. The SM-GW 544 stores transaction data of a database.

ESME 548 receives a deliver_sm request from SM-GW 545. This request is a separate SMPP transaction just as the two SIP MESSAGEs were other SIP transactions. However, the ESME 548 may correlate the submit_sm request based on the correlation ID for the deliver_sm request. Accordingly, the SM-GW 545 may identify a delivery report for the SMS message based on the status information inserted in the deliver_sm request. Thus, the ESME 548 can correlate the delivery status information with the SMS message that was advantageously sent. Although SM-GW 544 translated the SMS message from SMPP to SIP, ESME 548 could receive delivery status information for the SMS message.

Any of the various elements described herein or shown in the figures may be implemented as hardware, software, firmware or some combination thereof. For example, an element may be implemented as dedicated hardware. Dedicated hardware elements may be referred to as "processors", "controllers" or some similar term. When provided by a processor, the functions may be provided by a single dedicated processor, by a single shared processor, or by a plurality of individual processors, some of which may be shared. In addition, the explicit use of the term "processor" or "controller" should not be interpreted to refer solely to hardware capable of executing software, and, without limitation, digital signal processor (DSP) hardware, network processors, application specific integrated circuits (ASICs). Or other circuitry, field programmable gate array (FPGA), read only memory (ROM) for storing software, random access memory (RAM), nonvolatile memory, logic, or some other physical hardware component or module. It may include.

In addition, an element may be implemented as instructions executable by a processor or computer to carry out the functions of the element. Some examples of instructions are software, program code, and firmware. Instructions are optional when executed by a processor that directs the processor to perform the functions of the element. The instructions may be stored on storage devices readable by the processor. Some examples of storage devices are magnetic storage media such as digital or solid-state memories, magnetic disks and magnetic tapes, hard drives or optionally readable digital data storage media.

Although specific embodiments are described herein, the scope of the invention is not limited to these specific embodiments. The scope of the invention is defined by the following claims and the equivalents of any invention.

Claims (10)

A text message gateway configured to interwork communications between a packet-switched network and a text messaging application using Session Initiation Protocol (SIP),
The text message gateway also receives a first forwarding request from the text message application including an Application Originated (AO) text message intended for user equipment (UE) served by the packet-switched network. And identify a correlation identifier (ID) for the AO text message, insert the correlation ID in a delivery response, and send the delivery response to the text message application,
The text message gateway also converts the first delivery request into a first SIP request that encapsulates the AO text message, inserts the correlation ID into the first SIP request, and inserts the first SIP request. And transmit the message to the UE. The method of claim 1,
The text message gateway also receives a second SIP request from the UE that includes a delivery report for the AO text message, parses the second SIP request to identify the correlation ID, and And correlate at least one of the first SIP request and the first forwarding request with the second SIP request based on a correlation ID. 3. The method of claim 2,
The text message system is further configured to insert the delivery report in a second delivery request, insert the correlation ID in the second delivery request, and send the second delivery request to the text message application. Enable a messaging application to correlate the delivery report with the first delivery request originally used to send the AO text message. The method of claim 3, wherein
A signaling protocol used by the text message application includes a Short Message Peer-to-Peer (SMPP) protocol;
The first delivery request includes an SMPP submit_sm message;
The second delivery request includes an SMPP deliver_sm message;
The text message gateway is further configured to insert the correlation ID into a receipted_message_id field of the SMPP deliver_sm message. The method of claim 1,
The text message gateway is further configured to insert the correlation ID of the first SIP request into a Mobile Application Part (MAP) RP-Message Reference field;
The text message gateway is further configured to insert a gateway ID for the text message gateway along with the correlation ID in the MAP RP-Message Reference field. Receiving a first delivery request from a text message application comprising an Application Originated (AO) text message intended for user equipment (UE) served by a packet-switched network;
Identifying a correlation identifier (ID) for the AO text message;
Inserting the correlation ID in a transfer response;
Sending the delivery response to the text message application;
Converting the first forwarding request into a first SIP request compressing the AO text message;
Inserting the correlation ID in the first SIP request;
Sending the first SIP request to the UE. The method according to claim 6,
Receiving a second SIP request from the UE, the second SIP request comprising a delivery report for the AO text message;
Analyzing the second SIP request to identify the correlation ID;
Correlating the first forwarding request and the first SIP request with the second SIP request based on the correlation ID. The method of claim 7, wherein
Inserting the delivery report in the second delivery request;
Inserting the correlation ID in the second delivery request;
Sending the second delivery request to the text message application to enable the text message application to correlate the delivery report with the first delivery request originally used to send the AO text message. . The method of claim 8,
The signaling protocol used by the text message application includes an SMPP protocol;
The first delivery request includes an SMPP submit_sm message;
The second delivery request includes an SMPP deliver_sm message;
Inserting the correlation ID in the second delivery request comprises inserting the correlation ID in a receipted_message_id field of the SMPP deliver_sm message. The method according to claim 6,
Inserting the correlation ID of the first SIP request into a MAP RP-Message Reference field;
And inserting a gateway ID for a text message gateway along with the correlation ID in the MAP RP-Message Reference field.

Images