Rule switching method, apparatus, device, medium and product

Abstract

The application discloses a rule switching method and device, equipment, medium and product, relates to the field of rule management, and the method is applied to a risk control computing engine. The method comprises the following steps: receiving to-be-processed information sent by a data distribution route, recalculating a historical transaction information cache based on the to-be-processed information, obtaining a recalculation result, and sending the recalculation result to the data distribution route; receiving a version switching instruction sent by the data distribution route, performing rule switching on core calculation rules of the risk control computing engine based on the version switching instruction, and obtaining a switching result. Thus, the problem that current intelligent customer service is not accurate in recognizing multi-intention sentences is solved, and the efficiency of rule switching is improved.

Description

TECHNICAL FIELD

[0001] The present application relates to the field of rule management, and in particular to a rule switching method, device, equipment, medium and product. BACKGROUND

[0002] In the field of asset management compliance risk control, the platform needs to support business personnel to add, delete and modify rules in the middle of the operation and real-time affect rule calculation results. At present, there are two main rule effective implementation methods in the market. The first is the rule change next day effective method. The operation logic is that the rule change operation is not immediately sent to the risk control calculation engine, but the latest rule is loaded and made effective when the risk control calculation engine is started in the morning. The second is the rule card single real-time effective method. In this way, the rule change operation is immediately sent to the risk control calculation engine, and the risk control calculation engine needs to perform synchronous card single processing on the rule change operation. Only after the rule change related processing is completed, the subsequent business instructions and other messages can be processed.

[0003] However, the above two existing methods have obvious deficiencies and cannot meet the core needs of business scenarios. For the rule change next day effective method, there is a significant delay problem. The rule cannot be made effective immediately after the rule change, which prevents business personnel from viewing the impact of rule changes on calculation results in real time, which is not conducive to timely adjusting rules and conducting business. The rule card single real-time effective method will block the processing of subsequent messages, especially when the rule change involves a long time-consuming recalculation task, which will directly cause the risk control processing of subsequent business instructions to timeout, seriously affecting the smooth progress of the business process and reducing the efficiency of risk control processing.

[0004] The above content is only used to assist in understanding the technical solutions of the present application and does not represent the acknowledgement of the above content as prior art. SUMMARY

[0005] The main purpose of the present application is to provide a rule switching method, device, equipment, medium and product, which aims to solve the technical problem of high delay and blocking of subsequent business instruction processing in the existing technology in the field of asset management compliance risk control, and cannot realize real-time rule change.

[0006] To achieve the above purpose, the present application provides a rule switching method, which is applied to a risk control calculation engine, and the rule switching method comprises the following steps:

[0007] Receiving the to-be-processed information sent by the data distribution route, recalculating the historical transaction information cache based on the to-be-processed information to obtain a recalculation result, and sending the recalculation result to the data distribution route;

[0008] receive a version switching instruction sent by the data distribution route, perform rule switching on core computing rules of the risk control computing engine based on the version switching instruction, and obtain a switching result.

[0009] In an embodiment, the step of recalculating the historical transaction information cache based on the to-be-processed information to obtain a recalculated result comprises:

[0010] calculating transaction information in the to-be-processed information by using the initial rules to obtain a calculation result, and storing the calculation result in the historical transaction information cache;

[0011] in the case that there is rule change information in the to-be-processed information, constructing a new rule computing thread by using the rule change information;

[0012] calculating the to-be-processed transaction information and the historical transaction information cache by using the new rule computing thread to obtain a recalculated result.

[0013] In an embodiment, the step of constructing a new rule computing thread by using the rule change information comprises:

[0014] parsing the rule change information to obtain new rule logic parameters, a new rule identifier, and resource requirements;

[0015] creating an initial new rule computing thread based on the new rule identifier, and configuring computing resources to the initial new rule computing thread based on the resource requirements;

[0016] loading risk control computing logic corresponding to the new rule logic parameters to the initial new rule computing thread, and initializing a thread computing environment to obtain a new rule computing thread.

[0017] In an embodiment, the step of performing rule switching on core computing rules of the risk control computing engine based on the version switching instruction to obtain a switching result comprises:

[0018] adjusting an engine state of the risk control computing engine to a blocking state, and performing transaction task statistics on the new rule computing thread and an initial rule computing thread corresponding to the initial rules to obtain a to-be-completed task amount;

[0019] performing completion state detection on the new rule computing thread and the initial rule computing thread based on the to-be-completed task amount;

[0020] when the new rule computing thread and the initial rule computing thread complete the to-be-completed task amount, switching a computing interface to the new rule computing thread;

[0021] In the case of interface switching completion, the core computing rule is switched by the rule change information to obtain a switching result.

[0022] In addition, to achieve the above object, the application further provides a rule switching method applied to a data distribution route, comprising:

[0023] sending rule change information to a risk control computing engine, re-computing a historical transaction information cache based on the rule change information by the risk control computing engine to obtain a re-computation result, and sending the re-computation result to the data distribution route;

[0024] sending a rule version switching instruction to the risk control computing engine, and switching an initial computing rule of the risk control computing engine based on the version switching instruction by the risk control computing engine to obtain a switching result.

[0025] In an embodiment, after the step of sending the rule version switching instruction to the risk control computing engine, the method further comprises:

[0026] receiving second rule change information;

[0027] detecting processing information sent by the risk control computing engine;

[0028] if the switching result sent by the risk control computing engine is not detected, sending the second rule change information to a waiting queue;

[0029] if the switching result sent by the risk control computing engine is detected, sending the second rule change information to the risk control computing engine.

[0030] In addition, to achieve the above object, the application further provides a rule switching device applied to a risk control computing engine, comprising:

[0031] a re-computation module configured to receive to-be-processed information sent by a data distribution route, re-compute a historical transaction information cache based on the to-be-processed information to obtain a re-computation result, and send the re-computation result to the data distribution route;

[0032] a switching module configured to receive a version switching instruction sent by the data distribution route, switch a core computing rule of the risk control computing engine based on the version switching instruction to obtain a switching result.

[0033] In addition, to achieve the above object, the present application also provides a rule switching device, comprising a memory, a processor and a computer program stored in the memory and executable on the processor, and the computer program is configured to implement the steps of the rule switching method as described above.

