Business request management method and device, computer device and readable storage medium

Abstract

The application relates to a service request management method and device, computer equipment, a computer readable storage medium and a computer program product. The method comprises the following steps: acquiring a request quantity threshold value, a request error rate threshold value and a request period configured for initiating a service request based on a cloud management platform; when the current period is determined to end based on the request period, determining a first request error rate of a plurality of service requests initiated by a target user in a previous period and a second request error rate of a plurality of service requests initiated by the target user in the current period; if the second request error rate is greater than the error rate threshold value and the first request error rate, performing attenuation processing on the request quantity threshold value according to the second request error rate and the first request error rate to obtain an updated quantity threshold value in a next period; and determining the updated quantity threshold value as a maximum allowed request quantity of the target user for initiating a service request based on the cloud management platform in the next period. The method can improve the flexibility of service request management.

Description

Technical Field

[0001] This application relates to the field of cloud platform technology, and in particular to a business request management method, apparatus, computer equipment, computer-readable storage medium, and computer program product. Background Technology

[0002] With the development of cloud platform technology, users can initiate business requests based on the cloud management platform. After receiving the business request, the cloud management platform will process it and deploy the corresponding services and businesses.

[0003] In traditional technologies, a fixed number of requests is usually preset for each time period in the cloud management platform. However, if there is a problem with the service or network in the cloud management platform, using a fixed number of requests may cause users to retry too many business requests, increasing the risk of network congestion and resulting in inflexible business request management. Summary of the Invention

[0004] Therefore, it is necessary to provide a business request management method, apparatus, computer equipment, computer-readable storage medium, and computer program product that can improve the flexibility of business request management in response to the above-mentioned technical problems.

[0005] Firstly, this application provides a business request management method, including:

[0006] Obtain the request quantity threshold, request error rate threshold, and request cycle configured for business requests initiated based on the cloud management platform;

[0007] If the current period ends based on the request period, determine the first request error rate of multiple business requests initiated by the target user in the previous period of the current period, and the second request error rate of multiple business requests initiated by the target user in the current period.

[0008] If the second request error rate is greater than the error rate threshold and the first request error rate, then the request quantity threshold is attenuated based on the second request error rate and the first request error rate to obtain the update quantity threshold for the next period of the current period.

[0009] The update quantity threshold is determined as the maximum allowed number of business requests initiated by the target user based on the cloud management platform in the next cycle.

[0010] In one embodiment, the request quantity threshold is attenuated based on the second request error rate and the first request error rate to obtain the update quantity threshold for the next period of the current period, including:

[0011] Obtain the historical request error rate for each of the multiple historical periods preceding the previous period;

[0012] Based on the numerical relationship between each of the historical request error rates and the first request error rate, an error rate enhancement period group is determined; the error rate enhancement period group includes the current period and the previous period of the current period; the error rate enhancement period group includes at least two consecutive request periods, and the request error rate of any enhancement period in the error rate enhancement period group other than the first request period is greater than the request error rate of the previous period of the enhancement period;

[0013] Based on the error rate enhancement period group, the second request error rate, and the first request error rate, the request quantity threshold is attenuated to obtain the update quantity threshold for the next period of the current period.

[0014] In one embodiment, the request quantity threshold is attenuated based on the error rate enhancement period group, the second request error rate, and the first request error rate to obtain the update quantity threshold for the next period of the current period, including:

[0015] The attenuation factor is determined based on the number of request cycles included in the error rate enhancement cycle group and the number of first requests corresponding to the first request cycle in the error rate enhancement cycle group.

[0016] Based on the attenuation factor, the second request error rate, and the first request error rate, the request quantity threshold is attenuated to obtain the update quantity threshold for the next period of the current period.

[0017] In one embodiment, the method further includes:

[0018] If the second request error rate is greater than the error rate threshold and less than the first request error rate, then an error rate reduction period group is determined based on the numerical relationship between each of the historical request error rates and the first request error rate; the error rate reduction period group includes the current period and the previous period of the current period; the error rate reduction period group includes at least two consecutive request periods, and the request error rate of any reduction period other than the first request period in the error rate reduction period group is less than the request error rate of the previous period of the reduction period;

[0019] Based on the error rate reduction period group, the second request error rate, and the first request error rate, the request quantity threshold is attenuated to obtain the update quantity threshold for the next period of the current period.

[0020] In one embodiment, the step of attenuating the request quantity threshold based on the error rate attenuation period group, the second request error rate, and the first request error rate to obtain the update quantity threshold for the next period of the current period includes:

[0021] The attenuation factor is determined based on the number of request cycles included in the error rate attenuation cycle group and the number of first requests corresponding to the first request cycle in the error rate attenuation cycle group.

[0022] Based on the attenuation factor, the second request error rate, and the first request error rate, the request quantity threshold is attenuated to obtain the update quantity threshold for the next period of the current period.

[0023] In one embodiment, the method further includes:

[0024] If the error rate of the second request is less than the error rate threshold, then the request quantity threshold is determined as the maximum allowed number of business requests initiated by the target user based on the cloud management platform in the next period;

[0025] If the error rate of the second request is greater than the error rate threshold and equal to the error rate of the first request, then the maximum allowed number of requests in the current period is determined as the maximum allowed number of business requests initiated by the target user based on the cloud management platform in the next period.

[0026] Secondly, this application also provides a service request management device, comprising:

[0027] The data acquisition module is used to acquire the request quantity threshold, request error rate threshold, and request cycle configured for business requests initiated based on the cloud management platform;

