CN112218390A

CN112218390A - Data processing method and device

Info

Publication number: CN112218390A
Application number: CN201910621162.XA
Authority: CN
Inventors: 苗金华; 全海洋
Original assignee: Datang Mobile Communications Equipment Co Ltd
Current assignee: Datang Mobile Communications Equipment Co Ltd
Priority date: 2019-07-10
Filing date: 2019-07-10
Publication date: 2021-01-12
Also published as: WO2021004207A1; WO2021004207A9

Abstract

The embodiment of the invention provides a data processing method and equipment, wherein the method comprises the following steps: receiving feedback information sent by a decompression end; retransmitting the compressed data packet or updating the compression context according to the feedback information; wherein the feedback information comprises one or more of: decompressing the SN of the failed compressed packet; decompressing the failed information; and decompressing the information of the successful compressed data packet. In the embodiment of the invention, the compression failure rate can be reduced, and the system performance is improved.

Description

Data processing method and device

Technical Field

The embodiment of the invention relates to the technical field of communication, in particular to a data processing method and data processing equipment.

Background

When decompression fails, neither the current decompression end (alternatively referred to as decompression end) nor the compression end performs any processing on data that cannot be successfully decompressed, which results in loss of data packets.

For example: signaling Radio Bearers (SRBs) data, such as capability information sent by the terminal, or measurement reports. The signaling is characterized by being large, the system efficiency can be improved by using compression, but if decompression fails, data loss can be caused without any processing, and even the situation that the network cannot work can be caused.

Disclosure of Invention

An object of the embodiments of the present invention is to provide a method and an apparatus for data processing, which solve the problem of data packet loss caused by decompression failure.

In a first aspect, a method for data processing is provided, which is applied to a compression end, and includes:

receiving feedback information sent by a decompression end;

retransmitting the compressed data packet or updating the compression context according to the feedback information;

wherein the feedback information comprises one or more of: decompressing the SN of the failed compressed packet; decompressing the failed information; and decompressing the information of the successful compressed data packet.

Optionally, the SN of the compressed data packet that fails to decompress is the SN of the PDCP PDU that fails to compress.

Optionally, the information of the decompression failure includes one or more of the following: RB information corresponding to the decompression failure packet;

data flow information corresponding to the decompression failure data packet;

dictionary information corresponding to the decompression failure packet.

Optionally, the retransmitting the compressed data packet includes any one of:

retransmitting the compression failure data packet indicated by the SN of the compression data packet with the decompression failure;

retransmitting a data packet correspondingly carried by the RB information;

retransmitting the data packet correspondingly carried by the stream information;

and retransmitting the data packet correspondingly carried by the dictionary information.

Optionally, the updating the compression context comprises one or more of:

updating and retransmitting the dictionary;

retransmission of the compression algorithm.

Optionally, what carries the feedback information is RRC signaling, or PDCP control PDU, or header of PDCP.

Optionally, the compression end is located in a PDCP layer.

According to a second aspect, an embodiment of the present invention further provides a data processing method, applied to a decompression end, including:

sending feedback information to a compression end;

Optionally, the information of the decompression failure includes one or more of the following:

RB information corresponding to the decompression failure packet;

data flow information corresponding to the decompression failure data packet;

dictionary information corresponding to the decompression failure packet.

Optionally, the sending feedback information to the compression end includes:

and sending the feedback information to the compression end according to the triggering of the compression end or according to a preset period.

Optionally, the compression end is located in a PDCP layer.

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

the receiving module is used for receiving feedback information sent by the decompression end;

the processing module is used for retransmitting the compressed data packet or updating the compression context according to the feedback information;

In a fourth aspect, an embodiment of the present invention further provides a compression end, including: a first transceiver and a first processor;

the first transceiver is used for receiving feedback information sent by the decompression end;

the first processor is configured to retransmit a compressed data packet or update a compression context according to the feedback information;

In a fifth aspect, an embodiment of the present invention further provides a decompression end, including:

the sending module is used for sending feedback information to the compression end;

In a sixth aspect, an embodiment of the present invention further provides a decompression end, including: a second transceiver and a second processor;

the second transceiver is used for sending feedback information to the compression end;

In a seventh aspect, an embodiment of the present invention further provides a communication device, including: a processor, a memory and a program stored on the memory and executable on the processor, which program, when executed by the processor, carries out the steps of the method of data processing as described above.

