An internet of things access system

Abstract

The application relates to an Internet of Things access system, which comprises the following units: an Internet of Things terminal device unit, which is used for establishing a connection between an Internet of Things terminal device and an access server and transmitting uplink data to the access server; a third-party application server unit, which is used for transmitting downlink data by the third-party application server and realizing data interaction between the third-party application server and the Internet of Things terminal device to which the third-party application server belongs through data processing of a data checking and storing unit of the access server; an access server unit, which is used for inputting the uplink data and the downlink data into a message queue of the data storing unit, acquiring processed uplink messages and downlink messages, and then inputting the uplink messages and the downlink messages into the third-party application server and the Internet of Things terminal device respectively; and a data storing unit, which is used for processing and storing the uplink messages and the downlink messages. Compared with the prior art, the application has the advantages of high usability and expansibility.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of Internet of Things, and in particular to an Internet of Things access system. BACKGROUND

[0002] Current Internet of Things access devices have many drawbacks, mainly including connection stability problems, security challenges, insufficient mutual compatibility, high energy consumption and maintenance costs, data management and analysis, and other problems. In terms of connection stability of Internet of Things devices, communication between devices may be interfered or signal unstable, resulting in data transmission delay or disconnection, affecting the normal operation and data exchange of the device, which needs to improve the communication technology and network architecture of the device to improve the stability and reliability of the connection, and ensure the timely transmission of data and the stable work of the device. In terms of security, Internet of Things devices are vulnerable to hacker attacks, which may lead to information leakage or remote control of devices, and need to strengthen the security design and network protection measures of the device. At the same time, in terms of mutual compatibility, Internet of Things devices from different manufacturers usually use different communication protocols and standards, resulting in poor mutual compatibility between devices, which brings inconvenience and complexity to users. Finally, a large amount of data generated by Internet of Things devices needs to be effectively managed and analyzed, and powerful data processing and analysis tools need to be used to extract useful information and ensure the security and privacy protection of data. SUMMARY

[0003] The purpose of the present application is to provide an Internet of Things access system that improves the flexibility of system expansion and reduction.

[0004] The purpose of the present application can be achieved by the following technical solutions:

[0005] An Internet of Things access system, comprising an Internet of Things terminal device unit provided with a plurality of third-party application servers, an access server unit provided with a plurality of access servers, a data storage unit, and a third-party application server unit provided with a plurality of third-party application servers, the Internet of Things terminal device unit is connected with the access server unit, the access server unit is connected with the data storage unit, and the access server unit is also connected with the third-party application server unit;

[0006] The Internet of Things terminal device unit is used for the Internet of Things terminal device to establish a connection with the access server and send uplink data to the access server, and through data processing of the data storage unit, data interaction between the Internet of Things terminal device and the third-party application server is realized;

[0007] The third-party application server unit is used for the third-party application server to send downlink data, and through data verification of the access server and data processing of the data storage unit, data interaction between the third-party application server and the Internet of Things terminal device to which it belongs is realized;

[0008] Access server unit: used to input the uplink data and downlink data into the message queue of the data storage unit, and obtain the processed uplink messages and downlink messages, and then input them into the third-party application server and IoT terminal device respectively;

[0009] Data storage unit: used for processing and storing the uplink message and the downlink message.

[0010] Furthermore, it also includes a load balancing unit, the Internet of Things terminal device unit is connected to the access server unit through the load balancing unit, and the access server unit is connected to the third-party application server unit through the load balancing unit. The load balancing unit is used to ensure that a single access server is overloaded and allocate system resources by adopting a load balancing algorithm and resource allocation strategy.

[0011] Furthermore, the access server unit includes:

[0012] Heartbeat detection module: used to send a heartbeat signal to the IoT terminal device and wait for the response of the IoT terminal device, and timely update the access status of the IoT terminal device;

[0013] Device management module: used for unified management of the IoT terminal devices;

[0014] Session management module: used to manage the session status between the IoT terminal device and the system, including session establishment, maintenance and termination.

