A method, device and equipment for designing a risk control strategy

Abstract

The embodiment of the specification discloses a design method, device and equipment for risk control strategy arrangement. The scheme comprises the following steps: receiving a graphical arrangement operation on a risk control strategy through a canvas page of a front end to obtain risk control strategy canvas content; converting the risk control strategy canvas content into serialized data and transmitting the serialized data to a back end; receiving and converting the serialized data through the back end according to a business object defined in advance based on a standard graphical annotation irrelevant to a programming language to obtain a risk control strategy business object; converting the risk control strategy business object into a risk control strategy text according to a text format specified by the standard graphical annotation to perform a legality check; and if the legality check passes, storing the risk control strategy text in a database to wait for loading and execution.

Description

Technical Field

[0001] This specification relates to the field of security technology, and in particular to a design method, apparatus and equipment for risk control strategy orchestration. Background Technology

[0002] With the development of internet technology and the widespread use of mobile terminals, most businesses can be conducted online based on mobile applications, which brings convenience to users. However, it also makes online risks more likely to occur. Therefore, risk control (i.e., risk management) on applications is receiving increasing attention.

[0003] For some large and medium-sized applications or companies, a dedicated risk control engine is provided to orchestrate and execute risk control strategies. However, the current storage format of the orchestrated risk control strategies can only be applied to specific platforms. The storage format depends on the underlying implementation of the corresponding platform. Moreover, for the multiple types of relationships involved in the risk control strategy, a large number of related records must be stored separately for each type of relationship according to the database table structure design. This is not only cumbersome and time-consuming to store, maintain, and update, but also puts a lot of pressure on storage. In addition, since this storage format can only be applied to specific platforms, it cannot be migrated to other heterogeneous platforms and lacks universality and portability.

[0004] Therefore, a better solution for using risk control strategies is needed. Summary of the Invention

[0005] This specification provides one or more embodiments of a risk control strategy orchestration design method, apparatus, device, and storage medium to solve the following technical problem: the need for a better solution for using risk control strategies.

[0006] To solve the above-mentioned technical problems, one or more embodiments of this specification are implemented as follows: This specification provides a design method for orchestrating risk control strategies through one or more embodiments, including: The risk control strategy can be graphically arranged through the front-end canvas page to obtain the content of the risk control strategy canvas. The content of the risk control strategy canvas is converted into serialized data and transmitted to the backend; Through the backend, the serialized data is received and converted according to the business object predefined based on standard graphical annotations independent of programming languages ​​to obtain the risk control strategy business object; Based on the text format specified in the standard graphical annotation, the risk control strategy business object is converted into risk control strategy text for legality checking. If the legality check passes, the risk control strategy text is stored in the database to await loading and execution.

[0007] This specification provides a design device for orchestrating risk control strategies, comprising one or more embodiments, including: The canvas arrangement module receives graphical arrangement operations for risk control strategies through the front-end canvas page and obtains the content of the risk control strategy canvas. The serialization processing module converts the content of the risk control strategy canvas into serialized data and transmits it to the backend; The business object processing module receives and transforms the serialized data through the backend, based on business objects predefined using standard graphical annotations independent of programming languages, to obtain risk control strategy business objects. The strategy text checking module converts the risk control strategy business object into risk control strategy text according to the text format specified by the standard graphic annotation, so as to check its legality. If the legality check passes, the strategy text storage module stores the risk control strategy text in the database for loading and execution.

[0008] This specification provides a design device for risk control strategy orchestration through one or more embodiments, comprising: At least one processor; and, A memory communicatively connected to the at least one processor; wherein, The memory stores instructions executable by the at least one processor, which, when executed by the at least one processor, enable the at least one processor to: The risk control strategy can be graphically arranged through the front-end canvas page to obtain the content of the risk control strategy canvas. The content of the risk control strategy canvas is converted into serialized data and transmitted to the backend; Through the backend, the serialized data is received and converted according to the business object predefined based on standard graphical annotations independent of programming languages ​​to obtain the risk control strategy business object; Based on the text format specified in the standard graphical annotation, the risk control strategy business object is converted into risk control strategy text for legality checking. If the legality check passes, the risk control strategy text is stored in the database to await loading and execution.

[0009] This specification provides one or more embodiments of a non-volatile computer storage medium storing computer-executable instructions, wherein the computer-executable instructions are configured as follows: The risk control strategy can be graphically arranged through the front-end canvas page to obtain the content of the risk control strategy canvas. The content of the risk control strategy canvas is converted into serialized data and transmitted to the backend; Through the backend, the serialized data is received and converted according to the business object predefined based on standard graphical annotations independent of programming languages ​​to obtain the risk control strategy business object; Based on the text format specified in the standard graphical annotation, the risk control strategy business object is converted into risk control strategy text for legality checking. If the legality check passes, the risk control strategy text is stored in the database to await loading and execution.

[0010] The above-mentioned at least one technical solution adopted in one or more embodiments of this specification can achieve the following beneficial effects: Based on standard graphical annotations independent of programming languages, risk control strategies are arranged and formatted to obtain standardized business objects that can adapt to different platforms and systems, without relying on specific implementations, thus improving reusability and flexibility; Based on the legal risk control strategy text corresponding to the business objects (e.g., XML text conforming to the standard graphical annotation) stored in the database, it is no longer necessary to classify and store a large number of relationships, but can be stored and used using only one field, which can be completed in a single database IO process, and the business logic code is also more concise and easier to maintain, effectively reducing costs. Attached Figure Description

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

