Method and apparatus for determining node weight values

Abstract

This application provides a method and apparatus for determining node weight values. The method includes: determining the traffic link to be processed corresponding to the target task, and the current service node, upstream service node, and link policy of the traffic link to be processed; obtaining the initial weight value and policy configuration information of the current service node, and the reference weight value of the upstream service node; determining the current service node policy of the current service node based on the policy configuration information and the link policy; determining the target weight value of the current service node based on the current service node policy, the initial weight value, and the reference weight value; and obtaining the weight distribution information of the traffic link to be processed based on the target weight values ​​of each service node in the traffic link to be processed. This eliminates the need to configure policies for each service node in the traffic link to be processed individually, reducing the workload of policy configuration.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to a method for determining node weight values. This application also relates to a node weight value determination apparatus, a computing device, and a computer-readable storage medium. Background Technology

[0002] With the development of science and technology, internet technology is becoming increasingly integrated into people's lives, influencing their daily routines. In practical applications, data usage also affects users' experience on the network. To improve user experience, it is often necessary to implement data protection or data control measures.

[0003] However, traffic links often have multiple traffic nodes. If corresponding governance rules are configured for each traffic node, the workload of rule configuration is huge and the rule configuration process is also quite cumbersome. In subsequent configuration and maintenance work, there will also be maintenance difficulties.

[0004] Therefore, how to reduce the workload of rule configuration for each node in the traffic link and realize traffic detection for each node in the traffic link has become an urgent technical problem to be solved. Summary of the Invention

[0005] In view of this, embodiments of this application provide a method for determining node weight values. This application also relates to a node weight value determination apparatus, a computing device, and a computer-readable storage medium, to solve the aforementioned problems existing in the prior art.

[0006] According to a first aspect of the embodiments of this application, a method for determining node weight values ​​is provided, including:

[0007] Identify the traffic link to be processed corresponding to the target task, as well as the current service node, upstream service node, and link policy of the traffic link to be processed;

[0008] Obtain the initial weight value and strategy configuration information of the current business node, as well as the reference weight value of the upstream business node;

[0009] Based on the policy configuration information and the link policy, determine the current service node policy of the current service node;

[0010] The target weight value of the current business node is determined based on the current business node strategy, the initial weight value, and the reference weight value.

[0011] Based on the target weight values ​​of each service node in the traffic link to be processed, the weight value distribution information of the traffic link to be processed is obtained.

[0012] According to a second aspect of the embodiments of this application, a node weight value determination apparatus is provided, comprising:

[0013] The node determination module is configured to determine the traffic link to be processed corresponding to the target task, as well as the current business node, upstream business node and link policy of the traffic link to be processed.

[0014] The acquisition module is configured to acquire the initial weight value and strategy configuration information of the current business node, as well as the reference weight value of the upstream business node;

[0015] The strategy determination module is configured to determine the current service node strategy of the current service node based on the strategy configuration information and the link strategy.

[0016] The weight value determination module is configured to determine the target weight value of the current business node based on the current business node strategy, the initial weight value, and the reference weight value.

[0017] The acquisition module is configured to obtain the weight distribution information of the traffic link to be processed based on the target weight values ​​of each service node in the traffic link to be processed.

[0018] According to a third aspect of the embodiments of this application, a computing device is provided, including a memory, a processor, and computer instructions stored in the memory and executable on the processor, wherein the processor executes the computer instructions to implement the steps of the node weight value determination method.

[0019] According to a fourth aspect of the embodiments of this application, a computer-readable storage medium is provided that stores computer instructions, which, when executed by a processor, implement the steps of the node weight value determination method.

[0020] The node weight value determination method provided in this application includes: determining the traffic link to be processed corresponding to the target task, and the current service node, upstream service node, and link policy of the traffic link to be processed; obtaining the initial weight value and policy configuration information of the current service node, and the reference weight value of the upstream service node; determining the current service node policy of the current service node according to the policy configuration information and the link policy; determining the target weight value of the current service node according to the current service node policy, the initial weight value, and the reference weight value; and obtaining the weight value distribution information of the traffic link to be processed according to the target weight values ​​of each service node of the traffic link to be processed.

[0021] One embodiment of this application implements a method that first sets a link policy for the traffic link to be processed corresponding to the target task, then determines the policy configuration information of each service node in the traffic link to be processed, and determines the current service node policy of the current service node based on the policy configuration information and the link policy. This eliminates the need to configure policies for each service node in the traffic link to be processed one by one, reducing the workload of policy configuration. Based on the initial weight value, reference weight value and current service node policy of the service node, the target weight value of the current service node is determined, thereby obtaining the weight value distribution information of the traffic link to be processed. This is beneficial for traffic regulation of the traffic link to be processed based on the weight value distribution information of the traffic link to be processed, thereby improving processing efficiency. Attached Figure Description

[0022] Figure 1 This is a schematic diagram illustrating an application scenario of a node weight value determination method provided in an embodiment of this application;

[0023] Figure 2 This is a flowchart of a method for determining node weight values ​​provided in an embodiment of this application;

[0024] Figure 3a This is a schematic diagram illustrating the setting of initial node weight values ​​according to an embodiment of this application;

[0025] Figure 3b This is a schematic diagram illustrating another method for setting the initial weight value of a node according to an embodiment of this application;

[0026] Figure 4 This is a schematic diagram of the processing flow of a node weight value determination method provided in an embodiment of this application;

[0027] Figure 5 This is a schematic diagram of the weight value distribution information of a traffic link to be processed, provided in an embodiment of this application;

[0028] Figure 6 This is a flowchart illustrating a method for determining node weight values ​​in an e-commerce scenario, provided by an embodiment of this application.

[0029] Figure 7 This is a schematic diagram of a node weight value determination device provided in an embodiment of this application;

[0030] Figure 8 This is a structural block diagram of a computing device provided in one embodiment of this application. Detailed Implementation

[0031] Many specific details are set forth in the following description to provide a full understanding of this application. However, this application can be implemented in many other ways different from those described herein, and those skilled in the art can make similar extensions without departing from the spirit of this application; therefore, this application is not limited to the specific embodiments disclosed below.

[0032] The terminology used in one or more embodiments of this application is for the purpose of describing particular embodiments only and is not intended to limit the scope of one or more embodiments of this application. The singular forms “a,” “the,” and “the” used in one or more embodiments of this application and in the appended claims are also intended to include the plural forms unless the context clearly indicates otherwise. It should also be understood that the term “and / or” used in one or more embodiments of this application refers to and includes any or all possible combinations of one or more associated listed items.

