WO2017185368A1

WO2017185368A1 - Signalling transmission method and device

Info

Publication number: WO2017185368A1
Application number: PCT/CN2016/080802
Authority: WO
Inventors: 胡星星; 张宏卓; 邓天乐; 庞伶俐
Original assignee: 华为技术有限公司
Priority date: 2016-04-29
Filing date: 2016-04-29
Publication date: 2017-11-02
Also published as: CN108886705A

Abstract

A signalling transmission method and device, which are used for solving the problem of waste of air interface resources caused by the fact that in a TCP packet used in the existing TCP connection establishment and release process some pieces of information in a TCP header may also occupy a byte with the corresponding length even if it is empty. The method comprises: a first device interacts information related to transmission control protocol (TCP) connection establishment or release between the first device and a second device with a network device via first wireless air interface signalling, the first wireless air interface signalling that it does not contain a TCP/IP header structure; the first device establishing a TCP connection with the second device according to information related to TCP connection establishment between the first device and the second device; alternatively, the first device releasing a TCP connection with the second device according to information related to TCP connection release between the first device and the second device. Since first wireless air interface signalling does not contain a TCP/IP header structure, the load of air interface transmission is reduced.

Description

Signal transmission method and device

Technical field

The present invention relates to the field of communications technologies, and in particular, to a signaling transmission method and device.

Background technique

With the development of communication technology, more and more terminals need to access the wireless network, communication is no longer limited to communication between people, Machine Type Communication (MTC) technology realizes the machine and Machine to Machine has also become increasingly popular. In the current fifth-generation mobile communication network requirements, the connection density of low-power, low-cost and large-coverage MTC terminals (ie, terminals in MTC communication) reaches 200,000/km ² , and the amount of data of each MTC terminal communicates each time. Less, some MTC terminals have longer communication intervals.

Some MTC terminals still use the Transmission Control Protocol (TCP)/Internet Protocol (IP) in the MTC communication. This requires establishing a TCP connection before transmitting data. After the data is transmitted, the release is established. TCP connection. During the TCP connection establishment process, the initiating end uses the TCP packet to perform the three-way handshake process between the network side and the destination end to complete the establishment of the TCP connection with the destination end. The structure of the TCP packet is as shown in Figure 1, including the IPv4 header and TCP. The header and data, TCP and IPv4 headers occupy a total of 40 bytes. The TCP message used in the TCP connection establishment and release process contains a TCP header. The process of establishing a TCP connection is as shown in Figure 2. The initiator obtains the IP address of the destination end through interaction with the Domain Name System (DNS). Then, the initiator sends a three-way handshake process through the network side. The network side is responsible for transparently transmitting the TCP packet sent by the initiator to the destination end. details as follows:

First, the initiating end sends the segment 1 to the destination end through the network side, where the segment 1 carries the port of the destination end, and the initial number ISN of the originating end of the TCP, and the SYN=1, ACK=0 in the segment. The sequence number is set to seq=i, and seq=i is the selected TCP initial sequence number (ie, ISN). According to TCP, a segment with SYN=1 cannot carry data, but consumes a sequence number.

Then, the destination end returns a segment 2 containing the TCP initial sequence number of the destination end through the network side as a response. The acknowledgement sequence number in the segment 2 is set to 1 for the ISN of the initiator, SYN=1 for the segment 2, ACK=1, the sequence number ack=i+1 is confirmed, and the data sequence number is set to seq=j, seq= j is to select the TCP initial sequence number seq=j, and a SYN will occupy a sequence number.

Finally, the initiator returns the segment 3 as a confirmation through the network side. The acknowledgement sequence number in the segment 3 is set to the ISN of the destination end plus 1, ACK=1, the confirmation sequence number ack=j+1, and the data sequence number is set to seq=i+1.

During the TCP connection release process, the initiator uses the TCP packet to perform the four-way handshake process between the network side and the destination end, thereby completing the release of the TCP connection with the destination end, as shown in FIG. 3, where the network side is responsible for sending the originating end. The TCP packet is transparently transmitted to the destination. The specific process is as follows:

First, the initiator sends the segment 4 to the destination through the network side, stops the data transmission with the destination, and actively closes the TCP connection. In the segment 4, FIN=1, the data sequence number is seq=u, and the data sequence number is the sequence number of the last byte of the transmitted data plus one.

Then, the destination end returns the segment 5 through the network side, the ACK=1 in the segment 5, the confirmation sequence number is ack=u+1, the data sequence number is seq=v, and the data sequence number is the last of the transmitted data. The sequence number of one byte is incremented by 1.

Then, if the destination has no data to be sent to the initiator, the segment 6 is sent to the initiator through the network side, and the FIN=1 in the segment 6 confirms the sequence number ack=u+1, and the data sequence seq =w.

Finally, after receiving the segment 6, the initiator returns the segment 7 through the network side, and the ACK=1 in the segment 7 confirms the sequence number ack=w+1, and the data sequence seq=u+1.

It can be seen from the above that in the TCP packets used in the TCP connection establishment and release process, even if some information in the TCP header is empty, the bytes of the corresponding length are occupied, thereby causing waste of air interface resources.

Summary of the invention

The embodiment of the present invention provides a signaling transmission method and device, which are used to solve the TCP packet used in the establishment and release process of the existing TCP connection, and even if some information is empty in the TCP header, The byte of the corresponding length is occupied, which causes a waste of air interface resources.

In a first aspect, a signaling transmission method includes:

The first device exchanges, by using the first wireless air interface signaling, information related to the establishment or release of the TCP connection of the first device and the second device with the network device, where the first wireless air interface signaling does not include TCP/ IP header structure;

The first device establishes a TCP connection with the second device according to related information established by the TCP connection of the first device and the second device; or the first device is configured according to the first device and the second device The TCP connection releases relevant information, releasing the TCP connection with the second device.

In a possible implementation manner, the related information about the TCP connection established by the first device and the second device includes: indication information indicating that the network device is proxying the TCP connection between the first device and the second device; or

The related information about the TCP connection release of the first device and the second device includes: indication information for instructing the network device to proxy TCP release of the first device and the second device.

In a possible implementation manner, the related information about the TCP connection established by the first device and the second device includes: a TCP initial sequence number of the first device, or a TCP initial sequence number of the second device.

In a possible implementation manner, the related information about the TCP connection established by the first device and the second device further includes: an IP address of the first device, an IP address of the second device, and the first At least one of a TCP port number of the device and a TCP port number of the second device.

In a possible implementation manner, the first wireless air interface signaling is radio resource control RRC signaling, non-access stratum NAS signaling, or MAC layer signaling that is defined in a standard or a protocol.

In a possible implementation manner, the method includes:

The first device establishes a response by interacting with the network device by using the second wireless air interface signaling, where the second wireless air interface signaling does not include a TCP/IP header structure; or

The first device exchanges a TCP connection with the network device by using the third wireless air interface signaling, and the third wireless air interface signaling does not include a TCP/IP header structure.

In a possible implementation manner, the second wireless air interface signaling further includes: the first device The initial TCP serial number or the TCP initial serial number of the second device.

In a possible implementation, the second wireless air interface signaling further includes: an IP address of the first device, an IP address of the second device, and a TCP port number and location of the first device. At least one piece of information of a TCP port number of the second device.

In a possible implementation manner, the second wireless air interface signaling is RRC signaling, NAS signaling, or MAC layer signaling that is defined in a standard or a protocol;

The third wireless air interface signaling is RRC signaling, NAS signaling, or MAC layer signaling defined in a standard or protocol.

In a second aspect, a signaling transmission method includes:

The network device interacts with the first device by using the first wireless air interface signaling to establish or release information related to the TCP connection of the first device and the second device, where the first wireless air interface signaling does not include TCP/ IP header structure;

The network device initiates TCP of the first device and the second device to the first device or the second device according to related information established by the TCP connection of the first device and the second device Establishing the connection; or the network device initiating the first device and the second device according to the related information released by the TCP connection of the first device and the second device to the first device or the second device The TCP connection is released.

In a possible implementation manner, after the network device interacts with the first device by using the first wireless air interface signaling, the method further includes: after the first device interacts with the information about the TCP connection established or released by the first device and the second device, the method further includes: :

The network device reconstructs a TCP/IP header according to related information established by the TCP connection of the first device and the second device, and sends the second device to request the second device to establish and a first TCP connection establishment signaling of a TCP connection of the first device, where the first TCP connection establishment signaling includes a reconstructed TCP/IP header;

or

The network device initiates, according to the information about the release of the TCP connection of the first device and the second device, the TCP connection release of the first device and the second device to the second device, The network device reconfigures a TCP/IP header according to related information released by the TCP connection of the first device and the second device, and sends the second device to request the second device to release the device. The first TCP connection release signaling of the TCP connection of the first device, where the first TCP connection release signaling includes a reconstructed TCP/IP header.

