A risk control strategy verification method and device based on online environment

Abstract

One or more embodiments of the present specification provide a risk control strategy verification method and device based on an online environment, wherein the method includes: intercepting target business requests from online business traffic according to preset business interception rules; calling the risk control strategy to be verified to perform business processing on a specified number of the target business requests to obtain business processing result information; and determining the availability verification result information of the risk control strategy based on the business processing result information.

Description

Technical Field

[0001] This document relates to the field of Internet technology, and in particular to a risk control strategy verification method and device based on an online environment. Background Art

[0002] At present, with the rapid development of Internet technology, the back-end servers that provide services for front-end applications are facing more and more network risks and resource risks. Therefore, it is necessary to deploy risk control strategies for servers on demand to improve their risk resistance and ensure the stability and efficiency of their service capabilities.

[0003] Currently, after the risk control strategy is verified offline, it will be directly published to the server for online operation, and then the availability of the risk control strategy in the online scenario will be judged by observing the changes in the server operation log. In the above method, the minimum dimension of risk control strategy deployment is a single server. If the risk control strategy is lossless to the business, then the above method is still feasible. However, if the risk control strategy is lossy to the business, then once the availability of the risk control strategy does not meet expectations, it will have an adverse impact on a large number of businesses on the server, causing large-scale losses.

[0004] Therefore, it can be seen that it is necessary to provide a risk control strategy availability verification solution with a smaller impact range. Summary of the invention

[0005] The purpose of one or more embodiments of this specification is to provide a risk control strategy verification method based on an online environment. The risk control strategy verification method based on an online environment is applied to a target node server, and the method includes:

[0006] According to the preset business interception rules, target business requests are intercepted from online business traffic.

[0007] The risk control strategy to be verified is called to perform business processing on a specified number of the target business requests to obtain business processing result information.

[0008] According to the business processing result information, availability verification result information of the risk control strategy is determined.

[0009] The purpose of one or more embodiments of this specification is to provide a risk control strategy verification device based on an online environment. The risk control strategy verification device based on an online environment is applied to a target node server, and the device includes:

[0010] The interception module intercepts target business requests from online business traffic according to preset business interception rules.

[0011] The business processing module calls the risk control strategy to be verified to perform business processing on a specified number of the target business requests and obtain business processing result information.

[0012] An availability verification module determines availability verification result information of the risk control strategy according to the business processing result information.

[0013] The purpose of one or more embodiments of this specification is to provide a risk control strategy verification system based on an online environment, including: a first host computer, a second host computer, and a target node server;

[0014] The first host computer is used to send a slice code of a preset business interception rule to the target node server;

[0015] The second host computer is used to send information related to the policy to be verified to the target node server; the information related to the policy to be verified includes business processing policy change information or risk control business processing code;

[0016] The target node server is used to locally deploy the preset business interception rules according to the aspect code, and to locally deploy the risk control strategy to be verified according to the relevant information of the strategy to be verified; and to intercept the target business request from the online business traffic according to the preset business interception rules, call the risk control strategy to be verified to perform business processing on a specified number of the target business requests, obtain business processing result information, and determine the availability verification result information of the risk control strategy according to the business processing result information.

[0017] An object of one or more embodiments of the present specification is to provide a risk control strategy verification device based on an online environment, comprising: a processor; and a memory arranged to store computer executable instructions.

[0018] When the computer executable instructions are executed, the processor intercepts the target business request from the online business traffic according to the preset business interception rules; calls the risk control strategy to be verified to perform business processing on a specified number of the target business requests to obtain business processing result information; and determines the availability verification result information of the risk control strategy based on the business processing result information.

[0019] The purpose of one or more embodiments of this specification is to provide a storage medium for storing computer executable instructions. When the executable instructions are executed by a processor, according to a preset business interception rule, the target business request is intercepted from the online business traffic; the risk control strategy to be verified is called to perform business processing on a specified number of the target business requests to obtain business processing result information; and according to the business processing result information, the availability verification result information of the risk control strategy is determined. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] In order to more clearly illustrate one or more embodiments of this specification or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in one or more of this specification. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative labor.

[0021] Figure 1 A schematic diagram of an application scenario of a risk control strategy verification system based on an online environment provided in one or more embodiments of this specification;

[0022] Figure 2 A schematic diagram of information interaction of a risk control strategy verification system based on an online environment provided by one or more embodiments of this specification;

[0023] Figure 3 A first flow chart of a risk control strategy verification method based on an online environment provided in one or more embodiments of this specification;

[0024] Figure 4 A second flow chart of a risk control strategy verification method based on an online environment provided in one or more embodiments of this specification;

[0025] Figure 5 A third flow chart of a risk control strategy verification method based on an online environment provided in one or more embodiments of this specification;

[0026] Figure 6 A fourth flow chart of a risk control strategy verification method based on an online environment provided in one or more embodiments of this specification;

[0027] Figure 7 A fifth flow chart of a risk control strategy verification method based on an online environment provided in one or more embodiments of this specification;

[0028] Figure 8 A sixth flow chart of a risk control strategy verification method based on an online environment provided in one or more embodiments of this specification;

[0029] Fig. 9 A seventh flow chart of a risk control strategy verification method based on an online environment provided in one or more embodiments of this specification;

[0030] Fig.10An eighth flow chart of a risk control strategy verification method based on an online environment provided in one or more embodiments of this specification;

[0031] Fig.11 A ninth flow chart of a risk control strategy verification method based on an online environment provided in one or more embodiments of this specification;

[0032] Fig.12 A logical diagram of a risk control strategy for verifying a single business request in an online environment provided in one or more embodiments of this specification;

[0033] Fig.13 A schematic diagram of the module composition of a risk control strategy verification device based on an online environment provided in one or more embodiments of this specification;

[0034] Fig.14 A schematic diagram of the structure of a risk control strategy verification device based on an online environment provided in one or more embodiments of this specification. DETAILED DESCRIPTION

[0035] In order to enable persons skilled in the art to better understand the technical solutions in one or more embodiments of this specification, the technical solutions in one or more embodiments of this specification will be clearly and completely described below in conjunction with the drawings in one or more embodiments of this specification. Obviously, the described embodiments are only one or more partial embodiments of this specification, rather than all embodiments. Based on one or more embodiments of this specification, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of this document.

[0036] It should be noted that, in the absence of conflict, one or more embodiments and features in the embodiments in this specification can be combined with each other. One or more embodiments of this specification will be described in detail below with reference to the drawings and in combination with the embodiments.

[0037] One or more embodiments of the present specification provide a risk control strategy verification method and device based on an online environment, which intercepts target business requests from online business traffic according to preset business interception rules, and then calls the risk control strategy to be verified to perform business processing on a specified number of the target business requests to obtain business processing result information, and then determines the availability verification result information of the risk control strategy based on the business processing result information. In this way, a specified number of target business requests can be intercepted from the online business traffic to verify the availability of the risk control strategy, and the impact scope of the verification is limited to the specified number of target business requests. Compared with the existing method, the impact scope of the online verification of the risk control strategy can be effectively narrowed, and the adverse effects caused by the risk control strategy availability not meeting expectations can be reduced.

[0038] Figure 1 A schematic diagram of an application scenario of a risk control strategy verification system based on an online environment provided in one or more embodiments of this specification, such as Figure 1 As shown, the system includes: a first host computer, a second host computer and a target node server; wherein the target node server can be directly or indirectly connected to the client, and a front-end application is installed on the client. The target node server can be a server that provides background services for the front-end application and processes the business requests corresponding to the application. In addition, the target node server can also be connected to other business servers, can accept calls from other business servers, and process business requests sent by other business servers. The target node server can be an independent server or a server as shown in FIG. Figure 1 Shown is a server in a server cluster, which can be an intermediate node server for processing business requests, such as a mid-table server, or an end node server for processing business requests. The first host computer and the second host computer are both host management machines connected to the target node server, wherein the first host computer is responsible for pushing business interception rules to the target node server, and the second host computer is responsible for pushing risk control strategies to the target node server. The first host computer and the second host computer can be independent servers, and in some cases can also be integrated on the same server to implement the above two functions. In order to make the description of this specification clearer, in the following exemplary description, the first host computer and the second host computer are exemplified as independent servers.

