CTCafeTele
5G NR NTN ADVANCE  /  DAY 1  /  1.1 · 5G EVOLUTION & NETWORK VISION
KNOWLEDGE CHECK ↓
DAY 1 · LESSON 1.1 · ARCHITECTURE FOUNDATION

5G Evolution &
Network Vision

From the all-IP world of LTE to a service-driven, cloud-native 5G System — and why the road through 5G-Advanced inevitably leaves the ground and goes non-terrestrial.

eMBB URLLC mMTC NSA / SA NTN · Rel-17+
0 Gbps
IMT-2020 peak rate
0 ms
Target air latency
0/km²
Connection density
0
First NTN release (Rel-)
01
From LTE to NR

Four decades to reach one millisecond

Each generation solved one bottleneck: analog noise, digital capacity, mobile data, all-IP throughput. 5G NR is the first radio designed not for a single service — but as a configurable toolbox where latency, rate and density are dialed per use case.

1G
~1981 · NMT / AMPS
Analog voice
FDMA analog FM. No data, no encryption, no roaming standard.
≈ 2.4 kbps
2G
1991 · GSM
Digital voice + SMS
TDMA, SIM security, global roaming. GPRS/EDGE bolt data on.
≈ 384 kbps (EDGE)
3G
2001 · UMTS / WCDMA
Mobile data
CDMA air interface; packet domain arrives. HSPA+ pushes 42 Mbps.
≈ 42 Mbps (HSPA+)
4G
2009 · LTE / LTE-A
All-IP broadband
OFDMA + MIMO, flat EPC, VoLTE. Carrier aggregation to ~1 Gbps.
≈ 1 Gbps (LTE-A Pro)
5G
2019 · NR (Rel-15)
Service platform
Scalable OFDM numerology, mmWave, massive MIMO, cloud-native SBA core, slicing — and from Rel-17, satellites.
20 Gbps (IMT-2020 DL peak)
FIG 1.1-1 · Generation timeline — peak data rate shown on log-ish visual scale
DESIGN DIMENSION
4G · LTE
5G · NR
Subcarrier spacing
15 kHz, fixed
15/30/60/120 kHz, scalable μ FLEXIBLE
Max carrier bandwidth
20 MHz
100 MHz (FR1) · 400 MHz (FR2) 20×
Spectrum range
< 6 GHz
FR1 ≤ 7.125 GHz · FR2 to 71 GHz mmWave
Slot duration
1 ms TTI
1 → 0.125 ms + mini-slots
User-plane latency
~10 ms
< 1 ms (URLLC config) 10×
Uplink waveform
SC-FDMA only
CP-OFDM or DFT-s-OFDM
Always-on signals
CRS in every subframe
Lean carrier — SSB only ENERGY
Core network
EPC (point-to-point ifaces)
5GC — SBA, HTTP/2 APIs, slicing
QoS model
Bearer-based (EPS bearer)
QoS-flow based (5QI / SDAP)
FIG 1.1-2 · LTE vs NR — what actually changed in the radio & core
Interactive · Numerology Lab

Dial μ and watch the radio reshape itself

Orthogonal subcarriers — each peak sits exactly on its neighbours' nulls · Δf = 15 kHz × 2μ
One 1 ms subframe = 1 slot × 14 OFDM symbols
PDCCH / CORESETDM-RSPDSCH symbols
FIG 1.1-3 · Scalable numerology — the single biggest PHY idea NR added over LTE
THEORY · DEEP DIVE

Why scalable numerology exists — and why μ is a compromise

Subcarrier spacing is a three-way fight. The cyclic prefix must outlast the channel's delay spread — rural macro echoes arrive microseconds late, so wide-area coverage wants 15 kHz with its generous 4.69 μs CP. Phase noise grows brutally with carrier frequency — mmWave oscillators smear narrow subcarriers into each other, so FR2 demands 120 kHz. And the slot is the scheduler's heartbeat: it shrinks as 1/2μ, so URLLC pushes μ up to cut latency. NR refuses to crown one winner: μ is signalled per Bandwidth Part, so one gNB can serve 30 kHz eMBB and 120 kHz URLLC side by side on the same carrier.

