CN113711558A

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

Info

Publication number: CN113711558A
Application number: CN201980095284.8A
Authority: CN
Inventors: 付喆
Original assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Current assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date: 2019-09-30
Filing date: 2019-09-30
Publication date: 2021-11-26
Anticipated expiration: 2039-09-30
Also published as: CN113711558B; WO2021062690A1

Abstract

The present disclosure provides a method, an apparatus, a user terminal, a base station and a medium for compressing an ethernet frame header, wherein the method applied to the user terminal includes: when a packet data convergence protocol reconstruction instruction is obtained, if the transmission mode of the current bearer is a confirmation mode, the configuration file meets 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 header information and a first sequence number, the context information is context information reset by the user terminal after the user terminal acquires the packet data convergence protocol reconstruction instruction, and the first sequence number is any sequence number which is not received by the base station in the bearing process. Therefore, the base station can be ensured to successfully acquire the reset context information, and the normal transmission of data is ensured.

Description

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

Technical Field

The present disclosure relates to the field of data processing and network transmission technologies, and in particular, to a method and an apparatus for compressing an ethernet frame packet header, a user terminal, a base station, and a medium.

Background

At present, when a user terminal communicates with a base station, if a Packet Data Convergence Protocol (PDCP) reestablishment request is received, the user terminal needs to perform a PDCP reestablishment process, and perform normal Data transmission on a PDCP layer after the reestablishment process is performed.

However, if the configuration parameter drb-conteniuerohc in the configuration file is not assigned or is assigned as false, the user terminal resets the header compression context information when the transmission mode is the acknowledged mode and there is a Data packet that is not successfully transmitted before reconstruction, and correspondingly, the user terminal transmits a PDCP Protocol Data Unit (PDU) including complete header information and context information to the base station. If the transmitted data packet uses the Sequence Number (SN) of the PDCP PDU that was transmitted before and is reconstructed, the base station considers that the data packet corresponding to the SN has been received, and thus the base station directly deletes the PDCP PDU without further checking or acquiring the information therein, which results in the inability to acquire and/or store valid (new) header compression context information. Furthermore, the base station does not have valid header compression context information, which causes the problem that the compression packet sent by the subsequent user terminal cannot be decompressed, resulting in decompression failure and further data transmission failure.

BRIEF SUMMARY OF THE PRESENT DISCLOSURE

The present disclosure provides a method and an apparatus for compressing an ethernet frame packet header, a user terminal, a base station, and a medium, so as to ensure that the base station successfully obtains context information after being reset, so that the base station can perform normal decompression processing on a compressed packet sent by the user terminal, and ensure normal transmission of data, which is used to solve the technical problem in the prior art that the base station cannot perform decompression.

An embodiment of a first aspect of the present disclosure provides a method for compressing an ethernet frame header, which is applied to a user terminal, and includes:

when a packet data convergence protocol reconstruction instruction is obtained, if a transmission mode of a current bearer is a confirmation mode, the configuration file meets a preset condition, and the current bearer comprises a preset data packet, sending at least one first complete data packet to a base station;

wherein each first complete data packet comprises: the base station comprises context information, uncompressed header information and a first sequence number, wherein the context information is context information reset by the user terminal after acquiring a packet data convergence protocol reestablishment instruction, and the first sequence number is any sequence number which is not received by the base station in the bearing process.

According to the method for compressing the Ethernet frame packet header, when a user terminal obtains a packet data convergence protocol reconstruction instruction, if a transmission mode of a current bearer is a confirmation mode, a configuration file meets a preset condition, and the current bearer comprises a preset data packet, at least one first complete data packet is sent to a base station; wherein each first complete data packet comprises: the context information is context information reset after the user terminal obtains a packet data convergence protocol reestablishment instruction, and the first sequence number is any sequence number which is not received by the base station in the bearing process. In the disclosure, the user terminal sends at least one first complete data packet to the base station, and since the first complete data packet includes a serial number that is not received by the base station in the bearer, the base station can be ensured to successfully acquire the reset context information, so that the base station can perform normal decompression processing on a compressed packet sent by the user terminal, and normal transmission of data is ensured.

The embodiment of the second aspect of the present disclosure provides another ethernet frame header compression processing method, which is applied to a base station, and includes:

when a packet data convergence protocol reconstruction request is acquired, if a transmission mode of a current session is an acknowledgement mode and the configuration file meets a preset condition, and a first sequence number in a first complete data packet acquired from a user terminal is a sequence number which is not received by the base station in a current bearer, storing context information in the first complete data packet so as to decompress a new compressed packet according to the context information in the first complete data packet;

and the first complete data packet is sent to the base station after the user terminal acquires the packet data convergence protocol reconstruction instruction.

According to the method for compressing the Ethernet frame packet header, when a base station acquires a packet data convergence protocol reconstruction request, if a transmission mode of a current session is an acknowledgement mode and a configuration file meets a preset condition, and a first sequence number in a first complete data packet acquired from a user terminal is a sequence number which is not received by the base station in a current load, context information in the first complete data packet is stored, so that a new compressed packet is decompressed according to the context information in the first complete data packet; the first complete data packet is sent to the base station after the user terminal obtains the packet data convergence protocol reestablishment instruction. According to the method and the device, the base station can be ensured to successfully acquire the reset context information, so that the base station can perform normal decompression processing on the compressed packet sent by the user terminal, and normal transmission of data is ensured.

An embodiment of a third aspect of the present disclosure provides another ethernet frame header compression processing method, which is applied to a base station, and includes:

when a packet data convergence protocol reestablishment request is acquired, if the transmission mode of the current session is a confirmation mode, the configuration file meets a preset condition, and a second sequence number in a second complete data packet acquired from a user terminal is a sequence number already received by the base station in the current bearer, the context information in the second complete data packet is saved.

In the method for compressing the ethernet frame header according to the embodiment of the present disclosure, when the base station obtains the packet data convergence protocol reestablishment request, if the transmission mode of the current session is the acknowledged 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 has been received by the base station in the current bearer, the context information in the second complete data packet is saved. Therefore, the base station can be ensured to successfully acquire the context information, so that the base station can carry out normal decompression processing on the compressed packet sent by the user terminal, and normal transmission of data is ensured.

An embodiment of a fourth aspect of the present disclosure provides an ethernet frame packet header compression processing apparatus, which is disposed in a user terminal, and includes:

a sending module, configured to send at least one first complete data packet to a base station if a transmission mode of a current bearer is an acknowledgement mode, the configuration file meets a preset condition, and the current bearer includes a preset data packet when a packet data convergence protocol reestablishment instruction is obtained;

According to the device for compressing the Ethernet frame packet header in the embodiment of the disclosure, when a packet data convergence protocol reconstruction instruction is obtained through a user terminal, if a transmission mode of a current bearer is an acknowledgement mode, a configuration file meets a preset condition, and the current bearer includes a preset data packet, at least one first complete data packet is sent to a base station; wherein each first complete data packet comprises: the context information is context information reset after the user terminal acquires a packet data convergence protocol reestablishment instruction, and the first sequence number is any sequence number which is not used by the base station in the bearing. In the disclosure, the user terminal sends at least one first complete data packet to the base station, and since the first complete data packet includes a serial number that is not received by the base station in the bearer, the base station can be ensured to successfully acquire the reset context information, so that the base station can perform normal decompression processing on a compressed packet sent by the user terminal, and normal transmission of data is ensured.

An embodiment of a fifth aspect of the present disclosure provides another ethernet frame header compression processing apparatus, which is disposed in a base station, and includes:

a storage module, configured to, when a packet data convergence protocol reestablishment request is obtained, if a transmission mode of a current session is an acknowledged mode and the configuration file meets a preset condition, and a first sequence number in a first complete data packet obtained from a user terminal is a sequence number that has not been received by the base station in a current bearer, store context information in the first complete data packet, so as to decompress a new compressed packet according to the context information in the first complete data packet;

