Cascade management and control system for park

Abstract

The invention provides a cascade management and control system for a park. The cascade management and control system comprises a central park management and control system, n marginal park management and control systems, wherein the N marginal park management and control systems are in communication connection with the central park management and control system step by step according to a preset hierarchical relationship; the central park management and control system directly manages equipment in the central park, the N edge park management and control systems directly manage equipment in the corresponding edge parks, and the superior park management and control systems in the central park management and control system and the edge park management and control systems can send control instructions to the subordinate park management and control systems. And the lower-level park management and control system can synchronize data to the upper-level park management and control system. According to the invention, the central park management and control system and the edge management and control system can directly manage equipment in the corresponding park, thereby facilitating data transmission and timely response; the superior park management and control system can send a control instruction to the subordinate park management and control system, and the subordinate park management and control system can synchronize data to the superior park management and control system, thereby facilitating the realization of efficient cascade management and data collaboration.

Description

Technical Field

[0001] The present application belongs to the technical field of Internet of Things data processing, and in particular, relates to a park cascade management and control system. Background Art

[0002] With the rapid development of digital construction of smart cities, Internet of Things technology has gradually become the core of smart park management. However, the technical architecture of traditional park management systems generally adopts a decentralized solution, which has the limitations of decentralized data storage and processing, resulting in weak system data collaborative sharing capabilities, poor system scalability, and slow processing response, making it difficult to effectively respond to the growing data flow and management needs. At the same time, with the rapid growth in the number of sensors and devices, the demand for real-time data processing continues to increase, and the park management system faces huge challenges in data collection and computing capabilities. The existing park management system mainly relies on a single cloud control mode, which has problems such as data transmission delay and insufficient response speed. Summary of the invention

[0003] In view of the above-mentioned shortcomings of the prior art, the purpose of the present application is to provide a park cascade management and control system to solve the above-mentioned problems.

[0004] The park cascade control system provided in this application includes:

[0005] Central park management and control system;

[0006] N edge park management and control systems, wherein the N edge park management and control systems are communicatively connected with the central park management and control system step by step according to a preset hierarchical relationship, and N is a positive integer;

[0007] Among them, the central park management and control system directly manages the equipment in the central park, the N edge park management and control systems directly manage the equipment in the corresponding edge parks, and the upper-level park management and control systems in the central park management and control system and the edge park management and control systems can send control instructions to the lower-level park management and control systems, and the lower-level park management and control systems can synchronize data with the upper-level park management and control systems.

[0008] In one embodiment of the present application, the lower-level park management and control system may synchronize incremental data and full data to the upper-level park management and control system, and the full data synchronization includes:

[0009] The lower-level park management and control system divides the data to be synchronized into multiple modules according to the type;

[0010] The lower-level park management and control system divides the data of each module in the multiple modules into different batches;

[0011] The lower-level park management and control system executes an asynchronous concurrent strategy to synchronize different batches of data of each module to the upper-level park management and control system in batches;

[0012] Among them, the lower-level park management and control system records the data synchronization progress of each module during the full data synchronization process. After the synchronization of any module among the multiple modules is interrupted and restored, the last batch of successfully transmitted records before the interruption is used as the anchor point to resume the transmission from the breakpoint.

[0013] In one embodiment of the present application, after the lower-level park management and control system executes an asynchronous concurrency strategy and synchronizes different batches of data of each module to the upper-level park management and control system in batches, the lower-level park management and control system performs a data consistency check, and the data consistency check adopts a modular asynchronous check strategy, including:

[0014] The lower-level park management and control system searches for each batch of data of the first module and generates a first hash value corresponding to each batch of data, where the first module is any module among the multiple modules;

[0015] The lower-level park management and control system sends verification information to the upper-level park management and control system, wherein the verification information includes information of each batch of data;

[0016] The upper-level park management and control system queries each batch of data of the first module based on the verification information, and generates a second hash value corresponding to each batch of data.

[0017] The upper-level park management and control system sends the second hash value corresponding to each batch of data to the lower-level park management and control system;

[0018] The lower-level park management and control system verifies the first hash value and the second hash value corresponding to each batch of data. When the first hash value and the second hash value corresponding to the Mth batch of data are different, the lower-level park management and control system performs full supplementary sampling of each batch of data of the first module, where M is a positive integer.

[0019] In one embodiment of the present application, a direct connection device and an edge gateway can be connected to the park management and control system, and the devices of the direct connection device and the edge gateway both include data acquisition devices;

[0020] The directly connected device communicates with the park management and control system via HTTP protocol or MQTT protocol;

[0021] The edge gateway communicates with the park management and control system via the OPC UA or MQTT protocol, and the park management and control system communicates with the device of the edge gateway via the edge gateway;

[0022] Among them, the park management and control system is any system among the central park management and control system and the edge park management and control system.

[0023] In one embodiment of the present application, at least one device type can be created based on the park management and control system, and each device type in the at least one device type includes the following multiple information: message protocol type, offline timeout detection information of the device, data storage period of the device, device attributes, pre-processing information of device data, and alarm events;

[0024] The park management and control system is connected to a directly connected device, including:

[0025] Binding the directly connected device to a corresponding device type in the at least one device type;

[0026] After the park management and control system is connected to the edge gateway, it also includes:

[0027] Access a gateway sub-device associated with the edge gateway, and bind the gateway sub-device to a corresponding device type in the at least one device type.

[0028] In one embodiment of the present application, the edge gateway includes a first edge gateway that communicates with the park management and control system via OPC UA, and the first edge gateway includes a kepserver and a data acquisition controller;

