CN111385263A

CN111385263A - Method for maintaining data packet header compression information and communication equipment

Info

Publication number: CN111385263A
Application number: CN201811635735.6A
Authority: CN
Inventors: 刘佳敏
Original assignee: China Academy of Telecommunications Technology CATT
Current assignee: Datang Mobile Communications Equipment Co Ltd
Priority date: 2018-12-29
Filing date: 2018-12-29
Publication date: 2020-07-07
Anticipated expiration: 2038-12-29
Also published as: CN111385263B

Abstract

The embodiment of the invention provides a method for maintaining compressed information of a data packet header and communication equipment, wherein the method comprises the following steps: when the decompression end analyzes a data packet received from the compression end, if packet header analysis is abnormal, the decompression end sends analysis abnormal indication information for indicating that the packet header analysis is abnormal to the compression end; and receiving first compression method information sent by the compression end aiming at the analysis abnormity indication information, and analyzing the packet header of a data packet received from the compression end subsequently according to the first compression method information. The embodiment of the invention can be used for solving the problem that the data packet cannot be analyzed due to the fact that the information of the compression method of the decompression end and the compression end are asynchronous.

Description

Method for maintaining data packet header compression information and communication equipment

Technical Field

The present invention relates to the field of communications technologies, and in particular, to a method for maintaining header compression information of a packet and a communications device.

Background

In the prior art, when a data packet is transmitted between two communication devices (e.g., a base station and a terminal), in order to improve the efficiency of data transmission, a transmitting end (i.e., a compressing end) of the data packet compresses a header of the data packet, and a receiving end (i.e., a decompressing end) of the data packet decompresses the received header of the compressed data packet. Therefore, the compression end and the decompression end need to negotiate the compression mode of the data packet header, so that the decompression end can reliably analyze the correct original uncompressed packet header. However, the negotiation process is not always successful, and once the negotiation fails, the compression mode stored by the decompression end may be different from the compression mode used by the compression end, so that the decompression end cannot correctly analyze the original uncompressed packet header, and the data packet cannot be reliably transmitted.

Therefore, a solution that the decompression end cannot analyze the packet header of the data packet sent by the compression end according to the compression method stored by the decompression end is needed.

Disclosure of Invention

The embodiment of the invention provides a method for maintaining compressed information of a data packet header and communication equipment, which are used for solving the problem that data cannot be transmitted correctly and reliably due to failure negotiation of a compression mode about the data packet header between a decompression end and a compression end.

In order to achieve the above object, an embodiment of the present invention provides a method for maintaining header compression information, including:

when the decompression end analyzes a data packet received from the compression end, if packet header analysis is abnormal, the decompression end sends analysis abnormal indication information for indicating that the packet header analysis is abnormal to the compression end;

and the decompression end receives first compression method information which is sent by the compression end aiming at the analysis abnormity indication information, so that the header of a data packet received from the compression end subsequently is analyzed according to the first compression method information.

Optionally, when the decompression end parses a data packet received from the compression end, if packet header parsing is abnormal, the step of sending, to the compression end, parsing abnormal indication information for indicating that packet header parsing is abnormal includes:

when at least one of the following conditions exists, judging that header parsing abnormity occurs:

the data packet carries information indicating that the packet header has been compressed, but information required for correct decompression cannot be obtained from the data packet;

the data packet carries information indicating that the packet header has been compressed and first compression verification information, but second compression verification information obtained according to the decompressed packet header is not matched with the first compression verification information;

the data packet carries information indicating that the packet header is not compressed or information indicating that the packet header is compressed, but information which cannot be analyzed appears in the packet header;

the data packet carries information for indicating that the compression method information is carried, but the packet header cannot be normally analyzed.

Optionally, the information required for decompression includes a compression identifier corresponding to a second compression method information, where the second compression method information is previously sent by the compression end to the decompression end, and when at least one of the following conditions exists, it indicates that the correct information required for decompression cannot be obtained from the data packet:

the value of the compression identifier analyzed from the data packet exceeds the value range of the compression identifier;

and the decompression end does not have effective second compression method information corresponding to the compression identifier analyzed from the data packet.

Optionally, before the step of receiving, by the compression end, the first compression method information sent by the compression end for the analysis exception indication information, the method further includes:

and sending a data packet receiving state report to the compression end, wherein the data packet receiving state report is used for carrying self receiving related information or related information of a data packet with abnormal packet header analysis, the receiving related information is used for indicating the data packet with normal analysis, and the related information of the data packet with abnormal packet header analysis is used for indicating the data packet with abnormal packet header analysis.

Optionally, if the analysis exception indication information is based on the entire data bearer, at least one data flow currently exists on the data bearer, and the data packet with the packet header analysis exception belongs to one data flow of the at least one data flow;

the step of receiving the first compression method information sent by the compression end aiming at the analysis abnormal indication information comprises the following steps:

and receiving different first compression method information sent by the compression end aiming at each data stream currently existing on the data bearer respectively.

Optionally, if the analysis exception indication information is based on the data stream to which the data packet with the header analysis exception belongs,

and receiving first compression method information sent by the compression end aiming at the data stream to which the data packet with abnormal packet header analysis belongs.

Optionally, the analysis exception indication information is carried and can be used to indicate indication information of a data stream to which the data packet with the packet header analysis exception belongs, where the indication information includes at least one of:

the compression identifier is analyzed from the data packet with abnormal packet header analysis, and the compression identifier corresponds to second compression method information which is sent to the decompression end in advance on the compression end;

the target address in the second compression method information corresponding to the compression identifier on the decompression end;

the decompression end is used for decompressing a source address in the second compression method information corresponding to the compression identifier;

and analyzing the SN of the PDCP layer PDU from the data packet with abnormal packet header analysis.

Optionally, after the step of sending, by the decompressing end, analysis exception indication information for indicating that packet header analysis exception occurs to the compressing end, the method further includes:

starting a retransmission timer;

if first compression method information aiming at the analysis abnormity indication information and sent by the compression end is received within a time length set on the retransmission timer, the retransmission timer is stopped; and if not, retransmitting the analysis abnormal indication information.

Optionally, the method further includes:

the decompressing end receives first compression method information sent by the compressing end, and if a compression identifier in the first compression method information is the same as a compression identifier in second compression method information received before, but other information in the first compression method information and the second compression method information is different, only the first compression method information is reserved, and the other information is information except the compression identifier; or the decompressing end receives first compression method information sent by the compressing end, starts a first timer corresponding to the first compression method information, restarts the first timer if the first compression method information is used within a time length set by the first timer, and otherwise does not use the first compression method information.

