Beam failure recovery methods, devices and storage media

Abstract

This disclosure relates to a beam failure recovery method, apparatus, and storage medium. The beam failure recovery method, applied to a network device, includes: the network device determining that a terminal is configured for multiple transmit / receive point (TRP) operation; the network device configuring reference signal resources for the terminal, the reference signal resources being used for beam failure detection. This disclosure enables timely beam failure recovery based on random access in multiple TRP scenarios, ensuring the timeliness and effectiveness of beam failure recovery.

Description

[0001] This disclosure is a divisional application of application number 202180001833.8, entitled "Beam Failure Recovery Method, Apparatus and Storage Medium". Technical Field

[0002] This disclosure relates to the field of communication technology, and in particular to beam failure recovery methods, apparatus and storage media. Background Technology

[0003] In New Radio (NR) technologies, such as communication bands in frequency range 2, beam-based transmission and reception are required to ensure coverage due to the rapid attenuation of high-frequency channels.

[0004] In related technologies, network devices are configured with multiple transmission and reception points (TRPs). When a network device has multiple TRPs, it can use these TRPs to provide services to the terminal, for example, by using multiple TRPs to send physical downlink control channels (PDCCHs) to the terminal. The network device uses TRPs to send PDCCHs to the terminal, and the terminal detects reference signal resources used for failure detection. When the terminal detects that the radio link value of the reference signal used for failure detection is below a threshold, the terminal needs to initiate a beam failure recovery (BFR) request to the network device to perform BFR.

[0005] In related technologies, cell-level beamforming recovery (BFR) is defined. For example, a BFR for a special cell (SpCell) is defined. A special cell includes a primary cell (Pcell) and a primary secondary cell (PScell). The BFR mechanism for SpCell is a random access BFR mechanism; when a terminal detects a beam failure in the SpCell, it initiates a random access procedure to request beam recovery. Another example is the BFR at the secondary cell (SCell) level, which uses a physical uplink control channel (PUCCH)-scheduling request (SR) mechanism and / or a physical uplink share channel (PUSCH)-Medium Access Control (MAC) control element (CE) mechanism. That is, when a terminal detects a beam failure in the Scell, it sends MAC CE information on the PUSCH resource to indicate beam failure recovery information. However, the PUSCH resource can be either the PUCCH-SR resource specifically used for BFR to send scheduling request requests, or other PUSCH resources.

[0006] In related technologies, a TRP-level BFR (TRP-specific BFR) has been proposed. This means that when a terminal is configured for Multi-TRP PDCCH transmission, if a beam failure occurs at a certain TRP, the terminal can send a beam failure recovery request to inform the network device of the TRP beam failure and request a BFR. Currently, TRP-specific BFRs have agreed to use SCell-based PUCCH-SR and / or PUSCH MAC CE mechanisms to implement beam failure recovery requests. However, a problem remains: for SpCell, if multiple TRPs experience beam failures, whether and how to trigger a beam failure recovery request based on random access is an issue that needs to be addressed. Summary of the Invention

[0007] To overcome the problems existing in related technologies, this disclosure provides a beam failure recovery method, apparatus and storage medium.

[0008] According to a first aspect of the present disclosure, a beam failure recovery method is provided, applied to a network device, the method comprising:

[0009] The network device determines that the terminal is configured for multiple transmit / receive point (TRP) operation; the network device configures reference signal resources for the terminal, the reference signal resources being used for beam failure detection; if a first TRP with beam failure exists among the multiple TRPs, and the triggering condition for triggering random access beam failure recovery is met, beam failure recovery based on random access is triggered, the beam failure recovery being used for beam failure recovery of the Spcell; wherein, the triggering condition for triggering random access beam failure recovery includes: before a fifth time, a second TRP with beam failure exists among the multiple TRPs; wherein, the fifth time is the time when the terminal receives second downlink control information sent by the network device, the second downlink control information being used to determine that the network device has received MAC CE information, the second downlink control information being used to schedule a second physical uplink shared channel; the hybrid automatic repeat request identifier of the second physical uplink shared channel scheduled by the second downlink control information is the same as the hybrid automatic repeat request identifier of the first physical uplink shared channel, wherein, the first physical uplink shared channel is used to send the Media Access Control Unit (MAC) associated with the TRP with beam failure. CE information; and / or a change in the new data indication of the second physical uplink shared channel scheduled by the second downlink control information. In one embodiment, satisfying the triggering condition for triggering random access beam failure recovery further includes: after a first time and before a second time, a second TRP among the plurality of TRPs has experienced beam failure; the first time characterizes the time when the terminal detects that the first TRP has experienced beam failure, and the second time characterizes the time when the terminal sends a scheduling request on the physical uplink control channel resource.

[0010] In one embodiment, satisfying the triggering condition for random access beam failure recovery further includes: before a third time, there exists a second TRP among the plurality of TRPs that has experienced beam failure; the third time characterizes the time when the terminal receives first downlink control information for scheduling the physical uplink shared channel. In another embodiment, satisfying the triggering condition for random access beam failure recovery further includes: within a first time period after a second time, no downlink control information is received; the second time characterizes the time when the terminal sends a scheduling request on the physical uplink control channel resource. In yet another embodiment, satisfying the triggering condition for random access beam failure recovery includes: before a fourth time, there exists a second TRP among the plurality of TRPs that has experienced beam failure; the fourth time characterizes the time when the terminal sends Media Access Control Unit (MAC CE) information related to the TRP that experienced beam failure on the first physical uplink shared channel.

[0011] In one embodiment, the triggering condition for triggering random access beam failure recovery further includes: the beam corresponding to the first physical uplink shared channel is the beam that experienced beam failure; wherein, the first physical uplink shared channel is a first downlink control information scheduling channel, or a physical uplink shared channel with configuration authorization type 1 or type 2. In another embodiment, the triggering condition for triggering random access beam failure recovery further includes: within a second duration after a fourth time period, the terminal does not receive any downlink control information, the fourth time period representing the time during which the terminal transmits Media Access Control Unit (MAC) CE information related to the TRP that experienced beam failure on the first physical uplink shared channel.

[0012] In one embodiment, the triggering condition for triggering random access beam failure recovery includes: before a sixth time, there is a second TRP among the plurality of TRPs that has experienced beam failure; the sixth time represents the time when the terminal updates the beam of the first TRP.

[0013] In one embodiment, the method further includes: triggering TRP-level beam failure recovery in response to the presence of a second TRP experiencing beam failure again among the plurality of TRPs after the sixth time.

[0014] In one implementation, the beam failure recovery at the TRP level includes:

[0015] Trigger beam failure recovery based on Physical Uplink Control Channel Scheduling Request (PUCCH-SR) and / or Physical Uplink Shared Channel Media Access Control (PUSCH MAC CE).

[0016] In one embodiment, the method further includes: triggering beam failure recovery at the TRP level, or not triggering beam failure recovery at the TRP level.

[0017] In one embodiment, configuring multiple TRPs for the terminal includes: configuring multiple sets of reference signal resources for the terminal for beam failure monitoring, and / or configuring multiple control resource pool index values ​​for the terminal.

[0018] According to a second aspect of the present disclosure, a beam failure recovery method is provided, comprising: a network device determining that a terminal is configured as a multiple transmit / receive point (TRP) operation; the network device configuring reference signal resources for the terminal, the reference signal resources being used for beam failure detection; in response to the terminal being configured with multiple TRPs, performing beam failure monitoring of the multiple TRPs; in response to detecting that a first TRP among the multiple TRPs has experienced beam failure, and satisfying a triggering condition for triggering random access beam failure recovery, the terminal triggering beam failure recovery based on random access, the beam failure recovery being used for beam failure recovery of SpCell; wherein satisfying the triggering condition for triggering random access beam failure recovery includes: before a fifth time period, a second TRP among the multiple TRPs has experienced beam failure; wherein the fifth time period is the time of receiving second downlink control information sent by the network device, the second downlink control information being used to determine that the network device has received MAC. CE information, the second downlink control information is used to schedule the second physical uplink shared channel; the hybrid automatic repeat request identifier of the second physical uplink shared channel scheduled by the second downlink control information is the same as the hybrid automatic repeat request identifier of the first physical uplink shared channel, wherein the first physical uplink shared channel is used to send Media Access Control Unit (MAC) CE information related to the TRP that has experienced beam failure; and / or the new data indication of the second physical uplink shared channel scheduled by the second downlink control information has changed.

[0019] In one embodiment, the triggering condition for triggering random access beam failure recovery further includes: after a first time and before a second time, there is a second TRP among the plurality of TRPs that has experienced beam failure; the first time represents the time when the terminal detects that the first TRP has experienced beam failure, and the second time represents the time when the terminal sends a scheduling request on the physical uplink control channel resource.

[0020] In one embodiment, the triggering condition for triggering random access beam failure recovery further includes: before a third time, there is a second TRP among the plurality of TRPs that has experienced beam failure; the third time characterizes the time when the terminal receives the first downlink control information for scheduling the physical uplink shared channel.

[0021] In one embodiment, the triggering condition for triggering random access beam failure recovery further includes: within a first duration after the second time, no downlink control information is received, whereby the second time characterizes the time during which the terminal sends a scheduling request on the physical uplink control channel resources.

[0022] In one embodiment, the triggering condition for triggering random access beam failure recovery includes: before a fourth time, there is a second TRP among the plurality of TRPs that has experienced beam failure; the fourth time characterizes the time when the terminal transmits Media Access Control Unit (MAC CE) information related to the TRP that experienced beam failure on the first physical uplink shared channel.

[0023] In one embodiment, the triggering condition for triggering random access beam failure recovery further includes: the beam corresponding to the first physical uplink shared channel is the beam that has experienced beam failure; wherein, the first physical uplink shared channel is a first downlink control information scheduling, or a physical uplink shared channel with configuration authorization of type 1 or type 2.