[0029] The park management and control system and the first edge gateway may start node synchronization, so that the park management and control system synchronizes information of the first edge gateway, including channel information, information of the first device, and location;

[0030] When the park management and control system controls the first edge gateway to start, the park management and control system synchronizes the collected data of the first device and stores it in the cache;

[0031] In the park management and control system, when the first gateway sub-device has been connected and the device attributes of the first gateway sub-device are bound to the location of the first device, when the first edge gateway and the first gateway sub-device are controlled to be turned on by the park management and control system, the park management and control system synchronizes the collected data of the first device and stores it in the timing library.

[0032] In one embodiment of the present application, the edge gateway includes a visual process orchestration tool that communicates with the park management and control system via the MQTT protocol;

[0033] Through the park management and control system, information of the second gateway sub-device associated with the visual process orchestration tool can be exported;

[0034] The visual process orchestration tool is used to perform offline synchronization with the park management and control system to obtain information of the second gateway sub-device, and bind the information of the second gateway sub-device with the point information of the second device in the visual process orchestration tool;

[0035] When the visual process orchestration tool and the second gateway sub-device are both turned on by the park management and control system, the park management and control system synchronizes the collected data of the second device and stores it in the timing library.

[0036] In one embodiment of the present application, the edge gateway includes a data acquisition controller that communicates with the park management and control system via the MQTT protocol;

[0037] The park management and control system and the data acquisition controller can start node synchronization, so that the park management and control system synchronizes the information of the data acquisition controller, including channel information, information of the third device and point position;

[0038] In the park management and control system, when the third gateway sub-device has been connected and the device attributes of the third gateway sub-device are bound to the location of the third device, when the data acquisition controller and the third gateway sub-device are controlled by the park management and control system to be turned on, the park management and control system synchronizes the collected data of the third device and stores it in the timing library.

[0039] In one embodiment of the present application, the edge gateways are each provided with a heartbeat script to periodically send a heartbeat signal and a communication address to the park management system, and the park management system updates the status of the edge gateway based on the heartbeat monitoring mechanism.

[0040] In one embodiment of the present application, the central park management and control system and the N edge park management and control systems all adopt a unified technical framework, and the upper-level park management and control system can synchronously view the execution results of the control instructions through a callback mechanism.

[0041] Beneficial effects of the present application: In the present application, N edge park control systems are communicated and connected with the central park control system step by step according to the preset hierarchical relationship, that is, the central park control system and the N edge park control systems are cascaded up and down. The present application can adapt to park scenarios of different sizes and types through a flexible cascade architecture. For example, when the edge park control system is added, it can be set at the corresponding level of the cascade architecture. The present application is not a single cloud control mode, but a cascade architecture control mode of "one center and multiple bases" (one central park control system and multiple edge control systems). The central park control system and the edge control system can directly manage the equipment in the corresponding park respectively, which is conducive to data transmission and timely response; the upper park control system in the park cascade control system can send control instructions to the lower park control system, and the lower park control system can synchronize data with the upper park control system, which is conducive to efficient cascade management and data collaboration.

[0042] It should be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0043] The drawings herein are incorporated into the specification and constitute a part of the specification, showing embodiments consistent with the present application, and together with the specification, are used to explain the principles of the present application. Obviously, the drawings described below are only some embodiments of the present application, and for those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative work. In the drawings:

[0044] Figure 1 It is a schematic diagram of the architecture of a park cascade control system shown in an exemplary embodiment of the present application;

[0045] Figure 2 is a schematic diagram of a device access architecture shown in an exemplary embodiment of the present application;

[0046] Figure 3 It is a schematic diagram of the major categories of equipment in a park management system shown in an exemplary embodiment of the present application;

[0047] Figure 4 It is one of the flow charts of cloud-edge collaboration shown in an exemplary embodiment of the present application;

[0048] Figure 5 This is the second flowchart of cloud-edge collaboration shown in an exemplary embodiment of the present application;

[0049] Figure 6 This is the third flowchart of cloud-edge collaboration shown in an exemplary embodiment of the present application;

[0050] Figure 7FIG. 4 is a flowchart of a heartbeat response shown in an exemplary embodiment of the present application. DETAILED DESCRIPTION

[0051] The following will describe the implementation methods of the present application with reference to the accompanying drawings and preferred embodiments. Those skilled in the art can easily understand other advantages and effects of the present application from the contents disclosed in this specification. The present application can also be implemented or applied through other different specific implementation methods, and the details in this specification can also be modified or changed in various ways based on different viewpoints and applications without departing from the spirit of the present application. It should be understood that the preferred embodiments are only for illustrating the present application, not for limiting the scope of protection of the present application.

[0052] It should be noted that the illustrations provided in the following embodiments are only schematic illustrations of the basic concept of the present application, and thus the drawings only show components related to the present application rather than being drawn according to the number, shape and size of components in actual implementation. In actual implementation, the type, quantity and proportion of each component may be changed at will, and the component layout may also be more complicated.

[0053] In the following description, a large number of details are discussed to provide a more thorough explanation of the embodiments of the present application. However, it is obvious to those skilled in the art that the embodiments of the present application can be implemented without these specific details. In other embodiments, well-known structures and devices are shown in the form of block diagrams rather than in detail to avoid making the embodiments of the present application difficult to understand.

[0054] Figure 1 A park cascade control system is shown in an exemplary embodiment of the present application, comprising:

[0055] Central park management and control system;

