US 10,951,671 B2Granted

Content set based deltacasting

AssigneeViaSat, Inc.

InventorsWilliam B. Sebastian, Peter Lepeska

Life of this patent

Estimating the term…

Loading patent…

Abstract

Methods, apparatuses, and systems are provided for improving utilization of the satellite communications system through various “deltacasting” techniques for handling content sets (e.g., feeds or websites). Embodiments operate in a client-server context, including a server optimizer, a client optimizer, and, in some embodiments, a pre-positioning client. Within this client-server context, content sets are multicast (e.g., anticipatorily pre-positioned in a local dictionary) to end users of the communications system and are handled at the content set level, according to set-level metadata and/or user preferences. In some embodiments, when locally stored information from the content sets is requested by a user, deltacasting techniques are used to generate fingerprints for use in identifying and exploit multicasting and/or other opportunities for increased utilization of links of the communications system.

Claims15

Dependent claims

A method for receipt of multicast data over a communications system having a communications path between a server side of the communications system and a plurality of clients, the communications path comprising a shared forward link over which bandwidth resources are shared during a multicast communication, the method comprising:

generating a request at a requesting client of the plurality of clients for a content object, the content object being part of a content set having a plurality of content objects identified by one of a plurality of content set identifiers, the content set having a set-level profile;
intercepting the request with a client optimizer at the requesting device to identify a content set corresponding to the content set identifier of the requested object;
determining at the client optimizer if data needed to generate the requested object is stored locally at the requesting client by determining whether the content object is presently stored locally at the requesting client as a function of the content set identifier of the identified content set;
in response to determining the data needed to generate the requested object is not stored locally at the requesting client, communicating the request to the server side of the communication system, the request for the requested object being identifiable by the server side as relating to the content set identified by the one of the plurality of content set identifiers for association of a data block at the server side with the content set identifier of an identified content set relating to the requested object;
receiving at the requesting client the data block associated with the identified content set in a multicast communication received by the requesting client and the plurality of clients;
and
determining by the client optimizer whether the requesting client of the plurality of clients accepts the data block from the multicast communication over the communications path to store the data block at the requesting client based on the content set identifier.

4 more elements

A client system for receipt of multicast data over a communications system having a communications path between a server side of the communications system and a plurality of clients, the communications path comprising a shared forward link over which bandwidth resources are shared during a multicast communication, the client system comprising:

a memory;
a processor;
a client optimizer module, stored in the memory at the client side of the communications system, the client optimizer module, when executed, causing the processor to:
intercept a request for a content object, the content object being part of a content set having a plurality of content objects identified by one of a plurality of content set identifiers, the content set having a set-level profile;
identify a content set corresponding to the content set identifier of the requested object;
determining if data needed to generate the requested object is stored locally at the requesting client by determining whether the content object is presently stored locally at the requesting client as a function of the content set identifier of the identified content set;
in response to determining the data needed to generate the requested object is not stored locally at the requesting client, communicate the request to the server side of the communication system, the request for the requested object being identifiable by the server side as relating to the content set identified by the one of the plurality of content set identifiers for association of a data block at the server side with the content set identifier of an identified content set relating to the requested object;
receive the data block associated with the identified content set in a multicast communication;
and
determine whether the requesting client of the plurality of clients accepts the data block from the multicast communication over the communications path to store the data block at the requesting client based on the content set identifier.

7 more elements

Dependencies are inferred from the claim text.

Facts

Application: 16/723,851Filed 20 Dec 2019 · continuation
Priority: 13 Jan 2009
Published: US 2020/0322402 A18 Oct 2020
Granted: 16 Mar 2021
Term ends: Not estimatedThe source records don’t support an estimate.

Classification14 codes

H04L 12/1859
For broadcast or conference , e.g. multicast: adapted to provide push services, e.g. data channels
H04B 7/185
Active relay systems: space-based or airborne stations; Stations for satellite systems
H04L 12/1863
For broadcast or conference , e.g. multicast: comprising mechanisms for improved reliability, e.g. status reports
H04L 12/1881
For broadcast or conference , e.g. multicast: with schedule organisation, e.g. priority, sequence management

Family

Application61/144,363Us provisional application · filed 13 Jan 2009
Application61/170,359Us provisional application · filed 17 Apr 2009
Application12/685,729Parent of this division · filed 12 Jan 2010
Application13/919,888Parent of this continuation · filed 17 Jun 2013
US 8,489,672 B2Parent of this division · filed 16 Jul 2013
Application16/247,702Parent of this continuation · filed 15 Jan 2019
US 10,187,436 B2Parent of this continuation · filed 22 Jan 2019
US 2020/0322402 A1Pre-grant publication · published 8 Oct 2020
US 10,536,495 B2Parent of this continuation
Application13/919,888Parent of this division
US 2010/0179986 A1Published application
US 2013/0282796 A1Published application
US 2019/0306210 A1Published application
US 10,951,671 B2This patent

From the US filing history. Foreign family members aren’t listed.