Collaborative Linkage Method for Automatic Identification of Devices Based on Edge Controllers

Abstract

The present invention relates to a collaborative linkage method for automatic identification of devices based on an edge controller, comprising the following steps: discovering and identifying front-end devices; specifically including the steps of: collecting original data; executing a data processing process for discovering new devices; executing a device identity identification process; and executing multi-device linkage processing. The present invention applies the methods for automatically discovering and identifying front-end devices and multi-device linkage processing within a local area network to the Internet of Things edge controller on highways, solves the problems of incompatible interactions, unshared information, and difficult management among various devices on highways; realizes the interactive integration and information sharing among devices, and provides technical support for the informatization of highways; can automatically collect the basic information of front-end devices without manual participation, with complete and error-free information collection; realizes the collaborative linkage of multiple devices, and by using a combination of system-level linkage and local linkage, can be flexibly switched according to different scenarios.

Description

Technical Field

[0001] The present invention relates to the technical field of Internet of Things (IoT) control and management for expressways, and particularly to a collaborative linkage method for automatic device recognition based on an edge controller. Background Art

[0002] With the wide application of IoT devices on expressways, the informatization and intelligent development of expressways have been significantly accelerated. However, currently, there are a wide variety of front-end devices on expressways, and suppliers provide different technologies and devices, resulting in inconsistent device access standards and inability to achieve data interconnection and interoperability, and thus it is impossible to establish a unified IoT control and management platform for expressways. This has led to two problems to be solved:

[0003] 1. If a front-end device is to be launched on the control and management platform, it must first register basic information (including but not limited to manufacturer, device type, device model, IP address, MAC address, installation location) on the platform page. However, only by manually collecting the basic information of the front-end device first and then entering it into the system, an unfavorable situation is created, that is, not only the collection form is single, but also the entered information is often incomplete, even incorrect, or not modified in a timely manner, increasing the cost of system operation and maintenance;

[0004] 2. Due to the obvious structured characteristics, single functions, and mutual independence of front-end devices, data sharing cannot be achieved, and further, collaborative linkage cannot be realized in the process, and the scope of action is very limited.

[0005] To solve the above objectively existing technical problems, the solution of the prior art in the traditional way is to adopt a centralized device management method, connect all front-end devices to the platform, and then perform operation and maintenance management and centralized control of the devices through the front-end web page.

[0006] The defects of the prior art are as follows:

[0007] 1. Since the information entry of front-end devices into the system can only be carried out manually, not only the form is single, but also the entered information is incomplete or even incorrect;

[0008] 2. Due to the single structure, mutual independence, and fixed business processes of front-end devices, the regional collaborative effect is not obvious. Summary of the Invention

[0009] In view of the above problems, the present invention provides a collaborative linkage method for automatic identification of devices based on an edge controller, aiming to apply the methods for automatic discovery and identification of front-end devices and the method for multi-device linkage processing within a local area network to the Internet of Things edge controller on highways, so as to solve the problems of incompatible interaction, unshared information, and difficult management among various devices on highways, realize the interactive integration and information sharing among devices, and provide technical support for the informatization of highways; realize the automatic collection of basic information of front-end devices without manual participation, with complete and error-free information collection; realize the collaborative linkage of multiple devices, and use a combination of system-level linkage and local linkage, which can be flexibly switched according to different scenarios.

[0010] To solve the above problems, the technical solution provided by the present invention is as follows:

[0011] A collaborative linkage method for automatic identification of devices based on an edge controller, comprising the following steps:

[0012] S100. Discover and identify front-end devices; specifically including the following steps:

[0013] S110. Collect raw data;

[0014] S120. Execute the data processing flow for new device discovery;

[0015] S130. Execute the device identity identification process;

[0016] S200. Execute multi-device linkage processing.

[0017] Preferably, S110 specifically includes the following steps:

[0018] S111. Set the network card of the edge controller to promiscuous mode to receive all raw data packets passing through this network card;

