CN117938617B

CN117938617B - Device management method, device, computer device and storage medium

Info

Publication number: CN117938617B
Application number: CN202410309259.8A
Authority: CN
Inventors: 郭春庭
Original assignee: Jinan Inspur Data Technology Co Ltd
Current assignee: Jinan Inspur Data Technology Co Ltd
Priority date: 2024-03-19
Filing date: 2024-03-19
Publication date: 2024-06-21
Anticipated expiration: 2044-03-19
Also published as: CN117938617A

Abstract

The invention relates to the technical field of the Internet of things and discloses a device management method, a device, computer equipment and a storage medium. The invention provides a device management method, which is applied to a cloud, and comprises the following steps: sending a node access command, wherein the node access command is used for requesting to establish connection with an edge node under a target communication network; responding to the access of the current edge node, and sending the target equipment scanner to the current edge node so that the current edge node determines the Internet of things equipment to be managed according to the scanning result of the target equipment scanner; and controlling the current edge node to acquire equipment data of the to-be-managed Internet of things equipment based on the scanning result sent by the current edge node so as to manage the to-be-managed Internet of things equipment. The cloud end can independently manage the to-be-managed Internet of things equipment without manual intervention, and equipment management efficiency can be effectively improved.

Description

Device management method, device, computer device and storage medium

Technical Field

The invention relates to the technical field of the internet of things, in particular to a device management method, a device, computer equipment and a storage medium.

Background

Internet of things (Internet of Things, ioT) technology refers to a technology that connects various physical devices, sensors, and other objects through the internet, thereby enabling data sharing and communication.

In the related technology, in the cloud, the to-be-managed internet of things equipment to be supervised is bound to the edge node in a manual mode, and then the corresponding to-be-managed internet of things equipment is managed through the edge node. However, when the number of the internet of things devices to be managed is large and the number of the edge nodes is also large, if the internet of things devices to be managed are still managed in a manual mode, the device management efficiency is seriously affected.

Disclosure of Invention

In view of the above, the invention provides a device management method, a device, a computer device and a storage medium, so as to solve the problem of low efficiency of cloud management of the internet of things device to be managed.

In a first aspect, the present invention provides a device management method, applied to a cloud, where the method includes:

sending a node access command, wherein the node access command is used for requesting to establish connection with an edge node under a target communication network;

Responding to the access of the current edge node, and sending the target equipment scanner to the current edge node so that the current edge node determines the Internet of things equipment to be managed according to the scanning result of the target equipment scanner;

And controlling the current edge node to acquire equipment data of the to-be-managed Internet of things equipment based on the scanning result sent by the current edge node so as to manage the to-be-managed Internet of things equipment.

The beneficial effects are that: according to the device management method provided by the embodiment, the cloud terminal can enable the edge node under the same network to be automatically connected with the cloud terminal through the transmitted node access command, and further after connection is established with the current edge node, the target device scanner is transmitted to the current edge node, so that the current edge node can have the capability of automatically identifying the device of the internet of things to be managed, the current edge node is controlled to acquire the device data of the device of the internet of things to be managed according to the scanning result uploaded by the current edge node, the cloud terminal can be enabled to automatically manage the device of the internet of things to be managed without manual intervention, and the device management efficiency can be effectively improved.

In an alternative embodiment, in response to the current edge node being accessed, sending the target device scanner into the current edge node includes:

Responding to the accessed current edge node to obtain node information of the current edge node;

determining a target device scanner corresponding to the current edge node from a plurality of preset device scanners based on the node information;

The target device scanner is sent into the current edge node.

The beneficial effects are that: by sending the target equipment scanner to the current edge node in the mode, the issuing validity of the equipment scanner is guaranteed, and the Internet of things equipment to be managed can be effectively identified, so that the effectiveness of the Internet of things equipment to be managed in cloud management is improved.

In an alternative embodiment, determining a target device scanner corresponding to the current edge node from a preset plurality of device scanners based on the node information, includes:

determining the node identification of the current edge node according to the node information;

detecting whether the node identifier is a legal identifier or not through a preset access control list;

If the node identifier is legal identifier, determining a target device scanner corresponding to the current edge node from a plurality of preset device scanners.

In an alternative embodiment, determining, based on the node information, a target device scanner corresponding to the current edge node from a preset plurality of device scanners, further includes:

if the node identifier is an illegal identifier, a corresponding target device scanner is not determined from a plurality of preset device scanners for the current edge node.

In an alternative embodiment, different device scanners are used to scan different device types of internet of things devices to be managed; determining a target device scanner corresponding to the current edge node from a plurality of preset device scanners based on the node information, including:

Determining a target equipment type corresponding to the current edge node according to the node information;

And if the device scanner corresponding to the target device type exists in the plurality of device scanners, taking the device scanner corresponding to the target device type as the target device scanner.

In an alternative embodiment, the number of the target device types is a plurality, and the target device scanner corresponding to the current edge node is determined from a plurality of preset device scanners based on the node information, and the method further includes:

If the device scanner corresponding to the target device type does not exist in the device scanners, updating the device scanners based on the target device type.

In an alternative embodiment, the type of the target device corresponding to the current edge node depends on the current edge node group in which the current edge node is located, and the types of the target devices corresponding to different current edge node groups are not identical.

Determining a target network segment where a current edge node is located according to the node information;

detecting whether an associated edge node which is mutually communicated with the current edge node exists in the connected edge nodes corresponding to the target network segment through a preset node scanner;

if the connected edge nodes have associated edge nodes and the associated edge nodes comprise deployed device scanners, the deployed device scanners are used as target device scanners corresponding to the current edge nodes, and the deployed device scanners are target edge devices corresponding to the associated edge nodes in the device scanners.

In an alternative embodiment, the associated edge node is detected by the node scanner through a preset target internet protocol address list, and the target internet protocol address list includes a plurality of edge nodes corresponding to the target network segment and in communication with each other.

In an optional implementation manner, the scan result includes target device information of the internet of things device to be managed, and based on the scan result sent by the current edge node, the current edge node is controlled to collect device data of the internet of things device to be managed, including:

detecting whether the acquired historical scanning result comprises target equipment information or not;

if the history scanning result does not comprise the target equipment information, establishing a binding relation between the current edge node and the to-be-managed Internet of things equipment;

and sending the target data collector to the current edge node to control the current edge node to collect the equipment data of the to-be-managed Internet of things equipment through the target data collector.

In an optional implementation manner, based on the scan result sent by the current edge node, the current edge node is controlled to collect device data of the internet of things device to be managed, and the method further includes:

If the history scanning result comprises the target equipment information, acquiring the Internet protocol information of the current edge node;

And establishing and storing an association relation between the Internet protocol information and the target equipment information, and controlling the current edge node to acquire equipment data of the Internet of things equipment to be managed until the history scanning result does not comprise the target equipment information.

In an alternative embodiment, the method further comprises:

If the connection between the device association node and the current edge node is detected to be in a disconnection state, and the disconnection time is longer than a preset time threshold, determining a target edge node from a set of pre-stored device association nodes corresponding to the to-be-managed Internet of things device, wherein the scanning result corresponding to each edge node in the set of device association nodes comprises target device information;

And managing the Internet of things equipment to be managed through the target edge node.

In an alternative embodiment, the method further comprises:

and if the connection with the current edge node is detected to be in the connection state again, the internet of things equipment to be managed is managed again through the current edge node.

In an alternative embodiment, the node access command comprises a bulk access command for allowing simultaneous or sequential access of multiple edge nodes into the cloud.

In a second aspect, the present invention provides a device management method, applied to an edge node, where the method includes:

Responding to a received node access command sent by a cloud end, and establishing a connection relation with the cloud end, wherein the node access command is used for requesting to establish connection with an edge node under a target communication network;

receiving a target device scanner sent by a cloud through a connection relation;

The method comprises the steps of determining the to-be-managed Internet of things equipment through a target equipment scanner, and sending a scanning result of the to-be-managed Internet of things equipment to a cloud end to acquire equipment data of the to-be-managed Internet of things equipment.

The beneficial effects are that: according to the device management method, the edge node can be automatically connected with the cloud, and the target device scanner sent by the cloud has the identification capability of the device of the Internet of things to be managed, so that human intervention can be reduced in the process of managing the device of the Internet of things to be managed by the cloud through the edge node, and the device management efficiency is improved.

In an optional implementation manner, determining, by the target device scanner, the internet of things device to be managed, and sending a scan result of the internet of things device to be managed to the cloud, including:

Operating a target device scanner through a preset configuration file to determine the Internet of things device to be managed;

If the Internet of things equipment to be managed is scanned, acquiring target equipment information of the Internet of things equipment to be managed through a preset equipment discovery template, and obtaining a scanning result;

And sending the scanning result to the cloud.

In an alternative embodiment, the method further comprises:

receiving a target data collector sent by a cloud;

Acquiring equipment data of the to-be-managed Internet of things equipment through a target data acquisition device according to a binding relation between the to-be-managed Internet of things equipment and the to-be-managed Internet of things equipment;

And sending the device data to the cloud so that the cloud manages the to-be-managed Internet of things device according to the device data.

In a third aspect, the present invention provides a device management apparatus, applied to a cloud, where the device includes:

the first acquisition module is used for sending a node access command, wherein the node access command is used for requesting to establish connection with an edge node under a target communication network;

The first sending module is used for responding to the fact that the current edge node is accessed, sending the target equipment scanner to the current edge node, and enabling the current edge node to determine the Internet of things equipment to be managed according to the scanning result of the target equipment scanner;

The first control module is used for controlling the current edge node to collect the equipment data of the to-be-managed Internet of things equipment based on the scanning result sent by the current edge node so as to manage the to-be-managed Internet of things equipment.

In a fourth aspect, the present invention provides an apparatus for device management, applied to an edge node, the apparatus comprising:

The connection module is used for responding to a received node access command sent by the cloud end, establishing a connection relation with the cloud end, wherein the node access command is used for requesting to establish connection with an edge node under a target communication network;

the first receiving module is used for receiving the target equipment scanner sent by the cloud through the connection relation;

the second sending module is used for determining the to-be-managed internet of things equipment through the target equipment scanner and sending a scanning result of the to-be-managed internet of things equipment to the cloud end so as to acquire equipment data of the to-be-managed internet of things equipment.

In a fifth aspect, the present invention provides a computer device comprising: the device management system comprises a memory and a processor, wherein the memory and the processor are in communication connection, the memory stores computer instructions, and the processor executes the computer instructions to execute the device management method of the first aspect or any corresponding embodiment or execute the device management method of the second aspect or any corresponding embodiment.

In a sixth aspect, the present invention provides a computer-readable storage medium having stored thereon computer instructions for causing a computer to execute the device management method of the first aspect or any one of the embodiments corresponding thereto or to execute the device management method of the second aspect or any one of the embodiments corresponding thereto.

Drawings

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings that are needed in the description of the embodiments or the prior art will be briefly described, and it is obvious that the drawings in the description below are some embodiments of the present invention, and other drawings can be obtained according to the drawings without inventive effort for a person skilled in the art.

FIG. 1 is a schematic diagram of an architecture diagram according to an associated device management system;

FIG. 2 is a flow chart of a device management method according to an embodiment of the invention;

FIG. 3 is a flow chart of another device management method according to an embodiment of the invention;

FIG. 4 is a flow chart of yet another device management method according to an embodiment of the present invention;

FIG. 5 is a flow chart of yet another device management method according to an embodiment of the present invention;

FIG. 6 is a schematic diagram of an architecture of a device management system according to an embodiment of the present invention;

fig. 7 is a block diagram of a device management apparatus according to an embodiment of the present invention;

FIG. 8 is a block diagram of another device management apparatus according to an embodiment of the present invention;

fig. 9 is a schematic diagram of a hardware structure of a computer device according to an embodiment of the present invention.

Detailed Description

For the purpose of making the objects, technical solutions and advantages of the embodiments of the present invention more apparent, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention, and it is apparent that the described embodiments are some embodiments of the present invention, but not all embodiments of the present invention. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.

In the related art, an architecture diagram of a device management system for managing an internet of things device to be managed through a cloud may be as shown in fig. 1. The device management system comprises: cloud, a plurality of edge nodes and a plurality of internet of things devices to be managed. The numbers in the figures are only used for distinguishing different edge nodes or internet of things devices, and are not meant to represent numbers. The internet of things device to be managed includes, but is not limited to, the following device types: intelligent household equipment, intelligent health equipment, industrial to-be-managed Internet of things equipment, agricultural to-be-managed Internet of things equipment and the like. The number of internet of things devices to be managed may be different from the number of edge nodes. In order to facilitate cloud management of the to-be-managed internet of things equipment, a binding relationship between the edge node and the to-be-managed internet of things equipment is manually established on the cloud side by related personnel, and then the corresponding to-be-managed internet of things equipment is managed through the edge node according to the binding relationship. However, when the number of the to-be-managed internet of things devices is large and the number of the edge nodes is also large, the binding process is complicated and is easy to make mistakes, and if the to-be-managed internet of things devices are still managed in a manual mode, the device management efficiency is seriously affected.

In view of this, an embodiment of the present invention provides a device management method applied to a cloud, which sends a node access command, so that an edge node under the same network can actively connect to the cloud according to the received node access command, and further send a target device scanner to a current edge node when determining that the current edge node is accessed, so that the current edge node determines an internet of things device to be managed according to a scanning result of the target device scanner. Based on the scanning result sent by the current edge node, the current edge node is controlled to collect the equipment data of the to-be-managed Internet of things equipment, so that the cloud can autonomously find the to-be-managed Internet of things equipment to be managed, further, manual intervention is not needed, the to-be-managed Internet of things equipment can be managed automatically, and therefore equipment management efficiency can be effectively improved.

According to an embodiment of the present invention, there is provided an apparatus management method embodiment, it being noted that the steps shown in the flowcharts of the drawings may be performed in a computer system such as a set of computer executable instructions, and that although a logical order is shown in the flowcharts, in some cases the steps shown or described may be performed in an order different from that herein.

In this embodiment, a device management method is provided, which may be used for a cloud end with centralized hosting and management of cloud computing services, for example: fig. 2 is a flowchart of a device management method according to an embodiment of the present invention, as shown in fig. 2, including the following steps:

step S201, a node access command is sent.

In the embodiment of the invention, the node access command is used for requesting to establish connection with an edge node under the target communication network. In order to facilitate the edge node under the target communication network to be capable of being automatically connected with the cloud, the cloud generates a node access command internally and sends the node access command, so that the edge node under the target communication network can respond according to the received node access command, and connection can be actively established with the cloud. In an example, the node access command may be sent by way of broadcasting. For example: the node access command is periodically sent in a broadcast mode, and when a new edge node enters the network, the edge node can be guided to be actively connected with the cloud in time in a mode of sending the node access command, so that the connection efficiency is improved. In another example, the generated node access command may be sent to an edge node deployed under the same target communication network by means of point-to-point sending, so that it can establish a connection with the cloud end under the target communication network. For example: in order to ensure the sending effectiveness of the node access command, after the edge node is placed at a proper edge position in advance and a target communication network between the cloud terminal and the power-on configuration is well established, the cloud terminal sends the node access command, so that the edge node under the target communication network can receive the node access command. Wherein the network type of the target communication network may not be unique, for example: may include wired networks, wireless networks, local area networks, satellite networks, sensor networks, and the like.

Step S202, responding to the access of the current edge node, and sending the target equipment scanner to the current edge node so that the current edge node determines the to-be-managed Internet of things equipment according to the scanning result of the target equipment scanner.

In the embodiment of the invention, after the current edge node is accessed, the characterization can manage the to-be-managed internet of things equipment connected with the current edge node through the current edge node. Therefore, in order to enable the current edge node to autonomously scan and discover the to-be-managed internet of things equipment connected with the current edge node, the target equipment scanner is sent to the current edge node, so that the current edge node can quickly discover the to-be-managed internet of things equipment through the target equipment scanner. The to-be-managed internet of things equipment refers to the internet of things equipment to be managed which is newly added or is in communication with the current edge node. The target device scanner may be understood as a device scanner corresponding to the current edge node, and is configured to scan whether there is an internet of things device to be managed, which is connected to the current edge node and needs to be managed.

In some optional examples, the target device scanner may be a tool or program with a function of scanning for the internet of things to be managed, and may discover and identify the internet of things device to be managed connected to the current edge node by scanning for a specified local area network address or a serial port of the current edge node.

Step S203, based on the scan result sent by the current edge node, controls the current edge node to collect device data of the internet of things device to be managed, so as to manage the internet of things device to be managed.

In the embodiment of the invention, according to the scanning result sent by the current edge node, the existence of the to-be-managed Internet of things equipment which is connected with the current edge node and needs to be managed can be determined, so that the current edge node is controlled to collect the equipment data of the to-be-managed Internet of things equipment so as to determine the running condition of the to-be-managed Internet of things equipment through the equipment data, and the management effectiveness is improved.

According to the device management method provided by the embodiment, the cloud terminal can enable the edge node under the same network to be automatically connected with the cloud terminal through the transmitted node access command, and further after connection is established with the current edge node, the target device scanner is transmitted to the current edge node, so that the current edge node can have the capability of automatically identifying the device of the internet of things to be managed, the current edge node is controlled to acquire the device data of the device of the internet of things to be managed according to the scanning result uploaded by the current edge node, the cloud terminal can be enabled to automatically manage the device of the internet of things to be managed without manual intervention, and the device management efficiency can be effectively improved.

