DELAY-TOLERANT AND LOSS-TOLERANT DATA TRANSFER FOR MOBILE APPLICATIONS

• US 20140115406A1
• Filed: 05/01/2013
• Published: 04/24/2014
• Est. Priority Date: 10/19/2012
• Status: Active Grant

• Current Assignee: NEC Corporation
• Original Assignee: NEC Laboratories America Inc (NEC Corporation)
• Inventors: Aranya, Akshat, Ungureanu, Cristian, Agrawal, Nitin
• Granted Patent: US 9,131,010 B2
• Time in Patent Office: Days
• US Class Current: 714/47.1
• CPC Class Codes: H04L 67/06 specially adapted for file transfer, e.g. file transfer protocol [FTP]
• CPC Class Codes: H04L 67/1095 Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
• CPC Class Codes: H04L 67/62 Establishing a time schedule for servicing the requests
• CPC Class Codes: H04L 69/24 Negotiation of communication capabilities

Abstract

A method supports data communication in a mobile application by specifying in the mobile application a program intent and one or more course or fine-grained properties of data objects in terms of tolerance to delay and loss; selecting a transfer policy for a set of data objects based on the application intent; receiving and coalescing intents of one or more applications for object data for the one or more applications; crafting an aggregate transfer policy, and communicating data from one or more applications as an aggregate based on the aggregate transfer policy to programmatically incorporate and benefit from tolerance to delay in the transfer of data.

Claims

1. A method to communicate data in a mobile application, comprising:

specifying in the mobile application a program intent and one or more course or fine-grained properties of data objects in terms of tolerance to delay and loss; and

selecting a transfer policy for a set of data objects based on the application intent.

2. The method of claim 1, comprising handling events generated as a result of a data item being transferred, delayed, or lost, if a notification is desired by the application;

3. The method of claim 1, wherein the transfer policy comprises network type, network characteristics, server load, or system-wide metric of interest.

4. The method of claim 1, comprising sending instruction for data to be discarded on the server-side if the application can tolerate loss of that data

5. The method of claim 1, comprising connecting multiple writers (mobile devices) operating on the same table.

6. The method of claim 1, comprising operating a cloud service that interprets a custom network protocol and interprets application intents.

7. The method of claim 1, comprising reducing data through coalescing, compression, deduplication, and piggybacking to reduce the number of messages and bytes transferred over a network, based on a transfer policy.

8. The method of claim 1, comprising specifying predetermined data type (tables) to sync over a particular network by providing each table with its own network sync preference for reads and writes, wherein each app specifies a sync preference with a table registration.

9. The method of claim 1, comprising receiving and coalescing intents of multiple applications for object data for the multiple applications;

crafting an aggregate transfer policy, and

10. The method of claim 1, comprising communicating data from multiple applications as an aggregate based on the aggregate transfer policy to programmatically incorporate and benefit from tolerance to delay in the transfer of data.

11. The method of claim 1, comprising sending instruction for loss-tolerant data to be discarded on a server-side.

12. A system to communicate data in a mobile application, comprising computer readable code for:

specifying in the mobile application a program intent and one or more course or fine-grained properties of data objects in terms of tolerance to delay and loss;

selecting a transfer policy for a set of data objects based on the application intent;

receiving and coalescing intents of one or more applications for object data for the one or more applications;

crafting an aggregate transfer policy, and

communicating data from one or more applications as an aggregate based on the aggregate transfer policy to programmatically incorporate and benefit from tolerance to delay in the transfer of data.

13. The system of claim 12, comprising computer readable code for handling events generated as a result of a data item being transferred, delayed, or lost, if a notification is desired by the application;

14. The system of claim 12, wherein the transfer policy comprises network type, network characteristics, server load, or system-wide metric of interest.

15. The system of claim 12, comprising computer readable code for sending instruction for loss-tolerant data to be discarded on the server-side.

16. The system of claim 12, comprising computer readable code for connecting multiple disconnected writers to one table.

17. The system of claim 12, comprising computer readable code for operating a cloud service that interprets a custom network protocol and interprets application intents.

18. The system of claim 12, comprising computer readable code for reducing data through coalescing, compression, and piggybacking to reduce the number of messages and bytes transferred over a network, based on a transfer policy.

19. The system of claim 12, comprising computer readable code for aggregating intents across several mobile applications, each of which individually may have no or limited benefit from delay and loss tolerance.

20. The system of claim 12, comprising computer readable code for specifying predetermined data type (tables) to sync over a particular network by providing each table with its own network sync preference for reads and writes, wherein each app specifies a sync preference with a table registration.