Business processing method, device, electronic device and storage medium

Abstract

The embodiment of the present invention provides a business processing method, device, electronic device and storage medium, the method comprising: when a business event is intercepted, obtaining an initial event message matching the business event from a message queue, preprocessing it to obtain a standard event message message; extracting a target policy rule and a target policy action matching the message from a cache; instantiating the matching rule event to obtain a rule instance; after verifying that the judgment formula in the rule instance is established, instantiating the action to obtain an action instance and executing it to complete the business processing for the business event. Through a data-driven policy engine, online orchestration and intelligent matching of scenario strategies are realized, and high-throughput, low-latency generalized policy matching of business scenarios is quickly supported. Through interaction in the form of message queues, the business processing party and the receiving party are loosely coupled, and full-process tracking and analysis of message data are realized, and timely warning and push are carried out, which greatly improves the efficiency and accuracy of business event processing.

Description

Technical Field

[0001] The present invention relates to the field of big data processing technology, and in particular to a business processing method, a business processing device, an electronic device and a computer-readable storage medium. Background Art

[0002] Business processing depends on the policy engine. The current policy engine is based on the traditional http (hypertext transfer protocol) protocol + oracle (oracle database, relational database management system). The event source system loads configuration data in oracle through http protocol calls to trigger policy matching.

[0003] However, with the increase in scenarios and the surge in business volume, and the concentration of traffic in some business scenarios in a certain period of time, the disadvantages of existing technologies have become increasingly prominent: it is impossible to achieve peak shaving, and when the business surges in a certain period of time, the performance of the entire system will drop sharply, and the client needs to wait for the server to respond, and the client blocks resources, resulting in low utilization. Summary of the invention

[0004] In view of the above problems, embodiments of the present invention are proposed to provide a service processing method that overcomes the above problems or at least partially solves the above problems.

[0005] The embodiment of the present invention also provides a service processing device, an electronic device and a storage medium to ensure the implementation of the above method.

[0006] In order to solve the above problem, an embodiment of the present invention discloses a business processing method, which is applied to a policy platform, wherein the policy platform includes a message queue and a policy group engine, and a cache of the policy group engine stores multiple policies. The method includes:

[0007] When a service event is intercepted, an initial event message matching the service event is obtained from the message queue, and the initial event message is pre-processed to obtain a standard event message packet;

[0008] Extracting a target policy matching the standard event message from the cache; the target policy includes a target policy rule and a target policy action;

[0009] Using the standard event message, instantiating the target policy rule to obtain a target policy rule instance;

[0010] Verify whether the judgment formula in the target policy rule instance is established;

[0011] If the judgment formula is established, the target policy action is instantiated using the standard event message to obtain a target policy action instance;

[0012] The target policy action instance is executed to complete the business processing for the business event.

[0013] Optionally, the standard event message includes a service event identifier, and the multiple strategies respectively have corresponding scenario identifiers; and extracting a target strategy matching the standard event message from the cache includes:

[0014] Retrieving a target scenario identifier matching the business event identifier from the cache;

[0015] A target policy corresponding to the target scenario identifier is extracted from the cache.

[0016] Optionally, the adopting the standard event message to instantiate the target policy rule to obtain a target policy rule instance includes:

[0017] The data in the standard event message is filled in and replaces the rule parameters in the target policy rule to obtain a target policy rule instance.

[0018] Optionally, the adopting the standard event message to instantiate the target policy action to obtain the target policy action instance includes:

[0019] The data in the standard event message is filled in and replaces the action parameters in the target policy action to obtain a target policy action instance.

[0020] Optionally, the preprocessing the initial event message to obtain a standard event message message includes:

[0021] Performing data conversion on the initial event message to obtain a first event message; the data conversion includes data format conversion, message conversion and data type conversion;

[0022] Retrieving a portrait tag matching the first event message, and writing the portrait tag into the first event message to obtain a second event message;

[0023] The second event message is encapsulated according to a standard format of a business event message to obtain a standard event message message.

[0024] Optionally, executing the target policy action instance to complete business processing for the business event includes:

[0025] Determining the execution type of the target policy action instance;

[0026] If the execution type is a message push type, the target policy action instance is pushed to the message queue so that the corresponding business execution system can extract the target policy action instance from the message queue and execute the business action in the target policy action instance to complete the business processing for the business event.

[0027] Optionally, executing the target policy action instance to complete business processing for the business event includes:

[0028] Determining the execution type of the target policy action instance;

[0029] If the execution type is a capability scheduling type, extracting an application programming interface API address from the target policy action instance;

[0030] The target policy action instance is input with an API interface based on the API address to call a corresponding business execution system to execute the business action in the target policy action instance to complete business processing for the business event.

[0031] The embodiment of the present invention further discloses a service processing device, which is applied to a policy platform. The policy platform includes a message queue and a policy group engine. The cache of the policy group engine stores multiple policies. The device includes:

[0032] An initial event message preprocessing module, used for obtaining an initial event message matching the business event from the message queue when a business event is intercepted, and preprocessing the initial event message to obtain a standard event message packet;

[0033] A target policy extraction module, used to extract a target policy matching the standard event message from the cache; the target policy includes a target policy rule and a target policy action;

[0034] A rule instantiation module, used to instantiate the target policy rule using the standard event message to obtain a target policy rule instance;

[0035] A judgment formula verification module, used to verify whether the judgment formula in the target policy rule instance is established;

[0036] An action instantiation module, used for instantiating the target policy action using the standard event message if the judgment formula is established, to obtain a target policy action instance;

[0037] The business processing module is used to execute the target policy action instance to complete the business processing for the business event.

[0038] Optionally, the standard event message includes a service event identifier, and the multiple strategies respectively have corresponding scenario identifiers; and the target strategy extraction module includes:

[0039] A target scene identifier retrieval submodule, used to retrieve a target scene identifier matching the business event identifier from the cache;

[0040] The target policy extraction submodule is used to extract the target policy corresponding to the target scenario identifier from the cache.

[0041] Optionally, the rule instantiation module includes:

[0042] The rule instantiation submodule is used to fill the data in the standard event message and replace the rule parameters in the target policy rule to obtain a target policy rule instance.

[0043] Optionally, the action instantiation module includes:

[0044] The action instantiation submodule is used to fill the data in the standard event message and replace the action parameters in the target policy action to obtain a target policy action instance.

[0045] Optionally, the initial event message preprocessing module includes:

[0046] A data conversion submodule, used to perform data conversion on the initial event message to obtain a first event message; the data conversion includes data format conversion, message conversion and data type conversion;

[0047] A portrait tag writing submodule, used for retrieving a portrait tag matching the first event message, and writing the portrait tag into the first event message to obtain a second event message;

[0048] The encapsulation submodule is used to encapsulate the second event message according to the standard format of the business event message to obtain a standard event message message.

[0049] Optionally, the business processing module includes:

[0050] A first execution type determination submodule, used to determine the execution type of the target policy action instance;

[0051] The message push submodule is used to push the target policy action instance to the message queue if the execution type is the message push type, so that the corresponding business execution system can extract the target policy action instance from the message queue and execute the business action in the target policy action instance to complete the business processing for the business event.

[0052] Optionally, the business processing module includes:

[0053] A second execution type determination submodule, used to determine the execution type of the target policy action instance;

[0054] An API address extraction submodule, configured to extract an application programming interface API address from the target policy action instance if the execution type is a capability scheduling type;

[0055] The capability scheduling submodule is used to input the target policy action instance into an API interface based on the API address to call the corresponding business execution system to execute the business action in the target policy action instance to complete the business processing for the business event.

[0056] The embodiment of the present invention further discloses an electronic device, comprising a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory communicate with each other via the communication bus;

[0057] The memory is used to store computer programs;

[0058] The processor is used to implement the service processing method described in the embodiment of the present invention when executing the program stored in the memory.

[0059] The embodiment of the present invention further discloses one or more computer-readable media on which instructions are stored, and when executed by one or more processors, the processors execute the business processing method as described in the embodiment of the present invention.

[0060] Compared with the prior art, the embodiments of the present invention have the following advantages:

[0061] In an embodiment of the present invention, when a business event is intercepted, an initial event message matching the business event is obtained from a message queue, and the initial event message is preprocessed to obtain a standard event message message; a target policy matching the standard event message message is extracted from a cache; the target policy includes a target policy rule and a target policy action; the target policy rule is instantiated using a standard event message message to obtain a target policy rule instance; whether the judgment formula in the target policy rule instance is established is verified; if the judgment formula is established, the target policy action is instantiated using a standard event message message to obtain a target policy action instance; the target policy action instance is executed to complete the business processing for the business event. The embodiment of the present invention realizes online orchestration and intelligent matching of scenario strategies through a data-driven strategy engine, quickly supports high-throughput, low-latency generalized strategy matching for business scenarios, and interacts through a message queue, so that the business processing party and the receiving party are loosely coupled, and the full process tracking and analysis of message data is realized, and timely warning and push are carried out, which greatly improves the efficiency and accuracy of business event processing. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0063] Figure 1 is a flowchart of a business processing method provided by an embodiment of the present invention;

[0064] Figure 2 This is a general architecture diagram of a data-driven strategy engine provided by an embodiment of the present invention;

[0065] Figure 3 is a schematic diagram of a policy data chain provided by an embodiment of the present invention;

[0066] Figure 4 This is a schematic diagram of the data perception capability of the lake-warehouse integration provided by an embodiment of the present invention;

[0067] Figure 5 is a schematic diagram of a visual orchestration strategy engine provided by an embodiment of the present invention;

[0068] Figure 6 It is a diagram of the operation mechanism of the strategy group algorithm engine provided by an embodiment of the present invention;

[0069] Figure 7 It is a schematic diagram of the policy arrangement process provided by an embodiment of the present invention;

[0070] Figure 8Schematic diagram of a large-area fault warning scenario of a network device provided by an embodiment of the present invention;

[0071] Fig. 9 It is a structural block diagram of a service processing device provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0072] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0073] Reference Figure 1 , shows a flow chart of steps of a business processing method provided by an embodiment of the present invention, which is applied to a policy platform, the policy platform includes a message queue and a policy group engine, the cache of the policy group engine stores multiple policies, and the method may specifically include the following steps:

[0074] Step 101: when a service event is intercepted, an initial event message matching the service event is obtained from the message queue, and the initial event message is pre-processed to obtain a standard event message packet.

[0075] In an embodiment of the present invention, it can be applied to a policy platform, which may include a message queue and a policy group engine, wherein a cache of the policy group engine stores multiple policies, which are pre-configured by professional technicians in a visual orchestration interface and stored in the cache.

[0076] Among them, the message queue can be KAFKA (open source stream processing platform), which is a high-throughput distributed publish-subscribe message system that can process all action stream data of users on the website, which is a key factor in many social functions on the modern network. These data are usually solved by processing logs and log aggregation due to throughput requirements. The purpose of KAFKA is to unify online and offline message processing through Hadoop's parallel loading mechanism, and to provide real-time messages through clusters.

[0077] Among them, the policy group engine realizes rule calculation and logical inference through the triggering of real-time message queue event source, policy rule calculation and policy action execution scheduling of Druid Sql Parser component.

[0078] Reference Figure 2, shows the overall architecture diagram of the data-driven policy engine provided by the embodiment of the present invention, which includes data production, data perception, message center, policy engine, rule configuration, DCOOS capability exposure platform, message notification, action execution and other modules. Through architectural innovation, the embodiment of the present invention can realize a new generation of data-driven architecture, quickly discover problems through global data perception, and build a policy group engine to enable enterprises to automatically and efficiently handle problems; through the accumulation of knowledge and experience, and self-learning, it can realize the optimization of enterprise processes and the empowerment of production operations.

[0079] Among them, data production and data perception can be used as event collection tools. Event collection tools can be used to listen to and identify business events. The message queue of the event center is configured with different types of initial event messages for subsequent data preprocessing.

[0080] When a business event is intercepted, the initial event message matching the business event can be obtained from the message queue. Specifically, the event collection tool can identify the message type of the business event, use the message type = "initial event message" as the extraction judgment logic, and obtain the initial event message that meets the business requirements from the message queue.

[0081] After obtaining the initial event message that matches the business event, the initial event message needs to be preprocessed to obtain a standard event message packet, thereby processing the data into an event with business information.

