Why does 5G use bandwidth parts?

NR uses bandwidth parts to make the radio more flexible and efficient. They help balance wide carrier capability with practical UE monitoring, transmission behavior, and power-saving considerations.

How does BWP affect throughput?

BWP affects the resource region actually available for scheduling and monitoring. Engineers must read throughput expectations against the active BWP, not only the total carrier bandwidth.

Home / 5G / Protocols / PHY / Bandwidth Part

5G Bandwidth Part (BWP)

Q: What is a bandwidth part in 5G?

A bandwidth part in 5G NR is a configured subset of the carrier bandwidth that the UE actively uses for monitoring or transmission. It allows NR to avoid treating the full carrier as always active all the time.

Q: What is the difference between initial BWP and active BWP?

The initial BWP is the bandwidth part the UE commonly starts with for access and common operation, while the active BWP is the one currently in use for ongoing control or data behavior after configuration and possible switching.

A 5G NR bandwidth part is a configured active bandwidth region inside the wider carrier. It lets the network expose a manageable portion of the carrier to the UE for control monitoring and data transfer, instead of treating the whole carrier as always active in the same way at all times.

For beginners, BWP explains why a wide NR carrier does not always mean the UE is actively using the full width. For experienced engineers, it explains real differences between configured carrier bandwidth, monitored control region, active scheduling bandwidth, and what the UE is actually using at a given time.

Primary concept	A configurable active bandwidth region inside the wider NR carrier
Main specs	3GPP TS 38.211, 38.213, 38.214, 38.331
Core terms	initial BWP, active BWP, downlink BWP, uplink BWP, BWP switching
Why it matters	Power saving, scheduler behavior, control monitoring, throughput, and radio configuration interpretation

What BWP means in simple terms

In practical language, the BWP is the currently relevant slice of the carrier that the UE is paying attention to. The cell may have a wide carrier, but the UE does not always need to operate across the full width for every step of access, monitoring, or data activity.

the carrier can be wider than the currently active BWP
the UE may start on one BWP and later switch to another
BWP behavior is tightly linked to numerology, control resources, and RRC configuration
engineers should not confuse total carrier bandwidth with active scheduling bandwidth

Technical summary

Definition	A configured subset of carrier bandwidth used for active downlink or uplink operation
Configured by	RRC signaling and radio configuration
Key practical forms	Initial BWP, active BWP, downlink BWP, uplink BWP
Main impact	Control monitoring, scheduling region, throughput interpretation, and UE power behavior
Linked topics	Numerology, OFDM resource grid, PDCCH, PDSCH, PUSCH, RRC configuration

How BWP works in practice

The key engineering idea is that NR separates the full carrier capability from the currently active operating bandwidth. This gives the network more flexibility in how the UE monitors control, receives scheduling, and transmits or receives data.

Initial BWP

The initial BWP is the starting operating region used during early access and initial common behavior. It is often the first practical bandwidth context an engineer sees before more specific scheduling and data behavior begins.

Active BWP

The active BWP is the bandwidth part currently in use. This is the one that matters most when you inspect real scheduling, throughput, control monitoring, and data transfer behavior.

Downlink and uplink BWPs

BWPs can differ between downlink and uplink. Engineers should not assume that the monitored downlink region and the actively used uplink region are always identical in behavior or purpose.

BWP switching

NR can move the UE from one BWP to another depending on configuration and traffic behavior. This is why throughput or monitoring behavior can appear to change even when the cell bandwidth itself does not.

Concept	What engineers should remember
Carrier bandwidth	The total configured radio bandwidth of the carrier
Initial BWP	The UE starting bandwidth context for access and common operation
Active BWP	The bandwidth part currently being used for real scheduling and monitoring behavior
BWP switching	The mechanism that moves operation from one configured BWP to another

How BWP connects to numerology, OFDM, and scheduling

Numerology defines the timing and subcarrier grid inside which the BWP exists.
OFDM is the waveform and resource-grid model on which the BWP is actually realized.
PDCCH, PDSCH, and PUSCH behavior must be read against the active BWP rather than only against total carrier width.
RRC configures the BWPs, control resources, and switching behavior engineers later inspect in traces.

