Information configuration method and device, equipment and storage medium

Abstract

The invention discloses an information configuration method and device, equipment and a storage medium, and belongs to the technical field of Internet. The method is executed by a management server, the management server is used for providing flow control for at least two service servers deployed in a distributed mode, and the method comprises the steps that flow control quota information is sent, and the flow control quota information is used for indicating flow quota limitation for the service servers; receiving traffic data sent by the service server based on the information reporting period, wherein the traffic data is used for indicating the amount of service requests received by the service server in at least one information reporting period before the current reporting time of sending the traffic data; and under the condition that a first interval between the current reporting time corresponding to the flow data and the last reporting time of the service server exceeds a disaster tolerance threshold value, flow control reset information is sent to the service server, and the flow control reset information is used for indicating that the flow quota limit of the service server is reset to be a preset limit.

Description

Technical Field

[0001] The present application relates to the field of Internet technology, and in particular to an information configuration method, device, equipment and storage medium. Background Art

[0002] Traffic control is used to protect business servers and prevent them from crashing due to a sharp increase in business requests.

[0003] In the related art, a management server provides flow control to a service server. When the amount of service requests received by the service server exceeds the flow control limit, the service server will no longer provide service and inform the sender of the service request.

[0004] However, due to the influence of network fluctuations and other problems, the management server cannot transmit information to the business server in a timely manner. How the management server configures the traffic quota limit provided to the business server is an urgent problem to be solved. Summary of the invention

[0005] The present application provides an information configuration method, apparatus, device and storage medium, and the technical solution is as follows:

[0006] According to one aspect of the present application, there is provided an information configuration method, the method being executed by a management server, the management server being used to provide traffic control for at least two distributed deployed service servers, the method comprising:

[0007] Sending flow control quota information, where the flow control quota information is used to indicate a flow quota limit for the service server;

[0008] Receiving traffic data sent by the service server based on an information reporting period, the traffic data being used to indicate the amount of service requests received by the service server in at least one of the information reporting periods before the current reporting time of sending the traffic data;

[0009] When a first interval between the current reporting time corresponding to the traffic data and the last reporting time of the business server exceeds a disaster recovery threshold, flow control reset information is sent to the business server, and the flow control reset information is used to indicate that the traffic quota limit of the business server is reset to a preset limit.

[0010] According to another aspect of the present application, an information configuration method is provided, the method is performed by a service server, there are at least two distributed deployed service servers and flow control is provided by a management server, the method includes:

[0011] Determining the traffic quota limit of the service server according to the traffic control quota information, wherein the traffic control quota information is sent by the management server;

[0012] Reporting traffic data to the management server based on an information reporting period, the traffic data being used to indicate the amount of service requests received by the service server in at least one of the information reporting periods before the current reporting time of sending the traffic data;

[0013] The traffic quota limit of the business server is reset to a preset limit according to the flow control reset information, and the flow control reset information is sent by the management server when the first interval between the current reporting time corresponding to the traffic data and the last reporting time of the business server exceeds the disaster recovery threshold.

[0014] According to another aspect of the present application, an information configuration device is provided, the device is applied to a management server, the management server is used to provide flow control for at least two distributed deployed service servers, the device comprising:

[0015] A first sending module, used for sending flow control quota information, where the flow control quota information is used for indicating a flow quota limit for the service server;

[0016] A receiving module, used to receive the traffic data sent by the service server based on the information reporting period, wherein the traffic data is used to indicate the amount of service requests received by the service server in at least one of the information reporting periods before the current reporting time of sending the traffic data;

[0017] The first sending module is also used to send flow control reset information to the business server when a first interval between the current reporting time corresponding to the traffic data and the last reporting time of the business server exceeds a disaster recovery threshold. The flow control reset information is used to indicate that the traffic quota limit of the business server is reset to a preset limit.

[0018] In an optional design of the present application, the first sending module is further used for:

[0019] Obtaining an influence coefficient of the business server;

[0020] When the first interval exceeds the product of the information reporting period and the impact coefficient, the flow control reset information is sent to the service server.

[0021] In an optional design of the present application, the first sending module is further used for:

[0022] determining the impact coefficient according to the predicted business pressure of the business server, wherein the predicted business pressure is used to indicate the predicted reception status of the business request to the business server, and there is an inverse correlation between the impact coefficient and the predicted business pressure;

[0023] The predicted business pressure is used to indicate at least one of the historical business request volume of the business server, the number of online objects corresponding to the business server, and the number of reserved objects for the business request.

[0024] In an optional design of the present application, the first sending module is further used for:

[0025] Determining a first pressure coefficient based on a ratio between the number of appointment objects and the historical business request volume;

[0026] determining a second pressure coefficient based on a ratio between the number of online objects and the number of historical online objects;

[0027] Normalizing the product of the first pressure coefficient and the second pressure coefficient to obtain the influence coefficient;

[0028] The historical service request volume is used to indicate the total number of service requests received by the service server within a preset historical period, and the historical online object quantity is used to indicate the average value of the number of online objects within the preset historical period.

[0029] In an optional design of the present application, the device further includes:

[0030] A first determination module, configured to determine flow control update information based on the flow data when a second interval between the current reporting time of the flow data and the reference reporting time of the business server exceeds a startup threshold and the first interval does not exceed the disaster recovery threshold;

[0031] The first sending module is further used to send the flow control update information to the service server;

[0032] The reference reporting time is used to indicate the starting time for clearing obstacles to data transmission between the service server and the management server.

[0033] In an optional design of the present application, the first determining module is further configured to:

[0034] When the second interval exceeds the startup threshold and the first interval does not exceed the disaster recovery threshold, the product of the total traffic quota and the business server ratio is determined as the flow control update information;

[0035] Among them, the total traffic quota is used to indicate the total number of flow control quotas of multiple business servers for which the management server provides flow control, and the business server ratio is the ratio between the flow data of the business server and the total number of flow data of the multiple business servers for which the management server provides flow control.

[0036] In an optional design of the present application, the device further includes:

[0037] The first determining module is configured to update the reference reporting time of the service server to the current reporting time of the traffic data when the first interval exceeds the disaster recovery threshold.

[0038] In an optional design of the present application, the first sending module is further used for:

[0039] When a second interval between the current reporting time of the traffic data and the reference reporting time of the business server does not exceed the startup threshold, and the first interval does not exceed the disaster recovery threshold, the flow control reset information is sent to the business server.

[0040] In an optional design of the present application, the receiving module is further used for:

[0041] Receiving a traffic cache queue sent by the service server based on an information reporting period, wherein the traffic cache queue is used to carry the traffic data of the service server;

[0042] The traffic cache queue includes at least two cache segments, and the traffic data determines the cache segment that carries the service request based on the time when the service server receives the service request.

[0043] In an optional design of the present application, the device further includes:

[0044] A first determination module is used to determine, when the predicted business pressure of the business server exceeds the pressure threshold, a ratio between the total traffic quota and the number of multiple business servers for which the management server provides traffic control as the flow control reset information, wherein the total traffic quota is the total number of flow control quotas of the multiple business servers for which the management server provides traffic control;

[0045] And / or, the first determination module is used to determine the flow control cancellation indication as flow control reset information when the predicted business pressure of the business server does not exceed the pressure threshold, and the flow control cancellation indication is used to instruct the business server to turn off flow control.

[0046] In an optional design of the present application, the flow control quota information is also used to indicate the flow quota limit for the business server during the disconnection disaster recovery period when a transmission obstruction occurs between the management server and the business server.

[0047] In an optional design of the present application, the receiving module is further used to receive a stop deployment request from the business server, where the stop deployment request is used to indicate that the business server requests to no longer accept the flow control provided by the management server;

[0048] The processing module is used to stop providing flow control to the business server when other business servers except the business server can bear the total flow data of multiple business servers for which the management server provides flow control.

[0049] According to another aspect of the present application, an information configuration device is provided, the device is applied to a service server, there are at least two distributed deployed service servers, and flow control is provided by a management server, the device includes:

[0050] A second determination module, configured to determine the flow quota limit of the service server according to the flow control quota information, wherein the flow control quota information is sent by the management server;

[0051] A second sending module, configured to report flow data to the management server based on an information reporting period, wherein the flow data is used to indicate the amount of service requests received by the service server in at least one of the information reporting periods before the current reporting time of sending the flow data;

[0052] The second determination module is also used to reset the traffic quota limit of the business server to a preset limit based on the flow control reset information. The flow control reset information is sent by the management server when the first interval between the current reporting time corresponding to the traffic data and the last reporting time of the business server exceeds the disaster recovery threshold.

[0053] In an optional design of the present application, the second determining module is further used to:

[0054] In the case where a transmission obstruction occurs between the management server and the business server, a flow quota limit for the business server during the disconnection disaster recovery period is determined according to the flow control quota information.

[0055] According to another aspect of the present application, a computer device is provided, comprising a processor and a memory, wherein the memory stores at least one instruction, at least one program, a code set or an instruction set, and the at least one instruction, the at least one program, the code set or the instruction set is loaded and executed by the processor to implement the information configuration method as described above.

[0056] According to another aspect of the present application, a computer-readable storage medium is provided, in which at least one instruction, at least one program, a code set or an instruction set is stored, and the at least one instruction, the at least one program, the code set or the instruction set is loaded and executed by a processor to implement the information configuration method described above.

[0057] According to another aspect of the present application, a computer program product is provided, which includes computer instructions stored in a computer-readable storage medium, and a processor reads and executes the computer instructions from the computer-readable storage medium to implement the information configuration method described above.

[0058] The beneficial effects of the technical solution provided by this application include at least:

[0059] The credibility of the traffic data reported by the business server is determined by the disaster recovery threshold. When the first interval between the current reporting time of the traffic data and the last reporting time of the business server exceeds the disaster recovery threshold, the traffic data is in an unreliable state. By sending flow control reset information to the business server, a static method is used to control the traffic of the business server to ensure the safe operation of the business server, taking into account the efficiency of the business server in processing business requests and the safety of the operation status. BRIEF DESCRIPTION OF THE DRAWINGS