In an eighth aspect, the embodiment of the present invention further provides a computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements the steps of the method for data processing described above.

In the embodiment of the invention, the compression failure rate can be reduced, and the system performance is improved.

Drawings

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

FIG. 1 is a block diagram of a wireless communication system;

FIG. 2 is a flow chart of a method of data processing according to an embodiment of the present invention;

FIG. 3 is a second flowchart of a data processing method according to an embodiment of the present invention;

fig. 4 is a schematic diagram illustrating that, after a decompression failure occurs in the UE according to the embodiment of the present invention, the UE sends compression failure indication information to the network side, and the network side performs packet retransmission according to the indication information;

fig. 5 is a schematic diagram illustrating that after a network side fails to decompress, indication compression failure information is sent to a UE, and the UE performs packet retransmission according to the indication information in the embodiment of the present invention;

fig. 6 is a schematic diagram illustrating that, after a decompression failure occurs in the UE according to the embodiment of the present invention, the UE sends information indicating that compression is successful to the network side, and the network side performs packet retransmission according to the information indicating;

fig. 7 is a schematic diagram illustrating that after a network side fails to decompress, an indication successful compression message is sent to a UE, and the UE performs packet retransmission according to the indication message in the embodiment of the present invention;

fig. 8 is a schematic diagram illustrating that, after decompression failure occurs at the UE side, indication compression failure information is sent to the network side, and the network side updates the context of the UE compression algorithm according to the indication information;

fig. 9 is a schematic diagram illustrating that after a network side fails to decompress, the network side executes updating of a context of a UE compression algorithm in an embodiment of the present invention;

FIG. 10 is one of the schematic diagrams of the compression end of the embodiment of the present invention;

FIG. 11 is a second schematic diagram of the compression end according to the embodiment of the present invention;

FIG. 12 is a diagram illustrating an exemplary decompression port according to an embodiment of the present invention;

FIG. 13 is a second schematic diagram of the decompression port according to the embodiment of the present invention;

fig. 14 is a schematic diagram of a communication device according to an embodiment of the present invention.

Detailed Description

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

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

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

In order to facilitate understanding of the embodiments of the present invention, the following technical points will be described below.

First, regarding Upstream Data Compression (UDC):

in the existing data transmission process, when the data volume is large, the transmission resources are in shortage. Particularly, at the cell edge, the UpLink (UL) power of the terminal is limited, and the transmission success rate of large data packets is also affected. Therefore, in order to improve the utilization rate of the system radio resources, the concept of UDC is proposed.

The UDC, i.e. using the existing open source compression algorithm, compresses the UL packet and transmits it. Unlike RObust Header Compression (ROHC), ROHC only performs Compression on the Header of a Packet, and UDC can perform Compression on the entire Packet Data Convergence Protocol (PDCP) Service Data Unit (SDU), so the Compression efficiency is higher especially for large packets.

Currently, UDCs are configured by Radio Resource Control (RRC). The terminal prestores a dictionary, and the network side and the terminal keep the dictionary synchronous. And the terminal executes UDC compression according to the dictionary and sends the compressed data packet to the network side. And the network side decompresses according to the dictionary.

Second, regarding a Radio Link Control (RLC) Acknowledged Mode (AM) Mode:

the RLC AM mode is supported in both Fourth Generation mobile communication system (4G)/fifth Generation mobile communication system (5G). In the RLC AM mode, the transmitting end combines RLC SDUs into an RLC Protocol Data Unit (PDU) by means of segmentation/concatenation, and labels an RLC Sequence Number (SN). The RLC receiving end learns which RLC PDUs are not received according to the SNs and sends a status report to the transmitting end. And after the sending end receives the status report, finishing the retransmission of the RLC PDU which is not received according to the status report.

Therefore, the reliability of data packet transmission, i.e. very low packet loss rate, can be ensured in the RLC AM mode.

Third, regarding RLC Unacknowledged Mode (UM):

RLC UM mode is supported at both 4G/5G. In the RLC UM mode, the sending end combines RLC SDUs into RLC PDUs through segmentation/concatenation and the like, and labels RLC SNs. These are the same as RLC AM. However, in the RLC UM mode, the receiving end does not send the status report, and the transmitting end cannot know which data packets are lost, so that the PDU of the lost RLC cannot be retransmitted. This does not guarantee a lower packet loss rate for data transmission.

However, since no retransmission is involved, the transmission rate of data in RLC UM mode may be greater than in RLC AM mode. The RLC UM mode is selected for some data that is not packet loss rate sensitive but is transmission delay sensitive.

Fourthly, about UDC check failure:

in the prior art, if the UDC decompression end fails to decompress, an error indication is sent to the compression end, so that the compression end resets the dictionary after receiving the error indication. But there is no processing of the data that fails decompression.

Embodiments of the present invention are described below with reference to the accompanying drawings. The HARQ feedback method and the terminal provided by the embodiment of the invention can be applied to a wireless communication system. The wireless communication system may be a fifth-generation mobile communication technology (5G) system, an Evolved Long Term Evolution (lte) system, or a subsequent Evolved communication system.

Referring to fig. 1, an architecture diagram of a wireless communication system according to an embodiment of the present invention is shown. As shown in fig. 1, the wireless communication system may include: network Equipment 10 and a terminal (e.g., User Equipment (UE)), for example, denoted UE11, UE11 may communicate (transmit signaling or transmit data) with network Equipment 10. In practical applications, the connections between the above devices may be wireless connections, and fig. 1 illustrates the connections between the devices by solid lines for convenience and convenience in visual representation.

It should be noted that the communication system may include a plurality of UEs 11, and the network device 10 may communicate with a plurality of UEs 11.

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

The user equipment provided by the embodiment of the invention can be a Mobile phone, a tablet Computer, a notebook Computer, an Ultra-Mobile Personal Computer (UMPC), a netbook or a Personal Digital Assistant (PDA), and the like.

Referring to fig. 2, an embodiment of the present invention provides a data processing method, where an execution subject of the method is a compression end, such as a terminal or a network device. The method comprises the following steps: step 201 and step 202.

Step 201: receiving feedback information sent by a decompression end;

optionally, the feedback information indicates that decompression fails at the decompression end or indicates that decompression succeeds at the decompression end.

It is understood that the compression side transmits the compressed data before step 201.

Step 202: retransmitting the compressed data packet or updating the compression context according to the feedback information;

Wherein, in some embodiments, the feedback information includes one or more of: decompressing SN of compressed data packet failed and information of decompression failure;

in other embodiments, the feedback information includes: and decompressing the information of the successful compressed data packet. If the feedback information indicates that the data packets are not successfully decompressed, the compression end judges which data are not successfully decompressed according to the SN of the successful decompression end, and therefore retransmission is performed on the data packets.

It is understood that the feedback information may also include: and the compression end judges which data are not successfully decompressed according to the SN of the successfully decompressed end, or retransmits the data packets according to the SN of the compressed data packets which are not successfully decompressed.

In some embodiments, the SN of the decompression-failed compressed data packet is a SN of a compression-failed Packet Data Convergence Protocol (PDCP) Protocol Data Unit (PDU).

In some embodiments, the information of the decompression failure comprises one or more of:

(1) radio Bearer (RB) information corresponding to the decompression failure packet;

the RB information is used to indicate which RB the data decompression fails.

For example, the RB information may be SRB information or Data Radio Bearer (DRB) information indicating which Data stream has failed in Data decompression.

(2) Data flow information corresponding to the decompression failure data packet;

for example: the stream information is the ID of the data stream.

(3) Dictionary information corresponding to the decompression failure packet.

For example: the dictionary information is an Identification (ID) of the dictionary.

In some embodiments, the retransmitting the compressed data packet comprises any one of:

(1) retransmitting the compression failure data packet indicated by the SN of the compression data packet with the decompression failure;

for example: the SN may be an SN of a Packet Data Convergence Protocol (PDCP), or an SN of a Radio Link Control (RLC) PDU;

(2) retransmitting data packets correspondingly carried by the RB information;

for example, the RB information may be SRB information or Data Radio Bearer (DRB) information.

(3) Retransmitting data packets correspondingly carried by the data stream information;

for example: the stream information is the ID of the data stream. In a 5G system, one or more Data streams are mapped to a DRB in a Service Data Attachment Protocol (SDAP) layer, for example, a Data stream with a low requirement on a packet loss rate is mapped to the DRB1, and a Data stream with a relaxed requirement on the packet loss rate is mapped to the DRB 2.

