Lightweight equipment access method and device, equipment and storage medium

Abstract

The invention provides a lightweight equipment access method and device, equipment and a storage medium, a distributed equipment access system is determined, the distributed equipment access system comprises at least one equipment access node, the equipment access node supports multiple transmission protocols, and at least one piece of Internet of Things equipment is accessed to the equipment access node. The number of the equipment access nodes can be determined according to the requirements of the user, and the equipment access nodes support various transmission protocols, so that a plurality of nodes do not need to be set to correspond to different transmission protocols, and the realization of lightweight access of the Internet of Things equipment is facilitated; the method comprises the following steps: acquiring equipment data of Internet of Things equipment through an equipment access node, pushing the equipment data to an Internet of Things equipment management system, pushing the equipment data to an application system through the Internet of Things equipment management system, and processing the equipment data through the application system comprising an application platform of at least one industry. The method can be suitable for lightweight deployment of application platforms in different industries.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a lightweight device access method, apparatus, device and storage medium. Background Art

[0002] As the Internet of Things gradually matures, IoT platform products need to be deployed in specific industries and applied to many fields such as industrial IoT, smart transportation, security and epidemic prevention, and smart life. More and more industry applications require IoT platforms to be able to achieve private and lightweight deployment, so as to combine with industry applications as cheaply and quickly as possible to achieve the goals and requirements of intelligent transformation of industry applications.

[0003] At present, mainstream IoT platforms can provide capabilities such as multiple IoT device access, data collection and data analysis. However, when privatizing for different industries, users can only change the IoT devices of the corresponding industry connected to the IoT application platform, as well as analyze different types of data on IoT devices. It cannot change the architecture of the IoT platform and cannot effectively achieve lightweighting. Summary of the invention

[0004] The embodiments of the present application provide a lightweight device access method, apparatus, device, and storage medium to solve at least one problem existing in the related art. The technical solution is as follows:

[0005] In a first aspect, an embodiment of the present application provides a lightweight device access method, including:

[0006] Determine a distributed device access system, the distributed device access system includes at least one device access node, the device access node supports multiple transmission protocols;

[0007] Connecting at least one IoT device to the device access node;

[0008] Acquire the device data of the IoT device through the device access node, and push the device data to the IoT device management system;

[0009] The device data is pushed to an application system through the Internet of Things device management system, and the device data is processed through the application system; the application system includes an application platform for at least one industry.

[0010] In one embodiment, the method further comprises:

[0011] Registering node information of at least one of the device access nodes through a service registration center;

[0012] When the IoT device is online, the node information is pushed to the IoT device management system through the gRPC interface or the http interface.

[0013] In one embodiment, the method further comprises:

[0014] When at least one of the application platforms sends downlink data, the IoT device management system receives the downlink data and determines a target device access node based on the node information and device information of the downlink data;

[0015] The downlink data is received through the target device access node, and the downlink data is sent to the corresponding target Internet of Things device.

[0016] In one embodiment, when the IoT device is online, pushing the node information to the IoT device management system through a gRPC interface or an http interface includes:

[0017] When the IoT device is online, and when the device access node corresponding to the IoT device is registered through the service registration center, the node information of the device access node is pushed to the IoT device management system through the gRPC interface;

[0018] When the IoT device is online, and when the device access node corresponding to the IoT device is not registered with the service registration center, the node information of the device access node is pushed to the IoT device management system through the http interface.

[0019] In one embodiment, the method further comprises:

[0020] Through the Internet of Things device management system, node information of device access nodes registered through the service registration center is regularly obtained;

[0021] Through the Internet of Things device management system, a heartbeat request is periodically sent to a device access node that is not registered with the service registration center to determine whether the device access node is offline. If it is offline, the state of the device access node is set to an offline state.

[0022] In one implementation, pushing the device data to the application system through the IoT device management system includes:

[0023] Analyzing the data format of the device data through the device object model of the Internet of Things device management system;

[0024] Determining whether the data format is a preset standard format;

[0025] When the data format is not a preset standard format, a target conversion algorithm is determined according to the format type of the data format, and the device data is converted into a preset standard format according to the target conversion algorithm.

[0026] In one implementation, determining that a distributed device accesses the system includes:

[0027] In response to the construction instruction, construct at least one device access node, wherein the device access node is used to connect one or more Internet of Things devices;

[0028] In response to the deployment instruction, the device access node is deployed to one or more servers.

