CN110891041B

CN110891041B - Packet header compression method, decompression method, equipment and storage medium

Info

Publication number: CN110891041B
Application number: CN201811044566.9A
Authority: CN
Inventors: 张艳霞; 吴昱民
Original assignee: Vivo Mobile Communication Co Ltd
Current assignee: Vivo Mobile Communication Co Ltd
Priority date: 2018-09-07
Filing date: 2018-09-07
Publication date: 2021-09-14
Anticipated expiration: 2038-09-07
Also published as: CN110891041A

Abstract

The embodiment of the invention provides a method for compressing a packet header, a method for decompressing the packet header and equipment, wherein the method comprises the following steps: and performing packet header compression processing on a first packet header and a second packet header in a first data packet by using a transmitting PDCP entity of the transmitting end to obtain a first compressed packet header and a second compressed packet header, wherein the first packet header or the second packet header is an Ethernet packet header. In the embodiment of the invention, the sending PDCP entity of the sending end can compress the first packet header and the second packet header in the received first data packet, so that the packet header overhead can be reduced. In addition, the processing behaviors of the sending end and the receiving end on the compressed packet and the compression feedback are standardized, and the compression efficiency can be improved.

Description

Packet header compression method, decompression method, equipment and storage medium

Technical Field

The embodiment of the invention relates to the technical field of communication, in particular to a packet header compression method, a decompression method and equipment.

Background

In Long Term Evolution (LTE) and New Radio (NR), protocols provide that a Packet Data Convergence Protocol (PDCP) sublayer performs a header compression or header decompression function at a Radio Access Network (RAN) side.

The Header Compression protocol is based on Request For Comments (RFC) 9795 protocol established by The Internet Engineering Task Force (IETF), which defines a framework For Robust Header Compression (ROHC). The ROHC framework has a variety of header compression algorithms, called profiles. Each profile is specific to a particular network layer, transport layer and upper layer protocol combination, for example: transmission Control Protocol (TCP)/Internet Protocol (IP) and Real-time Transport Protocol (RTP)/TCP/IP.

If the header compression function is configured, the header compression protocol will produce two types of outgoing packets:

(1) compressing packet packets, each of which is obtained by header compressing one PDCP Service Data Unit (SDU);

(2) discrete ROHC feedback, not associated with PDCP SDU, belonging to PDCP control PDU generated by PDCP layer;

the PDCP control PDU of the PDCP layer has two kinds of uses: (1) for receiving a PDCP entity feedback receiving status; (2) for receiving the PDCP entity feedback decompression status, the format of the discrete ROHC feedback can be seen in fig. 1.

The Industry Internet of things (IIOT) project requires Ethernet header (Ethernet header) compression on the RAN side, and the PDCP layer performing header compression function does not support Ethernet header compression at present.

How to implement compression of at least two types of headers on the RAN side becomes a problem to be solved.

Disclosure of Invention

An object of the embodiments of the present invention is to provide a method for compressing a packet header, a method for decompressing a packet header, and an apparatus for decompressing a packet header, which solve the problem of compressing at least two types of packet headers on a RAN side.

In a first aspect, an embodiment of the present invention provides a method for compressing a packet header, where the method is applied to a sending end, and the method includes:

and performing packet header compression processing on a first packet header and a second packet header in a first data packet by using a Packet Data Convergence Protocol (PDCP) entity of the sending end to obtain a first compressed packet header and a second compressed packet header, wherein the first packet header or the second packet header is an Ethernet packet header.

In a second aspect, an embodiment of the present invention further provides a method for decompressing a packet header, which is applied to a receiving end, where the method includes:

receiving a first compressed packet header and a second compressed packet header through a receiving PDCP entity of the receiving end;

and performing packet header decompression processing on the first compressed packet header and the second compressed packet header to obtain a first packet header and a second packet header, wherein the first packet header or the second packet header is an ethernet packet header.

In a third aspect, an embodiment of the present invention further provides a sending end, including:

a compression module, configured to perform packet header compression processing on a first packet header and a second packet header in a first data packet through a sending PDCP entity of the sending end to obtain a first compressed packet header and a second compressed packet header, where the first packet header or the second packet header is an ethernet packet header.

In a fourth aspect, an embodiment of the present invention further provides a receiving end, including:

a receiving module, configured to receive the first compressed packet header and the second compressed packet header through a receiving PDCP entity of the receiving end;

and the decompression module is used for carrying out packet header decompression processing on the first compressed packet header and the second compressed packet header to obtain a first packet header and a second packet header, wherein the first packet header or the second packet header is an Ethernet packet header.

In a fifth aspect, an embodiment of the present invention further provides a sending end, including: a processor, a memory and a program stored on the memory and executable on the processor, which when executed by the processor, performs the steps of the method of packet header compression as described in the first aspect.

In a sixth aspect, an embodiment of the present invention further provides a receiving end, including: a processor, a memory and a program stored on the memory and executable on the processor, the program, when executed by the processor, implementing the steps of the method for header decompression as described in the second aspect.

In a seventh aspect, an embodiment of the present invention further provides a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and when executed by a processor, the computer program implements the steps of the packet header compression method according to the first aspect or the second aspect.

In the embodiment of the invention, the sending PDCP entity of the sending end can compress the first packet header and the second packet header in the received first data packet, so that the packet header overhead can be reduced. In addition, the processing behaviors of the sending end and the receiving end on the compressed packet and the compression feedback are standardized, and the compression efficiency can be improved.

Drawings

Various other advantages and benefits will become apparent to those of ordinary skill in the art upon reading the following detailed description of the preferred embodiments. The drawings are only for purposes of illustrating the preferred embodiments and are not to be construed as limiting the invention. Also, like reference numerals are used to refer to like parts throughout the drawings. In the drawings:

fig. 1 is a schematic diagram of a format of a conventional discrete ROHC feedback;

FIG. 2 is a block diagram of a wireless communication system according to an embodiment of the present invention;

fig. 3 is a flowchart of a method for compressing a packet header according to an embodiment of the present invention;

fig. 4 is a flowchart of a method for decompressing a packet header according to an embodiment of the present invention;

fig. 5 is a schematic structural diagram of a transmitting end according to an embodiment of the present invention;

fig. 6 is a schematic structural diagram of a receiving end according to an embodiment of the present invention;

fig. 7 is a structural diagram of a terminal of an embodiment of the present invention;

fig. 8 is a block diagram of a network device according to an embodiment of the present invention.

Detailed Description

The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, not all, embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.

The terms "comprises," "comprising," or any other variation thereof, in the description and claims of this application, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus. Furthermore, the use of "and/or" in the specification and claims means that at least one of the connected objects, such as a and/or B, means that three cases, a alone, B alone, and both a and B, exist.

