A data compression method, device and storage medium

Abstract

The embodiment of the present application provides a data compression method, device and storage medium. The method is used for a data sending end, and the data sending end can carry multiple services on a wireless bearer, and each service corresponds to a compression cache, including: determining the first compression cache corresponding to the service to which the first data to be sent belongs; compressing the first data using the dictionary corresponding to the first compression cache to obtain compressed second data; encapsulating the second data in a setting message, and adding a compression identifier for indicating the first compression cache in the setting message; sending the setting message carrying the compression identifier to the data receiving end. Therefore, the embodiment of the present application improves the efficiency of data compression and realizes efficient transmission of multiple services.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a data compression method, device and storage medium. Background Art

[0002] In communication systems, compressing data before transmitting it is a common data transmission method.

[0003] The current data compression transmission method has only one compression / decompression buffer corresponding to one compression dictionary, and its compression efficiency is low.

[0004] Therefore, how to solve the problem of low data compression efficiency is a technical problem that needs to be solved at present. Summary of the invention

[0005] The embodiments of the present application provide a data compression method, device and storage medium to solve the defect of low data compression efficiency in the prior art and achieve efficient transmission of multiple services.

[0006] In a first aspect, an embodiment of the present application provides a data transmission method, which is used for a data sending end, where the data sending end can carry multiple services on a radio bearer, and each service corresponds to a compression cache, including:

[0007] Determine a first compression cache corresponding to a service to which first data to be sent belongs;

[0008] compressing the first data using the dictionary corresponding to the first compression cache to obtain compressed second data;

[0009] encapsulating the second data in a setting message, and adding a compression identifier for indicating the first compression cache in the setting message;

[0010] The setting message carrying the compression identifier is sent to a data receiving end.

[0011] Optionally, according to a data compression method according to an embodiment of the present application, the setting message is a Packet Data Convergence Protocol PDCP message;

[0012] The adding a compression identifier for indicating the first compression cache in the setting message includes:

[0013] The compression identifier is added to the PDCP header of the PDCP message.

[0014] Optionally, according to a data compression method of an embodiment of the present application, adding the compression identifier to the PDCP header of the PDCP message includes:

[0015] Determine a setting field in the PDCP header for carrying the compression flag;

[0016] The compression flag is added to the setting field.

[0017] Optionally, according to the data compression method of an embodiment of the present application, the compression identifier includes one or a combination of the following:

[0018] a compression cache identifier of the first compression cache;

[0019] A dictionary identifier of a dictionary corresponding to the first compression cache;

[0020] The service identifier of the service corresponding to the first compression cache.

[0021] Optionally, the data compression method according to an embodiment of the present application further includes:

[0022] Receiving a first message sent by a network side device, wherein the first message includes compression information configured by the network side device for a service that needs to be compressed;

[0023] A corresponding compression cache is established for the service that needs to be compressed according to the compression information.

[0024] Optionally, according to the data compression method of an embodiment of the present application, the compressed information includes one or a combination of the following:

[0025] Compression cache identifier and / or decompression cache identifier;

[0026] Dictionary ID;

[0027] compressing cache information and / or decompressing cache information;

[0028] Business logotype.

[0029] Optionally, the data compression method according to an embodiment of the present application further includes:

[0030] receiving a second message sent by a network side device, where the second message includes release information configured by the network side device for a service to be released;

[0031] The compressed cache corresponding to the service that needs to be released is released according to the release information.

[0032] Optionally, according to the data compression method of an embodiment of the present application, the release information includes one or a combination of the following:

[0033] Compression cache identifier and / or decompression cache identifier;

[0034] Dictionary ID;

[0035] Business logotype.

[0036] Optionally, the data compression method according to an embodiment of the present application further includes:

[0037] The dictionary content corresponding to the first compression cache is updated using the first data.

[0038] In a second aspect, an embodiment of the present application provides a data transmission method, which is used for a data receiving end, where the data receiving end can receive multiple compressed services carried on a wireless bearer, each service corresponding to a decompression buffer, including:

[0039] receiving a setting message carrying a compression identifier sent by a data sending end, where the compression identifier is used to indicate a first compression cache corresponding to a service to which the received first data belongs, and the setting message also includes second data obtained by compressing the first data by the data sending end using a dictionary corresponding to the first compression cache;

[0040] Determine, according to the compression identifier, a first decompression cache corresponding to the first compression cache;

[0041] The second data is decompressed using the dictionary in the first decompression buffer to obtain the first data.

[0042] Optionally, according to a data compression method according to an embodiment of the present application, the setting message is a Packet Data Convergence Protocol PDCP message;

[0043] The PDCP header of the PDCP message includes the compression identifier.

[0044] Optionally, according to a data compression method of an embodiment of the present application, the setting field in the PDCP header for carrying the compression identifier includes the compression identifier.

[0045] Optionally, according to the data compression method of an embodiment of the present application, the compression identifier includes one or a combination of the following:

[0046] a compression cache identifier of the first compression cache;

[0047] A dictionary identifier of a dictionary corresponding to the first compression cache;

[0048] The service identifier of the service corresponding to the first compression cache.

[0049] Optionally, the data compression method according to an embodiment of the present application further includes:

[0050] Receiving a first message sent by a network side device, wherein the first message includes compression information configured by the network side device for a service that needs to be compressed;

[0051] A corresponding decompression buffer is established for the service that needs to be compressed according to the compression information.

[0052] Optionally, according to the data compression method of an embodiment of the present application, the compression information includes one or a combination of the following:

[0053] Compression cache identifier and / or decompression cache identifier;

[0054] Dictionary ID;

[0055] compressing cache information and / or decompressing cache information;

[0056] Business logotype.

[0057] Optionally, the data compression method according to an embodiment of the present application further includes:

[0058] receiving a second message sent by a network side device, where the second message includes release information configured by the network side device for a service to be released;

[0059] The decompression buffer corresponding to the service to be released is released according to the release information.

[0060] Optionally, according to the data compression method of an embodiment of the present application, the release information includes one or a combination of the following:

[0061] Compression cache identifier and / or decompression cache identifier;

[0062] Dictionary ID;

[0063] Business logotype.

[0064] Optionally, the data compression method according to an embodiment of the present application further includes:

[0065] The dictionary content in the first decompression buffer is updated using the first data.

[0066] In a third aspect, an embodiment of the present application further provides a data compression device, characterized in that the data compression device can carry multiple services on a wireless bearer, each service corresponds to a compression cache, including a memory, a transceiver, and a processor:

[0067] A memory for storing a computer program; a transceiver for transmitting and receiving data under the control of the processor; and a processor for reading the computer program in the memory and performing the following operations:

[0068] Determine a first compression cache corresponding to a service to which first data to be sent belongs;

[0069] compressing the first data using the dictionary corresponding to the first compression cache to obtain compressed second data;

[0070] encapsulating the second data in a setting message, and adding a compression identifier for indicating the first compression cache in the setting message;

[0071] The setting message carrying the compression identifier is sent to a data receiving end.

[0072] Optionally, according to the data compression device of an embodiment of the present application, the setting message is a Packet Data Convergence Protocol PDCP message;

[0073] The adding a compression identifier for indicating the first compression cache in the setting message includes:

[0074] The compression identifier is added to the PDCP header of the PDCP message.

[0075] Optionally, according to the data compression device of an embodiment of the present application, the adding the compression identifier to the PDCP header of the PDCP message includes:

[0076] Determine a setting field in the PDCP header for carrying the compression flag;

[0077] The compression flag is added to the setting field.

[0078] Optionally, according to a data compression device of an embodiment of the present application, the compression identifier includes one or a combination of the following:

[0079] a compression cache identifier of the first compression cache;

[0080] A dictionary identifier of a dictionary corresponding to the first compression cache;

[0081] The service identifier of the service corresponding to the first compression cache.

[0082] Optionally, the data compression device according to an embodiment of the present application further includes:

[0083] Receiving a first message sent by a network side device, wherein the first message includes compression information configured by the network side device for a service that needs to be compressed;

[0084] A corresponding compression cache is established for the service that needs to be compressed according to the compression information.

[0085] Optionally, according to a data compression device of an embodiment of the present application, the compression information includes one or a combination of the following:

[0086] Compression cache identifier and / or decompression cache identifier;

[0087] Dictionary ID;

[0088] compressing cache information and / or decompressing cache information;

[0089] Business logotype.

[0090] Optionally, the data compression device according to an embodiment of the present application further includes:

[0091] receiving a second message sent by a network side device, where the second message includes release information configured by the network side device for a service to be released;

[0092] The compressed cache corresponding to the service that needs to be released is released according to the release information.

[0093] Optionally, according to a data compression device of an embodiment of the present application, the release information includes one or a combination of the following:

[0094] Compression cache identifier and / or decompression cache identifier;

[0095] Dictionary ID;

[0096] Business logotype.

[0097] Optionally, the data compression device according to an embodiment of the present application further includes:

[0098] The dictionary content corresponding to the first compression cache is updated using the first data.

[0099] In a fourth aspect, an embodiment of the present application further provides a data compression device, characterized in that the data compression device can receive multiple compressed services carried on a wireless bearer, each service corresponds to a decompression buffer, including a memory, a transceiver, and a processor:

[0100] A memory for storing a computer program; a transceiver for transmitting and receiving data under the control of the processor; and a processor for reading the computer program in the memory and performing the following operations:

[0101] receiving a setting message carrying a compression identifier sent by a data sending end, where the compression identifier is used to indicate a first compression cache corresponding to a service to which the received first data belongs, and the setting message also includes second data obtained by compressing the first data by the data sending end using a dictionary corresponding to the first compression cache;

[0102] Determine, according to the compression identifier, a first decompression cache corresponding to the first compression cache;

[0103] The second data is decompressed using the dictionary in the first decompression buffer to obtain the first data.

[0104] Optionally, according to the data compression device of an embodiment of the present application, the setting message is a Packet Data Convergence Protocol PDCP message;

[0105] The PDCP header of the PDCP message includes the compression identifier.

[0106] Optionally, according to a data compression device of an embodiment of the present application, the setting field in the PDCP header for carrying the compression identifier includes the compression identifier.

[0107] Optionally, according to a data compression device of an embodiment of the present application, the compression identifier includes one or a combination of the following:

[0108] a compression cache identifier of the first compression cache;

[0109] A dictionary identifier of a dictionary corresponding to the first compression cache;

[0110] The service identifier of the service corresponding to the first compression cache.

[0111] Optionally, the data compression device according to an embodiment of the present application further includes:

[0112] Receiving a first message sent by a network side device, wherein the first message includes compression information configured by the network side device for a service that needs to be compressed;

[0113] A corresponding decompression buffer is established for the service that needs to be compressed according to the compression information.

[0114] Optionally, according to a data compression device of an embodiment of the present application, the compression information includes one or a combination of the following:

[0115] Compression cache identifier and / or decompression cache identifier;

[0116] Dictionary ID;

[0117] compressing cache information and / or decompressing cache information;

[0118] Business logotype.

[0119] Optionally, the data compression device according to an embodiment of the present application further includes:

[0120] receiving a second message sent by a network side device, where the second message includes release information configured by the network side device for a service to be released;

[0121] The decompression buffer corresponding to the service to be released is released according to the release information.

[0122] Optionally, according to a data compression device of an embodiment of the present application, the release information includes one or a combination of the following:

[0123] Compression cache identifier and / or decompression cache identifier;

[0124] Dictionary ID;

[0125] Business logotype.

[0126] Optionally, the data compression device according to an embodiment of the present application further includes:

[0127] The dictionary content in the first decompression buffer is updated using the first data.

[0128] In a fifth aspect, an embodiment of the present application provides a data compression device, characterized in that the device is used for a data sending end, the data sending end can carry multiple services on a wireless bearer, each service corresponds to a compression buffer, including:

[0129] A compression cache determination module, used to determine a first compression cache corresponding to a service to which first data to be sent belongs;

[0130] a compression module, configured to compress the first data using a dictionary corresponding to the first compression cache to obtain compressed second data;

[0131] an encapsulation module, configured to encapsulate the second data in a setting message, and add a compression identifier for indicating the first compression cache in the setting message;

[0132] The sending module is used to send the setting message carrying the compression identifier to a data receiving end.

[0133] In a sixth aspect, an embodiment of the present application further provides a data compression device, characterized in that the device is used for a data receiving end, the data receiving end can receive multiple compressed services carried on a wireless bearer, each service corresponds to a decompression buffer, including:

[0134] a receiving module, configured to receive a setting message carrying a compression identifier sent by a data sending end, wherein the compression identifier is used to indicate a first compression cache corresponding to a service to which the received first data belongs, and the setting message also includes second data obtained by compressing the first data by the data sending end using a dictionary corresponding to the first compression cache;

[0135] a decompression cache determining module, configured to determine a first decompression cache corresponding to the first compression cache according to the compression identifier;

[0136] A decompression module is used to decompress the second data using the dictionary in the first decompression buffer to obtain the first data.

[0137] In the seventh aspect, an embodiment of the present application provides a processor-readable storage medium, characterized in that the processor-readable storage medium stores a computer program, and the computer program is used to enable the processor to execute the method described in the first aspect above, or the method described in the second aspect above.

[0138] The data compression method, device and storage medium provided by the embodiments of the present application determine a first compression cache corresponding to a service to which first data to be sent belongs; compress the first data using a dictionary corresponding to the first compression cache to obtain compressed second data; encapsulate the second data in a setting message, and add a compression identifier for indicating the first compression cache in the setting message; and send the setting message carrying the compression identifier to a data receiving end, thereby improving data compression efficiency and realizing efficient transmission of multiple services. BRIEF DESCRIPTION OF THE DRAWINGS

[0139] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, a brief introduction will be given below to the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0140] Figure 1 It is a flowchart of a data compression method provided in an embodiment of the present application;

[0141] Figure 2 This is an example diagram of a compressed cache provided in an embodiment of the present application;

[0142] Figure 3 is an example diagram of a compression cache indication provided by an embodiment of the present application;

[0143] Figure 4 is another example diagram of a compressed cache indication provided by an embodiment of the present application;

[0144] Figure 5 It is an information interaction diagram of configuring compressed information provided by an embodiment of the present application;

[0145] Figure 6 This is an information interaction diagram for releasing a compressed cache provided by an embodiment of the present application;

[0146] Figure 7 This is an example diagram of releasing a compressed cache provided by an embodiment of the present application;

[0147] Figure 8 It is a flowchart of a data compression method provided in an embodiment of the present application;

[0148] Fig. 9 is a structural schematic diagram of a data compression device provided in an embodiment of the present application;

[0149] Fig.10 is a structural schematic diagram of a data compression device provided in an embodiment of the present application;

[0150] Fig.11 is a structural schematic diagram of a data compression device provided in an embodiment of the present application;

[0151] Fig.12 It is a structural schematic diagram of a data compression device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0152] In the embodiments of the present application, the term "and / or" describes the association relationship of the associated objects, indicating that three relationships may exist. For example, A and / or B may represent: A exists alone, A and B exist at the same time, and B exists alone. The character " / " generally indicates that the associated objects before and after are in an "or" relationship.

[0153] In the embodiments of the present application, the term "plurality" refers to two or more than two, and other quantifiers are similar.

[0154] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0155] In the LTE (Long-Term Evolution) / LTE-A (Long-Term Evolution-Advance) system, the network can configure the UE (User Equipment) to use the UDC (Uplink Data Compression) function to compress the uplink data before transmission to reduce the air interface resource overhead.

[0156] When performing uplink compression, the UE can also use the preset dictionary content to compress the data to be transmitted, thereby further improving the compression efficiency; correspondingly, the base station side needs to decompress according to the preset dictionary content.

[0157] In the existing UDC mechanism, one RB (Radio Bearer) has only one compression / decompression cache, corresponding to one compression dictionary. If only one service is carried on the RB, there is no problem using one dictionary for compression and decompression. However, when multiple services are carried on the RB, multiple services use the same dictionary for compression and decompression. Since there is no correlation between the data of multiple services, the compression efficiency will be greatly reduced.

[0158] Currently, there is no mechanism for using multiple compression dictionaries and compression / decompression caches on a wireless bearer. This application provides a data compression method for a wireless bearer carrying multiple services, where multiple services transmitted on a bearer are compressed and decompressed using multiple dictionaries, thereby achieving efficient transmission of multiple services.

[0159] 1. UDC Compression Mechanism

[0160] 1. The sender maintains a compression cache, and the receiver maintains a decompression cache. Both the compression and decompression caches are first-in-first-out queues.

[0161] 2. Before sending data, the sender compresses the data to be sent:

[0162] (1) In the data packet to be sent, find the target field that meets the following characteristics:

[0163] The length exceeds the preset threshold;

[0164] The destination field is the same as a field in the compression buffer or before the destination field in this packet.

[0165] (2) If the target field is found, replace field A with the offset and length combination:

[0166] The offset is the position offset between the target field and the same field before the target field;

[0167] The length is the length of the target field;

[0168] Because the length of the offset and length combination is shorter than the length of the target field itself, a compression effect is achieved; in a data packet, there may be multiple fields that meet the above characteristics, and all of these fields can be compressed.

[0169] 3. The sender sends the compressed data packet to the peer end; at the same time, the corresponding original data packet (uncompressed data) is filled into the compression buffer:

[0170] 4. The receiving end decompresses the received data packet based on the offset and length in the packet and the decompression buffer; then, the decompressed data packet is filled into the decompression buffer.

[0171] Based on the above principle, when UDC is just started, the compression and decompression caches are empty, the probability of the compressor finding the target field in the current packet to be sent is low, and the compression efficiency is correspondingly low; after UDC runs for a period of time, the compression cache gradually increases, the probability of the compressor finding the target field in the current packet to be sent increases, and the compression efficiency is correspondingly improved.

[0172] In UDC, the transmitting end is a terminal and the receiving end is a base station.

[0173] 2. Compression mechanism based on preset dictionary

[0174] As an optimization of UDC, you can compile a preset dictionary for frequently appearing fields based on business characteristics and store them in the compression and decompression caches of the compression end and decompression end before starting UDC.

[0175] In this way, when UDC is just started, the compression and decompression caches are no longer empty, but contain preset dictionaries of high-frequency fields; this can effectively increase the probability of finding the target field and improve compression efficiency.

[0176] Obviously, in order to implement the above mechanism, before the UDC is started, the terminal and the base station need to respectively obtain the preset dictionary to be used, that is, complete the preset dictionary synchronization process.

[0177] In the existing UDC mechanism, one radio bearer (RB) has only one compression / decompression buffer, corresponding to one compression dictionary. If only one service is carried on the radio bearer, there is no problem in using one dictionary for compression and decompression. However, when multiple services are carried on the radio bearer, and multiple services use the same dictionary for compression and decompression, the compression efficiency will be greatly reduced because there is no correlation between the data of multiple services.

[0178] Therefore, the embodiments of the present application provide a data compression method, device, and storage medium, which improve data compression efficiency and achieve efficient transmission of multiple services.

[0179] Among them, the method and the device are based on the same application concept. Since the method and the device solve the problem in a similar principle, the implementation of the device and the method can refer to each other, and the repeated parts will not be repeated.

[0180] The technical solution provided in the embodiment of the present application can be applicable to a variety of systems, especially 5G systems. For example, the applicable system can be a global system of mobile communication (GSM) system, a code division multiple access (CDMA) system, a wideband code division multiple access (WCDMA) general packet radio service (GPRS) system, a long term evolution (LTE) system, a LTE frequency division duplex (FDD) system, a LTE time division duplex (TDD) system, an advanced long term evolution (LTE-A) system, a universal mobile telecommunication system (UMTS), a world-wide interoperability for microwave access (WiMAX) system, a 5G new air interface (NR) system, etc. These various systems include terminal equipment and network equipment. The system may also include a core network part, such as an evolved packet system (EPS), a 5G system (5GS), etc.

[0181] The terminal device involved in the embodiment of the present application may be a device that provides voice and / or data connectivity to a user, a handheld device with a wireless connection function, or other processing devices connected to a wireless modem. In different systems, the name of the terminal device may also be different. For example, in a 5G system, the terminal device may be called a user equipment (UE). A wireless terminal device can communicate with one or more core networks (CN) via a radio access network (RAN). The wireless terminal device may be a mobile terminal device, such as a mobile phone (or a "cellular" phone) and a computer with a mobile terminal device. For example, it may be a portable, pocket-sized, handheld, computer-built-in or vehicle-mounted mobile device that exchanges language and / or data with a wireless access network. For example, personal communication service (PCS) phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs) and other devices. The wireless terminal device may also be referred to as a system, a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, an access point, a remote terminal device, an access terminal device, a user terminal device, a user agent, and a user device, but is not limited in the embodiments of the present application.

[0182] The network device involved in the embodiment of the present application may be a base station, which may include multiple cells providing services for the terminal. Depending on the specific application scenario, the base station may also be called an access point, or may be a device in the access network that communicates with the wireless terminal device through one or more sectors on the air interface, or other names. The network device may be used to interchange received air frames with Internet Protocol (IP) packets, and serve as a router between the wireless terminal device and the rest of the access network, wherein the rest of the access network may include an Internet Protocol (IP) communication network. The network device may also coordinate the attribute management of the air interface. For example, the network device involved in the embodiments of the present application may be a network device (Base Transceiver Station, BTS) in the Global System for Mobile communications (Global System for Mobile communications, GSM) or Code Division Multiple Access (Code Division Multiple Access, CDMA), or a network device (NodeB) in Wide-band Code Division Multiple Access (WCDMA), or an evolutionary network device (evolutional Node B, eNB or e-NodeB) in the long term evolution (long term evolution, LTE) system, a 5G base station (gNB) in the 5G network architecture (next generation system), or a home evolved Node B (Home evolved Node B, HeNB), a relay node, a home base station (femto), a pico base station (pico), etc., which is not limited in the embodiments of the present application. In some network structures, the network device may include a centralized unit (CU) node and a distributed unit (DU) node, and the centralized unit and the distributed unit may also be arranged geographically separately.

[0183] The following is an explanation through specific embodiments.

[0184] Figure 1 is a schematic diagram of a data compression method provided in an embodiment of the present application, the method is used for a data sending end, the data sending end can carry multiple services on a wireless bearer, each service corresponds to a compression buffer; Figure 1 As shown, the data compression method comprises the following steps:

[0185] S101. Determine a first compression cache corresponding to a service to which first data to be sent belongs.

[0186] Specifically, the data sending end determines a first compression buffer corresponding to a service to which the first data to be sent belongs. The data sending end here may be a base station or a terminal.

[0187] For example, when the data sending end is a terminal, the terminal determines the first compression cache corresponding to the service to which the first data to be sent belongs; when the data sending end is a base station, the base station determines the first compression cache corresponding to the service to which the first data to be sent belongs.

[0188] S102: Compress the first data using a dictionary corresponding to the first compression cache to obtain compressed second data.

[0189] Specifically, the data sending end compresses the first data to be sent using a dictionary corresponding to a first compression cache corresponding to a service to which the first data belongs, to obtain compressed second data. The data sending end here may be a base station or a terminal.

[0190] For example: when the data sending end is a terminal, that is, the terminal uses the dictionary corresponding to the first compression cache corresponding to the service to which the first data belongs to compress the first data to be sent, and obtains compressed second data; when the data sending end is a base station, that is, the base station uses the dictionary corresponding to the first compression cache corresponding to the service to which the first data belongs to compress the first data to be sent, and obtains compressed second data.

[0191] The dictionary corresponding to the first compression cache may be located within the first compression cache, ie, a dictionary pre-loaded into the first compression cache; or may be located outside the first compression cache, ie, a dictionary pre-established with the first compression cache.

[0192] S103: Encapsulate the second data in a setting message, and add a compression identifier for indicating the first compression cache in the setting message.

[0193] Specifically, the data sending end encapsulates the compressed second data in a setting message, and adds a compression identifier for indicating the first compression buffer to be sent in the setting message. The data sending end here can be a base station or a terminal.

[0194] For example: when the data sending end is a terminal, the terminal encapsulates the compressed second data in a setting message, and adds a compression identifier for indicating the first compressed cache to be sent in the setting message; when the data sending end is a base station, the base station encapsulates the compressed second data in a setting message, and adds a compression identifier for indicating the first compressed cache to be sent in the setting message.

[0195] S104: Send a setting message carrying a compression flag to a data receiving end.

[0196] Specifically, the data sending end sends a setting message carrying a compression identifier for indicating the first compression cache to be sent to the data receiving end. The data sending end here can be a base station or a terminal. When the data sending end is a terminal, the data receiving end is a base station; when the data sending end is a base station, the data receiving end is a terminal.

[0197] For example: when the data sending end is a terminal, the terminal will send a setting message carrying a compression identifier for indicating the first compressed cache to be sent to the base station; when the data sending end is a base station, the terminal will send a setting message carrying a compression identifier for indicating the first compressed cache to be sent to the terminal.

[0198] In an exemplary scenario, Figure 2 As shown, it includes a data sending end and a data receiving end. The compressed data compression process between the data sending end and the data receiving end can be:

[0199] The data sending end and the data receiving end establish two radio bearers DRB (Date Radio Bearer) 0 and DRB1. DRB0 carries three services, corresponding to compression cache 0, compression cache 1 and compression cache 2 of DRB0 respectively. DRB1 carries two services, corresponding to compression cache 0 and compression cache 1 of DRB1 respectively.

[0200] Step 1: The data transmitter wants to send a data packet of service 0 of DRB0. The data transmitter finds compression buffer 0 of DRB0 according to the correspondence between the service and the compression buffer. The data packet of service 0 is compressed using the dictionary in compression buffer 0 of DRB0, and then the compressed data packet is encapsulated into a PDCP (Packet Data Convergence Protocol) PDU (Protocol Data Unit), and a compression-related field is added to the PDCP header, which includes a compression buffer identifier or a compression dictionary identifier or a service identifier of service 0. The PDCP PDU is transmitted to the RLC (Radio Link Control) layer.

[0201] Step 2: The RLC layer, MAC (Medium Access Control) and physical layer perform data transmission on the compressed data packet.

[0202] Step 3: The RLC layer at the data receiving end decodes the PDCP PDU, and maps the compressed data packet to DRB0 according to the channel mapping relationship and passes it to the PDCP layer.

[0203] Step 4: The PDCP layer at the data receiving end finds the decompression buffer 0 of DRB0 according to the compression buffer identifier or compression dictionary identifier in the PDCP header, uses the decompression buffer 0 of DRB0 to decompress the data packet, and updates the dictionary information in the decompression buffer 0 of DRB0.

[0204] Step 5: The PDCP layer at the data receiving end delivers the decompressed data packet to the upper layer.

