WRAN CME V100R008 Feature Description

Document code
WRAN CME V100R008 Feature

Description
Issue V1.0
Date 2023-05-25
Huawei Technologies Co.,Ltd.

Copyright © Huawei Technologies Co., Ltd. 2009. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without
prior written consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions

and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd. All other
trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The purchased products, services and features are stipulated by the commercial contract made
between Huawei and the customer. All or partial products, services and features described in this
document may not be within the purchased scope or the usage scope. Unless otherwise agreed by
the contract, all statements, information, and recommendations in this document are provided “AS
IS” without warranties, guarantees or representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in
the preparation of this document to ensure accuracy of the contents, but all statements,
information, and recommendations in this document do not constitute the warranty of any kind,
express or implied.
Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: http://www.huawei.com
Email: support@huawei.com
CME V1R8 Feature Description
Contents
1 Basic Features.................................................................................................................................6
1.1 Platform Functions.............................................................................................................................................6
1.1.1 WOFD- 181500 Management of the Current Area and Planned Area.....................................................6
1.1.2 WOFD- 181600 Data Browsing and Searching.......................................................................................7
1.1.3 WOFD- 181700 Script Executor..............................................................................................................9
1.1.4 WOFD- 181800 Dump Feature of the Planned Data Area.....................................................................10
1.1.5 WOFD- 181900 Upgrade of History Planned Data Areas.....................................................................11
1.1.6 WOFD- 182000 Hardware Monitoring..................................................................................................12
1.1.7 WOFD- 182100 Automatic Upgrade of the CME Client.......................................................................13
1.1.8 WOFD- 182200 Supporting the Windows Vista Operating System......................................................14
1.2 Device Management........................................................................................................................................15
1.2.1 WOFD- 182300 Device Data Configuration..........................................................................................15
1.2.2 WOFD- 182400 Device Panel................................................................................................................15
1.2.3 WOFD- 182500 Automatic Discovery of RNCs and NodeBs...............................................................16
1.2.4 WOFD- 182600 RNC Pool Management...............................................................................................18
1.2.5 WOFD- 182700 RNC MOCN Management..........................................................................................19
1.3 Configuration of Transmission Parameters.....................................................................................................21
1.3.1 WOFD- 182800 Basic Configuration of Transmission Data.................................................................21
1.3.2 WOFD- 182900 Batch Configuration of the Objects Related to Transmission Properties....................22
1.3.3 WOFD- 183000 Import and Export of the Interface Negotiation Data..................................................22
1.3.4 WOFD- 183100 NodeB Configuration Template..................................................................................23
1.4 Radio Parameter Configuration.......................................................................................................................25
1.4.1 WOFD- 183200 Basic Configuration of Cells.......................................................................................25
1.4.2 WOFD- 183300 Configuration of Neighboring Cell Relations.............................................................25
1.4.3 WOFD- 183400 Wizard for Adjusting Radio Neighboring Relations...................................................26
1.4.4 WOFD- 183500 Import and Export of the Radio Network Planning Data............................................27
1.4.5 WOFD- 183600 Batch Configuration of Radio Parameters...................................................................28
1.4.6 WOFD- 183700 Wizard for Batch Configuration of Radio Parameters................................................28
1.5 Others...............................................................................................................................................................30
1.5.1 WOFD- 187000 Data Integrity Check in a Single RNC........................................................................30
2 Optional Features........................................................................................................................31
2.1 Optional Features.............................................................................................................................................31
Issue V1.0 (2009-03-20) Huawei Technologies Proprietary Page 3 of 53

2.1.1 WOFD- 183800 NodeB Topology Browsing.........................................................................................31

2.1.2 WOFD- 183900 NodeB Configuration Express.....................................................................................32
2.1.3 WOFD- 184000 Wizard for Configuring the Iub Transmission Data....................................................33
2.1.4 WOFD- 184100 Cell Configuration Template.......................................................................................34
2.1.5 WOFD- 184200 Wizard for Adjusting Cell Frequency Points...............................................................35
2.1.6 WOFD- 184300 Comparison of Radio Parameters................................................................................36
2.1.7 WOFD- 184400 Import and Export of the Radio Network Planning Data............................................37
2.1.8 WOFD- 184500 Interface for Exporting Radio and Transmission Parameter Files..............................39
2.1.9 WOFD- 184600 Interface for Importing Radio Parameters and Configuration Files of Neighboring
Cells.................................................................................................................................................................41
2.1.10 WOFD- 184700 Interface for Importing NodeB Configuration Data..................................................44
2.1.11 WOFD- 180400 NodeB Reparenting...................................................................................................45
2.1.12 WOFD- 180500 Consistency Check for Global Data..........................................................................46
2.1.13 WOFD- 510300 Integration Solution of Citrix-based CME Client.....................................................51
3 Acronyms and Abbreviations.....................................................................................................53

Figures
Figure 1-1 Batch reconfiguration of parameters...................................................................................................29
Figure 2-1 Northbound database interface............................................................................................................38
Figure 2-2 Northbound interface for exporting data.............................................................................................40
Figure 2-3 Northbound interface for importing data............................................................................................43
Figure 2-4 Customizing check items....................................................................................................................48
Figure 2-5 RAN AutoFix window........................................................................................................................49
Figure 2-6 RAN Consistency Check window.......................................................................................................50

1 Basic Features
1 WOFD – 181000 Basic Features
1.1 Platform Functions

1.1.1 WOFD- 181500 Management of the Current Area and
Planned Area
Availability
This feature is available in the WRAN CME V100R003 and later versions. WRAN is short
for WCDMA Radio Access Network and CME is short for Configuration Management
Express. Hereinafter, the WRAN CME is referred to as the CME.
Summary
The CME allows users to manage the current data area and planned data area. Users can plan
data in individual planned data area that are independent of each other.
1. Current data area: The current data area works as mirroring of the configuration data on
the existing network. A Radio Access Network (RAN) system has only one current data
area. The data in the current data area can be automatically synchronized with the data on
the existing network.
2. Planned data area: The planned data area contains the data related to a certain Radio
Network System (RNS). Users can create individual planned data areas that are
independent of each other and plan data in the planned data area.
After configuring data in planned data areas, users can export the data into scripts and deliver
the scripts to NEs. Then, the data takes effect on the NEs.
Benefits
By using the current data area, users can easily obtain the latest configuration data of the
existing network.
By using the planned data area, users can plan data offline on a local computer without
affecting the existing network.

Description
When the CME is integrated into the M2000, it provides a current data area and multiple
planned data areas. The multi-area management improves data configuration efficiency and
enables several users to configure the same NE at the same time.
The process of RAN optimization is complicated. Users need to analyze network performance
counters and optimization policies and solutions. The entire process is experimental. Through
the multi-area management, the CME assigns the data of the existing network and the user-
configured data to different workplaces, that is, current data area and planned data areas. The
CME allows users to concurrently configure data in respective planned data areas. If the data
configured by a user is not activated, the data on the existing network and the data configured
by other users are not affected.
Current data area:
The current data area records the RAN configuration data on the existing network. It works as
mirroring of the data on the existing network. A RAN system has only one current data area.
The CME can automatically synchronize the data in the current data area with the data on the
existing network. Users can also synchronize the data manually.
Planned data area:
The planned data area contains the data that is copied based on a certain RNS. Users can plan
data in the planned data area and create individual planned data areas that are independent of
each other. After configuring data in planned data areas, users can export the data into scripts
and deliver the scripts to NEs. Then, the data takes effect on the NEs.
Enhancement
None.
Dependency
None.
1.1.2 WOFD- 181600 Data Browsing and Searching

Availability
This feature is available in the CME V100R003 and later versions.
Summary
Before planning new data, users can browse the RAN data on the CME to learn about the data
configuration on the existing network. In this way, users can compare the new data with the
previous data during the planning, thus avoiding data conflict.
After the data is configured and takes effect, users can check whether the added or modified
data takes effect and whether it is consistent with the planned data by using the RAN data
browsing function provided by the CME.
Benefits
By using the data browsing and searching functions, users can easily browse data.

Description
The network has a large amount of data. Good browsing and searching functions help users
effectively locate the required information and prepare for the planning and adjustment. The
CME supports panorama browsing and searching of data. Users can browse the configuration
data of various objects such as NodeB status, cell status, information about the Iub interface in
different transmission modes, neighboring cells, and neighboring cell relations between cells.
Users can also search for data objects meeting preset conditions through customized searching
conditions.
Browsing of RAN data
The data browsing function enables users to browse the data of a single RNS or a RAN
consisting of multiple RNSs. The CME allows users to view the following data:
 Iub Interface data on the RNC side: The CME allows users to view the information and
configuration status of the Iub interface data on the RNC side.
 Status data on the RNC side: The CME allows users to view the statistical data related to
the NodeBs, cells, and neighboring cell relations on the RNC side.
 Iub interface interconnection data: The CME allows users to view the interconnection
