A method and system for controlling an Internet of Things gateway

Abstract

The present invention discloses a method for controlling an Internet of Things gateway, including: obtaining communication data sent by a communication tag; judging whether the communication data passes key verification, judging if yes, decrypting the communication data; judging whether the tag identity information is a preset access system permission, judging if yes, extracting the power data in the tag data, judging whether the power data is equal to the preset low power, judging if yes, adding the tag identity information to the preset low power tag list, judging whether the preset time filter table contains the tag identity information, judging if yes, adding the tag identity information to the preset time filter table, extracting the request type in the tag data; judging whether the request type is an upload server type, judging if yes, adding the tag data to a dedicated protocol stack for sending. Accordingly, the present invention discloses an Internet of Things gateway control system. By adopting the present invention, node devices of multiple communication protocols can be accessed, and data redundant fields can be reduced, thereby saving costs.

Description

Technical Field

[0001] The present invention relates to Internet control technology, and in particular to an Internet of Things gateway control method and system Background Art

[0002] The IoT gateway is a signal transfer device between IoT tags and servers. It receives signals sent by IoT tags and forwards the signals to the server to realize data transmission between IoT tags and IoT servers.

[0003] Comparative document CN 105898900A discloses a gateway system for large-scale zigbee sensor networks and mobile communication networks. It takes S3C6410 SoC as the core, connects multiple zigbee wireless sensor network units through UART interface, and connects mobile communication network units through USB interface to build the system hardware platform. The software part is divided into application layer and network layer. The application layer implements dynamic management of external interfaces and maintains routing tables and other functions. The network layer runs TCP / IP protocol stack and zigbee protocol stack, and runs protocol conversion program. The scalability design of the hardware part and the layered design and dynamic routing table mechanism of the software part make the system have great advantages in application scenarios that require large-scale deployment of zigbee sensor networks.

[0004] However, the existing IoT gateway control methods have the following disadvantages:

[0005] Designed only for a certain wireless communication technology, with limited access capabilities. For example, a LoRaWan gateway can only access IoT nodes (tags) based on LoRa communication technology.

[0006] Existing IoT gateway communication protocols mostly use character strings for encoding, which have many redundant fields, waste bandwidth, and increase operator costs. Summary of the invention

[0007] The technical problem to be solved by the present invention is to provide an Internet of Things gateway control method and system, which can access node devices of multiple communication protocols, reduce data redundant fields, and save costs.

[0008] In order to solve the above technical problems, the present invention provides an Internet of Things gateway control method, including: obtaining communication data sent by a communication tag; performing key verification on the communication data, judging whether the communication data passes the key verification, judging if yes, decrypting the communication data, generating tag data, and extracting tag identity information in the tag data; judging whether the tag identity information is a preset access system permission, judging if yes, extracting power data in the tag data, judging whether the power data is equal to a preset low power, judging if yes, adding the tag identity information to a preset low power tag list, judging whether the tag identity information exists in a preset time filter table, judging if yes, adding the tag identity information to a preset time filter table, and extracting the request type in the tag data; judging whether the request type is an upload server type, judging if yes, adding the tag data to a dedicated protocol stack for sending.

[0009] As an improvement of the above scheme, the dedicated protocol is the M2S protocol, and the steps of adding the tag data to the dedicated protocol stack for sending include: extracting the network type information in the tag data; judging whether the network type information is an Ethernet type, if so, binary-encoding the tag data, generating a data frame, and sending the data frame through the Ethernet interface; judging whether the network type information is a wireless network type, if so, binary-encoding the tag data, generating a data frame, and sending the data frame through the wireless network interface.

[0010] As an improvement to the above scheme, adding the tag data to a dedicated protocol stack for sending also includes: before the step of extracting the network type information in the tag data, performing the following steps: obtaining the network drop rate of the sending tag of the tag data; determining whether the network drop rate is greater than a preset drop alarm threshold, and if so, adding the network drop rate to the tag data.

