IP Library › Granted Patent US 12,341,719
Granted Patent B2
US 12,341,719 · App. 18/520,071 · Granted Jun 24, 2025

Beam failure recovery request transmission

Inventors: Hua Zhou (Vienna, VA); Esmael Hejazi Dinan (McLean, VA); Hyoungsuk Jeon (Centreville, VA); Kyungmin Park (Vienna, VA); Alireza Babaei (Fairfax, VA)
Assignee: Comcast Cable Communications, LLC
H04L5/0048H04B7/0626H04B7/0695H04B7/088H04L27/2692H04W76/18H04W76/19H04L27/2613H04W74/0833H04W76/27
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,341,719
App. No.
18/520,071
Granted
Jun 24, 2025
Kind
B2
Abstract

Systems, apparatuses, and methods are described for wireless communications. A base station may transmit an indication of a type of a beam failure recovery request. A wireless device may detect a beam failure and transmit a beam failure recovery requested based on the type.

Claims (101)

1. A method comprising:

receiving, by a wireless device, one or more messages that indicate:

one or more reference signals associated with beam failure recovery;

a plurality of beam failure recovery request resources; and

a beam failure recovery type; and

transmitting, based on at least one beam failure, an uplink signal, associated with the beam failure recovery type, via a beam failure recovery request resource of the plurality of beam failure recovery request resources.

2. The method of claim 1 , wherein the beam failure recovery type is associated with a beam failure recovery request, and wherein the transmitting the uplink signal comprises transmitting the uplink signal via a beam failure recovery request resource that is a random access channel resource associated with a serving beam on which the at least one beam failure has occurred.

3. The method of claim 1 , wherein the one or more reference signals comprise a plurality of candidate beam reference signals, wherein the beam failure recovery type is associated with a beam failure recovery request, and wherein the transmitting the uplink signal comprises transmitting the uplink signal via a beam failure recovery request resource that is a random access channel resource associated with the plurality of candidate beam reference signals.

4. The method of claim 1 , wherein the beam failure recovery type is associated with a beam failure recovery request, wherein the transmitting the uplink signal comprises transmitting the uplink signal via a beam failure recovery request resource that is a random access channel resource associated with a serving beam, and wherein the uplink signal indicates that the serving beam has failed and that no candidate beam has been identified.

5. The method of claim 1 , wherein the one or more reference signals comprise at least one beam failure detection reference signal, the method further comprising detecting, based on a determination that the at least one beam failure detection reference signal fails to satisfy a threshold, the at least one beam failure.

6. The method of claim 1 , wherein the one or more reference signals comprise at least one beam failure detection reference signal and a plurality of candidate beam reference signals, the method further comprising:

determining that a first channel quality of the at least one beam failure detection reference signal fails to satisfy a first threshold;

determining that a second channel quality of at least one reference signal of the plurality of candidate beam reference signals satisfies a second threshold; and

transmitting, via a beam failure recovery request resource associated with one or more of the plurality of candidate beam reference signals, a second uplink signal.

7. The method of claim 1 , wherein the one or more reference signals comprise at least one beam failure detection reference signal and a plurality of candidate beam reference signals, the method further comprising:

determining that a first channel quality of the at least one beam failure detection reference signal fails to satisfy a first threshold;

determining that a second channel quality of at least one reference signal of the plurality of candidate beam reference signals fails to satisfy a second threshold; and

transmitting, via a beam failure recovery request resource associated with a serving beam on which the at least one beam failure was detected, a second uplink signal.

8. The method of claim 1 , wherein the one or more messages comprise one or more radio resource control messages comprising a plurality of parameters, and wherein the plurality of parameters comprises configuration parameters of a cell.

9. 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 messages that indicate:

one or more reference signals associated with beam failure recovery;

a plurality of beam failure recovery request resources; and

a beam failure recovery type; and

transmit, based on at least one beam failure, an uplink signal, associated with the beam failure recovery type, via a beam failure recovery request resource of the plurality of beam failure recovery request resources.

