5G Bandwidth Part (BWP)

Contents

1. Overview
2. How the BWP model works
3. BWP switching
4. How BWP connects to numerology, OFDM, and control
5. Where BWP appears in real procedures
6. Troubleshooting
7. References
8. FAQ

Overview

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
• do not confuse total carrier bandwidth with active scheduling bandwidth

Quick interpretation

How the BWP model works

The key 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 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. Do 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.

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.
• CORESET and Search Space define where control monitoring happens inside the BWP.
• 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 later seen in traces.

A common 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, the initial BWP appears 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, changes may appear in control monitoring, throughput, apparent usable bandwidth, or UE power behavior without the carrier itself changing.

Troubleshooting

• 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

• 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

References

• 3GPP TS 38.211 - NR physical channels and modulation
• 3GPP TS 38.213 - NR physical-layer procedures for control
• 3GPP TS 38.214 - NR physical-layer procedures for data
• 3GPP TS 38.331 - NR radio resource control

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, while configuration and switching are largely seen through RRC.

Why is BWP often misread?

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.