Implementation method, device, equipment, medium and product of service request

Abstract

The present disclosure provides a service request implementation method, device, equipment, medium and product. In the present disclosure, in the case of receiving a service request from a client, the current instance comprehensive parameters of each service instance in the service instance candidate set of the server cluster are obtained. In the case that the current instance comprehensive parameters of at least a first preset proportion of service instances in the service instance candidate set meet the preset instance comprehensive parameter condition, a target service instance is determined from the service instances meeting the preset instance comprehensive parameter condition. In the case that the current instance comprehensive parameters of at least a second preset proportion of service instances in the service instance candidate set do not meet the preset instance comprehensive parameter condition, the number of service instances in the service instance candidate set is updated, and a target service instance is determined from the updated service instance candidate set. The service request is executed based on the target service instance. In this way, the server resources can be fully utilized, and the waste of server resources can be avoided.

Description

Technical Field

[0001] This application belongs to the field of big data technology, specifically relating to a method, apparatus, device, medium, and product for implementing service requests. Background Technology

[0002] A Kubernetes cluster is a group of load balancers used to run containerized applications. Each server contains multiple sets of containers, which can serve as service instances based on the deployment of different applications within the cluster. When a server receives a service request, it can allocate an appropriate service instance to fulfill that request.

[0003] Generally, when a service instance on a server cannot support a service request, the server's network application framework can be adjusted to improve the server's current performance, thereby improving the performance of the service instances and allowing for the selection of a suitable instance to fulfill the request. However, this may result in underutilization of server resources, leading to a waste of server resources. Summary of the Invention

[0004] This disclosure is made in view of the above-mentioned problems. This disclosure provides a method, apparatus, device, medium, and product for implementing service requests, reducing the waste of server resources.

[0005] According to one aspect of this disclosure, a method for implementing a service request is provided, comprising:

[0006] Upon receiving a service request from a client, the current instance comprehensive parameters of each service instance in the service instance candidate set of the server cluster are obtained. The current instance comprehensive parameters are used to characterize the current performance status of the service instance, and each service instance in the service instance candidate set is a service instance that is currently allowed to receive service requests.

[0007] If at least a first preset proportion of service instances in the service instance candidate set have current instance comprehensive parameters that satisfy preset instance comprehensive parameter conditions, then a target service instance is determined from the service instances that satisfy the preset instance comprehensive parameter conditions.

[0008] If at least a second preset proportion of the service instances in the service instance candidate set do not meet the preset instance comprehensive parameter conditions for their current instance comprehensive parameters, the number of service instances in the service instance candidate set is updated, and the target service instance is determined from the updated service instance candidate set.

[0009] The service request is executed based on the target service instance.

[0010] Optionally, updating the number of service instances in the service instance candidate set and determining the target service instance from the updated service instance candidate set includes:

[0011] The change in the number of service instances in the service instance candidate set is calculated based on the current instance comprehensive parameters of each service instance in the service instance candidate set, the number of service instances in the service instance candidate set, and the threshold of the expected instance comprehensive parameters.

[0012] Based on the change amount, the number of service instances, and the redundancy of the number of service instances, the number of service instances is updated to obtain an updated service instance candidate set. The redundancy of the number of service instances is used to characterize the proportion of the number of service instances that do not meet the preset comprehensive parameter conditions in the service instance candidate set.

[0013] The service instance with the smallest comprehensive parameters in the updated service instance candidate set is selected as the target service instance.

[0014] Optionally, updating the number of service instances based on the change, the number of service instances, and the redundancy of the number of service instances includes:

[0015] If the redundancy of the number of service instances indicates that the number of service instances is insufficient, and if it is determined that the sum of the change and the number of service instances is less than the preset maximum number of cluster service instances, then service instances equal to the change are added to the service instance candidate set.

[0016] If the redundancy level of the number of service instances indicates an overabundance of service instances, and if it is determined that the difference between the change and the number of service instances is greater than a preset minimum number of cluster service instances, then service instances equal to the change are removed from the service instance candidate set.

[0017] Optionally, after calculating the change in the number of service instances in the service instance candidate set based on the current instance comprehensive parameters of each service instance in the service instance candidate set, the number of service instances in the service instance candidate set, and a threshold for the desired instance comprehensive parameters, the method further includes:

[0018] If the sum of the change and the number of service instances is greater than the preset maximum number of cluster service instances, or the difference between the number of service instances and the change is less than the preset minimum number of cluster service instances, then the current threshold of the instance running status parameter affecting the preset instance comprehensive parameter condition setting is adjusted until at least the current instance comprehensive parameter of the first preset proportion of service instances meets the preset instance comprehensive parameter condition.

[0019] Optionally, adjusting the current threshold of the instance running status parameters that affect the preset instance comprehensive parameter condition setting until at least the current instance comprehensive parameters of the first preset proportion of service instances meet the preset instance comprehensive parameter condition includes:

[0020] Based on the current instance comprehensive parameters of each service instance, the number of service instances, the threshold of the desired instance comprehensive parameters, and the current threshold of the instance running status parameters to be adjusted, calculate the first preset threshold of the instance running status parameters to be adjusted.

[0021] If at least a first preset proportion of the service instances' current instance comprehensive parameters satisfy the preset instance comprehensive parameter conditions obtained based on the first preset threshold, the first preset threshold is used as the preset threshold for the instance running status parameters to be adjusted.

[0022] Optionally, determining the target service instance from service instances that meet the preset instance comprehensive parameter conditions includes:

[0023] The service instance with the smallest comprehensive parameter in the current instance candidate set is selected as the target service instance.

[0024] Optionally, obtaining the current instance comprehensive parameters of each service instance in the service instance candidate set of the server cluster includes:

[0025] Collect the current instance running status parameters of each service instance in the service instance candidate set, which include multiple running indicator parameters;

[0026] Obtain the performance score for each of the aforementioned operational metrics parameters, whereby the performance score characterizes the service performance exhibited by the service instance in relation to the aforementioned operational metrics parameters;

[0027] Based on the weights of each of the aforementioned operational metric parameters and the aforementioned performance scores, the current instance comprehensive parameters of each of the aforementioned service instances are calculated.

[0028] According to another aspect of this disclosure, an apparatus for implementing a service request is provided, comprising:

[0029] The acquisition module is used to acquire the current instance comprehensive parameters of each service instance in the service instance candidate set of the server cluster when a service request is received from the client. The current instance comprehensive parameters are used to characterize the current performance status of the service instance, and each service instance in the service instance candidate set is a service instance that is currently allowed to receive service requests.

[0030] The first determining module is used to determine a target service instance from the service instances that satisfy the preset instance comprehensive parameter conditions when there are at least a first preset proportion of service instances in the service instance candidate set whose current instance comprehensive parameters satisfy the preset instance comprehensive parameter conditions.

[0031] The second determining module is used to update the number of service instances in the service instance candidate set when at least a second preset proportion of the service instances in the service instance candidate set do not meet the preset instance comprehensive parameter conditions, and to determine the target service instance from the updated service instance candidate set.

[0032] An execution module is used to execute the service request based on the target service instance.

[0033] According to another aspect of this disclosure, an electronic device is provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the above-described method for fulfilling the service request.

[0034] According to another aspect of this disclosure, a computer-readable storage medium is provided having a computer program stored thereon, the program being executed by a processor to implement a method for implementing the aforementioned service request.

[0035] According to another aspect of this disclosure, a computer program product is provided, including computer-readable code, or a non-volatile computer-readable storage medium carrying the computer-readable code, wherein when the computer-readable code is run in a processor of an electronic device, the processor in the electronic device executes a method for implementing the above-described service request.

[0036] In this disclosure, upon receiving a service request from a client, the current instance comprehensive parameters of each service instance in the service instance candidate set of the server cluster are obtained. These parameters characterize the current performance status of the service instances, and each service instance in the candidate set is currently allowed to receive service requests. If at least a first preset proportion of service instances in the candidate set have current instance comprehensive parameters that satisfy preset instance comprehensive parameter conditions, a target service instance is determined from these satisfying instances. If at least a second preset proportion of service instances in the candidate set do not have current instance comprehensive parameters that do not satisfy the preset instance comprehensive parameter conditions, the number of service instances in the candidate set is updated, and the target service instance is determined from the updated candidate set. The service request is then executed based on the target service instance. This method compares the current performance status of service instances using the current instance comprehensive parameters, achieving load balancing based on these parameters. Furthermore, when the candidate set cannot satisfy the preset instance comprehensive parameter conditions, the number of service instances allowed to receive service requests in the candidate set is changed, avoiding the problem of underutilization of service instances. Therefore, it reduces the waste of server resources.

[0037] It should be understood that both the foregoing general description and the following detailed description are exemplary and intended to provide further illustration of the claimed technology. Attached Figure Description

[0038] The above and other objects, features, and advantages of this disclosure will become more apparent from the more detailed description of the embodiments thereof in conjunction with the accompanying drawings. The drawings are provided to further illustrate the embodiments of this disclosure and form part of the specification. They are used together with the embodiments of this disclosure to explain the disclosure and do not constitute a limitation thereof. In the drawings, the same reference numerals generally represent the same components or steps.

[0039] Figure 1 A flowchart illustrating a method for implementing a service request provided in this disclosure.

[0040] Figure 2 Another flowchart for implementing a service request method provided in this disclosure.

[0041] Figure 3 This is a schematic diagram of a service request implementation device provided in this disclosure.

[0042] Figure 4 This is a hardware block diagram of an electronic device provided in this disclosure.

[0043] Figure 5 This is a schematic diagram of a computer program product provided in this disclosure. Detailed Implementation

[0044] To enable those skilled in the art to better understand the technical solution of this application, the application scenario of this application will be described first below.

[0045] Automated Guided Vehicle (AGV) scheduling and management applications are primarily used to achieve real-time scheduling and management of AGVs in a factory. The real-time operational status of the AGVs is achieved through autonomous data reporting by the vehicles via an HTTP interface. This interface data includes information such as the vehicle's model, operating status, battery level, and location. The data reporting interval is approximately 100 milliseconds. The scheduling and management application can be implemented using a Kubernetes cluster. A Kubernetes cluster is a set of load balancing servers used to run containerized applications. Each server contains multiple container sets, which can serve as service instances based on the deployment of different applications within the cluster. When a server receives a service request, such as a data reporting request based on the HTTP protocol, it can allocate an appropriate service instance to fulfill the request.

[0046] Because the number of AGVs can vary significantly between different factories and even different workshops within the same factory, and the number of AGVs operating at different times also differs, the pressure on the scheduling and management application from receiving reported HTTP service requests fluctuates considerably. This can lead to situations where server resources are not fully utilized. For example, when the number of service requests surges and the service instances on the server cannot support them, the server's network application framework can be adjusted to improve the server's current performance, thereby improving the performance of service instances and allowing for the selection of service instances that can meet the service requests. However, this does not change the number of service instances, resulting in a waste of service instance resources while improving the server's own performance. Conversely, when the number of service requests is low, the number of service instances remains unchanged, leading to underutilization of service instance resources. Therefore, this also results in a waste of server resources.

[0047] In this disclosure, upon receiving a service request from a client, the current instance comprehensive parameters of each service instance in the service instance candidate set of the server cluster are obtained. These parameters characterize the current performance status of the service instances, and each service instance in the candidate set is currently allowed to receive service requests. If at least a first preset proportion of service instances in the candidate set have current instance comprehensive parameters that satisfy preset instance comprehensive parameter conditions, a target service instance is determined from these satisfying instances. If at least a second preset proportion of service instances in the candidate set do not have current instance comprehensive parameters that do not satisfy the preset instance comprehensive parameter conditions, the number of service instances in the candidate set is updated, and the target service instance is determined from the updated candidate set. The service request is then executed based on the target service instance. This method compares the current performance status of service instances using the current instance comprehensive parameters, achieving load balancing based on these parameters. Furthermore, when the candidate set cannot satisfy the preset instance comprehensive parameter conditions, the number of service instances allowed to receive service requests in the candidate set is changed, avoiding the problem of underutilization of service instances. Therefore, it reduces the waste of server resources.

[0048] To make the objectives, technical solutions, and advantages of this disclosure more apparent, exemplary embodiments according to this disclosure will now be described in detail with reference to the accompanying drawings. Obviously, the described embodiments are merely some embodiments of this disclosure, and not all embodiments of this disclosure. It should be understood that this disclosure is not limited to the exemplary embodiments described herein.

