CN104022970A - Web service QoS step control method and Web service container - Google Patents

Abstract

The invention discloses a Web service QoS hierarchical control method and a Web service container, wherein the method includes: receiving a service request sent by a user; determining the resource quantity allocated for the service under each QoS hierarchical control strategy; Under the control strategy, the first resource weight obtained by the service is the ratio of the resource quantity to the total resource; the second resource weight obtained by the service is determined, and the second resource weight is the first resource weight and The weighted sum of the influence proportions of each QoS hierarchical control strategy on the service; perform QoS hierarchical control on the service according to the second resource weight. The invention supports multiple QoS hierarchical control strategies, can use different QoS hierarchical control strategies according to different application requirements, effectively optimizes the processing capability of the service container, and ensures the service quality.

Description

Web service QoS hierarchical control method and Web service container

technical field

The invention relates to the technical field of computer networks, in particular to a Web service QoS hierarchical control method and a Web service container.

Background technique

In the service-oriented architecture (Service Oriented Architecture, hereinafter referred to as SOA), service providers need to provide different services for different service consumers, and at the same time meet the needs of service consumers as much as possible to obtain higher benefits . This requires a Web service container that supports hierarchical control of Quality of Service (QoS) in order to optimize the processing capability of the Web service container while ensuring different service QoS indicators.

Existing Web service containers are based on a single QoS hierarchical control strategy to optimize the processing capacity of service containers. For example, some QoS hierarchical control strategies are based on performance optimization. Performance parameters such as response time are used to measure the processing capacity of service containers as a hierarchical control strategy. basis; some QoS hierarchical control strategies are based on the perspective of revenue optimization, and use the revenue value obtained by successfully executing services to measure the processing capacity of service containers as the basis for hierarchical control; some QoS hierarchical control strategies are based on the perspective of resource optimization. Use the amount of system resources consumed in the process of processing service requests to measure the processing capacity of service containers as the basis for hierarchical control.

However, with the increasingly widespread application of SOA and the continuous development of Web service research, the limitations of the service container processing capacity optimization method based on a single QoS hierarchical control strategy are becoming more and more obvious. For example, the QoS hierarchical control strategy based on performance optimization, Since the service is graded only by a single performance index such as response time, it is impossible to distinguish services with the same response time; the QoS classification control strategy based on the revenue optimization perspective, because the revenue value and penalty value required by this strategy are both Artificial setting, using such indicators as the key factors of service classification leads to the realization effect of QoS hierarchical control will be greatly affected by subjective factors; QoS hierarchical control strategy based on resource optimization can reduce the energy consumption in the process of QoS hierarchical control consumption, but it is impossible to take into account both resource conservation and performance improvement at the same time.

Contents of the invention

The present invention provides a Web service QoS hierarchical control method and a Web service container, which are used to solve the problem in the prior art that the limitation of the service container processing capability optimization method based on a single QoS hierarchical control strategy becomes more and more obvious.

The present invention provides a Web service QoS hierarchical control method, including:

Receive service requests sent by users;

Determine the number of resources allocated for services under each QoS hierarchical control strategy;

Determine the first resource weight obtained by the service under each QoS hierarchical control strategy, where the first resource weight is the ratio of the number of resources to the total amount of resources;

Determining a second resource weight obtained by the service, where the second resource weight is a weighted sum of the first resource weight and the impact ratio of each QoS hierarchical control policy on the service;

Perform hierarchical QoS control on the service according to the second resource weight.

The present invention also provides a Web service container, including:

The receiving module is used to receive the service request sent by the user;

A determining module, configured to determine the amount of resources allocated for the service under each QoS hierarchical control strategy; determine the first resource weight value obtained by the service under each QoS hierarchical control strategy, and the first resource weight value is determined by The ratio of the number of resources to the total amount of resources; determine the second resource weight obtained by the service, and the second resource weight is the proportion of the impact of the first resource weight and each QoS hierarchical control strategy on the service The weighted sum of;