[0060] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0061] Figure 1 is a schematic diagram of a computer system provided by an exemplary embodiment of the present application;

[0062] Figure 2 is a schematic diagram of an information configuration method provided by an exemplary embodiment of the present application;

[0063] Figure 3 is a flow chart of an information configuration method provided by an exemplary embodiment of the present application;

[0064] Figure 4 is a flow chart of an information configuration method provided by an exemplary embodiment of the present application;

[0065] Figure 5 is a flow chart of an information configuration method provided by an exemplary embodiment of the present application;

[0066] Figure 6 is a flow chart of an information configuration method provided by an exemplary embodiment of the present application;

[0067] Figure 7 is a flow chart of an information configuration method provided by an exemplary embodiment of the present application;

[0068] Figure 8 is a schematic diagram of a traffic cache queue provided by an exemplary embodiment of the present application;

[0069] Fig. 9 is a flow chart of an information configuration method provided by an exemplary embodiment of the present application;

[0070] Fig.10 is a flow chart of an information configuration method provided by an exemplary embodiment of the present application;

[0071] Fig.11 is a flow chart of an information configuration method provided by an exemplary embodiment of the present application;

[0072] Fig.12 is a schematic diagram of a pending business provided by an exemplary embodiment of the present application;

[0073] Fig.13 is a flow chart of an information configuration method applied to a game provided by an exemplary embodiment of the present application;

[0074] Fig.14 is a structural block diagram of an information configuration device provided by an exemplary embodiment of the present application;

[0075] Fig.15 is a structural block diagram of an information configuration device provided by an exemplary embodiment of the present application;

[0076] Fig.16 It is a structural block diagram of a server provided by an exemplary embodiment of the present application.

[0077] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application. DETAILED DESCRIPTION

[0078] In order to make the objectives, technical solutions and advantages of the present application clearer, the implementation methods of the present application will be further described in detail below with reference to the accompanying drawings.

[0079] Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the following exemplary embodiments do not represent all implementations consistent with the present application. Instead, they are merely examples of devices and methods consistent with some aspects of the present application as detailed in the appended claims.

[0080] The terms used in this disclosure are for the purpose of describing specific embodiments only and are not intended to limit the disclosure. The singular forms of "a", "said" and "the" used in this disclosure and the appended claims are also intended to include plural forms unless the context clearly indicates otherwise. It should also be understood that the term "and / or" used herein refers to and includes any or all possible combinations of one or more associated listed items.

[0081] 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, stored data, displayed data, 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 relevant data must comply with the relevant laws, regulations and standards of the relevant countries and regions. For example, the traffic data and other information involved in this application are all obtained with full authorization.

[0082] It should be understood that although the terms first, second, etc. may be used in the present disclosure to describe various information, such information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other. For example, without departing from the scope of the present disclosure, the first parameter may also be referred to as the second parameter, and similarly, the second parameter may also be referred to as the first parameter. Depending on the context, the word "if" as used herein may be interpreted as "at the time of" or "when" or "in response to determining".

[0083] First, some of the terms in this application are explained:

[0084] The disaster recovery threshold is used to indicate the upper limit of the interval at which traffic data becomes unreliable due to an obstruction in data transmission between the business server and the management server; it is used to determine the reliability of traffic data reported by the business server.

[0085] The impact coefficient is used to indicate the degree of impact on the unreliability of traffic data caused by the obstruction of data transmission between the business server and the management server; for example, as the data transmission is obstructed, the degree of impact on the unreliability of traffic data increases, while the impact coefficient decreases.

[0086] The startup threshold is used to indicate the time required for the business server and the management server to complete initialization deployment and enter the formal working state after data transmission is established between the business server and the management server. It can also be called the cold start time of the business server and the management server.

[0087] The disconnection disaster recovery period is used to indicate the upper limit of the interval during which the flow control quota information provided by the management server is unreliable due to a blockage in data transmission between the business server and the management server.

[0088] Figure 1 A schematic diagram of a computer system provided by an embodiment of the present application is shown. The computer system can be implemented as a system architecture of an information configuration method. The computer system can include: a business server cluster 100 and a management server 200.

[0089] The business server cluster 100 includes at least two business servers, such as a first business server 110 and a second business server 120; it is understandable that in different implementations, the business server cluster 100 may further include more business servers. Exemplarily, the business servers are deployed in a distributed manner. The business servers in the business server cluster 100 can communicate with the management server 200 through a network, such as a wired or wireless network. The business servers in the business server cluster 100 may be independent physical servers, or a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides a cloud computing server. The business servers in the business server cluster 100 are used to provide background support for pending businesses, and the pending businesses include but are not limited to at least one of resource transfer businesses, data computing businesses, file access businesses, file upload businesses, and virtual activity businesses in a virtual environment.

[0090] In the case where the pending business is a virtual activity business in a virtual environment; the virtual activity business specifically includes but is not limited to at least one of the virtual environment login business, the virtual game support business, the virtual item transaction business, and the virtual session support business; accordingly, the business server in the business server cluster 100 is used to provide background support for any one of the battle royale shooting games, virtual reality (VR) programs, augmented reality (AR) programs, virtual reality games, augmented reality games, first-person shooting games (FPS), third-person shooting games (TPS), multiplayer online tactical competitive games (MOBA), and strategy games (SLG). In one implementation, some or all of the business servers in the business server cluster 100 can communicate with the downstream server 150 through the network, and provide background support for the pending business based on the downstream server 150 and the business service.

[0091] The management server 200 is used to provide flow control for the business servers in the business server cluster 100. Exemplarily, the management server 200 indicates the flow quota limit for the business server by sending flow control quota information to the business server in the business server cluster 100. The flow control quota information is used to prevent the business server from crashing due to the sharp increase in business requests, thereby ensuring the stability of the business server. Similarly, the management server 200 can be an independent physical server, a server cluster or a distributed system composed of multiple physical servers, or a cloud server that provides a cloud computing server. In one example, a server can provide both business services and flow control at the same time, which is not limited in this application.

[0092] Figure 2 A schematic diagram of an information configuration method provided by an exemplary embodiment of the present application is provided;

[0093] In this embodiment, the first reporting time 301 is the time when the business server first reports the flow data to the management server, which corresponds to 0 seconds on the time axis of this embodiment. Exemplarily, the business server periodically reports the flow data to the management server based on the information reporting cycle, and the information reporting cycle is 5 seconds.

[0094] The second reporting time 302 corresponds to 45 seconds on the time axis of this embodiment. After the second reporting time 302, due to network jitter and other reasons, the management server fails to successfully receive the traffic data transmitted according to the 5-second information reporting period. The time for receiving the traffic data after the second reporting time 302 is the third reporting time 303.

[0095] The reporting interval between the second reporting time 302 and the third reporting time 303 does not exceed the disaster recovery threshold 314, and the second interval between the third reporting time 303 and the first reporting time 301 does not exceed the startup threshold 312; the management server sends flow control reset information to the business server, and the flow control reset information is used to indicate that the traffic quota limit of the business server is reset to the preset limit. Exemplarily, the disaster recovery threshold is 3 times the information reporting period, that is, 15 seconds. The startup threshold 312 indicates the initialization time after the communication connection is established between the business server and the management server, such as 120 seconds.

[0096] In an optional implementation, there is no other reporting time for successfully receiving traffic information between the third reporting time 303 and the fourth reporting time 304, and the reporting interval between the third reporting time 303 and the fourth reporting time 304 exceeds the disaster recovery threshold 314, and the management server sends flow control reset information to the business server. And the reference reporting time of the business server is updated from the first reporting time 301 to the current reporting time of the traffic data indicated by the fourth reporting time 304.

[0097] In this embodiment, the traffic data transmitted according to the information reporting cycle is successfully received before and after the fourth reporting time 304. Since the second interval between the fourth reporting time 304 and the first reporting time 301 does not exceed the start threshold 312, the management server sends flow control reset information to the business server.

[0098] At the sixth reporting time 306, the first interval between the sixth reporting time 306 and the last reporting time, i.e., the fifth reporting time 305, does not exceed the disaster recovery threshold 314, and the second interval between the sixth reporting time 306 and the first reporting time 301 exceeds the start threshold 312; the management server sends flow control update information to the business server, and the flow control update information is determined based on the traffic data reported at the sixth reporting time 306; specifically, the product of the total traffic quota and the business server ratio is determined as the flow control update information, and the total traffic quota is used to indicate the total number of flow control quotas of multiple business servers for which the management server provides traffic control, and the business server ratio is the ratio between the traffic data of the business server and the total number of traffic data of multiple business servers for which the management server provides traffic control.

[0099] After the sixth reporting time 306, due to network jitter and other reasons, the management server fails to successfully receive the traffic data transmitted according to the 5-second information reporting cycle, and the time for receiving the traffic data after the sixth reporting time 306 is the seventh reporting time 307. The reporting interval between the sixth reporting time 306 and the seventh reporting time 307 exceeds the disaster recovery threshold 314, and the management server sends flow control reset information to the business server. And the reference reporting time of the business server is updated from the first reporting time 301 to the current reporting time of the traffic data indicated by the seventh reporting time 307.

[0100] Next, the information configuration method will be introduced through the following embodiments.

[0101] Figure 3 A flowchart of an information configuration method provided by an exemplary embodiment of the present application is shown. The method can be executed by a management server. The method includes:

[0102] Step 510: Send flow control quota information;

[0103] Exemplarily, the flow control quota information is used to indicate the flow quota limit for the business server; in one implementation, the flow control quota information indicates the flow quota limit of one business server or multiple business servers at the granularity of the business server. Exemplarily, the flow control quota information is used to indicate the limit number of business requests received by the business server. If the number of business requests received by the business server during the time period corresponding to the flow control quota information exceeds the flow control quota information, the business server exceeds the flow control limit and no longer provides business services. The management server is used to provide flow control for at least two distributed deployed business servers.

