CN111800371A - Data processing method, sender and receiver - Google Patents

Abstract

The present invention provides a data processing method, a transmitting end and a receiving end, wherein the method corresponding to the transmitting end includes: receiving a first data packet, the first data packet including an Ethernet frame header and an IP series packet header; The Ethernet frame header in the data packet is compressed to obtain a second data packet, and the second data packet includes at least a first compressed packet header; wherein, the first compressed packet header is to perform compression processing on the Ethernet frame header The resulting compressed header. In the present invention, the transmitting end can at least compress the Ethernet frame header in the Ethernet frame data, and the receiving end can decompress the compressed Ethernet frame data. In this way, the Ethernet frame data is between the transmitting end and the receiving end. During transmission, the required transmission resources are reduced, so that the transmission resource overhead of the Ethernet frame data can be reduced.

Description

Data processing method, sender and receiver

technical field

The present invention relates to the field of communication technologies, and in particular, to a data processing method, a sending end and a receiving end.

Background technique

In an industrial environment, data transmission usually adopts the Ethernet encapsulation technology, and the data transmitted on the Ethernet link is called an Ethernet frame. An Ethernet frame includes an Ethernet header and an Ethernet payload that carries valid data. The valid data in the Ethernet frame payload can be IP type data, which includes IP series headers (such as IP (Internet Protocol, Internet Protocol) header, TCP (Transmission Control Protocol, Transmission Control Protocol) header). In some cases, the length occupied by the header in the Ethernet frame data is relatively large, which causes the problem of large resource overhead due to the large length occupied by the header during the transmission of the Ethernet frame data.

SUMMARY OF THE INVENTION

Embodiments of the present invention provide a data processing method, a sending end and a receiving end, so as to solve the problem of large resource overhead due to the large length occupied by the header during data transmission of the Ethernet frame.

In order to solve the above-mentioned technical problems, the present invention is achieved in this way:

In a first aspect, an embodiment of the present invention provides a data processing method, which is applied to a sending end, and the method includes:

Receive a first data packet, where the first data packet includes an Ethernet frame header and an IP series header;

Perform compression processing on at least the Ethernet frame header in the first data packet to obtain a second data packet, and the second data packet includes at least the first compressed packet header;

Wherein, the first compressed packet header is a compressed packet header obtained by compressing the Ethernet frame header.

In a second aspect, an embodiment of the present invention provides a data processing method, which is applied to a receiving end, and the method includes:

receiving a first data packet, the first data packet including at least a first compressed packet header;

Decompressing the compressed header in the first data packet to obtain the second data packet including the Ethernet frame header and the IP series header;

Wherein, the first compressed packet header is a compressed packet header obtained by compressing the Ethernet frame header.

In a third aspect, an embodiment of the present invention provides a transmitter, including:

a receiving module, configured to receive a first data packet, where the first data packet includes an Ethernet frame header and an IP series packet header;

a compression module, configured to compress at least the Ethernet frame header in the first data packet to obtain a second data packet, where the second data packet includes at least the first compressed packet header;

Wherein, the first compressed packet header is a compressed packet header obtained by compressing the Ethernet frame header.

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

a receiving module, configured to receive a first data packet, where the first data packet includes at least a first compressed packet header;

a decompression module, for decompressing the compressed header in the first data packet to obtain a second data packet including an Ethernet frame header and an IP series header;

Wherein, the first compressed packet header is a compressed packet header obtained by compressing the Ethernet frame header.

In a fifth aspect, an embodiment of the present invention provides another sending end, including: a memory, a processor, and a computer program stored on the memory and executable on the processor, the computer program being executed by the processor When executed, the steps in the data processing method provided in the first aspect of the embodiments of the present invention are implemented.

In a sixth aspect, an embodiment of the present invention provides another receiving end, including: a memory, a processor, and a computer program stored on the memory and executable on the processor, the computer program being executed by the processor When executed, the steps in the data processing method provided in the second aspect of the embodiments of the present invention are implemented.

In a seventh aspect, an embodiment of the present invention provides a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the data provided in the first aspect of the embodiment of the present invention is implemented steps in the processing method.

In an eighth aspect, an embodiment of the present invention provides a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the data provided in the second aspect of the embodiment of the present invention is implemented steps in the processing method.

In the embodiment of the present invention, the sending end can at least perform compression processing on the Ethernet frame header in the Ethernet frame data, and the receiving end can perform decompression processing on the compressed Ethernet frame data. When transmitting between them, the required transmission resources are reduced, so that the transmission resource overhead of the Ethernet frame data can be reduced.

Description of drawings

In order to illustrate the technical solutions of the embodiments of the present invention more clearly, the following briefly introduces the accompanying drawings that need to be used in the description of the embodiments of the present invention. Obviously, the drawings in the following description are only some embodiments of the present invention. For those of ordinary skill in the art, other drawings can also be obtained from these drawings without creative labor.

1 is a system diagram of a network system provided by an embodiment of the present invention;

2 is a flowchart of a data processing method applied to a network system provided by an embodiment of the present invention;

3 is a schematic structural diagram of Ethernet frame data provided by an embodiment of the present invention;

4 is a flowchart of a data processing method applied to a sending end provided by an embodiment of the present invention;

5 is a flowchart of a compression processing method provided by an embodiment of the present invention;

6 is a flowchart of another compression processing method provided by an embodiment of the present invention;

7 is a flowchart of a data processing method applied to a receiving end provided by an embodiment of the present invention;

8 is a flowchart of a decompression processing method provided by an embodiment of the present invention;

9 is a flowchart of another decompression processing method provided by an embodiment of the present invention;

10 is a structural diagram of a transmitter provided by an embodiment of the present invention;

11 is a structural diagram of a receiving end provided by an embodiment of the present invention;

12 is a hardware structure diagram of a terminal provided by an embodiment of the present invention;

FIG. 13 is a hardware structural diagram of a network side device provided by an embodiment of the present invention.

Detailed ways

The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, but not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of the present invention.

The term "comprising" and any variations thereof in the description and claims of this application are intended to cover non-exclusive inclusion, for example, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to the explicit Those steps or units are explicitly listed, but may include other steps or units not expressly listed or inherent to the process, method, product or apparatus. In addition, the use of "and/or" in the description and the claims indicates at least one of the connected objects, such as A and/or B, indicating that there are three cases including A alone, B alone, and both A and B.

In the embodiments of the present invention, words such as "exemplary" or "for example" are used to mean serving as an example, illustration or illustration. Any embodiments or designs described as "exemplary" or "such as" in the embodiments of the present invention should not be construed as preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "such as" is intended to present the related concepts in a specific manner.

Embodiments of the present invention will be described below with reference to the accompanying drawings. The data processing method provided by the embodiment of the present invention can be applied to a wireless communication system. The wireless communication system may be a 5G system, or an evolved long-term evolution (Evolved Long Term Evolution, eLTE) system, or a subsequent evolution communication system.

FIG. 1 is a structural diagram of a network system provided by an embodiment of the present invention, as shown in FIG. 1 , including a terminal 11 and a network side device 12 . The above-mentioned terminal may be a mobile communication device, such as a mobile phone, a tablet computer (TabletPersonal Computer), a laptop computer (Laptop Computer), a personal digital assistant (PDA for short), a mobile Internet Device (Mobile Internet Device) , MID) or wearable device (Wearable Device), etc. The above-mentioned network side equipment may be 5G network side equipment (for example: gNB, 5G NR NB), or may be 4G network side equipment (for example: eNB), or may be 3G network side equipment (for example: NB), or subsequent evolution communication Network side devices in the system, etc.

Wherein, during uplink transmission, the terminal 11 can be used as the sending end of the embodiment of the present invention, and the network-side device 12 can be used as the receiving end of the embodiment of the present invention; during downlink transmission, the network-side device 12 can be used as the sending end of the embodiment of the present invention. terminal, the terminal 11 may serve as the receiving terminal in this embodiment of the present invention.

An embodiment of the present invention provides a data processing method applied to the network system shown in FIG. 1. As shown in FIG. 2, the method includes the following steps:

Step 201: the transmitting end receives a first data packet, where the first data packet includes an Ethernet frame header and an IP series packet header;

Step 202: The sender compresses at least the Ethernet frame header in the first data packet to obtain a second data packet, and the second data packet includes at least a first compressed packet header; wherein, the first compressed packet The packet header is a compressed packet header obtained by compressing the Ethernet frame header;

Step 203: the sender sends the second data packet to the receiver;

Step 204: the receiving end receives the second data packet;

Step 205: The receiving end decompresses the compressed header in the second data packet to obtain a third data packet including the Ethernet frame header and the IP series header.

In LTE (Long Term Evolution, long term evolution) and NR (New Radio, new air interface), the PDCP (Packet Data Convergence Protocol, Packet Data Convergence Protocol) sublayer can perform header compression and decompression functions. Therefore, in this embodiment of the present invention, the transmitting end may be a transmitting PDCP entity, and the receiving end may be a receiving PDCP entity.

In this embodiment of the present invention, any data packet (for example, the above-mentioned first data packet, second data packet, etc.) involved in the data processing process of the data processing method includes an Ethernet frame header or a compressed Ethernet frame header. All can be understood as Ethernet frame data. The data field carried by the Ethernet frame data can be either IP type data or non-IP (non-IP) type data. 3 is a schematic structural diagram of the Ethernet frame data when the data field of the Ethernet frame data is IP type data.

The first data packet received by the sender includes an Ethernet frame, wherein the Ethernet frame includes an Ethernet frame header and an Ethernet frame payload (Ethernet payload). The Ethernet frame payload carries valid data (eg, Ethernet data field), and in some cases, also carries a padding field (Ethernet PAD field). The valid data in the Ethernet frame payload may be data including IP series headers. The IP series packet headers may be IP series packet headers, TCP headers, RTP (Real Time Protocol, real-time protocol) headers, and the like.

The first data packet may further include an SDAP (Service Data Adaptation Protocol, service data adaptation protocol) subheader. If the first data packet includes the SDAP subheader, the sending end may separate (or remove or skip) the SDAP subheader from the first data packet before compressing the first data packet. After compressing the first data packet, the transmitting end may add the previously separated SDAP subheader to the data packet header with the compressed packet header, and add the PDCP subheader to obtain the SDAP subheader, the PDCP subheader, and the first compressed header. The packet header and the second data packet of the second compressed packet header, the second data packet is a PDCP PDU (Protocol Data Unit, protocol data unit). After receiving the second data packet, the receiving end can also separate the SDAP subheader and the PDCP subheader from the second data packet before decompressing the second data packet, and then decompress the second data packet. Compression processing. After the decompression process, the receiving end can add the SDAP subheader to the header of the data packet that does not contain the compressed header.

It should be noted that the embodiment of the present invention provides a technical solution for compressing and decompressing Ethernet frame data, which mainly reflects how to compress and decompress the Ethernet frame header and IP series packet header in the Ethernet frame data. Therefore, the related processing of other parts in the Ethernet frame data can be implemented in combination with the existing solution, which is not described in this embodiment of the present invention.

In the embodiment of the present invention, the sending end can at least perform compression processing on the Ethernet frame header in the Ethernet frame data, and the receiving end can perform decompression processing on the compressed Ethernet frame data. When transmitting between them, the required transmission resources are reduced, so that the transmission resource overhead of the Ethernet frame data can be reduced.

FIG. 4 is a flowchart of a data processing method provided by an embodiment of the present invention. As shown in Figure 4, the data processing method, applied to the sending end, includes the following steps:

Step 401: Receive a first data packet, where the first data packet includes an Ethernet frame header and an IP series header.

As mentioned above, in this embodiment of the present invention, the sending end may be a sending PDCP entity, and the sending end may compress the data packets it receives. The above-mentioned first data packet may be understood as Ethernet frame data, and the sending PDCP entity receives the first data packet from the upper layer, and the data packet may or may not contain an SDAP subheader. If the first data packet contains the SDAP subheader, the sending end may separate the SDAP subheader from the first data packet before compressing the first data packet. Of course, the SDAP subheader may not be separated from the first data packet, but the Ethernet frame header or the IP series packet header in the first data packet may be directly compressed.

It should be noted that separating the SDAP subheader from the first data packet can also be understood as removing the SDAP subheader from the first data packet, or removing the SDAP subheader from the first data packet. "Separating A from the data packet" involved in the embodiments of the present invention can be understood as "separating A from the data packet", or "removing A from the data packet", or "removing A from the data packet" Remove A" from the middle, and the description will not be repeated in the future.

Step 402: Compress at least the Ethernet frame header in the first data packet to obtain a second data packet, where the second data packet includes at least a first compressed packet header.

Wherein, the first compressed packet header is a compressed packet header obtained by compressing the Ethernet frame header.

After step 402, the sending end may send the second data packet to the receiving end, and after receiving the second data packet, the receiving end may perform decompression processing on the second data packet to obtain a data packet not including a compressed packet header. The specific manner in which the transmitting end sends the Ethernet frame data to the receiving end will be described in detail below.

In the embodiment of the present invention, the transmitting end can at least compress the Ethernet frame header in the Ethernet frame data. In this way, when the Ethernet frame data is transmitted between the transmitting end and the receiving end, the required transmission resources are reduced, so that the Ethernet frame data can be reduced. Transmission resource overhead of frame data.

In this embodiment of the present invention, the sending end may perform compression processing on the first data packet in a variety of manners, and the various compression processing manners will be described one by one in the following.

Manner 1: The sending end compresses the Ethernet frame header and the IP series header in the first data packet respectively to obtain a second data packet including the first compressed header and the second compressed header. The first compressed packet header is a compressed packet header obtained by compressing an Ethernet frame header, and the second compressed packet header is a compressed packet header obtained by compressing an IP series packet header.

In mode 1, the sender is configured with both the Ethernet frame header compression function and the IP series packet header compression function. For example, the sender is also configured with an Ethernet frame compression entity (or Ethernet frame compression module) and ROHC (RObust HeaderCompression, robust header compression) Entity (or ROHC module), in which the sending end can compress the Ethernet frame header in the first data packet through the Ethernet frame compression entity, and the sending end can compress the IP series header in the first data packet through the ROHC entity deal with.

In the first mode, the sending end performs compression processing on the Ethernet frame header and the IP series packet header in the first data packet respectively, and may also include parallel compression processing methods and serial compression processing methods.

For the parallel compression processing method, the Ethernet frame header and the IP series packet header are respectively compressed to obtain a second data packet including the first compressed packet header and the second compressed packet header, which may include the following steps:

