CN111163081B

CN111163081B - Data transmission method, device, equipment and storage medium

Info

Publication number: CN111163081B
Application number: CN201911370974.8A
Authority: CN
Inventors: 胥进
Original assignee: Spreadtrum Communications Shanghai Co Ltd
Current assignee: Spreadtrum Communications Shanghai Co Ltd
Priority date: 2019-12-26
Filing date: 2019-12-26
Publication date: 2022-04-22
Anticipated expiration: 2039-12-26
Also published as: CN111163081A

Abstract

The data transmission method, apparatus, device and storage medium provided by this embodiment include: the PDCP entity obtains at least one PDCP service data unit SDU and buffers each PDCP SDU in a PDCP SDU buffer area, the PDCP entity obtains a PDCP protocol data unit PDU corresponding to each PDCP SDU, and the PDCP entity sends the at least one PDCP PDU to the RLC entity and releases the at least one PDCP SDU at the same time. In the application, the PDCP entity sends the PDCP PDU to the RLC entity and simultaneously immediately releases the corresponding PDCP SDU from the PDCP SDU buffer area, thereby reducing the memory overhead, and the SDU which applies for the memory firstly releases the memory, thereby improving the convenience of memory management.

Description

Data transmission method, device, equipment and storage medium

Technical Field

The embodiment of the invention relates to the technical field of wireless communication, in particular to a data transmission method, a data transmission device, data transmission equipment and a storage medium.

Background

In Long Term Evolution (LTE) and 5G New Radio systems, after a Packet Data Convergence Protocol (PDCP) Layer receives user plane Data in an Internet Protocol (IP) Packet format, the user plane Data is transmitted between a transmitting device and a receiving device via a Radio Link Control (RLC), a Media Access Control (MAC), and a Physical Layer in sequence.

At present, after receiving an IP Data packet, i.e. a PDCP Service Data Unit (SDU), the PDCP stores the PDCP SDU in a PDCP SDU Buffer, and then performs related processing on the PDCP SDU, for example: header compression, ciphering and integrity protection, generating a PDCP Protocol Data Unit PDU (Protocol Data Unit, PDU), then sending to the RLC, and buffering in an RLC SDU Buffer of the RLC, in the process, when the RLC receives a message which indicates that the PDCP PDU is successfully received by the network equipment and is sent by the network equipment, the PDCP releases the PDCP SDU corresponding to the PDCP PDU.

However, before the RLC does not receive the message indicating successful reception, the PDCP may not release the corresponding PDCP SDU, so that one PDCP SDU is buffered in two parts, one part is buffered in the PDCP SDU Buffer and the other part is buffered in the RLC SDU Buffer, which increases memory overhead, and the life cycle of the memory used by the PDCP SDU is prolonged, which also increases memory overhead.

Disclosure of Invention

The application provides a data transmission method, a data transmission device, data transmission equipment and a data transmission storage medium, which are used for solving the problems that in the prior art, one PDCP SDU is cached for two times, and the life cycle of a memory used by the PDCP SDU is prolonged, so that the memory overhead is large.

In a first aspect, an embodiment of the present application provides a data transmission method, which is applied to a user equipment, where the user equipment includes a packet data convergence protocol layer PDCP entity and a radio link control layer RLC entity, and the method includes:

the PDCP entity acquires at least one PDCP service data unit SDU and buffers each PDCP SDU in a PDCP SDU buffer area;

the PDCP entity acquires a PDCP protocol data unit PDU corresponding to each PDCP SDU;

the PDCP entity releases at least one PDCP SDU from the PDCP SDU buffer while transmitting the at least one PDCP PDU to the RLC entity.

Further, when the data radio bearer configures header compression, the method further includes:

the PDCP entity buffers an IP related header in the PDCP SDU, wherein the PDCP SDU is an Internet Protocol (IP) data packet including an IP related header and an IP data part.

Further, the method further comprises:

the PDCP entity performs reverse decryption on the PDCP PDUs which are already sent to the RLC entity but do not receive an acknowledgement message in the at least one PDCP PDU to obtain a data part of the PDCP PDUs, wherein the acknowledgement message is used for indicating network equipment to successfully receive the PDCP PDUs sent by the user equipment;

the PDCP entity acquires a retransmitted PDCP SDU according to the cached IP related head corresponding to the PDCP SDU data part corresponding to the PDCP PDU and the PDCP PDU data part;

and the PDCP entity acquires a new PDCP PDU corresponding to the retransmitted PDCP SDU and sends the new PDCP PDU to the RLC entity.

Further, the PDCP entity obtains the retransmitted PDCP SDU according to the buffered IP related header corresponding to the PDCP PDU data part and the PDCP PDU data part, including:

the PDCP entity acquires the retransmitted PDCP SDU according to the cached IP related header and an IP data part in the PDCP PDU data part, wherein the PDCP PDU data part comprises the compressed IP related header and the IP data part;

correspondingly, the acquiring, by the PDCP entity, the new PDCP PDU corresponding to the retransmitted PDCP SDU includes:

the PDCP entity performs header compression on the cached IP related header again to obtain the IP related header after the header compression is performed again;

the PDCP entity encrypts the IP related head and the IP data part after the recompression by adopting new encryption parameters to obtain an encrypted PDCP PDU data part;

the PDCP entity generates a new head of the PDCP PDU by adopting the new PDCP identification information;

and the PDCP entity acquires a new PDCP PDU according to the encrypted PDCP PDU data part and the new head of the PDCP PDU.