[0039] It should be noted that the risks dealt with by the risk control strategy in this specification are not limited to the risks faced by the target node server itself, and may include the internal and / or external risks of the target node server, for example, the risks faced by the server cluster in which the target node server is located as a whole, or the risks faced by the business processed by the target node server, etc. For example, taking external risks as an example, in a server cluster, at least servers A, B, C, and D are included. In the business link of a business, there is a call link in which A calls B and B calls C. If server C is inefficient or down due to some factors, then there are risks for the entire server cluster and the execution of the business. In this case, it is necessary to deploy corresponding risk control strategies to avoid risks. If C and D have the same business functions, then server B can be selected as the target node server. The risk control strategy can be to modify the call link of B calling C to the call link of B calling D, so as to ensure the execution of the business. For another example, taking the internal risk as an example, the original business processing strategy of server B for processing business X, that is, the original processing logic, is to read data from the local cache and return it, but due to some factors, the cache is wrong and the cache is unavailable at this time. If it is still read, it may return wrong data, resulting in business execution errors. In this case, server B can be selected as the target node server, and the risk control strategy can be to set server B not to read the cache when processing business X and directly return a null value, so that the business requester reads the business data from the database instead, thereby avoiding business execution errors. For another example, taking the combined internal and external risks as an example, the resources of server B originally processing various businesses are average. In a certain period of time, the business volume of business X surges and the business priority increases. If the processing resources are still evenly distributed, then it will cause processing delays and backlogs of business X. In this case, server B can be selected as the target node server, and the risk control strategy is to re-divide the processing resources of server B, increase the processing resources for processing business X, or increase the priority of processing business X and reduce the priority of processing business Y and Z, so as to ensure the execution of business X and reduce processing delays or backlogs.

[0040] In actual applications, due to changes in relevant codes, changes in business parameters, differences in online and offline operating environments, etc., the above risk control strategies may be actually invalid after they are launched (i.e., the availability does not meet expectations). Since the above risk control strategies are unavailable, they may have an adverse impact on the execution of the business. Therefore, it is necessary to verify the above risk control strategies in a small range in the online environment. One of the purposes of the solution provided in this specification is to reduce the impact of the risk control strategy availability verification. In particular, please combine Figure 2 , Figure 2This is a schematic diagram of information interaction of a risk control strategy verification system based on an online environment provided in one or more embodiments of this specification. The specific process of risk control strategy verification based on an online environment is as follows:

[0041] Step S101: The first host computer sends a slice code of a preset business interception rule to a target node server.

[0042] Step S102: The target node server locally deploys a preset business interception rule according to the aspect code, and intercepts the target business request from the online business traffic according to the preset business interception rule.

[0043] Step S103: The second host computer sends information related to the policy to be verified to the target node server, where the information related to the policy to be verified includes business processing policy change information or risk control business processing code.

[0044] Step S104: the target node server locally deploys the risk control policy to be verified according to the relevant information of the policy to be verified.

[0045] Step S105: The target node server invokes the risk control policy to be verified to perform business processing on a specified number of target business requests to obtain business processing result information.

[0046] Step S106: The target node server determines availability verification result information of the risk control strategy according to the business processing result information.

[0047] Among them, deployment can mean configuration and effectiveness. For example, deploying preset business interception rules can mean configuring preset business interception rules and making them effective. Deploying risk control strategies can mean configuring risk control strategies and making them effective. In addition, deployment can also mean only configuration without triggering effectiveness. The effective action is triggered according to the call of the target node server. For example, deploying preset business interception rules can mean configuring preset business interception rules, which are triggered to take effect when the call of the target node server is received. Deploying risk control strategies can mean configuring risk control strategies, which are triggered to take effect when the call of the target node server is received.

[0048] Based on the above process, the target node server can intercept a specified number of target business requests from the online business traffic to verify the availability of the risk control strategy. The impact of the verification is limited to the specified number of target business requests. Compared with the existing method, it can effectively narrow the impact of online verification of the risk control strategy and reduce the adverse effects caused by the fact that the availability of the risk control strategy does not meet expectations.

[0049] The above process is further described below in conjunction with a method embodiment.

[0050] Figure 3 A first flow chart of a risk control strategy verification method based on an online environment provided in one or more embodiments of this specification, Figure 3 The method in can be Figure 1 The target node server in is executed, such as Figure 3 As shown, the method comprises at least the following steps:

[0051] Step S202: intercepting a target service request from online service traffic according to a preset service interception rule.

[0052] Among them, the above-mentioned preset business interception rules can be flexibly set according to the needs of risk control and combined with the characteristics of business requests. The purpose is to be able to identify and intercept target business requests from online business traffic.

[0053] Step S204: calling the risk control strategy to be verified to perform business processing on a specified number of target business requests to obtain business processing result information.

[0054] Among them, the above-mentioned risk control strategy refers to a business processing strategy set up to deal with risks. Its differences compared to the original business processing strategy include but are not limited to differences in business processing logic, algorithms, calling objects, calling interfaces, parameters or values. Technical personnel in this field can flexibly set it according to actual needs, and this specification does not limit it.

[0055] Step S206: Determine availability verification result information of the risk control strategy according to the business processing result information.

[0056] The above-mentioned risk control strategy verification method based on the online environment intercepts the target business request from the online business traffic according to the preset business interception rules, and then calls the risk control strategy to be verified to perform business processing on a specified number of the target business requests to obtain business processing result information, and then determines the availability verification result information of the risk control strategy based on the business processing result information. The specified number of target business requests can be intercepted from the online business traffic to verify the availability of the risk control strategy. The impact scope of the verification is limited to the specified number of target business requests. Compared with the existing method, it can effectively narrow the impact scope of the online verification of the risk control strategy and reduce the adverse effects caused by the situation that the availability of the risk control strategy does not meet expectations.

[0057] In one or more embodiments of this specification, please refer to Figure 4 As shown, the above step S202 intercepts the target service request from the online service traffic according to the preset service interception rule, which may include:

[0058] Step S2021: intercept the target business request from the online business traffic by executing the aspect code of the preset business interception rule, wherein the aspect code is prepended to the business processing code, and the business processing code is used to process the target business request.

[0059] Among them, the above-mentioned aspect code refers to the program code written using the aspect-oriented programming method. The full name of aspect-oriented programming in English is Aspect Oriented Programming, referred to as AOP. It is a technology that realizes the dynamic and unified addition of functions to the program without modifying the source code through pre-compilation and runtime dynamic proxy. It uses a technology called "cross-cutting" to dissect the inside of the encapsulated object, encapsulate the common behaviors that affect multiple classes into a reusable module, and name it Aspect aspect. The so-called aspect, in simple terms, is the logic that is unrelated to the business but is commonly called by the business module. Encapsulating it is convenient to reduce the system's duplicate code, reduce the coupling degree of the module, and utilize future operability and maintainability. The aspect code can be used to isolate the various parts of the business logic, thereby reducing the coupling degree between the various parts of the business logic, improving the reusability of the program, and improving development efficiency.

[0060] In this specification, the preset business interception rules are dynamically deployed in the form of aspect codes. Since the execution of the preset business interception rules themselves will not affect the processing results of the business, the preset business interception rules are weakly coupled with the business processing logic and can be dynamically deployed in the form of aspect codes. In actual applications, corresponding business interception rules can be flexibly formulated for each business according to the risks faced, or business interception rules can be adjusted, and deployed and removed in the form of aspect codes. It should be noted that the aspect code should be placed before the business processing code to intercept the business request before it is processed according to the original business processing strategy. Through the above implementation method, the preset business interception rules can be dynamically added, changed and deleted without modifying the source program code. It has high flexibility and convenience and can be flexibly and conveniently implemented in online scenarios.

[0061] Based on the above implementation, in one or more embodiments of this specification, please refer to Figure 5 As shown, before the above step S2021 intercepts the target business request from the online business traffic by executing the slice code of the preset business interception rule, it may also include:

[0062] Step S2011: receiving the slice code of the preset business interception rule sent by the first host computer.

[0063] Step S2012: inject the aspect code before the business processing code through a dynamic code injection tool.