[0104] Step 520: receiving traffic data sent by the service server based on the information reporting period;

[0105] Exemplarily, the traffic data is used to indicate the amount of service requests received by the service server; the service server sends the traffic data in a periodic reporting manner based on the information reporting period. Exemplarily, the traffic data is used to indicate the amount of service requests received by the service server within at least one information reporting period before the current reporting time of sending the traffic data. It should be noted that the traffic data can directly carry the number of service requests; it can also carry at least one of the information such as the sender of the service request, the receiving time, the type of service request, etc., to indirectly indicate the number of service requests, and the present application does not impose any restrictions on this. Exemplarily, due to network jitter and other reasons, the time interval between two adjacent traffic data of the service server received by the management server may exceed the information reporting period.

[0106] Step 530: When a first interval between the current reporting time corresponding to the traffic data and the last reporting time of the service server exceeds the disaster recovery threshold, a flow control reset message is sent to the service server;

[0107] Exemplarily, the disaster recovery threshold is used to determine the credibility of the traffic data reported by the business server. When the first interval between the current reporting time of the traffic data and the last reporting time of the business server exceeds the disaster recovery threshold, the credibility of the traffic data is considered insufficient due to the large time interval for the obstruction of data transmission between the business server and the management server; the flow control reset information is used to indicate that the traffic quota limit of the business server is reset to the preset limit. By sending the flow control reset information to the business server, the traffic of the business server is controlled in a static manner based on the preset limit indicated by the flow control reset information, thereby ensuring that when reliable traffic data cannot be obtained, the business server is protected by traffic control, while taking into account the processing efficiency of the business server for business requests and the security of the operating status.

[0108] Exemplarily, the last reporting time is a historical reporting time adjacent to the current reporting time corresponding to the traffic data. The disaster recovery threshold is used to indicate the upper limit of the interval at which the traffic data is unreliable due to an obstruction in data transmission between the business server and the management server.

[0109] To sum up, the method provided in this embodiment determines the credibility of the traffic data reported by the business server through the disaster recovery threshold. When the first interval between the current reporting time of the traffic data and the last reporting time of the business server exceeds the disaster recovery threshold, the traffic data is in an unreliable state. By sending flow control reset information to the business server, a static method is used to control the traffic of the business server, thereby ensuring the security of the running status of the business server and taking into account the processing efficiency of the business server for business requests and the security of the running status.

[0110] Figure 4 FIG. 1 is a flowchart of an information configuration method provided by an exemplary embodiment of the present application. The method can be executed by a management server. Figure 3 In the illustrated embodiment, step 530 may be implemented as steps 532 and 534:

[0111] Step 532: Obtain the influence coefficient of the service server;

[0112] Exemplarily, the impact coefficient may be predetermined or determined based on the operation of the business server, and this embodiment does not limit this. In this embodiment, the product of the information reporting period and the impact coefficient is determined as the disaster recovery threshold; the impact coefficient is used to indicate the impact of the information reporting period on the disaster recovery threshold; the impact coefficient is used to indicate the degree of impact on the unreliability of traffic data due to the obstruction of data transmission between the business server and the management server; for example, as the degree of impact on the unreliability of traffic data increases due to the obstruction of data transmission, the impact coefficient decreases.

[0113] Exemplarily, the traffic data is sent by the service server based on the information reporting period, and the value of the influence coefficient is greater than or equal to 1; further, the value of the influence coefficient is an integer greater than or equal to 1. In one example, the value of the obtained influence coefficient is 3.

[0114] Step 534: When the first interval exceeds the product of the information reporting period and the impact coefficient, a flow control reset message is sent to the service server;

[0115] In this embodiment, the product of the information reporting cycle and the impact coefficient is the upper limit of the interval at which the traffic data is unreliable due to the obstruction of data transmission between the business server and the management server. Exemplarily, in the case where the business server periodically reports the traffic data, the upper limit of the interval that causes the traffic data to be unreliable is determined according to the product of the information reporting cycle and the impact coefficient, and the disaster recovery threshold is normalized to the impact coefficient. In the case where the information reporting cycle changes, the disaster recovery threshold changes adaptively with the information reporting cycle; the impact coefficient indicates the stability requirement for data transmission between the business server and the management server.

[0116] In summary, the method provided in this embodiment determines the trust threshold through the influence coefficient and the information reporting cycle, establishes a connection between the credibility of the traffic data and the periodic reporting method of the traffic data; realizes that when the information reporting cycle changes, the disaster recovery threshold changes adaptively accordingly; reduces the number of parameters that need to be independently determined; when the first interval between the current reporting time of the traffic data and the last reporting time of the business server exceeds the disaster recovery threshold, the traffic data is in an untrustworthy state, and by sending flow control reset information to the business server, a static method is used to control the traffic of the business server, thereby ensuring the safety of the running status of the business server, and taking into account the processing efficiency of the business server for business requests and the safety of the running status.

[0117] The following is a further introduction to the method of determining the influence coefficient.

[0118] In an optional implementation, Figure 4 Step 532 in can be implemented as sub-step 32a:

[0119] Sub-step 32a: determining an impact coefficient according to the predicted service pressure of the service server;

[0120] Exemplarily, the predicted business pressure is used to indicate the predicted reception of business requests to the business server, and the impact coefficient and the predicted business pressure are inversely correlated. Exemplarily, as the predicted business pressure increases, the load level of the business server increases; when the business server is at a high load level, the business server needs to obtain the flow control information provided by the management server in a timely manner, and the impact coefficient and the predicted business pressure are inversely correlated. By reducing the impact coefficient, the upper limit of the interval in which the flow data is unreliable due to the obstruction of data transmission between the business server and the management server is shortened.

[0121] Exemplarily, the predicted business pressure is used to indicate at least one of the historical business request volume of the business server, the number of online objects corresponding to the business server, and the number of scheduled objects for business requests. The predicted business pressure can be determined by statistical calculation based on the above information, or by inputting the above information into an artificial neural network (ANN) to predict the influence coefficient; this embodiment does not limit the method of determining the influence coefficient.

[0122] In an optional implementation, a specific method of determining the impact coefficient according to the predicted business pressure is as follows:

[0123] Determine a first pressure coefficient based on a ratio between the number of appointment objects and the historical business request volume;

[0124] determining a second pressure coefficient based on a ratio between the number of online objects and the number of historical online objects;

[0125] Normalizing the product of the first pressure coefficient and the second pressure coefficient to obtain an influence coefficient;

[0126] Exemplarily, historical business requests are business requests that actually occurred, and the number of scheduled objects is the number of objects that have request interests for pending business; the first pressure coefficient is used to indicate the relative pressure of business requests corresponding to pending business supported by the scheduled business server compared to historical business requests in a preset historical period. The first pressure coefficient is used to predict the relative pressure of objects with request interests on the business server load.

[0127] Exemplarily, the number of historical online objects is an average number of online objects in a preset historical period, and the historical service requests are triggered by the historical online objects; as the number of historical online objects increases, the service server has a potential load pressure for receiving service requests. The second pressure coefficient determined based on the ratio between the number of online objects and the number of historical online objects is used to indicate the potential relative pressure of the increase in the number of online objects compared to the number of historical online objects.

[0128] In an optional implementation, since online objects do not necessarily initiate business requests, no business requests may be sent to the business server because there is no processing demand for pending business. The second pressure coefficient is determined as the ratio between the number of online objects and the number of historical online objects, multiplied by a hyperparameter, and the value of the hyperparameter is greater than 0 and less than 1.

[0129] Exemplarily, the historical business request volume is used to indicate the total number of business requests received by the business server within a preset historical period, and the historical online object number is used to indicate the average number of online objects within the preset historical period; the preset historical period can be a peak period for processing business requests obtained by screening, or it can be a period determined through human-computer interaction; for example, the preset historical period is 24 hours before the current timestamp.

[0130] Exemplarily, the normalization process is used to calculate the influence coefficient by multiplying the first pressure coefficient and the second pressure coefficient based on the anti-correlation relationship, and the present application does not limit the normalization process. It should be noted that the present embodiment only shows an implementation method for determining the influence coefficient based on the product of the first pressure coefficient and the second pressure coefficient, but does not exclude an implementation method for determining the influence coefficient based on the first pressure coefficient or the second pressure coefficient. The steps in the present embodiment can be split into a new implementation method, and the present application does not limit this.

[0131] To summarize, the method provided in this embodiment determines the trust threshold through the impact coefficient and the information reporting cycle, and determines the impact coefficient through the predicted reception of the business request of the business server based on the inverse correlation between the impact coefficient and the predicted business pressure; when the first interval between the current reporting time of the traffic data and the last reporting time of the business server exceeds the disaster recovery threshold, the traffic data is in an untrustworthy state, and by sending flow control reset information to the business server, a static method is used to control the flow of the business server, thereby ensuring the safety of the running status of the business server, and taking into account both the processing efficiency of the business server for business requests and the safety of the running status.

[0132] Figure 5 FIG. 1 is a flowchart of an information configuration method provided by an exemplary embodiment of the present application. The method can be executed by a management server. Figure 3Based on the embodiment shown, step 542 and step 544 are also included:

[0133] Step 542: when the second interval between the current reporting time of the traffic data and the reference reporting time of the service server exceeds the startup threshold and the first interval does not exceed the disaster recovery threshold, determine the flow control update information based on the traffic data;

