CN114339883A

CN114339883A - Data transmission method and device, electronic equipment and storage medium

Info

Publication number: CN114339883A
Application number: CN202011065941.5A
Authority: CN
Inventors: 姚富魁; 任荣辉
Original assignee: Chenxin Technology Co ltd
Current assignee: Chenxin Technology Co ltd
Priority date: 2020-09-30
Filing date: 2020-09-30
Publication date: 2022-04-12

Abstract

The embodiment of the invention discloses a data transmission method, a data transmission device, terminal equipment and a storage medium. The PDCP entity sends first data to a first RLC entity and a second RLC entity, wherein the first RLC entity and the second RLC entity adopt independent channels to send the first data to a receiving party; the PDCP entity sends a discard instruction to the second RLC entity after determining that the first RLC entity has completed sending the first data, so that the second RLC entity discards the first data. In the process that the PDCP transmits data to a receiving party by adopting mutually independent channels through the first RLC entity and the second RLC entity, the PDCP indicates the second RLC entity to discard the transmitted part under the condition that the first RLC entity is determined to be transmitted and received by the receiving party, and the part is not transmitted to the receiving party any more, thereby avoiding the waste of radio link resources caused by the transmission, the reception and the processing of invalid data and the overhead of system retransmission, and meeting the requirement of a user on data transmission.

Description

Data transmission method and device, electronic equipment and storage medium

Technical Field

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

Background

In an Ultra-Reliable and Low Latency Communications (URLLC) scenario of 5G Communications, in order to ensure reliability of Data transmission, at least one auxiliary RLC entity is further added to a Radio interface, on the basis that a Packet Data Convergence Protocol (PDCP) has been connected to a main Radio Link Control (Radio Link Control, RLC) entity, after the duplicate of the PDCP is activated, the PDCP delivers multiple identical PDCP Protocol Data Units (PDUs), each RLC entity corresponds to one of the PDCP Protocol Data units, and multiple identical PDCP PDUs are transmitted through mutually independent paths, so that reliability of Data transmission can be improved, and delay can be reduced.

However, in the process of data transmission by adopting the above-mentioned method, because the channel quality of the main/auxiliary entities corresponding to the respective logical channels is different, when the channel quality of one RLC entity is better and the data transmission is completed and successfully received by the receiving party, the other RLC entity can still continue to transmit the same data to the receiving party, thereby avoiding the waste of radio link resources caused by the transmission, reception and processing of invalid data, and the overhead of system retransmission, and meeting the requirement of the user for data transmission.

Disclosure of Invention

The embodiment of the invention provides a data transmission method, a data transmission device, a communication unit and a storage medium, which are used for avoiding the waste of wireless link resources caused by the transmission, the reception and the processing of invalid data.

In a first aspect, an embodiment of the present invention provides a data transmission method, which is applied to a terminal device, where the terminal device includes:

a Packet Data Convergence Protocol (PDCP) entity, a first radio link control layer protocol (RLC) entity and a second radio link control layer protocol (RLC) entity which are connected with the PDCP;

the PDCP entity sends first data to a first RLC entity and a second RLC entity, wherein the first RLC entity and the second RLC entity adopt independent channels to send the first data to a receiving party;

the PDCP entity sends a discard instruction to the second RLC entity after determining that the first RLC entity has completed sending the first data, so that the second RLC entity discards the first data.

In a second aspect, an embodiment of the present invention provides a data transmission apparatus, including: a first data sending module, configured to send first data to a first RLC entity and a second RLC entity by a PDCP entity, where the first RLC entity and the second RLC entity send the first data to a receiving party by using independent channels;

and the data discarding module is used for the PDCP entity to send a discarding instruction to the second RLC entity when determining that the first RLC entity has completed sending the first data, so that the second RLC entity discards the first data.

In a third aspect, an embodiment of the present invention provides a terminal device, where the terminal device includes:

one or more processors;

storage means for storing one or more programs;

when the one or more programs are executed by the one or more processors, the one or more processors are caused to implement the methods of any of the embodiments of the present invention.