[0033] It should be understood that although the terms first, second, etc., may be used to describe various information in one or more embodiments of this application, such information should not be limited to these terms. These terms are only used to distinguish information of the same type from one another. For example, first may also be referred to as second without departing from the scope of one or more embodiments of this application, and similarly, second may also be referred to as first. Depending on the context, the word "if" as used herein may be interpreted as "when," "when," or "in response to a determination."

[0034] First, the terms and concepts involved in one or more embodiments of this application will be explained.

[0035] Link: refers to a physical path from one node to an adjacent node, without any other switching nodes in between.

[0036] In practical applications, traffic governance and traffic protection are crucial functions in service governance, particularly in traffic circuit breaking, degradation, and rate limiting. For different resources, a downstream resource might have important upstream resources accessing it. In this case, the entire link should be allowed to pass. However, the importance of that resource might differ from others, leading to rate limiting or circuit breaking. Specifically, upstream traffic to that resource can be controlled. However, if the resource has multiple upstream levels, each level needs to be configured sequentially. If the resource has multiple upstreams, each upstream needs to be configured individually. This involves a significant workload and a cumbersome process, and also presents maintenance difficulties in subsequent configuration and upkeep.

[0037] This application provides a method for determining node weight values, and also relates to a device for determining node weight values, a computing device, and a computer-readable storage medium, which will be described in detail in the following embodiments.

[0038] Figure 1 The illustration shows an application scenario diagram of a node weight value determination method according to an embodiment of this application. The node weight value determination method provided in this application can calculate the weight value corresponding to each service node, thereby obtaining the weight value distribution information corresponding to each traffic link to be processed. This allows for traffic regulation of service nodes that can be regulated when the system load of subsequent node systems is too high or the traffic reaches its limit, based on the weight value distribution information corresponding to each traffic link to be processed.

[0039] like Figure 1 As shown in the example of an e-commerce scenario, both core and peripheral businesses need to query orders. If the traffic load on the system where the order query node is located is too high, traffic regulation needs to be implemented on the upstream resources (i.e., core and peripheral businesses). Specifically, the weight values ​​of core and peripheral businesses can be calculated separately. Based on these weight values, the upstream resources that can be subject to traffic regulation are determined. Compared to peripheral businesses, core businesses have a higher weight value. Therefore, traffic regulation can be implemented for requests entering order query from peripheral businesses, ensuring that requests entering order query from core businesses can access the service normally.

[0040] If the system hosting the product query node experiences excessive traffic load during the product query process, traffic regulation needs to be implemented on the upstream resources (i.e., query orders and create orders). Specifically, the weight values ​​of query orders and create orders can be calculated separately. Based on these weight values, upstream resources suitable for traffic regulation can be identified. Create orders have a higher weight value than query orders; therefore, traffic regulation can be applied to requests originating from query orders that then attempt to query products, ensuring that requests originating from create orders can access products normally.

[0041] For the method of determining the weight values ​​of core business, peripheral business, order query and order creation, please refer to the description of the technical solution of the node weight value determination method below, which will not be described in detail here.

[0042] The node weight determination method provided in this application obtains the weight distribution information of the traffic link to be processed by determining the weight value of each business node in the traffic link. This allows for traffic regulation of upstream resources of the node system based on the weight distribution information of the traffic link when the system load of the node system is too high or the traffic reaches the limit. By determining the weight value of each business node, it is no longer necessary to configure corresponding traffic regulation rules for each business node separately, which greatly reduces the workload of rule configuration.

[0043] Figure 2 The flowchart illustrates a method for determining node weight values ​​according to an embodiment of this application, which specifically includes the following steps:

[0044] Step 202: Determine the traffic link to be processed corresponding to the target task, as well as the current service node, upstream service node and link policy of the traffic link to be processed.

[0045] In practical applications, to achieve traffic management and protection, we can determine whether the traffic accessing the current business node has reached its limit. If it has, we can limit the traffic to the current business node. We can also determine whether the traffic of the associated nodes of the current business node has reached its limit. If it has, we can limit the traffic to the current business node. Alternatively, we can configure corresponding rate limiting rules for each business node in the entire traffic chain to achieve traffic management and protection.

[0046] In one embodiment provided in this application, a limited strategy can be used to configure the traffic link to be processed and each service node, and the weight value corresponding to each service node in the traffic link to be processed can be determined according to the limited strategy, thereby determining the service nodes that can be subject to traffic regulation.

[0047] In this context, a target task refers to a task initiated by a user that needs to be executed. For example, user C initiates an order task on a shopping app to search for the product "clothes," while user D initiates an order task on a shopping app to purchase the product "lipstick." Different target tasks correspond to different pending traffic paths.

[0048] Traffic links awaiting processing refer to traffic links where the weight values ​​of each service node need to be determined or where policy configuration has not yet been completed. Figure 1 For example, if the target task is to query products in an order based on core business, then the traffic path to be processed is "core business - query order - query product"; if the target task is to query products in an order based on edge business, then the traffic path to be processed is "edge business - query order - query product".

[0049] The current business node refers to the business node in the pending traffic chain that is currently determining its weight value. For example, if the pending traffic chain is "core business - query order - query product", and the weight value of the core business has been determined but the weight value of the query order has not yet been determined, then the business node corresponding to the query order is the current business node.

[0050] An upstream business node refers to the business node preceding the current business node. For example, if the traffic path to be processed is "core business - query order - query product", and the weight value of the core business has been determined but the weight value of the query order has not yet been determined, the business node corresponding to the query order is the current business node, and the business node corresponding to the core business is the upstream business node.

[0051] Link policy refers to the strategy configured for the traffic links to be processed, used to determine the weight values ​​of each service node. Link policies can be resource-priority policies, traffic-priority policies, and default comparison policies. A resource-priority policy prioritizes the importance of the service resources of the current service node over those of the upstream service node. A traffic-priority policy prioritizes the importance of the service resources of the upstream service node over those of the current service node. A default comparison policy determines the weight value of the current service node based on a comparison between the weight values ​​of the current service node and the upstream service node.

[0052] The weight value is used to characterize the importance of the business resources of each business node in the traffic link to be processed.