[0134] Exemplarily, the reference reporting time is used to indicate the starting time for clearing obstacles to data transmission between the business server and the management server; in one example, the reference reporting time is a reporting time from the historical reporting time before the current report; further, the reference reporting time is obtained by searching. Specifically, the reference reporting time is the i-th historical reporting time arranged in chronological order from front to back. When i is 1, the interval between the j-th historical reporting time and the j+1-th historical reporting time is less than or equal to the disaster recovery threshold; j is an integer greater than or equal to i; when i is greater than 1, the interval between the i-1-th historical reporting time and the i-th historical reporting time exceeds the disaster recovery threshold, and the interval between the j-th historical reporting time and the j+1-th historical reporting time is less than or equal to the disaster recovery threshold; j is an integer greater than or equal to i.

[0135] It can be understood that in an optional manner, when the first interval exceeds the disaster recovery threshold, the reference reporting time of the service server is updated to the current reporting time of the traffic data. Figure 3 Steps 510 to 530 in the above-mentioned embodiment constitute a new embodiment and are implemented separately, and this application does not limit this.

[0136] Exemplarily, the startup threshold is used to indicate the time required for the business server and the management server to complete the initialization deployment and enter the formal working state after data transmission is established between the business server and the management server, which can also be called the cold start time of the business server and the management server. Exemplarily, the startup threshold is usually a pre-set empirical value, or is determined according to the device computing capability attributes of the business server and / or the management server. This embodiment does not limit the method for determining the startup threshold.

[0137] Exemplarily, the flow control update threshold is obtained based on the prediction of the flow data, and the flow control update threshold is used to provide the service server with flow control for the time period after the current reporting time. The flow control update information can be obtained based on statistical calculations of the flow data, or can be obtained by predicting and processing the flow data based on an artificial neural network, which is not limited in this embodiment.

[0138] Step 544: Send flow control update information to the service server;

[0139] Exemplarily, the flow control update information is used to indicate the flow quota limit for the business server; exemplary, after the business server receives the flow control update information, the flow control quota information is updated to indicate the flow quota limit for the business server after this reporting time.

[0140] To sum up, the method provided in this embodiment determines the completion status of the initialization deployment of the business server and the management server through the startup threshold. When the second interval between the current reporting time of the traffic data and the reference reporting time of the business server exceeds the startup threshold, the business server and the management server complete the initialization deployment, determine the flow control update information based on the traffic data, and dynamically control the flow of the business server to ensure the safe operation status of the business server, taking into account the processing efficiency of the business server for business requests and the safety of the operation status.

[0141] In an optional implementation, Figure 5 Step 542 in the corresponding embodiment can be implemented as sub-step 42a:

[0142] Sub-step 42a: when the second interval exceeds the startup threshold and the first interval does not exceed the disaster recovery threshold, determine the product of the total traffic quota and the business server ratio as the flow control update information;

[0143] Exemplarily, the total traffic quota is used to indicate the total number of traffic control quotas of multiple service servers for which the management server provides traffic control; the total traffic quota is determined based on the number of multiple service servers for which the management server provides traffic control and the device computing capacity attribute, and is used to indicate the upper limit of the number of service requests that multiple service servers are allowed to carry. Exemplarily, the total traffic quota can be static and unchanged, or it can be modified and adjusted based on the historical reception of service requests by the service server, and this embodiment does not limit this.

[0144] Exemplarily, the business server ratio is the ratio between the traffic data of the business server and the total traffic data of multiple business servers for which the management server provides traffic control; in one implementation, a cache queue is provided in the management server for storing the total traffic data of multiple business servers.

[0145] In a specific example, the total traffic quota is recorded as quata; the traffic data of the service server is the amount of service requests received by the service server counted in multiple information reporting cycles, recorded as self. Among the total amount of traffic data of multiple service servers for which the management server provides traffic control, the second interval between the reporting time corresponding to the multiple service servers and the reference reporting time corresponding to the multiple service servers exceeds the start threshold, recorded as total. Exemplarily, the flow control update information is determined as quata*self / total.

[0146] To sum up, the method provided in this embodiment, when the second interval between the current reporting time of the traffic data and the reference reporting time of the business server exceeds the startup threshold, the business server and the management server complete the initialization deployment, determine the flow control update information based on the traffic data, and dynamically control the traffic of the business server. The product of the total traffic quota and the proportion of the business server is determined as the flow control update information, and the total traffic quota is allocated according to the load situation of the business server, so as to ensure the safe operation status of the business server and take into account the processing efficiency of the business server for business requests and the safety of the operation status.

[0147] Figure 6 FIG. 1 is a flowchart of an information configuration method provided by an exemplary embodiment of the present application. The method can be executed by a management server. Figure 3 Based on the illustrated embodiment, step 545 is also included:

[0148] Step 545: When the second interval between the current reporting time of the traffic data and the reference reporting time of the service server does not exceed the startup threshold, and the first interval does not exceed the disaster recovery threshold, send flow control reset information to the service server;

[0149] Exemplarily, the reference reporting time is used to indicate the starting time for clearing obstacles to data transmission between the business server and the management server; exemplary, the startup threshold is used to indicate the time required for the business server and the management server to complete initialization deployment and enter the formal working state after data transmission is established between the business server and the management server, which can also be called the cold start time of the business server and the management server.

[0150] Exemplarily, when the second interval between the current reporting time of the traffic data and the reference reporting time of the business server does not exceed the startup threshold, at least one of the business server and the management server has not completed the initialization deployment and is in an unstable state; based on the preset restrictions indicated by the flow control reset information, a static method is used to control the traffic of the business server to ensure that when at least one of the business server and the management server has not completed the initialization deployment, the business server is protected by traffic control, taking into account the processing efficiency of the business server for business requests and the safety of the operating status.

[0151] To sum up, the method provided in this embodiment determines the completion status of the initialization deployment of the business server and the management server through the startup threshold. When the second interval between the current reporting time of the traffic data and the reference reporting time of the business server does not exceed the startup threshold, the business server and the management server have not completed the initialization deployment. By sending flow control reset information to the business server, a static method is used to control the flow of the business server, thereby ensuring the safety of the running status of the business server and taking into account the processing efficiency of the business server for business requests and the safety of the running status.

[0152] In one example, the management server records the information transmission time of the service server providing flow control in a table, as shown in Table 1 below:

[0153] Table 1

[0154] address Reference reporting time Last reported time name 11.xxx.98.01 14:40:10 14:50:10 A 11.xxx.98.02 14:40:10 14:40:10 B 11.xxx.98.03 14:40:10 14:40:10 C

[0155] It should be noted that the address in Table 1 is used to indicate the Internet Protocol Address (IP) of the business server; the name is the device identifier of the business server.

[0156] The reference reporting time is recorded as FirstTime, which is used to indicate the starting time for clearing obstacles to data transmission between the business server and the management server. For an introduction to the reference reporting time, please refer to step 542 above. The reference reporting time of the business server named A is recorded as A.FirstTime.

[0157] The last reporting time is recorded as UpdateTime, which is the historical reporting time adjacent to the current reporting time corresponding to the traffic data. For the introduction of the reference reporting time, please refer to step 530 above. The reference reporting time of the business server named A is recorded as A.UpdateTime.

[0158] This embodiment shows that the management server is used to provide flow control to three distributed deployed service servers, but does not exclude the situation where flow control is provided to more or fewer service servers.

[0159] Taking a service server named A as an example, the time when the management server receives the traffic data sent by the service server named A is the reporting time, which is recorded as AccessTime.

[0160] When the first interval between the current reporting time and the last reporting time of the business server exceeds the disaster recovery threshold, for example, AccessTime-A.UpdateTime>15 seconds; the traffic data reported by the business server is considered unreliable, and the management server sends a flow control reset message to the business server.

[0161] When the second interval between the current reporting time of the traffic data and the reference reporting time of the business server does not exceed the startup threshold, and the first interval does not exceed the disaster recovery threshold, for example: AccessTime-A.UpdateTime<15 seconds&&AccessTime-A.First<2*60 seconds; the normal and stable communication between the management server and the business server does not reach 2*60 seconds, the initialization deployment is not completed, and the management server sends a flow control reset message to the business server.

[0162] When the second interval between the current reporting time of the traffic data and the reference reporting time of the business server exceeds the startup threshold and the first interval does not exceed the disaster recovery threshold, for example: AccessTime–A.UpdateTime<15 seconds&&AccessTime–A.First>2*60 seconds; the management server determines the flow control update information based on the traffic data; and sends the flow control update information to the business server.

[0163] Next, the traffic data received by the management server is introduced.

[0164] Figure 7 FIG. 1 is a flowchart of an information configuration method provided by an exemplary embodiment of the present application. The method can be executed by a management server. Figure 3 In the illustrated embodiment, step 520 may be implemented as step 522:

[0165] Step 522: receiving a traffic buffer queue sent by the service server based on an information reporting period;

[0166] Exemplarily, the traffic cache queue is used to carry traffic data of the service server; the traffic cache queue includes at least two cache segments, and the traffic data determines the cache segment carrying the service request based on the time when the service server receives the service request. Exemplarily, the service server reports the traffic cache queue to the management server through a software development kit (SDK).

[0167] Figure 8 A schematic diagram of a traffic cache queue provided by an exemplary embodiment of the present application is shown. In this embodiment, an example in which 6 cache segments are included in the traffic cache queue is used for introduction. The 6 cache segments are identified as 0 to 5, and the rectangular structures represented by fan-shaped structures and queues in the figure respectively show the traffic cache queues. It should be noted that the circle composed of the fan-shaped structure and the rectangular structure selected by the dotted box in the figure both represent traffic cache queues. The cache segment corresponds to a time, and the business requests received by the business server within the time corresponding to the cache segment are counted to obtain the corresponding number of requests.