[0056] N edge park management and control systems, wherein the N edge park management and control systems are communicatively connected with the central park management and control system step by step according to a preset hierarchical relationship, and N is a positive integer;

[0057] Among them, the central park management and control system directly manages the equipment in the central park, the N edge park management and control systems directly manage the equipment in the corresponding edge parks, and the upper-level park management and control systems in the central park management and control system and the edge park management and control systems can send control instructions to the lower-level park management and control systems, and the lower-level park management and control systems can synchronize data with the upper-level park management and control systems.

[0058] The park cascade control system is a multi-layer cascade architecture that supports expansion, that is, it supports the free downward expansion of the central system to adapt to the ever-expanding park and data scale. As an example, when the edge park control system is added, the level of the edge control system can be determined and connected to the park cascade control system, for example, Figure 1 The edge park management and control system D can also be added to connect with the central park management and control system, and the edge park management and control system DA can be added under the park cascade management and control system D.

[0059] The central park management and control system directly manages the devices in the central park. These devices refer to the devices in the central park that communicate with the central park management and control system. The central park can send control instructions and other data to them, and can receive data reported by them. The devices include data acquisition devices, etc. The embodiment of the present application can set a callback processing mechanism so that the park management and control system can obtain the instruction execution status of the device in a timely manner.

[0060] The edge park management system directly manages the devices in the corresponding edge park, that is, the edge park management system can directly manage the devices that are connected to the edge park management system, and the edge park management system can send control instructions and other data to them, and can receive data reported by them. The present application can also set a callback processing mechanism in the edge park management system so that the edge park management system can obtain the instruction execution status of the device in a timely manner.

[0061] The upper-level park control system in the above-mentioned park cascade control system can send control instructions to the lower-level park control system, so as to realize the upper-level park control system's control over the lower-level park control system. In addition, the lower-level park control system can synchronize data with the upper-level park control system. The issuance of control instructions supports the vertical transmission of control instructions across systems, and the control instructions can be transmitted layer by layer to ensure the integrity and real-time performance of the data flow. For example Figure 1 When the central park control system issues instructions to the edge park control system AA, it is issued layer by layer through the edge park control system A to the edge park control system AA. When the lower-level park control system can synchronize data with the upper-level park control system, it can synchronize incrementally or fully to achieve data collaboration. Data collaboration can cover system metadata, collected data, and recorded data. Among them, metadata includes definition data; collected data includes data collected from equipment points, such as voltage and water consumption, etc.; recorded data includes data distribution records and log records.

[0062] The above-mentioned upper and lower-level park management and control systems adopt the Message Queuing Telemetry Transport (MQTT) communication protocol, and the security certificate and authentication encryption mechanism based on MQTT ensure the security of data transmission.

[0063] This application does not use a single cloud control mode, but a cascade architecture control mode of "one center and multiple bases" (one central park control system and multiple edge park control systems). It adapts to park scenarios of different sizes and types through a flexible cascade architecture, supports flexible control strategies, greatly reduces system deployment and operation and maintenance costs, and establishes an efficient and complete two-way link for data synchronization and command control. The central park control system and the edge park control system can directly manage the equipment in the corresponding park, which is conducive to data transmission and timely response; the upper-level park control system in the park cascade control system can send control instructions to the lower-level park control system, and the lower-level park control system can synchronize data with the upper-level park control system, which is conducive to efficient cascade management and data collaboration.

[0064] In one embodiment of the present application, the central park management and control system and the N edge park management and control systems all adopt a unified technical framework, and the upper-level park management and control system can synchronously view the execution results of the control instructions through a callback mechanism.

[0065] In this implementation, all park management and control systems share the same technical framework, support independent deployment on demand and backward compatibility, and achieve smooth system upgrades. The upper-level park management and control system can synchronously view the execution results of the control instructions through the callback mechanism, which is conducive to timely acquisition of corresponding strategies.

[0066] In one embodiment of the present application, the lower-level park management and control system may synchronize incremental data and full data to the upper-level park management and control system, and the full data synchronization includes:

[0067] The lower-level park management and control system divides the data to be synchronized into multiple modules according to the type;

[0068] The lower-level park management and control system divides the data of each module in the multiple modules into different batches;

[0069] The lower-level park management and control system executes an asynchronous concurrent strategy to synchronize different batches of data of each module to the upper-level park management and control system in batches;

[0070] Among them, the lower-level park management and control system records the data synchronization progress of each module during the full data synchronization process. After the synchronization of any module among the multiple modules is interrupted and restored, the last batch of successfully transmitted records before the interruption is used as the anchor point to resume the transmission from the breakpoint.

[0071] This application formulates a complete synchronization compensation strategy to ensure data consistency between multi-park management and control systems through incremental data synchronization and full data synchronization. The full data synchronization of this application adopts a modular asynchronous concurrent strategy and supports breakpoint continuation.

[0072] Asynchronous concurrency in this application means that when synchronizing the data of the above multiple modules, the data synchronization task is executed in a non-blocking manner, and there is no need to wait for the data synchronization task of the previous module to be completed before starting the next one. The data of each module is divided into multiple batches. When the full amount is synchronized, the lower-level park management and control system transmits data to the upper-level park management and control system in batches and records the progress of data synchronization, such as recording the synchronization time node.

[0073] In this application, when the module data synchronization is interrupted due to network or system failure, the lower-level park management and control system uses the last batch of successfully transmitted records before the interruption as the anchor point, reads the anchor point information after the data synchronization is restored, and continues to transmit from the position or batch marked by the anchor point to avoid repeated transmission of the successfully completed part. For example, the data in module A is divided into multiple batches for transmission: batches 1, 2, and 3 have been successfully transmitted, and the transmission of batch 4 is interrupted; the system will generate an anchor point after the transmission of batch 3 is completed, and record the data paging size and page number of batch 3 and other related information; when the transmission is resumed, the system reads the anchor point information and continues the transmission from batch 4.

