Visual scene management method and system for Internet of Things

Abstract

The invention relates to an Internet of Things visual scene management method and system, and belongs to the field of Internet of Things equipment management. Graphical nodes of corresponding equipment are obtained through rendering function registration, the graphical nodes comprise message source nodes, conditional filtering nodes and message distribution nodes, the message source nodes forward object model data, the conditional filtering nodes filter the object model data, and the message distribution nodes forward the object model data to a target address. Drawing connecting lines for the graphical nodes, and setting a transmission path of object model data; setting parameters in each graphical node through the form content of the form corresponding to the graphical node; the parameters comprise a source address of object model data in the message source node, a filtering condition in the condition filtering node, and a target address and a message distribution mode in the message distribution node. According to the method, the platform can effectively and flexibly deal with various complex scenes through visualized and self-defined form contents of the equipment, and the adaptability and expansibility of the system are remarkably improved.

Description

Technical Field

[0001] This invention relates to a method and system for visual scene management in the Internet of Things (IoT), belonging to the field of IoT device management. Background Technology

[0002] The power Internet of Things (IoT) involves a large number of widely distributed devices, making the safe and stable operation of these devices a critical issue. Scenario management manages and schedules the resources of the power IoT platform, collects and analyzes platform data, and monitors the device status and environmental parameters in various scenarios in real time. Once anomalies or potential risks are detected, immediate measures can be taken to address them, thereby achieving cross-scenario data sharing, business collaboration, and resource integration.

[0003] However, the large number of devices connected to the power IoT platform has significantly increased the difficulty of management and monitoring. Visualized scene management, through an intuitive graphical interface and interactive operations, displays the real-time operating status, data information, and resource consumption of power IoT devices. Visualized scene management provides strong support for the innovation and development of IoT platforms, thereby driving the development and optimization of new functions.

[0004] Web components in web development are widely used in various fields due to their strong adaptability and cross-platform advantages. Users can customize the components according to their own needs and they can run on different browsers and devices. However, the IoT visualization scene management technology based on web components is not yet mature and lacks a complete process. Summary of the Invention

[0005] The purpose of this invention is to provide a method and system for managing visualized IoT scenarios, in order to solve the problem that the current power IoT platform lacks a more intuitive graphical interface based on Web components and a more convenient interactive operating system.

[0006] To achieve the above objectives, the present invention includes: This invention discloses an IoT visualization scene management method. It registers graphical nodes corresponding to different IoT devices through a rendering function. These graphical nodes include message source nodes, conditional filtering nodes, and message distribution nodes. Message source nodes correspond to message source devices in the IoT devices that forward object model data uploaded by other IoT devices. Conditional filtering nodes correspond to conditional filtering devices in the IoT devices that filter object model data. Message distribution nodes correspond to message distribution devices in the IoT devices that forward the filtered object model data to a target address. The method sets the transmission path of object model data through lines drawn between the graphical nodes. The method sets the parameters of the graphical nodes through the content in the forms corresponding to the graphical nodes. These parameters include the source of the object model data in the message source nodes, the filtering conditions in the conditional filtering nodes, and the target address and message distribution method in the message distribution nodes.

[0007] Furthermore, there must be at least one filtering condition. The filtering condition is defined by selecting object model data, selecting an operator, filling in a numerical value, and, when there are two or more filtering conditions, selecting the relationship between the filtering conditions.

[0008] Furthermore, after connecting the graphical nodes, the connections between each node are validated. The conditions for passing the validation are: 1) The message source node connects to the condition filter node, and the condition filter node connects to the message distribution node; 2) There is one and only one line connecting the two nodes; If the connection fails the verification, the connection will be deleted and an error message will pop up.

[0009] Furthermore, after passing the verification, the message source node, condition filter node, and message distribution node fill in their respective content into the corresponding forms.

[0010] Furthermore, the message distribution node is configured with at least one message distribution method, which includes HTTP forwarding, message queue, downlink-device attribute, and downlink-device service.

[0011] Furthermore, the message queue uses Kafka forwarding, including platform Kafka and custom Kafka.

