Service decision processing method, decision module, electronic equipment and readable storage medium

Abstract

The invention discloses a service decision processing method, a decision module, electronic equipment and a readable storage medium, and belongs to the technical field of communication. According to the technical scheme of the invention, the method comprises the steps: obtaining a target message input by a message producer, and converting the target message into an internal notification; according to the internal notice, matching a target decision fragment in a decision library; under the condition that the target decision fragment is matched, a decision action corresponding to the target decision fragment is executed, and the decision action comprises notification issuing and / or object attribute modification of the context object. According to the invention, the efficiency and precision of the life cycle management method in the application can be improved.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a business decision processing method, a decision module, an electronic device and a readable storage medium. Background Art

[0002] Lifecycle management activities are control activities that aim to close events. They generate control outputs based on event attributes, change the state of the managed system, and collect system feedback to update event attributes. When the relevant attributes meet certain characteristics, the managed system is considered to have reached the desired operating state, so the event is closed and the lifecycle management activity ends.

[0003] Since lifecycle management activities are mainly based on the operations of the managed systems, and these operations usually have a sequence, the general practice in the industry is to treat them as workflow issues, use BPMN (Business Process Modeling Notation) specifications to model the process, and then use a process engine to drive its operation. Figure 1 As shown in the figure, the BPMN model depicts the event processing process through nodes and connection relationships. Nodes are used to complete specific tasks, and connections are used to control the order in which nodes are executed. Among them, service nodes perform various operations, message capture nodes receive external information, and branch nodes perform conditional jumps. Defining the event processing process with a BPMN flowchart has the following disadvantages:

[0004] 1. Efficiency problem: There is a deviation between the artificially set operation diagram and the actual operation requirements. In the actual processing process, the execution of the action should be triggered by meeting its execution requirements, while the artificially set sequence limits the freedom of action execution, thereby reducing processing efficiency;

[0005] 2. Control accuracy problem: The process operation mode determines that specific operations can only be performed at specific locations. For example, the service node cannot receive external information, nor can it branch according to external requests. If the service node execution time is too long, it will cause a delay in the response to the external request, thus affecting the timeliness and accuracy of the control.

[0006] Therefore, the traditional event lifecycle management methods have problems of low efficiency and accuracy in application that need to be solved urgently. Summary of the invention

[0007] The main purpose of this application is to provide a business decision processing method, a decision module, an electronic device and a readable storage medium, aiming to solve the technical problems of low efficiency and accuracy in the application of lifecycle management methods.

[0008] To achieve the above object, the present application provides a decision module, including a distributed decision network, wherein the distributed decision network has a first decision unit and a second decision unit topologically connected to the first decision unit, wherein the first decision unit includes:

[0009] A connector, connected to the second decision unit, and configured to obtain a target message input by the second decision unit;

[0010] an input queue, connected to the connector, configured to convert the target message into an internal notification;

[0011] A decision engine is connected to the input queue and is configured to match the target decision fragment in the decision library according to the internal notification; when the target decision fragment is matched, the decision action corresponding to the target decision fragment is executed, wherein the decision action includes publishing a notification and / or modifying the object attributes of the context object.

[0012] In addition, to achieve the above purpose, the present application also provides a business decision processing method, including:

[0013] Obtaining a target message input by a message producer, and converting the target message into an internal notification;

[0014] According to the internal notification, matching the target decision fragment in the decision library;

[0015] When the target decision fragment is matched, a decision action corresponding to the target decision fragment is executed, wherein the decision action includes publishing a notification and / or modifying an object attribute of a context object.

[0016] In addition, to achieve the above-mentioned purpose, the present application also provides an electronic device, which includes a processor and a memory, and the memory stores programs or instructions that can be run on the processor. When the program or instructions are executed by the processor, the business decision processing method as described in any one of the above items is implemented.

[0017] In addition, to achieve the above objectives, the present application also provides a computer-readable storage medium, on which a program or instruction is stored, and when the program or instruction is executed by a processor, the business decision processing method as described in any of the above items is implemented.

[0018] The embodiment of the present application provides a business decision processing method, a decision module, an electronic device and a readable storage medium. The decision module of the embodiment of the present application includes a distributed decision network, the distributed decision network has a first decision unit, and a second decision unit topologically connected to the first decision unit, the first decision unit includes a connector, an input queue and a decision engine, wherein the connector is connected to the second decision unit, the connector is configured to obtain a target message input by the second decision unit, the input queue is connected to the connector, the input queue is configured to convert the target message into an internal notification, the decision engine is connected to the input queue, and is configured to match the target decision fragment in the decision library according to the internal notification, and when the target decision fragment is matched, Execute the decision action corresponding to the target decision fragment, so that the embodiment of the present application forms a processing process through dynamic series connection of decision fragments, and adopts a distributed decision network to drive process execution, so as to be able to respond to various sudden requests and states in lifecycle management activities in real time. Compared with the BPMN process engine, the distributed mode of the present application provides better concurrent processing and expansion capabilities, which can improve the efficiency of lifecycle management, and the actions are triggered by conditions, so that the system works under the drive of conditions. The architecture ensures that various influencing factors can be processed at any time, thereby obtaining higher control accuracy, effectively improving the accuracy of lifecycle management in specific applications, and thus solving the technical problems of low efficiency and accuracy of lifecycle management methods in applications. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0020] Figure 1 A schematic diagram of a process for lifecycle management based on a BPMN model in related technologies is shown;

[0021] Figure 2 A schematic diagram of application scenarios of lifecycle management activities is shown;

[0022] Figure 3 A schematic diagram of the application environment of the decision-making module in an embodiment of the present application is shown;

[0023] Figure 4 A structural block diagram showing the application of the business decision processing method in the embodiment of the present application;

[0024] Figure 5 A schematic diagram of the structure of the decision-making unit in an embodiment of the present application is shown;

[0025] Figure 6 The following is a logical structure diagram of the designer in the embodiment of the present application;

[0026] Figure 7 A schematic diagram of the structure of a distributed decision-making network in a specific embodiment of the present application is shown;

[0027] Figure 8 shows a binary decision table in an embodiment of the present application;

[0028] Fig. 9 A flowchart of a business decision processing method provided by an exemplary embodiment of the present application is shown;

[0029] Fig.10 A structural block diagram of an electronic device according to an exemplary embodiment of the present application is shown. DETAILED DESCRIPTION

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

[0031] Since lifecycle management activities are mainly based on the operations of the managed systems, and these operations usually have a sequence, the general practice in the industry is to treat them as workflow issues, use BPMN (Business Process Modeling Notation) specifications to model the process, and then use the process engine to drive its operation. The specific process is as follows:

[0032] 1. Model the life cycle process during the development phase:

[0033] (1) Mapping action execution to service nodes;

[0034] (2) Mapping information acquisition to the message capture node;

[0035] (3) Map the branch jump to the branch node;

[0036] (4) Define the execution order of the process by connecting nodes, and analyze and judge the conditions at the branch nodes so that the derived branches point to the service node, message capture node or other branch node corresponding to the next action;

[0037] (5) Map the end of the process to the end node;

[0038] 2. During the operation phase, the process engine drives the lifecycle management activities.

[0039] (1) Deploy the process model defined by BPMN;

[0040] (2) When a new event is generated, the process engine is called to create a corresponding process instance;

[0041] (3) The process instance is driven by the process engine;

[0042] (4) During the process instance running, the service node triggers the interface call of the managed system and waits for the return, and the message capture node waits for external message input;

[0043] (5) The branch node judges the execution result of the service node and the message returned by the message capture node, and switches to different process branches based on the judgment result;

