IP Library › Granted Patent US 12,587,434
Granted Patent B2
US 12,587,434 · App. 17/592,188 · Granted Mar 24, 2026

Downlink control information for multiple beam procedure types

Inventors: Hua Zhou (Herndon, VA); Esmael Hejazi Dinan (Herndon, VA); Hyoungsuk Jeon (Centreville, VA); Kyungmin Park (Vienna, VA); Alireza Babaei (Fairfax, VA)
Assignee: Comcast Cable Communications, LLC
H04L41/0654H04L5/0048H04W24/02H04W72/046H04W72/23H04W76/19H04W76/27H04L5/0091H04W16/28H04W74/0833
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,587,434
App. No.
17/592,188
Granted
Mar 24, 2026
Kind
B2
Abstract

Systems, apparatuses, and methods are described for wireless communications. A base station may transmit downlink control information that may comprise an indication of a beam procedure type of a plurality of beam procedure types. A wireless device may receive the downlink control information and determine a type of procedure to perform based on the indication.

Claims (160)

1 . A method comprising:

receiving, by a wireless device, downlink control information (DCI) comprising:

an indication of one or more beams; and

an indication of one beam procedure type, of a plurality of beam procedure types, to be performed via the one or more beams, wherein the plurality of beam procedure types comprise:

a first beam procedure type in which the wireless device transmits one or more uplink signals based on the one or more beams; and

a second beam procedure type in which the wireless device receives one or more downlink signals based on the one or more beams; and

performing, based on the indication of the one beam procedure type, a beam procedure of the one beam procedure type via the one or more beams.

2 . The method of claim 1 , further comprising:

transmitting an uplink signal associated with the first beam procedure type of the plurality of beam procedure types; and

after the receiving the DCI:

stopping monitoring one or more downlink control channels for DCI associated with the first beam procedure type; and

continuing monitoring one or more downlink control channels for DCI associated with the second beam procedure type of the plurality of beam procedure types.

3 . The method of claim 1 , wherein:

the one beam procedure type of the plurality of beam procedure types is a downlink beam failure recovery procedure; and

the performing the beam procedure comprises transmitting, after one or more beam failures and based on one or more parameters for the downlink beam failure recovery procedure, at least one of:

a beam failure recovery request; or

an uplink signal responsive to the DCI.

4 . The method of claim 1 , wherein:

the one beam procedure type of the plurality of beam procedure types is an uplink beam management procedure; and

the performing the beam procedure comprises transmitting, based on one or more parameters for the uplink beam management procedure and after receiving second DCI indicating sounding reference signal transmission, one or more sounding reference signals for uplink beam management.

5 . The method of claim 1 , further comprising determining, based on the indication of the one beam procedure type, that the DCI comprises one or more of:

a sounding reference signal resource index; or

a channel state information reference signal resource index.

6 . The method of claim 1 , wherein:

the one beam procedure type of the plurality of beam procedure types is a downlink beam management procedure; and

a beam procedure type field, of the DCI, indicates that one or more beam information fields, of the DCI, comprises one or more beam parameters for the downlink beam management procedure.

7 . The method of claim 1 , wherein the performing the beam procedure comprises:

determining, based on one or more beam information fields of the DCI, one or more adjusted receiving beams, wherein a beam procedure type field, of the DCI, indicates that the one or more beam information fields comprises one or more beam parameters for a downlink beam failure recovery procedure.

8 . The method of claim 1 , wherein the performing the beam procedure comprises:

determining, based on one or more beam information fields of the DCI, one or more adjusted transmitting beams, wherein a beam procedure type field, of the DCI, indicates that the one or more beam information fields comprises one or more beam parameters for an uplink beam management procedure.

9 . The method of claim 1 , further comprising receiving one or more parameters, for a downlink beam failure recovery procedure, comprising one or more of:

first reference signal (RS) resource parameters of a first plurality of reference signals (RSs);

second RS resource parameters of a second plurality of RSs; or

random access channel resources.

10 . The method of claim 1 , further comprising receiving one or more parameters, for an uplink beam management procedure, comprising one or more of:

a bandwidth of a sounding reference signal (SRS);

a numerology of the SRS;

a frequency resource of the SRS; or

a time resource of the SRS.

11 . The method of claim 1 , wherein the DCI comprises one or more beam information fields, wherein the one or more beam information fields comprises at least one of:

a first bits field indicating a first reference signal (RS) index associated with one or more reference signals; or

a second bits field indicating a second RS index associated with one or more of an RS or a synchronization block.

12 . The method of claim 1 , wherein the indication of the one beam procedure type indicates:

a downlink beam failure recovery procedure;

a downlink beam management procedure; or

an uplink beam management procedure.

13 . The method of claim 1 , wherein the indication of the one beam procedure type indicates:

a first type uplink beam management procedure comprising at least one beam sweeping associated with the wireless device and with a base station;

a second type uplink beam management procedure comprising a reception (Rx) beam sweeping associated with the base station; or

a third type uplink beam management procedure comprising a transmission (Tx) beam sweeping associated with the wireless device.

14 . The method of claim 1 , further comprising:

transmitting beam reporting information associated with a quality of one or more downlink reference signals,

wherein the DCI is associated with the beam reporting information, and

wherein the indication of the one beam procedure type indicates a downlink beam management procedure.

15 . The method of claim 1 , wherein the indication of the one beam procedure type indicates that one or more beam information fields, of the DCI, comprises one or more beam parameters for the one beam procedure type.

16 . The method of claim 15 , wherein the one or more beam parameters for the one beam procedure type comprises at least one of:

one or more synchronization signal (SS) blocks;

one or more channel state information reference signals (CSI-RSs);

one or more quasi co-location (QCL) parameters;

a measurement setting; or

a reporting setting.

17 . The method of claim 15 , wherein the one or more beam parameters for the one beam procedure type comprises at least one of:

one or more sounding reference signal (SRS) configurations;

one or more quasi co-location (QCL) parameters; or

an SRS power control command.

18 . A method comprising:

transmitting, by a base station, downlink control information (DCI) comprising:

an indication of one or more beams; and

an indication of one beam procedure type, of a plurality of beam procedure types, to be performed via the one or more beams, wherein the plurality of beam procedure types comprise:

a first beam procedure type in which a wireless device transmits one or more uplink signals based on the one or more beams; and

a second beam procedure type in which the wireless device receives one or more downlink signals based on the one or more beams; and

performing, based on the indication of the one beam procedure type, a beam procedure of the one beam procedure type associated with the one or more beams.

19 . The method of claim 18 , wherein:

the one beam procedure type of the plurality of beam procedure types is a downlink beam failure recovery procedure; and

the performing the beam procedure comprises receiving, after one or more beam failures and based on one or more parameters for the downlink beam failure recovery procedure, at least one of:

a beam failure recovery request; or

an uplink signal responsive to the DCI.

20 . The method of claim 18 , wherein:

the one beam procedure type of the plurality of beam procedure types is an uplink beam management procedure; and

the performing the beam procedure comprises receiving, based on one or more parameters for the uplink beam management procedure and after transmitting second DCI indicating sounding reference signal transmission, one or more sounding reference signals for uplink beam management.

21 . The method of claim 18 , wherein the DCI comprises one or more of:

a sounding reference signal resource index; or

a channel state information reference signal resource index.

22 . The method of claim 18 , wherein:

the one beam procedure type of the plurality of beam procedure types is a downlink beam management procedure; and

a beam procedure type field, of the DCI, indicates that one or more beam information fields, of the DCI, comprises one or more beam parameters for the downlink beam management procedure.

23 . The method of claim 18 , wherein a beam procedure type field, of the DCI, indicates that one or more beam information fields comprises at least one of:

one or more beam parameters for a downlink beam failure recovery procedure;

one or more beam parameters for a downlink beam management procedure; or

one or more beam parameters for an uplink beam management procedure.

24 . The method of claim 18 , wherein the DCI comprises one or more beam information fields, wherein the one or more beam information fields comprises at least one of:

a first bits field indicating a first reference signal (RS) index associated with one or more reference signals; or

a second bits field indicating a second RS index associated with one or more of an RS or a synchronization block.

25 . The method of claim 18 , wherein the indication of the one beam procedure type indicates:

a downlink beam failure recovery procedure;

a downlink beam management procedure; or

an uplink beam management procedure.

26 . The method of claim 18 , wherein the indication of the one beam procedure type indicates:

a first type uplink beam management procedure comprising at least one beam sweeping associated with the wireless device and with the base station;

a second type uplink beam management procedure comprising a reception (Rx) beam sweeping associated with the base station; or

a third type uplink beam management procedure comprising a transmission (Tx) beam sweeping associated with the wireless device.

27 . The method of claim 18 , further comprising:

receiving beam reporting information associated with a quality of one or more downlink reference signals,

wherein the DCI is associated with the beam reporting information, and

wherein the indication of the one beam procedure type indicates a downlink beam management procedure.

28 . The method of claim 18 , wherein the indication of the one beam procedure type indicates that one or more beam information fields, of the DCI, comprises one or more beam parameters for the one beam procedure type.

29 . The method of claim 28 , wherein the one or more beam parameters for the one beam procedure type comprises at least one of:

one or more synchronization signal (SS) blocks;

one or more channel state information reference signals (CSI-RSs);

one or more quasi co-location (QCL) parameters;

a measurement setting; or

a reporting setting.

30 . The method of claim 28 , wherein the one or more beam parameters for the one beam procedure type comprises at least one of:

one or more sounding reference signal (SRS) configurations;

one or more quasi co-location (QCL) parameters; or

an SRS power control command.

31 . 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 downlink control information (DCI) comprising:

an indication of one or more beams; and

an indication of one beam procedure type, of a plurality of beam procedure types, to be performed via the one or more beams, wherein the plurality of beam procedure types comprise:

a first beam procedure type in which the wireless device transmits one or more uplink signals based on the one or more beams; and

a second beam procedure type in which the wireless device receives one or more downlink signals based on the one or more beams; and

perform, based on the indication of the one beam procedure type, a beam procedure of the one beam procedure type via the one or more beams.

32 . The wireless device of claim 31 , wherein the indication of the one beam procedure type indicates:

a downlink beam failure recovery procedure;

a downlink beam management procedure; or

an uplink beam management procedure.

33 . The wireless device of claim 31 , wherein the indication of the one beam procedure type indicates:

a first type uplink beam management procedure comprising at least one beam sweeping associated with the wireless device and with a base station;

a second type uplink beam management procedure comprising a reception (Rx) beam sweeping associated with the base station; or

a third type uplink beam management procedure comprising a transmission (Tx) beam sweeping associated with the wireless device.

34 . The wireless device of claim 31 , wherein the instructions, when executed by the one or more processors, cause the wireless device to:

transmit beam reporting information associated with a quality of one or more downlink reference signals,

wherein the DCI is associated with the beam reporting information, and

wherein the indication of the one beam procedure type indicates a downlink beam management procedure.

35 . The wireless device of claim 31 , wherein the indication of the one beam procedure type indicates that one or more beam information fields, of the DCI, comprises one or more beam parameters for the one beam procedure type.

36 . 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 downlink control information (DCI) comprising:

an indication of one or more beams; and

an indication of one beam procedure type, of a plurality of beam procedure types, to be performed via the one or more beams, wherein the plurality of beam procedure types comprise:

a first beam procedure type in which a wireless device transmits one or more uplink signals based on the one or more beams; and

a second beam procedure type in which the wireless device receives one or more downlink signals based on the one or more beams; and

perform, based on the indication of the one beam procedure type, a beam procedure of the one beam procedure type associated with the one or more beams.

37 . The base station of claim 36 , wherein the indication of the one beam procedure type indicates:

a downlink beam failure recovery procedure;

a downlink beam management procedure; or

an uplink beam management procedure.

38 . The base station of claim 36 , wherein the indication of the one beam procedure type indicates:

a first type uplink beam management procedure comprising at least one beam sweeping associated with the wireless device and with the base station;

a second type uplink beam management procedure comprising a reception (Rx) beam sweeping associated with the base station; or

a third type uplink beam management procedure comprising a transmission (Tx) beam sweeping associated with the wireless device.

