IP Library Granted Patent US 12,382,539
Granted Patent B2
US 12,382,539 · App. 18/411,405 · Granted Aug 5, 2025

Uplink and downlink synchronization procedures

Inventors: Ali Cagatay Cirik (Chantilly, VA); Esmael Hejazi Dinan (McLean, VA); Hua Zhou (Vienna, VA); Hyoungsuk Jeon (Centreville, VA); Alireza Babaei (Fairfax, VA); Kyungmin Park (Vienna, VA)
Assignee: Comcast Cable Communications, LLC
H04W74/0833H04B7/0695H04W24/08H04W72/23H04W76/11H04W76/27H04W80/02
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,382,539
App. No.
18/411,405
Granted
Aug 5, 2025
Kind
B2
Abstract

Uplink and downlink synchronization procedures are described for wireless communications. A base station may send a reconfiguration message to a wireless device before a random access procedure. The reconfiguration message may set an active uplink index and an active downlink index to the same value.

Claims (106)

1. A method comprising:

transmitting, by a base station and for beam failure recovery, a first active downlink bandwidth part (BWP) index for a cell and a first active uplink BWP index for the cell that are set to a same value by the base station; and

transmitting, via a first active downlink BWP associated with the first active downlink BWP index, a random access response to a random access preamble for beam failure recovery.

2. The method of claim 1 , further comprising:

after the first active uplink BWP index and the first active downlink BWP index are set to the same value, initiating beam failure recovery.

3. The method of claim 1 , further comprising:

based on detecting a beam failure of a first active downlink BWP associated with the first active downlink BWP index, initiating beam failure recovery.

4. The method of claim 1 , further comprising:

based on a quantity of beam failure instance indications of a first active downlink BWP associated with the first active downlink BWP index satisfying a threshold value, determining a beam failure.

5. The method of claim 1 , further comprising initiating beam failure recovery, wherein the initiating the beam failure recovery comprises:

selecting a reference signal associated with a random access channel resource; and

transmitting, based on the reference signal associated with the random access channel resource, the random access response.

6. The method of claim 5 , wherein the transmitting the random access response is via the random access channel resource.

7. The method of claim 1 , further comprising:

receiving, via a first active uplink BWP associated with the first active uplink BWP index, the random access preamble for beam failure recovery.

8. A method comprising:

receiving, by a wireless device, a first active downlink bandwidth part (BWP) index for a cell and a first active uplink BWP index for the cell that are set to a same value by a base station; and

receiving, via a first active downlink BWP associated with the first active downlink BWP index, a random access response to a random access preamble for beam failure recovery.

9. The method of claim 8 , further comprising:

based on determining that the first active uplink BWP index and the first active downlink BWP index are set to a same value, starting monitoring one or more reference signals associated with a random access procedure for the cell.

10. The method of claim 8 , further comprising:

receiving a radio resource control (RRC) reconfiguration message comprising the first active downlink BWP index and the first active uplink BWP index, wherein the RRC reconfiguration message comprises beam failure recovery (BFR) parameters, and wherein the BFR parameters comprise at least one of:

a first reference signal;

a beam failure instance counter; or

a random access channel resource.

11. The method of claim 10 , wherein the receiving the random access response is via the random access channel resource.

12. The method of claim 8 , further comprising:

monitoring a downlink control channel of the first active downlink BWP associated with the first active downlink BWP index.

13. The method of claim 8 , further comprising:

determining that a radio quality of one or more first reference signals is less than a threshold value, wherein the threshold value is based on one or more of:

beam failure recovery parameters; or

a hypothetical block error rate.

14. The method of claim 8 , further comprising:

transmitting, via a first active uplink BWP associated with the first active uplink BWP index, a random access preamble for beam failure recovery.

15. The method of claim 8 , further comprising:

activating, prior to the receiving the random access response, the first active downlink BWP associated with the first active downlink BWP index.

16. 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, for beam failure recovery, a first active downlink bandwidth part (BWP) index for a cell and a first active uplink BWP index for the cell that are set to a same value by the base station; and

transmit, via a first active downlink BWP associated with the first active downlink BWP index, a random access response to a random access preamble for beam failure recovery.

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