According to the ethernet frame header compression processing device of the embodiment, when a base station acquires a packet data convergence protocol reconstruction request, if a transmission mode of a current session is an acknowledgement mode and a configuration file meets a preset condition, and a first sequence number in a first complete data packet acquired from a user terminal is a sequence number which is not received by the base station in a current bearer, context information in the first complete data packet is stored, so that a new compression packet is decompressed according to the context information in the first complete data packet; the first complete data packet is sent to the base station after the user terminal obtains the packet data convergence protocol reestablishment instruction. According to the method and the device, the base station can be ensured to successfully acquire the reset context information, so that the base station can perform normal decompression processing on the compressed packet sent by the user terminal, and normal transmission of data is ensured.

An embodiment of a sixth aspect of the present disclosure provides another ethernet frame header compression processing apparatus, which is disposed in a base station, and includes:

and the storage module is used for storing the context information in the second complete data packet 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 acquired from the user terminal is the sequence number already received by the base station in the current bearer when the packet data convergence protocol reestablishment request is acquired.

In the ethernet frame header compression processing apparatus of the embodiment of the present disclosure, when the base station obtains the packet data convergence protocol reestablishment request, if the transmission mode of the current session is the acknowledged mode, and the configuration file satisfies the preset condition, and the second sequence number in the second complete data packet obtained from the user terminal is the sequence number that has been received by the base station in the current bearer, the context information in the second complete data packet is saved. Therefore, the base station can be ensured to successfully acquire the context information, so that the base station can carry out normal decompression processing on the compressed packet sent by the user terminal, and normal transmission of data is ensured.

A seventh embodiment of the present disclosure provides a user terminal, including: the device comprises a memory, a processor and a computer program stored on the memory and capable of running on the processor, wherein the processor executes the program to realize the Ethernet frame header compression processing method provided by the embodiment of the first aspect of the disclosure.

An eighth aspect of the present disclosure provides a base station, including: the device comprises a memory, a processor and a computer program stored on the memory and capable of running on the processor, wherein the processor executes the program to realize the Ethernet frame header compression processing method according to the embodiment of the second aspect of the disclosure.

An embodiment of a ninth aspect of the present disclosure provides a base station, including: the device comprises a memory, a processor and a computer program stored on the memory and capable of running on the processor, wherein the processor executes the program to realize the Ethernet frame header compression processing method provided by the embodiment of the third aspect of the disclosure.

A tenth aspect of the present disclosure provides a computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements a method for compressing an ethernet frame header as set forth in the first aspect of the present disclosure, or implements a method for compressing an ethernet frame header as set forth in the second aspect of the present disclosure, or implements a method for compressing an ethernet frame header as set forth in the third aspect of the present disclosure.

Additional aspects and advantages of the disclosure will be set forth in part in the description which follows and, in part, will be obvious from the description, or may be learned by practice of the disclosure.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present disclosure, the drawings needed to be used in the embodiments will be briefly described below, and it is obvious that the drawings in the following description are some embodiments of the present disclosure, and it is obvious for those skilled in the art to obtain other drawings without creative efforts.

Fig. 1 is a schematic flowchart of a method for compressing an ethernet frame header according to an embodiment of the present disclosure;

fig. 2 is a schematic view of an interaction flow between a user equipment and a base station in an embodiment of the present disclosure;

fig. 3 is a schematic flowchart of a second embodiment of the present disclosure of a method for compressing an ethernet frame header;

fig. 4 is a schematic flowchart of a processing method for compressing an ethernet frame header according to a third embodiment of the present disclosure;

fig. 5 is a schematic structural diagram of an ethernet frame header compression processing apparatus according to a fourth embodiment of the present disclosure;

fig. 6 is a schematic structural diagram of an ethernet frame header compression processing apparatus according to a fifth embodiment of the present disclosure;

fig. 7 is a schematic structural diagram of an ethernet frame header compression processing apparatus according to a sixth embodiment of the present disclosure;

fig. 8 is a schematic structural diagram of an ethernet frame header compression processing apparatus according to a seventh embodiment of the present disclosure.

Detailed Description

Reference will now be made in detail to the embodiments of the present disclosure, examples of which are illustrated in the accompanying drawings, wherein like or similar reference numerals refer to the same or similar elements or elements having the same or similar functions throughout. The embodiments described below with reference to the drawings are exemplary and intended to be illustrative of the present disclosure, and should not be construed as limiting the present disclosure.

In the 5G Industrial internet (IIoT for short), there is a demand for supporting the transmission of services such as Factory automation (Factory automation), transmission automation (Transport Industry), and intelligent Power (electric Power Distribution) in a 5G system. IIoT introduces the concept of time sensitive network TSN or TSC based on its transmission requirements of latency and reliability, and requires header compression processing for TSN traffic. The TSC traffic may be carried by Ethernet frames (Ethernet frames) or IP packets.

The introduction of the ethernet frame issue is because only header compression of the data packet with IP PDU session is supported in the existing communication system. In a New Radio over the air (NR) system of 5G, the type of PDU session may be not only an IP 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, abbreviated as Pv4) or IPv6 or IPv4v6, the PDU session is corresponding to an IPv4 data packet and/or an IPv6 data packet; when the PDU session type is Ethernet, the PDU session is corresponding to an Ethernet frame.

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

When the PDCP is reconstructed, if drb-conteinurohc is configured in the configuration file, it means that the previous RoHC information is used for compression and decompression after reconstruction. Otherwise, the compression and decompression states are reset, that is, the decompression end will not have valid context information and needs to receive new context information, the compression end needs to reset the compression state and send an uncompressed data packet containing the context information, that is, a complete data packet, to the decompression end.

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 a PDCP re-establishment procedure, and after performing the re-establishment procedure, performs normal data transmission of the PDCP layer. If drb-conteniuerohc is not configured or is false, in the reconstruction process, if the transmission mode is the acknowledgement mode, and if PDCP PDUs have been transmitted to the lower layer before reconstruction but have not received acknowledgement of successful transmission or unsuccessful transmission, the user terminal needs to use SNs used before PDCP reconstruction when transmitting or retransmitting these data packets, but use new header compression context information to transmit the data packets, i.e. delete the original context, reset the header compression state and context information, and use new context information to transmit PDCP PDUs. Then, after receiving the re-establishment request, the ue needs to send an uncompressed data packet containing new context information to the base station using the SN before re-establishment. Then, the corresponding PDCP PDU corresponding to the subsequent SN is transmitted.

The base station needs to process the PDCP PDU and subsequent PDUs received from the lower layer due to the re-establishment when it receives a PDCP re-establishment request from the upper layer. For the PDCP PDU received before the re-establishment request, the base station may decompress the original context information, and for the PDCP PDU received after the re-establishment request, the processing procedure includes: deleting the PDU with the same SN (i.e. when the base station receives a PDU, the base station directly discards the data packet without further checking the information in the packet when finding that the SN corresponding to the PDU is the SN received before), resetting the new context information, resetting the decompression state, decompressing according to the new context information, and reconstructing the new PDU received after the request.

However, if the configuration parameter drb-conteniuerochc in the configuration file is not assigned or is assigned as false, the user terminal resets the header compression context information when the transmission mode is the acknowledged mode and there is a data packet that is not successfully transmitted before reconstruction, and correspondingly, the user terminal transmits the PDCP PDU including the complete header information and the context information to the base station. If the transmitted data packet uses the Sequence Number (SN) of the PDCP PDU that was transmitted before and is reconstructed, the base station considers that the data packet corresponding to the SN has been received, and thus the base station directly deletes the PDCP PDU without further checking or acquiring the information therein, which results in the inability to acquire and/or store valid (new) header compression context information. Furthermore, the base station has no effective header compression context information, which results in that the compression packet sent by the subsequent user terminal cannot be decompressed, resulting in decompression failure and further data transmission failure.

Therefore, the present disclosure provides a method for compressing an ethernet frame header, mainly aiming at the technical problem that the base station cannot decompress the ethernet frame header.

