Equipment access system and method based on dynamic registration

Abstract

The invention relates to the technical field of Internet of Things, in particular to a device access system and method based on dynamic registration, the system comprises a dynamic registration service system and an Internet of Things platform system, the dynamic registration service system is used for obtaining a dynamic registration request sent by a device to be accessed and authenticating the dynamic registration request, the Internet of Things intermediate station system matches a target Internet of Things intermediate station according to the device type and the protocol type of the device to be accessed, and sends scheduling information to the dynamic registration service system; business of a traditional system is separated, the dynamic registration service system is only responsible for registration and authentication of the equipment and does not involve the function of a business level, the traditional business part is separated to a platform system in the Internet of Things to be carried out, the overall safety of the system is greatly improved, and the security of the system is greatly improved. And unified management of devices of different types and different protocols is facilitated.

Description

Technical Field

[0001] This application relates to the field of Internet of Things (IoT) technology, and in particular to a device access system and method based on dynamic registration. Background Technology

[0002] In practical applications, it's often necessary to connect various types of devices to a unified platform for centralized management and comprehensive analysis. For example, in energy management, electricity meters, water meters, routers, and smart sockets need to be connected to the same energy management platform simultaneously to comprehensively and accurately grasp various energy consumption data. However, due to significant differences in communication protocols and access standards among these devices, managing them through a unified platform is quite difficult.

[0003] Currently, there are two main solutions. The first is to connect different protocols and types of devices to different server ports or physical servers. Taking a communication system and method disclosed in patent application CN117749763A as an example, in this solution, terminal devices establish communication connections with multiple dedicated service lines, and each service line is equipped with an independent service server. This solution is relatively simple to develop and easy to implement. However, on the device side, each device must have separate server information and encryption / decryption information to successfully connect to the platform, making true unified access and centralized management impossible. The other common solution is to build a centralized cloud management platform, similar to China Telecom Cloud or Tencent Cloud. This solution leverages the powerful computing capabilities and resource integration advantages of cloud computing to achieve unified device management. However, its development is more difficult, requiring significant investment of manpower, resources, and time for platform construction, optimization, and maintenance, resulting in relatively high deployment costs. Summary of the Invention

[0004] Therefore, it is necessary to provide a device access system and method based on dynamic registration to address the security verification and scheduling issues of multi-protocol and multi-type IoT devices when accessing the platform without excessively increasing development complexity.

[0005] Firstly, this application provides a device access system based on dynamic registration. The system includes a dynamic registration service system and an IoT middleware system, wherein the dynamic registration service system is connected to the IoT middleware system.

[0006] The dynamic registration service system is used to obtain dynamic registration requests sent by devices to be connected. The dynamic registration request includes device type, protocol type, encryption type, and encrypted device registration information.

[0007] The dynamic registration service system is also used to authenticate the dynamic registration request, and after successful authentication, send a scheduling request carrying the device type and the protocol type to the IoT middleware system;

[0008] The IoT middleware system is used to generate scheduling information for the device to be connected based on the scheduling request, and send the scheduling information to the dynamic registration service system; the scheduling information includes the IP address, port and key of the target IoT middleware.

[0009] The dynamic registration service system is also used to send a dynamic registration result carrying the scheduling information to the device to be connected. After the device to be connected obtains the dynamic registration result, it initiates a service connection request to the target IoT platform. After the target IoT platform verifies the service connection request, it connects to the device to be connected.

[0010] Furthermore, the dynamic registration service system is also used to encrypt the dynamic registration results.

[0011] Furthermore, both the device registration information and the dynamic registration result are encrypted using the RSA algorithm.

[0012] Furthermore, the service transmission data between the device to be connected and the target IoT platform are all encrypted and decrypted using the key of the target IoT platform.

[0013] Furthermore, the device to be connected sends a dynamic registration request to the dynamic registration service system once when it is powered on or restarted for the first time.

[0014] Furthermore, the devices to be connected uniformly store the IP address of the dynamic registration service system.

[0015] Furthermore, the system supports HTTP, HTTPS, MQTT, and TCP communication protocols; the system also supports Wi-Fi and 4G transmission methods.

[0016] Secondly, this application also provides a device access method based on dynamic registration. The method includes:

[0017] Step S1: The device to be connected sends a dynamic registration request to the dynamic registration service system; the dynamic registration request includes device type, protocol type, encryption type, and encrypted device registration information;

[0018] Step S2: The dynamic registration service system authenticates the dynamic registration request, and after successful authentication, sends a scheduling request carrying the device type and the protocol type to the IoT middleware system.

[0019] Step S3: The IoT middleware system generates scheduling information for the device to be connected based on the scheduling request, and sends the scheduling information to the dynamic registration service system; the scheduling information includes the IP address, port, and key of the target IoT middleware.

[0020] Step S4: The dynamic registration service system sends a dynamic registration result carrying the scheduling information to the device to be connected;

[0021] Step S5: After obtaining the dynamic registration result, the device to be connected initiates a service connection request to the target IoT platform.

[0022] Step S6: After the target IoT platform verifies the business connection request, it connects to the device to be accessed.

[0023] Further, step S2 includes:

[0024] Step S21: The dynamic registration service system selects a decryption algorithm based on the device type, the protocol type, and the encryption type to decrypt the device registration information and obtain the device code, manufacturer code, and current timestamp of the device to be connected.

[0025] Step S22: The dynamic registration service system determines whether the device code and the manufacturer code are valid; if yes, proceed to step S23; if no, return to step S1.

[0026] Step S23: The dynamic registration service system sends a scheduling request carrying the device type and the protocol type to the IoT middleware system.

[0027] Further, step S1 includes:

[0028] Step S11: The device to be connected uses the RSA algorithm to encrypt the device registration information and sends the dynamic registration request carrying the encrypted device registration information to the dynamic registration service system.

[0029] Step S21 includes:

[0030] In step S211, the dynamic registration service system uses the RSA algorithm to decrypt the device registration information to obtain the device code, manufacturer code, and current timestamp of the device to be connected.

[0031] The aforementioned device access system and method based on dynamic registration receives dynamic registration requests from devices seeking access through a dynamic registration service system and responds with the request results. The IoT middleware system schedules the IoT middleware access of the devices seeking access, achieving business separation from traditional systems and creating a certain degree of isolation between the devices seeking access and the IoT middleware system. The IoT middleware system is not directly exposed to the internet, improving the overall system security. Furthermore, for the devices seeking access, only the dynamic registration service system information needs to be uniformly stored, greatly reducing the difficulty of parameter management during device production. Simultaneously, the authentication of dynamic registration requests through the dynamic registration service system further enhances the security of device access. The IoT middleware system manages the access of devices based on device type and communication protocol, effectively managing the access of different types and protocols of devices while achieving load balancing. In addition, the system supports multiple transmission methods and communication protocols, exhibiting high compatibility and expanding its application scope and usage scenarios. In summary, the device access system and method based on dynamic registration provided in this application effectively solve the security verification and scheduling problems when different types of devices access access without excessively increasing development workload, achieving unified device management and being suitable for building access frameworks for small and medium-sized free devices. Attached Figure Description

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

[0033] Figure 1 This is a schematic diagram of the structure of a device access system based on dynamic registration in one embodiment;

[0034] Figure 2 This is a flowchart illustrating a device access method based on dynamic registration in one embodiment;

[0035] Figure 3 This is a flowchart illustrating the data interaction process between the device to be connected, the dynamic registration service system, and the IoT middleware system in one embodiment.

[0036] Figure 4 This is a schematic diagram of the access process for a device to be connected in one embodiment. Detailed Implementation

[0037] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0038] Example 1

[0039] like Figure 1 As shown, this embodiment provides a device access system based on dynamic registration, including a dynamic registration service system and an IoT middleware system, wherein the dynamic registration service system is connected to the IoT middleware system.

[0040] The dynamic registration service system is used to obtain dynamic registration requests sent by devices to be connected. These devices can include, but are not limited to, smart sockets, smart meters, and data collectors. There are no restrictions on the transmission methods and communication protocols between the devices and the dynamic registration service system. High-performance devices can use protocols such as HTTP, HTTPS, and MQTT, while low-performance devices can use protocols such as TCP. For example, smart sockets can transmit data via Wi-Fi and communicate with the dynamic registration service system using the TCP transmission protocol. Smart meters and data collectors can use 4G transmission and interact with the dynamic registration service system using the MQTT transmission protocol. Meanwhile, to ensure that the scheduling information on the device side is always up-to-date, each device to be connected needs to send a dynamic registration request to the dynamic registration service system upon first power-on or each restart and wait for its response. Only after receiving a dynamic registration result carrying scheduling information from the dynamic registration service system can the device to be connected begin normal business process interactions with the target IoT platform.