Further, when a Data Radio Bearer (DRB) is not configured with Header Compression (ROHC), the method further includes:

the PDCP entity acquires a retransmitted PDCP SDU according to the PDCP PDU data part, wherein the PDCP PDU data part comprises an IP related head and an IP data part;

Further, the acquiring, by the PDCP entity, a new PDCP PDU corresponding to the retransmitted PDCP SDU includes:

the PDCP entity encrypts the IP related head and the IP data part by adopting new encryption parameters to obtain an encrypted PDCP PDU data part;

and the PDCP entity acquires the new PDCP PDU according to the PDCP PDU data part and the new head of the PDCP PDU.

Further, the IP related header includes:

an IP packet header; or

An IP packet header, a User Datagram Protocol (UDP) packet header; or

An IP packet header, a UDP header, and a Real-time Transport Protocol (RTP) packet header; or

An IP packet header, a Transmission Control Protocol (TCP) packet header; or

IP data packet head, message safety packaging protocol ESP data packet head.

In a second aspect, an embodiment of the present application provides a PDCP entity, including:

a first obtaining module, configured to obtain at least one PDCP service data unit SDU, and buffer each PDCP SDU in a PDCP SDU buffer;

a second obtaining module, configured to obtain a PDCP protocol data unit PDU corresponding to each PDCP SDU;

a sending module, configured to release at least one PDCP SDU from the PDCP SDU buffer while sending the at least one PDCP PDU to the RLC entity.

and the storage module is used for caching the IP related head in the PDCP SDU, wherein the PDCP SDU is an Internet protocol IP data packet, and the IP data packet comprises the IP related head and an IP data part.

Further, still include:

a first de-ciphering module, configured to de-decipher, from the at least one PDCP PDU, a PDCP PDU that has been sent to the RLC entity but has not received an acknowledgement message, and obtain a data part of the PDCP PDU, where the acknowledgement message is used to indicate that network equipment successfully receives the PDCP PDU sent by the user equipment;

a third obtaining module, configured to obtain a retransmitted PDCP SDU according to a buffered IP-related header corresponding to the PDCP PDU data part and the PDCP PDU data part;

and a fourth obtaining module, configured to obtain a new PDCP PDU corresponding to the retransmitted PDCP SDU, and send the new PDCP PDU to the RLC entity.

Further, the third obtaining module is specifically configured to:

acquiring the retransmitted PDCP SDU according to the cached IP related header and an IP data part in the PDCP PDU data part, wherein the PDCP PDU data part comprises the compressed IP related header and the IP data part;

correspondingly, the fourth obtaining module is specifically configured to:

performing header compression on the cached IP related header again to obtain the IP related header after the header compression is performed again;

encrypting the recompressed IP related header and the IP data part by adopting new encryption parameters to obtain an encrypted PDCP PDU data part;

generating a new head of the PDCP PDU by adopting the new PDCP identification information;

and acquiring a new PDCP PDU according to the encrypted PDCP PDU data part and the new head of the PDCP PDU.

Further, when the data radio bearer is not configured with header compression, the method further includes:

a second de-ciphering module, configured to de-decipher, from the at least one PDCP PDU, a PDCP PDU that has been sent to the RLC entity but has not received an acknowledgement message, and obtain a data part of the PDCP PDU, where the acknowledgement message is used to indicate that network equipment successfully receives the PDCP PDU sent by the user equipment;

a fifth obtaining module, configured to obtain a retransmitted PDCP SDU according to the PDCP PDU data portion, where the PDCP PDU data portion includes an IP related header and an IP data portion;

and a sixth obtaining module, configured to obtain a new PDCP PDU corresponding to the retransmitted PDCP SDU, and send the new PDCP PDU to the RLC entity.

Further, the sixth obtaining module is specifically configured to:

encrypting the IP related head and the IP data part by adopting new encryption parameters to obtain an encrypted PDCP PDU data part;

and acquiring the new PDCP PDU according to the PDCP PDU data part and the new head of the PDCP PDU.

Further, the IP related header includes:

an IP packet header; or

An IP data packet header and a User Datagram Protocol (UDP) data packet header; or

An IP data packet header, a UDP header, and a real-time transport protocol RTP data packet header; or

An IP data packet header, a Transmission Control Protocol (TCP) data packet header; or

IP data packet head, message safety packaging protocol ESP data packet head.

In a third aspect, an embodiment of the present application provides an electronic device, including: the device comprises a memory, a processor, a transmitter and a receiver, wherein executable instructions of the processor are stored in the memory; wherein the processor is configured to perform the method of any of the first aspects via execution of the executable instructions.

In a fourth aspect, the present application provides a computer-readable storage medium, on which a computer program is stored, which when executed by a processor implements the method of any one of the first aspect.

The embodiment provides a data transmission method, a data transmission device, data transmission equipment and a storage medium, and the data transmission method comprises the following steps: the PDCP entity obtains at least one PDCP service data unit SDU and buffers each PDCP SDU in a PDCP SDU buffer area, the PDCP entity obtains a PDCP protocol data unit PDU corresponding to each PDCP SDU, and the PDCP entity sends the at least one PDCP PDU to the RLC entity and releases the at least one PDCP SDU at the same time. In the application, the PDCP entity sends the PDCP PDU to the RLC entity and simultaneously immediately releases the PDCP SDU from the PDCP SDU buffer area, thereby reducing the memory overhead, and the SDU which applies for the memory firstly can release the memory firstly, thereby improving the convenience of memory management.

