Uplink transmission control method, device and terminal

Abstract

The present application discloses a control method, device and terminal for uplink transmission, which belongs to the field of communication technology. The control method for uplink transmission in an embodiment of the present application includes: an IAB node receives a backhaul radio link failure indication RLF indication; the IAB node cancels or suspends the triggered data transmission. According to the scheme in the present application, after receiving the backhaul RLF indication, the triggered data transmission can be processed to ensure the stability of data transmission in the IAB network.

Description

Technical Field

[0001] The present application belongs to the field of communication technology, and specifically relates to a control method, device and terminal for uplink transmission. Background Art

[0002] In an Integrated Access Backhaul (IAB) network, when an IAB node receives a backhaul radio link failure (RLF) indication sent by its parent IAB node to the IAB node, further actions of the IAB node will be triggered. However, in this case, it is not yet determined how to process the triggered data transmission of the IAB node. Summary of the invention

[0003] The embodiments of the present application provide a method, device and terminal for controlling uplink transmission, which can solve the problem of how an IAB node processes triggered data transmission when receiving a return RLF indication.

[0004] In a first aspect, a method for controlling uplink transmission is provided, comprising:

[0005] The IAB node receives and returns the RLF indication;

[0006] The IAB node cancels or suspends the triggered data transmission.

[0007] In a second aspect, a control device for uplink transmission is provided, including:

[0008] A receiving module is used to receive the returned RLF indication;

[0009] The processing module is used to cancel or pause the triggered data sending.

[0010] In a third aspect, a terminal is provided, which is an IAB node, including a processor, a memory, and a program or instruction stored in the memory and executable on the processor, wherein the program or instruction, when executed by the processor, implements the steps of the method described in the first aspect.

[0011] In a fourth aspect, a terminal is provided, which is an IAB node, including a processor and a communication interface, wherein the communication interface is used to receive a returned RLF indication, and the processor is used to cancel or suspend triggered data transmission.

[0012] In a fifth aspect, a readable storage medium is provided, on which a program or instruction is stored. When the program or instruction is executed by a processor, the steps of the method described in the first aspect are implemented.

[0013] In a sixth aspect, a chip is provided, comprising a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run a program or instruction to implement the method described in the first aspect.

[0014] In a seventh aspect, a computer program / program product is provided, wherein the computer program / program product is stored in a non-volatile storage medium, and the program / program product is executed by at least one processor to implement the steps of the method described in the first aspect.

[0015] In the embodiment of the present application, after receiving the returned RLF indication, the IAB node may cancel or suspend the triggered data transmission, thereby processing the triggered data transmission and ensuring the stability of data transmission in the IAB network. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] Figure 1 is a block diagram of a wireless communication system to which the embodiments of the present application can be applied;

[0017] Figure 2 is a schematic diagram of an IAB system in an embodiment of the present application;

[0018] Figure 3 is a flow chart of a method for controlling uplink transmission provided in an embodiment of the present application;

[0019] Figure 4 It is a structural schematic diagram of a control device for uplink transmission provided in an embodiment of the present application;

[0020] Figure 5 is a schematic diagram of the structure of a terminal provided in an embodiment of the present application;

[0021] Figure 6 It is a structural diagram of another terminal provided in an embodiment of the present application. DETAILED DESCRIPTION

[0022] The following will be combined with the drawings in the embodiments of the present application to clearly describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field belong to the scope of protection of this application.

[0023] The terms "first", "second", etc. in the specification and claims of the present application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the terms used in this way are interchangeable under appropriate circumstances, so that the embodiments of the present application can be implemented in an order other than those illustrated or described here, and the objects distinguished by "first" and "second" are generally of the same type, and the number of objects is not limited. For example, the first object can be one or more. In addition, "and / or" in the specification and claims represents at least one of the connected objects, and the character " / " generally represents that the objects associated with each other are in an "or" relationship.

[0024] It is worth noting that the technology described in the embodiments of the present application is not limited to the Long Term Evolution (LTE) / LTE-Advanced (LTE-A) system, but can also be used in other wireless communication systems, such as 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) and other systems. The terms "system" and "network" in the embodiments of the present application are often used interchangeably, and the described technology can be used for the systems and radio technologies mentioned above as well as for other systems and radio technologies. The following description describes a New Radio (NR) system for illustrative purposes, and NR terminology is used in most of the following descriptions, but these technologies can also be applied to applications other than NR system applications, such as the 6th generation (6 th Generation, 6G) communication system.

[0025] Figure 1A block diagram of a wireless communication system applicable to an embodiment of the present application is shown. The wireless communication system includes a terminal 11 and a network side device 12. Among them, the terminal 11 can also be called a terminal device or a user terminal (User Equipment, UE), and the terminal 11 can be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer) or a notebook computer, a personal digital assistant (Personal Digital Assistant, PDA), a handheld computer, a netbook, an ultra-mobile personal computer (ultra-mobile personal computer, UMPC), a mobile Internet device (Mobile Internet Device, MID), a wearable device (Wearable Device) or a vehicle-mounted device (VUE), a pedestrian terminal (PUE) and other terminal side devices, and the wearable device includes: a smart watch, a bracelet, a headset, glasses, etc. It should be noted that the specific type of the terminal 11 is not limited in the embodiment of the present application. The network side device 12 can be a base station or a core network, wherein the base station can be referred to as a node B, an evolved node B, an access point, a base transceiver station (Base Transceiver Station, BTS), a radio base station, a radio transceiver, a basic service set (Basic Service Set, BSS), an extended service set (Extended Service Set, ESS), a B node, an evolved B node (eNB), a home B node, a home evolved B node, a WLAN access point, a WiFi node, a transmitting and receiving point (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 a specific technical vocabulary. It should be noted that in the embodiment of the present application, only the base station in the NR system is taken as an example, but the specific type of the base station is not limited.

[0026] In order to facilitate understanding of the embodiments of the present application, the following contents are first described.

[0027] See also Figure 2 , Figure 2A schematic diagram of an IAB system in an embodiment of the present application is shown. In the IAB system, an IAB node includes a distributed unit (DU) functional part and a mobile terminal (MT) functional part. Relying on the MT functional part, the IAB node can find a parent IAB node (parent IAB node) and establish a wireless connection with the DU of the parent IAB node. The wireless connection is called a backhaul link. After an IAB node establishes a complete backhaul link, the IAB node can turn on its DU function, and the DU will provide cell services, that is, the DU can provide access services for user equipment (UE). A self-backhaul loop includes a donor IAB node (or IAB donor), and the donor IAB node has a directly connected wired transmission network.

[0028] In the embodiment of the present application, the IAB system is introduced to solve the problem that 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 points can rely on wireless backhaul.

[0029] Optionally, the wireless link between the IAB nodes may be referred to as a backhaul (BH) link. A BH radio link control (RLC) channel may be configured on the BH link for wireless backhaul.

[0030] In an embodiment of the present application, a backhaul adaptation protocol (BAP) control protocol data unit (Protocol Data Unit) is used to carry control information of the BAP layer. Among them, a defined BAP control PDU type is: BH RLF indication. The BH RLF indication may also be referred to as type-4 BH RLF indication. The BH RLF indication may be carried by a BAP control PDU, and an IAB node may use the BAP control PDU to notify its child IAB node of a failure in the recovery of the wireless link between the IAB node and its parent IAB node.

[0031] For example, suppose the IAB network topology is:

[0032] IAB node 1->IAB node 2->IAB node 3->IAB-donor-DU->IAB-donor-CU

[0033] If an RLF occurs on the link between IAB node 2 and its parent node IAB node 3 and RLF recovery fails, IAB node 2 may send a BH RLF indication to its child node IAB node 1 to inform the IAB node 2 that a problem occurs on the link between IAB node 2 and IAB node 3.

[0034] Additionally, there are two BAP control PDU types:

[0035] 1) type-2BH RLF indication: When an IAB node experiences a radio link failure with its parent IAB node, it can notify the child IAB node of the RLF through type-2BH RLF indication;