[0049] Figure 1 This is a flowchart illustrating a method for implementing a service request as provided in this disclosure. Figure 1 As shown, the method includes:

[0050] S101: Upon receiving a service request from a client, obtain the current instance comprehensive parameters of each service instance in the service instance candidate set of the server cluster.

[0051] Specifically, in this embodiment, the client can be an AGV (Automated Guided Vehicle). When the AGV is performing operations, it can report service requests to the server cluster. These service requests can be data reporting requests including information such as the AGV's model, operating status, battery level, and location, enabling the server cluster to schedule and manage the AGVs. In this embodiment, the data reporting request can be implemented based on the HTTP protocol. It is understood that this disclosure does not specifically limit the implementation method of the service request.

[0052] A server cluster comprises multiple service instances. To ensure service requests execute correctly and without wasting service instance resources, an initial value can be set. Based on this preset initial value, a subset of service instances in the server cluster are added to a service instance candidate set to determine the total number of service instances in the candidate set. When a service request is subsequently received, the target service instance can be selected from the candidate set to fulfill the request. In other words, each service instance in the candidate set represents the currently authorized service instance to receive service requests.

[0053] After receiving a service request from the AGV (Automated Guided Vehicle), the server cluster obtains the current instance comprehensive parameters of each service instance in the service instance candidate set. These parameters characterize the current performance status of the service instance. In other words, the current usage of the service instance can be assessed based on these parameters. In this embodiment, a larger current instance comprehensive parameter indicates that the service instance is executing more service requests and has a higher load; conversely, a smaller parameter indicates that the service instance is executing fewer service requests and is underutilized.

[0054] S102: If at least a first preset proportion of service instances in the service instance candidate set have current instance comprehensive parameters that satisfy preset instance comprehensive parameter conditions, determine the target service instance from the service instances that satisfy the preset instance comprehensive parameter conditions.

[0055] Specifically, the preset instance comprehensive parameter conditions include a preset minimum and a preset maximum number of cluster service instances. When the current instance comprehensive parameters of a service instance are within the range of the maximum and minimum values, it indicates that the current performance status of the service instance is good. If at least a first preset proportion of service instances in the service instance candidate set have a current performance status of good, the target service instance can be determined from the service instances with a current performance status of good.

[0056] S103: If at least a second preset proportion of service instances in the service instance candidate set do not meet the preset instance comprehensive parameter conditions for their current instance comprehensive parameters, the number of service instances in the service instance candidate set is updated, and the target service instance is determined from the updated service instance candidate set.

[0057] Specifically, as mentioned earlier, when the current instance comprehensive parameters of a service instance are within the range of its maximum and minimum values, it indicates that the current performance status of the service instance is good. Similarly, when the current instance comprehensive parameters of a service instance exceed the range of its maximum or minimum values, it indicates that the service instance is overloaded or has excess load. If at least a second preset proportion of service instances in the service instance candidate set have an unhealthy current performance status, the number of service instances in the service instance candidate set needs to be updated so that the updated service instance candidate set meets the condition requirements of S102. The target service instance is then determined from the updated service instance candidate set. Each service instance in the updated service instance candidate set is a service instance currently allowed to receive service requests.

[0058] S104: Execute a service request based on the target service instance.

[0059] Specifically, a specific target service instance is used to execute service requests from the client to ensure that the service requests can be fulfilled normally.

[0060] In this disclosure, upon receiving a service request from a client, the current instance comprehensive parameters of each service instance in the service instance candidate set of the server cluster are obtained. These parameters characterize the current performance status of the service instances, and each service instance in the candidate set is currently allowed to receive service requests. If at least a first preset proportion of service instances in the candidate set have current instance comprehensive parameters that satisfy preset instance comprehensive parameter conditions, a target service instance is determined from these satisfying instances. If at least a second preset proportion of service instances in the candidate set do not have current instance comprehensive parameters that do not satisfy the preset instance comprehensive parameter conditions, the number of service instances in the candidate set is updated, and the target service instance is determined from the updated candidate set. The service request is then executed based on the target service instance. This method compares the current performance status of service instances using the current instance comprehensive parameters, achieving load balancing based on these parameters. Furthermore, when the candidate set cannot satisfy the preset instance comprehensive parameter conditions, the number of service instances allowed to receive service requests in the candidate set is changed, avoiding the problem of underutilization of service instances. Therefore, it reduces the waste of server resources.

[0061] In one possible embodiment, an exemplary method for updating the number of service instances in the service instance candidate set and determining the target service instance from the updated service instance candidate set includes:

[0062] The change in the number of service instances in the service instance candidate set is calculated based on the current instance comprehensive parameters of each service instance in the service instance candidate set, the number of service instances in the service instance candidate set, and the threshold of the expected instance comprehensive parameters.

[0063] Specifically, if the current instance's overall parameters do not meet the preset conditions, including if the current instance's overall parameters are greater than the preset maximum number of cluster service instances or less than the preset minimum number of cluster service instances, then the following conditions apply. If the parameters are greater than the maximum, it indicates that the number of service instances in the current candidate set is insufficient to support the number of service requests, requiring the addition of more service instances to expand the candidate set. If the parameters are less than the minimum, it indicates that the number of service instances in the current candidate set is excessive, and the current number of service requests does not require so many service instances, requiring the reduction of service instances to shrink the candidate set.

[0064] The change in the number of service instances in the service instance candidate set is calculated using the following formula, and the service instance candidate set is then expanded:

[0065]

[0066] Among them, T i T is the comprehensive parameter of the current instance of the i-th instance in the service instance candidate set. target Let N be the threshold for the desired comprehensive parameters of the instance, and N be the number of service instances in the current service instance candidate set. new For changes in service instances.

[0067] The change in the number of service instances in the service instance candidate set is calculated using the following formula, and the service instance candidate set is then scaled down:

[0068]

[0069] Among them, T i T is the comprehensive parameter of the current instance of the i-th instance in the service instance candidate set. tarhet Let N be the threshold for the desired comprehensive parameters of the instance, and N be the number of service instances in the current service instance candidate set. new For changes in service instances.

[0070] Then, based on the change amount, the number of service instances, and the redundancy of the number of service instances, the number of service instances is updated to obtain an updated set of service instance candidates.