Drawings

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, and it is obvious that the drawings in the following description are some embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to these drawings without inventive exercise.

Fig. 1 is a schematic view of a scene of a data transmission method according to an embodiment of the present application;

fig. 2 is a first schematic flowchart of a data transmission method according to an embodiment of the present application;

fig. 3 is a first schematic diagram of an IP packet according to an embodiment of the present application;

fig. 4 is a second schematic diagram of an IP packet according to an embodiment of the present application;

fig. 5 is a third schematic diagram of an IP packet provided in the embodiment of the present application;

fig. 6 is a fourth schematic diagram of an IP packet provided in the embodiment of the present application;

fig. 7 is a fifth schematic diagram of an IP packet provided in the embodiment of the present application;

fig. 8 is a first schematic diagram illustrating PDCP SDU generating PDCP PDUs according to an embodiment of the present application;

fig. 9 is a second schematic diagram illustrating PDCP SDU generating PDCP PDUs according to an embodiment of the present application;

fig. 10 is a second flowchart illustrating a data transmission method according to an embodiment of the present application;

FIG. 11 is a first schematic diagram illustrating a new PDCP PDU generation process according to an embodiment of the present application;

fig. 12 is a third schematic flowchart of a data transmission method according to an embodiment of the present application;

fig. 13 is a second schematic diagram illustrating a new PDCP PDU generating process according to an embodiment of the present application;

fig. 14 is a first schematic structural diagram of a data transmission device according to an embodiment of the present application;

fig. 15 is a schematic structural diagram of a data transmission device according to an embodiment of the present application;

fig. 16 is a schematic hardware structure diagram of a user equipment according to an embodiment of the present application.

With the above figures, there are shown specific embodiments of the present application, which will be described in more detail below. These drawings and written description are not intended to limit the scope of the inventive concepts in any manner, but rather to illustrate the inventive concepts to those skilled in the art by reference to specific embodiments.

Detailed Description

In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, 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 some embodiments of the present application, but not all 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.

Fig. 1 is a schematic view of a scenario of a data transmission method provided in an embodiment of the present application, as shown in fig. 1, including a user equipment 101 and a network device 102, where the data transmission method provided in the present application may be applied to an LTE communication system and a 5G NR communication system, and may also be applied to other various wireless communication systems, for example: a Global System for Mobile communications (GSM) System, a Code Division Multiple Access (CDMA) System, a Wideband Code Division Multiple Access (WCDMA) System, a General Packet Radio Service (GPRS), a Long Term Evolution (Long Term Evolution, LTE) System, an LTE Frequency Division Duplex (FDD) System, an LTE Time Division Duplex (TDD), a Universal Mobile Telecommunications System (UMTS), and the like.

The network device 102 in the present application may be a Base Transceiver Station (BTS) in Global System for Mobile communication (GSM) or Code Division Multiple Access (CDMA), a Base Station (NodeB, NB) in Wideband Code Division Multiple Access (WCDMA), an evolved Node B (eNB or eNodeB) in LTE, a relay Station or an Access point, or a Base Station in a future 5G network, and the like, which are not limited herein.

User equipment 101 may be a wireless terminal or a wired terminal, and a wireless terminal may be a device that provides voice and/or other traffic data connectivity to a user, a handheld device having wireless connection capability, or other processing device connected to a wireless modem. A wireless terminal, which may be a mobile terminal such as a mobile telephone (or "cellular" telephone) and a computer having a mobile terminal, e.g., a portable, pocket, hand-held, computer-included, or vehicle-mounted mobile device, may communicate with one or more core networks via a Radio Access Network (RAN), and may exchange language and/or data with the RAN. For example, devices such as Personal Communication Service (PCS) phones, cordless phones, Session Initiation Protocol (SIP) phones, Wireless Local Loop (WLL) stations, and Personal Digital Assistants (PDAs) are used. A wireless Terminal 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), a Remote Terminal (Remote Terminal), an Access Terminal (Access Terminal), a User Terminal (User Terminal), a User Agent (User Agent), and a User Device or User Equipment (User Equipment), which are not limited herein.

For the current stage, after the PDCP sends the PDCP PDU to the RLC, the PDCP releases the PDCP SDU corresponding to the PDCP PDU only when the RLC receives a message sent by the network device and indicating that the PDCP PDU has been successfully received by the network device. In the scheme, before the RLC does not receive the message indicating successful reception, the PDCP cannot release the corresponding PDCP SDU, so that one PDCP SDU is cached in two parts, one part is cached in the PDCP SDU Buffer, and the other part is cached in the RLC SDU Buffer, which increases memory overhead, and the life cycle of the memory used by the PDCP SDU is prolonged, which also increases memory overhead.

In order to solve the above problems, in the present application, the PDCP entity sends the PDCP PDU to the RLC entity and simultaneously immediately releases the PDCP SDU, thereby reducing memory overhead, and the SDU which applies for the memory first releases the memory first, thereby improving the convenience of memory management.

The technical solution of the present application will be described in detail below with specific examples. The following several specific embodiments may be combined with each other, and details of the same or similar concepts or processes may not be repeated in some embodiments.

Fig. 2 is a first flowchart of a data transmission method according to an embodiment of the present application, where an execution subject of the method is a user equipment, and the user equipment includes a packet data convergence protocol layer PDCP entity and a radio link control layer RLC entity, where the packet data convergence protocol layer PDCP entity is an entity corresponding to a PDCP protocol layer, and the RLC entity is an entity corresponding to an RLC protocol layer.

