WO2022199482A1 - 上行传输的控制方法、装置及终端 - Google Patents

上行传输的控制方法、装置及终端 Download PDF

Info

Publication number
WO2022199482A1
WO2022199482A1 PCT/CN2022/081691 CN2022081691W WO2022199482A1 WO 2022199482 A1 WO2022199482 A1 WO 2022199482A1 CN 2022081691 W CN2022081691 W CN 2022081691W WO 2022199482 A1 WO2022199482 A1 WO 2022199482A1
Authority
WO
WIPO (PCT)
Prior art keywords
iab node
bsr
timer
triggered
indication
Prior art date
Application number
PCT/CN2022/081691
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 WO2022199482A1 publication Critical patent/WO2022199482A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/06—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling

Definitions

  • the present application belongs to the field of communication technologies, and in particular relates to a control method, device and terminal for uplink transmission.
  • IAB Integrated Access Backhaul
  • RLF Radio Link Failure
  • the embodiments of the present application provide an uplink transmission control method, device, and terminal, which can solve the problem of how to process the triggered data transmission when an IAB node receives a back RLF indication.
  • a method for controlling uplink transmission including:
  • the IAB node receives the return RLF indication
  • the IAB node cancels or suspends the triggered data transmission.
  • a control device for uplink transmission including:
  • the receiving module is used to receive and return the RLF indication
  • the processing module is used to cancel or suspend the triggered data transmission.
  • a terminal which is an IAB node, including a processor, a memory, and a program or instruction stored on the memory and executable on the processor, the program or instruction being executed by the
  • the processor implements the steps of the method as described in the first aspect when executed.
  • a fourth aspect provides a terminal, which is an IAB node, including a processor and a communication interface, wherein the communication interface is used to receive and return an RLF indication, and the processor is used to cancel or suspend triggered data transmission .
  • a readable storage medium is provided, and a program or an instruction is stored on the readable storage medium, and when the program or instruction is executed by a processor, the steps of the method according to the first aspect are implemented.
  • a chip in a sixth aspect, includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is configured to run a program or an instruction to implement the method according to the first aspect .
  • a computer program/program product is provided, the computer program/program product is stored in a non-transitory storage medium, and the program/program product is executed by at least one processor to implement the first aspect the steps of the method.
  • the IAB node after receiving the returned RLF indication, can cancel or suspend the triggered data transmission, thereby realizing the processing of the triggered data transmission and ensuring the stability of data transmission in the IAB network.
  • FIG. 1 is a block diagram of a wireless communication system to which an embodiment of the present application can be applied;
  • FIG. 2 is a schematic diagram of an IAB system in an embodiment of the present application.
  • FIG. 3 is a flowchart of a method for controlling uplink transmission provided by an embodiment of the present application.
  • FIG. 4 is a schematic structural diagram of an apparatus for controlling uplink transmission provided by an embodiment of the present application.
  • FIG. 5 is a schematic structural diagram of a terminal provided by an embodiment of the present application.
  • FIG. 6 is a schematic structural diagram of another terminal provided by an embodiment of the present application.
  • first, second and the like in the description and claims of the present application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It is to be understood that the terms so used are interchangeable under appropriate circumstances so that the embodiments of the present application can be practiced in sequences other than those illustrated or described herein, and that "first”, “second” distinguishes Usually it is a class, and the number of objects is not limited.
  • the first object may be one or multiple.
  • “and/or” in the description and claims indicates at least one of the connected objects, and the character “/" generally indicates that the associated objects are in an "or” relationship.
  • LTE Long Term Evolution
  • LTE-Advanced LTE-Advanced
  • LTE-A Long Term Evolution-Advanced
  • CDMA Code Division Multiple Access
  • TDMA Time Division Multiple Access
  • FDMA Frequency Division Multiple Access
  • OFDMA Orthogonal Frequency Division Multiple Access
  • SC-FDMA Single-carrier Frequency-Division Multiple Access
  • system and “network” in the embodiments of the present application are often used interchangeably, and the described technology can be used not only for the above-mentioned systems and radio technologies, but also for other systems and radio technologies.
  • NR New Radio
  • the following description describes a New Radio (NR) system for example purposes, and uses NR terminology in most of the description below, but the techniques can also be applied to applications other than NR system applications, such as 6th generation (6th generation ) Generation, 6G) communication system.
  • 6th generation 6th generation
  • 6G 6th generation
  • FIG. 1 shows a block diagram of a wireless communication system to which the embodiments of the present application can be applied.
  • the wireless communication system includes a terminal 11 and a network-side device 12 .
  • the terminal 11 may also be referred to as a terminal device or user equipment (User Equipment, UE), and the terminal 11 may be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer) or a notebook computer, a personal digital computer Assistant (Personal Digital Assistant, PDA), PDA, Netbook, Ultra-Mobile Personal Computer (UMPC), Mobile Internet Device (Mobile Internet Device, MID), Wearable Device (Wearable Device) or vehicle-mounted device (Vehicle User Equipment, VUE), pedestrian terminal (Pedestrian User Equipment, PUE) and other terminal-side devices, wearable devices include: smart watches, bracelets, headphones, glasses, etc.
  • the network side device 12 may be a base station or a core network, wherein the base station may be referred to as a Node B, an evolved Node B, an access point, a Base Transceiver Station (BTS), a radio base station, a radio transceiver, a basic service Set (Basic Service Set, BSS), Extended Service Set (Extended Service Set, ESS), Node B, Evolved Node B (eNB), Home Node B, Home Evolved Node B, Wireless Local Area Network (WLAN) ) access point, WiFi node, Transmitting Receiving Point (TRP) or some other suitable term in the field, as long as the same technical effect is achieved, the base station is not limited to specific technical vocabulary, it should be noted that , in the embodiments of the present application, only the base station in the NR system is used as an example, but the specific type of the base station is not limited.
  • BSS Basic Service Set
  • ESS Extended Service Set
  • Node B Evolved Node B
  • FIG. 2 shows a schematic diagram of an IAB system in an embodiment of the present application.
  • an IAB node includes a Distributed Unit (DU) functional part and a Mobile Terminal (Mobile Termination, MT) functional part.
  • the IAB node can find a parent IAB node (parent IAB node) , and establishes a wireless connection with the DU of the parent IAB node, which is called a backhaul link.
  • the IAB node can turn on its DU function, and the DU can provide cell services, that is, the DU can provide access services for user equipment (User Equipment, UE).
  • a self-backhaul loop consists of a donor IAB node (or IAB donor), which has a directly connected wired transmission network.
  • the introduction of the IAB system is to solve the situation where the wired transmission network is not deployed in place when the access points are densely deployed, that is, when there is no wired transmission network, the access point can rely on wireless backhaul.
  • the wireless link between the IAB nodes may be referred to as a backhaul (Backhaul, BH) link.
  • the BH link can be configured with a BH Radio Link Control (RLC) channel for wireless backhaul.
  • RLC Radio Link Control
  • a backhaul adaptation protocol Backhaul adaptation protocol, BAP
  • BAP Backhaul adaptation protocol
  • PDU Protocol Data Unit
  • a defined BAP control PDU type is: BH RLF indication.
  • This BH RLF indication may also be referred to as a type-4 (type-4) BH RLF indication.
  • the BH RLF indication can be carried by the BAP control PDU, and an IAB node can use the BAP control PDU to notify its child IAB node that the radio link between the IAB node and its parent IAB node fails to recover.
  • CU represents the central unit (Central Unit). If RLF occurs on the link between IAB node 2 and its parent node IAB node 3, and the RLF recovery fails, then IAB node 2 can report to its child node IAB. Node 1 sends BH RLF indication to inform IAB node 2 and IAB node 3 that there is a problem in the link.
  • Central Unit Central Unit
  • type-2 BH RLF indication When an IAB node fails in the wireless link with its parent IAB node, it can notify the child IAB node of RLF through type-2 BH RLF indication;
  • type-3 BH RLF indication After an IAB node fails the wireless link with its parent IAB node, but the wireless link is successfully recovered, it can notify the child IAB node of the successful RLF recovery through the type-3 BH RLF indication.
  • the "deactivated state" described in this embodiment of the present application may also be referred to as a pending state or a suspended state.
  • the indication that the backhaul link is back to normal in this embodiment of the present application may include at least one of the following: type 3 backhaul RLF indication, a higher layer (eg, RRC layer, RLC layer) of the IAB node sends the message to the medium access control Indication that the backhaul link of the (Medium Access Control, MAC) layer is back to normal.
  • a higher layer eg, RRC layer, RLC layer
  • FIG. 3 is a flowchart of an uplink transmission control method provided by an embodiment of the present application.
  • the method is executed by an IAB node, and the IAB node is a terminal. As shown in FIG. 3, the method includes the following steps:
  • Step 31 The IAB node receives the RLF indication back.
  • the backhaul RLF indication received by the IAB node may be carried by a Backhaul Adaptation Protocol (Backhaul Adaptation Protocol, BAP) control PDU.
  • the returned RLF indication may include any one of the following: type 2 (type-2) return RLF indication, and type 4 (type-4) return RLF indication. That is, the backhaul RLF indication received by the IAB node may be a type-2 backhaul RLF indication, or a type-4 backhaul RLF indication.
  • Step 32 The IAB node cancels or suspends the triggered data transmission.
  • the above-mentioned triggered data transmission may be referred to as triggered uplink data transmission.
  • the above-mentioned triggered data transmission may include at least one of the following: triggered scheduling request (Scheduling Request, SR), triggered buffer status report (Buffer Status Report, BSR), triggered pre-emptive buffer status report (Pre-emptive status report) Buffer Status Report, PBSR), etc.
  • the IAB node after receiving the back RLF indication, can cancel or suspend the triggered data transmission, so as to realize the processing of the triggered data transmission and ensure the data transmission in the IAB network. stability.
  • the returned RLF indication is, for example, type-2/type-4 returned RLF indication, which can be used to cancel or suspend a triggered SR.
  • the IAB node when the IAB node receives the backhaul RLF indication on the backhaul link between its parent IAB node, the IAB node can cancel or suspend the first SR; wherein, the first SR is due to the fact that it is to be sent to the parent IAB
  • the above suspension of the first SR can be understood as deactivating the first SR.
  • the IAB node may stop running the first timer.
  • the first timer is, for example, sr-ProhibitTimer.
  • the IAB node may resume the suspended first SR when receiving an indication that the backhaul link is back to normal.
  • the IAB node may restart the first timer and set the value of the first timer when receiving an indication that the backhaul link is back to normal. is the remaining time value corresponding to when the first timer is suspended, or the value of the first timer is set as the initial value of the timer.
  • the initial value of the timer may be agreed in a protocol or configured by a network side device, etc., which is not limited.
  • the first timer sr-ProhibitTimer is 64ms in total and counts down to 30ms before stopping
  • the uplink resource may be a physical uplink control channel (Physical Uplink Control Channel, PUCCH) resource.
  • PUCCH Physical Uplink Control Channel
  • the RLC control PDU includes, for example, an RLC status report, and the first SR will not be canceled or suspended, that is, not canceled or suspended.
  • the first SR to ensure the sending of the RLC status report.
  • an IAB node receives a type-2 backhaul RLF indication on the backhaul link with its parent IAB node, it can be used for all pending SRs (pending SRs) triggered by BSRs to be sent to the parent IAB node. Cancel, and the respective timer sr-ProhibitTimer for each SR needs to be stopped (if the timer is running).
  • an IAB node receives a type-2 backhaul RLF indication on the backhaul link with its parent IAB node, then for pending SRs triggered by BSRs to be sent to the parent IAB node, suspend/deactivate the pair.
  • the subsequent processing of the pending SRs directly indicates that the operation of processing the pending SRs is stopped, and the timer sr-ProhibitTimer corresponding to each SR needs to be stopped (if the timer is running).
  • an IAB node receives a type-2 return RLF indication on the return link between its parent IAB node
  • the pending SRs triggered by the BSR to be sent to the parent IAB node still follow the traditional legacy Process, that is, waiting to be processed, indirectly indicates deactivation/stopping the operation of processing the pending SRs.
  • the pending SRs will not trigger the RACH process until the IAB node receives the indication that the backhaul link is back to normal.
  • an IAB node receives a type-2 backhaul RLF indication on the backhaul link with its parent IAB node, then for pending SRs triggered by BSRs to be sent to the parent IAB node, the The RACH process will not be triggered until the upper layer's backhaul link is back to normal.
  • the backhaul link that triggers the type-2 backhaul RLF indication does not return to normal, that is, if the backhaul link from the upper layer is received. , indicating that the backhaul link that triggered the type-2 backhaul RLF indication is back to normal.
  • the IAB node After suspending/deactivating pending SRs, if the IAB node receives an indication that the backhaul link from the upper layer is back to normal, it indicates that "the backhaul link that previously received the type-2 backhaul RLF indication has returned to normal.” , you can resume the operation of the previously suspended/deactivated pending SRs, that is, resume the pending SRs that were previously stopped due to the type-2 return RLF indication. And if the timer is triggered before pending SRs, the timer is restarted, and the value of the timer is set to the remaining time corresponding to the timer when it is suspended/deactivated, or set to the initial value of the timer.
  • the IAB node when the IAB node receives the backhaul RLF indication on the backhaul link between its parent IAB node, the IAB node can cancel or suspend the second SR; wherein the second SR is not due to being sent to the parent IAB
  • the suspending of the second SR may also be referred to as deactivating the second SR.
  • the IAB node may stop running the second timer.
  • the second timer is, for example, sr-ProhibitTimer.
  • the IAB node may resume the suspended second SR when receiving an indication that the backhaul link is back to normal.
  • the IAB node may restart the second timer and set the value of the second timer when receiving an indication that the backhaul link is back to normal. is the remaining time value corresponding to when the second timer is suspended, or the value of the second timer is set as the initial value of the timer.
  • the initial value of the timer may be agreed in a protocol or configured by a network side device, etc., which is not limited.
  • the second timer sr-ProhibitTimer is 32ms in total and counts down to 20ms before it stops running
  • an IAB node receives a type-2 backhaul RLF indication on the backhaul link with its parent IAB node, it can cancel all pending SRs that are not triggered by BSRs to be sent to the parent IAB node, and each An SR's respective timer sr-ProhibitTimer needs to be stopped (if the timer is running).
  • an IAB node receives a type-2 backhaul RLF indication on the backhaul link between its parent IAB node, then for those pending SRs that are not triggered by the BSR to be sent to the parent IAB node, after receiving Before returning an indication that the link is back to normal, the subsequent processing of the pending SRs is suspended/deactivated, and the respective timer sr-ProhibitTimer corresponding to each SR needs to be stopped (if the timer is running).
  • the IAB node After suspending/deactivating pending SRs, if the IAB node receives an indication that the backhaul link from the upper layer is back to normal, it indicates that "the backhaul link that previously received the type-2 backhaul RLF indication has returned to normal.” , you can resume the operation of the previously suspended/deactivated pending SRs, that is, resume the pending SRs that were previously stopped due to the type-2 return RLF indication. And if the timer is triggered before the pending SRs, the timer is restarted, and the value of the timer is set to the remaining time corresponding to the timer when it is suspended/deactivated, or is set to the initial value of the timer.
  • the above-mentioned indication that the backhaul link is back to normal may include at least one of the following: type-3 backhaul RLF indication, an indication that the backhaul link is back to normal sent by the upper layer of the IAB node to the MAC layer.
  • type-3 backhaul RLF indication an indication that the backhaul link is back to normal sent by the upper layer of the IAB node to the MAC layer.
  • the upper layer performs an inter-layer indication to inform the MAC layer that the backhaul link has returned to normal.
  • the triggered SR is processed according to the legacy process.
  • the returned RLF indication is, for example, type-2/type-4 returned RLF indication, which can be used to cancel or suspend a triggered BSR.
  • the IAB node when the IAB node receives the backhaul RLF indication on the backhaul link between its parent IAB node, the IAB node can cancel or suspend the first BSR.
  • the first BSR is a BSR that is determined based on the BSR process and will be triggered but not cancelled.
  • the suspending of the first BSR may also be referred to as deactivating the first BSR.
  • the first BSR may be a regular (regular) BSR, or may be a periodic (periodic) BSR.
  • regular BSR if no type-2 return RLF indication is received, it will be processed according to the legacy process.
  • type-2 return RLF indication is received and the type-3 return RLF indication is not received, it means that the regular BSR is still in the inactive state and cannot trigger SR; If the RLF indication is sent and the RLF indication is returned by type-3, it means that the regular BSR has returned to normal and the SR can be triggered.
  • the padding BSR is in the case that the uplink grant (UL grant) is redundant, the UE uses the remaining bits to report the BSR situation to the network side device. Therefore, the padding BSR occurs only when there is a surplus of resources. , there is no need to cancel the padding BSR. Therefore, when the first BSR is a padding BSR, the first BSR will not be cancelled or suspended.
  • the IAB node may stop running the third timer.
  • the third timer is a retransmission timer, such as retxBSR-Timer.
  • the third timer is a periodic timer, such as periodicBSR-Timer.
  • the IAB node may resume the suspended first BSR when receiving an indication that the backhaul link is back to normal.
  • the IAB node can restart the third timer and set the value of the third timer. is the remaining time value corresponding to when the third timer is suspended, or the value of the third timer is set as the initial value of the timer.
  • the initial value of the timer may be agreed in a protocol or configured by a network side device, etc., which is not limited.
  • the third timer retxBSR-Timer has a total of 10 subframes and counts down to 5 subframes before it stops running
  • the above-mentioned indication that the backhaul link is back to normal may include at least one of the following: type-3 backhaul RLF indication, an indication that the backhaul link is back to normal sent by the upper layer of the IAB node to the MAC layer.
  • type-3 backhaul RLF indication an indication that the backhaul link is back to normal sent by the upper layer of the IAB node to the MAC layer.
  • the upper layer performs an inter-layer indication to inform the MAC layer that the backhaul link has returned to normal.
  • the RLC control PDU includes, for example, an RLC status report
  • the first BSR will not be canceled or suspended, that is, the first SR will not be canceled or suspended, so as to Guarantees the sending of RLC status reports.
  • the IAB node can stop triggering the new BSR, and/or stop triggering the new SR; or, under the condition that triggers the BSR, the IAB node can trigger the new BSR, And the triggered BSR is determined to be in a suspended state/pending state.
  • the condition for triggering the BSR may be at least one of the following: the logical channel priority of the newly arrived uplink data is higher than the logical channel priority of any logical channel group in the uplink data buffered by the UE; Before there is any buffered upstream data, etc.
  • an IAB node receives a type-2 backhaul RLF indication on the backhaul link with its parent IAB node, and the BSR procedure determines that at least one BSR will be triggered and not cancelled, it can cancel the At least one BSR.
  • the IAB node After the IAB node receives the type-2 return RLF indication, it can still trigger a new BSR, but the BSR will be re-determined as deactivated/suspended, that is, the processing of the BSR will stop. Specifically, if the IAB node receives the type-2 backhaul RLF indication on the backhaul link with its parent IAB node, and has not received any indication from the upper layers, the link where the RLF occurred has returned to normal , and the BSR procedure determines that at least one BSR will be triggered and not cancelled, then: 1) Determine that at least one BSR is a deactivated/suspended BSR, that is, stop the operation on at least one BSR, and stop the corresponding retxBSR-Timer Or periodicaBSR-Timer (if the timer is running); 2) Optionally, no SR will be triggered.
  • the IAB node After suspending/deactivating the BSR, if the IAB node receives an indication that the backhaul link of the upper layer is back to normal, that is, it indicates that "the backhaul link that received the type-2 backhaul RLF indication has returned to normal", Then, the operation of the previously suspended/deactivated BSR can be resumed, that is, the operation of the BSR that was stopped due to receiving the type-2 return RLF indication can be resumed. And if the timer is triggered before the BSR, the timer corresponding to the BSR is restarted, and the value of the timer is set to the remaining time corresponding to the timer when it is deactivated, or to the initial value of the timer.
  • the returned RLF indication is, for example, type-2/type-4 returned RLF indication, which can be used to cancel or suspend the triggered PBSR.
  • the IAB node when the IAB node receives the backhaul RLF indication on the backhaul link between its parent IAB node, the IAB node can cancel or suspend the first PBSR.
  • the first PBSR is a PBSR that is determined based on the PBSR process and will be triggered and not cancelled.
  • the suspending of the first PBSR may also be referred to as deactivating the first PBSR.
  • the IAB node can resume the suspended first PBSR when receiving an indication that the backhaul link is back to normal.
  • the above-mentioned indication that the backhaul link is back to normal may include at least one of the following: type-3 backhaul RLF indication, an indication that the backhaul link is back to normal sent by the upper layer of the IAB node to the MAC layer.
  • type-3 backhaul RLF indication an indication that the backhaul link is back to normal sent by the upper layer of the IAB node to the MAC layer.
  • the upper layer performs inter-layer indication to inform the MAC layer that the backhaul link has returned to normal.
  • an IAB node receives a type-2 backhaul RLF indication on the backhaul link with its parent IAB node, and the PBSR procedure determines that at least one PBSR will be triggered and not cancelled, the at least one PBSR can be cancelled .
  • an IAB node receives a type-2 backhaul RLF indication on the backhaul link with its parent IAB node, it stops triggering a new PBSR, and processes the already-triggered PBSR in accordance with the existing process.
  • the IAB node after the IAB node receives the type-2 return RLF indication, it can still trigger a new PBSR, but the PBSR will be re-determined as deactivated/suspended, that is, the processing of the PBSR will stop.
  • the IAB node receives the type-2 backhaul RLF indication on the backhaul link with its parent IAB node, and has not received any indication from the upper layers, the link where the RLF occurred has returned to normal , and the PBSR procedure determines that at least one PBSR will be triggered and not cancelled, then: 1) determine that the at least one PBSR is a deactivated/suspended PBSR, that is, stop the operation of the at least one PBSR; 2) optionally , will not trigger any SR.
  • the IAB node After suspending/deactivating PBSR, if the IAB node receives an indication that the backhaul link from the upper layer is back to normal, that is, it indicates that "the backhaul link that received the type-2 backhaul RLF indication has returned to normal", Then the operation of the previously suspended/deactivated PBSR can be resumed, that is, the operation of the PBSR that was stopped due to the receipt of the type-2 return RLF indication can be resumed.
  • the second BSR will not be canceled after being triggered Or pause to ensure the sending of RLC status reports.
  • the SR corresponding to the second BSR is triggered when the resource size of the uplink grant (UL grant) of the IAB node is smaller than the resource size occupied by the second BSR, the SR corresponding to the second BSR is not triggered after being triggered. will be cancelled or suspended.
  • the RLC layer interacts with the MAC layer, informs the MAC layer that the current data to be transmitted includes the RLC Control PDU, and triggers the sending of the BSR, the triggered BSR will not be cancelled in all subsequent operations/ Pause; and when the BSR is sent, if the size of the UL grant is insufficient to accommodate the sum of the BSR MAC Control Element (CE) and its subheader (header), for example, according to the Logical Channel Prioritization (LCP) criterion
  • LCP Logical Channel Prioritization
  • the RLC Control PDU of the IAB node can only be transmitted through the first logical channel (Logical Channel, LCH), and when the data to be transmitted that triggers the third BSR includes the data to be transmitted in the first LCH, the third BSR After being triggered, it will not be canceled or paused. That is, if it is stipulated that the RLC Control PDU can only be transmitted through a specific LCH, when the data to be transmitted that triggers the BSR contains the data to be transmitted by the LCH, the BSR will not be cancelled/suspended in all subsequent operations .
  • LCH Logical Channel
  • the LCH corresponding to the third SR to be processed is the LCH used to transmit the RLC Control PDU, and/or, when the third BSR that triggers the third SR includes the data to be sent in the first LCH, the third SR will not be cancelled or suspended.
  • the processing of the uplink transmission permission by the IAB node may include at least one of the following:
  • the IAB node ignores the preconfigured uplink transmission license, that is, does not use the preconfigured uplink transmission license for uplink data transmission;
  • the IAB node uses the preconfigured uplink transmission license to transmit the RLC control PDU, that is, the preconfigured uplink transmission license can still be used to transmit the RLC control PDU;
  • the IAB node deactivates the preconfigured uplink transmission permission.
  • the IAB node can restore the preconfigured uplink transmission permission when the received backhaul link returns to normal indication, or the IAB node can be based on the parent IAB node of the IAB node. , activate the pre-configured uplink transmission license to use the pre-configured uplink transmission license for uplink data transmission.
  • the above-mentioned deactivation of the preconfigured uplink transmission permission means that the preconfigured uplink transmission permission is temporarily ignored.
  • the network side configures a series of/periodic Configuration Grant (CG) to the UE, and then the UE can directly transmit data on the time-frequency resource (CG) configured in advance by the network side; the meaning of "deactivation" here
  • CG time-frequency resource
  • the UE can send data on the CG, but because it has received the return RLF indication, it does not transmit data at the time of the CG, but waits until the return chain of the RLF After the road is restored successfully, CG is used for data transmission.
  • the restoration of the preconfigured uplink transmission permission by the IAB node means that the preconfigured uplink transmission permission is not ignored, that is, the preconfigured uplink transmission permission is used for data transmission.
  • the execution subject may be an uplink transmission control apparatus, or a control module in the uplink transmission control apparatus for executing the uplink transmission control method.
  • a method for controlling uplink transmission performed by an apparatus for controlling uplink transmission is taken as an example to describe the apparatus for controlling uplink transmission provided by the embodiments of the present application.
  • FIG. 4 is a schematic structural diagram of an uplink transmission control device provided by an embodiment of the present application.
  • the device is applied to an IAB node, and the IAB node is a terminal.
  • the uplink transmission control device 40 includes:
  • the receiving module 41 is used to receive and return the RLF indication
  • the processing module 42 is configured to cancel or suspend the triggered data transmission.
  • the control device for uplink transmission can cancel or suspend the triggered data transmission after receiving the back RLF indication, so as to realize the processing of the triggered data transmission and ensure the stability of data transmission in the IAB network. .
  • the triggered data transmission includes at least one of the following:
  • the returned RLF indication includes any one of the following: type 2 return RLF indication, type 4 return RLF indication.
  • processing module 42 is further configured to execute any one of the following:
  • the IAB node When the IAB node receives the backhaul RLF indication on the backhaul link with the parent IAB node of the IAB node, cancel or suspend the first SR; wherein, the first SR is due to sending the pending SR triggered by the BSR of the parent IAB node;
  • the IAB node When the IAB node receives the backhaul RLF indication on the backhaul link with the parent IAB node of the IAB node, cancel or suspend the second SR; wherein the second SR is not due to be sent The pending SR triggered by the BSR of the parent IAB node.
  • the first SR will not perform the operation until the IAB node receives the instruction that the backhaul link is back to normal. Trigger the RACH process.
  • processing module 42 is also used for:
  • processing module 42 is also used for:
  • the first SR when the data to be sent that triggers the BSR includes an RLC control PDU, the first SR will not be canceled or suspended.
  • processing module 42 is also used for:
  • the suspended first SR is resumed when an indication that the backhaul link is back to normal is received.
  • processing module 42 is also used for:
  • the suspended second SR is resumed when an indication that the backhaul link is back to normal is received.
  • processing module 42 is also used for:
  • processing module 42 is also used for:
  • processing module 42 is also used for:
  • the IAB node When the IAB node receives the backhaul RLF indication on the backhaul link with the parent IAB node of the IAB node, cancel or suspend the first BSR; wherein, the first BSR is based on the BSR process Determined will be triggered and there is no canceled BSR.
  • the first BSR when the first BSR is a BSR, the first BSR will not be cancelled or suspended.
  • processing module 42 is also used for:
  • the first BSR when the data to be sent that triggers the first BSR includes an RLC control PDU, the first BSR will not be canceled or suspended.
  • processing module 42 is also used for:
  • the suspended first BSR After suspending the first BSR, when receiving an indication that the backhaul link is back to normal, the suspended first BSR is resumed.
  • processing module 42 is also used for:
  • processing module 42 is also used for:
  • the IAB node When the IAB node receives the backhaul RLF indication on the backhaul link with the parent IAB node of the IAB node, cancel or suspend the first PBSR; wherein, the first PBSR is based on the PBSR process The determined PBSR will be triggered and not cancelled.
  • processing module 42 is also used for:
  • the suspended first PBSR is resumed when an indication that the backhaul link is back to normal is received.
  • the indication that the backhaul link is back to normal includes at least one of the following:
  • Type 3 returns RLF indication
  • the upper layer of the IAB node sends an indication to the MAC layer that the backhaul link is back to normal.
  • processing module 42 is also used for:
  • a new BSR is triggered, and the triggered BSR is determined to be in a suspended state.
  • the RLC layer of the IAB node indicates that the data to be transmitted by the MAC layer includes an RLC Control PDU, and the data to be transmitted triggers a second BSR, the second BSR will not be cancelled after being triggered. Or pause.
  • the SR corresponding to the second BSR is triggered when the resource size of the uplink grant of the IAB node is smaller than the resource size occupied by the second BSR, the SR corresponding to the second BSR is Once triggered, it will not be canceled or suspended.
  • the RLC Control PDU of the IAB node can only be transmitted through the first logical channel LCH, and when the data to be transmitted that triggers the third BSR includes the data to be transmitted in the first LCH, the third After the BSR is triggered, it will not be cancelled or suspended;
  • the LCH corresponding to the third SR to be processed is the LCH used to transmit the RLC Control PDU, and/or when the third BSR triggering the third SR includes the data to be sent in the first LCH, the Three SRs will not be cancelled or suspended.
  • processing module 42 is also used for:
  • the transmission of the RLC control PDU is performed by using a preconfigured uplink transmission license
  • processing module 42 is also used for:
  • the control apparatus for uplink transmission in this embodiment of the present application may be an apparatus, an apparatus having an operating system or an electronic device, or may be a component, an integrated circuit, or a chip in a terminal.
  • the apparatus or electronic device may be a mobile terminal or a non-mobile terminal.
  • the mobile terminal may include but is not limited to the types of terminals 11 listed above, and the non-mobile terminal may be a server, a network attached storage (Network Attached Storage, NAS), a personal computer (Personal Computer, PC), a television ( Television, TV), teller machine, or self-service machine, etc., which are not specifically limited in the embodiments of the present application.
  • the uplink transmission control apparatus provided in the embodiment of the present application can implement each process implemented by the method embodiment in FIG. 3 , and achieve the same technical effect. To avoid repetition, details are not repeated here.
  • an embodiment of the present application further provides a terminal 500 , where the terminal 500 is an IAB node, and includes a processor 501 and a memory 502 , which are stored on the memory 502 and can be stored on the processor 501
  • the running program or instruction when the program or instruction is executed by the processor 501, implements each process of the above-mentioned embodiments of the uplink transmission control method, and can achieve the same technical effect. To avoid repetition, details are not repeated here.
  • the embodiment of the present application also provides a terminal, where the terminal is an IAB node, and includes a processor and a communication interface, where the communication interface is used to receive and return an RLF indication, and the processor is used to cancel or suspend the triggered data transmission.
  • This terminal embodiment corresponds to the above-mentioned method embodiment shown in FIG. 3 , and each implementation process and implementation manner of the above-mentioned method embodiment can be applied to this terminal embodiment, and can achieve the same technical effect.
  • FIG. 6 is a schematic diagram of a hardware structure of a terminal implementing an embodiment of the present application.
  • the terminal 600 is an IAB node, including but not limited to: a radio frequency unit 601, a network module 602, an audio output unit 603, an input unit 604, a sensor 605, a display unit 606, a user input unit 607, an interface unit 608, a memory 609, and a processing at least some of the components in the device 610 and the like.
  • the terminal 600 may also include a power source (such as a battery) for supplying power to various components, and the power source may be logically connected to the processor 610 through a power management system, so as to manage charging, discharging, and power consumption through the power management system management and other functions.
  • a power source such as a battery
  • the terminal structure shown in FIG. 6 does not constitute a limitation on the terminal, and the terminal may include more or less components than shown, or combine some components, or arrange different components, which will not be repeated here.
  • the input unit 604 may include a graphics processor (Graphics Processing Unit, GPU) 6041 and a microphone 6042. Such as camera) to obtain still pictures or video image data for processing.
  • the display unit 606 may include a display panel 6061, which may be configured in the form of a liquid crystal display, an organic light emitting diode, or the like.
  • the user input unit 607 includes a touch panel 6071 and other input devices 6072 .
  • the touch panel 6071 is also called a touch screen.
  • the touch panel 6071 may include two parts, a touch detection device and a touch controller.
  • Other input devices 6072 may include, but are not limited to, physical keyboards, function keys (such as volume control keys, switch keys, etc.), trackballs, mice, and joysticks, which are not described herein again.
  • the radio frequency unit 601 receives the downlink data from the network side device, and then processes it to the processor 610; in addition, sends the uplink data to the network side device.
  • the radio frequency unit 601 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like.
  • Memory 609 may be used to store software programs or instructions as well as various data.
  • the memory 609 may mainly include a stored program or instruction area and a storage data area, wherein the stored program or instruction area may store an operating system, an application program or instruction required for at least one function (such as a sound playback function, an image playback function, etc.) and the like.
  • the memory 609 may include a high-speed random access memory, and may also include a non-volatile memory, wherein the non-volatile memory may be a read-only memory (Read-Only Memory, ROM), a programmable read-only memory (Programmable ROM) , PROM), erasable programmable read-only memory (Erasable PROM, EPROM), electrically erasable programmable read-only memory (Electrically EPROM, EEPROM) or flash memory.
  • ROM Read-Only Memory
  • PROM programmable read-only memory
  • PROM erasable programmable read-only memory
  • Erasable PROM Erasable PROM
  • EPROM electrically erasable programmable read-only memory
  • EEPROM electrically erasable programmable read-only memory
  • flash memory for example at least one magnetic disk storage device, flash memory device, or other non-volatile solid state storage device.
  • the processor 610 may include one or more processing units; optionally, the processor 610 may integrate an application processor and a modem processor, wherein the application processor mainly processes the operating system, user interface, and application programs or instructions, etc. Modem processors mainly deal with wireless communications, such as baseband processors. It can be understood that, the above-mentioned modulation and demodulation processor may not be integrated into the processor 610.
  • the radio frequency unit 601 is used for: receiving and returning RLF indication;
  • the processor 610 is configured to cancel or suspend the triggered data transmission.
  • the triggered data transmission after receiving the back RLF indication, the triggered data transmission can be cancelled or suspended, thereby realizing the processing of the triggered data transmission and ensuring the stability of data transmission in the IAB network.
  • the triggered data transmission includes at least one of the following:
  • the returned RLF indication includes any one of the following: type 2 return RLF indication, type 4 return RLF indication.
  • processor 610 is further configured to execute any one of the following:
  • the terminal 600 When the terminal 600 receives the backhaul RLF indication on the backhaul link with the parent IAB node of the terminal 600, it cancels or suspends the first SR; wherein, the first SR is to be sent to the parent The pending SR triggered by the BSR of the IAB node;
  • the terminal 600 When the terminal 600 receives the backhaul RLF indication on the backhaul link with the parent IAB node of the terminal 600, it cancels or suspends the second SR; wherein the second SR is not due to be sent to the parent The pending SR triggered by the BSR of the IAB node.
  • the first SR will not trigger the RACH process until the terminal 600 receives an indication that the backhaul link is back to normal.
  • processor 610 is further configured to:
  • processor 610 is further configured to:
  • the first SR when the data to be sent that triggers the BSR includes an RLC control PDU, the first SR will not be canceled or suspended.
  • processor 610 is further configured to:
  • the suspended first SR is resumed when an indication that the backhaul link is back to normal is received.
  • processor 610 is further configured to:
  • the suspended second SR is resumed when an indication that the backhaul link is back to normal is received.
  • processor 610 is further configured to:
  • processor 610 is further configured to:
  • processor 610 is further configured to:
  • the terminal 600 When the terminal 600 receives the backhaul RLF indication on the backhaul link with the parent IAB node of the terminal 600, it cancels or suspends the first BSR; wherein, the first BSR is determined based on the BSR process and will be Triggered and not cancelled BSR.
  • the first BSR when the first BSR is a BSR, the first BSR will not be cancelled or suspended.
  • processor 610 is further configured to:
  • the first BSR when the data to be sent that triggers the first BSR includes an RLC control PDU, the first BSR will not be canceled or suspended.
  • processor 610 is further configured to:
  • the suspended first BSR After suspending the first BSR, when receiving an indication that the backhaul link is back to normal, the suspended first BSR is resumed.
  • processor 610 is further configured to:
  • processor 610 is further configured to:
  • the terminal 600 When the terminal 600 receives the backhaul RLF indication on the backhaul link with the parent IAB node of the terminal 600, it cancels or suspends the first PBSR; wherein, the first PBSR is determined based on the PBSR process and will be PBSR that fires and is not canceled.
  • processor 610 is further configured to:
  • the suspended first PBSR is resumed when an indication that the backhaul link is back to normal is received.
  • the indication that the backhaul link is back to normal includes at least one of the following:
  • Type 3 returns RLF indication
  • the upper layer of the terminal 600 sends an indication to the MAC layer that the backhaul link is back to normal.
  • processor 610 is further configured to:
  • a new BSR is triggered, and the triggered BSR is determined to be in a suspended state.
  • the RLC layer of the terminal 600 indicates that the data to be transmitted by the MAC layer includes an RLC Control PDU, and the data to be transmitted triggers a second BSR, the second BSR will not be canceled or suspended after being triggered. .
  • the SR corresponding to the second BSR is triggered when the resource size of the uplink grant of the terminal 600 is smaller than the resource size occupied by the second BSR, the SR corresponding to the second BSR is triggered will not be canceled or suspended.
  • the RLC Control PDU of the terminal 600 can only be transmitted through the first logical channel LCH, and when the data to be transmitted that triggers the third BSR includes the data to be transmitted in the first LCH, the third BSR is After being triggered, it will not be canceled or suspended;
  • the LCH corresponding to the third SR to be processed is the LCH used to transmit the RLC Control PDU, and/or when the third BSR triggering the third SR includes the data to be sent in the first LCH, the Three SRs will not be cancelled or suspended.
  • processor 610 is further configured to:
  • the transmission of the RLC control PDU is performed by using a preconfigured uplink transmission license
  • processor 610 is further configured to:
  • the embodiments of the present application further provide a readable storage medium, the readable storage medium may be non-volatile or volatile, and a program or an instruction is stored on the readable storage medium, and the program or instruction is stored in the readable storage medium.
  • the processor executes, each process of the method embodiment shown in FIG. 3 is implemented, and the same technical effect can be achieved. To avoid repetition, details are not repeated here.
  • the processor is the processor in the terminal described in the foregoing embodiment.
  • the readable storage medium includes a computer-readable storage medium, such as a computer read-only memory (Read-Only Memory, ROM), a random access memory (Random Access Memory, RAM), a magnetic disk or an optical disk, and the like.
  • An embodiment of the present application further provides a chip, where the chip includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is configured to run a program or an instruction to implement the method shown in FIG. 3 above. In order to avoid repetition, the details are not repeated here.
  • the chip mentioned in the embodiments of the present application may also be referred to as a system-on-chip, a system-on-chip, a system-on-chip, or a system-on-a-chip, or the like.
  • An embodiment of the present application further provides a computer program product, where the computer program product is stored in a non-transitory storage medium, and the computer program product is executed by at least one processor to implement the above method embodiment shown in FIG. 3 .
  • Each process can achieve the same technical effect. In order to avoid repetition, it will not be repeated here.
  • the disclosed apparatus and method may be implemented in other manners.
  • the apparatus embodiments described above are only illustrative.
  • the division of the units is only a logical function division. In actual implementation, there may be other division methods.
  • multiple units or components may be combined or Can be integrated into another system, or some features can be ignored, or not implemented.
  • the shown or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, indirect coupling or communication connection of devices or units, and may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution in this embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit.
  • the functions, if implemented in the form of software functional units and sold or used as independent products, may be stored in a computer-readable storage medium.
  • the technical solution of the present application can be embodied in the form of a software product in essence, or the part that contributes to the related technology or the part of the technical solution.
  • the computer software product is stored in a storage medium, including several
  • the instructions are used to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present application.
  • the aforementioned storage medium includes: a U disk, a removable hard disk, a ROM, a RAM, a magnetic disk, or an optical disk and other mediums that can store program codes.