[0029] In a second aspect, an embodiment of the present application provides a lightweight device access apparatus, including:

[0030] A determination module, configured to determine a distributed device access system, wherein the distributed device access system includes at least one device access node, and the device access node supports multiple transmission protocols;

[0031] An access module, used to connect at least one IoT device to the device access node;

[0032] An acquisition module, used to acquire device data of the IoT device through the device access node, and push the device data to the IoT device management system;

[0033] A push module is used to push the device data to an application system through the Internet of Things device management system, and process the device data through the application system; the application system includes an application platform for at least one industry.

[0034] In one implementation, the lightweight device access apparatus further includes a registration module, and the registration module is used to:

[0035] Registering node information of at least one of the device access nodes through a service registration center;

[0036] When the IoT device is online, the node information is pushed to the IoT device management system through the gRPC interface or the http interface.

[0037] In one embodiment, the lightweight device access apparatus further includes a management module, and the management module is used to:

[0038] When at least one of the application platforms sends downlink data, the IoT device management system receives the downlink data and determines a target device access node based on the node information and device information of the downlink data;

[0039] The downlink data is received through the target device access node, and the downlink data is sent to the corresponding target Internet of Things device.

[0040] In one embodiment, the management module is further used for:

[0041] Through the Internet of Things device management system, node information of device access nodes registered through the service registration center is regularly obtained;

[0042] Through the Internet of Things device management system, a heartbeat request is periodically sent to a device access node that is not registered with the service registration center to determine whether the device access node is offline. If it is offline, the state of the device access node is set to an offline state.

[0043] In a third aspect, an embodiment of the present application provides an electronic device, comprising: a processor and a memory, wherein the memory stores instructions, and the instructions are loaded and executed by the processor to implement a method in any one of the above-mentioned embodiments.

[0044] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, which stores a computer program. When the computer program is executed, the method in any one of the above-mentioned embodiments is implemented.

[0045] The beneficial effects of the above technical solution include at least:

[0046] By determining a distributed device access system, the distributed device access system includes at least one device access node, the device access node supports multiple transmission protocols, and at least one Internet of Things device is connected to the device access node. The number of device access nodes can be determined according to user needs, and the device access node supports multiple transmission protocols. There is no need to set up multiple nodes corresponding to different transmission protocols, which is conducive to achieving lightweight Internet of Things device access; the device data of the Internet of Things device is obtained through the device access node, and the device data is pushed to the Internet of Things device management system, and the device data is pushed to the application system through the Internet of Things device management system. The device data is processed through the application system including the application platform of at least one industry, which can be suitable for lightweight deployment of application platforms in various industries.

[0047] The above summary is for illustrative purposes only and is not intended to be limiting in any way. In addition to the illustrative aspects, embodiments and features described above, further aspects, embodiments and features of the present application will be readily apparent by reference to the accompanying drawings and the following detailed description. BRIEF DESCRIPTION OF THE DRAWINGS

[0048] In the accompanying drawings, unless otherwise specified, the same reference numerals throughout the multiple drawings represent the same or similar parts or elements. These drawings are not necessarily drawn to scale. It should be understood that these drawings only depict some embodiments disclosed in the present application and should not be regarded as limiting the scope of the present application.

[0049] Figure 1 A schematic diagram of the steps of a lightweight device access method according to an embodiment of the present application;

[0050] Figure 2 This is a first schematic diagram of an Internet of Things device, a distributed device access system, an Internet of Things device management system, and an application system architecture according to an embodiment of the present application;

[0051] Figure 3 A second schematic diagram of an Internet of Things device, a distributed device access system, an Internet of Things device management system, and an application system architecture according to an embodiment of the present application;

[0052] Figure 4 A schematic diagram of a lightweight device access method process according to an embodiment of the present application;

[0053] Figure 5 This is a structural block diagram of a lightweight device access device according to an embodiment of the present application;

[0054] Figure 6 This is a structural block diagram of an electronic device according to an embodiment of the present application. DETAILED DESCRIPTION

[0055] In the following, only some exemplary embodiments are briefly described. As those skilled in the art will appreciate, the described embodiments may be modified in various ways without departing from the spirit or scope of the present application. Therefore, the drawings and descriptions are considered to be exemplary and non-restrictive in nature.

[0056] Reference Figure 1 , a flowchart of a lightweight device access method according to an embodiment of the present application is shown, and the lightweight device access method may at least include steps S100-S400:

[0057] S100: Determine a distributed device access system, where the distributed device access system includes at least one device access node.

[0058] In the embodiment of the present application, the device access node supports multiple transmission protocols, and the device access node can be added or deleted based on the actual needs of the user. Figure 2 As shown, the transmission protocols of access point 1 and access point 2 include but are not limited to MQTT, UDP, Lwm2m, JT808, CoaP, HTTP, ICP, and Modbus.

[0059] S200: Connect at least one IoT device to a device access node.

[0060] S300: Obtain device data of the IoT device through the device access node, and push the device data to the IoT device management system.

[0061] S400: Push device data to an application system through an IoT device management system, and process the device data through the application system.

[0062] It should be noted that the application system includes http interfaces such as device management and data reporting, interacts with the IoT device management system, and quickly builds the device management capabilities required by the application system based on the IoT device management system. Optionally, the (vertical industry) application system includes at least one industry application platform (or industry application system), such as Figure 3 The industry application system 1 and industry application system 2 shown can also be, for example, application platforms for smart home appliances such as the smart home platform, application platforms for fire protection such as the fire protection platform, application platforms for doors and windows such as the door magnetic platform, application platforms for industrial Internet of Things such as the industrial Internet of Things platform, etc., without specific limitation.

[0063] The technical solution of the embodiment of the present application determines a distributed device access system, which includes at least one device access node. The device access node supports multiple transmission protocols, and at least one Internet of Things device is connected to the device access node. The number of device access nodes can be determined according to user needs, and the device access node supports multiple transmission protocols. There is no need to set up multiple nodes corresponding to different transmission protocols, which is conducive to achieving lightweight Internet of Things device access; the device data of the Internet of Things device is obtained through the device access node, and the device data is pushed to the Internet of Things device management system, and the device data is pushed to the application system through the Internet of Things device management system. The device data is processed through the application system including the application platform of at least one industry, which can be suitable for lightweight deployment of application platforms in various industries.

[0064] In one embodiment, when determining a distributed device access system, a user can input a construction instruction in a terminal or server based on actual needs, and the terminal or server builds at least one device access node in response to the construction instruction, and the device access node is used to connect one or more IoT devices (referred to as devices). Then, based on actual deployment needs, a deployment instruction is input, and the terminal or server responds to the deployment instruction to deploy the device access node to one or more servers.