[0024] In one embodiment, the triggering condition for triggering random access beam failure recovery further includes: within a second duration after the fourth time, the terminal does not receive any downlink control information, wherein the fourth time characterizes the time during which the terminal transmits Media Access Control Unit (MAC CE) information related to the TRP that caused the beam failure on the first physical uplink shared channel.

[0025] In one embodiment, the triggering condition for triggering random access beam failure recovery includes: before a sixth time, there is a second TRP among the plurality of TRPs that has experienced beam failure; the sixth time represents the time when the terminal updates the beam of the first TRP.

[0026] In one embodiment, the method further includes: triggering TRP-level beam failure recovery in response to the presence of a second TRP experiencing beam failure again among the plurality of TRPs after the sixth time.

[0027] In one embodiment, triggering beam failure recovery at the TRP level includes: triggering beam failure recovery based on PUCCH-SR and / or PUSCH MAC CE.

[0028] In one embodiment, the method further includes: triggering beam failure recovery at the TRP level, or not triggering beam failure recovery at the TRP level. In another embodiment, configuring multiple TRPs for the terminal includes: configuring multiple sets of reference signal resources for beam failure monitoring for the terminal, and / or configuring multiple control resource pool index values ​​for the terminal.

[0029] According to a third aspect of the present disclosure, a beam failure recovery device is provided, comprising:

[0030] The monitoring unit is configured to determine that the terminal is configured as a multi-transmitter-receiver point (TRP) to configure reference signal resources for the terminal, the reference signal resources being used for beam failure detection; the processing unit is configured to trigger beam failure recovery based on random access when there is a first TRP in the multiple TRPs where beam failure occurs and the triggering condition for triggering random access beam failure recovery is met, the beam failure recovery being used for beam failure recovery of the Spcell;

[0031] The triggering conditions for triggering random access beam failure recovery include:

[0032] Before the fifth time, the monitoring unit detected a second TRP among the plurality of TRPs that had experienced beam failure using the following method;

[0033] Wherein, the fifth time is the time when the terminal receives the second downlink control information sent by the network device. The second downlink control information is used to determine that the network device has received MAC CE information and to schedule the second physical uplink shared channel. The hybrid automatic repeat request identifier of the second physical uplink shared channel scheduled by the second downlink control information is the same as the hybrid automatic repeat request identifier of the first physical uplink shared channel. The first physical uplink shared channel is used to send MAC CE information related to the TRP that has experienced beam failure. And / or the new data indication of the second physical uplink shared channel scheduled by the second downlink control information has changed.

[0034] In one embodiment, the triggering condition for triggering random access beam failure recovery further includes: after a first time and before a second time, there is a second TRP among the plurality of TRPs that has experienced beam failure; the first time represents the time when the terminal detects that the first TRP has experienced beam failure, and the second time represents the time when the terminal sends a scheduling request on the physical uplink control channel resource.

[0035] In one embodiment, the triggering condition for triggering random access beam failure recovery further includes: before a third time, there is a second TRP among the plurality of TRPs that has experienced beam failure; the third time characterizes the time when the terminal receives the first downlink control information for scheduling the physical uplink shared channel.

[0036] In one embodiment, the triggering condition for triggering random access beam failure recovery further includes: within a first duration after the second time, no downlink control information is received, whereby the second time characterizes the time during which the terminal sends a scheduling request on the physical uplink control channel resources.

[0037] In one embodiment, the triggering condition for triggering random access beam failure recovery includes: before a fourth time, there is a second TRP among the plurality of TRPs that has experienced beam failure; the fourth time characterizes the time when the terminal transmits Media Access Control Unit (MAC CE) information related to the TRP that experienced beam failure on the first physical uplink shared channel.

[0038] In one embodiment, the triggering condition for triggering random access beam failure recovery further includes: the beam corresponding to the first physical uplink shared channel is the beam that has experienced beam failure; wherein, the first physical uplink shared channel is a first downlink control information scheduling, or a physical uplink shared channel with configuration authorization of type 1 or type 2.

[0039] In one embodiment, the triggering condition for triggering random access beam failure recovery further includes: within a second duration after the fourth time, the terminal does not receive any downlink control information, wherein the fourth time characterizes the time during which the terminal transmits Media Access Control Unit (MAC CE) information related to the TRP that caused the beam failure on the first physical uplink shared channel.

[0040] In one embodiment, the triggering condition for triggering random access beam failure recovery includes: before a sixth time, there is a second TRP among the plurality of TRPs that has experienced beam failure; the sixth time represents the time when the terminal updates the beam of the first TRP.

[0041] In one embodiment, the processing unit is further configured to: trigger beam failure recovery at the TRP level in response to the presence of a second TRP experiencing beam failure again among the plurality of TRPs after the sixth time.

[0042] In one implementation, the beam failure recovery at the TRP level includes:

[0043] Trigger beam failure recovery based on Physical Uplink Control Channel Scheduling Request (PUCCH-SR) and / or Physical Uplink Shared Channel Media Access Control (PUSCH MAC CE).

[0044] In one embodiment, the processing unit is further configured to: trigger TRP-level beam failure recovery, or not trigger TRP-level beam failure recovery.

[0045] In one embodiment, configuring multiple TRPs for the terminal includes: configuring multiple sets of reference signal resources for the terminal for beam failure monitoring, and / or configuring multiple control resource pool index values ​​for the terminal.

[0046] According to a fourth aspect of this disclosure, a communication system is provided, the system comprising a terminal and a network device: the network device determines that the terminal is configured for multiple transmit / receive point (TRP) operation; the network device configures reference signal resources for the terminal, the reference signal resources being used for beam failure detection; in response to the terminal being configured with multiple TRPs, beam failure monitoring is performed on the multiple TRPs; in response to detecting that a first TRP among the multiple TRPs has experienced beam failure, and satisfying a triggering condition for triggering random access beam failure recovery, the terminal triggers beam failure recovery based on random access, the beam failure recovery being used for beam failure recovery of SpCell; wherein satisfying the triggering condition for triggering random access beam failure recovery includes: before a fifth time, a second TRP among the multiple TRPs has experienced beam failure; wherein the fifth time is the time when second downlink control information sent by the network device is received, the second downlink control information being used to determine that the network device has received MAC. CE information, the second downlink control information is used to schedule the second physical uplink shared channel; the hybrid automatic repeat request identifier of the second physical uplink shared channel scheduled by the second downlink control information is the same as the hybrid automatic repeat request identifier of the first physical uplink shared channel, wherein the first physical uplink shared channel is used to send Media Access Control Unit (MAC) CE information related to the TRP that has experienced beam failure; and / or the new data indication of the second physical uplink shared channel scheduled by the second downlink control information has changed.

[0047] According to a fifth aspect of the present disclosure, a beam failure recovery device is provided, comprising:

[0048] Processor; memory used to store processor-executable instructions;

[0049] The processor is configured to execute the beam failure recovery method described in the first aspect or any embodiment of the first aspect.

[0050] According to a sixth aspect of the present disclosure, a storage medium is provided, the storage medium storing instructions that, when executed by a processor of a terminal, enable the terminal to perform the beam failure recovery method described in the first aspect or any embodiment of the first aspect.

[0051] The technical solutions provided by the embodiments of this disclosure can include the following beneficial effects: when a terminal is configured with multiple TRPs, beam failure monitoring is performed on multiple TRPs. If a beam failure is detected among the multiple TRPs, beam failure recovery based on random access is triggered, enabling timely beam failure recovery based on random access in multiple TRP scenarios, ensuring the timeliness and effectiveness of beam failure recovery.

[0052] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and are not intended to limit this disclosure. Attached Figure Description

[0053] The accompanying drawings, which are incorporated in and form a part of this specification, illustrate embodiments consistent with this disclosure and, together with the description, serve to explain the principles of this disclosure.

[0054] Figure 1 This is a schematic diagram of a wireless communication system according to an exemplary embodiment.

[0055] Figure 2a This is a flowchart illustrating a BFR method according to an exemplary embodiment.

[0056] Figure 2b This is a flowchart illustrating a BFR method according to an exemplary embodiment.

[0057] Figure 3 This is a flowchart illustrating a BFR method according to an exemplary embodiment.

[0058] Figure 4 This is a flowchart illustrating a BFR method according to an exemplary embodiment.

[0059] Figure 5 This is a flowchart illustrating a BFR method according to an exemplary embodiment.

[0060] Figure 6 This is a flowchart illustrating a BFR method according to an exemplary embodiment.

[0061] Figure 7 This is a flowchart illustrating a BFR method according to an exemplary embodiment.

[0062] Figure 8 This is a flowchart illustrating a BFR method according to an exemplary embodiment.

[0063] Figure 9 This is a flowchart illustrating a BFR method according to an exemplary embodiment.

[0064] Figure 10 This is a flowchart illustrating a BFR method according to an exemplary embodiment.

[0065] Figure 11 This is a flowchart illustrating a BFR method according to an exemplary embodiment.

[0066] Figure 12 This is a flowchart illustrating a BFR method according to an exemplary embodiment.

[0067] Figure 13a This is a block diagram illustrating a BFR device according to an exemplary embodiment.

[0068] Figure 13b This is a block diagram illustrating a BFR device according to an exemplary embodiment.

[0069] Figure 14 This is a block diagram illustrating an apparatus for BFR according to an exemplary embodiment. Detailed Implementation

[0070] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numerals in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this disclosure. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this disclosure as detailed in the appended claims.

[0071] The beam failure recovery method provided in this disclosure can be applied to... Figure 1 The wireless communication system shown. (See attached image) Figure 1 As shown, this wireless communication system includes a terminal and a network device. The terminal connects to the network device via wireless resources and transmits and receives data.

[0072] Understandable, Figure 1 The wireless communication system shown is for illustrative purposes only. A wireless communication system may also include other network devices, such as core network equipment, wireless relay equipment, and wireless backhaul equipment. Figure 1 Not shown in the diagram. This disclosure does not limit the number of network devices and terminals included in the wireless communication system.