In this embodiment, a device management method is provided, which may be used for the cloud end with centralized hosting and management of cloud computing services, for example: fig. 3 is a flowchart of a device management method according to an embodiment of the present invention, as shown in fig. 3, including the steps of:

step S301, a node access command is sent. Please refer to step S201 in the embodiment shown in fig. 2 in detail, which is not described herein.

Step S302, responding to the fact that the current edge node is accessed, sending the target equipment scanner to the current edge node, and enabling the current edge node to determine the to-be-managed Internet of things equipment according to the scanning result of the target equipment scanner.

Specifically, the step S302 includes:

In step S3021, node information of the current edge node is acquired in response to the current edge node being accessed.

In the embodiment of the invention, in order to determine the currently accessed edge node, after determining that the current edge node is accessed, node information of the edge node is acquired so as to carry out targeted communication and management on the current edge node through the node information. The node information includes, but is not limited to, the following: the unique identifier of the edge node, the internet protocol address (Internet Protocol Address, IP address) to which it belongs), the operating system, hardware specifications, connection speed, etc.

Step S3022, determining a target device scanner corresponding to the current edge node from among a preset plurality of device scanners based on the node information.

In the embodiment of the invention, in order to ensure that the device scanner issued to the current edge node can effectively identify the to-be-managed Internet of things device, the running condition of the current edge node is defined based on the node information, and then a target device scanner suitable for the current edge node is selected from a plurality of preset device scanners, so that the scanning accuracy and the scanning effectiveness of the to-be-managed Internet of things device are improved.

In some optional implementation scenarios, taking any node in the edge node K8S as an example, the target device scanner is configured to discover an internet of things device of a corresponding access protocol. The target device scanner to be issued may be a container image stored in a cloud image repository developed based on a third party. Defining a custom resource definition (Custom Resource Definition, CRD) resource template in K8S to represent scanner template and Internet of things Discovery (Discovery), wherein each CRD instance represents a scanner plug-in, and filling access protocol, container mirror image, scanning parameters and the like into CRD instance. When the target device scanner issues, the container mirror image is issued to the edge node according to the CRD instance information, the container instance is operated, and meanwhile, the scanning parameters are bound into the container instance in the form of configmap (a resource object for storing configuration data) for scanning configuration. A CRD template resource of the scan result is defined in K8S, for example IoTResult, including access protocol, connection information, reporting edge node list, etc.

In some alternative embodiments, step S3022 includes:

step a1, determining the node identification of the current edge node according to the node information.

In this manner, in order to determine whether the current edge node can autonomously determine the internet of things device to be managed, a node identifier of the current edge node is determined from the node information, so as to determine the validity of the current edge node through the node identifier. Because the node identifiers have uniqueness, the occurrence of false recognition is reduced by screening the node identifiers.

In some alternative examples, the node identifier may be an internet protocol address, a node name of the current edge node, and may effectively identify the specific identifier of the current edge node.

Step a2, detecting whether the node identifier is a legal identifier or not through a preset access control list.

In this manner, to facilitate a quick determination of whether to send the device scanner to the current edge node, detection is performed via a preset access control list. Wherein the access control list may access a white list or a black list. The access control list includes a plurality of controlled node identifiers, and when detecting whether the node identifiers are legal identifiers, the access control list can be determined based on a matching result between the node identifiers and the plurality of controlled node identifiers.

For example: if the access control list is the access white list, the multiple controlled node identifiers are legal node identifiers. And if the node identifier is included in the plurality of controlled node identifiers, determining that the node identifier is a legal identifier. If the access control list is the access blacklist, the multiple controlled node identifiers are illegal identifiers. And if the node identifier is included in the plurality of controlled node identifiers, determining that the node identifier is illegal.

And a3, if the node identifier is a legal identifier, determining a target device scanner corresponding to the current edge node from a plurality of preset device scanners.

In the mode, if the node identifier is a legal identifier, the current edge node is characterized to be trusted, and then a target device scanner corresponding to the current edge node is determined from a plurality of preset device scanners, so that the current edge node can autonomously scan the to-be-managed Internet of things device connected with the current edge node according to the received target device scanner.

In some optional embodiments, step S3022 above further includes:

And a4, if the node identification is illegal identification, determining a corresponding target device scanner from a plurality of preset device scanners for the current edge node.

In this manner, if the node identifier is an illegal identifier, the node identifier is not trusted with the current edge node, so that, in order to improve the security of device management, a corresponding target device scanner is not determined from a plurality of preset device scanners for the current edge node, so that the current edge node cannot autonomously scan the to-be-managed internet of things device connected with the current edge node.

In other optional embodiments, the step S3022 includes:

Step b1, determining a target equipment type corresponding to a current edge node according to node information;

And b2, if the device scanner corresponding to the target device type exists in the plurality of device scanners, taking the device scanner corresponding to the target device type as the target device scanner.

Specifically, because the device protocols applied to the to-be-managed internet of things devices of different device types have differences, in order to reasonably issue the device scanner and avoid excessive waste of transmission resources, the device protocol corresponding to the to-be-managed internet of things device which can be accessed by the current edge node is determined according to the node information, and then the target device type corresponding to the current edge node is determined according to the device protocol. Each device scanner supports device discovery rules of at least one device protocol, so that the device scanners can communicate with the to-be-managed internet of things devices supporting the same device protocol correspondingly and acquire device information.

After determining the type of the target equipment, the type of the target equipment is respectively matched with the equipment types of all the equipment scanners, and the equipment scanner with the same equipment type as the target equipment type is used as the target equipment scanner, so that when the subsequent current edge node scans equipment through the target equipment scanner, the occurrence of invalid scanning can be effectively reduced, the scanning performance of the target equipment scanner is improved, and the purpose of reasonably utilizing the target equipment scanner can be achieved.

In some alternative implementation scenarios, the target device type may include, but is not limited to, any one or more of the following device types: intelligent household equipment, intelligent health equipment, industrial Internet of things equipment, intelligent traffic equipment and agricultural Internet of things equipment.

Wherein, intelligent house equipment can include: intelligent bulb, smart jack, intelligent door lock, intelligent camera etc.. Device protocols involved with smart home devices include, but are not limited to: wi-Fi protocol (a wireless network communication protocol), zigbee (a low power, low rate wireless communication protocol), Z-Wave (a wireless communication protocol focused on smart home), and the like.

The intelligent health device may include: intelligent wrist-watch, intelligent bracelet, intelligent weighing scale etc.. Device protocols involved with smart home devices include, but are not limited to: bluetooth (a short range wireless communication protocol), ant+ protocol (a wireless communication protocol that focuses on interconnecting health and sports equipment), and the like.

The industrial internet of things device may include: sensor, machine monitoring equipment, unmanned aerial vehicle, etc. Device protocols involved in industrial internet of things devices include, but are not limited to: message queue telemetry transport protocol (Message Queuing Telemetry Transport, MQTT), OPC UA (OLE for Process Control Unified Architecture, a communication protocol and data model), modbus (a communication protocol for connecting and exchanging data in automation and industrial control systems), and the like.

The intelligent transportation device may include: intelligent parking systems, intelligent traffic lights, intelligent vehicle tracking systems, etc. Device protocols involved in intelligent transportation devices include, but are not limited to: cellular V2X (Vehicle-to-evaluation, a Cellular network-based internet of vehicles communication protocol), dedicated short range communication technology (DEDICATED SHORT RANGE COMMUNICATIONS, DSRC), open network video interface forum (Open Network Video Interface Forum, ONVIF), and the like.

The agricultural internet of things device may include: soil humidity sensor, meteorological monitoring device, intelligent irrigation system etc.. Device protocols involved in agricultural internet of things devices include, but are not limited to: loRaWAN (Long RANGE WIDE AREA Network, a low power consumption wide area Internet of things communication protocol based on LoRa technology), narrowband Internet of things (Narrowband Internet of Things, NB-IoT).

In other alternative embodiments, the number of the target device types is plural, and the step S2022 further includes:

and b3, if the device scanner corresponding to the target device type does not exist in the device scanners, updating the device scanners based on the target device type.

In this manner, if there is no device scanner corresponding to the target device type in the plurality of device scanners, the device scanner in the characterization cloud is still not perfect, so in order to improve the effectiveness of device management, the plurality of device scanners are updated, so that the updated plurality of device scanners include the device scanner with the target device type.

In some examples, the updating may be performed by altering a device protocol supported by the device scanner such that the device type corresponding to the altered device scanner includes the target device type.

In other examples, the updating is performed by augmenting, and adding a device scanner corresponding to the target device type to the plurality of device scanners. For example, a new device scanner may be augmented by a configuration file. The configuration file includes the device parameters corresponding to the newly added device scanner. For example: the scan port parameters are configured in the configuration file for a device scanner with device protocol of ONVIF, and the topic parameters (a transmission medium for defining channels and paths for message transmission) are configured in the configuration file for a device scanner with device protocol of MQTT.

