CN112187400B

CN112187400B - Data transmission method and device

Info

Publication number: CN112187400B
Application number: CN201910594723.1A
Authority: CN
Inventors: 苗金华; 全海洋
Original assignee: Datang Mobile Communications Equipment Co Ltd
Current assignee: Datang Mobile Communications Equipment Co Ltd
Priority date: 2019-07-03
Filing date: 2019-07-03
Publication date: 2022-04-12
Anticipated expiration: 2039-07-03
Also published as: WO2021000763A1; CN112187400A

Abstract

The application discloses a data transmission method and a data transmission device, which are used for performing data compression transmission processing according to dictionary information and solving the problem of low compression efficiency caused by packet loss in an RLC UM mode. The data transmission method provided by the embodiment of the application is applied to a compression end, and comprises the following steps: compressing the data according to dictionary information containing mapping relation between the data information and the dictionary to generate compressed data; and sending the compressed data to a receiving end.

Description

Data transmission method and device

Technical Field

The present application relates to the field of communications technologies, and in particular, to a data transmission method and apparatus.

Background

In the prior art, in the data transmission process, when the data volume is large, the transmission resources are in shortage. Especially, at the edge of the cell, the uplink power of the terminal is limited, and the transmission success rate of the large data packet is also affected. Therefore, in order to improve the system radio resource utilization, a concept of Uplink Data Compression (UDC) has been proposed.

UDC, i.e. using the existing open source compression algorithm, compresses the Uplink (UL) packets before transmitting them. Unlike RObust Header Compression (ROHC), ROHC performs Compression only on the Header of a packet, while UDC can perform Compression on the entire PDCP SDU, so Compression efficiency is higher especially for large packets.

Currently, UDCs are configured by RRC. The terminal (UE) may pre-store a dictionary, and the network side and the UE keep the dictionary synchronized. And the UE executes UDC compression according to the dictionary and sends the compressed data packet to the network side. And the network side decompresses according to the dictionary.

RLC AM mode:

the 4G/5G system supports an RLC Acknowledged Mode (AM) Mode. In the RLC cam mode, a sending end combines RLC Service Data units (Service Data units, SDUs) into RLC Packet Data Units (PDUs) by means of segmentation/concatenation, and marks an RLC Secondary base Station (SN) number. The RLC receiving end knows which RLC PDUs are not received according to the SN numbers and sends a status report to the sending end. And after the sending end receives the status report, finishing the retransmission of the RLC PDU which is not received according to the status report.

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

RLC UM mode:

the 4G/5G system supports an RLC Unacknowledged Mode (UM) Mode. In the RLC UM mode, the sending end combines RLC SDUs into RLC PDUs through segmentation/cascade connection and the like, and marks RLC SN numbers. These are the same as RLC AM. However, in the RLC UM mode, the receiving end does not send the status report, and the transmitting end cannot know which data packets are lost, so that the PDU of the lost RLC cannot be retransmitted. This does not guarantee a lower packet loss rate for data transmission.

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

Currently, UDC is configured for RLC AM entities. And because the dictionary of the UDC is updated according to the transmission state, if a receiving end cannot receive some data packets, the updating degree of the dictionary is inconsistent with that of the sending end, and further the decompression failure of subsequent data packets is caused.

Because the dictionary used by the UDC is updated according to the transmission state, in the RLC UM mode, it cannot be guaranteed that all data can be successfully received, and packet loss is allowed in the UM mode, so that the receiving end cannot receive some data packets, which may cause the degree of dictionary update to be inconsistent with the sending end, and further cause the problem of failure in decompression of subsequent data packets, and therefore, the UDC cannot be applied in the RLC UM mode, resulting in a limited use scenario of the UDC.

Disclosure of Invention

The embodiment of the application provides a data transmission method and a data transmission device, which are used for performing data compression transmission processing according to dictionary information, and solving the problem of low compression efficiency caused by packet loss in an RLC UM mode.

The data transmission method provided by the embodiment of the application is applied to a compression end, and comprises the following steps:

compressing the data according to dictionary information containing mapping relation between the data information and the dictionary to generate compressed data;

and sending the compressed data to a receiving end.

According to the embodiment of the application, data are compressed according to dictionary information containing the mapping relation between the data information and the dictionary, and compressed data are generated; and sending the compressed data to a receiving end, thereby realizing the data compression transmission processing according to the dictionary information and solving the problem of low compression efficiency caused by packet loss in the RLC UM mode.

Optionally, the dictionary information includes at least one of:

mapping relation between data stream and dictionary;

mapping relation between data packet length and dictionary;

the mapping relation between the Radio Link Control (RLC) mode and the dictionary;

and carrying the mapping relation between the information and the dictionary.

Optionally, the bearer information includes an identifier of a bearer.

Optionally, the method further includes sending the dictionary information to a decompression end through a message in one of the following forms:

radio resource control, RRC, signaling, or;