[0012] Figure 1 A flowchart illustrating a design method for orchestrating risk control strategies provided in one or more embodiments of this specification; Figure 2 A schematic diagram of element relationships for a standard graphic annotation provided in one or more embodiments of this specification; Figure 3 In one practical application scenario provided by one or more embodiments of this specification, Figure 1 A schematic diagram of the risk control strategy orchestration and storage process involved in the process; Figure 4 In one practical application scenario provided by one or more embodiments of this specification, Figure 1 The process involves a schematic diagram of the risk control strategy loading and execution flow. Figure 5 A comparative diagram illustrating the effect of the decision computing engine provided in one or more embodiments of this specification on connecting to multiple business platforms; Figure 6 A comparative diagram illustrating the effects of database strategy storage structures provided in one or more embodiments of this specification; Figure 7 A schematic diagram of a design device for orchestrating risk control strategies provided in one or more embodiments of this specification; Figure 8 This is a structural schematic diagram of a risk control strategy orchestration design device provided for one or more embodiments of this specification. Detailed Implementation

[0013] This specification provides a design method, apparatus, device, and storage medium for risk control strategy orchestration.

[0014] To enable those skilled in the art to better understand the technical solutions in this specification, the technical solutions in the embodiments of this specification will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this specification, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of this application.

[0015] The problems described in the background technology exist not only across different platforms within different companies, but also within the same company. A crucial component of a risk control engine is the decision computing engine, which is responsible for interfacing with risk control strategies from different business stakeholders. It performs calculations on the rules and variables involved in these strategies, then outputs the results to the caller after a decision merging logic. Within a single company, the decision computing engine also needs to interface with multiple internal product lines. Each system within these product lines often implements its own strategy orchestration mechanism, lacking a unified and standardized specification. Consequently, the underlying storage formats differ, impacting the company's overall product development and operational efficiency.

[0016] To address the problems in the background technology, this paper proposes a universal format for orchestrating risk control strategies. This format is applicable to different heterogeneous systems, is platform-independent, has a simple and easily updated storage format, and reduces the storage pressure on the underlying database. A detailed explanation follows.

[0017] Figure 1This document presents a flowchart illustrating a risk control strategy orchestration design method provided in one or more embodiments. This method can be applied to various business domains, including electronic payment, e-commerce, social networking, gaming, and government services. The process can be executed on the platform's risk control-related equipment within these domains. Certain input parameters or intermediate results in the process can be manually adjusted to improve accuracy.

[0018] Figure 1 The process includes the following steps: S102: Receive graphical arrangement operations of risk control strategies through the front-end canvas page to obtain the content of the risk control strategy canvas.

[0019] In one or more embodiments of this specification, the risk control strategy is a decision process orchestrated based on decision nodes. From a viewpoint, it is a tree structure. Decision nodes are the basic units involved in the orchestration of risk control strategies. They are used to indicate which actions to perform when which rules are met (e.g., assigning parameter values, outputting message codes, etc.). Decision nodes can be directly included in the process or referenced by other nodes in the process. The latter approach is more flexible. For ease of description, some embodiments below will be described using the latter approach as an example.

[0020] Decision nodes are the arrangement of rules and actions, and can have various specific implementation types, such as rule nodes, rule set nodes, decision tree nodes, decision table nodes, and decision set nodes. Rule nodes and rule set nodes execute corresponding actions when a rule is met or not met. Decision tree nodes, with a tree structure, execute actions from the root node (which is also a condition of the rule) to the previous node (the leaf node is associated with an action). Decision table nodes, with a two-dimensional array structure, execute corresponding actions when the horizontal and vertical conditions are met. Decision set nodes, with a one-dimensional array, execute each row of the decision set sequentially, executing the corresponding action when a rule is met.

[0021] In one or more embodiments of this specification, the risk control strategy canvas content displayed on the canvas page is based on standard graphical annotations that are independent of programming languages. These standard graphical annotations are defined using a common markup language format, specifically defining various elements used to represent business processes. For example, the standard graphical annotations may include business process model annotations, in which case they may be defined using a common text format such as XML. Text formats themselves are not convenient for graphical arrangement and execution; therefore, business objects are defined based on these elements for arrangement and subsequent execution, while the corresponding text is used for storage.

[0022] S104: Convert the content of the risk control strategy canvas into serialized data and transmit it to the backend.

[0023] In one or more embodiments of this specification, the serialized data includes JSON format data, which is pre-adapted to the backend interface. Using the highly versatile JSON format as a bridge, the frontend does not need to fully understand the details of standard graphical annotations and their business objects. It only needs to support graphical operations and then hand over the risk control strategy canvas content as the substantive content of the risk control strategy to the backend. Further in-depth processing can then be conducted later. This facilitates easier and more unified integration with different platforms and internal product lines on the frontend, without imposing a learning burden on the other party.

[0024] S106: Through the backend, the serialized data is received and converted according to the business object predefined based on standard graphical annotations independent of programming languages ​​to obtain the risk control strategy business object.

[0025] In one or more embodiments of this specification, the substantive content of the risk control strategy derived from the serialized data is correspondingly filled into a predefined business object. The filled business object is temporarily stored in memory to facilitate the detection of whether there is valid strategy content. It should be noted that the business object here is a general term, which specifically includes various sub-objects, and the sub-objects may correspond to different elements contained in the standard graphical annotation.

[0026] Intuitively, taking a standard graphical annotation such as a business process model annotation as an example, one or more embodiments of this specification provide a schematic diagram of the element relationships of a standard graphical annotation, such as... Figure 2 As shown.

[0027] exist Figure 2 In the business process model annotation, there is a definition element as the root element that describes the entire strategy. The definition element contains process and view elements.

