Method and device for processing web requests

Patent metadata

Field	Value
Publication number	US-10075501-B2
Application number	US-201514728865-A
Country	US
Kind code	B2
Filing date	Jun 2, 2015
Priority date	Jun 4, 2014
Publication date	Sep 11, 2018
Grant date	Sep 11, 2018

Abstract

The invention relates to a device and a method for processing requests. In particular, the invention concerns building a dependency tree between the requests received from the client device for prioritizing the processing of the requests by the server device; maintaining a list of requests of the dependency tree in their removal order from the dependency tree while the server device is prioritizing the processing of the requests; and removing a selection of requests from the dependency tree wherein the selection is based on the order of requests in the list.

First claim

The invention claimed is:

1. A method of processing requests in a server device, comprising, at the server device, the steps of:
receiving requests from a client device within one connection established with the client device;
receiving priority parameter values, associated with the received requests, indicative of the relative order at which the client device wishes the server device to process the requests;
building a dependency tree between the received requests using the associated priority parameter values for prioritizing the processing of the requests by the server device;
maintaining a list of requests of the dependency tree in their removal order from the dependency tree while the server device is prioritizing the processing of the requests;
removing a selection of requests from the dependency tree wherein the selection is based on the order of requests in the list;
assigning relevance values to the requests of the list indicative of the order of removal of the requests from the dependency tree, where requests with lowest relevance values are to be removed first; and
wherein the built dependency tree includes one or more virtual nodes each being associated with a stream identifier and without being associated with any of the requests from the client device, the stream identifier being already referenced in a frame received from the client device, and the method further comprising assigning relevance values to one of the virtual nodes.

2. The method of claim 1 , wherein the maintaining comprises updating the order of removal of requests in the list based on at least one predefined rule.

3. The method of claim 2 , wherein a predefined rule is to keep the order of removal of a request, that is parent of a plurality of requests in the dependency tree, following the order of removals of its descendants.

4. The method of claim 1 , wherein the prioritizing the requests processing is triggered by the receiving of new priority parameter values from the client device.

5. The method of claim 1 , further comprising processing the received requests in an order that takes into account the tree of dependencies between the requests.

6. The method of claim 5 , wherein each request is associated with a stream identified by a stream identifier, and wherein a closed stream corresponds to a processed request.

7. The method of claim 6 , wherein the list of requests contains only processed requests of the dependency tree.

8. The method of claim 7 , wherein the maintaining of the list comprises the steps of:
creating a list containing all processed requests of the dependency tree; and
ordering the list in the removal order of the requests according to at least one rule.

9. The method of claim 8 , wherein the at least one rule is the requests creation order and wherein the ordering causes the less recently created requests to be removed first.

10. The method of claim 9 , wherein the application of the ordering step is performed each time a newly created descendant request is attached to the parent request.

11. The method of claim 8 , wherein the at least one rule is the requests usage order and wherein the ordering causes the less recently used requests to be removed first.

12. The method of claim 6 , wherein the building of the dependency tree comprises:
obtaining identifiers of the streams associated with the received requests; and
storing in memory the stream identifiers along with priority information linking hierarchically the stream identifiers.

13. The method of claim 12 , wherein the removing of the selection of requests comprises deleting from memory the corresponding stream identifiers and updating the hierarchical relationship between the remaining requests of the dependency tree.

14. The method of claim 12 , wherein the building of the dependency tree comprises:
obtaining identifiers of idle and/or virtual streams not associated with the received requests; and
storing in memory the identifiers of the idle and/or virtual streams and the identifiers of the streams associated with the received requests along with priority information linking hierarchically the identifiers.

15. The method of claim 1 , further comprising deciding on whether to keep in or remove from the dependency tree identifier(s) of one or more already processed requests, and notifying the client device about the result of the deciding.

16. The method of claim 15 , further comprising: receiving from the client device an indication of first type containing an identifier of a request or of a corresponding stream the client device wishes the service device to keep in the dependency tree.

17. The method of claim 15 , further comprising: receiving from the client device an indication of second type comprising an identifier of a request or of a corresponding stream the client device wishes the service device to remove from the dependency tree.

18. The method of claim 1 , further comprising assigning relevance values to the requests of the dependency tree, according to assignment rules, for selecting requests to be removed from the dependency tree, wherein a request that is parent of a plurality of requests in the dependency tree is assigned a relevance value greater than or equal to the highest relevance value previously assigned to one of its decedents, and
removing a selection of processed requests from the dependency tree based on the assigned relevance values where requests with lowest relevance values are removed first.

19. The method of claim 18 , wherein the assigning of relevance values comprises:
assigning sequence numbers to the received requests; and
updating the sequence numbers according to the assignment rules thereby obtaining the relevance values.

20. The method of claim 18 , wherein the assigning of relevance values comprises:
assigning reception timestamps to the received requests; and
updating the timestamps according to the assignment rules thereby obtaining the relevance values.

21. The method of claim 18 , wherein if a new request is inserted in the dependency tree between a parent request and the child requests of the parent request, thereby the new request becoming the new parent request of the child requests, the relevance value assigned to the new parent request is higher than the relevance values of the child requests.

22. A method of sending requests to a server device, comprising, at a client device, the steps of:
sending requests to the server device within one connection established with the server device;
sending priority parameter values, associated with the sent requests, indicative of the relative order at which the client device wishes the server device to process the requests;
building a dependency tree between the sent requests using the associated priority parameter values for prioritizing the processing of the requests by the server device;
maintaining a list of requests of the dependency tree in their removal order from the dependency tree;
removing a selection of requests from the dependency tree wherein the selection is based on the order of requests in the list;
assigning relevance values to the requests of the list indicative of the order of removal of the requests from the dependency tree, where requests with lowest relevance values are to be removed first;
wherein the priority parameter values sent to the server device are associated with sent requests that still belong to the maintained list after the removing step is executed; and
wherein the

Assignees

• Canon Kk

Inventors

• Ruellan Hervé
• Fablet Youenn
• Bellessort Romain

Classifications

• H04L67/42

  Electricity · mapped topic

• G06F9/48

  Program initiating; Program switching, e.g. by interrupt · CPC title

• H04L67/02 Primary

  based on web technology, e.g. hypertext transfer protocol [HTTP] · CPC title

• H04L69/03

  Protocol definition or specification  (protocol conformance testing H04L1/244) · CPC title

• H04L67/60 Primary

  Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources (admission control or resource allocation H04L47/70) · CPC title