Spectrum: FR1, FR2, Bands & Duplexing in 5G NR
Frequency ranges FR1 and FR2, NR operating bands, and TDD vs FDD in 5G.
5G NR runs across an enormous stretch of radio โ from a few hundred MHz all the way up to 71 GHz. To keep this manageable, 3GPP splits it into two frequency ranges, FR1 (sub-7 GHz) and FR2 (mmWave), and carves each into named operating bands. Which range you sit in decides your subcarrier spacing, your channel bandwidth, how you duplex, and even where the cell parks its sync beacon. This page walks the whole spectrum picture, from ranges and bands down to the raster arithmetic that pins a carrier to an exact frequency.
Introduction
Spectrum is the raw material of a radio network โ the specific slices of the electromagnetic spectrum an operator is licensed to transmit in. Everything else in NR is built on top of the answer to "which frequencies do I have?" 3GPP organises that raw material top-down: two broad frequency ranges (FR1 and FR2), each subdivided into licensed operating bands (the n-numbers), and within each band the discrete raster positions where a carrier and its sync signal are actually allowed to sit.
This matters at every stage of the UE lifecycle. At power-on the UE must know which bands to scan and which raster positions can hold an SSB, or blind cell search would take forever. When a carrier is configured, the band fixes the allowed subcarrier spacings and channel bandwidths, which in turn fix how many resource blocks the UE gets. And when the network plans capacity and coverage, the choice of band โ low vs mid vs mmWave โ and duplex mode determines reach, throughput, and how hard it must lean on beamforming.
The defining spec for all of this is TS 38.101 (UE RF: TS 38.101-1 for FR1, TS 38.101-2 for FR2) with base-station RF in TS 38.104. Read spectrum as a hierarchy โ range โ band โ channel โ raster โ and every parameter on this page has a clear home in that tree.
On this page
Why NR splits spectrum this way
In plain words: think of spectrum like real estate. The two frequency ranges are two very different neighbourhoods โ FR1 is sprawling countryside (cheap land, long views, but you can only build small), FR2 is downtown (tiny plots, but you can build skyscrapers of bandwidth). Bands are the individual plots you hold the deed to. And the raster is the zoning grid that says a building's centre line may only sit on certain surveyed markers โ so everyone knows exactly where to look for their neighbour.
Concretely, three problems force this structure. First, physics changes with frequency: low bands propagate far but carry little bandwidth, high bands carry huge bandwidth but barely reach and are easily blocked โ so NR needs different numerologies and duplexing rules for each, which is exactly what the FR1/FR2 split encodes. Second, spectrum is licensed in fixed blocks by regulators, so 3GPP must name those blocks (the operating bands) and pin each one's uplink/downlink ranges and duplex mode. Third, a UE cannot tune to arbitrary frequencies and cannot afford to search the whole range for a cell โ so NR defines a fine frequency raster to place carriers and a much sparser synchronization raster to place sync beacons, making blind cell search tractable.
A layered organisation of NR spectrum: ranges (FR1/FR2) โ operating bands (n-numbers) โ carriers of a supported bandwidth โ discrete raster positions (ARFCN, GSCN).
Different physics per range, regulator-defined licensed blocks, and the need for fast, deterministic cell search all demand a named, discretised structure rather than a free-for-all.
TS 38.101/38.104 fix each band's ranges and duplex, the allowed SCS and channel bandwidths per band, the transmission-bandwidth (N_RB) tables, and the two rasters the UE uses to place and find a carrier.
FR1 and FR2 โ the two worlds of NR
All of NR's spectrum (TS 38.101) is divided into two frequency ranges. They behave very differently, so it is worth carrying a clear mental picture of each before anything else.
FR1 spans 410 MHz to 7.125 GHz. This is the workhorse: good propagation, wide coverage, and the home of the famous mid-band carriers like n78. It is loosely called "sub-6", but the true ceiling was raised to 7.125 GHz to admit the 6 GHz unlicensed spectrum.
FR2 spans 24.25 to 71 GHz. It is split into FR2-1 (24.25โ52.6 GHz) and FR2-2 (52.6โ71 GHz). Huge bandwidth, huge capacity โ but short range and easily blocked, so it leans hard on beamforming and dense deployment.
Low frequency = long reach, little bandwidth. High frequency = little reach, enormous bandwidth. FR1 gives you coverage plus a solid capacity layer; FR2 gives you multi-gigabit hotspots wherever you can afford the sites.
The dividing philosophy matters. Everything in FR1 is designed around covering area with a modest slice of spectrum, so subcarrier spacings stay small and channels top out at 100 MHz. Everything in FR2 assumes you have bandwidth to burn but a hostile channel โ high phase noise, severe blockage, large Doppler โ so it uses wide subcarriers, wide channels, and swept narrow beams. Notice the empty stretch between them: nothing operates in the 7.125โ24.25 GHz gap in NR today, which is why the two ranges feel like separate universes.
Remember the numbers: FR1 = 410 MHz–7.125 GHz; FR2 = 24.25–71 GHz (FR2-1 up to 52.6 GHz, FR2-2 up to 71 GHz).
Operating bands: the n-numbers
Within each frequency range, spectrum is licensed in chunks called operating bands. NR bands are named n<number> โ for example n1, n3, n78. Each band definition (TS 38.101-1 for FR1, TS 38.101-2 for FR2) fixes an uplink range, a downlink range, and a duplex mode. Many NR band numbers deliberately echo their LTE cousins (LTE band 3 → NR n3) because they occupy the same spectrum and simplify re-farming.
| Band | Uplink / Downlink | Duplex | Range | Note |
|---|---|---|---|---|
n1 | 1920–1980 / 2110–2170 MHz | FDD | FR1 | Classic paired 2.1 GHz band. |
n3 | 1710–1785 / 1805–1880 MHz | FDD | FR1 | 1.8 GHz, widely re-farmed from LTE. |
n41 | 2496–2690 MHz | TDD | FR1 | 2.5 GHz capacity band. |
n78 | 3300–3800 MHz | TDD | FR1 | The flagship mid-band 5G carrier. |
n79 | 4400–5000 MHz | TDD | FR1 | 4.7 GHz upper mid-band (Asia). |
n257 | 26.5–29.5 GHz | TDD | FR2-1 | mmWave, "28 GHz". |
n258 | 24.25–27.5 GHz | TDD | FR2-1 | mmWave, "26 GHz". |
n260 | 37–40 GHz | TDD | FR2-1 | mmWave, "39 GHz". |
n261 | 27.5–28.35 GHz | TDD | FR2-1 | mmWave, US "28 GHz" subset. |
A few reading habits pay off. Bands numbered up to the low hundreds are FR1; the n257/n258/n259/n260/n261 family is FR2 mmWave. A paired band lists two frequency ranges (uplink and downlink); a TDD band lists one range shared by both directions. And a band's number tells you nothing about how wide it is โ n78 is 500 MHz of TDD spectrum, while an FDD band like n1 is only 60 MHz per direction.
Bands vs channels: a band is the licensed envelope; inside it an operator places one or more carriers (channels) of a supported bandwidth. n78 is 500 MHz wide but a single carrier there is at most 100 MHz โ you deploy several, or aggregate them.
LTE โ NR: NR reuses the operating-band idea from LTE but changes the naming and reach. LTE bands are bare numbers (band 3, band 41); NR prefixes an n (n3, n41), and many NR bands sit on the same spectrum as their LTE namesake to ease re-farming and EN-DC pairing. The big additions in NR are the mmWave bands (n257+) that LTE never had, and the extension of "sub-6" up to 7.125 GHz. LTE addresses carriers with the EARFCN; NR uses the NR-ARFCN (NREF) on a frequency-dependent raster.
Duplexing: FDD, TDD, SDL and SUL
Duplexing is how uplink and downlink share the spectrum. NR supports the two classic schemes plus two "supplementary" one-directional modes that exist to patch specific coverage or capacity gaps.
| Mode | What it means | Where used |
|---|---|---|
| FDD | Frequency-Division Duplex โ uplink and downlink use separate paired frequencies simultaneously. | Low bands where paired spectrum exists (n1, n3, n28). |
| TDD | Time-Division Duplex โ uplink and downlink share one frequency, alternating in time by a configured slot pattern. | Dominant in mid-band and all of FR2 (n41, n78, n257). |
| SDL | Supplementary Downlink โ an unpaired, downlink-only carrier that adds DL capacity, aggregated with a normal band. | Extra DL spectrum (e.g. L-band n75). |
| SUL | Supplementary Uplink โ an extra, usually lower-frequency uplink to extend UL reach. | Cell-edge UEs uplink on a low band while downlinking on a high band (e.g. n80 paired with n78). |
The two supplementary modes are easy to misread, so anchor them to a picture. A normal TDD mid-band cell like n78 has plenty of downlink reach โ the base station is powerful โ but the handset's uplink is weak and runs out of range first. SUL hands that struggling UE a second uplink carrier down at, say, 700 MHz or 1.5 GHz, where its transmit power carries much farther. The UE keeps downlinking on n78 but uplinks on the SUL, so the coverage-limited direction gets a low-band boost. The two uplinks are mutually exclusive at any instant โ the UE transmits on the normal UL or the SUL, selected against a broadcast RSRP threshold (rsrp-ThresholdSSB-SUL). SDL is the mirror-image capacity play: a leftover unpaired block that can only ever carry downlink, bolted on to soak up the DL-heavy traffic of modern networks.
Why TDD dominates NR: mid/high-band paired spectrum is scarce, and 5G traffic is heavily downlink-skewed. TDD lets the operator tilt the UL/DL slot ratio toward downlink and reuse one block for both directions โ perfect for beamformed mid-band and mmWave, where channel reciprocity also helps beamforming. The slot pattern itself is broadcast in tdd-UL-DL-ConfigurationCommon (with an optional UE-specific tdd-UL-DL-ConfigurationDedicated overlay).
LTE โ NR: LTE TDD used seven fixed uplink-downlink configurations (a small menu of DL/UL subframe patterns). NR replaces that rigid menu with a flexible slot format built from D (downlink), U (uplink) and F (flexible) symbols, configured via tdd-UL-DL-ConfigurationCommon and dynamically overridable by the Slot Format Indicator (DCI 2_0). SUL and the flexible-symbol concept are NR additions with no direct LTE equivalent.
Subcarrier spacing, channel bandwidth and PRB count
NR is flexible about numerology: the subcarrier spacing (SCS) and the channel bandwidth both depend on which frequency range โ and often which band โ you are in (TS 38.104). The SCS is always 2μ × 15 kHz for numerology μ = 0โฆ4, giving 15, 30, 60, 120 and 240 kHz. Higher SCS means each subcarrier is wider, symbols are shorter, and you can support wider channels and shorter latency, which is exactly what the higher ranges demand.
| Range | Allowed data SCS | SSB SCS | Max channel BW |
|---|---|---|---|
FR1 | 15, 30, 60 kHz | 15 or 30 kHz | up to 100 MHz per carrier |
FR2-1 | 60, 120 kHz | 120 or 240 kHz | up to 400 MHz per carrier |
FR2-2 | 120, 480, 960 kHz | 120, 480, 960 kHz | up to 2 GHz per carrier |
Which SCS a specific band allows is fixed per band in TS 38.104 โ a low FDD band like n3 supports only 15 and 30 kHz, whereas n78 is a 30/60 kHz band, and FR2 bands center on 120 kHz. The point of numerology is that the same radio grid stretches to fit the channel: pick the SCS the band allows, and the number of resource blocks you get follows. Note the SSB SCS is signalled independently of the data SCS via subCarrierSpacingCommon in the MIB.
The number of resource blocks (equivalently PRBs) you actually receive is a function of bandwidth divided by SCS, because each RB is always 12 subcarriers. Wider SCS packs fewer RBs into the same MHz, but each RB is physically wider.
The exact maxima are tabulated as the transmission bandwidth configuration NRB in TS 38.101-1 (FR1) and TS 38.101-2 (FR2). Here is the core of that table โ the numbers worth memorising:
| Channel BW | 15 kHz | 30 kHz | 60 kHz | 120 kHz |
|---|---|---|---|---|
| 5 MHz | 25 | 11 | — | — |
| 10 MHz | 52 | 24 | 11 | — |
| 15 MHz | 79 | 38 | 18 | — |
| 20 MHz | 106 | 51 | 24 | — |
| 50 MHz | 270 | 133 | 65 | 32 |
| 100 MHz | — | 273 | 135 | 66 |
| 200 MHz | — | — | — | 132 |
| 400 MHz | — | — | — | 264 |
Read the dashes as "not allowed": a 100 MHz channel is unreachable at 15 kHz because it would need far more RBs than the transmission-bandwidth limit permits, and the 200/400 MHz columns only exist at 120 kHz in FR2. The headline value is 100 MHz at 30 kHz SCS = 273 PRB โ the canonical FR1 mid-band carrier. Move to 60 kHz and the same 100 MHz gives only 135 PRB: identical spectrum, wider subcarriers, fewer but larger blocks. Note the maximum 273 PRB is also the largest carrier NR defines at any SCS, so it caps the FFT size the UE must implement.
This is why 30 kHz is the FR1 mid-band workhorse: it packs enough PRBs into a 100 MHz channel for high throughput while keeping the symbol short enough to tolerate the delay spread and Doppler seen at 3.5 GHz. In FR2 the same logic scales up โ 120 kHz unlocks the 400 MHz channels, and the 480/960 kHz spacings introduced for FR2-2 are what make GHz-class carriers practical against mmWave phase noise.
Spec anchor: frequency ranges, bands, channel bandwidths and the NRB transmission-bandwidth tables live in TS 38.101-1 (FR1 UE) and TS 38.101-2 (FR2 UE); base-station RF is in TS 38.104. The numerology definition (μ, SCS = 2μ×15 kHz, 12 subcarriers per RB) is in TS 38.211.
LTE โ NR: LTE fixed the subcarrier spacing at 15 kHz and a resource block at 12 subcarriers × 0.5 ms slot, so its numerology never changed. NR keeps the 12-subcarrier RB but makes the SCS scalable (15/30/60/120/240 kHz) so one design covers 700 MHz to 71 GHz. It also drops LTE's largest carrier of 110 RB (20 MHz at 15 kHz) in favour of up to 273 RB per carrier and carrier aggregation for still-wider effective bandwidth.
Rasters: ARFCN and the SS raster (GSCN)
Spectrum is continuous, but a UE cannot tune to arbitrary real numbers โ it needs a discrete set of allowed frequencies. NR defines two rasters for this. The global frequency raster pins where a carrier's center can sit, addressed by an ARFCN (NREF); the sparser synchronization raster pins where an SSB can sit, addressed by a GSCN.
Global frequency raster and ARFCN
Every RF reference frequency FREF maps to an integer channel number NREF (the ARFCN) via a step size ΔFGlobal that grows with frequency (TS 38.104 §5.4.2):
| Frequency range | ΔFGlobal | FREF-Offs | NREF-Offs | NREF range |
|---|---|---|---|---|
| 0 – 3000 MHz | 5 kHz | 0 MHz | 0 | 0 – 599999 |
| 3000 – 24250 MHz | 15 kHz | 3000 MHz | 600000 | 600000 – 2016666 |
| 24250 – 100000 MHz | 60 kHz | 24250.08 MHz | 2016667 | 2016667 – 3279165 |
So the raster is fine (5 kHz) in the low bands where channels are narrow, and coarse (60 kHz) up in mmWave where they are enormous. A carrier is signalled to the UE by its ARFCN, and the SIB / RRC field that points at it (for example absoluteFrequencyPointA or absoluteFrequencySSB) carries an NREF value the UE converts back to Hz with the formula above. Note that the applicable ARFCN raster within any given band is further narrowed by a band-specific ΔFRaster in TS 38.104, so not every global-raster point is a legal carrier centre in every band.
The SS raster and GSCN
Searching every ARFCN for a beacon would be brutally slow, so SSBs are only allowed on a much sparser synchronization raster. Each allowed position is a Global Synchronization Channel Number (GSCN), and the UE only checks these "parking spots" during blind cell search (TS 38.104 §5.4.3).
| Frequency range | SS block frequency position SSREF | GSCN |
|---|---|---|
| 0 – 3000 MHz | N × 1200 kHz + M × 50 kHz, M ∈ {1,3,5} | 3N + (M − 3)/2 |
| 3000 – 24250 MHz | 3000 MHz + N × 1.44 MHz | 7499 + N |
| 24250 – 100000 MHz | 24250.08 MHz + N × 17.28 MHz | 22256 + N |
The step jumps from 1.2 MHz-ish in the low range to 1.44 MHz in the mid range to 17.28 MHz in mmWave โ again, coarser where channels are wider. Because the SS raster is so much sparser than the frequency raster, the cell's SSB almost never sits exactly at the carrier center; the offset between them is signalled to the UE (as offsetToPointA plus the sub-carrier-level k_SSB from the MIB), which is how the UE bridges from "I found a beacon on this GSCN" to "here is the full resource grid". To shrink the search further, each band lists only a handful of sync raster entries (a GSCN range) in TS 38.104, so the UE scans tens of positions, not thousands.
Guard bands and minimum guardband
A channel's nominal bandwidth is never fully filled with usable subcarriers. Some spectrum at each edge is deliberately left empty as a guard band so the carrier's out-of-band emissions decay before they reach the neighbour's spectrum. That is exactly why the NRB counts above are a little less than "bandwidth ÷ (12 × SCS)" would suggest โ the difference is guard band.
The relationship, in words, is: occupied bandwidth = NRB × 12 × SCS, and the leftover splits into two edge guards. For the flagship case, 273 PRB at 30 kHz occupy 273 × 12 × 30 kHz = 98.28 MHz inside a 100 MHz channel, leaving about 1.72 MHz total, or roughly 0.845 MHz per side. TS 38.101-1 tabulates this as the minimum guardband per channel bandwidth and SCS.
| Channel BW | Min guardband @15 kHz | @30 kHz | @60 kHz |
|---|---|---|---|
| 10 MHz | 312.5 kHz | 665 kHz | 1010 kHz |
| 20 MHz | 452.5 kHz | 805 kHz | 1330 kHz |
| 50 MHz | 692.5 kHz | 1045 kHz | 1610 kHz |
| 100 MHz | — | 845 kHz | 1370 kHz |
Two things fall out of this. First, wider SCS needs a larger absolute guardband (its subcarriers spill wider), which is another reason the high-SCS configurations lose PRBs. Second, the guardband is a minimum โ an operator may leave more, but never less, or the carrier would fail its adjacent-channel leakage requirements. When two carriers are aggregated inside one band, a similar inter-carrier guard keeps them from interfering. The related metric to watch is the occupied bandwidth ratio (occupied ÷ channel BW), around 98.28% for the 273-PRB / 100 MHz case โ high spectral efficiency versus LTE's ~90%.
Unlicensed NR: NR-U and the 5/6 GHz bands
Not all NR runs on licensed spectrum. NR-U (NR-based access to unlicensed spectrum, introduced in Release 16) lets NR operate in the shared 5 GHz and 6 GHz bands, either anchored to a licensed carrier (License-Assisted Access) or fully standalone.
| Band | Frequency | Duplex | Note |
|---|---|---|---|
n46 | 5150–5925 MHz | TDD (SDL-like, DL-only in some regions) | 5 GHz unlicensed / LAA spectrum. |
n96 | 5925–7125 MHz | TDD | 6 GHz unlicensed band. |
n102 | 5925–6425 MHz | TDD | Lower 6 GHz subset. |
Because this spectrum is shared with Wi-Fi and other users, NR-U must play fair. It uses Listen-Before-Talk (LBT) โ the radio senses the channel (an energy-detect clear-channel assessment) and only transmits if it is clear โ plus occupied-channel-bandwidth rules and power limits set by regional regulators. To fit LBT's channel-access granularity, NR-U adds wideband operation split into 20 MHz LBT sub-bands and features like the Channel Occupancy Time (COT) and configured-grant enhancements. Note that n96 reaching to 7125 MHz is precisely why the FR1 ceiling was defined at 7.125 GHz rather than a round "6 GHz". For an operator, NR-U is a cheap capacity top-up: no license fee, but no guaranteed access either, so it is best used as an opportunistic downlink-heavy booster over a licensed anchor.
Summary
Hold spectrum as a hierarchy. At the top, two frequency ranges: FR1 (410 MHzโ7.125 GHz, coverage + mid-band capacity, SCS 15/30/60 kHz, up to 100 MHz) and FR2 (24.25โ71 GHz mmWave, SCS 60/120/480/960 kHz, up to 2 GHz) with an empty gap between them. Inside each range sit licensed operating bands (n-numbers), each with fixed UL/DL ranges and a duplex mode โ FDD on low paired bands, TDD dominant in mid-band and all of FR2, plus the supplementary SUL and SDL carriers.
Inside a band you place carriers whose PRB count follows from bandwidth ÷ (12 × SCS), minus guard band โ the canonical result being 273 PRB for 100 MHz at 30 kHz. Two rasters discretise placement: the fine global frequency raster (ARFCN/NREF, step ΔFGlobal) for carrier centres, and the sparse synchronization raster (GSCN) for where an SSB may sit so blind cell search stays fast.
Everything traces back to TS 38.101-1/-2 and TS 38.104. Know the range boundaries, the 273-PRB headline, the duplex logic, and the two-raster split, and the rest of the spectrum picture assembles around them.
Q. What are the exact boundaries of FR1 and FR2, and why 7.125 GHz?
A. FR1 is 410 MHz to 7.125 GHz; FR2 is 24.25 to 71 GHz (FR2-1 to 52.6 GHz, FR2-2 to 71 GHz). The FR1 ceiling is 7.125 GHz โ not 6 GHz โ to include the 6 GHz unlicensed band n96, which reaches 7125 MHz.
Q. How many PRB does a 100 MHz carrier give, and does SCS change it?
A. 273 PRB at 30 kHz SCS; the same 100 MHz gives only 135 PRB at 60 kHz. Doubling SCS roughly halves the PRB count because each RB is 12 subcarriers and thus twice as wide.
Q. What is the difference between the frequency raster and the SS raster?
A. The global frequency raster (addressed by ARFCN/NREF, step ΔFGlobal) is a fine grid that pins where a carrier's center can sit. The synchronization raster (addressed by GSCN) is a much sparser grid limiting where an SSB can sit, so blind cell search only checks a handful of positions.
Q. Why is TDD so common in NR while FDD sticks to low bands?
A. Mid/high-band paired spectrum is scarce and 5G traffic is downlink-heavy, so TDD lets one unpaired block serve both directions with a configurable, DL-favoured slot ratio (and reciprocity aids beamforming). FDD survives on low bands where paired spectrum already exists.
Q. What do SUL and SDL solve?
A. SUL is a supplementary low-frequency uplink so a cell-edge UE can uplink far while still downlinking on a high band; SDL is a supplementary downlink-only carrier that adds DL capacity, aggregated with a normal band.
Where to go next
Spectrum sets the stage โ ranges, bands, and the raster that pins a carrier in place. The next step is how the UE actually finds a cell inside that spectrum, and how NR chops the carrier in time and frequency: