IP Library › Granted Patent US 12,395,968
Granted Patent B2
US 12,395,968 · App. 18/135,544 · Granted Aug 19, 2025

Random access procedures using multiple active bandwidth parts

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/0833H04L5/0098H04W24/08H04W72/04H04W72/0453H04W72/23H04W74/02H04W76/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,395,968
App. No.
18/135,544
Granted
Aug 19, 2025
Kind
B2
Abstract

Wireless communications using multiple active resources (e.g., bandwidth parts (BWP)) are described. A predetermined rule may be used to determine on which downlink (DL) BWP of multiple active DL BWPs, and/or on which uplink (UL) BWP of multiple active UL BWPs, a message is to be sent. A wireless device and/or a base station may reduce the quantity of active DL BWPs and/or active UL BWPs to monitor for a response.

Claims (119)

1. A method comprising:

based on a plurality of downlink bandwidth part (BWP) indexes associated with a plurality of active downlink BWPs being different from an uplink BWP index associated with an active uplink BWP, activating, by a wireless device, a first downlink BWP associated with the uplink BWP index; and

sending, via the uplink BWP, a preamble for a random access procedure.

2. The method of claim 1 , further comprising:

monitoring at least one downlink control channel of the first downlink BWP for a random access response; and

based on the activating the first downlink BWP, deactivating a second downlink BWP of the plurality of downlink BWPs.

3. The method of claim 1 , wherein the activating the first downlink BWP comprises activating the first downlink BWP in a first slot, the method further comprising:

activating a second downlink BWP, of the plurality of downlink BWPs, in a second slot; and

activating the uplink BWP in a third slot, wherein each of the first slot, the second slot, and the third slot are different slots.

4. The method of claim 1 , further comprising determining the first downlink BWP for activation based on at least one of:

a lowest or highest downlink BWP index relative to the plurality of downlink BWP indexes; or

a lowest or highest BWP numerology relative to BWP numerologies associated with the plurality of downlink BWPs.

5. The method of claim 1 , further comprising:

determining the first downlink BWP for activation based on whether the first downlink BWP comprises a primary BWP or a secondary BWP.

6. The method of claim 1 , further comprising:

determining the first downlink BWP for activation based on whether the first downlink BWP comprises a default BWP or a non-default BWP.

7. The method of claim 1 , further comprising:

switching from a second downlink BWP, of the plurality of downlink BWPs, to the first downlink BWP.

8. The method of claim 7 , wherein the switching from the second downlink BWP to the first downlink BWP comprises deactivating the second downlink BWP.

9. The method of claim 1 , further comprising:

activating, by the wireless device, the plurality of downlink BWPs and the uplink BWP.

10. A method comprising:

based on a plurality of downlink bandwidth part (BWP) indexes associated with a plurality of active downlink BWPs being different from an uplink BWP index associated with an active uplink BWP, switching, by a wireless device, to a downlink BWP of the plurality of downlink BWPs as an active BWP, wherein the downlink BWP is associated with the uplink BWP index; and

sending, via the uplink BWP, a preamble for a random access procedure.

11. The method of claim 10 , further comprising:

activating the downlink BWP; and

monitoring at least one downlink control channel of the downlink BWP for a random access response.

12. The method of claim 10 , further comprising:

activating, as a first active downlink BWP, the downlink BWP in a first slot; and

activating the uplink BWP in a second slot, wherein each of the first slot and the second slot are different slots.

13. The method of claim 10 , wherein the switching comprises switching from a second downlink BWP of the plurality of downlink BWPs to the downlink BWP, the method further comprising selecting the second downlink BWP based on a determination of a downlink BWP associated with at least one of:

a lowest or highest downlink BWP index relative to the plurality of downlink BWP indexes; or

a lowest or highest BWP numerology relative to BWP numerologies associated with the plurality of downlink BWPs.

14. The method of claim 10 , wherein the switching comprises switching from a second downlink BWP of the plurality of downlink BWPs to the downlink BWP, the method further comprising selecting the second downlink BWP based on a determination of whether the second downlink BWP comprises a primary BWP or a secondary BWP.

15. The method of claim 10 , wherein the switching comprises switching from a second downlink BWP of the plurality of downlink BWPs to the downlink BWP, the method further comprising selecting the second downlink BWP based on a determination of whether the second downlink BWP comprises a default BWP or a non-default BWP.

16. The method of claim 10 , wherein the switching comprises switching from a second downlink BWP to the downlink BWP, the method further comprising maintaining the second downlink BWP in an active state.

17. The method of claim 10 , wherein the switching comprises switching from a second downlink BWP to the downlink BWP, the method further comprising deactivating the second downlink BWP.