a packet data unit PDU through a packet data convergence protocol PDCP, or;

through the PDCP header.

Optionally, when the compression end is a terminal, the dictionary information is sent by a base station;

or, the dictionary information is pre-configured by the core network;

alternatively, the dictionary information is pre-stored.

The data transmission method provided by the embodiment of the application is applied to a decompression end, and comprises the following steps:

receiving compressed data obtained by compressing dictionary information according to the mapping relation between the data information and the dictionary;

and decompressing the compressed data by utilizing the dictionary information.

Optionally, the dictionary information includes at least one of:

mapping relation between data stream and dictionary;

mapping relation between data packet length and dictionary;

and carrying the mapping relation between the information and the dictionary.

Optionally, the bearer information includes an identifier of a bearer.

Optionally, the method further comprises receiving the dictionary information via a message of one of the following forms:

radio resource control, RRC, signaling, or;

a packet data unit PDU through a packet data convergence protocol PDCP, or;

through the PDCP header.

or, the dictionary information is pre-configured by the core network;

alternatively, the dictionary information is pre-stored.

The data transmission device provided by the embodiment of the application is applied to a compression end, and comprises:

a memory for storing program instructions;

a processor for calling the program instructions stored in the memory and executing according to the obtained program:

and sending the compressed data to a receiving end.

Optionally, the dictionary information includes at least one of:

mapping relation between data stream and dictionary;

mapping relation between data packet length and dictionary;

and carrying the mapping relation between the information and the dictionary.

Optionally, the bearer information includes an identifier of a bearer.

Optionally, the processor is further configured to: sending the dictionary information to a decompression end through a message in one of the following forms:

radio resource control, RRC, signaling, or;

a packet data unit PDU through a packet data convergence protocol PDCP, or;

through the PDCP header.

or, the dictionary information is pre-configured by the core network;

alternatively, the dictionary information is pre-stored.

The data transmission device provided by the embodiment of the application is applied to a decompression end, and comprises:

a memory for storing program instructions;

and decompressing the compressed data by utilizing the dictionary information.

Optionally, the dictionary information includes at least one of:

mapping relation between data stream and dictionary;

mapping relation between data packet length and dictionary;

and carrying the mapping relation between the information and the dictionary.

Optionally, the bearer information includes an identifier of a bearer.

Optionally, the processor is further configured to: receiving the dictionary information via a message of one of the following forms:

radio resource control, RRC, signaling, or;

a packet data unit PDU through a packet data convergence protocol PDCP, or;

through the PDCP header.

or, the dictionary information is pre-configured by the core network;

alternatively, the dictionary information is pre-stored.

the compression unit is used for compressing the data according to dictionary information containing the mapping relation between the data information and the dictionary to generate compressed data;

and the sending unit is used for sending the compressed data to a receiving end.

Optionally, the dictionary information includes at least one of:

mapping relation between data stream and dictionary;

mapping relation between data packet length and dictionary;

and carrying the mapping relation between the information and the dictionary.

Optionally, the bearer information includes an identifier of a bearer.

Optionally, the sending unit is further configured to: sending the dictionary information to a decompression end through a message in one of the following forms:

radio resource control, RRC, signaling, or;

a packet data unit PDU through a packet data convergence protocol PDCP, or;

through the PDCP header.

or, the dictionary information is pre-configured by the core network;

alternatively, the dictionary information is pre-stored.

the receiving unit is used for receiving compressed data obtained by compressing dictionary information containing the mapping relation between the data information and the dictionary;

and the decompression unit is used for decompressing the compressed data by utilizing the dictionary information.

Optionally, the dictionary information includes at least one of:

mapping relation between data stream and dictionary;

mapping relation between data packet length and dictionary;

and carrying the mapping relation between the information and the dictionary.

Optionally, the bearer information includes an identifier of a bearer.

Optionally, the receiving unit is further configured to: receiving the dictionary information via a message of one of the following forms:

radio resource control, RRC, signaling, or;

a packet data unit PDU through a packet data convergence protocol PDCP, or;

through the PDCP header.

or, the dictionary information is pre-configured by the core network;

alternatively, the dictionary information is pre-stored.

Another embodiment of the present application provides a computing device, which includes a memory and a processor, wherein the memory is used for storing program instructions, and the processor is used for calling the program instructions stored in the memory and executing any one of the above methods according to the obtained program.

Another embodiment of the present application provides a computer storage medium having stored thereon computer-executable instructions for causing a computer to perform any one of the methods described above.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.

Fig. 1 is a schematic flowchart of a data transmission method at a sending end according to an embodiment of the present application;

fig. 2 is a schematic flowchart of a data transmission method at a receiving end according to an embodiment of the present disclosure;

fig. 3 is a schematic structural diagram of a data transmission apparatus at a sending end according to an embodiment of the present application;

fig. 4 is a schematic structural diagram of a data transmission apparatus at a receiving end according to an embodiment of the present disclosure;

