Real-time database cross-gateway transmission method and system

Abstract

The application provides a real-time database cross-gateway transmission method and system, comprising: connecting a client and a server one by one to establish communication, wherein the client comprises a source cross-gateway module and a client network transmission module, and the server comprises a server network transmission module and a destination cross-gateway module; after confirming that the connection is successful, the source cross-gateway module acquires point table data from the local end, processes the point table data through the client network transmission module, and sends the point table data to the destination cross-gateway module; after receiving the data, the destination cross-gateway module analyzes the data according to different transmission data types, and sends a byte response to the client network transmission module through the server network transmission module according to the analysis result; the point table and the data are independent of each other, the point table supports dynamic updating, the data transmission is not dependent on the point table, and the application is more flexible.

Description

Technical Field

[0001] This invention relates to the field of data transmission technology, and more specifically, to a method and system for real-time database cross-network gateway transmission. Background Technology

[0002] A network gateway, also known as a network security isolation device, is a specialized piece of hardware installed between two unconnected networks. It enables the secure transmission of data resources between these networks under specific restrictions. Therefore, many enterprises choose to use network gateways to isolate networks within security domains and then use their built-in data transfer function to transfer data across security domains to further protect their internal data.

[0003] Patent document CN111200624A discloses a cross-network gateway data transmission method and system, including: a first transmission device receiving data from a data source, generating corresponding data records in a first database, storing the data in a set directory of a first cache in the form of a file, and initially setting the flag bit in the data record to a first state; the first transmission device receiving access from a network gateway and transferring the data to a second network through the network gateway; after the data is taken away by the network gateway, the first transmission device updating the corresponding flag bit in the data record to a second state.

[0004] However, patent document CN111200624A has room for improvement in both real-time performance and reliability when transmitting massive amounts of cross-network gateway data.

[0005] Patent document CN113254411A discloses a method and system for real-time database synchronization across network gateways. It creates mirror tag sets in both internal and external databases of the network gateway, configuring them as mirror sending / receiving databases. The mirror sending end performs snapshot updates, caches successfully updated snapshots, and packages the cached snapshots and corresponding tags into a packet, sending it to the mirror receiving end. The mirror receiving end receives and decompresses the packet, obtaining the corresponding tag and snapshot, and writes it to its local database. The mirror tag set contains the full names of all used tags, and the CRC (Cyclic Redundancy Check) is used to compress all the full names of the tags to obtain the tag CRC.

[0006] However, patent document CN113254411A relies on mirror transmission. The snapshot and the corresponding tag need to be sent to the sending end at the same time. The point table and the data are interdependent and delayed. Summary of the Invention

[0007] To address the shortcomings of existing technologies, the purpose of this invention is to provide a method and system for real-time database cross-network gateway transmission.

[0008] A real-time database cross-network gateway transmission method provided by the present invention is characterized by comprising:

[0009] Step S1: Connect the client and server one-to-one to establish communication. The client includes a source-end cross-network gateway module and a client network transmission module. The server includes a server network transmission module and a destination-end cross-network gateway module.

[0010] Step S2: After confirming a successful connection, the source-end cross-network gateway module obtains the point table data from its local end, processes it through the client network transmission module, and then sends the point table data to the destination-end cross-network gateway module.

[0011] Step S3: After receiving the data, the destination network gateway module parses the data according to the different data types of transmission, and sends a byte back to the client network transmission module through the server-side network transmission module according to the parsing result;

[0012] Step S4: After receiving the byte response, the client network transmission module will determine whether the byte response is valid. If it is, the current byte response will be sent to the source-end cross-network gateway module for parsing and then step S5 will be executed. If not, it means that the source-end cross-network gateway module failed to receive data and then step S6 will be executed.

[0013] Step S5: Determine whether the current byte response is the response of the first sent point table. If yes, proceed to step S7; otherwise, continue monitoring for new collected data.

[0014] Step S6: Determine whether the current byte response is the response of the first sent point table. If yes, return to step S2; otherwise, it means that the data collection failed to be sent. Reconnect to the server according to the network status and return to step S3 to continue sending data.

[0015] Step S7: Determine if the response was successful. If yes, start two threads, namely the first thread and the second thread; otherwise, return to step S2.

[0016] Preferably, step S1 includes:

[0017] Step S1.1: During the startup process, the source-end cross-network gateway module will initiate a connection to the server through the client network transmission module;