[0041] Specifically, the dynamic registration request includes device registration information, device type, protocol type, and encryption type. In a preferred embodiment, the device type, protocol type, and encryption type are transmitted in plaintext, while the device registration information is transmitted in encrypted form. Preferably, the RSA algorithm is used to encrypt the device registration information, with the encrypted portion represented by `sign`. The encryption formula is `sign = rsa(string1 + key)`, where `string1` = device code + manufacturer code + current timestamp. Transmitting the device type, protocol type, and encryption type of the device to be connected in plaintext allows the dynamic registration service system to quickly identify the type of the device to be connected and its supported communication protocols, thus facilitating negotiation between the dynamic registration service system and the IoT platform system regarding the subsequent scheduling arrangements of the device to be connected. Conversely, transmitting the device registration information in encrypted form effectively protects the security of critical data domains, improving the security of the device when it connects to the IoT platform.

[0042] To improve access efficiency, the IP address information of the dynamic registration service system is pre-stored on all devices. Therefore, each device only needs to manage the IP address of the dynamic registration service system and its own device registration information, without needing to handle any other complex configurations. Furthermore, the device registration information includes the device code, manufacturer code, and current timestamp; these three parameters are configurable. The device type, protocol type, and encryption type parameters are customizable based on the actual situation of the devices to be accessed, better adapting to diverse device access needs.

[0043] The dynamic registration service system also authenticates dynamic registration requests and, upon successful authentication, sends a scheduling request carrying the device type and protocol type to the IoT middleware system. Specifically, when the dynamic registration service system receives a dynamic registration request from a device to be connected, it first verifies the encryption method of the device registration information. If the encryption method is incorrect, it indicates a potential security risk or abnormal data transmission in the dynamic registration request. In this case, the dynamic registration service system immediately returns a dynamic registration failure result to the device to be connected, terminating the dynamic registration process for the current time slot. If the encryption method is correct, the dynamic registration system determines which algorithm to use to decrypt the device registration information based on three key parameters: device type, protocol type, and encryption type. This allows it to obtain the device code, manufacturer code, and current timestamp of the device to be connected. For example, when the device type is a high-performance smart meter, the protocol type is MQTT, and the encryption type uses RSA encryption, the dynamic registration service system will call the appropriate RSA decryption process to decrypt the device registration information. The RSA algorithm, as an asymmetric encryption algorithm, is widely used in the field of data security. During the decryption process, the dynamic registration service system uses a pre-stored private key to decrypt the device registration information encrypted with RSA.

[0044] After successfully decrypting the device registration information, the dynamic registration service system further checks its internal database or relevant verification mechanisms to determine the existence and validity of the device code and manufacturer code. Authentication is considered successful only when both the device code and manufacturer code are valid. Once authentication is successful, the dynamic registration service system quickly generates a scheduling request carrying the device type and protocol type and sends it to the IoT middleware system. If authentication fails, the dynamic registration service system will also return a dynamic registration failure result to the device to be connected, informing it that dynamic registration has failed.

[0045] The IoT middleware system is used to generate scheduling information for devices to be connected based on scheduling requests, and then send the scheduling information to the dynamic registration service system.

