CN112584428A

CN112584428A - Data transmission method, device and equipment

Info

Publication number: CN112584428A
Application number: CN201910927578.4A
Authority: CN
Inventors: 谌丽
Original assignee: Datang Mobile Communications Equipment Co Ltd
Current assignee: Datang Mobile Communications Equipment Co Ltd
Priority date: 2019-09-27
Filing date: 2019-09-27
Publication date: 2021-03-30
Anticipated expiration: 2039-09-27
Also published as: CN112584428B

Abstract

The invention discloses a data transmission method, a device and equipment, wherein the method comprises the following steps: after determining that a first RLC PDU is successfully received, the first node generates successful receiving feedback information for a second RLC PDU, wherein the first node is an intermediate relay node in the relay network architecture or a node which finally receives data, and the second RLC PDU and the first RLC PDU are RLC PDUs which are generated by different RLC entities and contain the same PDCP PDU; and the first node sends the successful receiving feedback information of the second RLC PDU to the superior node through the second RLC entity. The embodiment of the invention can reduce the resource consumption in the PDCP repeated transmission, realize the reliability of data transmission and reduce the air interface resource overhead.

Description

Data transmission method, device and equipment

Technical Field

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

Background

The 5G NR (New Radio, New air interface) system mainly supports the following three types of services:

1) eMBB (enhanced Mobile Broadband, enhanced Broadband communications);

2) mtc (massive Machine Type Communications);

3) URLLC (Ultra-Reliable and Low Latency Communications)

For URLLC, because of its high requirements on delay and reliability, a solution proposed by 3GPP is to introduce a PDCP (Packet Data Convergence Protocol) repeat transmission mechanism, that is, transmit the same PDCP layer PDU (Protocol Data Unit) through multiple paths, improve transmission reliability through multiple transmission gains, and reduce transmission delay.

As shown in fig. 1 and fig. 2, a Radio bearer corresponds to a PDCP entity, and data on the Radio bearer is transmitted through a plurality of RLC entities and a Logical Channel (Logical Channel) corresponding to each RLC entity in an RLC (Radio Link Control) layer. For the CA model, a plurality of logical channels corresponding to the repeatedly transmitted radio bearers are processed by one MAC entity in the MAC layer, and data from different RLC entities are mapped to different carriers for transmission. For the DC model, multiple RLC entities corresponding to duplicate RBs and their corresponding logical channels are mapped to different MAC entities, respectively.

A multi-hop relay network architecture IAB (Integrated Access and Backhaul) is introduced into the 5G system, and fig. 3 is a schematic diagram of a relay network architecture (IAB architecture) for data transmission through a relay node. The RAN2, which is peered to the terminal (UE), controls the plane RRC layer and the PDCP layer of the user plane on an IAB donor (IAB donor), between which there are a number of wireless network nodes IAB, one IAB node containing an MT (Mobile-Termination) part and a DU (Data Unit) part. The MT part is responsible for establishing a connection between the IAB node and a higher-level network node (also called a parent node), and the DU part is responsible for communicating with a lower-level node or a terminal. Here, the upper node and the lower node are in an upper-lower relationship in terms of a data transmission direction, that is, the node receives data from the upper node and transmits data to the lower node.

In the IAB architecture, the IAB node air interface user plane layer 2 only has a BAP (Backhaul adaptation Protocol) layer, an RLC layer, and an MAC layer. The architecture shown in fig. 3 is only a schematic diagram, and the specific modeling manner of the BAP layer is not determined at present.

In the IAB architecture, when PDCP retransmission is adopted, each PDCP PDU needs to be retransmitted between each hop node, and resource consumption is large.

Disclosure of Invention

At least one embodiment of the present invention provides a data transmission method, apparatus, and device, which can reduce resource consumption in PDCP retransmission by introducing RLC retransmission, and reduce overhead of air interface resources while achieving reliability of data transmission.

The embodiment of the invention provides a data transmission method, which is applied to a first node in a relay network architecture for carrying out data transmission through a relay node, wherein when the first node carries out PDCP repeated transmission, a PDCP protocol data unit PDU is mapped to at least two radio link control RLC entities to organize into at least two RLC PDU transmission, and the method is characterized by comprising the following steps:

after determining that a first RLC PDU is successfully received, the first node generates successful receiving feedback information for a second RLC PDU, wherein the first node is an intermediate relay node in the relay network architecture or a node which finally receives data, and the second RLC PDU and the first RLC PDU are RLC PDUs which are generated by different RLC entities and contain the same PDCP PDU;

and the first node sends the successful receiving feedback information of the second RLC PDU to the superior node through the second RLC entity.

Optionally, in the above method, before generating the feedback information for successful reception of the second RLC PDU, the method further includes:

and receiving first feedback information fed back by the subordinate node and used for indicating the successful reception of the first RLC PDU, and determining that the first RLC PDU is successfully sent to the subordinate node according to the first feedback information.

Optionally, in the foregoing method, generating the successful reception feedback information for the second RLC PDU generated by the second RLC entity includes:

and when the first node receives the second RLC PDU, generating second feedback information for indicating the successful reception of the second RLC PDU according to the second RLC PDU.

Optionally, in the method, when the first node has received the second RLC PDU, the method further includes:

the first node cancels the sending of the second RLC PDU to the lower node.

Optionally, in the foregoing method, the PDCP PDU reception confirmation method of the PDCP repeated transmission is end-to-end RLC feedback from the terminal to a first-level network node in the relay network architecture.

Optionally, in the foregoing method, before determining that the first RLC PDU is successfully received, the method further includes:

and after the first node receives the first RLC PDU sent by the superior node, determining that the first RLC PDU is successfully received.

Optionally, in the foregoing method, the step of generating feedback information for successful reception of the second RLC PDU includes:

and when the first node does not receive the second RLC PDU, determining a Logic Channel Identifier (LCID) and a second RLC SN of the second RLC PDU corresponding to the first RLC PDU according to a pre-obtained RLC mapping relation corresponding to a superior node, and generating third feedback information for indicating successful reception of the second RLC PDU according to the LCID and the second RLC SN of the second RLC PDU.

Optionally, in the method, when the first node does not receive the second RLC PDU, the method further includes:

determining a third RLC SN of the second RLC PDU at the transmitting end of the first node according to the corresponding relation of RLC SN values among different RLC entities containing the same PDCP PDU;

constructing a third RLC PDU according to a pre-obtained RLC mapping relation corresponding to a subordinate node, the PDPC PDU contained in the first RLC PDU and the third RLC SN;

and transmitting the third RLC PDU to a subordinate node.

Optionally, in the above method, the PDCP PDU reception confirmation method of the PDCP repeated transmission is a hop-by-hop RLC feedback between adjacent network nodes.

the first node saves at least one of the following information of different RLC PDUs containing the same PDCP PDU:

a terminal identifier and a bearer identifier;

finally receiving the node identification of the data;

RLC mapping relation corresponding to the superior node;

RLC mapping relation corresponding to subordinate node;

the RLC mapping relation comprises a logical channel identifier and an RLC SN.

The embodiment of the present invention further provides a data transmission apparatus, which is applied to a first node in a relay network architecture for performing data transmission through a relay node, wherein when the first node performs PDCP duplicate transmission, one PDCP protocol data unit PDU is mapped to at least two RLC entities, and is organized into at least two RLC PDU transmissions, the data transmission apparatus includes:

a feedback information generating module, configured to generate successful reception feedback information for a second RLC PDU after it is determined that a first RLC PDU is successfully received, where the first node is an intermediate relay node in the relay network architecture or a node that finally receives data, and the second RLC PDU and the first RLC PDU are RLC PDUs generated by different RLC entities and containing the same PDCP PDU;

and the feedback information sending module is used for sending the feedback information of successful receiving of the second RLC PDU to the superior node through the second RLC entity.

An embodiment of the present invention further provides a first node, including: a memory, a processor, a transceiver, and a program stored on the memory and executable on the processor;

the processor implements the following steps when executing the program:

after the first RLC PDU is successfully received, generating successful receiving feedback information aiming at a second RLC PDU, wherein the first node is an intermediate relay node in the relay network architecture or a node which finally receives data, and the second RLC PDU and the first RLC PDU are RLC PDUs which are generated by different RLC entities and contain the same PDCP PDU;

sending successful receiving feedback information of a second RLC PDU to a superior node through a second RLC entity;

when the first node performs PDCP repeated transmission, one PDCP protocol data unit PDU is mapped to at least two radio link control RLC entities and organized into at least two RLC PDU transmission.

Optionally, in the first node, when the processor executes the program, the following steps are further implemented: before generating the feedback information for successful receiving of the second RLC PDU, receiving first feedback information fed back by a subordinate node and used for indicating successful receiving of the first RLC PDU, and determining that the first RLC PDU is successfully sent to the subordinate node according to the first feedback information.

Optionally, in the first node, when the processor executes the program, the following steps are further implemented: and when the first node receives the second RLC PDU, generating second feedback information for indicating the successful reception of the second RLC PDU according to the second RLC PDU.

Optionally, in the first node, when the processor executes the program, the following steps are further implemented: and canceling the second RLC PDU from being sent to a lower node when the first node receives the second RLC PDU.

Optionally, in the first node, when the processor executes the program, the following steps are further implemented: before generating the feedback information for successful receiving of the second RLC PDU, after the first node receives the first RLC PDU sent by the superior node, the first RLC PDU is determined to be successfully received.

Optionally, in the first node, when the processor executes the program, the following steps are further implemented: and when the first node does not receive the second RLC PDU, determining a Logic Channel Identifier (LCID) and a second RLC SN of the second RLC PDU corresponding to the first RLC PDU according to a pre-obtained RLC mapping relation corresponding to a superior node, and generating third feedback information for indicating successful reception of the second RLC PDU according to the LCID and the second RLC SN of the second RLC PDU.

