Management methods, equipment and storage media for IoT devices

Abstract

This invention belongs to the field of IoT device technology, specifically relating to a management method, device, and storage medium for IoT devices, and is also related to the field of communication technology. The method includes: acquiring a service request sent by the cloud through a first APP, the service request indicating management information of the IoT device and the identifier of a target server corresponding to the IoT device; sending an access request carrying the management information to a second APP of the target server based on the identifier of the target server; receiving an access result returned by the target server through the second APP, and sending the access result to the first APP in the cloud, the access result indicating the target server's response to the management information. This method establishes a stable transmission channel between the cloud and the target server. Since management information is transmitted bidirectionally via APPs, it is not limited by the size of the transmitted content and does not require additional hardware configuration, thus reducing configuration costs.

Description

Technical Field

[0001] This invention belongs to the field of IoT device technology, specifically relating to a management method, device, and storage medium for IoT devices. Background Technology

[0002] To manage IoT devices, it's essential to maintain crucial information such as device model name, communication attributes, lifecycle, and the IoT gateway to which they belong. Existing gateway architectures generally employ a cloud-edge node-edge device approach, managing edge devices through the cloud or edge node.

[0003] Under the premise that the existing gateway technology architecture is not significantly modified, the existing IoT device management methods include: local access through gateway hardware, such as browser console (Web Console) or network product user interface (Web UI); or unified maintenance of device creation on edge gateways in the cloud through asynchronous communication via Message Queuing Telemetry Transport (MQTT) protocol to manage devices.

[0004] In the above methods, the gateway hardware can only be accessed locally; the MQTT asynchronous communication method requires the additional deployment of MQTT message middleware and the separate design of the MQTT Application Program Interface (API), and there are limitations on the size of the data packets. Summary of the Invention

[0005] To address the aforementioned problems in existing technologies, namely, that existing gateway hardware can only access devices locally; that asynchronous MQTT communication requires additional deployment of MQTT message middleware and separate design of the MQTT Application Program Interface (API), and that there are limitations on data packet size, this invention provides a management method for IoT devices, specifically:

[0006] A method for managing IoT devices, applied to an edge node in an IoT device management system, the system further including a cloud and IoT devices connected to the cloud through the edge node, comprising:

[0007] Obtain the service request sent by the cloud through the first APP. The service request is used to indicate the management information of the IoT device and the identifier of the target server corresponding to the IoT device.

[0008] Based on the identifier of the target server, an access request carrying the management information is sent to the second APP of the target server;

[0009] The system receives the access result returned by the target server through the second APP and sends the access result to the first APP in the cloud. The access result is used to indicate the target server's response to the management information.

[0010] In one possible design, before sending an access request carrying the management information to the second APP of the target server based on the identifier of the target server, the method further includes:

[0011] Obtain the second APP interface protocol corresponding to the target server;

[0012] Determine whether the interface of the first APP matches the interface protocol of the second APP. If so, determine whether to send an access request carrying the management information to the second APP on the target server.

[0013] In one possible design, if the interface protocol of the first APP does not match that of the second APP, the step of sending an access request carrying the management information to the second APP of the target server based on the identifier of the target server includes:

[0014] Based on the interface protocol of the second APP, generate an access request adapted to the interface protocol of the second APP;

[0015] Based on the identifier of the target server, an access request carrying the management information and adapted to the interface protocol of the second APP is sent to the second APP of the target server.

[0016] In one possible design, the first app that sends the access result to the cloud includes:

[0017] Based on the interface protocol of the first APP and the access result, generate an access result adapted to the interface protocol of the first APP;

[0018] The access results adapted by the interface protocol of the first APP are sent to the first APP in the cloud.

[0019] In one possible design, the management information of the IoT device includes at least one of the following: IoT device creation, deletion, or communication protocol.

[0020] Secondly, this application provides a management system for IoT devices, including: a cloud, an edge node, and IoT devices connected to the cloud through the edge node;

[0021] The edge node is used to execute the management method for IoT devices.

[0022] In one possible design, the first app in the cloud is used for:

[0023] Acquire user-managed IoT devices;

[0024] The target server identifier is obtained based on the IoT device and the preset IoT device table, where the preset IoT device table stores the correspondence between IoT devices and target server identifiers.