[0028] The error rate determination module is used to determine, when the current period is determined to have ended based on the request period, a first request error rate of multiple business requests initiated by the target user in the previous period of the current period, and a second request error rate of multiple business requests initiated by the target user in the current period.

[0029] The attenuation processing module is used to attenuate the request quantity threshold according to the second request error rate and the first request error rate if the second request error rate is greater than the error rate threshold and the first request error rate, so as to obtain the update quantity threshold of the next period of the current period.

[0030] The request quantity determination module is used to determine the update quantity threshold as the maximum allowed number of business requests initiated by the target user based on the cloud management platform in the next period.

[0031] Thirdly, this application also provides a computer device. The computer device includes a memory and a processor, the memory storing a computer program, and the processor executing the computer program to implement the steps of the method described above.

[0032] Fourthly, this application also provides a computer-readable storage medium. The computer-readable storage medium stores a computer program thereon, which, when executed by a processor, implements the steps of the method described above.

[0033] Fifthly, this application also provides a computer program product. The computer program product includes a computer program that, when executed by a processor, implements the steps of the method described above.

[0034] The aforementioned business request management method, apparatus, computer equipment, computer-readable storage medium, and computer program product acquire request quantity thresholds, request error rate thresholds, and request periods configured for business requests initiated based on a cloud management platform. This allows for the determination of the specific details of the business request configuration. Given that the current period has ended based on the request period, the method determines the first request error rate of multiple business requests initiated by the target user in the previous period and the second request error rate of multiple business requests initiated by the target user in the current period. This allows for the determination of the request error rates for the current period and the previous period. If the second request error... If the error rate is greater than the error rate threshold and the first request error rate, it indicates that the error rate of the current period is relatively high and higher than the error rate of the previous period. Therefore, it is necessary to perform attenuation processing on the request quantity threshold based on the second request error rate and the first request error rate to obtain the update quantity threshold for the next period of the current period. The update quantity threshold is determined as the maximum allowed number of business requests initiated by the target user based on the cloud management platform in the next period. This adaptively reduces the maximum allowed number of requests in the next period of the current period to avoid the situation where the number of business requests initiated is too large when the error rate is too high, which helps to improve the flexibility of business request management. Attached Figure Description

[0035] To more clearly illustrate the technical solutions in the embodiments of this application or related technologies, the drawings used in the description of the embodiments of this application or related technologies will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.

[0036] Figure 1 This is an application environment diagram of a business request management method in one embodiment;

[0037] Figure 2 This is a flowchart illustrating a business request management method in one embodiment;

[0038] Figure 3 This is a schematic diagram illustrating the change in the request error rate of a business request management method in one embodiment;

[0039] Figure 4 This is a flowchart illustrating the business request management steps in one embodiment;

[0040] Figure 5 This is a flowchart illustrating the first stage of a business request management method in one embodiment;

[0041] Figure 6 This is a flowchart illustrating the second stage of a business request management method in one embodiment;

[0042] Figure 7 This is a flowchart illustrating the third stage of a business request management method in one embodiment;

[0043] Figure 8 This is a flowchart illustrating the business request management method in another embodiment;

[0044] Figure 9 This is a structural block diagram of a service request management device in one embodiment;

[0045] Figure 10 This is an internal structural diagram of a computer device in one embodiment. Detailed Implementation

[0046] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0047] The service request management method provided in this application embodiment can be applied to, for example, Figure 1In the application environment shown, terminal 102 communicates with cloud management platform 104 via a network. Terminal 102 can be, but is not limited to, various personal computers, laptops, smartphones, tablets, IoT devices, and portable wearable devices. IoT devices can include smart speakers, smart TVs, smart air conditioners, smart in-vehicle devices, and projection devices. Portable wearable devices can include smartwatches, smart bracelets, and head-mounted displays. Head-mounted displays can be virtual reality (VR) devices, augmented reality (AR) devices, and smart glasses. Cloud management platform 104 is a centralized platform for managing cloud resources and services, providing comprehensive monitoring, deployment, configuration, and management functions for the cloud environment. Cloud management platform 104 is typically deployed on a server to support large-scale, high-availability, and scalable requirements. Specifically, during the process of managing business requests, the terminal can obtain the request quantity threshold, request error rate threshold, and request period configured for business requests initiated based on the cloud management platform 104. If the current period has ended based on the request period, the terminal determines the first request error rate and the second request error rate of multiple business requests initiated by the target user in the previous period, as well as the second request error rate of multiple business requests initiated by the target user in the current period. If the second request error rate is greater than the error rate threshold and the first request error rate, the request quantity threshold is attenuated based on the second and first request error rates to obtain the update quantity threshold for the next period. The update quantity threshold is then determined as the maximum allowed number of business requests initiated by the target user based on the cloud management platform 104 in the next period.

[0048] In one exemplary embodiment, such as Figure 2 As shown, a business request management method is provided, which can be applied to... Figure 1 Taking the terminal in the example, the explanation includes the following steps S202 to S208. Wherein:

[0049] Step S202: Obtain the request quantity threshold, request error rate threshold, and request cycle configured for business requests initiated based on the cloud management platform.

[0050] The cloud management platform is a centralized platform for managing cloud resources and services, providing comprehensive monitoring, deployment, configuration, and management capabilities for the cloud environment. It is typically deployed on the server side to support large-scale, high-availability, and scalable requirements. A business request refers to a request or instruction issued by one entity (such as an individual, organization, or system) to another entity, aimed at performing a specific business operation or obtaining a certain business service. A request quantity threshold refers to the maximum number of business requests set for a given system, service, or application. A request error rate threshold refers to the maximum allowable error rate for business requests under specific time or conditions. A request period refers to a preset request time period; for example, a request period can contain multiple time windows. Specifically, the total duration of the time period is not limited here.