[0064] In combination with the above description of the risk control strategy verification system based on the online environment, the first host computer is the host management computer responsible for pushing business interception rules to the target node server. When the risk control strategy needs to be launched online, the target node server is first selected according to the risk control requirements, and then the first host computer pushes the preset business interception rules to the target node server. Specifically, the preset business interception rules can be pushed by sending the aspect code of the preset business interception rules. After receiving the above aspect code, the target node server can inject the aspect code into the business processing code through the dynamic code injection tool to complete the deployment of the preset business interception rules. Among them, the above dynamic code injection tool can include any tool that can realize the aspect code injection function, such as the unified aspect technology component Awatch, so as to realize the dynamic implantation of aspect code, which has high convenience and stability.

[0065] In addition, based on the aforementioned implementation, in one or more embodiments of this specification, the above-mentioned slice code includes the service parameters and the target interception quantity corresponding to the target service request; please refer to Figure 6 As shown, the above step S2021 intercepts the target business request from the online business traffic by executing the slice code of the preset business interception rule, including:

[0066] Step S20211: Determine whether the value of the counter has been reset to zero, wherein the initial value of the counter is equal to the number of target interceptions.

[0067] Step S20212: If it is not reset to zero, intercept the target service request from the online service traffic according to the service parameter.

[0068] Step S20213: If it has returned to zero, stop intercepting the target service request.

[0069] It is easy to understand that the target node server may handle multiple services. In order to intercept the target business request, the above-mentioned aspect code should also include an interception algorithm, which may include a matching interception algorithm, which can identify and intercept the target business request by matching business parameters. The above-mentioned business parameters may include but are not limited to business type identification information, business source identification information, business function identification information, etc., so as to achieve accurate matching and interception of the target business request according to the business parameters.

[0070] In addition, since one of the purposes of this implementation is to select a small number of business requests for verification in order to reduce the adverse effects when the risk control strategy is unavailable, the number of interceptions also needs to be limited. In this regard, this implementation sets a counter based on the aspect code, and constrains the interception events through the counter to achieve controllable scope of impact of risk control strategy verification, and control the adverse effects of online verification of risk control strategies to a smaller range.

[0071] In addition, considering that the interception process and the verification process are not necessarily synchronized, this embodiment selects the target interception number as the interception counting basis, and the target interception number can be greater than or equal to the specified number specified in step S204, and the specified number represents the number of target business requests that need to be processed using the risk control strategy. When the target interception number is greater than the specified number, the counter can be decremented by one according to the interception event of the target business request until the counter value returns to zero; when the target interception number is equal to the specified number, the counter can be decremented by one according to the verification event of the target business request until the counter value returns to zero, wherein the above-mentioned verification event refers to an event in which the target business request is processed according to the risk control strategy to be verified. Specifically, in one or more embodiments of this specification, please refer to Figure 7 As shown, the method also includes:

[0072] Step S205: Every time verification completion information is detected, the value of the counter is reduced by one until the value of the counter returns to zero, wherein the verification completion information is used to indicate that the target business request has completed business processing according to the risk control policy to be verified.

[0073] Through this implementation, the interception event of the target business request is strongly associated with the verification event. The target business request can be continuously intercepted before the risk control strategy verification is completed, and the interception of the target business request can be stopped immediately after the risk control strategy verification is completed, thereby ensuring that the impact scope of the risk control strategy verification is controllable to the greatest extent, and controlling the adverse effects of the online verification of the risk control strategy to a smaller range.

[0074] Considering that the target node server may process multiple services, it will receive a large number of different service requests. In order to distinguish the target service requests, in one or more embodiments of this specification, please refer to Figure 8 As shown, before the above step S204 calls the risk control strategy to be verified to process the specified number of target business requests, it also includes:

[0075] Step S2031: Add an interception success mark to the call chain log corresponding to the above target business request.

[0076] Step S2032: For other service requests in the online service traffic to which the above interception success mark is not added, the original service processing strategy corresponding to the above other service requests is used to perform service processing.

[0077] Step S2033: for the target business requests to which the above interception success mark has been added in the above online business traffic, trigger the step of calling the risk control policy to be verified to perform business processing on a specified number of the target business requests.

[0078] Among them, the call chain log tracelog is an event tracking log widely used in the microservice architecture, wherein the microservice architecture is a distributed architecture, which divides service units according to business. A distributed system often has many service units, and the target node server of this embodiment can be understood as a service unit in the distributed system. Due to the large number of service units, for businesses with higher complexity, if errors and exceptions occur, it is difficult to locate them. This is mainly reflected in the fact that a request may need to call many services, and the complexity of calling internal services determines that the problem is difficult to locate. Therefore, in the microservice architecture, distributed link tracking must be implemented to follow up on which services are involved in a request and what the order of participation is, so that the steps of each request are clearly visible, and problems can be quickly located. The call chain log records the following situation: each time the caller initiates a request to the system service, it will generate the relevant call chain log tracelog generated by this call, generate a global code traceId, and generate work information of different nodes. When the first service generates the global code traceId, it is placed in the header and passed to the subordinate service. The subordinate service can receive the link log code by setting the Filter filter (other solutions are also possible), record the log information of the call, and then pass the global code to the subordinate service. Finally, after the business call is completed, the call log is recorded and the global code generated by this call chain is cleared.

[0079] Based on the above description, this implementation can be applied to a distributed microservice architecture, and the interception success mark can be recorded based on the call chain log. In this way, in the subsequent business processing process, the target business request and other business requests can be distinguished according to the interception success mark, so that the corresponding business processing strategy can be used for business processing in a targeted manner, thereby improving the accuracy of risk control strategy verification.

[0080] It should be noted that, in the case of a distributed microservice architecture, the target node server can be a service node in the distributed microservice architecture. For complex situations where there are a large number of business requests, when intercepting the target business request, you can read the call chain log tracelog based on the call chain log and select the target business request with the tracelog method action.doaction (indicating that the business request has a core action at the current node and needs to be processed) to ensure that the intercepted target business request can use the risk control strategy for business processing.

[0081] As mentioned above, the first host computer is responsible for pushing business interception rules to the target node server, and the second host computer is responsible for pushing risk control strategies to the target node server. Based on this, on the target node server, the deployment of preset business interception rules and the deployment of risk control strategies are generally not synchronized. In order to avoid the risk control strategy being deployed too early and processing the unintercepted business requests on the target node server after it takes effect, which may cause adverse effects, the preset business interception rules can be deployed first, and then the risk control strategy can be deployed. Specifically, after the first host computer detects that the preset business interception rules have been deployed, it sends an interception rule deployment completion indication message to the second host computer. After the second host computer receives the interception rule deployment completion indication message, it triggers the push of the risk control strategy to be verified to the target node server. In this process, some target business requests may have been intercepted before the risk control strategy is deployed. For these target business requests, the original business processing strategy corresponding to the target business request can be used for business processing without waiting for the deployment of the risk control strategy. Specifically, in one or more embodiments of this specification, please refer to Fig. 9 As shown, the above step S204 calls the risk control strategy to be verified to perform business processing on a specified number of target business requests, which may include:

[0082] S2041: Check whether the risk control strategy to be verified has been deployed.

[0083] S2042: If the deployment is not completed, the original business processing strategy corresponding to the target business request is used to perform business processing.

[0084] S2043: If the deployment is complete, then a specified number of target business requests are processed according to the risk control strategy to be verified.

[0085] Since the purpose of intercepting the target business request is to verify the risk control strategy, this implementation will not affect the verification result of the risk control strategy, and can ensure that each business request is processed in a timely manner to avoid business processing delays or backlogs.

[0086] There may be a variety of implementations for the deployment of risk control strategies. This specification exemplifies two deployment methods, replacement and addition. Those skilled in the art may flexibly change and expand on this basis to obtain more implementation methods, all of which should be within the scope of protection of this application.

[0087] The first risk control strategy deployment method uses the risk control strategy to replace the original business processing strategy. Specifically, in one or more embodiments of this specification, please refer to Fig.10 As shown, before the risk control strategy to be verified is called in the above step S204 to process a specified number of target business requests, the following may also be included:

[0088] Step S2071: receiving the service processing policy change information sent by the second host computer.

