Delaycast queue prioritization

• US 10,361,964 B2
• Filed: 08/26/2015
• Issued: 07/23/2019
• Est. Priority Date: 03/14/2013
• Status: Active Grant

• Current Assignee: ViaSat Incorporated
• Original Assignee: ViaSat Incorporated
• Inventors: Dankberg, Mark D., Newman, Daniel M., Hart, Steven R.
• Primary Examiner(s): Crutchfield, Christopher M
• Application Number:
  US14/836,815
• Publication Number:
  US 20160191405A1
• Time in Patent Office: 1,427 Days
• CPC Class Codes: H04L 12/18 for broadcast or conference , e.g. multicast
• CPC Class Codes: H04L 12/1881 with schedule organisation, e.g. priority, sequence management
• CPC Class Codes: H04L 47/56 implementing delay-aware scheduling
• CPC Class Codes: H04L 47/806 Broadcast or multicast traffic
• CPC Class Codes: H04L 67/56 Provisioning of proxy services store-and-forward switching systems in data switching networks H04L12/54
• CPC Class Codes: H04L 67/566 Grouping or aggregating service requests, e.g. for unified processing
• CPC Class Codes: H04L 67/5682 Policies or rules for updating, deleting or replacing the stored data

Abstract

Systems and methods are described for optimizing resource utilization in a communications network while also optimizing subscriber engagement with media content over the communications network. Requested content objects can be identified as delayable objects that can be queued for opportunistically delayed communication to both requesting and non-requesting subscribers. Queued delayed content objects are scored with an eye toward optimizing both subscriber engagement and utilization of opportunistically available communications link resources. For example, a storage manager calculates a likelihood that each subscriber will engage with the content if it is opportunistically delivered, and a scheduler calculates a priority order in which to queue each requested delayable content object. Content objects can then be multicast to the subscribers in priority order and with associated information that can be used by the subscribers to determine whether to locally store the content objects as they are opportunistically received.

Claims

1. A provider-side system for prioritizing communications of content objects over a shared communications link to subscriber-side systems, the provider-side system comprising:

a content handling subsystem configured to receive from a source external to the provider-side system and the subscriber-side systems a content object requested by a requesting one of the subscriber-side systems;

a link scheduler subsystem configured to determine a scheduler score for the received content object according to a set of link-level scalars;

a storage manager subsystem configured to determine a storage score for the received content object according to a set of storage-level scalars; and

a communications subsystem configured to transmit the received content object with the storage score over the shared communications link to the requesting one of the subscriber-side systems after a delay period that corresponds to the scheduler score,

wherein the scheduler score comprises a sum of weighted values of the link-level scalars.

2. The provider-side system of claim 1, wherein the link-level scalars comprise two or more of the following:

a size of the received content object,

a number of past requests for the received content object received at the provider-side system,

a number of past requests for the received content object pending at the provider-side system,

a rated value of the received content object,

a number of past instances in which any of the subscriber-side systems connected to the shared communications link consumed the received content object,

a value corresponding to a history of past requests for content objects received at the provider-side system from the requesting one of the subscriber-systems, and

a value corresponding to a history of past requests for content objects from the requesting one of the subscriber-systems fulfilled by the provider-side system.

3. The provider-side system of claim 2, wherein the content handling subsystem is further configured to determine whether the received content object is delayable.

4. The provider-side system of claim 3, wherein the received content object is delayable if an express request to delay delivery of the received content object is received at the content handling subsystem from the requesting one of the subscriber-side systems.

5. The provider-side system of claim 2, wherein the content handling subsystem is further configured to determine whether the received content object is opportunistically delayable.

6. The provider-side system of claim 5, wherein the received content object is opportunistically delayable if delivery of the received content object to the requesting one of the subscriber-side systems is delayable to a later time period in which the shared communications link has or is predicted to have excess capacity.

7. The provider-side system of claim 2, wherein the communications subsystem is further configured to transmit the received content object by:

assigning the received content object to a transmission queue with other content objects in a priority order that corresponds to the scheduler score, and

transmitting the received content object from the transmission queue in accordance with the priority order.

8. The provider-side system of claim 2, wherein the communications subsystem is further configured to transmit the received content object by multicasting the received content object to a plurality of the subscriber-side systems connected to the shared communications link.

9. The provider-side system of claim 8, wherein the plurality of subscriber-side systems connected to the shared communications link comprises the requesting one of the subscriber-side systems.

10. The provider-side system of claim 1, wherein the link-level scalars comprise two or more of the following:

a size of the received content object,