[0051] Specifically, after a user initiates a business request based on the cloud management platform, the terminal needs to obtain the request quantity threshold, request error rate threshold, and request period configured for that business request to determine the specific details of the business request. It can be understood that the terminal's action of obtaining these thresholds can be either proactive or reactive. For example, the request quantity threshold obtained by the terminal could be 10 or 20 times, the request error rate threshold could be 5% or 6%, and the request period could be ten minutes or twenty minutes.

[0052] Step S204: If the current period ends based on the request period, determine the first request error rate of multiple business requests initiated by the target user in the previous period and the second request error rate of multiple business requests initiated by the target user in the current period.

[0053] Here, "current period" refers to the period ending at the current time. "Target user" refers to the user initiating the business request. "First request error rate" refers to the request error rate of multiple business requests initiated by the target user in the previous period of the current period. "Second request error rate" refers to the request error rate of multiple business requests initiated by the target user in the current period.

[0054] Specifically, such as Figure 3As shown, when the current period ends based on the request period, the terminal can obtain the number of business requests initiated by the target user in the previous period and the number of request errors. Based on the number of requests and the number of request errors, the terminal can determine the first request error rate of the multiple business requests initiated by the target user in the previous period. The terminal can also obtain the number of business requests initiated by the target user in the current period and the number of request errors. Based on the number of requests and the number of request errors, the terminal can determine the second request error rate of the multiple business requests initiated by the target user in the current period.

[0055] Step S206: If the second request error rate is greater than the error rate threshold and the first request error rate, then the request quantity threshold is attenuated according to the second request error rate and the first request error rate to obtain the update quantity threshold for the next period of the current period.

[0056] Among them, the update quantity threshold refers to the threshold of the number of requests after a certain update correction.

[0057] Specifically, after determining the first request error rate and the second request error rate, the terminal can first determine the magnitude between the second request error rate and the error rate threshold. If the second request error rate is less than the error rate threshold, the request quantity threshold is set as the update quantity threshold for the next period of the current period. If the second request error rate is greater than both the error rate threshold and the first request error rate, it means that the request error rate in the current period is higher than that in the previous period, and the second request error rate in the current period has exceeded the request error rate threshold, requiring intervention. Therefore, the request quantity threshold needs to be attenuated based on the second request error rate and the first request error rate to obtain the update quantity threshold for the next period of the current period.

[0058] In one specific embodiment, the terminal can obtain the historical request error rates of multiple historical periods preceding the previous period. Based on the numerical relationship between each historical request error rate and the first request error rate, an error rate enhancement period group is determined. This error rate enhancement period group includes the current period and the period preceding the current period. The group includes at least two consecutive request periods, and the request error rate of any enhancement period (excluding the first request period) is greater than the request error rate of the period preceding the enhancement period. Then, based on the error rate enhancement period group, the second request error rate, and the first request error rate, a request quantity threshold is attenuated to obtain the update quantity threshold for the period following the current period. In another specific embodiment, the terminal can also establish an attenuation processing model, using the second request error rate and the first request error rate as inputs. The output of this model is the update quantity threshold for the period following the current period.

[0059] Step S208 updates the quantity threshold to determine the maximum allowed number of business requests initiated by the target user based on the cloud management platform in the next cycle.

[0060] The maximum allowed number of requests refers to the maximum number of business requests that the cloud management platform can process or accept in the next cycle.

[0061] Specifically, after determining the update quantity threshold, the terminal can set the update quantity threshold as the maximum allowed number of business requests initiated by the target user based on the cloud management platform in the next cycle. That is, in the next cycle, the user can only initiate business requests based on the cloud management platform that are less than or equal to the maximum allowed number of requests.

[0062] The aforementioned business request management method obtains the request quantity threshold, request error rate threshold, and request period configured for business requests initiated based on the cloud management platform. This allows for the determination of the specific details of the business request configuration. Given that the current period has ended based on the request period, the method determines the first request error rate and the second request error rate of multiple business requests initiated by the target user in the previous period. This allows for the determination of the request error rates for the current period and the previous period. If the second request error rate is greater than both the error rate threshold and the first request error rate, it indicates that the error rate in the current period is relatively high, and higher than that in the previous period. Therefore, it is necessary to attenuate the request quantity threshold based on the second and first request error rates to obtain the update quantity threshold for the next period. This update quantity threshold is then determined as the maximum allowed number of business requests initiated by the target user based on the cloud management platform in the next period. This adaptively reduces the maximum allowed number of requests in the next period, preventing an excessive number of business requests initiated when the error rate is too high, thus improving the flexibility of business request management.

[0063] In an exemplary embodiment, the request quantity threshold is attenuated based on the second request error rate and the first request error rate to obtain the update quantity threshold for the next period of the current period. This includes: obtaining the historical request error rates of each of the previous historical periods; determining an error rate enhancement period group based on the numerical relationship between each historical request error rate and the first request error rate; and attenuating the request quantity threshold based on the error rate enhancement period group, the second request error rate, and the first request error rate to obtain the update quantity threshold for the next period of the current period.

[0064] The historical period refers to all previous request periods other than the current period and the period preceding it. The historical request error rate is the request error rate corresponding to the historical period. The error rate enhancement period group includes the current period and the period preceding it; the error rate enhancement period group includes at least two consecutive request periods, and the request error rate of any enhancement period other than the first request period in the error rate enhancement period group is greater than the request error rate of the period preceding it.