[0015] Furthermore, the access server unit also includes an OTA management module, which is used to download and install the latest version of firmware based on the firmware version detected in the IoT terminal device to ensure that the IoT terminal device is always in the latest state.

[0016] Furthermore, the access server unit also includes a system user management module: used to manage user rights and roles of system users, including registration, login, rights allocation, and role management.

[0017] Furthermore, the step of establishing a connection between the IoT terminal device and the access server includes:

[0018] The IoT terminal device sends a connection request message to the access server, where the connection request message includes the device serial number and the AppId of the third-party application;

[0019] The access server verifies whether the message format of the connection request message is correct. If so, the connection establishment fails; if not, the next step is executed;

[0020] The access server verifies whether the device serial number in the connection request message exists. If so, the next step is executed. If not, the connection establishment fails.

[0021] The access server determines whether the AppId to which the device serial number belongs is consistent with the AppId in the connection request message. If so, it executes the next step. If not, it sends the AppId to the IoT terminal device and the connection establishment fails.

[0022] The access server checks whether the IoT terminal device is allowed to access. If so, the next step is executed. If not, the connection establishment fails.

[0023] The access server checks whether a persistent connection between the IoT terminal device and the access server already exists. If so, the access server directly responds. If not, the access server establishes a persistent connection and responds.

[0024] Furthermore, the data storage unit includes:

[0025] Message production and consumption module: used to produce and consume messages in message queues, caches and databases based on the uplink data and downlink data;

[0026] Data parsing module: used to parse the messages in the message queue;

[0027] Data conversion module: used to convert the parsed message into a specific data format;

[0028] Data storage module: used to store parsed messages in the database.

[0029] Furthermore, the data storage unit further includes a log module, which is used to record various operations and events during the operation of the access system.

[0030] Furthermore, the execution step of the uplink data includes:

[0031] The IoT terminal device sends a data request message containing uplink data to the access server. The access server verifies whether the data format of the data request message is correct. If so, it executes the next step. If not, it rejects the data request message.

[0032] The access server checks whether there is a long connection between the IoT terminal device and it. If so, the uplink data is input into the uplink message queue of the data storage unit, and the uplink message is processed and stored. The processed uplink message is sent to the third-party application server to complete the data interaction between the IoT terminal device and the third-party application server. If not, the data request message is rejected.

[0033] Furthermore, the execution step of the downlink data includes:

[0034] The third-party application server sends a data message containing downlink data to the access server, and the access server verifies whether the data format of the data message is correct. If so, it executes the next step; if not, it rejects the data message;

[0035] The access server checks the format and attribution of the device serial number in the data message, and rejects the data message if the format or attribution is incorrect; if the format and attribution are correct, proceeds to the next step;

[0036] The access server checks the AppId and ApiKey in the data message. If either the AppId or the ApiKey is incorrect, the data message is rejected. If both the AppId and the ApiKey are correct, the next step is executed.

[0037] The access server inputs the downlink data into the downlink message queue of the data storage unit, processes and stores the downlink message, and sends the processed downlink message to the networked terminal device belonging to the third-party application server, completing the data interaction between the third-party application server and the networked terminal device.

[0038] Compared with the prior art, the present invention has the following beneficial effects:

[0039] (1) The distributed cluster model of the IoT terminal device unit, access server unit, and third-party application server unit in the system of the present invention, which are respectively constructed by multiple IoT terminal devices, access servers, and third-party application servers, brings high availability and scalability to the system, effectively avoids the risk of single point failure, improves the stability and reliability of the entire system, and processes data in the form of message queues in the data storage unit to achieve the purpose of data interaction in the system. Through the distributed architecture, the system can flexibly expand and reduce resources as needed to cope with changing business needs and traffic fluctuations, providing users with stable and reliable services.

[0040] (2) The load balancing unit's intelligent access request distribution technology enables the system to more efficiently utilize resources, balance the system load, effectively reduce the pressure on individual nodes, and improve the system's response speed and overall performance. By intelligently distributing access requests, the system can dynamically adjust based on the characteristics of the request and the load, ensuring that the user's access experience remains at a consistently high level.