[0082] In order to facilitate understanding of the overall process of the embodiment of the present invention, the policy data chain and policy engine of the embodiment of the present invention are first introduced:

[0083] Reference Figure 3 , showing a schematic diagram of a policy data chain provided by an embodiment of the present invention. The policy data chain is a policy tree that abstracts six elements, namely, policy classification, policy characteristics, policy owners, policy rules, policy processes, and policy actions, based on the precipitation of a large number of scenario instances.

[0084] The six elements of the strategy are as follows:

[0085] ① Strategy classification: business classification based on the operational management attributes of the strategy, such as network operation, customer service, management, etc.

[0086] ② Policy characteristics: refers to the identification of characteristic attributes of the policy, such as object characteristics, business characteristics, etc.

[0087] ③Strategy owner: refers to the division of responsibilities related to the operation, management or maintenance of the strategy;

[0088] ④ Strategy rules: including driving rules, filtering rules, evaluation criteria and other rules of the strategy;

[0089] ⑤ Strategy process: a flow chart of a series of strategy actions formed according to various logical rules and conditions;

[0090] ⑥ Strategic actions: operational behaviors and corresponding business content oriented to business objects.

[0091] The embodiment of the present invention forms a logical structure by combining the production and operation management attributes of the enterprise, and the six-element system of the strategy tree can well support the dynamic management of global operation scenario strategy instances.

[0092] The policy engine can be explained from three aspects: lake-warehouse integrated data perception, visual orchestration policy engine, and policy group algorithm engine:

[0093] Reference Figure 4 , shows a schematic diagram of the data perception capability of the lake-warehouse integration provided by an embodiment of the present invention. The data perception of the lake-warehouse integration is based on a standardized, logically related and labeled real-time aggregated data structure. The time series computing engine performs data perception calculations, and the policy parsing computing engine performs business policy parsing calculations to realize the data-driven engine capability based on the time series. The details are as follows:

[0094] ① Real-time data aggregation: The data lake enables real-time aggregation of BMO's global data. For example, data sources A, B, and C are all aggregated into a batch-stream computing framework, thereby building a standardized, logically relational, and data-labeled basic data structure.

[0095] ②Time series data computing engine: Based on TSDB time series data storage and stream processing computing engine, it is triggered by time index based on time series to achieve real-time computing based on event sequence;

[0096] ③Business policy analysis engine: includes event triggering, rule calculation, policy matching and other full-process policy analysis and calculation capabilities related to actual business applications.

[0097] Reference Figure 5 , shows a schematic diagram of a visual orchestration strategy engine provided by an embodiment of the present invention. The visual orchestration strategy engine is deployed in a Pass platform elastic container and uses a Druid SQLParser component. The Druid SQLParser component can be used for SQL statement parsing and rule judgment, and provides two major capabilities: strategy matching (message generation) and message interaction (message push / recovery). The details are as follows:

[0098] ① Policy rule configuration: The front end implements visual arrangement of policy rules based on JS Plumb and Query Builder;

[0099] ② Strategy matching calculation: The backend running state pulls "micro-batch data" from the message queue, builds an in-memory data table, performs strategy rule matching calculation based on the Druid SQLParser component, and generates new messages for those that meet the conditions;

[0100] ③Strategy model: multi-level strategy scaling execution;

[0101] ④Message interaction: Active message push and execution result recovery are completed through the message queue, which is highly coupled and efficient.

[0102] Reference Figure 6 , shows a diagram of the operation mechanism of the strategy group algorithm engine provided by an embodiment of the present invention, and the operation mechanism of the strategy group algorithm engine is specifically as follows:

[0103] ① Message access: Real-time monitoring to obtain the message queue event source trigger message, and perform data analysis, format adaptation and label supplement data collection for the message to form the message instance data (memory data table) required to support the policy calculation engine;

[0104] ② Strategy rule calculation: Scan the cache (CTG-Cache) to obtain the corresponding strategy rule information (SQL rule statements) according to the event scenario, use the open source Druid Sql Parser component to perform SQL rule statement calculation on the message instance memory data table, and call the corresponding strategy action execution according to the calculation results;

[0105] ③ Policy action execution scheduling: According to the execution rule configuration requirements, the relevant policy action execution requirements are pushed to the corresponding business execution system through message push or capability scheduling for business action execution.

[0106] In an optional embodiment of the present invention, step 101 may include the following sub-steps:

[0107] Sub-step S11, performing data conversion on the initial event message to obtain a first event message; the data conversion includes data format conversion, message conversion and data type conversion;

[0108] Sub-step S12, retrieving a portrait tag matching the first event message, and writing the portrait tag into the first event message to obtain a second event message;

[0109] Sub-step S13, encapsulating the second event message according to the standard format of the business event message to obtain a standard event message message.

[0110] The initial event message is preprocessed to obtain a standard event message packet, which is formed by performing message conversion, message enhancement and message encapsulation on the initial event message to form a final standardized event message packet.

[0111] In the specific implementation, message conversion is performed first, specifically, the obtained initial event message is standardized and converted to comply with the standardized message specifications, including but not limited to data format standardization, message structure standardization, data content standardization, etc., that is, data format conversion, message conversion, data type conversion and other data conversion actions are performed on the initial event message, thereby obtaining the first event message.

[0112] Then the message is enhanced, specifically by connecting the tag library, data lake and other data middle platforms, and retrieving and obtaining the portrait tags related to the first event message through the open data interface. The portrait tags are used to characterize user characteristics, such as how much impact the business event has on the user. The portrait tags are then written into the first event message to enrich the message content, thereby obtaining the second event message.

[0113] Finally, the message is encapsulated, specifically, the second event message is encapsulated according to the standard format of the business event message to form a standard event message message, thereby completing the business processing of the collection link. Among them, the standard event message message may include the event message serial number, business event identifier, event message content (collection item code, collection item value) and event name, etc.

[0114] Step 102: extracting a target policy matching the standard event message from the cache; the target policy includes a target policy rule and a target policy action.

[0115] After obtaining the standard event message, the corresponding target policy may be extracted from the cache based on the standard event message, wherein the target policy may include a target policy rule and a target policy action.