The embodiment of the invention also provides a method for maintaining the compressed information of the data packet header, which comprises the following steps:

the compression end receives analysis abnormity indication information which is sent by the decompression end and used for indicating that the packet header analysis abnormity occurs;

and the compression end sends first compression method information to the decompression end aiming at the analysis abnormal indication information, so that the decompression end analyzes the packet head of the data packet sent to the decompression end subsequently according to the first compression method information.

Optionally, before the step of sending, by the compression end, the first compression method information to the decompression end according to the analysis exception indication information, the method further includes:

receiving a data packet receiving status report sent by the compression end, wherein the data packet receiving status report is used for carrying receiving related information of the data packet or related information of a data packet with abnormal packet header analysis, the receiving related information is used for indicating the data packet which is analyzed normally, and the related information of the data packet with abnormal packet header analysis is used for indicating the data packet with abnormal packet header analysis;

after the step of sending, by the compression end, the first compression method information to the decompression end for the analysis exception indication information, the method further includes:

and determining the data packet which is not correctly analyzed by the decompressing terminal according to the data packet receiving state report, and retransmitting the data packet which is not correctly analyzed by the decompressing terminal.

Optionally, if the analysis abnormal indication information carries the SN of the PDCP layer PDU,

and retransmitting the data packet corresponding to the SN.

and directly sending the data packet with the required time delay smaller than a preset threshold value in a mode of not compressing the packet head of the data packet.

the step that the compression end sends the first compression method information to the decompression end aiming at the analysis abnormal indication information comprises the following steps:

and respectively sending different first compression method information aiming at each data stream currently existing on the data bearer to the decompression end.

and sending the first compression method information of the data stream to which the data packet with the abnormal packet header analysis belongs to the decompression end.

Optionally, the method further includes:

when a new data stream arrives, allocating a compression identifier for the new data stream, wherein the difference between the last used time of the compression identifier and the current time is greater than the preset time length; sending first compression method information to a decompression end, wherein the first compression method information comprises at least partial information in a data packet header of the new data stream and the compression identifier; alternatively, the first and second electrodes may be,

sending first compression method indication information to a decompression end, starting a second timer corresponding to the first compression method information, restarting the second timer if the compression method information is used within a time length set by the second timer, otherwise, not using the compression method information, wherein the time length set by the second timer is consistent with the time length set by the first timer.

An embodiment of the present invention further provides a communication device, where the communication device is used as a decompression end, and includes:

the analysis exception feedback module is used for sending analysis exception indication information for indicating that the packet header analysis exception occurs to the compression end if the packet header analysis exception occurs when analyzing the data packet received from the compression end;

and the analysis exception handling module is used for receiving first compression method information which is sent by the compression end aiming at the analysis exception indication information, and analyzing a packet header of a data packet received from the compression end subsequently according to the first compression method information.

Optionally, the analysis exception feedback module includes:

the judging unit is used for judging that the packet header analysis is abnormal when at least one of the following conditions exists:

Optionally, the communication device further includes:

and the status report sending module is used for sending a data packet receiving status report to the compression end, the data packet receiving status report is used for carrying relevant receiving information of the data packet or relevant information of a data packet with abnormal packet header analysis, the relevant receiving information is used for indicating the data packet which is analyzed normally, and the relevant information of the data packet with abnormal packet header analysis is used for indicating the data packet with abnormal packet header analysis.

the analysis exception handling module is configured to receive different first compression method information sent by the compression end for each data stream currently existing on the data bearer.

the analysis exception handling module is configured to receive first compression method information sent by the compression end for the data stream to which the data packet with the packet header analysis exception belongs.

Optionally, the analysis exception feedback module is further configured to:

starting a retransmission timer;

Optionally, the method further includes: a maintenance module, configured to receive first compression method information sent by the compression end, and if a compression identifier in the first compression method information is the same as a compression identifier in second compression method information received before, but other information in the first compression method information and the second compression method information is different, only retain the first compression method information, where the other information is information other than the compression identifier; alternatively, the first and second electrodes may be,

receiving first compression method information sent by the compression end, starting a first timer corresponding to the first compression method information, if the first compression method information is used within a time length set by the first timer, restarting the first timer, otherwise, not using the first compression method information.

An embodiment of the present invention further provides a communication device, where the communication device is used as a compression end, and includes:

the analysis exception receiving module is used for receiving analysis exception indication information which is sent by the decompression end and used for indicating that the packet header analysis exception occurs;

and the analysis exception response module is used for sending first compression method information to the decompressing end aiming at the analysis exception indication information so that the decompressing end analyzes the packet header of the data packet sent to the decompressing end subsequently according to the first compression method information.

Optionally, the communication device further includes:

a status report sending module, configured to receive a data packet receiving status report sent by the compression end, where the data packet receiving status report is used to carry relevant receiving information of the data packet or relevant information of a data packet with abnormal packet header analysis, the relevant receiving information is used to indicate a data packet that has been analyzed normally, and the relevant information of the data packet with abnormal packet header analysis is used to indicate a data packet with abnormal packet header analysis;

and the first data packet retransmission module is used for determining the data packet which is not correctly analyzed by the decompression end according to the data packet receiving state report and retransmitting the data packet which is not correctly analyzed by the decompression end.

Optionally, if the analysis abnormal indication information carries the SN of the PDCP layer PDU, the communication device further includes a second data packet retransmission module, configured to retransmit the data packet corresponding to the SN.

Optionally, the communication device further includes:

and the data packet sending module is used for directly sending the data packet with the required time delay smaller than the preset threshold value in a mode of not compressing the packet head of the data packet.

the analysis exception response module is used for respectively sending different first compression method information of each data stream currently existing on the data bearer to the decompression end.

the analysis exception response module is used for sending first compression method information of the data stream to which the data packet with the packet header analysis exception belongs to the decompression end.

Optionally, the communication device further includes:

the management module is used for allocating a compression identifier to a new data stream when the new data stream arrives, wherein the difference between the last used time of the compression identifier and the current time is greater than the preset time length; sending first compression method information to a decompression end, wherein the first compression method information comprises at least partial information in a data packet header of the new data stream and the compression identifier; alternatively, the first and second electrodes may be,

