CN117835320A

CN117835320A - Data compression method, device, equipment and storage medium

Info

Publication number: CN117835320A
Application number: CN202211183357.9A
Authority: CN
Inventors: 黄曲芳
Original assignee: Spreadtrum Communications Shanghai Co Ltd
Current assignee: Spreadtrum Communications Shanghai Co Ltd
Priority date: 2022-09-27
Filing date: 2022-09-27
Publication date: 2024-04-05

Abstract

The application provides a data compression method, a device, equipment and a storage medium. The method comprises the following steps: the sending device may send the ROHC CID to the receiving device before sending the actual service data, or when obtaining the service data to be transmitted, specify that the first packet in the service data to be transmitted carries the ROHC CID, and then the sending device obtains the acknowledgement message to determine that the ROHC CID negotiated by the two parties is available, and the receiving device may compress the packet header of the packet of the service data to be transmitted according to the ROHC CID. The method ensures the establishment of CIDs in the sending equipment and the receiving equipment, and improves the packet header data compression efficiency.

Description

Data compression method, device, equipment and storage medium

Technical Field

The present disclosure relates to the field of communications technologies, and in particular, to a data compression method, apparatus, device, and storage medium.

Background

With the development of the fifth generation communication technology (5 th-generation, 5G) technology, the data transmission efficiency is higher and higher, so that the transmission of Extended real (XR) data with larger data volume by using the 5G network becomes possible.

In the related art, for transmission of XR data, a packet data convergence protocol (Packet Data Convergence Protocol, PDCP) entity within a sender may use robust header compression (Robust Header Compression, ROHC) as a header compression manner of the XR data. Specifically, the header compression flow of ROHC is: the sender suggests to use a certain Context (Context) identifier (Identity Document, ID) to compress a string of longer bits in the header in a certain data packet of the XR data, and informs the receiver, and after the receiver feeds back the acknowledgement message, the sender can use the Context ID negotiated with the receiver to compress the header of other data packets in the XR data.

However, when the resource scheduler of the sender discards the data packet containing the Context ID due to poor network quality and the like, so that the receiver cannot receive the data packet, the sender cannot use the Context ID to compress data if not receiving the acknowledgement message, and re-initiates the Context ID reconstruction, which results in lower packet header data compression efficiency.

Disclosure of Invention

The application provides a data compression method, a device, equipment and a storage medium, which ensure the establishment of Context ID at a sender and a receiver and improve the data compression efficiency of a packet header.

In a first aspect, the present application provides a data compression method, including:

transmitting a robust packet header compression context identifier ROHC CID;

acquiring an acknowledgement message, wherein the acknowledgement message is used for determining that the ROHC CID is available;

and compressing service data to be transmitted according to the ROHC CID.

In a possible implementation manner, the sending the robustness header compresses the ROHC context identification CID, including:

acquiring packet header information of service data to be transmitted;

generating a mapping relation between the packet header information and the ROHC CID according to the packet header information;

and sending the mapping relation.

In a possible implementation manner, the sending the mapping relationship includes:

and sending a preset data packet, wherein the preset data packet comprises the mapping relation.

In a possible implementation manner, the number of the packet header information is N, and correspondingly, the number of the ROHC CIDs is N, where N is an integer greater than 1;

the number of the preset data packets is 1, and the preset data packets comprise mapping relations between each packet header information and each ROHC CID.

In a possible embodiment, the acknowledgement message includes response information indicating that 1 or N ROHC CIDs are agreed to be used.

In a possible implementation, the response information is a bit map, which is used to indicate that one or more ROHC CIDs of the N ROHC CIDs are agreed to be used.

In a possible implementation manner, the number of the packet header information is 1, and correspondingly, the number of the ROHC CIDs is 1 or more;

the number of the preset data packets is M, a first preset data packet in the M preset data packets comprises the mapping relation between the packet header information and the ROHC CID, and M is an integer greater than 1

In one possible implementation manner, the acquiring header information of the service data to be transmitted includes:

after the transmission channel of the service data to be transmitted is established, a packet header request is sent, wherein the packet header request is used for requesting packet header information of the service data to be transmitted;

and receiving the packet header information of the service data to be transmitted.

In one possible implementation manner, after the establishment of the transmission channel of the service data to be transmitted is completed, the sending a packet header request includes:

after the transmission channel of the service data to be transmitted is established for a first preset time period, sending the packet header request to a first network element;

And after the second preset time period, if the packet header information of the service data to be transmitted is not received, sending the packet header request to a second network element.

In a possible implementation manner, according to the ROHC CID, compressing service data to be transmitted includes:

and compressing the packet header of the data packet in the service data to be transmitted according to the ROHC CID.

In one possible implementation, the transmitting the robustness header compression context identifies an ROHC CID, including:

acquiring service data to be transmitted, wherein the service data to be transmitted comprises a plurality of data packets;

adding the ROHC CID to a first packet of the plurality of packets;

and sending the first data packet, wherein the first data packet carries the ROHC CID.

In a possible implementation manner, the first data packet further includes first indication information, where the first indication information is used to indicate that the receiving device does not need to transmit an acknowledgement message.

In one possible implementation, the first indication information is located in a reserved bit in a header of the first data packet.

In one possible embodiment, the method further comprises:

Transmitting a packet data convergence protocol PDCP control protocol data unit PDU or an RRC message, wherein the PDCP control PDU or the RRC message comprises first indication information;

the first indication information is used for indicating that the receiver does not need to transmit the confirmation message.

In one possible implementation manner, the acquiring the acknowledgement message includes:

and generating the confirmation message when the successful transmission of the first data packet is detected.

In a possible implementation manner, the adding the ROHC CID to the first packet of the plurality of packets includes:

determining the first data packet from the plurality of data packets;

the ROHC CID is added to the first data packet.

In one possible implementation manner, the determining the first data packet from the plurality of data packets includes:

and determining the first data packet from the plurality of data packets according to auxiliary information, wherein the auxiliary information is used for suggesting the data packet carrying the ROHC CID.

In a possible implementation manner, the auxiliary information is importance parameters of the plurality of data packets; or,

the auxiliary information is second indication information of other protocol layers, and the second indication information is used for suggesting that the first data packet is a data packet carrying an ROHC CID.

In a possible implementation manner, the first data packet further includes third indication information;

the third indication information is used for indicating that the first data packet includes the ROHC CID, so that the media access control MAC does not discard the first data packet when task scheduling.

and compressing the data packets except the first data packet in the service data to be transmitted according to the ROHC CID.

In a second aspect, the present application provides a data compression apparatus comprising:

a sending module, configured to send a robust header compression context identifier ROHC CID;

an acquisition module, configured to acquire an acknowledgement message, where the acknowledgement message is used to determine that the ROHC CID is available;

and the compression module is used for compressing the service data to be transmitted according to the ROHC CID.

In one possible implementation manner, the sending module is specifically configured to:

acquiring packet header information of service data to be transmitted;

and sending the mapping relation.

In a possible implementation manner, the sending module is further configured to:

In a possible implementation manner, the number of the packet header information is N, and correspondingly, the number of the ROHC CIDs is N;

In a possible embodiment, the acknowledgement message includes response information indicating approval to use the 1 or N ROHC CIDs.

the number of the preset data packets is M, and a first preset data packet in the M preset data packets comprises the mapping relation between the packet header information and the ROHC CID, wherein M is an integer greater than 1.

In one possible implementation manner, the acquiring module is specifically configured to:

In one possible implementation, the obtaining module is further configured to:

In one possible embodiment, the compression module is specifically configured to:

adding the ROHC CID to a first packet of the plurality of packets;

In one possible embodiment, the data compression device further includes: an indication module;

the indication module is specifically used for:

In one possible implementation, the obtaining module is further configured to:

determining the first data packet from the plurality of data packets;

the ROHC CID is added to the first data packet.

In one possible embodiment, the compression module is further configured to:

In a third aspect, an embodiment of the present application provides a data compression apparatus, including: a processor, and a memory communicatively coupled to the processor;

the memory stores computer-executable instructions;

the processor executes the computer-executed instructions stored in the memory to implement the data compression method according to the first aspect.

In a fourth aspect, embodiments of the present application provide a computer-readable storage medium having stored therein computer-executable instructions for implementing the data compression method according to the first aspect when the computer-executable instructions are executed on a computer.

In a fifth aspect, embodiments of the present application provide a computer program product comprising a computer program which, when executed on a computer, implements the data compression method of the first aspect.

In a sixth aspect, embodiments of the present application provide a chip, where a computer program is stored, and the computer program is executed by the chip to implement the data compression method according to the first aspect.

In one possible embodiment, the chip is a chip in a chip module.

According to the data compression method, the device, the equipment and the storage medium, the sending equipment can send the ROHC CID to the receiving equipment before sending the real service data, or when the service data to be transmitted is obtained, the first data packet in the service data to be transmitted is appointed to carry the ROHC CID, then the sending equipment obtains the confirmation information to determine that the ROHC CID negotiated by the two parties is available, and the receiving equipment can compress the packet header of the data packet of the service data to be transmitted according to the ROHC CID. The method ensures the establishment of CIDs in the sending equipment and the receiving equipment, and improves the packet header data compression efficiency.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the application and together with the description, serve to explain the principles of the application.

Fig. 1 is a protocol layer architecture of a base station;

FIG. 2 is a schematic diagram illustrating a transmission sequence of data packets of a video;

fig. 3 is a schematic diagram illustrating an exemplary packet transmission carrying ROHC CID 1;

fig. 4 is a schematic view of an application scenario provided in an embodiment of the present application;

fig. 5 is a flow chart of a data compression method according to an embodiment of the present application;

fig. 6 is a flow chart of another data compression method according to the second embodiment of the present application;

fig. 7 is a schematic diagram of a mapping relationship generated by a PDCP entity and an ROHC entity according to a second embodiment of the present application;

fig. 8 is a flow chart of another data compression method according to the third embodiment of the present application;

fig. 9 is a flow chart of another data compression method according to the fourth embodiment of the present application;

fig. 10 is a schematic structural diagram of a data compression device according to a fifth embodiment of the present application;

fig. 11 is a schematic structural diagram of a data compression device according to a sixth embodiment of the present application.

Specific embodiments thereof have been shown by way of example in the drawings and will herein be described in more detail. These drawings and the written description are not intended to limit the scope of the inventive concepts in any way, but to illustrate the concepts of the present application to those skilled in the art by reference to specific embodiments.

Detailed Description

Reference will now be made in detail to exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numbers in different drawings refer to the same or similar elements, unless otherwise indicated. The implementations described in the following exemplary examples are not representative of all implementations consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with some aspects of the present application as detailed in the accompanying claims.

The technical solution of the embodiment of the application may be applicable to various communication systems, for example: long term evolution (Long Term Evolution, LTE) system, LTE frequency division duplex (Frequency Division Duplex, FDD) system, LTE time division duplex (Time Division Duplex, TDD), universal mobile telecommunications system (Universal Mobile Telecommunication System, UMTS), worldwide interoperability for microwave access (Worldwide Interoperability for Microwave Access, wiMAX) telecommunications system, 5G mobile telecommunications system, or new radio access technology (New Radio Access Technology, NR). The 5G mobile communication system may include a Non-independent Networking (NSA) and/or an independent networking (SA).

The technical solutions provided herein may also be applicable to Machine-type communications (Machine Type Communication, MTC), inter-Machine communication long term evolution (LTE-M), device-to-Device (D2D) networks, machine-to-Machine (Machine to Machine, M2M) networks, internet of things (Internet of Things, ioT) networks, or other networks. The IoT network may include, for example, an internet of vehicles. The communication modes in the internet of vehicles system are generally called as Vehicle to other devices (V2X, X may represent anything), for example, the V2X may include: vehicle-to-vehicle (Vehicle to Vehicle, V2V) communication, vehicle-to-infrastructure (Vehicle to Infrastructure, V2I) communication, vehicle-to-pedestrian communication (Vehicle to Pedestrian, V2P) or vehicle-to-network (Vehicle to Network, V2N) communication, etc.

Related terms or nouns referred to in the present application are first introduced to facilitate understanding by those skilled in the art.

(1)ROHC

In the process of network transmission and wireless communication, many transmission protocols, such as TCP/IP, UDP and the like, are generally used, and the packet headers of these protocols have a certain rule, and a large part of the protocols are unchanged in the transmission process, so that when the data in a single transmission is shorter than the packet headers, the packet headers need to occupy more transmission resources. Therefore, the packet header can be compressed by utilizing the change rule of the packet header, and the transmission efficiency is improved.

ROHC is a protocol for header compression, complete header information (complete header) includes a static header and a dynamic header, each having different fields and values, a sender (transmitting device) ROHC stores the fields and values of the complete header, i.e., the static header and the dynamic header, in a local compression Context (Context) data structure, subsequent packets are compressed with reference to this, only the changed value fields are transferred, and the sender assigns a Context identifier Context ID (hereinafter CID) to each Context, uniquely identifying the data stream.

