WO2011085632A1 - 互联网协议数据包的压缩及解压缩方法和装置 - Google Patents
互联网协议数据包的压缩及解压缩方法和装置 Download PDFInfo
- Publication number
- WO2011085632A1 WO2011085632A1 PCT/CN2010/080574 CN2010080574W WO2011085632A1 WO 2011085632 A1 WO2011085632 A1 WO 2011085632A1 CN 2010080574 W CN2010080574 W CN 2010080574W WO 2011085632 A1 WO2011085632 A1 WO 2011085632A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- compression algorithm
- identifier
- data packet
- compression
- data
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W28/00—Network traffic management; Network resource management
- H04W28/02—Traffic management, e.g. flow control or congestion control
- H04W28/06—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information
-
- H—ELECTRICITY
- H03—ELECTRONIC CIRCUITRY
- H03M—CODING; DECODING; CODE CONVERSION IN GENERAL
- H03M7/00—Conversion of a code where information is represented by a given sequence or number of digits to a code where the same, similar or subset of information is represented by a different sequence or number of digits
- H03M7/30—Compression; Expansion; Suppression of unnecessary data, e.g. redundancy reduction
- H03M7/3084—Compression; Expansion; Suppression of unnecessary data, e.g. redundancy reduction using adaptive string matching, e.g. the Lempel-Ziv method
-
- H—ELECTRICITY
- H03—ELECTRONIC CIRCUITRY
- H03M—CODING; DECODING; CODE CONVERSION IN GENERAL
- H03M7/00—Conversion of a code where information is represented by a given sequence or number of digits to a code where the same, similar or subset of information is represented by a different sequence or number of digits
- H03M7/30—Compression; Expansion; Suppression of unnecessary data, e.g. redundancy reduction
- H03M7/60—General implementation details not specific to a particular type of compression
- H03M7/6011—Encoder aspects
-
- H—ELECTRICITY
- H03—ELECTRONIC CIRCUITRY
- H03M—CODING; DECODING; CODE CONVERSION IN GENERAL
- H03M7/00—Conversion of a code where information is represented by a given sequence or number of digits to a code where the same, similar or subset of information is represented by a different sequence or number of digits
- H03M7/30—Compression; Expansion; Suppression of unnecessary data, e.g. redundancy reduction
- H03M7/60—General implementation details not specific to a particular type of compression
- H03M7/6064—Selection of Compressor
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/04—Protocols for data compression, e.g. ROHC
Definitions
- the embodiments of the present invention relate to the field of communications technologies, and in particular, to a method and an apparatus for compressing and decompressing IP data packets. Background technique
- IP data packets are usually compressed and processed to save air interface resources.
- the compression method of the IP data packet adopts a header compression method, that is, the IP header of the IP data packet is compressed.
- the header compression is mainly for IP data packets with a large amount of data in the IP header and a small amount of data in the IP data.
- the IP headers of the plurality of IP data packets have little change and high repeatability.
- Embodiments of the present invention provide a method and apparatus for compressing and decompressing IP data packets, which are used to save air interface resources during transmission.
- An embodiment of the present invention provides a method for compressing an IP data packet, including:
- the first device performs compression processing on the IP data in the IP data packet according to the first compression algorithm; the first device encapsulates the compressed IP data into a packet data concentration protocol PDCP number According to the packet, the header information of the PDCP data packet includes identifier information, where the identifier information is used to indicate that the first compression algorithm or the IP data is compressed.
- An embodiment of the present invention provides a method for decompressing an IP data packet, including:
- the first device receives the packet data set protocol PDCP data packet sent by the second device, where the header information of the PDCP data packet includes the identifier information, where the identifier information is used to represent the first compression algorithm;
- the identification information in the header information of the PDCP data packet is learned by the first compression algorithm;
- the first device decompresses IP data in the PDCP data packet according to the first compression algorithm.
- An embodiment of the present invention provides a compression apparatus for an IP data packet, including:
- a first compression module configured to perform compression processing on the IP data in the IP data packet according to the first compression algorithm
- the encapsulating module is configured to encapsulate the compressed IP data into a packet data set protocol PDCP data packet, where the header information of the PDCP data packet includes identifier information, where the identifier information is used to indicate that the first compression algorithm or the IP data is compressed. .
- An embodiment of the present invention provides a device for decompressing an IP data packet, including:
- a third receiving module configured to receive a PDCP data packet sent by the second device, where the header information of the PDCP data packet includes identifier information, where the identifier information is used to represent a first compression algorithm, and the learning module is configured to The identification information in the header information of the PDCP data packet is learned by the first compression algorithm;
- a decompression module configured to perform decompression processing on the IP data in the PDCP data packet according to the first compression algorithm.
- the IP data in the IP data packet is compressed according to the first compression algorithm, and the compressed IP data is encapsulated into a PDCP data packet, so that the IP data in the IP data packet is implemented. Compression, which saves air interface resources during transmission.
- FIG. 1 is a flowchart of a method for compressing an IP data packet according to Embodiment 1 of the present invention
- FIG. 2 is a flowchart of a method for compressing an IP data packet according to Embodiment 2 of the present invention
- FIG. 4 is a flowchart of a method for compressing an IP data packet according to Embodiment 4 of the present invention
- FIG. 4 is a flowchart of a method for decompressing an IP data packet according to Embodiment 4 of the present invention
- FIG. 6 is a flowchart of a method for switching a IP data packet according to Embodiment 6 of the present invention
- Figure ⁇ is a schematic structural diagram of a compression apparatus for an IP data packet according to Embodiment 7 of the present invention.
- FIG. 8 is a schematic structural diagram of an apparatus for compressing an IP data packet according to Embodiment 8 of the present invention.
- FIG. 9 is a schematic structural diagram of an apparatus for compressing an IP data packet according to Embodiment 9 of the present invention.
- FIG. 10 is a schematic structural diagram of an apparatus for compressing an IP data packet according to Embodiment 10 of the present invention.
- FIG. 11 is a schematic structural diagram of an apparatus for compressing an IP data packet according to Embodiment 11 of the present invention.
- FIG. 12 is a schematic structural diagram of an apparatus for decompressing an IP data packet according to Embodiment 12 of the present invention. detailed description
- FIG. 1 is a flowchart of a method for compressing an IP data packet according to Embodiment 1 of the present invention. As shown in FIG. 1, the method includes:
- Step 101 Perform compression processing on the IP data in the IP data packet according to the first compression algorithm.
- each step may be performed by the first device or the second device.
- the first device may be a terminal or a network device
- the second device may be a terminal or a network device.
- the terminal may include a user equipment (User Equ i pment, hereinafter referred to as UE) or a relay station.
- the network device may include a radio network controller (Radio Ne twork Cont roler, hereinafter referred to as RNC), a gateway GPRS Supper t Node (GGSN) or a relay station.
- RNC Radio Ne twork Cont roler
- GGSN gateway GPRS Supper t Node
- the terminal and the network device are only used as examples of the embodiments of the present invention, and should not be limited to the embodiments of the present invention. In practical applications, both the terminal and the network device can adopt other devices as needed.
- the IP data packet includes an IP header and IP data.
- the IP data in the IP data packet can be compressed, and the IP header can be not compressed.
- Step 102 Encapsulate the compressed IP data into a Packet Data Center Protocol (PDCP) data packet, where the header information of the PDCP data packet includes identifier information, where the identifier information is used to indicate the first
- the compression algorithm or IP data is compressed; the identification information can be used to identify the compression state of the IP data. Specifically, the identification information can be used to indicate that the IP data is compressed or used to represent the first compression algorithm.
- the header information may include a PDCP header and an IP header, and the identification information may be set in the PDCP header or in the IP header, or the identification information may be simultaneously set in the PDCP header and the IP header.
- the identifier information is written in the header information of the PDCP data packet, so that the header information of the generated PDCP data packet includes the identifier information.
- the IP data in the IP data packet may be compressed according to the first compression algorithm, and the compressed IP data is encapsulated into a PDCP data packet, so that the IP data in the IP data packet is implemented. Compression, which saves air interface resources during transmission, reduces air interface transmission burden, and improves network capacity.
- FIG. 2 is a flowchart of a method for compressing an IP data packet according to Embodiment 2 of the present invention. As shown in FIG. 2, the method includes:
- Step 201 The first device receives a first identifier sent by the second device, where the first identifier is used to indicate a compression algorithm supported by the second device.
- the second device when the first device is a terminal, the second device may be a network device or a terminal; when the first device is a network device, the second device is a terminal or a network device. This will not be repeated in the subsequent embodiments.
- the compression algorithm supported by the second device may include one of the following or any combination thereof: LZW algorithm, LZSS algorithm, LZ0 algorithm.
- L in the LZW algorithm stands for Abraham Lempe Z stands for Jacob Ziv
- W stands for Wel ch
- L in LZSS algorithm stands for Abraham Lempe Z stands for Jacob Ziv
- W stands for Welch
- S stands for James S torer
- S stands for Thomas Szymanski
- LZO algorithm L stands for Abraham Lempe l
- Z stands for Jacob Ziv
- 0 stands for Markus Franz Xaver Johannes Oberhumer.
- the above L, Z, W and 0 represent the initials of the English name of the algorithm inventor.
- the second device may directly send the first identifier to the first device, or the second device may send the first identifier to the first device by using other network devices.
- the second device may send the first identifier to the first device by using a radio resource control (Radio Resource Cont rol, hereinafter referred to as RRC) message.
- RRC Radio Resource Cont rol
- the RRC message may include a dedicated RRC message or a system message
- the dedicated RRC message may include an uplink dedicated RRC message or a downlink dedicated RRC message.
- the second device may send the first identifier to the first device by using an uplink RRC message, for example, uplink dedicated RRC
- the information may include an INTER RAT HANDOVER INFO, an RRC CONNECTION SETUP COMPLETE or a UE CAPABILITY I FORMATION c.
- the second device sends the message to the first device.
- the uplink dedicated RRC message includes the first identifier in the uplink dedicated RRC message.
- the compression algorithm cell may be added to the "PDCP capability" in the cell "UE Radio access capability" of the uplink dedicated RRC message.
- the compression algorithm cell may be "IP data packet compress ion algorithm capability".
- the first identifier of the Bay 1 J can be set in the compression algorithm cell "IP data packet compress ion algorithm capability", as shown in Table 1 below:
- the "IP data packet compressing algorithm capability" may be represented by a bitmap format.
- the bitmap format can be xyz, where X can be the identifier of the LZSS algorithm, y can be the identifier of the LZ0 algorithm, and z can be the identifier of the LZW algorithm. If x, y or z is set to 1, it indicates that the first identifier includes the identifier of the compression algorithm corresponding to the x, y or z; if x, y or z is set to 0, it indicates that the first identifier does not include the x, y or z corresponds to the identity of the compression algorithm.
- xyz When xyz is 001, it indicates that the first identifier includes the LZW algorithm; when xyz is 011, it indicates that the first identifier includes the LZ0 algorithm and the LZW algorithm; when xyz is 111, the first identifier includes the LZSS algorithm, the LZ0 algorithm, and LZW algorithm.
- the second device may send the first identifier to the first device by using the system message.
- the second device is configured to the first device
- the system sends a system message, and the system message includes a first identifier.
- the system message can be a system information block (System Information Filter, hereinafter referred to as: SIB) message.
- SIB System Information Filter
- Step 202 The first device determines, according to the first identifier, a first compression algorithm from a compression algorithm supported by the second device.
- the first device may learn the compression algorithm supported by the second device according to the first identifier, and determine the first compression algorithm from the compression algorithm supported by the second device.
- the first device may determine the first compression algorithm from the compression algorithm supported by the second device according to the first identifier and the first compression algorithm configuration information.
- the first compression algorithm configuration information may be locally configured by the network device or configured by the core network and delivered to the network device.
- the first compression algorithm configuration information may be locally configured by the terminal, or sent to the terminal by the network side.
- the first compression algorithm configuration information may include one or any combination of the following: a compression algorithm that can be processed by the first device, a degree of consumption of the first device resource by the compression algorithm, a priority of the compression algorithm, or any combination thereof .
- the first device can learn the compression algorithm supported by the second device according to the first identifier, and according to the compression algorithm that can be processed by the first device,
- the first compression algorithm is determined in a compression algorithm supported by the second device.
- the compression algorithm supported by the second device includes an LZW algorithm, an LZSS algorithm, and an LZ0 algorithm.
- the compression algorithm that the first device can process includes the LZW algorithm, and the first compression algorithm determined is the LZW algorithm.
- the first device may learn the compression algorithm supported by the second device according to the first identifier, and consume the first device resource according to the compression algorithm.
- a first compression algorithm is determined from a compression algorithm supported by the second device.
- the first device is a network device, specifically, if the load of the first device is high, the compression algorithm that minimizes the consumption of the first device resource may be determined from the compression algorithm supported by the second device as the first Compression algorithm; or may be if the first device is loaded When low, the compression algorithm with the highest degree of consumption of the first device resource can be determined from the compression algorithm supported by the second device as the first compression algorithm.
- the first device may determine, as the first compression algorithm, a compression algorithm that minimizes the consumption of the first device resource in the compression algorithm supported by the second device.
- the first device can learn the compression algorithm supported by the second device according to the first identifier, and according to the The degree of consumption of the first device resource by the compression algorithm and the compression algorithm that the first device can process determines the first compression algorithm from the compression algorithm supported by the second device.
- the first device may determine, according to a compression algorithm that the first device can process, a compression algorithm to be determined from a compression algorithm supported by the second device, and consume the first device resource according to the compression algorithm from the to-be-determined compression algorithm.
- the first compression algorithm is determined.
- the compression algorithm supported by the second device includes an LZW algorithm, an LZSS algorithm, and an LZ0 algorithm.
- the compression algorithm that the first device can process includes the LZ0 algorithm and the LZSS algorithm, and the first device can be compressed according to the first device.
- the algorithm determines that the LZ0 algorithm and the LZSS algorithm are pending compression algorithms from the LZW algorithm, the LZSS algorithm and the LZ0 algorithm, and determines the first compression algorithm from the LZ0 algorithm and the LZSS algorithm according to the degree of consumption of the first device resource by the compression algorithm.
- the first device may learn the compression algorithm supported by the second device according to the first identifier, and according to the first device.
- the compressible algorithm and the compression algorithm that can be processed determine the first compression algorithm from the compression algorithms supported by the second device.
- the first device may determine, according to a compression algorithm that the first device can process, a compression algorithm to be determined from a compression algorithm supported by the second device, and determine a first compression algorithm from the pending compression algorithm according to a compression algorithm priority.
- the compression algorithm supported by the second device includes an LZW algorithm, an LZSS algorithm, and an LZ0 algorithm.
- the compression algorithm that the first device can process includes the LZ0 algorithm and the LZSS algorithm, and the first device can be compressed according to the first device.
- the algorithm determines from the LZW algorithm, the LZSS algorithm and the LZ0 algorithm that the LZ0 algorithm and the LZSS algorithm are pending compression algorithms.
- the priority when using hardware compression
- the priority may be, for example, LZSS algorithm > LZ0 algorithm > LZW algorithm, the first device may determine the LZSS algorithm with the highest priority from the pending compression algorithm as the first compression algorithm according to the priority of the compression algorithm; or when using software compression
- the priority of the compression algorithm in the algorithm may be, for example, LZ0 algorithm > LZW algorithm > LZSS algorithm, the first device may determine the LZ0 algorithm with the highest priority from the pending compression algorithm as the first compression algorithm according to the priority of the compression algorithm.
- the case where the first compression algorithm configuration information includes the degree of consumption of the first device resource by the compression algorithm, the priority of the compression algorithm, or any combination thereof is no longer enumerated.
- Step 203 The first device sends the second identifier to the second device, where the second identifier is used to indicate the first compression algorithm.
- the first device may directly send the second identifier to the second device, or the first device may send the second identifier to the second device by using other network devices.
- the first device when the first device is the network device, and the second device is the terminal device, the first device may send the second identifier to the second device by using the downlink dedicated RRC message, for example, the downlink dedicated RRC message may include the wireless device. Create a message (Radio Bearer Setup) or a Radio Bearer Reconf igurat ion. Specifically, the first device sends a downlink dedicated RRC message to the second device, where the downlink dedicated RRC message includes the second identifier.
- a compression algorithm cell may be added to a cell of a downlink dedicated RRC message, for example, the compression algorithm cell may be an "IP data packet compress ion algorithm", and the second identifier of the shell 1 J may be set in a compression algorithm letter.
- the cell of the downlink dedicated RRC message may include "PDCP info", and the "PDCP info” may be located in the cell “RB information to setup", the "RB”
- the information to setup" may be located in the "RAB information for setup”
- the cell of the downlink dedicated RRC message may include "PDCP info”, and the "PDCP info” may be located in the letter In the element "RB information to reconfigure”, the "RB information to reconfigure” can be located in the cell "RB information to reconfigure”.
- Compression algorithm letter The yuan can be as shown in Table 2 below:
- the first device in the non-connected state may send the second identifier to the second device by using the uplink dedicated RRC message, for example, the uplink dedicated RRC.
- the message may include an RRC CONNECTION REQUEST or an RRC CONNECTION SETUP COMPLETE.
- the second identifier may be set in a cell of an uplink dedicated RRC message. Specifically, for the cell of the uplink dedicated RRC message, refer to the description of the cell of the uplink dedicated RRC message in step 201.
- the identifier of the specified compression algorithm may be sent to the second device by using the uplink dedicated RRC message, where the uplink dedicated RRC message includes the second identifier.
- the second identifier determined by the second device may be sent to the first device by using the downlink dedicated RRC message.
- Step 204 Determine whether to compress the IP data in the IP data packet, if yes, go to step 205, if otherwise, go to step 206.
- This step can be performed by the first device or the second device.
- the first compression algorithm may be learned according to the received second identifier.
- whether the IP data in the IP data packet is compressed may be determined according to the compression ratio of the first compression algorithm.
- the compression ratio of the first compression algorithm meets the compression ratio currently required, it is determined that the IP data in the IP data packet is compressed; when the compression ratio of the first compression algorithm does not meet the compression ratio currently required. It is determined that the IP data in the IP packet is not compressed. For example: When the compression ratio of the first compression algorithm is high, and the compression ratio currently required is low, it is determined that the IP data in the IP data packet is not compressed.
- the number of IPs is based on the service type of the IP data.
- the compression processing is performed according to the IP data in the package.
- the service type of the IP data conforms to the service type that needs to be compressed, it is determined that the IP data in the IP data packet is compressed.
- the service type of the IP data does not meet the current service type that needs to be compressed, it is determined that the service type is incorrect.
- the IP data in the IP packet is compressed. For example, when the service type of the IP data is video data, and the service type that needs to be compressed is text data, it is determined that the IP data in the IP data packet is not compressed.
- Step 205 Perform compression processing on the IP data in the IP data packet according to the first compression algorithm, and encapsulate the compressed IP data into a PDCP data packet, where the header information of the PDCP data packet includes identifier information, where the identifier information is used. Indicates that the IP data is compressed and performs step 207.
- step 204 is performed by the first device, the step is performed by the first device; when step 204 is performed by the second device, the step is performed by the second device.
- the second device may learn the first compression algorithm according to the second identifier received in step 203.
- the PDCP data packet includes the header information and the compressed IP data.
- the header information includes the PDCP header and the IP header of the IP data packet.
- the identifier information may be set in the PDCP header or in the IP header.
- the identification information When the identification information is set in the PDCP header, the identification information may be a compression identifier (CID), and the CID may be set to 0 or 1.
- the CID may be set in a reserved bit of a packet identifier (Packet Ident if ier, hereinafter referred to as PID) of a PDCP header of a PDCP protocol data unit (hereinafter referred to as PDU) that constitutes a PDCP packet.
- PID Packet Ident if ier
- PDU PDCP protocol data unit
- the CID can also be set in the extension bit of the PID.
- the existing PID can be extended to add an extension bit after the existing 32-bit PID and write the CID to the extension bit.
- the identification information When the identification information is set in the IP header, the identification information may be a CID, and the CID may be set to a currently unused value, the CID indicates that the PDCP data packet is compressed, and the receiving end needs to perform a decompression operation; When the CID is not included in the header, it indicates that the PDCP data packet is not compressed, and the receiving end does not need to perform a decompression operation.
- the IP data may include IPv4 data, IPv6 data, and/or Point to Point Protocol (PPP data), the IP header of the IPv4 data is 0x4X, the IP header of the IPv6 is 0x6X, and the IP header of the PPP data is 0x7E.
- PPP data Point to Point Protocol
- the CID is written into a specific field of the IP header.
- the specific field can be the first 8 bits of the IP header.
- the structure of the PDCP packet including the CID in the IP header can be as follows:
- IP data IPv4 data / IPv6 data / PPP data
- Step 206 Encapsulate the IP data into a PDCP data packet, and perform step 207.
- step 204 is performed by the first device
- step 204 is performed by the second device
- step 207 is performed by the second device.
- the identifier information may be a CID
- the identifier information When the identifier information is set in the IP header, the identifier information may be a CID, and the PDCP packet does not include the CID.
- the structure of the PDCP packet that does not include the CID in the IP header may be as follows:
- IP header (0x4X I 0x6X / 0x7E) I IP data (IPv4 data / IPv6 data / PPP data)
- Step 207 Send a PDCP data packet.
- the step is specifically: the first device sends the PDCP data packet to the second device; when the step 204 is performed by the second device, the step is specifically: the second device uses the PDCP data packet Send to the first device.
- Step 208 Determine, according to the header information of the received PDCP data packet, whether the IP data in the PDCP data packet is the compressed IP data, and if yes, execute step 209, if no, the process ends.
- step 207 When step 207 is performed by the first device, the step is performed by the second device; when step 207 is performed by the second device, the step is performed by the first device.
- whether the IP data in the PDCP data packet is the compressed IP data may be determined according to whether the identifier information is included in the IP header, for example: when the identifier information is included in the IP header. It is determined that the IP data is the compressed IP data. When the IP header does not include the identification information, it is determined that the IP data is not the compressed IP data. Step 209: Decompress IP data in the PDCP data packet according to the first compression algorithm, and the process ends.
- step 205 When step 205 is performed by the first device, step 203 can be performed after step 205.
- the first device determines a first compression algorithm from the compression algorithm supported by the second device, and sends a second identifier indicating the first compression algorithm to the second device, where the first device or the second device may be configured according to the second device.
- the first compression algorithm compresses the IP data in the IP data packet, encapsulates the compressed IP data into a PDCP data packet, and transmits the PDCP data packet, thereby implementing compression on the IP data in the IP data packet, thereby
- the air interface resources are saved during the transmission process, the air interface transmission load is reduced, and the network capacity is increased.
- the first device determines the first compression algorithm and sends an identifier indicating the first compression algorithm to the second device, so that the second device can perform compression processing on the IP data according to the first compression algorithm, without using the first
- the second device performs a process of determining the first compression algorithm, thereby avoiding consumption of the second device resource.
- FIG. 3 is a flowchart of a method for compressing an IP data packet according to Embodiment 3 of the present invention. As shown in FIG. 3, the method includes:
- Step 301 The second device sends a first identifier to the first device, where the first identifier is used to indicate a compression algorithm supported by the second device.
- Step 302 The first device determines, according to the first identifier, a compression algorithm that can be supported by the first device and the second device from a compression algorithm supported by the second device.
- the first device may learn the compression algorithm supported by the second device according to the first identifier, and determine a compression algorithm that can be supported by the first device and the second device from the compression algorithm supported by the second device.
- the first device may determine, according to the first identifier and the second compression algorithm configuration information, a pressure that can be supported by the first device and the second device from a compression algorithm supported by the second device. Reduction algorithm.
- the second compression algorithm configuration information may be locally configured by the network device or configured by the core network and delivered to the network device.
- the first compression algorithm configuration information may be locally configured by the terminal, or sent to the terminal by the network side.
- the second compression algorithm configuration information may include a compression algorithm that the first device can process.
- the first device may learn the compression algorithm supported by the second device according to the first identifier, and determine the first device and the first device from the compression algorithm supported by the second device according to the compression algorithm that the first device can process.
- a compression algorithm that both devices can support.
- the compression algorithm supported by the second device includes a compression algorithm 1, a compression algorithm 2, a compression algorithm 3, and a compression algorithm 4, and the compression algorithm that the first device can process includes a compression algorithm 2, a compression algorithm 3, and a compression algorithm 4.
- the compression algorithm that can be supported by the first device and the second device determined by the first device includes a compression algorithm 2, a compression algorithm 3, and a compression algorithm 4.
- the second compression algorithm configuration information may include a compression algorithm that the first device can process and a degree of consumption of the first device resource by the compression algorithm.
- the first device may learn the compression algorithm supported by the second device according to the first identifier, and the compression algorithm supported by the second device according to the compression algorithm and the compression algorithm that the first device can process.
- a compression algorithm that both the first device and the second device can support is determined.
- the first device may learn, according to the first identifier, a compression algorithm supported by the second device, and determine, according to a compression algorithm that the first device can process, a compression algorithm to be determined from a compression algorithm supported by the second device, and according to The degree of consumption of the first device resource by the compression algorithm determines, from the pending compression algorithm, a compression algorithm that both the first device and the second device can support.
- the first device is a network device, for example, if the load of the first device is high, the compression algorithm that determines that the consumption of the first device resource is low from the pending compression algorithm is that both the first device and the second device can The compression algorithm is supported.
- the compression algorithm that is highly consumed by the first device resource can be determined from the pending compression algorithm to be a compression algorithm that can be supported by both the first device and the second device.
- the first device may be configured to determine the first device resource in the to-be-compressed compression algorithm.
- the least expensive compression algorithm determines a compression algorithm that both the first device and the second device can support.
- the compression algorithm supported by the second device includes a compression algorithm 1, a compression algorithm 2, a compression algorithm 3, and a compression algorithm 4, and the compression algorithm that the second device can process includes a compression algorithm 2, a compression algorithm 3, and a compression algorithm 4.
- the pending compression algorithm determined by the first device includes a compression algorithm 2, a compression algorithm 3, and a compression algorithm 4; and determining, according to the degree of consumption of the first device resource by the compression algorithm, the compression algorithm 3 and the compression algorithm 4 are determined from the pending compression algorithm.
- Step 303 The first device sends a third identifier to the second device, where the third identifier is used to indicate a compression algorithm that can be supported by both the first device and the second device.
- the first device may directly send the third identifier to the second device, or the first device may send the third identifier to the second device by using other network devices.
- the first device when the first device is a network device, and the second device is a terminal device, the first device may send the third identifier to the second device by using a downlink dedicated RRC message or a system message. Specifically, the first device sends a downlink dedicated RRC message or a system message to the second device, where the downlink dedicated RRC message or the system message includes a third identifier.
- the compression algorithm cell may be added to the downlink dedicated RRC message or the system message, and the third identifier may be set in the added compression algorithm cell.
- the compression algorithm cell may be “IP data packet compression algorithm”. In the capability", it is specifically shown in Table 1 in the second embodiment.
- the "IP data packet compression algorithm capability" may be represented by a bitmap format. For details, refer to the second embodiment.
- Step 304 Determine whether to compress the IP data in the IP data packet, if yes, go to step 305, if otherwise, go to step 307.
- step 304 For the description of the step 304, reference may be made to the step 204 in the second embodiment, and details are not described herein again.
- Step 305 Determine a first compression algorithm from a compression algorithm that can be supported by both the first device and the second device.
- step 304 is performed by the first device
- this step is performed by the first device.
- First device from The first compression algorithm is determined by the compression algorithm that can be supported by the first device and the second device. For the specific process, refer to the compression algorithm supported by the second device according to the first identifier in the second step 202 of the second embodiment. A description of the first compression algorithm is determined.
- step 304 is performed by the second device
- this step is performed by the second device.
- the second device determines, according to the third identifier, a first compression algorithm from a compression algorithm that can be supported by the first device and the second device, and the specific process may refer to the first device according to the first identifier in step 202 of the second embodiment.
- a description of the first compression algorithm is determined in a compression algorithm supported by the second device.
- Step 306 Perform compression processing on the IP data in the IP data packet according to the first compression algorithm, and encapsulate the compressed IP data into a PDCP data packet, where the header information of the PDCP data packet includes an algorithm identifier, where the identifier information is used.
- the first compression algorithm is represented and step 308 is performed.
- step 304 is performed by the first device, the step is performed by the first device; when step 304 is performed by the second device, the step is performed by the second device.
- the PDCP data packet includes header information and compressed IP data.
- the header information includes a PDCP header and an IP header of the IP data packet, and the identifier information may be set in the PDCP header or in the IP header.
- the identifier information may be a compression algorithm identifier (hereinafter referred to as CAID).
- CAID may be set to 00, 01, 10 or 11 .
- the first compression algorithm is the LZSS algorithm
- the CAID is set to 01.
- the CAID may be set in the reserved bits of the PID of the PDCP header of the PDCP PDU constituting the PDCP packet. As shown in Table 3 above, the CAID may be written in the reserved bits 13 to 31 of the PID "PID Va lue". .
- the CAID can also be set in the extension bit of the PID. The existing PID can be extended, the extension bit is added after the existing 32-bit PID, and the CAID is written into the extension bit.
- the identification information When the identification information is set in the IP header, the identification information may be a CAID, and the CAID may be set to a currently unused value, the CAID indicates that the PDCP data packet is compressed, and the receiving end needs to perform a decompression operation; When the CAID is not included, it indicates that the PDCP data packet is not compressed, and the receiving end does not need to perform a decompression operation.
- the IP data can include IPv4 data, IPv6 data, and/or PPP data
- the IP header of the IPv4 data is 0x4X
- the IP header of the IPv6 is 0x6X
- the IP header of the PPP data is 0x7E
- the CAID is written into a specific field of the IP header.
- the specific field can be the first 8bi t of the IP header
- the structure of the PDCP packet including the CAID in the IP header can be as follows:
- IP data IPv4 data / IPv6 data / PPP data
- Step 307 Encapsulate the IP data into a PDCP data packet, and perform step 308.
- step 304 is performed by the first device, the step is performed by the first device; when step 304 is performed by the second device, the step is performed by the second device.
- Step 308 Send a PDCP data packet.
- the step is specifically: the first device sends the PDCP data packet to the second device; when the step 304 is performed by the second device, the step is specifically: the second device uses the PDCP data packet Send to the first device.
- Step 309 Identify, in the PDCP data packet, according to the received header information of the PDCP data packet.
- step 308 is performed by the first device, the step is performed by the first device; when step 308 is performed by the second device, the step is performed by the second device.
- the compressed state of the IP data includes whether the IP data is the compressed IP data and the first compression algorithm used when the IP data is the compressed IP data.
- the identification information is set in the PDCP header of the header information
- whether the IP data in the PDCP data packet is the compressed IP data and the first time when the IP data is the compressed IP data may be identified according to the identification information.
- the IP data in the PDCP data packet is the compressed IP data and the first compression used when the identifier information is included may be identified according to whether the identifier information is included in the IP header.
- the method further includes:
- Step 310 Decompress the IP data in the PDCP data packet according to the first compression algorithm.
- step 305 When step 305 is performed by the first device, step 303 can be performed after step 305.
- the first device determines, from the compression algorithm supported by the second device, a compression algorithm that can be supported by the first device and the second device, and is used to indicate that the first device and the second device can support the compression.
- the algorithm is sent to the second device, where the first device or the second device can determine the first compression algorithm from the compression algorithms that can be supported by the first device and the second device, and the IP data in the IP data packet according to the first compression algorithm.
- Performing compression processing encapsulating the compressed IP data into a PDCP data packet and transmitting the PDCP data packet, thereby realizing compression of IP data in the IP data packet, thereby saving air interface resources and reducing air interface transmission during transmission burden, Increased network capacity.
- the first device determines a compression algorithm that can be supported by the first device and the second device from the compression algorithm supported by the second device, and is configured to indicate that the first device and the second device are both
- the third identifier of the supported compression algorithm enables the second device to learn the compression algorithm that the first device and the second device can support, and the first device or the second device can be compressed from the first device and the second device.
- the first compression algorithm is determined in the compression algorithm that can be supported by the two devices, so that the first compression algorithm can be selected each time the IP data is compressed.
- FIG. 4 is a flowchart of a method for decompressing an IP data packet according to Embodiment 4 of the present invention. As shown in FIG. 4, the method includes:
- Step 401 The first device receives the PDCP data packet sent by the second device, where the header information of the PDCP data packet includes identifier information, where the identifier information is used to represent the first compression algorithm.
- Step 402 The first device learns the first compression algorithm according to the identifier information.
- Step 403 The first device decompresses the IP data in the PDCP data packet according to the first compression algorithm.
- the first device learns the first compression algorithm according to the identifier information in the header information of the received PDCP data packet, and decompresses the IP data in the PDCP data packet according to the first compression algorithm. Since the IP data in the PDCP data packet is the IP data compressed according to the first compression algorithm, the air interface resource is saved in the transmission process, the air interface transmission load is reduced, and the network capacity is improved.
- FIG. 5 is a flowchart of a method for decompressing an IP data packet according to Embodiment 5 of the present invention. As shown in FIG. 5, the method includes:
- Step 501 to step 503 can refer to step 401 to step 403 in the fourth embodiment, and details are not described herein.
- Step 504 The first device determines, according to the first correspondence relationship and the first compression algorithm, a second compression algorithm, where the first correspondence relationship includes a correspondence between the first compression algorithm and the second compression algorithm.
- the first device may query, from the first correspondence, a corresponding to the first compression algorithm.
- Second compression algorithm Second compression algorithm.
- Step 505 The first device performs compression processing on the IP data in the IP data packet sent to the second device according to the second compression algorithm.
- Step 506 The first device encapsulates the compressed IP data into a PDCP data packet, and sends the PDCP data packet, where the header information of the PDCP data packet includes identifier information for indicating the second compression algorithm.
- the first device may query the second compression algorithm corresponding to the first compression algorithm according to the correspondence between the first compression algorithm and the second compression algorithm, according to the second specified compression algorithm.
- the IP data in the IP data packet is compressed, and the compressed IP data is encapsulated into a PDCP data packet, and the PDCP data packet is sent, so that the IP data in the IP data packet is compressed, thereby being transmitted.
- air interface resources are saved, the air interface transmission burden is reduced, and network capacity is increased.
- the first device can obtain the second compression algorithm by querying the correspondence between the first compression algorithm and the second compression algorithm, and does not need to perform the process of determining the second compression algorithm, thereby avoiding resources for the first device. Consumption.
- the first device may determine the second compression algorithm by itself. The first device may continue to execute 605 after determining the second fixed compression algorithm. Alternatively, if the second device does not send the PDCP data packet to the first device, the first device may not compress the IP data in the IP data packet, but directly encapsulate the IP data in the IP data packet into a PDCP data packet.
- the sixth embodiment of the present invention provides a handover method.
- the RNC migration is taken as an example.
- the first device is a network device of the target cell
- the second device is a terminal.
- the network device of the target cell is a Drift RNC (hereinafter referred to as DRNC)
- the terminal may be a UE.
- FIG. 6 is a flowchart of a handover method according to Embodiment 6 of the present invention; Figure, as shown in Figure 6, the method includes:
- Step 601 The service RNC (Serving RNC, hereinafter referred to as SRNC) sends a Reloca t ion Required to the Core Network (hereinafter referred to as CN).
- SRNC Service RNC
- the relocation request includes a fourth identification and/or a first identification.
- the SRNC sends the fourth identity and/or the first identity to the CN via a relocation request.
- the fourth identifier is used to indicate a third compression algorithm
- the first identifier is used to indicate a compression algorithm supported by the terminal. Since the terminal is a UE in this embodiment, the first identifier can be used to indicate a compression algorithm supported by the UE. In this embodiment, the first identifier may be sent by the UE to the SRNC.
- the third compression algorithm is a compression algorithm used by the UE in the source cell. For example, the fourth identifier or the first identifier may be set in the cell "Source To Target Transparent Conta iner" of the relocation request.
- Step 602 CN sends a relocation request (Reloca t ion Reques t) to DRNC c Relocation Request comprising the fourth identifier and / or the first identifier.
- C sends the fourth identity and/or the first identity to the DRNC through a relocation request.
- the fourth identifier and/or the first identifier are set in the cell "Source RNC To Target RNC Transparent Conta iner" of the relocation request.
- Step 603 The DRNC sends a Reloca t i on Reques t Acknowledge to the CN.
- the relocation request acknowledgement may include compression algorithm indication information, where the compression algorithm indication information includes indicating that the DRNC supports the third The information of the compression algorithm; for example, the compression algorithm indicates that the information is set in the cell "Target RNC To Source RNC Transparent Conta iner" of the relocation request confirmation. If the DRNC does not support the third compression algorithm represented by the fourth identifier, the relocation request acknowledgement may not include any indication information.
- the relocation request acknowledgement may include compression algorithm indication information, where the compression algorithm indication information includes a compression algorithm for indicating that the DRNC supports the UE supported compression algorithm. information.
- the DRNC supports the first identifier
- the DRNC may further determine the first compression algorithm from the compression algorithm supported by the UE, and the compression algorithm indication information in the relocation request acknowledgement may include the second identifier, the second The identifier is used to identify the first compression algorithm.
- the compression algorithm indicates that the information is set in the cell " Targe t RNC To Source RNC Trans parent Conta iner" of the relocation request confirmation.
- the relocation request acknowledgement may include compression algorithm indication information, where the compression algorithm indication information includes The DRNC supports information of the third compression algorithm; for example, the compression algorithm indicates that the information is set in the cell "Targe t RNC To Source RNC Trans parent Conta iner" of the relocation request confirmation; if the DRNC does not support the fourth identifier
- the third compression algorithm supports the compression algorithm supported by the UE indicated by the first identifier
- the relocation request acknowledgement may include compression algorithm indication information, where the compression algorithm indication information includes information indicating that the DRNC supports the compression algorithm supported by the UE. .
- the DRNC may further determine the first compression algorithm from the compression algorithm supported by the UE, and the compression algorithm indication information in the relocation request acknowledgement may be A second identifier is included, the fourth identifier being used to represent the first compression algorithm.
- the compression algorithm indicates that the information is placed in the cell " Targe t RNC To Source RNC Trans parent Conta iner" in which the relocation is confirmed. If the DRNC does not support the third compression algorithm indicated by the fourth identifier and the compression algorithm supported by the UE indicated by the first identifier, the relocation request acknowledgement may not include any indication information.
- Step 604 The CN sends a relocation command (Re l oca t i on Command) to the SRNC.
- the relocation command includes compression algorithm indication information; if the relocation request acknowledgement does not include compression algorithm indication information, the relocation command does not include compression algorithm indication information.
- the SRNC stops the compression processing of the IP data in the IP data packet in the source cell. After the switch is completed, it can be done by DRNC and The UE re-determines the compression algorithm.
- step 605 is performed, otherwise step 606 is directly performed.
- Step 605 The SRNC sends the compression algorithm indication information to the UE.
- the SRNC may send the compression algorithm indication information to the UE by using a downlink RRC message or a downlink PDCP data packet.
- the compression algorithm indication information can be set in the PDCP header of the downlink PDCP packet.
- the UE may use the compression algorithm to indicate information to learn a new specified compression algorithm.
- Step 606 The SRNC sends a Relocation Detect to the DRNC.
- Step 607 DRNC sends a relocation detect (Relocation Detect) c step to CN 608, UE and global DRNC Terrestrial Radio Access (Universal Terrestrial
- Step 609 The UE performs UE Capability Interaction with the DRNC. Thereby completing the switching process.
- Step 610 The UE and the DRNC perform a compression method of the IP data packet.
- step 610 refer to the method in the foregoing Embodiment 1, Embodiment 2 or Embodiment 3. If the compression algorithm indication information sent by the SRNC to the UE in step 605 includes the second identifier for indicating the first compression algorithm, the UE or the DRNC may perform the process of compressing the IP data packet by using the UE or the DRNC. A compression algorithm compresses the IP data in the IP packet.
- the SRNC in the process of the UE switching from the source cell to the target cell, sends, by the CN, a fourth identifier for indicating the third compression algorithm or a first identifier for indicating a compression algorithm supported by the UE, to the DRNC. If the DRNC determines the first compression algorithm from the compression algorithm supported by the UE, the second identifier used to represent the first compression algorithm is set in the compression algorithm indication information to the SRNC by the CN, and the compression algorithm indicates the information by the SRNC. Sending to the UE, so that the UE learns the first compression algorithm determined by the DRNC, and the UE may adopt the first compression algorithm to the IP after the handover is completed.
- the IP data in the data packet is compressed to ensure the continuity of IP packet compression.
- the compression algorithm indication information may be set in the handover to UTRAN command (Handover to Ut ran Command) sent by the network device to the UE, so that the UE is informed of the changed
- UTRAN command Handover to Ut ran Command
- the network device can be a BSC. This ensures that after the handover is completed, the UE can compress the IP data in the IP data packet by using the modified compression algorithm, thereby ensuring the continuity of the IP data packet compression.
- FIG. 7 is a schematic structural diagram of an apparatus for compressing an IP data packet according to Embodiment 7 of the present invention.
- the network device includes: a first compression module 11 and a packaging module 12.
- the first compression module 11 performs compression processing on the IP data in the IP data packet according to the first compression algorithm;
- the encapsulation module 12 encapsulates the compressed IP data into a packet data concentration protocol PDCP data packet, and the header information of the PDCP data packet
- the identification information is used to indicate that the first compression algorithm or the IP data is compressed.
- the compression device of the IP data packet in this embodiment may be disposed in the first network or in the second network device.
- first network device and the second network device refer to Embodiment 1 of the above method.
- the compression device of the IP data packet in this embodiment may be used to perform the compression method of the IP data packet provided in Embodiment 1.
- the compression device for the IP data packet in this embodiment may perform compression processing on the IP data in the IP data packet according to the first compression algorithm, and encapsulate the compressed IP data into a PDCP data packet, and implement the IP data packet in the IP data packet.
- the IP data is compressed, thereby saving air interface resources during the transmission process, reducing the air interface transmission burden and increasing the network capacity.
- FIG. 8 is a schematic structural diagram of an apparatus for compressing an IP data packet according to Embodiment 8 of the present invention.
- the apparatus may further include a first determining module 13 and a first receiving. Module 14 and first transmitting module 15.
- the first receiving module 14 receives the first identifier sent by the second device, where the first identifier is used to indicate a compression algorithm supported by the second device;
- the determining module 13 determines the first compression algorithm from the compression algorithm supported by the second device according to the first identifier received by the first receiving module 14, and is determined by the first compression module 11 according to the first determining module 13
- the first compression algorithm performs compression processing on the IP data in the IP data packet;
- the first sending module 15 may send a second identifier to the second device, where the second identifier is used to indicate the first determined by the first determining module 13 A compression algorithm.
- the compression device of the IP data packet may be disposed in the first device.
- the compression device of the IP data packet in this embodiment may be used to perform the compression method of the IP data packet provided in Embodiment 2.
- the first compression algorithm is determined from the compression algorithm supported by the second device, and the second identifier indicating the first compression algorithm is sent to the second device according to the first compression algorithm.
- the IP data in the IP data packet is compressed, and the compressed IP data is encapsulated into a PDCP data packet and the PDCP data packet is transmitted, thereby realizing compression of the IP data in the IP data packet, thereby saving in the transmission process.
- Air interface resources reduce the burden of air interface transmission and increase network capacity.
- FIG. 9 is a schematic structural diagram of an apparatus for compressing an IP data packet according to Embodiment 9 of the present invention.
- the apparatus may further include a second receiving module 16 and a second sending. Module 17.
- the second sending module 17 sends a first identifier to the first device, where the first identifier is used to indicate a compression algorithm supported by the second device, so that the first device supports the compression algorithm supported by the second device according to the first identifier.
- the second receiving module 16 receives a second identifier sent by the first device, where the second identifier is used to represent the first compression algorithm, and is received by the first compression module 11 according to the second receiving module 16
- the first compression algorithm represented by the second identifier is compressed on the IP data in the IP data packet.
- the compression device of the IP data packet may be disposed in the second device.
- the compression device of the IP data packet in this embodiment may be used to perform the compression method of the IP data packet provided in Embodiment 2.
- the compression device of the IP data packet of this embodiment is based on the received second identifier
- a compression algorithm compresses the IP data in the IP data packet, encapsulates the compressed IP data into a PDCP data packet, and transmits the PDCP data packet, thereby implementing compression on the IP data in the IP data packet, thereby transmitting
- air interface resources are saved, the air interface transmission burden is reduced, and network capacity is increased.
- the apparatus may further include a third receiving module 18 and a second determining.
- the third receiving module 18 receives the first identifier sent by the second device, where the first identifier is used to indicate a compression algorithm supported by the second device, and the second determining module 19 is configured according to the first identifier received from the third receiving module 18, A compression algorithm that can be supported by both the first device and the second device is determined by the compression algorithm supported by the second device.
- the first device and the second device determined by the third determining module 20 are supported by the second determining module 19.
- the first compression algorithm is determined in the compression algorithm, and the first compression module 11 performs compression processing on the IP data in the IP data packet according to the first compression algorithm determined by the third determination module 20;
- the second device sends a third identifier, where the third identifier is used to indicate a compression algorithm that can be supported by the first device and the second device determined by the second determining module 19, for the second device to use the third device according to the third identifier.
- the first compression algorithm is determined in a compression algorithm that can be supported by both the second device.
- the compression device of the IP data packet may be disposed in the first device.
- the compression device of the IP data packet in this embodiment may be used to perform the compression method of the IP data packet provided in Embodiment 3.
- the compression device of the IP data packet of the embodiment may determine, from the compression algorithm supported by the second device, a compression algorithm that can be supported by both the first device and the second device, and is used to represent both the first device and the second device.
- the compressible algorithm that can be supported is sent to the second device, and the first compression algorithm is determined from a compression algorithm that can be supported by the first device and the second device, and the IP data in the IP data packet is compressed according to the first compression algorithm.
- Encapsulating the compressed IP data into a PDCP data packet and transmitting the PDCP data packet, thereby implementing compression of the IP data in the IP data packet In the transmission process, air interface resources are saved, the air interface transmission load is reduced, and the network capacity is increased.
- the device may further include a fourth sending module 22 and a fourth receiving module 23, according to the seventh embodiment. And a fourth determining module 24.
- the fourth sending module 22 sends a first identifier to the first device, where the first identifier is used to indicate a compression algorithm supported by the second device, so that the first device determines, according to the first identifier, a compression algorithm supported by the second device. a compression algorithm that can be supported by both the first device and the second device; the fourth receiving module 23 receives the third identifier sent by the first device, where the third identifier is used to represent a compression algorithm that can be supported by the first device and the second device.
- the fourth determining module 24 determines the first compression algorithm from the compression algorithms supported by the first device and the second device according to the third identifier received by the fourth receiving module 23, and is determined by the first compression module 11 according to the first compression module 11
- the first compression algorithm determined by the determining module 24 performs compression processing on the IP data in the IP data packet.
- the compression device of the IP data packet may be disposed in the second device.
- the compression device of the IP data packet in this embodiment may be used to perform the compression method of the IP data packet provided in Embodiment 3.
- the compression device for the IP data packet of the embodiment determines the first compression algorithm from the compression algorithm supported by the first device and the second device indicated by the received third identifier, and the IP data according to the first compression algorithm
- the IP data in the packet is compressed, and the compressed IP data is encapsulated into a PDCP data packet and the PDCP data packet is transmitted, thereby realizing the compression of the IP data in the IP data packet, thereby saving air interface resources in the transmission process. , reducing the air interface transmission burden and increasing network capacity.
- FIG. 12 is a schematic structural diagram of an apparatus for decompressing an IP data packet according to Embodiment 12 of the present invention. As shown in FIG. 12, the apparatus includes: a fifth receiving module 25, a learning module 26, and a decompression module 27.
- the fifth receiving module 25 receives the PDCP data packet sent by the second device, where the header information of the PDCP data packet includes identifier information, where the identifier information is used to represent the first compression algorithm;
- the first compression algorithm is learned according to the identification information in the header information of the PDCP data packet;
- the decompression module 27 performs decompression processing on the IP data in the PDCP data packet according to the first compression algorithm.
- the apparatus in this embodiment may further include: a fifth determining module 28 and a second compressing module 29.
- the fifth determining module 28 determines a second compression algorithm according to the first correspondence relationship and the first compression algorithm, where the first correspondence relationship includes a correspondence between the first compression algorithm and the second compression algorithm; and the second compression module
- the IP data in the IP packet sent to the second device is compressed according to the second compression algorithm.
- the decompression device of the IP data packet may be disposed in the first device.
- the decompression device of the IP data packet in this embodiment may be used to perform the decompression method of the IP data packet provided in the fourth embodiment or the fifth embodiment.
- the decompression device of the IP data packet of the embodiment obtains the first compression algorithm according to the identification information in the header information of the received PDCP data packet, and decompresses the IP data in the PDCP data packet according to the first compression algorithm.
- the IP data in the PDCP data packet is the IP data compressed according to the first compression algorithm, thereby saving air interface resources during the transmission process, reducing the air interface transmission burden, and improving the network capacity.
- the decompression device of the IP data packet of the embodiment may query the second compression algorithm corresponding to the first compression algorithm according to the correspondence between the first compression algorithm and the second compression algorithm, according to the second
- the compression algorithm is used to compress the IP data in the IP data packet, and the compressed IP data is encapsulated into a PDCP data packet, and the PDCP data packet is sent to implement compression of the IP data in the IP data packet.
- the decompression device of the IP data packet of the embodiment can obtain the second compression algorithm by querying the correspondence between the first compression algorithm and the second compression algorithm, and does not need to perform the process of determining the second compression algorithm, thereby avoiding the The consumption of a device resource.
- the foregoing storage medium includes: various media that can store program codes, such as ROM, RAM, disk or optical disk.
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Mobile Radio Communication Systems (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Communication Control (AREA)
Description
Claims
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
BR112012017645-5A BR112012017645B1 (pt) | 2010-01-18 | 2010-12-31 | Método e aparelho para compressão de pacote de dados de ip, e método e aparelho para descompressão de pacote de dados de ip |
US13/547,748 US8971267B2 (en) | 2010-01-18 | 2012-07-12 | Method and apparatus for compressing and decompressing IP data packet |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201010003376.X | 2010-01-18 | ||
CN201010003376XA CN102131234B (zh) | 2010-01-18 | 2010-01-18 | Ip数据包的压缩及解压缩方法和装置 |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/547,748 Continuation US8971267B2 (en) | 2010-01-18 | 2012-07-12 | Method and apparatus for compressing and decompressing IP data packet |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2011085632A1 true WO2011085632A1 (zh) | 2011-07-21 |
Family
ID=44269101
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2010/080574 WO2011085632A1 (zh) | 2010-01-18 | 2010-12-31 | 互联网协议数据包的压缩及解压缩方法和装置 |
Country Status (4)
Country | Link |
---|---|
US (1) | US8971267B2 (zh) |
CN (1) | CN102131234B (zh) |
BR (1) | BR112012017645B1 (zh) |
WO (1) | WO2011085632A1 (zh) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN110891287A (zh) * | 2018-09-07 | 2020-03-17 | 维沃移动通信有限公司 | 以太网包头压缩的方法、解压缩的方法和设备 |
Families Citing this family (26)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN102291398B (zh) * | 2011-08-05 | 2017-03-29 | 中兴通讯股份有限公司 | 无线通讯***中数据压缩与解压缩方法、装置及*** |
EP2947776B1 (en) * | 2013-01-17 | 2022-04-13 | Huawei Technologies Co., Ltd. | Data packet processing method and device |
CN103152441B (zh) * | 2013-01-31 | 2015-12-02 | 北京天地互连信息技术有限公司 | 一种移动IPv6中的头标压缩方法 |
GB2510358A (en) * | 2013-01-31 | 2014-08-06 | Eip | Configuring layer 2 data compression between a UE and base station in LTE. |
CN103281156B (zh) * | 2013-05-02 | 2017-06-06 | 华为技术有限公司 | 一种数据压缩、解压缩方法及装置 |
WO2015109527A1 (zh) * | 2014-01-24 | 2015-07-30 | 华为技术有限公司 | 头压缩处理装置及方法 |
US10470090B2 (en) * | 2014-11-14 | 2019-11-05 | Qualcomm Incorporated | Data compression techniques for handover and radio link failure recovery |
US10341466B2 (en) | 2014-11-14 | 2019-07-02 | Qualcomm Incorporated | Evolved data compression scheme signaling |
CN106302245A (zh) * | 2015-06-08 | 2017-01-04 | ***通信集团公司 | 一种lte***中数据包的压缩方法和装置 |
US10602550B2 (en) * | 2015-07-23 | 2020-03-24 | Apple Inc. | Layer 2 relay protocols and mobility relay method |
WO2017147754A1 (zh) * | 2016-02-29 | 2017-09-08 | 华为技术有限公司 | 数据包的压缩方法和装置 |
WO2017156684A1 (zh) * | 2016-03-14 | 2017-09-21 | 华为技术有限公司 | 一种用于传输数据的方法、装置和*** |
CN107306444A (zh) * | 2016-04-25 | 2017-10-31 | 中兴通讯股份有限公司 | 发送数据的方法及装置 |
CN106817365B (zh) * | 2016-12-30 | 2019-07-09 | Oppo广东移动通信有限公司 | 一种基于移动终端架构的数据传输方法及移动终端 |
CN111587417A (zh) * | 2017-11-09 | 2020-08-25 | 瑞典爱立信有限公司 | 用于数据存储的方法、设备、计算机程序和计算机程序产品 |
WO2019214625A1 (zh) * | 2018-05-11 | 2019-11-14 | 电信科学技术研究院有限公司 | Ue能力信息的上报、获取和处理方法及对应装置 |
CN110475243B (zh) * | 2018-05-11 | 2020-10-30 | 电信科学技术研究院有限公司 | Ue能力信息的上报、获取和处理方法及对应装置 |
CN110958647A (zh) | 2018-09-27 | 2020-04-03 | 电信科学技术研究院有限公司 | 一种数据传输方法及装置 |
CN111278060B (zh) * | 2019-01-18 | 2023-10-24 | 维沃移动通信有限公司 | 一种以太帧传输方法和相关设备 |
EP3900192A2 (en) * | 2019-02-28 | 2021-10-27 | Huawei Technologies Co., Ltd. | Compressed data transmissions in networks implementing interior gateway protocol |
CN114071622B (zh) * | 2019-04-30 | 2024-06-11 | 华为技术有限公司 | 一种数据处理方法、通信装置和*** |
WO2020222437A1 (en) * | 2019-04-30 | 2020-11-05 | Lg Electronics Inc. | Method and apparatus for determining whether to transmit packet containing a full header information or a compressed header information in wireless communication system |
US10817460B2 (en) | 2019-08-28 | 2020-10-27 | Advanced New Technologies Co., Ltd. | RDMA data sending and receiving methods, electronic device, and readable storage medium |
CN110704361A (zh) * | 2019-08-28 | 2020-01-17 | 阿里巴巴集团控股有限公司 | Rdma数据发送及接收方法、电子设备及可读存储介质 |
CN114303355B (zh) * | 2019-11-05 | 2024-03-29 | Oppo广东移动通信有限公司 | 一种指示解压缩对象的方法及装置、通信设备 |
WO2023205565A2 (en) * | 2022-03-25 | 2023-10-26 | Northeastern University | Sem-o-ran: semantic nextg o-ran slicing for data-driven edge-assisted mobile applications |
Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN1783876A (zh) * | 2004-12-03 | 2006-06-07 | 华为技术有限公司 | 一种实现分组数据聚合协议功能的***及方法 |
CN101316379A (zh) * | 2007-06-01 | 2008-12-03 | 华为技术有限公司 | 第二代移动通信***中实现a接口ip化的方法、设备及*** |
Family Cites Families (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
DE19950653B4 (de) * | 1999-10-21 | 2020-01-16 | Ipcom Gmbh & Co. Kg | Verfahren zum Betreiben eines Mobilfunknetzes |
FI110739B (fi) * | 2000-10-18 | 2003-03-14 | Nokia Corp | Otsikkokenttien kompressoinnin määrittäminen datapakettiyhteydelle |
EP2369770A1 (en) * | 2001-11-08 | 2011-09-28 | Mitsubishi Denki Kabushiki Kaisha | Packet Transmission Method and Packet Transmission Device |
CN100547997C (zh) | 2005-08-20 | 2009-10-07 | 海信集团有限公司 | 移动通信中ip数据压缩发送和接收的方法 |
CN101325696B (zh) | 2007-06-15 | 2010-12-08 | 中兴通讯股份有限公司 | 一种实现视频数据向ip数据转换的方法及装置 |
-
2010
- 2010-01-18 CN CN201010003376XA patent/CN102131234B/zh active Active
- 2010-12-31 BR BR112012017645-5A patent/BR112012017645B1/pt active IP Right Grant
- 2010-12-31 WO PCT/CN2010/080574 patent/WO2011085632A1/zh active Application Filing
-
2012
- 2012-07-12 US US13/547,748 patent/US8971267B2/en active Active
Patent Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN1783876A (zh) * | 2004-12-03 | 2006-06-07 | 华为技术有限公司 | 一种实现分组数据聚合协议功能的***及方法 |
CN101316379A (zh) * | 2007-06-01 | 2008-12-03 | 华为技术有限公司 | 第二代移动通信***中实现a接口ip化的方法、设备及*** |
Non-Patent Citations (1)
Title |
---|
MA, HANGHANG ET AL.: "Research and Realization of IPComp Protocol in IPv6", SCIENCE TECHNOLOGY AND ENGINEERING, vol. 9, no. 14, 31 July 2009 (2009-07-31), pages 4162 * |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN110891287A (zh) * | 2018-09-07 | 2020-03-17 | 维沃移动通信有限公司 | 以太网包头压缩的方法、解压缩的方法和设备 |
CN110891287B (zh) * | 2018-09-07 | 2021-05-28 | 维沃移动通信有限公司 | 以太网包头压缩、解压缩的方法和设备、及可读存储介质 |
Also Published As
Publication number | Publication date |
---|---|
US8971267B2 (en) | 2015-03-03 |
CN102131234B (zh) | 2013-12-04 |
CN102131234A (zh) | 2011-07-20 |
BR112012017645B1 (pt) | 2021-08-17 |
US20120275424A1 (en) | 2012-11-01 |
BR112012017645A2 (pt) | 2016-04-12 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2011085632A1 (zh) | 互联网协议数据包的压缩及解压缩方法和装置 | |
CN108809596B (zh) | 一种基于反转服务流特性的通信方法及装置 | |
US8483176B2 (en) | Packet communication method, packet communication system, wireless terminal, and packet communication device | |
WO2014110773A1 (zh) | 一种数据包处理方法和装置 | |
EP2464063B1 (en) | Method and apparatus for header compression in network relay scenarios | |
US11246058B2 (en) | Radio communication device and radio communication method | |
US20240178932A1 (en) | Ethernet frame transmission method and communications device | |
WO2015139324A1 (zh) | 配置指示方法和通信设备 | |
US20220150332A1 (en) | Method for transmitting data, sending end device and receiving end device | |
CN112469084B (zh) | 数据传输方法、装置、设备、存储介质及程序产品 | |
WO2017031700A1 (zh) | 一种数据包的压缩参数确定方法及相关设备 | |
JP5609728B2 (ja) | 通信端末およびデータ転送方法 | |
US20180213451A1 (en) | Base station and communication device can handover between two base stations | |
JP2023176001A (ja) | 端末装置、通信方法、および基地局装置 | |
CN112690037B (zh) | 终端装置、基站装置以及方法 | |
WO2019098143A1 (ja) | 端末装置、基地局装置、および方法 | |
CN101287008B (zh) | 实现子网依赖汇聚协议的*** | |
WO2013102336A1 (zh) | 鲁棒性头压缩通道配置方法和装置 | |
CN116391444A (zh) | 管理在移动网络之间的转换期间的下行链路数据 | |
US20050007981A1 (en) | Method and apparatus for use by a GPRS device in responding to change in SAPI connection | |
US20220256399A1 (en) | Method for ethernet frame transmission, method for ethernet frame reception, compressor, and decompressor | |
WO2017147754A1 (zh) | 数据包的压缩方法和装置 | |
RU2775743C1 (ru) | Терминальное устройство, устройство базовой станции и способ | |
CN113411837A (zh) | 一种udc更新解压缩字典的数据传输方法和终端 | |
WO2023015420A1 (zh) | 数据传输方法及装置 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 10842914 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
REG | Reference to national code |
Ref country code: BR Ref legal event code: B01A Ref document number: 112012017645 Country of ref document: BR |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 10842914 Country of ref document: EP Kind code of ref document: A1 |
|
ENP | Entry into the national phase |
Ref document number: 112012017645 Country of ref document: BR Kind code of ref document: A2 Effective date: 20120717 |