data of the ATM physical port in the Iub interface on the RNC side.
This function also has the following sub-functions:
 Filtering data: The system filters the data that meets the preset filtering conditions .
 Rearranging fields: User can customize the sequence of displaying fields to view the key
information.
 Locating data: The system automatically displays the record that meets the preset
locating conditions.
 Saving data to a file: The system can save the displayed data to a file in .csv format.
Searching of RAN data
The searching objects are NodeBs and cells. Users can search for NodeBs and cells under a
single RNS or multiple RNSs.
The searching modes are as follows:
 Basic searching: used in the case of only one condition.
 Advanced searching: used in the case of multiple searching conditions. Users can
combine multiple searching conditions as required.
The information displayed after the searching is as follows:
 Name and ID of the NodeB, RNC that the NodeB belongs to, and operation and
maintenance IP address of the NodeB
 Cell ID, local cell ID, RNC that the cell belongs to, cell name, and scrambling code
Enhancement
None.
Dependency
None.

1.1.3 WOFD- 181700 Script Executor

Availability
Summary
The CME script executor provides the functions of creating, managing, and monitoring a
project through the friendly GUIs. Users can manage multiple configuration scripts of
different NEs by project on the CME, which avoids manual operations such as selecting NEs
and scripts and processing scripts.
Benefits
By using the script executor, users can easily deliver and activate scripts.
Description
The script executor provides the following functions:
 Creating a project: Multiple tasks can be created in one project, where each task
corresponds to one configuration script.
 Deleting a project: Users can delete the current project.
 Pre-activating a project: Users can pre-activate a project to check the correctness of the
reconfiguration file.
 Activating a project: Users can activate a project by activating all the configuration
scripts in this project.
 Canceling a project. Users can cancel the current project.
 Monitoring a project: Users can monitor the execution status of each configuration
script.
Enhancement
None.
Dependency
None.

1.1.4 WOFD- 181800 Dump Feature of the Planned Data Area

Availability
Summary
The CME supports the automatic backup If a planned data area is not used for a long time, it is
function for planned data areas. automatically backed up.
The CME supports the function of loading the If a planned data area is already backed up, its data is loaded
data of the planned data area that is backed again when the area is open.
up.
The CME supports the function of deleting If a planned data area is deleted, the backup files and the data
backup files of planned data areas. of this area are all cleared.
Benefits
By using the dump function, users can dump the data in the planned data area from the
database to compressed files, thus saving the disk space of the PC server. Compressed files
occupy only 1‰ to 1% space of the database.
Description
Backing up data automatically:
By using the automatic backup function, the CME can dump the data in a planned data area
that is idle for a long time from the database to compressed files, thus saving the disk space of
the PC server.
The standard for determining an idle planned data area and the time for an automatic dump
are set in the configuration file rather than on a GUI.
The PC server automatically backs up the planned data area that meets the preset conditions at
the specified dump time.
Loading data:
To use a planned data area that is idle for a long time, the PC server restores the backup files
to the database. Then, the planned data area is automatically opened.
Deleting backup files:
When a planned data area is deleted, its backup files are deleted.
When an RNS is deleted, the corresponding RNS backup files of the planned data area that is
backed up are deleted.
Enhancement
None.

Dependency
None.
1.1.5 WOFD- 181900 Upgrade of History Planned Data Areas

Availability
Summary
This feature enables the CME to open history planned data areas after the CME is upgraded.
For example, when the CME V100R008C00 is upgraded to the CME V100R008C00SPC000,
the planned data areas are upgraded accordingly from the V100R008C00 to the
V100R008C00SPC000.
Benefits
By using this new feature, users can use the planned data areas of an earlier version after an
upgrade.
Description
Browsing all the history planned data areas:
After the CME is upgraded, users can view the dumped planned data area of an earlier version
and the information about all the RNSs involved in this area.
Upgrading the planned data area:
After the CME is upgraded, the history planned data areas are upgraded to match the current
CME version so that users can process the history planned data areas.
Enhancement
None.
Dependency
Data in the history planned data areas is already backed up by the CME.
The installation path of the CME is not changed. If the installation path is changed, the data of
the history planned data areas must be already moved accordingly.
The CME provides the function of browsing history planned data areas.

1.1.6 WOFD- 182000 Hardware Monitoring

Availability
Summary
Supporting real-time browsing of PC This features enables users to browse the data related to the
hardware resource status CPU usage, memory, hard disk capacity, and available space
in real time.
Supporting alarms for PC hardware resources This feature enables the system to send alarm messages when
the hard disk usage exceeds a the threshold.
Supporting the alarm setting for PC hardware This feature enables users to use the parameter for the hard
resources disk usage as the parameter for the hard disk alarm and to set
the parameter.
Benefits
The PC server is responsible for providing service support for multiple clients and for storing
data.
By using the hardware monitoring function provided by the PC server, users can browse real-
time resource status of the server and be informed of the threshold-crossing situation by
alarms.
Description
PC Server Real-time browsing of PC hardware resources
The CME provides the real-time browsing function, which enables users to easily learn about
the resource usage of the PC server.
Performance monitoring: The CME provides an GUI to allow users to view the memory
usage, memory capacity, ratio of occupied memory, and ratio of occupied CPU of the PC
server. Thus, users can easily learn about the operation performance of the PC server.
Hard disk monitoring: The CME provides GUIs for the users to learn about the hard disk
capacity, and hard disk usage. Thus, users can easily learn about the usage of the storage
devices of the PC server.
Alarm setting for PC hardware resources
The CME provides the function of setting alarms related to the hard disks. By using this
function, users can adjust the alarm-specific threshold as required.
Users can set the period for checking hard disk status.
Users can set the parameter related to the hard disk usage. This parameter determines whether
an alarm is generated.

Users can set the offset of the hard disk usage. If the offset is set, the same alarm is not
repeatedly reported if the usage varies within the offset range.
Alarms for PC hardware resources
The CME provides the function of browsing alarms related to the hard disks.
When an alarm is generated, users can obtain the generation time and clearing time of the
alarm by browsing the M2000 alarm information window. In this way, users can learn about
the status of an alarm in a certain period of time.
Enhancement
None.
Dependency
Alarms of the PC hardware resources depend on the alarm management module of the
M2000. An alarm can be reported only when the M2000 allocates an alarm ID to the CME.
1.1.7 WOFD- 182100 Automatic Upgrade of the CME Client

Availability
Summary
1. Supports automatic upgrades of SP patches for the CME client.
2. Supports automatic upgrades of NodeB components for the CME client.
Benefits
In a version earlier than the CME V100R008, upgrades are manually performed. When a
NodeB component needs to be upgraded, the required patch package is sent to the customer,
and then the customer manually performs the upgrade. Manual upgrades become complicated
when the number of users increases. By providing this new feature, the CME V100R008
enables the customer to easily upgrade patches even when there are a great number of users.
Description
Automatic upgrades of SP patches for the CME client
The CME system consists of the following software: CMEClient, CMEServer, and
CMEAppService.
The CME AppService contains SP patches and it updates the codes and database scripts. After
the update is complete, the CME AppService proactively establishes an FTP connection with
the CMEServer. Then, it sends the patches to the CMEServer, which updates the CME version
information in the database accordingly.
When the CMEClient is started, it checks whether its current version is consistent with the
CMEAppService version. If the CMEClient version is inconsistent with the CMEAppService
version, the CMEClient is automatically upgraded to match the CMEAppService.
Automatic upgrades of NodeB components for the CME client

The CME system consists of the following software: CMEClient, CMEServer, and
CMEAppService.
NodeB components, namely, NodeB component codes and database scripts, are installed on
CMEAppService. After the NodeB components are installed, the CMEAppService proactively
establishes an FTP connection with the CMEServer and then sends the NodeB component
package to the CMEServer. When the CMEClient is started, it checks whether the
CMEAppService is installed with new NodeB components. If new NodeB components are
detected, the CMEClient is automatically upgraded with the new NodeB components.
Enhancement
None.
Dependency
None.
1.1.8 WOFD- 182200 Supporting the Windows Vista Operating

System
Availability
Summary
Supports the CME to operate on the Windows Vista operating system.
Benefits
This feature enables users to use the CME on the Windows Vista Operating system.
Description
1. The Windows Vista operating system supports the MSDE2000 and SQL Server2005
rather than the SQL Server2000.
2. Colors marking certain functions of the CME on the Windows Vista operating system
are different from the colors marking the same functions of the CME on the Windows
XP operating system. Users, however, can use the XP Style on the Windows Vista
operating system to solve this problem.
Enhancement
None.
Dependency
None.

1.2 Device Management

1.2.1 WOFD- 182300 Device Data Configuration
Availability
Summary
Through the GUIs of the CME, users can perform basic configuration for RNCs, macro
NodeBs, and distributed NodeBs. For example, users can add, delete, modify, or query the
resources such as cabinet, subrack, board, and physical ports.
Benefits
Users can use this feature on the NE side when the CME is integrated into the M2000
In addition, the GUIs of the CME are provided on the M2000, thus simplifying the
configuration management.
Description
None.
Enhancement
None.
Dependency
None.
1.2.2 WOFD- 182400 Device Panel