a number of past requests for the received content object received at the provider-side system,

a number of past requests for the received content object pending at the provider-side system,

a rated value of the received content object,

a number of past instances in which any of the subscriber-side systems connected to the shared communications link consumed the received content object,

a value corresponding to a history of past requests for content objects received at the provider-side system from the requesting one of the subscriber-systems, and

a value corresponding to a history of past requests for content objects from the requesting one of the subscriber-systems fulfilled by the provider-side system.

11. The provider-side system of claim 1, wherein the storage score comprises a sum of weighted values of the storage-level scalars.

12. The provider-side system of claim 11, wherein the storage-level scalars comprise one or more of the following:

a size of the received content object,

a predicted likelihood that one or more of the subscriber-side systems connected to the shared communications link will engage with the received content object, and

a popularity of the received content object.

13. A method of prioritizing communications of content objects over a shared communications link from a provider-side system to subscriber-side systems, the method comprising:

receiving at the provider-side system from a source external to the provider-side system and the subscriber-side systems a content object requested by a requesting one of the subscriber-side systems;

determining at the provider-side system a scheduler score for the received content object according to a set of link-level scalars;

determining at the provider-side system a storage score for the received content object according to a set of storage-level scalars; and

transmitting the received content object with the storage score from the provider-side system over the shared communications link to the requesting one of the subscriber-side systems after a delay period that corresponds to the scheduler score,

wherein the scheduler score comprises a sum of weighted values of the link-level scalars.

14. The method of claim 13, wherein the link-level scalars comprise two or more of the following:

a size of the received content object,

a number of past requests for the received content object received at the provider-side system,

a number of past requests for the received content object pending at the provider-side system,

a rated value of the received content object,

a number of past instances in which any of the subscriber-side systems connected to the shared communications link consumed the received content object,

a value corresponding to a history of past requests for content objects received at the provider-side system from the requesting one of the subscriber-systems, and

a value corresponding to a history of past requests for content objects from the requesting one of the subscriber-systems fulfilled by the provider-side system.

15. The method of claim 14 further comprising determining at the provider-side system whether the received content object is delayable.

16. The method of claim 15, wherein the received content object is delayable if an express request to delay delivery of the received content object is received at the provider-side system from the requesting one of the subscriber-side systems.

17. The method of claim 15 further comprising determining at the provider-side system whether the received content object is opportunistically delayable.

18. The method of claim 17, wherein the received content object is opportunistically delayable if delivery of the received content object to the requesting one of the subscriber-side systems is delayable to a subsequent time period in which the shared communications link has excess capacity.

19. The method of claim 14, wherein the transmitting comprises:

assigning the received content object to a transmission queue in the provider-side system with other content objects in a priority order that corresponds to the scheduler score, and

transmitting the received content object from the transmission queue in accordance with the priority order.

20. The method of claim 14, wherein the transmitting comprises multicasting the received content object to a plurality of the subscriber-side systems connected to the shared communications link.

21. The method of claim 20, wherein the plurality of subscriber-side systems connected to the shared communications link comprises the requesting one of the subscriber-side systems.

22. The method of claim 13, wherein the link-level scalars comprise two or more of the following:

a size of the received content object,

a number of past requests for the received content object received at the provider-side system,

a number of past requests for the received content object pending at the provider-side system,

a rated value of the received content object,

a number of past instances in which any of the subscriber-side systems connected to the shared communications link consumed the received content object,

a value corresponding to a history of past requests for content objects received at the provider-side system from the requesting one of the subscriber-systems, and

a value corresponding to a history of past requests for content objects from the requesting one of the subscriber-systems fulfilled by the provider-side system.

23. A method of prioritizing communications of content objects over a shared communications link from a provider-side system to subscriber-side systems, the method comprising:

receiving at the provider-side system from a source external to the provider-side system and the subscriber-side systems a content object requested by a requesting one of the subscriber-side systems;

determining at the provider-side system a scheduler score for the received content object according to a set of link-level scalars;

determining at the provider-side system a storage score for the received content object according to a set of storage-level scalars; and

transmitting the received content object with the storage score from the provider-side system over the shared communications link to the requesting one of the subscriber-side systems after a delay period that corresponds to the scheduler score,

wherein the storage score comprises a sum of weighted values of the storage-level scalars.

24. The method of claim 23, wherein the storage-level scalars comprise one or more of the following:

a size of the received content object,

a predicted likelihood that one or more of the subscriber-side systems connected to the shared communications link will engage with the received content object, and

a popularity of the received content object.