CM Operations Manager is used to provision complete, prepared plans to the network. The plan can be provisioned as a whole or partially. When provisioning partial plans, note that plan preparation can add new objects that are outside the selected provision- ing scope. These objects need to be provisioned in a separate operation.
There are two different ways to provision a plan to the network using CM Operations Manager user interface:
Activate: direct activation where the plan is transferred to the network and the plan values are taken into use immediately.
Pre-activate + Activate Pre-activated Plan: The plan is first transferred to the network, but the plan values are taken into use in a separate operation. Preactivating a plan does not affect the network traffic.
Activating a plan affects the network traffic, but it can be carried out in a controlled manner. You can define the scale of impact on traffic that is allowed during the configu- ration change.
A plan can contain changes on several network technologies and different element ver- sions.
The status of provision operation executed by the user in CM Operations Manager can be monitored in CM Operations Manager user interface. For more information, see section Operation statuses in CM Operations Manager.
The following figure illustrates the interfaces and databases in the network elements used during plan provisioning process:
Figure 41 Interfaces and databases in the network elements used during plan provi- sioning process
7.5.1
RNC plan activation and pre-activation
Pre-activate Fall Back Activate Active Fallback New Active Plan Pre-activate Activate New Plan Activate Pre-activate Activate Pre-activated PlanSave active config. as fallback Fall back via MML Activate Plan Active New Plan New Plan Activate Active New Plan Q3 File based provisioning NWI3 NWI3 MML MML Q3 BSC RNC AXC FTM 2G SGSN Fallback Pre-activate Activate
New Plan Active Plan
WBTS IADA (I-HSPA) Activate Pre-activated Plan New Plan New Plan Activate Active MSC/MGW NWI3 Activate Pre-activated Plan Activate Pre-activated Plan
(WCDMA and I-HSPA)
Pre-activate
Activate
New Plan Active Plan
eNB (LTE) Activate Pre-activated Plan NWI3 BSC Pre-activate BTS Activate Activate Pre-activated Plan Q3 BTS specific
base. When a plan is pre-activated, it is transferred to the New/Plan database to wait for the activation.
There are three modes for RNC plan activation: Object by Object (Slow), Use Activation Groups (Moderate), All Objects Parallel (Fast).
The Object by Object (Slow) mode is the slowest mode as it activates the objects one by one. The next object is handled only after the previous object has been updated to the NetAct Configurator database and the network. This mode has least impact on the network traffic. COCO objects are always activated using Object by Object mode.
The Use Activation Groups (Moderate) mode divides the planned WBTSs in sets containing WBTSs that are not adjacent to each other. All WBTSs in the set are updated parallel, first in the Configurator database and then the network. The same procedure is repeated for all WBTS sets until all modification rounds are completed. In this way, the dropped calls can be minimized and the activation time reduced sig- nificantly.
The All Objects Parallel (Fast) mode updates all planned WBTSs in the Configurator database and the network in one single round. This mode can have an effect on the traffic in the network if the objects need to be locked for modification. If locking is not required, this mode is the recommended and fastest solution.
Depending on the used tools, the defined default modes are different:
Use Activation Groups (Moderate) mode for generic plan activation from CM Oper- ations user interface
All Objects Parallel (Fast) mode for rehosting plan activation from CM Operations user interface
Object by Object (Slow) mode for Command Line Interface - originated plan activa- tion
7.5.2
BSC plan activation and pre-activation
For BSC provisioning, there are two methods available:File-based plan provisioning
Q3-based plan activation (only for BSC S13 release)
File-based plan provisioning
File-based plan provisioning offers better performance compared to the obsolete Q3- based plan activation method.
Impact on the network traffic can be controlled to reduce the number of dropped calls. You can also define the service impact level of the activation operation. For more infor- mation, see CM Operations Manager Help.
If needed, the plan file can be first transferred to the Plan database in BSC (pre-activate operation), and then activated separately (activate operation).
The plan is automatically validated before activation. Validating means cross-checking in BSCs to ensure that the plan is correct for activation. The validation logs can be reviewed in CM Operations Manager. If needed, a plan can be validated separately and
You can save the latest active configuration as a fallback and restore it using MML. You can check if an active configuration is stored as fallback before you start the activation. Since BSC S14 release, you do not longer need to select the method of plan provision- ing. Instead, the new mechanism of plan provisioning is used. At first all parameters sup- ported by file-based plan provisioning are activated using file-based plan provisioning method. Then the parameters not supported by file-based plan provisioning are auto- matically activated using new XML Send To Network functionality. All the operations are performed and controlled by the system. You do not need to choose the activation method.
For BSC S13 release, the objects and parameters not supported by file-based plan pro- visioning are left untouched during the plan provisioning operation. They must be acti- vated separately using Q3-based plan activation method. The following changes are not possible via file-based plan provisioning for S13 release:
BSS and Site Synchronisation do not allow moving BCFs from one chain to another in the plan.
You cannot modify the attached Dynamic Frequency and Channel Allocation (DFCA) mobile allocation (MA) lists of the DFCA hopping BTS(s).
You can create, modify, and delete Link Access Procedure on the D-channel (LAPD) and Transmission Network Element (TRE) objects locally after the RNW plan is downloaded. However, when the RNW plan is downloaded, local changes to LAPD and TRE RNW objects are not recommended as they may cause problems during plan activation.
No support for segment reconfiguration.
For a list of objects not supported by file-based provisioning, see Appendix: Objects not
supported by file-based plan provisioning.
Q3-based plan activation (only for BSC S13 release)
Q3-based plan activation is the obsolete method of plan provisioning, which can be used only for BSC S13 release. The method supports all BSC objects and parameters. The configuration change is directly taken into use in the Active database in the BSC, so the Pre-activate operation is not possible with this method. When it is required, objects are locked and unlocked automatically. The user can control the impact on the traffic by defining handover time limits.
Q3-based plan activation method is not available for BSC S14 release. For BSC S14 release plan provisioning only the file-based method (assisted by Send To Network) can be used.
7.5.3
Flexi EDGE BTS site configuration plan activation and pre-activa-
tion
Flexi EDGE BTS site configuration plan can be activated in the BTS directly, or the plan file can be first transferred to BSC by a pre-activation operation and the plan can be taken into use in a separate activation operation.
The File Based Provisioning feature is used for Flexi EDGE BTS site configuration plan activation, and the file is transferred via Q3 to BSC. From BSC to BTS, the file is trans- ferred via the OMUSIG link.
The BTS site configuration is validated as part of the activation operation. The validation operation can also be run as a separate operation before activating the plan.
The following rules must be considered when activation BTS site configuration:
In site creation cases, the BCF in BSC RNW configuration must be created before the BTS SC is activated. The same rule is applicable in site creation with and without autoconnection. For more information on the procedure, see Creating BTS sites.
In maintenance cases, the BTS site configuration is activated before the related BSC RNW data is modified. This is the default order when the BSC RNW and BTS SC data is activated in the same plan. Examples of this kind of modification are GSM BTS site rehosting and Migration to Packet Abis. For more information, see Rehost-
ing GSM BTS sites and <relevant document>
7.5.4
AXC and FTM plan activation and pre-activation
AXC and FTM plans can be activated in the network directly, or the plan file can be first transferred to the network by a pre-activation operation and the planned values can be taken into use in a separate activation operation.
7.5.5
I-HSPA WBTS and IADA plan activation and pre-activation
I-HSPA plans can be activated in the network directly, or the plan file can be first trans- ferred to the network by a pre-activation operation and the planned values can be taken into use in a separate activation operation.
7.5.6
eNB plan activation and pre-activation
eNB plans can be activated in the network directly, or the plan file can be first transferred to the network by a pre-activation operation and the planned values can be taken into use in a separate activation operation. The eNB configuration is validated as part of the activation operation. The validation operation can also be run as a separate operation.
g
"Locking" plan is generated automatically when activating "user plan" from Provi- sioning dialog or command line. "User plan" is checked, and temporary "locking" plan is generated for LNCELs when parameter modification requires object locking or BTS restart. LNCEL is not added to "locking plan" when it is already locked or it is not selected to the provisioning scope. "Locking plan" is Pre-activated and Acti- vated automatically before "user plan" is pre-activated and activated. Unlocking is appended to "user plan" and then eNB does the unlocking automatically after mod- ification. Automatic locking is not done for FTM parameter modifications.g
Note that when plan contains changes to parameters that require cell locking or BTS restart, then activate pre-activated plan is not possible, because required cells are automatically locked by downloading and activating first temporary locking plan and then downloading and activating the original plan.7.5.8
MSC and MGW plan activation
MSC and MGW does not support separate pre-activation operation but the changes are always activated directly in the network.
7.5.9
SGSN plan activation
SGSN does not support separate pre-activation operation but the changes are always activated directly in the network.
7.5.10
Non-network parameters and objects
Non-network parameters are saved into the actual configuration at the same time when the plan is activated in the network. A plan with only non-network parameters must be provisioned for updating the actual configuration.