KR101467970B1 - 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 convey Application Originated (AO) text messages to a user equipment (UE). A text messaging gateway is implemented between a text messaging application and a packet-switched network using Session Initiation Protocol (SIP). The text messaging gateway receives a delivery request from the text messaging application containing an AO text message intended for the UE. The text messaging gateway identifies the correlation ID for the AO text message, inserts the correlation ID in the delivery response, and forwards the delivery response to the text messaging application (to store for later use). The text messaging gateway also transforms the forwarding request into a SIP request compressing the AO text message, inserts the correlation ID into the SIP request, and sends a SIP request to the UE.

Description

METHOD AND APPARATUS FOR DELIVERING APPLICATION-ORIGINATED TEXT MESSAGES OVER A PACKET-SWITCHED NETWORK BACKGROUND OF THE INVENTION 1. Field of the Invention [0001]

The present invention relates to a method of correlating signaling messages used to convey communication fields, and in particular, application-originated (AO), text messages.

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

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

To transmit a text message, the application encapsulates the text message with the signaling message of the protocol. The protocol may be proprietary, or it may be commonly used in industry, such as SMPP. A text message originated by an 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 is passed 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 (e.g., SIP MESSAGE) and sends the SIP request to the destination (called the recipient) over the SIP-based network.

Technical specifications of 3GPP and 3GPP2 (Third Generation Partnership Project) define how much text messages are exchanged over packet-switched networks using SIP, such as 3GPP TS (Technical Specification) 24.341. As part of these specifications, when a text message is delivered to a 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 the success / failure of delivery of the text message.

Unfortunately, it is problematic to effectively associate multiple SIP transactions for AO MT text messages.

The embodiments described herein allow correlation of a plurality of SIP transactions using a correlation ID. When the gateway receives a text message initiated by the application, the gateway identifies the correlation ID and transmits the correlation ID to the application. The gateway also embeds a correlation ID in a SIP request that is used to send a text message to the recipient. The recipient's device (user device) receives the SIP request and initiates a new SIP request (a new SIP transaction) to report delivery success / failure for the text message. The recipient's device embeds the Correlation ID in the new SIP request according to an indication of delivery success / failure for the text message. When the gateway receives a new SIP request, the gateway locates the correlation ID and associates the new SIP request with the original delivery 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 the delivery report for the correlation ID and the text message. The application will be able to correlate a delivery request for a text message with a delivery response with a delivery report of the text message based on the correlation ID. Thus, the correlation ID advantageously allows the gateway to correlate multiple SIP transactions. Correlation IDs also allow an application to correlate delivery requests with delivery responses, allowing an application to know the delivery status of a text message.

One embodiment includes a text message gateway that intercepts communications between a text messaging application and a packet-switched network using SIP. When operating, the text messaging gateway receives a first delivery request from a text messaging application that includes an Application Originated (AO) text message intended for a user equipment (UE) served by the packet-switched network. The text messaging gateway identifies a correlation identifier (ID) for the AO text message, inserts the correlation ID into the delivery response, and forwards the delivery response to the text messaging application. The text messaging application can then store the correlation ID for later use. The text message gateway also transforms the first delivery request into a first SIP request (e.g., SIP MESSAGE) that compresses the AO text message, inserts the correlation ID into the first SIP request, Lt; / RTI >

In another embodiment, the text messaging gateway receives a second SIP request (e.g., another SIP MESSAGE) containing a delivery request for the AO text message from the UE, analyzes the second SIP request to identify the correlation ID And correlates the second SIP request with the first delivery 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 the correlation ID into the second delivery request, and send the second delivery request to the text messaging application. The text messaging application can 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 messaging application in an effective manner, so that the application can determine whether the text message has been successfully received by that receiver.

In another embodiment, the signaling protocol used by the text messaging application includes a Short Message Peer-to-Peer (SMPP) protocol. Thus, 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 messaging gateway can insert the correlation ID in the receipted_message_id field of the SMPP deliver_sm message.

In another embodiment, the text messaging gateway can insert the correlation ID of the first SIP request into the Mobile Application Part (RP) Message Reference field, and the text message gateway with the correlation ID in the MAP RP- Lt; RTI ID = 0.0 > ID < / RTI >