[0036] 2) type-3BH RLF indication: After an IAB node's radio link with its parent IAB node fails but the radio link recovers successfully, the IAB node can use type-3BH RLF indication to notify the child IAB node of the RLF recovery success.

[0037] Optionally, the “deactivated state” described in the embodiments of the present application may also be referred to as a pending state or a paused state.

[0038] Optionally, the indication that the backhaul link has returned to normal in the embodiment of the present application may include at least one of the following: type 3 backhaul RLF indication, an indication that the backhaul link has returned to normal sent by the higher layer of the IAB node (such as the RRC layer, the RLC layer) to the MAC layer.

[0039] The following describes in detail the uplink transmission control method provided by the embodiment of the present application through some embodiments and their application scenarios in combination with the accompanying drawings.

[0040] See also Figure 3 , Figure 3 is a flow chart of a method for controlling uplink transmission provided in an embodiment of the present application, the method is executed by an IAB node, the IAB node is a terminal, such as Figure 3 As shown, the method comprises the following steps:

[0041] Step 31: The IAB node receives the returned RLF indication.

[0042] Optionally, the return RLF indication received by the IAB node may be carried by a BAP control PDU. The return RLF indication may include any one of the following: type-2 return RLF indication, type-4 return RLF indication. That is, the return RLF indication received by the IAB node may be type-2 return RLF indication or type-4 return RLF indication.

[0043] Step 32: The IAB node cancels or suspends the triggered data transmission.

[0044] Optionally, the triggered data transmission may be referred to as triggered uplink data transmission. The triggered data transmission may include at least one of the following: a triggered scheduling request (SR), a triggered buffer status report (BSR), a triggered preemptive buffer status report (PBSR), etc.

[0045] In the uplink transmission control method of the embodiment of the present application, after receiving the return RLF indication, the IAB node 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.

[0046] The present application is described in detail below using SR, BSR and PBSR as examples.

[0047] (1) SR triggered by RLF indication processing

[0048] In the embodiment of the present application, the returned RLF indication, for example, type-2 / type-4 returned RLFindication, can be used to cancel or suspend the triggered SR.

[0049] Optionally, when the IAB node receives a backhaul RLF indication on the backhaul link between the IAB node and its parent IAB node, the IAB node may cancel or suspend the first SR, wherein the first SR is a pending SR triggered by a BSR to be sent to the parent IAB node. The above suspension of the first SR may be understood as deactivating the first SR.

[0050] Further, when the first SR is canceled or suspended, when a first timer corresponding to the first SR is running, the IAB node may stop running the first timer, such as sr-ProhibitTimer.

[0051] Further, after suspending the first SR, when receiving an indication that the backhaul link has returned to normal, the IAB node may resume the suspended first SR.

[0052] Further, after suspending the first SR and stopping the first timer, when receiving an indication that the backhaul link has returned to normal, the IAB node may restart the first timer and set the value of the first timer to the remaining time value corresponding to when the first timer was suspended, or set the value of the first timer to the timer initial value. The timer initial value may be agreed upon by the protocol or configured by the network side device, and there is no restriction on this.

[0053] For example, assuming that the first timer sr-ProhibitTimer is 64ms in total and counts down to 30ms before stopping, there are two situations for recovery after stopping: 1) setting the value of sr-ProhibitTimer to 64ms and counting down from 64ms again; 2) setting the value of sr-ProhibitTimer to 30ms and counting down from 30ms when stopping.

[0054] Optionally, when the MAC entity of the IAB node does not have valid uplink resources configured for the first SR, the first SR will not trigger a random access (RACH) process before the IAB node receives an indication that the backhaul link has returned to normal. For example, the uplink resource may be a physical uplink control channel (PUCCH) resource.

[0055] Optionally, when the data to be sent that triggers the BSR to be sent to the parent IAB node includes an RLC control PDU, which includes, for example, an RLC status report, the first SR will not be canceled or suspended, that is, the first SR will not be canceled or suspended to ensure the sending of the RLC status report.

[0056] For example, if the IAB node receives a type-2 backhaul RLFindication on the backhaul link between the IAB node and its parent IAB node, all pending SRs triggered by the BSR to be sent to the parent IAB node may be canceled, and the timer sr-ProhibitTimer corresponding to each SR needs to be stopped (if the timer is running).

[0057] For another example, if the IAB node receives a type-2 backhaul RLFindication on the backhaul link between the IAB node and its parent IAB node, then for pending SRs triggered by the BSR to be sent to the parent IAB node, the subsequent processing of the pending SRs is suspended / deactivated, which directly indicates to stop processing the pending SRs, and the timer sr-ProhibitTimer corresponding to each SR needs to be stopped (if the timer is running).

[0058] For another example, if the IAB node receives a type-2 backhaul RLF indication on the backhaul link between the IAB node and its parent IAB node, the pending SRs triggered by the BSR to be sent to the parent IAB node still follow the legacy process, that is, wait to be processed, which indirectly indicates the deactivation / stop of the operation of processing the pending SRs. In addition, the pending SRs will not trigger the RACH process before the IAB node receives an indication that the backhaul link has returned to normal. In other words, if the IAB node receives a type-2 backhaul RLF indication on the backhaul link between the IAB node and its parent IAB node, the pending SRs triggered by the BSR to be sent to the parent IAB node will not trigger the RACH process before receiving an indication from the upper layer that the backhaul link has returned to normal. Among them, before receiving an indication from the upper layer that the backhaul link has returned to normal, the backhaul link that triggered the type-2 backhaul RLF indication has not returned to normal, that is, if the indication from the upper layer that the backhaul link has returned to normal is received, it indicates that the backhaul link that triggered the type-2 backhaul RLF indication has returned to normal.