Performing compression processing on the Ethernet frame header by the Ethernet frame compression entity to obtain the first sub-data packet including the first compressed packet header;

The IP series packet header is compressed by the ROHC entity to obtain the second sub-data packet including the second compressed packet header;

The first sub-data packet and the second sub-data packet are combined to obtain a second data packet including the first compressed packet header and the second compressed packet header.

In this parallel compression processing method, the sender can send the Ethernet frame header and the IP series header in the first data packet to the Ethernet frame compression entity and the ROCH entity, respectively, or, through the Ethernet frame compression entity and the ROHC entity, respectively The Ethernet frame header part and the IP series packet header part are extracted from a data packet, so as to realize parallel compression processing of the Ethernet frame header and the IP series packet header. Due to the parallel compression processing, the Ethernet frame compression entity and the ROCH entity will obtain the first sub-packet and the second sub-packet including their respective compressed headers after each compression processing. After the compression process is performed, the first sub-packet and the second sub-packet need to be combined to obtain a second data packet including the first compressed packet header and the second compressed packet header. Here, combining the first sub-packet and the second sub-packet can be understood as reorganizing the data according to a specific format, for example, placing the first compressed packet header at the position of the second compressed packet header.

Optionally, before compressing the Ethernet frame header and the IP series packet header, the method further includes:

The first data packet is separated into a third sub-data packet and a fourth sub-data packet, the third sub-data packet includes an Ethernet frame header, and the fourth sub-data packet includes an IP series header;

The Ethernet frame header is compressed by the Ethernet frame compression entity to obtain the first sub-data package including the first compressed header, including:

Performing compression processing on the Ethernet frame header in the third sub-packet by the Ethernet frame compression entity to obtain the first sub-packet including the first compressed header;

The IP series packet header is compressed by the ROHC entity to obtain a second sub-packet including the second compressed packet header, including:

The IP series header in the fourth sub-packet is compressed by the ROHC entity to obtain a second sub-packet including the second compressed header.

In this optional implementation manner, the first data packet is separated into a third sub-data packet and a fourth sub-data packet, so that the Ethernet frame header and the IP series packet header in the first data packet are separated, so that the separated The Ethernet frame header part is sent to the Ethernet frame compression entity for compression processing, and the separated IP series packet header part is sent to the ROHC entity for compression processing.

Here, separating the first data packet into the third sub-data packet and the fourth sub-data packet can also be understood as dividing the first data packet to obtain the third sub-data packet and the fourth sub-data packet, or, The first data packet is segmented to obtain a third sub-packet and a fourth sub-packet.

It should be noted that the third sub-packet is not limited to including the Ethernet frame header, and the fourth sub-packet is not limited to including the IP series header. For example, the fourth sub-packet may be the Ethernet frame payload that includes the IP series header. Valid data (such as Ethernet data field) can also contain padding fields (Ethernet PAD field).

As shown in FIG. 5 , the first data packet includes an Ethernet frame header (E-Header), an IP series header (eg, IP) and a payload (payload). It should be noted that there is a difference between the payload in Figure 5 and the Ethernet frame payload. The Ethernet frame payload actually refers to the data including the IP series header, while the payload in Figure 5 is the data that does not include the IP series header.

The sending end separates the first data packet into a third sub-data packet and a fourth sub-data packet, wherein the third sub-data packet includes an Ethernet frame header, and the fourth sub-data packet includes an IP series header and a payload. The sender sends the third sub-data packet to the Ethernet frame compression entity (EHC), and compresses the Ethernet frame header through the Ethernet frame compression entity to obtain the first sub-data packet, that is, the compressed Ethernet frame header (Compressed E-header). ). Correspondingly, the sending end sends the fourth sub-data packet to the ROHC entity, and performs compression processing on the IP series header in the fourth sub-data packet through the ROHC entity to obtain a second sub-data packet, which includes: Compressed IP series header (Compressed IP-header) and payload. Then, the sending end combines the first sub-data packet and the second sub-data packet to obtain a second data packet including the compressed Ethernet frame header, the compressed IP series header and the payload. Before sending the second data packet to the receiving end, the sender may further add a PDCP subheader and an SDAP subheader (if there is an SDAP subheader) to the header of the second data packet.

It should be noted that, in the above-mentioned parallel compression processing method, the Ethernet frame compression entity compresses the Ethernet frame header, and the ROHC entity compresses the IP series packet header. The two belong to the same time sequence, but the execution time can be synchronized. Can also be out of sync.

For the serial compression processing mode, two optional serial compression processing modes may be included, which will be described in detail below.

Wherein, in the first serial compression processing mode, the Ethernet frame header and the IP series packet header are respectively compressed to obtain a second data packet including the first compressed packet header and the second compressed packet header, which may include the following steps:

Performing compression processing on the Ethernet frame header in the first data packet by the Ethernet frame compression entity to obtain a third data packet including the first compressed packet header and the IP series packet header;

The IP series packet header in the third data packet is compressed by the ROHC entity to obtain a second data packet including the first compressed packet header and the second compressed packet header.

In the first serial compression processing mode, the Ethernet frame header is first compressed, and then the IP series packet header is compressed. Specifically, first, the first data packet is sent to the Ethernet frame compression entity, and the Ethernet frame header in the first data packet is compressed to obtain a third data packet including the first compressed packet header and the IP series packet header. Then, the whole third data packet is sent to the ROHC entity, and the ROHC entity extracts the IP series header from the third data packet to perform compression processing; or, the third data packet is sent to the ROHC entity as a whole, and the ROHC entity skips The first compressed packet header of the three data packet headers is used to compress the IP series packet headers; or, the first compressed packet header is separated from the third data packet, and then the third data packet is sent to the ROHC entity to compress the IP series packet headers deal with. So far, the serial compression processing of the Ethernet frame header and the IP series packet header in sequence has been realized.

Optionally, performing compression processing on the IP series header in the third data packet by the ROHC entity to obtain a second data packet including the first compressed header and the second compressed header, including:

Separate the first compressed packet header from the third data packet to obtain the fourth data packet including the IP series packet header;

The IP series header in the fourth data packet is compressed by the ROHC entity to obtain the fifth data packet including the second compressed header;

The first compressed packet header is added to the header of the fifth data packet to obtain a second data packet including the first compressed packet header and the second compressed packet header.

In this optional implementation manner, after the first compressed packet header is separated from the third data packet, the IP series packet header can be located at the head of the third data packet, so that the ROHC entity can directly compress the IP series packet header. .

As shown in FIG. 6 , the first data packet includes an Ethernet frame header, an IP series packet header and a payload.

It should be noted that the payload in Figure 6 is different from the Ethernet frame payload. The Ethernet frame payload actually refers to the data including the IP series header; while the payload in Figure 6 is the data that does not include the IP series header.

The sender sends the first data packet to the Ethernet frame compression entity, and compresses the Ethernet frame header in the first data packet through the Ethernet frame compression entity to obtain the first data packet including the compressed Ethernet frame header and the uncompressed IP series header. Three packets. The sending end separates the compressed Ethernet frame header from the third data packet, and obtains a fourth data packet including the IP series packet header and the payload. The sending end then sends the fourth data packet to the ROHC entity, and the ROHC entity compresses the IP series packet header in the fourth data packet to obtain a fifth data packet including the compressed IP series packet header and the payload. Then, the sender adds the previously separated compressed Ethernet frame header to the header of the fifth data packet to obtain a second data packet including the compressed Ethernet frame header, the compressed IP series header and the payload. Before sending the second data packet to the receiving end, the sender may further add a PDCP subheader and an SDAP subheader (if there is an SDAP subheader) to the header of the second data packet.

Wherein, in the second type of serial compression processing, the Ethernet frame header and the IP series packet header are respectively compressed to obtain a second data packet including the first compressed packet header and the second compressed packet header, which may include the following steps:

The IP series header in the first data packet is compressed by the ROHC entity to obtain a third data packet including the Ethernet frame header and the second compressed header;

The Ethernet frame header in the third data packet is compressed by the Ethernet frame compression entity to obtain a second data packet including the first compressed packet header and the second compressed packet header.

In the second serial compression processing mode, the IP series packet header is compressed first, and then the Ethernet frame header is compressed. Specifically, first, the entire first data packet is sent to the ROHC entity, and the ROHC entity extracts the IP series header from the first data packet to perform compression processing; or, the entire first data packet is sent to the ROHC entity, and the ROHC entity skips The Ethernet frame header located in the header of the first data packet compresses the IP series packet header; or, separates the Ethernet frame header from the first data packet, and then sends the first data packet to the ROHC entity to compress the IP series packet header deal with. Then, the third data packet including the Ethernet frame header and the second compressed packet header is sent to the Ethernet frame compression entity, and the Ethernet frame header is compressed. So far, the serial compression processing of IP series packet headers and Ethernet frame headers has been realized.

Optionally, the ROHC entity compresses the IP series header in the first data packet to obtain a third data packet including the Ethernet frame header and the second compressed header, including:

Separate the Ethernet frame header from the first data packet to obtain the fourth data packet including the IP series packet header;

The IP series header in the fourth data packet is compressed by the ROHC entity to obtain the fifth data packet including the second compressed header;

The Ethernet frame header is added to the header of the fifth data packet to obtain a third data packet including the Ethernet frame header and the second compressed packet header.

In this optional implementation manner, the Ethernet frame header is separated from the first data packet, so that the IP series packet header can be located at the head of the fourth data packet, so that the ROHC entity can directly compress the IP series packet header. After the IP series packet header is compressed, the previously separated Ethernet frame header is added to the header of the data packet to obtain a third data packet including the Ethernet frame header and the second compressed packet header, and the third data packet is sent as a whole to The Ethernet frame compression entity is sufficient. Since the Ethernet frame header is located in the header of the third data packet, the Ethernet frame compression entity can directly compress the Ethernet frame header in the third data packet.

The main difference between the second serial compression processing method and the first serial compression processing method lies in the compression sequence of both the Ethernet frame header and the IP series packet header. Because it is easy to understand, this embodiment of the present invention no longer complies with the second serial compression processing method. There are too many descriptions of serial compression processing methods.

Mode 2: compressing the Ethernet frame header of the first data packet to obtain a second data packet including the first compressed packet header and the IP series packet header.

In this method, the sender is configured with the Ethernet frame header compression function, but not configured with the IP series header compression function. For example, the sender is only configured with an Ethernet frame compression entity (or an Ethernet frame compression module), and the sender can use the Ethernet frame compression The entity compresses the Ethernet frame header in the first data packet.

In addition, in the way of compressing the Ethernet frame data, the way of compressing only the IP series packet header is not excluded. In this way, the second data packet including the Ethernet frame header and the second compressed packet header can be obtained.

In this method, the sender is configured with the IP series packet header compression function, but is not configured with the Ethernet frame header compression function. For example, the sender is only configured with a ROHC entity (or ROHC module), and the sender can use the ROHC entity to compress the first data packet. The IP series packet headers in the file are compressed.

Combining the above embodiments, in this embodiment of the present invention, the sending end can be configured with the Ethernet frame header compression function and the IP series packet header compression function at the same time. For the way of configuring the Ethernet frame header compression function and the IP series packet header compression function at the same time, the Ethernet frame header compression and IP series compression can be compressed in parallel, or the Ethernet frame header compression and IP series compression can be compressed in series. In the embodiment of the present invention, regardless of the above-mentioned compression processing method, the transmission resource overhead of the Ethernet frame data can be reduced.

In the embodiment of the present invention, after the Ethernet frame data is compressed, the receiving end needs to decompress the compressed Ethernet frame data. In order to enable the receiving end to better decompress the compressed Ethernet frame data, the transmitting end can Add some indication information to the ether frame data.

In this embodiment of the present invention, the sending end may add first indication information in the first compressed packet header, where the first indication information is used to indicate an Ethernet frame domain combination mode or a preset bit stream corresponding to the first data stream, the preset The bit stream is used to correlate the Ethernet frame domain combination corresponding to the first data stream, where the first data stream is a series of data packet sets with the same compression characteristic.

Here, the same compression characteristic may refer to the same Ethernet frame format and the same Ethernet frame field to be compressed, and each of the Ethernet frame fields to be compressed has the same value. For example, these data packets all need to compress the Ethernet frame source MAC (Medium Access Control, media access control) address (Ethernet sourcemac address field) and the Ethernet frame destination MAC address (Ethernet destination mac address field), and the values of these fields that need to be compressed Are the same. Further, the above-mentioned "Ether frame combination mode" can be understood as the Ethernet frame fields that need to be compressed and the specific values of each Ethernet frame field that needs to be compressed. The above-mentioned "preset bit stream" can be understood as a bit stream in which the specific values of each Ethernet frame field to be compressed are concatenated in series.

Specifically, first indication information identifying a compressed file of a certain data stream is added to the first compressed packet header, and the compressed file identified by the first indication information is associated with a specific set of Ethernet frame domain combinations or a specific set of bit streams. For example, the first indication information indicates that the MAC source field in the data packet (assuming the value is "000000", here it can be understood that the bit stream associated with the source Mac address field of the Ethernet frame is "000000"), the MAC destination field (assuming the value is "000000") The value is "000001", here it can be understood that the bit stream associated with the Mac destination address field of the Ethernet frame is "000001") and the Q-tag field (assuming the value of this field is "000010", it can be understood here as the Ethernet frame The bit stream associated with the Q-tag field in the "000010") is compressed. In this example, the "preset bit stream" can be understood as a bit stream in which the specific values of each Ethernet frame field to be compressed are concatenated, that is, "000000000001000010". It should be noted that the value of the Ethernet frame field in the above example is only for the convenience of understanding, and does not represent the actual size of bytes occupied by the corresponding Ethernet frame frame field.

Further, the first indication information is further used to indicate the Ethernet frame header format corresponding to the first data stream.

In this way, the receiving end may determine, according to the first indication information, the Ethernet frame domain combination mode or the Ethernet frame header format of the first data packet before compression, so as to facilitate the receiving end to better decompress the Ethernet frame data.

In this embodiment of the present invention, the sending end may further add second indication information to the second data packet, where the second indication information is used to indicate the length of the first compressed packet header. The second indication information may be added at any suitable position in the second data packet, and specifically, the second indication information may be added in the PDCP subheader.

In this way, the receiving end can determine the length of the first compressed packet header according to the second indication information, so that the first compressed packet header can be intercepted (or extracted or identified) from the second data packet more accurately and quickly.