When the receiving party (receiving equipment) ROHC receives a new data stream packet, the complete header field and the value are stored in a local decompression context data structure, when the decompression party establishes the complete context, the transmitting party transmits the ROHC compressed packet, and in the subsequent data stream transmission, the decompression party searches the corresponding decompression context according to the CID of the packet to decompress. Since the header uses compression techniques, redundant header fields are not passed in ROHC compressed packets, the decompressor must know which header fields the original uncompressed packet contains in order to decompress them.

The CID may also be referred to as an ROHC CID, hereinafter referred to as an ROHC CID.

(2)PDCP

PDCP is a radio transport protocol stack in UMTS that is responsible for compressing and decompressing internet protocol (Internet Protocol, IP) headers, transmitting user data, and maintaining radio bearer sequence numbers set for lossless radio network service subsystems (Serving Radio Network Subsystem, SRNS).

The PDCP entity is located at the PDCP sublayer. Several PDCP entities may be defined for a terminal device. Each PDCP entity carrying user plane data may be configured to use header compression. Each PDCP entity carries data of one radio bearer. PDCP supports robust header compression protocol (ROHC). Each PDCP entity may use at least one ROHC compressor instance and at least one ROHC decompressor instance.

Taking a base station and a terminal device as an example, generally ROHC is located in PDCP protocol layers of the base station, as shown in fig. 1, in the architecture shown in fig. 1, both the terminal device and the PDCP entity in the base station have ROHC entities, for downlink transmission, ROHC in the base station performs header compression of a data packet, ROHC in the terminal device performs header compression of a data packet, for uplink transmission, ROHC in the terminal device performs header compression of a data packet, and ROHC in the base station performs header compression of a data packet. The SDAP is a service data adaptation protocol (Service Data Adaptation Protocol) in FIG. 1, which is an upper layer protocol of the PDCP protocol.

For transmission of XR data, transmission of XR data with a large data volume is possible by using a 5G network with high data transmission efficiency.

Taking video service as an example, video data is generally subjected to video compression coding in an I/P/B coding mode, a data packet is in units of frames, one frame includes several tens of data packets, and the frames are divided into three types: i frame, P frame and B frame, wherein I frame belongs to independent decoding frame, after receiving I frame, receiver can independently decode without referring to other frames; neither the P-frame nor the B-frame can be decoded independently, and the receiver needs to refer to the data of other frames for decoding after receiving. As shown in fig. 2, a video starts with a first frame, typically an I-frame, followed by P-frames.

The PDCP entity in the sender may use ROHC as a header compression method of video data. Specifically, the sender needs to negotiate a compression scheme with the receiver in the first I frame of the video data: a longer string of bits in the header (first I frame) is compressed using a certain ROHC CID. After receiving the confirmation message of the receiver, the sender compresses the P frame and B frame data in the video data by using the negotiated compression mode so as to realize the transmission of the video data.

The negotiation process needs to take several milliseconds or tens of milliseconds, and the transmission of all data of the I frame needs to be completed in 5-6 milliseconds, so that the packet header compression of the data packet of the first I frame cannot be performed.

Taking downlink transmission as an example, as shown in fig. 3, the first I frame includes 5 data packets, the base station informs the receiver of "suggested to use bit 0110001" in the packet header compressed from ROHC CID 1 in the packet header of packet number 2 ", after receiving the data, the terminal device sends an acknowledgement message (ROHC feedback) to the base station, and when the base station subsequently sends P frame data, the base station can compress the data using ROHC CID 1, so as to achieve the effect of packet header compression, but the first I frame cannot compress the data packet header.

Further, the act of adding the ROHC CID to the data packet is performed by the ROHC module in PDCP, and the scheduling is performed by the medium access control (Medium Access Control, MAC), if the resource scheduler of the sender discards the data packet containing the ROHC CID due to poor network quality or the like, and does not transmit the data packet over the air, the receiver cannot receive the data packet, and cannot receive the establishment information of the ROHC CID, and cannot reply to the sender with an acknowledgement message, and the sender and the receiver cannot establish the ROHC CID. In the example shown in fig. 3, if packet No. 2 is discarded by the resource scheduler of the base station, the terminal device will not send ROHC feedback, and the sender will not use ROHC CID 1 to compress the packet header, but re-initiate ROHC CID reconstruction, resulting in lower packet header data compression efficiency.

Therefore, the present application proposes a data compression method, where a transmitting device sends an ROHC CID to a receiving device before sending service data, or when obtaining service data to be transmitted, a PDCP of the transmitting device instructs the ROHC to use a first data packet in the service data to be transmitted to carry the ROHC CID. ROHC may also indicate which packets carry CIDs to indicate to the resource scheduler that the packet is not discarded. The method ensures the establishment of CIDs in the sending equipment and the receiving equipment, and improves the packet header data compression efficiency.

In order to facilitate understanding, an application scenario to which the embodiments of the present application are applicable is described below with reference to fig. 4.

Fig. 4 is a schematic view of an application scenario provided in the embodiment of the present application. Referring to fig. 4, a terminal device 401 and a network device 402 are included. Taking downlink transmission as an example, the network device 402 may send an ROHC CID to the terminal device 401 before transmitting the real service data, and when the terminal device 401 receives the ROHC CID, an acknowledgement message is returned to the network device 402 to establish the ROHC CID with the terminal device 401.

Alternatively, the network device 402 may further use the first packet in the service data to be transmitted to carry the ROHC CID in the service data to be transmitted, and instruct the resource scheduler to carry the ROHC CID in the first packet, so as to ensure that the transmission of the first packet is successful.

In this embodiment of the present application, the network device may be any device having a wireless transceiver function. The apparatus includes, but is not limited to: an Evolved Node B (eNB), a radio network controller (Radio Network Controller, RNC), a Node B (Node B, NB), a base station controller (Base Station Controller, BSC), a base transceiver station (Base Transceiver Station, BTS), a Home base station (Home Evolved NodeB, or a Home Node B, HNB, for example), a Base Band Unit (BBU), an Access Point (AP) in a wireless fidelity (Wireless Fidelity, wiFi) system, a wireless relay Node, a wireless backhaul Node, a transmission Point (Transmission Point, TP), or a transmission reception Point (Transmission and Reception Point, TRP), etc., may also be 5G, such as NR, a next generation base station (The Next Generation Node B, gNB) in the system, or a transmission Point (TRP or TP), one or a group of antenna panels (including multiple antenna panels) of a base station in the 5G system, or may also be a network Node constituting the gNB or the transmission Point, such as a Baseband Unit (BBU), or a Distributed Unit (DU), etc.

