URLLC and eMBB — The service classes, as configurations
5G Systems Notes · Concept map · URLLC and eMBB
Route · Hierarchy · Index · All concepts · Hub
RF and system
Where it sits
What it is
What they are. The three service classes 5G was designed around. They are not modes — the physical layer has no switch labelled URLLC. They are configurations, and every knob has already appeared in these notes.
| Class | Target | Clause | How the physical layer delivers it |
|---|---|---|---|
| eMBB enhanced mobile broadband | 20 Gbit/s peak DL; 4 ms user-plane latency | TR 38.913 §7.1, §7.5 | Wide bandwidth, carrier aggregation, many layers, high MCS. The default assumption of every other note here. |
| URLLC ultra-reliable low latency | 1 − 10−5 for 32 bytes within 1 ms; 0.5 ms user-plane latency | TR 38.913 §7.9, §7.5 | High numerology, mapping type B (PDSCH §8.2), CQI table 3 aimed at 10−5 (§10.2), short allocations, PDCP duplication. |
| mMTC massive machine-type | Connection density; 10 years battery; coverage at 164 dB MaxCL | TR 38.913 §7.6, §7.11, §7.10 | Narrow bandwidth, aggressive DRX, repetition, and the reduced-capability device profiles. |
Table 1: The three service classes, their targets from TR 38.913 clause 7, and the physical-layer settings that deliver each. The right-hand column is the point: nothing here is a new mechanism. URLLC is the same PDSCH as eMBB with four constants changed, which is the sense in which the service classes are configurations rather than modes.
PDSCH §12.3 checks the URLLC row arithmetically — a 120 kHz round trip is 375 µs against a 0.5 ms budget, which is why the numerology has to be high.
Read on
This concept was first written up in ref-system, which reads the whole group as one argument.
Before this concept, the hierarchy says to learn the following — the full chain, in order:
Keep going — where this sits on the route
5G Systems Notes · Concept map · URLLC and eMBB
Top · Concept map · Hub