Content for  TS 32.661  Word version:  17.0.0

Top   Top   None   None   Next
0…   2…


0  Introductionp. 4

The present document is part of a TS-family covering the 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; as identified below:
  • TS 32.661: Configuration Management (CM); Kernel CM Requirements
  • TS 32.662: Configuration Management (CM); Kernel CM Information Service (IS)
  • TS 32.666: Configuration Management (CM); Kernel CM Integration Reference Point (IRP); Solution Set (SS) definitions
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 , 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 3G network, or as part of a complex procedure involving actions on many resources/objects in one or several NEs.

1  Scopep. 5

The present document defines, in addition to the requirements defined in TS 32.101, TS 32.102 and TS 32.600, the requirements for the present IRP: Kernel Configuration Management IRP. It is the intent of Kernel Configuration Management to provide an IRP that contains the configuration management functionality that is basic and minimal. It is the functionality that is common to and required by both Basic CM and Bulk CM. While neither the Basic CM IRP nor Bulk CM IRP requires the other, they each require the Kernel CM IRP.

Up   Top   ToC