Business rule management method and device, terminal and storage medium

Abstract

The invention provides a business rule management method and device, a terminal and a storage medium, and belongs to the technical field of data processing, and the method comprises the steps: receiving business basic information generated when a user operates on a visual operation interface of a business rule editor; generating a service rule according to the service basic information; issuing the business rule to an application market; and in response to a downloading instruction of a user for the business rule on the application market, downloading the business rule and deploying the business rule in an execution engine. According to the invention, the business rules are arranged through the visual operation interface, the rule arrangement efficiency can be effectively improved, the generated business rules can be published to an application market and downloaded and deployed to an execution engine by a user, and the time period of the business rules from design to application is shortened.

Description

Technical Field

[0001] The present invention relates to the field of data processing technology, and in particular to a business rule management method, device, terminal and storage medium. Background Art

[0002] With the changes in the market environment and the frequent adjustments in business requirements, enterprises need to be able to quickly define, modify and deploy new business rules. However, in the traditional business rule management method, whenever a new business requirement is proposed, the requirements personnel need to elaborate on the specific requirements of business logic and data flow, and then these requirements are passed to the development team. The development team writes code according to the requirements document, implements the business rule logic, and integrates and tests it in the system. This process is relatively cumbersome, which makes the time cycle from business rule design to application longer, which greatly limits business flexibility and response speed.

[0003] Therefore, the prior art has defects and needs to be improved and developed. Summary of the invention

[0004] The technical problem to be solved by the present invention is to provide a business rule management method, device, terminal and storage medium in view of the above-mentioned defects of the prior art, aiming to solve the problem that the time period from design to application of business rules in the prior art is long.

[0005] The technical solution adopted by the present invention to solve the technical problem is as follows:

[0006] In a first aspect, an embodiment of the present invention provides a business rule management method, the method comprising:

[0007] Receive basic business information generated by the user's operation in the visual operation interface of the business rule editor;

[0008] Generate business rules according to the basic business information;

[0009] Publishing the business rules in the application market;

[0010] In response to a download instruction from a user for the business rules on the application market, the business rules are downloaded and deployed on an execution engine.

[0011] In one embodiment, the visual operation interface includes a plurality of node controls that support setting property values, connection controls for connecting node controls, and an editing interface, wherein the connection controls are used to connect different node controls; the receiving of business basic information generated by the user operating the visual operation interface of the business rule editor includes:

[0012] The business basic information generated by the user dragging each target node control to the editing area, dragging a connection line between each target node control in the editing area, and setting a property value for each target node control is received.

[0013] In one embodiment, before receiving the basic business information generated by the user operating on the visual operation interface of the business rule editor, the method further includes:

[0014] Using several preset interfaces provided by the preset device management platform, the capability information, trigger condition information and event information of each target device are obtained;

[0015] The capability information, trigger condition information and event information of each target device are mapped to each node control on the business rule editor.

[0016] In one embodiment, the receiving of basic business information generated by a user operating on a visual operation interface of a business rule editor further includes:

[0017] Record the user's operation behavior on each target node control to form a node operation history record.

[0018] In one implementation, the operation behavior includes the dragging time of the target node, the set attribute value change record, the connection adding operation information and the connection deleting operation information.

[0019] In one embodiment, before publishing the business rules on the application market, the method further includes:

[0020] Determine whether the version number of the business rule exists in the application market;

[0021] If the version number does not exist in the application market, the business rules are published in the application market.

[0022] In one embodiment, the method further comprises:

[0023] monitoring trigger events associated with the business rules;

[0024] When the trigger event is detected, the corresponding operation is executed using the business rules on the execution engine, and the execution result is output.

[0025] In a second aspect, an embodiment of the present invention further provides a business rule management device, including:

[0026] An information generation module is used to receive basic business information generated by the user in the visual operation interface of the business rule editor;

[0027] A rule generation module, used to generate business rules according to the business basic information;

[0028] A rule publishing module, used to publish the business rules in the application market;

[0029] The rule deployment module is used to respond to the download instruction of the user for the business rules on the application market, download and deploy the business rules to the execution engine.

[0030] In a third aspect, an embodiment of the present invention further provides a terminal, comprising: a memory, a processor, and a business rule management program stored in the memory and executable on the processor, wherein the business rule management program implements the steps of the business rule management method described above when executed by the processor.