An embodiment of the present invention further provides a communication device, including: a transceiver, a memory, a processor, and a program stored on the memory and executable on the processor, the communication device acting as a decompression peer, the program when executed by the processor implementing the steps of:

when a data packet received from a compression end is analyzed, if packet header analysis is abnormal, sending analysis abnormal indication information for indicating that the packet header analysis is abnormal to the compression end; and receiving first compression method information sent by the compression end aiming at the analysis abnormity indication information, and analyzing the packet header of a data packet received from the compression end subsequently according to the first compression method information.

Optionally, when executed by the processor, the program further implements the following steps:

when analyzing a data packet received from a compression end, if packet header analysis is abnormal, the step of sending analysis abnormal indication information for indicating that the packet header analysis is abnormal to the compression end comprises the following steps:

the decompression end does not have effective compression method information corresponding to the compression identification analyzed from the data packet.

before the step of the decompressing end receiving the first compression method information sent by the compressing end aiming at the analysis abnormal indication information, the decompressing end further includes:

Optionally, if the analysis exception indication information is based on the entire data bearer, at least one data flow currently exists on the data bearer, and the data packet with the packet header analysis exception belongs to one data flow of the at least one data flow; the program when executed by the processor further implements the steps of:

Optionally, if the analysis exception indication information is based on a data stream to which a data packet with a header analysis exception belongs, when the program is executed by the processor, the following steps are further implemented:

after the step of sending, by the decompression end, analysis exception indication information for indicating that packet header analysis exception occurs to the compression end, the method further includes:

starting a retransmission timer;

An embodiment of the present invention further provides a communication device, including: a transceiver, a memory, a processor, and a program stored on the memory and executable on the processor, the communication device acting as a compression side, the program when executed by the processor implementing the steps of:

receiving analysis abnormity indication information which is sent by a decompression end and used for indicating that packet header analysis abnormity occurs; and sending first compression method information to the decompressing end aiming at the analysis abnormal indication information, so that the decompressing end analyzes the packet header of the data packet sent to the decompressing end subsequently according to the first compression method information.

before the step of sending, by the compression end, the first compression method information to the decompression end according to the analysis abnormal indication information, the method further includes:

after the step of sending the first compression method information to the decompression end aiming at the analysis abnormal indication information, the method further comprises the following steps:

Optionally, if the analysis exception indication information carries the SN of the PDCP layer PDU, when the program is executed by the processor, the following steps are further implemented:

and retransmitting the data packet corresponding to the SN.

The embodiment of the present invention further provides a computer-readable storage medium, on which a computer program is stored, where the computer program is executed by a processor to implement the steps in the method for maintaining the data packet header compression information provided in the embodiment of the present invention.

In the embodiment of the invention, when the decompression end analyzes the data packet received from the compression end, if the packet header analysis is abnormal, probably because the compression method information of the decompression end is inconsistent with the compression method information of the compression end, the subsequent data packet can be too large and can not be analyzed correctly, the decompression end sends abnormal feedback to the compression end, and the compression end sends the first compression method information to the decompression end again aiming at the abnormal feedback, so that the synchronization of the compression method information of the decompression end and the compression method information of the compression end is realized, and the correct and reliable transmission of the subsequent data is further ensured.

Drawings

FIG. 1 is a schematic diagram of a network architecture to which embodiments of the present invention are applicable;

fig. 2 is a diagram of a MAC frame structure of the IEEE802.3 standard;

fig. 3 is a flowchart illustrating a method for maintaining compressed information in a packet header according to an embodiment of the present invention;

fig. 4 is a schematic structural diagram of analyzing abnormal indication information according to an embodiment of the present invention;

fig. 5 is a schematic structural diagram of another analysis exception indication information according to an embodiment of the present invention;

fig. 6 is a schematic structural diagram of third analysis exception indication information provided in the embodiment of the present invention;

fig. 7 is a flowchart illustrating a method for maintaining compressed information in a packet header according to a second embodiment of the present invention;

fig. 8 is a structural diagram of a communication device according to a third embodiment of the present invention;

fig. 9 is a structural diagram of a communication device according to a fourth embodiment of the present invention;

fig. 10 is a block diagram of another communication device according to a fifth embodiment of the present invention;

fig. 11 is a block diagram of another communication device according to a sixth embodiment of the present invention.

Detailed Description

In order to make the technical problems, technical solutions and advantages of the present invention more apparent, the following detailed description is given with reference to the accompanying drawings and specific embodiments.

Referring to fig. 1, fig. 1 is a schematic diagram of a network structure to which the embodiment of the present invention is applicable, and as shown in fig. 1, includes a terminal 11 (which may be used as a compression end or a decompression end) and a network side device 12 (which may be used as a compression end or a decompression end), where the terminal 11 may be a User Equipment (UE) or other terminal devices, for example: terminal side equipment such as a Mobile phone, a Tablet Personal Computer (Tablet Personal Computer), a Laptop Computer (Laptop Computer), a Personal Digital Assistant (PDA), a Mobile Internet Device (MID), or a Wearable Device (Wearable Device) is not limited to a specific type of terminal in the embodiments of the present invention. The network side device 12 may be a base station, for example: macro station, LTE eNB, 5G NR NB, etc.; the network side device may also be a small station, such as a Low Power Node (LPN), pico, femto, or an Access Point (AP); the base station may also be a network node that is composed of a Central Unit (CU) and a plurality of Transmission Reception Points (TRPs) whose management is and controls. It should be noted that, in the embodiment of the present invention, the specific type of the network-side device is not limited.

It should be noted that the present invention can be applied to any method of confirming the header compression.

For example, one method for compressing the packet header may be to replace static information (i.e., a static field) in the packet header of a data stream with a compression identifier. Then, the compression method information at least includes static information of a data packet header in a data stream and a compression identifier corresponding to the data stream, and if the data packet header in the data stream includes not only the static information but also dynamic information, the compression method information also includes a relative position of the static information in the data packet header. In addition, since Data streams in a DRB (Data Resource Bearer) are constantly changing, but the number of Data streams existing in a DRB at the same time has an upper limit, the number (i.e., the value range) of all the compression identifiers of a DRB may be a certain number (e.g., 64 Data streams, which have a value range of 0 to 63), and then these compression identifiers are repeatedly used in the DRB, that is, if there is a Data stream ending, the compression identifier of the Data stream ending may be recovered and used for a newly arriving Data stream.