[0019] S112. Copy the raw data packet from the network device driver to the memory of the upper-layer application for caching;

[0020] S113. Extract the IP address, MAC address, PORT port number, and connection method TCP / UDP of the source host in the data frame header; then package the IP address, the MAC address, the PORT port number, and the connection method TCP / UDP as device information and output it as the result of S110.

[0021] Preferably, the data processing flow for new device discovery in S120 specifically includes the following steps:

[0022] S121. Obtain the device information in S113;

[0023] S122. Divide the device information into newly discovered device information and device information existing in the flash;

[0024] S123a. Determine whether the device information existing in the flash is empty, and perform the following operations according to the determination result:

[0025] If the device information existing in the flash is not empty, return and execute S121 again;

[0026] If the device information existing in the flash is empty, execute S123b;

[0027] S123b. Determine whether the newly discovered device information is not registered in the real-time update table, and perform the following operations according to the determination result:

[0028] If the newly discovered device information is registered in the real-time update table, return and execute S121 again;

[0029] If the newly discovered device information is not registered in the real-time update table, register the newly discovered device information in the real-time update table; then execute S124;

[0030] S124. Determine whether the device information is not registered in the information summary table, and perform the following operations according to the determination result:

[0031] If the device information is registered in the information summary table, return and execute S121 again;

[0032] If the device information is not registered in the information summary table, register the device information in the information summary table; then execute S125;

[0033] S125. Determine whether the device identity is recognized, and perform the following operations according to the determination result:

[0034] If the device identity is not recognized, return and execute S121 again;

[0035] If the device identity is recognized, record the device identity in the information confirmation table.

[0036] Preferably, the device identity recognition process in S130 specifically includes the following steps:

[0037] S131. Copy the data in the information summary table to the memory;

[0038] S132. Perform OUI library analysis to find the corresponding device manufacturer code; then perform the following operations according to the search result:

[0039] If the MAC address does not have a corresponding device manufacturer code, return and execute S131 again;

[0040] If the MAC address has a corresponding device manufacturer code, execute S133;

[0041] S133. Analyze the device manufacturer parameter EMP library to find the network configuration parameters corresponding to the device manufacturer code obtained in S132; the network configuration parameters include the commonly used PORT port number of the device, the connection method TCP / UDP, and the instruction protocol; then perform the following operations according to the search results:

[0042] If the device manufacturer code does not have corresponding network configuration parameters, return and execute S131 again;

[0043] If the device manufacturer code has corresponding network configuration parameters, execute S134;

[0044] S134. Try to connect to the peer network device according to the IP address, the PORT port number, and the connection method TCP / UDP; then perform the following operations according to the connection result:

[0045] If the connection fails, return and execute S131 again;

[0046] If the connection is successful, execute S135;

[0047] S135. Send the general query command in the instruction protocol to the peer network device; then perform the following operations according to the response result of the peer network device:

[0048] If the peer network device does not reply within the artificially preset response period, return and execute S131 again;

[0049] If the peer network device replies within the artificially preset response period, execute S136;

[0050] S136. Further send a series of commands to the peer network device to obtain more device information;

[0051] S137. Store the device information in the flash in the artificially preset format.

[0052] Preferably, S200 specifically includes the following steps:

[0053] S210. Register the device information of the newly connected front-end device in the local Hash linked list; at the same time, report the device information to the system control platform;

[0054] S220. The system control platform matches the device linkage template according to the device information obtained in S210. The device linkage template includes: policy number, enabled status, trigger condition, cycle period, execution object, and configuration information.

[0055] S230. Check whether the system service data meets the linkage trigger condition preset manually, and then perform the following operations according to the check result:

[0056] If the system service data does not meet the linkage trigger condition, return and execute S220 again.

[0057] If the system service data meets the linkage trigger condition, execute S240.