[0031] In a fourth aspect, an embodiment of the present invention further provides a computer-readable storage medium, wherein the computer-readable storage medium stores a business rule management program, and the business rule management program can be executed to implement the steps of the business rule management method as described above.

[0032] Beneficial effects of the present invention: The present invention receives business basic information generated by the user's operation in the visual operation interface of the business rule editor; generates business rules according to the business basic information; publishes the business rules on the application market; and responds to the user's download instruction for the business rules on the application market, downloads and deploys the business rules on the execution engine. The present invention arranges business rules through a visual operation interface, which can effectively improve the efficiency of rule arrangement. The generated business rules can be published on the application market, downloaded and deployed to the execution engine by the user, shortening the time cycle from design to application of business rules. BRIEF DESCRIPTION OF THE DRAWINGS

[0033] Figure 1 It is a flow chart of a preferred embodiment of the business rule management method in the present invention.

[0034] Figure 2 The present invention is a schematic diagram of the rule arrangement of the electronic table name display.

[0035] Figure 3 It is a schematic diagram of rule arrangement for controlling lights and air conditioners in a conference room in the present invention.

[0036] Figure 4 It is a schematic diagram of rule arrangement for judging the presence of people in a conference room in the present invention.

[0037] Figure 5 It is a timing diagram of the release of business rules in the present invention.

[0038] Figure 6It is a timing diagram of business rule deployment in the present invention.

[0039] Figure 7 It is a structural diagram of a preferred embodiment of the business rule management device in the present invention.

[0040] Figure 8 It is a terminal principle block diagram of the present invention. DETAILED DESCRIPTION

[0041] In order to make the purpose, technical solution and advantages of the present invention clearer and more specific, the present invention is further described in detail below with reference to the accompanying drawings and examples. It should be understood that the specific embodiments described herein are only used to explain the present invention and are not used to limit the present invention.

[0042] With the changes in the market environment and the frequent adjustments in business requirements, enterprises need to be able to quickly define, modify and deploy new business rules. However, in the traditional business rule management method, whenever a new business requirement is proposed, the requirements personnel need to elaborate on the specific requirements of business logic and data flow, and then these requirements are passed to the development team. The development team writes code according to the requirements document, implements the business rule logic, and integrates and tests it in the system. This process is relatively cumbersome, which makes the time cycle from business rule design to application longer, which greatly limits business flexibility and response speed.

[0043] In view of the above-mentioned defects of the prior art, the present invention provides a business rule management method, device, terminal and storage medium, which belongs to the field of data processing technology. The method includes: receiving basic business information generated by the user's operation in the visual operation interface of the business rule editor; generating business rules according to the basic business information; publishing the business rules on the application market; responding to the user's download instruction for the business rules on the application market, downloading and deploying the business rules on the execution engine. The present invention arranges business rules through a visual operation interface, which can effectively improve the efficiency of rule arrangement. The generated business rules can be published to the application market, downloaded and deployed to the execution engine by the user, shortening the time cycle from design to application of business rules.

[0044] See also Figure 1 The business rule management method described in the embodiment of the present invention includes the following steps:

[0045] Step S100: receiving basic business information generated by a user operating on a visual operation interface of a business rule editor.

[0046] Specifically, the business rule editor of the present invention includes a visual operation interface, which includes a number of node controls that support setting attribute values, connection controls for connecting node controls, and an editing interface. The visual operation interface can be a web page interface, or a desktop application interface or a mobile application interface, which is not limited here. When the user drags the target node control to the editing interface, the connection control can be clicked to set the connection of the target node control key. In addition, it also supports setting the attribute value of the target node control in the editing interface. The present invention can effectively simplify the rule arrangement process through an intuitive operation method, allowing users to easily create and configure business rules.

[0047] In one implementation, the visual operation interface includes a plurality of node controls that support setting property values, connection controls for connecting node controls, and an editing interface, wherein the connection controls are used to connect different node controls; the receiving of business basic information generated by the user operating the visual operation interface of the business rule editor includes:

[0048] The business basic information generated by the user dragging each target node control to the editing area, dragging a connection line between each target node control in the editing area, and setting a property value for each target node control is received.

[0049] Specifically, a node control represents an element or operation (conditional judgment, data processing steps, etc.) in a business rule. These node controls support setting attribute values, and users can define specific parameters or behaviors for each node control. The editing interface provides a visual space and provides areas for users to perform operations such as dragging and setting attributes, so that users can intuitively see the business rules being built. By connecting lines, users can define the execution order or data flow path between nodes to construct complex business logic. Through visual operation methods, complex business rules can be quickly created and edited, which improves the efficiency and accuracy of business rule creation and enables non-technical personnel to participate in the formulation of business rules.