[0012] Furthermore, graphical nodes are formed by dragging the corresponding icons in the drag panel to the drawing panel. During the dragging process, the graphical nodes are obtained by re-registering the rendering function, which allows for connection and vector scaling.

[0013] Furthermore, the rendering function is the h function.

[0014] The present invention provides an Internet of Things (IoT) visualization scene management system, including a processor, which executes a computer program to implement an IoT visualization scene management method.

[0015] The beneficial effects of this invention are as follows: This invention is a pioneering invention. It registers graphical nodes corresponding to different IoT devices through a rendering function. These graphical nodes include message source nodes, conditional filtering nodes, and message distribution nodes. Message source nodes correspond to message source devices in the IoT device that forward object model data uploaded by other IoT devices. Conditional filtering nodes correspond to conditional filtering devices in the IoT device that filter object model data. Message distribution nodes correspond to message distribution devices in the IoT device that forward the filtered object model data to the target address. By graphically representing and managing IoT devices, a more intuitive graphical interface is provided. The transmission path of object model data is set through lines drawn between graphical nodes; parameters in each graphical node are set through the form content corresponding to the graphical nodes. These parameters include the source address of the object model data in the message source node, the filtering conditions in the conditional filtering node, and the target address and message distribution method in the message distribution node. By filling in the corresponding form content, users can customize the data source, filtering conditions, and target address according to their needs. This invention, through the visualization of IoT devices and the customization of form content, effectively enables the IoT platform to flexibly cope with various complex scenarios, significantly improving the adaptability and scalability of the IoT system. Attached Figure Description

[0016] Figure 1 This is a schematic diagram of the drawing component of the present invention; Figure 2 This is a schematic diagram of the drawing process of the present invention. Detailed Implementation

[0017] To make the objectives, technical solutions, and advantages of the present invention clearer, the present invention will be further described in detail below with reference to the accompanying drawings and embodiments.

[0018] The concept of this invention is to use Web components to realize the visual scene management of various IoT devices in the IoT platform. Considering the need to realize the intuitiveness of the data collected by IoT devices and the interactivity of the system, the IoT devices to be managed are graphically represented, and scene management that can be customized according to user needs is realized through appropriate methods.

[0019] Method Implementation Examples: This embodiment provides a method for visual scene management in the Internet of Things (IoT). The invention uses a drawing component to perform visual scene management for IoT devices. This drawing component consists of a drag-and-drop panel and a drawing panel. The drag-and-drop panel includes message source nodes, condition filter nodes, and message distribution nodes, which have been registered as icons through a rendering function. Message source nodes correspond to message source devices in the IoT device that forward object model data uploaded by other IoT devices. Condition filter nodes correspond to condition filter devices in the IoT device that filter object model data. Message distribution nodes correspond to message distribution devices in the IoT device that forward the filtered object model data to a target address. These nodes can be dragged into the drawing panel, and the nodes in the drawing panel can be dragged, clicked, deleted, scaled, and connected.

[0020] The message source node includes object model data reported by IoT devices, namely attribute and event function point data reported by IoT devices. These correspond to attribute data (device operation information and status) and event data (changes or anomalies in device operation) actively sent by IoT devices, respectively. The message source node processes the attribute and event data actively sent by IoT devices in the IoT platform, and then forwards them to the conditional filtering node. It also supports user-defined message scope, which can be triggered by specified products or devices.

[0021] Conditional filtering nodes are used to filter messages sent from message source nodes. Only messages that meet the filtering conditions are forwarded. Multiple filtering conditions can be specified, and the relationship between each condition is either "AND" or "OR". Filtering conditions are defined by selecting object model attributes and events, selecting operators, entering numerical values, and selecting the relationships between multiple filtering conditions. When object model data sent by the message source node meets the filtering conditions, the data that meets the filtering conditions is distributed to the message distribution node.

[0022] The message distribution node forwards processed messages to the IoT platform communication component used to push messages to applications. Supported distribution methods include MQ (Message Queue), HTTP (Hypertext Transfer Protocol) forwarding, downlink-device attribute, and downlink-device service. Multiple distribution methods can be configured for a single scenario; failure of one distribution action will not affect other actions. In summary, the structure of this drawing component is as follows: Figure 1 As shown.