[0059] For another example, after suspending / deactivating pending SRs, if the IAB node receives an indication from a higher layer that the backhaul link has returned to normal, that is, "the backhaul link that previously received the type-2 backhaul RLF indication has returned to normal", the operation of suspending / deactivating pending SRs can be resumed, that is, the pending SRs that were previously stopped due to receiving the type-2 backhaul RLF indication can be resumed. And if the pending SRs previously triggered a timer, the timer is restarted, and the timer value is set to the remaining time corresponding to the timer when it was suspended / deactivated, or to the initial value of the timer.

[0060] Optionally, when the IAB node receives a backhaul RLF indication on the backhaul link between the IAB node and its parent IAB node, the IAB node may cancel or suspend the second SR, wherein the second SR is not a pending SR triggered by a BSR to be sent to the parent IAB node. The suspension of the second SR may also be referred to as deactivating the second SR.

[0061] Further, when the second SR is canceled or suspended, when the second timer corresponding to the second SR is running, the IAB node may stop running the second timer, such as sr-ProhibitTimer.

[0062] Further, after suspending the second SR, when receiving an indication that the backhaul link has returned to normal, the IAB node may resume the suspended second SR.

[0063] Further, after suspending the second SR and stopping the second timer, when receiving an indication that the backhaul link has returned to normal, the IAB node may restart the second timer and set the value of the second timer to the remaining time value corresponding to when the second timer was suspended, or set the value of the second timer to the timer initial value. The timer initial value may be agreed upon by the protocol or configured by the network side device, and there is no restriction on this.

[0064] For example, assuming that the second timer sr-ProhibitTimer is 32ms in total and counts down to 20ms before stopping, there are two situations for recovery after stopping: 1) setting the value of sr-ProhibitTimer to 32ms and counting down from 32ms again; 2) setting the value of sr-ProhibitTimer to 20ms and counting down from 20ms when stopping.

[0065] For example, if an IAB node receives a type-2 backhaul RLFindication on the backhaul link between the IAB node and its parent IAB node, all pending SRs that are not triggered by a BSR to be sent to the parent IAB node may be canceled, and the timer sr-ProhibitTimer corresponding to each SR needs to be stopped (if the timer is running).

[0066] For another example, if the IAB node receives a type-2 backhaul RLFindication on the backhaul link between the IAB node and its parent IAB node, then for those pending SRs that are not triggered by the BSR to be sent to the parent IAB node, the subsequent processing of the pending SRs is suspended / deactivated before receiving the indication that the backhaul link is restored to normal, and the timer sr-ProhibitTimer corresponding to each SR needs to be stopped (if the timer is running).

[0067] For another example, after suspending / deactivating pending SRs, if the IAB node receives an indication from a higher layer that the backhaul link has returned to normal, that is, "the backhaul link that previously received the type-2 backhaul RLF indication has returned to normal", the operation of suspending / deactivating pending SRs can be resumed, that is, the pending SRs that were previously stopped due to receiving the type-2 backhaul RLF indication can be resumed. And if the pending SRs previously triggered a timer, the timer is restarted, and the timer value is set to the remaining time corresponding to the timer when it was suspended / deactivated, or to the initial value of the timer.

[0068] It should be noted that the above-mentioned indication that the backhaul link has returned to normal may include at least one of the following: type-3 backhaul RLF indication, an indication that the backhaul link has returned to normal sent by the upper layer of the IAB node to the MAC layer. The indication that the backhaul link has returned to normal sent by the upper layer to the MAC layer can be understood as an inter-layer indication by the upper layer to inform the MAC layer that the backhaul link has returned to normal.

[0069] In addition, in other cases where the IAB node does not receive the type-2 RLF indication, the triggered SR is processed according to the legacy process.

[0070] (2) BSR triggered by RLF indication processing

[0071] In the embodiment of the present application, the returned RLF indication, for example, type-2 / type-4 returned RLFindication, can be used to cancel or suspend a triggered BSR.

[0072] Optionally, when the IAB node receives a backhaul RLF indication on the backhaul link between the IAB node and its parent IAB node, the IAB node may cancel or suspend the first BSR. The first BSR is a BSR that is triggered and not canceled based on the BSR process. The suspension of the first BSR may also be referred to as deactivating the first BSR.

[0073] It should be noted that the first BSR can be a regular BSR or a periodic BSR. For a regular BSR, if a type-2 return RLF indication is not received, the legacy process is followed. For a regular BSR, if a type-2 return RLF indication is received and a type-3 return RLF indication is not received, it means that the regular BSR is still in an inactive state and cannot trigger an SR; if a type-2 return RLF indication is received and a type-3 return RLF indication is received, it means that the regular BSR has returned to normal and can trigger an SR.

[0074] It is understandable that since the padding BSR is when there is excess uplink grant (UL grant), the UE uses the remaining bits to report the BSR situation to the network side device. Therefore, the padding BSR only appears when there are surplus resources, and there is no need to cancel the padding BSR. Therefore, when the first BSR is the padding BSR, the first BSR will not be canceled or suspended.

[0075] Further, when the first BSR is canceled or suspended, when the third timer corresponding to the first BSR is running, the IAB node may stop running the third timer. Wherein, when the first BSR is a regular BSR, the third timer is a retransmission timer, such as retxBSR-Timer. Or, when the first BSR is a periodic BSR, the third timer is a periodic timer, such as periodicalBSR-Timer.

[0076] Further, when the first BSR is suspended, upon receiving an indication that the backhaul link is restored to normal, the IAB node may resume the suspended first BSR.

[0077] Further, after suspending the first BSR and stopping the third timer, when receiving an indication that the backhaul link has returned to normal, the IAB node may restart the third timer and set the value of the third timer to the remaining time value corresponding to when the third timer was suspended, or set the value of the third timer to the timer initial value. The timer initial value may be agreed upon by a protocol or configured by a network side device, and is not limited thereto.

[0078] For example, assuming that the third timer retxBSR-Timer has a total of 10 subframes and counts down to 5 subframes before stopping, there are two situations for recovery after stopping: 1) Set the value of retxBSR-Timer to 10 subframes and count down from 10 subframes again; 2) Set the value of retxBSR-Timer to 5 subframes and count down from 5 subframes when stopping.

[0079] It should be noted that the above-mentioned indication that the backhaul link has returned to normal may include at least one of the following: type-3 backhaul RLF indication, an indication that the backhaul link has returned to normal sent by the upper layer of the IAB node to the MAC layer. The indication that the backhaul link has returned to normal sent by the upper layer to the MAC layer can be understood as an inter-layer indication by the upper layer to inform the MAC layer that the backhaul link has returned to normal.