[0041] (3) The present invention is based on the design of load balancing and message queues, which continuously ensures the security of data access and distribution; supports data access and distribution of numerous IoT hardware terminals, and enhances the applicability and flexibility of the system. By adopting flexible strategies such as message queues and load balancing, the system can easily cope with massive data processing and high concurrent requests. Through message queue technology, the system can achieve asynchronous processing and decoupling, separate requests and processing, and improve the system's concurrent processing capabilities and response speed. At the same time, load balancing technology can effectively allocate system resources, avoid overloading of certain nodes, and ensure the stability and reliability of the system.

[0042] (4) The present invention is equipped with an OTA management module, which supports remote upgrades, 24 / 7 service, and high availability. The system's remote upgrade function allows users to upgrade and update the system at any time without downtime or service interruption, ensuring that the system is always up to date.

[0043] (5) The heartbeat detection module of the present invention continuously detects the access status of the IoT terminal device to ensure a stable connection. In addition, since the flexibility of expansion and contraction of the present invention is greatly improved, it can be quickly expanded or reduced when the system changes without affecting the operation of other devices, and the maintenance cost of the present invention is low.

[0044] (6) This invention supports massive data storage, providing a data foundation for big data mining, machine learning, and artificial intelligence. Through efficient data management and storage technologies, the system can process and store large amounts of data, providing users with support for data analysis and mining, thereby enhancing the value and application potential of data. BRIEF DESCRIPTION OF THE DRAWINGS

[0045] Figure 1 It is a schematic diagram of the overall system architecture of the present invention;

[0046] Figure 2 This is the Internet of Things access flow chart of the present invention;

[0047] Figure 3 This is a flowchart of IoT data uplink of the present invention;

[0048] Figure 4 This is a flowchart of the Internet of Things data downlink process of the present invention. DETAILED DESCRIPTION

[0049] The present invention is described in detail below with reference to the accompanying drawings and specific embodiments. This embodiment is implemented based on the technical solution of the present invention, and provides a detailed implementation method and specific operation process, but the protection scope of the present invention is not limited to the following embodiments.

[0050] This embodiment provides an Internet of Things access system, such as Figure 1As shown, the system consists of five major units, namely, an IoT terminal device unit 1, an access server unit 2, a data storage unit 3, a third-party application server unit 4, and a load balancing unit 5.

[0051] The Internet of Things terminal device unit 1 is composed of a variety of Internet of Things terminal devices, including Internet of Things sensors, Internet of Things controllers, etc., which are used to collect environmental parameters or control terminal devices. The Internet of Things terminal device unit 1 establishes a TCP connection with the access server through the load balancing unit 5 to ensure that a single access server in the access server unit 2 is overloaded.

[0052] The access server unit 2 is a server cluster composed of multiple access servers. The load balancing unit 5 allocates resources. The access server is responsible for managing, parsing, and distributing data packets, and providing data statistics and auditing.

[0053] Data storage unit 3 includes a message queue, cache server, and database server. The message queue transmits messages between the access server unit, third-party application server unit, and IoT terminal device unit, achieving unit decoupling and asynchronous communication between units, improving system scalability and stability. The cache server stores temporary data and frequently accessed data to speed up data access, reduce pressure on the database server, and improve system response speed and performance. The database server is used to store and manage data, providing persistent storage and efficient data query capabilities, as well as transaction management and data security.

[0054] The third-party application server unit 4 is composed of third-party application servers. The third-party application is ultimately user-oriented, and the data interaction behind it is distributed to the access service unit 2 through the load balancing unit 5.

[0055] The load balancing unit 5 is also responsible for managing the connection between IoT devices and the system, including establishing, maintaining, and closing connections. It processes connection requests and manages connection status to ensure unimpeded communication between IoT devices and the system.

