Internet of Things application system configuration method, device and equipment based on low-code platform

Abstract

The invention relates to the technical field of Internet of Things, and discloses an Internet of Things application system configuration method, device and equipment based on a low-code platform, and the method comprises the steps: generating an event strategy through triggering an interface control which is built in the low-code platform, the event strategy is used for defining an event triggering condition and an event linkage action for the application scene of the Internet of Things; calling a function node related to the event strategy in the low-code platform, and configuring the function node into an action logic chain based on the setting of an event triggering condition and an event linkage action; and sending a command for executing the action logic chain to a back-end server of the low-code platform in an apportionment manner, and configuring the Internet of Things application system to execute the command of the action logic chain under the condition that the event triggering condition is met. The development of the Internet of Things application system is realized by utilizing a low-code technology, the development and operation and maintenance process of the system can be simplified, and the development efficiency is improved.

Description

Technical Field

[0001] The present application relates to the field of Internet of Things technology, and in particular to a method, device and equipment for configuring an Internet of Things application system based on a low-code platform. Background Art

[0002] With the rapid development of IoT technology, more and more devices are connected through the Internet to achieve intelligent interaction and data transmission between devices. In related technologies, the development process of IoT application software usually relies on professional developers to customize the functions of the device according to specific needs. This customized development method not only has a long development cycle and high cost, but also has the problem of difficult software maintenance. Especially when the device function is updated or the demand changes, a large number of existing codes of IoT application software need to be modified, which increases the complexity of development and operation and maintenance. Summary of the invention

[0003] The present application provides an Internet of Things application system configuration method, device and equipment based on a low-code platform, which solves the current technical problems of long Internet of Things application software development cycle, high cost and difficult maintenance, and achieves the technical effect of simplifying the system development and operation and maintenance process and improving development efficiency.

[0004] In order to achieve the above objectives, the main technical solutions adopted in this application include:

[0005] In a first aspect, an embodiment of the present application provides an Internet of Things application system configuration method based on a low-code platform, including:

[0006] Generate an event strategy by triggering an interface control, wherein the interface control is built into the low-code platform, and the event strategy is used to define event triggering conditions and event linkage actions for IoT application scenarios;

[0007] Calling a function node related to the event strategy in the low-code platform, and configuring the function node into an action logic chain based on the event triggering condition and the setting of the event linkage action;

[0008] The commands for executing the action logic chain are distributed and sent to the back-end server of the low-code platform, and the Internet of Things application system is configured to execute the commands of the action logic chain when the event triggering conditions are met.

[0009] The method for configuring the Internet of Things application system proposed in the embodiment of the present application generates an event strategy through an interface control built into a low-code platform, and calls relevant function nodes based on the event strategy to configure an action logic chain, and distributes and sends commands for executing the action logic chain to the back-end server, and quickly executes relevant commands when the event triggering conditions are met to complete the configuration of the Internet of Things application system. Therefore, the present application can reduce the complexity of manual programming through the automated configuration of the low-code platform, and improve the configuration efficiency and flexibility of the Internet of Things application system. In addition, compared with the development method of traditional Internet of Things systems, the distributed command execution method adopted in this application significantly improves the concurrent processing capability of the system, ensuring that it can still operate efficiently and stably in a large number of concurrent device scenarios, effectively meeting the high concurrency and high response requirements of Internet of Things devices.

[0010] Optionally, in some embodiments of the present application, the event trigger condition includes a trigger time period and a trigger event type, wherein the trigger time period and the trigger event type are defined by the interface control to trigger the event linkage action when the trigger event type occurs within the trigger time period.

[0011] This application defines the trigger time period and trigger event type through interface controls, so as to trigger the corresponding event linkage action only when the specified trigger event type occurs within the set trigger time period. Therefore, this application can simplify the trigger conditions of event linkage actions in terms of time and event type through interface controls, can adapt to the complex needs of different IoT application scenarios, and at the same time improve the flexibility of the configuration process of the IoT application system.

[0012] Optionally, in some embodiments of the present application, the event policy also includes a device list, wherein an IoT device applicable to the event policy is selected through the interface control and added to the device list.

[0013] This application selects IoT devices applicable to the event policy through interface controls, which can achieve precise management and control of IoT devices, ensure that the event policy is only effective for designated IoT devices, and adapt to the differentiated needs of IoT devices in different IoT application scenarios.

