WO2020156569A1 - 发送rlc状态报告的方法、设备和存储介质 - Google Patents

发送rlc状态报告的方法、设备和存储介质 Download PDF

Info

Publication number
WO2020156569A1
WO2020156569A1 PCT/CN2020/074208 CN2020074208W WO2020156569A1 WO 2020156569 A1 WO2020156569 A1 WO 2020156569A1 CN 2020074208 W CN2020074208 W CN 2020074208W WO 2020156569 A1 WO2020156569 A1 WO 2020156569A1
Authority
WO
WIPO (PCT)
Prior art keywords
rlc
entity
status report
final destination
rlc entity
Prior art date
Application number
PCT/CN2020/074208
Other languages
English (en)
French (fr)
Inventor
肖芳英
堀贵子
Original Assignee
夏普株式会社
鸿颖创新有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 夏普株式会社, 鸿颖创新有限公司 filed Critical 夏普株式会社
Publication of WO2020156569A1 publication Critical patent/WO2020156569A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/1607—Details of the supervisory signal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1867—Arrangements specially adapted for the transmitter end

Definitions

  • the present disclosure relates to the field of wireless communication technology, and more specifically, the present disclosure relates to methods, devices, and corresponding storage media for sending and receiving RLC status reports in a multi-hop network.
  • the RLC status report reports the reception status of the RLC SDU or RLC PDU by the RLC receiving entity of the current hop.
  • the RLC sending entity receives the RLC status report, it indicates the successfully sent RLC SDU or RLC PDU to the PDCP entity, and the PDCP entity deletes the corresponding PDCP PDU and PDCP SDU after receiving the indication.
  • the uplink transmission if the data is successfully received by the access IAB node, the UE will delete the corresponding data, and then the access IAB node will forward the data to the next hop and delete it.
  • one of the goals proposed by the IAB work project is to define a mechanism to ensure packet loss-free transmission based on HbH ARQ. This disclosure is dedicated to solving the problem of transmission packet loss in HbH ARQ transmission.
  • the present disclosure proposes an enhanced RLC status report to realize end-to-end packet loss-free transmission in a multi-hop IAB network.
  • the proposed enhanced RLC status report contains indication information about the reception of RLC data units by the final destination RLC entity in multi-hop transmission.
  • the RLC sending entity can learn the receiving status of the RLC SDU by the final destination RLC entity through the enhanced RLC status report, so that it can identify the situation of packet loss on the way, and realize packet loss-free transmission through retransmission.
  • a method performed at a sending node in multi-hop transmission including: sending an inquiry to an RLC entity in direct communication; and receiving an RLC status report from the RLC entity,
  • the RLC status report includes information indicating the type of RLC status report, and at least one type of RLC status report includes information indicating whether the RLC data unit is received by the final destination RLC entity of the multi-hop data transmission.
  • the sending node may be user equipment. In other embodiments, the sending node may be a radio access network (RAN) node.
  • RAN radio access network
  • the method may further include: indicating the RLC data unit that receives a positive confirmation from the final destination RLC entity to the upper layer.
  • the method may further include: deleting the RLC data unit that has received a negative confirmation from the final destination RLC entity from the retransmission buffer.
  • the information indicating whether the RLC data unit is received by the final destination RLC entity of the multi-hop data transmission may include at least one of the following:
  • the RLC status report may include the following fields: a type field, a remote ACK_SN field, and a remote NACK_SN field, where:
  • the type field contains information indicating the type of RLC status report
  • the remote ACK_SN field indicates the maximum sequence number of the RLC data unit correctly received by the final destination RLC entity, or indicates the sequence number of the next RLC data unit not received by the final destination RLC entity,
  • the remote NACK_SN field indicates the sequence number of the RLC data unit detected as lost by the final destination RLC entity.
  • the RLC status report may include the following fields: a type field, a remote ACK_SN field, a remote NACK_SN field, and a remote NACK_range field, where:
  • the type field contains information indicating the type of RLC status report
  • the remote ACK_SN field indicates the maximum sequence number of the RLC data unit correctly received by the final destination RLC entity, or indicates the sequence number of the next RLC data unit not received by the final destination RLC entity,
  • the remote NACK_SN field indicates the sequence number of the RLC data unit detected as lost by the final destination RLC entity
  • the remote NACK_range field indicates the number of RLC data units that are continuously lost starting from the corresponding remote NACK_SN.
  • the RLC status report may include the following fields: a type field and a remote ACK_SN field, where:
  • the type field contains information indicating the type of RLC status report
  • the remote ACK_SN field indicates the maximum sequence number of the RLC data unit correctly received by the final destination RLC entity, or indicates the sequence number of the next RLC data unit not received by the final destination RLC entity.
  • the RLC status report may include the following fields: type field, FMSN field, and Bitmap field, where:
  • the type field contains information indicating the type of RLC status report
  • the FMSN field indicates the sequence number of the first lost RLC data unit detected by the final destination RLC entity
  • the Bitmap field indicates which RLC data units are correctly received by the final destination RLC entity after the FMSN and/or which RLC data units are detected as missing bitmaps by the final destination RLC entity.
  • the RLC status report may include the following fields: a type field, a first indication field, an ACK_SN field, and a NACK_SN field, where:
  • the type field contains information indicating the type of RLC status report
  • the first indication field indicates whether the ACK_SN field and the NACK_SN field are related to the final destination RLC entity or the directly communicating RLC entity,
  • the ACK_SN field indicates the maximum sequence number of the correctly received RLC data unit, or indicates the sequence number of the next unreceived RLC data unit,
  • the NACK_SN field indicates the sequence number of the RLC data unit detected as being lost.
  • the RLC status report includes the following fields: a type field, a first indication field, a remote ACK_SN field, and a NACK_SN field,
  • the type field contains information indicating the type of RLC status report
  • the first indication field indicates whether the NACK_SN field is related to the final destination RLC entity or the directly communicating RLC entity,
  • the remote ACK_SN field indicates the maximum sequence number of the RLC data unit correctly received by the final destination RLC entity, or indicates the sequence number of the next RLC data unit not received by the final destination RLC entity,
  • the NACK_SN field indicates the sequence number of the RLC data unit detected as being lost.
  • a method performed at a receiving node in a multi-hop transmission including: constructing a radio link control RLC status report, the RLC status report including information indicating the type of the RLC status report And at least one type of RLC status report includes information indicating whether the RLC data unit is received by the final destination RLC entity of the multi-hop data transmission; and the RLC status report is sent.
  • the constructing the RLC status report is performed in response to receiving the query.
  • the method further includes: receiving an inquiry from a directly communicating RLC entity in the path of the multi-hop data transmission.
  • the receiving node may be user equipment. In other embodiments, the receiving node may be a radio access network (RAN) node.
  • RAN radio access network
  • a first communication device including: a sending module configured to send an inquiry to an RLC entity in direct communication; and a receiving module configured to receive RLC status from the RLC entity Report, the RLC status report includes information indicating the type of RLC status report, and at least one type of RLC status report includes information indicating whether the final destination RLC entity of the multi-hop data transmission has received the RLC data unit.
  • the first communication device may include: user equipment and a radio access network RAN node.
  • a second communication device including: a processing module configured to: construct a radio link control RLC status report, the RLC status report including information indicating the type of the RLC status report, and At least one type of RLC status report includes information indicating whether the final destination RLC entity of the multi-hop data transmission receives the RLC data unit; and the sending module is configured to send the RLC status report.
  • the first communication device may include: user equipment and a radio access network RAN node.
  • a first communication device including: a sending module configured to send an inquiry to an RLC entity in direct communication; and a receiving module configured to receive RLC status from the RLC entity Report, the RLC status report includes information indicating the type of RLC status report, and at least one type of RLC status report includes information indicating whether the final destination RLC entity of the multi-hop data transmission has received the RLC data unit.
  • the first communication device may include: user equipment and a radio access network RAN node.
  • a second communication device including: a processing module configured to: construct a radio link control RLC status report, the RLC status report including information indicating the type of the RLC status report, and At least one type of RLC status report includes information indicating whether the final destination RLC entity of the multi-hop data transmission receives the RLC data unit; and the sending module is configured to send the RLC status report.
  • the first communication device may include: user equipment and a radio access network RAN node.
  • a communication device including: a processing module, a receiving module, and a sending module.
  • the processing module is configured to: construct a radio link control RLC status report, the RLC status report includes information indicating the type of RLC status report, and at least one type of RLC status report includes indicating the final destination of multi-hop data transmission Whether the RLC entity receives the information of the RLC data unit.
  • the receiving module is configured to receive queries and/or RLC status reports from other communication devices.
  • the sending module is configured to send RLC status reports and/or queries to other communication devices.
  • a communication device including: a processor, and a memory, on which machine-readable instructions are stored.
  • the processor executes the The method of the first or second aspect of the present disclosure.
  • a computer-readable storage medium having machine-readable instructions stored thereon.
  • the processor executes the or The second method.
  • Figure 1 shows a schematic diagram of uplink data transmission in a multi-hop IAB network.
  • Figure 2 shows a schematic diagram of downlink data transmission in a multi-hop IAB network.
  • Fig. 3 shows a flowchart of a method executed at a sending node in multi-hop transmission according to an embodiment of the present invention.
  • Fig. 4 shows a flowchart of a method executed at a receiving node in a multi-hop transmission according to an embodiment of the present invention.
  • Fig. 5 shows a schematic block diagram of a first communication device according to an embodiment of the present invention.
  • Fig. 6 shows a schematic block diagram of a second communication device according to an embodiment of the present invention.
  • Fig. 7 shows a schematic block diagram of a communication device according to another embodiment of the embodiment of the present invention.
  • Fig. 8 shows a schematic block diagram of a communication device according to yet another embodiment of the embodiments of the present invention.
  • Figures 9 to 16 show an example of the structure of an RLC status report according to an embodiment of the present invention.
  • Figure 17 shows another schematic diagram of uplink data transmission in a multi-hop IAB network.
  • PDCP Packet Data Convergence Protocol, packet data convergence protocol.
  • RLC Radio Link Control, radio link control.
  • the transmission mode of the RLC entity can be configured as one of transparent transmission mode TM, unconfirmed mode UM or confirmed mode AM.
  • the RLC entity When the RLC entity is configured in the transparent transmission mode TM, the unconfirmed mode UM, or the confirmed mode AM, it can be called a TM RLC entity, a UM RLC entity or an AM RLC entity, respectively.
  • TM RLC entity a TM RLC entity
  • UM RLC entity UM RLC entity
  • AM RLC entity In the current 3GPP communication system, only AM RLC entities support ARQ.
  • peer RLC entities all refer to peer AM RLC entities; correspondingly, AM RLC entity sender peer AM RLC
  • the entity refers to the AM RLC entity receiving end that directly communicates (ie, the same hop), and the peer AM RLC entity of the AM RLC entity receiving end refers to the AM RLC entity sending end that directly communicates (ie, the same hop).
  • the sending end of the RLC entity and the receiving end of the RLC entity that directly communicate (that is, the same hop) are called peer RLC entities.
  • the RLC entity refers to the AM RLC entity.
  • AMD AM data, AM data.
  • FIG. 1 shows a schematic diagram of uplink data transmission in a multi-hop IAB network.
  • RLC Tx is the sender of the RLC entity
  • RLC Rx is the receiver of the RLC entity.
  • the sending end of the RLC entity and the receiving end of the RLC entity that directly communicate are referred to as peer RLC entities.
  • the peer entity of the RLC Tx in the UE is the RLC Rx in the IAB node 1, and vice versa.
  • the peer entity of the RLC Tx in the IAB node 1 is the RLC Rx in the IAB node 2, and vice versa.
  • the peer entity of the RLC Tx in the IAB node 2 is the RLC Rx in the IAB donor, and vice versa.
  • the RLC Rx located in the IAB donor is referred to as the remote RLC entity of the RLC Tx in the UE.
  • the IAB donor or the IAB donor DU or the RLC entity receiving end in the IAB donor DU is the ultimate destination of uplink data transmission.
  • FIG. 2 shows a schematic diagram of multi-hop IAB network downlink data transmission.
  • the peer entity of the RLC Tx in the IAB donor is the RLC Rx in the IAB node 2.
  • the peer entity of the RLC Tx in the IAB node 2 is the RLC Rx in the IAB node 1, and vice versa.
  • the peer entity of the RLC Tx in the IAB node 1 is the RLC Rx in the UE, and vice versa.
  • the RLC Rx located in the UE is referred to as the remote RLC entity of the RLC Tx in the IAB donor.
  • the UE or the receiving end of the RLC entity in the UE is the final destination of downlink data transmission.
  • the previous hop/next hop refers to the peer RLC entity of the RLC entity, that is, the entity that directly communicates.
  • the previous hop of IAB node 1 is the user equipment, and the next The hop is IAB node 2.
  • the next hop of IAB node 1 is the user equipment, and the previous hop is IAB node 2.
  • MAC Medium Access Control, media access control.
  • PDU Protocol Data Unit, protocol data unit.
  • SDU Service Data Unit, service data unit.
  • the data received from or sent to the upper layer is called SDU, and the data sent to or received from the lower layer is called PDU.
  • PDU and SDU are also collectively referred to as data units.
  • the data received by the RLC entity from the upper layer or the data sent to the upper layer is called RLC SDU; the data received by the RLC entity from the MAC entity or the data sent to the MAC entity is called RLC PDU.
  • RLC PDU and RLC SDU are also collectively referred to as RLC data unit.
  • the PDCP entity is the upper layer of the RLC entity.
  • the adaptation entity is the upper layer of the RLC entity.
  • the adaptation PDU is an RLC SDU, because the adaptation entity directly forwards it according to the data forwarding rule or the UE ID or the logical channel ID after receiving the RLC SDU.
  • the adapted SDU is the RLC SDU. This is because, when the access IAB node receives the adaptation PDU from other IAB nodes or IAB donors, the adaptation entity removes the header of the adaptation PDU and obtains the result according to the data forwarding rules or UE ID or logical channel ID
  • the adapted SDU is submitted to the lower layer or the RLC layer. At this time, the RLC SDU is the adapted SDU.
  • the IAB node when the IAB node receives the RLC SDU from the RLC entity of the local UE, it adds an adaptation header to obtain an adapted PDU and forwards it according to the data forwarding rule.
  • the adaptation entity receives the RLC SDU from the RLC entity and forwards it to another RLC entity according to the destination address.
  • the RLC SDU is an adaptation PDU. Therefore, in the embodiments of the present disclosure, the RLC SDU containing the adaptation layer header (for example, the RLC SDU from another IAB node or IAB donor in the downlink transmission) is called the adaptation PDU, and the adaptation layer header is not included.
  • the RLC SDU in the uplink transmission, the RLC SDU from the local UE is called the adapted SDU.
  • IAB-node refers to the RAN node that supports wireless access and wireless backhaul access traffic of user equipment (RAN node that supports wireless access to UEs and wirelessly backhauls the access traffic).
  • the IAB node used to support the wireless access of the UE is called the access IAB node of the UE, and the corresponding UE is called the local UE of the IAB node.
  • IAB donor IAB-donor, RAN node which provides UE interface for core network and wireless backhaul function for IAB node (RAN node which provides UE’s interface to core network and wireless backhauling functionality to IAB-nodes).
  • the status PDU can also be called RLC status PDU, which includes the load of the status PDU and the RLC control PDU header.
  • the RLC control PDU header may contain a D/C field and a CPT field.
  • the D/C field indicates whether an RLC PDU is an RLC data PDU or an RLC control PDU.
  • the value of the D/C field is 0, indicating that the RLC PDU is an RLC control PDU; the value of the D/C field is 1, indicating that the RLC PDU is an RLC data PDU.
  • the CPT (Control PDU Type) field indicates the type of the RLC control PDU.
  • the RLC status report (also referred to as status PDU) defined in 3GPP TS38.322 is called the first RLC status report.
  • the first RLC status report is used by the receiving end of the AM RLC entity to inform the peer AM RLC entity which RLC data PDUs are successfully received and which RLC data PDUs are detected as lost by the receiving end of the AM RLC entity.
  • DRB Data Radio Bearer carrying user plane data, a data radio bearer that carries user plane data or simply a data radio bearer.
  • SRB Signaling Radio Bearer, signaling radio bearer.
  • CU Central Unit, the central unit or gNB-CU.
  • a CU has (hosting) or at least the RRC, SDAP and PDCP protocols of the base station or the RRC and PDCP protocols of the en-gNB, and controls one or more DUs or gNB-DUs.
  • the gNB-CU terminates the F1 interface connected to the gNB-DU.
  • CU can be divided into CU-CP (or gNB-CU-CP) and CU-UP (or gNB-CU-UP).
  • CU-CP is a logical node that carries the control plane part of the PDCP protocol of RRC and gNB-CU, and is used for en-gNB or gNB.
  • the gNB-CU-CP terminates the E1 interface connected to gNB-CU-UP and the F1-C interface connected to gNB-DU.
  • CU-UP is a logical node used to carry the user plane part of the PDCP protocol of gNB-CU of en-gNB, the user plane part of PDCP protocol of gNB-CU and the SDAP protocol of gNB-CU.
  • the gNB-CU-UP terminates the E1 interface connected to the gNB-CU-CP and the F1-U interface connected to the gNB-DU.
  • a DU Distributed Unit, distributed unit.
  • a DU is a logical node with or at least RLC, MAC, and physical layer.
  • the DU can be located in the IAB node or the IAB donor. In the IAB node or IAB donor, the DU may also have an adaptation layer.
  • MT Mobile-Termination, mobile terminal.
  • MT is the radio interface layer used in the IAB node to terminate the backhaul Uu interface with the IAB donor or other IAB nodes (MT is referred to as a function resisting on an IAB-node that terminates the radio interface layers of the backhaul Uu interface toward the IAB-donor or other IAB-nodes).
  • Each IAB node connects to an uplink IAB node or an IAB donor through an MT, and establishes an RLC channel with a UE or a MT of a downlink IAB node through the DU.
  • the IAB donor supports the MT of the UE and the downlink IAB node through the DU.
  • the AM RLC entity transmitter of the IAB node in uplink transmission, is located at the MT, and the AM RLC entity receiver of the IAB node is located at the DU; in downlink transmission, the AM RLC entity transmitter of the IAB node is located at the DU, and the AM RLC entity of the IAB node is located at the DU.
  • the receiving end of the entity is located at the MT.
  • RLC-BearerConfig cell The cell is used to configure the RLC entity, the corresponding logical channel in the MAC, and the association with the PDCP entity (service bearer) (used to configure an RLC entity, a corresponding logical channel in MAC and the linking to a PDCP entity (served radio bearer)).
  • Fig. 3 shows a flowchart of a method 100 executed at a sending node in a multi-hop transmission according to an embodiment of the present invention.
  • the sending node may refer to the source node or any intermediate node in multi-hop transmission, and it may be a user equipment or a RAN node.
  • the sending node may be the UE or IAB node 1 or IAB node 2.
  • the sending node may be an IAB donor or IAB node 2 or IAB node 1.
  • the method 100 may be executed by the AM RLC entity of the sending node.
  • step S110 send an inquiry or an RLC PDU containing the inquiry to the directly communicating RLC entity (that is, the peer RLC entity, or the next-hop RLC entity).
  • the directly communicating RLC entity that is, the peer RLC entity, or the next-hop RLC entity.
  • step S120 an RLC status report is received from the peer RLC entity, the RLC status report includes information indicating the type of RLC status report, and at least one type of RLC status report includes the final destination RLC indicating the multi-hop data transmission Whether the entity receives the information of the RLC data unit.
  • the types of the RLC status report are divided into at least two types.
  • the first type is the RLC status report defined in the aforementioned 3GPP TS38.322 (referred to as the first RLC status report).
  • the first RLC status report indicates which RLC data units (RCL SDU or RLC PDU) are successfully received by the peer AM RLC entity and which RLC data units are detected as lost by the peer AM RLC entity. That is, the feedback information in the first RLC status report is related to the reception status of the peer RLC entity.
  • the second type is the enhanced RLC status report proposed by the present disclosure (hereinafter also referred to as the second RLC status report).
  • the second RLC status report includes information indicating whether the RLC data unit is received by the final destination RLC entity of the multi-hop data transmission. That is, the enhanced RLC status report contains feedback information related to the reception status of the final destination RLC entity.
  • the enhanced RLC status report may also include feedback information related to the reception of the peer RLC entity, such as all or part of the information specified in the existing first RLC status report.
  • the information indicating whether the final destination RLC entity of the multi-hop data transmission receives the RLC data unit may include at least one of the following:
  • the sequence number of the next RLC data unit not received by the final destination RLC entity is not included in the RLC status report and the RLC data unit detected as lost by the final destination RLC entity In the serial number.
  • the information indicating whether the final destination RLC entity of the multi-hop data transmission receives the RLC data unit may be indicated by one or more fields in the second RLC status report.
  • the second RLC report For illustrative purposes, not limitation, several alternative examples of the second RLC report are shown below.
  • the second RLC status report includes the following fields: type field, remote ACK_SN field, and remote NACK_SN field, where,
  • the type field contains information indicating the type of RLC status report
  • the remote ACK_SN field indicates the maximum sequence number of the RLC data unit correctly received by the final destination RLC entity, or indicates the sequence number of the next RLC data unit not received by the final destination RLC entity, the sequence of the RLC data unit The number is not included in the sequence number of the RLC data unit that is detected as lost by the final destination RLC entity contained in the RLC status report,
  • the remote NACK_SN field indicates the sequence number of the RLC data unit detected as lost by the final destination RLC entity.
  • the second RLC status report may include the following fields: type field, remote ACK_SN field, remote NACK_SN field, and remote NACK_range field, where,
  • the type field contains information indicating the type of RLC status report
  • the remote ACK_SN field indicates the maximum sequence number of the RLC data unit correctly received by the final destination RLC entity, or indicates the sequence number of the next RLC data unit not received by the final destination RLC entity (the sequence of the RLC data unit The number is not included in the sequence number of the RLC data unit that is detected as lost by the final destination RLC entity included in the RLC status report),
  • the remote NACK_SN field indicates the sequence number of the RLC data unit detected as lost by the final destination RLC entity
  • the remote NACK_range field indicates the number of RLC data units that are continuously lost starting from the corresponding remote NACK_SN.
  • the second RLC status report may include the following fields: a type field and a remote ACK_SN field, where,
  • the type field contains information indicating the type of RLC status report
  • the remote ACK_SN field indicates the maximum sequence number of the RLC data unit correctly received by the final destination RLC entity, or indicates the sequence number of the next RLC data unit not received by the final destination RLC entity.
  • the second RLC status report may include the following fields: type field, FMSN field, and Bitmap field, where,
  • the type field contains information indicating the type of RLC status report
  • the FMSN field indicates the sequence number of the first lost RLC data unit detected by the final destination RLC entity
  • the Bitmap field indicates which RLC data units are correctly received by the final destination RLC entity after the FMSN and/or which RLC data units are detected as missing bitmaps by the final destination RLC entity.
  • the second RLC status report may include the following fields: a type field, a first indication field, an ACK_SN field, and a NACK_SN field, where,
  • the type field contains information indicating the type of RLC status report
  • the first indication field indicates whether the ACK_SN field and the NACK_SN field are related to the final destination RLC entity or the directly communicating RLC entity,
  • the ACK_SN field indicates the maximum sequence number of the correctly received RLC data unit, or indicates the sequence number of the next unreceived RLC data unit,
  • the NACK_SN field indicates the sequence number of the RLC data unit detected as being lost.
  • the second RLC status report may include the following fields: type field, first indication field, remote ACK_SN field, and NACK_SN field, where,
  • the type field contains information indicating the type of RLC status report
  • the first indication field indicates whether the NACK_SN field is related to the final destination RLC entity or the directly communicating RLC entity,
  • the remote ACK_SN field indicates the maximum sequence number of the RLC data unit correctly received by the final destination RLC entity, or indicates the sequence number of the next RLC data unit not received by the final destination RLC entity,
  • the NACK_SN field indicates the sequence number of the RLC data unit detected as being lost.
  • the second RLC status report may not only include feedback information related to the reception status of the final destination RLC entity, but also include feedback information related to the reception status of the peer RLC entity, such as existing All or part of the information specified in the first RLC status report.
  • the type field may be a new field, or an existing field (such as a CPT field) may be reused. This will be described in detail below.
  • the method 100 may also include processing the received RLC status report.
  • the method 100 may include: parsing the received RLC status report to obtain a positive acknowledgement ACK and/or a negative acknowledgement NACK for the RLC data unit.
  • the method 100 may further include: for the RLC data unit that receives a positive confirmation from the final destination RLC entity, indicating it to the upper layer.
  • the method 100 may further include: deleting the RLC protocol data unit and/or the RLC service data unit that received the negative confirmation from the final destination RLC entity from the retransmission buffer.
  • the receiving node (specifically, its RLC sending entity) can learn the receiving status of the RLC SDU by the final destination RLC entity through the received second RLC status report, so that it can identify the situation of packet loss on the way, and through re Transmission achieves no packet loss transmission.
  • FIG. 4 shows a flowchart of a method 200 executed at a receiving node in a multi-hop transmission according to an embodiment of the present invention.
  • the receiving node may refer to the final destination node in multi-hop transmission or any intermediate node, and it may be a user equipment or a RAN node.
  • the receiving node may be a UE or an IAB node 1 or an IAB node 2.
  • the receiving node may be an IAB donor or IAB node 2 or IAB node 1.
  • the method 200 may be executed by the AM RLC entity of the receiving node.
  • step S210 construct a radio link control RLC status report, the RLC status report includes information indicating the type of RLC status report, and at least one type of RLC status report includes the final report indicating multi-hop data transmission Whether the destination RLC entity receives the RLC data unit information.
  • step S220 the constructed RLC status report is sent. In other words, submit the constructed RLC status report to the lower layer.
  • step S210 is performed in response to receiving a query.
  • the method 200 further includes: receiving an inquiry from the directly communicating RLC entity (ie, the previous hop RLC entity) in the path of multi-hop data transmission. This query is used by the RLC entity sender to request its peer RLC entity to send a status report.
  • RLC entity ie, the previous hop RLC entity
  • the types of the RLC status report are divided into at least two types.
  • the first type is the RLC status report defined in the aforementioned 3GPP TS38.322 (referred to as the first RLC status report).
  • the second type is the enhanced RLC status report proposed by the present disclosure (hereinafter also referred to as the second RLC status report).
  • the two types of RLC status reports have been described in detail with reference to Figure 3, and will not be repeated here.
  • Fig. 5 shows a schematic block diagram of a first communication device 10 according to an embodiment of the present invention.
  • the first communication device 10 may include a sending module 12 and a receiving module 14.
  • the sending module 12 may be configured to send an inquiry to the directly communicating RLC entity.
  • the receiving module 14 may be configured to receive an RLC status report from the RLC entity, the RLC status report includes information indicating the type of the RLC status report, and at least one type of RLC status report includes an RLC entity indicating the final destination of multi-hop data transmission Whether to receive RLC data unit information.
  • the first communication device may include: user equipment and a radio access network RAN node.
  • the first communication device 10 may further include a processing module and/or a storage unit, etc.
  • the first communication device 10 may be a sending node that executes the method 100 described with reference to FIG. 3, where the sending module 12 and the receiving module 14 may execute steps S110 and S120, respectively. Similarly, the first communication device 10 may be a user equipment or a RAN node.
  • Fig. 6 shows a schematic block diagram of a second communication device 20 according to an embodiment of the present invention.
  • the second communication device 20 may include a processing module 22 and a sending module 24.
  • the processing module 22 may be configured to: construct a radio link control RLC status report, the RLC status report including information indicating the type of the RLC status report, and at least one type of RLC status report including the final destination RLC entity indicating the multi-hop data transmission Whether to receive RLC data unit information.
  • the sending module 24 may be configured to send the constructed RLC status report.
  • the second communication device 20 may further include a receiving module.
  • the receiving module may be configured to receive an inquiry from an RLC entity in direct communication in the path of multi-hop data transmission.
  • the second communication device 20 may also include a storage unit and the like.
  • the second communication device 20 may be a receiving node that executes the method 200 described with reference to FIG. 4, where the processing module 22 and the sending module 24 may execute steps S210 and S220, respectively.
  • the second communication device 20 may be a user equipment or a RAN node.
  • FIG. 7 shows a schematic block diagram of a communication device 30 according to another embodiment of the embodiment of the present invention.
  • the communication device 30 may include a sending module 32, a receiving module 34, and a processing module 36.
  • the processing module 36 may be configured to construct a radio link control RLC status report, the RLC status report including information indicating the type of the RLC status report, and at least one type of RLC status report including indicating the final destination RLC entity for multi-hop data transmission Whether to receive RLC data unit information.
  • the sending module 32 may be configured to send RLC status reports and/or queries to other communication devices.
  • the receiving module 34 may be configured to receive queries and/or RLC status reports from other communication devices.
  • the communication device 30 may execute the method 100 when operating as a sending node, and may execute the method 200 when operating as a receiving node.
  • FIG. 8 shows a schematic block diagram of a communication device 40 according to still another embodiment of the embodiments of the present invention.
  • the communication device 40 may include a transceiver 42, a processor 44, and a memory 46.
  • the communication device 40 may be a specific implementation example of the first communication device 10, the second communication device 20, or the communication device 30 described above.
  • the processor 46 may store instructions executable by the processor 44 to enable the communication device 40 to execute the method 100 and/or 200 described above in conjunction with FIG. 3 and/or FIG. 4.
  • the RLC data unit in the embodiment of the present disclosure may be RLC_SDU or RLC_PDU.
  • the RLC data unit included in the status report indication to indicate to the upper layer or forwarding the RLC entity is RLC_SDU, and the RLC status report includes the positive or negative confirmation of the RLC_PDU.
  • remote ACK_SN, remote NACK_SN, and remote NACK_range fields mentioned in the present disclosure have the same meanings as the second ACK_SN, second NACK_SN, and second NACK_range fields in the following embodiments, respectively.
  • the following describes the operations that need to be performed by the AM RLC entity transmitter in the IAB node.
  • the AM RLC entity transmitter receives an RLC status report (also referred to as a status PDU) from a peer entity (for example, a user equipment or other IAB node or an AM RLC entity receiver of an IAB donor).
  • the RLC status report is the first RLC status report or the second RLC status report.
  • the status report may include one or more of the following fields: CPT, RLC status report type, first ACK_SN, second ACK_SN, first NACK_SN, SOstart, SOend, E1, E2, E3, E4, first NACK_range , The second NACK_SN, the second NACK_range.
  • the status report may also include other extension fields E5, E6, and so on.
  • CPT represents the type of RLC control PDU
  • RLC status report type is used to indicate the type of the received status report
  • other fields in the RLC status PDU are related to the status report type
  • the RLC status report type field can be set to 0 or 1. .
  • different values of CPT may also be set to indicate different types of RLC status reports.
  • the RLC status report type field is not included in the first RLC status PDU and/or the second RLC status PDU.
  • Table 1 shows different RLC status reports by setting different values of CPT.
  • the status PDU is the first status PDU
  • the enhanced status PDU is the second status PDU.
  • the first status PDU may also be called the status PDU
  • the second status PDU is called the enhanced status PDU.
  • the status PDU is also called status report, which can be used alternatively in the embodiments of the present disclosure. It can be predefined.
  • the first RLC status report in the embodiment of the present disclosure is the RLC status report defined in the 3GPP standard document TS38.322, that is, when the CPT value is 000, it is the first RLC status report, and when the CPT value is 001 or 100 (other values can also be used) is the second RLC status report.
  • the first ACK_SN, the first NACK_SN, SOstart, SOend, E1, E2, E3, the first NACK_range and the ACK_SN, NACK_SN, SOstart, SOend, E1 defined in 3GPP TS38.322 , E2, E3, and NACK_range are the same and are the fields that can be included in the first status PDU.
  • the first ACK_SN is used to indicate the sequence number of the next unreceived RLC SDU (or RLC PDU) and the RLC SDU (or RLC PDU) is not reported as an unreceived RLC SDU (or RLC PDU) in the status PDU.
  • the unreceived RLC SDU (or PDU) can be indicated by the first NACK_SN and/or the first NACK_range and/or SOstart and/or SOend (it should be noted that in a multi-hop IAB network, the The first ACK_SN refers to the sequence number of the RLC SDU that has not been correctly received by the receiving end of the peer AM RLC entity).
  • the AM RLC entity sender When the AM RLC entity sender receives the status report, it considers that all RLC SDUs (or RLC PDUs) with sequence numbers smaller than ACK_SN have been received by its peer entity or peer AM RLC entity, except for the following: sequence number It is a part of the RLC SDU (or RLC PDU) indicating NACK_SN in the status PDU, part of the RLC SDU indicated by the status PDU with NACK_SN, SOstart and SOend, the RLC SDU indicated by the status PDU with NACK_SN and NACK_range, and the status PDU with NACK_SN, Part of the RLC SDU indicated by NACK_range, SOstart, and SOend.
  • the first NACK_SN is used to indicate the sequence number of the RLC SDU detected by the AM RLC entity receiving end as not received or lost.
  • the E1, E2, E3, and E4 fields are extended bit fields.
  • E1 is used to indicate whether there is a set of NACK_SN, E1, E2, E3, and/or E4 later (in this disclosure, whether there is a set later refers to whether the corresponding set is included after the extension bit in the corresponding PDU ).
  • a value of 0 in the E1 field indicates that there is no set of NACK_SN, E1, E2, E3, and/or E4 subsequently, and a value of 1 in the E1 field indicates that a set of NACK_SN, E1, E2, E3, and/or E4 is followed. vice versa.
  • E2 is used to indicate whether there is a subsequent set of SOstart and SOend.
  • the value of E2 is 0 to indicate no, and the value of E2 is 1 to indicate yes, and vice versa.
  • E3 is used to indicate whether it contains the information of continuous RLC and SDU that has not been received.
  • a value of E3 means that the corresponding NACK_SN does not include the NACK_range field, and the value of E3 is 1 means that the corresponding NACK_SN includes the NACK_range field.
  • the SOend field is used to indicate the position of the last byte of the missing part in the original RLC SDU (the SOend field indicators the position of the last byte of the portion of the RLC SDU in bytes within the original RLC SDU).
  • the first NACK_range field is used to indicate the number of RLC SDUs that are continuously lost starting from the first NACK_SN.
  • the second RLC status report may include one or more of the following fields: CPT field, first ACK_SN, first NACK_SN, SOstart, SOend, E1, E2, E3, first NACK_range, second ACK_SN, The second NACK_SN, E4.
  • the second ACK_SN indicates the maximum sequence number of the RLC SDU that has been confirmed correctly received by the receiving end of the final destination AM RLC entity or the receiving end of the final destination AM RLC entity indicates the next unreceived RLC SDU (or RLC PDU)
  • the RLC SDU (or RLC PDU) is not reported as an unreceived RLC SDU (or RLC PDU) in the status PDU, and the unreceived RLC SDU (or PDU) can be used by the second NACK_SN and/ Or the second NACK_range indication.
  • the second NACK_SN field indicates the sequence number of the RLC SDU that is detected as lost by the AM RLC entity receiver of the final destination.
  • E4 is used to indicate whether there is a second NACK_SN, E4 set subsequently. If the value of E4 is 0, it means that there is no NACK_SN, E4 set subsequently; if the value of E4 is 1, it means that there is a second NACK_SN, E4 set subsequently.
  • Figure 9 shows an example format of this second RLC status report when the sequence number is 12 bits in length.
  • the second RLC status report may also include an E5 extension field, which is used to indicate whether the NACK_SN, E4 set is included in the second status report. If the value of E5 is 0, it means that the second RLC status report does not include the NACK_SN, E4 set; if the value of E5 is 1, it means that the second RLC status report includes the second NACK_SN, E4 set.
  • Figure 10 shows an example format of this second RLC status report when the sequence number is 12 bits in length.
  • the second RLC status report may include one or more of the following fields: CPT field, first ACK_SN, first NACK_SN, SOstart, SOend, E1, E2, E3, first NACK_range, second ACK_SN , The second NACK_SN, the second NACK_range, E4, E5.
  • the second ACK_SN indicates the maximum sequence number of the RLC SDU that has been confirmed correctly received by the receiving end of the final destination AM RLC entity or the receiving end of the final destination AM RLC entity indicates the next unreceived RLC SDU (or RLC PDU) And the RLC SDU (or RLC PDU) is not reported as an unreceived RLC SDU (or RLC PDU) in the status PDU.
  • the unreceived RLC SDU (or RLC PDU) can be determined by the second NACK_SN and / Or the second NACK_range indication.
  • the second NACK_SN field indicates the sequence number of the RLC SDU that is detected as lost by the AM RLC entity receiver of the final destination.
  • the second NACK_range field is used to indicate the number of RLC SDUs continuously lost starting from the corresponding second NACK_SN.
  • the RLC SDUs whose sequence number SN is less than the second NACK_SN+the second NACK_range that is, the sum of the second NACK_SN and the second NACK_range) are all detected as lost by the AM RLC receiving end.
  • the RLC SDU whose sequence number SN satisfies the second NACK_SN ⁇ SN ⁇ second NACK_SN+the second NACK_range-1 is detected as lost by the AM RLC entity receiving end.
  • E4 is used to indicate whether there is a second NACK_SN, E4, E5 set subsequently. If the value of E4 is 0, it means that there is no second set of NACK_SN, E4, E5; if the value of E4 is 1, it means that there is a second set of NACK_SN, E4, and E5.
  • E5 is used to indicate whether it contains continuous RLC SDU information that has not been received.
  • FIG. 11 shows an example format of this second RLC status report when the sequence number is 12 bits in length.
  • E5 can also be replaced by E3, and the corresponding second NACK_rang field can also be replaced by the first NACK_rang field.
  • the second RLC status report further includes an E6 extension field, which is used to indicate whether the NACK_SN, E4, and E5 sets are included in the second status report. If the value of E6 is 0, it means that the second state report does not include the second set of NACK_SN, E4, and E5; if the value of E4 is 1, it means that the second state report includes the second set of NACK_SN, E4, and E5.
  • FIG. 12 shows an example format of the second RLC status report in this case when the sequence number is 12 bits in length.
  • the second RLC status report may include one or more of the following fields: CPT field, first ACK_SN, first NACK_SN, SOstart, SOend, E1, E2, E3, first NACK_range, second ACK_SN .
  • the second ACK_SN indicates the maximum sequence number of the RLC SDU that has been confirmed to be received correctly by the final destination or the remote AM RLC entity receiving end, or the final destination (or the remote AM RLC entity receiving end) indicates that the next one is not received The sequence number of the RLC SDU (or RLC PDU).
  • FIG. 13 shows an example format of the second RLC status report in this case when the length of the sequence number is 12 bits.
  • the second RLC status report may include one or more of the following fields: CPT field, first ACK_SN, first NACK_SN, first NACK_range, FMSN, SOstart, SOend, E1, E2, E3, E4, Bitmap, bitmap length, second ACK_SN.
  • the FMSN field is used to indicate the sequence number of the first RLC SDU or PDU that is confirmed as lost by the remote RLC entity in the sending window (or receiving window).
  • the extension field E4 is used to indicate whether there is a bitmap later or whether the status report contains a bitmap. Bitmap is used to indicate which RLC SDU (or PDU) is correctly received or detected as lost by the remote AM RLC entity receiver.
  • each bit in the bitmap with a value of 0 or 1 is shown in Table 2-1.
  • a value of 0 indicates that the corresponding RLC SDU is lost, and a value of 1 indicates that the corresponding RLC SDU is received correctly, and vice versa.
  • the position of the first bit of the bitmap in the bitmap (bit position) is 1, and the sequence number length refers to the number of bits occupied by the sequence number SN of the RLC SDU or PDU.
  • FIG. 14 shows an example format of the second RLC status report in this case when the sequence number is 12 bits in length.
  • the bitmap length field is used to indicate the number of bits occupied by the bitmap.
  • the peer RLC entity When the peer RLC entity receives the RLC status report, it considers that all RLC SDUs with sequence numbers less than or equal to FMSN+bitmap length and the bitmap value of 1 in the sending window are correctly received by the remote RLC entity. In addition, the maximum sequence number or PDU of the RLC SDU confirmed to be correctly received by the remote RLC entity or the sequence number of the next RLC SDU incorrectly received is FMSN+bitmap length+1. In other words, the sequence number of the next RLC data unit not received by the final destination RLC entity is FMSN+bitmap length+1.
  • the second ACK_SN indicates the maximum sequence number of the RLC SDU that has been confirmed by the receiving end of the final destination AM RLC entity to be correctly received or indicated by the receiving end of the final destination AM RLC entity as the next unreceived RLC SDU (or RLC PDU)
  • the sequence number and the RLC SDU (or RLC PDU) is not reported as unreceived RLC SDU (or RLC PDU) in the status PDU.
  • the unreceived RLC SDU (or RLC PDU) can be determined by the corresponding bit in the bitmap The value is 0. If the second ACK_SN field is included in the status report, the FMSN field may not be included. At this time, the interpretation of the bit value in the bitmap is shown in Table 2-2 or Table 2-3.
  • the second RLC status report includes one or more of the following fields: CPT field, ACK_SN, NACK_SN, SOstart, SOend, E1, E2, E3, E4, first NACK_range.
  • the E1 field indicates whether there is a subsequent set of NACK_SN, E1, E2, E3, and/or E4; if the E1 field takes a value of 0, it means that there is no subsequent set of NACK_SN, E1, E2, E3, and/or E4; if the E1 field takes a value If it is 1, it means that there is a set of NACK_SN, E1, E2, E3, and/or E4;
  • the value of the CPT field is the value corresponding to the first status report (for example, 000)
  • the E1 field indicates whether there is a subsequent set of NACK_SN, E1, E2, and E3 (as shown in Table 3); when the value of the CPT field is The value corresponding to the second status report (for example, 001 or 100), the E1 field indicates whether there is
  • the second RLC status report may include one or more of the following fields: CPT field, first ACK_SN, second ACK_SN, NACK_SN, SOstart, SOend, E1, E2, E3, E4, NACK_range.
  • the second ACK_SN indicates the maximum sequence number of the RLC SDU that has been confirmed correctly received by the receiving end of the final destination AM RLC entity or the receiving end of the final destination AM RLC entity indicates the next unreceived RLC SDU (or RLC PDU)
  • the RLC SDU (or RLC PDU) is not reported as an unreceived RLC SDU (or RLC PDU) in the status PDU, and the unreceived RLC SDU (or RLC PDU) can be set to the value of E4 1 corresponds to NACK_SN and/or NACK_range indication.
  • the unreceived RLC SDU may also be indicated by the NACK_SN and/or NACK_range corresponding to the value 0 of E4.
  • the E1 field indicates whether there is a subsequent set of NACK_SN, E1, E2, E3, and/or E4; if the E1 field takes a value of 0, it means that there is no subsequent set of NACK_SN, E1, E2, E3, and/or E4; if the E1 field takes a value If it is 1, it means that there is a set of NACK_SN, E1, E2, E3, and/or E4;
  • the CPT field takes the value corresponding to the first status report (for example, 000)
  • the E1 field indicates whether there is a subsequent set of NACK_SN, E1, E2, and E3 (for example, as shown in Table 3 above); when the CPT field takes a value For the value corresponding to the second status report (for example, 001 or 100), the E1 field indicates whether there is a subsequent set of NACK_SN, E
  • the E4 field indicates whether the NACK_SN, SOstart, SOend, and NACK_range fields are related to the final destination RLC entity or the directly communicating RLC entity. Specifically, the E4 field indicates whether the RLC SDU with the sequence number corresponding to NACK_SN is the next hop node (or peer RLC entity, that is, the AM RLC entity receiver) detected as lost or the final destination (for example, AM RLC in the IAB donor DU)
  • the SDU is the next hop node (or peer RLC entity, that is, AM RLC Whether the entity receiving end is detected as lost or the final destination (for example, the AM RLC entity receiving end in the IAB donor DU) is detected as being lost (for example, as shown in Table 5 above).
  • the final destination may also be referred to as the RAN destination or the remote AM RLC entity receiving end or the last hop. It is the destination to which the RLC SDU or PDU is finally sent, and the destination is the RAN The last jump.
  • the next hop may also be referred to as a peer RLC entity.
  • the second ACK_SN is used to indicate that the second ACK_SN is not used by the upper layer or the adaptation layer or the final
  • the destination or remote RLC entity receiving end confirms (or indicates) the sequence number of the received RLC SDU (or RLC PDU), or the second ACK_SN is used to indicate that it has been used by the upper layer or adaptation layer or the final destination or remote
  • the description of the second NACK_SN in the embodiment of the present disclosure is replaced with the following description.
  • the second NACK_SN field indicates the receiving end or upper layer or adaptation of the final destination or remote AM RLC entity
  • the layer or AM RLC entity receives the sequence number of the RLC SDU mapped to the AM RLC entity in the same node or user equipment and detected as lost by the transmitter.
  • FIG. 17 shows a schematic diagram of uplink data transmission.
  • IAB node 1 and IAB node 2 did not change their sequence numbers when forwarding the sequence numbers of RLC SDUs, but in a multi-hop IAB network based on hop-by-hop ARQ , RLC SDU may have different sequence numbers when sent between different nodes.
  • the IAB node will save the mapping relationship between the sequence number of the received RLC SDU or RLC PDU and the sequence number allocated for the RLC SDU or RLC PDU when the RLC SDU or RLC PDU is forwarded.
  • RLC status report when the RLC status report is received, it is also based on the mapping relationship to indicate to the corresponding forwarding RLC entity or to the upper layer related status report information (that is, which RLC SDUs are confirmed to be received correctly by the remote RLC entity, and which RLC The SDU is detected as lost by the remote RLC entity).
  • RLC Rx 1 received the RLC SDU (or RLC PDU) with sequence number SN 0, 2 to 7 from RLC Tx ue , but the RLC SDU (or RLC PDU) with sequence number 1 did not receive ( Or detected as lost).
  • RLC Tx 1 sends the RLC SDUs with sequence numbers 0, 2 to 6 in the received RLC SDU (or RLC PDU) to RLC Rx 2 , wherein the RLC SDUs (or RLC PDUs) with sequence numbers 2 and 6 are lost ( i.e. RLC Rx 2 are not received or detected as missing RLC Rx 2).
  • RLC Tx2 sends the RLC SDU (or RLC PDU) with sequence number 0, 3, 4 to RLC Rx3, but the RLC SDU (or RLC PDU) with sequence number 3 is lost (that is, it is not received by RLC Rx 3.
  • RLC Rx 3 is detected as lost).
  • RLC Rx 3 receives an inquiry from RLC Tx 2 , it will generate a first RLC status PDU, where the first ACK_SN is set to 5, the first NACK_SN is set to 3, and then the first status PDU Send to the corresponding RLC entity in the IAB node 2 (for example, RLC Tx 2 ).
  • the first ACK_SN and the first NACK_SN are indicated to the upper layer or RLC Rx 2 .
  • RLC Rx 2 receives an inquiry from RLC Tx 1 .
  • RLC Rx 2 generates a second RLC status report and sends it to the corresponding RLC entity in IAB node 1, where the first ACK_SN is set to 6, and the second ACK_AN is set to 5 (that is, the upper layer or the NACK_SN indicated by the forwarding RLC entity) , The first NACK_SN is set to 2, the other first NACK_SN is set to 6, and the second NACK_SN is set to 3.
  • the RLC entity in the IAB node 1 indicates the second ACK_SN, the first NACK_SN and the second NACK_SN whose sequence numbers are smaller than the second ACK_SN to the upper layer or RLC Rx 1 .
  • RLC Rx 1 generates a second RLC status report and sends it to the corresponding RLC entity in the UE, where the first ACK_SN is set to 8, the first NACK_SN is set to 1, and the second ACK_SN is set to 5 (that is, the upper layer or forwarding RLC entity indication ACK_SN), and the two second NACK_SNs are set to 2 and 3 respectively (that is, the second NACK_SN indicated by the upper layer or the forwarding RLC entity and the first NACK_SN that meets the condition).
  • the RLC status report contains the second NACK_SN as an example.
  • the RLC status report does not include the second NACK_SN, but uses a bitmap to describe it, then a method similar to setting the second NACK_SN can be used, and the bitmap The corresponding bit in is set to 0 or 1. For example, in the RLC status PDU generated by the RLC Rx 1 of the IAB node 1, the corresponding bits in the bitmap of the RLC PDUs with sequence numbers 2 and 3 are set to 0.
  • the second NACK_SN (or bitmap) contains the RLC SDU (or RLC PDU) or its corresponding sequence number that is detected as lost by the final destination RLC entity. Contains the RLC SDU (or RLC PDU) or its corresponding sequence number detected as lost by the RLC entity of the intermediate node.
  • the second NACK_SN (or bitmap) contains the sequence number of the RLC SUD or RLC PDU that was detected as lost by the final destination RLC entity and the sequence number of the RLC entity forwarded by it.
  • the peer entity detects that it is a lost RLC SDU or RLC PDU with a sequence number smaller than the second ACK_SN. However, considering that if the intermediate node RLC entity does not receive a certain RLC SDU (or RLC PDU), the final destination RLC entity must not receive the RLC SDU (or RLC PDU).
  • the RLC SDU (or RLC PDU) or its sequence number indicated by the second NACK_SN (or bit in the bitmap) is collectively referred to as the RLC SDU detected as missing by the final destination RLC entity Or RLC PDU) or its corresponding sequence number.
  • the AM RLC entity sender indicates the status report information (referred to as the status report indication) to the upper layer (for example, the adaptation entity) or the corresponding AM RLC entity receiver (referred to as forwarding RLC in the embodiment of this disclosure) entity).
  • the AM RLC entity receiving end that is, the forwarding RLC entity
  • the AM RLC entity sending end belong to the same IAB node, which is the AM RLC entity receiving end to which the AM RLC entity sending end is mapped, and the data from the AM RLC entity receiving end will be It is forwarded to the AM RLC entity sender, and then sent by the AM RLC entity sender to its peer RLC entity.
  • the AM RLC entity transmitter In uplink transmission, the AM RLC entity transmitter is located at the MT, and its corresponding AM RLC entity receiver is located at the DU; in downlink transmission, the AM RLC entity transmitter is located at the DU, and its corresponding AM RLC entity receiver is located at the MT.
  • the RLC Rx in the IAB node 1 in Figure 2 is the AM RLC entity receiver corresponding to the RLC Tx.
  • the AM RLC entity transmitter and its corresponding AM RLC entity receiver are referred to as forwarding RLC entities.
  • the status report indication may include the following content:
  • RLC SDU or RLC PDU confirmed to be received correctly by the peer AM RLC entity (ie, AM RLC entity receiving end).
  • the correctly received RLC SDU or RLC PDU is an RLC SDU or RLC PDU whose sequence number is less than the first ACK_SN and is not reported as missing in the status report.
  • the status report indication indicates the first ACK_SN or its corresponding RLC SDU.
  • RLC SDU or RLC PDU detected as lost by the peer AM RLC entity ie, AM RLC entity receiver.
  • the RLC SDU or RLC PDU detected as being lost is the sequence number SN being the first NACK_SN reported in the first status report or within the range determined by the first NACK_SN and the first NACK_range (that is, the first NACK_SN ⁇ SN ⁇ first NACK_SN+first NACK_range).
  • the corresponding RLC SDU is included in the status report indication.
  • the status report indication indicates the first NACK_SN and the corresponding first NACK_range (if any) or the corresponding RLC SDU.
  • the status report indication may include the following content:
  • the RLC SDU or RLC PDU that is confirmed by the remote AM RLC entity receiving end to be correctly received is the RLC SDU (or RLC PDU) whose sequence number SN is smaller than the second ACK_SN and is not detected as lost by the peer AM RLC entity and the remote AM RLC entity receiving end, and /Or any segment of the RLC SDU is not detected as lost by the peer AM RLC entity.
  • RLC SDU or RLC PDU detected as lost by the remote AM RLC entity receiving end is the RLC SDU or RLC PDU that is indicated as being detected as lost in the RLC status report.
  • the sequence number of these RLC SDU or RLC PDU is less than the first Two ACK_SN.
  • the RLC SDU or RLC PDU detected by the remote AM RLC entity as being lost includes the RLC SDU or RLC PDU with the second NACK_SN sequence number and the RLC SDU or the RLC SDU or RLC PDU detected as missing by the peer RLC entity and the sequence number is less than the first ACK_SN.
  • the RLC SDU or RLC PDU detected as being lost by the remote AM RLC entity includes an RLC SDU or RLC PDU with a sequence of the second NACK_SN and a sequence number of the first NACK_SN (the first NACK_SN).
  • One NACK_SN is smaller than the second ACK_SN) RLC SDU or RLC PDU.
  • the RLC SDU or RLC PDU detected as lost by the remote AM RLC entity is the RLC SDU of the NACK_SN corresponding to the sequence number E4 and the value 1 (or 0), and the NACK_SN is less than the first Two ACK_SN.
  • the RLC SDU or RLC PDU detected as lost by the remote AM RLC entity includes the RLC SDU (or RLC PDU) whose sequence is 0 in the bitmap and whose sequence number is less than the second ACK_SN and .
  • the status report indication includes the RLC SDU or RLC PDU detected by the remote RLC entity or the peer RLC entity as being lost and the sequence number is less than the second ACK_SN.
  • the adaptation entity sender indicates the status information to the upper layer (for example, the adaptation entity)
  • the adaptation entity receives the AM RLC entity sender (also called After the status information of the lower layer of the adaptation entity is indicated, according to the data forwarding rule, the status information indication is indicated to the forwarding RLC entity corresponding to the AM RLC entity sending end.
  • the data forwarding rule refers to a rule of which logical channel or RLC entity configured data from a logical channel or RLC entity should be forwarded to.
  • RLC Rx data of IAB node 1 in Figure 1 is configured to be forwarded to RLC Tx, then RLC Rx can be called RLC Tx forwarding RLC entity, or RLC Tx is RLC Rx forwarding RLC entity; received at RLC Tx After receiving the RLC status report from the peer RLC entity, the status report indication is indicated to the corresponding forwarding RLC entity.
  • a third ACK_SN can be defined. If the received RLC status report contains a second ACK_SN (corresponding to the second RLC status report), the value of the third ACK_SN is set to be the same as the value of the second ACK_SN, Otherwise (corresponding to the first RLC status report), the value of the third ACK_SN is set to be the same as the value of the first ACK_SN.
  • the status report information indicated to the forwarding RLC entity or upper layer may include one or more of the following:
  • the AM RLC entity sender is configured to indicate whether to forward the RLC entity or the upper layer a status report indication.
  • the configuration can be implemented through RRC messages.
  • the RLC-BearerConfig information element contained in the RRC message carries an indication identifier, which is used to indicate whether the corresponding RLC entity indicates a status report indication to the forwarding RLC entity or the upper layer.
  • the value of the indication identifier is true or 1 or the identifier appears, indicating that the corresponding RLC entity indicates the status report to the forwarding RLC entity or the upper layer, or that the corresponding RLC entity is receiving a status report from the peer RLC entity (It can be the first RLC status report or the second RLC status report), indicating the status report indication to the forwarding RLC entity or upper layer.
  • the following describes the operations that the AM RLC entity receiver in the IAB node needs to perform.
  • step 001 the AM RLC entity receiving end receives a poll or an RLC PDU containing the inquiry from the sender of the peer AM RLC entity, that is, the received RLC PDU contains the inquiry or the inquiry bit is set to 1.
  • the AM RLC entity receiver constructs an RLC status report according to the status report indication indicated by the upper layer or its corresponding forwarding RLC entity, and the RLC status report may be the first RLC status report or the second RLC status report.
  • the value of the second ACK_SN is set to the maximum sequence number of the RLC SDU or RLC PDU that is confirmed to be received correctly by the remote RLC entity.
  • the value of the second NACK_SN, the second NACK_range, or the corresponding bit in the bitmap is set according to the RLC SDU or RLC PDU that is detected as lost indicated by the forwarded RLC entity or the upper layer. For details, see other embodiments of the present invention. This will not be repeated.
  • the AM RLC entity receiving end is configured to send the second RLC status report, for example, the configuration can be implemented through an RRC message.
  • the RLC-BearerConfig information element included in the RRC message carries an indication identifier, and the indication identifier is used to indicate whether the corresponding RLC entity can construct the second RLC status report.
  • the AM RLC entity receiving end may also determine which type of status report to send according to whether there is status report information indicated by the upper layer or the forwarding RLC entity. If the M RLC entity receiving end receives the status report information indicated by the upper layer or the forwarding RLC entity, the second RLC status report is sent, otherwise, the first RLC status report is sent.
  • the AM RLC entity receiving end may also determine which type to construct according to whether the AM RLC entity is an AM RLC entity in an intermediate node (for example, IAB node 1 and IAB node 2 in Figure 1 and Figure 2) RLC status report, in which only the intermediate node will construct a second RLC status report.
  • an intermediate node for example, IAB node 1 and IAB node 2 in Figure 1 and Figure 2
  • RLC status report in which only the intermediate node will construct a second RLC status report.
  • the following describes the operations that need to be performed by the AM RLC entity transmitter in the UE.
  • step 001 the AM RLC entity transmitter receives the RLC status report from the AM RLC entity receiver. If the status report is the first status report (for example, the value of the CPT field is 000), perform at least one of the following operations:
  • the status report is the second status report (for example, the value of the CPT field is 001)
  • at least one of the following operations can be performed:
  • AM RLC If a negative confirmation of an RLC SDU or RLC SDU segment is received and the negative confirmation comes from the peer RLC entity (for example, the corresponding extension field in the status report has a value of 0, that is, the value of E4 is 0), AM RLC The entity sending end performs the following operations:
  • the positive or negative acknowledgement may come from the peer AM RLC entity or the remote AM RLC entity, If the timer t-PollRetransmit is running, stop and reset the timer.
  • POLL_SN is a query sending state variable used to store the maximum sequence number of AMD PDUs that have been submitted to the lower layer.
  • the POLL_SN is set according to section 5.3.3.2 in 3GPP TS38.322, and its initial value is 0( This state variable holds the value of the highest SN of the AMD PDU throughout the AMD PDUs submitted to lower layer when POLL_SN is set according to subclause 5.3.3.2.).
  • the timer t-PollRetransmit is used by the AM RLC entity sender to retransmit the query.
  • the value of the field (or state variable) related to the sequence number of the RLC SDU or RLC PDU in the embodiment of the present disclosure ranges from 0 to 2 sequence number length -1.
  • the value ranges from 0 to 4095
  • the length of the serial number is 18 bits
  • the value ranges from 0 to 262143.
  • the arithmetic operations of all state variables in the embodiments of the present disclosure are affected by modulus (that is, the final value is the value obtained by the arithmetic operation modulo 2 sequence number length ).
  • the RLC layer, the adaptation layer, and the MAC layer can be replaced with an RLC entity, an adaptation entity, and a MAC entity, respectively, and vice versa.
  • the identifier of the IAB donor may refer to the identifier of the DU or CU of the IAB donor, for example, the IP address of the DU or CU of the IAB donor.
  • the identifier of the IAB-node may refer to the identifier of the DU or MT of the IAB node, for example, the IP address of the DU or MT of the IAB node.
  • the adaptation entity adds an adaptation layer header to the data (such as RLC SDU) received from the UE or the local UE, and delivers the generated adaptation PDU to the corresponding data forwarding rule or destination address Adaptation entity or lower layer.
  • the data (adaptation PDU) received from other IAB nodes or their adaptation entities is delivered to the corresponding lower layer or corresponding adaptation entity according to the data forwarding rules or the destination address.
  • the data forwarding rule may be configured by the IAB donor for the IAB node, for example, configured through an RRC message.
  • the data of the adaptation layer can be referred to as adaptation SDU (which does not include the header of the adaptation layer) and adaptation PDU (which includes the header of the adaptation layer), respectively, where the adaptation PDU can also Divided into adaptation data PDU and adaptation control PDU.
  • a field (denoted as the D/C field) can be used in the header of the adaptation PDU to indicate whether the adaptation PDU is a control PDU or a data PDU. If the value of the D/C field is 0, it means that the data PDU is adapted, and if the value of the D/C field is 1, it means that the control PDU is adapted. vice versa.
  • the lower layer of the adaptation entity may be the RLC layer or the MAC layer. If there is a one-to-one mapping relationship between the DU and/or MT and the adaptation entity (that is, a DU or MT defines an adaptation entity) or there is a one-to-one mapping relationship between the adaptation entity and the RLC entity, then During data transmission, the receiving adaptation entity (or the IP layer or the entity that implements the routing function) should select the corresponding sending adaptation entity (or MT) according to the destination address or the address of the IAB-donor DU (for example, the IP address of the IAB-donor DU) Adaptation entity).
  • the AM RLC entity sender when the AM RLC entity sender receives the first RLC status report or the second RLC status report, the AM RLC entity sender can indicate the status information to the upper layer (for example, the adaptation entity), and the adaptation entity receives After the status information indication, the status information indication is indicated to the mapped adaptation entity, and then the mapped adaptation entity is indicated to the lower layer (for example, the forwarding RLC entity of the AM entity entity sending end).
  • the upper layer for example, the adaptation entity
  • the adaptation entity receives After the status information indication, the status information indication is indicated to the mapped adaptation entity, and then the mapped adaptation entity is indicated to the lower layer (for example, the forwarding RLC entity of the AM entity entity sending end).
  • the adaptation entity selects the corresponding RLC entity according to the destination address or the address of the IAB-donor DU (for example, the IP address of the IAB-donor DU).
  • the embodiments of the present disclosure are described based on the many-to-one mapping relationship between the DU and/or MT and the adaptation layer.
  • the adaptation entity (or the IP layer or the entity that implements the routing function) needs to select and send the adaptation entity according to the correspondence between the DU and/or MT and the adaptation entity when forwarding data (or indicating the status information indication).
  • the foregoing sending adaptation entity can also be used to receive data, and the receiving adaptation entity can also send data.
  • both the sending adaptation entity and the receiving adaptation entity can be called adaptation entities; or the sending adaptation entity is called For the sending end of the adaptation entity, the receiving adaptation entity is called the receiving end of the adaptation entity.
  • the routing function is integrated in the adaptation entity in the present disclosure.
  • the receiving adaptation entity sends the data to the upper layer after receiving the data that needs to be forwarded, and the upper layer sends the data according to the destination address. Route (or deliver) to the corresponding sending adaptation entity.
  • the destination address in the adaptation PDU may not be included in the adaptation PDU, for example, as the header of the IP packet included in the destination IP address.
  • the destination address can refer to the address of IAB-donor (or IAB-donor DU), such as the IP address of IAB-donor (or IAB-donor DU); for the downlink, the destination address can be Refers to the address of the IAB-nod (or IAB-node MT), such as the IP address of the IAB-nod (or IAB-node MT); for the downlink, the destination address can also be the identity of the UE, such as C-RNTI.
  • the IAB node used to receive data may be the DU of the IAB node, and the IAB donor used to receive data may be the DU of the IAB donor.
  • the IAB node used to receive data may be the MT of the IAB node.
  • the present disclosure proposes an enhanced RLC status report, which contains indication information about the reception of RLC data units by the final destination RLC entity in multi-hop transmission.
  • the RLC sending entity can learn the receiving status of the RLC SDU by the final destination RLC entity through the enhanced RLC status report, so that it can identify the situation of packet loss on the way, and realize packet loss-free transmission through retransmission.
  • end-to-end packet loss-free transmission in a multi-hop IAB network can be realized.
  • the term naming and field naming in the embodiments of the present disclosure are only examples and not limiting, and other naming (as long as they can indicate the same information) are also feasible, and therefore fall within the scope of the present disclosure.
  • the second ACK_SN, the second NACK_SN, and the second NACK_range are feedback information related to the reception status of the final destination RLC entity, so they can also be called remote ACK_SN, remote NACK_SN, and remote NACK_range. , Or other names can be used.
  • the method of the present invention is not limited to the steps shown in the foregoing embodiments, but may include more other steps.
  • the specific structure of the device of the present disclosure is not limited to the above-mentioned embodiment, but may include other components.
  • only components related to the present disclosure are shown in the communication devices of FIGS. 5 to 8 to avoid obscuring the present disclosure.
  • the communication device according to the embodiment of the present disclosure may also include other basic units constituting a user equipment or a RAN node.
  • the components having the same effects described in the above embodiments may be substituted for each other.
  • the computer-executable instructions or program running on the device according to the present invention may be a program that enables the computer to implement the functions of the embodiments of the present invention by controlling a central processing unit (CPU).
  • the program or the information processed by the program can be temporarily stored in volatile memory (such as random access memory RAM), hard disk drive (HDD), non-volatile memory (such as flash memory), or other memory systems.
  • Computer-executable instructions or programs for implementing the functions of the various embodiments of the present invention may be recorded on a computer-readable storage medium. Corresponding functions can be realized by causing the computer system to read the programs recorded on the recording medium and execute these programs.
  • the so-called “computer system” herein may be a computer system embedded in the device, and may include an operating system or hardware (such as peripheral devices).
  • the "computer-readable storage medium” may be a semiconductor recording medium, an optical recording medium, a magnetic recording medium, a recording medium storing a program dynamically for a short time, or any other recording medium readable by a computer.
  • circuits for example, single-chip or multi-chip integrated circuits.
  • Circuits designed to perform the functions described in this specification may include general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA), or other programmable logic devices, discrete Gate or transistor logic, discrete hardware components, or any combination of the above devices.
  • the general-purpose processor may be a microprocessor, or any existing processor, controller, microcontroller, or state machine.
  • the above-mentioned circuit can be a digital circuit or an analog circuit. In the case of new integrated circuit technologies that replace existing integrated circuits due to advances in semiconductor technology, one or more embodiments of the present invention can also be implemented using these new integrated circuit technologies.
  • the present invention is not limited to the above-mentioned embodiment. Although various examples of the embodiment have been described, the present invention is not limited thereto.
  • Fixed or non-mobile electronic equipment installed indoors or outdoors can be used as terminal equipment or communication equipment, such as AV equipment, kitchen equipment, cleaning equipment, air conditioners, office equipment, vending machines, and other household appliances.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本公开提供了发送RLC状态报告的方法、设备和存储介质。所述方法包括：向直接通信的RLC实体发送询问；以及，从所述RLC实体接收RLC状态报告，所述RLC状态报告包括指示RLC状态报告的类型的信息，并且至少一类RLC状态报告包含指示多跳数据传输的最终目的地RLC实体是否接收到RLC数据单元的信息。本公开实施例的方法有助于实现多跳IAB网络中的端到端无丢包传输。

