A method for binding IoT devices, a terminal, and an IoT device.
By configuring a target server with specific services for the IoT device binding method, the problems of high server configuration costs and heavy operating load are solved, achieving efficient terminal management and data security.
Patent Information
- Application Number
- CN202211333439.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2022-10-28
- Publication Date
- 2026-11-17
- Estimated Expiration
- 2042-10-28
AI Technical Summary
In existing technologies, the IoT device binding methods require each server to serve all terminals, resulting in high server configuration costs and heavy operating load.
By responding to the client's binding request, sending verification information, configuring the service content corresponding to the binding information, selecting a target server for the client, building and encrypting the binding relationship, and the target server only providing targeted services.
It reduces the difficulty and cost of server configuration, lowers the operating load, and improves data security.
Smart Images

Figure CN115811474B_ABST
Abstract
Description
Technical Field
[0001] This disclosure relates to the field of Internet of Things (IoT) technology, specifically to an IoT device binding method, a terminal, and an IoT device. Background Technology
[0002] In recent years, with the increasingly widespread application of IoT devices, the control and management of these devices has become a crucial means of realizing intelligent applications in the IoT field. To achieve control over IoT devices, it is necessary to first bind the terminal to the IoT device.
[0003] For example, patent CN201710210112.3 discloses an IoT device binding method, which includes: broadcasting a request message to establish a connection with an IoT device; after receiving a response message from an IoT device to the request message, establishing a communication connection with the IoT device that sent the response message; based on the communication connection, receiving a notification message from the IoT device indicating whether the IoT device has successfully registered with an IoT server; based on the notification message, if it is determined that the IoT device has failed to register with the IoT server, sending an instruction message to the failed IoT device to re-register with the IoT server, until it is determined that all IoT devices that have established communication connections have successfully registered with the IoT server. This invention also discloses a terminal and an IoT device.
[0004] In some IoT device binding methods in the county, after the terminal is successfully bound to the server, the terminal can send data to the server and receive relevant instructions from the server. However, after the terminal is bound to the IoT device, usually one server is used to serve all terminals in the area. Alternatively, in order to alleviate the access pressure of the terminals, multiple servers are configured to serve the terminals in the area. However, if each server is configured to serve all terminals, not only is the configuration cost of the server high, but the server's operating load is also large.
[0005] It should be noted that the information disclosed in the background section above is only used to enhance the understanding of the background of this disclosure, and therefore may include information that does not constitute prior art known to those skilled in the art. Summary of the Invention
[0006] The purpose of this disclosure is to provide an IoT device binding method, terminal, and IoT device, thereby overcoming, to at least some extent, the situation where configuring each server to serve all terminals is not only costly in terms of server configuration but also results in a heavy server load due to limitations and defects in related technologies.
[0007] Other features and advantages of this disclosure will become apparent from the following detailed description, or may be learned in part from practice of this disclosure.
[0008] According to a first aspect of this disclosure, an IoT device binding method is provided, comprising:
[0009] In response to a binding request sent by a client, the system sends verification information to the client, receives binding information from the client, and configures the service content corresponding to the binding information based on the binding information.
[0010] Configure the target server that provides the service content to the client based on the service content;
[0011] A binding relationship is established between the target server and the client, and the binding relationship is encrypted; the binding relationship is used by the target server to send control commands to the client, and by the client to send detection data to the target server.
[0012] Optionally, the steps of responding to a binding request sent by the client, sending verification information to the client, receiving binding information returned by the client, and configuring service content corresponding to the binding information based on the binding information include:
[0013] Users send a binding request to the server through the client;
[0014] The server receives the binding request and sends standardized verification information back to the client;
[0015] The user inputs the binding information corresponding to the verification information into the server through the client;
[0016] The server receives the binding information and invokes a local component, which configures the service content corresponding to the binding information for the client based on the binding information.
[0017] Optionally, the steps to return standardized verification information to the client include:
[0018] Construct a standard information database, which includes multiple verification information items;
[0019] The verification information is sent to the client.
[0020] Optionally, the step of configuring the target server for providing the service content to the client based on the service content includes:
[0021] Configure multiple sub-servers, each of which has different service content;
[0022] Establish the association between the sub-server and the service content;
[0023] Based on the aforementioned association, a sub-server corresponding to the service content is configured for the client; the sub-server is the target server.
[0024] Optionally, the step of establishing the binding relationship between the target server and the client includes:
[0025] Configure a security level for the service content;
[0026] The binding relationship between the target server and the client is established based on the security level.
[0027] Optionally, the step of encrypting the binding relationship includes:
[0028] Based on the security level, configure encryption rules corresponding to the security level for the binding relationship;
[0029] The binding relationship is encrypted using the encryption method described above, and the encryption rules are stored.
[0030] Optionally, the encryption rules are cryptographic encryption rules and / or blockchain-based encryption rules; the security levels include: Level I and Level II; Level I has a higher security level than Level II.
[0031] When the security level of the service content is Level II, configure password encryption rules for the binding relationship;
[0032] When the security level of the service content is Level I, configure blockchain-based encryption rules for the binding relationship.
[0033] Optionally, the server is also configured with a perception layer and an edge computing layer;
[0034] The perception layer is used to identify the client and collect the client's detection data;
[0035] The edge computing layer is used to receive the detection data and parse the detection data to obtain a parsing result; wherein, the edge computing layer parses the detection data including:
[0036] The detection data is transmitted to a predetermined folder, and the parsing formula corresponding to the detection data is invoked. The parsing formula is used to split the detection data into multiple computing nodes. The edge computing layer parses each computing node to obtain the parsing result corresponding to each computing node. The parsing results are cached and fed back to the client.
[0037] According to a second aspect of this disclosure, a terminal is provided, the terminal being equipped with software for interacting with the above-described Internet of Things (IoT) device binding method.
[0038] According to a third aspect of this disclosure, an Internet of Things (IoT) device is provided, characterized in that it comprises:
[0039] Processor; and
[0040] Memory for storing the executable instructions of the processor;
[0041] The processor is configured to execute the above-described IoT device binding method by executing the executable instructions.
[0042] This disclosure discloses an IoT device binding method, terminal, and IoT device. The IoT device binding method includes: responding to a binding request sent by a client, sending verification information to the client, receiving binding information returned by the client, and configuring service content corresponding to the binding information based on the binding information; configuring a target server providing the service content for the client based on the service content; constructing a binding relationship between the target server and the client, and encrypting the binding relationship; the binding relationship is used for the target server to send control commands to the client, and for the client to send detection data to the target server. By determining the service content based on the binding information and the target server based on the service content, and using the target server as the server for the current client, this application's solution provides a server that offers targeted services. The server in this application does not need to be configured with all functions; only functions corresponding to the corresponding client need to be configured, effectively reducing the server's configuration difficulty and cost, and lowering the server's operating load.
[0043] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and are not intended to limit this disclosure. Attached Figure Description
[0044] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this disclosure and, together with the description, serve to explain the principles of this disclosure. It is obvious that the drawings described below are merely some embodiments of this disclosure, and those skilled in the art can obtain other drawings based on these drawings without any inventive effort.
[0045] Figure 1 The schematic diagram illustrates a system architecture in an exemplary embodiment of the present disclosure;
[0046] Figure 2 This schematically illustrates a flowchart of an IoT device pairing method in an exemplary embodiment of the present disclosure;
[0047] Figure 3This schematic diagram illustrates a framework diagram of a server connection in an exemplary embodiment of the present disclosure;
[0048] Figure 4 This schematic diagram illustrates the composition of an Internet of Things (IoT) device according to an exemplary embodiment of the present disclosure.
[0049] Figure 5 This schematic diagram illustrates the composition of a terminal in an exemplary embodiment of the present disclosure. Detailed Implementation
[0050] Exemplary embodiments will now be described more fully with reference to the accompanying drawings. However, these exemplary embodiments can be implemented in many forms and should not be construed as limited to the examples set forth herein; rather, they are provided so that this disclosure will be more comprehensive and complete, and will fully convey the concept of the exemplary embodiments to those skilled in the art. The described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.
[0051] Furthermore, the accompanying drawings are merely illustrative of this disclosure and are not necessarily drawn to scale. The same reference numerals in the drawings denote the same or similar parts, and therefore repeated descriptions of them will be omitted. Some block diagrams shown in the drawings are functional entities and do not necessarily correspond to physically or logically independent entities. These functional entities may be implemented in software, in one or more hardware modules or integrated circuits, or in different network and / or processor devices and / or microcontroller devices.
[0052] The block diagrams shown in the accompanying drawings are merely functional entities and do not necessarily correspond to physically independent entities. That is, these functional entities can be implemented in software, in one or more hardware modules or integrated circuits, or in different network and / or processor devices and / or microcontroller devices.
[0053] The flowcharts shown in the accompanying drawings are merely illustrative and do not necessarily include all content and operations / steps, nor do they necessarily have to be performed in the described order. For example, some operations / steps can be broken down, while others can be combined or partially combined; therefore, the actual execution order may change depending on the specific circumstances.
[0054] This disclosure first provides a system architecture for an IoT device binding method in exemplary embodiments. (See reference...) Figure 1As shown, the system architecture may include clients 101, 102, and 103, a network 104, and a server 105. Network 104 serves as the medium for providing a communication link between clients 101, 102, and 103 and server 105. Network 104 may include various connection types, such as wired or wireless communication links, or fiber optic cables, etc.
[0055] Users can use clients 101, 102, and 103 to interact with server 105 via network 104 to receive or send data, etc. The clients can also establish a binding relationship with the server. Various sensors can be installed on clients 101, 102, and 103, such as pressure sensors, light intensity sensors, gas content detection sensors, etc.
[0056] Clients 101, 102, and 103 can be various smart devices with displays, which can interact with and control various sensors on their devices.
[0057] Server 105 can be a server that provides various services, such as a backend management server that supports information query websites browsed by users using clients 101, 102, and 103 (for example only). The server can bind to the terminal, receive data from the terminal, and send relevant instructions to the client. The terminal can control various sensors to collect data and then transmit the data collected by the various sensors to the server through the network for processing.
[0058] It should be noted that the IoT device binding method provided in this embodiment is executed by server 105. However, those skilled in the art will understand that the IoT device binding method provided in this embodiment requires interaction between client 101, 102, or 103 and server 105.
[0059] Taking the IoT device binding method as an example, the IoT device binding method provided in this solution can be completed by the interaction between the server 105 and the client. The specific execution process is as follows:
[0060] Upon initial use, the user sends a binding request to the server via the client. The server then sends verification information to the client, which may include: the type of detection data (e.g., gas detection, temperature and humidity detection, displacement detection, pressure detection, etc.), the client's name, and model. The user then sends this information back to the server via the client; this information constitutes the binding information described in this application. After receiving this information, the server configures corresponding service content based on the processing method of the binding information. The service content refers to the means of processing the aforementioned binding information, such as processing formulas or algorithms. The server then selects a corresponding target server based on the service content, whereby the target server is specifically designed to process the aforementioned service content. At this point, the current client is bound to the target server, establishing a binding relationship. Subsequently, the client can send corresponding detection data to the target server based on this binding relationship. The target server processes the detection data using corresponding formulas or algorithms to obtain processing results, thereby enabling monitoring of the physical object or space where the aforementioned client is installed through the processing results.
[0061] The data detection method provided in this disclosure can be applied to the following application scenarios:
[0062] For example, in a greenhouse, it is necessary to monitor carbon dioxide and light intensity in real time. The client application of this application can be installed in the greenhouse, and a carbon dioxide sensor and a light sensor can be configured on the client. After installation, the client needs to be bound to the corresponding server for processing of sensor data. Therefore, the user can send a binding request to the main server through the client. After receiving the binding request, the main server sends verification information to the client, including: the type of detection data and device information. The user selects the corresponding options through the client. In this scenario, the user selects: carbon dioxide sensor and light sensor, and the client interface type is 485 or PLC. The client uses this information as the binding information. After receiving the binding information, the server configures a server with carbon dioxide and light sensor data processing capabilities according to the binding information, and can receive servers whose data types match the 485 or PLC interface data types as target servers. Then, the main server establishes a binding relationship between the target server and the client. This binding relationship is used for the target server to send control commands to the client, and for the client to send detection data to the target server. This setup allows for more targeted configuration of data processing servers for clients, thereby reducing overall server power consumption and configuration costs. It eliminates the need to configure all servers to handle all data, thus simplifying server configuration.
[0063] Based on the above system architecture 100, this disclosure proposes an IoT device binding method, including: steps S210-S230.
[0064] Step S210. In response to the binding request sent by the client, send verification information to the client, receive the binding information returned by the client, and configure the service content corresponding to the binding information based on the binding information.
[0065] Step S220. Configure the target server for providing the service content to the client based on the service content.
[0066] Step S230. Establish a binding relationship between the target server and the client, and encrypt the binding relationship; the binding relationship is used by the target server to send control commands to the client, and by the client to send detection data to the target server.
[0067] This disclosure discloses an IoT device binding method, terminal, and IoT device. The IoT device binding method includes: responding to a binding request sent by a client, sending verification information to the client, receiving binding information returned by the client, and configuring service content corresponding to the binding information based on the binding information; configuring a target server providing the service content for the client based on the service content; constructing a binding relationship between the target server and the client, and encrypting the binding relationship; the binding relationship is used by the target server to send control commands to the client, and by the client to send detection data to the target server. By determining the service content based on the binding information and the target server based on the service content, and using the target server as the server for the current client, this application's solution provides a server that offers targeted services. The server in this application does not need to be configured with all functions, only those corresponding to the corresponding client, effectively reducing the server's configuration difficulty and cost, and lowering the server's operating load. Furthermore, by encrypting the binding relationship, after the client goes online, it can be verified using the bound information to log in to the server, thus effectively improving data security.
[0068] The following will describe in more detail each step of the IoT device binding method in this exemplary embodiment, with reference to the accompanying drawings and embodiments.
[0069] Step S210. In response to the binding request sent by the client, send verification information to the client, receive the binding information returned by the client, and configure the service content corresponding to the binding information based on the binding information.
[0070] In this example implementation, this step is performed by the server. The server responds to the binding request sent by the client by sending verification information to the client and configures the service content corresponding to the binding information based on the binding information.
[0071] In this example embodiment, the aforementioned client can be a device for managing various sensors, which can be equipped with various sensors, such as gas detection sensors, temperature and humidity detection sensors, displacement detection sensors, pressure detection sensors, etc. This application does not limit the types of sensors. For example, when it is necessary to detect whether a manhole cover has moved, a displacement sensor can be configured. When it is necessary to detect the carbon dioxide concentration in a greenhouse, a carbon dioxide sensor can be configured. Users can configure the corresponding detection sensors for the client according to their actual detection needs.
[0072] In this example implementation, the server sends verification information to the client. This verification information can be in a standardized format, facilitating server collection, organization, and processing. For example, the verification information could be the sensor type, with sensor options configured in a submenu for that type. Users can directly select from these options. Of course, this verification information needs to be maintained regularly by administrators, such as adding or modifying sensor types. The verification information can also include the serial port used by the client to receive data, such as a RS-485 serial port. Based on the data receiving serial port, the corresponding data receiving protocol can be obtained according to the serial port type, ensuring that the selected target server has the same data transmission protocol as the client. This avoids protocol conversion during data reception, which would reduce the target server's processing efficiency. In this embodiment, middleware can be configured based on a URL for sending verification information and collecting binding information.
[0073] In this example implementation, based on the binding information, the server can configure the service content corresponding to the binding information. The server can obtain the service content desired by the client that sent the binding information based on the content fed back by the binding information. For example, when the binding information includes: carbon dioxide sensor and 485 serial port, the server can obtain that the service content required by the current client is to process the relevant data of the carbon dioxide sensor, and that the data transmission protocol needs to match the 485 serial port. At this time, the server clarifies the service content required by the current client.
[0074] Step S220. Configure the target server for providing the service content to the client based on the service content.
[0075] In this example implementation, based on the service content obtained in step S210, this step requires configuring a target server corresponding to the service content. It can be understood that the role of the target server in this step is to receive the data from the current client and process the data.
[0076] For example:
[0077] When the binding information includes: carbon dioxide sensor and 485 serial port, the server can then determine that the current client requires services related to processing carbon dioxide sensor data, and that the data transmission protocol needs to match the 485 serial port. At this point, the server clearly defines the services required by the current client. The target server then needs to have the capability to process carbon dioxide sensor data and the ability to receive and process data from the 485 serial port without protocol conversion.
[0078] Step S230. Establish a binding relationship between the target server and the client, and encrypt the binding relationship; the binding relationship is used by the target server to send control commands to the client, and by the client to send detection data to the target server.
[0079] In this example implementation, the binding relationship between the target server and the client can be established based on existing verification methods. Each client corresponds to one target server, and one target server can correspond to multiple clients. To improve the security of the binding relationship and avoid data transmission errors between different clients, the binding relationship is encrypted in this step. The encryption method can be the existing username and password verification or a more secure blockchain-based verification method. This application does not limit the above encryption methods.
[0080] As can be seen, the target servers in this application all have specific data processing functions, and their functions are more singular, which is conducive to improving the processing power of the target servers. In addition, the target servers require fewer configuration functions compared to traditional servers, which simplifies the configuration difficulty of the target servers.
[0081] In this example implementation, the binding relationship is used for the target server to send control commands to the client, and for the client to send detection data to the target server. Once the client and target server establish a binding relationship, the client can transmit its collected data to the target server via the network, so that the target server can process it and obtain the processing results. Different clients can collect different data, and correspondingly, different data are processed by different target servers, resulting in different results. In addition, the target server can also send commands to the client, such as detection cycle commands and detection duration commands. After receiving these commands, the client executes the corresponding actions.
[0082] In one specific implementation, the steps of responding to a binding request sent by a client, sending verification information to the client, receiving binding information returned by the client, and configuring service content corresponding to the binding information based on the binding information include: a user sending a binding request to a server through a client; the server receiving the binding request and returning standardized verification information to the client; the user inputting the binding information corresponding to the verification information to the server through the client; the server receiving the binding information and invoking a local component, the local component configuring service content corresponding to the binding information for the client based on the binding information.
[0083] In one specific implementation, the step of feeding back standardized verification information to the client includes: constructing a standard information database, which includes multiple pieces of the verification information; and sending the verification information to the client.
[0084] In this example implementation, standardized verification information is beneficial for improving the processing efficiency of the target server and for simplifying the consistency of verification information sent by users through the client, thus avoiding the server's inability to process different types of information sent by different clients.
[0085] For example, verification information could include the sensor type, with sensor options configured in a submenu under that sensor type. Users can directly select from these options. Of course, this verification information needs to be maintained regularly by administrators, such as adding or modifying sensor types. Verification information can also include the serial port used by the client to receive data, such as a RS-485 serial port. Based on the data receiving serial port, the corresponding data receiving protocol can be obtained according to the serial port type, ensuring that the selected target server has the same data transmission protocol as the client. This avoids protocol conversion during data reception, which would reduce the target server's processing efficiency. In this embodiment, middleware can be configured based on a URL for sending verification information and collecting binding information.
[0086] In one specific implementation, the step of configuring a target server for providing the service content to the client based on the service content includes: configuring multiple sub-servers, each of which has different service content; establishing an association between the sub-servers and the service content; and configuring a sub-server corresponding to the service content for the client based on the association; wherein the sub-server is the target server.
[0087] In this example implementation, different sub-servers have different processing functions. For instance, there are three sub-servers: a, b, and c. Sub-server a has the ability to process temperature sensor data and carbon dioxide sensor data, and its data supports the PLC serial port data protocol. Sub-server b has the ability to process displacement sensor data, and its data supports the PLC serial port data protocol. Sub-server c has the ability to process pressure sensor data, and its data supports the RS485 serial port data protocol. Therefore, based on the binding information provided by the user, a sub-server that matches the binding information can be selected.
[0088] In one specific implementation, the step of constructing the binding relationship between the target server and the client includes: configuring a security level for the service content; and constructing the binding relationship between the target server and the client based on the security level.
[0089] In this example implementation, a hierarchical strategy is also provided. The binding relationship between the target server and the client is constructed based on the level of the service content. For example, if the data detected by the corresponding sensor is confidential, to avoid data leakage, the binding relationship between the server and the client can be set at a high security level. In this case, the binding relationship has a higher level, and correspondingly, the verification information and binding information used in the verification process are encrypted using high-level encryption methods to prevent the verification information and binding information stored on the server from being altered, which could lead to the client using incorrect information to log in to the target server.
[0090] In one specific implementation, the step of encrypting the binding relationship includes: configuring encryption rules corresponding to the security level for the binding relationship based on the security level; encrypting the binding relationship according to the encryption method; and storing the encryption rules.
[0091] In this example implementation, different security level encryption rules are configured according to different security levels, and encryption methods are used to encrypt the binding relationship. It can be understood that when the client successfully binds with the target server, the client needs to provide corresponding verification, such as a password, to log in to the target server. The encryption of the binding relationship mentioned in this embodiment is actually to encrypt the verification data between the bound client and the login target server, so as to ensure the security of the verification data during the login process, and prevent clients that have not established a binding relationship with the target server from accessing the target server due to the tampering of the verification data during the login process, thereby avoiding data leakage.
[0092] In one specific implementation, the encryption rule is a cryptographic encryption rule and / or a blockchain-based encryption rule; the security level includes: Level I and Level II; Level I has a higher security level than Level II; when the security level of the service content is Level II, a cryptographic encryption rule is configured for the binding relationship; when the security level of the service content is Level I, a blockchain-based encryption rule is configured for the binding relationship.
[0093] As a specific implementation method, the security level can be divided into Level I and Level II, and different levels of encryption can be applied to different binding relationships according to different security levels.
[0094] In one specific embodiment, the server is further configured with a perception layer and an edge computing layer; the perception layer is used to identify the client and collect the client's detection data; the edge computing layer is used to receive the detection data and parse the detection data to obtain a parsing result; wherein, the edge computing layer parses the detection data by: transferring the detection data to a predetermined folder, calling the parsing formula corresponding to the detection data, using the parsing formula to split the detection data into multiple computing nodes, the edge computing layer parses each computing node respectively to obtain the parsing result corresponding to each computing node, caching each parsing result, and feeding it back to the client.
[0095] In this example implementation, the perception layer is mainly responsible for identifying the devices (clients) connected to the gateway and collecting data. Multiple threads can be used to collect data from devices connected to different interfaces. Specifically, the binding information generated by the client can be read first, and after determining the type of the binding information, it can be copied into different JSON objects. Therefore, in the technical solution of this application, the perception layer can also determine the type (service content) of the binding information based on the binding information.
[0096] In this example implementation, the formulas required for edge computing are written into the configuration client according to the prescribed method, and the generated edge computing configuration file is transferred to the designated folder of the network management system. At the beginning of the gateway program's execution, the file is read into the program cache for immediate use. This design decomposes the edge computing formulas into pairs of computation nodes, facilitating the calculation of long formulas. The data processing layer has completed the data parsing and stored it in the linked list node cache of each device, stored in order of register address. The linked list node also contains a mapping table of device register addresses and register identifiers, so data can be directly accessed using the register identifier when using this data.
[0097] The following reference Figure 4 To describe an Internet of Things (IoT) device 400 according to this embodiment of the present invention. Figure 4 The IoT device 400 shown is merely an example and should not impose any limitations on the functionality and scope of use of the embodiments of the present invention.
[0098] like Figure 4 As shown, the Internet of Things (IoT) device 400 is presented in the form of a general-purpose computing device. The components of the IoT device 400 may include, but are not limited to: at least one processing unit 410, at least one storage unit 420, and a bus 430 connecting different system components (including storage unit 420 and processing unit 410).
[0099] The storage unit stores program code that can be executed by the processing unit 410, causing the processing unit 410 to perform the steps described in the "Exemplary Methods" section of this specification according to various exemplary embodiments of the present invention. For example, the processing unit 410 can perform actions such as... Figure 2 Step S210: In response to the binding request sent by the client, send verification information to the client, receive binding information returned by the client, and configure service content corresponding to the binding information based on the binding information. Step S220: Configure a target server providing the service content for the client based on the service content. Step S230: Establish a binding relationship between the target server and the client, and encrypt the binding relationship; the binding relationship is used for the target server to send control commands to the client, and for the client to send detection data to the target server.
[0100] Storage unit 420 may include a readable medium in the form of a volatile storage unit, such as random access memory (RAM) 4201 and / or cache memory 4202, and may further include a read-only memory (ROM) 4203.
[0101] Storage unit 420 may also include a program / utility 4204 having a set (at least one) program module 4205, such program module 4205 including but not limited to: operating system, one or more application programs, other program modules and program data, each or some combination of these examples may include an implementation of a network environment.
[0102] Bus 430 can represent one or more of several types of bus structures, including a memory cell bus or memory cell controller, a peripheral bus, a graphics acceleration port, a processing unit, or a local bus using any of the various bus structures.
[0103] The IoT device 400 can also communicate with one or more external devices 300 (e.g., keyboards, pointing devices, Bluetooth devices, etc.), one or more devices that enable users to interact with the IoT device 400, and / or any device that enables the IoT device 400 to communicate with one or more other computing devices (e.g., routers, modems, etc.). This communication can be performed via input / output (I / O) interface 450. Furthermore, the IoT device 400 can also communicate with one or more networks (e.g., local area networks (LANs), wide area networks (WANs), and / or public networks, such as the Internet) via network adapter 460. As shown, network adapter 460 communicates with other modules of the IoT device 400 via bus 430. It should be understood that, although not shown in the figures, other hardware and / or software modules can be used in conjunction with the IoT device 400, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems.
[0104] From the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments described herein can be implemented by software or by combining software with necessary hardware. Therefore, the technical solutions according to the embodiments of this disclosure can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (such as a CD-ROM, USB flash drive, external hard drive, etc.) or on a network, including several instructions to cause a computing device (such as a personal computer, server, terminal device, or network device, etc.) to execute the methods according to the embodiments of this disclosure.
[0105] In exemplary embodiments of this disclosure, a computer-readable storage medium is also provided, having stored thereon a terminal capable of implementing the methods described above. In some possible implementations, various aspects of the invention may also be implemented as a terminal including program code that, when the terminal is run on a client, causes the client to perform the steps described in the "Exemplary Methods" section of this specification according to various exemplary embodiments of the invention.
[0106] refer to Figure 5 As shown, a terminal 500 for implementing the above-described method according to an embodiment of the present invention is described. It may employ a portable compact disc read-only memory (CD-ROM) and include program code, and can run on a client, such as a personal computer. However, the terminal of the present invention is not limited thereto. In this document, the readable storage medium may be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device.
[0107] The terminal may employ any combination of one or more readable media. The readable media may be a readable signal medium or a readable storage medium. The readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples (a non-exhaustive list) of readable storage media include: electrical connections having one or more wires, portable disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.
[0108] Computer-readable signal media may include data signals propagated in baseband or as part of a carrier wave, carrying readable program code. Such propagated data signals may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. A readable signal medium may also be any readable medium other than a readable storage medium, capable of sending, propagating, or transmitting programs for use by or in conjunction with an instruction execution system, apparatus, or device.
[0109] The program code contained on the readable medium may be transmitted using any suitable medium, including but not limited to wireless, wired, optical fiber, RF, etc., or any suitable combination thereof.
[0110] Program code for performing the operations of this invention can be written in any combination of one or more programming languages, including object-oriented programming languages such as Java and C++, and conventional procedural programming languages such as C or similar languages. The program code can execute entirely on the user's computing device, partially on the user's device, as a standalone software package, partially on the user's computing device and partially on a remote computing device, or entirely on a remote computing device or server. In cases involving remote computing devices, the remote computing device can be connected to the user's computing device via any type of network, including a local area network (LAN) or a wide area network (WAN), or it can be connected to an external computing device (e.g., via the Internet using an Internet service provider).
[0111] Furthermore, the above figures are merely illustrative of the processes included in the method according to exemplary embodiments of the present invention, and are not intended to be limiting. It is readily understood that the processes shown in the above figures do not indicate or limit the temporal order of these processes. Additionally, it is readily understood that these processes may be executed synchronously or asynchronously, for example, in multiple modules.
[0112] Other embodiments of this disclosure will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of this disclosure that follow the general principles of this disclosure and include common knowledge or customary techniques in the art not disclosed herein. The specification and embodiments are to be considered exemplary only, and the true scope and spirit of this disclosure are indicated by the claims.
[0113] It should be understood that this disclosure is not limited to the precise structures described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this disclosure is limited only by the appended claims.
Claims
1. A method for binding Internet of Things (IoT) devices, characterized in that, include: In response to a binding request sent by a client, the system sends verification information to the client, receives binding information from the client, and configures the service content corresponding to the binding information based on the binding information. Configure the target server that provides the service content to the client based on the service content; A binding relationship is established between the target server and the client, and the binding relationship is encrypted; the binding relationship is used by the target server to send control commands to the client, and by the client to send detection data to the target server; The step of configuring the target server for providing the service content to the client based on the service content includes: Configure multiple sub-servers, each of which has different service content; Establish the association between the sub-server and the service content; Based on the aforementioned association, a sub-server corresponding to the service content is configured for the client; the sub-server is the target server. The steps for establishing the binding relationship between the target server and the client include: Configure a security level for the service content; Based on the security level, a binding relationship is established between the target server and the client; The step of encrypting the binding relationship includes: Based on the security level, configure encryption rules corresponding to the security level for the binding relationship; The binding relationship is encrypted according to the encryption rules, and the encryption rules are stored. The server is also configured with a perception layer and an edge computing layer; The perception layer is used to identify the client and collect the client's detection data; The edge computing layer is used to receive the detection data and parse the detection data to obtain a parsing result; wherein, the edge computing layer parses the detection data including: The detection data is transmitted to a predetermined folder, and the parsing formula corresponding to the detection data is invoked. The parsing formula is used to split the detection data into multiple computing nodes. The edge computing layer parses each computing node to obtain the parsing result corresponding to each computing node. The parsing results are cached and fed back to the client.
2. The IoT device binding method according to claim 1, characterized in that, The steps involve responding to a binding request sent by the client, sending verification information to the client, receiving binding information returned by the client, and configuring the service content corresponding to the binding information based on the binding information, including: Users send a binding request to the server through the client; The server receives the binding request and sends standardized verification information back to the client; The user inputs the binding information corresponding to the verification information into the server through the client; The server receives the binding information and invokes a local component, which configures the service content corresponding to the binding information for the client based on the binding information.
3. The IoT device binding method according to claim 2, characterized in that, The steps involved in sending standardized verification information back to the client include: A standard information database is constructed, which includes multiple verification information items; The verification information is sent to the client.
4. The IoT device binding method according to claim 3, characterized in that, The encryption rules are cryptographic encryption rules and / or blockchain-based encryption rules; the security levels include: Level I and Level II; Level I has a higher security level than Level II. When the security level of the service content is Level II, configure password encryption rules for the binding relationship; When the security level of the service content is Level I, configure blockchain-based encryption rules for the binding relationship.
5. An Internet of Things (IoT) device, characterized in that, include: processor; as well as Memory for storing the executable instructions of the processor; The processor is configured to execute the IoT device binding method according to any one of claims 1 to 4 by executing the executable instructions.
Citation Information
Patent Citations
Internet of things equipment binding method, terminal and internet of things equipment
CN108667778A
Service node selection method and device, device management method and device, , system and medium
CN110753126A
Equipment data processing method and device, equipment and medium
CN113055478A
Big data cleaning method and device, computer equipment and storage medium
CN113836131A
