Client-driven push of resources by a server device

• US 10,348,846 B2
• Filed: 01/15/2016
• Issued: 07/09/2019
• Est. Priority Date: 01/28/2015
• Status: Active Grant

• Current Assignee: Canon Kabushiki Kaisha (Canon Inc.)
• Original Assignee: Canon Kabushiki Kaisha (Canon Inc.)
• Inventors: Denoual, Franck, Fablet, Youenn, Ruellan, Herve, Maze, Frederic, Ouedraogo, Nael
• Primary Examiner(s): Coulter, Kenneth R
• Application Number:
  US15/543,534
• Publication Number:
  US 20180013845A1
• Time in Patent Office: 1,271 Days
• Field of Search: 709203, 709245, 709217-219, 709227-229, 709230
• CPC Class Codes: H04L 47/70 Admission control; Resource allocation
• CPC Class Codes: H04L 47/83 based on usage prediction
• CPC Class Codes: H04L 65/61 for supporting one-way streaming services, e.g. Internet radio
• CPC Class Codes: H04L 65/612 for unicast
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/55 Push-based network services
• CPC Class Codes: H04L 69/22 Parsing or analysis of headers

Abstract

The present invention relates to data transmission over HTTP communication networks, for instance data streaming. A method of transmitting data between a server and a client, comprises, at the server: receiving, from the client, an HTTP request to obtain first data, wherein the HTTP request includes first data identifying information allowing identification of the first data on the server and includes one or more additional header fields containing an indication relating to pushing second data; retrieving and sending the first data to the client; and sending acknowledgment data to the client device, the acknowledgment data being representative of the indication relating to pushing second data.

Claims

1. A method of communication between a server device and a client device, comprising the following steps, at the server device:

receiving, from the client device, an HTTP request to obtain first data, wherein the HTTP request includes first data identifying information allowing identification of the first data on the server device and includes one or more additional header fields containing information for identifying second data other than the first data requested by the HTTP request, wherein the information for identifying second data allows the server device to determine whether the client device is to receive the second data;

sending the first data to the client device in response to the HTTP request received from the client device;

determining the second data on the server device, using only the one or more additional header fields, the second data being related to the first data according to a reference file; and

pushing, to the client device, using the push feature of HTTP/2, the second data so determined using the one or more additional header fields contained in the HTTP request received from the client device to obtain the first data.

2. The method of claim 1, further comprising:

sending a push promise message to announce the push of the second data to the client device and/or pushing the second data to the client device.

3. The method of claim 1, further comprising:

sending acknowledgment data to the client device before pushing the second data, the acknowledgement data being representative of second data identifying information used to determine the second data to be pushed to the client device.

4. The method of claim 3, wherein the acknowledgement data are representative of a push policy driving the push of the second data.

5. The method of claim 3, wherein the second data identifying information within the HTTP request comprises a list including at least two different push policies driving different ways of pushing second data.

6. The method of claim 3, wherein the acknowledgment data contain second data identifying information being different from the second data identifying information within the HTTP request.

7. The method of claim 4, wherein the acknowledgment data comprise one of the at least two different push policies for pushing second data, the one of the at least two different push policies for pushing second data being used to identify the second data to be pushed to the client device.

8. The method of claim 1, wherein the second data identifying information is associated with a type of data of the second data, the type of data comprising a description data type or a content data type, the second data belonging to content data or to description data.

9. The method according to claim 1, wherein the second data identifying information within the HTTP request comprises at least one unique identifier, the at least one unique identifier being representative of directives for pushing second data and of identification of the second data to be pushed or being representative of directives for not pushing second data.

10. The method according to claim 1, wherein the one or more additional header fields are one or more optional header fields.

11. The method according to claim 1, wherein the first and second data identifying information within the HTTP request include first and second uniform resource identifiers, URIs, respectively.

12. The method according to claim 11, wherein the one or more optional header fields include at least one construction rule to generate the second URI from the content of the HTTP request.

13. The method according to claim 11, wherein the one or more optional header fields include varying-part information and substitution information, the varying-part information identifying at least one varying subpart in a reference URI and the substitution information including at least one substituting value to replace the varying subpart identified in the reference URI to define the second URI or URIs.

