Internet of Things edge gateway plug and play implementation method, edge gateway and edge cluster

Abstract

The invention relates to a plug-and-play implementation method for an edge gateway of the Internet of Things, the edge gateway and an edge cluster, and belongs to the technical field of power system management. According to the invention, the newly added and / or deleted equipment and the corresponding model thereof are identified through the edge gateway; correspondingly adding the identified model information corresponding to the newly-added and / or deleted equipment into a newly-added model list and / or a deleted model list in the edge gateway; sending a model change message generated by adding the model list and / or deleting the model list to the corresponding edge cluster; the edge cluster takes a device model file which does not exist in the edge cluster as a model file needing to be called according to the model change message, and takes a model file of a device model deleted by all edge gateways in the edge cluster as a model file needing to be deleted; calling the model file needing to be called through the edge cluster, and deleting the model file needing to be deleted in the edge cluster; and the edge gateway also responds to the call of the edge cluster and uploads the corresponding model file.

Description

Technical Field

[0001] The present invention relates to a plug-and-play implementation method for an edge gateway of the Internet of Things, an edge gateway and an edge cluster, and belongs to the technical field of power system management. Background Art

[0002] At present, the model management solutions adopted between the power dispatching master station and the substation monitoring system are basically that the substation provides model services to monitor model changes, send model change signals, and respond to the master station model call, and the plug-and-play of the model is not realized. At the same time, since the substation has only one model file (SCD file), there is no addition or deletion of model files. Therefore, the substation only needs to monitor the content changes of the model file. However, as long as the model changes, in order to maintain the model consistency between the master station and the substation, regardless of the size of the model file change, the master station needs to call the entire model file, resulting in low transmission efficiency. At the same time, the master station needs to perform difference analysis on the entire model file to determine the range of changes, which increases the burden on the master station.

[0003] The Chinese patent document with announcement number CN111969718B discloses a plug-and-play access method and device for low-voltage distribution network equipment, the device includes a distribution master station, a distribution transformer terminal and a low-voltage secondary device, and the method includes the distribution transformer terminal discovering the access request of the low-voltage secondary device; the distribution transformer terminal instantiates the low-voltage secondary device model; when the distribution transformer terminal accesses the distribution master station, the communication service App inside the distribution transformer terminal synthesizes all ICD files in the substation area and sends them to the distribution master station; the distribution master station receives and parses the total ICD file sent by the distribution transformer terminal, automatically completes the subscription to the data set, generates a CID file and sends it to the distribution transformer terminal; the communication service App inside the distribution transformer terminal parses the CID file sent by the distribution master station, generates a communication point table for information interaction between the distribution transformer terminal and the distribution master station, and communicates with the distribution transformer terminal to complete the low-voltage secondary device on the distribution master station, realizing automatic edge computing modeling and plug-and-play of terminal equipment. This method is equivalent to uploading the entire model file of the distribution transformer terminal to the distribution master station, which has the problems of low transmission efficiency and heavy burden on the master station.

[0004] A Chinese patent document with publication number CN117692313A discloses a device plug-and-play method based on cloud-edge collaborative application technology. The method includes the following steps: using the device information of the sensing device to establish a sensing device configuration model through the business main station; before the sensing device is installed, the business main station sends the configuration model of the sensing device to the edge device through the Internet of Things management platform. When the sensing device is installed and powered on, the edge device implements remote configuration of the sensing device according to the configuration model sent by the Internet of Things management platform. After the configuration is completed, the sensing device can be used directly to achieve plug-and-play function. In this method, the sensing device and the sending of the configuration model need to be completed through the main station. The main station needs to store a large amount of device model related information. If the main station does not have relevant model information, plug-and-play cannot be achieved. This method has high requirements for the main station and is limited in adaptability to scenarios. Summary of the invention

[0005] The purpose of the present invention is to provide a plug-and-play implementation method for an edge gateway of the Internet of Things, an edge gateway and an edge cluster, so as to solve the problem that the master station is overloaded or the storage or computing requirements of the master station are too high when the equipment in the power grid is changed.