[0018] Step S1.2: After receiving the connection request from the source network gateway module, the client network transmission module initiates a connection request to the server network transmission module.

[0019] Step S1.3: After receiving the connection request information sent by the client, the server network transmission module ensures a one-to-one connection between the client and the server.

[0020] Preferably, in step S2, the data type is set to DATA_TAG_SYNC for point table synchronization.

[0021] Preferably, step S2 includes:

[0022] Step S2.1: After receiving the data from the source-end cross-network gateway module, the client network transmission module sends the data packets to the server network transmission module;

[0023] Step S2.2: After receiving the data sent by the client, the server network transmission module will assemble the data according to the header information and send it to the destination network gateway module.

[0024] During the packet splitting process, the already split packets are sent to the server in sequence.

[0025] Preferably, the header of each data packet consists of three fields: SubFlag, SubLen, and DataType. SubFlag indicates the type of packet, SubLen indicates the length of the data, and DataType indicates the type of data.

[0026] Packet types include single packets, tail packets, and non-tail packets; data types include transmission data types and data types.

[0027] Preferably, step S2.1 includes:

[0028] Step S2.1.1: Determine whether the sum of the length of the data and the header length is less than 4069 bytes. If so, no packet splitting is required. Send the data and the corresponding header information directly to the server and set the current packet type to single packet. If not, packet splitting is required. Proceed to step S2.1.2.

[0029] Step S2.1.2: Process the packets according to their length. Except for the last packet, each packet is 4096 bytes long. The bytes in each packet include the data bytes and the header bytes.

[0030] Step S2.1.3: Determine whether the current packet is the last packet. If yes, set the SubFlag flag to the end packet, SubLen to the data length of the last packet, and DataType to the data type. If no, set the SubFlag flag to not be the end packet, SubLen to the length of the packet data, and DataType to the data type of the transmission.

[0031] Preferably, step S2.2 includes: determining the type of the SubFlag flag in the current data header; if it is a single packet, it indicates that the current data is not packetized, and the current data is directly sent to the destination network gateway module.

[0032] If it is not the tail packet, it means that the current data is a sub-packet and an intermediate packet. The sub-packet data is received, reassembled into a packet, and the data type of the transmission and the data of the assembled packet are sent to the destination network gateway module.

[0033] If it is the last packet, it means that the current data is a packet and it is the last packet. The received data packet is reassembled, and the data type of the transmitted packet and the data of the assembled packet are sent to the destination network gateway module.

[0034] Preferably, the first thread is a point table monitoring thread used to monitor whether there are any changes in the point table;

[0035] The second thread is a data collection monitoring thread used to monitor the collected data.

[0036] Preferably, when the first thread detects a change in the point table, it sets the data type to DATA_TAG_SYNC for point table synchronization and sends the point table data to the server.

[0037] When the second thread detects new collected data, it sets the data type to DATA_SNAPSHOTS and sends the collected data to the server.

[0038] A real-time database cross-network gateway transmission system provided by the present invention includes:

[0039] Module M1: Connects the client and server one-to-one to establish communication. The client includes a source-end cross-network gateway module and a client network transmission module. The server includes a server network transmission module and a destination-end cross-network gateway module.

[0040] Module M2: After confirming a successful connection, the source-end cross-network gateway module obtains the point table data from its local end, processes it through the client network transmission module, and then sends the point table data to the destination-end cross-network gateway module.

[0041] Module M3: After receiving the data, the destination network gateway module parses the data according to the different data types being transmitted, and sends a byte back to the client network transmission module through the server-side network transmission module based on the parsing result;

[0042] Module M4: After receiving the byte response, the client network transmission module will determine whether the byte response is valid. If it is, the byte will be sent to the source-end cross-network gateway module for parsing and then trigger module M5; if not, it means that the source-end cross-network gateway module failed to receive data and then triggers module M6.

[0043] Module M5: Determines whether the current byte response is the response from the first sent point table. If yes, it triggers module M7; otherwise, it continues to monitor for new collected data.

[0044] Module M6: Determines whether the current byte response is the response from the first sent point table. If yes, it triggers module M2; otherwise, it indicates that the data collection failed to be sent. Based on the network status, it reconnects to the server and triggers module M3 to continue sending data.

[0045] Module M7: Determines whether the parsing was successful. If so, it starts two threads, namely the first thread and the second thread; otherwise, it triggers module M2.

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