[0034] In addition, to achieve the above object, the present application also provides a storage medium, which is a computer readable storage medium, and the storage medium stores a computer program, and the computer program is executed by a processor to implement the steps of the rule switching method as described above.

[0035] In addition, to achieve the above object, the present application also provides a computer program product, which comprises a computer program, and the computer program is executed by a processor to implement the steps of the rule switching method as described above.

[0036] The one or more technical solutions provided by the present application have at least the following technical effects:

[0037] The rule switching method, device, equipment, storage medium and computer program product provided by the present application are applied to a risk control computing engine, the method comprises the following steps: receiving to-be-processed information sent by a data distribution route, re-calculating a historical transaction information cache based on the to-be-processed information to obtain a re-calculation result, and sending the re-calculation result to the data distribution route; receiving a version switching instruction sent by the data distribution route, and switching core calculation rules of the risk control computing engine based on the version switching instruction to obtain a switching result. Therefore, after receiving to-be-processed information, the historical transaction information cache is re-calculated, the new rules are quickly adapted to the past data without waiting for the next day, and the re-calculation process does not interfere with the processing of subsequent business instructions, so that the problems of high delay and blocking are solved. After receiving the version switching instruction, the core calculation rules are switched, so that the new rules take effect immediately, and finally the real-time rule change is realized. The problem that the current intelligent customer service is not accurate in recognizing multi-intention sentences is solved, and the efficiency of rule switching is improved. BRIEF DESCRIPTION OF DRAWINGS

[0038] The accompanying drawings, which are incorporated into and form part of the specification, illustrate embodiments consistent with the present application and, together with the specification, serve to explain the principles of the application.

[0039] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the accompanying drawings needed to be used in the embodiments or prior art description will be briefly introduced as follows. Obviously, for those skilled in the art, other drawings can also be obtained without creative labor based on these drawings.

[0040] Figure 1Flowchart provided by the rule switching method embodiment one of the present application;

[0041] Figure 2 Schematic diagram of the rule switching method of the present application involving re-calculation of the risk control computing engine;

[0042] Figure 3 Schematic diagram of the rule switching method of the present application involving rule switching under multi-instance deployment;

[0043] Figure 4 Flowchart provided by the rule switching method embodiment two of the present application;

[0044] Figure 5 Schematic diagram of the rule switching method of the present application involving data routing distribution instruction;

[0045] Figure 6 Schematic diagram of the rule switching method of the present application involving rule change information;

[0046] Figure 7 Brief flowchart of the rule switching method of the present application embodiment two;

[0047] Figure 8 Module structure schematic diagram of the rule switching device of the present application embodiment;

[0048] Figure 9 Device structure schematic diagram of the hardware running environment involved in the rule switching method of the present application embodiment.

[0049] The object implementation, functional features and advantages of the present application will be further explained with reference to the accompanying drawings in combination with the embodiments. DETAILED DESCRIPTION

[0050] It should be understood that the specific embodiments described herein are only used to explain the technical solutions of the present application, and are not used to limit the present application.

[0051] In order to better understand the technical solutions of the present application, the specific embodiments will be described in detail below in combination with the drawings and specific embodiments.

[0052] The main solution of the embodiment of the application is: calculating transaction information in the to-be-processed information through initial rules to obtain a calculation result, and storing the calculation result to the historical transaction information cache; in the case that there is rule change information in the to-be-processed information, constructing a new rule calculation thread through the rule change information; calculating the unprocessed transaction information in the to-be-processed information and the historical transaction information cache through the new rule calculation thread to obtain a recalculation result. Analyzing the rule change information to obtain new rule logic parameters, a new rule identifier and resource requirements; creating an initial new rule calculation thread based on the new rule identifier, and configuring calculation resources to the initial new rule calculation thread based on the resource requirements; loading the risk control calculation logic corresponding to the new rule logic parameters to the initial new rule calculation thread, and initializing a thread calculation environment to obtain a new rule calculation thread. Adjusting the engine state of the risk control calculation engine to a blocking state, and performing transaction task statistics on the new rule calculation thread and the initial rule corresponding to the initial rule calculation thread to obtain a to-be-completed task amount; performing completion state detection on the new rule calculation thread and the initial rule calculation thread based on the to-be-completed task amount; when the new rule calculation thread and the initial rule calculation thread complete the to-be-completed task amount, switching the calculation interface to the new rule calculation thread; in the case that the interface switching is completed, performing rule switching on the core calculation rule through the rule change information to obtain a switching result. Sending the rule change information to the risk control calculation engine, performing recalculation on the historical transaction information cache based on the rule change information by the risk control calculation engine to obtain a recalculation result, and sending the recalculation result to the data distribution route; sending a rule version switching instruction to the risk control calculation engine, and performing rule switching on the initial calculation rule of the risk control calculation engine based on the version switching instruction by the risk control calculation engine to obtain a switching result. Receiving second rule change information; detecting the processing information sent by the risk control calculation engine; if the switching result sent by the risk control calculation engine is not detected, sending the second rule change information to a waiting queue; if the switching result sent by the risk control calculation engine is detected, sending the second rule change information to the risk control calculation engine. Thus, the problem that the existing technology has high delay and blocks subsequent business instruction processing in asset management compliance risk control, and real-time rule change cannot be realized is solved, the switching of the rules is realized, and the efficiency of rule switching is improved. Based on the application scheme, the rule change operation existing in reality is not sent to the risk control calculation engine to take effect immediately, business personnel cannot view the change of the calculation result caused by the rule change in real time, and the risk control calculation engine needs to process the rule change operation synchronously and block the processing of subsequent messages, thereby the problem of low efficiency is solved. A rule switching method is designed, the effectiveness of the rule switching method of the application is verified when the rules are switched, and finally the accuracy of rule switching by the application method is obviously improved.

[0053] In this embodiment, for convenience of description, the following is described taking a rule switching device as an execution subject.