[0050] In one implementation, before receiving the basic business information generated by the user operating on the visual operation interface of the business rule editor, the method further includes:

[0051] Using several preset interfaces provided by the preset device management platform, the capability information, trigger condition information and event information of each target device are obtained;

[0052] The capability information, trigger condition information and event information of each target device are mapped to each node control on the business rule editor.

[0053] Specifically, the present invention provides a preset device management platform that can manage all devices in the target management area. Using several preset interfaces provided by the preset device management platform, the capability information, trigger condition information and event information of each target device can be obtained. The capability information includes the functional operation capabilities and parameter formats of the device, the trigger condition information clearly defines the expression of the device action trigger condition, and the event information records the state change events and parameters during the operation of the device. Then, the capability information, trigger condition information and event information of each target device are mapped to each node control on the business rule editor. The user can set corresponding business rules for these node controls in subsequent operations. For example, the user can define which operations should be performed or which events should be triggered when a certain device triggers a specific condition. Such a design not only improves the flexibility and convenience of business rule editing, but also forms a close linkage between device management and business rule editing, which helps to achieve a more intelligent and automated business processing flow.

[0054] In one embodiment, if Figure 2 As shown, Figure 2 The following example shows a rule arrangement diagram for displaying names on electronic table cards. When a face recognition event is detected, the name on the electronic table card can be immediately updated to the recognized name. This automated process not only improves efficiency, but also reduces human errors. This visual arrangement of rules is not only easy to arrange, but also easy to maintain and understand. Editors can see the logic of the business process more clearly, making it easier to troubleshoot and optimize rules. Users can focus more on the implementation of business logic without being bothered by complex technical details.

[0055] In one embodiment, if Figure 3 As shown, Figure 3 The example shows a schematic diagram of rule arrangement for controlling the lights and air conditioners in a conference room. When the human body sensing radar in the conference room senses the presence of a human body, the lights are turned on and the brightness is set to 100, and the air conditioner is set to cooling mode with a medium wind speed and a temperature of 24 degrees. When the human body sensing radar in the conference room does not sense the presence of a human body, the lights and air conditioner are turned off. The present invention not only improves the response speed but also optimizes the efficiency of resource use by executing the turning-on actions of the lights and air conditioners in parallel. On the contrary, when no one is detected, the system also turns off the air conditioner and lights in parallel. This intelligent response mechanism ensures energy conservation and environmental comfort. Through intelligent parallel processing and minimalist editing methods, the business rule system realizes an efficient automated process. This process not only reduces human intervention, but also improves the accuracy and reliability of business execution. In addition, the rule editor of the present invention allows the business logic layer to be flexibly added or modified to adapt to changing business needs. At the same time, the scalability of the system also ensures the possibility of adding more functions or handling more complex scenarios in the future.

[0056] In one embodiment, if Figure 4 As shown, Figure 4 The following example shows a rule arrangement diagram for judging the attendance of meeting room personnel. Users can pre-set the meeting time and the number of people who should be present in each meeting room. The number of people in each meeting room is obtained three minutes before the meeting starts, and it is judged whether they are all present. For meeting rooms that are full, the number of people who are not present is updated to zero, and for meeting rooms that are not full, the number of people who are not present is updated to the number of people counted. In an intelligent way, the situation of the meeting about to start is automatically detected, and the attendance of people is judged. This automated process greatly improves the efficiency and accuracy of meeting management.

[0057] In one implementation, the receiving of basic business information generated by a user operating on a visual operation interface of a business rule editor further includes:

[0058] Record the user's operation behavior on each target node control to form a node operation history record.

[0059] Specifically, the present invention can also record the user's operation behavior while operating in the editing area to form a node operation history record. The operation behavior includes the dragging time of the target node, the set attribute value change record, the connection addition operation information and the connection deletion operation information. In this way, the traceability and traceability of the business editor can be enhanced, providing users with a more convenient and reliable editing experience. The present invention uses a visual business rule editor to effectively manage the life cycle of the node control, including node creation, update, deletion and other operations, to ensure the stability and efficiency of the system.

[0060] See also Figure 1 The business rule management method described in the embodiment of the present invention further includes the following steps:

[0061] Step S200: Generate business rules according to the basic business information.

[0062] Specifically, the business basic information is parsed to obtain business rules. Business rules include the identifier of each target node control, the type of each target node control, the capabilities of each target node, execution link information, and upstream and downstream initialization data. The execution link information is the execution order and logical relationship between the controls of each target node. Each node plays a specific role in the link, such as data input, processing, or output. The execution link ensures that the business rules are executed in a predetermined order and logic during operation, thereby realizing the automation and optimization of complex business processes. The upstream and downstream initialization data are the initialization data and data flow required for the execution of business rules. The initialization data includes the initial input data required before the node runs, as well as the data transfer and conversion rules between nodes. This part of data is crucial to ensure the correct execution of business rules because it provides the background information and parameters required for node operations. The configuration of initialization data involves a detailed description of the data requirements of each node to ensure that the data can flow and process correctly throughout the business process. Through the close cooperation of these data, users can simplify complex business processes into clear business rules through intuitive drag-and-drop operations, and efficiently realize business automation through the execution engine. The types of each target node control include triggers, arithmetic operations, comparison operations, logical operations, and conversion nodes. Conversion nodes are used for data format conversion or data distribution. Triggers include device triggers, timed triggers, manual triggers, and capability calls. Target node capabilities include attribute reporting capabilities, event reporting capabilities, read attribute capabilities, write attribute capabilities, and call capabilities. Attribute reporting capabilities refer to reporting a certain attribute value of a node control to the upper-level module. For example, a temperature sensor reports the current temperature to the business rule management system. Event reporting capabilities refer to reporting a specific event when it occurs. For example, reporting an event when a button is clicked. Read attribute capabilities refer to reading a certain attribute value of a node control. Write attribute capabilities refer to modifying a certain attribute value of a control. Call capabilities refer to the ability to call other businesses or interfaces.

[0063] The data structure of the business rules in the present invention can be a single node structure, a combined node structure or a parallel node structure. Different nodes in the combined node structure can work together to meet different business needs. The business rule engine in the business editor of the present invention adopts a trigger node selection mechanism, which can automatically identify and respond to its associated attributes, ensuring that the process will continue to execute only when these associated attributes are triggered, thereby avoiding unnecessary processing and potential errors. In the process of attribute reporting, a dynamic screening mechanism is introduced, and only when all preset attributes are included can the subsequent nodes be executed, thereby ensuring the accuracy and effectiveness of the process. Through different nodes, a highly customized business process can be constructed, which not only improves development efficiency, but also increases the flexibility and scalability of the system. Users can quickly add, remove or reconfigure nodes according to changes in business needs, thereby realizing dynamic adjustment of business processes. In a parallel node structure, different nodes can be processed simultaneously. The business rule editor of the present invention simplifies the implementation of parallel logic. Compared with traditional editors, any node is allowed to be directly connected to multiple subsequent nodes on any branch without the need to add additional parallel nodes or perform group processing. This design greatly reduces the complexity in the editing process, making the arrangement of parallel logic more intuitive and easy to manage. By simplifying the implementation of parallel functions, the business rule editor of the present invention reduces the work of pulling and configuring unnecessary nodes that users need to do when editing complex parallel functions. This not only saves users' time and energy, but also improves the efficiency of the entire editing process. By simplifying the implementation of parallel functions, users are provided with an efficient, flexible and easy-to-use platform. This not only improves the user experience, but also provides strong support for the automation and intelligence of business processes, helping enterprises stand out in the fiercely competitive market.

[0064] In one implementation, the service editor of the present invention supports automatic addition of conversion nodes to cope with various new service requirements and challenges.

[0065] Specifically, users no longer need to manually write complex custom scripts to handle data conversion, which not only reduces the difficulty of operation, but also reduces the risk of errors caused by manual operation. In traditional data processing, the maintenance of inheritance relationships often requires additional logic and steps. However, the system of the present invention automatically maintains the inheritance relationship of data through intelligent conversion nodes, realizes seamless inheritance relationship maintenance, and simplifies user operations. This means that the transmission and processing of data are smoother, ensuring the consistency and accuracy of data. Since the system automatically handles data conversion and maintenance of inheritance relationships, the maintenance workload of users and administrators is significantly reduced, the efficiency of data processing is improved, and data changes can be quickly responded to, and data conversion and processing can be performed in a timely manner. This not only reduces maintenance costs, but also makes system maintenance simpler and more efficient.