Optionally, in the first node, when the processor executes the program, the following steps are further implemented: the processor, when executing the program, further implements the steps of: when the first node does not receive the second RLC PDU, determining a third RLC SN of the second RLC PDU at a transmitting end of the first node according to a corresponding relation of RLC SN values among different RLC entities containing the same PDCP PDU; constructing a third RLC PDU according to a pre-obtained RLC mapping relation corresponding to a subordinate node, the PDPC PDU contained in the first RLC PDU and the third RLC SN; and transmitting the third RLC PDU to a subordinate node.

Embodiments of the present invention also provide a computer storage medium, which includes instructions that, when executed on a computer, cause the computer to perform the method described above.

The embodiment of the invention has the beneficial effects that: in the embodiment of the invention, for PDCP repeated transmission on a first node in a multi-hop relay network architecture, after a certain RLC PDU is determined to be successfully received, the successful receiving feedback information of other RLC PDUs containing the same PDCP PDU is sent to an upper node, so that other RLC PDUs containing the same PDCP PDU can not be continuously transmitted and carried on the upper node or the lower node, thereby reducing resource consumption, improving data transmission speed, guaranteeing low-delay and high-reliability transmission, and reducing air interface resource overhead.

Drawings

Various other advantages and benefits will become apparent to those of ordinary skill in the art upon reading the following detailed description of the preferred embodiments. The drawings are only for purposes of illustrating the preferred embodiments and are not to be construed as limiting the invention. Also, like reference numerals are used to refer to like parts throughout the drawings. In the drawings:

FIG. 1 is a schematic diagram of a prior art CA model for repeated transmissions;

FIG. 2 is a schematic diagram of a DC model of a repetitive transmission of the prior art;

FIG. 3 is a schematic diagram of an IAB architecture of the prior art;

FIG. 4 is a flow chart of a data transmission method according to an embodiment of the present invention;

fig. 5 is a schematic diagram of example 1 of a data transmission method according to an embodiment of the present invention;

fig. 6 is a schematic diagram of example 2 of a data transmission method according to an embodiment of the present invention;

fig. 7 is a schematic diagram of example 3 of a data transmission method according to an embodiment of the present invention;

fig. 8 is a schematic diagram of example 4 of a data transmission method according to an embodiment of the present invention;

FIG. 9 is a block diagram of a data transmission apparatus according to an embodiment of the present invention;

fig. 10 is a structural diagram of a first node according to an embodiment of the present invention.

Detailed Description

Exemplary embodiments of the present invention will be described in more detail below with reference to the accompanying drawings. While exemplary embodiments of the invention are shown in the drawings, it should be understood that the invention can be embodied in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the invention to those skilled in the art.

The terms first, second and the like in the description and in the claims of the present application are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the application described herein are, for example, capable of operation in sequences other than those illustrated or otherwise described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus. In the description and in the claims "and/or" means at least one of the connected objects.

The following description provides examples and does not limit the scope, applicability, or configuration set forth in the claims. Changes may be made in the function and arrangement of elements discussed without departing from the spirit and scope of the disclosure. Various examples may omit, substitute, or add various procedures or components as appropriate. For example, the described methods may be performed in an order different than described, and various steps may be added, omitted, or combined. In addition, features described with reference to certain examples may be combined in other examples.

An embodiment of the present invention provides a data transmission method, which may be applied to a first node of a relay network architecture for data transmission through a relay node, such as shown in fig. 3, where when the first node performs PDCP duplicate transmission, one PDCP protocol data unit PDU is mapped to at least two RLC entities, and is organized into at least two RLC PDU transmissions. The first node may specifically be an intermediate relay node in the relay network architecture or a node that finally receives data.

Here, the intermediate relay node refers to an intermediate node in a route (e.g., a node between the IAB donor and the terminal), and the node that finally receives data refers to an end point of the route. For example, in fig. 3, in a route (downlink transmission) from the IAB node to the terminal (UE) via the IAB node #2 and the IAB node #1 in sequence, the intermediate relay node includes the IAB node #2 and the IAB node #1, and the node that finally receives data is the terminal (UE). For another example, in a route (uplink transmission) from a terminal (UE) to an IAB Donor via IAB node #1 and IAB node #2 in sequence, the intermediate relay node includes IAB node #1 and IAB node #2, and the node that finally receives data is the IAB Donor.

As shown in fig. 4, when applied to the first node, the data transmission method according to the embodiment of the present invention includes:

step 41, after determining that the first RLC PDU is successfully received, the first node generates successful reception feedback information for a second RLC PDU, where the second RLC PDU and the first RLC PDU are RLC PDUs which are generated by different RLC entities and contain the same PDCP PDU.

Here, the first RLC PDU and the second RLC PDU may be RLC PDUs generated by different RLC entities of the DU part of the upper node, and the MT part of the first node includes an RLC entity that is a peer of the RLC entity of the DU part of the upper node.

