IP Library › Granted Patent US 12,696,336
Granted Patent B2
US 12,696,336 · App. 18/584,574 · Granted Jul 28, 2026

Transmission power control for beam failure recovery requests

Inventors: Hua Zhou (Vienna, VA); Esmael Hejazi Dinan (McLean, VA); Alireza Babaei (Fairfax, VA); Hyoungsuk Jeon (Centreville, VA); Kyungmin Park (Vienna, VA)
Assignee: Bloomsbury Design Labs LLC
H04W76/18H04B7/06964H04B17/103H04L5/0051H04W52/146H04W52/42H04W52/50H04W74/0833H04L5/005H04W52/242
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,696,336
App. No.
18/584,574
Filed
Feb 22, 2024
Granted
Jul 28, 2026
Kind
B2
Art Unit
2465
USPC
370/329
Abstract

Systems, apparatuses, and methods are described for wireless communications. A base station may transmit indications of target received powers for a random access procedure and a beam failure recovery procedure. A wireless device may transmit a random access preamble and a beam failure recovery preamble using different transmission powers based on the indications of target received powers.

Claims (78)

1 . A method comprising:

receiving, by a wireless device, at least one configuration parameter for pathloss associated with a preamble transmission via a cell, wherein the at least one configuration parameter is associated with a candidate signal; and

transmitting, via a random access channel and using a transmission power that is based on the at least one configuration parameter for pathloss, a preamble for beam failure recovery associated with the cell.

2 . The method of claim 1 , wherein the at least one configuration parameter indicates a reference signal power associated with the candidate signal.

3 . The method of claim 2 , further comprising determining, based on a difference between the reference signal power and a filtered reference signal received power (RSRP), a pathloss value.

4 . The method of claim 1 , further comprising determining, based on a pathloss value, the transmission power,

wherein the pathloss value is based on a difference between a reference signal power associated with the candidate signal and a filtered reference signal received power (RSRP).

5 . The method of claim 1 , wherein the candidate signal comprises a synchronization signal block corresponding to a candidate beam.

6 . The method of claim 1 , wherein the candidate signal is associated with the random access channel for transmission of the preamble.

7 . The method of claim 1 , further comprising:

receiving at least one message indicating a plurality of candidate reference signals for beam failure recovery associated with the cell, wherein each candidate reference signal of the plurality of candidate reference signals corresponds to a respective preamble of a plurality of preambles, and

wherein the candidate signal is a selected candidate reference signal, of the plurality of candidate reference signals, corresponding to the transmitted preamble for beam failure recovery.

8 . A method comprising:

transmitting, by a base station, at least one configuration parameter for pathloss associated with a preamble transmission via a cell, wherein the at least one configuration parameter is associated with a candidate signal; and

receiving, via a random access channel, a preamble for beam failure recovery associated with the cell, wherein a transmission power for the preamble for beam failure recovery is associated with the at least one configuration parameter.

9 . The method of claim 8 , wherein the at least one configuration parameter indicates a reference signal power associated with the candidate signal.

10 . The method of claim 9 , wherein the pathloss is based on a difference between the reference signal power and a filtered reference signal received power (RSRP).

11 . The method of claim 8 , wherein the transmission power is based on the pathloss.

12 . The method of claim 8 , wherein the candidate signal comprises a synchronization signal block corresponding to a candidate beam.

13 . The method of claim 8 , wherein the candidate signal is associated with the random access channel for transmission of the preamble.

14 . The method of claim 8 , further comprising:

transmitting at least one message indicating a plurality of candidate reference signals for beam failure recovery associated with the cell, wherein each candidate reference signal of the plurality of candidate reference signals corresponds to a respective preamble of a plurality of preambles, and

wherein the candidate signal is a selected candidate reference signal, of the plurality of candidate reference signals, corresponding to the received preamble for beam failure recovery.

15 . A wireless device comprising:

one or more processors; and

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

receive at least one configuration parameter for pathloss associated with a preamble transmission via a cell, wherein the at least one configuration parameter is associated with a candidate signal; and

transmit, via a random access channel and using a transmission power that is based on the at least one configuration parameter for pathloss, a preamble for beam failure recovery associated with the cell.

16 . The wireless device of claim 15 , wherein the at least one configuration parameter indicates a reference signal power associated with the candidate signal.

17 . The wireless device of claim 16 , wherein the instructions, when executed by the one or more processors, configure the wireless device to determine, based on a difference between the reference signal power and a filtered reference signal received power (RSRP), a pathloss value.

18 . The wireless device of claim 15 , wherein the instructions, when executed by the one or more processors, configure the wireless device to determine, based on a pathloss value, the transmission power, and

wherein the pathloss value is based on a difference between a reference signal power associated with the candidate signal and a filtered reference signal received power (RSRP).

19 . The wireless device of claim 15 , wherein the candidate signal comprises a synchronization signal block corresponding to a candidate beam.

20 . The wireless device of claim 15 , wherein the candidate signal is associated with the random access channel for transmission of the preamble.

21 . The wireless device of claim 15 , wherein the instructions, when executed by the one or more processors, configure the wireless device to:

receive at least one message indicating a plurality of candidate reference signals for beam failure recovery associated with the cell, wherein each candidate reference signal of the plurality of candidate reference signals corresponds to a respective preamble of a plurality of preambles, and