[0046] The IoT middleware system boasts a flexible architecture, capable of being deployed on a single physical server or comprised of multiple physical servers working collaboratively to form a distributed system, catering to business needs of varying scales and complexities. Scheduling information includes crucial parameters such as the target IoT middleware's IP address, port, and key. Upon receiving a scheduling request from the dynamic registration service system, the IoT middleware system immediately initiates a data interaction process with the dynamic registration service system to negotiate a specific allocation scheme for the devices to be connected. Specifically, after receiving the scheduling request, the IoT middleware system employs an intelligent matching algorithm based on device characteristics and IoT middleware resources to determine the target IoT middleware for the devices to be connected to. Specific algorithm implementations can employ weighted scoring methods, fuzzy matching methods, etc., which can be selected and optimized according to actual application scenarios and requirements. Taking the weighted scoring method as an example, the IoT middleware system pre-sets a series of indicators for evaluating the suitability of the IoT middleware, assigning corresponding weights to each indicator to reflect its importance in the overall evaluation. These indicators include, but are not limited to, remaining computing resources, remaining storage resources, and network bandwidth. Among these metrics, remaining computing resources measure the current available computing power of the IoT platform. More abundant computing resources better meet the complex computing needs of devices; for example, this metric carries a relatively high weight for high-performance smart devices requiring extensive data processing and analysis. Remaining storage resources represent the IoT platform's remaining storage space, while network bandwidth availability reflects the bandwidth status of the IoT platform's connection to external networks. For devices with high real-time requirements, such as smart meters, network bandwidth carries a relatively high weight. The IoT platform system collects the above-mentioned metric data from each IoT platform in real time. Based on the collected metric data and weights, a weighted scoring method is used to calculate the comprehensive score of each IoT platform, and the IoT platform with the highest comprehensive score is selected as the target IoT platform for the device to be connected. Specifically, if multiple IoT platforms have the same and highest comprehensive score, the dynamic registration service system can further filter based on other indicators, such as historical access records and geographical location, to ultimately determine a unique target IoT platform. For example, the dynamic registration service system records the number of times each device has connected to each IoT platform over a period of time. If a device frequently connects to a specific IoT platform, it indicates that the communication link between the device and the IoT platform is relatively stable. The dynamic registration service system will then prioritize reassigning the device to that IoT platform to improve the stability of the connection.

[0047] The dynamic registration service system is also used to send dynamic registration results carrying scheduling information to the devices to be connected. Specifically, the dynamic registration service system sends the target IoT platform's IP address, port, key, and other data to the devices to be connected, thereby completing the access scheduling for the devices. Furthermore, the dynamic registration service system also encrypts the target IoT platform's IP address, port, key, and other data using the RSA algorithm before sending them to the devices to be connected.

[0048] After receiving the dynamic registration result, the device to be connected initiates a service connection request to the target IoT platform. The target IoT platform verifies the connection request and then connects to the device. Specifically, if the device receives a dynamic registration result carrying scheduling information, it indicates successful dynamic registration. The device then initiates a service connection request carrying its device code to the target IoT platform. The target IoT platform receives the connection request, performs security verification, and sends a connection success response to the device, thus completing the device's connection. After connection, all service data reported or sent between the device and the IoT platform can be encrypted and decrypted using the AES algorithm to improve data transmission security. The key used for AES encryption and decryption is the key issued by the IoT platform in the scheduling information. Furthermore, if the dynamic registration service system uses the RSA algorithm to encrypt the scheduling information, the device to be connected will correspondingly use the RSA algorithm for decryption. Similarly, the communication protocols between the device to be connected and the IoT platform include, but are not limited to, HTTP, HTTPS, MQTT, and TCP, and the transmission methods include, but are not limited to, Wi-Fi and 4G.

[0049] This embodiment of the device access system based on dynamic registration receives dynamic registration requests from devices seeking access through a dynamic registration service system and responds with the request results. The IoT middleware system schedules the IoT middleware access of the devices seeking access, achieving business separation of the traditional system and creating a certain degree of isolation between the devices seeking access and the IoT middleware system. The IoT middleware system is not directly exposed to the Internet, improving the overall system security. Furthermore, for the devices seeking access, only the dynamic registration service system information needs to be uniformly stored, greatly reducing the difficulty of parameter management during device production. At the same time, the authentication of dynamic registration requests through the dynamic registration service system further improves the security of device access. By managing the access of devices based on device type and communication protocol through the IoT middleware system, it can effectively manage the access of devices of different types and protocols, while also achieving load balancing. In addition, the system supports multiple transmission methods and communication protocols, has high compatibility, and expands the application scope and usage scenarios of the system. In summary, the device access system based on dynamic registration provided in this embodiment effectively solves the security verification and scheduling problems when different types of devices access access without excessively increasing the development workload, achieving unified device management, and is suitable for building access frameworks for small and medium-sized free devices.

[0050] Example 2

[0051] like Figure 2 As shown, this embodiment provides a device access method based on dynamic registration, which can be applied to, for example... Figure 1 The system shown is explained and described, specifically including the following steps:

[0052] Step S1: The device to be accessed sends a dynamic registration request to the dynamic registration service system.