The first node, upon determining successful reception of the first RLC PDU, will actively construct successful reception feedback information for other RLC PDUs (assumed to be second RLC PDUs) that contain the same PDCP PDU as the first RLC PDU, without having to wait until successful reception of the other RLC PDUs is determined before generating the successful reception feedback information. In addition, there may be 1 or more other RLC PDUs (i.e. the second RLC PDUs) that include the same PDCP PDU as the first RLC PDU, and if there are more than one RLC PDUs, the first node may generate corresponding successful reception feedback information for each second RLC PDU.

And step 42, the first node sends the successful receiving feedback information of the second RLC PDU to the superior node through the second RLC entity.

Here, the first node transmits the successful reception feedback information of the second RLC PDU to an upper node, which is an upper node in a data transmission direction, and receives data from the upper node in a data route and forwards the data to a lower node of the first node.

It should be noted that, in the step 42, the first node may have successfully received the second RLC PDU sent by the upper node, or may not have received the second RLC PDU sent by the upper node.

Through the above steps, in step 42, in the embodiment of the present invention, the first node sends the successful receiving feedback information of the second RLC PDU to the upper node, so that the upper node considers that the second RLC PDU has been successfully sent, and thus, if the first node has received the second RLC PDU sent by the upper node, the first node may not send the second RLC PDU to its lower node any more, so that the data amount sent by the first node to the lower node may be reduced, and the overhead of air interface resources is reduced, or, if the first node has not received the second RLC PDU sent by the upper node, the first node may not need to wait for receiving the second RLC PDU sent by the upper node, but directly construct and send the RLC PDU containing the same PDCP PDU as the second RLC PDU to the lower node, and the upper node may also cancel sending the second RLC PDU to the first node, so that the waiting time of the first node may be reduced, the data transmission speed is improved, the data volume sent by the superior node to the first node can be reduced, and the air interface resource overhead is reduced.

In addition, in order to facilitate generation of feedback information on successful reception of the second RLC PDU and/or construction of an RLC PDU containing the same PDCP PDU as the second RLC PDU, which is sent to the lower node, the embodiment of the present invention may store at least one of the following information of a different RLC PDU containing the same PDCP PDU in the first node row:

a terminal identifier and a bearer identifier;

a node identifier for finally receiving data (for downlink transmission, the node identifier is a terminal identifier, and for uplink transmission, the node identifier is an IAB donor identifier);

RLC mapping relation corresponding to the superior node;

RLC mapping relation corresponding to subordinate node;

wherein the RLC mapping relation comprises a logical channel identifier and an RLC sequence number (RLC SN).

The information may be configured to the first node by a general control node of a relay network architecture, or an IAB donor, or a superior node of the first node.

In the above step 41, the first node has the following different determination manners in determining that the first RLC PDU generated by the first RLC entity is successfully received.

Determination method 1:

the first node may determine, after receiving first feedback information (specifically, an RLC status report) fed back by a subordinate node and used for indicating that the first RLC PDU is successfully received, that the first RLC PDU is successfully sent to the subordinate node according to the first feedback information. The determining mode is particularly suitable for the PDCP PDU receiving confirmation mode of the PDCP repeated transmission, and is end-to-end RLC feedback between a terminal and a first-level network node in a relay network architecture. The end-to-end RLC feedback refers to RLC feedback performed at both ends of the PDCP repeated transmission including the PDCP peer entity, for example, taking fig. 2 as an example, the RLC feedback from the terminal (UE) to the IAB donor is RLC feedback from the IAB donor to the terminal (UE) in the downlink direction, and is RLC feedback from the IAB donor to the terminal (UE) in the uplink direction.

At this time, in step 41, if the first node has received the second RLC PDU, the first node may generate second feedback information indicating successful reception of the second RLC PDU according to the second RLC PDU.

In addition, the first node can also cancel sending the second RLC PDU to a lower node, so as to reduce resource overhead occupied by data transmission. Here, when the first node transmits the second RLC PDU to the lower node, the first node transmits the second RLC PDU through the RLC entity of the DU part of the first node, and at this time, another RLC PDU including the same PDCP PDU as the second RLC PDU may be generated and transmitted.

In the above-described determination method 1, the first node receives the RLC status report fed back by the lower receiving node, determines the RLC PDU correctly received by the lower node, generates a positive feedback RLC ARQ for the correctly received RLC PDU and other RLC PDUs which are the same PDCP PDU as the RLC PDU and transmitted to the upper transmitting node according to the RLC layer mapping relationship with the upper transmitting node, and transmits the positive feedback RLC ARQ to the upper transmitting node.

It should be noted that the IAB node may or may not have correctly received the RLC PDUs containing the same PDCP PDUs.

Fig. 5 shows a specific example of the above determination mode 1, in which PDCP PDU retransmission is performed between the IAB Donor and the UE, and two RLC PDUs, namely RLC1PDU1 and RLC2 PDU1, having the same PDCP PDU are transmitted. As shown in fig. 5:

1) the UE correctly receives RLC1PDU1 and sends RLC ARQ for RLC1PDU1 to IAB node # 1;