In this embodiment of the present invention, if the first data packet carries a length field or a padding field (PADfield), the sender may also remove the length field and padding carried in the first data packet through the Ethernet frame compression entity. At least one of the fields. Whether the length field and the padding field are removed may be agreed by the protocol or configured by the network side device. For example, the protocol stipulates that the length field and padding field in the Ethernet frame are removed, so the sender will always process the data packet containing the length field and/or the padding field. In addition, the removal processing of the two fields can be performed simultaneously with the compression of other Ethernet frame fields, or it can be performed at different times. When the data packet of the data stream is subjected to the Ethernet frame compression processing, the length field and/or the padding field contained in the Ethernet frame is removed. In some cases, several packets without Ethernet frame compression may be sent before a data stream is actually compressed. For such packets, length fields and/or padding may or may not be performed. Field removal processing, if the removal processing is performed, additional information indicating whether the length field and/or the padding field has been removed may be carried. In addition, when processing the first data packet, the timing of removing the length field or the padding field may be before the first data packet is compressed, that is, the sender removes the length field or the padding field before removing the length field or the padding field. The first data packet is compressed.

By removing the length field or the padding field, the transmission resource overhead of the Ethernet frame data can be further reduced.

In this embodiment of the present invention, the sender may also add at least one of the following indication information to the second data packet:

adding third indication information to the second data packet, where the third indication information is used to indicate whether the length field carried in the first data packet is removed;

adding fourth indication information to the second data packet, where the fourth indication information is used to indicate whether the padding field carried in the first data packet is removed;

Fifth indication information is added to the second data packet, where the fifth indication information is used to indicate whether the length field and the padding field carried in the first data packet are removed.

In this way, the receiving end can determine whether the length field or the padding field is removed according to any of the above-mentioned indication information, so that during the decompression process, it can more accurately and quickly determine whether the removed length field or the padding field needs to be added.

The above data processing method applied to the transmitting end belongs to the compression processing method of the Ethernet frame data, and the decompression processing method of the Ethernet frame data will be specifically described below.

FIG. 7 is a flowchart of another data processing method provided by an embodiment of the present invention. As shown in Figure 7, the data processing method is applied to the receiving end, and the method includes the following steps:

Step 501: Receive a first data packet, where the first data packet includes at least a first compressed packet header.

The first compressed packet header is a compressed packet header obtained by compressing the Ethernet frame header.

As described above, in this embodiment of the present invention, the receiving end may be a receiving PDCP entity, and the receiving end may decompress the received data packet with a compressed packet header. The above-mentioned first data packet can be understood as Ethernet frame data with a compressed packet header, and the first data packet can be regarded as the second data packet compressed by the sender in the aforementioned compression processing method.

In this step, the receiving PDCP entity receives the above-mentioned first data packet from the lower layer, and the data packet includes the PDCP subheader and the SDAP subheader (if there is an SDAP subheader) in addition to the first compressed packet header or the second compressed packet header. If the first data packet includes the PDCP subheader and the SDAP subheader, the receiving end may separate the PDCP subheader and the SDAP subheader from the first data packet before decompressing the first data packet. Of course, the PDCP subheader and the SDAP subheader may not be separated from the first data packet, and the Ethernet frame header or the IP series packet header in the first data packet may be directly compressed.

It should be noted that separating the PDCP subheader and the SDAP subheader from the first data packet can also be understood as removing the PDCP subheader and the SDAP subheader from the first data packet, or removing the PDCP subheader and the SDAP subheader from the first data packet Remove the PDCP subheader and SDAP subheader. "Separating A from the data packet" involved in the embodiments of the present invention can be understood as "separating A from the data packet", or "removing A from the data packet", or "removing A from the data packet" Remove A" from the middle, and the description will not be repeated in the future.

Step 502: Perform decompression processing on the compressed header in the first data packet to obtain a second data packet including an Ethernet frame header and an IP series header.

In the embodiment of the present invention, the sending end can perform compression processing on at least one of the Ethernet frame header and the IP series packet header in the Ethernet frame data, and the receiving end can perform decompression processing on the compressed Ethernet frame data. When the frame data is transmitted between the sending end and the receiving end, the required transmission resources are reduced, so that the transmission resource overhead of the Ethernet frame data can be reduced.

In the embodiment of the present invention, the first data packet may further include a second compressed packet header, and the second compressed packet header is a compressed packet header obtained by compressing the IP series packet headers. In the case where the first data packet includes the first compressed header and the second compressed header, the receiving end can be configured with both the Ethernet frame header decompression function and the IP series header decompression function. For example, the receiving end is also configured with the Ethernet frame decompression function entity (or called Ethernet frame decompression module) and ROHC decompression entity (or called ROHC decompression module), wherein the receiving end can decompress the Ethernet frame header in the first data packet through the Ethernet frame decompression entity, The receiving end may perform decompression processing on the IP series header in the first data packet through the ROHC decompression entity.

There are many ways for the receiving end to perform decompression processing on the first compressed packet header and the second compressed packet header in the first data packet, and the various decompression processing methods will be described one by one in the following.

Manner 1: Decompress the first compressed packet header and the second compressed packet header in the first data packet to obtain a second data packet including the Ethernet frame header and the IP series packet header, including:

The first compressed packet header is decompressed by the Ethernet frame decompression entity to obtain the first sub-packet including the Ethernet frame header;

The second compressed packet header is decompressed by the ROHC decompression entity to obtain the second sub-data packet including the IP series packet header;

The first sub-data packet and the second sub-data packet are combined to obtain the second data packet including the Ethernet frame header and the IP series packet header.

This method is a parallel decompression processing method. The receiving end can send the first compressed packet header and the second compressed packet header in the first data packet to the Ethernet frame decompression entity and the ROCH decompression entity respectively, or, through the Ethernet frame decompression entity and ROCH decompression entity. The frame decompression entity and the ROHC decompression entity respectively extract the first compressed packet header and the second compressed packet header from the first data packet, so as to realize parallel decompression processing of the first compressed packet header and the second compressed packet header. Due to the parallel decompression process, the Ethernet frame decompression entity and the ROCH decompression entity will obtain the first sub-data packet and the second sub-data packet after decompression respectively after the decompression process of the Ethernet frame decompression entity and the ROCH decompression entity. After the compression entity and the ROCH decompression entity perform decompression processing respectively, the first sub-data packet and the second sub-data packet need to be combined to obtain the second data packet including the Ethernet frame header and the IP series header. Here, combining the first sub-packet and the second sub-packet can be understood as data reorganization.

Optionally, before decompressing the first compressed packet header and the second compressed packet header, the method further includes:

Separating the first data packet into a third sub-data packet and a fourth sub-data packet, the third sub-data packet includes the first compressed packet header, and the fourth sub-data packet includes the second compressed packet header ;

The first compressed packet header is decompressed by the Ethernet frame decompression entity to obtain the first sub-packet including the Ethernet frame header, including:

Perform decompression processing on the first compressed header in the third sub-packet by the Ethernet frame decompression entity to obtain the first sub-packet including the Ethernet frame header;

The second compressed packet header is decompressed by the ROHC decompression entity to obtain a second sub-data packet including the IP series packet header, including:

The second compressed header in the fourth sub-packet is decompressed by the ROHC decompression entity to obtain the second sub-packet including the IP series header.

In this optional implementation manner, the first data packet is separated into a third sub-data packet and a fourth sub-data packet, so that the first compressed packet header and the second compressed packet header in the first data packet are separated, so that the separation The obtained first compressed packet header is sent to the Ethernet frame decompression entity for decompression processing, and the separated second compressed packet header is sent to the ROHC decompression entity for decompression processing.

Here, separating the first data packet into the third sub-data packet and the fourth sub-data packet can also be understood as dividing the first data packet to obtain the third sub-data packet and the fourth sub-data packet, or, The first data packet is segmented to obtain a third sub-packet and a fourth sub-packet.

It should be noted that the third sub-packet is not limited to including the first compressed header, and the fourth sub-packet is not limited to including the second compressed header. For example, the fourth sub-packet may also include the payload portion of the Ethernet frame data.

As shown in FIG. 8 , the first data packet includes a compressed Ethernet frame header, a compressed IP series packet header (eg, a compressed IP series packet header) and a payload.

It should be noted that there is a difference between the payload in Figure 8 and the Ethernet frame payload. The Ethernet frame payload actually refers to the data including the IP series header, while the payload in Figure 8 is the data that does not include the IP series header.

The receiving end separates the first data packet into a third sub-data packet and a fourth sub-data packet, wherein the third sub-data packet includes a compressed Ethernet frame header, and the fourth sub-data packet includes a compressed IP series packet header and a payload. The receiving end sends the third sub-data packet to the Ethernet frame decompression entity, and decompresses the compressed Ethernet frame header through the Ethernet frame decompression entity to obtain the first sub-data packet, that is, the uncompressed Ethernet frame header. Correspondingly, the receiving end sends the fourth sub-packet to the ROHC decompression entity, and decompresses the IP series header compressed in the fourth sub-packet by the ROHC decompression entity to obtain the second sub-packet, the first sub-packet. The second sub-packet includes uncompressed IP and payload. Then, the receiving end combines the first sub-data packet and the second sub-data packet to obtain a second data packet including the Ethernet frame header, the IP series packet header and the payload.

It should be noted that, in the above-mentioned parallel decompression processing method, the Ethernet frame decompression entity decompresses the first compressed packet header, and the ROHC decompression entity decompresses the second compressed packet header, and the two belong to the same time sequence. , but the execution time may or may not be synchronized.

It should also be noted that if the sending end adopts the parallel compression processing method, the receiving end can also adopt the parallel decompressing processing method; if the sending end adopts the serial compression processing method, the receiving end can also adopt the parallel decompression processing method. how to handle it. That is to say, the compression processing method adopted by the sender does not limit the decompression processing method adopted by the receiver.

Mode 2: Decompress the first compressed packet header and the second compressed packet header in the first data packet to obtain a second data packet including the Ethernet frame header and the IP series packet header, including:

Perform decompression processing on the second compressed packet header in the first data packet by the ROHC decompression entity to obtain a third data packet including the first compressed packet header and the IP series packet header;

The first compressed packet header in the third data packet is decompressed by the Ethernet frame decompression entity to obtain a second data packet including the Ethernet frame header and the IP series packet header.

This method is a serial decompression processing method. First, the second compressed packet header is decompressed, and then the first compressed packet header is decompressed. Specifically, first, the entire first data packet is sent to the ROHC decompression entity, and the ROHC decompression entity extracts the second compressed header from the first data packet for decompression processing; or, the entire first data packet is sent to the ROHC decompression entity. Among the compression entities, the ROHC decompression entity skips the first compressed header located in the header of the first data packet, and decompresses the second compressed header; or separates the first compressed header from the first data packet, and then decompresses the first compressed header. A data packet is sent to the ROHC decompression entity to decompress the second compressed packet header. Then, the third data packet including the first compressed packet header and the IP series packet header is sent to the Ethernet frame decompression entity, and the first compression entity is decompressed. So far, the sequential serial decompression process of the first compressed packet header and the second compressed packet header has been realized.

Optionally, perform decompression processing on the second compressed packet header in the first data packet by the ROHC decompression entity to obtain a third data packet including the first compressed packet header and the IP series packet header, including:

Separating the first compressed packet header from the first data packet to obtain a fourth data packet including the second compressed packet header;

The second compressed header in the fourth data packet is decompressed by the ROHC decompression entity to obtain the fifth data packet including the IP series header;

The first compressed packet header is added to the header of the fifth data packet to obtain a third data packet including the first compressed packet header and the IP series packet header.

In this optional implementation manner, the first compressed packet header is separated from the first data packet, so that the second compressed packet header can be located at the head of the fourth data packet, so that the ROHC decompression entity can directly decompress the second compressed packet header Perform decompression processing. After the second compressed packet header is decompressed, the previously separated first compressed packet header is added to the header of the data packet to obtain a third data packet including the first compressed packet header and the IP series packet header, and the third data packet is The whole can be sent to the Ethernet frame decompression entity. Since the first compressed packet header is located in the third data packet header, the Ethernet frame decompression entity can directly perform decompression processing on the first compressed packet header in the third data packet.

As shown in FIG. 9 , the first data packet includes a first compressed packet header, a second compressed packet header and a payload.

It should be noted that there is a difference between the payload in Figure 9 and the Ethernet frame payload. The Ethernet frame payload actually refers to data that includes IP series headers; while the payload in Figure 9 is data that does not include IP series headers.

The receiving end separates the first compressed packet header from the first data packet to obtain a fourth data packet including the second compressed packet header and the payload, and the receiving end sends the fourth data packet to the ROHC decompression entity, and uses the ROHC decompression entity The second compressed header in the fourth data packet is decompressed to obtain a fifth data packet including the uncompressed IP series header and the payload. Then, the receiving end adds the first compressed packet header separated before the header of the fifth data packet to obtain a third data packet including the first compressed packet header, the uncompressed IP series packet header and the payload. The receiving end sends the third data packet to the Ethernet frame decompression entity, and decompresses the first compressed packet header in the third data packet through the Ethernet frame decompression entity, and obtains a packet including the Ethernet frame header, the IP series packet header and the payload. second data packet.

Mode 3: Decompress the first compressed packet header and the second compressed packet header in the first data packet to obtain a second data packet including the Ethernet frame header and the IP series packet header, including:

Perform decompression processing on the first compressed packet header in the first data packet by the Ethernet frame decompression entity to obtain a third data packet including the Ethernet frame header and the second compressed packet header;

The ROHC decompression entity performs decompression processing on the second compressed packet header in the third data packet to obtain a second data packet including the Ethernet frame header and the IP series packet header.

This method is another serial decompression processing method. First, the first compressed packet header is decompressed, and then the second compressed packet header is decompressed. Specifically, first, the first data packet is sent to the Ethernet frame decompression entity, and the first compressed packet header in the first data packet is decompressed to obtain a third data packet including the Ethernet frame header and the second compressed packet header . Then, the whole third data packet is sent to the ROHC decompression entity, and the ROHC decompression entity extracts the second compressed header from the third data packet for decompression processing; or, the whole third data packet is sent to the ROHC decompression entity , the ROHC decompression entity skips the Ethernet frame header located in the header of the third data packet, and decompresses the second compressed packet header; or separates the Ethernet frame header from the third data packet, and then sends the third data packet to the The second compressed packet header is decompressed in the ROHC decompression entity. So far, the sequential serial decompression process of the first compressed packet header and the second compressed packet header has been realized.