[0011] As an improvement of the above scheme, the step of obtaining the network disconnection rate of the sending tag of the tag data includes: obtaining the number of received data sent by the sender of the tag data in the time filter table, and extracting the sending sequence number of the tag data; calculating the network disconnection rate based on the number of received data and the sending sequence number.

[0012] As an improvement of the above solution, when the communication tag is a LoRaWan tag, the step of obtaining the communication data sent by the communication tag includes: obtaining a signal sent by the LoRaWan tag; parsing the signal through the LoRaWan protocol stack to generate communication data.

[0013] Correspondingly, the present invention discloses an Internet of Things gateway control system, comprising: a communication data acquisition module, used for acquiring communication data sent by a communication tag; a key verification module, used for performing key verification on the communication data, judging whether the communication data passes the key verification, and if so, decrypting the communication data, generating tag data, and extracting tag identity information in the tag data; a tag data management module, used for judging whether the tag identity information is a preset access system permission, and if so, extracting power data in the tag data, judging whether the power data is equal to a preset low power, and if so, adding the tag identity information to a preset low power tag list, judging whether the tag identity information exists in a preset time filter table, and if so, adding the tag identity information to the preset time filter table, and extracting the request type in the tag data; a tag data sending module, used for judging whether the request type is an upload server type, and if so, adding the tag data to a dedicated protocol stack for sending.

[0014] As an improvement of the above scheme, the dedicated protocol is the M2S protocol, and the tag data sending module includes: a network type extraction unit, used to extract the network type information in the tag data; an Ethernet sending unit, used to determine whether the network type information is an Ethernet type, and if it is determined to be yes, the tag data is binary-encoded to generate a data frame, and the data frame is sent through the Ethernet interface; a wireless sending unit, used to determine whether the network type information is a wireless network type, and if it is determined to be yes, the tag data is binary-encoded to generate a data frame, and the data frame is sent through the wireless network interface.

[0015] As an improvement of the above scheme, the label data sending module also includes: a drop rate acquisition unit, which is used to obtain the network drop rate of the sending label of the label data; a drop alarm judgment unit, which is used to judge whether the network drop rate is greater than a preset drop alarm threshold, and a drop rate loading unit, which is used to judge if it is yes and add the network drop rate to the label data; the label data sending module calls the drop rate acquisition unit, the drop alarm judgment unit and the drop rate loading unit before calling the network type extraction unit.

[0016] As an improvement of the above scheme, the offline rate acquisition unit includes: a offline rate parameter acquisition subunit, which is used to obtain the offline rate parameter, obtain the number of received data sent by the sender of the label data in the time filter table, and extract the sending sequence number of the label data; a offline rate calculation subunit, which is used to calculate the network offline rate based on the received number and the sending sequence number.

[0017] As an improvement of the above scheme, the communication data acquisition module includes: a LoRaWan signal acquisition unit, used to acquire the signal sent by the LoRaWan tag; a LoRaWan signal parsing unit, used to parse the signal through the LoRaWan protocol stack to generate communication data; when the communication tag is a LoRaWan tag, the communication data acquisition module calls the LoRaWan signal acquisition unit and the LoRaWan signal parsing unit.

[0018] The implementation of the present invention has the following beneficial effects:

[0019] The Internet of Things gateway control method and system of the present invention can access node devices of multiple communication protocols, reduce data redundant fields, and save costs.

[0020] Specifically, after obtaining the communication data sent by the communication tag, the communication data is key-verified. Passing the key verification means that the communication data has obtained network access permission, that is, it can be transmitted to the server through the gateway. After that, the communication data is managed. First, the communication data is decrypted to generate tag data, and the tag identity information in the tag data is extracted. If the tag identity information has preset access system permissions, power management and time filtering operations are performed. Finally, the tag data is added to the dedicated protocol stack for transmission according to the request type, thereby completing the network access permission, data management and forwarding operations for different protocol data, and realizing the forwarding of multiple protocol data.