[0074] The lower-level park management and control system of the present application executes an asynchronous concurrency strategy, and synchronizes different batches of data of each module to the upper-level park management and control system in batches, which is conducive to improving data synchronization efficiency; the present application records anchor points for breakpoint resumption, which allows the system to skip the successfully transmitted parts, saving time and bandwidth, and the anchor points provide clear recovery points, which can ensure the integrity and consistency of data transmission even if the network is unstable or the transmission is interrupted.

[0075] In one embodiment of the present application, after the lower-level park management and control system executes an asynchronous concurrency strategy and synchronizes different batches of data of each module to the upper-level park management and control system in batches, the lower-level park management and control system performs a data consistency check, and the data consistency check adopts a modular asynchronous check strategy, including:

[0076] The lower-level park management and control system searches for each batch of data of the first module and generates a first hash value corresponding to each batch of data, where the first module is any module among the multiple modules;

[0077] The lower-level park management and control system sends verification information to the upper-level park management and control system, wherein the verification information includes information of each batch of data;

[0078] The upper-level park management and control system queries each batch of data of the first module based on the verification information, and generates a second hash value corresponding to each batch of data.

[0079] The upper-level park management and control system sends the second hash value corresponding to each batch of data to the lower-level park management and control system;

[0080] The lower-level park management and control system verifies the first hash value and the second hash value corresponding to each batch of data. When the first hash value and the second hash value corresponding to the Mth batch of data are different, the lower-level park management and control system performs full supplementary sampling of each batch of data of the first module, where M is a positive integer.

[0081] The first hash value and the second hash value may be calculated based on the MD5 algorithm. The verification information may include data type, ID of the park management and control system, batch data paging size and page number, etc.

[0082] In this implementation, data consistency verification is helpful to ensure the consistency of synchronized data between the upper and lower systems; and, the present application adopts a modular asynchronous verification strategy to calculate the hash value for each batch of each module separately. When the hash value of the Mth batch of data of the first module in the upper system is different from the hash value of the Mth batch of data of the first module in the lower system, it is only necessary to resample the data of the first module in full, which is helpful to save resources compared to directly resample the data of all modules in full.

[0083] In one embodiment of the present application, a direct connection device and an edge gateway can be connected to the park management and control system, and the devices of the direct connection device and the edge gateway both include data acquisition devices;

[0084] The directly connected device communicates with the park management and control system via HTTP protocol or MQTT protocol;

[0085] The edge gateway communicates with the park management and control system via the OPC UA or MQTT protocol, and the park management and control system communicates with the device of the edge gateway via the edge gateway;

[0086] Among them, the park management and control system is any system among the central park management and control system and the edge park management and control system.

[0087] In the embodiment of the present application, both the direct connection device and the edge gateway device include data acquisition devices, and the park management and control system accesses the device through two methods: the direct connection device and the integrated edge gateway. Figure 2 and Figure 3 As shown, a directly connected device is Figure 2 Devices directly connected to the park management and control system, including devices directly connected to the lower-level park management and control system. The upper-level park management and control system can communicate with the lower-level system, thereby indirectly communicating with the directly connected devices of the lower-level system. Devices connected by integrated edge gateways refer to devices that communicate with the park management and control system through edge gateways.

[0088] Taking into account that directly connected devices need to support HTTP protocol or MQTT protocol, this application sets up an edge gateway. The edge gateway is adapted to common park equipment communication protocols such as Modbus, BACnet and GBT26875 city fire protection protocol, and can connect more devices, so that the park management system can establish communication with more devices, and realize the collection, conversion, storage and distribution of multi-source data. Among them, the edge gateway itself can communicate with the park management system through OPC UA or MQTT protocol, and can support functions such as gateway start and stop, channel and point synchronization, collection point control, bad point reporting and status monitoring, so as to realize comprehensive monitoring and management of edge gateways and collection controllers. As an example, if Figure 3 As shown in FIG, the edge gateway may include a kepserver, a data acquisition controller, and a visual programming and orchestration tool. Figure 3 In the park management and control system, direct-connected devices and gateway sub-devices can be created separately. The gateway sub-device must be associated with the specified edge gateway, and the collected data of the gateway sub-device is synchronized through the associated edge gateway.

[0089] The embodiments of the present application provide a "one center, multiple edges" cloud-edge collaboration solution, that is, a solution in which a park management and control system can collaborate with multiple edge gateways. Through cloud-edge collaboration, it supports multiple device communication protocols, realizes uplink and downlink bidirectional forwarding of data between the park management system and the edge gateway devices, and improves the data processing and resource scheduling efficiency of the park management system.

[0090] In one embodiment of the present application, at least one device type can be created based on the park management and control system, and each device type in the at least one device type includes the following multiple information: message protocol type, offline timeout detection information of the device, data storage period of the device, device attributes, pre-processing information of device data, and alarm events;

[0091] The park management and control system is connected to a directly connected device, including:

[0092] Binding the directly connected device to a corresponding device type in the at least one device type;

[0093] After the park management and control system is connected to the edge gateway, it also includes:

[0094] Access a gateway sub-device associated with the edge gateway, and bind the gateway sub-device to a corresponding device type in the at least one device type.