[0054] In the field of asset management compliance risk control in the prior art, the platform needs to support business personnel to add, delete and modify rules in the disk and real-time affect rule calculation results. There are mainly two kinds of rule taking effect implementation methods in the current market. The first kind is a rule change next day taking effect method. The operation logic is that the rule change operation is not immediately sent to the risk control calculation engine, but the latest rule is loaded and takes effect when the risk control calculation engine starts in the disk the next day. The second kind is a rule card single real-time taking effect method. In this method, the rule change operation is immediately sent to the risk control calculation engine, and the risk control calculation engine needs to perform synchronous card single processing on the rule change operation. Only after the rule change related processing is completed, the subsequent business instructions and the like can be processed. However, in the rule change next day taking effect method, the new rule cannot take effect immediately, and the business personnel cannot real-time view the influence of the rule change on the calculation result, which is not conducive to timely adjusting the rule and developing the business. In addition, there is a blocking problem. In the rule card single real-time taking effect method, the synchronous card single processing hinders the subsequent message to advance, especially when the recalculation time is long, which can cause the risk control processing of the business instruction to be timed out, and seriously affects the smoothness of the business process. Further, there is an efficiency problem. The two methods cannot balance the real-time taking effect and the business continuity. Either the delay reduces the regulatory response efficiency, or the blocking drags the overall risk control processing efficiency. Therefore, in the rule change scene in the disk of the asset management compliance risk control, it is difficult to meet the core demand of real-time adjusting the rule by the business personnel and not affecting the normal instruction issuing.

[0055] The present application provides a solution. In the risk control calculation engine, after receiving the information to be processed, the recalculation based on the historical transaction information is cached, the new rule is quickly adapted to the past data without waiting for the next day, and the recalculation process does not interfere with the processing of subsequent business instructions, solving the problems of high delay and blocking. After receiving the version switching instruction, the core calculation rule is switched, so that the new rule takes effect immediately, and finally the real-time rule change is realized. The current intelligent customer service solves the problem of inaccurate recognition of multi-intention sentences, improves the efficiency of rule switching, and provides better service for users.

[0056] Based on this, the rule switching method provided in the embodiments of the present application is provided. Referring to Figure 1 , Figure 1 The flowchart of the first embodiment of the rule switching method of the present application is shown.

[0057] In this embodiment, the rule switching method is applied to the risk control calculation engine, and the rule switching method comprises steps S01-S02:

[0058] Step S01, receiving the to-be-processed information sent by the data distribution route, recalculating the historical transaction information cache based on the to-be-processed information, obtaining a recalculation result, and sending the recalculation result to the data distribution route;

[0059] Before the present embodiment is described, it should be clear that in the field of asset management compliance risk control, the platform needs to support business personnel to add, delete or modify rules in the middle of the game, and the operation needs to affect the rule calculation result in real time. There are two kinds of rule taking effect implementation methods in the current market, but both have obvious shortcomings. The first is the rule change taking effect the next day. The rule change operation will not be synchronized to the risk control calculation engine immediately, and the latest rule will be loaded to take effect when the engine starts before the next day. This method has a significant delay, and business personnel cannot view the impact of rule changes on calculation results in real time, which is not conducive to timely adjusting rules and promoting business. The second is the rule card single real-time taking effect method. The rule change operation will be immediately pushed to the engine, and the engine needs to be synchronized with the card single processing. After the rule change related task is completed, subsequent business instructions can be processed. This method will block the message flow. If the recalculation task related to rule change takes a long time, it is easy to cause the subsequent business risk control processing to timeout, which seriously reduces the risk control efficiency.

[0060] Therefore, in order to solve the above problems, the present embodiment receives the to-be-processed information sent by the data distribution route through the risk control calculation engine, and recalculates the historical transaction cache based on the to-be-processed information to obtain a recalculation result. The to-be-processed information includes rule change instructions and corresponding business data. After receiving the rule change instructions, the risk control calculation engine will mark the instructions as to-be-executed state, and preferentially perform incremental recalculation on the business data related to the rule change in the historical transaction cache, rather than full recalculation on all historical data, thereby reducing the time consumption of the recalculation task. During the incremental recalculation process, the risk control calculation engine will open an independent recalculation thread, which runs in parallel with the normal business instruction processing thread, to ensure that the recalculation task caused by the rule change will not block the real-time processing of the subsequent newly entered business instructions, thereby realizing the real-time taking effect of the rules while ensuring the overall efficiency of the risk control processing and the business continuity.

[0061] Step S02, receiving the version switching instruction sent by the data distribution route, performing rule switching on the core calculation rules of the risk control calculation engine based on the version switching instruction, and obtaining a switching result.

[0062] In the process of calculation, the risk control calculation engine can also receive a version switching instruction sent by the data distribution route, so the embodiment also switches the core calculation rule of the risk control calculation engine based on the received version switching instruction to obtain a switching result, wherein the version switching instruction carries a target rule version identifier and a corresponding rule effective timestamp. After receiving the instruction, the risk control calculation engine will first verify the integrity and legality of the target rule version, including verifying the signature information of the rule configuration file, the compatibility of the core algorithm module, and the integrity of the necessary parameters. After the verification is passed, the engine will trigger the switching process of the core calculation rule according to the setting of the effective timestamp. If the timestamp is the current time or the past time, the switching process of the core calculation rule is triggered immediately. If the timestamp is a future time, the switching task will be added to the timing task queue and automatically executed when the specified time point is reached. During the rule switching process, the engine uses a double-version parallel loading mechanism, that is, while retaining the old version of the rule currently running, the new version of the rule is loaded into a separate space in the memory asynchronously, and pre-compilation and initialization operations are performed on the new version of the rule to ensure its normal operation.

[0063] Specifically, the step S01 of recalculating the historical transaction information cache based on the to-be-processed information to obtain a recalculated result comprises:

[0064] Step S011, calculating the transaction information in the to-be-processed information through an initial rule to obtain a calculation result, and storing the calculation result to the historical transaction information cache;

[0065] Step S012, in the case that there is rule change information in the to-be-processed information, constructing a new rule calculation thread through the rule change information;

[0066] Step S013, calculating the to-be-processed transaction information and the historical transaction information cache through the new rule calculation thread to obtain a recalculated result.