[0006] To achieve the above object, the solution of the present invention includes: The invention discloses a plug-and-play implementation method for an edge gateway of the Internet of Things, comprising the following steps: identifying newly added and / or deleted devices and their corresponding models through an edge gateway; adding model information corresponding to the identified newly added and / or deleted devices into a newly added model list and / or a deleted model list in the edge gateway; sending a model change message generated by the newly added model list and / or the deleted model list to a corresponding edge cluster; the edge cluster uses a device model file that does not exist in itself as a model file to be summoned according to the model change message, and uses a model file of a device model deleted by all edge gateways in the edge cluster as a model file to be deleted; summoning the model file to be summoned through the edge cluster, and deleting the model file to be deleted in the edge cluster; the edge gateway also responds to the summoning of the edge cluster and sends the corresponding model file.

[0007] Furthermore, after the edge gateway establishes a connection with the edge cluster for the first time, the edge gateway actively uploads a model list of the models of the devices connected to the edge gateway. The edge cluster summons the device model files that do not exist in itself as the model files that need to be summoned based on the received model list. The edge gateway responds to the call of the edge cluster and sends the corresponding model files.

[0008] Furthermore, the edge gateway monitors the addition and / or deletion of devices connected to the edge gateway and their corresponding models through the application in the edge gateway. After the application initializes the information of the devices and their corresponding models in the current edge gateway, it will generate a new device list and a new model list currently in use. Then, it will traverse the new model list and compare it with the old model list that was last registered before this initialization. The model information of the models that are inconsistent with the old model list will be added to the new model list.

[0009] Furthermore, after traversing the new model list, the old device list will be traversed, and the device instance ID in the old device list will be compared with the device instance ID in the new device list. If no consistent device instance ID is found and the model information of the model corresponding to the device is not in the new model list, the model information of the device is added to the deleted model list. If a consistent device instance ID is found and the model information of the device model is not in the new model list, the model information of the model corresponding to the device is added to the deleted model list.

[0010] Furthermore, the device list is composed of device information including a unique device instance ID in the edge gateway and a model name corresponding to the device instance; the model list is composed of model information including a unique model name in the edge gateway, a model file modification time, a model file full path name and a model file verification code; the model change message is composed of model information and a model change type; the model name includes model version and model file verification code information. When the model content changes, the model version and model verification code information change accordingly, and the model name also changes accordingly; model change types include addition and deletion.

[0011] Furthermore, when both the newly added model list and the deleted model list are empty, the edge gateway no longer sends a model change message to the edge cluster.

[0012] An edge gateway of the Internet of Things of the present invention identifies newly added and / or deleted devices and their corresponding models; adds model information corresponding to the identified newly added and / or deleted devices to a newly added model list and / or a deleted model list in the edge gateway; sends a model change message generated by the newly added model list and / or the deleted model list to a corresponding edge cluster; and the edge gateway also responds to a call from the edge cluster and sends a corresponding model file.

[0013] Furthermore, after the edge gateway registers the model and device for the first time and establishes a new connection with the edge cluster, it actively uploads the model list of the registered model; the edge gateway also responds to the call of the edge cluster and uploads the corresponding model file.

[0014] Furthermore, the edge gateway monitors the addition and / or deletion of devices connected to the edge gateway and their corresponding models through the application in the edge gateway. After the application initializes the information of the devices and their corresponding models in the current edge gateway, it will generate a new device list and a new model list currently in use. Then, it will traverse the new model list and compare it with the old model list that was last registered before this initialization. The model information of the models that are inconsistent with the old model list will be added to the new model list.

[0015] Furthermore, after traversing the new model list, the old device list that was last registered before this initialization will be traversed, and the device instance ID in the old device list will be compared with the device instance ID in the new device list. If no consistent device instance ID is found and the model information corresponding to the device model is not in the new model list, the model information corresponding to the device model is added to the deleted model list. If a consistent device instance ID is found and the model information corresponding to the device model is not in the new model list, the model information corresponding to the device model is added to the deleted model list.

[0016] Furthermore, when both the newly added model list and the deleted model list are empty, the edge gateway no longer sends a model change message to the edge cluster.

[0017] An edge cluster of the Internet of Things of the present invention receives a model change message sent by an edge gateway, and according to the model change message, uses a device model file that does not exist in the edge cluster as a model file that needs to be summoned, and uses a model file of a device model deleted by all edge gateways as a model file that needs to be deleted; the edge cluster summons the model file that needs to be summoned, and deletes the model file that needs to be deleted in the edge cluster; the model change message is generated by the edge gateway according to the newly added and / or deleted devices.