[0021] Furthermore, the dedicated protocol for sending data adopts the M2S protocol. When sending data, the tag data is binary-encoded to generate a data frame, and the data frame is sent through an Ethernet interface or a wireless network interface. There is no redundant field caused by string encoding, which is different from the reduction of string encoding. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] Figure 1 It is an overall flow chart of the Internet of Things gateway control method of the present invention;

[0023] Figure 2 It is a flow chart of the Internet of Things gateway control method of the present invention, in which tag data is added to a dedicated protocol stack for transmission;

[0024] Figure 3 It is a flowchart of the processing steps of adding tag data to a dedicated protocol stack before sending in the Internet of Things gateway control method of the present invention;

[0025] Figure 4 It is a flow chart of the network disconnection rate of the sending tag of the Internet of Things gateway control method of the present invention for obtaining tag data;

[0026] Figure 5It is a flow chart of obtaining communication data sent by a communication tag when the communication tag is a LoRaWan tag in the Internet of Things gateway control method of the present invention;

[0027] Figure 6 It is a structural schematic diagram of the Internet of Things gateway control system of the present invention;

[0028] Figure 7 It is a hardware architecture diagram of the Internet of Things gateway control system of the present invention;

[0029] Figure 8 It is a structural schematic diagram of the first embodiment of the tag data sending module of the Internet of Things gateway control system of the present invention;

[0030] Fig. 9 It is a structural schematic diagram of a second embodiment of a tag data sending module of an Internet of Things gateway control system of the present invention;

[0031] Fig.10 It is a structural schematic diagram of a disconnection rate acquisition unit of an Internet of Things gateway control system of the present invention;

[0032] Fig.11 It is a structural schematic diagram of a communication data acquisition module of an Internet of Things gateway control system of the present invention. DETAILED DESCRIPTION

[0033] In order to make the purpose, technical solution and advantages of the present invention clearer, the present invention will be further described in detail below with reference to the accompanying drawings. It is hereby stated that the directional terms such as up, down, left, right, front, back, inside, outside, etc. that appear or will appear in the text of the present invention are only based on the accompanying drawings of the present invention, and are not specific limitations of the present invention.

[0034] Figure 1 It is an overall flow chart of the Internet of Things gateway control method of the present invention, including:

[0035] S101. Acquire communication data sent by a communication tag.

[0036] Communication tags include the use of different communication protocols, such as 856M protocol, LoRa protocol, WiFi protocol, Bluetooth 5.0 protocol, 2.4G communication protocol, etc.

[0037] S102, performing key verification on the communication data to determine whether the communication data passes the key verification, and if it is determined to be yes, decrypting the communication data, generating tag data, and extracting tag identity information from the tag data.

[0038] Key verification is a key step in network access permission. Each communication data contains specific key data to identify whether the source of the signal is legal. Once the key data is verified, it means that the communication data is sent by a tag in the Internet of Things, and the data can be allowed to enter the Internet of Things for transmission, including uploading to the server or sending to other Internet of Things terminals.

[0039] After confirming the source of the communication data, the communication data is decrypted to generate tag data, and the tag identity information in the tag data is extracted, also known as tag ID (Identification, referred to as ID).

[0040] S103, determine whether the tag identity information is the preset access system permission, if it is, extract the power data in the tag data, determine whether the power data is equal to the preset low power, if it is, add the tag identity information to the preset low power tag list, determine whether the tag identity information exists in the preset time filter table, if it is, add the tag identity information to the preset time filter table, and extract the request type in the tag data.

[0041] This step is the main content of tag data management, including power management and time filtering. Through power management, the specific location of low-power tags can be sent to management personnel in a timely manner to remind them to perform maintenance in a timely manner. Through time filtering, the time of sending and receiving communication data can be recorded, and data such as network disconnection rate can be calculated based on this.

[0042] After tag data management, extract the request type information in the tag data for subsequent forwarding work.

[0043] S104: Determine whether the request type is an upload server type, and if so, add the tag data to a dedicated protocol stack for transmission.

[0044] When the request type is an upload server type, the tag data is added to the dedicated protocol stack for encoding and the relevant communication interface is called for forwarding operations to realize the forwarding of the tag data.