2) the IAB node #1 does not correctly receive RLC2 PDU1 (containing the same PDCP PDU as RLC1PDU 1), and directly forwards RLC ARQ of RLC1PDU1 sent by the UE to the IAB node # 2;

3) the IAB node #2 receives RLC ARQ of RLC1PDU1 forwarded by the IAB node #1, and when having received RLC2 PDU1 transmitted by the IAB node #1, generates RLC ARQ of RLC2 PDU1, and delivers to the upper transmitting node together with RLC ARQ of RLC1PDU 1. From the IAB node #2, RLC2 PDU1 is not transmitted to the subordinate receiving node any more.

Determination mode 2:

the first node may also determine that the first RLC PDU is successfully received after the first node receives the first RLC PDU sent by the upper node. The determining mode is particularly suitable for the PDCP PDU receiving confirmation mode of the PDCP repeated transmission, namely the hop-by-hop RLC feedback between adjacent network nodes.

At this time, in step 41, if the first node does not receive the second RLC PDU, the first node may determine a logical channel identifier LCID and a second RLC SN of the second RLC PDU corresponding to the first RLC PDU according to a previously obtained RLC mapping relationship corresponding to the upper node, and generate third feedback information for indicating that the second RLC PDU is successfully received according to the LCID and the second RLC SN of the second RLC PDU.

In addition, the first node may further send the second RLC PDU to a subordinate node, and at this time, the first node may determine, according to a correspondence between RLC SN values of different RLC entities including the same PDCP PDU, a third RLC SN of the second RLC PDU at the sending end of the first node; then, constructing a third RLC PDU according to a pre-obtained RLC mapping relation corresponding to a lower node, the PDPC PDU contained in the first RLC PDU and the third RLC SN; then, the third RLC PDU is transmitted to the lower node.

In the above determining method 2, if RLC SN values containing the same PDCP PDU have a fixed corresponding relationship, such as a fixed offset value, between RLC entities for PDCP retransmission, after the first node correctly receives one RLC PDU, even if another RLC PDU containing the same PDCP PDU is not received, the following operations may be performed:

A) and generating positive feedback RLC ARQ of the RLC PDU and other RLC PDUs which are transmitted with the same PDCP PDU as the RLC PDU, and sending the RLC PDU and other RLC PDUs to an upper sending node.

B) And automatically generating other RLC PDUs according to the corresponding relation of the RLC SN values among different RLC entities containing the same PDCP PDU and sending the RLC PDUs to a lower-level receiving node. The RLC PDU is not transmitted from an upper transmitting node, but is generated by adding the determined RLC header of the other RLC PDU according to the payload part of the successfully received RLC PDU.

Fig. 7 shows a specific example of the above determination mode 2, in which PDCP PDU retransmission is performed between the IAB Donor and the UE, and two RLC PDUs, namely RLC1PDU1 and RLC2 PDU1, having the same PDCP PDU are transmitted. As shown in fig. 7:

1) IAB node #2 successfully received RLC1PDU1, but did not receive RLC2 PDU 1;

2) the IAB node #2 calculates the SN number of RLC2 PDU1 carrying the same PDCP PDU with RLC1PDU1 according to the corresponding relation of RLC SN values of the same PDCP PDUs carried by RLC1 and RLC2, and sends positive feedback RLC ARQ of RLC1PDU1 and RLC2 PDU1 to the superior node;

3) IAB node #2 constructs RLC2 PDU1 according to the calculated SN number of RLC2 PDU1 and the load part (namely PDCP PDU) of RLC1PDU 1;

4) the IAB node #2 transmits RLC1PDU1 and RLC2 PDU1 to the lower node on the respective RLC entities. Further, if the subordinate receiving node is already the final receiving node (terminal for downlink transmission and base station/IAB Donor for uplink transmission), the IAB node may not send RLC2 PDU1 after receiving a positive feedback of RLC1PDU 1.

The implementation of the data transmission method according to the embodiment of the present invention is described above. Several examples of data transmission methods to which embodiments of the invention may be applied are further provided below in conjunction with the figures. In the following drawings of the respective examples, for simplicity of explanation, the same RLC SN is used for both MT and DU parts of each node for the same duplicate data repeatedly transmitted by PDCP.

Example 1: the IAB node constructs positive feedback of other RLC PDUs containing the same PDCP PDU to an upper transmitting node according to the RLC positive feedback of a lower receiving node

The data transmission direction in this example 1 is a downlink transmission direction from the IAB Donor to the UE, and end-to-end RLC feedback (RLC ARQ) is adopted.

In this example 1, the IAB node learns and stores the PDCP entity and its corresponding RLC entity that perform PDCP retransmission and the respective RLC SNs of RLC PDUs used by different RLC entities that transmit the same PDCP PDU, through IAB donor notification or step-by-step notification among the IAB nodes in advance.

Still taking fig. 5 as an example for explanation, this example 1 includes:

1) the method comprises the steps that the DU side of an IAB node #2 receives the RLC state of a terminal forwarded by a lower node, and the RLC1PDU1 positive feedback is determined;

