Industrial device edge management and control system and method supporting parallel access of multiple types of devices

Abstract

The present application relates to the technical field of industrial automation and industrial internet, and particularly relates to an industrial equipment edge management and control system and method supporting parallel access of multiple types of equipment, comprising: at least one edge management and control domain, each edge management and control domain comprising an equipment layer and an intermediate access service layer; at least one centralized management and control layer configured to simultaneously establish a communication connection with at least two edge management and control domains; wherein the channel type comprises a management and control channel and a monitoring channel. The present application aims to overcome the shortcomings of the prior art and provide an industrial equipment edge management and control system and method supporting parallel access of multiple types of equipment, which, through a cross-domain connection channel type solidification mechanism, enables the same centralized management and control layer to independently establish a management and control channel or a monitoring channel for different edge management and control domains, thereby realizing flexible hierarchical cooperation and protocol layer security isolation.

Description

Technical Field

[0001] This invention relates to the fields of industrial automation and industrial internet technology, specifically to an industrial equipment edge management system and method that supports parallel access of multiple types of devices. Background Technology

[0002] In the industrial manufacturing sector, especially in the production and testing stages of power batteries and energy storage batteries, a large number of intermediate equipment such as formation and capacity testing cabinets and charge / discharge testing equipment are typically required. Effective management and control of these devices is crucial to ensuring production quality and efficiency.

[0003] Currently, the industry commonly uses a tightly coupled integrated architecture with a direct connection between the host computer and the intermediate computer. This architecture has the following inherent drawbacks:

[0004] 1. Existing host computer programs are usually statically bound to specific device types during the compilation or startup phase. The system only loads the driver, protocol parsing module and human-machine interface corresponding to the single type. In actual production, users often need to manage multiple devices with different power, functions and protocols at the same time. The existing architecture cannot meet this requirement and requires the deployment of independent PC hardware and software systems for each device type, which leads to a significant increase in hardware costs, deployment complexity and operation and maintenance burden.

[0005] 2. Because the host computer and the intermediate computer communicate directly, the business logic, communication protocol and device driver are highly coupled. When a new model of device needs to be connected or a new function needs to be added, the core program of the host computer must be modified a lot or even redesigned. The development cycle is long, the testing cost is high, the upgrade risk is high, and it cannot flexibly respond to rapidly changing production needs.

[0006] 3. The existing system is designed with only one field control mode. Any access to the system has complete control permissions. When the monitoring center needs to view the production data globally, or when equipment after-sales personnel need to remotely access the system to diagnose problems, the operation interface is no different from the field operator interface. This poses a significant risk of accidentally triggering control commands and interfering with the normal production process, forcing monitoring and debugging work to either be impossible or have to be done at the expense of production stability.

[0007] In view of this, there is an urgent need for a new technical solution to address the three core issues of unified access for multiple types of devices, flexible system expansion, and secure and interference-free monitoring. Summary of the Invention

[0008] This invention aims to overcome the shortcomings of the prior art and provide an industrial equipment edge control system and method that supports parallel access of multiple types of devices. Through a cross-domain connection channel type solidification mechanism, the same centralized control layer can independently establish control channels or monitoring channels for different edge control domains, thereby achieving flexible hierarchical collaboration and protocol layer security isolation.

[0009] To achieve the aforementioned objectives, this invention provides, in one aspect, an industrial equipment edge management system that supports parallel access by multiple types of devices, comprising:

[0010] At least one edge control domain, each edge control domain including a device layer and an intermediate access service layer, wherein the intermediate access service layer is equipped with an edge full database for persistently storing the full amount of operational data generated by its corresponding device layer;

[0011] At least one centralized control layer is configured to simultaneously establish communication connections with at least two of the edge control domains and independently perform bidirectional channel authentication with each edge control domain to negotiate and determine the channel type for this connection;

[0012] The channel types include control channels and monitoring channels;

[0013] When a control channel is established between the centralized control layer and a target edge control domain, the channel is registered with a downlink instruction frame parser and a control instruction writing interface at the protocol stack level, supporting bidirectional data synchronization and instruction issuance;

[0014] When a monitoring channel is established between the centralized control layer and a target edge control domain, the channel does not register a downlink instruction frame parser at the protocol stack level, so that the communication link does not have a handle for receiving or forwarding control instructions in its structure, and only supports one-way data push and query response from the edge to the center.