A control module, configured to perform QoS hierarchical control on the service according to the second resource weight.

The present invention firstly determines the resource quantity allocated for the service under each QoS hierarchical control strategy, and determines that under each QoS hierarchical control strategy, the first resource weight is the ratio of the resource quantity to the total amount of resources, and then determines The second resource weight obtained by the service is the weighted sum of the first resource weight and the impact ratio of each QoS hierarchical control policy on the service, and finally QoS is performed on the service according to the second resource weight Hierarchical control. In this way, the solution supports multiple QoS hierarchical control strategies, and can use different QoS hierarchical control strategies according to different application requirements, effectively optimizing the processing capacity of the service container and ensuring the quality of service.

Description of drawings

Fig. 1 is a schematic flow chart of Embodiment 1 of the Web service QoS hierarchical control method provided by the present invention;

FIG. 2 is a schematic flow chart of Embodiment 2 of the Web service QoS hierarchical control method provided by the present invention;

Fig. 3 is a schematic structural diagram of an embodiment of a Web service container provided by the present invention.

Detailed ways

In order to make the purpose, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments It is a part of embodiments of the present invention, but not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by persons of ordinary skill in the art without creative efforts fall within the protection scope of the present invention.

Embodiment one

As shown in Figure 1, it is a schematic flow chart of Embodiment 1 of the Web service QoS hierarchical control method provided by the present invention, which specifically includes the following steps:

S101. Receive a service request sent by a user;

It should be noted that the execution subject of this embodiment may be a Web service container, in which various services are deployed, and a user may send a service request to the Web service container through a user equipment to obtain required services.

S102. Determine the number of resources allocated for the service under each QoS hierarchical control strategy;

It should be noted that each of the QoS hierarchical control strategies includes at least two of the following strategies: performance optimization strategy, revenue optimization strategy and resource optimization strategy, to determine the amount of resources allocated for the service under each QoS hierarchical control strategy , specifically, under the following constraint conditions, a dynamic programming algorithm can be used to determine the number of resources allocated for the service; the constraint condition is: if a total of n services are deployed, and C is a constant, then each service The resource quantity W _i needs to satisfy $\underset{i=1}{\overset{\mathrm{no}}{\mathrm{\Σ}}}{W}_i=C.$

Specifically, under the constraints Next, by using the dynamic programming algorithm, the number of resources allocated to each service by the Web service container when applying each QoS hierarchical control strategy is calculated. The objective function used in the calculation process is shown in formula (1):