fig. 5 is a schematic structural diagram of another data transmission apparatus at a sending end according to an embodiment of the present application;

fig. 6 is a schematic structural diagram of another data transmission apparatus at a receiving end according to an embodiment of the present disclosure.

Detailed Description

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

The method and the device are based on the same application concept, and because the principles of solving the problems of the method and the device are similar, the implementation of the device and the method can be mutually referred, and repeated parts are not repeated.

The technical scheme provided by the embodiment of the application can be suitable for various systems, particularly 5G systems. For example, the applicable system may be a global system for mobile communication (GSM) system, a Code Division Multiple Access (CDMA) system, a Wideband Code Division Multiple Access (WCDMA) General Packet Radio Service (GPRS) system, a Long Term Evolution (LTE) system, an LTE Frequency Division Duplex (FDD) system, an LTE Time Division Duplex (TDD), a Universal Mobile Telecommunications System (UMTS), a universal microwave Access (WiMAX) system, a 5G NR system, and the like. These various systems include terminal devices and network devices.

The terminal device referred to in the embodiments of the present application may refer to a device providing voice and/or data connectivity to a user, a handheld device having a wireless connection function, or other processing device connected to a wireless modem. The names of the terminal devices may also be different in different systems, for example, in a 5G system, the terminal devices may be referred to as User Equipments (UEs). Wireless terminal devices, which may be mobile terminal devices such as mobile telephones (or "cellular" telephones) and computers with mobile terminal devices, e.g., mobile devices that may be portable, pocket, hand-held, computer-included, or vehicle-mounted, communicate with one or more core networks via the RAN. Examples of such devices include Personal Communication Service (PCS) phones, cordless phones, Session Initiated Protocol (SIP) phones, Wireless Local Loop (WLL) stations, Personal Digital Assistants (PDAs), and the like. The wireless terminal device may also be referred to as a system, a subscriber unit (subscriber unit), a subscriber station (subscriber station), a mobile station (mobile), a remote station (remote station), an access point (access point), a remote terminal device (remote terminal), an access terminal device (access terminal), a user terminal device (user terminal), a user agent (user agent), and a user device (user device), which are not limited in this embodiment of the present application.

The network device according to the embodiment of the present application may be a base station, and the base station may include a plurality of cells. A base station may also be referred to as an access point, or a device in an access network that communicates over the air-interface, through one or more sectors, with wireless terminal devices, or by other names, depending on the particular application. The network device may be configured to interconvert received air frames with Internet Protocol (IP) packets as a router between the wireless terminal device and the rest of the access network, which may include an Internet Protocol (IP) communication network. The network device may also coordinate attribute management for the air interface. For example, the network device according to the embodiment of the present application may be a Base Transceiver Station (BTS) in a global system for mobile communications (GSM) or a Code Division Multiple Access (CDMA), may also be a network device (NodeB) in a Wideband Code Division Multiple Access (WCDMA), may also be an evolved network device (eNB or e-NodeB) in a Long Term Evolution (LTE) system, a 5G base station in a 5G network architecture (next generation system), and may also be a home evolved node B (HeNB), a relay node (relay node), a home base station (femto), a pico base station (pico), and the like, which are not limited in the embodiments of the present application.

Various embodiments of the present application will be described in detail below with reference to the accompanying drawings. It should be noted that the display sequence of the embodiment of the present application only represents the sequence of the embodiment, and does not represent the merits of the technical solutions provided by the embodiments.

In the prior art, a dynamic dictionary cannot be used in an RLC UM mode, and the meaning of the dynamic dictionary is as follows: the compression end (i.e., the transmission end) and the decompression end (i.e., the reception end) may update the dictionary information according to the compression status. However, for other compression services, i.e. compression services other than UDC, if the RLC UM mode causes compression problems, the technical solution provided by the embodiment of the present application may be used.

The technical scheme provided by the embodiment of the application is suitable for a terminal side and a network side, and comprises the following steps:

the UE or the network side performs data compression/decompression according to the dictionary information;

when the compression end is a terminal, the dictionary information is sent by the base station;

or the dictionary information is pre-configured by the core network;

or, the dictionary information is pre-stored;

the dictionary information is sent to the decompression end through a message in one of the following forms, or the dictionary information is received from the compression end through a message in one of the following forms:

radio Resource Control (RRC) signaling;

PDCP control Packet Data Unit (PDU);

packet Data Convergence Protocol (PDCP) header.

The dictionary information may include a mapping relationship between a DRB (Data RB, Data bearer between the terminal and the base station) and a dictionary;

or, the dictionary information may include a mapping relationship between a data stream and a dictionary;

or, the dictionary information may include a mapping relationship between a Data packet (Service Data Unit (SDU)/PDU) and a dictionary;

or, the dictionary information may include a mapping relationship between a Radio Link Control (RLC) mode and a dictionary.

