Transport protocol for anticipatory content

• US 9,935,740 B2
• Filed: 10/17/2014
• Issued: 04/03/2018
• Est. Priority Date: 06/14/2011
• Status: Active Grant

• Current Assignee: ViaSat Incorporated
• Original Assignee: ViaSat Incorporated
• Inventors: Sebastian, William B.
• Primary Examiner(s): Oveissi, David
• Application Number:
  US14/517,337
• Publication Number:
  US 20150036686A1
• Time in Patent Office: 1,264 Days
• CPC Class Codes: H04L 1/08 by repeating transmission, e.g. Verdan system H04L1/1858 and H04L1/189 take precedence
• CPC Class Codes: H04L 12/18 for broadcast or conference , e.g. multicast
• CPC Class Codes: H04L 12/1863 comprising mechanisms for improved reliability, e.g. status reports arrangements for detecting or preventing errors by carrying supervisory signal the return channel H04L1/16
• CPC Class Codes: H04L 43/0823 Errors, e.g. transmission errors
• CPC Class Codes: H04L 65/612 for unicast
• CPC Class Codes: H04L 67/1097 for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
• CPC Class Codes: H04N 21/2402 Monitoring of the downstream path of the transmission network, e.g. bandwidth available traffic monitoring in data switching networks H04L43/00; monitoring data switching networks utilization H04L43/0876
• CPC Class Codes: H04N 21/6375 for requesting retransmission , e.g. of data packets lost or corrupted during transmission from serverARQ protocols H04L1/18; implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP] H04L69/16
• CPC Class Codes: H04N 21/6405 Multicasting data broadcast and multicast in packet switching networks H04L12/18
• CPC Class Codes: H04N 21/6408 Unicasting
• CPC Class Codes: H04N 21/6583 Acknowledgement
• CPC Class Codes: H04N 21/835 Generation of protective data, e.g. certificates protecting software against unauthorised usage in a vending or licensing environment G06F21/10

Abstract

Methods, apparatuses, and systems for improving utilization of a communications system (e.g., a satellite communications system) are provided, using delayed reliability techniques as part of a multicast transport protocol. Embodiments may operate in a client-server context, in which the server-side of the communication link multicasts data to requesting users and to users where the data is being speculatively prepositioned. Requesting users may implement reliability checks to verify receipt of complete data in response to the request while user systems where data is being speculatively prepositioned may receive multicast reliability information in response to reliability requests from other users, but may not request replacement of missing or corrupted data themselves until a request is made for the data by that system.

Claims

1. A method for providing reliability in a communications system having a server side in communication with a plurality of user systems via a shared communications infrastructure, the method comprising:

identifying, in response to receiving a request for a content object from a first user system, a second user system as an anticipatory user system that is presently not requesting the content object;

multicasting the content object over the shared communications infrastructure from the server side to at least the first and second user systems in response to the identifying;

first receiving, by the server side from the first user system in response to the multicasting, a first reliability message indicating which portions of the content object were received by the first user system via the multicasting;

first communicating, by the server side to at least the first user system in response to the first reliability message, a first repair message comprising at least some of the portions of the content object not received by the first user system via the multicasting as identified by the first reliability message;

second receiving, by the server side from the second user system, a request message explicitly requesting the content object, the request message being received after the multicasting the content object;

determining, by the server side, portions of the content object not received by the second user system via the multicasting; and

second communicating, by the server side to at least the second user system in response to the request message, a response message comprising at least some of the portions of the content object determined as not received by the second user system via the multicasting.

2. The method of claim 1 wherein:

the first user system is identified as a canary user system that represents common error dynamics of a cross-section of user systems.

3. The method of claim 1 wherein:

the first reliability message comprises explicit positive acknowledgements of data packets of the content object that were successfully received by the first user system via the multicasting.

4. The method of claim 1 wherein:

the first reliability message comprises explicit negative acknowledgements of data packets of the content object that were not successfully received by the first user system via the multicasting.

5. The method of claim 1, wherein:

the first reliability message identifies holes in a page map corresponding to portions of the content object that were not successfully received by the first user system via the multicasting.

6. The method of claim 1 wherein:

the first reliability message is generated by the first user system in response to the first user system error-checking received multicast data of the content object.

7. The method of claim 1 wherein:

the first communicating comprises the server side unicasting the first repair message to the first user system.

8. The method of claim 1 wherein:

the first communicating comprises the server side multicasting the first repair message to at least the first and second user systems.

9. The method of claim 1 wherein:

the request message comprises a second reliability message indicating which portions of the content object were received by the second user system via the multicasting.

10. The method of claim 1 wherein:

the second receiving is in response to a request by the server side to the second user system for the second user system to communicate a second reliability message indicating which portions of the content object were received by the second user system via at least the multicasting.

11. The method of claim 10 wherein:

the second reliability message indicates which portions of the content object were not successfully received by the second user system via at least the multicasting and the first repair message.

12. The method of claim 10 wherein:

the response message comprises at least some of the portions of the content object not received by the second user system via at least the multicasting as identified by the second reliability message.

13. The method of claim 1, wherein the second communicating comprises:

determining, for each data block of the content object, whether the data block is presently stored in a local cache of the second user system; and

formulating the response message to comprise;

compressed instances of the data blocks determined to be presently stored in the local cache; and

uncompressed instances of the data blocks determined not to be presently stored in the local cache.

14. The method of claim 13, wherein the second communicating comprises:

unicasting the compressed instances of the data blocks to the second user system; and

multicasting the uncompressed instances of the data blocks to a plurality of user systems comprising the second user system.

15. The method of claim 13, wherein the determining comprises, for each data block of the content object:

computing a fingerprint of the data block as a function of byte-level information comprised by the content portion of the data block; and

determining that the data block is presently stored in the local cache of the second user system when the fingerprint matches an entry in a client dictionary model that is associated with the second user system and maintained by the server side.

16. A server system for providing reliability in a communications system, the server system in communication with a plurality of user systems via a shared communications infrastructure, the server system comprising:

a multicaster module that multicasts a content object over the shared communications infrastructure from the server side to at least first and second user systems; and

a server optimizer that;

identifies, in response to receiving a request for a content object from a first user system, a second user system as an anticipatory user system that is presently not requesting the content object, wherein the multicasting is by the multicaster module according to the identifying;

first receives, from the first user system in response to the multicasting, a first reliability message indicating which portions of the content object were received by the first user system via the multicasting;

directs first communication, to at least the first user system in response to the first reliability message, of a first repair message comprising at least some of the portions of the content object not received by the first user system via the multicasting as identified by the first reliability message;

second receives, from the second user system, a request message explicitly requesting the content object, the request message being received after the multicasting the content object;

determines portions of the content object not received by the second user system via the multicasting; and

directs second communication, to at least the second user system in response to the request message, of a response message comprising at least some of the portions of the content object determined as not received by the second user system via the multicasting.

17. The system of claim 16 wherein:

the first reliability message comprises explicit positive acknowledgements of data packets of the content object that were successfully received by the first user system via the multicasting.

18. The system of claim 16 wherein:

the first reliability message comprises explicit negative acknowledgements of data packets of the content object that were not successfully received by the first user system via the multicasting.

19. The system of claim 16 wherein:

the first reliability message identifies holes in a page map corresponding to portions of the content object that were not successfully received by the first user system via the multicasting.

20. The system of claim 16 wherein the server optimizer directs first communication by directing unicasting of the first repair message to the first user system.

21. The system of claim 16 wherein the server optimizer directs first communication by directing multicasting of the first repair message to the first user system.

22. The system of claim 16 wherein:

the server optimizer communicates a request to the second user system for the second user system to communicate a second reliability message indicating which portions of the content object were received by the second user system via the multicasting; and

the server optimizer second receives the second reliability message is in response to the request from the server optimizer.

23. The system of claim 16 wherein the server optimizer directs second communication by:

determining, for each data block of the content object, whether the data block is presently stored in a local cache of the second user system; and

formulating the response message to comprise;

compressed instances of the data blocks determined to be presently stored in the local cache; and

uncompressed instances of the data blocks determined not to be presently stored in the local cache.

24. The system of claim 23 wherein the server optimizer directs second communication further by:

unicasting the compressed instances of the data blocks to the second user system; and

multicasting the uncompressed instances of the data blocks to a plurality of user systems comprising the second user system.

25. The system of claim 23 wherein the determining comprises, for each data block of the content object:

computing a fingerprint of the data block as a function of byte-level information comprised by the content portion of the data block; and

determining that the data block is presently stored in the local cache of the second user system when the fingerprint matches an entry in a client dictionary model that is associated with the second user system and maintained by the server side.