[0045] Furthermore, the dedicated protocol is the M2S protocol, and the steps of adding the tag data to the dedicated protocol stack for sending include:

[0046] S201. Extract network type information from label data.

[0047] The network type information is used to identify the target network type of the tag data, including Ethernet type and wireless network type.

[0048] S202: Determine whether the network type information is an Ethernet type. If it is, perform binary encoding on the tag data to generate a data frame, and send the data frame through the Ethernet interface.

[0049] S203: Determine whether the network type information is a wireless network type, and if so, perform binary encoding on the tag data to generate a data frame, and send the data frame through a wireless network interface.

[0050] It should be noted that for servers of different target networks, label data needs to be sent through different network interfaces, such as sending label data to an Ethernet server through an Ethernet interface, or sending label data through a wireless network interface, such as a 4G network interface.

[0051] The M2S protocol is a pure binary protocol that uses binary encoding to replace path strings that occupy more traffic, and reduces unnecessary fields in the protocol header information, thereby reducing traffic waste. The M2S protocol stack frame format is shown in Table 1:

[0052] name Length / Bytes Example Frame Header 1 0xAA / 55 Pipeline Encoding 1 0xYY Frame type code 1 0x80 Device ID Format 1 0x04 Device ID Custom 0x04 Frame number 1 0x01 Frame length 2 0x04 Frame data Custom 0x11223344 Frame Check 1 0x37

[0053] Table 1

[0054] The M2S protocol, including the M2S protocol stack frame format, is a specially designed communication protocol with strong privacy and high security.

[0055] Furthermore, if Figure 3 As shown, adding the tag data to the dedicated protocol stack for transmission also includes:

[0056] Before extracting the network type information in the tag data, perform the following steps:

[0057] S301, obtaining the network disconnection rate of the sending tag of the tag data;

[0058] S302: Determine whether the network disconnection rate is greater than a preset disconnection alarm threshold, and if so, add the network disconnection rate to the tag data.

[0059] The network drop rate is an important parameter that reflects the connection strength between the IoT tag and the gateway, and even the entire IoT network. When the network drop rate is greater than the preset drop alarm threshold, it means that the signal strength of the IoT is weak, and the signal environment affects the signal transmission of the IoT, which in turn affects the user's usage effect. The network drop rate needs to be added to the tag data to upload to the server to remind the network administrator to perform maintenance.

[0060] Furthermore, if Figure 4 As shown, the steps of obtaining the network disconnection rate of the sending tag of the tag data include:

[0061] S401, obtaining the number of received data sent by the sender of the tag data in the time filter table, and extracting the sending sequence number of the tag data.

[0062] S402: Calculate the network disconnection rate according to the received quantity and the sent sequence number.

[0063] The time filter table records the time when the gateway receives data and the source of the signal, so as to count the number of receptions from a specific source. The sending sequence number reflects the number of signals sent by the IoT tag. Then, the network disconnection rate is calculated based on the number of receptions and the sending sequence number:

[0064]

[0065] Among them, R is the network disconnection rate, Se is the number of transmissions determined according to the transmission sequence number, and Re is the number of receptions.

[0066] For example, if the number of received packets is 30 and the sending sequence number is S0040, the number of sent packets is 40. The network disconnection rate calculated according to the above formula is 25%.

[0067] Furthermore, if Figure 5 As shown, when the communication tag is a LoRaWan tag, the steps of obtaining the communication data sent by the communication tag include:

[0068] S501. Acquire a signal sent by a LoRaWan tag.

[0069] S502: Analyze the signal through the LoRaWan protocol stack to generate communication data.

[0070] Due to the encoding characteristics of the LoRaWan protocol, the signal needs to be parsed after it is acquired in order to convert it into communication data.

[0071] Accordingly, the present invention discloses an Internet of Things gateway control system 100, such as Figure 6 As shown, including:

[0072] The communication data acquisition module 1 is used to acquire the communication data sent by the communication tag.

[0073] Communication tags include the use of different communication protocols, such as 856M protocol, LoRa protocol, WiFi protocol, Bluetooth 5.0 protocol, 2.4G communication protocol, etc.