[0025] Send a service request to the edge node.

[0026] Thirdly, this application provides a management device for IoT devices, comprising:

[0027] The acquisition module is used to acquire business requests sent from the cloud through the first APP. The business requests are used to indicate the management information of the IoT device and the identifier of the target server corresponding to the IoT device.

[0028] The processing module is used to send an access request carrying the management information to the second APP of the target server based on the identifier of the target server;

[0029] The feedback module is used to receive the access result returned by the target server through the second APP, and send the access result to the first APP in the cloud. The access result is used to indicate the target server's response to the management information.

[0030] Fourthly, this application provides an electronic device, including: a processor, and a memory communicatively connected to the processor;

[0031] The memory stores computer-executed instructions;

[0032] The processor executes computer execution instructions stored in the memory to implement a management method for IoT devices.

[0033] Fifthly, this application provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement a management method for IoT devices.

[0034] Those skilled in the art will understand that the IoT device management method, device, and storage medium provided by the present invention, by acquiring a service request sent by the cloud through a first APP, the service request being used to indicate the management information of the IoT device and the identifier of the target server corresponding to the IoT device; sending an access request carrying the management information to a second APP of the target server according to the identifier of the target server; receiving the access result returned by the target server through the second APP, and sending the access result to the first APP in the cloud, the access result being used to indicate the means by which the target server responds to the management information, thereby establishing a stable transmission channel between the cloud and the target server. Since management information is transmitted bidirectionally using APPs, it is not limited by the size of the transmitted content, and at the same time, it does not require additional hardware configuration, thus reducing configuration costs. Attached Figure Description

[0035] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0036] Figure 1 This is a schematic diagram illustrating an application scenario of the IoT device management method provided in the embodiments of this application.

[0037] Figure 2 A flowchart illustrating the IoT device management method provided in the embodiments of this application. Figure 1 ;

[0038] Figure 3 A flowchart illustrating the IoT device management method provided in the embodiments of this application. Figure 2 ;

[0039] Figure 4 This is a schematic diagram of the structure of the management system for IoT devices provided in an embodiment of this application;

[0040] Figure 5 This is a schematic diagram of the structure of the management device for the IoT device provided in the embodiments of this application;

[0041] Figure 6 This is a schematic diagram of the hardware structure of the electronic device provided in the embodiments of this application. Detailed Implementation

[0042] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numerals in different drawings represent the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims, and not all embodiments. All other embodiments obtained by those skilled in the art based on the embodiments of this invention without inventive effort are within the scope of protection of this invention.

[0043] First, the relevant concepts or terms involved in this application will be explained:

[0044] The Internet of Things (IoT) refers to the use of various information sensors, RFID technology, GPS, infrared sensors, laser scanners, and other devices and technologies to collect real-time data on any object or process that needs to be monitored, connected, or interacted with. This data includes information on sound, light, heat, electricity, mechanics, chemistry, biology, location, and other parameters. Through various possible network access methods, it achieves ubiquitous connectivity between things and between things and people, enabling intelligent perception, identification, and management of objects and processes. The IoT is an information carrier based on the internet and traditional telecommunications networks, enabling all independently addressable ordinary physical objects to form an interconnected network.

[0045] Application (APP): refers to client software.

[0046] Message Queuing Telemetry Transport (MQTT) is an Internet of Things (IoT) transport protocol designed for lightweight publish / subscribe messaging. It aims to provide reliable network services for IoT devices in low-bandwidth and unstable network environments. Subscribers only receive data they have subscribed to, and do not receive non-subscribed data, thus ensuring the exchange of necessary data while avoiding the storage and processing of invalid data.

[0047] Broker: refers to a Transmission Control Protocol (TCP) server that can be used to test MQTT or real-world project applications.

[0048] Application Programming Interface (API): Defined as a standard set of information and commands that an application can use to exchange with a computer's operating system. It is a calling interface provided by the operating system for the application, which in turn calls the operating system's API to make the operating system execute the application's commands.

[0049] The current cloud-based management of IoT devices mainly uses asynchronous MQTT communication to manage IoT devices connected to edge nodes. This method requires additional deployment of an MQTT broker and separate design of an MQTT API device management interface, and there are limitations on the size of data packets transmitted during communication.