[0168] The business requests within the time corresponding to the cache fragment are counted in sequence, and the six cache fragments are connected end to end to form a circular use. As the time window moves, the cache fragment marked as 5 completes the counting of business requests, and continues to use the cache fragment marked as 0 to count. In an example, the traffic cache queue including 6 cache fragments is recorded as Arr, the time seconds for obtaining the business request is recorded as A, and the integer part of (A%60) / 10 is used as the array subscript, and the array subscript is marked as index, which is used to indicate one of the 6 cache fragments. The value of index is an integer between [0,5]. (A%60) is used to indicate the remainder of the time seconds minus the minute integer. For example, A is 682 seconds, and the remainder minus the minute integer is 22 seconds. Arr[i] is used to indicate the cache fragment marked as i in the traffic cache queue.

[0169] Exemplarily, the time of the service request is marked as timekey, and the time mark is determined by obtaining the minute integer part of the service request and the array index, and is used to indicate the time characteristics of the cache fragment corresponding to the array index. Exemplarily, timekey = AA%60 + index*10; Exemplarily, A is 682 seconds, and the corresponding time mark is 682-22 + 2*10 = 680; The time mark is used to indicate that the time of obtaining the service request is after 680 seconds.

[0170] Exemplarily, the cache fragment corresponding to the array index is recorded as Arr[index], and the cache fragment corresponding to the array index corresponds to a time stamp Arr[index].timekey; the time stamp corresponding to the cache fragment is used to indicate that the cache fragment is used to count the service requests obtained after the time stamp. In one example, when the time stamp timekey of the service request is equal to the time stamp Arr[index].timekey of the cache fragment Arr[index] corresponding to the array index of the service request, the count value of the cache fragment Arr[index] for the service request is increased by one, that is: Arr[index].sum=Arr[index].sum+1.

[0171] In another example, when the time stamp timekey of the business request is not equal to the time stamp Arr[index].timekey of the cache fragment Arr[index] corresponding to the array index of the business request, the count value of the cache fragment Arr[index] for the business request is recorded as 1, and the time stamp Arr[index].timekey of the cache fragment is updated; that is: Arr[index].sum=1, Arr[index].timekey=timekey.

[0172] It should be noted that this embodiment uses the example of a traffic cache queue including 6 cache fragments. In different implementations, there may be more or fewer cache fragments. Furthermore, this embodiment introduces a traffic cache queue sent by a business server. In one implementation, the management server uses the same data structure to store traffic cache queues sent by one or more business servers, and records the server ID of the business server in the cache fragment to distinguish the traffic data reported by different business servers. In one example, the management server records the traffic data of multiple business servers that provide traffic control in a table, as shown in Table 2 below:

[0173] Table 2

[0174]

[0175] Exemplarily, the total request volume is used to indicate the total request volume of pending services received daily or hourly, and the real-time request volume is used to indicate the real-time rate of the pending services received. It can be seen that the service server can support multiple types of pending services, and this embodiment does not limit the types of pending services and the number of service servers.

[0176] In summary, the method provided in this embodiment determines the credibility of the traffic data reported by the business server through the disaster recovery threshold, and the traffic data is stored in the traffic cache queue. The traffic cache queue includes at least two cache segments, which realizes the storage of traffic data based on time sequence, making it convenient for the management server to read and use traffic data of different time periods. The management server is used to provide traffic control to the business server, ensuring the safe operation status of the business server, and taking into account the processing efficiency of the business server for business requests and the safety of the operation status.

[0177] Next, the flow control reset information sent by the management server is introduced.

[0178] Fig. 9 FIG. 1 is a flowchart of an information configuration method provided by an exemplary embodiment of the present application. The method can be executed by a management server. Figure 3 Based on the illustrated embodiment, step 525a and step 525b are also included:

[0179] Step 525a: when the predicted service pressure of the service server exceeds the pressure threshold, the ratio between the total traffic quota and the number of the multiple service servers for which the management server provides traffic control is determined as the traffic control reset information;

[0180] Exemplarily, the predicted business pressure is used to indicate the predicted reception of business requests to the business server. For a detailed introduction to the predicted business pressure, please refer to sub-step 32a above. In one example, the predicted business pressure is the product of the first pressure coefficient and the second pressure coefficient in sub-step 32a.

[0181] Exemplarily, the total traffic quota is used to indicate the total number of traffic control quotas of multiple business servers for which the management server provides traffic control; for the introduction to the message about the total traffic quota, please refer to sub-step 42a above, which will not be repeated here. Exemplarily, the pressure threshold in this embodiment can be pre-set or determined based on the device computing capability attributes of the business server. Exemplarily, when the predicted business pressure of the business server exceeds the pressure threshold, the business server is in a high-load operation state, and the ratio between the total traffic quota and the number of multiple business servers for which the management server provides traffic control is determined as the traffic control reset information, so that the traffic control of the business server is implemented in a static manner.

[0182] Step 525b: when the predicted service pressure of the service server does not exceed the pressure threshold, determining the flow control cancellation indication as flow control reset information;

[0183] For example, when the predicted business pressure of the business server does not exceed the pressure threshold, the business server is in a low-load operation state, and there is no risk of the business server crashing due to the impact of a sharp increase in business requests; the flow control cancellation indication is used to instruct the business server to turn off flow control, thereby saving the data transmission cost between the business server and the management server.

[0184] It should be noted that this embodiment includes both step 525a and step 525b. In another implementation, the above two steps can be split and respectively form new embodiments with step 510, step 520, and step 530, and this application does not limit this. In this embodiment, step 525a and step 525b are executed before step 530, and the execution timing relationship between step 525a and step 525b and other steps is not limited.

[0185] To summarize, the method provided in this embodiment determines the preset limit of the flow quota limit indicated by the flow control reset information based on the predicted business pressure and the pressure threshold; cancels the flow control when there is no risk of the business server crashing due to the impact of a sharp increase in business requests; and adopts a static method to control the flow of the business server when there is a risk of the business server crashing due to the impact of a sharp increase in business requests; and takes into account the flow control schemes under different load pressures.

[0186] Next, changes in computing resources of the business server are introduced.

[0187] Fig.10 FIG. 1 is a flowchart of an information configuration method provided by an exemplary embodiment of the present application. The method can be executed by a management server. Figure 3 Based on the illustrated embodiment, step 552 and step 554 are also included:

[0188] Step 552: receiving a stop deployment request from the business server;

[0189] Exemplarily, a stop deployment request is used to instruct the business server to request that it no longer accept the traffic control provided by the management server; a stop deployment request is usually sent to the management server alone, but it does not rule out the possibility that it is sent simultaneously with other information, such as sending the stop deployment request and traffic data to the management server at the same time.

[0190] Step 554: when other service servers except the service server can bear the total amount of flow data of the multiple service servers for which the management server provides flow control, stop providing flow control to the service server;

[0191] Exemplarily, the total traffic quota can be used to indicate the traffic data that other business servers except the business server can carry; the total traffic quota is subtracted from the first quota corresponding to the business server to obtain a revised quota; when the revised quota is greater than the total amount of traffic data of multiple business servers for which the management server provides traffic control, traffic control is stopped to the business server; exemplarily, the first quota is determined based on the device computing power attributes of the business server.

[0192] In an optional implementation, when the total amount of traffic data of the multiple service servers exceeds the carrying capacity of other service servers except the service server, flow control correction information is sent to the other service servers, and flow control is stopped for the service servers;

[0193] Exemplarily, the ratio between the total traffic quota and the number of the plurality of service servers for which the management server continues to provide traffic control is determined as the traffic control correction information.

[0194] In another optional implementation, a request to add a new business server to join the deployment is received, and the new business server requests to accept the traffic control provided by the management server; since the new business server takes on a part of the business requests, the original business server receives fewer business requests, and there is no risk of the original business server crashing due to the sharp increase in business requests; there is no need to adjust the traffic control of the original business server.

[0195] To sum up, the method provided in this embodiment determines the carrying capacity of other business servers for the total amount of traffic data, and stops providing traffic control to the business server when other business servers are able to carry the total amount of traffic data of multiple business servers, thereby realizing the computing resource changes of the traffic control adaptive business server provided by the management server.

[0196] Fig.11 A flowchart of an information configuration method provided by an exemplary embodiment of the present application is shown. The method can be executed by a management server and a business server. The method includes:

[0197] Step 610: The management server sends flow control quota information;

[0198] Exemplarily, the flow control quota information is used to indicate the flow quota limit for the business server; for the introduction of the management server and the flow control quota information, please refer to step 510 above.

[0199] Step 620: The service server determines the traffic quota limit of the service server according to the traffic control quota information;

[0200] Exemplarily, the flow control quota information is sent by the management server; in one implementation, the flow control quota information indicates the flow quota limit of a service server or multiple service servers at the service server granularity. Exemplarily, the flow control quota information is used to indicate the limit number of service requests received by the service server.

[0201] Step 630: The business server reports the traffic data to the management server based on the information reporting cycle;

[0202] Exemplarily, the traffic data is used to indicate the amount of service requests received by the service server in at least one information reporting period before the current reporting time of sending the traffic data.

[0203] Exemplarily, the business server is used to provide background support for pending business, and the business request is request information for executing the pending business; taking the pending business as a virtual active business in a virtual environment as an example, Fig.12 A schematic diagram of pending services provided by an exemplary embodiment of the present application is shown. As shown in the first interface 410, the pending service is to visit the virtual mall to receive virtual decorations. The first interface 410 includes first introduction information 412 of the pending service and a first functional entry 414 for triggering a service request for the pending service. As shown in the second interface 420, the pending service is to collect virtual props in a virtual game to exchange for virtual decorations. The second interface 420 includes second introduction information 422 of the pending service and a second functional entry 424 for triggering a service request for the pending service.

[0204] Step 640: The management server receives the traffic data sent by the business server based on the information reporting cycle;

[0205] Exemplarily, the service server sends the flow data in a periodic reporting manner based on the information reporting period. For an introduction to the information reporting period and flow data, please refer to step 520 above.

[0206] Step 650: When the first interval between the current reporting time corresponding to the traffic data and the last reporting time of the service server exceeds the disaster recovery threshold, the management server sends flow control reset information to the service server;