[0047] 1. This invention eliminates the need for disk saving and file exchange, minimizing disk read and write operations and improving real-time transmission performance. Furthermore, by combining real-time database distributed technology, it employs multi-channel parallel transmission of real-time data from multiple data nodes, achieving high-performance transmission of massive amounts of real-time data.

[0048] 2. This invention uses a custom communication protocol to encrypt data and improve data transmission security.

[0049] 3. This invention sets up a data verification method to ensure that the data is not tampered with or lost during transmission, thereby improving transmission reliability.

[0050] 4. In this invention, the point table and data are independent of each other. The point table supports dynamic updates, and the data transmission does not depend on the point table, making it more flexible. Attached Figure Description

[0051] Other features, objects, and advantages of the present invention will become more apparent from the following detailed description of non-limiting embodiments with reference to the accompanying drawings:

[0052] Figure 1 This is a schematic diagram of the working method of the present invention;

[0053] Figure 2 This is a schematic diagram of the system architecture of the present invention. Detailed Implementation

[0054] The present invention will now be described in detail with reference to specific embodiments. These embodiments will help those skilled in the art to further understand the present invention, but do not limit the invention in any way. It should be noted that those skilled in the art can make several changes and improvements without departing from the concept of the present invention. These all fall within the protection scope of the present invention.

[0055] Example 1

[0056] According to the present invention, a method for real-time database cross-network gateway transmission is provided, such as... Figure 1 and Figure 2 As shown, it includes:

[0057] Step S1: Establish a one-to-one connection between the client and the server to build communication. Step S1 includes:

[0058] Step S1.1: During the startup process, the source-end cross-network gateway module will initiate a connection to the destination end through the client network transmission module.

[0059] Step S1.2: After receiving the connection request from the source network gateway module, the client network transmission module initiates a connection request to the server network transmission module.

[0060] Step S1.3: After receiving the connection request information sent by the client, the server network transmission module ensures a one-to-one connection between the client and the server.

[0061] Step S2: After confirming a successful connection, the source-end cross-network gateway module obtains the point table from its local end and sends data to the destination end through the client network transmission module. The data type is set to DATA_TAG_SYNC for point table synchronization. Confirming a successful connection includes checking if other clients are already connected to the server. If not, the connection request is accepted; otherwise, it is rejected.

[0062] Step S2.1: After receiving data from the source-end cross-network gateway module, the client network transmission module packets the data and sends it to the server network transmission module. Step S2 includes:

[0063] Step S2.1.1: Determine if the sum of the data length and header length is less than 4069 bytes. If so, no packet splitting is needed; the data and corresponding header are directly sent to the server. SubFlag indicates the packet type and is set to a single packet. If not, packet splitting is required, and step S2.1.2 is executed. The data packet header consists of three fields: SubFlag, SubLen, and DataType. SubFlag indicates the packet type, SubLen indicates the data length, and DataType indicates the data type. Packet types include single packet, tail packet, and non-tail packet; data types include transmission data type and data type.

[0064] Step S2.1.2: Packet segmentation is performed according to length. Excluding the last packet, each packet is 4096 bytes long, including data and a header. If the current packet is not the last packet, the SubFlag flag is set to "not the tail packet," the SubLen length is the packet data length, and the DataType is the data type. If the current packet is the last packet, the SubFlag flag is set to "tail packet," the SubLen length is the last packet's data length, and the DataType is the data type. For example, if the data length is 5000 bytes and the header is 8 bytes, it can be divided into two packets: the first packet is (8+4088), and the second packet is (8+912). The SubFlag of the first packet is set to "not the tail packet," and the SubFlag of the second packet is set to "tail packet." During the packet segmentation process, the segmented packets are sent to the server in sequence.

[0065] Step S2.2: Upon receiving data from the client, the server network transmission module assembles packets based on the header information. Step S2.2 includes determining the type of the SubFlag flag in the current data header. If it is a single packet, it indicates that the current data is not segmented, and the current data is directly sent to the destination network gateway module. If it is not the tail packet, it indicates that the current data is segmented and is an intermediate packet. The server receives the segmented data, assembles it into a packet, and sends the data type and the assembled packet data to the destination network gateway module. If it is the tail packet, it indicates that the current data is segmented and is the last packet. The server receives the data packet, assembles it into a packet, and sends the data type and the assembled packet data to the destination network gateway module.

[0066] Step S3: After receiving the data, the destination network gateway module parses the data according to the different data types of transmission, and sends a byte back to the source end through the server-side network transmission module according to the parsing result.

