Introduction

32.106-83GPPConfiguration Management (CM)Part 8: Name convention for Managed ObjectsRelease 1999Telecommunication managementTS

Configuration Management (CM), in general, provides the operator with the ability to assure correct and effective operation of the 3G network as it evolves. CM actions have the objective to control and monitor the actual configuration on the Network Elements (NEs) and Network Resources (NRs), and they may be initiated by the operator or by functions in the Operations Systems (OSs) or NEs.

CM actions may be requested as part of an implementation programme (e.g. additions and deletions), as part of an optimisation programme (e.g. modifications), and to maintain the overall Quality Of Service (QOS). The CM actions are initiated either as a single action on a NE of the 3G network or as part of a complex procedure involving actions on many NEs.

The Itf-N interface for CM is built up by a number of Integration Reference Points (IRPs) and a related Name Convention, which realise the functional capabilities over this interface. The basic structure of the IRPs is defined in to 3G TS 32.101 [11] and 3G TS 32.102 [12]. For CM, a number of IRPs (and the Name Convention) are defined herein, used by this as well as other specifications for Telecom Management (TM) produced by 3GPP. All these are included in 3G TS 32.106 from Part 2 and onwards.

The present document is Part 8 of 3G TS 32.106 (3G TS 32.106-8) – Name Convention for Managed Objects.

Current problems

At present, multiple name conventions are used by different vendors’ NEs, or even within the same vendor, to name network resources. Following problems arise:

  • Different classes of NE use different name conventions. Network Management applications, when interfacing with these NEs, are required to understand multiple name conventions to manage the NEs.
  • Network management applications (e.g., Fault Management application), when interfacing with other applications (e.g., Configuration Management application, trouble ticket system) are required to understand multiple name conventions.
  • When a customer purchases multiple classes of NEs from the same or different vendors, the customer is confronted with multiple name conventions.
  • Without a name convention, it is difficult to integrate IRP conformant vendors’ resource name space (see subclause 3.1.5 for definition of name space) into the customer’s Enterprise name space.

Benefits

The benefits of using the subject name convention to name 3G network resources for network management purposes are as follows:

  • A resource name is guaranteed to be unambiguous in that it refers to, at most, one network resource. Unambiguous naming of managed network resources is necessary for interoperability among managing applications and systems.
  • The resource name syntax is specified such that management applications can be designed with assurance that its name-parsing algorithm needs not be modified in the future. We can derive this benefit only if the subject name convention is widely accepted.

The root and upper portions of the name hierarchy are based on name infrastructure of Domain Name System (DNS) (see IETF RFC2247 [5]). The subject name convention can naturally fit in DNS and can integrate well with other hierarchical naming systems, such as ITU-T Recommendation X.500 [2].