[0080] Optionally, when the data to be sent that triggers the first BSR includes an RLC control PDU, the RLC control PDU includes, for example, an RLC status report, and the first BSR will not be canceled or suspended, that is, the first SR will not be canceled or suspended to ensure the sending of the RLC status report.

[0081] Optionally, after receiving the backhaul RLF indication, the IAB node may stop triggering a new BSR and / or stop triggering a new SR; or, if the conditions for triggering the BSR are met, the IAB node may trigger a new BSR, and the triggered BSR is determined to be in a suspended state / pending state. For example, 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 that the UE has cached, there is no cached uplink data before the new data arrives, etc.

[0082] For example, if the IAB node receives a type-2 backhaul RLFindication on the backhaul link between the IAB node and its parent IAB node, and the BSR procedure determines that at least one BSR will be triggered and is not cancelled, the at least one BSR may be cancelled.

[0083] For another example, after receiving a type-2 backhaul RLF indication, the IAB node can still trigger a new BSR, but the BSR will be determined to be in a deactivated / suspended state, that is, the processing of the BSR will be stopped. Specifically, if the IAB node receives a type-2 backhaul RLF indication on the backhaul link between its parent IAB node, and has not received any indication from the upper layers that the link where the RLF occurred has returned to normal, and the BSR procedure determines that at least one BSR will be triggered and has not been canceled, then: 1) at least one BSR is determined to be a deactivated / suspended BSR, that is, the operation of at least one BSR is stopped, and the corresponding retxBSR-Timer or periodicaBSR-Timer (if the timer is running) is stopped; 2) optionally, no SR is triggered.

[0084] For another example, after suspending / deactivating the BSR, if the IAB node receives an indication from a higher layer that the backhaul link has returned to normal, that is, "the backhaul link that previously received the type-2 backhaul RLF indication has returned to normal", the operation of the previously suspended / deactivated BSR can be resumed, that is, the BSR that was previously stopped due to receiving the type-2 backhaul RLFindication can be resumed. And if the BSR previously triggered a timer, the timer corresponding to the BSR is restarted, and the timer value is set to the remaining time corresponding to the timer when it was deactivated, or to the initial value of the timer.

[0085] (3) PBSR triggered by RLF indication processing

[0086] In the embodiment of the present application, the returned RLF indication, for example, type-2 / type-4 returned RLFindication, can be used to cancel or suspend a triggered PBSR.

[0087] Optionally, when the IAB node receives a backhaul RLF indication on the backhaul link between the IAB node and its parent IAB node, the IAB node may cancel or suspend the first PBSR. The first PBSR is a PBSR that is triggered and not canceled based on the PBSR process. The suspension of the first PBSR may also be referred to as deactivating the first PBSR.

[0088] Further, when the first PBSR is suspended, upon receiving an indication that the backhaul link is restored to normal, the IAB node may resume the suspended first PBSR.

[0089] It should be noted that the above-mentioned indication that the backhaul link has returned to normal may include at least one of the following: type-3 backhaul RLF indication, an indication that the backhaul link has returned to normal sent by the upper layer of the IAB node to the MAC layer. The indication that the backhaul link has returned to normal sent by the upper layer to the MAC layer can be understood as an inter-layer indication by the upper layer to inform the MAC layer that the backhaul link has returned to normal.

[0090] For example, if the IAB node receives a type-2 backhaul RLFindication on the backhaul link between the IAB node and its parent IAB node, and the PBSR procedure determines that at least one PBSR will be triggered and is not cancelled, the at least one PBSR may be cancelled.

[0091] For another example, if the IAB node receives a type-2 backhaul RLFindication on the backhaul link between the IAB node and its parent IAB node, it stops triggering new PBSRs and processes the already triggered PBSRs according to the existing process.

[0092] For another example, after receiving a type-2 backhaul RLF indication, the IAB node can still trigger a new PBSR, but the PBSR will be determined to be in a deactivated / suspended state, that is, the processing of the PBSR will be stopped. Specifically, if the IAB node receives a type-2 backhaul RLF indication on the backhaul link between its parent IAB node, and has not received any indication from the upper layers that the link where the RLF occurred has returned to normal, and the PBSR procedure determines that at least one PBSR will be triggered and has not been canceled, 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, do not trigger any SR.

[0093] For another example, after suspending / deactivating the PBSR, if the IAB node receives an indication from a higher layer that the backhaul link has returned to normal, i.e., an indication that "the backhaul link that previously received the type-2 backhaul RLF indication has returned to normal", the operation of the previously suspended / deactivated PBSR can be resumed, i.e., the PBSR that had stopped operating due to receiving the type-2 backhaul RLFindication can be resumed.

[0094] In an embodiment of the present application, optionally, if the RLC layer of the IAB node indicates to the MAC layer that the data to be transmitted includes an RLCControl PDU, and the data to be transmitted triggers a second BSR, the second BSR will not be canceled or suspended after being triggered to ensure the sending of the RLC status report.

[0095] Further, if the resource size of the uplink grant (UL grant) of the IAB node is smaller than the resource size occupied by the second BSR, and the SR corresponding to the second BSR is triggered, the SR corresponding to the second BSR will not be cancelled or suspended after being triggered.

[0096] That is to say, if the RLC layer interacts with the MAC layer between layers, informs the MAC layer that the data to be transmitted currently includes the RLCControl PDU, and triggers the sending of the BSR, the triggered BSR will not be canceled / suspended in all subsequent operations; and when the BSR is sent, if the size of the UL grant is not sufficient to accommodate the sum of the BSR MAC control element (CE) and its subheader according to the logical channel priority (LCP) criterion, the SR corresponding to the BSR is triggered (and the SR is marked), then the SR will not be canceled / suspended in all subsequent operations.

[0097] Optionally, 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 will not be cancelled or suspended after being triggered. 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 includes the data to be transmitted on the LCH, the BSR will not be cancelled / suspended in all subsequent operations.

[0098] Optionally, when the LCH corresponding to the third SR to be processed is an LCH used to transmit RLC Control PDU, and / or the third BSR that triggers the third SR includes data to be sent in the first LCH, the third SR will not be canceled or suspended.

[0099] In the embodiment of the present application, after receiving the backhaul RLF indication, the IAB node may process the uplink transmission grant by at least one of the following:

[0100] The IAB node ignores the pre-configured uplink transmission grant, that is, does not use the pre-configured uplink transmission grant for uplink data transmission;

[0101] When there is a transmission demand for RLC control PDU, the IAB node uses the pre-configured uplink transmission grant to transmit the RLC control PDU, that is, the pre-configured uplink transmission grant can still be used to transmit the RLC control PDU;

[0102] The IAB node deactivates the pre-configured uplink transmission grant.