In some deployments, the gNB may include a Centralized Unit (CU) and DUs. The gNB may also include an active antenna unit (Active Antenna Unit, AAU). The CU implements part of the functionality of the gNB and the DU implements part of the functionality of the gNB. For example, the CU is responsible for handling non-real-time protocols and services, implementing the functions of radio resource control (Radio Resource Control, RRC), PDCP layer. The DU is responsible for handling Physical layer protocols and real-time services, and implements functions of a radio link control (Radio Link Control, RLC), MAC, and Physical (PHY) layers. The AAU realizes part of physical layer processing function, radio frequency processing and related functions of the active antenna. Since the information of the RRC layer may eventually become information of the PHY layer or be converted from the information of the PHY layer, under this architecture, higher layer signaling, such as RRC layer signaling, may also be considered to be transmitted by the DU or by the du+aau. It is understood that the network device may be a device comprising one or more of a CU node, a DU node, an AAU node. In addition, the CU may be divided into Network devices in an access Network (Radio Access Network, RAN), or may be divided into Network devices in a Core Network (CN), which is not limited in this application.

The network device provides services for the Cell, and the terminal device communicates with the Cell through transmission resources (for example, frequency domain resources, or spectrum resources) allocated by the network device, where the Cell may belong to a macro base station (for example, macro eNB or macro gNB, etc.), or may belong to a base station corresponding to a Small Cell (Small Cell), where the Small Cell may include: urban cells (Metro cells), micro cells (Micro cells), pico cells (Pico cells), femto cells (Femto cells) and the like, and the small cells have the characteristics of small coverage area and low transmitting power and are suitable for providing high-rate data transmission services.

In the embodiments of the present application, the terminal device may also be referred to as a User Equipment (UE), an access terminal, a subscriber unit, a subscriber station, a mobile station, a remote terminal, a mobile device, a User terminal, a wireless communication device, a User agent, or a User Equipment.

The terminal device may be a device providing voice/data connectivity to a user, e.g., a handheld device with wireless connectivity, an in-vehicle device, etc. Currently, some examples of terminals may be: a Mobile Phone (Mobile Phone), a tablet (Pad), a computer with wireless transceiving function (such as a notebook, a palm, etc.), a Mobile internet device (Mobile Internet Device, MID), a Virtual Reality (VR) device, an augmented Reality (Augmented Reality, AR) device, an XR device, a wireless terminal in industrial control (industrial control), a wireless terminal in Self Driving (Self Driving), a wireless terminal in Remote Medical (Remote Medical), a wireless terminal in Smart Grid (Smart Grid), a wireless terminal in transportation security (Transportation Safety), a wireless terminal in Smart City (Smart City), a wireless terminal in Smart Home (Smart Home), a cellular Phone, a cordless Phone, a session initiation protocol (Session Initiation Protocol, SIP) Phone, a wireless local loop (Wireless Local Loop, WLL) station, a personal digital assistant (Personal Digital Assistant, PDA), a handheld device with wireless communication function, a computing device or other processing device connected to a wireless modem, a device, a wireless terminal in a wearable device, a future evolution network (PLMN) of a Mobile Phone (35G) or a Mobile network of the future, etc.

The wearable device can also be called as a wearable intelligent device, and is a generic name for intelligently designing daily wearing and developing wearable devices by applying a wearable technology, such as glasses, gloves, watches, clothes, shoes and the like. The wearable device is a portable device that is worn directly on the body or integrated into the clothing or accessories of the user. The wearable device is not only a hardware device, but also can realize a powerful function through software support, data interaction and cloud interaction. The generalized wearable intelligent device includes full functionality, large size, and may not rely on the smart phone to implement complete or partial functionality, such as: smart watches or smart glasses, etc., and focus on only certain types of application functions, and need to be used in combination with other devices, such as smart phones, for example, various smart bracelets, smart jewelry, etc. for physical sign monitoring.

Furthermore, the terminal device may also be a terminal device in an internet of things (Internet of things, ioT) system. IoT is an important component of future information technology development, and its main technical feature is to connect an item with a network through a communication technology, so as to implement man-machine interconnection and an intelligent network for object interconnection. IoT technology can achieve massive connectivity, deep coverage, and terminal power saving through, for example, narrowband (NB) technology.

The following describes the technical solutions of the present application and how the technical solutions of the present application solve the above technical problems in detail with specific embodiments. The following specific embodiments may exist alone or in combination with one another, and the same or similar concepts or processes may not be described in detail in some embodiments. Embodiments of the present application will be described below with reference to the accompanying drawings.

Fig. 5 is a schematic flow chart of a data compression method provided in an embodiment of the present application, where the method may be performed by a data compression apparatus, the apparatus may be a transmitting device, for downlink transmission, the transmitting device may be a network device, for uplink transmission, the transmitting device may be a terminal device, and referring to fig. 5, the method includes the following steps.

S501, transmitting ROHC CID.

The transmitting device may receive a data packet transmitted from an upper layer to be compressed and compress the data packet into a compressed packet that is identifiable to the receiving device, and then the transmitting device may transmit an ROHC CID to the receiving device, and establish the ROHC CID for compression and decompression with the receiving device.

Specifically, the manner in which the transmitting device transmits the ROHC CID may be, for example: the transmitting device may send the ROHC CID to the receiving device before sending the actual service data, or specify that the first packet in the service data to be transmitted carries the ROHC CID when the service data to be transmitted is acquired.

The ROHC CID may be determined by a source IP address, a destination IP address, a source port, a destination port, etc., and, for example, if downlink transmission is used, the source IP address and the source port are an IP address and a port of a service server that send service data to be transmitted, the destination IP address and the destination port are an IP address and a port of a terminal device that receives the service data to be transmitted, and these data packets with identical values originate from the same data stream and have the same context, and if any two packets are different, an unused CID is reassigned as a flag of a new data stream.

CIDs can be divided into Small CIDs and Large CIDs, with Small CIDs ranging in value [0, 15], large CIDs ranging in value [0, 65535].

S502, acquiring a confirmation message, wherein the confirmation message is used for determining that the ROHC CID is available.

After the transmitting device transmits the ROHC CID to the receiving device, the transmitting device may acquire the acknowledgement message.

In one possible implementation, the acknowledgement message may be sent to the transmitting device after the receiving device receives the ROHC CID.