[0205] Among them, the high layer may be (RRC (Radio Resource Control) layer, NAS (Non-Access-Stratum) layer, SDAP (Service Data Adaptation Protocol) layer, etc.

[0206] In addition to the compression cache identifier, compression dictionary identifier, or service identifier, the PDCP header may also have other identifiers, such as: Figure 3 or Figure 4 As shown, the PDCP header in the existing mechanism contains fields such as SN (Serial Number), FU (Flag of UDC), FR (Flag of Reset), Checksum, etc. Among them, FU indicates whether this data packet is compressed by the UDC protocol, and the value "1" indicates that the data packet is compressed by the UDC protocol; FR: indicates whether the UDC compression cache is reset. The value "1" indicates that this is the first compressed packet after the UDC cache is reset. Checksum means that this field contains the verification bit of the compressed cache buffer content: before the current data packet is placed in the cache buffer, the checksum is calculated based on the content of the current compressed cache buffer.

[0207] The operations of steps 1 to 5 are performed on each data packet to be transmitted, and the dictionary in the compression cache corresponding to the service is used to perform compression and decompression to complete the compressed transmission of the data.

[0208] It can be seen from the above embodiments that by determining the first compression cache corresponding to the service to which the first data to be sent belongs; compressing the first data using the dictionary corresponding to the first compression cache to obtain compressed second data; encapsulating the second data in a setting message, and adding a compression identifier for indicating the first compression cache in the setting message; and sending the setting message carrying the compression identifier to the data receiving end, the efficiency of data compression is improved and efficient transmission of multiple services is achieved.

[0209] In an optional embodiment, the setting message in S103 may be a PDCP message. When the compression identifier for indicating the first compression cache is added to the setting message in S103, the following implementations may be included but are not limited to:

[0210] S1031. Add a compression identifier for indicating a first compression buffer corresponding to a service to which the first data belongs to a PDCP header of the PDCP message.

[0211] Specifically, the compression identifier of the first compression cache may include one of the following or a combination thereof:

[0212] a compression cache identifier of the first compression cache;

[0213] A dictionary identifier of a dictionary corresponding to the first compression cache;

[0214] The service identifier of the service corresponding to the first compression cache.

[0215] It can be seen from the above embodiments that by adding a compression identifier for indicating the first compression cache corresponding to the service to which the first data belongs to the PDCP header of the PDCP message, the reliability of the transmission of the compression identifier can be improved.

[0216] In an optional embodiment, when performing the above S1031, the following implementations may be included but are not limited to:

[0217] Determine a setting field in a PDCP header for carrying the compression flag;

[0218] Add the compression flag in the settings field.

[0219] Specifically, the setting field may be a reserved field in the PDCP header, such as Figure 3 The buffer ID (BufferIdentity buffer sequence number) shown in the figure can also be a new field in the PDCP header, such as Figure 4 The buffer ID is shown. Figure 3 and Figure 4 This is only a specific example and does not constitute a limitation on the embodiments of the present application. That is, the setting field in the embodiments of the present application may be located at but not limited to Figure 3 or Figure 4 The location of the buffer ID shown.

[0220] in, Figure 3 The reserved bits are used directly to carry the buffer ID (Buffer Identity). Figure 4It adds a new byte to carry the buffer ID (BufferIdentity) in the PDCP header (Packet Data Convergence Protocol header). And, Figure 3 or Figure 4 The fields included are:

[0221] D / C (Data / Control) field;

[0222] R (Reserve) field;

[0223] SN (Serial Number) field;

[0224] FU (Flag of UDC, uplink data compression indication) field;

[0225] FR (Flag of Reset, reset indication) field;

[0226] Buffer ID (Buffer Identity) field;

[0227] Checksum field;

[0228] Oct (byte) field.

[0229] The compression flag can be set in Figure 3 or Figure 4 The location of the buffer ID field in .

[0230] In addition, the compression flag added to the setting field may include one or a combination of the following:

[0231] a compression cache identifier of the first compression cache;

[0232] A dictionary identifier of a dictionary corresponding to the first compression cache;

[0233] The service identifier of the service corresponding to the first compression cache.

[0234] It can be seen from the above embodiments that by adding a compression flag to the setting field of the PDCP header of the PDCP message, the flexibility and diversity of the compression flag transmission are enriched.

[0235] In an optional embodiment, the compression identifier used to indicate the first compression cache corresponding to the service to which the first data belongs in S103 may include one of the following or a combination thereof:

[0236] A compression cache identifier of a first compression cache corresponding to the service to which the first data belongs;

[0237] A dictionary identifier of a dictionary corresponding to a first compression cache corresponding to a service to which the first data belongs;

[0238] A service identifier of a service corresponding to the first compression cache corresponding to the service to which the first data belongs.

[0239] Specifically, for example, the compression identifier used to indicate the first compression cache corresponding to the service to which the first data belongs may include:

[0240] A compression cache identifier of a first compression cache corresponding to the service to which the first data belongs; or

[0241] A dictionary identifier of a dictionary corresponding to a first compression cache corresponding to a service to which the first data belongs; or

[0242] A service identifier of a service corresponding to the first compression cache corresponding to the service to which the first data belongs.

[0243] For another example, the compression identifier used to indicate the first compression cache corresponding to the service to which the first data belongs may include:

[0244] The compression cache identifier of the first compression cache corresponding to the service to which the first data belongs and the dictionary identifier of the dictionary corresponding to the first compression cache corresponding to the service to which the first data belongs; or

[0245] a compression cache identifier of a first compression cache corresponding to a service to which the first data belongs and a service identifier of a service corresponding to the first compression cache corresponding to the service to which the first data belongs; or

[0246] The dictionary identifier of the dictionary corresponding to the first compression cache corresponding to the service to which the first data belongs and the service identifier of the service corresponding to the first compression cache corresponding to the service to which the first data belongs.

[0247] For another example, the compression identifier used to indicate the first compression cache corresponding to the service to which the first data belongs may include:

[0248] A compression cache identifier of a first compression cache corresponding to the service to which the first data belongs; and

[0249] A dictionary identifier of a dictionary corresponding to a first compression cache corresponding to a service to which the first data belongs; and

[0250] A service identifier of a service corresponding to the first compression cache corresponding to the service to which the first data belongs.

[0251] In an optional embodiment, the data compression method may further include:

[0252] S105. Receive a first message sent by a network side device, where the first message includes compression information configured by the network side device for a service that needs to be compressed;

[0253] S106: Create a corresponding compression cache for the service that needs to be compressed according to the compression information.

[0254] Specifically, when the data receiving end receives the compression information configured by the network side device for the service that needs to be compressed, it can establish a corresponding compression cache for the service that needs to be compressed according to the compression information, and load the corresponding dictionary into the compression cache. When the data sending end is a terminal and the data receiving end is a base station, the network side device can be a base station.

[0255] Furthermore, the above S105 and S106 may be executed by establishing a compression cache in advance for each service that needs to be compressed before S101, and then determining a first compression cache corresponding to the service to which the first data to be sent belongs in step S101.

[0256] In an exemplary scenario, Figure 5 As shown, it includes a terminal, a base station and a core network. Among them, the compression information configuration process between the base station and the core network includes the steps of:

[0257] S1. Establish an RRC (Radio Resource Control) connection between the terminal and the base station. If the terminal is in a connected state, skip this step.

[0258] S2. The terminal initiates a PDU (Protocol Data Unit) establishment request to the core network, and the request includes service information QoS (Quality of Service) information.

[0259] S3. The core network determines to establish a PDU connection for the terminal, establishes a connection for the terminal between the base station and the core network, and sends a PDU session (session control) establishment acceptance message to the base station, while notifying the base station of corresponding service information (eg, QoS information).

[0260] S4. The base station configures the radio bearer and other information for the terminal, including the compressed information corresponding to the service. The information is sent to the terminal via a control plane message (e.g., an RRC reconfiguration message). The compressed information may include one or a combination of the following:

[0261] (1) Compression cache identifier and / or decompression cache identifier;

[0262] (2) Dictionary identification;

[0263] (3) compressing cache information and / or decompressing cache information (e.g., cache size);

[0264] (4)Business identification.

[0265] S5: After receiving the configuration information, the terminal establishes a compression cache for the corresponding service according to the compression information in the configuration signaling, loads the corresponding dictionary, and feeds back an RRC configuration completion message to the base station.

[0266] The multiple service configuration process repeats steps S2 to S5. The base station configures the radio bearer according to the service characteristics and can map multiple services to the same or different radio bearers. When multiple services are carried out simultaneously, each service will initiate its own PDU session establishment process, and then the base station uses RRC reconfiguration to configure the service to the appropriate RB.

[0267] It can be seen from the above embodiments that by receiving the first message sent by the network side device, the first message includes the compression information configured by the network side device for the service that needs to be compressed; and establishing a corresponding compression cache for the service that needs to be compressed according to the compression information, and loading the corresponding dictionary into the compression cache, so that it is convenient to directly use the dictionary in the compression cache for compression in the future, thereby improving the efficiency of data compression.

[0268] In an optional embodiment, the compression information configured by the network side device for the service to be compressed in the above S105 may include one or a combination of the following:

[0269] a. Compression cache identifier and / or decompression cache identifier;

[0270] b. Dictionary identification;

[0271] c. compress cache information and / or decompress cache information (e.g., cache size);

[0272] d. Business logo.

[0273] Specifically, the compression information configured by the network side device for the service that needs to be compressed may include:

[0274] The first case: a. Compression cache identifier and / or decompression cache identifier; or

[0275] b. Dictionary mark; or

[0276] c. compressing cache information and / or decompressing cache information; or

[0277] d. Business logo.

[0278] The second situation: a. compression cache identifier and / or decompression cache identifier; and

[0279] b. Dictionary identifier.

[0280] The third situation: a. compression cache identifier and / or decompression cache identifier; and

[0281] c. Compress cache information and / or decompress cache information.

[0282] Fourth situation: a. compression cache identifier and / or decompression cache identifier; and

[0283] d. Business logo.

[0284] The fifth case: b. Dictionary mark; and

[0285] c. Compress cache information and / or decompress cache information.

[0286] The sixth case: b. Dictionary mark; and

[0287] d. Business logo.

[0288] The seventh situation: c. compressing the cache information and / or decompressing the cache information; and

[0289] d. Business logo.

[0290] The eighth situation: a. compression cache identifier and / or decompression cache identifier; and

[0291] b. dictionary identification; and

[0292] c. compress cache information and / or decompress cache information;

[0293] The ninth situation: a. Compression cache identifier and / or decompression cache identifier;

[0294] and b, dictionary identification;

[0295] and d. business identity.

[0296] The tenth situation: a. compression cache identifier, decompression cache identifier, compression cache identifier and decompression cache identifier; and

[0297] c. compressing cache information and / or decompressing cache information; and

[0298] d. Business logo.

[0299] Case 11: b. Dictionary mark; and

[0300] c. compressing cache information and / or decompressing cache information; and

[0301] d. Business logo.

[0302] Case 12: a. Compression cache identifier and / or decompression cache identifier; and

[0303] b. dictionary identification; and

[0304] c. compressing cache information and / or decompressing cache information; and

[0305] d. Business logo.

[0306] In addition, the cache size in the above compression cache information and / or decompression cache information may refer to the amount of dictionary information that can be stored in the cache. The sending and receiving ends use the dictionary in the cache to compress and decompress the data. The larger the dictionary, the higher the compression rate.

[0307] In an optional embodiment, the data compression method may further include:

[0308] S107. Receive a second message sent by the network side device, where the second message includes release information configured by the network side device for the service to be released;

[0309] S108: Release the compression cache corresponding to the service that needs to be released according to the release information.

[0310] Specifically, when the data receiving end receives the release information for the service configuration to be released sent by the network side device, the compressed cache corresponding to the service to be released can be released according to the release information. Wherein, when the data sending end is a terminal, the network side device can be a base station.

[0311] Furthermore, the above S107 and S108 may be executed before S101 or after S104.

[0312] In an exemplary scenario, Figure 6 As shown, it includes a terminal, a base station and a core network. Among them, the compression cache release process between the terminal, the base station and the core network includes the steps of:

[0313] S1: The core network determines to release the PDU connection of a service of the terminal, sends a PDU session release message to the base station, and notifies the base station of the corresponding service information (such as QoS information).

[0314] S2: The base station reconfigures the radio bearer and other information for the terminal, including the compression cache identifier or compression dictionary identifier corresponding to the released service (for example: release Figure 2 2) and sends the compressed cache of DRB0 in the RRC reconfiguration message to the terminal.

[0315] S3: After receiving the configuration information, the terminal releases the compression cache of the corresponding service according to the configuration information in the configuration signaling (for example: release Figure 2 The compression cache of DRB0 in 2) feeds back a configuration completion message to the base station.

[0316] For example, the bearer and compression cache configuration of the data sender before release is as follows: Figure 2 shown; released Figure 2 After DRB0 compression cache 2 is in place, the bearer and compression cache configuration of the data sender is as follows Figure 7shown.

[0317] It can be seen from the above embodiments that by receiving the second message sent by the network side device, the second message includes the release information configured by the network side device for the service to be released, and releasing the compressed cache corresponding to the service to be released according to the release information, thereby avoiding resource waste and improving resource utilization.

[0318] In an optional embodiment, the release information configured by the network side device for the service to be released in the above S107 includes one or a combination of the following:

[0319] a. Compression cache identifier and / or decompression cache identifier;

[0320] b. Dictionary identification;

[0321] c. Business logo.

[0322] Specifically, the release information configured by the network side device for the service to be released includes the following:

[0323] The first case: a. Compression cache identifier and / or decompression cache identifier.

[0324] The second situation: b. Dictionary identification.

[0325] The third situation: c. Business identification.

[0326] Fourth situation: a. compression cache identifier and / or decompression cache identifier; and

[0327] b. Dictionary identifier.

[0328] The fifth case: b. Dictionary mark; and

[0329] c. Business logo.

[0330] The sixth situation: a. compression cache identifier and / or decompression cache identifier; and

[0331] c. Business logo.

[0332] The seventh situation: a. compression cache identifier and / or decompression cache identifier; and

[0333] b. dictionary identification; and

[0334] c. Business logo.

[0335] In an optional embodiment, the data compression method may further include:

[0336] S109: Use the first data to update dictionary content corresponding to the first compression cache corresponding to the service to which the first data belongs.

[0337] Specifically, the first data is data before compression.

[0338] Herein, updating the dictionary content means updating the dictionary information after each compression, and updating the cached dictionary according to the first data. The specific updating method may be directly using a first-in-first-out method to replace old data with new data.

[0339] It can be seen from the above embodiments that the data sending end can carry multiple services on a wireless bearer, each service corresponds to a compression cache, by determining the first compression cache corresponding to the service to which the first data to be sent belongs; compressing the first data using the dictionary corresponding to the first compression cache to obtain compressed second data; encapsulating the second data in a setting message, and adding a compression identifier for indicating the first compression cache in the setting message; sending the setting message carrying the compression identifier to the data receiving end, thereby improving data compression efficiency and achieving efficient transmission of multiple services.

[0340] Figure 8 is a schematic diagram of a data compression method provided in an embodiment of the present application, the method is used for a data receiving end, the data receiving end can receive multiple compressed services carried on a wireless bearer, each service corresponds to a decompression buffer; Figure 8 As shown, the data compression method may include the following steps:

[0341] S801. Receive a setting message carrying a compression identifier sent by a data sending end, where the compression identifier is used to indicate a first compression cache corresponding to a service to which the received first data belongs. The setting message also includes second data obtained by compressing the first data by the data sending end using a dictionary corresponding to the first compression cache.

[0342] Specifically, the data receiving end receives a setting message carrying a compression identifier sent by the data sending end, the compression identifier is used to indicate a first compression cache corresponding to a service to which the received first data belongs, and the setting message carrying the compression identifier sent by the data sending end also includes second data obtained by the data sending end compressing the first data received by the receiving end using a dictionary corresponding to the first compression cache corresponding to the service to which the first data belongs. The data receiving end here can be a base station or a terminal.

[0343] For example: the base station receives a setting message carrying a compression identifier sent by the terminal, where the compression identifier is used to indicate a first compression cache corresponding to a service to which the received first data belongs. The setting message carrying the compression identifier sent by the base station also includes second data obtained by the terminal compressing the first data received by the base station using a dictionary corresponding to the first compression cache corresponding to the service to which the first data belongs.

[0344] The terminal receives a setting message carrying a compression identifier sent by a base station, where the compression identifier is used to indicate a first compression cache corresponding to a service to which the received first data belongs. The setting message carrying the compression identifier sent by the terminal also includes second data obtained by compressing the first data received by the terminal using a dictionary corresponding to the first compression cache corresponding to the service to which the first data belongs.

[0345] S802: Determine a first decompression cache corresponding to the first compression cache according to the compression identifier.

[0346] Specifically, the data receiving end determines the first decompression buffer corresponding to the first compression buffer corresponding to the service to which the first data belongs according to the compression identifier. The data receiving end here can be a base station or a terminal.

[0347] For example: the base station determines, according to the compression identifier, a first decompression cache corresponding to a first compression cache corresponding to a service to which the first data belongs;

[0348] The terminal determines, according to the compression identifier, a first decompression cache corresponding to a first compression cache corresponding to a service to which the first data belongs.

[0349] S803: Decompress the second data using the dictionary in the first decompression buffer to obtain the first data.

[0350] Specifically, the data receiving end decompresses the second data compressed by the first data received by the receiving end using the dictionary in the first decompression buffer corresponding to the service to which the first data belongs, to obtain the first data received by the receiving end. The data receiving end here can be a base station or a terminal.

[0351] For example, the base station decompresses the second data compressed by the first data received by the base station using the dictionary in the first decompression buffer corresponding to the service to which the first data belongs, to obtain the first data received by the base station;

[0352] The terminal decompresses the second data compressed by the first data received by the terminal using the dictionary in the first decompression buffer corresponding to the service to which the first data belongs, to obtain the first data received by the terminal.

[0353] For example: In an exemplary scenario, as described above Figure 2 As shown, it includes a data sending end and a data receiving end. The compressed data compression process between the data sending end and the data receiving end is not described here.

[0354] It can be seen from the above embodiments that by receiving a setting message carrying a compression identifier sent by a data sending end, the compression identifier is used to indicate a first compression cache corresponding to a service to which the received first data belongs, and the setting message also includes second data after the data sending end compresses the first data using a dictionary corresponding to the first compression cache, determines the first decompression cache corresponding to the first compression cache according to the compression identifier, and decompresses the second data using the dictionary in the first decompression cache to obtain the first data, thereby improving the efficiency of data compression and achieving efficient transmission of multiple services.

[0355] In an optional embodiment, the setting message in the above S801 may be a PDCP message, and the PDCP header of the PDCP message includes a compression identifier for indicating a first compression buffer corresponding to a service to which the received first data belongs.

[0356] The compression identifier of the first compression cache may include one or a combination of the following:

[0357] a compression cache identifier of the first compression cache;

[0358] A dictionary identifier of a dictionary corresponding to the first compression cache;

[0359] The service identifier of the service corresponding to the first compression cache.

[0360] Correspondingly, when executing S201, the data receiving end may obtain the compression identifier from the PDCP header of the PDCP message after receiving the PDCP message.

[0361] It can be seen from the above embodiments that after receiving the PDCP message, obtaining the compression identifier from the PDCP header of the PDCP message can improve the reliability of the compression identifier transmission.

[0362] In an optional embodiment, the setting message in the above S801 may be a PDCP message, and the setting field of the PDCP header of the PDCP message includes compression information of the first compression buffer corresponding to the service to which the received first data belongs.

[0363] Correspondingly, when executing S201, the data receiving end may obtain the compression flag from the setting field of the PDCP header of the PDCP message after receiving the PDCP message.

[0364] Specifically, the setting field may be a reserved field in the PDCP header, as described above. Figure 3 The buffer ID (Buffer Identity) is located at the location shown; it can also be a new field in the PDCP header, as mentioned above Figure 4 The buffer ID is shown.

[0365] The compression flag can be set in the above Figure 3 or above Figure 4 The location of the buffer ID field in .

[0366] In addition, the compression flag added to the setting field may include one or a combination of the following:

[0367] a compression cache identifier of the first compression cache;

[0368] A dictionary identifier of a dictionary corresponding to the first compression cache;

[0369] The service identifier of the service corresponding to the first compression cache.

[0370] It can be seen from the above embodiments that after receiving the PDCP message, the compression flag is obtained from the setting field of the PDCP header of the PDCP message, which can enrich the flexibility and diversity of obtaining the compression flag.

[0371] In an optional embodiment, the compression identifier used to indicate the first compression cache corresponding to the service to which the first data belongs in S801 may include one of the following or a combination thereof:

[0372] A compression cache identifier of a first compression cache corresponding to the service to which the first data belongs;

[0373] A dictionary identifier of a dictionary corresponding to a first compression cache corresponding to a service to which the first data belongs;

[0374] A service identifier of a service corresponding to the first compression cache corresponding to the service to which the first data belongs.

[0375] Specifically, for example, the compression identifier used to indicate the first compression cache corresponding to the service to which the first data belongs may include:

[0376] A compression cache identifier of a first compression cache corresponding to the service to which the first data belongs; or

[0377] A dictionary identifier of a dictionary corresponding to a first compression cache corresponding to a service to which the first data belongs; or

[0378] A service identifier of a service corresponding to the first compression cache corresponding to the service to which the first data belongs.

[0379] For another example, the compression identifier used to indicate the first compression cache corresponding to the service to which the first data belongs may include:

[0380] The compression cache identifier of the first compression cache corresponding to the service to which the first data belongs and the dictionary identifier of the dictionary corresponding to the first compression cache corresponding to the service to which the first data belongs; or

[0381] a compression cache identifier of a first compression cache corresponding to a service to which the first data belongs and a service identifier of a service corresponding to the first compression cache corresponding to the service to which the first data belongs; or

[0382] The dictionary identifier of the dictionary corresponding to the first compression cache corresponding to the service to which the first data belongs and the service identifier of the service corresponding to the first compression cache corresponding to the service to which the first data belongs.

[0383] For another example, the compression identifier used to indicate the first compression cache corresponding to the service to which the first data belongs may include:

[0384] A compression cache identifier of a first compression cache corresponding to the service to which the first data belongs; and

[0385] A dictionary identifier of a dictionary corresponding to a first compression cache corresponding to a service to which the first data belongs; and

[0386] A service identifier of a service corresponding to the first compression cache corresponding to the service to which the first data belongs.

[0387] In an optional embodiment, the data compression method may further include:

[0388] S804: Receive a first message sent by a network side device, where the first message includes compression information configured by the network side device for a service that needs to be compressed;

[0389] S805: Establish a corresponding decompression cache for the service that needs to be compressed according to the compression information.

[0390] Specifically, when the data receiving end receives the compression information configured by the network side device for the service that needs to be compressed, it can establish a corresponding decompression cache for the service that needs to be compressed according to the compression information, and load the corresponding dictionary into the decompression cache. When the data sending end is a terminal and the data receiving end is a base station, the network side device can be a base station.

[0391] Furthermore, the above S804 and S805 may be executed before S801.

[0392] In an exemplary scenario, as described above Figure 5 As shown, it includes a terminal, a base station and a core network. Among them, the compression information configuration process between the base station and the core network includes the above Figure 5 In addition to S1 to S5, it also includes:

[0393] The base station establishes a corresponding decompression buffer for the service that needs to be compressed according to the compression information, and loads a corresponding dictionary into the decompression buffer.

[0394] It can be seen from the above embodiments that by receiving the first message sent by the network side device, the first message includes the compression information configured by the network side device for the service that needs to be compressed; and establishing a corresponding decompression cache for the service that needs to be compressed according to the compression information, it is convenient to directly use the dictionary in the decompression cache for decompression in the subsequent process, thereby improving the efficiency of data decompression and meeting the data decompression requirements of multiple services.

[0395] In an optional embodiment, the compression information configured by the network side device for the service to be compressed in the above S804 may include one or a combination of the following:

[0396] a. Compression cache identifier and / or decompression cache identifier;

[0397] b. Dictionary identification;

[0398] c. compress cache information and / or decompress cache information;

[0399] d. Business logo.

[0400] In an optional embodiment, the data compression method may further include:

[0401] S806. Receive a second message sent by the network side device, where the second message includes release information configured by the network side device for the service to be released;

[0402] S807: Release the decompression buffer corresponding to the service to be released according to the release information.

[0403] Specifically, when the data receiving end receives the second message sent by the network side device, and the second message includes the release information configured by the network side device for the service to be released, the decompression cache corresponding to the service to be released can be released according to the release information. When the data sending end is a terminal and the data receiving end is a base station, the network side device can be a base station.

[0404] Furthermore, the above S806 and S807 may be executed before S801 or after S803.

[0405] In an exemplary scenario, as described above Figure 6 As shown, it includes a terminal, a base station and a core network. Among them, the compression cache release process between the terminal, the base station and the core network includes the above Figure 6 In addition to S1 to S3, it also includes:

[0406] The base station releases the decompression buffer corresponding to the service to be released according to the release information (for example: release Figure 2 Decompression cache of DRB0 in 2).

[0407] For example, the bearer and decompression buffer configuration of the data receiving end before release is as follows Figure 2 shown; released Figure 2 After the decompression cache 2 of DRB0, the bearer and decompression cache configuration of the data receiving end is as follows Figure 7 shown.

[0408] In an optional embodiment, the release information configured by the network side device for the service to be released in S806 includes one or a combination of the following:

[0409] a. Compression cache identifier and / or decompression cache identifier;

[0410] b. Dictionary identification;

[0411] c. Business logo.

[0412] In an optional embodiment, the data compression method may further include:

[0413] S808: Use the first data to update the dictionary content in the first decompression buffer corresponding to the service to which the first data belongs.

[0414] Specifically, the first data is decompressed data.

[0415] Herein, updating the dictionary content means updating the dictionary information after each decompression, and updating the cached dictionary according to the first data. The specific updating method may be directly replacing the old data with the new data in a first-in-first-out manner.

[0416] It can be seen from the above embodiments that the data receiving end can carry multiple services on one wireless bearer, each service corresponds to a compression cache, by determining the first compression cache corresponding to the service to which the first data to be sent belongs; using the dictionary corresponding to the first compression cache to compress the first data to obtain compressed second data; encapsulating the second data in a setting message, and adding a compression identifier for indicating the first compression cache in the setting message; sending the setting message carrying the compression identifier to the data receiving end, thereby improving data compression efficiency and achieving efficient transmission of multiple services.

[0417] Fig. 9 It is a structural diagram of a data compression device provided in an embodiment of the present application, which can carry multiple services on a wireless bearer, each service corresponds to a compression cache, including a memory 920, a transceiver 900, and a processor 910.

[0418] Among them, Fig. 9In the embodiment, the bus architecture may include any number of interconnected buses and bridges, specifically one or more processors represented by processor 910 and various circuits of memory represented by memory 920 are linked together. The bus architecture may also link together various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and are therefore not further described herein. The bus interface provides an interface. The transceiver 900 may be a plurality of components, namely, a transmitter and a receiver, providing a unit for communicating with various other devices on a transmission medium, which transmission medium may include a wireless channel, a wired channel, an optical cable, and other transmission media. The processor 910 is responsible for managing the bus architecture and general processing, and the memory 920 may store data used by the processor 910 when performing operations.

[0419] The processor 910 may be a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or a complex programmable logic device (CPLD). The processor may also adopt a multi-core architecture.

[0420] The memory 920 is used to store computer programs; the transceiver 900 is used to send and receive data under the control of the processor; the processor 910 is used to read the computer program in the memory and perform the following operations:

[0421] Determine a first compression cache corresponding to a service to which first data to be sent belongs;

[0422] compressing the first data using the dictionary corresponding to the first compression cache to obtain compressed second data;

[0423] encapsulating the second data in a setting message, and adding a compression identifier for indicating the first compression cache in the setting message;

[0424] The setting message carrying the compression identifier is sent to a data receiving end.

[0425] Optionally, according to the data compression device of an embodiment of the present application, the setting message is a Packet Data Convergence Protocol PDCP message;

[0426] The adding a compression identifier for indicating the first compression cache in the setting message includes:

[0427] The compression identifier is added to the PDCP header of the PDCP message.

[0428] Optionally, according to the data compression device of an embodiment of the present application, the adding the compression identifier to the PDCP header of the PDCP message includes:

[0429] Determine a setting field in the PDCP header for carrying the compression flag;

[0430] The compression flag is added to the setting field.

[0431] Optionally, according to a data compression device of an embodiment of the present application, the compression identifier includes one or a combination of the following:

[0432] a compression cache identifier of the first compression cache;

[0433] A dictionary identifier of a dictionary corresponding to the first compression cache;

[0434] The service identifier of the service corresponding to the first compression cache.

[0435] Optionally, the data compression device according to an embodiment of the present application further includes:

[0436] Receiving a first message sent by a network side device, wherein the first message includes compression information configured by the network side device for a service that needs to be compressed;

[0437] A corresponding compression cache is established for the service that needs to be compressed according to the compression information.

[0438] Optionally, according to a data compression device of an embodiment of the present application, the compression information includes one or a combination of the following:

[0439] Compression cache identifier and / or decompression cache identifier;

[0440] Dictionary ID;

[0441] compressing cache information and / or decompressing cache information;

[0442] Business logotype.

[0443] Optionally, the data compression device according to an embodiment of the present application further includes:

[0444] receiving a second message sent by a network side device, where the second message includes release information configured by the network side device for a service to be released;

[0445] The compressed cache corresponding to the service that needs to be released is released according to the release information.

[0446] Optionally, according to a data compression device of an embodiment of the present application, the release information includes one or a combination of the following:

[0447] Compression cache identifier and / or decompression cache identifier;

[0448] Dictionary ID;

[0449] Business logotype.

[0450] Optionally, the data compression device according to an embodiment of the present application further includes:

[0451] The dictionary content corresponding to the first compression cache is updated using the first data.

[0452] It can be seen from the above embodiments that the data compression device is capable of carrying multiple services on a wireless bearer, each service corresponding to a compression cache, by determining the first compression cache corresponding to the service to which the first data to be sent belongs; compressing the first data using the dictionary corresponding to the first compression cache to obtain compressed second data; encapsulating the second data in a setting message, and adding a compression identifier for indicating the first compression cache in the setting message; sending the setting message carrying the compression identifier to the data receiving end, thereby improving data compression efficiency and achieving efficient transmission of multiple services.

[0453] Fig.10 It is a structural diagram of a data compression device provided in an embodiment of the present application, which can carry multiple services on a wireless bearer, each service corresponds to a compression cache, and includes a memory 1020, a transceiver 1000, and a processor 1010.

[0454] Among them, Fig.10 In the embodiment, the bus architecture may include any number of interconnected buses and bridges, specifically linking together various circuits of one or more processors represented by processor 1010 and memory represented by memory 1020. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art and are therefore not further described herein. The bus interface provides an interface. The transceiver 1000 may be a plurality of components, namely, a transmitter and a receiver, providing a unit for communicating with various other devices on a transmission medium, which transmission medium may include a wireless channel, a wired channel, an optical cable, and the like. The processor 1010 is responsible for managing the bus architecture and general processing, and the memory 1020 may store data used by the processor 1010 when performing operations.

[0455] The processor 3100 may be a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or a complex programmable logic device (CPLD). The processor may also adopt a multi-core architecture.

[0456] The memory 1020 is used to store computer programs; the transceiver 1000 is used to send and receive data under the control of the processor; the processor 1010 is used to read the computer program in the memory and perform the following operations:

[0457] receiving a setting message carrying a compression identifier sent by a data sending end, where the compression identifier is used to indicate a first compression cache corresponding to a service to which the received first data belongs, and the setting message also includes second data obtained by compressing the first data by the data sending end using a dictionary corresponding to the first compression cache;

[0458] Determine, according to the compression identifier, a first decompression cache corresponding to the first compression cache;

[0459] The second data is decompressed using the dictionary in the first decompression buffer to obtain the first data.

[0460] Optionally, the data compression device according to an embodiment of the present application further includes:

[0461] The setting message is a Packet Data Convergence Protocol PDCP message;

[0462] The PDCP header of the PDCP message includes the compression identifier.

[0463] Optionally, the data compression device according to an embodiment of the present application further includes:

[0464] The setting field in the PDCP header for carrying the compression flag includes the compression flag.

[0465] Optionally, the data compression device according to an embodiment of the present application further includes:

[0466] The compression identifier includes one or a combination of the following:

[0467] a compression cache identifier of the first compression cache;

[0468] A dictionary identifier of a dictionary corresponding to the first compression cache;

[0469] The service identifier of the service corresponding to the first compression cache.

[0470] Optionally, the data compression device according to an embodiment of the present application further includes:

[0471] Receiving a first message sent by a network side device, wherein the first message includes compression information configured by the network side device for a service that needs to be compressed;

[0472] A corresponding decompression buffer is established for the service that needs to be compressed according to the compression information.

[0473] Optionally, according to a data compression device of an embodiment of the present application, the compression information includes one or a combination of the following:

[0474] Compression cache identifier and / or decompression cache identifier;

[0475] Dictionary ID;

[0476] compressing cache information and / or decompressing cache information;

[0477] Business logotype.

[0478] Optionally, the data compression device according to an embodiment of the present application further includes:

[0479] receiving a second message sent by a network side device, where the second message includes release information configured by the network side device for a service to be released;

[0480] The decompression buffer corresponding to the service to be released is released according to the release information.

[0481] Optionally, according to a data compression device of an embodiment of the present application, the release information includes one or a combination of the following:

[0482] Compression cache identifier and / or decompression cache identifier;

[0483] Dictionary ID;

[0484] Business logotype.

[0485] Optionally, the data compression device according to an embodiment of the present application further includes:

[0486] The dictionary content in the first decompression buffer is updated using the first data.

[0487] It can be seen from the above embodiments that the data compression device is capable of receiving multiple compressed services carried on a wireless bearer, each service corresponding to a decompression cache, by receiving a setting message carrying a compression identifier sent by a data sending end, the compression identifier is used to indicate the first compression cache corresponding to the service to which the received first data belongs, and the setting message also includes second data obtained by the data sending end compressing the first data using the dictionary corresponding to the first compression cache; determining the first decompression cache corresponding to the first compression cache according to the compression identifier; and decompressing the second data using the dictionary in the first decompression cache to obtain the first data, thereby improving data compression efficiency and achieving efficient transmission of multiple services.

[0488] It should be noted here that the above-mentioned device provided in the embodiment of the present application can implement all the method steps implemented in the above-mentioned method embodiment, and can achieve the same technical effect. The parts and beneficial effects of this embodiment that are the same as those in the method embodiment will not be described in detail here.

[0489] Fig.11 1 is a schematic diagram of a data compression device provided in an embodiment of the present application. The device is used for a data sending end, and the data sending end can carry multiple services on a wireless bearer, and each service corresponds to a compression buffer, including:

[0490] A compression cache determining module 111, configured to determine a first compression cache corresponding to a service to which first data to be sent belongs;

[0491] A compression module 112, configured to compress the first data using a dictionary corresponding to the first compression cache to obtain compressed second data;

[0492] An encapsulation module 113, configured to encapsulate the second data in a setting message, and add a compression identifier for indicating the first compression cache in the setting message;

[0493] The sending module 114 is configured to send the setting message carrying the compression identifier to a data receiving end.

[0494] Optionally, based on the above device, the message is set to be a Packet Data Convergence Protocol (PDCP) message; the encapsulation module 113 includes:

[0495] The adding a compression identifier for indicating the first compression cache in the setting message includes:

[0496] The compression identifier is added to the PDCP header of the PDCP message.

[0497] Optionally, based on the above device, the encapsulation module 113 includes:

[0498] The adding the compression identifier to the PDCP header of the PDCP message includes:

[0499] Determine a setting field in the PDCP header for carrying the compression flag;

[0500] The compression flag is added to the setting field.

[0501] Optionally, based on the above device, the encapsulation module 113 includes:

[0502] The compression identifier includes one or a combination of the following:

[0503] First compression identification submodule: a compression cache identification of the first compression cache;

[0504] Second compression identification submodule: dictionary identification of the dictionary corresponding to the first compression cache;

[0505] The third compression identification submodule: a service identification of the service corresponding to the first compression cache.

[0506] Optionally, based on the above device, the compression cache determination module 111 further includes:

[0507] Receiving a first message sent by a network side device, wherein the first message includes compression information configured by the network side device for a service that needs to be compressed;

[0508] A corresponding compression cache is established for the service that needs to be compressed according to the compression information.

[0509] Optionally, based on the above device, the compression cache determination module 111 further includes:

[0510] The compressed information includes one or a combination of the following:

[0511] First compression information submodule: compression cache identifier and / or decompression cache identifier;

[0512] Second compression information submodule: dictionary identification;

[0513] The third compression information submodule is used to compress the cache information and / or decompress the cache information;

[0514] The fourth compressed information submodule: business identification.

[0515] Optionally, based on the above device, the compression cache determination module 111 further includes:

[0516] receiving a second message sent by a network side device, where the second message includes release information configured by the network side device for a service to be released;

[0517] The compressed cache corresponding to the service that needs to be released is released according to the release information.

[0518] Optionally, based on the above device, the compression cache determination module 111 further includes:

[0519] The release information includes one or a combination of the following:

[0520] First release information submodule: compression cache identifier and / or decompression cache identifier;

[0521] Second release information submodule: dictionary identification;

[0522] The third release information submodule: service identification.

[0523] Optionally, based on the above device, the compression cache determination module 111 further includes: using the first data to update the dictionary content corresponding to the first compression cache.

[0524] As can be seen from the above embodiments, a data compression device is used for a data sending end, and the data sending end can carry multiple services on a wireless bearer, and each service corresponds to a compression cache, including: a compression cache determination module, used to determine the first compression cache corresponding to the service to which the first data to be sent belongs; a compression module, used to compress the first data using the dictionary corresponding to the first compression cache to obtain compressed second data; an encapsulation module, used to encapsulate the second data in a setting message, and add a compression identifier for indicating the first compression cache in the setting message; a sending module, used to send the setting message carrying the compression identifier to the data receiving end. Therefore, the embodiment of the present application improves the data compression efficiency and realizes efficient transmission of multiple services.

[0525] Fig.12 1 is a schematic diagram of a data compression device provided in an embodiment of the present application. The device is used at a data receiving end, and the data receiving end can receive multiple compressed services carried on a wireless bearer, and each service corresponds to a decompression buffer, including:

[0526] A receiving module 121 is configured to receive a setting message carrying a compression identifier sent by a data sending end, wherein the compression identifier is used to indicate a first compression cache corresponding to a service to which the received first data belongs, and the setting message also includes second data obtained by compressing the first data by the data sending end using a dictionary corresponding to the first compression cache;

[0527] A decompression cache determining module 122, configured to determine a first decompression cache corresponding to the first compression cache according to the compression identifier;

[0528] The decompression module 123 is configured to decompress the second data using the dictionary in the first decompression buffer to obtain the first data.

[0529] Optionally, based on the above device, the receiving module 121 further includes: the setting message is a Packet Data Convergence Protocol PDCP message;

[0530] The PDCP header of the PDCP message includes the compression identifier.

[0531] Optionally, based on the above device, the receiving module 121 further includes:

[0532] The setting field in the PDCP header for carrying the compression flag includes the compression flag.

[0533] Optionally, based on the above device, the receiving module 121 further includes:

[0534] The compression identifier includes one or a combination of the following:

[0535] First compression identification submodule: a compression cache identification of the first compression cache;

[0536] Second compression identification submodule: dictionary identification of the dictionary corresponding to the first compression cache;

[0537] The third compression identification submodule: a service identification of the service corresponding to the first compression cache.

[0538] Optionally, based on the above device, the receiving module 121 further includes:

[0539] Receiving a first message sent by a network side device, wherein the first message includes compression information configured by the network side device for a service that needs to be compressed;

[0540] A corresponding decompression buffer is established for the service that needs to be compressed according to the compression information.

[0541] Optionally, based on the above device, the receiving module 121 further includes:

[0542] The compressed information includes one or a combination of the following:

[0543] First compression information submodule: compression cache identifier and / or decompression cache identifier;

[0544] Second compression information submodule: dictionary identification;

[0545] The third compression information submodule is used to compress the cache information and / or decompress the cache information;

[0546] The fourth compressed information submodule: business identification.

[0547] Optionally, based on the above device, the receiving module 121 further includes:

[0548] receiving a second message sent by a network side device, where the second message includes release information configured by the network side device for a service to be released;

[0549] The decompression buffer corresponding to the service to be released is released according to the release information.

[0550] Optionally, based on the above device, the receiving module 121 further includes:

[0551] The release information includes one or a combination of the following:

[0552] First release information submodule: compression cache identifier and / or decompression cache identifier;

[0553] Second release information submodule: dictionary identification;

[0554] The third release information submodule: service identification.

[0555] Optionally, based on the above device, the receiving module 121 further includes:

[0556] The dictionary content in the first decompression buffer is updated using the first data.

[0557] As can be seen from the above embodiments, a signal transmission device is used for a data receiving end, and the data receiving end can receive multiple compressed services carried on a wireless bearer, and each service corresponds to a decompression cache, including: a receiving module, which is used to receive a setting message carrying a compression identifier sent by a data sending end, and the compression identifier is used to indicate the first compression cache corresponding to the service to which the received first data belongs, and the setting message also includes the second data after the data sending end compresses the first data using the dictionary corresponding to the first compression cache; a decompression cache determination module, which is used to determine the first decompression cache corresponding to the first compression cache according to the compression identifier; a decompression module, which is used to decompress the second data using the dictionary in the first decompression cache to obtain the first data. Therefore, the embodiment of the present application improves the data compression efficiency and realizes efficient transmission of multiple services.

[0558] It should be noted that the division of units in the embodiments of the present application is schematic and is only a logical function division. There may be other division methods in actual implementation. In addition, each functional unit in each embodiment of the present application may be integrated into a processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0559] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a processor-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, server, or network device, etc.) or a processor (processor) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), disk or optical disk and other media that can store program codes.

