IP Library › Granted Patent US 12,381,614
Granted Patent B2
US 12,381,614 · App. 18/670,847 · Granted Aug 5, 2025

Beam management for cells in wireless communications

Inventors: Ali Cirik (Chantilly, VA); Esmael Hejazi Dinan (McLean, VA); Hua Zhou (Vienna, VA); Alireza Babaei (Fairfax, VA); Hyoungsuk Jeon (Centreville, VA); Kyungmin Park (Vienna, VA); Kai Xu (Herndon, VA)
Assignee: Ofinno, LLC
H04W76/19H04B17/327H04W72/1268H04W72/23
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,381,614
App. No.
18/670,847
Granted
Aug 5, 2025
Kind
B2
Abstract

Wireless communications and beam failure recovery are described. A wireless device may send one or more messages associated with a beam failure recovery for one or more cells. The one or more message may comprise an indication that a candidate beam is not available. The one or more message may comprise at least one value to indicate information associated with a candidate beam.

Claims (106)

1. A method comprising:

receiving, by a wireless device, at least one configuration parameter for a beam failure recovery (BFR) procedure of a plurality of cells, wherein the at least one configuration parameter indicates:

first candidate reference signals (RSs) for a first cell of the plurality of cells; and

second candidate reference signals (RSs) for a second cell of the plurality of cells; and

based on detection of beam failure of the plurality of cells, transmitting a BFR medium access control (MAC) control element (CE) indicating the detection of the beam failure of the plurality of cells, wherein the BFR MAC CE comprises:

a first field associated with a candidate RS identifier (ID) indication, wherein the first field is for the first cell of the plurality of cells, and wherein a first value for the first field has a value of zero that indicates no candidate RS, among the first candidate RSs, has a reference signal received power (RSRP) equal to or higher than a first RSRP threshold; and

a second field associated with a candidate RS ID indication, wherein the second field is for a second cell of the plurality of cells, and wherein a second value for the second field is configured to indicate information associated with a candidate RS, among the second candidate RSs, with an RSRP above a second RSRP threshold.

2. The method of claim 1 , wherein the transmitting the BFR MAC CE comprises:

transmitting a MAC protocol data unit (PDU) comprising:

a MAC subheader associated with the BFR MAC CE, wherein based on the BFR MAC CE being a variable-sized MAC CE, the MAC subheader comprises a length (L) field indicating a non-zero value; and

the BFR MAC CE.

3. The method of claim 1 , wherein the at least one configuration parameter further indicates:

the first RSRP threshold; and

the second RSRP threshold.

4. A wireless device comprising:

one or more processors; and

memory storing instructions that, when executed by the one or more processors, cause the wireless device to:

receive one or more radio resource control (RRC) messages comprising configuration parameters of a primary cell (PCell) and a secondary cell (SCell), wherein the configuration parameters comprise:

uplink bandwidth part (BWP) configuration parameters for an uplink BWP of the PCell, wherein the uplink BWP configuration parameters comprise, for a beam failure recovery (BFR) of the PCell:

a first candidate beam reference signal (RS) list parameter indicating one or more first candidate RSs; and

a first reference signal received power (RSRP) threshold parameter indicating a first threshold;

downlink BWP configuration parameters for a downlink BWP of the SCell, wherein the downlink BWP configuration parameters comprise, for a BFR of the SCell:

a second candidate beam RS list parameter indicating one or more second candidate RSs; and

a second RSRP threshold parameter indicating a second threshold; and

transmit a BFR medium access control (MAC) control element (CE) with a variable size determined based on a number of SCells detected to have beam failure, wherein the BFR MAC CE comprises:

a first field indicating the SCell; and

a second field with a value of zero, wherein the value of zero indicates that no candidate RS among the one or more second candidate RSs has an RSRP equal to or higher than the second threshold of the SCell.

5. The wireless device of claim 4 , wherein the instructions further cause the wireless device to:

trigger, based on not having uplink shared channel (UL-SCH) resources to transmit the BFR MAC CE, a scheduling request (SR); and

receive a downlink control information (DCI) indicating an uplink grant, wherein the BFR MAC CE is transmitted via one or more UL-SCH resources indicated by the uplink grant.

6. The wireless device of claim 5 , wherein the instructions further cause the wireless device to cancel, if pending, the SR based on a MAC protocol data unit (PDU) comprising the BFR MAC CE being transmitted.

7. The wireless device of claim 6 , wherein a logical channel of the BFR MAC CE has:

a higher priority than a logical channel of a configured grant confirmation MAC CE, and a logical channel of buffer status reporting (BSR) MAC CE; and

a lower priority than a logical channel of a cell radio network temporary identifier (C-RNTI) MAC CE or data from uplink common control channel (UL-CCCH).

8. The wireless device of claim 7 , wherein the instructions further cause the wireless device to:

receive, after transmitting the BFR MAC CE, an acknowledgment for the BFR MAC CE; and

complete a BFR of the SCell based on receiving the acknowledgment for the BFR MAC CE.

9. The wireless device of claim 8 , wherein the second field with the value of zero indicates that the wireless device has not identified a candidate RS for the BFR of the SCell.