[0014] Optionally, in some embodiments of the present application, the function node includes at least one of a start node, a database query node, a database insert node, an API call node, and an end node.

[0015] Optionally, in some embodiments of the present application, configuring the function node into an action logic chain based on the setting of the event triggering condition and the event linkage action includes:

[0016] Setting the start node, and selecting one of the database query node and the database insert node according to the event triggering condition to connect after the start node to generate a first initial logic chain;

[0017] Determine the execution device corresponding to each of the event linkage actions, and call the API call node built into the low-code platform for the execution device;

[0018] Arranging the API call nodes and the end nodes according to the sequence of the event linkage actions to generate a second initial logic chain;

[0019] The second initial logic chain is spliced ​​after the first initial logic chain to obtain the action logic chain.

[0020] This application avoids the tedious process of manually writing complex logic through the selection and arrangement of functional nodes, greatly simplifies the process of business logic configuration of the Internet of Things application system, and improves the development capabilities for Internet of Things application scenarios, which helps to improve the efficiency and flexibility of the configuration of the Internet of Things application system.

[0021] Optionally, in some embodiments of the present application, the backend server is deployed with a Kafka distributed messaging system, so as to distribute and send commands of the action logic chain based on the Kafka distributed messaging system;

[0022] Wherein, a Kafka topic corresponding to the command is set on the back-end server, and the Kafka topic is divided into a plurality of partitions so that the command can be evenly distributed and sent to each of the partitions.

[0023] This application can effectively utilize the high concurrent processing capabilities of the Kafka distributed architecture and distribute the commands of the logical chain to multiple partitions. This configuration method improves the concurrent processing capabilities and execution efficiency of the Internet of Things application system, thereby meeting the performance requirements of the Internet of Things application system in terms of response speed.

[0024] Optionally, in some embodiments of the present application, when at least one of the partitions fails, the commands of the action logic chain are randomly distributed to the remaining partitions that have not failed.

[0025] This application avoids the risk of failure in command execution of the action chain due to failure of individual partitions by setting up a random allocation mechanism involving multiple partitions, thereby improving the stability and reliability of the Internet of Things application system when processing high-concurrency commands.

[0026] Optionally, in some embodiments of the present application, the interface control is also used to configure a visual interface of the Internet of Things application system, and the method further includes:

[0027] The interface controls are used to generate a property display area and a device control button for each of the IoT devices in the visual interface, and the property display area and the device control button are respectively associated with the physical model of the IoT device.

[0028] In a second aspect, the embodiment of the present application provides an IoT application system configuration device based on a low-code platform, including:

[0029] A strategy generation module, used to generate an event strategy by triggering an interface control, wherein the interface control is built into the low-code platform, and the event strategy is used to define event triggering conditions and event linkage actions for IoT application scenarios;

[0030] A business logic orchestration module, used to call function nodes related to the event strategy in the low-code platform, and configure the function nodes into an action logic chain based on the event triggering conditions and the setting of the event linkage actions;

[0031] The distributed execution module is used to distribute the commands for executing the action logic chain to the back-end server of the low-code platform, and configure the Internet of Things application system to execute the commands of the action logic chain when the event triggering conditions are met.

[0032] The IoT application system configuration device proposed in the embodiment of the present application generates an event strategy through an interface control built into a low-code platform, and calls relevant function nodes based on the event strategy to configure an action logic chain, and distributes and sends commands for executing the action logic chain to the back-end server, and quickly executes relevant commands when the event triggering conditions are met to complete the configuration of the IoT application system. Therefore, the present application can reduce the complexity of manual programming through the automated configuration of the low-code platform, and improve the configuration efficiency and flexibility of the IoT application system. In addition, compared with the development method of traditional IoT systems, the distributed command execution method adopted by the present application significantly improves the concurrent processing capability of the system, ensuring that it can still operate efficiently and stably in a large number of concurrent device scenarios, effectively meeting the high concurrency and high response requirements of IoT devices.

[0033] In a third aspect, an embodiment of the present application provides a computer device, including:

[0034] A memory and a processor, the memory and the processor are communicatively connected to each other, the memory stores computer instructions, and the processor executes the Internet of Things application system configuration method based on a low-code platform as described in the first aspect of the embodiment above by executing the computer instructions.