[0044] (6) When the process instance runs to the end node, the event is closed and the process is exited, completing the lifecycle management activities.

[0045] like Figure 1 As shown in the figure, the BPMN model depicts the event processing process through nodes and connection relationships. Nodes are used to complete specific tasks, and connections are used to control the order in which nodes are executed. Among them, service nodes perform various operations, message capture nodes receive external information, and branch nodes perform conditional jumps. Defining the event processing process with a BPMN flowchart has the following disadvantages:

[0046] 1. Efficiency problem: There is a deviation between the artificially set operation diagram and the actual operation requirements. In the actual processing process, the execution of the action should be triggered by meeting its execution requirements, while the artificially set sequence limits the freedom of action execution, thereby reducing processing efficiency;

[0047] 2. Control accuracy problem: The process operation mode determines that specific operations can only be performed at specific locations. For example, the service node cannot receive external information, nor can it branch according to external requests. If the service node execution time is too long, it will cause a delay in the response to the external request, thus affecting the timeliness and accuracy of the control.

[0048] Therefore, the traditional event lifecycle management methods have problems of low efficiency and accuracy in application that need to be solved urgently.

[0049] Based on this, an embodiment of the present application provides a business decision processing method, a decision module, an electronic device and a readable storage medium. The decision module of the embodiment of the present application includes a distributed decision network, the distributed decision network has a first decision unit, and a second decision unit topologically connected to the first decision unit, the first decision unit includes a connector, an input queue and a decision engine, wherein the connector is connected to the second decision unit, the connector is configured to obtain a target message input by the second decision unit, the input queue is connected to the connector, the input queue is configured to convert the target message into an internal notification, the decision engine is connected to the input queue, and is configured to match the target decision fragment in the decision library according to the internal notification, and when the target decision fragment is matched Under the circumstance, the decision action corresponding to the target decision fragment is executed, so that the embodiment of the present application forms a processing process through the dynamic series connection of decision fragments, and adopts a distributed decision network to drive the process execution, so as to be able to respond to various sudden requests and states in life cycle management activities in real time. Compared with the BPMN process engine, the distributed mode of the present application provides better concurrent processing and expansion capabilities, which can improve the efficiency of life cycle management, and the actions are triggered by conditions, so that the system works under the drive of conditions, and the architecture ensures that various influencing factors can be processed at any time, so as to obtain higher control accuracy, effectively improve the accuracy of life cycle management in specific applications, and thus solve the technical problems of low efficiency and low accuracy of life cycle management methods in applications.

[0050] The technical solution provided in the embodiments of the present application is described below with reference to the accompanying drawings.

[0051] The application scenarios of the business decision processing method of the embodiment of the present application include but are not limited to: network intelligent operation and maintenance system, monitoring and emergency support system, etc. In this embodiment, the event closed loop is an automated cycle. By sensing the output of the managed system, analyzing its situation and mapping it into events, and then controlling the managed system through the event lifecycle management activities, and adjusting according to feedback and situation changes until the managed system reaches the desired state, closing the event and ending the management activity. Such a cyclic process can reduce manual participation and improve the ability to respond to changes. Figure 2 As shown in the figure, the alarm, performance and other data provided by the managed system are generated into events after perception and analysis. The lifecycle management activities process the events and generate control instructions to affect the managed system. The new data generated by the controlled system is used to update the events, which in turn triggers the adjustment of the control instructions. This cycle continues until the management goal is achieved.

[0052] Fig. 9 A flowchart of a business decision processing method provided by an exemplary embodiment of the present application is shown. Fig. 9 As shown, the business decision processing method mainly includes the following steps.

[0053] Step S100, obtaining a target message input by a message producer, and converting the target message into an internal notification;

[0054] Exemplarily, the step of obtaining the external message input by the message producer includes:

[0055] Step A10, obtaining various message topics generated by the message producer, filtering out the message topic required by the current business from the various message topics, and using it as the target message input by the message producer.

[0056] In this embodiment, the input end of the first decision unit can select the notification source and filter the notification type, so as to accurately obtain the target message input by the message producer.

[0057] Step S200, matching the target decision fragment in the decision library according to the internal notification;

[0058] Step S300, when the target decision fragment is matched, executing the decision action corresponding to the target decision fragment, wherein the decision action includes publishing a notification and / or modifying the object attributes of the context object.

[0059] In this embodiment, it should be noted that, when the target decision fragment is not matched, it is determined that the decision process of this round of business decision processing is ended.

[0060] Exemplarily, the method further includes:

[0061] Step B10, when the decision action is to publish a notification, output a target notification corresponding to the target decision fragment to a message consumer.

[0062] To help understand the technical concept of this application, please refer to Figure 3 , Figure 3 The following is a schematic diagram showing the application environment of the decision module in the embodiment of the present application. The embodiment of the present invention is applied to an event closed-loop system. The event closed-loop system includes the following modules:

[0063] 1. Access module, which provides registration and input / output mechanisms for connecting the target system to the operation and maintenance system;

[0064] 2. The analysis module provides a mechanism to identify the target system input information as events and judge its clearance;

[0065] 3. Management module, providing a mechanism for storing and closing events;

[0066] 4. Decision-making module, providing a mechanism for managing the life cycle of events;

[0067] 5. Execution module, which provides a mechanism for executing instructions on event processing decisions;

[0068] 6. Monitoring module, which provides a mechanism for presenting and manually controlling operation and maintenance information and event status.

[0069] Among them, the embodiment of the present application is applied to the decision module of the event closed-loop system, responds to various requests and states, and drives lifecycle management activities according to user-defined action flows and control requirements until the event is finally closed and closed, completing its lifecycle process.

[0070] The embodiment of the present application assumes the role of decision-making module in the event closed-loop system, and its two ends are respectively connected to the producer and consumer of messages. The monitoring module, management module and execution module will send various messages to the device (the device is the decision module) and belong to the producer of messages. At the same time, they will also receive messages sent by the device for subsequent processing, and therefore are also connected to the device as consumers. The decision network filters, converts and processes the received messages to generate output messages. The output message is used to perform specific actions (such as diagnosis, self-healing), and causes the generation of new messages to be fed back to the decision network for control and adjustment. The topological structure and decision library of the distributed decision network are uniformly designed by the designer.

[0071] Please refer to Figure 4 , Figure 4 The block diagram of the structure used in the business decision processing method of the embodiment of the present application is shown. The three parts arranged horizontally in the figure, the middle part is the device (i.e., the decision module) used in the embodiment of the present application, and the left and right sides are the message producers and consumers, which are implemented by external modules. The producer generates request and status messages to drive the decision network to make decisions. The consumer receives the control and notification messages generated by the decision network and performs related operations. Figure 4 The device (i.e., decision module) used in the embodiment of the present application shown in includes two parts: a distributed decision network and a designer. The distributed decision network works in the system operation phase and is designed by the designer in the development phase. The decision library of each decision unit is designed and customized by the designer in the system development or operation phase.

[0072] Among them, messages are the only way for external modules to transmit information to this device. Input messages (i.e., the target messages mentioned above) are used to initiate requests and state change notifications to this device, and output messages (i.e., the release notifications mentioned above) are used to control external modules to perform actions or notify operation and maintenance personnel to take measures.

[0073] Common input messages (i.e. target messages) are as follows:

[0074] Messages from the management module are used to express changes in event status, such as create, update, clear, close, etc. Messages from the monitoring module are used to initiate operation requests, such as pause, manual, previous step, next step, cancel, etc. Messages from the execution module are used to notify the execution results of the request, such as exception, timeout, busy or idle actuator, etc. Common output messages (i.e., published notifications) are as follows:

[0075] Messages sent to the management module are used to perform operations or collect results, such as event closure, result summary, etc. Messages sent to the monitoring module are used to notify the processing process, such as current operation, execution timing, etc. Messages sent to the execution module are used to initiate operation instructions, such as a certain interface call request, etc.

[0076] In this embodiment, a message represents a specific request or response. The message interface between modules should clearly define the message structure and interaction sequence sent by both parties to form a message interaction protocol. This message interaction protocol is used to design the input parameters of this device.

[0077] It should be noted that the external module may use different types of message mechanisms to communicate with the present device. In order to shield the differences, the present device (i.e., the decision module) uses an internal format called notification (i.e., the internal notification mentioned above) to transmit information between decision units. The data structure of the notification (i.e., the internal notification mentioned above) includes fields such as type, sender ID, timestamp, event object, and attribute table. Different types of internal notifications have different attribute table structures.

[0078] In this embodiment, the internal notification is a structure for information transmission between decision-making units. The functions and cooperative relationships of the decision-making units determine the content and interaction methods of the internal notification. It can be understood that the context object is an object that exists in the memory at runtime and is used to record various status information that affects the decision. When it changes, it means that a new decision needs to be made.

[0079] Among them, the context object connects different notifications in series to form a continuous processing process. The received notifications are used to update certain attributes in the context object, and the changes in the attributes will trigger decision evaluation and perform certain actions based on the evaluation results, including: generating and publishing new notifications, and further modifying certain attributes of the context object. Both actions can trigger further reactions. This reaction will continue until it is decided not to perform any action after evaluation. Then the attributes of the context object will no longer change, and no new processing actions will be generated. It should be noted that the structure of the context object includes two main parts: event type ID and attribute table. The structure of its attribute table is related to the notification content and can be designed after the notification interaction of each decision unit is determined.

[0080] In this embodiment, the target decision fragment refers to the decision fragment matched by the internal notification in the decision library. The decision fragment is used to describe the action performed under certain conditions. When the input data matches the condition of a decision fragment, the action part of this decision fragment will be executed. This device (i.e., decision module) has the following types of decision fragments:

[0081] 1. Input the adaptation decision fragment and extract the content of a received message to generate a notification;

[0082] 2. Output the adaptation decision fragment and convert a received notification into a message;

[0083] 3. Notification conversion decision fragment, converting a received notification into multiple notifications with other contents that are published sequentially;

[0084] 4. Notification processing decision fragment, using a received notification to update the context object;

[0085] 5. The context evaluation decision fragment is used to evaluate whether the attributes of the context object meet certain conditions, and then execute notification publishing and / or further attribute updates.

[0086] In this embodiment, for simple decision fragments, their conditions and actions can be directly defined by expressions. For contextual evaluation decision fragments, since a large number of attributes need to be evaluated as a whole, in order to avoid missing attributes during evaluation, a decision table can be used to describe it, and then each row of the table can be converted into a decision fragment separately. Please refer to Table (I), which illustrates an example of decision expression.

[0087] (one)

[0089] The embodiment of the present application adopts multiple decision fragments to define different actions and their triggering conditions, and deploys them to a distributed decision network with a certain topological structure. Through the decision-making process of the decision unit and the notification collaboration between multiple units, some decision fragments are dynamically connected in series under the drive of runtime messages to form an actual complete event processing process. The distributed decision network and decision fragments are uniformly designed and deployed by a visual designer to achieve a standardized and simplified design process.

[0090] In this embodiment, the distributed decision network is composed of multiple decision units (including a first decision unit and a second decision unit) interconnected. Among them, a decision unit is an entity that is deployed with a collection of decision fragments and exchanges conditions and results with the outside world through notifications. Driven by notifications, they perform decision matching and execute the prescribed actions (generating new notifications, updating the attributes of context objects) of the hit decision fragment (the hit decision fragment is the target decision fragment). Please refer to Figure 5 , Figure 5 Schematic diagram of the structure of the decision unit in the embodiment of the present application. The typical structure of the decision unit (first decision unit) includes:

[0091] A connector, used to connect the output queue of other decision units (i.e., the second decision unit), collect and filter the output notifications of other decision units (i.e., the second decision unit);

[0092] Input queue, which mixes and sorts inputs from different queues onto the same timeline;

[0093] The decision library is used to store the collection of all decision fragments of the decision unit;

[0094] Runtime memory, used to load decision fragments and store context objects;

[0095] Output queue, used to publish output notifications of this decision unit (i.e., publish notifications);

[0096] The decision engine is used to load decision fragments, read input notifications, match decision fragments, and execute decision actions corresponding to the matched decision fragments.

[0097] In this embodiment, when the notification generated by the decision unit (the first decision unit) is received and matched by the next decision unit (i.e., the third decision unit), new notifications can continue to be generated. Such transmission and feedback can realize complex business logic. Structurally, the input end of the decision unit can select the notification source and filter the notification type. The output end of the decision unit is a structure similar to a message topic, which is used to store the notifications issued by this unit in an orderly manner for use by multiple other decision units. The interconnection of decision units constitutes the basic architecture of the decision network.

[0098] In this embodiment, the decision-making units of this device (i.e., decision-making modules) are of three types:

[0099] The scheduling control unit is used for decision control of scheduling logic. Its input and output ends process notification class data structures, deploy notification conversion decision fragments, notification processing decision fragments, and context object evaluation decision fragments. The scheduling control unit responds to notifications and influences decisions through context objects;

[0100] The input adaptation unit is a special decision unit, whose input end is connected to various message topics, and the output end publishes notification data structures. This unit only deploys input adaptation decision fragments, and does not need to hold context objects internally;

[0101] The output adaptation unit is another special type of decision unit. Its input end processes notification data structures and its output end publishes messages. The output adaptation decision fragment is deployed on it, and it also does not need to hold the context object.

[0102] In addition, the distributed decision network of this embodiment may include one scheduling control unit or multiple scheduling control units. When there are multiple scheduling control units, the decision network forms a logical partition structure, and the control task is completed through the cooperation of different decision units.

[0103] In this embodiment, the structure of the distributed decision-making network includes the following elements:

[0104] Input adaptation decision unit, output adaptation decision unit, scheduling control decision unit (i.e. the scheduling control unit mentioned above), messages received by the input adaptation decision unit, messages issued by the output adaptation decision unit, notification connection channels between the decision units, and notifications on each connection channel.

[0105] Specifically, the input adaptation unit listens to messages from multiple topics and converts them into internal notifications for use by other units. The scheduling control unit receives notifications from other units and controls the execution of business flows. The output adaptation unit converts the received internal notifications into external messages and publishes them to the associated message topics.

[0106] The embodiment of the present application provides a business decision processing method, a decision module, an electronic device and a readable storage medium. The business decision processing method in the embodiment of the present application is to obtain a target message input by a message producer, convert the target message into an internal notification, and match the target decision fragment in the decision library according to the internal notification. When the target decision fragment is matched, the decision action corresponding to the target decision fragment is executed, wherein the decision action includes publishing a notification and / or modifying the object attribute of the context object, so that the embodiment of the present application forms a processing process by dynamically connecting decision fragments in series, and adopts a distributed decision network to drive process execution, so as to be able to respond to various sudden requests and states in life cycle management activities in real time. Compared with the BPMN process engine, the distributed mode of the present application provides better concurrent processing and expansion capabilities, which can improve the efficiency of life cycle management, and the action is triggered by a condition, so that the system works under the drive of the condition, and the architecture ensures that various influencing factors can be processed at any time, thereby obtaining higher control accuracy, effectively improving the accuracy of life cycle management in specific applications, and thus solving the technical problems of low efficiency and accuracy of the life cycle management method in application.

[0107] It is worth mentioning that the embodiment of the present application uses decision fragments to dynamically connect in series to form a processing process. Unlike the existing solution that uses processes to define activities, the embodiment of the present application believes that lifecycle management is essentially a decision-making process driven by multiple factors, and the execution of actions in the process is triggered by conditions rather than pre-arranged. When the conditions match, the corresponding action is executed. The result of executing the action leads to new condition matching, so that the execution process of the action flow can continue. Each of the above actions and its execution conditions form a decision fragment. The dynamic concatenation of decision fragments forms the actual processing process. The advantages of this solution are:

[0108] 1. There is no need to manually specify the execution order, so actions that meet the conditions can be run concurrently, improving processing efficiency;

[0109] 2. Actions are triggered by conditions, so that the system works under the drive of conditions. Therefore, the architecture ensures that various influencing factors can be handled at any time, thereby achieving higher control accuracy and being able to respond to various sudden requests and states in life cycle management activities in real time;

[0110] 3. The decision fragments have a simple structure and single responsibilities. They do not depend on each other and are therefore highly stable. They can be replaced individually and can adapt to adjustments in control requirements at a relatively low modification cost, thus improving the system's flexibility in responding to changes. In addition, they can describe control management activities with a simple structure in a variety of scenarios, from simple to complex.

[0111] Therefore, compared with the process engine, the embodiment of the present invention adopts a distributed processing process by dynamically connecting decision fragments in series, which can provide better concurrent processing and expansion capabilities.

[0112] In a possible implementation, the step of matching the target decision fragment in the decision library according to the internal notification includes:

[0113] Step B10, modifying the object attribute of the context object according to the internal notification;

[0114] Step B20, taking the modified object attribute as the target object attribute, and checking whether there is a target decision fragment matching the target object attribute in the decision library;

[0115] In this embodiment, the target decision fragment refers to a decision fragment that matches the attribute of the target object in the decision library.

[0116] Step B30: if there is a target decision segment that matches the target object attribute, determine that the target decision segment is matched.

[0117] In this embodiment, in order to help understand the technical concept of this embodiment, an operation workflow of a specific embodiment is listed, including:

[0118] 1. The input adaptation unit receives an external message (i.e., the target information referred to above), converts the message into a notification (i.e., the internal notification referred to above) through matching, and publishes it to the output end;

[0119] 2. The scheduling control unit that subscribes to the notification receives the notification (i.e., the internal notification referred to above), and updates the context object according to the notification (i.e., modifies the object attributes corresponding to the context);

[0120] 3. The updated context object causes a decision fragment to be hit, and the action corresponding to the hit decision fragment (the hit decision fragment is the target decision fragment) is executed (including issuing a new notification and further updating the context);

[0121] 4. In the case of multi-level scheduling, the secondary control unit repeats the work of step 2 in this specific embodiment after receiving the notification to perform matching and output;

[0122] 5. When the decision fragment containing the business operation is hit, the corresponding scheduling control unit executes the operation instruction contained in the decision fragment and issues a notification triggering the business operation (i.e., the aforementioned issuance notification);

[0123] 6. The output adapter unit receives and processes the action notification, converts it into a message and publishes it to the message topic;

[0124] 7. The external execution module listens to the action message, executes the instructions and feeds back the result message;

[0125] 8. The input adaptation unit receives and processes the feedback result message and republishes it to its output end for subsequent decision units to receive and process;

[0126] In this embodiment, the scheduling control unit that subscribes to the notification repeatedly performs the above actions, thereby providing a responsibility-sharing decision network, which decomposes complex decision problems into decision problems with single responsibilities and standardized forms. By increasing the number of decision units and expanding the scale of the decision network, more complex decision control can be achieved at a relatively small cost. At the same time, since the division of responsibilities is clearer and more single, the decision fragments of each decision unit become simple and standardized, which is conducive to the automatic generation of decision fragments.

[0127] The decision fragments in this embodiment are separated from each other by notifications, and notifications are connected to each other by decision fragments. Each link is simple and independent, which is easy to design and replace. In addition, the designer's support for the full-process architecture and strategy design can greatly simplify the construction process of the control application.

[0128] It is worth mentioning that the hierarchical decision network provided in the embodiment of the present application has the potential for distributed horizontal expansion. Only by simply dividing the notification types, multi-instance horizontal expansion and task sharing of the decision unit can be achieved, thereby improving the concurrent processing capabilities of large-scale event scenarios.

[0129] Furthermore, after the step of executing the decision action corresponding to the target decision segment, the method further includes:

[0130] Step C10, when the decision action is to modify the object attributes of the context object, returns to execute: the step of taking the modified object attributes as the target object attributes, and checking whether there is a target decision fragment matching the target object attributes in the decision library, until there is a target decision fragment matching the target object attributes in the decision library, and the decision action corresponding to the target decision fragment is to publish a notification.

[0131] In this embodiment, in order to help understand the technical concept of this embodiment, a typical working logic of a scheduling control unit (a type of first decision unit) in a specific embodiment is listed as follows:

[0132] 1. The connector receives and filters the notifications from the output queue of other decision units (second decision units), and puts the filtered notifications into the input queue for unified sorting;

[0133] 2. The decision engine reads the notifications from the input queue to match the notification processing decision fragments;

[0134] 3. The modification content of the context object attributes is defined in the hit notification processing decision fragment (i.e., the target decision fragment), and the decision engine sets the context object attributes in the memory accordingly;

[0135] 4. The modification of the context object attributes triggers the decision engine to perform a new round of matching using the context evaluation decision fragment;

[0136] 5. The matching context evaluation decision fragment defines the content of notification generation and attribute adjustment. The decision engine generates new notifications and adjusts the attributes of the context object accordingly.

[0137] 6. Modification of the attributes of the context object will trigger a new round of decision matching;

[0138] 7. When the new decision matching process does not find a matching context evaluation decision fragment, the attributes of the context object no longer change, and this round of decision-making process triggered by the notification ends.

[0139] It can be seen that one notification may trigger multiple rounds of decision-making and stimulate multiple secondary notifications. The processing process after the secondary notification is received by other decision-making units is similar to a chain reaction. Therefore, the embodiments of the present application can be used to implement complex processing processes, so that the responsiveness of business flows to environmental conditions is improved and the control is more precise. Different decision-making units in the decision-making network can intervene in the message processing they are responsible for at any time without waiting for a serial processing flow to execute to a certain decision position before processing. Therefore, it can respond to various emergencies more quickly and improve the control accuracy of business decision processing.

[0140] In a possible implementation manner, each decision segment in the decision library is designed by a designer.

[0141] Exemplarily, the designer includes a first designer and / or a second designer,

[0142] The first designer is configured to arrange the topological structure of the topological connection of each decision unit in the distributed decision network, and the second designer is configured to design each decision segment in the decision library.

[0143] In this embodiment, the designer supports visual decision network design. To facilitate understanding, the following is an introduction to the design functions of the designer in a specific embodiment, including:

[0144] (1) Decision-making unit instance layout;

[0145] (2) Notification connections between decision-making units;

[0146] (3) Input and output message structure definition;

[0147] (4) Definition of notification structure between decision-making units;

[0148] (5) Definition of the context structure of each decision unit.

[0149] 2. The design of the decision library of each unit supports the definition of decision fragments in the form of decision tables, as shown in Table (I), including:

[0150] (1) Design of decision library for input and output adaptation unit;

[0151] (2) Design of the decision library of the dispatching control unit.

[0152] 3. Import and export of design results.