[0053] The dynamic registration request includes device registration information, device type, protocol type, and encryption type. In a preferred embodiment, the device type, protocol type, and encryption type are transmitted in plaintext, while the device registration information is transmitted in encrypted form.

[0054] Furthermore, it is preferable to use the RSA algorithm to encrypt the device registration information. Step S1 includes:

[0055] Step S11: The device to be connected encrypts its registration information using the RSA algorithm and sends a dynamic registration request carrying the encrypted device registration information to the dynamic registration service system.

[0056] The encryption part is represented by `sign`, and its encryption formula is `sign = rsa(string1 + key)`, where `string1` = device code + manufacturer code + current timestamp. Transmitting the device type, protocol type, and encryption type of the device to be connected in plaintext allows the dynamic registration service system to quickly identify the type of the device and its supported communication protocols, facilitating negotiation between the dynamic registration service system and the IoT platform system regarding subsequent scheduling arrangements for the connected device. Conversely, transmitting device registration information in encrypted form effectively protects the security of critical data domains, improving the security of the device when connecting to the IoT platform.

[0057] To improve access efficiency, the IP address information of the dynamic registration service system is pre-stored on all devices. Therefore, each device only needs to manage the IP addresses of the dynamic registration service system and its own device registration information, without needing to handle any other complex configurations. Furthermore, the device registration information includes device code, manufacturer code, and current timestamp, all of which are configurable. Meanwhile, the device type, protocol type, and encryption type parameters can be customized based on the specific needs of the devices to be accessed, better adapting to diverse device access requirements.

[0058] Specifically, the device to be connected needs to send a dynamic registration request to the dynamic registration service system upon its first power-on or each restart, and wait for its response. Only after receiving a dynamic registration result carrying scheduling information from the dynamic registration service system can the device to be connected engage in normal business process interactions with the target IoT platform.

[0059] Step S2: The dynamic registration service system authenticates the dynamic registration request and sends a scheduling request carrying the device type and protocol type to the IoT middleware system after successful authentication.

[0060] Specifically, step S2 includes:

[0061] In step S21, the dynamic registration service system selects a decryption algorithm based on the device type, protocol type, and encryption type to decrypt the device registration information in the dynamic registration request, and obtains the device code, manufacturer code, and current timestamp of the device to be connected.

[0062] When the dynamic registration service system receives a dynamic registration request from a device seeking access, it first verifies the encryption method of the device registration information. If the encryption method is incorrect, it indicates a potential security risk or data transmission anomaly in the dynamic registration request. In this case, the dynamic registration service system immediately returns a dynamic registration failure result to the device seeking access, terminating the dynamic registration process for the current time slot. If the encryption method is correct, the dynamic registration system determines which algorithm to use to decrypt the device registration information based on three key parameters: device type, protocol type, and encryption type. This allows it to obtain the device code, manufacturer code, and current timestamp of the device seeking access. For example, when the device type is a high-performance smart meter, the protocol type is MQTT, and the encryption type is RSA, the dynamic registration service system will call the appropriate RSA decryption process to decrypt the device registration information. RSA, as an asymmetric encryption algorithm, is widely used in data security. During the decryption process, the dynamic registration service system uses a pre-stored private key to decrypt the RSA-encrypted device registration information.

[0063] In step S22, the dynamic registration service system determines whether the device code and manufacturer code are valid; if yes, proceed to step S23; otherwise, return to step S1.

[0064] Step S23: The dynamic registration service system sends a scheduling request carrying the device type and protocol type to the IoT middleware system.

[0065] After successfully decrypting the device registration information, the dynamic registration service system further checks its internal database or relevant verification mechanisms to determine the existence and validity of the device code and manufacturer code. Authentication is considered successful only when both the device code and manufacturer code are valid. Once authentication is successful, the dynamic registration service system generates a scheduling request carrying the device type and protocol type and sends it to the IoT middleware system. If authentication fails, the dynamic registration service system will also return a dynamic registration failure result to the device to be connected, informing it of the failure and returning to step S1.

[0066] Step S3: The IoT middleware system generates scheduling information for the devices to be connected based on the scheduling request, and sends the scheduling information to the dynamic registration service system.