[0035] The computer device proposed in the embodiment of this application can reduce the complexity of manual programming through the automated configuration of the low-code platform, thereby improving the configuration efficiency and flexibility of the IoT application system. In addition, compared with the development method of the traditional IoT system, the distributed command execution method adopted in this application significantly improves the concurrent processing capability of the system, ensuring that it can still operate efficiently and stably in a large number of concurrent device scenarios, effectively meeting the high concurrency and high response requirements of IoT devices. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0037] Figure 1 A flowchart of a method for configuring an Internet of Things application system based on a low-code platform proposed in an embodiment of the present application;

[0038] Figure 2 A schematic diagram of the action logic chain proposed in the embodiment of the present application;

[0039] Figure 3 This is a structural block diagram of an IoT application system configuration device based on a low-code platform proposed in an embodiment of the present application;

[0040] Figure 4 This is a structural block diagram of a computer device proposed in an embodiment of the present application. DETAILED DESCRIPTION

[0041] In order to make the purpose, technical solution and advantages of the embodiments of the present application clearer, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative work are within the scope of protection of the present application.

[0042] With the rapid development of Internet of Things (IoT) technology, more and more devices are connected through the Internet to achieve intelligent interaction and data transmission between devices. In related technologies, the development process of IoT application software usually relies on professional developers to carry out customized development according to specific needs. Developers need to write code for the interface of the selected device to achieve the integration and application of device functions.

[0043] In some application scenarios, a complete IoT application software development process needs to go through at least the process of "requirements-design-development-testing-deployment-operation and maintenance". This process not only has a long cycle and high development cost, but also has the problem of difficult software maintenance. Especially when the IoT device function is updated or the demand changes, it is often necessary to make a lot of modifications to the existing code, which increases the complexity of development and operation and maintenance.

[0044] In addition, in other application scenarios, as the types and numbers of devices increase, IoT application software developed using related technologies can hardly meet the needs of concurrent operation of a large number of devices and real-time data processing in IoT systems.

[0045] Low-code technology is a software development method that allows users to quickly develop application-related functions with minimal programming code or even without writing any code. This technology lowers the development threshold and is suitable for technical developers and non-technical personnel to participate in application development and configuration. This application uses the low-code platform based on low-code technology to provide a graphical user interface, visual development tools, and pre-built functional modules. Developers can configure the IoT application system by dragging and dropping functional modules and writing a small amount of code.

[0046] The Internet of Things application system configuration method provided in the embodiment of the present application can be applied to electronic devices with Internet of Things device management functions. The electronic devices may include industrial control terminals, personal mobile terminals, smart gateways, servers, etc. Of course, the Internet of Things application system configuration method provided in the embodiment of the present application can also be applied to applications running in the above-mentioned electronic devices.

[0047] According to an embodiment of the present application, an embodiment of an Internet of Things application system configuration method based on a low-code platform is provided. It should be noted that the steps shown in the flowchart in the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0048] like Figure 1 As shown, the method for configuring an IoT application system based on a low-code platform proposed in the embodiment of the present application includes the following steps:

[0049] Step S1, generate an event strategy by triggering the interface control, where the interface control is built into the low-code platform, and the event strategy is used to define event triggering conditions and event linkage actions for IoT application scenarios.

[0050] Interface controls are the basic elements that constitute the visual interface of the IoT application system, which are used to allow users to interact with software or systems. In the configuration of the IoT application system, interface controls are not only tools for displaying data, but can also trigger specific operations or logic. For example, when a button control is clicked, the IoT application system can execute a predefined function to implement the configuration of the event strategy. In an embodiment of the present application, the above-mentioned interface controls are developed by pre-building relevant functions using a low-code platform, thereby simplifying the configuration process of the event strategy.

[0051] Step S2, call the function nodes related to the event strategy in the low-code platform, and configure the function nodes into an action logic chain based on the setting of event trigger conditions and event linkage actions.

[0052] A function node is a logic unit used to perform specific functions in an IoT application system. It is responsible for processing specific operations, such as data processing, database query, external interface call, conditional judgment, etc. It combines multiple function nodes together to build an action logic chain to achieve the configuration of complex business logic. In the embodiment of the present application, the above-mentioned function nodes are also developed by pre-building relevant functions using a low-code platform, thereby improving the efficiency of action logic arrangement during the configuration process of the IoT application system.

[0053] Step S3, distributes and sends the commands for executing the action logic chain to the backend server of the low-code platform, and configures the IoT application system to execute the commands of the action logic chain when the event triggering conditions are met.

