IP Library Granted Patent US 12,191,962
Granted Patent B2
US 12,191,962 · App. 17/383,758 · Granted Jan 7, 2025

Method for beam failure recovery, method for beam failure handling, terminal, and network-side device

Inventors: Yu Yang (Chang'an Dongguan, CN); Peng Sun (Chang'an Dongguan, CN); Xueming Pan (Chang'an Dongguan, CN)
Assignee: VIVO MOBILE COMMUNICATION CO., LTD.
H04B7/0695H04W16/28H04W72/046H04W72/0466H04W72/23H04W76/19
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,191,962
App. No.
17/383,758
Granted
Jan 7, 2025
Kind
B2
Abstract

This disclosure provides a method for beam failure recovery, a method for beam failure handling, a terminal, and a network-side device. The method includes: obtaining N pieces of configuration information, where the N pieces of configuration information are applicable to different transmission and reception points TRPs, and the configuration information includes a parameter for beam failure recovery; and in a case that a beam failure event occurring on at least one TRP is determined, transmitting a beam failure recovery request based on the configuration information.

Claims (137)

1. A method for beam failure recovery, comprising:

obtaining, by a terminal, N pieces of configuration information, wherein the N pieces of configuration information are applicable to different transmission and reception points (TRPs), the configuration information comprises a parameter for beam failure recovery, and N is an integer greater than 1; and

in a case that a beam failure event occurring on at least one TRP is determined, transmitting, by the terminal, a beam failure recovery request based on the configuration information;

wherein in a case that a beam failure event occurs on M TRPs, and first resources, used for transmitting a beam failure recovery request by the terminal, in configuration information of the M TRPs are the same, wherein M is an integer greater than 1,

the transmitting a beam failure recovery request based on the configuration information comprises:

transmitting a beam failure recovery request to a higher-priority TRP in the M TRPs with the beam failure event by using the first resource in the configuration information of the M TRPS;

wherein a priority of the TRP is determined based on spatial relation information.

2. The method according to claim 1 , wherein different TRPs are identified by at least one of the following manners:

different control resource sets;

different control resource set groups;

different explicitly defined TRPs;

different transmission configuration indicator states;

different transmission configuration indicator state lists;

different transmission configuration indicator state pools;

different quasi co-location (QCL);

different quasi co-location (QCL) groups;

different spatial relations;

different spatial relation groups;

different physical downlink control channel (PDCCH) scrambling identifiers;

different PDCCH scrambling identifier groups;

different physical downlink shared channel (PDSCH) scrambling identifiers;

different PDSCH scrambling identifier groups;

different PDCCH-Config information elements; or

different PDSCH-Config information elements.

3. The method according to claim 1 , wherein the configuration information comprises at least one of the following:

a beam failure detection reference signal;

a candidate beam reference signal;

a first resource used for transmitting a beam failure recovery request by the terminal; or

a second resource used for transmitting a beam failure recovery request response by a network-side device.

4. The method according to claim 3 , wherein configuration information of different TRPs satisfies at least one of the following conditions:

that beam failure detection reference signals are different;

that candidate beam reference signals are different;

that first resources used for transmitting a beam failure recovery request by the terminal are different;

that first resources used for transmitting a beam failure recovery request by the terminal are the same;

that second resources used for transmitting a beam failure recovery request response by the network-side device are different; or

that second resources used for transmitting a beam failure recovery request response by the network-side device are the same.

5. The method according to claim 1 , wherein the obtaining N pieces of configuration information comprises:

obtaining the N pieces of configuration information that are configured by a network-side device in one bandwidth part (BWP).

6. The method according to claim 1 , wherein in a case that a beam failure event occurs on a first TRP, the transmitting a beam failure recovery request based on the configuration information comprises:

transmitting a beam failure recovery request to the first TRP based on a first resource, used for transmitting a beam failure recovery request by the terminal, in configuration information corresponding to the first TRP;

or

transmitting a beam failure recovery request to a second TRP based on a first resource, used for transmitting a beam failure recovery request by the terminal, in configuration information corresponding to the second TRP other than the first TRP, wherein the beam failure recovery request is forwarded to the first TRP by the second TRP.

7. The method according to claim 1 , wherein in a case that a beam failure event occurs on M TRPs, and first resources, used for transmitting a beam failure recovery request by the terminal, in configuration information of the M TRPs are different, wherein M is an integer greater than 1,

the transmitting a beam failure recovery request based on the configuration information comprises:

transmitting a beam failure recovery request to each of the M TRPs with the beam failure event by using different first resources in the configuration information of the M TRPs; and/or

wherein in a case that a beam failure event occurs on M TRPs, and second resources, used for transmitting a beam failure recovery request response by a network-side device, in configuration information of the M TRPs are the same, wherein M is an integer greater than 1, the method further comprises:

receiving a beam failure recovery request response that is transmitted by a higher-priority TRP in the M TRPs with the beam failure event by using the second resource in the configuration information.

8. The method according to claim 7 , wherein the second resource, used for transmitting a beam failure recovery request response by the network-side device, in the configuration information comprises:

a control resource set for beam failure recovery (CORESET-BFR).

9. The method according to claim 1 , wherein a priority of the TRP is further determined based on at least one of the following information:

index information of a control resource set;

index information of a control resource set group;

identification information of an explicitly defined TRP;

information about a transmission configuration indicator state;

information about a transmission configuration indicator state list;

information about a transmission configuration indicator state pool;

quasi-co-location (QCL) information;

quasi-co-location (QCL) group information;

PDCCH scrambling identifier information;

PDCCH scrambling identifier group information;

PDSCH scrambling identifier information;

PDSCH scrambling identifier group information;

information about a PDCCH-Config information element; or

information about a PDSCH-Config information element.

10. The method according to claim 1 , further comprising:

if a preset condition is satisfied, transmitting, by the terminal by using spatial relation information of a PUCCH associated with a TRP with a beam failure event, the PUCCH within a preset period of time.

11. The method according to claim 10 , wherein the preset condition is at least one of the following:

the terminal receives downlink information that is transmitted by the TRP with the beam failure event;

the terminal transmits a beam failure recovery request to the TRP with the beam failure event; or

the terminal transmits a beam failure recovery request to the TRP with the beam failure event, and does not receive, within a first preset duration, downlink information transmitted by the TRP with the beam failure event; and/or

wherein the preset period of time starts:

when the preset condition is satisfied; or

when a second preset duration elapses after the preset condition is satisfied; and/or

wherein the spatial relation information of the PUCCH associated with the TRP with the beam failure event is determined in one of the following manners:

using spatial relation information of an uplink channel for transmitting a beam failure recovery request in a preset cell;

using spatial relation information or QCL information of a preset channel in the preset cell;

using spatial relation information or QCL information of a preset reference signal in the preset cell;

using spatial relation information or QCL information of a preset channel in a primary cell; or

using spatial relation information or QCL information of a preset reference signal in the primary cell.

12. The method according to claim 1 , further comprising:

skipping transmitting a PUCCH in a case that after transmitting a beam failure recovery request to a TRP with a beam failure event, the terminal does not receive, within a third preset duration, downlink information that is transmitted by the TRP with the beam failure event.

13. The method according to claim 12 , wherein the downlink information comprises at least one of the following:

a PDCCH on a control resource set for beam failure recovery (CORESET-BFR) associated with the TRP with the beam failure event;

downlink control information (DCI);

a random access response (RAR);

a release command or deactivation command used for releasing a cell with a beam failure;

information triggering beam measurement and/or beam reporting for the TRP with the beam failure event;

information triggering channel state information (CSI) measurement and/or CSI reporting for the TRP with the beam failure event; or

acknowledgement (ACK) or negative acknowledgement (NACK) corresponding to scheduling information of the TRP with the beam failure event.

14. A terminal, comprising a processor, a memory, and a computer program stored in the memory and capable of running on the processor, wherein the computer program is executed by the processor to implement:

obtaining N pieces of configuration information, wherein the N pieces of configuration information are applicable to different transmission and reception points (TRPs), the configuration information comprises a parameter for beam failure recovery, and N is an integer greater than 1; and

in a case that a beam failure event occurring on at least one TRP is determined, transmitting a beam failure recovery request based on the configuration information;

wherein in a case that a beam failure event occurs on M TRPs, and first resources, used for transmitting a beam failure recovery request by the terminal, in configuration information of the M TRPs are the same, wherein M is an integer greater than 1,

the transmitting a beam failure recovery request based on the configuration information comprises:

transmitting a beam failure recovery request to a higher-priority TRP in the M TRPs with the beam failure event by using the first resource in the configuration information of the M TRPs;

wherein a priority of the TRP is determined based on spatial relation information.

15. The terminal according to claim 14 , wherein different TRPs are identified by at least one of the following manners:

different control resource sets;

different control resource set groups;

different explicitly defined TRPs;

different transmission configuration indicator states;

different transmission configuration indicator state lists;

different transmission configuration indicator state pools;

different quasi co-location (QCL);

different quasi co-location (QCL) groups;

different spatial relations;

different spatial relation groups;

different physical downlink control channel (PDCCH) scrambling identifiers;

different PDCCH scrambling identifier groups;

different physical downlink shared channel (PDSCH) scrambling identifiers;

different PDSCH scrambling identifier groups;

different PDCCH-Config information elements; or

different PDSCH-Config information elements.

16. The terminal according to claim 14 , wherein the configuration information comprises at least one of the following:

a beam failure detection reference signal;

a candidate beam reference signal;

a first resource used for transmitting a beam failure recovery request by the terminal; or

a second resource used for transmitting a beam failure recovery request response by a network-side device.

17. The terminal according to claim 16 , wherein configuration information of different TRPs satisfies at least one of the following conditions:

that beam failure detection reference signals are different;

that candidate beam reference signals are different;

that first resources used for transmitting a beam failure recovery request by the terminal are different;

that first resources used for transmitting a beam failure recovery request by the terminal are the same;

that second resources used for transmitting a beam failure recovery request response by the network-side device are different; or

that second resources used for transmitting a beam failure recovery request response by the network-side device are the same.

18. The terminal according to claim 14 , wherein the computer program is further executed by the processor to implement:

obtaining the N pieces of configuration information that are configured by a network-side device in one bandwidth part (BWP).

19. The terminal according to claim 14 , wherein in a case that a beam failure event occurs on a first TRP, the computer program is further executed by the processor to implement:

transmitting a beam failure recovery request to the first TRP based on a first resource, used for transmitting a beam failure recovery request by the terminal, in configuration information corresponding to the first TRP;

or

transmitting a beam failure recovery request to a second TRP based on a first resource, used for transmitting a beam failure recovery request by the terminal, in configuration information corresponding to the second TRP other than the first TRP, wherein the beam failure recovery request is forwarded to the first TRP by the second TRP.

20. A network-side device, comprising a processor, a memory, and a computer program stored in the memory and capable of running on the processor, wherein the computer program is executed by the processor to implement:

obtaining N pieces of configuration information, wherein the N pieces of configuration information are applicable to different transmission and reception points (TRPs), the configuration information comprises a parameter for beam failure recovery, and N is an integer greater than 1; and

in a case that a beam failure event occurring on at least one TRP is determined, transmitting a beam failure recovery request based on the configuration information;

wherein in a case that a beam failure event occurs on M TRPs, and first resources, used for transmitting a beam failure recovery request by the terminal, in configuration information of the M TRPs are different, wherein M is an integer greater than 1, the method further comprises:

receiving a beam failure recovery request that is transmitted by the terminal to a higher-priority TRP in the M TRPs with the beam failure event by using the first resource in the configuration information of the M TRPs;

wherein a priority of the TRP is determined based on spatial relation information.

Assignments (2)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 27, 2025
From: VIVO MOBILE COMMUNICATION CO., LTD.
To: KONINKLIJKE PHILIPS N.V.
Reel/Frame 071411/0483 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 23, 2021
From: YANG, YU; SUN, PENG; PAN, XUEMING
To: VIVO MOBILE COMMUNICATION CO., LTD.
Reel/Frame 056959/0664 →
Priority Claims (1)
CN 201910075898.1 · Jan 25, 2019 · national
Continuity (2)
Continuation PCTCN2020070079 · Jan 2, 2020
Related Publication 20210351834A1 · Nov 11, 2021
References Cited (59)
US 11743964B2 · Ahn · 2023 [cited by examiner]
US 20160164657A1 · Fan · 2016 [cited by applicant]
US 20180227899A1 · Yu · 2018 [cited by applicant]
US 20180234960A1 · Nagaraja et al. · 2018 [cited by applicant]
US 20180287860A1 · Xia · 2018 [cited by applicant]
US 20180302889A1 · Guo · 2018 [cited by examiner]
US 20190173740A1 · Zhang · 2019 [cited by examiner]
US 20190215863A1 · Kim · 2019 [cited by examiner]
US 20190372830A1 · Zhang · 2019 [cited by examiner]
US 20200099461A1 · Chen et al. · 2020 [cited by applicant]
US 20200106510A1 · Song et al. · 2020 [cited by applicant]
US 20200137801A1 · Chen et al. · 2020 [cited by applicant]
US 20200323015A1 · Jia · 2020 [cited by examiner]
US 20210014708A1 · Kim · 2021 [cited by examiner]
US 20210176773A1 · Jiang · 2021 [cited by examiner]
US 20210274404A1 · Koziol · 2021 [cited by examiner]
US 20210282168A1 · Matsumura et al. · 2021 [cited by applicant]
US 20210289372A1 · Liu et al. · 2021 [cited by applicant]
US 20210320764A1 · Gao · 2021 [cited by examiner]
US 20220021495A1 · Zhang · 2022 [cited by examiner]
US 20230032501A1 · Li · 2023 [cited by examiner]
US 20230121938A1 · Zhou · 2023 [cited by examiner]
CN 108811092A · 2018 [cited by applicant]
CN 108988978A · 2018 [cited by applicant]
CN 109076365A · 2018 [cited by applicant]
CN 109151869A · 2019 [cited by applicant]
CN 110896546B · 2022 [cited by examiner]
EP 3855661A1 · 2021 [cited by examiner]
RU 2631261C2 · 2017 [cited by applicant]
WO 2018227441A1 · 2018 [cited by applicant]
WO 2018237400A1 · 2018 [cited by applicant]
WO 2020012619A1 · 2020 [cited by applicant]
Wang, “Beam Failure Recovery Method and Device, Storage Medium User Equipment,” English Machine Translation of Wang (CN 110896546 B), Clarivate Analytics, pp. 1-14 (Year: 2023). [cited by examiner]
First Korean Office Action related to Application No. 10-2021-7026027; reported on Jan. 18, 2023. [cited by applicant]
R1-1809855—Source: NTT DOCOMO, Inc. “Offline summary for PDCCH structure and search space”, Agenda Item: 7.1.3.1, Document for: Discussion and Decision, 3GPP TSG RAN WG1 Meeting #94, Gothenburg, Sweden, Aug. 20-24, 2018. [cited by applicant]
R1-1900218—Source: MediaTek Inc. “Enhancements on multi-beam operations”, Agenda Item: 7.2.8.3, Document for: Discussion, 3GPP TSG RAN WG1 Ad-Hoc Meeting 1901, Taipei, Taiwan, Jan. 21-25, 2019. [cited by applicant]
International Search Report & Written Opinion related to Application No. PCT/CN2020/070079; reported on Aug. 5, 2021. [cited by applicant]
First Chinese Office Action for related Application No. 201910075898.1; reported on Dec. 29, 2021. [cited by applicant]
3rd Generation Partnership Project, “Technical Specification Group Radio Access Network; Study on New Radio (NR) Access Technology Physical Layer Aspects”, Nov. 2016, 3GPP TR 38,802 V1.0.0, Valbonne, France. [cited by applicant]
3rd Generation Partnership Project, “Technical Specification Group Radio Access Network; Study on New Radio (NR) Access Technology; Physical Layer Aspects”, Mar. 2017, 3GPP TR 38.802 V2.0.0, Valbonne, France,. [cited by applicant]
Intel Corporation, “Summary on SCell BFR and Beam Measurement”, Oct. 8-12, 2018, 3GPP TSG RAN WG1 Meeting #94b, Chengdu, China. [cited by applicant]
Convida Wireless, “On Beam Failure Recovery for SCell”, Nov. 12-16, 2018, 3GPP TSG-RAN WG1 Meeting #95, Spokane, USA. [cited by applicant]
Lenovo, Motorola Mobility, “Resource configuration for beam failure recovery request”, Jun. 27-29, 2017, 3GPP TSG-RAN WG2 Meeting#AH, Qingdao, China. [cited by applicant]
Huawei, Hisilicon, “non-contention based random access for beam failure recovery in CA”, Jan. 22-26, 2018, 3GPP TSG-RAN WG2#AH-1801, Vancouver, Canada. [cited by applicant]
Ericsson, “Beam Failure Recovery in Scell and contention-based BFR on SpCell”, Apr. 16-20, 2018, 3GPP TSG-RAN WG2 #101Bis, Sanya, P.R. of China. [cited by applicant]
Huawei, Hisilicon, “ASN.1 for Beam Failure Recovery”, Apr. 16-20, 2018, 3GPP TSG-RAN WG2 Meeting 101bis, Sanya, China. [cited by applicant]
Huawei, Hisilicon, “Discussion on beam failure recovery for SCell”, May 21-25, 2018, 3GPP TSG-RAN WG2 Meeting 102, Busan, Korea. [cited by applicant]
NTT DOCOMO, Inc., “Presentation of Specification/Report to TSG: TR 38.802, Version 2.0.0”, Mar. 6-9, 2017, 3GPP TSG-RAN Meeting #75, Dubrovnik, Croatia. [cited by applicant]
First Japanese Office Action for related Application No. 2021-542547; reported on Aug. 29, 2022. [cited by applicant]
Spreadtrum Communications, “Discussion on multi-beam operation”, Jan. 21-25, 2019, 3GPP TSG RAN WG1 Ad-Hoc Meeting 1901, R1-1900700, Taipei. [cited by applicant]
Intel Corporation, “Summary on SCell BFR and L1-SINR based beam selection”, Jan. 21-25, 2019, 3GPP TSG RAN WG1 Ad-Hoc Meeting 1901, R1-1901443, Taipei. [cited by applicant]
Extended European Search Report related to Application No. 20744732.7 reported on Jun. 13, 2022. [cited by applicant]
Chinese Office Action related to Application No. 201910075898.1 reported on Jul. 14, 2022. [cited by applicant]
Russian Office Action related to Application No. 2021124931.7 reported on May 16, 2022. [cited by applicant]
R1-1716169, Source: AT&T, “On beam recovery for partial and full control channel failure” Document for: Discussion/Approval, Agenda item: 6.2.2.4, Release: 3GPP TSG RAN WG1 Meeting NR#3, Sep. 18-21, 2017, Nagoya, Japan. [cited by applicant]
R1-1710058, Source: CATT, “Considerations on DL beam failure and recovery” Document for: Discussion and Decision, Agenda item: 5.1.2.2.2, Release: 3GPP TSG RAN WG1 NR Ad-Hoc#2, Jun. 27-30, 2017, Qingdao, P.R. China. [cited by applicant]
R1-1707255, Source: Fujitsu, “Discussion on beam failure recovery procedure” Document for: Discussion/Decision, Agenda Item: 7.1.2.2.2, Release: 3GPP TSG RAN WG1 Meeting #89, May 15-19, 2017, Hangzhou, P.R. China. [cited by applicant]
R1-1900092, Source: ZTE, “Additional considerations on beam management for multi-TRP” Document for: Discussion and Decision, Agenda Item: 7.2.8.6, Release: 3GPP TSG RAN WG1 Ad-Hoc Meeting 1901, Jan. 21-25, 2019, Taipei. [cited by applicant]
R2-1706680, Source: AT&T. “Beam Failure Recovery Mechanism and RLF” Document for: Discussion, Agenda item: 10.2.9, Release: 3GPP TSG-RAN WG2 NR-Adhoc, Jun. 27-29, 2017, Qingdao, China. [cited by applicant]
Cited By (5)
US 12,408,158 US 12,438,588 US 12,439,469 US 12,526,716 US 12,628,230