In still other examples, if there is a device scanner that is not used beyond a certain time threshold in the plurality of device scanners, to avoid wasting resources, the device scanner that is not used beyond the certain time threshold is deleted from the plurality of device scanners, so that the cloud can reasonably supervise the plurality of device scanners.

In some alternative embodiments, the target device type corresponding to the current edge node depends on the current edge node group in which the current edge node is located, and the target device types corresponding to different current edge node groups are not identical. The type of the target device corresponding to the edge node is determined in a grouping mode, so that the target device scanner which needs to be sent to the current edge device can be determined quickly, and further the efficiency of targeted management of the Internet of things device to be managed is improved.

In still other alternative embodiments, step S3022 includes:

step c1, determining a target network segment where a current edge node is located according to node information;

Step c2, detecting whether an associated edge node communicated with the current edge node exists in the connected edge nodes corresponding to the target network segment through a preset node scanner;

and c3, if the connected edge nodes have associated edge nodes and the associated edge nodes comprise deployed device scanners, taking the deployed device scanners as target device scanners corresponding to the current edge nodes.

Specifically, the deployed device scanner is a target edge device of the plurality of device scanners that corresponds to the associated edge node. In order to save bandwidth traffic between the cloud and the edge node, determining a target network segment where the current edge node is located according to node information, so as to determine an associated edge node which is in mutual communication with the current edge node in the same network segment through the target network segment.

After determining the target network segment, detecting the corresponding connected edge nodes of the target network segment through a preset node scanner to determine whether the connected edge nodes have associated edge nodes communicated with the current edge node. When the existence of the associated node is detected, the deployed device scanner is used as a target device scanner corresponding to the current edge node, so that the current edge node is controlled to acquire the required target device scanner from the associated edge node in order to effectively save the bandwidth flow between the cloud end and the edge node, and further the efficiency of the target device scanner is improved.

In some examples, the associated edge node is detected by a node scanner through a pre-set list of target internet protocol addresses (Internet Protocol address, IP ADDRESS). The target internet protocol address list comprises a plurality of edge nodes which correspond to the target network segments and are communicated with each other. That is, after the current edge node is actively connected to the cloud, the cloud determines a target network segment corresponding to the current edge node according to node information of the current edge node, further determines a target internet protocol address list corresponding to the target network segment from a plurality of preset internet protocol address lists, and adds the IP of the current edge node into the target internet protocol address list, so that the target internet protocol address list includes the IP of at least one edge node. Since the IP of each edge node in the target internet protocol address list is the same target network segment, when the target internet protocol address list includes the IP of a plurality of edge nodes, each edge node in the target internet protocol address list is an associated edge node of each other.

In other examples, in order to save management resources of the cloud, when the target internet protocol address list includes two or more IPs belonging to the same target network segment, the target internet protocol address list is sent to the corresponding edge nodes along with the target device scanner, and then the target device scanner performs a ping operation (an operation for testing network connection and delay between the target device and the target host) on other edge nodes in the target internet protocol address list, determines that the edge nodes in the intercommunication belong to the edge nodes in the same network segment, and informs the test result to the cloud, so that the cloud can delete the last determined edge node IP from the target internet protocol address list, and repeat the steps until all edge nodes perform the ping operation, thereby avoiding the occurrence of the situation that the IPs in the target internet protocol address list are repeated and being beneficial to quickly improving the target internet protocol address list.

Step S3023, the target device scanner is sent to the current edge node.

In the embodiment of the invention, after the target equipment scanner is determined, the target equipment scanner is sent to the current edge node, so that the current edge node can determine the to-be-managed internet of things equipment through the target equipment scanner, and data of the to-be-managed internet of things equipment are acquired in a targeted manner.

By sending the target equipment scanner to the current edge node in the mode, the issuing validity of the equipment scanner is guaranteed, and the Internet of things equipment to be managed can be effectively identified, so that the effectiveness of the Internet of things equipment to be managed in cloud management is improved.

Step S303, based on the scanning result sent by the current edge node, controlling the current edge node to collect the device data of the to-be-managed Internet of things device so as to manage the to-be-managed Internet of things device.

Specifically, the scan result includes target device information of the internet of things device to be managed, and step S303 includes:

in step S3031, it is detected whether the acquired history scan result includes target device information.

In the embodiment of the invention, when the scanning result sent by the current edge node includes the target equipment information of the to-be-managed internet of things equipment, a new to-be-managed internet of things equipment connected with the current edge node is characterized. In order to avoid wasting management resources, whether the acquired historical scanning result comprises target equipment information is detected, so that repeated management is avoided. The obtained historical scan result may be a scan result uploaded by other edge nodes.

Step S3032, if the history scanning result does not include the target device information, a binding relationship between the current edge node and the Internet of things device to be managed is established.

In the embodiment of the invention, if the history scanning result does not include the target equipment information, the fact that the to-be-managed internet of things equipment does not have a connection relation with other edge nodes is characterized, and the cloud end does not manage the to-be-managed internet of things equipment, so that a binding relation between the current edge node and the to-be-managed internet of things equipment is established, and the to-be-managed internet of things equipment can be managed in a targeted manner according to the binding relation.

Step S3033, the target data collector is sent to the current edge node to control the current edge node to collect the device data of the to-be-managed Internet of things device through the target data collector.

In the embodiment of the invention, in order to acquire the equipment data of the internet of things to be managed, the target data collector is sent to the current edge node so that the current edge node has the equipment data collection capability, and thus targeted collection is performed.

Specifically, according to target equipment information, determining a target data collector corresponding to an access protocol of the to-be-managed internet of things equipment from a plurality of preset data collectors, and sending the target data collector, registration information of the to-be-managed internet of things equipment and acquisition template information corresponding to the to-be-managed internet of things equipment to a current edge node, so that the target data collector is connected with the to-be-managed internet of things equipment based on connection information in the registration information, and equipment data acquisition is performed based on an acquisition template.

Wherein the registration information includes, but is not limited to: an equipment unique Identifier (ID), a name, a protocol, connection information, and the like of the internet of things equipment to be managed. If the device ID is not available, a unique ID is automatically generated. The device name may be composed of the current edge node name + device protocol + random characters. Some protocols do not need user name and password during scanning but need registration, for example, the ONVIF protocol can define a mechanism for adding additional parameters, and when the scanning result template is converted into the registration template, the additional parameters customized by the cloud user are automatically injected into the registration template.

The content in the acquisition template includes, but is not limited to: the access protocol, attribute name and attribute collection mode corresponding to the internet of things equipment to be managed are different in attribute and collection mode of different protocols, can be customized, and are not limited herein. In order to improve the configuration efficiency of the preset acquisition template, the same acquisition template can be configured for the internet of things equipment to be managed of the same equipment type or a batch of internet of things equipment to be managed, which is applicable to the same application.

In some alternative implementations, the data collector may be a general purpose data collector suitable for a platform, such as Modbus, or the like. In K8S, a collector CRD template resource is defined, for example IoTCollect, and each CRD instance represents a data collector, and access protocol, container mirror image, device connection information, etc. are filled into the CRD instance. When an internet of things device is found to automatically register, ioTCollect instance information corresponding to a protocol is used for connecting the device, and then data acquisition is carried out by combining with a pre-configured acquisition template, so that required device data is obtained.

In some optional embodiments, the step S303 further includes:

Step S3034, if the history scanning result includes the target device information, the Internet protocol information of the current edge node is obtained.

In the embodiment of the invention, if the history scanning result includes the target device information, the to-be-managed internet of things device is characterized as being in a connection state with the current edge node and other edge nodes, and the to-be-managed internet of things device is in a managed state. Therefore, in order to improve the security of the device management, the internet protocol information of the current edge node is obtained, so that when the cloud end manages the to-be-managed internet of things device through other edge nodes, the management can be restored through the current edge node.

Step S3035, an association relation between the Internet protocol information and the target equipment information is established and stored, and the current edge node is controlled to acquire the equipment data of the Internet of things equipment to be managed until the history scanning result does not comprise the target equipment information.

In the embodiment of the invention, the association relation between the internet protocol information and the target equipment information is established and stored, so that the cloud can clearly determine that the to-be-managed internet of things equipment can be subjected to targeted management through the current edge, and further, when the history scanning result does not comprise the target equipment information, other edge equipment for representing and managing the to-be-managed internet of things equipment is disconnected with the to-be-managed internet of things equipment, therefore, in order to enable the cloud to continuously monitor the to-be-managed internet of things equipment, the current edge node is controlled to acquire equipment data of the to-be-managed internet of things equipment, and further, the safety and the effectiveness of management of the cloud are ensured.