(4) And retransmitting the data packet correspondingly carried by the dictionary information.

For example: the dictionary information is the ID of the dictionary.

Optionally, if the feedback information includes: and SN, the compression end retransmits the PDU corresponding to the SN.

Optionally, if the feedback information includes: and carrying information, and the compression end renumbers and transmits the PDCP SDU corresponding to the carrying. The scheme mainly aims at SRB data, and because the SRB data generally appears in the form of one or more PDCP SDUs and does not exist in a large quantity, the PDCP SDUs can be directly sent and retransmitted.

Optionally, if the feedback information includes data flow information, the compression end retransmits the PDCP PDU corresponding to the data flow. This is mainly the case for DRB data.

Alternatively, if the feedback information includes ID information of a dictionary, dictionary data using this ID information may be recompressed based on the ID information of the dictionary and transmitted, which is suitable for a case where compression is just started, i.e., a compression failure occurs.

In some implementations, the updated compression context includes one or more of: and (4) retransmitting the dictionary update and retransmitting the compression algorithm.

In some embodiments, the feedback information is carried by Radio Resource Control (RRC) signaling, or a PDCP Control PDU, or a header of a PDCP.

Referring to fig. 3, an embodiment of the present invention provides a data processing method, where an execution subject of the method is a decompression end, such as a network device or a terminal. Including step 301.

Step 301: sending feedback information to a compression end;

in other embodiments, the feedback information includes: information of successfully decompressed compressed packets, indicating packets that were successfully decompressed.

It is understood that, before step 301, the decompression side receives the compressed data packet from the compression side and performs a decompression process.

Optionally, the feedback information indicates that the decompression end fails to decompress or indicates that the decompression end succeeds in decompressing.

In some embodiments, the SN of the decompression-failed compressed packet is the SN of the compression-failed PDCP PDU.

(3) dictionary information corresponding to the decompression failure packet.

In some embodiments, what carries the feedback information is RRC signaling, or PDCP control PDU, or header of PDCP.

In some embodiments, the sending feedback information to the compression end includes:

Optionally, the triggering according to the compression end is according to receiving a triggering message sent by the compression end.

Optionally, the preset period may be configured by the network side, and the period is not specifically limited.

The first embodiment is as follows: and after the decompression failure occurs to the UE, sending indication compression failure information to the network side, and carrying out data packet retransmission by the network side according to the indication information. Referring to fig. 4, the specific steps are as follows:

step 401: and the network side sends the compressed data packet to the UE.

Step 402: the UE performs the decompression procedure.

When the UE finds that the decompression fails, recording first information, wherein the first information comprises one or more of the following items: protocol Data Unit (PDU) Sequence Number (SN) where a decompression error occurs, Data Radio Bearer (DRB) information where a compression failure occurs, Data stream information where a compression failure occurs, and dictionary information where a compression failure occurs.

For example, the PDU SN may be an SN of a Packet Data Convergence Protocol (PDCP), or an SN of a Radio Link Control (RLC) PDU; the DRB information may be Identification (ID) information of the DRB; the data stream information may be ID information of the data stream; the dictionary information may be an ID of the dictionary, which is not described herein.

Optionally, the UE discards the decompression failed packet.

Step 403: and the UE sends the first information to the network side.

Optionally, carrying the first information may be Radio Resource Control (RRC) signaling, or a PDCP Control PDU, or a header of a PDCP.

Step 404: and after receiving the first information, the network side executes retransmission according to the first information.

Optionally, if the first information comprises: and SN, the network side retransmits the PDU corresponding to the SN.

Optionally, if the first information comprises: and carrying the information, and the network side renumbers and sends the PDCP SDU corresponding to the carrying information. The scheme is mainly directed to Signaling Radio Bearers (SRB) data, and since SRB data generally appears in the form of several PDCP SDUs, there are not many SRB data, so that it is sufficient to directly send and retransmit PDCP SDU numbers.

Optionally, if the first information comprises: and data flow information, wherein the network side retransmits the PDCP PDU corresponding to the data flow information. This is mainly the case for DRB data.

Alternatively, if the dictionary information is the ID of the dictionary, the dictionary data using this ID information may be recompressed according to the ID of the dictionary and transmitted. This case is suitable for data on which compression has just been performed.

