Description
In 3GPP management architecture, information is modelled as classes of managed objects (Information Object Classes, IOCs), each of which can have multiple instances. A naming attribute is a special class attribute whose value uniquely identifies an instance of that class within its naming scope. It is defined in 3GPP TS 28.821 (and referenced in TS 32.152 and TS 32.156) and is closely tied to the Top_ IOC defined in TS 28.620, which is the root class from which all managed object classes inherit. The attribute 'id' of Top_ is the canonical naming attribute: every managed object instance carries an identifier that distinguishes it from its siblings.
The concept originates in the ITU-T/OSI Common Management Information Service (CMIS) and Guidelines for the Definition of Managed Objects (GDMO) tradition, where each managed object class has a distinguished naming attribute that forms part of its Distinguished Name (DN). In 3GPP, the naming attribute plays the same role: it is the first component used when constructing the hierarchical DN of a managed object instance. For example, in a 3GPP management model, an instance of a class such as ManagedElement or GNBDUFunction is named by its id attribute, and the full DN is built by concatenating the naming attributes of the instance and all its ancestors up to the root.
Naming attributes are essential for the operation of the management interface. When a manager (e.g., an OSS or a network management system) issues a create, read, update, or delete operation via the management protocol (e.g., NETCONF, RESTCONF, or the older CMIP/XML-based interfaces), it must specify the target instance by its DN, which is composed of naming attributes. The naming attribute also enforces uniqueness: two instances of the same class under the same parent cannot share the same naming attribute value.
The definition in TS 28.821 is deliberately concise: 'It is a class attribute that holds the class instance identifier. See attribute id of Top_ in TS 28.620. See examples of naming attribute in 3GPP TS 32.300.' This reflects the fact that the naming attribute is a meta-model concept rather than a specific data field — it is a role that an attribute plays within a class definition. Any attribute can be designated as the naming attribute of a class, provided it satisfies the uniqueness requirement within the naming scope.
In practice, naming attributes enable stable references to managed objects across management sessions, support the hierarchical containment tree of the management information base, and allow generic management operations to be applied without knowledge of the specific class. They are therefore a foundational building block of 3GPP's management framework, used by all IOCs in the 28-series and 32-series specifications.
Purpose & Motivation
The naming attribute exists to solve the fundamental management problem of uniquely identifying managed object instances in a hierarchical, object-oriented management information base. Without a well-defined naming mechanism, a manager could not reliably address a specific instance for read, write, create, or delete operations, and the containment relationships between objects (e.g., a cell contained in a gNB function contained in a managed element) could not be expressed unambiguously.
The concept was inherited from OSI management (GDMO/CMIS) and adapted by 3GPP for its own management models. In early 3GPP releases, the definition was minimal — Rel-9 simply said 'See 3GPP TS 32.300' — because the naming attribute was considered self-evident from the referenced specification. As the management models grew more complex and the Top_ IOC was formally introduced in TS 28.620, the definition was expanded to explicitly state that a naming attribute holds the class instance identifier and to point to the 'id' attribute of Top_ as the canonical example.
The naming attribute also supports the evolution from CMIP-based to model-driven management (NETCONF/YANG and RESTCONF). In YANG models, the equivalent concept is the 'key' leaf of a list, and 3GPP's naming attribute maps directly onto this. This continuity allowed 3GPP to migrate its management interfaces to modern protocols without losing the ability to uniquely address managed objects.
What changed in its specifications
The latest release-to-release comparison of specifications that define Naming attribute. Each summary describes the whole specification, not only this term.
Rel-9 added UML model element descriptions, refined stereotypes, introduced new definitions, and removed outdated samples in TS 32.152.
Full comparison in TS 32.152 →Rel-19 added model-driven SBMA usage description and changed requirement strength of two attribute properties.
Full comparison in TS 32.156 →Release Timeline
Evolution Across Releases
An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.
Defining Specifications
3GPP specifications that define or reference Naming attribute, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 28.821 vd00 | FMC UML Model Repertoire | Rel-13 read |
| TS 32.152 ve10 | IRP Information Service UML Repertoire | Rel-14 read |
| TS 32.156 vk20 | UML Model Repertoire for Network Management | Rel-20 read |