[0023] HTTP forwarding uses an HTTP push communication component to send messages to the application server as HTTP / HTTPS POST requests, and then the application server pushes the messages to the application.

[0024] Message Queues (MQ) are crucial communication components in distributed systems. Taking Kafka forwarding as an example, Kafka forwarding includes platform Kafka and custom Kafka. Platform Kafka refers to Kafka Brokers deployed on a cloud platform. The IoT platform forwards processed messages to the Kafka Brokers. Applications only need to fill in the Topic and Consumer Group, and then consume messages using the URL (Uniform Resource Locator) provided by the cloud platform. Custom Kafka refers to Kafka Brokers deployed on the application side and maintained by the application. The IoT platform pushes messages to the application based on the configured Kafka address and Topic. As another embodiment, any MQ that can guarantee the successful forwarding and delivery of messages to users through appropriate methods can be used as a message distribution method for this rendering component.

[0025] Downlink-device attributes refer to the current status data of a device being forwarded to the IoT platform via downlink-device attributes. The IoT platform then sends instructions to the device to set the device's attribute values, which are used to control or modify the device's status or behavior (e.g., fault remission).

[0026] Downlink-device service refers to the forwarding of data on the current status of a device to the IoT platform through downlink-device service. The IoT platform then sends instructions to the device to invoke its services. Device services refer to instructions or methods that the device can invoke externally.

[0027] After dragging graphical nodes from the drag panel to the drawing panel, the drawing component adds listener events for nodes such as node click, node addition, node deletion, and historical data. After connecting nodes within the drawing panel, the drawing component adds listener events for connections such as connection addition, connection deletion, connection validation, and historical data. These listener events enable operations such as node click, node dragging, connection drawing, connection deletion, horizontal alignment, vertical alignment, undo, cancel undo, panel zoom in, and panel zoom out, ensuring users can better view and edit nodes and connections.

[0028] After the drawing component is instantiated, when dragging graphical nodes that have already been registered via the rendering function from the drag panel to the drawing panel, each node needs to be registered again via the rendering function to ensure correct display and use on the drawing panel. The rendering function is the `h` function. Registering each node via the `h` function converts the node into an SVG (Scalable Vector Graphics) tag. A complete SVG document includes multiple SVG tags, and an SVG tag can include multiple SVG child tags.

[0029] When drawing connections for nodes in the drawing panel, a connection validation listener function is required. The validation conditions are: 1. Whether the connections are made sequentially in the order of message source node, condition filter node, and message distribution node; 2. Whether there is exactly one connection between any two nodes. These conditions are configured as node attributes through a validator. If the connection validation fails, the connection will be deleted and an error message will be displayed. If the connection validation passes, the form content for the corresponding message source node, condition filter node, and message distribution node is filled in. After filling in the form content, it needs to be validated again. If the validation passes, the form is saved to the database, and the drawing process ends. Otherwise, the form content continues to be filled in until the form content passes validation. The overall process is as follows: Figure 2 As shown in the diagram. By filling in the form content corresponding to the message source node, users can specify which devices will upload the object model data; by filling in the form content corresponding to the conditional filter node, users can configure the filtering conditions within the conditional filter node; and by filling in the form content corresponding to the message distribution node, users can configure the distribution method and target address within the message distribution node. By filling in the forms for each node, message source nodes from different devices and data sources can be integrated into the IoT platform, facilitating the analysis of massive amounts of data. Furthermore, the attributes or configurations of each node can be displayed to users in form format, allowing for convenient management of node attributes or configurations. When users want to change business logic, they can quickly adjust the node configuration by modifying the form content without modifying the underlying code. By monitoring the information recorded in the forms, the IoT platform can monitor the operating status of each node in real time. Once an anomaly is detected, the problem can be quickly located, and appropriate measures can be taken.