[0050] Figure 1 This is a schematic diagram illustrating an application scenario of the IoT device management method provided in this application embodiment. For example... Figure 1 As shown, IoT devices are connected to the cloud through edge nodes. Both the cloud and the edge nodes have apps installed to manage the IoT devices. The cloud has the first app installed, and the edge nodes have the second app installed. The first app and the second app can access each other.

[0051] The IoT device management method provided in this application is applied to the edge node in the IoT device management system. The system also includes the cloud and IoT devices accessing the cloud through the edge node. By transmitting management information as a business request between the first APP and the second APP in the form of access request and access response, the cloud can manage the IoT devices. Since there is no limit to the data packet size of the APP's request and response, and no additional server and interface configuration is required, the above-mentioned technical problems of the prior art can be solved.

[0052] The technical solution of this application and how the technical solution of this application solves the above-mentioned technical problems are described in detail below with specific embodiments. These specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The embodiments of this application will now be described with reference to the accompanying drawings.

[0053] Figure 2 A flowchart illustrating the management method for IoT devices provided in this application embodiment. Figure 1 .like Figure 2 As shown, the method includes:

[0054] S201. Obtain the service request sent by the cloud through the first APP. The service request is used to indicate the management information of the IoT device and the identifier of the target server corresponding to the IoT device.

[0055] Specifically, different IoT devices correspond to different servers, and these servers are connected to nearby edge gateways via wired or wireless means. These edge gateways are all managed by the same cloud, and the edge gateways and servers together form edge nodes that can communicate with the cloud.

[0056] The first app is a pre-installed application in the cloud, and the second app is a pre-installed application on the server of the edge node. Based on the principle of cloud-edge service mutual access in the EdgeMesh network of the KubeEdge project, the application mutual access function between the cloud and the edge node is built.

[0057] Since applications can send and receive requests via HTTP without being limited by the amount of data, the management of IoT devices in the cloud can be transformed into sending management requests from the cloud to edge nodes, and then using the edge nodes to send the management requests to the corresponding IoT devices, thereby achieving unified management functionality in the cloud.

[0058] S202. Based on the identifier of the target server, send an access request carrying the management information to the second APP of the target server;

[0059] Specifically, based on the identifier carried in the business request, the server of the corresponding IoT device, i.e., the target server, can be analyzed. The target server contains all the management information for the corresponding IoT device. In other words, the IoT device can be managed by operating the target server. Therefore, a transmission channel needs to be established between the cloud and the target server. The business request is packaged into an access request carrying management information in the first app, and then the access request is sent to the target server, where it is received and parsed by the second app on the target server.

[0060] S203. Receive the access result returned by the target server through the second APP, and send the access result to the first APP in the cloud. The access result is used to indicate the target server's response to the management information.

[0061] Specifically, after the second app receives and parses the access request, it needs to respond to the access request, that is, generate an access result based on the access request, and then send it to the cloud through the target server. After the cloud receives the access result, it is parsed by the first app, thus completing the transmission channel from the cloud to the target server.

[0062] The method provided in this embodiment obtains a service request sent by the cloud through a first APP. The service request indicates the management information of the IoT device and the identifier of the target server corresponding to the IoT device. Based on the identifier of the target server, an access request carrying the management information is sent to a second APP of the target server. The access result returned by the target server through the second APP is received and sent to the first APP in the cloud. The access result indicates the means by which the target server responds to the management information. This establishes a stable transmission channel between the cloud and the target server. Since the management information is transmitted bidirectionally using APPs, it is not limited by the size of the transmitted content and does not require additional hardware configuration, thus reducing configuration costs.

[0063] The following detailed description of the IoT device management method of this application is based on a specific embodiment.

[0064] Figure 3 A flowchart illustrating the management method for IoT devices provided in this application embodiment. Figure 2 .like Figure 3 As shown, the method includes:

[0065] S301. Obtain the service request sent by the cloud through the first APP. The service request is used to indicate the management information of the IoT device and the identifier of the target server corresponding to the IoT device.

[0066] Specifically, different IoT devices correspond to different servers, and these servers are all connected to nearby edge gateways via wired or wireless means. These edge gateways are all managed by the same cloud, and the edge gateways and servers together form edge nodes that can communicate with the cloud. The first app is a pre-installed application in the cloud, and the second app is a pre-installed application on the server of the edge node. Based on the principle of cloud-edge service communication using the EdgeMesh network in the KubeEdge project, the application communication function between the cloud and the edge node is built.