[0067] The scheduling information includes the IP address, port, and key of the target IoT platform. Upon receiving the scheduling request from the dynamic registration service system, the IoT platform system immediately initiates a data interaction process with the dynamic registration service system to negotiate a specific allocation scheme for the devices to be connected. Specifically, after receiving the scheduling request, the IoT platform system uses an intelligent matching algorithm based on device characteristics and IoT platform resources to determine the target IoT platform for the devices to be connected. Specific algorithm implementations can employ weighted scoring methods, fuzzy matching methods, etc., and can be selected and optimized according to actual application scenarios and requirements.

[0068] Step S4: The dynamic registration service system sends the dynamic registration result carrying scheduling information to the device to be connected.

[0069] Specifically, the dynamic registration service system sends the target IoT platform's IP address, port, key, and other data to the device to be connected, thereby completing the access scheduling for the device. Furthermore, the dynamic registration service system also encrypts the target IoT platform's IP address, port, key, and other data using the RSA algorithm before sending them to the device to be connected.

[0070] Step S5: After the access device obtains the dynamic registration result, it initiates a business connection request to the target IoT platform.

[0071] Step S6: After the target IoT platform verifies the business connection request, it connects to the device to be accessed.

[0072] Specifically, when the device to be connected receives a dynamic registration result carrying scheduling information, it indicates successful dynamic registration. The device then initiates a service connection request carrying its device code to the target IoT platform. Upon receiving the request, the target IoT platform verifies the connection information. If verification is successful, it sends a connection success response to the device to be connected, thus completing the device's connection to the IoT platform. After connection, all service data reported or sent between the device and the IoT platform is encrypted and decrypted using the AES algorithm to improve data transmission security. The key used for AES encryption and decryption is the key issued by the IoT platform in the scheduling information. Furthermore, if the dynamic registration service system uses the RSA algorithm to encrypt the scheduling information, the device to be connected will correspondingly use the RSA algorithm for decryption.

[0073] To better understand the device access method based on dynamic registration in this embodiment, Figure 3The diagram illustrates the detailed data interaction process between the device to be connected, the dynamic registration service system, and the IoT middleware system. As shown in the figure, upon initial power-on or after each restart, the device to be connected sends a dynamic registration request to the dynamic registration service system. The device registration information carried in this request is encrypted using the RSA algorithm. Upon receiving the dynamic registration request, the dynamic registration service system decrypts and verifies the device registration information using the RSA algorithm. If the verification is successful, it sends a scheduling request to the IoT middleware system.

[0074] The IoT middleware system allocates suitable target IoT middleware based on information such as device type and protocol type included in the scheduling request, and generates corresponding scheduling information. Subsequently, the dynamic registration service system replies to the device to be connected with the dynamic registration result encrypted using the RSA algorithm. This result carries the scheduling information of the device to be connected.

[0075] After the device to be connected obtains the scheduling information, it initiates a service connection and sends a service connection request carrying the device code, which is encrypted using the AES algorithm. After the target IoT platform verifies the connection information, it returns a connection success response to the device to be connected. Then, the device to be connected and the target IoT platform conduct service interactions. All service interaction data uses messages encrypted with the AES algorithm.

[0076] Furthermore, Figure 4 The detailed access process for the device to be connected is illustrated. As shown in the figure, after the device is started, it first connects to the dynamic registration service system and sends a dynamic registration request to it. If registration is successful, the device obtains the scheduling information carried in the dynamic registration result and then connects to the target IoT platform. If the connection to the target IoT platform is successful, the device begins business interaction with the platform. If the connection to the target IoT platform fails, the device returns to the step of connecting to the target IoT platform. If registration fails, the device returns to the step of connecting to the dynamic registration service system and sending a dynamic registration request to retry the registration.

[0077] This embodiment of the device access method based on dynamic registration involves the device to be accessed sending a dynamic registration request carrying device registration information, device type, protocol type, and encryption type to the dynamic registration service system. The dynamic registration service system authenticates the dynamic registration request and, upon successful authentication, sends a scheduling request carrying the device type and protocol type to the IoT middleware system. The IoT middleware system generates scheduling information for the device to be accessed based on the scheduling request and sends the scheduling information to the dynamic registration service system. The dynamic registration service system forwards the scheduling information carrying the IP address, port, and key of the target IoT middleware to the device to be accessed. The device to be accessed initiates a service connection to the target IoT middleware. After verifying the connection information, the target IoT middleware connects to the device to be accessed, achieving secure and efficient device access. Furthermore, by separating the business of the traditional system, the dynamic registration service system is only responsible for device registration and authentication, without involving business-level functions. The traditional business part is separated to the IoT middleware system, which not only greatly enhances the overall security of the system but also facilitates unified management of devices of different types and protocols.