[0058] S240. The system control platform immediately sends the device linkage template to the node controller of the corresponding node. The device linkage template is saved in the flash of the node controller in the form of an XML file.

[0059] S250. After receiving the command, the node controller parses the device linkage template in the form of an XML file and matches the device information to obtain a control instruction.

[0060] S260. The node controller distributes the control instruction to the corresponding front-end device.

[0061] Preferably, in S240, the node controllers in different regions are divided into a logical group according to the application scenario. All the node controllers in the same logical group receive the issued linkage policy simultaneously at one time.

[0062] Preferably, in S220, the linkage policy in the new scenario is also designed manually by editing according to the obtained device information.

[0063] Preferably, when performing the OUI library analysis in S132, the corresponding device manufacturer code is found according to the first 24 bits of the MAC address.

[0064] Preferably, in S134, the SOCKET socket technology is adopted to attempt to connect to the peer network device according to the IP address, the PORT port number, and the connection method TCP / UDP.

[0065] Preferably, the XML file for local linkage in S240 is also directly obtained through the web client and the configuration information is modified.

[0066] Compared with the prior art, the present invention has the following advantages:

[0067] 1. Since the method for automatically discovering and identifying front-end devices within a local area network in the present invention is applied to the Internet of Things edge controller on highways, it realizes the automatic entry of the basic information of front-end devices into the system without manual participation, with complete information collection and low error rates.

[0068] 2. Since the present invention adopts a multi-device linkage processing method in the Internet of Things edge controller that can improve the regional collaborative ability of highways, it realizes the collaborative linkage of multiple devices. By using a combination of system-level linkage and local linkage, it can be flexibly switched according to different scenarios. BRIEF DESCRIPTION OF THE DRAWINGS

[0069] Figure 1 It is a system overall schematic block diagram of the embedded software and hardware system platform of a specific embodiment of the present invention;

[0070] Figure 2 It is a schematic diagram of the new device discovery data processing flow of a specific embodiment of the present invention;

[0071] Figure 3 It is a schematic diagram of the device identity recognition process of a specific embodiment of the present invention;

[0072] Figure 4 It is a schematic diagram of the combination method of system-level linkage and local linkage of multiple devices in a specific embodiment of the present invention. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0073] The following further clarifies the present invention in conjunction with specific embodiments. It should be understood that these embodiments are only used to illustrate the present invention and not to limit the scope of the present invention. After reading the present invention, various equivalent modifications made by those skilled in the art to the present invention fall within the scope defined by the appended claims of this application.

[0074] It should be noted in advance that the prerequisite for applying the present invention is that the networking must meet the requirements: the front-end device and the edge controller are connected to different network ports of the same switch, and all nodes of the system network must satisfy network reachability.

[0075] Such as Figure 1As shown in the figure, it should be further noted that in order to achieve the technical purpose of the present invention, this specific embodiment includes an Internet of Things edge controller based on an embedded software and hardware system platform, which is designed with functions of automatic discovery and identification of network devices, device management, and device collaborative linkage, reducing the operation and maintenance costs during the process of device access to the system. At the same time, it realizes the decoupling of the system center platform and the front-end devices, reduces the excessive dependence of the system on the network environment, and optimizes the collaborative process between devices. From the system level, the Internet of Things edge controller belongs to the edge layer and is a bridge connecting the upper management and control platform and the lower front-end devices. From the physical connection perspective, the edge controller and the front-end devices are connected to different network ports of the same switch and are accessed to the system in a bypass manner, mainly to be compatible with the traditional networking method of directly accessing the front-end devices to the system without damaging the original networking and reducing the risks brought by network transformation.

[0076] A collaborative linkage method for automatic identification of devices based on an edge controller includes the following steps:

[0077] S100. Discover and identify front-end devices; specifically including the following steps:

[0078] S110. Collect raw data.

[0079] In this specific embodiment, S110 specifically includes the following steps:

[0080] S111. Set the network card of the edge controller to promiscuous mode to receive all raw data packets passing through this network card.

[0081] S112. Copy the raw data packets from the network device driver to the memory of the upper-layer application for caching.

[0082] In this specific embodiment, S112 is implemented using the libcap technology under the Unix / Linux platform.

[0083] S113. Extract the IP address, MAC address, PORT port number, and connection method TCP / UDP of the source host in the data frame header; then package the IP address, MAC address, PORT port number, and connection method TCP / UDP as device information and output it as the result of S110.

[0084] It should be noted that in this specific embodiment, the method of the present invention only parses the header of the data frame and does not parse the complex service data in the data frame, improving the packet processing ability of the system.

[0085] As Figure 2 shown, S120. Execute the data processing flow for new device discovery.

[0086] It should be noted that in order to implement the functions of S200, three tables are designed and defined in the system of the present invention, namely:

[0087] The first table: the real-time update table, which is used to store the IP address, MAC address, PORT port number, and connection method TCP / UDP extracted from the original data frame header.

[0088] The second table: the information summary table, which is used to store all the contents of the first and third tables and remove duplicate information.

[0089] The third table: the information confirmation table, which refers to the table that successfully identifies the device identity and contains complete device information.

[0090] It should be further noted that operations such as addition, deletion, query, and modification of the first table (real-time update table) and the second table (information summary table) are all performed in memory, and the system processing efficiency is extremely high. The third table (information confirmation table) will be stored in the FLASH user data area, and even when the system power fails suddenly due to an unexpected situation, the data can be quickly restored after reboot.

[0091] In this specific embodiment, the new device discovery data processing flow in S120 specifically includes the following steps:

[0092] S121. Obtain the device information from S113.

[0093] S122. Divide the device information into newly discovered device information and device information existing in the flash.

[0094] S123a. Determine whether the device information existing in the flash is empty, and perform the following operations according to the determination result:

[0095] If the device information existing in the flash is not empty, return and execute S121 again.

[0096] If the device information existing in the flash is empty, execute S123b.

[0097] S123b. Determine whether the newly discovered device information is not registered in the real-time update table, and perform the following operations according to the determination result:

[0098] If the newly discovered device information is already registered in the real-time update table, return and execute S121 again.

[0099] If the newly discovered device information is not registered in the real-time update table, register the newly discovered device information in the real-time update table; then execute S124.

[0100] S124. Determine whether the device information is not registered in the information summary table, and perform the following operations according to the determination result:

[0101] If the device information has been registered in the information summary table, return and execute S121 again.

[0102] If the device information is not registered in the information summary table, register the device information in the information summary table; then execute S125.

[0103] S125. Determine whether the device identity is recognized, and perform the following operations according to the determination result:

[0104] If the device identity is not recognized, return and execute S121 again.

[0105] If the device identity is recognized, record the device identity in the information confirmation table.

[0106] As Figure 3 shown, S130. Execute the device identity recognition process.

[0107] It should be noted that the technical purpose of S130 is to quickly and accurately identify which manufacturer, what type, and more detailed information the network device belongs to.

[0108] It should be further noted that the method of the present invention integrates two types of private libraries. The first type is the OUI library, which is responsible for storing the correspondence between device manufacturer codes and the unique network identification MAC address. The second type is the device manufacturer parameter EMP library, which is responsible for storing, including but not limited to, the common product names, product models, network configuration parameters, and general instruction protocols of device manufacturers.

[0109] In this specific embodiment, the device identity recognition process in S130 specifically includes the following steps:

[0110] S131. Copy the data in the information summary table to the memory.

[0111] It should be noted that at this time, the information summary table records the IP address, MAC address, PORT port number, and connection method TCP / UDP of the newly discovered network device.

[0112] S132. Perform OUI library analysis to find the corresponding device manufacturer code; then perform the following operations according to the search result:

[0113] If there is no corresponding device manufacturer code for the MAC address, return and execute S131 again.

