Scheduling — Who gets the grid, this slot

5G Systems Notes · Concept map · Scheduling Route · Hierarchy · Index · All concepts · Hub

Procedures over time

Where it sits

Sits atLevel 10 of the hierarchy · Procedures over time · explained
Also writtensemi-persistent
The 1 of them
SPS — semi-persistent scheduling — a grant that repeats without a DCI each time
Learn firstMAC · DCI — 21 concepts in the full chain, see the paths
UnlocksNothing else depends on it directly.
Primary clauseTS 38.213 §10, TS 38.321 §5.4
Used inref-system 4 · nr-frame-structure 4 · nr-pdsch 4 · ref-session 4 · nr-srs 3 · index 2 · ref-signals 2
Scanned from the notes at page load and joined with terms.json; nothing on this card is typed by hand.

What it is

What it is. Deciding, every slot, which devices get which resources. The one thing 3GPP deliberately does not specify.

What is specified is the vocabulary: what a grant looks like (PDSCH §8), where a device must look for one (search space), how it acknowledges (PUCCH), and how the device prioritises among its own logical channels (TS 38.321 clause 5.4).

What is not specified is the policy — which device to serve when several are waiting. Round robin, proportional fair, delay-sensitive, or anything else. That is where vendors compete, and leaving it open is deliberate.

Three flavours of allocation exist:

SPS is control overhead traded against flexibility. A voice packet every 20 ms does not need a fresh grant each time, and the PDCCH it would consume is a scarce resource (aggregation levels). The cost is that the allocation cannot follow the channel.

Read on

This concept was first written up in ref-system, which reads the whole group as one argument.

Widget not found: sim_status

Before this concept, the hierarchy says to learn the following — the full chain, in order:

To understand Scheduling (level 10) you first need 21 other concepts. Read them in this order — everything on one line can be read in any order, but no line before the one above it:
Immediately before Scheduling: DCI, MAC.
Keep going — where this sits on the route
Nothing depends on this one directly
It is a leaf of the graph — follow the route rather than the branch.
The route is every concept in the folder ordered by level, so nothing here needs anything after it. Computed at page load from terms.json; the same numbering as the route page.
5G Systems Notes · Concept map · Scheduling Top · Concept map · Hub