The NTN twist (Day 3): at 600 km altitude even the longest CP is irrelevant against ±25 ms of propagation — satellite geometry is absorbed by timing advance, not by the cyclic prefix. Rel-17 NTN in S-band runs μ = 0/1, exactly the numerologies you just dialled.

Δf = 15 · 2μ kHzTslot = 1 / 2μ msTCP,normal ≈ 4.69 / 2μ μs14 symbols / slot (normal CP)
TS 38.211 §4.2–4.3TS 38.101-1/-2 channel BW
02
IMT-2020 Service Categories

One network, three personalities

ITU-R IMT-2020 defines three usage scenarios pulling the design in opposite directions. Click a corner of the triangle — every 5G feature you'll meet in this course exists to serve one of these corners.

IMT-2020 5G triangle eMBB Enhanced Mobile Broadband mMTC Massive Machine-Type URLLC Ultra-Reliable Low-Latency
FIG 1.1-4 · ITU-R M.2083 usage scenarios — interactive: select a corner
IMT-Advanced (4G)
ITU-R baseline that LTE-Advanced was certified against.
IMT-2020 (5G)
Eight key capabilities from ITU-R M.2083 — note the 10× latency cut, 100× efficiency and 10× connection density.
Where NTN strains
Satellite links can't hit 1 ms latency — but they crush the coverage axis no terrestrial network can reach. That tension shapes Days 2–4.
FIG 1.1-5 · IMT-2020 vs IMT-Advanced key capabilities (ITU-R M.2083 normalized targets)
THEORY · DEEP DIVE

From triangle corners to network slices

The triangle isn't marketing — it's encoded in the protocol. Every PDU session carries an S-NSSAI identifying its slice: SST 1 = eMBB, SST 2 = URLLC, SST 3 = MIoT (the mMTC corner), SST 4 = V2X, SST 5 = HMTC. The NSSF selects the slice, the PCF attaches policy, and each QoS flow is stamped with a 5QI whose standardized table row literally writes the corner's KPIs into every scheduler on the path — 5QI 1 for voice, 5QI 9 for best-effort eMBB, 5QI 82–85 for deterministic URLLC. One physical network, N logical ones.

Where this course goes (Day 4): slice continuity across TN and NTN — keeping an SST-2 SLA alive while the user plane rides a satellite. That's why the gauges above matter: a slice is a contract, and orbit changes what you can promise.

S-NSSAI = SST (8 bit) + SD (24 bit)5QI → {priority, PDB, PER}
TS 23.501 §5.15 slicing · §5.7 QoSITU-R M.2083
03
Deployment Models

NSA or SA — who anchors the control plane?

The single most important question of any 5G rollout. In NSA Option 3x the LTE eNB stays master and 5G NR rides as a secondary cell on the old EPC. In SA Option 2 the gNB talks natively to the 5G Core — unlocking slicing, sub-ms QoS flows and, later, NTN. Flip the switch and watch the control plane (dashed red) move.

EPC (4G Core) MME · S-GW · P-GW · HSS LTE eNB MASTER NODE (MeNB) en-gNB SECONDARY (SgNB) UE S1-C S1-U X2 (split bearer) LTE Uu (RRC) NR Uu (data)
5GC — Service-Based Core AMF · SMF · UPF · UDM · NRF · PCF · NSSF gNB CU + DU + RU · FULL RRC UE N2 (NGAP) N3 (GTP-U) NR Uu N1 (NAS, UE↔AMF) DN (N6)
Control plane User plane Inter-node
Press play — or click any step — to walk the attach signaling on the diagram above. Switch NSA ↔ SA to compare the two flows.
FIG 1.1-6 · EN-DC Option 3x vs SA Option 2 — animated signaling & data paths

NSA · Option 3x (EN-DC) FAST TO MARKET

  • LTE eNB is master — RRC anchor and mobility stay on 4G; NR adds a data-boost leg.
  • Reuses the deployed EPC; UE attaches with legacy NAS — no 5G registration.
  • In 3x, S1-U lands on the gNB, which splits the bearer over X2 toward LTE when needed.
  • No network slicing, no 5QI flows, no NTN — capabilities are capped by the EPC.
  • How most operators launched "5G" in 2019–2021.