[0207] Exemplarily, the flow control reset information is used to indicate that the flow quota limit of the service server is reset to a preset limit. For an introduction to the disaster recovery threshold and the flow control reset information, please refer to step 530 above.

[0208] Step 660: The service server resets the traffic quota limit of the service server to the preset limit according to the flow control reset information;

[0209] Exemplarily, the flow control reset information is sent by the management server when the first interval between the current reporting time corresponding to the flow data and the last reporting time of the business server exceeds the disaster recovery threshold. Exemplarily, the last reporting time is a historical reporting time adjacent to the current reporting time corresponding to the flow data. The disaster recovery threshold is used to indicate the upper limit of the interval at which the flow data is unreliable due to the obstruction of data transmission between the business server and the management server.

[0210] It should be noted that step 620, step 630, and step 660 in this embodiment can be implemented independently by the business server to form a new embodiment, and this application does not limit this.

[0211] In an optional implementation, this implementation further includes the following steps:

[0212] In the event of a transmission obstruction between the management server and the business server, the flow control quota information is used to indicate the flow quota limit for the business server during the disconnection disaster recovery period;

[0213] Exemplarily, in the event of a transmission obstruction between the management server and the business server, the business server cannot successfully receive the flow control reset information or flow control update information sent by the management server. The disconnection disaster recovery period is used to indicate the upper limit of the interval during which the flow control quota information provided by the management server is unreliable due to an obstruction in data transmission between the business server and the management server. When the disconnection disaster recovery period is exceeded, the flow control quota information has no reference value for flow control due to an obstruction in data transmission between the business server and the management server. In one example, the disconnection disaster recovery period is 5 minutes. Exemplarily, the disconnection disaster recovery period and the disaster recovery threshold and the start threshold are usually independent of each other, but it does not rule out the possibility that at least two of the above information are interrelated.

[0214] To sum up, the method provided in this embodiment determines the credibility of the traffic data reported by the business server through the disaster recovery threshold. When the first interval between the current reporting time of the traffic data and the last reporting time of the business server exceeds the disaster recovery threshold, the traffic data is in an unreliable state. By sending flow control reset information to the business server, a static method is used to control the traffic of the business server, thereby ensuring the security of the running status of the business server and taking into account the processing efficiency of the business server for business requests and the security of the running status.

[0215] Fig.13 A flowchart of an information configuration method applied to a game provided by an exemplary embodiment of the present application is shown.

[0216] The information configuration method provided in this embodiment is applied to the virtual item transaction process in the game. Accordingly, the game virtual transaction server is a business server for supporting the virtual activity business of the virtual item transaction business in the virtual environment corresponding to the game. In this embodiment, the game virtual transaction server is used to provide background support for the transaction business of virtual items in any of the battle royale shooting games, virtual reality games, augmented reality games, first-person shooting games, third-person shooting games, multiplayer online tactical competitive games, and strategy games.

[0217] In another implementation, the information configuration method can also be applied to a user login service in a game; accordingly, the game login server is a service server for supporting a virtual activity service as a user login service in a virtual environment corresponding to the game. This application does not limit the application of the information configuration method in a virtual environment corresponding to the game.

[0218] Step 702: The management server sends the game transaction traffic quota to the game virtual transaction server;

[0219] The game transaction traffic quota is used to indicate the upper limit of the number of game virtual transaction requests for virtual item transaction services received by the game virtual transaction server per second, such as 8,000 times per second. If the number of game virtual transaction requests received by the game virtual transaction server exceeds the game transaction traffic quota, the game virtual transaction server will no longer provide virtual item transaction services. Exemplarily, the management server is a server that provides traffic control for the transaction services of virtual items in the game.

[0220] Step 704: the terminal sends a game virtual transaction request corresponding to the transaction service of virtual items in the virtual environment to the game virtual transaction server;

[0221] In response to triggering the function entry displayed on the terminal, the terminal sends a game virtual transaction request to the game virtual transaction server. The terminal displays a business interface for the transaction of virtual items in the virtual environment. For an introduction to the business interface and the function entry in the business interface, please refer to the above Fig.12 Exemplarily, the terminal sends a game virtual transaction request for a transaction service to the game virtual transaction server through an installed game client or a web window accessing a web mobile game.

[0222] Exemplarily, there may be multiple terminals sending game virtual transaction requests to the game virtual transaction server, and this embodiment does not limit the number of terminals.

[0223] Step 706: the game virtual transaction server sends the game virtual transaction request volume for the virtual item transaction service to the management server based on the information reporting cycle;

[0224] Exemplarily, the amount of game virtual transaction requests is the amount of game virtual transaction requests received in at least one information reporting cycle before the current reporting time; Exemplarily, the current reporting time is used to indicate the time when the amount of game virtual transaction requests is sent. Exemplarily, the information reporting cycle can be preset, such as 5 seconds. Exemplarily, the game virtual transaction server sends the amount of game virtual transaction requests in an information reporting cycle before the current reporting time to the management server.

[0225] The method in which the management server provides traffic control to the game virtual transaction server includes at least the following steps 708a to 708d, which are at least one of the four steps:

[0226] Among them, in step 708a to step 708c, information can be transmitted between the management server and the game virtual transaction server, and the game virtual transaction server successfully receives the flow control reset information or flow control update information sent by the management server. In step 708d, a transmission obstacle occurs between the management server and the game virtual transaction server, resulting in the game virtual transaction server being unable to successfully receive information sent by the management server, such as flow control reset information or flow control update information.

[0227] Step 708a: When the first interval between the current reporting time and the last reporting time corresponding to the reported game virtual transaction request amount exceeds the disaster recovery threshold, send flow control reset information to the game virtual transaction server;

[0228] The disaster tolerance threshold is used to determine the credibility of the amount of game virtual transaction requests reported by the game virtual transaction server, and is used to indicate the upper limit of the interval at which the amount of game virtual transaction requests reported is unreliable due to the obstruction of data transmission between the game virtual transaction server and the management server. Exemplarily, the disaster tolerance threshold is an integer multiple of the information reporting cycle. For example, if the information reporting cycle is 5 seconds, the disaster tolerance threshold is 3 times the information reporting cycle, that is, 15 seconds.

[0229] When the first interval between the current reporting time and the last reporting time corresponding to the game virtual transaction server exceeds 15 seconds, it is considered that the credibility of the game virtual transaction request volume reported by the game virtual transaction server is insufficient. Based on the preset limit indicated by the flow control reset information, a static method is used to control the flow of the game virtual transaction server. This ensures that when a reliable game virtual transaction request volume cannot be obtained, the game virtual transaction server is protected by flow control, taking into account the processing efficiency of the game virtual transaction server for game virtual transaction requests and the security of its operating status.

[0230] Step 708b: when the second interval between the current reporting time and the reference reporting time of the game virtual transaction server exceeds the startup threshold and the first interval does not exceed the disaster recovery threshold, determine and send flow control update information to the game virtual transaction server based on the game virtual transaction request volume;

[0231] The startup threshold is used to indicate the time required for the game virtual transaction server and the management server to complete the initialization deployment and enter the formal working state after data transmission is established between the game virtual transaction server and the management server. It can also be called the cold start time of the game virtual transaction server and the management server. Exemplarily, the startup threshold is an empirical value, such as 180 seconds. The reference reporting time is used to indicate the starting time for clearing obstacles to data transmission between the game virtual transaction server and the management server.

[0232] When the first interval does not exceed 15 seconds and the second interval between the current reporting time and the reference reporting time of the game virtual transaction server exceeds 180 seconds, the game virtual transaction server and the management server complete the initialization deployment, enter the formal working state, and are in a stable state. The flow control update information is obtained based on the game virtual transaction request volume forecast reported by the game virtual transaction server.

[0233] Step 708c: When the second interval between the current reporting time and the reference reporting time of the game virtual transaction server does not exceed the startup threshold, and the first interval does not exceed the disaster recovery threshold, send flow control reset information to the game virtual transaction server;

[0234] Exemplarily, when the first interval does not exceed 15 seconds and the second interval between the current reporting time and the reference reporting time of the game virtual transaction server does not exceed 180 seconds, the game virtual transaction server and the management server have not completed the initialization deployment and are in an unstable state, a static method is used to control the flow of the game virtual transaction server to ensure that when at least one of the game virtual transaction server and the management server has not completed the initialization deployment, the game virtual transaction server is protected by flow control, taking into account the processing efficiency of the game virtual transaction server for game virtual transaction requests and the safety of the operating status.

[0235] Step 708d: in the event of a transmission obstruction between the management server and the game virtual transaction server, determine the traffic quota limit for the game virtual transaction server during the disconnection disaster recovery period according to the flow control quota information;

[0236] The disconnection disaster recovery period is used to indicate the upper limit of the interval during which the flow control quota information provided by the management server is unreliable due to the obstruction of data transmission between the game virtual transaction server and the management server. During the disconnection disaster recovery period, although the data transmission between the game virtual transaction server and the management server is obstructed, considering the timeliness of the data, the flow control quota information has a reference value for flow control. In the case of exceeding the disconnection disaster recovery period, due to the obstruction of data transmission between the game virtual transaction server and the management server, the flow control quota information does not have a reference value for flow control. Exemplarily, the disconnection disaster recovery period is 5 minutes.

[0237] Step 710: the game virtual transaction server sends a stop deployment request to the management server;

[0238] The stop deployment request is used to instruct the game virtual transaction server to request no longer accepting the traffic control provided by the management server; illustratively, the game virtual transaction server sends a stop deployment request when its function changes and no longer supports the transaction business of virtual items, or sends a stop deployment request when the game virtual transaction server is shut down for maintenance. This embodiment does not limit the reason for sending the stop deployment request.

[0239] Step 712: the management server stops providing flow control to the game virtual transaction server when other game virtual transaction servers except the game virtual transaction server can carry the total flow data of the plurality of game virtual transaction servers for which the management server provides flow control;