[0103] Further, after deactivating the preconfigured uplink transmission permission, when receiving an indication that the backhaul link has returned to normal, the IAB node may restore the preconfigured uplink transmission permission, or the IAB node may activate the preconfigured uplink transmission permission based on an indication of the parent IAB node of the IAB node to use the preconfigured uplink transmission permission for uplink data transmission.

[0104] It should be pointed out that the above-mentioned deactivation of the pre-configured uplink transmission permission means temporarily ignoring the pre-configured uplink transmission permission. For example, the network side configures a series / periodic configuration authorization (configured grant, CG) to the UE, and then the UE can directly transmit data on the time-frequency resources (CG) configured in advance by the network side; the meaning of "deactivation" here is that when a certain CG moment arrives, the UE can send data on the CG, but because it receives the backhaul RLF indication, it does not transmit data at the moment of the CG, but waits until the RLF backhaul link is successfully restored, and then uses the CG for data transmission. Furthermore, the meaning of the IAB node restoring the pre-configured uplink transmission permission means that the pre-configured uplink transmission permission is not ignored, that is, the pre-configured uplink transmission permission is used for data transmission.

[0105] It should be noted that the control method for uplink transmission provided in the embodiment of the present application can be executed by a control device for uplink transmission, or a control module in the control device for uplink transmission for executing the control method for uplink transmission. In the embodiment of the present application, the control device for uplink transmission provided in the embodiment of the present application is described by taking the control method for uplink transmission executed by the control device for uplink transmission as an example.

[0106] See also Figure 4 , Figure 4 is a schematic diagram of the structure of an uplink transmission control device provided in an embodiment of the present application, the device is applied to an IAB node, the IAB node is a terminal, such as Figure 4 As shown, the uplink transmission control device 40 includes:

[0107] A receiving module 41 is configured to receive a returned RLF indication;

[0108] The processing module 42 is used to cancel or pause the triggered data sending.

[0109] The control device for uplink transmission in the embodiment of the present application can cancel or suspend the triggered data transmission after receiving the return RLF indication, thereby realizing the processing of the triggered data transmission and ensuring the stability of data transmission in the IAB network.

[0110] Optionally, the triggered data sending includes at least one of the following:

[0111] The triggered scheduling request SR;

[0112] A triggered buffer status report BSR;

[0113] A preemptive buffer status report PBSR has been triggered.

[0114] Optionally, the feedback RLF indication includes any one of the following: type 2 feedback RLF indication, type 4 feedback RLF indication.

[0115] Optionally, the processing module 42 is further configured to perform any one of the following:

[0116] When the IAB node receives the backhaul RLF indication on the backhaul link between the IAB node and the parent IAB node of the IAB node, cancel or suspend the first SR; wherein the first SR is a pending SR triggered by a BSR to be sent to the parent IAB node;

[0117] When the IAB node receives the backhaul RLF indication on the backhaul link between the IAB node and the parent IAB node of the IAB node, the second SR is canceled or suspended; wherein the second SR is not a pending SR triggered by a BSR to be sent to the parent IAB node.

[0118] Optionally, when the MAC entity of the IAB node does not have valid uplink resources configured for the first SR, the first SR will not trigger a RACH process before the IAB node receives an indication that the backhaul link has returned to normal.

[0119] Optionally, the processing module 42 is further used for:

[0120] When the first SR is canceled or suspended, when a first timer corresponding to the first SR is running, the first timer is stopped.

[0121] Optionally, the processing module 42 is further used for:

[0122] When the second SR is canceled or suspended, when the second timer corresponding to the second SR is running, the second timer is stopped.

[0123] Optionally, when the data to be sent that triggers the BSR includes an RLC control PDU, the first SR will not be canceled or suspended.

[0124] Optionally, the processing module 42 is further used for:

[0125] After suspending the first SR, when receiving an indication that the backhaul link is restored to normal, resuming the suspended first SR.

[0126] Optionally, the processing module 42 is further used for:

[0127] After suspending the second SR, when receiving an indication that the backhaul link is restored to normal, resuming the suspended second SR.

[0128] Optionally, the processing module 42 is further used for:

[0129] After pausing the first SR and stopping the first timer, when receiving an indication that the backhaul link has returned to normal, restart the first timer and set the value of the first timer to the remaining time value corresponding to when the first timer was suspended, or set the value of the first timer to the initial value of the timer.

[0130] Optionally, the processing module 42 is further used for:

[0131] After pausing the second SR and stopping the second timer, when receiving an indication that the backhaul link has returned to normal, restart the second timer and set the value of the second timer to the remaining time value corresponding to when the second timer was suspended, or set the value of the second timer to the initial value of the timer.

[0132] Optionally, the processing module 42 is further used for:

[0133] When the IAB node receives the backhaul RLF indication on the backhaul link between the IAB node and the parent IAB node of the IAB node, the IAB node cancels or suspends the first BSR; wherein the first BSR is a BSR that will be triggered and not canceled based on a BSR process.

[0134] Optionally, when the first BSR is a BSR, the first BSR will not be cancelled or suspended.

[0135] Optionally, the processing module 42 is further used for:

[0136] When the first BSR is canceled or suspended, when a third timer corresponding to the first BSR is running, the third timer is stopped.

[0137] Optionally, 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.

[0138] Optionally, the processing module 42 is further used for:

[0139] After suspending the first BSR, when receiving an indication that the backhaul link has returned to normal, resuming the suspended first BSR.

[0140] Optionally, the processing module 42 is further used for:

[0141] After pausing the first BSR and stopping the third timer, when receiving an indication that the backhaul link has returned to normal, restart the third timer and set the value of the third timer to the remaining time value corresponding to when the third timer was suspended, or set the value of the third timer to the timer initial value.

[0142] Optionally, the processing module 42 is further used for:

[0143] When the IAB node receives the backhaul RLF indication on the backhaul link between the IAB node and the parent IAB node, the IAB node cancels or suspends the first PBSR; wherein the first PBSR is a PBSR that will be triggered and not canceled based on the PBSR process.

[0144] Optionally, the processing module 42 is further used for:

[0145] After suspending the first PBSR, when receiving an indication that the backhaul link is restored to normal, the suspended first PBSR is resumed.

[0146] Optionally, the indication that the backhaul link returns to normal includes at least one of the following:

[0147] Type 3 returns RLF indication;

[0148] The upper layer of the IAB node sends an indication to the MAC layer that the backhaul link has recovered to normal.

[0149] Optionally, the processing module 42 is further used for:

[0150] After receiving the backhaul RLF indication, stop triggering a new BSR and / or stop triggering a new SR;

[0151] or,

[0152] When the conditions for triggering a BSR are met, a new BSR is triggered, and the triggered BSR is determined to be in a suspended state.