[0560] It should be noted here that the above-mentioned device provided in the embodiment of the present application can implement all the method steps implemented in the above-mentioned method embodiment, and can achieve the same technical effect. The parts and beneficial effects of this embodiment that are the same as those in the method embodiment will not be described in detail here.

[0561] On the other hand, an embodiment of the present application further provides a processor-readable storage medium, wherein the processor-readable storage medium stores a computer program, wherein the computer program is used to enable the processor to execute a method for a data sending end or a method for a data receiving end.

[0562] The processor-readable storage medium can be any available medium or data storage device that can be accessed by the processor, including but not limited to magnetic storage (such as floppy disks, hard disks, magnetic tapes, magneto-optical disks (MO), etc.), optical storage (such as CD, DVD, BD, HVD, etc.), and semiconductor storage (such as ROM, EPROM, EEPROM, non-volatile memory (NANDFLASH), solid-state drive (SSD)), etc.

[0563] As can be seen from the above embodiments, the processor-readable storage medium stores a computer program, and the computer program is used to enable the processor to execute the above data compression method. Therefore, the embodiments of the present application improve the data compression efficiency and realize the efficient transmission of multiple services.

[0564] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage and optical storage, etc.) that contain computer-usable program code.

[0565] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer executable instructions. These computer executable instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0566] These processor executable instructions may also be stored in a processor readable memory that can direct a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the processor readable memory produce an article of manufacture including an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0567] These processor-executable instructions may also be loaded onto a computer or other programmable data processing device so that a series of operational steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for executing on the computer or other programmable device to implement the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0568] Obviously, those skilled in the art can make various changes and modifications to the present application without departing from the spirit and scope of the present application. Thus, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is also intended to include these modifications and variations.