In a fourth aspect, the embodiments of the present invention further provide a computer storage medium, on which a computer program is stored, which when executed by a processor implements the method according to any of the embodiments of the present invention.

In the technical scheme of the embodiment of the invention, when the PDCP determines that the first RLC entity finishes sending and is received by the receiving party in the process of sending data to the receiving party by adopting mutually independent channels through the first RLC entity and the second RLC entity, the PDCP indicates the second RLC entity to discard the sent part and not send the discarded part to the receiving party, thereby avoiding the waste of radio link resources caused by the sending, receiving and processing of invalid data and the overhead of system retransmission, and further meeting the requirement of a user on data transmission.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings needed to be used in the embodiments will be briefly described below, it should be understood that the following drawings only illustrate some embodiments of the present invention and therefore should not be considered as limiting the scope, and for those skilled in the art, other related drawings can be obtained according to the drawings without inventive efforts.

Fig. 1(a) is a flowchart of a data transmission method according to an embodiment of the present invention;

fig. 1(b) is a schematic view of an application scenario of a data transmission method according to an embodiment of the present invention;

FIG. 1(c) is a logic diagram for performing data discard according to an embodiment of the present invention;

fig. 1(d) is a logic diagram of receiving data by a receiving side according to an embodiment of the present invention;

fig. 2 is a schematic structural diagram of a data transmission apparatus according to a second embodiment of the present invention;

fig. 3 is a schematic structural diagram of a terminal device according to a third embodiment of the present invention.

Detailed Description

The present invention will be described in further detail with reference to the accompanying drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the invention and are not limiting of the invention. It should be further noted that, for the convenience of description, only some of the structures related to the present invention are shown in the drawings, not all of the structures.

It should be further noted that, for the convenience of description, only some but not all of the relevant aspects of the present invention are shown in the drawings. Before discussing exemplary embodiments in more detail, it should be noted that some exemplary embodiments are described as processes or methods depicted as flowcharts. Although a flowchart may describe the operations (or steps) as a sequential process, many of the operations can be performed in parallel, concurrently or simultaneously. In addition, the order of the operations may be re-arranged. The process may be terminated when its operations are completed, but may have additional steps not included in the figure. The processes may correspond to methods, functions, procedures, subroutines, and the like.

Example one

Fig. 1(a) is a flowchart of a data transmission method according to an embodiment of the present invention, where this embodiment is applicable to a situation where data is transmitted by using radio link resources in a URLLC scenario, and this method may be executed by a data transmission apparatus according to an embodiment of the present invention, and the apparatus may be implemented in a software and/or hardware manner. As shown in fig. 1(a), the method specifically includes the following operations:

step 101, a PDCP entity sends first data to a first RLC entity and a second RLC entity, wherein the first RLC entity and the second RLC entity send the first data to a receiving party by using independent channels.

As shown in fig. 1(b), which is a schematic view of an application scenario of the data transmission method in this embodiment, a terminal device, that is, a data sending party in this embodiment specifically includes: the system comprises a Packet Data Convergence Protocol (PDCP) entity, and a first radio link control layer protocol (RLC) entity and a second radio link control layer protocol (RLC) entity which are connected with the PDCP. In a specific implementation, the first RLC entity may be used as a main RLC, and the second RLC entity may be used as a secondary RLC; alternatively, the first RLC entity is used as the secondary RLC, and the second RLC entity is used as the primary RLC, which is not limited in this embodiment, as long as the first RLC entity and the second RLC entity use independent channels to transmit data within the protection scope of this application, which is not limited in this embodiment. The following description is given by taking the first RLC entity as the secondary RLC and the second RLC entity as the primary RLC as an example.

Optionally, the first data includes first protocol data units with different numbers; the first RLC entity preprocesses the first data to obtain second data and sends the second data to a receiving party, wherein the second data comprise second protocol data units with different numbers, and the numbers of the second protocol data units correspond to the numbers of the first protocol data units; and the second RLC entity preprocesses the first data to obtain third data and sends the third data to the receiving party, wherein the third data comprises third protocol data units with different numbers, and the number of the third protocol data unit corresponds to the number of the first protocol data unit.