Optionally, perform decompression processing on the second compressed packet header in the third data packet by a ROHC decompression entity, to obtain a second data packet including the Ethernet frame header and the IP series packet header, including:

Separate the Ethernet frame header from the third data packet to obtain a fourth data packet including the second compressed packet header;

The second compressed header in the fourth data packet is decompressed by the ROHC decompression entity to obtain the fifth data packet including the IP series header;

The Ethernet frame header is added to the header of the fifth data packet to obtain a second data packet including the Ethernet frame header and the IP series packet header.

In this optional implementation manner, after the Ethernet frame header is separated from the third data packet, the second compressed packet header can be located at the head of the third data packet, so that the ROHC decompression entity can directly decompress the second compressed packet header Perform decompression processing.

The main difference between the above two serial decompression processing methods is the decompression sequence of the first compressed packet header and the second compressed packet header. Because it is easy to understand, the embodiment of the present invention no longer performs the second serial decompression processing. way to describe too much.

It should be noted that if the sending end adopts the parallel compression processing method, the receiving end can adopt the serial decompressing processing method; if the sending end adopts the serial compression processing method, the receiving end can also adopt the serial decompressing processing method. how to handle it. In addition, the receiving end can adopt any one of two serial decompression processing methods. That is to say, the compression processing method adopted by the sender does not limit the decompression processing method adopted by the receiver.

Optionally, the first data packet includes a first compressed header;

Before decompressing the first compressed packet header, the method further includes:

determining the length of the first compressed packet header;

The first compressed packet header in the first data packet is determined according to the length of the first compressed packet header.

Optionally, the length of the first compressed packet header is determined by at least one of the following:

the first indication information carried in the first data packet, where the first indication information is used to indicate the length of the first compressed packet header;

The length of the first compressed packet header corresponding to the format of the Ethernet frame header of the first data packet based on the protocol agreement.

Optionally, the first compressed packet header carries second indication information, where the second indication information is used to indicate an Ethernet frame domain combination mode or a preset bit stream corresponding to the first data stream, and the preset bit stream uses Corresponding to the Ethernet frame domain combination corresponding to the first data stream, the first data stream is a series of data packet sets with the same compression characteristics.

Here, the same compression characteristic may refer to the same Ethernet frame format and the same Ethernet frame field to be compressed, and each of the Ethernet frame fields to be compressed has the same value. For example, these data packets all need to compress the Ethernet frame source MAC (Medium Access Control, media access control) address (Ethernet sourcemac address field) and the Ethernet frame destination MAC address (Ethernet destination mac address field), and the values of these fields that need to be compressed Are the same. Further, the above-mentioned "Ether frame combination mode" can be understood as the Ethernet frame fields that need to be compressed and the specific values of each Ethernet frame field that needs to be compressed. The above-mentioned "preset bit stream" can be understood as a bit stream in which the specific values of each Ethernet frame field to be compressed are concatenated in series.

Specifically, the compressed file identified by the second indication information is associated with a specific Ethernet frame domain combination or a specific bit stream. For example, the second indication information indicates that the MAC source field in the data packet (assuming the value is "000000", here it can be understood that the bit stream associated with the source Mac address field of the Ethernet frame is "000000"), the MAC destination field (assuming the value is "000000") The value is "000001", here it can be understood that the bit stream associated with the Mac destination address field of the Ethernet frame is "000001") and the Q-tag field (assuming the value of this field is "000010", it can be understood here as the Ethernet frame The bitstream associated with the Q-tag field in '000010') is compressed. In this example, the "preset bit stream" can be understood as a bit stream in which the specific values of each Ethernet frame field to be compressed are concatenated, that is, "000000000001000010". It should be noted that the value of the Ethernet frame field in the above example is only for the convenience of understanding, and does not represent the actual size of bytes occupied by the corresponding Ethernet frame frame field.

Further, the second indication information is further used to indicate the Ethernet frame header format corresponding to the first data stream.

Optionally, after decompressing the compressed header in the first data packet, the method further includes:

According to the second indication information, determine whether a length field needs to be added to the second data packet;

If so, add the length field at a specific position of the second data packet through the Ethernet frame decompression entity;

Wherein, the specific position is determined based on the second indication information, and the specific position is determined according to the Ethernet frame format of the high data packet.

Optionally, after decompressing the compressed header in the first data packet, the method further includes:

determining, according to the third indication information carried in the first data packet, whether a length field needs to be added to the second data packet;

If so, add the length field at a specific position of the second data packet through the Ethernet frame decompression entity;

Wherein, the third indication information is used to indicate whether the length field is removed before the first data packet is compressed.

Optionally, after decompressing the compressed header in the first data packet, the method further includes:

According to the minimum Ethernet frame size agreed in the protocol, or, according to the fourth indication information carried in the first data packet, determine whether a padding field needs to be added to the second data packet;

If so, add a padding field at the end of the second data packet through the Ethernet frame decompression entity;

Wherein, the fourth indication information is used to indicate whether the padding field is removed before the first data packet is compressed.

It should be noted that, since the length field in the Ethernet frame indicates the length of the valid data in the Ethernet frame payload (that is, the Ethernet data field, that is, the data including the IP series header), the Ethernet frame decompression entity needs to decompress the IP series header. Then determine the specific value indicated by the length field, which may involve the interaction between the Ethernet frame decompression entity and the ROHC decompression entity. For example, the ROCH decompression entity indicates the length of the decompressed data including the IP series header (that is, the Ethernetdata field) to The ether frame decompression entity, but does not necessarily require the interaction of two decompression entities, may depend on the implementation. In addition, for the padding field, since the Ethernet frame data packet has a minimum byte limit (such as 64 bytes), how many bytes the padding field needs to occupy needs to be determined after decompression and after the length field is added (if necessary).

In order to understand the technical solutions of the embodiments of the present invention more clearly, the following describes the entire process from the sending end compressing the Ethernet frame data to the receiving end decompressing the Ethernet frame data.

Example 1: The sending PDCP entity performs parallel compression processing on the Ethernet frame header and the IP series header in the data packet, and the receiving PDCP entity performs parallel decompression processing on the first compressed header and the second compressed header in the data packet.

Step S1: The sending PDCP entity receives the data packet containing the packet header from the upper layer, removes the SDAP subheader (if there is an SDAP subheader) contained in the data packet, and the compression processing behavior of the data packet with the SDAP subheader removed includes: :

The Ethernet frame header in the data packet from which the SDAP subheader has been removed is compressed by the Ethernet frame compression entity to obtain a compressed Ethernet frame header; the compressed Ethernet frame header that identifies a certain data stream is added to the compressed Ethernet frame header. The indication information of the file, the compressed file identified by the indication information is associated with a specific set of Ethernet frame domain combinations or a specific set of bit streams (for example, a specific Ethernet frame domain combination is MAC source=000000, MAC destination=000001 and Q-tag =000010, or the specific bit stream is 000000000001000010), further, the indication information may also indicate the corresponding Ethernet frame format or the Ethernet frame header format of the data stream;

The payload part in the data packet with the SDAP subheader removed is subjected to compression processing by the ROHC entity to obtain the data packet with the second compressed packet header;

A compressed Ethernet frame header is added to the obtained data packet header with the second compressed header to obtain a data packet with the first compressed header and the second compressed header.

In addition, if the protocol agreement or network configuration removes the length field and/or padding field carried in the data packet, the Ethernet frame entity compresses the data packet with the SDAP subheader removed before performing the compression process. Behavior also includes:

The length field and/or the padding field carried in the data packet from which the SDAP subheader has been removed is removed.

Step S2: Add the SDAP subheader removed before to the data packet header having the first compressed packet header and the second compressed packet header, and add the PDCP subheader to obtain a PDCP PDU and submit it to the lower layer for transmission.

In addition, the following information can also be carried in the PDCP PDU (for example, carried in the PDCP subheader):

length indication information of the Ethernet frame header, the indication information is used to indicate the length of the compressed Ethernet frame header;

Step S3: The receiving PDCP entity receives the data packet containing the compressed packet header from the lower layer, removes the PDCP subheader and the SDAP subheader (if there is an SDAP subheader) in the data packet, and removes the PDCP subheader and SDAP subheader. The decompression processing behavior of the header packet includes:

Determine the length of the compressed Ethernet frame header, and perform decompression processing on the determined compressed Ethernet frame header through the Ethernet frame decompression entity to obtain an uncompressed Ethernet frame header;

The payload part of the Ethernet frame is decompressed by the ROCH decompression entity to obtain the uncompressed payload part of the Ethernet frame;

Add the uncompressed Ethernet frame payload part at the end of the uncompressed Ethernet frame header to obtain a data packet that does not contain the compressed header.

Wherein, determining the length of the compressed Ethernet frame header may include the following methods:

Based on the length indication information of the Ethernet frame header carried in the received PDCP PDU;

Length information of an Ethernet frame compressed based on a certain Ethernet frame format agreed upon in the protocol.

In addition, if the protocol agreement or network configuration removes the length field and/or padding field carried in the data packet, the processing behavior of the Ethernet frame decompression entity to the data packet that does not contain the compressed packet header also includes:

The Ethernet frame decompression entity determines whether the decompressed data packet should have a length field based on the compressed file identification information of the data stream carried in the compressed packet header. Length field, where the length field indicates the length value of the decompressed data packet indicated by the ROHC decompression entity to the Ethernet frame decompression entity;

Determine whether the padding field should be carried according to the minimum Ethernet frame size agreed in the protocol. If so, add a padding field at the end of the decompressed data packet. The length of the padding field is the minimum data field length agreed in the protocol minus the actual Ethernet The length of the frame payload.

Step S4: Add the SDAP subheader (if there is an SDAP subheader) removed before to the header of the data packet that does not contain the compressed header, and submit it to the upper layer.

Example 2: The sending PDCP entity performs serial compression processing on the Ethernet frame header and the IP series header in the data packet, and the receiving PDCP entity performs serial decompression processing on the first compressed header and the second compressed header in the data packet.

Step S1: the sending PDCP entity receives the data packet including the packet header from the upper layer, removes the SDAP subheader (if there is an SDAP subheader) contained in the data packet, and compresses the data packet from which the SDAP subheader is removed.

Step S1.1: compressing the Ethernet frame header in the data packet with the SDAP subheader removed by the Ethernet frame compression entity to obtain a data packet containing the compressed Ethernet frame header; Indication information of a compressed file of a data stream, the compressed file identified by the indication information is associated with a specific set of Ethernet frame field combinations or a specific set of bit streams (for example, a specific Ethernet frame field combination is MAC source=000000, MAC destination= 000001 and Q-tag=000010, or the specific bit stream is 000000000001000010), additionally, the indication information may also indicate the Ethernet frame format or the Ethernet frame header format corresponding to the data stream.

In addition, if the protocol agreement or network configuration removes the length field and/or padding field carried in the data packet, the compression processing behavior of the Ethernet frame compression entity for the data packet from which the SDAP subheader has been removed also includes:

The length field and/or the padding field carried in the data packet from which the SDAP subheader has been removed is removed.

Step S1.2: remove the compressed Ethernet frame header from the data packet obtained in step S1.1, perform compression processing on the data packet that does not contain the compressed Ethernet frame header by the ROHC compression entity, and obtain data including the second compressed packet header Packet; adding a compressed Ethernet frame header to the header of the data packet including the second compressed header to obtain a data packet with the first compressed header and the second compressed header.

Step S2: Add the SDAP subheader removed before to the data packet header having the first compressed packet header and the second compressed packet header, and add the PDCP subheader to obtain a PDCP PDU and submit it to the lower layer for transmission.

In addition, the following information can also be carried in the PDCP PDU (for example, carried in the PDCP subheader):

Length indication information of the Ethernet frame header, the indication information is used to indicate the length of the compressed Ethernet frame header.

Step S3: the receiving PDCP entity receives the data packet containing the first compressed packet header and the second compressed packet header from the lower layer, removes the PDCP subheader and the SDAP subheader (if there is an SDAP subheader) in the data packet, and removes the data packet. The data packets containing the PDCP subheader and the SDAP subheader are decompressed.

Step S3.1: Determine the length of the compressed Ethernet frame header and remove the compressed Ethernet frame header, and perform decompression processing on the data packet with the compressed Ethernet frame header removed by the ROHC decompression entity, and obtain an uncompressed Ethernet frame header. The data packet of the IP series header; the compressed Ethernet frame header removed before the header of the packet containing the uncompressed IP series header is added to obtain a packet containing only the compressed Ethernet frame header, and the Ethernet frame is delivered Unpack the entity.

Step S3.2: The Ethernet frame decompression entity performs decompression processing on the Ethernet frame header in the data packet received from the ROHC entity based on its associated compressed file, restores the compressed Ethernet frame field, and obtains an Ethernet frame that does not contain the compressed packet header. data pack.

Wherein, determining the length of the compressed Ethernet frame header may include the following methods:

Based on the length indication information of the Ethernet frame header carried in the received PDCP PDU;

Length information of an Ethernet frame after being compressed by a certain Ethernet frame format agreed upon by the protocol. For example, the packet header format of the Ethernet frame can be known according to the compressed file indication information that identifies a certain data stream carried in the compressed Ethernet frame header, and then according to the protocol agreement Determine the number of bytes occupied by the compressed Ethernet frame header of this type of format, that is, the length of the compressed Ethernet frame header.

In addition, if the protocol agreement or network configuration removes the length field and/or padding field carried in the data packet, the processing behavior of the Ethernet frame decompression entity on the data packet received from the ROCH entity also includes:

Determine whether the Ethernet frame header should have a length field based on the indication information carried in the first compressed packet header that identifies the compressed file of a certain data stream, and if so, add a length field at a specific position according to the Ethernet frame format associated with the compressed file of the data stream , where the length field indicates the length of the data field in the Ethernet frame;

Determine whether there is a padding field according to the minimum Ethernet frame agreed in the protocol. If there is, add a padding field at the end of the decompressed data packet. The length of the padding field is the minimum data field length agreed in the protocol minus the actual data field. length.

Step S4: Add the SDAP subheader (if there is an SDAP subheader) removed before to the header of the data packet that does not contain the compressed header, and submit it to the upper layer.

Example 3: The sending PDCP entity compresses the Ethernet frame header in the data packet, and the IP series header compression function is not configured; the receiving PDCP entity decompresses the first compressed header in the data packet.