[0067] The management information of the IoT device includes at least one of the following: the creation, deletion, or communication protocol of the IoT device.

[0068] This embodiment uses the creation of IoT devices as an example to explain the management method of IoT devices step by step. Among them, the first APP in the cloud is the centralized control APP, and the second APP at the edge node is the device management APP.

[0069] To add an IoT device in the centralized management app, users first need to find the domain name of the server to which the IoT device belongs, such as the server domain name of the IoT (vendor 1) device management app (serviceGateway1). Then, in the centralized management app, under the corresponding server domain name, users select the "Add Device" operation in the management information. The centralized management app then generates an HTTP request to add the device (http: / / serviceGateway1:port.device / add).

[0070] S302. Obtain the second APP interface protocol corresponding to the target server;

[0071] Specifically, since the device management apps of different IoT device manufacturers are designed for their own IoT devices and cost requirements, their interfaces vary and cannot be guaranteed to be a unified standard interface. Therefore, in order to ensure that the sent content is received and parsed normally by the device management app, it is necessary to first obtain the interface protocol of the device management app.

[0072] S303. Determine whether the interface of the first APP matches the interface protocol of the second APP. If yes, execute S304; otherwise, execute S305-S306.

[0073] Specifically, after obtaining the interface protocol of the device management APP, it is first compared with the interface protocol of the centralized management APP in the cloud. If they are the same, no further processing is needed, and data can be directly exchanged. However, if the protocols are different, the access request generated by the centralized management APP needs to be modified to a format that the device management APP can parse before sending. This way, no additional configuration is needed for each device management APP. Only an adapter needs to be added in the cloud. The device management APP will still operate in the original way, which is in line with the original user habits and also facilitates the manufacturer's later maintenance work.

[0074] In another possible scenario, the adapter is set at the edge node.

[0075] S304. Based on the identifier of the target server, send an access request carrying the management information to the second APP of the target server;

[0076] Specifically, when the interface protocols of the centralized management APP and the device management APP are the same, the access request generated by the centralized management APP is directly sent to the target server and received and parsed by the device management APP on the target server.

[0077] S305. Generate an access request adapted to the interface protocol of the second APP according to the interface protocol of the second APP.

[0078] Specifically, when the interface protocols of the centralized management APP and the device management APP are different, the access request (http: / / serviceGateway1:port.device / add.stdURL) generated by the centralized management APP is adapted according to the interface protocol of the device management APP to obtain an access request (http: / / serviceGateway1:port.device / add.private1URL) that is compatible with the interface of the device management APP.

[0079] S306. Based on the identifier of the target server, send an access request carrying the management information and adapted to the interface protocol of the second APP of the target server to the second APP of the target server;

[0080] Specifically, after handling the interface protocol adaptation issue, the identifier of the target server is parsed from the access request, namely the server domain name of the device management APP (serviceGateway1), and the access request is sent according to the server domain name path of the device management APP.

[0081] S307. Receive the access result returned by the target server through the second APP, the access result being used to indicate the target server's response to the management information;

[0082] Specifically, after receiving the access request, the target server sends it to the device management APP. The device management APP identifies the management request to add the device based on device / add in the access request (http: / / serviceGateway1:port.device / add.private1URL), executes the corresponding add task, and outputs the execution result as the access result.

[0083] S308. Based on the interface protocol of the first APP and the access result, generate an access result adapted to the interface protocol of the first APP.

[0084] Specifically, because the device management app and the centralized control app have different interface protocols, the access results generated by the device management app cannot be read by the centralized control app. Therefore, the access results need to be adapted for the centralized control app. That is, the access results are first sent to the server's adaptation layer. This adaptation layer can be set in the server adaptation layer of the edge node or in the cloud server adaptation layer. The adaptation layer converts the access results according to the interface protocol of the centralized control app to generate access results that the centralized control app can parse.

[0085] S309. Send the access result adapted by the interface protocol of the first APP to the first APP in the cloud.