Landscapes

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

Abstract

本申请公开了一种上行传输的控制方法、装置及终端，属于通信技术领域，本申请实施例的上行传输的控制方法包括：IAB节点接收回传无线链路失败指示RLF indication；所述IAB节点取消或者暂停已触发的数据发送。

Description

上行传输的控制方法、装置及终端
相关申请的交叉引用
本申请主张在2021年03月25日在中国提交的中国专利申请No.202110321993.2的优先权，其全部内容通过引用包含于此。
技术领域
本申请属于通信技术领域，具体涉及一种上行传输的控制方法、装置及终端。
背景技术
在集成接入回传(Integrated Access Backhaul，IAB)网络中，当某IAB节点接收到其父IAB节点向该IAB节点发送的回传(Backhaul)无线链路失败(Radio Link Failure，RLF)指示(indication)时，会触发该IAB节点的进一步的行为。然而在此情况下，目前尚未确定如何对该IAB节点的已触发的数据发送进行处理。
发明内容
本申请实施例提供一种上行传输的控制方法、装置及终端，能够解决IAB节点在接收到回传RLF indication时，如何对已触发的数据发送进行处理的问题。
第一方面，提供了一种上行传输的控制方法，包括：
IAB节点接收回传RLF indication；
所述IAB节点取消或者暂停已触发的数据发送。
第二方面，提供了一种上行传输的控制装置，包括：
接收模块，用于接收回传RLF indication；
处理模块，用于取消或者暂停已触发的数据发送。
第三方面，提供了一种终端，该终端为IAB节点，包括处理器、存储器 及存储在所述存储器上并可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如第一方面所述的方法的步骤。
第四方面，提供了一种终端，该终端为IAB节点，包括处理器及通信接口，其中，所述通信接口用于接收回传RLF indication，所述处理器用于取消或者暂停已触发的数据发送。
第五方面，提供了一种可读存储介质，所述可读存储介质上存储程序或指令，所述程序或指令被处理器执行时实现如第一方面所述的方法的步骤。
第六方面，提供了一种芯片，所述芯片包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行程序或指令，实现如第一方面所述的方法。
第七方面，提供了一种计算机程序/程序产品，所述计算机程序/程序产品被存储在非瞬态的存储介质中，所述程序/程序产品被至少一个处理器执行以实现如第一方面所述方法的步骤。
在本申请实施例中，IAB节点在接收回传RLF indication之后，可以取消或者暂停已触发的数据发送，从而实现对已触发的数据发送的处理，保证IAB网络中数据传输的稳定性。
附图说明
图1是本申请实施例可应用的一种无线通信系统的框图；
图2是本申请实施例中IAB系统的示意图；
图3是本申请实施例提供的一种上行传输的控制方法的流程图；
图4是本申请实施例提供的一种上行传输的控制装置的结构示意图；
图5是本申请实施例提供的一种终端的结构示意图；
图6是本申请实施例提供的另一种终端的结构示意图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行 清楚描述，显然，所描述的实施例是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员所获得的所有其他实施例，都属于本申请保护的范围。
本申请的说明书和权利要求书中的术语“第一”、“第二”等是用于区别类似的对象，而不用于描述特定的顺序或先后次序。应该理解这样使用的术语在适当情况下可以互换，以便本申请的实施例能够以除了在这里图示或描述的那些以外的顺序实施，且“第一”、“第二”所区别的对象通常为一类，并不限定对象的个数，例如第一对象可以是一个，也可以是多个。此外，说明书以及权利要求中“和/或”表示所连接对象的至少其中之一，字符“/”一般表示前后关联对象是一种“或”的关系。
值得指出的是，本申请实施例所描述的技术不限于长期演进型(Long Term Evolution，LTE)/LTE的演进(LTE-Advanced，LTE-A)系统，还可用于其他无线通信系统，诸如码分多址(Code Division Multiple Access，CDMA)、时分多址(Time Division Multiple Access，TDMA)、频分多址(Frequency Division Multiple Access，FDMA)、正交频分多址(Orthogonal Frequency Division Multiple Access，OFDMA)、单载波频分多址(Single-carrier Frequency-Division Multiple Access，SC-FDMA)和其他系统。本申请实施例中的术语“系统”和“网络”常被可互换地使用，所描述的技术既可用于以上提及的系统和无线电技术，也可用于其他系统和无线电技术。以下描述出于示例目的描述了新空口(New Radio，NR)系统，并且在以下大部分描述中使用NR术语，但是这些技术也可应用于NR系统应用以外的应用，如第6代(6 th Generation，6G)通信系统。
图1示出本申请实施例可应用的一种无线通信系统的框图。无线通信系统包括终端11和网络侧设备12。其中，终端11也可以称作终端设备或者用户设备(User Equipment，UE)，终端11可以是手机、平板电脑(Tablet Personal Computer)、膝上型电脑(Laptop Computer)或称为笔记本电脑、个人数字助理(Personal Digital Assistant，PDA)、掌上电脑、上网本、超级移动个人计 算机(Ultra-Mobile Personal Computer，UMPC)、移动上网装置(Mobile Internet Device，MID)、可穿戴式设备(Wearable Device)或车载设备(Vehicle User Equipment，VUE)、行人终端(Pedestrian User Equipment，PUE)等终端侧设备，可穿戴式设备包括：智能手表、手环、耳机、眼镜等。需要说明的是，在本申请实施例并不限定终端11的具体类型。网络侧设备12可以是基站或核心网，其中，基站可被称为节点B、演进节点B、接入点、基收发机站(Base Transceiver Station，BTS)、无线电基站、无线电收发机、基本服务集(Basic Service Set，BSS)、扩展服务集(Extended Service Set，ESS)、B节点、演进型B节点(eNB)、家用B节点、家用演进型B节点、无线局域网(Wireless Local Area Network，WLAN)接入点、WiFi节点、发送接收点(Transmitting Receiving Point，TRP)或所述领域中其他某个合适的术语，只要达到相同的技术效果，所述基站不限于特定技术词汇，需要说明的是，在本申请实施例中仅以NR系统中的基站为例，但是并不限定基站的具体类型。
为了便于理解本申请实施例，首先说明以下内容。
请参见图2，图2示出本申请实施例中一个IAB系统的示意图。在IAB系统中，一个IAB节点包括分布单元(Distributed Unit，DU)功能部分和移动终端(Mobile Termination，MT)功能部分，依靠MT功能部分，该IAB节点可以找到一个父IAB节点(parent IAB node)，并与父IAB节点的DU建立无线连接，该无线连接被称为回传链路(backhaul link)。在一个IAB节点建立完整的回传链路后，该IAB节点可以打开其DU功能，DU会提供小区服务，即DU可以为用户设备(User Equipment，UE)提供接入服务。一个自回传回路包含一个施主donor IAB节点(或者称为IAB donor)，donor IAB节点有直接相连的有线传输网。
本申请实施例中，IAB系统的引入是为了解决接入点密集部署时，有线传输网部署不到位的情况，即在没有有线传输网络时，接入点可以依赖无线回传。
可选地，IAB节点之间的无线链路可称为回传(Backhaul，BH)链路link。 BH link上可以配置有BH无线链路控制(Radio Link Control，RLC)信道进行无线回传。
本申请实施例中，回传自适应协议(Backhaul adaptation protocol，BAP)控制control协议数据单元(Protocol Data Unit，PDU)用来承载BAP层的控制信息。其中，一种已定义的BAP control PDU类型为：BH RLF indication。该BH RLF indication也可称为类型4(type-4)BH RLF indication。该BH RLF indication可由BAP control PDU承载，一个IAB节点可以利用BAP control PDU通知其子IAB节点该IAB节点与其父IAB节点之间无线链路恢复失败的消息。
例如，假设IAB网络拓扑结构为：
IAB节点1->IAB节点2->IAB节点3->IAB-donor-DU->IAB-donor-CU
其中，CU表示集中单元(Central Unit)，若IAB节点2与其父节点IAB节点3之间的链路发生了RLF，且进行RLF恢复(recovery)失败了，则IAB节点2可以向其子节点IAB节点1发送BH RLF indication，用于告知IAB节点2与IAB节点3之间的链路出现问题。
此外，还存在两种BAP control PDU类型：
1)type-2 BH RLF indication：一个IAB节点在与其父IAB节点的无线链路发生失败，可以通过type-2 BH RLF indication向子IAB节点通知RLF；
2)type-3 BH RLF indication：一个IAB节点在与其父IAB节点的无线链路失败后，但无线链路恢复成功，可以通过type-3 BH RLF indication向子IAB节点通知RLF恢复成功。
可选地，本申请实施例中所描述的“去激活态”，也可以称为待处理(pending)态或暂停态。
可选地，本申请实施例中的回传链路恢复正常的指示可以包括以下至少一项：类型3回传RLF indication、IAB节点的高层(如RRC层、RLC层)发送给媒体接入控制(Medium Access Control，MAC)层的回传链路恢复正常的指示。
下面结合附图，通过一些实施例及其应用场景对本申请实施例提供的上行传输的控制方法进行详细地说明。
请参见图3，图3是本申请实施例提供的一种上行传输的控制方法的流程图，该方法由IAB节点执行，该IAB节点为终端，如图3所示，该方法包括以下步骤：
步骤31：IAB节点接收回传RLF indication。
可选地，IAB节点接收的回传RLF indication可以由回传适配协议(Backhaul Adaptation Protocol，BAP)control PDU承载。该回传RLF indication可以包括以下任意一项：类型2(type-2)回传RLF indication、类型4(type-4)回传RLF indication。即，IAB节点接收的回传RLF indication可以是type-2回传RLF indication，也可以是type-4回传RLF indication。
步骤32：IAB节点取消或者暂停已触发的数据发送。
可选地，上述已触发的数据发送可以称为已触发的上行数据发送。上述已触发的数据发送可以包括以下至少一项：已触发的调度请求(Scheduling Request，SR)、已触发的缓冲状态报告(Buffer Status Report，BSR)、已触发的抢先缓冲状态报告(Pre-emptive Buffer Status Report，PBSR)等。
本申请实施例的上行传输的控制方法，IAB节点在接收到回传RLF indication之后，可以取消或者暂停已触发的数据发送，从而实现对已触发的数据发送的处理，保证IAB网络中数据传输的稳定性。
下面分别以SR、BSR和PBSR为例，对本申请进行详细说明。
(1)基于回传RLF indication处理触发的SR
本申请实施例中，回传RLF indication比如为type-2/type-4回传RLF indication，可以用于取消或者暂停已触发的SR。
可选地，当IAB节点在与其父IAB节点间的回传链路上接收到回传RLF indication时，该IAB节点可以取消或者暂停第一SR；其中，第一SR是由于要发送给父IAB节点的BSR而触发的待处理SR。上述暂停第一SR可理解为去激活第一SR。
进一步的，在取消或者暂停第一SR时，当第一SR对应的第一定时器在运行时，IAB节点可以停止运行第一定时器。该第一定时器比如为sr-ProhibitTimer。
进一步的，在暂停第一SR之后，当接收到回传链路恢复正常的指示时，IAB节点可以恢复暂停的第一SR。
进一步的，在暂停第一SR，且停止运行第一定时器之后，当接收到回传链路恢复正常的指示时，IAB节点可以重新启动第一定时器，并将第一定时器的值设置为第一定时器被暂停时所对应的剩余时间值，或者，将第一定时器的值设置为计时器初始值。其中，该计时器初始值可以协议约定或者网络侧设备配置等，对此不进行限制。
比如，假设第一定时器sr-ProhibitTimer总共是64ms，停止运行前倒计时到30ms，则停止之后恢复具有2种情况：1)将sr-ProhibitTimer的值设置为64ms，重新从64ms倒计时；2)将sr-ProhibitTimer的值设置为30ms，从停止时的30ms倒计时。
可选地，当IAB节点的MAC实体没有为第一SR配置的有效上行资源时，第一SR在IAB节点接收到回传链路恢复正常的指示之前，不会触发随机接入(Random Access，RACH)过程。比如，该上行资源可以为物理上行控制信道(Physical Uplink Control Channel，PUCCH)资源。
可选地，当触发要发送给父IAB节点的BSR的待发送数据中包括RLC control PDU时，该RLC control PDU比如包括RLC状态报告，第一SR不会被取消或者暂停，即不取消或者暂停第一SR，以保证RLC状态报告的发送。
比如，如果IAB节点在与其父IAB节点间的回传链路上接收到type-2回传RLF indication，可以对于由于要发送给父IAB节点的BSR而触发的所有待处理SR(pending SRs)全部取消，并且每一个SR各自对应的计时器sr-ProhibitTimer需要被停止(如果计时器在运行的话)。
又比如，如果IAB节点在与其父IAB节点间的回传链路上接收到type-2回传RLF indication，则对于由于要发送给父IAB节点的BSR而触发的pending  SRs，暂停/去激活对该pending SRs的后续处理，即直接表明停止处理该pending SRs的操作，并且每一个SR各自对应的计时器sr-ProhibitTimer需要被停止(如果计时器在运行的话)。
又比如，如果IAB节点在与其父IAB节点间的回传链路上接收到type-2回传RLF indication，则对于由于要发送给父IAB节点的BSR而触发的pending SRs，仍然遵循传统legacy的流程，即等待被处理，间接表明去激活/停止处理该pending SRs的操作。并且，该pending SRs在IAB节点接收到回传链路恢复正常的指示之前，不会触发RACH过程。也就是说，如果IAB节点在与其父IAB节点间的回传链路上接收到type-2回传RLF indication，则对于由于要发送给父IAB节点的BSR而触发的pending SRs，在接收到来自高层的回传链路恢复正常的指示之前，不会触发RACH过程。其中，在接收到来自高层的回传链路恢复正常的指示之前，触发type-2回传RLF indication的回传链路没有恢复正常，即如果接收到来自高层的回传链路恢复正常的指示，表明触发type-2回传RLF indication的回传链路恢复正常。
又比如，在暂停/去激活pending SRs之后，如果IAB节点接收到高层的回传链路恢复正常的指示，即指示“之前接收到type-2回传RLF indication的回传链路已经恢复正常”，则可以重新恢复对之前暂停/去激活pending SRs的操作，即恢复之前由于收到type-2回传RLF indication而停止操作的pending SRs。并且如果pending SRs之前触发了定时器，则重新开启该定时器，并且将该定时器的值设置成暂停/去激活时该计时器所对应的剩余时间，或者设置成计时器初始值。
可选地，当IAB节点在与其父IAB节点间的回传链路上接收到回传RLF indication时，该IAB节点可以取消或者暂停第二SR；其中，第二SR不是由于要发送给父IAB节点的BSR而触发的待处理SR。该暂停第二SR也可以称为去激活第二SR。
进一步的，在取消或者暂停第二SR时，当第二SR对应的第二定时器在运行时，IAB节点可以停止运行第二定时器。该第二定时器比如为 sr-ProhibitTimer。
进一步的，在暂停第二SR之后，当接收到回传链路恢复正常的指示时，IAB节点可以恢复暂停的第二SR。
进一步的，在暂停第二SR，且停止运行第二定时器之后，当接收到回传链路恢复正常的指示时，IAB节点可以重新启动第二定时器，并将第二定时器的值设置为第二定时器被暂停时所对应的剩余时间值，或者，将第二定时器的值设置为计时器初始值。其中，该计时器初始值可以协议约定或者网络侧设备配置等，对此不进行限制。
比如，假设第二定时器sr-ProhibitTimer总共是32ms，停止运行前倒计时到20ms，则停止之后恢复具有2种情况：1)将sr-ProhibitTimer的值设置为32ms，重新从32ms倒计时；2)将sr-ProhibitTimer的值设置为20ms，从停止时的20ms倒计时。
比如，如果IAB节点在与其父IAB节点间的回传链路上接收到type-2回传RLF indication，可以对于那些不是由于要发送给父IAB节点的BSR而触发的pending SRs全部取消，并且每一个SR各自对应的计时器sr-ProhibitTimer需要被停止(如果计时器在运行的话)。
又比如，如果IAB节点在与其父IAB节点间的回传链路上接收到type-2回传RLF indication，则对于那些不是由于要发送给父IAB节点的BSR而触发的pending SRs，在接收到回传链路恢复正常的指示之前，暂停/去激活对该pending SRs的后续处理，并且每一个SR各自对应的计时器sr-ProhibitTimer需要被停止(如果计时器在运行的话)。
又比如，在暂停/去激活pending SRs之后，如果IAB节点接收到高层的回传链路恢复正常的指示，即指示“之前接收到type-2回传RLF indication的回传链路已经恢复正常”，则可以重新恢复对之前暂停/去激活pending SRs的操作，即恢复对那些之前由于收到type-2回传RLF indication而停止操作的pending SRs。并且如果pending SRs之前触发了定时器，则重新开启该定时器，并且将该定时器的值设置成暂停/去激活时该计时器所对应的剩余时间， 或者设置成计时器初始值。
需指出的，上述的回传链路恢复正常的指示可以包括以下至少一项：type-3回传RLF indication、IAB节点的高层发送给MAC层的回传链路恢复正常的指示。对于高层发送给MAC层的回传链路恢复正常的指示可以理解为，高层(upper layer)进行层间指示，告知MAC层回传链路已经恢复正常。
此外，对于IAB节点没有接收到type-2回传RLF indication的其他情况，针对触发的SR按照legacy流程进行处理。
(2)基于回传RLF indication处理触发的BSR
本申请实施例中，回传RLF indication比如为type-2/type-4回传RLF indication，可以用于取消或者暂停已触发的BSR。
可选地，当IAB节点在与其父IAB节点间的回传链路上接收到回传RLF indication时，该IAB节点可以取消或者暂停第一BSR。其中，第一BSR是基于BSR流程决定的会被触发并且没有被取消的BSR。该暂停第一BSR也可以称为去激活第一BSR。
需指出的，第一BSR可以为常规(regular)BSR，也可以为周期性(periodic)BSR。对于regular BSR，如果没有接收到type-2回传RLF indication，则按照legacy流程进行处理。对于regular BSR，在收到type-2回传RLF indication且没有收到type-3回传RLF indication的情况下，说明regular BSR仍然处于非激活态，不能触发SR；而在收到type-2回传RLF indication且收到type-3回传RLF indication的情况下，说明regular BSR已恢复正常，可以触发SR。
可理解的是，由于填充(padding)BSR是在上行授权(UL grant)有多余的情况下，UE利用剩余比特数将BSR情况汇报给网络侧设备，因此，在资源有富余时才出现padding BSR，没必要取消padding BSR。因此，当第一BSR为padding BSR时，第一BSR不会被取消或者暂停。
进一步的，在取消或者暂停第一BSR时，当第一BSR对应的第三定时器在运行时，IAB节点可以停止运行第三定时器。其中，当第一BSR为regular BSR时，第三定时器为重传定时器，比如retxBSR-Timer。或者，当第一BSR 为periodic BSR时，第三定时器为周期性定时器，比如periodicalBSR-Timer。
进一步的，在暂停第一BSR时，当接收到回传链路恢复正常的指示时，IAB节点可以恢复暂停的第一BSR。
进一步的，在暂停第一BSR，且停止运行第三定时器之后，当接收到回传链路恢复正常的指示时，IAB节点可以重新启动第三定时器，并将第三定时器的值设置为第三定时器被暂停时所对应的剩余时间值，或者，将第三定时器的值设置为计时器初始值。其中，该计时器初始值可以协议约定或者网络侧设备配置等，对此不进行限制。
比如，假设第三定时器retxBSR-Timer总共是10子帧，停止运行前倒计时到5子帧，则停止之后恢复具有2种情况：1)将retxBSR-Timer的值设置为10子帧，重新从10子帧倒计时；2)将retxBSR-Timer的值设置为5子帧，从停止时的5子帧倒计时。
需指出的，上述的回传链路恢复正常的指示可以包括以下至少一项：type-3回传RLF indication、IAB节点的高层发送给MAC层的回传链路恢复正常的指示。对于高层发送给MAC层的回传链路恢复正常的指示可以理解为，高层(upper layer)进行层间指示，告知MAC层回传链路已经恢复正常。
可选地，当触发第一BSR的待发送数据中包括RLC control PDU时，该RLC control PDU比如包括RLC状态报告，第一BSR不会被取消或者暂停，即不取消或者暂停第一SR，以保证RLC状态报告的发送。
可选地，在接收到回传RLF indication之后，IAB节点可以停止触发新的BSR，和/或，停止触发新的SR；或者，在满足触发BSR的条件下，IAB节点可以触发新的BSR，且触发后的BSR被判定为暂停态/待处理(pending)态。比如，触发BSR的条件可以为以下至少一项：新到来的上行数据的逻辑信道优先级比UE已经缓存的上行数据中的任意一个逻辑信道组中的逻辑信道优先级都高、在新数据到来前没有任何缓存的上行数据，等等。
比如，如果IAB节点在与其父IAB节点间的回传链路上接收到type-2回传RLF indication，并且BSR流程(procedure)决定了至少一个BSR会被触 发并且没有被取消，则可以取消该至少一个BSR。
又比如，IAB节点接收到type-2回传RLF indication后，仍然可触发新的BSR，但是该BSR会被再判定为去激活态/暂停态，即对该BSR的处理都会停止。具体为，如果IAB节点在与其父IAB节点间的回传链路上接收到type-2回传RLF indication，且还未收到任何从upper layers来的指示说明发生了RLF的链路已经恢复正常，并且BSR procedure决定了至少一个BSR会被触发并且没有被取消，则：1)判定至少一个BSR是去激活的/暂停的BSR，即停止对至少一个BSR的操作，并且停止对应的retxBSR-Timer或者periodicaBSR-Timer(如果计时器在运行的话)；2)可选地，不会触发任何SR。
又比如，在暂停/去激活BSR之后，如果IAB节点接收到高层的回传链路恢复正常的指示，即指示“之前接收到type-2回传RLF indication的回传链路已经恢复正常”，则可以重新恢复对之前暂停/去激活的BSR的操作，即恢复之前由于收到type-2回传RLF indication而停止操作的BSR。并且如果该BSR之前触发了计时器，则重新开启该BSR对应的计时器，并且将定时器的值设置成去激活时该计时器所对应的剩余时间，或者设置成计时器初始值。
(3)基于回传RLF indication处理触发的PBSR
本申请实施例中，回传RLF indication比如为type-2/type-4回传RLF indication，可以用于取消或者暂停已触发的PBSR。
可选地，当IAB节点在与其父IAB节点间的回传链路上接收到回传RLF indication时，IAB节点可以取消或者暂停第一PBSR。其中，第一PBSR是基于PBSR流程决定的会被触发并且没有被取消的PBSR。该暂停第一PBSR也可以称为去激活第一PBSR。
进一步的，在暂停第一PBSR时，当接收到回传链路恢复正常的指示时，IAB节点可以恢复暂停的第一PBSR。
需指出的，上述的回传链路恢复正常的指示可以包括以下至少一项：type-3回传RLF indication、IAB节点的高层发送给MAC层的回传链路恢复正常的指示。对于高层发送给MAC层的回传链路恢复正常的指示可以理解 为，高层(upper layer)进行层间指示，告知MAC层回传链路已经恢复正常。
比如，如果IAB节点在与其父IAB节点间的回传链路上接收到type-2回传RLF indication，并且PBSR procedure决定了至少一个PBSR会被触发并且没有被取消，则可以取消该至少一个PBSR。
又比如，如果IAB节点在与其父IAB节点间的回传链路上接收到type-2回传RLF indication，停止触发新的PBSR，且对于已经触发的PBSR遵循现有流程进行处理。
又比如，IAB节点接收到type-2回传RLF indication后，仍然可触发新的PBSR，但是该PBSR会被再判定为去激活态/暂停态，即对该PBSR的处理都会停止。具体为，如果IAB节点在与其父IAB节点间的回传链路上接收到type-2回传RLF indication，且还未收到任何从upper layers来的指示说明发生了RLF的链路已经恢复正常，并且PBSR procedure决定了至少一个PBSR会被触发并且没有被取消，则：1)判定该至少一个PBSR是去激活的/暂停的PBSR，即停止对该至少一个PBSR的操作；2)可选地，不会触发任何SR。
又比如，在暂停/去激活PBSR之后，如果IAB节点接收到高层的回传链路恢复正常的指示，即指示“之前接收到type-2回传RLF indication的回传链路已经恢复正常”，则可以重新恢复对之前暂停/去激活的PBSR的操作，即恢复之前由于收到type-2回传RLF indication而停止操作的PBSR。
本申请实施例中，可选的，若IAB节点的RLC层指示MAC层待传输数据中包括RLC Control PDU，且待传输数据触发第二BSR，则第二BSR在被触发后，不会被取消或者暂停，以保证RLC状态报告的发送。
进一步的，若在IAB节点的上行授权(UL grant)的资源大小小于第二BSR所占用的资源大小时，触发了第二BSR对应的SR，则第二BSR对应的SR在被触发后，不会被取消或者暂停。
也就是说，若RLC层与MAC层进行层间交互，告知MAC层当前待传输数据中包括RLC Control PDU，并且触发BSR的发送，则触发的BSR在后续的所有操作中都不会被取消/暂停；并且当发送该BSR时，若UL grant的 大小比如根据逻辑通道优先级(Logical Channel Prioritization，LCP)准则不足以容纳BSR MAC控制单元(Control Element，CE)以及其子头(header)之和时，触发该BSR对应的SR(并且标记该SR)，则该SR在后续的所有操作中都不会被取消/暂停。
可选的，IAB节点的RLC Control PDU仅能通过第一逻辑信道(Logical Channel，LCH)进行传输，且触发第三BSR的待发送数据中包括第一LCH中的待传输数据时，第三BSR在被触发后，不会被取消或者暂停。即，如果规定RLC Control PDU只能通过某一特定的LCH进行传输，则当触发BSR的待发送数据中包含该LCH待传输数据时，该BSR在后续的所有操作中都不会被取消/暂停。
可选的，待处理的第三SR对应的LCH为用于传输RLC Control PDU的LCH，和/或，触发第三SR的第三BSR中包括第一LCH中的待发送数据时，第三SR不会被取消或者暂停。
本申请实施例中，在接收回传RLF indication之后，IAB节点对于上行传输许可的处理可以包括以下至少一项：
IAB节点忽略预配置的上行传输许可，即不使用预配置上行传输许可进行上行数据传输；
当具有RLC control PDU的传输需求时，IAB节点利用预配置的上行传输许可进行RLC control PDU的传输，即仍可使用预配置上行传输许可进行RLC control PDU传输；
IAB节点去激活预配置的上行传输许可。
进一步的，在去激活预配置的上行传输许可之后，当接收的回传链路恢复正常的指示时，IAB节点可以恢复预配置的上行传输许可，或者，IAB节点可以基于IAB节点的父IAB节点的指示，激活预配置的上行传输许可，以使用预配置上行传输许可进行上行数据传输。
需指出的，上述去激活预配置的上行传输许可表示的含义为，暂时忽略预配置的上行传输许可。比如，网络侧配置了一连串/周期的配置授权 (Configured Grant，CG)给UE，这时UE可以直接在网络侧提前配置的时频资源(CG)上传输数据；此处“去激活”的含义为，当某个CG的时刻到来时，UE可以在该CG上发送数据，但是因为收到了回传RLF indication，所以在该CG的时刻不传输数据，而是一直等待，直到RLF的回传链路恢复成功，才再利用CG进行数据传输。进一步的，IAB节点恢复预配置的上行传输许可表示的含义为，不忽略预配置的上行传输许可，即使用预配置上行传输许可进行数据传输。
需要说明的是，本申请实施例提供的上行传输的控制方法，执行主体可以为上行传输的控制装置，或者，该上行传输的控制装置中的用于执行上行传输的控制方法的控制模块。本申请实施例中以上行传输的控制装置执行上行传输的控制方法为例，说明本申请实施例提供的上行传输的控制装置。
请参见图4，图4是本申请实施例提供的一种上行传输的控制装置的结构示意图，该装置应用于IAB节点，该IAB节点为终端，如图4所示，该上行传输的控制装置40包括：
接收模块41，用于接收回传RLF indication；
处理模块42，用于取消或者暂停已触发的数据发送。
本申请实施例的上行传输的控制装置，在接收到回传RLF indication之后，可以取消或者暂停已触发的数据发送，从而实现对已触发的数据发送的处理，保证IAB网络中数据传输的稳定性。
可选地，所述已触发的数据发送包括以下至少一项：
已触发的调度请求SR；
已触发的缓冲状态报告BSR；
已触发的抢先缓冲状态报告PBSR。
可选地，所述回传RLF indication包括以下任意一项：类型2回传RLF indication、类型4回传RLF indication。
可选地，所述处理模块42还用于执行以下任意一项：
当所述IAB节点在与所述IAB节点的父IAB节点间的回传链路上接收到 所述回传RLF indication时，取消或者暂停第一SR；其中，所述第一SR是由于要发送给所述父IAB节点的BSR而触发的待处理SR；
当所述IAB节点在与所述IAB节点的父IAB节点间的回传链路上接收到所述回传RLF indication时，取消或者暂停第二SR；其中，所述第二SR不是由于要发送给所述父IAB节点的BSR而触发的待处理SR。
可选地，当所述IAB节点的MAC实体没有为所述第一SR配置的有效上行资源时，所述第一SR在所述IAB节点接收到回传链路恢复正常的指示之前，不会触发RACH过程。
可选地，所述处理模块42还用于：
在取消或者暂停所述第一SR时，当所述第一SR对应的第一定时器在运行时，停止运行所述第一定时器。
可选地，所述处理模块42还用于：
在取消或者暂停所述第二SR时，当所述第二SR对应的第二定时器在运行时，停止运行所述第二定时器。
可选地，当触发所述BSR的待发送数据中包括RLC control PDU时，所述第一SR不会被取消或者暂停。
可选地，所述处理模块42还用于：
在暂停所述第一SR之后，当接收到回传链路恢复正常的指示时，恢复暂停的所述第一SR。
可选地，所述处理模块42还用于：
在暂停所述第二SR之后，当接收到回传链路恢复正常的指示时，恢复暂停的所述第二SR。
可选地，所述处理模块42还用于：
在暂停所述第一SR，且停止运行所述第一定时器之后，当接收到回传链路恢复正常的指示时，重新启动所述第一定时器，并将所述第一定时器的值设置为第一定时器被暂停时所对应的剩余时间值，或者，将所述第一定时器的值设置为计时器初始值。
可选地，所述处理模块42还用于：
在暂停所述第二SR，且停止运行所述第二定时器之后，当接收到回传链路恢复正常的指示时，重新启动所述第二定时器，并将所述第二定时器的值设置为所述第二定时器被暂停时所对应的剩余时间值，或者，将所述第二定时器的值设置为计时器初始值。
可选地，所述处理模块42还用于：
当所述IAB节点在与所述IAB节点的父IAB节点间的回传链路上接收到所述回传RLF indication时，取消或者暂停第一BSR；其中，所述第一BSR是基于BSR流程决定的会被触发并且没有被取消的BSR。
可选地，当所述第一BSR为BSR时，所述第一BSR不会被取消或者暂停。
可选地，所述处理模块42还用于：
在取消或者暂停所述第一BSR时，当所述第一BSR对应的第三定时器在运行时，停止运行所述第三定时器。
可选地，当触发所述第一BSR的待发送数据中包括RLC control PDU时，所述第一BSR不会被取消或者暂停。
可选地，所述处理模块42还用于：
在暂停所述第一BSR之后，当接收到回传链路恢复正常的指示时，恢复暂停的所述第一BSR。
可选地，所述处理模块42还用于：
在暂停所述第一BSR，且停止运行所述第三定时器之后，当接收到回传链路恢复正常的指示时，重新启动所述第三定时器，并将所述第三定时器的值设置为所述第三定时器被暂停时所对应的剩余时间值，或者，将所述第三定时器的值设置为计时器初始值。
可选地，所述处理模块42还用于：
当所述IAB节点在与所述IAB节点的父IAB节点间的回传链路上接收到所述回传RLF indication时，取消或者暂停第一PBSR；其中，所述第一PBSR 是基于PBSR流程决定的会被触发并且没有被取消的PBSR。
可选地，所述处理模块42还用于：
在暂停所述第一PBSR之后，当接收到回传链路恢复正常的指示时，恢复暂停的所述第一PBSR。
可选地，所述回传链路恢复正常的指示包括以下至少一项：
类型3回传RLF indication；
所述IAB节点的高层发送给MAC层的回传链路恢复正常的指示。
可选地，所述处理模块42还用于：
在接收到所述回传RLF indication之后，停止触发新的BSR，和/或，停止触发新的SR；
或者，
在满足触发BSR的条件下，触发新的BSR，且触发后的BSR被判定为暂停态。
可选地，若所述IAB节点的RLC层指示MAC层待传输数据中包括RLC Control PDU，且所述待传输数据触发第二BSR，则所述第二BSR在被触发后，不会被取消或者暂停。
可选地，若在所述IAB节点的上行授权的资源大小小于所述第二BSR所占用的资源大小时，触发了所述第二BSR对应的SR，则所述第二BSR对应的SR在被触发后，不会被取消或者暂停。
可选地，所述IAB节点的RLC Control PDU仅能通过第一逻辑信道LCH进行传输，且触发第三BSR的待发送数据中包括所述第一LCH中的待传输数据时，所述第三BSR在被触发后，不会被取消或者暂停；
或者，
待处理的第三SR对应的LCH为用于传输RLC Control PDU的LCH，和/或，触发所述第三SR的第三BSR中包括所述第一LCH中的待发送数据时，所述第三SR不会被取消或者暂停。
可选地，所述处理模块42还用于：
在接收所述回传RLF indication之后，执行以下至少一项：
忽略预配置的上行传输许可；
当具有RLC control PDU的传输需求时，利用预配置的上行传输许可进行所述RLC control PDU的传输；
去激活预配置的上行传输许可。
可选地，所述处理模块42还用于：
在去激活所述预配置的上行传输许可之后，当接收的回传链路恢复正常的指示时，恢复所述预配置的上行传输许可，或者，基于所述IAB节点的父IAB节点的指示，激活所述预配置的上行传输许可。
本申请实施例中的上行传输的控制装置可以是装置，具有操作系统的装置或电子设备，也可以是终端中的部件、集成电路、或芯片。该装置或电子设备可以是移动终端，也可以为非移动终端。示例性的，移动终端可以包括但不限于上述所列举的终端11的类型，非移动终端可以为服务器、网络附属存储器(Network Attached Storage，NAS)、个人计算机(Personal Computer，PC)、电视机(Television，TV)、柜员机或者自助机等，本申请实施例不作具体限定。
本申请实施例提供的上行传输的控制装置能够实现图3的方法实施例实现的各个过程，并达到相同的技术效果，为避免重复，这里不再赘述。
可选地，如图5所示，本申请实施例还提供一种终端500，该终端500为IAB节点，包括处理器501，存储器502，存储在存储器502上并可在所述处理器501上运行的程序或指令，该程序或指令被处理器501执行时实现上述上行传输的控制方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
本申请实施例还提供一种终端，该终端为IAB节点，包括处理器和通信接口，通信接口用于接收回传RLF indication，处理器用于取消或者暂停已触发的数据发送。该终端实施例是与上述图3所示方法实施例对应的，上述方法实施例的各个实施过程和实现方式均可适用于该终端实施例中，且能达到 相同的技术效果。
具体地，图6为实现本申请实施例的一种终端的硬件结构示意图。
该终端600为IAB节点，包括但不限于：射频单元601、网络模块602、音频输出单元603、输入单元604、传感器605、显示单元606、用户输入单元607、接口单元608、存储器609、以及处理器610等中的至少部分部件。
本领域技术人员可以理解，终端600还可以包括给各个部件供电的电源(比如电池)，电源可以通过电源管理系统与处理器610逻辑相连，从而通过电源管理系统实现管理充电、放电、以及功耗管理等功能。图6中示出的终端结构并不构成对终端的限定，终端可以包括比图示更多或更少的部件，或者组合某些部件，或者不同的部件布置，在此不再赘述。
应理解的是，本申请实施例中，输入单元604可以包括图形处理器(Graphics Processing Unit，GPU)6041和麦克风6042，图形处理器6041对在视频捕获模式或图像捕获模式中由图像捕获装置(如摄像头)获得的静态图片或视频的图像数据进行处理。显示单元606可包括显示面板6061，可以采用液晶显示器、有机发光二极管等形式来配置显示面板6061。用户输入单元607包括触控面板6071以及其他输入设备6072。触控面板6071，也称为触摸屏。触控面板6071可包括触摸检测装置和触摸控制器两个部分。其他输入设备6072可以包括但不限于物理键盘、功能键(比如音量控制按键、开关按键等)、轨迹球、鼠标、操作杆，在此不再赘述。
本申请实施例中，射频单元601将来自网络侧设备的下行数据接收后，给处理器610处理；另外，将上行的数据发送给网络侧设备。通常，射频单元601包括但不限于天线、至少一个放大器、收发信机、耦合器、低噪声放大器、双工器等。
存储器609可用于存储软件程序或指令以及各种数据。存储器609可主要包括存储程序或指令区和存储数据区，其中，存储程序或指令区可存储操作系统、至少一个功能所需的应用程序或指令(比如声音播放功能、图像播放功能等)等。此外，存储器609可以包括高速随机存取存储器，还可以包 括非易失性存储器，其中，非易失性存储器可以是只读存储器(Read-Only Memory，ROM)、可编程只读存储器(Programmable ROM，PROM)、可擦除可编程只读存储器(Erasable PROM，EPROM)、电可擦除可编程只读存储器(Electrically EPROM，EEPROM)或闪存。例如至少一个磁盘存储器件、闪存器件、或其他非易失性固态存储器件。
处理器610可包括一个或多个处理单元；可选的，处理器610可集成应用处理器和调制解调处理器，其中，应用处理器主要处理操作系统、用户界面和应用程序或指令等，调制解调处理器主要处理无线通信，如基带处理器。可以理解的是，上述调制解调处理器也可以不集成到处理器610中。
其中，射频单元601用于：接收回传RLF indication；
处理器610，用于取消或者暂停已触发的数据发送。
基于本实施例中的方案，在接收到回传RLF indication之后，可以取消或者暂停已触发的数据发送，从而实现对已触发的数据发送的处理，保证IAB网络中数据传输的稳定性。
可选地，所述已触发的数据发送包括以下至少一项：
已触发的调度请求SR；
已触发的缓冲状态报告BSR；
已触发的抢先缓冲状态报告PBSR。
可选地，所述回传RLF indication包括以下任意一项：类型2回传RLF indication、类型4回传RLF indication。
可选地，处理器610还用于执行以下任意一项：
当终端600在与终端600的父IAB节点间的回传链路上接收到所述回传RLF indication时，取消或者暂停第一SR；其中，所述第一SR是由于要发送给所述父IAB节点的BSR而触发的待处理SR；
当终端600在与终端600的父IAB节点间的回传链路上接收到所述回传RLF indication时，取消或者暂停第二SR；其中，所述第二SR不是由于要发送给所述父IAB节点的BSR而触发的待处理SR。
可选地，当终端600的MAC实体没有为所述第一SR配置的有效上行资源时，所述第一SR在终端600接收到回传链路恢复正常的指示之前，不会触发RACH过程。
可选地，处理器610还用于：
在取消或者暂停所述第一SR时，当所述第一SR对应的第一定时器在运行时，停止运行所述第一定时器。
可选地，处理器610还用于：
在取消或者暂停所述第二SR时，当所述第二SR对应的第二定时器在运行时，停止运行所述第二定时器。
可选地，当触发所述BSR的待发送数据中包括RLC control PDU时，所述第一SR不会被取消或者暂停。
可选地，处理器610还用于：
在暂停所述第一SR之后，当接收到回传链路恢复正常的指示时，恢复暂停的所述第一SR。
可选地，处理器610还用于：
在暂停所述第二SR之后，当接收到回传链路恢复正常的指示时，恢复暂停的所述第二SR。
可选地，处理器610还用于：
在暂停所述第一SR，且停止运行所述第一定时器之后，当接收到回传链路恢复正常的指示时，重新启动所述第一定时器，并将所述第一定时器的值设置为第一定时器被暂停时所对应的剩余时间值，或者，将所述第一定时器的值设置为计时器初始值。
可选地，处理器610还用于：
在暂停所述第二SR，且停止运行所述第二定时器之后，当接收到回传链路恢复正常的指示时，重新启动所述第二定时器，并将所述第二定时器的值设置为所述第二定时器被暂停时所对应的剩余时间值，或者，将所述第二定时器的值设置为计时器初始值。
可选地，处理器610还用于：
当终端600在与终端600的父IAB节点间的回传链路上接收到所述回传RLF indication时，取消或者暂停第一BSR；其中，所述第一BSR是基于BSR流程决定的会被触发并且没有被取消的BSR。
可选地，当所述第一BSR为BSR时，所述第一BSR不会被取消或者暂停。
可选地，处理器610还用于：
在取消或者暂停所述第一BSR时，当所述第一BSR对应的第三定时器在运行时，停止运行所述第三定时器。
可选地，当触发所述第一BSR的待发送数据中包括RLC control PDU时，所述第一BSR不会被取消或者暂停。
可选地，处理器610还用于：
在暂停所述第一BSR之后，当接收到回传链路恢复正常的指示时，恢复暂停的所述第一BSR。
可选地，处理器610还用于：
在暂停所述第一BSR，且停止运行所述第三定时器之后，当接收到回传链路恢复正常的指示时，重新启动所述第三定时器，并将所述第三定时器的值设置为所述第三定时器被暂停时所对应的剩余时间值，或者，将所述第三定时器的值设置为计时器初始值。
可选地，处理器610还用于：
当终端600在与终端600的父IAB节点间的回传链路上接收到所述回传RLF indication时，取消或者暂停第一PBSR；其中，所述第一PBSR是基于PBSR流程决定的会被触发并且没有被取消的PBSR。
可选地，处理器610还用于：
在暂停所述第一PBSR之后，当接收到回传链路恢复正常的指示时，恢复暂停的所述第一PBSR。
可选地，所述回传链路恢复正常的指示包括以下至少一项：
类型3回传RLF indication；
终端600的高层发送给MAC层的回传链路恢复正常的指示。
可选地，处理器610还用于：
在接收到所述回传RLF indication之后，停止触发新的BSR，和/或，停止触发新的SR；
或者，在满足触发BSR的条件下，触发新的BSR，且触发后的BSR被判定为暂停态。
可选地，若终端600的RLC层指示MAC层待传输数据中包括RLC Control PDU，且所述待传输数据触发第二BSR，则所述第二BSR在被触发后，不会被取消或者暂停。
可选地，若在终端600的上行授权的资源大小小于所述第二BSR所占用的资源大小时，触发了所述第二BSR对应的SR，则所述第二BSR对应的SR在被触发后，不会被取消或者暂停。
可选地，终端600的RLC Control PDU仅能通过第一逻辑信道LCH进行传输，且触发第三BSR的待发送数据中包括所述第一LCH中的待传输数据时，所述第三BSR在被触发后，不会被取消或者暂停；
或者，
待处理的第三SR对应的LCH为用于传输RLC Control PDU的LCH，和/或，触发所述第三SR的第三BSR中包括所述第一LCH中的待发送数据时，所述第三SR不会被取消或者暂停。
可选地，处理器610还用于：
在接收所述回传RLF indication之后，执行以下至少一项：
忽略预配置的上行传输许可；
当具有RLC control PDU的传输需求时，利用预配置的上行传输许可进行所述RLC control PDU的传输；
去激活预配置的上行传输许可。
可选地，处理器610还用于：
在去激活所述预配置的上行传输许可之后，当接收的回传链路恢复正常的指示时，恢复所述预配置的上行传输许可，或者，基于终端600的父IAB节点的指示，激活所述预配置的上行传输许可。
本申请实施例还提供一种可读存储介质，所述可读存储介质可以是非易失的，也可以是易失的，所述可读存储介质上存储有程序或指令，该程序或指令被处理器执行时实现上述图3所示方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
其中，所述处理器为上述实施例中所述的终端中的处理器。所述可读存储介质，包括计算机可读存储介质，如计算机只读存储器(Read-Only Memory，ROM)、随机存取存储器(Random Access Memory，RAM)、磁碟或者光盘等。
本申请实施例另提供了一种芯片，所述芯片包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行程序或指令，实现上述图3所示方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
应理解，本申请实施例提到的芯片还可以称为系统级芯片，系统芯片，芯片系统或片上系统芯片等。
本申请实施例还提供一种计算机程序产品，所述计算机程序产品被存储在非瞬态的存储介质中，所述计算机程序产品被至少一个处理器执行以实现上述图3所示方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
需要说明的是，在本文中，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、物品或者装置不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、物品或者装置所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括该要素的过程、方法、物品或者装置中还存在另外的相同要素。此外，需要指出的是，本申请实施方式中的方法和装置的范围不限按示出或讨论的顺序来执行功能，还 可包括根据所涉及的功能按基本同时的方式或按相反的顺序来执行功能，例如，可以按不同于所描述的次序来执行所描述的方法，并且还可以添加、省去、或组合各种步骤。另外，参照某些示例所描述的特征可在其他示例中被组合。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到上述实施例方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分可以以计算机软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端(可以是手机，计算机，服务器，空调器，或者网络设备等)执行本申请各个实施例所述的方法。
在本申请所提供的实施例中，应该理解到，所揭露的装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的 技术方案本质上或者说对相关技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、ROM、RAM、磁碟或者光盘等各种可以存储程序代码的介质。
上面结合附图对本申请的实施例进行了描述，但是本申请并不局限于上述的具体实施方式，上述的具体实施方式仅仅是示意性的，而不是限制性的，本领域的普通技术人员在本申请的启示下，在不脱离本申请宗旨和权利要求所保护的范围情况下，还可做出很多形式，均属于本申请的保护之内。