The following describes an ethernet frame header compression processing method, apparatus, user terminal, base station, and medium according to an embodiment of the present disclosure with reference to the drawings. Before the embodiments of the present disclosure are described in detail, for the purpose of understanding, common technical terms of the present disclosure are first introduced:

header compression (header compression) is used to compress the header of a data packet and improve the transmission efficiency of user data. Currently, in Long Term Evolution (LTE) and NR, a PDCP layer performs header compression on a packet header by using RoHC.

A full packet (full packet) is an Ethernet packet (Ethernet packet), and the packet includes full Ethernet header information, context information, and the like, for example, a context ID, indication information (for indicating whether the packet is a compressed packet or a full packet), and other possible but undetermined uplink information, such as a profile ID. Wherein, the context information is used for compressing and/or decompressing the packet header. Specifically, after the compression end and the decompression end establish their context relationship, or the decompression end receives and stores valid context information (specifically, the valid context information includes a context identifier or indication and complete header information).

A compressed packet (Ethernet packet) is an Ethernet packet that includes compressed Ethernet header information (including no header information or only partial header information), context information, and the like.

Fig. 1 is a flowchart illustrating a method for compressing an ethernet frame header according to an embodiment of the present disclosure.

The ethernet frame header compression processing method of 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. Accordingly, the receiving end (decompression end, PDCP receiving entity) is the base station.

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

The following description mainly uses the compression end to which the ethernet frame header compression processing method is applied as the user terminal. The method of compressing the base station is similar to the method.

As shown in fig. 1, the ethernet frame header compression processing method may include the following steps:

step 101, when a packet data convergence protocol reestablishment instruction is obtained, if a transmission mode of a current bearer is a confirmation mode, a configuration file meets a preset condition, and the current bearer includes a preset data packet, sending at least one first complete data packet to a base station.

Wherein each first complete data packet comprises: the context information is context information reset after the user terminal obtains a packet data convergence protocol reestablishment instruction, and the first sequence number is any sequence number which is not received by the base station in the bearing process.

In the disclosed embodiment, the transmission mode may include a Transparent Mode (TM), an Unacknowledged Mode (UM), and an Acknowledged Mode (AM).

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

In this 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 a data packet that the user terminal does not obtain a successful sending confirmation or an unconfirmed sending state when obtaining the reconstruction instruction, or the preset data packet may also be a data packet that the user terminal loses before obtaining the reconstruction instruction, which is not limited by this disclosure. For example, a pre-set packet may be acknowledged according to the PDCP status report, wherein the pre-set packet may include at least one of: successfully transmitted PDUs, unsuccessfully transmitted PDUs, missing (missing) PDUs, PDUs whose transmission status is uncertain.

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

In this embodiment of the disclosure, the first sequence number in the first complete packet is any sequence number that is not received by the base station in the current bearer, where the sequence number that is not received by the base station in the current bearer is, that is, the first sequence number may be a sequence number that is not used by the user terminal, or may also be a sequence number that is used by the user terminal, but the sequence number is a sequence number in a lost packet (missing PDU), which is not limited to this.

As a possible implementation manner, when the sequence numbers are sequentially generated, the first sequence number may be the first of the unused sequence numbers, or may be the mth of the unused sequence numbers. For example, the first sequence number may be an unused SN or an unsent SN when the user terminal sends a data packet before PDCP re-establishment, or the first sequence number may be a next SN or an M-th SN after the last SN carried in the PDCP status report, for example, the last SN carried in the PDCP status report is 10, and the first sequence number may be 11, 12, 13, and so on, or the first sequence number may also be a next SN or an M-th SN after a SN whose reception status is not confirmed by the base station, which is not limited by this disclosure.

As another possible implementation manner, when the sequence numbers are randomly generated, that is, the sequence numbers sent by the user terminal each time are not consecutive, the sequence numbers used by the user terminal may be recorded, so that the sequence numbers that are not used may be determined according to the sequence numbers that are used. For example, if the serial numbers used by the user terminal are 1 and 10, the first serial number may be 3, 5, 15, 17, etc.

In this embodiment of the present disclosure, when the user terminal receives a PDCP reestablishment instruction, or when the higher layer instructs the PDCP reestablishment, it may be determined whether the transmission mode of the current bearer is simultaneously satisfied as an acknowledged mode, the configuration file satisfies a preset condition, and the current bearer includes a preset data packet, and if the transmission mode of the current bearer is simultaneously satisfied, the user terminal may send at least one first complete data packet to the base station, where each first complete data packet includes: the context information is context information reset after the user terminal acquires the packet data convergence protocol reestablishment instruction, for example, the user terminal may update the existing context information or reset the existing context information, and the context information at least includes a context identifier; the first sequence number is any sequence number that is not used by the base station in the bearer session.

It should be noted that before the user terminal resets the context information, the user terminal sends the complete data packet and the compressed packet to the base station, where the context forms, contents, and other information in the complete data packet and the compressed packet may be different, and after the user terminal receives the reestablishment instruction, the user terminal resets or updates 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 not changed, 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 received by the base station 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 discard the complete data packet. Therefore, in the present disclosure, in order to avoid a situation that the base station directly discards the complete data packet without further checking or acquiring information therein, which may cause that effective context information cannot be acquired and/or stored, the sequence number in the complete data packet sent by the user terminal to the base station may be a sequence number that the base station has not received in the current bearer, thereby ensuring that the base station successfully acquires the reset context information, so that the base station may perform normal decompression processing on the compressed packet sent by the user terminal by using the reset context information, and ensuring normal transmission of data.

In the embodiment of the present disclosure, when there is a predetermined data packet that is not successfully transmitted and the predetermined data packet is not a lost data packet (e.g., a packet with a reception failure or an unacknowledged (NACK)), the user terminal may further transmit a third complete data packet to the base station according to an existing manner, where the third complete data packet includes the uncompressed header information and a third sequence number in the predetermined data packet.

In this embodiment of the disclosure, under the condition that the existing communication protocol is not changed, because the third complete data packet has the third sequence number of the preset data packet, that is, the sequence number used before reconstruction, if the user terminal only sends 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 may be determined that the data packet corresponding to the third sequence number is received, and the base station may directly delete the third complete data packet, so that effective (or new) context information cannot be acquired and/or stored. Therefore, in order to avoid the above problem, the user terminal may further send at least one first complete data packet to the base station, where the first complete data packet includes any sequence number that is not received by the base station in the bearer, that is, a first sequence number, so that after receiving the first complete data packet, the base station may determine that the corresponding data packet is not received according to the first sequence number, and at this time, the base station may parse the received complete data packet, obtain and store context information that is reset by the user terminal after obtaining the PDCP re-establishment instruction, so that the compressed packet sent by the user terminal may be decompressed according to the reset context information, thereby ensuring normal transmission of data.

As an example, taking the sequence number as SN and the SNs are sequentially generated, when the transmission mode of the current bearer is the acknowledged mode, the user terminal determines that the last SN included in the PDCP PDU already sent to the base station is SN 20 and the PDCP PDUs with SNs 15, 17, 18, 20 are not successfully transmitted (e.g., may be determined according to the PDCP status report) and drb-ContinueROHC is not configured when receiving the PDCP re-establishment instruction, then the user terminal resets the header compression context information (new or valid context information), resets the header compression status, and re-sends the PDCP PDUs using SNs 15, 17, 18, 19, 20 (SN is also the original 15, 17, 18, 20) using the new context information. After the ue sends a new integrity packet containing new context information and integrity header using SN 21 (the first sequence number), the ue may send a compressed packet thereafter.

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

As another example, when the transmission mode of the current bearer is the acknowledged mode, the user terminal determines that a PDU with SN 19 in the PDCP PDUs already transmitted to the base station is missing when receiving the PDCP reestablishment instruction, and drb-conteniueroch is not configured, the user terminal resets header compression context information (new or valid context information), resets a header compression state, and retransmits the PDCP PDUs using SN 19 using the new context information. After the ue sends a new integrity packet containing new context information and integrity header using SN 19 (third sequence number), the ue may thereafter send a compressed packet.