[0065] Specifically, if the request error rate increases, the maximum allowed number of requests in the next period needs to be reduced accordingly; if the request error rate decreases, the maximum allowed number of requests in the next period needs to be increased accordingly. Therefore, when the second request error rate is greater than the error rate threshold and the first request error rate, the terminal can first obtain the historical request error rates of each of the previous historical periods to determine the historical request situation corresponding to the historical period. Then, based on the numerical relationship between each historical request error rate and the first request error rate, the error rate enhancement period group is determined, thereby determining the continuous error rate enhancement situation. Finally, based on the error rate enhancement period group, the second request error rate, and the first request error rate, the request quantity threshold is attenuated to obtain the update quantity threshold for the next period of the current period.

[0066] In this embodiment, based on the numerical relationship between the error rates of each historical request and the error rate of the first request, an error rate enhancement period group is determined. This allows us to determine the continuous enhancement of the error rate corresponding to the current period, and then determine the update quantity threshold for the next period. This enables us to flexibly adjust the maximum allowed number of business requests in the next period according to the changes in the error rate.

[0067] In an exemplary embodiment, the request quantity threshold is attenuated based on the error rate enhancement period group, the second request error rate, and the first request error rate to obtain the update quantity threshold for the next period of the current period. This includes: determining an attenuation factor based on the number of request periods included in the error rate enhancement period group and the number of first requests corresponding to the first request period in the error rate enhancement period group; and attenuating the request quantity threshold based on the attenuation factor, the second request error rate, and the first request error rate to obtain the update quantity threshold for the next period of the current period.

[0068] Here, the first request quantity refers to the maximum allowed request quantity corresponding to the first request period in the error rate enhancement period group. In this embodiment, the principle for updating the maximum allowed request quantity is based on an exponential function decay, as shown in the following formula:

[0069]

[0070] Where ml is the request quantity threshold, t represents the decay factor, which is gradually increased by 1 from 1 to s, p1 represents the first request error rate corresponding to the first p consecutive time windows, pn represents the second request error rate corresponding to the nth p consecutive time windows, and n takes values ​​greater than 1, such as 2, 3, 4, 5, ..., and neither p1 nor pn is 0.

[0071] Specifically, the terminal can determine the consecutive number of error rate enhancements based on the number of request cycles included in the error rate enhancement cycle group. Then, based on the number of first requests corresponding to the first request cycle in the error rate enhancement cycle group, it can determine the first decay factor corresponding to the first request cycle. Based on the first decay factor and the consecutive number of enhancements, a decay factor t is determined. Finally, based on the decay factor t, the second request error rate pn, and the first cycle request error rate p1, the request quantity threshold ml is decayed to determine the update quantity threshold for the next cycle. It can be understood that when a user makes only two request cycles of business requests, the first cycle request error rate is the first request error rate. When a user makes more than two request cycles of business requests, the first cycle request error rate needs to be actively obtained.

[0072] In this embodiment, the attenuation factor is determined based on the number of request cycles included in the error rate enhancement cycle group and the number of first requests corresponding to the first request cycle in the error rate enhancement cycle group. Finally, the update quantity threshold for the next cycle is determined based on the attenuation factor. The update quantity threshold for the next cycle can be flexibly and adaptively adjusted based on the update changes of the request error rate, thereby improving the flexibility of business request management.

[0073] In an exemplary embodiment, the business request management method further includes: if the second request error rate is greater than the error rate threshold and less than the first request error rate, then an error rate reduction period group is determined based on the numerical relationship between each historical request error rate and the first request error rate; the error rate reduction period group includes the current period and the previous period of the current period.

[0074] The error rate reduction period group includes at least two consecutive request periods, and the request error rate of any reduction period other than the first request period in the error rate reduction period group is less than the request error rate of the previous period of the reduction period. Based on the error rate reduction period group, the second request error rate and the first request error rate, the request quantity threshold is attenuated to obtain the update quantity threshold of the next period of the current period.

[0075] Specifically, if the request error rate decreases, the maximum allowed number of requests in the next cycle needs to be increased adaptively; if the request error rate increases, the maximum allowed number of requests in the next cycle needs to be decreased adaptively. Therefore, when the second request error rate is greater than the error rate threshold but less than the first request error rate, the terminal can determine the error rate reduction cycle group based on the numerical relationship between each historical request error rate and the first request error rate, thereby determining the continuous error rate reduction. Finally, based on the error rate reduction cycle group, the second request error rate, and the first request error rate, the request quantity threshold is attenuated to obtain the update quantity threshold for the next cycle of the current cycle. It can be understood that the request quantity threshold is the maximum allowed number of requests corresponding to each request cycle. The adjusted update quantity threshold can only be less than or equal to this request quantity threshold. Therefore, even if the request error rate decreases, the request quantity threshold is still being attenuated; only the attenuation factor decreases. Correspondingly, in the exponential decay function, the update quantity threshold increases.

[0076] In this embodiment, based on the numerical relationship between the error rates of each historical request and the error rate of the first request, the error rate reduction period group is determined. This allows us to determine the continuous reduction of the error rate corresponding to the current period, and thus determine the update quantity threshold for the next period. This enables us to flexibly adjust the maximum allowed number of business requests in the next period according to the changes in the error rate.