In another possible implementation manner, the acknowledgement message may also be that the sending device detects whether the packet for carrying the ROHC CID is successfully sent, i.e. the sending device detects that the packet is successfully sent to the receiving device, and the sending device may also generate the acknowledgement message.

S503, compressing the service data to be transmitted according to the ROHC CID.

After the transmitting device obtains the ROHC CID, the packet header of the data packet of the service data to be transmitted may be compressed according to the ROHC CID.

In this embodiment, before sending real service data, the sending device may send an ROHC CID to the receiving device, or when obtaining service data to be transmitted, specify that a first data packet in the service data to be transmitted carries the ROHC CID, then the sending device obtains a confirmation message to determine that the ROHC CIDs negotiated by both sides are available, and the receiving device may compress a packet header of the data packet of the service data to be transmitted according to the ROHC CID. The method ensures the establishment of CIDs in the sending equipment and the receiving equipment, and improves the packet header data compression efficiency.

Next, a data compression method by which the transmitting device can transmit the ROHC CID to the receiving device before transmitting the real service data will be described in detail through embodiment two.

Fig. 6 is a flow chart of another data compression method provided in the second embodiment of the present application, where the method may be performed by a data compression apparatus, and the apparatus may be a transmitting device, for downlink transmission, the transmitting device may be a network device, for uplink transmission, the transmitting device may be a terminal device, and referring to fig. 6, the method includes the following steps.

S601, acquiring packet header information of service data to be transmitted.

The transmitting device may acquire header information of the service data to be transmitted before transmitting the service data to be transmitted to the receiving device. The service data to be transmitted is real service data.

Specifically, taking downlink transmission of service data as an example, the following modes may be adopted for the sending device to obtain header information of the service data to be transmitted:

in the first mode, the sending device may acquire header information of service data to be transmitted from the terminal device.

The second mode, transmitting device, may also be obtained from a core network control plane network element, e.g. an access and mobility management function (Access and Mobility Management Function, AMF).

The third mode, the transmitting device, may also be obtained from a core network user plane network element, such as a user plane function (User Plane Function, UPF).

It will be appreciated that, for the first mode, the header information of the service data to be transmitted provided by the terminal device may originate from the service server that sends the service data to be transmitted.

The sending device can actively acquire the packet header information of the service data to be transmitted, and can also receive the packet header information of the service data to be transmitted, which is actively reported by the opposite-end network element.

For the active acquisition mode of the sending device, in one possible implementation manner, the sending device may send, to the peer network element, a packet header request after the establishment of the transmission channel of the service data to be transmitted is completed, where the packet header request is used to request packet header information of the service data to be transmitted. And then the packet header information of the service data to be transmitted, which is sent by the opposite-end network element, can be received.

It should be noted that, the peer network element may be a terminal device, a UPF, an AMF, or the like.

In another possible implementation manner, the sending device may send a packet header request to the first network element after the transmission channel of the service data to be transmitted is established for a first preset duration, and send a packet header request to the second network element after the second preset duration if packet header information of the service data to be transmitted is not received. The first network element and the second network element are not the same network element, and the first network element and the second network element may be terminal equipment, UPF, AMF, or the like.

Specifically, the sending device may set a first timer, and start the first timer when the transmission channel of the service data to be transmitted is established, where the duration set by the first timer is a first preset duration, and during the operation of the first timer, the sending device waits for the peer network element to actively send header information of the service data to be transmitted. When the timer is completed (i.e. after the first preset time period), if the sending device does not receive the packet header information of the service data to be transmitted, the sending device may send a packet header request to the first network element.

It may be appreciated that when the first preset duration is 0, the sending device may send a packet header request to the first network element if the sending device does not receive packet header information of the service data to be transmitted when the transmission channel of the service data to be transmitted is established.

Meanwhile, the sending device starts a second timer, the duration set by the second timer is a second preset duration, and if the sending device receives the packet header information of the service data to be transmitted sent by the first network element or receives the packet header information of the service data to be transmitted sent by other network element devices during the running period of the second timer, the second timer is stopped. If the second timer is finished, the sending device does not receive the packet header information of the service data to be transmitted sent by the first network element or other network element devices, and the sending device can send a packet header request to the second network element to continuously request the packet header information of the service data to be transmitted.

In this embodiment, the header information may include a destination address, a source address, a destination port, a source port, and a length of each packet of the service data to be transmitted, which correspond to the service data to be transmitted.

S602, generating a mapping relation between the packet header information and the ROHC CID according to the packet header information.

After the sending device obtains the packet header information of the service data to be transmitted, the mapping relationship between the packet header information and the ROHC CID can be generated.

Illustratively, determining the mapping relationship between the longer-length bit 0110101 in the packet header information and CID1 may be expressed as cid1= 0110101, i.e., the receiving device and the transmitting device negotiate to use the packet header of the data packet for CID1 to compress and decompress through the mapping relationship.

S603, sending the mapping relation.

The sending device may send the mapping relationship through a preset data packet, and specifically, the sending device may use the preset data packet to carry the mapping relationship.

In a possible implementation manner, when the number of header information of the service data to be transmitted acquired by the sending device is N, and correspondingly, the number of ROHC CIDs determined by the sending device is also N, then the sending device may send, through a preset data packet, a mapping relationship between the header information and the ROHC CIDs, that is, the preset data packet includes a mapping relationship between each header information and each ROHC CID. Wherein N is an integer greater than 1.

It can be understood that the transmitting device may also carry the mapping relationship between the N packet header information and the ROHC CID through N preset data packets.

Optionally, the preset data packet may be a data packet including random bits, or may be a null packet, where the preset data packet is configured with a preset packet data convergence protocol sequence number PDCP SN, for example, the preset PDCP SN may be 0, and then when the sending device obtains service data to be transmitted, the PDCP SN may start from 1.

As shown in fig. 7, for example, the PDCP entity of the transmitting device may input an empty packet to the ROHC entity, and send header information of service data to be transmitted to the ROHC entity to inform the ROHC entity to generate a ROHC CID, the ROHC entity adds the mapping relationship between the generated ROHC CID and the header information to the empty packet, and then after the PDCP entity obtains a data packet including the mapping relationship between the ROHC CID and the header information, the PDCP entity may divide the data packet into PDCP sn=0.

In another possible implementation manner, when the number of header information of the service data to be transmitted acquired by the sending device is 1, and correspondingly, the number of ROHC CIDs determined by the sending device is also 1, the number of preset data packets is M, and a first preset data packet in the M preset data packets includes a mapping relationship between the header information and the ROHC CIDs, where M is an integer greater than 1. In this case, the M preset data packets may be data packets including random bits.