[0089] Step S2071: According to the business processing policy change information, the original business processing policy corresponding to the target business request is changed to obtain a deployed risk control policy to be verified.

[0090] After the risk control strategy to be verified is called in the above step S204 to process the specified number of target business requests, the following further includes:

[0091] Step S208: restore the above risk control strategy to the above original business processing strategy.

[0092] The business processing strategy change information includes the information necessary to adjust the original business processing strategy to the risk control strategy to be verified. According to the business processing strategy change information, the target node server can adjust the original business processing strategy to obtain the risk control strategy to be verified. In order to reduce the impact of the risk control strategy verification, it is also necessary to restore the risk control strategy to the original business processing strategy after using the risk control strategy to process a specified number of target business requests. After that, when the risk control strategy is verified and it is determined that the risk control strategy meets expectations, the second host computer will formally push the risk control strategy for implementation.

[0093] This replacement deployment method has little impact on the source program code. The risk control strategy can be deployed and verified without major modifications to the source program code. It is easy to implement and has low risks.

[0094] Based on the above implementation, in one or more embodiments of this specification, the above target node server belongs to any business processing server in the distributed server cluster; the above receiving the business processing strategy change information sent by the second host computer may include:

[0095] Receive the business processing policy change information sent by the second host computer through the distributed configuration management system DRM.

[0096] Among them, the distributed configuration management system (DRM, Distributed Resource Management) can be a real-time dynamic background configuration management system in a distributed environment, which can send business processing policy change information in the form of configuration information to one, multiple or all business processing servers in a distributed server cluster, which includes a server and a client, wherein the server is located on the second host computer and the client is located on the target node server. The server can push the above-mentioned business processing policy change information to the client, and the client is responsible for modifying the original business processing policy to a risk control strategy to be verified on the target node server according to the business processing policy change information. During this process, if the server push fails due to some factors, the client can also actively pull the above-mentioned business processing policy change information from the server to ensure the successful deployment of the business processing policy change information.

[0097] This embodiment can realize accurate push of business processing strategy change information through a distributed configuration management system, and ensure the successful deployment of business processing strategy change information. In addition, the benefit of using a distributed configuration management system is that it can realize the dynamic deployment of risk control strategies. In this way, combined with the dynamic deployment of the preset business interception rules mentioned in the above embodiment, the dynamic deployment and adjustment of the entire verification process of the risk control strategy can be realized. Based on this, preset business interception rules and risk control strategies can be flexibly added, so as to perform short online verification for risk control strategies of different businesses, and control the adverse effects of online verification of risk control strategies to a smaller range to the maximum extent. In addition, the benefit of using a distributed configuration management system is that, when the above risk control strategy verification is completed and it is determined that the above risk control strategy meets expectations, the second host computer can quickly push the verified risk control strategy to each node server using the distributed configuration management system to realize the distributed rapid deployment of the above risk control strategy and ensure the consistency of the risk control strategy between each node server.

[0098] It should be noted that the push of the preset business interception rules in the aforementioned embodiment can also be implemented using the distributed configuration management system DRM. The DRM server is configured on the first host computer, and the DRM client is configured on the target node server. The first host computer pushes the aspect code corresponding to the preset business interception rule to the DRM client through the DRM server. The target node server can use Awatch to inject the above-mentioned aspect code before the business processing code to implement the deployment of the preset business interception rules.

[0099] The second risk control strategy deployment method is to add a risk control strategy. Specifically, in one or more embodiments of this specification, please refer to Fig.11 As shown, before the above step S204 calls the risk control strategy to be verified to process the specified number of target business requests, it also includes:

[0100] Step S2091: receiving the risk control business processing code sent by the second host computer.

[0101] Step S2092: locally deploy the risk control strategy to be verified according to the risk control business processing code, wherein the risk control strategy is in parallel with the original business processing strategy corresponding to the target business request.

[0102] Among them, the above-mentioned risk control business processing code is a code used to deploy the above-mentioned risk control strategy to be verified. According to the risk control business processing code, the target node server can add the above-mentioned risk control strategy locally, which is equivalent to adding a logical channel. The intercepted target business request can go through the logical channel corresponding to the risk control strategy, and the unintercepted business request continues to go through the logical channel corresponding to the original business processing strategy. This implementation method can realize the parallel of risk control strategy and original business processing strategy. The target node server can select the appropriate logical channel to process business requests as needed, and has good compatibility.

[0103] In one or more embodiments of this specification, the above-mentioned determining the availability verification result information of the risk control strategy according to the business processing result information includes:

[0104] If the business processing result information indicates that the business processing result of the target business request is consistent with the expected execution result of the risk control strategy, it is determined that the risk control strategy is available.

[0105] For example, in the case where the specified number is multiple, if the above-mentioned business processing result information represents that the business processing results of calling the above-mentioned risk control strategy for each of the above-mentioned specified business requests of the specified number are consistent with the expected results of the above-mentioned risk control strategy, then it is determined that the above-mentioned risk control strategy is available; otherwise, it is determined that the above-mentioned risk control strategy is not available.

[0106] It should be noted that in any of the foregoing embodiments of the present specification, the above-mentioned specified number can be 1, 2, or more, and those skilled in the art can flexibly set the value of the specified number based on actual needs to achieve controllable impact range of risk control strategy verification and control the adverse effects of online verification of risk control strategies within a suitable smaller range.

[0107] Preferably, in one or more embodiments of the present specification, the above-mentioned specified number of target business requests is one target business request. In this way, the online verification of the risk control strategy can be realized through a single business request, and the verification of the risk control strategy only affects the single business request, and the verification of the availability of the risk control strategy can be completed with minimal impact on the online business traffic.

[0108] Regarding the selection of the above-mentioned target node server, in order to further reduce the adverse effects of online verification of risk control strategies, the selected target node server should be a server in the distributed server cluster whose online business traffic is gray, that is, the online business traffic is relatively small. Since the traffic of the target node server is originally small, the number of businesses affected when the online verification risk control strategy is unavailable can be further reduced, and the adverse effects of online verification of risk control strategies can be controlled within a smaller range, adding a layer of protection for the online verification of risk control strategies, and achieving the effect of multiple risk controls as a whole.

[0109] For ease of understanding, a specific example is given to illustrate the above risk control strategy verification method based on the online environment. For example, a specified number of target business requests is taken as one target business request, that is, a single business request is intercepted online to verify the risk control strategy. Please refer to Fig.12 Combined with the above-mentioned embodiments, the main process includes:

[0110] Step S301: Receive the preset business interception rules pushed by the first host computer, and then use the unified aspect technology component Awatch to dynamically deploy the preset business interception rules locally. The rule is to intercept the target business request with the method action.doAction in the call chain log tracelog, and the number of interceptions is 1.

[0111] Step S302: After the preset service interception rule takes effect, the counter is set to 1, the target service request is intercepted, and an interception success mark is added to the call chain log corresponding to the intercepted target service request.

[0112] Step S303: Receive and deploy the risk control policy to be verified pushed by the second host computer through the distributed configuration management system DRM. After the risk control policy to be verified takes effect, the risk control strategy is used to perform business processing on a target business request to obtain business processing result information. In addition, for other business requests other than the one target business request, the original business processing strategy is used for business processing.

[0113] Step S304: After the processing of the above-mentioned one target business request is completed, the trigger counter is reset to zero, the preset business interception rule is disabled, and the risk control strategy is restored to the original business processing strategy to process subsequent business requests, that is, everything is restored to the original state.

[0114] Step S305: If the business processing result information indicates that the business processing result of the target business request is consistent with the expected execution result of the risk control strategy, it is determined that the risk control strategy is available.

[0115] Step S306: When it is determined that the risk control strategy is available, the second host computer pushes the risk control strategy to the relevant node servers in the distributed server cluster where the target node server is located, so as to implement the risk control strategy, wherein the relevant node servers refer to the servers related to the risk control strategy.

[0116] Through the above embodiment, only a single business request is needed to realize the online verification of the risk control strategy. The verification of the risk control strategy only affects the single business request. The verification of the availability of the risk control strategy can be completed with minimal impact on the online business traffic.

[0117] The risk control strategy verification method based on the online environment in one or more embodiments of the present specification intercepts the target business request from the online business traffic according to the preset business interception rules, and then calls the risk control strategy to be verified to perform business processing on a specified number of the target business requests to obtain business processing result information, and then determines the availability verification result information of the risk control strategy based on the business processing result information. In this way, a specified number of target business requests can be intercepted from the online business traffic to verify the availability of the risk control strategy, and the impact scope of the verification is limited to the specified number of target business requests. Compared with the existing method, the impact scope of the online verification of the risk control strategy can be effectively narrowed, and the adverse effects caused by the risk control strategy availability not meeting expectations can be reduced.

[0118] Corresponding to the above Figures 3 to 11 The risk control strategy verification method based on the online environment described above is based on the same technical concept. One or more embodiments of this specification also provide a risk control strategy verification device based on the online environment. Fig.13 A schematic diagram of the module composition of a risk control strategy verification device based on an online environment provided in one or more embodiments of this specification, the device is used to execute Figures 3 to 11 The risk control strategy verification method based on the online environment described, such as Fig.13As shown, the device includes: an interception module 1302, a service processing module 1304 and an availability verification module 1306, and the interception module 1302, the service processing module 1304 and the availability verification module 1306 are connected in sequence.

[0119] In a specific embodiment, the interception module 1302 is used to intercept target business requests from online business traffic according to preset business interception rules; the business processing module 1304 is used to call the risk control strategy to be verified to perform business processing on a specified number of the target business requests to obtain business processing result information; the availability verification module 1306 is used to determine the availability verification result information of the risk control strategy based on the business processing result information.

[0120] Optionally, the interception module 1302 is specifically used to intercept the target business request from the online business traffic by executing the aspect code of the preset business interception rule, wherein the aspect code is prepended to the business processing code, and the business processing code is used to process the target business request.

[0121] Optionally, the above device further includes:

[0122] A section code receiving module, used to receive the section code of the preset business interception rule sent by the first host computer;

[0123] The code injection module is used to inject the aspect code before the business processing code through a dynamic code injection tool.

[0124] Optionally, the aspect code includes a service parameter and a target interception quantity corresponding to the target service request;

[0125] The interception module 1302 is specifically used to determine whether the value of the counter has returned to zero, wherein the initial value of the counter is equal to the target interception quantity; if it has not returned to zero, intercept the target business request from the online business traffic according to the business parameters; if it has returned to zero, stop intercepting the target business request.

[0126] Optionally, the above device further includes:

[0127] The counting module is used to reduce the value of the counter by one every time verification completion information is detected until the value of the counter returns to zero, wherein the verification completion information is used to indicate that a target business request has completed business processing in accordance with the risk control strategy to be verified.

[0128] Optionally, the above device further includes:

[0129] An identification adding module, used to add an interception success identification in the call chain log corresponding to the target business request;

[0130] Other request processing modules, used for processing other service requests in the online service traffic to which the interception success mark is not added, using the original service processing strategy corresponding to the other service requests for service processing;

[0131] A designated request processing trigger module is used to trigger the step of calling the risk control strategy to be verified to perform business processing on a designated number of target business requests to which the interception success identifier has been added in the online business traffic.

[0132] Optionally, the business processing module 1304 is specifically used to detect whether the risk control strategy to be verified has been deployed; if not, the original business processing strategy corresponding to the target business request is used to perform business processing; if it has been deployed, a specified number of the target business requests are processed according to the risk control strategy to be verified.

[0133] Optionally, the above device further includes:

[0134] A change information receiving module, used for receiving the business processing strategy change information sent by the second host computer;

[0135] A policy change module, configured to change the original business processing policy corresponding to the target business request according to the business processing policy change information, and obtain a deployed risk control policy to be verified;

[0136] The policy restoration module is used to restore the risk control policy to the original business processing policy after calling the risk control policy to be verified to perform business processing on a specified number of the target business requests.

[0137] Optionally, the target node server belongs to any business processing server in a distributed server cluster;

[0138] The change information receiving module is specifically used to receive the business processing strategy change information sent by the second host computer through the distributed configuration management system DRM.

[0139] Optionally, the above device further includes:

[0140] A risk control code receiving module, used to receive the risk control business processing code sent by the second host computer;

[0141] A risk control strategy deployment module is used to locally deploy a risk control strategy to be verified according to the risk control business processing code, wherein the risk control strategy is in parallel with the original business processing strategy corresponding to the target business request.

[0142] Optionally, the availability verification module 1306 is specifically configured to determine that the risk control strategy is available if the business processing result information indicates that the business processing result of the target business request is consistent with the expected execution result of the risk control strategy.

[0143] Optionally, the specified number of target service requests is one target service request.

[0144] The risk control strategy verification device based on the online environment in one or more embodiments of the present specification is configured by setting an interception module, a business processing module and an availability verification module connected in sequence, wherein the interception module is used to intercept the target business request from the online business traffic according to the preset business interception rule; the business processing module is used to call the risk control strategy to be verified to perform business processing on a specified number of the target business requests to obtain business processing result information; the availability verification module is used to determine the availability verification result information of the risk control strategy according to the business processing result information. Thus, the specified number of target business requests can be intercepted from the online business traffic as a whole to verify the availability of the risk control strategy, and the impact scope of the verification is limited to the specified number of target business requests. Compared with the existing method, it can effectively reduce the impact scope of the online verification of the risk control strategy and reduce the adverse effects caused by the failure of the availability of the risk control strategy to meet expectations.

[0145] It should be noted that the embodiment of the risk control strategy verification device based on the online environment in this specification and the embodiment of the risk control strategy verification method based on the online environment in this specification are based on the same inventive concept. Therefore, the specific implementation of this embodiment can refer to the aforementioned corresponding implementation of the risk control strategy verification method based on the online environment, and the repeated parts will not be repeated.

[0146] Furthermore, corresponding to the above Figures 3 to 11 Based on the same technical concept, one or more embodiments of this specification also provide a risk control strategy verification system based on an online environment, which can be used to execute the above-mentioned risk control strategy verification method based on an online environment. Please refer to Figure 1 As shown, the system includes: a first host computer, a second host computer and a target node server;

[0147] Wherein, the first host computer and the second host computer are both connected to the target node server;

[0148] The first host computer is used to send a slice code of a preset business interception rule to the target node server;

[0149] The second host computer is used to send information related to the policy to be verified to the target node server; the information related to the policy to be verified includes business processing policy change information or risk control business processing code;

[0150] The target node server is used to locally deploy the preset business interception rules according to the aspect code, and to locally deploy the risk control strategy to be verified according to the relevant information of the strategy to be verified; and to intercept the target business request from the online business traffic according to the preset business interception rules, call the risk control strategy to be verified to perform business processing on a specified number of the target business requests, obtain business processing result information, and determine the availability verification result information of the risk control strategy according to the business processing result information.

[0151] Optionally, the target node server is specifically used to intercept target business requests from online business traffic by executing aspect codes of preset business interception rules, wherein the aspect codes are prepended to business processing codes, and the business processing codes are used to process the target business requests.

[0152] Optionally, the target node server is further used to receive the aspect code of the preset business interception rule sent by the first host computer; and inject the aspect code into the front of the business processing code through a dynamic code injection tool.

[0153] Optionally, the aspect code includes business parameters and a target interception number corresponding to the target business request; the target node server is specifically used to determine whether the value of the counter has returned to zero, wherein the initial value of the counter is equal to the target interception number; if it has not returned to zero, intercepting the target business request from the online business traffic according to the business parameters; if it has returned to zero, stopping intercepting the target business request.

[0154] Optionally, the target node server is also used to decrement the value of the counter by one each time verification completion information is detected until the value of the counter returns to zero, wherein the verification completion information is used to indicate that a target business request has completed business processing in accordance with the risk control policy to be verified.

[0155] Optionally, the target node server is also used to add an interception success mark in the call chain log corresponding to the target business request; for other business requests in the online business traffic to which the interception success mark is not added, the original business processing strategy corresponding to the other business requests is used to perform business processing; for the target business request in the online business traffic to which the interception success mark is added, trigger the execution of the step of calling the risk control strategy to be verified to perform business processing on a specified number of the target business requests.