10. The wireless device of claim 9 , wherein the beam failure recovery type is associated with a beam failure recovery request, and wherein the instructions, when executed by the one or more processors, cause the wireless device to transmit, via a beam failure recovery request resource that is a random access channel resource associated with a serving beam on which the at least one beam failure has occurred, the uplink signal.

11. The wireless device of claim 9 , wherein the one or more reference signals comprise a plurality of candidate beam reference signals, wherein the beam failure recovery type is associated with a beam failure recovery request, and wherein the instructions, when executed by the one or more processors, cause the wireless device to transmit, via a beam failure recovery request resource that is a random access channel resource associated with the plurality of candidate beam reference signals, the uplink signal.

12. The wireless device of claim 9 , wherein the one or more reference signals comprise at least one beam failure detection reference signal, and wherein the instructions, when executed by the one or more processors, cause the wireless device to detect, based on a determination that the at least one beam failure detection reference signal fails to satisfy a threshold, the at least one beam failure.

13. The wireless device of claim 9 , wherein the one or more reference signals comprise at least one beam failure detection reference signal and a plurality of candidate beam reference signals, and wherein the instructions, when executed by the one or more processors, cause the wireless device to:

determine that a first channel quality of the at least one beam failure detection reference signal fails to satisfy a first threshold;

determine that a second channel quality of at least one reference signal of the plurality of candidate beam reference signals satisfies a second threshold; and

transmit, via a beam failure recovery request resource associated with one or more of the plurality of candidate beam reference signals, a second uplink signal.

14. The wireless device of claim 9 , wherein the one or more reference signals comprise at least one beam failure detection reference signal and a plurality of candidate beam reference signals, and wherein the instructions, when executed by the one or more processors, cause the wireless device to:

determine that a first channel quality of the at least one beam failure detection reference signal fails to satisfy a first threshold;

determine that a second channel quality of at least one reference signal of the plurality of candidate beam reference signals fails to satisfy a second threshold; and

transmit, via a beam failure recovery request resource associated with a serving beam on which the at least one beam failure was detected, a second uplink signal.

15. The wireless device of claim 9 , wherein the beam failure recovery type is associated with a beam failure recovery request, wherein the instructions, when executed by the one or more processors, cause the wireless device to transmit, via a beam failure recovery request resource that is a random access channel resource associated with a serving beam, the uplink signal, and wherein the uplink signal indicates that the serving beam has failed and that no candidate beam has been identified.

16. A method comprising:

transmitting, by a base station, one or more messages that indicate:

one or more reference signals associated with beam failure recovery;

a plurality of beam failure recovery request resources; and

a beam failure recovery type; and

receiving, based on at least one beam failure, an uplink signal, associated with the beam failure recovery type, via a beam failure recovery request resource of the plurality of beam failure recovery request resources.

17. The method of claim 16 , wherein the beam failure recovery type is associated with a beam failure recovery request, and wherein the receiving the uplink signal comprises receiving, via a beam failure recovery request resource that is a random access channel resource associated with a serving beam on which the at least one beam failure has occurred, the uplink signal.

18. The method of claim 16 , wherein the one or more reference signals comprise a plurality of candidate beam reference signals, wherein the beam failure recovery type is associated with a beam failure recovery request, and wherein the receiving the uplink signal comprises receiving, via a beam failure recovery request resource that is a random access channel resource associated with the plurality of candidate beam reference signals, the uplink signal.

19. The method of claim 16 , wherein the one or more reference signals comprise at least one beam failure detection reference signal, and wherein the receiving is based on a determination that the at least one beam failure detection reference signal fails to satisfy a threshold.

20. The method of claim 16 , wherein the one or more reference signals comprise a plurality of candidate beam reference signals, the method further comprising:

receiving, based on a determination that a channel quality of at least one reference signal of the plurality of candidate beam reference signals satisfies a threshold and via a beam failure recovery request resource associated with one or more of the plurality of candidate beam reference signals, a second uplink signal.

21. The method of claim 16 , wherein the one or more reference signals comprise a plurality of candidate beam reference signals, the method further comprising:

receiving, based on a determination that a channel quality of at least one reference signal of the plurality of candidate beam reference signals fails to satisfy a threshold and via a beam failure recovery request resource associated with a serving beam on which the at least one beam failure was detected, a second uplink signal.