[0095] In this implementation, a device type can be created before connecting a direct-connected device and a gateway sub-device. When a device is bound to a certain device type, it inherits all the information under the device type. There is no need to define the device type for each direct-connected device and gateway sub-device separately, which is conducive to simplifying operations. For example, different electric meter A and electric meter B can be bound to the electric meter device type.

[0096] Among the above device types: message protocol types such as HTTP, MQTT or OPC UA; offline timeout detection information of the device, which can be configured or not; the data storage period of the device includes support for long-term storage of configuration data; device attributes may include any number of dynamic and static device attributes, including 16 data types such as integer, floating point, Boolean, character, coordinate, date, array, enumeration and picture; the device type can also support the division of each device attribute into read-write and read-only permissions, and support data pre-processing functions such as configuration data scaling and data type conversion (that is, configure the above data pre-processing information); the device type can also support the configuration of alarm events, and can create alarm events based on device attributes. Alarm events can be divided into alarm and warning types, and the event level can be adjusted as needed.

[0097] When creating a device in the park management and control system, if you create a direct-connected device, you can directly bind the device type associated with the direct-connected device; when creating a gateway sub-device in the park management and control system, you also need to bind the created gateway sub-device to the corresponding edge gateway. If the corresponding edge gateway has not been created, you also need to create an edge gateway in the park management and control system first. The edge gateway in the park management and control system is created based on the data acquisition gateway application, and supports access to kepserver, self-developed data acquisition controllers, and visual IoT process programming tools through OPC UA or MQTT communication protocols.

[0098] In one embodiment of the present application, the edge gateway includes a first edge gateway that communicates with the park management and control system via OPC UA, and the first edge gateway includes a kepserver and a data acquisition controller;

[0099] The park management and control system and the first edge gateway may start node synchronization, so that the park management and control system synchronizes information of the first edge gateway, including channel information, information of the first device, and location;

[0100] When the park management and control system controls the first edge gateway to start, the park management and control system synchronizes the collected data of the first device and stores it in the cache;

[0101] In the park management and control system, when the first gateway sub-device has been connected and the device attributes of the first gateway sub-device are bound to the location of the first device, when the first edge gateway and the first gateway sub-device are controlled to be turned on by the park management and control system, the park management and control system stores the collected data of the first device in the timing library.

[0102] See also Figure 4 , Figure 4 This is a flowchart of cloud-edge collaboration based on OPC UA. Figure 4 As shown, the control system, as an OPC UA client, actively initiates a connection to the OPC UA server (i.e., the first edge gateway mentioned above), supports synchronization of OPC UA channels, devices, and point information to the control system, and the control system uniformly manages the mapping relationship between device attributes and collection points. The following is a detailed description of this.

[0103] A first edge gateway can be newly established in the park management system, and the first edge gateway includes a kepserver and a data acquisition controller. In this field, kepserver and kepware usually refer to the same type of software without strict distinction. For example, Figure 3 to Figure 4 The kepware in this embodiment is also the kepsever; in essence, kepserver is a specific product under the kepware brand, which is an OPC server software.

[0104] After the first edge gateway is newly created in the park management and control system, synchronization can be enabled to synchronize the information of the first edge gateway, including channel information, information of the first device, and points (points in kepserver are also called marks). The above channel information is the information of the channel created in the first edge gateway, the first device refers to the device created under the channel in the first edge gateway, and the above point refers to the device point under the first device.

[0105] After synchronizing the information of the first edge node, a new first gateway sub-device may be created on the campus management and control system side, including binding the corresponding device type and binding the first edge gateway.