[0077] In an exemplary embodiment, the request quantity threshold is attenuated based on the error rate reduction period group, the second request error rate, and the first request error rate to obtain the update quantity threshold for the next period of the current period. This includes: determining an attenuation factor based on the number of request periods included in the error rate reduction period group and the number of first requests corresponding to the first request period in the error rate reduction period group; and attenuating the request quantity threshold based on the attenuation factor, the second request error rate, and the first request error rate to obtain the update quantity threshold for the next period of the current period.

[0078] Specifically, the terminal can determine the number of consecutive error rate reductions based on the number of request cycles included in the error rate reduction cycle group. Then, based on the number of requests corresponding to the first request cycle in the error rate reduction cycle group, it can determine the first attenuation factor for the first request cycle. Based on the first attenuation factor and the number of consecutive reductions, a attenuation factor t is determined. Finally, based on the attenuation factor t, the second request error rate pn, and the first cycle request error rate p1, the request quantity threshold ml is attenuated to determine the update quantity threshold for the next cycle. It can be understood that when a user makes only two request cycles of business requests, the first cycle request error rate is the first request error rate. When a user makes more than two request cycles of business requests, the first cycle request error rate needs to be actively obtained.

[0079] In this embodiment, the attenuation factor is determined based on the number of request cycles included in the error rate reduction cycle group and the number of first requests corresponding to the first request cycle in the error rate reduction cycle group. Finally, the update quantity threshold for the next cycle is determined based on the attenuation factor. The update quantity threshold for the next cycle can be flexibly and adaptively adjusted based on the update changes of the request error rate, thereby improving the flexibility of business request management.

[0080] In an exemplary embodiment, the business request management method further includes: if the second request error rate is less than the error rate threshold, then the request quantity threshold is determined as the maximum allowed number of business requests initiated by the target user based on the cloud management platform in the next period; if the second request error rate is greater than the error rate threshold and equal to the first request error rate, then the maximum allowed number of requests in the current period is determined as the maximum allowed number of business requests initiated by the target user based on the cloud management platform in the next period.

[0081] Specifically, if the error rate of the second request is less than the error rate threshold, it is considered that the error rate of the second request is low, and there is no need to change the maximum allowed number of requests in the next period. Therefore, the request number threshold is set as the maximum allowed number of business requests initiated by the target user based on the cloud management platform in the next period. If the error rate of the second request is greater than the error rate threshold and equal to the error rate of the first request, the error rate of the table request is relatively stable, and the maximum allowed number of requests in the current period can be set as the maximum allowed number of business requests initiated by the target user based on the cloud management platform in the next period.

[0082] In this embodiment, the maximum allowed number of requests in the next cycle can be flexibly changed according to the changes in the error rate of the second request, which can improve the flexibility of business request management.

[0083] In a specific embodiment, such as Figure 4 As shown, after determining the error rate of the second request and the error rate of the first request, the specific steps to be performed are as follows:

[0084] Step S401: Determine whether the error rate of the second request is greater than the error rate threshold;

[0085] If not, proceed to step S402 to determine the request quantity threshold as the maximum allowed number of business requests initiated by the target user based on the cloud management platform in the next cycle.

[0086] If so, proceed to step S403 to determine whether the error rate of the second request is greater than the error rate of the first request;

[0087] If not, proceed to step S404 to obtain the historical request error rates of each of the previous historical periods; determine the error rate reduction period group based on the numerical relationship between each historical request error rate and the first request error rate; and perform attenuation processing on the request quantity threshold based on the error rate reduction period group, the second request error rate, and the first request error rate to obtain the update quantity threshold of the next period of the current period.

[0088] If so, proceed to step S405 to obtain the historical request error rates of each of the previous historical periods; determine the error rate enhancement period group based on the numerical relationship between each historical request error rate and the first request error rate; and perform attenuation processing on the request quantity threshold based on the error rate enhancement period group, the second request error rate, and the first request error rate to obtain the update quantity threshold for the next period of the current period.

[0089] In one specific embodiment, a business request management method for a specific implementation scenario is provided, including:

[0090] Methods for calculating Redis error rates:

[0091] S01. Count the total number of requests at fixed time intervals;

[0092] S02. Count the total number of request errors at fixed time intervals;

[0093] S03. Error rate ev = error / total;

[0094] Overall process:

[0095] S01. Request quantity threshold ml;

[0096] S02. Minimum number of requests nl;

[0097] S03. Request error rate threshold el;

[0098] S04. Maximum allowed number of requests: newm;

[0099] S05. The error rate of the first time window is denoted by ev1, and so on, the error rate of the p-th time window is denoted by evp;

[0100] S06. After receiving a user request, the cloud management platform queries Redis and calculates the average error rate aev = (ev1 + ev2 + ev3 + ... + evp) / p for the current consecutive p time windows;

[0101] S07. If the average error rate aev=0, then directly set newm=ml;

[0102] S08. Determine the relationship between the second request error rate and the request error rate threshold el. If it is less than or equal to el, the maximum number of retries remains unchanged at newm=ml, and then newm request retries are performed. At the same time, update newm, the request period, and the request error rate of the current p time windows.

[0103] S09. If the number of requests is greater than el, the current maximum allowed number of requests is reset according to the exponential decay dynamic strategy, and then newm requests are retried; at the same time, newm, the request period, and the request error rate of the current p time windows are updated.

[0104] S10. Execute sequentially, dynamically changing the maximum allowed number of requests.

[0105] Specifically, taking a practical example, the implementation is divided into three stages.

[0106] like Figure 5 As shown, this is stage one:

[0107] S01. The first request quantity refers to the maximum allowed request quantity corresponding to the first request period in the error rate enhancement period group. In this embodiment, the principle for updating the maximum allowed request quantity is based on an exponential function decay, as follows:

[0108]

[0109] Where ml is the request quantity threshold, t represents the decay factor, which is gradually increased by 1 from 1 to s, p1 represents the first request error rate corresponding to the first p consecutive time windows, pn represents the second request error rate corresponding to the nth p consecutive time windows, and n takes values ​​greater than 1, such as 2, 3, 4, 5, ..., and neither p1 nor pn is 0.

[0110] S02.p2 represents the request error rate from the current time window to the previous p time windows, that is, the second request error rate. p1 represents the request error rate of the first request period p time windows, that is, the first period request error rate. When p2 is greater than p1, the maximum allowed number of requests is set to newm=f(1).

[0111] like Figure 6 As shown, this is stage two:

[0112] S01. Assume p2 is the current period, and p3 is the request error rate of p time windows in the next period after the current period;

[0113] S02.p2 represents p2 in stage 1;

[0114] S03. When p3>p2, then continue to reduce the maximum number of retries newm=f(2);

[0115] S04. Repeat the above process. If p4 is still greater than p3 next, continue to reduce the maximum allowed request quantity newm = f(3) until newm <= nl;

[0116] S05. In the subsequent process, once newm <= nl, stop reducing the maximum allowed request quantity and set newm = nl;

[0117] As Figure 7 shown, it is stage three:

[0118] S01. p4 represents the request error rate of p time windows in the subsequent cycle of p3;

[0119] S02. p3 represents p3 in stage 2;

[0120] S03. When p4 < p3, modify and increase the maximum number of retries newm = f(1);

[0121] S04. Repeat the above process. If p5 is still less than p4 next, continue to increase the maximum allowed request quantity newm = f(0) = ml;

[0122] S05. In the subsequent process, once newm = ml, stop increasing the maximum allowed request quantity.

[0123] In a specific embodiment, as Figure 8 shown, a service request management method is further provided, including:

[0124] Step S801, obtain the request quantity threshold, request error rate threshold, and request cycle configured for the service requests initiated based on the cloud management platform;

[0125] Step S802, when it is determined that the current cycle ends based on the request cycle, determine the first request error rate of multiple service requests initiated by the target user in the previous cycle of the current cycle, and the second request error rate of multiple service requests initiated by the target user in the current cycle;

[0126] Step S803, if the second request error rate is greater than the error rate threshold and the first request error rate, obtain the historical request error rates of multiple historical cycles before the previous cycle;

[0127] Step S804, determine the error rate enhancement cycle group according to the numerical relationship between each historical request error rate and the first request error rate;

[0128] The error rate enhancement period group includes the current period and the previous period; the error rate enhancement period group includes at least two consecutive request periods, and the request error rate of any enhancement period other than the first request period in the error rate enhancement period group is greater than the request error rate of the previous period of the enhancement period.

[0129] Step S805: Determine the attenuation factor based on the number of request cycles contained in the error rate enhancement cycle group and the number of first requests corresponding to the first request cycle in the error rate enhancement cycle group;

[0130] Step S806: Based on the decay factor, the second request error rate and the first request error rate, the request quantity threshold is decayed to obtain the update quantity threshold for the next period of the current period.

[0131] Step S807: If the error rate of the second request is greater than the error rate threshold and less than the error rate of the first request, then determine the error rate reduction cycle group based on the numerical relationship between each historical request error rate and the error rate of the first request.

[0132] The error rate reduction period group includes the current period and the previous period; the error rate reduction period group includes at least two consecutive request periods, and the request error rate of any reduction period other than the first request period in the error rate reduction period group is less than the request error rate of the previous period of the reduction period.

[0133] Step S808: Determine the attenuation factor based on the number of request cycles contained in the error rate attenuation cycle group and the number of first requests corresponding to the first request cycle in the error rate attenuation cycle group;

[0134] Step S809: Based on the decay factor, the second request error rate and the first request error rate, the request quantity threshold is decayed to obtain the update quantity threshold for the next period of the current period.

[0135] Step S810: Update the quantity threshold and determine it as the maximum allowed number of business requests initiated by the target user based on the cloud management platform in the next cycle.

[0136] Step S811: If the error rate of the second request is less than the error rate threshold, then the request quantity threshold is determined as the maximum allowed number of business requests initiated by the target user based on the cloud management platform in the next cycle.

[0137] Step S812: If the error rate of the second request is greater than the error rate threshold and equal to the error rate of the first request, then the maximum number of allowed requests in the current period is determined as the maximum number of allowed business requests initiated by the target user based on the cloud management platform in the next period.

[0138] It should be understood that although the steps in the flowcharts of the above embodiments are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the above embodiments may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages of other steps.

[0139] Based on the same inventive concept, this application also provides a business request management device for implementing the business request management method described above. The solution provided by this device is similar to the implementation described in the above method; therefore, the specific limitations in one or more business request management device embodiments provided below can be found in the limitations of the business request management method described above, and will not be repeated here.

[0140] In one exemplary embodiment, such as Figure 9 As shown, a business request management device 900 is provided, including: a data acquisition module 902, an error rate determination module 904, an attenuation processing module 906, and a request quantity determination module 908, wherein:

[0141] The data acquisition module 902 is used to acquire the request quantity threshold, request error rate threshold, and request cycle configured for business requests initiated based on the cloud management platform;