According to the device management method provided by the embodiment, after the current edge node is actively connected to the cloud, the cloud can respectively send the target device scanner and the target data collector to the current edge node according to the connection state between the current edge node and the current edge node, so that the current edge node has the capability of automatically finding out the to-be-managed internet of things device and collecting the device data, the cloud can conduct targeted management through the to-be-managed internet of things device connected with the current edge node and the current edge node, manual intervention is not needed, management performance of the cloud can be effectively improved, and device management efficiency of the cloud is improved.

In some optional embodiments, the device management method further includes:

Step d1, if the connection between the current edge node and the current edge node is detected to be in a disconnection state, and the disconnection time is longer than a preset time threshold, determining a target edge node from a prestored equipment association node set corresponding to the to-be-managed Internet of things equipment;

And d2, managing the Internet of things equipment to be managed through the target edge node.

Specifically, in order to ensure the integrity of the device data, the connection state between the current edge node and the current edge node is monitored in real time in the process of establishing connection with the current edge node. When the connection state between the current edge node and the current edge node is detected to be in the disconnection state, determining the disconnection time length, and determining whether the switching target edge node is required to take over the to-be-managed Internet of things equipment according to the disconnection time length.

In order to determine whether the current edge node has a fault, a time threshold is preset to judge that the current edge node automatically restores the fault through the time threshold. If the disconnection time is longer than a preset time threshold, the connection between the cloud end and the current edge node is characterized as abnormal, and the current edge node cannot repair the fault autonomously, so that a target edge node is determined from a prestored equipment association node set corresponding to the to-be-managed Internet of things equipment, and the to-be-managed Internet of things equipment is managed through the target edge node. The time threshold may be determined based on averaging of user traffic demands or historical empirical data, without limitation.

The scan result corresponding to each edge node in the device association node set includes target device information, and when determining a target edge node, one edge node can be determined from the device association node set as the target edge node. In one example, since each edge node in the device association node is connected to the device to be managed, which is connected to the current edge node, in order to improve the determination efficiency of the target edge node, one edge node may be randomly selected from the device association node set as the target edge node. In another example, the target edge node may be an edge node that is designated in advance in the set of device association nodes, so that when determining the target edge node, the saving of filtering time may be improved. In another example, the edge node with the lowest load can be used as the target edge node based on the load condition of all edge nodes in the equipment association node set, so that the occurrence of the condition that disconnection occurs again can be reduced, and the stability of the equipment of the internet of things to be managed is guaranteed.

In other optional embodiments, the device management method further includes:

and d3, if the connection with the current edge node is detected to be in a connection state again, the internet of things equipment to be managed is managed again through the current edge node.

In the embodiment of the invention, if the connection with the current edge node is detected to be in the connection state again, the current edge node is characterized to be recovered to be normal and can be normally connected with the cloud, and then the internet of things equipment to be managed is managed again through the current edge node, so that the safety and reliability of equipment data are ensured.

In some examples, if the current edge node is offline, and the to-be-managed internet of things device connected with the current edge node is not offline, the target edge node for taking over the to-be-managed internet of things device is intensively determined from the device association node, and then the to-be-managed internet of things device is managed through the target edge node, so that the to-be-managed internet of things device is always in a state of being monitored by the cloud, and the integrity of device data is guaranteed.

In some optional embodiments, the node access command includes a bulk access command, where the bulk access command is used to allow multiple edge nodes to be accessed into the cloud end simultaneously or sequentially, thereby helping to improve connection efficiency. The generated node access command includes an access uniform resource location system (Uniform Resource Locator, URL), an access authentication information token (token), the number of nodes allowed to connect the edge nodes, the belonging group (optional) of each edge node and the validity period, so that when the batch access command is received by the corresponding edge nodes, the cloud terminal can be automatically connected by the edge nodes, and the connection efficiency of the cloud terminal and the edge nodes can be effectively improved. In an example, to ensure security of accessing the authentication information token, an access number limit and an access time range of the edge node are set, and an edge node unique device number list accessed through the token is set, so that the edge node which can be allowed to be actively accessed to the cloud is selected in a directional manner. The device number list may be self-defined and maintained, and may be specified when the token is generated.

Based on the same inventive concept, there is also provided in this embodiment a device management method, which may be used for the above edge node, and fig. 4 is a flowchart of the device management method according to an embodiment of the present invention, as shown in fig. 4, where the flowchart includes the following steps:

step S401, a connection relation is established with the cloud in response to receiving a node access command sent by the cloud.

In the embodiment of the invention, the node access command is used for requesting to establish connection with an edge node under the target communication network. When the edge node receives the node access command, the characterization is allowed to autonomously establish connection with the cloud, and then a connection relationship is established with the cloud.

In some examples, in order to enable the edge node to be autonomously connected to the cloud end, the edge node is placed in a proper edge position in advance, a communication network between the cloud end and the edge node is configured in a powered-on mode, and a node access command is generated and sent by an edge node management module preset in the cloud end. The edge node is internally provided with an edge access module which is used for responding to the receiving of the node access command by the edge node. And after receiving the node access instruction, the edge node responds by the edge access module, and establishes a connection relationship with the cloud through the edge access module.

In some optional implementation scenarios, a plurality of edge nodes may be placed in a certain local area, so as to perform data collection of the internet of things device with each other as a master, and further facilitate load balancing. Different edge nodes can collect device data of internet of things devices of different protocols.

In some optional implementation scenarios, the cluster where the edge node is located may be implemented based on a container and a Kubernetes open source technical framework, so that a management node of the Kubernetes cluster is pre-deployed in the cloud, and then a node access command is generated by an edge node management module in the management node, so that the edge node can respond to the node access command and be connected with the cloud autonomously.

Step S402, receiving a target device scanner sent by a cloud through a connection relation.

In the embodiment of the invention, in order to enable the cloud to perform targeted management on the to-be-managed internet of things equipment connected with the cloud, a target equipment scanner sent by the cloud is received through a connection relation between the cloud and the cloud, so that the to-be-managed internet of things equipment which is connected with the edge node and is not supervised by the cloud is identified through the target equipment scanner.

Step S403, determining the to-be-managed Internet of things equipment through the target equipment scanner, and sending a scanning result of the to-be-managed Internet of things equipment to the cloud to acquire equipment data of the to-be-managed Internet of things equipment.

In the embodiment of the invention, the target device scanner is operated so that the target device scanner can identify whether the to-be-managed Internet of things device which is connected with the edge node and is not regulated currently exists. When the to-be-managed internet of things equipment which is connected with the edge node and is not supervised is scanned, a scanning result is generated and sent to the cloud end, so that the cloud end is informed of the existence of a new to-be-managed internet of things equipment, and equipment data of the to-be-managed internet of things equipment can be collected.

According to the device management method, the edge node can be automatically connected with the cloud, and the target device scanner sent by the cloud has the identification capability of the device of the Internet of things to be managed, so that human intervention can be reduced in the process of managing the device of the Internet of things to be managed by the cloud through the edge node, and the device management efficiency is improved.

In this embodiment, a device management method is provided, which may be used for the edge node, and fig. 5 is a flowchart of a device management method according to an embodiment of the present invention, as shown in fig. 5, where the flowchart includes the following steps:

Step S501, in response to receiving the node access command sent by the cloud, a connection relationship is established with the cloud. Please refer to step S401 in the embodiment shown in fig. 4 in detail, which is not described herein.

Step S502, receiving a target device scanner sent by a cloud through a connection relation. Please refer to step S402 in the embodiment shown in fig. 4 in detail, which is not described herein.

In step S503, the internet of things device to be managed is determined by the target device scanner, and the scan result of the internet of things device to be managed is sent to the cloud end, so as to collect the device data of the internet of things device to be managed.

Specifically, the step S503 includes:

In step S5031, the target device scanner is operated through a preset configuration file to determine the internet of things device to be managed.

In the embodiment of the invention, in order to enable the target equipment scanner to normally operate in the edge node, a configuration file capable of controlling the target equipment scanner to operate is preset, so that the target equipment scanner can conduct targeted scanning on the Internet of things equipment to be managed according to the configuration file, and an effective scanning result is obtained.

Step S5032, if the internet of things device to be managed is scanned, obtaining target device information of the internet of things device to be managed through a preset device discovery template, and obtaining a scanning result.

In the embodiment of the invention, in order to facilitate efficient management in the cloud and quickly understand the target device information of the internet of things device to be managed, the device discovery template is pre-configured, and then after the internet of things device to be managed is scanned, the target device information of the internet of things device to be managed can be acquired according to the device discovery template, so that a corresponding scanning result is obtained. Among other things, the device discovery templates include, but are not limited to, those related to the following device information content: the device ID of the internet of things device to be managed, the access protocol used when accessing the edge node, the connection address, the list of discovered node names (including at least the node name of the edge node currently connected with the internet of things device to be managed).