In a possible implementation manner, before the network device interacts with the first device by using the first wireless air interface signaling, the method further includes: before the first device interacts with the information about the TCP connection established or released by the first device and the second device, the method further includes: :

Receiving, by the network device, the second TCP connection establishment signaling sent by the second device, where the second TCP connection establishment signaling includes information about establishing a TCP connection between the first device and the second device, where The second TCP connection setup signaling includes a TCP/IP header structure; or

Receiving, by the network device, the second TCP connection release signaling sent by the second device, where the second TCP connection release signaling includes information about the release of the TCP connection of the first device and the second device, where The second TCP connection release signaling includes a TCP/IP header structure.

In a possible implementation manner, the method further includes:

The network device establishes a response by interacting with the first device by using a second wireless air interface signaling; or

The network device releases a response by interacting with the first device by using a third wireless air interface signaling.

The related information of the TCP connection establishment or release of the first device and the second device in the second aspect, the first wireless air interface signaling, the second wireless air interface signaling, and the third wireless air interface signaling For details, refer to the description of related embodiments in the first aspect, and details are not described herein again.

In a third aspect, a terminal device includes:

An information interaction module, configured to exchange, by using the first wireless air interface signaling, information related to the establishment or release of the TCP connection of the first device and the second device with the network device, where the first wireless air interface signaling is not Contains the TCP/IP header structure;

a processing module, configured to establish a TCP connection with the second device according to related information established by the TCP connection of the first device and the second device; or according to the first device and the second device The related information released by the TCP connection releases the TCP connection with the second device.

In a possible implementation manner, the information interaction module is further configured to:

Establishing, by the second wireless air interface signaling, a TCP connection establishment response with the network device, where the second wireless air interface signaling does not include a TCP/IP header structure; or

And transmitting, by the third wireless air interface signaling, a TCP connection release response with the network device, where the third wireless air interface signaling does not include a TCP/IP header structure.

The related information of the TCP connection establishment or release of the first device and the second device in the third aspect, the first wireless air interface signaling, the second wireless air interface signaling, and the third wireless air interface signaling For details, refer to the description of related embodiments in the first aspect, and details are not described herein again.

In a fourth aspect, a terminal device includes: a transceiver, and at least one processor coupled to the transceiver, wherein:

A processor for reading a program in the memory, performing the following process:

Controlling, by the first wireless air interface signaling, the transceiver, by using the first wireless air interface signaling, to exchange information related to the establishment or release of the transmission control protocol TCP connection between the first device and the second device, where the first wireless air interface signaling does not include TCP/IP header structure;

Establishing a TCP connection with the second device according to the related information established by the TCP connection of the first device and the second device; or releasing the related information according to the TCP connection released by the first device and the second device a TCP connection of the second device;

A transceiver for receiving and transmitting data under the control of a processor.

In a possible implementation, the processor reads the program in the memory and also performs the following process:

Controlling, by the second wireless air interface signaling, the transceiver to establish a response with the network device to exchange a TCP connection, where the second wireless air interface signaling does not include a TCP/IP header structure; or

And controlling, by the third wireless air interface signaling, the transceiver to perform a TCP connection release response with the network device, where the third wireless air interface signaling does not include a TCP/IP header structure.

The related information of the TCP connection establishment or release of the first device and the second device in the fourth aspect, the first wireless air interface signaling, the second wireless air interface signaling, and the third wireless air interface signaling For details, refer to the description of related embodiments in the first aspect, and details are not described herein again.

In a fifth aspect, a network device includes:

An interaction module, configured to exchange, by using the first wireless air interface signaling, information related to the establishment or release of the TCP connection of the first device and the second device by the first device, where the first wireless air interface signaling is not Contains the TCP/IP header structure;

a management module, configured to initiate, according to the related information established by the TCP connection of the first device and the second device, the first device and the second device to the first device or the second device Establishing a TCP connection; or initiating a TCP connection between the first device and the second device to the first device or the second device according to related information released by the TCP connection of the first device and the second device freed.

In a possible implementation manner, the interaction module is further configured to:

Reconstructing a TCP/IP header according to related information established by the TCP connection of the first device and the second device, and sending, to the second device, a request for the second device to establish the first device The first TCP connection establishment signaling of the TCP connection, where the first TCP connection establishment signaling includes a reconstructed TCP/IP header;

or

Reconstructing a TCP/IP header according to related information released by the TCP connection of the first device and the second device, and sending, to the second device, a request for the second device to release the TCP with the first device The connected first TCP connection releases signaling, and the first TCP connection release signaling includes a reconstructed TCP/IP header.

In a possible implementation, the interaction module is configured to: before the first device interacts with the first device to establish or release the related information about the TCP connection of the first device and the second device, by using the first wireless air interface signaling,

Receiving, by the second device, the second TCP connection establishment signaling, where the second TCP connection establishment signaling includes information about establishing a TCP connection between the first device and the second device, where the second TCP is The connection establishment signaling includes a TCP/IP header structure; or

Receiving, by the second device, the second TCP connection release signaling, where the second TCP connection release signaling includes information about the release of the TCP connection of the first device and the second device, where The second TCP connection release signaling includes a TCP/IP header structure.

Establishing a response by interacting with the first device by using the second wireless air interface signaling; or

The TCP connection release response is exchanged with the first device by the third wireless air interface signaling.

The related information of the TCP connection establishment or release of the first device and the second device in the fifth aspect, the first wireless air interface signaling, the second wireless air interface signaling, and the third wireless air interface signaling For details, refer to the description of related embodiments in the first aspect, and details are not described herein again.

In a seventh aspect, a network device includes: a transceiver, and at least one processor coupled to the transceiver, wherein:

Controlling, by the first wireless air interface signaling, the transceiver, by using the first wireless air interface signaling, to exchange information related to the establishment or release of the transmission control protocol TCP connection between the first device and the second device by the first device, where the first wireless air interface signaling is not Contains the TCP/IP header structure;

Establishing, by the first device or the second device, a TCP connection establishment of the first device and the second device according to the related information about the TCP connection established by the first device and the second device; or Deleting a TCP connection release of the first device and the second device to the first device or the second device according to the information about the TCP connection release of the first device and the second device;

In a possible implementation manner, the processor reads a program in the memory, and further executes:

Reconstructing a TCP/IP header according to related information established by the TCP connection of the first device and the second device, and controlling the transceiver to send the second device to request the second device to establish a first TCP connection establishment signaling of the TCP connection of the first device, where the first TCP connection establishment signaling includes a reconstructed TCP/IP header;

or

Reconstructing a TCP/IP header according to related information released by the TCP connection of the first device and the second device, and controlling the transceiver to send the second device to request release of the second device The first TCP connection of the TCP connection of the first device releases signaling, and the first TCP connection release signaling includes a reconstructed TCP/IP header.

In a possible implementation manner, the transceiver performs, by using the first wireless air interface signaling, before the first device interacts with the information about the establishment or release of the TCP connection between the first device and the second device,

Receiving, by the second device, the second TCP connection release signaling, where the second TCP connection release signaling includes information about the release of the TCP connection of the first device and the second device, the second TCP The connection release signaling includes a TCP/IP header structure.

Controlling, by the second wireless air interface signaling, the transceiver to establish a response by interacting with the first device by using a TCP connection; or

And controlling the transceiver to release a response by interacting with the first device by using a third wireless air interface signaling.

The related information of the TCP connection establishment or release of the first device and the second device in the sixth aspect, the first wireless air interface signaling, the second wireless air interface signaling, and the third wireless air interface signaling For details, refer to the description of related embodiments in the first aspect, and details are not described herein again.

In the method and device provided by the embodiment of the present invention, the first device and the network device exchange the related information about the establishment or release of the TCP connection between the first device and the second device by using the first wireless air interface signaling, The first wireless air interface signaling does not include a TCP/IP header structure, and the first wireless air interface signaling carries the related information released by the TCP connection of the first device and the second device, thereby reducing the load of the air interface transmission. .

DRAWINGS

FIG. 1 is a schematic structural diagram of a TCP packet;

2 is a schematic diagram of an existing TCP connection establishment process;

3 is a schematic diagram of a conventional TCP connection release process;

4 is a schematic diagram of a possible network architecture according to an embodiment of the present invention;

FIG. 5 is a schematic flowchart of a signaling transmission method according to Embodiment 1 of the present invention;

FIG. 6 is a schematic flowchart of a signaling transmission method according to Embodiment 2 of the present invention;

FIG. 7 is a schematic flowchart of a signaling transmission method according to Embodiment 3 of the present invention;

FIG. 8 is a schematic flowchart of a signaling transmission method according to Embodiment 4 of the present invention;