[0153] Optionally, if the RLC layer of the IAB node indicates to the MAC layer that the data to be transmitted includes an RLC Control PDU, and the data to be transmitted triggers a second BSR, then the second BSR will not be cancelled or suspended after being triggered.

[0154] Optionally, if the SR corresponding to the second BSR is triggered when the resource size of the uplink authorization of the IAB node is smaller than the resource size occupied by the second BSR, the SR corresponding to the second BSR will not be cancelled or suspended after being triggered.

[0155] Optionally, the RLC Control PDU of the IAB node can only be transmitted through the first logical channel LCH, and when the data to be sent that triggers the third BSR includes the data to be transmitted in the first LCH, the third BSR will not be cancelled or suspended after being triggered;

[0156] or,

[0157] When 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 third SR will not be canceled or suspended.

[0158] Optionally, the processing module 42 is further used for:

[0159] After receiving the returned RLF indication, perform at least one of the following:

[0160] Ignore pre-configured uplink transmission permissions;

[0161] When there is a transmission demand for the RLC control PDU, transmitting the RLC control PDU using a pre-configured uplink transmission grant;

[0162] Deactivate the pre-configured uplink transmission grant.

[0163] Optionally, the processing module 42 is further used for:

[0164] After deactivating the preconfigured uplink transmission grant, when receiving an indication that the backhaul link is restored to normal, the preconfigured uplink transmission grant is restored, or based on an indication of a parent IAB node of the IAB node, the preconfigured uplink transmission grant is activated.

[0165] The control device for uplink transmission in the embodiment of the present application may be a device, a device or an electronic device with an operating system, or a component, an integrated circuit, or a chip in a terminal. The device or electronic device may be a mobile terminal or a non-mobile terminal. Exemplarily, 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 (NAS), a personal computer (PC), a television (TV), a teller machine or a self-service machine, etc., which is not specifically limited in the embodiment of the present application.

[0166] The control device for uplink transmission provided in the embodiment of the present application can achieve Figure 3 The various processes implemented by the method embodiment and achieving the same technical effect are not described here to avoid repetition.

[0167] Alternatively, if Figure 5 As shown, an embodiment of the present application also provides a terminal 500, which is an IAB node, including a processor 501, a memory 502, and a program or instruction stored in the memory 502 and executable on the processor 501. When the program or instruction is executed by the processor 501, each process of the above-mentioned uplink transmission control method embodiment is implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0168] The embodiment of the present application also provides a terminal, which is an IAB node, including a processor and a communication interface, the communication interface is used to receive the returned RLF indication, and the processor is used to cancel or suspend the triggered data transmission. Figure 3 Corresponding to the method embodiment shown, each implementation process and implementation method of the above method embodiment can be applied to the terminal embodiment and can achieve the same technical effect.

[0169] Specifically, Figure 6 A schematic diagram of the hardware structure of a terminal for implementing an embodiment of the present application.

[0170] 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 at least some of the components of a processor 610.

[0171] Those skilled in the art will appreciate that 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, thereby implementing functions such as managing charging, discharging, and power consumption management through the power management system. Figure 6 The terminal structure shown in the figure does not constitute a limitation on the terminal. The terminal may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently, which will not be described in detail here.

[0172] It should be understood that in the embodiment of the present application, the input unit 604 may include a graphics processor (Graphics Processing Unit, GPU) 6041 and a microphone 6042, and the graphics processor 6041 processes the image data of the static picture or video obtained by the image capture device (such as a camera) in the video capture mode or the image capture mode. The display unit 606 may include a display panel 6061, and the display panel 6061 may be configured in the form of a liquid crystal display, an organic light emitting diode, etc. 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, a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, and a joystick, which will not be repeated here.

[0173] In the embodiment of the present application, the radio frequency unit 601 receives downlink data from the network side device and sends it to the processor 610 for processing; in addition, the uplink data is sent to the network side device. Generally, 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, etc.

[0174] The memory 609 can be used to store software programs or instructions and various data. The memory 609 can mainly include a program or instruction storage area and a data storage area, wherein the program or instruction storage area can 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.), etc. In addition, the memory 609 can include a high-speed random access memory, and can also include a non-volatile memory, wherein the non-volatile memory can be a read-only memory (Read-Only Memory, ROM), a programmable read-only memory (Programmable ROM, PROM), an erasable programmable read-only memory (Erasable PROM, EPROM), an electrically erasable programmable read-only memory (Electrically EPROM, EEPROM) or a flash memory. For example, at least one disk storage device, a flash memory device, or other non-volatile solid-state storage devices.

[0175] 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 an operating system, a user interface, and application programs or instructions, etc., and the modem processor mainly processes wireless communications, such as a baseband processor. It is understandable that the modem processor may not be integrated into the processor 610.

[0176] The radio frequency unit 601 is used to: receive a returned RLF indication;

[0177] The processor 610 is used to cancel or pause the triggered data transmission.

[0178] Based on the solution in this embodiment, after receiving the return RLF indication, the triggered data transmission can be canceled or suspended, thereby realizing the processing of the triggered data transmission and ensuring the stability of data transmission in the IAB network.

[0179] Optionally, the triggered data sending includes at least one of the following:

[0180] The triggered scheduling request SR;

[0181] A triggered buffer status report BSR;

[0182] A preemptive buffer status report PBSR has been triggered.

[0183] Optionally, the feedback RLF indication includes any one of the following: type 2 feedback RLF indication, type 4 feedback RLF indication.

[0184] Optionally, the processor 610 is further configured to perform any one of the following:

[0185] When the terminal 600 receives the backhaul RLFindication on the backhaul link between the terminal 600 and the parent IAB node, cancel or suspend the first SR; wherein the first SR is a pending SR triggered by a BSR to be sent to the parent IAB node;

[0186] When the terminal 600 receives the backhaul RLFindication on the backhaul link between the terminal 600 and the parent IAB node, the second SR is canceled or suspended; wherein the second SR is not a pending SR triggered by a BSR to be sent to the parent IAB node.

[0187] Optionally, when the MAC entity of the terminal 600 does not have valid uplink resources configured for the first SR, the first SR will not trigger the RACH process before the terminal 600 receives an indication that the backhaul link has returned to normal.

[0188] Optionally, the processor 610 is further configured to:

[0189] When the first SR is canceled or suspended, when a first timer corresponding to the first SR is running, the first timer is stopped.

[0190] Optionally, the processor 610 is further configured to:

[0191] When the second SR is canceled or suspended, when the second timer corresponding to the second SR is running, the second timer is stopped.

[0192] Optionally, when the data to be sent that triggers the BSR includes an RLC control PDU, the first SR will not be canceled or suspended.

[0193] Optionally, the processor 610 is further configured to:

[0194] After suspending the first SR, when receiving an indication that the backhaul link is restored to normal, resuming the suspended first SR.