[0067] Step S4: The server-side network transmission module only supports sending one byte to the client. After receiving a one-byte response from the destination network gateway module, the server sends the response to the client.

[0068] Step S5: After receiving a byte response from the server, the client network transmission module determines whether the byte is a valid response. If it is, the byte is sent to the source-end cross-network gateway module for parsing, and then step S6 is executed. If not, it indicates that the source-end cross-network gateway module has failed to receive data. The module then determines whether the current byte response is the response from the first sending point table. If it is, the process returns to step S2. If not, it indicates that the data collection has failed to be sent. The module then reconnects to the server based on the network status and returns to step S3 to continue sending data.

[0069] Step S6: The source-end cross-network gateway module determines whether the current byte response is the response of the first sending point table. If yes, proceed to step S7; otherwise, continue monitoring for new data collection.

[0070] Step S7: Determine if the parsing was successful. If so, start two threads: the first thread and the second thread. The first thread is the monitoring point table thread, used to monitor whether there are any changes in the point table. The second thread is the monitoring data collection thread, used to monitor the collected data. If not, return to step S2.

[0071] When the first thread detects a change in the point table, it sets the data type to DATA_TAG_SYNC for point table synchronization and sends the point table data to the destination. When the second thread detects new collected data, it sets the data type to DATA_SNAPSHOTS for collected data and sends the collected data to the destination.

[0072] This invention aims to achieve cross-network gateway data transmission between the source and destination ends by establishing a one-to-one connection between the client and server. The client network transmission module at the source end uses packet segmentation technology to ensure stable transmission of large amounts of data, effectively improving sending efficiency. The server network transmission module at the destination end guarantees a one-to-one connection with the client and restricts the transmission to only one byte at a time, satisfying cross-network gateway security policies.

[0073] Example 2

[0074] The present invention also provides a real-time database cross-network gateway transmission system. Those skilled in the art can implement the real-time database cross-network gateway transmission system by executing the steps of the real-time database cross-network gateway transmission method. That is, the real-time database cross-network gateway transmission method can be understood as a preferred embodiment of the real-time database cross-network gateway transmission system.

[0075] A real-time database cross-network gateway transmission system provided by the present invention includes:

[0076] Module M1: Establishes a one-to-one connection between the client and server, enabling communication. The client includes a source-end cross-network gateway module and a client network transmission module. The server includes a server network transmission module and a destination-end cross-network gateway module. Module M1 includes: Module M1.1: During startup, the source-end cross-network gateway module initiates a connection to the server through the client network transmission module. Module M1.2: Upon receiving a connection request from the source-end cross-network gateway module, the client network transmission module initiates a connection request to the server network transmission module. Module M1.3: Upon receiving the connection request information from the client, the server network transmission module ensures a one-to-one connection between the client and server.

[0077] Module M2: After confirming a successful connection, the source-end cross-network gateway module obtains the point table data from its local end, processes it through the client network transmission module, and then sends the point table data to the destination-end cross-network gateway module. Module M2 sets the data type to DATA_TAG_SYNC point table synchronization. Module M2 includes: Module M2.1: After receiving data from the source-end cross-network gateway module, the client network transmission module packets the data and sends it to the server network transmission module. Module M2.2: Upon receiving data from the client, the server network transmission module reassembles the data according to the header information and sends it to the destination-end cross-network gateway module. During packet segmentation, the segmented packets are sent to the server in sequence. Each data packet header consists of three fields: SubFlag, SubLen, and DataType. SubFlag indicates the packet type, SubLen indicates the data length, and DataType indicates the data type. Packet types include single packets, tail packets, and non-tail packets; data types include transmission data type and data type.

[0078] Module M2.1 includes: Module M2.1.1: Determines whether the sum of the data length and header length is less than 4069 bytes. If so, no packet splitting is needed; the data and corresponding header information are directly sent to the server, and the current packet type is set to single packet. If not, packet splitting is required, triggering module M2.1.2. Module M2.1.2: Performs packet splitting according to length. Except for the last packet, each packet is 4096 bytes long, and each packet includes sub-data bytes and header bytes. Module M2.1.3: Determines whether the current packet is the last packet. If so, sets the SubFlag flag to the tail packet, SubLen to the data length of the last packet, and DataType to the data type. If not, sets the SubFlag flag to non-tail packet, SubLen to the sub-packet data length, and DataType to the transmission data type.