[0074] Figure 7 The hardware architecture diagram of the IoT gateway control system is shown. The communication data acquisition module 1 includes:

[0075] 856M communication module, preferably sub1G RF IC;

[0076] LoRa communication module, preferably SX1301 or SX1255;

[0077] WiFi communication module, preferably ZW6201;

[0078] Bluetooth 5.0 communication module, preferably NRF52832;

[0079] 2.4G communication module, the preferred model is NRF2401.

[0080] The key verification module 2 is used to perform key verification on the communication data, determine whether the communication data passes the key verification, and if it is determined to be yes, decrypt the communication data, generate label data, and extract label identity information from the label data.

[0081] Key verification is a key step in network access permission. Each communication data contains specific key data to identify whether the source of the signal is legal. Once the key data is verified, it means that the communication data is sent by a tag in the Internet of Things. The key verification module 2 can allow the data to enter the Internet of Things for transmission, including uploading to the server or sending to other Internet of Things terminals.

[0082] After confirming the source of the communication data, the key verification module 2 decrypts the communication data to generate tag data, and extracts tag identity information in the tag data, also known as tag ID (Identification, ID for short).

[0083] The tag data management module 3 is used to determine whether the tag identity information is the preset access system permission. If it is, it extracts the power data in the tag data, determines whether the power data is equal to the preset low power, if it is, it adds the tag identity information to the preset low power tag list, determines whether the tag identity information exists in the preset time filter table, if it is, it adds the tag identity information to the preset time filter table, and extracts the request type in the tag data.

[0084] This step is the main content of tag data management, including power management and time filtering. Through power management, the tag data management module 3 promptly sends the specific location of low-power tags to the management personnel to remind them to perform maintenance in time. Through time filtering, the tag data management module 3 records the time of sending and receiving communication data, and provides other functional modules with the calculation of network disconnection rate and other data.

[0085] After performing tag data management, the tag data management module 3 extracts the request type information in the tag data for subsequent forwarding work by other functional modules.

[0086] The tag data sending module 4 is used to determine whether the request type is an upload server type, and if it is, add the tag data to the dedicated protocol stack for sending.

[0087] When the request type is an upload server type, the tag data sending module 4 adds the tag data to the dedicated protocol stack for encoding and calls the relevant communication interface for forwarding operation to realize forwarding of the tag data.

[0088] Furthermore, the dedicated protocol is the M2S protocol, such as Figure 8 As shown, the tag data sending module 4 includes:

[0089] The network type extraction unit 41 is used to extract network type information from the label data.

[0090] The network type information is used to identify the target network type of the tag data, including Ethernet type and wireless network type.

[0091] The Ethernet sending unit 42 is used to determine whether the network type information is an Ethernet type, and if it is determined to be yes, binary encode the label data to generate a data frame, and send the data frame through the Ethernet interface;

[0092] The wireless sending unit 43 is used to determine whether the network type information is a wireless network type, and if it is determined to be yes, the tag data is binary-encoded to generate a data frame, and the data frame is sent through the wireless network interface.

[0093] It should be noted that for servers of different target networks, label data needs to be sent through different network interfaces. For example, the Ethernet sending unit 42 sends label data to the Ethernet server through the Ethernet interface, and the wireless sending unit 43 sends label data through a wireless network interface, such as a 4G network interface.

[0094] The M2S protocol is a pure binary protocol that uses binary encoding to replace path strings that occupy more traffic, and reduces unnecessary fields in the protocol header information, thereby reducing traffic waste. The M2S protocol stack frame format is shown in Table 1:

[0095]

[0096]

[0097] Table 1

[0098] The M2S protocol, including the M2S protocol stack frame format, is a specially designed communication protocol with strong privacy and high security.

[0099] Furthermore, if Fig. 9 As shown, the tag data sending module 4 also includes:

[0100] A disconnection rate acquisition unit 44, used to acquire a disconnection rate of a network sending a tag of tag data;