Specifically, after the PDCP entity is configured with the duplicate activation, first data is generated, where the first data includes first protocol data units with different numbers, and the first data may be represented by PDCP PDUs. The PDCP entity sends the first data to the first RLC entity and the second RLC entity, the first RLC entity preprocesses the acquired first data to obtain the second data, the second RLC entity preprocesses the acquired first data to obtain the third data, and the first RLC entity and the second RLC entity send the preprocessed data to the receiving party by using independent channels. In addition, the first RLC or the second RLC in this embodiment may adopt two transmission modes, i.e., an AM-acknowledged mode or an UM-unacknowledged mode, for data transmission. Fig. 1(c) is a logic diagram for performing data discarding in this embodiment, where numbers of first protocol data units included in the first data are 2-13, numbers of second protocol data units included in the second data are 15-25, and numbers of third protocol data units included in the third data are 1-10, for example, a first data unit with a first data number of 8 corresponds to a second data unit with a second data number of 17, and a specific meaning may be that a second data unit with a second data number of 17 may be obtained by adding a header symbol on the basis of the first data unit with the first data number of 8. In this embodiment, the first data unit may correspond to a plurality of second data units, which in this case means that the data is segmented. Of course, this embodiment is merely an example, and the specific numerical value of the number in each type of data is not limited.

Step 102, the PDCP entity sends a discard instruction to the second RLC entity after determining that the first RLC entity has completed sending the first data, so that the second RLC entity discards the first data.

Optionally, the determining, by the PDCP entity, that the first RLC entity has completed sending the first data may include: the PDCP receives the number of the current updated second protocol data unit sent by the first RLC entity, wherein the current updated second protocol data unit is the second protocol data unit with the maximum number and the message confirmation of a receiving party is completed; and determining the maximum number of the first protocol data unit which has been completely sent by the first RLC entity aiming at the first data according to the number of the second protocol data unit which is updated currently.

Optionally, sending a discard instruction to the second RLC entity to cause the second RLC entity to discard the first data may include: sending a discarding instruction to a second RLC entity, wherein the discarding instruction comprises the maximum number of the first protocol data unit which is sent; the second RLC entity discards the first data which is not transmitted and is less than the maximum number of the first protocol data unit which is completely transmitted.

For example, in fig. 1(c), the number of the last second pdu in the second data in the first RLC entity is SN-24, i.e. TX-Next points to 25, which indicates the starting number of the Next update of the first RLC entity. The PDCP entity receives the number SN of the currently updated second pdu sent by the first entity, which is 18, that is, the TX _ Next _ Ack point is 18, which indicates that all the second pdus with the number SN <18 in the second data are acknowledged by the receiving party, and since the second pdu with the number 17 corresponds to the first pdu with the number 8, it can be known that all the first pdus with the number SN < 8 in the first data have been successfully sent by the first RLC entity channel path and acknowledged by the receiving party. Similarly, for the second RLC entity, the number of the last third pdu in the third data is SN 9, i.e. TX-Next points to 10, which indicates the starting number of the second RLC entity for the Next update. Since TX _ Next _ Ack in the second RLC entity points to 1, the third protocol data unit with number 1 corresponds to the first protocol data unit with number 3, and the third protocol data unit with number 6 corresponds to the first protocol data unit with number 8, it can be known that the first protocol data units with number SN < ═ 2 in the first data have been successfully transmitted by the second RLC entity channel path and confirmed by the receiving party. Therefore, the channel quality of the first RLC entity is better than that of the second RLC entity, and therefore the data transmission speed is higher.

The PDCP entity receives the number SN of the currently updated second protocol data unit sent by the first RLC entity, which is 18, and determines that the first protocol data unit with SN of the first data being less than 8 has been completely received by the receiving party in the first RLC entity, and then notifies the second RLC entity to discard the first protocol data unit with the number within the interval of 3-8 in the acquired first data, thereby avoiding unnecessary resource waste caused by the second RLC entity retransmitting the data that has been sent and determined to be completed.