10. The wireless device of claim 7 , wherein the BFR MAC CE further comprises:

a third field indicating a second SCell; and

a fourth field indicating a candidate RS of the second SCell, wherein an RSRP of the candidate RS of the second SCell is equal to or higher than a third threshold of the second SCell.

11. The wireless device of claim 7 , wherein the BFR MAC CE further comprises:

a third field indicating a second SCell; and

a fourth field with a value of zero.

12. The wireless device of claim 11 , wherein the fourth field with the value of zero indicates that no candidate RS among one or more third candidate RSs of the second SCell has an RSRP equal to or higher than a third threshold of the second SCell.

13. The wireless device of claim 11 , wherein the fourth field with the value of zero indicates that the wireless device has not identified a candidate RS for a BFR of the second SCell.

14. The wireless device of claim 5 , wherein, based on the SCell being deactivated, the instructions further cause the wireless device to:

stop transmission of the SR; and

abort a BFR of the SCell.

15. The wireless device of claim 14 , wherein a logical channel of the BFR MAC CE has:

a higher priority than a logical channel of a configured grant confirmation MAC CE, and a logical channel of buffer status reporting (BSR) MAC CE; and

a lower priority than a logical channel of a cell radio network temporary identifier (C-RNTI) MAC CE or data from uplink common control channel (UL-CCCH).

16. The wireless device of claim 5 , wherein the instructions further cause the wireless device to cancel, based on a request of a reset of a MAC entity of the wireless device, the SR.

17. The wireless device of claim 16 , wherein a logical channel of the BFR MAC CE has:

a higher priority than a logical channel of a configured grant confirmation MAC CE, and a logical channel of buffer status reporting (BSR) MAC CE; and

a lower priority than a logical channel of a cell radio network temporary identifier (C-RNTI) MAC CE or data from uplink common control channel (UL-CCCH).

18. The wireless device of claim 4 , wherein the BFR MAC CE further comprises:

a third field indicating a second SCell; and

a fourth field indicating a candidate RS of the second SCell, wherein an RSRP of the candidate RS of the second SCell is equal to or higher than a third threshold of the second SCell.

19. The wireless device of claim 18 , wherein the instructions further cause the wireless device to:

trigger, based on not having uplink shared channel (UL-SCH) resources to transmit the BFR MAC CE, a scheduling request (SR); and

receive a downlink control information (DCI) indicating an uplink grant, wherein the BFR MAC CE is transmitted via one or more UL-SCH resources indicated by the uplink grant.

20. The wireless device of claim 19 , wherein a logical channel of the BFR MAC CE has:

a higher priority than a logical channel of a configured grant confirmation MAC CE, and a logical channel of buffer status reporting (BSR) MAC CE; and

a lower priority than a logical channel of a cell radio network temporary identifier (C-RNTI) MAC CE or data from uplink common control channel (UL-CCCH).

21. The wireless device of claim 20 , wherein the instructions further cause the wireless device to:

receive, after transmitting the BFR MAC CE, an acknowledgment for the BFR MAC CE;

complete a BFR of the SCell based on receiving the acknowledgment for the BFR MAC CE; and

cancel, if pending, the SR based on a MAC protocol data unit (PDU) comprising the BFR MAC CE being transmitted.

22. The wireless device of claim 4 , wherein a logical channel of the BFR MAC CE has:

a higher priority than a logical channel of a configured grant confirmation MAC CE, and a logical channel of buffer status reporting (BSR) MAC CE; and

a lower priority than a logical channel of a cell radio network temporary identifier (C-RNTI) MAC CE or data from uplink common control channel (UL-CCCH).

23. The wireless device of claim 22 , wherein the instructions further cause the wireless device to:

trigger, based on not having uplink shared channel (UL-SCH) resources to transmit the BFR MAC CE, a scheduling request (SR); and

receive a downlink control information (DCI) indicating an uplink grant, wherein the BFR MAC CE is transmitted via one or more UL-SCH resources indicated by the uplink grant.

24. The wireless device of claim 23 , wherein the second field with the value of zero indicates that the wireless device has not identified a candidate RS for the BFR of the secondary cell.

25. The wireless device of claim 23 , wherein the BFR MAC CE further comprises:

a third field indicating a second SCell; and

a fourth field indicating a candidate RS of the second SCell, wherein an RSRP of the candidate RS of the second SCell is equal to or higher than a third threshold of the second SCell.

26. The wireless device of claim 23 , wherein the BFR MAC CE further comprises:

a third field indicating a second SCell; and

a fourth field with a value of zero.

27. The wireless device of claim 26 , wherein the fourth field with the value of zero indicates that no candidate RS among one or more third candidate RSs of the second SCell has an RSRP equal to or higher than a third threshold of the second SCell.

28. The wireless device of claim 26 , wherein the fourth field with the value of zero indicates that the wireless device has not identified a candidate RS for a BFR of the second SCell.

29. The wireless device of claim 4 , wherein the instructions further cause the wireless device to cancel, based on a request of a reset of a MAC entity of the wireless device, a scheduling request (SR) triggered based on not having uplink shared channel (UL-SCH) resources to transmit the BFR MAC CE.