Step S1: The sending PDCP entity receives the data packet including the packet header from the upper layer, removes the SDAP subheader (if there is an SDAP subheader) contained in the data packet, and compresses the data packet with the SDAP subheader removed by the Ethernet frame header compression entity. The Ethernet frame subheader in the data packet is processed to obtain a data packet with a first compressed packet header; the first compressed packet header carries indication information identifying the compressed file of the data stream, and the compressed file identified by the indication information is associated with a group of specific. Ethernet frame field combination or a specific set of bitstreams (such as a specific Ethernet frame field combination of MAC source=000000, MAC destination=000001 and Q-tag=000010, or a specific bitstream of 000000000001000010), additionally, the indication The information may also indicate the Ethernet frame format of the data stream.

In addition, if the protocol agreement or network configuration removes the length field and/or padding field carried in the data packet, the compression processing behavior of the Ethernet frame compression entity for the data packet from which the SDAP subheader has been removed also includes:

The length field and/or the padding field carried in the data packet from which the SDAP subheader has been removed is removed.

Step S2: Add the SDAP subheader removed before to the data packet header with the first compressed packet header, and add the PDCP subheader to obtain the PDCP PDU and submit it to the lower layer.

In addition, the PDCP PDU may also carry (for example, carried in the PDCP subheader) length indication information of the Ethernet frame header, where the indication information is used to indicate the length of the compressed Ethernet frame header.

Step S3: the receiving PDCP entity receives the data packet including the first compressed packet header from the lower layer, and removes the PDCP subheader and the SDAP subheader (if there is an SDAP subheader) in the data packet, and the Ethernet frame decompression entity is based on the packet. The associated compressed file decompresses the Ethernet frame header in the data packet from which the PDCP subheader and the SDAP subheader are removed, restores the compressed Ethernet frame field, and obtains a data packet that does not contain the compressed header.

In addition, if the protocol agreement or network configuration removes the length field and/or padding field carried in the data packet, the Ethernet frame decompression entity will process the data packet with the PDCP subheader and SDAP subheader removed. Also includes:

Based on the indication information that identifies the compressed file of a data stream carried in the compressed packet header, determine whether the Ethernet frame header should have a length field, and if so, add a length field at a specific position according to the Ethernet frame format associated with the compressed file of the data stream. Wherein, the length field indicates the length of the data field in the Ethernet frame;

Determine whether there is a padding field according to the minimum Ethernet frame agreed in the protocol. If there is, add a padding field at the end of the decompressed data packet. The length of the padding field is the minimum data field length agreed in the protocol minus the actual data field. length.

Step S4: Add the previously removed SDAP subheader (if there is an SDAP subheader) to the decompressed data packet header, and submit it to the upper layer.

Example 4: The sending PDCP entity compresses the IP series header in the data packet, and the Ethernet frame header compression function is not configured; the receiving PDCP entity decompresses the second compressed header in the data packet.

Step S1: The sending PDCP entity receives the data packet containing the packet header from the upper layer, removes the SDAP subheader (if there is an SDAP subheader) and the Ethernet frame subheader in the data packet, and removes the SDAP subheader through the ROHC entity pair. And/or the data packet of the Ethernet frame subheader is compressed to obtain the data packet with the second compressed packet header.

Step S2: Add the SDAP subheader (if there is an SDAP subheader) and the Ethernet frame subheader removed before the header of the data packet with the second compressed header, and add the PDCP subheader to obtain the PDCP PDU and submit it to the lower layer.

Step S3: the receiving PDCP entity receives the data packet containing the second compressed packet header from the lower layer, removes the PDCP subheader, the SDAP subheader (if there is an SDAP subheader) and the Ethernet frame subheader in the data packet, and decomposes the data packet by ROHC. The compression entity decompresses the data packet from which the PDCP subheader, the SDAP subheader and the Ethernet frame subheader are removed to obtain a decompressed data packet.

Step S4: Add the SDAP subheader and the Ethernet frame subheader that were removed before to the decompressed data packet header, and submit it to the upper layer.

From the above, it can be seen that, by using any of the above data processing methods provided in the embodiments of the present invention, the compression processing of the Ethernet frame data can be implemented, and the transmission resource overhead of the Ethernet frame data can be reduced. In addition, it also provides the processing behavior of the sender and the receiver for compressed packets and compression feedback, which can improve the compression efficiency and decompression efficiency.

FIG. 10 is a structural diagram of a transmitter according to an embodiment of the present invention. As shown in FIG. 10 , the transmitter 600 includes:

A receiving module 601, configured to receive a first data packet, where the first data packet includes an Ethernet frame header and an IP series packet header;

A compression module 602, configured to compress at least the Ethernet frame header in the first data packet to obtain a second data packet, where the second data packet at least includes a first compressed packet header;

Wherein, the first compressed packet header is a compressed packet header obtained by compressing the Ethernet frame header.

Optionally, the compression module 602 includes one of the following:

a first compression submodule, configured to compress the Ethernet frame header and the IP series header respectively, to obtain a second data packet including the first compressed header and the second compressed header;

a second compression submodule, configured to compress the Ethernet frame header to obtain a second data packet including the first compressed header and the IP series header;

Wherein, the second compressed packet header is a compressed packet header obtained by compressing the IP series packet header.

Optionally, the first compression submodule includes:

a first compression unit, configured to perform compression processing on the Ethernet frame header by an Ethernet frame compression entity to obtain a first sub-packet including the first compressed header;

a second compression unit, configured to perform compression processing on the IP series header by the robust header compression ROHC entity to obtain a second sub-packet including the second compressed header;

A combining unit, configured to combine the first sub-packet and the second sub-packet to obtain a second data packet including the first compressed packet header and the second compressed packet header.

Optionally, the first compression submodule further includes:

a separation unit, configured to separate the first data packet into a third sub-data packet and a fourth sub-data packet, where the third sub-data packet includes the Ethernet frame header, and the fourth sub-data packet includes the IP series header;

The first compression unit is specifically used for:

Performing compression processing on the Ethernet frame header in the third sub-packet by an Ethernet frame compression entity to obtain a first sub-packet including the first compressed header;

The second compression unit is specifically used for:

The IP series header in the fourth sub-packet is compressed by the ROHC entity to obtain a second sub-packet including the second compressed header.

Optionally, the first compression submodule includes:

a third compression unit, configured to perform compression processing on the Ethernet frame header in the first data packet by an Ethernet frame compression entity, to obtain a third data packet including the first compressed packet header and the IP series packet header;

The fourth compression unit is configured to perform compression processing on the IP series header in the third data packet by using the ROHC entity to obtain a second data packet including the first compressed packet header and the second compressed packet header.

Optionally, the fourth compression unit is specifically used for:

Remove and separate the first compressed packet header from the third data packet to obtain a fourth data packet including the IP series packet header;

Perform compression processing on the IP series header in the fourth data packet by the ROHC entity, to obtain a fifth data packet including the second compressed header;

The first compressed packet header is added to the header of the fifth data packet to obtain a second data packet including the first compressed packet header and the second compressed packet header.

Optionally, the first compression submodule includes:

a fifth compression unit, configured to perform compression processing on the IP series header in the first data packet by the ROHC entity, to obtain a third data packet including the Ethernet frame header and the second compressed header;

A sixth compression unit, configured to compress the Ethernet frame header in the third data packet by using the Ethernet frame compression entity to obtain a second data packet including a first compressed packet header and a second compressed packet header.

Optionally, the fifth compression unit is specifically used for:

Remove and separate the Ethernet frame header from the first data packet to obtain a fourth data packet including the IP series packet header;

Perform compression processing on the IP series header in the fourth data packet by the ROHC entity, to obtain a fifth data packet including the second compressed header;

The Ethernet frame header is added to the header of the fifth data packet to obtain a third data packet including the Ethernet frame header and the second compressed packet header.

Optionally, the sending end 600 further includes:

The first adding module is configured to add first indication information in the first compressed packet header; the first indication information is used to indicate the Ethernet frame domain combination mode or preset bit stream corresponding to the first data stream, and the pre- It is assumed that the bit stream is used to associate the Ethernet frame domain combination corresponding to the first data stream, and the first data stream is a set of data packets with the same compression characteristics.

Optionally, the first indication information is further used to indicate an Ethernet frame header format corresponding to the first data stream.

Optionally, the sending end 600 further includes:

A second adding module, configured to add second indication information to the second data packet, where the second indication information is used to indicate the length of the first compressed packet header.

Optionally, the sending end 600 further includes:

A removing module, configured to remove at least one of the length field and the padding field carried in the first data packet by using the Ethernet frame compression entity.

Optionally, the sending end 600 further includes a third adding module, and the third adding module is used for at least one of the following:

adding third indication information to the second data packet, where the third indication information is used to indicate whether the length field carried in the first data packet is removed;

adding fourth indication information to the second data packet, where the fourth indication information is used to indicate whether the padding field carried in the first data packet is removed;

Fifth indication information is added to the second data packet, where the fifth indication information is used to indicate whether the length field and the padding field carried in the first data packet are removed.

It should be noted that, in this embodiment of the present invention, the above-mentioned transmitting end 600 may be a transmitting end of any implementation manner in the method embodiment, and any implementation of the transmitting end in the method embodiment may be used by the above-mentioned transmitting end 600 in this embodiment of the present invention. and achieve the same beneficial effect, in order to avoid repetition, details are not repeated here.

FIG. 11 is a structural diagram of a receiving end provided by an embodiment of the present invention. As shown in FIG. 11 , the receiving end 700 includes:

a receiving module 701, configured to receive a first data packet, where the first data packet includes at least a first compressed packet header;

A decompression module 702, configured to decompress the compressed header in the first data packet to obtain a second data packet including an Ethernet frame header and an IP series header;

Wherein, the first compressed packet header is a compressed packet header obtained by compressing the Ethernet frame header.

Optionally, the first data packet further includes a second compressed packet header, and the second compressed packet header is a compressed packet header obtained by compressing the IP series packet headers;

The decompression module 702 includes:

a first decompression submodule, configured to perform decompression processing on the first compressed packet header by the Ethernet frame decompression entity to obtain the first sub-data packet including the Ethernet frame header;

The second decompression submodule is used for decompressing the second compressed packet header through the robustness header compression ROHC decompression entity to obtain the second sub-data packet including the IP series packet header;

A combining submodule is configured to combine the first sub-data packet and the second sub-data packet to obtain a second data packet including the Ethernet frame header and the IP series packet header.

Optionally, the decompression module 702 further includes:

A separation sub-module, configured to separate the first data packet into a third sub-data packet and a fourth sub-data packet, where the third sub-data packet includes the first compressed header, and the fourth sub-data packet includes the second compressed packet header;

The first decompression submodule is specifically used for:

Perform decompression processing on the first compressed header in the third sub-packet by the Ethernet frame decompression entity to obtain the first sub-packet including the Ethernet frame header;

The second decompression submodule is specifically used for:

The second compressed header in the fourth sub-packet is decompressed by the ROHC decompression entity to obtain the second sub-packet including the IP series header.

Optionally, the first data packet further includes a second compressed packet header, and the second compressed packet header is a compressed packet header obtained by compressing the IP series packet headers;

The decompression module 702 includes:

A third decompression submodule, configured to decompress the second compressed header in the first data packet by using the ROHC decompression entity to obtain third data including the first compressed header and the IP series header Bag;

The fourth decompression submodule is used for decompressing the first compressed packet header in the third data packet by using the Ethernet frame decompression entity to obtain the second data including the Ethernet frame header and the IP series packet header Bag.

Optionally, the third decompression submodule is specifically used for:

Separating the first compressed packet header from the first data packet to obtain a fourth data packet including the second compressed packet header;

The second compressed header in the fourth data packet is decompressed by the ROHC decompression entity to obtain the fifth data packet including the IP series header;

The first compressed packet header is added to the header of the fifth data packet to obtain a third data packet including the first compressed packet header and the IP series packet header.

Optionally, the first data packet further includes a second compressed packet header, and the second compressed packet header is a compressed packet header obtained by compressing the IP series packet headers;

The decompression module 702 includes:

The fifth decompression sub-module is used for decompressing the first compressed packet header in the first data packet by using the Ethernet frame decompression entity to obtain a third compressed packet header including the Ethernet frame header and the second compressed packet header. data pack;

The sixth decompression submodule is used for decompressing the second compressed packet header in the third data packet through the ROHC decompression entity to obtain the second data packet including the Ethernet frame header and the IP series packet header .

Optionally, the sixth decompression submodule is specifically used for:

Separate the Ethernet frame header from the third data packet to obtain a fourth data packet including the second compressed packet header;

The second compressed header in the fourth data packet is decompressed by the ROHC decompression entity to obtain the fifth data packet including the IP series header;

The Ethernet frame header is added to the header of the fifth data packet to obtain a second data packet including the Ethernet frame header and the IP series packet header.

Optionally, the first data packet includes a first compressed header;

The receiving end 700 also includes:

a first determining module, configured to determine the length of the first compressed packet header;

A second determining module, configured to determine the first compressed packet header in the first data packet according to the length of the first compressed packet header.

Optionally, the length of the first compressed packet header is determined by at least one of the following:

the first indication information carried in the first data packet, where the first indication information is used to indicate the length of the first compressed packet header;

The length of the first compressed packet header corresponding to the format of the Ethernet frame header of the first data packet based on the protocol agreement.

Optionally, the first compressed packet header carries second indication information, where the second indication information is used to indicate an Ethernet frame domain combination mode or a preset bit stream corresponding to the first data stream, and the preset bit stream uses For associating the Ethernet frame domain combination corresponding to the first data stream, the first data stream is a set of data packets with the same compression characteristics.

Optionally, the second indication information is further used to indicate the Ethernet frame header format corresponding to the first data stream.

Optionally, the receiving end 700 further includes:

a third determining module, configured to determine, according to the second indication information, whether a length field needs to be added to the second data packet;

a first adding module, configured to add the length field at a specific position of the second data packet through an Ethernet frame decompression entity;

Wherein, the specific location is determined based on the second indication information.

Optionally, the receiving end 700 further includes:

a fourth determining module, configured to determine whether a length field needs to be added to the second data packet according to the third indication information carried in the first data packet;

a second adding module, configured to add the length field at a specific position of the second data packet through the Ethernet frame decompression entity;

Wherein, the third indication information is used to indicate whether the length field is removed before the first data packet is compressed.

Optionally, the receiving end 700 further includes:

a fifth determination module, configured to determine whether a padding field needs to be added to the second data packet according to the minimum Ethernet frame size agreed upon in the protocol, or according to the fourth indication information carried in the first data packet;