[0067] First, based on the preset initial risk control rule, full-dimensional compliance and risk verification calculation is carried out on the transaction information in the to-be-processed information flowing in, and corresponding risk control calculation results such as risk level and disposal suggestion are generated, and the calculation results are stored to the historical transaction information cache, as shown in Figure 2 When the DDR (message distribution component) receives an instruction and other transaction messages, it directly submits them to the PTRCE (calculation engine) to trigger the above-mentioned rule calculation. The PTRCE synchronously caches the transaction messages to the historical transaction information cache.

Instruction message 1

Instruction message 3

Instruction message 4

[0068] When the rule change information such as rule addition, deletion, modification is contained in the to-be-processed information, the DDR submits the rule change message to the PTRCE, and the PTRCE immediately starts an independent new rule calculation thread to realize parallel advancement of new rule calculation and original transaction message processing process without interrupting the processing rhythm of normal transaction information.

[0069] After the new rule calculation thread is started, on the one hand, the transaction information in the current to-be-processed information which has not been completed calculation is executed synchronous calculation according to the new rule, and on the other hand, all historical transaction messages stored before the rule change message in the historical transaction information cache are recalled for full recalculation, such as Figure 2 As shown, after

rule change 2

instruction message 1

rule recalculation completion 2

[0070] More specifically, the step S012 of constructing a new rule calculation thread by the rule change information comprises:

[0071] The step S0121 comprises: parsing the rule change information to obtain a new rule logic parameter, a new rule identifier and resource demand;

[0072] The step S0122 comprises: creating an initial new rule calculation thread based on the new rule identifier, and configuring a calculation resource to the initial new rule calculation thread based on the resource demand;

[0073] The step S0123 comprises: loading a risk control calculation logic corresponding to the new rule logic parameter to the initial new rule calculation thread, and initializing a thread calculation environment to obtain a new rule calculation thread.

[0074] After receiving the rule change information in the to-be-processed information, a multi-dimensional analysis process is started, not only the core logic parameters (such as risk control threshold, judgment condition, priority weight, risk level mapping relationship, etc.) and the unique new rule identifier (used for distinguishing from historical rules, thread association and result tracing) of the new rule are extracted, but also a "resource demand prediction mechanism" is innovatively introduced. Through analyzing the rule change type (addition / modification / deletion), rule application scenario (such as cross-border transaction, large amount transfer, etc.), associated rule quantity and data processing level, the resource type (such as CPU core number, memory occupation, cache access permission, etc.) and resource quota required by the new rule calculation are accurately identified to avoid calculation lag or low efficiency caused by insufficient resources during subsequent thread running, and data support is provided for accurate resource configuration of the thread.

[0075] The new rule identified by the above step is indexed as a unique index, and an independent initial new rule calculation thread is created, which is completely isolated from the original transaction processing thread, ensuring that rule change calculation does not interfere with the advancement of normal business processes. Based on the parsed resource requirements, a "dynamic resource elastic allocation strategy" is adopted instead of a fixed resource allocation mode. Through the resource scheduling center of the risk control system, the overall resource occupation of the current system is monitored in real time, and the resource priority of the new rule (such as high-risk scenario rules) is combined to dynamically allocate the appropriate computing resources for the initial new rule calculation thread. For example, for complex rules involving large-scale historical data recalculation, CPU core number and memory quota are automatically increased; for simple rule adjustment, only basic resources are allocated, maximizing resource utilization efficiency while avoiding waste.

[0076] Further, the step S02 of switching the core calculation rule of the risk control calculation engine based on the version switching instruction to obtain a switching result comprises:

[0077] Step S021, adjusting the engine state of the risk control calculation engine to a blocking state, and performing transaction task statistics on the new rule calculation thread and the initial rule calculation thread corresponding to the initial rule to obtain a to-be-completed task amount;

[0078] Step S022, based on the to-be-completed task amount, detecting the completion state of the new rule calculation thread and the initial rule calculation thread;

[0079] Step S023, when the new rule calculation thread and the initial rule calculation thread complete the to-be-completed task amount, switching the calculation interface to the new rule calculation thread;

[0080] Step S024, in the case of completed interface switching, switching the core calculation rule based on the rule change information to obtain a switching result.

[0081] First, the running state of the risk control calculation engine (PTRCE) is adjusted to a blocking state, and new transaction calculation requests are suspended to avoid conflicts between new and old rules during rule switching. At the same time, a cross-thread task statistics mechanism is started to comprehensively count the historical data recalculation tasks being executed by the new rule calculation thread, the unprocessed transaction calculation tasks, and all transaction tasks in the initial rule calculation thread corresponding to the initial rule that have not been completed, accurately accounting for the total amount of to-be-completed tasks of the two types of threads, providing a clear basis for subsequent completion state detection. When PTRCE adopts multi-instance or multi-cluster deployment, each instance will be synchronized into a blocking state and develop task statistics to ensure the consistency of the whole cluster task statistics.

[0082] The task quantity to be completed counted in the above steps is taken as a reference to build a real-time state monitoring link to continuously track the task execution progress of the new rule calculation thread and the initial rule calculation thread. The monitoring dimensions include the execution state of a single task (not started, processing, completed, exception), the overall task completion rate of the thread, the estimated time consumption of the remaining tasks, etc. Through the combination of regular sampling and real-time feedback, the task completion of the two types of threads is accurately mastered. In the PTRCE multi-instance / multi-cluster deployment scenario, each instance independently carries out state detection and synchronizes to the message distribution component (DDR). The DDR aggregates the task completion states of all instances to form a complete cluster thread completion state view, avoiding the impact of single instance task delay on the overall switching rhythm.

