Canonical Atlas record

TS 32.300

Telecommunication management; Configuration Management (CM); Name convention for Managed Objects

Responsible WGS5
StatusUnder change control
Initial releaseRel-4
Selected releaseRel-11
Latest indexed version19.0.0
Series32
TypeTS

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.

Release ledger

Version · WI · CR evidence by release

Rel-44.1.21 WI1 CR · 1 approved
Rel-55.0.20 WI1 CR · 1 approved
Rel-66.3.12 WI5 CRs · 5 approved
Rel-77.2.02 WI2 CRs · 2 approved
Rel-88.0.00 WI0 CRs
Rel-99.2.02 WI5 CRs · 3 approved
Rel-1010.0.01 WI1 CR · 1 approved
Rel-1111.2.02 WI4 CRs · 2 approved
Rel-1212.2.02 WI7 CRs · 3 approved
Rel-1313.1.01 WI2 CRs · 1 approved
Rel-1414.0.00 WI0 CRs
Rel-1515.0.00 WI0 CRs
Rel-1616.0.00 WI0 CRs
Rel-1717.1.01 WI1 CR · 1 approved
Rel-1818.1.01 WI5 CRs · 3 approved
Rel-1919.0.00 WI0 CRs
R99no version indexed1 WI0 CRs

Rel-11 snapshot

Work affecting this release

4 indexed Change Requests · 2 connected Work Items.

Showing 4 CR records from the available cross-release sample. Browse release CR records (JSON) →

CR 0014 rev.1 — CR Rel-11 32300-b00 Clarify wild card usage Name Convention

CR 0014 — CR Rel-11 32300-b00 Clarify wild card usage Name Convention

CR 0013 — CR R11 32300 on DN capilization

CR 0015 — S5-Qingdao E CR Rel 11 32300 on code set clarification v2

Version history

Indexed versions

Showing 37 of 37 indexed versions.

19.0.0Rel-19SA#1092025-10-23
18.1.0Rel-18SA#1062025-01-10
17.1.0Rel-17SA#1062025-01-10
18.0.0Rel-18SA#1022024-01-05
17.0.0Rel-17SA#95-e2022-03-31
16.0.0Rel-16SA#88-e2020-07-10
15.0.0Rel-15SA#802018-06-26
14.0.0Rel-14SA#752017-03-29
13.1.0Rel-13SA#712016-03-17
13.0.0Rel-13SA#702016-01-14
12.2.0Rel-12SA#682015-06-26
12.1.0Rel-12SA#662014-12-22
12.0.0Rel-12SA#632014-03-17
11.2.0Rel-11SA#602013-06-27
11.1.0Rel-11SA#592013-03-15
11.0.0Rel-11SA#562012-06-29
10.0.0Rel-10SA#512011-04-01
9.2.0Rel-9SA#482010-06-18
9.1.0Rel-9SA#462009-12-18
9.0.0Rel-9SA#452009-10-01
8.0.0Rel-8SA#422008-12-22
7.2.0Rel-7SA#382007-12-17
7.1.0Rel-7SA#372007-10-03
7.0.0Rel-7SA#362007-06-20
6.3.1Rel-6SA#322006-07-05
5.0.2Rel-5SA#322006-07-05
4.1.2Rel-4SA#322006-07-05
6.3.0Rel-6SA#302005-12-20
6.2.0Rel-6SA#282005-06-23
6.1.0Rel-6SA#272005-04-01
6.0.0Rel-6SA#262005-01-04
5.0.1Rel-5SA-#182003-01-13
4.1.1Rel-4SA-#182003-01-13
5.0.0Rel-5SA-#172002-09-18
4.1.0Rel-4SA-#142002-01-11
4.0.0Rel-4SA-#122001-07-03
2.0.0Rel-4 · pre-approvalSA-#122001-06-18

Atlas classifications

Meaning and provenance

No Atlas classifications have been attached yet.

Work Items

Standards work connected to TS 32.300

WI 2082

Configuration Management

Rel-4official
WI 35014

Network Infrastructure Management

Rel-6official
OAM6

Rel-6 Operations, Administration, Maintenance and Provisioning (OAM&P)

Rel-6official
OAM7

Rel-7 Operations, Administration, Maintenance and Provisioning (OAM&P)

Rel-7official
OAM7-NIM

Rel-7 Network Infrastructure Management

Rel-7official
OAM9

Rel-9 Operations, Administration, Maintenance and Provisioning (OAM&P)

Rel-9official
OAM9-NIM

Rel-9 Network Infrastructure Management

Rel-9official
OAM10

Rel-10 Operations, Administration, Maintenance and Provisioning (OAM&P)

Rel-10parsed
OAM-FMC-IRP

IRP framework enhancements to support Management of Converged Networks

Rel-11parsed
OAM11

Rel-11 Operations, Administration, Maintenance and Provisioning (OAM&P)

Rel-11parsed
OAM-SHARE-SA5imp

OAM aspects of Network Sharing - Impacts on existing specifications

Rel-12official
OAM12

Rel-12 Operations, Administration, Maintenance and Provisioning (OAM&P)

Rel-12parsed
OAM13

Rel-13 Operations, Administration, Maintenance and Provisioning (OAM&P)

Rel-13parsed
TEI17

(Small) Technical Enhancements and Improvements for Rel-17

Rel-17parsed
eSBMA

Service based management architecture

Rel-18parsed
OAMCM,CM

OAM Configuration Management

R99official

Knowledge graph

Related standards

No graph edges indexed yet. The graph API is available at this JSON endpoint.