[0071] Specifically, when determining the redundancy level of service instances, the number of service instances and the change in the number of service instances are used to calculate the number of service instances in the updated service instance candidate set, and the service instance candidate set is then updated to obtain the updated service instance candidate set. The redundancy level of service instances is used to characterize the proportion of service instances in the service instance candidate set that do not meet the preset comprehensive instance parameter conditions.

[0072] Furthermore, during the update of the service instance candidate set, service requests received by the server cluster can be placed in a message queue. These requests are sorted according to their acceptance timestamps. After the service instance candidate set is updated, service instances are allocated to service requests with smaller acceptance timestamps first, following the first-in-first-out (FIFO) rule of the message queue.

[0073] Then, the service instance with the smallest comprehensive parameters in the updated service instance candidate set is selected as the target service instance.

[0074] Specifically, as mentioned earlier, the smaller the overall parameters of the current instance, the better the current performance of the service instance. Therefore, in this embodiment, the service instance with the smallest overall parameters in the updated service instance candidate set can be selected as the target service instance to achieve load balancing while executing service requests.

[0075] In one possible embodiment, an exemplary method for updating the number of service instances based on the amount of change, the number of service instances, and the redundancy of the number of service instances includes:

[0076] If the redundancy of the number of service instances indicates that the number of service instances is insufficient, and if the sum of the change and the number of service instances is less than the preset maximum number of cluster service instances, then service instances equal to the change are added to the service instance candidate set.

[0077] Specifically, the redundancy level of service instances indicates an insufficient number of service instances. This means that a large proportion of the service instances in the candidate set have overall parameters exceeding the preset maximum number of cluster service instances. Currently, most service instances in the candidate set are in poor performance, and there are few healthy service instances, making it impossible to continuously allocate suitable service instances to service requests. Therefore, the candidate set of service instances can be expanded.

[0078] When scaling up, you can first sum the change and the number of service instances. If the sum is less than the preset maximum number of cluster service instances, it means that the calculated change is reasonable and the updated number of service instances is within the maximum number of service instances that the current server cluster can run at the same time. You can then add service instances equal to the change to the service instance candidate set.

[0079] For example, when the second preset ratio is 2 / 3, if the number of service instances whose current instance comprehensive parameters exceed the preset maximum number of cluster service instances exceeds 2 / 3, then it is determined that the service instance candidate set needs to be expanded. If the number of service instances in the service instance candidate set is 3, and there are currently 2 service instances whose current instance comprehensive parameters exceed the preset maximum number of cluster service instances, then the calculated change is 2. Two more service instances need to be added to the service instance candidate set.

[0080] When the redundancy of the number of service instances indicates an overabundance of service instances, if the difference between the change and the number of service instances is greater than the preset minimum number of cluster service instances, then service instances whose number is the change will be removed from the service instance candidate set.

[0081] Specifically, the redundancy level of service instances indicates an overabundance of service instances. This means that a large proportion of the service instances in the candidate set have overall parameters less than the preset minimum number of cluster service instances. Currently, most service instances in the candidate set have idle performance, resulting in underutilization of resources and wasted resources. Therefore, the candidate set of service instances can be reduced in size.

[0082] When scaling down, first calculate the difference between the number of service instances and the change in quantity. If the difference is greater than the preset minimum number of cluster service instances, the calculated change is reasonable, and the updated number of service instances is within the minimum range allowed for simultaneous operation in the current server cluster. Service instances whose quantity equals the change in quantity can then be removed from the service instance candidate set. The removed service instances stop receiving new service requests. This has no impact on currently executing service instances; they can continue executing until the service request ends.

[0083] For example, when the second preset ratio is 1 / 2, if the number of service instances whose current instance comprehensive parameters are less than the preset minimum number of cluster service instances exceeds 1 / 2, then it is determined that the service instance candidate set needs to be scaled down. If the number of service instances in the service instance candidate set is 3, and there are two service instances whose current instance comprehensive parameters are less than the preset minimum number of cluster service instances, then the calculated change is 1. One service instance needs to be removed from the service instance candidate set.

[0084] In one possible embodiment, after calculating the change in the number of service instances in the service instance candidate set based on the current instance comprehensive parameters of each service instance in the service instance candidate set, the number of service instances in the service instance candidate set, and the threshold of the desired instance comprehensive parameters, the method further includes:

[0085] If the sum of the change and the number of service instances is greater than the preset maximum number of cluster service instances, or if the difference between the number of service instances and the change is less than the preset minimum number of cluster service instances, then the current threshold of the instance running status parameter that affects the preset instance comprehensive parameter setting will be adjusted until at least the current instance comprehensive parameter of the first preset proportion of service instances meets the preset instance comprehensive parameter condition.

[0086] Specifically, if, after scaling up or down, the number of service instances in the updated service instance candidate set exceeds the preset range for the number of cluster service instances, it indicates that simply adjusting the number of service instances in the candidate set is insufficient to meet the current service requests. In this case, the current threshold of the instance running status parameters set in the server cluster may be unreasonable and needs to be adjusted until the number of service instances in the candidate set that meet the preset comprehensive instance parameter conditions reaches a first preset ratio. The current threshold of the instance running status parameters is used to regulate the performance of service instances.

[0087] For example, a method for adjusting the current threshold of instance running status parameters that affect the preset instance comprehensive parameter conditions until at least a first preset proportion of service instances' current instance comprehensive parameters meet the preset instance comprehensive parameter conditions includes:

[0088] Based on the current instance comprehensive parameters, the number of service instances, the threshold of the expected instance comprehensive parameters, and the current threshold of the instance running status parameters to be adjusted for each service instance, calculate the first preset threshold of the instance running status parameters to be adjusted.

[0089] Specifically, the instance running status parameters include multiple running indicator parameters. In this embodiment, the priority of each running indicator parameter can be set, and the running indicator parameter with higher priority can be used as the instance running status parameter to be adjusted, thereby adjusting the threshold.

[0090] The first preset threshold for the instance running status parameters to be adjusted is calculated using the following formula:

[0091]

[0092] Among them, T target T is the threshold of the expected instance synthesis parameters. i C represents the current instance comprehensive parameters for the i-th service instance. max C is the current threshold for the instance's runtime status parameters to be adjusted. new The first preset threshold is the calculated runtime status parameters of the instance to be adjusted.