S604, acquiring an acknowledgement message, wherein the acknowledgement message is used for determining that the ROHC CID is available.

After the transmitting device transmits the mapping relationship to the receiving device, the transmitting device may receive an acknowledgement message transmitted by the receiving device, where the acknowledgement message includes response information indicating approval to use 1 or N ROHC CIDs.

In one possible implementation, the response information may be a bit map, where the bit map is used to indicate that one or more ROHC CIDs of the N ROHC CIDs are agreed to be used, specifically, 0 may be used to indicate that they are agreed to be used, 1 may be used to indicate that they are not agreed to be used, and of course, the meanings of 0 and 1 may be opposite, which is not limited in this application.

S605, compressing the service data to be transmitted according to the ROHC CID.

After the sending device obtains the acknowledgement message, the packet header of the data packet in the service data to be transmitted may be compressed according to the ROHC CID.

Specifically, the transmitting device may compress a header of a data packet that may be compressed in the service data to be transmitted.

In this embodiment, before transmitting real service data, the transmitting device may acquire header information of the service data to be transmitted, then generate a mapping relationship between the header information and the ROHC CID according to the header information, and transmit the mapping relationship to the receiving device. Then the sending device receives the confirmation message sent by the receiving device, determines that the ROHC CID negotiated by the two parties is available, and the receiving device can compress the packet header of the data packet of the service data to be transmitted according to the ROHC CID. The method ensures the establishment of CIDs in the sending equipment and the receiving equipment, and improves the packet header data compression efficiency.

In the following, description is given by embodiment three on the sending device, when obtaining the service data to be transmitted, specifying that the first packet in the service data to be transmitted carries the ROHC CID.

I.e. after the PDCP entity of the transmitting device acquires the packet carrying the ROHC CID from the ROHC entity, the PDCP entity may generate an acknowledgement message.

Fig. 8 is a flow chart of another data compression method provided in the third embodiment of the present application, where the method may be performed by a data compression apparatus, and the apparatus may be a transmitting device, for downlink transmission, the transmitting device may be a network device, for uplink transmission, the transmitting device may be a terminal device, and referring to fig. 8, the method includes the following steps.

S801, service data to be transmitted is acquired, wherein the service data to be transmitted comprises a plurality of data packets.

Specifically, the sending device may receive service data to be transmitted sent by the service server.

S802, adding the ROHC CID to a first data packet in the plurality of data packets.

Specifically, the ROHC entity of the transmitting device adds the ROHC CID to the first packet of the plurality of packets, so that the first packet carries the ROHC CID.

In one possible implementation, the PDCP entity of the transmitting device may input a plurality of packets of service data to be transmitted to an ROHC entity therein, and may instruct the ROHC entity to request the addition of the ROHC CID to a first packet of the plurality of packets.

In another possible implementation manner, after the PDCP entity of the transmitting device sends a plurality of data packets to the RHOC entity, the PDCP entity may receive the plurality of data packets sent by the ROHC entity, and the PDCP entity may determine, according to explicit or implicit information output by the ROHC entity, that the plurality of data packets carry a first data packet of the ROHC CID.

In another possible implementation manner, after the PDCP entity of the sending device sends a plurality of data packets to the RHOC entity, the PDCP entity may receive the plurality of data packets sent by the ROHC entity, and then may perform deep packet inspection on the plurality of data packets to determine which data packet carries the ROHC CID, and determine the data packet as the first data packet.

S803, a first data packet is sent, wherein the first data packet carries the ROHC CID.

After adding the ROHC CID to the first packet of the plurality of packets, the transmitting device may transmit the first packet to the receiving device.

Specifically, when the transmitting device transmits the first data packet, one or more of the following preset transmission policies may be adopted to transmit the first data packet: reducing modulation and coding strategies (Modulation and Coding Scheme, MCS), increasing the number of retransmissions of hybrid automatic repeat request (Hybrid Automatic Repeat reQuest, HARQ), low band transmissions, etc.

In one possible implementation manner, the first data packet may further include first indication information, where the first indication information is used to indicate that the receiving device does not need to transmit an acknowledgement message after receiving the first data packet.

Specifically, the first indication information may be located in a reserved bit in a header of the first data packet.

In another possible implementation, the transmitting device may send a PDCP protocol data unit (Protocol Data Unit, PDU) or an RRC message to the receiving device, where the PDCP control PDU or the RRC message includes first indication information, where the first indication information is used to indicate that the receiving device does not need to transmit an acknowledgement message.

Then, the receiving device may not generate the acknowledgement message after receiving the first indication information, or the ROHC of the receiving device may generate the acknowledgement message, but the PDCP entity or the resource scheduler (e.g., MAC) of the receiving device discards the acknowledgement message, i.e., does not transmit the acknowledgement message.

S804, acquiring a confirmation message, wherein the confirmation message is used for determining that the ROHC CID is available.

After the sending device sends the first data packet to the receiving device, the sending device may detect whether the first data packet is successfully transmitted, and when it is determined that the first data packet is successfully transmitted, the PDCP entity of the sending device may generate an acknowledgement message, and input the acknowledgement message into the ROHC entity, so that the ROHC entity performs header compression on a data packet to be transmitted in service data to be transmitted according to the ROHC CID.

It may be appreciated that, when the acknowledgement message is generated inside the sending device, the sending device may not send the acknowledgement message sent by the receiving device to the ROHC entity after receiving the acknowledgement message sent by the receiving device, where the receiving device may be the acknowledgement message sent before receiving the first indication information.

S805, compressing the service data to be transmitted according to the ROHC CID.

After the sending device obtains the acknowledgement message, the sending device may compress, according to the ROHC CID, the data packets except the first data packet in the service data to be transmitted.

In this embodiment, the sending device may obtain service data to be transmitted, where the service data to be transmitted includes a plurality of data packets, and add an ROHC CID to a first data packet in the plurality of data packets, and then the sending device sends the first data packet to the receiving device, where the first data packet carries the ROHC CID, and after the sending device obtains the acknowledgement message, compress, according to the ROHC CID, a packet header of a data packet other than the first data packet in the service data to be transmitted, thereby ensuring establishment of the CID between the sending device and the receiving device, and improving packet header data compression efficiency.

Next, another data compression method for instructing the ROHC to carry the first packet of the plurality of packets with the ROHC CID by the transmitting device according to the fourth embodiment will be described in detail.

