IP Library Granted Patent US 12,463,786
Granted Patent B2
US 12,463,786 · App. 17/800,984 · Granted Nov 4, 2025

Bandwidth part (BWP) partition and sub-BWP hopping

Inventors: Jing Dai (Beijing, CN); Chao Wei (Beijing, CN); Min Huang (Beijing, CN)
Assignee: QUALCOMM Incorporated
H04L5/0092H04L5/0012H04L5/0051
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,463,786
App. No.
17/800,984
Granted
Nov 4, 2025
Kind
B2
Abstract

Aspects of the disclosure relate to defining a bandwidth part (BWP) within an operating bandwidth, and sub-BWPs within the BWP, where the sub-BWPs can be used for scheduling frequency-hopping transmissions. As one example, a base station may schedule frequency-hopping transmissions using two or more sub-BWPs. The base station may configure a portion of an operating bandwidth to serve as a BWP used for communicating with a UE over the wireless communication network, define two or more sub-BWPs at different frequency locations within the BWP, each sub-BWP including resource blocks provided in the BWP, and provide a scheduling gap when a frequency hop is scheduled between two or more sub-BWPs at the UE, wherein the scheduling gap accommodates radio frequency retuning at the UE.

Claims (72)

1 . A method for wireless communication at a scheduling entity in a wireless communication network, the method comprising:

configuring a portion of an operating bandwidth to serve as a bandwidth part (BWP) used for communicating with a user equipment (UE) over the wireless communication network;

defining two or more sub-BWPs at different frequency locations within the BWP, each sub-BWP including resource blocks provided in the BWP;

providing a scheduling gap when a frequency hop is scheduled between two or more sub-BWPs at the UE, wherein the scheduling gap accommodates radio frequency retuning at the UE;

transmitting a physical downlink control channel (PDCCH) in a first sub-BWP; and

transmitting a physical downlink shared channel (PDSCH) scheduled by the PDCCH with a preceding hop in a second sub-BWP the PDSCH commencing after the scheduling gap,

wherein the scheduling gap is provided after the PDCCH and comprises a slot offset that includes an integer number of slots,

wherein the PDSCH conforms to physical downlink shared channel mapping type A defined by the Third Generation Partnership Project (3GPP), and

wherein the PDCCH and PDSCH are prohibited from being transmitted in a same slot.

2 . The method of claim 1 , wherein the scheduling gap includes an integer number of symbols.

3 . The method of claim 2 , further comprising:

determining a first number of symbols (N) associated with a processing time for the PDCCH; and

determining a second number of symbols (N retuning ) associated with a time for the radio frequency retuning at the UE, wherein the scheduling gap covers at least N+N retuning symbols.

4 . The method of claim 1 , wherein the integer number of slots (K th,A ) for PDSCH that complies with physical downlink shared channel mapping type A defined by the Third Generation Partnership Project (3GPP) is different from the integer number of slots (K th,B ) for PDSCH that complies with physical downlink shared channel mapping type B defined by the 3GPP.

5 . The method of claim 1 , wherein one or more symbols preceding a symbol that carries a demodulation reference signal (DMRS) are punctured.

6 . The method of claim 1 , wherein defining the two or more sub-BWPs comprises:

determining a first number (N RB BWP ) quantifying resource blocks in the BWP;

determining a second number (N RB sub ) quantifying resource blocks in each sub-BWP; and

determining a third number (M) quantifying remaining resource blocks, where M=N RB BWP mod N RB sub ,

wherein M resource blocks located at one or both edges of the BWP are unused.

7 . The method of claim 6 , wherein defining the two or more sub-BWPs further comprises:

determining a size of at least one sub-BWP located at an edge of the BWP that includes fewer than N RB sub resource blocks when M equals or exceeds a first threshold number,

wherein the M resource blocks located at the one or both edges of the BWP are unused when M is less than the first threshold number.

8 . The method of claim 7 , further comprising:

defining two equally-sized edge sub-BWPs, each edge sub-BWP including (M+N RB sub )/2 resource blocks when the number of remaining resource blocks is less than the first threshold number.

9 . A scheduling entity in a wireless communication network, comprising:

a wireless transceiver;

a memory; and

one or more processors communicatively coupled to the wireless transceiver and the memory, wherein the one or more processors are individually or collectively configured to cause the scheduling entity to:

configure a portion of an operating bandwidth to serve as a bandwidth part (BWP) used for communicating with a user equipment (UE) over the wireless communication network;

define two or more sub-BWPs at different frequency locations within the BWP, each sub-BWP including resource blocks provided in the BWP; and

provide a scheduling gap when a frequency hop is scheduled between two or more sub-BWPs at the UE, wherein the scheduling gap accommodates radio frequency retuning at the UE;

transmit a physical downlink control channel (PDCCH) in a first sub-BWP; and

transmit a physical downlink shared channel (PDSCH) scheduled by the PDCCH with a preceding hop in a second sub-BWP the PDSCH commencing after the scheduling gap,

wherein the scheduling gap is provided after the PDCCH and comprises a slot offset that includes an integer number of slots,

wherein the PDSCH conforms to physical downlink shared channel mapping type A defined by the Third Generation Partnership Project (3GPP), and

wherein the PDCCH and PDSCH are prohibited from being transmitted in a same slot.

10 . The scheduling entity of claim 9 , wherein the scheduling gap includes an integer number of symbols.