Claims (34)

  1. 一种上行传输的控制方法，包括：
    集成接入回传IAB节点接收回传无线链路失败指示RLF indication；
    所述IAB节点取消或者暂停已触发的数据发送。
  2. 根据权利要求1所述的方法，其中，所述已触发的数据发送包括以下至少一项：
    已触发的调度请求SR；
    已触发的缓冲状态报告BSR；
    已触发的抢先缓冲状态报告PBSR。
  3. 根据权利要求1所述的方法，其中，所述回传RLF indication包括以下任意一项：类型2回传RLF indication、类型4回传RLF indication。
  4. 根据权利要求1所述的方法，其中，所述取消或者暂停已触发的数据发送，包括以下任意一项：
    当所述IAB节点在与所述IAB节点的父IAB节点间的回传链路上接收到所述回传RLF indication时，所述IAB节点取消或者暂停第一SR；其中，所述第一SR是由于要发送给所述父IAB节点的BSR而触发的待处理SR；
    当所述IAB节点在与所述IAB节点的父IAB节点间的回传链路上接收到所述回传RLF indication时，所述IAB节点取消或者暂停第二SR；其中，所述第二SR不是由于要发送给所述父IAB节点的BSR而触发的待处理SR。
  5. 根据权利要求4所述的方法，其中，当所述IAB节点的媒体接入控制MAC实体没有为所述第一SR配置的有效上行资源时，所述第一SR在所述IAB节点接收到回传链路恢复正常的指示之前，不会触发随机接入RACH过程。
  6. 根据权利要求4所述的方法，其中，在取消或者暂停所述第一SR时，所述方法还包括：
    当所述第一SR对应的第一定时器在运行时，所述IAB节点停止运行所述第一定时器；
    或者，
    在取消或者暂停所述第二SR时，所述方法还包括：
    当所述第二SR对应的第二定时器在运行时，所述IAB节点停止运行所述第二定时器。
  7. 根据权利要求4所述的方法，其中，当触发所述BSR的待发送数据中包括无线链路控制RLC控制control协议数据单元PDU时，所述第一SR不会被取消或者暂停。
  8. 根据权利要求4所述的方法，其中，在暂停所述第一SR之后，所述方法还包括：
    当接收到回传链路恢复正常的指示时，所述IAB节点恢复暂停的所述第一SR；
    或者，
    在暂停所述第二SR之后，所述方法还包括：
    当接收到回传链路恢复正常的指示时，所述IAB节点恢复暂停的所述第二SR。
  9. 根据权利要求6所述的方法，其中，在暂停所述第一SR，且停止运行所述第一定时器之后，所述方法还包括：
    当接收到回传链路恢复正常的指示时，所述IAB节点重新启动所述第一定时器，并将所述第一定时器的值设置为第一定时器被暂停时所对应的剩余时间值，或者，将所述第一定时器的值设置为计时器初始值；
    或者，
    在暂停所述第二SR，且停止运行所述第二定时器之后，所述方法还包括：
    当接收到回传链路恢复正常的指示时，所述IAB节点重新启动所述第二定时器，并将所述第二定时器的值设置为所述第二定时器被暂停时所对应的剩余时间值，或者，将所述第二定时器的值设置为计时器初始值。
  10. 根据权利要求1所述的方法，其中，所述取消或者暂停已触发的数据发送，包括：
    当所述IAB节点在与所述IAB节点的父IAB节点间的回传链路上接收到所述回传RLF indication时，所述IAB节点取消或者暂停第一BSR；
    其中，所述第一BSR是基于BSR流程决定的会被触发并且没有被取消的BSR。
  11. 根据权利要求10所述的方法，其中，当所述第一BSR为填充BSR时，所述第一BSR不会被取消或者暂停。
  12. 根据权利要求10所述的方法，其中，在取消或者暂停所述第一BSR时，所述方法还包括：
    当所述第一BSR对应的第三定时器在运行时，所述IAB节点停止运行所述第三定时器。
  13. 根据权利要求10所述的方法，其中，当触发所述第一BSR的待发送数据中包括RLC control PDU时，所述第一BSR不会被取消或者暂停。
  14. 根据权利要求10所述的方法，其中，在暂停所述第一BSR之后，所述方法还包括：
    当接收到回传链路恢复正常的指示时，所述IAB节点恢复暂停的所述第一BSR。
  15. 根据权利要求12所述的方法，其中，在暂停所述第一BSR，且停止运行所述第三定时器之后，所述方法还包括：
    当接收到回传链路恢复正常的指示时，所述IAB节点重新启动所述第三定时器，并将所述第三定时器的值设置为所述第三定时器被暂停时所对应的剩余时间值，或者，将所述第三定时器的值设置为计时器初始值。
  16. 根据权利要求1所述的方法，其中，所述取消或者暂停已触发的数据发送，包括：
    当所述IAB节点在与所述IAB节点的父IAB节点间的回传链路上接收到所述回传RLF indication时，所述IAB节点取消或者暂停第一PBSR；
    其中，所述第一PBSR是基于PBSR流程决定的会被触发并且没有被取消的PBSR。
  17. 根据权利要求16所述的方法，其中，在暂停所述第一PBSR之后，所述方法还包括：
    当接收到回传链路恢复正常的指示时，所述IAB节点恢复暂停的所述第一PBSR。
  18. 根据权利要求8、9、14、15和17中任一项所述的方法，其中，所述回传链路恢复正常的指示包括以下至少一项：
    类型3回传RLF indication；
    所述IAB节点的高层发送给MAC层的回传链路恢复正常的指示。
  19. 根据权利要求1所述的方法，其中，在接收到所述回传RLF indication之后，所述方法还包括：
    所述IAB节点停止触发新的BSR，和/或，停止触发新的SR；
    或者，
    在满足触发BSR的条件下，所述IAB节点触发新的BSR，且触发后的BSR被判定为暂停态。
  20. 根据权利要求1所述的方法，其中，
    若所述IAB节点的RLC层指示MAC层待传输数据中包括RLC Control PDU，且所述待传输数据触发第二BSR，则所述第二BSR在被触发后，不会被取消或者暂停。
  21. 根据权利要求20所述的方法，其中，
    若在所述IAB节点的上行授权的资源大小小于所述第二BSR所占用的资源大小时，触发了所述第二BSR对应的SR，则所述第二BSR对应的SR在被触发后，不会被取消或者暂停。
  22. 根据权利要求1所述的方法，其中，所述IAB节点的RLC Control PDU仅能通过第一逻辑信道LCH进行传输，且触发第三BSR的待发送数据中包括所述第一LCH中的待传输数据时，所述第三BSR在被触发后，不会被取 消或者暂停；
    或者，
    待处理的第三SR对应的LCH为用于传输RLC Control PDU的LCH，和/或，触发所述第三SR的第三BSR中包括所述第一LCH中的待发送数据时，所述第三SR不会被取消或者暂停。
  23. 根据权利要求1所述的方法，其中，在接收所述回传RLF indication之后，所述方法还包括以下至少一项：
    所述IAB节点忽略预配置的上行传输许可；
    当具有RLC control PDU的传输需求时，所述IAB节点利用预配置的上行传输许可进行所述RLC control PDU的传输；
    所述IAB节点去激活预配置的上行传输许可。
  24. 根据权利要求23所述的方法，其中，在去激活所述预配置的上行传输许可之后，所述方法还包括：
    当接收的回传链路恢复正常的指示时，所述IAB节点恢复所述预配置的上行传输许可，或者，所述IAB节点基于所述IAB节点的父IAB节点的指示，激活所述预配置的上行传输许可。
  25. 一种上行传输的控制装置，包括：
    接收模块，用于接收回传RLF indication；
    处理模块，用于取消或者暂停已触发的数据发送。
  26. 根据权利要求25所述的装置，其中，所述已触发的数据发送包括以下至少一项：
    已触发的SR；
    已触发的BSR；
    已触发的PBSR。
  27. 根据权利要求25所述的装置，其中，所述处理模块还用于执行以下任意一项：
    当IAB节点在与所述IAB节点的父IAB节点间的回传链路上接收到所述 回传RLF indication时，取消或者暂停第一SR；其中，所述第一SR是由于要发送给所述父IAB节点的BSR而触发的待处理SR；
    当IAB节点在与所述IAB节点的父IAB节点间的回传链路上接收到所述回传RLF indication时，取消或者暂停第二SR；其中，所述第二SR不是由于要发送给所述父IAB节点的BSR而触发的待处理SR。
  28. 根据权利要求25所述的装置，其中，所述处理模块还用于：
    当IAB节点在与所述IAB节点的父IAB节点间的回传链路上接收到所述回传RLF indication时，取消或者暂停第一BSR；
    其中，所述第一BSR是基于BSR流程决定的会被触发并且没有被取消的BSR。
  29. 根据权利要求25所述的装置，其中，所述处理模块还用于：
    当IAB节点在与所述IAB节点的父IAB节点间的回传链路上接收到所述回传RLF indication时，取消或者暂停第一PBSR；
    其中，所述第一PBSR是基于PBSR流程决定的会被触发并且没有被取消的PBSR。
  30. 一种终端，所述终端为IAB节点，包括处理器，存储器及存储在所述存储器上并可在所述处理器上运行的程序或指令，其中，所述程序或指令被所述处理器执行时实现如权利要求1至24任一项所述的上行传输的控制方法的步骤。
  31. 一种可读存储介质，所述可读存储介质上存储程序或指令，其中，所述程序或指令被处理器执行时实现如权利要求1至24任一项所述的上行传输的控制方法的步骤。
  32. 一种芯片，包括处理器和通信接口，其中，所述通信接口和所述处理器耦合，所述处理器用于运行程序或指令，实现如权利要求1至24任一项所述的上行传输的控制方法的步骤。
  33. 一种计算机程序产品，其中，所述计算机程序产品被存储在非瞬态的存储介质中，所述计算机程序产品被至少一个处理器执行以实现如权利要 求1至24任一项所述的上行传输的控制方法的步骤。
  34. 一种通信设备，被配置为执行如权利要求1至24任一项所述的上行传输的控制方法的步骤。
