Release ledger
Canonical Atlas record
TS 24.259
Personal Network Management (PNM); 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-8 snapshot
Work affecting this release
8 indexed Change Requests · 2 connected Work Items.
Showing 8 CR records from the available cross-release sample. Browse release CR records (JSON) →
CR 0003 — Flow updates
CR 0004 — Correction of 3GPP URN link
CR 0005 — Cleanup of PNM stage 3
CR 0005 rev.1 — Cleanup of PNM stage 3
CR 0016 — XML example clarification
CR 0018 — Access flow corrections
CR 0001 — Correction of URN-value for Service Identifiers
CR 0002 — Conveying PN UE information using 3rd party Registration and ICSI/IARI corrections
Version history
Indexed versions
Showing 53 of 53 indexed versions.
Atlas classifications
Meaning and provenance
No Atlas classifications have been attached yet.
Work Items
Standards work connected to TS 24.259
Identification of Communication Services in IMS
Historical association · verification pendingPersonal Network Management
Historical association · verification pendingCT1 aspects of Stage 3 PNM
Historical association · verification pendingSupport of Personal Area Networks and Enhancements to Personal Network Management
Historical association · verification pendingStage 3 for Support of Personal Area Networks and Enhancements to Personal Network Management
Historical association · verification pending(Small) Technical Enhancements and Improvements for Rel-9
(Small) Technical Enhancements and Improvements for Rel-10
(Small) Technical Enhancements and Improvements for Rel-11
CT1 part of Impacts of RFC7044 for introduction of the new History-Info header field
Historical association · verification pending(Small) Technical Enhancements and Improvements for Rel-13
IMS Stage-3 IETF Protocol Alignment
Knowledge graph
Related standards
No graph edges indexed yet. The graph API is available at this JSON endpoint.