Availability
Summary
The CME displays the configuration of NodeBs on the Device Panel tab page. In addition,
users can configure NodeBs such as adding and deleting a board and modifying board
attributes on the Device Panel tab page.
Benefits
By using templates, users can configure NodeBs and view the entire configuration process on
the GUI.

Description
The CME displays the physical structure of the configured NodeB through the device panel.
The following figure shows a typical template for configuring NodeBs. By using the template,
users can configure NodeBs and view the entire configuration process on the GUI.
Enhancement
None.
Dependency
None.
1.2.3 WOFD- 182500 Automatic Discovery of RNCs and NodeBs

Availability

Summary
After RNCs and NodeBs are created on the M2000, the system automatically adds their
configuration data to the CME.
Benefits
When NE data is added or deleted, the system can automatically perform relevant operations
such as creating and synchronizing NEs. This avoids manual operations and ensures that the
CME data is consistent with the M2000.
Description
1. Currently, this feature is applicable to only 3G NEs, namely, RNCs and NodeBs.
2. Automatic discovery of NEs refers to the situation where the M2000 creates NEs and
synchronizes NE data successfully. The database and synchronization of the CME
depend on the M2000. Thus, data synchronization on the CME must be performed after
data on the M2000 is successfully synchronized.
3. In the case of an RNC, this feature supports the processing of NE creation on the M2000
rather than the processing of data changes of existing NEs. NE data changes are
processed by the AVC mechanism.
4. In the case of a NodeB, this feature supports the processing of both NE creation and data
change of existing NEs. In addition, the NodeB data on the CME is always consistent
with the NodeB data on the M2000.
5. The CME does not process the NEs whose data is changed and the NEs that are created
before the connection between the AppService and the CmeServer is established. If the
CME processes such NEs, the system takes a long time to create databases and
synchronize data, and these operations cannot be cancelled. To provide a good user
experience, the CME processes only NEs that are created and the NEs whose data is
changed after the connection between the AppService and the CmeServer is established.
6. When processing a newly discovered NodeB, the CME synchronizes data with the
corresponding RNC if the corresponding logical NodeB data is unavailable on the CME.
If the corresponding RNC is not created, the CME does not synchronize the NodeB.
7. When the M2000 discovers a new NodeB, users can manually synchronize the NodeB on
the CME client before the M2000 automatically performs the synchronization. If the
RNC does not have the corresponding logical NodeB at this time, this NodeB should be
marked to be separated from other NodeBs. When users synchronize this NodeB, the
RNC is synchronized accordingly.
8. If a NodeB is deleted on the M2000, the CME automatically deletes the corresponding
physical NodeB data from the system. If an RNC is deleted on the M2000, the CME
does not perform any processing.
9. In addition to the existing selection modes (namely, selecting all NEs and selecting a
specified NE), another selection mode (namely, selecting all the NEs under an RNS) is
provided for the CME upload task of the centralized task management on the M2000. In
either of the existing selection modes, the upload task is automatically modified when a
NodeB is added or deleted. In the mode of selecting a specified NE, the system does not
perform any processing when a NodeB is added or deleted. When an RNC is added or
deleted, the upload task is not processed.
10. Users are allowed to disable the automatic discovery function of all the NEs. In addition,
users are allowed to disable the real-time synchronization function of NodeBs. The real-
time synchronization function of the NodeB covers the automatic discovery function.

Thus, disabling the automatic discovery function of the NodeB does not mean that the
real-time synchronization function of the NodeB is disabled.
11. The creation and synchronization of an NE should be independent of the creation and
synchronization of the other NEs. The synchronization mode of an NE can be set to
Once or Period.
Enhancement
None.
Dependency
This feature depends on the CME upload task of the centralized task management on the
M2000. To support this feature, the M2000 must provide the mode of selecting all the NEs
under an RNS.
1.2.4 WOFD- 182600 RNC Pool Management

Availability
Summary
1. Supports the basic configuration of Pool parameters.
2. Supports the basic configuration of dual-homed NodeBs and their Iub interfaces. It does
not affect the enhancement function. In the case of using an existing enhancement
function, dual-homed NodeBs are operated as single-homed NodeBs. In the case of
reparenting, dual-homed NodeBs must be modified to single-homed NodeBs and then
are reparented.
3. Supports the basic configuration of dual-homed cells and their neighboring cell relations.
It does not affect the enhancement function. In the case of using an existing enhancement
function, dual-homed cells are operated as single-homed cells and neighboring cell
relations of the dual-homed cells are processed as the neighboring cell relations of
single-homed cells.
4. Supports the configuration of dual-homed cells and their neighboring cell relations on
two RNCs. The CME imports the planning data from the two RNCs by using the radio
negotiation plan (RNP) function and then creates the primary and secondary cells and
their neighboring cell relations.
Benefits
Users can use this feature on the NE side when the CME is integrated into the M2000.
The M2000 provides the configuration for dual-homed cells of their neighboring cell relations
on both sides, which simplifies the configuration management.
The M2000 provides the function of checking data consistency and refreshing the data of the
Pool, which ensures data consistency.

Description
1. Supports the basic configuration of Pool parameters and the function of configuring
RNCs as a Pool.
2. Supports the basic configuration of dual-homed NodeBs and their Iub interfaces. It does
not affect the enhancement function. For the existing enhancement function, dual-homed
NodeBs are operated as single-homed NodeB. In the case of reparenting, dual-homed
NodeBs are modified to single-homed NodeBs and then are reparented.
3. Supports the basic configuration of dual-homed cells and their neighboring cell relations.
It does not affect the enhancement function. For the existing enhancement function, dual-
homed cells are operated as single-homed cells and neighboring cell relations of the
dual-homed cells are processed as the neighboring cell relations of single-homed cells.
4. Supports the configuration of dual-homed cells and their neighboring cell relations on
two RNCs. The CME imports the planning data from the two RNCs by using the RNP
function and then creates the primary and secondary cells and their neighboring cell
relations.
Enhancement
None.
Dependency
1. Currently, one Pool can contain only two RNCs.
2. The physical NodeB identifies the RNC that it currently belongs to based on the
OwnerId. A NodeB has two copies of Iub interface data. One copy is for one RNC.
3. Though a NodeB can be controlled by two RNCs, it is available to either of the two
RNCs. The CME can synchronize the NodeB data of the two RNCs.
1.2.5 WOFD- 182700 RNC MOCN Management

Availability
Summary
1. Supports the multi-operator core network (MOCN) sharing configuration for RNCs.
2. Supports the configuration of four types of operators, that is, primary operator,
secondary operation, outer operator, and common operator.
3. Supports the configuration of operator groups.
4. Supports the MOCN sharing configuration for NodeBs.
5. Supports the parameter configuration of the shared cells of the MOCN, NRNC cells, and
GSM cells.
6. Supports the configuration of neighboring cell relations for the shared cells of the
MOCN.
7. Supports the configuration of neighboring cell relations based on the MOCN
neighboring cell relation adjustment wizard designed for the radio layer.
8. Supports the creation and configuration of NodeBs, cells, and neighboring cell relations
of the MOCN by importing data through the RNP.
9. Supports the NodeB reparenting of the MOCN.

10. Supports the function of checking the data consistency and refreshing data for the
MOCN and the operator groups.
Benefits
By providing enhanced configuration functions on the M2000, the CME can simplify the
By providing the function of checking data consistency and refreshing data of the MOCN on
the M2000, the CME can ensure data consistency.
Description
1. Supports the MOCN sharing configuration for RNCs.
2. Supports the configuration of four types of operators, that is, primary operator,
secondary operator, outer operator, and common operator.
3. Supports the configuration of operator groups.
4. Supports the MOCN sharing configuration for NodeBs.
5. Supports the parameter configuration of the shared cells of the MOCN, NRNC cells, and
GSM cells.
6. Supports the configuration of neighboring cell relations for the shared cells of the
MOCN.
7. Supports the configuration of neighboring cell relations based on the MOCN
neighboring cell relation adjustment wizard designed for the radio layer.
8. Supports the creation and configuration of NodeBs, cells, and neighboring cell relations
of the MOCN by importing data through the RNP.
9. Supports the NodeB reparenting of the MOCN.
10. Supports the function of checking the data consistency and refreshing data for the
MOCN and the operator groups.
The MOCN features are mainly realized at the radio layer. Generally, a significant number of
manual configuration operations are performed on the radio layer, which causes errors. This
new feature enables the CME to import the data of the NodeBs, RNC cells, GSM cells, and
neighboring cell relations that support the MOCN by using the RNP function and then
generates incremental MML commands. This feature also enables users to adjust the
neighboring cell relations of the MOCN by using the neighboring cell relation adjustment
wizard and then generates incremental MML commands. In addition, this feature enables
users to migrate data during the BTS reparenting and generates MML commands for the
reparenting. The CME supports the function of checking the data consistency of the MOCN.
If any data inconsistency is detected, the CME refreshes the inconsistent data and generates
MML commands.
Enhancement
None.