In step S5033, the scanning result is sent to the cloud.

According to the device management method provided by the embodiment, after the edge node is actively connected with the cloud, the to-be-managed internet of things device to be managed in the cloud can be automatically identified according to the target device scanner issued by the cloud, and then target device information of the newly accessed to-be-managed internet of things device to be managed is sent to the cloud as a scanning result, so that the cloud can manage the to-be-managed internet of things device more conveniently and efficiently.

In some optional embodiments, when the target device scanner is in a stable running state, the target device scanner can be controlled to perform periodic scanner, and then when the edge node has the newly accessed to-be-managed internet of things device, a scanning result can be found and generated in time, so that the cloud end can be helped to improve the efficiency of managing the newly accessed to-be-managed internet of things device.

In some optional embodiments, the device management method further includes:

Step S504, receiving a target data collector sent by the cloud.

In the embodiment of the invention, when the cloud confirms that the to-be-managed internet of things equipment is managed, the target data collector is sent to the edge node, so that the edge node can collect the equipment data of the to-be-managed internet of things equipment according to the received target data collector, and the cloud can manage the internet of things equipment through the edge node in a targeted mode.

Step S505, according to the binding relation with the Internet of things equipment to be managed, acquiring the equipment data of the Internet of things equipment to be managed through the target data acquisition device.

According to the embodiment of the invention, according to the binding relation between the edge node and the to-be-managed Internet of things equipment, the to-be-acquired equipment data can be definitely acquired, and further, when the received target data acquisition device is used for acquiring the to-be-managed equipment data of the to-be-managed Internet of things equipment, the effectiveness of data acquisition can be ensured, so that the ineffective acquisition condition can be avoided.

Step S506, the device data is sent to the cloud end, so that the cloud end manages the to-be-managed Internet of things device according to the device data.

In the embodiment of the invention, the acquired equipment data is sent to the cloud so that the cloud can determine the running condition of the to-be-managed Internet of things equipment according to the acquired equipment data, and the cloud is further facilitated to conduct targeted management on the to-be-managed Internet of things equipment, so that the reliability of the cloud in managing the Internet of things equipment is improved.

Through the mode, the device data of the to-be-managed Internet of things device can be acquired in a targeted manner based on the binding relation between the edge node and the to-be-managed Internet of things device, so that the cloud can manage the to-be-managed Internet of things device in a targeted manner through the edge node, and the reliability of management of the to-be-managed Internet of things device by the cloud can be effectively improved.

Based on the same inventive concept, the present embodiment also provides a device management system to perform any one of the above device management methods. As shown in fig. 6, the device management system includes the following modules: cloud 610, a plurality of edge nodes 620, and a plurality of internet of things devices 630.

The cloud end deploys a scanner management module 611, an edge node management module 612, an internet of things device management module 613, and a collector management module 614. The edge node 620 includes an edge node access module 621 and an internet of things device edge management module 622.

The edge node management module 612 is configured to issue node access commands to the plurality of edge nodes 620, so that the plurality of edge nodes 620 can access the cloud end in batches through the edge node access module 621 according to the received node access commands.

The scanner management module 611 is configured to issue a corresponding target device scanner 623 to an edge node 620 connected to the cloud. The target device scanner 623 is configured to identify whether the edge node where the target device scanner locates has a newly accessed to-be-managed internet of things device 630, and upload the scanning result to the internet of things device management module 613 through the internet of things device edge management module 622, so that the cloud can obtain the scanning result, and further perform targeted management on the to-be-managed internet of things device 630.

The collector management module 614 is configured to issue a corresponding target data collector 624 to an edge node 620 connected to the cloud. The target data collector 624 is configured to collect device data of the internet of things device to be managed in the corresponding edge node, and upload the obtained device data to the internet of things device management module 613 through the internet of things device edge management module 622, so that the cloud end 610 can determine an operation state of the internet of things device 630 to be managed according to the uploaded device data.

Referring to fig. 6, as one or more specific application embodiments of the present invention, a process of managing an internet of things device to be managed through a cloud may be as follows:

The edge node 620 accesses the cloud 610 through an edge node management module 612 in the cloud 610. The scanner management module 611 automatically issues the target device scanner 623 to the current edge node 620 after it finds that the current edge node 620 is accessed. The current edge node 620 controls the target device scanner 623 to operate, so that the target device scanner 623 discovers the to-be-managed internet of things device 630 connected with the current edge node 620, and reports the obtained scanning result to the internet of things device management module 613 of the cloud through the internet of things device edge management module 622, so that the cloud 610 can automatically complete registration of the internet of things device according to the scanning result. After registration, the collector management module 614 automatically issues the target data collector 624 to the current edge node 620 according to the protocol, completes data collection, and the collected data is reported to the internet of things device management module 613 of the cloud through the internet of things device edge management module 622 for storage and display.

The target device scanner may be a container image stored in a cloud image repository developed based on a third party. Defining a custom resource definition (Custom Resource Definition, CRD) resource template in K8S to represent scanner template and Internet of things Discovery (Discovery), wherein each CRD instance represents a scanner plug-in, and filling access protocol, container mirror image, scanning parameters and the like into CRD instance. When the target device scanner issues, the container mirror image is issued to the edge node according to the CRD instance information, the container instance is operated, and meanwhile, the scanning parameters are bound into the container instance in the form of configmap (a resource object for storing configuration data) for scanning configuration. A CRD template resource of the scan result is defined in K8S, for example IoTResult, including access protocol, connection information, reporting edge node list, etc.

In order to enable the cloud internet of things device management module 613 to automatically register the internet of things device according to the received scanning result, a IoTDevice CRD resource template is predefined, including device connection information, state, attribute collection information and familiar real-time values, and a IoTResult CRD resource template is defined to represent the scanning result of the device. Creating a IoTDevice instance, registering on behalf of a physical internet of things device, and filling IoTResult content into the connection information of the IoTDevice instance, thereby registering.

The data collector may be a general purpose data collector suitable for a platform, such as Modbus or the like. In K8S, a collector CRD template resource is defined, for example IoTCollect, and each CRD instance represents a data collector, and access protocol, container mirror image, device connection information, etc. are filled into the CRD instance. When an internet of things device is found to automatically register, ioTCollect instance information corresponding to a protocol is used for connecting the device, and then data acquisition is carried out by combining with a pre-configured acquisition template, so that required device data is obtained.

In order to realize data collection, an attribute data collection template IoTProperties is defined in the K8S, including the attribute name to be collected, the collection mode, different protocols, and the same protocol may also define different collection templates. When the collector issues to the edge node, the collection template and the connection information in the IoT collection are issued together as configuration, and are implemented through configmap of K8S and mounted to the collector. The edge node runs the container instance, and the attribute data defined in the acquired template is reported to the central terminal.

After the target data collector 624 collects the device data, the device data is placed in a message queue of the internet of things device edge management module 622, the internet of things device edge management module 622 monitors the message queue message, and then the device data is reported to the internet of things device management module 613 in the cloud.

The internet of things device management module 613 fills the obtained device data into the IoTDevice resources, and stores the data in a time sequence database in the form of historical data, for example, prometheus, reads the data in IoTDevice for page display, and reads the historical data display history curve in prometheus.

Through the device management system provided by the disclosure, the cloud can automatically discover, register and bind the internet of things devices with different protocols, and data acquisition is completed. In addition, in the management process, the data is reported to the cloud end with high reliability through cooperation of the multi-edge nodes, so that the whole process is fully automatic, the management complexity and error rate are greatly reduced, and the management efficiency is improved.

In some optional implementation scenes, the device management system provided by the disclosure is suitable for automatic discovery, life cycle management and real-time data acquisition and display of mass internet of things devices, and meets the scene of unified management of mass internet of things devices with different protocols, so that the problems of heavy task, complex configuration, low efficiency and the like faced when the devices are effectively and manually registered and managed are solved.

In this embodiment, an apparatus for device management is further provided, and this apparatus is used to implement the foregoing embodiments and preferred embodiments, and will not be described in detail. As used below, the term "module" may be a combination of software and/or hardware that implements a predetermined function. While the means described in the following embodiments are preferably implemented in software, implementation in hardware, or a combination of software and hardware, is also possible and contemplated.

The embodiment provides a device management apparatus applied to a cloud, as shown in fig. 7, including:

a first obtaining module 701, configured to send a node access command, where the node access command is used to request to establish a connection with an edge node under a target communication network;

a first sending module 702, configured to send, in response to the current edge node being accessed, the target device scanner to the current edge node, so that the current edge node determines, according to a scanning result of the target device scanner, an internet of things device to be managed;

The first control module 703 is configured to control, based on a scan result sent by the current edge node, the current edge node to collect device data of the internet of things device to be managed, so as to manage the internet of things device to be managed.