[0153] In this embodiment, the output of the designer includes deployment description files and decision fragment files. The deployment description files are used to describe the structure of the decision network; the decision configuration files are used to describe the decision library of each unit. Figure 6 As shown, Figure 6This is a logical structure diagram of the designer in the embodiment of the present application.

[0154] In order to further understand the technical concept of the present application, the following steps are required to introduce the mechanism for implementing the embodiments of the present invention:

[0155] 1. Use the designer to build the decision network structure;

[0156] (1) Determine the interface message between the device (i.e., decision module) and the external module, and establish the data structure in the designer. The output message is mainly various operation messages; the input message includes response, result, request, timeout, exception, update and other types;

[0157] (2) Determine the layout and responsibilities of decision-making units and set the topological connections between decision-making units;

[0158] (3) Determine the notification structure and interaction relationship between decision-making units;

[0159] 2. Use the designer to design the decision library of each unit;

[0160] (1) Design the messages of the input and output adaptation units and the decision fragments required to notify the conversion decision library;

[0161] (2) Use a decision table to describe the response of the decision context object to the notification;

[0162] (3) Use decision tables to describe the response of context objects to output notifications (including action execution);

[0163] (4) Convert the decision table into the scheduling control decision fragments required by the decision library;

[0164] 3. Output deployment files and decision configuration files;

[0165] 4. Generate decision network entities using deployment files;

[0166] 5. Load the decision configuration file into the decision library of each decision unit;

[0167] 6. When the processing flow needs to be adjusted, use the designer to load the decision configuration file for adjustment, and reconfigure the decision library of each unit after output.

[0168] It is worth mentioning that the embodiment of the present application uses a programmable distributed decision network to drive process execution. Among them, the distributed decision network is an architecture in which multiple decision units are interconnected to make collaborative decisions. The decision unit makes a decision on the received notification and sends the decision result to other units in the form of a new notification to trigger subsequent decisions. The transmission of notifications enables the decision to form a chain, so that complex tasks can be completed step by step. The use of a programmable distributed decision network has the following advantages:

[0169] 1. The decision-making units have the same structure, and their behaviors are defined only by decision fragments, thus achieving separation of business and technology;

[0170] 2. Collaboration among decision-making units shares the pressure of decision-making and simplifies the difficulty of decision-making design;

[0171] 3. The distributed architecture makes each node simple, standardized, easy to replace and horizontally expand, and suitable for cloud deployment.

[0172] This embodiment implements an editable structure through a designer, so that various decision units are organized and connected as needed to achieve business needs with the most suitable topology.

[0173] In addition, the embodiment of the present application uses a designer to uniformly model services and networks.

[0174] The designer supports topology design and decision design of distributed decision networks in a visual way, and imports and exports existing designs, providing the ability to quickly customize decision networks in the form of templates. The designer provides a check function for the dependencies between design elements and provides a wizard to simplify the design process. The advantages of using the designer are as follows:

[0175] 1. The design difficulty is simplified through interface visualization;

[0176] 2. Standardize the design process through wizards to avoid uncontrollable design results;

[0177] 3. The built-in tools can realize the automatic generation of decision layout and decision fragments, which reduces the design workload and improves the flexibility of on-site design;

[0178] Compared with existing solutions, the embodiments of the present application abandon the idea of ​​traditional process processing, convert the predefined execution process into decision fragments connected at runtime, and use a distributed decision network to reduce the complexity of decision entities and improve the system scalability.

[0179] In addition, the present application also lists another specific embodiment, including:

[0180] like Figure 7 As shown, each layer of control can deploy a scheduling control unit, thus forming a distributed decision network consisting of the following decision units:

[0181] An input adaptation unit for converting external messages into internal notifications;

[0182] An output adaptation unit, used to convert internal notifications into external messages;

[0183] The global control unit is used to control the logic of scheduling start, stop, result aggregation, etc.

[0184] A service flow control unit, used to control the flow direction of the service flow;

[0185] The business link control unit is used to control the execution process of each operation.

[0186] In this embodiment, hierarchical control belongs to a scenario of logical partitioning. The essence of the idea of ​​logical partitioning is to convert a part of the logic in which decision fragments are connected in series during operation into the logic of static connection of notification channels. In this way, the purpose of simplifying the logic complexity is achieved through static and dynamic sharing.

[0187] After the hierarchical control is adopted in the embodiment of the present application, each decision unit is only responsible for a part of the logical control, which reduces the number of attributes of the context object of each decision unit, thereby simplifying the table items of the decision table, reducing the number of rows in a single decision table, and simplifying the design of the decision table and decision fragments. In addition, another benefit of adopting hierarchical control is that frequently adjusted strategies can be separated from basically fixed strategies, so that a part of the decision fragments can be solidified in the development stage, so that in the operation stage, only a few decisions need to be designed, which is conducive to flexible customization according to the conditions of the operation site.

[0188] Furthermore, the embodiment of the present application also adopts a binary approach to the decision-making design process of the designer.

[0189] In this embodiment, the traditional decision table conditions and actions are not clearly defined and have various forms, which is not conducive to the automatic generation of rules. A binary decision table can be used to calculate the conditions and action results in a numerical way, making the decision fragment structure simple and standardized, which is conducive to design and low-code automatic generation.

[0190] like Figure 8 As shown, the binary decision table is mainly composed of binary flags, each row represents a decision fragment, and each column represents a binary attribute of the context.

[0191] Among them, a context object is described by a set of ordered binary flags. Each flag represents a state attribute, and its value is: 0, 1, ignore (0 or 1). For such a binary number, its mask and value can be calculated for the generation of decision fragments. The action part consists of a notification list and a binary attribute list of the context object. The notification field is used to describe the notification generation requirements, and the ordered binary flag group is used to record the update of the decision to the state, and the values ​​are: set, reset, and unchanged. The individual operation of each flag can be processed at one time through the values ​​of the set field and the reset field.

[0192] The binary decision table is used as follows:

[0193] 1. Mask calculation method: If a flag bit in the conditional area is 1 or 0, the corresponding position is set to 1, otherwise it is set to 0, and the binary value is obtained;

[0194] 2. Value calculation method: If a flag bit in the condition area is 1, then the corresponding position is 1, otherwise it is set to 0, and the binary value is obtained;

[0195] 3. Calculation method of setting value: if a flag in the action area is 1, then the corresponding position is 1, otherwise it is set to 0, and the binary value is obtained;

[0196] 4. Reset value calculation method: If a flag bit in the action area is 0, then the corresponding position is 0, otherwise it is set to 1, and the binary value is obtained.

[0197] This embodiment can obtain all the flags of the decision table by collecting all the state attributes and control request types that affect the decision, thereby forming a decision table structure. By exhaustively enumerating and simplifying the values ​​of each flag, the conditions of the decision table can be obtained, thereby generating a row of the decision table. For the conditions represented by each row of the decision table, its corresponding action is determined, and the generation notification and flag position and reset actions are filled in to complete a decision design. This embodiment can obtain the parameters required for the programmatic generation rule by calculating the mask, value, set value and reset value of each row.

[0198] This embodiment provides a new idea for solving complex policy problems: 1. Complex policy problems are broken down into relatively simple policy problems through a distributed decision network, and solved in steps, making standardization and low-code possible; 2. By clearly defining the responsibilities between context objects and notifications, and introducing decision tables and binary decision tables, a set of simple, feasible and easy-to-promote decision library design procedures is formed; 3. A new idea for realizing interactive process processing through a distributed decision network is provided.

[0199] It should be noted that the many details described in this specific embodiment are only helpful for understanding the technical concept of the present application and do not constitute a limitation of the present application. More simple transformations based on the technical concept of the present application should all be within the scope of protection of the present application.