FIG. 9 is a schematic flowchart of a signaling transmission method according to Embodiment 5 of the present invention;

FIG. 10 is a schematic flowchart of a signaling transmission method according to Embodiment 6 of the present invention;

FIG. 11 is a schematic flowchart diagram of a signaling transmission method according to Embodiment 7 of the present invention;

FIG. 12 is a schematic flowchart of a signaling transmission method according to Embodiment 8 of the present invention;

FIG. 13 is a schematic flowchart of a signaling transmission method according to Embodiment 9 of the present invention;

FIG. 14 is a schematic diagram of a terminal device according to Embodiment 10 of the present invention; FIG.

FIG. 15 is a schematic diagram of a terminal device according to Embodiment 11 of the present invention; FIG.

FIG. 16 is a schematic diagram of a network device according to Embodiment 12 of the present invention; FIG.

FIG. 17 is a schematic diagram of a network device according to Embodiment 13 of the present invention.

detailed description

The technical solutions in the embodiments of the present invention will be clearly and completely described in conjunction with the drawings in the embodiments of the present invention. It is a partial embodiment of the invention, and not all of the embodiments. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without creative efforts are within the scope of the present invention.

The embodiments of the present invention are further described in detail below with reference to the accompanying drawings. It is to be understood that the embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.

The technical solution described in the present invention can be applied to various communication systems, such as current 2G, 3G communication systems and next generation communication systems, such as Global System for Mobile Communications (GSM, Global System for Mobile communications), Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Wideband Code Division Multiple Access (WCDMA), multiple frequency divisions FDMA (Frequency Division Multiple Addressing) system, Orthogonal Frequency-Division Multiple Access (OFDMA) system, single carrier FDMA (SC-FDMA) system, general packet radio service (GPRS, General Packet Radio Service) Systems, Long Term Evolution (LTE) systems, and other such communication systems.

FIG. 4 is a schematic diagram of a possible network architecture according to an embodiment of the present invention. The base station (eNB) in FIG. 4 is a network device, and the user equipment (UE) is a first device, and the network device and the first device communicate with each other through air interface technology. In the embodiment of the present invention, the first device and the network device transmit the related information about the establishment or release of the TCP connection between the first device and the second device by using the first wireless interface signaling, so that the network device proxy initiates the first A TCP connection between the device and the second device is established or released. Since the first wireless air interface signaling does not include a TCP/IP header structure, the load of the air interface transmission is reduced.

The first device in the embodiment of the present invention is a wireless terminal, and the second device may be a wireless terminal, or may be a wired terminal or a wired device (such as a server). The wireless terminal can be a device that provides voice and/or data connectivity to the user, a handheld device with wireless connectivity, or other processing device that is connected to the wireless modem. The wireless terminal can communicate with one or more core networks via a radio access network (eg, RAN, Radio Access Network), which can be a mobile terminal, such as a mobile phone (or "cellular" phone) and with a mobile terminal The computers, for example, can be portable, pocket-sized, handheld, computer-integrated or in-vehicle mobile devices that exchange language and/or data with the wireless access network. For example, personal communication service (PCS, Personal Communication Service) telephone, cordless telephone, Session Initiation Protocol (SIP) telephone, Wireless Local Loop (WLL) station, Personal Digital Assistant (PDA, Personal Digital Assistant), etc. .

The network device in the embodiment of the present invention may refer to an access network that passes through one or A device in which multiple sectors communicate with a wireless terminal. For example, the network device may be a base station (BTS, Base Transceiver Station) in GSM or CDMA, or may be a base station (NodeB) in WCDMA, or may be an evolved base station in LTE (NodeB or eNB or e-NodeB, evolutional) Node B) is not limited in the present invention.

In the first embodiment of the present invention, a signaling transmission method is provided, as shown in FIG. 5, including:

S51: The first device exchanges, by using the first wireless air interface signaling, information related to the establishment or release of the TCP connection between the first device and the second device, and the first wireless air interface signaling does not include the TCP/IP. Header structure.

In this step, if the first device actively initiates the establishment or release of the TCP connection with the second device, the first device sends the TCP connection between the first device and the second device to the network device by using the first wireless air interface signaling. Establishing or releasing related information; if the first device passively establishes or releases a TCP connection with the second device, the network device establishes or releases the TCP connection between the first device and the second device that is sent by the second device After the related information, the related information of the TCP connection establishment or release of the first device and the second device is sent to the first device by using the first wireless air interface signaling.

S52. The first device establishes a TCP connection with the second device according to related information established by the TCP connection of the first device and the second device, or the first device is configured according to the first device and the first device. The information about the release of the TCP connection of the two devices releases the TCP connection with the second device.

S53. The network device initiates, according to the information about the TCP connection established by the first device and the second device, the TCP of the first device and the second device to the first device or the second device. Establishing the connection; or the network device initiating the first device and the second device according to the related information released by the TCP connection of the first device and the second device to the first device or the second device The TCP connection is released.

Specifically, if the first device actively initiates the establishment of the TCP connection, the network device acquires related information about the TCP connection establishment of the first device and the second device from the first device, and initiates the information to the second device. The TCP connection of the first device and the second device is established; if the second device actively initiates the establishment of the TCP connection, the network device acquires the TCP of the first device and the second device from the second device Correlating the established related information, and initiating the first setting to the first device A TCP connection with the second device is established. If the first device actively initiates the release of the TCP connection, the network device acquires related information about the release of the TCP connection between the first device and the second device from the first device, and initiates the information to the second device. The TCP connection of the device and the second device is released; if the second device actively initiates the release of the TCP connection, the network device acquires the TCP connection of the first device and the second device from the second device. Related information, and initiating a TCP connection release of the first device and the second device to the first device.

In the embodiment of the present invention, the first device and the network device exchange the related information about the establishment or release of the TCP connection between the first device and the second device by using the first wireless air interface signaling, because the first wireless air interface message The command does not include the TCP/IP header structure, and the first wireless air interface signaling carries the related information released by the TCP connection of the first device and the second device, thereby reducing the load of the air interface transmission.

In this embodiment, the execution order of S51 and S52 is not limited. Specifically, S51 may be executed first, and then S52 may be executed; S52 may be executed first, and then S51 may be executed; and S51 and S52 may be simultaneously executed.

In a possible implementation manner, the first device may be a user equipment, and the second device may be a server.

In the second embodiment of the present invention, a method for signaling transmission in a process of establishing a TCP connection with a second device by a first device is provided. The process is as shown in FIG. 6 and includes the following steps:

S61. The first device establishes a TCP connection with the second device.

S62. The first device sends, by using the first wireless air interface signaling, related information about establishing a TCP connection between the first device and the second device to the network device.

Specifically, the first device indicates, by using the first wireless air interface signaling, that the network device is configured to establish a TCP connection between the first device and the second device, where the first wireless air interface signaling does not include a TCP/IP header structure.

In a specific implementation, in a possible implementation manner, the first wireless air interface signaling is a Radio Resource Control (RRC) signaling defined in a standard or a protocol, and a non-access layer (Non Access Stratum) , referred to as NAS) signaling, or Media Access Control (MAC) signaling.

Specifically, the first device carries related information about the TCP connection established by the first device and the second device by extending the wireless air interface signaling defined in the standard or the protocol. By extending the standard air interface signaling in the standard or protocol, the idle resources in the existing signaling can be better utilized, thereby reducing the air interface signaling load and further reducing the load of the air interface transmission.

In another possible implementation manner, the first wireless air interface signaling is newly defined signaling.

Specifically, the first device carries the TCP connection establishment between the first device and the second device by using newly defined signaling, such as IP proxy request signaling and MAC control element signaling. Related information.

In a specific implementation, in a possible implementation manner, the related information about the TCP connection established by the first device and the second device includes: an indication for instructing the network device to proxy a TCP connection between the first device and the second device information.

Further, optionally, the related information about the TCP connection established by the first device and the second device further includes: a TCP initial sequence number of the first device.

Further, the related information about the TCP connection established by the first device and the second device further includes: an IP address of the first device and an IP address of the second device, and a TCP of the first device At least one of a port number and a TCP port number of the second device.

In a specific implementation, the related information about the TCP connection established by the first device and the second device includes: a TCP initial sequence number of the first device.

In this step, in order not to affect the TCP/IP layer of the first device, the wireless air interface protocol layer of the first device, such as Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) a layer, an RRC layer, a MAC layer, a physical layer, etc., when receiving a TCP packet (also referred to as a TCP packet) sent by the TCP/IP layer of the first device for initiating a TCP connection establishment or release, from the TCP packet Acquiring information about establishing or releasing a TCP connection between the first device and the second device in the TCP/IP header of the text, by using the first wireless air interface signaling, Sending, to the network device, related information about establishing or releasing a TCP connection of the first device and the second device, where the first wireless air interface signaling does not include a TCP/IP header.