[0116] It should be noted that the strategies of the embodiments of the present invention are all configured in advance by professional technicians in the visual orchestration interface and stored in the cache. Specifically, the embodiments of the present invention provide a visual orchestration strategy engine, which is based on JS Plumb and QueryBuilder to implement visual orchestration of strategies, and Druid SQL Parser components to perform strategy matching calculations, and overall provides two major capabilities: strategy matching (message generation) and message interaction (message push / recovery).

[0117] Reference Figure 7 , shows a schematic diagram of the policy orchestration process provided by an embodiment of the present invention. The front end can orchestrate message flow rules, business action execution rules, etc. by visually dragging the canvas to form a policy execution process for the scenario. The back end can abstract the execution points of message flow conditions / business actions into node components, which can be distinguished by type as conditional nodes and execution nodes, and support different node configurations to form different policies, as follows:

[0118] ①Node type: condition node + business action execution node;

[0119] ② Condition node: configure the conditions for message flow between nodes. For example, {fault level} = level 4 and {impact scale}>1000, {execution result} = restart success;

[0120] ③Execution node: configure the execution action code, execution time limit, speech script and other policy information for the execution of business actions.

[0121] After arranging the policies, you can build a policy model based on multi-level policies, as follows:

[0122] ① Simple strategy rules are constructed based on the combination of rule elements, and multiple rule combinations are constructed into multi-level strategies;

[0123] ② Based on complex real-world business, it is decomposed into two system atomic structures: simple strategy and rule elements to describe the strategy rules, and multi-level expansion is used to describe the display business rules.

[0124] In an optional embodiment of the present invention, the standard event message includes a service event identifier, and the multiple strategies respectively have corresponding scenario identifiers; step 102 may include the following sub-steps:

[0125] Sub-step S21, retrieving a target scenario identifier matching the business event identifier from the cache;

[0126] Sub-step S22, extracting the target policy corresponding to the target scenario identifier from the cache.

[0127] In an embodiment of the present invention, each strategy has a corresponding application scenario, including but not limited to wired equipment alarms, large-area obstacle warnings, wired high-frequency serious obstacles, wireless base station disconnections, poor quality cell broadcasts, satisfaction predictions, high-incidence complaint scenarios, magic mirror end-to-end alarms and other application scenarios. The embodiment of the present invention can set a corresponding scenario identifier for each strategy in advance, thereby storing multiple strategies and their corresponding scenario identifiers in the cache.

[0128] After obtaining the standard event message, the business event identifier "ev_owe_business_type" can be extracted from the standard event message, and then the corresponding target scene identifier can be retrieved from the cache. For example, assuming that the business event is "wireless base station disconnection", the corresponding target scene identifier of the "wireless base station disconnection" event is "base station disconnection scene ID", so that the scene matching the event can be found through the relationship of "event ID-scene ID".

[0129] After the target scenario identifier is retrieved, the target policy of the corresponding scenario can be extracted from the cache based on the target scenario identifier. For example, after the "base station disconnection scenario ID" is retrieved, the target policy belonging to the scenario of "base station disconnection scenario ID" can be extracted from the cache based on the "base station disconnection scenario ID".

[0130] In the embodiment of the present invention, the target policy includes target policy rules and target policy actions. The target policy rules can be a judgment logic tree composed of AND, OR, NOT, regular expressions, etc. For example, the "base station disconnection policy rule" includes broadcast objects and contact words corresponding to different base station obstacle levels. The target policy action is the business execution action corresponding to each judgment logic tree result, which includes the system for executing the action, the object of the action, the content of the action, etc.

[0131] Step 103: Use the standard event message to instantiate the target policy rule to obtain a target policy rule instance.

[0132] Since the target policy only belongs to the same scenario as the business event, the target policy rules in the target policy are not instantiated for the business event. Therefore, the target policy rules at this time need to be instantiated. The standard event message already contains the specific data of the business event. Therefore, the data in the standard event message can be used to instantiate the target policy rules to form a target policy rule instance for the business event.

[0133] In an optional embodiment of the present invention, step 103 may include the following sub-steps:

[0134] Sub-step S31, filling the data in the standard event message into and replacing the rule parameters in the target policy rule to obtain a target policy rule instance.

[0135] In a specific implementation, the rule parameters are filled and replaced according to the corresponding relationship between the data in the standard event message and the variables in the target policy rule. Exemplarily, the variable placeholders in the "base station disconnection policy rule" are replaced according to the specific data in the standard event message, thereby realizing the instantiation of the "base station disconnection policy rule".

[0136] Step 104: Check whether the judgment formula in the target policy rule instance is established.

[0137] In an embodiment of the present invention, the target policy rule instance is applied to the memory for rule calculation, and the policy corresponding to this instantiation calculation is identified through judgment logic. For example, the "base station disconnection policy rule" after instantiation is relied upon to make a compliance judgment on the specific rule prerequisite, and calculate whether the judgment formula in the "base station disconnection policy rule" matching this standard event message is established.

[0138] Specifically, the data in the standard event message can be introduced into the target policy rule instance for calculation to verify whether the judgment formula in the target policy rule instance is established. If established, the target policy action is called; if not established, the subsequent steps are terminated.

[0139] Step 105: If the judgment formula is established, the target policy action is instantiated using the standard event message to obtain a target policy action instance.

[0140] Since the target policy only belongs to the same scenario as the business event, the target policy action in the target policy is not instantiated for the business event. Therefore, after verifying that the judgment expression in the target policy rule instance is established, the action needs to be instantiated. The standard event message message already contains the specific data of the business event. Therefore, the data in the standard event message message can be used to instantiate the target policy action to form a target policy action instance for the business event.

[0141] In an optional embodiment of the present invention, step 105 may include the following sub-steps:

[0142] Sub-step S41, filling the data in the standard event message and replacing the action parameters in the target policy action to obtain a target policy action instance.

[0143] In the specific implementation, according to the correspondence between the data in the standard event message and the variables in the target policy action, the action parameters are filled and replaced to realize the instantiation of the target policy action and form a target policy action instance that can be pointed to, thereby supporting policy scheduling. Among them, the instantiated policy action can include dispatch contacts, broadcast objects, broadcast content, etc.

[0144] Step 106: execute the target policy action instance to complete the business processing for the business event.