[0101] A disconnection alarm judging unit 45 is used to judge whether the network disconnection rate is greater than a preset disconnection alarm threshold, and a disconnection rate loading unit 46 is used to judge whether the network disconnection rate is greater than a preset disconnection alarm threshold, and add the network disconnection rate to the tag data if the judgment is yes;

[0102] The tag data sending module calls the offline rate acquisition unit 44, the offline alarm determination unit 45 and the offline rate loading unit 46 before calling the network type extraction unit.

[0103] The network drop rate is an important parameter that reflects the connection strength between the IoT tag and the gateway, and even the entire IoT network. The drop alarm judgment unit 45 determines that the network drop rate is greater than the preset drop alarm threshold, indicating that the signal strength of the IoT is weak, and the signal environment affects the signal transmission of the IoT, which in turn affects the user's usage effect. At this time, the drop rate loading unit 46 adds the network drop rate to the tag data to upload it to the server to remind the network administrator to perform maintenance.

[0104] Furthermore, if Fig.10 As shown, the offline rate acquisition unit 44 includes:

[0105] The drop rate parameter acquisition subunit 441 is used for acquiring the drop rate parameter to obtain the number of received data sent by the sender of the tag data in the time filter table, and extract the sending sequence number of the tag data;

[0106] The disconnection rate calculation subunit 442 is used to calculate the network disconnection rate according to the reception quantity and the transmission sequence number.

[0107] The time filter table records the time when the gateway receives data and the signal source, so that the drop rate parameter acquisition subunit 441 counts the number of receptions from a specific source. The sending sequence number reflects the number of signals sent by the IoT tag. Then, the drop rate calculation subunit 442 calculates the network drop rate based on the number of receptions and the sending sequence number:

[0108]

[0109] Among them, R is the network disconnection rate, Se is the number of transmissions determined according to the transmission sequence number, and Re is the number of receptions.

[0110] For example, if the number of received packets is 30 and the sending sequence number is S0040, the number of sent packets is 40. The network disconnection rate calculated according to the above formula is 25%.

[0111] Furthermore, if Fig.11 As shown, the communication data acquisition module 1 includes:

[0112] A LoRaWan signal acquisition unit 11, used to acquire a signal sent by a LoRaWan tag;

[0113] A LoRaWan signal analysis unit 12, used to analyze the signal through the LoRaWan protocol stack and generate communication data;

[0114] When the communication tag is a LoRaWan tag, the communication data acquisition module 1 calls the LoRaWan signal acquisition unit 11 and the LoRaWan signal analysis unit 12 .

[0115] Due to the coding characteristics of the LoRaWan protocol, after the LoRaWan signal acquisition unit 11 acquires the signal, the LoRaWan signal parsing unit 12 needs to parse and process the signal, and then convert the signal into communication data.

[0116] The above is a preferred embodiment of the present invention. It should be pointed out that a person skilled in the art can make several improvements and modifications without departing from the principle of the present invention. These improvements and modifications are also considered to be within the scope of protection of the present invention.

Claims

1. A method for controlling an Internet of Things gateway, characterized in that: include: Acquire communication data sent by the communication tag; Performing key verification on the communication data to determine whether the communication data passes the key verification, and if it is determined to be yes, decrypting the communication data to generate tag data, and extracting tag identity information from the tag data; Determine whether the tag identity information is a preset access system permission, if it is, extract the power data in the tag data, determine whether the power data is equal to the preset low power, if it is, add the tag identity information to the preset low power tag list, determine whether the tag identity information exists in the preset time filter table, if it is, add the tag identity information to the preset time filter table, and extract the request type in the tag data; Determine whether the request type is an upload server type, and if so, add the tag data to a dedicated protocol stack for transmission; The step of adding the tag data to a dedicated protocol stack for sending includes: Extracting network type information from the tag data; Determine whether the network type information is an Ethernet type, and if so, perform binary encoding on the tag data to generate a data frame, and send the data frame through an Ethernet interface; Determine whether the network type information is a wireless network type, and if so, perform binary encoding on the tag data to generate a data frame, and send the data frame through a wireless network interface.

2. The Internet of Things gateway control method as claimed in claim 1, characterized in that: The dedicated protocol is the M2S protocol.

3. The Internet of Things gateway control method as claimed in claim 1, characterized in that: The step of adding the tag data to the dedicated protocol stack for sending further comprises: Before the step of extracting the network type information in the tag data, perform the following steps: Obtaining a network disconnection rate of a sending tag of the tag data; Determine whether the network disconnection rate is greater than a preset disconnection alarm threshold, If the judgment is yes, the network disconnection rate is added to the label data.

4. The Internet of Things gateway control method as claimed in claim 3, characterized in that: The step of obtaining the network disconnection rate of the sending tag of the tag data comprises: Obtaining the number of received data sent by the sender of the tag data in the time filter table, and extracting the sending sequence number of the tag data; The network disconnection rate is calculated according to the received quantity and the sent sequence number.

5. The Internet of Things gateway control method as claimed in claim 1, characterized in that: When the communication tag is a LoRaWan tag, the step of acquiring the communication data sent by the communication tag includes: Obtaining a signal sent by the LoRaWan tag; The signal is parsed through the LoRaWan protocol stack to generate communication data.

6. An Internet of Things gateway control system, characterized in that: include: A communication data acquisition module, used to acquire the communication data sent by the communication tag; A key verification module is used to perform key verification on the communication data, determine whether the communication data passes the key verification, and if it is determined to be yes, decrypt the communication data, generate tag data, and extract tag identity information from the tag data; a tag data management module, used to determine whether the tag identity information is a preset access system permission, if the determination is yes, extract the power data in the tag data, determine whether the power data is equal to a preset low power, if the determination is yes, add the tag identity information to a preset low power tag list, determine whether the tag identity information exists in a preset time filter table, if the determination is yes, add the tag identity information to the preset time filter table, and extract the request type in the tag data; The tag data sending module is used to determine whether the request type is an upload server type, and if it is, add the tag data to a dedicated protocol stack for sending; Wherein, the tag data sending module includes: A network type extraction unit, used to extract network type information from the label data; An Ethernet sending unit, used for judging whether the network type information is an Ethernet type, and if it is judged to be yes, binary encoding the label data to generate a data frame, and sending the data frame through an Ethernet interface; The wireless sending unit is used to determine whether the network type information is a wireless network type, and if it is determined to be, binary encode the tag data to generate a data frame, and send the data frame through a wireless network interface.

7. The Internet of Things gateway control system as claimed in claim 6, characterized in that: The dedicated protocol is the M2S protocol.

8. The Internet of Things gateway control system as claimed in claim 6, characterized in that: The tag data sending module also includes: A disconnection rate acquisition unit, used to acquire a network disconnection rate of a sending tag of the tag data; A disconnection alarm determination unit is used to determine whether the network disconnection rate is greater than a preset disconnection alarm threshold, A disconnection rate loading unit, configured to add the network disconnection rate to the label data if the judgment is yes; The label data sending module calls the offline rate acquisition unit, the offline alarm judgment unit and the offline rate loading unit before calling the network type extraction unit.

9. The Internet of Things gateway control system as claimed in claim 8, characterized in that: The offline rate acquisition unit includes: A drop rate parameter acquisition subunit, used for obtaining the drop rate parameter to obtain the number of received data sent by the sender of the label data in the time filter table, and to extract the sending sequence number of the label data; The disconnection rate calculation subunit is used to calculate the network disconnection rate according to the received quantity and the sent sequence number.

10. The Internet of Things gateway control system as claimed in claim 6, characterized in that: The communication data acquisition module comprises: A LoRaWan signal acquisition unit, used to acquire the signal sent by the LoRaWan tag; A LoRaWan signal parsing unit, used to parse the signal through the LoRaWan protocol stack to generate communication data; When the communication tag is a LoRaWan tag, the communication data acquisition module calls the LoRaWan signal acquisition unit and the LoRaWan signal parsing unit.

Images