As still another example, when the transmission mode of the current bearer is the acknowledged mode, the user terminal determines that the last SN included in the PDCP PDU already transmitted to the base station is SN 20, and PDCP PDUs with SNs 15, 17, 18, 20 are not successfully transmitted, PDU with SN 19 is missing, and drb-contexturohc is not configured when receiving the PDCP reestablishment instruction, then the user terminal resets the header compression context information (new or valid context information), resets the header compression state, and retransmits the PDCP PDUs using SNs 15, 17, 18, 19, 20 (SN number is also original 15, 17, 18, 20) using the new context information. When the ue sends a new integrity packet containing new context information and an integrity packet header using SN 19 (the third sequence number) and/or SN 21 (the first sequence number), the ue sends a compressed packet thereafter.

That is to say, when the predetermined data packet is a lost data packet, the ue may send only the first complete data packet to the base station, where the first sequence number included in the first complete data packet may specifically refer to the third sequence number in the predetermined data packet. When the predetermined data packet is a non-lost data packet, the user terminal may send a first complete data packet and a third complete data packet to the base station, where the third complete data packet includes uncompressed header information and a third sequence number in the predetermined data packet.

Further, in order to ensure that the base station acquires the corresponding context information, the number of the first complete data packets may be multiple, and the first sequence number included in each first complete data packet may be different. For example, each SN may be used as a first sequence number by using a SN that is not used by the ue and K SNs subsequent to the SN, so that the ue may send K +1 first complete data packets to the base station, so that the base station can successfully receive the reset context information. That is, the number of the first complete data packets sent by the user terminal to the base station may be multiple, the first sequence numbers corresponding to the first complete data packets are different, and after the user terminal sends one first complete data packet to the base station, the base station may determine, according to the first complete data packet, that the first sequence number in the first complete data packet is a sequence number that has not been received in the current bearer.

It should be noted that the number of the third complete data packets is the same as the number of the preset data packets, that is, several data packets failed to be sent before the reconstruction, and after receiving the PDCP reconstruction instruction, the data packets failed to be sent can be sent again to ensure the reliability and effectiveness of data transmission. 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, the base station directly discards the data packet containing the repetition number after receiving the data packet, and therefore, the data packet may be discarded even if the third complete data packet contains the reset context information.

It should be noted that 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, if the base station determines that the SN corresponding to the data packet has not been received after receiving the data packet containing the third sequence number (e.g. the PDU corresponding to the SN is a lost data packet), the base station stores the PDU and stores the context information. At this time, the base station may obtain and store context information reset by the user terminal after obtaining the PDCP re-establishment instruction, so that the compressed packet sent by the user terminal may be decompressed subsequently according to the context information, thereby ensuring normal transmission of data. Further, in order to ensure that the base station acquires the corresponding context information, the user terminal may further send a first complete data packet. The number of the first complete data packets is a non-negative integer.

In addition, the base station may transmit a feedback packet to the user terminal after saving the updated context information. After receiving the feedback packet, the user terminal may start sending the compressed packet.

As a possible implementation manner, when the protocol of the base station is not modified, and the base station receives the third complete data packet and/or at least one first complete data packet, the base station may determine whether a sequence number already received in the current bearer exists in the received complete data packet, and if not, may store the context information after being reset in the complete data packet. Further, the base station sends a feedback packet to the user terminal, where the feedback packet may be sent after the base station determines to receive a complete data packet containing the context information; alternatively, the feedback packet may be sent by the base station after the context information is saved. 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: and context information, wherein the context information is context information reset by the user terminal after the user terminal acquires the packet data convergence protocol reconstruction instruction, so that the base station can decompress the compressed packet based on the reset context information to ensure normal transmission of data.

As a possible implementation manner, under the condition that the protocol of the base station is modified, when the base station receives the third complete data packet and/or the at least one first complete data packet, the base station may determine whether a sequence number that has been received in the current bearer exists in the received complete data packet, and if so, may store the context information that is reset in the complete data packet. Further, the base station sends a feedback packet to the user terminal, where the feedback packet may be sent after the base station determines to receive a complete data packet containing the context information; alternatively, the feedback packet may be sent by the base station after the context information is saved. 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: and context information, wherein the context information is context information reset by the user terminal after the user terminal acquires the packet data convergence protocol reconstruction instruction, so that the base station can decompress the compressed packet based on the reset context information to ensure normal transmission of data.

As a possible implementation manner, after receiving the PDCP re-establishment instruction for a preset time period, the ue may default that the base station has received a complete data packet containing context information, or that the default base station has stored the reset context information, at this time, the ue may send a compressed packet to the base station, where the compressed packet includes: and context information, wherein the context information is context information reset after the user terminal acquires the packet data convergence protocol reconstruction instruction.

Specifically, after a first preset time interval, the user terminal may transmit a 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 command at 10:00:00, and may consider that the PDCP re-establishment procedure is completed at 10:00:02, and at this time, the user terminal may send the compressed packet to the base station.

As a possible implementation manner, after completing the PDCP re-establishment procedure, the user terminal may send a PDCP re-establishment completion message to an upper layer or a higher layer, and after sending a second preset time interval of the PDCP re-establishment completion message, may send a compressed packet to the base station, where the compressed packet includes context information, and the context information is context information reset after the user terminal obtains the packet data convergence protocol re-establishment instruction.

As an example, the processing flow of the uplink data packet is exemplified (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, the decompression end is the user terminal) is similar to the above, which is not described herein again.

1. The first DRB may be configured with Ethernet header compression parameters at the network side, where DRB-conteinurohc is not configured or its value is false, and specifically, the message is indicated to the user terminal through a dedicated RRC, such as PDCP-config IE.

2. And when the user terminal sends in the follow-up process, the user terminal carries out header compression processing according to the configuration information. Specifically, the user terminal sends a complete data packet including complete header information and context information, and sends a compressed packet to the base station after receiving a feedback packet or sending N complete data packets.

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

4. When a User Equipment (UE) receives a PDCP reestablishment instruction from a high layer (such as an RRC layer), or when the high layer indicates that the PDCP is reestablished (for example, when the UE RRC receives a reestablishment instruction from a base station, and the UE RRC requires the PDCP layer of the UE to reestablish the PDCP), if a transmission mode of a current bearer is a confirmation mode, a configuration file meets a preset condition, and the current bearer comprises a preset data packet, the user equipment sends a complete data packet.

For example, when the transmission mode of the current bearer is the acknowledged mode, the user terminal determines that the last SN included in the PDCP PDU that has been sent to the base station is SN 20, and PDCP PDUs with SNs 15, 17, 18, 20 are not successfully transmitted (e.g., may be determined according to the PDCP status report) and drb-conteuerrohc is not configured when receiving the PDCP re-establishment instruction, then the user terminal resets the header compression context information (new or valid context information), resets the header compression status, and re-sends PDCP PDUs using SNs 15, 17, 18, 20 (third sequence number) (SN number is still 15, 17, 18, 20) using the new context information. When the ue sends a new integrity packet containing new context information and integrity header using SN 21 (the first sequence number), the ue sends a compressed packet thereafter.

For another example, when the transmission mode of the current bearer is the acknowledged mode, and the user terminal determines that the last SN included in the PDCP PDU that has been sent to the base station is SN 20 and drb-contexturohc is not configured when it receives the PDCP re-establishment instruction, the user terminal resets the header compression context information (new or valid context information), resets the header compression state, and re-sends the PDU in the unacknowledged state 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 packet header, and receives a feedback packet of the base station, the user terminal sends a compression packet.