[0093] If it is determined that the current instance comprehensive parameters of at least a first preset proportion of service instances meet the preset instance comprehensive parameter conditions obtained based on the first preset threshold, the first preset threshold is used as the preset threshold for the instance running status parameters to be adjusted.

[0094] Specifically, based on the priority of each operational metric parameter, the operational metric parameters are adjusted sequentially. When at least a first preset proportion of service instances' current comprehensive instance parameters meet the preset comprehensive instance parameter conditions obtained based on a first preset threshold, the first preset threshold can be used as the preset threshold for the operational status parameters of the instances to be adjusted, and the adjustment stops. By dynamically adjusting the current thresholds of instance operational status parameters in the server, it is possible to ensure that the server flexibly adapts to different business scenarios, reducing the inaccuracy of experience-based presets, and simultaneously reducing the configuration and maintenance costs of static thresholds.

[0095] For example, the current threshold settings for instance runtime status parameters include a minimum CPU utilization of 30%, a minimum memory utilization of 40%, a maximum concurrent connection count of 1000, and a minimum number of cluster service instances of 2. At a certain point, the scaling down calculation shows that the number of service instances has decreased to the minimum number of cluster service instances of 2, and the concurrent connection count per instance has reached the maximum value of 1000. However, the CPU utilization and memory utilization of the service instances are still less than the set minimum thresholds. In this case, the maximum concurrent connection count of the instance runtime status parameters should be dynamically adjusted, for example, to 2000, thereby increasing the service request pressure on each service instance and preventing resource waste.

[0096] In one possible embodiment, an exemplary method for determining a target service instance from service instances that meet preset instance comprehensive parameter conditions includes:

[0097] The service instance with the smallest comprehensive parameters in the current instance candidate set is selected as the target service instance.

[0098] Specifically, as mentioned above, the smaller the overall parameters of the current instance, the better the current performance of the service instance. In this embodiment, when selecting a target service instance, service instances with better current performance can be selected first.

[0099] For example, assuming the first preset ratio is 1 / 3, when the number of service instances that meet the preset comprehensive parameter conditions exceeds 1 / 3, it means that the current performance status of most service instances in the current service instance candidate set is healthy and can continue to execute service requests.

[0100] In one possible embodiment, an exemplary method for obtaining the current instance comprehensive parameters of each service instance in the service instance candidate set of the server cluster includes:

[0101] Collect the current instance running status parameters of each service instance in the candidate set of service instances.

[0102] Specifically, the current instance running status parameters include multiple running metrics, such as the number of cluster service instances, CPU utilization, memory usage, request rate, response time, concurrent connections, and expected instance comprehensive parameters.

[0103] In this embodiment, the current instance running status parameters of each service instance in the service instance candidate set can be collected according to a preset collection period to ensure that the service instances in the current service instance candidate set can achieve load balancing when executing service requests.

[0104] Next, obtain the performance scores for each running metric parameter.

[0105] The performance score characterizes the service performance of a service instance in terms of runtime metrics parameters. Specifically, a performance score table for runtime metrics parameters can be pre-defined, with different values ​​corresponding to different performance scores, as shown in Table 1. Table 1 shows the performance scores corresponding to CPU utilization. Based on the collected current instance runtime status parameters, the corresponding performance score is obtained from the performance score table.

[0106] Table 1 Performance scores corresponding to CPU utilization

[0107] CPU utilization (%) <50 50-80 80-90 >90 Performance score 100 80 40 10

[0108] The performance score table settings for other operating indicators are similar and will not be elaborated on here.

[0109] Then, based on the weights of each operational metric parameter and each performance score, the current instance comprehensive parameters of each service instance are calculated.

[0110] Specifically, different performance metrics parameters in the current instance's running status parameters have varying degrees of importance in calculating the overall parameters of the current instance for the service instance. Therefore, the weights of each performance metric parameter can be preset. Based on each performance score and its corresponding weight, the overall parameters of the current instance for each service instance are calculated.

[0111] The current instance comprehensive parameters for each service instance are calculated using the following formula:

[0112]

[0113] Among them, T cur_fusion For the current instance comprehensive parameters of the service instance, P cpu P is a performance score representing CPU utilization. mem P is a performance score representing memory utilization. tps P is the performance score for request rate.rt P is the performance score for response time. concurrency W is the performance score for the number of concurrent connections. cpu W is the weight for CPU utilization. mem W is the weight for memory utilization. tps W is the weight for request rate. rt As a weight for response time, W concurrency The weight for the number of concurrent connections.

[0114] Furthermore, this embodiment sets a maximum and a minimum threshold for instance running status parameters. These thresholds constrain the range of running indicator parameters, and the maximum and minimum instance comprehensive parameters can be calculated based on the maximum and minimum thresholds. The maximum and minimum instance comprehensive parameters are the maximum and minimum values ​​of preset instance comprehensive parameter conditions. The specific calculation methods for the maximum and minimum instance comprehensive parameters are the same as those described above for calculating the current instance comprehensive parameters, and will not be repeated here.

[0115] Figure 2 Another flowchart illustrating a method for implementing a service request provided in this disclosure. (Example) Figure 2 As shown, the method includes:

[0116] S201: Collect the current instance running status parameters of each service instance in the candidate service instance set.

[0117] Specifically, assume there are three service instances in the candidate service instance set: Service Instance 1, Service Instance 2, and Service Instance 3. The current runtime status parameters of each of the three service instances are collected. The runtime metrics for Service Instance 1 are: CPU utilization 95%, memory utilization 92%, request rate 240, response time 2s, and concurrent connections 600; for Service Instance 2, CPU utilization 90%, memory utilization 91%, request rate 220, response time 3s, and concurrent connections 450; and for Service Instance 3, CPU utilization 85%, memory utilization 81%, request rate 220, response time 1s, and concurrent connections 400.

[0118] S202: Calculate the current instance comprehensive parameters for each service instance.

[0119] Specifically, based on the data collected by S201, the current instance comprehensive parameter of service instance 1 is calculated to be 32; the current instance comprehensive parameter of service instance 2 is 35; and the current instance comprehensive parameter of service instance 3 is 52.

