52indexed specifications
14working groups
—indexed Work Items
4provenance classes
Standards Matrix
Where does each specification sit?
Full-corpus placement uses series-level inference unless a spec has reviewed Atlas placement. Open a specification to move to its canonical record.
✓ official◇ parsed● curated◌ inferred
abstraction ↓ / system →
Services
UE
RAN
Core
OAM
Cross-cutting
Test
Stage 1
Stage 2
Stage 3
Radio
Security
Management
Conformance
Specification
TS 23.501
5GS architecture
Working groupSA2
System domainCore
AbstractionStage 2
Release lensRel-98
Status—
Initial release—
Latest version—
Series23
Why read this?
The architectural anchor for 5GS: network functions, reference points, service-based architecture, mobility, sessions, slicing and policy interactions.
5GCSlicingMobilityQoSNTN
Specification relationships
curated fallbackcuratedcurated fallback
curatedcurated fallback
curatedcurated fallback
curatedcurated fallback
curatedcurated fallback
curatedcurated fallback
curatedcurated fallback
curatedcurated fallback
Lens stack
Same spec, different questions
WGSA2Who owns it?
Series23How is it numbered?
LayerCoreWhere is it used?
StageStage 2What abstraction level?
Trust model
Every relationship has provenance
✓ official◇ parsed● curated◌ inferred
Official = 3GPP metadata. Parsed = deterministic extraction. Curated = reviewed Atlas classification. Inferred = machine suggestion requiring review.
Reviewed semantic coverage ↗