[0065] In one embodiment, it also includes an Internet of Things device management system and a distributed device access system (also referred to as a distributed device access point (system), such as Figure 2 The steps of registering as shown in FIG. 1 include steps S110-S120:

[0066] S110. Register node information of at least one device access node through a service registration center.

[0067] Optionally, the service registration center is used to perform service registration management for the IoT device management system and the distributed device access system. The specific service registration center is not limited to open source registration center tools such as Zookeeper, Eureka, Nacos, Consul and Etcd.

[0068] It should be noted that the IoT device management system (device management system for short) includes a device object model, including but not limited to device attributes, functional services, event management, device management, data storage, message forwarding, device online and offline management, device authentication such as device serial code, IMEI number, identity authentication, etc., device reporting data processing, and interface management with industry applications, to achieve data transmission between distributed device access systems and application systems. The distributed device access system supports distributed deployment, containerized deployment, rapid expansion and contraction, and supports the deployment of device access capabilities to different servers, such as distributing IoT devices to distributed deployed device access servers to achieve dynamic expansion capabilities for device access. In addition, IoT devices can access each device access node of the distributed device access system through different protocols of the device access node.

[0069] S120. When the IoT device is online, the node information is pushed to the IoT device management system through the gRPC interface or the http interface.

[0070] In the embodiment of the present application, after the corresponding access device of the IoT device accesses the node, the IoT device management system will record the node information of the device access node, including but not limited to the device going online and offline, the device uplink and downlink data transmission, the ID / device number of the IoT device, the node name, the node IP, the node status, the routing relationship between the IoT device and the device access node, etc., and the node information of at least one device access node can be registered through the service registration center, and the node information is pushed to the IoT device management system through the gRPC interface or the http interface when the IoT device goes online. The node information includes the transmission of the device going online and offline, the device uplink and downlink data, etc. Optionally, the IoT device management system provides gRPC service (interface) and http interface to directly transmit data with the device access node in the distributed device access system, and the interface can also include functions such as device authentication, device information query, and device object model query; the gRPC service (interface) can be provided by the service registration center. In addition, the IoT device management system has a database that can store node information, reporting, and sending data.

[0071] Optionally, the IoT device may be a white appliance, a smart door lock, etc., without specific limitation.

[0072] Specifically, S120 includes step S1201 or S1202:

[0073] S1201. When an IoT device is online and the device access node corresponding to the IoT device is registered through the service registration center, the node information of the device access node is pushed to the IoT device management system through the gRPC interface.

[0074] In the embodiment of the present application, the gRPC interface is used for distributed device access system and IoT device management system to register in the same service registration center, providing more efficient transmission efficiency than the http interface. Specifically, when the IoT device is online, and when the device access node corresponding to the IoT device is registered through the service registration center, the node information of the device access node is pushed to the IoT device management system through the gRPC interface.

[0075] S1202: When the IoT device is online, and when the device access node corresponding to the IoT device is not registered with the service registration center, the node information of the device access node is pushed to the IoT device management system through the http interface.

[0076] In the embodiment of the present application, in order to facilitate the distributed device access system and the IoT device management system that are not registered in the same service registration center, an http interface is provided for the data transmission method in this case. Specifically, when the IoT device is online, and when the device access node corresponding to the IoT device is not registered in the service registration center, the node information of the device access node is pushed to the IoT device management system through the http interface, and the normal transmission and use of data is guaranteed through the http interface.

[0077] In the embodiment of the present application, when the application platform needs to send data to the target IoT device, steps S101-S102 are included:

[0078] S101. When at least one application platform sends downlink data, the IoT device management system receives the downlink data and determines a target device access node based on node information and device information of the downlink data.

[0079] Optionally, when the user needs to send downlink data to a certain IoT device on the application platform, the IoT device is recorded as the target IoT device. The user will select the target IoT device and then send downlink data (including but not limited to control instructions, data acquisition instructions, update instructions, etc.). The downlink data will include the device information of the selected target IoT device such as ID, device number, etc. At this time, the IoT device management system receives the downlink data and can know which device access node the target IoT device is specifically connected to and its node address based on the node information and device information, thereby determining the target device access node.

[0080] S102. Receive downlink data through the target device access node, and send the downlink data to the corresponding target IoT device.

[0081] Optionally, after determining the target device access node, the target device access node receives the above-mentioned downlink data, and then sends the downlink data to the corresponding target Internet of Things device to complete the transmission of the downlink data.

[0082] Optionally, in S300, the device access node can obtain the device data of the IoT device connected to the device access node, and then push the device data to the IoT device management system. Similarly, the device data can be pushed to the IoT device management system through the gRPC interface or the http interface, and then pushed to the IoT device management system to upload the device data to the application platform to complete the reporting of the device data.

[0083] In one implementation, the device data is pushed to the application system through the IoT device management system, and step S400 includes steps S410-S430:

[0084] S410: Analyze the data format of the device data through the device object model of the Internet of Things device management system.

[0085] Optionally, when the IoT device uploads device data, it reports it in its own protocol format corresponding to the currently used protocol. At this time, the data format of the device data is analyzed through the device object model of the IoT device management system.

[0086] S420: Determine whether the data format is a preset standard format.

[0087] S430: When the data format is not a preset standard format, determine a target conversion algorithm according to the format type of the data format, and convert the device data into the preset standard format according to the target conversion algorithm.

[0088] Optionally, a preset standard format can be set in advance. For example, if the preset standard format is json, no conversion is required at this time. If the data format is not json, the target conversion algorithm is determined according to the format type of the data format. For example, the target conversion algorithm corresponding to one or more data formats is determined in advance, and then the device data is converted to json format according to the target conversion algorithm. Finally, the data converted to json is uploaded to the application platform to complete the reporting of the device data, ensuring that the device data is applicable to application platforms of different industries and that data storage and management are convenient.

[0089] Similarly, when the IoT device management system obtains downlink data, the device object model of the IoT device management system converts the format of the downlink data into the IoT device's own protocol format, then routes it to the device access node to which the IoT device is connected, and finally sends it to the IoT device.

[0090] Optionally, in step S400, after acquiring the device data, the application system may perform targeted processing on the device data. The processing process is not specifically limited and is adjusted based on actual conditions. For example, in some embodiments, data preprocessing and storage, abnormality judgment, big data analysis, etc. may be performed.

[0091] In one implementation, the lightweight device access method of the embodiment of the present application may further include steps S510-S520:

[0092] S510. Obtain node information of device access nodes registered through a service registration center at regular intervals through an Internet of Things device management system.

[0093] In an embodiment of the present application, if the Internet of Things device management system and the distributed device access system are registered in advance through the service registration center, then the Internet of Things device management system periodically obtains the node information of the device access nodes registered through the service registration center. When there is addition or deletion of device access nodes, the situation is updated in time and the storage space is better managed.

[0094] S520. Through the IoT device management system, a heartbeat request is periodically sent to a device access node registered with a non-service registration center to determine whether the device access node is offline. If offline, the state of the device access node is set to an offline state.

[0095] In an embodiment of the present application, if the Internet of Things device management system and the distributed device access system are not registered through the same service registration center, the Internet of Things device management system periodically sends heartbeat requests to the device access node registered with the non-service registration center to determine whether the device access node is offline. If it is offline, the status of the device access node is set to offline. When registration is not performed, the node status can also be monitored.

[0096] like Figure 4 As shown, it is a specific example. The service of the distributed device access system is started, the node data is reported to the Internet of Things device management system, the node data is stored and the node is monitored, and the node ID is returned when monitoring the specific device access node. When the Internet of Things device is online, an online request is sent to the device access node for device authentication. After the authentication is successful, the Internet of Things device management system returns the authentication result. The device access node of the distributed device access system stores the connection, sets the Internet of Things device to an online state, and records the online node information of the Internet of Things device; asynchronously sends the device online state to the Internet of Things device management system, and the Internet of Things device management system updates the device online state, device node data, device data, etc., and pushes the device online state and device data to the industry application system for data processing to realize business handling.

[0097] By using the method of the embodiment of the present application, at least the following effects can be achieved:

[0098] 1) By setting up a lightweight distributed system architecture based on a distributed device access system, the connection and data transmission of IoT devices of different numbers can be dynamically processed, which can disperse the load and improve the scalability and reliability of the system; at the same time, it can dynamically expand the capacity and improve the robustness and stability of the system.