[0015] Preferably, the device layer in the edge control domain includes various industrial devices with different device type identifiers; the intermediate access service layer of the edge control domain is deployed at the device site to connect to and manage the devices in the device layer.

[0016] Preferably, the centralized management and control layer pre-registers device type description files corresponding to all device type identifiers, forming a device type resource library. The centralized management and control layer is configured to dynamically load the device type description file corresponding to the device type identifier from the pre-registered device type resource library when it receives a device type identifier reported from the intermediate access service layer, and instantiate an isolated driver runtime context for the device type. The driver runtime context includes an independent register address mapping table, a protocol parser state machine, and a UI component sandbox to provide parallel management and control of multiple types of devices in the same management and control interface, while avoiding address space conflicts and protocol stack preemption of driver resources of different device types.

[0017] Preferably, when the centralized control layer connects to the first edge control domain via a control channel and to the second edge control domain via a monitoring channel, it automatically adapts and switches between the control interface corresponding to the device type in the first edge control domain and the monitoring interface corresponding to the device type in the second edge control domain through a dynamic loading mechanism, without needing to deploy independent user interface systems for different channels.

[0018] Preferably, when the centralized management and control layer connects to the edge management and control domain via a monitoring channel, the data synchronization from the edge management and control domain is performed on-demand, incremental data extraction and aggregation; the edge full database is configured with a data sovereignty protocol module, which is used to perform signature verification, permission verification and audit records on the data query requests of the centralized management and control layer, and embed digital watermarks on the returned data; the centralized management and control layer does not persistently store a full copy of the data of the connected edge management and control domain.

[0019] Preferably, the intermediate access service layer further includes a standard extension interface for accessing newly added functional service modules in a sandboxed plug-in manner. The newly added functional service modules obtain data and process it by subscribing to the data bus inside the intermediate access service layer through a read-only image. The processing result is digitally signed and published through the data bus to prevent malicious plug-ins from tampering with the device control path.

[0020] Preferably, the intermediate access service layer further includes a permission verification module; the permission verification module is configured to: in response to an authorization debugging request initiated by the centralized management and control layer accessing through the monitoring channel, after a preset approval process, issue a temporary scope token to the centralized management and control layer, enabling the monitoring channel to obtain limited control permissions for a specific device within the token's validity period. After the token expires, the permissions are automatically revoked, and the protocol stack of the monitoring channel temporarily registers the corresponding downlink instruction frame parser within the token's validity period.

[0021] Based on the aforementioned industrial equipment edge control system, this invention also provides an industrial equipment control method, comprising:

[0022] S100, each edge control domain operates independently and continuously stores all operational data generated at its device layer in the local edge full database;

[0023] S200: The centralized control layer initiates a connection to at least one edge control domain and independently performs bidirectional channel authentication with each edge control domain, negotiating and establishing the channel type for this connection, wherein the channel type is a control channel or a monitoring channel.

[0024] S300. The centralized control layer executes differentiated data synchronization strategies and device control permissions according to the channel type established with each edge control domain: for the control channel, it executes bidirectional interaction of instruction issuance and data return; for the monitoring channel, it only executes data query and subscription from the edge control domain to the centralized control layer, and blocks any control instruction frames flowing to the edge control domain at the protocol stack level.

[0025] S400. In response to the channel switching request initiated by the centralized control layer, the target edge control domain approves the request. After approval, it renegotiates the channel type for connection and synchronously updates the instruction frame parser registration status, data synchronization strategy, and permission strategy at the protocol stack level.

[0026] Preferably, step S200 includes:

[0027] S210. When a new device is connected in the device layer of the edge control domain, the intermediate access service layer of the edge control domain identifies its device type identifier and reports it to the centralized control layer.

[0028] S220. The centralized control layer matches the corresponding equipment type description file from the equipment type resource library based on the equipment type identifier;

[0029] S230. Based on the device type description file, dynamically instantiate the corresponding device driver object and create an isolated driver runtime context for the device type; and dynamically load the differentiated operation view and function set associated with the device type and inject them into the unified management interface to provide parallel management of multiple types of devices in the same management interface of the centralized management layer.

[0030] Preferably, in step S300, the edge control domain performs bidirectional data synchronization with the centralized control layer through asynchronous communication, performs local caching when the network is interrupted, and performs breakpoint resume transmission after the network is restored.

[0031] In another aspect, the present invention provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the above-described industrial equipment control method.

[0032] The present invention, through the above-described solution, brings the following significant beneficial effects:

[0033] The monitoring channel of this invention does not register a downlink instruction frame parser at the protocol stack level, so that the communication link of the connection does not have a handle for receiving or forwarding control instructions in its structure. Even if the application layer is bypassed or the connection is hijacked, the monitoring channel cannot construct a legitimate control message that can be accepted by the edge domain, fundamentally eliminating the possibility of the monitoring channel being used to issue control instructions, and realizing hard isolation between the control plane and the monitoring plane at the protocol stack level.

[0034] By instantiating an independent driver runtime context for each device type, the technical problem of register address space conflicts and protocol stack preemption occurring in the same process space for different device type drivers in traditional architectures is solved. For the first time, a single system can achieve parallel access and unified management of multiple types of heterogeneous devices, and realize the isolated coexistence of runtime contexts for multiple types of device drivers.

[0035] The data sovereignty protocol module configured in the edge full database ensures that when the center accesses through the monitoring channel, it can only perform on-demand queries through a limited API and cannot obtain a full copy of the data. This technically guarantees the data sovereignty and security compliance of each production unit and realizes the protocol-based protection of edge data sovereignty.

[0036] The temporary scope token mechanism allows the monitoring channel to temporarily register a downlink command frame parser within a time window after authorization, which not only meets the flexible needs of remote debugging, but also ensures security through the automatic token expiration mechanism. Attached Figure Description

[0037] Figure 1 This is a connection block diagram of the industrial equipment edge control system according to an embodiment of the present invention;

[0038] Figure 2 This is a flowchart of the industrial equipment edge control method according to an embodiment of the present invention;

[0039] Figure 3 This is a flowchart of step S200 in the industrial equipment edge control system of this embodiment of the invention;

[0040] Figure 4 This is a flowchart of step S300 in the industrial equipment edge control system of this embodiment of the invention.

[0041] In the diagram: 100, Centralized Management and Control Layer; 200, Edge Management and Control Domain; 210, Intermediate Access Service Layer; 211, Synchronization Service Module; 212, MQTT Communication Module; 213, Edge Full Database; 214, Standard Extension Interface; 220, Device Layer. Detailed Implementation

[0042] The technical solutions of this invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described invention is only a part of the invention, not all of the invention. All other inventions obtained by those skilled in the art based on the invention without creative effort are within the scope of protection of this invention.

[0043] In the description of this invention, it should be noted that the terms "upper," "lower," "inner," "outer," "top / bottom," etc., indicate the orientation or positional relationship based on the orientation or positional relationship shown in the accompanying drawings. They are used only for the convenience of describing the invention and for simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, or be constructed and operated in a specific orientation. Therefore, they should not be construed as limitations on the invention. Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance.

[0044] In the description of this invention, it should be noted that, unless otherwise explicitly specified and limited, the terms "installed," "equipped with," "sleeved / connected," "connected," etc., should be interpreted broadly. For example, "connection" can be a fixed connection, a detachable connection, or an integral connection; it can be a mechanical connection or an electrical connection; it can be a direct connection or an indirect connection through an intermediate medium; it can be a connection within two components. Those skilled in the art can understand the specific meaning of the above terms in this invention based on the specific circumstances.

[0045] Currently, the industry commonly adopts a tightly coupled integrated architecture where the host computer and the intermediate computer are directly connected. This architecture has the following inherent drawbacks: existing host computer programs are usually statically bound to specific device types during the compilation or startup phase, requiring the deployment of independent PC hardware and software systems for each device type, which leads to a significant increase in hardware costs, deployment complexity, and maintenance burden; due to the direct communication between the host computer and the intermediate computer, business logic, communication protocols, and device drivers are highly coupled, resulting in long development cycles, high testing costs, and high upgrade risks, making it impossible to flexibly respond to rapidly changing production needs; any access to the system has complete control permissions, posing a significant risk of accidentally triggering control commands and interfering with normal production processes.

[0046] like Figure 1 As shown, in response to the technical problems existing in the current mainstream solutions, this embodiment proposes an industrial equipment edge control system that supports parallel access and unified management of multiple types of devices. Through a cross-system channel binding mechanism, the same centralized control layer can independently configure control terminals or monitoring channels for different edge control domains, realizing flexible hierarchical collaboration. It also protects edge data sovereignty by ensuring the data security and autonomous controllability of each production unit through the edge full database and data sovereignty protocol.

