Method for processing requests and server device processing requests

Patent metadata

Field	Value
Publication number	US-10084882-B2
Application number	US-201514630468-A
Country	US
Kind code	B2
Filing date	Feb 24, 2015
Priority date	Feb 27, 2014
Publication date	Sep 25, 2018
Grant date	Sep 25, 2018

Abstract

The invention relates to a server and a method for processing requests when several requests compete within the same connection having fixed resources. Conventionally, a priority scheme provides priority values for a priority parameter that express priorities relatively to the priorities of other requests, meaning that a relative allocation of resources is obtained for each request. To achieve a better control on the server by the client, the invention provides specific possible values for the priority parameter that correspond to respective processing profiles. Each processing profile represents specific server behavior for resources allocation, by defining a predefined amount of resources. Thus, the client may choose between using the specific possible values to control the exact amount of resources that will be allocated by the server to process some specific requests, and using the other possible values that correspond to a relative allocation of resources as already done in known techniques.

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 and the same connection established with the client device;
receiving, from the client device, a priority parameter value associated with at least one designated request of the received requests;
allocating resources of the server device for processing one or more target requests of the received requests based on the priority parameter value; and
processing simultaneously the target requests using the allocated resources;

wherein, for each of the target requests,
if the received priority parameter value belongs to a first subset of possible values for the priority parameter, the server device allocates, independently to other priority parameter values associated with other received requests for processing the target request, a predefined amount of resources that is specific to the received priority parameter value; and
if the received priority parameter value belongs to a second subset of possible values for the priority parameter, the server device allocates, for processing the target request, an amount of resources that depends on other priority parameter values associated with other received requests.

2. The method of claim 1 , wherein one possible value of the first subset used to allocate an amount of resources independently to other priority parameter values associated with other received requests, defines an amount of zero resource for allocation to the processing of the target request considered, and if received priority value associated with the target request considered equals the one possible value, the processing of the target request or the quests is paused.

3. The method of claim 2 , wherein if the processing of the target request considered is paused, the method further comprises resuming the processing of the target request or requests upon occurrence of an event triggering the release of the predefined amount of allocated resources.

4. The method of claim 3 , wherein the processing of the target request or requests is resumed upon occurrence of a release triggering event, the target request or requests being assigned, when resuming, priority parameter value or values associated with them just before they were paused.

5. The method of claim 1 , wherein one possible value of the first subset defines a predefined amount equal to all the resources available at the server device for allocation to the processing of the target request or requests.

6. The method of claim 5 , wherein the received priority parameter value equals the one possible value so as to process only the target request or requests with all the resources allocated, thereby suspending the processing of other requests; and the method further comprises, upon occurrence of an event triggering the release of the predefined amount of allocated resources, resuming the processing of the other requests based on priority parameter values associated with them just before they were suspended.

7. The method of claim 1 , wherein one possible value of the first subset defines a predefined amount of resources that is relative to resources available at the server device, for allocation to the processing of the target request.

8. The method of claim 1 , wherein the at least one target request includes all the requests received from the client device within the connection.

9. The method of claim 1 , wherein the at least one target request includes all the requests received from the client device within the connection except the at least one designated request.

10. The method of claim 1 , wherein the at least one target request is the at least one designated request.

11. The method of claim 1 , wherein the at least one target request includes all the requests received from the client device within the connection that are associated with respective priority parameter values that are all above or all below a predefined priority threshold.

12. The method of claim 1 , further comprising allocating first the predefined amounts of resources to the target requests for which a priority parameter value belonging to the first subset has been received, and then sharing the remaining resources of the server device between the remaining received requests from which a priority parameter value belonging to the second subset has been received.

13. A server device in a communication network, comprising:
at least one predefined processing profile which associates a predefined amount of resources of the server device with a specific priority parameter value;
a receiving module configured to receive requests from a client device within one and the same connection established with the client device and to receive, from the client device, a priority parameter value associated with at least one designated request of the received requests;
a resource allocating module configured to allocate resources of the server device for processing one or more target requests of the received requests based on the received priority parameter value; and
a processor to process simultaneously the target requests using the allocated resources for each of the target requests;
wherein the resource allocating module is configured:
if the received priority parameter value belongs to a first subset of possible values for the priority parameter, to determine a predefined processing profile based on the received priority parameter value and to allocate independently to other priority parameter values associated with other received requests, for processing the target request, the predefined amount of resources corresponding to the determined predefined processing profile; and
if the received priority parameter value belongs to a second subset of possible values for the priority parameter, to allocate, for processing the target request, an amount of resources that depends on other priority parameter values associated with other received requests.

14. The server device of claim 13 , wherein one predefined processing profile associated with one possible value of the first subset used to allocate an amount of resources independently to other priority parameter values associated with other received requests, defines an amount of zero resource for allocation to the processing of the target request considered, and if the received priority parameter value associated with the target request considered equals the one possible value, the processing of the target request or requests is paused.

15. The server device of claim 14 , wherein the processing of the target request or requests upon occurrence of an event triggering the release of the predefined amount of allocated resources is resume if the processing of the target request considered is paused.

16. The server device of claim 15 , configured to store in memory priority parameter value or values associated with the target request or requests just before the latter are paused, so that the processing of the target request or requests is resumed upon occurrence of a release triggering event, the target request or requests being assigned, when resuming, their corresponding stored priority parameter value or values.

17. The server device of claim 13 , wherein one predefined processing profile associated with one possible value of the first subset defines an amount equal to all the resources of the server device for allocation to the processing of the target request.

18. The server device of claim 17 , configured to process

Assignees

• Canon Kk

Inventors

• Bellessort Romain
• Ruellan Hervé
• Fablet Youenn

Classifications

• H04L47/70

  Admission control; Resource allocation · CPC title

• H04L67/322 Primary

  Electricity · mapped topic

• G06F9/50

  Allocation of resources, e.g. of the central processing unit [CPU] · CPC title

• G06F9/5038

  considering the execution order of a plurality of tasks, e.g. taking priority or time dependency constraints into consideration (scheduling strategies G06F9/4881 and subgroups) · CPC title

• G06F9/5027 Primary

  the resource being a machine, e.g. CPUs, Servers, Terminals · CPC title