$\mathrm{<span\; class="notranslate">\; u</span>}<span\; class="notranslate">\; (</span>\mathrm{<span\; class="notranslate">\; i</span>}<span\; class="notranslate">\; ,</span>\mathrm{<span\; class="notranslate">\; j</span>}<span\; class="notranslate">\; )</span><span\; class="notranslate">\; =</span>\left\{\begin{array}{c}{\mathrm{<span\; class="notranslate">\; u</span>}}_{\mathrm{<span\; class="notranslate">\; i</span>}}<span\; class="notranslate">\; (</span>\mathrm{<span\; class="notranslate">\; w</span>}<span\; class="notranslate">\; )</span>\\ \mathrm{<span\; class="notranslate">\; max</span>}<span\; class="notranslate">\; \{</span>\mathrm{<span\; class="notranslate">\; u</span>}<span\; class="notranslate">\; (</span>\mathrm{<span\; class="notranslate">\; i</span>}<span\; class="notranslate">\; -</span>\mathrm{<span\; class="notranslate">\; 1</span>}<span\; class="notranslate">\; ,</span>\mathrm{<span\; class="notranslate">\; j</span>}<span\; class="notranslate">\; -</span>\mathrm{<span\; class="notranslate">\; c</span>}<span\; class="notranslate">\; )</span><span\; class="notranslate">\; +</span>{\mathrm{<span\; class="notranslate">\; u</span>}}_{\mathrm{<span\; class="notranslate">\; i</span>}}<span\; class="notranslate">\; (</span>\mathrm{<span\; class="notranslate">\; c</span>}<span\; class="notranslate">\; )</span><span\; class="notranslate">\; \}</span>\end{array}\right.<span\; class="notranslate">\; -</span><span\; class="notranslate">\; -</span><span\; class="notranslate">\; -</span><span\; class="notranslate">\; (</span>\mathrm{<span\; class="notranslate">\; 1</span>}<span\; class="notranslate">\; )</span>$

Among them, U(i,j) represents the processing capability of the Web service container when calculating the number of resources allocated for the i-th service and a total of j resources have been allocated. u _i (c) represents the processing capability of the Web service container for the i-th service when c resources are allocated to the i-th service, and W is the total amount of Web service container resources. n is the number of services deployed in the web service container. The objective function of the dynamic programming algorithm in the above formula is common to different QoS hierarchical control strategies. However, different QoS hierarchical control strategies have different u _i (c) functions when formula (1) is applied. In addition, since the dynamic programming algorithm in formula (1) is aimed at maximizing the value, when dealing with the strategy aiming at minimizing the value, it is necessary to take the reciprocal of the function value of u _i (c) and expand Multiple, such as in the resource optimization strategy, the QoS hierarchical control strategy is aimed at minimizing resource consumption. When calculating U(i,j), the value of u _i (c) can be reciprocated and multiplied by 100000. Taking the QoS hierarchical control strategy including performance optimization strategy, revenue optimization strategy and resource optimization strategy as an example, the number of resources allocated for the service under the performance optimization strategy is calculated by using the above dynamic programming algorithm, and under the revenue optimization strategy is The resource quantity allocated to the service and the resource quantity allocated to the service under the resource optimization strategy. In addition, for the same Web service container, in the case of deploying the same service, the amount of resources that the Web service container can allocate is the same when different QoS hierarchical control policies are applied.

S103. Determine the first resource weight obtained by the service under each QoS hierarchical control strategy, where the first resource weight is a ratio of the resource quantity to the total resource quantity;

It should be noted that the total amount of resources is a constant, which can be set as the total number of deployed services multiplied by the total number of elements in the service priority queue. Specifically, the total amount of resources that can be allocated in the Web service container can be measured by the number of services deployed in the Web service container, expressed as: W=n×K.

Among them, W represents the total amount of resources that can be allocated; n is the number of services deployed in the Web service container; K is a constant. When using priority queues to implement QoS hierarchical control, it is recommended to set K as the number of priorities. Taking the QoS hierarchical control strategy as an example that includes performance optimization strategy, revenue optimization strategy, and resource optimization strategy at the same time, it is calculated that the first resource weight obtained by a service under the performance optimization strategy is the resource allocated for the service under the performance optimization strategy The ratio of the quantity to the total amount of resources and the ratio of the total amount of resources, the first resource weight obtained by the service under the revenue optimization strategy is the ratio of the number of resources allocated to the service under the revenue optimization strategy to the total amount of resources and the resource The first resource weight obtained by the service under the optimization strategy is the ratio of the amount of resources allocated to the service under the resource optimization strategy to the total amount of resources.

S104. Determine a second resource weight obtained by the service, where the second resource weight is a weighted sum of the first resource weight and the impact ratio of each QoS hierarchical control policy on the service;

It should be noted that for the same service, the sum of the impact ratios of different QoS hierarchical control strategies is 1. Also, taking the QoS hierarchical control strategy including performance optimization strategy, revenue optimization strategy and resource optimization strategy as an example, assuming that the performance optimization strategy has a significant impact on The influence proportion of the service is q1, the influence proportion of the revenue optimization strategy on the service is q2, and the influence proportion of the resource optimization strategy on the service is q3, then q1+q2+q3=1, and the second resource right The value is the weighted sum of the first resource weight and the impact ratio of each QoS hierarchical control strategy on the service, assuming that the first resource weight obtained by the service under the performance optimization strategy is w1, and the service obtains under the revenue optimization strategy The first resource weight of the service is w2, and the first resource weight obtained by the service under the resource optimization strategy is w3, then the second resource weight corresponding to the service is w1×q1+w2×q2+w3×q3.

In addition, if the service request sent by the user includes a preset response time, if it is determined that the average response time of the service exceeds the preset response time, then it is determined that the second resource weight obtained by the service is the first The weighted sum of the resource weight and the proportion of impact of each QoS hierarchical control strategy on the service is multiplied by 2, which is (w1×q1+w2×q2+w3×q3)×2. Wherein, the service response time is the time interval from when the service request is received to when the service is executed and the result is returned. The average response time of a service is obtained by calculating the average response time of each invocation of the service. For service i, if the Web service container has successfully processed m _i requests for the service, and the response time of each request is t _si , then the average response time T _i of the service is calculated using the following formula (2):

${\mathrm{<span\; class="notranslate">\; T</span>}}_{\mathrm{<span\; class="notranslate">\; i</span>}}<span\; class="notranslate">\; =</span>\underset{\mathrm{<span\; class="notranslate">\; the\; si</span>}<span\; class="notranslate">\; =</span>\mathrm{<span\; class="notranslate">\; 1</span>}}{\overset{{\mathrm{<span\; class="notranslate">\; m</span>}}_{\mathrm{<span\; class="notranslate">\; i</span>}}}{\mathrm{<span\; class="notranslate">\; \&Sigma;</span>}}}{\mathrm{<span\; class="notranslate">\; t</span>}}_{\mathrm{<span\; class="notranslate">\; the\; si</span>}}<span\; class="notranslate">\; -</span><span\; class="notranslate">\; -</span><span\; class="notranslate">\; -</span><span\; class="notranslate">\; (</span>\mathrm{<span\; class="notranslate">\; 2</span>}<span\; class="notranslate">\; )</span>$

Or, if the service request sent by the user includes a preset QoS satisfaction rate, if it is determined that the actual QoS satisfaction rate of the service is less than the preset QoS satisfaction rate, then determine that the second resource weight obtained by the service is The weighted sum of the first resource weight and the proportion of influence of each QoS hierarchical control policy on the service is multiplied by 2, which is (w1×q1+w2×q2+w3×q3)×2. Wherein, the service QoS satisfaction rate of the Web service is measured by counting the percentage of service calls that are successfully executed and meet the service QoS requirements during the service call process. For service i, if the Web service container has processed m _i requests for the service, among which k _i requests are successfully executed and meet the agreed QoS requirements of the service, then the QoS satisfaction rate R _i of the service uses the following formula (3) to calculate:

${\mathrm{<span\; class="notranslate">\; R</span>}}_{\mathrm{<span\; class="notranslate">\; i</span>}}<span\; class="notranslate">\; =</span>\frac{{\mathrm{<span\; class="notranslate">\; k</span>}}_{\mathrm{<span\; class="notranslate">\; i</span>}}}{{\mathrm{<span\; class="notranslate">\; m</span>}}_{\mathrm{<span\; class="notranslate">\; i</span>}}}<span\; class="notranslate">\; -</span><span\; class="notranslate">\; -</span><span\; class="notranslate">\; -</span><span\; class="notranslate">\; (</span>\mathrm{<span\; class="notranslate">\; 3</span>}<span\; class="notranslate">\; )</span>$

Or, if the service request sent by the user includes the preset response time and the preset QoS satisfaction rate, if it is determined that the average response time of the service exceeds the preset response time and the actual QoS satisfaction rate of the service is less than the If the QoS satisfaction rate is preset, then it is determined that the second resource weight obtained by the service is the weighted sum of the first resource weight and the impact of each QoS hierarchical control strategy on the service multiplied by 2, which is (w1 ×q1+w2×q2+w3×q3)×2.

S105. Perform hierarchical QoS control on the service according to the second resource weight.

Specifically, the priority order of the services may be determined according to the second resource weight, and the operation corresponding to the service may be completed according to the priority order of the services, that is, the second resource weight may be used as a QoS hierarchical control The control parameter of the policy, using the control parameter to perform QoS hierarchical control on the service, complete the operation corresponding to the service, and return the result to the user.

In this embodiment, by determining the number of resources allocated to the service under each QoS hierarchical control policy, the first resource weight obtained by the service, the first resource weight is the ratio of the number of resources to the total amount of resources, Determine the second resource weight obtained by the service, where the second resource weight is the weighted sum of the first resource weight and the impact ratio of each QoS hierarchical control policy on the service, according to the second resource The weight performs QoS hierarchical control on the service. In this way, the solution supports multiple QoS hierarchical control strategies, and can use different QoS hierarchical control strategies according to different application requirements, effectively optimizing the processing capacity of the Web service container and ensuring the quality of service.

Embodiment two

As shown in FIG. 2 , it is a schematic flow chart of Embodiment 2 of the Web service QoS hierarchical control method provided by the present invention. On the basis of the above Embodiment 1, this embodiment determines the second resource weight obtained by the service. Afterwards, the normalization processing of the second resource weight obtained by the service is further added. Specifically include the following steps:

S201. Receive a service request sent by a user;

S202. Determine the number of resources allocated for the service under each QoS hierarchical control strategy;

S203. Determine the first resource weight obtained by the service under each QoS hierarchical control strategy, where the first resource weight is a ratio of the resource quantity to the total resource quantity;

S204. Determine a second resource weight obtained by the service, where the second resource weight is a weighted sum of the first resource weight and the impact ratio of each QoS hierarchical control policy on the service;

S205. Perform normalization processing on the second resource weight obtained by the service to obtain a normalized resource weight of the service;

Specifically, the normalized resource weight of the service may be calculated using the following formula (4):

${{\mathrm{<span\; class="notranslate">\; W</span>}}_{\mathrm{<span\; class="notranslate">\; i</span>}}}^{<span\; class="notranslate">\; \&prime;</span><span\; class="notranslate">\; \&prime;</span>}<span\; class="notranslate">\; =</span>\frac{{{\mathrm{<span\; class="notranslate">\; W</span>}}_{\mathrm{<span\; class="notranslate">\; i</span>}}}^{<span\; class="notranslate">\; \&prime;</span>}}{\underset{\mathrm{<span\; class="notranslate">\; i</span>}<span\; class="notranslate">\; =</span>\mathrm{<span\; class="notranslate">\; 1</span>}}{\overset{\mathrm{<span\; class="notranslate">\; i</span>}<span\; class="notranslate">\; =</span>\mathrm{<span\; class="notranslate">\; no</span>}}{\mathrm{<span\; class="notranslate">\; \&Sigma;</span>}}}{{\mathrm{<span\; class="notranslate">\; W</span>}}_{\mathrm{<span\; class="notranslate">\; i</span>}}}^{<span\; class="notranslate">\; \&prime;</span>}}<span\; class="notranslate">\; -</span><span\; class="notranslate">\; -</span><span\; class="notranslate">\; -</span><span\; class="notranslate">\; (</span>\mathrm{<span\; class="notranslate">\; 4</span>}<span\; class="notranslate">\; )</span>$

Among them, W _i ″ is the normalized resource weight obtained by the i-th service, and W _i ' is the second resource weight obtained by the i-th service, which is an unnormalized second resource weight; n The number of services deployed in the web service container.

S206. Perform QoS hierarchical control on the service according to the normalized resource weight of the service.

Normalize the second resource weights of each service in the Web service container to obtain the normalized resource weights obtained by the services in the Web service container, and calculate the normalized resource weights of the services according to the normalized resource weights of the services Perform hierarchical QoS control. Specifically, the priority order of the service may be determined according to the normalized resource weight of the service, and the operation corresponding to the service may be completed according to the priority order of the service, that is, the normalized resource weight of the service The weight is used as a control parameter of the QoS hierarchical control strategy, and the control parameter is used to perform QoS hierarchical control on the service, complete the operation corresponding to the service, and return the result to the user.

In addition, for the detailed description of steps S201 to S204 in this embodiment, refer to the description of the relevant steps in Embodiment 1, which will not be repeated here.

In this embodiment, by determining the number of resources allocated to the service under each QoS hierarchical control policy, the first resource weight obtained by the service, the first resource weight is the ratio of the number of resources to the total amount of resources, Determining a second resource weight obtained by the service, where the second resource weight is the weighted sum of the first resource weight and the proportion of impact of each QoS hierarchical control policy on the service, and calculating the second The resource weight is normalized, and QoS hierarchical control is performed on the service according to the normalized resource weight. In this way, the solution supports multiple QoS hierarchical control strategies, and can use different QoS hierarchical control strategies according to different application requirements, effectively optimizing the processing capacity of the Web service container and ensuring the quality of service.

Embodiment Three

As shown in FIG. 3 , it is a schematic structural diagram of an embodiment of a Web service container provided by the present invention. The specific structure is as follows: a receiving module 301 , a determining module 302 , a controlling module 303 and a normalizing module 304 .

Wherein, the receiving module 301 is used to receive the service request sent by the user;

The determining module 302 is configured to determine the amount of resources allocated for the service under each QoS hierarchical control strategy; determine the first resource weight obtained by the service under each QoS hierarchical control strategy, and the first resource weight is The ratio of the number of resources to the total amount of resources; determine the second resource weight obtained by the service, and the second resource weight is the impact of the first resource weight and each QoS hierarchical control strategy on the service weighted sum of proportions;

The control module 303 is configured to perform QoS hierarchical control on the service according to the second resource weight.

Further, each QoS hierarchical control strategy includes at least two of the following strategies: performance optimization strategy, revenue optimization strategy and resource optimization strategy.

Further, the determining module 302 is specifically configured to use a dynamic programming algorithm to determine the number of resources allocated for the service under constraints; the constraints are: if a total of n services are deployed, C is a constant, Then the resource quantity Wi allocated to each service needs to satisfy

Further, the total amount of resources is the total number of deployed services multiplied by the total number of elements in the service priority queue.

Further, the service request includes a preset response time and/or a preset QoS satisfaction rate;

Correspondingly, the determining module is specifically configured to determine if the average response time of the service exceeds the preset response time, and/or if the actual QoS satisfaction rate of the service is less than the preset QoS satisfaction rate The second resource weight obtained by the service is a weighted sum of the first resource weight and the impact proportion of each QoS hierarchical control policy on the service multiplied by 2.

Further, the Web service container also includes:

A normalization module 304, configured to perform normalization processing on the second resource weight obtained by the service after the determination of the second resource weight obtained by the service, to obtain a normalized resource of the service Weight;

Correspondingly, the control module 303 is specifically configured to perform QoS hierarchical control on the service according to the normalized resource weight of the service.

Further, the control module 303 is specifically configured to determine the priority order of the service according to the second resource weight; complete the operation corresponding to the service according to the priority order of the service, and return the result to user.

The Web service container described in this embodiment is used to execute the method steps described in Embodiment 1 and Embodiment 2, and its technical principles and technical effects are similar and will not be repeated here.

It should be noted that, for the foregoing method embodiments, for the sake of simple description, they are expressed as a series of action combinations, but those skilled in the art should know that the present invention is not limited by the described action sequence. Because of the present invention, certain steps may be performed in other orders or simultaneously. Secondly, those skilled in the art should also know that the embodiments described in the specification belong to preferred embodiments, and the actions and modules involved are not necessarily required by the present invention.

Those of ordinary skill in the art can understand that all or part of the steps for realizing the above-mentioned method embodiments can be completed by hardware related to program instructions, and the aforementioned program can be stored in a computer-readable storage medium. When the program is executed, the It includes the steps of the above method embodiments; and the aforementioned storage medium includes: ROM, RAM, magnetic disk or optical disk and other various media that can store program codes.

Finally, it should be noted that: the above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit them; although the present invention has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that: it can still be Modifications are made to the technical solutions described in the foregoing embodiments, or equivalent replacements are made to some of the technical features; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the various embodiments of the present invention.

Claims (10)

1. A Web service QoS hierarchical control method, characterized in that, comprising: Receive service requests sent by users; Determine the number of resources allocated for services under each QoS hierarchical control strategy; Determine the first resource weight obtained by the service under each QoS hierarchical control strategy, where the first resource weight is the ratio of the number of resources to the total amount of resources; Determining a second resource weight obtained by the service, where the second resource weight is a weighted sum of the first resource weight and the impact ratio of each QoS hierarchical control policy on the service; Perform hierarchical QoS control on the service according to the second resource weight. 2. The method according to claim 1, wherein each QoS hierarchical control strategy includes at least two of the following strategies: performance optimization strategy, revenue optimization strategy and resource optimization strategy. 3. The method according to claim 1 or 2, wherein the determining the amount of resources allocated for the service under each QoS hierarchical control strategy includes: Under the constraints, using a dynamic programming algorithm to determine the amount of resources allocated for the service; The constraint condition is: if a total of n services are deployed and C is a constant, the resource quantity W _i allocated to each service needs to satisfy 4. The method according to claim 1 or 2, further comprising: after said determining the second resource weight obtained by said service: performing normalization processing on the second resource weight obtained by the service to obtain the normalized resource weight of the service; Correspondingly, performing QoS hierarchical control on the service according to the second resource weight includes: Perform QoS hierarchical control on the service according to the normalized resource weight of the service. 5. The method according to claim 1 or 2, wherein the performing QoS hierarchical control on the service according to the second resource weight comprises: determining the priority order of the services according to the second resource weight; The operations corresponding to the services are completed according to the priority order of the services, and the results are returned to the user. 6. A web service container, characterized in that it comprises: The receiving module is used to receive the service request sent by the user; A determining module, configured to determine the amount of resources allocated for the service under each QoS hierarchical control strategy; determine the first resource weight value obtained by the service under each QoS hierarchical control strategy, and the first resource weight value is determined by The ratio of the number of resources to the total amount of resources; determine the second resource weight obtained by the service, and the second resource weight is the proportion of the impact of the first resource weight and each QoS hierarchical control strategy on the service weighted sum of A control module, configured to perform QoS hierarchical control on the service according to the second resource weight. 7. The Web service container according to claim 6, wherein each QoS hierarchical control strategy includes at least two of the following strategies: performance optimization strategy, revenue optimization strategy and resource optimization strategy. 8. The Web service container according to claim 6 or 7, wherein the determining module is specifically configured to use a dynamic programming algorithm to determine the number of resources allocated for the service under constraints; the constraints The condition is: if a total of n services are deployed and C is a constant, the resource quantity W _i allocated to each service needs to satisfy 9. The Web service container according to claim 6 or 7, further comprising: A normalization module, configured to perform normalization processing on the second resource weight obtained by the service after the determination of the second resource weight obtained by the service, to obtain the normalized resource weight of the service value; Correspondingly, the control module is specifically configured to perform QoS hierarchical control on the service according to the normalized resource weight of the service. 10. The Web service container according to claim 6 or 7, wherein the control module is specifically configured to determine the priority order of the services according to the second resource weight value; The corresponding operations of the service are completed in sequence, and the results are returned to the user.