The project MCCM was split into two phases covering the following scenarios to demonstrate the proper working of the Mobile Common Configuration Management implementation:
Scenario "Change code/frequency plan":
Changing the code/frequency plan of a complete area
Click here to view workflow process
Description:
In most mobile cellular networks the code/frequency plan is changed in regular intervals. The code/ frequency plan is an input from the Network Planning and Development Process to the Network Provisioning Process. Common Configuration Management in this scenario shall:
- Check the consistency of the code/frequency plan
- Recognize affected cells and generate the configuration files
- Distribute the code/frequency plan to the Network Element Managers
This has been demonstrated during TMW Chicago in November 2000. During Phase 2 the following scenarios have been implemented:
Scenario "New NodeB":
Taking new cell into service and add neighbour relationships
Description:
Setting up the infrastructure for UTRAN requires a frequent reconfiguration of the GSM/UMTS network or parts of it. To get operational a new NodeB has to be provided with a set of radio network parameters and neighbor relationships. These are to be introduced and checked for consistency including all related neighbour relationships. Neighbour relationships to be considered are:
- GSM <-> GSM
- GSM <-> UMTS
- UMTS <-> UMTS
where equipment and Network Element Managers of different manufacturers may be involved on every side. It shall be possible to send the cell and neighbour relationship parameters to the involved Network Element Managers.
During network setup, typically done by the supplier, tests and assignments of specific values to the equipment are performed. Thus a NodeB (and also other NEs) is visible across the interface-N already in an early phase of the network construction and might even be "pre"-configured on-site and set into operation. The current state of a NodeB is indicated by the UserDefinedState. When for example the NodeB is ready, the UserDefinedState is set to READY_FOR_INTEGRATION, this means that the NodeB can accept radio parameters.
The MCCM application, responsible for providing the NodeB with valid radio parameters and neighbour relationship information, detects this change of state and updates its current area‘, the master data area for delta calculation. Having received planning data, the MCCM tool can configure and activate the cell put up by this NodeB.
The MCCM application enables the user to create these neighbour relationship (handover definitions) interactively, without the planning department being involved. This is important if planning data for the new NodeB is not yet available from the planning dept.
Scenario "Optimisation":
Optimizing the radio network
Description:
The performance of the mobile cellular network is constantly monitored in the Network Data Management Process. Performance Data are given to the Network Planning and Development Process, which will evaluate whether a bad performance is due to poor parameter setting. In this case the Network Provisioning Process is ordered to change a very limited set of radio parameters. Common Configuration Management in this scenario shall
- Be able to upload the current radio parameter setting
- Check the influence of parameters that are planned to be changed on the current parameterisation
- Propose all necessary changes to keep the radio network consistent
- Generate the change information to be sent to the Network Element Managers