Example two: and after the network side fails to decompress, sending indication compression failure information to the UE, and carrying out data packet retransmission by the UE according to the indication information. Referring to fig. 5, the steps are as follows:

step 501: and the UE sends the compressed data packet to the network side.

Step 502: the network side performs the decompression process.

When the network side finds that the decompression fails, first information is recorded, wherein the first information comprises one or more of the following items: PDU SN with errors, DRB information with compression failure, data flow with compression failure and dictionary information with compression failure.

For example, the PDU SN can be a SN of a PDCP, or a SN of an RLC PDU. The DRB information may be ID information of the DRB, the data stream information may be ID information of the data stream, and the dictionary information may be an ID number of the dictionary, which is not described herein again.

Optionally, the network side discards the data packet with decompression failure.

Step 503: and the network side sends the first information to the UE.

Optionally, what carries the first information may be RRC signaling, or PDCP control PDU, or header of PDCP.

Step 504: and after receiving the first information, the UE executes retransmission according to the first information.

Optionally, if the first information comprises: and SN, the UE performs retransmission on the PDU corresponding to the SN.

Optionally, if the first information comprises: and carrying the information, and the UE renumbers and sends the PDCP SDU corresponding to the carrying again. The scheme mainly aims at SRB data, and because the SRB data generally appears in the form of one or more PDCP SDUs and does not exist in a large quantity, the PDCP SDUs can be directly sent and retransmitted.

Optionally, if the first information includes data flow information, the UE retransmits the PDCP PDU corresponding to the data flow. This is mainly the case for DRB data.

Alternatively, if the dictionary information is the ID information of the dictionary, the dictionary data using this ID information may be recompressed and transmitted based on the ID information of the dictionary, which is suitable for a case where compression is just started, i.e., a compression failure occurs.

Example three: after the decompression failure occurs to the UE, sending information indicating the successful compression to the network side, and the network side performing packet retransmission according to the information, referring to fig. 6, the specific steps are as follows:

step 601: and the network side sends the compressed data packet to the UE.

Step 602: the UE performs the decompression procedure.

When the UE performs data packet decompression, recording second information, wherein the second information comprises: successfully decompressed PDU SN, which can be SN of PDCP or SN of RLC PDU.

Step 603: and the UE sends the second information to the network side.

Optionally, the UE selects to send the second information periodically, where the period may be configured by the network side. Or compression-side based triggering. For example, when the network side needs to delete data considered to be successfully received (for example, according to the inter-layer interaction information), the network side sends a trigger message to the decompressing side, and the decompressing side sends the second information according to the trigger message.

Optionally, carrying the second information may be RRC signaling, or PDCP control PDU, or header of PDCP.

Step 604: and after receiving the second information, the network side deletes or retransmits the compressed data according to the second information.

If the second information indicates that the data packets are not successfully decompressed, the compression end judges which data are not successfully decompressed according to the SN of the successful decompression end, and therefore retransmission is performed on the data packets.

Example four: after the network side fails to decompress, it sends the information indicating successful compression to the UE, and the UE performs packet retransmission according to the indication information, see fig. 7, which includes the following specific steps:

step 701: and the UE sends the compressed data packet to the network side.

Step 702: the network side performs the decompression process.

When the network side performs packet decompression, second information is recorded, and the second information may be: successfully decompressed PDU SN, which can be a PDCP SN or a RLC PDU SN.

Step 703: and the network side sends the second information to the UE.

Optionally, the network side selects to send the second information periodically. Or may be a UE-based trigger. For example, when the UE needs to delete data considered to be successfully received (for example, according to the inter-layer interaction information), the UE sends a trigger message to the decompressor, and the decompressor sends the second information according to the trigger message.

Step 704: and after receiving the second information, the UE deletes or retransmits the compressed data according to the second information.

Example five: and after the decompression failure occurs on the UE side, sending indication compression failure information to the network side, and executing context updating of the UE compression algorithm by the network side according to the indication information. Referring to fig. 8, the specific steps are as follows:

step 801: and the network side sends the compressed data packet to the UE.

Step 802: the UE performs the decompression procedure.

When the UE finds that the decompression fails, the UE records third information, where the third information may include one or more of the following: and the dictionary information is used for decompressing SN of the failed data packet.