[0086] Specifically, after the adaptation is completed, the access results are sent to the centralized management APP in the cloud. The centralized management APP then displays the result information to the user, showing whether the IoT device has been successfully added, thus completing the management of the IoT device.

[0087] The method provided in this embodiment obtains a service request sent by the cloud through a first APP, the service request indicating the management information of the IoT device and the identifier of the target server corresponding to the IoT device; obtains the interface protocol of the second APP corresponding to the target server; determines whether the interface of the first APP matches the interface protocol of the second APP. If yes, an access request carrying the management information is sent to the second APP of the target server according to the identifier of the target server; if no, an access request adapted to the interface protocol of the second APP is generated according to the interface protocol of the second APP. This method enables unified management of IoT devices from various manufacturers or types in the cloud, avoids dependence on a single IoT device supplier, and does not affect the development and maintenance of existing IoT devices, avoids excessive duplication of development, and preserves the usage habits of existing users.

[0088] Based on the identifier of the target server, an access request carrying the management information and adapted to the interface protocol of the second APP of the target server is sent to the second APP of the target server; the access result returned by the target server through the second APP is received, and the access result is used to indicate the target server's response to the management information; based on the interface protocol of the first APP and the access result, an access result adapted to the interface protocol of the first APP is generated; the access result adapted to the interface protocol of the first APP is sent to the first APP in the cloud. This means that unified control of multiple IoT devices in the cloud is realized, which is conducive to updating the file information of IoT devices synchronously in the cloud, has real-time modification timeliness, avoids the complex process of updating information one by one for each IoT device, and because the information transmission is directly connected to the APP, the technical links involved in the device management process are reduced, and the difficulty of troubleshooting problems in the IoT device management process is reduced.

[0089] This method is widely used in whole-house intelligent digital control application scenarios such as smart homes, smart home ecosystems, and intelligence house ecosystems.

[0090] The aforementioned network may include, but is not limited to, at least one of the following: wired network, wireless network.

[0091] The aforementioned wired network may include, but is not limited to, at least one of the following: wide area network, metropolitan area network, local area network; the aforementioned wireless network may include, but is not limited to, at least one of the following: WIFI (Wireless Fidelity), Bluetooth.

[0092] Terminal devices are not limited to: PCs, mobile phones, tablets, smart air conditioners, smart range hoods, smart refrigerators, smart ovens, smart stoves, smart washing machines, smart water heaters, smart washing equipment, smart dishwashers, smart projectors, smart TVs, smart clothes racks, smart curtains, smart audio-visual equipment, smart sockets, smart speakers, smart speakers, smart fresh air systems, smart kitchen and bathroom equipment, smart bathroom equipment, smart robot vacuum cleaners, smart window cleaning robots, smart mopping robots, smart air purifiers, smart steam ovens, smart microwave ovens, smart water heaters, smart air purifiers, smart water dispensers, smart door locks, etc.

[0093] Figure 4 This is a schematic diagram of the structure of the management system for IoT devices provided in an embodiment of this application. Figure 4 As shown, the system 40 includes:

[0094] The cloud 401, the edge node 402, and the IoT device 403 connected to the cloud 401 through the edge node 402; wherein the edge node 402 is used to execute the management method of the IoT device 403.

[0095] Specifically, the management methods for IoT devices under 403 include:

[0096] The cloud 401 receives a service request sent through the first APP. The service request is used to indicate the management information of the IoT device 403 and the identifier of the target server corresponding to the IoT device 403.

[0097] Based on the identifier of the target server, an access request carrying the management information is sent to the second APP of the target server;

[0098] The system receives the access result returned by the target server through the second APP and sends the access result to the first APP in the cloud 401. The access result is used to indicate the target server's response to the management information.

[0099] Furthermore, the first APP of the cloud 401 is used for:

[0100] 403. Obtain user-managed IoT devices;

[0101] The target server identifier is obtained based on the IoT device 403 and the preset IoT device table, where the preset IoT device table stores the correspondence between the IoT device 403 and the target server identifier.

[0102] Send a service request to the edge node 402.

[0103] In another preferred embodiment, the edge node 402 is provided with an adapter layer, which is used to perform the management method of the IoT device 403.

[0104] The IoT device management system provided in this embodiment can execute the IoT device management method of the above embodiment. Its implementation principle and technical effect are similar, and will not be described again here.

