Data Processing Method and Device

Abstract

In the data processing method and device provided by the embodiments of the present application, when the sending end sends the compressed data packet to the receiving end, it can send the first indication information to the receiving end at the same time, so as to indicate, through the first indication information, the compression cache used by the sending end when compressing the data packet to be compressed. In this way, after receiving the first indication information, the receiving end can determine which compression cache among the compression caches used by the sending end when compressing the data packet to be compressed according to the first indication information, and use the decompression cache corresponding to the compression cache to decompress the compressed data packet, ensuring that the decompression cache used by the receiving end is consistent with the compression cache used by the sending end, thereby improving the success rate of decompression.

Description

Technical Field

[0001] This application relates to the field of communication technologies, and in particular, to a data processing method and apparatus. Background Art

[0002] In a mobile communication network, in order to effectively improve the service transmission rate and resource utilization rate, data packets transmitted over the air interface can be compressed through a data compression mechanism to reduce the actual amount of data transmitted over the air interface. Currently, relatively common data compression methods include uplink data compression (UDC), robust header compression (RoHC), ethernet header compression (EHC), etc.

[0003] Taking the UDC mechanism as an example, the sending end will perform compression processing on the entire obtained data packet, including the packet header and payload parts; both the sending end and the receiving end will maintain a cache. When the sending end sends a data packet, it compresses the data packet based on the compression cache it maintains. Correspondingly, when the receiving end receives the compressed data packet, it will decompress the compressed data packet based on the decompression cache it maintains, so as to restore the data before compression. In a semi-static cache, taking the receiving end instructing the sending end to update the compression cache as an example, if the receiving end has instructed the sending end to update the compression cache, but due to reasons such as data retransmission, the sending end has not received the instruction information in time. Therefore, when compressing the current data packet, the sending end will still continue to compress it using the compression cache before the update. However, since the receiving end has instructed to update the compression cache, the receiving end will use the updated decompression cache to decompress the compressed data packet, which will result in the decompressed data packet being inconsistent with the data packet actually sent by the sending end, thus causing an error in decompression.

[0004] Therefore, in the process of data packet transmission, how to ensure that the decompression cache used by the receiving end is consistent with the compression cache used by the sending end to improve the success rate of decompression is an urgent problem to be solved by those skilled in the art. Summary of the Invention

[0005] Embodiments of this application provide a data processing method and apparatus, which ensure that the decompression cache used by the receiving end is consistent with the compression cache used by the sending end during the data packet transmission process, thereby improving the success rate of decompression.

[0006] In a first aspect, embodiments of this application provide a data processing method, which may include:

[0007] Update the compression cache.

[0008] Compress the data packet to be sent.

[0009] Send the first indication information to the receiving end; the first indication information is used to indicate the compression cache used when compressing the data packet to be sent, the compression cache used is the compression cache before update, or the compression cache used is the compression cache after update.

[0010] Thus, when the sending end sends the compressed data packet to the receiving end, it can send the first indication information to the receiving end together, so as to indicate, through the first indication information, the compression cache used by the sending end when compressing the data packet to be compressed. After receiving the first indication information, the receiving end can determine which compression cache among the compression caches used by the sending end when compressing the data packet to be compressed according to the first indication information, and use the decompression cache corresponding to the compression cache to decompress the compressed data packet, ensuring that the decompression cache used by the receiving end is consistent with the compression cache used by the sending end, thereby improving the success rate of decompression.

[0011] In a possible implementation manner, the first indication information is carried in the compressed data packet, so that the first indication information can be sent to the receiving end together with the compressed data packet. After receiving the first indication information, the receiving end can determine which compression cache among the compression caches used by the sending end when compressing the data packet to be compressed according to the first indication information, and use the decompression cache corresponding to the compression cache to decompress the compressed data packet, ensuring that the decompression cache used by the receiving end is consistent with the compression cache used by the sending end, thereby improving the success rate of decompression.

[0012] In a possible implementation manner, the first indication information is carried in the protocol header of the compressed data packet, or the first indication information is carried in the data header of the compressed data packet. The first indication information is carried in the compressed data packet through the protocol header or the data header of the data packet. In this way, when the sending end sends the compressed data packet, it sends the first indication information together without occupying other network resources additionally.

[0013] In a possible implementation manner, the first indication information is a field in the data packet to be sent.

[0014] If the value of the field is the same as the value of the field in the previous packet adjacent to the packet to be sent received by the receiving end, the compression cache used is the compression cache before the update; if the value of the field is different from the value of the field in the previous packet adjacent to the packet to be sent received by the receiving end, the compression cache used is the compression cache after the update. In this way, after receiving the compressed packet, the receiving end can parse out the value of the field in the packet to be sent, and compare the value of the field of the packet to be sent with the value of the field in the previous packet adjacent to the packet to be sent received by the receiving end, so as to determine the compression cache used by the sending end when compressing the packet to be sent according to the comparison result.

[0015] In a possible implementation, the first indication information is the checksum field in the packet to be sent, and the checksum field is determined according to the compression cache used when compressing the packet to be sent. In this way, after receiving the compressed packet, the receiving end can also parse out the value of the checksum field in the packet to be sent, and compare the value of the checksum field in the packet to be sent with the value of the checksum field calculated according to the compression cache before the update and the value of the checksum field calculated according to the compression cache after the update respectively. If the value of the checksum field in the packet to be sent is the same as the value of the checksum field calculated by the receiving end according to the compression cache before the update, it means that the compression cache used by the sending end when compressing the packet to be sent is the compression cache before the update; if the value of the checksum field in the packet to be sent is the same as the value of the checksum field calculated by the receiving end according to the compression cache after the update, it means that the compression cache used by the sending end when compressing the packet to be sent is the compression cache after the update, so as to determine the compression cache used by the sending end when compressing the packet to be sent according to the comparison result.

[0016] In a possible implementation, the data processing method may further include:

[0017] Receiving a control message from the receiving end; the control message is used to indicate an update to the compression cache; wherein, the control message includes any one of the compression cache after the update, the identifier of the compression cache after the update, and the string information used to indicate an update to the compression cache, so that the sending end determines the compression cache after the update according to the relevant information of the updated cache content in the control message.

[0018] In a possible implementation, the control message further includes second indication information, which is used to indicate the sequence number of the first data packet to be compressed using the updated compression cache, so that the sender can directly determine which compression cache to use for compressing the data packet to be sent according to the second indication information. In this way, the sender only needs to send the compressed data packet to the receiver subsequently, without sending the first indication information to the receiver to indicate the compression cache used by the sender when compressing the data packet to be compressed, which also ensures that the decompression cache used by the receiver is consistent with the compression cache used by the sender, thereby improving the success rate of decompression.

[0019] In a possible implementation, updating the compression cache may include:

[0020] Receiving third indication information from the receiver; the third indication information is used to indicate that the update type of the compression cache is semi-static cache update.

[0021] Updating the compression cache according to the third indication information, that is, realizing that the receiver explicitly configures semi-static cache update for the sender.

[0022] In a possible implementation, updating the compression cache may include:

[0023] Determining that the update type of the compression cache is semi-static cache update according to the unacknowledged mode radio link control (UM RLC) entity associated with the bearer of the data packet to be sent.

[0024] Updating the compression cache according to the UM RLC entity, that is, realizing that the sender can implicitly determine that its cache update type is semi-static cache update.

[0025] In a second aspect, an embodiment of the present application provides a data processing method, which may include:

[0026] Receiving second indication information from the receiver, where the second indication information is used to indicate the sequence number of the first data packet for which the sender uses the updated compression cache for compression.

[0027] Updating the compression cache.

[0028] Compressing the data packet to be sent according to the second indication information; wherein, the compression cache used when compressing the data packet to be sent is the compression cache before update, or the compression cache used when compressing the data packet to be sent is the compression cache after update.

[0029] It can be seen that the sending end first receives the second indication information indicating the sequence number of the first data packet used to instruct the sending end to perform compression using the updated compression cache, and determines the compression cache to be used when compressing the data packet to be compressed according to the second indication information. In this way, after the receiving end receives the compressed data packet, it can determine which compression cache of the compression cache used by the sending end when compressing the data packet to be compressed according to the sequence number of the compressed data packet, and use the decompression cache corresponding to the compression cache to decompress the compressed data packet, ensuring that the decompression cache used by the receiving end is consistent with the compression cache used by the sending end, thereby improving the success rate of decompression.

[0030] In a possible implementation manner, compressing the data packet to be sent according to the second indication information may include:

[0031] If the sequence number of the data packet to be sent is greater than or equal to the sequence number indicated by the second indication information, the updated compression cache is used to compress the data packet to be sent; if the sequence number of the data packet to be sent is less than the sequence number indicated by the second indication information, the compression cache before the update is used to compress the data packet to be sent. In this way, the sending end can determine which compression cache to use for compressing the data packet to be sent according to the sequence number of the data packet to be sent and the sequence number indicated by the second indication information, and also ensures that the decompression cache used by the receiving end is consistent with the compression cache used by the sending end, thereby improving the success rate of decompression.

[0032] In a possible implementation manner, receiving the second indication information from the receiving end may include:

[0033] Receiving a control message from the receiving end; wherein, the control message is used to indicate the update of the compression cache, and the control message includes the second indication information, so that the second indication information is sent to the sending end through the control message, so that the sending end can determine which compression cache to use for compressing the data packet to be sent according to the sequence number of the data packet to be sent and the sequence number indicated by the second indication information, ensuring that the decompression cache used by the receiving end is consistent with the compression cache used by the sending end, thereby improving the success rate of decompression.

[0034] In a possible implementation manner, the control message further includes any one of the updated compression cache, the identifier of the updated compression cache, and the string information used to indicate the update of the compression cache, so that the sending end determines the updated compression cache according to the relevant information of the updated cache content in the control message.

[0035] In a third aspect, an embodiment of the present application further provides a data processing method, and the data processing method may include:

[0036] Updating the compression cache.

[0037] Receive first indication information from a sending end; the first indication information is used to indicate a compression cache adopted by the sending end when compressing a data packet to be sent, and the adopted compression cache is a compression cache before update or a compression cache after update.

[0038] It can be seen that before compressing the data packet to be sent, the receiving end, by receiving the first indication information, can determine which one of the compression caches adopted by the sending end when compressing the data packet to be compressed according to the first indication information, and use the decompression cache corresponding to the compression cache to decompress the compressed data packet, ensuring that the decompression cache adopted by the receiving end is consistent with the compression cache adopted by the sending end, thereby improving the success rate of decompression.

[0039] In a possible implementation manner, the first indication information is carried in the compressed data packet, so that when the receiving end receives the compressed data packet, it can receive the first indication information together, enabling it to determine which one of the compression caches adopted by the sending end when compressing the data packet to be compressed according to the first indication information, and use the decompression cache corresponding to the compression cache to decompress the compressed data packet, ensuring that the decompression cache adopted by the receiving end is consistent with the compression cache adopted by the sending end, thereby improving the success rate of decompression.

[0040] In a possible implementation manner, the first indication information is carried in the protocol header of the compressed data packet, or the first indication information is carried in the data header of the compressed data packet. The first indication information is carried in the compressed data packet through the protocol header or data header of the data packet, so that the receiving end can receive the first indication information together when receiving the compressed data packet without occupying other network resources additionally.

[0041] In a possible implementation manner, the first indication information is a field in the data packet to be sent.

[0042] If the value of the field is the same as the value of the field in the previous data packet adjacent to the data packet to be sent received by the receiving end, the adopted compression cache is the compression cache before update; if the value of the field is different from the value of the field in the previous data packet adjacent to the data packet to be sent received by the receiving end, the adopted compression cache is the compression cache after update. In this way, after receiving the compressed data packet, the receiving end can parse out the value of the field in the data packet to be sent, and compare the value of the field of the data packet to be sent with the value of the field in the previous data packet adjacent to the data packet to be sent received by the receiving end, thereby determining the compression cache adopted by the sending end when compressing the data packet to be sent according to the comparison result.

[0043] In a possible implementation, the first indication information is the checksum field in the data packet to be sent. The checksum field is determined according to the compression cache used when compressing the data packet to be sent. In this way, after receiving the compressed data packet, the receiving end can also parse the value of the checksum field in the data packet to be sent, and compare the value of the checksum field in the data packet to be sent with the value of the checksum field calculated by it according to the compression cache before update and the value of the checksum field calculated by it according to the compression cache after update respectively. If the value of the checksum field in the data packet to be sent is the same as the value of the checksum field calculated by the receiving end according to the compression cache before update, it indicates that the compression cache used by the sending end when compressing the data packet to be sent is the compression cache before update; if the value of the checksum field in the data packet to be sent is the same as the value of the checksum field calculated by the receiving end according to the compression cache after update, it indicates that the compression cache used by the sending end when compressing the data packet to be sent is the compression cache after update, so as to determine the compression cache used by the sending end when compressing the data packet to be sent according to the comparison result.

[0044] In a possible implementation, the data processing method may further include:

[0045] Sending a control message to the sending end; the control message is used to indicate to update the compression cache; wherein, the control message includes any one of the compression cache after update, the identifier of the compression cache after update, and the string information used to indicate the update of the compression cache, so that the sending end can determine the compression cache after update according to the relevant information of the updated cache content in the control message.

[0046] In a possible implementation, the control message further includes second indication information, and the second indication information is used to indicate the sequence number of the first data packet compressed by using the compression cache after update, so that the sending end can directly determine which compression cache to use for compressing the data packet to be sent according to the second indication information. In this way, the sending end only needs to send the compressed data packet to the receiving end subsequently, and there is no need to send the first indication information to the receiving end for indicating the compression cache used by the sending end when compressing the data packet to be compressed, which also ensures that the decompression cache used by the receiving end is consistent with the compression cache used by the sending end, thereby improving the success rate of decompression.

[0047] In a possible implementation, the data processing method may further include:

[0048] Sending third indication information to the sending end; the third indication information is used to indicate that the update type of the compression cache is semi-static cache update and to indicate the sending end to update the compression cache according to the third indication information, that is, the receiving end explicitly configures semi-static cache update for the sending end.

[0049] In a fourth aspect, an embodiment of the present application further provides a data processing method, which may include:

[0050] Update the compression cache.