In the embodiments of the present invention, words such as "exemplary" or "for example" are used to mean serving as examples, illustrations or descriptions. Any embodiment or design described as "exemplary" or "e.g.," an embodiment of the present invention is not necessarily to be construed as preferred or advantageous over other embodiments or designs. Rather, use of the word "exemplary" or "such as" is intended to present concepts related in a concrete fashion.

The techniques described herein are not limited to Long Time Evolution (LTE)/LTE Evolution (LTE-Advanced) systems, and may also be used for various wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA), and other systems, for example: a fifth generation mobile communication (5th-generation, 5G) system and a subsequent evolution communication system.

The terms "system" and "network" are often used interchangeably. CDMA systems may implement Radio technologies such as CDMA2000, Universal Terrestrial Radio Access (UTRA), and so on. UTRA includes Wideband CDMA (Wideband Code Division Multiple Access, WCDMA) and other CDMA variants. TDMA systems may implement radio technologies such as Global System for Mobile communications (GSM). The OFDMA system may implement radio technologies such as Ultra Mobile Broadband (UMB), evolved-UTRA (E-UTRA), IEEE 802.11(Wi-Fi), IEEE 802.16(WiMAX), IEEE 802.20, Flash-OFDM, etc. UTRA and E-UTRA are parts of the Universal Mobile Telecommunications System (UMTS). LTE and higher LTE (e.g., LTE-A) are new UMTS releases that use E-UTRA. UTRA, E-UTRA, UMTS, LTE-A, and GSM are described in documents from an organization named "third Generation Partnership Project" (3 GPP). CDMA2000 and UMB are described in documents from an organization named "third generation partnership project 2" (3GPP 2). The techniques described herein may be used for both the above-mentioned systems and radio technologies, as well as for other systems and radio technologies.

Embodiments of the present invention are described below with reference to the accompanying drawings. The method for compressing the Ethernet packet header, the method for decompressing the Ethernet packet header and the equipment provided by the embodiment of the invention can be applied to a wireless communication system.

Fig. 2 is a block diagram of a wireless communication system according to an embodiment of the present invention. As shown in fig. 2, the wireless communication system may include: network Equipment 20 and a terminal, denoted User Equipment (UE) 21, UE21 may communicate (transmit signaling or transmit data) with network Equipment 20. In practical applications, the connections between the above devices may be wireless connections, and fig. 2 is illustrated with solid lines for convenience and intuition of the connection relationships between the devices. It should be noted that the communication system may include a plurality of UEs 21, and the network device 20 may communicate with a plurality of UEs 21.

The terminal provided by the embodiment of the invention can be a Mobile phone, a tablet Computer, a notebook Computer, an Ultra-Mobile Personal Computer (UMPC), a netbook or a Personal Digital Assistant (PDA), a Mobile Internet Device (MID), a Wearable Device (Wearable Device), a vehicle-mounted Device, or the like.

The network device 20 provided in the embodiment of the present invention may be a base station, which may be a commonly used base station, an evolved node base station (eNB), or a network device in a 5G system (e.g., a next generation base station (gNB) or a Transmission and Reception Point (TRP)).

Referring to fig. 3, an embodiment of the present invention provides a method for packet header compression, where an execution main body of the method may be a sending end, and the sending end may be a terminal or a network device, and the method includes the following specific steps:

step 301: and performing packet header compression processing on a first packet header and a second packet header in a first data packet by using a transmitting PDCP entity of the transmitting end to obtain a first compressed packet header and a second compressed packet header, wherein the first packet header or the second packet header is an Ethernet packet header.

Wherein, the first packet header is an Ethernet packet header, and the second packet header is a TCP/IP packet header; alternatively, the first packet header is an ethernet packet header, and the second packet header is a Real-time Transport Protocol (RTP)/User Datagram Protocol (UDP)/IP packet header, but is not limited thereto.

In this embodiment of the present invention, optionally, the method further includes: receiving a second data packet (e.g., a PDCP control protocol data unit, PDU) by a receiving PDCP entity of the transmitting end, where the second data packet includes feedback information;

wherein the feedback information is compression feedback for the first packet header or compression feedback for the second packet header generated by an ROHC entity at a receiving end.

In this embodiment of the present invention, optionally, after the receiving the second data packet by the receiving PDCP entity of the transmitting end, the method further includes:

acquiring first indication information from a PDCP subheader of the second data packet, wherein the first indication information is used for indicating that the feedback information is compression feedback aiming at a first packet header or compression feedback aiming at a second packet header; and sending the feedback information to a corresponding ROHC entity of the sending end according to the first indication information, and further adjusting the compression state of the ROHC entity of the sending end.

In this embodiment of the present invention, optionally, the performing, by the sending PDCP entity of the sending end, a header compression process on a first header and a second header in a first data packet to obtain a first compressed header and a second compressed header includes:

respectively transmitting the first packet header and the second packet header in the first data packet to corresponding ROHC entities through a transmitting PDCP entity of the transmitting end;

respectively compressing the first packet header and the second packet header through ROHC entities corresponding to the first packet header and the second packet header to obtain a first compressed packet header and a second compressed packet header;

obtaining a third data packet containing the first compressed packet header, the second compressed packet header and the data to be processed according to the first compressed packet header, the second compressed packet header and the data to be processed in the first data packet;

adding a first PDCP subheader to the third data packet, wherein the first PDCP subheader comprises information indicating the length of the first compressed packet header and/or the second compressed packet header.

sending the first data packet to an ROHC entity corresponding to the first packet header through a sending PDCP entity of the sending end;

performing packet header compression processing on the first packet header through an ROHC entity corresponding to the first packet header to obtain a first compressed packet header;

obtaining a fourth data packet containing the first compressed packet header, the second packet header and the data to be processed according to the first compressed packet header, the second packet header in the first data packet and the data to be processed;

sending the fourth data packet to an ROHC entity corresponding to the second packet header, and performing packet header compression processing on the second packet header through the ROHC entity corresponding to the second packet header to obtain a fifth data packet including the first compressed packet header, the second compressed packet header and data to be processed;

and adding a second PDCP subheader to the fifth data packet, wherein the second PDCP subheader comprises related information used for indicating the length of the first compressed packet header and/or the second compressed packet header.

In this embodiment of the present invention, optionally, the first PDCP subheader or the second PDCP subheader includes: second indication information, the second indication information comprising at least one of:

first information for indicating a length of the first compressed packet header;

second information indicating a length of the second compressed packet header.

performing packet header compression processing on the first packet header through an ROHC entity corresponding to the first packet header to obtain a first compressed packet header, and performing packet header compression processing on the second packet header through an ROHC entity corresponding to the second packet header to obtain a second compressed packet header;

determining a sixth data packet carrying the first compressed packet header;