[0028] Process elements reflect the essential content of a strategy and are used to logically describe the arrangement of nodes and edges. The arrangement of a strategy is essentially the arrangement of the content contained in process elements. Process elements include service tasks, gateways, start nodes, end nodes, and sequence flows.

[0029] Service task elements, associated with decision nodes, represent the rules that actually need to be executed to perform the corresponding rule calculation tasks.

[0030] The gateway element represents a branching node in the process. It can connect an inbound sequential flow and several outbound sequential flows. Based on the condition of the sequential flows, it selects the first outbound sequential flow that is hit for execution.

[0031] The starting node element marks the beginning of a process. It cannot have inbound sequential flow, but can have several outbound sequential flow.

[0032] Terminating elements mark the end of a process. They cannot have outgoing sequential flows, but can have several ingoing sequential flows.

[0033] Sequential flow sub-elements are essentially edges, connecting source nodes (e.g., start node, ordinary node, gateway, etc.) and target nodes (e.g., end node, ordinary node, gateway, etc.). They can also carry the conditions for the gateway to choose which outgoing sequential flow.

[0034] View elements reflect how the strategy is displayed, showing the relationships between nodes, and specifically describing the position, size, and specifications of each node, gateway, and sequence flow on the canvas page. View elements include panels, styles, borders, shapes, and other elements.

[0035] Style elements define the specific style of logical elements (elements contained within process elements), such as describing the thickness, style, and size of lines.

[0036] Panel elements include border elements and shape elements. Border elements are used to describe the positions of source and target nodes in the sequential flow, while shape elements are used to describe the position, width, and height of nodes.

[0037] Each element can have its corresponding business object, and the inclusion relationship between business objects is consistent with the inclusion relationship between corresponding elements. It should be noted that, in addition to the business object corresponding to the standard graphical annotation, the risk control strategy business object can also include other content, such as tenant, version, status, and other attributes, which can be represented using metadata.

[0038] S108: Convert the risk control strategy business object into risk control strategy text according to the text format specified by the standard graphic annotation, so as to perform a legality check on it.

[0039] In one or more embodiments of this specification, the risk control strategy text is a direct representation of the risk control strategy using standard graphical annotations, which is also a suitable format for storage. Within the risk control strategy text, corresponding element tags (e.g., tags in XML) can be used to indicate which content in the text belongs to which of the aforementioned elements. The legality check here is mainly used to check whether the current risk control strategy content truly conforms to the requirements of the standard graphical annotations (e.g., whether the in-degree and out-degree of nodes meet expectations, whether a cycle is formed, the containment relationship between elements, the content format of elements, etc.). If it is invalid, the corresponding business object may also be incorrect, which will affect subsequent execution. Therefore, the risk control strategy text is stored only after its legality is confirmed.

[0040] S110: If the legality check passes, the risk control strategy text is stored in the database to await loading and execution.

[0041] In one or more embodiments of this specification, the risk control strategy text or its substantive content can be stored in a database using a single field, which can effectively reduce storage and query pressure. For example, subtext corresponding to process elements can be obtained from the risk control strategy text. This subtext is the substantive content, and it can be stored in the database using a single field so that subsequent decision calculations can be performed by querying this single field.

[0042] pass Figure 1 This method, based on standard graphical annotations independent of programming languages, orchestrates and formats risk control strategies, resulting in standardized business objects that can adapt to different platforms and systems, without relying on specific implementations, thus improving reusability and flexibility. By storing the corresponding legal risk control strategy text (e.g., XML text conforming to the standard graphical annotation) in the database, it eliminates the need to categorize and store numerous relationships; instead, storage and use can be achieved using only a single field, completed in a single database I / O operation. Furthermore, the business logic code is more concise and easier to maintain, effectively reducing costs.

[0043] based on Figure 1 In addition to the above methods, this manual also provides some specific implementation schemes and extension schemes of the method. For a more intuitive understanding, the following explanation will mainly focus on the merchant scenario.

[0044] In one or more embodiments of this specification, the process elements are further analyzed. In practical applications, the arrangement operations on the front-end canvas page may be performed manually by the user. Therefore, two problems may exist that affect subsequent execution. First, there may be missing elements, redundancies, or abnormal connections between elements; second, there may be a lack of valid execution conditions or execution actions.

[0045] The first problem can be identified and resolved during the legality check, while the second problem involves decision nodes. In practical applications, decision nodes may not be directly part of the risk control strategy business object; they may only be associated with certain objects within it, such as sub-objects corresponding to service task elements within the risk control strategy business object. In this case, legality checks may not be sufficient. Therefore, the existence and validity of decision nodes can be checked separately. Specifically, after obtaining the risk control strategy business object, before storing the risk control strategy text in the database, the sub-objects corresponding to service task elements within the risk control strategy business object can be retrieved. It can be determined whether the sub-objects of the service task elements are associated with valid decision nodes. Decision nodes at least indicate which rules are matched and corresponding actions should be executed; they can also specify the action content. If the result is positive, then consider storing the risk control strategy text. Otherwise, the current risk control strategy can be considered problematic and needs modification and adjustment.

[0046] Based on the above description, and for ease of understanding, one or more embodiments of this specification provide a practical application scenario. Figure 1 The process involves a schematic diagram of the risk control strategy orchestration and storage process, such as... Figure 3 As shown.

[0047] Figure 3 The process includes the following steps: (1) Business personnel edit risk control strategies on the front-end canvas page during management and complete the arrangement of strategies by dragging and dropping.