[0120] Based on the preset maximum and minimum thresholds for instance running status parameters, the maximum and minimum comprehensive instance parameters can be calculated. For example, the preset parameters could be: maximum CPU utilization of 90%, minimum CPU utilization of 60%, maximum memory utilization of 85%, minimum memory utilization of 60%, maximum request rate of 300, minimum request rate of 30, maximum response time of 3s, minimum response time of 0.1s, maximum concurrent connections of 800, and minimum concurrent connections of 20. According to the calculation formula, the minimum comprehensive instance parameter is 40, and the maximum comprehensive instance parameter is 89.

[0121] As shown in the examples above, the current instance comprehensive parameter of service instance 1 is less than the minimum instance comprehensive parameter, the current instance comprehensive parameter of service instance 2 is less than the minimum instance comprehensive parameter, and the current instance comprehensive parameter of service instance 3 is greater than the minimum instance comprehensive parameter and less than the maximum instance comprehensive parameter. In this case, service instance 1 and service instance 2 can generate alarm information.

[0122] S203: Determine the number of service instances that do not meet the preset instance comprehensive parameter conditions.

[0123] Specifically, based on the number of service instances that generated the alarm in S202, it can be determined that the number of service instances that do not meet the preset instance comprehensive parameter conditions exceeds the preset second preset ratio. Therefore, it is determined that the service instance candidate set needs to be updated.

[0124] S204: Service request temporary message queue.

[0125] Specifically, when determining to update the candidate set of service instances, it is necessary to pause the allocation of service instances for service requests and temporarily store all service requests during the pause allocation phase in a message queue.

[0126] S205: Update the number of service instances in the service instance candidate set.

[0127] Specifically, as shown in the example above, the scaling-down condition is met, and the number of service instances needs to be reduced. According to the calculation formula, one service instance needs to be reduced, and the number of service instances in the updated service instance candidate set is 2.

[0128] S206: Service request for consuming message queues.

[0129] Specifically, when updating the number of service instances and confirming that service requests can be executed normally, it is necessary to reallocate instances for service requests in the message queue.

[0130] Figure 3 This is a schematic diagram of a service request implementation apparatus provided in an embodiment of this disclosure. Figure 3As shown, the device 300 includes: an acquisition module 310, a first determination module 320, a second determination module 330, and an execution module 340.

[0131] The acquisition module 310 is used to acquire the current instance comprehensive parameters of each service instance in the service instance candidate set of the server cluster when a service request is received from the client. The current instance comprehensive parameters are used to characterize the current performance status of the service instance. Each service instance in the service instance candidate set is a service instance that is currently allowed to receive service requests.

[0132] The first determining module 320 is used to determine a target service instance from the service instances that satisfy the preset instance comprehensive parameter conditions when there are at least a first preset proportion of service instances in the service instance candidate set whose current instance comprehensive parameters satisfy the preset instance comprehensive parameter conditions.

[0133] The second determining module 330 is used to update the number of service instances in the service instance candidate set when at least a second preset proportion of the service instances in the service instance candidate set do not meet the preset instance comprehensive parameter conditions, and to determine the target service instance from the updated service instance candidate set.

[0134] Execution module 340 is used to execute the service request based on the target service instance.

[0135] Optionally, the second determining module is used to:

[0136] The change in the number of service instances in the service instance candidate set is calculated based on the current instance comprehensive parameters of each service instance in the service instance candidate set, the number of service instances in the service instance candidate set, and the threshold of the expected instance comprehensive parameters.

[0137] Based on the change amount, the number of service instances, and the redundancy of the number of service instances, the number of service instances is updated to obtain an updated service instance candidate set. The redundancy of the number of service instances is used to characterize the proportion of the number of service instances that do not meet the preset comprehensive parameter conditions in the service instance candidate set.

[0138] The service instance with the smallest comprehensive parameters in the updated service instance candidate set is selected as the target service instance.

[0139] Optionally, the second determining module is used to:

[0140] If the redundancy of the number of service instances indicates that the number of service instances is insufficient, and if it is determined that the sum of the change and the number of service instances is less than the preset maximum number of cluster service instances, then service instances equal to the change are added to the service instance candidate set.

[0141] If the redundancy level of the number of service instances indicates an overabundance of service instances, and if it is determined that the difference between the change and the number of service instances is greater than a preset minimum number of cluster service instances, then service instances equal to the change are removed from the service instance candidate set.

[0142] Optionally, the second determining module is used to:

[0143] After calculating the change in the number of service instances in the service instance candidate set based on the current instance comprehensive parameters of each service instance in the service instance candidate set, the number of service instances in the service instance candidate set, and the threshold of the expected instance comprehensive parameters, if the sum of the change and the number of service instances is greater than the preset maximum number of cluster service instances, or the difference between the number of service instances and the change is less than the preset minimum number of cluster service instances, then the current threshold of the instance running status parameters affecting the preset instance comprehensive parameter condition setting is adjusted until at least the current instance comprehensive parameters of the first preset proportion of service instances meet the preset instance comprehensive parameter condition.

[0144] Optionally, the second determining module is used to:

[0145] Based on the current instance comprehensive parameters of each service instance, the number of service instances, the threshold of the desired instance comprehensive parameters, and the current threshold of the instance running status parameters to be adjusted, calculate the first preset threshold of the instance running status parameters to be adjusted.

[0146] If at least a first preset proportion of the service instances' current instance comprehensive parameters satisfy the preset instance comprehensive parameter conditions obtained based on the first preset threshold, the first preset threshold is used as the preset threshold for the instance running status parameters to be adjusted.

[0147] Optionally, the first determining module is used to:

[0148] The service instance with the smallest comprehensive parameter in the current instance candidate set is selected as the target service instance.

[0149] Optionally, the acquisition module is used for:

[0150] Collect the current instance running status parameters of each service instance in the service instance candidate set, which include multiple running indicator parameters;

[0151] Obtain the performance score for each of the aforementioned operational metrics parameters, whereby the performance score characterizes the service performance exhibited by the service instance in relation to the aforementioned operational metrics parameters;

[0152] Based on the weights of each of the aforementioned operational metric parameters and the aforementioned performance scores, the current instance comprehensive parameters of each of the aforementioned service instances are calculated.