[0053] Specifically, before determining the weight value of the current business node, it is necessary to first determine the current business node, the upstream business node corresponding to the current business node, and the link strategy corresponding to the traffic link to be processed in the traffic link to be processed.

[0054] For example, if the traffic path to be processed is "core business - query order - query product", and the weight values ​​of core business and query order have been determined, but the weight value of query product has not yet been determined, it is necessary to determine the weight value of the query product node. In this case, the query product node is determined as the current business node, and the query order node is determined as the upstream business node of the query product node. If the strategy set for the traffic path to be processed "core business - query order - query product" is a resource priority strategy, then the link strategy for the traffic path to be processed "core business - query order - query product" is determined to be a resource priority strategy.

[0055] The node weight value determination method provided in this application requires determining the current business node, the upstream business node of the current business node, and the link strategy of the traffic link to be processed before determining the weight value of each business node in the traffic link to be processed, so as to determine the node strategy corresponding to each business node based on the link strategy of the traffic link to be processed in the subsequent process.

[0056] Step 204: Obtain the initial weight value and strategy configuration information of the current business node, as well as the reference weight value of the upstream business node.

[0057] After identifying the current business node and upstream business node that need to have their weights determined in the traffic chain to be processed, the initial weight value and policy configuration information of the current business node, as well as the reference weight value of the upstream business node, can be obtained. This allows the target weight value of the current business node to be determined based on the initial weight value of the current business node and the reference weight value of the upstream business node.

[0058] The initial weight value refers to the weight value set based on the business level of the business resources corresponding to each business node, used to characterize the importance of the business resources corresponding to each business node. Policy configuration information refers to whether the current business node has configured node policies. Node policies refer to the policies configured for business nodes on the traffic link to be processed. Node policies can be resource priority policies, traffic priority policies, and default comparison policies.

[0059] The reference weight value refers to the determined weight value of the upstream business node, which is used to characterize the importance of the business resources corresponding to the upstream business node.

[0060] Specifically, in practical applications, the initial weight values ​​of each service node in the traffic link to be processed can be preset according to the service resources corresponding to each service node. Based on this, in a specific embodiment provided in this application, the method further includes:

[0061] Determine the business resources corresponding to each business node in the traffic link to be processed;

[0062] Based on the service level of the service resources corresponding to each service node in the traffic link to be processed, an initial weight value is set for each service node.

[0063] After identifying the traffic links to be processed, the business resources corresponding to each business node are obtained and determined. Then, the business level of each business resource is determined according to its importance, and an initial weight value is set for the business nodes corresponding to each business resource based on the business level.

[0064] Specifically, see Figure 3a , Figure 3a A schematic diagram illustrating the setting of initial node weight values ​​according to an embodiment of this application is shown. Figure 3aIn this system, the node system is a front-end business node system, which includes five business nodes. The business resources corresponding to each business node include core business 1, core business 2, core business 3, edge business 1, and edge business 2. Based on the importance of the above business resources, they are set to five business levels. The business resources are sorted from high to low according to their business level, namely core business 3, core business 2, core business 1, edge business 2, and edge business 1. Based on the business level of each business resource, the corresponding business nodes are assigned corresponding initial weight values. The initial weight values ​​of core business 3, core business 2, core business 1, edge business 2, and edge business 1 are 5, 4, 3, 2, and 1, respectively.

[0065] See Figure 3b , Figure 3b A schematic diagram illustrating another node initial weight value setting according to an embodiment of this application is shown. Figure 3b In this system, the node system is the order center node system, which includes five business nodes. The business resources corresponding to each business node include creating an order, modifying an order, adding notes to an order, querying an order, and expiring an order. Based on the importance of these business resources, they are set to five business levels. The business resources are sorted from highest to lowest business level as follows: create an order, modify an order, add notes to an order, query an order, and expire an order. Based on the business level of each business resource, the corresponding business nodes are assigned corresponding initial weight values. The initial weight values ​​for the create an order node, modify an order node, add notes to an order node, query an order node, and expire an order node are 5, 4, 3, 2, and 1, respectively.

[0066] It should be noted that the method for setting the initial weight value for each business node is not limited to the method described above. In the process of setting the initial weight value, it can also be set according to a fixed ratio. For example, the initial weight values ​​corresponding to the order creation node, order modification node, order note node, order query node, and order expiration node can be set to 25, 20, 15, 10, and 5 respectively.

[0067] The node weight value determination method provided in this application can pre-set different business levels for each business resource based on the importance of the business resources corresponding to each business node, and set initial weight values ​​for the business nodes corresponding to each business resource based on the business level corresponding to the business resource.

[0068] Step 206: Determine the current service node policy of the current service node based on the policy configuration information and the link policy.

[0069] After obtaining the policy configuration information of the current business node, it can be determined whether the current business node has a node policy configured. After knowing whether the current business node has a node policy configured, the current business node policy can be further determined by combining the link policy.

[0070] The current business node policy refers to the policy configured for the current business node. The current business node policy is only used to determine the weight value of the current business node and does not affect other nodes in the pending traffic link to which the current business node belongs.

[0071] In practical applications, due to the high importance of certain business resources in the traffic link to be processed, a node policy may be configured separately for the corresponding business node. When the node policy and the link policy are different, the current business node policy of the business node needs to be determined in both the node policy and the link policy.

[0072] Furthermore, in a specific embodiment provided in this application, determining the current service node policy of the current service node based on the policy configuration information and the link policy includes:

[0073] Based on the policy configuration information, determine whether the current business node has a node policy configured;

[0074] If the current service node is configured with a node policy, the current service node policy of the current service node is determined from the node policy and the link policy.

[0075] If no node policy is configured on the current service node, the link policy will be determined as the current service node policy of the current service node.

[0076] Specifically, based on the obtained policy configuration information of the current business node, it is determined whether the current business node has a configured node policy. If it is determined that the current business node has a configured node policy, then one of the node policy and the link policy needs to be determined as the current business node policy of the current business node. If it is determined that the current business node has not configured a node policy, then the link policy is determined as the current business node policy of the current business node.

[0077] Taking a traffic-first policy as an example, if the current business node is a query order node, and based on the policy configuration information of the query order node, it is determined that the node policy configured for the query order node is a resource-first policy, then one of the resource-first policy and the traffic-first policy needs to be determined as the current business node policy for the query order node. That is, the resource-first policy or the traffic-first policy is determined as the current business node policy for the query order node. If, based on the policy configuration information of the query order node, it is determined that the query order node has no configured node policy, then the traffic-first policy is directly determined as the current business node policy for the query order node.

