CN107911415A - Multiplex system and its method, the storage medium and terminal of TCP flow - Google Patents

Abstract

The present invention discloses multiplex system and its method, the storage medium and terminal of TCP flow.The method includes the steps：APP, equipment are established to TCP long connections with intermediate server respectively；After APP and equipment receive the handshake request of opposite end, check local terminal parameter and send it to opposite end, and after receiving the response of shaking hands of opposite end, select a parameter set supported jointly to complete handshake procedure；Make the HTTP server address of APP requests opposite end binding；After the HTTP server Address requests that equipment receives APP transmissions, the IP ports of oneself binding are returned to；APP is received the IP ports of equipment end return, bind a local address；APP is set to initiate HTTP request toward address；The TCP mux of APP is received HTTP request, and request data is subjected to burst, encapsulation, be then sent to intermediate server；Intermediate server is set to forward the data to equipment；The demux of equipment is set to receive HTTP request from intermediate server, and by data recombination, decapsulation, then it is sent to HTTP Server.Multiple transmission demand stagings can be interleaved alternately with TCP channel by the present invention in transmitting terminal, in these requests of receiving terminal restructuring reduction.

Description

Multiplexing system of TCP stream and its method, storage medium and terminal

technical field

The present invention relates to a multiplexing system of TCP streams and its method, storage medium and terminal, in particular to a multiplexing system of TCP streams, a multiplexing method of TCP streams, and a computer applying the method A readable storage medium and a computer terminal applying the method.

Background technique

With the rise of private cloud technology, more and more devices located in the intranet need to provide service interfaces based on public network addresses, so that users can access them anytime and anywhere. However, limited by factors such as NAT and firewalls, the devices in the intranet cannot be directly accessed by the outside. By introducing an intermediate server located in the public network, both intranet devices and users transmit information through the intermediate server. In order to save server resources, usually only one TCP channel is maintained between the device and the user and the server. When there is data transmission, the TCP channel is used serially. For small data volumes such as control messages, it can meet the usage requirements, but when transferring large files, the channel will be occupied for a long time, resulting in no opportunity for other data to be transmitted, which obviously cannot meet the requirements of high concurrency and low latency.

Contents of the invention

In order to solve the problem of inefficient serial transmission, the present invention provides a multiplexing system for TCP streams, a multiplexing method for TCP streams, a computer-readable storage medium applying the method, and a computer applying the method The terminal, the system introduces a concurrent transmission method, inserting multiple transmission request segments alternately into the TCP channel at the sending end, and recombining and restoring these requests at the receiving end.

The present invention is realized by the following technical solutions: a multiplexing system of TCP streams, the network framework of the system includes APP, equipment, and an intermediate server as a communication bridge between the APP and the equipment; wherein,

The App establishes a long TCP connection with the intermediate server, and sends a handshake request to the opposite end to negotiate parameter information;

The device establishes a TCP long connection with the intermediate server, and sends a handshake request to the opposite end to negotiate parameter information;

After the App and the device receive the handshake request from the opposite end, check the local parameters and send them to the opposite end;

After the App and the device receive the handshake response from the opposite end, check the parameters of the local end, and select a commonly supported parameter set to complete the handshake process;

The App requests the HTTP server address bound to the peer;

After the device receives the HTTP server address request sent by the App, it returns the IP port bound to itself;

The App receives the IP port returned by the device and binds a local address;

The App initiates an HTTP request to the address of the link URL corresponding to the local address;

The TCP mux of the App receives the HTTP request, fragments and encapsulates the request data, and then sends it to the intermediate server;

the intermediate server forwards data to the device;

The demux of the device receives the HTTP request from the intermediate server, reassembles and decapsulates the data, and then sends the data to the HTTP Server.

As a further improvement of the above solution, the App integrates a TCP multiplexer and demultiplexer, and maintains a long connection with the intermediate server through TCP.

As a further improvement of the above solution, the App actively initiates an HTTP request to acquire information of the device or pull a file from the device.

As a further improvement of the above solution, the device integrates a TCP multiplexer and demultiplexer, and maintains a long connection with the intermediate server through TCP.

As a further improvement of the above solution, the device provides an HTTP Server for use by the App.