[0153] This application also provides an electronic device for executing the above-described method for fulfilling the service request. Please refer to... Figure 4 It illustrates a schematic diagram of an electronic device provided by some embodiments of this application. For example... Figure 4 As shown, the electronic device 4 includes: a processor 400, a memory 401, a bus 402, and a communication interface 403. The processor 400, the communication interface 403, and the memory 401 are connected via the bus 402. The memory 401 stores a computer program that can run on the processor 400. When the processor 400 runs the computer program, it executes the service request implementation method provided in any of the foregoing embodiments of this application.

[0154] The memory 401 may include high-speed random access memory (RAM) or non-volatile memory, such as at least one disk storage device. Communication between this device network element and at least one other network element is achieved through at least one communication interface 403 (which can be wired or wireless), such as the Internet, wide area network, local area network, metropolitan area network, etc.

[0155] Bus 402 can be an ISA bus, PCI bus, or EISA bus, etc. The bus can be divided into an address bus, a data bus, a control bus, etc. The memory 401 is used to store programs. After receiving an execution instruction, the processor 400 executes the program. The service request implementation method disclosed in any of the foregoing embodiments of this application can be applied to the processor 400, or implemented by the processor 400.

[0156] The processor 400 may be an integrated circuit chip with signal processing capabilities. In implementation, each step of the above method can be completed by the integrated logic circuitry in the hardware of the processor 400 or by instructions in software form. The processor 400 may be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it may also be a digital signal processor (DSP), an application-specific integrated circuit (ASIC), an off-the-shelf programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor may be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this application can be directly embodied in the execution of a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software modules may reside in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. The storage medium is located in memory 401. The processor 400 reads the information in memory 401 and, in conjunction with its hardware, completes the steps of the above method.

[0157] The electronic device provided in this application embodiment and the service request implementation method provided in this application embodiment are based on the same inventive concept and have the same beneficial effects as the methods they adopt, operate or implement.

[0158] This application also provides a computer-readable storage medium corresponding to the service request implementation method provided in the foregoing embodiments. The computer-readable storage medium shown may be an optical disc, on which a computer program is stored. When the computer program is run by a processor, it executes the service request implementation method provided in any of the foregoing embodiments.

[0159] It should be noted that examples of the computer-readable storage medium may also include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other optical and magnetic storage media, which will not be elaborated here.

[0160] The computer-readable storage medium provided in the above embodiments of this application and the service request implementation method provided in the embodiments of this application are based on the same inventive concept and have the same beneficial effects as the methods adopted, run or implemented by the application stored therein.

[0161] This application also provides a computer program product 500, such as... Figure 5 As shown. This computer program product carries a computer program 501. The instructions included in the program code can be used to execute the steps of the service request implementation method described in the above method embodiments. For details, please refer to the above method embodiments, which will not be repeated here.

[0162] The aforementioned computer program product can be implemented through hardware, software, or a combination thereof. In one optional embodiment, the computer program product is specifically embodied in a computer storage medium; in another optional embodiment, the computer program product is specifically embodied in a software product, such as a software development kit (SDK), etc.

[0163] The basic principles of this disclosure have been described above with reference to specific embodiments. However, it should be noted that the advantages, benefits, and effects mentioned in this disclosure are merely examples and not limitations, and should not be considered as essential features of each embodiment of this disclosure. Furthermore, the specific details disclosed above are for illustrative and facilitative purposes only, and are not limitations. These details do not limit the scope of this disclosure to the necessity of employing the aforementioned specific details for implementation.

[0164] The block diagrams of devices, apparatuses, devices, and systems disclosed herein are merely illustrative examples and are not intended to require or imply that they must be connected, arranged, or configured in the manner shown in the block diagrams. As those skilled in the art will recognize, these devices, apparatuses, devices, and systems can be connected, arranged, and configured in any manner. Words such as “comprising,” “including,” “having,” etc., are open-ended terms meaning “including but not limited to,” and are used interchangeably with them. The terms “or” and “and” as used herein refer to the terms “and / or,” and are used interchangeably with them unless the context clearly indicates otherwise. The term “such as” as used herein refers to the phrase “such as but not limited to,” and is used interchangeably with it.

[0165] Additionally, as used herein, the “or” used in a list of items beginning with “at least one” indicates a separate list, such that a list of, for example, “at least one of A, B, or C” means A or B or C, or AB or AC or BC, or ABC (i.e., A and B and C). Furthermore, the word “exemplary” does not imply that the described example is preferred or better than other examples.

[0166] It should also be noted that in the systems and methods of this disclosure, the components or steps can be decomposed and / or recombined. These decompositions and / or recombinations should be considered as equivalent solutions to this disclosure.

[0167] Various changes, substitutions, and modifications can be made to the technology described herein without departing from the teachings defined by the appended claims. Furthermore, the scope of the claims of this disclosure is not limited to the specific aspects of the processes, machines, manufactures, events, means, methods, and actions described above. Currently existing or later-developed processes, machines, manufactures, events, means, methods, or actions that perform substantially the same function or achieve substantially the same result as the corresponding aspects described herein can be utilized. Therefore, the appended claims include such processes, machines, manufactures, events, means, methods, or actions within their scope.

[0168] The above description of the disclosed aspects is provided to enable any person skilled in the art to make or use this disclosure. Various modifications to these aspects will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects without departing from the scope of this disclosure. Therefore, this disclosure is not intended to be limited to the aspects shown herein, but rather to be carried out within the widest scope consistent with the principles and novel features disclosed herein.

[0169] The above description has been given for purposes of illustration and description. Furthermore, this description is not intended to limit the embodiments of this disclosure to the forms disclosed herein. Although numerous exemplary aspects and embodiments have been discussed above, those skilled in the art will recognize certain variations, modifications, alterations, additions, and sub-combinations therein.

Claims