wherein the candidate signal is a selected candidate reference signal, of the plurality of candidate reference signals, corresponding to the transmitted preamble for beam failure recovery.

22 . A base station comprising:

one or more processors; and

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

transmit at least one configuration parameter for pathloss associated with a preamble transmission via a cell, wherein the at least one configuration parameter is associated with a candidate signal; and

receive, via a random access channel, a preamble for beam failure recovery associated with the cell, wherein a transmission power for the preamble for beam failure recovery is associated with the at least one configuration parameter.

23 . The base station of claim 22 , wherein the at least one configuration parameter indicates a reference signal power associated with the candidate signal.

24 . The base station of claim 23 , wherein the pathloss is based on a difference between the reference signal power and a filtered reference signal received power (RSRP).

25 . The base station of claim 22 , wherein the transmission power is based on the pathloss.

26 . The base station of claim 22 , wherein the candidate signal comprises a synchronization signal block corresponding to a candidate beam.

27 . The base station of claim 22 , wherein the candidate signal is associated with the random access channel for transmission of the preamble.

28 . The base station of claim 22 , wherein the instructions, when executed by the one or more processors, configure the base station to:

transmit at least one message indicating a plurality of candidate reference signals for beam failure recovery associated with the cell, wherein each candidate reference signal of the plurality of candidate reference signals corresponds to a respective preamble of a plurality of preambles, and

wherein the candidate signal is a selected candidate reference signal, of the plurality of candidate reference signals, corresponding to the received preamble for beam failure recovery.

29 . A non-transitory computer-readable medium storing instructions that, when executed, configure a wireless device to:

receive at least one configuration parameter for pathloss associated with a preamble transmission via a cell, wherein the at least one configuration parameter is associated with a candidate signal; and

transmit, via a random access channel and using a transmission power that is based on the at least one configuration parameter for pathloss, a preamble for beam failure recovery associated with the cell.

30 . The non-transitory computer-readable medium of claim 29 , wherein the at least one configuration parameter indicates a reference signal power associated with the candidate signal, and

wherein the candidate signal is associated with the random access channel for transmission of the preamble.

31 . The non-transitory computer-readable medium of claim 29 , wherein the instructions, when executed, configure the wireless device to determine, based on a pathloss value, the transmission power, and

wherein the pathloss value is based on a difference between a reference signal power associated with the candidate signal and a filtered reference signal received power (RSRP).

32 . A non-transitory computer-readable medium storing instructions that, when executed, configure a base station to:

transmit at least one configuration parameter for pathloss associated with a preamble transmission via a cell, wherein the at least one configuration parameter is associated with a candidate signal; and

receive, via a random access channel, a preamble for beam failure recovery associated with the cell, wherein a transmission power for the preamble for beam failure recovery is associated with the at least one configuration parameter.

33 . The non-transitory computer-readable medium of claim 32 , wherein the at least one configuration parameter indicates a reference signal power associated with the candidate signal, and

wherein the candidate signal is associated with the random access channel for transmission of the preamble.

34 . The non-transitory computer-readable medium of claim 33 , wherein the pathloss is based on a difference between the reference signal power and a filtered reference signal received power (RSRP), and

wherein the transmission power is based on the pathloss.

35 . A system comprising:

a wireless device; and

a base station,

wherein the base station is configured to:

transmit at least one configuration parameter for pathloss associated with a preamble transmission via a cell, wherein the at least one configuration parameter is associated with a candidate signal, and

wherein the wireless device is configured to:

transmit, via a random access channel and using a transmission power that is based on the at least one configuration parameter for pathloss, a preamble for beam failure recovery associated with the cell.

36 . The system of claim 35 , wherein the at least one configuration parameter indicates a reference signal power associated with the candidate signal, and

wherein the candidate signal is associated with the random access channel for transmission of the preamble.

37 . The system of claim 36 , wherein the pathloss is based on a difference between the reference signal power and a filtered reference signal received power (RSRP), and

wherein the transmission power is based on the pathloss.

38 . The system of claim 35 , wherein the base station is configured to:

transmit at least one message indicating a plurality of candidate reference signals for beam failure recovery associated with the cell, wherein each candidate reference signal of the plurality of candidate reference signals corresponds to a respective preamble of a plurality of preambles, and

wherein the candidate signal is a selected candidate reference signal, of the plurality of candidate reference signals, corresponding to the preamble for beam failure recovery.

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 Oct 2, 2024
From: ZHOU, HUA; DINAN, ESMAEL HEJAZI; BABAEI, ALIREZA; JEON, HYOUNGSUK; PARK, KYUNGMIN
To: COMCAST CABLE COMMUNICATIONS, LLC
Reel/Frame 068761/0770 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 2, 2024
From: ZHOU, HUA; DINAN, ESMAEL HEJAZI; BABAEI, ALIREZA; JEON, HYOUNGSUK; PARK, KYUNGMIN
To: COMCAST CABLE COMMUNICATIONS, LLC
Reel/Frame 068761/0794 →
Continuity (5)
Continuation 17860594 · Jul 8, 2022
Continuation 17107426 · Nov 30, 2020
Continuation 16101283 · Aug 10, 2018
Provisional Application 62543821 · Aug 10, 2017
Related Publication 20240284536A1 · Aug 22, 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 20110216741A1 · Yang et al. · 2011 [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 · Mn 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]
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-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, 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]
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, November 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]
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-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]