[0018] Furthermore, after the edge cluster establishes a connection with the edge gateway for the first time, the device model files that do not exist in the edge cluster are summoned as model files that need to be summoned according to the model list sent by the edge gateway.

[0019] The beneficial effects of the present invention are: The present invention is a pioneering invention. The present invention provides a plug-and-play implementation method for an edge gateway of the Internet of Things, an edge gateway and an edge cluster. The edge gateway is a gateway deployed at the edge of the Internet of Things. In the power grid Internet of Things, an edge gateway can correspond to a substation, and an edge gateway can access many terminal devices in the substation; the edge cluster is usually used to deploy and manage a large number of computing resources and services in the edge environment. In the power grid Internet of Things, an edge cluster corresponds to a power dispatching master station (master station), and a master station governs multiple substations (that is, an edge cluster can connect to many edge gateways). The terminal devices in the substation have their own model files. The edge gateway dynamically monitors the model files of all devices in the substation, identifies new models and deleted models, and sends model change message notifications to the edge cluster. The edge cluster combines the storage and usage of the current model file to call the new model and delete the deleted model in the edge gateway, thereby maintaining the consistency of the edge cluster and the edge gateway model, realizing the plug-and-play of the edge gateway model, reducing the burden of the master station, and appropriately reducing the requirements for the master station storage and computing power. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] Figure 1 It is the interaction diagram between edge gateway and edge cluster model; Figure 2 It is the edge gateway model change monitoring flow chart. DETAILED DESCRIPTION

[0021] In order to make the purpose, technical solutions and advantages of the present invention more clear, the present invention is further described in detail below in conjunction with the accompanying drawings and embodiments.

[0022] The concept of the present invention is to propose a plug-and-play implementation method for an edge gateway of the Internet of Things, an edge gateway and an edge cluster. The edge gateway is a gateway deployed at the edge of the Internet of Things. The following takes the application of the solution of the present invention in the power grid Internet of Things as an example to illustrate the solution of the present invention. In the power grid Internet of Things, an edge gateway can correspond to a substation or energy storage station, and an edge gateway can access many terminal devices in the corresponding substation or energy storage station; the edge cluster is usually used to deploy and manage a large number of computing resources and services in the edge environment. In the power grid Internet of Things, an edge cluster corresponds to a power dispatching master station or a business master station (i.e., a master station), and a master station governs multiple substations or multiple energy storage stations (i.e., an edge cluster can connect to many edge gateways). The terminal devices in the edge gateway have their own model files. The edge gateway dynamically monitors the model files of all devices within its range, identifies new models and deleted models, and sends model change message notifications to the edge cluster. The edge cluster combines the storage and usage of the current model files to call the new model and delete the deleted model in the edge gateway, thereby maintaining the consistency of the edge cluster and the edge gateway model, and realizing the plug-and-play of the edge gateway model.

[0023] Edge gateway plug-and-play implementation method embodiment: like Figure 1 As shown in the figure, the interaction process between the edge gateway and the edge cluster is as follows: (1) Edge gateway registration model and device; Model information includes: a) Model name (a unique name within the edge gateway. Model names within the same edge gateway are not repeated. The model name contains the model version and model file verification code information. When the model content changes, the model version and model verification code information change accordingly, and the model name also changes accordingly) b) Model file modification time c) Full path name of the model file d) Model file verification code Device information includes: a) Device instance ID (unique ID within the edge gateway) b) Model name corresponding to the device instance (2) The edge cluster establishes a secure connection with the edge gateway; (3) The edge gateway actively uploads the model list, which contains all model information. Each model information includes: model name, model file modification time, model file full path name, and model file verification code; (4) The edge cluster parses the received model list, combines the model files uploaded by all edge gateways connected to the edge cluster, and takes the non-existent device model files as the model files that need to be summoned; (5) Edge cluster summoning model file; (6) The edge gateway responds to the file call and uploads the model file; (7) Repeat steps (5) to (6) until all model files that need to be summoned have been uploaded; (8) The edge gateway starts model change monitoring. The process is as follows: Figure 2 As shown, it is specifically introduced in the edge gateway model change monitoring process below; (9) The edge gateway detects model changes and actively sends model change messages; The model change message contains all the model information that has changed. Each model information change includes: a) Model name b) Model modification time c) Full path name of the model file d) Model change type (divided into addition and deletion) e) Model file verification code (10) The edge cluster parses the received model change message, compares the model file whose model change type is added with the model file stored in itself, adds the device model file that does not exist in the edge cluster to the summoning queue as the model file that needs to be summoned, and deletes the device model file whose change type is deleted and is not used by all edge gateways in the edge cluster as the model file that needs to be deleted; (11) Repeat steps (5) to (6) until all model files that need to be summoned have been uploaded.