[0078] Since the importance of the business resources corresponding to each business node is different, the corresponding node strategies are also different. Different node strategies are configured according to the importance of the business resources. Therefore, different node strategies have different priorities. The current business node strategy can be determined among different node strategies based on the priority of the node strategy.

[0079] Furthermore, in a specific embodiment provided in this application, determining the current service node policy of the current service node in the node policy and the link policy includes:

[0080] Determine the node policy priority of the node policy and the link policy priority of the link policy;

[0081] The current business node policy is determined based on the node policy priority and the link policy priority.

[0082] Among them, node policy priority refers to the priority of node policies, and link policy priority refers to the priority of link policies.

[0083] If it is determined that the current business node is configured with a node policy, the priority of the node policy and the priority of the link policy are obtained respectively. Based on the comparison results of the node policy priority and the link policy priority, the current business node policy of the current business node is determined from the node policy and the link policy.

[0084] Furthermore, in a specific embodiment provided in this application, determining the current service node policy of the current service node based on the node policy priority and the link policy priority includes:

[0085] If the priority of the node policy is higher than the priority of the link policy, the node policy is determined as the current business node policy of the current business node.

[0086] If the priority of the node policy is lower than the priority of the link policy, the link policy is determined as the current business node policy of the current business node.

[0087] Specifically, the policy priorities of the node policy and the link policy are compared. If the node policy priority is higher than the link policy priority, the node policy is determined as the current business node policy of the current business node. If the node policy priority is lower than the link policy priority, the link policy is determined as the current business node policy of the current business node. If the node policy and the link policy are the same policy, the policy is directly determined as the current business node policy of the current business node.

[0088] It should be noted that the priorities of the resource priority strategy, traffic priority strategy, and default comparison strategy can be set according to the actual application situation. For example, if the upstream business resources of the traffic link to be processed are of higher importance and need to be protected first, the traffic priority strategy can be set to a higher priority. If the downstream business resources of the traffic link to be processed are of higher importance and need to be protected first, the resource priority strategy can be set to a higher priority. In practical applications, the strategy priorities can also be set according to the actual application situation, and this application does not impose any restrictions on this.

[0089] In one embodiment provided in this application, preferably, the policy priority settings are set from high to low as resource priority policy, traffic priority policy, and default comparison policy.

[0090] For example, in the pending traffic link "Edge Business - Query Order - Query Product", if no link strategy is configured, the pending traffic link adopts the default comparison strategy. If the current business node is the Query Product node and the Query Product node is configured with a traffic priority strategy, since the strategy priority of the traffic priority strategy is higher than the default comparison strategy, the current business node strategy of the Query Product node is determined to be the traffic priority strategy.

[0091] For example, in the pending traffic link "edge business - query order - query product", the link policy is configured as a resource priority policy. If the current business node is a query order node and the query order node is configured with a traffic priority policy, since the traffic priority policy has a lower priority than the resource priority policy, the current business node policy of the query order node is determined to be a resource priority policy.

[0092] The node weight determination method provided in this application can determine whether a current business node has a configured node policy based on its policy configuration information. If a node policy is configured, the current business node policy can be determined from the node policy and link policy priorities. By first setting the link policy for the traffic to be processed, then setting the node policy for the business node individually, and further determining the node policy of the current business node by setting policy priorities, the workload of configuring the current business node policy for each business node is greatly reduced.

[0093] Step 208: Determine the target weight value of the current business node based on the current business node strategy, the initial weight value, and the reference weight value.

[0094] The target weight value refers to the weight value of the current business node that needs to be determined, which is used to characterize the importance of the business resources corresponding to the current business node.

[0095] See Figure 4 , Figure 4 A schematic diagram illustrating the processing flow of a node weight value determination method according to an embodiment of this application is shown. Figure 4 As shown, after determining the reference weight value of the upstream business node, the upstream business node sends the reference weight value to the current business node. Further, after obtaining the reference weight value sent by the upstream business node, the current business node determines the target weight value of the current business node based on the obtained initial weight value of the current business node and the current business node strategy, and sends the target weight value to the downstream business node, so that the downstream business node determines the weight value of the downstream business node based on the target weight value of the current business node.

[0096] In one specific embodiment provided in this application, the current service node strategy includes any one of a resource priority strategy, a traffic priority strategy, and a default comparison strategy;

[0097] Based on the current business node strategy, the initial weight value, and the reference weight value, the target weight value of the current business node is determined, including:

[0098] If the current business node strategy includes a resource priority strategy, the initial weight value is determined to be the target weight value of the current business node.

[0099] If the current business node strategy includes a traffic priority strategy, the reference weight value is determined to be the target weight value of the current business node.

[0100] If the current business node strategy includes a default comparison strategy, the target weight value of the current business node is determined from the initial weight value and the reference weight value.

[0101] Specifically, if the current business node's current business node strategy is determined to be a resource priority strategy, then the initial weight value of the current business node is determined as the target weight value of the current business node. If the current business node's current business node strategy is determined to be a traffic priority strategy, then the reference weight value of the upstream business node is determined as the target weight value of the current business node. If the current business node's current business node strategy is determined to be a default comparison strategy, then the target weight value of the current business node is determined from the initial weight value of the current business node and the reference weight value of the upstream business node.

[0102] Specifically, in one embodiment provided in this application, determining the target weight value of the current service node from the initial weight value and the reference weight value includes:

[0103] If the initial weight value is greater than the reference weight value, the initial weight value is determined to be the target weight value for the current business node;

[0104] If the initial weight value is less than or equal to the reference weight value, the reference weight value is determined to be the target weight value of the current business node.

[0105] The initial weight value of the current business node is compared with the reference weight value of the upstream business node. If the initial weight value is greater than the reference weight value, the initial weight value is determined as the target weight value of the current business node. If the initial weight value is less than the reference weight value, the reference weight value is determined as the target weight value of the current business node. If the initial weight value is equal to the reference weight value, either the initial weight value or the reference weight value is determined as the target weight value of the current business node.

[0106] Furthermore, combined Figure 3a and Figure 3b To illustrate this using an e-commerce scenario as an example, see the details below:

[0107] Traffic Link 1 to be Processed: Core Business 1 needs to query orders in the order center system and query products in the product center system. Therefore, Traffic Link 1 to be Processed is determined to be "Core Business 1 - Query Orders - Query Products". For example, if Traffic Link 1 to be Processed is not configured with a link strategy, then Traffic Link 1 to be Processed will use the default comparison strategy, that is, the link strategy of Traffic Link 1 to be Processed will be the default comparison strategy. Based on this, the weight value of Core Business 1 is Value(1) = Max{Resource(1),0} = 3, the weight value of querying orders in the order center system is Value(2) = Max{2,3} = 3, and the weight value of querying products in the product center system is Value(3) = Max{2,3} = 3.

[0108] Traffic Link 2 to be Processed: If Edge Business 1 needs to query orders in the Order Center System and query products in the Product Center System, then Traffic Link 2 to be Processed is determined to be "Edge Business 1 - Query Order - Query Product". For example, if Traffic Link 2 to be Processed is not configured with a link strategy, then Traffic Link 2 to be Processed adopts the default comparison strategy, that is, the link strategy of Traffic Link 2 to be Processed is determined to be the default comparison strategy. Based on this, the weight value Value(1) of Edge Business 1 = Max{Resource(1),0} = 1, the weight value Value(2) of querying orders in the Order Center System = Max{2,1} = 2, and the weight value Value(3) of querying products in the Product Center System = Max{2,2} = 2.

[0109] Traffic Link 3 to be Processed: Core Business 2 needs to query orders in the order center system and query products in the product center system. Therefore, traffic link 3 to be processed is determined to be "Core Business 2 - Query Order - Query Product". For example, it is determined that traffic link 3 to be processed is configured with a link strategy, and the link strategy of traffic link 3 to be processed is a traffic priority strategy. Based on this, the weight value of core business 2 is Value(1) = Max{Resource(1),0} = 4, the weight value of querying orders in the order center system is Value(2) = Value(1) = 4, and the weight value of querying products in the product center system is Value(3) = Value(2) = 4.

[0110] Traffic Link 4 to be Processed: Core Business 3 needs to query orders in the order center system and query products in the product center system. Therefore, traffic link 4 to be processed is determined to be "Core Business 3 - Query Order - Query Product". For example, if traffic link 4 to be processed is not configured with a link strategy, then traffic link 4 to be processed adopts the default comparison strategy, that is, the link strategy of traffic link 4 to be processed is determined to be the default comparison strategy, in which the query order node is configured with a resource priority strategy. Based on this, the weight value of core business 3 is Value(1) = Max{Resource(1),0} = 5, the weight value of querying orders in the order center system is Value(2) = Resource(2) = 2, and the weight value of querying products in the product center system is Value(3) = Max{2,2} = 2.

[0111] Traffic Link 5 to be Processed: Core Business 2 needs to create an order in the order center system and query a product in the product center system. Therefore, traffic link 5 to be processed is determined to be "Core Business 2 - Create Order - Query Product". For example, it is determined that traffic link 5 to be processed is configured with a link strategy, and the link strategy of traffic link 5 to be processed is a traffic priority strategy. Among them, the order creation node is configured with a resource priority strategy. Based on this, the weight value Value(1) of core business 2 = Max{Resource(1),0} = 4, the weight value Value(2) of creating an order in the order center system = Resource(2) = 5, and the weight value Value(3) of querying a product in the product center system = Value(2) = 5.

[0112] Here, Value represents the weight value, and Resource represents the initial weight value.

[0113] The node weight value determination method provided in this application first determines the link policy of the traffic link to be processed, then determines whether each business node is configured with a node policy. If the business node is configured with a node policy, the current business node policy is determined from the node policy and link policy based on the policy priority. Based on the current business node policy, the initial weight value and the reference weight value, the target weight value of the business node can be further determined. This allows subsequent determination of whether to perform traffic control on each business node based on the target weight value of each business node. Therefore, it is not necessary to configure a corresponding node policy for each business node in the traffic link to be processed, which reduces the workload of node policy configuration and improves processing efficiency.

[0114] Step 210: Obtain the weight distribution information of the traffic link to be processed based on the target weight values ​​of each service node in the traffic link to be processed.

[0115] The weight distribution information refers to the weight distribution information of each service node in the traffic link to be processed.

[0116] See Figure 5 , Figure 5 A schematic diagram illustrating the weight distribution information of a traffic link to be processed according to an embodiment of this application is shown. Figure 5 The diagram illustrates the weight distribution information for the aforementioned traffic links 1, 2, 3, 4, and 5 to be processed. A swimlane is formed between two dashed lines, and different target weight values ​​can be set within each swimlane. For example, a swimlane might have a target weight value of 1-2, and so on, with target weight values ​​for 3-4, 5-6, and so on. Figure 5 Taking an information distribution swimlane with a target weight value set as an example, the weight value distribution information of the traffic links 1-5 to be processed is shown.

[0117] Furthermore, based on such Figure 5 The weight distribution information of the traffic links to be processed shown can quickly adjust the traffic of the link nodes when the system load of the node system in the traffic link to be processed is too high or the traffic reaches the limit.

[0118] Based on this, in a specific embodiment provided in this application, after obtaining the weight value distribution information of the traffic link to be processed, the method further includes:

[0119] When the target node system meets the preset control conditions, traffic control is performed on the service nodes in the target node system based on the weight distribution information of each traffic link to be processed. The target node system is the node system to which any service node in each traffic link to be processed belongs.

[0120] Among them, the preset control conditions refer to the pre-set conditions used to determine whether traffic control of business nodes is required. Specifically, it can be that the system load of the node system reaches the preset load, or that the traffic usage of the node system reaches the preset limit, etc.

[0121] If the node system to which any business node in each traffic link to be processed belongs is determined and the preset control conditions are met, traffic control can be performed on the business nodes in the node system that meet the preset control conditions based on the obtained weight value distribution information of each traffic link to be processed.

[0122] Furthermore, in a specific embodiment provided in this application, traffic regulation is performed on the service nodes in the target node system based on the weight distribution information of each traffic link to be processed, including:

[0123] In the target node system, at least one service node to be regulated is identified, wherein the at least one service node to be regulated is deployed on different traffic links to be processed;

[0124] Obtain the target weight value of the at least one service node to be regulated in at least two traffic links to be processed;

[0125] Traffic regulation is performed on the at least one service node to be regulated based on the target weight value of the at least one service node to be regulated in at least two traffic links to be processed.