after the first active uplink BWP index and the first active downlink BWP index are set to the same value, initiate beam failure recovery.

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

based on detecting a beam failure of a first active downlink BWP associated with the first active downlink BWP index, initiate beam failure recovery.

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

based on a quantity of beam failure instance indications of a first active downlink BWP associated with the first active downlink BWP index satisfying a threshold value, determine a beam failure.

20. The base station of claim 16 , wherein the instructions, when executed by the one or more processors, further cause the base station to initiate beam failure recovery by causing:

selecting a reference signal associated with a random access channel resource; and

transmit, based on the reference signal associated with the random access channel resource, the random access response.

21. The base station of claim 20 , wherein the transmitting the random access response is via the random access channel resource.

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

receive, via a first active uplink BWP associated with the first active uplink BWP index, the random access preamble for beam failure recovery.

23. 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 a first active downlink bandwidth part (BWP) index for a cell and a first active uplink BWP index for the cell that are set to a same value by a base station; and

receive, via a first active downlink BWP associated with the first active downlink BWP index, a random access response to a random access preamble for beam failure recovery.

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

based on determining that the first active uplink BWP index and the first active downlink BWP index are set to a same value, start monitoring one or more reference signals associated with a random access procedure for the cell.

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

receive a radio resource control (RRC) reconfiguration message comprising the first active downlink BWP index and the first active uplink BWP index, wherein the RRC reconfiguration message comprises beam failure recovery (BFR) parameters, and wherein the BFR parameters comprise at least one of:

a first reference signal;

a beam failure instance counter; or

a random access channel resource.

26. The wireless device of claim 25 , wherein the receiving the random access response is via the random access channel resource.

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

monitor a downlink control channel of the first active downlink BWP associated with the first active downlink BWP index.

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

determine that a radio quality of one or more first reference signals is less than a threshold value, wherein the threshold value is based on one or more of:

beam failure recovery parameters; or

a hypothetical block error rate.

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

transmit, via a first active uplink BWP associated with the first active uplink BWP index, a random access preamble for beam failure recovery.

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

activate, prior to the receiving the random access response, the first active downlink BWP associated with the first active downlink BWP index.

31. A system comprising:

a base station comprising:

one or more processors; and

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

transmit, for beam failure recovery, a first active downlink bandwidth part (BWP) index for a cell and a first active uplink BWP index for the cell, wherein the first active uplink BWP index and the first active downlink BWP index are set to a same value by the base station; and

transmit, via a first active downlink BWP associated with the first active downlink BWP index, a random access response to a random access preamble for beam failure recovery; and

a wireless device comprising:

one or more processors; and

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

receive, via the first active downlink BWP, the random access response.

32. The system of claim 31 , wherein the instructions stored in the memory of the base station, when executed by the one or more processors of the base station, cause the base station to:

after the first active uplink BWP index and the first active downlink BWP index are set to the same value, initiate beam failure recovery.

33. The system of claim 31 , wherein the instructions stored in the memory of the base station, when executed by the one or more processors of the base station, cause the base station to:

based on detecting a beam failure of a first active downlink BWP associated with the first active downlink BWP index, initiate beam failure recovery.

34. The system of claim 31 , wherein the instructions stored in the memory of the base station, when executed by the one or more processors of the base station, cause the base station to:

based on a quantity of beam failure instance indications of a first active downlink BWP associated with the first active downlink BWP index satisfying a threshold value, determine a beam failure.

35. The system of claim 31 , wherein the instructions stored in the memory of the base station, when executed by the one or more processors of the base station, cause the base station to:

receive, via a first active uplink BWP associated with the first active uplink BWP index, the random access preamble for beam failure recovery.

36. The system of claim 31 , wherein the instructions stored in the memory of the wireless device, when executed by the one or more processors of the wireless device, cause the wireless device to:

based on determining that the first active uplink BWP index and the first active downlink BWP index are set to a same value, start monitoring one or more reference signals associated with a random access procedure for the cell.

37. The system of claim 31 , wherein the instructions stored in the memory of the wireless device, when executed by the one or more processors of the wireless device, cause the wireless device to:

monitor a downlink control channel of the first active downlink BWP associated with the first active downlink BWP index.

38. The system of claim 31 , wherein the instructions stored in the memory of the wireless device, when executed by the one or more processors of the wireless device, cause the wireless device to:

determine that a radio quality of one or more first reference signals is less than a threshold value, wherein the threshold value is based on one or more of:

beam failure recovery parameters; or

a hypothetical block error rate.

39. The system of claim 31 , wherein the instructions stored in the memory of the wireless device, when executed by the one or more processors of the wireless device, cause the wireless device to:

transmit, via a first active uplink BWP associated with the first active uplink BWP index, a random access preamble for beam failure recovery.

40. The system of claim 31 , wherein the instructions stored in the memory of the wireless device, when executed by the one or more processors of the wireless device, cause the wireless device to:

activate, prior to the receiving the random access response, the first active downlink BWP associated with the first active downlink BWP index.

Assignments (2)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 2, 2024
From: CIRIK, ALI CAGATAY; DINAN, ESMAEL HEJAZI; ZHOU, HUA; JEON, HYOUNGSUK; BABAEI, ALIREZA; PARK, KYUNGMIN
To: COMCAST CABLE COMMUNICATIONS, LLC
Reel/Frame 068761/0905 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 2, 2024
From: CIRIK, ALI CAGATAY; DINAN, ESMAEL HEJAZI; ZHOU, HUA; JEON, HYOUNGSUK; BABAEI, ALIREZA; PARK, KYUNGMIN
To: COMCAST CABLE COMMUNICATIONS, LLC
Reel/Frame 068761/0915 →
Continuity (4)
Continuation 17829894 · Jun 1, 2022
Continuation 16530122 · Aug 2, 2019
Provisional Application 62714205 · Aug 3, 2018
Related Publication 20240147540A1 · May 2, 2024
References Cited (153)
US 8976698B2 · Chen et al. · 2015 [cited by applicant]
US 10959271B2 · Yi · 2021 [cited by examiner]
US 11388755B2 · Cirik · 2022 [cited by examiner]
US 11917692B2 · Cirik · 2024 [cited by examiner]
US 20120113938A1 · Larsson · 2012 [cited by examiner]
US 20170026962A1 · Liu · 2017 [cited by examiner]
US 20170156152A1 · Nazar et al. · 2017 [cited by applicant]
US 20170238323A1 · Marinier et al. · 2017 [cited by applicant]
US 20170245165A1 · Onggosanusi et al. · 2017 [cited by applicant]
US 20170353223A1 · Kim et al. · 2017 [cited by applicant]
US 20180006701A1 · Ahn et al. · 2018 [cited by applicant]
US 20180049047A1 · Lin et al. · 2018 [cited by applicant]
US 20180049169A1 · Lin et al. · 2018 [cited by applicant]
US 20180124687A1 · Park et al. · 2018 [cited by applicant]
US 20180124815A1 · Papasakellariou · 2018 [cited by applicant]
US 20180131493A1 · Luo et al. · 2018 [cited by applicant]
US 20180183551A1 · Chou et al. · 2018 [cited by applicant]
US 20180287860A1 · Xia · 2018 [cited by examiner]
US 20190110300A1 · Chen · 2019 [cited by examiner]
US 20190132109A1 · Zhou et al. · 2019 [cited by applicant]
US 20190253949A1 · Park · 2019 [cited by examiner]
US 20190254110A1 · He et al. · 2019 [cited by applicant]
US 20200044723A1 · Cirik · 2020 [cited by examiner]
US 20200288508A1 · Shi · 2020 [cited by examiner]
EP 2672649A1 · 2013 [cited by applicant]
EP 3282633A1 · 2018 [cited by applicant]
WO 2011038243A2 · 2011 [cited by applicant]
WO 2011038243A3 · 2011 [cited by applicant]
WO 2011085230A2 · 2011 [cited by applicant]
WO 2017197155A1 · 2017 [cited by applicant]
WO 2018021834A1 · 2018 [cited by applicant]
WO 2018031638A1 · 2018 [cited by applicant]
WO 2018031924A1 · 2018 [cited by applicant]
WO 2018044116A1 · 2018 [cited by applicant]
WO 2018080260A1 · 2018 [cited by applicant]
WO 2018084544A1 · 2018 [cited by applicant]
WO 2018084571A1 · 2018 [cited by applicant]
WO 2018085145A1 · 2018 [cited by applicant]
WO 2018089117A1 · 2018 [cited by applicant]
WO 2018145019A1 · 2018 [cited by applicant]
R1-1715454 3GPP TSG RAN WG1 Meeting NR Ad Hoc, Nagoya, Japan, Sep. 18-21, 2017, Source: ZTE, Sanechips, Title: On NR Power Control. [cited by applicant]
R1-1715478 3GPP TSG RAN WG1 Meeting NR Ad Hoc, Nagoya, Japan, Sep. 18-21, 2017, Source: Huawei, HiSilicon, Title: General considerations on UL power control design. [cited by applicant]
R1-1715505 3GPP TSG RAN WG1 Meeting NR Ad Hoc, Nagoya, Japan, Sep. 18-21, 2017, Source: Mitsubishi Electric, Title: UL transmission power control. [cited by applicant]
R1-1715651 3GPP TSG RAN WG1 Meeting NR Ad Hoc, Nagoya, Japan, Sep. 18-21, 2017, Source: vivo, Title: NR UL power control framework. [cited by applicant]
R1-1715675 3GPP TSG RAN WG1 Meeting NR Ad Hoc, Nagoya, Japan, Sep. 18-21, 2017, Source: Guangdong OPPO Mobile Telecom, Title: Uplink power control mechanism for NR. [cited by applicant]
R1-1715838 3GPP TSG RAN WG1 Meeting NR Ad Hoc, Nagoya, Japan, Sep. 18-21, 2017, Source: CATT, Title: NR Power Control Framework. [cited by applicant]
R1-1715902 3GPP TSG RAN WG1 Meeting NR Ad Hoc, Nagoya, Japan, Sep. 18-21, 2017, Source: LG Electronics, Title: Discussion on UL power control for NR. [cited by applicant]
R1-1716040 3GPP TSG RAN WG1 Meeting NR Ad Hoc, Nagoya, Japan, Sep. 18-21, 2017, Source: Samsung, Title: On UL Power Control. [cited by applicant]
R1-1716061 3GPP TSG RAN WG1 Meeting NR Ad Hoc, Nagoya, Japan, Sep. 18-21, 2017, Source: CMCC, Title: Discussion on power control framework. [cited by applicant]
R1-1716114 3GPP TSG RAN WG1 Meeting NR Ad Hoc, Nagoya, Japan, Sep. 18-21, 2017, Source: NTT Docomo, Inc., Title: Power control framework for PUSCH. [cited by applicant]
R1-1716127 3GPP TSG RAN WG1 Meeting NR Ad Hoc, Nagoya, Japan, Sep. 18-21, 2017, Source: Nokia, Nokia Shanghai Bell, Title: Discussion on NR power control framework. [cited by applicant]
R1-1716451 3GPP TSG RAN WG1 Meeting NR Ad Hoc, Nagoya, Japan, Sep. 18-21, 2017, Source: Qualcomm Incorporated, Title: Power control and PHR for NR. [cited by applicant]
R1-1716515 3GPP TSG RAN WG1 Meeting NR Ad Hoc, Nagoya, Japan, Sep. 18-21, 2017, Source: InterDigital Inc., Title: Further Details on Uplink Power Control. [cited by applicant]
R1-1716535 3GPP TSG RAN WG1 Meeting NR Ad Hoc, Nagoya, Japan, Sep. 18-21, 2017, Source: Panasonic, Title: Discussion on NR power control framework. [cited by applicant]
R1-1716604 3GPP TSG RAN WG1 Meeting NR Ad Hoc, Nagoya, Japan, Sep. 18-21, 2017, Source: Ericsson, Title: NR UL power control framework. [cited by applicant]
R1-1716606 3GPP TSG RAN WG1 Meeting NR Ad Hoc, Nagoya, Japan, Sep. 18-21, 2017, Source: Ericsson, Title: Closed loop PC in NR. [cited by applicant]
R1-1717311 3GPP TSG RAN WG1 Meeting NR Ad Hoc, Nagoya, Japan, Sep. 18-21, 2017, Source: Huawei, HiSilicon, Title: General considerations on UL power control design. [cited by applicant]
R1-1717408 3GPP TSG RAN WG1 Meeting #90bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: Intel Corporation, Title: Remaining Details On UL Power Control Framework. [cited by applicant]
R1-1717438 3GPP TSG RAN WG1 Meeting #90bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: ZTE, Sanechips, Title: On NR Power Control. [cited by applicant]
R1-1717508 3GPP TSG RAN WG1 Meeting #90bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: vivo, Title: Remaining issues on NR UL power control. [cited by applicant]
R1-1717692 3GPP TSG RAN WG1 Meeting #90bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: Samsung, Title: On UL Power Control. [cited by applicant]
R1-1717846 3GPP TSG RAN WG1 Meeting NR Ad Hoc, Nagoya, Japan, Sep. 18-21, 2017, Source: CATT, Title: NR Power Control Aspects. [cited by applicant]
R1-1717892 3GPP TSG RAN WG1 Meeting #90bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: CMCC, Title: Discussion on power control framework. [cited by applicant]
R1-1717919 3GPP TSG RAN WG1 Meeting #90bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: Panasonic, Title: Discussion on NR power control framework. [cited by applicant]
R1-1717983 3GPP TSG RAN WG1 Meeting #90bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: LG Electronics, Title: Discussion on UL power control for NR. [cited by applicant]
R1-1718031 3GPP TSG RAN WG1 Meeting #90bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: OPPO, Title: On uplink power control for NR. [cited by applicant]
R1-1718228 3GPP TSG RAN WG1 Meeting #90bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: NTT Docomo, Inc., Title: Power control framework for PUSCH. [cited by applicant]
R1-1718502 3GPP TSG RAN WG1 Meeting #90bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: InterDigital, Inc., Title: On NR Power Control Framework. [cited by applicant]
R1-1718592 3GPP TSG RAN WG1 Meeting #90bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: Qualcomm Incorporated, Title: Power control and PHR for NR. [cited by applicant]
R1-1718625 3GPP TSG RAN WG1 Meeting #90bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: ITL, Title: UL power control and PHR. [cited by applicant]
R1-1718652 3GPP TSG RAN WG1 Meeting #90bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: Ericsson, Title: NR power control framework. [cited by applicant]
R1-1718655 3GPP TSG RAN WG1 Meeting #90bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: Ericsson, Title: Further details on closed loop power control. [cited by applicant]
R1-1718692 3GPP TSG RAN WG1 Meeting #90bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: Nokia, Nokia Shanghai Bell, Title: Discussion on NR power control framework. [cited by applicant]
R1-1718704 3GPP TSG RAN WG1 Meeting #90bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: Motorola Mobility, Lenovo, Title: On NR power control. [cited by applicant]
3GPP TS 36.413 V13.3.0 (Jun. 2016), Technical Specification, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Appli… [cited by applicant]
3GPP TS 36.321 V10.3.0 (Sep. 2011), Technical Specification, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Con… [cited by applicant]
3GPP TS 36.321 V14.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 Con… [cited by applicant]
3GPP TS 36.331 V14.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 Co… [cited by applicant]
3GPP TSG RAN WG1 Meeting #90bis, Prague, Czech Republic, Oct. 9-13, 2017, Title: RAN1 Chairman's Notes. [cited by applicant]
3GPP TSG RAN WG1 Meeting #93, Busan, Korea, May 21-25, 2018, Title: RAN1 Chairman's Notes. [cited by applicant]
3GPP TSG RAN WG2 NR Ad Hoc, Vancouver, Canada, Jan. 22-26, 2018, Source: Session Chair (InterDigital), Title: Report from LTE and NR User Plane Break-Out Session. [cited by applicant]
R2-1711835 3GPP TSG RAN WG2 Meeting #99bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: Session Chair (InterDigital), Title: Report from LTE and NR User Plane Break-Out Session. [cited by applicant]
R1-1716353 3GPP TSG RAN WG1 Meeting NR Ad Hoc, Nagoya, Japan, Sep. 18-21, 2017, Source: Ericsson, Title: On dynamic triggering for CSI reports and CSI-RS. [cited by applicant]
R1-1716354 3GPP TSG RAN WG1 Meeting NR Ad Hoc, Nagoya, Japan, Sep. 18-21, 2017, Source: Ericsson, Title: A comparison of CSI-RS activation schemes based on MAC CE and DCI. [cited by applicant]
R1-1716357 3GPP TSG RAN WG1 Meeting NR Ad Hoc, Nagoya, Japan, Sep. 18-21, 2017, Source: Ericsson, Title: On semi-persistent CSI reporting on PUSCH. [cited by applicant]
R1-1717939 3GPP TSG RAN WG1 Meeting #90bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: LG Electronics, Title: Discussion on CSI measurement. [cited by applicant]
R1-1801073 3GPP TSG RAN WG1 NR Ad Hoc, Vancouver, Canada, Jan. 22-26, 2018, Source: RAN2, Title: LS on PDCCH order for initiation of random access. [cited by applicant]
R1-1805701 3GPP TSG RAN WG1 Meeting #92bis, Sanya, China, Apr. 16-20, 2018, Source: Qualcomm Incorporated, Title: Summary of Remaining Details on RACH Procedure. [cited by applicant]
R1-1805876 3GPP TSG RAN WG1 Meeting #93, Busan, Korea, May 21-25, 2018, Source: Huawei, HiSilicon, Title: Remaining details of RACH Procedures. [cited by applicant]
R1-1807747 3GPP TSG RAN WG1 Meeting #93, Busan, Korea, May 21-25, 2018, Source: Qualcomm Incorporated, Title: Summary of Remaining Details on RACH Procedure. [cited by applicant]
Jan. 16, 2019—European Search Report—EP 18202948.8. [cited by applicant]
OPPO “SPS operations for BWP switching” Oct. 8, 2017. [cited by applicant]
Ericsson “URLLC aspects for grant-free UL transmission in NR” Feb. 12, 2017. [cited by applicant]
Mar. 29, 2019—Extended European Search Report—EP 18205418.9. [cited by applicant]
Jun. 28, 2019—European Extended Search Report—19166254.3. [cited by applicant]
Huawei, HiSilicon: “Bandwidth part activation and adaptation”, Sep. 18, 2017. [cited by applicant]
InterDigital, Inc.: “Remaining details of BWP”, Sep. 18, 2017. [cited by applicant]
LG Electronics: “Discussion on carrier aggregation and bandwidth parts”, Sep. 18, 2017. [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 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]
Jul. 10, 2019—European Extended Search Report—EP 19175762.4. [cited by applicant]
3GPP TSG-RAN WG2 Meeting #102: “Email Discussion on SSB and Cell relationship”, May 21, 2018. [cited by applicant]
3GPP TSG RAN WG1 Meeting #93: “Remaining Issues on Beam Management”, May 21, 2018. [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]
R1-1715425 3GPP TSG RAN WG1 Meeting NR Ad Hoc, Nagoya, Japan, Sep. 18-21, 2017, Source: Huawei, HiSilicon, Title: Overview of bandwidth part, CA, and DC operation including SRS switching. [cited by applicant]
R1-1715492 3GPP TSG RAN WG1 Meeting NR Ad Hoc, Nagoya, Japan, Sep. 18-21, 2017, Source: Fujitsu, Title: Considerations on UCI feedback for carrier aggregation. [cited by applicant]
R1-1715517 3GPP TSG RAN WG1 Meeting NR Ad Hoc, Nagoya, Japan, Sep. 18-21, 2017, Source: Spreadtrum Communications, Title: Consideration on monitoring preemption indication in bandwidth parts. [cited by applicant]
R1-1715535 3GPP TSG RAN WG1 Meeting NR Ad Hoc, Nagoya, Japan, Sep. 18-21, 2017, Source: Lenovo, Motorola Mobility, Title: HARQ-ACK codebook size determination for CA with different numerologies. [cited by applicant]
R1-1715648 3GPP TSG RAN WG1 Meeting NR Ad Hoc, Nagoya, Japan, Sep. 18-21, 2017, Source: vivo, Title: Remaining details for bandwidth part operation. [cited by applicant]
R1-1715692 3GPP TSG RAN WG1 Meeting NR Ad Hoc, Nagoya, Japan, Sep. 18-21, 2017, Source: Guangdong OPPO Mobile Telecom, Title: Remaining issues on bandwidth part configuration and activation. [cited by applicant]
R1-1715755 3GPP TSG RAN WG1 Meeting NR Ad Hoc, Nagoya, Japan, Sep. 18-21, 2017, Source: Nokia, Nokia Shanghai Bell, Title: On remaining aspects of NR CA/DC and BWPs. [cited by applicant]
R1-1715770 3GPP TSG RAN WG1 Meeting NR Ad Hoc, Nagoya, Japan, Sep. 18-21, 2017, Source: ETRI, Title: Remaining details of bandwidth part for initial access. [cited by applicant]
R1-1715774 3GPP TSG RAN WG1 Meeting NR Ad Hoc, Nagoya, Japan, Sep. 18-21, 2017, Source: Panasonic, Title: Combining DRX with BWP adaptation. [cited by applicant]
R1-1715830 3GPP TSG RAN WG1 Meeting NR Ad Hoc, Nagoya, Japan, Sep. 18-21, 2017, Source: CATT, Title: Remaining aspects of CA and wider bandwidth operation. [cited by applicant]
R1-1715892 3GPP TSG RAN WG1 Meeting NR Ad Hoc, Nagoya, Japan, Sep. 18-21, 2017, Source: LG Electronics, Title: Discussion on carrier aggregation and bandwidth parts. [cited by applicant]
R1-1716019 3GPP TSG RAN WG1 Meeting NR Ad Hoc, Nagoya, Japan, Sep. 18-21, 2017, Source: Samsung, Title: On Bandwidth Part Operation. [cited by applicant]
R1-1716109 3GPP TSG RAN WG1 Meeting NR Ad Hoc, Nagoya, Japan, Sep. 18-21, 2017, Source: NTT Docomo,Inc., Title: Remaining issues on bandwidth parts for NR. [cited by applicant]
R1-1716192 3GPP TSG RAN WG1 Meeting NR Ad Hoc, Nagoya, Japan, Sep. 18-21, 2017, Source: AT&T, Title: Remaining Details of Carrier Aggregation and Bandwidth Parts. [cited by applicant]
R1-1716202 3GPP TSG RAN WG1 Meeting NR Ad Hoc, Nagoya, Japan, Sep. 18-21, 2017, Source: MediaTek Inc., Title: Remaining Details on Bandwidth Part Operation in NR. [cited by applicant]
R1-1716258 3GPP TSG RAN WG1 Meeting NR Ad Hoc, Nagoya, Japan, Sep. 18-21, 2017, Source: InterDigital, Inc., Title: Remaining details of BWP. [cited by applicant]
R1-1716327 3GPP TSG RAN WG1 Meeting NR Ad Hoc, Nagoya, Japan, Sep. 18-21, 2017, Source: Intel Corporation, Title: Remaining aspects for carrier aggregation and bandwidth parts. [cited by applicant]
R1-1716440 3GPP TSG RAN WG1 Meeting NR Ad Hoc, Nagoya, Japan, Sep. 18-21, 2017, Source: Qualcomm Incorporated, Title: CA and BWP. [cited by applicant]
R1-1716601 3GPP TSG RAN WG1 Meeting NR Ad Hoc, Nagoya, Japan, Sep. 18-21, 2017, Source: Ericsson, Title: On CA related aspects and BWP related aspects. [cited by applicant]
R1-1716647 3GPP TSG RAN WG1 Meeting NR Ad Hoc, Nagoya, Japan, Sep. 18-21, 2017, Source: Convida Wireless, Title: Discussion on BWP Design. [cited by applicant]
R1-1717077 3GPP TSG RAN WG1 Meeting #90bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: Huawei, HiSilicon, Title: Remaining issues on bandwidth part. [cited by applicant]
R1-1717400 3GPP TSG RAN WG1 Meeting #90bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: Intel Corporation, Title: Remaining details for bandwidth parts. [cited by applicant]
R1-1717504 3GPP TSG RAN WG1 Meeting #90bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: vivo, Title: Remaining details for bandwidth part operation. [cited by applicant]
R1-1717675 3GPP TSG RAN WG1 Meeting #90bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: Samsung, Title: On Bandwidth Part Operation. [cited by applicant]
R1-1717839 3GPP TSG RAN WG1 Meeting #90bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: CATT, Title: Remaining aspects of BWP operation. [cited by applicant]
R1-1717972 3GPP TSG RAN WG1 Meeting #90bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: LG Electronics, Title: Remaining issues on bandwidth parts. [cited by applicant]
R1-1718050 3GPP TSG RAN WG1 Meeting #90bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: OPPO, Title: Remaining issues on bandwidth part configuration and activation. [cited by applicant]
R1-1718223 3GPP TSG RAN WG1 Meeting #90bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: NTT Docomo, Inc., Title: Remaining issues on bandwidth parts for NR. [cited by applicant]
R1-1718327 3GPP TSG RAN WG1 Meeting #90bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: MediaTek Inc., Title: Remaining Details on Bandwidth Part Operation in NR. [cited by applicant]
R1-1718365 3GPP TSG RAN WG1 Meeting #90bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: InterDigital, Inc., Title: Remaining details of BWP. [cited by applicant]
R1-1718404 3GPP TSG RAN WG1 Meeting #90bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: AT&T, Title: Remaining details for bandwidth parts. [cited by applicant]
R1-1718523 3GPP TSG RAN WG1 Meeting #90bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: Ericsson, Title: On bandwidth parties. [cited by applicant]
R1-1718580 3GPP TSG RAN WG1 Meeting #90bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: Qualcomm Incorporated, Title: Open Issues on BWP. [cited by applicant]
R1-1718607 3GPP TSG RAN WG1 Meeting #90bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: Nokia, Nokia Shanghai Bell, Title: On remaining aspects of BWPs. [cited by applicant]
R2-1800688 3GPP TSG RAN WG2 NR Ad Hoc, Vancouver, Canada, Jan. 22-26, 2018, Source: Ericsson, Title: Need for PDCCH order. [cited by applicant]
Sep. 9, 2019—European Extended Search Report—EP 19174705.4. [cited by applicant]
Sep. 16, 2019—European Extended Search Report—EP 19175772.3. [cited by applicant]
R2-1712212 3GPP TSG RAN WG2 Meeting #100, Reno, USA, Nov. 27-Dec. 1, 2017, Source: ASUSTek, Title: Details of BWP inactivity timer. [cited by applicant]
Sep. 26, 2019—European Extended Search Report—EP 19175077.7. [cited by applicant]
R1-1718581 3GPP TSG RAN WG1 Meeting #90bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: Qualcomm Incorporated, Title: Open Issues on CA. [cited by applicant]
R1-1718901 3GPP TSG RAN WG1 Meeting 90bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: MediaTek Inc., Title: Summary of Bandwidth Part Operation. [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]
Nov. 22, 2019—European Office Action—EP 18205418.9. [cited by applicant]
Jan. 3, 2020—European Extended Search Report—EP 19189782.6. [cited by applicant]
R2-1806991 3GPP TSG RAN WG2 Meeting #102, Busan, Korea, May 21-25, 2018, Source: CATT, Title: Further issues with switching of bandwidth part and random access. [cited by applicant]
R2-1810513 3GPP TSG RAN WG2 NR AH1807, Montreal, Canada, Jul. 2-6, 2018, Source: Huawei, HiSilicon, Title: Clarification on RA procedure for BFR on BWPs without CBRA occasions. [cited by applicant]
Jun. 1, 2021—European Office Action—EP 19189782.6. [cited by applicant]