SA · Option 2 FULL 5G SYSTEM

  • gNB connects natively to 5GC via N2 (NGAP control) and N3 (GTP-U data).
  • 5G NAS over N1: true 5G registration, PDU sessions, 5QI QoS flows.
  • Unlocks network slicing (NSSF/S-NSSAI), edge breakout, RedCap, precise positioning.
  • NTN requires SA — Rel-17 satellite access is specified against the 5G System, not EPC.
  • This course's labs (Open5GS + UERANSIM) run pure SA.
THEORY · DEEP DIVE

Why SA is the ticket to space

Separating control from user plane is 3GPP's longest-running refactor: CUPS in Rel-14 split the S/P-GW, and the 5GC finished the job — the AMF owns NAS signaling, the UPF owns packets, and the two scale independently. NTN leans on that separation hard. Rel-17 gives NAS its satellite patch: extended timers in TS 24.501, because a GEO round trip of ~541 ms would blow through terrestrial retransmission timers; new satellite RAT types — NR(LEO), NR(GEO) — visible to the AMF so the core knows it is serving an orbit, not a street; and per-orbit policy so an operator can treat a LEO PDU session differently from a fiber-fed one.

None of this exists in EPC/NSA. That single fact decides the architecture of every NTN deployment you will build in this course: it's SA, always.

TS 23.501 satellite access & RAT typesTS 24.501 NAS timers for satelliteTS 38.413 NGAP
04
3GPP Release Roadmap

Rel-15 → Rel-20: watch NTN grow up

3GPP ships 5G in releases, each frozen roughly every 18–24 months. Track the violet 🛰 chips — NTN enters as a study item, becomes a Rel-17 work item, and by Rel-19/20 satellites are first-class citizens on the road to 6G.

R15
Release 15FROZEN 2018 · "5G PHASE 1"NR is born
NR FR1 + FR2EN-DC (NSA)SA Option 25GC / SBAScalable numerologyNTN study starts (TR 38.811)
R16
Release 16FROZEN 2020 · "5G FOR INDUSTRY"Verticals arrive
URLLC enhancementsNR V2X sidelinkNR-U (unlicensed)IAB2-step RACHNTN solutions study (TR 38.821)
R17
Release 17FROZEN 2022 · ⭐ THE NTN RELEASESatellites become 3GPP radios
NR-NTN work item — normative!IoT-NTN (NB-IoT / eMTC)Common + UE-specific TA, GNSS-assistHARQ disabling, K_offsetRedCapFR2-2 up to 71 GHz
R18
Release 18FROZEN 2024 · "5G-ADVANCED"AI meets the air interface
AI/ML for NRXR awarenessNetwork energy savingNTN coverage & mobility enh.NTN above 10 GHz (Ka)IoT-NTN mobility
R19
Release 192025–26 · 5G-ADVANCED PHASE 2Regenerative & beyond
Regenerative payload (gNB on board)Store-and-forward IoT-NTNNTN-TN multi-connectivityAmbient IoTISAC studies
R20
Release 202026+ · BRIDGE TO 6GIMT-2030 studies begin
6G (IMT-2030) study phaseIntegrated TN + NTN 3D networksAI-native architectureNew spectrum (7–24 GHz)
FIG 1.1-7 · 3GPP roadmap — violet chips trace the NTN thread through every release
05
The Coverage Problem

Why 5G-Advanced leaves the ground

Terrestrial networks chase population, not area. Towers need power, backhaul and economics — oceans, deserts, airspace and disaster zones have none of the three. The only radio site that covers them all is in orbit.

