Granted Patent
B2
US 12,615,078 · App. 18/435,020 · Granted Apr 28, 2026
Priority of beam failure recovery request and uplink channels
Inventors:
Hua Zhou (Vienna, VA); Esmael Hejazi Dinan (McLean, VA); Hyoungsuk Jeon (Centreville, VA); Kyungmin Park (Vienna, VA); Alireza Babaei (Fairfax, VA)
Assignee:
Bloomsbury Design Labs LLC
H04B7/06964H04B7/0632H04B17/17H04B17/309H04L27/2692H04W52/281H04W52/30H04W52/346H04W52/367H04W52/40H04W52/50H04W74/0833H04W76/19H04B7/0628H04L27/2613H04W36/305H04W74/0838
View Patent ↗
Loading inventors, assignments & file history…
Abstract
Systems, apparatuses, and methods are described for wireless communications. A wireless device may distribute power for various transmission types based on a priority, which may be received from a base station.
Claims (70)
1 . A method comprising:
receiving, by a wireless device, at least one configuration parameter for:
an uplink control channel transmission associated with beam failure recovery; and
a physical uplink control channel (PUCCH) resource for the uplink control channel transmission associated with beam failure recovery; and
based on the uplink control channel transmission being associated with beam failure recovery and based on the uplink control channel transmission overlapping in time with a second uplink channel transmission of a second signal:
performing the uplink control channel transmission associated with beam failure recovery; and
performing the second uplink channel transmission using power allocation that prioritizes the uplink control channel transmission associated with beam failure recovery over the second uplink channel transmission.
2 . The method of claim 1 , wherein the performing the second uplink channel transmission comprises:
determining first transmission power for the uplink control channel transmission associated with beam failure recovery;
determining second transmission power for the second uplink channel transmission; and
performing, using adjusted transmission power that is less than the second transmission power, the second uplink channel transmission.
3 . The method of claim 2 , wherein a total transmission power, comprising a sum of the first transmission power and the adjusted transmission power, does not exceed a total allowable power.
4 . The method of claim 2 , wherein the first transmission power is not reduced based on power allocation to the uplink control channel transmission associated with beam failure recovery being prioritized over power allocation to the second uplink channel transmission.
5 . The method of claim 1 , further comprising:
allocating, based on a first priority, first transmission power to the uplink control channel transmission associated with beam failure recovery; and
allocating, based on a second priority, second transmission power to the second uplink channel transmission, wherein the first priority is higher than the second priority.
6 . The method of claim 1 , wherein the performing the second uplink channel transmission comprises transmitting, via a PUCCH, channel state information.
7 . The method of claim 1 , wherein the uplink control channel transmission associated with beam failure recovery is performed via a primary cell or a secondary cell; and
wherein the second uplink channel transmission is performed via the primary cell.
8 . A method comprising:
sending, by a base station, at least one configuration parameter for:
an uplink control channel transmission associated with beam failure recovery; and
a physical uplink control channel (PUCCH) resource for the uplink control channel transmission associated with beam failure recovery; and
receiving the uplink control channel transmission associated with beam failure recovery; and
receiving a second uplink channel transmission of a second signal, wherein, based on the uplink control channel transmission being associated with beam failure recovery and being overlapped in time with the second uplink channel transmission, power allocation to the uplink control channel transmission associated with beam failure recovery is prioritized over power allocation to the second uplink channel transmission.
9 . The method of claim 8 , wherein received power associated with the uplink control channel transmission associated with beam failure recovery is greater than received power associated with the second uplink channel transmission.
10 . The method of claim 8 , wherein a total transmission power, comprising a sum of first transmission power and second transmission power, does not exceed a total allowable power,
wherein the first transmission power is associated with first uplink transmission power for the uplink control channel transmission associated with beam failure recovery, and
wherein the second transmission power is associated with second uplink transmission power for the second uplink channel transmission.
11 . The method of claim 8 , wherein first uplink transmission power, for the uplink control channel transmission associated with beam failure recovery, is not reduced based on power allocation to the uplink control channel transmission associated with beam failure recovery being prioritized over power allocation to the second uplink channel transmission.
12 . The method of claim 8 , wherein the receiving the second uplink channel transmission comprises receiving, via a PUCCH, channel state information.
13 . The method of claim 8 , wherein the uplink control channel transmission associated with beam failure recovery is received via a primary cell or a secondary cell; and
wherein the second uplink channel transmission is received via the primary cell.
14 . A wireless device comprising:
one or more processors; and
memory storing instructions that, when executed by the one or more processors, configure the wireless device to:
receive at least one configuration parameter for:
an uplink control channel transmission associated with beam failure recovery; and
a physical uplink control channel (PUCCH) resource for the uplink control channel transmission associated with beam failure recovery; and
based on the uplink control channel transmission being associated with beam failure recovery and based on the uplink control channel transmission overlapping in time with a second uplink channel transmission of a second signal:
perform the uplink control channel transmission associated with beam failure recovery; and
perform the second uplink channel transmission using power allocation that prioritizes the uplink control channel transmission associated with beam failure recovery over the second uplink channel transmission.
15 . The wireless device of claim 14 , wherein the instructions, when executed by the one or more processors, configure the wireless device to perform the second uplink channel transmission by:
determining first transmission power for the uplink control channel transmission associated with beam failure recovery;
determining second transmission power for the second uplink channel transmission; and
performing, using adjusted transmission power that is less than the second transmission power, the second uplink channel transmission.
16 . The wireless device of claim 15 , wherein a total transmission power, comprising a sum of the first transmission power and the adjusted transmission power, does not exceed a total allowable power.
17 . The wireless device of claim 15 , wherein the first transmission power is not reduced based on power allocation to the uplink control channel transmission associated with beam failure recovery being prioritized over power allocation to the second uplink channel transmission.
18 . The wireless device of claim 14 , wherein the instructions, when executed by the one or more processors, configure the wireless device to:
allocate, based on a first priority, first transmission power to the uplink control channel transmission associated with beam failure recovery; and
allocate, based on a second priority, second transmission power to the second uplink channel transmission, wherein the first priority is higher than the second priority.
19 . The wireless device of claim 14 , wherein the instructions, when executed by the one or more processors, configure the wireless device to perform the second uplink channel transmission by transmitting, via a PUCCH, channel state information.
20 . The wireless device of claim 14 , wherein the uplink control channel transmission associated with beam failure recovery is performed via a primary cell or a secondary cell; and
wherein the second uplink channel transmission is performed via the primary cell.
21 . A base station comprising:
one or more processors; and
memory storing instructions that, when executed by the one or more processors, configure the base station to:
send at least one configuration parameter for:
an uplink control channel transmission associated with beam failure recovery; and
a physical uplink control channel (PUCCH) resource for the uplink control channel transmission associated with beam failure recovery; and
receive the uplink control channel transmission associated with beam failure recovery; and
receive a second uplink channel transmission of a second signal, wherein, based on the uplink control channel transmission being associated with beam failure recovery and being overlapped in time with the second uplink channel transmission, power allocation to the uplink control channel transmission associated with beam failure recovery is prioritized over power allocation to the second uplink channel transmission.
22 . The base station of claim 21 , wherein received power associated with the uplink control channel transmission associated with beam failure recovery is greater than received power associated with the second uplink channel transmission.
23 . The base station of claim 21 , wherein a total transmission power, comprising a sum of first transmission power and second transmission power, does not exceed a total allowable power,
wherein the first transmission power is associated with first uplink transmission power for the uplink control channel transmission associated with beam failure recovery, and
wherein the second transmission power is associated with second uplink transmission power for the second uplink channel transmission.
24 . The base station of claim 21 , wherein first uplink transmission power, for the uplink control channel transmission associated with beam failure recovery, is not reduced based on power allocation to the uplink control channel transmission associated with beam failure recovery being prioritized over power allocation to the second uplink channel transmission.
25 . The base station of claim 21 , wherein the instructions, when executed by the one or more processors, configure the base station to receive the second uplink channel transmission by receiving, via a PUCCH, channel state information.
26 . The base station of claim 21 , wherein the uplink control channel transmission associated with beam failure recovery is received via a primary cell or a secondary cell; and
wherein the second uplink channel transmission is received via the primary cell.
Assignments (4)
ASSIGNMENT OF ASSIGNOR'S INTEREST
Recorded Mar 13, 2026
From: OFINNO, LLC
To: BLOOMSBURY DESIGN LABS LLC
Reel/Frame 075081/0540 →
ASSIGNMENT OF ASSIGNOR'S INTEREST
Recorded Jan 6, 2026
From: COMCAST CABLE COMMUNICATIONS, LLC
To: OFINNO, LLC
Reel/Frame 074245/0446 →
ASSIGNMENT OF ASSIGNOR'S INTEREST
Recorded Oct 2, 2024
From: ZHOU, HUA; DINAN, ESMAEL HEJAZI; JEON, HYOUNGSUK; PARK, KYUNGMIN; BABAEI, ALIREZA
To: COMCAST CABLE COMMUNICATIONS, LLC
Reel/Frame 068761/0827 →
ASSIGNMENT OF ASSIGNOR'S INTEREST
Recorded Oct 2, 2024
From: ZHOU, HUA; DINAN, ESMAEL HEJAZI; JEON, HYOUNGSUK; PARK, KYUNGMIN; BABAEI, ALIREZA
To: COMCAST CABLE COMMUNICATIONS, LLC
Reel/Frame 068761/0846 →
Continuity (5)
Provisional Application
62543826
· Aug 10, 2017
References Cited (400)
US 6490261B1
· Dent et al.
· 2002
[cited by applicant]
US 9125218B2
· Chang
· 2015
[cited by applicant]
US 9585188B2
· Jang et al.
· 2017
[cited by applicant]
US 9736795B2
· Dinan
· 2017
[cited by applicant]
US 9814076B2
· Kim et al.
· 2017
[cited by applicant]
US 9936516B2
· Hirsch et al.
· 2018
[cited by applicant]
US 9949298B1
· Akoum et al.
· 2018
[cited by applicant]
US 20110216741A1
· Yang et al.
· 2011
[cited by applicant]
US 20150189574A1
· Ng et al.
· 2015
[cited by applicant]
US 20150365921A1
· Wu
· 2015
[cited by applicant]
US 20180132266A1
· Chen et al.
· 2018
[cited by applicant]
US 20180241452A1
· Akkarakaran et al.
· 2018
[cited by applicant]
US 20180287860A1
· Xia et al.
· 2018
[cited by applicant]
US 20180359790A1
· Ingale et al.
· 2018
[cited by applicant]
US 20190104549A1
· Deng et al.
· 2019
[cited by applicant]
US 20200068416A1
· Kang et al.
· 2020
[cited by applicant]
CN 108809580A
· 2018
[cited by applicant]
EP 3099118A1
· 2016
[cited by applicant]
EP 3397015A1
· 2018
[cited by applicant]
EP 3424152A1
· 2019
[cited by applicant]
WO 2013025142A1
· 2013
[cited by applicant]
WO 2017024516A1
· 2017
[cited by applicant]
WO 2017123060A1
· 2017
[cited by applicant]
WO 2017135803A1
· 2017
[cited by applicant]
WO 2017151876A1
· 2017
[cited by applicant]
WO 2017196612A1
· 2017
[cited by applicant]
WO 2017217898A1
· 2017
[cited by applicant]
WO 2018017840A1
· 2018
[cited by applicant]
WO 2018031327A1
· 2018
[cited by applicant]
WO 2018031799A1
· 2018
[cited by applicant]
WO 2018038859A1
· 2018
[cited by applicant]
WO 2018038860A1
· 2018
[cited by applicant]
WO 2018038861A1
· 2018
[cited by applicant]
WO 2018038862A1
· 2018
[cited by applicant]
WO 2018038864A1
· 2018
[cited by applicant]
WO 2018075985A1
· 2018
[cited by applicant]
WO 2018084544A1
· 2018
[cited by applicant]
WO 2018128426A1
· 2018
[cited by applicant]
WO 2018129300A1
· 2018
[cited by applicant]
WO 2018136300A1
· 2018
[cited by applicant]
WO 2018141303A1
· 2018
[cited by applicant]
WO 2018144592A1
· 2018
[cited by applicant]
WO 2018148552A1
· 2018
[cited by applicant]
WO 2018156299A1
· 2018
[cited by applicant]
WO 2018156696A1
· 2018
[cited by applicant]
WO 2018169848A1
· 2018
[cited by applicant]
WO 2018170481A1
· 2018
[cited by applicant]
WO 2018171476A1
· 2018
[cited by applicant]
WO 2018174667A1
· 2018
[cited by applicant]
WO 2018174800A1
· 2018
[cited by applicant]
WO 2018175303A1
· 2018
[cited by applicant]
WO 2018190617A1
· 2018
[cited by applicant]
WO 2018195975A1
· 2018
[cited by applicant]
WO 2018196520A1
· 2018
[cited by applicant]
WO 2018199074A1
· 2018
[cited by applicant]
WO 2018199079A1
· 2018
[cited by applicant]
WO 2018199100A1
· 2018
[cited by applicant]
WO 2018199162A1
· 2018
[cited by applicant]
WO 2018199243A1
· 2018
[cited by applicant]
WO 2018200579A1
· 2018
[cited by applicant]
WO 2018201450A1
· 2018
[cited by applicant]
WO 2018201990A1
· 2018
[cited by applicant]
WO 2018203719A1
· 2018
[cited by applicant]
WO 2018203785A1
· 2018
[cited by applicant]
WO 2018204255A1
· 2018
[cited by applicant]
WO 2018204718A1
· 2018
[cited by applicant]
WO 2018204922A1
· 2018
[cited by applicant]
WO 2018222276A1
· 2018
[cited by applicant]
WO 2018227464A1
· 2018
[cited by applicant]
WO 2018227551A1
· 2018
[cited by applicant]
WO 2018228187A1
· 2018
[cited by applicant]
WO 2018230862A1
· 2018
[cited by applicant]
WO 2018231655A1
· 2018
[cited by applicant]
WO 2018232090A1
· 2018
[cited by applicant]
WO 2018232259A1
· 2018
[cited by applicant]
WO 2018237400A1
· 2018
[cited by applicant]
WO 2019004694A1
· 2019
[cited by applicant]
WO 2019032882A1
· 2019
[cited by applicant]
R1-1801454 3GPP TSG RAN WG1 Meeting #92, Athens, Greece, Feb. 26-Mar. 2, 2018, Source: Huawei, HiSilicon, Title: Remaining issues on beam failure recovery.
[cited by applicant]
R1-1801722 3GPP TSG RAN WG1 Meeting #92, Athens, Greece, Feb. 26-Mar. 2, 2018, Source: CATT, Title: Remaining issues on DL beam failure recovery.
[cited by applicant]
R1-1802393 3GPP TSG RAN WG1 Meeting #92, Athens, Greece, Feb. 26-Mar. 2, 2018, Source: Intel Corporation, Title: on beam management issues for multi-CC operation.
[cited by applicant]
R1-1802397 3GPP TSG RAN WG1 Meeting #92, Athens, Greece, Febr. 26-Mar. 2, 2018, Source: Intel Corporation, Title: Remaining Issues on Beam Failure Recovery.
[cited by applicant]
R1-1802472 3GPP TSG RAN WG1 Meeting #92, Athens, Greece, Feb. 26-Mar. 2, 2018, Source: NTT Docomo, Title: Remaining issues on beam recovery.
[cited by applicant]
R1-1802557 3GPP TSG RAN WG1 Meeting #92, Athens, Greece, Feb. 26-Mar. 2, 2018, Source: Nokia, Nokia Shanghai Bell, Title: Remaining Details on Beam Recovery.
[cited by applicant]
R1-1802593 3GPP TSG RAN WG1 Meeting #92, Athens, Greece, Feb. 26-Mar. 2, 2018, Source: AT&T, Title: In support of partial beam failure.
[cited by applicant]
R1-1802744 3GPP TSG RAN WG1 Meeting #92, Athens, Greece, Feb. 26-Mar. 2, 2018, Source: Ericsson, Title: Remaining details on beam recovery.
[cited by applicant]
R1-1802824 3GPP TSG RAN WG1 Meeting #92, Athens, Greece, Feb. 26-Mar. 2, 2018, Source: Qualcomm Incorporated, Title: Beam recovery procedures.
[cited by applicant]
R1-1803362 3GPP TSG RAN WG1 Meeting #92, Athens, Greece, Feb. 26-Mar. 2, 2018, Source: MediaTek Inc., Title: Summary on Remaining issues on Beam Failure Recovery.
[cited by applicant]
R1-1803397 3GPP TSG RAN WG1 Meeting #92, Athens, Greece, Feb. 26-Mar. 2, 2018, Source: CATT, Title: Summary of Email Discussion on Beam Failure Recovery on Scell.
[cited by applicant]
R1-1803745 3GPP TSG-RAN WG1 Meeting #92bis, Sanya, China, Apr. 16-20, 2018, Source: CATT, Title: Remaining Details on Beam Failure Recovery.
[cited by applicant]
R1-1804210 3GPP TSG-RAN WG1 Meeting #92bis, Sanya, China, Apr. 16-20, 2018, Source: Lenovo, Motorola Mobility, Title: Discussion of Beam Measurement for Carrier Aggregation.
[cited by applicant]
R1-1804363 3GPP TSG-RAN WG1 Meeting #92bis, Sanya, China, Apr. 16-20, 2018, Source: Samsung, Title: Simultaneous Reception of Physical Channels and Reference Signals.
[cited by applicant]
R1-1804789 3GPP TSG-RAN WG1 Meeting #92bis, Sanya, China, Apr. 16-20, 2018, Source: Qualcomm Incorporated, Title: Details on Simultaneous Reception/Transmission of PHY Channels and RS in FR2.
[cited by applicant]
R1-1804975 3GPP TSG-RAN WG1 Meeting #92bis, Sanya, China, Apr. 16-20, 2018, Source: Ericsson, Title: Remaining Issues on Beam Recovery.
[cited by applicant]
R1-1804977 3GPP TSG-RAN WG1 Meeting #92bis, Sanya, China, Apr. 16-20, 2018, Source: Ericsson, Title: On Simultaneous Reception of Physical and Reference Signals Across CCs.
[cited by applicant]
R1-1805538 3GPP TSG-RAN WG1 Meeting #92bis, Sanya, China, Apr. 16-20, 2018, Source: NTT Docomo, Inc., Title: Offline Summary for AI 7.1.3.1.2 Search Space.
[cited by applicant]
R1-1806616 3GPP TSG-RAN WG1 #93, Busan, Korea, May 21-25, 2018, Source: LG Electronics, Title: Remaining Issues on Search Space.
[cited by applicant]
R1-1806729 3GPP TSG-RAN WG1 #93, Busan, Korea, May 21-25, 2018, Source: Samsung, Title: Corrections on Search Space Design.
[cited by applicant]
R2-1707999 3GPP TSG-RAN WG2 #99, Berlin, Germany, Aug. 21-25, 2017, Source: MediaTek Inc., Title: Beam Management and Beam Recovery in MAC.
[cited by applicant]
R2-1708677 3GPP TSG RAN WG2 #99, Berlin, Germany, Aug. 21-25, 2017, Source: Nokia, Nokia Shanghai Bell, Title: Beam Recovery in NR.
[cited by applicant]
R2-1708697 3GPP TSG RAN WG2 #99, Berlin, Germany, Aug. 21-25, 2017, Source: Huawei, HiSilicon, Title: Handling of Resources for Beam Failure Recovery.
[cited by applicant]
R2-1709085 3GPP TSG-RAN WG2 #99, Berlin, Germany, Aug. 21-25, 2017, Source: Qualcomm Incorporated, Title: Beam Recovery Request.
[cited by applicant]
R2-1709320 3GPP TSG-RAN WG2 #99, Berlin, Germany, Aug. 21-25, 2017, Source: ASUSTek, Title: Discussion on Beam Recover Request in NR.
[cited by applicant]
R2-1800042 3GPP TSG-RAN WG2 AH, Vancouver, Canada, Jan. 22-26, 2018, Source: ASUSTek, Title: Discussion on Beam Failure Recovery Request in NR.
[cited by applicant]
R2-1800049 3GPP TSG-RAN WG2 AH, Vancouver, Canada, Jan. 22-26, 2018, Source: ASUSTek, Title: UE Behaviours Upon Beam Failure and Recovery.
[cited by applicant]
R2-1800168 3GPP TSG-RAN WG2 AH, Vancouver, Canada, Jan. 22-26, 2018, Source: CATT, Title: Solution for PH Type Inconsistency Between RAN1 and RAN2.
[cited by applicant]
R2-1800169 3GPP TSG-RAN WG2 AH, Vancouver, Canada, Jan. 22-26, 2018, Source: CATT, Title: PHR MAC CE for EN-DC.
[cited by applicant]
R2-1800231 3GPP TSG-RAN WG2 #100, Reno, USA, Nov. 27-Dec. 1, 2017, Source: Xiaomi, Title: Consideration on PHR Trigger Condition for Supporting SUL.
[cited by applicant]
R2-1800253 3GPP TSG-RAN WG2 AH, Vancouver, Canada, Jan. 22-26, 2018, Source: ASUSTek, Title: Pathloss Change for Triggering PHR.
[cited by applicant]
R2-1800254 3GPP TSG-RAN WG2 AH, Vancouver, Canada, Jan. 22-26, 2018, Source: CATT, Title: RA Procedure and Parameters for BFR.
[cited by applicant]
R2-1800343 3GPP TSG-RAN WG2 AH, Vancouver, Canada, Jan. 22-26, 2018, Source: Ericsson, Title: PHR Format for SUL.
[cited by applicant]
R2-1800614 3GPP TSG-RAN WG2 AH, Vancouver, Canada, Jan. 22-26, 2018, Source: Samsung, Title: Support for Type 2 PH in NR.
[cited by applicant]
R2-1800619 3GPP TSG-RAN WG2 AH, Vancouver, Canada, Jan. 22-26, 2018, Source: Samsung, Title: SUL and PHR.
[cited by applicant]
R2-1800642 3GPP TSG-RAN WG2 AH, Vancouver, Canada, Jan. 22-26, 2018, Source: Huawei, HiSilicon, Title: PHR Alignment Between RAN1 and RAN2.
[cited by applicant]
R2-1800680 3GPP TSG-RAN WG2 AH, Vancouver, Canada, Jan. 22-26, 2018, Source: Lenovo, Motorola Mobility, Title: PHR for NR CA.
[cited by applicant]
R2-1800822 3GPP TSG-RAN WG2 AH, Vancouver, Canada, Jan. 22-26, 2018, Source: Spreadtrum Communications, Title: Beam Failure Recovery Clarification.
[cited by applicant]
R2-1801008 3GPP TSG-RAN WG2 AH, Vancouver, Canada, Jan. 22-26, 2018, Source: Huawei, HiSilicon, Title: Discussion on Power Sharing and its Impact on PHR for EN-DC.
[cited by applicant]
R2-1801009 3GPP TSG-RAN WG2 AH, Vancouver, Canada, Jan. 22-26, 2018, Source: Huawei, HiSilicon, Title: General Consideration on RA Procedure for Beam Failure Recovery.
[cited by applicant]
R2-1801041 3GPP TSG-RAN WG2 AH, Vancouver, Canada, Jan. 22-26, 2018, Source: Huawei, HiSilicon, Title: Remaining Issue of Power Management in NR.
[cited by applicant]
R2-1801043 3GPP TSG-RAN WG2 AH, Vancouver, Canada, Jan. 22-26, 2018, Source: Huawei, HiSilicon, Title: Consideration of PHR with Multi-Beam Operation.
[cited by applicant]
R2-1801404 3GPP TSG-RAN WG2 AH, Vancouver, Canada, Jan. 22-26, 2018, Source: NTT Docomo, Inc., Title: Discussion on Beam Failure Recovery.
[cited by applicant]
R2-1801406 3GPP TSG-RAN WG2 AH, Vancouver, Canada, Jan. 22-26, 2018, Source: NTT Docomo, Inc., Title: Remaining Issue on PHR.
[cited by applicant]
R2-1801539 3GPP TSG-RAN WG2 AH, Vancouver, Canada, Jan. 22-26, 2018, Source: CATT, Title: PHR MAC CE for EN-DC.
[cited by applicant]
R2-1801540 3GPP TSG-RAN WG2 AH, Vancouver, Canada, Jan. 22-26, 2018, Source: CATT, Title: Correction on PHR MAC CE in EN-DC in TS38.321.
[cited by applicant]
R2-1801564 3GPP TSG-RAN WG2 AH, Vancouver, Canada, Jan. 22-26, 2018, Source: NTT Docomo, Inc., Title: LS on PHR.
[cited by applicant]
R2-1801568 3GPP TSG-RAN WG2 AH, Vancouver, Canada, Jan. 22-26, 2018, Source: RAN WG2, Title: LS on PHR.
[cited by applicant]
R2-1801814 3GPP TSG-RAN WG2 #101, Athens, Greece, Feb. 26-Mar. 2, 2018, Source: Huawei, HiSilicon, Title: Beam Failure Recovery on SCell.
[cited by applicant]
R2-1802490 3GPP TSG-RAN WG2 #101, Athens, Greece, Feb. 26-Mar. 2, 2018, Source: CATT, Huawei, HiSilicon, Title: Discussion on Beam Failure Recovery for CA.
[cited by applicant]
R2-1707001 3GPP TSG-RAN WG2 Meeting #AH, Qingdao, China, Jun. 27-29, 2017, Source: Lenovo, Motorola Mobility, Title: Random access procedure for beam recovery request.
[cited by applicant]
R1-17111617 3GPP TSG RAN WG1 NR AH#2, Qingdao, China, Jun. 27-30, 2017, Source: CATT, Title: RACH power control and power ramping procedure (revision of R1-1710034).
[cited by applicant]
R1-1711161 3GPP TSG RAN WG1 NR#2, Qingdao, China, Jun. 27-30, 2017, Source: Qualcomm Incorporated, Title: Beam recovery procedures.
[cited by applicant]
International Search Report and Written Opinion for PCT/US2018/046368 mailing date Dec. 13, 2018.
[cited by applicant]
Apr. 15, 2019—Extended European Search Report—EP 19150964.5.
[cited by applicant]
R1-1708678 3GPP TSG-RAN WG1 #89, Hangzhou, China, May 15-19, 2017, Source: Ericsson, Title: Beam failure recovery mechanism.
[cited by applicant]
May 22, 2019—Extended European Search Report—19156175.2.
[cited by applicant]
R2-1800560 3GPP TSG-RAN WG2 NR, Vancouver, Canada, Jan. 22-26, 2018, Source: Sharp, Title: Remaining issues on beam failure recovery.
[cited by applicant]
R2-1800632 3GPP TSG-RAN WG2 AH, Vancouver, Canada, Jan. 22-26, 2018, Source: Huawei, HiSilicon, Title: Remaining issue for beam failure recovery.
[cited by applicant]
R2-1801049 3GPP TSG-RAN WG2 AH, Vancouver, Canada, Jan. 22-26, 2018, Source: Huawei, HiSilicon, Title: Non-contention based random access for beam failure recovery in CA.
[cited by applicant]
3GPP TS 38.321 V15.0.0 (Dec. 2017); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Medium Access Control (MAC) protocol specification (Release 15).
[cited by applicant]
3GPP TS 38.213 V15.0.1 (Dec. 2018); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Physical layer procedures for control (Release 15).
[cited by applicant]
R2-1804475 3GPP TSG-RAN WG2 Meeting #101bis, Sanya, China, Apr. 16-20, 2018, Source: Spreadtrum Communications, Title: Beam Failure recovery on SCell.
[cited by applicant]
May 14, 2019—European Extended Search Report—19157460.7.
[cited by applicant]
R2-1710562 3GPP TSG-RAN WG2 #99bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: Huawei, HiSilicon, Title: RAN2 aspects of DL beam management (revision of R2-1708695).
[cited by applicant]
3GPP TS 36.211 V14.3.0 (Jun. 2017); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels…
[cited by applicant]
3GPP TS 36.213 V14.3.0 (Jun. 2017); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer pr…
[cited by applicant]
3GPP TS 36.321 V.14.3.0 (Jun. 2017); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Co…
[cited by applicant]
3GPP TS 36.331 V.14.3.0 (Jun. 2017); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource C…
[cited by applicant]
3GPP TR 38.802 V14.1.0 (Jun. 2017), Technical Report, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Study on New Radio Access Technology Physical Layer Aspects (Release 14).
[cited by applicant]
3GPP TR 38.912 V14.0.0 (Mar. 2017), Technical Report, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Study on New Radio (NR) Access Technology (Release 14).
[cited by applicant]
R1-171xxxx 3GPP TSG RAN WG1 Meeting #90, Prague, Czech Republic, Aug. 21-25, 2017, Source: MCC Support, Title: Draft Report of 3GPP TSG RAN WG1 #89 v0.2.0 (Hangzhou, China, May 15-19, 2017).
[cited by applicant]
R1-171xxxx 3GPP TSG RAN WG1 Meeting #90, Prague, Czech Republic, Aug. 21-25, 2017, Source: MCC Support, Title: Draft Report of 3GPP TSG RAN WG1 #AH NR2 v0.1.0 (Qingdao, China, Jun. 27-30, 2017).
[cited by applicant]
R1-1708890 3GPP TSG RAN WG1 Meeting #89, Hangzhou, China, May 15-19, 2017, Source: MCC Support, Title: Final Report of 3GPP TSG RAN WG1 #88bis v1.0.0 (Spokane, Washington, Apr. 3-7, 2017).
[cited by applicant]
R1-1709907 3GPP TSG RAN WG1 NR Ad-Hoc#2, Qingdao, China, Jun. 27-30, 2017, Source: Xinwei, Title: Discussion on Beam Failure Recovery.
[cited by applicant]
R1-1709929 3GPP TSG RAN WG1 NR Ad Hoc Meeting, Qingdao, China, Jun. 27-30, 2017, Source: Huawei, HiSilicon, Title: General views on beam failure recovery.
[cited by applicant]
R1-1710058 3GPP TSG RAN WG1 NR Ad-Hoc#2, Qingdao, China, Jun. 27-30, 2017, Source: CATT, Title: Considerations on DL beam failure and recovery.
[cited by applicant]
R1-1710283 3GPP TSG RAN WG1 NR Ad-Hoc#2, Qingdao, China, Jun. 27-30, 2017, Source: LG Electronics, Title: Discussion on beam failure recovery.
[cited by applicant]
R1-1710400 3GPP TSG RAN WG1 NR Ad-Hoc#2, Qingdao, China, Jun. 27-30, 2017, Source: Vivo, Title: Beam failure recovery procedure.
[cited by applicant]
R1-1710596 3GPP TSG RAN WG1 NR Ad-Hoc#2, Qingdao, China, Jun. 27-30, 2017, Source: Lenovo, Motorola Mobility, Title: Discussion of beam recovery procedure.
[cited by applicant]
R1-1710810 3GPP TSG RAN WG1 AH_NR Meeting, Qingdao, China, Jun. 27-30, 2017, Source: MediaTek Inc., Title: Mechanism for flexible beam failure recovery.
[cited by applicant]
R1-1710926 3GPP TSG RAN WG1 NR Ad-Hoc#2, Qingdao, China, Jun. 27-30, 2017, Source: InterDigital, Inc., Title: On Remaining Details of Beam Failure Recovery.
[cited by applicant]
R1-1711017 3GPP TSG RAN WG1 #89ah-NR, Qingdao, China, Jun. 27-30, 2017, Source: Ericsson, Title: Mechanism to recover from beam failure.
[cited by applicant]
R1-1711291 3GPP TSG RAN WG1 NR Ad-Hoc#2, Qingdao, China, Jun. 27-30, 2017, Source: Nokia, Alcatel-Lucent Shanghai Bell, Title: Beam Recovery.
[cited by applicant]
R2-1706680 3GPP TSG-RAN WG2 NR-Adhoc, Qingdao, China, Jun. 27-29, 2017, Source: AT&T, Title: Beam Failure Recovery Mechanism and RLF.
[cited by applicant]
3GPP TSG-RAN WG2 NR Ad Hoc, Qingdao, China, Jun. 27-29, 2017, Source: RAN2 Chairman (Intel), Object: Chairman Notes.
[cited by applicant]
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 Beam Failure Recovery Configuration.
[cited by applicant]
3GPP TS 38.331 V15.2.1 (Jun. 2018), Technical Specification, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Radio Resource Control (RRC) protocol specification (Release 15).
[cited by applicant]
R1-180XXXX 3GPP TSG-RAN WG1 Meeting #94, Gothenburg, Sweden, Aug. 20-24, 2018, Source: Ericsson, Title: Feature lead summary beam management v2.
[cited by applicant]
R2-1804763 3GPP TSG-RAN WG2 Meeting #101bis, Sanya, China, Apr. 16-20, 2018, Source: Nokia, Nokia Shanghai Bell, Title: Running MAC CR for euCA.
[cited by applicant]
R1-180XXXX 3GPP TSG-RAN WG1 Meeting #94, Gothenburg, Sweden, Aug. 20-24, 2018, Source: NTT Docomo, Inc., Title: Offline summary for PDCCH structure and search space.
[cited by applicant]
R1-180XXXX 3GPP TSG-RAN WG1 Meeting #94, Gothenburg, Sweden, Aug. 20-24, 2018, Source: MediaTek Inc., Title: Summary #1 on Remaining Issues on Beam Failure Recovery.
[cited by applicant]
R1-1712153 3GPP TSG RAN WG1 Meeting #90, Prague, Czech Republic, Aug. 21-25, 2017, Source: Huawei, HiSilicon, Title: Overview of bandwidth part.
[cited by applicant]
R1-1713204 3GPP TSG RAN WG1 Meeting #90, Prague, Czech Republic, Aug. 21-25, 2017, Source: LG Electronics, Title: Further remaining details on wider bandwidth operation.
[cited by applicant]
R1-1713978 3GPP TSG RAN WG1 Meeting #90, Prague, Czech Republic, Aug. 21-25, 2017, Source: MediaTek Inc., Title: Further Details on Bandwidth Part Operation in NR.
[cited by applicant]
R1-1719650 3GPP TSG RAN WG1 Meeting #91, Reno, USA, Nov. 27-Dec. 1, 2017, Source: AT&T, Title: Remaining details on bandwidth parts.
[cited by applicant]
R1-1719651 3GPP TSG RAN WG1 Meeting #91, Reno, USA, Nov. 27-Dec. 1, 2017, Source: AT&T, Title: Remaining details on carrier aggregation.
[cited by applicant]
R1-1721027 3GPP TSG RAN WG1 Meeting #91, Reno, USA, Nov. 27-Dec. 1, 2017, Source: Ericsson, Title: On Carrier aggregation related aspects.
[cited by applicant]
R1-1800879 3GPP TSG RAN WG1 NR Ad Hoc, Vancouver, Canada, Jan. 22-26, 2018, Source: Qualcomm Incorporated, Title: Remaining Issues on BWP.
[cited by applicant]
R1-1803622 3GPP TSG RAN WG1 Meeting #92, Sanya, China, Apr. 16-20, 2018, Source: NEC, Title: Remaining issues on beam failure recovery.
[cited by applicant]
R1-1804211 3GPP TSG-RAN WG1 Meeting #92bis, Sanya, China, Apr. 16-20, 2018, Source: Lenovo, Motorola Mobility, Title: Discussion of beam failure recovery for Carrier Aggregation.
[cited by applicant]
R1-1806281 3GPP TSG-RAN WG1 #93, Busan, Korea, May 21-25, 2018, Source: CATT, Title: Remaining issues on beam failure recovery.
[cited by applicant]
R1-1806508 3GPP TSG-RAN WG1 #93, Busan, Korea, May 21-25, 2018, Source: Intel Corporation, Title: Remaining issues on beam failure recovery.
[cited by applicant]
R1-1806789 3GPP TSG-RAN WG1 #93, Busan, Korea, May 21-25, 2018, Source: MediaTek Inc., Title: Remaining issues on beam failure recovery.
[cited by applicant]
R1-1807796 3GPP TSG-RAN WG1 #93, Busan, Korea, May 21-25, 2018, Source: MediaTek Inc., Title: Summary 2 on Remaining issues on beam failure recovery.
[cited by applicant]
R1-1808720 3GPP TSG-RAN WG1 Meeting #94, Gothenburg, Sweden, Aug. 20-24, 2018, Source: Intel Corporation, Title: On SCell Beam Failure Recovery.
[cited by applicant]
R1-1810020 3GPP TSG-RAN WG1 Meeting #94, Gothenburg, Sweden, Aug. 20-24, 2018, Source: Samsung, Title: CR to 38.213 capturing the RAN1#94 meeting agreements.
[cited by applicant]
R2-1713170 3GPP TSG RAN WG2 Meeting #100, Reno, USA, Nov. 27-Dec. 1, 2017, Source: Nokia (rapporteur), Title: Report of [99bis#32][LTE/euCA] Faster activation for Scells (Nokia).
[cited by applicant]
R2-1714289 3GPP TSG RAN WG2 Meeting #100, Reno, USA, Nov. 27-Dec. 1, 2017, Source: Nokia, Nokia Shanghai Bell, Title: Running CR for euCA Stage-2.
[cited by applicant]
R2-1800866 3GPP TSG-RAN WG2 AH, Vancouver, Canada, Jan. 22-26, 2018, Source: vivo, Title: RACH configuration for beam recovery.
[cited by applicant]
R2-1800895 3GPP TSG-RAN WG2 AH, Vancouver, Canada, Jan. 22-26, 2018, Source: vivo, Title: Discussion on the impact on beam failure recovery.
[cited by applicant]
R2-1801432 3GPP TSG RAN WG2 NR Ad Hoc, Vancouver, Canada, Jan. 22-26, 2018, Source: Qualcomm Incorporated, Title: Dormant BWP for fast SCell activation.
[cited by applicant]
R2-1801926 3GPP TSG-RAN WG2 #101, Athens, Greece, Feb. 26-Mar. 2, 2018, Source: ZTE, Sanechips, Title: Remaining considerations on RACH procedure for BFR.
[cited by applicant]
R2-1802143 3GPP TSG-RAN WG2 #101, Athens, Greece, Feb. 26-Mar. 2, 2018, Source: CATT, Title: RACH reattempt considering beam selection.
[cited by applicant]
R2-1802151 3GPP TSG-RAN WG2 #101, Athens, Greece, Feb. 26-Mar. 2, 2018, Source: CATT, Title: Beam failure recovery.
[cited by applicant]
R2-1802756 3GPP TSG RAN WG2 Meeting #101, Athens, Greece, Feb. 26-Mar. 2, 2018, Source: Nokia, Nokia Shanghai Bell, Title: Remaining details on temporary CQI reporting during activation.
[cited by applicant]
R2-1803229 3GPP TSG-RAN WG2 #101, Athens, Greece, Feb. 26-Mar. 2, 2018, Source: Nokia, Nokia Shanghai Bell, Title: BWP switch interaction with contention free BFR preamble.
[cited by applicant]
R2-1803564 3GPP TSG RAN WG2 Meeting #101, Athens, Greece, Feb. 26-Mar. 2, 2018, Source: Qualcomm Incorporated, Title: Dormant BWP for fast SCell activation.
[cited by applicant]
R2-1804279 3GPP TSG-RAN WG2 Meeting #101, Sanya, China, Apr. 16-20, 2018, Source: ASUSTek, Title: UE behaviours upon beam failure and recovery.
[cited by applicant]
R2-1804303 3GPP TSG-RAN WG2 Meeting #101, Sanya, China, Apr. 16-20, 2018, Source: Samsung, Title: MAC Impacts: Beam Failure Recovery for SCell.
[cited by applicant]
R2-1804407 3GPP TSG-RAN WG2 Meeting #101, Sanya, China, Apr. 16-20, 2018, Source: ZTE, Sanechips, Title: Consideration on beam failure recovery for SCell.
[cited by applicant]
R2-1804410 3GPP TSG-RAN WG2 Meeting #101, Sanya, China, Apr. 16-20, 2018, Source: Huawei, HiSilicon, Title: Beam failure recovery using MAC CE.
[cited by applicant]
R2-1804411 3GPP TSG-RAN WG2 Meeting #101, Sanya, China, Apr. 16-20, 2018, Source: Huawei, HiSilicon, Title: BWP issues for BFR.
[cited by applicant]
R2-1804434 3GPP TSG-RAN WG2 Meeting #101, Sanya, China, Apr. 16-20, 2018, Source: OPPO, Title: Issues on supporting SCell BFR RACH.
[cited by applicant]
R2-1804481 3GPP TSG-RAN WG2 Meeting #101, Sanya, China, Apr. 16-20, 2018, Source: CATT, Title: Leftover issues for BFR.
[cited by applicant]
R2-1804482 3GPP TSG-RAN WG2 Meeting #101, Sanya, China, Apr. 16-20, 2018, Source: CATT, Title: BFR configurations and fallback options.
[cited by applicant]
R2-1804483 3GPP TSG-RAN WG2 Meeting #101, Sanya, China, Apr. 16-20, 2018, Source: CATT, Title: BFR on SCell.
[cited by applicant]
R2-1804696 3GPP TSG-RAN WG2 Meeting #101, Sanya, China, Apr. 16-20, 2018, Source: vivo, Title: Discussion on the SCell BFR.
[cited by applicant]
R2-1805204 3GPP TSG-RAN WG2 Meeting #101, Sanya, China, Apr. 16-20, 2018, Source: Lenovo, Motorola Mobility, Title: Dedicated PRACH resource for beam failure recovery.
[cited by applicant]
R2-1805414 3GPP TSG-RAN WG2 Meeting #101, Sanya, China, Apr. 16-20, 2018, Source: Ericsson, Title: Beam Failure Recovery in SCell and contention-based BFR on SpCell.
[cited by applicant]
R2-1805896 3GPP TSG-RAN WG2 Meeting #101, Sanya, China, Apr. 16-20, 2018, Source: Huawei, HiSilicon, Title: ASN.1 for Beam Failure Recovery.
[cited by applicant]
R2-1805905 3GPP TSG-RAN WG2 Meeting #101, Sanya, China, Apr. 16-20, 2018, Source: Huawei, HiSilicon, Title: Discussions on RA for SCells BFR.
[cited by applicant]
R1-1719423 3GPP TSG RAN WG1 Meeting #91, Reno, USA, Nov. 27-Dec. 1, 2017, Source: Huawei, HiSilicon, Title: Remaining details on beam failure recovery.
[cited by applicant]
R1-1719619 3GPP TSG RAN WG1 Meeting #91, Reno, USA, Nov. 27-Dec. 1, 2017, Source: Fujitsu, Title: Discussion on beam failure recovery.
[cited by applicant]
R1-1719633 3GPP TSG RAN WG1 Meeting #91, Reno, USA, 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-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: MediaTek Inc., Title: On Parallel SR and RACH Procedure in NR.
[cited by applicant]
R1-170xxxx 3GPP TSG RAN WG1 Meeting #88b, Spokane, USA, Apr. 3-7, 2017, Source: Huawei, HiSilicon, Title: WF on Beam Failure Recovery.
[cited by applicant]
R1-171xxxx 3GPP TSG RAN WG1 Meeting #90, Prague, Czech Republic, Aug. 21-25, 2017, Source: MediaTek Inc. Title: Offline Discussion on Beam Recovery Mechanism.
[cited by applicant]
R1-1704230 3GPP TSG RAN WG1 Meeting #88b, Spokane, USA, Apr. 3-7, 2017, Source: Huawei, HiSilicon, Title: Link recovery procedure for beam failure.
[cited by applicant]
3GPP TS 36.212 V14.3.0 (Jun. 2017); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Multiplexing and …
[cited by applicant]
3GPP TSG RAN WG1 Meeting #90, Prague, Czech Republic, Aug. 21-25, 2017, Title: RAN1 Chairman's Notes.
[cited by applicant]
R1-1705719 3GPP TSG RAN WG1 Meeting #88bis, Spokane, USA, Apr. 3-7, 2017, Source: NTT Docomo, Inc., Title: Further views on mechanism to recover from beam failure.
[cited by applicant]
R1-1711016 3GPP TSG RAN WG1 #89AH-NR, Qingdao, China, Jun. 27-30, 2017, Source: Ericsson, Title: UL beam management details.
[cited by applicant]
R1-1712223 3GPP TSG RAN WG1 Meeting #90, Prague, Czech Republic, Aug. 21-25, 2017, Source: Huawei, HiSilicon, Title: UL beam management.
[cited by applicant]
R1-1712224 3GPP TSG RAN WG1 Meeting #90, Prague, Czech Republic, Aug. 21-25, 2017, Source: Huawei, HiSilicon, Title: Procedure details for beam failure recovery.
[cited by applicant]
R1-1712268 3GPP TSG RAN WG1 Meeting #90, Prague, Czech Republic, Aug. 21-25, 2017, Source: Xinwei, Title: Discussion on beam failure recovery.
[cited by applicant]
R1-1712299 3GPP TSG RAN WG1 Meeting #90, Prague, Czech Republic, Aug. 21-25, 2017, Source: ZTE, Title: UL beam management for NR MIMO.
[cited by applicant]
R1-1712378 3GPP TSG RAN WG1 Meeting #90, Prague, Czech Republic, Aug. 21-25, 2017, Source: CATT, Title: Considerations on UL beam management.
[cited by applicant]
R1-1712379 3GPP TSG RAN WG1 Meeting #90, Prague, Czech Republic, Aug. 21-25, 2017, Source: CATT, Title: Beam failure detection and recovery.
[cited by applicant]
R1-1712551 3GPP TSG RAN WG1 Meeting #90, Prague, Czech Republic, Aug. 21-25, 2017, Source: Intel Corporation, Title: Details for UL beam management.
[cited by applicant]
R1-1712552 3GPP TSG RAN WG1 Meeting #90, Prague, Czech Republic, Aug. 21-25, 2017, Source: Intel Corporation, Title: Discussion for mechanism to recover from beam failure.
[cited by applicant]
R1-1721672 3GPP TSG RAN WG1 Meeting #90, Prague, Czech Republic, Aug. 21-25, 2017, Source: Lenovo, Motorola Mobility, Title: Discussion of beam failure recovery.
[cited by applicant]
R1-1712713 3GPP TSG RAN WG1 Meeting #90, Prague, Czech Republic, Aug. 21-25, 2017, Source: AT&T, Title: Mechanisms to recover from beam failure.
[cited by applicant]
R1-1712838 3GPP TSG RAN WG1 Meeting #90, Prague, Czech Republic, Aug. 21-25, 2017, Source: Vivo, Title: Discussion on uplink beam management.
[cited by applicant]
R1-1712966 3GPP TSG RAN WG1 Meeting #90, Prague, Czech Republic, Aug. 21-25, 2017, Source: Sony, Title: Considerations on UL beam management.
[cited by applicant]
R1-1713287 3GPP TSG RAN WG1 Meeting #90, Prague, Czech Republic, Aug. 21-25, 2017, Source: Guangdong OPPO Mobile Telecom, Title: Discussion on the UL beam management.
[cited by applicant]
R1-1713596 3GPP TSG RAN WG1 Meeting #90, Prague, Czech Republic, Aug. 21-25, 2017, Source: Samsung, Title: Discussion on UL beam management.
[cited by applicant]
R1-1714143 3GPP TSG RAN WG1 Meeting #90, Prague, Czech Republic, Aug. 21-25, 2017, Source: InterDigital, Inc., Title: On efficient UL beam management.
[cited by applicant]
R1-1714250 3GPP TSG RAN WG1 Meeting #90, Prague, Czech Republic, Aug. 21-25, 2017, Source: Nokia, Nokia Shanghai Bell, Title: SRS transmission for beam management.
[cited by applicant]
R1-1714292 3GPP TSG RAN WG1 Meeting #90, Prague, Czech Republic, Aug. 21-25, 2017, Source: Ericsson, Title: On UL beam management.
[cited by applicant]
R1-1714383 3GPP TSG RAN WG1 Meeting #90, Prague, Czech Republic, Aug. 21-25, 2017, Source: ASUSTek, Title: Considerations on UE Beamforming Management.
[cited by applicant]
3GPP TSG RAN WG1 Meeting NR#3, Nagoya, Japan, Sep. 18-21, 2017, Title: RAN1 Chairman's Notes.
[cited by applicant]
R1-1715441 3GPP TSG RAN WG1 Meeting NR#3, Nagoya, Japan, Sep. 18-21, 2017, Source: ZTE, Sanechips, Title: Discussion on beam recovery.
[cited by applicant]
R1-1715620 3GPP TSG RAN WG1 Meeting NR#3, Nagoya, Japan, Sep. 18-21, 2017, Source: Vivo, Title: Discussion on beam failure recovery procedure.
[cited by applicant]
R1-1715802 3GPP TSG RAN WG1 Meeting NR#3, Nagoya, Japan, Sep. 18-21, 2017, Source: CATT, Title: Beam failure detection and recovery.
[cited by applicant]
R2-1708696 3GPP TSG RAN WG2 #99, Berlin, Germany, Aug. 21-25, 2017, Source: Huawei, HiSilicon, Title: Consideration on DRX with beam management.
[cited by applicant]
R2-1708755 3GPP TSG RAN WG2 #99, Berlin, Germany, Aug. 21-25, 2017, Source: LG Electronics, Title: DRX related timers in NR (Revision of R2-1706750).
[cited by applicant]