30. The wireless device of claim 29 , wherein the second field with the value of zero indicates that the wireless device has not identified a candidate RS for the BFR of the secondary cell.

31. The wireless device of claim 30 , wherein the instructions further cause the wireless device to:

trigger, based on not having the UL-SCH resources to transmit the BFR MAC CE, the SR; and

receive a downlink control information (DCI) indicating an uplink grant, wherein the the BFR MAC CE is transmitted via one or more UL-SCH resources indicated by the uplink grant.

32. The wireless device of claim 31 , wherein the instructions further cause the wireless device to cancel, if pending, the SR based on a MAC protocol data unit (PDU) comprising the BFR MAC CE being transmitted.

33. The wireless device of claim 4 , wherein the instructions further cause the wireless device to cancel, if pending, a scheduling request (SR) based on a MAC protocol data unit (PDU) comprising the BFR MAC CE being transmitted.

34. The wireless device of claim 33 , wherein a logical channel of the BFR MAC CE has:

a higher priority than a logical channel of a configured grant confirmation MAC CE, and a logical channel of buffer status reporting (BSR) MAC CE; and

a lower priority than a logical channel of a cell radio network temporary identifier (C-RNTI) MAC CE or data from uplink common control channel (UL-CCCH).

35. The wireless device of claim 34 , wherein the instructions further cause the wireless device to:

receive, after transmitting the BFR MAC CE, an acknowledgment for the BFR MAC CE; and

complete a BFR of the SCell based on receiving the acknowledgment for the BFR MAC CE.

36. The wireless device of claim 35 , wherein the second field with the value of zero indicates that the wireless device has not identified a candidate RS for the BFR of the secondary cell.

37. The wireless device of claim 35 , wherein the BFR MAC CE further comprises:

a third field indicating a second SCell; and

a fourth field indicating a candidate RS of the second SCell, wherein an RSRP of the candidate RS of the second SCell is equal to or higher than a third threshold of the second SCell.

38. The wireless device of claim 35 , wherein the BFR MAC CE further comprises:

a third field indicating a second SCell; and

a fourth field with a value of zero.

39. The wireless device of claim 38 , wherein the fourth field with the value of zero indicates that no candidate RS among one or more third candidate RSs of the second SCell has an RSRP equal to or higher than a third threshold of the second SCell.

40. The wireless device of claim 38 , wherein the fourth field with the value of zero indicates that the wireless device has not identified a candidate RS for a BFR of the second SCell.