[0073] It is further understood that the wireless communication system of this disclosure is a network providing wireless communication functionality. The wireless communication system can employ different communication technologies, such as code division multiple access (CDMA), wideband code division multiple access (WCDMA), 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 carrier sense multiple access with collision avoidance. Based on factors such as capacity, speed, and latency, networks can be categorized as 2G networks, 3G networks, 4G networks, or future evolution networks, such as 5G networks. 5G networks can also be referred to as New Radio (NR). For ease of description, this disclosure may sometimes simply refer to the wireless communication network as a network.

[0074] Furthermore, the network device involved in this disclosure can also be referred to as a wireless access network device. This wireless access network device can be: a base station, an evolved Node B (eNB), a home base station, an access point (AP) in a Wireless Fidelity (WIFI) system, a wireless relay node, a wireless backhaul node, a transmission point (TP), or a transmission and reception point (TRP), etc. It can also be a gNB in ​​an NR system, or a component or part of a base station. When it is a vehicle-to-everything (V2X) communication system, the network device can also be an in-vehicle device. It should be understood that the specific technologies and specific device forms used in the embodiments of this disclosure are not limited.

[0075] Furthermore, the terminal involved in this disclosure can also be referred to as a terminal device, user equipment (UE), mobile station (MS), mobile terminal (MT), etc., and is a device that provides voice and / or data connectivity to a user. For example, a terminal can be a handheld device with wireless connectivity, an in-vehicle device, etc. Currently, some examples of terminals include: smartphones (Mobile Phones), pocket personal computers (PPCs), handheld computers, personal digital assistants (PDAs), laptops, tablets, wearable devices, or in-vehicle devices, etc. In addition, when it is a vehicle-to-everything (V2X) communication system, the terminal device can also be an in-vehicle device. It should be understood that the embodiments of this disclosure do not limit the specific technology or specific device form adopted by the terminal.

[0076] In this disclosure, data transmission between the network device and the terminal is based on beamforming. When the network device and terminal transmit data based on beamforming, the network device can use a Transmission Resource Registry (TRP) to provide services to the terminal. For example, the network device can use the TRP to send a PDCCH to the terminal. When the terminal detects that the radio link quality of the reference signal resource used for failure detection is below a threshold, the terminal performs a Link Recovery (BFR). The reference signal resource used for failure detection can be explicitly configured by the base station; if the base station does not explicitly configure it, it is the reference signal resource for QCL type D in the Transmission State Indication (TCI) state corresponding to the Control Resource Set (CORESET) used for sending the PDCCH. The terminal performing BFR is also referred to as the terminal performing Link Recovery.

[0077] In related technologies, the mechanisms for terminal beam recovery (BFR) include cell-specific BFR. Cell-specific BFR includes random access BFR mechanisms (Spcell-specific BFR) and BFR mechanisms based on PUCCH-SR and / or PUSCH MAC CE (Scell-specific BFR). Terminal BFR mechanisms also include TRP-level BFR mechanisms (TRP-specific BFR). Random access-based BFR mechanisms include contention-based random access methods (CBRA) and contention-free random access methods (CFRA). Under Spcell-specific BFR, i.e., random access BFR mechanisms, the terminal initiates a random access procedure to request beam recovery. Under Scell-specific BFR, i.e., PUCCH-SR and / or PUSCH MAC CE-based BFR mechanisms, the terminal performs beam failure recovery based on the PUCCH-SR and / or PUSCH MAC CE mechanisms. When a terminal detects a beam failure in a secondary cell, it sends MAC CE information on the PUSCH resource to indicate beam failure recovery information. The PUSCH resource can be obtained by sending a scheduling request on the PUCCH-SR specifically used for BFR, or it can be other PUSCH resources. Under the TRP-level BFR mechanism, Scell-specific BFRs will be reused.

[0078] In related technologies, when a terminal performs beam failure detection, it typically monitors the reference signal (RS) used for TRP beam failure detection. When the radio link quality of the corresponding RS is detected to be lower than a threshold N times, it is determined that the RS has failed; when all RSs used for TRP failure detection fail, it is determined that a beam failure has occurred in the TRP. In related technologies, there is a Multi-TRP PDCCH scenario between the terminal and network equipment. In the Multi-TRP PDCCH scenario, the terminal is configured with both random access BFR mechanism and TRP-level BFR mechanism in the same cell. Since multiple TRPs correspond to multiple sets of reference signals for failure detection, multiple sets of reference signals for failure detection are configured in the same cell. Each of these multiple sets of reference signals can be explicitly configured by the base station; if the base station does not explicitly configure it, the terminal can determine it based on the reference signal of QCLType D in the CORESET TCI state. In cases where two or more TRPs experience beamout failures, the relevant technologies do not provide a solution for whether to trigger cell-level BFR for random access BFR.

[0079] This disclosure provides a BFR method that triggers random access-based BFR when beam failure is detected in one of multiple TRPs.

[0080] In this embodiment of the disclosure, for ease of description, one of the at least two TRPs in which beam failure occurs among the plurality of TRPs configured for the terminal is referred to as the first TRP, and the other as the second TRP.

[0081] Figure 2a This is a flowchart illustrating a BFR method according to an exemplary embodiment, such as... Figure 2a As shown, the BFR method is used in a terminal that is configured with a random access BFR mechanism and a TRP-level BFR mechanism on the same cell. The BFR method provided in this disclosure includes the following steps.

[0082] In step S11a, in response to the terminal being configured with multiple TRPs, beam failure monitoring of multiple TRPs is performed.

[0083] In this embodiment of the disclosure, in response to the terminal being configured with multiple TRPs, the network device may determine that the terminal is configured with multiple TRPs. The network device may also configure reference signal resources for the terminal, wherein the reference signal resources are used for beam failure detection. In step S12a, in response to detecting that a first TRP among the multiple TRPs has experienced beam failure, a random access-based BFR is triggered.

[0084] Figure 2b This is a flowchart illustrating a BFR method according to an exemplary embodiment, such as... Figure 2b As shown, the BFR method is used in network devices. The BFR method provided in this disclosure includes the following steps.

[0085] In step S11b, the network device determines that the terminal is configured for multiple transmit / receive point (TRP) operation.

[0086] In step S12b, the network device configures reference signal resources for the terminal, and the reference signal resources are used for beam failure detection.

[0087] In this embodiment of the disclosure, if a first TRP experiences beam failure among multiple TRPs and the triggering condition for triggering random access beam failure recovery is met, beam failure recovery based on random access is triggered, and the beam failure recovery is used for beam failure recovery of the Spcell.

[0088] In this embodiment of the disclosure, the terminal is configured with multiple TRPs, which can be understood as being configured with multiple sets of reference signal resources for beam failure monitoring, and / or, the terminal is configured with multiple control resource pool index values ​​(CORESETPoolIndex values). The terminal being configured with multiple sets of reference signal resources for beam failure monitoring can be understood as the terminal being explicitly configured with multiple sets of reference signal resources for failure detection. When the terminal is not explicitly configured with a set of reference signal resources for failure detection, the terminal can determine one or more sets of reference signal resources for failure detection based on CORESETPoolIndex or CORESETGroup. For example, if all CORESETs of the terminal correspond to the same CORESETPoolIndex or CORESETGroup, the terminal determines the reference signal resources for failure detection based on the reference signal resources of QCL Type D of the TCI state of at least one CORESET among all CORESETs. If all CORESETs of the terminal correspond to different CORESETPoolIndex or CORESETGroup, the terminal determines the reference signal resource for failure detection corresponding to that CORESETPoolIndex or CORESETGroup based on the reference signal resource of QCLType D of the TCI state of at least one CORESET among all CORESETs corresponding to the same CORESETPoolIndex or CORESETGroup. Each CORESETPoolIndex or CORESETGroup corresponds to one reference signal resource for failure detection.

[0089] In all embodiments of this disclosure, "the terminal is configured with multiple TRPs" means that the terminal is configured to perform uplink and downlink transmissions with multiple TRPs of the base station. In some embodiments, the terminal may determine the multiple TRP configurations according to communication standards; or the terminal may determine the multiple TRP configurations according to configuration parameters or configuration signaling sent by the base station; or the terminal may negotiate with the base station to determine multiple TRPs, and these multiple TRPs are a subset or a proper subset of the base station's multiple TRPs (thus there is a possibility that the base station may assign different UEs to different TRP sets, or that some UEs may correspond to the same TRP set while other UEs may correspond to different TRP sets). The same content will not be repeated hereafter.

[0090] In this embodiment of the disclosure, the terminal performs beam failure monitoring for multiple TRPs. This can be achieved by the terminal monitoring the reference signal sets corresponding to each of the multiple TRPs when monitoring beam failure for some or all of them. For example, the terminal monitors the respective reference signal sets used for beam failure detection of the first TRP and / or the second TRP.

[0091] In this embodiment of the disclosure, if a TRP with beam failure is detected, a conventional method for determining the presence of a TRP with beam failure can be used. For example, for a given TRP, for each RS in the reference signal set used for failure detection, if the radio link quality of the corresponding RS is detected to be below a threshold N times, it is determined that the TRP has detected beam failure.

[0092] In this embodiment of the disclosure, if a first TRP with beam failure is detected among multiple TRPs, beam failure recovery based on random access can be triggered to achieve timely beam failure recovery based on random access in multiple TRP scenarios, ensuring the timeliness and effectiveness of beam failure recovery.

[0093] The BFR method provided in this disclosure allows a terminal to trigger a random access-based BFR when it determines that the triggering conditions for triggering a random access BFR are met.

[0094] Figure 3 This is a flowchart illustrating a BFR method according to an exemplary embodiment, such as... Figure 3 As shown, the BFR method used in the terminal includes the following steps.

[0095] In step S21, in response to the terminal being configured with multiple TRPs, beam failure monitoring is performed on multiple TRPs. In step S22, in response to the detection of a first TRP among the multiple TRPs experiencing beam failure, and the triggering condition for triggering random access BFR is met, random access-based BFR is triggered.

