Release ledger
Canonical Atlas record
TS 32.551
Telecommunication management; Energy Saving Management (ESM); Concepts and requirements
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-10 snapshot
Work affecting this release
8 indexed Change Requests · 1 connected Work Item.
Showing 8 CR records from the available cross-release sample. Browse release CR records (JSON) →
CR 0002 rev.1 — Add energy saving compensation deactivation requirement
CR 0003 rev.1 — Modify the requirements about traffic threshold and time duration for Energy Saving Management (ESM)
CR 0004 — Modify errors in state name and in section title
CR 0005 — CR R10 32.551 Clarify the description of energy saving compensation activation and deactivation over Itf-N
CR 0005 rev.1 — Clarify the description of energy saving compensation activation and deactivation over Itf-N
CR 0006 — Correct requirements for EM-centralized Energy Saving Architecture
CR 0023 — CR R10 32.551 Correction of load characteristic for ES
CR 0001 rev.1 — Modify the energy saving compensation related use cases
Version history
Indexed versions
Showing 19 of 19 indexed versions.
Atlas classifications
Meaning and provenance
No Atlas classifications have been attached yet.
Work Items
Standards work connected to TS 32.551
OAM aspects of Energy Saving in Radio Networks
Management of Carrier Aggregation for LTE
Historical association · verification pendingInter-RAT Energy Saving Management
Rel-11 Operations, Administration, Maintenance and Provisioning (OAM&P)
Compliance of 3GPP SA5 specifications to the NGMN Top Operational Efficiency (OPE) Recommendations
Historical association · verification pendingTS work on Compliance of 3GPP SA5 specifications to the NGMN Top Operational Efficiency (OPE) Recommendations
Historical association · verification pendingKnowledge graph
Related standards
No graph edges indexed yet. The graph API is available at this JSON endpoint.