[0056] The access server unit 2 includes a heartbeat detection module 21, an OTA management module 22, a device management module 23, a session management module 24, and a system user management module 25. The heartbeat detection module 2 sends heartbeat signals and waits for responses from IoT terminal devices, promptly updating the IoT terminal device's access status and taking appropriate measures. The OTA management module 22 is responsible for remote firmware upgrades and management of IoT terminal devices. It detects the current firmware version of IoT terminal devices, downloads and installs the latest firmware version, and ensures that IoT terminal devices are always up to date, improving system reliability and security. The device management module 23 manages IoT terminal device information in the IoT terminal device unit 1, including functions such as device registration, binding and unbinding with the application platform, and device status monitoring. This allows for unified management of IoT terminal devices, making it easier for users to view and operate them. The session management module 24 manages the session status between IoT terminal devices and the system, ensuring smooth communication. This includes functions such as session establishment, maintenance, and termination, ensuring communication stability and security. The system user management module 25 manages system user permissions and roles, including user registration, login, permission allocation, and role management. Ensure the system is secure and controllable to prevent unauthorized access and operation.

[0057] The data storage unit 3 includes a message production and consumption module 31, a data parsing module 32, a data conversion module 33, a data storage module 34, and a logging module 35. The message production and consumption module 31 is responsible for producing and consuming messages in the system's message queues, caches, and databases, enabling communication and collaboration between various modules within the system. Messages are transmitted and processed using methods such as message queues or event buses. The data parsing module 32 is responsible for parsing data streams transmitted from IoT terminal devices and converting them into a format that the system can recognize and process. This includes operations such as parsing data packets and verifying data integrity. The data conversion module 33 converts the parsed data into a specific data format configured by the access platform, ensuring that data exchange processes conform to the data format required by IoT terminal devices and third-party application platforms. The data storage module 34 stores the parsed data in a database for subsequent data query and analysis. The logging module 35 records various operations and events during system operation, including error logs, information logs, and warning logs. These are used for troubleshooting, system monitoring, and performance optimization.

[0058] The third-party application server unit 4 can also interact with the interface and data of the third-party platform, including authentication and authorization, data transmission, etc., to ensure that the communication with the third-party platform is safe and reliable.

[0059] Figure 2This is the IoT access flow chart. The IoT terminal device in the IoT terminal device unit 1 needs to go through a series of verification steps before it can finally establish a connection with a specific access server in the access server unit 2. First, the IoT terminal device sends a connection request message to the access server. The connection request message includes information such as the device serial number and the AppId of the third-party application. The access server first verifies the format of its access message. If the format is incorrect, the connection establishment fails. Otherwise, it performs a device serial number verification. If the device serial number does not exist, the connection establishment fails. Otherwise, it performs an AppId consistency check. When the AppId belonging to the device serial number is inconsistent with the AppId in the connection request message, the AppId is sent to the IoT terminal device and the connection establishment fails. Otherwise, it checks whether the IoT terminal device is allowed to access. If access is allowed, it checks whether the service time of the third-party platform to which the IoT terminal device belongs has expired. If not, it checks whether a long connection between the IoT terminal device and the access server already exists. If not, it establishes a long connection and responds to a message indicating that the connection is successfully established. If it exists, it directly responds to a message indicating that the connection is successfully established.

[0060] Figure 3 This is the IoT data uplink flow chart. The IoT terminal device in the IoT terminal device unit 1 sends uplink data to the access server unit 2. The data is parsed, converted, and stored by a specific access server in the access server unit 2, and data interaction is carried out with a specific third-party application server in the third-party application server unit 4 to which the IoT terminal device belongs. First, the IoT terminal device sends a data request message to the access server. The access server verifies the data format. If the format is incorrect, the message is rejected. Otherwise, it checks whether a long connection between the IoT terminal device and the access server exists. If not, the message is rejected. Otherwise, the uplink data is entered into the uplink message queue. Then, in the data parsing thread, the message is obtained from the uplink message queue, and data parsing, data conversion, and data storage are performed. Finally, the uplink message is sent to the third-party application server to complete the data interaction between the IoT terminal device and the third-party application server.