[0096] In this embodiment of the disclosure, the triggering condition required to trigger a random access-based BFR can be determined during a TRP-specific BFR process after detecting a first TRP among multiple TRPs that has experienced beam failure.

[0097] The BFR method provided in this disclosure allows a terminal to send a scheduling request on the Physical Uplink Control Channel (PUCCH) resource within the nearest waiting time when it detects a first TRP among multiple TRPs experiencing beam failure. For ease of description, the time when the terminal detects the first TRP experiencing beam failure is referred to as the first time (t1), and the time when the terminal sends the scheduling request on the PUCCH-SR resource is referred to as the second time (t2). In one example, the terminal monitors respective reference signal sets used for beam failure detection of the first TRP and / or the second TRP. When a beam failure is detected, for example, in the first TRP, the terminal waits for the nearest PUCCH-SR at time t2. The terminal then sends the scheduling request on the PUCCH-SR resource at time t2.

[0098] It is understood that the first time and t1 involved in the embodiments of this disclosure are sometimes used interchangeably, but those skilled in the art should understand the consistency of their meanings, and the first time / t1 involved in each embodiment has the same meaning.

[0099] It is further understood that the second time and t2 involved in the embodiments of this disclosure are sometimes used interchangeably, but those skilled in the art should understand the consistency of their meanings, and the second time / t2 involved in each embodiment has the same meaning.

[0100] Figure 4 This is a flowchart illustrating a BFR method according to an exemplary embodiment, such as... Figure 4 As shown, the BFR method used in the terminal includes the following steps.

[0101] In step S31, in response to the terminal being configured with multiple TRPs, beam failure monitoring of multiple TRPs is performed.

[0102] In step S32, in response to the detection of a first TRP with beam failure among multiple TRPs, and before the second time, the detection of a second TRP with beam failure among multiple TRPs, a BFR based on random access is triggered.

[0103] In one embodiment of this disclosure, in response to the detection of a second TRP experiencing beam failure among a plurality of TRPs after a first time and before a second time, it is determined that the triggering condition for triggering random access beam failure recovery is met. The first time is the time when the beam failure of the first TRP is detected, and the second time is the time (t2) when a scheduling request is sent on the physical uplink control channel resources.

[0104] Based on the above example, if the terminal detects that the second TRP has also experienced beam failure before t2, then it triggers BFR based on random access.

[0105] In another embodiment of this disclosure, after the terminal sends a scheduling request on the PUCCH-SR resource at the second time, it can wait for a certain period of time before receiving Downlink Control Information (DCI) for scheduling PUSCH. For ease of description, the DCI for scheduling PUSCH will be referred to as the first DCI, and the time of receiving the first DCI will be referred to as the third time (t3).

[0106] It is understood that the third time and t3 involved in the embodiments of this disclosure are sometimes used interchangeably, but those skilled in the art should understand the consistency of their meanings, and the third time / t3 involved in each embodiment has the same meaning.

[0107] Figure 5 This is a flowchart illustrating a BFR method according to an exemplary embodiment, such as... Figure 5 As shown, the BFR method used in the terminal includes the following steps.

[0108] In step S41, in response to the terminal being configured with multiple TRPs, beam failure monitoring is performed on multiple TRPs.

[0109] In step S42, in response to the detection of a first TRP with beam failure among multiple TRPs, and before the third time, the detection of a second TRP with beam failure among multiple TRPs, a random access-based BFR is triggered.

[0110] In one embodiment of this disclosure, in response to the detection of a second TRP among multiple TRPs experiencing beam failure at a second time, or after the second time and before the third time, it is determined that the triggering condition for triggering random access beam failure recovery is met. The second time is the time when a scheduling request is sent on the physical uplink control channel resource, and the third time is the time when first downlink control information for scheduling the physical uplink shared channel is received.

[0111] Based on the above example, if the terminal detects a beam failure in the second TRP at or after t2 but before t3, then a BFR based on random access is triggered.

[0112] In another embodiment of this disclosure, in response to detecting a second TRP among a plurality of TRPs that has experienced beam failure before a third time, it is determined that the triggering condition for triggering random access beam failure recovery is met.

[0113] Based on the above example, if the terminal detects a beam failure in the second TRP at or after t1 but before t3, then a BFR based on random access is triggered.

[0114] Figure 6 This is a flowchart illustrating a BFR method according to an exemplary embodiment, such as... Figure 6 As shown, the BFR method used in the terminal includes the following steps.

[0115] In step S51, in response to the terminal being configured with multiple TRPs, beam failure monitoring of multiple TRPs is performed.

[0116] In step S52, in response to the detection of a first TRP with beam failure among multiple TRPs, and the detection of a second TRP with beam failure among multiple TRPs before the third time, and the failure to receive any downlink control information within a first time period after the second time period, a BFR based on random access is triggered.

[0117] In one embodiment of this disclosure, if no DCI signaling is received within a certain period of time (first period T1) after the second time, it can be determined that the triggering condition for triggering BFR based on random access is met. For example, if the terminal does not receive the first DCI signaling after time t2+T1, then BFR based on random access is triggered. As another example, if the terminal does not receive the DCI (hereinafter referred to as the second DCI) used to determine that the network device has received MAC CE information after time t2+T1, then BFR based on random access is triggered.

[0118] In another embodiment of this disclosure, the terminal receives the first DCI for scheduling the PUSCH at a third time. After waiting for a certain period of time, it can send MAC CE information related to the TRP that has experienced beam failure on the PUSCH. For ease of description, the time when the MAC CE information related to the TRP that has experienced beam failure is sent on the PUSCH will be referred to as the fourth time (t4).

[0119] It is further understood that the fourth time and t4 involved in the embodiments of this disclosure are sometimes used interchangeably, but those skilled in the art should understand the consistency of their meanings, and the fourth time / t4 involved in each embodiment has the same meaning.

[0120] Figure 7 This is a flowchart illustrating a BFR method according to an exemplary embodiment, such as... Figure 7 As shown, the BFR method used in the terminal includes the following steps.

[0121] In step S61, in response to the terminal being configured with multiple TRPs, beam failure monitoring of multiple TRPs is performed.

[0122] In step S62, in response to the detection of a first TRP among multiple TRPs that has experienced beam failure, before the fourth time, a second TRP among multiple TRPs that has experienced beam failure is detected, triggering a BFR based on random access.

[0123] The fourth time is the time when MAC CE information related to the TRP that has experienced beam failure is sent on the PUSCH.

[0124] It should be noted that the PUSCH used to transmit MAC CE information related to the TRP where beam failure occurred can be scheduled by the first DCI signaling or a PUSCH configured with grant type 1 or type 2. For ease of description, the PUSCH used to transmit MAC CE information related to the TRP where beam failure occurred will be referred to as the first PUSCH in the following embodiments.

[0125] In one implementation, in response to the detection of a second TRP among a plurality of TRPs experiencing beam failure at a third time, or after the third time and before the fourth time, it is determined that the triggering condition for triggering a random access BFR is met.

[0126] Based on the above example, if the terminal detects a beam failure in the second TRP at or after t3 but before t4, then a BFR based on random access is triggered.

[0127] In another implementation, in response to the detection of a second TRP among multiple TRPs that has experienced beam failure before the fourth time, it is determined that the triggering condition for triggering random access BFR is met.

[0128] Based on the above example, if the terminal detects a beam failure in the second TRP at or after t1 but before t4, then a BFR based on random access is triggered.

[0129] Furthermore, in this embodiment of the present disclosure, if a second TRP with beam failure is detected among multiple TRPs before the fourth time, and the beam corresponding to the first PUSCH is the beam with beam failure, then it can also be determined that the triggering condition for triggering random access BFR is met.

[0130] Figure 8 This is a flowchart illustrating a BFR method according to an exemplary embodiment, such as... Figure 8 As shown, the BFR method used in the terminal includes the following steps.

[0131] In step S71, in response to the terminal being configured with multiple TRPs, beam failure monitoring of multiple TRPs is performed.

[0132] In step S72, in response to the detection of a first TRP among multiple TRPs that has experienced beam failure, before the fourth time, a second TRP among multiple TRPs that has experienced beam failure is detected, and the beam corresponding to the first PUSCH is the beam that has experienced beam failure, triggering BFR based on random access.

[0133] In one implementation, if a second TRP with beam failure is detected among multiple TRPs at a third time, or after the third time and before the fourth time, and the beam corresponding to the first PUSCH is the beam with beam failure, then it can also be determined that the triggering condition for triggering random access BFR is met.

[0134] In another implementation, if a second TRP with beam failure is detected among multiple TRPs before the fourth time, and the beam corresponding to the first PUSCH is the beam with beam failure, then it can also be determined that the triggering condition for triggering random access BFR is met.

[0135] In this embodiment of the disclosure, the terminal sends MAC CE information related to the TRP that has experienced beam failure on the PUSCH at the fourth time, and receives the second DCI signaling after waiting for a certain period of time. The time at which the second DCI is received is referred to as the fifth time (t5). The fifth time is the time at which the second DCI is received, and the second DCI is used to determine that the network device has received the MAC CE information.

[0136] It is further understood that the fifth time and t5 involved in the embodiments of this disclosure are sometimes used interchangeably, but those skilled in the art should understand the consistency of their meanings, and the fifth time / t5 involved in each embodiment has the same meaning.

[0137] Figure 9 This is a flowchart illustrating a BFR method according to an exemplary embodiment, such as... Figure 9 As shown, the BFR method used in the terminal includes the following steps.

[0138] In step S81, in response to the terminal being configured with multiple TRPs, beam failure monitoring of multiple TRPs is performed.

[0139] In step S82, in response to the detection of a first TRP among multiple TRPs that has experienced beam failure, before the fifth time, a second TRP among multiple TRPs that has experienced beam failure is detected, triggering a BFR based on random access.