[0054] This application distributes the commands used to execute the action logic chain and sends them to the back-end server, which then quickly executes the relevant commands to meet the high concurrency and high response performance requirements in IoT application scenarios.

[0055] The method for configuring the Internet of Things application system provided in this embodiment generates an event strategy through an interface control built into a low-code platform, and calls relevant function nodes based on the event strategy to configure an action logic chain, and distributes and sends commands for executing the action logic chain to the back-end server, and quickly executes relevant commands when the event triggering conditions are met to complete the configuration of the Internet of Things application system. Therefore, the present application can reduce the complexity of manual programming through the automated configuration of the low-code platform, and improve the configuration efficiency and flexibility of the Internet of Things application system. In addition, compared with the development method of traditional Internet of Things systems, the distributed command execution method adopted in this application significantly improves the concurrent processing capability of the system, ensuring that it can still operate efficiently and stably in a large number of concurrent device scenarios, effectively meeting the high concurrency and high response requirements of Internet of Things devices.

[0056] In some embodiments of the present application, the above-mentioned event trigger conditions include a trigger time period and a trigger event type, wherein the trigger time period and the trigger event type are defined through interface controls to achieve trigger event linkage actions when the trigger event type occurs within the trigger time period.

[0057] Interface controls are visible and operable parts of the interface of the IoT application system, which help users input, view or operate related configuration data. Common interface controls include buttons, text boxes, drop-down menus, check boxes, sliders, etc. The embodiment of the present application uses interface controls to implement visual configuration of event strategies. Users can quickly configure event trigger conditions through operations such as selection, input, and dragging without writing complex codes.

[0058] Specifically, the user defines the trigger time period through the interface control, or selects a preset time template, which includes multiple time periods of multiple dates. For example, for the application scenario of receiving and processing the alarm event of the intrusion anti-theft device defense zone, the trigger time period is used as one of the event trigger conditions. Only when the alarm event occurs within the trigger time period will the corresponding event strategy be hit.

[0059] In addition, the user defines the trigger event type through the interface control. It should be noted that in the embodiment of the present application, the user can select multiple trigger event types. For example, the defense zone alarm and anti-dismantling alarm are selected as trigger event types through the interface control. Only when the defense zone alarm or anti-dismantling alarm occurs will the corresponding event strategy be hit.

[0060] This application defines the trigger time period and trigger event type through interface controls, so as to trigger the corresponding event linkage action only when the specified trigger event type occurs within the set trigger time period. Therefore, this application can simplify the trigger conditions of event linkage actions in terms of time and event type through interface controls, can adapt to the complex needs of different IoT application scenarios, and at the same time improve the flexibility of the configuration process of the IoT application system.

[0061] In some embodiments of the present application, the above-mentioned event policy also includes a device list, wherein the Internet of Things devices applicable to the event policy are selected through the interface control and added to the device list.

[0062] Specifically, users can select multiple IoT devices through interface controls and add them to the device list. Taking the application scenario of accepting and processing alarm events of intrusion anti-theft device defense zones as an example, only alarms from IoT devices in the device list will hit the corresponding event strategy.

[0063] This application selects IoT devices applicable to the event policy through interface controls, which can achieve accurate management and control of IoT devices, ensure that event policies are only effective for specified IoT devices, and adapt to the differentiated needs of IoT devices in different IoT application scenarios. In addition, the use of interface controls to achieve visual configuration of IoT application systems simplifies the configuration process of event policies and helps improve the configuration efficiency of IoT application systems.

[0064] In some embodiments of the present application, the interface control is also used to configure the visual interface of the Internet of Things application system, and the attribute display area and device control button of each Internet of Things device are generated on the visual interface through the interface control, and the attribute display area and the device control button are respectively associated with the physical model of the Internet of Things device.

[0065] The object model is an important part of the IoT field. It is used to describe and define the properties, behaviors, states, and interaction methods of IoT devices. It abstracts and models the data and functions of IoT devices such as sensors and smart home devices in a digital form, allowing developers to understand and control devices through the object model. Among them, the object model provides a standardized interface to achieve interaction with IoT devices, that is, you can view the property status of IoT devices, and you can also control IoT devices to perform related services.

[0066] In the IoT application system proposed in the embodiment of the present application, although the configuration requirements of users are mostly different, there are many interface controls in the presented visual interface that are the same and reusable. For example, the IoT application software needs to display the current status of the IoT device, including the offline status and device attribute status, and needs to configure the function of remotely controlling the device. Therefore, the interface controls proposed in the embodiment of the present application have the following functions:

[0067] (1) Support users to set device icons corresponding to IoT devices to visually display the type of IoT devices;

[0068] (2) Support users to associate the device name, device location, and fields in the background database table of the offline IoT application system with the IoT device to display the name, location, and offline status of the IoT device;

[0069] (3) Supporting users to add one or more device attribute status values ​​in the above attribute display area and associate them with the attribute fields in the object model. For example, as an IoT device, the device attributes of an air conditioner include current temperature, set temperature, wind speed, and humidity. The relevant information of the air conditioner device attributes can be displayed in the attribute display area through the configuration of the interface controls;

[0070] (4) Support users to add one or more device control buttons and associate them with the service fields in the object model. For example, the device control buttons of an air conditioner include a switch button, a wind speed adjustment button, and a self-cleaning button. By configuring the interface controls, the device control buttons of the air conditioner are associated with the service fields of the object model to enable users to call related service commands by clicking the device control buttons.

[0071] It should be noted that the above-mentioned object model has different settings of attribute fields and service fields according to different types of IoT devices.

[0072] The embodiment of the present application implements the above configuration on the visual interface through interface controls, realizes visual management of IoT devices, and greatly improves the user interaction experience of the IoT application system.

[0073] In some embodiments of the present application, the functional node is configured into an action logic chain based on the setting of the event trigger condition and the event linkage action, wherein the functional node includes at least one of a start node, a database query node, a database insert node, an API call node, and an end node.

[0074] Specifically, in some embodiments of the present application, the start node is used to support external input parameters, the database query node is used to support querying data in the background database according to preset conditions, the database insertion node is used to support saving data in the background database, the API (Application Programming Interface) call node is used to support configuration calling of an external HTTP interface, and the end node is used to end the action and exit.

[0075] Furthermore, the process of configuring the function node into an action logic chain based on the setting of the event triggering condition and the event linkage action includes the following steps:

[0076] Step S310, setting the start node, and selecting one of the database query node and the database insert node according to the event triggering condition to connect after the start node to generate a first initial logic chain;

[0077] Step S320, determining the execution device corresponding to each of the event linkage actions, and calling the API call node built into the low-code platform for the execution device;

[0078] Step S330, arranging the API call nodes and the end nodes according to the sequence of the event linkage actions to generate a second initial logic chain;

[0079] Step S340: splice the second initial logic chain after the first initial logic chain to obtain the action logic chain.

[0080] The following describes in detail the configuration process of the above action logic chain by taking the application scenario of receiving and processing the alarm event of the intrusion anti-theft device defense zone as an example.

[0081] In the application scenario of receiving and processing alarm events of intrusion prevention equipment defense zones, user needs include: recording equipment alarm logs, linking voice broadcasts to prompt alarms, linking cameras in the alarm area to record and save alarm scene videos in real time, and linking to send text messages to security managers.

[0082] Based on the above functional nodes, you can configure Figure 2 The action logic chain shown. Since it is necessary to record the equipment alarm log, it is necessary to select the database insertion node 102 to insert the alarm record, and connect the start node 101 and the database insertion node 102 as the first initial logic chain, and the connection direction points to the database insertion node 102. In view of the need for linkage voice broadcast to prompt the occurrence of an alarm, the first API call node 103 is selected to call the voice broadcast interface. In view of the need for linkage with the camera in the alarm area to record in real time and save the video of the alarm scene, the second API call node 104 is selected to call the linkage recording interface, and it is connected after the first API call node 103. In view of the need to send text messages to the security person in charge, the third API call node 105 is selected to call the text message sending interface, and it is connected after the second API call node 104, and finally the end node 106 is connected after the third API call node 105.

[0083] It can be seen that the first API call node 103, the second API call node 104, the third API call node 105 and the end node 106 are sequentially connected as the second initial logic chain, and the second initial logic chain is spliced ​​after the first initial logic chain to obtain the action logic chain. The application scenario that can be realized by the action logic chain is to receive the alarm record of the intrusion of the anti-theft device defense zone, and insert the alarm record into the background database of the Internet of Things application system, and then call the voice broadcast interface, the linkage video interface and the SMS sending interface in sequence to realize the alarm prompt.