S63. The network device reconfigures a TCP/IP header according to related information established by the TCP connection of the first device and the second device, and sends the first TCP connection establishment signaling to the second device. a segment 1), instructing the second device to establish a TCP connection with the first device, that is, step 1 in the TCP establishment three-way handshake process, where the first TCP connection establishment signaling includes a reconstructed TCP /IP header, TCP establishes a three-way handshake process. The main purpose of step 1 is to notify the peer to initiate TCP establishment.

Since the second device is generally a server, and the wired connection is generally between the network device and the server, the network device needs to reconstruct the TCP/IP header and send it to the second device.

The information required to reconstruct the TCP/IP header, such as the initial TCP sequence number of the first device, may further include: an IP address of the first device and an IP address of the second device, and the The TCP port number of the device and the TCP port number of the second device may be directly obtained from the first wireless air interface signaling, or may be obtained by other means, in the communication with the first device as described above, The first device notifies the network device of the information required for establishing the TCP connection of the first device and the second device, where the network device saves information required for establishing a TCP connection between the first device and the second device . The embodiment of the present invention does not limit the manner in which the network device acquires information required for establishing a TCP connection between the first device and the second device.

S64. The network device receives a TCP connection setup response returned by the second device.

Specifically, after completing the TCP connection with the first device, the second device returns a TCP connection establishment response (ie, segment 2) to the network device, that is, TCP establishes step 2 in the three-way handshake, and the TCP establishes three times. The main purpose of step 2 in the handshake process is as a response to step 1.

S65. The network device returns a TCP connection establishment response to the first device by using the second wireless air interface signaling, to notify the first device that the second device has completed establishing a TCP connection, and the second wireless air interface The TCP/IP header structure is not included in the signaling.

Optionally, the second wireless air interface signaling includes a TCP initial sequence number of the second device.

Further, the second wireless air interface signaling further includes an IP address of the first device and the At least one of an IP address of the second device, and a TCP port number of the first device and a TCP port number of the second device.

Correspondingly, after receiving the TCP connection establishment response, the first device determines that the second device has established a TCP connection with the first device.

Optionally, in order not to affect the TCP/IP layer of the first device, after the wireless air interface protocol layer of the first device receives the TCP connection establishment response by using the second wireless air interface signaling, the wireless air interface protocol layer of the first device According to the information carried in the second wireless air interface signaling, the TCP packet (including the TCP/IP header) corresponding to the step 2 in the three-way handshake process is reconstructed, that is, the segment 2 is sent, and the TCP packet is sent. Give the TCP/IP layer of the first device.

Optional, after S65, also includes:

S66. The first device returns an acknowledgement message to the network device by using the fourth wireless air interface signaling to indicate that the TCP connection establishment response is correctly received, and the fourth wireless air interface signaling does not include the TCP/IP header. structure.

Optionally, in order not to affect the TCP/IP layer of the first device, the TCP/IP layer of the first device receives the TCP packet corresponding to the step 2 in the TCP establishment three-way handshake process delivered by the wireless air interface protocol layer of the first device. After the TCP is generated, the TCP packet corresponding to the step 3 in the three-way handshake process is generated, that is, the packet 3 is sent, and the TCP packet is sent to the wireless air interface protocol layer of the first device; the wireless air interface protocol layer of the first device is generated. And returning, by the fourth wireless air interface signaling, an acknowledgement message to the network device according to the received TCP packet.

S67. The network device reconstructs a TCP/IP header, and sends a message carrying the reconstructed TCP/IP header to the second device, that is, TCP establishes step 3 in the three-way handshake, and TCP establishes a three-way handshake step 3 Is a confirmation of step 2 to indicate that the TCP connection setup response has been received correctly.

It should be noted that, in this embodiment, the execution order of S61 is not limited, and S61 may also be performed after S62 and before S63, or may be performed after S66.

In the third embodiment of the present invention, another method for signaling transmission in the process of establishing a TCP connection with a second device by the first device is provided. In this embodiment, the first device and the network device extend the existing RRC. Signaling, interacting with the establishment of a TCP connection between the first device and the second device Information, other situations are similar to this embodiment, and will not be exemplified herein. The flow of this embodiment is shown in FIG. 7 and includes the following steps:

S701. The UE sends an RRC Connection Request message to the eNB.

S702. The eNB sends an RRC Connection Setup message to the UE.

S703. The UE sends an RRC Connection Setup Complete message to the eNB.

S704. The eNB sends a Security Mode Command message to the UE.

S705. The UE sends a Security Mode Complete message to the eNB, where the Security Mode Complete message carries the information of the first step (step 1) in the three-way handshake process.

For example, an IPAgentReuest item is added to the IE (Information Element) of the Security Mode Complete message, and the IPAgentQuest includes the information of the step 1 in the TCP establishment handshake process, including: the initial TCP sequence number of the first device, and The IP address of the first device and the IP address of the second device, and the TCP port number of the first device and the TCP port number of the second device may be included.

S706, the eNB initiates a TCP establishment three-way handshake process to the peer (Peer entity), such as a server;

Specifically, the eNB establishes the information of step 1 in the three-way handshake process according to the TCP carried in the Security Mode Complete message, reconstructs the TCP/IP header, and sends a message including the reconstructed TCP/IP header to the peer end, the TCPTCP/IP The header includes the information of step 1 in TCP establishing the three-way handshake process.

S707, the peer end initiates a TCP establishment three-way handshake process to the eNB, step 2;

S708. The eNB sends an RRC Connection Reconfiguration (RRC Connection Reconfiguration) message to the UE, where the RRC connection reconfiguration message carries the information of the step 2 in the three-way handshake process.

For example, an IPAgent entry is added to the IE field in the RRC Connection reconfiguration message, where the IPAgent includes the information of the step 2, specifically including the TCP of the second device. The initial sequence number may further include an IP address of the first device and an IP address of the second device, and a TCP port number of the first device and a TCP port number of the second device.

S709. The UE passes the RRC Connection Reconfiguration Complete (RRC Connection Reconfiguration Complete) message, indicating that the information of step 2 in the TCP establishment three-way handshake process has been correctly received.

Optionally, in order to not affect the TCP/IP layer of the UE, after receiving the RRC Connection Reconfiguration message, the wireless air interface protocol layer of the UE reconstructs the TCP corresponding to the step 2 in the three-way handshake process established by the TCP according to the information carried in the message. a packet (including a TCP/IP header), and sending the TCP packet to the TCP/IP layer of the UE;

Correspondingly, after receiving the TCP packet sent by the wireless air interface protocol layer of the UE, the TCP/IP layer of the UE generates a TCP packet corresponding to the step 2 in the three-way handshake process, and sends the TCP packet to the wireless air interface protocol layer of the UE.

Correspondingly, after receiving the TCP packet sent by the TCP/IP layer of the UE, the wireless air interface protocol layer of the UE indicates that the information of step 2 in the three-way handshake process of the TCP establishment has been correctly received through the RRC Connection Reconfiguration Complete message.

For example, the RRC Connection Reconfiguration Complete message may not carry additional information. If the eNB receives the RRC Connection Reconfiguration Complete message, it determines that the UE has correctly received the information of step 2 in the TCP establishment three-way handshake process. Certainly, the RRC Connection Reconfiguration Complete message may also carry an indication IE, indicating that the information of step 2 in the TCP establishment three-way handshake process has been correctly received.

S710. The eNB returns a TCP to the peer end to establish a three-way handshake process in step 3;

Specifically, the eNB reconstructs the TCP/IP header and returns a message including the reconstructed TCP/IP header to the peer end, that is, initiating TCP to the peer to establish step 3 in the three-way handshake process.

S711. The UE initiates uplink information transmission (UL Information Transfer) to the eNB.

In the fourth embodiment of the present invention, a method for signaling transmission in a process of establishing a TCP connection with a first device by a second device is provided. The process is as shown in FIG. 8 and includes the following steps:

S81. The second device establishes a TCP connection with the first device.

S82. The second device sends, by using a TCP packet, the related information about the TCP connection established by the first device and the second device to the network device, that is, initiates a TCP establishment three-step handshake process.

S83. The network device sends, by using the first wireless air interface signaling, related information about establishing a TCP connection between the first device and the second device to the first device.

For details, refer to the related description in the embodiment shown in FIG. 6 for the first wireless air interface signaling, and details are not described herein again.

Further, optionally, the related information about the TCP connection established by the first device and the second device further includes: a TCP initial sequence number of the second device.

In a specific implementation, the related information about the TCP connection established by the first device and the second device includes: a TCP initial sequence number of the second device.

S84. The first device establishes a TCP connection with the second device.

Specifically, the first device establishes a TCP connection with the second device after receiving the related information about the TCP connection established by the first device and the second device that is sent by the network device by using the first wireless air interface signaling. .

Optionally, after S84, it also includes:

S85. The first device returns a TCP connection establishment response to the network device by using the second wireless air interface signaling, to indicate that the TCP connection establishment of the first device and the second device is completed, and the second The TCP/IP header structure is not included in the wireless air interface signaling.

Optionally, the second wireless air interface signaling includes a TCP initial sequence number of the first device.

Further optionally, the second wireless air interface signaling further includes: an IP address of the first device and an IP address of the second device, and a TCP port number of the first device and the second At least one of the TCP port numbers of the device.

Optionally, in order to not affect the TCP/IP layer of the UE, after receiving the first wireless air interface signaling, the wireless air interface protocol layer of the UE reconstructs the step 1 of the TCP establishment three-way handshake process according to the information carried in the signaling. Corresponding TCP packet (including the TCP/IP header), and sending the TCP packet to the TCP/IP layer of the UE;

Correspondingly, after receiving the TCP packet sent by the TCP/IP layer of the UE, the wireless air interface protocol layer of the UE indicates that the information of step 1 in the three-way handshake process is correctly received by the TCP through the second wireless air interface signaling.

S86. The network device reconstructs a TCP/IP header, and sends a message carrying the reconstructed TCP/IP header to the second device, that is, TCP establishes step 2 in the three-way handshake to indicate that the first A TCP connection is established between the device and the second device.

Optional, after S86, also includes:

S87. The second device returns an acknowledgement message to the network device by using a TCP packet, that is, the TCP establishes step 3 in the three-way handshake to indicate that the TCP connection setup response has been correctly received.

S88. The network device returns an acknowledgement message to the first device by using the fourth wireless air interface signaling, to indicate that the TCP connection establishment response is correctly received, and the fourth wireless air interface signaling does not include the TCP/IP header. structure.

Optionally, in order to not affect the TCP/IP layer of the first device, after receiving the fourth wireless air interface signaling sent by the network device, the wireless air interface protocol layer of the first device needs to reconstruct the TCP/IP header and include The TCP packet of the TCP/IP header is sent to the TCP/IP layer of the first device.

In the fifth embodiment of the present invention, another method for actively initiating the first device by the second device is provided. The signaling transmission method in the process of establishing a TCP connection. In this embodiment, the first device and the network device exchange existing RRC signaling, and exchange related information established by the TCP connection between the first device and the second device. Other situations are similar to this embodiment, and are not illustrated here. The flow of this embodiment is shown in FIG. 9 and includes the following steps:

S901, the peer end (such as a server) initiates a TCP establishment three-way handshake process to the eNB, step 1;

S902. The eNB sends a paging message to the UE.

S903. The UE sends an RRC Connection Request message to the eNB.

S904. The eNB sends an RRC Connection Setup message to the UE.

S905. The UE sends an RRC Connection Setup Complete message to the eNB.

S906. The eNB sends a Security Mode Command message to the UE, where the Security Mode Command message carries the information of step 1 in the three-way handshake process.

For example, an IPAgentRequest item is added to the IE (Information Element) of the Security Mode Command message, where the IPAgentRequest includes the information of the step 1 in the TCP establishment handshake process, including: the initial TCP sequence number of the second device, and The IP address of the first device and the IP address of the second device, and the TCP port number of the first device and the TCP port number of the second device may be included.

S907. The UE sends a Security Mode Complete message to the eNB, where the Security Mode Complete message carries the information of step 2 in the three-way handshake process.

In this embodiment, optionally, in order not to affect the TCP/IP layer of the UE, after receiving the Security Mode Command message sent by the eNB, the wireless air interface protocol layer of the UE reconstructs the TCP corresponding to the step 1 in the three-way handshake process. The message (including the TCP/IP header) is sent to the TCP/IP layer of the UE.

After receiving the TCP packet corresponding to step 2 in the three-way handshake process of the TCP/IP layer sent by the UE, the wireless air interface protocol layer of the UE sends a TCP to establish a three-way handshake process in step 2 by using a Security Mode Complete message. information.

S908, the eNB initiates a TCP establishment of a three-way handshake process to the peer (Peer entity), such as a server;

Specifically, the eNB establishes the information of step 2 in the three-way handshake process according to the TCP carried in the Security Mode Complete message, reconstructs the TCP/IP header, and sends a message including the reconstructed TCP/IP header to the peer end, the TCPTCP/IP The header includes information that TCP establishes step 2 in the three-way handshake process.

S909. The peer initiates a TCP establishment to the eNB to establish step 3 in the three-way handshake process.

S910. The eNB sends an RRC Connection Reconfiguration message to the UE, where the RRC connection reconfiguration message carries the information of step 3 in the three-way handshake process.

For example, an IPAgent entry is added to the IE field in the RRC Connection reconfiguration message, where the IPAgent includes the information of the step 3, and specifically includes the indication information for instructing the second device to correctly receive the step 2 of the TCP establishment three-way handshake process; The method may include: an IP address of the first device and an IP address of the second device, and a TCP port number of the first device and a TCP port number of the second device.

S911. The UE sends an RRC Connection Reconfiguration Complete message to the eNB.

Optionally, in order to not affect the TCP/IP layer of the UE, after receiving the RRC Connection Reconfiguration message sent by the eNB, the wireless air interface protocol layer of the UE reconstructs the TCP packet corresponding to step 3 in the three-way handshake process (including TCP). /IP header), and send the TCP packet to the TCP/IP layer of the UE.

S912. The UE initiates UL Information Transfer to the eNB.

In the sixth embodiment of the present invention, a signaling transmission method in a process of actively initiating a TCP connection release with a second device by a first device is provided. The process is as shown in FIG. 10, and includes the following steps:

S101. The first device sends, by using the first wireless air interface signaling, related information released by the TCP connection of the first device and the second device to the network device.

Specifically, the first device indicates, by using the first wireless air interface signaling, that the network device is configured to release the TCP connection of the first device and the second device, and the first wireless air interface signaling does not include a TCP/IP header structure.

In a possible implementation manner, the first device carries related information about the release of the TCP connection between the first device and the second device by extending the wireless air interface signaling defined in the standard or the protocol. For example, by extending the existing RRC signaling, the NAS signaling or the MAC signaling carries the related information released by the TCP connection of the first device and the second device.

By extending the standard air interface signaling in the standard or protocol, the idle resources in the existing signaling can be better utilized, thereby reducing the air interface signaling load and further reducing the load of the air interface transmission.

In another possible implementation manner, the first device carries the first device and the first device by using newly defined signaling, such as IP proxy request signaling, and MAC control element signaling. Information about the release of the TCP connection of the second device.

Optionally, the related information about the TCP connection release of the first device and the second device includes: indication information used to indicate that the network device is proxying the TCP release of the first device and the second device.

Optionally, in order not to affect the TCP/IP layer of the first device, the wireless air interface protocol layer of the first device corresponds to step 1 in the TCP release four-way handshake process sent by the TCP/IP layer of the first device. After the TCP packet is received, the information in the TCP packet is obtained and sent to the network device by using the first wireless air interface signaling.

S102. The first device releases a TCP connection established with the second device.

S103. The network device reconfigures a TCP/IP header according to related information released by the TCP connection of the first device and the second device.

Since the second device is generally a server, and the wired connection is generally between the network device and the server, the network device needs to reconstruct the TCP/IP according to the related information released by the TCP connection between the first device and the second device. The header is sent to the second device.

S104. The network device sends the first TCP connection release signaling (ie, segment 4) to the second device, to indicate that the second device releases the established TCP connection with the first device. That is, the TCP releases the step 1 in the four-way handshake process, where the first TCP connection release signaling includes the reconstructed TCP/IP header; the TCP release four-way handshake process is mainly used to notify the second device of the first step. The device initiates a release of the TCP connection.

S105. The network device returns a TCP connection release response to the first device by using the third wireless air interface signaling, to notify the second device that the TCP connection release is completed, and the third wireless space is The TCP/IP header structure is not included in the port signaling.

Optionally, in order to not affect the TCP/IP layer of the first device, after receiving the third wireless air interface signaling sent by the network device, the wireless air interface protocol layer of the first device needs to reconfigure the TCP release four-step handshake process. 2 and / or step 3 corresponding TCP message (including TCP / IP header), and send the TCP message to the TCP / IP layer of the first device. Step 2 is a response to step 1 in the TCP release four-way handshake process, and the corresponding TCP packet is segment 5; in the TCP release four-way handshake process, step 3 is used to notify the first device that the second device initiates the release. For a TCP connection, the corresponding TCP packet is segment 6.