Description

发送RLC状态报告的方法、设备和存储介质 技术领域
本公开涉及无线通信技术领域，更具体地，本公开涉及用于在多跳网络中发送和接收RLC状态报告的方法、设备和对应的存储介质。
背景技术
2018年9月，在第三代合作伙伴计划(3rd Generation Partnership Project：3GPP)RAN#81次全会上，高通提出了一个关于NR一体接入和回程(Integrated Access and Backhaul for NR，简称IAB)的工作项目(参见非专利文献：RP-182882：New WID：Integrated Access and Backhaul for NR)，并获批准。在RAN2#104次会议上达成在多跳的IAB网络中针对数据传输采用逐跳自动重传请求(Hop-by-Hop Automatic Repeat request，记为HbH ARQ)机制，这种数据传输也称为HbH ARQ传输(下文中也简称为多跳传输)。HbH ARQ传输的问题之一是无法保证端到端的无丢包传输(lossless delivery)。在目前的RLC ARQ中，RLC状态报告中报告的是当前一跳的RLC接收实体对RLC SDU或RLC PDU的接收情况。当RLC发送实体接收到RLC状态报告时，将成功发送的RLC SDU或RLC PDU指示给PDCP实体，PDCP实体在接收到所述指示后删除对应的PDCP PDU和PDCP SDU。在上行传输中，如果数据被接入IAB节点成功接收后，UE将删除对应的数据，随后接入IAB节点将数据转发给下一跳并删除。此时，如果中间IAB节点发生故障，则这些被UE认为已成功发送的数据将不能被IAB施主接收到。基于此，IAB工作项目提出的目标之一就是定义一种机制来确保基于HbH ARQ的无丢包传输。本公开致力于解决HbH ARQ传输中的传输丢包问题。
发明内容
为此，本公开提出了一种增强的RLC状态报告，以实现多跳IAB网络中的端到端无丢包传输。所提出的增强的RLC状态报告包含关于多 跳传输中的最终目的地RLC实体对RLC数据单元的接收情况的指示信息。由此，RLC发送实体可以通过该增强的RLC状态报告获知最终目的地RLC实体对RLC SDU的接收情况，从而可以识别出途中丢包的情形，通过重传实现无丢包传输。
根据本公开的第一方面，提供了一种在多跳传输中的发送节点处执行的方法，包括：向直接通信的RLC实体发送询问；以及，从所述RLC实体接收RLC状态报告，所述RLC状态报告包括指示RLC状态报告的类型的信息，并且至少一类RLC状态报告包含指示多跳数据传输的最终目的地RLC实体是否接收到RLC数据单元的信息。
在一些实施例中，所述发送节点可以是用户设备。在另一些实施例中，所述发送节点可以是无线接入网(RAN)节点。
在一些实施例中，所述方法还可以包括：对于收到来自最终目的地RLC实体的肯定确认的RLC数据单元，将其指示给上层。作为替代或补充，所述方法还可以包括：对于收到来自最终目的地RLC实体的否定确认的RLC数据单元，将其从重传缓存区中删除。
可选地，所述指示多跳数据传输的最终目的地RLC实体是否接收到RLC数据单元的信息可以包括下述中的至少一个：
最终目的地RLC实体正确接收的RLC数据单元的最大序列号；
最终目的地RLC实体下一个未接收到的RLC数据单元的序列号；
被最终目的地RLC实体检测为已丢失的RLC数据单元的序列号；
被最终目的地RLC实体检测为连续丢失的RLC数据单元的数目；
被最终目的地RLC实体检测为第一个丢失的RLC数据单元的序列号；以及
指示哪些RLC数据单元被最终目的地RLC实体正确接收和/或哪些RLC数据单元被最终目的地RLC实体检测为丢失的位图。
可选地，所述RLC状态报告可以包括下述字段：类型字段、远端ACK_SN字段和远端NACK_SN字段，其中，
所述类型字段包含指示RLC状态报告的类型的信息，
所述远端ACK_SN字段指示最终目的地RLC实体正确接收的RLC数据单元的最大序列号，或者指示最终目的地RLC实体下一个未接收到 的RLC数据单元的序列号，
所述远端NACK_SN字段指示被最终目的地RLC实体检测为已丢失的RLC数据单元的序列号。
可选地，所述RLC状态报告可以包括下述字段：类型字段、远端ACK_SN字段、远端NACK_SN字段和远端NACK_range字段，其中，
所述类型字段包含指示RLC状态报告的类型的信息，
所述远端ACK_SN字段指示最终目的地RLC实体正确接收的RLC数据单元的最大序列号，或者指示最终目的地RLC实体下一个未接收到的RLC数据单元的序列号，
所述远端NACK_SN字段指示被最终目的地RLC实体检测为已丢失的RLC数据单元的序列号，
所述远端NACK_range字段指示从对应的远端NACK_SN开始连续丢失的RLC数据单元的数目。
可选地，所述RLC状态报告可以包括下述字段：类型字段和远端ACK_SN字段，其中，
所述类型字段包含指示RLC状态报告的类型的信息，
所述远端ACK_SN字段指示最终目的地RLC实体正确接收的RLC数据单元的最大序列号，或者指示最终目的地RLC实体下一个未接收到的RLC数据单元的序列号。
可选地，所述RLC状态报告可以包括下述字段：类型字段、FMSN字段和Bitmap字段，其中，
所述类型字段包含指示RLC状态报告的类型的信息，
所述FMSN字段指示被最终目的地RLC实体检测为第一个丢失的RLC数据单元的序列号，
所述Bitmap字段指示在所述FMSN之后哪些RLC数据单元被最终目的地RLC实体正确接收和/或哪些RLC数据单元被最终目的地RLC实体检测为丢失的位图。
可选地，所述RLC状态报告可以包括下述字段：类型字段、第一指示字段、ACK_SN字段和NACK_SN字段，其中，
所述类型字段包含指示RLC状态报告的类型的信息，
所述第一指示字段指示所述ACK_SN字段和NACK_SN字段与最终目的RLC实体相关还是与直接通信的RLC实体相关，
所述ACK_SN字段指示正确接收的RLC数据单元的最大序列号，或者指示下一个未接收到的RLC数据单元的序列号，
所述NACK_SN字段指示被检测为已丢失的RLC数据单元的序列号。
可选地，所述RLC状态报告包括下述字段：类型字段、第一指示字段、远端ACK_SN字段和NACK_SN字段，
其中，
所述类型字段包含指示RLC状态报告的类型的信息，
所述第一指示字段指示所述NACK_SN字段与最终目的RLC实体相关还是与直接通信的RLC实体相关，
所述远端ACK_SN字段指示最终目的地RLC实体正确接收的RLC数据单元的最大序列号，或者指示最终目的地RLC实体下一个未接收到的RLC数据单元的序列号，
所述NACK_SN字段指示被检测为已丢失的RLC数据单元的序列号。
根据本公开的第二方面，提供了一种在多跳传输中的接收节点处执行的方法，包括：构造无线链路控制RLC状态报告，所述RLC状态报告包括指示RLC状态报告的类型的信息，并且至少一类RLC状态报告包含指示多跳数据传输的最终目的地RLC实体是否接收到RLC数据单元的信息；以及，发送所述RLC状态报告。
在一些实施例中，所述构造RLC状态报告是响应于接收到所述询问而执行的。在这样的实施例中，所述方法还包括：接收来自所述多跳数据传输的路径中的直接通信的RLC实体的询问。
在一些实施例中，所述接收节点可以是用户设备。在另一些实施例中，所述接收节点可以是无线接入网(RAN)节点。
根据本公开的第三方面，提供了一种第一通信设备，包括：发送模块，配置为：向直接通信的RLC实体发送询问；以及，接收模块，配置为：从所述RLC实体接收RLC状态报告，所述RLC状态报告包括指示 RLC状态报告的类型的信息，并且至少一类RLC状态报告包含指示多跳数据传输的最终目的地RLC实体是否接收到RLC数据单元的信息。所述第一通信设备可以包括：用户设备和无线接入网RAN节点。
根据本公开的第四方面，提供了一种第二通信设备，包括：处理模块，配置为：构造无线链路控制RLC状态报告，所述RLC状态报告包括指示RLC状态报告的类型的信息，并且至少一类RLC状态报告包含指示多跳数据传输的最终目的地RLC实体是否接收到RLC数据单元的信息；以及，发送模块，配置为：发送所述RLC状态报告。所述第一通信设备可以包括：用户设备和无线接入网RAN节点。
根据本公开的第三方面，提供了一种第一通信设备，包括：发送模块，配置为：向直接通信的RLC实体发送询问；以及，接收模块，配置为：从所述RLC实体接收RLC状态报告，所述RLC状态报告包括指示RLC状态报告的类型的信息，并且至少一类RLC状态报告包含指示多跳数据传输的最终目的地RLC实体是否接收到RLC数据单元的信息。所述第一通信设备可以包括：用户设备和无线接入网RAN节点。
根据本公开的第四方面，提供了一种第二通信设备，包括：处理模块，配置为：构造无线链路控制RLC状态报告，所述RLC状态报告包括指示RLC状态报告的类型的信息，并且至少一类RLC状态报告包含指示多跳数据传输的最终目的地RLC实体是否接收到RLC数据单元的信息；以及，发送模块，配置为：发送所述RLC状态报告。所述第一通信设备可以包括：用户设备和无线接入网RAN节点。
根据本公开的第五方面，提供了一种通信设备，包括：处理模块、接收模块和发送模块。其中，所述处理模块配置为：构造无线链路控制RLC状态报告，所述RLC状态报告包括指示RLC状态报告的类型的信息，并且至少一类RLC状态报告包含指示多跳数据传输的最终目的地RLC实体是否接收到RLC数据单元的信息。所述接收模块配置用于接收来自其他通信设备的查询和/或RLC状态报告。所述发送模块配置用于向其他通信设备发送RLC状态报告和/或查询。
根据本公开的第六方面，提供了一种通信设备，包括：处理器，以及，存储器，其上存储有机器可读指令，所述指令在由处理器执行时， 使得所述处理器执行根据本公开第一方面或第二方面的方法。
根据本公开的第七方面，提供了一种计算机可读存储介质，其上存储有机器可读指令，所述指令在由处理器执行时，使得所述处理器执行根据本公开第一方面或第二方面的方法。
附图说明
通过下文结合附图的详细描述，本公开的上述和其它特征将会变得更加明显，其中：
图1示出了多跳IAB网络中上行数据传输示意图。
图2示出了多跳IAB网络中下行数据传输示意图。
图3示出了根据本发明实施例的在多跳传输中的发送节点处执行的方法的流程图。
图4示出了根据本发明实施例的在多跳传输中的接收节点处执行的方法的流程图。
图5示出了根据本发明实施例的第一通信设备的示意框图。
图6示出了根据本发明实施例的第二通信设备的示意框图。
图7示出了根据本发明实施例另一实施例的通信设备的示意框图。
图8示出了根据本发明实施例又一实施例的通信设备的示意框图。
图9～图16示出了根据本发明实施例的RLC状态报告的结构示例。
图17示出了多跳IAB网络中的上行数据传输的另一示意图。
具体实施方式
下面结合附图和具体实施方式对本公开进行详细阐述。应当注意，本公开不应局限于下文所述的具体实施方式。另外，为了简便起见，省略了对与本公开没有直接关联的公知技术的详细描述，以防止对本公开的理解造成混淆。
下面描述本公开涉及的部分术语，如未特别说明，本公开涉及的术语采用此处定义。本公开给出的术语在NR、LTE和eLTE中可能采用不同的命名方式，但本公开中采用统一的命名，在应用到具体的系统中时，可以替换为相应系统中采用的命名。
PDCP：Packet Data Convergence Protocol，分组数据汇聚协议。
RLC：Radio Link Control，无线链路控制。RLC实体的传输模式可以配置为透传模式TM、非确认模式UM或确认模式AM之一。当RLC实体配置为透传模式TM、非确认模式UM或确认模式AM时，其可以分别被称为TM RLC实体、UM RLC实体或AM RLC实体。在目前的3GPP通信系统中，仅AM RLC实体支持ARQ，因此本公开的下面的实施例中，对等RLC实体都是指对等AM RLC实体；相应的，AM RLC实体发送端的对等AM RLC实体是指直接通信(即同一跳)的AM RLC实体接收端，AM RLC实体接收端的对等AM RLC实体是指直接通信(即同一跳)的AM RLC实体发送端。直接通信(即同一跳)的RLC实体发送端和RLC实体接收端互称为对等RLC实体。在本公开的下面的实施例中，除非另有说明，RLC实体指AM RLC实体。
AMD：AM data，AM数据。
图1给出了多跳IAB网络上行数据传输示意图。在图1中，RLC Tx是RLC实体发送端，RLC Rx是RLC实体接收端。本公开实施例中，直接通信的RLC实体发送端和RLC实体接收端互称为对等RLC实体。例如，在图1中，UE中的RLC Tx的对等实体是IAB节点1中的RLC Rx，反之亦然。IAB节点1中的RLC Tx的对等实体是IAB节点2中的RLC Rx，反之亦然。IAB节点2中的RLC Tx的对等实体是IAB施主中的RLC Rx，反之亦然。在本公开实施例中，位于IAB施主中的RLC Rx称为UE中的RLC Tx的远端RLC实体。相应的，IAB施主或IAB施主DU或IAB施主DU中的RLC实体接收端是上行数据传输的最终目的地。
图2给出了多跳IAB网络下行数据传输示意图。与上行数据传输的情况类似，在图2中，IAB施主中的RLC Tx的对等实体是IAB节点2中的RLC Rx。IAB节点2中的RLC Tx的对等实体是IAB节点1中的RLC Rx，反之亦然。IAB节点1中的RLC Tx的对等实体是UE中的RLC Rx，反之亦然。在本公开实施例中，位于UE中的RLC Rx称为IAB施主中的RLC Tx的远端RLC实体。相应的，UE或UE中的RLC实体接收端是下行数据传输的最终目的地。
在本公开实施例中，上一跳/下一跳是指RLC实体的对等RLC实体，即直接通信的实体，例如在上行数据传输中，IAB节点1的上一跳是用 户设备，下一跳是IAB节点2。在下行数据传输中，IAB节点1的下一跳是用户设备，上一跳是IAB节点2。
MAC：Medium Access Control，媒体访问控制。
PDU：Protocol Data Unit，协议数据单元。
SDU：Service Data Unit，服务数据单元。
在本公开实施例中，将从上层接收或发往上层的数据称为SDU，将发往下层或从下层接收的数据称为PDU。在本文中，也将PDU和SDU统称为数据单元。例如，RLC实体从上层接收的数据或发往上层的数据称为RLC SDU；RLC实体从MAC实体接收到的数据或发往MAC实体的数据称为RLC PDU。在本文中，也将RLC PDU和RLC SDU统称为RLC数据单元。在用户设备UE中，PDCP实体是RLC实体的上层。在IAB节点和IAB施主中，适配实体是RLC实体的上层。在中间IAB节点中，适配PDU是RLC SDU，因为适配实体在接收到RLC SDU后直接根据数据转发规则或UE标识或逻辑信道标识转发。在接入IAB节点中，对IAB节点对应的本地LE的RLC实体来说，适配SDU是RLC SDU。这是因为，当接入IAB节点接收到来自其他IAB节点或IAB施主的适配PDU时，适配实体移除适配PDU的头部并根据数据转发规则或UE标识或逻辑信道标识将得到的适配SDU递交给下层或RLC层，此时RLC SDU就是适配SDU。此外，当IAB节点接收到来自本地UE的RLC实体的RLC SDU时，为其增加适配头部得到适配PDU并根据数据转发规则转发。在中间IAB节点中，适配实体从RLC实体接收RLC SDU，并根据目的地址转发到另一个RLC实体，从适配层看来，所述RLC SDU就是适配PDU。因此，在本公开实施例中，将包含适配层头部(例如下行传输中来自另一IAB节点或IAB施主的RLC SDU)的RLC SDU称为适配PDU，将不包含适配层头部的RLC SDU(在上行传输中，来自本地UE的RLC SDU)称为适配SDU。
IAB节点：IAB-node，指支持用户设备的无线接入和无线回程接入流量的RAN节点(RAN node that supports wireless access to UEs and wirelessly backhauls the access traffic)。用于支持UE无线接入的IAB节点称为UE的接入IAB节点，相应的UE称为IAB节点的本地UE。
IAB施主：IAB-donor，为核心网络提供UE接口，并为IAB节点提 供无线回程功能的RAN节点(RAN node which provides UE’s interface to core network and wireless backhauling functionality to IAB-nodes)。
状态PDU：STATUS PDU。
如果在RLC层，状态PDU也可称RLC状态PDU，它包括状态PDU的负载和RLC控制PDU头部。RLC控制PDU头部可包含一个D/C字段和一个CPT字段。D/C字段指示一个RLC PDU是RLC数据PDU还是RLC控制PDU。D/C字段取值为0，表示RLC PDU是RLC控制PDU；D/C字段取值为1，表示RLC PDU是RLC数据PDU。CPT(Control PDU Type)字段指示RLC控制PDU的类型。
在本公开实施例中，将3GPP TS38.322中定义的RLC状态报告(也称为状态PDU)称为第一RLC状态报告。所述第一RLC状态报告被AM RLC实体的接收端用来通知对等AM RLC实体哪些RLC数据PDU被成功接收和哪些RLC数据PDU被AM RLC实体接收端检测为已丢失。
DRB：Data Radio Bearer carrying user plane data，承载用户面数据的数据无线承载或简称数据无线承载。
SRB：Signalling Radio Bearer，信令无线承载。
CU：Central Unit，中心单元或记为gNB-CU。一个CU具有(hosting)或至少具有基站的RRC、SDAP和PDCP协议或者en-gNB的RRC和PDCP协议，并控制一个或多个DU或gNB-DU。gNB-CU终止与gNB-DU连接的F1接口。CU又可分为CU-CP(或记为gNB-CU-CP)和CU-UP(或记为gNB-CU-UP)。CU-CP是一个逻辑节点，承载RRC和gNB-CU的PDCP协议的控制面部分，用于en-gNB或gNB。gNB-CU-CP终止与gNB-CU-UP连接的E1接口和与gNB-DU连接的F1-C接口。CU-UP是一个逻辑节点，用于承载en-gNB的gNB-CU的PDCP协议的用户面部分，以及gNB-CU的PDCP协议的用户面部分和gNB-CU的SDAP协议。gNB-CU-UP终止与gNB-CU-CP连接的E1接口和与gNB-DU连接的F1-U接口。
DU：Distributed Unit，分布式单元。DU是具有或至少具有RLC、MAC和物理层的逻辑节点。DU可以位于IAB节点或IAB施主中。在IAB节点或IAB施主中，DU还可以具有适配层。
MT：Mobile-Termination，移动终端。MT是IAB节点中用于终止 与IAB施主或其他IAB节点的回程Uu接口的无线接口层(MT is referred to as a function residing on an IAB-node that terminates the radio interface layers of the backhaul Uu interface toward the IAB-donor or other IAB-nodes)。
每个IAB节点通过MT连接到上行IAB节点或IAB施主，并通过DU与UE或下行IAB节点的MT建立RLC通道。IAB施主通过DU来支持UE和下行IAB节点的MT。换言之，在上行传输中，IAB节点的AM RLC实体发送端位于MT，IAB节点的AM RLC实体接收端位于DU；在下行传输中，IAB节点的AM RLC实体发送端位于DU，IAB节点的AM RLC实体的接收端位于MT。
RLC-BearerConfig信元：所述信元用于配置RLC实体、MAC中对应的逻辑信道、以及与PDCP实体(服务的承载)的关联(used to configure an RLC entity，a corresponding logical channel in MAC and the linking to a PDCP entity(served radio bearer))。
下面结合附图对本公开实施例的方案进行详细描述。
图3示出了根据本发明实施例的在多跳传输中的发送节点处执行的方法100的流程图。
在本实施例中，该发送节点可以指多跳传输中的源节点或者任一中间节点，其可以是用户设备，也可以是RAN节点。对于上行数据传输，以图1为例，该发送节点可以是UE或者IAB节点1或者IAB节点2。对于下行数据传输，以图2为例，该发送节点可以是IAB施主或者IAB节点2或者IAB节点1。
具体地，方法100可以由发送节点的AM RLC实体来执行。
如图3所示，在步骤S110中：向直接通信的RLC实体(即对等RLC实体，或称下一跳RLC实体)发送询问或者包含询问的RLC PDU。
在步骤S120中，从所述对等RLC实体接收RLC状态报告，所述RLC状态报告包括指示RLC状态报告的类型的信息，并且至少一类RLC状态报告包含指示多跳数据传输的最终目的地RLC实体是否接收到RLC数据单元的信息。
所述RLC状态报告的类型至少分为两类。
第一类是前述3GPP TS38.322中定义的RLC状态报告(称为第一RLC状态报告)。第一RLC状态报告指示哪些RLC数据单元(RCL SDU或RLC PDU)被对等AM RLC实体成功接收和哪些RLC数据单元被对等AM RLC实体检测为已丢失。也即，第一RLC状态报告中的反馈信息与对等RLC实体的接收情况相关。
第二类是本公开提出的增强的RLC状态报告(在下文中也称为第二RLC状态报告)。第二RLC状态报告包含指示多跳数据传输的最终目的地RLC实体是否接收到RLC数据单元的信息。也即，该增强的RLC状态报告中包含与最终目的地RLC实体的接收情况相关的反馈信息。优选地，该增强的RLC状态报告也可以包含与对等RLC实体的接收情况相关的反馈信息，如现有的第一RLC状态报告中规定的全部或部分信息。
所述指示多跳数据传输的最终目的地RLC实体是否接收到RLC数据单元的信息可以包括下述中的至少一个：
最终目的地RLC实体正确接收的RLC数据单元的最大序列号；
最终目的地RLC实体下一个未接收到的RLC数据单元的序列号；所述RLC数据单元的序列号未包含在RLC状态报告中所包含的被最终目的地RLC实体检测为已丢失的RLC数据单元的序列号中。
被最终目的地RLC实体检测为已丢失的RLC数据单元的序列号；
被最终目的地RLC实体检测为连续丢失的RLC数据单元的数目；
被最终目的地RLC实体检测为第一个丢失的RLC数据单元的序列号；以及
指示哪些RLC数据单元被最终目的地RLC实体正确接收和/或哪些RLC数据单元被最终目的地RLC实体检测为丢失的位图。
所述指示多跳数据传输的最终目的地RLC实体是否接收到RLC数据单元的信息可以通过第二RLC状态报告中的一个或多个字段来指示。出于示例说明的目的，而非限制，下面示出第二RLC报告的若干可选示例。
在第一示例中，第二RLC状态报告包括下述字段：类型字段、远端ACK_SN字段和远端NACK_SN字段，其中，
所述类型字段包含指示RLC状态报告的类型的信息，
所述远端ACK_SN字段指示最终目的地RLC实体正确接收的RLC数据单元的最大序列号，或者指示最终目的地RLC实体下一个未接收到的RLC数据单元的序列号，所述RLC数据单元的序列号未包含在RLC状态报告中所包含的被最终目的地RLC实体检测为已丢失的RLC数据单元的序列号中，
所述远端NACK_SN字段指示被最终目的地RLC实体检测为已丢失的RLC数据单元的序列号。
在第二示例中，第二RLC状态报告可以包括下述字段：类型字段、远端ACK_SN字段、远端NACK_SN字段和远端NACK_range字段，其中，
所述类型字段包含指示RLC状态报告的类型的信息，
所述远端ACK_SN字段指示最终目的地RLC实体正确接收的RLC数据单元的最大序列号，或者指示最终目的地RLC实体下一个未接收到的RLC数据单元的序列号(所述RLC数据单元的序列号未包含在RLC状态报告中所包含的被最终目的地RLC实体检测为已丢失的RLC数据单元的序列号中)，
所述远端NACK_SN字段指示被最终目的地RLC实体检测为已丢失的RLC数据单元的序列号，
所述远端NACK_range字段指示从对应的远端NACK_SN开始连续丢失的RLC数据单元的数目。
在第三示例中，第二RLC状态报告可以包括下述字段：类型字段和远端ACK_SN字段，其中，
所述类型字段包含指示RLC状态报告的类型的信息，
所述远端ACK_SN字段指示最终目的地RLC实体正确接收的RLC数据单元的最大序列号，或者指示最终目的地RLC实体下一个未接收到的RLC数据单元的序列号。
在第四示例中，第二RLC状态报告可以包括下述字段：类型字段、FMSN字段和Bitmap字段，其中，
所述类型字段包含指示RLC状态报告的类型的信息，
所述FMSN字段指示被最终目的地RLC实体检测为第一个丢失的RLC数据单元的序列号，
所述Bitmap字段指示在所述FMSN之后哪些RLC数据单元被最终目的地RLC实体正确接收和/或哪些RLC数据单元被最终目的地RLC实体检测为丢失的位图。
在第五示例中，第二RLC状态报告可以包括下述字段：类型字段、第一指示字段、ACK_SN字段和NACK_SN字段，其中，
所述类型字段包含指示RLC状态报告的类型的信息，
所述第一指示字段指示所述ACK_SN字段和NACK_SN字段与最终目的RLC实体相关还是与直接通信的RLC实体相关，
所述ACK_SN字段指示正确接收的RLC数据单元的最大序列号，或者指示下一个未接收到的RLC数据单元的序列号，
所述NACK_SN字段指示被检测为已丢失的RLC数据单元的序列号。
在第六示例中，第二RLC状态报告可以包括下述字段：类型字段、第一指示字段、远端ACK_SN字段和NACK_SN字段，其中，
所述类型字段包含指示RLC状态报告的类型的信息，
所述第一指示字段指示所述NACK_SN字段与最终目的RLC实体相关还是与直接通信的RLC实体相关，
所述远端ACK_SN字段指示最终目的地RLC实体正确接收的RLC数据单元的最大序列号，或者指示最终目的地RLC实体下一个未接收到的RLC数据单元的序列号，
所述NACK_SN字段指示被检测为已丢失的RLC数据单元的序列号。
如前所述，优选地，第二RLC状态报告在包含与最终目的地RLC实体的接收情况相关的反馈信息之外，还可以包含与对等RLC实体的接收情况相关的反馈信息，如现有的第一RLC状态报告中规定的全部或部分信息。如此，可以容易地分别通过在上述示例中加入现有的第一RLC状态报告中的若干的字段而得第二RLC状态的报告的变形示例。在这种变形示例中，该类型字段可以是新字段，或者可以重用现有的字段(如CPT字段)。这将在下文详细描述。
在一些实施例中，方法100还可以包括对接收的RLC状态报告的处理。例如方法100可以包括：解析接收到的RLC状态报告以获得针对RLC数据单元的肯定确认ACK和/或否定确认NACK。可选地，方法100还可以包括：对于收到来自最终目的地RLC实体的肯定确认的RLC数据单元，将其指示给上层。作为替代或补充，方法100还可以包括：对于收到来自最终目的地RLC实体的否定确认的RLC协议数据单元和/或RLC服务数据单元，将其从重传缓存区中删除。
通过方法100，接收节点(具体地，它的RLC发送实体)可以通过接收的第二RLC状态报告获知最终目的地RLC实体对RLC SDU的接收情况，从而可以识别出途中丢包的情形，通过重传实现无丢包传输。
图4示出了根据本发明实施例的在多跳传输中的接收节点处执行的方法200的流程图。
在本实施例中，该接收节点可以指多跳传输中的最终目的地节点或者任一中间节点，其可以是用户设备，也可以是RAN节点。对于下行数据传输，以图2为例，该接收节点可以是UE或者IAB节点1或者IAB节点2。对于上行数据传输，以图1为例，该接收节点可以是IAB施主或者IAB节点2或者IAB节点1。
具体地，方法200可以由接收节点的AM RLC实体来执行。
如图4所示，在步骤S210中：构造无线链路控制RLC状态报告，所述RLC状态报告包括指示RLC状态报告的类型的信息，并且至少一类RLC状态报告包含指示多跳数据传输的最终目的地RLC实体是否接收到RLC数据单元的信息。
在步骤S220中，发送所构造的RLC状态报告。换言之，将所构造的RLC状态报告递交给下层。
在一些实施例中，步骤S210是响应于接收到询问而执行的。在这样的实施例中，在步骤S210之前，方法200还包括：接收来自多跳数据传输的路径中的直接通信的RLC实体(即前一跳RLC实体)的询问。该询问用于RLC实体发送端请求其对等RLC实体发送一个状态报告。
如前所述，所述RLC状态报告的类型至少分为两类。第一类是前述3GPP TS38.322中定义的RLC状态报告(称为第一RLC状态报告)。第二类是本公开提出的增强的RLC状态报告(在下文中也称为第二RLC状态报告)。关于这两类RLC状态报告已经参考图3进行了详细描述，在此不再赘述。
图5示出了根据本发明实施例的第一通信设备10的示意框图。如图所示，第一通信设备10可以包括发送模块12和接收模块14。
发送模块12可以配置为向直接通信的RLC实体发送询问。
接收模块14可以配置为从所述RLC实体接收RLC状态报告，所述RLC状态报告包括指示RLC状态报告的类型的信息，并且至少一类RLC状态报告包含指示多跳数据传输的最终目的地RLC实体是否接收到RLC数据单元的信息。所述第一通信设备可以包括：用户设备和无线接入网RAN节点。
可选地，第一通信设备10还可以包括处理模块和/或存储单元等。
第一通信设备10可以是执行参考图3描述的方法100的发送节点，其中发送模块12和接收模块14可以分别执行步骤S110和S120。同样，第一通信设备10可以是用户设备，也可以是RAN节点。
关于第一通信设备10的具体操作可以参见上文关于方法的描述，在此不再赘述。
图6示出了根据本发明实施例的第二通信设备20的示意框图。如图所示，第二通信设备20可以包括处理模块22和发送模块24。
处理模块22可以配置为：构造无线链路控制RLC状态报告，所述RLC状态报告包括指示RLC状态报告的类型的信息，并且至少一类RLC状态报告包含指示多跳数据传输的最终目的地RLC实体是否接收到RLC数据单元的信息。
发送模块24可以配置为发送所构造的RLC状态报告。
可选地，第二通信设备20还可以包括接收模块。该接收模块可以配置为接收来自多跳数据传输的路径中的直接通信的RLC实体的询问。
可选地，第二通信设备20还可以包括存储单元等。
第二通信设备20可以是执行参考图4描述的方法200的接收节点，其中处理模块22和发送模块24可以分别执行步骤S210和S220。
同样，第二通信设备20可以是用户设备，也可以是RAN节点。
关于第二通信设备20的具体操作可以参见上文关于方法的描述，在此不再赘述。
图7示出了根据本发明实施例另一实施例的通信设备30的示意框图。如图所示，通信设备30可以包括发送模块32、接收模块34和处理模块36。
处理模块36可以配置为：构造无线链路控制RLC状态报告，所述RLC状态报告包括指示RLC状态报告的类型的信息，并且至少一类RLC状态报告包含指示多跳数据传输的最终目的地RLC实体是否接收到RLC数据单元的信息。
发送模块32可以配置用于向其他通信设备发送RLC状态报告和/或查询。
接收模块34可以配置用于接收来自其他通信设备的查询和/或RLC状态报告。
通信设备30在操作为发送节点时可以执行方法100，在操作为接收节点时可以执行方法200。关于通信设备30的具体操作可以参见上文关于方法的描述，在此不再赘述。
图8示出了根据本发明实施例又一实施例的通信设备40的示意框图。如图所示，通信设备40可以包括收发机42、处理器44和存储器46。
通信设备40可以是上述第一通信设备10、第二通信设备20或通信设备30的具体实现示例。处理器46可以存储处理器44可执行的指令，使得通信设备40执行以上结合图3和/或图4描述的方法100和/或200。
关于通信设备40的具体操作可以参见上文关于方法的描述，在此不再赘述。
本公开实施例中所述RLC数据单元可以是RLC_SDU或RLC_PDU。通常，包含在状态报告指示中用于指示给上层或转发RLC实体的RLC数据单元是RLC_SDU，而RLC状态报告中包含的是RLC_PDU的肯定或否定确认。
本公开上面提到的远端ACK_SN、远端NACK_SN和远端NACK_range字段分别与下面实施例中的第二ACK_SN、第二NACK_SN和第二NACK_range字段表示的含义相同。
下面以IAB节点和用户设备为例对本公开的方案作进一步的详细描述。
下面描述IAB节点中AM RLC实体发送端需要执行的操作。
在步骤001中，AM RLC实体发送端接收到来自对等实体(例如，用户设备或其他IAB节点或IAB施主的AM RLC实体接收端)的RLC状态报告(也可称为状态PDU)。所述RLC状态报告是第一RLC状态报告或是第二RLC状态报告。
具体地，所述状态报告可以包括以下一个或多个字段：CPT、RLC状态报告类型、第一ACK_SN、第二ACK_SN、第一NACK_SN、SOstart、SOend、E1、E2、E3、E4、第一NACK_range、第二NACK_SN、第二NACK_range。可选地，所述状态报告还可以包括其他扩展字段E5、E6等等。其中：CPT表示RLC控制PDU的类型；RLC状态报告类型用于指示接收到的状态报告的类型，RLC状态PDU中其他字段与状态报告类型相关，可以设置RLC状态报告类型字段取值为0或1。
需要说明的是，在本公开实施例中，也可以通过设置CPT的不同取值表示不同类型的RLC状态报告。此时，在第一RLC状态PDU和/或第二RLC状态PDU中不包括RLC状态报告类型字段。表1给出了通过设置CPT的不同取值表示不同的RLC状态报告。表1中，状态PDU是第一状态PDU，增强的状态PDU是第二状态PDU，在本公开实施例中也可以将第一状态PDU称为状态PDU，第二状态PDU称为增强的状态PDU。另外，状态PDU也称为状态报告，在本公开实施例中可替换使用。可以预定义，本公开实施例中所述第一RLC状态报告是3GPP标准文献TS38.322中定义的RLC状态报告，即当CPT取值为000时是第一RLC 状态报告，当CPT取值为001或100(也可以是其他值)时是第二RLC状态报告。
表1CPT字段解释
Figure PCTCN2020074208-appb-000001
在本公开实施例中，如未特别说明，第一ACK_SN、第一NACK_SN、SOstart、SOend、E1、E2、E3、第一NACK_range与3GPP TS38.322中定义的ACK_SN、NACK_SN、SOstart、SOend、E1、E2、E3、NACK_range相同，是第一状态PDU中可包含的字段。具体地，第一ACK_SN用于指示下一个未接收到的RLC SDU(或RLC PDU)的序列号且所述RLC SDU(或RLC PDU)未在状态PDU中报告为未收到的RLC SDU(或RLC PDU)，所述未接收到的RLC SDU(或PDU)可由第一NACK_SN和/或第一NACK_range和/或SOstart和/或SOend指示(需要说明的是，在多跳IAB网络中，所述第一ACK_SN是指未被对等AM RLC实体接收端正确接收的RLC SDU的序列号)。AM RLC实体发送端在接收到所述状态报告时，它认为所有序列号小于ACK_SN的RLC SDU(或RLC PDU)都已被其对等实体或对等AM RLC实体接收，但以下除外：序列号为状态PDU的中指示NACK_SN的RLC SDU(或RLC PDU)、由状态PDU用NACK_SN，SOstart和SOend指示的RLC SDU的一部分、由状态PDU用NACK_SN和NACK_range指示的RLC SDU、由状态PDU用NACK_SN、NACK_range、SOstart和SOend指示的RLC SDU的一部分。第一NACK_SN用于指示被AM RLC实体接收端检测为未接收到或已丢失的RLC SDU的序列号。E1、E2、E3和E4字段是扩展比特字段。E1用于指示随后是否有NACK_SN、E1、E2、E3和/或E4的集合(本公开中所述随后是否有某个集合是指在对应的PDU中在所述扩展比特之后是否包含对应的集合)。E1字段取值为0表示随后没有NACK_SN、E1、E2、E3和/或E4的集合，E1字段取值为1表示随后有NACK_SN、 E1、E2、E3和/或E4的集合。反之亦然。E2用于指示随后是否有SOstart和SOend的集合，E2取值为0表示没有，E2取值为1表示有，反之亦然。E3用于指示是否包含尚未收到的连续RLC SDU的信息，E3取值为0表示对应的NACK_SN后面不包含NACK_range字段，E3取值为1表示对应的NACK_SN后面包含NACK_range字段。SOstart字段用于指示序列号SN＝NACK_SN的RLC SDU中被AM RLC实体检查为丢失的部分。更进一步，SOstart字段指示所述丢失部分的第一字节在原RLC SDU中的位置。SOend字段用于指示所述丢失部分的最后一字节在原RLC SDU中的位置(the SOend field indicates the position of the last byte of the portion of the RLC SDU in bytes within the original RLC SDU)。第一NACK_range字段用于指示从第一NACK_SN开始连续丢失的RLC SDU数。
以下描述本公开实施例中所述的第二RLC状态报告实施例。
在一个实施例中，第二RLC状态报告中可以包括以下一个或多个字段：CPT字段、第一ACK_SN、第一NACK_SN、SOstart、SOend、E1、E2、E3、第一NACK_range、第二ACK_SN、第二NACK_SN、E4。其中，第二ACK_SN指示已被最终目的地AM RLC实体接收端确认正确接收的RLC SDU的最大序列号或者被最终目的地AM RLC实体接收端指示下一个未接收到的RLC SDU(或RLC PDU)的序列号且所述RLC SDU(或RLC PDU)未在状态PDU中报告为未收到的RLC SDU(或RLC PDU)，所述未接收到的RLC SDU(或PDU)可由第二NACK_SN和/或第二NACK_range指示。第二NACK_SN字段指示被最终目的地的AM RLC实体接收端检测为已丢失的RLC SDU的序列号。E4用于指示随后是否有第二NACK_SN、E4集合。如果E4取值为0，表示随后没有NACK_SN、E4集合；如果E4取值为1，表示随后有第二NACK_SN、E4集合。图9示出了序列号长度为12比特时这种第二RLC状态报告的一个示例格式。
可选地，第二RLC状态报告还可以包含E5扩展字段，用于指示在该第二状态状态报告中是否包含NACK_SN、E4集合。如果E5取值为0，表示第二RLC状态报告中不包含NACK_SN、E4集合；如果E5取 值为1，表示第二RLC状态报告中包含第二NACK_SN、E4集合。图10示出了序列号长度为12比特时这种第二RLC状态报告的一个示例格式。
在另一个实施例中，第二RLC状态报告中可以包括以下一个或多个字段：CPT字段、第一ACK_SN、第一NACK_SN、SOstart、SOend、E1、E2、E3、第一NACK_range、第二ACK_SN、第二NACK_SN、第二NACK_range、E4、E5。其中，第二ACK_SN指示已被最终目的地AM RLC实体接收端确认正确接收的RLC SDU的最大序列号或者被最终目的地AM RLC实体接收端指示下一个未接收到的RLC SDU(或RLC PDU)的序列号且所述RLC SDU(或RLC PDU)未在状态PDU中报告为未收到的RLC SDU(或RLC PDU)，所述未接收到的RLC SDU(或RLC PDU)可由第二NACK_SN和/或第二NACK_range指示。第二NACK_SN字段指示被最终目的地的AM RLC实体接收端检测为已丢失的RLC SDU的序列号。第二NACK_range字段用于指示从对应的第二NACK_SN开始连续丢失的RLC SDU数。序列号SN小于第二NACK_SN+第二NACK_range(即第二NACK_SN和第二NACK_range的和)的RLC SDU均被AM RLC接收端检测为已丢失。换言之，序列号SN满足第二NACK_SN≤SN≤第二NACK_SN+第二NACK_range-1的RLC SDU被AM RLC实体接收端检测为已丢失。E4用于指示随后是否有第二NACK_SN、E4、E5集合。如果E4取值为0，表示随后没有第二NACK_SN、E4、E5集合；如果E4取值为1，表示随后有第二NACK_SN、E4、E5集合。E5用于指示是否包含尚未接收到的连续RLC SDU的信息，E5取值为0表示对应的第二NACK_SN后面不包含第二NACK_range字段，E5取值为1表示对应的第二NACK_SN后面包含第二NACK_range字段。反之亦然。图11示出了序列号长度为12比特时这种第二RLC状态报告的一个示例格式。
需要说明的是，E5也可以用E3代替，相应的第二NACK rang字段也可以用第一NACK_rang字段代替。
可选地，第二RLC状态报告还包含E6扩展字段，用于指示在第二 状态状态报告中是否包含NACK_SN、E4、E5集合。如果E6取值为0，表示第二状态状态报告中不包含第二NACK_SN、E4、E5集合；如果E4取值为1，表示第二状态状态报告中包含第二NACK_SN、E4、E5集合。图12示出了序列号长度为12比特时这种情况下的第二RLC状态报告的一个示例格式。
在另一个实施例中，第二RLC状态报告中可以包括以下一个或多个字段：CPT字段、第一ACK_SN、第一NACK_SN、SOstart、SOend、E1、E2、E3、第一NACK_range、第二ACK_SN。其中，第二ACK_SN指示已被最终目的地或远端AM RLC实体接收端确认正确接收的RLC SDU的最大序列号或者被最终目的地(或远端AM RLC实体接收端)指示下一个未接收到的RLC SDU(或RLC PDU)的序列号。所有序列号小于(或者小于或等于)第二ACK_SN的RLC SDU(或RLC PDU)都被最终目的地(或远端RLC实体)确认正确接收。图13示出了序列号长度为12比特时这种情况下的第二RLC状态报告的一个示例格式。
在另一个实施例中，第二RLC状态报告可以包括以下一个或多个字段：CPT字段、第一ACK_SN、第一NACK_SN、第一NACK_range、FMSN、SOstart、SOend、E1、E2、E3、E4、Bitmap、位图长度、第二ACK_SN。FMSN字段用于指示发送窗(或接收窗)内第一个被远端RLC实体确认为丢失的RLC SDU或PDU的序列号。扩展字段E4用于指示随后是否有位图或者指示状态报告中是否包含位图。位图Bitmap用于指示，哪个或哪些RLC SDU(或PDU)被远端AM RLC实体接收端正确接收或检测为丢失。位图中各位取值为0或1表示的意义如下表2-1所示，取值为0表示对应的RLC SDU丢失，取值为1表示对应的RLC SDU被正确接收，反之亦然。其中，位图第一位在位图中的位置(bit position)是1，序列号长度是指RLC SDU或PDU的序列号SN所占的比特数。图14示出了序列号长度为12比特时这种情况下的第二RLC状态报告的一个示例格式。位图长度字段用于指示位图Bitmap所占的比特数。对等RLC实体接收到所述RLC状态报告时，认为发送窗内所有序列号小于 或等于FMSN+位图长度且位图中取值为1的RLC SDU被远端RLC实体正确接收。另外，被远端RLC实体确认正确接收的RLC SDU的最大序列号或PDU或下一个未正确接收的RLC SDU的序列号为FMSN+位图长度+1。换言之，最终目的地RLC实体下一个未接收到的RLC数据单元的序列号为FMSN+位图长度+1。第二ACK_SN指示已被最终目的地AM RLC实体接收端确认正确接收的RLC SDU的最大序列号或者被最终目的地AM RLC实体接收端指示为下一个未接收到的RLC SDU(或RLC PDU)的序列号且所述RLC SDU(或RLC PDU)未在状态PDU中报告为未收到的RLC SDU(或RLC PDU)，所述未接收到的RLC SDU(或RLC PDU)可由位图中对应位取值为0。如果如果状态报告中包含第二ACK_SN字段，则可以不包含FMSN字段。此时位图中位取值的解释如表2-2所示或表2-3所示。
表2-1 位图中的位取值的解释
位 解释
0 序列号SN＝(FMCSN+位图中的位置)模2 序列号长度的RLC SDU丢失
1 序列号SN＝(FMCSN+位图中的位置)模2 序列号长度的RLC SDU被正确接收
表2-2 位图中的位取值的解释
位 解释
0 序列号SN＝(第二ACK_SN-位图中的位置)模2 序列号长度的RLC SDU丢失
1 序列号SN＝(第二ACK_SN-位图中的位置)模2 序列号长度的RLC SDU被正确接收
表2-3 位图中的位取值的解释
Figure PCTCN2020074208-appb-000002
在另一个实施例中，第二RLC状态报告包括以下一个或多个字段：CPT字段、ACK_SN、NACK_SN、SOstart、SOend、E1、E2、E3、E4、第一NACK_range。E1字段指示随后是否有NACK_SN、E1、E2、E3和/或E4的集合；如果E1字段取值为0，表示随后没有NACK_SN、E1、E2、E3和/或E4的集合；如果E1字段取值为1，表示随后有NACK_SN、E1、E2、E3和/或E4的集合；反之亦然。换言之，当CPT字段取值为 第一状态报告对应的值(例如000)，E1字段指示随后是否有NACK_SN、E1、E2和E3的集合(具体如表3所示)；当CPT字段取值为第二状态报告对应的值(例如001或100)，E1字段指示随后是否有NACK_SN、E1、E2、E3和E4的集合(具体如表4所示)。E4字段指示ACK_SN、NACK_SN字段、SOstart、SOend和NACK_range字段与最终目的RLC实体相关还是与直接通信的RLC实体相关。具体地，E4字段指示序列号为对应NACK_SN的RLC SDU是下一跳节点(或对等RLC实体，即AM RLC实体接收端)检测为已丢失还是最终目的地(例如IAB施主DU中的AM RLC实体接收端)检测为已丢失，或者序列号为对应的NACK_SN以及序列号SN满足NACK_SN＜＝SN＜＝NACK_SN+NACK_range-1的RLC SDU是下一跳节点(或对等RLC实体，即AM RLC实体接收端)检测为已丢失还是最终目的地(例如IAB施主DU中的AM RLC实体接收端)检测为已丢失(具体如表5所示)。如果E4取值为0表示对应NACK_SN的RLC SDU是下一跳节点(或对等RLC实体，即AM RLC实体接收端)检测为已丢失，或者序列号为对应的NACK_SN以及序列号SN满足NACK_SN＜＝SN＜＝NACK_SN+NACK_range-1的RLC SDU或其分段(根据SOstart、SOend确定)是下一跳节点检测为已丢失；如果E4取值为1表示对应NACK_SN的RLC SDU是最终目的地(例如IAB施主DU中的AM RLC实体接收端)检测为已丢失，或者序列号为对应的NACK_SN以及序列号SN满足NACK_SN＜＝SN＜＝NACK_SN+NACK_range-1的RLC SDU是远端RLC实体或最终目的地(例如IAB施主DU中的AM RLC实体接收端)检测为已丢失；反之亦然。其中，符号“＜＝”表示小于或等于。图15示出了这种情况下的第二RLC状态报告的一个示例格式。
表3 当CPT＝000(对应第一RLC状态PDU)时，E1取值的意义
Figure PCTCN2020074208-appb-000003
表4 当CPT＝001或100(对应第二RLC状态PDU)时，E1取值的意义
Figure PCTCN2020074208-appb-000004
表5E4取值的意义
Figure PCTCN2020074208-appb-000005
在另一个实施例中，第二RLC状态报告可以包括以下一个或多个字段：CPT字段、第一ACK_SN、第二ACK_SN、NACK_SN、SOstart、SOend、E1、E2、E3、E4、NACK_range。其中，第二ACK_SN指示已被最终目的地AM RLC实体接收端确认正确接收的RLC SDU的最大序列号或者被最终目的地AM RLC实体接收端指示下一个未接收到的RLC SDU(或RLC PDU)的序列号且所述RLC SDU(或RLC PDU)未在状态PDU中报告为未收到的RLC SDU(或RLC PDU)，所述未接收到的RLC SDU(或RLC PDU)可由E4取值为1对应的NACK_SN和/或NACK_range指示。可选的，所述未接收到的RLC SDU(或RLC PDU)还可由E4取值为0对应的NACK_SN和/或NACK_range指示。E1字段指示随后是否有NACK_SN、E1、E2、E3和/或E4的集合；如果E1字段取值为0，表示随后没有NACK_SN、E1、E2、E3和/或E4的集合；如果E1字段取值为1，表示随后有NACK_SN、E1、E2、E3和/或E4的集合；反之亦然。换言之，当CPT字段取值为第一状态报告对应的值 (例如000)，E1字段指示随后是否有NACK_SN、E1、E2和E3的集合(例如如上面表3所示)；当CPT字段取值为第二状态报告对应的值(例如001或100)，E1字段指示随后是否有NACK_SN、E1、E2、E3和E4的集合(例如如上面表4所示)。E4字段指示NACK_SN、SOstart、SOend和NACK_range字段与最终目的RLC实体相关还是与直接通信的RLC实体相关。具体地，E4字段指示序列号为对应NACK_SN的RLC SDU是下一跳节点(或对等RLC实体，即AM RLC实体接收端)检测为已丢失还是最终目的地(例如IAB施主DU中的AM RLC实体接收端)检测为已丢失，或者序列号为对应的NACK_SN以及序列号SN满足NACK_SN＜＝SN＜＝NACK_SN+NACK_range-1的RLC SDU是下一跳节点(或对等RLC实体，即AM RLC实体接收端)检测为已丢失还是最终目的地(例如IAB施主DU中的AM RLC实体接收端)检测为已丢失(例如如上面表5所示)。如果E4取值为0表示对应NACK_SN的RLC SDU是下一跳节点(或对等RLC实体，即AM RLC实体接收端)检测为已丢失，或者序列号为对应的NACK_SN以及序列号SN满足NACK_SN＜＝SN＜＝NACK_SN+NACK_range-1的RLC SDU或其分段(根据SOstart、SOend确定)是下一跳节点检测为已丢失；如果E4取值为1表示对应NACK_SN的RLC SDU是最终目的地(例如IAB施主DU中的AM RLC实体接收端)检测为已丢失，或者序列号为对应的NACK_SN以及序列号SN满足NACK_SN＜＝SN＜＝NACK_SN+NACK_range-1的RLC SDU是远端RLC实体或最终目的地(例如IAB施主DU中的AM RLC实体接收端)检测为已丢失；反之亦然。其中，符号“＜＝”表示小于或等于。图16示出了序列号长度为12比特时这种情况下的第二RLC状态报告的一个示例格式。
在本公开实施例中，最终目的地也可称为RAN目的地或远端AM RLC实体接收端或最后一跳，是RLC SDU或PDU最终要发送到的目的地，所述目的地是RAN中最后一跳。例如IAB施主DU或者UE或者IAB施主DU中的RLC实体接收端或者UE中的RLC实体接收端。下一跳也可称为对等RLC实体。
需要说明的是，将本公开实施例中第二ACK_SN的描述替换为以下描述得到的实施例也落在本公开的范围内：第二ACK_SN用于指示下一个未被上层或适配层或最终目的地或远端RLC实体接收端确认(或指示)为接收到的RLC SDU(或RLC PDU)的序列号，或者第二ACK_SN用于指示已被上层或适配层或最终目的地或远端RLC实体接收端确认(或指示)已成功接收的RLC SDU或RLC PDU的最大序列号。将本公开实施例中第二NACK_SN的描述替换为以下描述得到的实施例也落在本公开的范围内：第二NACK_SN字段指示被最终目的地或远端AM RLC实体接收端或上层或适配层或AM RLC实体接收所映射到的处于同一节点或用户设备的AM RLC实体发送端检测为已丢失的RLC SDU的序列号。
下面以图17为例说明上述替换实施例。图17给出了上行数据传输的示意图。需要说明的是，为了便于描述，在图17示出的示例中，IAB节点1和IAB节点2在转发RLC SDU的序列号时没有改变其序列号，但在基于逐跳ARQ的多跳IAB网络中，RLC SDU在不同节点间发送时序列号可能不同。这时，IAB节点中将保存接收到的RLC SDU或RLC PDU的序列号和在转发所述RLC SDU或RLC PDU时为其分配的序列号之间的映射关系。同样地，在接收到RLC状态报告时，也是基于所述映射关系来向对应的转发RLC实体指示或向上层指示相关的状态报告信息(即哪些RLC SDU被远端RLC实体确认正确接收，哪些RLC SDU被远端RLC实体检测为丢失)。在图17中，RLC Rx 1接收到来自RLC Tx ue的序列号SN为0，2～7的RLC SDU(或RLC PDU)，但序列号为1的RLC SDU(或RLC PDU)未接收到(或检测为已丢失)。RLC Tx 1将所述接收到RLC SDU(或RLC PDU)中序列号为0、2～6的RLC SDU发送给RLC Rx 2，其中序列号为2和6的RLC SDU(或RLC PDU)丢失(即未被RLC Rx 2接收到或被RLC Rx 2检测为丢失)。RLC Tx2将其中序列号为0，3，4的RLC SDU(或RLC PDU)发送给RLC Rx3，但是序列号为3的RLC SDU(或RLC PDU)丢失(即未被RLC Rx 3接收到或被RLC Rx 3检测为丢失)。此时，如果RLC Rx 3接收到来自RLC Tx 2的询问，将生成一个第一RLC状态PDU，其中第一ACK_SN被设置为5，第一NACK_SN被设置为3，然后将所述第一状态PDU发送给IAB节点2中对应的RLC 实体(例如RLC Tx 2)。在接收到所述第一RLC状态PDU后，将第一ACK_SN和第一NACK_SN指示上层或指示RLC Rx 2。此时，如果RLC Rx 2接收到来自RLC Tx 1的询问。RLC Rx 2生成一个第二RLC状态报告并发送给IAB节点1中对应的RLC实体，其中，第一ACK_SN被设置为6，第二ACK_AN被设置为5(即上层或转发RLC实体指示的NACK_SN)，第一NACK_SN设置为2，另一个第一NACK_SN被设置为6，第二NACK_SN设置为3。IAB节点1中的RLC实体接收到所述状态报告后，将第二ACK_SN、序列号小于第二ACK_SN的第一NACK_SN以及第二NACK_SN指示给上层或RLC Rx 1。在本示例中，RLC Tx 1向上层或RLC RX 1指示的第二ACK_SN＝5，第一NACK_SN＝2，第二NACK_SN＝3。此时，如果RLC Rx 1接收到来自RLC Tx ue的询问。RLC Rx 1生成一个第二RLC状态报告并发送给UE中对应的RLC实体，其中，第一ACK_SN设置为8，第一NACK_SN设置为1，第二ACK_SN设置为5(即上层或转发RLC实体指示的第二ACK_SN)，两个第二NACK_SN分别设置为2和3(即上层或转发RLC实体指示的第二NACK_SN和满足条件的第一NACK_SN)。本示例中以RLC状态报告中包含第二NACK_SN为例进行说明，如果RLC状态报告中不包含第二NACK_SN，而是用位图描述，那么可采用与设置第二NACK_SN类似的方法，将位图中对应的位设置为0或1。例如，在IAB节点1的RLC Rx 1生成的RLC状态PDU中，将序列号为2和3的RLC PDU在位图中对应的位设置为0。
从上述示例可以看出，本公开实施例中，所述第二NACK_SN(或位图)中包含被最终目的地RLC实体检测为丢失的RLC SDU(或RLC PDU)或其对应的序列号，也包含被中间节点RLC实体检测为丢失的RLC SDU(或RLC PDU)或其对应的序列号。换言之，一个RLC实体接收端生成的第二RLC状态报告中，第二NACK_SN(或位图)包含被最终目的地RLC实体检测为丢失的RLC SUD或RLC PDU的序列号和被其转发RLC实体的对等实体检测为丢失且序列号小于第二ACK_SN的RLC SDU或RLC PDU。但是，考虑到如果中间节点RLC实体未接收到某个RLC SDU(或RLC PDU)，那么最终目的地RLC实体必然也收不到 所述RLC SDU(或RLC PDU)。在本公开实施例中，为了描述方便，将第二NACK_SN(或位图中的位)指示的RLC SDU(或RLC PDU)或其序列号统称为被最终目的地RLC实体检测为丢失的RLC SDU或RLC PDU)或其对应的序列号。
在步骤002中，AM RLC实体发送端将状态报告信息(称为状态报告指示)指示给上层(例如适配实体)或指示给对应的AM RLC实体接收端(本公开实施例中称为转发RLC实体)。所述AM RLC实体接收端(即转发RLC实体)与AM RLC实体发送端属于同一个IAB节点，是所述AM RLC实体发送端映射到的AM RLC实体接收端，来自AM RLC实体接收端的数据将被转发到AM RLC实体发送端，然后由AM RLC实体发送端发送给其对等RLC实体。在上行传输中，AM RLC实体发送端位于MT，其对应的AM RLC实体接收端位于DU；在下行传输中，AM RLC实体发送端位于DU，其对应的AM RLC实体接收端位于MT。例如，图2中IAB节点1中RLC Rx是RLC Tx对应的AM RLC实体接收端。在本公开实施例中，AM RLC实体发送端和其对应的AM RLC实体接收端互称为转发RLC实体。
如果所述接收到的状态报告是第一RLC状态报告，所述状态报告指示可以包括以下内容：
(1)被对等AM RLC实体(即AM RLC实体接收端)确认正确接收的RLC SDU或RLC PDU)。所述正确接收的RLC SDU或RLC PDU是序列号小于第一ACK_SN且不是状态报告中被报告为丢失的RLC SDU或RLC PDU。例如，状态报告指示指示第一ACK_SN或其对应的RLC SDU。
(2)被对等AM RLC实体(即AM RLC实体接收端)检测为已丢失的RLC SDU或RLC PDU。所述检测为已丢失的RLC SDU或RLC PDU是序列号SN为第一状态报告中报告的第一NACK_SN或在第一NACK_SN和第一NACK_range确定的范围内(即第一NACK_SN＜SN＜第一NACK_SN+第一NACK_range)。可选的，如果一个RLC SDU的分段被AM RLC 实体接收端检测为已丢失，在状态报告指示中包含对应的RLC SDU。例如，状态报告指示指示第一NACK_SN和对应的第一NACK_range(如果存在)或其对应的RLC SDU。
如果所述接收到的状态报告是第二RLC状态报告，所述状态报告指示可以包括以下内容：
(1)被远端AM RLC实体接收端确认正确接收的RLC SDU或RLC PDU。所述正确接收的RLC SDU(或RLC PDU)是序列号SN小于第二ACK_SN且不被对等AM RLC实体和远端AM RLC实体接收端检测为已丢失的RLC SDU(或RLC PDU)，和/或所述RLC SDU的任意分段也不被对等AM RLC实体检测为已丢失。
(2)被远端AM RLC实体接收端检测为已丢失的RLC SDU或RLC PDU。所述被远端AM RLC实体接收端检测为已丢失的RLC SDU或RLC PDU是RLC状态报告中指示为被检测为已丢失的RLC SDU或RLC PDU，这些RLC SDU或RLC PDU的序列号小于第二ACK_SN。换言之，远端AM RLC实体检测为已丢失的RLC SDU或RLC PDU包含序列号为第二NACK_SN的RLC SDU或RLC PDU和被对等RLC实体检测为丢失且序列号小于第一ACK_SN的RLC SDU或RLC PDU。具体的，在一个实施例中，所述被远端AM RLC实体检测为已丢失的RLC SDU或RLC PDU包含序列为第二NACK_SN的RLC SDU或RLC PDU和序列号为第一NACK_SN(所述第一NACK_SN小于第二ACK_SN)的RLC SDU或RLC PDU。在另一实施例中，所述被远端AM RLC实体检测为已丢失的RLC SDU或RLC PDU是序列号为E4取值为1(或0)对应的NACK_SN的RLC SDU且所述NACK_SN小于第二ACK_SN。例如，序列号SN为E4取值为1所对应的NACK_SN的RLC SDU(或RLC PDU)和/或序列号SN满足E4取值为1所对应的NACK_SN和NACK_range确定的范围内(即NACK_SN＜＝SN＜NACK_SN+NACK_range)的RLC SDU或 PDU且SN＜第二ACK_SN。。在一个实施例中，所述被远端AM RLC实体检测为已丢失的RLC SDU或RLC PDU包含序列为位图中取值为0且序列号小于第二ACK_SN的RLC SDU(或RLC PDU)和。综上所述，所述状态报告指示包含被远端RLC实体或对等RLC实体检测为已丢失且序列号小于第二ACK_SN的RLC SDU或RLC PDU。
需要说明的是，在本公开实施例中，如果AM RLC实体发送端将状态信息指示指示上层(例如适配实体)，那么适配实体在收到来自所述AM RLC实体发送端(也称为适配实体的下层)的状态信息指示后，根据数据转发规则，将所述状态信息指示指示给所述AM RLC实体发送端所对应的转发RLC实体。所述数据转发规则是指被配置的来自一个逻辑信道或RLC实体的数据应该转发到哪个逻辑信道或RLC实体的规则。例如，图1的IAB节点1的RLC Rx的数据被配置为转发到RLC Tx，那么可以称RLC Rx为RLC Tx的转发RLC实体，或者称RLC Tx为RLC Rx的转发RLC实体；在RLC Tx接收到来自对等RLC实体的RLC状态报告后，看将状态报告指示指示给对应的转发RLC实体。
综合上述两种情况，可以定义第三ACK_SN，如果接收到的RLC状态报告中包含第二ACK_SN(对应第二RLC状态报告)，则将第三ACK_SN的值设置为与第二ACK_SN的值相同，否则(对应第一RLC状态报告)，将第三ACK_SN的值设置为与第一ACK_SN的值相同。此时，所述向转发RLC实体或上层指示的状态报告信息可以包括以下一项或多项：
(1)被远端RLC实体或对等RLC实体检测为已丢失且序列号小于第三ACK_SN的RLC SDU或RLC PDU或其序列号。
(2)被远端AM RLC实体接收端确认正确接收的RLC SDU或RLC PDU或其序列号。
(3)被远端AM RLC实体接收端确认正确接收的RLC SDU或RLC  PDU的最大序列号。
(4)被检测为已丢失且序列号小于第三ACK_SN的RLC SDU或RLC PDU或其序列号。
(5)第三ACK_SN。
可选地，AM RLC实体发送端被配置为是否向转发RLC实体或上层指示状态报告指示。例如，可以通过RRC消息来实现该配置。具体地，在RRC消息中包含的RLC-BearerConfig信元中携带一个指示标识，用于指示对应的RLC实体是否向转发RLC实体或上层指示状态报告指示。所述指示标识的取值为真或1或所述标识出现，表示对应的RLC实体向转发RLC实体或上层指示状态报告指，或者表示对应的RLC实体在接收到来自对等RLC实体的状态报告(可以是第一RLC状态报告或第二RLC状态报告)时，向转发RLC实体或上层指示状态报告指示。
下面描述IAB节点中AM RLC实体接收端需要执行的操作。
在步骤001中，AM RLC实体接收端接收到来自对等AM RLC实体发送端的询问(poll)或包含询问的RLC PDU，即接收到的RLC PDU中包含询问或询问比特被设置为1。
在步骤002中，AM RLC实体接收端根据上层或其对应的转发RLC实体所指示的状态报告指示构建RLC状态报告，所述RLC状态报告可以是第一RLC状态报告或第二RLC状态报告。如果是构建第二RLC状态报告，则将第二ACK_SN的值设置为被远端RLC实体确认为正确接收的RLC SDU或RLC PDU的最大序列号。第二NACK_SN、第二NACK_range或位图中对应的位的值根据被转发RLC实体或上层指示的被检测为已丢失的RLC SDU或RLC PDU来设置，具体见本发明其他实施例所述，在此不再累述。
可选的，AM RLC实体接收端被配置为是否可以发送第二RLC状态报告，例如可以通过RRC消息来实现该配置。具体地，在RRC消息中包含的RLC-BearerConfig信元中携带一个指示标识，所述指示标识用于指示对应的RLC实体是否可以构建第二RLC状态报告。
可选的，AM RLC实体接收端还可以根据是否有来自上层或转发 RLC实体指示的状态报告信息来确定发送哪种类型的状态报告。如果M RLC实体接收端接收到来自上层或转发RLC实体指示的状态报告信息，则发送第二RLC状态报告，否则发送第一RLC状态报告。
可选的，AM RLC实体接收端还可以根据所述AM RLC实体是否是中间节点中的AM RLC实体(例如，图1和图2中的IAB节点1和IAB节点2)来确定构建哪种类型的RLC状态报告，其中只有中间节点会构建第二RLC状态报告。
下面描述UE中AM RLC实体发送端需要执行的操作。
在步骤001中，AM RLC实体发送端接收到来自AM RLC实体接收端的RLC状态报告。如果所述状态报告是第一状态报告(例如CPT字段取值为000)，则执行以下操作至少一项：
(1)将被正确接收的RLC SDU指示上层。
(2)如果所述状态报告中包含序列号SN＝POLL_SN的RLC SDU的肯定或否定确认(positive or negative acknowledgement)且定时器t-PollRetransmit正在运行，则停止和重置所述定时器。
如果所述状态报告是第二状态报告(例如CPT字段取值为001)，则可执行以下操作至少一项：
(1)如果接收到一个RLC SDU或RLC SDU分段的否定确认且所述否定确认来自对等RLC实体(例如状态报告中对应扩展字段取值为0，即E4取值为0)，AM RLC实体发送端执行以下操作：
如果所述RLC SDU的序列号SN在发送窗内且满足SN＜＝已递交给下层的AMD PDU的最大序列号(the highest SN of the AMD PDU among the AMD PDUs submitted to lower layer)，则重传所述被否定确认的RLC SDU或RLC SDU的分段。
(2)如果接收到一个RLC SDU的肯定确认且所述肯定确认来自最终目的地或远端AM RLC实体(例如所述RLC SDU被最终目的地和下一跳肯定确认)，则将所述被肯定确认(或被正确接收)的RLC SDU指示上层。
(3)如果接收到一个RLC SDU的否定确认且所述否定确认来自最终目的地或远端AM RLC实体，则从重传缓存区中删除所述RLC SDU。
(4)如果所述状态报告中包含序列号SN＝POLL_SN的RLC SDU的肯定或否定确认(positive or negative acknowledgement)，所述肯定或否定确认可来自对等AM RLC实体或远端AM RLC实体，如果定时器t-PollRetransmit正在运行，则停止和重置所述定时器。
本公开实施例中，POLL_SN是询问发送状态变量，用于存储已递交给下层的AMD PDU的最大序列号，所述POLL_SN根据3GPP TS38.322中的5.3.3.2节设置，其初始值为0(This state variable holds the value of the highest SN of the AMD PDU among the AMD PDUs submitted to lower layer when POLL_SN is set according to sub clause 5.3.3.2.)。定时器t-PollRetransmit被AM RLC实体发送端用来重传询问。
应该理解，上面描述的UE中AM RLC实体发送端执行的操作适用于作为多跳传输的源节点，因此同样适用于下行数据传输中的IAB施主中的AM RLC实体发送端。在此不再赘述。
需要说明的是，本公开实施例中与RLC SDU或RLC PDU序列号相关的字段(或称状态变量)的取值从0到2 序列号长度-1。例如，当序列号长度为12比特是，取值从0到4095，当序列号长度为18比特时，取值从0到262143。本公开实施例中的所有状态变量的运算操作(arithmetic operations)都受模的影响(即最终值为运算操作得到的值模2 序列号长度)。
在本公开实施例中，RLC层、适配层和MAC层可分别替换为RLC实体、适配实体以及MAC实体，反之亦然。
本公开实施例中，IAB施主的标识可以指IAB施主的DU或CU的标识，例如IAB施主的DU或CU的IP地址。IAB-节点的标识可以指IAB节点的DU或MT的标识，例如IAB节点的DU或MT的IP地址。
在本公开实施例中，适配实体为接收自UE或本地UE的数据(例如：RLC SDU)增加适配层头部，并根据数据转发规则或目的地址将 产生的适配PDU递交给对应的适配实体或下层。对接收自其他IAB节点或其适配实体的数据(适配PDU)根据数据转发规则或目的地址递交给对应的下层或对应的适配实体。所述数据转发规则可以由IAB施主为IAB节点配置，例如，通过RRC消息配置。
本公开实施例中，适配层的数据可以分别称为适配SDU(其中不包含适配层的头部)和适配PDU(其中包含适配层的头部)，其中适配PDU又可分为适配数据PDU和适配控制PDU。可以在适配PDU的头部用一个字段(记为D/C字段)指示适配PDU是控制PDU还是数据PDU。如果D/C字段取值为0表示适配数据PDU，如果D/C字段取值为1表示适配控制PDU。反之亦然。
在本公开实施例中所述适配实体的下层可以是RLC层或MAC层。如果DU和/或MT与适配实体之间是一对一的映射关系(即一个DU或MT中定义一个适配实体)或者适配实体与RLC实体间是一对一的映射关系，在进行数据传输时，接收适配实体(或IP层或实现路由功能的实体)要根据目的地址或IAB-donor DU的地址(例如IAB-donor DU的IP地址)选择对应的发送适配实体(或MT适配实体)。相应的，AM RLC实体发送端在接收到第一RLC状态报告或第二RLC状态报告时，AM RLC实体发送端可以将状态信息指示指示给上层(例如适配实体)，适配实体在接收到所述状态信息指示后将所述状态信息指示指示给所映射到的适配实体，然后由所映射到的适配实体指示给下层(例如，所述AM实体实体发送端的转发RLC实体)。如果DU和/或MT与适配层之间是多对一的映射关系(即多个DU和/或MT中定义一个适配实体或一个IAB节点或施主中定义一个适配实体)，在进行数据传输时，适配实体(或IP层或实现路由功能的实体)根据目的地址或IAB-donor DU的地址(例如IAB-donor DU的IP地址)选择对应的RLC实体。本公开实施例是基于DU和/或MT与适配层之间是多对一的映射关系进行描述的，如果DU和/或MT与适配实体之间是一对一的映射关系，则接收适配实体(或IP层或实现路由功能的实体)在转发数据(或指示状态信息指示)时需要按照DU和/或MT与适配实体之间的对应关系选择发送适配实体。上述发送适配实体也可以用于接收数据，接收适配实体也可以发送数据， 在这种情形下，发送适配实体和接收适配实体都可称为适配实体；或者发送适配实体称为适配实体的发送端，接收适配实体称为适配实体的接收端。另外，本公开中将路由功能整合在适配实体中，如果路由功能属于适配实体的上层实体，则接收适配实体在接收到需要转发的数据后，发送给上层，上层按照目的地址将数据路由(或递交)到对应的发送适配实体。本公开实施例中，适配PDU中的目的地址可以不包含在适配PDU中，例如，作为目的IP地址包含的IP报文的头部。本公开中，如未特别说明，对于上行，目的地址可以指IAB-donor(或IAB-donor DU)的地址，例如IAB-donor(或IAB-donor DU)的IP地址；对于下行，目的地址可以指IAB-nod(或IAB-node MT)的地址，例如IAB-nod(或IAB-node MT)的IP地址；对于下行，目的地址也可以是UE的标识，例如C-RNTI。
在本公开实施例中，对于上行，用于接收数据的IAB节点可以是IAB节点的DU，用于接收数据的IAB施主可以是IAB施主的DU。对于下行，用于接收数据的IAB节点可以是IAB节点的MT。
如上，已经参考附图对本公开的实施例进行了详细描述。本公开提出了一种增强的RLC状态报告，其包含关于多跳传输中的最终目的地RLC实体对RLC数据单元的接收情况的指示信息。RLC发送实体可以通过该增强的RLC状态报告获知最终目的地RLC实体对RLC SDU的接收情况，从而可以识别出途中丢包的情形，通过重传实现无丢包传输。通过本发明实施例的方案，可以实现多跳IAB网络中的端到端无丢包传输。
应该理解，在本公开的实施例中的术语命名和字段命名仅是作为示例而非限定，其他命名(只要能够指示同样的信息)也是可行的，并且因此落在本公开的范围内。例如，在上述实施例中，第二ACK_SN、第二NACK_SN、第二NACK_range是与最终目的地RLC实体的接收情况相关的反馈信息，因此也可以称为远端ACK_SN、远端NACK_SN、远端NACK_range，或者可以采用其他命名。
应该理解，本发明的方法不限于上述实施例示出的步骤，而是可以 包括更多的其他步骤。本公开的设备的具体结构也不局限于上述实施例，而是可以包括其他部件。例如，在图5～图8的通信设备中仅示出了与本公开相关的部件，以避免混淆本公开。然而，本领域技术人员应理解，尽管在图中未示出，但是根据本公开实施例的通信设备还可以包括构成用户设备或RAN节点的其他基本单元。此外，上述实施例中所描述的具有相同效果的组件可以相互替代。
运行在根据本发明的设备上的计算机可执行指令或者程序可以是通过控制中央处理单元(CPU)来使计算机实现本发明的实施例功能的程序。该程序或由该程序处理的信息可以临时存储在易失性存储器(如随机存取存储器RAM)、硬盘驱动器(HDD)、非易失性存储器(如闪速存储器)、或其他存储器系统中。
用于实现本发明各实施例功能的计算机可执行指令或程序可以记录在计算机可读存储介质上。可以通过使计算机系统读取记录在所述记录介质上的程序并执行这些程序来实现相应的功能。此处的所谓“计算机系统”可以是嵌入在该设备中的计算机系统，可以包括操作系统或硬件(如外围设备)。“计算机可读存储介质”可以是半导体记录介质、光学记录介质、磁性记录介质、短时动态存储程序的记录介质、或计算机可读的任何其他记录介质。
用在上述实施例中的设备的各种特征或功能模块可以通过电路(例如，单片或多片集成电路)来实现或执行。设计用于执行本说明书所描述的功能的电路可以包括通用处理器、数字信号处理器(DSP)、专用集成电路(ASIC)、现场可编程门阵列(FPGA)、或其他可编程逻辑器件、分立的门或晶体管逻辑、分立的硬件组件、或上述器件的任意组合。通用处理器可以是微处理器，也可以是任何现有的处理器、控制器、微控制器、或状态机。上述电路可以是数字电路，也可以是模拟电路。因半导体技术的进步而出现了替代现有集成电路的新的集成电路技术的情况下，本发明的一个或多个实施例也可以使用这些新的集成电路技术来实现。
此外，本发明并不局限于上述实施例。尽管已经描述了所述实施例的各种示例，但本发明并不局限于此。安装在室内或室外的固定或非移动电子设备可以用作终端设备或通信设备，如AV设备、厨房设备、清 洁设备、空调、办公设备、自动贩售机、以及其他家用电器等。
如上，已经参考附图对本发明的实施例进行了详细描述。但是，具体的结构并不局限于上述实施例，本发明也包括不偏离本发明主旨的任何设计改动。另外，可以在权利要求的范围内对本发明进行多种改动，通过适当地组合不同实施例所公开的技术手段所得到的实施例也包含在本发明的技术范围内。此外，上述实施例中所描述的具有相同效果的组件可以相互替代。