[0114] If there is a corresponding device manufacturer code for the MAC address, execute S133.

[0115] In this specific embodiment, when performing OUI library analysis in S132, the corresponding device manufacturer code is obtained by looking up the first 24 bits (i.e., the first 3 bytes) of the MAC address.

[0116] S133. Perform device manufacturer parameter EMP library analysis to find the network configuration parameters corresponding to the device manufacturer code obtained in S132; the network configuration parameters include the commonly used PORT port number of the device, the connection method TCP / UDP, and the instruction protocol; then perform the following operations according to the search results:

[0117] If there are no corresponding network configuration parameters for the device manufacturer code, return and execute S131 again.

[0118] If there are corresponding network configuration parameters for the device manufacturer code, execute S134.

[0119] S134. Try to connect to the peer network device according to the IP address, PORT port number, and connection method TCP / UDP; then perform the following operations according to the connection result:

[0120] If the connection fails, return and execute S131 again.

[0121] If the connection is successful, execute S135.

[0122] In this specific embodiment, in S134, the SOCKET socket technology is used to try to connect to the peer network device according to the IP address, PORT port number, and connection method TCP / UDP matched in the above steps.

[0123] S135. Send the general query command in the instruction protocol to the peer network device; then perform the following operations according to the response result of the peer network device:

[0124] If the peer network device does not reply within the artificially preset response period, return and execute S131 again.

[0125] If the peer network device has a reply within the artificially preset response period, execute S136.

[0126] S136. Further send a nested instruction to the peer network device to obtain more device information.

[0127] S137. Store the device information in the flash in the artificially preset format.

[0128] As Figure 4 shown, S200. Perform multi-device linkage processing.

[0129] In this specific embodiment, S200 specifically includes the following steps:

[0130] S210. Register the device information of the newly connected front-end device into the local Hash linked list; meanwhile, report the device information to the system control platform.

[0131] It should be noted that the device information at this time includes but is not limited to device type, device manufacturer, and device model.

[0132] S220. The system control platform matches the device linkage template according to the device information obtained in S210; the device linkage template includes: policy number, enabled status, trigger condition, cycle period, execution object, and configuration information.

[0133] It should be noted that in addition to the above method of automatically matching the linkage policy template in S220, in this specific embodiment, a new linkage policy in a new scenario is also designed through manual editing according to the obtained device information.

[0134] S230. Check whether the system service data meets the linkage trigger condition preset manually, and then perform the following operations according to the check result:

[0135] If the system service data does not meet the linkage trigger condition, return and execute S220 again.

[0136] If the system service data meets the linkage trigger condition, execute S240.

[0137] S240. The system control platform immediately distributes the device linkage template to the node controller of the corresponding node; the device linkage template is saved in the flash of the node controller in the form of an XML file.

[0138] It should be noted that after the linkage policy template distributed by the system control platform is saved in the flash of the node controller in the form of an XML file, when the data collected by the node controller meets the linkage trigger condition, the control instruction will be immediately distributed to the corresponding front-end device without the need to be processed by the system control platform again, thus quickly achieving the linkage effect.

[0139] In this specific embodiment, in S240, the node controllers in different regions are divided into a logical group according to the application scenario; all the node controllers in the same logical group receive the distributed linkage policy simultaneously at one time.

[0140] It should be noted that the method of dividing the node controllers in different regions into a logical group according to the application scenario aims to improve the regional cooperation ability.

[0141] In this specific embodiment, the XML file of the local linkage in S240 can also be directly obtained through the web client and the configuration information can be modified.

[0142] It should be noted that the method of directly obtaining the XML file through the web client and the method of the system distributing the XML file coexist and are applied simultaneously, aiming to meet the personalized needs in different scenarios.

[0143] S250. After receiving the command, the node controller parses the device linkage template in the form of an XML file and matches the device information to obtain a control instruction.

