Unified entry, exit and classification processing method for data information flow of IoT devices

Abstract

The present invention discloses a method for unified entry and exit and classified processing of data information flows of Internet of Things devices. The Internet of Things devices send device information data to a front-end transceiver module. The front-end transceiver module obtains a protocol type based on a device ID and sends the device information data to a corresponding protocol processing module. The protocol processing module parses the device information data and stores it in a database. Based on the service type obtained from the parsing, the data information is sent to a corresponding service processing module. The service processing module processes the data information and returns the processed data to the front-end transceiver module. The front-end transceiver module sends the data to the Internet of Things device, stores it in a database, or sends it to a client. The present invention realizes unified entry and exit and classified balanced processing of information flow processing, which not only increases the service's information processing capability but also increases its own maintenance convenience. It has a relatively good effect on the distributed deployment of services or deployment on the same server.

Description

Technical Field

[0001] The present invention relates to the technical field of data processing for Internet of Things platforms and device services, and in particular to a method for unified entry, exit, and classification processing of data information flows of Internet of Things devices. Background Art

[0002] The Internet of Things (IoT) refers to the use of various devices and technologies, such as information sensors, radio frequency identification (RFID), global positioning systems (GPS), infrared sensors, and laser scanners, to collect real-time information about objects or processes that require monitoring, connection, and interaction. This information includes acoustic, optical, thermal, electrical, mechanical, chemical, biological, and location information. This information is then connected to networks to achieve ubiquitous connectivity between objects and between objects and people, enabling intelligent perception, identification, and management of objects and processes. The IoT is an information carrier based on the internet and traditional telecommunications networks, enabling all independently addressable, common physical objects to form an interconnected network.

[0003] With the development of IoT technology, more and more devices are connecting to cloud platforms, and the number is increasing significantly. Various types of IoT devices are connected to cloud platforms and systems through IoT smart gateways, which have increasingly demanded uniformity and efficient and rapid processing. However, many existing devices on the market need to be connected to cloud platforms. The deployed server may be a small intranet server. These devices have different interaction protocols and data formats, corresponding processing procedures and requirements, and require different program services. To ensure the unified and differentiated processing of information flows from different devices, a unified input and output and classification processing method involving the input and output of multiple types of devices is required. Summary of the Invention

[0004] The purpose of the present invention is to provide a method for unified entry, exit and classification processing of data information flow of Internet of Things devices, which is used to solve the problem in the prior art that Internet of Things devices connected to the cloud platform cannot uniformly enter, exit and classify information flow due to different interaction protocols and data formats.

[0005] The present invention solves the above problems through the following technical solutions:

[0006] A method for unified ingress and egress and classification processing of data information flows of IoT devices, comprising:

[0007] Step S1: Add IoT device information to the database, including device ID, device type corresponding to the device ID, protocol type and service type, information validity period, and encryption flag;

[0008] Step S2: The IoT device sends device information data to the front-end transceiver module. The front-end transceiver module parses the device information data to obtain a device ID, searches the database for the protocol type corresponding to the device ID, and sends the device information data to the corresponding protocol processing module.

[0009] Step S3: The protocol processing module verifies the device information data, parses the verified device information data, stores the parsed data in the database, and sends the data information to the corresponding business processing module according to the business type corresponding to the parsed device ID;

[0010] Step S4: The business processing module processes the data information according to the business logic and business requirements, and returns the processed data to the front-end transceiver module, which sends the data to the IoT device, stores it in the database, or sends it to the client.

[0011] IoT devices and clients communicate with the front-end transceiver module, which is in communication with multiple protocol processing modules. Each protocol processing module is in communication with one or more business processing modules, and each business processing module is in communication with the front-end transceiver module. The front-end transceiver module, protocol processing module, and business processing module are in communication with the database, thereby unifying the data input and output of IoT devices. At the same time, data streams of different device types and interaction protocols are classified and processed, and data is persisted. The processed information data is then further classified and processed according to different business needs. Through the unified transceiver of the front-end module, the classification processing of the protocol processing module, the demand processing of the business processing module, and the persistence processing of the database, the concurrent processing capability of information from different devices is achieved, the uniformity and security of external information are improved, and the performance and security of the overall service and system are greatly increased.

[0012] The protocol types include the Modbus communication protocol and the GW376.1 communication protocol. Device information data for the Modbus communication protocol includes an address, function code, data, and a check code; device information data for the GW376.1 communication protocol includes a start character, length, control field, address field, link user data, a check code, and an end character. It should be noted that the present invention is not limited to these two communication protocols, and the data format of the communication protocols can be expanded.

[0013] The encryption flag is used to encrypt and decrypt information when IoT devices interact with the front-end transceiver module. The encryption flag is automatically generated and unique for each IoT device. During interaction with the front-end transceiver module, the IoT gateway device generates corresponding device identity information (including the device ID string and encryption flag). Once a connection is established, the front-end device associates this device ID with the device connection information, creating a key-value pair relationship to facilitate locating the corresponding device connection information using the device ID.

[0014] Compared with the prior art, the present invention has the following advantages and beneficial effects:

[0015] (1) The present invention achieves unified inflow and outflow, classified and balanced processing of information flow, and internal coupling between the protocol processing module and the business processing module. This not only increases the service's information processing capabilities, but also makes it easier to maintain, greatly improving the performance and security of the overall service and system, and has a relatively good effect on distributed deployment of services or deployment on the same server.

[0016] (2) The present invention utilizes a database read / write program to perform database read / write operations, including simple or complex database operations such as adding, deleting, modifying, and querying data, and to perform read / write operations on various data such as device information and service information. The database read / write program can be used by a front-end program, a protocol processing program, a business processing program, and other program services. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] Figure 1 This is a principle block diagram of the present invention. DETAILED DESCRIPTION

[0018] The present invention will be further described in detail below with reference to the examples, but the embodiments of the present invention are not limited thereto.

[0019] Example:

[0020] Combined with attachment Figure 1 As shown, a unified entry, exit and classification processing method for data information flow of IoT devices includes a front-end transceiver module that is communicatively connected to the IoT device and the client, the front-end transceiver module is communicatively connected to multiple protocol processing modules, each protocol processing module is communicatively connected to one or more business processing modules, each business processing module is communicatively connected to the front-end transceiver module, and the front-end transceiver module, the protocol processing module and the business processing module are communicatively connected to a database, wherein:

[0021] The front-end transceiver module is the external transceiver interface of the entire platform system. It is responsible for maintaining the connection between all devices and the data transmission and reception interaction, maintaining the connection between the device and the platform program, and determining the protocol type of the device information data. The information data is initially processed and distributed to the corresponding protocol processing module.

[0022] The protocol processing module is used to process special device protocol information. Devices of different protocol types may send and receive different information, and the data encapsulation and parsing processing logic is also different. The protocol processing module will check whether the information packets received and sent by the device are complete, whether they comply with the provisions of the protocol document, whether they are within the normal logical range, etc., and parse and encapsulate the information packets that meet the requirements according to the corresponding protocol content. Each device type with different interactive protocols has a corresponding protocol handler, which is specifically used to handle the information parsing and encapsulation of all devices belonging to this type. The processed device data information is pushed to the corresponding business processing module. Each protocol handler is independent of each other. Turning off and on one of the protocol handlers will not affect the normal operation of other protocol processing modules;

[0023] The business processing module further processes device data according to business logic and requirements. It receives information from the protocol processing module or the front-end processor, processes it according to business requirements, and then passes it to the front-end transceiver module. The front-end transceiver module uses database read / write programs to store the information in the database or provide it for interactive use by the front-end program. Different projects have different business requirements and business logic, and the business processing module processes device data accordingly. Each business processing module corresponds to a project requirement and may include different types of devices. Different types of device information can be processed within the same business processing program. Data from the same device can also be processed in different business processing modules.

[0024] Database read / write programs are used to read and write data from and to the database. These programs include simple or complex database operations such as adding, deleting, modifying, and querying data, as well as reading and writing various data such as device information and service information. These programs can be used by modules such as the front-end processor, protocol processing module, and business processing module.

[0025] Methods include:

[0026] Step S1: Add IoT device information to the database, including device ID, device type corresponding to the device ID, protocol type and service type, information validity period, and encryption flag;

[0027] Devices can be added and registered by customers using a client program, or by system maintenance personnel, either individually or in batches. Registration uses the device's unique IMEI number, which generates a device ID string, an encryption flag, and information validity period, which are then stored in the database. During initial device registration, the system automatically generates the device ID, encryption flag, and information validity period. It also obtains the device type and service type. The device type determines the protocol program associated with the device, while the service type determines the service program associated with the device ID. The encryption flag is used to encrypt and decrypt information when the IoT device interacts with the front-end processor. It is automatically generated for each device and is unique. For example, it can be a random number between 1 and 255. When interacting with the front-end transceiver module, the IoT gateway device generates its corresponding device identity information (including the device ID string and encryption flag). Once a connection is established, the front-end processor associates the device ID with the device connection information, creating a key-value pair to facilitate locating the corresponding device connection information by device ID.

[0028] The device data information flow is processed in two parts: upstream and downstream.

[0029] 1. During device information uplink, all IoT devices share the same server connection address and port number, and all devices are connected to the front-end transceiver module. After executing relevant instructions such as acquisition control, the IoT device sends device information data A0 to the front-end transceiver module in accordance with the requirements of the uplink interaction protocol. The front-end transceiver module initially parses the device ID in the data packet and searches the database for a corresponding device ID and device protocol type. If the device ID does not exist in the database, the IoT device is unknown, and the front-end transceiver module disconnects the IoT device. If the device ID exists in the database, the IoT device is normal, and the front-end transceiver module sends device information data packet A0 to the corresponding protocol processing module A based on the device protocol type. Protocol processing module A determines whether device information data A is complete, complies with the protocol document, and falls within the normal logical range. It then parses and processes the corresponding protocol content for the information packets that meet the requirements. The processed data information A1 is updated and stored in the database and sent to the corresponding business processing module. The business processing module processes the corresponding device information data A1 according to the business needs of different projects, and hands the processed data A2 to the database reading and writing program or provides it to the front-end project program for interactive use through the front-end program.

