CN-121985002-A - Non-blocking type high-concurrency Internet of things platform and testing method

Abstract

The invention relates to a non-blocking type high-concurrency internet of things platform and a testing method, wherein the non-blocking type high-concurrency internet of things platform comprises a data acquisition system, a data analysis system and a data analysis system, wherein the data acquisition system is used for establishing connection with internet of things equipment and receiving and analyzing equipment uplink data; and the message middleware is connected between the data acquisition system and the application system and is used for realizing asynchronous operation between the data acquisition system and the application system. The invention has the beneficial effects that the high-speed data acquisition part is isolated from the relatively slow service processing part, the decoupling of the system is realized, and the maintainability and expansibility of the system are improved.

Inventors

• LI FEI
• JIANG WEN

Assignees

• 浙大城市学院

Dates

Publication Date

20260505

Application Date

20260203

Claims (10)

1. 1. A non-blocking high concurrency internet of things platform, comprising: the data acquisition system is used for establishing connection with the Internet of things equipment and receiving and analyzing the uplink data of the equipment; the application system is used for carrying out service processing on the uplink data of the equipment; and the message middleware is connected between the data acquisition system and the application system and is used for realizing asynchronous operation between the data acquisition system and the application system.
2. 2. The non-blocking high concurrency internet of things platform of claim 1, wherein the message middleware is a rabitmq single message queue node or a rabitmq cluster.
3. 3. The non-blocking high concurrency internet of things platform of claim 1, wherein the data acquisition system comprises a Netty network model, the Netty network model is used for supporting access and verification of at least one internet of things protocol, the internet of things protocol comprises an MQTT browser, a CoAP and a TCP, the application system comprises an application back end and an application front end, the message middleware is used for forwarding device uplink data sent by the data acquisition system to the application back end, the application back end is used for carrying out business processing and/or storage on the device uplink data, and the application front end is communicated with the application back end and used for providing an interactive interface for a user.
4. 4. A method of testing a non-blocking high concurrency internet of things platform as claimed in any one of claims 1 to 3, comprising: S1, simulating Internet of things equipment to issue a message to an Internet of things platform by using a pressure testing tool; S2, the data acquisition system receives and analyzes the message issued by the pressure test tool, and forwards the message to the application system through the message middleware; s3, the application system processes and/or stores the information.
5. 5. The method for testing a non-blocking type high-concurrency internet of things platform according to claim 4, wherein in S1, the pressure testing tool is JMeter, and the message issued by the pressure testing tool follows MQTT protocol.
6. 6. The method for testing a non-blocking high-concurrency internet of things platform according to claim 5, wherein in S1, further comprising: And simulating the Internet of things equipment to send heartbeat information to the message middleware by using the pressure testing tool to realize equipment long connection management.
7. 7. The method for testing the non-blocking high-concurrency internet of things platform according to claim 6, wherein in S2, an uplink data persistence queue is set in a message middleware, after service consumption data, confirmation information needs to be fed back, a dead message queue is configured for the uplink data persistence queue, and when a message is failed in multiple retries, the dead message queue is automatically entered.
8. 8. The method for testing a non-blocking high-concurrency internet of things platform according to claim 6, wherein in S2, further comprising: and respectively establishing a special downlink queue and a persistent offline command queue for the online equipment and the offline equipment.
9. 9. A computer storage medium, characterized in that the computer storage medium has stored therein a computer program which, when run on a computer, causes the computer to perform the method of any of claims 4 to 8.
10. 10. An electronic device, comprising: A memory for storing a computer program; A processor for executing the computer program to implement the method of any one of claims 4 to 8.

Description

Non-blocking type high-concurrency Internet of things platform and testing method Technical Field The invention belongs to the technical field of the Internet of things, and particularly relates to a non-blocking type high-concurrency Internet of things platform and a testing method. Background In the early development stage of the Internet of things, the platform only needs to be connected with a small amount of Internet of things equipment, and the Internet of things platform only has the function of collecting data which is only used for local monitoring. After receiving the data, the early-stage internet of things platform directly sends the data to a service processing part or stores the data in a disk and other devices. But the collected data is directly processed in service, no matter the service processing is local or cloud, the mode has obvious defects that 1) the data is seriously coupled with a service system, the service system is directly connected after the data is collected, once the service system fails, equipment data is directly lost, a buffer bottom-blocking mechanism is not available, 2) all functions of accessing, verifying and distributing the data are concentrated on a server component (such as an MQTT Broker) to cause that mass equipment cannot be accessed and detection data is easy to lose, 3) a mature long connection management mechanism is lacking, namely no heartbeat detection, disconnection reconnection, half package/package sticking processing is lacking, enterprise grade characteristics such as dead letter queues, delay queues, mirror image clusters and the like are not available, the core service system is difficult to be connected in a butt joint mode, and on-site network fluctuation easily causes equipment offline, data messy codes and the like. With the development of the technology and application of the internet of things and in recent years, the industry of the internet of things has developed a new situation by integrating various communication technologies, sensor technologies, computer technologies and artificial intelligence technologies. The main expression is as follows: 1) Explosive growth in the networking scale of devices. With the promotion of the application of the Internet of things of 4.0 industry, smart cities and the like, enterprises are likely to realize the large-scale networking of tens of thousands/hundreds of thousands of devices. 2) Business extends from "data acquisition" to "full scene applications". The initial internet of things platform core complaints are that data can be acquired, and in a large-scale stage, the platform needs to support multi-service system linkage. The equipment data needs to meet the requirements of flowing in all directions, such as synchronous flowing time sequence database (storage), AI alarm system (fault detection), business processing, digital twin platform (real-time rendering) and the like, backward issuing instructions (such as machine tool processing parameter configuration and remote shutdown) to equipment, and requiring the instructions to be 'not lost and traceable', and supporting stable communication of cross-regional and weak network scenes (such as remote factory distribution equipment and mobile terminals). 3) Enterprise level reliability and compliance requirements are improved. In the scene of industrial Internet of things, core data such as machine tool processing data, fault alarm information, production work order instructions and the like can cause production accidents or economic loss once lost/delayed, and meanwhile, enterprises have compliance requirements on 'data traceability, fault locatable and high availability' of a system, so that a platform is updated from 'functionality' to 'reliability'. Due to the development of the Internet of things industry, the demands of enterprises on the novel Internet of things platform are improved to be high-performance, high-reliability, easy to expand and easy to maintain. High performance refers to supporting mass devices to communicate concurrently with low latency. The equipment side is required to support access of thousands of equipment, such as in industrial Internet of things, thousands of machine tools/robots are supported to be accessed simultaneously, on the service side, real-time response is required for instruction issuing (such as the delay of feeding and discharging instructions of the robots is less than 50 ms), normal service is avoided, various weak network environments are adapted on the network side, and data are required to be ensured not to be interrupted even in severe environments with low bandwidth and high packet loss rate. Reliability refers to zero loss of core data and traceability of instructions. The industrial Internet of things is taken as an example, the reliability mainly refers to three types of reliability, namely 1) data reliability, machine tool fault warning and production tool data need to be sent 100%, even if a sy