The compression method of the data packet header is particularly suitable for a scene of transmitting a data packet of a Time Sensitive Network (TSN) in a common communication network in the field of industrial internet of things. The data for the TSN may be an ethernet data structure or other type of data structure, and the header (i.e., header) of the ethernet data structure may vary depending on the ethernet protocol used. One of the ethernet data structures, the MAC (Media Access control) frame structure of IEEE802.3 standard, can refer to fig. 2, and the header thereof includes: PREAMBLE of 7 OCTETS, SFD of 1 OCTET (Start of Frame Delimiter), DESTINATION ADDRESS of 6 OCTETS, SOURCE ADDRESS of 6 OCTETS, LENGTH/TYPE of 2 OCTETS, TAG CONTROL INFORMATION of 2 OCTETS, and MAC CLIENT LENGTH/TYPE of 2 OCTETS (MAC client LENGTH/TYPE): protocol 802.1QTag Type (tag Type). Wherein, the first OCTET of the TAG CONTROL INFORMATION includes priority and DEI (discard indication), the second OCTET includes VLAN IDENTIFIER (virtual local area network identifier, VID for short), and the MAC FRAME structure further includes MAC CLIENT DATA (MAC client data field), PAD (padding field), FRAME check sequence and EXTENSION field.

For another example, another Compression method for the data packet header, ROHC (robust header Compression) proposed in RFC3095 protocol, ROHC can be described as the interaction between two state machines — a Compression state machine and a decompression state machine. The compression gain is obtained by establishing Context, i.e. a set of static and dynamic header fields, in the state machines at both ends of the link. The compression end and the decompression end must keep context synchronization during operation, and ROHC adds CRC (cyclic redundancy check) to the compressed packet and can ensure timely and correct updating of the context through feedback (ACK/NACK, acknowledge/non-acknowledge).

The compression end has three states: IR (initialization refresh), FO (first level), SO (second level) states, the state of the compression side characterizing the degree of header compression that can be performed. The decompression side also has three states: NC (no context), SC (static context), FC (complete context), state characterization decompression end is able to decompress the corresponding data packet header, so that the state corresponds to the header compression performance. States can migrate from one state to another.

ROHC supports three modes of operation: u (unidirectional), O (bidirectional optimized), R (bidirectional reliable) modes. The three modes can be switched with each other. Each mode specifies the manner and frequency of some information interaction (e.g., whether more feedback is used, etc.). If the system can be switched to the reliable mode in time, feedback information of states, special domains and the like can be interacted more, the consistency of the contexts of the receiving party and the transmitting party can be ensured as much as possible, and therefore the correct probability of decompression under the high compression ratio state is improved.

The RFC3095 protocol provides for feeding back an ACK if the current packet is an update packet when the CRC at the decompression end succeeds. The compression end and the decompression end initially work in a U mode, the decompression end is switched to an O mode or an R mode after successfully decompressing an update packet, ACK is fed back to the compression end, and the compression end is triggered to be switched to the O mode or the R mode. Later both ends will operate in O or R mode. And if the decompression end continuously monitors that the CRC is successfully checked in the R mode, carrying out state transition of NC- (SC) -FC, feeding back ACK (O), and carrying out conversion of the R-O mode. If the decompression end continuously monitors that the CRC fails in the O mode, the state is degraded, the O- (R) -mode conversion is carried out, and NACK (R) is fed back. And according to the feedback information, the compression end performs corresponding action operation so as to cooperate with the synchronization of the context state.

Referring to fig. 3, fig. 3 is a flowchart of a method for maintaining compressed information in a packet header according to an embodiment of the present invention, as shown in fig. 3, including the following steps:

201. when the decompression end analyzes a data packet received from the compression end, if packet header analysis is abnormal, the decompression end sends analysis abnormal indication information for indicating that the packet header analysis is abnormal to the compression end;

202. and the decompression end receives first compression method information which is sent by the compression end aiming at the analysis abnormity indication information, so that the header of a data packet received from the compression end subsequently is analyzed according to the first compression method information.

The decompression end may be a network side device (e.g., a base station) or a terminal.

Specifically, when the decompression end analyzes a data packet received from the compression end, if packet header analysis is abnormal, the step of sending analysis abnormality indication information for indicating that the packet header analysis is abnormal to the compression end includes:

for example, some compression-related fields have unrecognized values or some anomalies, which results in that the decompression end cannot perform decompression normally. The compression-related field may be, for example, a compression flag, or may be information indicating the relative position of the static header field in the original uncompressed packet header.

the first compression check information is carried by the compression end when sending the data packet to the decompression end, and is used for checking whether the compression method information between the two ends is synchronous or not. The first compression check information is obtained by a compression end according to an original uncompressed packet header of the data packet.

for example, some domains may not be interpretable and errors may exist.

For example, some domains may exhibit some unknown values, or may exhibit unrecognized domains.

It should be noted that, the above-mentioned case for determining that the packet header parsing abnormality occurs is only an example, and there are some other cases that may also be determined that the packet header parsing abnormality occurs, which is not exhaustive here.

In the embodiment of the present invention, once the packet header analysis is abnormal, the decompression end cannot correctly process the data packet and the information carried by the data packet, and determines that the compression method information is not synchronized between the compression end and the decompression end, and the subsequent data packet still cannot be normally analyzed, so that the subsequent data packet needs to be immediately fed back to the compression end.

Further, the information required for decompression includes a compression identifier corresponding to a second compression method information, where the second compression method information is previously sent by the compression end to the decompression end, and when at least one of the following conditions exists, it indicates that the correct information required for decompression cannot be obtained from the data packet:

that is, the value of the compression flag parsed from the packet is an invalid value.

That is, although the value of the compression identifier parsed from the data packet is a valid value, the compression end does not store the compression method information corresponding to the compression identifier or the compression method information is invalid.

Preferably, the decompressing side may further include, before or after the step of receiving the first compression method information sent by the compressing side for the analysis abnormality indication information:

That is, while feeding back the decompression abnormality to the compression end, the decompression end may also trigger a status report to report its reception condition to the compression end, or report only a data packet condition with an abnormal analysis, so as to facilitate the compression end to perform data recovery (for example, may retransmit a data packet with an abnormal analysis).

As an optional implementation manner, the analysis exception indication information is based on an entire data bearer, at least one data flow currently exists on the data bearer, and the data packet with the packet header analysis exception belongs to one data flow of the at least one data flow;