[0200] also, Figure 3 A schematic diagram of the application environment of the decision-making module in the embodiment of the present application is shown. Figure 3 As shown, the decision module includes a distributed decision network, the distributed decision network has a first decision unit, and a second decision unit topologically connected to the first decision unit, wherein the first decision unit includes:

[0201] A connector, connected to the second decision unit, and configured to obtain a target message input by the second decision unit;

[0202] Exemplarily, the connector is further configured as:

[0203] A plurality of message topics generated by the second decision unit are obtained, and a message topic required by the current business is filtered out from the various message topics as a target message input by the second decision unit.

[0204] In this embodiment, the input end of the first decision unit can select the notification source and filter the notification type, so as to accurately obtain the target message input by the message producer.

[0205] an input queue, connected to the connector, configured to convert the target message into an internal notification;

[0206] A decision engine is connected to the input queue and is configured to match the target decision fragment in the decision library according to the internal notification; when the target decision fragment is matched, the decision action corresponding to the target decision fragment is executed, wherein the decision action includes publishing a notification and / or modifying the object attributes of the context object.

[0207] In this embodiment, it should be noted that, when the target decision fragment is not matched, it is determined that the decision process of this round of business decision processing is ended.

[0208] Exemplarily, the distributed decision network further includes a third decision unit topologically connected to the first decision unit, the first decision unit further includes an output queue, the decision engine, the output queue and the third decision unit are connected in sequence, and the output queue is set to:

[0209] In the case where the decision action is to issue a notification, a target notification corresponding to the target decision segment is output to the third decision unit.

[0210] To help understand the technical concept of this application, please refer to Figure 3 , Figure 3 The following is a schematic diagram showing the application environment of the decision module in the embodiment of the present application. The embodiment of the present invention is applied to an event closed-loop system. The event closed-loop system includes the following modules:

[0211] 1. Access module, which provides registration and input / output mechanisms for connecting the target system to the operation and maintenance system;

[0212] 2. The analysis module provides a mechanism to identify the target system input information as events and judge its clearance;

[0213] 3. Management module, providing a mechanism for storing and closing events;

[0214] 4. Decision-making module, providing a mechanism for managing the life cycle of events;

[0215] 5. Execution module, which provides a mechanism for executing instructions on event processing decisions;

[0216] 6. Monitoring module, which provides a mechanism for presenting and manually controlling operation and maintenance information and event status.

[0217] Among them, the embodiment of the present application is applied to the decision module of the event closed-loop system, responds to various requests and states, and drives lifecycle management activities according to user-defined action flows and control requirements until the event is finally closed and closed, completing its lifecycle process.

[0218] The embodiment of the present application assumes the role of decision-making module in the event closed-loop system, and its two ends are respectively connected to the producer and consumer of messages. The monitoring module, management module and execution module will send various messages to the device (the device is the decision module) and belong to the producer of messages. At the same time, they will also receive messages sent by the device for subsequent processing, and therefore are also connected to the device as consumers. The decision network filters, converts and processes the received messages to generate output messages. The output message is used to perform specific actions (such as diagnosis, self-healing), and causes the generation of new messages to be fed back to the decision network for control and adjustment. The topological structure and decision library of the distributed decision network are uniformly designed by the designer.

[0219] Please refer to Figure 4 , Figure 4 The block diagram of the structure used in the business decision processing method of the embodiment of the present application is shown. The three parts arranged horizontally in the figure, the middle part is the device (i.e., the decision module) used in the embodiment of the present application, and the left and right sides are the message producers and consumers, which are implemented by external modules. The producer generates request and status messages to drive the decision network to make decisions. The consumer receives the control and notification messages generated by the decision network and performs related operations. Figure 4 The device (i.e., decision module) used in the embodiment of the present application shown in includes two parts: a distributed decision network and a designer. The distributed decision network works in the system operation phase and is designed by the designer in the development phase. The decision library of each decision unit is designed and customized by the designer in the system development or operation phase.

[0220] Among them, messages are the only way for external modules to transmit information to this device. Input messages (i.e., the target messages mentioned above) are used to initiate requests and state change notifications to this device, and output messages (i.e., the release notifications mentioned above) are used to control external modules to perform actions or notify operation and maintenance personnel to take measures.

[0221] Common input messages (i.e. target messages) are as follows:

[0222] Messages from the management module are used to express changes in event status, such as create, update, clear, close, etc. Messages from the monitoring module are used to initiate operation requests, such as pause, manual, previous step, next step, cancel, etc. Messages from the execution module are used to notify the execution results of the request, such as exception, timeout, busy or idle actuator, etc.

[0223] Common output messages (i.e., publishing notifications) are as follows:

[0224] Messages sent to the management module are used to perform operations or collect results, such as event closure, result summary, etc. Messages sent to the monitoring module are used to notify the processing process, such as current operation, execution timing, etc. Messages sent to the execution module are used to initiate operation instructions, such as a certain interface call request, etc.

[0225] In this embodiment, a message represents a specific request or response. The message interface between modules should clearly define the message structure and interaction sequence sent by both parties to form a message interaction protocol. This message interaction protocol is used to design the input parameters of this device.

[0226] It should be noted that the external module may use different types of message mechanisms to communicate with the present device. In order to shield the differences, the present device (i.e., the decision module) uses an internal format called notification (i.e., the internal notification mentioned above) to transmit information between decision units. The data structure of the notification (i.e., the internal notification mentioned above) includes fields such as type, sender ID, timestamp, event object, and attribute table. Different types of internal notifications have different attribute table structures.

[0227] In this embodiment, the internal notification is a structure that exists for information transmission between decision-making units. The functions and cooperation relationships of the decision-making units determine the content and interaction methods of the internal notification.

[0228] Those skilled in the art will appreciate that a context object is an object that exists in memory during runtime and is used to record various status information that affects decision making. When the context object changes, it indicates that a new decision needs to be made.

[0229] In this embodiment, the context object connects different notifications in series to form a continuous processing process. The received notifications are used to update certain attributes in the context object, and the change of the attributes will trigger the decision evaluation, and perform certain actions according to the evaluation results, including: generating and publishing new notifications, and further modifying certain attributes of the context object. Both actions can trigger further reactions. This reaction will continue until it is determined after evaluation that no action will be performed, then the attributes of the context object will no longer change, and no new processing actions will be generated.

[0230] It should be noted that the structure of the context object includes two main parts: event type ID and attribute table. The structure of the attribute table is related to the notification content and can be designed after the notification interaction of each decision unit is determined.

[0231] In this embodiment, the target decision fragment refers to the decision fragment matched by the internal notification in the decision library. The decision fragment is used to describe the action performed under certain conditions. When the input data matches the condition of a decision fragment, the action part of this decision fragment will be executed. This device (i.e., decision module) has the following types of decision fragments:

[0232] 1. Input the adaptation decision fragment and extract the content of a received message to generate a notification;

[0233] 2. Output the adaptation decision fragment and convert a received notification into a message;

[0234] 3. Notification conversion decision fragment, converting a received notification into multiple notifications with other contents that are published sequentially;

[0235] 4. Notification processing decision fragment, using a received notification to update the context object;

[0236] 5. The context evaluation decision fragment is used to evaluate whether the attributes of the context object meet certain conditions, and then execute notification publishing and / or further attribute updates.

[0237] In this embodiment, for simple decision fragments, their conditions and actions can be directly defined by expressions. For contextual evaluation decision fragments, since a large number of attributes need to be evaluated as a whole, in order to avoid missing attributes during evaluation, a decision table can be used to describe it, and then each row of the table can be converted into a decision fragment separately. Please refer to Table (I), which illustrates an example of decision expression.

