WO2021062690A1

WO2021062690A1 - Ethernet frame packet header compression processing method and apparatus, user terminal, base station and medium

Info

Publication number: WO2021062690A1
Application number: PCT/CN2019/109580
Authority: WO
Inventors: 付喆
Original assignee: Oppo广东移动通信有限公司
Priority date: 2019-09-30
Filing date: 2019-09-30
Publication date: 2021-04-08
Also published as: CN113711558B; CN113711558A

Abstract

The present disclosure provides an Ethernet frame packet header compression processing method and apparatus, a user terminal, a base station, and a medium. Said method applied to a user terminal comprises: upon acquisition of a packet data convergence protocol re-establishment instruction, if a transmission mode of a current bearer is a confirmation mode, a configuration file satisfies a preset condition and the current bearer comprises a preset data packet, sending at least one first complete data packet to a base station; each first complete data packet comprises context information, uncompressed packet header information and a first sequence number, the context information being context information reset after the user terminal has acquired the packet data convergence protocol re-establishment instruction, and the first sequence number being any sequence number not received by the base station in the bearer. Thus, successful acquisition of the reset context information by the base station can be guaranteed, and normal data transmission can be guaranteed.

Description

Ethernet frame header compression processing method, device, user terminal, base station and medium

Technical field

The present disclosure relates to the technical fields of data processing and network transmission, and in particular to a method, device, user terminal, base station, and medium for compressing the header of an Ethernet frame.

Background technique

At present, when the user terminal communicates with the base station, if it receives a Packet Data Convergence Protocol (PDCP) reconstruction request, the user terminal needs to perform the PDCP reconstruction process. After performing the reconstruction process, perform the normal PDCP layer data transmission.

However, if the configuration parameter drb-ContinueROHC in the configuration file is not assigned or is assigned false, the user terminal will reset the header when the transmission mode is confirmed and there is an unsuccessful data packet before reconstruction. The context information is compressed, and accordingly, the user terminal will send a PDCP protocol data unit (Protocol Data Unit, PDU for short) containing complete header information and context information to the base station. If the data packet sent uses the sequence number (SN) of the PDCP PDU sent before reconstruction, the base station will think that the data packet corresponding to this SN has been received, which will cause the base station to directly delete the PDCP PDU without further checking or Obtaining the information therein results in the inability to obtain and/or store valid (new) header compression context information. Furthermore, since the base station does not have valid header compression context information, the compressed package sent by the subsequent user terminal cannot be decompressed, resulting in decompression failure and data transmission failure.

Public content

The present disclosure proposes an Ethernet frame header compression processing method, device, user terminal, base station, and medium to ensure that the base station successfully obtains the reset context information, so that the base station can normally decompress the compressed packet sent by the user terminal Processing to ensure the normal transmission of data is used to solve the technical problem that the base station cannot perform decompression in the prior art.

The embodiment of the first aspect of the present disclosure proposes an Ethernet frame header compression processing method, which is applied to a user terminal, and includes:

When the packet data convergence protocol re-establishment instruction is obtained, if the transmission mode of the current bearer is the confirmed mode, and the configuration file meets the preset conditions, and the current bearer includes preset data packets, at least one first complete packet is sent to the base station data pack;

Wherein, each first complete data packet includes: context information, uncompressed header information, and a first sequence number, where the context information is the context reset after the user terminal obtains the packet data convergence protocol reconstruction instruction Information, the first sequence number is any sequence number that the base station has not received in the bearer.

In the method for compressing the header of an Ethernet frame in the embodiment of the present disclosure, when the user terminal obtains the packet data convergence protocol reconstruction instruction, if the transmission mode of the current bearer is the confirmed mode, and the configuration file meets the preset conditions, and the current bearer includes pre- Assuming a data packet, at least one first complete data packet is sent to the base station; where each first complete data packet includes: context information, uncompressed header information, and a first sequence number, where the context information is the user terminal The context information reset after the packet data convergence protocol reconstruction instruction is acquired, the first sequence number is any sequence number that the base station has not received in the bearer. In the present disclosure, the user terminal sends at least one first complete data packet to the base station. Since the first complete data packet includes a sequence number that the base station has not received in the bearer, it can ensure that the base station successfully obtains the reset context information, thereby enabling The base station performs normal decompression processing on the compressed packet sent by the user terminal to ensure the normal transmission of data.

The embodiment of the second aspect of the present disclosure proposes another method for compressing the header of an Ethernet frame, which is applied to a base station, and includes:

When the packet data convergence protocol reconstruction request is obtained, if the transmission mode of the current session is the confirmation mode, the configuration file meets the preset conditions, and the first sequence number in the first complete data packet obtained from the user terminal is If the base station has not received a sequence number in the current bearer, then save the context information in the first complete data packet, so as to perform decompression processing on the new compressed packet according to the context information in the first complete data packet;

Wherein, the first complete data packet is sent by the user terminal to the base station after obtaining the packet data convergence protocol reconstruction instruction.

According to the method for compressing the header of the Ethernet frame in the embodiment of the present disclosure, when the base station obtains the packet data convergence protocol reconstruction request, if the transmission mode of the current session is the confirmation mode and the configuration file meets the preset conditions, and the first obtained from the user terminal The first sequence number in a complete data packet is a sequence number that the base station has not received in the current bearer, and the context information in the first complete data packet is saved to compare the new compressed packet according to the context information in the first complete data packet. Perform decompression processing; where the first complete data packet is sent by the user terminal to the base station after obtaining the packet data convergence protocol reconstruction instruction. In the present disclosure, it can be ensured that the base station successfully obtains the reset context information, so that the base station can perform normal decompression processing on the compressed packet sent by the user terminal, and ensure the normal transmission of data.

The embodiment of the third aspect of the present disclosure proposes another method for compressing the header of an Ethernet frame, which is applied to a base station, and includes:

When the packet data convergence protocol reconstruction request is obtained, if the transmission mode of the current session is the confirmation mode, the configuration file meets the preset condition, and the second sequence number in the second complete data packet obtained from the user terminal is The sequence number that the base station has received in the current bearer saves the context information in the second complete data packet.

According to the method for compressing the header of the Ethernet frame in the embodiment of the present disclosure, when the base station obtains the packet data convergence protocol reconstruction request, if the transmission mode of the current session is the confirmation mode, and the configuration file meets the preset conditions, and the first obtained from the user terminal 2. The second sequence number in the second complete data packet is a sequence number that the base station has received in the current bearer, and the context information in the second complete data packet is saved. In this way, it can be ensured that the base station successfully obtains the context information, so that the base station can perform normal decompression processing on the compressed packet sent by the user terminal to ensure normal data transmission.

The embodiment of the fourth aspect of the present disclosure proposes an Ethernet frame header compression processing device, which is set in a user terminal and includes:

The sending module is used to send to the base station if the transmission mode of the current bearer is the confirmed mode, the configuration file meets the preset condition, and the preset data packet is included in the current bearer when the packet data convergence protocol reconstruction instruction is obtained At least one first complete data packet;

In the Ethernet frame header compression processing device of the embodiment of the present disclosure, when the user terminal obtains the packet data convergence protocol reconstruction instruction, if the transmission mode of the current bearer is the confirmed mode, and the configuration file meets the preset conditions, and the current bearer includes pre- Assuming a data packet, at least one first complete data packet is sent to the base station; where each first complete data packet includes: context information, uncompressed header information, and a first sequence number, where the context information is the user terminal The context information reset after the packet data convergence protocol re-establishment instruction is acquired, the first sequence number is any sequence number that the base station has not used in the bearer. In the present disclosure, the user terminal sends at least one first complete data packet to the base station. Since the first complete data packet includes a sequence number that the base station has not received in the bearer, it can ensure that the base station successfully obtains the reset context information, thereby enabling The base station performs normal decompression processing on the compressed packet sent by the user terminal to ensure the normal transmission of data.

The embodiment of the fifth aspect of the present disclosure proposes another Ethernet frame header compression processing device, which is set in a base station, and includes:

The saving module is used to obtain the packet data convergence protocol reconstruction request, if the transmission mode of the current session is the confirmation mode, and the configuration file meets the preset condition, and the first complete data packet obtained from the user terminal A sequence number is a sequence number that the base station has not received in the current bearer, and then the context information in the first complete data packet is saved, so that the new compressed packet can be performed according to the context information in the first complete data packet. Decompression processing;

In the Ethernet frame header compression processing device of the embodiment of the present disclosure, when the base station obtains the packet data convergence protocol reconstruction request, if the transmission mode of the current session is the confirmation mode, and the configuration file meets the preset conditions, and the first obtained from the user terminal The first sequence number in a complete data packet is a sequence number that the base station has not received in the current bearer, and the context information in the first complete data packet is saved to compare the new compressed packet according to the context information in the first complete data packet. Perform decompression processing; where the first complete data packet is sent by the user terminal to the base station after obtaining the packet data convergence protocol reconstruction instruction. In the present disclosure, it can be ensured that the base station successfully obtains the reset context information, so that the base station can perform normal decompression processing on the compressed packet sent by the user terminal, and ensure the normal transmission of data.

The embodiment of the sixth aspect of the present disclosure proposes another Ethernet frame header compression processing device, which is set in a base station, and includes:

The saving module is used to, when the packet data convergence protocol reconstruction request is obtained, if the transmission mode of the current session is the confirmation mode, and the configuration file meets the preset conditions, and the second complete data packet obtained from the user terminal is the first The second sequence number is the sequence number that the base station has received in the current bearer, and the context information in the second complete data packet is saved.

In the Ethernet frame header compression processing device of the embodiment of the present disclosure, when the base station obtains the packet data convergence protocol reconstruction request, if the transmission mode of the current session is the confirmation mode, and the configuration file meets the preset conditions, and the first obtained from the user terminal 2. The second sequence number in the second complete data packet is a sequence number that the base station has received in the current bearer, and the context information in the second complete data packet is saved. In this way, it can be ensured that the base station successfully obtains the context information, so that the base station can perform normal decompression processing on the compressed packet sent by the user terminal to ensure normal data transmission.

An embodiment of the seventh aspect of the present disclosure proposes a user terminal, including: a memory, a processor, and a computer program stored in the memory and capable of running on the processor. When the processor executes the program, the implementation is as follows: The Ethernet frame header compression processing method proposed by the embodiment of the first aspect.

The embodiment of the eighth aspect of the present disclosure proposes a base station, including: a memory, a processor, and a computer program stored in the memory and capable of running on the processor. When the processor executes the program, the implementation is as described in the present disclosure. The embodiment of the second aspect proposes a method for compressing the header of an Ethernet frame.

An embodiment of the ninth aspect of the present disclosure proposes a base station, including: a memory, a processor, and a computer program stored on the memory and capable of running on the processor. When the processor executes the program, the implementation is as follows: The third embodiment provides a method for compressing the header of an Ethernet frame.

An embodiment of the tenth aspect of the present disclosure proposes a computer-readable storage medium on which a computer program is stored, characterized in that, when the program is executed by a processor, the Ethernet frame header compression as proposed in the embodiment of the first aspect of the present disclosure is implemented The processing method, or implements the Ethernet frame header compression processing method as proposed in the embodiment of the second aspect of the present disclosure, or implements the Ethernet frame header compression processing method as proposed in the embodiment of the third aspect of the present disclosure.

The additional aspects and advantages of the present disclosure will be partially given in the following description, and some will become obvious from the following description, or be understood through the practice of the present disclosure.

Description of the drawings

In order to more clearly describe the technical solutions in the embodiments of the present disclosure, the following will briefly introduce the drawings that need to be used in the embodiments. Obviously, the drawings in the following description are some embodiments of the present disclosure. For those of ordinary skill in the art, without creative work, other drawings can be obtained from these drawings.

FIG. 1 is a schematic flowchart of a method for compressing an Ethernet frame header provided by Embodiment 1 of the present disclosure;

FIG. 2 is a schematic diagram of the interaction flow between a user terminal and a base station in an embodiment of the disclosure;

3 is a schematic flow chart of the method for compressing the header of an Ethernet frame provided by the second embodiment of the present disclosure;

4 is a schematic flowchart of a method for compressing an Ethernet frame header provided by the third embodiment of the disclosure;

5 is a schematic structural diagram of an Ethernet frame header compression processing apparatus provided by Embodiment 4 of the present disclosure;

6 is a schematic structural diagram of an Ethernet frame header compression processing apparatus provided by Embodiment 5 of the present disclosure;

FIG. 7 is a schematic structural diagram of an Ethernet frame header compression processing apparatus provided by Embodiment 6 of the present disclosure;

FIG. 8 is a schematic structural diagram of an Ethernet frame header compression processing apparatus provided by the seventh embodiment of the disclosure.

Detailed ways

The embodiments of the present disclosure are described in detail below. Examples of the embodiments are shown in the accompanying drawings, in which the same or similar reference numerals denote the same or similar elements or elements with the same or similar functions. The embodiments described below with reference to the drawings are exemplary, and are intended to explain the present disclosure, but should not be construed as limiting the present disclosure.

In the 5G Industrial Internet (Industrial Internet of Things, IIoT), it is required to support the transmission of services such as Industrial Automation (Factory Automation), Transmission Automation (Transport Industry), and Intelligent Power (Electrical Power Distribution) in 5G systems. Based on its transmission requirements for delay and reliability, IIoT introduces the concept of time-sensitive network TSN or TSC, and requires header compression processing for TSN services. Among them, the TSC service can be carried by an Ethernet frame, or can be carried by an IP data packet.

Among them, the introduction of the Ethernet frame issue is because the existing communication system only supports header compression for data packets whose PDU session is IP. In a 5G New Radio (NR) system, the type of PDU session can be not only an IP data packet type, but also an Ethernet frame type. For example, for the PDU layer, when the PDU session type is Internet Protocol version 4 (Internet Protocol version 4, Pv4 for short) or IPv6 or IPv4v6, the PDU session corresponds to IPv4 data packets and/or IPv6 data packets; when the PDU session When the type is Ethernet, the PDU session corresponds to an Ethernet frame.

At present, the PDCP protocol has introduced header compression and decompression functions to perform header compression on IP data packets. The current Robust Header Compression (RoHC) is configured for Data Radio Bearer (DRB). The compression end and the decompression end use different header compression and header compression parameters according to the configuration file. RoHC protocol for compression and decompression processing. Among them, it is configured in PDCP-config, and each PDCP-config corresponds to a DRB.

During PDCP reconstruction, if the parameter drb-ContinueROHC is configured in the configuration file, it means that the previous RoHC information will be used for compression and decompression after reconstruction. Otherwise, the state of compression and decompression will be reset, that is, the decompression end will not have valid context information, and it needs to receive new context information. The compression end needs to reset the compression state and send the uncompressed state containing context information to the decompression end. Data packet, that is, complete data packet.

When the user terminal communicates with the base station, when receiving a PDCP re-establishment request from a higher layer, the user terminal needs to perform the PDCP re-establishment process. After performing the re-establishment process, perform normal PDCP layer data transmission. If drb-ContinueROHC is not configured, or is false, during the reconstruction process, when the transmission mode is the confirmation mode, if PDCP PDU has been transmitted to the lower layer before the reconstruction, but the confirmation of successful transmission or unsuccessful transmission has not been received yet, Then when the user terminal transmits or retransmits these data packets, it needs to use PDCP to rebuild the SN used before, but use the new header compression context information to send the data packets, that is, delete the original context, header compression status and context information reset, use The new context information sends PDCP PDU. Then, after receiving the reconstruction request, the user terminal needs to use the SN before the reconstruction to send the uncompressed data packet containing the new context information to the base station. Then, the corresponding PDCP PDU corresponding to the subsequent SN is sent.

When the base station receives the PDCP re-establishment request from the upper layer, it needs to process the PDCP PDU received from the lower layer due to the re-establishment and subsequent PDUs. For the PDCP PDU received before the reconstruction request, the base station can perform decompression processing according to the original context information, and for the PDCP PDU received after the reconstruction request, the processing process includes: deleting the PDU with the same SN (that is, when the base station receives After a PDU, when the SN corresponding to this PDU is found to be the previously received SN, the base station will directly discard the data packet without further checking the information in the packet), reset the new context information, and reset the decompression state , Decompress according to the new context information, and receive the new PDU after the reconstruction request.

However, if the configuration parameter drb-ContinueROHC in the configuration file is not assigned or is assigned false, the user terminal will reset the header when the transmission mode is confirmed and there is an unsuccessful data packet before reconstruction. The context information is compressed, and accordingly, the user terminal will send a PDCP PDU containing complete header information and context information to the base station. If the data packet sent uses the sequence number (SN) of the PDCP PDU sent before reconstruction, the base station will think that the data packet corresponding to this SN has been received, which will cause the base station to directly delete the PDCP PDU without further checking or Obtaining the information therein results in the inability to obtain and/or store valid (new) header compression context information. Furthermore, since the base station does not have valid header compression context information, the compressed package sent by the subsequent user terminal cannot be decompressed, resulting in decompression failure and data transmission failure.

Therefore, the present disclosure mainly aims at the above-mentioned base station's inability to perform decompression technology, and proposes an Ethernet frame header compression processing method.

The following describes the method, device, user terminal, base station, and medium for compressing the header of an Ethernet frame according to the embodiments of the present disclosure with reference to the accompanying drawings. Before describing the embodiments of the present disclosure in detail, in order to facilitate understanding, first introduce the common technical terms of the present disclosure:

Header compression refers to compressing the header of a data packet to improve the transmission efficiency of user data. Currently, in Long Term Evolution (LTE) and NR, at the PDCP layer, RoHC is used to perform header compression on data packet headers.

A full packet (full packet) is an Ethernet packet (Ethernet packet) that contains complete Ethernet hearer header information and context information, etc., such as context ID, indication information (used to indicate that the packet is Compressed packet or complete data packet), and other possible but yet to be determined uplink information, such as profile ID. Among them, the context information is used for packet header compression and/or decompression. Specifically, when the compression end and the decompression end establish their context relationship, or the decompression end receives and saves valid context information (specifically, valid context information includes: context identification or indication, complete header information. Further, it can be inferred Or after saving the context identifier or indicating the corresponding relationship with the complete header information), the two can interact with each other to compress the package.