Another embodiment includes a method of interworking communications between a text messaging application and a packet-switched network using SIP. The method includes receiving from a text message application a first delivery request comprising 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 the correlation ID into the delivery response, and sending the delivery response to the text messaging application. The method also includes transforming the first forwarding request into a first SIP request compressing the AO text message, inserting the correlation ID into the first SIP request, and sending a first SIP request to the UE.

In another embodiment, the method further comprises receiving from the UE a second SIP request comprising a delivery report for the AO text message, analyzing a second SIP request to identify the correlation ID, 2 SIP request with a first forwarding request and a first SIP request.

In another embodiment, the method includes the steps of: inserting a delivery report into a second delivery request; inserting a correlation ID into a second delivery request; and sending a second delivery request to the text message application, Which can correlate a delivery report with a first delivery request originally used to deliver the delivery report.

In another embodiment, the signaling protocol used by the text messaging application includes the SMPP protocol. Thus, the first delivery request may include an SMPP submit_sm message, and the second delivery request may include an SMPP deliver_sm message. The step of 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 further comprises 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 with the correlation ID into the MAP RP-Message Reference field .

Other exemplary embodiments may be described below.

Some embodiments of the present invention are now described by way of example only and with reference to the drawings. The same reference numerals denote the same elements or the same elements of all the figures.

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

The drawings and the following description illustrate specific exemplary embodiments of the invention. It will therefore be understood by those skilled in the art that various ways of encompassing the principles of the invention and falling within the scope of the invention may be devised, although not explicitly described or shown herein. In addition, some of the examples described herein are intended for purposes of understanding the principles of the invention, and are intended to be interpreted without limitation to these specifically recited 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.

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

The external message center 110 includes any system, server, or device capable of generating a text message and sending a text message to the packet-switched network 120 for delivery to the UE 140. One example of the 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 transmission of text messages to the packet-switched network 120.

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

The communication system 100 also includes a text message gateway 130. The text messaging gateway 130 includes any system, server or device that intercepts communications between the external message center 110 and the UE 140 and / or the network element 122 of the packet-switched network 120 do. The application 112 of the external message center 110 can not support the protocols used for message delivery of the packet-switched network 120, such as SIP. Thus, the text messaging gateway 130 may allow the application 112 and various other applications to communicate with other protocols directed to the packet-switched network 120, such as Parlay, RESTful, LDAP, XML and SMPP ) ≪ / RTI > For example, if application 112 sends a text message intended for UE 140, application 112 may use the RESTful API to send a text message. The text message gateway 130 may normalize the RESTful protocol message and convert it to a SIP request. The text messaging gateway 130 may then send a SIP request to the UE 140 over the packet-switched network 120 to deliver the original text message. Some examples of text messaging gateway 130 include an IP-SM-GW in an IMS network or an LTE SMS gateway in an LTE network.

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

