IP Library › Granted Patent US 12,659,877
Granted Patent B2
US 12,659,877 · App. 17/859,805 · Granted Jun 16, 2026

Beam failure report

Inventors: Hyoungsuk Jeon (Centreville, VA); Esmael Hejazi Dinan (McLean, VA); Kyungmin Park (Vienna, VA); Hua Zhou (Vienna, VA); Ali Cagatay Cirik (Chantilly, VA); Alireza Babaei (Fairfax, VA)
Assignee: Ofinno, LLC
H04W52/365H04B7/0626H04B7/06964H04L1/0061H04L5/0048H04L25/0226H04W16/28H04W72/046H04W72/0466H04W72/0473H04W72/23H04W76/11H04W76/19H04W80/02H04B7/0413
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,659,877
App. No.
17/859,805
Granted
Jun 16, 2026
Kind
B2
Abstract

Systems, apparatuses, and methods are described for wireless communications. A wireless device configured to communicate via beams of one or more cells may report a beam failure using a media access control (MAC) control element (CE). The MAC CE may also be used to report other information for one or more cells with which the wireless device is associated. Beam failure reporting with a MAC CE may be combined with other beam failure procedures.

Claims (144)

1 . A method comprising:

receiving, by a wireless device from a base station, one or more messages comprising configuration parameters of a plurality of secondary cells (SCells);

determining, by the wireless device, a beam failure of a first SCell of the plurality of SCells; and

transmitting, by the wireless device, a medium access control (MAC) control element (CE) for reporting the beam failure of the first SCell, wherein:

the MAC CE comprises a plurality of fields;

each field of the plurality of fields indicates presence or absence of a respective octet, within the MAC CE, for a respective SCell of the plurality of SCells;

the respective octet of which presence or absence is indicated by each field comprises a respective field comprising respective one or more reserved bits for indicating information related to a beam failure of the respective SCell;

the plurality of fields comprises a first field indicating presence of a first octet, within the MAC CE, for the first SCell; and

the first octet of which presence or absence is indicated by the first field comprises a second field comprising one or more reserved bits for indicating information related to the beam failure of the first SCell.

2 . The method of claim 1 , wherein the MAC CE is associated with at least one of:

reporting beam failure;

a beam failure indication;

a power backoff;

a real transmission;

a reference format;

a power headroom report (PHR); or

a transmit power.

3 . The method of claim 1 , wherein:

the transmitting the MAC CE comprises transmitting the MAC CE via a second cell; and

the second cell is different from the plurality of SCells.

4 . The method of claim 1 , further comprising receiving at least one message comprising beam configuration parameters, wherein the beam configuration parameters indicate at least one of:

configuration of at least one reference signal for beam failure recovery;

a first threshold for beam failure recovery;

a second threshold for beam failure recovery;

at least one uplink channel resource for beam failure recovery; or

association between each of the at least one uplink channel resource and the at least one reference signal.

5 . The method of claim 1 , wherein the first SCell is configured as a downlink-only cell for the wireless device.

6 . The method of claim 1 , wherein:

the one or more messages further comprise configuration parameters for a beam failure recovery procedure; and

the beam failure recovery procedure comprises:

detecting a beam failure; and

determining a candidate beam identified by a channel state information (CSI) reference signal (RS) resource index or a synchronization signal (SS) block index.

7 . The method of claim 6 , wherein the information related to the beam failure of the first SCell is determined based on the beam failure recovery procedure.

8 . The method of claim 6 , further comprising performing the beam failure recovery procedure in response to no candidate beam being identified.

9 . The method of claim 1 , further comprising triggering a multiplexing and assembly procedure to generate the MAC CE indicating the beam failure detected on the first SCell.

10 . The method of claim 1 , wherein the MAC CE further comprises a second field indicates a beam failure of a primary cell.

11 . A method comprising:

transmitting, by a base station to a wireless device, one or more messages comprising configuration parameters of a plurality of secondary cells (SCells); and

receiving, from the wireless device, a medium access control (MAC) control element (CE) for reporting a beam failure of a first SCell of the plurality of SCells, wherein:

the MAC CE comprises a plurality of fields;

each field of the plurality of fields indicates presence or absence of a respective octet, within the MAC CE, for a respective SCell of the plurality of SCells;

the respective octet of which presence or absence is indicated by each field comprises a respective field comprising respective one or more reserved bits for indicating information related to a beam failure of the respective SCell;

the plurality of fields comprises a first field indicating presence of a first octet, within the MAC CE, for the first SCell; and

the first octet of which presence or absence is indicated by the first field comprises a second field comprising one or more reserved bits for indicating information related to the beam failure of the first SCell.

12 . The method of claim 11 , wherein the MAC CE is associated with at least one of:

reporting beam failure;

a beam failure indication;

a power backoff;

a real transmission;

a reference format;

a power headroom report (PHR); or

a transmit power.

13 . The method of claim 11 , wherein:

the receiving the MAC CE comprises receiving the MAC CE via a second cell; and

the second cell is different from the plurality of SCells.

14 . The method of claim 11 , further comprising transmitting at least one message comprising beam configuration parameters, wherein the beam configuration parameters indicate at least one of:

configuration of at least one reference signal for beam failure recovery;

a first threshold for beam failure recovery;

a second threshold for beam failure recovery;

at least one uplink channel resource for beam failure recovery; or

association between each of the at least one uplink channel resource and the at least one reference signal.