18. The method of claim 10 , wherein each of the plurality of downlink BWP indexes is different from all the other downlink BWP indexes of the plurality of downlink BWP indexes.

19. 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:

based on a plurality of downlink bandwidth part (BWP) indexes associated with a plurality of active downlink BWPs being different from an uplink BWP index associated with an active uplink BWP, activate a first downlink BWP associated with the uplink BWP index; and

send, via the uplink BWP, a preamble for a random access procedure.

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

monitor at least one downlink control channel of the first downlink BWP for a random access response; and

based on the activating the first downlink BWP, deactivate a second downlink BWP of the plurality of downlink BWPs.

21. The wireless device of claim 19 , wherein the instructions, when executed by the one or more processors, cause the wireless device to activate the first downlink BWP by causing activating the first downlink BWP in a first slot, and wherein the instructions, when executed by the one or more processors, further cause the wireless device to:

activate a second downlink BWP, of the plurality of downlink BWPs, in a second slot; and

activate the uplink BWP in a third slot, wherein each of the first slot, the second slot, and the third slot are different slots.

22. The wireless device of claim 19 , wherein the instructions, when executed by the one or more processors, cause the wireless device to determine the first downlink BWP for activation based on at least one of:

a lowest or highest downlink BWP index relative to the plurality of downlink BWP indexes; or

a lowest or highest BWP numerology relative to BWP numerologies associated with the plurality of downlink BWPs.

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

determine the first downlink BWP for activation based on whether the first downlink BWP comprises a primary BWP or a secondary BWP.

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

determine the first downlink BWP for activation based on whether the first downlink BWP comprises a default BWP or a non-default BWP.

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

switch from a second downlink BWP, of the plurality of downlink BWPs, to the first downlink BWP.

26. The wireless device of claim 25 , wherein the instructions, when executed by the one or more processors, cause the wireless device to switch from the second downlink BWP to the first downlink BWP by causing deactivating the second downlink BWP.

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

activate the plurality of downlink BWPs and the uplink BWP.

28. A wireless device comprising:

one or more processors; and

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

activate a plurality of downlink bandwidth parts (BWPs), associated with a plurality of downlink BWP indexes, and an uplink BWP;

based on the plurality of downlink BWP indexes being different from an uplink BWP index associated with the uplink BWP, switch to a downlink BWP of the plurality of downlink BWPs as an active BWP, wherein the downlink BWP is associated with the uplink BWP index; and

send, via the uplink BWP, a preamble for a random access procedure.

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

activate the downlink BWP; and

monitor at least one downlink control channel of the downlink BWP for a random access response.

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

activate, as a first active downlink BWP, the downlink BWP in a first slot; and

activate the uplink BWP in a second slot, wherein each of the first slot and the second slot are different slots.

31. The wireless device of claim 28 , wherein the instructions, when executed by the one or more processors, cause the wireless device to switch from a second downlink BWP of the plurality of downlink BWPs to the downlink BWP, wherein the instructions, when executed by the one or more processors, further cause the wireless device to select the second downlink BWP based on a determination of a downlink BWP associated with at least one of:

a lowest or highest downlink BWP index relative to the plurality of downlink BWP indexes; or

a lowest or highest BWP numerology relative to BWP numerologies associated with the plurality of downlink BWPs.

32. The wireless device of claim 28 , wherein the instructions, when executed by the one or more processors, cause the wireless device to switch from a second downlink BWP of the plurality of downlink BWPs to the downlink BWP, wherein the instructions, when executed by the one or more processors, further cause the wireless device to select the second downlink BWP based on a determination of whether the second downlink BWP comprises a primary BWP or a secondary BWP.

33. The wireless device of claim 28 , wherein the instructions, when executed by the one or more processors, cause the wireless device to switch from a second downlink BWP of the plurality of downlink BWPs to the downlink BWP, wherein the instructions, when executed by the one or more processors, further cause the wireless device to select the second downlink BWP based on a determination of whether the second downlink BWP comprises a default BWP or a non-default BWP.

34. The wireless device of claim 28 , wherein the instructions, when executed by the one or more processors, cause the wireless device to switch from a second downlink BWP to the downlink BWP, wherein the instructions, when executed by the one or more processors, further cause the wireless device to maintain the second downlink BWP in an active state.

35. The wireless device of claim 28 , wherein the instructions, when executed by the one or more processors, cause the wireless device to switch from a second downlink BWP to the downlink BWP, wherein the instructions, when executed by the one or more processors, further cause the wireless device to deactivate the second downlink BWP.

36. The wireless device of claim 28 , wherein each of the plurality of downlink BWP indexes is different from all the other downlink BWP indexes of the plurality of downlink BWP indexes.

37. One or more non-transitory computer readable media storing instructions that, when executed cause:

based on a plurality of downlink bandwidth part (BWP) indexes associated with a plurality of active downlink BWPs being different from an uplink BWP index associated with an active uplink BWP, activating a first downlink BWP associated with the uplink BWP index; and

sending, via the uplink BWP, a preamble for a random access procedure.

38. The one or more non-transitory computer readable media of claim 37 , wherein the instructions, when executed, further cause:

monitoring at least one downlink control channel of the first downlink BWP for a random access response; and

based on the activating the first downlink BWP, deactivating a second downlink BWP of the plurality of downlink BWPs.

39. The one or more non-transitory computer readable media of claim 37 , wherein the instructions, when executed, cause the activating the first downlink BWP by activating the first downlink BWP in a first slot, and wherein the instructions, when executed, further cause:

activating a second downlink BWP, of the plurality of downlink BWPs, in a second slot; and

activating the uplink BWP in a third slot, wherein each of the first slot, the second slot, and the third slot are different slots.

40. The one or more non-transitory computer readable media of claim 37 , wherein the instructions, when executed, further cause determining the first downlink BWP for activation based on at least one of:

a lowest or highest downlink BWP index relative to the plurality of downlink BWP indexes; or

a lowest or highest BWP numerology relative to BWP numerologies associated with the plurality of downlink BWPs.

41. The one or more non-transitory computer readable media of claim 37 , wherein the instructions, when executed, further cause:

determining the first downlink BWP for activation based on whether the first downlink BWP comprises a primary BWP or a secondary BWP.

42. The one or more non-transitory computer readable media of claim 37 , wherein the instructions, when executed, further cause:

determining the first downlink BWP for activation based on whether the first downlink BWP comprises a default BWP or a non-default BWP.

43. The one or more non-transitory computer readable media of claim 37 , wherein the instructions, when executed, further cause:

switching from a second downlink BWP, of the plurality of downlink BWPs, to the first downlink BWP.

44. The one or more non-transitory computer readable media of claim 43 , wherein the instructions, when executed, further cause switching from the second downlink BWP to the first downlink BWP by causing deactivating the second downlink BWP.

45. The one or more non-transitory computer readable media of claim 37 , wherein the instructions, when executed, further cause:

activating the plurality of downlink BWPs and the uplink BWP.

46. One or more non-transitory computer readable media storing instructions that, when executed cause:

based on a plurality of downlink bandwidth part (BWP) indexes associated with a plurality of active downlink BWPs being different from an uplink BWP index associated with an active uplink BWP, switching to a downlink BWP of the plurality of downlink BWPs as an active BWP, wherein the downlink BWP is associated with the uplink BWP index; and

sending, via the uplink BWP, a preamble for a random access procedure.

47. The one or more non-transitory computer readable media of claim 46 , wherein the instructions, when executed, further cause:

activating the downlink BWP; and

monitoring at least one downlink control channel of the downlink BWP for a random access response.

48. The one or more non-transitory computer readable media of claim 46 , wherein the instructions, when executed, further cause:

activating, as a first active downlink BWP, the downlink BWP in a first slot; and

activating the uplink BWP in a second slot, wherein each of the first slot and the second slot are different slots.

49. The one or more non-transitory computer readable media of claim 46 , wherein the instructions, when executed, cause switching to the downlink BWP by causing switching from a second downlink BWP of the plurality of downlink BWPs to the downlink BWP, and wherein the instructions, when executed, further cause selecting the second downlink BWP based on a determination of a downlink BWP associated with at least one of:

a lowest or highest downlink BWP index relative to the plurality of downlink BWP indexes; or

a lowest or highest BWP numerology relative to BWP numerologies associated with the plurality of downlink BWPs.

50. The one or more non-transitory computer readable media of claim 46 , wherein the instructions, when executed, cause switching to the downlink BWP by causing switching from a second downlink BWP of the plurality of downlink BWPs to the downlink BWP, and wherein the instructions, when executed, further cause selecting the second downlink BWP based on a determination of whether the second downlink BWP comprises a primary BWP or a secondary BWP.

51. The one or more non-transitory computer readable media of claim 46 , wherein the instructions, when executed, cause switching to the downlink BWP by causing switching from a second downlink BWP of the plurality of downlink BWPs to the downlink BWP, and wherein the instructions, when executed, further cause selecting the second downlink BWP based on a determination of whether the second downlink BWP comprises a default BWP or a non-default BWP.

52. The one or more non-transitory computer readable media of claim 46 , wherein the instructions, when executed, cause switching to the downlink BWP by causing switching from a second downlink BWP to the downlink BWP, and wherein the instructions, when executed, further cause maintaining the second downlink BWP in an active state.