Step 803: and the UE sends the third information to the network side.

Optionally, what carries the third information may be RRC signaling, or PDCP control PDU, or header of PDCP.

Step 804: and after receiving the third information, the network side executes the updating of the UE compression context according to the third information.

Optionally, the updating of the UE compression context includes: the network side retransmits the compression algorithm; and/or, the network side retransmits the compression dictionary.

Step 805: and the UE updates the compression context according to the UE compression context updated by the network side.

Optionally, if the network side updates the compression algorithm, the UE will update the compression algorithm; if the network side retransmits the dictionary, the UE updates the dictionary;

step 806: the UE performs data decompression according to the updated compression context.

Example six: and after the network side fails to decompress, the network side executes the updating of the context of the UE compression algorithm. Referring to fig. 9, the specific steps are as follows:

step 901: and the UE sends the compressed data packet to the network side.

Step 902: and after receiving the compressed data packet sent by the UE, the network side executes a decompression process.

When finding that the decompression fails, the network side records third information, where the third information may be: dictionary information, and/or SN of the decompressed failed packet.

Step 903: the network side performs the update of the UE compression context.

Optionally, the network side performing UE compression context update includes: the network side retransmits the compression algorithm; and/or network side resending the compression dictionary.

Step 904: and the UE updates the compression context according to the UE compression context updated by the network side.

step 905: the UE performs data compression according to the updated compression context.

The embodiment of the invention also provides a compression end, and as the principle of solving the problem of the compression end is similar to the method for data processing in the embodiment of the invention, the implementation of the compression end can refer to the implementation of the method, and the repeated parts are not described again.

Referring to fig. 10, embodiments of the present invention also provide a compression end, the compression end 1000 including:

a receiving module 1001, configured to receive feedback information sent by a decompression end;

a processing module 1002, configured to retransmit a compressed data packet or update a compression context according to the feedback information;

In some embodiments, the information of the decompression failure comprises one or more of: (1) RB information corresponding to the decompression failure packet;

(3) dictionary information corresponding to the decompression failure packet. In some embodiments, the retransmitting the compressed data packet comprises any one of:

(2) retransmitting a data packet correspondingly carried by the RB information;

(3) retransmitting the data packet correspondingly carried by the stream information;

In some implementations, the updated compression context includes one or more of: updating and retransmitting the dictionary; retransmission of the compression algorithm.

In some embodiments, the compression end is located in the PDCP layer.

The compression end provided by the embodiment of the present invention may implement the above-mentioned embodiments, and the implementation principle and technical effect are similar, which is not described herein again.

Referring to fig. 11, embodiments of the present invention also provide a compression end 1100, which includes: a first transceiver 1101 and a first processor 1102;

the first transceiver 1101 is configured to receive feedback information sent by a decompression end;

the first processor 1102 is configured to retransmit a compressed data packet or update a compression context according to the feedback information;

(2) retransmitting a data packet correspondingly carried by the RB information;

In some embodiments, the compression end is located in the PDCP layer.

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

Referring to fig. 12, an embodiment of the present invention further provides a decompression end, where the decompression end 1200 includes:

a sending module 1201, configured to send feedback information to a compression end;

(1) RB information corresponding to the decompression failure packet;

(3) dictionary information corresponding to the decompression failure packet.

In some embodiments, the sending module 1201 is further configured to: and sending the feedback information to the compression end according to the triggering of the compression end or according to a preset period.

In some embodiments, the compression end is located in the PDCP layer.

The decompression end provided by the embodiment of the present invention can implement the above-mentioned embodiments, and the implementation principle and technical effect are similar, which are not described herein again.

Referring to fig. 13, an embodiment of the present invention further provides a decompression end, where the decompression end 1300 includes: a second transceiver 1301 and a second processor 1302;

the second transceiver 1301 is configured to send feedback information to a compression end, where the feedback information indicates that the decompression end fails to decompress or indicates that the decompression end succeeds in decompressing;

wherein the feedback information comprises one or more of: decompressing the SN of the failed compressed packet; decompressing the failed information; decompressing the information of the successful compressed data packet;

the second processor 1302 is used for performing the decompression processing, but is not limited thereto.

(1) RB information corresponding to the decompression failure packet;

(3) dictionary information corresponding to the decompression failure packet.