The text message gateway 130 includes a network interface 132 and a control system 134. The network interface 132 includes any device or component that communicates with the external message center 110 and other message centers via a variety of protocols. The network interface 132 may also communicate with one or more of the elements 122 of the packet-switched network 120 over a protocol used in 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 makes 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. The gateway 130 then sends a text message to the UE 140 of the SIP request. As a background, there are 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 so on. 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 (compressing a text message) is sent to the device, the receiving device does not provide a delivery report (text message delivery 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 SIP 200 OK. However, this SIP response does not indicate whether a text message in the SIP request has been successfully delivered to its recipient (s); It only indicates the delivery status of the SIP request. There can 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. For the 3GPP specification, the receiving device initiates a new SIP transaction to provide a delivery report of the text message by sending a separate SIP request reporting the delivery status.

The embodiments described herein allow correlation of a plurality of SIP transactions of the gateway 130 when processing AO text messages. Correlation is possible using the correlation ID, which is also described in Figs. 2-4.

2 is a flow diagram illustrating a method 200 of processing an AO text message of an exemplary embodiment. The steps of the method 200 will be described with reference to the text message gateway 130 of FIG. 1, but one of ordinary skill in the art will appreciate that the method 200 may be implemented in other networks and systems. The steps of the flowcharts described herein may not include all, but may include other steps not shown. The steps may also be performed in an alternate order.

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

In step 204, the 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 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 the correlation ID into 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 a delivery response. In step 208, the network interface 132 sends a forwarding response to the application 112 of the external message center 110. The 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 translates or intercepts the delivery request to SIP so that the text message is compressed into the SIP request or embedded in the SIP request. The SIP request may include a SIP MESSAGE or other type of SIP request to send text messages (e.g., SMS messages). The control system 134 may embed a text message in the MAP RP-DATA field of the SIP request. In step 212, the control system 134 also inserts or embeds the correlation ID in the SIP request. For example, the control system 134 may insert the correlation ID in the MAP RP-Message Reference field of the SIP request. The control system 134 may also identify the gateway ID to the gateway 130 and may insert or embed the gateway ID in the SIP request with the correlation ID. The gateway ID includes any string, integer, or value that uniquely references the text messaging gateway, such as gateway 130. The packet-switched network 120 may have a plurality of gateways used to transform or interwork text messages for redundancy and load balancing from the application 112 to the UE 140 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, the network element 122 attempts to deliver the SIP request to the UE 140.

3 is a flow chart illustrating a method 300 of processing an AO text message of a UE 140 in an exemplary embodiment. The steps of method 300 will be described with reference to system 100 of FIG. 1, but one of ordinary skill in the art will appreciate that method 300 may be implemented in other networks, systems, or devices.

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

In step 306, the UE 140 parses the original SIP request to identify the correlation ID. UE 140 may analyze the MAP RP-Message Reference field to look up 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 include another type of SIP request or SIP MESSAGE that again transmits the text messages (e.g., 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 to the MAP RP-Message Reference field of the new SIP request. At step 312, the UE 140 inserts a delivery report of the text message into the new SIP request. For example, the UE 140 may set the MAP-RP-Message Type to the RP-ACK or RP-ERROR of the new SIP request. At step 314, the UE 140 sends a new SIP request to the gateway 130 via the network element 122.

4 is a flow chart illustrating additional steps of a method 200 for processing AO text messages in an exemplary embodiment. At 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 receipt of the new SIP request, the gateway 130 sends a SIP 200 OK (via the network element 122) to the UE 140 which returns a successful receipt of the new SIP request. At step 218, the 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 look up the correlation ID. The control system 134 then correlates the original SIP request (which transmitted the text message) based on the correlation ID with the new SIP request (which transmitted the delivery report for the text message)

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

Thus, the 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 will be able to correlate the AO text message from the original delivery request with the delivery report from the new delivery request, and can determine whether the text message has been successfully delivered to its recipient (s) will be. The correlation ID advantageously allows the gateway 130 to correlate multiple SIP transactions in reporting the delivery status of the text message. The Correlation ID also allows the gateway 130 to pass back to the application 112 because all requests used to send a delivery report and text message between the application 112 and the UE 140 are surrounded by a common Correlation ID Allows to provide reports. As a result, delivery reports / receipts can be effectively provided to AO MT text messages.

Yes

FIG. 5 illustrates a communication system 500 of another exemplary embodiment. 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 (e. G., 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) HLR 512 is a central subscriber database that stores subscription information and other details (e.g., subscriber profiles) of UEs authorized to use CDMA network 510. The MSC 514 is a serving node for UEs and is responsible for processing voice telephones, SMS and other services in the CDMA network 510. The PDN-GW 516 includes any node or element in the CDMA network 510 that intercepts signaling between the CDMA network 510 and the packet-switched network, such as the IMS network 520. [ The CDMA network 510 may include other network elements not shown for the sake of brevity, such as base stations, radio 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, -GW) < / RTI > The P-CSCF 522 is an entry point for the IMS domain and served as an outbound proxy server for IMS devices. The S-CSCF 524 is the central node of the signaling plane and implements session control for IMS devices that initiate sessions over the IMS network 520. The S-CSCF 524 communicates with the IMS devices via one or more access networks not shown in FIG. The HSS 526 is a subscriber server that stores subscription-related information (e.g., subscriber profiles), performs authentication and authorization of end users, and provides information about the subscriber's location and the like. The P-GW 528 includes any node or element of the IMS network 520 that exchanges packets and external networks.

The elements of LTE network 530 are not shown in this embodiment for clarity.

The communication system 500 may also include an SMSC 542 and an LTE gateway, an IP Short Message Gateway (IP-SM-GW), or some other gateway for processing SMS via IP And Short Message Gateways (SM-GW) 544-545. The SMSC 542 includes any node for the circuit-translated network that carries SMS messages using store-and-forward processing. The SM-GWs 544-545 include any node that intercepts signaling between a SIP-based network and a network or device using a different signaling protocol. For example, if a network or device uses the SMPP protocol to exchange SMS messages, the SM-GWs 544-545 intercept the SMPP protocol messages for SIP, and vice versa. Communication system 500 also includes External Short Messaging Entities (ESME) 546 and 548. ESME is an external application connected to SMSC 542 or SM-GW 544-545 to engage in the transmission and / or reception of SMS messages.

Assume that this embodiment in which ESME 548 generates an SMS message intended for UE 550. The following example illustrates how the delivery state is provided to the SIP response.

6 is a message diagram illustrating successful delivery of an SMS message of an exemplary embodiment. By way of reference, the text message gateway 130 of FIG. 1 will be implemented in the SM-GWs 544 and 545 of this embodiment. After the ESME 548 generates an SMS message for the UE 550, the 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 indicates a delivery request from the ESME 548. One assumption at this point is that the 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. Thus, the ESME 548 sends 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. The SM-GW 544 may generate a new, unique ID in response to receiving the submit_sm request. Alternatively, the SM-GW 544 may re-use the message ID that was received from the ESME 548 in the submit_sm request. The SM-GW 544 then generates a submit_resp response and inserts the correlation ID into the submit_resp response. The SM-GW 544 then sends a submit_resp response to the ESME 548 with the Correlation ID (CORR ID). The ESME 548 parses 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 the Diameter UDR (User Data Request). The HSS 526 determines whether the UE 550 is registered and responds to the SM-GW 544 with a Diameter UDA (User Data Answer) indicating that the UE 550 is registered. The SM-GW 544 then configures the SIP MESSAGE to compress the SMS message. The SMS message is embedded in the RP-DATA (for example, the RP-USER DATA field) of the SIP MESSAGE. The SM-GW 544 also embeds the gateway ID and correlation ID for the SM-GW 544 in the SIP MESSAGE. For example, the SM-GW 544 may embed a gateway ID and a correlation ID as a combination string of RP-DATA (e.g., RP-Message Reference field) compressed in SIP MESSAGE. The SIP MESSAGE header may be constructed as follows:

MESSAGE tel: +19305020103 SIP / 2.0

Via: SIP / 2.0 / UDP 135.1.62.120:5060;branch=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:

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

The UE 550 also attempts to resolve the SMS message (RP-DATA) of the SIP MESSAGE to determine whether the SMS message was successfully delivered. Assume this embodiment that SMS has been successfully delivered. The UE 550 consequently determines that the delivery of the SMS message was successful and informs the SM-GW 544 of the successful delivery as follows. 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. Essentially, the UE 550 copies the RP-Message Reference field from the received SIP MESSAGE into the new SIP MESSAGE. The UE 550 also inserts the transfer report into the new SIP MESSAGE. The UE 550 then sends a new SIP MESSAGE to the S-CSCF 524. The new SIP MESSAGE can be as follows:

MESSAGE tel: +19305020103 SIP / 2.0

Via: SIP / 2.0 / UDP 135.1.30.70:5080;branch=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 a new SIP MESSAGE:

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. Thus, the SM-GW 545 sends a SIP 200 OK to the S-CSCF 524 that reports the successful receipt of the new SIP MESSAGE. The S-CSCF 524 sends a SIP 200 OK to the UE 550.

After receiving the new SIP MESSAGE, the SM-GW 545 analyzes the RP-ACK from the RP-Message Reference field and SIP MESSAGE to identify the correlation ID. The SM-GW 545 discovers that the previous RP-DATA message was sent by the SM-GW 544 based on the gateway ID for the 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 along with the correlation ID and delivery report. The SM-GW 545 sets the receipted_message_id of the SMPP deliver_sm request for the correlation ID. The SM-GW 545 also notifies the SM-GW 544 of the transactions. The SM-GW 544 stores the transaction data of the database.

The ESME 548 receives a deliver_sm request from the SM-GW 545. This request is a separate SMPP transaction 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. Thus, the SM-GW 545 can identify the delivery report for the SMS message based on the status information inserted in the deliver_sm request. Thus, the ESME 548 may correlate delivery status information with the SMS message that was advantageously transmitted. Although the SM-GW 544 translated the SMS message from the SMPP to the SIP, the ESME 548 could receive delivery status information for the SMS message.

Any of the various elements described herein or illustrated 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 components may be referred to as "processors," " controllers, " or some similar terminology. 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 apparent use of the term " processor "or" controller "should not be construed to refer solely to hardware capable of executing software and includes, without limitation, digital signal processor (DSP) ) Or other circuitry, a field programmable gate array (FPGA), read only memory (ROM) for storing software, random access memory (RAM), nonvolatile storage, logic, or some other physical hardware component or module .

In addition, elements may be implemented as instructions executable by a processor or computer to perform the functions of an element. Some examples of the instructions are software, program code and firmware. The instructions are optional when executed by a processor that directs the processor to execute the functions of the element. The instructions may be stored on storage devices readable by the processor. Some examples of storage devices are digital or solid-state memories, magnetic storage media such as magnetic disks and magnetic tapes, hard drives, or selectively 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 any equivalents thereof.

Claims (10)

A text messaging gateway configured to interwork communications between a packet-switched network using a Session Initiation Protocol (SIP) and a text messaging application,
The text messaging gateway may also receive a first delivery request from the text message application, the first delivery request including an AO (Application Originated) text message intended for User Equipment (UE) served by the packet- Creating a correlation identifier that uniquely references the AO text message, inserting the correlation ID that uniquely references the AO text message in the delivery response, And send a response to the text messaging application,
The text message gateway may also be configured to translate the first delivery request into a first SIP request that encapsulates the AO text message and to associate the correlation ID that uniquely references the AO text message with the first SIP request And send the first SIP request to the UE. The method according to claim 1,
The text messaging gateway may also receive a second SIP request from the UE that includes a delivery report for the AO text message, parse the second SIP request to identify the correlation ID, And correlate at least one of the first SIP request and the first delivery request with the second SIP request based on the correlation ID. 3. The method of claim 2,
The text messaging gateway is further configured to insert the delivery report in a second delivery request, insert the correlation ID into the second delivery request, and send the second delivery request to the text messaging application, Wherein the message application is capable of correlating the delivery report with the first delivery request originally used to deliver the AO text message. The method of claim 3,
Wherein the signaling protocol used by the text messaging application comprises a Short Message Peer-to-Peer (SMPP) protocol;
The first delivery request comprising an SMPP submit_sm message;
The second delivery request comprising an SMPP deliver_sm message;
Wherein the text messaging gateway is further configured to insert the correlation ID in the receipted_message_id field of the SMPP deliver_sm message. The method according to claim 1,
The text messaging gateway is further configured to insert the correlation ID of the first SIP request in a Mobile Application Part (RP) Message Reference field;
Wherein the text messaging gateway is further configured to insert the gateway ID for the text message gateway with the correlation ID in the MAP RP-Message Reference field. Receiving from a text message application a first delivery request comprising an Application Originated (AO) text message intended for a User Equipment (UE) served by a packet-switched network;
Generating a correlation identifier (ID) that uniquely references the AO text message;
Inserting the Correlation ID that solely refers to the AO text message in the delivery response;
Sending the forwarding response to the text messaging application;
Converting the first delivery request into a first SIP request compressing the AO text message;
Inserting the correlation ID that uniquely references the AO text message in the first SIP request;
And sending the first SIP request to the UE. The method according to claim 6,
Receiving a second SIP request from the UE comprising a delivery report for the AO text message;
Analyzing the second SIP request to identify the correlation ID;
And correlating the first delivery request and the first SIP request with the second SIP request based on the correlation ID. 8. The method of claim 7,
Inserting the delivery report in a second delivery request;
Inserting the correlation ID into the second delivery request;
And sending the second delivery request to the text messaging application to allow the text messaging application to correlate the delivery report with the first delivery request originally used to send the AO text message. . 9. The method of claim 8,
Wherein the signaling protocol used by the text messaging application comprises an SMPP protocol;
The first delivery request comprising an SMPP submit_sm message;
The second delivery request comprising an SMPP deliver_sm message;
Wherein inserting the correlation ID in the second delivery request comprises inserting the correlation ID in the 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 in a MAP RP-Message Reference field;
And inserting the gateway ID for the text message gateway with the correlation ID in the MAP RP-Message Reference field.

Images