A compressed packet is an Ethernet packet that contains compressed Ethernet hearer header information (not including header information, or only part of the header information), context information, and so on.

FIG. 1 is a schematic flowchart of a method for compressing an Ethernet frame header provided by Embodiment 1 of the present disclosure.

The method for compressing the header of an Ethernet frame in the embodiment of the present disclosure may be applied to a user terminal, and the user terminal may specifically be a compression end, that is, a PDCP sending entity. Correspondingly, the receiving end (decompression end, PDCP receiving entity) is a base station.

Of course, in another implementation manner, the Ethernet frame header compression processing method can be applied to the base station side, that is, the base station is the compression end, that is, the PDCP sending entity. Correspondingly, the receiving end (decompression end, PDCP receiving entity) is the user terminal.

The following mainly uses the compression end to which the Ethernet frame header compression processing method is applied to the user terminal. The method where the compression end is a base station is similar.

As shown in FIG. 1, the method for compressing the header of an Ethernet frame may include the following steps:

Step 101: When the packet data convergence protocol re-establishment instruction is obtained, if the transmission mode of the current bearer is the confirmed mode, the configuration file meets preset conditions, and the current bearer includes preset data packets, send at least one first data packet to the base station. Complete data package.

Among them, each first complete data packet includes: context information, uncompressed header information, and a first sequence number. The context information is context information that is reset after the user terminal obtains the packet data convergence protocol reconstruction instruction. The first sequence number is any sequence number that the base station has not received in the bearer.

In the embodiment of the present disclosure, the transmission mode may include a transparent mode (TM), an unconfirmed mode (UM), and an acknowledged mode (AM).

In the embodiment of the present disclosure, that the configuration file satisfies the preset condition may include: the configuration parameter preset in the configuration file is not assigned a value, or the configuration parameter preset in the configuration file is assigned a value of false. For example, the preset configuration parameter may be drb-ContinueROHC. When drb-ContinueROHC is not assigned, or when drb-ContinueROHC is assigned false, it is determined that the configuration parameter satisfies the preset condition.

In the embodiment of the present disclosure, the preset data packet may be a data packet that the user terminal fails to send before obtaining the reconstruction instruction, or the preset data packet may be the user terminal that fails to obtain a successful transmission confirmation or an unconfirmed transmission when the user terminal obtains the reconstruction instruction. The state of the data packet, or the preset data packet may also be the data packet lost when the user terminal obtains the reconstruction instruction, or the preset data packet may also be the data packet lost before the user terminal obtains the reconstruction instruction. This is not a limitation. For example, the preset data packet may be confirmed according to the PDCP status report, where the preset data packet may include at least one of the following: PDUs that have been successfully transmitted, PDUs that have not been successfully transmitted, missing PDUs, and transmission status Uncertain PDU.

In the embodiment of the present disclosure, each first complete data packet includes a first sequence number, and the first sequence number in different first complete data packets may be different. Among them, the first serial number may be a serial number (SN), or the first serial number may also be a count (COUNT). Among them, COUNT occupies 32 bits and is composed of Hyper Frame Number (HFN) and PDCP SN, and SN is the low bit of COUNT.

In the embodiment of the present disclosure, the first sequence number in the first complete data packet is any sequence number that the base station has not received in the current bearer. Among them, the sequence number that the base station has not received in the current bearer, that is, the first sequence number may be the user The sequence number that has not been used by the terminal, or may also be the sequence number used by the user terminal, but the sequence number is the sequence number in the missing data packet (missing PDU), which is not limited.

As a possible implementation manner, when the serial numbers are generated sequentially, the first serial number may be the first of the unused serial numbers, or the M-th of the unused serial numbers. For example, the first sequence number may be an SN that has not been used or sent when the user terminal sends a data packet before the PDCP reestablishment, or the first sequence number may be the next SN or the next SN or the last SN carried in the PDCP status report. After the M-th SN, for example, if the last SN carried in the PDCP status report is 10, the first sequence number can be 11, 12, 13, etc., or the first sequence number can also be one that has not been confirmed by the base station. The next SN or the Mth SN of the SN, this disclosure does not limit this.

As another possible implementation, when the serial number is randomly generated, that is, the serial number sent by the user terminal each time is not continuous. In this case, the serial number that the user terminal has used can be recorded, so that the serial number that has been used can be recorded according to the used serial number. Serial number, to determine the serial number that has not been used. For example, if the serial numbers that the user terminal has used are 1 and 10, the first serial number can be 3, 5, 15, 17, and so on.

In the embodiment of the present disclosure, when the user terminal receives the PDCP re-establishment instruction, or when the higher layer instructs the PDCP re-establishment, it can determine whether the above-mentioned current bearer transmission mode is the confirmed mode, the configuration file meets the preset conditions, and the current bearer includes If the three conditions of the preset data packet are met at the same time, the user terminal can send at least one first complete data packet to the base station, where each first complete data packet includes: context information, uncompressed header information, and The first serial number, where the context information, is the context information reset by the user terminal after obtaining the packet data convergence protocol reconstruction instruction. For example, the user terminal can update the existing context information, or reset the existing context information, context information At least the context identifier is included; the first sequence number is any sequence number that the base station has not used in the bearer session.

It should be noted that before the user terminal resets the context information, the user terminal has sent a complete data packet and a compressed packet to the base station. The context form and content in the complete data packet and the compressed packet may be different, which is received at the user terminal. After the rebuild instruction, it is reset or updated according to the context in the original complete data packet to obtain the reset context information.

It should be understood that, under the condition that the existing communication protocol is unchanged, after receiving the PDCP re-establishment instruction, if the sequence number included in the complete data packet sent by the user terminal to the base station is the sequence number that the base station has received in the current bearer, For example, the sequence number is the last SN carried in the PDCP status report. At this time, after receiving the complete data packet, the base station determines that the sequence number in the complete data packet has been received, and will use the existing protocol to determine the complete data packet. The packet is discarded. Therefore, in this disclosure, in order to prevent the base station from directly discarding the complete data packet without further checking or obtaining the information in it, resulting in the inability to obtain and/or store valid context information, the user terminal sends the complete data packet to the base station. The sequence number can be a sequence number that the base station has not received in the current bearer, thereby ensuring that the base station successfully obtains the reset context information, so that the base station can use the reset context information to perform the compressed package sent by the user terminal. Normal decompression processing ensures the normal transmission of data.

In the embodiment of the present disclosure, when there is a preset data packet that has not been successfully sent, and the preset data packet is not a lost data packet (such as a confirmed reception failure or a NACK packet), the user terminal can also According to the existing manner, the third complete data packet is sent to the base station, where the third complete data packet includes uncompressed header information and the third sequence number in the preset data packet.

In the embodiment of the present disclosure, under the condition that the existing communication protocol remains unchanged, since the third complete data packet has the preset third sequence number of the data packet, that is, the sequence number used before reconstruction, if the user terminal only sends the third sequence number Complete data packet, after the base station receives the third complete data packet, according to the third sequence number in the third complete data packet, it can be determined that the data packet corresponding to the third sequence number has been received, and the base station may directly delete the first data packet. Three complete data packets, resulting in the inability to obtain and/or store valid (or new) context information. Therefore, in order to avoid the above problem, the user terminal may also send at least one first complete data packet to the base station, where the first complete data packet contains any sequence number that the base station has not received in the bearer, that is, the first sequence number, so that the base station After receiving the first complete data packet, according to the first sequence number, it can be determined that the corresponding data packet has not been received. At this time, the base station can analyze the received complete data packet, obtain and store the PDCP The context information reset after the instruction is reconstructed, so that the compressed package sent by the user terminal can be decompressed according to the reset context information subsequently to ensure normal data transmission.

As an example, the sequence number is SN, and SN is an example of sequential generation. When the transmission mode of the current bearer is the confirmation mode, when the user terminal receives the PDCP re-establishment instruction, it determines that the PDCP PDU that has been sent to the base station contains The last SN is SN=20, and the PDCP PDU with SN of 15, 17, 18, 20 is not successfully transmitted (for example, it can be determined according to the PDCP status report), and drb-ContinueROHC is not configured, then the user terminal resets the header compression context information (New or valid context information), reset the header compression state, and use the new context information to resend PDCP PDU with SN 15, 17, 18, 19, 20 (SN number is still the original 15, 17, 18 , 20). After the user terminal uses SN=21 (the first sequence number) to send a new complete data packet containing the new context information and the complete header, the user terminal can send the compressed packet thereafter.

It should be noted that when the preset data packet is a lost data packet, the serial number corresponding to the lost data packet is not received by the base station, but is the serial number used or sent by the user terminal. At this time, the user terminal sends The first sequence number in the first complete data packet sent by the base station may specifically be the third sequence number in the preset data packet.

As another example, when the current bearer transmission mode is the confirmation mode, when the user terminal receives the PDCP re-establishment instruction, it determines that the SN 19 of the PDCP PDUs that have been sent to the base station is missing, and drb-ContinueROHC is not configured. Then the user terminal resets the header compression context information (new or valid context information), resets the header compression state, and retransmits the PDCP PDU with SN 19 using the new context information. After the user terminal uses SN=19 (the third sequence number) to send a new complete data packet containing the new context information and the complete header, the user terminal can send the compressed packet thereafter.