[0079] Module M2.2 includes: determining the type of the SubFlag flag in the current data header; if it is a single packet, it indicates that the current data is not segmented, and the current data is directly sent to the destination network gateway module. If it is not the tail packet, it indicates that the current data is segmented and is an intermediate packet; the module receives the segmented data, assembles it into a packet, and sends the data of the transmission type and the assembled packet to the destination network gateway module. If it is the tail packet, it indicates that the current data is segmented and is the last packet; the module receives the data packet, assembles it into a packet, and sends the data of the transmission type and the assembled packet to the destination network gateway module.

[0080] Module M3: After receiving the data, the destination network gateway module parses the data according to the different data types of transmission, and sends a byte back to the client network transmission module through the server-side network transmission module based on the parsing result.

[0081] Module M4: After receiving the byte response, the client network transmission module will determine whether the byte response is valid. If it is, the current byte response will be sent to the source-end cross-network gateway module for parsing, triggering module M5. If not, it indicates that the source-end cross-network gateway module failed to receive data, and then module M6 will be triggered.

[0082] Module M5: Determines if the current byte response is a response from the first sent point table. If yes, it triggers module M7. If not, it continues monitoring for new collected data.

[0083] Module M6: Determines if the current byte response is a response from the initial transmission point table. If yes, it triggers module M2. If no, it indicates that the current data transmission failed, and the system reconnects to the server based on the network status, triggering module M3 to continue sending data.

[0084] Module M7: Determines if the response was successful. If successful, it starts two threads: Thread 1 and Thread 2. If unsuccessful, it triggers module M2. Thread 1 is a monitoring point table thread used to monitor for changes in the point table. Thread 2 is a monitoring data acquisition thread used to monitor the acquired data. When Thread 1 detects a change in the point table, it sets the data type to DATA_TAG_SYNC for point table synchronization and sends the point table data to the server. When Thread 2 detects new acquired data, it sets the data type to DATA_SNAPSHOTS for acquired data and sends the acquired data to the server.

[0085] Those skilled in the art will understand that, besides implementing the system and its various devices, modules, and units provided by this invention in the form of purely computer-readable program code, the same functions can be achieved entirely through logical programming of the method steps, making the system and its various devices, modules, and units of this invention function in the form of logic gates, switches, application-specific integrated circuits, programmable logic controllers, and embedded microcontrollers. Therefore, the system and its various devices, modules, and units provided by this invention can be considered as a hardware component, and the devices, modules, and units included therein for implementing various functions can also be considered as structures within the hardware component; alternatively, the devices, modules, and units for implementing various functions can be considered as both software modules implementing the method and structures within the hardware component.

[0086] Specific embodiments of the present invention have been described above. It should be understood that the present invention is not limited to the specific embodiments described above, and those skilled in the art can make various changes or modifications within the scope of the claims, which do not affect the essence of the present invention. Unless otherwise specified, the embodiments and features described in this application can be arbitrarily combined with each other.

Claims

1. A method for real-time database cross-network gateway transmission, characterized in that, include: Step S1: Connect the client and server one-to-one to establish communication. The client includes a source-end cross-network gateway module and a client network transmission module. The server includes a server network transmission module and a destination-end cross-network gateway module. Step S2: After confirming a successful connection, the source-end cross-network gateway module obtains the point table data from its local end, processes it through the client network transmission module, and then sends the point table data to the destination-end cross-network gateway module. Step S3: After receiving the data, the destination network gateway module parses the data according to the different data types of transmission, and sends a byte back to the client network transmission module through the server-side network transmission module according to the parsing result; Step S4: After receiving the byte response, the client network transmission module will determine whether the byte response is valid. If it is, the current byte response will be sent to the source-end cross-network gateway module for parsing and then step S5 will be executed. If not, it means that the source-end cross-network gateway module failed to receive data and then step S6 will be executed. Step S5: Determine whether the current byte response is the response of the first sent point table. If yes, proceed to step S7; otherwise, continue monitoring for new collected data. Step S6: Determine whether the current byte response is the response of the first sent point table. If yes, return to step S2; otherwise, it means that the data collection failed to be sent. Reconnect to the server according to the network status and return to step S3 to continue sending data. Step S7: Determine if the response was successful. If yes, start two threads, namely the first thread and the second thread; otherwise, return to step S2.

2. The real-time database cross-network gateway transmission method according to claim 1, characterized in that, Step S1 includes: Step S1.1: During the startup process, the source-end cross-network gateway module will initiate a connection to the server through the client network transmission module; Step S1.2: After receiving the connection request from the source network gateway module, the client network transmission module initiates a connection request to the server network transmission module; Step S1.3: After receiving the connection request information sent by the client, the server network transmission module ensures a one-to-one connection between the client and the server.