[0047] like Figure 1 As shown, in order to achieve the above-mentioned objectives, this embodiment provides an industrial equipment edge control system, which adopts a layered decoupling design and includes at least one edge control domain 200 and at least one centralized control layer 100 from bottom to top. The centralized control layer 100 is a logical entity, and the edge control domain 200 includes a device layer 220 and an intermediate access service layer 210. Each device layer 220 and the intermediate access service layer 210 constitute a logically autonomous whole.

[0048] Specifically, it is described as follows:

[0049] In the edge control domain 200, the device layer 220 includes various industrial devices with different device type identifiers, which generate data including full operation data, time logs, and process parameters. Specifically, the industrial devices can be multiple mid-level machines of different power types and project types. These mid-level machines have different type identifiers such as power level and customized version, and are connected to the intermediate access service layer 210 through fieldbuses such as industrial Ethernet and CAN.

[0050] The intermediate access service layer 210 in the edge control domain 200 is physically and logically decoupled from the device layer 220 and the centralized control layer 100. It is deployed at the device site and connects between the device layer 220 and the centralized control layer 100. The intermediate access service layer 210 is directly connected to the device layer 220 and communicates with all the intermediate machines in the device layer 220 via the MQTT protocol.

[0051] The intermediate access service layer 210 specifically includes a synchronization service module 211, an MQTT communication module 212, and an edge full database 213, while reserving a standard extension interface 214.

[0052] The synchronization service module 211 forwards instructions issued by the centralized management layer 100 to the MQTT communication module 212 on the one hand, and completes bidirectional data synchronization between the edge full database 213 and the centralized management layer 100 on the other hand, realizing data pass-through between the upper and lower layers, replacing the original direct connection communication logic, and achieving decoupling.

[0053] The MQTT communication module 212 connects to multiple mid-level machines in the device layer 220 based on the MQTT publish-subscribe mechanism, supports parallel data transmission of multiple devices, meets the requirement of simultaneous access of multiple mid-level machines, and realizes the breakpoint-resume bidirectional synchronization between the centralized management layer 100 and the edge full database 213.

[0054] The edge full database 213 caches uplink device data uploaded by device layer 220 and downlink commands issued by centralized management layer 100. When the upper and lower layer links are abnormal, the intermediate access service layer 210 continues to perform data acquisition and device control tasks normally. The full running data of device layer 220 is continuously cached in edge full database 213. After the link is restored, the synchronization service module 211 immediately queries the edge full database 213 for data whose timestamps were not synchronized during the network outage and automatically transmits the cached data to the global database of the management center to ensure the continuity and integrity of the data curve. Specifically, an embedded database can be used to cache the raw data collected from the device, the control commands to be issued, and metadata in real time. When the connection with the upper layer network is interrupted, local caching continues to ensure that the data is not lost.

[0055] The reserved standard extension interface 214 is used to access new functional service modules in a plug-in or microservice manner. The functional service modules obtain information by subscribing to the internal data bus of the intermediate access service layer 210, and then publish the processing results back to the bus. New functions do not need to be modified in the core architecture of the upper and lower layers, thus achieving flexible expansion.

[0056] The communication between the intermediate access service layer 210 and the device layer 220 is not limited to the MQTT communication module 212. It can be replaced with Modbus-RTU / TCP, OPCUA, CoAP, WebSocket or private TCP protocol according to the device capabilities. The protocol adaptation module of the intermediate access service layer 210 is pluggable, and the protocol replacement does not affect the overall architecture.

[0057] It is important to note that the edge full database 213 of the intermediate access service layer 210 is used to cache the uplink device data uploaded by the device layer 220. The data generated by the device layer 220 will be persistently stored in the edge full database 213 of the intermediate access service layer 210. The intermediate access service layer 210, as the sole authoritative storage and manager of the data of the device layer 220, has data sovereignty, and each intermediate access service layer 210 of the edge control domain 200 independently and completely retains all its own data.

[0058] The centralized control layer 100 is configured to simultaneously establish communication connections with at least one edge control domain 200, and independently perform bidirectional channel authentication with each edge control domain 200 to negotiate and determine the channel type for this connection. The channel types include control channels and monitoring channels. The centralized control layer 100 can simultaneously access and serve multiple different edge control domains 200, which means it can simultaneously access and serve multiple different intermediate access service layers 210.

[0059] The device layer 220, intermediate access service layer 210 and centralized management and control layer 100 are deployed in a three-layer separate manner to maximize scalability and reliability. The centralized management and control layer 100 and the intermediate access service layer 210 are physically separated and deployed on different computing devices, that is, a layered deployment across physical devices is adopted. However, for small-scale scenarios, the centralized management and control layer 100 and the intermediate access service layer 210 can be combined and deployed on the same high-performance industrial PC, which can still realize the core functions of multiple access types and dual modes.

[0060] In the connection channels of the centralized control layer 100, for each edge control domain 200 connected to it, the centralized control layer 100 is configured to have an independent connection channel, which is a control channel or a monitoring channel.

[0061] When the centralized control layer 100 connects to a target edge control domain 200 via a control channel, it registers a downlink instruction frame parser and a control instruction writing interface at the protocol stack level. The centralized control layer 100 has complete business control permissions over the edge control domain 200, performs bidirectional data synchronization with the target edge control domain 200, and has the authority to issue control instructions to the device layer 220 of the target edge control domain 200, including issuing control instructions, modifying process formulas, and managing equipment tasks. During bidirectional data synchronization, all operational data of the device layer 220 is saved to the edge full database 213 of the intermediate access service layer 210 and can optionally be synchronized back to the centralized control layer 100. This mode can be applied to the operation of the intermediate access service layer 210 deployed in the field, which is responsible for processing the business processes of the device layer 220, executing control instructions, and undertaking the actual control functions of the field equipment. It serves as the business command center of the edge control domain 200.

[0062] When the centralized management layer 100 connects to a target edge management domain 200 via a monitoring channel, no downlink command frame parser is registered at the protocol stack level. The communication link being connected does not structurally possess handles for receiving or forwarding control commands. The channel only supports unidirectional data push and query response from the edge to the center; the centralized management layer 100 cannot issue any control commands to the device layer 220. The centralized management layer 100 only has data monitoring permissions for the edge domain. It performs unidirectional data synchronization from the edge to the center with the target edge management domain 200. Data synchronization from the edge management domain 200 is on-demand, incremental data extraction and aggregation. The centralized management layer 100 only subscribes to or pulls the required monitoring data from the edge full database 213, does not persistently store the synchronized data of the connected edge management domain 200, and is prohibited from issuing control commands to the device layer 220 of the target edge management domain 200. This completely avoids interfering with on-site operations while meeting monitoring and debugging requirements. When a global overview of the operation of device layer 220 is required or after-sales debugging is needed, a monitoring channel can be granted to the remote monitoring center, large screen dashboard, or after-sales debugging mobile terminal. The mode only pulls synchronous operation data, does not issue control commands, does not modify edge business processes, and will not interfere with the normal operation of on-site equipment, thus meeting the monitoring and debugging needs while ensuring business stability.

[0063] In response to access channel requests from the centralized control layer 100, the intermediate access service layer 210 also includes a permission verification module. The permission verification module is configured to: in response to an authorization debugging request initiated by the centralized control layer 100 accessing via a control channel, after a preset approval process, issue a temporary scope token to the centralized control layer, granting the monitoring channel limited control permissions for a specific device within the token's validity period. Upon token expiration, the permissions are automatically revoked, and the monitoring channel's protocol stack temporarily registers the corresponding downlink command frame parser within the token's validity period.

[0064] For example, when the centralized control layer 100 needs to access a certain edge control domain 200, it initiates an authentication request to the intermediate access service layer 210 of the edge control domain 200, declaring the access channel type requested. The permission verification module of the intermediate access service layer 210 performs verification according to preset security policies, such as IP whitelists, digital certificates, and authorization codes. After successful verification, the two parties establish a connection and solidify this channel throughout the connection. Under monitoring channel verification, this mechanism achieves physical isolation between the monitoring flow and the control flow at the software level, ensuring interference-free monitoring. The same centralized control layer 100 can simultaneously bind a control channel to the first edge control domain and a monitoring channel to the second edge control domain.

[0065] Furthermore, in order to achieve the management and monitoring of multiple types of devices, the technical solution provided in this embodiment abandons the logic of binding a single type at startup in the existing technology. In this embodiment, the centralized management layer 100 is pre-registered with device type description files corresponding to all device type identifiers, including differentiated operation views and function sets, service classes, protocol parsing modules, management views, etc., supporting all device types, providing a unified management interface, and forming a device type resource library, so there is no need to bind a single device type at startup.