Dependency
1. The RNC needs to support the MOCN so that the MOCN radio layer configuration can
be imported through the RNP.
2. To configure the MOCN neighboring cell relations, the switchover function between
operators must be enables.
3. On the GUIs for adjusting the neighboring cell relations and configuring the basic
neighboring cell relations, the neighboring cell relations of the RNC Pool cannot be
configured.
1.3 Configuration of Transmission Parameters

1.3.1 WOFD- 182800 Basic Configuration of Transmission Data
Availability
Summary
The CME provides a GUI-based configuration policy for the data of all the supported
transmission interfaces. The CME allows users to configure the following interfaces:
 Iub interface
 Iur interface
 Iu-CS and Iu-PS interfaces
 Iu-BC interface
Benefits
Description
None.
Enhancement
None.
Dependency
None.

1.3.2 WOFD- 182900 Batch Configuration of the Objects Related

to Transmission Properties
Availability
Summary
The CME allows users to add, delete, and modify the configuration objects on the radio
transmission layer in batches. The configuration objects are as follows:
 Physical links such as IMA and UNI
 Objects on the transmission network layer, such as AAL2 and AAL5
Benefits
By providing batch configuration, the CME improves the configuration efficiency.
Description
This takes the SAAL link as an example. Users need to specify only a traffic index and a PVC
value. Then, the CME automatically calculates the configurable SAAL link of the current link
and adds the configurable SAAL link to the SAAL link pool as a candidate link. The
information about the required SAAL links, such as link numbers, send/receive traffic
indexes, and VPI/VCI, is automatically arranged in the link pool. The link pool cannot be
configured or modified. Users can create SAAL links in batches by selecting one or multiple
SAAL links.
Enhancement
None.
Dependency
None.
1.3.3 WOFD- 183000 Import and Export of the Interface

Negotiation Data
Availability
Summary
The CME allows users to import and export the Iub site survey and planning data through
an .xls template. This simplifies the configuration process of each interface. It adds the
collection of the interface configuration data obtained in the site preparation phase to the
negotiated data file. Then, the CME imports the data table into the RNS. The data generated

contains the configuration of the objects on the two sides of the interface. The interface
negotiation data that can be imported and exported is as follows:
 Iub interface negotiation data
 Iur interface negotiation data
 Iu-CS interface negotiation data
 Iu-PS interface negotiation data
Negotiated data files, which are in .xls format, are delivered with the CME. Users can fill in
the files with the negotiated and planned data and then import the files to the current project
on the CME. This is an auxiliary way of configuring data on the CME.
Note:
The Iub interface negotiation data can be only imported or exported for creating or modifying
the logical Iub interface.
Benefits
By providing the function of importing and exporting interface negotiation data, the CME
greatly improves the configuration efficiency.
Description
None.
Enhancement
None.
Dependency
None.
1.3.4 WOFD- 183100 NodeB Configuration Template

Availability
Summary
The CME provides a NodeB system template. The system template provides recommended
parameter settings for common application scenarios. Users can use the NodeB system
template to set the parameters at the radio level, such as the demodulation mode, Iub interface
data, and cell.
The CME allows users to customize a template. Users can store common configuration data
of NodeBs as a custom template. By customizing a NodeB template, users can minimize the
repetitive efforts for configuration. After a NodeB template is applied to site deployment,
users need to adjust only a small number of mandatory parameters.

Benefits
By providing a configuration template, the CME simplifies configuration operations.
In addition, the CME reduces the expenditure incurred on learning and ensures that
maintenance skills can be shared between operation and maintenance engineers.
Description
The amount of default configuration data and typical configuration data of NodeBs and cells
is large. If multiple NodeBs and cells exist on the network, the efficiency of manual
configuration is low. Thus, the CME provides the NodeB templates and cell algorithm
parameter templates to facilitate the configuration and improve the working efficiency.
Application scenarios
 When creating a NodeB, users can add NodeB data by importing the NodeB template
file, and then reconfigure the data according to the plan.
 If the data is frequently used, users can save the data as a custom template file to
facilitate future configuration. This allows users to manage template files in real time.
NodeB Template
A NodeB template file contains a set of recommended and typical data that is predefined
based on the common configuration types, demodulation modes, and Iub transmission modes.
The NodeB template contains the following types of data:
 Device layer data of NodeBs includes the data about the transmission board, main
control board, and radio frequency board
 NodeB transport layer data: includes the data required for the protocol stack in special
transport mode.
 NodeB radio layer data: includes the radio resources and the data about sites, sectors, and
local cells.
 The NodeB template files include the following:
 Template file provided by the CME software. It cannot be deleted or modified.
 Customized template file. After configuring the NodeB data, users can save the
configuration data as a template file, which can be used as an optional data source for
future configuration.
The NodeB system template file is delivered with the CME software. The file is available in
CME installation directory\WRANCMEV100R005\template\NodeB.
The NodeB template file is named as follows: transport protocol type_demodulation
mode_number of sectors_number of frequencies_transmit diversity mode.xml. For
example, ATM_2-Channels Demodulation_3_1_Transmitter Non_diversity.xml.
Enhancement
None.
Dependency
None.

1.4 Radio Parameter Configuration

1.4.1 WOFD- 183200 Basic Configuration of Cells
Availability
Summary
The CME enables users to configure the WCDMA cell data, which covers the following:
 UMTS cells, external UMTS cells, and GSM cells
 Common channel of a cell and dedicated channel of a cell
 Cell-oriented algorithm parameter
 RNC-oriented algorithm parameter
 Information about location areas, service areas, and routing areas
Benefits
Description
None.
Enhancement
None.
Dependency
None.
1.4.2 WOFD- 183300 Configuration of Neighboring Cell Relations

Availability
Summary
The CME provides various configuration solutions for the neighboring cell relations of cells.
It supports the configuration of intra-frequency neighboring cell relations, inter-frequency
neighboring cell relations, and inter-system neighboring cell relations. Users can complete the
configuration process on the GUI. As the relations and status of neighboring cells are
displayed on the GUI, users can view them directly.

Benefits
Description
None.
Enhancement
None.
Dependency
None.
1.4.3 WOFD- 183400 Wizard for Adjusting Radio Neighboring

Relations
Availability
Summary
The CME allows users to configure data during network optimization. Through a wizard, the
CME guides users to adjust the neighboring cell relations between intra-frequency cells, inter-
frequency cells, or inter-system cells. The CME also generates the relevant incremental MML
command.
Neighboring relations of the following cells can be modified:
 Intra-frequency neighboring cells
 Inter-frequency neighboring cells
 Neighboring GSM cells
The CME also allows users to adjust the relations of neighboring cells in batches.
Benefits
By providing a wizard, the CME simplifies the configuration operations and improves the
working efficiency.
Description
None.
Enhancement
None.

Dependency
None.
1.4.4 WOFD- 183500 Import and Export of the Radio Network

Planning Data
Availability
Summary
The CME allows users to import and export the radio network planning data through a
template. By collecting the template data, the CME can generate the radio network planning
data.
Benefits
By providing the function of importing and exporting interface negotiation data, the CME
greatly improves the configuration efficiency.
Description
The negotiation data file provides the definition of the file and describes the scenarios for
using the file, the method of obtaining the file, and the role of the file in the CME. The radio
network planning data file contains a collection of negotiated and planned data, such as cell
data, neighboring cell data, GSM cell data, and neighboring cell relations.
The negotiated data is filled in the preset template that is in .xls format. When using the CME
to perform RAN initial configuration or expansion, import data in the negotiation data file
into the CME to generate the CME configuration data. The file containing the radio network
planning data can be exported in .xls format. When the data in the file needs to be modified,
users can export the file.
Users can import a negotiation data file to the current RNS to simplify the initial
configuration. The radio network layer data obtained during the site preparation includes
NodeB data on the RNC side, cell data on the RNC side, neighboring cell data, neighboring
cell relationship data, and uplink and downlink delay in the NodeB antenna paths. After
specifying a file path, users must specify the data items to be imported. Users can specify a
template for the import of cell data. The CME allows users to export the incremental MML
command of the corresponding data if one of the following data is imported: GSMCell Data,
NRNCCell Data, NeighborCellRelation Data, and GSMCellRelation Data.
User can export the radio negotiation and planning data file for manually modification. After
specifying a file path, users must specify the data items to be exported. Then, the CME
exports the negotiation data file to the specified path.
Enhancement
None.

Dependency
None.
1.4.5 WOFD- 183600 Batch Configuration of Radio Parameters

Availability
Summary
The CME allows users to add, delete, or modify radio configuration objects in batch mode.
The radio configuration objects are as follows:
 Objects on the radio network layer, such as an NBAP dedicated object and an NBAP