[0084] It should be noted that each functional node is connected by a directional line, and the direction of the line represents the order of action execution. In addition, the above process simplifies the configuration of the action logic chain in a visual way by selecting and dragging the interface controls on the user interface of the Internet of Things application system to arrange the order of functional nodes.

[0085] Therefore, this application avoids the tedious process of manually writing complex logic through the selection and arrangement of functional nodes, greatly simplifies the process of business logic configuration of the Internet of Things application system, and improves the development capabilities for Internet of Things application scenarios, which helps to improve the efficiency and flexibility of the configuration of the Internet of Things application system.

[0086] In some embodiments of the present application, the backend server is deployed with a Kafka distributed messaging system so as to distribute and send commands of the action logic chain based on the Kafka distributed messaging system;

[0087] Wherein, a Kafka topic corresponding to the command is set on the back-end server, and the Kafka topic is divided into a plurality of partitions so that the command can be evenly distributed and sent to each of the partitions.

[0088] The Kafka distributed messaging system is a distributed, partition-supported, Zookeeper-coordinated messaging system that can process large amounts of data in real time to meet a variety of demand scenarios. The Kafka distributed messaging system has the following core components:

[0089] (1) Producer: A producer is a client that writes data to a topic.

[0090] (2) Consumer: A consumer is a client that reads data from a topic.

[0091] (3) Topic: Data in the Kafka distributed messaging system is classified by topic. Each topic can be understood as a specific type of message queue. Producers send messages to a specific topic, and consumers read messages from the topic. For example, there may be an alarm topic for an intrusion alarm device zone alarm event, which is used to store all alarm records.

[0092] (4) Partition: Each topic is divided into multiple partitions. Partitioning allows data to be processed in parallel, improving Kafka's throughput. Messages within each partition are ordered, but there is no global order between partitions. The benefit of partitioning is that it makes the Kafka distributed messaging system highly scalable, because each partition can be processed in parallel on different servers.

[0093] In addition, in order to maintain the stability and reliability of the Internet of Things application system when processing high-concurrency commands, when at least one of the partitions fails, the commands of the action logic chain are randomly distributed to the remaining partitions that have not failed.

[0094] For example, for the above-mentioned intrusion anti-theft device zone alarm event, set the Kafka topic as the alarm topic, and set 5 partitions in the topic. When the event occurs, assuming that the IoT device reports 100 alarm records concurrently at a certain moment, each partition can be allocated to process 20 alarm records, greatly improving the concurrent processing capability. The balancing mechanism of the Kafka distributed messaging system can achieve the average distribution of zone alarms to each partition, so that multiple partitions can be allocated to process events, thereby providing the system with concurrent processing capabilities.

[0095] In addition, if one of the five partitions fails at a certain moment and the remaining four partitions can still operate normally, the Kafka distributed messaging system in the embodiment of the present application can automatically randomly distribute the alarm records originally assigned to the failed partition to the remaining four partitions. For example, one partition is randomly selected from the four partitions to distribute the alarm records assigned to the failed partition. In this way, the remaining four partitions can continue to process all alarm records without causing system failures and event losses.

[0096] Accordingly, please refer to Figure 3 , the embodiment of the present application provides an IoT application system configuration device based on a low-code platform, the device comprising:

[0097] A strategy generation module 610, for generating an event strategy by triggering an interface control, wherein the interface control is built into the low-code platform, and the event strategy is used to define event triggering conditions and event linkage actions for IoT application scenarios;

[0098] A business logic orchestration module 620, for calling function nodes related to the event strategy in the low-code platform, and configuring the function nodes into an action logic chain based on the event triggering conditions and the setting of the event linkage actions;

[0099] The distributed execution module 630 is used to distribute the commands for executing the action logic chain to the back-end server of the low-code platform, and configure the Internet of Things application system to execute the commands of the action logic chain when the event triggering conditions are met.

[0100] In some optional implementations, the business logic orchestration module 620 includes:

[0101] A first logic chain generating unit 621 is used to set the start node and select one of the database query node and the database insert node according to the event triggering condition to connect after the start node to generate a first initial logic chain;

[0102] A calling node unit 622 is used to determine the execution device corresponding to each of the event linkage actions, and call the API call node built into the low-code platform for the execution device;

[0103] A second logic chain generating unit 623, configured to arrange the API call nodes and the end nodes according to the sequence of the event linkage actions to generate a second initial logic chain;

[0104] The splicing unit 624 is used to splice the second initial logic chain after the first initial logic chain to obtain the action logic chain.