Claims

1. A data compression method, characterized in that: The method is used for a data transmitting end, where the data transmitting end can carry multiple services on a wireless bearer, and each service corresponds to a compression buffer, and includes: Determine a first compression cache corresponding to a service to which first data to be sent belongs; compressing the first data using the dictionary corresponding to the first compression cache to obtain compressed second data; encapsulating the second data in a setting message, and adding a compression identifier for indicating the first compression cache in the setting message; Sending the setting message carrying the compression identifier to a data receiving end; The method further comprises: receiving a second message sent by a network side device, where the second message includes release information configured by the network side device for a service to be released; The compressed cache corresponding to the service that needs to be released is released according to the release information.

2. The method according to claim 1, characterized in that The setting message is a Packet Data Convergence Protocol PDCP message; The adding a compression identifier for indicating the first compression cache in the setting message includes: The compression identifier is added to the PDCP header of the PDCP message.

3. The method according to claim 2, characterized in that The adding the compression identifier to the PDCP header of the PDCP message includes: Determine a setting field in the PDCP header for carrying the compression flag; Add the compression flag in the setting field.

4. The method according to any one of claims 1 to 3, characterized in that: The compression identifier includes one or a combination of the following: a compression cache identifier of the first compression cache; A dictionary identifier of a dictionary corresponding to the first compression cache; The service identifier of the service corresponding to the first compression cache.