As another example, when the current bearer transmission mode is the confirmation mode, when the user terminal receives the PDCP re-establishment instruction, it determines that the last SN contained in the PDCP PDU that has been sent to the base station is SN=20, and the SN is 15. The PDCP PDU of 17, 18, 20 is not successfully transmitted, the PDU of SN is 19 is missing, and drb-ContinueROHC is not configured, then the user terminal resets the header compression context information (new or valid context information) and resets the header compression Status, and use the new context information to resend the PDCP PDU with SN of 15, 17, 18, 19, 20 (the SN number is still the original 15, 17, 18, 20). When the user terminal uses SN=19 (third sequence number) and/or SN=21 (first sequence number) to send a new complete data packet containing new context information and a complete header, the user terminal sends the compressed packet thereafter.

That is, when the preset data packet is a lost data packet, the user terminal may only send the first complete data packet to the base station, and the first sequence number included in the first complete data packet may specifically refer to the first sequence number in the preset data packet. Three serial numbers. When the preset data packet is a non-lost data packet, the user terminal may send the first complete data packet and the third complete data packet to the base station. The third complete data packet includes uncompressed header information and the preset data packet The third sequence number.

Further, in order to ensure that the base station obtains the corresponding context information, the number of first complete data packets may be multiple, and the first sequence number included in each first complete data packet may be different. For example, a certain SN that is not used by the user terminal and the K subsequent SNs of the SN can be used, and each SN is used as a first sequence number, so that the user terminal can send K+1 first complete data packets to the base station to Enable the base station to successfully receive the reset context information. That is, there may be multiple first complete data packets sent by the user terminal to the base station, and the first sequence number corresponding to each first complete data packet is different. When the user terminal sends each first complete data packet to the base station, the base station For the first complete data packet, it can be determined that the first sequence number in the first complete data packet is a sequence number that has not been received in the current bearer. Therefore, the valid context information in the first complete data packet will be saved so that the base station can Successfully received the reset context information.

It should be noted that the number of third complete data packets is the same as the number of preset data packets, that is, before the reconstruction, several data packets failed to be sent, and after receiving the PDCP reconstruction instruction, the failed data packets are sent Both can be sent again to ensure the reliability and effectiveness of data transmission. In addition, the third complete data packet may include the reset context information, or may not include the reset context information. It should be understood that if the protocol of the base station is not modified, the base station will directly discard the data packet after receiving the data packet containing the repeated sequence number. Therefore, even if the third complete data packet contains the reset context information, It may also be discarded. Therefore, in the present disclosure, in order to reduce the number of bits of the data packet, the third complete data packet may not include the reset context information.

It should be noted that the third complete data packet may or may not include the reset context information. It should be understood that if the protocol of the base station is not modified, if the base station receives a data packet containing the third sequence number, it is determined that the SN corresponding to the data packet has not been received (for example, the PDU of the corresponding SN is a missing data packet), Then the base station will save the PDU and save the context information. At this time, the base station can obtain and store the context information reset by the user terminal after obtaining the PDCP reconstruction instruction, so that the compressed package sent by the user terminal can be subsequently decompressed according to the context information to ensure normal data transmission. Further, in order to ensure that the base station obtains the corresponding context information, the user terminal may also send the first complete data packet. The number of the first complete data packet is a non-negative integer.

In addition, the base station may send a feedback packet to the user terminal after saving the updated context information. After the user terminal receives the feedback package, it can start sending the compressed package.

As a possible implementation manner, under the condition that the protocol of the base station is not modified, when the base station receives the third complete data packet, and/or, at least one first complete data packet, the base station can determine the received complete data packet Whether there is a sequence number that has been received in the current bearer in the current bearer, if not, the reset context information in the complete data packet can be stored. Further, the base station sends a feedback packet to the user terminal, and the feedback packet may be sent after the base station determines that a complete data packet containing the context information is received; or the feedback packet may be sent after the base station saves the context information. Correspondingly, after receiving the feedback packet sent by the base station, the user terminal may send a compressed packet to the base station, where the compressed packet includes: context information, which is reset after the user terminal obtains the packet data convergence protocol reconstruction instruction Context information, so that the base station can decompress the compressed package based on the reset context information to ensure normal data transmission.

As a possible implementation, when the base station’s protocol is modified, when the base station receives the third complete data packet and/or at least one first complete data packet, the base station can determine whether the received complete data packet exists If the sequence number has been received in the current bearer, the reset context information in the complete data packet can be stored. Further, the base station sends a feedback packet to the user terminal, and the feedback packet may be sent after the base station determines that a complete data packet containing the context information is received; or the feedback packet may be sent after the base station saves the context information. Correspondingly, after receiving the feedback packet sent by the base station, the user terminal may send a compressed packet to the base station, where the compressed packet includes: context information, which is reset after the user terminal obtains the packet data convergence protocol reconstruction instruction Context information, so that the base station can decompress the compressed package based on the reset context information to ensure normal data transmission.

As a possible implementation, after a preset period of time after the user terminal receives the PDCP re-establishment instruction, it can default to the base station having received the complete data packet containing the context information, or the default base station has saved the reset context information At this time, the user terminal may send a compressed package to the base station, where the compressed package includes context information, and the context information is context information reset by the user terminal after obtaining the packet data convergence protocol reconstruction instruction.

Specifically, after the first preset time interval, the user terminal may send the compressed packet to the base station. For example, assuming that the first preset time interval is 2 seconds, the user terminal receives the PDCP re-establishment instruction at 10:00:00, and it can be considered that the PDCP re-establishment process is completed at 10:00:02. At this time, the user terminal The compressed package can be sent to the base station.

As a possible implementation, after the user terminal completes the PDCP reconstruction process, it can send a PDCP reconstruction complete message to the upper or higher layers, and after sending the PDCP reconstruction complete message for a second preset time interval, it can send a compressed packet to the base station, Wherein, the compressed package includes context information, and the context information is context information reset after the user terminal obtains the packet data convergence protocol reconstruction instruction.

As an example, the processing flow of the upstream data packet is illustrated (the compression end is the user terminal, the decompression end is the base station), and the processing of the downlink data packet (the compression end is the base station, and the decompression end is the user terminal) is similar. Do not repeat them here.

1. The Ethernet header compression parameters can be configured for the first DRB on the network side, where drb-ContinueROHC is not configured or its value is false. Specifically, the message is indicated to the user terminal through a dedicated RRC, such as PDCP-config IE.

2. The user terminal performs header compression processing according to the configuration information during subsequent transmissions. Specifically, the user terminal sends a complete data packet containing complete header information and context information, and after receiving a feedback packet or sending N complete data packets, it sends a compressed packet to the base station.

3. The base station receives the PDCP PDU from the user terminal, including complete data packets and compressed packets.

4. When the user terminal (UE) receives a PDCP re-establishment instruction from a higher layer (such as the RRC layer), or when a higher layer instructs PDCP re-establishment (for example, when the UE RRC receives a re-establishment instruction from the base station, the UE RRC requires the UE PDCP layer to perform PDCP During reconstruction), if the transmission mode of the current bearer is the confirmed mode, the configuration file meets the preset condition, and the current bearer includes the preset data packet, the user terminal sends the complete data packet.

For example, when the current bearer transmission mode is the confirmation mode, when the user terminal receives the PDCP re-establishment instruction, it determines that the last SN contained in the PDCP PDU that has been sent to the base station is SN=20, and the SN is 15, 17, 18 , The PDCP PDU of 20 is not successfully transmitted (for example, it can be determined according to the PDCP status report), and drb-ContinueROHC is not configured, then the user terminal resets the header compression context information (new or valid context information) and resets the header compression state, And use the new context information to resend the PDCP PDU with SN of 15, 17, 18, 20 (third sequence number) (the SN is still the original 15, 17, 18, 20). After the user terminal uses SN=21 (first sequence number) to send a new complete data packet containing the new context information and the complete header, the user terminal sends the compressed packet thereafter.

For another example, when the current bearer transmission mode is the confirmation mode, when the user terminal receives the PDCP re-establishment instruction, it determines that the last SN contained in the PDCP PDU sent to the base station is SN=20, and drb-ContinueROHC is not configured. Then the user terminal resets the header compression context information (new or valid context information), resets the header compression state, and retransmits the unconfirmed PDU using the new context information. When the user terminal uses SN=21 to send a new complete data packet containing new context information and a complete header, and receives a feedback packet from the base station, the user terminal sends a compressed packet.

For another example, when the current bearer transmission mode is the confirmation mode, when the user terminal receives the PDCP re-establishment instruction, it determines that the last SN contained in the PDCP PDU that has been sent to the base station is SN=20, and the SN is 15, 17. The PDCP PDU of 18, 20 is not successfully transmitted (for example, it can be determined according to the PDCP status report), the PDU of SN is 19 is missing, and drb-ContinueROHC is not configured, then the user terminal resets the header compression context information (new or valid context information) ), reset the header compression state, and use the new context information to resend the PDCP PDU with SN 15, 17, 18, 19, 20 (the third sequence number) (the SN number is still the original 15, 17, 18, 20) . When the user terminal uses SN=19 (third sequence number) and/or SN=21 (first sequence number) to send a new complete data packet containing new context information and a complete header, the user terminal sends the compressed packet thereafter.