[0105] The further functional description of each of the above modules and units is the same as that of the above corresponding embodiments and will not be repeated here.

[0106] The Internet of Things application system configuration device in this embodiment is presented in the form of a functional unit, where the unit refers to an ASIC (Application Specific Integrated Circuit) circuit, a processor and memory that executes one or more software or fixed programs, and / or other devices that can provide the above functions.

[0107] See also Figure 4 , Figure 4 is a schematic diagram of the structure of a computer device provided in an embodiment of the present application, such as Figure 4 As shown, the computer device includes: one or more processors 10, a memory 20, and interfaces for connecting various components, including high-speed interfaces and low-speed interfaces. Various components are connected to each other using different buses for communication, and can be installed on a common mainboard or installed in other ways as needed. The processor can process the instructions executed in the computer device, including instructions stored in or on the memory to display the graphical information of the GUI on an external input / output device (such as, a display device coupled to the interface). In some optional embodiments, if necessary, multiple processors and / or multiple buses can be used together with multiple memories and multiple memories. Similarly, multiple computer devices can be connected, and each device provides some necessary operations (for example, as a server array, a group of blade servers, or a multi-processor system). Figure 4 A processor 10 is taken as an example.

[0108] The processor 10 may be a central processing unit, a network processor or a combination thereof. The processor 10 may further include a hardware chip. The hardware chip may be a dedicated integrated circuit, a programmable logic device or a combination thereof. The programmable logic device may be a complex programmable logic device, a field programmable gate array, a general purpose array logic or any combination thereof.

[0109] The memory 20 stores instructions executable by at least one processor 10, so that the at least one processor 10 executes the method shown in the above embodiment.

[0110] The memory 20 may include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application required for at least one function; the data storage area may store data created according to the use of the computer device, etc. In addition, the memory 20 may include a high-speed random access memory, and may also include a non-transient memory, such as at least one disk storage device, a flash memory device, or other non-transient solid-state storage device. In some optional embodiments, the memory 20 may optionally include a memory remotely arranged relative to the processor 10, and these remote memories may be connected to the computer device via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0111] The memory 20 may include a volatile memory, such as a random access memory; the memory may also include a non-volatile memory, such as a flash memory, a hard disk or a solid state drive; the memory 20 may also include a combination of the above types of memory.

[0112] like Figure 4 As shown, the computer device further includes an input device 30 and an output device 40. The processor 10, the memory 20, the input device 30 and the output device 40 may be connected via a bus or other means.

[0113] The input device 30 can receive input digital or character information, and generate key signal input related to the user settings and function control of the computer device, such as a touch screen, a keypad, a mouse, a track pad, a touch pad, an indicator bar, one or more mouse buttons, a trackball, a joystick, etc. The output device 40 may include a display device, an auxiliary lighting device (e.g., an LED) and a tactile feedback device (e.g., a vibration motor), etc. The above-mentioned display device includes but is not limited to a liquid crystal display, a light emitting diode, a display and a plasma display. In some optional embodiments, the display device can be a touch screen.

[0114] The present application embodiment also provides a computer-readable storage medium. The above method according to the embodiment of the present application can be implemented in hardware, firmware, or implemented as a computer code that can be recorded in a storage medium, or is implemented as a computer code that is originally stored in a remote storage medium or a non-temporary machine-readable storage medium and will be stored in a local storage medium and downloaded through a network, so that the method described herein can be stored in such software processing on a storage medium using a general-purpose computer, a dedicated processor, or programmable or dedicated hardware. Among them, the storage medium can be a magnetic disk, an optical disk, a read-only storage memory, a random access memory, a flash memory, a hard disk or a solid-state hard disk, etc.; further, the storage medium can also include a combination of the above types of memories. It can be understood that a computer, a processor, a microprocessor controller, or programmable hardware includes a storage component that can store or receive software or computer code. When the software or computer code is accessed and executed by a computer, a processor, or hardware, the method shown in the above embodiment is implemented.

[0115] The embodiment of the present application provides a computer program product, which includes computer instructions, which are stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device executes the method of any embodiment of the present application.

[0116] Although the embodiments of the present application are described in conjunction with the accompanying drawings, those skilled in the art may make various modifications and variations without departing from the spirit and scope of the present application, and such modifications and variations are all within the scope defined by the appended claims.