[0145] The target policy action instance is a specific policy action message for a business event, so the target policy action instance is executed to complete the business processing for the business event.

[0146] In an optional embodiment of the present invention, step 106 may include the following sub-steps:

[0147] Sub-step S51, determining the execution type of the target policy action instance;

[0148] Sub-step S52, if the execution type is a message push type, the target policy action instance is pushed to the message queue, so that the corresponding business execution system can extract the target policy action instance from the message queue and execute the business action in the target policy action instance to complete the business processing for the business event.

[0149] In the embodiment of the present invention, the policy actions in the target policy action instance have different execution types, wherein the execution types include message push type and capability scheduling type. Specifically, message push is a process initiated and executed by the current system to push the data of the current system to the target system. After the data is pushed, the target system can use the data to perform a series of business actions. Capability scheduling is a process initiated by the current system, routed through the intermediate platform, and executed by the target system.

[0150] In the embodiment of the present invention, the execution type in the target policy action instance is judged, and if the execution type is a message push type, then the relevant business action of the message push type can be performed. Specifically, for the message push type, the target policy action instance can be pushed to the message queue for the downstream system to extract and consume, and the downstream system executes the relevant business actions by itself, that is, the corresponding business execution system can extract the target policy action instance from the message queue, and then execute the business action in the target policy action instance, thereby completing the business processing for the business event.

[0151] In an optional embodiment of the present invention, step 106 may include the following sub-steps:

[0152] Sub-step S61, determining the execution type of the target policy action instance;

[0153] Sub-step S62, if the execution type is a capability scheduling type, extracting an API address from the target policy action instance;

[0154] Sub-step S63, inputting the target policy action instance into an API interface based on the API address, so as to call the corresponding business execution system to execute the business action in the target policy action instance, so as to complete the business processing for the business event.

[0155] In an embodiment of the present invention, a judgment is made through the execution type in the target policy action instance. If the execution type is a capability scheduling type, then relevant business actions of the capability scheduling type can be performed. Specifically, for the capability scheduling type, the API (Application Programming Interface) address in the target policy action instance can be extracted, and relevant parameters can be filled. Through the third-party capability opening, its API capability is called to complete the execution of the corresponding business action, that is, the API address is extracted from the target policy action instance, and the target policy action instance is input into the API interface based on the API address, and then the corresponding business execution system is called to execute the business action in the target policy action instance, thereby completing the business processing for the business event. Exemplarily, the API address in the instantiated "base station disconnection policy action" is extracted, the API interface specification is adapted, and the instantiated "base station disconnection policy action" is converted into an API interface input parameter to call the API capability to complete the execution of the corresponding business action.

[0156] In addition, after executing the corresponding business action, the execution result can be fed back. Specifically, the standardized action execution interface can be used to support the relevant systems of message push type and the relevant systems of capability scheduling type to feed back the execution result of the policy action.

[0157] In addition, after the execution result is fed back, strategy coordination can be performed. Specifically, based on the standard execution result message fed back, determine whether there are corresponding subsequent coordination strategies for the business actions of the message push type and the business actions of the capability scheduling type. If relevant subsequent coordination strategies are identified, then step 102 can be entered to continue the coordination strategy calculation and subsequent execution steps; if no relevant subsequent coordination strategies are identified, then the entire process can be terminated directly.

[0158] It can be seen that the traditional policy engine cannot achieve peak shaving. When the business surges during a certain period, the performance of the entire system will drop sharply. The embodiment of the present invention can effectively solve this problem. Specifically, the business operation dispatch of the traditional policy engine is mostly scenario-driven, with many monthly and daily dispatch scenarios. At the beginning of each month, the scenario is triggered, and monthly and daily scenario work orders are generated, forming a business peak. The embodiment of the present invention changes the scenario drive to data drive. The work order will not be recycled and updated with the daily and monthly cycle changes of the scenario, but will be updated more according to the changes in data. This greatly reduces the sorting of business work order updates, thereby reducing business peaks.

[0159] It can be seen that in the traditional policy engine, the client needs to wait for the server to respond, and the client blocks resources, resulting in low utilization. The embodiment of the present invention can effectively solve this problem. Specifically, the traditional policy engine adopts the http interface interaction mode, which determines that the entire data flow is limited by the availability of the central http interface service, such as high concurrency blocking, service exceptions, service upgrades, etc., resulting in the inability of the two parties of the message interaction to be loosely coupled, resulting in low utilization of client blocking resources. The embodiment of the present invention adopts the message queue mode of interaction, so that the business processing party and the receiving party are loosely coupled and are not affected by the availability of the event center service.

[0160] In addition, traditional policy engines have some drawbacks: the HTTP protocol uses a question-and-answer mode, with many network handshakes and low efficiency; frequent access to the database to obtain configuration data, which is inefficient; and the inability to prevent data loss when the network or system is unstable.

[0161] In the traditional policy engine, the HTTP protocol is in a question-and-answer mode, and the network handshake times are high and inefficient. The embodiments of the present invention can effectively solve this problem. Specifically, the traditional policy engine adopts the HTTP interface interaction mode, which determines that the event source system must initiate an HTTP interface call interaction request in real time every time after the event message is triggered. For example, each request is responded once. Compared with the message queue interface mode, the HTTP interface interaction mode is much worse in data transmission efficiency. The embodiments of the present invention adopt the message queue mode to push batch messages, such as 1 or 1000 messages, thereby greatly improving the message data transmission efficiency.

[0162] In traditional policy engines, frequent access to the database to obtain configuration data is inefficient. The embodiments of the present invention can effectively solve this problem. Specifically, the traditional policy engine uses direct real-time access to the database to obtain configuration data. The embodiments of the present invention adopt a secondary cache mode: local node memory cache + high-speed cache + specified expiration time, automatically obtaining the latest configuration data from the database, thereby reducing database interactions and improving efficiency.

[0163] In traditional policy engines, it is impossible to prevent data loss when the network or system is unstable. The embodiments of the present invention can effectively solve this problem. Specifically, the embodiments of the present invention use two mechanisms to ensure that: when pushing messages, the push is considered successful only after receiving ACK (Acknowledgement) message confirmation; when parsing messages, the log is recorded first and then the business logic processing is executed. The two mechanisms can ensure that data quality is not lost. Even if data loss occurs, the log records can be automatically audited, monitored and compared, and the alarm re-push mechanism can be automatically triggered.