5. After the PDCP reconstruction request is received, the base station receives the complete data packet sent by the user terminal, obtains the new context information, and saves it, so that the new context information can be subsequently used to decompress the compressed packet.

That is to say, referring to Figure 2, when the user terminal receives the PDCP re-establishment instruction from the higher layer, if it also meets the current bearer transmission mode, the confirmation mode, the configuration file meets the preset conditions, and the current bearer includes preset data packets. If conditions are met, the user terminal can send uncompressed PDCP PDUs to the base station, where the uncompressed PDCP PDUs are complete data packets, including the third complete data packet and/or at least one first complete data packet. When the data packet is a lost data packet, the first complete data packet is sent, and the first sequence number in the first complete data packet is the sequence number corresponding to the lost data packet, and when the preset data packet is a non-lost data packet , Send the first complete data packet and the third complete data packet. If the transmission mode of the current bearer is the confirmed mode, the configuration file meets the preset condition, and the current bearer includes the preset data packet, one of the three conditions is not met, the user terminal sends the compressed packet to the base station.

Alternatively, the base station may also send a feedback packet to the user terminal after saving the updated context information. Correspondingly, after the user terminal receives the feedback packet, the user terminal can start sending the compressed packet to the base station.

In order to implement the foregoing embodiment, the present disclosure also proposes a method for compressing the header of an Ethernet frame.

FIG. 3 is a schematic flowchart of the method for compressing the header of an Ethernet frame provided by the second embodiment of the disclosure.

As shown in FIG. 3, the method for compressing the header of an Ethernet frame may include the following steps:

The method for compressing the header of an Ethernet frame in the embodiment of the present disclosure may be applied to a base station, and the base station may specifically be a decompression end, that is, a PDCP receiving entity. Correspondingly, the sending end (compression end, PDCP sending entity) is the user terminal.

Of course, in another implementation manner, the Ethernet frame header compression processing method can be applied to the user terminal, and the base station is the compression end, that is, the PDCP sending entity. Correspondingly, the receiving end (decompression end, PDCP receiving entity) is the user terminal.

The following mainly uses the decompression end to which the method for compressing the header of the Ethernet frame is applied as the base station. The method for decompressing the terminal as the user terminal is similar.

Step 201: When the packet data convergence protocol reconstruction request is obtained, if the transmission mode of the current session is the confirmed mode, the configuration file meets the preset conditions, and the first sequence number in the first complete data packet obtained from the user terminal is If the base station has not received a sequence number in the current bearer, it saves the context information in the first complete data packet, so as to perform decompression processing on the new compressed packet according to the context information in the first complete data packet.

The first complete data packet is sent by the user terminal to the base station after obtaining the packet data convergence protocol reconstruction instruction.

In the embodiment of the present disclosure, the first sequence number in the first complete data packet is any sequence number that the base station has not received in the current bearer. Among them, the sequence number that the base station has not received in the current bearer, that is, the first sequence number may be the user The sequence number that has not been used by the terminal, or may also be the sequence number used by the user terminal, but the sequence number is the sequence number in the missing data packet (missing PDU), which is not limited. Among them, the first serial number may be a serial number (SN), or the first serial number may also be a count (COUNT). Among them, COUNT occupies 32 bits and is composed of Hyper Frame Number (HFN) and PDCP SN, and SN is the low bit of COUNT.

In the embodiments of the present disclosure, when the base station receives the PDCP re-establishment request, or when the higher layer instructs the PDCP re-establishment, it can determine whether the transmission mode of the current session is the confirmation mode, the configuration file meets the preset conditions, and the information obtained from the user terminal The first sequence number in the first complete data packet is the three conditions of the sequence number that the base station has not received in the current bearer. If the three conditions are met at the same time, the base station can save the context information in the first complete data packet, so that the base station can save the context information in the first complete data packet. The context information in a complete data packet is decompressed. Among them, the first complete data packet corresponding to the first sequence number is received after the base station receives the PDCP reconstruction request from the upper layer, or the first complete data packet is received from the lower layer again due to PDCP.

Specifically, when the user terminal receives the PDCP re-establishment instruction, or when the higher layer instructs the PDCP re-establishment, it can determine whether the transmission mode of the current bearer is the confirmation mode, the configuration file meets the preset conditions, and the current bearer includes preset data. If the three conditions of the packet are met at the same time, the user terminal can send at least one first complete data packet to the base station, where each first complete data packet can include context information, uncompressed header information, and a first sequence number, The context information is context information reset after the user terminal obtains the PDCP re-establishment instruction, and the first sequence number is any sequence number that the base station has not received in the bearer. Among them, the preset data packet may be a data packet that the user terminal fails to send before obtaining the reconstruction instruction, or the preset data packet may be a data packet that the user terminal does not obtain a successful transmission confirmation or an unconfirmed transmission status when the user terminal obtains the reconstruction instruction. Or, the preset data packet may also be a data packet lost when the user terminal obtains the reconstruction instruction, or the preset data packet may also be a data packet lost before the user terminal obtains the reconstruction instruction, which is not limited in the present disclosure . For example, the preset data packet may be confirmed according to the PDCP status report, where the preset data packet may include at least one of the following: PDUs that have been successfully transmitted, PDUs that have not been successfully transmitted, missing PDUs, and transmission status Uncertain PDU.

Correspondingly, after receiving the first complete data packet, the base station determines that the corresponding data packet has not been received according to the first sequence number. At this time, the base station can parse the received complete data packet, obtain and store the user terminal information. The context information reset after the PDCP reconstruction request is obtained, so that the new compressed package sent by the user terminal can be decompressed according to the context information subsequently to ensure normal data transmission.

In the embodiment of the present disclosure, when there is a preset data packet that has not been successfully sent, and the preset data packet is not a lost data packet (such as a packet that confirms reception failure or NACK), the user terminal can also follow the existing In this manner, a third complete data packet is sent to the base station, where the third complete data packet includes uncompressed header information and the third sequence number in the preset data packet.

That is to say, in the present disclosure, under the condition that the existing communication protocol remains unchanged, since the third complete data packet has the preset third sequence number of the data packet, that is, the sequence number used before reconstruction, if the user terminal only sends the The third complete data packet, after the base station receives the third complete data packet, according to the third sequence number in the third complete data packet, it can be determined that the data packet corresponding to the third sequence number has been received, and the base station may delete it directly The third complete data packet makes it impossible to obtain and/or store valid (or new) context information. Therefore, in order to avoid the above problem, the user terminal may also send at least one first complete data packet to the base station, where the first complete data packet contains any sequence number that the base station has not received in the bearer, that is, the first sequence number, so that the base station After receiving the first complete data packet, according to the first sequence number, it can be determined that the corresponding data packet has not been received. At this time, the base station can analyze the received complete data packet, obtain and store the PDCP The context information reset after the instruction is reconstructed, so that the new compressed package sent by the user terminal can be decompressed according to the context information subsequently to ensure the normal transmission of data.

As an example, the sequence number is SN, and SN is an example of sequential generation. When the transmission mode of the current bearer is the confirmation mode, when the user terminal receives the PDCP re-establishment instruction, it determines that the PDCP PDU that has been sent to the base station contains The last SN is SN=20, and the PDCP PDU with SN of 15, 17, 18, 20 is not successfully transmitted (for example, it can be determined according to the PDCP status report), and drb-ContinueROHC is not configured, then the user terminal resets the header compression context information (New or valid context information), reset the header compression state, and use the new context information to resend PDCP PDU with SN 15, 17, 18, 19, 20 (SN number is still the original 15, 17, 18 , 20). After the user terminal uses SN=21 (first sequence number) to send a new complete data packet containing the new context information and the complete header, the user terminal sends the compressed packet thereafter.

As another example, when the current bearer transmission mode is the confirmation mode, when the user terminal receives the PDCP re-establishment instruction, it determines that the SN 19 of the PDCP PDUs that has been sent to the base station is missing, and drb-ContinueROHC is not configured. Then the user terminal resets the header compression context information (new or valid context information), resets the header compression state, and retransmits the PDCP PDU with SN 19 using the new context information. When the user terminal uses SN=19 (the third sequence number) to send a new complete data packet containing the new context information and the complete header, the user terminal sends the compressed packet thereafter.

Further, in order to ensure that the base station obtains the corresponding context information, the number of first complete data packets may be multiple, and the first sequence number included in each first complete data packet may be different. For example, a certain SN that is not used by the user terminal and the K subsequent SNs of the SN can be used, and each SN is used as a first sequence number, so that the user terminal can send K+1 first complete data packets to the base station to Enable the base station to successfully receive the reset context information. That is, there may be multiple first complete data packets sent by the user terminal to the base station, and the first sequence number corresponding to each first complete data packet is different. When the user terminal sends a first complete data packet to the base station each time, the base station For the first complete data packet, it can be determined that the first sequence number in the first complete data packet is a sequence number that has not been received in the current bearer. Therefore, the valid context information in the first complete data packet will be saved so that the base station can Successfully received the reset context information.

In addition, the base station can send a feedback packet to the user terminal after saving the updated context information. After the user terminal receives the feedback package, it can start sending the compressed package.