For another example, when the transmission mode of the current bearer is the acknowledged mode, and the user terminal determines that the last SN included in the PDCP PDU already sent to the base station is SN 20 and the PDCP PDUs with SNs 15, 17, 18, and 20 are not successfully transmitted (e.g., may be determined according to the PDCP status report), the PDU with SN 19 is missing and drb-conteniuerohc is not configured when receiving the PDCP re-establishment instruction, the user terminal resets the header compression context information (new or valid context information), resets the header compression state, and re-sends the PDCP PDUs (whether SN is the original 15, 17, 18, and 20) using SNs 15, 17, 18, 19, and 20 (third sequence number) using the new context information. When the ue sends a new integrity packet containing new context information and an integrity packet header using SN 19 (the third sequence number) and/or SN 21 (the first sequence number), the ue sends a compressed packet thereafter.

5. After receiving the PDCP reestablishment request, the base station receives a complete data packet sent by the user terminal, acquires and stores new context information, so that the compression packet can be decompressed by using the new context information subsequently.

That is, referring to fig. 2, after the user terminal receives the PDCP reestablishment instruction from the higher layer, if the three conditions that the transmission mode of the current bearer is the acknowledged mode, the configuration file meets the preset condition, and the current bearer includes the preset data packet are simultaneously met, the user terminal may send an uncompressed PDCP PDU to the base station, where the uncompressed PDCP PDU is a complete data packet and includes a third complete data packet and/or at least one first complete data packet, specifically, when the preset data packet is a lost data packet, send a first complete data packet, where a first sequence number in the first complete data packet is a 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. And if the transmission mode of the current bearer is the confirmation mode, the configuration file meets the preset conditions, and one of the three conditions that the current bearer comprises the preset data packet does not meet the preset conditions, the user terminal sends the compressed packet to the base station.

Alternatively, the base station may transmit the feedback packet to the user terminal after storing the updated context information. Correspondingly, after the user terminal receives the feedback packet, the user terminal may start to send the compressed packet to the base station.

In order to implement the above embodiments, the present disclosure further provides a method for compressing an ethernet frame packet header.

Fig. 3 is a flowchart illustrating a method for compressing an ethernet frame header according to a second embodiment of the disclosure.

As shown in fig. 3, the ethernet frame header compression processing method may include the following steps:

the ethernet frame header compression processing method of 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. Accordingly, the transmitting end (compression end, PDCP transmitting entity) is the user terminal.

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

The following description mainly takes the decompression end to which the ethernet frame header compression processing method is applied as a base station. The method of the decompressing end being the user terminal is similar.

Step 201, when a packet data convergence protocol reestablishment request is obtained, if a transmission mode of a current session is an acknowledged mode and a configuration file meets a preset condition, and a first sequence number in a first complete data packet obtained from a user terminal is a sequence number that a base station has not received in a current bearer, storing context information in the first complete data packet, so as to decompress a new compressed packet according to the context information in the first complete data packet.

The first complete data packet is sent to the base station after the user terminal obtains the packet data convergence protocol reestablishment instruction.

In this embodiment of the disclosure, the first sequence number in the first complete packet is any sequence number that is not received by the base station in the current bearer, where the sequence number that is not received by the base station in the current bearer is, that is, the first sequence number may be a sequence number that is not used by the user terminal, or may also be a sequence number that is used by the user terminal, but the sequence number is a sequence number in a lost packet (missing PDU), which is not limited to this. The first sequence number may be a Sequence Number (SN), or the first sequence number may also be a COUNT (COUNT). Wherein, COUNT occupies 32 bits, and is composed of Hyper Frame Number (HFN for short) and PDCP SN, and SN is the low bit of COUNT.

In the embodiment of the present disclosure, when the base station receives the PDCP reestablishment request, or when the higher layer indicates the PDCP reestablishment, it may determine whether the transmission mode of the current session is simultaneously satisfied as the confirmation mode, the configuration file satisfies the preset condition, the first sequence number in the first complete data packet acquired from the user terminal, and the sequence number that is not received by the base station in the current bearer, and if the transmission mode and the configuration file satisfy the preset condition, the base station may store the context information in the first complete data packet, so that decompression processing may be performed subsequently according to the context information in the first complete data packet. The first complete data packet corresponding to the first sequence number is received by the base station after receiving a request for reconstructing the higher layer PDCP, or the first complete data packet is received from the lower layer due to the PDCP.

Specifically, when the user terminal receives the PDCP reestablishment instruction, or when the higher layer indicates that the PDCP is reestablished, it may determine whether the transmission mode of the current bearer is simultaneously satisfied as an acknowledged mode, the configuration file satisfies the preset condition, and the current bearer includes the preset data packet, and if the transmission mode of the current bearer is simultaneously satisfied, the user terminal may send at least one first complete data packet to the base station, where each first complete data packet may include context information, uncompressed header information, and a first sequence number, where the context information is context information reset by the user terminal after the user terminal obtains the PDCP reestablishment instruction, and the first sequence number is any sequence number that the base station has not received in the bearer. 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 sending confirmation state or an unconfirmed sending state when obtaining the reconstruction instruction, or the preset data packet may also be a data packet that the user terminal loses before obtaining the reconstruction instruction, which is not limited by the present disclosure. For example, a pre-set packet may be acknowledged according to the PDCP status report, wherein the pre-set packet may include at least one of: successfully transmitted PDUs, unsuccessfully transmitted PDUs, missing (missing) PDUs, PDUs whose transmission status is uncertain.

Correspondingly, after receiving the first complete data packet, the base station determines that the corresponding data packet is not received according to the first sequence number, and at this time, the base station can analyze the received complete data packet, and obtain and store context information reset by the user terminal after obtaining the PDCP reestablishment request, so that the new compressed packet sent by the user terminal can be decompressed subsequently according to the context information, and normal transmission of data is ensured.

In the embodiment of the present disclosure, when there is a predetermined data packet that is not successfully transmitted and the predetermined data packet is not a lost data packet (e.g., a packet with reception failure or NACK), the ue may further transmit a third complete data packet to the base station according to an existing manner, where the third complete data packet includes uncompressed header information and a third sequence number in the predetermined data packet.

That is to say, in the present disclosure, under the condition that the existing communication protocol is not changed, since the third complete data packet has the third sequence number of the preset data packet, that is, the sequence number used before reconstruction, if the user terminal only sends the third complete data packet, after receiving the third complete data packet, the base station may determine that the data packet corresponding to the third sequence number is received according to the third sequence number in the third complete data packet, and the base station may directly delete the third complete data packet, so that effective (or new) context information cannot be acquired and/or stored. Therefore, in order to avoid the above problem, the user terminal may further send at least one first complete data packet to the base station, where the first complete data packet includes any sequence number that is not received by the base station in the bearer, that is, a first sequence number, so that after receiving the first complete data packet, the base station may determine that the corresponding data packet is not received according to the first sequence number, and at this time, the base station may parse the received complete data packet, obtain and store context information that is reset after the user terminal obtains the PDCP re-establishment instruction, so that a new compressed packet sent by the user terminal may be decompressed according to the context information subsequently, and normal transmission of data is ensured.

As an example, taking the sequence number as SN and the SNs are sequentially generated, when the transmission mode of the current bearer is the acknowledged mode, the user terminal determines that the last SN included in the PDCP PDU already sent to the base station is SN 20 and the PDCP PDUs with SNs 15, 17, 18, 20 are not successfully transmitted (e.g., may be determined according to the PDCP status report) and drb-ContinueROHC is not configured when receiving the PDCP re-establishment instruction, then the user terminal resets the header compression context information (new or valid context information), resets the header compression status, and re-sends the PDCP PDUs using SNs 15, 17, 18, 19, 20 (SN is also the original 15, 17, 18, 20) using the new context information. When the ue sends a new integrity packet containing new context information and integrity header using SN 21 (the first sequence number), the ue sends a compressed packet thereafter.