22. The method of claim 16 , wherein the beam failure recovery type is associated with a beam failure recovery request, wherein the receiving the uplink signal comprises receiving, via a beam failure recovery request resource that is a random access channel resource associated with a serving beam, the uplink signal, and wherein the uplink signal indicates that the serving beam has failed and that no candidate beam has been identified.

23. A base station comprising:

one or more processors; and

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

transmit one or more messages that indicate:

one or more reference signals associated with beam failure recovery;

a plurality of beam failure recovery request resources; and

a beam failure recovery type; and

receive, based on at least one beam failure, an uplink signal, associated with the beam failure recovery type, via a beam failure recovery request resource of the plurality of beam failure recovery request resources.

24. The base station of claim 23 , wherein the beam failure recovery type is associated with a beam failure recovery request, and wherein the instructions, when executed by the one or more processors, cause the base station to receive, via a beam failure recovery request resource that is a random access channel resource associated with a serving beam on which the at least one beam failure has occurred, the uplink signal.

25. The base station of claim 23 , wherein the one or more reference signals comprise at least one beam failure detection reference signal, wherein the instructions, when executed by the one or more processors, cause the base station to receive, based on a determination that the at least one beam failure detection reference signal fails to satisfy a threshold, the uplink signal.

26. The base station of claim 23 , wherein the one or more reference signals comprise a plurality of candidate beam reference signals, wherein the beam failure recovery type is associated with a beam failure recovery request, and wherein the instructions, when executed by the one or more processors, cause the base station to receive, via a beam failure recovery request resource that is a random access channel resource associated with the plurality of candidate beam reference signals, the uplink signal.

27. The base station of claim 23 , wherein the one or more reference signals comprise a plurality of candidate beam reference signals, wherein the instructions, when executed by the one or more processors, cause the base station to receive, based on a determination that a channel quality of at least one reference signal of the plurality of candidate beam reference signals satisfies a threshold and via a beam failure recovery request resource associated with one or more of the plurality of candidate beam reference signals, a second uplink signal.

28. The base station of claim 23 , wherein the one or more reference signals comprise a plurality of candidate beam reference signals, wherein the instructions, when executed by the one or more processors, cause the base station to receive, based on a determination that a channel quality of at least one reference signal of the plurality of candidate beam reference signals fails to satisfy a threshold and via a beam failure recovery request resource associated with a serving beam on which the at least one beam failure was detected, a second uplink signal.

29. The base station of claim 23 , wherein the beam failure recovery type is associated with a beam failure recovery request, wherein the instructions, when executed by the one or more processors, cause the base station to receive, via a beam failure recovery request resource that is a random access channel resource associated with a serving beam, the uplink signal, and wherein the uplink signal indicates that the serving beam has failed and that no candidate beam has been identified.

30. A non-transitory computer-readable medium storing instructions that, when executed, cause:

receiving, by a wireless device, one or more messages that indicate:

one or more reference signals associated with beam failure recovery;

a plurality of beam failure recovery request resources; and

a beam failure recovery type; and

transmitting, based on at least one beam failure, an uplink signal, associated with the beam failure recovery type, via a beam failure recovery request resource of the plurality of beam failure recovery request resources.

31. The non-transitory computer-readable medium of claim 30 , wherein the beam failure recovery type is associated with a beam failure recovery request, and wherein the transmitting the uplink signal comprises transmitting the uplink signal via a beam failure recovery request resource that is a random access channel resource associated with a serving beam on which the at least one beam failure has occurred.

32. The non-transitory computer-readable medium of claim 30 , wherein the one or more reference signals comprise a plurality of candidate beam reference signals, wherein the beam failure recovery type is associated with a beam failure recovery request, and wherein the transmitting the uplink signal comprises transmitting the uplink signal via a beam failure recovery request resource that is a random access channel resource associated with the plurality of candidate beam reference signals.

33. The non-transitory computer-readable medium of claim 30 , wherein the beam failure recovery type is associated with a beam failure recovery request, wherein the transmitting the uplink signal comprises transmitting the uplink signal via a beam failure recovery request resource that is a random access channel resource associated with a serving beam, and wherein the uplink signal indicates that the serving beam has failed and that no candidate beam has been identified.