FIG. 4 is a schematic flowchart of the method for compressing the header of an Ethernet frame provided by the third embodiment of the disclosure.

As shown in FIG. 4, the method for compressing the header of an Ethernet frame may include the following steps:

Of course, in another implementation manner, the Ethernet frame header compression processing can be applied to the user terminal, and the base station is the compression end, that is, the PDCP sending entity. Correspondingly, the receiving end (decompression end, PDCP receiving entity) is the user terminal.

The following description mainly takes the decompression end of the Ethernet frame header compression processing as the base station. The method for decompressing the terminal as the user terminal is similar.

Step 301: When the packet data convergence protocol reconstruction request is obtained, if the transmission mode of the current session is the confirmed mode, the configuration file meets the preset conditions, and the second sequence number in the second complete data packet obtained from the user terminal is The sequence number that the base station has received in the current bearer saves the context information in the second complete data packet.

In the embodiment of the present disclosure, the second serial number may be a serial number (SN), or the second serial number may also be a count (COUNT). Among them, COUNT occupies 32 bits and consists of HFN and PDCP SN, and SN is the low bit of COUNT.

In the embodiments of the present disclosure, when the base station receives the PDCP re-establishment request, or when the higher layer instructs the PDCP re-establishment, it can determine whether the transmission mode of the current session is the confirmation mode, the configuration file meets the preset conditions, and the information obtained from the user terminal is also satisfied. The second sequence number in the second complete data packet is the sequence number that the base station has received in the current bearer or the repeated sequence number (for example, repeated SN, that is, duplicate SN). If these three conditions are met at the same time, the base station can save the first sequence number. The context information in the second complete data packet, so that subsequent decompression processing can be performed according to the context information in the second complete data packet. The third complete data packet corresponding to the second sequence number is received after the base station receives the PDCP reconstruction request from the upper layer, or the second complete data packet is received from the lower layer again due to PDCP.

That is to say, you can modify the protocol of the base station (that is, the receiving end or the decompression end). When the PDCP reconstruction request is received, if the sequence number in the complete data packet received by the base station is the one previously received, the complete data packet is saved Therefore, the subsequent base station can perform decompression processing on the compressed packet sent by the user terminal according to the context information to ensure the normal transmission of data.

In addition, the base station can send a feedback packet to the user terminal after saving the context information. After the user terminal receives the feedback package, it can start sending the compressed package.

According to the method for compressing the header of the Ethernet frame in the embodiment of the present disclosure, when the base station obtains the packet data convergence protocol reconstruction request, if the transmission mode of the current session is the confirmation mode, and the configuration file meets the preset conditions, and the first obtained from the user terminal 2. The second sequence number in the second complete data packet is a sequence number that the base station has received in the current bearer, and the context information in the second complete data packet is saved. In this way, it can be ensured that the base station successfully obtains the reset context information, so that the base station can perform normal decompression processing on the compressed packet sent by the user terminal to ensure normal data transmission.

As a possible implementation manner, the base station saves the context information in the second complete data packet, or the base station uses the context information to successfully decompress the received compressed packet, or, when the base station has valid context information, the base station returns A feedback packet can be sent to the user terminal, where the feedback packet is used to indicate that the context information in the second complete data packet has been saved, or used to indicate that the base station has successfully decompressed the received compressed packet, or Indicates that the base station has valid context information.

As a possible implementation manner, in order to prevent the base station from repeatedly storing the same context information, before the base station saves the context information in the second complete data packet, it is also necessary to determine that the context information in the second complete data packet is not stored in the base station. That is to say, it is determined that the context information stored in the base station is stored before the PDCP reconstruction request is obtained, so that when the context information in the second complete data packet is saved, it can be determined that there is no repeated context in the stored data. information.

As a possible implementation, after the base station stores the context information in the second complete data packet, if the sequence number in the complete data packet sent by the user terminal to the base station, such as SN, the base station has already received it in the current bearer. If the sequence number is displayed, the complete data packet is discarded. Specifically, after the base station stores the context information in the second complete data packet, if the third sequence number in the third complete data packet newly acquired by the base station from the user terminal is the sequence number that the base station has received in the current bearer, Then the third complete data packet is discarded.

In the embodiment of the present disclosure, after the base station stores the context information in the second complete data packet, the existing protocol can be used to receive and store the data. Specifically, when the complete data packet received by the base station contains a previously received sequence number, the data packet may be discarded. That is to say, in the present disclosure, if the sequence number in the data packet subsequently received by the base station is the sequence number that the base station has received in the current bearer, the base station can use the existing protocol to discard the data packet.

As a possible implementation, in order to prevent the base station from repeatedly storing the same context information, before the base station saves the context information in the second complete data packet, it is also necessary to make sure that the base station does not send a feedback packet to the user terminal after obtaining the PDCP reconstruction request. , Where the feedback packet is used to indicate that the base station has successfully decompressed the acquired data packet, or the base station has reset context information, or the reset context information has been saved.

2. The user terminal performs header compression processing according to the configuration information during subsequent transmissions. Specifically, the user terminal sends a complete data packet containing complete header information and context information, and after receiving a feedback packet or sending N packets containing complete data packets, it sends a compressed packet to the base station.

4. When the user terminal (UE) receives a PDCP re-establishment request from a higher layer (such as the RRC layer), for example, when the UE RRC receives a re-establishment request from the base station, and the UE RRC requires the UE to perform PDCP re-establishment at the PDCP layer, the current bearer transmission The mode is the confirmation mode. The user terminal resets the context information, resets the header compression state, and sends the PDCP PDU according to the new context information.

5. When the PDCP re-establishment request is received or when the higher layer instructs PDCP re-establishment, the base station receives the data packet sent by the user terminal, obtains and saves the new context information. Specifically, after the base station receives the PDCP re-establishment request, the current bearer transmission mode is the confirmation mode. When the SN corresponding to the received PDCP PDU is a duplicate SN or an SN that has been received before re-establishment, perform at least one of the following operations One:

1) Decompress the PDCP PDU;

2) Save valid (new) context information. Specifically, if the PDCP PDU is a complete data packet, and/or the PDCP PDU has complete header information and context information, the base station considers the context contained therein as a valid (new) context and/or saves the context;

3) Send a feedback packet to the user terminal, where the feedback packet is used to indicate that valid context information has been successfully established and/or saved.

Otherwise, the user terminal will use the existing protocol, that is, when the SN in the PDCP PDU is an SN that has been received, the base station discards the PDCP PDU.

After that, the base station can perform decompression processing according to the saved new context information. In particular, when a feedback packet needs to be sent, the feedback packet sent by the base station is used to indicate that the base station has received and/or saved valid context information. When the user terminal receives the feedback package, it can send the compressed package.

For example, the transmission mode of the current session is the confirmation mode. After receiving the PDCP re-establishment request, the base station receives the PDCP PDU with SN of 10, and the data packet corresponding to the SN has been received before, because drb-ContinueROHC is not configured , And the base station does not have a valid context at this time, the base station decompresses the PDU with a SN of 10. When it is determined that this PDU is a complete data packet, or that there is complete header information and context information in this PDCP PDU, the base station considers the context contained in it to be valid (new) context information, and the base station will save the context for subsequent reception. Decompress when the package is compressed. In addition, if a PDU with an SN of 11 is subsequently received, and the data packet corresponding to the SN has been received before, since there is already valid context information at this time, the base station will use the existing protocol to discard the data packet deal with.

In order to implement the above-mentioned embodiment, the present disclosure also proposes an Ethernet frame header compression processing device.

FIG. 5 is a schematic structural diagram of an Ethernet frame header compression processing apparatus provided by the fourth embodiment of the disclosure.

The device for compressing the header of an Ethernet frame in the embodiment of the present disclosure may be provided in a user terminal, and the user terminal may specifically be a compression end, that is, a PDCP sending entity. Correspondingly, the receiving end (decompression end, PDCP receiving entity) is a base station.

Of course, in another implementation manner, the Ethernet frame header compression processing device can be set on the base station side, that is, the base station is the compression end, that is, the PDCP sending entity. Correspondingly, the receiving end (decompression end, PDCP receiving entity) is the user terminal.

The following description mainly uses the compression end where the Ethernet frame header compression processing device is set as the user terminal. The device where the compression end is the base station is similar.

As shown in FIG. 5, the device for compressing the header of an Ethernet frame includes a sending module 501.

Wherein, the sending module 501 is configured to, when the packet data convergence protocol re-establishment request is obtained, if the transmission mode of the current bearer is the confirmed mode, the configuration file meets the preset conditions, and the current bearer includes preset data packets, send a message At least one first complete data packet is sent.

Among them, each first complete data packet includes: context information, uncompressed header information, and a first sequence number. The context information is context information that is reset after the user terminal obtains the packet data convergence protocol reconstruction request. The first sequence number is any sequence number that the base station has not received in the bearer.

As a possible implementation, the preset data packet is the data packet that the user terminal fails to send before obtaining the reconstruction instruction, or the user terminal does not obtain the data of the successful transmission confirmation or the unconfirmed transmission status when the user terminal obtains the reconstruction instruction. A packet, or, is a data packet that is lost when the user terminal obtains the rebuild instruction or before the rebuild instruction is obtained.