PCT/CN2022/081691 2021-03-25 2022-03-18 上行传输的控制方法、装置及终端 WO2022199482A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202110321993.2 2021-03-25
CN202110321993.2A CN115134865A (zh) 2021-03-25 2021-03-25 上行传输的控制方法、装置及终端

Publications (1)

Publication Number Publication Date
WO2022199482A1 true WO2022199482A1 (zh) 2022-09-29

Family

ID=83374459

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/081691 WO2022199482A1 (zh) 2021-03-25 2022-03-18 上行传输的控制方法、装置及终端

Country Status (2)

Country Link
CN (1) CN115134865A (zh)
WO (1) WO2022199482A1 (zh)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020153274A1 (en) * 2019-01-22 2020-07-30 Sharp Kabushiki Kaisha Cell selection on a radio link failure in wireless relay networks
WO2020191728A1 (en) * 2019-03-28 2020-10-01 Lenovo (Beijing) Limited Method and apparatus for transmitting radio link information
CN111757398A (zh) * 2019-03-28 2020-10-09 华为技术有限公司 一种通信方法与装置
CN112075097A (zh) * 2018-07-30 2020-12-11 株式会社Kt 在中继节点中处理数据的方法及其装置
CN112470508A (zh) * 2018-08-03 2021-03-09 联想(北京)有限公司 处置无线电链路失败的方法及设备

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112075097A (zh) * 2018-07-30 2020-12-11 株式会社Kt 在中继节点中处理数据的方法及其装置
CN112470508A (zh) * 2018-08-03 2021-03-09 联想(北京)有限公司 处置无线电链路失败的方法及设备
WO2020153274A1 (en) * 2019-01-22 2020-07-30 Sharp Kabushiki Kaisha Cell selection on a radio link failure in wireless relay networks
WO2020191728A1 (en) * 2019-03-28 2020-10-01 Lenovo (Beijing) Limited Method and apparatus for transmitting radio link information
CN111757398A (zh) * 2019-03-28 2020-10-09 华为技术有限公司 一种通信方法与装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
ITRI: "Backhaul RLF handling", 3GPP DRAFT; R2-1913063_BH_RLF_HANDLING, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Chongqing, China; 20191014 - 20191018, 4 October 2019 (2019-10-04), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , pages 1 - 4, XP051791081 *