The third adding module is used to add a padding field at the end of the second data packet through the Ethernet frame decompression entity;

Wherein, the fourth indication information is used to indicate whether the padding field is removed before the first data packet is compressed.

It should be noted that, in this embodiment of the present invention, the above-mentioned receiving end 900 may be a receiving end of any implementation manner in the method embodiment, and any implementation of the receiving end in the method embodiment may be recognized by the above-mentioned receiving end 700 in this embodiment of the present invention. and achieve the same beneficial effect, in order to avoid repetition, details are not repeated here.

12 is a schematic diagram of the hardware structure of a terminal implementing various embodiments of the present invention. The terminal 800 includes but is not limited to: a radio frequency unit 801, a network module 802, an audio output unit 803, an input unit 804, a sensor 805, a display unit 806, User input unit 807, interface unit 808, memory 809, processor 810, power supply 811 and other components. Those skilled in the art can understand that the structure shown in FIG. 12 does not constitute a limitation on the sending end, and the terminal may include more or less components than the one shown, or combine some components, or arrange different components. In the embodiment of the present invention, the terminal includes but is not limited to a mobile phone, a tablet computer, a notebook computer, a palmtop computer, a vehicle-mounted terminal, a wearable device, a pedometer, and the like.

The terminal 800 may serve as both a sending end in this embodiment of the present invention and a receiving end in this embodiment of the present invention. During the uplink transmission, the terminal 800 may serve as the sending end; during the downlink transmission, the terminal 800 may serve as the receiving end.

During uplink transmission, the terminal 800 acts as a transmitting end and executes the following data processing method.

The radio frequency unit 801 is used for:

Receive a first data packet, where the first data packet includes an Ethernet frame header and an IP series header;

Processor 810 is used to:

Perform compression processing on at least the Ethernet frame header in the first data packet to obtain a second data packet, and the second data packet includes at least the first compressed packet header;

Wherein, the first compressed packet header is a compressed packet header obtained by compressing the Ethernet frame header.

Optionally, the processor 810 is specifically used for one of the following:

compressing the Ethernet frame header and the IP series packet header respectively to obtain a second data packet including the first compressed packet header and the second compressed packet header;

compressing the Ethernet frame header to obtain a second data packet including the first compressed packet header and the IP series packet header;

Wherein, the second compressed packet header is a compressed packet header obtained by compressing the IP series packet header.

Optionally, the processor 810 is specifically configured to:

Performing compression processing on the Ethernet frame header by the Ethernet frame compression entity to obtain a first sub-packet including the first compressed header;

The IP series packet header is compressed by the robustness header compression ROHC entity to obtain a second sub-data packet including the second compressed packet header;

The first sub-packet and the second sub-packet are combined to obtain a second data packet including the first compressed packet header and the second compressed packet header.

Optionally, the processor 810 is further configured to:

Separating the first data packet into a third sub-data packet and a fourth sub-data packet, the third sub-data packet includes the Ethernet frame header, and the fourth sub-data packet includes the IP series header;

The processor 810 is specifically used for:

Performing compression processing on the Ethernet frame header in the third sub-packet by an Ethernet frame compression entity to obtain a first sub-packet including the first compressed header;

The IP series header in the fourth sub-packet is compressed by the ROHC entity to obtain a second sub-packet including the second compressed header.

Optionally, the processor 810 is specifically configured to:

Performing compression processing on the Ethernet frame header in the first data packet by the Ethernet frame compression entity to obtain a third data packet including the first compressed packet header and the IP series packet header;

The IP series header in the third data packet is compressed by the ROHC entity to obtain a second data packet including the first compressed header and the second compressed header.

Optionally, the processor 810 is specifically configured to:

Separating the first compressed packet header from the third data packet to obtain a fourth data packet including the IP series packet header;

Perform compression processing on the IP series header in the fourth data packet by the ROHC entity, to obtain a fifth data packet including the second compressed header;

The first compressed packet header is added to the header of the fifth data packet to obtain a second data packet including the first compressed packet header and the second compressed packet header.

Optionally, the processor 810 is specifically configured to:

Perform compression processing on the IP series header in the first data packet by the ROHC entity, to obtain a third data packet including the Ethernet frame header and the second compressed header;

The Ethernet frame header in the third data packet is compressed by the Ethernet frame compression entity to obtain a second data packet including a first compressed packet header and a second compressed packet header.

Optionally, the processor 810 is specifically configured to:

Separate the Ethernet frame header from the first data packet to obtain a fourth data packet including the IP series packet header;

Perform compression processing on the IP series header in the fourth data packet by the ROHC entity, to obtain a fifth data packet including the second compressed header;

The Ethernet frame header is added to the header of the fifth data packet to obtain a third data packet including the Ethernet frame header and the second compressed packet header.

Optionally, the processor 810 is further configured to:

First indication information is added to the first compressed packet header; the first indication information is used to indicate an Ethernet frame domain combination mode or a preset bit stream corresponding to the first data stream, and the preset bit stream is used to associate the An Ethernet frame domain combination corresponding to a first data stream, where the first data stream is a set of data packets with the same compression characteristics.

Optionally, the first indication information is further used to indicate an Ethernet frame header format corresponding to the first data stream.

Optionally, the processor 810 is further configured to:

Adding second indication information to the second data packet, where the second indication information is used to indicate the length of the first compressed packet header.

Optionally, the processor 810 is further configured to:

At least one of the length field and the padding field carried in the first data packet is removed by using the Ethernet frame compression entity.

Optionally, the processor 810 is also used for at least one of the following:

adding third indication information to the second data packet, where the third indication information is used to indicate whether the length field carried in the first data packet is removed;

adding fourth indication information to the second data packet, where the fourth indication information is used to indicate whether the padding field carried in the first data packet is removed;

Fifth indication information is added to the second data packet, where the fifth indication information is used to indicate whether the length field and the padding field carried in the first data packet are removed.

In the embodiment of the present invention, the transmitting end can at least compress the Ethernet frame header in the Ethernet frame data. In this way, when the Ethernet frame data is transmitted between the transmitting end and the receiving end, the required transmission resources are reduced, so that the Ethernet frame data can be reduced. Transmission resource overhead of frame data.

During downlink transmission, the terminal 800 acts as a receiving end and executes the following data processing method.

The radio frequency unit 801 is used for:

receiving a first data packet, the first data packet including at least a first compressed packet header;

Processor 810 is used to:

Decompressing the compressed header in the first data packet to obtain the second data packet including the Ethernet frame header and the IP series header;

Wherein, the first compressed packet header is a compressed packet header obtained by compressing the Ethernet frame header.

Optionally, the first data packet further includes a second compressed packet header, and the second compressed packet header is a compressed packet header obtained by compressing the IP series packet headers;

The processor 810 is specifically used for:

Perform decompression processing on the first compressed packet header by the Ethernet frame decompression entity to obtain the first sub-packet including the Ethernet frame header;

The second compressed packet header is decompressed by the robustness header compression ROHC decompression entity to obtain the second sub-data packet including the IP series packet header;

The first sub-data packet and the second data packet of the first Ethernet frame header and the IP series packet header.

Optionally, the processor 810 is further configured to:

Separating the first data packet into a third sub-data packet and a fourth sub-data packet, the third sub-data packet includes the first compressed packet header, and the fourth sub-data packet includes the second compressed packet header ;

The processor 810 is specifically used for:

Perform decompression processing on the first compressed header in the third sub-packet by the Ethernet frame decompression entity to obtain the first sub-packet including the Ethernet frame header;

The second compressed header in the fourth sub-packet is decompressed by the ROHC decompression entity to obtain the second sub-packet including the IP series header.

Optionally, the first data packet further includes a second compressed packet header, and the second compressed packet header is a compressed packet header obtained by compressing the IP series packet headers;

The processor 810 is specifically used for:

Perform decompression processing on the second compressed packet header in the first data packet by the ROHC decompression entity to obtain a third data packet including the first compressed packet header and the IP series packet header;

The first compressed packet header in the third data packet is decompressed by the Ethernet frame decompression entity to obtain a second data packet including the Ethernet frame header and the IP series packet header.

Optionally, the processor 810 is specifically configured to:

Separating the first compressed packet header from the first data packet to obtain a fourth data packet including the second compressed packet header;

The second compressed header in the fourth data packet is decompressed by the ROHC decompression entity to obtain the fifth data packet including the IP series header;

The first compressed packet header is added to the header of the fifth data packet to obtain a third data packet including the first compressed packet header and the IP series packet header.

Optionally, the first data packet further includes a second compressed packet header, and the second compressed packet header is a compressed packet header obtained by compressing the IP series packet headers;

The processor 810 is specifically used for:

Perform decompression processing on the first compressed packet header in the first data packet by the Ethernet frame decompression entity to obtain a third data packet including the Ethernet frame header and the second compressed packet header;

The ROHC decompression entity performs decompression processing on the second compressed packet header in the third data packet to obtain a second data packet including the Ethernet frame header and the IP series packet header.

Optionally, the processor 810 is specifically configured to:

Separate the Ethernet frame header from the third data packet to obtain a fourth data packet including the second compressed packet header;

The second compressed header in the fourth data packet is decompressed by the ROHC decompression entity to obtain the fifth data packet including the IP series header;

The Ethernet frame header is added to the header of the fifth data packet to obtain a second data packet including the Ethernet frame header and the IP series packet header.

Optionally, the first data packet includes a first compressed header;

Processor 810 is also used to:

determining the length of the first compressed packet header;

The first compressed packet header in the first data packet is determined according to the length of the first compressed packet header.

Optionally, the length of the first compressed packet header is determined by at least one of the following:

the first indication information carried in the first data packet, where the first indication information is used to indicate the length of the first compressed packet header;

The length of the first compressed packet header corresponding to the format of the Ethernet frame header of the first data packet based on the protocol agreement.

Optionally, the first compressed packet header carries second indication information, where the second indication information is used to indicate an Ethernet frame domain combination mode or a preset bit stream corresponding to the first data stream, and the preset bit stream uses For associating the Ethernet frame domain combination corresponding to the first data stream, the first data stream is a set of data packets with the same compression characteristics.

Optionally, the second indication information is further used to indicate the Ethernet frame header format corresponding to the first data stream.

Optionally, the processor 810 is further configured to:

According to the second indication information, determine whether a length field needs to be added to the second data packet;

If so, add the length field at a specific position of the second data packet through the Ethernet frame decompression entity;

Wherein, the specific location is determined based on the second indication information.

Optionally, the processor 810 is further configured to:

determining, according to the third indication information carried in the first data packet, whether a length field needs to be added to the second data packet;

If so, add the length field at a specific position of the second data packet through the Ethernet frame decompression entity;

Wherein, the third indication information is used to indicate whether the length field is removed before the first data packet is compressed.

Optionally, the processor 810 is further configured to:

According to the minimum Ethernet frame size agreed in the protocol, or, according to the fourth indication information carried in the first data packet, determine whether a padding field needs to be added to the second data packet;

If so, add a padding field at the end of the second data packet through the Ethernet frame decompression entity;

Wherein, the fourth indication information is used to indicate whether the padding field is removed before the first data packet is compressed.

In the embodiment of the present invention, the sending end can at least perform compression processing on the Ethernet frame header in the Ethernet frame data, and the receiving end can perform decompression processing on the compressed Ethernet frame data. When transmitting between them, the required transmission resources are reduced, so that the transmission resource overhead of the Ethernet frame data can be reduced.

It should be understood that, in this embodiment of the present invention, the radio frequency unit 801 can be used for receiving and sending signals during sending and receiving of information or during a call. Specifically, after receiving the downlink data from the network side device, it is processed by the processor 810; , and send the uplink data to the network side device. Generally, the radio frequency unit 801 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like. In addition, the radio frequency unit 801 can also communicate with the network and other devices through a wireless communication system.

The sending end provides the user with wireless broadband Internet access through the network module 802, such as helping the user to send and receive emails, browse web pages, and access streaming media.

The audio output unit 803 may convert audio data received by the radio frequency unit 801 or the network module 802 or stored in the memory 809 into audio signals and output as sound. Also, the audio output unit 803 may also provide audio output related to a specific function performed by the terminal 800 (eg, call signal reception sound, message reception sound, etc.). The audio output unit 803 includes a speaker, a buzzer, a receiver, and the like.

The input unit 804 is used to receive audio or video signals. The input unit 804 may include a graphics processor (Graphics Processing Unit, GPU) 8041 and a microphone 8042, and the graphics processor 8041 captures images of still pictures or videos obtained by an image capture device (such as a camera) in a video capture mode or an image capture mode data is processed. The processed image frames may be displayed on the display unit 806 . The image frames processed by the graphics processor 8041 may be stored in the memory 809 (or other storage medium) or transmitted via the radio frequency unit 801 or the network module 802 . The microphone 8042 can receive sound and can process such sound into audio data. The processed audio data can be converted into a format that can be sent to the device on the mobile communication network side via the radio frequency unit 801 for output in the case of a telephone call mode.

The terminal 800 also includes at least one sensor 805, such as a light sensor, a motion sensor, and other sensors. Specifically, the light sensor includes an ambient light sensor and a proximity sensor, wherein the ambient light sensor can adjust the brightness of the display panel 8061 according to the brightness of the ambient light, and the proximity sensor can turn off the display panel 8061 and the backlight when the terminal 800 is moved to the ear . As a kind of motion sensor, the accelerometer sensor can detect the magnitude of acceleration in all directions (usually three axes), and can detect the magnitude and direction of gravity when stationary, which can be used to identify the posture of the sender (such as horizontal and vertical screen switching, related games , magnetometer attitude calibration), vibration recognition related functions (such as pedometer, tapping), etc.; the sensor 805 may also include a fingerprint sensor, a pressure sensor, an iris sensor, a molecular sensor, a gyroscope, a barometer, a hygrometer, a thermometer, Infrared sensors, etc., are not repeated here.

The display unit 806 is used to display information input by the user or information provided to the user. The display unit 806 may include a display panel 8061, and the display panel 8061 may be configured in the form of a liquid crystal display (LCD), an organic light-emitting diode (OLED), or the like.