[0066] When a new device is connected, the device layer 220 sends a registration message to the intermediate access service layer 210, which includes the device serial number and model code. The intermediate access service layer 210 identifies the device type identifier and reports it to the centralized management and control layer 100. The centralized management and control layer 100 matches the corresponding device type description file from the pre-registered device type resource library according to the device type identifier. Based on the device type description file, it dynamically instantiates the corresponding device driver object and creates an isolated driver runtime context for the device type, which includes an independent register address mapping table, a protocol parser state machine, and a UI component sandbox. It dynamically loads the differentiated operation views and function sets associated with the device type and injects them into the unified management and control interface.

[0067] Through the above mechanism, drivers of different device types have their own independent runtime contexts within the same process space, and there will be no register address space conflicts or protocol stack preemption, thus realizing the parallel access and unified management of multiple types of heterogeneous devices in a single system.

[0068] In addition to the pre-registration mentioned above, for scenarios where the centralized management layer 100 has low hardware configuration or the device layer 220 has large resources, a cloud loading strategy can be adopted. The device type resource package is stored in the cloud. After receiving a new device type report, the centralized management layer 100 dynamically downloads and decompresses the corresponding resource package from the cloud and then loads it, thereby reducing the memory occupation of the centralized management layer 100 when it starts up. This method only adjusts the loading timing and can still achieve the effect of parallel access of multiple types of devices.

[0069] In actual operation, the centralized control layer 100 can simultaneously connect to the first edge control domain via a control channel and to the second edge control domain via a monitoring channel. The two channel types coexist in the same system without interfering with each other. Through a dynamic loading mechanism, the control interface corresponding to the device type in the first edge control domain and the monitoring interface corresponding to the device type in the second edge control domain automatically adapt and switch, eliminating the need to deploy independent user interface systems for different channels.

[0070] like Figure 2 As shown, based on the above-mentioned industrial equipment edge control system, this embodiment also provides an industrial equipment control method, including:

[0071] S100 and each edge control domain 200 operate independently and continuously store all operational data generated by their device layer 220 in the local edge full database 213.

[0072] S200, the centralized control layer 100 initiates a connection to at least one edge control domain 200, and independently performs two-way authentication with each edge control domain 200 to negotiate and establish the channel type of this connection, which is a control channel or a monitoring channel; the two-way authentication process outputs a channel capability descriptor, which is fixed during the connection lifecycle. The descriptor of the control channel contains the downlink command frame parser entry address, and the entry address field in the descriptor of the monitoring channel is empty.

[0073] like Figure 3 As shown, step S200 includes:

[0074] S210. When a new device is connected in the device layer 220 of the edge control domain 200, the intermediate access service layer 210 of the edge control domain 200 identifies its device type identifier and reports it to the centralized control layer 100.

[0075] S220, the centralized control layer 100 matches the corresponding equipment type description file from the equipment type resource library based on the equipment type identifier;

[0076] S230. Based on the device type description file, dynamically instantiate the corresponding device driver object; and dynamically load the differentiated operation view and function set associated with the device type, and inject them into the unified management interface, so as to provide parallel management and control of multiple types of devices in the same management interface of the centralized management layer 100.

[0077] S300 and the centralized control layer 100 execute differentiated data synchronization strategies and device control permissions based on the channels bound to each edge control domain 200, thereby enabling control or monitoring of different edge control domains 200.

[0078] like Figure 4 As shown, step S300 includes:

[0079] S310. For the edge control domain 200 connected by the control channel, perform bidirectional interaction between instruction issuance and data return; the edge control domain 200 performs bidirectional data synchronization with the centralized control layer 100 through asynchronous communication, and performs local caching when the network is interrupted, and performs breakpoint resume transmission after the network is restored.

[0080] S320. For the edge control domain 200 connected by the monitoring channel, only data query and subscription from the edge control domain 200 to the centralized control layer 100 are executed, and any control commands flowing to the edge control domain 200 are blocked.

[0081] S400: In response to the channel switching request initiated by the centralized control layer 100, the target edge control domain 200 approves the request. After approval, it dynamically switches the connection channel of the centralized control layer 100 within the lifecycle of the current connection and updates the data synchronization policy and permission policy simultaneously.

[0082] This embodiment also provides a computer-readable storage medium storing a computer program thereon, which, when executed by a processor, implements the above-described industrial equipment control method.

[0083] The following are some application scenarios of the industrial equipment edge control system and method provided in this embodiment:

[0084] Scene 1:

[0085] A factory introduced a new type of testing cabinet. The development team wrote a protocol parsing dynamic library, device driver class, front-end UI component package and device type description file for the new equipment. Through the upload interface of the centralized management layer, the equipment was registered to the device type resource library without restarting any running services.

