Application data delivery service for networks supporting multiple transport mechanisms

Patent metadata

Field	Value
Publication number	US-10993089-B2
Application number	US-202016788727-A
Country	US
Kind code	B2
Filing date	Feb 12, 2020
Priority date	Jul 3, 2014
Publication date	Apr 27, 2021
Grant date	Apr 27, 2021

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. A user equipment comprising a processor and a memory, the memory storing computer executable instructions which, when executed by the processor, cause the user equipment to provide an application data delivery service for enabling communication between a first application that is hosted on the user equipment and a second application, the application data delivery service being configured to perform operations comprising:
receiving, from the first application on a first interface that comprises an application programing interface exposed by the application data delivery service to the first application, a first request to send a packet to the second application via a communications network, the first request comprising an indication of whether the first application desires the packet to be acknowledged and an identifier of the second application;
encoding, based on the first request, a header comprising the indication of whether the packet should be acknowledged, the identifier of the second 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 Non-Access Stratum (NAS) Message, a second request requesting that the packet be sent to the second application, the second request comprising the packet and the header.

2. The user equipment of claim 1 , wherein the instructions, when executed, further cause the application data delivery service to perform operations comprising:
receiving, at the user equipment, a message with an indication that the application data delivery service is supported in the PDN connection.

3. The user equipment of claim 2 , 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.

4. The user equipment of claim 3 , wherein the message with the indication includes a maximum packet size.

5. The user equipment 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.

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

7. The user equipment 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.

8. The user equipment of claim 1 , wherein the application data delivery service receives an acknowledgement of the packet from the communications network.

9. The user equipment of claim 8 , wherein the application data delivery service, after receiving the acknowledgement from the communications network, sends an indication to the first application that sending of the packet is complete.

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

11. A method implemented in a user equipment, the user equipment providing an application data delivery service for enabling communication between a first application that is hosted on the user equipment and a second application, the method comprising:
receiving, from the first application on a first interface that comprises an application programing interface exposed by the application data delivery service to the first application, a first request to send a packet to the second application via a communications network, the first request comprising an indication of whether the first application desires the packet to be acknowledged and an identifier of the second application;
encoding, based on the first request, a header comprising the indication of whether the packet should be acknowledged, the identifier of the second 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 Non-Access Stratum (NAS) Message, a second request requesting that the packet be sent to the second application, the second request comprising the packet and the header.

12. The method of claim 11 , further comprising:
receiving, at the user equipment, a message with an indication that the application data delivery service is supported in the PDN connection.

13. The method of claim 12 , 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.

14. The method of claim 13 , wherein the message with the indication includes a maximum packet size.

15. The method of claim 11 , 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.

16. The method of claim 11 , wherein the application data delivery service responds to the first application to indicate that the first request to send a packet has been accepted for delivery.

17. The method of claim 11 , 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.

18. The method of claim 11 , wherein the application data delivery service receives an acknowledgement of the packet from the communications network.

19. The method of claim 18 , wherein the application data delivery service, after receiving the acknowledgement from the communications network, sends an indication to the first application that sending of the packet is complete.

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

Assignees

• Convida Wireless LLC

Inventors

• Palanisamy Suresh
• Murthy Prashanth
• Starsinic Michael F

Classifications

• H04W4/50

  Service provisioning or reconfiguring · 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/70 Primary

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