IP Library › Granted Patent US 12,199,728
Granted Patent B2
US 12,199,728 · App. 18/440,612 · Granted Jan 14, 2025

Resource management for beam failure recovery procedures

Inventors: Ali Cagatay Cirik (Chantilly, VA); Esmael Hejazi Dinan (McLean, VA); Hua Zhou (Vienna, VA); Hyoungsuk Jeon (Centreville, VA); Alireza Babaei (Fairfax, VA); Kyungmin Park (Vienna, VA)
Assignee: Comcast Cable Communications, LLC
H04B7/0695H04L1/0026H04L5/0051H04L5/0094H04W74/0833H04W80/02
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,199,728
App. No.
18/440,612
Granted
Jan 14, 2025
Kind
B2
Abstract

Wireless communications are described. A wireless device and/or a base station may provide improved resource management. A base station may configure and/or transmit a beam failure recovery medium access control control element (BFR MAC CE) to a wireless device to activate one or more beam failure reference signal resources for beam failure of a downlink bandwidth part (BWP) of a cell. The wireless device may assess, based on receiving the BFR MAC CE, a radio link quality of one or more reference signals for beam failure detection of the downlink BWP of the cell.

Claims (48)

1. A method comprising:

receiving, by a wireless device, a first beam failure medium access control (MAC) control element (CE) that comprises a field indicating one or more first beam failure reference signal resources, wherein the first beam failure MAC CE is configured to activate the one or more first beam failure reference signal resources for beam failure of a downlink bandwidth part (BWP) of a cell;

based on receiving the first beam failure MAC CE, assessing a radio link quality of one or more reference signals for beam failure detection of the downlink BWP of the cell;

incrementing a beam failure instance counter for the cell;

receiving a second beam failure MAC CE that comprises a field indicating one or more second beam failure reference signal resources, wherein the second beam failure MAC CE is configured to activate the one or more second beam failure reference signal resources for beam failure of the downlink BWP of the cell; and

based on the receiving the second beam failure MAC CE, setting the beam failure instance counter to zero.

2. The method of claim 1 , wherein the first beam failure MAC CE comprises:

a second field indicating the cell; and

a third field indicating the BWP of the cell.

3. The method of claim 1 , wherein the incrementing comprises incrementing, based on a value of the radio link quality not satisfying a threshold, the beam failure instance counter.

4. The method of claim 1 , further comprising:

transmitting, for beam failure of the downlink BWP of the cell and based on the beam failure instance counter satisfying a threshold, an uplink signal.

5. The method of claim 1 , further comprising:

measuring one or more second reference signals in the one or more second beam failure reference signal resources for beam failure of the downlink BWP of the cell.

6. The method of claim 1 , wherein the first beam failure MAC CE comprises a beam failure recovery MAC CE (BFR MAC CE).

7. The method of claim 1 , wherein the second beam failure MAC CE indicates deactivation of the one or more first beam failure reference signal resources.

8. A method comprising:

receiving, by a wireless device, a beam failure medium access control (MAC) control element (CE) comprising:

a first field indicating a cell;

a second field indicating a downlink bandwidth part (BWP) of the cell; and

a third field indicating one or more beam failure reference signal resources, associated with one or more reference signals, for beam failure of the downlink BWP of the cell,

wherein the beam failure MAC CE is configured to activate the one or more beam failure reference signal resources; and

based on receiving the beam failure MAC CE, assessing a radio link quality of the one or more reference signals.

9. The method of claim 8 , further comprising:

incrementing, based on a value of a radio link quality not satisfying a threshold, a beam failure instance counter.

10. The method of claim 9 , further comprising:

transmitting, for beam failure of the downlink BWP of the cell and based on the beam failure instance counter satisfying a threshold, an uplink signal.

11. The method of claim 10 , wherein the uplink signal indicates a second reference signal of the one or more beam failure reference signal resources.

12. The method of claim 8 , further comprising:

measuring one or more second reference signals of the one or more beam failure reference signal resources for beam failure of the downlink BWP of the cell.

13. The method of claim 8 , wherein the beam failure MAC CE comprises a beam failure recovery MAC CE (BFR MAC CE).

14. A method comprising:

incrementing, by a wireless device, a beam failure instance counter based on a beam failure instance indication of a cell;

receiving a beam failure medium access control (MAC) control element (CE) comprising:

a first field indicating the cell;

a second field indicating a downlink bandwidth part (BWP) of the cell; and

a third field indicating one or more beam failure reference signal resources for beam failure of the downlink BWP of the cell,

wherein the beam failure MAC CE is configured to activate the one or more beam failure reference signal resources; and

based on the receiving the beam failure MAC CE, setting the beam failure instance counter to zero.

15. The method of claim 14 , further comprising:

determining, based on the beam failure instance counter satisfying a threshold, beam failure of the downlink BWP of the cell.

16. The method of claim 14 , further comprising:

measuring one or more reference signals, of the one or more beam failure reference signal resources, for beam failure of the downlink BWP of the cell.

17. The method of claim 16 , further comprising:

transmitting, for beam failure of the downlink BWP of the cell, an uplink signal indicating a reference signal of the one or more reference signals.

18. The method of claim 14 , wherein a physical layer of the wireless device indicates a beam failure instance indication to a medium access layer of the wireless device based on a radio link quality, of one or more reference signals used for beam failure, not satisfying than a threshold.

19. The method of claim 14 , wherein the beam failure MAC CE comprises a fourth field, wherein the fourth field comprises a value indicating activation of the one or more beam failure reference signal resources.

20. The method of claim 14 , wherein the beam failure MAC CE indicates deactivation of one or more second beam failure reference signal resources.