[0238] The embodiment of the present application adopts multiple decision fragments to define different actions and their triggering conditions, and deploys them to a distributed decision network with a certain topological structure. Through the decision-making process of the decision unit and the notification collaboration between multiple units, some decision fragments are dynamically connected in series under the drive of runtime messages to form an actual complete event processing process. The distributed decision network and decision fragments are uniformly designed and deployed by a visual designer to achieve a standardized and simplified design process.

[0239] In this embodiment, the distributed decision network is composed of multiple decision units (including a first decision unit and a second decision unit) interconnected. Among them, a decision unit is an entity that is deployed with a collection of decision fragments and exchanges conditions and results with the outside world through notifications. Driven by notifications, they perform decision matching and execute the prescribed actions (generating new notifications, updating the attributes of context objects) of the hit decision fragment (the hit decision fragment is the target decision fragment). Please refer to Figure 5 , Figure 5 Schematic diagram of the structure of the decision unit in the embodiment of the present application. The typical structure of the decision unit (first decision unit) includes:

[0240] A connector, used to connect the output queue of other decision units (i.e., the second decision unit), collect and filter the output notifications of other decision units (i.e., the second decision unit);

[0241] Input queue, which mixes and sorts inputs from different queues onto the same timeline;

[0242] The decision library is used to store the collection of all decision fragments of the decision unit;

[0243] Runtime memory, used to load decision fragments and store context objects;

[0244] Output queue, used to publish output notifications of this decision unit (i.e., publish notifications);

[0245] The decision engine is used to load decision fragments, read input notifications, match decision fragments, and execute decision actions corresponding to the matched decision fragments.

[0246] In this embodiment, when the notification generated by the decision unit (the first decision unit) is received and matched by the next decision unit (i.e., the third decision unit), new notifications can continue to be generated. Such transmission and feedback can realize complex business logic. Structurally, the input end of the decision unit can select the notification source and filter the notification type. The output end of the decision unit is a structure similar to a message topic, which is used to store the notifications issued by this unit in an orderly manner for use by multiple other decision units. The interconnection of decision units constitutes the basic architecture of the decision network.

[0247] In this embodiment, the decision-making units of this device (i.e., decision-making modules) are of three types:

[0248] The scheduling control unit is used for decision control of scheduling logic. Its input and output ends process notification class data structures, deploy notification conversion decision fragments, notification processing decision fragments, and context object evaluation decision fragments. The scheduling control unit responds to notifications and influences decisions through context objects;

[0249] The input adaptation unit is a special decision unit, whose input end is connected to various message topics, and the output end publishes notification data structures. This unit only deploys input adaptation decision fragments, and does not need to hold context objects internally;

[0250] The output adaptation unit is another special type of decision unit. Its input end processes notification data structures and its output end publishes messages. The output adaptation decision fragment is deployed on it, and it also does not need to hold the context object.

[0251] In addition, the distributed decision network of this embodiment may include one scheduling control unit or multiple scheduling control units. When there are multiple scheduling control units, the decision network forms a logical partition structure, and the control task is completed through the cooperation of different decision units.

[0252] In this embodiment, the structure of the distributed decision-making network includes the following elements:

[0253] Input adaptation decision unit, output adaptation decision unit, scheduling control decision unit (i.e. the scheduling control unit mentioned above), messages received by the input adaptation decision unit, messages issued by the output adaptation decision unit, notification connection channels between the decision units, and notifications on each connection channel.

[0254] Specifically, the input adaptation unit listens to messages from multiple topics and converts them into internal notifications for use by other units. The scheduling control unit receives notifications from other units and controls the execution of business flows. The output adaptation unit converts the received internal notifications into external messages and publishes them to the associated message topics.

[0255] The embodiment of the present application provides a business decision processing method, a decision module, an electronic device and a readable storage medium. The decision module of the embodiment of the present application includes a distributed decision network, the distributed decision network has a first decision unit, and a second decision unit topologically connected to the first decision unit, the first decision unit includes a connector, an input queue and a decision engine, wherein the connector is connected to the second decision unit, the connector is configured to obtain a target message input by the second decision unit, the input queue is connected to the connector, the input queue is configured to convert the target message into an internal notification, the decision engine is connected to the input queue, and is configured to match the target decision fragment in the decision library according to the internal notification, and when the target decision fragment is matched, Execute the decision action corresponding to the target decision fragment, so that the embodiment of the present application forms a processing process through dynamic series connection of decision fragments, and adopts a distributed decision network to drive process execution, so as to be able to respond to various sudden requests and states in lifecycle management activities in real time. Compared with the BPMN process engine, the distributed mode of the present application provides better concurrent processing and expansion capabilities, which can improve the efficiency of lifecycle management, and the actions are triggered by conditions, so that the system works under the drive of conditions. The architecture ensures that various influencing factors can be processed at any time, thereby obtaining higher control accuracy, effectively improving the accuracy of lifecycle management in specific applications, and thus solving the technical problems of low efficiency and accuracy of lifecycle management methods in applications.

[0256] It is worth mentioning that the embodiment of the present application uses decision fragments to dynamically connect in series to form a processing process. Unlike the existing solution that uses processes to define activities, the embodiment of the present application believes that lifecycle management is essentially a decision-making process driven by multiple factors, and the execution of actions in the process is triggered by conditions rather than pre-arranged. When the conditions match, the corresponding action is executed. The result of executing the action leads to new condition matching, so that the execution process of the action flow can continue. Each of the above actions and its execution conditions form a decision fragment. The dynamic concatenation of decision fragments forms the actual processing process. The advantages of this solution are:

[0257] 1. There is no need to manually specify the execution order, so actions that meet the conditions can be run concurrently, improving processing efficiency;

[0258] 2. Actions are triggered by conditions, so that the system works under the drive of conditions. Therefore, the architecture ensures that various influencing factors can be handled at any time, thereby achieving higher control accuracy and being able to respond to various sudden requests and states in life cycle management activities in real time;

[0259] 3. The decision fragments have a simple structure and single responsibilities. They do not depend on each other and are therefore highly stable. They can be replaced individually and can adapt to adjustments in control requirements at a relatively low modification cost, thus improving the system's flexibility in responding to changes. In addition, they can describe control management activities with a simple structure in a variety of scenarios, from simple to complex.

[0260] Therefore, compared with the process engine, the embodiment of the present invention adopts a distributed processing process by dynamically connecting decision fragments in series, which can provide better concurrent processing and expansion capabilities.

[0261] In a possible implementation, the decision engine is further configured to:

[0262] Modify the object property of the context object according to the internal notification;

[0263] Using the modified object attributes as target object attributes, checking whether there is a target decision fragment matching the target object attributes in the decision library;

[0264] In the case that there is a target decision segment that matches the target object attribute, it is determined that the target decision segment is matched.

[0265] In an practicable manner, the decision engine is further configured to:

[0266] In the case where the decision action is to modify the object attributes of the context object, the execution returns to the step of taking the modified object attributes as the target object attributes and checking whether there is a target decision fragment matching the target object attributes in the decision library, until there is a target decision fragment matching the target object attributes in the decision library, and the decision action is to publish a notification.

[0267] In a possible implementation, the decision module further includes a designer, and each decision segment in the decision library is designed by the designer.

[0268] Exemplarily, the designer includes a first designer and / or a second designer,

[0269] The first designer is configured to arrange the topological structure of the topological connection of each decision unit in the distributed decision network, and the second designer is configured to design each decision segment in the decision library.

[0270] The decision module provided in the embodiment of the present invention adopts the business decision processing method of the above embodiment, which can solve the technical problems of low efficiency and low precision in the application of the lifecycle management method. Compared with the prior art, the beneficial effects of the decision module provided in the embodiment of the present invention are the same as the beneficial effects of the business decision processing method provided in the above embodiment, and the other technical features in the decision module are the same as the features disclosed in the above embodiment method, which will not be repeated here.