A common engineering mistake is to assume that the full carrier width is always the relevant scheduling region. In many practical cases, the active BWP is the more important number.

Where BWP appears in real procedures

Initial access and setup

Common configuration -> initial BWP context -> control monitoring -> scheduling -> later reconfiguration

During early access, engineers often encounter the initial BWP before more optimized ongoing radio behavior is established.

Connected-mode scheduling

Active BWP -> PDCCH monitoring -> PDSCH/PUSCH scheduling -> throughput behavior

This is the most important BWP context in daily work. The active BWP defines the bandwidth region that is actually shaping practical user throughput and control behavior.

Reconfiguration and performance changes

If the network reconfigures BWP behavior, engineers may see changes in control monitoring, throughput, apparent usable bandwidth, or power-related UE behavior without the carrier itself changing.

Real-world engineering examples

Example 1: Why a wide carrier does not guarantee wide scheduling

A cell can advertise a wide NR carrier, but the UE may still be operating on a smaller active BWP for its practical control and data activity. If you only look at the carrier width, you can overestimate throughput.

Example 2: Why throughput changed after reconfiguration

Engineers sometimes attribute throughput changes to RF or scheduler quality alone, when the more immediate explanation is that the active BWP or the control-monitoring context changed.

Example 3: Why control behavior can look constrained

Search-space and CORESET behavior should be interpreted together with the active BWP. Looking at control issues without that context can hide the actual reason for the observed limitation.

What to check in logs, counters, and traces

configured carrier bandwidth versus active BWP
initial BWP and later active BWP behavior
downlink and uplink BWP configuration differences
PDCCH monitoring context, CORESET, and search-space configuration inside the active BWP
PDSCH and PUSCH scheduling region versus expected throughput assumptions
RRC reconfiguration events that may have changed BWP behavior

Common mistakes engineers make

equating total carrier width with active scheduling width
ignoring the initial BWP when analyzing early access behavior
blaming throughput only on RF quality without checking active BWP context
reading control-channel issues without considering the BWP-specific control region

Troubleshooting clues

Symptom	Possible BWP-side pattern	Next check
Lower-than-expected throughput	Active BWP is narrower than the engineer assumed, or control/data usage is constrained inside that region	Check active BWP size and use the NR Throughput Calculator
Control monitoring issue	CORESET or search-space behavior is being interpreted without the active BWP context	Check BWP-specific control configuration and related RRC settings
Behavior changes after setup or reconfiguration	BWP switching or updated active BWP context may have changed the usable scheduling region	Check reconfiguration timing and compare before/after active BWP state

FAQ

What is a bandwidth part in 5G?

It is a configured subset of the NR carrier bandwidth that the UE actively uses for control monitoring or data transmission behavior.

Why does 5G use BWPs?

BWPs give NR more flexibility and help balance full carrier capability with practical UE operation and power behavior.

What is the difference between initial BWP and active BWP?

The initial BWP is the starting bandwidth context, while the active BWP is the one currently being used for real ongoing operation.

Does BWP affect throughput?

Yes. Throughput must be interpreted against the active BWP and the usable scheduling region, not only the full carrier bandwidth.

Is BWP a PHY concept or an RRC concept?

It is both in practice: the operating bandwidth behavior is a PHY reality, but engineers usually inspect and control it through RRC configuration.

Why do engineers misread BWP behavior?

Because it is easy to focus on carrier bandwidth, while the active BWP is often the more relevant value for actual control and data behavior.

Beginner takeaway

A BWP is the active part of the carrier that the UE is currently using. If you understand the difference between total carrier width and active BWP, many NR scheduling and throughput questions become easier.

Advanced engineer notes

BWP should always be interpreted together with numerology, control configuration, and scheduler policy.
Many practical throughput misunderstandings are really BWP misunderstandings.
Initial BWP, active BWP, and later reconfiguration should be separated clearly in trace analysis.
Control-channel interpretation without the correct BWP context often leads to the wrong troubleshooting path.

Use the tools naturally in this workflow

Pair this page with the NR Throughput Calculator to sanity-check active-bandwidth assumptions, and with the 3GPP Decoder when you want to connect RRC configuration and trace behavior back to the active BWP.