[0140] In one implementation, in response to the detection of a second TRP among multiple TRPs experiencing beam failure at a fourth time, or after the fourth time and before the fifth time, it is determined that the triggering condition for triggering a random access BFR is met. The fourth time is the time when MAC CE information related to the TRP experiencing beam failure is transmitted on the PUSCH.

[0141] Based on the above example, if the terminal detects a beam failure in the second TRP at or after t4 but before t5, then a BFR based on random access is triggered.

[0142] In one implementation, in response to the detection of a second TRP among multiple TRPs experiencing beam failure before a fifth time, it is determined that the triggering condition for triggering a random access buffer (BFR) is met. The fifth time is the time when the second DCI is received, which is used to determine that the network device has received the MAC CE information.

[0143] Based on the above example, if the terminal detects a beam failure in the second TRP at or after t1 but before t5, then a BFR based on random access is triggered.

[0144] Furthermore, in this embodiment of the present disclosure, if the terminal detects that the second TRP has also experienced beam failure before the fifth time period, and if the terminal does not receive the second DCI signaling within a certain period of time after the fourth time period (hereinafter referred to as the second time period T2), then it is determined that the triggering condition for triggering BFR based on random access is met. That is, if the second DCI signaling is not received after time t4+T2, then BFR based on random access is triggered.

[0145] In this embodiment of the disclosure, the second DCI signaling is used to determine that the network device has received the MAC CE information. The terminal will update its beam after a certain period of time following receipt of the second DCI signaling. In this embodiment of the disclosure, the second DCI can also be used to schedule PUSCHs. For ease of description, the PUSCH scheduled by the second DCI will be referred to as the second PUSCH. The Hybrid Automatic Repeat reQuest (HARQ) identifier (ID) of the second PUSCH is the same as that of the first PUSCH, but the new data indicator (NDI) has changed (toggle). The first PUSCH is scheduled by the first DCI, or is a PUSCH configured with grant Type 1 or Type 2.

[0146] Updating the beam includes updating at least one of the following: quasi co-location (QCL) Type-D parameter, uplink transmit spatial filter (UL TX spatial filter), spatial relation info, transmission configuration indication state (TCI state), downlink TCI state (DL TCI state), and uplink TCI state (UL TCI state).

[0147] Figure 10 This is a flowchart illustrating a BFR method according to an exemplary embodiment, such as... Figure 10 As shown, the BFR method used in the terminal includes the following steps.

[0148] In step S91, in response to the terminal being configured with multiple TRPs, beam failure monitoring of multiple TRPs is performed.

[0149] In step S92, in response to the detection of a first TRP among multiple TRPs that has experienced beam failure, before the fifth time period, a second TRP among multiple TRPs that has experienced beam failure is detected, and no DCI is received within the second time period after the fourth time period, triggering BFR based on random access.

[0150] In one implementation, at a fourth time, or after the fourth time and before the fifth time, a second TRP with beam failure is detected among multiple TRPs, and no DCI is received within a second time period after the fourth time.

[0151] Based on the above example, if the terminal detects a beam failure in the second TRP at or after time t4 but before time t5, and if the terminal does not receive the second DCI signaling after time t4+T2, it will trigger a BFR based on random access.

[0152] In another implementation, before the fifth time, a second TRP with beam failure is detected among multiple TRPs, and no DCI is received within a second time period after the fourth time.

[0153] Based on the above example, if the terminal detects a beam failure in the second TRP at or after time t1 but before time t5, and if the terminal does not receive the second DCI signaling after time t4+T2, it will trigger a BFR based on random access.

[0154] In this embodiment of the present disclosure, after the terminal receives the second DCI at the fifth time, it can wait for a certain period of time before updating the beam of the TRP that has failed, that is, updating the beam of the first TRP. In this embodiment of the present disclosure, the time for updating the beam of the first TRP is referred to as the sixth time.

[0155] It is further understood that the sixth time and t6 involved in the embodiments of this disclosure are sometimes used interchangeably, but those skilled in the art should understand the consistency of their meanings, and the sixth time / t6 involved in each embodiment has the same meaning.

[0156] In one implementation, in response to the detection of a second TRP among multiple TRPs experiencing beam failure before the sixth time, it is determined that the triggering condition for triggering a random access bounding window (BFR) is met. The fifth time is the time when the second digital interface (DCI) is received, which is used to determine that the network device has received the MAC CE information. The sixth time is the time when the beam of the first TRP is updated.

[0157] Figure 11 This is a flowchart illustrating a BFR method according to an exemplary embodiment, such as... Figure 11 As shown, the BFR method used in the terminal includes the following steps.

[0158] In step S101, in response to the terminal being configured with multiple TRPs, beam failure monitoring of multiple TRPs is performed.

[0159] In step S102, in response to the detection of a first TRP among multiple TRPs that has experienced beam failure, before the sixth time, a second TRP among multiple TRPs that has experienced beam failure is detected, triggering a BFR based on random access.

[0160] In one implementation, in response to the detection of a second TRP experiencing beam failure among multiple TRPs at a fifth time, or after the fifth time and before the sixth time, it is determined that the triggering condition for triggering a random access bounding window (BFR) is met. The fifth time is the time when the second digital interface (DCI) is received, which is used to determine that the network device has received the MAC CE information, and the sixth time is the time when the beam of the first TRP is updated.

[0161] Based on the above example, if the terminal detects a beam failure in the second TRP at or after t5 but before t6, it triggers a BFR based on random access.

[0162] In another implementation, in response to the detection of a second TRP among multiple TRPs that has experienced beam failure before the sixth time, it is determined that the triggering condition for triggering random access BFR is met.

[0163] Based on the above example, if the terminal detects a beam failure in the second TRP at or after t1 but before t6, then a BFR based on random access is triggered.

[0164] In this embodiment of the disclosure, it is possible to continuously monitor multiple TRPs for the presence of a TRP that has experienced beam failure, and in response to the detection of a second TRP that has experienced beam failure again among multiple TRPs after a sixth time period, triggering a BFR at the TRP level.

[0165] Figure 12 This is a flowchart illustrating a BFR method according to an exemplary embodiment, such as... Figure 12 As shown, the BFR method used in the terminal includes the following steps.

[0166] In step S111, in response to the terminal being configured with multiple TRPs, beam failure monitoring of multiple TRPs is performed.

[0167] In step S112, in response to the detection of a first TRP among multiple TRPs that has experienced beam failure, before the sixth time, a second TRP among multiple TRPs that has experienced beam failure is detected, triggering a BFR based on random access.

[0168] In step S113, in response to the detection of a second TRP with beam failure among multiple TRPs after the sixth time, a BFR at the TRP level is triggered.

[0169] In this embodiment of the disclosure, triggering a BFR at the TRP level can be understood as triggering a BFR based on PUCCH-SR and / or PUSCH MAC CE.

[0170] This disclosure uses an example where the terminal is configured with two TRPs, such as a first TRP and a second TRP. The TRP-based BFR can be understood as the following execution process:

[0171] a) The terminal monitors the respective reference signal sets used for beam failure detection of the first TRP and / or the second TRP. When a beam failure is detected at time t1, for example, in the first TRP, the terminal waits for the nearest PUCCH-SR at time t2. This assumes that no other PUCCH-SRs were sent before t1, or that if no PUCCH-SR is sent at time t2, there will be no available PUSCH resources in the near future.

[0172] It is understood that if a beam failure is detected in a certain TRP in this embodiment of the present disclosure, a traditional predefined method can be reused, that is, for each RS in the reference signal set, the radiolink quality of its corresponding RS is monitored N times when it is found to be lower than a certain threshold.

[0173] b) The terminal waits for the first DCI signaling at time t3 to schedule the first PUSCH.

[0174] c) The terminal receives the first DCI for scheduling the first PUSCH at time t3, and then sends the MAC CE information related to the TRP that has experienced beam failure on the PUSCH at time t4.

[0175] d) The terminal sends MAC CE information related to the TRP that caused the beam failure on the first PUSCH at time t4, and waits for the second DCI signaling at time t5. The second DCI signaling is used to determine that the base station has received the MAC CE information. After receiving the second DCI signaling at time T0, the terminal will update the beam.

[0176] Understandably, the second DCI signaling can also be used to schedule the second PUSCH. The HARQ ID of the second PUSCH is the same as that of the first PUSCH, but the NDI field value is toggleed. The first PUSCH is scheduled by the first DCI, or it is a PUSCH configured with grant Type 1 or Type 2.

[0177] Furthermore, updating the beam includes updating at least one of the following: quasi co-location QCL Type-D parameter, UL TX spatial filter, spatialrelation info, TCI state, DL TCI state, ULTCI state.

[0178] e) The terminal receives the second DCI signaling at time t5. It waits for time t6 to update the beam of the TRP that failed.

[0179] Furthermore, in this embodiment of the disclosure, when triggering a BFR for random access, a TRP-level BFR may be triggered, or a TRP-level BFR may not be triggered. That is, when triggering a BFR based on random access, whether or not a TRP-specific BFR is triggered will not affect the BFR based on random access.

[0180] Based on the above embodiments, the triggering conditions for triggering a BFR based on random access provided in this disclosure embodiment may include at least one of the following situations, and trigger a BFR based on random access:

[0181] a) If the terminal detects a beam failure in the second TRP before t2, it triggers a BFR based on random access.

[0182] b) If the terminal detects a beam failure in the second TRP before t3, it triggers a BFR based on random access.

[0183] c) If the terminal detects a beam failure in the second TRP at or after time t2 but before time t3, and the terminal does not receive the first DCI signaling after time t2+T1, then a BFR based on random access is triggered.

[0184] d) If the terminal detects a beam failure in the second TRP before t4, it triggers a BFR based on random access.

[0185] e) If the terminal detects a beam failure in the second TRP at or after t3 but before t4, and the beam of the first PUSCH is the failed beam, then a BFR based on random access is triggered.

[0186] f) If the terminal detects a beam failure in the second TRP before t5, it triggers a BFR based on random access.

[0187] g) If the terminal detects a beam failure in the second TRP at or after time t4 but before time t5, and if the terminal does not receive the second DCI signaling after time t4+T2, then a BFR based on random access is triggered.

[0188] h) If the terminal detects a beam failure in the second TRP before t6, it triggers a BFR based on random access.

[0189] I) If the terminal detects a beam failure in the second TRP again after t6, it will only trigger a TRP-specific BFR.

[0190] The BFR method provided in this disclosure determines the conditions for triggering cell-specific BFR in a Multi-TRP PDCCH scenario for terminals that are configured with both TRP-specific BFR and cell-specific BFR on the same cell, thus ensuring the timeliness and effectiveness of beam failure recovery.

[0191] An exemplary embodiment of this disclosure proposes a communication system, including a terminal and a network device: the network device determines that the terminal is configured for multiple transmit / receive point (TRP) operation; the network device configures reference signal resources for the terminal, the reference signal resources being used for beam failure detection; in response to the terminal being configured with multiple TRPs, beam failure monitoring is performed on the multiple TRPs; in response to detecting that a first TRP among the multiple TRPs has experienced beam failure, and the triggering condition for triggering random access beam failure recovery is met, the terminal triggers beam failure recovery based on random access, the beam failure recovery being used for beam failure recovery of SpCell; wherein, meeting the triggering condition for triggering random access beam failure recovery includes: before a fifth time, a second TRP among the multiple TRPs has experienced beam failure; wherein the fifth time is the time when the network device receives second downlink control information, the second downlink control information determining that the network device has received MAC. The CE information, second downlink control information used to schedule the second physical uplink shared channel; the hybrid automatic repeat request identifier of the second physical uplink shared channel scheduled by the second downlink control information is the same as the hybrid automatic repeat request identifier of the first physical uplink shared channel, wherein the first physical uplink shared channel is used to send Media Access Control Unit (MAC) CE information related to the TRP that has experienced beam failure; and / or the new data indication of the second physical uplink shared channel scheduled by the second downlink control information changes. In one embodiment, satisfying the triggering condition for triggering random access beam failure recovery further includes: after a first time and before a second time, there is a second TRP among the plurality of TRPs that has experienced beam failure; the first time characterizes the time when the terminal detects that the first TRP has experienced beam failure, and the second time characterizes the time when the terminal sends a scheduling request on the physical uplink control channel resource.

[0192] In one embodiment, the triggering condition for triggering random access beam failure recovery further includes: before a third time, there is a second TRP among the multiple TRPs that has experienced beam failure; the third time characterizes the time when the terminal receives the first downlink control information for scheduling the physical uplink shared channel.

[0193] In one embodiment, the triggering condition for triggering random access beam failure recovery further includes: within a first duration after the second time, no downlink control information is received, whereby the second time characterizes the time during which the terminal sends a scheduling request on the physical uplink control channel resources.

[0194] In one implementation, the triggering condition for triggering random access beam failure recovery includes: before a fourth time, there is a second TRP among the plurality of TRPs that has experienced beam failure; the fourth time characterizes the time when the terminal transmits Media Access Control Unit (MAC CE) information related to the TRP that experienced beam failure on the first physical uplink shared channel.

[0195] In one embodiment, the triggering condition for triggering random access beam failure recovery further includes: the beam corresponding to the first physical uplink shared channel is the beam that experienced beam failure; wherein, the first physical uplink shared channel is the first downlink control information scheduling, or a physical uplink shared channel with configuration authorization of type 1 or type 2.

[0196] In one embodiment, the triggering condition for triggering random access beam failure recovery further includes: within a second duration after the fourth time, the terminal does not receive any downlink control information, whereby the fourth time characterizes the time during which the terminal transmits Media Access Control Unit (MAC CE) information related to the TRP that caused the beam failure on the first physical uplink shared channel.

[0197] In one implementation, the triggering condition for triggering random access beam failure recovery includes: before a sixth time, there is a second TRP among the multiple TRPs that has experienced beam failure; the sixth time characterizes the time when the terminal updates the beam of the first TRP.

[0198] In one embodiment, the method further includes: triggering TRP-level beam failure recovery in response to the presence of a second TRP experiencing beam failure again among the plurality of TRPs after a sixth time period.

[0199] In one implementation, triggering beam failure recovery at the TRP level includes triggering beam failure recovery based on PUCCH-SR and / or PUSCH MAC CE.

[0200] In one embodiment, the method further includes: triggering beam failure recovery at the TRP level, or not triggering beam failure recovery at the TRP level.

[0201] In one implementation, configuring multiple TRPs for a terminal includes: configuring multiple sets of reference signal resources for beam failure monitoring for the terminal, and / or configuring multiple control resource pool index values ​​for the terminal.

[0202] It should be noted that those skilled in the art will understand that the various embodiments / examples described above in this disclosure can be used in conjunction with the foregoing embodiments, or they can be used independently. Whether used alone or in conjunction with the foregoing embodiments, the implementation principle is similar. In this disclosure, some embodiments are described as implementations used together. Of course, those skilled in the art will understand that such illustrative examples are not intended to limit the embodiments of this disclosure. Based on the same concept, this disclosure also provides a BFR device.

[0203] It is understood that the BFR device provided in this disclosure includes hardware structures and / or software modules corresponding to each function in order to achieve the above-mentioned functions. In conjunction with the units and algorithm steps of the various examples disclosed in this disclosure, this disclosure can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed by hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of the technical solutions of this disclosure.

[0204] Figure 13a This is a block diagram of a BFR device according to an exemplary embodiment. (Refer to...) Figure 13a The BFR device 100a includes a monitoring unit 101a and a processing unit 102a.

[0205] The monitoring unit 101a is configured to perform beam failure monitoring of multiple TRPs when the terminal is configured with multiple TRPs; the processing unit 102a is configured to trigger a random access-based BFR when the monitoring unit 101a detects that a first TRP among the multiple TRPs has experienced beam failure.

[0206] In one embodiment, the processing unit 102a is further configured to: determine whether the triggering conditions for triggering the random access BFR are met before triggering the random access-based BFR.

[0207] In one embodiment, in response to the monitoring unit 101a detecting a second TRP among multiple TRPs that has experienced beam failure before the second time, the processing unit 102a determines that the triggering condition for triggering random access BFR is met; the first time is the time when the first TRP is detected to have experienced beam failure, and the second time is the time when a scheduling request is sent on the PUCCH resource.

[0208] In one embodiment, in response to the monitoring unit 101a detecting a second TRP among multiple TRPs that has experienced beam failure before a third time, the processing unit 102a determines that the triggering conditions for triggering random access BFR are met; the third time is the time when the first DCI for scheduling PUSCH is received.

[0209] In one implementation, in response to the fact that no DCI is received within a first duration after the second time, the processing unit 102a determines that the triggering condition for triggering the random access BFR is met, and the second time is the time when the scheduling request is sent on the PUCCH resource.

[0210] In one embodiment, in response to the monitoring unit 101a detecting a second TRP among multiple TRPs that has experienced beam failure before the fourth time, the processing unit 102a determines that the triggering condition for triggering random access BFR is met; the fourth time is the time when MAC CE information related to the TRP that has experienced beam failure is sent on the first PUSCH.

[0211] In one embodiment, in response to the first PUSCH corresponding to a beam that has experienced beam failure, the processing unit 102a determines that the triggering conditions for triggering random access BFR are met.

[0212] In one embodiment, in response to the monitoring unit 101a detecting a second TRP among multiple TRPs that has experienced beam failure before the fifth time, the processing unit 102a determines that the triggering condition for triggering random access BFR is met; the fifth time is the time when the second DCI is received, and the second DCI is used to determine that the network device has received MAC CE information.

[0213] In one implementation, the second DCI is used to schedule the second PUSCH.

[0214] The hybrid automatic repeat request identifier of the second PUSCH of the second DCI scheduling is the same as that of the first PUSCH, wherein the first PUSCH is the first DCI scheduling, or the configure grant Type 1 or Type 2 PUSCH; and / or the new data indication of the second PUSCH of the second DCI scheduling changes.

[0215] In one embodiment, in response to the fact that no DCI is received within a second duration after the fourth time, the processing unit 102a determines that the triggering condition for triggering random access BFR is met, wherein the fourth time is the time when the Media Access Control Unit (MAC CE) information related to the TRP that has experienced beam failure is transmitted on the first PUSCH.

[0216] In one embodiment, in response to the monitoring unit 101a detecting a second TRP among a plurality of TRPs that has experienced beam failure before the sixth time, it determines that the triggering condition for triggering random access BFR is met; the sixth time is the time for updating the beam of the first TRP.

[0217] In one embodiment, in response to the monitoring unit 101a detecting again, after a sixth time period, that a second TRP among the multiple TRPs has experienced beam failure, the processing unit 102a triggers a BFR at the TRP level.

[0218] In one implementation, triggering a BFR at the TRP level includes: triggering a BFR based on PUCCH-SR and / or PUSCH MACCE.

[0219] In one embodiment, the processing unit 102a is further configured to trigger a BFR at the TRP level, or not trigger a BFR at the TRP level.

[0220] In one implementation, the terminal is configured with multiple TRPs, including: the terminal is configured with multiple sets of reference signal resources for beam failure monitoring, and / or the terminal is configured with multiple control resource pool index values.

[0221] Figure 13b This is a block diagram of a BFR device according to an exemplary embodiment. (Refer to...) Figure 13b The BFR device 100b includes a monitoring unit 101b and a processing unit 102b.

[0222] Monitoring unit 101b is configured to determine that the terminal is configured for multiple transmit / receive point (TRP) operation; and to configure reference signal resources for the terminal, which are used for beam failure detection.