obtaining a seventh data packet containing the second compressed packet header and the data to be processed according to the second compressed packet header and the data to be processed in the first data packet;

a sequence number (or referred to as a sequence number field) in a PDCP subheader of the sixth data packet is the same as a sequence number in a PDCP subheader of the seventh data packet, and the PDCP subheader of the sixth data packet carries third indication information, where the third indication information is used to indicate that the sixth data packet includes the first compressed packet header.

It is understood that the sixth data packet (PDCP PDU) including the first compressed header does not affect the repetitive detection and reordering of the seventh data packet (PDCP PDU) including the second compressed header and the data to be processed.

obtaining an eighth data packet containing the second packet header and the data to be processed according to the second packet header and the data to be processed in the first data packet;

sending the eighth data packet to an ROHC entity corresponding to the second packet header, and performing packet header compression processing on the second packet header through the ROHC entity corresponding to the second packet header to obtain a second compressed packet header;

determining a ninth data packet carrying the first compressed packet header;

obtaining a tenth data packet containing the second compressed packet header and the data to be processed according to the second compressed packet header and the data to be processed in the eighth data packet;

the sequence number in the PDCP subheader of the ninth data packet is the same as the sequence number in the PDCP subheader of the tenth data packet, and the PDCP subheader of the ninth data packet carries fourth indication information, where the fourth indication information is used to indicate that the ninth data packet includes the first compressed packet header.

Referring to fig. 4, an embodiment of the present invention provides a method for decompressing a packet header, where an execution main body of the method may be a receiving end, and the receiving end may be a network device or a terminal, and the method includes the following specific steps:

step 401: receiving a first compressed packet header and a second compressed packet header through a receiving PDCP entity of the receiving end;

step 402: and performing packet header decompression processing on the first compressed packet header and the second compressed packet header to obtain a first packet header and a second packet header, wherein the first packet header or the second packet header is an ethernet packet header.

Wherein, the first packet header is an Ethernet packet header, and the second packet header is a TCP/IP packet header; alternatively, the first packet header is an ethernet packet header, and the second packet header is an RTP/UDP/IP packet header, but is not limited thereto.

In this embodiment of the present invention, optionally, the method further includes:

sending a second data packet through a sending PDCP entity of the receiving end, wherein the second data packet comprises feedback information;

wherein the feedback information is compressed feedback for the first packet header or compressed feedback for the second packet header.

In this embodiment of the present invention, optionally, the PDCP subheader of the second data packet includes first indication information, where the first indication information is used to indicate that the feedback information is compression feedback for the first packet header or compression feedback for the second packet header.

In this embodiment of the present invention, optionally, the receiving, by the receiving PDCP entity at the receiving end, the first compressed packet header and the second compressed packet header includes:

receiving a second data packet containing the first compressed packet header, a second compressed packet header and data to be processed by a receiving PDCP entity of the receiving end;

acquiring the first compressed packet header and the second compressed packet header from the third data packet;

the performing packet header decompression processing on the first compressed packet header and the second compressed packet header to obtain a first packet header and a second packet header includes:

sending the first compressed packet header and the second compressed packet header to corresponding ROHC entities;

respectively decompressing the first compressed packet header and the second compressed packet header through ROHC entities corresponding to the first compressed packet header and the second compressed packet header to obtain the first packet header and the second packet header;

and obtaining a first data packet containing the first packet header, the second packet header and the data to be processed according to the first packet header, the second packet header and the data to be processed.

In this embodiment of the present invention, optionally, the obtaining the first compressed packet header and the second compressed packet from the second data packet includes: and acquiring the first compressed packet header and the second compressed packet header from the third data packet according to a first PDCP subheader of the third data packet, wherein the first PDCP subheader comprises information indicating the length of the first compressed packet header and/or the second compressed packet header.

receiving, by a receiving PDCP entity of the receiving end, a fifth data packet including a first compressed packet header, a second compressed packet header, and data to be processed, where the fifth data packet includes a second PDCP subheader, and the second PDCP subheader includes related information for indicating a length of the first compressed packet header and/or the second compressed packet header;

sending the fifth data packet to an ROHC entity corresponding to the second compressed packet header for decompression to obtain a fourth data packet containing the first compressed packet header, the second packet header and data to be processed;

and sending the fourth data packet to an ROHC entity corresponding to the first compressed packet header for decompression to obtain a first data packet containing the first packet header, the second packet header and the data to be processed.

receiving a sixth data packet containing the first compressed packet header and a seventh data packet containing the second compressed packet header and the data to be processed by a receiving PDCP entity of the receiving end;

the receiving the first compressed packet header and the second compressed packet header by the receiving PDCP entity of the receiving end includes:

respectively sending the first compressed packet header in the sixth data packet and the second compressed packet header in the seventh data packet to corresponding ROHC entities for decompression processing to obtain the first packet header and the second packet header;

obtaining a first data packet through the data to be processed in the first packet header, the second packet header and the seventh data packet;

wherein, a sequence number in the PDCP subheader of the sixth data packet is the same as a sequence number in the PDCP subheader of the seventh data packet, and the PDCP subheader of the sixth data packet carries third indication information, where the third indication information is used to indicate that the sixth data packet includes the first compressed packet header.

receiving a ninth data packet containing the first compressed packet header and a tenth data packet containing the second compressed packet header and data to be processed by a receiving PDCP entity of the receiving end;

sending the tenth data packet to an ROHC entity corresponding to the second compressed packet header for decompression processing, so as to obtain an eighth data packet including the second packet header and data to be processed;

sending the ninth data packet to an ROHC entity corresponding to the first compressed packet header for decompression processing to obtain the first packet header;

obtaining a first data packet through the first packet header and the eighth data packet;

The following describes a packet header compression and packet header decompression processing flow according to an embodiment of the present invention with reference to examples 1 to 4.

Example 1: and performing compression or decompression processing on two packet headers in parallel, wherein the PDCP subheader carries indication information.

Step 0: the network equipment configuration terminal performs packet header compression processing on data carried by the network equipment configuration terminal;

step 1: a sending PDCP entity of the terminal receives a data packet (e.g., PDCP SDU) from a higher layer, and performs header compression on the data packet to obtain a data packet with a compressed header, which specifically includes the following steps:

step 1.1: extracting a first packet header (e.g., the first packet header may be an Ethernet header) and a second packet header (e.g., the second packet header may be a TCP/IP header) from the received data packet, and submitting the first packet header and the second packet header to a different ROHC entity;

step 1.2: the ROHC entity compresses the first packet header and the second packet header by using a specific profile (for example, for the first packet header, adopting a packet header compression algorithm for Ethernet), and generates a corresponding first compressed packet header and a corresponding second compressed packet header;

step 1.3: recombining a data packet (or called a compressed packet) with a first compressed packet header and a second compressed packet header according to the first compressed packet header and the second compressed packet header obtained by header compression;