Optionally, after determining that the first RLC entity has completed sending the first data, the PDCP entity sends a discard instruction to the second RLC entity, so that the second RLC entity discards the first data, the method may further include: determining the maximum number of the first protocol data unit which is sent by the second RLC entity and the corresponding effective number of the third protocol data unit; and generating a synchronous state report state packet according to the effective number of the third protocol data unit by the second RLC entity, and sending the synchronous state report state packet to the receiving party so that the receiving party stops feeding back the state of the data unit with the effective number smaller than the third protocol data unit to the second RLC entity.

Optionally, the synchronization status report status packet further includes: the type of synchronization status packet.

Specifically, for the above example, according to the new transmission window, the first RLC entity updates the valid number TX _ Sync _ Next of the second pdu to be equal to the number TX _ Next _ Ack in the second data, i.e. TX _ Sync _ Next ═ 18. And after the PDCP entity notifies the second RLC entity to discard the first pdu with the number within the interval 3-8 in the acquired first data, the second RLC entity updates the valid number TX _ Sync _ Next of the third pdu to the maximum number of the first pdu that is completely sent, that is, TX _ Sync _ Next equals 6. And the second RLC entity may generate the synchronization status report status packet according to the valid number of the third pdu, the synchronization status report status packet in this embodiment may adopt 12 bits or 18 bits, as shown in the following table 1-1, the structure of the synchronization status report status packet is shown as 12 bits, and as shown in the following table 1-2, the structure of the synchronization report status packet is shown as 18 bits:

TABLE 1-1

Tables 1 to 2

The D/C field is used to represent the data format, and occupies 1 bit of bytes, as shown in table 2 below:

TABLE 2

Value of	Description of the invention
		0	Control PDU
1	Data PDU

And CPT is used to indicate the type of the synchronization status packet, and occupies 3 bytes, as shown in table 3 below:

TABLE 3

When the structure of the 12-bit synchronization report status packet in table 1-1 is adopted to determine the synchronization status report status packet, when it is determined that the validity number TX _ Sync _ Nex of the third protocol data unit is 6, the ACK-SN in table 1-1 is filled to 6, the D/C in table 1-1 is filled to 0 in combination with table 2, and the CPT in table 1-1 is filled to 001 in combination with table 3, so that the finally obtained synchronization status report status packet is specifically shown in table 4 below:

TABLE 4

Optionally, after the generating, by the second RLC entity, the synchronization status report status packet according to the valid number of the third protocol data unit and sending the synchronization status report status packet to the receiving party, the method may further include: the second RLC entity determines the state of the current third data unit fed back by the receiving party; and judging whether the received number of the current third data unit is greater than the effective number of the third protocol data unit, if so, determining that the synchronous state report state packet is successfully sent, and otherwise, resending the synchronous state report state packet.

It should be noted that the second RLC entity sends the synchronization status report status packet shown in table 4 to the receiving side, so that the receiving side stops feeding back the status of the third pdu with a number less than 6 to the second RLC entity. If the second RLC entity determines that the status sent by the receiving party is received and the status indicates that the packet loss occurs in the third protocol data unit numbered 4, since 4<6, it can be determined that the receiving party does not successfully receive the synchronization status report status packet sent by the second RLC entity, and the synchronization status report status packet shown in the above table 4 is sent to the receiving party again; if the second RLC entity determines that the status sent by the receiving party is received and the status indicates that the packet loss of the third protocol data unit with the number of 8 occurs, since 8>6, it can be determined that the receiving party has successfully received the synchronization status report status packet sent by the second RLC entity, and the retransmission operation of the status packet is not needed.

Note that the receiving side in this embodiment has the same configuration as the transmitting side, and includes a main RLC^、Entity, auxiliary RLC^、Entity and PDCP^、Entity, wherein the data sent by the main RLC entity of the terminal equipment and the sender are transmitted to the main RLC of the receiver^、Entity, auxiliary R for transmitting data sent by auxiliary RLC entity of sending party to receiving partyLC^、An entity. Thus the second RLC entity, i.e. the secondary RLC of the sending peer^、When the entity sends the synchronization status report status packet shown in table 4 to the receiving party, specifically, the secondary RLC of the receiving party^、The entity receives. Secondary RLC of receiver^、And after the entity receives the synchronization status report status packet, analyzing the D/C domain, if the D/C is 0, continuously analyzing the CPT domain, if the CPT is 001, continuously analyzing the ACK-SN domain, and otherwise, discarding the D/C domain.

