Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TS 32.600  Word version:  17.0.0

Top   Top   None   None   Next
0…   2…

 

0  Introductionp. 4

Configuration Management (CM), in general, provides the operator with the ability to assure correct and effective operation of the PLMN network as it evolves. CM actions have the objective to control and monitor the actual configuration on the Network Elements (NEs) and network resources , 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 single actions on single NEs of the PLMN network, or as part of a complex procedure involving actions on many resources/objects in one or several NEs.
Clauses 4 to 6 give an introduction and description of the main concepts of CM, which are not mandatory for compliance with this specification. Clause 7 contains the specific definitions for the standardised interface Itf N, which are necessary to follow for compliance.
Clause 4 provides a brief background of CM, while Clause 5 explains CM services available to the operator. Clause 6 breaks these services down into individual CM functions, which support the defined services. Clause 7 defines the Itf N (see TS 32.102) to be used for CM.
Up

1  Scopep. 5

The present document describes the Configuration Management (CM) aspects of managing a PLMN network. This is described from the management perspective in TS 32.101 and TS 32.102.
The present document defines a set of controls to be employed to effect set-up and changes to a PLMN network in such a way that operational capability and Quality Of Service (QOS), network integrity and system inter working are ensured. In this way, the present document describes the interface definition and behaviour for the management of relevant NEs in the context of the described management environment. The context is described for both the management system (OS) and Network Element (NE) functionality.
Clause 7 contains the specific definitions for the standardised Itf-N, which are necessary to follow for compliance to this specification.
The Itf N 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 TS 32.150. For CM, a number of IRPs (and a Name Convention see TS 32.300) are defined, used by this as well as by other specifications for Telecom Management produced by 3GPP.
Up

Up   Top   ToC