34. The non-transitory computer-readable medium of claim 30 , wherein the one or more reference signals comprise at least one beam failure detection reference signal, and wherein the instructions, when executed, further cause:

detecting, based on a determination that the at least one beam failure detection reference signal fails to satisfy a threshold, the at least one beam failure.

35. The non-transitory computer-readable medium of claim 30 , wherein the one or more reference signals comprise at least one beam failure detection reference signal and a plurality of candidate beam reference signals, and wherein the instructions, when executed, further cause:

determining that a first channel quality of the at least one beam failure detection reference signal fails to satisfy a first threshold;

determining that a second channel quality of at least one reference signal of the plurality of candidate beam reference signals satisfies a second threshold; and

transmitting, via a beam failure recovery request resource associated with one or more of the plurality of candidate beam reference signals, a second uplink signal.

36. The non-transitory computer-readable medium of claim 30 , wherein the one or more reference signals comprise at least one beam failure detection reference signal and a plurality of candidate beam reference signals, and wherein the instructions, when executed, further cause:

determining that a first channel quality of the at least one beam failure detection reference signal fails to satisfy a first threshold;

determining that a second channel quality of at least one reference signal of the plurality of candidate beam reference signals fails to satisfy a second threshold; and

transmitting, via a beam failure recovery request resource associated with a serving beam on which the at least one beam failure was detected, a second uplink signal.

37. The non-transitory computer-readable medium of claim 30 , wherein the one or more messages comprise one or more radio resource control messages comprising a plurality of parameters, and wherein the plurality of parameters comprises configuration parameters of a cell.

38. A non-transitory computer-readable medium storing instructions that, when executed, cause:

transmitting, by a base station, one or more messages that indicate:

one or more reference signals associated with beam failure recovery;

a plurality of beam failure recovery request resources; and

a beam failure recovery type; and

receiving, based on at least one beam failure, an uplink signal, associated with the beam failure recovery type, via a beam failure recovery request resource of the plurality of beam failure recovery request resources.

39. The non-transitory computer-readable medium of claim 38 , wherein the beam failure recovery type is associated with a beam failure recovery request, and wherein the receiving the uplink signal comprises receiving, via a beam failure recovery request resource that is a random access channel resource associated with a serving beam on which the at least one beam failure has occurred, the uplink signal.

40. The non-transitory computer-readable medium of claim 38 , wherein the one or more reference signals comprise a plurality of candidate beam reference signals, wherein the beam failure recovery type is associated with a beam failure recovery request, and wherein the receiving the uplink signal comprises receiving, via a beam failure recovery request resource that is a random access channel resource associated with the plurality of candidate beam reference signals, the uplink signal.

41. The non-transitory computer-readable medium of claim 38 , wherein the one or more reference signals comprise at least one beam failure detection reference signal, and wherein the receiving is based on a determination that the at least one beam failure detection reference signal fails to satisfy a threshold.

42. The non-transitory computer-readable medium of claim 38 , wherein the one or more reference signals comprise a plurality of candidate beam reference signals, and wherein the instructions, when executed, further cause:

receiving, based on a determination that a channel quality of at least one reference signal of the plurality of candidate beam reference signals satisfies a threshold and via a beam failure recovery request resource associated with one or more of the plurality of candidate beam reference signals, a second uplink signal.

43. The non-transitory computer-readable medium of claim 38 , wherein the one or more reference signals comprise a plurality of candidate beam reference signals, and wherein the instructions, when executed, further cause:

receiving, based on a determination that a channel quality of at least one reference signal of the plurality of candidate beam reference signals fails to satisfy a threshold and via a beam failure recovery request resource associated with a serving beam on which the at least one beam failure was detected, a second uplink signal.

44. The non-transitory computer-readable medium of claim 38 , wherein the beam failure recovery type is associated with a beam failure recovery request, wherein the receiving the uplink signal comprises receiving, via a beam failure recovery request resource that is a random access channel resource associated with a serving beam, the uplink signal, and wherein the uplink signal indicates that the serving beam has failed and that no candidate beam has been identified.