3. The real-time database cross-network gateway transmission method according to claim 1, characterized in that, In step S2, the data type is set to DATA_TAG_SYNC for point table synchronization.

4. The real-time database cross-network gateway transmission method according to claim 1, characterized in that, Step S2 includes: Step S2.1: After receiving the data from the source-end cross-network gateway module, the client network transmission module sends the data packets to the server network transmission module; Step S2.2: After receiving the data sent by the client, the server network transmission module will assemble the data according to the header information and send it to the destination network gateway module. During the packet splitting process, the already split packets are sent to the server in sequence.

5. The real-time database cross-network gateway transmission method according to claim 4, characterized in that, Each data packet header consists of three fields: SubFlag, SubLen, and DataType. SubFlag indicates the packet type, SubLen indicates the data length, and DataType indicates the data type. Packet types include single packets, tail packets, and non-tail packets; data types include transmission data types and data types.

6. The real-time database cross-network gateway transmission method according to claim 5, characterized in that, Step S2.1 includes: Step S2.1.1: Determine whether the sum of the length of the data and the header length is less than 4069 bytes. If so, no packet splitting is required. Send the data and the corresponding header information directly to the server and set the current packet type to single packet. If not, packet splitting is required. Proceed to step S2.1.

2. Step S2.1.2: Process the packets according to their length. Except for the last packet, each packet is 4096 bytes long. The bytes in each packet include the data bytes and the header bytes. Step S2.1.3: Determine whether the current packet is the last packet. If yes, set the SubFlag flag to the last packet, SubLen to the data length of the last packet, and DataType to the data type. If no, set the SubFlag flag to the non-last packet, SubLen to the length of the packet data, and DataType to the data type of the transmission.

7. The real-time database cross-network gateway transmission method according to claim 5, characterized in that, Step S2.2 includes: determining the type of the SubFlag flag in the current data header; if it is a single packet, it means that the current data is not packetized, and the current data is directly sent to the destination network gateway module. If it is not the tail packet, it means that the current data is a sub-packet and an intermediate packet. The sub-packet data is received, reassembled into a packet, and the data type of the transmission and the data of the assembled packet are sent to the destination network gateway module. If it is the last packet, it means that the current data is a packet and it is the last packet. The received data packet is reassembled, and the data type of the transmitted packet and the assembled packet data are sent to the destination network gateway module.

8. The real-time database cross-network gateway transmission method according to claim 1, characterized in that, The first thread is the point table monitoring thread, used to monitor whether there are any changes in the point table; The second thread is a data collection monitoring thread used to monitor the collected data.

9. The real-time database cross-network gateway transmission method according to claim 8, characterized in that, When the first thread detects a change in the point table, it sets the data type to DATA_TAG_SYNC for point table synchronization and sends the point table data to the server. When the second thread detects new collected data, it sets the data type to DATA_SNAPSHOTS and sends the collected data to the server.

10. A real-time database cross-network gateway transmission system, characterized in that, include: Module M1: Connects the client and server one-to-one to establish communication. The client includes a source-end cross-network gateway module and a client network transmission module. The server includes a server network transmission module and a destination-end cross-network gateway module. Module M2: After confirming a successful connection, the source-end cross-network gateway module obtains the point table data from its local end, processes it through the client network transmission module, and then sends the point table data to the destination-end cross-network gateway module. Module M3: After receiving the data, the destination network gateway module parses the data according to the different data types being transmitted, and sends a byte back to the client network transmission module through the server-side network transmission module based on the parsing result; Module M4: After receiving the byte response, the client network transmission module will determine whether the byte response is valid. If it is, the byte will be sent to the source-end cross-network gateway module for parsing and then trigger module M5; if not, it means that the source-end cross-network gateway module failed to receive data and then triggers module M6. Module M5: Determines whether the current byte response is the response to the first sent point table. If yes, it triggers module M7; otherwise, it continues to monitor for new collected data. Module M6: Determines whether the current byte response is the response from the first sent point table. If yes, it triggers module M2; otherwise, it indicates that the data collection failed to be sent. Based on the network status, it reconnects to the server and triggers module M3 to continue sending data. Module M7: Determines whether the parsing was successful. If so, it starts two threads, namely the first thread and the second thread; otherwise, it triggers module M2.

Images