[0086] When the first new test cabinet is powered on, the dynamic loading process is automatically triggered, and it is instantly recognized and managed by the system. The information and test data of the new test cabinet can then be displayed at the centralized control layer.

[0087] Scene 2:

[0088] In the edge control domain of a factory, in addition to controlling the device layer within the edge control domain, monitoring of the device layer is added. The first centralized control layer connects to the intermediate access service layer of the edge control domain via a control channel to obtain all control and data transmission permissions for the device layer. The technical team, carrying a second centralized control layer, sends an access request to the intermediate access service layer via a monitoring channel. Upon receiving the request, the administrator at the first centralized control layer approves the access.

[0089] It works well. In a factory's edge control domain, there are two centralized control layers connected to the intermediate access service layer of the edge control domain via control channels and monitoring channels, respectively, simultaneously controlling and monitoring the equipment layer. The second centralized control layer is connected to the field edge control domain via a monitoring channel. When the technical team needs to temporarily upgrade the monitoring channel of the second centralized control layer to a control channel to perform debugging operations on the production line, they initiate a channel switching request on the interface of the second centralized control layer, switching from the current monitoring end to the control end. The intermediate access service layer of the field edge control domain receives the request and sends an approval notification to the first centralized control layer on-site, which is connected via a control channel. The on-site administrator reviews the request in the first centralized control layer, confirms the necessity of debugging, and approves it. Once approved, the connection channel between the second centralized control layer and the field edge control domain dynamically switches to the control end. The technical team gains limited control authority and can issue debugging instructions. After the time limit expires, the channel automatically switches back to the monitoring end, and the control authority is revoked.

[0090] Scene 3:

[0091] One day, the network between the workshop and the information center experienced a temporary outage.

[0092] During the network outage: The intermediate access service layer detects that the connection with the centralized management and control layer has been lost. The intermediate access service layer continues to perform data acquisition and device control tasks normally. All voltage, current and temperature data read from the device layer, as well as the command logs issued locally, are completely recorded in the edge full database of the intermediate access service layer.

[0093] Network recovery: The synchronization service module of the intermediate access service layer detects network recovery, immediately starts the data synchronization coroutine, queries the data with timestamps during the network outage in the edge full database, packages them into batches, and uploads them to the centralized management and control layer via MQTT.

[0094] In summary, the technical solution provided in this embodiment enables unified centralized management and remote monitoring of multiple types of heterogeneous equipment without interfering with the normal operation of on-site equipment, and improves the scalability and data reliability of the system. While ensuring the data sovereignty and business independence of each production unit, it allows a centralized management node to dynamically adapt to dual channels of the management end and the monitoring end, realizing hierarchical, peer-to-peer collaboration and interference-free global monitoring of multiple edge systems, thereby supporting more complex group-based and multi-workshop production management scenarios.

[0095] The above description is only a preferred embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any equivalent substitutions or modifications made by those skilled in the art within the scope of the technology disclosed in the present invention, based on the technical solution and inventive concept of the present invention, should be covered within the scope of protection of the present invention.

Claims

1. An industrial equipment edge control system supporting parallel access of multiple types of devices, characterized in that: include: At least one edge control domain, each edge control domain including a device layer and an intermediate access service layer, wherein the intermediate access service layer is equipped with an edge full database for persistently storing the full amount of operational data generated by its corresponding device layer; At least one centralized control layer is configured to simultaneously establish communication connections with at least two of the edge control domains and independently perform bidirectional channel authentication with each edge control domain to negotiate and determine the channel type for this connection; The channel types include control channels and monitoring channels; When a control channel is established between the centralized control layer and a target edge control domain, the channel is registered with a downlink instruction frame parser and a control instruction writing interface at the protocol stack level, supporting bidirectional data synchronization and instruction issuance; When a monitoring channel is established between the centralized control layer and a target edge control domain, the channel does not register a downlink instruction frame parser at the protocol stack level, so that the communication link does not have a handle for receiving or forwarding control instructions in its structure, and only supports one-way data push and query response from the edge to the center.

2. The industrial equipment edge control system according to claim 1, characterized in that: The device layer in the edge control domain includes various industrial devices with different device type identifiers; the intermediate access service layer of the edge control domain is deployed at the device site to connect to and manage the devices in the device layer.