step 1.4: adding a PDCP subheader to a data packet comprising a first compressed packet header and a second compressed packet header, wherein the PDCP subheader can carry indication information, and the indication information comprises at least one of the following contents:

first indication information, which is used to indicate the length of the first compressed packet header (for example, the first compressed packet header may also be called Ethernet compressed header);

second indication information indicating a length of a second compressed packet header (e.g., the second compressed packet header may also be referred to as a TCP/IP compressed header);

step 2: a receiving PDCP entity of the network device receives a data packet (e.g., PDCP data PDU) from a lower layer, where the data packet includes a first compressed packet header and a second compressed packet header, and performs a header decompression process on the received data packet before delivering a PDCP SDU to an upper layer, where the specific actions are as follows:

step 2.1: extracting a first compressed header (for example: Ethernet compressed header) and a second compressed header (for example: TCP/IP compressed header) from the received data packet according to the indication information carried in the PDCP subheader corresponding to the data packet, and delivering the first compressed header and the second compressed header to different ROHC entities;

step 2.2: the ROHC entity uses a specific profile to decompress the first compressed packet header and the second compressed packet header and generate a corresponding original packet header;

step 2.3: according to the original first packet header and the original second packet header obtained by decompressing the packet header, an uncompressed data packet (PDCP SDU) is obtained by recombination;

and step 3: additionally, the ROHC entity of the network device generates discrete feedback information, and when the sending PDCP entity of the network device sends PDCP control PDUs containing the feedback information, the corresponding behavior is as follows:

step 3.1: carrying indication information in a PDCP control PDU subheader to indicate whether the feedback information is compression feedback to a first packet header or compression feedback to a second packet header;

step 3.2: the indication information may be a one-bit indication information, and the corresponding PDCP control PDU format is illustrated in fig. 1.

When the value of the H field is '0', the feedback information is the compression feedback aiming at the first packet header; and when the value of the H domain is 1, the feedback information is the compression feedback aiming at the second packet header.

And 4, step 4: a receiving PDCP entity of the terminal receives a PDCP Control PDU containing feedback information from a bottom layer (Radio Link Control (RLC) layer), and the corresponding behavior is as follows:

step 4.1: reading indication information (for example, H domain) carried in a sub-header of the PDCP control PDU, and submitting the indication information to a corresponding ROHC entity (for example, when the H domain is 0, submitting the PDCP control PDU to the ROHC entity corresponding to the first packet header);

step 4.2: based on the feedback information, the terminal adjusts the compression state of the corresponding ROHC entity;

example 2: and performing compression or decompression processing on two packet headers in parallel, wherein the PDCP SDU carries the first compressed packet header.

step 1: a sending PDCP entity of the terminal receives a data packet (PDCP SDU) from a higher layer, and performs header compression processing on the received data packet to obtain a data packet with a compressed header, which specifically acts as follows:

step 1.1: extracting a first packet header (for example, the first packet header may be an Ethernet header) and a second packet header (for example, the second packet header may be a TCP/IP header) from the received data packet, and delivering to different ROHC entities;

step 1.2: the ROHC entity compresses the first packet header and the second packet header by using a specific profile (for example, for the first packet header, adopting a packet header compression algorithm aiming at Ethernet), and generates a corresponding first compressed packet header and a corresponding second compressed packet header;

step 1.3: recombining a data packet (or called a compressed packet) only including a second compressed packet header according to a first compressed packet header and the second compressed packet header obtained by header compression;

step 1.4: a PDCP subheader is added to the data packet containing the second compressed header. The first compressed header is stored in one PDCP SDU and associated with a PDCP PDU containing the second compressed header. The specific association relationship is as follows:

(1) a Sequence Number (SN) field carried by a PDCP subheader of the PDCP PDU containing the first compressed packet header is the same as an SN field carried by a PDCP subheader of the PDCP PDU containing the second compressed packet header;

(2) the PDCP subheader of the PDCP PDU containing the first compressed packet header carries an indicating bit which is used for indicating that the PDCP PDU carries the first compressed packet header;

when transmitting the PDCP PDU containing the first compressed packet header, the transmitting PDCP entity does not update a transmitting state variable, and when receiving the PDCP PDU, the receiving PDCP entity does not perform repeated detection based on SN;

different from example 1, the first compressed packet header is stored in the PDCP SDU and transmitted in the form of PDCP PDU, so that the receiving end can extract the first compressed packet header for header decompression;

step 2: a receiving PDCP entity of the network device receives a data packet (PDCP data PDU) having a first compressed header and a second compressed header from a lower layer, and performs header decompression on the received data packet before delivering a PDCP SDU to an upper layer, specifically as follows:

step 2.1: extracting a first compressed header (for example, the first compressed header may also be referred to as an Ethernet compressed header) and a second compressed header (for example, the second compressed header may also be referred to as a TCP/IP compressed header) from the received data packet, and delivering the first compressed header and the second compressed header to different ROHC entities;

step 2.3: according to the original first packet header and the original second packet header obtained by decompressing the packet header, an uncompressed original data packet (PDCP SDU) is obtained by recombination;

step 3-4: the same contents as those of steps 3 to 4 of example 1 will not be described here.

Example 3: and sequentially performing compression or decompression processing on the two types of packet headers, wherein the PDCP subheaders carry indication information.

Step 0: the same contents as those of step 0 of example 1 are not described herein;

step 1: a sending PDCP entity of the terminal receives a data packet (e.g., PDCP SDU) from a higher layer, and performs header compression on the data packet to obtain a data packet with a compressed header, which specifically acts as follows:

step 1.1: delivering the data packet from the higher layer to an ROHC entity corresponding to the first packet header;

step 1.2: removing a Service Data Adaptation Protocol (SDAP) sub-header or an SDAP control PDU (if the SDAP control PDU is contained), and performing header compression on a first packet header by using a specific profile by the ROHC entity to generate a corresponding first compressed packet header;

step 1.3: reconstructing a data packet (or referred to as a compressed packet) including a first compressed packet header according to the first compressed packet header obtained by compressing the packet header;

step 1.4: delivering the data packet containing the first compressed packet header to an ROHC entity corresponding to the second packet header;

step 1.5: removing the SDAP subheader or the SDAP control PDU (if contained) and the first compressed packet header, performing header compression on the second packet header by using a specific profile, and generating a corresponding second compressed packet header;

step 1.6: recombining a second compressed packet header obtained by compressing the packet header to obtain a data packet with the first compressed packet header and the second compressed packet header;

step 1.7: the same as in step 1.4 of example 1, and will not be described again here;

step 2: a receiving PDCP entity of the network device receives a data packet (PDCP PDU) containing a first compressed packet header and a second compressed packet header from a lower layer, and performs header decompression on the received data packet when delivering a PDCP SDU to an upper layer, specifically as follows:

step 2.1: delivering the data packet from the bottom layer to an ROHC entity corresponding to the second packet header;

step 2.2: removing the SDAP subheader or the SDAP control PDU (if the SDAP control PDU and the first compressed packet header) according to the indication information carried in the PDCP subheader corresponding to the compressed data packet, and decompressing the second compressed packet header by using specific profile to obtain an original second packet header;

step 2.3: based on the original second packet header obtained by decompression, recombining to obtain a data packet only containing the first compressed packet header;

step 2.4: delivering the data packet only containing the first compressed packet header to an ROHC entity corresponding to the first packet header;

step 2.5: removing the SDAP subheader or the SDAP control PDU (if included), decompressing the first compressed packet header using a specific profile (e.g., applying a header compression algorithm for ethernet to the first packet header), and generating a corresponding original first packet header;

step 2.6: according to the original first packet head obtained by head decompression, an uncompressed data packet (PDCP SDU) is obtained by recombination;

Example 4: and sequentially performing compression/decompression processing on the two types of packet headers, wherein the PDCP SDU carries the first compressed packet header.

step 1, a sending PDCP entity of a terminal receives a data packet (for example, PDCP SDU) from a high layer and carries out packet header compression processing on the data packet to obtain the data packet with a compressed packet header, and the concrete actions are as follows:

step 1.1: delivering the data packet from the higher layer to an ROHC entity corresponding to the first packet header (or called a first packet header special ROHC entity);

step 1.2: removing the SDAP subheader or the SDAP control PDU (if the SDAP subheader or the SDAP control PDU is contained), and performing header compression on the first packet header by using a specific profile by the ROHC entity to generate a corresponding first compressed packet header;

step 1.3: according to a first compressed packet header obtained by compressing the packet header, recombining to obtain a data packet containing the first compressed packet header;

step 1.5: removing the SDAP subheader or the SDAP control PDU (if the SDAP subheader or the SDAP control PDU is contained), performing header compression on the second packet header by using specific profile, and generating a corresponding second compressed packet header;

step 1.6: recombining a second compressed packet header obtained according to the packet header compression to obtain a data packet with the second compressed packet header;

step 1.7: a PDCP subheader is added to the data packet containing the second compressed header. The first compressed header is stored in one PDCP SDU and associated with a PDCP PDU containing the second compressed header. The specific association relationship is as follows:

(1) the SN domain carried by the PDCP subheader of the PDCP PDU containing the first compressed packet header is the same as the SN domain carried by the PDCP subheader of the PDCP PDU containing the second compressed packet header;

when transmitting the PDCP PDU containing the first compressed packet header, the transmitting PDCP entity does not update a transmitting state variable, and the receiving PDCP entity does not perform repeated detection based on SN when receiving the packet;

unlike example 3, the first compressed packet header is stored in the PDCP SDU and transmitted in the form of PDCP PDU, which facilitates the receiving end to extract the first compressed packet header for decompression;

step 2: a receiving PDCP entity of the network device receives a data packet (PDCP data PDU) with a compressed header from a lower layer, and performs header decompression on the received data packet before delivering a PDCP SDU to an upper layer, specifically as follows:

step 2.1: delivering the PDCP SDU containing the first compressed packet header to an ROHC entity corresponding to the first packet header;

step 2.2: the ROHC entity uses a specific profile to decompress the packet header of the first compressed packet header and generates a corresponding original first packet header;

step 2.3: recombining to obtain a data packet containing a second compressed packet header according to an original first packet header obtained by decompressing the packet header and a PDCP SDU containing the second compressed packet header, and submitting the data packet to an ROHC entity corresponding to the second compressed packet header;

step 2.4: the ROHC entity uses specific profile to decompress the packet header of the second compressed packet header, generate an original second packet header and obtain an uncompressed original data packet;

The embodiment of the invention also provides a sending end, and as the principle of solving the problems of the sending end is similar to the method for compressing the packet header in the embodiment of the invention, the implementation of the sending end can refer to the implementation of the method, and repeated parts are not described again.

Referring to fig. 5, an embodiment of the present invention further provides a sending end, where the sending end 500 includes:

a compressing module 501, configured to perform packet header compression processing on a first packet header and a second packet header in a first data packet through a sending PDCP entity of the sending end, so as to obtain a first compressed packet header and a second compressed packet header, where the first packet header or the second packet header is an ethernet packet header.

In this embodiment of the present invention, optionally, the sending end further includes:

a receiving module, configured to receive a second data packet through a receiving PDCP entity of the sending end, where the second data packet includes feedback information;

an obtaining module, configured to obtain first indication information from a PDCP subheader of the second data packet, where the first indication information is used to indicate that the feedback information is compression feedback for the first packet header or compression feedback for the second packet header; according to the first indication information, the feedback information is sent to a corresponding ROHC entity of the sending end; further, the compression state of the ROHC entity of the corresponding sender may be adjusted.

In this embodiment of the present invention, optionally, the compression module is further configured to:

obtaining a third data packet containing the first compressed packet header and the second compressed packet header according to the first compressed packet header, the second compressed packet header and the data to be processed in the first data packet;

second information indicating a length of the second compressed packet header.

determining a sixth data packet carrying the first compressed packet header;

determining a ninth data packet carrying the first compressed packet header;

The sending end provided by the embodiment of the present invention may execute the method embodiments described above, and the implementation principle and the technical effect are similar, which are not described herein again.

The embodiment of the invention also provides a receiving end, and as the principle of solving the problem of the receiving end is similar to the method for decompressing the packet header in the embodiment of the invention, the implementation of the receiving end can refer to the implementation of the method, and repeated parts are not repeated.

Referring to fig. 6, an embodiment of the present invention further provides a receiving end, where the receiving end 600 includes:

a receiving module 601, configured to receive the first compressed packet header and the second compressed packet header through a receiving PDCP entity of the receiving end;

a decompression module 602, configured to perform packet header decompression processing on the first compressed packet header and the second compressed packet header to obtain a first packet header and a second packet header, where the first packet header or the second packet header is an ethernet packet header.

In this embodiment of the present invention, optionally, the receiving end further includes:

a sending module, configured to send a second data packet through a sending PDCP entity of the receiving end, where the second data packet includes feedback information;

In this embodiment of the present invention, optionally, the receiving module is further configured to:

receiving a third data packet containing the first compressed packet header, the second compressed packet header and data to be processed by a receiving PDCP entity of the receiving end;

the decompression module is further to:

and acquiring the first compressed packet header and the second compressed packet header from the third data packet according to a first PDCP subheader of the third data packet, wherein the first PDCP subheader comprises information indicating the length of the first compressed packet header and/or the second compressed packet header.