The user input unit 807 can be used for receiving inputted numerical or character information, and generating key signal input related to user setting and function control of the transmitting end. Specifically, the user input unit 807 includes a touch panel 8071 and other input devices 8072 . The touch panel 8071, also referred to as a touch screen, collects the user's touch operations on or near it (such as the user's finger, stylus, etc., any suitable object or accessory on or near the touch panel 8071). operate). The touch panel 8071 may include two parts, a touch detection device and a touch controller. Among them, the touch detection device detects the user's touch orientation, detects the signal brought by the touch operation, and transmits the signal to the touch controller; the touch controller receives the touch information from the touch detection device, converts it into contact coordinates, and then sends it to the touch controller. To the processor 810, the command sent by the processor 810 is received and executed. In addition, the touch panel 8071 can be realized by various types of resistive, capacitive, infrared, and surface acoustic waves. In addition to the touch panel 8071 , the user input unit 807 may also include other input devices 8072 . Specifically, other input devices 8072 may include, but are not limited to, physical keyboards, function keys (such as volume control keys, switch keys, etc.), trackballs, mice, and joysticks, which will not be repeated here.

Further, the touch panel 8071 can be covered on the display panel 8071. When the touch panel 8071 detects a touch operation on or near it, it transmits it to the processor 810 to determine the type of the touch event, and then the processor 810 determines the type of the touch event according to the touch The type of event provides a corresponding visual output on the display panel 8061. Although in FIG. 9, the touch panel 8071 and the display panel 8061 are used as two independent components to realize the input and output functions of the transmitting end, in some embodiments, the touch panel 8071 and the display panel 8061 can be integrated to form Realize the input and output functions of the sending end, which is not limited here.

The interface unit 808 is an interface for connecting an external device to the terminal 800 . For example, external devices may include wired or wireless headset ports, external power (or battery charger) ports, wired or wireless data ports, memory card ports, ports for connecting devices with identification modules, audio input/output (I/O) ports, video I/O ports, headphone ports, and more. The interface unit 808 may be used to receive input (eg, data information, power, etc.) from an external device and transmit the received input to one or more elements within the terminal 800 or may be used to communicate between the terminal 800 and the external device. transfer data between.

The memory 809 may be used to store software programs as well as various data. The memory 809 may mainly include a stored program area and a stored data area, wherein the stored program area may store an operating system, an application program (such as a sound playback function, an image playback function, etc.) required for at least one function, and the like; Data created by the use of the mobile phone (such as audio data, phone book, etc.), etc. Additionally, memory 809 may include high-speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid state storage device.

The processor 810 is the control center of the sending end, uses various interfaces and lines to connect various parts of the entire sending end, and executes the sending end by running or executing the software programs and modules stored in the memory 809, and calling the data stored in the memory 809. Various functions and processing data for overall monitoring of the sender. The processor 810 may include one or more processing units; preferably, the processor 810 may integrate an application processor and a modem processor, wherein the application processor mainly processes the operating system, user interface, and application programs, etc., and the modem The processor mainly handles wireless communication. It can be understood that, the above-mentioned modulation and demodulation processor may not be integrated into the processor 810.

The terminal 800 may also include a power supply 811 (such as a battery) for supplying power to various components. Preferably, the power supply 811 may be logically connected to the processor 810 through a power management system, so as to manage charging, discharging, and power consumption management through the power management system. Function.

In addition, the terminal 800 includes some unshown functional modules, which are not repeated here.

Preferably, an embodiment of the present invention further provides a terminal, including a processor 810, a memory 809, a computer program stored in the memory 809 and running on the processor 810, and the computer program is implemented when the processor 810 executes it. The various processes of the above data processing method embodiments can achieve the same technical effect, and are not repeated here in order to avoid repetition.

It should be noted that, in this embodiment, the above-mentioned terminal 800 may be a sending end of any implementation in the method embodiments in the embodiments of the present invention, or may be a receiving end in any implementation in the method embodiments in the embodiments of the present invention. Any implementation of the transmitting end or the receiving end in the method embodiment in the embodiment of the present invention can be implemented by the above-mentioned terminal 800 in this embodiment, and achieve the same beneficial effects, which will not be repeated here.

FIG. 13 is a structural diagram of a network side device according to an embodiment of the present invention. As shown in FIG. 13 , the network side device 900 includes: a processor 901 , a transceiver 902 , a memory 903 and a bus interface.

The network-side device 900 may serve as both a sending end in this embodiment of the present invention and a receiving end in this embodiment of the present invention. During uplink transmission, the network-side device 900 may serve as a receiving end; during downlink transmission, the network-side device 900 may serve as a sending end.

During uplink transmission, the network-side device 900 acts as a receiving end and executes the following data processing method.

Transceiver 902 is used to:

receiving a first data packet, the first data packet including at least a first compressed packet header;

Processor 901 is used to:

Decompressing the compressed header in the first data packet to obtain the second data packet including the Ethernet frame header and the IP series header;

Wherein, the first compressed packet header is a compressed packet header obtained by compressing the Ethernet frame header.

Optionally, the first data packet further includes a second compressed packet header, and the second compressed packet header is a compressed packet header obtained by compressing the IP series packet headers;

The processor 901 is specifically used for:

Perform decompression processing on the first compressed packet header by the Ethernet frame decompression entity to obtain the first sub-packet including the Ethernet frame header;

The second compressed packet header is decompressed by the robustness header compression ROHC decompression entity to obtain the second sub-data packet including the IP series packet header;

Using the first sub-packet and the optional first sub-packet, the processor 901 is further configured to:

Separating the first data packet into a third sub-data packet and a fourth sub-data packet, the third sub-data packet includes the first compressed packet header, and the fourth sub-data packet includes the second compressed packet header ;

The processor 901 is specifically used for:

Perform decompression processing on the first compressed header in the third sub-packet by the Ethernet frame decompression entity to obtain the first sub-packet including the Ethernet frame header;

The second compressed header in the fourth sub-packet is decompressed by the ROHC decompression entity to obtain the second sub-packet including the IP series header.

Optionally, the first data packet further includes a second compressed packet header, and the second compressed packet header is a compressed packet header obtained by compressing the IP series packet headers;

The processor 901 is specifically used for:

Perform decompression processing on the second compressed packet header in the first data packet by the ROHC decompression entity to obtain a third data packet including the first compressed packet header and the IP series packet header;

The first compressed packet header in the third data packet is decompressed by the Ethernet frame decompression entity to obtain a second data packet including the Ethernet frame header and the IP series packet header.

Optionally, the processor 901 is specifically used for:

Separating the first compressed packet header from the first data packet to obtain a fourth data packet including the second compressed packet header;

The second compressed header in the fourth data packet is decompressed by the ROHC decompression entity to obtain the fifth data packet including the IP series header;

The first compressed packet header is added to the header of the fifth data packet to obtain a third data packet including the first compressed packet header and the IP series packet header.

Optionally, the first data packet further includes a second compressed packet header, and the second compressed packet header is a compressed packet header obtained by compressing the IP series packet headers;

The processor 901 is specifically used for:

Perform decompression processing on the first compressed packet header in the first data packet by the Ethernet frame decompression entity to obtain a third data packet including the Ethernet frame header and the second compressed packet header;

The ROHC decompression entity performs decompression processing on the second compressed packet header in the third data packet to obtain a second data packet including the Ethernet frame header and the IP series packet header.

Optionally, the processor 901 is specifically used for:

Separate the Ethernet frame header from the third data packet to obtain a fourth data packet including the second compressed packet header;

The second compressed header in the fourth data packet is decompressed by the ROHC decompression entity to obtain the fifth data packet including the IP series header;

The Ethernet frame header is added to the header of the fifth data packet to obtain a second data packet including the Ethernet frame header and the IP series packet header.

Optionally, the first data packet includes a first compressed header;

Processor 901 is also used to:

determining the length of the first compressed packet header;

The first compressed packet header in the first data packet is determined according to the length of the first compressed packet header.

Optionally, the length of the first compressed packet header is determined by at least one of the following:

the first indication information carried in the first data packet, where the first indication information is used to indicate the length of the first compressed packet header;

The length of the first compressed packet header corresponding to the format of the Ethernet frame header of the first data packet based on the protocol agreement.

Optionally, the first compressed packet header carries second indication information, where the second indication information is used to indicate an Ethernet frame domain combination mode or a preset bit stream corresponding to the first data stream, and the preset bit stream uses For associating the Ethernet frame domain combination corresponding to the first data stream, the first data stream is a set of data packets with the same compression characteristics.

Optionally, the second indication information is further used to indicate the Ethernet frame header format corresponding to the first data stream.

Optionally, the processor 901 is further configured to:

According to the second indication information, determine whether a length field needs to be added to the second data packet;

If so, add the length field at a specific position of the second data packet through the Ethernet frame decompression entity;

Wherein, the specific location is determined based on the second indication information.

Optionally, the processor 901 is further configured to:

determining, according to the third indication information carried in the first data packet, whether a length field needs to be added to the second data packet;

If so, add the length field at a specific position of the second data packet through the Ethernet frame decompression entity;

Wherein, the third indication information is used to indicate whether the length field is removed before the first data packet is compressed.

Optionally, the processor 901 is further configured to:

According to the minimum Ethernet frame size agreed in the protocol, or, according to the fourth indication information carried in the first data packet, determine whether a padding field needs to be added to the second data packet;

If so, add a padding field at the end of the second data packet through the Ethernet frame decompression entity;

Wherein, the fourth indication information is used to indicate whether the padding field is removed before the first data packet is compressed.

In the embodiment of the present invention, the sending end can at least perform compression processing on the Ethernet frame header in the Ethernet frame data, and the receiving end can perform decompression processing on the compressed Ethernet frame data. When transmitting between them, the required transmission resources are reduced, so that the transmission resource overhead of the Ethernet frame data can be reduced.

During downlink transmission, the network-side device 900 acts as a sender and executes the following data processing methods.

Transceiver 902 is used to:

Receive a first data packet, where the first data packet includes an Ethernet frame header and an IP series header;

Processor 901 is used to:

Perform compression processing on at least the Ethernet frame header in the first data packet to obtain a second data packet, and the second data packet includes at least the first compressed packet header;

Wherein, the first compressed packet header is a compressed packet header obtained by compressing the Ethernet frame header.

Optionally, the processor 901 is specifically used for one of the following:

compressing the Ethernet frame header and the IP series packet header respectively to obtain a second data packet including the first compressed packet header and the second compressed packet header;

compressing the Ethernet frame header to obtain a second data packet including the first compressed packet header and the IP series packet header;

Wherein, the second compressed packet header is a compressed packet header obtained by compressing the IP series packet header.

Optionally, the processor 901 is specifically used for:

Performing compression processing on the Ethernet frame header by the Ethernet frame compression entity to obtain a first sub-packet including the first compressed header;

The IP series packet header is compressed by the robustness header compression ROHC entity to obtain a second sub-data packet including the second compressed packet header;

Combining the first sub-packet with the second data packet including the first compressed packet header and the second compressed packet header.

Optionally, the processor 901 is further configured to:

Separating the first data packet into a third sub-data packet and a fourth sub-data packet, the third sub-data packet includes the Ethernet frame header, and the fourth sub-data packet includes the IP series header;

The processor 901 is specifically used for:

Performing compression processing on the Ethernet frame header in the third sub-packet by an Ethernet frame compression entity to obtain a first sub-packet including the first compressed header;

The IP series header in the fourth sub-packet is compressed by the ROHC entity to obtain a second sub-packet including the second compressed header.

Optionally, the processor 901 is specifically used for:

Performing compression processing on the Ethernet frame header in the first data packet by the Ethernet frame compression entity to obtain a third data packet including the first compressed packet header and the IP series packet header;

The IP series header in the third data packet is compressed by the ROHC entity to obtain a second data packet including the first compressed header and the second compressed header.

Optionally, the processor 901 is specifically used for:

Separating the first compressed packet header from the third data packet to obtain a fourth data packet including the IP series packet header;

Perform compression processing on the IP series header in the fourth data packet by the ROHC entity, to obtain a fifth data packet including the second compressed header;

The first compressed packet header is added to the header of the fifth data packet to obtain a second data packet including the first compressed packet header and the second compressed packet header.

Optionally, the processor 901 is specifically used for:

Perform compression processing on the IP series header in the first data packet by the ROHC entity, to obtain a third data packet including the Ethernet frame header and the second compressed header;

The Ethernet frame header in the third data packet is compressed by the Ethernet frame compression entity to obtain a second data packet including a first compressed packet header and a second compressed packet header.

Optionally, the processor 901 is specifically used for:

Separate the Ethernet frame header from the first data packet to obtain a fourth data packet including the IP series packet header;

Perform compression processing on the IP series header in the fourth data packet by the ROHC entity, to obtain a fifth data packet including the second compressed header;

The Ethernet frame header is added to the header of the fifth data packet to obtain a third data packet including the Ethernet frame header and the second compressed packet header.

Optionally, the processor 901 is further configured to:

First indication information is added to the first compressed packet header; the first indication information is used to indicate an Ethernet frame domain combination mode or a preset bit stream corresponding to the first data stream, and the preset bit stream is used to associate the An Ethernet frame domain combination corresponding to a first data stream, where the first data stream is a set of data packets with the same compression characteristics.

Optionally, the first indication information is further used to indicate an Ethernet frame header format corresponding to the first data stream.

Optionally, the processor 901 is further configured to:

Adding second indication information to the second data packet, where the second indication information is used to indicate the length of the first compressed packet header.

Optionally, the processor 901 is further configured to:

At least one of the length field and the padding field carried in the first data packet is removed by using the Ethernet frame compression entity.

Optionally, the processor 901 is also used for at least one of the following:

adding third indication information to the second data packet, where the third indication information is used to indicate whether the length field carried in the first data packet is removed;

adding fourth indication information to the second data packet, where the fourth indication information is used to indicate whether the padding field carried in the first data packet is removed;

Fifth indication information is added to the second data packet, where the fifth indication information is used to indicate whether the length field and the padding field carried in the first data packet are removed.

In the embodiment of the present invention, the transmitting end can at least compress the Ethernet frame header in the Ethernet frame data. In this way, when the Ethernet frame data is transmitted between the transmitting end and the receiving end, the required transmission resources are reduced, so that the Ethernet frame data can be reduced. Transmission resource overhead of frame data.

In FIG. 13, the bus architecture may include any number of interconnected buses and bridges, specifically one or more processors represented by processor 901 and various circuits of memory represented by memory 903 linked together. The bus architecture may also link together various other circuits, such as peripherals, voltage regulators, and power management circuits, which are well known in the art and, therefore, will not be described further herein. The bus interface provides the interface. Transceiver 902 may be a number of elements, including a transmitter and a receiver, that provide a means for communicating with various other devices over a transmission medium. For different terminals, the user interface 904 may also be an interface capable of externally connecting a required device, and the connected devices include but are not limited to a keypad, a display, a speaker, a microphone, a joystick, and the like.

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