As shown in fig. 2, the data transmission method provided in this embodiment includes the following steps:

s201, the PDCP entity obtains at least one PDCP service data unit SDU and buffers each PDCP SDU in a PDCP SDU buffer area.

S202, the PDCP entity acquires a PDCP protocol data unit PDU corresponding to each PDCP SDU.

Wherein, PDCP SDU is an internet protocol IP packet, for example: and service data packets such as internet data packets and voice data packets. Fig. 3 is a first schematic diagram of an IP data packet provided in the embodiment of the present application, fig. 4 is a second schematic diagram of the IP data packet provided in the embodiment of the present application, fig. 5 is a third schematic diagram of the IP data packet provided in the embodiment of the present application, fig. 6 is a fourth schematic diagram of the IP data packet provided in the embodiment of the present application, and fig. 7 is a fifth schematic diagram of the IP data packet provided in the embodiment of the present application.

As shown in fig. 3, the IP packet includes an IP packet header and an IP packet data part (IP Payload).

As shown in fig. 4, the IP packet includes an IP packet Header (IP Header), a UDP packet Header (UDP Header), and a UDP packet data part (UDP Payload).

As shown in fig. 5, the IP packet includes an IP packet Header (IP Header), a UDP packet Header (UDP Header), an RTP packet Header (RTP Header), and an RTP packet data part (RTP Payload).

As shown in fig. 6, the IP packet includes an IP packet Header (IP Header), a TCP packet Header (TCP Header), and a TCP packet data part (TCP Payload).

As shown in fig. 7, the IP packet includes an IP packet Header (IP Header), an ESP packet Header (ESP Header), and an ESP packet data section (ESP Payload).

Of course, the above is merely illustrative of the types of IP packets, and in practical applications, the above IP packets include, but are not limited to, the above IP packets.

When the PDCP entity receives at least one PDCP SDU sent by the upper layer entity, it buffers each PDCP SDU in a PDCP SDU Buffer (Buffer), and when the PDCP entity needs to perform data interaction with the lower layer RLC entity, the PDCP entity performs related processing on each PDCP SDU buffered in the PDCP SDU Buffer, for example: header compression, encryption and integrity protection, and acquiring the PDCP PDU corresponding to each PDCP SDU.

The IP packet types provided in fig. 4 are used as an example for explanation. Fig. 8 is a schematic diagram of generating a PDCP PDU from a PDCP SDU according to an embodiment of the present application, as shown in fig. 7, when a Data Radio Bearer (DRB) configures a Header Compression (ROHC), a PDCP entity performs Header Compression on an IP Header (IP Header and UDP Header in fig. 4) in the received PDCP SDU, encrypts the compressed IP Header and an IP Data portion (UDP packet Data portion in fig. 4) in the PDCP SDU to obtain encrypted Data, acquires PDCP identification information, generates a PDCP Header (PDCP Header) according to the PDCP identification information, and generates a PDCP PDU according to the encrypted Data and the PDCP Header. Wherein, the PDCP identification information may be a sequence number allocated by the PDCP entity for the PDCP SDU.

As can be seen, the PDCP PDU includes a PDCP Header and ciphered data obtained by ciphering the compressed IP-related headers (IP Header and UDP Header) and the IP data part (UDP packet data part in fig. 4).

In the 5G NR communication system, integrity protection processing may be performed on the PDCP header, the compressed IP-related header, and the IP data portion in the PDCP SDU (UDP packet data portion in fig. 4) to obtain an integrity protection parameter MAC-I, and the compressed IP-related header, the IP data portion in the PDCP SDU (UDP packet data portion in fig. 4), and the integrity protection parameter MAC-I may be ciphered to obtain ciphered data, and then the PDCP PDU may be generated according to the PDCP header and the ciphered data.

Therefore, in the 5G NR communication system, integrity protection processing is further required to obtain PDCP PDUs, where the generated PDCP PDUs include PDCP headers and ciphered data, where the ciphered data are obtained by ciphering compressed IP-related headers (IP Header and UDP Header), an IP data portion (UDP packet data portion in fig. 4), and an integrity protection parameter MAC-I.

Similarly, taking the IP packet type provided in fig. 4 as an example for explanation, fig. 9 is a schematic diagram two of generating PDCP PDUs from PDCP SDUs provided in this embodiment, where when a Data Radio Bearer (DRB) is not configured with Header Compression (ROHC), a PDCP entity performs ciphering on IP related headers (IP Header and UDP Header in fig. 4) in the received PDCP SDUs and an IP Data portion (UDP packet Data portion in fig. 4) in the PDCP SDUs to obtain ciphered Data, then acquires PDCP identification information, generates PDCP headers according to the PDCP identification information, and generates PDCP PDUs according to the ciphered Data and the PDCP headers.

Also in the 5G NR communication system, it is also possible to perform integrity protection processing on the PDCP header, the compressed IP-related header, and the IP data part in the PDCP SDU (UDP packet data part in fig. 4) to obtain an integrity protection parameter MAC-I, and perform ciphering on the compressed IP-related header, the IP data part in the PDCP SDU (UDP packet data part in fig. 4), and the integrity protection parameter MAC-I to obtain ciphered data, and then generate a PDCP PDU according to the PDCP header and the ciphered data.

S203, the PDCP entity sends the at least one PDCP PDU to the RLC entity and releases the at least one PDCP SDU from the PDCP SDU buffer area.