It should be noted that, in this embodiment, the execution order of S102 is not limited, S102 may be performed before S101, and S102 may also be executed after S105.

The process of releasing the TCP connection between the first device and the second device initiated by the network device to the second device includes:

The network device initiates a TCP release four-way handshake process to the second device, and initiates a TCP release process.

The second device initiates a TCP release four-way handshake process step 2, that is, a response to step 1 to the network device, indicating that the second device has received step 1;

The second device initiates a TCP release four-way handshake process step 3 to the network device, that is, notifying the first device that the second device initiates releasing the TCP connection;

The network device initiates a TCP release four-way handshake process step 4 to the second device, that is, an acknowledgement to step 3, indicating that the network device has received step 3.

In the seventh embodiment of the present invention, a signaling transmission method in a process of the second device actively initiating a TCP connection release with the first device is provided. The process is as shown in FIG. 11 and includes the following steps:

S111, the network device receives the second TCP connection release signaling sent by the second device, that is, the TCP release four-way handshake process step 1, the second TCP connection release signaling includes the first device and the first Information about the release of the TCP connection of the second device, where the second TCP connection release signaling includes a TCP/IP header structure;

S112. The network device sends the first device to the first device by using the first wireless air interface signaling. Information about the release of the TCP connection with the second device.

For details of the first wireless air interface signaling, refer to the related description in the embodiment shown in FIG. 10, and details are not described herein again.

Optionally, the network device may reconfigure the TCP/IP packet corresponding to step 2 in the TCP release four-way handshake process, and send the packet to the second device.

S113. The first device releases a TCP connection established with the second device.

Optionally, in order to not affect the TCP/IP layer of the first device, after receiving the first wireless air interface signaling sent by the network device, the wireless air interface protocol layer of the first device needs to reconstruct the TCP release four-step handshake process. 1 corresponding TCP message (including TCP/IP header), and the TCP message is sent to the TCP/IP layer of the first device.

Optionally, after S113, it also includes:

S114. The first device returns a TCP connection release response to the network device by using the third wireless air interface signaling, to indicate that the first device has completed the TCP connection release, and the third wireless air interface signaling does not include TCP/IP header structure.

Optionally, in order not to affect the TCP/IP layer of the first device, the wireless air interface protocol layer of the first device receives the TCP corresponding to step 3 in the TCP release four-way handshake process sent by the TCP/IP layer of the first device. After the packet is received, the information in the TCP packet is obtained and sent to the network device through the third wireless air interface signaling.

Optionally, after the third air interface signaling is sent by the wireless air interface protocol layer of the first device, the TCP/IP packet corresponding to step 4 in the TCP release four-way handshake process (including the TCP/IP header) is reconstructed, that is, Segment 7 is sent to the TCP/IP layer of the first device.

Further, after receiving the third wireless air interface signaling, the network device reconstructs a TCP packet (including a TCP/IP header) corresponding to step 3 in the TCP release four-way handshake process, and sends the packet to the second device.

In the eighth embodiment of the present invention, another signaling transmission method in the process of actively initiating a TCP connection release with the first device by the second device is provided. In this embodiment, the first device and the network device extend the existing RRC. Signaling, interacting with the release of the TCP connection of the first device and the second device Information, other situations are similar to this embodiment, and will not be exemplified herein. The flow of this embodiment is as shown in FIG. 12, and includes the following steps:

S121, a peer (Peer entity), such as a server, initiates a TCP release four-way handshake process to the eNB, step 1;

S122, the eNB initiates a TCP release four-way handshake process to the peer end step 2;

S123, the eNB initiates a TCP release four-way handshake process to the peer end in step 3;

S124, the peer end initiates a TCP release four-way handshake process to the eNB, step 4;

S125. The eNB sends an RRC Connection Release message to the UE, where the RRC connection release message carries related information released by the TCP connection of the first device and the second device.

S126. The UE releases the established TCP connection with the peer.

Optionally, in order to not affect the TCP/IP layer of the UE, the wireless air interface protocol layer of the UE needs to reconstruct the TCP packet corresponding to the step 1 of the TCP release process (including the TCP/IP header) after receiving the RRC connection release message. And sending the TCP packet to the TCP/IP layer of the UE.

Further, in order not to affect the TCP/IP layer of the UE, the wireless air interface protocol layer of the UE receives the TCP packet (including the TCP/IP header) corresponding to step 3 of the TCP release process sent by the TCP/IP layer of the UE, The TCP packet corresponding to step 4 of the TCP release process (including the TCP/IP header) is constructed, and the TCP packet is sent to the TCP/IP layer of the UE.

In the ninth embodiment of the present invention, another signaling transmission method in the process of actively initiating a TCP connection release with the first device by the second device is provided. In this embodiment, the first device and the network device extend the existing RRC. The signaling is related to the information about the release of the TCP connection between the first device and the second device. The other situations are similar to the embodiment, and are not illustrated here. The flow of this embodiment is shown in FIG. 13 and includes the following steps:

S131, a peer (Peer entity), such as a server, initiates a TCP release four-way handshake process to the eNB, step 1;

S132. The eNB sends an RRC Connection Reconfiguration message to the UE, where the RRC Connection Reconfiguration message carries the TCP connection between the first device and the second device. Relevant information released;

S133. The eNB initiates a TCP release four-way handshake process to the peer end.

S134. The UE releases the established TCP connection with the peer end.

Optionally, in order to not affect the TCP/IP layer of the UE, after receiving the RRC Connection Reconfiguration message, the UE wireless air interface protocol layer reconstructs the TCP packet corresponding to the step 1 in the TCP release four-way handshake process (including TCP/IP). The header is sent to the TCP/IP layer of the UE;

Correspondingly, the TCP/IP layer of the UE sends the received TCP packet (including the TCP/IP header) to the application layer of the UE;

Correspondingly, the application layer of the UE releases the established TCP connection with the peer according to the received TCP packet (including the TCP/IP header).

S135. The UE sends an RRC Connection Reconfiguration Complete message to the eNB, where the RRC Connection Reconfiguration Complete message carries a TCP connection release response, to indicate that the UE has completed the TCP connection release.

Optionally, in order not to affect the TCP/IP layer of the UE, the wireless air interface protocol layer of the UE receives the TCP/IP packet corresponding to step 3 in the TCP release four-way handshake process sent by the TCP/IP layer of the UE (including TCP) After the /IP header, the trigger sends an RRC Connection Reconfiguration Complete message to the eNB.

S136, the eNB initiates a TCP release four-way handshake process to the peer end, step 3;

S137. The peer end initiates a TCP release four-way handshake process step 4 to the eNB.

In the embodiment of the present invention, in order to save the load of the TCP/IP header in the wireless air interface, the content of the TCP/IP header field does not need to be transmitted in the wireless air interface, that is, the network device and the first device use the wireless air interface. When transmitting, the structure of the TCP/IP header is not included in the transmitted signaling. However, for signaling of non-wireless air interface transmission, that is, signaling transmitted between the network device and the second device, the network device needs to obtain related information and reconstruct a corresponding TCP/IP header structure. In addition, after the TCP is established, when the data is sent between the first device and the second device, the air interface between the first device and the network side may not need to send a TCP/IP header, and the first device and the network side follow certain rules. Heavy Construct a corresponding TCP/IP header. The TCP/IP header reconstruction in the data transmission phase mainly includes the TCP/IP header sent by the network side to the second device (the network side receives the data sent by the first device and the network side receives the data sent by the second device). The TCP ACK packet and the first device reconstruct the TCP/IP header sent to the upper layer.

A possible method for reconstructing the TCP/IP header structure is given below, as follows:

1. Recovery of SYN/FIN in the TCP header:

When the network side or the first device receives the wireless air interface signaling and needs to resume the TCP establishment or release the corresponding TCP header, set SYN or FIN to 1 in the constructed TCP header, otherwise set to 0.

2. Recovery of the data sequence number in the TCP header:

If the current recovered TCP header has SYN=1, the data sequence number in the TCP header is the initial sequence number carried in the wireless air interface signaling or an initial sequence number randomly generated (when the wireless air interface signaling does not carry the initial sequence) Number);

otherwise:

If the previous recovered TCP header is SYN=1, the data sequence number in the currently recovered TCP/IP header is the data sequence number of the previously restored TCP header +1; otherwise, the data sequence number in the currently restored TCP header is (previous The data sequence number in the TCP header of a recovery + the size of the data carried in the TCP/IP packet to which the previously restored TCP header belongs)%(2 ³² );

3. Recovery of the window field (Window) in the TCP header: The window field is used for flow control, indicating the number of bytes that can be sent. Since the network device has the TCP layer processing function, the flow control function can be set on the network device side; when the network device reconstructs the TCP/IP header, it can be set according to the current buffer status; when the first device (such as the UE) reconstructs the TCP When the /IP header is set, it can be set to the maximum value of the window field.