[0142] Error rate determination module 904 is used to determine the first request error rate and the second request error rate of multiple business requests initiated by the target user in the previous period of the current period, when the current period is determined to have ended based on the request period.

[0143] The attenuation processing module 906 is used to attenuate the request quantity threshold based on the second request error rate and the first request error rate if the second request error rate is greater than the error rate threshold and the first request error rate, so as to obtain the update quantity threshold of the next period of the current period.

[0144] The request quantity determination module 908 is used to determine the update quantity threshold as the maximum allowed number of business requests initiated by the target user based on the cloud management platform in the next cycle.

[0145] In one exemplary embodiment, the attenuation processing module 906 includes:

[0146] The request error rate determination unit is used to obtain the historical request error rates for each of the previous historical periods.

[0147] The period group determination unit is used to determine the error rate enhancement period group based on the numerical relationship between the error rates of each historical request and the first request error rate. The error rate enhancement period group includes the current period and the previous period of the current period. The error rate enhancement period group includes at least two time-continuous request periods, and the request error rate of any enhancement period other than the first request period in the error rate enhancement period group is greater than the request error rate of the previous period of the enhancement period.

[0148] The first attenuation processing unit is used to attenuate the request quantity threshold based on the error rate enhancement cycle group, the second request error rate, and the first request error rate to obtain the update quantity threshold for the next cycle of the current cycle.

[0149] In one exemplary embodiment, the first attenuation processing unit is specifically used for:

[0150] The attenuation factor is determined based on the number of request cycles contained in the error rate enhancement cycle group and the number of the first request corresponding to the first request cycle in the error rate enhancement cycle group.

[0151] Based on the decay factor, the second request error rate, and the first request error rate, the request quantity threshold is decayed to obtain the update quantity threshold for the next period of the current period.

[0152] In one exemplary embodiment, the service request management device 900 further includes an error rate reduction cycle group determination module, comprising:

[0153] The error rate reduction cycle group determination unit is used to determine the error rate reduction cycle group based on the numerical relationship between each historical request error rate and the first request error rate if the second request error rate is greater than the error rate threshold and less than the first request error rate. The error rate reduction cycle group includes the current cycle and the previous cycle of the current cycle. The error rate reduction cycle group includes at least two time-continuous request cycles, and the request error rate of any reduction cycle other than the first request cycle in the error rate reduction cycle group is less than the request error rate of the previous cycle of the reduction cycle.

[0154] The second attenuation processing unit is used to attenuate the request quantity threshold according to the error rate attenuation period group, the second request error rate and the first request error rate to obtain the update quantity threshold of the next period of the current period.

[0155] In one exemplary embodiment, the second attenuation processing unit is specifically used for:

[0156] The attenuation factor is determined based on the number of request cycles contained in the error rate attenuation cycle group and the number of the first request corresponding to the first request cycle in the error rate attenuation cycle group.

[0157] Based on the decay factor, the second request error rate, and the first request error rate, the request quantity threshold is decayed to obtain the update quantity threshold for the next period of the current period.

[0158] In an exemplary embodiment, the service request management device 900 further includes a second request error rate judgment module, specifically used for:

[0159] If the error rate of the second request is less than the error rate threshold, then the request quantity threshold is determined as the maximum allowed number of business requests initiated by the target user based on the cloud management platform in the next cycle.

[0160] If the error rate of the second request is greater than the error rate threshold and equal to the error rate of the first request, then the maximum number of allowed requests in the current period will be determined as the maximum number of allowed business requests initiated by the target user based on the cloud management platform in the next period.

[0161] Each module in the aforementioned business request management device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in or independent of the processor in a computer device, or stored in the memory of a computer device as software, so that the processor can invoke and execute the operations corresponding to each module.

[0162] In one exemplary embodiment, a computer device is provided, which may be a terminal, and its internal structure diagram may be as follows: Figure 10As shown, the computer device includes a processor, memory, input / output interfaces, a communication interface, a display unit, and an input device. The processor, memory, and input / output interfaces are connected via a system bus, and the communication interface, display unit, and input device are also connected to the system bus via the input / output interfaces. The processor provides computing and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system and computer programs. The internal memory provides an environment for the operation of the operating system and computer programs stored in the non-volatile storage media. The input / output interfaces are used for exchanging information between the processor and external devices. The communication interface is used for wired or wireless communication with external terminals; wireless communication can be achieved through Wi-Fi, mobile cellular networks, Near Field Communication (NFC), or other technologies. When executed by the processor, the computer program implements a business request management method. The display unit is used to form a visually visible image and can be a display screen, a projection device, or a virtual reality imaging device. The display screen can be an LCD screen or an e-ink screen. The input device of the computer device can be a touch layer covering the display screen, or buttons, trackballs, or touchpads set on the casing of the computer device, or external keyboards, touchpads, or mice, etc.

[0163] Those skilled in the art will understand that Figure 10 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0164] In one embodiment, a computer device is provided, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the steps of the method described above.

[0165] In one embodiment, a computer-readable storage medium is provided having a computer program stored thereon, which, when executed by a processor, implements the steps of the above-described method.

[0166] In one embodiment, a computer program product is provided, including a computer program that, when executed by a processor, implements the steps of the method described above.

[0167] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of the relevant data must comply with relevant regulations.

[0168] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium. When executed, the computer program can include the processes of the embodiments of the above methods. Any references to memory, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile memory and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM). The databases involved in the embodiments provided in this application may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this application may be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, artificial intelligence (AI) processors, etc., and are not limited to these.

[0169] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this application.