[0030] For example, if it is a Modbus communication protocol, it will include the address, function code, data, and check code; if it is a GW376.1 communication protocol, it will include the start character, length, control field, address field, link user data, check code, and end character. The communication protocol format can be expanded.

[0031] For example, if the packet is a Modbus communication protocol, and a temperature packet is 01030200017984, the protocol processing module will parse it and convert it into {Device ID: A, Address: 01, Function Code: 03, Data: 020001, Checksum: 7984}. This data is A1. Data A1 is then passed to the corresponding business processing module for further processing and stored in the database.

[0032] This involves the interactive parsing of different communication protocols, including data packet verification and data verification through checksums. Other protocols are also processed according to their corresponding protocol formats, such as the GW376.1 communication protocol.

[0033] Before parsing, the data is a hexadecimal string. After parsing, according to the protocol content format, the value of each content in the data can be displayed. From a hexadecimal data packet, a JSON data string A1 is obtained, which can be clearly used and called.

[0034] The business processing module involves further processing of business data based on business needs. For example, after protocol processing, data A1 is parsed into {Device ID: A, Address: 1, Function Code: 3, Temperature: 1, Checksum: 25CA}, resulting in data A2. This data can be returned to the front-end transceiver module, where it is pushed to the client and stored in the database.

[0035] Second, during device information downlink, when the client initiates a call to the front-end transceiver module for a specific device information B0 interface in a service program, the front-end transceiver module determines the device ID and interface information in the call, searches the database for the corresponding device, and returns a failure message if the device does not exist. If so, it distributes the corresponding device information to the corresponding service processing module. The service processing module receives the corresponding information data B0, encapsulates it according to the service logic information, and sends the protocol type of the device to which the information data B1 belongs to the corresponding protocol processing module B. Protocol processing module B re-encapsulates the contents of the IoT uplink interaction protocol into message B2. For example, the protocol processing module extracts and encapsulates message data B1 {Device ID: B, Address: 01, Function Code: 06, Data 0001007C}, generates the check code D9EB, and obtains the data {Device ID: B, Address: 01, Function Code: 06, Data: 0001007C, Check code: D9EB}. This ultimately generates the Modbus protocol packet 01060001007CD9EB. Message data B2 contains this packet and the device ID. Finally, device information data B2 is sent to the front-end transceiver module. The front-end transceiver module finds the corresponding device connection B and sends the data to IoT device B for execution.

[0036] In an embodiment, different protocol processing programs (such as A) process different protocol information (such as A), and starting or stopping one of the protocol processing programs (such as A) will not affect the operation of other protocol programs (such as B).

[0037] Although the present invention is described herein with reference to illustrative embodiments of the present invention, the above embodiments are merely preferred embodiments of the present invention, and the embodiments of the present invention are not limited to the above embodiments. It should be understood that those skilled in the art can design many other modifications and implementations, which will fall within the scope and spirit of the principles disclosed in this application.

Claims

1. A method for unified ingress and egress and classification processing of data information flows of IoT devices, characterized in that: include: Step S1: Add IoT device information to the database, including device ID, device type corresponding to the device ID, protocol type and service type, information validity period, and encryption flag; Step S2: The IoT device sends device information data to the front-end transceiver module. The front-end transceiver module is responsible for maintaining the connection of all IoT devices and the data transmission and reception interaction. The front-end transceiver module parses the device information data to obtain the device ID, searches the database for the protocol type corresponding to the device ID, and sends the device information data to the corresponding protocol processing module. Step S3: The protocol processing module is used to process the specific device protocol information. Each device type with different interaction protocols has a corresponding protocol processing program. The protocol processing module verifies the device information data, parses the verified device information data, stores the parsed data information in the database, and sends the data information to the corresponding business processing module according to the business type corresponding to the parsed device ID; Step S4: The business processing module processes the data information according to the business logic and business requirements, and returns the processed data to the front-end transceiver module, which sends the data to the IoT device, stores it in the database, or sends it to the client.

2. The method for unified entry and exit and classification processing of IoT device data information flow according to claim 1, characterized in that: The front-end transceiver module is communicatively connected to a plurality of protocol processing modules, and each protocol processing module is communicatively connected to a plurality of service processing modules.

3. The method for unified entry and exit and classification processing of data information flow of Internet of Things devices according to claim 1 is characterized in that: The protocol types include modbus communication protocol and GW376.1 communication protocol.

4. The method for unified entry and exit and classification processing of data information flow of Internet of Things devices according to claim 3 is characterized in that: The device information data of the protocol type Modbus communication protocol includes address, function code, data and check code; the device information data of the protocol type GW376.1 communication protocol includes start character, length, control field, address field, link user data, check code and end character.

5. The method for unified entry and exit and classification processing of data information flow of Internet of Things devices according to claim 1 is characterized in that: The encryption flag is used to encrypt and decrypt information when the Internet of Things device interacts with the front-end transceiver module. The encryption flag of each Internet of Things device is automatically generated and different.

Images