[0061] Figure 4This is the IoT data downlink flow chart. A specific third-party application server in the third-party application server unit 4 sends downlink data to a specific access server in the access server unit 2. The data is parsed, converted, and stored by the access server, and data interaction is carried out with the Internet terminal device to which the third-party application server belongs. First, the third-party application server sends a data message to the access server. The access server verifies the data format. If the format is incorrect, the message is rejected. Otherwise, the format and ownership of the device serial number in the message are checked. If the format or ownership is incorrect, the message is rejected. Otherwise, the AppId and ApiKey are checked. If either of them is incorrect, the message is rejected. Otherwise, the downlink data is entered into the downlink message queue. Then, in the data parsing thread, the message is obtained from the downlink message queue, and data parsing, data conversion, and data storage are performed. Finally, the downlink message is sent to the target Internet terminal device to which the third-party application server belongs, completing the data interaction between the third-party application server and the Internet terminal device.

[0062] In summary, this embodiment provides an IoT access system composed of the aforementioned units and modules. The design of the load balancing unit 5 solves the problem of connection stability between IoT terminal devices and access servers. IoT terminal device connectivity is fundamental to the operation of the entire system. Unstable connections can lead to poor data transmission, malfunctions, and other issues, impacting user experience and system reliability. Through mechanisms such as effective management of connection requests and load balancing resource allocation, stable communication between IoT terminal devices and access servers is ensured, effectively addressing the problem of connection stability. The design of the data parsing module 32 and the data conversion module 33 addresses the issues of data processing and format conversion in IoT systems. IoT terminal devices generate data in diverse formats and may have compatibility issues between different manufacturers, making data processing difficult. Data parsing module 32 parses the raw data, and data conversion module 33 converts the data into a unified format, providing a foundation for subsequent data storage, analysis, and application. This reduces the complexity of data processing and improves system efficiency and reliability. The design of the data storage unit 3 solves the problems of secure data storage and efficient querying. IoT systems generate enormous amounts of data, requiring secure and reliable storage and rapid query and analysis. The access platform, through a combination of message queues, cache servers, and database servers, enables secure data storage, efficient querying of frequently accessed data, and persistent data management, providing strong support for the system's data management. The design of the session management module and logging module enhances system stability and traceability. The session management module 24 manages the session status between IoT terminal devices and the system, ensuring smooth communication; while the logging module 35 records various operations and events during system operation for troubleshooting, system monitoring, and performance optimization. These designs ensure system stability and provide a rich set of operational logs, enabling timely identification and resolution of issues and ensuring the proper functioning of the system.

[0063] Although the preferred embodiments of the present invention have been described, those skilled in the art may make additional changes and modifications to these embodiments once they have learned the basic creative concept. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments and all changes and modifications that fall within the scope of the present invention.

[0064] Obviously, those skilled in the art may make various changes and modifications to the present invention without departing from the spirit and scope of the present invention. Thus, if such changes and modifications fall within the scope of the claims and their equivalents, the present invention is intended to include such changes and modifications.

Claims

1. An Internet of Things access system, characterized in that: The invention comprises an Internet of Things terminal device unit (1) provided with a plurality of Internet of Things terminal devices, an access server unit (2) provided with a plurality of access servers, a data storage unit (3), and a third-party application server unit (4) provided with a plurality of third-party application servers, wherein the Internet of Things terminal device unit (1) is connected to the access server unit (2), the access server unit (2) is connected to the data storage unit (3), and the access server unit (2) is also connected to the third-party application server unit (4); The Internet of Things terminal device unit (1) is used to establish a connection between the Internet of Things terminal device and the access server, and to send uplink data to the access server, and to process the data in the data storage unit (3) to realize data interaction between the Internet of Things terminal device and the third-party application server; A third-party application server unit (4) is used for the third-party application server to send downlink data, and to realize data interaction between the third-party application server and the IoT terminal device to which it belongs through data verification of the access server and data processing of the data storage unit (3); An access server unit (2) is used to input the uplink data and downlink data into the message queue of the data storage unit (3), obtain the processed uplink message and downlink message, and then input them into the third-party application server and the Internet of Things terminal device respectively; Data storage unit (3): used for processing and storing the uplink message and the downlink message.