The first embodiment is as follows: the UE selects a dictionary according to dictionary information, wherein the dictionary information comprises mapping relation between bearing information and the dictionary, mapping relation between data flow and the dictionary, mapping relation between data packet length and the dictionary, mapping relation between Radio Link Control (RLC) mode and the dictionary, and Quality of Service (QoS) information.

The method comprises the following steps: the UE stores a plurality of dictionaries in advance.

Specifically, the dictionaries may be configured by an operator, for example, the dictionary is sent to the UE through a broadcast message/a dedicated signaling, and further, the network side may send the dictionary corresponding to the bearer information to the UE according to the bearer information established by the UE; or, the network side may send the dictionary corresponding to the capability of the UE to the UE according to the capability of the UE. Optionally, before the base station sends the dictionary to the UE, the UE sends dictionary request information to the base station, and the base station sends the dictionary to the UE based on the request of the UE.

The dictionary may also be pre-stored by the UE, for example, in a Subscriber Identity Module (SIM).

Step two: the UE performs a data compression process according to the dictionary information.

The UE performs a data compression procedure. Optionally, the UE selects a dictionary according to the dictionary information to perform compression. The dictionary information may be indication information sent by a network, such as network side indication information, core network configuration information, or stored compression indication information, and is used to indicate a mapping relationship between a dictionary and data to be compressed.

Mode 1), dictionary information may be a mapping relationship between the bearer attribute of the data to be compressed and the dictionary. For example, the dictionary corresponding to the DRB1 configured by the network side is dictionary 1, and the dictionary corresponding to the DRB2 configured by the network side is dictionary 2. Then, when compressing the data on the DRB1, the UE selects the dictionary 1 to perform compression according to the dictionary information, and then sends the compressed data to the network side. Similarly, when compressing the data on the DRB2, the UE selects the dictionary 2 to perform compression, and then sends the compressed data to the network side. Thus, on the PDCP side, different bearers can perform compression according to different dictionaries, resulting in higher compression efficiency.

Certainly, the mapping relationship between the bearers and the dictionaries may be one-to-many, that is, one DRB may correspond to multiple dictionaries, and the UE may select the packet length; or many-to-one, that is, a plurality of DRBs correspond to one dictionary; and may be one-to-one, which is not limited herein.

Mode 2), in another possible mode, the dictionary information may be a mapping relationship between the data stream attribute of the data to be compressed and the dictionary. For example, the corresponding data flow in the current PDCP entity may be multiple (specifically mapped according to the SDAP layer). For example, the dictionary corresponding to the data flow 1 is configured to be the dictionary 1 on the network side, and the dictionary corresponding to the data flow 2 is the dictionary 2. Then when compressing the data on the data stream 1, the UE selects the dictionary to perform compression according to the indication information, and sends the compressed data to the network side. Similarly, when compressing the data on the data stream 2, the UE selects the dictionary 2 to perform compression, and then sends the compressed data to the network side. Thus, at the PDCP side, the load is refined to data flows, and different data flows are compressed according to different dictionaries, so that the compression efficiency is improved.

Of course, the mapping relationship between the data stream and the dictionary may be one-to-many, that is, one data stream may correspond to multiple dictionaries, and the UE may further select which dictionary according to the packet length; or many-to-one, that is, a plurality of data streams correspond to a dictionary; and may be one-to-one, which is not limited herein.

Mode 3), dictionary information may be a correspondence between packet lengths and dictionaries.

Specifically, the network sends the mapping relation of different data lengths corresponding to different dictionaries to the UE. For example, the byte length 0-x of a data packet corresponds to dictionary 1, the byte length x + 1-y of the data packet corresponds to dictionary 2, the byte length y + 1-z of the data packet corresponds to dictionary 3, and so on. Then, when the lengths of the PDCP SDU packets of the UE correspond to different length sections, respectively, data compression is performed through the relation between the PDCP SDUs or PDUs and the dictionary.

Mode 4), dictionary information may be a correspondence between RLC modes configured by the network side and dictionaries.

In this case, the network configures the UE to select the dictionary according to the RLC mode.

If the RLC mode configured on the network side is AM mode, the UE will perform compression of the dynamic dictionary, i.e. the dictionary is updated according to the real-time compression. When the RLC mode configured on the network side is the UM mode, then the UE will perform the compression of the static dictionary, i.e. the dictionary is pre-configured.

Step three: and the UE sends dictionary information based on the compression dictionary to the network side so as to facilitate the network side to perform decompression.

This step is an optional step, and if the relationship of the compressed data to the dictionary is unknown to the network, the network side may perform decompression based on the received data.

Example two: and the network side selects a dictionary according to the dictionary information and performs compression.

The method comprises the following steps: the network side prestores a plurality of dictionaries.

In particular, the plurality of dictionaries may be operator configured, and may be configured according to the capability of the UE.

Step two: and the network side executes a data compression process according to the dictionary information.

The network side performs UDC compression. Optionally, the network side selects a dictionary according to the dictionary information to perform compression. The dictionary information may be core network configuration information, or stored compression indication information, and the like, and is used to indicate a mapping relationship between the dictionary and the data to be compressed.