1. A method for implementing a service request, characterized in that, include: Upon receiving a service request from a client, the current instance comprehensive parameters of each service instance in the service instance candidate set of the server cluster are obtained. The current instance comprehensive parameters are used to characterize the current performance status of the service instance, and each service instance in the service instance candidate set is a service instance that is currently allowed to receive service requests. If at least a first preset proportion of service instances in the service instance candidate set have current instance comprehensive parameters that satisfy preset instance comprehensive parameter conditions, then a target service instance is determined from the service instances that satisfy the preset instance comprehensive parameter conditions. If at least a second preset proportion of the service instances in the service instance candidate set do not meet the preset instance comprehensive parameter conditions for their current instance comprehensive parameters, the number of service instances in the service instance candidate set is updated, and the target service instance is determined from the updated service instance candidate set. Execute the service request based on the target service instance; The step of updating the number of service instances in the service instance candidate set and determining the target service instance from the updated service instance candidate set includes: The change in the number of service instances in the service instance candidate set is calculated based on the current instance comprehensive parameters of each service instance in the service instance candidate set, the number of service instances in the service instance candidate set, and the threshold of the expected instance comprehensive parameters. Based on the change amount, the number of service instances, and the redundancy of the number of service instances, the number of service instances is updated to obtain an updated service instance candidate set. The redundancy of the number of service instances is used to characterize the proportion of the number of service instances that do not meet the preset comprehensive parameter conditions in the service instance candidate set. The service instance with the smallest comprehensive parameters in the updated service instance candidate set is taken as the target service instance. The method further includes, after calculating the change in the number of service instances in the service instance candidate set based on the current instance comprehensive parameters of each service instance in the service instance candidate set, the number of service instances in the service instance candidate set, and a threshold for the expected instance comprehensive parameters: If the sum of the change and the number of service instances is greater than the preset maximum number of cluster service instances, or the difference between the number of service instances and the change is less than the preset minimum number of cluster service instances, then the current threshold of the instance running status parameter affecting the preset instance comprehensive parameter condition setting is adjusted until at least the current instance comprehensive parameter of the first preset proportion of service instances meets the preset instance comprehensive parameter condition.

2. The method according to claim 1, characterized in that, The step of updating the number of service instances based on the change amount, the number of service instances, and the redundancy of the number of service instances includes: If the redundancy of the number of service instances indicates that the number of service instances is insufficient, and if it is determined that the sum of the change and the number of service instances is less than the preset maximum number of cluster service instances, then service instances equal to the change are added to the service instance candidate set. If the redundancy level of the number of service instances indicates an overabundance of service instances, and if it is determined that the difference between the change and the number of service instances is greater than a preset minimum number of cluster service instances, then service instances equal to the change are removed from the service instance candidate set.

3. The method according to claim 1, characterized in that, The step of adjusting the current threshold of the instance running status parameters that affect the preset instance comprehensive parameter conditions until at least the current instance comprehensive parameters of the first preset proportion of service instances meet the preset instance comprehensive parameter conditions includes: Based on the current instance comprehensive parameters of each service instance, the number of service instances, the threshold of the desired instance comprehensive parameters, and the current threshold of the instance running status parameters to be adjusted, calculate the first preset threshold of the instance running status parameters to be adjusted. If it is determined that at least a first preset proportion of the service instances' current instance comprehensive parameters meet the preset instance comprehensive parameter conditions obtained based on the first preset threshold, the first preset threshold is used as the preset threshold for the instance running status parameters to be adjusted.

4. The method according to claim 1, characterized in that, The step of determining the target service instance from service instances that meet the preset instance comprehensive parameter conditions includes: The service instance with the smallest comprehensive parameter in the current instance candidate set is selected as the target service instance.

5. The method according to claim 1, characterized in that, The process of obtaining the current instance comprehensive parameters of each service instance in the service instance candidate set of the server cluster includes: Collect the current instance running status parameters of each service instance in the service instance candidate set, which include multiple running indicator parameters; Obtain the performance score for each of the aforementioned operational metrics parameters, whereby the performance score characterizes the service performance exhibited by the service instance in relation to the aforementioned operational metrics parameters; Based on the weights of each of the aforementioned operational metric parameters and the aforementioned performance scores, the current instance comprehensive parameters of each of the aforementioned service instances are calculated.

6. An apparatus for implementing a service request, characterized in that, include: The acquisition module is used to acquire the current instance comprehensive parameters of each service instance in the service instance candidate set of the server cluster when a service request is received from the client. The current instance comprehensive parameters are used to characterize the current performance status of the service instance, and each service instance in the service instance candidate set is a service instance that is currently allowed to receive service requests. The first determining module is used to determine a target service instance from the service instances that satisfy the preset instance comprehensive parameter conditions when there are at least a first preset proportion of service instances in the service instance candidate set whose current instance comprehensive parameters satisfy the preset instance comprehensive parameter conditions. The second determining module is used to update the number of service instances in the service instance candidate set when at least a second preset proportion of the service instances in the service instance candidate set do not meet the preset instance comprehensive parameter conditions, and to determine the target service instance from the updated service instance candidate set. The execution module is used to execute the service request based on the target service instance; The second determining module is used for: The change in the number of service instances in the service instance candidate set is calculated based on the current instance comprehensive parameters of each service instance in the service instance candidate set, the number of service instances in the service instance candidate set, and the threshold of the expected instance comprehensive parameters. Based on the change amount, the number of service instances, and the redundancy of the number of service instances, the number of service instances is updated to obtain an updated service instance candidate set. The redundancy of the number of service instances is used to characterize the proportion of the number of service instances that do not meet the preset comprehensive parameter conditions in the service instance candidate set. The service instance with the smallest comprehensive parameters in the updated service instance candidate set is taken as the target service instance. The second determining module is used for: After calculating the change in the number of service instances in the service instance candidate set based on the current instance comprehensive parameters of each service instance in the service instance candidate set, the number of service instances in the service instance candidate set, and the threshold of the expected instance comprehensive parameters, if the sum of the change and the number of service instances is greater than the preset maximum number of cluster service instances, or the difference between the number of service instances and the change is less than the preset minimum number of cluster service instances, then the current threshold of the instance running status parameters affecting the preset instance comprehensive parameter condition setting is adjusted until at least the current instance comprehensive parameters of the first preset proportion of service instances meet the preset instance comprehensive parameter condition.

7. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, The processor executes the computer program to implement the method as described in any one of claims 1-5.

8. A computer-readable storage medium having a computer program stored thereon, characterized in that, The program is executed by a processor to implement the method as described in any one of claims 1-5.

9. A computer program product, characterized in that, Includes computer-readable code, or a non-volatile computer-readable storage medium carrying computer-readable code, wherein when the computer-readable code is run in a processor of an electronic device, the processor in the electronic device performs the actions described in any one of claims 1-5.

Images