It should be noted that, in this embodiment, the above-mentioned network-side device 900 may be a sending end of any implementation of the method embodiments in the embodiments of the present invention, or may be a receiving end of any implementation of the method embodiments in the embodiments of the present invention , any implementation of the transmitting end or the receiving end in the method embodiment in the embodiment of the present invention can be implemented by the network side device 900 in this embodiment, and achieve the same beneficial effect, which is not repeated here.

Embodiments of the present invention further provide a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, each process of the foregoing embodiment corresponding to the sending end or the receiving end is implemented, and can To achieve the same technical effect, in order to avoid repetition, details are not repeated here. The computer-readable storage medium is, for example, a read-only memory (Read-Only Memory, ROM for short), a random access memory (Random Access Memory, RAM for short), a magnetic disk or an optical disk, and the like.

It should be noted that, herein, the terms "comprising", "comprising" or any other variation thereof are intended to encompass non-exclusive inclusion, such that a process, method, article or device comprising a series of elements includes not only those elements, It also includes other elements not expressly listed or inherent to such a process, method, article or apparatus. Without further limitation, an element qualified by the phrase "comprising a..." does not preclude the presence of additional identical elements in a process, method, article or apparatus that includes the element.

From the description of the above embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus a necessary general hardware platform, and of course hardware can also be used, but in many cases the former is better implementation. Based on this understanding, the technical solutions of the present invention can be embodied in the form of software products in essence or the parts that make contributions to the prior art, and the computer software products are stored in a storage medium (such as ROM/RAM, magnetic disk, CD-ROM), including several instructions to make a terminal (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) execute the methods described in the various embodiments of the present invention.

The above are only specific embodiments of the present invention, but the protection scope of the present invention is not limited thereto. Any person skilled in the art can easily think of changes or substitutions within the technical scope disclosed by the present invention. should be included within the protection scope of the present invention. Therefore, the protection scope of the present invention should be subject to the protection scope of the claims.

Claims (32)

1. A data processing method is applied to a sending end, and is characterized in that the method comprises the following steps:

receiving a first data packet, wherein the first data packet comprises an Ethernet frame header and an IP series packet header;

compressing at least the Ethernet frame header in the first data packet to obtain a second data packet, wherein the second data packet at least comprises a first compressed packet header;

and the first compressed packet header is a compressed packet header obtained by compressing the Ethernet frame header.

2. The method of claim 1, wherein compressing at least the ethernet header in the first packet to obtain a second packet comprises one of:

respectively compressing the Ethernet frame header and the IP series packet header to obtain a second data packet comprising the first compressed packet header and a second compressed packet header;

compressing the Ethernet frame header to obtain a second data packet comprising the first compressed packet header and the IP series packet header;

and the second compressed packet header is a compressed packet header obtained by compressing the IP series packet header.

3. The method according to claim 2, wherein compressing the ethernet header and the IP-based packet header respectively to obtain a second packet including the first compressed packet header and a second compressed packet header comprises:

compressing the Ethernet frame header through an Ethernet frame compression entity to obtain a first sub-packet comprising the first compressed packet header;

compressing the IP series packet header through a robustness header compression ROHC entity to obtain a second sub-packet comprising a second compressed packet header;

and combining the first sub data packet and the second sub data packet to obtain a second data packet comprising the first compressed packet header and the second compressed packet header.

4. The method according to claim 3, wherein before the compressing the Ethernet header and the IP-series header, the method further comprises:

separating the first data packet into a third data packet and a fourth data packet, wherein the third data packet comprises the Ethernet header, and the fourth data packet comprises the IP series packet header;

compressing the ethernet header by an ethernet frame compression entity to obtain a first sub-packet including the first compressed header, including:

compressing the ethernet header in the third sub-packet by an ethernet frame compression entity to obtain a first sub-packet including the first compressed header;

compressing the IP series packet header by the ROHC entity to obtain a second sub packet including the second compressed packet header, including:

and compressing the IP series packet header in the fourth sub-packet through an ROHC entity to obtain a second sub-packet comprising the second compressed packet header.

5. The method according to claim 2, wherein compressing the ethernet header and the IP-based packet header respectively to obtain a second packet including the first compressed packet header and a second compressed packet header comprises:

compressing the Ethernet frame header in the first data packet by an Ethernet frame compression entity to obtain a third data packet comprising the first compressed packet header and the IP series packet header;

and compressing the IP series packet header in the third data packet through an ROHC entity to obtain a second data packet comprising the first compressed packet header and the second compressed packet header.

6. The method according to claim 5, wherein compressing the IP-based packet header in the third data packet by an ROHC entity to obtain a second data packet including the first compressed packet header and the second compressed packet header comprises:

separating the first compressed packet header from the third data packet to obtain a fourth data packet including the IP series packet header;

compressing the IP series packet header in the fourth data packet through an ROHC entity to obtain a fifth data packet comprising the second compressed packet header;

and adding the first compressed packet header to the header of the fifth data packet to obtain a second data packet comprising the first compressed packet header and the second compressed packet header.

7. The method according to claim 2, wherein compressing the ethernet header and the IP-based packet header respectively to obtain a second packet including the first compressed packet header and a second compressed packet header comprises:

compressing the IP series packet header in the first data packet through an ROHC entity to obtain a third data packet comprising the Ethernet header and the second compressed packet header;

and compressing the Ethernet frame header in the third data packet through an Ethernet frame compression entity to obtain a second data packet comprising a first compressed packet header and a second compressed packet header.

8. The method according to claim 7, wherein compressing the IP-based header of the first packet by an ROHC entity to obtain a third packet including the ethernet header and the second compressed header comprises:

separating the Ethernet frame header from the first data packet to obtain a fourth data packet comprising the IP series packet header;

compressing the IP series packet header in the fourth data packet through an ROHC entity to obtain a fifth data packet comprising the second compressed packet header;

and adding the Ethernet frame header to the head of the fifth data packet to obtain a third data packet comprising the Ethernet frame header and the second compressed packet header.

9. The method according to any one of claims 1 to 8, further comprising:

adding first indication information in the first compressed packet header; the first indication information is used to indicate an ethernet frame domain combination mode or a preset bit stream corresponding to a first data stream, where the preset bit stream is used to associate the ethernet frame domain combination corresponding to the first data stream, and the first data stream is a data packet set with the same compression characteristic.

10. The method of claim 9, wherein the first indication information is further used for indicating an ethernet frame header format corresponding to the first data stream.

11. The method according to any one of claims 1 to 8, further comprising:

and adding second indication information in the second data packet, wherein the second indication information is used for indicating the length of the first compressed packet header.

12. The method according to any one of claims 1 to 8, further comprising:

removing at least one of a length field and a padding field carried in the first packet by an Ethernet frame compression entity.

13. The method according to any one of claims 1 to 8, further comprising at least one of:

adding third indication information in the second data packet, wherein the third indication information is used for indicating whether a length field carried in the first data packet is removed or not;

adding fourth indication information in the second data packet, wherein the fourth indication information is used for indicating whether the padding field carried in the first data packet is removed or not;

and adding fifth indication information in the second data packet, wherein the fifth indication information is used for indicating whether the length field and the padding field carried in the first data packet are removed or not.

14. A data processing method is applied to a receiving end, and is characterized by comprising the following steps:

receiving a first data packet, wherein the first data packet at least comprises a first compressed packet header;

decompressing the compressed packet header in the first data packet to obtain a second data packet comprising an Ethernet frame header and an IP series packet header;

the first compressed packet header is obtained by compressing an ethernet header.

15. The method according to claim 14, wherein the first data packet further includes a second compressed packet header, and the second compressed packet header is a compressed packet header obtained by compressing an IP-series packet header;

decompressing the compressed packet header in the first data packet to obtain a second data packet including an ethernet header and an IP-series packet header, including:

decompressing the first compressed packet header through an ethernet frame decompressing entity to obtain a first sub packet including an ethernet frame header;

decompressing the second compressed packet header through a robust header compression ROHC decompression entity to obtain a second sub packet including an IP series packet header;

and combining the first sub data packet and the second sub data packet to obtain a second data packet comprising the Ethernet header and the IP series header.

16. The method of claim 15, wherein before decompressing the first compressed packet header and the second compressed packet header, the method further comprises:

separating the first data packet into a third sub data packet and a fourth sub data packet, wherein the third sub data packet comprises the first compressed packet header, and the fourth sub data packet comprises the second compressed packet header;

decompressing the first compressed packet header by an ethernet frame decompressing entity to obtain a first sub packet including the ethernet frame header, including:

decompressing the first compressed packet header in the third sub packet by an ethernet frame decompressing entity to obtain a first sub packet including an ethernet frame header;

decompressing the second compressed packet header by an ROHC decompressing entity to obtain a second sub packet including an IP series packet header, including:

decompressing the second compressed packet header in the fourth sub packet by an ROHC decompressing entity to obtain a second sub packet including an IP series packet header.

17. The method according to claim 14, wherein the first data packet further includes a second compressed packet header, and the second compressed packet header is a compressed packet header obtained by compressing an IP-series packet header;

decompressing the compressed packet header in the first data packet to obtain a second data packet including an ethernet header and an IP-series packet header, including:

decompressing the second compressed packet header in the first data packet by an ROHC decompressing entity to obtain a third data packet including the first compressed packet header and an IP-series packet header;

and decompressing the first compressed packet header in the third data packet by an ethernet frame decompressing entity to obtain a second data packet comprising the ethernet frame header and the IP series packet header.

18. The method according to claim 17, wherein decompressing, by an ROHC decompression entity, the second compressed packet header in the first packet to obtain a third packet including the first compressed packet header and an IP-series packet header, comprises:

separating the first compressed packet header from the first data packet to obtain a fourth data packet including the second compressed packet header;

decompressing the second compressed packet header in the fourth data packet by an ROHC decompressing entity to obtain a fifth data packet including an IP series packet header;

and adding the first compressed packet header to the header of the fifth data packet to obtain a third data packet comprising the first compressed packet header and the IP series packet header.

19. The method according to claim 14, wherein the first data packet further includes a second compressed packet header, and the second compressed packet header is a compressed packet header obtained by compressing an IP-series packet header;

decompressing the compressed packet header in the first data packet to obtain a second data packet including an ethernet header and an IP-series packet header, including:

decompressing the first compressed packet header in the first data packet by an ethernet frame decompressing entity to obtain a third data packet including an ethernet frame header and the second compressed packet header;

and decompressing the second compressed packet header in the third data packet by an ROHC decompression entity to obtain a second data packet comprising the Ethernet header and the IP series packet header.

20. The method according to claim 19, wherein decompressing, by an ROHC decompression entity, the second compressed packet header in the third packet to obtain a second packet including the ethernet header and an IP-series packet header, comprises:

separating the ethernet header from the third data packet to obtain a fourth data packet including the second compressed packet header;

decompressing the second compressed packet header in the fourth data packet by an ROHC decompressing entity to obtain a fifth data packet including an IP series packet header;

and adding the Ethernet frame header to the header of the fifth data packet to obtain a second data packet comprising the Ethernet frame header and the IP series packet header.

21. The method of any one of claims 14 to 20, wherein the first data packet comprises a first compressed packet header;

before decompressing the first compressed packet header, the method further includes:

determining the length of the first compressed packet header;

and determining the first compressed packet header in the first data packet according to the length of the first compressed packet header.

22. The method of claim 21, wherein the length of the first compressed packet header is determined by at least one of:

first indication information carried in the first data packet, wherein the first indication information is used for indicating the length of the first compressed packet header;

a length of a first compressed packet header corresponding to an Ethernet frame header format of the first packet based on protocol conventions.

23. The method according to any one of claims 14 to 20, wherein the first compressed packet header carries second indication information, the second indication information is used to indicate an ethernet frame domain combination mode or a preset bit stream corresponding to a first data stream, the preset bit stream is used to associate the ethernet frame domain combination corresponding to the first data stream, and the first data stream is a set of data packets with the same compression characteristic.

24. The method of claim 23, wherein the second indication information is further used for indicating an ethernet frame header format corresponding to the first data stream.

25. The method of claim 23, wherein after decompressing the compressed header of the first packet, the method further comprises:

determining whether a length field needs to be added in the second data packet according to the second indication information;

if yes, adding the length field at a specific position of the second data packet through an Ethernet frame decompression entity;

wherein the specific location is determined based on the second indication information.

26. The method according to any one of claims 14 to 20, wherein after decompressing the compressed header in the first data packet, the method further comprises:

determining whether a length field needs to be added in the second data packet according to third indication information carried in the first data packet;

if yes, adding the length field at a specific position of the second data packet through an Ethernet frame decompression entity;

wherein the third indication information is used to indicate whether the length field is removed from the first packet before compression.

27. The method according to any one of claims 14 to 20, wherein after decompressing the compressed header in the first data packet, the method further comprises:

determining whether a padding field needs to be added in the second data packet according to a minimum Ethernet frame size agreed by a protocol or according to fourth indication information carried in the first data packet;

if yes, adding a filling domain at the tail part of the second data packet through an Ethernet frame decompression entity;

wherein the fourth indication information is used to indicate whether the padding field is removed from the first packet before compression.

28. A transmitting end, comprising:

a receiving module, configured to receive a first data packet, where the first data packet includes an ethernet header and an IP-series header;

a compressing module, configured to compress at least the ethernet header in the first data packet to obtain a second data packet, where the second data packet at least includes a first compressed packet header;

and the first compressed packet header is a compressed packet header obtained by compressing the Ethernet frame header.

29. A receiving end, comprising:

a receiving module, configured to receive a first data packet, where the first data packet at least includes a first compressed packet header;

a decompression module, configured to decompress the compressed packet header in the first data packet to obtain a second data packet including an ethernet frame header and an IP-series packet header;

the first compressed packet header is obtained by compressing an ethernet header.

30. A transmitting end, comprising: memory, processor and computer program stored on the memory and executable on the processor, which computer program, when executed by the processor, carries out the steps in the data processing method according to any one of claims 1 to 13.

31. A receiving end, comprising: memory, processor and computer program stored on the memory and executable on the processor, which computer program, when executed by the processor, carries out the steps in the data processing method according to any one of claims 14 to 27.

32. A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the steps in the data processing method according to any one of claims 1 to 13; or implementing steps in a data processing method according to any of claims 14 to 27.

Images