[0240] Exemplarily, the first quota corresponding to the game virtual transaction server is subtracted from the total traffic quota to obtain a revised quota; when the revised quota is greater than the total traffic data of multiple game virtual transaction servers for which the management server provides traffic control, traffic control is stopped for the game virtual transaction server. The multiple game virtual transaction servers are all the game virtual transaction servers for which traffic control is provided before receiving the stop deployment request.

[0241] In summary, the method provided in this embodiment is that the management server determines the management method for limiting the traffic of the game virtual transaction server according to the time when the game virtual transaction server reports the game virtual transaction request volume; fully considers the time required for initialization deployment between the management server and the game virtual transaction server, and the credibility of the game virtual transaction request volume reported by the game virtual transaction server; and in the case of transmission obstruction between the management server and the game virtual transaction server, expands the traffic control according to the timeliness of the game transaction traffic quota provided by the management server in different situations; adopts dynamic or static methods to control the traffic of the business server, ensures the safe operation status of the business server, and takes into account the processing efficiency and operation status safety of the business server for the game virtual transaction request.

[0242] Those skilled in the art can understand that the above embodiments can be implemented independently, or the above embodiments can be freely combined to form new embodiments to implement the information configuration method of the present application.

[0243] Fig.14 A structural block diagram of an information configuration device provided by an exemplary embodiment of the present application is shown. The device is applied to a management server, and the management server is used to provide flow control for at least two distributed deployed service servers, and the device includes:

[0244] A first sending module 810 is used to send flow control quota information, where the flow control quota information is used to indicate a flow quota limit for the service server;

[0245] The receiving module 820 is used to receive the traffic data sent by the service server based on the information reporting period, where the traffic data is used to indicate the amount of service requests received by the service server in at least one of the information reporting periods before the current reporting time of sending the traffic data;

[0246] The first sending module 810 is also used to send flow control reset information to the business server when a first interval between the current reporting time corresponding to the traffic data and the last reporting time of the business server exceeds a disaster recovery threshold. The flow control reset information is used to indicate that the traffic quota limit of the business server is reset to a preset limit.

[0247] In an optional implementation of this embodiment, the first sending module 810 is further configured to:

[0248] Obtaining an influence coefficient of the service server; and sending the flow control reset information to the service server when the first interval exceeds the product of the information reporting period and the influence coefficient.

[0249] In an optional implementation of this embodiment, the first sending module 810 is further configured to:

[0250] The impact coefficient is determined according to the predicted business pressure of the business server, the predicted business pressure is used to indicate the predicted reception status of business requests to the business server, and there is an inverse correlation between the impact coefficient and the predicted business pressure; wherein, the predicted business pressure is used to indicate at least one of the historical business request volume of the business server, the number of online objects corresponding to the business server, and the number of appointment objects for the business request.

[0251] In an optional implementation of this embodiment, the first sending module 810 is further configured to:

[0252] Determining a first pressure coefficient based on a ratio between the number of appointment objects and the historical business request volume;

[0253] determining a second pressure coefficient based on a ratio between the number of online objects and the number of historical online objects;

[0254] The product of the first pressure coefficient and the second pressure coefficient is normalized and calculated to obtain the impact coefficient; wherein the historical business request volume is used to indicate the total number of business requests received by the business server within a preset historical period, and the historical number of online objects is used to indicate the average number of online objects within the preset historical period.

[0255] In an optional implementation of this embodiment, the device further includes:

[0256] A first determination module 830 is configured to determine flow control update information based on the flow data when a second interval between the current reporting time of the flow data and the reference reporting time of the business server exceeds a startup threshold and the first interval does not exceed the disaster recovery threshold;

[0257] The first sending module 810 is further used to send the flow control update information to the business server; wherein the reference reporting time is used to indicate the start time for clearing obstacles to data transmission between the business server and the management server.

[0258] In an optional implementation of this embodiment, the first determining module 830 is further configured to:

[0259] When the second interval exceeds the startup threshold and the first interval does not exceed the disaster recovery threshold, the product of the total traffic quota and the business server ratio is determined as the flow control update information; wherein the total traffic quota is used to indicate the total number of flow control quotas of multiple business servers for which the management server provides traffic control, and the business server ratio is the ratio between the traffic data of the business server and the total number of traffic data of the multiple business servers for which the management server provides traffic control.

[0260] In an optional implementation of this embodiment, the device further includes:

[0261] The first determining module 830 is configured to update the reference reporting time of the service server to the current reporting time of the traffic data when the first interval exceeds the disaster recovery threshold.

[0262] In an optional implementation of this embodiment, the first sending module 810 is further configured to:

[0263] When a second interval between the current reporting time of the traffic data and the reference reporting time of the business server does not exceed the startup threshold, and the first interval does not exceed the disaster recovery threshold, the flow control reset information is sent to the business server.

[0264] In an optional implementation of this embodiment, the receiving module 820 is further configured to:

[0265] Receiving a traffic cache queue sent by the service server based on an information reporting period, wherein the traffic cache queue is used to carry the traffic data of the service server;

[0266] The traffic cache queue includes at least two cache segments, and the traffic data determines the cache segment that carries the service request based on the time when the service server receives the service request.

[0267] In an optional implementation of this embodiment, the device further includes:

[0268] A first determining module 830 is configured to determine, when the predicted business pressure of the business server exceeds the pressure threshold, a ratio between a total traffic quota and the number of multiple business servers for which the management server provides traffic control as the flow control reset information, wherein the total traffic quota is the total number of flow control quotas of the multiple business servers for which the management server provides traffic control;

[0269] And / or, the first determination module 830 is used to determine the flow control cancellation indication as flow control reset information when the predicted business pressure of the business server does not exceed the pressure threshold, and the flow control cancellation indication is used to instruct the business server to turn off flow control.

[0270] In an optional implementation of this embodiment, the flow control quota information is also used to indicate the flow quota limit for the business server during the disconnection disaster recovery period when a transmission obstruction occurs between the management server and the business server.

[0271] In an optional implementation of this embodiment, the receiving module 820 is further used to receive a stop deployment request from the business server, where the stop deployment request is used to indicate that the business server requests to no longer accept the flow control provided by the management server;

[0272] The processing module 840 is used to stop providing flow control to the business server when other business servers except the business server can bear the total flow data of multiple business servers for which the management server provides flow control.

[0273] Fig.15 The structural block diagram of an information configuration device provided by an exemplary embodiment of the present application is shown. The device is applied to a business server, and there are at least two distributed business servers provided with flow control by a management server, and the device includes:

[0274] A second determination module 850, configured to determine the traffic quota limit of the service server according to the traffic control quota information, wherein the traffic control quota information is sent by the management server;

[0275] A second sending module 860 is used to report traffic data to the management server based on an information reporting period, where the traffic data is used to indicate the amount of service requests received by the service server in at least one of the information reporting periods before the current reporting time of sending the traffic data;

[0276] The second determination module 850 is also used to reset the traffic quota limit of the business server to a preset limit based on the flow control reset information. The flow control reset information is sent by the management server when the first interval between the current reporting time corresponding to the traffic data and the last reporting time of the business server exceeds the disaster recovery threshold.

[0277] In an optional implementation of this embodiment, the second determining module 850 is further configured to:

[0278] In the case where a transmission obstruction occurs between the management server and the business server, a flow quota limit for the business server during the disconnection disaster recovery period is determined according to the flow control quota information.

[0279] One point that needs to be explained is that the device provided in the above embodiment only uses the division of the above-mentioned functional modules as an example to implement its functions. In actual applications, the above-mentioned functions can be assigned to different functional modules according to actual needs, that is, the content structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[0280] Regarding the device in the above embodiment, the specific manner in which each module performs operations has been described in detail in the embodiment of the method; the technical effects achieved by each module performing operations are the same as those in the embodiment of the method, and will not be elaborated here.

[0281] An embodiment of the present application also provides a computer device, which includes: a processor and a memory, wherein a computer program is stored in the memory; the processor is used to execute the computer program in the memory to implement the information configuration method provided by the above-mentioned method embodiments.

[0282] Optionally, the computer device is a server. Fig.16 It is a structural block diagram of a server provided by an exemplary embodiment of the present application.

[0283] Typically, the server 2300 includes: a processor 2301 and a memory 2302 .

[0284] The processor 2301 may include one or more processing cores, such as a 4-core processor, an 8-core processor, etc. The processor 2301 may be implemented in at least one hardware form of digital signal processing (DSP), field programmable gate array (FPGA), and programmable logic array (PLA). The processor 2301 may also include a main processor and a coprocessor. The main processor is a processor for processing data in an awake state, also known as a central processing unit (CPU); the coprocessor is a low-power processor for processing data in a standby state. In some embodiments, the processor 2301 may be integrated with a graphics processing unit (GPU), which is responsible for rendering and drawing the content to be displayed on the display screen. In some embodiments, the processor 2301 may also include an artificial intelligence (AI) processor, which is used to process computing operations related to machine learning.

[0285] The memory 2302 may include one or more computer-readable storage media, which may be non-transitory. The memory 2302 may also include a high-speed random access memory, and a non-volatile memory, such as one or more disk storage devices, flash memory storage devices. In some embodiments, the non-transitory computer-readable storage medium in the memory 2302 is used to store at least one instruction, which is used to be executed by the processor 2301 to implement the information configuration method provided in the method embodiment of the present application.

[0286] In some embodiments, the server 2300 may also optionally include: an input interface 2303 and an output interface 2304. The processor 2301, the memory 2302, the input interface 2303, and the output interface 2304 may be connected via a bus or a signal line. Each peripheral device may be connected to the input interface 2303 and the output interface 2304 via a bus, a signal line, or a circuit board. The input interface 2303 and the output interface 2304 may be used to connect at least one peripheral device related to input / output (I / O) to the processor 2301 and the memory 2302. In some embodiments, the processor 2301, the memory 2302, the input interface 2303, and the output interface 2304 are integrated on the same chip or circuit board; in some other embodiments, any one or two of the processor 2301, the memory 2302, the input interface 2303, and the output interface 2304 may be implemented on a separate chip or circuit board, which is not limited in the embodiments of the present application. Those skilled in the art will appreciate that the structure shown above does not constitute a limitation on the server 2300 , and may include more or fewer components than shown in the figure, or combine certain components, or adopt a different component arrangement.