[0024] like Figure 2 As shown, the edge gateway model change monitoring process is as follows: (1) The APP is launched and the current model and device information are initialized; (2) Query the data center for a list of currently registered model information; (3) Traverse the currently used model list (new model list) and compare it with the queried registered model list (old model list) to check whether the model name, model file modification time, and model file verification code in the model information are consistent. If a model with consistent information is not found in the registered model list, it indicates that the model is not registered, and then it is added to the new model list; (4) Query the data center for a list of currently registered devices; (5) Traverse the queried registered device information list (old device list) and compare it with the current device list (new device list). If the device instance ID does not exist in the current device list and the model used by the device is not used by other devices, then add the model used by the device to the deleted model list; if the device instance ID exists in the current device list and the model used by the device does not exist in the currently used model list, then add the model used by the device to the deleted model list; (6) If both the newly added model list and the deleted model list are empty, there is no need to send a message to the edge cluster; if the newly added model list or the deleted model list is not empty, a model change message is generated by the newly added model list and the deleted model list, the model and device information is registered with the data center, and a model change message is sent to the edge cluster. The edge cluster parses the received model change message, combines the model files uploaded by all edge gateways connected to the edge cluster, compares the model files with the model change type of addition with the model files stored in itself, adds the device model files that do not exist in the edge cluster to the summoning queue as the model files that need to be summoned, and deletes the device model files with the change type of deletion that are no longer used by other edge gateways as the model files that need to be deleted.

[0025] To sum up, in the plug-and-play implementation method of the IoT edge gateway, the identification of new devices and the registration of models and devices are all completed by the edge gateway. The edge gateway can identify new models and deleted models and generate a model change list. When interacting with the edge cluster, it actively sends model change messages. The edge cluster summons the new model and deletes the deleted model based on the list sent by the edge gateway and the storage and usage of the current model files in the edge cluster, thereby maintaining the consistency of the edge cluster and edge gateway models.

[0026] Edge Gateway Example: This embodiment provides an Internet of Things edge gateway, which has been clearly introduced in the embodiment of the edge gateway plug-and-play implementation method and will not be repeated here.

[0027] Edge cluster implementation: This embodiment provides an Internet of Things edge cluster, which has been clearly introduced in the embodiment of the edge gateway plug-and-play implementation method and will not be repeated here.

Claims

1. A plug-and-play implementation method for an edge gateway of the Internet of Things, characterized in that: The method comprises the following steps: identifying newly added and / or deleted devices and their corresponding models through an edge gateway; adding the model information corresponding to the identified newly added and / or deleted devices to a newly added model list and / or a deleted model list in the edge gateway; and sending a model change message generated by the newly added model list and / or the deleted model list to a corresponding edge cluster; The edge cluster uses the device model files that do not exist in the edge cluster as the model files that need to be summoned according to the model change message, and uses the model files of the device models that are deleted by all edge gateways in the edge cluster as the model files that need to be deleted; Call the model files that need to be called through the edge cluster, and delete the model files that need to be deleted in the edge cluster; The edge gateway also responds to the call of the edge cluster and sends the corresponding model file.

2. The method for implementing plug-and-play of an edge gateway of the Internet of Things according to claim 1, characterized in that: After the edge gateway establishes a connection with the edge cluster for the first time, the edge gateway actively sends a model list of the models of the devices connected to the edge gateway. The edge cluster summons the device model files that do not exist in itself as the model files that need to be summoned according to the received model list. The edge gateway responds to the call of the edge cluster and sends the corresponding model files.