[0126] Among them, the business nodes to be regulated refer to the business nodes in the target node system that require traffic regulation, and the business nodes to be regulated are deployed on different traffic links to be processed.

[0127] Specifically, at least one service node to be regulated is identified in the target node system, and the target weight value of at least one service node to be regulated is obtained. The target weight values ​​of the service node to be regulated in different traffic links to be processed are compared. Based on the comparison results, traffic regulation is performed on the service node to be regulated with the smaller target weight value.

[0128] Using the example of traffic links 1-5 to be processed above, the Value(3) of traffic link 1 to be processed is 3, that is, the weight value of the query product node of traffic link 1 to be processed is 3, and the Value(3) of traffic link 2 to be processed is 2, that is, the weight value of the query product node of traffic link 2 to be processed is 2. It can be determined that the Value(3) of traffic link 1 to be processed is greater than the Value(3) of traffic link 2 to be processed. Therefore, traffic regulation can be performed on the query product node of traffic link 2 to be processed. Specifically, it can be to restrict the requests from the query order node to the query product node in traffic link 2 to be processed.

[0129] Using the example of traffic links 1-5 to be processed again, the value (3) of traffic link 3 to be processed is 4, that is, the weight value of the query product node of traffic link 3 to be processed is 4, and the value (3) of traffic link 2 to be processed is 2, that is, the weight value of the query product node of traffic link 2 to be processed is 2. It can be determined that the value (3) of traffic link 3 to be processed is greater than the value (3) of traffic link 2 to be processed. Therefore, traffic regulation can be performed on the query product node of traffic link 2 to be processed. Specifically, it can be to restrict the requests from the query order node to the query product node in traffic link 2 to be processed.

[0130] The node weight value determination method provided in this application can quickly regulate the traffic of the link nodes when the system load of the node system in the traffic link to be processed is too high or the traffic reaches the limit. Based on the comparison of the weight values ​​of each business node, it can quickly realize the traffic regulation of the link nodes.

[0131] The node weight value determination method provided in this application includes: determining the traffic link to be processed corresponding to the target task, and the current service node, upstream service node, and link policy of the traffic link to be processed; obtaining the initial weight value and policy configuration information of the current service node, and the reference weight value of the upstream service node; determining the current service node policy of the current service node according to the policy configuration information and the link policy; determining the target weight value of the current service node according to the current service node policy, the initial weight value, and the reference weight value; and obtaining the weight value distribution information of the traffic link to be processed according to the target weight values ​​of each service node of the traffic link to be processed.

[0132] One embodiment of this application implements a method that first sets a link policy for the traffic link to be processed corresponding to the target task, then determines the policy configuration information of each service node in the traffic link to be processed, and determines the current service node policy of the current service node based on the policy configuration information and the link policy. This eliminates the need to configure policies for each service node in the traffic link to be processed one by one, reducing the workload of policy configuration. Based on the initial weight value, reference weight value and current service node policy of the service node, the target weight value of the current service node is determined, thereby obtaining the weight value distribution information of the traffic link to be processed. This is beneficial for traffic regulation of the traffic link to be processed based on the weight value distribution information of the traffic link to be processed, thereby improving processing efficiency.

[0133] The following is in conjunction with the appendix Figure 6 Taking the application of the node weight value determination method provided in this application in an e-commerce scenario as an example, the node weight value determination method will be further explained. Among them, Figure 6 This application provides a flowchart illustrating a method for determining node weight values ​​in an e-commerce scenario, which includes the following steps:

[0134] Step 602: Determine the current business node of the traffic link to be processed corresponding to the target task as the product query node, the upstream business node as the order query node, and the link strategy as the default comparison strategy.

[0135] Step 604: Obtain the initial weight value and strategy configuration information of the query product node, and the reference weight value of the query order node.

[0136] Step 606: Based on the strategy configuration information, determine that the query product node is configured with a resource priority strategy.

[0137] Step 608: Based on the resource priority strategy and the default comparison strategy, determine the current business node strategy of the queried product node as the resource priority strategy.

[0138] Step 610: Based on the resource priority strategy, determine the initial weight value as the target weight value of the queried product node.

[0139] Step 612: Obtain the weight distribution information of the traffic link to be processed based on the target weight values ​​of each service node in the traffic link to be processed.

[0140] One embodiment of this application implements a method that first sets a link policy for the traffic link to be processed corresponding to the target task, then determines the policy configuration information of each service node in the traffic link to be processed, and determines the current service node policy of the current service node based on the policy configuration information and the link policy. This eliminates the need to configure policies for each service node in the traffic link to be processed one by one, reducing the workload of policy configuration. Based on the initial weight value, reference weight value and current service node policy of the service node, the target weight value of the current service node is determined, thereby obtaining the weight value distribution information of the traffic link to be processed. This is beneficial for traffic regulation of the traffic link to be processed based on the weight value distribution information of the traffic link to be processed, thereby improving processing efficiency.

[0141] Corresponding to the above method embodiments, this application also provides an embodiment of a node weight value determination device. Figure 7 A schematic diagram of a node weight value determination device according to an embodiment of this application is shown. Figure 7 As shown, the device includes:

[0142] The node determination module 702 is configured to determine the pending traffic link corresponding to the target task, as well as the current service node, upstream service node and link policy of the pending traffic link;

[0143] The acquisition module 704 is configured to acquire the initial weight value and strategy configuration information of the current business node, as well as the reference weight value of the upstream business node;

[0144] The strategy determination module 706 is configured to determine the current service node strategy of the current service node based on the strategy configuration information and the link strategy.

[0145] The weight value determination module 708 is configured to determine the target weight value of the current business node based on the current business node strategy, the initial weight value, and the reference weight value.

[0146] The acquisition module 710 is configured to obtain the weight distribution information of the traffic link to be processed based on the target weight values ​​of each service node of the traffic link to be processed.

[0147] Optionally, the strategy determination module 706 is further configured to:

[0148] Based on the policy configuration information, determine whether the current business node has a node policy configured;

[0149] If the current service node is configured with a node policy, the current service node policy of the current service node is determined from the node policy and the link policy.

[0150] If no node policy is configured on the current service node, the link policy will be determined as the current service node policy of the current service node.

[0151] Optionally, the strategy determination module 706 is further configured to:

[0152] Determine the node policy priority of the node policy and the link policy priority of the link policy;

[0153] The current business node policy is determined based on the node policy priority and the link policy priority.

