Client-driven push of resources by a server device
US-2018013845-A1 · Jan 11, 2018 · US
US11201934B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-11201934-B2 |
| Application number | US-201615746745-A |
| Country | US |
| Kind code | B2 |
| Filing date | Jul 22, 2016 |
| Priority date | Jul 24, 2015 |
| Publication date | Dec 14, 2021 |
| Grant date | Dec 14, 2021 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
The present invention relates to pushing at least one resource associated with a main resource, in response to a request for this main resource. After having received a request for a main resource and obtained from the cache memory a list of at least one resource linked to the main resource, an indication being associated with the at least one resource, the indication comprising a push policy defined by an application server, the at least one resource stored in the cache memory is pushed in response to a comparison of the indication associated with the at least one resource with a recommendation comprising a preferred push policy.
Opening claim text (preview).
The invention claimed is: 1. A method for pushing at least one resource associated with a main resource, in response to a request for this main resource, the method being carried out in an intermediary component comprising a cache memory, the method comprising: receiving a request for a main resource and a recommendation comprising a preferred push policy; obtaining from the cache memory a list of at least one resource linked to the main resource; obtaining from the cache memory, an indication associated with the at least one resource, the indication comprising a push policy defined by the application server; and pushing the at least one resource stored in the cache memory in response to a comparison of the indication associated with the at least one resource with the recommendation comprising the preferred push policy, wherein the at least one resource, the link between the at least one resource and the main resource, and the indication associated with the at least one resource are stored in the cache memory, following reception from an application server in response to another request for the main resource. 2. The method of claim 1 , further comprising a step of transmitting the indication associated with the at least one resource. 3. The method of claim 1 , further comprising steps of, establishing a link between the main resource and a resource to push; and associating with the linked resource to push an indication comprising a push policy defined by an application server, enabling the selection of the resource to push as a function of a recommendation comprising a preferred push policy. 4. The method of claim 3 , further comprising a step of receiving the indication comprising a push policy defined by an application server. 5. The method of claim 4 , wherein the indication comprising a push policy defined by an application server is received from the application server, directly or indirectly. 6. The method of claim 1 , further comprising a step of transmitting the indication used to identify the at least one pushed resource. 7. The method of claim 1 , further comprising a step of selecting a subset of resources to push among a set of resources to push, the subset of resources to push being selected in response to the comparison of an item of information of the indication, different from the push policy, with the recommendation, or in response to the comparison of an item of information of the indication, different from the push policy, with an item of information of the recommendation, different from the preferred push policy. 8. The method of claim 7 , wherein the item of information of the indication is received along with this resource to push. 9. The method of claim 7 , wherein the item of information of the recommendation is received along with the request for the main resource. 10. The method of claim 1 , further comprising a step of identifying from the cache memory at least one resource as a function of an indication associated with another resource, the indication associated with the other resource comprising a push policy defined by an application server, and a step of transmitting the identified resource. 11. The method of claim 1 , wherein the indications and the recommendations are received and transmitted as header parameters. 12. A device for pushing at least one resource associated with a main resource, in response to a request for this main resource, the device comprising a cache memory and a processor configured for carrying out the steps of: receiving a request for a main resource and a recommendation comprising a preferred push policy; obtaining from the cache memory a list of at least one resource linked to the main resource; obtaining, from the cache memory, an indication associated with the at least one resource, the indication comprising a push policy defined by the application server; and pushing the at least one resource stored in the cache memory in response to a comparison of the indication associated with the at least one resource with the recommendation comprising the preferred push policy, wherein the at least one resource, the link between the at least one resource and the main resource, and the indication associated with the at least one resource are stored in the cache memory, following reception from an application server in response to another request for the main resource. 13. The device of claim 12 , wherein the processor is further configured to carry out a step of transmitting the indication associated with the at least one resource. 14. The device of claim 12 , wherein the processor is further configured to carry out steps of, establishing a link between the main resource and a resource to push; and associating with the linked resource to push an indication comprising a push policy defined by an application server, enabling the selection of the resource to push as a function of a recommendation comprising a preferred push policy. 15. The device of claim 14 , wherein the processor is further configured to carry out a step of receiving the indication comprising a push policy defined by an application server. 16. The device of claim 12 , wherein the processor is further configured to carry out a step of transmitting the indication used to identify the at least one pushed resource. 17. The device of claim 12 , wherein the processor is further configured to carry out a step of selecting a subset of resources to push among a set of resources to push, the subset of resources to push being selected in response to the comparison of an item of information of the indication, different from the push policy, with the recommendation, or in response to the comparison of an item of information of the indication, different from the push policy, with an item of information of the recommendation, different from the preferred push policy. 18. The device of claim 12 , wherein the processor is further configured to carry out a step of identifying from the cache memory at least one resource as a function of an indication associated with another resource, the indication associated with the other resource comprising a push policy defined by an application server, and a step of transmitting the identified resource. 19. The device of claim 12 , wherein the processor is configured so that the indications and the recommendations are received and transmitted as header parameters.
Storing data temporarily at an intermediate stage, e.g. caching · CPC title
Push-based network services · CPC title
of access to content, e.g. by caching · CPC title
based on web technology, e.g. hypertext transfer protocol [HTTP] · CPC title
Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.