In some alternative embodiments, the first transmitting module 702 includes: the first acquisition unit is used for responding to the accessed current edge node and acquiring node information of the current edge node; a screening unit for determining a target device scanner corresponding to the current edge node from a plurality of preset device scanners based on the node information; and the first sending unit is used for sending the target equipment scanner to the current edge node.

In some alternative embodiments, the screening unit comprises: the first determining unit is used for determining the node identification of the current edge node according to the node information; the first detection unit is used for detecting whether the node identifier is a legal identifier or not through a preset access control list; and the first screening unit is used for determining a target device scanner corresponding to the current edge node from a plurality of preset device scanners if the node identifier is legal identifier.

In some alternative embodiments, the screening unit further comprises: and the second screening unit is used for determining a corresponding target device scanner from a plurality of preset device scanners for the current edge node if the node identifier is an illegal identifier.

In some optional embodiments, different device scanners are used to scan for different device types of internet of things devices to be managed; the screening unit includes: the second determining unit is used for determining the type of the target equipment corresponding to the current edge node according to the node information; and the third screening unit is used for taking the device scanner corresponding to the target device type as the target device scanner if the device scanner corresponding to the target device type exists in the device scanners.

In some optional embodiments, the number of target device types is a plurality, and the screening unit further includes: and the updating unit is used for updating the plurality of device scanners based on the target device type if the device scanner corresponding to the target device type does not exist in the plurality of device scanners.

In some alternative embodiments, the target device type corresponding to the current edge node depends on the current edge node group in which the current edge node is located, and the target device types corresponding to different current edge node groups are not identical.

In some alternative embodiments, the screening unit comprises: the third determining unit is used for determining a target network segment where the current edge node is located according to the node information; the second detection unit is used for detecting whether the connected edge nodes corresponding to the target network segment have associated edge nodes communicated with the current edge node or not through a preset node scanner; and the fourth screening unit is used for taking the deployed equipment scanner as a target equipment scanner corresponding to the current edge node if the connected edge nodes have the associated edge nodes and the associated edge nodes comprise the deployed equipment scanner, wherein the deployed equipment scanner is the target edge equipment corresponding to the associated edge nodes in the plurality of equipment scanners.

In some alternative embodiments, the associated edge node is detected by the node scanner through a preset target internet protocol address list, where the target internet protocol address list includes a plurality of edge nodes corresponding to the target network segment and in communication with each other.

In some optional embodiments, the scan result includes target device information of the internet of things device to be managed, and the first control module 703 includes: a third detecting unit for detecting whether the acquired history scanning result includes target device information; the binding unit is used for establishing a binding relation between the current edge node and the Internet of things equipment to be managed if the history scanning result does not comprise the target equipment information; and the second sending unit is used for sending the target data collector to the current edge node so as to control the current edge node to collect the equipment data of the to-be-managed Internet of things equipment through the target data collector.

In some alternative embodiments, the first control module 703 further comprises: the second acquisition unit is used for acquiring the Internet protocol information of the current edge node if the history scanning result comprises the target equipment information; and the processing unit is used for establishing and storing the association relation between the Internet protocol information and the target equipment information, and controlling the current edge node to acquire the equipment data of the Internet of things equipment to be managed until the history scanning result does not comprise the target equipment information.

In some alternative embodiments, the apparatus further comprises: the node screening module is used for determining target edge nodes from a prestored equipment association node set corresponding to the to-be-managed internet of things equipment if the connection between the node screening module and the current edge node is detected to be in a disconnection state, and the disconnection time is longer than a preset time threshold value, wherein the scanning result corresponding to each edge node in the equipment association node set comprises target equipment information; and the second control module is used for managing the Internet of things equipment to be managed through the target edge node.

In some alternative embodiments, the apparatus further comprises: and the third control module is used for managing the Internet of things equipment to be managed through the current edge node again if the connection with the current edge node is detected to be in the connection state again.

In some alternative embodiments, the node access command comprises a bulk access command for allowing simultaneous or sequential access of multiple edge nodes into the cloud.

The present embodiment provides an apparatus management device applied to an edge node, as shown in fig. 8, including:

The connection module 801 is configured to establish a connection relationship with the cloud in response to receiving a node access command sent by the cloud, where the node access command is used to request establishment of connection with an edge node under the target communication network;

the first receiving module 802 is configured to receive, through a connection relationship, a target device scanner sent by a cloud;

The second sending module 803 is configured to determine, by using the target device scanner, an internet of things device to be managed, and send a scan result of the internet of things device to be managed to the cloud end, so as to collect device data of the internet of things device to be managed.

In some alternative embodiments, the second transmitting module 803 includes: the first execution unit is used for running the target equipment scanner through a preset configuration file so as to determine the equipment of the Internet of things to be managed; the scanning unit is used for acquiring target equipment information of the Internet of things equipment to be managed through a preset equipment discovery template if the Internet of things equipment to be managed is scanned, so as to obtain a scanning result; and the result sending unit is used for sending the scanning result to the cloud.

In some alternative embodiments, the apparatus further comprises: the second receiving module is used for receiving the target data collector sent by the cloud; the second acquisition module is used for acquiring the equipment data of the Internet of things equipment to be managed through the target data acquisition device according to the binding relation between the second acquisition module and the Internet of things equipment to be managed; the third sending module is used for sending the equipment data to the cloud end so that the cloud end can manage the to-be-managed Internet of things equipment according to the equipment data.

Further functional descriptions of the above respective modules and units are the same as those of the above corresponding embodiments, and are not repeated here.

The device management apparatus in this embodiment is presented in the form of a functional unit, where the unit refers to an ASIC (Application SPECIFIC INTEGRATED Circuit) Circuit, a processor and a memory that execute one or more software or firmware programs, and/or other devices that can provide the above functions.

The embodiment of the invention also provides computer equipment, which is provided with the equipment management device shown in the figure 7 or the figure 8.

Referring to fig. 9, fig. 9 is a schematic structural diagram of a computer device according to an alternative embodiment of the present invention, as shown in fig. 9, the computer device includes: one or more processors 10, memory 20, and interfaces for connecting the various components, including high-speed interfaces and low-speed interfaces. The various components are communicatively coupled to each other using different buses and may be mounted on a common motherboard or in other manners as desired. The processor may process instructions executing within the computer device, including instructions stored in or on memory to display graphical information of the GUI on an external input/output device, such as a display device coupled to the interface. In some alternative embodiments, multiple processors and/or multiple buses may be used, if desired, along with multiple memories and multiple memories. Also, multiple computer devices may be connected, each providing a portion of the necessary operations (e.g., as a server array, a set of blade servers, or a multiprocessor system). One processor 10 is illustrated in fig. 9.

The processor 10 may be a central processor, a network processor, or a combination thereof. The processor 10 may further include a hardware chip, among others. The hardware chip may be an application specific integrated circuit, a programmable logic device, or a combination thereof. The programmable logic device may be a complex programmable logic device, a field programmable gate array, a general-purpose array logic, or any combination thereof.

Wherein the memory 20 stores instructions executable by the at least one processor 10 to cause the at least one processor 10 to perform a method for implementing the embodiments described above.

The memory 20 may include a storage program area that may store an operating system, at least one application program required for functions, and a storage data area; the storage data area may store data created according to the use of the computer device, etc. In addition, the memory 20 may include high-speed random access memory, and may also include non-transitory memory, such as at least one magnetic disk storage device, flash memory device, or other non-transitory solid-state storage device. In some alternative embodiments, memory 20 may optionally include memory located remotely from processor 10, which may be connected to the computer device via a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.

Memory 20 may include volatile memory, such as random access memory; the memory may also include non-volatile memory, such as flash memory, hard disk, or solid state disk; the memory 20 may also comprise a combination of the above types of memories.

The computer device further comprises input means 30 and output means 40. The processor 10, memory 20, input device 30, and output device 40 may be connected by a bus or other means, for example by a bus connection in fig. 9.

The input device 30 may receive input numeric or character information and generate key signal inputs related to user settings and function control of the computer apparatus, such as a touch screen, a keypad, a mouse, a trackpad, a touchpad, a pointer stick, one or more mouse buttons, a trackball, a joystick, and the like. The output means 40 may include a display device, auxiliary lighting means (e.g., LEDs), tactile feedback means (e.g., vibration motors), and the like. Such display devices include, but are not limited to, liquid crystal displays, light emitting diodes, displays and plasma displays. In some alternative implementations, the display device may be a touch screen.