As another example, when the transmission mode of the current bearer is the acknowledged mode, the user terminal determines that a PDU with SN 19 in the PDCP PDUs already transmitted to the base station is missing when receiving the PDCP reestablishment instruction, and drb-conteniueroch is not configured, the user terminal resets header compression context information (new or valid context information), resets a header compression state, and retransmits the PDCP PDUs using SN 19 using the new context information. When the ue sends a new integrity packet containing new context information and integrity header using SN 19 (third sequence number), the ue then sends a compressed packet.

Fig. 4 is a flowchart illustrating a method for compressing an ethernet frame header according to a third embodiment of the present disclosure.

As shown in fig. 4, the ethernet frame header compression processing method may include the following steps:

Of course, in another implementation, the ethernet frame header compression process may be applied to the user terminal, and the base station is a compression end, i.e. the PDCP sending entity. Accordingly, 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 of the decompressing end being the user terminal is similar.

Step 301, when a packet data convergence protocol reestablishment request is obtained, if the transmission mode of the current session is the acknowledged 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 already received by the base station in the current bearer, then context information in the second complete data packet is saved.

In the embodiment of the present disclosure, the second sequence number may be a Sequence Number (SN), or the second sequence number may also be a COUNT (COUNT). Wherein, COUNT occupies 32 bits, and is composed of HFN and PDCP SN, and SN is the low order of COUNT.

In this embodiment of the present disclosure, when the base station receives the PDCP reestablishment request, or when the higher layer indicates that the PDCP is reestablished, it may determine whether the transmission mode of the current session is the acknowledged mode, the configuration file satisfies the preset condition, the second sequence number in the second complete data packet obtained from the user terminal is the sequence number already received by the base station in the current bearer or the repeated sequence number (for example, repeated SN, that is, duplicate SN) is satisfied at the same time, and if the transmission mode and the configuration file satisfy the preset condition, the base station may store the context information in the second complete data packet, so that the decompression processing may be performed subsequently according to the context information in the second complete data packet. And the third complete data packet corresponding to the second sequence number is received by the base station after receiving the request for reconstructing the higher layer PDCP, or the second complete data packet is received from the lower layer again due to the PDCP.

That is, the protocol of the base station (i.e., the receiving end or the decompressing end) may be modified, and when the PDCP re-establishment request is received, if the sequence number in the complete data packet received by the base station is previously received, the context information in the complete data packet is stored, so that the subsequent base station may decompress the compressed packet sent by the user terminal according to the context information, thereby ensuring normal transmission of data.

In addition, the base station may send a feedback packet to the user terminal after saving the context information. After receiving the feedback packet, the user terminal may start sending the compressed packet.

In the method for compressing the ethernet frame header according to the embodiment of the present disclosure, when the base station obtains the packet data convergence protocol reestablishment request, if the transmission mode of the current session is the acknowledged 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 has been received by the base station in the current bearer, the context information in the second complete data packet is saved. Therefore, the base station can be ensured to successfully acquire the reset context information, so that the base station can carry out normal decompression processing on the compressed packet sent by the user terminal, and normal transmission of data is ensured.

As a possible implementation manner, the base station stores the context information in the second complete data packet, or the base station successfully decompresses the received compressed packet by using the context information, or the base station may further send a feedback packet to the user terminal when there is valid context information, where the feedback packet is used to indicate that the context information in the second complete data packet has been stored, or indicate that the base station successfully decompresses the received compressed packet, or indicate that there is valid context information in the base station.

As a possible implementation manner, in order to avoid that the base station stores the same context information repeatedly, before the base station stores the context information in the second complete data packet, it is further required to determine that the base station does not store the context information in the second complete data packet. That is, the context information already stored in the base station is determined and stored before the PDCP re-establishment request is acquired, so that when the context information in the second complete packet is stored, it can be determined that there is no duplicate context information in the stored data.

As a possible implementation manner, after the base station stores the context information in the second complete data packet, if the sequence number, such as the SN, in the complete data packet sent by the user terminal to the base station is a sequence number already received by the base station in the current bearer, the complete data packet is discarded. Specifically, after the base station stores the context information in the second complete data packet, if a third sequence number in a third complete data packet newly acquired by the base station from the user terminal is a sequence number that has already been received by the base station in the current bearer, 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 base station may receive and store data by using an existing protocol. Specifically, when the complete data packet received by the base station includes a sequence number that has been received before, 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 already received in the current bearer, the base station may use the existing protocol to discard the data packet.

As a possible implementation manner, in order to avoid that the base station stores the same context information repeatedly, before the base station stores the context information in the second complete data packet, it is further determined that the base station does not send a feedback packet to the user terminal after obtaining the PDCP reestablishment request, where the feedback packet is used to indicate: the base station decompresses the acquired data packet successfully, or the base station has the reset context information, or the reset context information is already stored.

2. And when the user terminal sends in the follow-up process, the user terminal carries out header compression processing according to the configuration information. Specifically, the user terminal sends a complete data packet including complete packet header information and context information, and sends a compressed packet to the base station after receiving a feedback packet or sending N packets including complete data packets.

4. When a User Equipment (UE) receives a PDCP reestablishment request from a higher layer (such as an RRC layer), for example, when the UE RRC receives the reestablishment request from a base station, and the UE RRC requires the UE PDCP layer to carry out PDCP reestablishment, the current transmission mode of the bearer is an acknowledgement mode, the user equipment resets context information, resets a header compression state, and sends a PDCP PDU according to new context information.

5. When a PDCP reestablishment request is received or a higher layer indicates PDCP reestablishment, the base station receives a data packet sent by the user terminal, acquires and stores new context information. Specifically, after receiving the PDCP reestablishment request, the base station determines that the current bearer transmission mode is an acknowledgement mode, and when the SN corresponding to the received PDCP PDU is a duplicate SN or a received SN before reestablishment, performs at least one of the following operations:

1) decompressing the PDCP PDU;

2) valid (new) context information is saved. 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 an effective (new) context and/or stores the context;

3) and sending a feedback packet to the user terminal, wherein the feedback packet is used for indicating that the effective context information is successfully established and/or saved.

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

The base station may then perform decompression according to the stored new context information. In particular, when the feedback packet needs to be sent, the base station sends the feedback packet to indicate that the base station has received and/or stored valid context information. And after the user terminal receives the feedback packet, the user terminal can send a compressed packet.

For example, the transmission mode of the current session is an acknowledgement mode, after receiving the PDCP reestablishment request, the base station receives the PDCP PDU with SN of 10, and the data packet corresponding to the SN has been received before, and since drb-conteinurohc is not configured and the base station does not have an effective context at this time, the base station decompresses the PDU with SN of 10. When the PDU is determined to be a complete data packet, or the PDCP PDU has complete header information and context information, the base station considers the context contained therein to be valid (new) context information, and the base station stores the context for decompression when subsequently receiving a compressed packet. In addition, if a PDU with SN of 11 is received subsequently and a data packet corresponding to the SN has been received before, the base station will discard the data packet by using the existing protocol because there is valid context information.

In order to implement the foregoing embodiments, the present disclosure further provides an ethernet frame header compression processing apparatus.

Fig. 5 is a schematic structural diagram of an ethernet frame header compression processing apparatus according to a fourth embodiment of the present disclosure.

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

Of course, in another implementation manner, the ethernet frame header compression processing apparatus may be disposed at the base station side, that is, the base station is a compression end, that is, the PDCP sending entity. Accordingly, 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 apparatus is installed as the user terminal. The device with the compression end being the base station is similar.

As shown in fig. 5, the ethernet frame header compression processing apparatus includes a sending module 501.

The sending module 501 is configured to send at least one first complete data packet to the base station when the packet data convergence protocol reestablishment request is obtained, if the transmission mode of the current bearer is the acknowledged mode, the configuration file meets the preset condition, and the current bearer includes a preset data packet.

Wherein each first complete data packet comprises: the base station comprises context information, uncompressed header information and a first sequence number, wherein the context information is context information reset by the user terminal after acquiring a packet data convergence protocol reestablishment request, and the first sequence number is any sequence number which is not received by the base station in the bearing process.