As a possible implementation manner, the configuration file satisfies the preset conditions, including: the configuration parameter preset in the configuration file is not assigned a value; or the configuration parameter preset in the configuration file is assigned a value of false.

As a possible implementation, the sending module 401 is also configured to send a compressed package to the base station if the feedback package sent by the base station is acquired, where the compressed package includes: context information, which is the user terminal's The context information reset after the data convergence protocol rebuild request; where the feedback packet is sent by the base station after confirming that it receives a complete data packet containing the context information; or the feedback packet is sent after the base station saves the context information.

As a possible implementation, the sending module 401 is also configured to send a compressed packet to the base station after a first preset time interval, where the compressed packet includes: context information, which is that the user terminal obtains the packet Context information reset after the data aggregation protocol rebuild request.

As a possible implementation, after the second preset time interval of the packet data convergence protocol reconstruction complete message is sent, the compressed packet is sent to the base station, where the compressed packet includes context information, and the context information is that the user terminal obtains the packet Context information reset after the data aggregation protocol rebuild request.

As a possible implementation, the first serial number; or, the first serial number is a count.

It should be noted that the explanation of the method for compressing the header of the Ethernet frame in the foregoing embodiments of FIG. 1 to FIG. 2 is also applicable to the device for compressing the header of the Ethernet frame, and the implementation principle is similar, and will not be repeated here.

In the Ethernet frame header compression processing device of the embodiment of the present disclosure, when the user terminal obtains the packet data convergence protocol reconstruction request, if the transmission mode of the current bearer is the confirmed mode, and the configuration file meets the preset conditions, and the current bearer includes the preset Assuming a data packet, at least one first complete data packet is sent to the base station; where each first complete data packet includes: context information, uncompressed header information, and a first sequence number, where the context information is the user terminal After obtaining the context information reset after the packet data convergence protocol reconstruction request is obtained, the first sequence number is any sequence number that has not been used by the user terminal in the bearer session. In the present disclosure, the user terminal sends at least one first complete data packet to the base station. Since the first complete data packet includes a sequence number that the base station has not received in the bearer, it can ensure that the base station successfully obtains the reset context information, thereby enabling The base station performs normal decompression processing on the compressed packet sent by the user terminal to ensure the normal transmission of data.

FIG. 6 is a schematic structural diagram of an Ethernet frame header compression processing apparatus provided by Embodiment 5 of the present disclosure.

The Ethernet frame header compression processing apparatus in the embodiment of the present disclosure may be set in a base station, and the base station may specifically be a decompression end, that is, a PDCP receiving entity. Correspondingly, the sending end (compression end, PDCP sending entity) is the user terminal.

Of course, in another implementation manner, the Ethernet frame header compression processing device may be set on the user terminal side, and the base station is the compression terminal, that is, the PDCP sending entity. Correspondingly, the receiving end (decompression end, PDCP receiving entity) is the user terminal.

The following description mainly takes the decompression end where the Ethernet frame header compression processing device is installed as the base station. The device where the decompression end is the user terminal is similar.

As shown in FIG. 6, the device for compressing the header of an Ethernet frame includes: a saving module 601.

The saving module 601 is configured to, when the packet data convergence protocol reconstruction request is obtained, if the transmission mode of the current session is the confirmation mode, and the configuration file meets the preset conditions, and the first complete data packet obtained from the user terminal is the first The sequence number is a sequence number that the base station has not received in the current bearer, and the context information in the first complete data packet is saved, so as to decompress the new compressed packet according to the context information in the first complete data packet; A complete data packet is sent by the user terminal to the base station after obtaining the packet data convergence protocol reconstruction instruction.

It should be noted that the explanation of the method for compressing the header of an Ethernet frame in the foregoing embodiment of FIG. 3 is also applicable to the apparatus for compressing the header of an Ethernet frame, and the implementation principle is similar, and will not be repeated here.

FIG. 7 is a schematic structural diagram of an Ethernet frame header compression processing apparatus provided by the sixth embodiment of the disclosure.

As shown in FIG. 7, the device for compressing the header of an Ethernet frame includes: a saving module 701.

Wherein, the saving module 701 is configured to, when the packet data convergence protocol reconstruction request is obtained, if the transmission mode of the current session is the confirmation mode, and the configuration file meets the preset conditions, and the data in the second complete data packet obtained from the user terminal The second sequence number is the sequence number that the base station has received in the current bearer, and the context information in the second complete data packet is saved.

In a possible implementation as an embodiment of the present disclosure, referring to FIG. 8, based on the embodiment shown in FIG. 7, the method for compressing the header of an Ethernet frame may further include:

The sending module 702 is configured to send a feedback packet to the user terminal, and the feedback packet is used to indicate that the context information in the second complete data packet has been saved.

The determining module 703 is configured to determine that the context information in the second complete data packet is not stored in the base station.

The discarding module 704 is configured to discard the third complete data packet if the third sequence number in the third complete data packet newly acquired from the user terminal is the sequence number that the base station has already received in the current bearer.

As a possible implementation, the determining module 703 is also used to determine that the base station does not send a feedback packet to the user terminal after obtaining the packet data convergence protocol reconstruction request. The feedback packet is used to indicate that the base station decompresses the acquired data packet. Success, or the context information after reset exists in the base station, or the context information after reset has been saved.

It should be noted that the explanation of the method for compressing the header of an Ethernet frame in the foregoing embodiment of FIG. 4 is also applicable to the apparatus for compressing the header of an Ethernet frame, and the implementation principle is similar, and will not be repeated here.

In the Ethernet frame header compression processing device of the embodiment of the present disclosure, when the base station obtains the packet data convergence protocol reconstruction request, if the transmission mode of the current session is the confirmation mode, and the configuration file meets the preset conditions, and the first obtained from the user terminal 2. The second sequence number in the second complete data packet is a sequence number that the base station has received in the current bearer, and the context information in the second complete data packet is saved. In this way, it can be ensured that the base station successfully obtains the context information, so that the base station can perform normal decompression processing on the compressed packet sent by the user terminal according to the context information, so as to ensure the normal transmission of data.

In order to implement the above-mentioned embodiments, the present disclosure also proposes a user terminal, including: a memory, a processor, and a computer program stored on the memory and running on the processor. When the processor executes the program, the implementation is as described in Figure 1 of the present disclosure. To the method for compressing the header of the Ethernet frame proposed in the embodiment of FIG. 2.

In order to implement the above-mentioned embodiments, the present disclosure also proposes a base station, including: a memory, a processor, and a computer program stored on the memory and capable of running on the processor. When the processor executes the program, the implementation is as described in Figure 3 of the present disclosure. Example of the proposed method of compressing the header of the Ethernet frame.

In order to implement the above-mentioned embodiments, the present disclosure also proposes another base station, including: a memory, a processor, and a computer program stored in the memory and capable of running on the processor. When the processor executes the program, the implementation is as described above in the present disclosure. The Ethernet frame header compression processing method proposed in the embodiment.

In order to implement the above-mentioned embodiments, the present disclosure also proposes a computer-readable storage medium on which a computer program is stored, which is characterized in that, when the program is executed by a processor, the implementation is as described in the foregoing embodiments of FIG. 1 to FIG. 2 of the present disclosure. The method for compressing the header of an Ethernet frame, or implementing the method for compressing the header of an Ethernet frame as proposed in the embodiment of FIG. 3 of the present disclosure, or implementing the method of compressing the header of an Ethernet frame as proposed in the foregoing FIG. 4 embodiment of the present disclosure.

In the description of this specification, descriptions with reference to the terms "one embodiment", "some embodiments", "examples", "specific examples", or "some examples" etc. mean specific features described in conjunction with the embodiment or example , Structures, materials, or characteristics are included in at least one embodiment or example of the present disclosure. In this specification, the schematic representations of the above terms do not necessarily refer to the same embodiment or example. Moreover, the described specific features, structures, materials or characteristics may be combined in any one or more embodiments or examples in a suitable manner. In addition, those skilled in the art can combine and combine the different embodiments or examples and the features of the different embodiments or examples described in this specification without contradicting each other. In addition, the terms "first" and "second" are only used for descriptive purposes, and cannot be understood as indicating or implying relative importance or implicitly indicating the number of indicated technical features. Therefore, the features defined with "first" and "second" may explicitly or implicitly include at least one of the features. In the description of the present disclosure, "plurality" means at least two, such as two, three, etc., unless otherwise specifically defined.

Any process or method description described in the flowchart or described in other ways herein can be understood as a module, segment or part of code that includes one or more executable instructions for implementing custom logic functions or steps of the process , And the scope of the preferred embodiments of the present disclosure includes additional implementations, which may not be in the order shown or discussed, including performing functions in a substantially simultaneous manner or in the reverse order according to the functions involved. This should It is understood by those skilled in the art to which the embodiments of the present disclosure belong.