Assignments (3)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 19, 2024
From: COMCAST CABLE COMMUNICATIONS, LLC
To: OFINNO, LLC
Reel/Frame 069643/0230 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 13, 2024
From: CIRIK, ALI; DINAN, ESMAEL; ZHOU, HUA; JEON, HYOUNGSUK; PARK, KYUNGMIN; XU, KAI; BABAEI, ALIREZA
To: COMCAST CABLE COMMUNICATIONS, LLC
Reel/Frame 067719/0977 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 13, 2024
From: CIRIK, ALI; DINAN, ESMAEL; ZHOU, HUA; BABAEI, ALIREZA; JEON, HYOUNGSUK; PARK, KYUNGMIN; XU, KAI
To: COMCAST CABLE COMMUNICATIONS, LLC
Reel/Frame 067720/0070 →
Continuity (3)
Continuation 16670225 · Oct 31, 2019
Provisional Application 62753288 · Oct 31, 2018
Related Publication 20240314874A1 · Sep 19, 2024
References Cited (132)
US 11006441B2 · Shih · 2021 [cited by examiner]
US 11259306B2 · Koskela et al. · 2022 [cited by applicant]
US 11336357B2 · Koskela et al. · 2022 [cited by applicant]
US 12035404B2 · Cirik · 2024 [cited by examiner]
US 12041594B2 · Koskela et al. · 2024 [cited by applicant]
US 20180270700A1 · Babaei et al. · 2018 [cited by applicant]
US 20180302889A1 · Guo et al. · 2018 [cited by applicant]
US 20190274098A1 · Cheng et al. · 2019 [cited by applicant]
US 20200169340A1 · Hwang · 2020 [cited by examiner]
US 20200374960A1 · Deenoo et al. · 2020 [cited by applicant]
US 20210021320A1 · Koskela · 2021 [cited by examiner]
US 20210058129A1 · Takeda · 2021 [cited by examiner]
US 20210058133A1 · Takeda · 2021 [cited by examiner]
US 20210234752A1 · Matsumura · 2021 [cited by examiner]
US 20210344405A1 · Yuan · 2021 [cited by examiner]
US 20220006690A1 · Matsumura · 2022 [cited by examiner]
US 20220061087A1 · Koskela · 2022 [cited by examiner]
WO WO2019119399A1 · 2019 [cited by examiner]
R2-1810008 3GPP TSG RAN WG2 AH-1807, Montreal, Canada, Jul. 2-6, 2018, Source: Sharp, Title: Remaining issues on DL BWP switching upon RACH procedure initiation. [cited by applicant]
R2-1810091 3GPP TSG RAN WG2 AH-1807, Montreal, Canada, Jul. 2-6, 2018, Source: Huawei, HiSilicon, Title: BWP switch for BFR. [cited by applicant]
R2-1810513 3GPP TSG RAN WG2 AH-1807, Montreal, Canada, Jul. 2-6, 2018, Source: Huawei, HiSilicon, Title: Clarification on RA procedure for BFR on BWPs without CBRA occasions. [cited by applicant]
R2-1810641 3GPP TSG RAN WG2 AH-1807, Montreal, Canada, Jul. 2-6, 2018, Source: Huawei, HiSilicon, Title: Issues on BWP switch and search space configuration for BFR. [cited by applicant]
R2-1810643 3GPP TSG RAN WG2 AH-1807, Montreal, Canada, Jul. 2-6, 2018, Source: Huawei, HiSilicon, Title: RACH configuration on BWPs. [cited by applicant]
R2-1810797 3GPP TSG RAN WG2 AH-1807, Montreal, Canada, Jul. 2-6, 2018, Source: CATT, Title: Offline discussion #100 on DL-UL linking for CFRA. [cited by applicant]
R2-1811482 3GPP TSG-RAN WG2 Meeting #103, Gothenburg, Sweden, Aug. 20-24, 2018, Source: ZTE, Sanechips, Title: Consideration on implicit configuration of RS for BFD. [cited by applicant]
R2-1811896 3GPP TSG-RAN WG2 Meeting #103, Gothenburg, Sweden, Aug. 20-24, 2018, Source: Huawei, HiSilicon, Title: BWP switch for BFR. [cited by applicant]
R2-1812639 3GPP TSG-RAN WG2 Meeting #103, Gothenburg, Sweden, Aug. 20-24, 2018, Source: LG Electronics Inc., Title: BWP operation for BFR RA. [cited by applicant]
Aug. 16, 2021—European Office Action—19206560.5. [cited by applicant]
R2-1807584 3GPP TSG-RAN WG2 #102, Busan, Korea, May 21-25, 2018, Source: vivo, Title: Discussion on the SCell BFR. [cited by applicant]
Feb. 12, 2020—European Extended Search Report—EP 19206560.5. [cited by applicant]
R1-1807796 3GPP TSG-RAN WG1 #93, Busan, Korea, May 21-25, 2018, Source: MediaTek Inc., Title: Summary 2 on Remaining issues on Beam Failure Recovery. [cited by applicant]
R2-1806822 3GPP TSG-RAN WG2 #102, Busan, Korea, May 21-25, 2018, Source: InterDigital Inc., Title: Corrections on BFR for SCell. [cited by applicant]
R2-1806831 3GPP TSG-RAN WG2 #102, Busan, Korea, May 21-25, 2018, Source: Samsung Electronics, Title: CSI RS Beam Reporting during CB BFR. [cited by applicant]
R1-1811472 3GPP TSG-RAN WG1 Meeting #94bis, Chengdu, PR China, Oct. 8-12, 2018, Source: ASUS TeK, Title: Discussion on enhancements on multi-beam operation. [cited by applicant]
R1-1811526 3GPP TSG-RAN WG1 Meeting #94bis, Chengdu, PR China, Oct. 8-12, 2018, Source: CEWiT, Title: On fast SRS precoder updation. [cited by applicant]
R1-1811635 3GPP TSG-RAN WG1 Meeting #94bis, Chengdu, PR China, Oct. 8-12, 2018, Source: OPPO, Title: Discussion on Multi-beam Operation Enhancements. [cited by applicant]
R2-1800049 3GPP TSG-RAN WG2 Meeting #AH-1801, Vancouver, Canada, Jan. 22-26, 2018, Source: ASUS Tek, Title: UE behaviours upon beam failure and recovery. [cited by applicant]
R2-1800632 3GPP TSG-RAN WG2 Meeting #AH-1801, Vancouver, Canada, Jan. 22-26, 2018, Source: Huawei, HiSilicon, Title: Remaining issue for beam failure recovery. [cited by applicant]
R2-1800895 3GPP TSG-RAN WG2 Meeting #AH-1801, Vancouver, Canada, Jan. 22-26, 2018, Source: vivo, Title: Discussion on the impact of beam failure recovery. [cited by applicant]
R2-1801009 3GPP TSG-RAN WG2 Meeting #AH-1801, Vancouver, Canada, Jan. 22-26, 2018, Source: Huawei, HiSilicon, Title: General consideration on RA procedure for beam failure recovery. [cited by applicant]
R2-1801049 3GPP TSG-RAN WG2 Meeting #AH-1801, Vancouver, Canada, Jan. 22-26, 2018, Source: Huawei, HiSilicon, Title: Non-contention based random access for beam failrue recovery in CA. [cited by applicant]
R2-1801814 3GPP TSG-RAN WG2 #101, Athens, Greece, Feb. 26-Mar. 2, 2018, Source: Huawei, HiSilicon, Title: Beam failure recovery for SCell. [cited by applicant]
R2-1801926 3GPP TSG-RAN WG2 #101, Athens, Greece, Feb. 26-Mar. 2, 2018, Source: ZTE, Sanechips, Title: Remaining considerations on RACH procedure for BFR. [cited by applicant]
R2-1802143 3GPP TSG-RAN WG2 #101, Athens, Greece, Feb. 26-Mar. 2, 2018, Source: CATT, Title: RACH reattempt considering beam selection. [cited by applicant]
R2-1802151 3GPP TSG-RAN WG2 #101, Athens, Greece, Feb. 26-Mar. 2, 2018, Source: CATT, Title: Beam failure recovery. [cited by applicant]
R2-1802490 3GPP TSG-RAN WG2 #101, Athens, Greece, Feb. 26-Mar. 2, 2018, Source: CATT, Huawei, HiSilicon, Title: Discussion on Beam Failure Recovery for CA. [cited by applicant]
R2-1803045 3GPP TSG-RAN WG2 #101, Athens, Greece, Feb. 26-Mar. 2, 2018, Source: Sharp, Title: Identification of Contention based random access for beam failure recovery. [cited by applicant]
R2-1803198 3GPP TSG-RAN WG2 #101, Athens, Greece, Feb. 26-Mar. 2, 2018, Source: Ericsson, Title: Contention based random access for beam failure recovery (revision of R2-1800340). [cited by applicant]
R2-1803229 3GPP TSG-RAN WG2 #101, Athens, Greece, Feb. 26-Mar. 2, 2018, Source: Nokia, Nokia Shanghail Bell, Title: BWP switch interaction with contention free BFR preamble (revision of R2-1800961). [cited by applicant]
R2-1804279 3GPP TSG-RAN WG2 Meeting #101, Sanya, China, Apr. 16-20, 2018, Source: ASUSTek, Title: UE behaviours upon beam failure and recovery. [cited by applicant]
R2-1804303 3GPP TSG-RAN WG2 Meeting #101, Sanya, China, Apr. 16-20, 2018, Source: Samsung, Title: MAC Impacts: Beam Failure Recovery for SCell. [cited by applicant]
R2-1804304 3GPP TSG-RAN WG2 Meeting #101, Sanya, China, Apr. 16-20, 2018, Source: Samsung, Title: Contention Based BFR Procedure: Reporting Candidate Beam. [cited by applicant]
R2-1804407 3GPP TSG-RAN WG2 Meeting #101, Sanya, China, Apr. 16-20, 2018, Source: ZTE, Sanechips, Title: Consideration on beam failure recovery for SCell. [cited by applicant]
R2-1804410 3GPP TSG-RAN WG2 Meeting #101, Sanya, China, Apr. 16-20, 2018, Source: Huawei, HiSilicon, Title: Beam failure recovery using MAC CE. [cited by applicant]
R2-1804411 3GPP TSG-RAN WG2 Meeting #101, Sanya, China, Apr. 16-20, 2018, Source: Huawei, HiSilicon, Title: BWP issues for BFR. [cited by applicant]
R2-1804434 3GPP TSG-RAN WG2 Meeting #101, Sanya, China, Apr. 16-20, 2018, Source: OPPO, Title: Issues on supporting SCell BFR RACH. [cited by applicant]
R2-1804481 3GPP TSG-RAN WG2 Meeting #101, Sanya, China, Apr. 16-20, 2018, Source: CATT, Title: Leftover issues for BFR. [cited by applicant]
R2-1804482 3GPP TSG-RAN WG2 Meeting #101, Sanya, China, Apr. 16-20, 2018, Source: CATT, Title: BFR configurations and fallback options. [cited by applicant]
R2-1804483 3GPP TSG-RAN WG2 Meeting #101, Sanya, China, Apr. 16-20, 2018, Source: CATT, Title: BFR on SCell. [cited by applicant]
R2-1804696 3GPP TSG-RAN WG2 Meeting #101, Sanya, China, Apr. 16-20, 2018, Source: vivo, Title: Discussion on the SCell BFR. [cited by applicant]
R2-1805005 3GPP TSG-RAN WG2 Meeting #101, Sanya, China, Apr. 16-20, 2018, Source: Intel Corporation, Title: On beam failure detection and recovery using random access. [cited by applicant]
R2-1805342 3GPP TSG-RAN WG2 Meeting #101, Sanya, China, Apr. 16-20, 2018, Source: Nokia, Nokia Shanghai Bell, Title: SCell Beam Failure Recovery. [cited by applicant]
R2-1805414 3GPP TSG-RAN WG2 Meeting #101, Sanya, China, Apr. 16-20, 2018, Source: Ericsson, Title: Beam Failure Recovery in SCell and contention-based BFR on SpCell. [cited by applicant]
R2-1805896 3GPP TSG-RAN WG2 Meeting #101, Sanya, China, Apr. 16-20, 2018, Source: Huawei, HiSilicon, Title: ASN.1 for Beam Failure Recovery. [cited by applicant]
R2-1805905 3GPP TSG-RAN WG2 Meeting #101, Sanya, China, Apr. 16-20, 2018, Source: Huawei, HiSilicon, Title: Discussions on RA for SCells BFR. [cited by applicant]
R2-1806120 3GPP TSG-RAN WG2 Meeting #101, Sanya, China, Apr. 16-20, 2018, Source: ITL, Title: Beam Failure Recovery on SCell. [cited by applicant]
R2-1806166 3GPP TSG-RAN WG2 Meeting #101, Sanya, China, Apr. 16-20, 2018, Source: MediaTek, Inc., Title: On switching between CFRA and CBRA. [cited by applicant]
R2-1806819 3GPP TSG-RAN WG2 Meeting #102, Busan, Korea, May 21-25, 2018, Source: Samsung, Title: MAC Impacts: Beam Failure Recovery for SCell. [cited by applicant]
R2-1806821 3GPP TSG-RAN WG2 Meeting #102, Busan, Korea, May 21-25, 2018, Source: InterDigital, Inc., Title: BFR on SCell. [cited by applicant]
R2-1806824 3GPP TSG-RAN WG2 Meeting #102, Busan, Korea, May 21-25, 2018, Source: Samsung, Title: Contention Based BFR Procedure: Reporting Candidate Beam. [cited by applicant]
R2-1807405 3GPP TSG-RAN WG2 Meeting #102, Busan, Korea, May 21-25, 2018, Source: ZTE, Title: Discussion on the beam failure recovery timer. [cited by applicant]
R2-1807415 3GPP TSG-RAN WG2 Meeting #102, Busan, Korea, May 21-25, 2018, Source: OPPO, Title: MAC impacts on supporting BFR procedure on SCell. [cited by applicant]
R2-1807444 3GPP TSG-RAN WG2 Meeting #102, Busan, Korea, May 21-25, 2018, Source: Huawei, HiSilicon, Title: BWP switch for BFR. [cited by applicant]
R2-1807961 3GPP TSG RAN WG2 Meeting #102, Busan, Korea, May 21-25, 2018, Source: Huawei, HiSilicon, Title: Discussion on BFR-config for SCell BFR. [cited by applicant]
R2-1807975 3GPP TSG RAN WG2 Meeting #102, Busan, Korea, May 21-25, 2018, Source: Huawei, HiSilicon, Title: Discussion on beam failure recovery for SCell. [cited by applicant]
R2-1808024 3GPP TSG RAN WG2 Meeting #102, Busan, Korea, May 21-25, 2018, Source: Nokia, Nokia Shanghai Bell, Title: SCell Beam Failure Recovery. [cited by applicant]
R2-1808658 3GPP TSG RAN WG2 Meeting #102, Busan, Korea, May 21-25, 2018, Source: ITL, Title: Beam failure recovery on SCell. [cited by applicant]
R2-1809515 3GPP TSG RAN WG2 AH-1807, Montreal, Canada, Jul. 2-6, 2018, Source: CATT, Title: Further issues with DL BWP switching for CFRA. [cited by applicant]
R2-1809523 3GPP TSG RAN WG2 AH-1807, Montreal, Canada, Jul. 2-6, 2018, Source: CATT, Title: Further discussion on BFR termination criterion. [cited by applicant]
R2-1809721 3GPP TSG RAN WG2 AH-1807, Montreal, Canada, Jul. 2-6, 2018, Source: InterDigital, Title: BWP switching for RA-BFR. [cited by applicant]
R2-1809872 3GPP TSG RAN WG2 AH-1807, Montreal, Canada, Jul. 2-6, 2018, Source: vivo, Title: Remaining configuration issues for BFR. [cited by applicant]
R2-1809894 3GPP TSG RAN WG2 AH-1807, Montreal, Canada, Jul. 2-6, 2018, Source: vivo, Title: Preamble Selection when CFRA Resource Available. [cited by applicant]
R2-1809925 3GPP TSG RAN WG2 AH-1807, Montreal, Canada, Jul. 2-6, 2018, Source: OPPO, Title: The issue of BWP switching for BFR RACH. [cited by applicant]
R2-1811483 3GPP TSG-RAN WG2 Meeting #103, Gothenburg, Sweden, Aug. 20-24, 2018, Source: ZTE, Sanechips, Title: CR for the reset of BFD in 38.321. [cited by applicant]
R2-1812108 3GPP TSG-RAN WG2 Meeting #103, Gothenburg, Sweden, Aug. 20-24, 2018, Source: Nokia, Nokia Shanghai Bell, Title: Reset of BFD. [cited by applicant]
3GPP TS 38.213 V15.2.0 (Jun. 2018), Technical Specification, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Physical layer procedures for control (Release 15). [cited by applicant]
R2-1806229 3GPP TSG-RAN WG2 Meeting #101bis, Sanya, China, Apr. 16-20, 2018, Source: Samsung, Title: Miscellaneous corrections. [cited by applicant]
R2-1811325 3GPP TSG-RAN WG2 Meeting #103, Gothenburg, Sweden, Aug. 20-24, 2018, Source: Samsung Electronics, Title: Handling Beam Failure Recovery Configuration Update. [cited by applicant]
3GPP TS 38.321 V15.2.0 (Jun. 2018), Technical Specification, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Medium Access Control (MAC) protocol specification (Release 15). [cited by applicant]
R2-1811149 3GPP TSG-RAN WG2 Meeting #103, Gothenburg, Sweden, Aug. 20-24, 2018, Source: OPPO, Title: CR on beam failure recovery configuration. [cited by applicant]
R2-1811593 3GPP TSG-RAN WG2 Meeting #103, Gothenburg, Sweden, Aug. 20-24, 2018, Source: ZTE Corporation, Sanechips, Title: CR for the configuration of BeamFailureRecoveryConfig. [cited by applicant]
3GPP TS 38.331 V15.2.1 (Jun. 2018), Technical Specification, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Radio Resource Control (RRC) protocol specification (Release 15). [cited by applicant]
R1-180XXXX 3GPP TSG-RAN WG1 Meeting #94, Gothenburg, Sweden, Aug. 20-24, 2018, Source: Ericsson, Title: Feature lead summary beam management v2. [cited by applicant]
R1-180XXXX 3GPP TSG-RAN WG1 Meeting #94, Gothenburg, Sweden, Aug. 20-24, 2018, Source: NTT DOCOMO, Inc., Title: Offline summary for PDCCH structure and search space. [cited by applicant]
R1-180XXXX 3GPP TSG-RAN WG1 Meeting #94, Gothenburg, Sweden, Aug. 20-24, 2018, Source: MediaTek Inc., Title: Summary #1 on Remaining Issues on Beam Failure Recovery. [cited by applicant]
R1-1801722 3GPP TSG RAN WG1 Meeting #92, Athens, Greece, Feb. 26-Mar. 2, 2018, Source: CATT, Title: Remaining issues on DL beam failure recovery. [cited by applicant]
R1-1802824 3GPP TSG RAN WG1 Meeting #92, Athens, Greece, Feb. 26-Mar. 2, 2018, Source: Qualcomm Incorporated, Title: Beam recovery procedures. [cited by applicant]
R1-1803622 3GPP TSG RAN WG1 Meeting #92, Sanya, China, Apr. 16-20, 2018, Source: NEC, Title: Remaining issues on beam failure recovery. [cited by applicant]
R1-1804211 3GPP TSG-RAN WG1 Meeting #92bis, Sanya, China, Apr. 16-20, 2018, Source: Lenovo, Motorola Mobility, Title: Discussion of beam failure recovery for Carrier Aggregation. [cited by applicant]
R1-1806281 3GPP TSG-RAN WG1 #93, Busan, Korea, May 21-25, 2018, Source: CATT, Title: Remaining issues on beam failure recovery. [cited by applicant]
R1-1806789 3GPP TSG-RAN WG1 #93, Busan, Korea, May 21-25, 2018, Source: MediaTek Inc., Title: Remaining issues on beam failure recovery. [cited by applicant]
R1-1808720 3GPP TSG-RAN WG1 Meeting #94, Gothenburg, Sweden, Aug. 20-24, 2018, Source: Intel Corporation, Title: On SCell Beam Failure Recovery. [cited by applicant]
R1-1810020 3GPP TSG-RAN WG1 Meeting #94, Gothenburg, Sweden, Aug. 20-24, 2018, Source: Samsung, Title: CR to 38.213 capturing the RAN1#94 meeting agreements. [cited by applicant]
R1-1810105 3GPP TSG-RAN WG1 Meeting #94bis, Chengdu, PR China, Oct. 8-12, 2018, Source: Huawei, HiSilicon, Title: Beam management enhancements for latency and overhead reduction. [cited by applicant]
R1-1810106 3GPP TSG-RAN WG1 Meeting #94bis, Chengdu, PR China, Oct. 8-12, 2018, Source: Huawei, HiSilicon, Title: Beam failure recovery for SCell. [cited by applicant]
R1-1810221 3GPP TSG-RAN WG1 Meeting #94bis, Chengdu, PR China, Oct. 8-12, 2018, Source: ZTE, Title: Enhancements on multi-beam operation. [cited by applicant]
R1-1810303 3GPP TSG-RAN WG1 Meeting #94bis, Chengdu, PR China, Oct. 8-12, 2018, Source: LG Electronics, Title: Discussion on multi-beam based operations and enhancements. [cited by applicant]
R1-1810403 3GPP TSG-RAN WG1 Meeting #94bis, Chengdu, PR China, Oct. 8-12, 2018, Source: vivo, Title: Discussion on Enhancements on Multi-Beam Operation. [cited by applicant]
R1-1810408 3GPP TSG-RAN WG1 Meeting #94bis, Chengdu, PR China, Oct. 8-12, 2018, Source: vivo, Title: Discussion on beam measurement and reporting. [cited by applicant]
R1-1810409 3GPP TSG-RAN WG1 Meeting #94bis, Chengdu, PR China, Oct. 8-12, 2018, Source: vivo, Title: Discussion on SCell BFR. [cited by applicant]
R1-1810410 3GPP TSG-RAN WG1 Meeting #94bis, Chengdu, PR China, Oct. 8-12, 2018, Source: vivo, Title: Discussion on UL multi-beam transmission. [cited by applicant]
R1-1810411 3GPP TSG-RAN WG1 Meeting #94bis, Chengdu, PR China, Oct. 8-12, 2018, Source: vivo, Title: Discussion on beam management latency and overhead reduction. [cited by applicant]
R1-1810435 3GPP TSG-RAN WG1 Meeting #94bis, Chengdu, PR China, Oct. 8-12, 2018, Source: MediaTek Inc., Title: Enhancements on multi-beam operation. [cited by applicant]
R1-1810556 3GPP TSG-RAN WG1 Meeting #94bis, Chengdu, PR China, Oct. 8-12, 2018, Source: CATT, Title: Consideration on multi-beam operation enhancements. [cited by applicant]
R1-1810572 3GPP TSG-RAN WG1 Meeting #94bis, Chengdu, PR China, Oct. 8-12, 2018, Source: Lenovo, Motorola Mobility, Title: Discussion of enhancements for multi-beam operation. [cited by applicant]
R1-1810598 3GPP TSG-RAN WG1 Meeting #94bis, Chengdu, PR China, Oct. 8-12, 2018, Source: Fujitsu, Title: Discussion on beam failure recovery for SCell. [cited by applicant]
R1-1810644 3GPP TSG-RAN WG1 Meeting #94bis, Chengdu, PR China, Oct. 8-12, 2018, Source: Sony, Title: Considerations on multi-beam operation. [cited by applicant]
R1-1810688 3GPP TSG-RAN WG1 Meeting #94bis, Chengdu, PR China, Oct. 8-12, 2018, Source: AT&T, Title: Enhancements on Multi-Beam Operation for NR. [cited by applicant]
R1-1810791 3GPP TSG-RAN WG1 Meeting #94bis, Chengdu, PR China, Oct. 8-12, 2018, Source: Intel Corporation, Title: On Beam Management Enhancement. [cited by applicant]
R1-1810805 3GPP TSG-RAN WG1 Meeting #94bis, Chengdu, PR China, Oct. 8-12, 2018, Source: NEC, Title: Discussion on Beam Failure Recovery. [cited by applicant]
R1-1810886 3GPP TSG-RAN WG1 Meeting #94bis, Chengdu, PR China, Oct. 8-12, 2018, Source: Samsung, Title: Enhancements on multi-beam operations. [cited by applicant]
R1-1810970 3GPP TSG-RAN WG1 Meeting #94bis, Chengdu, PR China, Oct. 8-12, 2018, Source: OPPO, Title: Discussion on Multi-beam Operation Enhancements. [cited by applicant]
R1-1811002 3GPP TSG-RAN WG1 Meeting #94bis, Chengdu, PR China, Oct. 8-12, 2018, Source: Spreadtrum Communications, Title: Discussion on multi-beam operation. [cited by applicant]
R1-1811086 3GPP TSG-RAN WG1 Meeting #94bis, Chengdu, PR China, Oct. 8-12, 2018, Source: Fraunhofer IIS, Fraunhofer HHI, Title: Discussion on signaling of beam correspondence. [cited by applicant]
R1-1811188 3GPP TSG-RAN WG1 Meeting #94bis, Chengdu, PR China, Oct. 8-12, 2018, Source: Ericsson, Title: Enhancements on Multi-beam Operation. [cited by applicant]
R1-1811189 3GPP TSG-RAN WG1 Meeting #94bis, Chengdu, PR China, Oct. 8-12, 2018, Source: Ericsson, Title: Link recovery on SCell. [cited by applicant]
R1-1811223 3GPP TSG-RAN WG1 Meeting #94bis, Chengdu, PR China, Oct. 8-12, 2018, Source: InterDigital Inc., Title: Discussion on Multi-Beam Operation Enhancements. [cited by applicant]
R1-1811278 3GPP TSG-RAN WG1 Meeting #94bis, Chengdu, PR China, Oct. 8-12, 2018, Source: Qualcomm Incorporated, Title: Enhancements on Multi-beam Operation. [cited by applicant]
R1-1811349 3GPP TSG-RAN WG1 Meeting #94bis, Chengdu, PR China, Oct. 8-12, 2018, Source: NTT DOCOMO, Inc., Title: Discussion on multi-beam enhancement. [cited by applicant]
R1-1811393 3GPP TSG-RAN WG1 Meeting #94bis, Chengdu, PR China, Oct. 8-12, 2018, Source: Xiaomi, Title: Enhancements on beam management. [cited by applicant]
R1-1811408 3GPP TSG-RAN WG1 Meeting #94bis, Chengdu, PR China, Oct. 8-12, 2018, Source: Nokia, Nokia Shanghai Bell, Title: Enhancements on Multi-beam Operation. [cited by applicant]
R1-1811470 3GPP TSG-RAN WG1 Meeting #94bis, Chengdu, PR China, Oct. 8-12, 2018, Source: Huawei, HiSilicon, Title: Enhancements on multi-beam operation. [cited by applicant]