[0066] See also Figure 1 The business rule management method described in the embodiment of the present invention further includes the following steps:

[0067] Step S300: publishing the business rules in the application market.

[0068] Specifically, Figure 5 As shown, Figure 5 This is a timing diagram for publishing business rules. When the business rules are generated, determine whether the version number of the business rules exists in the application market; if the version number does not exist in the application market, publish the business rules in the application market and return the publishing information. The business rule editor can receive the publishing information. In the process of generating business rules, the expression language (i.e., el expression) generated by the business editor and the trigger type are bound and stored in the MySQL database, and the storage information is returned to the business editor. At this time, the business rules are generated.

[0069] See also Figure 1 The business rule management method described in the embodiment of the present invention further includes the following steps:

[0070] Step S400: In response to a download instruction from a user for the business rules on the application market, the business rules are downloaded and deployed on an execution engine.

[0071] Specifically, the execution engine includes a cloud execution engine and a local operating system side execution engine, which are kept in sync when deploying rules. Figure 6 As shown, after the user publishes the business rules to the application market, the business rules can be deployed to the execution engine in response to the user's download instruction for the business rules on the application market, and the business rules are executed by the execution engine. When the deployment is completed, the execution engine will return information about the deployment success or deployment failure to the application market.

[0072] In one implementation, the method further includes:

[0073] monitoring trigger events associated with the business rules;

[0074] When the trigger event is detected, the corresponding operation is executed using the business rules on the execution engine, and the execution result is output.

[0075] Specifically, in the present invention, separating the business rule editor and the execution engine is the core of "one-time orchestration, multi-terminal operation". Through this separation, users can use the business rule editor to create and define business rules, convert them into executable rule instances, and publish them to the application market, which are deployed to the execution engine by the application market. The business execution end is the starting point of the business operation and the entrance for users to interact with the system to trigger the business process. It can be various types of devices or software platforms, such as the conference control terminal in the smart conference room, the mobile application used by the user, the business operation interface of the web page, etc. The main function of the business execution end is to receive the user's operation instructions or event trigger signals, and pass the relevant business information to the execution engine. When the system detects a trigger event associated with the business rule, the execution engine processes it according to the preset business rules. For example, in the smart conference room scenario, the user initiates a business transaction through a button or touch screen operation on the conference control terminal (such as clicking the "Start Meeting" button). At this time, the conference control terminal acts as a business execution end and sends the operation information to the execution engine. The execution engine is the actual executor of the business rules. It is responsible for parsing and executing the business rules received from the business execution end, processing the business data, and generating corresponding execution results. The execution engine has powerful computing and logic processing capabilities. It can coordinate the operations between various node controls according to the execution link information and upstream and downstream initialization data in the business rules, and realize the automatic processing of complex business logic. The execution engine can be deployed in the cloud or on the device side, and select the most appropriate execution location according to different business needs and scenarios to provide efficient and reliable services. For example, in business scenarios that process large-scale data analysis or multi-device collaborative control, the cloud-side execution engine can use its powerful computing resources and network communication capabilities to centrally process data from multiple business execution terminals; in scenarios with high real-time requirements and the need for fast local response, such as real-time control operations of equipment, the device-side execution engine can directly execute relevant business rules locally, reduce data transmission delays, and improve system response speed.

[0076] In one implementation, the method further includes:

[0077] Report the data during the operation of business rules;

[0078] When an abnormal situation is detected, the time when the abnormality occurs, the target nodes involved, and the business operation information are recorded to generate alarm information;

[0079] The warning information is sent to relevant personnel in a preset manner.

[0080] Specifically, the data during the operation of the business rules is reported to facilitate monitoring and analysis of the execution and performance of the nodes. Recording the time when the exception occurs provides an accurate time clue for subsequent troubleshooting, which helps technicians quickly locate the time node when the problem occurs. Combined with system logs and other information, the system state when the exception occurs can be effectively restored. The target node information involved clarifies the specific business link where the problem is located, which is the key basis for determining the root cause of the problem. For example, if an exception occurs at the air-conditioning control node, the technician can specifically check the configuration parameters of the node, the communication connection with the device, and the logic of related business rules. The business operation information describes in detail the content of the ongoing business operation when the exception occurs, including the input data of the operation, the executed business rules, etc., to further assist the technicians in in-depth analysis of the cause of the problem. By timely recording these key information to generate alarm information and sending it to relevant personnel, the problem can be quickly resolved and small problems can be effectively prevented from turning into major failures, thereby greatly enhancing the reliability and stability of the system and ensuring the continuous and stable operation of the business.