In the embodiment of the invention, the analysis exception reporting is carried out based on the whole bearer, which is the simplest feedback mode. This parsing exception indication may be in the form of a control PDU (control Protocol Data Unit), see fig. 4, where the D/C field indicates that this is a control PDU, and the feedback information that this is a parsing exception is displayed in a PDU type (PDU type) like field.

After receiving the analysis exception indication information, the compression end re-establishes synchronization of the compression method information for all data streams on the bearer, that is, re-sends the compression method information for each data stream.

And analyzing the abnormal indication feedback based on the whole bearer, wherein the effect is to reestablish the synchronization of the compression method information of all data streams on the whole bearer, and all abnormal problems can be solved. However, in some cases, if it can be known exactly which data stream has compression abnormality, it is better to perform only resynchronization of the compression method information of the data stream, and it is not necessary to affect other data streams that can be decompressed normally, so as to improve efficiency. As another optional implementation manner, the parsing exception indication information is based on a data stream to which a data packet with a header parsing exception belongs,

In order to enable the compression end to know exactly which data stream has an analysis exception, the analysis exception indication information sent by the decompression end to the compression end is carried by the analysis exception indication information and can be used to indicate the indication information of the data stream to which the data packet with the packet header analysis exception belongs, and specifically, the indication information may include at least one of the following information:

The most direct way that both the compression end and the decompression end can be used for identifying data streams is to carry a compression identifier in the analysis exception indication information, the compression identifier generally corresponds to the compression method information, one data stream generally corresponds to only one compression method information, and the compression end carries the compression identifier when sending a packet header compressed data packet, so that at the decompression end, as long as the compression identifier in the compressed data packet can be obtained, the compression identifier can be added into the analysis exception indication information. When the parsing exception indication information is transmitted using the control PDU shown in fig. 4, a Compression identification (Compression Index) field may be added in the second byte, as shown in fig. 5.

However, if the decompression end fails to resolve the compression identifier in the data packet sent by the compression end, or the resolved compression identifier is not within the value range, there is no way to use the compression identifier to distinguish which one of the compression identifiers is abnormal. If the PDCP layer is used as an execution layer of compression, because the PDCP layer data PDUs have SNs, the decompression end can know which PDU corresponding to the SN has the decompression abnormity, so that the SN is informed to the compression end, the compression end can know which data packet has the decompression abnormity according to the SN, and therefore, the compression end can know which data flow or which compression method information has a problem, and then corresponding processing is carried out. When the parsing abnormality indication information is transmitted using the control PDU shown in fig. 4, as shown in fig. 6, SN information (12 bits) may be added to the second byte and the third byte, and if the SN information is 18 bits, SN information may be added to the second byte, the third byte, and the fourth byte of the control PDU, and the length of the SN information is configured by the RRC layer.

In addition, since the SN uniquely corresponds to one packet of one data stream, when the indication information includes the SN, the decompression end can know which packet has an analysis abnormality without additionally transmitting a reception status report, and the compression end only needs to retransmit the packet and subsequent packets.

In other embodiments, if the decompression end fails to resolve the compression identifier in the data packet sent by the compression end, and the execution layer of compression is not the PDCP, the compression identifier may also be carried in the analysis exception indication information, and other information capable of identifying the data flow, such as the destination address and the source address. Specifically, the target address and/or the source address in the second compression method information corresponding to the compression identifier on the decompression end may be used, and the compression end may know the old compression method information corresponding to the target address and/or the source address by querying all the compression method information sent to the decompression end before, and then determine the data stream currently using the compression identifier according to the compression identifier in the old compression method information.

starting a retransmission timer;

Generally, after receiving new compression method information, the decompression end reestablishes synchronization of the compression method information with the compression end, and then the decompression operation can be performed normally. If the exception is sent again, the feedback is sent to the compression end again, and generally, repeated reporting or reported retransmission does not need to be carried out for one exception, because if the exception feedback is lost, the exception detection and feedback can be triggered again by subsequent data. However, if the transmission of the fast reply data is required, the decompression end may start a retransmission timer after sending the analysis exception indication information, and if the compression method information for the analysis exception indication information is not received within the time duration set by the retransmission timer, the retransmission timer is over time and then sends the analysis exception indication information to the compression end again, and if the compression method information for the analysis exception indication information is received within the time duration set by the retransmission timer, the retransmission timer is stopped, and the exception handling process is ended.

In other optional embodiments, if the analysis exception indication information carries the SN of the PDCP layer PDU, or the decompression end further sends a reception status report to the compression end, if a data packet with abnormal packet header analysis and retransmitted by the compression end is received within a time period set by the retransmission timer, the retransmission timer is stopped, and if neither the retransmitted data packet with abnormal packet header analysis nor the compression method information for the analysis exception indication information is received, the analysis exception indication information is retransmitted to the compression end.

As another embodiment of the present invention, the method for maintaining the header compression information further includes:

the decompressing end receives first compression method information sent by the compressing end, and if a compression identifier in the first compression method information is the same as a compression identifier in second compression method information received before, but other information in the first compression method information and the second compression method information is different, only the first compression method information is reserved, and the other information is information except the compression identifier.

As packets arrive continuously, the flow of data requiring compression/decompression operations is increasing and in the process of constant change. The compression method information also needs to be updated continuously as the data stream arrives and is released. The establishment of the compression method information is natural along with the arrival of the first data packet, the establishment of the compression method information is firstly carried out, and then the compression data packet is sent, but the release of the compression method information is difficult to judge, because it is difficult to judge which data packet is the last data packet of the data stream unless the whole release or the chain breaking is carried. Therefore, in order to solve the problem of releasing the compression method information, embodiments of the present invention provide a way to overwrite old compression method information (second compression method information) with new compression method information (first compression method information). Specifically, for the decompressing end, after receiving the new compression method information, the decompressing end updates and covers the compression identifier carried in the compression method information, that is, only the latest received compression method information is stored for each compression identifier, and when subsequently receiving the compressed data packet (the packet header is compressed) carrying the compression identifier, the decompressing end decompresses the packet header only according to the latest received compression method information.

As another other embodiment of the present invention, the method for maintaining the header compression information further includes:

and the decompressing end receives first compression method information sent by the compressing end, starts a first timer corresponding to the first compression method information, restarts the first timer if the first compression method information is used within a time length set by the first timer, and otherwise does not use the first compression method information.