Also Published As

Publication number Publication date
CN115134865A (zh) 2022-09-30

Similar Documents

Publication Publication Date Title
WO2017193766A1 (zh) 一种下行数据传输的方法及设备
US20230262517A1 (en) Pdcp duplication configuring, activating, or deactivating method and terminal
US20230247553A1 (en) DRX Determining Method and Apparatus, Terminal, and Readable Storage Medium
WO2022148478A1 (zh) 配置方法、装置、设备及可读存储介质
WO2023040893A1 (zh) 连续lbt失败处理方法及装置、终端及网络侧设备
US20230109276A1 (en) Access procedure processing method, apparatus and communications device
WO2022206612A1 (zh) 通信路径的切换方法、装置及终端
WO2022199482A1 (zh) 上行传输的控制方法、装置及终端
WO2022213923A1 (zh) 传输处理方法、装置及通信设备
WO2023066106A1 (zh) 数据丢弃方法、装置、终端及网络侧设备
WO2023093636A1 (zh) 信息上报方法、配置方法、装置、终端及网络侧设备
WO2023066308A1 (zh) Sl drx的配置方法、装置及终端
WO2022237619A1 (zh) Rrc消息的传输方法及装置、终端及可读存储介质
WO2022206664A1 (zh) 信息传输方法、装置及通信设备
WO2023185841A1 (zh) 中继终端的选择方法、装置、终端及存储介质
WO2022237678A1 (zh) 带宽部分处理方法、装置及终端
WO2023131304A1 (zh) 旁链路资源选择方法及装置
WO2023185803A1 (zh) 无线链路失败的确定方法、装置、终端及网络侧设备
US20230086504A1 (en) Method and apparatus for leaving network, and terminal
WO2022083612A1 (zh) 用户信息的发送方法、装置及终端
CN113766675B (zh) 离开网络的方法、装置和终端
WO2022262865A1 (zh) Gap处理方法、装置、终端及可读存储介质
WO2023185819A1 (zh) Pdcch监听方法、终端、网络侧设备及介质
WO2023051447A1 (zh) 主小区组mcg恢复方法、装置、终端和可读存储介质
WO2023116836A1 (zh) 图像帧的获取方法、装置及通信设备

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: 22774143

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: 22774143

Country of ref document: EP

Kind code of ref document: A1