Release ledger
Canonical Atlas record
TS 29.217
Policy and Charging Control (PCC); Congestion reporting over Np reference point
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-14 snapshot
Work affecting this release
18 indexed Change Requests · 1 connected Work Item.
Showing 12 CR records from the available cross-release sample. Browse release CR records (JSON) →
CR 0030 rev.2 — Diameter Load Control Mechanism
CR 0031 — Diameter base protocol specification update
CR 0031 rev.1 — Diameter base protocol specification update
CR 0032 — Diameter Load Control Mechanism
CR 0033 — Support of long and short Macro eNodeB IDs
CR 0033 rev.1 — Support of long and short Macro eNodeB IDs
CR 0033 rev.2 — Support of long and short Macro eNodeB IDs
CR 0040 — Vendor-Specific-Application-Id AVP handling
CR 0035 — Reference update for draft-ietf-dime-load
CR 0035 rev.1 — Reference update for draft-ietf-dime-load
CR 0037 — Support for signaling transport level packet marking
CR 0039 — Support for signaling transport level packet marking
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.217
Stage 3 PCC within SAE
(Small) Technical Enhancements and Improvements for Rel-13
BB1: RAN Downlink Traffic Differentiation, Congestion Detection and Reporting
CT3 part of CT aspects of User Plane Congestion Management for BB1
CT aspects of User Plane Congestion Management for BB1
Continuation of the Overload Control for PCC based Diameter applications
CT aspects of voice over E-UTRAN Paging Policy Differentiation
(Small) Technical Enhancements and Improvements for Rel-14
CT aspects of 5G System - Phase 1
(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.