As a further improvement of the above solution, the intermediate server respectively establishes a TCP connection with the App and the device, and transparently transmits the data sent by the App and the device to the opposite end.

The present invention also provides a method for multiplexing TCP streams, the method is applied in a multiplexing system for TCP streams, and the network framework of the multiplexing system for TCP streams includes APP, equipment, and As an intermediate server of the communication bridge between the APP and the device; the multiplexing method of the TCP flow comprises the following steps:

Establish a TCP long connection between the APP and the intermediate server, and send a handshake request to the peer to negotiate parameter information;

Establish a TCP long connection between the device and the intermediate server, and send a handshake request to the opposite end to negotiate parameter information;

After the App and the device receive the handshake request from the opposite end, check the local parameters and send them to the opposite end;

After the App and the device receive the handshake response from the opposite end, check the parameters of the local end, and select a commonly supported parameter set to complete the handshake process;

make the App request the HTTP server address bound to the peer;

After the device receives the HTTP server address request sent by the App, it returns the IP port bound to itself;

Make the App receive the IP port returned by the device and bind a local address;

Make the App initiate an HTTP request to the address of the link URL corresponding to the local address;

The TCP mux of the App is made to receive the HTTP request, and the request data is fragmented and encapsulated, and then sent to the intermediate server;

causing the intermediate server to forward data to the device;

Make the demux of the device receive the HTTP request from the intermediate server, reassemble and decapsulate the data, and then send the data to the HTTP Server.

As a further improvement of the above scheme, the multiplexing system of the TCP stream is the multiplexing system of any of the above TCP streams, and the TCP mux receives the request from the HTTP Client, and then multiplexes it into a single TCP channel, and the After the data is sent to the intermediate server, the TCP demux receives the data from the intermediate server, demultiplexes it, and then sends it to the HTTP Server.

The present invention also provides a computer-readable storage medium, on which a computer program is stored, and when the program is executed by a processor, the following steps are implemented:

Establish a TCP long connection between the APP and the intermediate server, and send a handshake request to the peer to negotiate parameter information;

Establish a TCP long connection between the device and the intermediate server, and send a handshake request to the opposite end to negotiate parameter information;

After the App and the device receive the handshake request from the opposite end, check the local parameters and send them to the opposite end;

After the App and the device receive the handshake response from the opposite end, check the parameters of the local end, and select a commonly supported parameter set to complete the handshake process;

make the App request the HTTP server address bound to the peer;

After the device receives the HTTP server address request sent by the App, it returns the IP port bound to itself;

Make the App receive the IP port returned by the device and bind a local address;

Make the App initiate an HTTP request to the address of the link URL corresponding to the local address;

The TCP mux of the App is made to receive the HTTP request, and the request data is fragmented and encapsulated, and then sent to the intermediate server;

causing the intermediate server to forward data to the device;

Make the demux of the device receive the HTTP request from the intermediate server, reassemble and decapsulate the data, and then send the data to the HTTP Server.

The present invention also provides a computer terminal, which includes a memory, a processor, and a computer program stored on the memory and operable on the processor; when the processor executes the program, the following steps are implemented:

Establish a TCP long connection between the App and the intermediate server, and send a handshake request to the peer to negotiate parameter information;

Establish a TCP long connection between the device and the intermediate server, and send a handshake request to the opposite end to negotiate parameter information;

After the App and the device receive the handshake request from the opposite end, check the local parameters and send them to the opposite end;

After the App and the device receive the handshake response from the opposite end, check the parameters of the local end, and select a commonly supported parameter set to complete the handshake process;

make the App request the HTTP server address bound to the peer;

After the device receives the HTTP server address request sent by the App, it returns the IP port bound to itself;

Make the App receive the IP port returned by the device, and bind a local address;

Make the App initiate an HTTP request to the address of the link URL corresponding to the local address;

The TCP mux of the App is made to receive the HTTP request, and the request data is fragmented and encapsulated, and then sent to the intermediate server;

causing the intermediate server to forward data to the device;

Make the demux of the device receive the HTTP request from the intermediate server, reassemble and decapsulate the data, and then send the data to the HTTP Server.

The invention can solve the problem of inefficient serial transmission. By introducing a concurrent transmission method, a plurality of transmission request segments are alternately inserted into the TCP channel at the sending end, and the requests are reassembled and restored at the receiving end.