3. The industrial equipment edge control system according to claim 2, characterized in that: The centralized management and control layer pre-registers device type description files corresponding to all device type identifiers, forming a device type resource library. The centralized management and control layer is configured to dynamically load the device type description file corresponding to the device type identifier from the pre-registered device type resource library when it receives a device type identifier reported from the intermediate access service layer, and instantiate an isolated driver runtime context for the device type. The driver runtime context includes an independent register address mapping table, a protocol parser state machine, and a UI component sandbox to provide parallel management and control of multiple types of devices in the same management and control interface, while avoiding address space conflicts and protocol stack preemption of driver resources of different device types.

4. The industrial equipment edge control system according to claim 3, characterized in that: When the centralized management and control layer connects to the first edge management and control domain via a management and control channel and to the second edge management and control domain via a monitoring channel, it automatically adapts and switches between the management and control interface corresponding to the device type in the first edge management and control domain and the monitoring interface corresponding to the device type in the second edge management and control domain through a dynamic loading mechanism, without the need to deploy independent user interface systems for different channel types.

5. The industrial equipment edge control system according to claim 1, characterized in that: When the centralized control layer connects to the edge control domain via a monitoring channel, the data synchronization from the edge control domain is an on-demand, incremental data extraction and aggregation. The edge full database is configured with a data sovereignty protocol module, which is used to perform signature verification, permission verification and audit records on the data query requests of the centralized management layer, and embed digital watermarks on the returned data; the centralized management layer does not persistently store full data copies of the connected edge management domain.

6. The industrial equipment edge control system according to claim 1, characterized in that: The intermediate access service layer also includes a standard extension interface for accessing new functional service modules in a sandboxed plug-in manner. The new functional service modules obtain data and process it by subscribing to the data bus inside the intermediate access service layer through a read-only image. The processing results are digitally signed and published through the data bus to prevent malicious plug-ins from tampering with the device control path.

7. The industrial equipment edge control system according to claim 6, characterized in that: The intermediate access service layer also includes a permission verification module; the permission verification module is configured to: in response to an authorization debugging request initiated by the centralized management and control layer accessing through the monitoring channel, after a preset approval process, issue a temporary scope token to the centralized management and control layer, so that the monitoring channel obtains limited control permissions for a specific device within the token's validity period. After the token expires, the permissions are automatically revoked, and the protocol stack of the monitoring channel temporarily registers the corresponding downlink instruction frame parser within the token's validity period.

8. An industrial equipment control method based on the industrial equipment edge control system according to any one of claims 1-7, characterized in that, include: S100, each edge control domain operates independently and continuously stores all operational data generated at its device layer in the local edge full database; S200: The centralized control layer initiates a connection to at least one edge control domain and independently performs bidirectional channel authentication with each edge control domain, negotiating and establishing the channel type for this connection, wherein the channel type is a control channel or a monitoring channel. S300. The centralized control layer executes differentiated data synchronization strategies and device control permissions according to the channel type established with each edge control domain: for the control channel, it executes bidirectional interaction of instruction issuance and data return; for the monitoring channel, it only executes data query and subscription from the edge control domain to the centralized control layer, and blocks any control instruction frames flowing to the edge control domain at the protocol stack level. S400. In response to the channel switching request initiated by the centralized control layer, the target edge control domain approves the request. After approval, it renegotiates the channel type for connection and synchronously updates the instruction frame parser registration status, data synchronization strategy, and permission strategy at the protocol stack level.

9. The industrial equipment control method according to claim 8, characterized in that: Step S200 includes: S210. When a new device is connected in the device layer of the edge control domain, the intermediate access service layer of the edge control domain identifies its device type identifier and reports it to the centralized control layer. S220. The centralized control layer matches the corresponding equipment type description file from the equipment type resource library based on the equipment type identifier; S230. Based on the device type description file, dynamically instantiate the corresponding device driver object and create an isolated driver runtime context for the device type; and dynamically load the differentiated operation view and function set associated with the device type and inject them into the unified management interface to provide parallel management of multiple types of devices in the same management interface of the centralized management layer.

10. The industrial equipment control method according to claim 8, characterized in that: In step S300, the edge control domain performs bidirectional data synchronization with the centralized control layer through asynchronous communication, performs local caching when the network is interrupted, and performs breakpoint resume transmission after the network is restored.

11. A computer-readable storage medium, characterized in that: It stores a computer program, which, when executed by a processor, implements the industrial equipment control method as described in any one of claims 8-10.

Images