Claims (13)

  1. 一种在多跳传输中的发送节点处执行的方法，包括：
    向直接通信的RLC实体发送询问；以及
    从所述RLC实体接收RLC状态报告，所述RLC状态报告包括指示RLC状态报告的类型的信息，并且至少一类RLC状态报告包含指示多跳数据传输的最终目的地RLC实体是否接收到RLC数据单元的信息。
  2. 根据权利要求1所述的方法，其中所述发送节点包括用户设备和无线接入网RAN节点。
  3. 根据权利要求1所述的方法，其中所述指示多跳数据传输的最终目的地RLC实体是否接收到RLC数据单元的信息包括下述中的至少一个：
    最终目的地RLC实体正确接收的RLC数据单元的最大序列号；
    最终目的地RLC实体下一个未接收到的RLC数据单元的序列号；
    被最终目的地RLC实体检测为已丢失的RLC数据单元的序列号；
    被最终目的地RLC实体检测为连续丢失的RLC数据单元的数目；
    被最终目的地RLC实体检测为第一个丢失的RLC数据单元的序列号；以及
    指示哪些RLC数据单元被最终目的地RLC实体正确接收和/或哪些RLC数据单元被最终目的地RLC实体检测为丢失的位图。
  4. 根据权利要求1～3中任一项所述的方法，其中所述RLC状态报告包括下述字段：类型字段、远端ACK_SN字段和远端NACK_SN字段，
    其中，
    所述类型字段包含指示RLC状态报告的类型的信息，
    所述远端ACK_SN字段指示最终目的地RLC实体正确接收的RLC数据单元的最大序列号，或者指示最终目的地RLC实体下一个未接收到的RLC数据单元的序列号，
    所述远端NACK_SN字段指示被最终目的地RLC实体检测为已丢失的RLC数据单元的序列号。
  5. 根据权利要求1～3中任一项所述的方法，其中所述RLC状态报 告包括下述字段：类型字段、远端ACK_SN字段、远端NACK_SN字段和远端NACK_range字段，
    其中，
    所述类型字段包含指示RLC状态报告的类型的信息，
    所述远端ACK_SN字段指示最终目的地RLC实体正确接收的RLC数据单元的最大序列号，或者指示最终目的地RLC实体下一个未接收到的RLC数据单元的序列号，
    所述远端NACK_SN字段指示被最终目的地RLC实体检测为已丢失的RLC数据单元的序列号，
    所述远端NACK_range字段指示从对应的远端NACK_SN开始连续丢失的RLC数据单元的数目。
  6. 根据权利要求1～3中任一项所述的方法，其中所述RLC状态报告包括下述字段：类型字段和远端ACK_SN字段，
    其中，
    所述类型字段包含指示RLC状态报告的类型的信息，
    所述远端ACK_SN字段指示最终目的地RLC实体正确接收的RLC数据单元的最大序列号，或者指示最终目的地RLC实体下一个未接收到的RLC数据单元的序列号。
  7. 根据权利要求1～3中任一项所述的方法，其中所述RLC状态报告包括下述字段：类型字段、FMSN字段和Bitmap字段，
    其中，
    所述类型字段包含指示RLC状态报告的类型的信息，
    所述FMSN字段指示被最终目的地RLC实体检测为第一个丢失的RLC数据单元的序列号，
    所述Bitmap字段指示在所述FMSN之后哪些RLC数据单元被最终目的地RLC实体正确接收和/或哪些RLC数据单元被最终目的地RLC实体检测为丢失的位图。
  8. 根据权利要求1～3中任一项所述的方法，其中所述RLC状态报告包括下述字段：类型字段、第一指示字段、远端ACK_SN字段和NACK_SN字段，
    其中，
    所述类型字段包含指示RLC状态报告的类型的信息，
    所述第一指示字段指示所述NACK_SN字段与最终目的RLC实体相关还是与直接通信的RLC实体相关，
    所述远端ACK_SN字段指示最终目的地RLC实体正确接收的RLC数据单元的最大序列号，或者指示最终目的地RLC实体下一个未接收到的RLC数据单元的序列号，
    所述NACK_SN字段指示被检测为已丢失的RLC数据单元的序列号。
  9. 根据权利要求1～3中任一项所述的方法，其中所述发送节点是用户设备，所述方法还包括：
    对于收到来自最终目的地RLC实体的肯定确认的RLC数据单元，将其指示给上层。
  10. 一种在多跳传输中的接收节点处执行的方法，包括：
    构造无线链路控制RLC状态报告，所述RLC状态报告包括指示RLC状态报告的类型的信息，并且至少一类RLC状态报告包含指示多跳数据传输的最终目的地RLC实体是否接收到RLC数据单元的信息；以及
    发送所述RLC状态报告。
  11. 根据权利要求10所述的方法，其中所述指示多跳数据传输的最终目的地RLC实体是否接收到RLC数据单元的信息包括下述中的至少一个：
    最终目的地RLC实体正确接收的RLC数据单元的最大序列号，
    最终目的地RLC实体下一个未接收到的RLC数据单元的序列号，
    被最终目的地RLC实体检测为已丢失的RLC数据单元的序列号，
    被最终目的地RLC实体检测为连续丢失的RLC数据单元的数目，
    被最终目的地RLC实体检测为第一个丢失的RLC数据单元的序列号，
    指示哪些RLC数据单元被最终目的地RLC实体正确接收和/或哪些RLC数据单元被最终目的地RLC实体检测为丢失的位图。
  12. 一种第一通信设备，包括：
    发送模块，配置为：向直接通信的RLC实体发送询问；以及
    接收模块，配置为：从所述RLC实体接收RLC状态报告，所述RLC状态报告包括指示RLC状态报告的类型的信息，并且至少一类RLC状态报告包含指示多跳数据传输的最终目的地RLC实体是否接收到RLC数据单元的信息。
  13. 一种第二通信设备，包括：
    处理模块，配置为：构造无线链路控制RLC状态报告，所述RLC状态报告包括指示RLC状态报告的类型的信息，并且至少一类RLC状态报告包含指示多跳数据传输的最终目的地RLC实体是否接收到RLC数据单元的信息；以及
    发送模块，配置为：发送所述RLC状态报告。
