ZXWR RNC
Radio Network Controller
Configuration Management Description
Version: V3.14.10.12
ZTE CORPORATION
No. 55, Hi-tech Road South, ShenZhen, P.R.China Postcode: 518057
Tel: +86-755-26771900 Fax: +86-755-26770801 URL: http://support.zte.com.cn E-mail: [email protected]
Copyright © 2016 ZTE CORPORATION.
The contents of this document are protected by copyright laws and international treaties. Any reproduction or distribution of this document or any portion of this document, in any form by any means, without the prior written consent of ZTE CORPORATION is prohibited. Additionally, the contents of this document are protected by contractual confidentiality obligations.
All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE CORPORATION or of their respective owners.
This document is provided “as is”, and all express, implied, or statutory warranties, representations or conditions are disclaimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose, title or non-infringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the use of or reliance on the information contained herein.
ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications covering the subject matter of this document. Except as expressly provided in any written license between ZTE CORPORATION and its licensee, the user of this document shall not acquire any license to the subject matter herein.
ZTE CORPORATION reserves the right to upgrade or make technical change to this product without further notice. Users may visit the ZTE technical support website http://support.zte.com.cn to inquire for related information. The ultimate right to interpret this product resides in ZTE CORPORATION.
Revision History
Revision No. Revision Date Revision Reason
R1.0 2015–03–30 First edition
Serial Number: SJ-20141209142725-027 Publishing Date: 2015–03–30 (R1.0)
Contents
About This Manual ... I
Chapter 1 Configuration Management Overview ... 1-1
1.1 Terms ... 1-1 1.2 Configuration Management Functions... 1-2 1.3 Configuration Data Composition ... 1-4
Chapter 2 Integrated Configuration Management ... 2-1
2.1 Planning Data Import and Export... 2-1 2.2 Optimization Data Import and Export ... 2-2 2.3 Site Migration and Cutover... 2-4
Chapter 3 Single-Point Configuration Management ... 3-1
3.1 Configuration Data Stream... 3-1 3.1.1 Full Table Synchronization ... 3-2 3.1.2 Incremental Synchronization Mechanism ... 3-3 3.1.3 Configuration Rollback Mechanism... 3-5 3.2 Quick Configuration Import and Export ... 3-5 3.3 Data Backup and Recovery... 3-6
Chapter 4 Data Configuration Scenarios ... 4-1
Glossary ... I
About This Manual
Purpose
This manual describes the configuration management implementation principle and main functions of the network management system of the ZXWR RNC.
Intended Audience
l Network planning engineers l Data configuration engineers l Network optimization engineers
What Is in This Manual
Chapter 1, Configuration Management Overview
Describes basic concepts and functions of configuration management and the composition of configuration data of the ZXWR RNC. Chapter 2, Integrated
Configuration Management
Describes the function implementation of theICMsystem.
Chapter 3, Single-Point Configuration Management
Describes the function implementation of the single-point configuration management system.
Chapter 4, Data Configuration Scenarios
Chapter 1
Configuration Management
Overview
The configuration management system includes single-point configuration management and ICM, and implements data configuration for one or multiple controller NE devices.
Table of Contents
Terms ...1-1 Configuration Management Functions ...1-2 Configuration Data Composition ...1-4
1.1 Terms
Current Network Area
There is a current network area on the ICM. Configuration data for network operation is saved in this area. When an NE initially accesses the EMS, the ICM proactively synchronizes data to obtain the latest configuration data of the NE and save the data to the ICM database. Data consistency is implemented through southbound data updates and automatic reporting. Manual or timed full data synchronization is also supported. Data in the current network area comes from configuration data for NE operation, and cannot be manually modified by users.
Planning Area
A planning area is a backup of configuration data for some subnetworks or NEs at a specific moment. A user can edit configuration data in a planning area. When a user edits configuration data, current network operation data is not affected, and thus risks are reduced. Users can create multiple planning areas. They can edit configuration data in their own planning areas. The ICM only delivers users’ incremental data to the network to put it into effect. Users can edit data for different NEs in multiple planning areas at the same time.
Modification Area
In the OMM system, the modification area is used to store configuration data. Users can edit configuration data offline in the modification area, and then submit the data for synchronization with NE devices.
Snapshot Area
In the OMM system, the snapshot area is a copy of NE data. Users can view but cannot edit configuration data in the snapshot area. When data synchronization between the modification area and NE devices is successful, the system automatically copies data in the modification area to the snapshot area to ensure that data in the snapshot area is always consistent with NE data.
Migration
Migration refers to the transition of a site from a BSC to another BSC when the software version of the site remains the same, and includes online migration of sites in the same EMS and offline migration of sites between EMSs.
Cutover
Cutover refers to the transition of a site from a BSC to another BSC when the software version of the site is changed to another version in another series.
Planning Template
A planning template is a data planning template in the Excel format provided by the configuration management system. It provides physical configurations, transmission configurations, and wireless configurations. It abstracts some frequently used and required data, and organizes the data format in accordance with user experience and habits. There is an OMM planning template and an ICM planning template.
Each sheet in a planning template is used to plan data for one or multiple objects in the
MO model. Most parameters in the planning template are parameters that require to be entered, or interconnection parameters. A planning template is used for commissioning data generation and data addition. Users can plan data in the template, but cannot change the format of the template.
Optimization Template
An optimization template is a full parameter template provided by the configuration management system. It includes all objects and attributes in the configuration model, namely all objects and attributes visible to users on configuration pages. Users rarely use the optimization templates to create or delete objects. They only use them to adjust parameter values.
1.2 Configuration Management Functions
Chapter 1 Configuration Management Overview
Figure 1-1 Configuration Management System Architecture
EMSconfiguration management provides northbound adaptation, includingNMSaccess, adaptive conversion between the NMS model and the EMS model, and a variety of northbound interfaces such as the DB interface, Corba interface, and various file interfaces. EMS configuration management also provides southbound adaptation, including NE access and adaptive conversion between the network management model and the NE model. It supports various types of controllers and base stations such as RNCs, BSCs, AGs, SDR base stations, and BTSs.
Based on different configuration modes, EMS configuration management is divided into
GUIconfiguration andMMLconfiguration. l GUI configuration
Configuration management through GUI access is supported. User-friendly configuration measures are provided, such as template import, quick configuration, guide, copy, paste, search, and filtering.
l MML configuration
The MML access mode is provided. MML terminals are supported. You can also telnet to the network management server and execute MML commands.
Based on configured NEs, EMS configuration management is divided into integrated configuration and single-point configuration.
l Integrated configuration
Integrated configuration supports simultaneous configuration of multiple NEs, including cross-NE configuration operations such as checking interconnection parameter consistency between a controller and a base station, checking adjacent cell mutual configuration, and site migration and cutover.
l Single-point configuration
Configuration management of a specified NE is supported, which includes viewing, creation, deletion, and modification of one MO, and import and export of planning templates. Single-point configuration supports GUI and MML modes.
1.3 Configuration Data Composition
Configuration data is divided into wireless configuration parameters and ground configuration parameters.
Ground Configuration Parameters
Ground configuration parameters include:l System equipment configuration parameters
System equipment configuration parameters refer to parameters that need to be configured for proper operation of physical devices that compose a controller. These parameters include:
à Configuration parameters for controller rack, subrack, and board resources
à Configuration parameters for externalinterfaces provided by boards, such as the E1, T1, optical, and Ethernet interfaces.
à Configuration parameters for other processing modules on boards, such asDSP
processing chips
l System transmission network configuration parameters
System transmission network configuration parameters refer to parameters that need to be configured for providing all controller transmission network functions. These parameters include:
à ATM transmission network configuration parameters such as PVC, Nni, Uni, AAL2, andIMAconfiguration parameters
à IPtransmission network configuration parameters such as IP interface, IP routing, IP network security, and IP OAM configuration parameters
à SS7 signaling configuration parameters such as MTP2, MTP3, and M3UA
protocol configuration parameters
Chapter 1 Configuration Management Overview
l Controller system function parameters
Based on the types of interfaces provided by controllers in the communication system, configuration parameters for 3G controller system functions include configuration parameters for the Iu, Iur, Iub, Iur-g, IuBC, and IuPC interfaces.
Wireless Configuration Parameters
3G wireless configuration parameters include wireless global resource control parameters, configurations of all NodeBs under an RNC, configurations of all cells under an RNC, information about neighbor cells of the cells under an RNC, interconnection parameters, and other functional parameters.
To enable an RNC to provide services and functions, configuring these wireless parameters is a required procedure. By modifying wireless parameters, you can make each RNC adaptable to different traffic models and user requirements.
3G wireless configuration parameters include:
l Wireless global resource control parameters: RNC-related 3GPP parameters such as the global functional switches, QoS-related parameters, timer parameters, and positioning parameters.
l NodeB resource control parameters: site-level control parameters such as configurations of NodeBs under an RNC.
l Cell-level control parameters: configurations of all NodeBs under an RNC, including handover control parameters, power control parameters, wireless channel resource allocation control parameters and cell-level functional switches.
l Neighbor cell configuration parameters: information about neighbor cells of the cells under an RNC.
l Interconnection parameters: parameters that need to be consistent between adjacent NEs, for example, those that need to be consistent between the CN and the RNC. l Other parameters: include positioning parameters and counter control parameters.
Chapter 2
Integrated Configuration
Management
The EMS supports integrated configuration management of multiple NE devices. Integrated configuration management provides planning data import and export, optimization data import and export, site migration, interconnection data comparison, and neighbor cell mutual configuration functions. This chapter describes the implementation principles of planning data import and export, optimization data import and export, and site migration and cutover functions.
Table of Contents
Planning Data Import and Export...2-1 Optimization Data Import and Export ...2-2 Site Migration and Cutover ...2-4
2.1 Planning Data Import and Export
ICM supports importing planning template data to planning areas or exporting planning template data files for user editing in MML or GUI mode. After planning data is imported, the system executes data confliction and validity checks, and then performs download and activation operations. ICM supports creating activation tasks and performing download and activation operations in MML or GUI mode. Download refers to delivering data in planning areas to the OMM modification area to put the data into effect. Activation means synchronizing data in the OMM modification area with NE devices. Figure 2-1shows the operation processes.
Figure 2-1 Planning Data Import and Export Processes
2.2 Optimization Data Import and Export
Optimization Data Import
ICM supports importing optimization template data to planning areas in MML or GUI mode or putting it into effect in the OMM system in MML or GUI mode.
l Figure 2-2 shows the process of importing optimization template data to a planning area.
Chapter 2 Integrated Configuration Management
Figure 2-2 Process of Importing Optimization Template Data to a Planning Area
In this operation mode, imported data goes through a validity check before being delivered to the next level. Imported data does not affect NE agent servers before being downloaded, and does not affect network operation data before being activated. Therefore, data is more secure and the efficiency of batch data modification is higher. l Figure 2-3shows the process of importing optimization template data to the current
network area.
Figure 2-3 Process of Importing Optimization Template Data to the Current Network Area
In this operation mode, imported data is parsed into an MML script and delivered to NEs to put it into effect. Data validity is checked when the data is delivered to NEs. If the amount of changed data is large, the execution efficiency is low.
Optimization Data Export
In optimization template data export, the data source may be the current network area or a planning area. Optimization template data export supports MML and GUI modes, and Excel, CSV, and custom file formats. Figure 2-4shows the optimization data export process.
Figure 2-4 Optimization Data Export Process
2.3 Site Migration and Cutover
In network O&M, site migration and cutover belong to the same scenario such as capacity expansion, cross-version controller replacement, and network plan adjustment. The difference between site migration and cutover is that site migration can migrate transmission data and wireless data (including neighbor cell data) together, but site cutover only migrates wireless data (including neighbor cell data). In most cases, configuration data (especially network planning and optimization parameters) is required to be inherited after migration and cutover, and performance indexes should not be lowered after migration and cutover.
The following site migration and cutover functions are provided on the ICM page: l Online site migration tool, which is used for site migration within the same EMS l Offline site migration tool, which is used for site migration between EMSs
l Independent site cutover tool, which is used for site cutover between different version series
Chapter 2 Integrated Configuration Management
Figure 2-5 Site Migration Flow
Figure 2-6 Site Cutover Flow
Original network management files, new network management files, and planning data files are all input files of the cutover tool.
l Original network management files refer to all ground and wireless data files under the controller, which are exported from the network management system corresponding to the cutover source site.
l New network management files refer to all ground and wireless data files under the controller, which are exported from the network management system corresponding to the cutover destination site.
l Planning data files refer to parameter files for cutover source and destination sites and files of parameters that should be adjusted in the cutover procedure, which should be filled out by engineering personnel.
The main function of the cutover tool is to convert original network management data files into interface data files in accordance with planning data files. The cutover tool is divided into three modules, see Figure 2-7.
Chapter 2 Integrated Configuration Management
Figure 2-7 Processing Modules of the Cutover Tool
l Parse module
Parses network management data files and planning files. l Check module
Checks services for planning files. l Conversion module
Chapter 3
Single-Point Configuration
Management
Single-point configuration management refers to configuration management of one NE device. It is implemented by the network management systemOMM. The OMM server operates on an OMM board. The EMS can be connected to the OMM server in remote ERT mode or through an independently installed OMM client.
Single-point configuration management provides configuration data for upper-layer network management systems including the EMS and OSS, accepts data change requests from the EMS and OSS, and changes current network configurations. In addition, it provides data query interfaces for other systems including performance and alarm systems.
Table of Contents
Configuration Data Stream ...3-1 Quick Configuration Import and Export ...3-5 Data Backup and Recovery ...3-6
3.1 Configuration Data Stream
In the OMM system, all configuration data is stored in databases, including the modification area and snapshot area. The modification area is used by users to edit data. The snapshot area is a copy of NE data, and is always the same as NE data. All configurations used by performance, alarm, diagnostic testing, and status management modules come from the snapshot area.
A user edits data in the modification area, and then synchronizes data with NE devices. After NE devices load data, they process services based on the new data. After data in the modification area is successfully synchronized with NEs, the data is automatically copied to the snapshot area to ensure that data in the snapshot area is the same as NE data. Configuration data synchronization is divided into full table synchronization and incremental synchronization. Full table synchronization refers to synchronizing all data of all configuration objects with NE devices. Incremental synchronization refers to synchronizing data modified after the last full table synchronization with NE devices. The following describes full table synchronization and incremental synchronization mechanisms.
3.1.1 Full Table Synchronization
Full table synchronization needs to be executed in initial commissioning and upgrades of the equipment and batch configuration modification. In the configuration view, users edit data in the modification area, and then initiate full table synchronization. The system performs global validity and license checks based on configurations. After the checks are passed, users can initiate full table synchronization with NE devices.
Figure 3-1shows interactions between network management and NE device modules in the full table synchronization procedure.
Figure 3-1 Interaction Between Modules in Full Table Synchronization
Module meanings are as follows:
l WSF refers to the client module of the OMM system. It implements client operation functions and interactions with the server.
l OSF refers to the O&M function module at the server end of the OMM system. It implements configuration validity check and database import functions.
l EMF refers to the NE media module at the server end of the OMM system. It implements communication and message interactions between the OMM system and NEs.
Chapter 3 Single-Point Configuration Management
All OMM system configurations are stored in databases. Configurations are transferred between the OMM system and NEs in file mode. Figure 3-2shows the configuration data stream directions in the full table synchronization procedure.
Figure 3-2 Configuration Data Streams
Flow No. Meaning
1 A user edits data, and initiates a synchronization operation. 2 Synchronization data is written into the database.
3 A full table synchronization message is initiated.
4 The full table synchronization message is sent to MO adaptation. 5 MO adaptation reads data from the database.
6 A ZDB file is returned.
7 The ZDB file is transferred to NEs through FTP. Synchronization messages are sent.
8 A synchronization response message is returned. 9 The synchronization response message is returned. A synchronization operation results are returned.
B Latest data is read.
C Data is updated.
3.1.2 Incremental Synchronization Mechanism
In the routine system O&M procedure, users modify only a small part of configurations. To save time on synchronization operations, users can only perform incremental synchronization, which means only synchronizing modified configuration data with NEs. The system supports table-level incremental synchronization instead of record-level
synchronization. If a user modifies only an attribute of an object instance, all instances (all MO records) of the object are synchronized with NE devices in incremental synchronization.
When a user edits data in the modification area, the OMM system records the objects modified by the user in an incremental table (the modification of the userlabel attribute is not recorded in the incremental table.) When the user initiates incremental synchronization, the MO adaptation module generates an incremental ZDB file in accordance with only records in the incremental table. The OMM system synchronizes the incremental ZDB file with NE devices.
Figure 3-3 shows the interactions between the OMM system and NE device modules in an incremental synchronization procedure.
Figure 3-3 Module Interactions in Incremental Synchronization
In the incremental synchronization procedure, directions of configuration data streams are similar to those in full table synchronization, seeFigure 3-1. The difference is that the MO adaptation module generates a full ZDB file in full table synchronization, but it generates an incremental ZDB file in incremental synchronization.
Chapter 3 Single-Point Configuration Management
3.1.3 Configuration Rollback Mechanism
The OMM system supports configuration rollback, which means that data can be restored to the status before the latest synchronization operation. After each time data synchronization (including full table synchronization and incremental synchronization) is successful, the OMM automatically backs up configurations, including ZDB files in the NE format and ZTD files in the OMM format. When a user needs data rollback, the user can select the data synchronized most recently or data synchronized several times ago. Data rollback to different rollback points is supported. Each management NE stores five backup files at most. If it is detected that there are more than five backup files, the oldest backup file is deleted.
3.2 Quick Configuration Import and Export
The quick configuration import and export function is applicable to scenarios where configurations are quickly operated in batches on the OMM, such as batch site commissioning and neighbor cell planning. You can fill in a planning template in Excel format provided by the system with planning data, and then import the template to the configuration management system to complete batch data creation, deletion and modification operations. You can also export configurations from the current system, modify the exported Excel file, and then import the file into the system to complete data configuration or optimization.
Figure 3-4shows the principle of quick configuration import and export.
3.3 Data Backup and Recovery
Configuration data backup and recovery can quickly back up and recover the same NEs, and can ensure data security and improve system robustness in routine maintenance and system upgrades.
The unit of backup is an NE. Backup content is sql statements. Recovery uses sql batch processing mode.
The system supports manual and automatic backup, and provides a default backup path. You can also specify a backup file path.
Figure 3-5shows the principle of data backup and recovery.
Chapter 4
Data Configuration Scenarios
Commissioning and Capacity Expansion
Commissioning and capacity expansion are executed in single-point configuration management. The operation steps are as follows:
1. Fill in a quick configuration template file. 2. Import the quick configuration template file.
3. Transfer configurations to the RNC to implement configuration synchronization.
Optimization and Migration
Optimization and migration are modifications based on current configurations. Optimization operation steps are as follows:
1. Create a planning area based on the current network data area. 2. Export an optimization table from the planning area.
3. Import the optimization table to the planning area.
4. Perform a data confliction check, verification, and submission in the planning area. 5. In planning data activation management, create a script, download the script, and
activate data.
Migration operation steps are as follows:
1. Create a planning area containing source and destination NE data based on the current network data area.
2. Fill in a site migration template file.
3. After importing the site migration template file to the planning area, execute the site migration function, and adjust cell and neighbor cell data for source and destination NEs.
4. Perform a data confliction check, verification, and submission in the planning area. 5. In planning data activation management, create a script, download the script, and
Glossary
ATM
- Asynchronous Transfer Mode DSP
- Digital Signal Processor EMS
- Element Management System GUI
- Graphical User Interface ICM
- Integrated Configuration Management IMA
- Inverse Multiplexing over ATM IP
- Internet Protocol M3UA
- MTP3-User Adaptation layer protocol MML
- Man Machine Language MO
- Managed Object MTP2
- Message Transfer Part layer 2 MTP3
- Message Transfer Part layer 3 NMS
- Network Management System OMM
- Operation & Maintenance Module PVC