[0099] 2) By setting up an IoT device management system, the functions of intelligent identification, positioning, tracking, and supervision of IoT devices can be realized.

[0100] 3) To meet the needs of industry applications, the application platform can be privately deployed and lightweight, and can be combined with industry applications at low cost and quickly. At the same time, it can ensure the dynamic expansion of the application platform on the access of devices of different orders of magnitude, improve the efficiency, security and reliability of the application platform in different deployment environments, enhance the scalability and adaptability of the system, reduce deployment costs, and accelerate the penetration and application of Internet of Things technology in multiple fields.

[0101] 4) The service registration and management mechanism of the service registration center is introduced to realize the dynamic registration and management of the IoT device management system and the distributed device access system, allowing new device access nodes to automatically join the system during deployment without manual configuration, significantly improving the flexibility and efficiency of deployment; at the same time, the introduction of the service registration center and the automated device management function greatly simplify the system's operation and maintenance work, reduce the risk of operational errors, and make system maintenance more efficient and convenient. The dynamic resource allocation strategy and intelligent device status management mechanism ensure the effective use of system resources, avoid resource waste, and improve the overall system's operating efficiency and economic benefits;

[0102] 5) Efficient data interaction protocol: Combining gRPC and HTTP interfaces ensures efficient transmission of device information, authentication data, and device object models. The gRPC service (interface) is suitable for providing high-performance data exchange in the presence of a service registry, while the HTTP interface ensures compatibility and convenience in an environment without a service registry.

[0103] Reference Figure 5 , shows a structural block diagram of a lightweight device access device according to an embodiment of the present application, the device may include:

[0104] A determination module, used to determine a distributed device access system, the distributed device access system includes at least one device access node, and the device access node supports multiple transmission protocols;

[0105] An access module, used to connect at least one IoT device to a device access node;

[0106] An acquisition module is used to acquire device data of IoT devices through device access nodes and push the device data to the IoT device management system;

[0107] The push module is used to push device data to the application system through the Internet of Things device management system, and process the device data through the application system; the application system includes an application platform for at least one industry.

[0108] In one embodiment, the lightweight device access apparatus further includes a registration module, and the registration module is used to:

[0109] Registering node information of at least one device access node through a service registration center;