The embodiments of the present invention also provide a computer readable storage medium, and the method according to the embodiments of the present invention described above may be implemented in hardware, firmware, or as a computer code which may be recorded on a storage medium, or as original stored in a remote storage medium or a non-transitory machine readable storage medium downloaded through a network and to be stored in a local storage medium, so that the method described herein may be stored on such software process on a storage medium using a general purpose computer, a special purpose processor, or programmable or special purpose hardware. The storage medium can be a magnetic disk, an optical disk, a read-only memory, a random access memory, a flash memory, a hard disk, a solid state disk or the like; further, the storage medium may also comprise a combination of memories of the kind described above. It will be appreciated that a computer, processor, microprocessor controller or programmable hardware includes a storage element that can store or receive software or computer code that, when accessed and executed by the computer, processor or hardware, implements the methods illustrated by the above embodiments.

Although embodiments of the present invention have been described in connection with the accompanying drawings, various modifications and variations may be made by those skilled in the art without departing from the spirit and scope of the invention, and such modifications and variations fall within the scope of the invention as defined by the appended claims.

Claims

1. A device management method, applied to a cloud, the method comprising:

transmitting a node access command, wherein the node access command is used for requesting to establish connection with an edge node under a target communication network;

Responding to the access of a current edge node, sending a target device scanner to the current edge node, so that the current edge node determines the Internet of things device to be managed according to the scanning result of the target device scanner, and the method comprises the following steps: detecting the connected edge nodes corresponding to the target network segment where the current edge node is located through a preset node scanner, and determining whether the connected edge nodes have associated edge nodes communicated with the current edge node or not; if the connected edge node exists the associated edge node and the associated edge node comprises a deployed equipment scanner, the deployed equipment scanner is used as a target equipment scanner corresponding to the current edge node, and the current edge node is controlled to acquire the target equipment scanner from the associated edge node, wherein the deployed equipment scanner is sent by the cloud end and is used for scanning whether the to-be-managed Internet of things equipment which is connected with the current edge node and needs to be managed exists;

And controlling the current edge node to acquire the equipment data of the to-be-managed Internet of things equipment based on the scanning result sent by the current edge node so as to manage the to-be-managed Internet of things equipment.

2. The method of claim 1, wherein the sending the target device scanner into the current edge node in response to the current edge node being accessed comprises:

Responding to the accessed current edge node, and acquiring node information of the current edge node;

And sending the target equipment scanner to the current edge node.

3. The method of claim 2, wherein the determining a target device scanner corresponding to the current edge node from a preset plurality of device scanners based on the node information comprises:

determining a target network segment where the current edge node is located according to the node information;

Detecting whether an associated edge node communicated with the current edge node exists in the connected edge nodes corresponding to the target network segment through a preset node scanner;

and if the connected edge nodes have associated edge nodes and the associated edge nodes comprise deployed equipment scanners, the deployed equipment scanners are used as target equipment scanners corresponding to the current edge nodes, and the deployed equipment scanners are target edge equipment corresponding to the associated edge nodes in the equipment scanners.

4. A method according to claim 3, wherein the associated edge node is detected by the node scanner via a preset target internet protocol address list, and the target internet protocol address list includes a plurality of edge nodes corresponding to the target network segment and in communication with each other.

5. The method of claim 1, wherein the scan result includes target device information of the to-be-managed internet of things device, and the controlling the current edge node to collect device data of the to-be-managed internet of things device based on the scan result sent by the current edge node includes:

detecting whether the acquired historical scanning result comprises the target equipment information or not;

If the history scanning result does not include the target equipment information, establishing a binding relation between the current edge node and the to-be-managed Internet of things equipment;

And sending a target data collector to the current edge node to control the current edge node to collect the equipment data of the to-be-managed Internet of things equipment through the target data collector.

6. The method according to claim 5, wherein the controlling the current edge node to collect the device data of the internet of things device to be managed based on the scan result sent by the current edge node further comprises:

and establishing and storing an association relation between the Internet protocol information and the target equipment information, and controlling the current edge node to acquire the equipment data of the Internet of things equipment to be managed until the history scanning result does not comprise the target equipment information.

7. The method according to claim 1, wherein the method further comprises:

if the connection between the device association node and the current edge node is detected to be in a disconnection state, and the disconnection time is longer than a preset time threshold, determining a target edge node from a prestored device association node set corresponding to the to-be-managed internet of things device, wherein a scanning result corresponding to each edge node in the device association node set comprises the target device information;

And managing the to-be-managed internet of things equipment through the target edge node.

8. The method of claim 7, wherein the method further comprises:

And if the connection between the current edge node and the current edge node is detected to be in a connection state again, the internet of things equipment to be managed is managed again through the current edge node.

9. The method of claim 1, wherein the node access command comprises a bulk access command for allowing simultaneous or sequential access of a plurality of edge nodes into the cloud.

10. A device management method, applied to a current edge node, the method comprising:

Responding to a received node access command sent by a cloud, and establishing a connection relationship with the cloud, wherein the node access command is used for requesting to establish connection with a current edge node under a target communication network;

Receiving the target device scanner sent by the cloud through the connection relation, wherein the process of sending the target device scanner by the cloud comprises the following steps: detecting the connected edge nodes corresponding to the target network segment where the current edge node is located through a preset node scanner, and determining whether the connected edge nodes have associated edge nodes communicated with the current edge node or not; if the connected edge node exists the associated edge node and the associated edge node comprises a deployed equipment scanner, the deployed equipment scanner is used as a target equipment scanner corresponding to the current edge node, and the current edge node is controlled to acquire the target equipment scanner from the associated edge node, wherein the deployed equipment scanner is sent by the cloud end and is used for scanning whether the to-be-managed Internet of things equipment which is connected with the current edge node and needs to be managed exists;

And determining the to-be-managed Internet of things equipment through the target equipment scanner, and sending a scanning result of the to-be-managed Internet of things equipment to the cloud end so as to acquire equipment data of the to-be-managed Internet of things equipment.

11. The method of claim 10, wherein the determining, by the target device scanner, the internet of things device to be managed and sending the scan result of the internet of things device to be managed to the cloud comprises:

operating the target equipment scanner through a preset configuration file to determine the equipment of the Internet of things to be managed;

If the to-be-managed Internet of things equipment is scanned, acquiring target equipment information of the to-be-managed Internet of things equipment through a preset equipment discovery template, and obtaining a scanning result;

and sending the scanning result to the cloud.

12. The method according to claim 10, wherein the method further comprises:

Receiving a target data collector sent by the cloud;

Acquiring equipment data of the to-be-managed Internet of things equipment through the target data acquisition device according to the binding relation between the to-be-managed Internet of things equipment and the to-be-managed Internet of things equipment;

And sending the device data to the cloud end so that the cloud end manages the to-be-managed Internet of things device according to the device data.

13. A device management apparatus for use in a cloud, the apparatus comprising:

The first sending module is configured to send a target device scanner to a current edge node in response to the current edge node being accessed, so that the current edge node determines an internet of things device to be managed according to a scanning result of the target device scanner, and includes: detecting the connected edge nodes corresponding to the target network segment where the current edge node is located through a preset node scanner, and determining whether the connected edge nodes have associated edge nodes communicated with the current edge node or not; if the connected edge node exists the associated edge node and the associated edge node comprises a deployed equipment scanner, the deployed equipment scanner is used as a target equipment scanner corresponding to the current edge node, and the current edge node is controlled to acquire the target equipment scanner from the associated edge node, wherein the deployed equipment scanner is sent by the cloud end and is used for scanning whether the to-be-managed Internet of things equipment which is connected with the current edge node and needs to be managed exists;

14. A device management apparatus for use with a current edge node, the apparatus comprising:

the connection module is used for responding to a received node access command sent by the cloud end, establishing a connection relation with the cloud end, wherein the node access command is used for requesting to establish connection with a current edge node under a target communication network;

The first receiving module is configured to receive, through the connection relationship, the target device scanner sent by the cloud, where a process of sending, by the cloud, the target device scanner includes: detecting the connected edge nodes corresponding to the target network segment where the current edge node is located through a preset node scanner, and determining whether the connected edge nodes have associated edge nodes communicated with the current edge node or not; if the connected edge node exists the associated edge node and the associated edge node comprises a deployed equipment scanner, the deployed equipment scanner is used as a target equipment scanner corresponding to the current edge node, and the current edge node is controlled to acquire the target equipment scanner from the associated edge node, wherein the deployed equipment scanner is sent by the cloud end and is used for scanning whether the to-be-managed Internet of things equipment which is connected with the current edge node and needs to be managed exists;

The second sending module is used for determining the to-be-managed internet of things equipment through the target equipment scanner and sending the scanning result of the to-be-managed internet of things equipment to the cloud end so as to acquire equipment data of the to-be-managed internet of things equipment.

15. A computer device, comprising:

a memory and a processor communicatively coupled to each other, the memory having stored therein computer instructions that, upon execution, perform the device management method of any of claims 1 to 9 or the device management method of any of claims 10 to 12.

16. A computer-readable storage medium having stored thereon computer instructions for causing a computer to execute the device management method according to any one of claims 1 to 9 or the device management method according to any one of claims 10 to 12.