[0154] Optionally, the strategy determination module 706 is further configured to:

[0155] If the priority of the node policy is higher than the priority of the link policy, the node policy is determined as the current business node policy of the current business node.

[0156] If the priority of the node policy is lower than the priority of the link policy, the link policy is determined as the current business node policy of the current business node.

[0157] Optionally, the current service node strategy includes any one of the following: resource priority strategy, traffic priority strategy, and default comparison strategy;

[0158] The weight value determination module 708 is further configured to:

[0159] If the current business node strategy includes a resource priority strategy, the initial weight value is determined to be the target weight value of the current business node.

[0160] If the current business node strategy includes a traffic priority strategy, the reference weight value is determined to be the target weight value of the current business node.

[0161] If the current business node strategy includes a default comparison strategy, the target weight value of the current business node is determined from the initial weight value and the reference weight value.

[0162] Optionally, the weight value determination module 708 is further configured to:

[0163] If the initial weight value is greater than the reference weight value, the initial weight value is determined to be the target weight value for the current business node;

[0164] If the initial weight value is less than or equal to the reference weight value, the reference weight value is determined to be the target weight value of the current business node.

[0165] Optionally, the device further includes:

[0166] The resource determination module is configured to determine the business resources corresponding to each business node in the traffic link to be processed.

[0167] The setting module is configured to set an initial weight value for each service node based on the service level of the service resources corresponding to each service node in the traffic link to be processed.

[0168] Optionally, the device further includes:

[0169] The control module is configured to control the traffic of service nodes in the target node system based on the weight distribution information of each traffic link to be processed, when the target node system meets the preset control conditions. The target node system is the node system to which any service node in each traffic link to be processed belongs.

[0170] Optionally, the control module is further configured to:

[0171] In the target node system, at least one service node to be regulated is identified, wherein the at least one service node to be regulated is deployed on different traffic links to be processed;

[0172] Obtain the target weight value of the at least one service node to be regulated in at least two traffic links to be processed;

[0173] Traffic regulation is performed on the at least one service node to be regulated based on the target weight value of the at least one service node to be regulated in at least two traffic links to be processed.

[0174] The node weight value determination device provided in this application includes: a node determination module configured to determine the traffic link to be processed corresponding to the target task, and the current service node, upstream service node, and link policy of the traffic link to be processed; an acquisition module configured to acquire the initial weight value and policy configuration information of the current service node, and the reference weight value of the upstream service node; a policy determination module configured to determine the current service node policy of the current service node according to the policy configuration information and the link policy; a weight value determination module configured to determine the target weight value of the current service node according to the current service node policy, the initial weight value, and the reference weight value; and an acquisition module configured to acquire the weight value distribution information of the traffic link to be processed according to the target weight values ​​of each service node of the traffic link to be processed.

[0175] One embodiment of this application implements a method that first sets a link policy for the traffic link to be processed corresponding to the target task, then determines the policy configuration information of each service node in the traffic link to be processed, and determines the current service node policy of the current service node based on the policy configuration information and the link policy. This eliminates the need to configure policies for each service node in the traffic link to be processed one by one, reducing the workload of policy configuration. Based on the initial weight value, reference weight value and current service node policy of the service node, the target weight value of the current service node is determined, thereby obtaining the weight value distribution information of the traffic link to be processed. This is beneficial for traffic regulation of the traffic link to be processed based on the weight value distribution information of the traffic link to be processed, thereby improving processing efficiency.

[0176] The above is a schematic scheme of a node weight value determination device according to this embodiment. It should be noted that the technical solution of this node weight value determination device and the technical solution of the node weight value determination method described above belong to the same concept. For details not described in detail in the technical solution of the node weight value determination device, please refer to the description of the technical solution of the node weight value determination method described above.

[0177] Figure 8 A structural block diagram of a computing device 800 according to an embodiment of this application is shown. The components of the computing device 800 include, but are not limited to, a memory 810 and a processor 820. The processor 820 is connected to the memory 810 via a bus 830, and a database 850 is used to store data.

[0178] The computing device 800 also includes an access device 840, which enables the computing device 800 to communicate via one or more networks 860. Examples of these networks include Public Switched Telephone Network (PSTN), Local Area Network (LAN), Wide Area Network (WAN), Personal Area Network (PAN), or combinations of communication networks such as the Internet. The access device 840 may include one or more of any type of wired or wireless network interface (e.g., a network interface controller (NIC)), such as an IEEE 802.11 Wireless Local Area Network (WLAN) wireless interface, a Wi-MAX (Worldwide Interoperability for Microwave Access) interface, an Ethernet interface, a Universal Serial Bus (USB) interface, a cellular network interface, a Bluetooth interface, a Near Field Communication (NFC) interface, and so on.

[0179] In one embodiment of this application, the aforementioned components of the computing device 800 and Figure 8 Other components, not shown, can also be connected to each other, for example, via a bus. It should be understood that... Figure 8 The block diagram of the computing device shown is for illustrative purposes only and is not intended to limit the scope of this application. Those skilled in the art can add or replace other components as needed.

[0180] The computing device 800 can be any type of stationary or mobile computing device, including mobile computers or mobile computing devices (e.g., tablet computers, personal digital assistants, laptop computers, notebook computers, netbooks, etc.), mobile phones (e.g., smartphones), wearable computing devices (e.g., smartwatches, smart glasses, etc.) or other types of mobile devices, or stationary computing devices such as desktop computers or personal computers (PCs). The computing device 800 can also be a mobile or stationary server.

[0181] The processor 820 implements the node weight value determination method when executing the computer instructions.

[0182] The above is an illustrative scheme of a computing device according to this embodiment. It should be noted that the technical solution of this computing device and the technical solution of the node weight value determination method described above belong to the same concept. For details not described in detail in the technical solution of the computing device, please refer to the description of the technical solution of the node weight value determination method described above.

[0183] An embodiment of this application also provides a computer-readable storage medium storing computer instructions that, when executed by a processor, implement the steps of the node weight value determination method described above.

[0184] The above is an illustrative scheme of a computer-readable storage medium according to this embodiment. It should be noted that the technical solution of this storage medium and the technical solution of the node weight value determination method described above belong to the same concept. For details not described in detail in the technical solution of the storage medium, please refer to the description of the technical solution of the node weight value determination method described above.

