32.106-13GPPConfiguration Management (CM)Part 1: Concept and requirementsRelease 4Telecommunication managementTS
While a 3G network is first installed and brought into service, and following installation the 3G network operator will enhance and adapt the network to short and long term requirements. In addition, it will be optimised to satisfy customer needs. To cover these aspects of CM, the system will provide the operator with the following capabilities:
– initial system installation to establish the network;
– system operation to adapt the system to short term requirements;
– system up-date whenever it is necessary to modify the system to overcome SW bugs or equipment faults;
– system up-grade to enhance or extend the network by features or equipment respectively.
These capabilities are provided by the management system through its service components:
– system modification to change the network to meet the operators requirements;
– system monitoring to gain an overview on the present SW, equipment and data situation of the network.
The service components will be explained in more detail in the following subclauses.
5.1 System modification service component
Whenever it is necessary to adapt the system data to a new requirement due to optimisation or new network configurations, it will require an operator action to introduce new or modified data into the system. The data will be distributed to:
– either one EM/NE when dealing with a locally limited modification; or
– each EM/NE concerned when the change affects multiple EM/NEs; and
– the other NMs in the case where multiple NMs exist in the same management domain.
This implies the necessity of mechanisms to ensure data integrity and to maintain system data consistency (cf. subclause 18.104.22.168).
The concept of system modification includes the following aspects:
– if subscriber traffic impacting data modifications are performed, the NEs/NRs concerned are first cleared from traffic in a controlled way;
– the necessary modification is performed by the EM/NE;
– only once all needed data is given to the system, are the concerned NEs/NRs put back into traffic again;
– safeguards shall be available within the NEs to prevent changes to configuration affecting service(s) in use.
In emergencies, it shall be possible to override these safeguards.
On occasion, modifications may not be stable or not fulfil the operator intentions. In these cases, reversion to the previous stable configuration may be necessary. Occasionally there will be changes to the network that create a new configuration, which cannot revert to any previous network status for protection. Such changes may involve major equipment modification to the core elements of the network or re-distribution of traffic across interconnected nodes to other Operators. In these cases it is necessary to implement the changes and to manage the consequences of any problems or failures without the protection of ‘reversion’, as equipment may have been removed or the work programme may be complex, time limited and expensive.
Progress of these changes should be sequential through an agreed milestone plan which includes effective tests to prove network functionality with only one action, or a coherent series of actions, completed at a time. The decision points, beyond which there is no return, should be clearly identified.
"Automatic re-configuration" shall not be dealt with in the present document as it is dependent on the implementation. However, if an automatic re-configuration occurs, the operator shall be informed of the result.
5.2 System monitoring service component
The system monitoring service component provides the operator with the ability to receive reports (on request or spontaneously) on the configuration of the entire network or parts of it from managed NEs. These consist of structure, states, versions employed and data settings. The NE sends spontaneous reports if there was an autonomous change of, for example, the states or other values due to Fault Management (FM) actions. Also, the NM may ask the managed EM/NE to send the information required to the NM at any time.
The data that shall be possible to provide on request is a subset of, or the whole, MIB, which is an instantiation of the NRM, defined in 3G TS 32.106-5 .
Any inconsistencies found during system monitoring by the NM should be reported to the operator, and it is left to the operator or an Operations System Function (OSF) to take appropriate actions.