[0156] Optionally, the target node server is specifically used to detect whether the risk control strategy to be verified has been deployed; if not, the original business processing strategy corresponding to the target business request is used to perform business processing; if it has been deployed, a specified number of the target business requests are processed according to the risk control strategy to be verified.

[0157] Optionally, the target node server is also used to receive business processing policy change information sent by the second host computer; according to the business processing policy change information, the original business processing policy corresponding to the target business request is changed to obtain a deployed risk control policy to be verified; after calling the risk control policy to be verified to perform business processing on a specified number of the target business requests, it also includes: restoring the risk control policy to the original business processing policy.

[0158] Optionally, the target node server belongs to any business processing server in a distributed server cluster; the target node server is specifically used to receive business processing policy change information sent by the second host computer through the distributed configuration management system DRM.

[0159] Optionally, the target node server is also used to receive the risk control business processing code sent by the second host computer; and locally deploy the risk control strategy to be verified according to the risk control business processing code, wherein the risk control strategy is parallel to the original business processing strategy corresponding to the target business request.

[0160] Optionally, the target node server is specifically configured to determine that the risk control strategy is available if the business processing result information indicates that a business processing result of the target business request is consistent with an expected execution result of the risk control strategy.

[0161] Optionally, the specified number of target service requests is one target service request.

[0162] The risk control strategy verification system based on the online environment in one or more embodiments of this specification intercepts the target business request from the online business traffic according to the preset business interception rules, and then calls the risk control strategy to be verified to perform business processing on a specified number of the target business requests to obtain business processing result information, and then determines the availability verification result information of the risk control strategy based on the business processing result information. It can be seen that through the risk control strategy verification system based on the online environment in one or more embodiments of this specification, it is possible to intercept a specified number of target business requests from the online business traffic to verify the availability of the risk control strategy, and the impact scope of the verification is limited to the specified number of target business requests. Compared with the existing methods, it can effectively reduce the impact scope of the online verification of the risk control strategy and reduce the adverse effects caused by the failure of the availability of the risk control strategy to meet expectations.

[0163] It should be noted that the embodiment of the risk control strategy verification system based on the online environment in this specification and the embodiment of the risk control strategy verification method based on the online environment in this specification are based on the same inventive concept. Therefore, the specific implementation of this embodiment can refer to the aforementioned corresponding implementation of the risk control strategy verification method based on the online environment, and the repeated parts will not be repeated.

[0164] Furthermore, corresponding to the above Figures 3 to 11 Based on the same technical concept, one or more embodiments of this specification also provide a risk control strategy verification device based on an online environment, which is used to execute the above-mentioned risk control strategy verification method based on an online environment, such as Fig.14 shown.

[0165] The risk control strategy verification device based on the online environment may have relatively large differences due to different configurations or performances, and may include one or more processors 1401 and memory 1402, and the memory 1402 may store one or more storage applications or data. Among them, the memory 1402 may be a short-term storage or a persistent storage. The application stored in the memory 1402 may include one or more modules (not shown in the figure), and each module may include a series of computer executable instructions in the risk control strategy verification device based on the online environment. Furthermore, the processor 1401 may be configured to communicate with the memory 1402, and execute a series of computer executable instructions in the memory 1402 on the risk control strategy verification device based on the online environment. The risk control strategy verification device based on the online environment may also include one or more power supplies 1403, one or more wired or wireless network interfaces 1404, one or more input and output interfaces 1405, one or more keyboards 1406, etc.

[0166] In a specific embodiment, the risk control strategy verification device based on the online environment includes a memory and one or more programs, wherein the one or more programs are stored in the memory, and the one or more programs may include one or more modules, and each module may include a series of computer executable instructions in the risk control strategy verification device based on the online environment, and the one or more programs are configured to be executed by one or more processors, including the following computer executable instructions:

[0167] According to preset business interception rules, target business requests are intercepted from online business traffic; the risk control strategy to be verified is called to perform business processing on a specified number of the target business requests to obtain business processing result information; based on the business processing result information, the availability verification result information of the risk control strategy is determined.

[0168] Optionally, when the computer executable instructions are executed, the target business request is intercepted from the online business traffic according to the preset business interception rules, including: intercepting the target business request from the online business traffic by executing the aspect code of the preset business interception rules, wherein the aspect code is prepended to the business processing code, and the business processing code is used to process the target business request.

[0169] Optionally, when the computer executable instructions are executed, before the aspect code that executes the preset business interception rules intercepts the target business request from the online business traffic, it also includes: receiving the aspect code of the preset business interception rules sent by the first host computer; injecting the aspect code before the business processing code through a dynamic code injection tool.

[0170] Optionally, when the computer executable instructions are executed, the aspect code includes business parameters and a target interception number corresponding to the target business request; the aspect code intercepts the target business request from the online business traffic by executing the preset business interception rules, including: determining whether the value of the counter has returned to zero, wherein the initial value of the counter is equal to the target interception number; if it has not returned to zero, intercepting the target business request from the online business traffic according to the business parameters; if it has returned to zero, stopping intercepting the target business request.

[0171] Optionally, when the computer executable instructions are executed, they also include the following computer executable instructions: each time verification completion information is detected, the value of the counter is decremented by one until the value of the counter returns to zero, wherein the verification completion information is used to indicate that a target business request has completed business processing in accordance with the risk control policy to be verified.

[0172] Optionally, when the computer executable instructions are executed, before the risk control policy to be verified is called to perform business processing on a specified number of the target business requests, it also includes: adding an interception success mark in the call chain log corresponding to the target business request; for other business requests in the online business traffic to which the interception success mark is not added, using the original business processing strategy corresponding to the other business requests to perform business processing; for the target business request in the online business traffic to which the interception success mark has been added, triggering the step of executing the call to the risk control policy to be verified to perform business processing on a specified number of the target business requests.

[0173] Optionally, when the computer executable instructions are executed, the risk control strategy to be verified is called to perform business processing on a specified number of the target business requests, including: detecting whether the risk control strategy to be verified has been deployed; if not, using the original business processing strategy corresponding to the target business request to perform business processing; if it has been deployed, performing business processing on the specified number of the target business requests according to the risk control strategy to be verified.

[0174] Optionally, when the computer executable instructions are executed, before the risk control policy to be verified is called to perform business processing on a specified number of the target business requests, it also includes: receiving business processing policy change information sent by a second host computer; according to the business processing policy change information, changing the original business processing policy corresponding to the target business request to obtain a deployed risk control policy to be verified; after the risk control policy to be verified is called to perform business processing on a specified number of the target business requests, it also includes: restoring the risk control policy to the original business processing policy.

[0175] Optionally, when the computer executable instructions are executed, the target node server belongs to any business processing server in the distributed server cluster; the receiving of business processing policy change information sent by the second host computer includes: receiving business processing policy change information sent by the second host computer through the distributed configuration management system DRM.

[0176] Optionally, when the computer executable instructions are executed, before calling the risk control strategy to be verified to perform business processing on a specified number of the target business requests, it also includes: receiving a risk control business processing code sent by a second host computer; locally deploying the risk control strategy to be verified according to the risk control business processing code, wherein the risk control strategy is parallel to the original business processing strategy corresponding to the target business request.

[0177] Optionally, when the computer executable instructions are executed, the availability verification result information of the risk control strategy is determined based on the business processing result information, including: if the business processing result information represents that the business processing result of the target business request is consistent with the expected execution result of the risk control strategy, then it is determined that the risk control strategy is available.

[0178] Optionally, when the computer executable instruction is executed, the specified number of target service requests is one target service request.

[0179] The risk control strategy verification device based on the online environment in one or more embodiments of this specification intercepts the target business request from the online business traffic according to the preset business interception rules, and then calls the risk control strategy to be verified to perform business processing on a specified number of the target business requests to obtain business processing result information, and then determines the availability verification result information of the risk control strategy based on the business processing result information. It can be seen that through the risk control strategy verification device based on the online environment in one or more embodiments of this specification, it is possible to intercept a specified number of target business requests from the online business traffic to verify the availability of the risk control strategy, and the impact scope of the verification is limited to the specified number of target business requests. Compared with the existing methods, it can effectively reduce the impact scope of the online verification of the risk control strategy and reduce the adverse effects caused by the failure of the availability of the risk control strategy to meet expectations.