[0185] The foregoing has described specific embodiments of this application. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims may be performed in a different order than that shown in the embodiments and may still achieve the desired results. Furthermore, the processes depicted in the drawings do not necessarily require the specific or sequential order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0186] The computer instructions include computer program code, which may be in the form of source code, object code, executable file, or some intermediate form. The computer-readable medium may include: any entity or device capable of carrying the computer program code, recording media, USB flash drive, portable hard drive, magnetic disk, optical disk, computer memory, read-only memory (ROM), random access memory (RAM), electrical carrier signals, telecommunication signals, and software distribution media, etc.

[0187] It should be noted that, for the sake of simplicity, the foregoing method embodiments are all described as a series of actions. However, those skilled in the art should understand that this application is not limited to the described order of actions, as some steps may be performed in other orders or simultaneously according to this application. Furthermore, those skilled in the art should also understand that the embodiments described in the specification are preferred embodiments, and the actions and modules involved are not necessarily essential to this application.

[0188] In the above embodiments, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions of other embodiments.

[0189] The preferred embodiments disclosed above are merely illustrative of this application. The optional embodiments do not exhaustively describe all details, nor do they limit the invention to the specific implementations described. Clearly, many modifications and variations can be made based on the content of this application. These embodiments are selected and specifically described in this application to better explain the principles and practical applications of this application, thereby enabling those skilled in the art to better understand and utilize this application. This application is limited only by the claims and their full scope and equivalents.

Claims

1. A method of determining node weight values, characterized by, The method comprises the following steps: determining a to-be-processed traffic link corresponding to a target task, a current service node, an upstream service node and a link policy of the to-be-processed traffic link, wherein the link policy represents a policy configured for the to-be-processed traffic link and used for determining a weight value of each service node; obtaining an initial weight value and policy configuration information of the current service node, and a reference weight value of the upstream service node; determining a current service node policy of the current service node according to the policy configuration information and the link policy, wherein the policy configuration information represents information about whether the current service node is configured with the node policy, and the node policy represents a policy configured for the service node on the to-be-processed traffic link; determining a target weight value of the current service node according to the current service node policy, the initial weight value and the reference weight value; obtaining weight value distribution information of the to-be-processed traffic link according to target weight values of each service node of the to-be-processed traffic link.

2. The method of claim 1, wherein, The method further comprises the following steps: determining a current service node policy of the current service node according to the policy configuration information and the link policy, wherein the policy configuration information represents information about whether the current service node is configured with the node policy, and the node policy represents a policy configured for the service node on the to-be-processed traffic link; judging whether the current service node is configured with the node policy according to the policy configuration information; in a case where the current service node is configured with the node policy, determining the current service node policy of the current service node in the node policy and the link policy; 3. The method of claim 2, wherein, in a case where the current service node is not configured with the node policy, determining the link policy as the current service node policy of the current service node. The method further comprises the following steps: determining a node policy priority of the node policy and a link policy priority of the link policy; 4. The method of claim 3, wherein, determining the current service node policy of the current service node based on the node policy priority and the link policy priority. The method further comprises the following steps: in a case where the node policy priority is higher than the link policy priority, determining the node policy as the current service node policy of the current service node; 5. The method of claim 1, wherein, in a case where the node policy priority is lower than the link policy priority, determining the link policy as the current service node policy of the current service node. The current service node policy comprises any one of a resource priority policy, a traffic priority policy and a default comparison policy. The method further comprises the following steps: in a case where the current service node policy comprises the resource priority policy, determining the initial weight value as the target weight value of the current service node; in a case where the current service node policy comprises the traffic priority policy, determining the reference weight value as the target weight value of the current service node. In a case where the current service node policy comprises a default comparison policy, a target weight value of the current service node is determined from the initial weight value and the reference weight value.

6. The method of claim 5, wherein, Determining the target weight value of the current service node from the initial weight value and the reference weight value comprises: In a case where the initial weight value is greater than the reference weight value, determining the initial weight value as the target weight value of the current service node; In a case where the initial weight value is less than or equal to the reference weight value, determining the reference weight value as the target weight value of the current service node.

7. The method of claim 1, wherein, The method further comprises: Determining service resources corresponding to each service node of a to-be-processed traffic link; Setting an initial weight value for each service node according to a service level of the service resource corresponding to each service node of the to-be-processed traffic link.

8. The method of claim 1, wherein, After obtaining the weight value distribution information of the to-be-processed traffic link, the method further comprises: In a case where a target node system satisfies a preset regulation condition, performing traffic regulation on service nodes in the target node system based on the weight value distribution information of each to-be-processed traffic link, wherein the target node system is a node system to which any service node in each to-be-processed traffic link belongs.

9. The method of claim 8, wherein, Performing traffic regulation on service nodes in the target node system based on the weight value distribution information of each to-be-processed traffic link comprises: Determining at least one to-be-regulated service node in the target node system, wherein the at least one to-be-regulated service node is deployed in different to-be-processed traffic links; Obtaining target weight values of the at least one to-be-regulated service node in at least two to-be-processed traffic links; Performing traffic regulation on the at least one to-be-regulated service node based on the target weight values of the at least one to-be-regulated service node in at least two to-be-processed traffic links.

10. A node weight value determination apparatus characterized by comprising: Comprise: A node determination module configured to determine a to-be-processed traffic link corresponding to a target task, and a current service node, an upstream service node and a link policy of the to-be-processed traffic link, wherein the link policy represents a policy configured for the to-be-processed traffic link and used to determine weight values of each service node; An acquisition module configured to acquire an initial weight value and policy configuration information of the current service node, and a reference weight value of the upstream service node; A policy determination module configured to determine a current service node policy of the current service node according to the policy configuration information and the link policy, wherein the policy configuration information represents information about whether the current service node is configured with the node policy, and the node policy represents a policy configured for the service node on the to-be-processed traffic link; A weight value determination module configured to determine a target weight value of the current service node according to the current service node policy, the initial weight value and the reference weight value; An acquisition module configured to acquire weight value distribution information of the to-be-processed traffic link according to target weight values of each service node of the to-be-processed traffic link.

11. A computing device comprising a memory, a processor, and computer instructions stored on the memory and executable on the processor, wherein, The computer instructions, when executed by the processor, implement the steps of the method of any one of claims 1-9.

12. A computer-readable storage medium storing computer instructions, wherein, The computer instructions, when executed by the processor, implement the steps of the method of any one of claims 1-9.

Images