53. The one or more non-transitory computer readable media of claim 46 , wherein the instructions, when executed, cause switching to the downlink BWP by causing switching from a second downlink BWP to the downlink BWP, and wherein the instructions, when executed, further cause deactivating the second downlink BWP.

54. The one or more non-transitory computer readable media of claim 46 , wherein each of the plurality of downlink BWP indexes is different from all the other downlink BWP indexes of the plurality of downlink BWP indexes.

Assignments (4)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 29, 2023
From: CIRIK, ALI CAGATAY; DINAN, ESMAEL HEJAZI; ZHOU, HUA; JEON, HYOUNGSUK; BABAEI, ALIREZA; PARK, KYUNGMIN
To: COMCAST CABLE COMMUNICATIONS, LLC
Reel/Frame 065071/0218 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 29, 2023
From: CIRIK, ALI CAGATAY; DINAN, ESMAEL HEJAZI; ZHOU, HUA; JEON, HYOUNGSUK; BABAEI, ALIREZA
To: COMCAST CABLE COMMUNICATIONS, LLC
Reel/Frame 065069/0146 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 29, 2023
From: CIRIK, ALI CAGATAY; DINAN, ESMAEL HEJAZI; ZHOU, HUA; JEON, HYOUNGSUK; BABAEI, ALIREZA; PARK, KYUNGMIN
To: COMCAST CABLE COMMUNICATIONS, LLC
Reel/Frame 065069/0151 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 29, 2023
From: CIRIK, ALI CAGATAY; DINAN, ESMAEL HEJAZI; ZHOU, HUA; JEON, HYOUNGSUK; BABAEI, ALIREZA
To: COMCAST CABLE COMMUNICATIONS, LLC
Reel/Frame 065069/0156 →
Continuity (7)
Continuation 16950631 · Nov 17, 2020
Continuation 16418411 · May 21, 2019
Continuation 16418078 · May 21, 2019
Provisional Application 62688421 · Jun 22, 2018
Provisional Application 62674904 · May 22, 2018
Provisional Application 62674550 · May 21, 2018
Related Publication 20230379973A1 · Nov 23, 2023
References Cited (170)
US 8976698B2 · Chen et al. · 2015 [cited by applicant]
US 9210676B2 · Dinan · 2015 [cited by applicant]
US 10750534B2 · Son · 2020 [cited by applicant]
US 20140198746A1 · Ahn et al. · 2014 [cited by applicant]
US 20150043505A1 · Kim et al. · 2015 [cited by applicant]
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 20190132109A1 · Zhou et al. · 2019 [cited by applicant]
US 20190149308A1 · Son · 2019 [cited by applicant]
US 20190166529A1 · Chen et al. · 2019 [cited by applicant]
US 20190208548A1 · Shih et al. · 2019 [cited by applicant]
US 20190215130A1 · Aiba et al. · 2019 [cited by applicant]
US 20190215847A1 · Abdoli et al. · 2019 [cited by applicant]
US 20190215869A1 · Lin · 2019 [cited by applicant]
US 20190222290A1 · Ly et al. · 2019 [cited by applicant]
US 20190222404A1 · Ang et al. · 2019 [cited by applicant]
US 20190253531A1 · Basu Mallick et al. · 2019 [cited by applicant]
US 20190254110A1 · He et al. · 2019 [cited by applicant]
US 20190335508A1 · Agiwal et al. · 2019 [cited by applicant]
US 20190349060A1 · Liao et al. · 2019 [cited by applicant]
US 20190349983A1 · Loehr et al. · 2019 [cited by applicant]
US 20190357085A1 · Chervyakov et al. · 2019 [cited by applicant]
US 20190357092A1 · Jung et al. · 2019 [cited by applicant]
US 20200127799A1 · Orsino et al. · 2020 [cited by applicant]
US 20200136878A1 · Yi et al. · 2020 [cited by applicant]
US 20200221499A1 · Hofstrom et al. · 2020 [cited by applicant]
US 20200288413A1 · Ahn et al. · 2020 [cited by applicant]
US 20200389922A1 · Xu et al. · 2020 [cited by applicant]
US 20210058999A1 · Chen et al. · 2021 [cited by applicant]
US 20220264475A1 · Yi et al. · 2022 [cited by applicant]
CN 109788573A · 2019 [cited by applicant]
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]
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]
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]
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]
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: Remaing 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: Remaing 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]
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.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.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 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 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 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]
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]
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]
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-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-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]
Jul. 12, 2021—European Search Report—EP 21171212.0. [cited by applicant]
MediaTek Inc. “Remaining details on RACH procedure”, 3GPP TSP RAN WG1 Meeting #92, Athens, Greece, Feb. 26-Mar. 2, 2018. [cited by applicant]