[0180] It should be noted that the embodiment of the risk control strategy verification device based on the online environment in this specification and the embodiment of the risk control strategy verification method based on the online environment in this specification are based on the same inventive concept. Therefore, the specific implementation of this embodiment can refer to the aforementioned corresponding implementation of the risk control strategy verification method based on the online environment, and the repeated parts will not be repeated.

[0181] Furthermore, corresponding to the above Figures 3 to 11 The method shown is based on the same technical concept. One or more embodiments of this specification also provide a storage medium for storing computer executable instructions. In a specific embodiment, the storage medium can be a USB flash drive, an optical disk, a hard disk, etc. When the computer executable instructions stored in the storage medium are executed by the processor, the following process can be implemented:

[0182] According to preset business interception rules, target business requests are intercepted from online business traffic; the risk control strategy to be verified is called to perform business processing on a specified number of the target business requests to obtain business processing result information; based on the business processing result information, the availability verification result information of the risk control strategy is determined.

[0183] Optionally, when the computer executable instructions stored in the storage medium are executed by the processor, the target business request is intercepted from the online business traffic according to the preset business interception rules, including: intercepting the target business request from the online business traffic by executing the aspect code of the preset business interception rules, wherein the aspect code is prepended to the business processing code, and the business processing code is used to process the target business request.

[0184] Optionally, when the computer executable instructions stored in the storage medium are executed by the processor, before intercepting the target business request from the online business traffic by executing the aspect code of the preset business interception rule, it also includes: receiving the aspect code of the preset business interception rule sent by the first host computer; injecting the aspect code before the business processing code through a dynamic code injection tool.

[0185] Optionally, when the computer executable instructions stored in the storage medium are executed by the processor, the aspect code includes business parameters and a target interception number corresponding to the target business request; the aspect code intercepts the target business request from the online business traffic by executing the preset business interception rule, including: determining whether the value of the counter has returned to zero, wherein the initial value of the counter is equal to the target interception number; if it has not returned to zero, intercepting the target business request from the online business traffic according to the business parameters; if it has returned to zero, stopping intercepting the target business request.

[0186] Optionally, the computer executable instructions stored in the storage medium, when executed by the processor, also implement the following process: each time verification completion information is detected, the value of the counter is decremented by one until the value of the counter returns to zero, wherein the verification completion information is used to indicate that a target business request has completed business processing in accordance with the risk control policy to be verified.

[0187] Optionally, when the computer executable instructions stored in the storage medium are executed by the processor, before the risk control policy to be verified is called to perform business processing on a specified number of the target business requests, the instructions also include: adding an interception success mark in the call chain log corresponding to the target business request; for other business requests in the online business traffic to which the interception success mark is not added, using the original business processing strategy corresponding to the other business requests to perform business processing; for the target business request in the online business traffic to which the interception success mark has been added, triggering the step of executing the call to the risk control policy to be verified to perform business processing on a specified number of the target business requests.

[0188] Optionally, when the computer executable instructions stored in the storage medium are executed by the processor, the risk control strategy to be verified is called to perform business processing on a specified number of the target business requests, including: detecting whether the risk control strategy to be verified has been deployed; if not, using the original business processing strategy corresponding to the target business request to perform business processing; if it has been deployed, performing business processing on the specified number of the target business requests according to the risk control strategy to be verified.

[0189] Optionally, when the computer executable instructions stored in the storage medium are executed by the processor, before the risk control policy to be verified is called to perform business processing on a specified number of the target business requests, the instructions also include: receiving business processing policy change information sent by a second host computer; according to the business processing policy change information, changing the original business processing policy corresponding to the target business request to obtain a deployed risk control policy to be verified; after the risk control policy to be verified is called to perform business processing on a specified number of the target business requests, the instructions also include: restoring the risk control policy to the original business processing policy.

[0190] Optionally, when the computer executable instructions stored in the storage medium are executed by the processor, the target node server belongs to any business processing server in the distributed server cluster; the receiving of business processing policy change information sent by the second host computer includes: receiving business processing policy change information sent by the second host computer through the distributed configuration management system DRM.

[0191] Optionally, when the computer executable instructions stored in the storage medium are executed by the processor, before calling the risk control strategy to be verified to perform business processing on a specified number of the target business requests, it also includes: receiving a risk control business processing code sent by a second host computer; locally deploying the risk control strategy to be verified according to the risk control business processing code, wherein the risk control strategy is parallel to the original business processing strategy corresponding to the target business request.

[0192] Optionally, when the computer executable instructions stored in the storage medium are executed by the processor, the availability verification result information of the risk control strategy is determined based on the business processing result information, including: if the business processing result information represents that the business processing result of the target business request is consistent with the expected execution result of the risk control strategy, then it is determined that the risk control strategy is available.

[0193] Optionally, when the computer executable instructions stored in the storage medium are executed by the processor, the specified number of target service requests is one target service request.

[0194] When the computer executable instructions stored in the storage medium in one or more embodiments of this specification are executed by the processor, the target business request is intercepted from the online business traffic according to the preset business interception rules, and then the risk control strategy to be verified is called to perform business processing on a specified number of the target business requests to obtain business processing result information, and then the availability verification result information of the risk control strategy is determined based on the business processing result information. It can be seen that through the storage medium in one or more embodiments of this specification, a specified number of target business requests can be intercepted from the online business traffic to verify the availability of the risk control strategy, and the impact scope of the verification is limited to the specified number of target business requests. Compared with the existing method, it can effectively reduce the impact scope of the online verification of the risk control strategy and reduce the adverse effects caused by the failure of the availability of the risk control strategy to meet expectations.

[0195] It should be noted that the embodiment of the storage medium in this specification and the embodiment of the risk control strategy verification method based on the online environment in this specification are based on the same inventive concept. Therefore, the specific implementation of this embodiment can refer to the aforementioned corresponding implementation of the risk control strategy verification method based on the online environment, and the repeated parts will not be repeated.

[0196] The above is a description of a specific embodiment of the specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be performed in an order different from that in the embodiments and still achieve the desired results. In addition, the processes depicted in the drawings do not necessarily require the specific order or continuous order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0197] In the 1990s, improvements to a technology could be clearly distinguished as hardware improvements (for example, improvements to the circuit structure of diodes, transistors, switches, etc.) or software improvements (improvements to the method flow). However, with the development of technology, many improvements to the method flow today can be regarded as direct improvements to the hardware circuit structure. Designers almost always obtain the corresponding hardware circuit structure by programming the improved method flow into the hardware circuit. Therefore, it cannot be said that an improvement in a method flow cannot be implemented using a hardware entity module. For example, a programmable logic device (PLD) (such as a field programmable gate array (FPGA)) is such an integrated circuit whose logical function is determined by the user's programming of the device. Designers can "integrate" a digital system on a PLD by programming it themselves, without having to ask a chip manufacturer to design and produce a dedicated integrated circuit chip. Moreover, nowadays, instead of manually making integrated circuit chips, this kind of programming is mostly implemented by "logic compiler" software, which is similar to the software compiler used when developing and writing programs. The original code before compilation must also be written in a specific programming language, which is called hardware description language (HDL). There is not only one HDL, but many kinds, such as ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HD Cal, JHDL (Java Hardware Description Language), Lava, Lola, My HDL, PALASM, RHDL (Ruby Hardware Description Language), etc. The most commonly used ones are VHDL (Very-High-Speed ​​Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art should also know that it is only necessary to program the method flow slightly in the above-mentioned hardware description languages ​​and program it into the integrated circuit, and then it is easy to obtain the hardware circuit that implements the logic method flow.

[0198] The controller can be implemented in any appropriate manner, for example, the controller can take the form of a microprocessor or processor and a computer-readable medium storing a computer-readable program code (such as software or firmware) that can be executed by the (micro)processor, a logic gate, a switch, an application-specific integrated circuit (ASIC), a programmable logic controller, and an embedded microcontroller. Examples of controllers include, but are not limited to, the following microcontrollers: ARC625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320. The memory controller can also be implemented as part of the control logic of the memory. Those skilled in the art also know that in addition to implementing the controller in a purely computer-readable program code manner, the controller can be implemented in the form of a logic gate, a switch, an application-specific integrated circuit, a programmable logic controller, and an embedded microcontroller by logically programming the method steps. Therefore, this controller can be considered as a hardware component, and the devices included therein for implementing various functions can also be regarded as structures within the hardware component. Or even, the devices for implementing various functions can be regarded as both software modules for implementing the method and structures within the hardware component.