[0144] S260. The node controller distributes the control instruction to the corresponding front-end device.

[0145] It should be noted that the present invention has achieved the organic combination and complementarity of the system-level linkage method and the local linkage method so far, making the best use of their respective advantages; specifically:

[0146] The system-level linkage method can be manually edited according to the network topology, and the node controllers in multiple locations are grouped into a logical unit, further expanding the regional linkage scope; the local linkage method does not require the participation of the system management platform and has higher execution efficiency. The combined use of the system-level linkage and the local linkage methods can meet the requirements of different scenarios and is more flexible and efficient.

[0147] In the above detailed description, various features are combined in a single embodiment to simplify the present disclosure. This method of disclosure should not be construed as reflecting an intention that the embodiments of the claimed subject matter require more features than those clearly recited in each claim. On the contrary, as reflected in the appended claims, the present invention is in a state with fewer features than all the features of the disclosed single embodiment. Therefore, the appended claims are hereby clearly incorporated into the detailed description, where each claim stands alone as a separate preferred embodiment of the present invention.

[0148] In order to enable any person skilled in the art to implement or use the present invention, the above-described disclosed embodiments have been described. For those skilled in the art; various modification methods of these embodiments are obvious, and the general principles defined herein can also be applied to other embodiments without departing from the spirit and protection scope of the present disclosure. Therefore, the present disclosure is not limited to the embodiments given herein, but is consistent with the broadest scope of the principles and novel features disclosed in this application.

[0149] The foregoing description includes examples of one or more embodiments. Of course, it is not possible to describe all possible combinations of components or methods for the purpose of describing the above embodiments, but those of ordinary skill in the art should recognize that the various embodiments can be further combined and arranged. Therefore, the embodiments described herein are intended to cover all such changes, modifications, and variations that fall within the scope of the appended claims. In addition, with respect to the term "comprising" as used in the specification or claims, this term is covered in a manner similar to the term "including" as interpreted when "including," is used as a transitional word in a claim. Further, any use of the term "or" in the specification or claims is to mean "non-exclusive or."

[0150] The specific embodiments described above further elaborate on the object, technical solution, and beneficial effects of the present invention. It should be understood that the above description is only the specific embodiments of the present invention and is not used to limit the protection scope of the present invention. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principle of the present invention shall be included within the protection scope of the present invention.

Claims

1. A collaborative linkage method for automatic identification of devices based on an edge controller, characterized in that: It includes the following steps: S100. Discover and identify the front-end devices; specifically, it includes the following steps: S110. Collect the original data; S120. Execute the new device discovery data processing flow; S130. Execute the device identity recognition process; S200. Execute the multi-device linkage processing; The new device discovery data processing flow described in S120 specifically includes the following steps: S121. Obtain the device information; S122. Divide the device information into newly discovered device information and device information existing in the flash; S123a. Determine whether the device information existing in the flash is empty, and perform the following operations according to the determination result: If the device information existing in the flash is not empty, return and execute S121 again; If the device information existing in the flash is empty, execute S123b; S123b. Determine whether the newly discovered device information is not registered in the real-time update table, and perform the following operations according to the determination result: If the newly discovered device information is already registered in the real-time update table, return and execute S121 again; If the newly discovered device information is not registered in the real-time update table, register the newly discovered device information in the real-time update table; then execute S124; S124. Determine whether the device information is not registered in the information summary table, and perform the following operations according to the determination result: If the device information is already registered in the information summary table, return and execute S121 again; If the device information is not registered in the information summary table, register the device information in the information summary table; Then execute S125; S125. Determine whether the device identity is recognized, and perform the following operations according to the determination result: If the device identity is not recognized, return and execute S121 again; If the device identity is recognized, record the device identity in the information confirmation table.

