Numerology, live — computed while you read

5G Systems Notes · Concept map · Numerology · live ← the written note · Simulator ↗ · Hub

computed at page load   The working half of Numerology. That page is the explanation; this one is what the simulator can compute about it, kept apart so the written note stays a document rather than a control panel.

In one line. Every number below is produced by 5G Simulation/src/nrsim/ while this page renders, from the same code its tests run against — so nothing here can drift from what the written note says.

The seven numerologies

Every value derived from μ alone, and each row asserted to close to exactly 1 ms per subframe. μ is not a frequency-range property — TS 38.211 defines all seven for the physical layer, and it is the channel-bandwidth tables that pick three for FR1 and four for FR2.

Widget not found: sim_show

Seven here, three in a channel

Why TS 38.211 defines seven and TS 38.101-1 tabulates three.

Widget not found: sim_show

What FR1 actually offers

The 15, 30 and 60 kHz spacings of TS 38.101-1 Table 5.3.2-1.

Widget not found: sim_show

What FR2 actually offers

TS 38.101-2 Table 5.3.2-1 — 120 kHz across 50 to 400 MHz. The same clause 5.3.3 formula computes both guards, in both ranges.

Widget not found: sim_show

Where this comes from

Computed, not transcribed. ../widgets/sim_show.py imports the simulator's specification and parameter tiers inside the engine process. Those tiers are stdlib-only precisely so this is possible — the engine's own environment has no NumPy, which is also why anything from the physical layer (LDPC, HARQ, the waveform) cannot appear here and is offered as a nrsim show command on the written note instead.

This page is generated by tools/make_live_pages.py from LIVE_FOR in that widget. To change what appears, edit the declaration, not this file.

5G Systems Notes · Concept map · Numerology · live ← the written note · Simulator ↗ · Hub