3. The method for implementing plug-and-play of an edge gateway of the Internet of Things according to claim 1, characterized in that: The edge gateway monitors the addition and / or deletion of devices connected to the edge gateway and their corresponding models through the application in the edge gateway. After the application initializes the information of the devices and their corresponding models in the current edge gateway, it will generate a new device list and a new model list currently in use. Then, it will traverse the new model list and compare it with the old model list that was last registered before this initialization. The model information of the model that is inconsistent with the old model list is added to the new model list.

4. The method for implementing plug-and-play of an edge gateway of the Internet of Things according to claim 3, characterized in that: After traversing the new model list, the old device list that was last registered before this initialization will be traversed, and the device instance ID in the old device list will be compared with the device instance ID in the new device list. If no consistent device instance ID is found and the model information corresponding to the device model is not in the new model list, the model information corresponding to the device model is added to the deleted model list. If a consistent device instance ID is found and the model information corresponding to the device model is not in the new model list, the model information corresponding to the device model is added to the deleted model list.

5. The method for implementing plug-and-play of an edge gateway of the Internet of Things according to claim 4, characterized in that: The device list is composed of device information including a unique device instance ID in the edge gateway and a model name corresponding to the device instance; the model list is composed of model information including a unique model name in the edge gateway, a model file modification time, a full path name of the model file and a model file verification code; the model change message is composed of the model information and the model change type; the model name includes the model version and model file verification code information. When the model content changes, the model version and model verification code information change accordingly, and the model name also changes accordingly; the model change types include addition and deletion.

6. The method for implementing plug-and-play of an edge gateway of the Internet of Things according to claim 1, characterized in that: When both the newly added model list and the deleted model list are empty, the edge gateway no longer sends the model change message to the edge cluster.

7. An Internet of Things edge gateway, characterized in that: The edge gateway identifies the newly added and / or deleted devices and their corresponding models; In the edge gateway, the model information corresponding to the newly added and / or deleted devices is added to the newly added model list and / or the deleted model list; and a model change message generated by the newly added model list and / or the deleted model list is sent to the corresponding edge cluster; The edge gateway also responds to the call of the edge cluster and sends the corresponding model file.

8. The IoT edge gateway according to claim 7, characterized in that: After the edge gateway registers the model and device for the first time and establishes a new connection with the edge cluster, it actively sends the model list of the registered model; the edge gateway also responds to the call of the edge cluster and sends the corresponding model file.

9. The IoT edge gateway according to claim 7, characterized in that: The edge gateway monitors the addition and / or deletion of devices connected to the edge gateway and their corresponding models through the application in the edge gateway. After the application initializes the information of the devices and their corresponding models in the current edge gateway, it will generate a new device list and a new model list currently in use. Then, it will traverse the new model list and compare it with the old model list that was last registered before this initialization. The model information of the model that is inconsistent with the old model list is added to the new model list.

10. The IoT edge gateway according to claim 9, characterized in that: After traversing the new model list, the old device list that was last registered before this initialization will be traversed, and the device instance ID in the old device list will be compared with the device instance ID in the new device list. If no consistent device instance ID is found and the model information corresponding to the device model is not in the new model list, the model information corresponding to the device model is added to the deleted model list. If a consistent device instance ID is found and the model information corresponding to the device model is not in the new model list, the model information corresponding to the device model is added to the deleted model list.

11. The IoT edge gateway according to claim 7, characterized in that: When both the newly added model list and the deleted model list are empty, the edge gateway no longer sends the model change message to the edge cluster.

12. An Internet of Things edge cluster, characterized in that: The edge cluster receives the model change message sent by the edge gateway, and according to the model change message, takes the device model file that does not exist in the edge cluster as the model file that needs to be summoned, and takes the model file of the device model deleted by all edge gateways as the model file that needs to be deleted; The model files that need to be summoned are summoned through the edge cluster, and the model files that need to be deleted are deleted in the edge cluster; the model change message is generated by the edge gateway according to the newly added and / or deleted devices.

13. The IoT edge cluster according to claim 12, characterized in that: After the edge cluster establishes a connection with the edge gateway for the first time, the device model file that does not exist in the edge cluster is summoned as the model file that needs to be summoned according to the model list sent by the edge gateway.

Images