In order to solve the problem of releasing the compression method information, an embodiment of the present invention provides a manner for configuring an effective compression method information timer. Specifically, when the header compression of the data packet is started, the network side device (specifically, the base station) configures the duration of the timer, and the usage rule of the timer is as follows: for a piece of compression method information, when the compression method information is not used for compression or decompression operation within the duration of the timer, the compression method information can be released or invalidated after the timer is overtime.

When the compression method information validity timer is used, the start and maintenance are performed for each piece of compression method information, and one of the timers needs to be started and maintained at both the compression end and the decompression end for each piece of compression method information. For the decompressing end, after receiving the data packet related to the compression method information each time (except for some special cases, for example, the data packet carrying the compression method information has some exceptions, specifically, the domain related to compression cannot be identified, the decompression check fails, etc.), the timer (i.e., the first timer) needs to be restarted until the timer is overtime, and the compression method information and the corresponding compression identifier are released or invalidated.

Referring to fig. 7, fig. 7 is a flowchart of another method for maintaining compressed information in a packet header according to a second embodiment of the present invention, as shown in fig. 7, including the following steps:

301. the compression end receives analysis abnormity indication information which is sent by the decompression end and used for indicating that the packet header analysis abnormity occurs;

302. and the compression end sends first compression method information to the decompression end aiming at the analysis abnormal indication information, so that the decompression end analyzes the packet head of the data packet sent to the decompression end subsequently according to the first compression method information.

The compression end may be a network side device (e.g., a base station) or a terminal.

Optionally, before, possibly after, the step of sending, by the compression end, the first compression method information to the decompression end according to the analysis exception indication information, the method further includes:

after or before the step of sending, by the compression end, the first compression method information to the decompression end for the analysis exception indication information, the method further includes:

In one preferred embodiment, the analysis exception indication information carries a Sequence Number (SN) of a Packet Data Convergence Protocol (PDCP) layer PDU,

and retransmitting the data packet corresponding to the SN.

In an optional implementation manner, the analysis exception indication information is based on an entire data bearer, at least one data flow currently exists on the data bearer, and the data packet with the packet header analysis exception belongs to one data flow of the at least one data flow;

After the compression end receives the analysis exception indication information sent by the decompression end, synchronization of the compression method information is reestablished for all data streams on the bearer, that is, the compression method information is resent for each data stream. After synchronization is achieved, transmission of the data packet with the compressed header is resumed.

Because the synchronization of the compression method information is established with the decompression end again, a certain time is needed, and the data packets with high time delay requirements can be directly sent in a way of not compressing the packet header.

In another optional implementation, if the analysis exception indication information is based on the data stream to which the packet header analysis exception occurs,

when a new data stream arrives, a compression end allocates a compression identifier for the new data stream, and the difference between the last used time of the compression identifier and the current time is greater than the preset time length; and sending first compression method information to a decompression end, wherein the first compression method information comprises at least partial information in a data packet header of the new data stream and the compression identifier.

As packets arrive continuously, the flow of data requiring compression/decompression operations is increasing and in the process of constant change. The compression method information also needs to be updated continuously as the data stream arrives and is released. The establishment of the compression method information is natural along with the arrival of the first data packet, the establishment of the compression method information is firstly carried out, and then the compression data packet is sent, but the release of the compression method information is difficult to judge, because it is difficult to judge which data packet is the last data packet of the data stream unless the whole release or the chain breaking is carried. Therefore, in order to solve the problem of releasing the compression method information, embodiments of the present invention provide a way to overwrite old compression method information (second compression method information) with new compression method information (first compression method information). Specifically, for the compression end, if a new data stream arrives, a compression identifier that has been unused for a long time before is used to establish a compression method information (i.e., the first compression method information) for the data stream, and the compression method information is sent to the decompression end to achieve synchronization.

When the compression method information validity timer is used, the start and maintenance are performed for each piece of compression method information, and one of the timers needs to be started and maintained at both the compression end and the decompression end for each piece of compression method information. For the decompression end, the timer (second timer) needs to be restarted each time the compression method information is used for header compression and transmission of the data packet until the timer is overtime, which indicates that the data packet is not used all the time, at this time, the compression method information and the corresponding compression identifier can be released, and the establishment process of the compression method information needs to be carried out again when a new data stream comes later, even when a new data packet arrives in the original data stream. In addition, if the timer is configured to correspond to the compression identifier, the corresponding timer also needs to be restarted each time the compression method information corresponding to the compression identifier is established to be used or the compression method information corresponding to the compression identifier is modified (rebuilt).

It should be noted that, the embodiment is used as an implementation of the compression end corresponding to the embodiment shown in fig. 3, and specific implementation thereof may refer to the relevant description of the embodiment shown in fig. 3, so that, in order to avoid repeated description, the embodiment is not described again, and the same beneficial effects may also be achieved.

Referring to fig. 8, fig. 8 is a structural diagram of a communication device according to a third embodiment of the present invention, and as shown in fig. 8, the communication device 400 is used as a decompression end, and includes:

the analysis exception feedback module 401 is configured to, when analyzing a data packet received from the compression end, send analysis exception indication information used for indicating that packet header analysis exception occurs to the compression end if packet header analysis exception occurs;

an analysis exception handling module 402, configured to receive first compression method information sent by the compression end for the analysis exception indication information, and to analyze a packet header of a subsequent data packet received from the compression end according to the first compression method information.

Optionally, the analysis exception feedback 401 module includes:

Optionally, the communication device 400 further includes:

the analysis exception handling module 402 is configured to receive different first compression method information sent by the compression end for each data stream currently existing on the data bearer.

the analysis exception handling module 402 is configured to receive first compression method information sent by the compression end for the data stream to which the data packet with the packet header analysis exception belongs.

Optionally, the analysis exception feedback module 401 is further configured to:

starting a retransmission timer;

Optionally, the communication device 400 further includes: a maintenance module, configured to receive first compression method information sent by the compression end, and if a compression identifier in the first compression method information is the same as a compression identifier in second compression method information received before, but other information in the first compression method information and the second compression method information is different, only retain the first compression method information, where the other information is information other than the compression identifier; alternatively, the first and second electrodes may be,

It should be noted that, in this embodiment, the communication device 400 may be a communication device in any implementation manner in the method embodiment of the present invention, and any implementation manner of the communication device in the method embodiment of the present invention may be implemented by the communication device 400 in this embodiment, so as to achieve the same beneficial effects, and details are not described here again.