Assignments (4)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 13, 2026
From: OFINNO, LLC
To: BLOOMSBURY DESIGN LABS LLC
Reel/Frame 075081/0540 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 6, 2026
From: COMCAST CABLE COMMUNICATIONS, LLC
To: OFINNO, LLC
Reel/Frame 074245/0446 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 3, 2024
From: ZHOU, HUA; DINAN, ESMAEL HEJAZI; JEON, HYOUNGSUK; PARK, KYUNGMIN; BABAEI, ALIREZA
To: COMCAST CABLE COMMUNICATIONS, LLC
Reel/Frame 067908/0252 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 3, 2024
From: ZHOU, HUA; DINAN, ESMAEL HEJAZI; JEON, HYOUNGSUK; PARK, KYUNGMIN; BABAEI, ALIREZA
To: COMCAST CABLE COMMUNICATIONS, LLC
Reel/Frame 067908/0261 →
Continuity (4)
Continuation 17722108 · Apr 15, 2022
Continuation 16101307 · Aug 10, 2018
Provisional Application 62543816 · Aug 10, 2017
Related Publication 20240163048A1 · May 16, 2024
References Cited (400)
US 6490261B1 · Dent et al. · 2002 [cited by applicant]
US 9125218B2 · Chang · 2015 [cited by applicant]
US 9585188B2 · Jang et al. · 2017 [cited by applicant]
US 9736795B2 · Dinan · 2017 [cited by applicant]
US 9814076B2 · Kim et al. · 2017 [cited by applicant]
US 9936516B2 · Hirsch et al. · 2018 [cited by applicant]
US 9949298B1 · Akoum et al. · 2018 [cited by applicant]
US 10278160B2 · Agiwal et al. · 2019 [cited by applicant]
US 10313216B2 · Zheng et al. · 2019 [cited by applicant]
US 10333672B2 · Nagaraja et al. · 2019 [cited by applicant]
US 10461994B2 · Liu et al. · 2019 [cited by applicant]
US 10541741B2 · Islam et al. · 2020 [cited by applicant]
US 10555359B2 · Xia et al. · 2020 [cited by applicant]
US 10965568B2 · Zheng et al. · 2021 [cited by applicant]
US 20100279700A1 · Kim et al. · 2010 [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 20150271796A1 · Jang et al. · 2015 [cited by applicant]
US 20150365921A1 · Wu · 2015 [cited by applicant]
US 20160205631A1 · Chen et al. · 2016 [cited by applicant]
US 20170099126A1 · Yoo et al. · 2017 [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 20170346545A1 · Islam 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 20180034611A1 · Nagaraja 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 20180083751A1 · Seo 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 20180145807A1 · Nagata et al. · 2018 [cited by applicant]
US 20180167933A1 · Yin 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 20180270689A1 · Akkarakaran 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 20180279229A1 · Dinan et al. · 2018 [cited by applicant]
US 20180287860A1 · Xia 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 20180359790A1 · Ingale 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 20180375560A1 · Wei · 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 20190044792A1 · Kwon et al. · 2019 [cited by applicant]
US 20190052339A1 · Zhou et al. · 2019 [cited by applicant]
US 20190053294A1 · Xia 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 20190075600A1 · Kwon et al. · 2019 [cited by applicant]
US 20190090143A1 · Luo et al. · 2019 [cited by applicant]
US 20190104549A1 · Deng et al. · 2019 [cited by applicant]
US 20190141555A1 · Tooher et al. · 2019 [cited by applicant]
US 20190159234A1 · Yi et al. · 2019 [cited by applicant]
US 20190173740A1 · Zhang et al. · 2019 [cited by applicant]
US 20190268893A1 · Tsai et al. · 2019 [cited by applicant]
US 20200059285A1 · Zhang et al. · 2020 [cited by applicant]
US 20200059398A1 · Pan et al. · 2020 [cited by applicant]
US 20200059898A1 · Osawa et al. · 2020 [cited by applicant]
US 20200068416A1 · Kang et al. · 2020 [cited by applicant]
US 20200092785A1 · Yang · 2020 [cited by applicant]
US 20200120714A1 · Wang et al. · 2020 [cited by applicant]
US 20200178338A1 · Ahn et al. · 2020 [cited by applicant]
CN 108809580A · 2018 [cited by applicant]
EP 3099118A1 · 2016 [cited by applicant]
EP 3397015A1 · 2018 [cited by applicant]
EP 3424152A1 · 2019 [cited by applicant]
WO 2013025142A1 · 2013 [cited by applicant]
WO 2017024516A1 · 2017 [cited by applicant]
WO 2017123060A1 · 2017 [cited by applicant]
WO 2017135803A1 · 2017 [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 Beam Failure Recovery Configuration. [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, November 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, February 26-Mar. 2, 2018, Source: CATT, Title: RACH reattempt considering beam selection. [cited by applicant]
R2-1802151 3GPP TSG-RAN WG2 #101, Athens, Greece, February 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]
R1-1801454 3GPP TSG RAN WG1 Meeting #92, Athens, Greece, Feb. 26-Mar. 2, 2018, Source: Huawei, HiSilicon, Title: 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-1802393 3GPP TSG RAN WG1 Meeting #92, Athens, Greece, Feb. 26-Mar. 2, 2018, Source: Intel Corporation, Title: On beam management issues for multi-CC operation. [cited by applicant]
R1-1802397 3GPP TSG RAN WG1 Meeting #92, Athens, Greece, Feb. 26-Mar. 2, 2018, Source: Intel Corporation, Title: Remaining Issues on Beam Failure Recovery. [cited by applicant]
R1-1802472 3GPP TSG RAN WG1 Meeting #92, Athens, Greece, Feb. 26-Mar. 2, 2018, Source: NTT DOCOMO, Title: Remaining issues on beam recovery. [cited by applicant]
R1-1802557 3GPP TSG RAN WG1 Meeting #92, Athens, Greece, Feb. 26-Mar. 2, 2018, Source: Nokia, Nokia Shanghai Bell, Title: Remaining Details on Beam Recovery. [cited by applicant]
R1-1802593 3GPP TSG RAN WG1 Meeting #92, Athens, Greece, Feb. 26-Mar. 2, 2018, Source: AT&T, Title: In support of partial beam failure. [cited by applicant]
R1-1802744 3GPP TSG RAN WG1 Meeting #92, Athens, Greece, Feb. 26-Mar. 2, 2018, Source: Ericsson, Title: Remaining details on beam 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-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-1803397 3GPP TSG RAN WG1 Meeting #92, Athens, Greece, Feb. 26-Mar. 2, 2018, Source: CATT, Title: Summary of Email Discussion on Beam Failure Recovery on Scell. [cited by applicant]
R1-1803745 3GPP TSG-RAN WG1 Meeting #92bis, Sanya, China, Apr. 16-20, 2018, Source: CATT, Title: Remaining Details on Beam Failure Recovery. [cited by applicant]
R1-1804210 3GPP TSG-RAN WG1 Meeting #92bis, Sanya, China, Apr. 16-20, 2018, Source: Lenovo, Motorola Mobility, Title: Discussion of Beam Measurement for Carrier Aggregation. [cited by applicant]
R1-1804363 3GPP TSG-RAN WG1 Meeting #92bis, Sanya, China, Apr. 16-20, 2018, Source: Samsung, Title: Simultaneous Reception of Physical Channels and Reference Signals. [cited by applicant]
R1-1804789 3GPP TSG-RAN WG1 Meeting #92bis, Sanya, China, Apr. 16-20, 2018, Source: Qualcomm Incorporated, Title: Details on Simultaneous Reception/Transmission of PHY Channels and RS in FR2. [cited by applicant]
R1-1804975 3GPP TSG-RAN WG1 Meeting #92bis, Sanya, China, Apr. 16-20, 2018, Source: Ericsson, Title: Remaining Issues on Beam Recovery. [cited by applicant]
R1-1804977 3GPP TSG-RAN WG1 Meeting #92bis, Sanya, China, Apr. 16-20, 2018, Source: Ericsson, Title: On Simultaneous Reception of Physical and Reference Signals Across CCs. [cited by applicant]
R1-1805538 3GPP TSG-RAN WG1 Meeting #92bis, Sanya, China, Apr. 16-20, 2018, Source: NTT DOCOMO, Inc., Title: Offline Summary for AI 7.1.3.1.2 Search Space. [cited by applicant]
R1-1806616 3GPP TSG-RAN WG1 #93, Busan, Korea, May 21-25, 2018, Source: LG Electronics, Title: Remaining Issues on Search Space. [cited by applicant]
R1-1806729 3GPP TSG-RAN WG1 #93, Busan, Korea, May 21-25, 2018, Source: Samsung, Title: Corrections on Search Space Design. [cited by applicant]
R2-1707999 3GPP TSG-RAN WG2 #99, Berlin, Germany, Aug. 21-25, 2017, Source: MediaTek Inc., Title: Beam Management and Beam Recovery in MAC. [cited by applicant]
R2-1708677 3GPP TSG RAN WG2 #99, Berlin, Germany, Aug. 21-25, 2017, Source: Nokia, Nokia Shanghai Bell, Title: Beam Recovery in NR. [cited by applicant]
R2-1708697 3GPP TSG RAN WG2 #99, Berlin, Germany, Aug. 21-25, 2017, Source: Huawei, HiSilicon, Title: Handling of Resources for Beam Failure Recovery. [cited by applicant]
R2-1709085 3GPP TSG-RAN WG2 #99, Berlin, Germany, Aug. 21-25, 2017, Source: Qualcomm Incorporated, Title: Beam Recovery Request. [cited by applicant]
R2-1709320 3GPP TSG-RAN WG2 #99, Berlin, Germany, Aug. 21-25, 2017, Source: ASUSTek, Title: Discussion on Beam Recover Request in NR. [cited by applicant]
R2-1800042 3GPP TSG-RAN WG2 AH, Vancouver, Canada, Jan. 22-26, 2018, Source: ASUSTek, Title: Discussion on Beam Failure Recovery Request in NR. [cited by applicant]
R2-1800049 3GPP TSG-RAN WG2 AH, Vancouver, Canada, Jan. 22-26, 2018, Source: ASUSTek, Title: UE Behaviours Upon Beam Failure and Recovery. [cited by applicant]
R2-1800168 3GPP TSG-RAN WG2 AH, Vancouver, Canada, Jan. 22-26, 2018, Source: CATT, Title: Solution for PH Type Inconsistency Between RAN1 and RAN2. [cited by applicant]
R2-1800169 3GPP TSG-RAN WG2 AH, Vancouver, Canada, Jan. 22-26, 2018, Source: CATT, Title: PHR MAC CE for EN-DC. [cited by applicant]
R2-1800231 3GPP TSG-RAN WG2 #100, Reno, USA, Nov. 27-Dec. 1, 2017, Source: Xiaomi, Title: Consideration on PHR Trigger Condition for Supporting SUL. [cited by applicant]
R2-1800253 3GPP TSG-RAN WG2 AH, Vancouver, Canada, Jan. 22-26, 2018, Source: ASUSTek, Title: Pathloss Change for Triggering PHR. [cited by applicant]
R2-1800254 3GPP TSG-RAN WG2 AH, Vancouver, Canada, Jan. 22-26, 2018, Source: CATT, Title: RA Procedure and Parameters for BFR. [cited by applicant]
R2-1800343 3GPP TSG-RAN WG2 AH, Vancouver, Canada, Jan. 22-26, 2018, Source: Ericsson, Title: PHR Format for SUL. [cited by applicant]
R2-1800614 3GPP TSG-RAN WG2 AH, Vancouver, Canada, Jan. 22-26, 2018, Source: Samsung, Title: Support for Type 2 PH in NR. [cited by applicant]
R2-1800619 3GPP TSG-RAN WG2 AH, Vancouver, Canada, Jan. 22-26, 2018, Source: Samsung, Title: SUL and PHR. [cited by applicant]
R2-1800642 3GPP TSG-RAN WG2 AH, Vancouver, Canada, Jan. 22-26, 2018, Source: Huawei, HiSilicon, Title: PHR Alignment Between RAN1 and RAN2. [cited by applicant]
R2-1800680 3GPP TSG-RAN WG2 AH, Vancouver, Canada, Jan. 22-26, 2018, Source: Lenovo, Motorola Mobility, Title: PHR for NR CA. [cited by applicant]
R2-1800822 3GPP TSG-RAN WG2 AH, Vancouver, Canada, Jan. 22-26, 2018, Source: Spreadtrum Communications, Title: Beam Failure Recovery Clarification. [cited by applicant]
R2-1801008 3GPP TSG-RAN WG2 AH, Vancouver, Canada, Jan. 22-26, 2018, Source: Huawei, HiSilicon, Title: Discussion on Power Sharing and its Impact on PHR for EN-DC. [cited by applicant]
R2-1801009 3GPP TSG-RAN WG2 AH, Vancouver, Canada, Jan. 22-26, 2018, Source: Huawei, HiSilicon, Title: General Consideration on RA Procedure for Beam Failure Recovery. [cited by applicant]
R2-1801041 3GPP TSG-RAN WG2 AH, Vancouver, Canada, Jan. 22-26, 2018, Source: Huawei, HiSilicon, Title: Remaining Issue of Power Management in NR. [cited by applicant]
R2-1801043 3GPP TSG-RAN WG2 AH, Vancouver, Canada, Jan. 22-26, 2018, Source: Huawei, HiSilicon, Title: Consideration of PHR with Multi-Beam Operation. [cited by applicant]
R2-1801404 3GPP TSG-RAN WG2 AH, Vancouver, Canada, Jan. 22-26, 2018, Source: NTT DOCOMO, Inc., Title: Discussion on Beam Failure Recovery. [cited by applicant]
R2-1801406 3GPP TSG-RAN WG2 AH, Vancouver, Canada, Jan. 22-26, 2018, Source: NTT DOCOMO, Inc., Title: Remaining Issue on PHR. [cited by applicant]
R2-1801539 3GPP TSG-RAN WG2 AH, Vancouver, Canada, Jan. 22-26, 2018, Source: CATT, Title: PHR MAC CE for EN-DC. [cited by applicant]
R2-1801540 3GPP TSG-RAN WG2 AH, Vancouver, Canada, Jan. 22-26, 2018, Source: CATT, Title: Correction on PHR MAC CE in EN-DC in TS38.321. [cited by applicant]
R2-1801564 3GPP TSG-RAN WG2 AH, Vancouver, Canada, Jan. 22-26, 2018, Source: NTT DOCOMO, Inc., Title: LS on PHR. [cited by applicant]
R2-1801568 3GPP TSG-RAN WG2 AH, Vancouver, Canada, Jan. 22-26, 2018, Source: Ran WG2, Title: LS on PHR. [cited by applicant]
R2-1801814 3GPP TSG-RAN WG2 #101, Athens, Greece, Feb. 26-Mar. 2, 2018, Source: Huawei, HiSilicon, Title: Beam Failure Recovery on SCell. [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-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—Extended 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-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 Incorporated, Title: Beam recovery procedure. [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 Dormant 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]
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-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-1810063 3GPP TSG RAN WG2 AH-1807, Montreal, Canada, Jul. 2-6, 2018, Source: Ericsson, Title: Dormant SCell state in NR. [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-1810424 3GPP TSG RAN WG2 AH-1807, Montreal, Canada, Jul. 2-6, 2018, Source: Qualcomm Inc., Title: BFD procedure in DRX mode. [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]
R2-1814198 3GPP TSG RAN WG2 Meeting #103bis, Chengdu, China, Oct. 8-12, 2018, Source: vivo, Title: Clarification on the beam change during BFR. [cited by applicant]
RP-181344 3GPP TSG RAN Meeting #80, La Jolla, USA, Jun. 11-14, 2018, Source: Ericsson, Nokia, Nokia Shanghai Bell, Huawei, Title: New WID on MR-DC enhancements (NR_MRDC_Enh). [cited by applicant]