11 . The scheduling entity of claim 10 , wherein the one or more processors are individually or collectively configured to cause the scheduling entity to:

determine a first number of symbols (N) associated with a processing time for the PDCCH; and

determine a second number of symbols (N retuning ) associated with a time for the radio frequency retuning at the UE, wherein the scheduling gap covers at least N+N retuning symbols.

12 . The scheduling entity of claim 9 , wherein the integer number of slots (K th,A ) for PDSCH that complies with physical downlink shared channel mapping type A defined by the Third Generation Partnership Project (3GPP) is different from the integer number of slots (K th,B ) for PDSCH that complies with physical downlink shared channel mapping type B defined by the 3GPP.

13 . The scheduling entity of claim 9 , wherein one or more symbols preceding a symbol that carries a demodulation reference signal (DMRS) are punctured.

14 . A scheduling entity in a wireless communication network, comprising:

a wireless transceiver;

a memory; and

one or more processors communicatively coupled to the wireless transceiver and the memory, wherein the one or more processors are individually or collectively configured cause the scheduling entity to:

configure a portion of an operating bandwidth to serve as a bandwidth part (BWP) used for communicating with a user equipment (UE) over the wireless communication network;

define two or more sub-BWPs at different frequency locations within the BWP, each sub-BWP including resource blocks provided in the BWP;

provide a scheduling gap when a frequency hop is scheduled between two or more sub-BWPs at the UE, wherein the scheduling gap accommodates radio frequency retuning at the UE;

determine a first number (N RB BWP ) quantifying resource blocks in the BWP;

determine a second number (N RB sub ) quantifying resource blocks in each sub-BWP; and

determine a third number (M) quantifying remaining resource blocks, where M=N RB BWP mod N RB sub ,

wherein M resource blocks located at one or both edges of the BWP are unused.

15 . The scheduling entity of claim 9 , wherein the one or more processors are individually or collectively configured to cause the scheduling entity to:

determine a size of at least one sub-BWP located at an edge of the BWP that includes fewer than N RB sub resource blocks when M equals or exceeds a first threshold number,

wherein the M resource blocks located at the one or both edges of the BWP are unused when M is less than the first threshold number.

16 . The scheduling entity of claim 15 , wherein the one or more processors are individually or collectively configured to cause the scheduling entity to:

define two equally-sized edge sub-BWPs, each edge sub-BWP including (M+N RB sub )/2 resource blocks when the number of remaining resource blocks is less than the first threshold number.

17 . A scheduled entity, comprising:

a wireless transceiver;

a memory; and

one or more processors communicatively coupled to the wireless transceiver and the memory, wherein the one or more processors are individually or collectively configured to cause the scheduled entity to:

configure the wireless transceiver to communicate using a bandwidth part (BWP) comprising a portion of an operating bandwidth provided by a wireless communication network;

receive a physical downlink control channel (PDCCH) in a first sub-BWP that is located at a first frequency within the BWP and that includes first resource blocks provided in the BWP;

retune one or more radio frequency components of the wireless transceiver from the first frequency to a second frequency within the BWP; and

receive a physical downlink shared channel (PDSCH) scheduled by the PDCCH in a second sub-BWP that is located at the second frequency and that includes second resource blocks provided in the BWP,

wherein the one or more components of the wireless transceiver are retuned during a scheduling gap provided between the PDCCH and the PDSCH,

wherein the PDSCH conforms to physical downlink shared channel mapping type A defined by the Third Generation Partnership Project (3GPP), and

wherein the PDCCH and PDSCH are prohibited from being transmitted in a same slot.

18 . The scheduled entity of claim 17 , wherein the scheduling gap covers an integer number (N+N retuning ) of symbols that comprises at least a first number of symbols (N) associated with a processing time for the PDCCH, and a second number of symbols (N retuning ) associated with a time for the retuning.

19 . The scheduled entity of claim 17 , wherein the scheduling gap comprises a slot offset that includes an integer number of slots, and wherein the integer number of slots (K th,A ) for PDSCH that complies with physical downlink shared channel mapping type A defined by the Third Generation Partnership Project (3GPP) is different from the integer number of slots (K th,B ) for PDSCH that complies with physical downlink shared channel mapping type B defined by the 3GPP.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 7, 2022
From: DAI, JING; WEI, CHAO; HUANG, MIN
To: QUALCOMM INCORPORATED
Reel/Frame 061676/0043 →
Continuity (1)
Related Publication 20230072549A1 · Mar 9, 2023
References Cited (7)
US 20190132109A1 · Zhou · 2019 [cited by examiner]
US 20190141546A1 · Zhou et al. · 2019 [cited by applicant]
US 20190223086A1 · Jung et al. · 2019 [cited by applicant]
WO WO2020087470A1 · 2020 [cited by examiner]
Machine Translation of WO-2020087470-A1 (Year: 2020). [cited by examiner]
Intel Corporation: “Layer 1 Enhancements for eURLLC”, 3GPP Draft; R1-1810785, 3GPP TSG RAN WG1 Meeting #94b, Intel-Eurllc L1 Enhancements Final, 3rd Generation Partnership Project (3GPP), Mobile Competence Centre ; 650,… [cited by applicant]
International Search Report and Written Opinion—PCT/CN2020/077179—ISA/EPO—Nov. 26, 2020. [cited by applicant]