[0170] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are specific and detailed, they should not be construed as limiting the scope of this patent application. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this application should be determined by the appended claims.

Claims

1. A business request management method, characterized in that, The method includes: Obtain the request quantity threshold, request error rate threshold, and request cycle configured for business requests initiated based on the cloud management platform; If the current period ends based on the request period, determine the first request error rate of multiple business requests initiated by the target user in the previous period of the current period, and the second request error rate of multiple business requests initiated by the target user in the current period. If the second request error rate is less than the error rate threshold, then the request quantity threshold is set to the update quantity threshold of the next period of the current period; If the second request error rate is greater than the error rate threshold and the first request error rate, then obtain the historical request error rates of each of the multiple historical periods prior to the previous period; An error rate enhancement period group is determined based on the numerical relationship between each historical request error rate and the first request error rate. The error rate enhancement period group includes the current period and the previous period of the current period. The error rate enhancement period group includes at least two consecutive request periods, and the request error rate of any enhancement period other than the first request period in the error rate enhancement period group is greater than the request error rate of the previous period of the enhancement period. The historical period refers to the remaining request periods that have already been performed, excluding the current period and the previous period of the current period. Based on the error rate enhancement period group, the second request error rate, and the first request error rate, the request quantity threshold is attenuated to obtain the update quantity threshold for the next period of the current period; The update quantity threshold is determined as the maximum allowed number of business requests initiated by the target user based on the cloud management platform in the next cycle.

2. The method according to claim 1, characterized in that, The step of attenuating the request quantity threshold based on the error rate enhancement period group, the second request error rate, and the first request error rate to obtain the update quantity threshold for the next period of the current period includes: The attenuation factor is determined based on the number of request cycles included in the error rate enhancement cycle group and the number of first requests corresponding to the first request cycle in the error rate enhancement cycle group. Based on the attenuation factor, the second request error rate, and the first request error rate, the request quantity threshold is attenuated to obtain the update quantity threshold for the next period of the current period.

3. The method according to claim 1, characterized in that, The method further includes: If the second request error rate is greater than the error rate threshold and less than the first request error rate, then an error rate reduction period group is determined based on the numerical relationship between each of the historical request error rates and the first request error rate; the error rate reduction period group includes the current period and the previous period of the current period; the error rate reduction period group includes at least two consecutive request periods, and the request error rate of any reduction period other than the first request period in the error rate reduction period group is less than the request error rate of the previous period of the reduction period; Based on the error rate reduction period group, the second request error rate, and the first request error rate, the request quantity threshold is attenuated to obtain the update quantity threshold for the next period of the current period.

4. The method according to claim 3, characterized in that, The step of attenuating the request quantity threshold based on the error rate reduction period group, the second request error rate, and the first request error rate to obtain the update quantity threshold for the next period of the current period includes: The attenuation factor is determined based on the number of request cycles included in the error rate attenuation cycle group and the number of first requests corresponding to the first request cycle in the error rate attenuation cycle group. Based on the attenuation factor, the second request error rate, and the first request error rate, the request quantity threshold is attenuated to obtain the update quantity threshold for the next period of the current period.

5. The method according to claim 1, characterized in that, The method further includes: If the error rate of the second request is less than the error rate threshold, then the request quantity threshold is determined as the maximum allowed number of business requests initiated by the target user based on the cloud management platform in the next period; If the error rate of the second request is greater than the error rate threshold and equal to the error rate of the first request, then the maximum allowed number of requests in the current period is determined as the maximum allowed number of business requests initiated by the target user based on the cloud management platform in the next period.

6. A service request management device, characterized in that, The device includes: The data acquisition module is used to acquire the request quantity threshold, request error rate threshold, and request cycle configured for business requests initiated based on the cloud management platform; The error rate determination module is used to determine, when the current period is determined to have ended based on the request period, a first request error rate of multiple business requests initiated by the target user in the previous period of the current period, and a second request error rate of multiple business requests initiated by the target user in the current period. If the second request error rate is less than the error rate threshold, then the request quantity threshold is set to the update quantity threshold of the next period of the current period; The attenuation processing module includes: The request error rate determination unit is configured to obtain the historical request error rates of each of the multiple historical periods prior to the previous period if the second request error rate is greater than the error rate threshold and the first request error rate. A period group determination unit is used to determine an error rate enhancement period group based on the numerical relationship between each of the historical request error rates and the first request error rate; the error rate enhancement period group includes the current period and the previous period of the current period; the error rate enhancement period group includes at least two time-continuous request periods, and the request error rate of any enhancement period other than the first request period in the error rate enhancement period group is greater than the request error rate of the previous period of the enhancement period; historical periods refer to the remaining request periods that have already occurred, excluding the current period and the previous period of the current period; The first attenuation processing unit is used to perform attenuation processing on the request quantity threshold according to the error rate enhancement cycle group, the second request error rate and the first request error rate, to obtain the update quantity threshold of the next cycle of the current cycle. The request quantity determination module is used to determine the update quantity threshold as the maximum allowed number of business requests initiated by the target user based on the cloud management platform in the next period.

7. The apparatus according to claim 6, characterized in that, The first attenuation processing unit is specifically used for: The attenuation factor is determined based on the number of request cycles included in the error rate enhancement cycle group and the number of first requests corresponding to the first request cycle in the error rate enhancement cycle group. Based on the attenuation factor, the second request error rate, and the first request error rate, the request quantity threshold is attenuated to obtain the update quantity threshold for the next period of the current period.

8. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 5.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 5.

10. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 5.

Images