Method, system and server device for transmitting a digital resource in a client-server communication system

• US 20130246583A1
• Filed: 03/11/2013
• Published: 09/19/2013
• Est. Priority Date: 03/14/2012
• Status: Active Grant

• Current Assignee: Canon Kabushiki Kaisha (Canon Inc.)
• Original Assignee: Canon Kabushiki Kaisha (Canon Inc.)
• Inventors: BELLESSORT, ROMAIN, FABLET, YOUENN, RUELLAN, Herv
• Granted Patent: US 9,781,222 B2
• Time in Patent Office: Days
• US Class Current: 709/219
• CPC Class Codes: H04L 67/55 Push-based network services

Abstract

The present invention relates to transmitting a digital resource in a client-server communication system. A disclosed method comprises at a main server device: receiving a request for a main resource from a client device; determining at least one missing secondary resource, wherein the at least one missing secondary resource is at least one resource associated with said requested main resource and missing at the main server device; and requesting a secondary server device to push the at least one missing secondary resource to the client device. Thanks to the push initiated by the main server device, the secondary resources required by the main resource become available at the client device before the latter discovers that they are required to exploit or display the main resource.

Claims

1. A method of transmitting a digital resource in a client-server communication system, the method comprising, at a main server device:

receiving a request for a main resource from a client device;

determining at least one missing secondary resource, wherein the at least one missing secondary resource is at least one resource associated with said requested main resource and missing at the server device;

requesting a secondary server device to push the at least one missing secondary resource to the client device.

2. The method of claim 1, further comprising, at the main server device, transmitting the requested main resource to the client device in response to the request from the client device;

wherein requesting the secondary server device to push the at least one missing secondary resource is prior to transmitting the requested main resource to the client device.

3. The method of claim 1, wherein the at least one missing secondary resource is hosted by the requested secondary server device.

4. The method of claim 1, further comprising at the main server device:

receiving from the secondary server device a notification that the at least one missing secondary resource has been pushed to the client device in response to the request sent by the main server device.

5. The method of claim 4, wherein the requested main resource is sent by the main server device to the requesting client device after receiving the notifications from the requested secondary server devices for all the requests sent by the main server device.

6. The method of claim 1, further comprising, at the main server device, identifying at least one hosted secondary resource that is associated with the requested main resource and hosted by the main server device;

and pushing the at least one identified hosted secondary resource to the client device.

7. The method of claim 1, further comprises determining whether a secondary server device has capabilities to operate as a push server to push a resource to the client device.

8. The method of claim 7, wherein determining whether a secondary server device has capabilities to operate as a push server comprises determining whether a network connection between the secondary server device and the client device is already established or the secondary server device is authorized to establish a new network connection with the client device.

9. The method of claim 7, wherein determining whether a secondary server device has capabilities to operate as a push server to push a resource to the client device is performed by the main server device prior to requesting the secondary server device to push the at least one missing secondary resource to the client device in case of positive determination.

10. The method of claim 7, wherein in case of negative determination, the main server device requests the at least one missing secondary resource from the secondary server device and pushes the at least one missing secondary resource received from the secondary server device to the client device.

11. The method of claim 7, further comprising, in case of negative determination, determining at least one other server device trusted by the client device and/or the secondary server device and requesting the trusted server device to push the at least one missing secondary resource to the client device.

12. The method of claim 11, wherein the trusted server device has a network connection already established with the client device or is authorized to establish, on its own initiative, a new network connection with the client device.

13. The method of claim 11, wherein the trusted server device requests the at least one missing secondary resource from the secondary server device.

14. The method of claim 1, wherein the secondary server device determines whether it has a network connection already established with the client device or it is authorized to establish a new network connection with the client device;

wherein, in case of positive determination, the secondary server device pushes the at least one missing secondary resource to the client device over the network connection already established or the new network connection once established.

15. The method of claim 14, wherein, in case of negative determination, the secondary server device requests a trusted server device to push the at least one missing secondary resource to the client device, the trusted server device having a network connection already established with the client device or being authorized to establish, on its own initiative, a new network connection with the client device.

16. The method of claim 15, wherein the request from the secondary server device comprises the missing secondary resource to be pushed.

17. The method of claim 15, wherein the trusted server device is the main server device.

18. The method of claim 1, wherein a secondary resource associated with the main resource is a resource referenced within the main resource.

19. The method of claim 1, wherein a secondary resource associated with the main resource is a resource that is statistically requested after the main resource by the same client device.

20. The method of claim 1, wherein a secondary resource associated with the main resource is a resource requested by a script embedded within the main resource.

21. The method of claim 1, wherein determining at least one missing secondary resource that is hosted by a secondary server device comprises building a secondary server list including secondary server devices hosting missing secondary resources associated with the main resource, and sending the secondary server list to the client device.

22. The method of claim 1, wherein the client device comprises a cache memory configured to store requested main resources and secondary resources already received, and the client device sends a list of cached resources to the main server device and to secondary server devices.

23. The method of claim 1, wherein determining at least one missing secondary resource that is hosted by a secondary server device comprises determining, by the main server device, all the missing secondary resources hosted by the same secondary server device and sending, by the main server device, a single request to the secondary server device to push all the missing secondary resources that it hosts.

24. The method of claim 1, further comprising, at the main server device, transmitting a token together with the requested main resource to the client device and inserting the same token in the request to the secondary server device to push the at least one missing secondary resource to the client device.

25. The method of claim 24, wherein the secondary server device pushes the at least one missing secondary resource to the client device together with the token included in the request received from the main server device.

26. A server device in a client-server communication system, comprising:

a communication interface for receiving a request for a main resource from a client device;

a missing resource module configured to determine at least one missing secondary resource, wherein the at least one missing secondary resource is at least one resource associated with said requested main resource and missing at the server device;

a requesting module for requesting a secondary server device to push the at least one missing secondary resource to the client device.

27. A client-server communication system comprising:

a server device according to claim 26;

a client device configured to request a main resource from the server device;

at least one secondary server device.

28. A non-transitory computer-readable medium storing a program which, when executed by a microprocessor or computer system in a server device, causes the server device to perform the steps of:

receiving a request for a main resource from a client device;

determining at least one missing secondary resource, wherein the at least one missing secondary resource is at least one resource associated with said requested main resource and missing at the server device;

requesting a secondary server device to push the at least one missing secondary resource to the client device.