[0117] The systems, devices, modules or units described in the above embodiments may be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, the computer may be, for example, a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.

[0118] For the convenience of description, the above device is described in various units according to their functions. Of course, when implementing the present application, the functions of each unit can be implemented in the same or multiple software and / or hardware.

[0119] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented in one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that include computer-usable program code.

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

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

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

[0123] 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.

[0124] Each embodiment in this specification is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the system embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

[0125] The above is only an embodiment of the present application and is not intended to limit the present application. For those skilled in the art, the present application may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.

[0126] Although the embodiments of the present application have been described in conjunction with the accompanying drawings, those skilled in the art may make various modifications and variations without departing from the spirit and scope of the present application, and such modifications and variations are all within the scope defined by the appended claims.

Claims

1. The method for configuring an IoT application system based on a low-code platform is characterized in that: The Internet of Things application system configuration method comprises: Generate an event strategy by triggering an interface control, wherein the interface control is built into the low-code platform, and the event strategy is used to define event triggering conditions and event linkage actions for IoT application scenarios; Calling a function node related to the event strategy in the low-code platform, and configuring the function node into an action logic chain based on the event triggering condition and the setting of the event linkage action; The commands for executing the action logic chain are distributed and sent to the back-end server of the low-code platform, and the Internet of Things application system is configured to execute the commands of the action logic chain when the event triggering conditions are met.

2. The method for configuring an Internet of Things application system according to claim 1, characterized in that: The event triggering condition includes a triggering time period and a triggering event type, wherein the triggering time period and the triggering event type are defined through the interface control to trigger the event linkage action when the triggering event type occurs within the triggering time period.

3. The method for configuring an Internet of Things application system according to claim 1 or 2, characterized in that: The event strategy also includes a device list, wherein an IoT device applicable to the event strategy is selected through the interface control and added to the device list.

4. The method for configuring the Internet of Things application system according to claim 1, characterized in that: The function node includes at least one of a start node, a database query node, a database insert node, an API call node, and an end node.

5. The method for configuring the Internet of Things application system according to claim 4, characterized in that: The configuring the function nodes into an action logic chain based on the setting of the event triggering condition and the event linkage action includes: Setting the start node, and selecting one of the database query node and the database insert node according to the event triggering condition to connect after the start node to generate a first initial logic chain; Determine the execution device corresponding to each of the event linkage actions, and call the API call node built into the low-code platform for the execution device; Arranging the API call nodes and the end nodes according to the sequence of the event linkage actions to generate a second initial logic chain; The second initial logic chain is spliced ​​after the first initial logic chain to obtain the action logic chain.

6. The method for configuring the Internet of Things application system according to claim 1, characterized in that: The backend server is deployed with a Kafka distributed messaging system so as to distribute and send commands of the action logic chain based on the Kafka distributed messaging system; Wherein, a Kafka topic corresponding to the command is set on the back-end server, and the Kafka topic is divided into a plurality of partitions so that the command can be evenly distributed and sent to each of the partitions.

7. The method for configuring the Internet of Things application system according to claim 6, characterized in that: In the event that at least one of the partitions fails, commands of the action logic chain are randomly distributed to the remaining partitions that have not failed.

8. The method for configuring an Internet of Things application system according to claim 1, characterized in that: The interface control is also used to configure the visual interface of the Internet of Things application system. The method also includes: The interface controls are used to generate a property display area and a device control button for each of the IoT devices in the visual interface, and the property display area and the device control button are respectively associated with the physical model of the IoT device.

9. An IoT application system configuration device based on a low-code platform, characterized in that: The Internet of Things application system configuration device includes: A strategy generation module, used to generate an event strategy by triggering an interface control, wherein the interface control is built into the low-code platform, and the event strategy is used to define event triggering conditions and event linkage actions for IoT application scenarios; A business logic orchestration module, used to call function nodes related to the event strategy in the low-code platform, and configure the function nodes into an action logic chain based on the event triggering conditions and the setting of the event linkage actions; The distributed execution module is used to distribute the commands for executing the action logic chain to the back-end server of the low-code platform, and configure the Internet of Things application system to execute the commands of the action logic chain when the event triggering conditions are met.

10. A computer device, characterized in that include: A memory and a processor, the memory and the processor are communicatively connected to each other, the memory stores computer instructions, and the processor executes the Internet of Things application system configuration method based on a low-code platform as described in any one of claims 1 to 8 by executing the computer instructions.

Images