2) the MT side of the IAB node #2 generates RLC ARQ of RLC2 PDU1, and delivers to the upper sending node together with RLC ARQ of RLC1PDU 1;

3) the IAB node #2 no longer sends RLC2 PDU1 to the subordinate node, optionally informing the subordinate node to stop the transmission of RLC2 PDU1 if RLC2 PDU1 has been sent to the subordinate node.

Example 2: the IAB node constructs positive feedback of other RLC PDUs containing the same PDCP PDU to an upper transmitting node according to the RLC positive feedback of a lower receiving node

The data transmission direction in this example 2 is an uplink transmission direction from the UE to the IAB Donor, and end-to-end RLC feedback (RLC ARQ) is adopted.

In this example 2, the IAB node obtains and stores the PDCP entity and its corresponding RLC entity performing PDCP retransmission and the RLC SNs of the respective RLC PDUs used by different RLC entities transmitting the same PDCP PDU through IAB donor notification or notification step by step between IAB nodes in advance.

Taking fig. 6 as an example for explanation, this example 2 includes:

1) the MT side of the IAB node IAB #2 receives the RLC state of the IAB node, including determining the positive feedback of RLC1PDU 1;

2) the DU side of the IAB node #2 generates RLC2 PDU1 RLC ARQ, which is delivered to the upper transmitting node (IAB node #1 in the figure) together with RLC1PDU1 RLC ARQ;

3) the IAB node #2 does not send RLC2 PDU1 to the subordinate node (IAB node in the figure), optionally if RLC2 PDU1 has been sent to the subordinate node, informing the subordinate node to stop the sending of RLC2 PDU 1.

Example 3: the IAB node generates and sends RLC ARQ containing a plurality of RLC PDUs of the same PDCP PDU to an upper node in advance according to the RLC PDU successfully received by the IAB node

The data transmission direction in this example 3 is a downlink transmission direction from the IAB Donor to the UE, and the hop-by-hop RLC feedback between adjacent network nodes is adopted.

In this example 3, the IAB node obtains and stores the relationship between the PDCP entity and its corresponding RLC entity that performs PDCP retransmission and the RLC SNs of the respective RLC PDUs used by different RLC entities that transmit the same PDCP PDU, through IAB donor step-by-step notification among the IAB nodes in advance. For example, when RLC1 SN of RLC PDU of RLC1 entity transmitting the same PDCP PDU is SN1, RLC2 SN of RLC PDU of RLC2 entity is SN1+ k.

Still taking fig. 7 as an example for explanation, this example 3 includes:

1) the MT of IAB node #2 successfully receives RLC1PDU1 but does not receive RLC2 PDU 1;

2) the IAB node #2 deduces the RLC SN of the RLC2 PDU1 carrying the same PDCP PDU with the RLC1PDU1 according to the corresponding relation of the RLC SNs of the RLC PDUs carrying the same PDCP PDUs by the RLC1 and the RLC2, and the MT of the IAB node #2 sends positive feedback RLC ARQ of RLC1PDU1 and RLC2 PDU1 to an upper node;

3) the IAB node #2 constructs RLC2 PDU1 according to the estimated RLC SN of the RLC2 PDU1 and the load part (namely PDCP PDU) of the RLC1PDU 1;

4) the DU of the IAB node #2 transmits RLC1PDU1 and RLC2 PDU1 to the lower node on the respective RLC entities. Further, if the subordinate receiving node is already the final receiving node (terminal for downlink transmission), the IAB node may not send RLC2 PDU1 any more after receiving the positive feedback of RLC1PDU 1.

Example 4: the IAB node generates and sends RLC ARQ containing a plurality of RLC PDUs of the same PDCP PDU to an upper node in advance according to the RLC PDU successfully received by the IAB node

The data transmission direction in this example 4 is an uplink transmission direction from the UE to the IAB Donor, and the hop-by-hop RLC feedback between adjacent network nodes is adopted.

In this example 4, the IAB node obtains and stores the relationship between the PDCP entity and its corresponding RLC entity that performs PDCP retransmission and the RLC SNs of the respective RLC PDUs used by different RLC entities that transmit the same PDCP PDU, through IAB donor step-by-step notification among the IAB nodes in advance. For example, when RLC1 SN of RLC PDU of RLC1 entity transmitting the same PDCP PDU is SN1, RLC2 SN of RLC PDU of RLC2 entity is SN1+ k.

Taking fig. 8 as an example for explanation, this example 2 includes:

1) the DU of IAB node #1 successfully receives RLC1PDU1 sent by the UE, but does not receive RLC2 PDU 1;

2) the IAB node #1 deduces the RLC SN of the RLC2 PDU1 carrying the same PDCP PDU with the RLC1PDU1 according to the corresponding relation of the RLC SNs of the respective RLC PDUs carrying the same PDCP PDUs by the RLC1 and the RLC2, and the DU of the IAB node #1 sends positive feedback RLC ARQ of the RLC1PDU1 and the RLC2 PDU1 to an upper node (namely UE);