[0081] In one implementation, the preset method is any one of a voice call, a text message, an email, or an application message.

[0082] In summary, the present invention receives the basic business information generated by the user's operation in the visual operation interface of the business rule editor; generates business rules according to the basic business information; publishes the business rules on the application market; and responds to the user's download instruction for the business rules on the application market, downloads and deploys the business rules on the execution engine. The present invention arranges business rules through a visual operation interface, which can effectively improve the efficiency of rule arrangement. The generated business rules can be published to the application market, downloaded and deployed to the execution engine by the user, shortening the time cycle from design to application of business rules.

[0083] In one embodiment, if Figure 7 As shown, based on the above business rule management method, the present invention also provides a business rule management device, including:

[0084] The information generation module 100 is used to receive basic business information generated by the user operating in the visual operation interface of the business rule editor;

[0085] A rule generation module 200, used to generate business rules according to the business basic information;

[0086] A rule publishing module 300, used to publish the business rules in the application market;

[0087] The rule deployment module 400 is used to download and deploy the business rules to the execution engine in response to a download instruction from a user for the business rules on the application market.

[0088] In one embodiment, the visual operation interface includes a plurality of node controls that support setting property values, connection controls for connecting node controls, and an editing interface, wherein the connection controls are used to connect different node controls; the information generation module includes:

[0089] The basic information generation unit is used to receive the business basic information generated by the user dragging each target node control to the editing area in the visual operation interface of the business rule editor, dragging the connection line between the target node controls in the editing area, and setting the attribute value of each target node control.

[0090] In one embodiment, the device further comprises:

[0091] An information acquisition unit, used to acquire capability information, trigger condition information and event information of each target device by using a number of preset interfaces provided by a preset device management platform;

[0092] The node generation unit is used to map the capability information, trigger condition information and event information of each target device to each node control on the business rule editor.

[0093] In one embodiment, the device further comprises:

[0094] The history record generating unit is used to record the user's operation behavior on each target node control to form a node operation history record.

[0095] In one embodiment, the device further comprises:

[0096] A version determination unit, used to determine whether the version number of the business rule exists in the application market;

[0097] A version publishing unit is used to publish the business rules in the application market if the version number does not exist in the application market.

[0098] In one embodiment, the device further comprises:

[0099] A monitoring unit, configured to monitor trigger events associated with the business rules;

[0100] The rule execution unit is used to execute corresponding operations using the business rules on the execution engine when the trigger event is detected, and output the execution result.

[0101] Based on the above embodiment, the present invention further provides a terminal, whose principle block diagram can be shown as follows: Figure 8As shown. The terminal includes a processor, a memory, a network interface and a display screen connected via a device bus. The processor of the terminal is used to provide computing and control capabilities. The memory of the terminal includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating device and a business rule management program. The internal memory provides an environment for the operation of the operating device and the business rule management program in the non-volatile storage medium. The network interface of the terminal is used to communicate with an external terminal via a network connection. When the business rule management program is executed by the processor, the steps of any one of the above-mentioned business rule management methods are implemented. The display screen of the terminal can be a liquid crystal display screen or an electronic ink display screen.

[0102] Those skilled in the art will understand that Figure 8 The principle block diagram shown in the figure is only a block diagram of a partial structure related to the scheme of the present invention, and does not constitute a limitation on the terminal to which the scheme of the present invention is applied. The specific terminal may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0103] In one embodiment, a terminal is provided, comprising a memory, a processor, and a business rule management program stored in the memory and executable on the processor, wherein the business rule management program, when executed by the processor, implements the steps of any one of the business rule management methods provided in the embodiments of the present invention.

[0104] An embodiment of the present invention further provides a computer-readable storage medium, on which a business rule management program is stored. When the business rule management program is executed by a processor, the steps of any one of the business rule management methods provided in the embodiments of the present invention are implemented.

[0105] It should be understood that the serial numbers of the steps in the above embodiments do not imply a sequence of execution, and the execution sequence of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present invention.