Description of drawings

FIG. 1 is a network architecture diagram of a TCP stream multiplexing system according to Embodiment 1 of the present invention.

FIG. 2 is a functional framework diagram inside the multiplexing system of the TCP stream in FIG. 1 .

Detailed ways

In order to make the object, technical solution and advantages of the present invention clearer, the present invention will be further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described here are only used to explain the present invention, not to limit the present invention.

Example 1

As shown in FIG. 1 , the network framework of the multiplexing system of TCP streams of the present invention includes APP, equipment and an intermediate server as a communication bridge between APP and equipment. TCP is the abbreviation of Transmission Control Protocol, and Chinese is Transmission Control Protocol.

Please combine with Figure 2, the app integrates TCP multiplexer and demultiplexer, and maintains a long connection with the intermediate server through TCP. The app actively initiates an HTTP request to obtain device information or pull files from the device.

The device integrates a TCP multiplexer and demultiplexer, and maintains a long connection with the intermediate server through TCP. The device provides HTTP Server for App to use.

The intermediate server establishes a TCP connection with the App and the device respectively, and transparently transmits the data sent by the App and the device to the opposite end.

TCP mux is equivalent to TCP Server, which receives requests from HTTP Clients, then multiplexes them into a single TCP channel, and sends the data to the intermediate server. The TCP demux receives data from the intermediate server, demultiplexes it, and sends it to the HTTP Server. Wherein, mux is multiplexing, HTTP Client=HyperText Transfer ProtocolClient, means hypertext transfer protocol, demux means demultiplexer, HTTP Server means web server, TCP mux is equivalent to TCP Server (server),

The multiplexing system for TCP streams uses the following steps when running the process.

S201, the App establishes a TCP persistent connection with the intermediate server, and sends a handshake request to the peer end to negotiate parameter information.

S202, the device establishes a TCP persistent connection with the intermediate server, and sends a handshake request to the peer end to negotiate parameter information.

S203. After receiving the handshake request from the opposite end, the App and the device check the local parameters and send them to the opposite end.

S204. After receiving the handshake response from the opposite end, the App and the device check the parameters of the local end, and select a commonly supported parameter set to complete the handshake process.

S205, the App requests the HTTP server address bound to the peer.

S206. After receiving the HTTP server address request sent by the App, the device returns the IP port (IP, Port) bound to itself.

S207, the App receives the (IP, Port) returned by the device, and binds a local address, such as the local address: 127.0.0.1:port2.

S208, the APP initiates an HTTP request to the address of the link URL corresponding to the local address, for example, initiates an HTTP request to the address of http://127.0.0.1:port2.

S209, the TCP mux of the App receives the HTTP request, fragments and encapsulates the request data, and then sends it to the intermediate server.

S210, the intermediate server forwards the data to the device.

S211. The demux of the device receives the HTTP request from the intermediate server, reassembles and decapsulates the data, and then sends the data to the HTTP Server.

Example 2

Embodiment 2 provides a method for multiplexing TCP streams, and the method is applied to a multiplexing system for TCP streams, such as the multiplexing system for TCP streams described in Embodiment 1.

The multiplexing method of described TCP stream comprises the following steps:

Establish a TCP long connection between the APP and the intermediate server, and send a handshake request to the peer to negotiate parameter information;

Establish a TCP long connection between the device and the intermediate server, and send a handshake request to the opposite end to negotiate parameter information;

After the App and the device receive the handshake request from the opposite end, check the local parameters and send them to the opposite end;

After the App and the device receive the handshake response from the opposite end, check the parameters of the local end, and select a commonly supported parameter set to complete the handshake process;

make the App request the HTTP server address bound to the peer;

After the device receives the HTTP server address request sent by the App, it returns the IP port bound to itself;

Make the App receive the IP port returned by the device and bind a local address;

Make the App initiate an HTTP request to the address of the link URL corresponding to the local address;

The TCP mux of the App is made to receive the HTTP request, and the request data is fragmented and encapsulated, and then sent to the intermediate server;

causing the intermediate server to forward data to the device;

Make the demux of the device receive the HTTP request from the intermediate server, reassemble and decapsulate the data, and then send the data to the HTTP Server.

Example 3