[0083] When it is monitored that the new rule calculation thread and the initial rule calculation thread have both completed all the tasks to be completed, and there is no unprocessed task queue, the calculation interface switching process is immediately started to seamlessly switch the calculation request interface of all transaction messages in the risk control system from the interface corresponding to the initial rule calculation thread to the new rule calculation thread, so as to ensure that the subsequent transaction messages are processed by the new rule calculation thread, and the new rule is fully effective, as shown in Figure 3 As shown in the figure, in the PTRCE multi-instance or multi-cluster deployment, each instance will respectively feed back a rule recalculation completion message (such as

Rule Recalculation Completion 2

Rule Version Switching 2

[0084] Finally, after the interface switching is completed, the switching process of the core calculation rule is started based on the rule change information to replace the original initial core calculation rule in the risk control calculation engine with the new rule logic, parameter configuration and associated dependency relationship corresponding to the rule change information, and update the rule version identifier, complete the full switching of the core rule. During the switching process, the last verification of the syntax correctness, logical integrity and parameter validity of the new rule is performed to ensure that the switched rule can normally perform calculation. In the PTRCE multi-instance / multi-cluster deployment scenario, all instances will synchronously receive the rule version switching message sent by the DDR and perform the core rule switching operation in parallel. After the switching is completed, each instance feeds back the switching result to the DDR. After the DDR confirms that all instances have successfully switched, the engine blocking state is released and the reception of new transaction calculation requests is restored. The whole switching process ensures the consistency of the rule version of the complete cluster and the consistency of the input message.

[0085] This embodiment, through the above-described scheme, specifically receives pending information sent by the data distribution route, recalculates the cached historical transaction information based on the pending information, obtains the recalculation result, and sends the recalculation result to the data distribution route; it also receives a version switching instruction sent by the data distribution route, and switches the core calculation rules of the risk control calculation engine based on the version switching instruction, obtaining the switching result. Thus, by receiving pending information and recalculating based on the cached historical transaction information, the new rules can quickly adapt to past data without waiting for the next day, and the recalculation process does not interfere with subsequent business instruction processing, solving the problems of high latency and blocking. Upon receiving the version switching instruction, the core calculation rules are switched, making the new rules effective immediately, ultimately achieving real-time rule changes. This solves the current problem of inaccurate recognition of multi-intent statements by intelligent customer service and improves the efficiency of rule switching.

[0086] Based on the first embodiment of this application, in the second embodiment of this application, the content that is the same as or similar to the first embodiment described above can be referred to the above description, and will not be repeated hereafter. Based on this, please refer to... Figure 4 The rule switching method is applied to data distribution routing, and the rule switching method includes steps S03-S04:

[0087] Step S03: Send rule change information to the risk control calculation engine. The risk control calculation engine recalculates the historical transaction information cache based on the rule change information to obtain the recalculation result, and sends the recalculation result to the data distribution route.

[0088] Step S04: Send a rule version switching instruction to the risk control calculation engine. The risk control calculation engine then switches its initial calculation rules based on the version switching instruction to obtain the switching result.

[0089] First, all messages, including rule change information and transaction instructions, are uniformly accessed by the Data Distribution Router (DDR) component, and then forwarded by the DDR to the Prior Real-time Rule Computing Engine (PTRCE). Figure 5 As shown, [Instruction Message 1], [Rule Change 2], [Instruction Message 3], [Rule Recalculation Complete 2], and [Instruction Message 4] all flow through this path. After sending rule change information to the risk control calculation engine, PTRCE immediately initiates the recalculation process based on this rule change information. It retrieves all past transaction data stored in the historical transaction information cache, performs a full recalculation operation according to the new rule logic, and generates the corresponding recalculation results. During this process, subsequent transaction messages received after the rule change message (such as...) Figure 5The instruction message 3 in the rule change 2 is sent to the thread of the old rule for normal calculation and is synchronously sent to the thread of the new rule for parallel calculation, so as to ensure the continuity and integrity of the transaction data calculation before and after the rule switching, avoid the problems of data omission or repeated calculation, and feed back the recalculation result to the DDR after the recalculation is completed.

[0090] After the DDR receives the rule recalculation completion message fed back by the PTRCE, the DDR immediately sends a rule version switching instruction to the PTRCE. After the PTRCE receives the switching instruction, the PTRCE enters a blocking waiting state and continuously monitors the task execution of the thread of the old rule and the thread of the new rule. After all the messages are processed, the PTRCE replaces the initial calculation rule in the engine with the new rule corresponding to the rule change information based on the version switching instruction, completes the version switching of the core calculation rule, generates a switching result, and releases the parallel calculation thread resource corresponding to the rule change after the switching is completed. All the subsequent transaction messages are no longer shunted to the old rule thread and are only single-streamed to the new rule calculation thread for rule calculation after the switching, so as to ensure that the new rule is fully effective and the calculation logic is unified.

[0091] Specifically, after the step S04 of sending the rule version switching instruction to the risk control calculation engine, the method further includes:

[0092] Step S041, receiving second rule change information;

[0093] Step S042, detecting the processing information sent by the risk control calculation engine;

[0094] Step S043, if the switching result sent by the risk control calculation engine is not detected, the second rule change information is sent to a waiting queue;

[0095] Step S044, if the switching result sent by the risk control calculation engine is detected, the second rule change information is sent to the risk control calculation engine.

[0096] The data distribution router (DDR) continuously monitors the flow of various messages. When a new rule change request is captured, the new rule change request is defined as second rule change information and is received, as shown in the message processing logic. Figure 6 The second rule change information and other rule change messages (such as the rule change 2 and the rule change 3) follow a unified access standard. The DDR records the receiving time stamp, the change type (addition, modification, or deletion), and other metadata of the message when receiving, provides a basis for subsequent queuing and scheduling, and ensures the integrity and consistency in the message transmission process, so as to avoid the message loss caused by network jitter or system delay.

[0097] After receiving the second rule change information, the DDR immediately starts real-time detection of the processing state of the risk control computing engine (PTRCE). The detection dimension focuses on whether the PTRCE is processing a previous rule change message, whether a feedback of a rule recalculation completion message of the previous round has been received, whether it is in a rule version switching process, and the core is to determine whether there is an unprocessed rule change message in the cache. Due to the limited resources of the server where the PTRCE is located, multiple rule changes share the same thread for parallel computing inside the PTRCE. If multiple rule change messages are directly queued for parallel computing, the version switching message of the previous rule change may lag behind the message of the subsequent rule change, causing the problem of delayed switching. Therefore, this detection link provides key state support for the subsequent scheduling logic.

[0098] If it is found after detection that the DDR has not received the rule switching result of the previous round sent by the PTRCE, it indicates that the PTRCE is still processing the previous rule change related task (such as recalculation and version switching). At this time, the DDR will not send the second rule change information directly to the PTRCE, but will add it to the preset rule change to-be-sent queue for queuing. When the DDR has sent

rule change 2

rule change 3

[0099] If the DDR receives the rule switching result of the previous round sent by the PTRCE, it indicates that the recalculation and version switching of the previous rule change have been completed, and the PTRCE is in an idle state to process new tasks. At this time, the DDR takes the second rule change information from the rule change to-be-sent queue and immediately sends it to the PTRCE for processing. After the DDR receives

rule recalculation completion 2

rule version switching 2

rule change 3

[0100] The embodiment realizes the implementation process of the rule switching method by the above scheme, specifically by sending rule change information to the risk control computing engine, re-computing the historical transaction information cache based on the rule change information by the risk control computing engine to obtain a re-computed result, and sending the re-computed result to the data distribution router; sending a rule version switching instruction to the risk control computing engine, and switching the initial computing rule of the risk control computing engine based on the version switching instruction to obtain a switching result. Thus, after receiving the to-be-processed information, the historical transaction information cache is re-computed, the new rule is quickly adapted to the past data without waiting for the next day, and the re-computation process does not interfere with the subsequent business instruction processing, solving the problems of high delay and blocking. After receiving the version switching instruction, the core computing rule is switched, the new rule takes effect immediately, and finally the real-time rule change is realized. The problems of inaccurate recognition of multi-intention sentences by the current intelligent customer service are solved, and the efficiency of rule switching is improved.

[0101] Exemplarily, in order to help understand the implementation process of the rule switching method obtained after the above embodiment one, please refer to Figure 7 , Figure 7 A brief flowchart of a rule switching method is provided, specifically:

[0102] First, the DDR is the core of unified message access and distribution, continuously receives various instruction messages and rule change messages, and all messages enter the system first through a repetition checking mechanism. If a repeated rule change message or instruction message is detected, a discard logic is triggered directly to avoid repeated computation from occupying system resources and ensure the uniqueness of message processing.

[0103] When the DDR receives a rule change message, it immediately queries whether there is an uncompleted rule change task in the current cache. If there is no uncompleted rule change, the rule change message is directly sent to the PTRCE, and the PTRCE starts an independent thread to load a new rule logic to perform parallel re-computation on the historical transaction information cache and unprocessed instruction messages. If there is an uncompleted rule change message, the newly received rule change message is added to a to-be-sent queue and queued in the order of reception to ensure that the PTRCE only processes one rule change message at the same time, avoiding version switching confusion caused by parallel rule changes.

[0104] The PTRCE continuously receives the instruction messages forwarded by the DDR while processing the rule change messages, performs risk control computation according to the currently effective rule (initial rule or switched new rule), and synchronously caches the instruction messages to the historical transaction information cache to reserve data for possible future rule change re-computation.

[0105] When the PTRCE completes the recalculation task corresponding to the rule change, a rule recalculation completion message is fed back to the DDR. After receiving the feedback, the DDR immediately sends a rule version switching instruction to the PTRCE. After blocking and waiting for all the processing instruction messages to be calculated, the PTRCE completes the version switching of the new and old rules, releases the original rule calculation thread resources, and the subsequent received instruction messages are executed according to the new rule.

[0106] Finally, after the rule version switching is completed, the DDR extracts the next queued rule change message from the to-be-sent queue, and repeats the above-mentioned message sending, recalculation, feedback and switching process to form a multi-round ordered closed loop of rule change. In the whole process, through the repeated message discarding, rule change queuing, version switching synchronization and other mechanisms, the efficient use of system resources is guaranteed, and the real-time effectiveness of rule change and the consistency of risk control calculation results are ensured.

[0107] It should be noted that the above examples are only used to understand the present application and do not constitute a limitation on the rule switching method of the present application. More forms of simple changes based on this technical concept are within the protection scope of the present application.

[0108] The present application also provides a rule switching device, please refer to Figure 8 , the rule switching is applied to a risk control calculation engine, and the rule switching device comprises:

[0109] The recalculation module 10 is configured to receive the to-be-processed information sent by the data distribution route, recalculate the historical transaction information cache based on the to-be-processed information, obtain a recalculation result, and send the recalculation result to the data distribution route.

[0110] The switching module 20 is configured to receive the version switching instruction sent by the data distribution route, perform rule switching on the core calculation rule of the risk control calculation engine based on the version switching instruction, and obtain a switching result.

[0111] The rule switching device provided by the present application adopts the rule switching method in the above-mentioned embodiments, and can solve the technical problem that the existing technology has high delay and blocks the processing of subsequent business instructions, and cannot realize real-time rule change in the management compliance risk control. Compared with the prior art, the rule switching device provided by the present application has the same beneficial effects as the rule switching method provided by the above-mentioned embodiments, and other technical features in the rule switching device are the same as the features disclosed in the above-mentioned embodiments, which will not be repeated here.

[0112] The application provides a rule switching device, which comprises at least one processor and a memory connected with the at least one processor; the memory stores instructions executable 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 rule switching method in the above embodiment one.

[0113] Reference will now be made to the drawings Figure 9 , which show structural diagrams of a rule switching device suitable for implementing embodiments of the application. The rule switching device in the embodiments of the application can include, but is not limited to, mobile terminals such as mobile phones, notebook computers, digital broadcast receivers, PDAs (Personal Digital Assistant), PADs (Portable Application Description), PMPs (Portable Media Player), vehicle-mounted terminals (for example, vehicle-mounted navigation terminals), and the like, and fixed terminals such as digital TVs, desktop computers, and the like. Figure 9 The rule switching device shown is merely an example and should not impose any limitation on the functions and use range of the embodiments of the application.

[0114] As shown in Figure 9 , the rule switching device can include a processing apparatus 1001 (for example, a central processor, a graphic processor, or the like) that can perform various appropriate actions and processes according to programs stored in a read-only memory 1002 or loaded from a storage apparatus 1003 into a random access memory 1004. Various programs and data required for operation of the rule switching device are also stored in the random access memory 1004. The processing apparatus 1001, the read-only memory 1002, and the random access memory 1004 are connected to each other through a bus 1005. An input / output interface 1006 is also connected to the bus. Generally, the following systems can be connected to the input / output interface 1006: input apparatuses 1007 including, for example, a touch screen, a touch pad, a keyboard, a mouse, an image sensor, a microphone, an accelerometer, a gyroscope, and the like; output apparatuses 1008 including, for example, a liquid crystal display (LCD), a speaker, a vibrator, and the like; the storage apparatus 1003 including, for example, a magnetic tape, a hard disk, and the like; and a communication apparatus 1009. The communication apparatus 1009 can allow the rule switching device to perform wireless or wired communication with other devices to exchange data. Although the rule switching device having various systems is shown in the drawing, it should be understood that all the systems shown are not required to be implemented or provided. More or fewer systems can be alternatively implemented or provided.

[0115] In particular, the processes described above with reference to the flow charts can be implemented as computer software programs in accordance with the embodiments disclosed herein. For example, embodiments disclosed herein include a computer program product comprising a computer program carried on a computer readable medium, the computer program comprising program code for performing the methods illustrated by the flow charts. In such embodiments, the computer program can be downloaded and installed from a network via a communication device, or installed from a storage device 1003, or installed from a read only memory 1002. When the computer program is executed by the processing device 1001, the above-mentioned functions defined in the methods of the embodiments disclosed herein are performed.

[0116] The rule switching device provided by the present application adopts the rule switching method in the above embodiments, and can solve the technical problem that the existing technology has high delay and blocks subsequent business instruction processing, and cannot realize real-time rule change in the fund management compliance risk control. Compared with the prior art, the fund management compliance risk control device provided by the present application has the beneficial effects of the fund management compliance risk control method provided by the above embodiments, and other technical features in the fund management compliance risk control device are the same as those disclosed in the above embodiment, which will not be repeated here.

[0117] It should be understood that various parts of the present application can be realized by hardware, software, firmware or a combination thereof. In the description of the above embodiments, specific features, structures, materials or characteristics can be combined in any appropriate manner in any one or more embodiments or examples.

[0118] The above is merely specific implementation of the present application, but the protection scope of the present application is not limited thereto, and any person skilled in the art can easily think of changes or replacements within the technical scope disclosed by the present application, which should be covered by the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

[0119] The present application provides a computer readable storage medium having stored thereon computer readable program instructions (i.e. computer program) for performing the fund management compliance risk control method in the above embodiments.

[0120] The computer readable storage medium provided in the application may be, for example, a U disk, but is not limited to an electric, magnetic, optical, electromagnetic, infrared, or semiconductor system or device, or any combination of the above. More specific examples of the computer readable storage medium may include, but are not limited to, an electric connection with one or more conductive wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the embodiment, the computer readable storage medium may be any tangible medium containing or storing a program that can be used by or in combination with an instruction execution system or device. The program code contained on the computer readable storage medium can be transmitted by any suitable medium, including but not limited to an electric wire, an optical cable, an RF (Radio Frequency), and the like, or any suitable combination of the above.

[0121] The computer readable storage medium described above may be included in the asset management compliance risk control device, and the existing technology has high latency and blocks subsequent business instruction processing, and cannot realize the real-time rule change device contained in the asset management compliance risk control device. It may also exist independently without being assembled into the asset management compliance risk control device, and the existing technology has high latency and blocks subsequent business instruction processing, and cannot realize the real-time rule change device.

[0122] The computer readable storage medium described above carries one or more programs, when the one or more programs are executed by the asset management compliance risk control device, the existing technology has high latency and blocks subsequent business instruction processing, and cannot realize the real-time rule change device, so that the asset management compliance risk control device, the existing technology has high latency and blocks subsequent business instruction processing, and cannot realize the real-time rule change device: receiving the to-be-processed information sent by the data distribution route, recalculating the historical transaction information cache based on the to-be-processed information, obtaining the recalculation result, and sending the recalculation result to the data distribution route; receiving the version switching instruction sent by the data distribution route, performing rule switching on the core calculation rules of the risk control calculation engine based on the version switching instruction, and obtaining the switching result.

[0123] Computer program code for carrying out operations of the present application can be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C++ or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code can execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer can be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection can be made to an external computer (for example, through the Internet using an Internet Service Provider).

[0124] The flow diagrams and the block diagrams in the drawings are illustrations of architectures, functionalities, and operations of possible implementations of systems, methods, and computer program products according to various embodiments of the present application. In this regard, each block in the flow diagrams or block diagrams can represent a module, a segment, or a portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that in some alternative implementations, the functions noted in the blocks can occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently or the blocks may

[0125] The modules involved in the embodiments of the present application can be implemented in the form of software or in the form of hardware. In some cases, the name of the module does not constitute a limitation on the module itself.

[0126] The readable storage medium provided by the present application is a computer readable storage medium, which stores computer readable program instructions (i.e., a computer program) for executing the above-mentioned rule switching method, and can solve the technical problems of high latency and blocking of subsequent business instruction processing in the asset management compliance risk control, and cannot realize real-time rule change. Compared with the prior art, the computer readable storage medium provided by the present application has the same beneficial effects as the rule switching method provided by the above-mentioned embodiments, and will not be described here.

[0127] The application also provides a computer program product comprising a computer program which, when executed by a processor, implements the steps of the rule switching method as described above.

[0128] The computer program product provided by the application can solve the technical problem that the existing technology has high latency and blocks subsequent business instruction processing, and cannot realize real-time rule change in asset management compliance risk control. Compared with the prior art, the beneficial effects of the computer program product provided by the application are the same as those of the rule switching method provided by the above-mentioned embodiments, and will not be repeated here.

[0129] The above only describes some embodiments of the application, and does not limit the patent scope of the application. Any equivalent structural transformation, direct / indirect application in other related technical fields, or direct / indirect application in other related technical fields based on the technical concept of the application and the content of the specification and drawings are included in the patent protection scope of the application.

Claims

1. A method of rule switching, characterized by, The rule switching method is applied to a risk control computing engine, and the rule switching method comprises: Receiving information to be processed sent by a data distribution route, recalculating a historical transaction information cache based on the information to be processed to obtain a recalculated result, and sending the recalculated result to the data distribution route; The step of recalculating the historical transaction information cache based on the information to be processed to obtain a recalculated result comprises: Calculating transaction information in the information to be processed by an initial rule to obtain a calculation result, and storing the calculation result in the historical transaction information cache; In the case that there is rule change information in the information to be processed, a new rule calculation thread is constructed by using the rule change information; The recalculated result is obtained by calculating the unprocessed transaction information in the information to be processed and the historical transaction information cache by using the new rule calculation thread; Receiving a version switching instruction sent by the data distribution route, switching the core calculation rule of the risk control computing engine based on the version switching instruction to obtain a switching result; The step of switching the core calculation rule of the risk control computing engine based on the version switching instruction to obtain a switching result comprises: Adjusting the engine state of the risk control computing engine to a blocking state, and counting the transaction tasks of the new rule calculation thread and the initial rule calculation thread corresponding to the initial rule to obtain a to-be-completed task amount; Detecting the completion state of the new rule calculation thread and the initial rule calculation thread based on the to-be-completed task amount; When the new rule calculation thread and the initial rule calculation thread complete the to-be-completed task amount, switching the calculation interface to the new rule calculation thread; In the case that the interface switching is completed, switching the core calculation rule based on the rule change information to obtain a switching result.

2. The rule switching method of claim 1, wherein, The step of constructing a new rule calculation thread by using the rule change information comprises: Analyzing the rule change information to obtain a new rule logic parameter, a new rule identifier, and resource requirements; Creating an initial new rule calculation thread based on the new rule identifier, and configuring a calculation resource to the initial new rule calculation thread based on the resource requirements; Loading a risk control logic corresponding to the new rule logic parameter to the initial new rule calculation thread, and initializing a thread calculation environment to obtain a new rule calculation thread.

3. A method of rule switching, characterized by, The rule switching method is applied to a data distribution route, and the rule switching method comprises: Sending rule change information to a risk control computing engine, recalculating a historical transaction information cache based on the rule change information by the risk control computing engine to obtain a recalculated result, and sending the recalculated result to the data distribution route; The step of recalculating the historical transaction information cache based on the rule change information by the risk control computing engine to obtain a recalculated result comprises: Calculating transaction information in the information to be processed by an initial rule by the risk control computing engine to obtain a calculation result, and storing the calculation result in the historical transaction information cache; In the case that the rule change information exists in the to-be-processed information, the risk control computing engine constructs a new rule computing thread through the rule change information; The risk control computing engine performs computing on the unprocessed transaction information in the to-be-processed information and the historical transaction information cache through the new rule computing thread, to obtain a recalculation result; The risk control computing engine sends a rule version switching instruction, and performs rule switching on the core computing rule of the risk control computing engine based on the version switching instruction, to obtain a switching result; The step of performing rule switching on the core computing rule of the risk control computing engine based on the version switching instruction, to obtain a switching result, includes: The risk control computing engine adjusts the engine state of the risk control computing engine to a blocking state, and performs transaction task statistics on the new rule computing thread and the initial rule computing thread corresponding to the initial rule, to obtain a to-be-completed task amount; Based on the to-be-completed task amount, the risk control computing engine performs completion state detection on the new rule computing thread and the initial rule computing thread; When the new rule computing thread and the initial rule computing thread complete the to-be-completed task amount, the risk control computing engine switches the computing interface to the new rule computing thread; In the case that the interface switching is completed, the risk control computing engine performs rule switching on the core computing rule through the rule change information, to obtain a switching result.

4. The method of claim 3, wherein the rule switching is performed when the number of the received packets is equal to or greater than a predetermined number. After the step of sending a rule version switching instruction to the risk control computing engine, the method further includes: Receiving second rule change information; Detecting the processing information sent by the risk control computing engine; If the switching result sent by the risk control computing engine is not detected, the second rule change information is sent to a waiting queue; If the switching result sent by the risk control computing engine is detected, the second rule change information is sent to the risk control computing engine.

5. A rule switching device, characterized by, The rule switching device is applied to a risk control computing engine, and includes: A recalculation module configured to receive to-be-processed information sent by a data distribution route, perform recalculation on a historical transaction information cache based on the to-be-processed information, obtain a recalculation result, and send the recalculation result to the data distribution route; The recalculation module is further configured to perform computing on transaction information in the to-be-processed information through an initial rule, obtain a computing result, and store the computing result in the historical transaction information cache; In the case that the rule change information exists in the to-be-processed information, a new rule computing thread is constructed through the rule change information; The new rule computing thread is used to perform computing on unprocessed transaction information in the to-be-processed information and the historical transaction information cache, to obtain a recalculation result; A switching module configured to receive a version switching instruction sent by the data distribution route, perform rule switching on a core computing rule of the risk control computing engine based on the version switching instruction, and obtain a switching result; The switching module is further configured to switch the core computing rules of the risk control computing engine based on the version switching instruction, and the step of obtaining the switching result comprises: adjusting the engine state of the risk control computing engine to a blocking state, and counting the transaction tasks of the new rule computing thread and the initial rule computing thread corresponding to the initial rules to obtain a to-be-completed task amount; detecting the completion state of the new rule computing thread and the initial rule computing thread based on the to-be-completed task amount; when the new rule computing thread and the initial rule computing thread complete the to-be-completed task amount, switching the computing interface to the new rule computing thread; in the case of interface switching completion, switching the core computing rules based on the rule change information to obtain a switching result.

6. A rule switching device, characterized by, The device comprises a memory, a processor, and a computer program stored on the memory and executable on the processor, and the computer program is configured to implement the steps of the rule switching method according to any one of claims 1 to 4.

7. A storage medium, characterized by The storage medium is a computer readable storage medium, and the storage medium stores a computer program. The computer program is executed by the processor to implement the steps of the rule switching method according to any one of claims 1 to 4.

8. A computer program product, characterised in that, The computer program product comprises a computer program. The computer program is executed by the processor to implement the steps of the rule switching method according to any one of claims 1 to 4.

Images