Business function building method and device and business function execution method and device
Through the setting of functional node parameters and the association of relation nodes, sub-function modules are independently determined and executed, which solves the complexity of business function construction in the existing technology, and realizes the simplified business function construction and execution process.
Patent Information
- Application Number
- CN202310569084.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2023-05-16
- Publication Date
- 2024-11-22
AI Technical Summary
In the prior art, users need to learn the underlying code logic when building business functions, which leads to the need to consider its impact on other subfunctions when setting up a subfunction, which seems cumbersome and complicated.
By responding to the parameter setting operation of the functional node, an execution node corresponding to the functional node is obtained, and a relation node is associated with each execution node to determine the sub-function modules, and each sub-function module executes independently to avoid mutual influence.
Users can build and execute business functions without learning the underlying code. Each sub-function module executes independently, simplifying the business function construction process and reducing the complexity of considering the impact of other sub-functions.
Smart Images

Figure CN119002994A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the field of rule engine technology, and in particular to a business function construction method, business function execution method and device. Background Art
[0002] As user demands gradually increase, the business functions that need to be implemented in various scenarios are also increasing. Common business functions include data push and fault statistics.
[0003] In the prior art, when a user wants to build a complete business function, he needs to learn the writing logic of the underlying code, so as to edit each execution action required to implement the business function in the code. Business functions usually include multiple sub-functions. Considering that the sub-functions in the underlying code are usually interrelated, when setting one of the sub-functions, it is usually necessary to consider whether it will affect the implementation of other sub-functions. This is obviously troublesome for users, so it is necessary to provide a more convenient business function building method. Summary of the invention
[0004] In order to overcome the problems existing in the related art, this specification provides a business function construction method, a business function execution method and a device.
[0005] According to a first aspect of an embodiment of this specification, a method for building a business function is provided, including:
[0006] In response to a parameter setting operation for a plurality of functional nodes, obtaining execution nodes corresponding to the plurality of functional nodes one by one, each of the execution nodes being capable of executing at least part of the actions in the business function based on the parameters in the parameter setting operation;
[0007] When it is detected that a first relationship node is associated with each of the execution nodes and there are at least two first relationship nodes, at least two sub-function modules corresponding to the at least two first relationship nodes are determined; each of the sub-function modules includes a corresponding first relationship node and at least one execution node associated with the first relationship node, and each of the first relationship nodes is used to define the execution logic of at least one execution node associated with the first relationship node;
[0008] Based on the at least two sub-functional modules, corresponding business functions are constructed.
[0009] According to a second aspect of an embodiment of the present specification, a method for executing a business function is provided. The method is executed by a rule engine, wherein the rule engine includes at least two independent sub-function modules, each of which includes: a relationship node, and at least one execution node associated with the relationship node; each of the execution nodes is used to execute at least part of the actions in the business function, and each of the relationship nodes is used to limit the execution logic of at least one execution node associated with it; the method includes:
[0010] In response to a start-up operation on the rule engine, determining a first relationship node in each of the sub-function modules;
[0011] Determine a first execution logic of at least one execution node associated with the first relationship node;
[0012] Based on the first execution logic, the execution node is executed.
[0013] According to a third aspect of an embodiment of this specification, a service function building device is provided, the device comprising:
[0014] A first response module, configured to obtain, in response to a parameter setting operation for a plurality of functional nodes, execution nodes corresponding one to one to the plurality of functional nodes, each of the execution nodes being capable of executing at least part of the actions in the business function based on the parameters in the parameter setting operation;
[0015] A first determination module is configured to determine at least two sub-function modules corresponding to the at least two first relationship nodes when it is detected that a first relationship node is associated with each of the execution nodes and there are at least two first relationship nodes; each of the sub-function modules includes a corresponding first relationship node and at least one execution node associated with the first relationship node, and each of the first relationship nodes is used to define the execution logic of at least one execution node associated with the first relationship node;
[0016] A building module is used to build corresponding business functions based on the at least two sub-function modules.
[0017] According to a fourth aspect of an embodiment of the present specification, a business function execution device is provided, the device is executed by a rule engine, the rule engine includes at least two independent sub-function modules, each of the sub-function modules includes: a relationship node, and at least one execution node associated with the relationship node; each of the execution nodes is used to execute at least part of the actions in the business function, and each of the relationship nodes is used to limit the execution logic of at least one execution node associated with it; the device includes:
[0018] A second response module, configured to determine a first relationship node in each of the sub-function modules in response to a start operation on the rule engine;
[0019] A second determination module, configured to determine a first execution logic of at least one execution node associated with the first relationship node;
[0020] An execution module is used to execute the execution node based on the first execution logic.
[0021] According to a fifth aspect of the embodiments of this specification, a computer-readable storage medium is provided, on which a computer program is stored, and when the program is executed by a processor, the steps of any method described in the embodiments provided in the first aspect or the second aspect are implemented.
[0022] According to the sixth aspect of the embodiments of this specification, a computer device is provided, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor; wherein the processor is configured to execute the steps of any method described in the embodiments provided in the first aspect or the second aspect.
[0023] The technical solutions provided by the embodiments of this specification may have the following beneficial effects:
[0024] In the embodiments of this specification, by responding to the parameter setting operation for the function node, an execution node capable of executing at least part of the actions in the business function can be directly obtained without learning the underlying code.
[0025] After obtaining the execution node, by associating a first relationship node for each execution node, when there are at least two first relationship nodes, at least one execution node associated with each first relationship node can be determined, thereby determining the sub-function modules corresponding to the at least two first relationship nodes one by one, and then obtaining at least two sub-function modules, each of which includes one of the first relationship nodes and the execution node associated with the first relationship node, and the execution nodes in the sub-function modules can be executed according to the execution logic restricted by the first relationship nodes. Since the sub-function modules are independent of each other, when setting the parameters of the execution node of any sub-function module, there is no need to consider whether it will affect other sub-function modules.
[0026] It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present specification. BRIEF DESCRIPTION OF THE DRAWINGS
[0027] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the specification and, together with the description, serve to explain the principles of the specification.
[0028] Figure 1 A flow chart of a method for establishing a business function provided in an embodiment of this specification is shown.
[0029] Figure 2 An application scenario diagram of a business function building method provided in an embodiment of this specification is shown.
[0030] Figure 3 An application scenario diagram of another business function building method provided in an embodiment of this specification is shown.
[0031] Figure 4 A flow chart of a method for executing a business function provided in an embodiment of this specification is shown.
[0032] Figure 5 A schematic diagram of the structure of a business function building device provided in an embodiment of this specification is shown.
[0033] Figure 6 A schematic diagram of the structure of a business function execution device provided in an embodiment of this specification is shown.
[0034] Figure 7 A hardware structure diagram of a computer device provided in an embodiment of this specification is shown. DETAILED DESCRIPTION
[0035] 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, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The implementations described in the following exemplary embodiments do not represent all implementations consistent with this specification. Instead, they are merely examples of devices and methods consistent with some aspects of this specification as detailed in the appended claims.
[0036] The terms used in this specification are for the purpose of describing specific embodiments only and are not intended to limit this specification. The singular forms "a", "the" and "the" used in this specification and the appended claims are also intended to include plural forms unless the context clearly indicates otherwise. It should also be understood that the term "and / or" used herein refers to and includes any or all possible combinations of one or more associated listed items.
[0037] It should be understood that although the terms first, second, third, etc. may be used in this specification to describe various information, this information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other. For example, without departing from the scope of this specification, the first information may also be referred to as the second information, and similarly, the second information may also be referred to as the first information. Depending on the context, the word "if" as used herein may be interpreted as "at the time of" or "when" or "in response to determining".
[0038] As user demands gradually increase, the business functions that need to be implemented in various scenarios are also increasing. Common business functions include data push and fault statistics.
[0039] In the prior art, when a user wants to build a complete business function, he needs to learn the writing logic of the underlying code, so as to edit each execution action required to implement the business function in the code. Business functions usually include multiple sub-functions. Considering that the sub-functions in the underlying code are usually interrelated, when setting one of the sub-functions, it is usually necessary to consider whether it will affect the implementation of other sub-functions.
[0040] For example, a business function needs to perform the following actions:
[0041] Action 1: Determine whether the system is faulty.
[0042] Action 2: When the system fails, the fault information is sent to port 1.
[0043] Action 3: When the system is not faulty, send the information that there is no fault to port 2.
[0044] When implementing the above business functions, the prior art usually divides them according to the functions corresponding to each action. For example, the function of action one is judgment, and the functions of action two and action three are data transmission. And because both action two and action three need to obtain the judgment result of action one, action one is usually used as a sub-function (such as sub-function one) to judge whether the system is faulty; action two and action three are evenly divided into sub-function two to realize data transmission, and the implementation scheme of the above business functions is:
[0045] Execute sub-function one, determine whether the system fails, and send the determination result of sub-function one to sub-function two.
[0046] Execute sub-function 2: When it is determined that sub-function 1 determines that the system is faulty, execute action 2; when it is determined that sub-function 1 determines that the system is not faulty, execute action 3.
[0047] It can be seen that these two sub-functions are usually interrelated and interdependent. Therefore, when setting the parameters in sub-function one (determining whether the system is faulty), it is necessary to consider whether sub-function two can be realized (it can be related to both action two and action three). When the business function is more complex and contains more sub-functions, this setting method needs to consider many situations, which is obviously troublesome for users. Therefore, it is necessary to provide a more convenient business function construction method.
[0048] Next, the embodiments of this specification are described in detail. The following embodiments are applied to the business end to assist users in completing the construction of business functions (or the execution of business functions). The business end corresponds to a server end (the server end can be set at the business end or can be independent of the business end). The server end is used to receive the user's operations in the business end and feedback the corresponding execution results. The server end is connected to a database for storing relevant data of the business functions.
[0049] Figure 1 A flowchart of a method for building a business function provided by an embodiment of this specification is shown. Figure 1 As shown, the method comprises the following steps:
[0050] Step 101, in response to a parameter setting operation for a plurality of functional nodes, obtaining execution nodes corresponding to the plurality of functional nodes one by one, each of the execution nodes being able to execute at least part of the actions in the business function based on the parameters in the parameter setting operation.
[0051] Among them, the function node is a pre-packaged underlying code. Function nodes can be divided into different types of function nodes according to the different actions they can perform, such as function nodes for sending data, function nodes for judging data, function nodes for processing data, function nodes for limiting time intervals, etc. However, regardless of the type of function node, it is necessary to set corresponding parameters for it, so as to guide the function node to complete the specified action through the parameters set for the function node. Exemplarily, when the function node is used to send data, it is necessary to determine to whom the data is to be sent and what kind of data to send according to the parameters set for it.
[0052] Exemplarily, the parameter setting operation may be generated in the following manner:
[0053] Directly set parameters for a function node that has not yet been set with parameters, and generate a parameter setting operation for this function node.
[0054] Alternatively, directly copy the function node with parameters already set (for example, directly copy and paste the previously generated execution node), in which case the copy operation is used as a parameter setting operation, and the function node with parameters already set obtained by the copy operation is used as an execution node.
[0055] Taking the data push function as an example, this article briefly introduces how to set parameters for function nodes:
[0056] When the service function is a data push function, the response to the parameter setting operation for a plurality of function nodes to obtain execution nodes corresponding to the plurality of function nodes one by one includes the following two setting methods:
[0057] Method 1: For each functional node, in response to a first parameter used to characterize a data push condition in a received parameter setting operation, a first execution node is generated, and the first execution node is used to determine whether the received target data meets the data push condition based on the first parameter.
[0058] Among them, the first execution node is an execution node for executing a judgment action, so the judgment condition of the first execution node needs to be set in the parameter setting operation. Since the business function is a business push function, the judgment action that the business function needs to perform at this time is: judging under what circumstances data push is required. Therefore, the parameter that needs to be set in the parameter setting operation is: the first parameter for characterizing the data push condition.
[0059] For example, the data push condition is: the received target data indicates an air conditioner failure. At this time, when the first execution node receives the target data, it can complete the judgment action required in the business function by judging whether the target data meets the data push condition. Alternatively, the data push condition is: the received target data is generated within the time interval of 20:00-23:00.
[0060] Or in the second mode, for each functional node, in response to the second parameter used to characterize the data to be pushed and the target port in the received parameter setting operation, a first execution node is generated, and the second execution node is used to push the data to be pushed to the target port.
[0061] The second execution node is used to execute the data sending action, so the second execution node needs to send data to whom (target port) and what kind of data (data to be pushed) to be sent are set through parameter setting operation. For example, the data to be pushed is set as prompt information used to characterize air conditioner failure (or air conditioner is not faulty), and the target port is set as: user end (or background service end, or maintenance end).
[0062] Through the above manner, after performing parameter setting operations on each functional node, an execution node corresponding to each functional node can be obtained, thereby obtaining a plurality of execution nodes.
[0063] Step 102, when it is detected that a first relationship node is associated with each of the execution nodes and there are at least two first relationship nodes, at least two sub-function modules corresponding one to one with the at least two first relationship nodes are determined; each of the sub-function modules includes a corresponding first relationship node and at least one execution node associated with the first relationship node, and each of the first relationship nodes is used to limit the execution logic of at least one execution node associated with the first relationship node.
[0064] The method is applied to a business end, which includes an interactive interface so that users can complete the construction of business functions through the interactive interface.
[0065] After executing step 101 to obtain execution nodes corresponding one-to-one to the plurality of function nodes, the execution nodes and at least two first relationship nodes to be associated are added to the interaction interface.
[0066] Exemplarily, the execution node in the interactive interface can be automatically generated after the first execution node is obtained in response to the parameter configuration operation. The first relationship node to be associated can be directly dragged from the taskbar or toolbar to the interactive interface by the user, or it can be generated in the interactive interface after the user clicks on a specified interactive control. The execution node and at least two first relationship nodes to be associated are all located in the user-operable area of the interactive interface. At this time, each execution node and each first relationship node are operable interactive controls.
[0067] The first relationship node is used to define the execution logic of the execution node, which includes but is not limited to: execution order, whether to terminate, whether to execute, etc. When the various execution nodes are associated together through the first relationship node, the execution logic will also become complicated. For example, the execution logic may represent: only executing a few of the execution nodes, or executing each execution node in a specific order, etc. Therefore, it is necessary to set a first relationship node for each execution node to determine the execution logic of the execution node.
[0068] After the execution node and at least two first relationship nodes to be associated are added to the interactive interface, when it is detected that one first relationship node is associated with each execution node and there are at least two first relationship nodes, at least two sub-function modules corresponding to the at least two first relationship nodes are determined, including the following steps:
[0069] In response to detecting an operation of connecting at least one execution node in the interaction interface to one of the relationship nodes to be associated, an association relationship between the at least one execution node and the first relationship node to be associated is established. When it is determined based on the association relationship that each of the execution nodes in the interaction interface is associated with a first relationship node, and the number of first relationship nodes in the association relationship is at least two, at least two sub-function modules are determined based on at least one execution node associated with the first relationship node in each of the association relationships.
[0070] In the interactive interface, the user can select one or more execution nodes at the same time, and establish a connection between at least one selected execution node and one of the relationship nodes to be associated by connecting lines, marking, etc. When the business end detects the above operation of the user, an association relationship is established between at least one execution node and the relationship node to be associated.
[0071] When it is detected that each execution node in the interactive interface is associated with a corresponding first relationship node, at least one sub-function module can be generated according to the association relationship between the execution node and the first relationship node. When it is determined that the number of first relationship nodes recorded in the association relationship is at least two, since each sub-function module includes only one first relationship node and at least one execution node associated with the first relationship node, the number of first relationship nodes is consistent with the number of sub-function modules, and at this time, at least two sub-function modules are obtained according to the association relationship.
[0072] Step 103: Building corresponding business functions based on the at least two sub-function modules.
[0073] By adding the at least two sub-function modules, the at least two sub-function modules are combined into a corresponding business function, thereby completing the construction of the business function.
[0074] In the embodiments of this specification, by responding to the parameter setting operation for the function node, an execution node capable of executing at least part of the actions in the business function can be directly obtained without learning the underlying code.
[0075] After obtaining the execution node, by associating a first relationship node for each execution node, when there are at least two first relationship nodes, at least one execution node associated with each first relationship node can be determined, thereby determining the sub-function modules corresponding to the at least two first relationship nodes one by one, and then obtaining at least two sub-function modules, each of which includes one of the first relationship nodes and the execution node associated with the first relationship node, and the execution nodes in the sub-function modules can be executed according to the execution logic restricted by the first relationship nodes. Since the sub-function modules are independent of each other, when setting the parameters of the execution node of any sub-function module, there is no need to consider whether it will affect other sub-function modules.
[0076] In a feasible implementation scheme, when building business functions, in order to meet more abundant business functions, the execution logic between the sub-function modules may be further considered. The execution step 103 is based on the at least two sub-function modules and includes the following steps:
[0077] In response to the operation of associating the at least two sub-function modules to at least one second relationship node, the business function is constructed; the second relationship node is used to define the execution logic between the at least two sub-function modules.
[0078] The function of the second relationship node is similar to that of the first relationship node, except that the second relationship node is used to associate various sub-functional modules, thereby determining the order in which the sub-functional modules are executed, whether each execution module is executed, whether to stop, etc. by limiting the execution logic of the sub-functional modules.
[0079] It should be noted that, since each sub-function module includes a first relationship node and at least one execution node associated with the first relationship node, if the second relationship node is directly associated with the execution node, the execution logic defined by the first relationship node will be disrupted. Therefore, when the sub-function module is associated with the second associated node, the second relationship node is actually associated with the first relationship node, and the logical relationship of the first relationship node is further defined by the second relationship node.
[0080] Through the above method, when the number of sub-function modules is limited, the sub-function modules can be flexibly matched to meet the needs of richer business function settings.
[0081] In a feasible embodiment, the method further comprises the following steps:
[0082] For each of the execution nodes, when the execution node is the first execution node, a relationship between the execution node and a preset data source port is established; and data received from the data source port is determined as the target data.
[0083] Since the first execution node is used to execute the judgment action in the business function, it is necessary to first receive the target data in order to determine whether the target data meets the conditions corresponding to the parameters in the first execution node. If the data source port corresponding to the first execution node is not restricted, any data received will trigger the first execution node to make a judgment (which will cause the first execution node to be continuously occupied, affecting normal functions). Therefore, by setting the data source port, the data sent by the data source port can be determined as the target data, so that the first execution node will only be triggered by the data (target data) sent by the data source port, which can avoid the first execution node from performing redundant operations or avoiding the first execution node from being occupied.
[0084] Exemplarily, the data source port can be a data transmission interface of a certain application. For example, when the business function is used for fault reminder, the first execution node needs to receive the diagnostic data reported by the vehicle diagnostic system, and then determine whether the diagnostic data indicates that the vehicle has a fault. In this case, the data source port is the vehicle diagnostic system, and the target data is the diagnostic data sent by the vehicle diagnostic system.
[0085] It should be noted that the data source port is directly configured to the execution node in the form of parameters. For example, the unique identifier of the data source port is configured as one of the parameters to the function node to obtain the corresponding execution node. The parameters in the parameter setting operation are the execution rules that the user wants to set when the execution node is executed, so as to guide the function node to complete the specified action according to the execution rules set by the user. Based on this, the parameters set for the function node include but are not limited to:
[0086] The unique identifier of the data source port (or the unique identifier generated for the application corresponding to the data source interface), the name of the application corresponding to the data source port, whether the application is available, the relationship between the function node and the data source interface, the program code required for the parameters, the type of function node, the data to be pushed, the target port for receiving the data to be pushed, the path used to reach the target port, and the time period when the function node is effective (for example, the function node will only take effect from 19:00 to 20:00 every day, and at other times it is assumed that the function node is invalid, and the nodes associated with the function node are also invalid at the same time).
[0087] In a feasible implementation scheme, the first relationship node and the second relationship node both belong to relationship nodes; each task to be executed associated with the relationship node is executed in sequence according to a preset execution order; when the relationship node is the first relationship node, the task to be executed is the execution node, and when the relationship node is the second relationship node, the task to be executed is the sub-function module.
[0088] The preset execution order may be determined based on the connection order between the tasks to be executed and the relationship nodes (eg, from top to bottom, from front to back), or may be determined based on the execution order after setting the execution order for each task to be executed.
[0089] The relationship node is used to limit the execution logic of at least one to-be-executed task associated with the relationship node, including the following three situations: Figure 2 An application scenario diagram of a business function building method provided by an embodiment of this specification is shown, such as Figure 2 As shown, a relationship node is associated with two pending tasks (pending task 1 and pending task 2). Figure 2 The following three situations are described:
[0090] Case 1: when the type of the relationship node is the first type, the execution logic of the at least one task to be executed is: in response to the failure of execution of any of the tasks to be executed, stop executing each of the tasks to be executed.
[0091] Assume that the type of the relationship node is the first type and the execution order is from top to bottom. At this time, the first task to be executed is executed first. If the first task to be executed is executed successfully, the relationship node receives the information that the first task to be executed is executed successfully, and then the second task to be executed is triggered and executed. If the first task to be executed fails, then after the relationship node receives the information that the first task to be executed fails, each task to be executed associated with this relationship node stops executing.
[0092] For example, a sub-function module is used as an example for explanation, and the sub-function module includes the first execution node, the second execution node, and target relationship nodes respectively associated with the first execution node and the second execution node. When the type of the target relationship node is the first type, and the execution order of the first execution node is earlier than the execution order of the second execution node, the execution logic between the execution nodes in the sub-function module is:
[0093] triggering the first relationship node;
[0094] The target first relationship node triggers the second execution node when receiving the information that the first execution node determines that the target data meets the data push condition.
[0095] by Figure 2 Take this as an example to explain. Figure 2The relationship node in is the first relationship node, the task to be executed one is the first execution node, and the task to be executed two is the second execution node. Therefore, the task to be executed one is used to determine whether the received target data meets the data push conditions; the node to be executed two is used to push the data to be pushed to the target port.
[0096] Therefore, when it is determined in the first task to be executed that the target data meets the data push conditions, a success flag is sent to the relationship node to indicate successful execution; when it is determined in the first task to be executed that the target data does not meet the data push conditions, a failure flag is sent to the relationship node to indicate failure.
[0097] When the relationship node is of the first type, in response to receiving that the execution of the pending task 1 fails, it is considered that the target data does not meet the data push condition in the pending task 1, and it is not necessary to execute the data push task in the pending task 2 at this time, so the pending task 2 is not executed. In response to receiving that the execution of the pending task 1 succeeds, it is considered that the target data meets the data push condition in the pending task 1, and it is necessary to send the data to be pushed to the target port by executing the pending task 2.
[0098] Case 2: when the type of the relationship node is the second type, the execution logic of the at least one task to be executed is: in response to the successful execution of any of the tasks to be executed, stop executing each of the tasks to be executed.
[0099] Assume that the type of the relationship node is the second type and the execution order is from top to bottom. At this time, the first task to be executed is executed first. If the first task to be executed is executed successfully, then the relationship node receives the information that the first task to be executed is executed successfully, and then each task to be executed associated with this relationship node stops executing; if the first task to be executed fails, then after the relationship node receives the information that the first task to be executed fails, the second task to be executed is triggered and executed.
[0100] Case three: when the type of the relationship node is the third type, the execution logic of the at least one task to be executed is: in response to each of the at least one task to be executed being completed, stop executing each of the tasks to be executed.
[0101] Assuming that the type of the relationship node is the third type and the execution order is from top to bottom, at this time, the first task to be executed is executed first, and after the first task to be executed is completed, regardless of the execution result of the first task to be executed, the second task to be executed is executed.
[0102] Figure 3 An application scenario diagram of another business function building method provided by an embodiment of this specification is shown, such as Figure 3As shown, sub-function module one includes: relationship node one (first relationship node), and an execution node associated with relationship node one; sub-function module two includes: relationship node two (first relationship node), and an execution node associated with relationship node two; sub-function module three includes: relationship node three (first relationship node), and an execution node associated with relationship node three.
[0103] The sub-function module 1, the sub-function module 2 and the sub-function module 3 are associated together through a plurality of second relationship nodes (relationship node 4, relationship node 5).
[0104] The following is a business function that indicates a fault. Figure 3 The execution logic is explained as follows:
[0105] The business functions need to complete the following tasks:
[0106] After receiving the fault data, the vehicle diagnostic system needs to push the fault information (including air conditioning fault and power system fault) to different business platforms or responsible persons. The push content is as follows:
[0107] Push content: When the air conditioning system is confirmed to be faulty, the information about the air conditioning system fault will be pushed to platform A;
[0108] When a power system failure is determined, the information of the power system failure is sent to the B platform, and when it is determined that the power system failure occurs between 20:00 and 23:00 every day, the information of the power system failure is pushed to the C platform.
[0109] Requirement: If the information about the air conditioning system failure has been pushed, the information about the power system failure will not be pushed.
[0110] At this time, it is first necessary to be able to receive the fault data sent by the vehicle diagnostic system and process (judge) it as target data. Therefore, it is necessary to use the port where the vehicle diagnostic system sends the fault data as the data source port.
[0111] Secondly, determine that three independent sub-function modules need to be set up to execute:
[0112] Sub-function 1: When the air-conditioning system fails, the information of the air-conditioning system failure is pushed to the A platform.
[0113] Sub-function 2: When the power system fails, the information of the power system failure is pushed to the B platform.
[0114] Sub-function three: when a power system failure occurs between 20:00 and 23:00 every day, the information of the power system failure is pushed to the C platform.
[0115] Therefore, the following three sub-function modules are set:
[0116] In the sub-function module 1: the execution node 1 is used to determine whether the air conditioning system fails according to the received target data, and the execution node 2 is used to push the information of the air conditioning system failure to the A platform. The execution node 1 and the execution node 2 are associated through the relationship node 1 (first relationship node).
[0117] In sub-function module 2: execution node 3 is used to determine whether it is a power system failure according to the received target data, and execution node 4 is used to push the information of the power system failure to platform B. Execution node 3 and execution node 4 are associated through relationship node 2 (first relationship node).
[0118] In the sub-function module 2: the execution node 5 is used to determine whether it is a power system fault according to the received target data, and whether the generation time of the target data is between 20:00 and 23:00 (wherein, the time interval can be directly set in the relationship node 3, or the execution node 7 can be added between the execution node 5 and the execution node 6, and the judgment condition in the execution node 7 is: whether the generation time of the target data is within the interval of 20:00-23:00), and the execution node 6 is used to push the information of the power system fault to the C platform. The execution node 5 and the execution node 6 are associated through the relationship node 3 (the first relationship node).
[0119] The execution order of the execution nodes associated with each first relationship node is preset to be executed from top to bottom. The types of the above relationship nodes 1, 2, and 3 are all of the first type (only when the previous execution node is successfully executed can the next execution node be executed, and the failure of any execution node will cause each execution node in the current sub-function module to stop executing).
[0120] At this time, the business function also requires that if the information about the air-conditioning system failure has been pushed, the information about the power system failure will no longer be pushed.
[0121] Therefore, each sub-function module does not necessarily need to be executed in full. When sub-function module 1 is successfully executed, sub-function module 2 and sub-function module 3 do not need to be executed. Sub-function module 2 and sub-function module 3 both need to be executed, so the type of relationship node 4 associated with sub-function module 2 and sub-function module 3 is the first type, and the type of relationship node 5 associated with relationship node 1 and relationship node 4 is the second type.
[0122] The execution order of the sub-function modules associated with the above second relationship nodes (relationship node four and relationship node five) is from top to bottom.
[0123] In this way, after sub-function module 1 is successfully executed (pushed to platform A, and returns to relationship node 1: success mark), relationship node 1 will feedback to relationship node 5: success mark. At this time, since the type of relationship node 5 is the second type, the tasks to be executed associated with relationship node 5 (sub-function module 2 and sub-function module 3) are stopped.
[0124] Figure 4 A flowchart of a method for executing a business function provided by an embodiment of the present specification is shown. The method is executed by a rule engine, and the rule engine includes at least two independent sub-function modules, each of which includes: a relationship node, and at least one execution node associated with the relationship node; each of the execution nodes is used to execute at least part of the actions in the business function, and each of the relationship nodes is used to limit the execution logic of at least one execution node associated with it; the method includes the following steps:
[0125] Step 401, in response to a start-up operation on the rule engine, determining a relationship node in each of the sub-function modules.
[0126] Step 402: Determine, based on the relationship node, the execution logic of at least one execution node associated with the relationship node.
[0127] Step 403: Execute the execution node based on the execution logic.
[0128] Among them, the startup operation for the rule engine can be generated by the user directly clicking the startup control, or it can be automatically generated after receiving data from a designated port, or it can be automatically generated according to a specific cycle. The business function in this embodiment is built according to the business function building method described above and executed by the rule engine. The relevant contents involved in the above steps 401 to 403 have been described in the above embodiments and will not be repeated here.
[0129] It should be noted that when the business function is used for fault reminder business, the start operation of the rule engine is triggered after receiving the target data, so that the target data is judged through the sub-function module to determine whether the target data meets the data push conditions.
[0130] In a feasible implementation manner, the at least two sub-functional modules are associated with at least one second relationship node; the second relationship node is used to define the execution logic between the at least two sub-functional modules.
[0131] When building a business function, in order to meet more abundant business needs, each sub-function module is associated together through the second relationship node, so that there is a corresponding execution logic between at least two sub-function modules. At this time, when determining the first relationship node in each of the sub-function modules in step 401, the following steps are included:
[0132] Based on each of the second relationship nodes, determine the second execution logic of the at least two sub-function modules. Based on the second execution logic, execute each of the sub-function modules. When executing each of the sub-function modules, determine the first relationship node in the sub-function module.
[0133] Since the second relationship node is associated with at least two sub-function modules, and each sub-function module is associated with at least one execution node through the first relationship node, before determining the execution logic of the execution node, it is necessary to first determine the execution logic of at least two sub-function modules according to the second relationship node (for example, which sub-function modules to execute, how to execute each sub-function module, etc.). When executing each sub-function module, it is necessary to consider which execution logic the execution node in the sub-function module is executed according to.
[0134] Through the above method, the execution logic in the business function can be gradually determined according to the hierarchy between the second relationship node - sub-function module - first relationship node - execution node, without having to determine the execution logic between each execution node at the beginning, which helps to improve processing efficiency.
[0135] Take the fault reminder service as an example to explain:
[0136] After the vehicle diagnostic system generates a fault diagnosis data packet, it sends the data packet to the rule engine through the data source port. Since the data packet is sent from the data source port, it is considered to have triggered the rule engine. The rule engine preprocesses the data packet as target data (for example, parses it), and triggers the corresponding sub-function modules and the corresponding execution nodes in the sub-function modules according to the execution logic between the tasks to be processed determined by the relationship node, thereby performing corresponding actions (for example, determining whether the data push conditions are met, pushing the data to be pushed to the target port, etc.).
[0137] After execution is completed, the rule engine traverses each sub-function module and the execution node in each sub-function module, determines the execution status of each execution node and each sub-function module, obtains the traversal results, and notifies the vehicle diagnostic system of the end of the fault reminder service based on the traversal results.
[0138] In a feasible embodiment, the method further comprises the following steps:
[0139] In response to the type modification operation on the relationship node, a relationship node after type modification is obtained, so as to replace the execution logic between each task to be executed based on the type set in the type modification operation. The first relationship node and the second relationship node both belong to the relationship node; when the relationship node is the first relationship node, the task to be executed is the execution node, and when the relationship node is the second relationship node, the task to be executed is the sub-function module.
[0140] When a business function is built and executed, it may be found that the architecture of the business function needs to be adjusted based on the execution results (for example, it was originally necessary to execute each task to be executed, but now only one of the tasks to be executed needs to be executed). In this case, you only need to change the type of relationship nodes connecting the tasks to be executed, and there is no need to rebuild the business function.
[0141] In a feasible embodiment, the method further comprises the following steps:
[0142] For each of the execution nodes, in response to a parameter modification operation on the execution node, an execution node after parameter modification is obtained, so as to replace an action to be performed by the execution node based on the parameters in the parameter modification operation.
[0143] After building a business function, when executing the business function, you may find that you need to readjust a sub-function module of the business function according to the execution result. At this time, you can directly modify the parameters of the execution node in the sub-function module without deleting the execution node and then adding it. In addition, since each execution node is only associated with the sub-function module in which it is located, modifying the parameters of the execution node will not affect the business implementation of other sub-function modules, which is obviously more convenient for users.
[0144] It should be noted that, according to the needs of users, first relationship nodes, second relationship nodes, execution nodes and sub-function modules can be added or deleted in the established business functions. The above operations will not affect the functional implementation of other sub-function modules.
[0145] In one possible embodiment, Figure 5 A schematic diagram of the structure of a business function building device provided in an embodiment of this specification is shown, such as Figure 5 As shown, the device comprises:
[0146] The first response module 501 is used to respond to the parameter setting operation for several functional nodes, obtain execution nodes corresponding to the several functional nodes one by one, and each of the execution nodes can execute at least part of the actions in the business function based on the parameters in the parameter setting operation.
[0147] The first determination module 502 is used to determine at least two sub-function modules corresponding to the at least two first relationship nodes when it is detected that a first relationship node is associated with each of the execution nodes and there are at least two first relationship nodes; each of the sub-function modules includes a corresponding first relationship node and at least one execution node associated with the first relationship node, and each of the first relationship nodes is used to limit the execution logic of at least one execution node associated with the first relationship node.
[0148] The building module 503 is used to build the corresponding business function based on the at least two sub-function modules.
[0149] In a feasible implementation manner, when the building module is used to build a corresponding business function based on the at least two sub-function modules, it is used to:
[0150] In response to the operation of associating the at least two sub-function modules to at least one second relationship node, the business function is constructed; the second relationship node is used to define the execution logic between the at least two sub-function modules.
[0151] In a feasible embodiment, the device further comprises:
[0152] The adding module is used to add the execution node and at least two first relationship nodes to be associated to the interactive interface after obtaining the execution nodes corresponding to the plurality of function nodes one by one.
[0153] When the first determining module is used to determine at least two sub-function modules corresponding to the at least two first relationship nodes in a one-to-one manner when it is detected that a first relationship node is associated with each of the execution nodes and there are at least two first relationship nodes, the first determining module is used to:
[0154] In response to detecting an operation of connecting at least one execution node in the interaction interface to one of the relationship nodes to be associated, an association relationship between the at least one execution node and the first relationship node to be associated is established.
[0155] When it is determined based on the association relationship that each of the execution nodes in the interactive interface is associated with a first relationship node, and the number of first relationship nodes in the association relationship is at least two, at least two sub-function modules are determined based on at least one execution node associated with each first relationship node in the association relationship.
[0156] In a feasible implementation scheme, the business function is a data push function.
[0157] When the first response module is used to obtain execution nodes corresponding to the plurality of functional nodes in one-to-one response to the parameter setting operation for the plurality of functional nodes, it is used to:
[0158] For each functional node, in response to a first parameter used to characterize a data push condition in a received parameter setting operation, a first execution node is generated, and the first execution node is used to determine whether the received target data meets the data push condition based on the first parameter.
[0159] Alternatively, for each functional node, in response to a second parameter used to characterize the data to be pushed and the target port in the received parameter setting operation, a first execution node is generated, and the second execution node is used to push the data to be pushed to the target port.
[0160] In a feasible embodiment, the device further comprises:
[0161] The first establishing module is used to establish, after obtaining the execution nodes corresponding one-to-one to the plurality of functional nodes, for each of the execution nodes, when the execution node is the first execution node, a relationship between the execution node and a preset data source port.
[0162] A third determination module is used to determine the data received from the data source port as the target data.
[0163] In a feasible implementation scheme, the first relationship node and the second relationship node both belong to relationship nodes; each task to be executed associated with the relationship node is executed in sequence according to a preset execution order; when the relationship node is the first relationship node, the task to be executed is the execution node, and when the relationship node is the second relationship node, the task to be executed is the sub-function module.
[0164] The relationship node is used to limit the execution logic of at least one to-be-executed task associated with the relationship node, including:
[0165] When the type of the relationship node is the first type, the execution logic of the at least one task to be executed is: in response to the failure of execution of any of the tasks to be executed, stop executing each of the tasks to be executed; when the type of the relationship node is the second type, the execution logic of the at least one task to be executed is: in response to the successful execution of any of the tasks to be executed, stop executing each of the tasks to be executed; when the type of the relationship node is the third type, the execution logic of the at least one task to be executed is: in response to the completion of execution of each of the at least one task to be executed, stop executing each of the tasks to be executed.
[0166] In one possible embodiment, Figure 6 A schematic diagram of the structure of a service function execution device provided in an embodiment of this specification is shown. Figure 6 As shown, the device is executed through a rule engine, which includes at least two independent sub-function modules, each of which includes: a relationship node, and at least one execution node associated with the relationship node; each of the execution nodes is used to execute at least part of the actions in the business function, and each of the relationship nodes is used to limit the execution logic of at least one execution node associated with it.
[0167] The device comprises:
[0168] The second response module 601 is used to determine the first relationship node in each of the sub-function modules in response to the start operation of the rule engine.
[0169] The second determination module 602 is configured to determine a first execution logic of at least one execution node associated with the first relationship node.
[0170] The execution module 603 is used to execute the execution node based on the first execution logic.
[0171] In a feasible implementation manner, the at least two sub-functional modules are associated with at least one second relationship node; the second relationship node is used to define the execution logic between the at least two sub-functional modules.
[0172] The second response module, when used to determine the first relationship node in each of the sub-function modules in response to the start operation on the rule engine, is used to:
[0173] Based on each of the second relationship nodes, determine the second execution logic of the at least two sub-function modules; based on the second execution logic, execute each of the sub-function modules; when executing each of the sub-function modules, determine the first relationship node in the sub-function module.
[0174] In a feasible embodiment, the device further comprises:
[0175] In response to the type modification operation on the relationship node, a relationship node after type modification is obtained, so as to replace the execution logic between the tasks to be executed based on the type set in the type modification operation.
[0176] The first relationship node and the second relationship node both belong to the relationship node; when the relationship node is the first relationship node, the task to be executed is the execution node, and when the relationship node is the second relationship node, the task to be executed is the sub-function module.
[0177] In a feasible embodiment, the device further comprises:
[0178] For each of the execution nodes, in response to a parameter modification operation on the execution node, an execution node after parameter modification is obtained, so as to replace an action to be performed by the execution node based on the parameters in the parameter modification operation.
[0179] The implementation process of the functions and effects of each module in the above-mentioned device is specifically described in the implementation process of the corresponding steps in the above-mentioned method, which will not be repeated here.
[0180] For the device embodiment, since it basically corresponds to the method embodiment, the relevant parts can refer to the partial description of the method embodiment. The device embodiment described above is only schematic, wherein the modules described as separate components may or may not be physically separated, and the components displayed as modules may or may not be physical modules, that is, they may be located in one place, or they may be distributed on multiple network modules. Some or all of the modules may be selected according to actual needs to achieve the purpose of the scheme of this specification. A person of ordinary skill in the art can understand and implement it without paying creative labor.
[0181] Figure 7 A hardware structure diagram of a computer device provided in an embodiment of this specification is shown, and the device may include: a processor 701, a memory 702, an input / output interface 703, a communication interface 704, and a bus 705. The processor 701, the memory 702, the input / output interface 703, and the communication interface 704 are connected to each other in communication within the device through the bus 705.
[0182] The processor 701 can be implemented using a general-purpose CPU (Central Processing Unit), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits, and is used to execute relevant programs to implement a business function building method or a business function execution method provided in the embodiments of this specification.
[0183] The memory 702 may be implemented in the form of ROM (Read Only Memory), RAM (Random Access Memory), static storage device, dynamic storage device, etc. The memory 702 may store an operating system and other application programs. When the technical solutions provided in the embodiments of this specification are implemented by software or firmware, the relevant program codes are stored in the memory 702 and are called and executed by the processor 701.
[0184] The input / output interface 703 is used to connect the input / output module to realize information input and output. The input / output module can be configured in the device as a component (not shown in the figure), or it can be externally connected to the device to provide corresponding functions. The input device may include a keyboard, a mouse, a touch screen, a microphone, various sensors, etc., and the output device may include a display, a speaker, a vibrator, an indicator light, etc.
[0185] The communication interface 704 is used to connect a communication module (not shown) to realize communication interaction between the device and other devices. The communication module can realize communication through a wired mode (such as USB, network cable, etc.) or a wireless mode (such as mobile network, WIFI, Bluetooth, etc.).
[0186] The bus 705 includes a path for transmitting information between various components of the device (eg, the processor 701 , the memory 702 , the input / output interface 703 , and the communication interface 704 ).
[0187] It should be noted that, although the above device only shows the processor 701, the memory 702, the input / output interface 703, the communication interface 704 and the bus 705, in the specific implementation process, the device may also include other components necessary for normal operation. In addition, it can be understood by those skilled in the art that the above device may also only include the components necessary for implementing the embodiments of the present specification, and does not necessarily include all the components shown in the figure.
[0188] An embodiment of the present specification also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of a business function building method or a business function execution method as described in any one of the embodiments of the present specification.
[0189] Computer readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.
[0190] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.
[0191] The above is a description of a specific embodiment of the specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be performed in an order different from that in the embodiments and still achieve the desired results. In addition, the processes depicted in the drawings do not necessarily require the specific order or continuous order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.
Claims
1. A method for building a business function, characterized in that: include: In response to a parameter setting operation for a plurality of functional nodes, obtaining execution nodes corresponding to the plurality of functional nodes one by one, each of the execution nodes being capable of executing at least part of the actions in the business function based on the parameters in the parameter setting operation; When it is detected that a first relationship node is associated with each of the execution nodes and there are at least two first relationship nodes, at least two sub-function modules corresponding to the at least two first relationship nodes are determined; Each of the sub-function modules includes a corresponding first relationship node and at least one execution node associated with the first relationship node, and each of the first relationship nodes is used to define the execution logic of the at least one execution node associated with the first relationship node; Based on the at least two sub-functional modules, corresponding business functions are constructed.
2. The method according to claim 1, characterized in that The corresponding business functions are constructed based on the at least two sub-function modules, including: In response to the operation of associating the at least two sub-function modules to at least one second relationship node, the business function is constructed; the second relationship node is used to define the execution logic between the at least two sub-function modules.
3. The method according to claim 1, characterized in that After obtaining the execution nodes corresponding one-to-one to the plurality of function nodes, the method further includes: Adding the execution node and at least two first relationship nodes to be associated to the interaction interface; When it is detected that a first relationship node is associated with each of the execution nodes and there are at least two first relationship nodes, determining at least two sub-function modules corresponding to the at least two first relationship nodes in a one-to-one manner includes: In response to detecting an operation of connecting at least one execution node in the interaction interface to one of the relationship nodes to be associated, establishing an association relationship between the at least one execution node and the first relationship node to be associated; When it is determined based on the association relationship that each of the execution nodes in the interactive interface is associated with a first relationship node, and the number of first relationship nodes in the association relationship is at least two, at least two sub-function modules are determined based on at least one execution node associated with each first relationship node in the association relationship.
4. The method according to claim 1, characterized in that: The business function is a data push function; The step of obtaining, in response to the parameter setting operation for the plurality of functional nodes, execution nodes corresponding to the plurality of functional nodes in a one-to-one manner comprises: For each functional node, in response to a first parameter used to characterize a data push condition in a received parameter setting operation, generating a first execution node, wherein the first execution node is used to determine whether the received target data meets the data push condition based on the first parameter; Alternatively, for each functional node, in response to a second parameter used to characterize the data to be pushed and the target port in the received parameter setting operation, a first execution node is generated, and the second execution node is used to push the data to be pushed to the target port.
5. The method according to claim 4, characterized in that After obtaining the execution nodes corresponding one-to-one to the plurality of function nodes, the method further includes: For each of the execution nodes, when the execution node is the first execution node, establishing a relationship between the execution node and a preset data source port; The data received from the data source port is determined as the target data.
6. The method according to claim 2, characterized in that The first relationship node and the second relationship node both belong to relationship nodes; each to-be-executed task associated with the relationship node is executed in sequence according to a preset execution order; when the relationship node is the first relationship node, the to-be-executed task is the execution node, and when the relationship node is the second relationship node, the to-be-executed task is the sub-function module; The relationship node is used to limit the execution logic of at least one to-be-executed task associated with the relationship node, including: When the type of the relationship node is the first type, the execution logic of the at least one task to be executed is: in response to the failure of execution of any of the tasks to be executed, stop executing each of the tasks to be executed; When the type of the relationship node is the second type, the execution logic of the at least one task to be executed is: in response to any one of the tasks to be executed being executed successfully, stopping the execution of each of the tasks to be executed; When the type of the relationship node is the third type, the execution logic of the at least one to-be-executed task is: in response to each to-be-executed task in the at least one to-be-executed task being completed, stopping the execution of each to-be-executed task.
7. A method for executing a business function, characterized in that: The method is executed by a rule engine, wherein the rule engine includes at least two mutually independent sub-function modules, each of which includes: a relationship node and at least one execution node associated with the relationship node; each of the execution nodes is used to execute at least part of the actions in the business function, and each of the relationship nodes is used to limit the execution logic of at least one execution node associated with it; The method comprises: In response to a start-up operation on the rule engine, determining a first relationship node in each of the sub-function modules; Determine a first execution logic of at least one execution node associated with the first relationship node; Based on the first execution logic, the execution node is executed.
8. The method according to claim 7, characterized in that The at least two sub-function modules are associated with at least one second relationship node; The second relationship node is used to define the execution logic between the at least two sub-function modules; The determining of the first relationship node in each of the sub-function modules includes: Based on each of the second relationship nodes, determining the second execution logic of the at least two sub-function modules; Based on the second execution logic, execute each of the sub-function modules; When executing each of the sub-functional modules, a first relationship node in the sub-functional module is determined.
9. The method according to claim 8, characterized in that The method further comprises: In response to the type modification operation on the relationship node, a relationship node after the type modification is obtained, so as to replace the execution logic between the tasks to be executed based on the type set in the type modification operation; The first relationship node and the second relationship node both belong to the relationship node; when the relationship node is the first relationship node, the task to be executed is the execution node, and when the relationship node is the second relationship node, the task to be executed is the sub-function module.
10. The method according to claim 7, characterized in that The method further comprises: For each of the execution nodes, in response to a parameter modification operation on the execution node, an execution node after parameter modification is obtained, so as to replace an action to be performed by the execution node based on the parameters in the parameter modification operation.
11. A business function building device, characterized in that: The device comprises: A first response module, configured to obtain, in response to a parameter setting operation for a plurality of functional nodes, execution nodes corresponding one to one to the plurality of functional nodes, each of the execution nodes being capable of executing at least part of the actions in the business function based on the parameters in the parameter setting operation; A first determination module is configured to determine at least two sub-function modules corresponding to the at least two first relationship nodes when it is detected that a first relationship node is associated with each of the execution nodes and there are at least two first relationship nodes; each of the sub-function modules includes a corresponding first relationship node and at least one execution node associated with the first relationship node, and each of the first relationship nodes is used to define the execution logic of at least one execution node associated with the first relationship node; A building module is used to build corresponding business functions based on the at least two sub-function modules.
12. A business function execution device, characterized in that: The device is executed by a rule engine, wherein the rule engine includes at least two mutually independent sub-function modules, each of which includes: a relationship node and at least one execution node associated with the relationship node; each of the execution nodes is used to execute at least part of the actions in the business function, and each of the relationship nodes is used to limit the execution logic of at least one execution node associated with it; The device comprises: A second response module, configured to determine a first relationship node in each of the sub-function modules in response to a start operation on the rule engine; A second determination module, configured to determine a first execution logic of at least one execution node associated with the first relationship node; An execution module is used to execute the execution node based on the first execution logic.
13. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, the steps of any method described in claims 1-10 are implemented.
14. A computer device, characterized in that: The method comprises a memory, a processor and a computer program stored in the memory and executable on the processor, wherein the processor implements the steps of any one of the methods of claims 1 to 10 when executing the computer program.