[0106] Those skilled in the art can clearly understand that for the convenience and simplicity of description, only the division of the above-mentioned functional units and modules is used as an example for illustration. In practical applications, the above-mentioned function allocation can be completed by different functional units and modules as needed, that is, the internal structure of the above-mentioned device can be divided into different functional units or modules to complete all or part of the functions described above. The functional units and modules in the embodiment can be integrated in a processing unit, or each unit can exist physically separately, or two or more units can be integrated in one unit. The above-mentioned integrated unit can be implemented in the form of hardware or in the form of software functional units. In addition, the specific names of the functional units and modules are only for the convenience of distinguishing each other, and are not used to limit the scope of protection of the present invention. The specific working process of the units and modules in the above-mentioned device can refer to the corresponding process in the aforementioned method embodiment, which will not be repeated here.

[0107] In the above embodiments, the description of each embodiment has its own emphasis. For parts that are not described or recorded in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0108] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of the present invention.

[0109] In the embodiments provided by the present invention, it should be understood that the disclosed apparatus / terminal equipment and method can be implemented in other ways. For example, the apparatus / terminal equipment embodiments described above are only illustrative, for example, the division of the above modules or units is only a logical function division, and in actual implementation, other division methods can be used, for example, multiple units or components can be combined or integrated into another apparatus, or some features can be ignored or not executed.

[0110] The embodiments described above are only used to illustrate the technical solutions of the present invention, rather than to limit the same. Although the present invention has been described in detail with reference to the aforementioned embodiments, it should be understood by those skilled in the art that the technical solutions described in the aforementioned embodiments may still be modified, or some of the technical features therein may be replaced by equivalents. However, these modifications or replacements do not deviate from the spirit and scope of the technical solutions of the embodiments of the present invention, and should be included in the protection scope of the present invention.

Claims

1. A business rule management method, characterized in that: The method comprises: Receive basic business information generated by the user's operation in the visual operation interface of the business rule editor; Generate business rules according to the basic business information; Publishing the business rules in the application market; In response to a download instruction from a user for the business rules on the application market, the business rules are downloaded and deployed on an execution engine.

2. The business rule management method according to claim 1, characterized in that: The visual operation interface includes a number of node controls that support setting property values, connection controls for connecting node controls, and an editing interface, wherein the connection controls are used to connect different node controls; The receiving of basic business information generated by the user operating in the visual operation interface of the business rule editor includes: The business basic information generated by the user dragging each target node control to the editing area, dragging a connection line between each target node control in the editing area, and setting a property value for each target node control is received.

3. The business rule management method according to claim 1, characterized in that: Before receiving the basic business information generated by the user operating on the visual operation interface of the business rule editor, the method further includes: Using several preset interfaces provided by the preset device management platform, the capability information, trigger condition information and event information of each target device are obtained; The capability information, trigger condition information and event information of each target device are mapped to each node control on the business rule editor.

4. The business rule management method according to claim 1, characterized in that: The receiving of basic business information generated by the user operating on the visual operation interface of the business rule editor also includes: Record the user's operation behavior on each target node control to form a node operation history record.

5. The business rule management method according to claim 4, characterized in that: The operation behavior includes the dragging time of the target node, the set attribute value change record, the connection adding operation information and the connection deleting operation information.

6. The business rule management method according to claim 1, characterized in that: Before publishing the business rules on the application market, the method further includes: Determine whether the version number of the business rule exists in the application market; If the version number does not exist in the application market, the business rules are published in the application market.

7. The business rule management method according to claim 1, characterized in that: The method further comprises: monitoring trigger events associated with the business rules; When the trigger event is detected, the corresponding operation is executed using the business rules on the execution engine, and the execution result is output.

8. A business rule management device, characterized in that: include: An information generation module is used to receive basic business information generated by the user's operation in the visual operation interface of the business rule editor; A rule generation module, used to generate business rules according to the business basic information; A rule publishing module, used to publish the business rules in the application market; The rule deployment module is used to respond to the download instruction of the user for the business rules on the application market, download and deploy the business rules to the execution engine.

9. A terminal, characterized in that: The terminal includes a memory, a processor, and a business rule management program stored in the memory and executable on the processor. When the business rule management program is executed by the processor, the steps of the business rule management method according to any one of claims 1 to 7 are implemented.

10. A computer-readable storage medium, characterized in that: The computer readable storage medium The business rule management program is substantially stored, and when the business rule management program is executed by the processor, Implement the steps of the business rule management method as described in any one of claims 1 to 7.

Images