Assignments (2)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 9, 2024
From: CIRIK, ALI CAGATAY; DINAN, ESMAEL HEJAZI; ZHOU, HUA; JEON, HYOUNGSUK; BABAEI, ALIREZA; PARK, KYUNGMIN
To: COMCAST CABLE COMMUNICATIONS, LLC
Reel/Frame 068525/0044 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 9, 2024
From: CIRIK, ALI CAGATAY; DINAN, ESMAEL HEJAZI; ZHOU, HUA; JEON, HYOUNGSUK; BABAEI, ALIREZA; PARK, KYUNGMIN
To: COMCAST CABLE COMMUNICATIONS, LLC
Reel/Frame 068525/0322 →
Continuity (4)
Continuation 17231862 · Apr 15, 2021
Continuation 16537027 · Aug 9, 2019
Provisional Application 62716817 · Aug 9, 2018
Related Publication 20240187073A1 · Jun 6, 2024
References Cited (400)
US 9125218B2 · Chang · 2015 [cited by applicant]
US 9736795B2 · Dinan · 2017 [cited by applicant]
US 9949298B1 · Akoum et al. · 2018 [cited by applicant]
US 11026109B2 · Wei · 2021 [cited by examiner]
US 20100279700A1 · Kim et al. · 2010 [cited by applicant]
US 20120300715A1 · Pelletier et al. · 2012 [cited by applicant]
US 20130039345A1 · Kim et al. · 2013 [cited by applicant]
US 20130188580A1 · Dinan · 2013 [cited by applicant]
US 20130250828A1 · Chou et al. · 2013 [cited by applicant]
US 20150189574A1 · Ng et al. · 2015 [cited by applicant]
US 20150208462A1 · Lee et al. · 2015 [cited by applicant]
US 20150365921A1 · Wu · 2015 [cited by applicant]
US 20170195998A1 · Zhang et al. · 2017 [cited by applicant]
US 20170207843A1 · Jung et al. · 2017 [cited by applicant]
US 20170332406A1 · Islam et al. · 2017 [cited by applicant]
US 20170339662A1 · Lin et al. · 2017 [cited by applicant]
US 20170373731A1 · Guo et al. · 2017 [cited by applicant]
US 20180006770A1 · Guo et al. · 2018 [cited by applicant]
US 20180054348A1 · Luo et al. · 2018 [cited by applicant]
US 20180054382A1 · Luo et al. · 2018 [cited by applicant]
US 20180054783A1 · Luo et al. · 2018 [cited by applicant]
US 20180054811A1 · Luo et al. · 2018 [cited by applicant]
US 20180054812A1 · Luo et al. · 2018 [cited by applicant]
US 20180054832A1 · Luo et al. · 2018 [cited by applicant]
US 20180083753A1 · Nagaraja et al. · 2018 [cited by applicant]
US 20180098334A1 · Tie et al. · 2018 [cited by applicant]
US 20180110066A1 · Luo et al. · 2018 [cited by applicant]
US 20180115940A1 · Abedini et al. · 2018 [cited by applicant]
US 20180115990A1 · Abedini et al. · 2018 [cited by applicant]
US 20180124687A1 · Park et al. · 2018 [cited by applicant]
US 20180132266A1 · Chen et al. · 2018 [cited by applicant]
US 20180138962A1 · Islam et al. · 2018 [cited by applicant]
US 20180176958A1 · Islam et al. · 2018 [cited by applicant]
US 20180191422A1 · Xia et al. · 2018 [cited by applicant]
US 20180219604A1 · Lu et al. · 2018 [cited by applicant]
US 20180220448A1 · Akkarakaran et al. · 2018 [cited by applicant]
US 20180227899A1 · Yu et al. · 2018 [cited by applicant]
US 20180234960A1 · Nagaraja et al. · 2018 [cited by applicant]
US 20180241452A1 · Akkarakaran et al. · 2018 [cited by applicant]
US 20180249453A1 · Nagaraja et al. · 2018 [cited by applicant]
US 20180270698A1 · Babaei et al. · 2018 [cited by applicant]
US 20180270699A1 · Babaei et al. · 2018 [cited by applicant]
US 20180270700A1 · Babaei et al. · 2018 [cited by applicant]
US 20180278310A1 · Lee et al. · 2018 [cited by applicant]
US 20180279150A1 · He et al. · 2018 [cited by applicant]
US 20180279193A1 · Park et al. · 2018 [cited by applicant]
US 20180279218A1 · Park et al. · 2018 [cited by applicant]
US 20180279229A1 · Dinan et al. · 2018 [cited by applicant]
US 20180288756A1 · Xia et al. · 2018 [cited by applicant]
US 20180302889A1 · Guo et al. · 2018 [cited by applicant]
US 20180310321A1 · Basu Mallick et al. · 2018 [cited by applicant]
US 20180317123A1 · Chen et al. · 2018 [cited by applicant]
US 20180323856A1 · Xiong et al. · 2018 [cited by applicant]
US 20180324723A1 · Akkarakaran et al. · 2018 [cited by applicant]
US 20180324867A1 · Basu Mallick et al. · 2018 [cited by applicant]
US 20180343653A1 · Guo · 2018 [cited by applicant]
US 20180351611A1 · Nagaraja et al. · 2018 [cited by applicant]
US 20180367374A1 · Liu et al. · 2018 [cited by applicant]
US 20180368126A1 · Islam et al. · 2018 [cited by applicant]
US 20180368142A1 · Liou · 2018 [cited by applicant]
US 20190028174A1 · Chakraborty et al. · 2019 [cited by applicant]
US 20190037423A1 · Yu et al. · 2019 [cited by applicant]
US 20190037498A1 · Tseng et al. · 2019 [cited by applicant]
US 20190037604A1 · Akkarakaran et al. · 2019 [cited by applicant]
US 20190059129A1 · Luo et al. · 2019 [cited by applicant]
US 20190074882A1 · Zhou et al. · 2019 [cited by applicant]
US 20190074891A1 · Kwon et al. · 2019 [cited by applicant]
US 20190098655A1 · Shih · 2019 [cited by examiner]
US 20190173740A1 · Zhang et al. · 2019 [cited by applicant]
US 20190268893A1 · Tsai et al. · 2019 [cited by applicant]
US 20200169310A1 · Kwon et al. · 2020 [cited by applicant]
US 20200403761A1 · Nguyen · 2020 [cited by applicant]
US 20210058998A1 · Yuan et al. · 2021 [cited by applicant]
CN 108809580A · 2018 [cited by applicant]
EP 3397015A1 · 2018 [cited by applicant]
EP 3424152A1 · 2019 [cited by applicant]
WO 2013025142A1 · 2013 [cited by applicant]
WO 2017151876A1 · 2017 [cited by applicant]
WO 2017196612A1 · 2017 [cited by applicant]
WO 2017217898A1 · 2017 [cited by applicant]
WO 2018017840A1 · 2018 [cited by applicant]
WO 2018031327A1 · 2018 [cited by applicant]
WO 2018031799A1 · 2018 [cited by applicant]
WO 2018038859A1 · 2018 [cited by applicant]
WO 2018038860A1 · 2018 [cited by applicant]
WO 2018038861A1 · 2018 [cited by applicant]
WO 2018038862A1 · 2018 [cited by applicant]
WO 2018038864A1 · 2018 [cited by applicant]
WO 2018075985A1 · 2018 [cited by applicant]
WO 2018084544A1 · 2018 [cited by applicant]
WO 2018128426A1 · 2018 [cited by applicant]
WO 2018129300A1 · 2018 [cited by applicant]
WO 2018136300A1 · 2018 [cited by applicant]
WO 2018141303A1 · 2018 [cited by applicant]
WO 2018144592A1 · 2018 [cited by applicant]
WO 2018148552A1 · 2018 [cited by applicant]
WO 2018156299A1 · 2018 [cited by applicant]
WO 2018156696A1 · 2018 [cited by applicant]
WO 2018169848A1 · 2018 [cited by applicant]
WO 2018170481A1 · 2018 [cited by applicant]
WO 2018171476A1 · 2018 [cited by applicant]
WO 2018174667A1 · 2018 [cited by applicant]
WO 2018174800A1 · 2018 [cited by applicant]
WO 2018175303A1 · 2018 [cited by applicant]
WO 2018190617A1 · 2018 [cited by applicant]
WO 2018195975A1 · 2018 [cited by applicant]
WO 2018196520A1 · 2018 [cited by applicant]
WO 2018199074A1 · 2018 [cited by applicant]
WO 2018199079A1 · 2018 [cited by applicant]
WO 2018199100A1 · 2018 [cited by applicant]
WO 2018199162A1 · 2018 [cited by applicant]
WO 2018199243A1 · 2018 [cited by applicant]
WO 2018200579A1 · 2018 [cited by applicant]
WO 2018201450A1 · 2018 [cited by applicant]
WO 2018201990A1 · 2018 [cited by applicant]
WO 2018203719A1 · 2018 [cited by applicant]
WO 2018203785A1 · 2018 [cited by applicant]
WO 2018204255A1 · 2018 [cited by applicant]
WO 2018204718A1 · 2018 [cited by applicant]
WO 2018204922A1 · 2018 [cited by applicant]
WO 2018222276A1 · 2018 [cited by applicant]
WO 2018227464A1 · 2018 [cited by applicant]
WO 2018227551A1 · 2018 [cited by applicant]
WO 2018228187A1 · 2018 [cited by applicant]
WO 2018230862A1 · 2018 [cited by applicant]
WO 2018231655A1 · 2018 [cited by applicant]
WO 2018232090A1 · 2018 [cited by applicant]
WO 2018232259A1 · 2018 [cited by applicant]
WO 2018237400A1 · 2018 [cited by applicant]
WO 2019004694A1 · 2019 [cited by applicant]
WO 2019032882A1 · 2019 [cited by applicant]
R2-1815644 3GPP TSG-RAN WG2 Meeting #103bis, Chengdu, PR China, Oct. 8-12, 2018, Source: Ericsson, Samsung, Title: Correction for Reconfiguration of CFRA during ongoing RA. [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]
R2-1804763 3GPP TSG-RAN WG2 Meeting #101bis, Sanya, China, Apr. 16-20, 2018, Source: Nokia, Nokia Shanghai Bell, Title: Running MAC CR for euCA. [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-1712153 3GPP TSG RAN WG1 Meeting #90, Prague, Czech Republic, Aug. 21-25, 2017, Source: Huawei, HiSilicon, Title: Overview of bandwidth part. [cited by applicant]
R1-1713204 3GPP TSG RAN WG1 Meeting #90, Prague, Czech Republic, Aug. 21-25, 2017, Source: LG Electronics, Title: Further remaining details on wider bandwidth operation. [cited by applicant]
R1-1713978 3GPP TSG RAN WG1 Meeting #90, Prague, Czech Republic, Aug. 21-25, 2017, Source: MediaTek Inc., Title: Further Details on Bandwidth Part Operation in NR. [cited by applicant]
R1-1719650 3GPP TSG RAN WG1 Meeting #91, Reno, USA, Nov. 27-Dec. 1, 2017, Source: AT&T, Title: Remaining details on bandwidth parts. [cited by applicant]
R1-1719651 3GPP TSG RAN WG1 Meeting #91, Reno, USA, Nov. 27-Dec. 1, 2017, Source: AT&T, Title: Remaining details on carrier aggregation. [cited by applicant]
R1-1721027 3GPP TSG RAN WG1 Meeting #91, Reno, USA, Nov. 27-Dec. 1, 2017, Source: Ericsson, Title: On Carrier aggregation related aspects. [cited by applicant]
R1-1800879 3GPP TSG RAN WG1 NR Ad Hoc, Vancouver, Canada, Jan. 22-26, 2018, Source: Qualcomm Incorporated, Title: Remaining Issues on BWP. [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-1806508 3GPP TSG-RAN WG1 #93, Busan, Korea, May 21-25, 2018, Source: Intel Corporation, 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-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]
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]
R2-1713170 3GPP TSG RAN WG2 Meeting #100, Reno, USA, Nov. 27-Dec. 1, 2017, Source: Nokia (rapporteur), Title: Report of [99bis#32][LTE/euCA] Faster activation for Scells (Nokia). [cited by applicant]
R2-1714289 3GPP TSG RAN WG2 Meeting #100, Reno, USA, Nov. 27-Dec. 1, 2017, Source: Nokia, Nokia Shanghai Bell, Title: Running CR for euCA Stage-2. [cited by applicant]
R2-1800866 3GPP TSG-RAN WG2 AH, Vancouver, Canada, Jan. 22-26, 2018, Source: vivo, Title: RACH configuration for beam recovery. [cited by applicant]
R2-1800895 3GPP TSG-RAN WG2 AH, Vancouver, Canada, Jan. 22-26, 2018, Source: vivo, Title: Discussion on the impact on beam failure recovery. [cited by applicant]
R2-1801432 3GPP TSG RAN WG2 NR Ad Hoc, Vancouver, Canada, Jan. 22-26, 2018, Source: Qualcomm Incorporated, Title: Dormant BWP for fast SCell activation. [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-1802756 3GPP TSG RAN WG2 Meeting #101, Athens, Greece, Feb. 26-Mar. 2, 2018, Source: Nokia, Nokia Shanghai Bell, Title: Remaining details on temporary CQI reporting during activation. [cited by applicant]
R2-1803229 3GPP TSG-RAN WG2 #101, Athens, Greece, Feb. 26-Mar. 2, 2018, Source: Nokia, Nokia Shanghai Bell, Title: BWP switch interaction with contention free BFR preamble. [cited by applicant]
R2-1803564 3GPP TSG RAN WG2 Meeting #101, Athens, Greece, Feb. 26-Mar. 2, 2018, Source: Qualcomm Incorporated, Title: Dormant BWP for fast SCell activation. [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-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-1805204 3GPP TSG-RAN WG2 Meeting #101, Sanya, China, Apr. 16-20, 2018, Source: Lenovo, Motorola Mobility, Title: Dedicated PRACH resource for 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-1707001 3GPP TSG-RAN WG2 Meeting #AH, Qingdao, China, Jun. 27-29, 2017, Source: Lenovo, Motorola Mobility, Title: Random access procedure for beam recovery request. [cited by applicant]
R1-17111617 3GPP TSG RAN WG1 NR AH#2, Qingdao, China, Jun. 27-30, 2017, Source: CATT, Title: RACH power control and power ramping procedure (revision of R1-1710034). [cited by applicant]
R1-1711161 3GPP TSG RAN WG1 NR#2, Qingdao, China, Jun. 27-30, 2017, Source: Qualcomm Incorporated, Title: Beam recovery procedures. [cited by applicant]
International Search Report and Written Opinion for PCT/US2018/046368 mailing date Dec. 13, 2018. [cited by applicant]
Apr. 15, 2019—Extented European Search Report—EP 19150964.5. [cited by applicant]
R1-1708678 3GPP TSG-RAN WG1 #89, Hangzhou, China, May 15-19, 2017, Source: Ericsson, Title: Beam failure recovery mechanism. [cited by applicant]
May 22, 2019—Extended European Search Report—19156175.2. [cited by applicant]
R2-1800560 3GPP TSG-RAN WG2 NR, Vancouver, Canada, Jan. 22-26, 2018, Source: Sharp, Title: Remaining issues on beam failure recovery. [cited by applicant]
R2-1800632 3GPP TSG-RAN WG2 AH, Vancouver, Canada, Jan. 22-26, 2018, Source: Huawei, HiSilicon, Title: Remaining issue for beam failure recovery. [cited by applicant]
R2-1801049 3GPP TSG-RAN WG2 AH, Vancouver, Canada, Jan. 22-26, 2018, Source: Huawei, HiSilicon, Title: Non-contention based random access for beam failure recovery in CA. [cited by applicant]
3GPP TS 38.321 V15.0.0 (Dec. 2017); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Medium Access Control (MAC) protocol specification (Release 15). [cited by applicant]
3GPP TS 38.213 V15.0.1 (Feb. 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-1804475 3GPP TSG-RAN WG2 Meeting #101bis, Sanya, China, Apr. 16-20, 2018, Source: Spreadtrum Communications, Title: Beam Failure recovery on SCell. [cited by applicant]
May 14, 2019—European Extended Search Report—19157460.7. [cited by applicant]
R2-1710562 3GPP TSG-RAN WG2 #99bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: Huawei, HiSilicon, Title: RAN2 aspects of DL beam management (revision of R2-1708695). [cited by applicant]
3GPP TS 36.211 V14.3.0 (Jun. 2017); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels… [cited by applicant]
3GPP TS 36.213 V14.3.0 (Jun. 2017); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer pr… [cited by applicant]
3GPP TS 36.321 V.14.3.0 (Jun. 2017); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Co… [cited by applicant]
3GPP TS 36.331 V.14.3.0 (Jun. 2017); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource C… [cited by applicant]
3GPP TR 38.802 V14.1.0 (Jun. 2017), Technical Report, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Study on New Radio Access Technology Physical Layer Aspects (Release 14). [cited by applicant]
3GPP TR 38.912 V14.0.0 (Mar. 2017), Technical Report, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Study on New Radio (NR) Access Technology (Release 14). [cited by applicant]
R1-171xxxx 3GPP TSG RAN WG1 Meeting #90, Prague, Czech Republic, Aug. 21-25, 2017, Source: MCC Support, Title: Draft Report of 3GPP TSG RAN WG1 #89 v0.2.0 (Hangzhou, China, May 15-19, 2017). [cited by applicant]
R1-171xxxx 3GPP TSG RAN WG1 Meeting #90, Prague, Czech Republic, Aug. 21-25, 2017, Source: MCC Support, Title: Draft Report of 3GPP TSG RAN WG1 #AH NR2 v0. 1.0 (Qingdao, China, Jun. 27-30, 2017). [cited by applicant]
R1-1708890 3GPP TSG RAN WG1 Meeting #89, Hangzhou, China, May 15-19, 2017, Source: MCC Support, Title: Final Report of 3GPP TSG RAN WG1 #88bis v1.0.0 (Spokane, Washington, Apr. 3-7, 2017). [cited by applicant]
R1-1709907 3GPP TSG RAN WG1 NR Ad-Hoc#2, Qingdao, China, Jun. 27-30, 2017, Source: Xinwei, Title: Discussion on Beam Failure Recovery. [cited by applicant]
R1-1709929 3GPP TSG RAN WG1 NR Ad Hoc Meeting, Qingdao, China, Jun. 27-30, 2017, Source: Huawei, HiSilicon, Title: General views on beam failure recovery. [cited by applicant]
R1-1710058 3GPP TSG RAN WG1 NR Ad-Hoc#2, Qingdao, China, Jun. 27-30, 2017, Source: CATT, Title: Considerations on DL beam failure and recovery. [cited by applicant]
R1-1710283 3GPP TSG RAN WG1 NR Ad-Hoc#2, Qingdao, China, Jun. 27-30, 2017, Source: LG Electronics, Title: Discussion on beam failure recovery. [cited by applicant]
R1-1710400 3GPP TSG RAN WG1 NR Ad-Hoc#2, Qingdao, China, Jun. 27-30, 2017, Source: Vivo, Title: Beam failure recovery procedure. [cited by applicant]
R1-1710596 3GPP TSG RAN WG1 NR Ad-Hoc#2, Qingdao, China, Jun. 27-30, 2017, Source: Lenovo, Motorola Mobility, Title: Discussion of beam recovery procedure. [cited by applicant]
R1-1710810 3GPP TSG RAN WG1 AH_NR Meeting, Qingdao, China, Jun. 27-30, 2017, Source: MediaTek Inc., Title: Mechanism for flexible beam failure recovery. [cited by applicant]
R1-1710926 3GPP TSG RAN WG1 NR Ad-Hoc#2, Qingdao, China, Jun. 27-30, 2017, Source: InterDigital, Inc., Title: On Remaining Details of Beam Failure Recovery. [cited by applicant]
R1-1711017 3GPP TSG RAN WG1 #89ah-NR, Qingdao, China, Jun. 27-30, 2017, Source: Ericsson, Title: Mechanism to recover from beam failure. [cited by applicant]
R1-1711291 3GPP TSG RAN WG1 NR Ad-Hoc#2, Qingdao, China, Jun. 27-30, 2017, Source: Nokia, Alcatel-Lucent Shanghai Bell, Title: Beam Recovery. [cited by applicant]
R2-1706680 3GPP TSG-RAN WG2 NR-Adhoc, Qingdao, China, Jun. 27-29, 2017, Source: AT&T, Title: Beam Failure Recovery Mechanism and RLF. [cited by applicant]
3GPP TSG-RAN WG2 NR Ad Hoc, Qingdao, China, Jun. 27-29, 2017, Source: RAN2 Chairman (Intel), Object: Chairman Notes. [cited by applicant]
PRACH—Preamble Detection and Timing Advance Estimation for multi-UE in 3GPP LTE, 3GPP LTE Solutions, from www.mymowireless.com. [cited by applicant]
Jul. 16, 2019—European Extended Search Report—EP 19166184.2. [cited by applicant]
R1-1702078 3GPP TSG RAN WG1 Meeting #88, Athens, Greece, Feb. 13-17, 2017, Source: CATT, Title: Considerations on beam recovery mechanism. [cited by applicant]
R1-1707121 3GPP TSG RAN WG1 Meeting #89, Hangzhou, China, May 15-19, 2017, Source: ZTE, Title: Discussion on beam recovery mechanism. [cited by applicant]
3GPP TS 38.213 V15.0.0 (Dec. 2017); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Physical layer procedures for control (Release 15). [cited by applicant]
3GPP TS 38.213 V15.1.0 (Mar. 2018); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Physical layer procedures for control (Release 15). [cited by applicant]
3GPP TS 38.321 V15.1.0 (Mar. 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]
3GPP TS 38.331 V15.1.0 (Mar. 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 #93 Busan, South Korea, May 21-25, 2018, Source: Ericsson, Title: Feature lead summary for beam measurement and reporting. [cited by applicant]
R1-180xxxx 3GPP TSG RAN WG1 Meeting #92bis, Sanya, China, Apr. 16-20, 2018, Source: MediaTek, Inc., Title: Summary 1 on Remaining issues on Beam Failure Recovery. [cited by applicant]
R1-1803362 3GPP TSG RAN WG1 Meeting #92, Athens, Greece, Feb. 26-Mar. 2, 2018, Source: MediaTek, Inc., Title: Summary on remaining issues on Beam Failure Recovery. [cited by applicant]
R1-180xxxx 3GPP TSG RAN WG1 Meeting #93 Busan, South Korea, May 21-25, 2018, Source: MediaTek Inc., Title: Summary on Remaining issues on Beam Failure Recovery. [cited by applicant]
R1-1704400 3GPP TSG RAN WG1 Meeting #88bis, Spokane, USA, Apr. 3-7, 2017, Source: ZTE, ZTE Microelectronics, Title: Discussion on beam recovery mechanism. [cited by applicant]
R1-1704465 3GPP TSG RAN WG1 Meeting #88bis, Spokane, USA, Apr. 3-7, 2017, Source: MediaTek, Inc., Title: Discussion on beam recovery mechanism. [cited by applicant]
R1-1704478 3GPP TSG RAN WG1 Meeting #88bis, Spokane, USA, Apr. 3-7, 2017, Source: Fujitsu, Title: Discussion on beam failure recovery procedure. [cited by applicant]
R1-1704723 3GPP TSG RAN WG1 Meeting #88bis, Spokane, USA, Apr. 3-7, 2017, Source: Intel Corporation, Title: Details for UL Beam Management. [cited by applicant]
R1-1704725 3GPP TSG RAN WG1 Meeting #88bis, Spokane, USA, Apr. 3-7, 2017, Source: Intel Corporation, Title: On UE Initiated Beam Recovery. [cited by applicant]
R1-1705582 3GPP TSG RAN WG1 Meeting #88bis, Spokane, USA, Apr. 3-7, 2017, Source: Qualcomm Incorporated, Title: Beam recovery procedures. [cited by applicant]
R1-1705893 3GPP TSG RAN WG1 Meeting #88bis, Spokane, USA, Apr. 3-7, 2017, Source: Ericsson, Title: Beam failure detection and beam recovery actions. [cited by applicant]
R1-1705961 3GPP TSG RAN WG1 Meeting #88bis, Spokane, USA, Apr. 3-7, 2017, Source: Nokia, Alcatel-Lucent Shanghai Bell, Title: Beam Recovery in NR. [cited by applicant]
R1-1706928 3GPP TSG RAN WG1 Meeting #89, Hangzhou, China, May 15-19, 2017, Source: Huawei, HiSilicon, Title: Beam management across multiple carriers. [cited by applicant]
R1-1707255 3GPP TSG RAN WG1 Meeting #89, Hangzhou, China, May 15-19, 2017, Source: Fujitsu, Title: Discussion on beam failure recovery procedure. [cited by applicant]
R1-1707356 3GPP TSG RAN WG1 Meeting #89, Hangzhou, China, May 15-19, 2017, Source: Intel Corporation, Title: Discussion for Mechanism to Recover from Beam Failure. [cited by applicant]
R1-1707477 3GPP TSG RAN WG1 Meeting #89, Hangzhou, China, May 15-19, 2017, Source: CATT, Title: Discussion on DL beam recovery. [cited by applicant]
R1-1707698 3GPP TSG RAN WG1 Meeting #89, Hangzhou, China, May 15-19, 2017, Source: Guangdong OPPO Mobile Telecom, Title: On Beam Recovery Mechanism. [cited by applicant]
R1-1707782 3GPP TSG RAN WG1 Meeting #89, Hangzhou, China, May 15-19, 2017, Source: Spreadtrum Communications, Title: Discussion on UE initiated recovery from beam failure. [cited by applicant]
R1-1707814 3GPP TSG RAN WG1 Meeting #89, Hangzhou, China, May 15-19, 2017, Source: NEC, Title: Low latency beam failure recovery by PRACH/PRACH-like. [cited by applicant]
R1-1707954 3GPP TSG RAN WG1 Meeting #89, Hangzhou, China, May 15-19, 2017, Source: Samsung, Title: Discussion on beam recovery procedure. [cited by applicant]
R1-1708678 3GPP TSG RAN WG1 Meeting #89, Hangzhou, China, May 15-19, 2017, Source: Ericsson, Title: Beam failure recovery mechanism. [cited by applicant]
R1-1708905 3GPP TSG RAN WG1 Meeting #89, Hangzhou, China, May 15-19, 2017, Source: Nokia, Alcatel-Lucent Shanghai Bell, Title: Beam Recovery. [cited by applicant]
R1-1710144 3GPP TSG RAN WG1 NR Ad-Hoc #2, Qingdao, China, Jun. 27-30, 2017, Source: Guangdong OPPO Mobile Telecom, Title: On Beam Recovery Mechanism. [cited by applicant]
R1-1710185 3GPP TSG RAN WG1 NR Ad-Hoc #2, Qingdao, China, Jun. 27-30, 2017, Source: ZTE, Title: Discussion on beam recovery mechanism. [cited by applicant]
R1-1710527 3GPP TSG RAN WG1 NR Ad-Hoc #2, Qingdao, China, Jun. 27-30, 2017, Source: Intel Corporation, Title: Discussion for mechanism to recover from beam failure. [cited by applicant]
R1-1710655 3GPP TSG RAN WG1 NR Ad-Hoc #2, Qingdao, China, Jun. 27-30, 2017, Source: Samsung, Title: Beam failure recovery. [cited by applicant]
R1-1714251 3GPP TSG RAN WG1 Meeting #90, Prague, Czech Republic, Aug. 21-25, 2017, Source: Nokia, Nokia Shanghai Bell, Title: Beam recovery in NR. [cited by applicant]
R1-1715468 3GPP TSG RAN WG1 Meeting NR#3, Nagoya, Japan, Sep. 18-21, 2017, Source: Huawei, HiSilicon, Title: Beam Failure Recovery Design Details. [cited by applicant]
R1-1715860 3GPP TSG RAN WG1 Meeting NR#3, Nagoya, Japan, Sep. 18-21, 2017, Source: LG Electronics, Title: Discussion on beam failure recovery. [cited by applicant]
R1-1800362 3GPP TSG RAN WG1 Meeting AH 1801, Vancouver, Canada, Jan. 22-26, 2018, Source: LG Electronics, Title: Clarification on PDCCH beam indication by higher-layers. [cited by applicant]
R1-1800363 3GPP TSG RAN WG1 Meeting AH 1801, Vancouver, Canada, Jan. 22-26, 2018, Source: LG Electronics, Title: Text proposals on UL beam management. [cited by applicant]
R1-1800364 3GPP TSG RAN WG1 Meeting AH 1801, Vancouver, Canada, Jan. 22-26, 2018, Source: LG Electronics, Title: Discussion on PHY and MAC operation for beam failure recovery. [cited by applicant]
R1-1800401 3GPP TSG RAN WG1 Meeting AH 1801, Vancouver, Canada, Jan. 22-26, 2018, Source: Lenovo, Motorola Mobility, Title: Corrections on beam management. [cited by applicant]
R1-1800402 3GPP TSG RAN WG1 Meeting AH 1801, Vancouver, Canada, Jan. 22-26, 2018, Source: Lenovo, Motorola Mobility, Title: Corrections on beam failure recovery. [cited by applicant]
R1-1800432 3GPP TSG RAN WG1 Meeting AH 1801, Vancouver, Canada, Jan. 22-26, 2018, Source: Samsung, Title: Issues on beam management. [cited by applicant]
R1-1800433 3GPP TSG RAN WG1 Meeting AH 1801, Vancouver, Canada, Jan. 22-26, 2018, Source: Samsung, Title: Aperiodic beam reporting. [cited by applicant]
R1-1800434 3GPP TSG RAN WG1 Meeting AH 1801, Vancouver, Canada, Jan. 22-26, 2018, Source: Samsung, Title: Issues on beam failure recovery. [cited by applicant]
R1-1800472 3GPP TSG RAN WG1 Meeting AH 1801, Vancouver, Canada, Jan. 22-26, 2018, Source: Samsung, Title: PHR for CA. [cited by applicant]
R1-1800498 3GPP TSG RAN WG1 Meeting AH 1801, Vancouver, Canada, Jan. 22-26, 2018, Source: OPPO, Title: Text Proposal for Beam Management. [cited by applicant]
R1-1800499 3GPP TSG RAN WG1 Meeting AH 1801, Vancouver, Canada, Jan. 22-26, 2018, Source: OPPO, Title: Text Proposal for Beam Failure Recovery. [cited by applicant]
R1-1715941 3GPP TSG RAN WG1 Meeting NR#3, Nagoya Japan, Sep. 18-21, 2017, Source: Samsung, Title: Beam Failure recovery. [cited by applicant]
R1-1716295 3GPP TSG RAN WG1 Meeting NR#3, Nagoya, Japan, Sep. 18-21, 2017, Source: Intel Corporation, Title: Remaining Issues on Beam Failure Recovery. [cited by applicant]
R1-1716397 3GPP TSG RAN WG1 Meeting NR#3, Nagoya, Japan, Sep. 18-21, 2017, Source: Qualcomm Incorporated, Title: Beam recovery procedure. [cited by applicant]
R1-1716500 3GPP TSG RAN WG1 Meeting NR#3, Nagoya, Japan, 18-21, Sep. 2017, Source: Nokia, Nokia Shanghai Bell, Title Beam Recovery in NR. [cited by applicant]
R1-1716469 3GPP TSG RAN WG1 Meeting NR#3, Nagoya, Japan, Sep. 18-21, 2017: Source: InterDigital, Inc., Title: Remaining issues on beam recovery. [cited by applicant]
R1-1717302 3GPP TSG RAN WG1 Meeting #90bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: Huawei, HiSilicon Title: Beam failure recovery design details. [cited by applicant]
R1-1717369 3GPP TSG RAN WG1 Meeting #90bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: Intel Corporation, Title: Remaining Issues on Beam Failure Recovery. [cited by applicant]
R1-1717473 3GPP TSG RAN WG1 Meeting #90bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: vivo, Title: Discussion on beam failure recovery. [cited by applicant]
R1-1717606 3GPP TSG RAN WG1 Meeting #90bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: Samsung, Title: Beam failure recovery. [cited by applicant]
R1-1717942 3GPP TSG RAN WG1 Meeting #90bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: LG Electronics, Title: Discussion on beam failure recovery. [cited by applicant]
R1-1718010 3GPP TSG RAN WG1 Meeting #90bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: NEC, Title: Discussion on Beam Failure Recovery. [cited by applicant]
R1-1718055 3GPP TSG RAN WG1 Meeting #90bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: OPPO, Title: Discussion on Beam Recovery Mechanism. [cited by applicant]
R1-1718193 3GPP TSG RAN WG1 Meeting #90bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: NTT DOCOMO, Title: Views on beam recovery. [cited by applicant]
R1-1718389 3GPP TSG RAN WG1 Meeting #90bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: AT&T, Title: Beam Recovery for Full and Partial Control Channel Failure. [cited by applicant]
R1-1718512 3GPP TSG RAN WG1 Meeting #90bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: Nokia, Nokia Shanghai Bell, Title: Beam Recovery in NR. [cited by applicant]
R1-1718542 3GPP TSG RAN WG1 Meeting #90bis, Prague Czech Republic, Oct. 9-13, 2017, Source: Qualcomm Incorpated, Title: Beam recovery procedure. [cited by applicant]
R2-1802554 3GPP TSG-RAN WG2 #101, Athens, Greece, February 26-Mar. 2, 2018, Source: ASUSTek, Title: Discussion on Beam Failure Recovery Request in NR. [cited by applicant]
R2-1803195 3GPP TSG-RAN WG2 #101, Athens, Greece, Feb. 26-Mar. 2, 2018, Source: Ericsson, Title: Beam Failure Recovery in Scell. [cited by applicant]
R2-1804877 3GPP TSG-RAN WG2 Meeting #101bis, Sanya, China, Apr. 16-20, 2018, Source: Xiaomi, Title: Consideration on SR Transmission Occasion Overlap with a UL-SCH Resource. [cited by applicant]
R2-18006164 3GPP TSG-RAN WG2 Meeting #101bis, Sanya, China, Apr. 16-20, 2018, Source: MediaTek Inc., Title: On Parallel SR and RACH Procedure in NR. [cited by applicant]
R1-170xxxx 3GPP TSG RAN WG1 Meeting #88b, Spokane, USA, Apr. 3-7, 2017, Source: Huawei, HiSilicon, Title: WF on Beam Failure Recovery. [cited by applicant]
R1-171xxxx 3GPP TSG RAN WG1 Meeting #90, Prague, Czech Republic, Aug. 21-25, 2017, Source: MediaTek Inc. Title: Offline Discussion on Beam Recovery Mechanism. [cited by applicant]
R1-1704230 3GPP TSG RAN WG1 Meeting #88b, Spokane, USA, Apr. 3-7, 2017, Source: Huawei, HiSilicon, Title: Link recovery procedure for beam failure. [cited by applicant]
3GPP TS 36.212 V14.3.0 (Jun. 2017); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Multiplexing and … [cited by applicant]
3GPP TSG RAN WG1 Meeting #90, Prague, Czech Republic, Aug. 21-25, 2017, Title: RAN1 Chairman's Notes. [cited by applicant]
R1-1705719 3GPP TSG RAN WG1 Meeting #88bis, Spokane, USA, Apr. 3-7, 2017, Source: NTT DOCOMO, Inc., Title: Further views on mechanism to recover from beam failure. [cited by applicant]
R1-1711016 3GPP TSG RAN WG1 #89AH-NR, Qingdao, China, Jun. 27-30, 2017, Source: Ericsson, Title: UL beam management details. [cited by applicant]
R1-1712223 3GPP TSG RAN WG1 Meeting #90, Prague, Czech Republic, Aug. 21-25, 2017, Source: Huawei, HiSilicon, Title: UL beam management. [cited by applicant]
R1-1712224 3GPP TSG RAN WG1 Meeting #90, Prague, Czech Republic, Aug. 21-25, 2017, Source: Huawei, HiSilicon, Title: Procedure details for beam failure recovery. [cited by applicant]
R1-1712268 3GPP TSG RAN WG1 Meeting #90, Prague, Czech Republic, Aug. 21-25, 2017, Source: Xinwei, Title: Discussion on beam failure recovery. [cited by applicant]
R1-1712299 3GPP TSG RAN WG1 Meeting #90, Prague, Czech Republic, Aug. 21-25, 2017, Source: ZTE, Title: UL beam management for NR MIMO. [cited by applicant]
R1-1712378 3GPP TSG RAN WG1 Meeting #90, Prague, Czech Republic, Aug. 21-25, 2017, Source: CATT, Title: Considerations on UL beam management. [cited by applicant]
R1-1712379 3GPP TSG RAN WG1 Meeting #90, Prague, Czech Republic, Aug. 21-25, 2017, Source: CATT, Title: Beam failure detection and recovery. [cited by applicant]
R1-1712551 3GPP TSG RAN WG1 Meeting #90, Prague, Czech Republic, Aug. 21-25, 2017, Source: Intel Corporation, Title: Details for UL beam management. [cited by applicant]
R1-1712552 3GPP TSG RAN WG1 Meeting #90, Prague, Czech Republic, Aug. 21-25, 2017, Source: Intel Corporation, Title: Discussion for mechanism to recover from beam failure. [cited by applicant]
R1-1721672 3GPP TSG RAN WG1 Meeting #90, Prague, Czech Republic, Aug. 21-25, 2017, Source: Lenovo, Motorola Mobility, Title: Discussion of beam failure recovery. [cited by applicant]
R1-1712713 3GPP TSG RAN WG1 Meeting #90, Prague, Czech Republic, Aug. 21-25, 2017, Source: AT&T, Title: Mechanisms to recover from beam failure. [cited by applicant]
R1-1712838 3GPP TSG RAN WG1 Meeting #90, Prague, Czech Republic, Aug. 21-25, 2017, Source: Vivo, Title: Discussion on uplink beam management. [cited by applicant]
R1-1712966 3GPP TSG RAN WG1 Meeting #90, Prague, Czech Republic, Aug. 21-25, 2017, Source: Sony, Title: Considerations on UL beam management. [cited by applicant]
R1-1713287 3GPP TSG RAN WG1 Meeting #90, Prague, Czech Republic, Aug. 21-25, 2017, Source: Guangdong OPPO Mobile Telecom, Title: Discussion on the UL beam management. [cited by applicant]
R1-1713596 3GPP TSG RAN WG1 Meeting #90, Prague, Czech Republic, Aug. 21-25, 2017, Source: Samsung, Title: Discussion on UL beam management. [cited by applicant]
R1-1714143 3GPP TSG RAN WG1 Meeting #90, Prague, Czech Republic, Aug. 21-25, 2017, Source: InterDigital, Inc., Title: On efficient UL beam management. [cited by applicant]
R1-1714250 3GPP TSG RAN WG1 Meeting #90, Prague, Czech Republic, Aug. 21-25, 2017, Source: Nokia, Nokia Shanghai Bell, Title: SRS transmission for beam management. [cited by applicant]
R1-1714292 3GPP TSG RAN WG1 Meeting #90, Prague, Czech Republic, Aug. 21-25, 2017, Source: Ericsson, Title: On UL beam management. [cited by applicant]
R1-1714383 3GPP TSG RAN WG1 Meeting #90, Prague, Czech Republic, Aug. 21-25, 2017, Source: ASUSTek, Title: Considerations on UE Beamforming Management. [cited by applicant]
3GPP TSG RAN WG1 Meeting NR#3, Nagoya, Japan, Sep. 18-21, 2017, Title: RAN1 Chairman's Notes. [cited by applicant]
R1-1715441 3GPP TSG RAN WG1 Meeting NR#3, Nagoya, Japan, Sep. 18-21, 2017, Source: ZTE, Sanechips, Title: Discussion on beam recovery. [cited by applicant]
R1-1715620 3GPP TSG RAN WG1 Meeting NR#3, Nagoya, Japan, Sep. 18-21, 2017, Source: Vivo, Title: Discussion on beam failure recovery procedure. [cited by applicant]
R1-1715802 3GPP TSG RAN WG1 Meeting NR#3, Nagoya, Japan, Sep. 18-21, 2017, Source: CATT, Title: Beam failure detection and recovery. [cited by applicant]
R2-1708696 3GPP TSG RAN WG2 #99, Berlin, Germany, Aug. 21-25, 2017, Source: Huawei, HiSilicon, Title: Consideration on DRX with beam management. [cited by applicant]
R2-1708755 3GPP TSG RAN WG2 #99, Berlin, Germany, Aug. 21-25, 2017, Source: LG Electronics, Title: DRX related timers in NR (Revision of R2-1706750). [cited by applicant]
R2-1708791 3GPP TSG RAN WG2 #99, Berlin, Germany, Aug. 21-25, 2017, Source: Intel Corporation, Title: C-DRX enhancement in NR (Revision of R2-1707026). [cited by applicant]
R2-1709223 3GPP TSG RAN WG2 #99, Berlin, Germany, Aug. 21-25, 2017, Source: Qualcomm Incorporated, Title: Beam management in C-DRX. [cited by applicant]
R2-1709588 3GPP TSG RAN WG2 #99, Berlin, Germany, Aug. 21-25, 2017, Source: Samsung, Title: NR beamformed C-DRX operation (updated resubmission of R2-1705734). [cited by applicant]
R2-1709652 3GPP TSG RAN WG2 #99, Berlin, Germany, Aug. 21-25, 2017, Source: Qualcomm Incorporated, Apple, OPPO, Title: Wake-Up Signaling for C-DRX Mode. [cited by applicant]
R2-1709916 3GPP TSG RAN WG2 #99, Berlin, Germany, Aug. 21-25, 2017, Source: Ericsson, Title: Reply LS to SA2 on 5QIs for URLLC. [cited by applicant]
Aug. 27, 2019—European Extended Search Report—EP 19173892.1. [cited by applicant]
3GPP TSG-RAN WG1 #89: “Beam failure recovery mechanism”, May 15, 2017. [cited by applicant]
3GPP TSG-RAN WG2 Meeting#AH: “Random access procedure for beam recovery request”, Jun. 27, 2017. [cited by applicant]
Sep. 25, 2019—European Extended Search Report—EP 19166863.1. [cited by applicant]
R1-1803368 3GPP TSG RAN WG1 Meeting #92, Athens, Greece, Feb. 26-Mar. 2, 2018, Source: [RAN1], Title: Draft LS reply to RAN2 on beam failure recovery. [cited by applicant]
R1-1803441 3GPP TSG RAN WG1 Meeting #92, Athens, Greece, Feb. 26-Mar. 2, 2018, Source: MediaTek Inc., Title: Summary 2 on Remaing issues on Beam Failure Recovery. [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]
R1-1719423 3GPP TSG RAN WG1 Meeting #91, Reno, USA, Nov. 27-Dec. 1, 2017, Source: Huawei, HiSilicon, Title: Remaining details on beam failure recovery. [cited by applicant]
R1-1719619 3GPP TSG RAN WG1 Meeting #91, Reno, USA, Nov. 27-Dec. 1, 2017, Source: Fujitsu, Title: Discussion on beam failure recovery. [cited by applicant]
R1-1719633 3GPP TSG RAN WG1 Meeting #91, Reno, USA, Nov. 27-Dec. 1, 2017, Source: AT&T, Title: Remaining Details on Mechanisms to Recover from Beam Failure. [cited by applicant]
R1-1719695 3GPP TSG RAN WG1 Meeting #91, Reno, USA, Nov. 27-Dec. 1, 2017, Source: Spreadtrum Communications, Title: Remaining issues on beam failure recovery mechanism. [cited by applicant]
R1-1719770 3GPP TSG RAN WG1 Meeting #91, Reno, USA, Nov. 27-Dec. 1, 2017, Source: vivo, Title: Remaining details on mechanism to recover from beam failure. [cited by applicant]
R1-1719809 3GPP TSG RAN WG1 Meeting #91, Reno, USA, Nov. 27-Dec. 1, 2017, Source: Huawei, HiSilicon, Title: Design of PUCCH-based Beam Failure Recovery. [cited by applicant]
R1-1719908 3GPP TSG RAN WG1 Meeting #91, Reno, USA, Nov. 27-Dec. 1, 2017, Source: LG Electronics, Title: Discussion on beam failure recovery. [cited by applicant]
R1-1719988 3GPP TSG RAN WG1 Meeting #91, Reno, USA, Nov. 27-Dec. 1, 2017, Source: Discussion on Beam Recovery Mechanism. [cited by applicant]
R1-1720072 3GPP TSG RAN WG1 Meeting #91, Reno, USA, Nov. 27-Dec. 1, 2017, Source: Intel Corporation, Title: Remaining Issues on Beam Failure Recovery. [cited by applicant]
R1-1720291 3GPP TSG RAN WG1 Meeting #91, Reno, USA, Nov. 27-Dec. 1, 2017, Source Samsung, Title: Beam failure recovery. [cited by applicant]
R1-1720305 3GPP TSG RAN WG1 Meeting #91, Reno, USA, Nov. 27-Dec. 1, 2017, Source: Samsung, Title: Discussion on cross-carrier beam management. [cited by applicant]
R1-1720574 3GPP TSG RAN WG1 Meeting #91, Reno, USA, Nov. 27-Dec. 1, 2017, Source: NEC, Title: On Partial Beam Failure Recovery. [cited by applicant]
R1-1720631 3GPP TSG RAN WG1 Meeting #91, Reno, USA, Nov. 27-Dec. 1, 2017, Source: InterDigital, Inc., Title: Remaining issues on beam recovery. [cited by applicant]
R1-1720804 3GPP TSG RAN WG1 Meeting #91, Reno, USA, Nov. 27-Dec. 1, 2017, Source: NTT DOCOMO, Title: Remaining issue on beam recovery. [cited by applicant]
R1-1720891 3GPP TSG RAN WG1 Meeting #91, Reno, USA, Nov. 27-Dec. 1, 2017, Source: Nokia, Nokia Shanghai Bell, Title: Beam Recovery in NR. [cited by applicant]
R1-1721523 3GPP TSG RAN WG1 Meeting #91, Reno, USA, Nov. 27-Dec. 1, 2017, Source: NTT DOCOMO, Samsung, Mediatek, AT&T, ZTE, Intel, Huawei, CATT, Qualcomm, Fujitsu, Spreadtrum, Title: WF for handling partial beam failure. [cited by applicant]
R1-1721673 3GPP TSG RAN WG1 Meeting #91, Reno, USA, Nov. 27-Dec. 1, 2017, Source: NTT DOCOMO, Intel, Huawei, NEC, Spreadtrum, Mediatek, China Telecom, AT&T, Samsung, ZTE, Catt, Qualcomm, Fujitsu, Nokia, Title: WF for ha… [cited by applicant]
R1-1800100 3GPP TSG RAN WG1 Meeting Ad Hoc, Vancouver, Canada, Jan. 22-26, 2018, Source: Huawei, HiSilicon, Title: Summary of remaining issues of beam measurement, reporting and indication. [cited by applicant]
R1-1800101 3GPP TSG RAN WG1 Meeting Ad Hoc, Vancouver, Canada, Jan. 22-26, 2018, Source: Huawei, HiSilicon, Title: Summary of remaining issues on beam failure recovery. [cited by applicant]
R1-1800110 3GPP TSG RAN WG1 Meeting Ad Hoc, Vancouver, Canada, Jan. 22-26, 2018, Source: ZTE, Sanechips, Title: Remaining details on bean management. [cited by applicant]
R1-1800111 3GPP TSG RAN WG1 Meeting Ad Hoc, Vancouver, Canada, Jan. 22-26, 2018, Source: ZTE, Sanechips, Title: Remaining details on mean management. [cited by applicant]
R1-1800312 3GPP TSG RAN WG1 Meeting Ad Hoc, Vancouver, Canada, Jan. 22-26, 2018, Source: Intel Corporation, Title: Remaining Issues on Beam Failure Recovery. [cited by applicant]
R1-1800526 3GPP TSG RAN WG1 Meeting Ad Hoc, Vancouver, Canada, Jan. 22-26, 2018, Source: Huawei, HiSilicon, Title: Remaining details of PHR. [cited by applicant]
R1-1800542 3GPP TSG RAN WG1 Meeting Ad Hoc, Vancouver, Canada, Jan. 22-26, 2018, Source: CMCC, Title: Discussion on remaining issues for beam indication. [cited by applicant]
R1-1800543 3GPP TSG RAN WG1 Meeting Ad Hoc, Vancouver, Canada, Jan. 22-26, 2018, Source: CMCC, Title: Discussion on beam recovery mechanism. [cited by applicant]
R1-1800582 3GPP TSG RAN WG1 Meeting Ad Hoc, Vancouver, Canada, Jan. 22-26, 2018, Source: AT&T, Title: TCI states configuration design to support dynamic BWP switching. [cited by applicant]
R1-1800583 3GPP TSG RAN WG1 Meeting Ad Hoc, Vancouver, Canada, Jan. 22-26, 2018, Source: AT&T, Title: In support of partial beam failure. [cited by applicant]
R1-1800622 3GPP TSG RAN WG1 Meeting Ad Hoc, Vancouver, Canada, Jan. 22-26, 2018, Source: ASUSTek, Title: Remaining Issues for Beam Failure Recovery Procedure. [cited by applicant]
R1-1800629 3GPP TSG RAN WG1 Meeting Ad Hoc, Vancouver, Canada, Jan. 22-26, 2018, Source: InterDigital, Inc., Title: Remaining details on beam failure recovery. [cited by applicant]
R1-1800642 3GPP TSG RAN WG1 Meeting Ad Hoc, Vancouver, Canada, Jan. 22-26, 2018, Source: ITRI, Title: Discussion on timer for beam failure recovery. [cited by applicant]
R1-1800660 3GPP TSG RAN WG1 Meeting Ad Hoc, Vancouver, Canada, Jan. 22-26, 2018, Source: NTT DOCOMO, Title: Remaining Issue on Beam Indication. [cited by applicant]
R1-1800661 3GPP TSG RAN WG1 Meeting Ad Hoc, Vancouver, Canada, Jan. 22-26, 2018, Source: NTT DOCOMO, Title: Remaining issue on beam recovery. [cited by applicant]
R1-1800682 3GPP TSG RAN WG1 Meeting Ad Hoc, Vancouver, Canada, Jan. 22-26, 2018, Source: NTT DOCOMO, Inc., Title: Remaining issues on PHR. [cited by applicant]
R1-1800699 3GPP TSG RAN WG1 Meeting Ad Hoc, Vancouver, Canada, Jan. 22-26, 2018, Source: Ericsson, Title: Remaining details on beam management. [cited by applicant]
R1-1800700 3GPP TSG RAN WG1 Meeting Ad Hoc, Vancouver, Canada, Jan. 22-26, 2018, Source: Ericsson, Title: Remaining details and corrections for beam recovery. [cited by applicant]
R1-1800734 3GPP TSG RAN WG1 Meeting Ad Hoc, Vancouver, Canada, Jan. 22-26, 2018, Source: InterDigital, Inc., Title: Remaining issues on beam management. [cited by applicant]
R1-1800751 3GPP TSG RAN WG1 Meeting Ad Hoc, Vancouver, Canada, Jan. 22-26, 2018, Source: Nokia, Nokia Shanghai Bell, Title: Remaining details on beam indication, measurement and reporting. [cited by applicant]
R1-1800752 3GPP TSG RAN WG1 Meeting Ad Hoc, Vancouver, Canada, Jan. 22-26, 2018, Source: Nokia, Nokia Shanghai Bell, Title: Remaining Details on Beam Recovery. [cited by applicant]
R1-1800859 3GPP TSG RAN WG1 Meeting Ad Hoc, Vancouver, Canada, Jan. 22-26, 2018, Source: Qualcomm, Title: Beam management for NR. [cited by applicant]
R1-1800860 3GPP TSG RAN WG1 Meeting Ad Hoc, Vancouver, Canada, Jan. 22-26, 2018, Source: Qualcomm Incorporated, Title: Remaining details on beam recovery procedure. [cited by applicant]
R1-1801006 3GPP TSG RAN WG1 Meeting Ad Hoc, Vancouver, Canada, Jan. 22-26, 2018, Source: Ericsson, Title; Feature lead summary 1 of beam measurement and reporting. [cited by applicant]
R1-1801089 3GPP TSG RAN WG1 Meeting Ad Hoc, Vancouver, Canada, Jan. 22-26, 2018, Source: Media Tec Inc., Title: Summary for Remaining issue on Beam Failure Recovery. [cited by applicant]
R1-1801143 3GPP TSG RAN WG1 Meeting Ad Hoc, Vancouver, Canada, Jan. 22-26, 2018, Source: Ericsson, Title: Feature lead summary 2 of beam measurement and reporting. [cited by applicant]
R1-1801160 3GPP TSG RAN WG1 Meeting Ad Hoc, Vancouver, Canada, Jan. 22-26, 2018, Source: NTT DOCOMO, Qualcomm, Huawei, HiSilicon, ZTE, Sanechips, Fujitsu, Title: Updated offline proposal on PHR. [cited by applicant]
R1-1801187 3GPP TSG RAN WG1 Meeting Ad Hoc, Vancouver, Canada, Jan. 22-26, 2018, Source: Ericsson, Title: Feature lead summary 3 of beam measurement and reporting. [cited by applicant]
R1-1801197 3GPP TSG RAN WG1 Meeting Ad Hoc, Vancouver, Canada, Jan. 22-26, 2018, Source: MediaTek Inc., Title: Offline Summary for Remaining issues on Beam Failure Recovery. [cited by applicant]
R1-1801223 3GPP TSG RAN WG1 Meeting Ad Hoc, Vancouver, Canada, Jan. 22-26, 2018, Source: MediaTek Inc., Title: Offline Discussion Summary for Beam Failure Recovery. [cited by applicant]
R1-1801228 3GPP TSG RAN WG1 Meeting Ad Hoc, Vancouver, Canada, Jan. 22-26, 2018, Source: Ericsson, Title: Text proposal on source QCL for semi-persistent CSI-RS. [cited by applicant]
R1-1801229 3GPP TSG RAN WG1 Meeting Ad Hoc, Vancouver, Canada, Jan. 22-26, 2018, Source: Ericsson, Title: Text proposal for source spatial relation for semi-persistent SRS. [cited by applicant]
R1-1801230 3GPP TSG RAN WG1 Meeting Ad Hoc, Vancouver, Canada, Jan. 22-26, 2018, Source: Ericsson, Title: Text proposal on priority rules for PUCCH carrying RSRP reports and SRS. [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-1806774 3GPP TSG-RAN WG2 Meeting #102, Sanya, China, Apr. 16-20, 2018, Source: Nokia, Nokia Shanghai Bell, Title: Finalization of dormant SCell state. [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-1806924 3GPP TSG-RAN WG2 Meeting #102, Busan, Korea, May 21-25, 2018, Source: Qualcomm, Inc., Title: SCell Dormant State Transitions based on New Timers & MAC-CEs. [cited by applicant]
R2-1806998 3GPP TSG-RAN WG2 Meeting #102, Busan, Korea, May 21-25, 2018, Source: CATT, Title: The validity of CFRA resources for BFR. [cited by applicant]
R2-1807160 3GPP TSG-RAN WG2 Meeting #102, Busan, Korea, May 21-25, 2018, Source: Panasonic, Title: Timer associated with the dedicated BFR PRACH resource. [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-1807481 3GPP TSG RAN WG2 Meeting #102, Busan, Korea, May 21-25, 2018, Source: Huawei, HiSilicon, Title: Remaining issues of temporary CQI reporting. [cited by applicant]
R2-1807584 3GPP TSG RAN WG2 Meeting #102, Busan, Korea, May 21-25, 2018, Source: vivo, Title: Discussion on the SCell 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-1808570 3GPP TSG RAN WG2 Meeting #102, Busan, Korea, May 21-25, 2018, Source: Qualcomm Incorporated, Title: Dormant BWP for fast SCell activation. [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-1808809 3GPP TSG RAN WG2 Meeting #102, Busan, Korea, May 21-25, 2018, Source: Ericsson, Title: CR on Dormat SCell state transition Mac Ce. [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]