[0195] Optionally, the processor 610 is further configured to:

[0196] After suspending the second SR, when receiving an indication that the backhaul link is restored to normal, resuming the suspended second SR.

[0197] Optionally, the processor 610 is further configured to:

[0198] After pausing the first SR and stopping the first timer, when receiving an indication that the backhaul link has returned to normal, restart the first timer and set the value of the first timer to the remaining time value corresponding to when the first timer was suspended, or set the value of the first timer to the initial value of the timer.

[0199] Optionally, the processor 610 is further configured to:

[0200] After pausing the second SR and stopping the second timer, when receiving an indication that the backhaul link has returned to normal, restart the second timer and set the value of the second timer to the remaining time value corresponding to when the second timer was suspended, or set the value of the second timer to the initial value of the timer.

[0201] Optionally, the processor 610 is further configured to:

[0202] When the terminal 600 receives the backhaul RLFindication on the backhaul link between the terminal 600 and the parent IAB node, the first BSR is canceled or suspended; wherein the first BSR is a BSR that is triggered and not canceled based on the BSR process.

[0203] Optionally, when the first BSR is a BSR, the first BSR will not be cancelled or suspended.

[0204] Optionally, the processor 610 is further configured to:

[0205] When the first BSR is canceled or suspended, when a third timer corresponding to the first BSR is running, the third timer is stopped.

[0206] Optionally, 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.

[0207] Optionally, the processor 610 is further configured to:

[0208] After suspending the first BSR, when receiving an indication that the backhaul link has returned to normal, resuming the suspended first BSR.

[0209] Optionally, the processor 610 is further configured to:

[0210] After pausing the first BSR and stopping the third timer, when receiving an indication that the backhaul link has returned to normal, restart the third timer and set the value of the third timer to the remaining time value corresponding to when the third timer was suspended, or set the value of the third timer to the timer initial value.

[0211] Optionally, the processor 610 is further configured to:

[0212] When the terminal 600 receives the backhaul RLFindication on the backhaul link between the terminal 600 and the parent IAB node, the first PBSR is canceled or suspended; wherein the first PBSR is a PBSR that is triggered and not canceled based on the PBSR process.

[0213] Optionally, the processor 610 is further configured to:

[0214] After suspending the first PBSR, when receiving an indication that the backhaul link is restored to normal, the suspended first PBSR is resumed.

[0215] Optionally, the indication that the backhaul link returns to normal includes at least one of the following:

[0216] Type 3 returns RLF indication;

[0217] An indication that the backhaul link of terminal 600 is restored to normal is sent to the MAC layer by the higher layer of terminal 600.

[0218] Optionally, the processor 610 is further configured to:

[0219] After receiving the backhaul RLF indication, stop triggering a new BSR and / or stop triggering a new SR;

[0220] Alternatively, when the condition for triggering the BSR is met, a new BSR is triggered, and the triggered BSR is determined to be in the suspended state.

[0221] Optionally, if the RLC layer of the terminal 600 indicates to the MAC layer that the data to be transmitted includes an RLC Control PDU, and the data to be transmitted triggers a second BSR, then the second BSR will not be cancelled or suspended after being triggered.

[0222] Optionally, if the SR corresponding to the second BSR is triggered when the resource size of the uplink authorization of the terminal 600 is smaller than the resource size occupied by the second BSR, the SR corresponding to the second BSR will not be cancelled or suspended after being triggered.

[0223] Optionally, the RLC Control PDU of the terminal 600 can only be transmitted through the first logical channel LCH, and when the data to be sent that triggers the third BSR includes the data to be transmitted in the first LCH, the third BSR will not be cancelled or suspended after being triggered;

[0224] or,

[0225] When 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 third SR will not be canceled or suspended.

[0226] Optionally, the processor 610 is further configured to:

[0227] After receiving the returned RLF indication, perform at least one of the following:

[0228] Ignore pre-configured uplink transmission permissions;

[0229] When there is a transmission demand for the RLC control PDU, transmitting the RLC control PDU using a pre-configured uplink transmission grant;

[0230] Deactivate the pre-configured uplink transmission grant.

[0231] Optionally, the processor 610 is further configured to:

[0232] After deactivating the preconfigured uplink transmission grant, when receiving an indication that the backhaul link is restored to normal, the preconfigured uplink transmission grant is restored, or based on an indication of a parent IAB node of the terminal 600, the preconfigured uplink transmission grant is activated.

[0233] The embodiment of the present application also provides a readable storage medium on which a program or instruction is stored. When the program or instruction is executed by a processor, the above Figure 3 The various processes of the method embodiment shown can achieve the same technical effect, and will not be described again here to avoid repetition.

[0234] The processor is the processor in the terminal described in the above embodiment. The readable storage medium includes a computer readable storage medium, such as a computer read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0235] The present application also provides a chip, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run a program or instruction to implement the above Figure 3 The various processes of the method embodiment shown can achieve the same technical effect, and will not be described again here to avoid repetition.

[0236] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0237] It should be noted that, in this article, the terms "comprise", "include" or any other variant thereof are intended to cover non-exclusive inclusion, so that the process, method, article or device including a series of elements includes not only those elements, but also includes other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise one..." do not exclude the presence of other identical elements in the process, method, article or device including the element. In addition, it should be pointed out that the scope of the methods and devices in the embodiments of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in reverse order according to the functions involved, for example, the described method may be performed in an order different from that described, and various steps may also be added, omitted, or combined. In addition, the features described with reference to certain examples may be combined in other examples.