common object
 District configuration objects such as LAC, RAC, SAC, and URA
 Cell configuration objects
 Neighboring relation configuration objects
Benefits
By providing batch configuration, the CME improves the configuration efficiency.
Description
None.
Enhancement
None.
Dependency
None.
1.4.6 WOFD- 183700 Wizard for Batch Configuration of Radio

Parameters
Availability
Summary
The CME supports network optimization scenarios. Through a wizard, the CME enables users
to reconfigure radio parameters of cells in batches. Through batch modification, the CME
generates the relevant increment MML commands.

Benefits
By providing batch reconfiguration, the CME improves the configuration efficiency.
Description
By providing a wizard, the CME supports the reconfiguration of the RRM algorithm
parameters such as CELLAMRC, CELLCAC, CELLCMCF, CELLDCCC, CELLDRD,
and CELLFRC. After users specify the objects to be reconfigured in batches, the CME lists
the cells in the resource pool. Then, users need to specify the associated cells. As a result, the
reconfiguration of the algorithm parameters takes effect at the same time in the specified cells.
This takes the batch reconfiguration of the CELLCAC parameter as an example.
Figure 1-1 Batch reconfiguration of parameters
After the Expected Value parameter is reconfigured, the new values take effect immediately
in the cells specified by users.
Enhancement
None.
Dependency
None.

1.5 Others
1.5.1 WOFD- 187000 Data Integrity Check in a Single RNC
Availability
Summary
The CME provides the Sanity Checking function. This function enables users to find the
unsanitary data in the global range, that is, in the data of multiple RNCs. The unsanitary data
is the data that is not intact, redundant, or improper.
Users can use this function to check data in an RNS.
Benefits
Users can check data consistency within a single RNC by using the consistency check
function provided by the CME.
Description
The intact data refers to the configured data that can take effect on devices after being
delivered. In addition, after the data takes effect, the devices can be started and work
normally.
After the data configuration is complete, users can check data redundancy on the CME. The
redundant data refers to the obsolete underlying data. The redundancy check helps clear
redundant data to reduce the load. It also helps ensure that obsolete data is deleted after data
modification .
By using the data consistency check function, users can perform the following operations:
 Check the data integrity of the Iub, Iur, Iu-PS, and Iu-CS interfaces within a single RNC.
 Check the unidirectional neighboring cells within a single RNC.
Enhancement
None.
Dependency
None.

2 Optional Features
2 WOFD – 181001 Optional Features
2.1 Optional Features

2.1.1 WOFD- 183800 NodeB Topology Browsing
Availability
Summary
1. Supports browsing the networking topology of ATM-based or IP-based NodeBs.
2. Supports adjusting hierarchical relations on the networking topology of NodeBs.
3. Supports generating MML commands during the adjustment of the NodeB networking
topology.
4. Supports creating NodeB topology data for the entire network at a time.
Benefits
Users can browse the cascading relations between NodeBs on the CME and save the
cascading relations permanently to the NE database. In addition, users can use the NodeB
topology browsing function to adjust the cascading relations between NodeBs according to
the planning.
Description
 Supports browsing the networking topology of ATM-based or IP-based NodeBs.
Regardless of the transport mode of a NodeB, the CME enables users to browse the cascading
relations between NodeBs if the data about the ADJNE configuration object exists in the
configuration data. The ADJNE configuration object describes the NE name of the parent
node. The CME displays the NodeB cascading relations by providing a navigation tree on the
left and a topology on the right. The navigation tree shows the parent relations between NEs.
The topology shows the following basic information about the existing NodeBs: NodeB ID,
NodeB name, NodeB serial number, and NodeB version number.
 Supports adjusting hierarchical relations on the networking topology of NodeBs.

Users can user the CME to adjust the cascading relations between any two NodeBs and
generate MML commands for adjusting the ADJNE configuration object. When the CME
works in standalone mode, MML commands are generated in a file for multiple NodeBs. Each
MML command is suffixed with the NE name. The MML commands can be delivered to
multiple NEs at a time through the M2000. When the CME works in integrated mode, MML
commands are generated in a file for one NodeB. In this case, the MML commands can be
delivered directly through the script executor of the CME.
 Supports generating MML commands during the adjustment of the NodeB networking
topology.
Users can user the CME to adjust the cascading relations between any two NodeBs and
generate MML commands for adjusting the ADJNE configuration object. When the CME
works in standalone mode, MML commands are generated in a file for multiple NodeBs. Each
MML command is suffixed with the NE name. The MML commands can be delivered to
multiple NEs at a time through the M2000. When the CME works in integrated mode, MML
commands are generated in a file for one NodeB. In this case, the MML commands can be
delivered directly through the script executor of the CME.
 Supports creating NodeB topology data for the entire network at a time.
The CME provides the .xls file. If data about the NodeB cascading relations are correctly
entered in the .xls file, the CME can generate MML commands related to the NodeB topology
information of the entire network at a time.
Enhancement
None.
Dependency
1. The NodeB must support the ADJNE configuration object.
2. Configuration of the ADJNE object must be performed in an .xls file or on the CME
topology browsing interface
2.1.2 WOFD- 183900 NodeB Configuration Express

Availability
Summary
The CME provides an interface to help users configure all the parameters of a NodeB. Based
on the display of the protocol stack, the CME guides users to configure the following objects:
 Physical carrier
 AAL2/AAL5 link
 NBAP/ALCAP/AAL2PATH/IPOA
Benefits
By integrating the NodeB configuration, the CME simplifies the configuration operations,
which reduces learning costs of customers and improves the working efficiency.

Description
Enhancement
None.
Dependency
None.
2.1.3 WOFD- 184000 Wizard for Configuring the Iub

Transmission Data
Availability
Summary
The CME supports configuring the Iub interface data by importing the Iub interface planned
data file. The Iub interface data includes the data about the transmission parameters on the
two sides (RNC and NodeB) of the Iub interface.
The negotiation data file, which is in .xls format, is delivered with the CME. After obtaining
the file, users can fill in the file according to the planned data and then import the file to the
system. By using the negotiation data file, users can quickly and accurately complete the
configuration of interface data.
Benefits
The CME supports integrated site deployment and Iub interface adjustment. It enables users
to configure the Iub data on both the RNC side and the NodeB side.
Description
Supports importing the planned data of the logical Iub interface for creating or modifying the
Iub interface of the logical NodeB in the following networking scenarios:
 ATM-based transmission networking
 IP-based transmission networking
 ATM/IP-based transmission networking
Supports importing the planned data of the physical Iub interface for creating or modifying
the Iub interface of the physical NodeB in the following networking scenarios:
 ATM-based transmission networking
 IP-based transmission networking
 ATM/IP-based transmission networking

Enhancement
The CME V100R005 enhances the function of importing the Iub interface data of the
NodeBs.
Dependency
None.
2.1.4 WOFD- 184100 Cell Configuration Template

Availability
Summary
The CME provides a preset template. It also allows users to customize a cell template. When
using a template to create a cell, the CME automatically configures the cell algorithm
parameters based on the template. After a cell is created for an RNC, users can save this cell
data as a template. This template can be shared by other RNCs that are of the same version
with the local RNC. In addition, the CME allows users to compare the parameters of the
custom cell with the parameters of the template cell.
Benefits
By providing a configuration template, the CME simplifies configuration operations.
In addition, the CME reduces the expenditure incurred on learning and ensures that
maintenance skills can be shared between operation and maintenance engineers.
Description
A cell template contains a collection of radio algorithm parameters preset by users. The
system automatically configures algorithm parameters according to the template.
The CME allows users to save the data of a created cell as a template. By using this template,
users can create another cell.
The hierarchies of cell templates are based on network planning, which are as follows:
 First level refers to the highest level of parameters, including AcPara (access-related
parameter), HoPara (handover-related parameter), and ChPara (channel-related
parameter).
 Second level refers to the subclasses of the first-level parameters. For example, AcPara
on the first level includes the cell common channels configuration parameter
CellCChCfg.
 Third level refers to the subclasses of the second-level parameters. For example,
CellCChCfg on the second level includes the following subclasses: CellPrachCfg (cell
PRACH configuration parameter), CellPrachTfc (TFC on the PRACH), and
CellPrachSlotFormat (timeslot format on the PRACH).

Enhancement
None.
Dependency
None
2.1.5 WOFD- 184200 Wizard for Adjusting Cell Frequency Points

Availability
Summary
The CME allows users to configure data during network optimization. Through a wizard, the
CME guides users to change the frequency points and scrambling codes of the local RNC or
NRNC. The CME also generates the relevant incremental MML commands.
Benefits
By providing a wizard, the CME simplifies the configuration operations and improves the
working efficiency.
In addition, by automatically handling complicated adjustment of neighboring cell relations,
the CME simplifies maintenance operations and ensures adjustment accuracy.
Description
The following table describes the negotiated and planned data involved in the change of the cell frequency points and scrambling codes.
Frequency Band
Uplink frequency The frequency value varies according to the band