[0110] When an IoT device goes online, the node information is pushed to the IoT device management system through the gRPC interface or http interface.

[0111] In one embodiment, the lightweight device access apparatus further includes a management module, and the management module is used to:

[0112] When at least one application platform sends downlink data, the IoT device management system receives the downlink data and determines the target device access node based on the node information and the device information of the downlink data;

[0113] The downlink data is received through the target device access node and sent to the corresponding target IoT device.

[0114] In one embodiment, the management module is further configured to:

[0115] Through the IoT device management system, the node information of the device access nodes registered through the service registration center is obtained regularly;

[0116] Through the IoT device management system, a heartbeat request is periodically sent to the device access node registered with the non-service registration center to determine whether the device access node is offline. If it is offline, the state of the device access node is set to offline.

[0117] The functions of each module in each device in the embodiments of the present application can be found in the corresponding description in the above method, and will not be repeated here.

[0118] Reference Figure 6 , shows a structural block diagram of an electronic device according to an embodiment of the present application, the electronic device includes: a memory 310 and a processor 320, the memory 310 stores instructions that can be run on the processor 320, and the processor 320 loads and executes the instructions to implement the lightweight device access method in the above embodiment. The number of the memory 310 and the processor 320 can be one or more.

[0119] In one embodiment, the electronic device also includes a communication interface 330 for communicating with external devices and performing data exchange transmission. If the memory 310, the processor 320 and the communication interface 330 are implemented independently, the memory 310, the processor 320 and the communication interface 330 can be interconnected through a bus and complete mutual communication. 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. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 6 Only one thick line is used in the diagram, but this does not mean that there is only one bus or only one type of bus.

[0120] Optionally, in a specific implementation, if the memory 310, the processor 320 and the communication interface 330 are integrated on a chip, the memory 310, the processor 320 and the communication interface 330 can communicate with each other through an internal interface.

[0121] An embodiment of the present application provides a computer-readable storage medium storing a computer program, which, when executed by a processor, implements the lightweight device access method provided in the above embodiment.

[0122] An embodiment of the present application also provides a chip, which includes a processor for calling and executing instructions stored in the memory from the memory, so that a communication device equipped with the chip executes the method provided by the embodiment of the present application.

[0123] An embodiment of the present application also provides a chip, including: an input interface, an output interface, a processor and a memory, wherein the input interface, the output interface, the processor and the memory are connected via an internal connection path, and the processor is used to execute the code in the memory. When the code is executed, the processor is used to execute the method provided in the embodiment of the application.

[0124] It should be understood that the processor may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor, etc. It is worth noting that the processor may be a processor supporting the advanced RISC machines (ARM) architecture.

[0125] Further, optionally, the above-mentioned memory may include a read-only memory and a random access memory, and may also include a non-volatile random access memory. The memory may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, the non-volatile memory may include a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may include a random access memory (RAM), which is used as an external cache. By way of example but not limitation, many forms of RAM are available. For example, static RAM (SRAM), dynamic random access memory (DRAM), synchronous DRAM (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM) and direct rambus RAM (DR RAM).

[0126] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function according to the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium.

[0127] In the description of this specification, the description with reference to the terms "one embodiment", "some embodiments", "example", "specific example" or "some examples" means that the specific features, structures, materials or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the present application. Moreover, the described specific features, structures, materials or characteristics may be combined in any one or more embodiments or examples in a suitable manner. In addition, those skilled in the art may combine and combine different embodiments or examples described in this specification and the features of different embodiments or examples, unless they are contradictory.

[0128] In addition, the terms "first" and "second" are used for descriptive purposes only and should not be understood as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Therefore, a feature defined as "first" or "second" may explicitly or implicitly include at least one of the features. In the description of this application, the meaning of "plurality" is two or more, unless otherwise clearly and specifically defined.

[0129] Any process or method description in the flow chart or otherwise described herein can be understood to represent a module, fragment or portion of a code including one or more executable instructions for implementing the steps of a specific logical function or process. And the scope of the preferred embodiment of the present application includes other implementations, in which the functions may not be performed in the order shown or discussed, including in a substantially simultaneous manner or in a reverse order according to the functions involved.

[0130] The logic and / or steps represented in the flowchart or otherwise described herein, for example, can be considered as an ordered list of executable instructions for implementing logical functions, which can be embodied in any computer-readable medium for use by an instruction execution system, apparatus or device (such as a computer-based system, a system including a processor or other system that can fetch instructions from an instruction execution system, apparatus or device and execute instructions), or used in combination with these instruction execution systems, apparatuses or devices.