[0048] (2) The front-end code converts the corresponding strategy on the canvas, i.e. the content of the risk control strategy canvas, into JSON format data required by the back-end interface, and then passes it to the back-end.

[0049] (3) Use the corresponding business object that has been predefined in the backend code according to the business process model annotation to receive the JSON format data and convert it into a risk control strategy object in memory. This is a deserialization process.

[0050] (4) Check if the decision node associated with the sub-object corresponding to the service task element exists. If it does not exist, end directly and return an error to the front end. If it exists, continue to the next step.

[0051] (5) Adapt to the XML format specified in the business process model annotation, and try to convert the sub-objects corresponding to the defined elements in the risk control strategy object into the corresponding XML text to check their legality. For example, whether the in-degree and out-degree of the node meet the expectations, whether a cycle is formed, etc. If it is not legal, it will end directly; if it is legal, it will continue to the next step.

[0052] (6) Store at least part of the XML text content corresponding to the risk control strategy object (for example, mainly including the XML content corresponding to the sub-objects of the definition element) in the table corresponding to the risk control strategy in the database.

[0053] In one or more embodiments of this specification, after the risk control strategy text is stored in the database, when the corresponding risk control strategy needs to be loaded, the risk control strategy text is read from the database, converted into a risk control strategy business object, and the metadata of the decision nodes associated with the risk control strategy business object is obtained. Based on the metadata of the decision nodes, the corresponding rules and actions are assembled, instantiated into corresponding executable objects, and the decision calculations are performed on the received risk control events according to the risk control strategy and the executable objects. In this way, the risk control strategy business object guides the direction of the process, and the decision nodes guide the specific conditions and actions in the process, realizing decision calculations for risk control events.

[0054] Risk control events can be caused by HTTP requests sent by business access parties (different platforms or product lines, etc.) in accordance with an agreed message format (e.g., JSON format).

[0055] Furthermore, in the specific implementation, the process engine and the decision calculation engine can work together to execute the steps in the previous paragraph. After converting the risk control strategy business object, the sub-objects corresponding to the service task elements can be located, and then the associated decision nodes can be located to generate executable objects. In addition, if the process engine can directly support the sub-objects corresponding to process elements in the risk control strategy business object, then the process engine can be allowed to use the sub-object.

[0056] It should be noted that in practical applications, sub-objects used for front-end and back-end interaction may not be compatible with sub-objects supported by the process engine, even if their substantive content is essentially the same. In cases of incompatibility, the required sub-objects can be separately converted to meet the requirements of the process engine. Based on this idea, when performing decision calculations on received risk control events according to the risk control strategy and based on the executable object, the sub-text corresponding to the process element can be obtained from the risk control strategy text. This sub-text is then converted into the strategy process business object required by the process engine. If the decision calculation engine receives a risk control event, it starts from the sub-object corresponding to the starting node element in the strategy process business object, passes through the sub-object corresponding to the sequential flow element, and calls the corresponding executable object to perform decision calculations when encountering the sub-object corresponding to the gateway element, until it reaches the sub-object corresponding to the ending node element. In this case, although the sub-objects corresponding to the process elements in the strategy process business object and the risk control strategy object mentioned above are essentially the same in substantive content, they are not completely identical.

[0057] Before a risk control event occurs, the policy process business object and executable object can be cached so that when a risk control event is received, it can be determined whether there is a corresponding risk control policy in the cache. If there is no corresponding risk control policy, no decision calculation will be performed.

[0058] Based on the above description, one or more embodiments of this specification also provide a practical application scenario, Figure 1 The process involves a schematic diagram of the risk control strategy loading and execution flow, as shown below. Figure 4 As shown.

[0059] Figure 4 The process includes the following steps: (1) When the program starts, it will start a timed task, for example, it will be executed once every 60 seconds. Each task in it is to complete the things in steps (2) to (6) below.

[0060] (2) Load the running risk control strategy from the database, that is, the risk control strategy text of at least part of the previously stored XML. The running state can include trial operation, gray-scale and formal operation.

[0061] (3) The data loaded from the database will be deserialized into the corresponding risk control strategy business object.

[0062] (4) Read the metadata of the decision nodes associated with the risk control strategy business object, assemble the corresponding rules and actions, and instantiate them into the corresponding executable objects.

[0063] (5) Convert the XML sub-text corresponding to the process element in the risk control strategy text into the business object required by the process engine, namely the strategy process business object. The process engine can then schedule and manage the entire process based on this business object.

[0064] (6) Cache the converted strategy process business objects and the executable objects corresponding to the decision nodes.

[0065] (7) The business access party sends a risk control event according to the agreed format and sends a request to the decision calculation engine to obtain the calculation result of the risk control strategy.

[0066] (8) When the decision calculation engine receives a request, it first checks whether there is a corresponding risk control strategy (i.e., strategy process business object and executable object) in the cache. If it does not exist, it returns an error and ends. If it exists, it continues to execute the next step.

[0067] (9) The process engine schedules and loads the risk control strategy associated with the risk control event for calculation.

[0068] (10) The calculation process of the risk control strategy starts with the starting node.

[0069] (11) The intermediate calculation process of the whole process includes several decision nodes and branch nodes (i.e. gateways). When a decision node is scheduled, it will execute the rules and actions associated with it. When a branch node is scheduled, it will execute the conditions associated with the edge it is connected to, so that the process engine can select an outgoing edge to continue execution.

[0070] (12) When the edge is reached, a decision will be made because the next node may be a fork node, a decision node, or a termination node.

[0071] (13) If the next node is the termination node, the entire process can end after the next step is completed. Otherwise, return to step (11) and continue the process of steps (11) to (13) in the next round.

[0072] (14) After entering the termination node, the parameter assignment and decision results will be summarized based on the calculation results of the decision node, and a complete result will be returned to the caller after merging. Among them, parameter is the left value part of parameter assignment, which is used to store the calculation result of parameter script and return it to the business access party in the risk control interface; parameter script is the right value part of parameter assignment, which can be a combination of variables, functions and parameters, and is a computable expression; parameter assignment is a combination of parameter and parameter script, the left value part is the parameter, and the right value part is the parameter script. It is an assignment expression that assigns the calculation result of the right value to the left value.

[0073] The above describes the orchestration, storage, loading, and execution process of risk control strategies provided in this application. In practical applications, compared to normal business operations, risk control work has distinct characteristics: frequent iterative updates are likely in multiple localized areas of the process. Furthermore, these updates are often subtle and highly independent, generally not affecting other parts of the process. Examples include updates to decision conditions for certain branches, multiple parallel sub-conditions, corresponding actions, blacklists, and whitelists. The volatile nature of online environment risks necessitates these characteristics, requiring risk control strategies to closely follow the latest or potential risks. In this situation, for orchestrated and stored risk control strategies, if business personnel want to update them via the front end, they may need to restore the text format to the original canvas content, then modify and orchestrate the canvas content before converting and storing it. This process is cumbersome, and if business personnel change, it becomes inconvenient for successors to continue updating and maintaining the risk control strategies. To prevent such problems from occurring, this application further provides a solution for rapid iteration of single-point content for risk control strategies. This solution allows for accurate updates without restoring stored content back to the canvas when updating risk control strategies, and is especially suitable for nodes that are frequently updated. The specific solution is as follows.

[0074] In one or more embodiments of this specification, the graphical orchestration operation is further extended to include marking operations for rapid iteration points of risk control strategies. When business personnel initially orchestrate a certain risk control strategy, they can mark one or more objects as rapid iteration points of the risk control strategy so that the content involved in the marked points can be quickly iterated and updated when needed. The standard graphical annotation is extended with the design of strategy injection fusion marking elements, which are included in process elements, for example.

[0075] Assuming that a marking operation for the rapid iteration point of the risk control strategy is performed on the canvas page, after the initial risk control strategy canvas content is completed, it can be serialized and passed to the backend. The backend can then obtain the business object defined by the strategy injection and fusion marking element as the rapid iteration business object. Based on the rapid iteration business object, it receives and converts the data corresponding to the marking operation in the serialized data, and converts and stores the corresponding formatted text to the database.

[0076] After storing the risk control strategy text in the database, if you want to update the risk control strategy, especially if you only want to update objects with a small scope that have been marked, you don't need to restore the previous risk control strategy from the database to the canvas page. Instead, you can directly receive the single-point content of the risk control strategy (i.e., the update content for the object to be updated) through the front-end canvas page. Then, through the back-end code, based on the rapidly iterating business objects, the single-point content of the risk control strategy can be automatically injected and integrated into the corresponding position in the risk control strategy text. In other words, you only need to perform a small number of write operations on the database, without having to read a lot of data and restore the canvas content. This can effectively improve efficiency and reduce the data interaction burden when rapidly iterating risk control strategies.

[0077] The above detailed explanation demonstrates that the solution presented in this application effectively addresses the problems in the background art and further improves efficiency. For a more intuitive comparison, a diagram illustrating the effect is provided to address the problems in the background art; see [link to diagram]. Figure 5 , Figure 6 .

[0078] Figure 5 This diagram illustrates the comparison of the effects of the decision computing engine provided in one or more embodiments of this specification on connecting to multiple business platforms.

[0079] exist Figure 5 In the middle, the left side represents the previous solution, which requires designing corresponding control strategies, orchestration, and storage formats for different platforms; the right side represents the solution proposed in this application, which can be processed according to a standardized and unified orchestration and storage format, and is applicable to multiple different platforms without relying on a specific implementation, thus improving the reusability and flexibility of the system.

[0080] Figure 6 This diagram illustrates the effect comparison of the strategy storage structure in the database provided in one or more embodiments of this specification.

[0081] exist Figure 6 In the diagram, the left side represents the previous solution, which required maintaining a large number of relationships in the database tables, including nodes and edges (representing the execution order of nodes), nodes and processes (the risk control strategies to which decision nodes belong), edges and branches (representing the execution order of gateways), branches and processes (the risk control strategies to which gateways belong), and edges and processes (the risk control strategies to which edges belong). The right side represents the solution proposed in this application. Under this solution, these relationships are constrained and defined through the aforementioned process elements, rather than a large number of complex relationship data tables. This reduces the number of relationships to just one field in the risk control strategy metadata, effectively reducing the storage pressure on the database.

[0082] Based on the same idea, one or more embodiments of this specification also provide apparatus and devices corresponding to the above methods, such as... Figure 7 , Figure 8 As shown. The apparatus and equipment are capable of performing the above methods and related alternatives accordingly.

[0083] Figure 7 This specification provides a schematic diagram of a design apparatus for orchestrating risk control strategies, which includes one or more embodiments. The canvas arrangement operation module 702 receives graphical arrangement operations of risk control strategies through the front-end canvas page and obtains the risk control strategy canvas content. The serialization processing module 704 converts the content of the risk control strategy canvas into serialized data and transmits it to the backend. The business object processing module 706 receives and converts the serialized data through the backend according to the business object predefined based on standard graphical annotations independent of programming languages, to obtain the risk control strategy business object; The strategy text checking module 708 converts the risk control strategy business object into risk control strategy text according to the text format specified by the standard graphic annotation, so as to check its legality. If the legality check passes, the strategy text storage module 710 stores the risk control strategy text in the database to await loading and execution.