indicator.
Downlink frequency For value ranges of the uplink frequency and downlink
frequency, refer to the CME parameter reference.
Primary DL scrambling code
The system lists the cells under the current RNC and provides the information about the
neighboring cells. If the frequency of a cell is modified, the CME automatically refreshes the
neighboring cell relations of the cell.
Enhancement
None.

Dependency
None.
2.1.6 WOFD- 184300 Comparison of Radio Parameters

Availability
Summary
This feature enables users to compare the values of global algorithm parameters or cell
algorithm parameters with the baseline values. The CME displays the parameters whose
values are inconsistent. The results of the comparison help users identify the modified
parameters.
Benefits
Users can clearly identify system changes by using the parameter comparison function.
Description
 Comparing global algorithm parameters
The CME compares the values of global algorithm parameters with the baseline values.
After the comparison, it displays the parameters whose values are inconsistent. The
results of the comparison help users identify the modified parameters. The CME allows
users to use the default values as the baseline value for comparison. It also allows users
to select other baseline templates. The CME provides parameters and their corresponding
current values and baseline values. After comparing parameters, users can export the
comparison results. To view the global parameters, users can double-click the object
record to switch to the interface of global parameters.
 Comparing cell algorithm parameters
The CME allows users to compare the values of cell algorithm parameters with the
baseline values. After the comparison, it displays the parameters whose values are
inconsistent. The results of the comparison help users identify the modified parameters.
The CME lists the cells under the current RNC in the resource pool, and users specify
the cells to be compared. In addition, users need to specify a cell template for
comparison. After comparing parameters, users can export the comparison result. To
view certain parameters, users can double-click the object record to switch to the
corresponding configuration interface.
Enhancement
None.
Dependency
None.

2.1.7 WOFD- 184400 Import and Export of the Radio Network

Planning Data
Availability
Summary
The CME allows users to export the NBI (NBI) data related to the radio and transmission
interface configuration. By using the NBI data, the NMS can check the network status and
collect statistics on the network. The CME obtains the configuration data about the existing
network from the current data area and writes the data to the northbound database. The NMS
access the database to view the configuration data according to the name of the negotiation
data file.
Benefits
Devices on the network of a telecommunications operator are provided by different
manufacturers. To deal with differences between the devices and reduce workloads, users of
the NMS can manage data configuration of NEs directly through the NBIs. In this way, the
network can be efficiently planned and configured. The NMS can access the database of the
CME to obtain the required data through the NBI. The database is read only, which ensures
the security and integrity of the data.
Description
Based on the NBI model, the CME enables users to query the NBI databases. Only one NBI
database, that is, wnbidb, is provided directly to the NMS. Considering the database sizes and
the different RNC versions, only one data file is provided for an RNS at R version level. To
demonstrate the differences of RNS configuration models, multiple data files are provided for
RNSs with different R versions.
To provide uniform read-only interfaces to users, views need to be created in the RNS
databases of each R version. After the database in the current data area is updated, the data in
the views is extracted to the wnbidb database. In this way, the data security is ensured and
users can easily query the data.

Figure 1-1 Northbound database interface
Users can update the northbound database in the following ways:

1. Manually synchronize the RNS to trigger the update function of the northbound
database.
2. Manually enable the update function of the northbound database.
3. Set a scheduled task to synchronize the RNS and thus to trigger the update function of
the northbound database.
The northbound database file is named as follows: NBI_WRAN_<MOC name>_Version
number. Note that the version number is R level, for example, R008.
The file contains the negotiated radio interface and transmission interface parameters. The
radio interface parameters are as follows:
 Area information such as the LAC, SAC, RAC, URA, and MBMSSA.
 Cell
 Neighboring cell
 RNC global algorithm parameters
 Cell algorithm parameters
 Cell channel
 Information about the local cell and the related site and sector
The transmission interface parameters are as follows:
 Flow control parameters of the Iub interface

 Parameters of the logical Iub interface (ATM networking)

 Parameters of the physical Iub interface (ATM networking)
There are following constraints when the NMS accesses the CME database through the NBI:
1. The database can be read only by the NMS.
2. The CME database may change according to the software. In this case, the NMS needs
to be adapted for the change. Note that the adaptation of the NMS is a part of the normal
software change process.
3. When the NMS accesses the CME database through the NBI, the CME performance may
be affected. This is normal.
The NMS can connect the NBI in ODBC drive mode to access the database.
Enhancement
None.
Dependency
None.
2.1.8 WOFD- 184500 Interface for Exporting Radio and Transmission

Parameter Files
Availability
Summary
This feature provides the northbound data related to the configuration of the radio and
transmission interface for the NMS to check the data and collect statistics. Configuration data
is exported as XML files by the CME and is transferred to the NMS through the FTP. The
NMS obtains the configuration data exported by the CME from the FTP directory of the
M2000 through the FTP.
Benefits
This feature enables NMS users to manage configuration data through the NBI, thus
normalizing the devices of different vendors and reducing manpower requirement. This
facilitates network planning and configuration. By using this feature, the NMS obtains the
configuration data exported by the CME from the FTP directory of the M2000 through the
FTP.
Description
This feature provides the interface for exporting files based on the northbound configuration
model. For the radio network subsystem (RNS) that has multiple versions, each R version
uses only one model to normalize the data of B versions. Different R versions use different
models to demonstrate the difference between configuration models.

Figure 1-1 Northbound interface for exporting data
Based on the northbound configuration model, users can export the data of multiple RNSs
as .xml files manually or as scheduled.
To control the file size and reduce the transfer time, users can export files in either
compression mode or non-compression mode. The BZIP algorithm is used as the compression
algorithm.
To export the northbound file in .xml format, users can perform the following steps:
Step 1 Create an export task through the CME client.
Step 2 Select a target RNS and set the export time and export directory.
Step 3 Submit the task.
The default directory for saving the exported file is /export/home/omc/var/fileint/cm/0.
The naming conventions of the exported file are as follows:
<RNC-Name>_CME_<MM>_<DD>_<YYYY>_<HH>_<MM>_<SS>_<IP-field1>_
<IP-field2>_<IP-field3>_<IP-field4>.xml
The description of the naming rules is as follows:
<RNC-Name> is the placeholder for RNC name, which is defined by operator.
<MM>_<DD>_<YYYY>_<HH>_<MM>_<SS> is the date and time when the exported file is
generated.

<MM> represents the month. The value ranges from 1 to 12.

<DD> represents the day. The value ranges from 1 to 31.
<YYYY> represents the year. The value ranges from 1980 to 2099.
<HH> represents the hour. The value ranges from 0 to 23.
<MM> represents the minute. The value ranges from 0 to 59.
<SS> represent the second. The value ranges from 0 to 59.
<IP-field1>_<IP-field2>_<IP-field3>_<IP-field4> represents the IP address of the CME
server.
The exported file contains radio parameters and transmission parameters.
The radio parameters are categorized into the following types:
 Area information such as LAC, SAC, RAC, URA, and MBMSSA
 Cells
 Neighboring cells
 Global algorithm parameters of RNCs
 Channel parameters of cells
 Local cell data such as Site, Sector, and Locell
The transmission parameters are categorized into the following types:
 Logical parameters of the Iub interface (ATM)
 Physical parameters of the Iub interface (ATM)
Enhancement
None.
Dependency
None.
2.1.9 WOFD- 184600 Interface for Importing Radio Parameters and

Configuration Files of Neighboring Cells
Availability
Summary
NMS users can manage configuration data of NEs through the Northbound interface, thus
shielding the difference between the configuration tools on different element management
layers (EMLs). As a data transfer channel, the EML transfers messages between the NMS and
the NEs. In addition, the EML provides data check management.

After the radio parameters and configuration data are modified, the NMS issues the modified
parameters and configuration data to the NEs for the modification to take effect through the
CME.
The NMS imports the modified NE data into the CME. Then, the CME automatically
generates MML commands based on the imported files and issues them to NEs through the
script executor for the modification to take effect.
Benefits
The Northbound interfaces for importing and exporting data shield the difference between the
devices of different vendors, thus enable users to quickly and accurately configure and
manage the NEs based on planning.
After the data is imported, users can export it to check the data accuracy.
Description
The NMS compresses the .xml file to be imported and saves it in the specified FTP directory
on the M2000 through the FTP. The file is named based on the conventions that need to be
complied to by the NMS and the CME. The CME obtains and decompresses the file, and then
performs rule check on the data in the file. If the data passes the rule check, the CME
generates the incremental script for modifying data and issues the script to NEs. Then, the
NEs activate the script.
If the .xml file does not pass the rule check, the CME generates a rule check report in .txt
format and saves it in the specified FTP directory on the M2000. The NMS can obtain the
report from the M2000. The NEs generates a report in .xml format indicating whether the
script is successfully activated and submits the report to the CME. Then, the CME saves the
report in the specified FTP directory on the M2000. The NMS can obtain the report from the
M2000.
The following figure shows the process for importing data through the Northbound interface.