As a possible implementation manner, the data packet is preset, and the data packet is a data packet that is sent unsuccessfully before the user terminal obtains the reconstruction instruction, or a data packet that is sent successfully or in an unacknowledged sending state is not obtained when the user terminal obtains the reconstruction instruction, or a data packet that is lost when the user terminal obtains the reconstruction instruction or before the user terminal obtains the reconstruction instruction.

As a possible implementation manner, the configuration file satisfies a preset condition, including: the configuration parameters preset in the configuration file are not assigned; or the assignment of the preset configuration parameters in the configuration file is false.

As a possible implementation manner, the sending module 401 is further configured to send a compressed packet to the base station if the feedback packet sent by the base station is obtained, where the compressed packet includes: context information, wherein the context information is context information reset after the user terminal acquires a packet data convergence protocol reconstruction request; the feedback packet is sent after the base station determines to receive a complete data packet containing the context information; or the feedback packet is sent by the base station after the context information is stored.

As a possible implementation manner, the sending module 401 is further configured to send a compressed packet to the base station after a first preset time interval, where the compressed packet includes: and context information, wherein the context information is context information reset after the user terminal acquires the packet data convergence protocol reconstruction request.

As a possible implementation manner, after sending a second preset time interval of the packet data convergence protocol reestablishment completion message, sending a compressed packet to the base station, where the compressed packet includes context information, and the context information is context information reset by the user terminal after obtaining the packet data convergence protocol reestablishment request.

As a possible implementation, the first sequence number; alternatively, the first sequence number is a count.

It should be noted that the explanation of the ethernet frame header compression processing method in the foregoing embodiments of fig. 1-2 is also applicable to the ethernet frame header compression processing apparatus, and the implementation principle is similar, and is not described herein again.

According to the device for compressing the Ethernet frame packet header in the embodiment of the disclosure, when a user terminal acquires a packet data convergence protocol reconstruction request, if a transmission mode of a current bearer is a confirmation mode, a configuration file meets a preset condition, and the current bearer comprises a preset data packet, at least one first complete data packet is sent to a base station; wherein each first complete data packet comprises: the context information is context information reset after the user terminal obtains the packet data convergence protocol reestablishment request, and the first sequence number is any sequence number which is not used by the user terminal in the bearer session. In the disclosure, the user terminal sends at least one first complete data packet to the base station, and since the first complete data packet includes a serial number that is not received by the base station in the bearer, the base station can be ensured to successfully acquire the reset context information, so that the base station can perform normal decompression processing on a compressed packet sent by the user terminal, and normal transmission of data is ensured.

Fig. 6 is a schematic structural diagram of an ethernet frame header compression processing apparatus according to a fifth embodiment of the present disclosure.

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

Of course, in another implementation manner, the ethernet frame header compression processing apparatus may be disposed at the user terminal side, and the base station is a compression side, that is, a PDCP sending entity. Accordingly, 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 apparatus is installed as a base station. The apparatus of which the decompression end is the user terminal is similar to the apparatus.

As shown in fig. 6, the ethernet frame header compression processing apparatus includes: a save module 601.

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

It should be noted that, the explanation of the ethernet frame header compression processing method in the foregoing embodiment of fig. 3 is also applicable to the ethernet frame header compression processing apparatus, and the implementation principle is similar, and is not described herein again.

Fig. 7 is a schematic structural diagram of an ethernet frame header compression processing apparatus according to a sixth embodiment of the present disclosure.

As shown in fig. 7, the ethernet frame header compression processing apparatus includes: a save module 701.

The saving module 701 is configured to, when the packet data convergence protocol reestablishment request is obtained, if the transmission mode of the current session is the acknowledged 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 already received by the base station in the current bearer, save context information in the second complete data packet.

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

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

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

A discarding module 704, configured to discard the third complete data packet if a third sequence number in the third complete data packet newly acquired from the user equipment is a sequence number already received by the base station in the current bearer.

As a possible implementation manner, the determining module 703 is further configured to determine that the base station does not send a feedback packet to the user equipment after acquiring the packet data convergence protocol reestablishment request, where the feedback packet is used to indicate: the base station decompresses the acquired data packet successfully, or the base station has the reset context information, or the reset context information is already stored.

It should be noted that, the explanation of the ethernet frame header compression processing method in the foregoing embodiment of fig. 4 is also applicable to the ethernet frame header compression processing apparatus, and the implementation principle is similar, and is not described herein again.

In the ethernet frame header compression processing apparatus of the embodiment of the present disclosure, when the base station obtains the packet data convergence protocol reestablishment request, if the transmission mode of the current session is the acknowledged mode, and the configuration file satisfies the preset condition, and the second sequence number in the second complete data packet obtained from the user terminal is the sequence number that has been received by the base station in the current bearer, the context information in the second complete data packet is saved. Therefore, the base station can be ensured to successfully acquire 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, and normal transmission of data is ensured.

In order to implement the foregoing embodiment, the present disclosure further provides a user terminal, including: the present disclosure relates to a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the ethernet frame header compression processing method according to the embodiments of fig. 1 to 2 of the present disclosure.

In order to implement the foregoing embodiments, the present disclosure further provides a base station, including: the device comprises a memory, a processor and a computer program stored in the memory and capable of running on the processor, wherein the processor executes the program to implement the ethernet frame header compression processing method according to the foregoing fig. 3 embodiment of the present disclosure.

In order to implement the foregoing embodiment, the present disclosure further provides another base station, including: the device comprises a memory, a processor and a computer program stored in the memory and capable of running on the processor, wherein the processor executes the program to implement the ethernet frame header compression processing method according to the foregoing fig. 4 embodiment of the present disclosure.

In order to implement the foregoing embodiments, the present disclosure further provides a computer-readable storage medium, on which a computer program is stored, where the computer program is configured to, when executed by a processor, implement the ethernet frame header compression processing method proposed in the foregoing fig. 1 to fig. 2 embodiments of the present disclosure, or implement the ethernet frame header compression processing method proposed in the foregoing fig. 3 embodiments of the present disclosure, or implement the ethernet frame header compression processing method proposed in the foregoing fig. 4 embodiments of the present disclosure.

In the description herein, references to the description of the term "one embodiment," "some embodiments," "an example," "a specific example," or "some examples," etc., mean that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the present disclosure. In this specification, the schematic representations of the terms used above are not necessarily intended to refer to the same embodiment or example. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples. Furthermore, various embodiments or examples and features of different embodiments or examples described in this specification can be combined and combined by one skilled in the art without contradiction. Furthermore, the terms "first", "second" and "first" are used for descriptive purposes only and are not to be construed as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one such feature. In the description of the present disclosure, "a plurality" means at least two, e.g., two, three, etc., unless explicitly specifically limited otherwise.

Any process or method descriptions in flow charts or otherwise described herein may be understood as representing modules, segments, or portions of code which include one or more executable instructions for implementing steps of a custom logic function or process, and alternate implementations are included within the scope of the preferred embodiment of the present disclosure in which functions may be executed out of order from that shown or discussed, including substantially concurrently or in reverse order, depending on the functionality involved, as would be understood by those reasonably skilled in the art of the embodiments of the present disclosure.

The logic and/or steps represented in the flowcharts or otherwise described herein, e.g., an ordered listing of executable instructions that can be considered to implement logical functions, can be embodied in any computer-readable medium for use by or in connection with an instruction execution system, apparatus, or device, such as a computer-based system, processor-containing system, or other system that can fetch the instructions from the instruction execution system, apparatus, or device and execute the instructions. For the purposes of this description, a "computer-readable medium" can be any means that can contain, store, communicate, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device. More specific examples (a non-exhaustive list) of the computer-readable medium would include the following: an electrical connection (electronic device) having one or more wires, a portable computer case (magnetic device), a Random Access Memory (RAM), a read-only memory, an erasable programmable read-only memory (EPROM or flash memory), an optical fiber device, and a portable compact disc read-only memory. Additionally, the computer-readable medium could even be paper or another suitable medium upon which the program is printed, as the program can be electronically captured, via for instance optical scanning of the paper or other medium, then compiled, interpreted or otherwise processed in a suitable manner if necessary, and then stored in a computer memory.