2. The collaborative linkage method for automatic identification of devices based on an edge controller according to claim 1, wherein: S110 specifically includes the following steps: S111. Set the network card of the edge controller to promiscuous mode to receive all the original data packets passing through this network card; S112. Copy the original data packets from the network device driver to the memory of the upper-layer application for caching; S113. Extract the IP address, MAC address, PORT port number, and connection method TCP / UDP of the source host in the data frame header; then pack the IP address, the MAC address, the PORT port number, and the connection method TCP / UDP into device information as the result output of S110.

3. The collaborative linkage method for automatic identification of devices based on an edge controller according to claim 2, characterized in that: The device identity recognition process described in S130 specifically includes the following steps: S131. Copy the data in the information summary table to the memory; S132. Perform OUI library analysis to find the corresponding device manufacturer code; then perform the following operations according to the search result: If there is no corresponding device manufacturer code for the MAC address, return and execute S131 again; If there is a corresponding device manufacturer code for the MAC address, execute S133; S133. Analyze the equipment manufacturer parameter EMP library, and search for the network configuration parameters corresponding to the equipment manufacturer code obtained in S132; the network configuration parameters include the commonly used PORT port number of the device, the connection method TCP / UDP, and the instruction protocol; then perform the following operations according to the search results: If there are no corresponding network configuration parameters for the equipment manufacturer code, return and execute S131 again; If there are corresponding network configuration parameters for the equipment manufacturer code, execute S134; S134. Try to connect to the peer network device according to the IP address, the PORT port number, and the connection method TCP / UDP; then perform the following operations according to the connection result: If the connection fails, return and execute S131 again; If the connection is successful, execute S135; S135. Send the general query command in the instruction protocol to the peer network device; then perform the following operations according to the response result of the peer network device: If the peer network device does not reply within the manually preset response period, return and execute S131 again; If the peer network device replies within the manually preset response period, execute S136; S136. Further send a nested instruction to the peer network device to obtain more device information; S137. Store the device information in the flash in the manually preset format.

4. The collaborative linkage method for automatic identification of devices based on an edge controller according to claim 3, characterized in that: S200 specifically includes the following steps: S210. Register the device information of the newly connected front-end device in the local Hash linked list; at the same time, report the device information to the system control platform; S220. The system control platform matches the device linkage template according to the device information obtained in S210; The device linkage template includes: policy number, enabled status, trigger condition, cycle period, execution object, configuration information; S230. Check whether the system service data meets the manually preset linkage trigger condition, and then perform the following operations according to the check result: If the system service data does not meet the linkage trigger condition, return and execute S220 again; If the system service data meets the linkage trigger condition, execute S240; S240. The system control platform immediately distributes the device linkage template to the node controller of the corresponding node; the device linkage template is saved in the flash of the node controller in the form of an XML file; S250. After receiving the command, the node controller parses the device linkage template in the form of an XML file and matches the device information to obtain the control instruction; S260. The node controller distributes the control instruction to the corresponding front-end device.

5. The collaborative linkage method for automatic identification of devices based on an edge controller according to claim 4, wherein: In S240, the node controllers in different regions are divided into a logical group according to the application scenario; all the node controllers in the same logical group receive the distributed linkage policy at the same time.

6. The collaborative linkage method for automatic identification of devices based on an edge controller according to claim 5, wherein: In S220, a new linkage policy in the new scenario is also designed by manual editing according to the obtained device information.

7. The collaborative linkage method for automatic identification of devices based on an edge controller according to claim 6, characterized in that: When performing the OUI library analysis in S132, the corresponding device manufacturer code is obtained by looking up the first 24 bits of the MAC address.

8. The collaborative linkage method for automatic identification of devices based on an edge controller according to claim 7, characterized in that: In S134, the SOCKET socket technology is adopted to attempt to connect to the peer network device according to the IP address, the PORT port number, and the connection method TCP / UDP.

9. The collaborative linkage method for automatic identification of devices based on an edge controller according to claim 8, characterized in that: In S240, the XML file for local linkage is also directly obtained through the web client, and the configuration information is modified.

Images