For example, as shown in FIG. 1(d), the logic diagram of the received data for the receiving side, the main RLC in the receiving side^、The entity receives the second protocol data unit in the second data of the sending main RLC entity with the latest SN of 21, namely RX-Next-Highest points to 22, and RX _ Next represents the packet loss position, RX _ Highest _ Status represents the state feedback position, and RX _ Next 18, namely the packet loss occurs for the first time at the position with the SN of 18 in the second protocol data unit, and the state feedback is carried out to the sending party. Number SN in second data<Second protocol data unit primary RLC entity receiving completely, PDCP to receiver^、The entity is submitted, because the second protocol data unit with the number of 18 corresponds to the first protocol data unit with the number of 8, the SN number in the first data can be known<The first protocol data unit of 8 is completely received. Similarly, secondary RLC for receiver^、The entity, RX _ Next _ high ═ 8, RX _ Next ═ 1, and RX _ high _ Status ═ 3, that is, packet loss occurs first at the position with the number SN ═ 1 in the third protocol data unit, and packet loss occurs correspondingly at both the positions with SN ═ 3 and SN ═ 6, and therefore, Status feedback is performed to the sender. According to the new receiving window mechanism, if the auxiliary RLC^、The entity feeds back to the sender that the third protocol data unit with the number SN of 2 is received and the third-party protocol data unit with the number SN of 1 is not completely received, then after receiving the synchronization Status report Status packet, determines that the ACK-SN is 6 by analyzing the ACK-SN field, and updates RX _ Next and RX _ Highest _ Status to the SN>6 and the first SN that has not been acknowledged, i.e. 8.

Example two

Fig. 2 is a schematic structural diagram of a data transmission device according to an embodiment of the present invention, where the device includes:

a first data sending module 210, configured to send first data to a first RLC entity and a second RLC entity by a PDCP entity, where the first RLC entity and the second RLC entity send the first data to a receiving party by using independent channels;

the data discarding module 220 is configured to, when the PDCP entity determines that the first RLC entity has completed sending the first data, send a discard instruction to the second RLC entity, so that the second RLC entity discards the first data.

Optionally, the first data includes first protocol data units with different numbers;

the first RLC entity preprocesses the first data to obtain second data and sends the second data to a receiving party, wherein the second data comprise second protocol data units with different numbers, and the numbers of the second protocol data units correspond to the numbers of the first protocol data units;

and the second RLC entity preprocesses the first data to obtain third data and sends the third data to the receiving party, wherein the third data comprises third protocol data units with different numbers, and the number of the third protocol data unit corresponds to the number of the first protocol data unit.

Optionally, the data discarding module 220 includes a data transmission completion determining sub-module, configured to:

the PDCP receives the number of the current updated second protocol data unit sent by the first RLC entity, wherein the current updated second protocol data unit is the second protocol data unit with the maximum number and the message confirmation of a receiving party is completed;

and determining the maximum number of the first protocol data unit which has been completely sent by the first RLC entity aiming at the first data according to the number of the second protocol data unit which is updated currently.

Optionally, the data discarding module 220 includes a data discarding submodule for:

sending a discarding instruction to a second RLC entity, wherein the discarding instruction comprises the maximum number of the first protocol data unit which is sent;

the second RLC entity discards the first data which is not transmitted and is less than the maximum number of the first protocol data unit which is completely transmitted.

Optionally, the apparatus further includes a status packet sending module, configured to:

determining the maximum number of the first protocol data unit which is sent by the second RLC entity and the corresponding effective number of the third protocol data unit;

and generating a synchronous state report state packet according to the effective number of the third protocol data unit by the second RLC entity, and sending the synchronous state report state packet to the receiving party so that the receiving party stops feeding back the state of the data unit with the effective number smaller than the third protocol data unit to the second RLC entity.