The logic and/or steps represented in the flowchart or described in other ways herein, for example, can be considered as a sequenced list of executable instructions for implementing logic functions, and can be embodied in any computer-readable medium, For use by instruction execution systems, devices, or equipment (such as computer-based systems, systems including processors, or other systems that can fetch and execute instructions from instruction execution systems, devices, or equipment), or combine these instruction execution systems, devices Or equipment. For the purposes of this specification, a "computer-readable medium" can be any device that can contain, store, communicate, propagate, or transmit a program for use by an instruction execution system, device, or device or in combination with these instruction execution systems, devices, or devices. More specific examples (non-exhaustive list) of computer readable media include the following: electrical connections (electronic devices) with one or more wiring, portable computer disk cases (magnetic devices), random access memory (RAM), Read-only memory, erasable and editable read-only memory (EPROM or flash memory), fiber optic devices, and portable CD-ROM read-only memory. In addition, the computer-readable medium may even be paper or other suitable medium on which the program can be printed, because it can be used, for example, by optically scanning the paper or other medium, followed by editing, interpretation, or other suitable media if necessary. The program is processed in a way to obtain the program electronically and then stored in the computer memory.

It should be understood that each part of the present disclosure can be implemented by hardware, software, firmware, or a combination thereof. In the above embodiments, multiple steps or methods can be implemented by software or firmware stored in a memory and executed by a suitable instruction execution system. For example, if it is implemented by hardware as in another embodiment, it can be implemented by any one or a combination of the following technologies known in the art: Discrete logic gate circuits with logic functions for data signals Logic circuits, application specific integrated circuits with suitable combinational logic gates, programmable gate arrays, field programmable gate arrays, etc. A person of ordinary skill in the art can understand that all or part of the steps carried in the method of the foregoing embodiments can be implemented by a program instructing relevant hardware to complete. The program can be stored in a computer-readable storage medium, and the program can be stored in a computer-readable storage medium. When executed, it includes one of the steps of the method embodiment or a combination thereof.

In addition, the functional units in the various embodiments of the present disclosure may be integrated into one processing module, or each unit may exist alone physically, or two or more units may be integrated into one module. The above-mentioned integrated modules can be implemented in the form of hardware or software function modules. If the integrated module is implemented in the form of a software function module and sold or used as an independent product, it can also be stored in a computer readable storage medium. The aforementioned storage medium may be a read-only memory, a magnetic disk or an optical disk, etc. Although the embodiments of the present disclosure have been shown and described above, it can be understood that the above-mentioned embodiments are exemplary and should not be construed as limiting the present disclosure. Those of ordinary skill in the art can comment on the foregoing within the scope of the present disclosure. The embodiment undergoes changes, modifications, substitutions, and modifications.

Claims

An Ethernet frame header compression processing method, applied to a user terminal, and characterized in that it includes:

When the packet data convergence protocol re-establishment instruction is obtained, if the transmission mode of the current bearer is the confirmed mode, and the configuration file meets the preset conditions, and the current bearer includes preset data packets, at least one first complete packet is sent to the base station data pack;

Wherein, each first complete data packet includes: context information, uncompressed header information, and a first sequence number, where the context information is the context reset after the user terminal obtains the packet data convergence protocol reconstruction instruction Information, the first sequence number is any sequence number that the base station has not received in the bearer.
The method of claim 1, wherein:

The preset data packet is a data packet that fails to be sent by the user terminal before acquiring the reconstruction instruction, or is a data packet that the user terminal does not obtain a successful transmission confirmation or an unconfirmed transmission status when the user terminal acquires the reconstruction instruction, Or, it is a data packet lost when the user terminal obtains the reconstruction instruction or before the reconstruction instruction is obtained.
The method of claim 1, wherein the configuration file satisfies a preset condition, comprising:

The configuration parameters preset in the configuration file are not assigned values;

or,

The preset configuration parameter assignment in the configuration file is false.
The method according to claim 1, wherein after the sending at least one first complete data packet to the base station, the method further comprises:

If the feedback packet sent by the base station is obtained, the compressed packet is sent to the base station, where the compressed packet includes: context information, and the context information is that the user terminal obtains the packet data convergence protocol reconstruction instruction Context information reset afterwards;

Wherein, the feedback packet is sent after the base station determines that a complete data packet containing context information is received; or, the feedback packet is sent after the base station saves the context information.
The method according to claim 1, wherein after obtaining the packet data convergence protocol reconstruction instruction, the method further comprises:

After the first preset time interval, send a compressed package to the base station, where the compressed package includes: context information, and the context information is that the user terminal restarts after obtaining the packet data convergence protocol reconstruction instruction Contextual information of the setting.
The method according to any one of claims 1-5, wherein after the sending at least one first complete data packet to the base station, the method further comprises:

After sending the packet data convergence protocol reconstruction complete message at a second preset time interval, the compressed packet is sent to the base station, wherein the compressed packet includes context information, and the context information indicates that the user terminal has acquired the packet Context information reset after the data aggregation protocol rebuild command.
5. The method according to any one of claims 1-6, wherein the first sequence number is a sequence number;

Alternatively, the first sequence number is a count.
A method for compressing the header of an Ethernet frame, applied to a base station, is characterized in that it includes:

When the packet data convergence protocol reconstruction request is obtained, if the transmission mode of the current session is the confirmation mode, the configuration file meets the preset conditions, and the first sequence number in the first complete data packet obtained from the user terminal is If the base station has not received a sequence number in the current bearer, then save the context information in the first complete data packet, so as to perform decompression processing on the new compressed packet according to the context information in the first complete data packet;

Wherein, the first complete data packet is sent by the user terminal to the base station after obtaining the packet data convergence protocol reconstruction instruction.
A method for compressing the header of an Ethernet frame, applied to a base station, is characterized in that it includes:

When the packet data convergence protocol reconstruction request is obtained, if the transmission mode of the current session is the confirmation mode, the configuration file meets the preset condition, and the second sequence number in the second complete data packet obtained from the user terminal is The sequence number that the base station has received in the current bearer saves the context information in the second complete data packet.
The method according to claim 9, wherein the configuration file satisfies a preset condition, comprising:

The configuration parameters preset in the configuration file are not assigned values;

or,

The preset configuration parameter assignment in the configuration file is false.
The method according to claim 9, wherein after the storing the context in the second complete data packet, the method further comprises:

Send a feedback packet to the user terminal, where the feedback packet is used to indicate that the context information in the second complete data packet has been saved.
The method according to any one of claims 9-11, wherein before storing the context information in the second complete data packet, the method further comprises:

It is determined that the context information in the second complete data packet is not stored in the base station.
The method according to claim 12, wherein after the saving the context information in the second complete data packet, the method further comprises:

If the third sequence number in the third complete data packet newly acquired from the user terminal is the sequence number that the base station has already received in the current bearer, then the third complete data packet is discarded.
The method according to any one of claims 9-13, wherein before storing the context information in the second complete data packet, the method further comprises:

It is determined that the base station does not send a feedback packet to the user terminal after obtaining the packet data convergence protocol reconstruction request. The feedback packet is used to indicate that the base station has successfully decompressed the obtained data packet, or the base station has been reset. The context information of the, or the context information after reset has been saved.
A device for compressing and processing Ethernet frame headers, which is arranged in a user terminal, and is characterized in that it includes:

The sending module is used to send to the base station if the transmission mode of the current bearer is the confirmed mode, the configuration file meets the preset condition, and the preset data packet is included in the current bearer when the packet data convergence protocol reconstruction instruction is obtained At least one first complete data packet;

Wherein, each first complete data packet includes: context information, uncompressed header information, and a first sequence number, where the context information is the context reset after the user terminal obtains the packet data convergence protocol reconstruction instruction Information, the first sequence number is any sequence number that the base station has not received in the bearer.
A device for compressing and processing Ethernet frame headers, which is set in a base station, and is characterized in that it includes:

The saving module is used to obtain the packet data convergence protocol reconstruction request, if the transmission mode of the current session is the confirmation mode, and the configuration file meets the preset condition, and the first complete data packet obtained from the user terminal A sequence number is a sequence number that the base station has not received in the current bearer, and then the context information in the first complete data packet is saved, so that the new compressed packet can be performed according to the context information in the first complete data packet. Decompression processing;

Wherein, the first complete data packet is sent by the user terminal to the base station after obtaining the packet data convergence protocol reconstruction instruction.
A device for compressing and processing Ethernet frame headers, which is set in a base station, and is characterized in that it includes:

The saving module is used to, when the packet data convergence protocol reconstruction request is obtained, if the transmission mode of the current session is the confirmation mode, and the configuration file meets the preset conditions, and the second complete data packet obtained from the user terminal is the first The second sequence number is the sequence number that the base station has received in the current bearer, and the context information in the second complete data packet is saved.
A user terminal, characterized by comprising: a memory, a processor, and a computer program stored in the memory and capable of running on the processor. When the processor executes the program, it can implement any of claims 1-7. 1. The method for compressing the header of the Ethernet frame.
A base station, characterized by comprising: a memory, a processor, and a computer program stored in the memory and running on the processor, and when the processor executes the program, the Ethernet frame according to claim 8 is implemented Packet header compression processing method.
A base station, characterized by comprising: a memory, a processor, and a computer program stored on the memory and capable of running on the processor, and when the processor executes the program, it implements any one of claims 9-14 The described Ethernet frame header compression processing method.
A computer-readable storage medium with a computer program stored thereon, characterized in that, when the program is executed by a processor, the Ethernet frame header compression processing method according to any one of claims 1-7 is realized, or The method for compressing the header of an Ethernet frame according to claim 8, or the method for compressing the header of an Ethernet frame according to any one of claims 9-14.