School of Specs TSG RAN — the group that specifies th…Quick start

Cheat sheet

TSG RAN — the group that specifies the radio

3GPP's radio groups in under an hour

Depth
Quick start
Chapters
4
Reading
15 min
Questions
16
Document
TS 38.300 v19.3.0
Sources cited
76

Back to the course

The shape of it

1 Who writes the rules for the radio

  1. 1 Who decides how a phone talks to a mast
  2. 2 The six groups, and what each one worries about

2 What they wrote, and where to read it

  1. 3 What NR is, read off the document itself
  2. 4 Where to look yourself, and what the record does not say

Keep these in your head

Easy to get wrong

The numbers, and where each came from

Every one was counted out of a file on this machine. Hover a row to read the question that produced it.

The document's own words

  • 1.7 Who decides how a phone talks to a mast

    The present document provides an overview and overall description of the NG-RAN and focuses on the radio interface protocol architecture of NR connected to 5GC (E-UTRA connected to 5GC is covered in the 36 series). Details of the radio interface protocols are specified in companion specifications of the 38 series.

  • 3.4 What NR is, read off the document itself

    RRC_INACTIVE is a state where a UE remains in CM-CONNECTED and can move within an area configured by NG-RAN (the RNA) without notifying NG-RAN. In RRC_INACTIVE, the last serving gNB node keeps the UE context and the UE-associated NG connection with the serving AMF and UPF.

The words

6 the course explains, out of 264 the document defines — all of them.

5GC
5G Core Network
AMF
Access and Mobility Management Function
NR
NR Radio Access
RNA
RAN-based Notification Area
SDAP
Service Data Adaptation Protocol
UPF
User Plane Function

Where to look it up

The 15 clauses of TS 38.300 this course is built from.

§1§4.1§4.2§4.3§4.4§4.5§4.6§5§5.1§6.1§6.10§7.1§7.2§9.2.2.1§12.1

The 47 named sources it cites, by what they are.

Specification 21

TS 38.300TS 38.211TS 38.212TS 38.213TS 38.214TS 38.331TS 38.321TS 38.322TS 38.323TS 38.401TS 38.413TS 38.423TS 38.473TS 38.101-1TS 38.104TS 38.133TS 38.508-1TS 38.521-1TS 38.523-1TS 38.533TR 38.914

Meeting 8

3GPPRAN#1123GPPRAN1#1253GPPRAN6#18-Decision Teleconference3GPPRAN#1133GPPRAN#1143GPPRAN1#124-bis3GPPRAN5#1103GPPRAN5#111

Working group 7

RANRAN6RAN1RAN2RAN3RAN4RAN5

Meeting document 6

RP-261197RP-260830RP-260831RP-260832R5-261705RP-260870

Pattern 5

address of one specification's information pageaddress of one specification's file folderaddress of one meeting's portal pageaddress of one meeting's document listaddress of one meeting document

Where to go from here

The raised numbers on this page

  1. 1629581 meeting documents of all of 3GPP in the local databaserows in the pygppe meeting-document table /var/www/whatthespec.net/data/database/api/api.sqlite, read 2026-08-04
  2. 811563 RAN meeting documents in the local databaserows in the pygppe meeting-document table /var/www/whatthespec.net/data/database/api/api.sqlite whose document number starts with one of RP-, R1-, R2-, R3-, R4-, R5-, R6-, read 2026-08-04
  3. 3230 work items were opened by a RAN plenary documentfolders under /var/www/whatthespec.net/data/data/wis whose metadata.json has a tdoc_code starting 'RP-', of 9406 work items in all, read 2026-08-04
  4. 3 active catalogue rows carry no usable grouprows in the pygppe specification catalogue /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite where active='yes' and wg is empty, '-' or '0', read 2026-08-04