[0084] Optionally, the standard graphical annotation includes a business process model annotation containing service task elements, and the text format specified by the standard graphical annotation includes XML format.

[0085] Optionally, the business object processing module 706, after obtaining the risk control strategy business object and before storing the risk control strategy text in the database, obtains the sub-object corresponding to the service task element in the risk control strategy business object; Determine whether the sub-objects of the service task element are associated with valid decision nodes, wherein the decision nodes are used to indicate which rules are matched and the corresponding actions are executed. The result of the judgment is determined to be yes.

[0086] Optionally, it also includes: The strategy loading and execution module 712, after storing the risk control strategy text in the database, converts the risk control strategy text into a risk control strategy business object when it is necessary to load the risk control strategy. Obtain the metadata of the decision node associated with the risk control strategy business object; Based on the metadata of the decision node, assemble the corresponding rules and actions, and instantiate them into the corresponding executable objects; According to the risk control strategy, decision calculations are performed on the received risk control events based on the executable object.

[0087] Optionally, the business process model annotation includes process elements; the process elements include the service task element, start node element, sequence flow element, gateway element, and end node element.

[0088] Optionally, the strategy loading and execution module 712 obtains the sub-text corresponding to the process element from the risk control strategy text; Convert the subtext into the strategy process business object required by the process engine; If the decision calculation engine receives a risk control event, it starts from the sub-object corresponding to the starting node element in the strategy process business object, passes through the sub-object corresponding to the sequence flow element, and when it encounters the sub-object corresponding to the gateway element, it calls the corresponding executable object to perform decision calculation, until it reaches the sub-object corresponding to the termination node element.

[0089] Optionally, the graphical orchestration operation includes marking the rapid iteration points of the risk control strategy, and the standard graphical annotation includes strategy injection fusion marking elements; The business object processing module 706 obtains the business object defined by the injection fusion marker element according to the strategy, and uses it as the fast iteration business object. Based on the fast iteration business object, receive and transform the data in the serialized data corresponding to the tag operation; The canvas arrangement operation module 702 receives single-point content of the risk control strategy through the front-end canvas page after storing the risk control strategy text in the database. The business object processing module 706 and the strategy text checking module 708 automatically inject and integrate the single-point content of the risk control strategy into the corresponding position in the risk control strategy text according to the rapid iteration business object.

[0090] Optionally, the strategy loading and execution module caches the strategy process business object and the executable object before the decision calculation engine receives the risk control event, so as to determine whether there is a corresponding risk control strategy in the cache when the risk control event is received; If no corresponding risk control strategy exists, the aforementioned decision calculation will not be performed.

[0091] Optionally, the strategy text storage module 710, after converting the risk control strategy business object into risk control strategy text, obtains the sub-text corresponding to the process element from the risk control strategy text; The subtext is stored in the database using a single field so that it can be used for decision calculations by querying that single field.

[0092] Optionally, the business process model annotation includes a definition element as the root element, the definition element includes the process element and a view element, and the view element is used to represent the position and appearance of the elements included in the process element on the canvas page.

[0093] Figure 8 A schematic diagram of a design device for orchestrating risk control strategies, provided for one or more embodiments of this specification, the device comprising: At least one processor; and, A memory communicatively connected to the at least one processor; wherein, The memory stores instructions executable by the at least one processor, which, when executed by the at least one processor, enable the at least one processor to: The risk control strategy can be graphically arranged through the front-end canvas page to obtain the content of the risk control strategy canvas. The content of the risk control strategy canvas is converted into serialized data and transmitted to the backend; Through the backend, the serialized data is received and converted according to the business object predefined based on standard graphical annotations independent of programming languages ​​to obtain the risk control strategy business object; Based on the text format specified in the standard graphical annotation, the risk control strategy business object is converted into risk control strategy text for legality checking. If the legality check passes, the risk control strategy text is stored in the database to await loading and execution.

[0094] Based on the same idea, one or more embodiments of this specification also provide a non-volatile computer storage medium storing computer-executable instructions, wherein the computer-executable instructions are configured as follows: The risk control strategy can be graphically arranged through the front-end canvas page to obtain the content of the risk control strategy canvas. The content of the risk control strategy canvas is converted into serialized data and transmitted to the backend; Through the backend, the serialized data is received and converted according to the business object predefined based on standard graphical annotations independent of programming languages ​​to obtain the risk control strategy business object; Based on the text format specified in the standard graphical annotation, the risk control strategy business object is converted into risk control strategy text for legality checking. If the legality check passes, the risk control strategy text is stored in the database to await loading and execution.

