Application data delivery service for networks supporting multiple transport mechanisms

Patent metadata

Field	Value
Publication number	US-10602322-B2
Application number	US-201816050078-A
Country	US
Kind code	B2
Filing date	Jul 31, 2018
Priority date	Jul 3, 2014
Publication date	Mar 24, 2020
Grant date	Mar 24, 2020

Abstract

An Application Data Delivery Service (ADDS) facilitates application data transfer between applications that may reside in a device domain (e.g., M2M/MTC devices and gateways) and applications residing in a network domain (e.g., an AS or SCS). The ADDS leverages existing 3GPP transport mechanisms, such as NAS, SMS, USSD, and User Plane, and it is configured to select a transport mechanism for delivering application data based on criteria, such as application data characteristics, application/end node characteristics and availability, subscription information, policies of the network, network conditions (such as congestion, node availability) and the like.

First claim

What is claimed:

1. An apparatus comprising a processor and a memory, the memory storing computer-executable instructions which, when executed by the processor, cause the apparatus to operate as an interworking function of a communications network, the computer-executable instructions further causing the interworking function to provide an application data delivery service for enabling communication between a first application that is hosted on a user equipment and a second application that is hosted on a server, the application data delivery service configured to perform operations comprising:
receiving, from the second application on a first interface that comprises an application programming interface exposed by the application data delivery service to the second application, a first request to send a packet to the first application via the communications network, the first request comprising an indication of whether the second application desires the packet to be acknowledged and an identifier of the first application;
encoding, based on the first request, a header comprising the indication of whether the packet should be acknowledged, the identifier of the first application, and a field that is used to support sequencing of packets; and
sending, to a mobility management entity of the communications network, via a second interface that comprises a diameter interface, a second request requesting that the header and the packet be sent to the user equipment, the second request comprising the packet and the header, wherein the application data delivery service is first configured for communication with the first application by:
receiving, from the second application, a third request to configure a connection between the second application and the user equipment that hosts the first application, the third request comprising an identifier of the user equipment, the identifier of the first application, and an identifier of the second application;
sending a fourth request to a home subscriber server of the communications network to authorize the connection to the user equipment, the fourth request comprising the user equipment identifier;
receiving a response to the fourth request, the response comprising an international mobile subscriber identity and an indication of whether or not the connection to the user equipment is authorized;
maintaining a mapping between the user equipment identifier, the identifier of the first application, the identifier of the second application, and the international mobile subscriber identity; and
responding to the third request, the response indicating that the application data delivery service between the first and second applications is supported.

2. The apparatus of claim 1 , wherein the application data delivery service receives a message from the home subscriber server indicating that a subscription associated with the user equipment has changed.

3. The apparatus of claim 1 , wherein the application data delivery service performs additional operations comprising:
sending, to the user equipment, a message with an indication that the application data delivery service is supported.

4. The apparatus of claim 3 , wherein the message with the indication to the user equipment is sent in a protocol configuration options (PCO) field in response to a packet data network (PDN) connectivity request.

5. The apparatus of claim 4 , wherein the message with the indication includes a maximum packet size.

6. The apparatus of claim 1 , wherein the first request comprises at least one of an indication of whether or not the packet can be buffered by the application data delivery service, how long the packet is valid and a priority of the packet.

7. The apparatus of claim 1 , wherein the application data delivery service responds to the server to indicate that the first request to send a packet has been accepted for delivery.

8. The apparatus of claim 1 , wherein if the first request includes an indication that the request is delay tolerant, the application data delivery service buffers the request until the first application becomes reachable.

9. The apparatus of claim 1 , wherein the application data delivery service receives an acknowledgement of the packet from the user equipment.

10. The apparatus of claim 9 , wherein the application data delivery service, after receiving the acknowledgement from the user equipment, sends an indication to the server that sending of the packet is complete.

11. The apparatus of claim 1 , wherein the second request further comprises a second field that is used to support segmentation and re-assembly of packets.

12. A method implemented in an interworking function of a communications network, the interworking function providing an application data delivery service for enabling communication between a first application that is hosted on a user equipment and a second application that is hosted on a server, the method comprising:
receiving, from the second application on a first interface that comprises an application programming interface exposed by the application data delivery service to the second application, a first request to send a packet to the first application via the communications network, the first request comprising an indication of whether the second application desires the packet to be acknowledged and an identifier of the first application;
encoding, based on the first request, a header comprising the indication of whether the packet should be acknowledged, the identifier of the first application, and a field that is used to support sequencing of packets; and
sending, to a mobility management entity of the communications network, via a second interface that comprises a diameter interface, a second request requesting that the header and the packet be sent to the user equipment, the second request comprising the packet and the header, wherein the application data delivery service is first configured for communication with the first application by:
receiving, from the second application, a third request to configure a connection between the second application and the user equipment that hosts the first application, the third request comprising an identifier of the user equipment, the identifier of the first application, and an identifier of the second application;
sending a fourth request to a home subscriber server of the communications network to authorize the connection to the user equipment, the fourth request comprising the user equipment identifier;
receiving a response to the fourth request, the response comprising an international mobile subscriber identity and an indication of whether or not the connection to the user equipment is authorized;
maintaining a mapping between the user equipment identifier, the identifier of the first application, the identifier of the second application, and the international mobile subscriber identity; and
responding to the third request, the response indicating that the application data delivery service between the first and second applications is supported.

13. The method of claim 12 , further comprising receiving a message from the home subscriber server indicating that a subscription associated with the user equipment has changed.

14. The method of claim 12 , further comprising:
sending, to the user equipment, a message with an indication that the application data delivery service is supported.

15. The method of claim 14 , wherein the message with the indication to the user equipment is sent in a protocol configuration options (PCO) field in response to a packet data network (PDN) connectivity request.

Assignees

• Convida Wireless LLC

Inventors

• Palanisamy Suresh
• Murthy Prashanth
• Starsinic Michael F

Classifications

• H04W4/70 Primary

  Services for machine-to-machine communication [M2M] or machine type communication [MTC] · CPC title

• H04W4/14 Primary

  Short messaging services, e.g. short message services [SMS] or unstructured supplementary service data [USSD] · CPC title

• H04W4/60

  Subscription-based services using application servers or record carriers, e.g. SIM application toolkits · CPC title

• H04W4/50

  Service provisioning or reconfiguring · CPC title