In this embodiment of the present invention, optionally, the receiving module is further configured to: receiving, by a receiving PDCP entity of the receiving end, a fourth data packet including a first compressed packet header, a second compressed packet header, and data to be processed, where the fourth data packet includes a second PDCP subheader, and the second PDCP subheader is used to indicate a length of the first compressed packet header and/or the second compressed packet header;

in this embodiment of the present invention, optionally, the receiving module is further configured to: receiving, by a receiving PDCP entity of the receiving end, a fifth data packet including a first compressed packet header, a second compressed packet header, and data to be processed, where the fifth data packet includes a second PDCP subheader, and the second PDCP subheader includes related information for indicating a length of the first compressed packet header and/or the second compressed packet header;

the decompression module is further to: sending the fifth data packet to an ROHC entity corresponding to the second compressed packet header for decompression to obtain a fourth data packet containing the first compressed packet header, the second packet header and data to be processed; and sending the fourth data packet to an ROHC entity corresponding to the first compressed packet header for decompression to obtain a first data packet containing the first packet header, the second packet header and the data to be processed.

In this embodiment of the present invention, optionally, the receiving module is further configured to: receiving a sixth data packet containing the first compressed packet header and a seventh data packet containing the second compressed packet header and the data to be processed by a receiving PDCP entity of the receiving end;

the decompression module is further to:

respectively sending the first compressed packet header in the sixth data packet and the second compressed packet header in the seventh data packet to corresponding ROHC entities for decompression processing to obtain the first packet header and the second packet header; obtaining a first data packet through the data to be processed in the first packet header, the second packet header and the seventh data packet;

In this embodiment of the present invention, optionally, the receiving module is further configured to: receiving a ninth data packet containing the first compressed packet header and a tenth data packet containing the second compressed packet header and data to be processed by a receiving PDCP entity of the receiving end;

the decompression module is further to: sending the tenth data packet to an ROHC entity corresponding to the second compressed packet header for decompression processing, so as to obtain an eighth data packet including the second packet header and data to be processed; sending the ninth data packet to an ROHC entity corresponding to the first compressed packet header for decompression processing to obtain the first packet header; obtaining a first data packet through the first packet header and the eighth data packet; the sequence number in the PDCP subheader of the ninth data packet is the same as the sequence number in the PDCP subheader of the tenth data packet, and the PDCP subheader of the ninth data packet carries fourth indication information, where the fourth indication information is used to indicate that the ninth data packet includes the first compressed packet header.

The receiving end provided by the embodiment of the present invention may execute the above method embodiment, and the implementation principle and technical effect are similar, which are not described herein again.

As shown in fig. 7, the terminal 700 shown in fig. 7 includes: at least one processor 701, a memory 702, at least one network interface 704, and a user interface 703. The various components in the terminal 700 are coupled together by a bus system 705. It is understood that the bus system 705 is used to enable communications among the components. The bus system 705 includes a power bus, a control bus, and a status signal bus in addition to a data bus. But for clarity of illustration the various busses are labeled in figure 7 as the bus system 705.