[0164] In summary, the embodiment of the present invention implements a universal, efficient, and low-latency strategy engine based on a cache (CTG-CACHE), a message queue (KAFKA), and DruidSQLParser, which solves the problems existing in the prior art such as the need for customized development of scenarios, low strategy matching efficiency, and high latency, thereby doubling the event processing capability on the original basis.

[0165] The open source framework JS Plumb and Query Builder are used to implement the front-end drag-and-drop multi-channel collaborative process orchestration of marketing services. At the same time, combined with KAFKA and REDIS, the message queue that pushes data on the production side can be used to track and analyze the entire process of message data, provide timely warnings, and push messages. Error data can be traced and re-pushed.

[0166] The embodiments of the present invention can realize unified configuration, centralized management, and rapid calculation of business events by establishing a data-driven and policy center, greatly improving the configuration access efficiency of business events and event scenarios. The embodiments of the present invention realize the full-process policy orchestration capability of atomization of business capabilities, componentization of policy configuration, process-based scenario orchestration, and activity-based scenario configuration, realize self-service customization and flexible orchestration of business processes, realize guided registration and self-service debugging of marketing touchpoints and touchpoint capabilities, build a standardized touchpoint message interaction system, completely get rid of the messy and disordered status of write-back messages, build the full-process monitoring capability of production operation, and realize the goal of digital monitoring of the full-process of production processes and operational execution links.

[0167] The data-driven engine of the embodiment of the present invention has achieved initial results, and event-driven has actually served production business and achieved significant results, as follows:

[0168] The establishment of the event center has significantly improved the efficiency of event scenario configuration and launch, shortening it from three days to half a day, and unified the processing procedures of existing event scenarios;

[0169] The strategy orchestration and coordination capabilities are combined with the actual needs of the early warning system and based on future business development. The overall improvement of strategy orchestration and coordination capabilities is achieved from multiple aspects such as scenario management, agile orchestration, strategy engine, and effect evaluation. The details are as follows:

[0170] 1) Scenario management: Based on business classification and data classification management and control capabilities, it provides scenario editing and operation management capabilities to ensure that cross-business scenarios are logically independent and do not affect each other;

[0171] 2) Agile orchestration: Based on atomic strategy capabilities, it supports agile orchestration of business scenarios and rapid configuration of operation scenarios;

[0172] 3) Policy engine: The policy engine performs rule calculation and policy matching, opens up global business calls, and realizes cross-domain business collaboration;

[0173] 4) Effect evaluation: Provides process analysis and result evaluation capabilities, supports full-scenario operation monitoring, and achieves scenario strategy optimization and iteration through data analysis.

[0174] In summary, in an embodiment of the present invention, when a business event is intercepted, an initial event message matching the business event is obtained from the message queue, and the initial event message is preprocessed to obtain a standard event message message; a target policy matching the standard event message message is extracted from the cache; the target policy includes a target policy rule and a target policy action; the target policy rule is instantiated using the standard event message message to obtain a target policy rule instance; whether the judgment formula in the target policy rule instance is established is verified; if the judgment formula is established, the target policy action is instantiated using the standard event message message to obtain a target policy action instance; the target policy action instance is executed to complete the business processing for the business event. The embodiment of the present invention realizes online orchestration and intelligent matching of scenario strategies through a data-driven strategy engine, quickly supports high-throughput, low-latency generalized strategy matching for business scenarios, and interacts through message queues, so that the business processing party and the receiving party are loosely coupled, and the full process tracking and analysis of message data is realized, and timely warning and push are carried out, which greatly improves the efficiency and accuracy of business event processing.

[0175] In order to enable those skilled in the art to better understand the embodiments of the present invention, the embodiments of the present invention are described below through the following examples:

[0176] refer to Figure 8 , showing a schematic diagram of a large-area obstacle warning scenario for network equipment provided by an embodiment of the present invention, the large-area obstacle warning scenario for network equipment description: timely notification and early warning of large-area obstacle information caused by wireless base station disconnection, rapid exploration, location, resolution and tracking of equipment problems, thereby achieving prior intervention in possible customer dissatisfaction.

[0177] The specific process of warning for large-scale network equipment failure is as follows:

[0178] Step 1-Message Collection: Detect and identify business events through event collection tools, and obtain the initial event message matching the business event from the cache according to the message type, such as Figure 8 As shown, a large-scale network abnormality complaint event was intercepted by user No. 10,000;

[0179] Step 2-Message conversion: The obtained initial event message is converted into a standardized message to comply with the standardized message specification, including but not limited to data format standardization, message structure standardization, data content standardization, etc., thereby obtaining the converted first event message;

[0180] Step 3-Message Enhancement: Connect the data middle platform such as the tag library and data lake, and retrieve and obtain the portrait tags related to the first event message through the open data interface, such as the impact scope of the business event, and write the portrait tags to the first event message, thereby obtaining the enhanced second event message;

[0181] Step 4-message encapsulation: encapsulate the second event message according to the standard format of the business event message to form a standard event message message, such as Figure 8 As shown, the standard event message includes an event name and event content. The event name is XX equipment failure. The event content includes message 1 and message 2. Message 1 is a list of customers involved in customer network perception anomalies, and message 2 is the ID of the base station with abnormal communication.

[0182] Step 5-Scene Identification: According to the service event identifier in the standard event message, the corresponding target scenario identifier is retrieved from the cache, for example, the base station disconnection scenario ID;

[0183] Step 6-Strategy extraction: According to the target scenario identifier (base station disconnection scenario ID), the target strategy of the corresponding scenario is obtained from the cache, such as Figure 8 As shown, Strategy 1, Strategy 2, Strategy 3 and Strategy 4 are all target strategies for this business event. Strategy 1 and Strategy 2 can be executed in parallel, and Strategy 3 and Strategy 4 can be executed in series.

[0184] The target policy includes target policy rules and target policy actions:

[0185] The target policy rule is a judgment logic tree composed of AND, OR, NOT, regular expressions, etc., including broadcast objects and contact words corresponding to different base station obstacle levels, such as Figure 8 As shown, customer service number 10000, network diagnosis platform, network optimization platform and electronic operation and maintenance platform are all broadcast objects;

[0186] The target policy action is the business execution action corresponding to each judgment logic tree result, including the system that executes the action, the object of the action, the content of the action, etc. Figure 8 As shown, the network diagnosis platform, network optimization platform and electronic operation and maintenance platform are all systems that perform actions, base station No. 237 is the object of the action, and customer service interception, equipment self-checking, automatic recovery and manual operation and maintenance are all the contents of the action;

[0187] Step 7-Rule instantiation: According to the specific data in the standard event message, replace the rule parameters in the "base station disconnection policy rule" to obtain the target policy rule instance, thereby realizing the instantiation of the "base station disconnection policy rule";

[0188] Step 8-strategy rule calculation: relying on the instantiated "base station disconnection strategy rule", make a compliance judgment on the specific rule prerequisites, and calculate whether the judgment formula in the "base station disconnection strategy rule" matching this standard event message is established: if established, call the target strategy action, if not established, terminate the subsequent steps;

[0189] Step 9-Policy action matching: When the judgment formula in the target policy rule instance is established, the action parameters in the "base station disconnection policy action" are replaced according to the data in the standard event message to obtain the target policy action instance, thereby realizing the instantiation of the "base station disconnection policy action";

[0190] Step 10-strategy action execution judgment: judge by the execution type in the instantiated "base station disconnection strategy action": if the execution type is "message push type", execute step 11; if the execution type is "capability scheduling type", execute step 12;

[0191] Step 11-Message push type: Push the instantiated "base station disconnection strategy action" to the message queue for downstream systems to extract, and the downstream system will perform business processing such as SMS sending on its own;

[0192] Step 12 - Capability scheduling type: extract the API address in the instantiated "base station disconnection strategy action", adapt the API interface specification, convert the instantiated "base station disconnection strategy action" into an API interface input parameter, call the API capability, and complete the execution of the corresponding business action;

[0193] Step 13-Execution feedback: Through the standardized action execution interface, the relevant systems or platforms of steps 11 and 12 are supported to provide feedback on the execution results of their policy actions;

[0194] Step 14-Strategy collaboration: Based on the execution result message fed back from step 13, determine whether the corresponding steps 11 and 12 have corresponding subsequent collaboration strategies. If relevant subsequent collaboration strategies are identified, proceed to step 6 to continue the collaboration strategy calculation and subsequent execution steps; if no relevant subsequent collaboration strategies are identified, end the entire process.

[0195] refer to Fig. 9 , shows a structural block diagram of a service processing device provided by an embodiment of the present invention, which is applied to a policy platform, wherein the policy platform includes a message queue and a policy group engine, wherein a cache of the policy group engine stores multiple policies, and specifically includes the following modules:

[0196] The initial event message preprocessing module 901 is used to obtain the initial event message matching the business event from the message queue when a business event is intercepted, and preprocess the initial event message to obtain a standard event message message;

[0197] A target policy extraction module 902 is used to extract a target policy matching the standard event message from the cache; the target policy includes a target policy rule and a target policy action;

[0198] A rule instantiation module 903, configured to instantiate the target policy rule using the standard event message to obtain a target policy rule instance;

[0199] A judgment formula verification module 904 is used to verify whether the judgment formula in the target policy rule instance is established;

[0200] The action instantiation module 905 is used to instantiate the target policy action using the standard event message to obtain a target policy action instance if the judgment formula is established;

[0201] The business processing module 906 is used to execute the target policy action instance to complete the business processing for the business event.

[0202] In an optional embodiment of the present invention, the standard event message includes a service event identifier, and the multiple strategies respectively have corresponding scenario identifiers; the target strategy extraction module 902 may include:

[0203] A target scene identifier retrieval submodule, used to retrieve a target scene identifier matching the business event identifier from the cache;

[0204] The target policy extraction submodule is used to extract the target policy corresponding to the target scenario identifier from the cache.

[0205] In an optional embodiment of the present invention, the rule instantiation module 903 may include:

[0206] The rule instantiation submodule is used to fill the data in the standard event message and replace the rule parameters in the target policy rule to obtain a target policy rule instance.

[0207] In an optional embodiment of the present invention, the action instantiation module 905 may include:

[0208] The action instantiation submodule is used to fill the data in the standard event message and replace the action parameters in the target policy action to obtain a target policy action instance.

[0209] In an optional embodiment of the present invention, the initial event message pre-processing module 901 may include:

[0210] A data conversion submodule, used to perform data conversion on the initial event message to obtain a first event message; the data conversion includes data format conversion, message conversion and data type conversion;

[0211] A portrait tag writing submodule, used for retrieving a portrait tag matching the first event message, and writing the portrait tag into the first event message to obtain a second event message;

[0212] The encapsulation submodule is used to encapsulate the second event message according to the standard format of the business event message to obtain a standard event message message.

[0213] In an optional embodiment of the present invention, the service processing module 906 may include:

[0214] A first execution type determination submodule, used to determine the execution type of the target policy action instance;

[0215] The message push submodule is used to push the target policy action instance to the message queue if the execution type is the message push type, so that the corresponding business execution system can extract the target policy action instance from the message queue and execute the business action in the target policy action instance to complete the business processing for the business event.

[0216] In an optional embodiment of the present invention, the service processing module 906 may include:

[0217] A second execution type determination submodule, used to determine the execution type of the target policy action instance;

[0218] An API address extraction submodule, configured to extract an application programming interface API address from the target policy action instance if the execution type is a capability scheduling type;

[0219] The capability scheduling submodule is used to input the target policy action instance into an API interface based on the API address to call the corresponding business execution system to execute the business action in the target policy action instance to complete the business processing for the business event.