0%+
of Earth's land mass has no terrestrial mobile coverage — towers follow people, not geography.
0%
of the planet is ocean — effectively 0% covered by ground networks, yet full of ships, sensors and aircraft routes.
0 ms
max round-trip time of a LEO @ 600 km transparent link (TR 38.821) — satellite latency is now usable.
TN CELL TN CELL COVERAGE GAP — ocean / desert / air GEO · 35,786 kmRTT ≈ 541 ms · fixed footprint MEO · ~8,000–20,000 kmRTT ≈ 95–180 ms LEO · 300–1,500 kmRTT ≈ 8–26 ms · moving cells!
FIG 1.1-8 · Three orbit classes — the LEO satellite sweeps; its beam serves the gap no tower reaches (delays per 3GPP TR 38.821)
LEO 400 MEO 8 000 GEO 35 786 UE GATEWAY → gNB → 5GC SERVICE LINK FEEDER LINK RTT — move the slider
Ping animation slowed for visibility — the readouts are exact (geometry at 10° elevation, transparent payload)
Interactive · Orbit Delay Lab

Fly the satellite, feel the physics

ALTITUDE600 km= TR 38.821 ✓
FIG 1.1-9 · Orbit Delay Lab — real orbital mechanics: v = √(GM/r), slant range at 10° elevation, RTT = 4 legs / c
Latency Race

Same question, four paths — who answers first?

FIG 1.1-10 · Round-trips completed in a fixed window — animation 20× slower than reality; counters use true RTTs
THEORY · DEEP DIVE

The physics floor no release can patch

Light covers 299,792 km every second — and that is the only spec 3GPP cannot rewrite. The lab above runs the true geometry: the slant range at 10° elevation follows d = RE(√((RE+h)²/RE² − cos²ε) − sin ε), and a transparent payload pays that distance four times per round trip (UE→satellite→gateway, then back). At 600 km that lands on 25.77 ms — matching TR 38.821 Table 4.2-2 to the hundredth of a millisecond. Every Day-3 mechanism — Koffset, extended HARQ timers, stretched RACH response windows — is engineering wrapped around these few milliseconds.

And the reason TCP hates satellites (Day 4): the bandwidth×delay product balloons while slow-start still creeps up one RTT at a time — a GEO link spends most of a short transfer just waiting for ACKs.

d = RE(√((r/RE)² − cos²ε) − sin ε)RTTtransparent ≈ 4·d / cv = √(GM/r)
TR 38.821 §4.2 delay tablesTR 38.811 channel models

Space layer

LEO mega-constellations, MEO and GEO. Rel-17 transparent payloads today; Rel-19 puts the gNB on board with inter-satellite links.

300 – 35,786 KM

Aerial layer

HAPS at ~20 km and UAV platforms — quasi-stationary, low delay, rapid deployment over disasters and events.

8 – 50 KM

Ground layer

Classic gNBs and small cells where density pays. In 6G's IMT-2030 vision all three layers fuse into one 3D network with seamless TN↔NTN mobility.

0 – 200 M
Q
Knowledge Check

Prove it — 5 questions

Instant feedback with 3GPP-grounded explanations. Score 4+ to consider Lesson 1.1 mastered.

Key Takeaways

Carry these into Lesson 1.2

1

5G NR is a configurable radio toolbox — scalable numerology, lean carrier and flexible slots let one standard serve eMBB, URLLC and mMTC.

2

NSA Option 3x anchors RRC on LTE over EPC; SA Option 2 connects gNB↔5GC via N2/N3 and unlocks slicing, 5QI flows — and NTN.

3

The NTN thread runs Rel-15 (study) → Rel-17 (normative NR-NTN + IoT-NTN) → Rel-18/19 (Ka-band, regenerative, store-and-forward) → Rel-20/6G.

4

Terrestrial networks cover people, not the planet: most land and all oceans are dark. LEO at ~600 km brings RTT down to ~26 ms — good enough to merge with 5G.

3GPP TS 38.300 · NR overall description 3GPP TR 38.811 · NTN study (Rel-15) 3GPP TR 38.821 · NTN solutions (Rel-16) ITU-R M.2083 · IMT-2020 vision 3GPP TR 21.917 · Rel-17 summary
NEXT · LESSON 1.2

End-to-End 5G System Architecture

UE → gNB → 5GC → Data Network: control vs user plane, the N1/N2/N3/N4/N6/N9 reference points, and the full registration + PDU session flow.

CONTINUE → 1.2