When the PDCP entity needs to perform data interaction with the RLC of the lower layer, the PDCP entity sends the acquired at least one PDCP PDU to the RLC entity, and simultaneously immediately releases the at least one PDCP SDU buffered in the PDCP SDU buffer. For the RLC entity, the PDCP PDU sent by the PDCP entity is an RLC SDU, and the RLC entity may further obtain a corresponding RLC PDU according to the RLC SDU and send the RLC PDU to a lower layer entity, so that the user equipment sends the RLC PDU to the network equipment.

When receiving the PDCP PDU sent by the PDCP entity, the RLC entity may buffer the PDCP PDU in an RLC SDU buffer.

Compared with the prior art, the PDCP SDU can be released without waiting for the user equipment to receive the confirmation message sent by the network equipment, so that the memory overhead is reduced.

The data transmission method provided by the embodiment comprises the following steps: the PDCP entity obtains at least one PDCP service data unit SDU and buffers each PDCP SDU in a PDCP SDU buffer area, the PDCP entity obtains a PDCP protocol data unit PDU corresponding to each PDCP SDU, and the PDCP entity sends the at least one PDCP PDU to the RLC entity and releases the at least one PDCP SDU at the same time. In the application, the PDCP entity sends the PDCP PDU to the RLC entity and simultaneously immediately releases the PDCP SDU from the PDCP SDU buffer area, thereby reducing the memory overhead, and the SDU which applies for the memory firstly can release the memory firstly, thereby improving the convenience of memory management.

On the basis of the above embodiment, after the PDCP entity releases at least one PDCP SDU buffered in the PDCP SDU buffer, the PDCP entity may further receive an acknowledgement message sent by the RLC entity, where the acknowledgement message is used to indicate that the network device successfully receives a PDCP PDU sent by the user equipment, and the acknowledgement message may carry identification information of the RLC PDU, may map the corresponding PDCP PDU, and indicate, for a PDCP PDU that does not receive the acknowledgement message, that the network device has not received a PDCP PDU sent by the user equipment, and may also perform PDCP reestablishment when performing cell handover or when performing Radio Resource Control (RRC) reestablishment, so as to recover the corresponding PDCP SDU and resend the corresponding PDCP SDU to the network device. The following is described in detail with reference to the embodiment of fig. 10:

fig. 10 is a flowchart illustrating a second method for transmitting data according to an embodiment of the present application, where as shown in fig. 10, when a packet header compression is configured for a data radio bearer, the method further includes the following steps:

s301, the PDCP entity buffers the IP related head in the PDCP SDU.

Wherein, the PDCP SDU is an internet protocol IP packet, and the IP packet includes an IP related header and an IP data part. Optionally, the IP related header includes:

an IP packet header; or

IP data packet head, message safety packaging protocol ESP data packet head.

Referring to fig. 3 to 7, in fig. 3, the IP correlation Header includes an IP Header, and the IP data part includes an IP Payload; in fig. 4, the IP-related Header includes an IP Header and a UDP Payload, and the IP data portion includes a UDP Payload; in fig. 5, the IP related Header includes an IP Header, a UDP Header, and an RTP Header, and the IP data portion includes an RTP Payload; in fig. 6, the IP-related Header includes an IP Header and a TCP Header, and the IP data portion includes a TCP Payload; in fig. 7, the IP-related Header includes an IP Header and an ESP Header, and the IP data portion includes an ESP Payload.

Since the compressed IP-related header cannot be recovered to the IP-related header, in order to recover the PDCP SDU corresponding to the PDCP PDU that the network device has not successfully received, in this embodiment, the IP-related header in each PDCP SDU is cached, and step S301 may be executed before step S202 or after step S202, which is not limited in this embodiment.

S302, the PDCP entity performs deciphering reversal on at least one PDCP PDU which is sent to the RLC entity but the RLC entity does not receive the confirmation message, and acquires a data part of the PDCP PDU.

The acknowledgement message is used for indicating the network equipment to successfully receive the PDCP PDU sent by the user equipment, the acknowledgement message is issued to the user equipment by the network equipment, and the RLC entity of the user equipment receives the acknowledgement message and sends the acknowledgement message to the PDCP entity.

In this embodiment, the PDCP entity determines, according to the received acknowledgement message, at least one PDCP PDU that the network device has not received, and then decrypts the PDCP PDU that has been sent to the RLC entity but the RLC entity has not received the acknowledgement message, so as to obtain a PDCP PDU data part, where the PDCP PDU data part includes a compressed IP related header and an IP data part.

S303, the PDCP entity obtains the retransmitted PDCP SDU according to the buffered IP related head corresponding to the PDCP PDU data part and the PDCP PDU data part.

When the data radio bearer is configured with header compression, step S303 specifically includes:

the PDCP entity acquires the retransmitted PDCP SDU according to the IP related head buffered by the PDCP PDU and the IP data part in the PDCP PDU data part.

Specifically, when the data radio bearer configures header compression, which indicates that the IP-related header of the PDCP SDU is compressed when the PDCP PDU is acquired in step S202, the data part of the PDCP PDU obtained by the de-decryption includes the compressed IP-related header and IP data part. Then in this embodiment, the PDCP SDU in the embodiment of figure 2, i.e., the retransmitted PDCP SDU, can be recovered from the buffered IP-related header and the IP data portion of the PDCP PDU data portion.

It should be noted that the IP related header cached by the PDCP entity and the PDCP PDU data part have a mapping relationship, and when recovering the retransmitted PDCP SDU, the IP related header corresponding to the PDCP PDU data part can be obtained according to the mapping relationship.