[0287] In an exemplary embodiment, a chip is also provided. The chip includes a programmable logic circuit and / or program instructions. When the chip runs on a computer device, it is used to implement the information configuration method described in the above aspects.

[0288] In an exemplary embodiment, a computer program product is also provided, the computer program product includes computer instructions, the computer instructions are stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium, and the processor reads and executes the computer instructions from the computer-readable storage medium to implement the information configuration method provided by each of the above method embodiments.

[0289] In an exemplary embodiment, a computer-readable storage medium is further provided, in which a computer program is stored. The computer program is loaded and executed by a processor to implement the information configuration method provided by the above-mentioned method embodiments.

[0290] A person skilled in the art will understand that all or part of the steps to implement the above embodiments may be accomplished by hardware or by instructing related hardware through a program, and the program may be stored in a computer-readable storage medium, and the above-mentioned storage medium may be a read-only memory, a disk or an optical disk, etc.

[0291] Those skilled in the art should be aware that in one or more of the above examples, the functions described in the embodiments of the present application can be implemented with hardware, software, firmware, or any combination thereof. When implemented using software, these functions can be stored in a computer-readable medium or transmitted as one or more instructions or codes on a computer-readable medium. Computer-readable media include computer storage media and communication media, wherein the communication media include any media that facilitates the transmission of a computer program from one place to another. The storage medium can be any available medium that a general or special-purpose computer can access.

[0292] The above description is only an optional embodiment of the present application and is not intended to limit the present application. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present application shall be included in the protection scope of the present application.

Claims

1. An information configuration method, characterized in that: The method is executed by a management server, and the management server is used to provide flow control for at least two distributed deployed service servers. The method includes: Sending flow control quota information, where the flow control quota information is used to indicate a flow quota limit for the service server; Receiving traffic data sent by the service server based on an information reporting period, the traffic data being used to indicate the amount of service requests received by the service server in at least one of the information reporting periods before the current reporting time of sending the traffic data; When a first interval between the current reporting time corresponding to the traffic data and the last reporting time of the business server exceeds a disaster recovery threshold, flow control reset information is sent to the business server, and the flow control reset information is used to indicate that the traffic quota limit of the business server is reset to a preset limit.

2. The method according to claim 1, characterized in that When a first interval between the current reporting time corresponding to the traffic data and the last reporting time of the service server exceeds a disaster recovery threshold, sending flow control reset information to the service server includes: Obtaining an influence coefficient of the business server; When the first interval exceeds the product of the information reporting period and the impact coefficient, the flow control reset information is sent to the service server.

3. The method according to claim 2, characterized in that The obtaining the influence coefficient of the business server includes: determining the impact coefficient according to the predicted business pressure of the business server, wherein the predicted business pressure is used to indicate the predicted reception status of the business request to the business server, and there is an inverse correlation between the impact coefficient and the predicted business pressure; The predicted business pressure is used to indicate at least one of the historical business request volume of the business server, the number of online objects corresponding to the business server, and the number of reserved objects for the business request.

4. The method according to claim 3, characterized in that The determining the impact coefficient according to the predicted business pressure of the business server includes: Determining a first pressure coefficient based on a ratio between the number of appointment objects and the historical business request volume; determining a second pressure coefficient based on a ratio between the number of online objects and the number of historical online objects; Normalizing the product of the first pressure coefficient and the second pressure coefficient to obtain the influence coefficient; The historical service request volume is used to indicate the total number of service requests received by the service server within a preset historical period, and the historical online object quantity is used to indicate the average value of the number of online objects within the preset historical period.

5. The method according to any one of claims 1 to 4, characterized in that: The method further comprises: Determine flow control update information based on the flow data when a second interval between the current reporting time of the flow data and the reference reporting time of the business server exceeds a startup threshold and the first interval does not exceed the disaster recovery threshold; Sending the flow control update information to the service server; The reference reporting time is used to indicate the starting time for clearing obstacles to data transmission between the service server and the management server.

6. The method according to claim 5, characterized in that When the second interval between the current reporting time of the traffic data and the reference reporting time of the business server exceeds the startup threshold and the first interval does not exceed the disaster recovery threshold, determining the flow control update information based on the traffic data includes: When the second interval exceeds the startup threshold and the first interval does not exceed the disaster recovery threshold, the product of the total traffic quota and the business server ratio is determined as the flow control update information; Among them, the total traffic quota is used to indicate the total flow control quotas of multiple business servers for which the management server provides flow control, and the business server ratio is the ratio between the flow data of the business server and the total flow data of the multiple business servers for which the management server provides flow control.

7. The method according to any one of claims 1 to 4, characterized in that: The method further comprises: When the first interval exceeds the disaster recovery threshold, the reference reporting time of the service server is updated to the current reporting time of the traffic data.

8. The method according to any one of claims 1 to 4, characterized in that: The method further comprises: When a second interval between the current reporting time of the traffic data and the reference reporting time of the business server does not exceed the startup threshold, and the first interval does not exceed the disaster recovery threshold, the flow control reset information is sent to the business server.

9. The method according to any one of claims 1 to 4, characterized in that: The receiving the traffic data sent by the service server based on the information reporting period includes: Receiving a traffic cache queue sent by the service server based on an information reporting period, wherein the traffic cache queue is used to carry the traffic data of the service server; The traffic cache queue includes at least two cache segments, and the traffic data determines the cache segment that carries the service request based on the time when the service server receives the service request.

10. The method according to any one of claims 1 to 4, characterized in that: The method further comprises at least one of the following: In the case where the predicted business pressure of the business server exceeds the pressure threshold, the ratio between the total traffic quota and the number of the multiple business servers for which the management server provides traffic control is determined as the flow control reset information, wherein the total traffic quota is the total number of flow control quotas of the multiple business servers for which the management server provides traffic control; When the predicted service pressure of the service server does not exceed the pressure threshold, the flow control cancellation indication is determined as flow control reset information, and the flow control cancellation indication is used to instruct the service server to turn off flow control.

11. The method according to any one of claims 1 to 4, characterized in that: The flow control quota information is also used to indicate the flow quota limit for the business server during the disconnection disaster recovery period when a transmission obstruction occurs between the management server and the business server.

12. The method according to any one of claims 1 to 4, characterized in that: The method further comprises: receiving a stop deployment request from the business server, wherein the stop deployment request is used to indicate that the business server requests to no longer accept the flow control provided by the management server; In the case that other service servers except the service server can bear the total amount of flow data of the plurality of service servers for which the management server provides flow control, flow control provision to the service server is stopped.

13. An information configuration method, characterized in that: The method is performed by a business server, and there are at least two distributed business servers provided with flow control by a management server. The method includes: Determining the traffic quota limit of the service server according to the traffic control quota information, wherein the traffic control quota information is sent by the management server; Reporting traffic data to the management server based on an information reporting period, the traffic data being used to indicate the amount of service requests received by the service server in at least one of the information reporting periods before the current reporting time of sending the traffic data; The traffic quota limit of the business server is reset to a preset limit according to the flow control reset information, and the flow control reset information is sent by the management server when the first interval between the current reporting time corresponding to the traffic data and the last reporting time of the business server exceeds the disaster recovery threshold.

14. The method according to claim 13, characterized in that The method further comprises: In the case where a transmission obstruction occurs between the management server and the business server, a flow quota limit for the business server during the disconnection disaster recovery period is determined according to the flow control quota information.

15. An information configuration device, characterized in that: The device is applied to a management server, and the management server is used to provide flow control for at least two distributed deployed service servers, and the device includes: A first sending module, used for sending flow control quota information, where the flow control quota information is used for indicating a flow quota limit for the service server; A receiving module, used to receive the traffic data sent by the service server based on the information reporting period, wherein the traffic data is used to indicate the amount of service requests received by the service server in at least one of the information reporting periods before the current reporting time of sending the traffic data; The first sending module is also used to send flow control reset information to the business server when a first interval between the current reporting time corresponding to the traffic data and the last reporting time of the business server exceeds a disaster recovery threshold. The flow control reset information is used to indicate that the traffic quota limit of the business server is reset to a preset limit.

16. An information configuration device, characterized in that: The device is applied to a business server, and there are at least two distributed business servers whose flow control is provided by a management server. The device includes: A second determination module, configured to determine the flow quota limit of the service server according to the flow control quota information, wherein the flow control quota information is sent by the management server; A second sending module, configured to report flow data to the management server based on an information reporting period, wherein the flow data is used to indicate the amount of service requests received by the service server in at least one of the information reporting periods before the current reporting time of sending the flow data; The second determination module is also used to reset the traffic quota limit of the business server to a preset limit based on the flow control reset information. The flow control reset information is sent by the management server when the first interval between the current reporting time corresponding to the traffic data and the last reporting time of the business server exceeds the disaster recovery threshold.

17. A computer device, characterized in that: The computer device includes: a processor and a memory, wherein the memory stores at least one program; the processor is used to execute the at least one program in the memory to implement the information configuration method as described in any one of claims 1 to 14.

18. A computer-readable storage medium, characterized in that: The readable storage medium stores executable instructions, and the executable instructions are loaded and executed by a processor to implement the information configuration method as described in any one of claims 1 to 14.

19. A computer program product, characterized in that The computer program product includes computer instructions, which are stored in a computer-readable storage medium. The processor reads and executes the computer instructions from the computer-readable storage medium to implement the information configuration method as described in any one of claims 1 to 14.

Images