Mode 1), for example, the dictionary information may be a mapping relationship between a bearer attribute of the data to be compressed and the dictionary. For example, the dictionary corresponding to the DRB1 is dictionary 1, and the dictionary corresponding to the DRB2 is dictionary 2. Then, when compressing the data of the DRB1, the network side selects the dictionary 1 to perform compression according to the dictionary information, and then sends the compressed data to the UE. Similarly, when compressing the data on the DRB2, the network side selects the dictionary 2 to perform compression, and then sends the compressed data to the UE. Thus, on the PDCP side, different bearers can perform compression according to different dictionaries, resulting in higher compression efficiency.

Certainly, the mapping relationship between the bearers and the dictionaries may be one-to-many, that is, one DRB may correspond to multiple dictionaries, and the UE may further select which dictionary according to the packet length; the mapping relation between the bearer and the dictionary can also be many-to-one, that is, a plurality of DRBs correspond to one dictionary; and may be one-to-one, which is not limited herein.

Mode 2), in another possible mode, the dictionary information may be a mapping relationship between stream attributes of the data to be compressed and a dictionary. For example, the corresponding Data flow in the current PDCP entity may be multiple (specifically mapped according to a Service Data Adaptation Protocol (SDAP) layer). For example, the dictionary corresponding to the data stream 1 is the dictionary 1, and the dictionary corresponding to the data stream 2 is the dictionary 2, so that when the data on the data stream 1 is compressed, the network side selects the dictionary to perform compression according to the dictionary information, and then sends the compressed data to the UE. Similarly, when compressing the data on the data stream 2, the network side selects the dictionary 2 to perform compression, and then sends the compressed data to the UE. Thus, at the PDCP side, the bearers are refined to data flows, and different data flows are compressed according to different dictionaries, which improves compression efficiency but increases complexity.

Of course, the mapping relationship between the data stream and the dictionary may be one-to-many, that is, one data stream may correspond to multiple dictionaries, and the UE may further select the data stream according to the packet length; or many-to-one, that is, a plurality of data streams correspond to a dictionary; and may be one-to-one, which is not limited herein.

Specifically, the network side stores the mapping relation of different data lengths corresponding to different dictionaries. For example, byte length 0-x corresponds to dictionary 1, byte length x + 1-y corresponds to dictionary 2, byte length y + 1-z corresponds to dictionary 3, and so on. Then, when the lengths of the PDCP SDUs/PDUs at the network side correspond to different length intervals, respectively, the data compression is performed by matching the relationship between the PDCP SDUs or PDUs and the dictionary.

Mode 4), dictionary information may be a corresponding relationship between the RLC mode configured on the network side and the dictionary.

In this case, the network side selects the dictionary according to the RLC mode.

If the RLC mode configured by the network side is the AM mode, the network side executes the compression mode of the dynamic dictionary, namely the dictionary is updated according to the real-time compression condition. When the RLC mode is the UM mode, then the network side will perform the compression of the static dictionary, i.e. pre-configured on the dictionary.

Step three: and the network side sends dictionary information based on the compression dictionary to the UE so as to facilitate the UE to carry out decompression.

This step is an optional step, where the UE performs decompression based on the received data.

The first and second embodiments above are the case where the terminal and the network side are respectively compression sides.

Two embodiments are described below, which are the cases where the terminal and the network side are respectively used as the decompression side.

Example three: and the UE executes the decompression process.

The method comprises the following steps: the UE side prestores a plurality of dictionaries.

The terminal may obtain the dictionary in various ways, such as pre-storing, sending the dictionary to the terminal by the network side, and so on.

Step two: and after receiving the compressed data, the UE performs data decompression.

Optionally, the UE performs a decompression process according to the indication information of the network side.

Specifically, the indication information may include one or more information in a dictionary, a mapping relationship between the dictionary and the data, a dictionary index number, and the like. The information may be sent to the UE via one or more signaling. The indication to the UE may be through RRC signaling, or may be through PDCP control PDU, or header of PDCP. And will not be described in detail herein.

The mapping relationship between the dictionary and the compressed data is implemented in the same way, for example:

may be a mapping relationship between the bearer property of the compressed data and the dictionary;

may be a mapping relationship between the data stream properties of the compressed data and the dictionary;

may be the correspondence of packet length to dictionary;

the correspondence between the RLC mode and the dictionary may be used.

Example four: the network side performs the decompression process.

Step two: and after receiving the compressed data, the network side performs data decompression.

Optionally, before the network performs decompression, a mapping relationship between the dictionary and the compressed data sent by the core network/UE is received, where the mapping relationship may also be stored by the network itself. And will not be described in detail herein.

The specific mapping relationship may be:

1) mapping relation between data load and dictionary; for example, the specific DRB1 corresponds to dictionary 1 and DRB2 corresponds to dictionary 2. When the network side receives the data of the DRB1, decompression is performed according to the dictionary 1; when compressed data on the DRB2 is received, decompression is performed as per dictionary 2.

2) And mapping relationship between the data stream and the dictionary, for example, data stream 1 corresponds to dictionary 1, and data stream 2 corresponds to dictionary 2. Meanwhile, the PDCP at the network side acquires information of the data flow through the SDAP, and performs data decompression according to the dictionary 1 if the received data belongs to the data flow 1, and performs data decompression according to the dictionary 2 if the received data belongs to the data flow 2.

3) And the mapping relation between the data packet length and the dictionary. For example, byte length 0-x corresponds to dictionary 1, byte length x + 1-y corresponds to dictionary 2, byte length y + 1-z corresponds to dictionary 3, and so on. Then, when the lengths of the PDCP SDUs/PDUs received by the network side correspond to different byte length intervals respectively, the data decompression is executed by matching the relation between the lengths of the PDCP SDUs or the PDUs and the dictionary.

In summary, referring to fig. 1, a data transmission method provided in the embodiment of the present application is applied to a compression end (i.e. a sending end), and the method includes:

s101, compressing data according to dictionary information containing mapping relations between data information and a dictionary to generate compressed data;

s102, sending the compressed data to a receiving end.

Optionally, the dictionary information includes at least one of:

mapping relation between data stream and dictionary;

mapping relation between data packet length and dictionary;

and carrying the mapping relation between the information and the dictionary.

Optionally, the bearer information includes an identifier of a bearer. Of course, the bearer information may also include other information.

radio resource control, RRC, signaling, or;

a packet data unit PDU through a packet data convergence protocol PDCP, or;

through the PDCP header.

Optionally, the dictionary information is sent by the base station, or is preconfigured by the core network, or is pre-stored.

Accordingly, referring to fig. 2, an embodiment of the present application provides a data transmission method applied to a decompression end (i.e., a receiving end), where the method includes:

s201, receiving compressed data obtained by compressing dictionary information according to the mapping relation between the data information and the dictionary;

s202, decompressing the compressed data by utilizing the dictionary information.

Optionally, the dictionary information includes at least one of:

mapping relation between data stream and dictionary;

mapping relation between data packet length and dictionary;

and carrying the mapping relation between the information and the dictionary.

Optionally, the bearer information includes an identifier of a bearer.

radio resource control, RRC, signaling, or;

a packet data unit PDU through a packet data convergence protocol PDCP, or;

through the PDCP header.

Referring to fig. 3, a data transmission apparatus provided in an embodiment of the present application is applied to a compression end, and the apparatus includes:

a memory 520 for storing program instructions;

a processor 500 for calling the program instructions stored in the memory, and executing, according to the obtained program:

and sending the compressed data to a receiving end.

Optionally, the dictionary information includes at least one of:

mapping relation between data stream and dictionary;

mapping relation between data packet length and dictionary;

and carrying the mapping relation between the information and the dictionary.

Optionally, the bearer information includes an identifier of a bearer.

Optionally, the processor 500 is further configured to: sending the dictionary information to a decompression end through a message in one of the following forms:

radio resource control, RRC, signaling, or;

a packet data unit PDU through a packet data convergence protocol PDCP, or;

through the PDCP header.

A transceiver 510 for receiving and transmitting data under the control of the processor 500.

Where in fig. 3, the bus architecture may include any number of interconnected buses and bridges, with various circuits being linked together, particularly one or more processors represented by processor 500 and memory represented by memory 520. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further herein. The bus interface provides an interface. The transceiver 510 may be a number of elements, including a transmitter and a transceiver, providing a means for communicating with various other apparatus over a transmission medium. The processor 500 is responsible for managing the bus architecture and general processing, and the memory 520 may store data used by the processor 500 in performing operations.

The processor 500 may be a Central Processing Unit (CPU), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA), or a Complex Programmable Logic Device (CPLD).

It should be noted that both the compression end and the decompression end provided in the embodiments of the present application may be terminals, or may be network side devices.

Referring to fig. 4, a data transmission apparatus provided in an embodiment of the present application is applied to a decompression end, and the apparatus includes:

a memory 620 for storing program instructions;

a processor 600, configured to call the program instructions stored in the memory, and execute, according to the obtained program:

and decompressing the compressed data by utilizing the dictionary information.

Optionally, the dictionary information includes at least one of:

mapping relation between data stream and dictionary;

mapping relation between data packet length and dictionary;

and carrying the mapping relation between the information and the dictionary.

Optionally, the bearer information includes an identifier of a bearer.

Optionally, the processor 600 is further configured to: receiving the dictionary information via a message of one of the following forms:

radio resource control, RRC, signaling, or;

a packet data unit PDU through a packet data convergence protocol PDCP, or;

through the PDCP header.

A transceiver 610 for receiving and transmitting data under the control of the processor 600.