[0106] The campus management and control system can control the start and stop of the first edge gateway. When the first edge gateway is enabled, refer to Figure 4 The data synchronization process in the edge gateway can synchronize the collected data of the device (i.e. Figure 4Wherein, on the park management and control system side, when the device attribute of the first gateway sub-device is not bound to the location of the first device, after the first edge gateway is enabled, the park management and control system listens to OPC UA, and stores the latest value of the acquired device collection data into the cache; when the device attribute of the first gateway sub-device is bound to the location of the first device on the park management and control system side, the park management and control system side can correctly manage the collection data of the first device, and store the device collection data into the time series library so that its historical value can be viewed later.

[0107] The campus management and control system can send device data to the first edge gateway and view the sending results through the control callback mechanism.

[0108] In one embodiment of the present application, the edge gateway includes a visual process orchestration tool that communicates with the park management and control system via the MQTT protocol;

[0109] Through the park management and control system, information of the second gateway sub-device associated with the visual process orchestration tool can be exported;

[0110] The visual process orchestration tool is used to perform offline synchronization with the park management and control system to obtain information of the second gateway sub-device, and bind the information of the second gateway sub-device to the point of the second device in the visual process orchestration tool;

[0111] When the visual process orchestration tool and the second gateway sub-device are both turned on by the park management and control system, the park management and control system synchronizes the collected data of the second device and stores it in the timing library.

[0112] A visual process orchestration tool (such as Node-RED) is a software tool that uses a graphical interface (such as dragging components, configuring nodes, etc.) to design and manage business processes, data flows, or automated tasks. Figure 5 In the embodiment of the present application, a visual IoT process orchestration tool can be integrated through proxy forwarding. For example, a uniform resource locator (URL) of the visual process orchestration tool can be added to the park management and control system.

[0113] Given the flexibility of the visual process orchestration tool, the tool itself manages the mapping relationship between system device attributes and collection points. Figure 5As shown, specifically, the visual process orchestration tool is synchronized offline with the park management and control system to obtain the information of the second gateway sub-device. The information of the second gateway sub-device includes the device ID and the point code; on the visual process orchestration tool side, a mapping relationship between the device attributes in the management and control system and the device points in the orchestration tool is established, and the device ID and point code of the second gateway sub-device can be bound to the point of the second device. After the mapping relationship between the device attributes and the device points is established on the visual process orchestration tool side, the park management and control system can manage the synchronized collected data and store it in the time series library for subsequent viewing.

[0114] During the data distribution process, the park management and control system can distribute device data through the MQTT subscription node of the visual process orchestration tool, and can view the distribution results through the control callback mechanism.

[0115] In the embodiment of the present application, the park management and control system can integrate a visual IoT process orchestration tool through proxy forwarding. The visual IoT process orchestration tool completes the configuration of data task flows by dragging and dropping components, and can provide a user-friendly visual interface to realize edge device rule node orchestration and simplify the management and scheduling of edge devices.

[0116] In one embodiment of the present application, the edge gateway includes a data acquisition controller that communicates with the park management and control system via the MQTT protocol;

[0117] The park management and control system and the data acquisition controller can start node synchronization, so that the park management and control system synchronizes the information of the data acquisition controller, including channel information, third device information and point position;

[0118] In the park management and control system, when the third gateway sub-device has been connected and the device attributes of the third gateway sub-device are bound to the location of the third device, when the data acquisition controller and the third gateway sub-device are controlled by the park management and control system to be turned on, the park management and control system synchronizes the collected data of the third device and stores it in the timing library.

[0119] In this implementation, the data acquisition controller can also communicate with the park management and control system via the MQTT protocol. Figure 6 The park management and control system communicates through the MQTT protocol to synchronize the information of the data acquisition controller, including channel information, information of the third device, and location. A third gateway sub-device can be newly created on the park management and control system side, and the device type and data acquisition controller can be bound.

[0120] In this embodiment, the park management and control system manages the mapping relationship between the device attributes of the third gateway sub-device and the location of the third device. Figure 6As shown, during the data synchronization process, when the data acquisition controller and the third gateway sub-device are enabled and the device attributes of the third gateway sub-device are bound to the location of the third device, the park management and control system synchronizes the collected data of the third device and stores it in the timing library; when the device attributes of the third gateway sub-device are not bound to the location of the third device, they need to be bound on the park management and control system side.

[0121] During the data sending process, the park management and control system can send device data to the data acquisition controller through the MQTT protocol, and can view the sending results through the control callback mechanism.

[0122] In one embodiment of the present application, the edge gateways are each provided with a heartbeat script to periodically send a heartbeat signal and a communication address to the park management system, and the park management system updates the status of the edge gateway based on the heartbeat monitoring mechanism.

[0123] See also Figure 7 , the edge gateways are all equipped with a heartbeat script to periodically send heartbeat signals and communication addresses (such as MAC addresses) to the park management system, and the park management system updates the status of the edge gateway based on the heartbeat monitoring mechanism. Specifically, taking edge gateway A as an example, after the heartbeat response API in the park management system receives the heartbeat signal and MAC address sent by edge gateway A, it queries the edge gateway A corresponding to the MAC address by querying the edge gateway API, and updates its status in Redis.

[0124] In order to more clearly understand the technical solution of the embodiments of the present application, the present application is further illustrated below.

[0125] Step 1: Establish system cascade topology

[0126] When the control system is started, it will initialize and generate the system unique identifier, system communication address and MQTT connection configuration. Considering the scalability of the cascade architecture, each control system can be used as both the upper and lower systems. The data is reported layer by layer and summarized in the root system, that is, the central control system. Figure 1 As shown. The communication between the management and control systems adopts the MQTT communication protocol, and the security certificate and authentication encryption mechanism based on MQTT ensure the security of data transmission. The connection specifications are as follows:

[0127] Topic Agreement:

[0128] Publish to the upstream data point topic: $sys / {systemId} / dp

[0129] subscribe listens to the command topic: $sys / {systemId} / cmd

[0130] CONNECT message

[0131] clientId specification: systemcode=${systemCode}|signmethod=hmacsha1|timestamp=xxx

[0132] Among them, systemcode is the system code; signmethod can specify HmacSHA1, HmacSHA256 or HmacMD5; timestamp is (optional) timestamp. If the system code is subsystem, the signature algorithm is md5, and the timestamp is 1699318128371, then the final generated value is: systemcode = subsystem | signmethod = hmacmd5 | timestamp = 1699318128371

[0133] userName specification: ${systemId}, system unique identifier, such as: 067719b4f7f041abba49ad2b40148c50

[0134] Password specification: It is generated by concatenating the clientId and userName parameter values ​​mentioned above and combining them with the system key and encryption algorithm.

[0135] Step 1: Calculate the concatenated string in the following format: clientId = ${clientId}&userName = ${userName}

[0136] Step 2: Obtain a byte array of the first result in UTF-8 format as data, obtain a byte array of the system key systemKey in UTF-8 format as ciphertext, use the corresponding hmac algorithm to calculate the signature byte array, convert it to lowercase hexadecimal to obtain a string, and use the final string as the password.

[0137] Step 2: Create system devices and edge gateways

[0138] like Figure 2 As shown, the park management and control system proposed in the present invention supports access to collection devices through direct connection and integrated edge gateway. Before accessing the device, the system data model needs to be created through the following steps:

[0139] Create a device type. The device type needs to be bound to a message protocol such as HTTP, MQTT, or OPC UA, and supports configuration of device offline timeout detection and long-term data storage; any number of dynamic and static device attributes can be configured under each device type, including 16 data types such as integer, floating point, Boolean, character, coordinate, date, array, enumeration, and image; each device attribute is divided into read-write and read-only permissions, and supports data preprocessing functions such as data scaling and data type conversion; supports the creation of device alarm events based on device attributes, and alarm events are divided into alarm and warning types, and event levels can be adjusted as needed.

[0140] Create a device. The device needs to be bound to the device type and inherit all the information under the device type; devices can be divided into direct-connected devices and gateway sub-devices. Devices connected through edge gateways must be gateway sub-device types and must be bound to a specified edge gateway.

[0141] Create an edge gateway. The system edge gateway is created based on the data acquisition gateway application. It supports access to kepserver, self-developed data acquisition controller, and visual IoT process programming tools through OPCUA or MQTT communication protocols; it supports monitoring the running status of edge computing gateway physical devices and gateway applications respectively, and completes the status reporting of physical devices through heartbeat monitoring scripts, such as Figure 7 shown.

[0142] According to the above steps, the data model creation and cloud-edge collaborative management of the park management and control system can be completed to form a complete multi-source data collection link, such as Figure 3 shown.

[0143] Step 3: Connect to the OPC UA Edge Gateway

[0144] The park management and control system proposed in the present invention supports access to the edge gateway via the OPC UA communication protocol. Figure 4 As shown in the figure, the control system, as an OPC UA client, actively initiates connections to OPC UA servers such as kepserver and self-developed data acquisition controllers, supports synchronization of OPC UA channels, equipment, and point information to the control system, and the control system uniformly manages the mapping relationship between system equipment attributes and collection points.

[0145] Step 4: Connect to the MQTT edge gateway

[0146] The park management and control system proposed in the present invention supports access to the edge gateway through the MQTT communication protocol, including two gateway applications: a visual Internet of Things process orchestration tool and a self-developed data acquisition controller.

[0147] Visual IoT process orchestration tool

[0148] like Figure 5As shown in the figure, the control system integrates the visual IoT process orchestration tool through proxy forwarding. Given the flexibility of the visual process orchestration tool, the tool itself manages the mapping relationship between system device attributes and collection points, and sends the binding point information and collection point data to the control system through the MQTT publishing node. The control system will provide process orchestration and data conversion specification documents to assist in completing task flow configuration.

[0149] Self-developed data acquisition controller

[0150] like Figure 6 As shown, the control system is deeply integrated with the self-developed data acquisition controller. The MQTT communication specification refers to the connection specification of the upper and lower control systems in step 1. The Topic convention is:

[0151] Publish synchronization node data topic: $sys / {edgeGatewayId} / sync / dp

[0152] Publish reports bad point data topic: $sys / {edgeGatewayId} / bad / dp

[0153] Publish reported collected data topic: $sys / {edgeGatewayId} / device / dp

[0154] Publish control callback topic: $sys / {edgeGatewayId} / callback / dp

[0155] subscribe listens to synchronization node command topic: $sys / {edgeGatewayId} / sync / cmd

[0156] subscribe monitors the control collection node topic: $sys / {edgeGatewayId} / subs / cmd

[0157] subscribe listens for control command topic: $sys / {edgeGatewayId} / control / cmd

[0158] Through the joint development of the management and control system and the self-developed data acquisition controller, the system supports the synchronization of the gateway connection, acquisition equipment and equipment points of the self-developed data acquisition controller, and the management and control system uniformly manages the mapping relationship between system equipment attributes and acquisition points; supports dynamic control of data reporting of some acquisition points to avoid excessive resource cost consumption caused by reporting all acquisition point data; supports bad point detection, and the self-developed data acquisition controller regularly reports bad point data to the management and control system; supports point data reporting and command issuance, and the management and control system can synchronously view the issuance results through the control callback mechanism.

[0159] This application establishes a multi-layer cascade architecture that supports expansion, realizes efficient cascade management and data collaboration between upper and lower systems; formulates a complete synchronization compensation strategy to ensure data consistency between multi-park management and control systems; provides cloud-edge collaboration capabilities, based on the communication protocols and specifications jointly formulated by the system and edge devices, to achieve uplink and downlink bidirectional forwarding of data; provides a user-friendly visual interface to realize edge device rule node orchestration, and simplifies the management and scheduling of edge devices. The present invention can provide flexible management and control strategies, greatly reduce system deployment and operation and maintenance costs, introduce edge computing technology, and achieve efficient data processing and resource scheduling.

[0160] The flowcharts and block diagrams in the accompanying drawings illustrate the possible architecture, functions and operations of the systems, methods and computer program products according to various embodiments of the present application. Among them, each box in the flowchart or block diagram can represent a module, a program segment or a part of the code, and the above-mentioned module, program segment, or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram or flowchart, and the combination of boxes in the block diagram or flowchart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0161] The units involved in the embodiments described in this application may be implemented by software or hardware, and the units described may also be set in a processor. The names of these units do not, in some cases, constitute limitations on the units themselves.