5. The method according to claim 1, characterized in that Also includes: Receiving a first message sent by a network side device, wherein the first message includes compression information configured by the network side device for a service that needs to be compressed; A corresponding compression cache is established for the service that needs to be compressed according to the compression information.

6. The method according to claim 5, characterized in that The compressed information includes one or a combination of the following: Compression cache identifier and / or decompression cache identifier; Dictionary ID; compressing cache information and / or decompressing cache information; Business logotype.

7. The method according to claim 1, characterized in that The release information includes one or a combination of the following: Compression cache identifier and / or decompression cache identifier; Dictionary ID; Business logotype.

8. The method according to claim 1, characterized in that: Also includes: The dictionary content corresponding to the first compression cache is updated using the first data.

9. A data compression method, characterized in that: The method is used for a data receiving end, the data receiving end can receive multiple compressed services carried on a wireless bearer, each service corresponds to a decompression buffer, and includes: receiving a setting message carrying a compression identifier sent by a data sending end, where the compression identifier is used to indicate a first compression cache corresponding to a service to which the received first data belongs, and the setting message also includes second data obtained by compressing the first data by the data sending end using a dictionary corresponding to the first compression cache; Determine, according to the compression identifier, a first decompression cache corresponding to the first compression cache; Decompressing the second data using the dictionary corresponding to the first decompression cache to obtain the first data; The method further comprises: receiving a second message sent by a network side device, where the second message includes release information configured by the network side device for a service to be released; The decompression buffer corresponding to the service to be released is released according to the release information.