It should be understood that portions of the present disclosure may be implemented in hardware, software, firmware, or a combination thereof. In the above embodiments, the various steps or methods may be implemented in software or firmware stored in memory and executed by a suitable instruction execution system. If implemented in hardware, as in another embodiment, any one or combination of the following techniques, which are known in the art, may be used: a discrete logic circuit having a logic gate circuit for implementing a logic function on a data signal, an application specific integrated circuit having an appropriate combinational logic gate circuit, a programmable gate array, a field programmable gate array, or the like. It will be understood by those skilled in the art that all or part of the steps carried by the method for implementing the above embodiments may be implemented by hardware related to instructions of a program, which may be stored in a computer readable storage medium, and when the program is executed, the program includes one or a combination of the steps of the method embodiments.

In addition, functional units in 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 are integrated into one module. The integrated module can be realized in a hardware mode, and can also be realized in a software functional module mode. The integrated module, if implemented in the form of a software functional module and sold or used as a separate product, may also be stored in a computer readable storage medium. The storage medium mentioned above may be a read-only memory, a magnetic or optical disk, etc. Although embodiments of the present disclosure have been shown and described above, it is understood that the above embodiments are exemplary and should not be construed as limiting the present disclosure, and that changes, modifications, substitutions and alterations may be made to the above embodiments by those of ordinary skill in the art within the scope of the present disclosure.

Claims

A compression processing method for Ethernet frame header is applied to user terminal, which is characterized in that the method comprises:

when a packet data convergence protocol reconstruction instruction is obtained, if a transmission mode of a current bearer is a confirmation mode, the configuration file meets a preset condition, and the current bearer comprises a preset data packet, sending at least one first complete data packet to a base station;

wherein each first complete data packet comprises: the base station comprises context information, uncompressed header information and a first sequence number, wherein the context information is context information reset by the user terminal after acquiring a packet data convergence protocol reestablishment instruction, and the first sequence number is any sequence number which is not received by the base station in the bearing process.
The method of claim 1,

the preset data packet is a data packet which is failed to be sent by the user terminal before the user terminal acquires the reconstruction instruction, or a data packet which is not successfully sent or sent in an unconfirmed state is not acquired by the user terminal when the user terminal acquires the reconstruction instruction, or a data packet which is lost by the user terminal when the user terminal acquires the reconstruction instruction or before the user terminal acquires the reconstruction instruction.
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;

or,

and assigning a value of a preset configuration parameter in the configuration file to be false.
The method of claim 1, wherein after transmitting at least one first complete data packet to the base station, further comprising:

if the feedback packet sent by the base station is obtained, sending a compressed packet to the base station, wherein the compressed packet comprises: context information, wherein the context information is context information reset by the user terminal after the user terminal obtains a packet data convergence protocol reconstruction instruction;

the feedback packet is sent by the base station after the base station determines to receive a complete data packet containing context information; or, the feedback packet is sent by the base station after the context information is saved.
The method of claim 1, wherein after obtaining the packet data convergence protocol reestablishment instruction, the method further comprises:

after a first preset time interval, sending a compressed packet to the base station, wherein the compressed packet comprises: and context information, wherein the context information is context information reset by the user terminal after the user terminal acquires the packet data convergence protocol reestablishment instruction.
The method of any of claims 1-5, wherein after transmitting at least one first complete data packet to the base station, further comprising:

and after sending a second preset time interval of the packet data convergence protocol reconstruction completion message, sending a compressed packet to the base station, wherein the compressed packet comprises context information, and the context information is context information reset after the user terminal obtains a packet data convergence protocol reconstruction instruction.
The method of any of claims 1-6, wherein the first sequence number is a sequence number;

alternatively, the first sequence number is a count.
A compression processing method for Ethernet frame header is applied to a base station, and is characterized by comprising the following steps:

when a packet data convergence protocol reconstruction request is acquired, if a transmission mode of a current session is an acknowledgement mode and the configuration file meets a preset condition, and a first sequence number in a first complete data packet acquired from a user terminal is a sequence number which is not received by the base station in a current bearer, storing context information in the first complete data packet so as to decompress a new compressed packet according to the context information in the first complete data packet;

and the first complete data packet is sent to the base station after the user terminal acquires the packet data convergence protocol reconstruction instruction.
A compression processing method for Ethernet frame header is applied to a base station, and is characterized by comprising the following steps:

when a packet data convergence protocol reestablishment request is acquired, if the transmission mode of the current session is a confirmation mode, the configuration file meets a preset condition, and a second sequence number in a second complete data packet acquired from a user terminal is a sequence number already received by the base station in the current bearer, the context information in the second complete data packet is saved.
The method of claim 9, wherein the configuration file satisfies a preset condition, comprising:

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

or,

and assigning a value of a preset configuration parameter in the configuration file to be false.
The method of claim 9, wherein after saving the context in the second complete packet, further comprising:

and sending a feedback packet to the user terminal, wherein the feedback packet is used for indicating that the context information in the second complete data packet is stored.
The method of any of claims 9-11, wherein prior to saving the context information in the second complete packet, further comprising:

determining that the context information in the second complete data packet is not stored in the base station.
The method of claim 12, wherein after saving the context information in the second complete packet, further comprising:

and if the third sequence number in the third complete data packet newly acquired from the user terminal is the sequence number already received by the base station in the current bearer, discarding the third complete data packet.
The method of any of claims 9-13, wherein prior to saving the context information in the second complete packet, further comprising:

determining that the base station does not send a feedback packet to the user terminal after acquiring the packet data convergence protocol reestablishment request, wherein the feedback packet is used for indicating: the base station decompresses the acquired data packet successfully, or the base station has the reset context information, or the reset context information is already stored.
An ethernet frame header compression processing device, disposed in a user terminal, comprising:

a sending module, configured to send at least one first complete data packet to a base station if a transmission mode of a current bearer is an acknowledgement mode, the configuration file meets a preset condition, and the current bearer includes a preset data packet when a packet data convergence protocol reestablishment instruction is obtained;

wherein each first complete data packet comprises: the base station comprises context information, uncompressed header information and a first sequence number, wherein the context information is context information reset by the user terminal after acquiring a packet data convergence protocol reestablishment instruction, and the first sequence number is any sequence number which is not received by the base station in the bearing process.
An ethernet frame header compression processing apparatus, provided in a base station, comprising:

a storage module, configured to, when a packet data convergence protocol reestablishment request is obtained, if a transmission mode of a current session is an acknowledged mode and the configuration file meets a preset condition, and a first sequence number in a first complete data packet obtained from a user terminal is a sequence number that has not been received by the base station in a current bearer, store context information in the first complete data packet, so as to decompress a new compressed packet according to the context information in the first complete data packet;

and the first complete data packet is sent to the base station after the user terminal acquires the packet data convergence protocol reconstruction instruction.
An ethernet frame header compression processing apparatus, provided in a base station, comprising:

and the storage module is used for storing the context information in the second complete data packet 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 acquired from the user terminal is the sequence number already received by the base station in the current bearer when the packet data convergence protocol reestablishment request is acquired.
A user terminal, comprising: memory, processor and computer program stored on the memory and executable on the processor, which when executed by the processor implements the ethernet frame header compression processing method according to any of claims 1 to 7.
A base station, comprising: a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the method of compressing the ethernet frame header according to claim 8 when executing the program.
A base station, comprising: memory, processor and computer program stored on the memory and executable on the processor, which when executed by the processor implements the ethernet frame header compression processing method according to any of claims 9 to 14.
A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, implements the ethernet frame header compression processing method according to any one of claims 1 to 7, or implements the ethernet frame header compression processing method according to claim 8, or implements the ethernet frame header compression processing method according to any one of claims 9 to 14.