2. The Internet of Things access system according to claim 1, characterized in that: The system further comprises a load balancing unit (5), wherein the Internet of Things terminal device unit (1) is connected to the access server unit (2) via the load balancing unit (5), and the access server unit (2) is connected to the third-party application server unit (4) via the load balancing unit (5). The load balancing unit (5) is used to ensure that a single access server is overloaded and to allocate system resources by adopting a load balancing algorithm and a resource allocation strategy.

3. The Internet of Things access system according to claim 1, characterized in that: The access server unit (2) comprises: Heartbeat detection module (21): used for sending a heartbeat signal to the IoT terminal device and waiting for a response from the IoT terminal device, and timely updating the access status of the IoT terminal device; Device management module (23): used for unified management of the IoT terminal devices; Session management module (24): used to manage the session status between the IoT terminal device and the system, including session establishment, maintenance and termination.

4. The Internet of Things access system according to claim 3, characterized in that: The access server unit (2) further comprises an OTA management module (22), which is used to download and install the latest version of the firmware according to the detected firmware version in the IoT terminal device, so as to ensure that the IoT terminal device is always in the latest state.

5. The Internet of Things access system according to claim 3, characterized in that: The access server unit (2) further comprises a system user management module (25) for managing the user rights and roles of system users, including registration, login, rights allocation, and role management.

6. The Internet of Things access system according to claim 1, characterized in that: The steps of establishing a connection between the IoT terminal device and the access server include: The IoT terminal device sends a connection request message to the access server, where the connection request message includes the device serial number and the AppId of the third-party application; The access server verifies whether the message format of the connection request message is correct. If so, the connection establishment fails; if not, the next step is executed; The access server verifies whether the device serial number in the connection request message exists. If so, the next step is executed. If not, the connection establishment fails. The access server determines whether the AppId to which the device serial number belongs is consistent with the AppId in the connection request message. If so, it executes the next step. If not, it sends the AppId to the IoT terminal device and the connection establishment fails. The access server checks whether the IoT terminal device is allowed to access. If so, the next step is executed. If not, the connection establishment fails. The access server checks whether a persistent connection between the IoT terminal device and the access server already exists. If so, the access server directly responds. If not, the access server establishes a persistent connection and responds.

7. The Internet of Things access system according to claim 1, characterized in that: The data storage unit (3) comprises: Message production and consumption module (31): used for producing and consuming messages in message queues, caches and databases based on the uplink data and downlink data; Data parsing module (32): used for parsing messages in the message queue; Data conversion module (33): used to convert the parsed message into a specific data format; Data storage module (34): used to store the parsed message in a database.

8. The Internet of Things access system according to claim 7, characterized in that: The data storage unit (3) further comprises a log module (35), and the log module (35) is used to record various operations and events during the operation of the access system.

9. The Internet of Things access system according to claim 7, characterized in that: The execution step of the uplink data includes: The IoT terminal device sends a data request message containing uplink data to the access server. The access server verifies whether the data format of the data request message is correct. If so, it executes the next step. If not, it rejects the data request message. The access server checks whether there is a long connection between the Internet of Things terminal device and it. If so, the uplink data is input into the uplink message queue of the data storage unit (3), the uplink message is processed and stored, and the processed uplink message is sent to the third-party application server to complete the data interaction between the Internet of Things terminal device and the third-party application server. If not, the data request message is rejected.

10. The Internet of Things access system according to claim 7, characterized in that: The execution steps of the downlink data include: The third-party application server sends a data message containing downlink data to the access server, and the access server verifies whether the data format of the data message is correct. If so, it executes the next step; if not, it rejects the data message; The access server checks the format and attribution of the device serial number in the data message, and rejects the data message if the format or attribution is incorrect; if the format and attribution are correct, proceeds to the next step; The access server checks the AppId and ApiKey in the data message. If either the AppId or the ApiKey is incorrect, the data message is rejected. If both the AppId and the ApiKey are correct, the next step is executed. The access server inputs the downlink data into the downlink message queue of the data storage unit (3), processes and stores the downlink message, and sends the processed downlink message to the network terminal device to which the third-party application server belongs, thereby completing the data interaction between the third-party application server and the network terminal device.

Images