Figure 1-1 Northbound interface for importing data
Through the import interface, users can add, delete, and modify the following configuration
objects:
 Area information such as LAC, SAC, RAC, URA, and MBMSSA
 Cells
 Neighboring cells
 Global algorithm parameters of RNCs
 Channel parameters of cells
 Local cell data such as Site, Sector, and Locell
Users can add, delete, and modify each configuration object and the configuration parameters
of the object. For details, see the configuration model definition of each R version.
Enhancement
None.
Dependency
None.

2.1.10 WOFD- 184700 Interface for Importing NodeB Configuration

Data
Availability
Summary
NMS users can manage configuration data of NEs through the Northbound interface, thus
shielding the difference between the configuration tools on different element management
layers (EMLs). As a data transfer channel, the EML transfers messages between the NMS and
NEs. In addition, the EML provides data check management.
After the NodeB configuration data is modified, the NMS issues the modified parameters and
configuration data to NEs for the modification to take effect through the CME.
The NMS imports the modified NE data into the CME. Then, the CME automatically
generates a script file based on the imported file and issues the script to NEs through the script
executor to create or delete a NodeB, or adjust the transmission.
Benefits
The Northbound interfaces for importing and exporting data shield the difference between the
devices of different vendors, thus enable users to quickly and accurately configure and
manage NEs based on planning.
After the data is imported, users can export it to check the data accuracy.
Description
The NMS compresses the .xml file to be imported and saves it in the specified FTP directory
on the M2000 through the FTP. The file is named based on the rules agreed by the NMS and
the CME. The CME obtains and decompresses the file, and then performs rule check on the
data in the file. If the data passes the rule check, the CME generates the incremental script for
modifying data and issues the script to NEs. Then, the NEs activate the script.
If the .xml file does not pass the rule check, the CME generates a rule check report in .txt
format and saves it in the specified FTP directory on the M2000. The NMS can obtain this
report from the M2000. The NEs generates a report in .xml format indicating whether the
script is successfully activated and submits the report to the CME. Then, the CME saves the
report in the specified FTP directory on the M2000. The NMS can obtain the report from the
M2000.
Through the import interface, users can add, delete, and modify the following configuration
objects:
 Logical parameters of the Iub interface (ATM)
 Physical parameters of the Iub interface (ATM)
This feature is applicable to the following scenarios:
 Creating and deleting logical NodeBs in ATM mode
 Creating and deleting physical NodeBs in ATM mode

 Modifying the configuration data of the Iub protocol stack of logical NodeBs in ATM
mode
 Modifying the configuration data of the Iub protocol stack of physical NodeBs in ATM
mode
 To ensure the interface integrity, a complete Iub model should be provided when adding
and modifying the interface. The configuration of single transmission link is not
supported.
 Adding and deleting Iub interfaces does not affect the addition and deletion of cells
under the corresponding NodeB.
Enhancement
None.
Dependency
None.
2.1.11 WOFD- 180400 NodeB Reparenting

Availability
Summary
The WRAN NodeB reparenting function is an enhanced feature provided by the CME. The
CME provides a GUI-based wizard for NodeB reparenting inside one RNC or between
different RNCs. The NodeB reparenting function adjusts the neighboring cell relations, thus
ensuring the data consistency of neighboring cell relations after the reparenting.
Benefits
Complicated operations are integrated into an easy-to-use wizard, which improves the
maintenance efficiency and accuracy.
Description
NodeB reparenting inside one RNC
During network construction, operators may need to reparent NodeBs inside one RNC or
between different RNCs owing to the following reasons:
 For adjusting the network planning during the network operation
 For balancing the load after an RNC expansion during the network operation
 For adjusting the number of NodeBs in hot spot areas and in non-hot spot areas for load
balancing between the service subracks of the RNC
For NodeB reparenting inside one RNC, the NodeB is relocated from one RNS to another or
from one subrack to another with the upper layer applications unchanged. The physical

location of the NodeB is not changed; thus, the neighboring cell relations of its corresponding
cell and other cells remain unchanged. The consistency of neighboring cell relations is
automatically updated by the CME.
 Supporting the scenario of NodeB reparenting inside one subrack of one RNC (over
ATM)
The CME provides a GUI-based wizard for NodeB reparenting inside one subrack of one
RNC. The NodeB is relocated from one RNS to another with the upper layer applications
unchanged. The physical location of the NodeB is not changed; thus, the neighboring cell
relations of its corresponding cell and other cells remain unchanged.
 Supporting the scenario of NodeB reparenting between different subracks of one RNC
(over ATM)
The CME provides a GUI-based wizard for NodeB reparenting between subracks inside one
RNC. The NodeB is relocated from one subrack to another with the upper layer applications
unchanged. The physical location of the NodeB is not changed; thus, the neighboring cell
relations of its corresponding cell and other cells remain unchanged.
NodeB reparenting between RNCs
During network construction, operators may need to reparent NodeBs inside one RNC or
between different RNCs owning to the following reasons:
 For adjusting the network planning during the network operation
 For balancing the load after an RNC expansion during the network operation
 For adjusting the number of NodeBs in hot spots and in non-hot spots for load balancing
between the service subracks of the RNC
For NodeB reparenting between RNCs, the upper-layer applications remain unchanged, but
the location of the NodeB is changed. Therefore, the corresponding cell and the neighboring
cell relations are updated. The CME automatically handles the neighboring cell relations and
maintains the neighboring cell relations after the NodeB reparenting.
Enhancement
None.
Dependency
None.
2.1.12 WOFD- 180500 Consistency Check for Global Data

Availability
Summary
The CME provides the Sanity Checking function to check data redundancy and consistency.
This function enables users to find the unsanitary data globally, that is, in the data of multiple
RNCs. The unsanitary data is the data that is not intact, redundant, or improper. In addition,
the CME provides the interface switchover function for data modification.

Users can use this function to check data consistency among RNSs so that improperly
configured or erroneous data can be detected. By using the interface switchover function,
users can restore such data.
Benefits
Users can check data consistency by using the consistency check function provided by the
CME.
The interface switchover function of the CME helps users to restore the system.
Description
Data integrity is ensured only when configuration data is loaded on network elements and the
network elements start and run successfully. Users can set conditions for data consistency
check. The check conditions include object types and rule types under a selected object type.
The CME performs consistency check on the current configuration data. The check result has
two alarm severities: Major and Warning. Major indicates the absence of required data. Such
absence data may affect the operation of the system. Warning is an alarm severity lower than
Major. An alarm at the Warning severity does not significantly affect the operation of the
system. Based on the check result, the interface switchover function helps users to switch to
the related interface to modify data.
After data configuration is complete, users can check data redundancy on the CME. The
redundant data refers to the data that has not been used for a long time. The redundancy check
helps clear redundant data to reduce the load. It also helps ensure that obsolete data is deleted
after a data modification. Users can set conditions for checking data redundancy. The check
conditions include object types and rule types under a selected object. The CME checks the
current configuration data and provides the check result. The interface switchover function of
the CME helps users to switch to the related interface to browse information. Based on the
check result, the CME allows users to delete redundant data from the system.
By using the data consistency check function, users can perform the following operations:
 Check whether parameters of the same cell or NRNC cell configured for different RNSs
are the same.
 Check whether parameters of the same GSM cell configured for different RNSs are the
same.
 Check whether the cell that corresponds to the NRNC cell is configured.
 Check whether the names of the cell, NRNC cell, and GSM cell conflict.
 Check unidirectional neighboring cells.
Users can customize check items based on all the items provided by the system, as shown in
Figure 1-1.

Figure 1-1 Customizing check items
The system allows users to set the following severities for check items:
 Error
 Major
 Warning
Based on the check result, users can switch to the related configuration interface to modify
data or select automatic recovery for specific errors, as shown in Figure 1-2.

Figure 1-2 RAN AutoFix window
 Delete TwinCell->FddCell Relation: deletes the inter-frequency neighboring relations

from TwinCell to FddCell.
 Deactivated FddCell HSPA: deactivates the HSDPA/HSUPA service of the FddCell if
the service is activated in the check result.
 Activated TwinCell HSPA: activates the HSDPA/HSUPA service of the TwindCell if
the service is deactivated in the check result.
 Modify FddCell->TwinCell Relation BlindHo: If only one inter-frequency relation
exists from FddCell to TwinCell, and the blind handover priority is not set, set this
priority to 0.
 Refresh NCell: automatically modifies the NRNCCell data of the other RNCs in this
check, to ensure that the NRNCCell data is consistent with that of the source cell.
Users can select multiple check results for comparison, as shown Figure 1-3.

