Release ledger
Canonical Atlas record
TS 29.675
User Equipment (UE) radio capability provisioning service; Stage 3
Release evolution
Compare evidence between releases
Use indexed version, Work Item and Change Request evidence to see what changed around this specification. This is an evidence trail, not a clause-by-clause normative diff.
Rel-18 snapshot
Work affecting this release
11 indexed Change Requests · 2 connected Work Items.
Showing 11 CR records from the available cross-release sample. Browse release CR records (JSON) →
CR 0045 — Update of info and externalDocs fields
CR 0044 — Update of info and externalDocs fields
CR 0043 — ProblemDetails RFC 7807 obsoleted by RFC 9457
CR 0042 — Update obsoleted IETF HTTP RFCs
CR 0041 — Resolve ENs on redirection responses
CR 0040 — Update of info and externalDocs fields
CR 0037 rev.1 — Support of temporary and permanent redirections
CR 0033 rev.1 — Adding the mandatory error code 502 Bad Gateway
CR 0034 — Update of info and externalDocs fields
CR 0033 — Adding the mandatory error code 502 Bad Gateway
CR 0037 — Support of temporary and permanent redirections
Version history
Indexed versions
Showing 29 of 29 indexed versions.
Atlas classifications
Meaning and provenance
No Atlas classifications have been attached yet.
Work Items
Standards work connected to TS 29.675
Enhancements to the Service-Based 5G System Architecture
Optimisations on UE radio capability signalling
Historical association · verification pendingStage 2 of RACS
(Small) Technical Enhancements and Improvements for Rel-16
Historical association · verification pendingService Based Interface Protocol Improvements Release 17
Historical association · verification pending(Small) Technical Enhancements and Improvements for Rel-17
Service Based Interface Protocol Improvements Release 18
(Small) Technical Enhancements and Improvements for Rel-18
Service Based Interface Protocol Improvements Release 19
(Small) Technical Enhancements and Improvements for Rel-19
Knowledge graph
Related standards
No graph edges indexed yet. The graph API is available at this JSON endpoint.