S304, the PDCP entity obtains a new PDCP PDU corresponding to the retransmitted PDCP SDU and sends the new PDCP PDU to the RLC entity.

When configuring packet header compression for a data radio bearer, a PDCP entity obtains a new PDCP PDU corresponding to a retransmitted PDCP SDU, which specifically includes:

the PDCP entity performs header compression on the IP related header cached in the retransmitted PDCP SDU again to obtain the IP related header after the recompression;

the PDCP entity encrypts the recompressed IP related head and the IP data part by adopting new encryption parameters to obtain an encrypted PDCP PDU data part;

Specifically, when configuring packet header compression for a data radio bearer and recovering a retransmitted PDCP SDU by a PDCP entity, the PDCP entity may perform header compression on an IP-related header buffered in the retransmitted PDCP SDU again, obtain a recompressed IP-related header, encrypt the recompressed IP-related header and IP data part using a new encryption parameter, obtain an encrypted PDCP PDU data part (corresponding to the encrypted data in fig. 8), and generate a new header of the PDCP PDU using new PDCP identification information, where the new PDCP identification information may be a sequence number allocated by the PDCP entity for the retransmitted PDCP SDU.

Then, the PDCP entity acquires a new PDCP PDU according to the encrypted PDCP PDU data part and the new head of the PDCP PDU. In a similar manner as in step S202.

In the 5G NR communication system, integrity protection processing may be further performed on the new header of the PDCP PDU, the IP related header after recompression, and the IP data portion, so that the PDCP entity obtains the new PDCP PDU according to the encrypted PDCP PDU data portion and the new header of the PDCP PDU, including:

and carrying out integrity protection processing on the new head part of the PDCP PDU, the IP related head part after recompression and the IP data part to obtain an integrity protection parameter MAC-I.

And encrypting the recompressed IP related head, the IP data part and the integrity protection parameter MAC-I by adopting a new encryption parameter to obtain an encrypted PDCP PDU data part, and then generating a new PDCP PDU according to the new head and the encrypted PDCP PDU data part of the PDCP PDU.

Therefore, the new PDCP PDU includes a new header of the PDCP PDU and a data part of the ciphered PDCP PDU, wherein the ciphered PDCP PDU is obtained by ciphering the recompressed IP related header, IP data part and integrity protection parameter MAC-I.

Based on the foregoing fig. 8 embodiment, fig. 11 is a schematic diagram of a generating process of a new PDCP PDU provided in this embodiment, as shown in fig. 11, when a packet header compression is configured for a data radio bearer, the PDCP PDU is decrypted to obtain a PDCP PDU data part, where the PDCP PDU data part includes a compressed IP-related header, an IP data part, and a MAC-I, and obtains a retransmitted PDCP SDU according to the IP data part and a corresponding buffered IP-related header, and then obtains the new PDCP PDU (i.e., a newly transmitted PDCP PDU) according to the retransmitted PDCP SDU, and sends the new PDCP PDU to an RLC entity.

The data transmission method provided by the embodiment comprises the following steps: when the data radio bearer is configured with header compression, the PDCP entity caches an IP-related header in PDCP SDUs, wherein the PDCP SDUs are internet protocol IP data packets, each of the IP data packets includes an IP-related header and an IP data part, the PDCP entity decrypts, of at least one PDCP PDU, a PDCP PDU that has been sent to the RLC entity but has not received an acknowledgement message, to obtain a PDCP PDU data part, wherein the acknowledgement message is used to indicate the network device to successfully receive a PDCP PDU sent by the user equipment, the PDCP entity obtains a retransmitted PDCP SDU according to the cached IP-related header and PDCP PDU data part corresponding to the PDCP PDU data part, and the PDCP entity obtains a new PDCP PDU corresponding to the retransmitted PDCP SDU and sends the new PDCP PDU to the RLC entity. When the packet header compression is configured, the PDCP SDU is recovered according to the cached IP related header, and the PDCP SDU corresponding to the PDCP PDU which is not successfully received by the network equipment is retransmitted, so that the user equipment is ensured to send the data to the network equipment.

Fig. 12 is a schematic flowchart of a third method for data transmission according to an embodiment of the present application, and as shown in fig. 12, when a packet header compression is not configured in a data radio bearer, the method further includes the following steps:

s401, the PDCP entity performs reverse decryption on at least one PDCP PDU which is already sent to the RLC entity but the RLC entity does not receive an acknowledgement message, and acquires a data part of the PDCP PDU, wherein the acknowledgement message is used for indicating that the network equipment successfully receives the PDCP PDU sent by the user equipment.

Wherein, when the data radio bearer is not configured with header compression, the PDCP PDU data part comprises a PDCP SDU comprising an IP data part and an IP related header.

S402, the PDCP entity obtains the retransmitted PDCP SDU according to the PDCP PDU data part, wherein the PDCP SDU comprises an IP related head and an IP data part.

Specifically, when the data radio bearer is not configured with header compression, it indicates that only the IP-related header and the IP data part of the PDCP SDU are ciphered when acquiring the PDCP PDU in step S202. Then in this embodiment, the PDCP SDU in the embodiment of fig. 2, i.e. the retransmitted PDCP SDU, can be recovered from the IP related header and IP data part obtained by de-decryption.

S403, the PDCP entity obtains a new PDCP PDU corresponding to the retransmitted PDCP SDU and sends the new PDCP PDU to the RLC entity.

The PDCP entity obtaining a new PDCP PDU corresponding to the retransmitted PDCP SDU specifically includes:

and the PDCP entity encrypts the IP related head and the IP data part by adopting the new encryption parameters to obtain the encrypted PDCP PDU data part.

And the PDCP entity generates a new head of the PDCP PDU by adopting the new PDCP identification information.

The PDCP entity acquires a new PDCP PDU according to the PDCP PDU data part and the new head of the PDCP PDU.

Specifically, when the packet header compression is not configured in the data radio bearer and the PDCP entity recovers the retransmitted SDU, the new ciphering parameter may be used to cipher the IP related header and the IP data portion, obtain the ciphered PDCP PDU data portion, and generate the new header of the PDCP PDU using the new PDCP identification information, where the new PDCP identification information may be a sequence number allocated by the PDCP entity to the retransmitted PDCP SDU. Then, a new PDCP PDU is acquired based on the PDCP PDU data portion and the new header of the PDCP PDU.

In the 5G NR communication system, the integrity protection processing may be further performed on a new header, an IP related header, and an IP data part of the PDCP PDU, and the PDCP entity obtains the new PDCP PDU according to the PDCP PDU data part and the new header of the PDCP PDU, including:

the PDCP entity carries out integrity protection processing on a new head, an IP related head and an IP data part of the PDCP PDU to obtain an integrity protection parameter MAC-I; encrypting the IP related head, the IP data part and the integrity protection parameter MAC-I by adopting new encryption parameters to obtain an encrypted PDCP PDU data part; and then generating a new PDCP PDU according to the new header of the PDCP PDU and the data part of the encrypted PDCP PDU.

The new PDCP PDU includes a new header of the PDCP PDU, a data part of the encrypted PDCP PDU, and an integrity protection parameter MAC-I, and the integrity protection processing is specifically performed in a manner similar to that in the prior art, which is not described herein again.

Based on the above-mentioned embodiment of fig. 9, fig. 13 is a schematic diagram of a second generation process of a new PDCP PDU provided in the embodiment of the present application, as shown in fig. 13, when a packet header compression is not configured in a data radio bearer, the PDCP PDU is decrypted to obtain an IP-related header and an IP data portion, and a retransmitted PDCP SDU is obtained according to the IP-related header and the IP data portion, and then the new PDCP PDU (i.e., a newly transmitted PDCP PDU) is obtained according to the retransmitted PDCP SDU, and then the new PDCP PDU may be sent to an RLC entity.

The data transmission method provided by the embodiment comprises the following steps: the PDCP entity performs deciphering on at least one PDCP PDU which is already sent to the RLC entity but the RLC entity does not receive an acknowledgement message, and acquires a data part of the PDCP PDU, wherein the acknowledgement message is used for indicating that the network equipment successfully receives the PDCP PDU sent by the user equipment, the PDCP entity acquires a retransmitted PDCP SDU according to the data part of the PDCP PDU, the data part of the PDCP PDU comprises an IP related header and an IP data part, and the PDCP entity acquires a new PDCP PDU corresponding to the retransmitted PDCP SDU and sends the new PDCP PDU to the RLC entity. Therefore, when the packet header compression is not configured, the PDCP SDU is recovered through the reverse decryption of the PDCP PDU, and the PDCP SDU corresponding to the PDCP PDU which is not successfully received by the network equipment is retransmitted, so that the user equipment is ensured to send the data to the network equipment.

Fig. 14 is a first schematic structural diagram of a data transmission device according to an embodiment of the present application, and as shown in fig. 14, the data transmission device includes:

a first obtaining module 11, configured to obtain at least one PDCP service data unit SDU, and buffer each PDCP SDU in a PDCP SDU buffer;

a second obtaining module 12, configured to obtain a PDCP protocol data unit PDU corresponding to each PDCP SDU;

a sending module 13, configured to release at least one PDCP SDU from the PDCP SDU buffer while sending the at least one PDCP PDU to the RLC entity.

Further, when the data radio bearer is configured with header compression, the method further includes:

a storage module 14, configured to buffer an IP-related header in the PDCP SDU, where the PDCP SDU is an internet protocol IP data packet, and the IP data packet includes an IP-related header and an IP data portion.

Further, still include:

a first de-ciphering module 15, configured to de-decipher, from the at least one PDCP PDU, a PDCP PDU that has been sent to the RLC entity but has not received an acknowledgement message by the RLC entity, to obtain a data part of the PDCP PDU, where the acknowledgement message is used to indicate that a network device successfully receives the PDCP PDU sent by the user equipment;

a third obtaining module 16, configured to obtain a retransmitted PDCP SDU according to the buffered IP-related header corresponding to the PDCP PDU data part and the PDCP PDU data part;

a fourth obtaining module 17, configured to obtain a new PDCP PDU corresponding to the retransmitted PDCP SDU, and send the new PDCP PDU to the RLC entity.

Further, the third obtaining module 16 is specifically configured to:

acquiring the retransmitted PDCP SDU according to the cached IP related header and the IP data part, wherein the PDCP PDU data part comprises a compressed IP related header and the IP data part;

correspondingly, the fourth obtaining module 17 is specifically configured to:

The PDCP entity of this embodiment may execute the technical solution in the method shown above, and for the specific implementation process and technical principle, reference is made to the related description in the method shown above, which is not described herein again.

Fig. 15 is a schematic structural diagram of a data transmission apparatus according to an embodiment of the present application, and as shown in fig. 15, when a packet header compression is not configured in a data radio bearer, the data transmission apparatus further includes:

a second de-ciphering module 21, configured to de-decipher, from the at least one PDCP PDU, a PDCP PDU that has been sent to the RLC entity but has not received an acknowledgement message, and obtain a data part of the PDCP PDU, where the acknowledgement message is used to indicate that a network device successfully receives the PDCP PDU sent by the user equipment;

a fifth obtaining module 22, configured to obtain a retransmitted PDCP SDU according to the PDCP PDU data part, where the PDCP PDU data part includes an IP related header and an IP data part;

a sixth obtaining module 23, configured to obtain a new PDCP PDU corresponding to the retransmitted PDCP SDU, and send the new PDCP PDU to the RLC entity.

Further, the sixth obtaining module 23 is specifically configured to:

Further, the IP related header includes:

an IP packet header; or

IP data packet head, message safety packaging protocol ESP data packet head.

Fig. 16 is a schematic diagram of a hardware structure of a user equipment according to an embodiment of the present application, and as shown in fig. 16, a user equipment 30 according to this embodiment may include: a processor 31 and a memory 32, a transmitter 33, a receiver 34.

A memory 32 for storing a computer program (e.g., an application program, a functional module, etc. implementing the above-described method), computer instructions, etc.;

the computer programs, computer instructions, etc. described above may be stored in one or more memories 32 in partitions. And the above-mentioned computer program, computer instructions, data, etc. can be called by the processor 31.

A processor 31 for executing the computer program stored in the memory 32 to implement the steps of the method according to the above embodiments.

Reference may be made in particular to the description relating to the preceding method embodiment.

The processor 31 and the memory 32, the transmitter 33, and the receiver 34 may be separate structures or may be integrated structures integrated together. When the processor 31 and the memory 32, the transmitter 33, and the receiver 34 are independent structures, the processor 31 and the memory 32, the transmitter 33, and the receiver 34 may be coupled by a bus 33.

In the embodiment, specific implementation processes and technical principles of the technical solution that can be implemented in the method are described in the related description of the method, and are not described herein again.

In addition, embodiments of the present application further provide a computer-readable storage medium, in which computer-executable instructions are stored, and when at least one processor of the user equipment executes the computer-executable instructions, the user equipment performs the above-mentioned various possible methods.

Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A storage media may be any available media that can be accessed by a general purpose or special purpose computer. An exemplary storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium. Of course, the storage medium may also be integral to the processor. The processor and the storage medium may reside in an ASIC. Additionally, the ASIC may reside in user equipment. Of course, the processor and the storage medium may reside as discrete components in a communication device.

Those of ordinary skill in the art will understand that: all or a portion of the steps of implementing the above-described method embodiments may be performed by hardware associated with program instructions. The program may be stored in a computer-readable storage medium. When executed, the program performs steps comprising the method embodiments described above; and the aforementioned storage medium includes: various media that can store program codes, such as ROM, RAM, magnetic or optical disks.

The present application further provides a program product comprising a computer program stored in a readable storage medium, from which the computer program can be read by at least one processor of a server, the computer program being executable by the at least one processor to cause the server to carry out the method of any of the embodiments of the present application described above.

Finally, it should be noted that: the above embodiments are only used for illustrating the technical solutions of the present application, and not for limiting the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some or all of the technical features may be equivalently replaced; and the modifications or the substitutions do not make the essence of the corresponding technical solutions depart from the scope of the technical solutions of the embodiments of the present application.

Claims

1. A data transmission method is applied to user equipment, and the user equipment comprises a Packet Data Convergence Protocol (PDCP) entity and a Radio Link Control (RLC) entity, and the method comprises the following steps:

the PDCP entity acquires at least one PDCP service data unit SDU and caches each PDCP PSDU in a PDCP SDU buffer area;

the PDCP entity sends at least one PDCP PDU to an RLC entity and simultaneously releases at least one PDCP SDU from the PDCP SDU buffer area;

when the data radio bearer configures header compression, the method further comprises:

the PDCP entity caches an IP related head in the PDCP SDU, wherein the PDCP SDU is an Internet protocol IP data packet, and the IP data packet comprises an IP related head and an IP data part;

the method further comprises the following steps:

the PDCP entity acquires a retransmitted PDCP SDU according to the cached IP related head corresponding to the PDCP PDU data part and the PDCP PDU data part;

2. The method as claimed in claim 1, wherein the PDCP entity obtains the retransmitted PDCP SDU according to the buffered IP related header corresponding to the PDCP PDU data part and the PDCP PDU data part, comprising:

3. The method of claim 1, wherein when a data radio bearer is not configured with header compression, the method further comprises:

4. The method as claimed in claim 3, wherein the PDCP entity obtaining a new PDCP PDU corresponding to the retransmitted PDCP SDU comprises:

5. The method according to any of claims 1-4, wherein the IP related header comprises:

an IP packet header; or

IP data packet head, message safety packaging protocol ESP data packet head.

6. A data transmission apparatus, comprising:

a sending module, configured to release at least one PDCP SDU from the PDCP SDU buffer while sending the at least one PDCP PDU to an RLC entity;

when the data radio bearer is configured with header compression, the method further comprises the following steps:

a storage module, configured to cache an IP-related header in the PDCP SDU, where the PDCP SDU is an internet protocol IP data packet, and the IP data packet includes an IP-related header and an IP data portion;

7. A user device, comprising: the device comprises a memory, a processor, a transmitter and a receiver, wherein executable instructions of the processor are stored in the memory; wherein the processor is configured to perform the method of any of claims 1-5 via execution of the executable instructions.

8. A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the method of any one of claims 1 to 5.