3) the IAB node #1 constructs RLC2 PDU1 according to the estimated RLC SN of RLC2 PDU1 and the load part (namely PDCP PDU) of RLC1PDU 1;

4) the MT of the IAB node #1 transmits RLC1PDU1 and RLC2 PDU1 to the lower node (IAB node #2 in the drawing) on the respective RLC entities. Further, if the subordinate receiving node is already the final receiving node (e.g. the transmission sent by the IAB node #2 to the IAB node in the figure), the IAB node #2 may not send the RLC2 PDU1 after receiving the positive feedback of the RLC1PDU1 sent by the IAB node.

Various methods of embodiments of the present invention have been described above. An apparatus for carrying out the above method is further provided below.

Referring to fig. 9, an embodiment of the present invention provides a data transmission apparatus 90, which may be applied to a first node in a relay network architecture for data transmission via a relay node, where when the first node performs PDCP duplicate transmission, one PDCP protocol data unit PDU is mapped to at least two RLC entities, and is organized into at least two RLC PDU transmissions. As shown in fig. 9, the data transmission device 90 specifically includes:

a feedback information generating module 91, configured to generate successful reception feedback information for a second RLC PDU after it is determined that a first RLC PDU is successfully received, where the first node is an intermediate relay node in the relay network architecture or a node that finally receives data, and the second RLC PDU and the first RLC PDU are RLC PDUs that are generated by different RLC entities and include the same PDCP PDU;

a feedback information sending module 92, configured to send the successful receiving feedback information of the second RLC PDU to the upper node through the second RLC entity.

Optionally, the data transmission device 90 further includes:

a first determining module (not shown in the figure), configured to receive first feedback information, which is fed back by a subordinate node and used to indicate that the first RLC PDU is successfully received, and determine, according to the first feedback information, that the first RLC PDU is successfully sent to the subordinate node.

Optionally, the feedback information generating module 91 is further configured to generate, when the first node has received the second RLC PDU, second feedback information for indicating that the second RLC PDU is successfully received according to the second RLC PDU.

Optionally, the data transmission device 90 further includes:

a transmission canceling module (not shown) configured to cancel sending the second RLC PDU to a lower node when the first node has received the second RLC PDU.

Optionally, the PDCP PDU receiving confirmation method of the PDCP repeated transmission is end-to-end RLC feedback between the terminal and a first-level network node in the relay network architecture.

Optionally, the data transmission device 90 further includes:

a second determining module (not shown in the figure), configured to determine that the first RLC PDU is successfully received after the first node receives the first RLC PDU sent by the upper node.

Optionally, the feedback information generating module 91 is further configured to, when the first node does not receive the second RLC PDU, determine a logical channel identifier LCID and a second RLC SN of the second RLC PDU corresponding to the first RLC PDU according to a pre-obtained RLC mapping relationship corresponding to a superior node, and generate third feedback information indicating that the second RLC PDU is successfully received according to the LCID and the second RLC SN of the second RLC PDU.

Optionally, the data transmission device 90 further includes:

a sending processing module (not shown in the figure), configured to determine, when the first node does not receive the second RLC PDU, a third RLC SN of the second RLC PDU at the sending end of the first node according to a correspondence between RLC SN values of different RLC entities including the same PDCP PDU; constructing a third RLC PDU according to a pre-obtained RLC mapping relation corresponding to a subordinate node, the PDPC PDU contained in the first RLC PDU and the third RLC SN; and transmitting the third RLC PDU to a subordinate node.

Optionally, the PDCP PDU reception confirmation method of the PDCP repeated transmission is a hop-by-hop RLC feedback between adjacent network nodes.

Optionally, the data transmission device 90 further includes:

an information holding unit (not shown in the figure) for holding at least one of the following information of different RLC PDUs including the same PDCP PDU, before it is determined that the first RLC PDU is successfully received:

a terminal identifier and a bearer identifier;

finally receiving the node identification of the data;

RLC mapping relation corresponding to the superior node;

RLC mapping relation corresponding to subordinate node;

the RLC mapping relation comprises a logical channel identifier and an RLC SN.

Referring to fig. 10, an embodiment of the present invention provides a structural schematic diagram of a first node 1000, including: a processor 1001, a transceiver 1002, a memory 1003, and a bus interface, wherein:

in this embodiment of the present invention, the first node 1000 further includes: a program stored on the memory 1003 and executable on the processor 1001, which when executed by the processor 1001 performs the steps of:

and sending the successful receiving feedback information of the second RLC PDU to the superior node through the second RLC entity.

It can be understood that, in the embodiment of the present invention, when the computer program is executed by the processor 1001, each process of the data transmission method embodiment shown in fig. 4 can be implemented, and the same technical effect can be achieved.

In fig. 10, the bus architecture may include any number of interconnected buses and bridges, with one or more processors represented by processor 1001 and various circuits of memory represented by memory 1003 being linked together. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further herein. The bus interface provides an interface. The transceiver 1002 may be a number of elements including a transmitter and a receiver that provide a means for communicating with various other apparatus over a transmission medium.