The apparatus further comprises a detection module for:

the second RLC entity determines the state of the current third data unit fed back by the receiving party;

and judging whether the received number of the current third data unit is greater than the effective number of the third protocol data unit, if so, determining that the synchronous state report state packet is successfully sent, and otherwise, resending the synchronous state report state packet.

The device can execute the data transmission method provided by any embodiment of the invention, and has corresponding functional modules and beneficial effects of the execution method. For technical details not described in detail in this embodiment, reference may be made to the method provided in any embodiment of the present invention.

EXAMPLE III

Fig. 3 is a schematic structural diagram of a terminal device according to an embodiment of the present invention. Fig. 3 illustrates a block diagram of an exemplary communications unit 412 suitable for use in implementing embodiments of the present invention. The terminal device 412 shown in fig. 3 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present invention.

As shown in fig. 3, the communication unit 412 is in the form of a general purpose computing communication unit. The components of the communication unit 412 may include, but are not limited to: one or more processors 416, a memory 428, and a bus 418 that couples the various system components (including the memory 428 and the processors 416).

Bus 418 represents one or more of any of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, and a processor or local bus using any of a variety of bus architectures. By way of example, such architectures include, but are not limited to, Industry Standard Architecture (ISA) bus, micro-channel architecture (MAC) bus, enhanced ISA bus, Video Electronics Standards Association (VESA) local bus, and Peripheral Component Interconnect (PCI) bus.

The communication unit 412 typically includes a variety of computer system readable media. Such media may be any available media that is accessible by communication unit 412 and includes both volatile and nonvolatile media, removable and non-removable media.

The memory 428 is used to store instructions. Memory 428 can include computer system readable media in the form of volatile memory, such as Random Access Memory (RAM)430 and/or cache memory 432. The communication unit 412 may further include other removable/non-removable, volatile/nonvolatile computer system storage media. By way of example only, storage system 434 may be used to read from and write to non-removable, nonvolatile magnetic media (not shown in FIG. 3, commonly referred to as a "hard drive"). Although not shown in FIG. 3, a magnetic disk drive for reading from and writing to a removable, nonvolatile magnetic disk (e.g., a "floppy disk") and an optical disk drive for reading from or writing to a removable, nonvolatile optical disk (e.g., a CD-ROM, DVD-ROM, or other optical media) may be provided. In these cases, each drive may be connected to bus 418 by one or more data media interfaces. Memory 428 can include at least one program product having a set (e.g., at least one) of program modules that are configured to carry out the functions of embodiments of the invention.

A program/utility 440 having a set (at least one) of program modules 442 may be stored, for instance, in memory 428, such program modules 442 including, but not limited to, an operating system, one or more application programs, other program modules, and program data, each of which examples or some combination thereof may comprise an implementation of a network environment. The program modules 442 generally perform the functions and/or methodologies of the described embodiments of the invention.

The communication unit 412 may also communicate with one or more external communication units 414 (e.g., keyboard, pointing communication unit, display 424, etc.), with one or more communication units that enable a user to interact with the communication unit 412, and/or with any communication unit (e.g., network card, modem, etc.) that enables the communication unit 412 to communicate with one or more other computing communication units. Such communication may occur via input/output (I/O) interfaces 422. Also, the communication unit 412 may communicate with one or more networks (e.g., a Local Area Network (LAN), a Wide Area Network (WAN), and/or a public network, such as the internet) through the network adapter 420. As shown, network adapter 420 communicates with the other modules of communications unit 412 over bus 418. It should be appreciated that although not shown in fig. 3, other hardware and/or software modules may be used in conjunction with the communication unit 412, including but not limited to: microcode, communication unit drives, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems, among others.

The processor 416 executes instructions stored in the memory 428 to perform various functional applications and data processing, such as implementing the data transmission method provided by the embodiment of the present invention: the PDCP entity sends first data to a first RLC entity and a second RLC entity, wherein the first RLC entity and the second RLC entity adopt independent channels to send the first data to a receiving party; the PDCP entity sends a discard instruction to the second RLC entity after determining that the first RLC entity has completed sending the first data, so that the second RLC entity discards the first data.