[0095] In the 1990s, improvements to a technology could be clearly distinguished as either hardware improvements (e.g., improvements to the circuit structure of diodes, transistors, switches, etc.) or software improvements (improvements to the methodology). However, with technological advancements, many methodological improvements today can be considered direct improvements to the hardware circuit structure. Designers almost always obtain the corresponding hardware circuit structure by programming the improved methodology into the hardware circuit. Therefore, it cannot be said that a methodological improvement cannot be implemented using hardware physical modules. For example, a Programmable Logic Device (PLD) (such as a Field Programmable Gate Array (FPGA)) is such an integrated circuit whose logic function is determined by the user programming the device. Designers can program and "integrate" a digital system onto a PLD themselves, without needing chip manufacturers to design and manufacture dedicated integrated circuit chips. Furthermore, nowadays, instead of manually manufacturing integrated circuit chips, this programming is mostly implemented using "logic compiler" software. Similar to the software compiler used in program development, the original code before compilation must also be written in a specific programming language, called a Hardware Description Language (HDL). There are many HDLs, such as ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, and RHDL (Ruby Hardware Description Language). Currently, the most commonly used are VHDL (Very-High-Speed ​​Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art should also understand that by simply performing some logic programming on the method flow using one of these hardware description languages ​​and programming it into an integrated circuit, the hardware circuit implementing the logical method flow can be easily obtained.

[0096] The controller can be implemented in any suitable manner. For example, it can take the form of a microprocessor or processor and a computer-readable medium storing computer-readable program code (e.g., software or firmware) executable by the (micro)processor, logic gates, switches, application-specific integrated circuits (ASICs), programmable logic controllers, and embedded microcontrollers. Examples of controllers include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicon Labs C8051F320. A memory controller can also be implemented as part of the control logic of the memory. Those skilled in the art will also recognize that, in addition to implementing the controller in purely computer-readable program code form, the same functionality can be achieved by logically programming the method steps to make the controller take the form of logic gates, switches, application-specific integrated circuits, programmable logic controllers, and embedded microcontrollers. Therefore, such a controller can be considered a hardware component, and the means included therein for implementing various functions can also be considered as structures within the hardware component. Alternatively, the means for implementing various functions can be considered as both software modules implementing the method and structures within the hardware component.

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

[0098] For ease of description, the above devices are described in terms of function, divided into various units. Of course, in implementing this specification, the functions of each unit can be implemented in one or more software and / or hardware components.

[0099] Those skilled in the art will understand that the embodiments of this specification can be provided as methods, systems, or computer program products. Therefore, the embodiments of this specification can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the embodiments of this specification can 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.

[0100] This specification is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this specification. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0101] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0102] These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable apparatus for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

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

[0104] Memory may include non-persistent storage in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.

[0105] Computer-readable media includes both permanent and non-permanent, removable and non-removable media that can store information using any method or technology. Information can be computer-readable instructions, data structures, modules of programs, 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 technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic magnetic disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0106] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0107] This specification can be described in the general context of computer-executable instructions that are executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, etc., that perform a specific task or implement a specific abstract data type. This specification can also be practiced in distributed computing environments, where tasks are performed by remote processing devices connected via a communication network. In distributed computing environments, program modules can reside in local and remote computer storage media, including storage devices.

[0108] The various embodiments in this specification are described in a progressive manner. Similar or identical parts between embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. In particular, the embodiments of apparatus, devices, and non-volatile computer storage media are basically similar to the method embodiments, so the descriptions are relatively simple; relevant parts can be referred to the descriptions of the method embodiments.

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

[0110] The above description is merely one or more embodiments of this specification and is not intended to limit this specification. Various modifications and variations can be made to the one or more embodiments of this specification by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principle of one or more embodiments of this specification should be included within the scope of the claims of this specification.

Claims

1. A design method for risk control strategy orchestration, comprising: The risk control strategy can be graphically arranged through the front-end canvas page to obtain the content of the risk control strategy canvas. The content of the risk control strategy canvas is converted into serialized data and transmitted to the backend; Through the backend, the serialized data is received and converted according to the business object predefined based on standard graphical annotations independent of programming languages ​​to obtain the risk control strategy business object; Based on the text format specified in the standard graphical annotation, the risk control strategy business object is converted into risk control strategy text for legality checking. If the legality check passes, the risk control strategy text is stored in the database to await loading and execution.

2. The method as described in claim 1, wherein the standard graphical annotation includes a business process model annotation containing service task elements, and the text format specified by the standard graphical annotation includes XML format.

3. The method as described in claim 2, wherein after obtaining the risk control strategy business object and before storing the risk control strategy text in the database, the method further includes: Obtain the sub-object corresponding to the service task element in the risk control strategy business object; Determine whether the sub-objects of the service task element are associated with valid decision nodes, wherein the decision nodes are used to indicate which rules are matched and the corresponding actions are executed. The result of the judgment is determined to be yes.

4. The method as described in claim 3, wherein after storing the risk control strategy text in the database, the method further includes: When the risk control strategy needs to be loaded, the risk control strategy text is converted into a risk control strategy business object; Obtain the metadata of the decision node associated with the risk control strategy business object; Based on the metadata of the decision node, assemble the corresponding rules and actions, and instantiate them into the corresponding executable objects; According to the risk control strategy, decision calculations are performed on the received risk control events based on the executable object.

5. The method as described in claim 4, wherein the business process model annotation includes process elements; the process elements include the service task element, the start node element, the sequence flow element, the gateway element, and the end node element.

6. The method as described in claim 5, wherein the step of performing decision calculations on the received risk control events based on the executable object according to the risk control strategy specifically includes: Obtain the sub-text corresponding to the process element from the risk control strategy text; Convert the subtext into the strategy process business object required by the process engine; If the decision calculation engine receives a risk control event, it starts from the sub-object corresponding to the starting node element in the strategy process business object, passes through the sub-object corresponding to the sequence flow element, and when it encounters the sub-object corresponding to the gateway element, it calls the corresponding executable object to perform decision calculation, until it reaches the sub-object corresponding to the termination node element.