[0078] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0079] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are relatively specific and detailed, they should not be construed as limiting the scope of the invention patent. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this patent application should be determined by the appended claims.

Claims

1. A device access system based on dynamic registration, characterized in that, The system includes a dynamic registration service system and an IoT middleware system, wherein the dynamic registration service system is connected to the IoT middleware system. The dynamic registration service system is used to obtain dynamic registration requests sent by devices to be connected. The dynamic registration request includes device type, protocol type, encryption type, and encrypted device registration information. The dynamic registration service system is also used to authenticate the dynamic registration request, and after successful authentication, send a scheduling request carrying the device type and the protocol type to the IoT middleware system; The IoT middleware system is used to generate scheduling information for the device to be connected based on the scheduling request, and send the scheduling information to the dynamic registration service system; the scheduling information includes the IP address, port and key of the target IoT middleware. The dynamic registration service system is also used to send a dynamic registration result carrying the scheduling information to the device to be connected. After the device to be connected obtains the dynamic registration result, it initiates a service connection request to the target IoT platform. After the target IoT platform verifies the service connection request, it connects to the device to be connected.

2. The device access system based on dynamic registration according to claim 1, characterized in that, The dynamic registration service system is also used to encrypt the dynamic registration results.

3. The device access system based on dynamic registration according to claim 2, characterized in that, Both the device registration information and the dynamic registration result are encrypted using the RSA algorithm.

4. The device access system based on dynamic registration according to claim 1, characterized in that, All business transmission data between the device to be connected and the target IoT platform are encrypted and decrypted using the key of the target IoT platform.

5. The device access system based on dynamic registration according to claim 1, characterized in that, When the device to be connected is powered on or restarted for the first time, it sends a dynamic registration request to the dynamic registration service system.

6. The device access system based on dynamic registration according to claim 1, characterized in that, The devices to be connected uniformly store the IP addresses of the dynamic registration service system.

7. The device access system based on dynamic registration according to claim 1, characterized in that, The system supports HTTP, HTTPS, MQTT and TCP communication protocols; the system supports Wi-Fi and 4G transmission methods.

8. A device access method based on dynamic registration, characterized in that, The method includes: Step S1: The device to be connected sends a dynamic registration request to the dynamic registration service system; the dynamic registration request includes device type, protocol type, encryption type, and encrypted device registration information; Step S2: The dynamic registration service system authenticates the dynamic registration request, and after successful authentication, sends a scheduling request carrying the device type and the protocol type to the IoT middleware system. Step S3: The IoT middleware system generates scheduling information for the device to be connected based on the scheduling request, and sends the scheduling information to the dynamic registration service system; the scheduling information includes the IP address, port, and key of the target IoT middleware. Step S4: The dynamic registration service system sends a dynamic registration result carrying the scheduling information to the device to be connected; Step S5: After obtaining the dynamic registration result, the device to be connected initiates a service connection request to the target IoT platform. Step S6: After the target IoT platform verifies the business connection request, it connects to the device to be accessed.

9. The device access method based on dynamic registration according to claim 8, characterized in that, Step S2 includes: Step S21: The dynamic registration service system selects a decryption algorithm based on the device type, the protocol type, and the encryption type to decrypt the device registration information and obtain the device code, manufacturer code, and current timestamp of the device to be connected. Step S22: The dynamic registration service system determines whether the device code and the manufacturer code are valid; if yes, proceed to step S23; if no, return to step S1. Step S23: The dynamic registration service system sends a scheduling request carrying the device type and the protocol type to the IoT middleware system.

10. The device access method based on dynamic registration according to claim 9, characterized in that, Step S1 includes: Step S11: The device to be connected uses the RSA algorithm to encrypt the device registration information and sends the dynamic registration request carrying the encrypted device registration information to the dynamic registration service system. Step S21 includes: In step S211, the dynamic registration service system uses the RSA algorithm to decrypt the device registration information to obtain the device code, manufacturer code, and current timestamp of the device to be connected.

Images