Where in fig. 4, the bus architecture may include any number of interconnected buses and bridges, with various circuits being linked together, particularly one or more processors represented by processor 600 and memory represented by memory 620. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further herein. The bus interface provides an interface. The transceiver 610 may be a number of elements including a transmitter and a receiver that provide a means for communicating with various other apparatus over a transmission medium. For different user devices, the user interface 630 may also be an interface capable of interfacing with a desired device externally, including but not limited to a keypad, display, speaker, microphone, joystick, etc.

The processor 600 is responsible for managing the bus architecture and general processing, and the memory 620 may store data used by the processor 600 in performing operations.

Alternatively, the processor 600 may be a CPU (central processing unit), an ASIC (Application Specific Integrated Circuit), an FPGA (Field Programmable Gate Array), or a CPLD (Complex Programmable Logic Device).

Referring to fig. 5, a data transmission apparatus provided in an embodiment of the present application is applied to a compression end, and the apparatus includes:

the compression unit 11 is configured to compress data according to dictionary information including a mapping relationship between data information and a dictionary, and generate compressed data;

a sending unit 12, configured to send the compressed data to a receiving end.

Optionally, the dictionary information includes at least one of:

mapping relation between data stream and dictionary;

mapping relation between data packet length and dictionary;

and carrying the mapping relation between the information and the dictionary.

Optionally, the bearer information includes an identifier of a bearer.

Optionally, the sending unit 12 is further configured to: sending the dictionary information to a decompression end through a message in one of the following forms:

radio resource control, RRC, signaling, or;

a packet data unit PDU through a packet data convergence protocol PDCP, or;

through the PDCP header.

Referring to fig. 6, a data transmission apparatus provided in an embodiment of the present application is applied to a decompression end, and the apparatus includes:

a receiving unit 21, configured to receive compressed data obtained by compressing dictionary information including a mapping relationship between data information and a dictionary;

a decompressing unit 22, configured to decompress the compressed data by using the dictionary information.

Optionally, the dictionary information includes at least one of:

mapping relation between data stream and dictionary;

mapping relation between data packet length and dictionary;

and carrying the mapping relation between the information and the dictionary.

Optionally, the bearer information includes an identifier of a bearer.

Optionally, the receiving unit 21 is further configured to: receiving the dictionary information via a message of one of the following forms:

radio resource control, RRC, signaling, or;

a packet data unit PDU through a packet data convergence protocol PDCP, or;

through the PDCP header.

It should be noted that the division of the unit in the embodiment of the present application is schematic, and is only a logic function division, and there may be another division manner in actual implementation. In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.

The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application may be substantially implemented or contributed by the prior art, or all or part of the technical solution may be embodied in a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, a network device, or the like) or a processor (processor) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.

The embodiment of the present application provides a computing device, which may specifically be a desktop computer, a portable computer, a smart phone, a tablet computer, a Personal Digital Assistant (PDA), and the like. The computing device may include a Central Processing Unit (CPU), memory, input/output devices, etc., the input devices may include a keyboard, mouse, touch screen, etc., and the output devices may include a Display device, such as a Liquid Crystal Display (LCD), a Cathode Ray Tube (CRT), etc.

The memory may include Read Only Memory (ROM) and Random Access Memory (RAM), and provides the processor with program instructions and data stored in the memory. In the embodiments of the present application, the memory may be used for storing a program of any one of the methods provided by the embodiments of the present application.

The processor is used for executing any one of the methods provided by the embodiment of the application according to the obtained program instructions by calling the program instructions stored in the memory.

Embodiments of the present application provide a computer storage medium for storing computer program instructions for an apparatus provided in the embodiments of the present application, which includes a program for executing any one of the methods provided in the embodiments of the present application.

The computer storage media may be any available media or data storage device that can be accessed by a computer, including, but not limited to, magnetic memory (e.g., floppy disks, hard disks, magnetic tape, magneto-optical disks (MOs), etc.), optical memory (e.g., CDs, DVDs, BDs, HVDs, etc.), and semiconductor memory (e.g., ROMs, EPROMs, EEPROMs, non-volatile memory (NAND FLASH), Solid State Disks (SSDs)), etc.

The method provided by the embodiment of the application can be applied to terminal equipment and also can be applied to network equipment.

The Terminal device may also be referred to as a User Equipment (User Equipment, abbreviated as "UE"), a Mobile Station (Mobile Station, abbreviated as "MS"), a Mobile Terminal (Mobile Terminal), or the like, and optionally, the Terminal may have a capability of communicating with one or more core networks through a Radio Access Network (RAN), for example, the Terminal may be a Mobile phone (or referred to as a "cellular" phone), a computer with Mobile property, or the like, and for example, the Terminal may also be a portable, pocket, hand-held, computer-built-in, or vehicle-mounted Mobile device.

