Interface between restful web services and packet-switched networks for text messaging
View Patent ↗Systems and methods are disclosed for interfacing RESTful web applications with packet-switched networks for text messaging. One embodiment comprises a system that handles a Mobile Terminated (MT) text message from a web application to a packet-switched network. The system receives a RESTful send operation for sending the MT text message from the web application. The system converts the RESTful send operation for the MT text message to a send request that is based on a signaling protocol used by the packet switched network, such as SIP, SMPP, or MAP. The system then transmits the send request for the MT text message to the packet-switched network for delivery of the MT text message to a recipient.
1. A system comprising:
a conversion system implemented between a web application and a packet-switched network, the conversion system comprising:
an interface configured to receive a RESTful send operation for sending a Mobile Terminated (MT) text message from the web application to a recipient; and
a controller configured to convert the RESTful send operation for the MT text message to a first Session Initiation Protocol (SIP) request that encapsulates MAP-Relay Protocol (RP) data, to extract address data and an SMS body for the MT text message from the RESTful send operation, to map the address data to a MAP RP-Originating-Address field and a MAP RP-Destination-Address field of the first SIP request, and to map the SMS body for the MT text message to a MAP TP-User Data field of a Transfer Protocol Data Unit (TPDU) contained in a MAP RP-User-Data field of the first SIP request;
the interface is configured to transmit the first SIP request for the MT text message to the packet-switched network for delivery of the MT text message to the recipient;
the interface is configured to receive a second SIP request from the packet-switched network indicating a delivery status for the MT text message, wherein the second SIP request encapsulates the MAP-RP data;
the controller is configured to convert the second SIP request to a RESTful status operation, to parse the MAP TP-User Data field of the TPDU contained in the MAP RP-User-Data field of the second SIP request to identify a delivery status of the MT text message to the recipient, and to encapsulate the delivery status of the MT text message in the RESTful status operation; and
the interface is configured to transmit the RESTful status operation to the web application.
2. The system of claim 1 wherein:
the first SIP request comprises a SIP MESSAGE.
3. The system of claim 1 wherein:
the RESTful send operation comprises an HTTP POST.
4. The system of claim 1 wherein the MT text message comprises a Short Messaging Service (SMS) message.
5. The system of claim 1 wherein the MT text message comprises a Multimedia Messaging Service (MMS) message.
6. The system of claim 1 wherein:
the interface is configured to receive a third SIP request for a Mobile Originated (MO) text message from the packet-switched network, wherein the third SIP request encapsulates the MO text message in the MAP-RP data;
the controller is configured to convert the third SIP request to a RESTful receive operation, to extract an SMS body for the MO text message from the MAP TP-User Data field of the TPDU contained in the MAP RP-User-Data field of the third SIP request, and to encapsulate the SMS body for the MO text message in the RESTful receive operation; and
the interface is configured to transmit the RESTful receive operation for the MO text message to the web application for delivery of the MO text message to a user of the web application.
7. The system of claim 6 wherein:
the interface is configured to receive a RESTful status operation from the web application indicating a delivery status for the MO text message to the user of the web application;
the controller is configured to convert the RESTful status operation to a fourth SIP request that encapsulates the MAP-RP data, and to map the delivery status from the RESTful status operation to the MAP TP-User Data field of the TPDU contained in the MAP RP-User-Data field of the fourth SIP request; and
the interface is configured to transmit the fourth SIP request to the packet-switched network.
8. A method comprising:
receiving a RESTful send operation for sending a Mobile Terminated (MT) text message from a web application to a recipient;
converting the RESTful send operation for the MT text message to a first Session Initiation Protocol (SIP) request that encapsulates MAP-Relay Protocol (RP) data;
extracting address data and an SMS body for the MT text message from the RESTful send operation;
mapping the address data to a MAP RP-Originating-Address field and a MAP RP-Destination-Address field of the first SIP request;
mapping the SMS body for the MT text message to a MAP TP-User Data field of a Transfer Protocol Data Unit (TPDU) contained in a MAP RP-User-Data field of the first SIP request;
transmitting the first SIP request for the MT text message to the packet-switched network for delivery of the MT text message to the recipient;
receiving a second SIP request from the packet-switched network indicating a delivery status for the MT text message, wherein the second SIP request encapsulates the MAP-RP data;
converting the second SIP request to a RESTful status operation;
parsing the MAP TP-User Data field of the TPDU contained in the MAP RP-User-Data field of the second SIP request to identify a delivery status of the MT text message to the recipient;
encapsulating the delivery status of the MT text message in the RESTful status operation; and
transmitting the RESTful status operation to the web application.
9. The method of claim 8 wherein:
the first SIP request comprises a SIP MESSAGE.
10. The method of claim 8 wherein:
the RESTful send operation comprises an HTTP POST.
11. The method of claim 8 wherein the MT text message comprises a Short Messaging Service (SMS) message.
12. The method of claim 8 wherein the MT text message comprises a Multimedia Messaging Service (MMS) message.
13. The method of claim 8 further comprising:
receiving a third SIP request for a Mobile Originated (MO) text message from the packet-switched network, wherein the third SIP request encapsulates the MO text message in the MAP-RP data;
converting the third SIP request to a RESTful receive operation;
extracting an SMS body for the MO text message from the MAP TP-User Data field of the TPDU contained in the MAP RP-User-Data field of the third SIP request;
encapsulating the SMS body for the MO text message in the RESTful receive operation; and
transmitting the RESTful receive operation for the MO text message to the web application for delivery of the MO text message to a user of the web application.
14. The method of claim 13 further comprising:
receiving a RESTful status operation from the web application indicating a delivery status for the MO text message to the user of the web application;
converting the RESTful status operation to a fourth SIP request that encapsulates the MAP-RP data;
mapping the delivery status from the RESTful status operation to the MAP TP-User Data field of the TPDU contained in the MAP RP-User-Data field of the fourth SIP request; and
transmitting the fourth SIP request to the packet-switched network.
15. A system comprising:
an Application Programming Interface (API) for a web application used in text messaging;
the API including a processor configured to receive a RESTful send operation for sending a Mobile Terminated (MT) text message from the web application to User Equipment (UE), to convert the RESTful send operation for the MT text message to a first Session Initiation Protocol (SIP) request that encapsulates MAP-Relay Protocol (RP) data, to extract address data and an SMS body for the MT text message from the RESTful send operation, to map the address data to a MAP RP-Originating-Address field and a MAP RP-Destination-Address field of the first SIP request, to map the SMS body for the MT text message to a MAP TP-User Data field of a Transfer Protocol Data Unit (TPDU) contained in a MAP RP-User-Data field of the first SIP request, and to transmit the first SIP request for the MT text message to the packet-switched network for delivery of the MT text message to the UE;
the processor of the API is configured to receive a second SIP request from the packet-switched network indicating a delivery status for the MT text message, wherein the second SIP request encapsulates the MAP-RP data;
the processor of the API is configured to convert the second SIP request to a RESTful status operation, to parse the MAP TP-User Data field of the TPDU contained in the MAP RP-User-Data field of the second SIP request to identify a delivery status of the MT text message to the UE, to encapsulate the delivery status of the MT text message in the RESTful status operation, and to transmit the RESTful status operation to the web application.
16. The system of claim 15 wherein:
the processor of the API is configured to receive a third SIP request for a Mobile Originated (MO) text message from the packet-switched network, wherein the third SIP request encapsulates the MO text message in the MAP-RP data;
the processor of the API is configured to convert the third SIP request to a RESTful receive operation, to extract an SMS body for the MO text message from the MAP TP-User Data field of the TPDU contained in the MAP RP-User-Data field of the third SIP request, to encapsulate the SMS body for the MO text message in the RESTful receive operation, and to transmit the RESTful receive operation for the MO text message to the web application for delivery of the MO text message to a user of the web application.