[0162] The above embodiments are merely illustrative of the principles and effects of the present application, and are not intended to limit the present application. Anyone familiar with the technology may modify or change the above embodiments without violating the spirit and scope of the present application. Therefore, all equivalent modifications or changes made by a person of ordinary skill in the art without departing from the spirit and technical ideas disclosed in the present application shall still be covered by the claims of the present application.

Claims

1. A park cascade control system, characterized in that: include: Central park management and control system; N edge park management and control systems, wherein the N edge park management and control systems are communicatively connected with the central park management and control system step by step according to a preset hierarchical relationship, and N is a positive integer; Among them, the central park management and control system directly manages the equipment in the central park, the N edge park management and control systems directly manage the equipment in the corresponding edge parks, and the upper-level park management and control systems in the central park management and control system and the edge park management and control systems can send control instructions to the lower-level park management and control systems, and the lower-level park management and control systems can synchronize data with the upper-level park management and control systems.

2. The system according to claim 1, characterized in that The lower-level park management and control system can synchronize incremental data and full data with the upper-level park management and control system, and the full data synchronization includes: The lower-level park management and control system divides the data to be synchronized into multiple modules according to the type; The lower-level park management and control system divides the data of each module in the multiple modules into different batches; The lower-level park management and control system executes an asynchronous concurrent strategy to synchronize different batches of data of each module to the upper-level park management and control system in batches; Among them, the lower-level park management and control system records the data synchronization progress of each module during the full data synchronization process. After the synchronization of any module among the multiple modules is interrupted and restored, the last batch of successfully transmitted records before the interruption is used as the anchor point to resume the transmission from the breakpoint.