10. The method according to claim 9, characterized in that The setting message is a Packet Data Convergence Protocol PDCP message; The PDCP header of the PDCP message includes the compression identifier.

11. The method according to claim 10, characterized in that The setting field in the PDCP header for carrying the compression flag includes the compression flag.

12. The method according to any one of claims 9 to 11, characterized in that: The compression identifier includes one or a combination of the following: a compression cache identifier of the first compression cache; A dictionary identifier of a dictionary corresponding to the first compression cache; The service identifier of the service corresponding to the first compression cache.

13. The method according to claim 9, characterized in that Also includes: Receiving a first message sent by a network side device, wherein the first message includes compression information configured by the network side device for a service that needs to be compressed; A corresponding decompression buffer is established for the service that needs to be compressed according to the compression information.

14. The method according to claim 13, characterized in that The compressed information includes one or a combination of the following: Compression cache identifier and / or decompression cache identifier; Dictionary ID; compressing cache information and / or decompressing cache information; Business logotype.

15. The method according to claim 9, characterized in that The release information includes one or a combination of the following: Compression cache identifier and / or decompression cache identifier; Dictionary ID; Business logotype.

16. The method according to claim 9, characterized in that Also includes: The dictionary content corresponding to the first decompression cache is updated using the first data.

17. A data compression device, characterized in that: The data compression device can carry multiple services on one wireless bearer, each service corresponds to a compression buffer, including a memory, a transceiver, and a processor: Memory for storing computer programs; a transceiver, for transmitting and receiving data under the control of the processor; A processor is configured to read the computer program in the memory and perform the following operations: Determine a first compression cache corresponding to a service to which first data to be sent belongs; compressing the first data using the dictionary corresponding to the first compression cache to obtain compressed second data; encapsulating the second data in a setting message, and adding a compression identifier for indicating the first compression cache in the setting message; Sending the setting message carrying the compression identifier to a data receiving end; The processor is further configured to perform the following operations: receiving a second message sent by a network side device, where the second message includes release information configured by the network side device for a service to be released; The compressed cache corresponding to the service that needs to be released is released according to the release information.

18. The device according to claim 17, characterized in that The setting message is a Packet Data Convergence Protocol PDCP message; The adding a compression identifier for indicating the first compression cache in the setting message includes: The compression identifier is added to the PDCP header of the PDCP message.

19. The device according to claim 18, characterized in that The adding the compression identifier to the PDCP header of the PDCP message includes: Determine a setting field in the PDCP header for carrying the compression flag; Add the compression flag in the setting field.

20. The device according to any one of claims 17 to 19, characterized in that The compression identifier includes one or a combination of the following: a compression cache identifier of the first compression cache; A dictionary identifier of a dictionary corresponding to the first compression cache; The service identifier of the service corresponding to the first compression cache.

21. The device according to claim 17, characterized in that Also includes: Receiving a first message sent by a network side device, wherein the first message includes compression information configured by the network side device for a service that needs to be compressed; A corresponding compression cache is established for the service that needs to be compressed according to the compression information.

22. The device according to claim 21, characterized in that The compressed information includes one or a combination of the following: Compression cache identifier and / or decompression cache identifier; Dictionary ID; compressing cache information and / or decompressing cache information; Business logotype.

23. The device according to claim 17, characterized in that The release information includes one or a combination of the following: Compression cache identifier and / or decompression cache identifier; Dictionary ID; Business logotype.

24. The device according to claim 17, characterized in that Also includes: The dictionary content corresponding to the first compression cache is updated using the first data.

25. A data compression device, characterized in that: The data compression device can receive multiple compressed services carried on a wireless bearer, each service corresponds to a decompression buffer, and includes a memory, a transceiver, and a processor: Memory for storing computer programs; a transceiver, for transmitting and receiving data under the control of the processor; A processor is configured to read the computer program in the memory and perform the following operations: receiving a setting message carrying a compression identifier sent by a data sending end, where the compression identifier is used to indicate a first compression cache corresponding to a service to which the received first data belongs, and the setting message also includes second data obtained by compressing the first data by the data sending end using a dictionary corresponding to the first compression cache; Determine, according to the compression identifier, a first decompression cache corresponding to the first compression cache; Decompressing the second data using the dictionary corresponding to the first decompression cache to obtain the first data; The processor is further configured to perform the following operations: receiving a second message sent by a network side device, where the second message includes release information configured by the network side device for a service to be released; The decompression buffer corresponding to the service to be released is released according to the release information.

26. The device according to claim 25, characterized in that The setting message is a Packet Data Convergence Protocol PDCP message; The PDCP header of the PDCP message includes the compression identifier.

27. The device according to claim 26, characterized in that The setting field in the PDCP header for carrying the compression flag includes the compression flag.

28. The device according to any one of claims 25 to 27, characterized in that The compression identifier includes one or a combination of the following: a compression cache identifier of the first compression cache; A dictionary identifier of a dictionary corresponding to the first compression cache; The service identifier of the service corresponding to the first compression cache.

29. The device according to claim 25, characterized in that Also includes: Receiving a first message sent by a network side device, wherein the first message includes compression information configured by the network side device for a service that needs to be compressed; A corresponding decompression buffer is established for the service that needs to be compressed according to the compression information.

30. The device according to claim 29, characterized in that The compressed information includes one or a combination of the following: Compression cache identifier and / or decompression cache identifier; Dictionary ID; compressing cache information and / or decompressing cache information; Business logotype.

31. The device according to claim 25, characterized in that The release information includes one or a combination of the following: Compression cache identifier and / or decompression cache identifier; Dictionary ID; Business logotype.

32. The device according to claim 25, characterized in that Also includes: The dictionary content corresponding to the first decompression cache is updated using the first data.

33. A data compression device, characterized in that: The device is used for a data transmitting end, and the data transmitting end can carry multiple services on a wireless bearer, and each service corresponds to a compression buffer, including: A compression cache determination module, used to determine a first compression cache corresponding to a service to which first data to be sent belongs; a compression module, configured to compress the first data using a dictionary corresponding to the first compression cache to obtain compressed second data; an encapsulation module, configured to encapsulate the second data in a setting message, and add a compression identifier for indicating the first compression cache in the setting message; A sending module, used for sending the setting message carrying the compression identifier to a data receiving end; The compression cache determination module is further used to receive a second message sent by the network side device, where the second message includes release information configured by the network side device for the service to be released; The compressed cache corresponding to the service that needs to be released is released according to the release information.

34. A signal transmission device, characterized in that: The device is used for a data receiving end, and the data receiving end can receive multiple compressed services carried on a wireless bearer, and each service corresponds to a decompression buffer, including: a receiving module, configured to receive a setting message carrying a compression identifier sent by a data sending end, wherein the compression identifier is used to indicate a first compression cache corresponding to a service to which the received first data belongs, and wherein the setting message also includes second data obtained by compressing the first data by the data sending end using a dictionary corresponding to the first compression cache; a decompression cache determining module, configured to determine a first decompression cache corresponding to the first compression cache according to the compression identifier; a decompression module, configured to decompress the second data using the dictionary corresponding to the first decompression buffer to obtain the first data; The receiving module is further used to receive a second message sent by the network side device, where the second message includes release information configured by the network side device for the service to be released; The decompression buffer corresponding to the service to be released is released according to the release information.

35. A processor-readable storage medium, characterized in that: The processor-readable storage medium stores a computer program, and the computer program is used to enable the processor to execute the method according to any one of claims 1 to 7, or any one of claims 8 to 16.

Images