[0199] The systems, devices, modules or units described in the above embodiments may be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, the computer may be, for example, a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.

[0200] For the convenience of description, the above devices are described in various units according to their functions. Of course, when implementing one or more of the present specification, the functions of each unit can be implemented in the same or more software and / or hardware.

[0201] It will be appreciated by those skilled in the art that one or more embodiments of this specification may be provided as methods, systems, or computer program products. Therefore, one or more of this specification may be in the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, one or more of this specification may be in the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0202] One or more of the present specification is described with reference to flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to one or more embodiments of the present specification. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0203] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0204] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 A step that specifies a function in one or more boxes.

[0205] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0206] The memory may include non-permanent storage in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. The memory is an example of a computer-readable medium.

[0207] Computer readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.

[0208] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.

[0209] It should be understood by those skilled in the art that one or more embodiments of this specification may be provided as methods, systems or computer program products. Therefore, one or more of this specification may take the form of a complete hardware embodiment, a complete software embodiment or an embodiment combining software and hardware. Moreover, one or more of this specification may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0210] One or more of the present descriptions may be described in the general context of computer-executable instructions executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types. One or more of the present descriptions may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are connected through a communications network. In a distributed computing environment, program modules may be located in local and remote computer storage media, including storage devices.

[0211] Each embodiment in this specification is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the system embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

[0212] The above description is only one or more embodiments of this specification and is not intended to limit this specification. For those skilled in the art, this specification may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of this specification should be included in the scope of one or more claims of this specification.

Claims

1. A risk control strategy verification method based on an online environment, applied to a target node server, comprising: According to the preset business interception rule, the target business request is intercepted from the online business traffic, wherein the preset business interception rule is deployed before the business processing code in the form of a section code, the business processing code is used to process the target business request, and the preset business interception rule is set according to the needs of risk control, and is used to identify and intercept the target business request from the online business traffic; the online business traffic is the traffic in the online environment corresponding to the target business; Calling the risk control strategy to be verified to perform business processing on a specified number of the target business requests to obtain business processing result information, wherein the risk control strategy is used to deal with the risks existing in the server cluster to which the target node server belongs; According to the business processing result information, availability verification result information of the risk control strategy is determined.

2. The method according to claim 1, wherein: The intercepting of the target service request from the online service traffic according to the preset service interception rule includes: By executing the aspect code of the preset business interception rule, the target business request is intercepted from the online business traffic, wherein the aspect code is placed before the business processing code, and the business processing code is used to process the target business request.

3. The method according to claim 2, wherein: Before intercepting the target business request from the online business traffic by executing the slice code of the preset business interception rule, the method further includes: Receive the slice code of the preset business interception rule sent by the first host computer; The aspect code is injected before the business processing code through a dynamic code injection tool.

4. The method according to claim 2, wherein: The aspect code includes a service parameter corresponding to the target service request and a target interception quantity; The target business request is intercepted from the online business traffic by executing the slice code of the preset business interception rule, including: Determining whether the value of the counter has been reset to zero, wherein the initial value of the counter is equal to the number of target interceptions; If it is not reset to zero, intercepting the target service request from the online service traffic according to the service parameters; If it has returned to zero, stop intercepting the target service request.

5. The method according to claim 4, wherein: The method further comprises: Each time verification completion information is detected, the value of the counter is decremented by one until the value of the counter returns to zero, wherein the verification completion information is used to indicate that a target business request has completed business processing according to the risk control policy to be verified.

6. The method according to claim 1, wherein: Before calling the risk control strategy to be verified to perform business processing on a specified number of the target business requests, the method further includes: Add an interception success mark in the call chain log corresponding to the target business request; For other service requests in the online service traffic to which the interception success mark is not added, the original service processing strategy corresponding to the other service requests is used to perform service processing; For the target business request to which the interception success mark has been added in the online business traffic, trigger the step of calling the risk control strategy to be verified to perform business processing on a specified number of the target business requests.

7. The method according to claim 1, wherein: The calling of the risk control strategy to be verified to perform business processing on a specified number of the target business requests includes: Check whether the risk control strategy to be verified has been deployed; If the deployment is not completed, the original business processing strategy corresponding to the target business request is used to perform business processing; If the deployment is complete, business processing is performed on a specified number of the target business requests according to the risk control strategy to be verified.

8. The method according to claim 1, wherein: Before calling the risk control strategy to be verified to perform business processing on a specified number of the target business requests, the method further includes: Receiving business processing strategy change information sent by the second host computer; According to the business processing strategy change information, the original business processing strategy corresponding to the target business request is changed to obtain a deployed risk control strategy to be verified; After the risk control strategy to be verified is called to perform business processing on a specified number of the target business requests, the method further includes: The risk control strategy is restored to the original business processing strategy.

9. The method according to claim 8, wherein: The target node server belongs to any business processing server in the distributed server cluster; The receiving of the service processing strategy change information sent by the second host computer includes: Receive the business processing policy change information sent by the second host computer through the distributed configuration management system DRM.

10. The method according to claim 1, wherein: Before calling the risk control strategy to be verified to perform business processing on a specified number of the target business requests, the method further includes: Receive the risk control business processing code sent by the second host computer; A risk control strategy to be verified is deployed locally according to the risk control business processing code, wherein the risk control strategy is parallel to an original business processing strategy corresponding to the target business request.

11. The method according to claim 1, wherein: The determining, according to the business processing result information, the availability verification result information of the risk control strategy includes: If the business processing result information indicates that the business processing result of the target business request is consistent with the expected execution result of the risk control strategy, it is determined that the risk control strategy is available.

12. The method according to any one of claims 1 to 11, wherein: The specified number of target service requests is one target service request.

13. A risk control strategy verification device based on an online environment, applied to a target node server, comprising: An interception module, which intercepts a target business request from online business traffic according to a preset business interception rule, wherein the preset business interception rule is deployed before the business processing code in the form of a section code, the business processing code is used to process the target business request, and the preset business interception rule is set according to the needs of risk control, and is used to identify and intercept the target business request from the online business traffic; the online business traffic is the traffic in the online environment corresponding to the target business; A business processing module, which calls the risk control strategy to be verified to perform business processing on a specified number of the target business requests to obtain business processing result information, wherein the risk control strategy is used to deal with the risks existing in the server cluster to which the target node server belongs; An availability verification module determines availability verification result information of the risk control strategy according to the business processing result information.

14. A risk control strategy verification system based on an online environment, comprising: A first host computer, a second host computer and a target node server; The first host computer is used to send a slice code of a preset business interception rule to the target node server; The second host computer is used to send information related to the policy to be verified to the target node server; The information related to the policy to be verified includes business processing policy change information or risk control business processing code; The target node server is used to locally deploy the preset business interception rule according to the aspect code, and to locally deploy the risk control policy to be verified according to the relevant information of the policy to be verified; and according to the preset business interception rule, intercepting the target business request from the online business traffic, calling the risk control strategy to be verified to perform business processing on a specified number of the target business requests, obtaining business processing result information, and determining the availability verification result information of the risk control strategy according to the business processing result information, wherein the preset business interception rule is deployed before the business processing code in the form of a section code, the business processing code is used to process the target business request, and the preset business interception rule is set according to the need of the risk control, and is used to identify and intercept the target business request from the online business traffic; The risk control strategy is also used to deal with risks existing in the server cluster to which the target node server belongs; the online business traffic is the traffic in the online environment corresponding to the target business.

15. A risk control strategy verification device based on an online environment, comprising: A processor and a memory electrically connected to the processor, the memory storing a computer program, the processor being used to call and execute the computer program from the memory to implement a risk control strategy verification method based on an online environment as described in any one of claims 1 to 12.

16. A computer-readable storage medium, wherein the storage medium is used to store a computer program, wherein the computer program can be executed by a processor to implement a risk control strategy verification method based on an online environment as described in any one of claims 1 to 12.

Images