15 . The method of claim 11 , wherein the first SCell is configured as a downlink-only cell for the wireless device that transmits the MAC CE.

16 . The method of claim 11 , wherein:

the one or more messages further comprise configuration parameters for a beam failure recovery procedure; and

the beam failure recovery procedure comprises:

detecting a beam failure; and

determining a candidate beam identified by a channel state information (CSI) reference signal (RS) resource index or a synchronization signal (SS) block index.

17 . The method of claim 16 , wherein the information related to the beam failure of the first SCell is determined based on the beam failure recovery procedure.

18 . The method of claim 16 , wherein the beam failure recovery procedure is performed by the wireless device in response to no candidate beam being identified.

19 . The method of claim 11 , wherein the MAC CE further comprises a second field indicates a beam failure of a primary cell.

20 . The method of claim 11 , wherein the MAC CE further comprises a second field indicates a beam failure of a primary cell.

21 . 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, from a base station, one or more messages comprising configuration parameters of a plurality of secondary cells (SCells);

determine a beam failure of a first SCell of the plurality of SCells; and

transmit a medium access control (MAC) control element (CE) for reporting the beam failure of the first SCell, wherein:

the MAC CE comprises a plurality of fields;

each field of the plurality of fields indicates presence or absence of a respective octet, within the MAC CE, for a respective SCell of the plurality of SCells;

the respective octet of which presence or absence is indicated by each field comprises a respective field comprising respective one or more reserved bits for indicating information related to a beam failure of the respective SCell;

the plurality of fields comprises a first field indicating presence of a first octet, within the MAC CE, for the first SCell; and

the first octet of which presence or absence is indicated by the first field comprises a second field comprising one or more reserved bits for indicating information related to the beam failure of the first SCell.

22 . The wireless device of claim 21 , wherein the MAC CE is associated with at least one of:

reporting beam failure;

a beam failure indication;

a power backoff;

a real transmission;

a reference format;

a power headroom report (PHR); or

a transmit power.

23 . The wireless device of claim 21 , wherein:

the instructions, when executed by the one or more processors, cause the wireless device to transmit the MAC CE by transmitting the MAC CE via a second cell; and

the second cell is different from the plurality of SCells.

24 . The wireless device of claim 21 , wherein the instructions, when executed by the one or more processors, cause the wireless device to receive at least one message comprising beam configuration parameters, wherein the beam configuration parameters indicate at least one of:

configuration of at least one reference signal for beam failure recovery;

a first threshold for beam failure recovery;

a second threshold for beam failure recovery;

at least one uplink channel resource for beam failure recovery; or

association between each of the at least one uplink channel resource and the at least one reference signal.

25 . The wireless device of claim 21 , wherein the first SCell is configured as a downlink-only cell for the wireless device.

26 . The wireless device of claim 21 , wherein:

the one or more messages further comprise configuration parameters for a beam failure recovery procedure; and

the beam failure recovery procedure comprises:

detecting a beam failure; and

determining a candidate beam identified by a channel state information (CSI) reference signal (RS) resource index or a synchronization signal (SS) block index.

27 . The wireless device of claim 26 , wherein the information related to the beam failure of the first SCell is determined based on the beam failure recovery procedure.

28 . The wireless device of claim 26 , wherein the instructions further cause the wireless device to perform the beam failure recovery procedure in response to no candidate beam being identified.

29 . The wireless device of claim 21 , wherein the instructions further cause the wireless device to trigger a multiplexing and assembly procedure to generate the MAC CE indicating the beam failure detected on the first SCell.

30 . The wireless device of claim 21 , wherein the MAC CE further comprises a second field indicates a beam failure of a primary cell.

31 . 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, to a wireless device, one or more messages comprising configuration parameters of a plurality of secondary cells (SCells); and

receive, from the wireless device, a medium access control (MAC) control element (CE) for reporting a beam failure of a first SCell of the plurality of SCells, wherein:

the MAC CE comprises a plurality of fields;

each field of the plurality of fields indicates presence or absence of a respective octet, within the MAC CE, for a respective SCell of the plurality of SCells;

the respective octet of which presence or absence is indicated by each field comprises a respective field comprising respective one or more reserved bits for indicating information related to a beam failure of the respective SCell;

the plurality of fields comprises a first field indicating presence of a first octet, within the MAC CE, for the first SCell; and

the first octet of which presence or absence is indicated by the first field comprises a second field comprising one or more reserved bits for indicating information related to the beam failure of the first SCell.

32 . The base station of claim 31 , wherein the MAC CE is associated with at least one of:

reporting beam failure;

a beam failure indication;

a power backoff;

a real transmission;

a reference format;

a power headroom report (PHR); or

a transmit power.

33 . The base station of claim 31 , wherein:

the instructions, when executed by the one or more processors, cause the base station to receive the MAC CE by receiving the MAC CE via a second cell; and

the second cell is different from the plurality of SCells.

34 . The base station of claim 31 , wherein the instructions, when executed by the one or more processors, cause the base station to transmit at least one message comprising beam configuration parameters, wherein the beam configuration parameters indicate at least one of:

configuration of at least one reference signal for beam failure recovery;

a first threshold for beam failure recovery;

a second threshold for beam failure recovery;

at least one uplink channel resource for beam failure recovery; or

association between each of the at least one uplink channel resource and the at least one reference signal.

35 . The base station of claim 31 , wherein the first SCell is configured as a downlink-only cell for the wireless device that transmits the MAC CE.