[0131] It should be understood that the various parts of the present application can be implemented with hardware, software, firmware or a combination thereof. In the above embodiments, multiple steps or methods can be implemented with software or firmware stored in a memory and executed by a suitable instruction execution system. All or part of the steps of the above embodiment method can be completed by instructing the relevant hardware through a program, which can be stored in a computer-readable storage medium, and when the program is executed, it includes one of the steps of the method embodiment or a combination thereof.

[0132] In addition, each functional unit in each embodiment of the present application can be integrated into a processing module, or each unit can exist physically separately, or two or more units can be integrated into one module. The above-mentioned integrated module can be implemented in the form of hardware or in the form of a software functional module. If the above-mentioned integrated module is implemented in the form of a software functional module and sold or used as an independent product, it can also be stored in a computer-readable storage medium. The storage medium can be a read-only memory, a disk or an optical disk, etc.

[0133] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any technician familiar with the technical field can easily think of various changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

1. A lightweight device access method, characterized in that: include: Determine a distributed device access system, the distributed device access system includes at least one device access node, the device access node supports multiple transmission protocols; Connecting at least one IoT device to the device access node; Acquire the device data of the IoT device through the device access node, and push the device data to the IoT device management system; Pushing the device data to the application system through the IoT device management system, and processing the device data through the application system; The application system includes an application platform for at least one industry.

2. The lightweight device access method according to claim 1, characterized in that: The method further comprises: Registering node information of at least one of the device access nodes through a service registration center; When the IoT device is online, the node information is pushed to the IoT device management system through the gRPC interface or the http interface.

3. The lightweight device access method according to claim 2, characterized in that: The method further comprises: When at least one of the application platforms sends downlink data, the IoT device management system receives the downlink data and determines a target device access node based on the node information and device information of the downlink data; The downlink data is received through the target device access node, and the downlink data is sent to the corresponding target Internet of Things device.

4. The lightweight device access method according to claim 2, characterized in that: When the IoT device is online, pushing the node information to the IoT device management system through the gRPC interface or the http interface includes: When the IoT device is online, and when the device access node corresponding to the IoT device is registered through the service registration center, the node information of the device access node is pushed to the IoT device management system through the gRPC interface; When the IoT device is online, and when the device access node corresponding to the IoT device is not registered with the service registration center, the node information of the device access node is pushed to the IoT device management system through the http interface.

5. The lightweight device access method according to claim 4, characterized in that: The method further comprises: Through the Internet of Things device management system, node information of device access nodes registered through the service registration center is regularly obtained; Through the Internet of Things device management system, a heartbeat request is periodically sent to a device access node that is not registered with the service registration center to determine whether the device access node is offline. If it is offline, the state of the device access node is set to an offline state.

6. The lightweight device access method according to any one of claims 1 to 5, characterized in that: The pushing of the device data to the application system through the Internet of Things device management system includes: Analyzing the data format of the device data through the device object model of the Internet of Things device management system; Determining whether the data format is a preset standard format; When the data format is not a preset standard format, a target conversion algorithm is determined according to the format type of the data format, and the device data is converted into a preset standard format according to the target conversion algorithm.

7. The lightweight device access method according to any one of claims 1 to 5, characterized in that: Determining the distributed device access system includes: In response to the construction instruction, construct at least one device access node, wherein the device access node is used to connect one or more Internet of Things devices; In response to the deployment instruction, the device access node is deployed to one or more servers.

8. A lightweight device access device, characterized in that: include: A determination module, configured to determine a distributed device access system, wherein the distributed device access system includes at least one device access node, and the device access node supports multiple transmission protocols; An access module, used to connect at least one IoT device to the device access node; An acquisition module, used to acquire device data of the IoT device through the device access node, and push the device data to the IoT device management system; A push module, used to push the device data to the application system through the IoT device management system, and process the device data through the application system; The application system includes an application platform for at least one industry.

9. An electronic device, characterized in that: include: A processor and a memory, wherein the memory stores instructions, and the instructions are loaded and executed by the processor to implement the method according to any one of claims 1 to 7.

10. A computer-readable storage medium, wherein a computer program is stored in the computer-readable storage medium, and when the computer program is executed, the method according to any one of claims 1 to 7 is implemented.

Images