[0223] Processing unit 102b is configured to trigger beam failure recovery based on random access when a first TRP among multiple TRPs experiences beam failure and the triggering conditions for triggering random access beam failure recovery are met. The beam failure recovery is used for beam failure recovery of the Spcell. The triggering conditions for triggering random access beam failure recovery include: before a fifth time period, monitoring unit 101b detects a second TRP among multiple TRPs experiencing beam failure using the following method: the fifth time period is the time when the terminal receives second downlink control information sent by the network device; the second downlink control information determines that the network device has received MAC CE information; the second downlink control information is used to schedule a second physical uplink shared channel; the hybrid automatic repeat request identifier of the second physical uplink shared channel scheduled by the second downlink control information is the same as the hybrid automatic repeat request identifier of the first physical uplink shared channel, wherein the first physical uplink shared channel is used to send MAC CE information related to the TRP experiencing beam failure; and / or the new data indication of the second physical uplink shared channel scheduled by the second downlink control information changes.

[0224] In one embodiment, the triggering condition for triggering random access beam failure recovery further includes: after a first time and before a second time, there is a second TRP among the multiple TRPs that has experienced beam failure; the first time represents the time when the terminal detects that the first TRP has experienced beam failure, and the second time represents the time when the terminal sends a scheduling request on the physical uplink control channel resources.

[0225] In one embodiment, the triggering condition for triggering random access beam failure recovery further includes: before a third time, there is a second TRP among the multiple TRPs that has experienced beam failure; the third time characterizes the time when the terminal receives the first downlink control information for scheduling the physical uplink shared channel.

[0226] In one embodiment, the triggering condition for triggering random access beam failure recovery further includes: within a first duration after the second time, no downlink control information is received, whereby the second time characterizes the time during which the terminal sends a scheduling request on the physical uplink control channel resources.

[0227] In one implementation, the triggering condition for triggering random access beam failure recovery includes: before a fourth time, there is a second TRP among the plurality of TRPs that has experienced beam failure; the fourth time characterizes the time when the terminal transmits Media Access Control Unit (MAC CE) information related to the TRP that experienced beam failure on the first physical uplink shared channel.

[0228] In one embodiment, the triggering condition for triggering random access beam failure recovery further includes: the beam corresponding to the first physical uplink shared channel is the beam that experienced beam failure; wherein, the first physical uplink shared channel is the first downlink control information scheduling, or a physical uplink shared channel with configuration authorization of type 1 or type 2.

[0229] In one embodiment, the triggering condition for triggering random access beam failure recovery further includes: within a second duration after the fourth time, the terminal does not receive any downlink control information, whereby the fourth time characterizes the time during which the terminal transmits Media Access Control Unit (MAC CE) information related to the TRP that caused the beam failure on the first physical uplink shared channel.

[0230] In one implementation, the triggering condition for triggering random access beam failure recovery includes: before a sixth time, there is a second TRP among the multiple TRPs that has experienced beam failure; the sixth time characterizes the time when the terminal updates the beam of the first TRP.

[0231] In one embodiment, the processing unit 102b is further configured to: trigger beam failure recovery at the TRP level in response to the presence of a second TRP that has experienced beam failure again among the plurality of TRPs after a sixth time.

[0232] In one implementation, triggering beam failure recovery at the TRP level includes: triggering beam failure recovery based on the Physical Uplink Control Channel Scheduling Request (PUCCH-SR) and / or the Physical Uplink Shared Channel Media Access Control (PUSCH MAC CE).

[0233] In one embodiment, the processing unit 102b is further configured to: trigger TRP-level beam failure recovery, or not trigger TRP-level beam failure recovery.

[0234] In one implementation, configuring multiple TRPs for a terminal includes: configuring multiple sets of reference signal resources for beam failure monitoring for the terminal, and / or configuring multiple control resource pool index values ​​for the terminal.

[0235] Regarding the apparatus in the above embodiments, the specific manner in which each module performs its operation has been described in detail in the embodiments related to the method, and will not be elaborated upon here. Figure 14 This is a block diagram illustrating an apparatus 200 for BFR according to an exemplary embodiment. For example, apparatus 200 may be a mobile phone, computer, digital broadcast terminal, messaging device, game console, tablet device, medical device, fitness equipment, personal digital assistant, etc.

[0236] Reference Figure 14The device 200 may include one or more of the following components: processing component 202, memory 204, power component 206, multimedia component 208, audio component 210, input / output (I / O) interface 212, sensor component 214, and communication component 216.

[0237] Processing component 202 typically controls the overall operation of device 200, such as operations associated with display, telephone calls, data communication, camera operation, and recording. Processing component 202 may include one or more processors 220 to execute instructions to perform all or part of the steps of the methods described above. Furthermore, processing component 202 may include one or more modules to facilitate interaction between processing component 202 and other components. For example, processing component 202 may include a multimedia module to facilitate interaction between multimedia component 208 and processing component 202.

[0238] Memory 204 is configured to store various types of data to support the operation of device 200. Examples of such data include instructions for any application or method operating on device 200, contact data, phonebook data, messages, pictures, videos, etc. Memory 204 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk.

[0239] The power supply component 206 provides power to the various components of the device 200. The power supply component 206 may include a power management system, one or more power sources, and other components associated with generating, managing, and distributing power to the device 200.

[0240] Multimedia component 208 includes a screen that provides an output interface between the device 200 and the user. In some embodiments, the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touchscreen to receive input signals from the user. The touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. The touch sensors may sense not only the boundaries of the touch or swipe action but also the duration and pressure associated with the touch or swipe operation. In some embodiments, multimedia component 208 includes a front-facing camera and / or a rear-facing camera. When the device 200 is in an operating mode, such as a shooting mode or a video mode, the front-facing camera and / or the rear-facing camera may receive external multimedia data. Each front-facing camera and rear-facing camera may be a fixed optical lens system or have focal length and optical zoom capabilities.

[0241] Audio component 210 is configured to output and / or input audio signals. For example, audio component 210 includes a microphone (MIC) configured to receive external audio signals when device 200 is in an operating mode, such as call mode, recording mode, and voice recognition mode. The received audio signals may be further stored in memory 204 or transmitted via communication component 216. In some embodiments, audio component 210 also includes a speaker for outputting audio signals.

[0242] I / O interface 212 provides an interface between processing component 202 and peripheral interface modules, such as keyboards, click wheels, buttons, etc. These buttons may include, but are not limited to, home buttons, volume buttons, power buttons, and lock buttons.

[0243] Sensor assembly 214 includes one or more sensors for providing status assessments of various aspects of device 200. For example, sensor assembly 214 may detect the on / off state of device 200, the relative positioning of components such as the display and keypad of device 200, changes in the position of device 200 or a component of device 200, the presence or absence of user contact with device 200, the orientation or acceleration / deceleration of device 200, and temperature changes of device 200. Sensor assembly 214 may include a proximity sensor configured to detect the presence of nearby objects without any physical contact. Sensor assembly 214 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, sensor assembly 214 may also include an accelerometer, a gyroscope, a magnetometer, a pressure sensor, or a temperature sensor.

[0244] Communication component 216 is configured to facilitate wired or wireless communication between device 200 and other devices. Device 200 can access wireless networks based on communication standards, such as WiFi, 2G, or 3G, or combinations thereof. In one exemplary embodiment, communication component 216 receives broadcast signals or broadcast-related information from an external broadcast management system via a broadcast channel. In one exemplary embodiment, communication component 216 also includes a near-field communication (NFC) module to facilitate short-range communication. For example, the NFC module may be implemented based on radio frequency identification (RFID) technology, Infrared Data Association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology, and other technologies.

[0245] In an exemplary embodiment, the apparatus 200 may be implemented by one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic components to perform the methods described above.

[0246] In an exemplary embodiment, a non-transitory computer-readable storage medium including instructions is also provided, such as a memory 204 including instructions, which can be executed by a processor 220 of the device 200 to perform the above-described method. For example, the non-transitory computer-readable storage medium may be a ROM, random access memory (RAM), CD-ROM, magnetic tape, floppy disk, and optical data storage device, etc.

[0247] It can be further understood that in this disclosure, "multiple" refers to two or more, and other quantifiers are similar. "And / or" describes the relationship between related objects, indicating that three relationships can exist; for example, A and / or B can represent: A alone, A and B simultaneously, and B alone. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. The singular forms "a," "the," and "the" are also intended to include the plural forms unless the context clearly indicates otherwise.

[0248] It is further understood that the terms "first," "second," etc., are used to describe various types of information, but this information should not be limited to these terms. These terms are only used to distinguish information of the same type from one another, and do not indicate a specific order or degree of importance. In fact, the expressions "first," "second," etc., are completely interchangeable. For example, without departing from the scope of this disclosure, first information can also be referred to as second information, and similarly, second information can also be referred to as first information.

[0249] It is further understood that although operations are described in a specific order in the accompanying drawings in the embodiments of this disclosure, this should not be construed as requiring these operations to be performed in the specific order or serial order shown, or requiring all of the shown operations to be performed to obtain the desired result. In certain environments, multitasking and parallel processing may be advantageous.

[0250] Other embodiments of this disclosure will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of this disclosure that follow the general principles of this disclosure and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this disclosure are indicated by the following claims.

[0251] It should be understood that this disclosure is not limited to the precise structures described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this disclosure is limited only by the appended claims.

Claims

1. A beam failure recovery method, characterized in that, Applied to network devices, the method includes: The network device determines that the terminal is configured for multiple transmit / receive point (TRP) operation; The network device configures reference signal resources for the terminal, and the reference signal resources are used for beam failure detection. If a first TRP experiences beam failure among multiple TRPs and the triggering condition for triggering random access beam failure recovery is met, then random access-based beam failure recovery is triggered, and the beam failure recovery is used for beam failure recovery of the Spcell. The triggering conditions for triggering random access beam failure recovery include: Prior to the fifth time, a second TRP among the plurality of TRPs experienced beam failure; Wherein, the fifth time is the time when the terminal receives the second downlink control information sent by the network device. The second downlink control information is used to determine that the network device has received MAC CE information and to schedule the second physical uplink shared channel. The hybrid automatic repeat request identifier of the second physical uplink shared channel scheduled by the second downlink control information is the same as the hybrid automatic repeat request identifier of the first physical uplink shared channel. The first physical uplink shared channel is used to send MAC CE information related to the TRP that has experienced beam failure. And / or the new data indication of the second physical uplink shared channel scheduled by the second downlink control information has changed.