PCT/CN2020/074208 2019-02-03 2020-02-03 发送rlc状态报告的方法、设备和存储介质 WO2020156569A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910108853.XA CN111525989A (zh) 2019-02-03 2019-02-03 发送rlc状态报告的方法、设备和存储介质
CN201910108853.X 2019-02-03

Publications (1)

Publication Number Publication Date
WO2020156569A1 true WO2020156569A1 (zh) 2020-08-06

Family

ID=71841889

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/074208 WO2020156569A1 (zh) 2019-02-03 2020-02-03 发送rlc状态报告的方法、设备和存储介质

Country Status (2)

Country Link
CN (1) CN111525989A (zh)
WO (1) WO2020156569A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115087026A (zh) * 2022-08-19 2022-09-20 中电防务科技有限公司 一种提高卫星移动通信系统无线链路传输可靠性的方法

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113473532B (zh) * 2021-06-29 2022-04-19 中信科移动通信技术股份有限公司 一种无线链路控制状态报告优化传输方法及系统
CN114584263B (zh) * 2022-01-19 2024-05-03 网络通信与安全紫金山实验室 重发超限及双无条件下rlc确认模式增强方法及装置
CN114826495B (zh) * 2022-06-22 2022-09-16 深圳市佳贤通信设备有限公司 一种降低nr、rlc、am分片丢失报告开销的方法

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102056226A (zh) * 2009-11-10 2011-05-11 中兴通讯股份有限公司 Pdcp状态报告的获取方法和pdcp实体
WO2018009011A1 (en) * 2016-07-06 2018-01-11 Lg Electronics Inc. Method and apparatus for supporting handover of drone in wireless communication system

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102056226A (zh) * 2009-11-10 2011-05-11 中兴通讯股份有限公司 Pdcp状态报告的获取方法和pdcp实体
WO2018009011A1 (en) * 2016-07-06 2018-01-11 Lg Electronics Inc. Method and apparatus for supporting handover of drone in wireless communication system

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
ERICSSON: "RLC Status Report Format", 3GPP TSG-RAN WG2 #100 R2-1712936, 1 December 2017 (2017-12-01), XP051371807, DOI: 20200401115237A *
KYOCERA: "Further consideration of hop-by-hop RLC ARQ in IAB", 3GPP TSG-RAN WG2 #103 R2-1811844, 24 August 2018 (2018-08-24), XP051521482, DOI: 20200401115137X *
OPPO: "Discussion on User Plane for IAB", 3GPP TSG-RAN2 MEETING #102 R2-1806693, 25 May 2018 (2018-05-25), XP051443163, DOI: 20200401121705X *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115087026A (zh) * 2022-08-19 2022-09-20 中电防务科技有限公司 一种提高卫星移动通信系统无线链路传输可靠性的方法
CN115087026B (zh) * 2022-08-19 2022-11-01 中电防务科技有限公司 一种提高卫星移动通信系统无线链路传输可靠性的方法