39 . The base station of claim 36 , wherein the instructions, when executed by the one or more processors, cause the base station to:

receive beam reporting information associated with a quality of one or more downlink reference signals,

wherein the DCI is associated with the beam reporting information, and

wherein the indication of the one beam procedure type indicates a downlink beam management procedure.

40 . The base station of claim 36 , wherein the indication of the one beam procedure type indicates that one or more beam information fields, of the DCI, comprises one or more beam parameters for the one beam procedure type.

Assignments (2)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 22, 2023
From: ZHOU, HUA; DINAN, ESMAEL HEJAZI; JEON, HYOUNGSUK; PARK, KYUNGMIN; BABAEI, ALIREZA
To: COMCAST CABLE COMMUNICATIONS, LLC
Reel/Frame 063061/0632 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 22, 2023
From: ZHOU, HUA; DINAN, ESMAEL; JEON, HYOUNGSUK; PARK, KYUNGMIN; BABAEI, ALIREZA
To: COMCAST CABLE COMMUNICATIONS, LLC
Reel/Frame 063061/0609 →
Continuity (3)
Continuation 16125434 · Sep 7, 2018
Provisional Application 62555352 · Sep 7, 2017
Related Publication 20220158891A1 · May 19, 2022
References Cited (400)
US 9125218B2 · Chang · 2015 [cited by applicant]
US 9515802B2 · Seo · 2016 [cited by examiner]
US 9736795B2 · Dinan · 2017 [cited by applicant]
US 9949298B1 · Akoum et al. · 2018 [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 20130231011A1 · Sytsma et al. · 2013 [cited by applicant]
US 20130250828A1 · Chou et al. · 2013 [cited by applicant]
US 20140177607A1 · Li et al. · 2014 [cited by applicant]
US 20140204856A1 · Chen et al. · 2014 [cited by applicant]
US 20150189574A1 · Ng et al. · 2015 [cited by applicant]
US 20150208462A1 · Lee et al. · 2015 [cited by applicant]
US 20150288497A1 · Li et al. · 2015 [cited by applicant]
US 20150365921A1 · Wu · 2015 [cited by applicant]
US 20160242159A1 · Ho et al. · 2016 [cited by applicant]
US 20170195998A1 · Zhang et al. · 2017 [cited by applicant]
US 20170207843A1 · Jung · 2017 [cited by examiner]
US 20170332406A1 · Islam et al. · 2017 [cited by applicant]
US 20170339662A1 · Lin et al. · 2017 [cited by applicant]
US 20170367114A1 · Ahn 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 20180041319A1 · Cheng et al. · 2018 [cited by applicant]
US 20180049055A1 · Wiberg 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 20180062724A1 · Onggosanusi et al. · 2018 [cited by applicant]
US 20180083753A1 · Nagaraja et al. · 2018 [cited by applicant]
US 20180098334A1 · Tie et al. · 2018 [cited by applicant]
US 20180110066A1 · Luo et al. · 2018 [cited by applicant]
US 20180115940A1 · Abedini et al. · 2018 [cited by applicant]
US 20180115990A1 · Abedini et al. · 2018 [cited by applicant]
US 20180124687A1 · Park et al. · 2018 [cited by applicant]
US 20180132266A1 · Chen et al. · 2018 [cited by applicant]
US 20180138962A1 · Islam et al. · 2018 [cited by applicant]
US 20180176958A1 · Islam et al. · 2018 [cited by applicant]
US 20180191422A1 · Xia et al. · 2018 [cited by applicant]
US 20180219604A1 · Lu et al. · 2018 [cited by applicant]
US 20180220448A1 · Akkarakaran et al. · 2018 [cited by applicant]
US 20180227899A1 · Yu et al. · 2018 [cited by applicant]
US 20180234960A1 · Nagaraja et al. · 2018 [cited by applicant]
US 20180241452A1 · Akkarakaran et al. · 2018 [cited by applicant]
US 20180249453A1 · Nagaraja et al. · 2018 [cited by applicant]
US 20180254863A1 · Choi · 2018 [cited by examiner]
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 20180288756A1 · Xia et al. · 2018 [cited by applicant]
US 20180302889A1 · Guo et al. · 2018 [cited by applicant]
US 20180310321A1 · Basu Mallick et al. · 2018 [cited by applicant]
US 20180317123A1 · Chen et al. · 2018 [cited by applicant]
US 20180323856A1 · Xiong et al. · 2018 [cited by applicant]
US 20180324723A1 · Akkarakaran et al. · 2018 [cited by applicant]
US 20180324867A1 · Basu Mallick et al. · 2018 [cited by applicant]
US 20180343653A1 · Guo · 2018 [cited by applicant]
US 20180351611A1 · Nagaraja et al. · 2018 [cited by applicant]
US 20180367374A1 · Liu et al. · 2018 [cited by applicant]
US 20180368126A1 · Islam et al. · 2018 [cited by applicant]
US 20180368142A1 · Liou · 2018 [cited by applicant]
US 20190028174A1 · Chakraborty et al. · 2019 [cited by applicant]
US 20190037423A1 · Yu et al. · 2019 [cited by applicant]
US 20190037498A1 · Tseng et al. · 2019 [cited by applicant]
US 20190059129A1 · Luo et al. · 2019 [cited by applicant]
US 20190074882A1 · Zhou 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 20220158891A1 · Zhou · 2022 [cited by examiner]
CN 108809580A · 2018 [cited by applicant]
EP 3397015A1 · 2018 [cited by applicant]
EP 3424152A1 · 2019 [cited by applicant]
EP 4535712A2 · 2025 [cited by examiner]
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 WO2018088902A1 · 2018 [cited by examiner]
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 mutli-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-1802554 3GPP TSG-RAN WG2 #101, Athens, Greece, Feb. 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: Media Tek Inc., Title: On Parallel SR and RACH Procedure in NR. [cited by applicant]
R1-170xxxx 3GPP TSG RAN WG1 Meeting #88b, Spokane, USA, Apr. 3-7, 2017, Source: Huawei, HiSilicon, Title: WF on Beam Failure Recovery. [cited by applicant]
R1-171xxxx 3GPP TSG RAN WG1 Meeting #90, Prague, Czech Republic, Aug. 21-25, 2017, Source: MediaTek Inc. Title: Offline Discussion on Beam Recovery Mechanism. [cited by applicant]
R1-1704230 3GPP TSG RAN WG1 Meeting #88b, Spokane, USA, Apr. 3-7, 2017, Source: Huawei, HiSilicon, Title: Link recovery procedure for beam failure. [cited by applicant]
3GPP TS 36.212 V14.3.0 (Jun. 2017); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Multiplexing and … [cited by applicant]
3GPP TSG RAN WG1 Meeting #90, Prague, Czech Republic, Aug. 21-25, 2017, Title: RAN1 Chairman's Notes. [cited by applicant]
R1-1705719 3GPP TSG RAN WG1 Meeting #88bis, Spokane, USA, Apr. 3-7, 2017, Source: NTT Docomo, Inc., Title: Further views on mechanism to recover from beam failure. [cited by applicant]
R1-1711016 3GPP TSG RAN WG1 #89AH-NR, Qingdao, China, Jun. 27-30, 2017, Source: Ericsson, Title: UL beam management details. [cited by applicant]
R1-1712223 3GPP TSG RAN WG1 Meeting #90, Prague, Czech Republic, Aug. 21-25, 2017, Source: Huawei, HiSilicon, Title: UL beam management. [cited by applicant]
R1-1712224 3GPP TSG RAN WG1 Meeting #90, Prague, Czech Republic, Aug. 21-25, 2017, Source: Huawei, HiSilicon, Title: Procedure details for beam failure recovery. [cited by applicant]
R1-1712268 3GPP TSG RAN WG1 Meeting #90, Prague, Czech Republic, Aug. 21-25, 2017, Source: Xinwei, Title: Discussion on beam failure recovery. [cited by applicant]
R1-1712299 3GPP TSG RAN WG1 Meeting #90, Prague, Czech Republic, Aug. 21-25, 2017, Source: ZTE, Title: UL beam management for NR MIMO. [cited by applicant]
R1-1712378 3GPP TSG RAN WG1 Meeting #90, Prague, Czech Republic, Aug. 21-25, 2017, Source: CATT, Title: Considerations on UL beam management. [cited by applicant]
R1-1712379 3GPP TSG RAN WG1 Meeting #90, Prague, Czech Republic, Aug. 21-25, 2017, Source: CATT, Title: Beam failure detection and recovery. [cited by applicant]
R1-1712551 3GPP TSG RAN WG1 Meeting #90, Prague, Czech Republic, Aug. 21-25, 2017, Source: Intel Corporation, Title: Details for UL beam management. [cited by applicant]
R1-1712552 3GPP TSG RAN WG1 Meeting #90, Prague, Czech Republic, Aug. 21-25, 2017, Source: Intel Corporation, Title: Discussion for mechanism to recover from beam failure. [cited by applicant]
R1-1721672 3GPP TSG RAN WG1 Meeting #90, Prague, Czech Republic, Aug. 21-25, 2017, Source: Lenovo, Motorola Mobility, Title: Discussion of beam failure recovery. [cited by applicant]
R1-1712713 3GPP TSG RAN WG1 Meeting #90, Prague, Czech Republic, Aug. 21-25, 2017, Source: AT&T, Title: Mechanisms to recover from beam failure. [cited by applicant]
R1-1712838 3GPP TSG RAN WG1 Meeting #90, Prague, Czech Republic, Aug. 21-25, 2017, Source: Vivo, Title: Discussion on uplink beam management. [cited by applicant]
R1-1712966 3GPP TSG RAN WG1 Meeting #90, Prague, Czech Republic, Aug. 21-25, 2017, Source: Sony, Title: Considerations on UL beam management. [cited by applicant]
R1-1713287 3GPP TSG RAN WG1 Meeting #90, Prague, Czech Republic, Aug. 21-25, 2017, Source: Guangdong OPPO Mobile Telecom, Title: Discussion on the UL beam management. [cited by applicant]
R1-1713596 3GPP TSG RAN WG1 Meeting #90, Prague, Czech Republic, Aug. 21-25, 2017, Source: Samsung, Title: Discussion on UL beam management. [cited by applicant]
R1-1714143 3GPP TSG RAN WG1 Meeting #90, Prague, Czech Republic, Aug. 21-25, 2017, Source: InterDigital, Inc., Title: On efficient UL beam management. [cited by applicant]
R1-1714250 3GPP TSG RAN WG1 Meeting #90, Prague, Czech Republic, Aug. 21-25, 2017, Source: Nokia, Nokia Shanghai Bell, Title: SRS transmission for beam management. [cited by applicant]
R1-1714292 3GPP TSG RAN WG1 Meeting #90, Prague, Czech Republic, Aug. 21-25, 2017, Source: Ericsson, Title: On UL beam management. [cited by applicant]
R1-1714383 3GPP TSG RAN WG1 Meeting #90, Prague, Czech Republic, Aug. 21-25, 2017, Source: ASUSTeK, Title: Considerations on UE Beamforming Management. [cited by applicant]
3GPP TSG RAN WG1 Meeting NR#3, Nagoya, Japan, Sep. 18-21, 2017, Title: RAN1 Chairman's Notes. [cited by applicant]
R1-1715441 3GPP TSG RAN WG1 Meeting NR#3, Nagoya, Japan, Sep. 18-21, 2017, Source: ZTE, Sanechips, Title: Discussion on beam recovery. [cited by applicant]
R1-1715620 3GPP TSG RAN WG1 Meeting NR#3, Nagoya, Japan, Sep. 18-21, 2017, Source: Vivo, Title: Discussion on beam failure recovery procedure. [cited by applicant]
R1-1715802 3GPP TSG RAN WG1 Meeting NR#3, Nagoya, Japan, Sep. 18-21, 2017, Source: CATT, Title: Beam failure detection and recovery. [cited by applicant]
R2-1708696 3GPP TSG RAN WG2 #99, Berlin, Germany, Aug. 21-25, 2017, Source: Huawei, HiSilicon, Title: Consideration on DRX with beam management. [cited by applicant]
R2-1708755 3GPP TSG RAN WG2 #99, Berlin, Germany, Aug. 21-25, 2017, Source: LG Electronics, Title: DRX related timers in NR (Revision of R2-1706750). [cited by applicant]
R2-1708791 3GPP TSG RAN WG2 #99, Berlin, Germany, Aug. 21-25, 2017, Source: Intel Corporation, Title: C-DRX enhancement in NR (Revision of R2-1707026). [cited by applicant]
R2-1709223 3GPP TSG RAN WG2 #99, Berlin, Germany, Aug. 21-25, 2017, Source: Qualcomm Incorporated, Title: Beam management in C-DRX. [cited by applicant]
R2-1709588 3GPP TSG RAN WG2 #99, Berlin, Germany, Aug. 21-25, 2017, Source: Samsung, Title: NR beamformed C-DRX operation (updated resubmission of R2-1705734). [cited by applicant]
R2-1709652 3GPP TSG RAN WG2 #99, Berlin, Germany, Aug. 21-25, 2017, Source: Qualcomm Incorporated, Apple, OPPO, Title: Wake-Up Signaling for C-DRX Mode. [cited by applicant]
R2-1709916 3GPP TSG RAN WG2 #99, Berlin, Germany, Aug. 21-25, 2017, Source: Ericsson, Title: Reply LS to SA2 on 5QIs for URLLC. [cited by applicant]
Aug. 27, 2019—European Extended Search Report—EP 19173892.1. [cited by applicant]
3GPP TSG-RAN WG1 #89: “Beam failure recovery mechanism”, May 15, 2017. [cited by applicant]
3GPP TSG-RAN WG2 Meeting#AH: “Random access procedure for beam recovery request”, Jun. 27, 2017. [cited by applicant]
Sep. 25, 2019—European Extended Search Report—EP 19166863.1. [cited by applicant]
R1-1803368 3GPP TSG RAN WG1 Meeting #92, Athens, Greece, Feb. 26-Mar. 2, 2018, Source: [RAN1], Title: Draft LS reply to RAN2 on beam failure recovery. [cited by applicant]
R1-1803441 3GPP TSG RAN WG1 Meeting #92, Athens, Greece, Feb. 26-Mar. 2, 2018, Source: MediaTek Inc., Title: Summary 2 on Remaing issues on Beam Failure Recovery. [cited by applicant]
R2-1811483 3GPP TSG-RAN WG2 Meeting #103, Gothenburg, Sweden, Aug. 20-24, 2018, Source: ZTE, Sanechips, Title: CR for the reset of BFD in 38.321. [cited by applicant]
R2-1812108 3GPP TSG-RAN WG2 Meeting #103, Gothenburg, Sweden, Aug. 20-24, 2018, Source: Nokia, Nokia Shanghai Bell, Title: Reset of BFD. [cited by applicant]
3GPP TS 38.213 V15.2.0 (Jun. 2018), Technical Specification, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Physical layer procedures for control (Release 15). [cited by applicant]
R2-1806229 3GPP TSG-RAN WG2 Meeting #101bis, Sanya, China, Apr. 16-20, 2018, Source: Samsung, Title: Miscellaneous corrections. [cited by applicant]
R2-1806120 3GPP TSG-RAN WG2 Meeting #101, Sanya, China, Apr. 16-20, 2018, Source: ITL, Title: Beam Failure Recovery on SCell. [cited by applicant]
R2-1806166 3GPP TSG-RAN WG2 Meeting #101, Sanya, China, Apr. 16-20, 2018, Source: MediaTek, Inc., Title: On switching between CFRA and CBRA. [cited by applicant]
R2-1806774 3GPP TSG-RAN WG2 Meeting #102, Sanya, China, Apr. 16-20, 2018, Source: Nokia, Nokia Shanghai Bell, Title: Finalization of dormant SCell state. [cited by applicant]
R2-1806819 3GPP TSG-RAN WG2 Meeting #102, Busan, Korea, May 21-25, 2018, Source: Samsung, Title: MAC Impacts: Beam Failure Recovery for SCell. [cited by applicant]
R2-1806924 3GPP TSG-RAN WG2 Meeting #102, Busan, Korea, May 21-25, 2018, Source: Qualcomm, Inc., Title: SCell Dormant State Transitions based on New Timers & MAC-CEs. [cited by applicant]
R2-1806998 3GPP TSG-RAN WG2 Meeting #102, Busan, Korea, May 21-25, 2018, Source: CATT, Title: The validity of CFRA resources for BFR. [cited by applicant]
R2-1807160 3GPP TSG-RAN WG2 Meeting #102, Busan, Korea, May 21-25, 2018, Source: Panasonic, Title: Timer associated with the dedicated BFR PRACH resource. [cited by applicant]
R2-1807405 3GPP TSG-RAN WG2 Meeting #102, Busan, Korea, May 21-25, 2018, Source: ZTE, Title: Discussion on the beam failure recovery timer. [cited by applicant]
R2-1807415 3GPP TSG-RAN WG2 Meeting #102, Busan, Korea, May 21-25, 2018, Source: OPPO, Title: MAC impacts on supporting BFR procedure on SCell. [cited by applicant]
R2-1807444 3GPP TSG-RAN WG2 Meeting #102, Busan, Korea, May 21-25, 2018, Source: Huawei, HiSilicon, Title: BWP switch for BFR. [cited by applicant]
R2-1807481 3GPP TSG RAN WG2 Meeting #102, Busan, Korea, May 21-25, 2018, Source: Huawei, HiSilicon, Title: Remaining issues of temporary CQI reporting. [cited by applicant]
R2-1807584 3GPP TSG RAN WG2 Meeting #102, Busan, Korea, May 21-25, 2018, Source: vivo, Title: Discussion on the SCell BFR. [cited by applicant]
R2-1807961 3GPP TSG-RAN WG2 Meeting #102, Busan, Korea, May 21-25, 2018, Source: Huawei, HiSilicon, Title: Discussion on BFR-config for SCell BFR. [cited by applicant]
R2-1807975 3GPP TSG-RAN WG2 Meeting #102, Busan, Korea, May 21-25, 2018, Source: Huawei, HiSilicon, Title: Discussion on beam failure recovery for SCell. [cited by applicant]
R2-1808024 3GPP TSG-RAN WG2 Meeting #102, Busan, Korea, May 21-25, 2018, Source: Nokia, Nokia Shanghai Bell, Title: SCell Beam Failure Recovery. [cited by applicant]
R2-1808570 3GPP TSG RAN WG2 Meeting #102, Busan, Korea, May 21-25, 2018, Source: Qualcomm Incorporated, Title: Dormant BWP for fast SCell activation. [cited by applicant]
R2-1808658 3GPP TSG-RAN WG2 Meeting #102, Busan, Korea, May 21-25, 2018, Source: ITL, Title: Beam failure recovery on SCell. [cited by applicant]
R2-1808809 3GPP TSG RAN WG2 Meeting #102, Busan, Korea, May 21-25, 2018, Source: Ericsson, Title: CR on Dormat SCell state transition MAC CE. [cited by applicant]
R2-1809515 3GPP TSG RAN WG2 AH-1807, Montreal, Canada, Jul. 2-6, 2018, Source: CATT, Title: Further issues with DL BWP switching for CFRA. [cited by applicant]
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]
Dec. 16, 2019—European Extended Search Report—EP 19191018.1. [cited by applicant]
Dec. 20, 2019—European Extended Search Report—EP 19199208.0. [cited by applicant]
R2-1811208 3GPP TSG-RAN WG2 Meeting #103, Gothenburg, Sweden, Aug. 20-24, 2018, Source: CATT, Title: UL/DL BWP linkage for PDCCH order initiated CFRA. [cited by applicant]
R1-1807210 3GPP TSG RAN WG1 Meeting #93, Busan, Korea, May 21-25, 2018, Source: ASUSTeK, Title: Remaining issues on beam management. [cited by applicant]
R1-1804788 3GPP TSG RAN WG1 Meeting #92b, Sanya, China, Apr. 16-20, 2018, Source: Qualcomm, Title: Beam failure recovery procedure. [cited by applicant]
Jan. 24, 2020—European Extended Search Report—EP 19199658.6. [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, Sep. 18-21, 2017, Source: Nokia, Nokia Shanghai Bell, Title Beam Recovery in NR. [cited by applicant]
R1-1716469 3GPP TSG RAN WG1 Meeting NR#3, Nagoya, Japan, Sep. 18-21, 2017: Source: InterDigital, Inc., Title: Remaining issues on beam recovery. [cited by applicant]
R1-1717302 3GPP TSG RAN WG1 Meeting #90bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: Huawei, HiSilicon Title: Beam failure recovery design details. [cited by applicant]
R1-1717369 3GPP TSG RAN WG1 Meeting #90bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: Intel Corporation, Title: Remaining Issues on Beam Failure Recovery. [cited by applicant]
R1-1717473 3GPP TSG RAN WG1 Meeting #90bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: vivo, Title: Discussion on beam failure recovery. [cited by applicant]
R1-1717606 3GPP TSG RAN WG1 Meeting #90bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: Samsung, Title: Beam failure recovery. [cited by applicant]
R1-1717942 3GPP TSG RAN WG1 Meeting #90bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: LG Electronics, Title: Discussion on beam failure recovery. [cited by applicant]
R1-1718010 3GPP TSG RAN WG1 Meeting #90bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: NEC, Title: Discussion on Beam Failure Recovery. [cited by applicant]
R1-1718055 3GPP TSG RAN WG1 Meeting #90bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: OPPO, Title: Discussion on Beam Recovery Mechanism. [cited by applicant]
R1-1718193 3GPP TSG RAN WG1 Meeting #90bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: NTT Docomo, Title: Views on beam recovery. [cited by applicant]
R1-1718389 3GPP TSG RAN WG1 Meeting #90bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: AT&T, Title: Beam Recovery for Full and Partial Control Channel Failure. [cited by applicant]
R1-1718512 3GPP TSG RAN WG1 Meeting #90bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: Nokia, Nokia Shanghai Bell, Title: Beam Recovery in NR. [cited by applicant]
R1-1718542 3GPP TSG RAN WG1 Meeting #90bis, Prague Czech Republic, Oct. 9-13, 2017, Source: Qualcomm Incorpated, Title: Beam recovery procedure. [cited by applicant]
R2-1815644 3GPP TSG-RAN WG2 Meeting #103bis, Chengdu, PR China, Oct. 8-12, 2018, Source: Ericsson, Samsung, Title: Correction for Reconfiguration of CFRA during ongoing RA. [cited by applicant]
R2-1811325 3GPP TSG-RAN WG2 Meeting #103, Gothenburg, Sweden, Aug. 20-24, 2018, Source: Samsung Electronics, Title: Handling Beam Failure Recovery Configuration Update. [cited by applicant]
3GPP TS 38.321 V15.2.0 (Jun. 2018), Technical Specification, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Medium Access Control (MAC) protocol specification (Release 15). [cited by applicant]
R2-1811149 3GPP TSG-RAN WG2 Meeting #103, Gothenburg, Sweden, Aug. 20-24, 2018, Source: OPPO, Title: CR on beam failure recovery configuration. [cited by applicant]
R2-1811593 3GPP TSG-RAN WG2 Meeting #103, Gothenburg, Sweden, Aug. 20-24, 2018, Source: ZTE Corporation, Sanechips, Title: CR for the configuration of BeamFailureRecoveryConfig. [cited by applicant]
3GPP TS 38.331 V15.2.1 (Jun. 2018), Technical Specification, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Radio Resource Control (RRC) protocol specification (Release 15). [cited by applicant]
R1-180XXXX 3GPP TSG-RAN WG1 Meeting #94, Gothenburg, Sweden, Aug. 20-24, 2018, Source: Ericsson, Title: Feature lead summary beam management v2. [cited by applicant]
R2-1804763 3GPP TSG-RAN WG2 Meeting #101bis, Sanya, China, Apr. 16-20, 2018, Source: Nokia, Nokia Shanghai Bell, Title: Running MAC CR for euCA. [cited by applicant]
R1-180XXXX 3GPP TSG-RAN WG1 Meeting #94, Gothenburg, Sweden, Aug. 20-24, 2018, Source: Ntt Docomo, Inc., Title: Offline summary for PDCCH structure and search space. [cited by applicant]
R1-180XXXX 3GPP TSG-RAN WG1 Meeting #94, Gothenburg, Sweden, Aug. 20-24, 2018, Source: MediaTek Inc., Title: Summary #1 on Remaining Issues on Beam Failure Recovery. [cited by applicant]
R1-1712153 3GPP TSG RAN WG1 Meeting #90, Prague, Czech Republic, Aug. 21-25, 2017, Source: Huawei, HiSilicon, Title: Overview of bandwidth part. [cited by applicant]
R1-1713204 3GPP TSG RAN WG1 Meeting #90, Prague, Czech Republic, Aug. 21-25, 2017, Source: LG Electronics, Title: Further remaining details on wider bandwidth operation. [cited by applicant]
R1-1713978 3GPP TSG RAN WG1 Meeting #90, Prague, Czech Republic, Aug. 21-25, 2017, Source: MediaTek Inc., Title: Further Details on Bandwidth Part Operation in NR. [cited by applicant]
R1-1719650 3GPP TSG RAN WG1 Meeting #91, Reno, USA, Nov. 27-Dec. 1, 2017, Source: AT&T, Title: Remaining details on bandwidth parts. [cited by applicant]
R1-1719651 3GPP TSG RAN WG1 Meeting #91, Reno, USA, Nov. 27-Dec. 1, 2017, Source: AT&T, Title: Remaining details on carrier aggregation. [cited by applicant]
R1-1721027 3GPP TSG RAN WG1 Meeting #91, Reno, USA, Nov. 27-Dec. 1, 2017, Source: Ericsson, Title: On Carrier aggregation related aspects. [cited by applicant]
R1-1800879 3GPP TSG RAN WG1 NR Ad Hoc, Vancouver, Canada, Jan. 22-26, 2018, Source: Qualcomm Incorporated, Title: Remaining Issues on BWP. [cited by applicant]
R1-1803622 3GPP TSG RAN WG1 Meeting #92, Sanya, China, Apr. 16-20, 2018, Source: NEC, Title: Remaining Issues on beam failure recovery. [cited by applicant]
R1-1804211 3GPP TSG-RAN WG1 Meeting #92bis, Sanya, China, Apr. 16-20, 2018, Source: Lenovo, Motorola Mobility, Title: Discussion of beam failure recovery for Carrier Aggregation. [cited by applicant]
R1-1806281 3GPP TSG-RAN WG1 #93, Busan, Korea, May 21-25, 2018, Source: CATT, Title: Remaining issues on beam failure recovery. [cited by applicant]
R1-1806508 3GPP TSG-RAN WG1 #93, Busan, Korea, May 21-25, 2018, Source: Intel Corporation, Title: Remaining Issues on beam failure recovery. [cited by applicant]
R1-1806789 3GPP TSG-RAN WG1 #93, Busan, Korea, May 21-25, 2018, Source: MediaTek Inc., Title: Remaining Issues on beam failure recovery. [cited by applicant]
R1-1807796 3GPP TSG-RAN WG1 #93, Busan, Korea, May 21-25, 2018, Source: MediaTek Inc., Title: Summary 2 on Remaining issues on beam failure recovery. [cited by applicant]
R1-1808720 3GPP TSG-RAN WG1 Meeting #94, Gothenburg, Sweden, Aug. 20-24, 2018, Source: Intel Corporation, Title: On SCell Beam Failure Recovery. [cited by applicant]
R1-1810020 3GPP TSG-RAN WG1 Meeting #94, Gothenburg, Sweden, Aug. 20-24, 2018, Source: Samsung, Title: CR to 38.213 capturing the RAN1#94 meeting agreements. [cited by applicant]
R2-1713170 3GPP TSG RAN WG2 Meeting #100, Reno, USA, Nov. 27-Dec. 1, 2017, Source: Nokia (rapporteur), Title: Report of [99bis#32][LTE/euCA] Faster activation for Scells (Nokia). [cited by applicant]
R2-1714289 3GPP TSG RAN WG2 Meeting #100, Reno, USA, Nov. 27-Dec. 1, 2017, Source: Nokia, Nokia Shanghai Bell, Title: Running CR for euCA Stage-2. [cited by applicant]
R2-1800866 3GPP TSG-RAN WG2 AH, Vancouver, Canada, Jan. 22-26, 2018, Source: vivo, Title: RACH configuration for beam recovery. [cited by applicant]
R2-1800895 3GPP TSG-RAN WG2 AH, Vancouver, Canada, Jan. 22-26, 2018, Source: vivo, Title: Discussion on the impact on beam failure recovery. [cited by applicant]
R2-1801432 3GPP TSG RAN WG2 NR Ad Hoc, Vancouver, Canada, Jan. 22-26, 2018, Source: Qualcomm Incorporated, Title: Dormant BWP for fast SCell activation. [cited by applicant]
R2-1801926 3GPP TSG-RAN WG2 #101, Athens, Greece, Feb. 26-Mar. 2, 2018, Source: ZTE, Sanechips, Title: Remaining considerations on RACH procedure for BFR. [cited by applicant]
R2-1802143 3GPP TSG-RAN WG2 #101, Athens, Greece, Feb. 26-Mar. 2, 2018, Source: CATT, Title: RACH reattempt considering beam selection. [cited by applicant]
R2-1802151 3GPP TSG-RAN WG2 #101, Athens, Greece, Feb. 26-Mar. 2, 2018, Source: CATT, Title: Beam failure recovery. [cited by applicant]
R2-1802756 3GPP TSG RAN WG2 Meeting #101, Athens, Greece, Feb. 26-Mar. 2, 2018, Source: Nokia, Nokia Shanghai Bell, Title: Remaining details on temporary CQI reporting during activation. [cited by applicant]
R2-1803229 3GPP TSG-RAN WG2 #101, Athens, Greece, Feb. 26-Mar. 2, 2018, Source: Nokia, Nokia Shanghai Bell, Title: BWP switch interaction with contention free BFR preamble. [cited by applicant]
R2-1803564 3GPP TSG RAN WG2 Meeting #101, Athens, Greece, Feb. 26-Mar. 2, 2018, Source: Qualcomm Incorporated, Title: Dormant BWP for fast SCell activation. [cited by applicant]
R2-1804279 3GPP TSG-RAN WG2 Meeting #101, Sanya, China, Apr. 16-20, 2018, Source: ASUSTeK, Title: UE behaviours upon beam failure and recovery. [cited by applicant]
R2-1804303 3GPP TSG-RAN WG2 Meeting #101, Sanya, China, Apr. 16-20, 2018, Source: Samsung, Title: MAC Impacts: Beam Failure Recovery for SCell. [cited by applicant]
R2-1804407 3GPP TSG-RAN WG2 Meeting #101, Sanya, China, Apr. 16-20, 2018, Source: ZTE, Sanechips, Title: Consideration on beam failure recovery for SCell. [cited by applicant]
R2-1804410 3GPP TSG-RAN WG2 Meeting #101, Sanya, China, Apr. 16-20, 2018, Source: Huawei, HiSilicon, Title: Beam failure recovery using MAC CE. [cited by applicant]
R2-1804411 3GPP TSG-RAN WG2 Meeting #101, Sanya, China, Apr. 16-20, 2018, Source: Huawei, HiSilicon, Title: BWP issues for BFR. [cited by applicant]
R2-1804434 3GPP TSG-RAN WG2 Meeting #101, Sanya, China, Apr. 16-20, 2018, Source: OPPO, Title: Issues on supporting SCell Bfr Rach. [cited by applicant]
R2-1804481 3GPP TSG-RAN WG2 Meeting #101, Sanya, China, Apr. 16-20, 2018, Source: CATT, Title: Leftover ssues for BFR. [cited by applicant]
R2-1804482 3GPP TSG-RAN WG2 Meeting #101, Sanya, China, Apr. 16-20, 2018, Source: CATT, Title: BFR configurations and fallback options. [cited by applicant]
R2-1804483 3GPP TSG-RAN WG2 Meeting #101, Sanya, China, Apr. 16-20, 2018, Source: CATT, Title: BFR on SCell. [cited by applicant]
R2-1804696 3GPP TSG-RAN WG2 Meeting #101, Sanya, China, Apr. 16-20, 2018, Source: vivo, Title: Discussion on the SCell BFR. [cited by applicant]
R2-1805204 3GPP TSG-RAN WG2 Meeting #101, Sanya, China, Apr. 16-20, 2018, Source: Lenovo, Motorola Mobility, Title: Dedicated PRACH resource for beam failure recovery. [cited by applicant]
R2-1805414 3GPP TSG-RAN WG2 Meeting #101, Sanya, China, Apr. 16-20, 2018, Source: Ericsson, Title: Beam Failure Recovery in SCell and contention-based BFR on SpCell. [cited by applicant]
R2-1805896 3GPP TSG-RAN WG2 Meeting #101, Sanya, China, Apr. 16-20, 2018, Source: Huawei, HiSilicon, Title: ASN.1 for Beam Failure Recovery. [cited by applicant]
R2-1805905 3GPP TSG-RAN WG2 Meeting #101, Sanya, China, Apr. 16-20, 2018, Source: Huawei, HiSilicon, Title: Discussions on RA for SCells BFR. [cited by applicant]
R2-1707001 3GPP TSG-RAN WG2 Meeting #AH, Qingdao, China, Jun. 27-29, 2017, Source: Lenovo, Motorola Mobility, Title: Random access procedure for beam recovery request. [cited by applicant]
R1-17111617 3GPP TSG-RAN WG1 NR AH#2, Qingdao, China, Jun. 27-30, 2017, Source: CATT, Title: RACH power control and power ramping procedure (revision of R1-1710034). [cited by applicant]
R1-1711161 3GPP TSG RAN WG1 NR#2, Qingdao, China, Jun. 27-30, 2017, Source: Qualcomm Incorporated, Title: Beam recovery procedures. [cited by applicant]
International Search Report and Written Opinion for PCT/US2018/046368 mailing date Dec. 13, 2018. [cited by applicant]
Apr. 15, 2019—Extented European Search Report—EP 19150964.5. [cited by applicant]
R1-1708678 3GPP TSG-RAN WG1 #89, Hangzhou, China, May 15-19, 2017, Source: Ericsson, Title: Beam failure recovery mechanism. [cited by applicant]
May 22, 2019—Extended European Search Report—19156175.2. [cited by applicant]
R2-1800560 3GPP TSG-RAN WG2 NR, Vancouver, Canada, Jan. 22-26, 2018, Source: Sharp, Title: Remaining issues on beam failure recovery. [cited by applicant]
R2-1800632 3GPP TSG-RAN WG2 AH, Vancouver, Canada, Jan. 22-26, 2018, Source: Huawei, HiSilicon, Title: Remaining issue for beam failure recovery. [cited by applicant]
R2-1801049 3GPP TSG-RAN WG2 AH, Vancouver, Canada, Jan. 22-26, 2018, Source: Huawei, HiSilicon, Title: Non-contention based random access for beam failure recovery in CA. [cited by applicant]
3GPP TS 38.321 V15.0.0 (Dec. 2017); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Medium Access Control (MAC) protocol specification (Release 15). [cited by applicant]
3GPP TS 38.213 V15.0.1 (Feb. 2018); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Physical layer procedures for control (Release 15). [cited by applicant]
R2-1804475 3GPP TSG-RAN WG2 Meeting #101bis, Sanya, China, Apr. 16-20, 2018, Source: Spreadtrum Communications, Title: Beam Failure recovery on SCell. [cited by applicant]
May 14, 2019—European Extended Search Report—19157460.7. [cited by applicant]
R2-1710562 3GPP TSG-RAN WG2 #99bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: Huawei, HiSilicon, Title: RAN2 aspects of DL beam management (revision of R2-1708695). [cited by applicant]
3GPP TS 36.211 V14.3.0 (Jun. 2017); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels… [cited by applicant]
3GPP TS 36.213 V14.3.0 (Jun. 2017); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer pr… [cited by applicant]
3GPP TS 36.321 V.14.3.0 (Jun. 2017); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Co… [cited by applicant]