Referring to fig. 9, fig. 9 is a structural diagram of a communication device according to a fourth embodiment of the present invention, and as shown in fig. 9, the communication device 500 is used as a compression end, and includes:

an analysis exception receiving module 501, configured to receive analysis exception indication information sent by the decompression end and used for indicating that packet header analysis exception occurs;

an analysis exception response module 502, configured to send, to the decompressing end, first compression method information according to the analysis exception indication information, so that the decompressing end analyzes a packet header of a data packet that is subsequently sent to the decompressing end according to the first compression method information.

Optionally, the communication device 500 further includes:

the analysis exception response module 502 is configured to send different first compression method information for each data stream currently existing on the data bearer to the decompression end, respectively.

the analysis exception response module 502 is configured to send, to the decompression end, first compression method information of a data stream to which the packet header analysis exception data packet belongs.

Optionally, the communication device 500 further includes:

It should be noted that, in this embodiment, the communication device 500 may be a communication device in any implementation manner in the method embodiment of the present invention, and any implementation manner of the communication device in the method embodiment of the present invention may be implemented by the communication device 500 in this embodiment, so as to achieve the same beneficial effects, and details are not described here again.

Referring to fig. 10, fig. 10 is a structural diagram of another communication device according to a fifth embodiment of the present invention, and as shown in fig. 10, the communication device includes: a transceiver 610, a memory 620, a processor 600 and a program stored on the memory 620 and executable on the processor 600, the communication device acting as a decompression end, wherein the program when executed by the processor 600 implements the steps of:

The transceiver 610 may be used for receiving and transmitting data under the control of the processor 600.

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

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

It should be noted that the memory 620 is not limited to only being on the communication device, and the memory 620 and the processor 600 may be separated in different geographical locations.

Optionally, when executed by the processor 600, the program further implements the following steps:

Optionally, if the analysis exception indication information is based on the entire data bearer, at least one data flow currently exists on the data bearer, and the data packet with the packet header analysis exception belongs to one data flow of the at least one data flow; the program when executed by the processor 600 further realizes the steps of:

Optionally, if the analysis exception indication information is based on a data stream to which a data packet with a header analysis exception belongs, when the program is executed by the processor 600, the following steps are further implemented:

starting a retransmission timer;

It should be noted that, the communication device in this embodiment may be a communication device in any implementation manner in the method embodiment in the embodiment of the present invention, and any implementation manner of the communication device in the method embodiment in the embodiment of the present invention may be implemented by the communication device in this embodiment to achieve the same beneficial effects, and details are not described here.

Referring to fig. 11, fig. 11 is a structural diagram of another communication device according to a sixth embodiment of the present invention, and as shown in fig. 11, the communication device includes: a transceiver 710, a memory 720, a processor 700 and a program stored on the memory 720 and executable on the processor 700, the communication device acting as a compression side, wherein the program when executed by the processor 700 implements the steps of:

The transceiver 710 may be used for receiving and transmitting data under the control of the processor 700.

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

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

It should be noted that the memory 720 is not limited to only being on the communication device, and the memory 720 and the processor 700 may be separated in different geographical locations.

Optionally, when executed by the processor 700, the program further implements the following steps:

Optionally, if the analysis exception indication information carries the SN of the PDCP layer PDU, when the program is executed by the processor 700, the following steps are further implemented:

and retransmitting the data packet corresponding to the SN.

Optionally, if the analysis exception indication information is based on the entire data bearer, at least one data flow currently exists on the data bearer, and the data packet with the packet header analysis exception belongs to one data flow of the at least one data flow; the program when executed by the processor 700 further realizes the steps of:

Optionally, if the analysis exception indication information is based on a data stream to which a data packet with a header analysis exception belongs, when the program is executed by the processor 700, the following steps are further implemented:

The embodiment of the present invention further provides a computer-readable storage medium, on which a computer program is stored, where the computer program is executed by a processor to implement the steps in the method for maintaining the data header compression information of the decompression end provided in the embodiment of the present invention, or the computer program is executed by the processor to implement the steps in the method for maintaining the data header compression information of the compression end provided in the embodiment of the present invention.

In the several embodiments provided in the present application, it should be understood that the disclosed method and apparatus may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may be physically included alone, or two or more units may be integrated into one unit. The integrated unit can be realized in a form of hardware, or in a form of hardware plus a software functional unit.

The integrated unit implemented in the form of a software functional unit may be stored in a computer readable storage medium. The software functional unit is stored in a storage medium and includes several instructions to enable a computer device (which may be a personal computer, a server, or a network device) to execute some steps of the processing method of the information data block according to various embodiments of the present invention. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.

While the foregoing is directed to the preferred embodiment of the present invention, it will be understood by those skilled in the art that various changes and modifications may be made without departing from the spirit and scope of the invention as defined in the appended claims.

Claims

1. A method for maintaining compressed information of a data packet header is characterized by comprising the following steps:

2. The method for maintaining the compressed information in the data packet header according to claim 1, wherein when the decompression end parses the data packet received from the compression end, if the packet header parsing is abnormal, the step of sending, to the compression end, parsing abnormal indication information indicating that the packet header parsing is abnormal includes:

3. The method for maintaining the compression information in the data packet header according to claim 2, wherein the information required for decompression includes a compression identifier corresponding to a second compression method information, the second compression method information is previously sent from the compression end to the decompression end, and when at least one of the following conditions exists, it indicates that the information required for proper decompression cannot be obtained from the data packet:

4. The method for maintaining the packet header compression information according to claim 1, wherein before the step of the decompressing end receiving the first compression method information sent by the compressing end for the parsing abnormality indication information, the method further comprises:

5. The method according to claim 1, wherein if the analysis exception indication information is based on an entire data bearer, at least one data flow currently exists on the data bearer, and the data packet with the analysis exception of the packet header belongs to one of the at least one data flow;

6. The method for maintaining compressed information in a data packet header according to claim 1, wherein if the parsing abnormality indication information is based on a data stream to which a data packet with header parsing abnormality belongs,

7. The method for maintaining the packet header compression information according to claim 6, wherein the analysis exception indication information carries indication information that can be used to indicate a data stream to which the packet header analysis exception packet belongs, and the indication information includes at least one of:

8. The method for maintaining the packet header compression information according to claim 1, wherein after the step of sending, by the decompressing end, the parsing exception indication information for indicating that the packet header parsing exception occurs to the compressing end, the method further comprises:

starting a retransmission timer;

9. The method for maintaining the compression information in the data packet header according to claim 1, further comprising:

the decompressing end receives first compression method information sent by the compressing end, and if a compression identifier in the first compression method information is the same as a compression identifier in second compression method information received before, but other information in the first compression method information and the second compression method information is different, only the first compression method information is reserved, and the other information is information except the compression identifier; alternatively, the first and second electrodes may be,

10. A method for maintaining compressed information of a data packet header is characterized by comprising the following steps:

11. The method for maintaining the compression information in the data packet header according to claim 10,

12. The method for maintaining the compression information in the data packet header according to claim 10,

if the analysis abnormal indication information carries the SN of the PDCP layer PDU,

and retransmitting the data packet corresponding to the SN.

13. The method for maintaining the packet header compression information according to claim 10, wherein before the step of the compressing end sending the first compression method information to the decompressing end according to the parsing abnormality indication information, the method further comprises:

14. The method for maintaining the header compression information of the data packets according to claim 10, wherein if the analysis exception indication information is based on an entire data bearer, at least one data flow currently exists on the data bearer, and the data packet with the header analysis exception belongs to one of the at least one data flow;

15. The method for maintaining packet header compression information as claimed in claim 10, wherein if the parsing abnormality indication information is based on the data stream to which the packet header parsing abnormality occurs,

16. The method for maintaining the compression information in the data packet header as claimed in claim 10, wherein the method further comprises:

17. A communication device, wherein the communication device is used as a decompression side, comprising:

18. The communications device of claim 17, wherein the parsing exception feedback module comprises:

19. The communication device of claim 18, wherein the information required for decompression comprises a compression flag corresponding to a second compression method information, the second compression method information being previously sent by the compression end to the decompression end, and indicating that the correct information required for decompression cannot be obtained from the data packet when at least one of the following conditions exists:

20. The communications device of claim 17, further comprising:

21. The communications device according to claim 17, wherein if the parsing abnormality indication information is based on an entire data bearer, at least one data flow currently exists on the data bearer, and the data packet with the header parsing abnormality belongs to one of the at least one data flow;

22. The apparatus according to claim 17, wherein if the parsing abnormality indication information is based on a data flow to which a packet with a header parsing abnormality occurs,

23. The communication device according to claim 22, wherein the parsing abnormality indication information carries indication information that can be used to indicate a data flow to which the packet header parsing abnormality occurs belongs, and the indication information includes at least one of:

24. The communications device of claim 17, wherein the parsing exception feedback module is further configured to:

starting a retransmission timer;

25. The communications device of claim 17, further comprising: a maintenance module, configured to receive first compression method information sent by the compression end, and if a compression identifier in the first compression method information is the same as a compression identifier in second compression method information received before, but other information in the first compression method information and the second compression method information is different, only retain the first compression method information, where the other information is information other than the compression identifier; alternatively, the first and second electrodes may be,

26. A communication device, wherein the communication device is used as a compression side, comprising:

27. The communications device of claim 26, further comprising:

28. The communication device according to claim 26, wherein if the analysis abnormal indication information carries a SN of a PDCP layer PDU, the communication device further comprises a second packet retransmission module, configured to retransmit a packet corresponding to the SN.

29. The communications device of claim 26, further comprising:

30. The communications device according to claim 26, wherein if the parsing abnormality indication information is based on an entire data bearer, at least one data flow currently exists on the data bearer, and the data packet with the header parsing abnormality belongs to one of the at least one data flow;

31. The communication apparatus according to claim 26, wherein if the parsing abnormality indication information is based on a data flow to which a packet with a header parsing abnormality occurs belongs,

32. The communications device of claim 26, further comprising:

33. A communication device, comprising: a transceiver, a memory, a processor, and a program stored on the memory and executable on the processor, wherein the communication device acts as a decompression peer, and wherein the program when executed by the processor performs the steps of:

34. The communication device of claim 33, wherein the program when executed by the processor further performs the steps of:

35. The communication device of claim 33, wherein the information required for decompression comprises a compression flag corresponding to a second compression method information, the second compression method information being previously sent by the compression end to the decompression end, and indicating that the correct information required for decompression cannot be obtained from the data packet when at least one of the following conditions exists:

36. The communication device of claim 33, wherein the program when executed by the processor further performs the steps of:

37. The communications device according to claim 33, wherein if the parsing abnormality indication information is based on an entire data bearer, at least one data flow currently exists on the data bearer, and the data packet with the header parsing abnormality belongs to one of the at least one data flow; the program when executed by the processor further implements the steps of:

38. The communication device according to claim 33, wherein if the parsing abnormality indication information is based on a data flow to which a packet with a header parsing abnormality occurs, the program when executed by the processor further implements the following steps:

39. The communication device according to claim 38, wherein the parsing abnormality indication information carries indication information that can be used to indicate a data flow to which the packet header parsing abnormality occurs belongs, and the indication information includes at least one of:

40. The communication device of claim 33, wherein the program when executed by the processor further performs the steps of:

starting a retransmission timer;

41. A communication device, comprising: a transceiver, a memory, a processor, and a program stored on the memory and executable on the processor, wherein the communication device acts as a compression side, and wherein the program when executed by the processor performs the steps of:

42. The communication device according to claim 41, wherein the program when executed by the processor further performs the steps of:

43. The communication device of claim 41,

if the analysis abnormal indication information carries the SN of the PDCP layer PDU, the program further realizes the following steps when being executed by the processor:

and retransmitting the data packet corresponding to the SN.

44. The communication device according to claim 41, wherein the program when executed by the processor further performs the steps of:

45. The communications device according to claim 41, wherein if the parsing abnormality indication information is based on an entire data bearer, at least one data flow currently exists on the data bearer, and the data packet with the header parsing abnormality belongs to one of the at least one data flow; the program when executed by the processor further implements the steps of:

46. The communication device according to claim 41, wherein if the parsing abnormality indication information is based on a data flow to which a packet with a header parsing abnormality occurs, the program when executed by the processor further implements the following steps:

47. A computer-readable storage medium, on which a computer program is stored, the program, when being executed by a processor, implementing the steps in the method for maintaining the header compression information according to any one of claims 1 to 16.