The header compression method shown in fig. 9 may be used alone or in combination with the methods of other embodiments.

Fig. 9 is a flow chart of another data compression method provided in the fourth embodiment of the present application, where the method may be performed by a data compression apparatus, and the apparatus may be a transmitting device, for downlink transmission, the transmitting device may be a network device, for uplink transmission, the transmitting device may be a terminal device, and referring to fig. 9, the method includes the following steps.

S901, acquiring service data to be transmitted, wherein the service data to be transmitted comprises a plurality of data packets.

S902, determining a first data packet from a plurality of data packets.

After the sending device obtains a plurality of data packets of the service data to be transmitted, the first data packet may be determined from the plurality of data packets.

Specifically, the transmitting device may determine the first packet from the plurality of packets according to the auxiliary information, where the auxiliary information is used to suggest a packet carrying an ROHC CID.

In one possible implementation, the auxiliary information may be an importance parameter of a plurality of data packets, where the importance parameter may be represented by a value between 0 and 1, for example, where 0 may represent the lowest importance and 1 may represent the highest importance, or vice versa, which is not limited in this application.

The PDCP entity of the transmitting device may read importance parameters corresponding to each data packet, and then determine the data packet with the highest importance degree as the first data packet, so as to ensure that the first data packet is not discarded when the resource scheduler schedules.

In another example, the PDCP entity of the transmitting device may set a threshold, e.g., 0.7, when the importance parameter of the data packet is greater than the threshold, it is determined that the data packet may carry an ROHC CID, and when the importance parameter of the data packet is less than or equal to the threshold, it may be suggested that the data packet does not carry an ROHC CID.

The PDCP entity may then also directly inform the ROHC entity of the packet that is suggested to carry the ROHC CID. Alternatively, when the PDCP entity determines that X data packets may carry an ROHC CID according to the above threshold, the PDCP entity may notify the ROHC entity that one or more data packets may be selected from the X data packets for carrying the ROHC CID, where X is an integer greater than 1. The ROHC entity may determine whether to select a packet for carrying the ROHC CID among the X packets according to the suggestion of the PDCP entity.

In this example, different thresholds may be configured per packet, or the same thresholds may be configured per group of packets. The present application is not limited in this regard.

In another possible implementation manner, the auxiliary information may also be second indication information of other protocol layers, where the second indication information is used to suggest that the first data packet is a data packet carrying an ROHC CID.

S903, adding the ROHC CID to the first packet.

After the ROHC entity of the transmitting device determines the first data packet, the ROHC CID may be added to the first data packet.

In one possible implementation, the first data packet may further include third indication information, where the third indication information is used to indicate that the first data packet includes an ROHC CID, so that the MAC does not discard the first data packet when the task is scheduled.

S904, a first data packet is sent, wherein the first data packet carries the ROHC CID.

After the ROHC entity of the transmitting device adds the ROHC CID to the first data packet, where the first data packet may carry the ROHC CID, the PDCP entity of the transmitting device may then transmit the first data packet to the receiving device.

S905, acquiring an acknowledgement message, where the acknowledgement message is used to determine that the ROHC CID is available.

S906, compressing the service data to be transmitted according to the ROHC CID.

In this embodiment, the sending device may obtain service data to be transmitted, where the service data to be transmitted includes a plurality of data packets, determine a first data packet from the plurality of data packets, add an ROHC CID to the first data packet, and then send the first data packet to the receiving device, where the first data packet carries the ROHC CID, and after the sending device obtains the acknowledgement message, compress a packet header of a data packet except for the first data packet in the service data to be transmitted according to the ROHC CID, thereby ensuring establishment of the CID between the sending device and the receiving device and improving packet header data compression efficiency.

Fig. 10 is a schematic structural diagram of a data compression device according to a fifth embodiment of the present application. The data compression device 110 may be a transmitting apparatus, a chip or a chip module. Referring to fig. 10, the apparatus 100 includes: a transmission module 1001, an acquisition module 1002, and a compression module 1003, wherein,

a sending module 1001, configured to send the robustness header compression context identifier ROHC CID.

An obtaining module 1002, configured to obtain an acknowledgement message, where the acknowledgement message is used to determine that the ROHC CID is available.

And the compression module 1003 is configured to compress service data to be transmitted according to the ROHC CID.

In one possible implementation, the sending module 1001 is specifically configured to:

and acquiring packet header information of the service data to be transmitted.

And generating a mapping relation between the packet header information and the ROHC CID according to the packet header information.

And sending the mapping relation.

In one possible implementation, the sending module 1001 is further configured to:

and sending a preset data packet, wherein the preset data packet comprises a mapping relation.

In one possible embodiment, the number of packet header information is N, and the number of ROHC CIDs is N.

The number of preset data packets is 1, and the preset data packets comprise the mapping relation between each packet header information and each ROHC CID.

In one possible embodiment, the acknowledgement message includes response information indicating that 1 or N ROHC CIDs are agreed to be used.

In one possible implementation, the response information is a bit map indicating approval to use one or more ROHC CIDs of the N ROHC CIDs.

In one possible embodiment, the number of packet header information is 1, and the number of ROHC CIDs is 1 or more.

The number of the preset data packets is M, and a first preset data packet in the M preset data packets comprises a mapping relation between packet header information and ROHC CID, wherein M is an integer larger than 1.

In one possible implementation, the obtaining module 1002 is specifically configured to:

and after the transmission channel of the service data to be transmitted is established, sending a packet header request, wherein the packet header request is used for requesting packet header information of the service data to be transmitted.

And receiving packet header information of the service data to be transmitted.

In one possible implementation, the obtaining module 1002 is further configured to:

and after the transmission channel of the service data to be transmitted is established for a first preset time period, sending a packet header request to the first network element.

And after the second preset time period, if the packet header information of the service data to be transmitted is not received, sending a packet header request to the second network element.

In one possible implementation, the compression module 1003 is specifically configured to:

and acquiring service data to be transmitted, wherein the service data to be transmitted comprises a plurality of data packets.

The ROHC CID is added to a first packet of the plurality of packets.

And sending a first data packet, wherein the first data packet carries the ROHC CID.

In a possible embodiment, the first data packet further includes first indication information, where the first indication information is used to indicate that the receiving device does not need to transmit an acknowledgement message.

In one possible embodiment, the first indication information is located in a reserved bit in a header of the first data packet.

In one possible implementation, the data compression apparatus 100 further includes: an indication module;

the indication module is specifically used for:

and transmitting a packet data convergence protocol PDCP control protocol data unit PDU or an RRC message, wherein the PDCP control PDU or the RRC message comprises first indication information.