[0051] Send second indication information to the sending end, where the second indication information is used to indicate the sequence number of the first data packet for which the sending end uses the updated compression cache for compression, and indicate that the sending end compresses the data packets to be sent according to the second indication information; wherein, the compression cache used for compressing the data packets to be sent is the compression cache before the update, or the compression cache used for compressing the data packets to be sent is the updated compression cache.

[0052] It can be seen that the receiving end sends the second indication information to the sending end, which is used to indicate the sequence number of the first data packet for which the sending end uses the updated compression cache for compression, so that the sending end can determine the compression cache to be used for compressing the data packets to be compressed according to the second indication information. In this way, after receiving the compressed data packets, the receiving end can determine which compression cache in the compression cache used by the sending end for compressing the data packets to be compressed according to the sequence number of the compressed data packets, and use the decompression cache corresponding to the compression cache to decompress the compressed data packets, ensuring that the decompression cache used by the receiving end is consistent with the compression cache used by the sending end, thereby improving the success rate of decompression.

[0053] In a possible implementation manner, if the sequence number of the data packet to be sent is greater than or equal to the sequence number indicated by the second indication information, the compression cache used for compressing the data packet to be sent is the updated compression cache; if the sequence number of the data packet to be sent is less than the sequence number indicated by the second indication information, the compression cache used for compressing the data packet to be sent is the compression cache before the update. In this way, the sending end can determine which compression cache to use for compressing the data packet to be sent according to the sequence number of the data packet to be sent and the sequence number indicated by the second indication information, and also ensures that the decompression cache used by the receiving end is consistent with the compression cache used by the sending end, thereby improving the success rate of decompression.

[0054] In a possible implementation manner, sending the second indication information to the sending end may include:

[0055] Send a control message to the sender; wherein, the control message is used to indicate an update to the compression cache, and the control message includes second indication information, so as to send the second indication information to the sender through the control message, enabling the sender to determine which compression cache to use for compressing the packets to be sent based on the sequence number of the packets to be sent and the sequence number indicated by the second indication information, ensuring that the decompression cache used by the receiver is consistent with the compression cache used by the sender, thereby improving the success rate of decompression.

[0056] In a possible implementation manner, the control message further includes any one of the updated compression cache, the identifier of the updated compression cache, and the string information used to indicate an update to the compression cache, so that the sender can determine the updated compression cache according to the relevant information of the updated cache content in the control message.

[0057] In a fifth aspect, an embodiment of the present application further provides a communication device, which may include:

[0058] A processing unit, configured to update the compression cache; and compress the packets to be sent.

[0059] A sending unit, configured to send first indication information to the receiver; the first indication information is used to indicate the compression cache used when compressing the packets to be sent, and the compression cache used is the compression cache before the update, or the compression cache used is the updated compression cache.

[0060] In a possible implementation manner, the first indication information is carried in the compressed packet.

[0061] In a possible implementation manner, the first indication information is carried in the protocol header of the compressed packet, or the first indication information is carried in the data header of the compressed packet.

[0062] In a possible implementation manner, the first indication information is a field in the packet to be sent. If the value of the field is the same as the value of the field in the previous packet adjacent to the packet to be sent received by the receiver, the compression cache used is the compression cache before the update; if the value of the field is different from the value of the field in the previous packet adjacent to the packet to be sent received by the receiver, the compression cache used is the updated compression cache.

[0063] In a possible implementation manner, the first indication information is the checksum field in the packet to be sent, and the checksum field is determined according to the compression cache used when compressing the packet to be sent.

[0064] In a possible implementation manner, the communication device may further include:

[0065] A receiving unit, configured to receive a control message from a receiving end; the control message is used to indicate an update to a compression cache; wherein, the control message includes any one of an updated compression cache, an identifier of the updated compression cache, and string information used to indicate an update to the compression cache.

[0066] In a possible implementation, the control message further includes second indication information, and the second indication information is used to indicate a sequence number of a first data packet compressed using the updated compression cache.

[0067] In a possible implementation, the receiving unit is further configured to receive third indication information from the receiving end; the third indication information is used to indicate that the update type of the compression cache is a semi-static cache update.

[0068] A processing unit, specifically configured to update the compression cache according to the third indication information.

[0069] In a possible implementation, the processing unit is specifically configured to determine that the update type of the compression cache is a semi-static cache update according to an unacknowledged mode radio link control (UM RLC) entity associated with a bearer of a data packet to be sent; and update the compression cache according to the UM RLC entity.

[0070] In a sixth aspect, an embodiment of the present application further provides a communication device, and the communication device may include:

[0071] A receiving unit, configured to receive second indication information from a receiving end, and the second indication information is used to indicate a sequence number of a first data packet compressed by the communication device using an updated compression cache.

[0072] A processing unit, configured to update the compression cache; and compress a data packet to be sent according to the second indication information; wherein, the compression cache used for compressing the data packet to be sent is the compression cache before the update, or the compression cache used for compressing the data packet to be sent is the updated compression cache.

[0073] In a possible implementation, the processing unit is configured to, if the sequence number of the data packet to be sent is greater than or equal to the sequence number indicated by the second indication information, compress the data packet to be sent using the updated compression cache; if the sequence number of the data packet to be sent is less than the sequence number indicated by the second indication information, compress the data packet to be sent using the compression cache before the update.

[0074] In a possible implementation, the receiving unit is configured to receive a control message from a receiving end; wherein, the control message is used to indicate an update to the compression cache, and the control message includes the second indication information.

[0075] In a possible implementation, the control message further includes any one of the updated compression cache, the identifier of the updated compression cache, and the string information used to indicate the update of the compression cache.

[0076] In a seventh aspect, an embodiment of the present application further provides a communication device, which may include:

[0077] A processing unit, configured to update the compression cache.

[0078] A receiving unit, configured to receive first indication information from a sending end; the first indication information is used to indicate the compression cache used by the sending end when compressing the data packet to be sent, the compression cache used is the compression cache before the update, or the compression cache used is the updated compression cache.

[0079] In a possible implementation, the first indication information is carried in the compressed data packet.

[0080] In a possible implementation, the first indication information is carried in the protocol header of the compressed data packet, or the first indication information is carried in the data header of the compressed data packet.

[0081] In a possible implementation, the first indication information is a field in the data packet to be sent. If the value of the field is the same as the value of the field in the previous data packet adjacent to the data packet to be sent received by the communication device, the compression cache used is the compression cache before the update; if the value of the field is different from the value of the field in the previous data packet adjacent to the data packet to be sent received by the communication device, the compression cache used is the updated compression cache.

[0082] In a possible implementation, the first indication information is the checksum field in the data packet to be sent, and the checksum field is determined according to the compression cache used when compressing the data packet to be sent.

[0083] In a possible implementation, the communication device may further include:

[0084] A sending unit, configured to send a control message to the sending end; the control message is used to indicate the update of the compression cache; wherein, the control message includes any one of the updated compression cache, the identifier of the updated compression cache, and the string information used to indicate the update of the compression cache.

[0085] In a possible implementation, the control message further includes second indication information, and the second indication information is used to indicate the sequence number of the first data packet compressed using the updated compression cache.

[0086] In a possible implementation, the sending unit is further configured to send third indication information to the sending end; the third indication information is used to indicate that the update type of the compression cache is semi-static cache update, and to indicate that the sending end updates the compression cache according to the third indication information.

[0087] In a eighth aspect, an embodiment of the present application further provides a communication device, which may include:

[0088] A processing unit, configured to update the compression cache.

[0089] A sending unit, configured to send second indication information to the sending end, where the second indication information is used to indicate the sequence number of the first data packet to be compressed by the sending end using the updated compression cache, and to indicate that the sending end compresses the data packets to be sent according to the second indication information; wherein, when compressing the data packets to be sent, the compression cache used is the compression cache before update, or the compression cache used when compressing the data packets to be sent is the updated compression cache.

[0090] In a possible implementation, if the sequence number of the data packet to be sent is greater than or equal to the sequence number indicated by the second indication information, the compression cache used when compressing the data packet to be sent is the updated compression cache; if the sequence number of the data packet to be sent is less than the sequence number indicated by the second indication information, the compression cache used when compressing the data packet to be sent is the compression cache before update.

[0091] In a possible implementation, the sending unit is specifically configured to send a control message to the sending end; wherein, the control message is used to indicate an update of the compression cache, and the control message includes the second indication information.

[0092] In a possible implementation, the control message further includes any one of the updated compression cache, the identifier of the updated compression cache, and the string information used to indicate an update of the compression cache.

[0093] It can be understood that the communication device shown in the above fifth aspect to the eighth aspect may be the communication device itself, or a component (such as a chip, a circuit, a module or a unit) configurable in the communication device.

[0094] In a ninth aspect, an embodiment of the present application further provides a communication device, the device includes a processor and a memory, a computer program is stored in the memory, and the processor executes the computer program stored in the memory, so that the device executes the data processing method described in any possible implementation of the first aspect; or, the processor executes the computer program stored in the memory, so that the device executes the data processing method described in any possible implementation of the second aspect.

[0095] In a tenth aspect, an embodiment of the present application further provides a communication device, which includes a processor and a memory. A computer program is stored in the memory, and the processor executes the computer program stored in the memory to enable the device to execute the data processing method described in any possible implementation manner of the third aspect; or, the processor executes the computer program stored in the memory to enable the device to execute the data processing method described in any possible implementation manner of the fourth aspect.

[0096] In an eleventh aspect, an embodiment of the present application further provides a communication device, which includes a processor and an interface circuit.

[0097] The interface circuit is configured to receive code instructions and transmit them to the processor;

[0098] The processor is configured to run the code instructions to execute the data processing method described in any possible implementation manner of the first aspect; or, to run the code instructions to execute the data processing method described in any possible implementation manner of the second aspect.

[0099] In a twelfth aspect, an embodiment of the present application further provides a communication device, which may include a processor and an interface circuit.

[0100] The interface circuit is configured to receive code instructions and transmit them to the processor.

[0101] The processor is configured to run the code instructions to execute the data processing method described in any possible implementation manner of the third aspect; or, to run the code instructions to execute the data processing method described in any possible implementation manner of the fourth aspect.

[0102] In a thirteenth aspect, an embodiment of the present application further provides a readable storage medium, which is used to store instructions. When the instructions are executed, the data processing method described in any possible implementation manner of the first aspect is implemented; or, when the instructions are executed, the data processing method described in any possible implementation manner of the second aspect is implemented.

[0103] In a fourteenth aspect, an embodiment of the present application further provides a readable storage medium, which is used to store instructions. When the instructions are executed, the data processing method described in any possible implementation manner of the third aspect is implemented; or, when the instructions are executed, the data processing method described in any possible implementation manner of the fourth aspect is implemented.

[0104] In a fifteenth aspect, an embodiment of the present application further provides a chip, on which a computer program is stored. When the computer program is executed by a processor, it executes the data processing method described in any possible implementation manner of the first aspect; or, when the computer program is executed by a processor, it executes the data processing method described in any possible implementation manner of the second aspect.

[0105] In a sixteenth aspect, an embodiment of the present application further provides a chip, on which a computer program is stored. When the computer program is executed by a processor, it executes the data processing method described in any possible implementation manner of the third aspect; or, when the computer program is executed by a processor, it executes the data processing method described in any possible implementation manner of the fourth aspect.

[0106] In a seventeenth aspect, an embodiment of the present application further provides a communication system, which may include: the communication device described in the fifth aspect above and the communication device described in the sixth aspect above; or, the communication device described in the seventh aspect above and the communication device described in the eighth aspect above; or, the communication device described in the ninth aspect above and the communication device described in the tenth aspect above; or, the communication device described in the eleventh aspect above and the communication device described in the twelfth aspect above.

[0107] For the data processing method and device provided by the embodiment of the present application, when the sending end sends the compressed data packet to the receiving end, it may send the first indication information to the receiving end together, so as to indicate the compression cache adopted by the sending end when compressing the data packet to be compressed through the first indication information. In this way, after receiving the first indication information, the receiving end may determine which compression cache among the compression caches adopted by the sending end when compressing the data packet to be compressed according to the first indication information, and use the decompression cache corresponding to the compression cache to decompress the compressed data packet, ensuring that the decompression cache adopted by the receiving end is consistent with the compression cache adopted by the sending end, thereby improving the success rate of decompression. BRIEF DESCRIPTION OF THE DRAWINGS

[0108] Figure 1 It is a schematic diagram of an application scenario provided by an embodiment of the present application;

[0109] Figure 2 It is another schematic diagram of an application scenario provided by an embodiment of the present application;

[0110] Figure 3 It is a schematic flowchart of a data processing method provided by an embodiment of the present application;

[0111] Figure 4 It is a schematic structural diagram of a PDCP header carrying a field U provided by an embodiment of the present application;

[0112] Figure 5 Schematic diagram of a UDC header carrying field U provided by an embodiment of the present application;

[0113] Figure 6 Schematic diagram of a data packet processing procedure provided by an embodiment of the present application;

[0114] Figure 7 Schematic diagram of a PDCP header carrying field I provided by an embodiment of the present application;

[0115] Figure 8 Schematic diagram of a UDC header carrying field I provided by an embodiment of the present application;

[0116] Figure 9 Schematic diagram of another data packet processing procedure provided by an embodiment of the present application;

[0117] Figure 10 Schematic diagram of a PDCP header carrying field Indication provided by an embodiment of the present application;

[0118] Figure 11 Schematic diagram of a UDC header carrying field Indication provided by an embodiment of the present application;

[0119] Figure 12 Schematic diagram of a flowchart of another data processing method provided by an embodiment of the present application;

[0120] Figure 13 Schematic diagram of a flowchart of yet another data processing method provided by an embodiment of the present application;

[0121] Figure 14 Schematic diagram of a communication device provided by an embodiment of the present application;

[0122] Figure 15 Schematic diagram of another communication device provided by an embodiment of the present application;

[0123] Figure 16 Schematic diagram of a communication device provided by an embodiment of the present application;

[0124] Figure 17 Schematic diagram of another communication device provided by an embodiment of the present application;

[0125] Figure 18 Schematic diagram of a communication device provided by an embodiment of the present application;

[0126] Figure 19 Schematic diagram of another communication device provided by an embodiment of the present application. Detailed implementation manners

[0127] The embodiments of this application are applied to the fifth-generation (5G) communication system or other systems that may emerge in the future. It should be noted that when the solutions of the embodiments of this application are applied to the 5G system or other systems that may emerge in the future, the names of the receiving end and the terminal may change, but this does not affect the implementation of the solutions of the embodiments of this application.

[0128] In the embodiments of this application, "at least one" means one or more, and "a plurality" means two or more. "And / or" describes the association relationship of associated objects and indicates that three relationships may exist. For example, A and / or B may represent three situations: A exists alone, A and B exist simultaneously, and B exists alone, where A and B may be singular or plural. In the text description of this application, the character " / " generally represents an "or" relationship between the associated objects before and after.

[0129] The data processing method provided by the embodiments of this application can be applied to a communication system that uses the Uu interface for data transmission. For example, please refer to Figure 1 as shown in Figure 1 which is a schematic diagram of an application scenario provided by the embodiments of this application. The Figure 1 application scenario shown may include at least one terminal and one network device. Among them, one of the terminal and the network device is the sending end, and the other is the receiving end. The Uu interface is used for data transmission between the terminal and the network device. However, the data processing method provided by the embodiments of this application is not limited to being applied to a communication system that uses the Uu interface for data transmission, and can also be applied to a communication system that uses the sidelink interface for data transmission. For example, please refer to Figure 2 as shown in Figure 2 which is another schematic diagram of an application scenario provided by the embodiments of this application. The Figure 2 application scenario shown may include at least two terminals. Among them, one of the two terminals is the sending end, and the other is the receiving end. The sidelink interface is used for data transmission between the two terminals.

[0130] Among them, a terminal device, also known as a user equipment (UE), a mobile station (MS), a mobile terminal (MT), etc., is a device that provides voice / data connectivity to users. For example, it can be a handheld device with a wireless connection function, a vehicle-mounted device, etc. Currently, some examples of terminal devices are: mobile phones, tablet computers, laptop computers, palmtop computers, mobile internet devices (MIDs), wearable devices, virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical surgery, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, etc. In the embodiments of this application, the method executed by the terminal device can be specifically executed by at least one chip in the terminal device.

[0131] A network device is an entity in the network side for transmitting or receiving signals, such as a new generation base station (generation Node B, gNodeB). The network device can be a device for communicating with a terminal device. The network device can be an evolved Node B (eNB or eNodeB) in Long Term Evolution (LTE), or a relay station or access point, or a vehicle-mounted device, a wearable device, and a network device in the future 5G network or a network device in a future evolved public land mobile network (PLMN), or a gNodeB in an NR system, etc. Additionally, in the embodiments of this application, the network device provides services for a cell, and the terminal device communicates with the network device through the transmission resources used by the cell (for example, frequency domain resources, or in other words, spectrum resources). The cell can be the cell corresponding to the network device (such as a base station). The cell can belong to a macro base station or a base station corresponding to a small cell. Here, the small cell can include: metro cell, microcell, pico cell, femto cell, etc. These small cells have the characteristics of small coverage range and low transmission power, and are suitable for providing high-rate data transmission services. In addition, in other possible cases, the network device can be other devices that provide wireless communication functions for the terminal device. The embodiments of this application do not limit the specific technologies and specific device forms adopted by the network device. For the convenience of description, in the embodiments of this application, the device that provides wireless communication functions for the terminal device is called a network device. The methods executed by the network device in the embodiments of this application can be specifically executed by at least one chip in the network device.

[0132] In the above Figure 1 or Figure 2 In the application scenario shown, when the sending end sends a data packet to the receiving end, in order to reduce the amount of data actually transmitted over the air interface, the sending end can adopt the UDC mechanism to compress the data packet to be sent. Under the semi-static cache update mechanism, taking the receiving end instructing the sending end to update the compression cache as an example, if the receiving end has already instructed the sending end to update the compression cache, but due to reasons such as data retransmission, the sending end has not received this instruction information in time. Therefore, it will still continue to compress using the compression cache before the update. However, since the receiving end has already instructed to update the compression cache, the receiving end will use the updated decompression cache to decompress the compressed data packet, which will result in the decompressed data packet being inconsistent with the data packet actually sent by the sending end, thus causing an error in decompression.

[0133] To solve the problem that in the UDC compression mechanism, when the receiving end instructs the sending end to update the compression cache, but due to reasons such as data retransmission, the sending end does not receive this instruction information and still continues to compress with the compression cache before the update, resulting in an error in decompression because the decompression cache adopted by the receiving end is inconsistent with the compression cache adopted by the sending end, the embodiments of the present application propose the following at least two possible implementation manners, so that the decompression cache adopted by the receiving end is consistent with the compression cache adopted by the sending end, thereby improving the success rate of decompression.

[0134] In a possible implementation manner, in the UDC compression mechanism, the sending end actively controls which compression cache (the compression cache before the update or the compression cache after the update) is used to compress the data to be sent, and notifies the receiving end of the compression cache it uses. The implementation process can be as follows: when the sending end sends the compressed data packet to the receiving end, it can send the first indication information to the receiving end at the same time, so as to indicate through the first indication information which compression cache the sending end uses when compressing the data packet to be compressed. In this way, after receiving the first indication information, the receiving end can determine which compression cache among the compression caches the sending end uses when compressing the data packet to be compressed according to the first indication information, and use the decompression cache corresponding to the compression cache to decompress the compressed data packet, ensuring that the decompression cache adopted by the receiving end is consistent with the compression cache adopted by the sending end, thereby improving the success rate of decompression.

[0135] In another possible implementation, different from the previous possible implementation, in the UDC compression mechanism, it is no longer the sending end that actively controls which compression cache (the compression cache before update or the compression cache after update) to use to compress the data to be sent. Instead, it is the receiving end that controls the sending end to use a certain compression cache to compress the data to be sent. The implementation process can be as follows: The receiving end sends second indication information to the sending end to indicate, through this second indication information, the sequence number of the first data packet to be compressed using the compression cache after update. After receiving this second indication information, the sending end can determine which compression cache to use to compress the data to be sent according to the sequence number indicated by this second indication information. If the sequence number of the current data packet to be sent is less than the sequence number indicated by the second indication information, the sending end uses the compression cache before update to compress the data packet to be sent. If the sequence number of the current data packet to be sent is greater than or equal to the sequence number indicated by the second indication information, the sending end uses the compression cache after update to compress the data packet to be sent and sends the compressed data packet to the receiving end. Since the receiving end has negotiated with the sending end through the second indication information, after receiving the compressed data packet, the receiving end can determine the corresponding decompression cache according to the sequence number of the compressed data packet and use this decompression cache to decompress the compressed data packet, which also ensures that the decompression cache used by the receiving end is consistent with the compression cache used by the sending end, thereby improving the success rate of decompression.

[0136] It can be understood that in the embodiments of the present application, in the UDC compression mechanism, when the sending end uses a compression cache to compress the data packets to be sent, the compression cache can be regarded as the basis for compressing the data packets to be sent. Its basic principle is: if there is a segment of string in the data packet to be sent that is the same as a segment of string in the compression cache, then the position information and length information of the string in the compression cache are used to replace the string in the data packet to be sent. For example, if there is a segment of string 'ABCD' in the data packet to be sent, and there is also a string 'ABCD' in the compression cache, and the starting position of this string saved in the compression cache is the 200th byte and the length is 4 bytes, then the sending end can use the position information and length information <200, 4> to replace the string 'ABCD' in the data packet to be sent, so as to achieve the compression of the string 'ABCD' in the data packet to be sent. Correspondingly, when the receiving end uses a decompression cache to decompress the compressed data packet, its basic principle is: using the position information and length information of the string indicated in the compressed data packet, the corresponding string is retrieved from the decompression cache to reconstruct the original data packet. For example, according to the position information and length information <200, 4> carried in the compressed data packet, look for 4 consecutive bytes starting from the 200th byte in the decompression cache. If the decompression cache is the same as the compression cache, then the 4 consecutive bytes starting from the 200th byte in the decompression cache will also be the string 'ABCD'. After determining the string 'ABCD', and replacing the position information and length information with the string 'ABCD', the data packet to be sent can be restored.

[0137] It can be understood that in the embodiments of the present application, the compression cache before update and the compression cache after update occupy the same size of cache space. The reason for being described as the compression cache before update and the compression cache after update is that: the content saved in the cache space has changed before and after the update. Therefore, in order to facilitate the distinction between the content of the compression cache before update and the content of the compression cache after update, the compression cache before the update of the compression cache content is described as the compression cache before update, and the compression cache after the update of the compression cache content is described as the compression cache after update.

[0138] It should be noted that when the data processing method provided in the embodiments of the present application is applied to the UDC mechanism, the compression content used by the sending end for compressing the data packets to be sent is the content in the compression cache, that is, the sending end can use the compression cache to compress the data packets to be sent.

[0139] The data processing method provided by the embodiments of this application can be applied to the RoHC mechanism. When compressing IP data packets, the compression cache is also called the RoHC context. That is, the sending end can use the RoHC compression context to compress the data packets to be sent, and the receiving end can use the RoHC decompression context corresponding to the RoHC compression context to decompress the received data packets and restore the original data packets. Under the RoHC mechanism, in order to ensure that the RoHC decompression context used by the receiving end is consistent with the RoHC compression context used by the sending end to improve the decompression success rate, it can also be implemented through two possible implementation methods. In one possible implementation method, the sending end actively controls which RoHC compression context (the RoHC compression context before update or the RoHC compression context after update) to use to compress the data to be sent and notifies the receiving end of the RoHC compression context it uses. In another possible implementation method, it is no longer the sending end that actively controls which RoHC compression context (the RoHC compression context before update or the RoHC compression context after update) to use to compress the data to be sent, but the receiving end controls which RoHC compression context the sending end uses to compress the data to be sent.

[0140] The data processing method provided by the embodiments of this application can also be applied to the EHC mechanism. When compressing Ethernet data packets, the compression cache is also called the EHC context. That is, the sending end can use the EHC compression context to compress the data packets to be sent, and the receiving end can use the EHC decompression context corresponding to the EHC context to decompress the received data packets and restore the original data packets. Under the RoHC mechanism and the EHC mechanism, the semi-static compression update operation can also be implemented by using the solution in this application. Under the EHC mechanism, in order to ensure that the EHC decompression context used by the receiving end is consistent with the EHC context used by the sending end to improve the decompression success rate, it can also be implemented through two possible implementation methods. In one possible implementation method, the sending end actively controls which EHC context (the EHC context before update or the EHC context after update) to use to compress the data to be sent and notifies the receiving end of the EHC context it uses. In another possible implementation method, it is no longer the sending end that actively controls which EHC context (the EHC context before update or the EHC context after update) to use to compress the data to be sent, but the receiving end controls which EHC context the sending end uses to compress the data to be sent. It can be understood that the two possible implementation methods under these two mechanisms are respectively similar to the two possible implementation methods in the above UDC mechanism. In the subsequent description, the data processing method under the UDC mechanism will be described in detail.

[0141] To facilitate the understanding of the data processing method provided by the embodiments of the present application, hereinafter, the embodiments of the present application will separately describe the data processing method provided by the embodiments of the present application in detail in combination with the above two possible implementation manners. It should be noted that, hereinafter, when describing these two possible implementation manners, the scenario shown in Figure 1 will be used as an example, where the sending end is a terminal and the receiving end is a receiving end. Of course, in the scenario shown in Figure 1 , the sending end can also be a receiving end, and the receiving end can also be a terminal, which can be specifically set according to actual needs.

[0142] In a possible implementation manner, the sending end (terminal) actively controls which compression cache (the compression cache before update or the compression cache after update) is used to compress the data to be sent, and notifies the receiving end (receiving end) of the compression cache it uses. For example, please refer to Figure 3 shown in Figure 3 , which is a schematic flowchart of a data processing method provided by the embodiments of the present application. The data processing method may include:

[0143] S301. The network device configures semi-static cache update for the terminal.

[0144] Among them, semi-static cache update can be understood as that the compression cache maintained by the terminal and the decompression cache maintained by the network device are changeable, but compared with dynamic cache update, the change frequency of the cache content is lower.

[0145] It is not difficult to understand that before the network device configures semi-static cache update for the terminal, it needs to first obtain the capability information of the terminal. The capability information may include whether it supports semi-static compression cache update, and / or whether it supports the network device to control semi-static compression cache update. For example, when the network device obtains the capability information of the terminal, it can obtain the capability information actively reported by the terminal, or the network device can obtain the capability information of the terminal from an adjacent network device. In this case, the terminal does not need to report its capability information. If the terminal only supports the uplink data transmission compression mechanism based on the compression cache, that is, the terminal only supports the UDC capability, the capability information of the terminal includes the capability information that the terminal supports the UDC capability; if the terminal supports both the UDC and the downlink data transmission compression mechanism based on the compression cache (indicating that the UDC mechanism is applied to the compression of downlink data transmission) these two data compression capabilities, the capability information of the terminal includes the capability information that the terminal supports these two data compression capabilities, and the capability information of these two data compression capabilities can be reported separately; they can also be reported together. Of course, only one capability information can also be reported, and this capability information indicates that the terminal supports these two data compression capabilities of the UDC and the downlink data transmission compression mechanism based on the compression cache, which can be specifically set according to actual needs. Here, the embodiments of the present application do not make specific limitations.

[0146] After the network device obtains the capability information of the terminal, it can configure semi-static cache update for the terminal based on the capability information of the terminal. For example, when configuring semi-static cache update for the terminal, the semi-static update can be configured for the terminal in at least two possible ways. In one possible way, the network device can explicitly configure semi-static cache update for the terminal. In another possible way, the terminal can implicitly determine that its cache update type is semi-static cache update.

[0147] In the first possible way, when the network device can explicitly configure semi-static cache update for the terminal, the network device can send the third indication information to the terminal, and the third indication information is used to indicate that the update type of the compressed cache is semi-static cache update. For example, the network device can send the third indication information to the terminal through at least two possible ways as follows.

[0148] Method 1: The network device sends radio resource control (RRC) configuration signaling to the terminal. If the RRC configuration signaling carries a semi-static buffer update (semistaticBufferUpdate) parameter, it means that the bearer used by the network device for the packet to be sent is configured with semi-static cache update. On the contrary, if the RRC configuration signaling does not carry the semistaticBufferUpdate parameter, it means that the bearer used by the network device for the packet to be sent is not configured with semi-static cache update. In this Method 1, the semistaticBufferUpdate parameter can be understood as the third indication information.

[0149] In Method 2, the network device sends RRC configuration signaling to the terminal. Even if the RRC configuration signaling carries the semistaticBufferUpdate parameter, it does not mean that the bearer configured by the network device for the packet to be sent uses semi-static buffer update. Instead, it is necessary to further configure the bearer for the packet to be sent based on the value of the semistaticBufferUpdate parameter. For example, semistaticBufferUpdate = {true} indicates that the bearer configured for the packet to be sent uses semi-static buffer update, and semistaticBufferUpdate = {false} indicates that the bearer configured for the packet to be sent does not use semi-static buffer update, but other types of buffer updates, such as dynamic buffer update or static buffer update; or, semistaticBufferUpdate = {0} indicates that the bearer configured for the packet to be sent uses dynamic buffer update, semistaticBufferUpdate = {1} indicates that the bearer configured for the packet to be sent uses semi-static buffer update, and semistaticBufferUpdate = {2} indicates that the bearer configured for the packet to be sent uses static buffer update. In this Method 2, semistaticBufferUpdate = {true} or semistaticBufferUpdate = {1} can be understood as the third indication information, so that through this third indication information, the semi-static buffer update is explicitly configured for the terminal. It can be seen that in this possible implementation method, when the network device explicitly configures the semi-static buffer update for the terminal, it only determines the buffer update type configured for the terminal by whether the RRC configuration signaling carries the semistaticBufferUpdate parameter, or when the semistaticBufferUpdate parameter is carried, by the buffer update type configured for the bearer used for the packet to be sent according to the value of the semistaticBufferUpdate parameter. For example, it is described; of course, it is also possible to directly configure the buffer update type for the terminal by whether the RRC configuration signaling carries the semistaticBufferUpdate parameter, or when the semistaticBufferUpdate parameter is carried, by the value of the semistaticBufferUpdate parameter. The configuration method is similar to the method of configuring the buffer update type for the bearer used for the packet to be sent, and reference can be made to the relevant description of configuring the buffer update type for the bearer used for the packet to be sent above. Here, the embodiments of the present application will not be elaborated.

[0150] When configuring semi-static buffer update for the terminal by means of the semistaticBufferUpdate parameter or when the value of the semistaticBufferUpdate parameter is 1, the applicable range of the semistaticBufferUpdate parameter can be further restricted. For example, when the semistaticBufferUpdate parameter is configured in a bearer configuration information element, such as a PDCP configuration information element, a DRB configuration information element, or a UDC configuration information element corresponding to a bearer, it is determined that the semi-static buffer update is only valid for that bearer; when the semistaticBufferUpdate parameter is configured in a cell group configuration, it is determined that the semi-static buffer update is valid for all bearers corresponding to that cell group, or is configured to be valid for all bearers of the terminal device.

[0151] It should be noted that when configuring semi-static buffer update for the terminal, only the case where the carried parameter is the semistaticBufferUpdate parameter or the value of the semistaticBufferUpdate parameter is 1 is taken as an example for illustration, and specific settings can be made according to actual needs. Here, the embodiments of the present application do not make further restrictions.

[0152] In the second possible manner, when the terminal implicitly determines that its buffer update type is semi-static buffer update, the terminal can judge the packet data convergence protocol (PDCP) PDCP entity associated with the bearer of the packet to be sent. If the PDCP entity associated with the bearer of the packet to be sent is an unacknowledged mode radio link control (UM RLC) entity, it can be determined that the update type of the terminal compression buffer is semi-static buffer update.

[0153] It can be understood that when configuring the buffer update type for the terminal in any of the above possible manners, if a UDC is configured for the terminal, the terminal can use the compression buffer it maintains to compress the packet to be sent and send the compressed packet; if a compression mechanism for downlink data transmission based on the compression buffer is configured for the terminal, it means that the UDC mechanism is applied to the compression of downlink data transmission. The sending end can be a network device, and the receiving end can be a terminal. The terminal can use the decompression buffer it maintains to decompress the compressed packet sent by the network device. Taking the network device configuring a UDC for the terminal as an example, when the network device determines to update the compression buffer, it can send a control message to the terminal to indicate to the terminal to update the compression buffer through the control message, that is, execute the following S302:

[0154] S302. The network device sends a control message to the terminal.

[0155] Among them, the control message is used to indicate the update of the compression cache. For example, the control message can be an RRC signaling or a PDCP control protocol data unit (PDU) signaling. The control message can include information related to the updated cache content, such as the updated compression cache, the identifier of the updated cache, and any one of the string information used to indicate the update of the compression cache. For example, the string information used to indicate the update of the compression cache can be the string information in the dictionary predefined in the standard or the string information in the preconfigured dictionary, and can be specifically set according to actual needs.

[0156] It should be noted that since the terminal may maintain both a compression cache and a decompression cache at the same time, when the network device indicates to the terminal to update the cache through the control message, in addition to directly indicating the information related to the cache content updated by the terminal through the control message, it can also indicate whether it is the compression cache or the decompression cache to be updated through the control message. In this case, a direction indication information needs to be carried in the control message, and the direction indication information is used to indicate the terminal device to update the compression cache. In addition, when the network device indicates to the terminal to update the compression cache through the control message, the control message can further carry a second indication information for indicating the sequence number of the first data packet to be compressed using the updated compression cache by the terminal. The second indication information can be a PDCP COUNT value, and / or the second indication information can be a PDCP SN value, so that the terminal determines which compression cache to use for compressing the data packet to be sent according to the second indication information. In this way, the terminal only needs to send the compressed data packet to the network device subsequently, without having to send the first indication information for indicating the compression cache used by the terminal when compressing the data packet to be compressed to the network device, that is, the embodiment shown below Figure 12 Of course, when the control message carries the second indication information, when the terminal sends the compressed data packet to the network device, it can also send the first indication information for indicating the compression cache used by the terminal when compressing the data packet to be compressed to the network device, so that the network device can determine which compression cache the terminal uses when compressing the data packet to be compressed according to any one of the first indication information and the second indication information.

[0157] In the embodiment of the present application, updating the compression cache can be understood as updating the current compression cache, and the current compression cache can be understood as the compression cache before the update. Taking the current compression cache as the initial compression cache as an example, the content of the initial compression cache can be empty, or it can be the dictionary content indicated by the network device for it or directly indicate the content of the initial compression cache; of course, it can also be the predefined dictionary content or the content of the predefined initial compression cache to determine the current compression cache. After determining the current compression cache, the terminal can use the current compression cache to compress the data packet to be sent. Correspondingly, after receiving the compressed data packet, the network device will also use the decompression cache corresponding to the current compression cache to decompress the compressed data packet to obtain the data packet to be sent sent by the terminal. However, since there may be no data transmission between the network device and the terminal when the network device configures the initial compression cache for the terminal, the initial compression cache pre-set by the network device for the terminal may not be applicable to the currently transmitted data. Therefore, after a period of data transmission, the network device can determine the new compression cache content based on the transmitted data, and after determining the new compression cache content, send a control message to the terminal to instruct the terminal to update the compression cache through the control message.

[0158] When the network device instructs the terminal to update the compression cache through the control message, it can also instruct the terminal on how to update the current compression cache. By way of example, when instructing the terminal on how to update the current compression cache, any one of the updated compression cache for instructing the terminal on how to update, the identifier of the updated compression cache, and the string information for instructing the update of the compression cache can be carried in the control message and sent to the terminal, so that the terminal updates the compression cache it maintains according to the control message.

[0159] S303. The terminal updates the compression cache.

[0160] For example, when the control message used to indicate the updated compression cache includes the updated compression cache, it can be understood that the network device directly sends the updated compression cache to the terminal, so that the terminal can directly use the updated compression cache as the updated compression cache to be adopted subsequently. When the control message used to indicate the updated compression cache includes the identifier of the updated compression cache, it can be understood that the network device does not directly send the updated compression cache to the terminal, but sends the identifier of the updated compression cache to the terminal. The identifier of the updated compression cache can be the name of the updated compression cache or the serial number of the updated compression cache, as long as the updated compression cache can be uniquely determined according to the identifier of the updated compression cache. In this way, after receiving the identifier of the updated compression cache, the terminal needs to first find the updated compression cache according to the identifier of the updated compression cache, and use the updated compression cache as the updated compression cache to be adopted subsequently. When the control message used to indicate the updated compression cache includes the string information used to indicate the update of the compression cache, it can be understood that the network device does not directly send the updated compression cache to the terminal, but sends the string information used to indicate the update of the compression cache to the terminal. In this way, after receiving the string information, the terminal needs to first update the current compression cache according to the string information to obtain the updated compression cache, and use the updated compression cache as the updated compression cache to be adopted subsequently.

[0161] S304. The terminal compresses the packet to be sent.

[0162] When the terminal compresses the packet to be sent, it can use the pre-update compression cache to compress the packet to be sent, or use the updated compression cache to compress the packet to be sent.

[0163] For example, taking the terminal using the pre-update compression cache as an example, if there is a string 'abcde' in the packet to be sent that is the same as a string content in the pre-update compression cache, and the starting position of the string saved in the pre-update compression cache is the 100th byte and the length is 5 bytes, the terminal can replace the string 'abcde' in the packet to be sent with the position information and length information <100, 5>, so as to realize the compression of the string 'abcde' in the packet to be sent. Since the pre-update compression cache used for compressing the packet to be sent is actively controlled by the terminal and the network device cannot know it, in order to ensure that the decompression cache used by the network device is consistent with the compression cache used by the terminal, when the terminal sends the compressed packet to the network device, it needs to send the first indication information used to indicate the compression cache used by the terminal when compressing the packet to be compressed to the network device, that is, execute the following S305:

[0164] S305. The terminal sends first indication information to the network device.

[0165] The first indication information is used to indicate the compression cache adopted when compressing the data packet to be sent, where the compression cache is the compression cache before update, or the compression cache is the compression cache after update.

[0166] Exemplarily, the first indication information can be sent to the network device independently of the compressed data packet, or can be carried in the compressed data packet and sent to the network device. Further, when the first indication information is carried in the compressed data packet and sent to the network device, the first indication information can be carried in the protocol header of the compressed data packet, or the first indication information can also be carried in the data header of the compressed data packet.

[0167] Exemplarily, the first indication information is a field in the data packet to be sent or a checksum field in the data packet to be sent. When the first indication information is a field in the data packet to be sent, if the value of the field in the data packet to be sent is the same as the value of the field in the previous data packet adjacent to the data packet to be sent received by the receiving end, it indicates that the compression cache adopted by the terminal is the compression cache before update; if the value of the field in the data packet to be sent is different from the value of the field in the previous data packet adjacent to the data packet to be sent received by the receiving end, it indicates that the compression cache adopted by the terminal is the compression cache after update; in this way, after receiving the compressed data packet, the network device can parse out the value of the field in the data packet to be sent, and compare the value of the field in the data packet to be sent with the value of the field in the previous data packet adjacent to the data packet to be sent received by the receiving end, so as to determine the compression cache adopted by the terminal when compressing the data packet to be sent according to the comparison result.

[0168] When the first indication information is the checksum field in the data packet to be sent, the terminal can calculate the value of the checksum field according to the compression cache adopted when compressing the data packet to be sent. In this way, after receiving the compressed data packet, the network device can also parse out the value of the checksum field in the data packet to be sent, and compare the value of the checksum field in the data packet to be sent with the value of the checksum field calculated according to the compression cache before update and the value of the checksum field calculated according to the compression cache after update respectively.

[0169] If the value of the checksum field in the data packet to be sent is the same as the value of the checksum field calculated by the network device based on the compression cache before the update, it indicates that the compression cache used by the terminal for compressing the data packet to be sent is the compression cache before the update; if the value of the checksum field in the data packet to be sent is the same as the value of the checksum field calculated by the network device based on the updated compression cache, it indicates that the compression cache used by the terminal for compressing the data packet to be sent is the updated compression cache, so as to determine the compression cache used by the terminal for compressing the data packet to be sent according to the comparison result.

[0170] Exemplarily, when the first indication information is a field in the data packet to be sent, this field may include M bits, and the value of the M bits may be specified by the protocol or may be predefined (for example, negotiated between the terminal and the network device), where M is an integer greater than or equal to 1.

[0171] In a possible implementation manner, the first indication information may be a 1-bit indication field U, and this field U may be carried in the PDCP header. Exemplarily, please refer to Figure 4 as shown. Figure 4 FIG. is a schematic structural diagram of a PDCP header carrying the field U provided by an embodiment of the present application. In addition, this field U may also be carried in the compression header. Exemplarily, please refer to Figure 5 as shown. Figure 5 FIG. is a schematic structural diagram of a compression header carrying the field U provided by an embodiment of the present application. When the field U is carried in the PDCP header, a reserved bit in the PDCP header may be used as the field U; when the field U is carried in the compression header, taking the LTE compression header as an example, a reserved bit in the LTE compression header may also be used as the field U. It should be noted that when the value of the field U is used to indicate the compression cache used by the terminal for compressing the data packet to be sent, the value of this field U is specified by the protocol.

[0172] In this possible implementation manner, the compression cache used by the terminal for compressing the data packet to be sent may be indicated by the value of the field U. If the value of the field U in the data packet to be sent has not changed compared with the value of the field U in the previous packet adjacent to the data packet to be sent received by the receiving end (without considering the case where the sequence number of the data packet is reversed), it indicates that the terminal has not updated the compression cache, and the compression cache used for compressing the data packet to be sent is still the compression cache before the update; if the value of the field U in the data packet to be sent has changed compared with the value of the field U in the previous packet adjacent to the data packet to be sent received by the receiving end, it indicates that the terminal has updated the compression cache, and the compression cache used for compressing the data packet to be sent is the updated compression cache.

[0173] After receiving the compressed data packet, the network device can parse the value of field U in the data packet to be sent, and compare the value of field U in the data packet to be sent with the value of field U in the previous data packet adjacent to the data packet to be sent received at the receiving end. If the value of field U in the data packet to be sent remains unchanged compared with the value of field U in the previous data packet adjacent to the data packet to be sent (without considering the case where the sequence number of the data packet is flipped), the network device can determine that the compression cache used by the terminal when compressing the data packet to be sent is the compression cache before the update; if the value of field U in the data packet to be sent changes compared with the value of field U in the previous data packet adjacent to the data packet to be sent received at the receiving end, the network device can determine that the compression cache used by the terminal when compressing the data packet to be sent is the compression cache after the update. After the compression cache used by the terminal when compressing the data packet to be sent, the compressed data packet can be decompressed using the decompression cache corresponding to the compression cache, ensuring that the decompression cache used by the network device is consistent with the compression cache used by the terminal, thereby improving the success rate of decompression.

[0174] To help understand the meaning of flipping, taking the SN length as 12 bits as an example, the SN number ranges from 0 to 4095, and the SN corresponding to the next data packet of the data packet with SN = 4095 is SN = 0, then it is considered that SN has flipped. For the case where SN has flipped, the data packet with SN = 4095 is the previous data packet adjacent to the data packet with SN = 0.

[0175] Exemplarily, reference can be made to Figure 6 as shown Figure 6 FIG. shows a schematic diagram of a data packet processing process provided by an embodiment of the present application. Assuming that when the terminal compresses the data packet with the sequence number SN = 100 and the data packet with the sequence number SN = 101, the compression cache 1 before the update is used to compress the data packet with the sequence number SN = 100 and the data packet with the sequence number SN = 101 respectively, and the values of field U in the compressed data packets with the sequence numbers SN = 100 and SN = 101 are both equal to 0; when the terminal compresses the data packet with the sequence number SN = 102, the compression cache 2 after the update is used to compress the data packet with the sequence number SN = 102, and the value of field U in the compressed data packet with the sequence number SN = 102 is equal to 1; if the subsequent compression of the data packet with the sequence number SN = 103 and subsequent data packets still uses the compression cache 2 after the update, then the values of field U in the compressed data packets with the sequence numbers SN = 103 and subsequent data packets do not flip and are still equal to 1.

[0176] When the network device receives these compressed data packets, if a data packet with a compressed sequence number SN of 102 is lost, when it receives a data packet with a compressed sequence number SN of 103, it can compare the value of field U in the data packet with a compressed sequence number SN of 103 with the value of field U in the previous data packet with a compressed sequence number SN of 101 that it receives and is adjacent to the data packet with SN of 103. It can be seen that the value of field U changes from 0 to 1, which is a flip. Then the network device can determine that the compression cache used by the terminal for compressing the data packet with sequence number SN of 103 is the updated compression cache 2. In this way, the network device can use the decompression cache corresponding to the updated compression cache 2 to decompress the compressed data packet, so that even in the case of packet loss, it can ensure that the decompression cache used by the network device is consistent with the compression cache used by the terminal, thereby improving the success rate of decompression.

[0177] In another possible implementation, the first indication information may be an N-bit indication field I, where N is greater than or equal to 1. This field I can be carried in the PDCP header. For example, please refer to Figure 7 as shown. Figure 7 FIG. shows a schematic structural diagram of a PDCP header carrying field I provided by an embodiment of the present application. In addition, this field I can also be carried in the UDC header. For example, please refer to Figure 8 as shown.

[0178] Figure 8 FIG. shows a schematic structural diagram of a UDC header carrying field I provided by an embodiment of the present application. When field I can be carried in the PDCP header, two reserved bits in the PDCP header can be used as field I; when field U can also be carried in the UDC header, taking the LTE UDC header as an example, two reserved bits in the LTE UDC header can also be used as field I. It should be noted that the value of field I can be 0 to 3; the initial value can be 0. If the compression cache used by the terminal for compressing a data packet is different from the compression cache used for compressing the previous data packet, the value of field I is incremented by 1. When it exceeds the maximum value of 3, it flips to 0. When indicating the compression cache used by the terminal for compressing the data packet to be sent through the value of this field I, the value of this field I is specified by the protocol.

[0179] In this possible implementation, the value of field I can be used to indicate the compression cache adopted by the terminal when compressing the packet to be sent. If the value of field I in the packet to be sent remains unchanged compared with the value of field I in the previous packet adjacent to the packet to be sent received by the receiving end (without considering the case where the packet sequence number is reversed), it means that the terminal has not updated the compression cache, and the compression cache adopted when compressing the packet to be sent is still the compression cache before the update. If the value of field I in the packet to be sent has changed compared with the value of field I in the previous packet adjacent to the packet to be sent received by the receiving end, it means that the terminal has updated the compression cache, and the compression cache adopted when compressing the packet to be sent is the compression cache after the update.

[0180] In this way, after the network device receives the compressed packet, it can parse out the value of field I in the packet to be sent, and compare the value of field I in the packet to be sent with the value of field I in the previous packet adjacent to the packet to be sent received by the receiving end. If the value of field I in the packet to be sent remains unchanged compared with the value of field I in the previous packet adjacent to the packet to be sent received by the receiving end (without considering the case where the packet sequence number is reversed), the network device can determine that the compression cache adopted by the terminal when compressing the packet to be sent is the compression cache before the update. If the value of field I in the packet to be sent has changed compared with the value of field I in the previous packet adjacent to the packet to be sent received by the receiving end, the network device can determine that the compression cache adopted by the terminal when compressing the packet to be sent is the compression cache after the update. After the compression cache adopted by the terminal when compressing the packet to be sent, the decompression cache corresponding to the compression cache can be used to decompress the compressed packet, ensuring that the decompression cache adopted by the network device is consistent with the compression cache adopted by the terminal, thereby improving the success rate of decompression.

[0181] For example, refer to Figure 9 as shown in Figure 9 FIG. 4 is a schematic diagram of another packet processing process provided by an embodiment of the present application. Assume that when the terminal compresses the packet with sequence number SN = 100 and the packet with sequence number SN = 101, the compression cache 1 before the update is used to compress the packet with sequence number SN = 100 and the packet with sequence number SN = 101 respectively, and the values of field I in the compressed packets with sequence number SN = 100 and sequence number SN = 101 are both equal to 2. When the terminal compresses the packet with sequence number SN = 102, the compression cache 2 after the update is used to compress the packet with sequence number SN = 102, and the value of field I in the compressed packet with sequence number SN = 102 is equal to 3.

[0182] When subsequent packets with sequence number SN of 103 and subsequent packets are compressed, if the updated compression cache 2 is still used for compression, and the value of field I in the compressed packets with sequence number SN of 103 and subsequent packets does not flip and is still equal to 3. When the network device receives these compressed packets, if the packet with compressed sequence number SN of 102 is lost, when it receives the packet with compressed sequence number SN of 103, it can compare the value of field I in the packet with compressed sequence number SN of 103 with the value of field I in the immediately preceding packet with compressed sequence number SN of 101 adjacent to the packet with sequence number SN of 103. It can be seen that the value of field U changes from 2 to 3, which flips. Then the network device can determine that the compression cache used by the terminal for compressing the packet with sequence number SN of 103 is the updated compression cache 2. In this way, the network device can use the decompression cache corresponding to the updated compression cache 2 to decompress the compressed packets, so that even in the case of packet loss, it can ensure that the decompression cache used by the network device is consistent with the compression cache used by the terminal, thereby improving the success rate of decompression.

[0183] In another possible implementation, the first indication information can be a P-bit indication field Indication, where P is greater than or equal to 1. This field Indication can be carried in the PDCP header. For example, please refer to Figure 10 as shown Figure 10 FIG. [X] is a schematic structural diagram of a PDCP header carrying the field Indication provided by an embodiment of the present application. In addition, this field Indication can also be carried in the compression header. For example, please refer to Figure 11 as shown Figure 11 Note: In the above translation, [X] in "FIG. [X]" needs to be filled with the actual figure number according to the specific content.Schematic diagram of a compression header carrying the field Indication provided by an embodiment of this application. When the field Indication can be carried in the PDCP header, two reserved bits in the PDCP header can be used as the field Indication; when the field Indication can also be carried in the compression header, taking the LTE compression header as an example, two reserved bits in the LTE compression header can also be used as the field Indication. It should be noted that the value of the field Indication is different from the values of the above-mentioned fields U and I. The value of this field Indication is not specified by the protocol but is predefined. For example, when the network device controls the terminal to update the compression cache through a control message, it can carry the value of the field Indication in the control message and send it to the terminal together, so that when the terminal compresses the data packet using the updated compression cache, it can modify the value of the field Indication in the data packet to the value of the field Indication included in the received control message.

[0184] In this possible implementation, assume that when the terminal compresses data packet 1, it uses the pre-update compression cache 1 to compress this data packet 1, then the field Indication in the compressed data packet is the initial value 0; when the network device indicates the terminal to update the compression cache through a control message, it sends the value 1 of the field Indication to the terminal together; when the terminal executes the update of the compression cache and uses the updated compression cache 2 to compress the subsequent data packet 2, then the field Indication in the compressed data packet becomes 1; when the network device receives the compressed data packet, if the field Indication in the compressed data packet is 1, it can determine that the compression cache used by the terminal when compressing data packet 2 is the updated compression cache 2. In this way, the network device can use the decompression cache corresponding to this updated compression cache 2 to decompress the compressed data packet, ensuring that the decompression cache used by the network device is consistent with the compression cache used by the terminal, thereby improving the success rate of decompression.

[0185] In yet another possible implementation, the first indication information may be the field FR, and this field FR may also be carried in the UDC header. When the original field FR is used to indicate the compression cache adopted by the terminal for the data packet to be sent, the FR field is no longer defined as: FR = 0 indicates that the compression cache is not reset, and FR = 1 indicates that the compression cache is reset. Instead, it is re - defined as: if the value of the field FR is flipped, it indicates that the compression cache is updated; if the value of the field FR is not flipped, it indicates that the compression cache is not updated, which is similar to the field U in the above - mentioned first possible implementation. When the field FR is used to indicate the compression cache adopted by the terminal for the data packet to be sent, its specific implementation is similar to the specific implementation of using the field U to indicate the compression cache adopted by the terminal for the data packet to be sent in the above - mentioned first possible implementation. For the relevant description of using the field U to indicate the compression cache adopted by the terminal for the data packet to be sent, refer to the above - mentioned first possible implementation. Here, for how to use the field FR to indicate the compression cache adopted by the terminal for the data packet to be sent, the embodiments of the present application will not elaborate further.

[0186] To ensure that the decompression cache adopted by the network device is consistent with the compression cache adopted by the terminal, when the terminal sends the compressed data packet to the network device, it can send the first indication information used to indicate the compression cache adopted by the terminal for the data packet to be compressed to the network device in the above - mentioned several possible ways. After receiving the compressed data packet and the first indication information, the network device can decompress the compressed data packet according to the first indication information to obtain the data packet sent by the terminal, that is, execute the following S306.

[0187] S306. The network device decompresses the compressed data packet according to the first indication information.

[0188] After receiving the first indication information, the network device can determine which compression cache of the compression cache adopted by the terminal for the data packet to be compressed according to the first indication information. The specific determination method can refer to the relevant description in the above - mentioned S305, and use the decompression cache corresponding to the compression cache to decompress the compressed data packet, ensuring that the decompression cache adopted by the network device is consistent with the compression cache adopted by the terminal, thereby improving the success rate of decompression.

[0189] Taking the replacement of the string 'abcde' in the data packet to be sent with the position information and length information <100,5> of the compression cache adopted by the terminal as an example of the compression of the string 'abcde' in the data packet to be sent, since the compression cache before the update adopted during the compression of this data packet to be sent is actively controlled by the terminal, the network device cannot know it.

[0190] Therefore, in order to ensure that the decompression cache used by the network device is the same as the compression cache used by the terminal, when the terminal sends the compressed data packet to the network device, it needs to send the first indication information indicating the compression cache used by the terminal when compressing the data packet to be compressed to the network device at the same time. After receiving the first indication information, the network device can determine which compression cache the terminal used when compressing the data packet to be compressed according to the first indication information, and search for 5 consecutive bytes starting from the 100th byte in the decompression cache corresponding to the compression cache according to the position information and length information <100,5> carried in the compressed data packet. Since the decompression cache and the compression cache are the same, the 5 consecutive bytes starting from the 100th byte in the decompression cache will also be the string 'abcde'. After determining the string 'abcde' and replacing the position information and length information with the string 'abcde', the data packet to be sent can be restored.

[0191] It can be seen that in the data processing method provided by the embodiment of the present application, when the terminal sends the compressed data packet to the network device, it can send the first indication information to the network device at the same time, so as to indicate the compression cache used by the terminal when compressing the data packet to be compressed through the first indication information. In this way, after receiving the first indication information, the network device can determine which compression cache the terminal used when compressing the data packet to be compressed according to the first indication information, and use the decompression cache corresponding to the compression cache to decompress the compressed data packet, ensuring that the decompression cache used by the network device is the same as the compression cache used by the terminal, thereby improving the success rate of decompression.

[0192] The above Figure 3 In the embodiment shown, it is described in detail that in a possible implementation manner, in order to ensure that the decompression cache used by the network device is the same as the compression cache used by the terminal and improve the success rate of decompression, the terminal actively controls which compression cache (the compression cache before update or the compression cache after update) to use to compress the data to be sent, and notifies the network device of the compression cache it uses. Next, in another possible implementation manner, in order to ensure that the decompression cache used by the network device is the same as the compression cache used by the terminal and improve the success rate of decompression, it is no longer the terminal that actively controls which compression cache (the compression cache before update or the compression cache after update) to use to compress the data to be sent, but the network device controls which compression cache the terminal uses to compress the data to be sent. For example, please refer to Figure 12 As shown, Figure 12 FIG. is a schematic flowchart of another data processing method provided by the embodiment of the present application. The data processing method may include:

[0193] S1201. The network device configures semi-static cache update for the terminal.

[0194] It can be understood that in S1201, the method by which the network device configures semi-static cache update for the terminal is similar to the method by which the network device configures semi-static cache update for the terminal in S301 above. Specifically, reference can be made to the relevant description of the method by which the network device configures semi-static cache update for the terminal in S301 above. Here, for the method by which the network device configures semi-static cache update for the terminal, the embodiments of the present application will not be elaborated further.

[0195] S1202. The network device sends a control message to the terminal.

[0196] Among them, the control message is used to indicate the update of the compression cache, and the control message includes any one of the updated compression cache, the identifier of the updated compression cache, and the string information used to indicate the update of the compression cache.

[0197] It can be understood that in S1202, the method by which the network device sends a control message to the terminal, and the content included in the control message is respectively similar to the method by which the network device sends a control message to the terminal in S302 above, and the content included in the control message. Specifically, reference can be made to the method by which the network device sends a control message to the terminal in S302 above, and the relevant description of the content included in the control message. Here, the embodiments of the present application will not be elaborated further.

[0198] S1203. The network device sends second indication information to the terminal.

[0199] Among them, the second indication information is used to indicate the sequence number of the first data packet compressed by the terminal using the updated compression cache. By way of example, the second indication information may be a PDCP COUNT value, and / or the second indication information may be a PDCP SN value.

[0200] When the network device sends the second indication information to the terminal, the second indication information may be sent to the terminal independently of the control message, or may be carried in the control message and sent to the terminal. Specifically, it can be set according to actual needs. Here, for the sending manner of the second indication information, the embodiments of the present application will not be further restricted.

[0201] It can be understood that when the second indication information is carried in the control message and sent to the terminal, compared with the control message in S302 above, in addition to including any one of the updated compression cache, the identifier of the updated compression cache, and the string information used to indicate the update of the compression cache, the control message further includes the second indication information for indicating the sequence number of the first data packet compressed by the terminal using the updated compression cache, so as to indicate which compression cache the terminal uses to compress the data packet to be sent through the second indication information.

[0202] S1204. The terminal updates the compressed cache.

[0203] It can be understood that in S1204, the method for the terminal to update the compressed cache is similar to the method for the terminal to update the compressed cache in S303 above. For the specific details, reference can be made to the relevant description of the terminal updating the compressed cache in S303 above. Here, the embodiments of the present application will not elaborate on how the terminal updates the compressed cache.

[0204] S1205. The terminal compresses the data packet to be sent according to the second indication information.

[0205] Among them, when compressing the data packet to be sent, the compressed cache used is the compressed cache before the update, or the compressed cache used when compressing the data packet to be sent is the compressed cache after the update.

[0206] When the terminal compresses the data packet to be sent, it is no longer that the terminal actively controls which compressed cache (the compressed cache before the update or the compressed cache after the update) is used to compress the data to be sent and notifies the network device of the compressed cache it uses. Instead, it determines which compressed cache to use to compress the data packet to be sent according to the second indication information sent by the network device. When compressing the data packet to be sent, it will compare the sequence number of the data packet to be sent with the sequence number indicated by the second indication information. If the sequence number of the data packet to be sent is less than the sequence number indicated by the second indication information, the compressed cache before the update is used to compress the data packet to be sent; if the sequence number of the data packet to be sent is greater than or equal to the sequence number indicated by the second indication information, the compressed cache after the update is used to compress the data packet to be sent. For subsequent data packets with sequence numbers greater than the sequence number indicated by the second indication information, if the terminal does not receive a new control message for updating the compressed cache and a new second indication information, the compressed cache after the update continues to be used to compress the data packet to be sent.

[0207] Suppose that when the terminal compresses the PDCP packet with the sequence number SN being 100, it uses the pre-update compression cache 1 to compress the PDCP packet with the sequence number SN being 100. When compressing the PDCP packet with the sequence number SN being 101, if the terminal receives the control message for updating the compression cache and the second indication information sent by the network device, and the sequence number indicated by the second indication information is 200, then the terminal continues to use the pre-update compression cache 1 to compress the PDCP packet with the sequence number SN being 101, and uses the pre-update compression cache 1 to compress the PDCP packets with the sequence numbers SN being 102 and subsequent ones until compressing the PDCP packet with the sequence number 200, at which time it uses the post-update compression cache 2 to compress the PDCP packet with the sequence number SN being 200. For the subsequent packets with the sequence numbers greater than 200, if the terminal does not receive the new control message for updating the compression cache and the new second indication information, it continues to use the post-update compression cache to compress the packets; in this way, after receiving the compressed packet, the network device can determine the compression cache used by the terminal when compressing the packet according to the sequence number of the compressed packet, and use the decompression cache corresponding to the compression cache to decompress the compressed packet, so that even in the case of packet loss, it can ensure that the decompression cache used by the network device is consistent with the compression cache used by the terminal, thereby improving the decompression success rate.

[0208] In the embodiment of the present application, when the terminal compresses the packet to be sent, it is no longer the terminal that actively controls which compression cache (the pre-update compression cache or the post-update compression cache) to use to compress the packet to be sent, but determines which compression cache to use to compress the packet to be sent according to the second indication information sent by the network device. Therefore, after the terminal compresses the packet to be sent, it only needs to send the compressed packet to the network device, and there is no need to send the first indication information for indicating the compression cache used by the terminal when compressing the packet to be sent to the terminal device. Of course, it is also possible to carry the first indication information in the packet at the same time when sending the compressed packet to the network device, which can be specifically set according to actual needs. Here, the embodiment of the present application only takes the example that after the terminal compresses the packet to be sent, it only needs to send the compressed packet to the network device for illustration, but it does not mean that the embodiment of the present application is only limited to this.

[0209] S1206. The terminal sends the compressed packet to the network device.

[0210] S1207. The network device decompresses the compressed packet according to the second indication information.

[0211] After receiving the compressed data packet sent by the terminal, the network device determines which compression cache in the compression cache used by the terminal for compressing the data packet to be compressed according to the sequence number of the compressed data packet, and uses the decompression cache corresponding to the compression cache to decompress the compressed data packet, ensuring that the decompression cache used by the network device is consistent with the compression cache used by the terminal, thereby improving the success rate of decompression.

[0212] It can be seen that in the data processing method provided by the embodiment of the present application, the terminal first receives the second indication information for indicating the sequence number of the first data packet for the terminal to use the updated compression cache for compression sent by the network device, and determines the compression cache used for compressing the data packet to be compressed according to the second indication information. In this way, after the network device receives the compressed data packet, it can determine which compression cache in the compression cache used by the terminal for compressing the data packet to be compressed according to the sequence number of the compressed data packet, and use the decompression cache corresponding to the compression cache to decompress the compressed data packet, ensuring that the decompression cache used by the network device is consistent with the compression cache used by the terminal, thereby improving the success rate of decompression.

[0213] It can be seen that the above Figure 3 and Figure 12 The data processing methods of the illustrated embodiments are all described by taking the Figure 1 illustrated scenario as an example. Among them, the sending end is the terminal, the receiving end is the network device, and the Uu interface is used for data transmission between the terminal and the network device. Of course, the data processing method provided by the embodiment of the present application can also be applied to the Figure 2 illustrated scenario. As shown in combination with Figure 2 , the sending end is one of the two terminals, and the receiving end is the other terminal. For the convenience of distinguishing the sending end and the receiving end, the sending end can be denoted as the first terminal, and the receiving end can be denoted as the second terminal. The first terminal and the second terminal use the sidelink interface for data transmission. It can be understood that in the Figure 2 illustrated scenario, in order to ensure that the decompression cache used by the receiving end, the second terminal, is consistent with the compression cache used by the sending end, the first terminal, to improve the success rate of decompression, it can also be implemented through two possible implementation manners. In one possible implementation manner, in the UDC compression mechanism, the first terminal actively controls which compression cache (the compression cache before update or the updated compression cache) is used to compress the data to be sent, and notifies the second terminal of the compression cache it uses. See the above Figure 3the relevant description in the embodiments shown; in another possible implementation, in the UDC compression mechanism, it is no longer the first terminal that actively controls which compression cache (the compression cache before update or the compression cache after update) to use for compressing the data to be sent, but the second terminal controls the first terminal to use which compression cache to compress the data to be sent. Refer to the relevant description in the embodiments shown above Figure 12 the relevant description in the embodiments shown above can ensure that the decompression cache used by the second terminal is consistent with the compression cache used by the first terminal, thereby improving the success rate of decompression. Next, in combination with Figure 2 the scenario shown, taking the second terminal controlling the first terminal to use which compression cache to compress the data to be sent as an example, the data processing method provided in the embodiments of the present application will be described in detail. For example, please refer to Figure 13 as shown Figure 13 is a schematic flowchart of another data processing method provided in the embodiments of the present application. The data processing method may include:

[0214] S1301. The second terminal configures semi-static cache update for the first terminal.

[0215] It can be understood that in S1301, the method for the second terminal to configure semi-static cache update for the first terminal is similar to the method for the receiving end to configure semi-static cache update for the terminal in S301 above. Specifically, refer to the relevant description of the receiving end configuring semi-static cache update for the terminal in S301 above. Here, for how the second terminal configures semi-static cache update for the first terminal, the embodiments of the present application will not be elaborated further.

[0216] It should be noted that in the embodiments of the present application, when configuring semi-static cache update for the first terminal, the network device may also configure semi-static cache update for the first terminal and the second terminal respectively. When the network device configures semi-static cache update for the first terminal and the second terminal respectively, the method for the network device to configure semi-static cache update for the first terminal and the second terminal respectively is similar to the method for the network device to configure semi-static cache update for the terminal in S301 above. Specifically, refer to the relevant description of the network device configuring semi-static cache update for the terminal in S301 above. Here, for how the network device configures semi-static cache update for the first terminal and the second terminal respectively, the embodiments of the present application will not be elaborated further.

[0217] S1302. The second terminal sends a control message to the first terminal.

[0218] Among them, the control message is used to indicate updating the compression cache, and the control message includes any one of the updated compression cache, the identifier of the updated compression cache, and the string information used to indicate updating the compression cache.

[0219] It can be understood that in S1202, the method for the second terminal to send a control message to the first terminal, and the content included in the control message is respectively similar to the method for the network device to send a control message to the terminal in S302 above, and the content included in the control message. Specifically, reference can be made to the relevant description of the method for the network device to send a control message to the terminal in S302 above, and the content included in the control message. Here, the embodiments of the present application will not be described in detail again.

[0220] It can be seen that in the above S1301 - S1302, it is the second terminal that configures semi-static cache update for the first terminal and sends a control message to the first terminal, that is, the second terminal is the control end. Of course, in the above S1301 - S1302, it can also be the first terminal that configures semi-static cache update for the second terminal and sends a control message to the second terminal, which can be specifically set according to actual needs. Here, the embodiments of the present application only take the case where the second terminal configures semi-static cache update for the first terminal and sends a control message to the first terminal as an example for illustration, but it does not mean that the embodiments of the present application are only limited to this.

[0221] S1303. The second terminal sends second indication information to the first terminal.

[0222] Among them, the second indication information is used to indicate the sequence number of the first data packet for which the first terminal uses the updated compression cache for compression. By way of example, the second indication information can be a PDCP COUNT value, and / or the second indication information can be a PDCP SN value.

[0223] When the second terminal sends the second indication information to the first terminal, the second indication information can be sent to the first terminal independently of the control message, or can be carried in the control message and sent to the first terminal, which can be specifically set according to actual needs. Here, the embodiments of the present application do not further limit the sending method of the second indication information. It can be understood that when the second indication information is carried in the control message and sent to the first terminal, compared with the control message in S302 above, in addition to including any one of the updated compression cache, the identifier of the updated compression cache, and the string information used to indicate the update of the compression cache, the control message further includes the second indication information used to indicate the sequence number of the first data packet for which the first terminal uses the updated compression cache for compression, so as to indicate which compression cache the first terminal uses to compress the data packet to be sent through the second indication information.

[0224] S1304. The first terminal updates the compression cache.

[0225] It can be understood that, in S1304, the method for the first terminal to update the compression cache is similar to the method for the terminal to update the compression cache in S303 above. Specifically, reference can be made to the relevant description of the terminal updating the compression cache in S303 above. Here, for how the first terminal updates the compression cache, the embodiments of this application will not elaborate further.

[0226] S1305. The first terminal compresses the data packet to be sent according to the second indication information.

[0227] Among them, when compressing the data packet to be sent, the compression cache used is the compression cache before the update, or the compression cache used when compressing the data packet to be sent is the updated compression cache.

[0228] It can be understood that the method for the first terminal to compress the data packet to be sent according to the second indication information is similar to the method for the terminal to compress the data packet to be sent according to the second indication information in S1205 above. Specifically, reference can be made to the relevant description of the terminal compressing the data packet to be sent according to the second indication information in S1205 above. Here, for how the first terminal compresses the data packet to be sent according to the second indication information, the embodiments of this application will not elaborate further.

[0229] In the embodiments of this application, when the first terminal compresses the data packet to be sent, since it determines which compression cache to use for compressing the data packet to be sent according to the second indication information sent by the second terminal, after the first terminal compresses the data packet to be sent, it only needs to send the compressed data packet to the second terminal, and there is no need to send the first indication information to the first terminal device indicating the compression cache used when the first terminal compresses the data packet to be sent. Of course, it is also possible to carry the first indication information in the data packet at the same time when sending the compressed data packet to the second terminal, which can be specifically set according to actual needs. Here, the embodiments of this application only take the example that after the first terminal compresses the data packet to be sent, it only needs to send the compressed data packet to the second terminal for illustration, but it does not mean that the embodiments of this application are only limited to this.

[0230] S1306. The first terminal sends the compressed data packet to the receiving end.

[0231] S1307. The second terminal decompresses the compressed data packet according to the second indication information.

[0232] After receiving the compressed data packet sent by the first terminal, the second terminal determines which compression cache among the compression caches for compression buffering the first terminal used when compressing the data packet to be compressed according to the sequence number of the compressed data packet, and decompresses the compressed data packet by using the decompression cache corresponding to the compression cache, ensuring that the decompression cache used by the second terminal is consistent with the compression cache used by the first terminal, thereby improving the success rate of decompression.

[0233] It can be seen that in the data processing method provided by the embodiment of this application, the first terminal first receives the second indication information indicating the sequence number of the first data packet for instructing the first terminal to use the updated compression cache for compression sent by the second terminal, and determines the compression cache used when compressing the data packet to be compressed according to the second indication information sent by the second terminal. In this way, after the second terminal receives the compressed data packet, it can determine which compression cache among the compression caches for compression buffering the first terminal used when compressing the data packet to be compressed according to the sequence number of the compressed data packet, and decompresses the compressed data packet by using the decompression cache corresponding to the compression cache, ensuring that the decompression cache used by the second terminal is consistent with the compression cache used by the first terminal, thereby improving the success rate of decompression.

[0234] The above Figure 3 、 Figure 12 and Figure 13 The embodiments shown can all solve the problem that in the UDC compression mechanism, when the receiving end instructs the sending end to update the compression cache, due to reasons such as data retransmission, the sending end does not receive the indication information and still continues to compress with the compression cache before the update, resulting in an incorrect decompression because the decompression cache used by the receiving end is inconsistent with the compression cache used by the sending end. In a possible implementation manner, the sending end actively controls which compression cache (the compression cache before the update or the updated compression cache) to use to compress the data to be sent, and notifies the receiving end of the compression cache it uses through the first indication information, so that the receiving end uses the corresponding decompression cache for decompression, ensuring that the decompression cache used by the receiving end is consistent with the compression cache used by the sending end, thereby improving the success rate of decompression. For the specific technical solution, reference can be made to the embodiments shown in the above Figure 3 In another possible implementation manner, it is no longer the sending end that actively controls which compression cache (the compression cache before the update or the updated compression cache) to use to compress the data to be sent, but the receiving end controls which compression cache the sending end uses to compress the data to be sent through the second indication information, and the receiving end uses the corresponding decompression cache for decompression, ensuring that the decompression cache used by the receiving end is consistent with the compression cache used by the sending end, thereby improving the success rate of decompression. For the specific technical solution, reference can be made to the above Figure 12 or Figure 13The technical solutions in the illustrated embodiments.

[0235] It can be understood that when the sending end instructs the receiving end to update the decompression cache, due to reasons such as data retransmission, the receiving end does not receive this indication information and still continues to decompress the data using the decompression cache before the update. This will also cause the problem of decompression errors due to the mismatch between the decompression cache adopted by the receiving end and the compression cache adopted by the sending end. To solve the problem that due to reasons such as data retransmission, the receiving end does not receive the indication information to update the decompression cache and still continues to decompress the data using the decompression cache before the update, which will also cause the problem of decompression errors due to the mismatch between the decompression cache adopted by the receiving end and the compression cache adopted by the sending end, it can also be achieved through two possible implementation methods.

[0236] In one possible implementation method, the sending end actively controls which decompression cache (the decompression cache before the update or the decompression cache after the update) the receiving end uses to decompress the compressed data packet, and controls which decompression cache the receiving end uses to decompress the compressed data packet through an indication information. For example, this indication information can be the first indication information in the above Figure 3 illustrated embodiment, that is, implicitly indicates the decompression cache that the receiving end should use when decompressing the data packet by the compression cache adopted by the sending end when compressing the data packet to be sent. Similar to the method in the above Figure 3 illustrated embodiment, where the sending end notifies the receiving end of the compression cache adopted when compressing the data packet to be sent through the first indication information. Specifically, reference can be made to the relevant description in the above Figure 3 illustrated embodiment. Here, the embodiments of the present application will not be elaborated further. In this way, it can be ensured that the decompression cache adopted by the receiving end is consistent with the compression cache adopted by the sending end, thereby improving the success rate of decompression. Of course, when the sending end actively controls which decompression cache (the decompression cache before the update or the decompression cache after the update) the receiving end uses to decompress the data packet, this indication information can also directly be the sequence number of the first data packet for which the receiving end uses the decompression cache after the update to decompress. By way of example, this indication information can be the PDCP COUNT value, and / or, this indication information can be the PDCP SN value. Similar to the method in the above Figure 12 or Figure 13 illustrated embodiment, where the receiving end controls which compression cache the sending end uses to compress the data to be sent through the second indication information. Specifically, reference can be made to the relevant description in the above Figure 12 or Figure 13 illustrated embodiment. Here, the embodiments of the present application will not be elaborated further. In this way, it can be ensured that the decompression cache adopted by the receiving end is consistent with the compression cache adopted by the sending end, thereby improving the success rate of decompression.

[0237] In another possible implementation, the receiving end actively controls which decompression cache (the decompression cache before update or the decompression cache after update) is used to decompress the compressed data packet, and controls the sequence number of the first data packet for which the sending end uses the updated compression cache for compression through an indication message. For example, the indication message can be a PDCP COUNT value, and / or the indication message can be a PDCP SN value, which is similar to the method in the above Figure 12 Or Figure 13 In the embodiment shown, the method by which the receiving end controls which compression cache the sending end uses to compress the data to be sent through the second indication message is similar. For specific details, reference can be made to the relevant descriptions in the above Figure 12 Or Figure 13 shown embodiment. Here, the embodiments of the present application will not be elaborated again. In this way, it can be ensured that the decompression cache used by the receiving end is consistent with the compression cache used by the sending end, thereby improving the success rate of decompression.

[0238] Combined with the above Figure 3 、 Figure 12 And Figure 13 It can be seen from the shown embodiments that the above embodiments are all described by taking the example that when the terminal supports UDC, the network device instructs the terminal to update the compression cache. When the terminal supports the compression mechanism for downlink data transmission based on the compression cache, the network device can instruct the terminal to update the decompression cache. When the network device instructs the terminal to update the decompression cache, there are also at least two possible implementation manners.

[0239] In a possible implementation manner, the network device can actively control which decompression cache (the decompression cache before update or the decompression cache after update) the terminal uses to decompress the compressed data packet, and controls which decompression cache the terminal uses to decompress the compressed data packet through an indication message. For example, the indication message can be the first indication message in the above Figure 3 shown embodiment, that is, the compression cache used by the network device when compressing the data packet to be sent implicitly indicates the decompression cache that should be used when the terminal decompresses the data packet, which is similar to the method in the above Figure 3 shown embodiment in which the terminal notifies the network device of the compression cache used when compressing the data packet to be sent through the first indication message. For specific details, reference can be made to the relevant descriptions in the above Figure 3 shown embodiment. Here, the embodiments of the present application will not be elaborated again.

[0240] This can ensure that the decompression cache adopted by the receiving end matches the compression cache adopted by the sending end, thereby improving the success rate of decompression. Of course, when the network device actively controls which decompression cache (the decompression cache before update or the decompression cache after update) the terminal uses to decompress the compressed data packet, the indication information can directly be the sequence number of the first data packet that the terminal uses the decompression cache after update to decompress. By way of example, the indication information can be the PDCP COUNT value, and / or, the indication information can be the PDCP SN value, which is similar to the method in which the network device controls which compression cache the terminal uses to compress the data to be sent through the second indication information in the embodiment shown above. Specifically, reference can be made to the relevant description in the embodiment shown above. Here, the embodiments of the present application will not be elaborated any further. This can ensure that the decompression cache adopted by the terminal is consistent with the compression cache adopted by the network device, thereby improving the success rate of decompression. Figure 12 In the embodiment shown above, the method in which the network device controls which compression cache the terminal uses to compress the data to be sent through the second indication information is similar. Specifically, reference can be made to the relevant description in the embodiment shown above. Figure 12 Here, the embodiments of the present application will not be elaborated any further. This can ensure that the decompression cache adopted by the terminal is consistent with the compression cache adopted by the network device, thereby improving the success rate of decompression.

[0241] In another possible implementation manner, the terminal actively controls which decompression cache (the decompression cache before update or the decompression cache after update) to use to decompress the compressed data packet, and controls the sequence number of the first data packet that the network device uses the decompression cache after update to compress through an indication information. By way of example, the indication information can be the PDCP COUNT value, and / or, the indication information can be the PDCP SN value, which is similar to the method in which the network device controls which compression cache the terminal uses to compress the data to be sent through the second indication information in the embodiment shown above. Specifically, reference can be made to the relevant description in the embodiment shown above. Figure 12 Here, the embodiments of the present application will not be elaborated any further. This can ensure that the decompression cache adopted by the terminal is consistent with the compression cache adopted by the network device, thereby improving the success rate of decompression. Figure 12 Here, the embodiments of the present application will not be elaborated any further. This can ensure that the decompression cache adopted by the terminal is consistent with the compression cache adopted by the network device, thereby improving the success rate of decompression.

[0242] Figure 14 FIG. 15 is a schematic structural diagram of a communication device 140 provided by an embodiment of the present application. The communication device 140 is a sending end. By way of example, please refer to Figure 14 shown in FIG. The communication device 140 may include:

[0243] A processing unit 1401, configured to update the compression cache; and compress the data packet to be sent.

[0244] A sending unit 1402, configured to send a first indication information to a receiving end; the first indication information is used to indicate the compression cache used when compressing the data packet to be sent, the compression cache used is the compression cache before update, or, the compression cache used is the compression cache after update.

[0245] Optionally, the first indication information is carried in the compressed data packet.

[0246] Optionally, the first indication information is carried in the protocol header of the compressed data packet, or the first indication information is carried in the data header of the compressed data packet.

[0247] Optionally, the first indication information is a field in the data packet to be sent. If the value of the field is the same as the value of the field in the previous data packet adjacent to the data packet to be sent received by the receiving end, the compression cache used is the compression cache before the update; if the value of the field is different from the value of the field in the previous data packet adjacent to the data packet to be sent received by the receiving end, the compression cache used is the updated compression cache.

[0248] Optionally, the first indication information is the checksum field in the data packet to be sent, and the checksum field is determined according to the compression cache used when compressing the data packet to be sent.

[0249] Optionally, the communication device 140 may further include:

[0250] A receiving unit 1403, configured to receive a control message from a receiving end; the control message is used to indicate an update of the compression cache; wherein, the control message includes any one of the updated compression cache, an identifier of the updated compression cache, and string information for indicating an update to the compression cache.

[0251] Optionally, the control message further includes second indication information, and the second indication information is used to indicate the sequence number of the first data packet compressed using the updated compression cache.

[0252] Optionally, the receiving unit 1403 is further configured to receive third indication information from the receiving end; the third indication information is used to indicate that the update type of the compression cache is semi-static cache update.

[0253] A processing unit 1401, specifically configured to update the compression cache according to the third indication information.

[0254] Optionally, the processing unit 1401 is specifically configured to determine that the update type of the compression cache is semi-static cache update according to the unacknowledged mode radio link control UM RLC entity associated with the bearer of the data packet to be sent; and update the compression cache according to the UM RLC entity.

[0255] The communication device 140 shown in the embodiments of the present application may execute the data processing method of the sending end in the embodiments shown in any of the above figures. The implementation principle and beneficial effects are similar to those of the data processing method of the sending end, and will not be described in detail here.

[0256] Figure 15Schematic diagram of another communication device 150 provided by an embodiment of this application. The communication device 150 is a sending end. For example, please refer to Figure 15 As shown, the communication device 150 may include:

[0257] A receiving unit 1501, configured to receive second indication information from a receiving end, where the second indication information is used to indicate the sequence number of the first data packet for which the communication device 150 performs compression using an updated compression cache.

[0258] A processing unit 1502, configured to update the compression cache; and compress the data packet to be sent according to the second indication information; where the compression cache used for compressing the data packet to be sent is the compression cache before update, or the compression cache used for compressing the data packet to be sent is the updated compression cache.

[0259] Optionally, the processing unit 1502 is configured to, if the sequence number of the data packet to be sent is greater than or equal to the sequence number indicated by the second indication information, use the updated compression cache to compress the data packet to be sent; if the sequence number of the data packet to be sent is less than the sequence number indicated by the second indication information, use the compression cache before update to compress the data packet to be sent.

[0260] Optionally, the receiving unit 1501 is configured to receive a control message from the receiving end; where the control message is used to indicate an update of the compression cache, and the control message includes the second indication information.

[0261] Optionally, the control message further includes any one of the updated compression cache, an identifier of the updated compression cache, and string information for indicating an update of the compression cache.

[0262] The communication device 150 shown in the embodiment of this application may execute the data processing method of the sending end in any of the embodiments shown in the above-mentioned drawings. The implementation principle and beneficial effects are similar to those of the data processing method of the sending end, and will not be elaborated here.

[0263] Figure 16 Schematic diagram of a communication device 160 provided by an embodiment of this application. The communication device 160 is a receiving end. For example, please refer to Figure 16 As shown, the communication device 160 may include:

[0264] A processing unit 1601, configured to update the compression cache.

[0265] A receiving unit 1602, configured to receive first indication information from a sending end; the first indication information is used to indicate a compression cache adopted by the sending end when compressing a data packet to be sent, the adopted compression cache is a compression cache before update, or the adopted compression cache is a compression cache after update.

[0266] Optionally, the first indication information is carried in the compressed data packet.

[0267] Optionally, the first indication information is carried in the protocol header of the compressed data packet, or the first indication information is carried in the data header of the compressed data packet.

[0268] Optionally, the first indication information is a field in the data packet to be sent. If the value of the field is the same as the value of the field in the previous data packet adjacent to the data packet to be sent received by the communication device 160, the adopted compression cache is the compression cache before update; if the value of the field is different from the value of the field in the previous data packet adjacent to the data packet to be sent received by the communication device 160, the adopted compression cache is the compression cache after update.

[0269] Optionally, the first indication information is a checksum field in the data packet to be sent, and the checksum field is determined according to the compression cache adopted when compressing the data packet to be sent.

[0270] Optionally, the communication device 160 may further include:

[0271] A sending unit 1603, configured to send a control message to the sending end; the control message is used to indicate an update of the compression cache; wherein, the control message includes any one of the updated compression cache, an identifier of the updated compression cache, and string information used to indicate an update of the compression cache.

[0272] Optionally, the control message further includes second indication information, and the second indication information is used to indicate a sequence number of the first data packet compressed by using the updated compression cache.

[0273] Optionally, the sending unit 1603 is further configured to send third indication information to the sending end; the third indication information is used to indicate that the update type of the compression cache is semi-static cache update, and to indicate that the sending end updates the compression cache according to the third indication information.

[0274] The communication device 160 shown in the embodiments of the present application may execute the data processing method of the receiving end in any of the embodiments shown in the above-mentioned drawings. The implementation principle and beneficial effects are similar to those of the data processing method of the receiving end, and will not be elaborated here.

[0275] Figure 17Schematic diagram of another communication device 170 provided by an embodiment of the present application. The communication device 170 is a receiving end. For example, please refer to Figure 17 As shown, the communication device 170 may include:

[0276] A processing unit 1701, configured to update the compression cache.

[0277] A sending unit 1702, configured to send second indication information to a sending end. The second indication information is used to indicate the sequence number of the first data packet for which the sending end uses the updated compression cache for compression, and to indicate that the sending end compresses the data packets to be sent according to the second indication information; wherein, when compressing the data packets to be sent, the compression cache used is the compression cache before the update, or, when compressing the data packets to be sent, the compression cache used is the updated compression cache.

[0278] Optionally, if the sequence number of the data packet to be sent is greater than or equal to the sequence number indicated by the second indication information, the compression cache used when compressing the data packet to be sent is the compression cache before the update; if the sequence number of the data packet to be sent is less than the sequence number indicated by the second indication information, the compression cache used when compressing the data packet to be sent is the updated compression cache.

[0279] Optionally, the sending unit 1702 is specifically configured to send a control message to the sending end; wherein, the control message is used to indicate an update of the compression cache, and the control message includes the second indication information.

[0280] Optionally, the control message further includes any one of the updated compression cache, an identifier of the updated compression cache, and string information used to indicate an update of the compression cache.

[0281] The communication device 170 shown in the embodiments of the present application may execute the data processing method of the receiving end in any of the embodiments shown in the above-mentioned drawings. Its implementation principle and beneficial effects are similar to those of the data processing method of the receiving end, and will not be elaborated here.

[0282] Figure 18 Schematic diagram of a communication device 180 provided by an embodiment of the present application. The device includes a processor 1801 and a memory 1802. A computer program is stored in the memory 1802. The processor 1801 executes the computer program stored in the memory 1802, so that the device executes the data processing method of the sending end in any of the embodiments shown in the above-mentioned drawings. Its implementation principle and beneficial effects are similar to those of the data processing method of the sending end, and will not be elaborated here.

[0283] Figure 19FIG. 0 is a schematic structural diagram of another communication device 190 provided by an embodiment of the present application. The device includes a processor 1901 and a memory 1902. A computer program is stored in the memory 1902. The processor 1901 executes the computer program stored in the memory 1902 so that the device executes the data processing method of the receiving end in the embodiment shown in any of the above-mentioned figures. The implementation principle and beneficial effects are similar to those of the data processing method of the receiving end, and will not be elaborated here.

[0284] An embodiment of the present application further provides a communication device, which may include: a processor and an interface circuit.

[0285] The interface circuit is configured to receive code instructions and transmit them to the processor.

[0286] The processor is configured to run the code instructions to execute the data processing method of the sending end in the embodiment shown in any of the above-mentioned figures. The implementation principle and beneficial effects are similar to those of the data processing method of the sending end, and will not be elaborated here.

[0287] An embodiment of the present application further provides a communication device, which may include: a processor and an interface circuit.

[0288] The interface circuit is configured to receive code instructions and transmit them to the processor.

[0289] The processor is configured to run the code instructions to execute the data processing method of the receiving end in the embodiment shown in any of the above-mentioned figures. The implementation principle and beneficial effects are similar to those of the data processing method of the receiving end, and will not be elaborated here.

[0290] An embodiment of the present application further provides a chip. A computer program is stored on the chip. When the computer program is executed by a processor, it executes the data processing method of the sending end in the embodiment shown in any of the above-mentioned figures. The implementation principle and beneficial effects are similar to those of the data processing method of the sending end, and will not be elaborated here.

[0291] An embodiment of the present application further provides a chip. A computer program is stored on the chip. When the computer program is executed by a processor, it executes the data processing method of the receiving end in the embodiment shown in any of the above-mentioned figures. The implementation principle and beneficial effects are similar to those of the data processing method of the receiving end, and will not be elaborated here.

[0292] The embodiments of the present application further provide a readable storage medium for storing instructions, which, when executed, implement the data processing method of the sending end in the embodiments shown in any of the above-mentioned drawings. The implementation principle and beneficial effects are similar to those of the data processing method of the sending end and will not be elaborated here.

[0293] The embodiments of the present application further provide a readable storage medium for storing instructions, which, when executed, implement the data processing method of the receiving end in the embodiments shown in any of the above-mentioned drawings. The implementation principle and beneficial effects are similar to those of the data processing method of the receiving end and will not be elaborated here.

[0294] The embodiments of the present application further provide a communication system, which may include the communication devices shown in any of the above Figure 14 and the communication devices shown in any of the above Figure 16 or the communication system may include the communication devices shown in any of the above Figure 15 and the communication devices shown in any of the above Figure 17 or the communication devices shown in any of the above Figure 18 and the communication devices shown in any of the above Figure 19 The implementation principle and beneficial effects are similar to those of the data processing method in the embodiments shown in any of the above-mentioned drawings and will not be elaborated here.

[0295] In the above embodiments, the processor may be a general-purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components. It can implement or execute the various methods, steps and logic block diagrams disclosed in the embodiments of the present application. The general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc. The steps of the method disclosed in combination with the embodiments of the present application may be directly embodied as being executed by a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software module may be located in a mature storage medium in the art such as a random access memory (RAM), a flash memory, a read-only memory (ROM), a programmable read-only memory or an electrically erasable programmable memory, a register, etc. This storage medium is located in the memory, and the processor reads the instructions in the memory and combines its hardware to complete the steps of the above method.

[0296] In several embodiments provided by the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the displayed or discussed couplings or direct couplings or communication connections to each other can be through some interfaces. The indirect couplings or communication connections of the devices or units can be in electrical, mechanical or other forms.

[0297] The units described as separate components may or may not be physically separated. The components displayed as units may or may not be physical units, that is, they may be located in one place or distributed to multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0298] In addition, in each embodiment of the present application, the functional units can be integrated in a processing unit, or each unit can exist physically alone, or two or more units can be integrated in one unit. The above integrated units can be implemented in the form of hardware or in the form of a combination of hardware and software functional units.

Claims

1. A data processing method, characterized in that, Including: Updating the compression cache; Compressing the data packet to be sent; Sending first indication information to the receiving end; The first indication information is used to indicate the compression cache adopted when compressing the data packet to be sent, the adopted compression cache is the compression cache before update, or the adopted compression cache is the compression cache after update; The method further includes: Receiving a control message from the receiving end; The control message includes second indication information, and the second indication information is used to indicate the sequence number of the first data packet compressed by using the compression cache after update.

2. The method according to claim 1, wherein The first indication information is carried in the compressed data packet.

3. The method according to claim 1, wherein The first indication information is a field in the data packet to be sent; If the value of the field is the same as the value of the field in the previous data packet adjacent to the data packet to be sent received by the receiving end, the adopted compression cache is the compression cache before update; If the value of the field is different from the value of the field in the previous data packet adjacent to the data packet to be sent received by the receiving end, the adopted compression cache is the compression cache after update.

4. The method according to any one of claims 1-3, characterized in that, The control message is further used to indicate updating the compression cache; wherein, the control message includes any one of the compression cache after update, the identifier of the compression cache after update, and string information for indicating updating the compression cache.

5. A data processing method, characterized in that, Including: Receiving second indication information from the receiving end, the second indication information is used to indicate the sequence number of the first data packet compressed by the sending end by using the compression cache after update; Updating the compression cache; Compressing the data packet to be sent according to the second indication information; wherein, the compression cache adopted when compressing the data packet to be sent is the compression cache before update, or the compression cache adopted when compressing the data packet to be sent is the compression cache after update.

6. The method according to claim 5, wherein The compressing the data packet to be sent according to the second indication information includes: If the sequence number of the data packet to be sent is greater than or equal to the sequence number indicated by the second indication information, using the compression cache after update to compress the data packet to be sent; If the sequence number of the data packet to be sent is less than the sequence number indicated by the second indication information, using the compression cache before update to compress the data packet to be sent.

7. The method according to claim 5 or 6, characterized in that, The receiving the second indication information from the receiving end includes: Receiving a control message from the receiving end; wherein, the control message is used to indicate updating the compression cache, and the control message includes the second indication information.

8. A data processing method, characterized in that, Including: Updating the compression cache; Receiving first indication information from the sending end; The first indication information is used to indicate the compression cache adopted by the sending end when compressing the data packet to be sent, the adopted compression cache is the compression cache before update, or the adopted compression cache is the compression cache after update; The method further includes: Send a control message to the sending end, where the control message includes second indication information for indicating the sequence number of the first data packet to be compressed using the updated compression cache.

9. The method according to claim 8, wherein The first indication information is carried in the compressed data packet.

10. The method according to claim 8, wherein The first indication information is a field in the data packet to be sent; If the value of the field is the same as the value of the field in the previous data packet adjacent to the data packet to be sent received by the receiving end, the compression cache used is the compression cache before the update; If the value of the field is different from the value of the field in the previous data packet adjacent to the data packet to be sent received by the receiving end, the compression cache used is the updated compression cache.

11. The method according to any one of claims 8-10, characterized in that, The control message is further used to indicate an update to the compression cache; wherein the control message includes any one of the updated compression cache, an identifier of the updated compression cache, and string information for indicating an update to the compression cache.

12. A data processing method, characterized in that, Includes: Update the compression cache; Send second indication information to the sending end, where the second indication information is used to indicate the sequence number of the first data packet to be compressed by the sending end using the updated compression cache, and to indicate that the sending end compresses the data packet to be sent according to the second indication information; wherein the compression cache used for compressing the data packet to be sent is the compression cache before the update, or the compression cache used for compressing the data packet to be sent is the updated compression cache.

13. The method according to claim 12, wherein If the sequence number of the data packet to be sent is greater than or equal to the sequence number indicated by the second indication information, the compression cache used for compressing the data packet to be sent is the updated compression cache; If the sequence number of the data packet to be sent is less than the sequence number indicated by the second indication information, the compression cache used for compressing the data packet to be sent is the compression cache before the update.

14. The method according to claim 12 or 13, characterized in that, The sending the second indication information to the sending end includes: Send a control message to the sending end; wherein the control message is used to indicate an update to the compression cache, and the control message includes the second indication information.

15. A communication device, characterized in that, Includes: A processing unit for updating the compression cache; And compressing the data packet to be sent; A sending unit for sending first indication information to the receiving end; The first indication information is used to indicate the compression cache used for compressing the data packet to be sent, and the compression cache used is the compression cache before the update, or the compression cache used is the updated compression cache; A receiving unit for receiving a control message from the receiving end; the control message includes second indication information for indicating the sequence number of the first data packet to be compressed using the updated compression cache.

16. The apparatus according to claim 15, wherein The first indication information is a field in the data packet to be sent. If the value of the field is the same as the value of the field in the previous data packet immediately adjacent to the data packet to be sent received by the receiving end, the compression cache used is the compression cache before the update; If the value of the field is different from the value of the field in the previous data packet immediately adjacent to the data packet to be sent received by the receiving end, the compression cache is the updated compression cache.

17. A communication device, characterized in that, Comprising: A receiving unit, configured to receive second indication information from a receiving end, where the second indication information is used to indicate the sequence number of the first data packet for which the communication device uses the updated compression cache for compression; A processing unit, configured to update the compression cache; and compress the data packet to be sent according to the second indication information; where the compression cache used when compressing the data packet to be sent is the compression cache before the update, or the compression cache used when compressing the data packet to be sent is the updated compression cache.

18. The device according to claim 17, wherein The processing unit is configured to, if the sequence number of the data packet to be sent is greater than or equal to the sequence number indicated by the second indication information, use the updated compression cache to compress the data packet to be sent; if the sequence number of the data packet to be sent is less than the sequence number indicated by the second indication information, use the compression cache before the update to compress the data packet to be sent.

19. A communication device, characterized in that, Comprising: A processing unit, configured to update the compression cache; A receiving unit, configured to receive first indication information from a sending end; The first indication information is used to indicate the compression cache used by the sending end when compressing the data packet to be sent, and the compression cache used is the compression cache before the update, or the compression cache used is the updated compression cache; A sending unit, configured to send, by the sending end, a control message, where the control message includes second indication information, and the second indication information is used to indicate the sequence number of the first data packet for which the updated compression cache is used for compression.

20. The device according to claim 19, wherein The first indication information is a field in the data packet to be sent. If the value of the field is the same as the value of the field in the previous data packet immediately adjacent to the data packet to be sent received by the communication device, the compression cache used is the compression cache before the update; If the value of the field is different from the value of the field in the previous data packet immediately adjacent to the data packet to be sent received by the communication device, the compression cache used is the updated compression cache.

21. A communication device, characterized in that, Comprising: A processing unit, configured to update the compression cache; A sending unit, configured to send second indication information to a sending end, where the second indication information is used to indicate a sequence number of a first data packet for which the sending end compresses using an updated compression buffer, and to indicate that the sending end compresses data packets to be sent according to the second indication information; wherein, when compressing the data packets to be sent, the compression buffer used is the compression buffer before update, or the compression buffer used when compressing the data packets to be sent is the updated compression buffer.

22. The apparatus according to claim 21, wherein if the sequence number of the data packet to be sent is greater than or equal to the sequence number indicated by the second indication information, then the compression buffer used when compressing the data packet to be sent is the updated compression buffer; if the sequence number of the data packet to be sent is less than the sequence number indicated by the second indication information, then the compression buffer used when compressing the data packet to be sent is the compression buffer before update.

23. A communication device, characterized in that, The apparatus includes a processor and a memory, where a computer program is stored in the memory, and the processor executes the computer program stored in the memory to enable the apparatus to execute the data processing method according to any one of claims 1 to 4; or, the processor executes the computer program stored in the memory to enable the apparatus to execute the data processing method according to any one of claims 5 to 7.

24. A communication device, characterized in that, The apparatus includes a processor and a memory, where a computer program is stored in the memory, and the processor executes the computer program stored in the memory to enable the apparatus to execute the data processing method according to any one of claims 8 to 11; or, the processor executes the computer program stored in the memory to enable the apparatus to execute the data processing method according to any one of claims 12 to 14.

25. A communication device, characterized in that, Comprising: a processor and an interface circuit; The interface circuit is configured to receive code instructions and transmit them to the processor; The processor is configured to run the code instructions to execute the data processing method according to any one of claims 1 to 4; or, configured to run the code instructions to execute the data processing method according to any one of claims 5 to 7.

26. A communication device, characterized in that, Comprising: a processor and an interface circuit; The interface circuit is configured to receive code instructions and transmit them to the processor; The processor is configured to run the code instructions to execute the data processing method according to any one of claims 8 to 11; or, configured to run the code instructions to execute the data processing method according to any one of claims 12 to 14.

27. A readable storage medium, characterized in that, For storing instructions, when the instructions are executed, the data processing method according to any one of claims 1 to 4 is implemented; or, when the instructions are executed, the data processing method according to any one of claims 5 to 7 is implemented; or, when the instructions are executed, the data processing method according to any one of claims 8 to 11 is implemented; or, when the instructions are executed, the data processing method according to any one of claims 12 to 14 is implemented.

28. A communication system, characterized in that, Comprising: The communication device according to claim 15 or 16 above and the communication device according to claim 17 or 18 above; or, the communication device according to claim 19 or 20 above and the communication device according to claim 21 or 22 above; or, the communication device according to claim 23 above and the communication device according to claim 24 above; or, the communication device according to claim 25 above and the communication device according to claim 26 above.

Images