14. The method of claim 1, wherein the second data identifying information for identifying the second data is determined in the determining step by using the one or more additional header fields contained in the HTTP request from the client device.

15. A non-transitory computer-readable storage medium storing instructions of a computer program which, when loaded and executed by a microprocessor or computer system in a device, causes the device to carry out the method according to claim 1.

16. A method of communication between a server device and a client device, comprising the following steps, at the client device:

identifying first data to be requested to the server device;

generating an HTTP request to obtain the first data, wherein the HTTP request includes first data identifying information to be used by the server device to identify the first data on the server device and includes one or more additional header fields containing an information item for the server device related to whether to push, using the push feature of HTTP/2, data related to the first data according to a reference file or not to push the data, wherein the information item allows the server device to determine whether the client device is to receive the data related to the first data;

sending the HTTP request to the server device to obtain the first data, the HTTP request including the one or more additional header fields containing the information item related to whether to push data or not to push data; and

in response to sending the HTTP request, receiving the first data from the server device.

17. A non-transitory computer-readable storage medium storing instructions of a computer program which, when loaded and executed by a microprocessor or computer system in a device, causes the device to carry out the method according to claim 16.

18. A method of communication between a server device and a client device, comprising the following steps, at the client device:

generating an HTTP request to obtain first data, wherein the HTTP request includes a first optional header field comprising one or more filtering parameters, wherein the one or more filtering parameters allows the server device to determine whether the client device is to receive second data;

sending the HTTP request including the first optional header field, to the server device to obtain the first data and to drive the server device to push, according to the filtering parameters and using the push feature of HTTP/2, the second data referenced in the first data obtained based on the HTTP request.

19. The method of claim 18, wherein the one or more filtering parameters:

define a resource type; and

the resource type or types include one or more types from an application type, a text type, an image type, a video type, an audio type;

or

identify one or more groups of data using identifiers of elements in a DASH media presentation description;

or

are defined in the first optional header field using time ranges identifying subpart of the first data to be obtained based on the HTTP request.

20. A non-transitory computer-readable storage medium storing instructions of a computer program which, when loaded and executed by a microprocessor or computer system in a device, causes the device to carry out the method according to claim 18.

21. A server device for communicating with a client device, the server device comprising:

a receiving unit for receiving from the client device, an HTTP request to obtain first data, wherein the HTTP request includes first data identifying information allowing identification of the first data on the service device and includes one or more additional header fields containing information for identifying second data other than the first data requested by the HTTP request, wherein the information for identifying second data allows the server device to determine whether the client device is to receive the second data;

a sending unit for sending the first data to the client device in response to the HTTP request received from the client device;

a determining unit for determining the second data on the server device, using the one or more additional header fields, the second data being related to the first data according to a reference file; and

a pushing unit for pushing to the client device, using the push feature of HTTP/2, the second data so determined using the one or more additional header fields contained in the HTTP request received from the client device to obtain the first data.

22. A client device for communicating with a server device, the client device comprising:

an identifying unit for identifying first data to be requested to the server device;

a generating unit for generating an HTTP request to obtain the first data, wherein the HTTP request includes first data identifying information to be used by the server device to identify the first data on the server device and includes one or more additional header fields containing an information item for the server device related to whether to push, using the push feature of HTTP/2, data related to the first data according to a reference file or not to push the data, wherein the information item allows the server device to determine whether the client device is to receive the data related to the first data;

a sending unit for sending the HTTP request to the server device to obtain the first data, the HTTP request including the one or more additional header fields containing the information item related to whether to push data or not to push data; and

in response to sending the HTTP request, receiving the first data from the server device.

23. A client device for communicating with a server device, the client device comprising:

a generating unit for generating an HTTP request to obtain first data, wherein the HTTP request includes a first optional header field comprising one or more filtering parameters, wherein the one or more filtering parameters allows the server device to determine whether the client device is to receive second data;

a sending unit for sending the HTTP request including the first optional header field, to the server device to obtain the first data and to drive the server device to push, according to the filtering parameters and using the push feature of HTTP/2, the second data referenced in the first data obtained based on the HTTP request.