Figure 1-3 RAN Consistency Check window
Users can perform consistency check manually or set a time point for automatic check.
Check the consistency of the Iub interface data.
By performing consistency check for the Iub interface data, users can detect inconsistent
interconnection data for the two ends of the Iub interface. This helps users to find improper or
erroneous configuration data, thus ensuring the normal communication between the RNC and
the NodeB. Iub data consistency check involves only the data at the data link layer and higher
layers. Note that the check should be performed according to the Iub protocol stack in
descending order.
Iub data consistency check is applicable to the following scenarios:
− After the Iub interface data is configured on both the RNC side and the NodeB side,
users need to perform Iub data consistency check for each NodeB connected by the
Iub interface to implement the communication between the RNC and NodeBs.
− The data on the RNC side is synchronized with the data on the NodeB side by
updating the Iub interface data. In such a case, if the data on the RNC or NodeB side
is modified, users need to perform Iub data consistency check to compare the data on
the two sides and determine whether the data modification affects the communication
between the RNC and the NodeB.
Enhancement
None.
Dependency
None.

2.1.13 WOFD- 510300 Integration Solution of Citrix-based CME

Client
Availability
Summary
This feature allows users to integrate the CME client into the existing Citrix environment. In
this way, the CME can provide enterprise level deployment of OM applications by using the
powerful functions of the Citrix.
Benefits
 Provides quick deployment and single-point maintenance: Users can install, upgrade, and
maintain the CME client on only the Citrix server, which implements the quick deployment of
the CME applications, improves the maintenance efficiency, and reduces the maintenance
cost.
 Requires less bandwidth resource: The bandwidth requirement of the Citrix is only 64 kbit/s
on each client.
 Supports multiple networks and reducing networking costs: The Citrix-based integration
solution supports multiple network protocols such as IPX, SPX, NetBEUI, TCP/IP, and PPP,
and supports multiple networking modes such as Dial-Up, ISDN, Frame Relay, X.25, and
ATM. In addition, it supports the wireless connection over the Internet or Intranet.
 Improves security: The CME client is installed on the Citrix server. The Citrix server is
deployed with the same firewall as the CME server, which reduces the risks of unauthorized
visits, virus attacks, and malicious attacks. In addition, the Citrix server provides the enhanced
security networking that is optional, allows the SSL connection during the visit to the server,
and encrypts information such as the account, password, server IP address, and server port
number.
 Supports the web-based remote visit over platforms: The Citrix can convert the CME client
windows to web pages and send them to the Citrix client. Users can remotely use the CME by
installing the Citrix client and installing the Internet Explorer (IE) or Netscape Explorer.
 Supports investment estimation: The Citrix has low requirements for clients, thus supporting
multiple client types and networks. The Citrix also provides the integrated deployment and
maintenance of the clients, thus reducing the maintenance cost. In this case, users can focus on
only the investment on the Citrix server to accurately estimate the investment.
Description
The applications of the CME client are installed on a Citrix server or on a Farm group
consisting of multiple Citrix servers. Users can operate the CME by installing the Independent
Computing Architecture (ICA) on the Citrix client to communicate with the Citrix server or
Farm group. All the applications are executed on the Citrix server, and all the operation results
of the Citrix server can be displayed on the local Citrix client.
The Citrix supports the Farm group consisting of multiple Citrix servers and implements the
load balance between the servers. Citrix The Farm group balance load is based on the
resources of the servers, such as the CPU and memory. It ensures optimal usage of server
resources and the performance of the CME client.

This feature has the following constraints:

 If multiple users log in to the CME through the same account, local settings may be
overwrote by the settings of a later user.
 The input/output (I/O) operations such as Print or Save As are performed on the Citrix
server rather than the Citrix client.
 If there is a firewall between the Citrix server and Citrix client, ports 80 and 1494 should
be enabled.
The CME uses the Windows operating system; thus, this feature supports only the Windows-
based Citrix.
Enhancement
None.
Dependency
None.

3 Acronyms and Abbreviations
Abbreviation Full Spelling
WRAN WCDMA Radio Access Network
CME Configuration Management Express
3GPP2 3rd Generation Partnership Project 2
AAL ATM Adaptation Layer
APN Access Point Name
ATM Asynchronous Transfer Mode
BCCH Broadcast Control Channel
BG Border Gateway

WRAN CME V100R008 Feature Description

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

WRAN CME V100R008 Feature Description

Uploaded by

Copyright:

Available Formats

Document code

WRAN CME V100R008 Feature

Huawei Technologies Co.,Ltd.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue V1.0 (2009-03-20) Huawei Technologies Proprietary Page 3 of 53

2.1.1 WOFD- 183800 NodeB Topology Browsing.........................................................................................31

3 Acronyms and Abbreviations.....................................................................................................53

Issue V1.0 (2009-03-20) Huawei Technologies Proprietary Page 4 of 53

Figure 1-1 Batch reconfiguration of parameters...................................................................................................29

Figure 2-1 Northbound database interface............................................................................................................38

Figure 2-2 Northbound interface for exporting data.............................................................................................40

Figure 2-3 Northbound interface for importing data............................................................................................43

Figure 2-4 Customizing check items....................................................................................................................48

Figure 2-5 RAN AutoFix window........................................................................................................................49

Figure 2-6 RAN Consistency Check window.......................................................................................................50

Issue V1.0 (2009-03-20) Huawei Technologies Proprietary Page 5 of 53

1 WOFD – 181000 Basic Features

1.1 Platform Functions

Issue V1.0 (2009-03-20) Huawei Technologies Proprietary Page 6 of 53

1.1.2 WOFD- 181600 Data Browsing and Searching

Issue V1.0 (2009-03-20) Huawei Technologies Proprietary Page 7 of 53

Issue V1.0 (2009-03-20) Huawei Technologies Proprietary Page 8 of 53

1.1.3 WOFD- 181700 Script Executor

Issue V1.0 (2009-03-20) Huawei Technologies Proprietary Page 9 of 53

1.1.4 WOFD- 181800 Dump Feature of the Planned Data Area

Issue V1.0 (2009-03-20) Huawei Technologies Proprietary Page 10 of 53

1.1.5 WOFD- 181900 Upgrade of History Planned Data Areas

Issue V1.0 (2009-03-20) Huawei Technologies Proprietary Page 11 of 53

1.1.6 WOFD- 182000 Hardware Monitoring

Issue V1.0 (2009-03-20) Huawei Technologies Proprietary Page 12 of 53

1.1.7 WOFD- 182100 Automatic Upgrade of the CME Client

Issue V1.0 (2009-03-20) Huawei Technologies Proprietary Page 13 of 53

1.1.8 WOFD- 182200 Supporting the Windows Vista Operating

Issue V1.0 (2009-03-20) Huawei Technologies Proprietary Page 14 of 53

1.2 Device Management

1.2.2 WOFD- 182400 Device Panel

Issue V1.0 (2009-03-20) Huawei Technologies Proprietary Page 15 of 53

1.2.3 WOFD- 182500 Automatic Discovery of RNCs and NodeBs

Issue V1.0 (2009-03-20) Huawei Technologies Proprietary Page 16 of 53

Issue V1.0 (2009-03-20) Huawei Technologies Proprietary Page 17 of 53

1.2.4 WOFD- 182600 RNC Pool Management

Issue V1.0 (2009-03-20) Huawei Technologies Proprietary Page 18 of 53

1.2.5 WOFD- 182700 RNC MOCN Management

Issue V1.0 (2009-03-20) Huawei Technologies Proprietary Page 19 of 53

Issue V1.0 (2009-03-20) Huawei Technologies Proprietary Page 20 of 53

1.3 Configuration of Transmission Parameters

Issue V1.0 (2009-03-20) Huawei Technologies Proprietary Page 21 of 53

1.3.2 WOFD- 182900 Batch Configuration of the Objects Related

1.3.3 WOFD- 183000 Import and Export of the Interface

Issue V1.0 (2009-03-20) Huawei Technologies Proprietary Page 22 of 53

1.3.4 WOFD- 183100 NodeB Configuration Template

Issue V1.0 (2009-03-20) Huawei Technologies Proprietary Page 23 of 53

Issue V1.0 (2009-03-20) Huawei Technologies Proprietary Page 24 of 53

1.4 Radio Parameter Configuration

1.4.2 WOFD- 183300 Configuration of Neighboring Cell Relations

Issue V1.0 (2009-03-20) Huawei Technologies Proprietary Page 25 of 53

1.4.3 WOFD- 183400 Wizard for Adjusting Radio Neighboring

Issue V1.0 (2009-03-20) Huawei Technologies Proprietary Page 26 of 53

1.4.4 WOFD- 183500 Import and Export of the Radio Network

Issue V1.0 (2009-03-20) Huawei Technologies Proprietary Page 27 of 53

1.4.5 WOFD- 183600 Batch Configuration of Radio Parameters

1.4.6 WOFD- 183700 Wizard for Batch Configuration of Radio

Issue V1.0 (2009-03-20) Huawei Technologies Proprietary Page 28 of 53