[0271] Fig.10 The structural block diagram of an electronic device 1800 shown in an exemplary embodiment of the present application is shown. The electronic device can be implemented as a cloud terminal management platform in the above-mentioned solution of the present application or a cloud server with a cloud terminal. The electronic device 1800 includes a central processing unit (CPU) 1801, a system memory 1804 including a random access memory (RAM) 1802 and a read-only memory (ROM) 1803, and a system bus 1805 connecting the system memory 1804 and the central processing unit 1801. The electronic device 1800 also includes a storage device 1806 for storing an operating system 1809, a client 1810 and other program modules 1811.

[0272] Without loss of generality, the computer-readable medium may include computer storage media and communication media. Computer storage media include volatile and non-volatile, removable and non-removable media implemented by any method or technology for storing information such as computer-readable instructions, data structures, program modules or other data. Computer storage media include RAM, ROM, Erasable Programmable Read Only Memory (EPROM), Electronically-Erasable Programmable Read-Only Memory (EEPROM) flash memory or other solid-state storage technology, CD-ROM, Digital Versatile Disc (DVD) or other optical storage, cassettes, tapes, disk storage or other magnetic storage devices. Of course, those skilled in the art will appreciate that the computer storage medium is not limited to the above. The above-mentioned system memory 1804 and storage device 1806 can be collectively referred to as memory.

[0273] According to various embodiments of the present disclosure, the electronic device 1800 can also be connected to a remote computer on the network through a network such as the Internet. That is, the electronic device 1800 can be connected to the network 1808 through the network interface unit 1807 connected to the system bus 1805, or the network interface unit 1807 can be used to connect to other types of networks or remote computer systems (not shown).

[0274] The memory also includes at least one instruction, at least one program, code set or instruction set, and the at least one instruction, at least one program, code set or instruction set is stored in the memory. The central processing unit 1801 implements all or part of the steps in the business decision processing method shown in the above-mentioned embodiments by executing the at least one instruction, at least one program, code set or instruction set.

[0275] In an exemplary embodiment, a computer-readable storage medium is also provided, wherein at least one computer program is stored in the computer-readable storage medium, and the computer program is loaded and executed by a processor to implement all or part of the steps in the above-mentioned business decision processing method, or to implement all or part of the steps in the above-mentioned business decision processing method. For example, the computer-readable storage medium may be a read-only memory (ROM), a random access memory (RAM), a compact disc read-only memory (CD-ROM), a magnetic tape, a floppy disk, an optical data storage device, etc.

[0276] In an exemplary embodiment, a computer program product is also provided, which includes at least one computer program, which is loaded by a processor and executes all or part of the steps in the above-mentioned business decision processing method shown in any of the above-mentioned embodiments, or all or part of the steps in the above-mentioned business decision processing method.

[0277] Those skilled in the art will readily appreciate other embodiments of the present application after considering the specification and practicing the invention disclosed herein. The present application is intended to cover any modification, use or adaptation of the present application, which follows the general principles of the present application and includes common knowledge or customary techniques in the art that are not disclosed in the present application. The specification and examples are intended to be exemplary only, and the true scope and spirit of the present application are indicated by the claims.

[0278] It should be understood that the present application is not limited to the precise structures that have been described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present application is limited only by the appended claims.

Claims

1. A decision module, characterized in that: The invention comprises a distributed decision network, wherein the distributed decision network comprises a first decision unit and a second decision unit topologically connected to the first decision unit, wherein the first decision unit comprises: A connector, connected to the second decision unit, and configured to obtain a target message input by the second decision unit; an input queue, connected to the connector, configured to convert the target message into an internal notification; A decision engine is connected to the input queue and is configured to match the target decision fragment in the decision library according to the internal notification; when the target decision fragment is matched, the decision action corresponding to the target decision fragment is executed, wherein the decision action includes publishing a notification and / or modifying the object attributes of the context object.

2. The decision module according to claim 1, characterized in that: The decision engine is further configured to: Modify the object property of the context object according to the internal notification; Using the modified object attributes as target object attributes, checking whether there is a target decision fragment matching the target object attributes in the decision library; In the case that there is a target decision segment that matches the target object attribute, it is determined that the target decision segment is matched.

3. The decision module according to claim 2, characterized in that: The decision engine is further configured to: In the case where the decision action is to modify the object attributes of the context object, the execution returns to the step of taking the modified object attributes as the target object attributes and checking whether there is a target decision fragment matching the target object attributes in the decision library, until there is a target decision fragment matching the target object attributes in the decision library, and the decision action is to publish a notification.

4. The decision module according to claim 1, characterized in that: The distributed decision network further includes a third decision unit topologically connected to the first decision unit, the first decision unit further includes an output queue, the decision engine, the output queue and the third decision unit are connected in sequence, and the output queue is set as: In the case where the decision action is to issue a notification, a target notification corresponding to the target decision segment is output to the third decision unit.

5. The decision module according to any one of claims 1 to 4, characterized in that: The decision module also includes a first designer, which is configured to arrange the topological structure of the topological connections of the decision units in the distributed decision network.

6. The decision module according to any one of claims 1 to 4, characterized in that: The decision module also includes a second designer, which is configured to design each decision segment in the decision library.

7. The decision module according to any one of claims 1 to 4, characterized in that: The connector is also configured to: A plurality of message topics generated by the second decision unit are obtained, and a message topic required by the current business is filtered out from the various message topics as a target message input by the second decision unit.

8. A business decision processing method, characterized in that: include: Obtaining a target message input by a message producer, and converting the target message into an internal notification; According to the internal notification, matching the target decision fragment in the decision library; When the target decision fragment is matched, a decision action corresponding to the target decision fragment is executed, wherein the decision action includes publishing a notification and / or modifying an object attribute of a context object.

9. The business decision processing method according to claim 8, characterized in that: The method further comprises: When the decision action is to publish a notification, a target notification corresponding to the target decision fragment is output to a message consumer.

10. The business decision processing method according to claim 8, characterized in that: The step of matching the target decision fragment in the decision library according to the internal notification includes: Modify the object property of the context object according to the internal notification; Using the modified object attributes as target object attributes, checking whether there is a target decision fragment matching the target object attributes in the decision library; In the case that there is a target decision segment that matches the target object attribute, it is determined that the target decision segment is matched.

11. The business decision processing method according to claim 10, characterized in that: After the step of executing the decision action corresponding to the target decision segment, the method further includes: In the case where the decision action is to modify the object attributes of the context object, return to the execution: the step of taking the modified object attributes as the target object attributes, and checking whether there is a target decision fragment matching the target object attributes in the decision library, until there is a target decision fragment matching the target object attributes in the decision library, and the decision action corresponding to the target decision fragment is to publish a notification.

12. The business decision processing method according to any one of claims 8 to 11, characterized in that: The step of obtaining the external message input by the message producer comprises: Obtain multiple message topics generated by the message producer, filter out the message topic required by the current business from the various message topics, and use it as the target message input by the message producer.

13. The business decision processing method according to any one of claims 8 to 11, characterized in that: Each decision segment in the decision library is designed by a designer.

14. An electronic device, characterized in that: The electronic device includes a processor and a memory, wherein the memory stores programs or instructions that can be run on the processor, and when the programs or instructions are executed by the processor, the business decision processing method as described in any one of claims 8 to 13 is implemented.

15. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a program or instruction, and when the program or instruction is executed by the processor, the business decision processing method according to any one of claims 8 to 13 is implemented.

Images