4. Recovery of the identifier in the IP header: Since the identifier in the IP header is only used to indicate which packet is currently in use, the primary purpose of the identifier is to use the scenario for IP packet segmentation. When the network device reconfigures the TCP/IP header, since the uplink packet passes only the first device (such as the UE) side and does not segment the IP packet, it only needs to be set to (the last identifier + 1)% ( 2 ¹⁶ ) Yes, the first identifier can be a randomly generated number (within the valid range). When the first device reconfigures the TCP/IP header, since the network side has the TCP/IP layer function, the network side can wait until all the same IP packet arrives before sending it to the first device, so it only needs to be set to (on The identifier of one time is +1)%(2 ¹⁶ ), and the first identifier can be a randomly generated number (within the effective range);

5. Recovery of the acknowledgment sequence number (ACK SN) and acknowledgement field (ACK) in the TCP header:

In addition to setting the acknowledgment field (ACK) to 0 in step 1 of the TCP connection establishment procedure, the acknowledgment field (ACK) is set to 1 under other conditions.

For the TCP connection establishment process TCP ACK message (including the TCP ACK constructed by the network device and the UE), the ACK SN is set to (the initial sequence number +1 carried in the wireless air interface signaling) +1% (2 ³² ).

For the TCP ACK packet corresponding to the downlink data packet (that is, the TCP ACK constructed by the network device) and the TCP ACK packet constructed by the network device side in the TCP release process, the network device generates the ACK according to the RLC layer ACK or the physical (PHY) layer ACK. That is, the network device can know which packets are correctly transmitted and which packets are not transmitted correctly, and the network device can generate a TCP/IP ACK according to the situation, wherein the ACK SN is set to correspond to the ordered data packet that the network device has correctly transmitted. Byte number; or, the network device saves the received downlink data packet, and directly sends the TCP layer ACK SN and ACK to the opposite end (that is, the wireless side does not need to wait for the correct transmission, and the subsequent wireless side transmission error occurs, the network device directly focuses on the wireless side. The ACK SN is set to the byte number corresponding to the TCP packet that the network device has received correctly and orderly.

For the TCP ACK message corresponding to the uplink data packet (ie, the TCP ACK constructed by the UE side) and the TCP ACK message constructed by the UE side in the TCP release process, the first device (such as the UE) according to the RLC layer ACK or PHY layer in the wireless protocol The ACK situation is generated, that is, the RLC layer or the PHY layer in the wireless protocol can know which packets are correctly transmitted and which packets are not transmitted correctly. Therefore, the first device can generate a TCP/IP ACK according to these conditions (the ACK SN is set to the wireless protocol has been correctly transmitted. The byte number corresponding to the ordered data packet.

Based on any of the foregoing embodiments, in the embodiment of the present invention, if the second device is also a wireless device, the second device and the network device may perform interaction through wireless air interface signaling. Optionally, the second device and the network device The wireless air interface signaling between the interaction does not include the TCP/IP header, and the specific process and the The wireless air interface signaling between a device and a network device is similar, and is not illustrated in the present invention.

The above method processing flow can be implemented by a software program, which can be stored in a storage medium, and when the stored software program is called, the above method steps are performed.

Based on the same inventive concept, in a tenth embodiment of the present invention, a terminal device is provided. As shown in FIG. 14, the device includes:

The information interaction module 141 is configured to exchange, by using the first wireless air interface signaling, information related to the establishment or release of the transmission control protocol TCP connection between the first device and the second device, and the first wireless air interface signaling. Does not include the TCP/IP header structure;

The processing module 142 is configured to establish a TCP connection with the second device according to the related information about the TCP connection established by the first device and the second device, or release the TCP connection according to the first device and the second device. Related information, releasing a TCP connection with the second device.

For the related information about the establishment of the TCP connection between the first device and the second device, refer to the related description in any embodiment shown in FIG. 6 to FIG. 13 , and details are not described herein again.

In this embodiment, the first wireless air interface signaling, the second wireless air interface signaling, and the third wireless air interface signaling, refer to related descriptions in any of the embodiments shown in FIG. 6 to FIG. I will not repeat them here.

Based on any of the foregoing embodiments, the information interaction module is further configured to:

Based on the same inventive concept, in the eleventh embodiment of the present invention, another terminal device is provided. As shown in FIG. 15, the device includes: a transceiver 151, and at least one processor 152 connected to the transceiver 151. among them:

The processor 152 is configured to read a program in the memory 153 and perform the following process:

Controlling, by the first wireless air interface signaling, the transceiver interacts with the network device to establish or release related information of the transmission control protocol TCP connection between the first device and the second device, where the first wireless The TCP/IP header structure is not included in the air interface signaling;

The transceiver 151 is configured to receive and transmit data under the control of the processor 152.

Wherein, in FIG. 15, the bus architecture can include any number of interconnected buses and bridges, specifically linked by one or more processors represented by processor 152 and various circuits of memory represented by memory 153. The bus architecture can also link various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art and, therefore, will not be further described herein. The bus interface provides an interface. Transceiver 151 can be a plurality of components, including a transmitter and a receiver, providing means for communicating with various other devices on a transmission medium. For different user equipments, the user interface 154 may also be an interface capable of externally connecting the required devices, including but not limited to a keypad, a display, a speaker, a microphone, a joystick, and the like.

The processor 152 is responsible for managing the bus architecture and general processing, and the memory 153 can store data used by the processor 152 in performing operations.

For the information about the establishment or the release of the TCP connection between the first device and the second device, refer to the related description in any embodiment shown in FIG. 6 to FIG. 13 , and details are not described herein again.

Based on any of the above embodiments, the processor 152 reads the program in the memory 153 and also performs the following process:

Based on the same inventive concept, in the twelfth embodiment of the present invention, a network device is provided, as shown in the figure. As shown in Figure 16, the device includes:

The interaction module 161 is configured to exchange, by using the first wireless air interface signaling, information related to the connection or release of the transmission control protocol TCP connection between the first device and the second device, and the first wireless air interface signaling. Does not include the TCP/IP header structure;

The management module 162 is configured to initiate the first device and the second device to the first device or the second device according to related information about the TCP connection established by the first device and the second device. The TCP connection is established; or the TCP of the first device and the second device is initiated to the first device or the second device according to the related information released by the TCP connection of the first device and the second device The connection is released.

Optionally, the interaction module is further configured to:

or

Optionally, the information interaction module is configured to: before the first device interacts with the first device to establish or release the related information about the TCP connection of the first device and the second device, by using the first wireless air interface signaling,

Based on any of the above embodiments, the interaction module is further configured to:

In this embodiment, the first wireless air interface signaling, the second wireless air interface signaling, and the third wireless air interface signaling are specifically referred to the related description in any of the embodiments shown in FIG. 6 to FIG. I won't go into details here.

Based on the same inventive concept, in the thirteenth embodiment of the present invention, another network device is provided. As shown in FIG. 17, the device includes: a transceiver 171, and at least one processor 172 connected to the transceiver 171. among them:

The processor 172 is configured to read a program in the memory 173 and perform the following process:

The transceiver 171 is configured to receive and transmit data under the control of the processor 172.

Here, in FIG. 17, the bus architecture may include any number of interconnected buses and bridges, specifically linked by one or more processors represented by processor 172 and various circuits of memory represented by memory 173. The bus architecture can also link various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art and, therefore, will not be further described herein. The bus interface provides an interface. Transceiver 171 can be a plurality of components, including a transmitter and a transceiver, providing means for communicating with various other devices on a transmission medium. The processor 172 is responsible for managing the bus architecture and general processing, and the memory 173 can store data used by the processor 172 in performing operations.

Optionally, the processor reads the program in the memory, and further executes:

or

Reconstructing a TCP/IP header according to related information released by the TCP connection of the first device and the second device, and controlling the transceiver to send the second device to request the second device to release the The first TCP connection of the TCP connection of the first device releases signaling, and the first TCP connection release signaling includes a reconstructed TCP/IP header.

Optionally, the transceiver performs, by using the first wireless air interface signaling, before the first device interacts with the information about establishing or releasing the TCP connection between the first device and the second device,

Based on any of the above embodiments, the processor reads the program in the memory and further performs:

Those skilled in the art will appreciate that embodiments of the present invention can be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment, or a combination of software and hardware. Moreover, the invention can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) including computer usable program code.

The present invention has been described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (system), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flowchart illustrations and/or FIG. These computer program instructions can be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing device to produce a machine for the execution of instructions for execution by a processor of a computer or other programmable data processing device. Means for implementing the functions specified in one or more of the flow or in a block or blocks of the flow chart.

The computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device. The apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.

These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device. The instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.

While the preferred embodiment of the invention has been described, it will be understood that Therefore, the right to attach All changes and modifications are intended to be included within the scope of the invention.

It is apparent that those skilled in the art can make various modifications and variations to the invention without departing from the spirit and scope of the invention. Thus, it is intended that the present invention cover the modifications and modifications of the invention

Claims

A signaling transmission method, the method comprising:

The first device exchanges, by using the first wireless air interface signaling, information related to the establishment or release of the TCP connection of the first device and the second device with the network device, where the first wireless air interface signaling does not include TCP/ IP header structure;

The first device establishes a TCP connection with the second device according to related information established by the TCP connection of the first device and the second device; or the first device is configured according to the first device and the second device The TCP connection releases relevant information, releasing the TCP connection with the second device.
The method of claim 1, wherein the information about the TCP connection established by the first device and the second device comprises: indicating that the network device is proxying the TCP connection of the first device and the second device Instructions; or

The related information about the TCP connection release of the first device and the second device includes: indication information for instructing the network device to proxy TCP release of the first device and the second device.
The method according to claim 1 or 2, wherein the information about the TCP connection established by the first device and the second device comprises: a TCP initial sequence number of the first device or a TCP of the second device Initial serial number.
The method according to claim 1, wherein the first wireless air interface signaling is radio resource control RRC signaling, non-access stratum NAS signaling, or MAC layer signaling defined in a standard or protocol.
The method according to any one of claims 1 to 4, wherein the method comprises:

The first device establishes a response by interacting with the network device by using the second wireless air interface signaling, where the second wireless air interface signaling does not include a TCP/IP header structure; or

The first device exchanges a TCP connection with the network device by using the third wireless air interface signaling, and the third wireless air interface signaling does not include a TCP/IP header structure.
The method according to claim 5, wherein the second wireless air interface signaling further comprises: a TCP initial sequence number of the first device, or a TCP initial sequence number of the second device.
The method according to claim 5, wherein the second wireless air interface signaling is RRC signaling, NAS signaling, or MAC layer signaling defined in a standard or protocol;

The third wireless air interface signaling is RRC signaling, NAS signaling, or MAC layer signaling defined in a standard or protocol.
A signaling transmission method, the method comprising:

The network device interacts with the first device by using the first wireless air interface signaling to establish or release information related to the TCP connection of the first device and the second device, where the first wireless air interface signaling does not include TCP/ IP header structure;

The network device initiates TCP of the first device and the second device to the first device or the second device according to related information established by the TCP connection of the first device and the second device Establishing the connection; or the network device initiating the first device and the second device according to the related information released by the TCP connection of the first device and the second device to the first device or the second device The TCP connection is released.
The method according to claim 8, wherein the network device interacts with the first device by using the first wireless air interface signaling, after the first device interacts with the TCP connection of the first device and the second device. The method further includes:

The network device reconstructs a TCP/IP header according to related information established by the TCP connection of the first device and the second device, and sends the second device to request the second device to establish and a first TCP connection establishment signaling of a TCP connection of the first device, where the first TCP connection establishment signaling includes a reconstructed TCP/IP header;

or

The network device initiates, according to the information about the release of the TCP connection of the first device and the second device, the TCP connection release of the first device and the second device to the second device, including: Determining, by the network device, the TCP/IP header according to the related information released by the TCP connection of the first device and the second device, and sending the second device to request the second device to release the first The first TCP connection of the TCP connection of the device releases signaling, and the first TCP connection release signaling includes a reconstructed TCP/IP header.
The method according to claim 8 or 9, wherein the information about the establishment or release of the TCP connection between the first device and the second device comprises: indicating that the network device is proxying the first device and the second device Instructions for TCP connection or release.
The method according to claim 8 or 9, wherein the information about the TCP connection established by the first device and the second device comprises: a TCP initial sequence number of the first device, or a second device TCP initial sequence number.
The method of claim 9 wherein the method further comprises:

The network device establishes a response by interacting with the first device by using a second wireless air interface signaling; or

The network device releases a response by interacting with the first device by using a third wireless air interface signaling.
The method according to claim 12, wherein the second wireless air interface signaling further comprises: a TCP initial sequence number of the first device, or a TCP initial sequence number of the second device.
The method according to claim 12, wherein the first wireless air interface signaling is defined as radio resource control RRC signaling, non-access stratum NAS signaling, or MAC layer signaling defined in a standard or protocol; and / or

The second wireless air interface signaling is RRC signaling, NAS signaling, or MAC layer signaling defined in a standard or protocol; and/or

The third wireless air interface signaling is RRC signaling, NAS signaling, or MAC layer signaling defined in a standard or protocol.
A terminal device, the device comprising:

An information interaction module, configured to exchange, by using the first wireless air interface signaling, information related to the establishment or release of the TCP connection of the first device and the second device with the network device, where the first wireless air interface signaling is not Contains the TCP/IP header structure;

a processing module, configured to establish a TCP connection with the second device according to the related information about the TCP connection established by the first device and the second device; or release the TCP connection according to the first device and the second device Related information, releasing a TCP connection with the second device.
The device according to claim 15, wherein the information about the TCP connection established by the first device and the second device comprises: indicating that the network device is proxying the TCP connection of the first device and the second device Instructions; or

The related information about the TCP connection release of the first device and the second device includes: indication information for instructing the network device to proxy TCP release of the first device and the second device.
The device according to claim 15 or 16, wherein the information about the TCP connection established by the first device and the second device comprises: a TCP initial sequence number of the first device, or a second device TCP initial sequence number.
The device according to claim 15, wherein the first wireless air interface signaling is radio resource control RRC signaling, non-access stratum NAS signaling, or MAC layer signaling defined in a standard or protocol.
The device according to claim 15 or 16, wherein the information interaction module is further configured to:

Establishing, by the second wireless air interface signaling, a TCP connection establishment response with the network device, where the second wireless air interface signaling does not include a TCP/IP header structure; or

And transmitting, by the third wireless air interface signaling, a TCP connection release response with the network device, where the third wireless air interface signaling does not include a TCP/IP header structure.
The device according to claim 19, wherein the second wireless air interface signaling further comprises: a TCP initial sequence number of the first device or a TCP initial sequence number of the second device.
The device according to claim 19, wherein the second wireless air interface signaling is RRC signaling, NAS signaling, or MAC layer signaling defined in a standard or protocol;

The third wireless air interface signaling is RRC signaling, NAS signaling, or MAC layer signaling defined in a standard or protocol.
A network device, the device comprising:

An interaction module, configured to exchange, by using the first wireless air interface signaling, information related to the establishment or release of the TCP connection of the first device and the second device by the first device, where the first wireless air interface signaling is not Contains the TCP/IP header structure;

a management module, configured to initiate, according to the related information established by the TCP connection of the first device and the second device, the first device and the second device to the first device or the second device Establishing a TCP connection; or initiating a TCP connection between the first device and the second device to the first device or the second device according to related information released by the TCP connection of the first device and the second device freed.
The device of claim 22, wherein the interaction module is further configured to:

Reconstructing a TCP/IP header according to related information established by the TCP connection of the first device and the second device, and sending, to the second device, a request for the second device to establish the first device The first TCP connection establishment signaling of the TCP connection, where the first TCP connection establishment signaling includes a reconstructed TCP/IP header;

or

Reconstructing a TCP/IP header according to related information released by the TCP connection of the first device and the second device, and sending, to the second device, a request for the second device to release the TCP with the first device The connected first TCP connection releases signaling, and the first TCP connection release signaling includes a reconstructed TCP/IP header.
The device according to claim 22 or 23, wherein the information about the establishment or release of the TCP connection between the first device and the second device comprises: indicating that the network device is proxying the first device and the second device Instructions for TCP connection or release.
The device according to claim 22 or 23, wherein the information about the TCP connection established by the first device and the second device comprises: a TCP initial sequence number of the first device, or a second device TCP initial sequence number.
The device of claim 23, wherein the interaction module is further configured to:

Establishing a response by interacting with the first device by using the second wireless air interface signaling; or

The TCP connection release response is exchanged with the first device by the third wireless air interface signaling.
The device according to claim 26, wherein the second wireless air interface signaling further comprises: a TCP initial sequence number of the second device.
The device according to claim 26, wherein said first wireless air interface signaling is Radio resource control RRC signaling, non-access stratum NAS signaling, or MAC layer signaling defined in the standard or protocol; and/or

The second wireless air interface signaling is RRC signaling, NAS signaling, or MAC layer signaling defined in a standard or protocol; and/or

The third wireless air interface signaling is RRC signaling, NAS signaling, or MAC layer signaling defined in a standard or protocol.