[0238] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present application, or the part that contributes to the prior art, can be embodied in the form of a computer software product, which is stored in a storage medium (such as ROM / RAM, a magnetic disk, or an optical disk), and includes a number of instructions for enabling a terminal (which can be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to execute the methods described in each embodiment of the present application.

[0239] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of the present application, ordinary technicians in this field can also make many forms without departing from the purpose of the present application and the scope of protection of the claims, all of which are within the protection of the present application.

Claims

1. A method for controlling uplink transmission, characterized in that: include: The integrated access backhaul IAB node receives the backhaul radio link failure indication RLF indication; The IAB node cancels or suspends the triggered data transmission; The triggered data transmission includes at least one of the following: The triggered scheduling request SR; A triggered buffer status report BSR; The triggered preemptive buffer status report PBSR; The canceling or suspending the triggered data transmission includes at least one of the following: When the IAB node receives the backhaul RLFindication on the backhaul link between the IAB node and the parent IAB node of the IAB node, the IAB node performs any one of the following: canceling or suspending the first SR, canceling or suspending the second SR; wherein the first SR is a pending SR triggered by a BSR to be sent to the parent IAB node, and the second SR is not a pending SR triggered by a BSR to be sent to the parent IAB node; When the IAB node receives the backhaul RLFindication on the backhaul link between the IAB node and the parent IAB node of the IAB node, the IAB node cancels or suspends the first BSR; wherein the first BSR is a BSR that will be triggered and not canceled based on the BSR process; When the IAB node receives the backhaul RLFindication on the backhaul link between the IAB node and its parent IAB node, the IAB node cancels or suspends a first PBSR; wherein the first PBSR is a PBSR that is triggered and not canceled based on a PBSR process.

2. The method according to claim 1, characterized in that The feedback RLF indication includes any one of the following: type 2 feedback RLF indication, type 4 feedback RLF indication.

3. The method according to claim 1, characterized in that When the media access control MAC entity of the IAB node does not have valid uplink resources configured for the first SR, the first SR will not trigger a random access RACH process before the IAB node receives an indication that the backhaul link is restored to normal.

4. The method according to claim 1, characterized in that: When canceling or suspending the first SR, the method further includes: When a first timer corresponding to the first SR is running, the IAB node stops running the first timer; or, When canceling or suspending the second SR, the method further includes: When the second timer corresponding to the second SR is running, the IAB node stops running the second timer.

5. The method according to claim 1, characterized in that When the data to be sent that triggers the BSR includes a radio link control RLC control protocol data unit PDU, the first SR will not be cancelled or suspended.

6. The method according to claim 1, characterized in that After pausing the first SR, the method further includes: When receiving an indication that the backhaul link is restored to normal, the IAB node resumes the suspended first SR; or, After pausing the second SR, the method further includes: When receiving an indication that the backhaul link is restored to normal, the IAB node resumes the suspended second SR.

7. The method according to claim 4, characterized in that After pausing the first SR and stopping the first timer, the method further includes: When receiving an indication that the backhaul link has returned to normal, the IAB node restarts the first timer and sets the value of the first timer to the remaining time value corresponding to when the first timer was suspended, or sets the value of the first timer to the timer initial value; or, After pausing the second SR and stopping the second timer, the method further includes: When receiving an indication that the backhaul link has returned to normal, the IAB node restarts the second timer and sets the value of the second timer to the remaining time value corresponding to when the second timer was suspended, or sets the value of the second timer to the timer initial value.

8. The method according to claim 1, characterized in that When the first BSR is a filling BSR, the first BSR will not be cancelled or suspended.

9. The method according to claim 1, characterized in that: When canceling or suspending the first BSR, the method further includes: When a third timer corresponding to the first BSR is running, the IAB node stops running the third timer.

10. The method according to claim 1, characterized in that When the data to be sent that triggers the first BSR includes an RLC control PDU, the first BSR will not be cancelled or suspended.

11. The method according to claim 1, characterized in that: After suspending the first BSR, the method further includes: When receiving an indication that the backhaul link is restored to normal, the IAB node resumes the suspended first BSR.

12. The method according to claim 9, characterized in that After suspending the first BSR and stopping running the third timer, the method further includes: When receiving an indication that the backhaul link has returned to normal, the IAB node restarts the third timer and sets the value of the third timer to the remaining time value corresponding to when the third timer was suspended, or sets the value of the third timer to the timer initial value.

13. The method according to claim 1, characterized in that After pausing the first PBSR, the method further comprises: When receiving an indication that the backhaul link is restored to normal, the IAB node resumes the suspended first PBSR.

14. The method according to any one of claims 6, 7, 11, 12 and 13, characterized in that The indication that the backhaul link returns 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 has recovered to normal.

15. The method according to claim 1, characterized in that After receiving the returned RLF indication, the method further includes: The IAB node stops triggering new BSRs and / or stops triggering new SRs; or, When the condition for triggering the BSR is met, the IAB node triggers a new BSR, and the triggered BSR is determined to be in a suspended state.

16. The method according to claim 1, characterized in that If the RLC layer of the IAB node indicates to the MAC layer that the data to be transmitted includes an RLC Control PDU, and the data to be transmitted triggers a second BSR, then the second BSR will not be cancelled or suspended after being triggered.

17. The method according to claim 15, characterized in that If the resource size of the uplink authorization of the IAB node is smaller than the resource size occupied by the second BSR, and the SR corresponding to the second BSR is triggered, the SR corresponding to the second BSR will not be cancelled or suspended after being triggered.

18. The method according to claim 1, characterized in that The RLC Control PDU of the IAB node can only be transmitted through the first logical channel LCH, and when the data to be sent that triggers the third BSR includes the data to be transmitted in the first LCH, the third BSR will not be cancelled or suspended after being triggered; or, When 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 third SR will not be canceled or suspended.

19. The method according to claim 1, characterized in that After receiving the returned RLF indication, the method further includes at least one of the following: The IAB node ignores the pre-configured uplink transmission permission; When there is a transmission demand for the RLC control PDU, the IAB node transmits the RLC control PDU using a pre-configured uplink transmission grant; The IAB node deactivates the preconfigured uplink transmission grant.

20. The method according to claim 19, characterized in that After deactivating the preconfigured uplink transmission grant, the method further includes: When receiving an indication that the backhaul link has returned to normal, the IAB node restores the pre-configured uplink transmission grant, or the IAB node activates the pre-configured uplink transmission grant based on an indication of a parent IAB node of the IAB node.

21. A control device for uplink transmission, characterized in that: include: A receiving module is used to receive the returned RLF indication; A processing module, used to cancel or pause the triggered data sending; The triggered data transmission includes at least one of the following: Triggered SR; Triggered BSR; Triggered PBSR; The processing module is further configured to perform at least one of the following: When the IAB node receives the backhaul RLFindication on the backhaul link between the IAB node and the parent IAB node of the IAB node, perform any one of the following: cancel or suspend the first SR, cancel or suspend the second SR; wherein the first SR is a pending SR triggered by a BSR to be sent to the parent IAB node, and the second SR is not a pending SR triggered by a BSR to be sent to the parent IAB node; When the IAB node receives the backhaul RLFindication on the backhaul link between the IAB node and the parent IAB node of the IAB node, cancel or suspend the first BSR; wherein the first BSR is a BSR that will be triggered and not canceled based on the BSR process; When the IAB node receives the backhaul RLFindication on the backhaul link between the IAB node and the parent IAB node, the first PBSR is canceled or suspended; wherein the first PBSR is a PBSR that is triggered and not canceled based on the PBSR process.

22. A terminal, characterized in that: The terminal is an IAB node, including a processor, a memory, and a program or instruction stored in the memory and executable on the processor. When the program or instruction is executed by the processor, the steps of the uplink transmission control method according to any one of claims 1 to 20 are implemented.

23. A readable storage medium, characterized in that: The readable storage medium stores a program or instruction, and when the program or instruction is executed by the processor, the steps of the uplink transmission control method according to any one of claims 1 to 20 are implemented.

Images