5G NR ARFCN

Contents

1. Overview
2. Global frequency raster and channel raster
3. Where ARFCN appears
4. ARFCN vs GSCN
5. All NR bands and ARFCN ranges
6. Troubleshooting
7. References
8. FAQ

Overview

In practical language, ARFCN is the channel number version of a radio frequency. Instead of saying “this carrier is at 3510 MHz,” the system can refer to the matching NR ARFCN. That makes frequency handling more consistent across configuration files, logs, signaling, and tools.

• the UE uses ARFCN-related configuration to understand where the serving and neighbor carriers are
• the gNB uses ARFCN when configuring carrier-related radio parameters
• ARFCN is used when validating bands, planning cells, and reading traces
• ARFCN belongs naturally with PHY and radio-planning topics, not as a stand-alone blog concept

Global frequency raster and channel raster

NR defines a global channel raster. Each valid point on that raster can be represented by an NR ARFCN value. The exact mapping depends on the frequency range and the associated offset and step rules.

Why the mapping matters

A human may think in MHz or GHz, but systems need a normalized representation. ARFCN gives that representation and allows frequencies to be exchanged, stored, and compared consistently.

FR1 and FR2 behavior

Global raster formula

NR-ARFCN = (Fref - Foffset) / DeltaFglobal + Noffset

The important point is not memorizing every constant, but understanding that ARFCN is a spec-defined mapping from frequency to channel number, not an arbitrary vendor label.

Global raster parameters

Channel raster inside each operating band

The global frequency raster is broader than the set of usable values in one NR band. Each band uses a channel raster, which is a subset of the global raster with a band-specific step size. Depending on the band, every valid value may be usable, or only every second, third, sixth, or twentieth global-raster point may be applicable.

This is why not every ARFCN inside a numerical range is valid for every band. Band validation needs the band table, the raster step, and the uplink or downlink context.

7.5 kHz uplink shift case

For SUL bands and for uplink in FDD bands, the uplink RF reference frequency can include a network-signalled 7.5 kHz shift. That matters when the ARFCN looks correct at band level but the exact uplink frequency still appears offset from the value you expected.

Channel position and resource-element mapping

ARFCN is not only a band-planning label. The channel raster maps to a specific resource-element position on the carrier, so ARFCN sits directly in the PHY frequency-position model used by the carrier.

Common example

In a common n78 deployment around 3500 MHz, the matching ARFCN is often around the 620000 region. When that value appears in logs or configuration, it can be tied back to the serving carrier and band context immediately.

Where NR ARFCN fits inside the 5G PHY cluster

• Numerology explains the timing and subcarrier behavior that rides on top of the chosen carrier.
• Frame structure explains how time is organized once the carrier is known.
• SSB and PBCH explain how the UE first finds and reads the cell.
• Physical-layer measurements and RRC measurement pages use frequency and neighbor context tied to ARFCN.
• The NR ARFCN calculator converts theory into a practical validation workflow.

ARFCN is therefore not a detached theory page. It is part of the radio-frequency foundation that sits underneath access, measurements, mobility, and carrier planning.

Where ARFCN appears in real workflows

Cell configuration and planning

ARFCN is used when configuring a carrier, validating band use, and confirming that the deployed cell is aligned with the intended frequency plan.

System information and serving-cell interpretation

During early access, the UE first finds the cell through synchronization, then learns broader radio context through broadcast and configuration information. ARFCN-related parameters become part of how serving frequency that the UE is camped on or connected to the intended carrier.

Measurements and mobility

Neighbor-frequency planning and mobility analysis frequently depend on ARFCN. If handover behavior looks wrong, one of the first checks is whether the expected neighbor ARFCNs and bands align with what the network is actually advertising or measuring.

Mini sequence view

Carrier plan -> ARFCN configured -> UE finds SSB -> UE reads broadcast/config context -> measurements and mobility use ARFCN-based carrier references

NR ARFCN vs GSCN

ARFCN and GSCN are related, but they solve different problems.

A common mistake is to treat GSCN as if it were the same as the serving carrier ARFCN. It is not. GSCN is about where the UE looks for synchronization, while ARFCN is about how the carrier itself is represented.

All 5G NR operating bands and ARFCN ranges

The table below summarizes the current NR band dataset used by the NR ARFCN calculator. It is based on the NR operating-band definitions in 3GPP TS 38.104, so the page and the calculator are aligned to the same reference model.

Use this table when you need a quick band-level reference, and use the calculator when you want to validate a specific frequency or ARFCN from logs, planning sheets, or configuration files.

Troubleshooting

Example 1: Cell audit

A log shows a serving NR ARFCN of 620000. The first questions are: which band does that align with, what center frequency does it represent, and does it match the planned deployment?

Example 2: Mobility validation

A UE is not handing over to an expected neighbor. Check whether the neighbor list, measurements, and mobility configuration reference the intended ARFCN values and whether those values match the band plan.

Example 3: Tool-assisted troubleshooting

A trace provides only ARFCN and band-related hints. Convert the ARFCN to frequency with the NR ARFCN calculator and then validates whether the observed cell behavior matches the intended deployment.

• does the serving ARFCN map to the expected center frequency and band?
• do neighbor ARFCNs align with the intended measurement and mobility design?
• is the observed carrier in FR1 or FR2, and are you using the correct mapping assumptions?
• is the band using a channel-raster step that makes only some ARFCNs valid inside the band?
• for FDD uplink or SUL cases, could a 7.5 kHz shift be part of the interpretation?
• are you confusing GSCN-based synchronization details with ARFCN-based carrier details?
• does the ARFCN line up with the bandwidth, numerology, and deployment scenario you expect?

• do not treat ARFCN as a band identifier instead of a carrier-channel identifier
• do not forget that FR1 and FR2 use different raster behavior
• do not mix up GSCN and ARFCN during early-access analysis
• do not assume one observed ARFCN value is enough without checking actual band and frequency context
• do not read planning spreadsheets in MHz while trace tools report ARFCN without translating between them correctly

References

• 3GPP TS 38.104 - NR base station radio transmission and reception, including global frequency raster, channel raster, band entries, and synchronization raster
• 3GPP TS 38.331 - NR radio resource control, including frequency-related configuration and measurement context

FAQ

What is NR ARFCN in 5G?

It is the standardized channel number used to represent a 5G NR carrier frequency.

Why use ARFCN instead of only MHz?

Because ARFCN provides a normalized, spec-defined numbering system that is easier to use across planning, signaling, and tools.

Is ARFCN a PHY topic?

Yes. It belongs naturally with radio-frequency planning, raster interpretation, and early access or measurement context inside the PHY layer cluster.

What is the difference between ARFCN and GSCN?

ARFCN identifies the carrier-channel position. GSCN identifies synchronization raster positions used for SSB search.

Where should I validate an ARFCN quickly?

Use the NR ARFCN calculator to map channel number to frequency and band context.

Is every ARFCN inside a band range valid?

No. Each operating band uses a channel raster, so only values that match the applicable band step size are valid.