The user interface 703 may include, among other things, a display, a keyboard, or a pointing device (e.g., a mouse, trackball, touch pad, or touch screen, among others.

It is to be understood that the memory 702 in embodiments of the present invention may be either volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. The non-volatile Memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically Erasable PROM (EEPROM), or a flash Memory. Volatile Memory can be Random Access Memory (RAM), which acts as external cache Memory. By way of illustration, and not limitation, many forms of RAM are available, such as Static random access memory (Static RAM, SRAM), Dynamic Random Access Memory (DRAM), Synchronous Dynamic random access memory (Synchronous DRAM, SDRAM), Double Data rate Synchronous Dynamic random access memory (ddr DRAM), Enhanced Synchronous SDRAM (ESDRAM), Synchronous link SDRAM (SLDRAM), and Direct Rambus RAM (DRRAM). The memory 702 of the systems and methods described in this embodiment of the invention is intended to comprise, without being limited to, these and any other suitable types of memory.

In some embodiments, memory 702 holds the following elements, executable modules or data structures, or a subset thereof, or an expanded set thereof: an operating system 7021 and application programs 7022.

The operating system 7021 includes various system programs, such as a framework layer, a core library layer, a driver layer, and the like, for implementing various basic services and processing hardware-based tasks. The application 7022 includes various applications, such as a Media Player (Media Player), a Browser (Browser), and the like, for implementing various application services. Programs that implement methods in accordance with embodiments of the present invention can be included within application program 7022.

In an embodiment of the present invention, by calling a program or an instruction stored in the memory 702, specifically, a program or an instruction stored in the application 7022, the following steps are implemented when the program or the instruction is executed: and performing packet header compression processing on a first packet header and a second packet header in a first data packet by using a Packet Data Convergence Protocol (PDCP) entity of the sending end to obtain a first compressed packet header and a second compressed packet header, wherein the first packet header or the second packet header is an Ethernet packet header.

In another embodiment of the present invention, by calling a program or an instruction stored in the memory 702, specifically, a program or an instruction stored in the application 7022, the following steps are implemented when executing: receiving a first compressed packet header and a second compressed packet header through a receiving PDCP entity of the receiving end; and performing packet header decompression processing on the first compressed packet header and the second compressed packet header to obtain a first packet header and a second packet header, wherein the first packet header or the second packet header is an ethernet packet header.

The terminal device provided by the embodiment of the present invention may execute the method embodiment, and the implementation principle and the technical effect are similar, which are not described herein again.

Referring to fig. 8, fig. 8 is a structural diagram of a network device applied in the embodiment of the present invention, and as shown in fig. 8, the network device 800 includes: a processor 801, a transceiver 802, a memory 803, and a bus interface, wherein:

in one embodiment of the present invention, the network device 800 further includes: a program stored on the memory 803 and executable on the processor 801, which when executed by the processor 801, performs the steps of: receiving a first compressed packet header and a second compressed packet header through a receiving PDCP entity of the receiving end; and performing packet header decompression processing on the first compressed packet header and the second compressed packet header to obtain a first packet header and a second packet header, wherein the first packet header or the second packet header is an ethernet packet header.

In another embodiment of the present invention, the network device 800 further includes: a program stored on the memory 803 and executable on the processor 801, which when executed by the processor 801, performs the steps of: and performing packet header compression processing on a first packet header and a second packet header in a first data packet by using a transmitting PDCP entity of the transmitting end to obtain a first compressed packet header and a second compressed packet header, wherein the first packet header or the second packet header is an Ethernet packet header.

In FIG. 8, the bus architecture may include any number of interconnected buses and bridges, with one or more processors, represented by the processor 801, and various circuits, represented by the memory 803, linked together. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further herein. The bus interface provides an interface. The transceiver 802 may be a number of elements including a transmitter and a receiver that provide a means for communicating with various other apparatus over a transmission medium.

The processor 801 is responsible for managing the bus architecture and general processing, and the memory 803 may store data used by the processor 801 in performing operations.

The network device provided by the embodiment of the present invention may execute the above method embodiment, and the implementation principle and technical effect are similar, which are not described herein again.

The steps of a method or algorithm described in connection with the disclosure herein may be embodied in hardware or in software instructions executed by a processor. The software instructions may consist of corresponding software modules that may be stored in RAM, flash memory, ROM, EPROM, EEPROM, registers, hard disk, a removable hard disk, a compact disk, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium. Of course, the storage medium may also be integral to the processor. The processor and the storage medium may reside in an ASIC. Additionally, the ASIC may reside in a core network interface device. Of course, the processor and the storage medium may reside as discrete components in a core network interface device.

Those skilled in the art will recognize that, in one or more of the examples described above, the functions described in this invention may be implemented in hardware, software, firmware, or any combination thereof. When implemented in software, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A storage media may be any available media that can be accessed by a general purpose or special purpose computer.

The above-mentioned embodiments, objects, technical solutions and advantages of the present invention are further described in detail, it should be understood that the above-mentioned embodiments are only exemplary embodiments of the present invention, and are not intended to limit the scope of the present invention, and any modifications, equivalent substitutions, improvements and the like made on the basis of the technical solutions of the present invention should be included in the scope of the present invention.

As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, embodiments of the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, embodiments of the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

Embodiments of the present invention are described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

It will be apparent to those skilled in the art that various changes and modifications may be made in the embodiments of the present invention without departing from the spirit and scope of the invention. Thus, if such modifications and variations of the embodiments of the present invention fall within the scope of the claims of the present invention and their equivalents, the present invention is also intended to encompass such modifications and variations.

Claims

1. A method for compressing packet header is applied to a sending end, and is characterized in that the method comprises the following steps:

performing packet header compression processing on a first packet header and a second packet header in a first data packet by using a Packet Data Convergence Protocol (PDCP) entity of the sending end to obtain a first compressed packet header and a second compressed packet header, wherein the first packet header or the second packet header is an Ethernet packet header; the said performing packet header compression processing on the first packet header and the second packet header in the first data packet by the sending PDCP entity of the sending end to obtain a first compressed packet header and a second compressed packet header, includes:

adding a first PDCP subheader to the third data packet, wherein the first PDCP subheader comprises information indicating the length of the first compressed packet header and/or the second compressed packet header;

or, the performing, by the sending PDCP entity of the sending end, a header compression process on a first header and a second header in a first data packet to obtain a first compressed header and a second compressed header includes:

adding a second PDCP subheader to the fifth data packet, wherein the second PDCP subheader includes related information for indicating the length of the first and/or second compressed packet header;

determining a sixth data packet carrying the first compressed packet header;

wherein, a sequence number in the PDCP subheader of the sixth data packet is the same as a sequence number in the PDCP subheader of the seventh data packet, and the PDCP subheader of the sixth data packet carries third indication information, where the third indication information is used to indicate that the sixth data packet includes the first compressed packet header;

determining a ninth data packet carrying the first compressed packet header;

2. The method of claim 1, further comprising:

receiving a second data packet through a receiving PDCP entity of the sending end, wherein the second data packet comprises feedback information;

3. The method of claim 2, wherein after the receiving of the second data packet by the receiving PDCP entity of the transmitting end, the method further comprises:

acquiring first indication information from a PDCP subheader of the second data packet, wherein the first indication information is used for indicating that the feedback information is compression feedback aiming at the first packet header or compression feedback aiming at the second packet header;

and sending the feedback information to a corresponding ROHC entity of the sending end according to the first indication information.

4. The method of claim 1, wherein the first header and the second header in the first data packet are respectively transmitted to corresponding ROHC entities at a transmitting PDCP entity at the transmitting end; respectively compressing the first packet header and the second packet header through ROHC entities corresponding to the first packet header and the second packet header to obtain a first compressed packet header and a second compressed packet header; obtaining a third data packet including the first compressed packet header and the second compressed packet header according to the first compressed packet header, the second compressed packet header and the data to be processed in the first data packet, where the third data packet includes a first PDCP subheader or is sent to an ROHC entity corresponding to the first packet header through a sending PDCP entity of the sending end; performing packet header compression processing on the first packet header through an ROHC entity corresponding to the first packet header to obtain a first compressed packet header; obtaining a fourth data packet containing the first compressed packet header, the second packet header and the data to be processed according to the first compressed packet header, the second packet header in the first data packet and the data to be processed; sending the fourth data packet to an ROHC entity corresponding to the second packet header, performing packet header compression processing on the second packet header through the ROHC entity corresponding to the second packet header to obtain a fifth data packet including the first compressed packet header, the second compressed packet header and the data to be processed, where the fifth data packet includes a second PDCP subheader,

the first or second PDCP subheader comprises: second indication information, the second indication information comprising at least one of:

second information indicating a length of the second compressed packet header.

5. A method for decompressing packet header is applied to a receiving end, and is characterized in that the method comprises the following steps:

performing packet header decompression processing on the first compressed packet header and the second compressed packet header to obtain a first packet header and a second packet header, wherein the first packet header or the second packet header is an ethernet packet header;

acquiring the first compressed packet header and the second compressed packet header from the third data packet according to a first PDCP subheader of the third data packet, wherein the first PDCP subheader comprises information indicating the length of the first compressed packet header and/or the second compressed packet header;

obtaining a first data packet containing the first packet header, the second packet header and the data to be processed according to the first packet header, the second packet header and the data to be processed;

or, the receiving, by the receiving PDCP entity of the receiving end, the first compressed packet header and the second compressed packet header includes:

sending the fourth data packet to an ROHC entity corresponding to the first compressed packet header for decompression to obtain a first data packet containing the first packet header, a second packet header and data to be processed;

6. The method of claim 5, further comprising:

7. The method of claim 6, wherein the PDCP subheader of the second packet contains first indication information, wherein the first indication information is used to indicate whether the feedback information is compressed feedback for the first packet header or compressed feedback for the second packet header.

8. A transmitting end, comprising:

a compression module, configured to perform packet header compression processing on a first packet header and a second packet header in a first data packet through a sending PDCP entity of the sending end to obtain a first compressed packet header and a second compressed packet header, where the first packet header or the second packet header is an ethernet packet header;

the compression module is further to: respectively transmitting the first packet header and the second packet header in the first data packet to corresponding ROHC entities through a transmitting PDCP entity of the transmitting end; respectively compressing the first packet header and the second packet header through ROHC entities corresponding to the first packet header and the second packet header to obtain a first compressed packet header and a second compressed packet header; obtaining a third data packet containing the first compressed packet header and the second compressed packet header according to the first compressed packet header, the second compressed packet header and the data to be processed in the first data packet; adding a first PDCP subheader to the third data packet, wherein the first PDCP subheader comprises information indicating the length of the first compressed packet header and/or the second compressed packet header;

or, the compression module is further configured to: sending the first data packet to an ROHC entity corresponding to the first packet header through a sending PDCP entity of the sending end; performing packet header compression processing on the first packet header through an ROHC entity corresponding to the first packet header to obtain a first compressed packet header; obtaining a fourth data packet containing the first compressed packet header, the second packet header and the data to be processed according to the first compressed packet header, the second packet header in the first data packet and the data to be processed; sending the fourth data packet to an ROHC entity corresponding to the second packet header, and performing packet header compression processing on the second packet header through the ROHC entity corresponding to the second packet header to obtain a fifth data packet including the first compressed packet header, the second compressed packet header and data to be processed; adding a second PDCP subheader to the fifth data packet, wherein the second PDCP subheader includes related information for indicating the length of the first and/or second compressed packet header;

or, the compression module is further configured to: respectively transmitting the first packet header and the second packet header in the first data packet to corresponding ROHC entities through a transmitting PDCP entity of the transmitting end; performing packet header compression processing on the first packet header through an ROHC entity corresponding to the first packet header to obtain a first compressed packet header, and performing packet header compression processing on the second packet header through an ROHC entity corresponding to the second packet header to obtain a second compressed packet header; determining a sixth data packet carrying the first compressed packet header; obtaining a seventh data packet containing the second compressed packet header and the data to be processed according to the second compressed packet header and the data to be processed in the first data packet; wherein, a sequence number in the PDCP subheader of the sixth data packet is the same as a sequence number in the PDCP subheader of the seventh data packet, and the PDCP subheader of the sixth data packet carries third indication information, where the third indication information is used to indicate that the sixth data packet includes the first compressed packet header;

or, the compression module is further configured to: sending the first data packet to an ROHC entity corresponding to the first packet header through a sending PDCP entity of the sending end; performing packet header compression processing on the first packet header through an ROHC entity corresponding to the first packet header to obtain a first compressed packet header; obtaining an eighth data packet containing the second packet header and the data to be processed according to the second packet header and the data to be processed in the first data packet; sending the eighth data packet to an ROHC entity corresponding to the second packet header, and performing packet header compression processing on the second packet header through the ROHC entity corresponding to the second packet header to obtain a second compressed packet header; determining a ninth data packet carrying the first compressed packet header; obtaining a tenth data packet containing the second compressed packet header and the data to be processed according to the second compressed packet header and the data to be processed in the eighth data packet; the sequence number in the PDCP subheader of the ninth data packet is the same as the sequence number in the PDCP subheader of the tenth data packet, and the PDCP subheader of the ninth data packet carries fourth indication information, where the fourth indication information is used to indicate that the ninth data packet includes the first compressed packet header.

9. A receiving end, comprising:

the decompression module is used for carrying out packet header decompression processing on the first compressed packet header and the second compressed packet header to obtain a first packet header and a second packet header, wherein the first packet header or the second packet header is an Ethernet packet header;

the receiving module is further configured to: receiving a third data packet containing the first compressed packet header, the second compressed packet header and data to be processed by a receiving PDCP entity of the receiving end; acquiring the first compressed packet header and the second compressed packet header from the third data packet according to a first PDCP subheader of the third data packet, wherein the first PDCP subheader comprises information indicating the length of the first compressed packet header and/or the second compressed packet header; the decompression module is further to: sending the first compressed packet header and the second compressed packet header to corresponding ROHC entities; respectively decompressing the first compressed packet header and the second compressed packet header through ROHC entities corresponding to the first compressed packet header and the second compressed packet header to obtain the first packet header and the second packet header; obtaining a first data packet containing the first packet header, the second packet header and the data to be processed according to the first packet header, the second packet header and the data to be processed;

or, the receiving module is further configured to: receiving, by a receiving PDCP entity of the receiving end, a fifth data packet including a first compressed packet header, a second compressed packet header, and data to be processed, where the fifth data packet includes a second PDCP subheader, and the second PDCP subheader includes related information for indicating a length of the first compressed packet header and/or the second compressed packet header; the decompression module is further to: sending the fifth data packet to an ROHC entity corresponding to the second compressed packet header for decompression to obtain a fourth data packet containing the first compressed packet header, the second packet header and data to be processed; sending the fourth data packet to an ROHC entity corresponding to the first compressed packet header for decompression to obtain a first data packet containing the first packet header, a second packet header and data to be processed;

or, the receiving module is further configured to: receiving a sixth data packet containing the first compressed packet header and a seventh data packet containing the second compressed packet header and the data to be processed by a receiving PDCP entity of the receiving end; the decompression module is further to: respectively sending the first compressed packet header in the sixth data packet and the second compressed packet header in the seventh data packet to corresponding ROHC entities for decompression processing to obtain the first packet header and the second packet header; obtaining a first data packet through the data to be processed in the first packet header, the second packet header and the seventh data packet; wherein, a sequence number in the PDCP subheader of the sixth data packet is the same as a sequence number in the PDCP subheader of the seventh data packet, and the PDCP subheader of the sixth data packet carries third indication information, where the third indication information is used to indicate that the sixth data packet includes the first compressed packet header;

or, the receiving module is further configured to: receiving a ninth data packet containing the first compressed packet header and a tenth data packet containing the second compressed packet header and data to be processed by a receiving PDCP entity of the receiving end; the decompression module is further to: sending the tenth data packet to an ROHC entity corresponding to the second compressed packet header for decompression processing, so as to obtain an eighth data packet including the second packet header and data to be processed; sending the ninth data packet to an ROHC entity corresponding to the first compressed packet header for decompression processing to obtain the first packet header; obtaining a first data packet through the first packet header and the eighth data packet; the sequence number in the PDCP subheader of the ninth data packet is the same as the sequence number in the PDCP subheader of the tenth data packet, and the PDCP subheader of the ninth data packet carries fourth indication information, where the fourth indication information is used to indicate that the ninth data packet includes the first compressed packet header.

10. A transmitting end, comprising: processor, memory and program stored on the memory and executable on the processor, which when executed by the processor implements the steps of the method of packet header compression according to any of claims 1 to 4.

11. A receiving end, comprising: processor, memory and program stored on the memory and executable on the processor, which when executed by the processor implements the steps of the method of header decompression according to any of claims 5 to 7.

12. A computer-readable storage medium, characterized in that a computer program is stored thereon, which, when being executed by a processor, carries out the steps of the method for packet header compression according to any one of claims 1 to 4; or the steps of the method of header decompression according to any of claims 5 to 7.