The processor 1001 is responsible for managing a bus architecture and general processes, and the memory 1003 may store data used by the processor 1001 in performing operations.

In some embodiments of the invention, there is also provided a computer readable storage medium having a program stored thereon, which when executed by a processor, may implement the following steps on a first node:

When executed by the processor, the program can implement all the implementation manners in the data transmission method applied to the first node, and can achieve the same technical effect, and is not described herein again to avoid repetition.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.

It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

In the embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment of the present invention.

In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned storage medium includes: various media capable of storing program codes, such as a U disk, a removable hard disk, a ROM, a RAM, a magnetic disk, or an optical disk.

The above description is only for the specific embodiments of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present invention, and all the changes or substitutions should be covered within the scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.

Claims

1. A data transmission method applied to a first node in a relay network architecture for data transmission via a relay node, wherein when the first node performs PDCP retransmission, one PDCP protocol data unit PDU is mapped to at least two RLC entities, organized into at least two RLC PDU transmissions, the method comprising:

2. The method of claim 1, wherein prior to generating the successful reception feedback information for the second RLC PDU, the method further comprises:

3. The method of claim 2, wherein generating successful reception feedback information for a second RLC PDU generated by a second RLC entity comprises:

4. The method of claim 3, wherein when the first node has received the second RLC PDU, the method further comprises:

the first node cancels the sending of the second RLC PDU to the lower node.

5. The method of claim 3, wherein the PDCP PDU reception confirmation for PDCP repeated transmission is an end-to-end RLC feedback between a terminal and a first level network node in a relay network architecture.

6. The method of claim 1, wherein prior to determining successful reception of the first RLC PDU, the method further comprises:

7. The method of claim 6, wherein the step of generating successful reception feedback information for the second RLC PDU comprises:

8. The method of claim 7, wherein when the first node does not receive the second RLC PDU, the method further comprises:

and transmitting the third RLC PDU to a subordinate node.

9. The method of claim 7, wherein the PDCP PDU reception confirmation for PDCP repeated transmission is a hop-by-hop RLC feedback between neighboring network nodes.

10. The method of any of claims 1 to 9, wherein prior to determining successful reception of the first RLC PDU, the method further comprises:

a terminal identifier and a bearer identifier;

finally receiving the node identification of the data;

RLC mapping relation corresponding to the superior node;

RLC mapping relation corresponding to subordinate node;

the RLC mapping relation comprises a logical channel identifier and an RLC SN.

11. A data transmission apparatus applied to a first node in a relay network architecture for data transmission via a relay node, wherein when the first node performs PDCP retransmission, one PDCP protocol data unit PDU is mapped to at least two RLC entities, and is organized into at least two RLC PDU transmissions, the data transmission apparatus comprising:

12. A first node, comprising: a memory, a processor, a transceiver, and a program stored on the memory and executable on the processor; it is characterized in that the preparation method is characterized in that,

the processor implements the following steps when executing the program:

13. The first node of claim 12,

the processor, when executing the program, further implements the steps of: before generating the feedback information for successful receiving of the second RLC PDU, receiving first feedback information fed back by a subordinate node and used for indicating successful receiving of the first RLC PDU, and determining that the first RLC PDU is successfully sent to the subordinate node according to the first feedback information.

14. The first node of claim 13,

the processor, when executing the program, further implements the steps of: and when the first node receives the second RLC PDU, generating second feedback information for indicating the successful reception of the second RLC PDU according to the second RLC PDU.

15. The first node of claim 14,

the processor, when executing the program, further implements the steps of: and canceling the second RLC PDU from being sent to a lower node when the first node receives the second RLC PDU.

16. The first node of claim 12,

the processor, when executing the program, further implements the steps of: before generating the feedback information for successful receiving of the second RLC PDU, after the first node receives the first RLC PDU sent by the superior node, the first RLC PDU is determined to be successfully received.

17. The first node of claim 16,

the processor, when executing the program, further implements the steps of: and when the first node does not receive the second RLC PDU, determining a Logic Channel Identifier (LCID) and a second RLC SN of the second RLC PDU corresponding to the first RLC PDU according to a pre-obtained RLC mapping relation corresponding to a superior node, and generating third feedback information for indicating successful reception of the second RLC PDU according to the LCID and the second RLC SN of the second RLC PDU.

18. The first node of claim 17,

the processor, when executing the program, further implements the steps of: the processor, when executing the program, further implements the steps of: when the first node does not receive the second RLC PDU, determining a third RLC SN of the second RLC PDU at a transmitting end of the first node according to a corresponding relation of RLC SN values among different RLC entities containing the same PDCP PDU; constructing a third RLC PDU according to a pre-obtained RLC mapping relation corresponding to a subordinate node, the PDPC PDU contained in the first RLC PDU and the third RLC SN; and transmitting the third RLC PDU to a subordinate node.

19. A computer storage medium comprising instructions which, when executed on a computer, cause the computer to perform the method of any one of claims 1 to 10.