Also Published As

Publication number Publication date
CN111525989A (zh) 2020-08-11

Similar Documents

Publication Publication Date Title
WO2020156569A1 (zh) 发送rlc状态报告的方法、设备和存储介质
CN108617029B (zh) 无线承载配置方法、及相应的ue和基站
US9900798B2 (en) Polling and reporting mechanism
US9985749B2 (en) Method and system for improving wireless link efficiency
JP5671122B2 (ja) 無線通信システムの状態情報送信方法及び受信装置
TWI361591B (en) A method of performing polling procedure in a wireless communication system
US20120257509A1 (en) Method and apparatus for communicating deliver of data packets to a user equipment in a wireless communication system
JP2013243722A (ja) 無線通信システムにおけるｈａｒｑに基づくデータ伝送の制御
WO2021128913A1 (zh) 蜂窝网络上行链路ecn机制的增强方法、设备及介质
WO2020088472A1 (zh) 通信方法及装置
JP2009534916A (ja) セルラ・アクセス・システムにおける改良されたデータ通信のための方法および装置
WO2016161594A1 (zh) 一种数据传输的方法及装置
JP2010521869A (ja) 移動通信システムにおけるｒｌｃｐｄｕ送信方法、無線リソース割当方法、及び移動通信システムのｒｌｃエンティティ
US20220225163A1 (en) Communications device, infrastructure equipment and methods
US20220132362A1 (en) Wireless communication methods for adaptive entity and rlc entity, and communication device
WO2022042379A1 (zh) 数据处理方法、基站、终端及存储介质
JP2020507963A (ja) データ送信方法および装置、ならびに顧客宅内機器
WO2015018009A1 (zh) 用于自动重传的方法、用户设备和基站
WO2019062760A1 (zh) 服务数据单元处理方法、丢弃方法、相应的用户设备和计算机可读介质
WO2021027685A1 (zh) Pdcp实体发送端/接收端的执行方法、pdcp实体及通信设备
WO2021233192A1 (zh) 一种无线链路控制状态报告的方法及对应装置
KR102609328B1 (ko) 무선 통신 방법 및 디바이스
WO2019192425A1 (zh) 确认模式rlc实体及其发送/重传方法、通信设备
WO2020151655A1 (zh) 基于逐跳自动重传请求的数据传输方法以及用户设备ue
WO2018189882A1 (ja) 無線通信装置、無線通信方法、及び無線通信システム

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20749454

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20749454

Country of ref document: EP

Kind code of ref document: A1