Example four

A fourth embodiment of the present invention provides a computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements the data transmission method provided in all the embodiments of the present invention:

the PDCP entity sends first data to a first RLC entity and a second RLC entity, wherein the first RLC entity and the second RLC entity adopt independent channels to send the first data to a receiving party; the PDCP entity sends a discard instruction to the second RLC entity after determining that the first RLC entity has completed sending the first data, so that the second RLC entity discards the first data.

Any combination of one or more computer-readable media may be employed. The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.

A computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.

Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

Computer program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C + +, or the like, as well as conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet service provider).

It is to be noted that the foregoing is only illustrative of the preferred embodiments of the present invention and the technical principles employed. It will be understood by those skilled in the art that the present invention is not limited to the particular embodiments described herein, but is capable of various obvious changes, rearrangements and substitutions as will now become apparent to those skilled in the art without departing from the scope of the invention. Therefore, although the present invention has been described in greater detail by the above embodiments, the present invention is not limited to the above embodiments, and may include other equivalent embodiments without departing from the spirit of the present invention, and the scope of the present invention is determined by the scope of the appended claims.

Claims

1. A data transmission method is applied to a terminal device, and the terminal device comprises: a Packet Data Convergence Protocol (PDCP) entity, a first radio link control layer protocol (RLC) entity and a second radio link control layer protocol (RLC) entity which are connected with the PDCP;

and the PDCP entity sends a discarding instruction to the second RLC entity after determining that the first RLC entity has finished sending the first data, so that the second RLC entity discards the first data.

2. The method of claim 1, wherein the first data comprises first protocol data units with different numbers;

the first RLC entity preprocesses the first data to obtain second data and sends the second data to the receiving party, wherein the second data comprise second protocol data units with different numbers, and the numbers of the second protocol data units correspond to the numbers of the first protocol data units;

3. The method as claimed in claim 2, wherein the PDCP entity, in determining that the first RLC entity has completed transmitting the first data, comprises:

the PDCP receives a number of a currently updated second pdu sent by the first RLC entity, where the currently updated second pdu is a largest-numbered second pdu for which the receiving side has completed message acknowledgement;

and determining the maximum number of the first protocol data unit which has finished sending the first data by the first RLC entity according to the number of the second protocol data unit which is updated currently.

4. The method of claim 3, wherein the sending a discard instruction to the second RLC entity to cause the second RLC entity to discard the first data comprises:

sending a discarding instruction to the second RLC entity, wherein the discarding instruction comprises the maximum number of the first protocol data unit which is sent;

5. The method of claim 4, wherein the PDCP entity, after determining that the first RLC entity has completed transmitting the first data, transmits a discard instruction to the second RLC entity to cause the second RLC entity to discard the first data, further comprising:

determining, by the second RLC entity, a valid number of a third protocol data unit corresponding to the maximum number of the first protocol data unit that has completed sending;

and generating a synchronous state report state packet according to the effective number of the third protocol data unit by the second RLC entity, and sending the synchronous state report state packet to the receiving party, so that the receiving party stops feeding back the state of the data unit with the effective number smaller than the third protocol data unit to the second RLC entity.

6. The method of claim 5, wherein after the generating, by the second RLC entity, the synchronization status report status packet according to the valid number of the third pdu and sending the synchronization status report status packet to the receiving side, further comprising:

7. The method of claim 5, wherein the synchronization status report status packet further comprises: the type of synchronization status packet.

8. A data transmission apparatus, comprising:

a first data sending module, configured to send first data to a first RLC entity and a second RLC entity by a PDCP entity, where the first RLC entity and the second RLC entity send the first data to a receiving party by using independent channels;

a data discarding module, configured to send a discarding instruction to the second RLC entity when the PDCP entity determines that the first RLC entity has completed sending the first data, so that the second RLC entity discards the first data.

9. A terminal device, characterized in that the terminal device comprises:

one or more processors;

storage means for storing one or more programs;

when executed by the one or more processors, cause the one or more processors to implement the method of any one of claims 1-7.

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