[0105] In this embodiment of the invention, electronic devices or main control devices can be divided into functional modules according to the above method examples. For example, each function can be divided into its own functional modules, or two or more functions can be integrated into one processing unit. The integrated unit can be implemented in hardware or as a software functional module. It should be noted that the module division in this embodiment of the invention is illustrative and only represents one logical functional division; other division methods may be used in actual implementation.

[0106] Figure 5 A schematic diagram of the structure of the management device for the IoT device provided in this application. (For example...) Figure 5 As shown, the device 50 includes:

[0107] The acquisition module 501 is used to acquire a business request sent by the cloud through the first APP. The business request is used to indicate the management information of the IoT device and the identifier of the target server corresponding to the IoT device.

[0108] The processing module 502 is used to send an access request carrying the management information to the second APP of the target server according to the identifier of the target server;

[0109] Specifically, the processing module 502 is used to: before sending an access request carrying the management information to the second APP of the target server based on the identifier of the target server, the method further includes:

[0110] Obtain the second APP interface protocol corresponding to the target server;

[0111] Determine whether the interface of the first APP matches the interface protocol of the second APP. If so, determine whether to send an access request carrying the management information to the second APP on the target server.

[0112] In one possible design, before sending an access request carrying the management information to the second APP of the target server based on the identifier of the target server, the method further includes:

[0113] Obtain the second APP interface protocol corresponding to the target server;

[0114] Determine whether the interface of the first APP matches the interface protocol of the second APP. If so, determine whether to send an access request carrying the management information to the second APP on the target server.

[0115] In one possible design, if the interface protocol of the first APP does not match that of the second APP, the step of sending an access request carrying the management information to the second APP of the target server based on the identifier of the target server includes:

[0116] Based on the interface protocol of the second APP, generate an access request adapted to the interface protocol of the second APP;

[0117] Based on the identifier of the target server, an access request carrying the management information and adapted to the interface protocol of the second APP is sent to the second APP of the target server.

[0118] In one possible design, the first app that sends the access result to the cloud includes:

[0119] Based on the interface protocol of the first APP and the access result, generate an access result adapted to the interface protocol of the first APP;

[0120] The access results adapted by the interface protocol of the first APP are sent to the first APP in the cloud.

[0121] In one possible design, the management information of the IoT device includes at least one of the following: IoT device creation, deletion, or communication protocol.

[0122] Feedback module 503 is used to receive the access result returned by the target server through the second APP, and send the access result to the first APP in the cloud. The access result is used to indicate the target server's response to the management information.

[0123] The IoT device management device provided in this embodiment can execute the IoT device management method of the above embodiment. Its implementation principle and technical effect are similar, and will not be described again in this embodiment.

[0124] In the specific implementation of the aforementioned IoT device management device, each module can be implemented as a processor. The processor can execute computer execution instructions stored in the memory, thereby enabling the processor to execute the aforementioned IoT device management method.

[0125] Figure 6A schematic diagram of the structure of the electronic device provided in this application. Figure 6 As shown, the electronic device 60 includes at least one processor 601 and a memory 602. The electronic device 60 also includes a communication component 603. The processor 601, memory 602, and communication component 603 are connected via a bus 604.

[0126] In the specific implementation process, at least one processor 601 executes the computer execution instructions stored in the memory 602, causing at least one processor 601 to execute the IoT device management method executed on the electronic device side as described above.

[0127] The specific implementation process of processor 601 can be found in the above method embodiments, and its implementation principle and technical effect are similar. It will not be repeated here.

[0128] In the above embodiments, it should be understood that the processor can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), etc. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in this invention can be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules within the processor.

[0129] The memory may include high-speed RAM, and may also include non-volatile storage (NVM), such as at least one disk storage.

[0130] The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. Buses can be categorized as address buses, data buses, control buses, etc. For ease of illustration, the buses shown in the accompanying drawings are not limited to a single bus or a single type of bus.

[0131] The above description addresses the functions implemented by the electronic device and the main control device, illustrating the solutions provided by the embodiments of the present invention. It is understood that, in order to achieve the above functions, the electronic device or main control device includes corresponding hardware structures and / or software modules for executing each function.

[0132] Based on the units and algorithm steps described in the embodiments of this invention, the embodiments of this invention can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed by hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution.

[0133] Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of the technical solutions of the embodiments of the present invention.

[0134] This application also provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, implement the above-mentioned IoT device management method.

[0135] The aforementioned computer-readable storage medium can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk. The readable storage medium can be any available medium accessible to a general-purpose or special-purpose computer.

[0136] An exemplary readable storage medium is coupled to a processor, enabling the processor to read information from and write information to the readable storage medium. Of course, the readable storage medium can also be a component of the processor. The processor and the readable storage medium can reside in an Application Specific Integrated Circuit (ASIC). Alternatively, the processor and the readable storage medium can exist as discrete components in an electronic device or a host device.

[0137] Those skilled in the art will understand that all or part of the steps of the above-described method embodiments can be implemented by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When executed, the program performs the steps of the above-described method embodiments; and the aforementioned storage medium includes various media capable of storing program code, such as ROM, RAM, magnetic disks, or optical disks.

[0138] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, and not to limit them; although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some or all of the technical features; and these modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present invention.

Claims

1. A method for managing IoT devices, applied to an edge node in an IoT device management system, the system further including a cloud and IoT devices connected to the cloud via the edge node, characterized in that, include: Obtain the service request sent by the cloud through the first APP. The service request is used to indicate the management information of the IoT device and the identifier of the target server corresponding to the IoT device. Based on the identifier of the target server, an access request carrying the management information is sent to the second APP of the target server; The system receives the access result returned by the target server through the second APP and sends the access result to the first APP in the cloud. The access result is used to indicate the target server's response to the management information. Before sending an access request carrying the management information to the second APP of the target server based on the identifier of the target server, the method further includes: Obtain the second APP interface protocol corresponding to the target server; Determine whether the interface of the first APP matches the interface protocol of the second APP. If so, determine whether to send an access request carrying the management information to the second APP on the target server.

2. The method according to claim 1, characterized in that, If the interface protocol of the first APP does not match that of the second APP, the step of sending an access request carrying the management information to the second APP of the target server based on the identifier of the target server includes: Based on the interface protocol of the second APP, generate an access request adapted to the interface protocol of the second APP; Based on the identifier of the target server, an access request carrying the management information and adapted to the interface protocol of the second APP is sent to the second APP of the target server.

3. The method according to claim 2, characterized in that, The first APP that sends the access result to the cloud includes: Based on the interface protocol of the first APP and the access result, generate an access result adapted to the interface protocol of the first APP; The access results adapted by the interface protocol of the first APP are sent to the first APP in the cloud.

4. The method according to claim 1, characterized in that, The management information of the IoT device includes at least one of the following: the creation, deletion, or communication protocol of the IoT device.

5. A management system for IoT devices, characterized in that, include: The cloud, edge nodes, and IoT devices connected to the cloud via the edge nodes; wherein, The edge node is used to perform the method as described in any one of claims 1 to 4.

6. The system according to claim 5, characterized in that, The first app in the cloud is used for: Acquire user-managed IoT devices; The target server identifier is obtained based on the IoT device and the preset IoT device table, where the preset IoT device table stores the correspondence between IoT devices and target server identifiers. Send a service request to the edge node.

7. A management device for IoT devices, characterized in that, include: The acquisition module is used to acquire business requests sent from the cloud through the first APP. The business requests are used to indicate the management information of the IoT device and the identifier of the target server corresponding to the IoT device. The processing module is used to send an access request carrying the management information to the second APP of the target server based on the identifier of the target server; The feedback module is used to receive the access result returned by the target server through the second APP, and send the access result to the first APP in the cloud. The access result is used to indicate the target server's response to the management information. Before sending an access request carrying the management information to the second APP of the target server based on the identifier of the target server, the processing module is further configured to obtain the interface protocol of the second APP corresponding to the target server; determine whether the interface of the first APP matches the interface protocol of the second APP; if so, determine to send an access request carrying the management information to the second APP of the target server.

8. An electronic device, characterized in that, include: A processor, and a memory communicatively connected to the processor; The memory stores computer-executed instructions; The processor executes computer execution instructions stored in the memory to implement the method as described in any one of claims 1 to 4.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, are used to implement the method as described in any one of claims 1 to 4.

Images