Embodiment 3 provides a computer-readable storage medium on which a computer program is stored, and when the program is executed by a processor, the following steps are implemented.

Establish a TCP long connection between the APP and the intermediate server, and send a handshake request to the peer to negotiate parameter information;

Establish a TCP long connection between the device and the intermediate server, and send a handshake request to the opposite end to negotiate parameter information;

After the App and the device receive the handshake request from the opposite end, check the local parameters and send them to the opposite end;

After the App and the device receive the handshake response from the opposite end, check the parameters of the local end, and select a commonly supported parameter set to complete the handshake process;

make the App request the HTTP server address bound to the peer;

After the device receives the HTTP server address request sent by the App, it returns the IP port bound to itself;

Make the App receive the IP port returned by the device and bind a local address;

Make the App initiate an HTTP request to the address of the link URL corresponding to the local address;

The TCP mux of the App is made to receive the HTTP request, and the request data is fragmented and encapsulated, and then sent to the intermediate server;

causing the intermediate server to forward data to the device;

Make the demux of the device receive the HTTP request from the intermediate server, reassemble and decapsulate the data, and then send the data to the HTTP Server.

Example 4

Embodiment 4 provides a computer terminal, which includes a memory, a processor, and a computer program stored in the memory and operable on the processor.

When the processor executes the program, the following steps are implemented:

Establish a TCP long connection between the App and the intermediate server, and send a handshake request to the peer to negotiate parameter information;

Establish a TCP long connection between the device and the intermediate server, and send a handshake request to the opposite end to negotiate parameter information;

After the App and the device receive the handshake request from the opposite end, check the local parameters and send them to the opposite end;

After the App and the device receive the handshake response from the opposite end, check the parameters of the local end, and select a commonly supported parameter set to complete the handshake process;

make the App request the HTTP server address bound to the peer;

After the device receives the HTTP server address request sent by the App, it returns the IP port bound to itself;

Make the App receive the IP port returned by the device, and bind a local address;

Make the App initiate an HTTP request to the address of the link URL corresponding to the local address;

The TCP mux of the App is made to receive the HTTP request, and the request data is fragmented and encapsulated, and then sent to the intermediate server;

causing the intermediate server to forward data to the device;

Make the demux of the device receive the HTTP request from the intermediate server, reassemble and decapsulate the data, and then send the data to the HTTP Server.

The above descriptions are only preferred embodiments of the present invention, and are not intended to limit the present invention. Any modifications, equivalent replacements and improvements made within the spirit and principles of the present invention should be included in the protection of the present invention. within range.

Claims (10)