2. The beam failure recovery method according to claim 1, characterized in that, The triggering conditions for triggering random access beam failure recovery also include: After the first time and before the second time, there is a second TRP among the plurality of TRPs where beam failure occurs; The first time represents the time when the terminal detects that the first TRP has experienced beam failure, and the second time represents the time when the terminal sends a scheduling request on the physical uplink control channel resources.

3. The beam failure recovery method according to claim 1, characterized in that, The triggering conditions for triggering random access beam failure recovery also include: Prior to the third time, a second TRP among the plurality of TRPs experienced beam failure; The third time represents the time when the terminal receives the first downlink control information for scheduling the physical uplink shared channel.

4. The beam failure recovery method according to claim 3, characterized in that, The triggering conditions for triggering random access beam failure recovery also include: Within a first duration following the second time period, no downlink control information is received. The second time period represents the time during which the terminal sends a scheduling request on the physical uplink control channel resources.

5. The beam failure recovery method according to claim 1, characterized in that, The triggering conditions for triggering random access beam failure recovery include: Prior to the fourth time, a second TRP among the plurality of TRPs experienced beam failure; The fourth time characterizes the time when the terminal transmits Media Access Control Unit (MAC CE) information related to the TRP that has experienced beam failure on the first physical uplink shared channel.

6. The beam failure recovery method according to claim 5, characterized in that, The triggering conditions for triggering random access beam failure recovery also include: The beam corresponding to the first physical uplink shared channel is the beam that has experienced beam failure; The first physical uplink shared channel is either the first downlink control information scheduling channel or a physical uplink shared channel of type 1 or type 2 with configuration authorization.

7. The beam failure recovery method according to claim 1, characterized in that, The triggering conditions for triggering random access beam failure recovery also include: During the second duration following the fourth time period, the terminal did not receive any downlink control information. The fourth time period represents the time during which the terminal transmits Media Access Control Unit (MAC CE) information related to the TRP that has experienced beam failure on the first physical uplink shared channel.

8. The beam failure recovery method according to claim 1, characterized in that, The triggering conditions for triggering random access beam failure recovery include: Prior to the sixth time, a second TRP among the plurality of TRPs experienced beam failure; The sixth time represents the time when the terminal updates the beam of the first TRP.

9. The beam failure recovery method according to claim 8, characterized in that, The method further includes: In response to the presence of a second TRP experiencing beam failure again among the plurality of TRPs after the sixth time, beam failure recovery at the TRP level is triggered.

10. The beam failure recovery method according to claim 9, characterized in that, The beam failure recovery triggered at the TRP level includes: Trigger beam failure recovery based on PUCCH-SR and / or PUSCH MAC CE.

11. The beam failure recovery method according to any one of claims 1 to 10, characterized in that, The method further includes: Trigger TRP-level beam failure recovery, or do not trigger TRP-level beam failure recovery.

12. A beam failure recovery method, characterized in that, The method includes: The network device determines that the terminal is configured for multiple transmit / receive point (TRP) operation; The network device configures reference signal resources for the terminal, and the reference signal resources are used for beam failure detection. In response to the terminal being configured with multiple TRPs, beam failure monitoring is performed on the multiple TRPs; In response to the detection that a first TRP among the plurality of TRPs has experienced beam failure, and the triggering condition for triggering random access beam failure recovery is met, the terminal triggers beam failure recovery based on random access, wherein the beam failure recovery is used for beam failure recovery of SpCell; The triggering conditions for random access beam failure recovery include: Prior to the fifth time, a second TRP among the plurality of TRPs experienced beam failure; Wherein, the fifth time is the time when the second downlink control information sent by the network device is received. The second downlink control information is used to determine that the network device has received the MAC CE information. The second downlink control information is used to schedule the second physical uplink shared channel. The hybrid automatic repeat request identifier of the second physical uplink shared channel scheduled by the second downlink control information is the same as the hybrid automatic repeat request identifier of the first physical uplink shared channel. The first physical uplink shared channel is used to send the Media Access Control Unit (MAC CE) information related to the TRP that has experienced beam failure. And / or the new data indication of the second physical uplink shared channel scheduled by the second downlink control information has changed.

13. The beam failure recovery method according to claim 12, characterized in that, The triggering conditions for triggering random access beam failure recovery also include: After the first time and before the second time, there is a second TRP among the plurality of TRPs where beam failure occurs; The first time represents the time when the terminal detects that the first TRP has experienced beam failure, and the second time represents the time when the terminal sends a scheduling request on the physical uplink control channel resources.

14. The beam failure recovery method according to claim 12, characterized in that, The triggering conditions for triggering random access beam failure recovery also include: Prior to the third time, a second TRP among the plurality of TRPs experienced beam failure; The third time represents the time when the terminal receives the first downlink control information for scheduling the physical uplink shared channel.

15. The beam failure recovery method according to claim 14, characterized in that, The triggering conditions for triggering random access beam failure recovery also include: Within a first duration following the second time period, no downlink control information is received. The second time period represents the time during which the terminal sends a scheduling request on the physical uplink control channel resources.

16. The beam failure recovery method according to claim 12, characterized in that, The triggering conditions for triggering random access beam failure recovery include: Prior to the fourth time, a second TRP among the plurality of TRPs experienced beam failure; The fourth time characterizes the time when the terminal transmits Media Access Control Unit (MAC CE) information related to the TRP that has experienced beam failure on the first physical uplink shared channel.

17. The beam failure recovery method according to claim 16, characterized in that, The triggering conditions for triggering random access beam failure recovery also include: The beam corresponding to the first physical uplink shared channel is the beam that has experienced beam failure; The first physical uplink shared channel is either the first downlink control information scheduling channel or a physical uplink shared channel of type 1 or type 2 with configuration authorization.

18. The beam failure recovery method according to claim 12, characterized in that, The triggering conditions for triggering random access beam failure recovery also include: During the second duration following the fourth time period, the terminal did not receive any downlink control information. The fourth time period represents the time during which the terminal transmits Media Access Control Unit (MAC CE) information related to the TRP that has experienced beam failure on the first physical uplink shared channel.

19. The beam failure recovery method according to claim 12, characterized in that, The triggering conditions for triggering random access beam failure recovery include: Prior to the sixth time, a second TRP among the plurality of TRPs experienced beam failure; The sixth time represents the time when the terminal updates the beam of the first TRP.

20. The beam failure recovery method according to claim 19, characterized in that, The method further includes: In response to the presence of a second TRP experiencing beam failure again among the plurality of TRPs after the sixth time, beam failure recovery at the TRP level is triggered.

21. The beam failure recovery method according to claim 20, characterized in that, The beam failure recovery triggered at the TRP level includes: Trigger beam failure recovery based on PUCCH-SR and / or PUSCH MAC CE.

22. The beam failure recovery method according to any one of claims 12 to 21, characterized in that, The method further includes: Trigger TRP-level beam failure recovery, or do not trigger TRP-level beam failure recovery.

23. A beam failure recovery device, characterized in that, include: The monitoring unit is configured to determine if the terminal is configured for multiple transmit / receive point (TRP) operation; The terminal is configured with reference signal resources, which are used for beam failure detection. The processing unit is configured to trigger beam failure recovery based on random access when a first TRP in a plurality of TRPs has experienced beam failure and the triggering condition for triggering random access beam failure recovery is met. The beam failure recovery is used for beam failure recovery of the Spcell. The triggering conditions for triggering random access beam failure recovery include: Before the fifth time, the monitoring unit detected a second TRP among the plurality of TRPs that had experienced beam failure using the following method; Wherein, the fifth time is the time when the terminal receives the second downlink control information sent by the network device. The second downlink control information is used to determine that the network device has received MAC CE information and to schedule the second physical uplink shared channel. The hybrid automatic repeat request identifier of the second physical uplink shared channel scheduled by the second downlink control information is the same as the hybrid automatic repeat request identifier of the first physical uplink shared channel. The first physical uplink shared channel is used to send MAC CE information related to the TRP that has experienced beam failure. And / or the new data indication of the second physical uplink shared channel scheduled by the second downlink control information has changed.

24. A communication system, characterized in that, The system includes terminals and network devices: The network device determines that the terminal is configured for multiple transmit / receive point (TRP) operation; The network device configures reference signal resources for the terminal, and the reference signal resources are used for beam failure detection. In response to the terminal being configured with multiple TRPs, beam failure monitoring is performed on the multiple TRPs; In response to the detection that a first TRP among the plurality of TRPs has experienced beam failure, and the triggering condition for triggering random access beam failure recovery is met, the terminal triggers beam failure recovery based on random access, wherein the beam failure recovery is used for beam failure recovery of SpCell; The triggering conditions for random access beam failure recovery include: Prior to the fifth time, a second TRP among the plurality of TRPs experienced beam failure; Wherein, the fifth time is the time when the second downlink control information sent by the network device is received. The second downlink control information is used to determine that the network device has received the MAC CE information. The second downlink control information is used to schedule the second physical uplink shared channel. The hybrid automatic repeat request identifier of the second physical uplink shared channel scheduled by the second downlink control information is the same as the hybrid automatic repeat request identifier of the first physical uplink shared channel. The first physical uplink shared channel is used to send the Media Access Control Unit (MAC CE) information related to the TRP that has experienced beam failure. And / or the new data indication of the second physical uplink shared channel scheduled by the second downlink control information has changed.

25. A beam failure recovery device, characterized in that, include: processor; Memory used to store processor-executable instructions; The processor is configured to execute the beam failure recovery method according to any one of claims 1 to 11.

26. A storage medium, characterized in that, The storage medium stores instructions that, when executed by the terminal's processor, enable the terminal to perform the beam failure recovery method according to any one of claims 1 to 11.

Images