In some embodiments, the sending module 1301 is further configured to: and sending the feedback information to the compression end according to the triggering of the compression end or according to a preset period.

In some embodiments, the compression end is located in the PDCP layer.

Referring to fig. 14, fig. 14 is a structural diagram of a communication device applied in the embodiment of the present invention, as shown in fig. 14, the communication device 1400 includes: a processor 1401, a transceiver 1402, a memory 1403, and a bus interface, wherein the processor 1401 may be responsible for managing the bus architecture and general processing. The memory 1403 may store data used by the processor 1401 in performing operations.

In one embodiment of the present invention, the communication device 1400 further comprises: a program stored on the memory 1303 and executable on the processor 1401, which when executed by the processor 1301, performs the steps in the above method.

In fig. 14, the bus architecture may include any number of interconnected buses and bridges, with one or more processors, represented by processor 1401, and various circuits, represented by memory 1403, 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 1402 may be a plurality of elements including a transmitter and a receiver that provide a means for communicating with various other apparatus over a transmission medium.

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

The steps of a method or algorithm described in connection with the disclosure herein may be embodied in hardware or may be embodied in software instructions executed by a processor. The software instructions may be comprised of corresponding software modules that may be stored in Random Access Memory (RAM), flash Memory, Memory (ROM), Erasable programmable Read-Only Memory (EPROM), Electrically Erasable programmable Read-Only Memory (EEPROM), registers, a hard disk, a removable hard disk, a compact disc Read-Only Memory (cd-ROM), or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium. Of course, the storage medium may also be integral to the processor. The processor and the storage medium may reside in an Application Specific Integrated Circuit (ASIC). In addition, the ASIC may be carried in a core network interface device. Of course, the processor and the storage medium may reside as discrete components in a core network interface device.

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

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

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

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

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

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

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

Claims

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

receiving feedback information sent by a decompression end;

wherein the feedback information comprises one or more of: decompressing the sequence number SN of the failed compressed data packet; decompressing the failed information; and decompressing the information of the successful compressed data packet.

2. The method of claim 1, wherein the SN of the decompressed compressed data packet is the SN of a compressed failed Packet Data Convergence Protocol (PDCP) Protocol Data Unit (PDU).

3. The method of claim 1, wherein the information of the decompression failure comprises one or more of: radio bearer RB information corresponding to the decompression failure packet;

data flow information corresponding to the decompression failure data packet;

dictionary information corresponding to the decompression failure packet.

4. The method of claim 3, wherein the retransmitting the compressed data packet comprises any one of:

retransmitting a data packet correspondingly carried by the RB information;

5. The method of claim 1, wherein updating the compression context comprises one or more of:

updating and retransmitting the dictionary;

retransmission of the compression algorithm.

6. The method of claim 1, wherein the feedback information is carried in a Radio Resource Control (RRC) signaling or a packet header of a packet data protocol (PDCP) control Protocol Data Unit (PDU) or a PDCP packet header.

7. The method according to any of claims 1 to 6, wherein the compression end is located in a PDCP layer.

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

sending feedback information to a compression end;

9. The method of claim 8, wherein the SN of the decompressed compressed packet is the SN of the decompressed PDCP PDU.

10. The method of claim 8, wherein the information of the decompression failure comprises one or more of:

RB information corresponding to the decompression failure packet;

data flow information corresponding to the decompression failure data packet;

dictionary information corresponding to the decompression failure packet.

11. The method of claim 8, wherein the feedback information is carried in a Radio Resource Control (RRC) signaling or a packet header of a packet data protocol (PDCP) control Protocol Data Unit (PDU) or a PDCP packet header.

12. The method of claim 8, wherein sending feedback information to the compression end comprises:

13. The method according to any of claims 8 to 12, wherein the compression end is located in a PDCP layer.

14. A compression end, comprising:

15. A compression end, comprising: a first transceiver and a first processor;

16. A decompression terminal, comprising:

17. A decompression terminal, comprising: a second transceiver and a second processor;

18. A communication device, comprising: processor, memory and program stored on the memory and executable on the processor, which when executed by the processor implements the steps of the method of data processing according to any of claims 1 to 13.

19. A computer-readable storage medium, characterized in that a computer program is stored thereon, which computer program, when being executed by a processor, carries out the steps of the method of data processing according to any one of claims 1 to 13.