36 . The base station of claim 31 , wherein:

the one or more messages further comprise configuration parameters for a beam failure recovery procedure; and

the beam failure recovery procedure comprises:

detecting a beam failure; and

determining a candidate beam identified by a channel state information (CSI) reference signal (RS) resource index or a synchronization signal (SS) block index.

37 . The base station of claim 36 , wherein the information related to the beam failure of the first SCell is determined based on the beam failure recovery procedure.

38 . The base station of claim 36 , wherein the beam failure recovery procedure is performed by the wireless device in response to no candidate beam being identified.

Assignments (3)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 19, 2024
From: COMCAST CABLE COMMUNICATIONS, LLC
To: OFINNO, LLC
Reel/Frame 069743/0577 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 1, 2024
From: JEON, HYOUNGSUK; DINAN, ESMAEL HEJAZI; PARK, KYUNGMIN; ZHOU, HUA; CIRIK, ALI CAGATAY; BABAEI, ALIREZA
To: COMCAST CABLE COMMUNICATIONS, LLC
Reel/Frame 067888/0244 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 1, 2024
From: JEON, HYOUNGSUK; DINAN, ESMAEL HEJAZI; PARK, KYUNGMIN; ZHOU, HUA; CIRIK, ALI CAGATAY; BABAEI, ALIREZA
To: COMCAST CABLE COMMUNICATIONS, LLC
Reel/Frame 067888/0249 →
Continuity (3)
Continuation 16277400 · Feb 15, 2019
Provisional Application 62631332 · Feb 15, 2018
Related Publication 20220361117A1 · Nov 10, 2022
References Cited (400)
US 9125218B2 · Chang · 2015 [cited by applicant]
US 9736795B2 · Dinan · 2017 [cited by applicant]
US 9949298B1 · Akoum et al. · 2018 [cited by applicant]
US 11050478B2 · Guo et al. · 2021 [cited by applicant]
US 11457493B2 · Harada · 2022 [cited by examiner]
US 20100279700A1 · Kim et al. · 2010 [cited by applicant]
US 20130039345A1 · Kim et al. · 2013 [cited by applicant]
US 20130188580A1 · Dinan · 2013 [cited by applicant]
US 20130250828A1 · Chou et al. · 2013 [cited by applicant]
US 20150189574A1 · Ng et al. · 2015 [cited by applicant]
US 20150208462A1 · Lee et al. · 2015 [cited by applicant]
US 20150365921A1 · Wu · 2015 [cited by applicant]
US 20160270007A1 · Dinan · 2016 [cited by examiner]
US 20160270094A1 · Dinan · 2016 [cited by examiner]
US 20160308713A1 · Yi · 2016 [cited by examiner]
US 20160309424A1 · Dinan · 2016 [cited by examiner]
US 20170195998A1 · Zhang et al. · 2017 [cited by applicant]
US 20170207843A1 · Jung · 2017 [cited by examiner]
US 20170302355A1 · Islam · 2017 [cited by examiner]
US 20170332406A1 · Islam et al. · 2017 [cited by applicant]
US 20170339662A1 · Lin et al. · 2017 [cited by applicant]
US 20170373731A1 · Guo et al. · 2017 [cited by applicant]
US 20180006770A1 · Guo et al. · 2018 [cited by applicant]
US 20180054348A1 · Luo et al. · 2018 [cited by applicant]
US 20180054382A1 · Luo et al. · 2018 [cited by applicant]
US 20180054783A1 · Luo et al. · 2018 [cited by applicant]
US 20180054811A1 · Luo et al. · 2018 [cited by applicant]
US 20180054812A1 · Luo et al. · 2018 [cited by applicant]
US 20180054832A1 · Luo et al. · 2018 [cited by applicant]
US 20180083753A1 · Nagaraja et al. · 2018 [cited by applicant]
US 20180098334A1 · Tie et al. · 2018 [cited by applicant]
US 20180110066A1 · Luo et al. · 2018 [cited by applicant]
US 20180115940A1 · Abedini et al. · 2018 [cited by applicant]
US 20180115990A1 · Abedini et al. · 2018 [cited by applicant]
US 20180124687A1 · Park et al. · 2018 [cited by applicant]
US 20180132266A1 · Chen et al. · 2018 [cited by applicant]
US 20180138962A1 · Islam et al. · 2018 [cited by applicant]
US 20180176958A1 · Islam et al. · 2018 [cited by applicant]
US 20180191422A1 · Xia et al. · 2018 [cited by applicant]
US 20180192371A1 · Jung · 2018 [cited by examiner]
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 20180262999A1 · Yi · 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 20180279262A1 · Babaei · 2018 [cited by examiner]
US 20180279318A1 · Wang · 2018 [cited by examiner]
US 20180288756A1 · Xia et al. · 2018 [cited by applicant]
US 20180302889A1 · Guo · 2018 [cited by examiner]
US 20180310321A1 · Basu Mallick et al. · 2018 [cited by applicant]
US 20180317123A1 · Chen · 2018 [cited by examiner]
US 20180323856A1 · Xiong et al. · 2018 [cited by applicant]
US 20180324723A1 · Akkarakaran et al. · 2018 [cited by applicant]
US 20180324867A1 · Basu Mallick · 2018 [cited by examiner]
US 20180343653A1 · Guo · 2018 [cited by applicant]
US 20180351611A1 · Nagaraja et al. · 2018 [cited by applicant]
US 20180367374A1 · Liu · 2018 [cited by examiner]
US 20180368009A1 · Xia · 2018 [cited by examiner]
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 20190052339A1 · Zhou · 2019 [cited by examiner]
US 20190053294A1 · Xia et al. · 2019 [cited by applicant]
US 20190053313A1 · Zhou · 2019 [cited by examiner]
US 20190059129A1 · Luo et al. · 2019 [cited by applicant]
US 20190074882A1 · Zhou et al. · 2019 [cited by applicant]
US 20190081675A1 · Jung · 2019 [cited by examiner]
US 20190081689A1 · Yu et al. · 2019 [cited by applicant]
US 20190081691A1 · Nagaraja · 2019 [cited by examiner]
US 20190089447A1 · Sang · 2019 [cited by examiner]
US 20190089579A1 · Sang · 2019 [cited by examiner]
US 20190141546A1 · Zhou · 2019 [cited by examiner]
US 20190141592A1 · Park et al. · 2019 [cited by applicant]
US 20190173740A1 · Zhang et al. · 2019 [cited by applicant]
US 20190182870A1 · Shih · 2019 [cited by examiner]
US 20190190582A1 · Guo et al. · 2019 [cited by applicant]
US 20190200248A1 · Basu Mallick · 2019 [cited by examiner]
US 20190207667A1 · Zhou · 2019 [cited by examiner]
US 20190208436A1 · Zhou · 2019 [cited by examiner]
US 20190208548A1 · Shih · 2019 [cited by examiner]
US 20190215136A1 · Zhou · 2019 [cited by examiner]
US 20190215896A1 · Zhou et al. · 2019 [cited by applicant]
US 20190230529A1 · Sadiq · 2019 [cited by examiner]
US 20190245737A1 · Zhou · 2019 [cited by examiner]
US 20190261288A1 · Loehr · 2019 [cited by examiner]
US 20190268893A1 · Tsai et al. · 2019 [cited by applicant]
US 20190349915A1 · Ahn · 2019 [cited by examiner]
US 20190349960A1 · Li · 2019 [cited by examiner]
US 20200059398A1 · Pan et al. · 2020 [cited by applicant]
US 20200099437A1 · Harada · 2020 [cited by examiner]
US 20200127883A1 · Liu et al. · 2020 [cited by applicant]
US 20200153542A1 · Zhou · 2020 [cited by examiner]
US 20200213034A1 · Zhou · 2020 [cited by examiner]
US 20200280359A1 · Jung · 2020 [cited by examiner]
US 20200322035A1 · Shi · 2020 [cited by examiner]
US 20200344723A1 · Babaei · 2020 [cited by examiner]
US 20200344834A1 · Harada et al. · 2020 [cited by applicant]
US 20200374960A1 · Deenoo · 2020 [cited by examiner]
US 20210068162A1 · Agiwal · 2021 [cited by examiner]
US 20240163048A1 · Zhou et al. · 2024 [cited by applicant]
CN 108809580A · 2018 [cited by applicant]
EP 3397015A1 · 2018 [cited by applicant]
EP 3424152A1 · 2019 [cited by applicant]
WO 2013025142A1 · 2013 [cited by applicant]
WO 2016127403A1 · 2016 [cited by applicant]
WO 2017024516A1 · 2017 [cited by applicant]
WO 2017123060A1 · 2017 [cited by applicant]
WO 2017123079A1 · 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 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]
R1-1719423 3GPP TSG RAN WG1 Meeting #91, Reno, USA, Nov. 27-Dec. 1, 2017, Source: Huawei, HiSilicon, Title: Remaining details on beam failure recovery. [cited by applicant]
R1-1719619 3GPP TSG RAN WG1 Meeting #91, Reno, USA, Nov. 27-Dec. 1, 2017, Source: Fujitsu, Title: Discussion on beam failure recovery. [cited by applicant]
R1-1719633 3GPP TSG RAN WG1 Meeting #91, Reno, USA, Nov. 27-Dec. 1, 2017, Source: AT&T, Title: Remaining Details on Mechanisms to Recover from Beam Failure. [cited by applicant]
R1-1719695 3GPP TSG RAN WG1 Meeting #91, Reno, USA, Nov. 27-Dec. 1, 2017, Source: Spreadtrum Communications, Title: Remaining issues on beam failure recovery mechanism. [cited by applicant]
R1-1719770 3GPP TSG RAN WG1 Meeting #91, Reno, USA, Nov. 27-Dec. 1, 2017, Source: vivo, Title: Remaining details on mechanism to recover from beam failure. [cited by applicant]
R1-1719809 3GPP TSG RAN WG1 Meeting #91, Reno, USA, Nov. 27-Dec. 1, 2017, Source: Huawei, HiSilicon, Title: Design of PUCCH-based Beam Failure Recovery. [cited by applicant]
R1-1719908 3GPP TSG RAN WG1 Meeting #91, Reno, USA, Nov. 27-Dec. 1, 2017, Source: LG Electronics, Title: Discussion on beam failure recovery. [cited by applicant]
R1-1719988 3GPP TSG RAN WG1 Meeting #91, Reno, USA, Nov. 27-Dec. 1, 2017, Source: Discussion on Beam Recovery Mechanism. [cited by applicant]
R1-1720072 3GPP TSG RAN WG1 Meeting #91, Reno, USA, Nov. 27-Dec. 1, 2017, Source: Intel Corporation, Title: Remaining Issues on Beam Failure Recovery. [cited by applicant]
R1-1720291 3GPP TSG RAN WG1 Meeting #91, Reno, USA, Nov. 27-Dec. 1, 2017, Source Samsung, Title: Beam failure recovery. [cited by applicant]
R1-1720305 3GPP TSG RAN WG1 Meeting #91, Reno, USA, Nov. 27-Dec. 1, 2017, Source: Samsung, Title: Discussion on cross-carrier beam management. [cited by applicant]
R1-1720574 3GPP TSG RAN WG1 Meeting #91, Reno, USA, Nov. 27-Dec. 1, 2017, Source: NEC, Title: On Partial Beam Failure Recovery. [cited by applicant]
R1-1720631 3GPP TSG RAN WG1 Meeting #91, Reno, USA, Nov. 27-Dec. 1, 2017, Source: InterDigital, Inc., Title: Remaining issues on beam recovery. [cited by applicant]
R1-1720804 3GPP TSG RAN WG1 Meeting #91, Reno, USA, Nov. 27-Dec. 1, 2017, Source: NTT Docomo, Title: Remaining issue on beam recovery. [cited by applicant]
R1-1720891 3GPP TSG RAN WG1 Meeting #91, Reno, USA, Nov. 27-Dec. 1, 2017, Source: Nokia, Nokia Shanghai Bell, Title: Beam Recovery in NR. [cited by applicant]
R1-1721523 3GPP TSG RAN WG1 Meeting #91, Reno, USA, Nov. 27-Dec. 1, 2017, Source: NTT Docomo, Samsung, Mediatek, AT&T, ZTE, Intel, Huawei, CATT, Qualcomm, Fujitsu, Spreadtrum, Title: WF for handling partial beam failure. [cited by applicant]
R1-1721673 3GPP TSG RAN WG1 Meeting #91, Reno, USA, Nov. 27-Dec. 1, 2017, Source: NTT Docomo, Intel, Huawei, NEC, Spreadtrum, Mediatek, China Telecom, AT&T, Samsung, ZTE, CATT, Qualcomm, Fujitsu, Nokia, Title: WF for ha… [cited by applicant]
R1-1800100 3GPP TSG RAN WG1 Meeting Ad Hoc, Vancouver, Canada, Jan. 22-26, 2018, Source: Huawei, HiSilicon, Title: Summary of remaining issues of beam measurement, reporting and indication. [cited by applicant]
R1-1800101 3GPP TSG RAN WG1 Meeting Ad Hoc, Vancouver, Canada, Jan. 22-26, 2018, Source: Huawei, HiSilicon, Title: Summary of remaining issues on beam failure recovery. [cited by applicant]
R1-1800110 3GPP TSG RAN WG1 Meeting Ad Hoc, Vancouver, Canada, Jan. 22-26, 2018, Source: ZTE, Sanechips, Title: Remaining details on bean management. [cited by applicant]
R1-1800111 3GPP TSG RAN WG1 Meeting Ad Hoc, Vancouver, Canada, Jan. 22-26, 2018, Source: ZTE, Sanechips, Title: Remaining details on mean management. [cited by applicant]
R1-1800312 3GPP TSG RAN WG1 Meeting Ad Hoc, Vancouver, Canada, Jan. 22-26, 2018, Source: Intel Corporation, Title: Remaining Issues on Beam Failure Recovery. [cited by applicant]
R1-1800526 3GPP TSG RAN WG1 Meeting Ad Hoc, Vancouver, Canada, Jan. 22-26, 2018, Source: Huawei, HiSilicon, Title: Remaining details of PHR. [cited by applicant]
R1-1800542 3GPP TSG RAN WG1 Meeting Ad Hoc, Vancouver, Canada, Jan. 22-26, 2018, Source: CMCC, Title: Discussion on remaining issues for beam indication. [cited by applicant]
R1-1800543 3GPP TSG RAN WG1 Meeting Ad Hoc, Vancouver, Canada, Jan. 22-26, 2018, Source: CMCC, Title: Discussion on beam recovery mechanism. [cited by applicant]
R1-1800582 3GPP TSG RAN WG1 Meeting Ad Hoc, Vancouver, Canada, Jan. 22-26, 2018, Source: AT&T, Title: TCI states configuration design to support dynamic BWP switching. [cited by applicant]
R1-1800583 3GPP TSG RAN WG1 Meeting Ad Hoc, Vancouver, Canada, Jan. 22-26, 2018, Source: AT&T, Title: In support of partial beam failure. [cited by applicant]
R1-1800622 3GPP TSG RAN WG1 Meeting Ad Hoc, Vancouver, Canada, Jan. 22-26, 2018, Source: ASUSTeK, Title: Remaining Issues for Beam Failure Recovery Procedure. [cited by applicant]
R1-1800629 3GPP TSG RAN WG1 Meeting Ad Hoc, Vancouver, Canada, Jan. 22-26, 2018, Source: InterDigital, Inc., Title: Remaining details on beam failure recovery. [cited by applicant]
R1-1800642 3GPP TSG RAN WG1 Meeting Ad Hoc, Vancouver, Canada, Jan. 22-26, 2018, Source: ITRI, Title: Discussion on timer for beam failure recovery. [cited by applicant]
R1-1800660 3GPP TSG RAN WG1 Meeting Ad Hoc, Vancouver, Canada, Jan. 22-26, 2018, Source: NTT Docomo, Title: Remaining Issue on Beam Indication. [cited by applicant]
R1-1800661 3GPP TSG RAN WG1 Meeting Ad Hoc, Vancouver, Canada, Jan. 22-26, 2018, Source: NTT Docomo, Title: Remaining issue on beam recovery. [cited by applicant]
R1-1800682 3GPP TSG RAN WG1 Meeting Ad Hoc, Vancouver, Canada, Jan. 22-26, 2018, Source: NTT Docomo, Inc., Title: Remaining issues on PHR. [cited by applicant]
R1-1800699 3GPP TSG RAN WG1 Meeting Ad Hoc, Vancouver, Canada, Jan. 22-26, 2018, Source: Ericsson, Title: Remaining details on beam management. [cited by applicant]
R1-1800700 3GPP TSG RAN WG1 Meeting Ad Hoc, Vancouver, Canada, Jan. 22-26, 2018, Source: Ericsson, Title: Remaining details and corrections for beam recovery. [cited by applicant]
R1-1800734 3GPP TSG RAN WG1 Meeting Ad Hoc, Vancouver, Canada, Jan. 22-26, 2018, Source: InterDigital, Inc., Title: Remaining issues on beam management. [cited by applicant]
R1-1800751 3GPP TSG RAN WG1 Meeting Ad Hoc, Vancouver, Canada, Jan. 22-26, 2018, Source: Nokia, Nokia Shanghai Bell, Title: Remaining details on beam indication, measurement and reporting. [cited by applicant]
R1-1800752 3GPP TSG RAN WG1 Meeting Ad Hoc, Vancouver, Canada, Jan. 22-26, 2018, Source: Nokia, Nokia Shanghai Bell, Title: Remaining Details on Beam Recovery. [cited by applicant]
R1-1800859 3GPP TSG RAN WG1 Meeting Ad Hoc, Vancouver, Canada, Jan. 22-26, 2018, Source: Qualcomm, Title: Beam management for NR. [cited by applicant]
R1-1800860 3GPP TSG RAN WG1 Meeting Ad Hoc, Vancouver, Canada, Jan. 22-26, 2018, Source: Qualcomm Incorporated, Title: Remaining details on beam recovery procedure. [cited by applicant]
R1-1801006 3GPP TSG RAN WG1 Meeting Ad Hoc, Vancouver, Canada, Jan. 22-26, 2018, Source: Ericsson, Title; Feature lead summary 1 of beam measurement and reporting. [cited by applicant]
R1-1801089 3GPP TSG RAN WG1 Meeting Ad Hoc, Vancouver, Canada, Jan. 22-26, 2018, Source: Media Tec Inc., Title: Summary for Remaining issue on Beam Failure Recovery. [cited by applicant]
R1-1801143 3GPP TSG RAN WG1 Meeting Ad Hoc, Vancouver, Canada, Jan. 22-26, 2018, Source: Ericsson, Title: Feature lead summary 2 of beam measurement and reporting. [cited by applicant]
R1-1801160 3GPP TSG RAN WG1 Meeting Ad Hoc, Vancouver, Canada, Jan. 22-26, 2018, Source: NTT Docomo, Qualcomm, Huawei, HiSilicon, ZTE, Sanechips, Fujitsu, Title: Updated offline proposal on PHR. [cited by applicant]
R1-1801187 3GPP TSG RAN WG1 Meeting Ad Hoc, Vancouver, Canada, Jan. 22-26, 2018, Source: Ericsson, Title: Feature lead summary 3 of beam measurement and reporting. [cited by applicant]
R1-1801197 3GPP TSG RAN WG1 Meeting Ad Hoc, Vancouver, Canada, Jan. 22-26, 2018, Source: MediaTek Inc., Title: Offline Summary for Remaining issues on Beam Failure Recovery. [cited by applicant]
R1-1801223 3GPP TSG RAN WG1 Meeting Ad Hoc, Vancouver, Canada, Jan. 22-26, 2018, Source: MediaTek Inc., Title: Offline Discussion Summary for Beam Failure Recovery. [cited by applicant]
R1-1801228 3GPP TSG RAN WG1 Meeting Ad Hoc, Vancouver, Canada, Jan. 22-26, 2018, Source: Ericsson, Title: Text proposal on source QCL for semi-persistent CSI-RS. [cited by applicant]
R1-1801229 3GPP TSG RAN WG1 Meeting Ad Hoc, Vancouver, Canada, Jan. 22-26, 2018, Source: Ericsson, Title: Text proposal for source spatial relation for semi-persistent SRS. [cited by applicant]
R1-1801230 3GPP TSG RAN WG1 Meeting Ad Hoc, Vancouver, Canada, Jan. 22-26, 2018, Source: Ericsson, Title: Text proposal on priority rules for PUCCH carrying RSRP reports and SRS. [cited by applicant]
R2-1806120 3GPP TSG-RAN WG2 Meeting #101, Sanya, China, Apr. 16-20, 2018, Source: ITL, Title: Beam Failure Recovery on SCell. [cited by applicant]
R2-1806166 3GPP TSG-RAN WG2 Meeting #101, Sanya, China, Apr. 16-20, 2018, Source: MediaTek, Inc., Title: On switching between CFRA and CBRA. [cited by applicant]
R2-1806774 3GPP TSG-RAN WG2 Meeting #102, Sanya, China, Apr. 16-20, 2018, Source: Nokia, Nokia Shanghai Bell, Title: Finalization of dormant SCell state. [cited by applicant]
R2-1806819 3GPP TSG-RAN WG2 Meeting #102, Busan, Korea, May 21-25, 2018, Source: Samsung, Title: MAC Impacts: Beam Failure Recovery for SCell. [cited by applicant]
R2-1806924 3GPP TSG-RAN WG2 Meeting #102, Busan, Korea, May 21-25, 2018, Source: Qualcomm, Inc., Title: SCell Dormant State Transitions based on New Timers & MAC-CEs. [cited by applicant]
R2-1806998 3GPP TSG-RAN WG2 Meeting #102, Busan, Korea, May 21-25, 2018, Source: CATT, Title: The validity of CFRA resources for BFR. [cited by applicant]
R2-1807160 3GPP TSG-RAN WG2 Meeting #102, Busan, Korea, May 21-25, 2018, Source: Panasonic, Title: Timer associated with the dedicated BFR PRACH resource. [cited by applicant]
R2-1807405 3GPP TSG-RAN WG2 Meeting #102, Busan, Korea, May 21-25, 2018, Source: ZTE, Title: Discussion on the beam failure recovery timer. [cited by applicant]
R2-1807415 3GPP TSG-RAN WG2 Meeting #102, Busan, Korea, May 21-25, 2018, Source: OPPO, Title: MAC impacts on supporting BFR procedure on SCell. [cited by applicant]
R2-1807444 3GPP TSG-RAN WG2 Meeting #102, Busan, Korea, May 21-25, 2018, Source: Huawei, HiSilicon, Title: BWP switch for BFR. [cited by applicant]
R2-1807481 3GPP TSG RAN WG2 Meeting #102, Busan, Korea, May 21-25, 2018, Source: Huawei, HiSilicon, Title: Remaining issues of temporary CQI reporting. [cited by applicant]
R2-1807584 3GPP TSG RAN WG2 Meeting #102, Busan, Korea, May 21-25, 2018, Source: vivo, Title: Discussion on the SCell BFR. [cited by applicant]
R2-1807961 3GPP TSG-RAN WG2 Meeting #102, Busan, Korea, May 21-25, 2018, Source: Huawei, HiSilicon, Title: Discussion on BFR-config for SCell BFR. [cited by applicant]
R2-1807975 3GPP TSG-RAN WG2 Meeting #102, Busan, Korea, May 21-25, 2018, Source: Huawei, HiSilicon, Title: Discussion on beam failure recovery for SCell. [cited by applicant]
R2-1808024 3GPP TSG-RAN WG2 Meeting #102, Busan, Korea, May 21-25, 2018, Source: Nokia, Nokia Shanghai Bell, Title: SCell Beam Failure Recovery. [cited by applicant]
R2-1808570 3GPP TSG RAN WG2 Meeting #102, Busan, Korea, May 21-25, 2018, Source: Qualcomm Incorporated, Title: Dormant BWP for fast SCell activation. [cited by applicant]
R2-1808658 3GPP TSG-RAN WG2 Meeting #102, Busan, Korea, May 21-25, 2018, Source: ITL, Title: Beam failure recovery on SCell. [cited by applicant]
R2-1808809 3GPP TSG RAN WG2 Meeting #102, Busan, Korea, May 21-25, 2018, Source: Ericsson, Title: CR on Dormat SCell state transition MAC CE. [cited by applicant]
R2-1809515 3GPP TSG RAN WG2 AH-1807, Montreal, Canada, Jul. 2-6, 2018, Source: CATT, Title: Further issues with DL BWP switching for CFRA. [cited by applicant]
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: JUL/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]
Apr. 30, 2020—European Office Action—EP 19157460.7. [cited by applicant]
Jan. 11, 2021—European Office Action—19157460.7. [cited by applicant]
Dec. 5, 2022—European Office Action—19157460.7. [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]
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]
3GPP TS 36.211 V14.3.0 (Jun. 2017); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels… [cited by applicant]
3GPP TS 36.213 V14.3.0 (Jun. 2017); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer pr… [cited by applicant]
3GPP TS 36.321 V.14.3.0 (Jun. 2017); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Co… [cited by applicant]
3GPP TS 36.331 V.14.3.0 (Jun. 2017); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource C… [cited by applicant]
3GPP TR 38.802 V14.1.0 (Jun. 2017), Technical Report, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Study on New Radio Access Technology Physical Layer Aspects (Release 14). [cited by applicant]
3GPP TR 38.912 V14.0.0 (Mar. 2017), Technical Report, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Study on New Radio (NR) Access Technology (Release 14). [cited by applicant]
R1-171xxxx 3GPP TSG RAN WG1 Meeting #90, Prague, Czech Republic, Aug. 21-25, 2017, Source: MCC Support, Title: Draft Report of 3GPP TSG RAN WG1 #89 v0.2.0 (Hangzhou, China, May 15-19, 2017). [cited by applicant]
R1-171xxxx 3GPP TSG RAN WG1 Meeting #90, Prague, Czech Republic, Aug. 21-25, 2017, Source: MCC Support, Title: Draft Report of 3GPP TSG RAN WG1 #AH NR2 v0.1.0 (Qingdao, China, Jun. 27-30, 2017). [cited by applicant]
R1-1708890 3GPP TSG RAN WG1 Meeting #89, Hangzhou, China, May 15-19, 2017, Source: MCC Support, Title: Final Report of 3GPP TSG RAN WG1 #88bis v1.0.0 (Spokane, Washington, Apr. 3-7, 2017). [cited by applicant]
R1-1709907 3GPP TSG RAN WG1 NR Ad-Hoc#2, Qingdao, China, Jun. 27-30, 2017, Source: Xinwei, Title: Discussion on Beam Failure Recovery. [cited by applicant]
R1-1709929 3GPP TSG RAN WG1 NR Ad Hoc Meeting, Qingdao, China, Jun. 27-30, 2017, Source: Huawei, HiSilicon, Title: General views on beam failure recovery. [cited by applicant]
R1-1710058 3GPP TSG RAN WG1 NR Ad-Hoc#2, Qingdao, China, Jun. 27-30, 2017, Source: CATT, Title: Considerations on DL beam failure and recovery. [cited by applicant]
R1-1710283 3GPP TSG RAN WG1 NR Ad-Hoc#2, Qingdao, China, Jun. 27-30, 2017, Source: LG Electronics, Title: Discussion on beam failure recovery. [cited by applicant]
R1-1710400 3GPP TSG RAN WG1 NR Ad-Hoc#2, Qingdao, China, Jun. 27-30, 2017, Source: Vivo, Title: Beam failure recovery procedure. [cited by applicant]
R1-1710596 3GPP TSG RAN WG1 NR Ad-Hoc#2, Qingdao, China, Jun. 27-30, 2017, Source: Lenovo, Motorola Mobility, Title: Discussion of beam recovery procedure. [cited by applicant]
R1-1710810 3GPP TSG RAN WG1 AH_NR Meeting, Qingdao, China, Jun. 27-30, 2017, Source: MediaTek Inc., Title: Mechanism for flexible beam failure recovery. [cited by applicant]
R1-1710926 3GPP TSG RAN WG1 NR Ad-Hoc#2, Qingdao, China, Jun. 27-30, 2017, Source: InterDigital, Inc., Title: On Remaining Details of Beam Failure Recovery. [cited by applicant]
R1-1711017 3GPP TSG RAN WG1 #89ah-NR, Qingdao, China, Jun. 27-30, 2017, Source: Ericsson, Title: Mechanism to recover from beam failure. [cited by applicant]
R1-1711291 3GPP TSG RAN WG1 NR Ad-Hoc#2, Qingdao, China, Jun. 27-30, 2017, Source: Nokia, Alcatel-Lucent Shanghai Bell, Title: Beam Recovery. [cited by applicant]
R2-1706680 3GPP TSG-RAN WG2 NR-Adhoc, Qingdao, China, Jun. 27-29, 2017, Source: AT&T, Title: Beam Failure Recovery Mechanism and RLF. [cited by applicant]
3GPP TSG-RAN WG2 NR Ad Hoc, Qingdao, China, Jun. 27-29, 2017, Source: RAN2 Chairman (Intel), Object: Chairman Notes. [cited by applicant]
PRACH—Preamble Detection and Timing Advance Estimation for multi-UE in 3GPP LTE, 3GPP LTE Solutions, from www.mymowireless.com. [cited by applicant]
Jul. 16, 2019—European Extended Search Report—EP 19166184.2. [cited by applicant]
R1-1702078 3GPP TSG RAN WG1 Meeting #88, Athens, Greece, Feb. 13-17, 2017, Source: CATT, Title: Considerations on beam recovery mechanism. [cited by applicant]
R1-1707121 3GPP TSG RAN WG1 Meeting #89, Hangzhou, China, May 15-19, 2017, Source: ZTE, Title: Discussion on beam recovery mechanism. [cited by applicant]
3GPP TS 38.213 V15.0.0 (Dec. 2017); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Physical layer procedures for control (Release 15). [cited by applicant]
3GPP TS 38.213 V15.1.0 (Mar. 2018); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Physical layer procedures for control (Release 15). [cited by applicant]
3GPP TS 38.321 V15.1.0 (Mar. 2018); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Medium Access Control (MAC) protocol specification (Release 15). [cited by applicant]
3GPP TS 38.331 V15.1.0 (Mar. 2018); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Radio Resource Control (RRC) protocol specification (Release 15). [cited by applicant]
R1-180xxxx 3GPP TSG RAN WG1 Meeting #93 Busan, South Korea, May 21-25, 2018, Source: Ericsson, Title: Feature lead summary for beam measurement and reporting. [cited by applicant]
R1-180xxxx 3GPP TSG RAN WG1 Meeting #92bis, Sanya, China, Apr. 16-20, 2018, Source: MediaTek, Inc., Title: Summary 1 on Remaining issues on Beam Failure Recovery. [cited by applicant]
R1-180xxxx 3GPP TSG RAN WG1 Meeting #93 Busan, South Korea, May 21-25, 2018, Source: MediaTek Inc., Title: Summary on Remaining issues on Beam Failure Recovery. [cited by applicant]
R1-1704400 3GPP TSG RAN WG1 Meeting #88bis, Spokane, USA, Apr. 3-7, 2017, Source: ZTE, ZTE Microelectronics, Title: Discussion on beam recovery mechanism. [cited by applicant]
R1-1704465 3GPP TSG RAN WG1 Meeting #88bis, Spokane, USA, Apr. 3-7, 2017, Source: MediaTek, Inc., Title: Discussion on beam recovery mechanism. [cited by applicant]
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]