The first indication information is used for indicating that the receiving party does not need to transmit the confirmation message.

and generating an acknowledgement message when the successful transmission of the first data packet is detected.

a first data packet is determined from the plurality of data packets.

The ROHC CID is added to the first packet.

In one possible implementation, the auxiliary information is an importance parameter of the plurality of data packets; or,

In a possible implementation manner, the first data packet further includes third indication information.

The third indication information is used for indicating that the first data packet includes the ROHC CID, so that the media access control MAC does not discard the first data packet when the task is scheduled.

In one possible implementation, the compression module 1003 is further to:

The device of the present embodiment may be used to execute the technical solutions of the foregoing method embodiments, and the specific implementation manner and the technical effects are similar, and are not repeated herein.

Fig. 11 is a schematic structural diagram of an electronic device according to a sixth embodiment of the present application, as shown in fig. 11, an electronic device 110 may include: at least one processor 1101 and a memory 1102.

A memory 1102 for storing programs. In particular, the program may include program code including computer-operating instructions.

The Memory 1102 may include random access Memory (Random Access Memory, RAM) and may also include Non-volatile Memory (Non-volatile Memory), such as at least one disk Memory.

The processor 1101 is configured to execute computer-executable instructions stored in the memory 1102 to implement the methods described in the foregoing method embodiments. The processor 1101 may be a central processing unit (Central Processing Unit, CPU), or an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), or one or more integrated circuits configured to implement embodiments of the present application.

Optionally, the electronic device 110 may further include: communication interface 1103. In a specific implementation, if the communication interface 1103, the memory 1102, and the processor 1101 are implemented independently, the communication interface 1103, the memory 1102, and the processor 1101 may be connected to each other and perform communication with each other through buses. The bus may be an industry standard architecture (Industry Standard Architecture, ISA) bus, an external device interconnect (Peripheral Component, PCI) bus, or an extended industry standard architecture (Extended Industry Standard Architecture, EISA) bus, among others. Buses may be divided into address buses, data buses, control buses, etc., but do not represent only one bus or one type of bus.

Alternatively, in a specific implementation, if the communication interface 1103, the memory 1102, and the processor 1101 are implemented integrally on a single chip, the communication interface 1103, the memory 1102, and the processor 1101 may complete communication through internal interfaces.

The electronic device 110 may be a chip, a chip module, an IDE, a transmitting device, etc.

The electronic device of the present embodiment may be used to execute the technical solutions of the foregoing method embodiments, and the specific implementation manner and the technical effects are similar, and are not repeated herein.

A seventh embodiment of the present application provides a computer-readable storage medium, which may include: various media capable of storing computer execution instructions, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a RAM, a magnetic disk, or an optical disc, etc., specifically, the computer execution instructions are stored in the computer readable storage medium, and when the computer execution instructions are executed by a processor, the computer execution instructions are used to implement the technical schemes shown in the above method embodiments, and specific implementation manners and technical effects are similar, and are not repeated herein.

An eighth embodiment of the present application provides a computer program product, which includes a computer program, and when the computer program is executed by a processor, implements the technical solutions shown in the foregoing method embodiments, and specific implementation manners and technical effects are similar, and are not repeated herein.

A ninth embodiment of the present application provides a chip, on which a computer program is stored, where the computer program, when executed by the chip, implements a method shown in the foregoing method embodiment. The chip can also be a chip module.

Other embodiments of the present application will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of the application following, in general, the principles of the application and including such departures from the present disclosure as come within known or customary practice within the art to which the application pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the application being indicated by the following claims.

It is to be understood that the present application is not limited to the precise arrangements and instrumentalities shown in the drawings, which have been described above, and that various modifications and changes may be effected without departing from the scope thereof. The scope of the application is limited only by the appended claims.

Claims

1. A method of data compression, comprising:

transmitting a robust packet header compression context identifier ROHC CID;

and compressing service data to be transmitted according to the ROHC CID.

2. The method of claim 1, wherein the transmitting the robustness header compression context identifies an ROHC CID, comprising:

acquiring packet header information of service data to be transmitted;

and sending the mapping relation.

3. The method of claim 2, wherein the sending the mapping relationship comprises:

4. The method of claim 3, wherein the number of header information is N, and the number of ROHC CIDs is N, and N is an integer greater than 1;

5. The method of claim 4, wherein the acknowledgement message includes response information indicating approval to use 1 or N ROHC CIDs.

6. The method of claim 5, wherein the response information is a bit map indicating approval to use one or more ROHC CIDs of the N ROHC CIDs.

7. The method of claim 3, wherein the number of header information is 1, and the number of ROHC CIDs is 1 or more, respectively;

8. The method according to any one of claims 2-7, wherein the obtaining header information of the service data to be transmitted includes:

9. The method of claim 8, wherein the sending the packet header request after the establishment of the transmission channel of the service data to be transmitted is completed comprises:

10. The method according to any of claims 2-7, wherein compressing traffic data to be transmitted according to the ROHC CID comprises:

11. The method of claim 1, wherein the transmitting the robustness header compression context identifies an ROHC CID, comprising:

adding the ROHC CID to a first packet of the plurality of packets;

12. The method of claim 11, wherein the first data packet further comprises first indication information, the first indication information indicating that the receiving device does not need to transmit an acknowledgement message.

13. The method of claim 12, wherein the first indication information is located in reserved bits in a header of the first data packet.

14. The method of claim 11, wherein the method further comprises:

15. The method of claim 11, wherein the acquiring the acknowledgement message comprises:

16. The method of claim 11, wherein the adding the ROHC CID to the first packet of the plurality of packets comprises:

determining the first data packet from the plurality of data packets;

the ROHC CID is added to the first data packet.

17. The method of claim 16, wherein said determining said first data packet from said plurality of data packets comprises:

18. The method of claim 17, wherein the auxiliary information is an importance parameter of the plurality of data packets; or,

19. The method of claim 16, wherein the first data packet further includes third indication information;

20. The method of claim 11, wherein compressing traffic data to be transmitted according to the ROHC CID comprises:

21. A data compression apparatus, comprising:

22. An electronic device, comprising: a processor, and a memory communicatively coupled to the processor;

the memory stores computer-executable instructions;

the processor executes computer-executable instructions stored in the memory to implement the data compression method of any one of claims 1-20.

23. A computer readable storage medium having stored therein computer executable instructions which when executed by a processor are adapted to carry out a data compression method as claimed in any one of claims 1 to 20.