[0030] Taking the drawing of a rectangle as an example, the overall process of this invention is illustrated. The message scope in the message source node is selected, the filtering conditions in the conditional filter node are defined, and the message distribution method in the message distribution node is determined. After the drawing component is instantiated, the already rendered rectangular message source node, conditional filter node, and message distribution node in the drag panel are dragged to the drawing panel. During the dragging process, each node is registered through the h function. Each h function represents an SVG tag, with the following format: h( 'rect', { x: 5, y: 2, width: 384 Height: 77, rx: 6, fill: "#F8F8F8"} ) This represents drawing a rectangle with coordinates (5, 2), width 384, height 77, and color "#F8F8F8". Each node, after registration, can be used normally in the drawing panel. Connections are drawn between nodes. After the connections are completed, once the connection validation function is passed, the corresponding form content for each node is filled in, and all form content is validated. After the form content validation passes, the drawing process of the drawing component ends. For example, the message source node is configured to upload temperature data from a temperature sensor, the filter node's filter condition is temperature greater than or equal to 30 "AND" less than or equal to 50, and the message distribution node's message distribution method is HTTP forwarding with a target address of a server. In this case, the temperature message collected by the message source node can be transmitted normally to the message distribution node through the custom filter condition in the filter node. Then, the message distribution node will send the message to the server via an HTTPS POST request. The server will periodically push the message, which is displayed as a rectangle on the web page.

[0031] System Implementation Example: This embodiment provides an Internet of Things (IoT) visualization scene management system. The system includes a processor. When performing visualization scene management on IoT devices, the processor executes a computer program to implement an IoT visualization scene management method as described in the method embodiment. Since the description of the method is already clear enough, it will not be repeated here.

[0032] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention and not to limit it. Although the present invention has been described in detail with reference to the above embodiments, those skilled in the art should understand that modifications or equivalent substitutions can still be made to the specific implementation of the present invention. Any modifications or equivalent substitutions that do not depart from the spirit and scope of the present invention should be covered within the scope of protection of the claims of the present invention.

Claims

1. A method for managing visualized scenes for an Internet of Things, characterized in that, The graphical nodes corresponding to different Internet of Things devices are obtained by rendering function registration, and the graphical nodes include a message source node, a condition filtering node, and a message distribution node. The message source node corresponds to a message source device in the Internet of Things device for forwarding uploaded physical model data of other Internet of Things devices. The condition filtering node corresponds to a condition filtering device in the Internet of Things device for filtering physical model data. The message distribution node corresponds to a message distribution device in the Internet of Things device for forwarding filtered physical model data to a target address. A transmission path of the physical model data is set through a connection line drawn between the graphical nodes. Parameters of the graphical nodes are set through content in a corresponding form of the graphical nodes. The parameters include a source of the physical model data in the message source node, a filtering condition in the condition filtering node, and a target address and a message distribution mode in the message distribution node.

2. The IoT visualized scene management method of claim 1, wherein, The filtering condition is defined by selecting physical model data, selecting an operator, filling in a value, and selecting a relationship between the filtering conditions when there are more than two filtering conditions.

3. The IoT visualized scene management method of claim 1, wherein, After the connection line between the graphical nodes is drawn, the connection between the nodes is also checked. The conditions for passing the check are as follows: 1) The message source node is connected to the condition filtering node, and the condition filtering node is connected to the message distribution node. 2) There is only one connection line between two nodes. When the connection line fails the check, the connection line is deleted and an error prompt message is popped up.

4. The IoT visualized scene management method of claim 3, wherein, After passing the check, the message source node, the condition filtering node, and the message distribution node fill in the content of the corresponding form.

5. The IoT visualized scene management method of claim 1, wherein, The message distribution node is provided with at least one message distribution mode, and the message distribution mode includes HTTP forwarding, message queue, down-device attribute, and down-device service.

6. The IoT visualized scene management method of claim 5, wherein, The message queue uses kafka forwarding including platform kafka and custom kafka.

7. The IoT visualized scene management method of claim 1, wherein, The graphical nodes are formed by dragging the corresponding icons registered by the rendering function in the drag panel to the drawing panel. During the dragging process, the graphical nodes are obtained through re-registration of the rendering function, which can be connected and vector scaled.

8. The IoT visualized scene management method of claim 7, wherein, The rendering function is an h function.

9. An Internet of Things visualized scene management system comprising a processor, characterized in that, The processor is configured to execute a computer program to implement the Internet of Things visualization scene management method of any one of claims 1-8.

Images