[0220] In an embodiment of the present invention, when a business event is intercepted, an initial event message matching the business event is obtained from a message queue, and the initial event message is preprocessed to obtain a standard event message message; a target policy matching the standard event message message is extracted from a cache; the target policy includes a target policy rule and a target policy action; the target policy rule is instantiated using a standard event message message to obtain a target policy rule instance; whether the judgment formula in the target policy rule instance is established is verified; if the judgment formula is established, the target policy action is instantiated using a standard event message message to obtain a target policy action instance; the target policy action instance is executed to complete the business processing for the business event. The embodiment of the present invention realizes online orchestration and intelligent matching of scenario strategies through a data-driven strategy engine, quickly supports high-throughput, low-latency generalized strategy matching for business scenarios, and interacts through a message queue, so that the business processing party and the receiving party are loosely coupled, and the full process tracking and analysis of message data is realized, and timely warning and push are carried out, which greatly improves the efficiency and accuracy of business event processing.

[0221] As for the device embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

[0222] An embodiment of the present invention also provides an electronic device, including: a processor, a memory, and a computer program stored in the memory and executable on the processor. When the computer program is executed by the processor, the various processes of the above-mentioned business processing method embodiment are implemented, and the same technical effect can be achieved. To avoid repetition, it will not be described here.

[0223] An embodiment of the present invention further provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the various processes of the above-mentioned business processing method embodiment are implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0224] The various embodiments in this specification are described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The same or similar parts between the various embodiments can be referenced to each other.

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

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

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

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

[0229] Although the preferred embodiments of the present invention have been described, those skilled in the art may make other changes and modifications to these embodiments once they have learned the basic creative concept. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments and all changes and modifications that fall within the scope of the embodiments of the present invention.

[0230] Finally, it should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or terminal device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or terminal device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the existence of other identical elements in the process, method, article or terminal device including the elements.

[0231] The business processing method, device, electronic device and computer-readable storage medium provided by the present invention are introduced in detail above. Specific examples are used in this article to illustrate the principles and implementation methods of the present invention. The description of the above embodiments is only used to help understand the method of the present invention and its core idea; at the same time, for general technical personnel in this field, according to the idea of ​​the present invention, there will be changes in the specific implementation method and application scope. In summary, the content of this specification should not be understood as a limitation on the present invention.

Claims

1. A business processing method, characterized in that: Applied to a policy platform, the policy platform includes a message queue and a policy group engine, the cache of the policy group engine stores multiple policies, and the method includes: When a service event is intercepted, an initial event message matching the service event is obtained from the message queue, and the initial event message is pre-processed to obtain a standard event message packet; Extracting a target policy matching the standard event message from the cache; the target policy includes a target policy rule and a target policy action; Using the standard event message, instantiating the target policy rule to obtain a target policy rule instance; Verify whether the judgment formula in the target policy rule instance is established; If the judgment formula is established, the target policy action is instantiated using the standard event message to obtain a target policy action instance; Executing the target policy action instance to complete the business processing for the business event; The preprocessing of the initial event message to obtain a standard event message includes: Performing data conversion on the initial event message to obtain a first event message; the data conversion includes data format conversion, message conversion and data type conversion; Retrieving a portrait tag matching the first event message, and writing the portrait tag into the first event message to obtain a second event message; Encapsulating the second event message according to a standard format of a business event message to obtain a standard event message message; The standard event message includes a service event identifier, and the multiple strategies respectively have corresponding scenario identifiers; and extracting a target strategy matching the standard event message from the cache includes: Retrieving a target scenario identifier matching the business event identifier from the cache; A target policy corresponding to the target scenario identifier is extracted from the cache.

2. The method according to claim 1, characterized in that The adopting the standard event message to instantiate the target policy rule to obtain the target policy rule instance includes: The data in the standard event message is filled in and replaces the rule parameters in the target policy rule to obtain a target policy rule instance.

3. The method according to claim 1, characterized in that The adopting the standard event message to instantiate the target policy action to obtain the target policy action instance includes: The data in the standard event message is filled in and replaces the action parameters in the target policy action to obtain a target policy action instance.

4. The method according to claim 1, characterized in that: The executing the target policy action instance to complete the business processing for the business event includes: Determining the execution type of the target policy action instance; If the execution type is a message push type, the target policy action instance is pushed to the message queue so that the corresponding business execution system can extract the target policy action instance from the message queue and execute the business action in the target policy action instance to complete the business processing for the business event.

5. The method according to claim 1, characterized in that The executing the target policy action instance to complete the business processing for the business event includes: Determining the execution type of the target policy action instance; If the execution type is a capability scheduling type, extracting an application programming interface API address from the target policy action instance; The target policy action instance is input with an API interface based on the API address to call a corresponding business execution system to execute the business action in the target policy action instance to complete business processing for the business event.

6. A service processing device, characterized in that: Applied to a policy platform, the policy platform includes a message queue and a policy group engine, the cache of the policy group engine stores multiple policies, and the device includes: An initial event message preprocessing module, used for obtaining an initial event message matching the business event from the message queue when a business event is intercepted, and preprocessing the initial event message to obtain a standard event message packet; A target policy extraction module, used to extract a target policy matching the standard event message from the cache; the target policy includes a target policy rule and a target policy action; A rule instantiation module, used to instantiate the target policy rule using the standard event message to obtain a target policy rule instance; A judgment formula verification module, used to verify whether the judgment formula in the target policy rule instance is established; An action instantiation module, used for instantiating the target policy action using the standard event message if the judgment formula is established, to obtain a target policy action instance; A business processing module, used to execute the target policy action instance to complete the business processing for the business event; The initial event message preprocessing module includes: A data conversion submodule, used to perform data conversion on the initial event message to obtain a first event message; the data conversion includes data format conversion, message conversion and data type conversion; A portrait tag writing submodule, used for retrieving a portrait tag matching the first event message, and writing the portrait tag into the first event message to obtain a second event message; An encapsulation submodule, used for encapsulating the second event message according to a standard format of a business event message to obtain a standard event message message; The standard event message includes a business event identifier, and the multiple strategies respectively have corresponding scenario identifiers; the target strategy extraction module includes: A target scene identifier retrieval submodule, used to retrieve a target scene identifier matching the business event identifier from the cache; The target policy extraction submodule is used to extract the target policy corresponding to the target scenario identifier from the cache.

7. An electronic device, characterized in that: include: A processor, a memory, and a computer program stored in the memory and executable on the processor, wherein the computer program, when executed by the processor, implements the steps of the business processing method according to any one of claims 1 to 5.

8. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the business processing method according to any one of claims 1 to 5 are implemented.

Images