1. a multiplexing system of TCP flow, the network framework of described system comprises APP, equipment and the intermediate server as the communication bridge between described APP and described equipment; It is characterized in that: The App establishes a long TCP connection with the intermediate server, and sends a handshake request to the opposite end to negotiate parameter information; The device establishes a TCP long connection with the intermediate server, and sends a handshake request to the opposite end to negotiate parameter information; After the App and the device receive the handshake request from the opposite end, check the local parameters and send them to the opposite end; After the App and the device receive the handshake response from the opposite end, check the parameters of the local end, and select a commonly supported parameter set to complete the handshake process; The App requests the HTTP server address bound to the peer; After the device receives the HTTP server address request sent by the App, it returns the IP port bound to itself; The App receives the IP port returned by the device and binds a local address; The App initiates an HTTP request to the address of the link URL corresponding to the local address; The TCP mux of the App receives the HTTP request, fragments and encapsulates the request data, and then sends it to the intermediate server; the intermediate server forwards data to the device; The demux of the device receives the HTTP request from the intermediate server, reassembles and decapsulates the data, and then sends the data to the HTTP Server. 2. The multiplexing system of TCP streams as claimed in claim 1, characterized in that: the App integrates a TCP multiplexing and demultiplexing device, and maintains a long connection with the intermediate server through TCP. 3. The multiplexing system of TCP streams according to claim 1, wherein the App actively initiates an HTTP request to acquire information of the device or pull files from the device. 4. The multiplexing system of TCP streams as claimed in claim 1, characterized in that: the device integrates a TCP multiplexing and demultiplexing device, and maintains a long connection with the intermediate server through TCP. 5. The multiplexing system of TCP streams according to claim 1, characterized in that: said device provides HTTP Server for use by said App. 6. The multiplexing system of TCP streams as claimed in claim 1, characterized in that: the intermediate server establishes TCP connections with the App and the device respectively, and sends the App and the device The data is transparently transmitted to the peer. 7. A multiplexing method of a TCP flow, said method is applied in a multiplexing system of a TCP flow, and the network framework of the multiplexing system of said TCP flow includes APP, equipment, and as all An intermediate server of the communication bridge between the APP and the device; it is characterized in that: the multiplexing method of the TCP flow comprises the following steps: Establish a TCP long connection between the APP and the intermediate server, and send a handshake request to the peer to negotiate parameter information; Establish a TCP long connection between the device and the intermediate server, and send a handshake request to the opposite end to negotiate parameter information; After the App and the device receive the handshake request from the opposite end, check the local parameters and send them to the opposite end; After the App and the device receive the handshake response from the opposite end, check the parameters of the local end, and select a commonly supported parameter set to complete the handshake process; make the App request the HTTP server address bound to the peer; After the device receives the HTTP server address request sent by the App, it returns the IP port bound to itself; Make the App receive the IP port returned by the device and bind a local address; Make the App initiate an HTTP request to the address of the link URL corresponding to the local address; The TCP mux of the App is made to receive the HTTP request, and the request data is fragmented and encapsulated, and then sent to the intermediate server; causing the intermediate server to forward data to the device; Make the demux of the device receive the HTTP request from the intermediate server, reassemble and decapsulate the data, and then send the data to the HTTP Server. 8. the multiplexing method of TCP flow as claimed in claim 7 is characterized in that: the multiplexing system of described TCP flow is the multiplexing of TCP flow as described in any one in claim 1 to 6. Multiplexing system, TCP mux receives requests from HTTPClient, then multiplexes them to a single TCP channel, sends the data to the intermediate server, TCP demux receives data from the intermediate server, demultiplexes it, and then sends to the HTTP Server. 9. A computer-readable storage medium, on which a computer program is stored, characterized in that: when the program is executed by a processor, the following steps are implemented: Establish a TCP long connection between the APP and the intermediate server, and send a handshake request to the peer to negotiate parameter information; Establish a TCP long connection between the device and the intermediate server, and send a handshake request to the opposite end to negotiate parameter information; After the App and the device receive the handshake request from the opposite end, check the local parameters and send them to the opposite end; After the App and the device receive the handshake response from the opposite end, check the parameters of the local end, and select a commonly supported parameter set to complete the handshake process; make the App request the HTTP server address bound to the peer; After the device receives the HTTP server address request sent by the App, it returns the IP port bound to itself; Make the App receive the IP port returned by the device and bind a local address; Make the App initiate an HTTP request to the address of the link URL corresponding to the local address; The TCP mux of the App is made to receive the HTTP request, and the request data is fragmented and encapsulated, and then sent to the intermediate server; causing the intermediate server to forward data to the device; Make the demux of the device receive the HTTP request from the intermediate server, reassemble and decapsulate the data, and then send the data to the HTTP Server. 10. A computer terminal, comprising a memory, a processor, and a computer program stored on the memory and operable on the processor; it is characterized in that: the processor implements the following steps when executing the program: Establish a TCP long connection between the App and the intermediate server, and send a handshake request to the peer to negotiate parameter information; Establish a TCP long connection between the device and the intermediate server, and send a handshake request to the opposite end to negotiate parameter information; After the App and the device receive the handshake request from the opposite end, check the local parameters and send them to the opposite end; After the App and the device receive the handshake response from the opposite end, check the parameters of the local end, and select a commonly supported parameter set to complete the handshake process; make the App request the HTTP server address bound to the peer; After the device receives the HTTP server address request sent by the App, it returns the IP port bound to itself; Make the App receive the IP port returned by the device, and bind a local address; Make the App initiate an HTTP request to the address of the link URL corresponding to the local address; The TCP mux of the App is made to receive the HTTP request, and the request data is fragmented and encapsulated, and then sent to the intermediate server; causing the intermediate server to forward data to the device; Make the demux of the device receive the HTTP request from the intermediate server, reassemble and decapsulate the data, and then send the data to the HTTP Server.