3. The system according to claim 2, characterized in that After the lower-level park management and control system executes the asynchronous concurrency strategy and synchronizes different batches of data of each module to the upper-level park management and control system in batches, the lower-level park management and control system executes data consistency verification, and the data consistency verification adopts a modular asynchronous verification strategy, including: The lower-level park management and control system searches for each batch of data of the first module and generates a first hash value corresponding to each batch of data, where the first module is any module among the multiple modules; The lower-level park management and control system sends verification information to the upper-level park management and control system, wherein the verification information includes information of each batch of data; The upper-level park management and control system queries each batch of data of the first module based on the verification information, and generates a second hash value corresponding to each batch of data. The upper-level park management and control system sends the second hash value corresponding to each batch of data to the lower-level park management and control system; The lower-level park management and control system verifies the first hash value and the second hash value corresponding to each batch of data. When the first hash value and the second hash value corresponding to the Mth batch of data are different, the lower-level park management and control system performs full supplementary sampling of each batch of data of the first module, where M is a positive integer.

4. The system according to claim 1, characterized in that The park management and control system can be connected to a direct-connect device and an edge gateway, and the devices of the direct-connect device and the edge gateway both include data acquisition devices; The directly connected device communicates with the park management and control system via HTTP protocol or MQTT protocol; The edge gateway communicates with the park management and control system via the OPC UA or MQTT protocol, and the park management and control system communicates with the device of the edge gateway via the edge gateway; Among them, the park management and control system is any system among the central park management and control system and the edge park management and control system.

5. The system according to claim 4, characterized in that At least one device type can be created based on the park management and control system, and each device type in the at least one device type includes the following information: message protocol type, offline timeout detection information of the device, data storage cycle of the device, device attributes, pre-processing information of device data, and alarm events; The park management and control system is connected to a directly connected device, including: Binding the directly connected device to a corresponding device type in the at least one device type; After the park management and control system is connected to the edge gateway, it also includes: Access a gateway sub-device associated with the edge gateway, and bind the gateway sub-device to a corresponding device type in the at least one device type.

6. The system according to claim 4 or 5, characterized in that: The edge gateway includes a first edge gateway that communicates with the park management and control system via OPC UA, and the first edge gateway includes a kepserver and a data acquisition controller; The park management and control system and the first edge gateway may start node synchronization, so that the park management and control system synchronizes information of the first edge gateway, including channel information, information of the first device, and location; When the park management and control system controls the first edge gateway to start, the park management and control system synchronizes the collected data of the first device and stores it in the cache; In the park management and control system, when the first gateway sub-device has been connected and the device attributes of the first gateway sub-device are bound to the location of the first device, when the first edge gateway and the first gateway sub-device are controlled to be turned on by the park management and control system, the park management and control system synchronizes the collected data of the first device and stores it in the timing library.

7. The system according to claim 4 or 5, characterized in that: The edge gateway includes a visual process orchestration tool that communicates with the park management and control system via the MQTT protocol; Through the park management and control system, information of the second gateway sub-device associated with the visual process orchestration tool can be exported; The visual process orchestration tool is used to perform offline synchronization with the park management and control system to obtain information of the second gateway sub-device, and bind the information of the second gateway sub-device to the point of the second device in the visual process orchestration tool; When the visual process orchestration tool and the second gateway sub-device are both turned on by the park management and control system, the park management and control system synchronizes the collected data of the second device and stores it in the timing library.

8. The system according to claim 4 or 5, characterized in that: The edge gateway includes a data acquisition controller that communicates with the park management and control system via the MQTT protocol; The park management and control system and the data acquisition controller can start node synchronization, so that the park management and control system synchronizes the information of the data acquisition controller, including channel information, information of the third device and point position; In the park management and control system, when the third gateway sub-device has been connected and the device attributes of the third gateway sub-device are bound to the location of the third device, when the data acquisition controller and the third gateway sub-device are controlled by the park management and control system to be turned on, the park management and control system synchronizes the collected data of the third device and stores it in the timing library.

9. The system according to claim 4 or 5, characterized in that: The edge gateways are all provided with a heartbeat script to periodically send a heartbeat signal and a communication address to the park management system. The park management system updates the status of the edge gateway based on the heartbeat monitoring mechanism.

10. The system according to claim 1, characterized in that The central park management and control system and the N edge park management and control systems all adopt a unified technical framework, and the upper-level park management and control system can synchronously view the execution results of the control instructions through a callback mechanism.

Images