7. The method as described in claim 1, wherein the graphical orchestration operation includes a marking operation for rapid iteration points of the risk control strategy, and the standard graphical annotation includes strategy injection fusion marking elements; The process of receiving and converting the serialized data based on a business object pre-defined using standard graphical annotations independent of programming languages ​​specifically includes: Obtain the business object defined by the fusion marker element injected according to the strategy, and use it as the fast iteration business object; Based on the fast iteration business object, receive and transform the data in the serialized data corresponding to the tag operation; After storing the risk control strategy text in the database, the method further includes: Receive risk control strategy content at a single point through the front-end canvas page; Based on the rapidly iterating business object, the single-point content of the risk control strategy is automatically injected and integrated into the corresponding position in the risk control strategy text.

8. The method of claim 6, wherein before the decision calculation engine receives the risk control event, the method further comprises: The strategy process business object and the executable object are cached so that when a risk control event is received, it can be determined whether there is a corresponding risk control strategy in the cache. If no corresponding risk control strategy exists, the aforementioned decision calculation will not be performed.

9. The method of claim 5, wherein after converting the risk control strategy business object into risk control strategy text, the method further includes: Obtain the sub-text corresponding to the process element from the risk control strategy text; The subtext is stored in the database using a single field so that it can be used for decision calculations by querying that single field.

10. The method of claim 5, wherein the business process model annotation includes a definition element as the root element, the definition element includes the process element and a view element, and the view element is used to represent the position and appearance of the elements included in the process element on the canvas page.

11. A design device for orchestrating risk control strategies, comprising: The canvas arrangement module receives graphical arrangement operations for risk control strategies through the front-end canvas page and obtains the content of the risk control strategy canvas. The serialization processing module converts the content of the risk control strategy canvas into serialized data and transmits it to the backend; The business object processing module receives and transforms the serialized data through the backend, based on the business objects predefined according to standard graphical annotations independent of programming languages, to obtain risk control strategy business objects; The strategy text checking module converts the risk control strategy business object into risk control strategy text according to the text format specified by the standard graphic annotation, so as to check its legality. If the legality check passes, the strategy text storage module stores the risk control strategy text in the database for loading and execution.

12. The apparatus of claim 11, wherein the standard graphical annotation includes a business process model annotation containing service task elements, and the text format specified by the standard graphical annotation includes XML format.

13. The apparatus of claim 12, wherein the business object processing module, after obtaining the risk control strategy business object and before storing the risk control strategy text in the database, obtains a sub-object in the risk control strategy business object corresponding to the service task element; Determine whether the sub-objects of the service task element are associated with valid decision nodes, wherein the decision nodes are used to indicate which rules are matched and the corresponding actions are executed. The result of the judgment is determined to be yes.

14. The apparatus of claim 13, further comprising: The strategy loading and execution module, after storing the risk control strategy text in the database, converts the risk control strategy text into a risk control strategy business object when it is necessary to load the risk control strategy. Obtain the metadata of the decision node associated with the risk control strategy business object; Based on the metadata of the decision node, assemble the corresponding rules and actions, and instantiate them into the corresponding executable objects; According to the risk control strategy, decision calculations are performed on the received risk control events based on the executable object.

15. The apparatus of claim 14, wherein the business process model annotation includes process elements; the process elements include the service task element, the start node element, the sequence flow element, the gateway element, and the end node element.

16. The apparatus of claim 15, wherein the strategy loading and execution module obtains sub-text corresponding to the process element from the risk control strategy text; Convert the subtext into the strategy process business object required by the process engine; If the decision calculation engine receives a risk control event, it starts from the sub-object corresponding to the starting node element in the strategy process business object, passes through the sub-object corresponding to the sequence flow element, and when it encounters the sub-object corresponding to the gateway element, it calls the corresponding executable object to perform decision calculation, until it reaches the sub-object corresponding to the termination node element.

17. The apparatus of claim 11, wherein the graphical orchestration operation includes a marking operation for rapid iteration points of the risk control strategy, and the standard graphical annotation includes a strategy injection fusion marking element; The business object processing module obtains the business object defined by the injection fusion marker element according to the strategy, and uses it as the fast iteration business object. Based on the fast iteration business object, receive and transform the data in the serialized data corresponding to the tag operation; The canvas arrangement operation module receives single-point content of the risk control strategy through the front-end canvas page after storing the risk control strategy text in the database. The business object processing module and the strategy text checking module automatically inject and integrate the single-point content of the risk control strategy into the corresponding position in the risk control strategy text based on the rapidly iterating business object.

18. The apparatus of claim 16, wherein the strategy loading and execution module caches the strategy process business object and the executable object before the decision calculation engine receives the risk control event, so as to determine whether there is a corresponding risk control strategy in the cache when the risk control event is received; If no corresponding risk control strategy exists, the aforementioned decision calculation will not be performed.

19. The apparatus of claim 15, wherein the strategy text storage module, after converting the risk control strategy business object into risk control strategy text, obtains the sub-text corresponding to the process element from the risk control strategy text; The subtext is stored in the database using a single field so that it can be used for decision calculations by querying that single field.

20. The apparatus of claim 15, wherein the business process model annotation includes a definition element as a root element, the definition element including the process element and a view element, the view element being used to represent the position and appearance of the elements included in the process element on the canvas page.

21. A design device for risk control strategy orchestration, comprising: At least one processor; as well as, A memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to perform: The risk control strategy can be graphically arranged through the front-end canvas page to obtain the content of the risk control strategy canvas. The content of the risk control strategy canvas is converted into serialized data and transmitted to the backend; Through the backend, the serialized data is received and converted according to the business object predefined based on standard graphical annotations independent of programming languages ​​to obtain the risk control strategy business object; Based on the text format specified in the standard graphical annotation, the risk control strategy business object is converted into risk control strategy text for legality checking. If the legality check passes, the risk control strategy text is stored in the database to await loading and execution.

Images