A network device may be a base station (e.g., access point) that refers to a device in an access network that communicates over the air-interface, through one or more sectors, with wireless terminals. The base station may be configured to interconvert received air frames and IP packets as a router between the wireless terminal and the rest of the access network, which may include an Internet Protocol (IP) network. The base station may also coordinate management of attributes for the air interface. For example, the Base Station may be a Base Transceiver Station (BTS) in GSM or CDMA, a Base Station (NodeB) in WCDMA, an evolved Node B (NodeB or eNB or e-NodeB) in LTE, or a gNB in 5G system. The embodiments of the present application are not limited.

The above method process flow may be implemented by a software program, which may be stored in a storage medium, and when the stored software program is called, the above method steps are performed.

To sum up, in the technical solution provided in the embodiment of the present application, the compression end and the decompression end perform data compression/decompression according to the mapping relationship between the compressed data and the dictionary. Therefore, the problem of low compression efficiency caused by packet loss in the RLC UM mode is solved.

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

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

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

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

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

Claims

1. A data transmission method is applied to a compression end, and is characterized in that the method comprises the following steps:

sending the compressed data to a receiving end;

the dictionary information comprises a mapping relation between a Radio Link Control (RLC) mode and a dictionary; in this case, the network side configures the terminal to select the dictionary according to the RLC mode; when the RLC mode configured on the network side is the AM mode, the dictionary selected by the terminal is a dictionary updated according to the real-time compression condition; when the RLC mode configured by the network side is the UM mode, the dictionary selected by the terminal is a pre-configured dictionary;

or, the dictionary information includes: a mapping of data flows to dictionaries and a mapping of radio link control, RLC, modes to dictionaries.

2. The method of claim 1, further comprising sending the dictionary information to a decompressor by a message of one of the following forms:

radio resource control, RRC, signaling, or;

a packet data unit PDU through a packet data convergence protocol PDCP, or;

through the PDCP header.

3. The method of claim 1, wherein when the compressing end is a terminal, the dictionary information is transmitted by a base station;

or, the dictionary information is pre-configured by the core network;

alternatively, the dictionary information is pre-stored.

4. A data transmission method is applied to a decompression end, and is characterized in that the method comprises the following steps:

decompressing the compressed data by using the dictionary information;

5. The method of claim 4, further comprising receiving the dictionary information via a message of one of the following forms:

radio resource control, RRC, signaling, or;

a packet data unit PDU through a packet data convergence protocol PDCP, or;

through the PDCP header.

6. The method of claim 4, wherein the dictionary information is sent by the base station, or is pre-configured by the core network, or is pre-stored.

7. A data transmission apparatus applied to a compression end, the apparatus comprising:

a memory for storing program instructions;

sending the compressed data to a receiving end;

8. The apparatus of claim 7, wherein the processor is further configured to: sending the dictionary information to a decompression end through a message in one of the following forms:

radio resource control, RRC, signaling, or;

a packet data unit PDU through a packet data convergence protocol PDCP, or;

through the PDCP header.

9. The apparatus of claim 7, wherein when the compressing end is a terminal, the dictionary information is transmitted by a base station;

or, the dictionary information is pre-configured by the core network;

alternatively, the dictionary information is pre-stored.

10. A data transmission apparatus applied to a decompression end, the apparatus comprising:

a memory for storing program instructions;

decompressing the compressed data by using the dictionary information;

11. The apparatus of claim 10, wherein the processor is further configured to: receiving the dictionary information via a message of one of the following forms:

radio resource control, RRC, signaling, or;

a packet data unit PDU through a packet data convergence protocol PDCP, or;

through the PDCP header.

12. The apparatus of claim 10, wherein when the compressing end is a terminal, the dictionary information is transmitted by a base station;

or, the dictionary information is pre-configured by the core network;

alternatively, the dictionary information is pre-stored.

13. A data transmission apparatus applied to a compression end, the apparatus comprising:

a sending unit, configured to send the compressed data to a receiving end;

14. The apparatus of claim 13, wherein the sending unit is further configured to: sending the dictionary information to a decompression end through a message in one of the following forms:

radio resource control, RRC, signaling, or;

a packet data unit PDU through a packet data convergence protocol PDCP, or;

through the PDCP header.

15. The apparatus of claim 13, wherein the dictionary information is sent by the base station, or is pre-configured by the core network, or is pre-stored.

16. A data transmission apparatus applied to a decompression end, the apparatus comprising:

the decompression unit is used for decompressing the compressed data by utilizing the dictionary information;

17. The apparatus of claim 16, wherein the receiving unit is further configured to: receiving the dictionary information via a message of one of the following forms:

radio resource control, RRC, signaling, or;

a packet data unit PDU through a packet data convergence protocol PDCP, or;

through the PDCP header.

18. The apparatus of claim 16, wherein when the compressing end is a terminal, the dictionary information is transmitted by a base station;

or, the dictionary information is pre-configured by the core network;

alternatively, the dictionary information is pre-stored.

19. A computer storage medium having stored thereon computer-executable instructions for causing a computer to perform the method of any one of claims 1 to 6.