Wran Cme User Guide-(v100r005_01)

WRAN CME V100R005

WRAN CME User Guide

Issue

01

Date

2008-06-25

Part Number

Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd

Huawei Technologies Co., Ltd. provides customers with comprehensive technical support and service. For any assistance, please contact our local office or company headquarters.

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

Copyright © Huawei Technologies Co., Ltd. 2008. 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 the property of Huawei Technologies Co., Ltd. All other trademarks and trade names mentioned in this document are the property of their respective holders.

Notice 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 the statements, information, and recommendations in this document do not constitute a warranty of any kind, express or implied.


WRAN CME WRAN CME User Guide

Contents

Contents About This Document.....................................................................................................................1 1 Copyright Declaration of the Third-Party Software...........................................................1-1 2 Introduction to the CME...........................................................................................................2-1 2.1 Software Structure of the CME.......................................................................................................................2-2 2.2 Hardware Structure of the CME......................................................................................................................2-3 2.3 Features of the CME.......................................................................................................................................2-5

3 Applications of the CME..........................................................................................................3-1 3.1 Definition of RAN Initial Configuration.........................................................................................................3-2 3.1.1 Definition of RNC Initial Configuration................................................................................................3-2 3.1.2 Definition of NodeB Initial Configuration.............................................................................................3-2 3.2 Process of RAN Initial Configuration.............................................................................................................3-3 3.3 Definition of RAN Reconfiguration................................................................................................................3-4 3.4 Process of RAN Reconfiguration....................................................................................................................3-4 3.5 Configuration Objects of the CME.................................................................................................................3-6

4 Concepts of the CME.................................................................................................................4-1 4.1 Workspace.......................................................................................................................................................4-2 4.2 Negotiation and Planning Data File................................................................................................................4-2 4.3 NodeB Template File......................................................................................................................................4-3 4.4 NodeB Configuration File...............................................................................................................................4-4 4.5 RNC BAM Database.......................................................................................................................................4-4 4.6 RNC Configuration File..................................................................................................................................4-5 4.7 CME License File............................................................................................................................................4-6

5 Views of the CME Client..........................................................................................................5-1 5.1 Main Window..................................................................................................................................................5-2 5.2 NodeB Device Panel.......................................................................................................................................5-4 5.3 NodeB Network Topology..............................................................................................................................5-6 5.4 Resource Usage Display..................................................................................................................................5-8 5.5 Window for Batch Addition............................................................................................................................5-9 5.6 Shortcut Keys................................................................................................................................................5-10

6 Installing the CME.....................................................................................................................6-1 6.1 Installing the CME Server (Standalone).........................................................................................................6-2 Issue 01 (2008-06-25)


i


Contents

6.1.1 Computer Requirements of the CME Server (Standalone)....................................................................6-2 6.1.2 Installing MSDE 2000 SP4 (Standalone)...............................................................................................6-3 6.2 Installing the CME Server (Integrated)...........................................................................................................6-4 6.2.1 Computer Requirements of the CME Server (Integrated)......................................................................6-5 6.2.2 Installing the Operating System.............................................................................................................6-6 6.2.3 Installing the Database Software..........................................................................................................6-20 6.2.4 Configuring Initialization Parameters for the CMEServer Service......................................................6-41 6.2.5 Installing the Application Software......................................................................................................6-43 6.3 Installing and Uninstalling the CME Client..................................................................................................6-44 6.3.1 Computer Requirements of the CME Client........................................................................................6-44 6.3.2 Installing the CME Client Software.....................................................................................................6-45 6.3.3 Uninstalling the CME Client Software................................................................................................6-49 6.4 IP Port Configuration Requirements.............................................................................................................6-51

7 Operating the CME....................................................................................................................7-1 7.1 Data Configuration Process in Standalone Mode...........................................................................................7-2 7.1.1 Starting the CME Client.........................................................................................................................7-4 7.1.2 Opening the RAN...................................................................................................................................7-6 7.1.3 Creating an RNS.....................................................................................................................................7-7 7.1.4 Opening an RNS.....................................................................................................................................7-8 7.1.5 Synchronizing RNC Data.......................................................................................................................7-9 7.1.6 Checking Data......................................................................................................................................7-11 7.1.7 Closing an RNS....................................................................................................................................7-37 7.1.8 Deleting an RNS...................................................................................................................................7-37 7.1.9 Exiting the CME Client........................................................................................................................7-37 7.2 Data Configuration Process in Integrated Mode...........................................................................................7-38 7.2.1 Starting the CME Client.......................................................................................................................7-42 7.2.2 Loading Data from the Existing Network............................................................................................7-42 7.2.3 Viewing Changed NEs.........................................................................................................................7-44 7.2.4 Synchronizing with the Data on the Existing Network........................................................................7-47 7.2.5 Creating a Planned Data Area..............................................................................................................7-50 7.2.6 Opening a Planned Data Area..............................................................................................................7-52 7.2.7 Synchronizing RNS Data.....................................................................................................................7-53 7.2.8 Opening an RNS...................................................................................................................................7-54 7.2.9 Checking Data......................................................................................................................................7-55 7.2.10 Checking Data Consistency...............................................................................................................7-83 7.2.11 Exporting a Modification Report.......................................................................................................7-84 7.2.12 Activating Data..................................................................................................................................7-85 7.2.13 Closing a Planned Data Area.............................................................................................................7-90 7.2.14 Deleting a Planned Data Area............................................................................................................7-90 7.2.15 Exiting the CME Client......................................................................................................................7-91 7.3 Managing Data Files.....................................................................................................................................7-92 7.3.1 Managing a Radio Network Planning Data File..................................................................................7-93 ii


Issue 01 (2008-06-25)


Contents

7.3.2 Managing an Interface Negotiation Data File......................................................................................7-98 7.3.3 Managing a NodeB Template File.....................................................................................................7-102 7.3.4 Managing an NodeB Configuration File............................................................................................7-105 7.3.5 Managing an RNC Configuration File...............................................................................................7-109 7.3.6 Managing a Cell Template File..........................................................................................................7-132 7.3.7 Managing Hot NodeBs and Cells.......................................................................................................7-134 7.3.8 Exporting Cell Algorithm Parameters and Channel Data..................................................................7-138 7.4 Comparing Radio Algorithm Parameters....................................................................................................7-139 7.4.1 Comparing RNC-Oriented Algorithm Parameters.............................................................................7-139 7.4.2 Comparing Cell-Oriented Algorithm Parameters..............................................................................7-141 7.5 Backing Up and Restoring an RNS.............................................................................................................7-142 7.5.1 Backing Up an RNS...........................................................................................................................7-143 7.5.2 Restoring an RNS...............................................................................................................................7-144 7.5.3 Deleting a Backup File.......................................................................................................................7-146 7.5.4 Backing Up an RNS (bcp)..................................................................................................................7-147 7.5.5 Storing an RNS (bcp).........................................................................................................................7-148 7.6 Searching and Browsing Data.....................................................................................................................7-149

Issue 01 (2008-06-25)


iii


Figures

Figures Figure 2-1 Software components of the CME......................................................................................................2-2 Figure 2-2 Software structure of the CME in integrated mode............................................................................2-3 Figure 2-3 Position of the CME in standalone mode...........................................................................................2-4 Figure 2-4 Position of the CME in integrated mode............................................................................................2-5 Figure 3-1 Process of RAN initial configuration.................................................................................................3-3 Figure 3-2 Process of RAN reconfiguration.........................................................................................................3-5 Figure 3-3 CME-based configuration objects......................................................................................................3-6 Figure 5-1 Main window with no RNS open (standalone CME).........................................................................5-2 Figure 5-2 Main window with an RNS open (standalone CME).........................................................................5-3 Figure 5-3 Main window with an RNS open (CME integrated into the M2000)................................................5-4 Figure 5-4 Selecting a physical cell.....................................................................................................................5-5 Figure 5-5 Device Panel of the BTS3836A..........................................................................................................5-6 Figure 5-6 NodeB Network Topology.................................................................................................................5-7 Figure 5-7 Resource usage display.......................................................................................................................5-8 Figure 5-8 Window for batch adding AAL2 Path links.......................................................................................5-9 Figure 6-1 Entering the disk array configuration dialog box...............................................................................6-7 Figure 6-2 Creating a logical disk........................................................................................................................6-8 Figure 6-3 Selecting a RAID mode......................................................................................................................6-9 Figure 6-4 Setting the working mode.................................................................................................................6-10 Figure 6-5 Configuring the disk arrays..............................................................................................................6-11 Figure 6-6 Selecting the operating system.........................................................................................................6-12 Figure 6-7 Selecting the disk partition...............................................................................................................6-13 Figure 6-8 Specifying the size of the disk partition...........................................................................................6-14 Figure 6-9 Configure Operating System information........................................................................................6-15 Figure 6-10 Configure SNMP............................................................................................................................6-16 Figure 6-11 Select PSP mode.............................................................................................................................6-16 Figure 6-12 Ready to install...............................................................................................................................6-17 Figure 6-13 Selecting the Ethernet adapters.......................................................................................................6-19 Figure 6-14 Teaming the Ethernet adapters.......................................................................................................6-19 Figure 6-15 information dialog box...................................................................................................................6-22 Figure 6-16 Entering a computer name..............................................................................................................6-22 Figure 6-17 Selecting an installation option.......................................................................................................6-23 Figure 6-18 Entering the user information.........................................................................................................6-23 Issue 01 (2008-06-25)


v


Figures

Figure 6-19 Entering the CD-Key......................................................................................................................6-24 Figure 6-20 Defining the installation.................................................................................................................6-25 Figure 6-21 Entering an instance name..............................................................................................................6-25 Figure 6-22 Selecting a setup type.....................................................................................................................6-26 Figure 6-23 Selecting components.....................................................................................................................6-26 Figure 6-24 Setting service accounts..................................................................................................................6-27 Figure 6-25 Setting the authentication mode.....................................................................................................6-28 Figure 6-26 Setting the collation........................................................................................................................6-29 Figure 6-27 Setting network libraries.................................................................................................................6-30 Figure 6-28 Starting copying files......................................................................................................................6-30 Figure 6-29 Choosing a licensing mode.............................................................................................................6-31 Figure 6-30 Setup complete...............................................................................................................................6-32 Figure 6-31 Selecting an installation folder.......................................................................................................6-34 Figure 6-32 Connecting to the SQL server........................................................................................................6-35 Figure 6-33 Setting the backward compatibility................................................................................................6-36 Figure 6-34 Setting whether to report errors to Microsoft.................................................................................6-37 Figure 6-35 Confirming the setup......................................................................................................................6-37 Figure 6-36 Confirming the setup......................................................................................................................6-38 Figure 6-37 Connecting to the SQL Server........................................................................................................6-39 Figure 6-38 SQL Server Service Manager in operation.....................................................................................6-40 Figure 6-39 SQL Server Service Manager out of operation...............................................................................6-40 Figure 6-40 License agreement..........................................................................................................................6-47 Figure 6-41 Entering customer information.......................................................................................................6-48 Figure 6-42 Specifying the destination folder....................................................................................................6-48 Figure 6-43 Confirming the installation.............................................................................................................6-49 Figure 6-44 Uninstalling the CME client software............................................................................................6-50 Figure 7-1 Data configuration process.................................................................................................................7-2 Figure 7-2 Reading the license information.........................................................................................................7-5 Figure 7-3 Logging in to the CME.......................................................................................................................7-5 Figure 7-4 Opening the RAN...............................................................................................................................7-6 Figure 7-5 Setting the parameters of the CME server..........................................................................................7-7 Figure 7-6 Creating an RNS on a standalone CME............................................................................................. 7-8 Figure 7-7 Selecting a BAM................................................................................................................................ 7-9 Figure 7-8 Registering the information of the BAM..........................................................................................7-10 Figure 7-9 Configuring the information of the BAM.........................................................................................7-10 Figure 7-10 Specifying check rules....................................................................................................................7-16 Figure 7-11 Checking data consistency..............................................................................................................7-17 Figure 7-12 Modifying the NRNC of the neighboring cell................................................................................7-19 Figure 7-13 Selecting the objects to be modified...............................................................................................7-19 Figure 7-14 Modifying the cell name.................................................................................................................7-20 Figure 7-15 Selecting a reference cell................................................................................................................7-20 Figure 7-16 Export the MML script...................................................................................................................7-21 vi


Issue 01 (2008-06-25)


Figures

Figure 7-17 Checking data consistency (1)........................................................................................................7-22 Figure 7-18 Creating a check task......................................................................................................................7-23 Figure 7-19 Checking data consistency (2)........................................................................................................7-24 Figure 7-20 Comparison of check results...........................................................................................................7-25 Figure 7-21 Modifying the NRNC of the neighboring cell................................................................................7-27 Figure 7-22 Selecting the objects to be modified...............................................................................................7-27 Figure 7-23 Modifying the cell name.................................................................................................................7-28 Figure 7-24 Selecting a reference cell................................................................................................................7-28 Figure 7-25 Export the MML script...................................................................................................................7-29 Figure 7-26 Specifying check rules....................................................................................................................7-30 Figure 7-27 Checking data redundancy..............................................................................................................7-31 Figure 7-28 Iub interface data check result........................................................................................................7-35 Figure 7-29 Data configuration process.............................................................................................................7-39 Figure 7-30 Available RNS(s) to be created......................................................................................................7-43 Figure 7-31 Displaying the RNS creation progress............................................................................................7-44 Figure 7-32 Checking changed NEs...................................................................................................................7-45 Figure 7-33 Viewing the changed NEs..............................................................................................................7-45 Figure 7-34 Browsing the log.............................................................................................................................7-46 Figure 7-35 Specifying filter conditions............................................................................................................7-47 Figure 7-36 Viewing the RNSs available for synchronization...........................................................................7-48 Figure 7-37 Create a planned data area..............................................................................................................7-51 Figure 7-38 Creating a planned data area successfully......................................................................................7-51 Figure 7-39 Loading RNS data..........................................................................................................................7-52 Figure 7-40 Selecting a planned data area..........................................................................................................7-53 Figure 7-41 Selecting the NEs to be synchronized............................................................................................7-54 Figure 7-42 Setting the check items...................................................................................................................7-55 Figure 7-43 Viewing the check report................................................................................................................7-56 Figure 7-44 Data check report............................................................................................................................7-57 Figure 7-45 Specifying check rules....................................................................................................................7-62 Figure 7-46 Checking data consistency..............................................................................................................7-63 Figure 7-47 Modifying the NRNC of the neighboring cell................................................................................7-65 Figure 7-48 Selecting the objects to be modified...............................................................................................7-65 Figure 7-49 Modifying the cell name.................................................................................................................7-66 Figure 7-50 Selecting a reference cell................................................................................................................7-66 Figure 7-51 Export the MML script...................................................................................................................7-67 Figure 7-52 Checking data consistency (1)........................................................................................................7-68 Figure 7-53 Creating a check task......................................................................................................................7-69 Figure 7-54 Checking data consistency (2)........................................................................................................7-70 Figure 7-55 Comparison of check results...........................................................................................................7-71 Figure 7-56 Modifying the NRNC of the neighboring cell................................................................................7-73 Figure 7-57 Selecting the objects to be modified...............................................................................................7-73 Figure 7-58 Modifying the cell name.................................................................................................................7-74 Issue 01 (2008-06-25)


vii


Figures

Figure 7-59 Selecting a reference cell................................................................................................................7-74 Figure 7-60 Export the MML script...................................................................................................................7-75 Figure 7-61 Specifying check rules....................................................................................................................7-76 Figure 7-62 Checking data redundancy..............................................................................................................7-77 Figure 7-63 Iub interface data check result........................................................................................................7-81 Figure 7-64 Checking data consistency..............................................................................................................7-84 Figure 7-65 Viewing the modification report.....................................................................................................7-85 Figure 7-66 Displaying the project state............................................................................................................7-86 Figure 7-67 Modifying task-related information................................................................................................7-87 Figure 7-68 Uploading a project........................................................................................................................7-88 Figure 7-69 Checking result or adjusting execution..........................................................................................7-89 Figure 7-70 Selecting a planned data area..........................................................................................................7-91 Figure 7-71 Selecting a file................................................................................................................................7-94 Figure 7-72 Confirming the items to be imported..............................................................................................7-95 Figure 7-73 Confirming the items to be exported..............................................................................................7-97 Figure 7-74 Selecting a File...............................................................................................................................7-98 Figure 7-75 Selecting the interface type.............................................................................................................7-99 Figure 7-76 Specifying an interface data file...................................................................................................7-100 Figure 7-77 Selecting the interface type...........................................................................................................7-101 Figure 7-78 Creating a physical NodeB...........................................................................................................7-103 Figure 7-79 Specifying NodeB information.....................................................................................................7-104 Figure 7-80 Creating a physical NodeB...........................................................................................................7-105 Figure 7-81 Creating a physical NodeB...........................................................................................................7-107 Figure 7-82 Importing a NodeB data configuration file...................................................................................7-107 Figure 7-83 Viewing the NodeB list................................................................................................................7-108 Figure 7-84 Creating a physical NodeB...........................................................................................................7-109 Figure 7-85 Selecting the type of data to be exported......................................................................................7-111 Figure 7-86 Specifying the objects to be exported...........................................................................................7-111 Figure 7-87 Specifying the path for the file to be exported.............................................................................7-112 Figure 7-88 Specifying the type of script to be exported.................................................................................7-113 Figure 7-89 Setting the data items to be exported............................................................................................7-114 Figure 7-90 Selecting a NodeB complete.........................................................................................................7-115 Figure 7-91 Specifying to export cell data.......................................................................................................7-116 Figure 7-92 Setting the data items to be exported............................................................................................7-117 Figure 7-93 Specifying the type of script to be exported.................................................................................7-118 Figure 7-94 Selecting algorithms to be exported.............................................................................................7-119 Figure 7-95 Specifying the data to be exported and cell status configuration data..........................................7-120 Figure 7-96 Selecting algorithms to be exported.............................................................................................7-121 Figure 7-97 Specifying the data and the type of script to be exported.............................................................7-122 Figure 7-98 Specifying the data and the type of script to be exported.............................................................7-123 Figure 7-99 Selecting ATM traffic records......................................................................................................7-124 Figure 7-100 Specifying Data and Script Type................................................................................................7-125 viii


Issue 01 (2008-06-25)


Figures

Figure 7-101 Setting Data Items to be Exported..............................................................................................7-126 Figure 7-102 Specifying the data and the type of script to be exported...........................................................7-128 Figure 7-103 Setting the data items to be exported..........................................................................................7-128 Figure 7-104 Selecting a neighboring RNC.....................................................................................................7-129 Figure 7-105 Selecting a neighboring RNC complete.....................................................................................7-130 Figure 7-106 Specifying to export NRNC cell data.........................................................................................7-131 Figure 7-107 Configuring a cell template........................................................................................................7-132 Figure 7-108 Loading hot objects....................................................................................................................7-135 Figure 7-109 Setting attributes.........................................................................................................................7-135 Figure 7-110 An example file for accurate matching.......................................................................................7-136 Figure 7-111 Loading hot objects....................................................................................................................7-136 Figure 7-112 Setting attributes.........................................................................................................................7-137 Figure 7-113 Setting the matching mode.........................................................................................................7-137 Figure 7-114 An example file for accurate matching.......................................................................................7-138 Figure 7-115 Browsing cell channel information.............................................................................................7-139 Figure 7-116 Global Params Compare window...............................................................................................7-140 Figure 7-117 Cell Oriented Params Compare window....................................................................................7-142 Figure 7-118 Selecting an RNS........................................................................................................................7-143 Figure 7-119 Specifying the path for the backup file.......................................................................................7-144 Figure 7-120 Selecting a backup file................................................................................................................7-145 Figure 7-121 Modifying the RNS ID...............................................................................................................7-145 Figure 7-122 Selecting the RAN......................................................................................................................7-146 Figure 7-123 Selecting a backup file................................................................................................................7-147 Figure 7-124 Selecting RNSs...........................................................................................................................7-148 Figure 7-125 Selecting a target RNS................................................................................................................7-149 Figure 7-126 Panorama browser window........................................................................................................7-150 Figure 7-127 Specifying sorting fields (1).......................................................................................................7-151 Figure 7-128 Specifying sorting fields (2).......................................................................................................7-151 Figure 7-129 Panorama browser window........................................................................................................7-152

Issue 01 (2008-06-25)


ix


Tables

Tables Table 3-1 Process of RAN initial configuration...................................................................................................3-3 Table 3-2 Process of RAN reconfiguration..........................................................................................................3-5 Table 5-1 Elements in the window.......................................................................................................................5-2 Table 5-2 Elements in the window.......................................................................................................................5-3 Table 5-3 Elements on the resource usage display...............................................................................................5-8 Table 5-4 Elements in the window for batch adding AAL2 Path links..............................................................5-10 Table 5-5 Shortcut keys......................................................................................................................................5-10 Table 6-1 Hardware requirements of the CME server..........................................................................................6-2 Table 6-2 Software requirements of the CME server...........................................................................................6-3 Table 6-3 MSDE 2000 SP4 icons.........................................................................................................................6-4 Table 6-4 Hardware requirements of the HP server.............................................................................................6-5 Table 6-5 Software requirements of the CME server...........................................................................................6-6 Table 6-6 CME server configuration checklist...................................................................................................6-20 Table 6-7 Hardware requirements of the CME client........................................................................................6-45 Table 6-8 Software requirements of the CME client..........................................................................................6-45 Table 7-1 Process of data configuration through the CME in standalone mode..................................................7-3 Table 7-2 Data to be checked on the radio network layer..................................................................................7-13 Table 7-3 Modification wizard...........................................................................................................................7-18 Table 7-4 Description of result comparison.......................................................................................................7-25 Table 7-5 Modification wizard...........................................................................................................................7-25 Table 7-6 Rules of consistency check for ATM transport mode........................................................................7-32 Table 7-7 Rules of consistency check for IP transport mode.............................................................................7-33 Table 7-8 Process of data configuration through the CME in integrated mode.................................................7-40 Table 7-9 Data to be checked on the radio network layer..................................................................................7-59 Table 7-10 Modification wizard.........................................................................................................................7-64 Table 7-11 Description of result comparison.....................................................................................................7-71 Table 7-12 Modification wizard.........................................................................................................................7-71 Table 7-13 Rules of consistency check for ATM transport mode......................................................................7-78 Table 7-14 Rules of consistency check for IP transport mode...........................................................................7-79 Table 7-15 Shortcut menu options......................................................................................................................7-87 Table 7-16 Areas in the configuration interface...............................................................................................7-132

Issue 01 (2008-06-25)


xi


About This Document

About This Document

Purpose This document describes the WRAN CME in terms of the functions, working principles, application scenarios, and basic operations, through which the user can be familiar with the CME and able to perform data configuration.

Product Versions The following table lists the product versions related to this document. Product Name

Product Version

WRAN CME

V100R005

M2000

V200R005 V200R006 and V200R008

Intended Audience This document is intended for: l

Field engineers

l

Network operators

l

System engineers

This document assumes that the audience is familiar with the following topics: l

Architecture, principles, and hardware of the RNC

l

Architecture, principles, and hardware of the NodeB

Change History For changes in the document, refer to Changes in WRAN CME User Guide.

Organization 1 Copyright Declaration of the Third-Party Software Issue 01 (2008-06-25)


1


About This Document

This provides the copyright declaration of the third-party software. The third-party software installed on the CME server refers to Windows Server 2003, SQL Server 2000, and so on. 2 Introduction to the CME This introduces the software structure, hardware structure, and features of the WCDMA Radio Access System (WRAN) Configuration Management Express (CME). 3 Applications of the CME The CME supports initial configuration and reconfiguration. 4 Concepts of the CME This describes the concepts involved in data configuration through the CME. 5 Views of the CME Client The GUI-based CME client vividly displays the device panel, resource usage, and windows for batch configuration. 6 Installing the CME This describes how to install the server software and client software of the CME in standalone and integrated modes. 7 Operating the CME This describes the data reconfiguration process on the CME in standalone mode and integrated mode. The primary operations on the CME are also described.

Conventions 1. Symbol Conventions The following symbols may be found in this document. They are defined as follows Symbol

Description

DANGER

WARNING

CAUTION

Indicates a hazard with a high level of risk that, if not avoided, will result in death or serious injury. Indicates a hazard with a medium or low level of risk which, if not avoided, could result in minor or moderate injury. Indicates a potentially hazardous situation that, if not avoided, could cause equipment damage, data loss, and performance degradation, or unexpected results. Indicates a tip that may help you solve a problem or save your time.

TIP

Provides additional information to emphasize or supplement important points of the main text.

NOTE

2. General Conventions 2


Issue 01 (2008-06-25)


About This Document

Convention

Description

Times New Roman

Normal paragraphs are in Times New Roman.

Boldface

Names of files,directories,folders,and users are in boldface. For example,log in as user root .

Italic

Book titles are in italics.

Courier New

Terminal display is in Courier New.

3. Command Conventions Convention

Description

Boldface

The keywords of a command line are in boldface.

Italic

Command arguments are in italic.

[]

Items (keywords or arguments) in square brackets [ ] are optional.

{x | y | ...}

Alternative items are grouped in braces and separated by vertical bars.One is selected.

[ x | y | ... ]

Optional alternative items are grouped in square brackets and separated by vertical bars.One or none is selected.

{ x | y | ... } *

Alternative items are grouped in braces and separated by vertical bars.A minimum of one or a maximum of all can be selected.

[ x | y | ... ] *

Alternative items are grouped in braces and separated by vertical bars.A minimum of zero or a maximum of all can be selected.

4. GUI Conventions Convention

Description

Boldface

Buttons,menus,parameters,tabs,window,and dialog titles are in boldface. For example,click OK.

>

Multi-level menus are in boldface and separated by the ">" signs. For example,choose File > Create > Folder .

5. Keyboard Operation

Issue 01 (2008-06-25)

Convention

Description

Key

Press the key.For example,press Enter and press Tab.

Key1+Key2

Press the keys concurrently.For example,pressing Ctrl+Alt+A means the three keys should be pressed concurrently.


3


About This Document

Convention

Description

Key1,Key2

Press the keys in turn.For example,pressing Alt,A means the two keys should be pressed in turn.

6. Mouse Operation

4

Action

Description

Click

Select and release the primary mouse button without moving the pointer.

Double-click

Press the primary mouse button twice continuously and quickly without moving the pointer.

Drag

Press and hold the primary mouse button and move the pointer to a certain position.


Issue 01 (2008-06-25)


1

1 Copyright Declaration of the Third-Party Software

Copyright Declaration of the Third-Party Software This provides the copyright declaration of the third-party software. The third-party software installed on the CME server refers to Windows Server 2003, SQL Server 2000, and so on.

CAUTION l

The Windows Server 2003 and the SQL Server 2000 are products of Microsoft Corporation. See the related technical documents for details.

l

All the company names and trademarks mentioned in this declaration are properties of Microsoft Corporation.

You can install the delivery-attached third-party software (such as Windows Server 2003 and SQL Server 2000) on the CME server as licensed. Huawei Technologies Co., Ltd is not responsible for any copyright issue or conflict resulting from your unauthorized installation. The versions of the third-party software, such as Windows Server 2003 and SQL Server 2000, provided along with the CME are the latest versions issued by Microsoft. In the future, Microsoft may issue some patches or upgrade versions to solve software problems. Considering the relations between software versions, you are advised to consult the local Huawei office for technical support before patching or upgrading.

Issue 01 (2008-06-25)


1-1


2 Introduction to the CME

2

Introduction to the CME

About This Chapter This introduces the software structure, hardware structure, and features of the WCDMA Radio Access System (WRAN) Configuration Management Express (CME). The CME is an auxiliary project design tool for Radio Access System (RAN) equipment. With the Graphic User Interface (GUI), the CME provides integrated solutions for RAN data configuration, improves data configuration efficiency, and reduces daily maintenance cost. The RAN system consists of multiple Radio Network Subsystems (RNSs), each of which has one RNC and at least one NodeB. 2.1 Software Structure of the CME This describes the software structure of the CME. 2.2 Hardware Structure of the CME The hardware structure of the CME is determined by the running mode of the CME. 2.3 Features of the CME This describes the features of the CME.

Issue 01 (2008-06-25)


2-1



2.1 Software Structure of the CME This describes the software structure of the CME.

Software Components Figure 2-1 Software components of the CME

l

Operating system: You should use an appropriate operating system, based on the way to run the CME.

l

Database software: You should use appropriate database software, based on the way to run the CME.

l

Application software: upper-layer application software mandatory for the CME. It includes the CME server software and the CME client software. The application software is used to implement the functions of different logical CME entities.

Software Structure of the CME in Integrated Mode Figure 2-2 shows the software structure of the CME integrated into the M2000.

2-2


Issue 01 (2008-06-25)



Figure 2-2 Software structure of the CME in integrated mode

CME server: agency for the interaction between the CME and NEs

2.2 Hardware Structure of the CME The hardware structure of the CME is determined by the running mode of the CME. The CME hardware consists of the following components: l

CME server: It can be installed in the cabinet of the M2000 or in standalone mode. With the database software and associated applications, it implements logic processing of core data.

l

CME clients: They can be installed in distributed mode as required. With the CME client software, they provide the GUI, help the selection of NE versions, and serve as a platform of data configuration.

Running in Standalone Mode The standalone mode means that the CME is not integrated into the M2000 and not connected to the network in real time. You can directly start the CME client software for data configuration. The standalone mode is applicable to data configuration performed outside the equipment room in which the M2000 is located. Therefore, the application scenarios for the standalone CME are relatively flexible. Issue 01 (2008-06-25)


2-3



Physically, the CME server and the CME client can be installed on either the same computer or different computers. Figure 2-3 shows the position of the CME. Figure 2-3 Position of the CME in standalone mode

Running in Integrated Mode The integrated mode means that the CME is integrated into the M2000, an EMS. The CME is connected to the network in real time. You can start the CME client on the M2000 client to perform data configuration. The integrated mode is applicable to data configuration performed in the equipment room in which the M2000 is located. Physically, the CME client and the M2000 client are installed on the same computer, and the CME server is installed in the cabinet of the M2000. Figure 2-4 shows the position of the CME.

2-4


Issue 01 (2008-06-25)



Figure 2-4 Position of the CME in integrated mode

NOTE

The IP addresses of the CME server and the M2000 server are configured on the same network segment. The devices on this network segment are reachable in the presence of routes.

2.3 Features of the CME This describes the features of the CME.

Scenario-Oriented Integrated Solutions The CME supports common configuration scenarios, such as initial configuration, system expansion, network optimization, and base station reparenting. The CME can provide end-toend integrated solutions as required.

Configuration Management for Multiple RNSs of Different Versions The CME enables the NE management conversion from single-point configuration to multipoint configuration. The CME allows overall configuration management for multiple RNSs of different versions. Thus, it can be used in practical applications with NEs of different versions. Issue 01 (2008-06-25)


2-5



RNS-Based Data Management All the configuration data of the CME is saved in the database of the CME server. When the CME is integrated into the M2000, multiple planned data areas can be created for different types of RNS. In these areas, multiple engineers can work in parallel without interference to others. RNS-based data management facilitates data configuration and maintenance.

Flexible Running Modes The CME runs in standalone or integrated mode, which is specified on the basis of different scenarios.

User-Centered Design The CME supports multiple information navigation modes, such as navigation by NE, by protocol stack, and by configuration. l

In the mode of navigation by NE, the RNS navigation tree in the main window displays the RNC in an RNS and all the NodeBs and cells controlled by the RNC. You can rightclick an item to view the corresponding configuration window.

l

In the mode of navigation by protocol stack, you can view the Iub, Iu-CS, Iu-PS, and Iur protocol stacks on the CME. The protocol stacks are vivid for configuration of the interface data.

l

In the mode of navigation by configuration, you can perform data configuration through the wizard.

User-Centered Design (UCD) simplifies data configuration.

Data Consistency Guarantee of the Iub Through the Iub refreshing function and the consistency check function, the CME can guarantee the Iub data consistency, reduce the workload on manual check, improve the processing efficiency, and thus implement integrated data configuration.

Convenient Resource Management The CME enables convenient resource management, which is described as follows: l

The resource indication on the CME client shows in real time the usage of transmission resources, such as the bandwidth and physical links.

l

The device panel on the CME client shows the data configuration for the NodeB hardware and the connections between RRUs in real time.

Intelligent Data Operation During the configuration, the CME automatically operates and checks key data, which is described as follows:

2-6

l

The CME automatically calculates the key data of neighboring cells, SAAL links, IP routes, and ATM addresses. Then, the CME collects available resources, gathers them into the resource pool, and displays them on the GUI.

l

The CME automatically checks the entered data according to related rules. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd

Issue 01 (2008-06-25)

WRAN CME WRAN CME User Guide l


The CME checks data consistency and redundancy after configuration to ensure data correctness before activation.

Auxiliary Data Modification Tool The CME provides wizards for data configuration and modification, such as cell data addition and batch modification of cell radio algorithm parameters, frequencies, neighboring relationships, and global algorithm parameters. After these operations, the modification script can be exported and can take effect in different ways. Such data modification is applicable to routine maintenance and network optimization.

Base Station Reparent Tool The CME provides wizards for base station reparenting in different scenarios, such as reparenting within an RNC, reparenting between RNCs, and reparenting from one transmission mode to another. This function simplifies the maintenance during network optimization and improves the work efficiency.

Batch Script Execution Tool Through the GUI, the CME provides the data activation function in different scenarios, such as in base station reparenting. configuration This tool supports parallel execution of batch scripts, which increases the processing efficiency.

Diverse Data Sources The CME supports the data from the following sources: l

4.2 Negotiation and Planning Data File

l

4.5 RNC BAM Database

l

4.3 NodeB Template File

l

4.4 NodeB Configuration File

Multiple Types of Data for Export After data configuration, the CME can export the following files: l


l

4.4 NodeB Configuration File

l

4.6 RNC Configuration File

l


Issue 01 (2008-06-25)


2-7


3 Applications of the CME

3

Applications of the CME

About This Chapter The CME supports initial configuration and reconfiguration. 3.1 Definition of RAN Initial Configuration RAN initial configuration consists of RNC initial configuration and NodeB initial configuration. 3.2 Process of RAN Initial Configuration Initial configuration of network elements is performed at an early stage of network construction. The following takes a standalone CME as an example. 3.3 Definition of RAN Reconfiguration RAN reconfiguration is used in routine maintenance and reconfiguration of RNC and NodeB. 3.4 Process of RAN Reconfiguration When a network runs properly, data reconfiguration may be required because of capacity expansion and network optimization. The following description is deployed on the assumption that the CME integrated into the M2000. 3.5 Configuration Objects of the CME This describes the objects involved in CME-based RAN reconfiguration.

Issue 01 (2008-06-25)


3-1



3.1 Definition of RAN Initial Configuration RAN initial configuration consists of RNC initial configuration and NodeB initial configuration. RAN initial configuration refers to certain operations that are performed after the RAN hardware, which consists of at least one RNC and one NodeB, is initially installed. During RAN initial configuration, you configure data for the RAN elements based on the hardware configuration, network planning, and negotiation between network elements. Then, you export configuration files and load the files onto the RNC and NodeB through LMT or M2000. RAN initial configuration consists of the following activities: l

Adding an RNC initially

l

Adding a NodeB initially

3.1.1 Definition of RNC Initial Configuration RNC initial configuration is the process of preparing and configuring the data after the RNC hardware components are installed. The configuration is based on the RNC hardware components, network planning, and data negotiation between the RNC and other equipment. After the configuration, you can obtain an RNC initial configuration file in .txt format. 3.1.2 Definition of NodeB Initial Configuration NodeB initial configuration is the process of preparing and configuring the data after the NodeB hardware components are installed. The configuration is based on the NodeB hardware components, network planning, and data negotiation between the NodeB and other equipment. After the configuration, a data configuration file in .xml format is generated.

3.1.1 Definition of RNC Initial Configuration RNC initial configuration is the process of preparing and configuring the data after the RNC hardware components are installed. The configuration is based on the RNC hardware components, network planning, and data negotiation between the RNC and other equipment. After the configuration, you can obtain an RNC initial configuration file in .txt format. The configuration file must meet the following requirements: l

The data is intact, correct, and compatible with the physical configuration of the equipment.

3.1.2 Definition of NodeB Initial Configuration NodeB initial configuration is the process of preparing and configuring the data after the NodeB hardware components are installed. The configuration is based on the NodeB hardware components, network planning, and data negotiation between the NodeB and other equipment. After the configuration, a data configuration file in .xml format is generated. The configuration file must meet the following requirements:

3-2

l

The data is intact, correct, and compatible with the physical configuration of the equipment.

l

The Iub interface data at the transport layer is consistent with that at the RNC. This ensures normal data exchange between the NodeB and the RNC.


Issue 01 (2008-06-25)



3.2 Process of RAN Initial Configuration Initial configuration of network elements is performed at an early stage of network construction. The following takes a standalone CME as an example.

Figure of RAN Initial Configuration Process Figure 3-1 shows the process of RAN initial configuration on the CME. Figure 3-1 Process of RAN initial configuration

Description of RAN Initial Configuration Process Table 3-1 describes the process of RAN initial configuration on the CME. Table 3-1 Process of RAN initial configuration

Issue 01 (2008-06-25)

Operation

Description

Creating an RNS

Before initial configuration, you need to create an RNS, that is, to set up a workspace. For details, refer to 7.1.3 Creating an RNS.

Importing CME Files

The following files can be imported during RAN initial configuration: l


l



3-3



Operation

Description

Export files

The following files can be exported when the configuration is complete: l

NodeB configuration file: an XML file loaded onto the NodeB. For details, refer to 4.4 NodeB Configuration File.

l

RNC configuration file: a TXT file loaded onto the RNC. For details, refer to 4.6 RNC Configuration File.

Send files

The CME sends the files to the RNC LMT, NodeB LMT, or M2000, for example, through FTP or online sharing.

Load files

The CME activates the data on the existing network through the LMT.

3.3 Definition of RAN Reconfiguration RAN reconfiguration is used in routine maintenance and reconfiguration of RNC and NodeB. RAN reconfiguration involves configuring all the data of the RAN system that is in service. The RAN system consists of at least one RNC and one NodeB. RAN reconfiguration should have no or minimized impact on the on-going services. RAN reconfiguration may be required due to the following reasons: l

Network optimization Network optimization is implemented on the basis of the data collected from performance measurement or drive tests on the network in service.

l

RAN capacity expansion RAN capacity expansion enables the RAN system to provide optimized services for more users, through additional hardware or data reconfiguration on the existing network.

l

NodeB reparenting NodeB reparenting refers to the reparenting of NodeB data within an RNC or between RNCs for load balance and system expansion. NodeB data includes subrack data, subsystem data, and port data.

3.4 Process of RAN Reconfiguration When a network runs properly, data reconfiguration may be required because of capacity expansion and network optimization. The following description is deployed on the assumption that the CME integrated into the M2000.

RAN Reonfiguration Process Figure 3-2 shows the process of RAN reconfiguration on the CME that is integrated into the M2000.

3-4


Issue 01 (2008-06-25)



Figure 3-2 Process of RAN reconfiguration

Process Description Table 3-2 describes the process of RAN reconfiguration on the CME. Table 3-2 Process of RAN reconfiguration

Issue 01 (2008-06-25)

Operation

Description

Load data from the existing network.

Before reconfiguration, you need to ensure that the data in the current data area of the CME is consistent with that on the existing network. For details, refer to 7.2.4 Synchronizing with the Data on the Existing Network. If there is no information about the NE to be synchronized in the current data area, you are required to load the RNS at first. For details, refer to 7.2.2 Loading Data from the Existing Network.

Create/Open a planned data area.

Before reconfiguration, you need to create a workspace. For details, refer to 7.2.5 Creating a Planned Data Area and 7.2.6 Opening a Planned Data Area.

Reconfigure data.

Based on scenarios and requirements, reconfigure the data from the existing network. The reconfiguration scenario can be capacity expansion, network optimization, or NodeB reparenting.

Send files.

In integrated mode, the M2000 server acts as a data transmission channel to provide the activated data for the NE.

Load files.

For details, refer to 7.2.12 Activating Data.


3-5



3.5 Configuration Objects of the CME This describes the objects involved in CME-based RAN reconfiguration. Figure 3-3 shows the configuration objects. Figure 3-3 CME-based configuration objects

3-6


Issue 01 (2008-06-25)


4 Concepts of the CME

4

Concepts of the CME

About This Chapter This describes the concepts involved in data configuration through the CME. 4.1 Workspace Workspace is a space where operators can perform data configuration. 4.2 Negotiation and Planning Data File This defines the negotiation and planning data file and describes the scenarios for using the file, the method of obtaining the file, and the role of the file in the CME. 4.3 NodeB Template File This defines the NodeB template file and describes the scenarios for using the file, the method of obtaining the file, and the role of the file in the CME. 4.4 NodeB Configuration File This defines the NodeB configuration file and describes the scenarios for using the file, the method of obtaining the file, and the role of the file in the CME. 4.5 RNC BAM Database This defines the RNC BAM database and describes the scenarios for using the database, the method of accessing the database, and the role of the database in the CME. 4.6 RNC Configuration File This defines the RNC configuration file and describes the scenarios for using the file, the method of obtaining the file, and the role of the file in the CME. 4.7 CME License File This defines the CME license file and describes the licensing modes, the method of obtaining the license file, and the implementation mode.

Issue 01 (2008-06-25)


4-1



4.1 Workspace Workspace is a space where operators can perform data configuration. The minimum unit of the workspace is an RNS, which is composed of one RNC and multiple NodeBs controlled by this RNC. The CME supports management and maintenance of multiple RNSs. When the CME is integrated into the M2000, the workspace is divided into the current data area and planned data areas.

Current Data Area The current data area records the data on the existing network. It manages the configuration data of all the NEs within the RAN, which is composed of multiple RNSs. The current data area can synchronize its data with that on the existing network at default intervals. You can also perform the synchronization manually.

Planned Data Area The data in a planned data area is synchronized with that in the current data area before related data configuration. Before data activation, the planned data area functions as an offline working area. Users configure the data in their own planned data areas. Therefore, several users can work in parallel. The data on the existing network is modified only after the configured data is activated.

CAUTION To protect the system from failures, ensure that one object is not modified in several planned data areas at the same time.

4.2 Negotiation and Planning Data File This defines the negotiation and planning data file and describes the scenarios for using the file, the method of obtaining the file, and the role of the file in the CME.

Definition The negotiation and planning data file includes a set of negotiated and planned data that is obtained during site preparation. It aims to simplify data configuration. The negotiation and planning data file is of the following types: l

Radio network planning data file, including cell data, neighboring cell data, GSM cell data, and neighboring relations between cells

l

Iub/Iu/Iur interface negotiation data file, including the transport network negotiation data of the Iub, Iu, and Iur interfaces

The file provides templates in .xls format for negotiated and planned data. 4-2


Issue 01 (2008-06-25)



Application Scenario When using the CME to perform RAN data configuration, import the negotiation and planning data files into the CME to generate configuration data. The negotiation and planning data file can be exported as an XLS file for data modification.

Obtaining Method All the negotiation and planning data files are provided with the CME software. The file is available at CME installation directory\WRANCMEV100R005\import. The negotiation and planning data file is named in the form of WCDMA RNCversion number Interface Data.xls or WCDMA RNCversion number Radio Network Planning Data.xls, for example, WCDMA RNC2.10 Iu and Iur Interface Data.xls.

Role in the CME The negotiation and planning data file can be a data source for data configuration on the CME.

4.3 NodeB Template File This defines the NodeB template file and describes the scenarios for using the file, the method of obtaining the file, and the role of the file in the CME.

Definition A NodeB template file contains a set of recommended data that is predefined with common configuration types, demodulation modes, and Iub transmission modes to simplify NodeB data configuration. The NodeB template file contains a large number of default parameters. The NodeB template file is of the following two types: l

Template file provided with the CME software. It cannot be deleted.

l

User-defined template file. After configuring the NodeB data, you can save the data configuration as a template, which serves as a data source for future data configuration.

WARNING The default NodeB template provided by the CME cannot be modified.

Application Scenario During NodeB initial configuration on the CME, import a NodeB template file according to the NodeB type. The NodeB template file facilitates NodeB data configuration.

Obtaining Method The NodeB template file is provided with the CME software. The file is available at CME installation directory\WRANCMEV100R005\template\NodeB. Issue 01 (2008-06-25)


4-3



The NodeB template file is named in the form of transport protocol type_demodulation mode_sector quantity_frequency quantity_transmit diversity mode.xml, for example, ATM_2-Channels Demodulation_3_1_Transmitter Non_diversity.xml. You can also name a NodeB template file in your own way. You can reconfigure a NodeB template file and export it. For details, refer to 7.3.3.2 Exporting a NodeB Template File.

Role in the CME The NodeB template file can be a data source for NodeB data configuration on the CME.

4.4 NodeB Configuration File This defines the NodeB configuration file and describes the scenarios for using the file, the method of obtaining the file, and the role of the file in the CME.

Definition A NodeB configuration file contains a complete set of NodeB configuration data for proper operation of the NodeB. The NodeB configuration file, also called NodeB XML file, is saved in .xml format.

Application Scenario The NodeB configuration file is used in the following scenarios: l

Export the NodeB configuration file to the NodeB LMT after the RAN configuration is complete on the CME. Then load the file onto the NodeB and validate the file.

l

Before reconfiguring the RAN on the CME, import the NodeB configuration file to the CME server to synchronize the NodeB data in the CME with that on the existing network.

Obtaining Method You can obtain the NodeB configuration file by exporting all the NodeB data from the CME or obtain the file from the NodeB LMT.

Role in the CME The NodeB configuration file can be loaded to the NodeB. The file can be a data source for NodeB configuration on the CME.

4.5 RNC BAM Database This defines the RNC BAM database and describes the scenarios for using the database, the method of accessing the database, and the role of the database in the CME.

Definition The RNC BAM database is a location for storing the RNC operation and maintenance data in the existing network. 4-4


Issue 01 (2008-06-25)



Application Scenario When the CME runs in standalone mode, you can import the data from the RNC BAM database for further data reconfiguration.

Obtaining Method Through the local area network, synchronize data on the CME server with the data in the BAM database.

Role in the CME The RNC BAM database can be a data source for RAN reconfiguration on the CME.

4.6 RNC Configuration File This defines the RNC configuration file and describes the scenarios for using the file, the method of obtaining the file, and the role of the file in the CME.

Definition An RNC configuration file contains a complete set of RNC configuration data for specific RNC operations. The RNC configuration file, also called MML script, is saved in .txt format. Depending on scenarios, the RNC configuration file is of the following two types: l

RNC initial configuration file: contains all MML scripts to be run during initial configuration.

l

RNC reconfiguration file: contains a type of script to be run during reconfiguration. The script may involve the reconfiguration of the data on the RNC side, such as the NodeB data, cell data, algorithm parameters, or ATM traffic data.

Application Scenario The scenarios for using the RNC data configuration file are as follows: l

The RNC initial configuration file is used for RAN initial configuration.

l

The RNC reconfiguration file is used for RAN reconfiguration.

Obtaining Method Export the RNC configuration file after data configuration on the CME.

Role in the CME The RNC configuration file can be exported from the CME and loaded onto the RNC.

Issue 01 (2008-06-25)


4-5



4.7 CME License File This defines the CME license file and describes the licensing modes, the method of obtaining the license file, and the implementation mode.

Definition l

A license is an authorization agreement between the supplier and the customer in terms of the application scope, functions, and service life of products.

l

Physically, a license is a license certificate and a license file.

l

Applications decide to enable or disable functional modules according to the license file.

Licensing Modes of the CME The license file of the CME is used in the following scenarios: l

For the CME that is integrated into the M2000, the M2000 server performs license control. The license file of the M2000 is located in a specific directory on the M2000 server. When you start the CME client on the M2000 client, the system automatically reads the license file and acquires the control items.

l

For the standalone CME, the license is client-specific. The license file is named WRANCME License.DAT and located in the system directory under the installation directory of the CME. When you start the CME client, the system automatically reads the local license file and acquires the control items.

Obtaining Method The license file is obtained according to the procedure worked out by the supplier and the customer.

Implementation Method Under the control of the CME license file, the functions of the CME are categorized into the following types: l

GUI-based basic functions of WRAN data configuration

l

Enhanced functions of WRAN transport network configuration

l

Enhanced functions of WRAN radio network configuration

l

Check of consistency in WRAN configuration data

l

WRAN NodeB reparenting

Based on the license, the CME controls to enable or disable functions. Without a license file, the CME performs only basic functions. With a license file, the CME controls and manages functions as negotiated between the supplier and the customer.

4-6


Issue 01 (2008-06-25)


5 Views of the CME Client

5

Views of the CME Client

About This Chapter The GUI-based CME client vividly displays the device panel, resource usage, and windows for batch configuration. 5.1 Main Window The main window of the CME client varies according to the running mode of the CME. The CME can be standalone or integrated into the M2000. 5.2 NodeB Device Panel The CME can display the physical structure of the configured NodeB through the device panel. 5.3 NodeB Network Topology The CME can display the network topology of RF modules of the NodeB. Through this function, you can obtain their relative positions. 5.4 Resource Usage Display The resource usage display of the CME client dynamically shows the quantities of used, spare, and total resources. 5.5 Window for Batch Addition Batch configuration is applicable to configuration of a large amount of typical data. 5.6 Shortcut Keys When you configure data on the CME, you can use the shortcut keys for easy operation.

Issue 01 (2008-06-25)


5-1



5.1 Main Window The main window of the CME client varies according to the running mode of the CME. The CME can be standalone or integrated into the M2000.

1. Main Window with No RNS Open (Standalone CME) After the CME client starts, the main window with no RNS open is displayed, as shown in Figure 5-1. Figure 5-1 Main window with no RNS open (standalone CME)

Table 5-1 describes the elements shown in the figure. Table 5-1 Elements in the window

5-2

Element

Description

Menu bar

Consists of the menus used to perform basic RNS operations and system operations and to get help information.

RNS navigation tree

Displays all the RNSs in the RAN, the version of each RNC, and all the NodeBs and cells.

Welcome pane

Displays software declaration.


Issue 01 (2008-06-25)



2. Main Window with an RNS Open (Standalone CME) When an RNS is created or an existing RNS is opened, the main window is displayed as shown in Figure 5-2. Figure 5-2 Main window with an RNS open (standalone CME)

Table 5-2 describes the elements shown in the figure. Table 5-2 Elements in the window Element

Description

Menu bar

Consists of the menus used to perform basic RNS operations and system operations, to use tools and wizards, and to get help information.

RNS navigation tree

Displays all the RNSs in the RAN, the version of each RNC, and all the NodeBs and cells. The navigation tree supports only browsing and window switching. You can right-click a NodeB or cell to configure the object in the corresponding window.

Issue 01 (2008-06-25)

Configuration object pane

Displays network elements and interfaces ready for configuration.

Configuration task pane

Displays all configuration tasks for a network element or an interface.


5-3



3. Main Window with an RNS Open (CME Integrated into the M2000) The main window of the CME that is integrated into the M2000 has a menu for operations in the current data area or a planned data area, as shown in Figure 5-3. Figure 5-3 Main window with an RNS open (CME integrated into the M2000)

5.2 NodeB Device Panel The CME can display the physical structure of the configured NodeB through the device panel.

Procedure

Step 1 Click in the CME configuration object pane, and then click NodeB CM Express in the configuration task pane. The NodeB CM Express window is displayed. Step 2 Click 5-4.

5-4

. The Physical NodeB Basic Information window is displayed, as shown in Figure


Issue 01 (2008-06-25)



Figure 5-4 Selecting a physical cell

Step 3 Click

. The NodeB Equipment Layer window is displayed.

Step 4 Select the Device Panel tab. The NodeB device panel is displayed, as shown in Figure 5-5.

Issue 01 (2008-06-25)


5-5



Figure 5-5 Device Panel of the BTS3836A

----End

5.3 NodeB Network Topology The CME can display the network topology of RF modules of the NodeB. Through this function, you can obtain their relative positions.

5-6


Issue 01 (2008-06-25)



Network Topology Figure 5-6 NodeB Network Topology

Modules (Including Boards) The network topology can show the following RF modules: l

BBU

l

EBOI

l

RRU

l

RHUB

l

Pico RRU

Relevant Parameters The position of an RF module is identified by the following three parameters: l

Floor: identifies the floor where the module is located.

l

Horizontal: Each floor is divided into 1000 parts horizontally, and a mark is applied every 100 parts, as shown inFigure 5-6.

l

Vertical: Each floor is divided into 1000 parts vertically, and a mark is applied every 100 parts, as shown in Figure 5-6.

The position of a module is determined by the position of the upper left corner of the module.

Prerequisites The position of each RF module is set. Issue 01 (2008-06-25)


5-7



Procedure

1.

in the CME configuration object pane, and then click NodeB CM Click Express in the configuration task pane. The NodeB CM Express window is displayed.

2.

Click

3.

Select a physical NodeB, and then click as shown in Figure 5-6.

4.

To modify the position of an NE, select it and then click Set.

5.

Click Find. You can locate a module by floor number, subrack number, board number, or RRU link number.

. The Physical NodeB Basic Information window is displayed. . The Topological View window is displayed,

To save the changed position, click Save. As long as you do not click Save after you drag an NE, the position will not be changed.

5.4 Resource Usage Display The resource usage display of the CME client dynamically shows the quantities of used, spare, and total resources. Figure 5-7 shows the resource usage display of the CME client. Figure 5-7 Resource usage display

Table 5-3 describes the elements shown in the figure. Table 5-3 Elements on the resource usage display

5-8

No.

Element

Description

1

Spare

Indicates remaining resources.

2

Used

Indicates used resources.

3

Total

Indicates total resources.

4

Tx Bandwidth

Indicates the transmit bandwidth.


Issue 01 (2008-06-25)



No.

Element

Description

5

Rx Bandwidth Indicates the receive bandwidth.

6

Unit

Indicates resource usage in cell/s or kbit/s.

7

Interface board type and slot No.

Indicates the type of board that carries the link and the number of the slot that hosts the board.

8

Physical bearer type

Identifies the type and number of the bearer for the physical link.

9

Realtime flag

Available for you to set whether to display the bandwidth usage in real time.

5.5 Window for Batch Addition Batch configuration is applicable to configuration of a large amount of typical data. Figure 5-8 shows an example window for batch adding AAL2 Path links. Figure 5-8 Window for batch adding AAL2 Path links

Table 5-4 describes the elements shown in the figure.

Issue 01 (2008-06-25)


5-9



Table 5-4 Elements in the window for batch adding AAL2 Path links No.

Element

Description

1

Configuration objects

Shows the objects for batch configuration.

2

Added object area

Shows links that are already added.

3

Buttons

Used to add, remove, or set up links.

4

Resource pool

Shows the links that are available during the batch configuration.

5

Physical link data pane

Shows data about physical links, such as the bearer type and link resource usage.

5.6 Shortcut Keys When you configure data on the CME, you can use the shortcut keys for easy operation. Table 5-5 describes the shortcut keys commonly used in data configuration on the CME. Table 5-5 Shortcut keys

5-10

Shortcut Key

Function

Ctrl+A

Select all the entries from a resource pool.

Ctrl+click

Select multiple entries from a resource pool.

Ctrl+Delete

Delete an entry.

Ctrl+Home

Select the first entry.

Ctrl+End

Select the last entry.

Ctrl+D

Copy the previous cell.

Ctrl+S

Add 1 to the value in the previous cell.

Ctrl+Up

Select the first entry.

Ctrl+Down

Select the last entry.

ESC

Exit from an editing state, or restore the system to the previous state when an error occurs.

F2

Enter the editing state.

Insert

Add an entry.

Page Up

Select the first entry on a page.

Page Down

Select the last entry on a page.

Shift+Tab

Select the previous entry.


Issue 01 (2008-06-25)


Issue 01 (2008-06-25)


Shortcut Key

Function

Shift+Down

Select multiple entries from a resource pool.

Tab

Select the next entry.


5-11


6 Installing the CME

6

Installing the CME

About This Chapter This describes how to install the server software and client software of the CME in standalone and integrated modes. 6.1 Installing the CME Server (Standalone) This describes server computer requirements of the standalone CME and the procedure for installing the server software. 6.2 Installing the CME Server (Integrated) This describes server computer requirements of the CME integrated into the M2000 and the procedure for installing the server software. 6.3 Installing and Uninstalling the CME Client This describes the computer requirements of the CME client and the procedures for installing and uninstalling the CME client software. 6.4 IP Port Configuration Requirements This specifies the requirements of the CME in standalone and integrated modes for IP port configuration.

Issue 01 (2008-06-25)


6-1



6.1 Installing the CME Server (Standalone) This describes server computer requirements of the standalone CME and the procedure for installing the server software. 6.1.1 Computer Requirements of the CME Server (Standalone) This describes the hardware and software requirements of the CME server used in the standalone CME. 6.1.2 Installing MSDE 2000 SP4 (Standalone) This describes how to install MSDE 2000 SP4, a type of database software of the CME server.

6.1.1 Computer Requirements of the CME Server (Standalone) This describes the hardware and software requirements of the CME server used in the standalone CME.

Hardware Requirements Table 6-1 describes the hardware requirements of the CME server. Table 6-1 Hardware requirements of the CME server Item

Minimum Configuration

Recommended Configuration

CPU

PIII 1.0 GHz

Pentium 4 CPU 2.4 GHz

Memory

256 MB

512 MB

Hard disk

10 GB

40 GB

Drive

CD-ROM drive

CD-ROM drive

Network adapter

Ethernet adapter

Ethernet adapter

Video adapter

VGA

VGA or super VGA

NOTE

When a CME client and a CME server are installed on the same computer, you are advised to use hardware configurations that meet the Recommended Configuration requirements.

Software Requirements Table 6-2 describes the software requirements of the CME server.

6-2


Issue 01 (2008-06-25)



Table 6-2 Software requirements of the CME server Software


Operating system

l

If the operating system is Microsoft Windows XP, then the database software is MSDE 2000 SP4 and the patch is Service Pack 1 or later.

l

If the operating system is Microsoft Windows Server 2003, then the database software is SQL Server 2000 with Service Pack 4 or later and the patch of the operating system is Service Pack 1 or later.

Default language of the operating system

English (United States)

Database software

MSDE 2000 SP4/SQL Server 2000

NOTE

To guarantee the stable running of the CME server software, the operating system of English version is recommended.

6.1.2 Installing MSDE 2000 SP4 (Standalone) This describes how to install MSDE 2000 SP4, a type of database software of the CME server.

Prerequisite l

The installation disk is ready.

l

The hardware configuration of the CME server meets the requirements. For details of the requirements, refer to 6.1.1 Computer Requirements of the CME Server (Standalone).

Procedure Step 1 Check the software configuration on the computer. Check the computer for the following software: l

MSDE 2000 SP4

l

SQL Server 2000

If any database software is installed on the server, check the software configuration, and then uninstall the incompatible database software, if any. Step 2 Install the database software. To install MSDE 2000 SP4, perform the following steps: 1.

Log in to the operating system as administrator.

2.

Check whether the following requirements are fulfilled:

Issue 01 (2008-06-25)


6-3


6 Installing the CME l

The installation directory of MSDE 2000 SP4 does not exist, or the directory exists but is left empty.

l

The remaining space on the installation disk is not less than 2 GB.

Go to Step 2.3 if the preceding requirements are fulfilled. Otherwise, install the software in another path. 3.

Run the install.bat program.

4.

Restart the computer after the installation.

Step 3 Check the installation results. Check the status area at the lower right corner of the screen after the computer restarts. If any of the program icons listed in Table 6-3 appears, it is an indication that MSDE 2000 SP4 is installed successfully. Table 6-3 MSDE 2000 SP4 icons Program Icon

Description Indicates that the database is in progress. Indicates that the database service is suspended. Indicates that the database service is stopped.

----End

6.2 Installing the CME Server (Integrated) This describes server computer requirements of the CME integrated into the M2000 and the procedure for installing the server software. 6.2.1 Computer Requirements of the CME Server (Integrated) This describes the hardware and software requirements of the CME server used in the CME that is integrated into the M2000. 6.2.2 Installing the Operating System For the CME that is integrated into the M2000, you should install the operating system Windows Server 2003 on the CME server. 6.2.3 Installing the Database Software For the CME that is integrated into the M2000, you should install the database software SQL Server 2000 on the CME server. 6.2.4 Configuring Initialization Parameters for the CMEServer Service The CMEServer service is installed on the M2000 along with the software components of the M2000 server. But the initialization parameters for this component should be configured manually. 6.2.5 Installing the Application Software For the CME that is integrated into the M2000, you should install the associated application software on the CME server. 6-4


Issue 01 (2008-06-25)



6.2.1 Computer Requirements of the CME Server (Integrated) This describes the hardware and software requirements of the CME server used in the CME that is integrated into the M2000.

Hardware Requirements The CME server uses the HP server. Table 6-4 describes the hardware requirements of the CME server. Table 6-4 Hardware requirements of the HP server Item

Standard Configuration

CPU

Xeon DualCore Woodcrest 1.6 GHz or above

Memory

4 GB (4 x 1 GB)

Hard disk

2 x 146 GB 2.5" SFF SAS

Floppy disk drive

None

Drive

DVD drive

Network adapter

2 x Integrated 1000M NIC

Monitor

None

CAUTION For the hardware installation of the CME Server, refer toM2000 Hardware Installation Guide.

Software Requirements

CAUTION The CME server requires the following software: l

Operating system

l

Database software

l

Application: CME Application Service

Issue 01 (2008-06-25)


6-5



CAUTION You should also install CMEServer on the common layer at the M2000 server. For details about how to install M2000 Server Application, refer to the installation guide for M2000 documents. Table 6-5 describes the software requirements of the CME server. Table 6-5 Software requirements of the CME server Software


Operating system

Microsoft Windows Server 2003 with Service Pack 1 or later versions



Database software

SQL Server 2000 with Service Pack 4 or later versions

6.2.2 Installing the Operating System For the CME that is integrated into the M2000, you should install the operating system Windows Server 2003 on the CME server. 6.2.2.1 Configuring the Disk Arrays Before installing the operating system, you need to set the server-connected physical disk in the disk arrays as a logical disk. 6.2.2.2 Installing Windows Server 2003 This describes how to install the Windows Server 2003 operating system on the CME server. 6.2.2.3 Checking the Version Information of Windows Server 2003 This describes how to check the version information of Windows Server 2003 installed on the CME server. 6.2.2.4 Teaming the Ethernet Adapters To enhance reliability, the CME server is installed with two Ethernet adapters to communicate with the M2000 server. This procedure describes how to team the Ethernet adapters.

Configuring the Disk Arrays Before installing the operating system, you need to set the server-connected physical disk in the disk arrays as a logical disk.

Prerequisite The hardware of the HP server is ready.

6-6


Issue 01 (2008-06-25)



Context NOTE

This task takes P400 as an example. The user should operate based on the practical application.

Procedure Step 1 Start the server. Then, the server starts self-check and displays a dialog box, as shown in Figure 6-1. The dialog box for configuring the disk arrays are titled HP Smart Array. Figure 6-1 Entering the disk array configuration dialog box

Step 2 Press F8. A dialog box is displayed, as shown in Figure 6-2.

Issue 01 (2008-06-25)


6-7



Figure 6-2 Creating a logical disk

Step 3 Select Create Logical Drive and then press Enter. A dialog box is displayed, as shown in Figure 6-3.

6-8


Issue 01 (2008-06-25)



Figure 6-3 Selecting a RAID mode

Step 4 Select a disk from the left part and select RAID 1 from the right part. Step 5 Press Enter to confirm the operations and then press F8 to save the settings. ----End

Installing Windows Server 2003 This describes how to install the Windows Server 2003 operating system on the CME server.

Prerequisite l

The hardware is ready. The CME server and M2000 server are located on the same network segment. The servers are reachable for the clients through routes.

l

The CD-ROM drive is set as the first boot device of the CME server.

l

The HP boot disk is ready. It is delivered with the CME.

l

The Windows Server 2003 Enterprise Edition setup disk is ready. It is delivered with the CME.

Context The following methods are available for installing the operating system on the CME server: l

Booting from the CD-ROM that is delivered with the HP device This method is recommended.

l

Issue 01 (2008-06-25)

Installing the operating system and then driving it from the HP boot disk Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd

6-9



CAUTION l

The first method requires that the operating system setup disk does not incorporate multiple Windows versions.

l

The operating system setup disk and Windows Server 2003 Service Pack 1 must be available.

This procedure takes booting from the HP disk as an example.

Procedure Step 1 Insert the SmartStart installation disk into the driver. According to the screen information, select F1 to continue. Step 2 Select the current version of SmartStart. Then, wait for initialization. Step 3 In the language specifying dialog box, select english and click Continue. The license confirmation dialog box is displayed. Step 4 Click agree and then click Continue. The Smart Start Home dialog box is displayed, as shown in Figure 6-4. Figure 6-4 Setting the working mode

Step 5 Set the working mode to Deploy Server, and then click Continue. The Hardware Configuration dialog box is displayed, as shown in Figure 6-5.

6-10


Issue 01 (2008-06-25)



Figure 6-5 Configuring the disk arrays

Step 6 Click Continue. The Operating System Selection is displayed, as shown in Figure 6-6.

Issue 01 (2008-06-25)


6-11



Figure 6-6 Selecting the operating system

Step 7 Select Microsoft Windows Server 2003 Enterprise Edition and then click Continue. The Operating System Media Source dialog box is displayed, as shown in Figure 6-7.

6-12


Issue 01 (2008-06-25)



Figure 6-7 Selecting the disk partition

Step 8 Select CD-ROM and then click Continue. The Disk Partitioning Options dialog box is displayed, as shown in Figure 6-8.

Issue 01 (2008-06-25)


6-13



Figure 6-8 Specifying the size of the disk partition

Step 9 Check to use the default disk partitioning properties, and then click Continue. The Operating System Configuration Information dialog box is displayed, as shown in Figure 6-9.

6-14


Issue 01 (2008-06-25)



Figure 6-9 Configure Operating System information

Step 10 Enter the user name, organization name, product key of the operating system, and license type (Per Seat), and then click Continue. The SNMP Configuration dialog box is displayed.

Issue 01 (2008-06-25)


6-15



Figure 6-10 Configure SNMP

Step 11 Select No, click Continue. The Proliant Support Pack dialog box is displayed. Figure 6-11 Select PSP mode

6-16


Issue 01 (2008-06-25)



Step 12 Use the default value, and then click Continue. The Ready To Install dialog box is displayed. Figure 6-12 Ready to install

Step 13 Click Continue, and wait while the system is performing disk partitioning. This process takes about 30 seconds. After the partitioning, the SmartStart disk is ejected from the driver. Step 14 According to the prompt, insert the operating system installation disk. The SmartStart then copies the information on the hard disk. After the copying, the installation disk is ejected from the drive, and the CME server restarts automatically. The server enters the standard installation process, during which it may restart three or four times. The following standard installation operations are not described in this document. ----End

Checking the Version Information of Windows Server 2003 This describes how to check the version information of Windows Server 2003 installed on the CME server.

Procedure Step 1 On the CME server, choose Start > Control Panel > System . Step 2 In the displayed dialog box, click the General tab. Step 3 Check whether Microsoft Windows Server 2003, Enterprise Edition, and Service Pack 1 are displayed under System. Issue 01 (2008-06-25)


6-17



If...

Then...

Microsoft Windows Server 2003, Enterprise Edition, and Service Pack 1 are displayed,

Windows Server 2003 and Windows Server 2003 Service Pack 1 are installed successfully.

Microsoft Windows Server 2003, Enterprise Edition, and Service Pack 1 are not displayed,

Windows Server 2003 is not installed successfully. Reinstall it by referring to 6.2.2.2 Installing Windows Server 2003.

----End

Teaming the Ethernet Adapters To enhance reliability, the CME server is installed with two Ethernet adapters to communicate with the M2000 server. This procedure describes how to team the Ethernet adapters.

Prerequisite l

Windows Server 2003 is installed.

l

The driver for the Ethernet adapter is installed from an HP boot disk.

l

The NCU software in the HP tool disk is installed.

Procedure Step 1 Team the Ethernet adapters. 1.

6-18

in the status area at the lower right of Windows, which is the shortcut Double-click icon of Network Configuration Utility. Click OK in the prompt. The HP Network Configuration Utility Properties dialog box is displayed, as shown in Figure 6-13.


Issue 01 (2008-06-25)



Figure 6-13 Selecting the Ethernet adapters

2.

Select the two Ethernet adapters, and then click Team to team the Ethernet adapters, as shown in Figure 6-14.

Figure 6-14 Teaming the Ethernet adapters

Issue 01 (2008-06-25)


6-19



3.

Click OK.

Step 2 Set an IP address for the Ethernet adapters. 1.

Open the window for network connections. An additional Ethernet adapter icon is displayed in the window.

2.

Right-click the icon of the new Ethernet adapter of which the Device Name is HP Network Team, and then select Properties from the shortcut menu. The Local Area Connection Properties dialog box is displayed.

3.

Click Internet Protocol (TCP/IP) and then click Properties. A dialog box for setting the TCP/IP properties is displayed.

4.

Enter the IP address according to network planning.

----End

6.2.3 Installing the Database Software For the CME that is integrated into the M2000, you should install the database software SQL Server 2000 on the CME server. 6.2.3.1 Installing SQL Server 2000 This describes how to install SQL Server 2000. 6.2.3.2 Installing SQL Server 2000 Service Pack 4 This task describes how to install SQL Server 2000 Service Pack 4. 6.2.3.3 Checking the Version Information of SQL Server This describes how to check the version information of SQL Server 2000 Service Pack 4 installed on the CME server. 6.2.3.4 Checking the Operation of the SQL Server Database This describes how to check the operation of the SQL Server database.

Installing SQL Server 2000 This describes how to install SQL Server 2000.

Prerequisite l

The setup disk of Microsoft SQL Server 2000 Standard Edition.

l

The configurations of the CME server meet the requirements described in Table 6-6.

Table 6-6 CME server configuration checklist

6-20

Item

Method

Expectation

Operating system

Check the version of the operating system and that of the patch. For details, refer to 6.2.2.3 Checking the Version Information of Windows Server 2003.

The operating system is Microsoft Windows Server 2003, Standard Edition. The patch is Service Pack 1.


Issue 01 (2008-06-25)



Item

Method

Expectation

Microsoft Internet Explorer

Open the Internet Explorer, choose Help > About Internet Explorer , and then view the version information of the Internet Explorer.

The version of the Internet Explorer is 6.0 or later.

Context

CAUTION l

The system can run properly only after the patch is installed.

l

The password to be specified during the installation can contain only letters and numbers. Any space or any other special character is not allowed. If such an invalid character is included, the installation may fail. NOTE

l

Read the guide on the screen during the installation.

l

For more information, refer to the installation helps on the setup disk.

l

It is recommended that SQL Server 2000 be installed in C:\Program Files\Microsoft SQL Server \ and ensure that MSSQL\BACKUP exists under the installation directory of SQL Server 2000.

Procedure Step 1 Log in to the operating system as an administrator. Step 2 Check whether there are icons of the event browser and registry browser in the status area. If there are the icons, quit the event browser and the registry browser. Step 3 Insert the setup disk of SQL Server 2000 into the CD-ROM drive. Step 4 The disk automatically starts the installation. If not, run the Autorun.exe file under the root directory to start the installation. Then, a selection dialog box is displayed. Step 5 Click SQL Server 2000 Components. The component selection interface is displayed. Step 6 Click Install Database Server. The information dialog box is disaplayed as shown in Figure 6-15.

Issue 01 (2008-06-25)


6-21



Figure 6-15 information dialog box

Step 7 Click Continue. The welcome dialog box is displayed. Step 8 Click Next. A dialog box is displayed, as shown in Figure 6-16. Figure 6-16 Entering a computer name

Step 9 Leave the default setting Local Computer unchanged, and then click Next. A dialog box is displayed, as shown in Figure 6-17.

6-22


Issue 01 (2008-06-25)



Figure 6-17 Selecting an installation option

Step 10 Click Create a new instance of SQL Server, or install Client Tools, and then click Next. A dialog box is displayed, as shown in Figure 6-18. Figure 6-18 Entering the user information

Step 11 Enter the user name and company name, and then click Next. Issue 01 (2008-06-25)


6-23



Step 12 Read carefully the agreement, and then click Yes. A dialog box is displayed, as shown in Figure 6-19. Figure 6-19 Entering the CD-Key

Step 13 Enter the CD-Key, and then click Next. A dialog box is displayed, as shown in Figure 6-20.

6-24


Issue 01 (2008-06-25)



Figure 6-20 Defining the installation

Step 14 Click Server and Client Tools, and then click Next. A dialog box is displayed, as shown in Figure 6-21. Figure 6-21 Entering an instance name

Issue 01 (2008-06-25)


6-25



Step 15 Select the Default check box, and then click Next. A dialog box is displayed, as shown in Figure 6-22. Figure 6-22 Selecting a setup type

Step 16 Click Custom, leave the default settings of Destination Folder unchanged, and then click Next. A dialog box is displayed, as shown in Figure 6-23. Figure 6-23 Selecting components

6-26


Issue 01 (2008-06-25)



Step 17 Leave the default settings unchanged, and then click Next. A dialog box is displayed, as shown in Figure 6-24. Figure 6-24 Setting service accounts

Step 18 Click Use the same account for each service. Auto start SQL Server Service, click Use the Local System account under Service Settings, and then click Next. A dialog box is displayed, as shown in Figure 6-25.

Issue 01 (2008-06-25)


6-27



Figure 6-25 Setting the authentication mode

Step 19 Click Mixed mode (Windows Authentication and SQL Server Authentication), enter and confirm the password, and record the password. Click Next. A dialog box is displayed, as shown in Figure 6-26.

6-28


Issue 01 (2008-06-25)



Figure 6-26 Setting the collation

Step 20 Click Collation designator and click Chinese_PRC in the drop-down list. Select the Binary check box. Then, click Next. A dialog box is displayed, as shown in Figure 6-27.

Issue 01 (2008-06-25)


6-29



Figure 6-27 Setting network libraries

Step 21 Enter values in the Named Pipe name and Port number boxes. (The default named pipe name is recommended. The port number is 57001.) Then, click Next. A dialog box is displayed, as shown in Figure 6-28. Figure 6-28 Starting copying files

6-30


Issue 01 (2008-06-25)



Step 22 Click Next. A dialog box is displayed, as shown in Figure 6-29. Figure 6-29 Choosing a licensing mode

Step 23 Select the Per Seat for check box, set the number of devices to 25, and then click Next. The setup program creates directories and copies files. When the copying is complete, a dialog box is displayed, as shown in Figure 6-30. NOTE

If the setup program detects that some required files are being used by other programs, a dialog box is displayed, prompting whether to quit these programs or not. Click Next.

Issue 01 (2008-06-25)


6-31



Figure 6-30 Setup complete

Step 24 Click Finish. NOTE

If the setup program detects that some required files are being used by other programs, a dialog box prompting whether to restart the computer is displayed after the setup is complete. In this case, you must restart the computer to validate the settings.

Step 25 Choose Start > All Programs to check whether there is a Microsoft SQL Server program group in the menu.

6-32

If...

Then...

There is a Microsoft SQL Server program group in the menu and the program group contains the following items:

The installation of SQL Server 2000 is successful.

l

Query Analyzer

l

Import and Export Data

l

Service Manager

l

Server Network Utility

l

Client Network Utility

l

Books Online

l

Enterprise Manager

l

Profiler

l

Configure SQL XML Support in IIS


Issue 01 (2008-06-25)



If...

Then...

There is no Microsoft SQL Server program The installation of SQL Server 2000 fails. group in the menu, You are advised to uninstall SQL Server 2000 and restart the CME server. Follow the preceding procedure to reinstall the software. ----End

Installing SQL Server 2000 Service Pack 4 This task describes how to install SQL Server 2000 Service Pack 4.

Prerequisite l

The compressed patch SQL2000-KB884525-SP4-x86-ENU.exe of SQL Server 2000 Service Pack 4 is ready.

l

You are logged in to Windows Server 2003 as a system administrator.

l

SQL Server 2000 is installed.

Context Decompress the setup file before installing SQL Server 2000 Service Pack 4.

Procedure Step 1 Run SQL2000-KB884525-SP4-x86-ENU.exe. A dialog box is displayed, as shown in Figure 6-31.

Issue 01 (2008-06-25)


6-33



Figure 6-31 Selecting an installation folder

Step 2 Use the default path C:\SQL2KSP4\ and then click Next to start the decompression. Step 3 In the dialog box displayed after the decompression, click Finish. Step 4 Run the file Setup.bat in C:\SQL2KSP4. The welcome window is displayed. Step 5 Click Next. Step 6 Read the software license agreement, and then click Yes. The Instance Name dialog box is displayed. Step 7 Click Next. A dialog box is displayed, as shown in Figure 6-32.

6-34


Issue 01 (2008-06-25)



Figure 6-32 Connecting to the SQL server

Step 8 Select The SQL Server system administrator login information (SQL Server authentication), enter the password of the user sa as recorded in Step 19, and then click Next. A dialog box is displayed, as shown in Figure 6-33.

Issue 01 (2008-06-25)


6-35



Figure 6-33 Setting the backward compatibility

Step 9 Select Upgrade Microsoft Search and apply SQL Server 2000 SP4 (required), and then click Continue. A dialog box is displayed, as shown in Figure 6-34.

6-36


Issue 01 (2008-06-25)



Figure 6-34 Setting whether to report errors to Microsoft

Step 10 Click OK. The Start Copying Files dialog box is displayed. Step 11 Click Next. When the copying is complete, a dialog box is displayed, as shown in Figure 6-35. Figure 6-35 Confirming the setup

Step 12 Click OK. A dialog box is displayed, as shown in Figure 6-36.

Issue 01 (2008-06-25)


6-37



Figure 6-36 Confirming the setup

Step 13 Select No, I will restart my computer later, and then click Finish. ----End

Checking the Version Information of SQL Server This describes how to check the version information of SQL Server 2000 Service Pack 4 installed on the CME server.

Procedure Step 1 On the CME server, choose Start > All Programs > Microsoft SQL Server > Query Analyzer. A dialog box is displayed, as shown in Figure 6-37.

6-38


Issue 01 (2008-06-25)



Figure 6-37 Connecting to the SQL Server

Step 2 Enter a user-defined server name in the SQL Server box. Enter the login password in the Password box. Then, click OK. Step 3 In the SQL Query Analyzer window, enter the commands xp_msver and select SERVERPROPERTY('Edition'). Note that there is a space preceded by select. Press F5 to run the SQL script. If...

Then...

ProductVersion is 8.00.2039 and product The version of SQL Server 2000 is correct type is Standard Edition, and the service pack is installed successfully. ProductVersion is 8.00.2223 and product The version of SQL Server 2000 Service Pack 4 is correct and the service pack is type is Standard Edition, installed successfully. The version information is incorrect,

It is recommended that the following steps be performed: 1. Uninstall SQL Server 2000. 2. Restart the CME server. 3. Strictly follow the steps described in 6.2.3.1 Installing SQL Server 2000 to reinstall the software.

----End

Checking the Operation of the SQL Server Database This describes how to check the operation of the SQL Server database.

Issue 01 (2008-06-25)


6-39



Procedure Step 1 Double-click the icon of SQL Server Service Manager, that is, in the status area of the CME server. The SQL Server Service Manager window is displayed. Step 2 Click SQL Server Agent in the Services drop-down list. If...

Then...

A window as shown in Figure 6-38 is displayed,

You can infer that the SQL Server 2000 service manager is operational.

A window as shown in Figure 6-39 is displayed,

You can infer that the SQL Server 2000 service manager is not running. Click Start/ Continue. The manager refreshes services.

Figure 6-38 SQL Server Service Manager in operation

Figure 6-39 SQL Server Service Manager out of operation

----End 6-40


Issue 01 (2008-06-25)



6.2.4 Configuring Initialization Parameters for the CMEServer Service The CMEServer service is installed on the M2000 along with the software components of the M2000 server. But the initialization parameters for this component should be configured manually.

Prerequisite l

The software components, including the CMEServer service, are installed on the M2000 server. For details about this operation, refer to Installing the M2000 Server Application in the M2000 Software Installation Guide.

l

The default installation path is /opt/OMC/. If this path is changed, the related commands in the following steps are subject to the actual installation path.

Procedure Step 1 Log in to the M2000 server as user root, and run the following command: # . /opt/OMC/ svc_profile.sh Step 2 Run the following command to enter the /opt/OMC/bin directory.# cd /opt/OMC/bin Step 3 Run the following config_cme_service.sh script: # ./config_cme_service.sh The following information is displayed: ************************************************************** 1) Config the CMEServer parameters for WRAN CME. 2) Config the CMEServer parameters for GBSS CME. 0) Quit the Operation menu. Please choose a number[ 0 ~ 2 ]:1 **************************************************************

Step 4 Enter 1. The CME starts configuring parameters for the CMEServer service. Step 5 In the prompting window, enter y to proceed. The following information is displayed: ************************************************************** 1) Modify the configuration parameters of CmeServer. 2) Initialize the configuration parameters of CmeServer. !!!Only for the first time to run CmeServer that you need to initialize the parameters. 3) Disable the CmeServer. !You can chose 1 to enable the CmeServer. 0) Quit the Operation menu.. Please choose a number[ 0 ~ 2 ]:2 **************************************************************

Step 6 Enter 2. The CME starts initializing all the running parameters for the CME. The following information is displayed:

Issue 01 (2008-06-25)


6-41



CAUTION When the M2000 version is V200R005, the following parameters are required: ************************************************************** Please input OMC Database server [default:SYB]: Please input OMC Database user name [default:sa]: Please input OMC Database password [default:emsems]: Please input CME DBServer host IP[default:10.121.72.215]: Please input CME DBServer port [default:57001]: Please input CME DB user name [default:sa]: Please input CME DB password [default:cme]: Please input the RNS-timing-upload-interval: [default:180 s, must between 60 and 300]: Please input the max-simultaneously-upload-RNS numbers: [default:5, must between 5 and 20 ]: Please input the RNS-upload-operation timeout interval: [default:7200 s, must between 600 and 10800]: **************************************************************

CME DB server host IP refers to the IP address of the server installed with the SQL Server. Port refers to the port number of the SQL Server. The default port number is 57001, which can be modified as required.

CAUTION When the M2000 version is V200R006 or V200R008, the following parameters are required: ************************************************************** Please input OMC Database server [default:SYB]: Please input OMC Database user name [default:sa]: Please input OMC Database password [default:emsems]: Please input CME DBServer host IP[default:10.121.72.215]: Please input CME DBServer port [default:57001]: Please input CME DB user name [default:sa]: Please input CME DB password [default:cme]: **************************************************************

Step 7 Check and enter the parameters. The following information is displayed: ************************************************************** The CME database host IP is 10.121.71.171 The CME database host port is 57001 The CME database user name is sa The CME database password is cme The RNS-timing-refresh-interval are 180 seconds The RNS-upload-operation timeout interval are 7200 seconds The max-simultaneous-RNS numbers are 5 entries Are you sure to continue? [y/n]:y **************************************************************

Step 8 Enter y. The initialization parameter configuration succeeds if the following information is displayed: ************************************************************** 1) Modify the configuration parameters of CmeServer. 2) Initialize the configuration parameters of CmeServer. !!!Only for the first time to run CmeServer that you need to initialize the

6-42


Issue 01 (2008-06-25)



parameters. 3) Disable the CmeServer. !You can chose 1 to enable the CmeServer. 0) Quit the Operation menu. Please choose a number[ 0 ~ 3 ]:0 **************************************************************

Step 9 Enter 0.

CAUTION When the M2000 version is V200R005, the initialization parameter configuration is complete. When the M2000 version is V200R006 or V200R008, the following information is displayed: ************************************************************** 1) Config the CMEServer parameters for WRAN CME. 2) Config the CMEServer parameters for GBSS CME. 0) Quit the Operation menu. Please choose a number[ 0 ~ 2 ]:0 **************************************************************

Step 10 Enter O to exit. ----End

6.2.5 Installing the Application Software For the CME that is integrated into the M2000, you should install the associated application software on the CME server.

Prerequisite l

The application software CMEServer of the M2000 server is installed. For details, refer to the relevant user guide.

l

The hardware configuration of the CME server meets the requirements. For details of the requirements, refer to 6.2.1 Computer Requirements of the CME Server (Integrated).

l

The operating system and the database software are installed on the server.

Context You should install CME Application Service on the server.

Procedure Step 1 Find the setup.exe file from the software package of CME Application Service, and then run the file. The welcome dialog box is displayed. Step 2 Click Next. The License Agreement dialog box is displayed. Step 3 Click Yes. The Customer Information dialog box is displayed. Step 4 Enter the user information and the CD-Key CME. You can try a maximum of three CD-Keys. After three failed attempts, the installation program is automatically quit. Issue 01 (2008-06-25)


6-43



Step 5 Click Next. The SQL Server Information dialog box is displayed. Step 6 Enter the local password for logging in to the database. You can try a maximum of three passwords. After three failed attempts, the installation program is automatically quit. Step 7 Click Next. The FTP Server Client Information dialog box is displayed. Step 8 Enter the IP address of the FTP server, the user name, and the password. The IP address of the FTP server is that of the M2000 server. The user name and password of the FTP server are those defined in the M2000. If the M2000 server uses the highly-available Watchman, that is, the dual-server system, the IP address of the M2000 should be the service IP address on the active server. You can try the configuration information for a maximum of three times. After three failed attempts, the installation program is automatically quit. Step 9 Click Next. The Choose Destination Location dialog box is displayed. Step 10 Specify the installation path, and then click Next. The Start Copying Files dialog box is displayed. Step 11 Check and confirm the installation information, and then click Next. The CME starts installing the database. When the installation is complete, the InstallShield Wizard Complete dialog box is displayed. Step 12 Click Finish. The application is installed. ----End

6.3 Installing and Uninstalling the CME Client This describes the computer requirements of the CME client and the procedures for installing and uninstalling the CME client software. 6.3.1 Computer Requirements of the CME Client This describes the hardware and software requirements of the computer installed with the CME client software. 6.3.2 Installing the CME Client Software This describes how to install the CME client software. 6.3.3 Uninstalling the CME Client Software This describes how to uninstall the CME client software.

6.3.1 Computer Requirements of the CME Client This describes the hardware and software requirements of the computer installed with the CME client software.

Hardware Requirements Table 6-7 describes the hardware requirements of the CME client. 6-44


Issue 01 (2008-06-25)



Table 6-7 Hardware requirements of the CME client Hardware

Minimum Configuration


CPU

Pentium III CPU 866 MHz

Pentium 4 CPU 1.6 GHz

Memory

256 MB

512 MB

Hard disk

10 GB

40 GB

Drive

CD-ROM drive

CD-ROM drive

Network adapter

Ethernet adapter

Ethernet adapter

Video adapter

VGA

VGA or super VGA

NOTE

l

You should set the screen resolution to 1024 x 768 pixels to optimize the screen display.

l

When the CME client is integrated with the M2000 client, the computer must meet the hardware requirements of the M2000 client and those of the CME client.

Software Requirements Table 6-8 describes the software requirements of the CME client. Table 6-8 Software requirements of the CME client Hardware


Operating system

The operating system can be one of the following: l

Microsoft Windows 2000 Professional with Service Pack 4 or later versions

l

Microsoft Windows XP Professional with Service Pack 1 or later versions



Default language of Microsoft Office


NOTE

The operating system and Microsoft Office support only Chinese and English. In other languages, the stable operation of the CME cannot be guaranteed.

6.3.2 Installing the CME Client Software This describes how to install the CME client software. Issue 01 (2008-06-25)


6-45



Prerequisite l

The software package is ready.

l

The hardware configuration of the client meets the requirements. For details of the requirements, refer to 6.3.1 Computer Requirements of the CME Client.

Context The software version of the CME client should be V100R005.

Procedure Step 1 Make preparations for the installation. Before installing the CME client software, perform the following operations: l

Ensure that the computer ready for software installation meets the requirements described in 6.3.1 Computer Requirements of the CME Client.

l

Get the client software installation program ready.

l

Check that the version of the client software to be installed is correct. NOTE

If the CME client is integrated with the M2000, ensure that the M2000 client is installed.

Step 2 Check whether the CME client software is installed on the computer. Uninstall the CME client software of incorrect version. Step 3 Install the CME client software. To install the CME client software, perform the following steps:

6-46

1.

Double-click setup.exe. In the displayed dialog box, specify the destination folder for extracting the files. Then, the CME system starts initialization. After the initialization is complete, a welcome dialog box is displayed.

2.

Read the displayed information. Then, click Next. The license agreement is displayed, as shown in Figure 6-40.


Issue 01 (2008-06-25)



Figure 6-40 License agreement

3.

Issue 01 (2008-06-25)

If you accept the terms in the license agreement, select I accept the terms of the license agreement and then click Next. A dialog box requiring customer information is displayed, as shown in Figure 6-41. If you do not accept the terms in the license agreement, click Cancel.


6-47



Figure 6-41 Entering customer information

4.

Enter the user name, company name, and CME serial number. Then, click Next. A dialog box is displayed for specifying the destination folder, as shown in Figure 6-42. Figure 6-42 Specifying the destination folder

6-48


Issue 01 (2008-06-25)


5.


Select a destination folder, and then click Next. A confirm dialog box is displayed, as shown in Figure 6-43. If required, click Change to change the software installation path. Figure 6-43 Confirming the installation

6.

Read through the prompt information, and then click Install. The software is automatically extracted and installed in the destination folder. When the installation is complete, a dialog box is displayed.

7.

Click Finish.

8.

(Optional) Install the CME license file. For details, refer to 4.7 CME License File.

9.

Choose Start > All Programs > Huawei WRAN CM Express > V100R005 > WRAN CME . If the CME starts normally, the CME client software is installed successfully. Alternatively, you can choose Tools > WRAN CMEV15 on the M2000 client. If the CME starts normally, the CME client software is installed successfully.

----End

6.3.3 Uninstalling the CME Client Software This describes how to uninstall the CME client software.

Prerequisite The CME client is exited.

Procedure l

Issue 01 (2008-06-25)

To uninstall the CME client software through the uninstall program, perform the following steps: Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd

6-49



1.

Choose Start > All Programs > Huawei WRAN CM Express > Uninstall WRAN CME. The CME begins to collect data. When the collection is complete, an uninstall wizard is displayed, as shown in Figure 6-44. Figure 6-44 Uninstalling the CME client software

l

l

2.

Click Next. A message is displayed for confirmation.

3.

Click Yes. The CME client software begins to be uninstalled. If you do not want to uninstall the CME client software now, click No to go back to the uninstall wizard.

4.

When the CME client software is uninstalled, the finish dialog box is displayed. Click Finish.

To uninstall the CME client software through the control panel, perform the following steps: 1.

Choose Start > Control Panel.

2.

Double-click the Add/Remove Programs icon. The Add/Remove Programs window is displayed. Then select the CME client software.

3.

Click Add/Remove. A message is displayed for confirmation.

4.

Click Yes. The CME client software is uninstalled.

To check that the CME client software is uninstalled, perform the following steps: 1.

Check that the CME shortcut icon is removed from the desktop.

2.

Check that the CME option is removed from the Start > All Programs menu.

3.

Check that the CME option is removed from the Add/Remove Programs window, which is displayed after you click Add/Remove Programs on the control panel.

----End 6-50


Issue 01 (2008-06-25)



6.4 IP Port Configuration Requirements This specifies the requirements of the CME in standalone and integrated modes for IP port configuration.

IP Port Configuration Requirements When the CME is integrated into the M2000, you need to configure the related access control policy on the firewall, if the firewall separates the CME client from the M2000 and CME servers. The firewall should allow access through the ports on the M2000 server side, on the CME server side, and on the CME client side. No firewall is configured between the M2000 server and the CME server.

Issue 01 (2008-06-25)

SN

Connection

Port Type

Port No.

Description

1

From the CME client to the M2000 server

TCP

20 and 21

FTP access

55001

CMEServer port

2

From the CME client to the CME server

TCP

57001

Database server port

3

From the RNC to the CME client

TCP

7001

If the CME runs in standalone mode, the RNC provides the CME with the port for data configuration.


6-51


7 Operating the CME

7

Operating the CME

About This Chapter This describes the data reconfiguration process on the CME in standalone mode and integrated mode. The primary operations on the CME are also described. 7.1 Data Configuration Process in Standalone Mode This describes the process of data reconfiguration and activation on the standalone CME. 7.2 Data Configuration Process in Integrated Mode This describes the process of data reconfiguration and activation on the CME that is integrated into the M2000. 7.3 Managing Data Files The CME supports different data sources. Importing data or files to the CME facilitates data configuration and enhances configuration flexibility. 7.4 Comparing Radio Algorithm Parameters This describes how to compare the values of global algorithm parameters or cell algorithm parameters with the baseline values. The results of the comparison can help you identify the modified parameters. 7.5 Backing Up and Restoring an RNS This describes how to back up the RNS database by using the backup function of the CME or by importing the BCP file to the CME. In the case of data error or system failure, you can use the backup file to restore the RNS database. 7.6 Searching and Browsing Data The CME supports panorama browsing and searching of data. You can browse the configuration data of various objects, such as the NodeB status, cell status, Iub interface in different transmission modes, neighboring cell information, and neighboring relations between cells.

Issue 01 (2008-06-25)


7-1


7 Operating the CME

7.1 Data Configuration Process in Standalone Mode This describes the process of data reconfiguration and activation on the standalone CME.

Data Configuration Process Figure 7-1 shows the process of data configuration through the standalone CME. Figure 7-1 Data configuration process

7-2


Issue 01 (2008-06-25)


7 Operating the CME

Description of Data Configuration Table 7-1 Process of data configuration through the CME in standalone mode Operation

Description

Start CME client

For details, refer to 7.1.1 Starting the CME Client.

Open RAN

For details, refer to 7.1.2 Opening the RAN.

Create an RNS

Before the RAN reconfiguration, open or create an RNS project. To stop the reconfiguration temporarily, save the data and then exit the RNS project. For details, refer to 7.1.3 Creating an RNS and 7.1.4 Opening an RNS.

Synchronize data

Before the data reconfiguration, synchronize the CME database with the corresponding RNC data. For details, refer to 7.1.5 Synchronizing RNC Data. Synchronize with the NodeB data on the existing network by loading the NodeB configuration file onto the BAM FTP server and then importing the file to the current RNS. Through the wizards provided by the CME, perform the initial configuration and export the data modification file. For details, refer to RNC Initial Configuration Guide and NodeB Initial Configuration Guide.

Perform initial configuration

You can check data during the reconfiguration, as listed below: Check the RNC data by referring to: l

7.1.6.1.2 Checking RNC Data Consistency

l

7.1.6.1.4 Checking RNC Data Redundancy

Check the NodeB data by referring to:

Reconfigure data

l

7.1.6.2.1 Checking Iub Interface Data Consistency (Optional)

l

7.1.6.2.2 Checking NodeB Data Integrity

Through the wizards provided by the CME, reconfigure common objects in batches and export the data modification file. For details, refer to RAN Reconfiguration Guide (CMEBased). You can check data during the reconfiguration, as listed below: Check the RNC data by referring to: l


l



Issue 01 (2008-06-25)

l


l



7-3


7 Operating the CME

Operation

Description

Activate data

After data reconfiguration on the standalone CME, run the MML or XML scripts on the RNC or NodeB LMT.

7.1.1 Starting the CME Client This describes how to start a standalone CME client and how an NMS user remotely accesses the CME client. 7.1.2 Opening the RAN After the CME is started in standalone mode, you need to open the RAN for creating a project and configuring the data. 7.1.3 Creating an RNS This describes how to create an RNS before data configuration in standalone mode. 7.1.4 Opening an RNS You need to open an appropriate RNS to continue an incomplete data configuration task. 7.1.5 Synchronizing RNC Data This describes how to synchronize the CME database with the RNC data. 7.1.6 Checking Data This describes how to check global data and Iub interface data. You need to check data integrity and redundancy after data configuration or reconfiguration. 7.1.7 Closing an RNS You can close an RNS to suspend the configuration. 7.1.8 Deleting an RNS You can delete an obsolete RNS. 7.1.9 Exiting the CME Client After you exit the CME client, the CME client is disconnected from the CME server.

7.1.1 Starting the CME Client This describes how to start a standalone CME client and how an NMS user remotely accesses the CME client.

Prerequisite l

The CME software is installed.

l

The CME server is started.

l

The license file is obtained and is named WRANCME License.DAT under the system directory in the installation path.

l

In remote access mode, you must log in to the M2000 as a user that is already created in the NMS user group on the M2000 client. For details, refer to Creating a Northbound User. NOTE

The remote access mode is an optional mode, used only in the case of RAN sharing.

7-4


Issue 01 (2008-06-25)


7 Operating the CME

Context l

Through the remote connection to the CME client, a user can reconfigure the data on the existing network when the M2000 is unavailable.

l

The remote access mode is applicable only for the NMS users whose telecom operator information, such as the MCC, MNC, and telecom operator index, exist on the CME client.

l

Start the standalone CME client.

Procedure 1.

Choose Start > All Programs > Huawei WRAN CM Express > V100R005 > WRAN CME , or double-click the shortcut icon of the CME on the desktop. The Login dialog box is displayed.

2.

Click OK. If you have a license file, the CME license description dialog box is displayed, as shown in Figure 7-2. For the standalone CME, no information in the Login dialog box requires to be configured, and you can log in to the CME using a default account, that is, administrator. If you do not have a license file, an associated message is displayed. Figure 7-2 Reading the license information

l

(Optional) Start the CME client remotely. 1.

Double-click the shortcut icon of the CME client. The Login dialog box is displayed, as shown in Figure 7-3. Figure 7-3 Logging in to the CME

Issue 01 (2008-06-25)


7-5


7 Operating the CME

2.

Click Remote.

3.

Enter the user authority information, that is, the user name and password. The user authority information should be already defined in the M2000.

4.

Click ... to set the IP address of the M2000 server.

5.

Click OK. After the authentication and license check, the user can log in to the CME client.

----End

7.1.2 Opening the RAN After the CME is started in standalone mode, you need to open the RAN for creating a project and configuring the data.

Prerequisite The CME client is started.

Procedure Step 1 Choose System > Open RAN. The Open RAN dialog box is displayed, as shown in Figure 7-4. Figure 7-4 Opening the RAN

Step 2 Select the CME server from the drop-down list in the Open RAN dialog box, and click OK to open the RAN. If no server is registered, go to Step 3 to configure one. Otherwise, this procedure ends. Step 3 Click Config in the Open RAN dialog box. The CME Server Info Registration dialog box is displayed. Step 4 Click Add. The CME Server Info dialog box is displayed, as shown in Figure 7-5.

7-6


Issue 01 (2008-06-25)


7 Operating the CME

Figure 7-5 Setting the parameters of the CME server

Step 5 Set the following parameters of the CME server: l

Name: user-defined CME server name

l

IP Address: IP address of the CME server

l

User Name: user name for logging in to the CME server. The initial value is sa.

l

Password: password for logging in to the CME server. The initial value is sql.

l

Port: port number. The default port number is 1433.

Step 6 Click OK to return to the CME Server Info Registration dialog box. Step 7 Click Close to return to the Open RAN dialog box. Select the server, and then click OK to open the RAN.

CAUTION If the CME is already upgraded, for example, from V100R005C01B010 to V100R005C01B020, a dialog box is displayed after you click OK in the Open RAN dialog box. The dialog box asks you whether to delete the projects created on the CME of the earlier version. If the data configuration tasks of all the projects created on the old version are complete, you are advised to delete all these projects and then create an RNS on the new version and synchronize the data in the RNS with that on the existing network. ----End

7.1.3 Creating an RNS This describes how to create an RNS before data configuration in standalone mode.

Prerequisite l

The CME client is started.

l

7.1.2 Opening the RAN is complete.

Issue 01 (2008-06-25)


7-7


7 Operating the CME

Procedure Step 1 In the RAN navigation tree, right-click RAN, and then select Add RNS from the shortcut menu. The Add RNS dialog box is displayed, as shown in Figure 7-6. Figure 7-6 Creating an RNS on a standalone CME

Step 2 Set related parameters. 1.

In the RNS Id text box, enter a customized ID of the RNS.

2.

In the RNC Version drop-down list, select a version of the RNC.

3.

In the NodeB Versions area, select one or more types of NodeB to be created under the RNC.

Step 3 Click OK. The CME starts creating the RNS. The created RNS is displayed in the RAN navigation tree. ----End

7.1.4 Opening an RNS You need to open an appropriate RNS to continue an incomplete data configuration task.

Prerequisite

7-8

l


l

No RNS is open on the CME client.

l

The RNS to be opened exists in the CME database. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd

Issue 01 (2008-06-25)


7 Operating the CME

Procedure In the main window of the CME, right-click the RNS to be opened, and choose Open RNS on the shortcut menu. ----End

7.1.5 Synchronizing RNC Data This describes how to synchronize the CME database with the RNC data. 7.1.5.1 Synchronizing Data with the RNC BAM Database This describes how to import the data from the RNC BAM database to the RNS project on the standalone CME. 7.1.5.2 Synchronizing Data with the RNC Data (bcp) This describes how to synchronize the data on the standalone CME with the data in the RNC BAM database by importing the data backup file, also called the BCP file, of the BAM database when the CME fails to be connected to the BAM server.

Synchronizing Data with the RNC BAM Database This describes how to import the data from the RNC BAM database to the RNS project on the standalone CME.

Prerequisite l

7.1.4 Opening an RNS is performed.

l

The client of the RNS is connected to the RNC BAM.

Procedure Step 1 Choose Tools > Synchronize RNC in the main window. The Select Bam dialog box is displayed, as shown in Figure 7-7. Figure 7-7 Selecting a BAM

Step 2 Click Config. The Bam Server Info Registration dialog box is displayed, as shown in Figure 7-8.

Issue 01 (2008-06-25)


7-9


7 Operating the CME

Figure 7-8 Registering the information of the BAM

Step 3 Click Add. The Bam Server Info dialog box is displayed, as shown in Figure 7-9. Figure 7-9 Configuring the information of the BAM

Step 4 Enter the name and IP address of the active BAM in the Name and IP Address boxes respectively, and enter the port number (7001 by default) in the Port box. Then click OK to return to the Bam Server Info Registration dialog box. Step 5 Click Close to return to the Select Bam dialog box. Then select the configured BAM, and then click OK. The CME starts synchronizing data with the RNC BAM database.

CAUTION Before the CME synchronizes data with the BAM, a message is displayed for your confirmation. The message indicates that the current data in the CME will be deleted and the deletion cannot be rolled back. Only one version of CME can be synchronized with a BAM at a time. Step 6 When the progress indicator shows 100%, the data synchronization window is automatically closed and the current RNS is open. The data synchronization is complete. ----End

Synchronizing Data with the RNC Data (bcp) This describes how to synchronize the data on the standalone CME with the data in the RNC BAM database by importing the data backup file, also called the BCP file, of the BAM database when the CME fails to be connected to the BAM server. 7-10


Issue 01 (2008-06-25)


7 Operating the CME

Prerequisite l

You have logged in to the M2000 client.

l

7.1.1 Starting the CME Client is complete.

l

7.1.4 Opening an RNS is complete.

Context The BCP file is generated on the M2000 side. It is the data source for this procedure.

Procedure Step 1 On the M2000 client, click

to open the command execution window.

Step 2 From the left navigation tree, select the RNC with which the CME is synchronized, and then run the EXP CFGDATA command to export a backup file. Set MOC ID to ALL. The default name of the exported file is CMECfgSyncView.zip. Step 3 Log in to the BAM FTP server and download the file onto the computer where the CME client is installed. When the RNC version is V200Rxxx, the default file path and file name is /BAM/VersionA/ FTP/ExportCMESyncView/CMECfgSyncView.zip. When the RNC version is V100Rxxx, the default file path and file name is /BAM/FTP/ ExportCMESyncView/CMECfgSyncView.zip. Step 4 Choose Tools > Synchronize RNC with BCP File. A dialog box is displayed. Step 5 Select the backup file. The CME starts importing the file. When the progress reaches 100%, the window for data synchronization is automatically closed and the current RNS project is open. The data synchronization with the RNC BAM database is complete. ----End

7.1.6 Checking Data This describes how to check global data and Iub interface data. You need to check data integrity and redundancy after data configuration or reconfiguration. 7.1.6.1 Checking RNC Data This describes how to check RNC data consistency and redundancy. 7.1.6.2 Checking NodeB Data This describes how to check NodeB data integrity and how to check Iub interface data consistency.

Checking RNC Data This describes how to check RNC data consistency and redundancy. 7.1.6.1.1 Rules of Data Consistency Check Issue 01 (2008-06-25)


7-11


7 Operating the CME

This describes how to check data integrity of a single RNC or multiple RNCs and how to check data consistency on the radio network layer. 7.1.6.1.2 Checking RNC Data Consistency This describes how to check RNC data integrity and how to check data consistency of the radio network layer. The inconsistent data can be loaded onto network elements and validated before the network elements start up and run properly. 7.1.6.1.3 Checking Data Consistency of Multiple RNCs This describes how to check data integrity of multiple RNCs and how to check data consistency on the radio network layer. The inconsistent data can be loaded onto network elements and validated before the network elements start up and run properly. 7.1.6.1.4 Checking RNC Data Redundancy The redundant data is physical bearer data that is obsolete. The redundancy check helps clear redundant data to lighten the load. It also helps you ensure that obsolete data is deleted after data modification.

?.1. Rules of Data Consistency Check This describes how to check data integrity of a single RNC or multiple RNCs and how to check data consistency on the radio network layer. The check items are as follows: l

Global location information –

l

l

l

7-12

LAC, RAC, URA, and SAC

Basic information of the RNC –

OSP

–

Clock source and working mode

–

CN domain data

Data of the transport network user plane and control plane on the Iub, Iur, Iu-CS, Iu-PS, and Iu-BC interfaces –

NCP and CCP

–

AAL2 adjacent node

–

AAL2 path

–

AAL2 route

–

MTP3b signaling link set

–

MTP3b signaling link

–

MTP3b route

–

Physical link for carrying each of the SAAL link, IPoA PVC, an AAL2 path

–

DSP of IUCS or IUCS_ALCAP type

Cell data and neighboring relation at the radio network layer, including the consistency of the cell parameters, cell names, NRNC IDs, and GSM cells and also the unidirectional or bidirectional neighboring relations Data to be checked is listed in Table 7-2.


Issue 01 (2008-06-25)


7 Operating the CME

Table 7-2 Data to be checked on the radio network layer Data

Description

NRNC Cell

l

Check Existence of NRNCCELL: After the reparenting, the NRNC cells configured by a third party may not exist on the NRNCs. In this case, the CME checks whether the involved RNCs exist and provides a wizard for changing the ownership of the NRNC cells. This wizard guides you to move the NRNC cells to other RNC and exports the modified MML script.

l

Check CellNameConflict: The CME checks whether the names of the cells and NRNC cells under the current RNC are in conflict with the names of the cells configured with the Iub interface under other RNCs. After the check, the CME provides a modification wizard and generates an MML script. To modify the name of a cell under an NRNC, you need to exit the current RNC and open the NRNC.

l

Check Consistency of NRNCCELL: Based on the cell ID, the CME checks whether the data of a cell under an RNC is consistent with the data of the same cell under another RNC. The data includes the cell name, frequency, and scrambling code. After the check, the CME provides a modification wizard and generates an MML script. If the frequency is changed, the CME can automatically adjust the neighboring relations between cells.

l

Check GSMCELL Consistency: If the MCC, MNC, CID, and LAC of each GSM cell configured on the local RNC are consistent with those configured on other RNCs, the CME checks the consistency of other data and displays the inconsistent data.

l

Check GSMCELL Frequency: The CME checks whether the frequency of a GSM cell in the current RNS adheres to the rules.

GSM Cell

The CME does not provide a modification wizard.

Issue 01 (2008-06-25)


7-13


7 Operating the CME

Data

Description

Neighborin g Relations

l

Check TwinCell Neighboring Reflexivity: The CME checks whether the cells controlled by the same NodeB are configured with the bidirectional inter-frequency neighboring relations. Through the modification wizard, the user can delete the corresponding neighboring relation and export the modified MML script.

l

Check Total Number of Intra and Inter Neighboring Links for Each Cell: The CME checks whether the number of cells that are configured with intra-frequency and inter-frequency neighboring relations to a target cell exceeds the maximum value. The user can set the maximum value. Through the modification wizard, the user can delete the corresponding neighboring relation and export the modified MML script.

l

Check Total Number of Intra Neighboring Links for Each Cell: The CME checks whether the number of cells that are configured with intra-frequency neighboring relations to a target cell exceeds the maximum value. The user can set the maximum value. Through the modification wizard, the user can delete the corresponding neighboring relation and export the modified MML script.

l

Check Total Number of Inter Neighboring Links for Each Cell: The CME checks whether the number of cells that are configured with inter-frequency neighboring relations to a target cell exceeds the maximum value. The user can set the maximum value. Through the modification wizard, the user can delete the corresponding neighboring relation and export the modified MML script.

l

Check Total Number of Intra Neighboring Links with Sib11 Usage for Each Cell: When the SIB11 delivering indication (SIB11Ind) is set to TRUE, that is, when the neighboring relation is delivered in the SIB11, the CME checks whether the number of the intra-frequency neighboring relations configured for a target cell exceeds the maximum value. The user can set the maximum value. Through the modification wizard, the user can delete the corresponding neighboring relation and export the modified MML script.

l

Check Total Number of Inter Neighboring Links with Sib11 Usage for Each Cell: When the SIB11 delivering indication (SIB11Ind) is set to TRUE, that is, when the neighboring relation is delivered in the SIB11, the CME checks whether the number of the inter-frequency neighboring relations configured for a target cell exceeds the maximum value. The user can set the maximum value. Through the modification wizard, the user can delete the corresponding neighboring relation and export the modified MML script.

l

Check Unidirectional Intra Neighboring Relations: The CME checks the cells configured with the unidirectional intra-frequency neighboring relations. Through the modification wizard, the system automatically adjusts the neighboring relation to bidirectional neighboring relation. For the inconsistent parameter configuration between cells, the system adjustment is as follows: –

7-14

If the cell frequencies are inconsistent, the system adjusts the cell frequencies based on the source cell frequency, and then determines


Issue 01 (2008-06-25)


7 Operating the CME

Data

Description whether the frequency of the neighboring cells is the same as that of the current cell. If the frequencies are the same, the neighboring relation is not changed. If the frequencies are different, the system adjusts the neighboring relation to inter-frequency neighboring relation. –

l

If the parameters other than cell frequency are inconsistent, the system adjusts the parameters based on the source cell parameters.

Check Unidirectional Inter Neighboring Relations: The CME checks the cells configured with the unidirectional inter-frequency neighboring relation. Through the modification wizard, the system automatically adjusts the neighboring relation to bidirectional neighboring relation. For the inconsistent parameter configuration between cells, the system adjustment is as follows: –

If the cell frequencies are inconsistent, the system adjusts the cell frequencies based on the source cell frequency, and then determines whether the frequency of the neighboring cells is the same as that of the current cell. If the frequencies are different, the neighboring relation is not changed. If the frequencies are the same, the system adjusts the neighboring relation to intra-frequency neighboring relation.

–


?.2. Checking RNC Data Consistency This describes how to check RNC data integrity and how to check data consistency of the radio network layer. The inconsistent data can be loaded onto network elements and validated before the network elements start up and run properly.

Prerequisite 7.1.4 Opening an RNS is complete.

Context Rules of RNC data check, refer to7.1.6.1.1 Rules of Data Consistency Check.

Procedure Step 1 Choose Tools > Preferences. The Preferences dialog box is displayed, as shown in Figure 7-10.

Issue 01 (2008-06-25)


7-15


7 Operating the CME

Figure 7-10 Specifying check rules

Step 2 Set the check items: l

In the Check Categories field, select check items. In the Check Rules field, select check sub-items. Select the fault level on the right part: Major, Warning, or Error.

l

When multiple users work in different planned data areas in parallel, set the concurrence control switch in the Concurrence Setting tab page. If this switch is enabled, the CME can automatically assign IDs for some configuration objects to avoid data conflict in different planned data areas.

l

If the Neighboring Relations option is selected, set the maximum number of neighboring relations of each type in the Set Maximum of UMTS neighboring links tab page.

Step 3 Select check sub-items and then click OK to return to the main window. Step 4 Choose Tools > Sanity Check > Consistency . After the check is finished, the Check Consistency window is displayed, as shown in Figure 7-11.

7-16


Issue 01 (2008-06-25)


7 Operating the CME

Figure 7-11 Checking data consistency

Step 5 View un-configured data and inconsistent data. l

The check results of all levels are displayed by default.

l

: displays the result of Warning level.

l

: displays the result of Major level.

l l

: displays the result of Error level. Recheck: When Auto Recheck is not selected, you should manually click this button to refresh the check results.

Step 6 Double-click a data item. Modify the data in the corresponding data configuration window or through the wizard. The following takes the wizard of modifying an NRNC cell as an example. 1.

Issue 01 (2008-06-25)

Double-click the data item to be modified. A modification wizard is displayed, as shown in Table 7-3.


7-17


7 Operating the CME

Table 7-3 Modification wizard Check Items

Wizard Description

Operation Description

Whether the source cell of an NRNC cell exists

A welcome dialog box is displayed.

a. Click Next. The Please modify the NRNC ID dialog box is displayed, as shown in Figure 7-12. b. Specify the NewNRNCID of the neighboring cell.

Check whether the cell name conflicts with others.

An object selection dialog box is displayed, as shown in Figure 7-13. The options are as follows: l Modify Cell Name l Modify NRNC ID

a. Select Modify Cell Name and click Next. The Please modify the Cell name dialog box is displayed, as shown in Figure 7-14.


a. Click Next. The Please modify the Cell name dialog box is displayed, as shown in Figure 7-14.

a. Select Modify NRNC ID and click Next. The Please modify the NRNC ID dialog box is displayed, as shown in Figure 7-12. b. Specify the NewNRNCID of the neighboring cell.

b. Enter the cell name in the Cell_Name field. Whether the data of the NRNC cells configured on the current RNC is consistent with the data of the source cells or NRNC cells configured on other RNCs.

7-18


a. Click Next. The Please select reference cell dialog box is displayed, as shown in Figure 7-15. b. Select a reference cell.


Issue 01 (2008-06-25)


7 Operating the CME

Figure 7-12 Modifying the NRNC of the neighboring cell

NOTE

Specify the NRNC ID of the neighboring cell.

Figure 7-13 Selecting the objects to be modified

Issue 01 (2008-06-25)


7-19


7 Operating the CME

Figure 7-14 Modifying the cell name

NOTE

Enter the cell name in the Cell_Name field.

Figure 7-15 Selecting a reference cell

7-20


Issue 01 (2008-06-25)


7 Operating the CME NOTE

The CME displays the data of the cells controlled by other RNCs that have the same parameters, except for NRNC_ID and NCell_Id, as the current RNC. If there are multiple such cells, select any one of them as the reference cell.

2.

Modify the data item, and then click Next. The MML Export dialog box is displayed, as shown in Figure 7-16. Figure 7-16 Export the MML script

3.

Specify a path for storing the MML script, and then click Next. The export progress is displayed.

4.

After the export is finished, a dialog box is displayed. Click Finish to end the modification of the neighboring cell.

Step 7 Repeat Step 6 if you want to configure any more data. ----End

?.3. Checking Data Consistency of Multiple RNCs This describes how to check data integrity of multiple RNCs and how to check data consistency on the radio network layer. The inconsistent data can be loaded onto network elements and validated before the network elements start up and run properly.


Context For details about rules of data check for multiple RNCs, refer to 7.1.6.1.1 Rules of Data Consistency Check. Issue 01 (2008-06-25)


7-21


7 Operating the CME

Procedure Step 1 Choose System > RAN Consistency Check. The RAN Consistency Check window is displayed, as shown in Figure 7-17. Figure 7-17 Checking data consistency (1)

The left pane displays the check history, and the right pane displays the corresponding check results and related details. l

New Check: used to create a check task.

l

Delete: used to delete a historical check task selected in the left pane.

l

Auto fix: used to open the configuration dialog box corresponding to the check result selected in the right pane.

l


l


l

: displays the result of Error level.

Step 2 Click New Check. The New Check window is displayed, as shown in Figure 7-18.

7-22


Issue 01 (2008-06-25)


7 Operating the CME

Figure 7-18 Creating a check task

Step 3 Setting the check items l

In the Choose RNS, select the RNS to be checked.

l

In the Check Categories field, select check items. In the Check Rules field, select check sub-items.

l

In the Check task name box, enter the task name.

l

Click Apply To All. The CME refreshes the other selected RNSs under Choose RNS according to the selected check items under Check Catagories of the current RNS.

Step 4 Click Check. The RAN Consistency Check Progress dialog box is displayed. Step 5 After the check, the RAN Consistency Check is displayed, as shown in Figure 7-19.

Issue 01 (2008-06-25)


7-23


7 Operating the CME

Figure 7-19 Checking data consistency (2)

Step 6 (Optional) Compare the check result of an RNC at a time with the check result of the same RNC at another time.

7-24

1.

Select a history check result in History check results, and then click Choose to compare.

2.

Select another check result in History check results, and then click Compare with. The RAN Consistency Check[Compare] window is displayed, as shown in Figure 7-20.


Issue 01 (2008-06-25)


7 Operating the CME

Figure 7-20 Comparison of check results

Table 7-4 Description of result comparison Area

Description

1

Information available in the check result of 333 but unavailable in the check result of 222

2


3

Information available in the check result of both 333 and 222


Double-click the data item to be modified. A modification wizard is displayed, as shown in Table 7-5. Table 7-5 Modification wizard Check Items

Wizard Description





Issue 01 (2008-06-25)


7-25


7 Operating the CME

Check Items

Wizard Description









7-26




Issue 01 (2008-06-25)


7 Operating the CME


NOTE



Issue 01 (2008-06-25)


7-27


7 Operating the CME


NOTE



7-28


Issue 01 (2008-06-25)




2.


3.


4.


Step 8 Repeat Step 7 to configure other data items, if required. ----End

?.4. Checking RNC Data Redundancy The redundant data is physical bearer data that is obsolete. The redundancy check helps clear redundant data to lighten the load. It also helps you ensure that obsolete data is deleted after data modification.


Procedure Step 1 Choose Tools > Preferences. The Preferences dialog box is displayed, as shown in Figure 7-26. Issue 01 (2008-06-25)


7-29


7 Operating the CME


Step 2 Select the Redundancy check box in the Check Categories area, and then select the check box in the Check Rules area. Step 3 Click OK to return to the main window. Step 4 Choose Tools > Sanity Check > Redundancy. The CME starts to check data redundancy. When the check is complete, the Check Redundancy window is displayed, as shown in Figure 7-27.

7-30


Issue 01 (2008-06-25)


7 Operating the CME

Figure 7-27 Checking data redundancy

Step 5 View the redundant data in the window. To browse the related data in the corresponding configuration window, double-click the data item, or select the data item and click

.

Step 6 To delete the redundant data, select one or more entries, right-click the entries, and then choose Delete from the shortcut menu. NOTE

In data configuration, redundant data can be retained for the purpose of, for example, RAN capacity expansion. Therefore, the redundancy check is optional. The results of the redundancy check only serve as a reminder of redundant data.

----End

Checking NodeB Data This describes how to check NodeB data integrity and how to check Iub interface data consistency. 7.1.6.2.1 Checking Iub Interface Data Consistency(Optional) This describes how to check the consistency between RNC data and NodeB data on the Iub interface. Data consistency is necessary to the normal communication between RNC and NodeB. 7.1.6.2.2 Checking NodeB Data Integrity This describes how to check the data integrity of the physical layer, transport network layer, and radio network layer on the NodeB side. The purpose is to ensure that the NodeB data can be sent to the NodeB and take effect on the NodeB. Issue 01 (2008-06-25)


7-31


7 Operating the CME

?.1. Checking Iub Interface Data Consistency(Optional) This describes how to check the consistency between RNC data and NodeB data on the Iub interface. Data consistency is necessary to the normal communication between RNC and NodeB.

Prerequisite l

The Iub interface data is configured on the RNC side.

l

The Iub interface data is configured on the NodeB side.

Context When the RNC and the NodeB are connected through a switching device, the features of the physical layer of the RNC can be inconsistent with those of the NodeB. In this case, you need to check the data consistency of only the data link layer and above. Note that the check should be performed from the top layer to the data link layer in the Iub protocol stack. For ATM transport mode, the check items include NCP, CCP, ALCAP, AAL2Path, IPoA, FRAATM, IMA, and UNI. For IP transport mode, the check items include NCP, CCP, IPPath, OMIP, PPP, MLPPP, EtherIP, and IPRT. Table 7-6 and Table 7-7 describe the check rules. Table 7-6 Rules of consistency check for ATM transport mode Check Item

Rule

NCP/CCP

l

The CCP port number and link quantity configured on the RNC must be consistency with those configured on the NodeB.

l

For the same NCP and the same CCP, the following parameters must be consistent on the two ends: ServiceType, PCR, SCR, MCR, MBS (maximum burst size), CCTM (CC timer), POLLTM (POLL timer), IDLETM (IDLE timer), NRTM (NO_RESPONSE timer), KATM (KEEP_ALIVE timer), MaxCC (maximum number of retransmissions upon expiration of the connection control timer), MaxPD (maximum number of PDUs that can be transmitted during a polling period), MaxSTATLE (maximum length of the STAT PDU list), VPI, VCI, and CarrierType.

l

If the ownership attribute of the ATM address of the adjacent node on the RNC is set to yes, that is, this adjacent node is directly connected to the RNC, then this ATM address must be consistent with that on the NodeB. Otherwise, such consistency is not required.

l

For the same NodeB, the following parameters must be consistent on the two ends: NSAP, ServiceType, PCR, SCR, MCR, MBS, CCTM, POLLTM, IDLETM, NRTM, KATM, MaxCC, MaxPD, MaxSTATLE, VPI, VCI, and CarrierType.

l

The number of AAL2 paths must be consistent on the two ends.

l

For the same path, the following parameters must be consistent on the two ends: ServiceType, PCR, SCR, MCR, MBS, CDVT (cell delay variation tolerance), VPI, VCI, and CarrierType.

ALCAP

AAL2PAT H

7-32


Issue 01 (2008-06-25)


7 Operating the CME

Check Item

Rule

IPoA

l

The local IP address on the RNC must be consistent with the peer IP address on the NodeB. The peer IP address on the RNC must be consistent with that on the NodeB.

l

The following parameters must be consistent on the two ends: ServiceType, PCR, SCR, MCR, MBS, CDVT, VPI, VCI, and CarrierType.

IMA Group

The following parameters must be consistent on the two ends: IMALinkNum (number of links, IMAVer (IMA protocol version), TxFrameLength, and MinActiveLinks.

FRAATM

TimeSlotNum (number of E1/T1 timeslots) must be consistent on the two ends.

UNI

-

Optical port

-

Others

The physical link bearers must be consistent on the two ends. Here is a counterexample. On the RNC side, the NCP and CCP0 are carried on R_UNI1 and the CCP1 and CCP2 are carried on R_UNI2; on the NodeB side, however, the NCP and CCP1 are carried on N_UNI1 and the CCP0 and CCP2 are carried on N_UNI2.

Table 7-7 Rules of consistency check for IP transport mode Check Item

Rule

NCP/CCP

l

The number of CCP ports must be consistent on the two ends.

l

For the same port, the local SCTP address on the NodeB must be consistent with one of the destination SCTP addresses on the RNC; the destination SCTP address on the NodeB must be consistent with one of the local SCTP addresses on the RNC.

l

The number of IP paths must be consistent on the two ends.

l

For the same path, the local IP address on the RNC must be consistent with the peer IP address on the NodeB; the peer IP address on the RNC must be consistent with that on the NodeB.

l

The path type, physical link type, TX bandwidth, and RX bandwidth must be consistent on the two ends.

IPPath

OMIP

Issue 01 (2008-06-25)



7-33


7 Operating the CME

Check Item

Rule

PPP

l


l

TimeSlotNum (number of timeslots) must be consistent on the two ends.

l

The following parameters must be consistent on the two ends: IPHC (IP header compression), MRU (maximum receive unit), and RestartTimer.

l


l

The number of PPP links must be consistent on the two ends.

l

IPHC must be consistent on the two ends.

MP

EtherIP

No consistency is required for the IP address and route data on the two ends.

PPPoE

No consistency is required. The NodeB side uses the PPPoE mode while the RNC uses the Ethernet mode.

Procedure

Step 1 Click in the CME configuration object pane, and then click NodeB CM Express in the configuration task pane. The NodeB CM Express window is displayed. Step 2 Click

. The Physical NodeB Basic Information window is displayed.

Step 3 Select a NodeB to be checked from the right pane, and then click dialog box is displayed.

. The NodeB Selection

Step 4 ClickFilter,TheSelect NodeB dialog box is displayed. (Optional) You can also click Load to select NodeBs by loading a user-defined file in the Select NodeB window. For details, refer to 7.3.7 Managing Hot NodeBs and Cells. Step 5 Select a NodeB from the resource poor, click Add or double-click the NodeB, and then click Close. The information of the NodeB is displayed in the NodeB Selection dialog box. Step 6 click Next. The Compare Result dialog box is displayed. Step 7 The dialog box displays the number of NodeBs on which the Iub interface data is inconsistent with that on the RNC. Click Details to view the details, as shown in Figure 7-28.

7-34


Issue 01 (2008-06-25)


7 Operating the CME

Figure 7-28 Iub interface data check result

The upper part of the window displays the items that are inconsistent on the two ends. One pane in the lower part displays the already configured items, and the other pane is empty. l

APPType: checked item

l

APPNo: link number

l

ParamName: parameter name

l

RNCValue: parameter value on the RNC

l

NodeBValue: parameter value on the NodeB

Step 8 Based on the check result, manually adjust the inconsistent data. ----End

?.2. Checking NodeB Data Integrity This describes how to check the data integrity of the physical layer, transport network layer, and radio network layer on the NodeB side. The purpose is to ensure that the NodeB data can be sent to the NodeB and take effect on the NodeB.

Prerequisite The data of the physical layer, transport network layer, and radio network layer on the NodeB side is configured.

Context Check data to ensure that: Issue 01 (2008-06-25)


7-35


7 Operating the CME

Transport network layer: l

NCP, CCP, and ALCAP data are configured.

l

OMIP or IPoA data is configured, and IPPath or AAL2Path data is configured.

l

The IP routes are reachable.

l

No empty MPGroup exists.

l

The resources in an IMA group cannot be used when the minimum number of activated links in the group is greater than the number of links in the group.

Physical layer: Check data to ensure that the relations between boards are configured. Radio network layer: l

Cell data is configured.

l

On the same TRU, the frequency difference between two local cells is equal to or greater than 4.2 MHz (= 21 x 0.2 MHz) and equal to or smaller than 5 MHz (25 x 0.2 MHz). This is true for both UL and DL.

l

If the sector where the local cell is located is in TX diversity mode or 0.5/0.5 carrier mode, then two transmitting channels of the local cell cannot be the same.

l

The transmitting units of the local cell uses one tributary of the antenna channel of the sector.

l

If the sector has one, two, or four antennas, then it must have one, two, or four antenna channels respectively.

l

If the sector is in no TX diversity mode, then at least one tributary of the antenna channel is a TX and RX tributary. If the sector is in TX diversity mode, then at least two are TX and RX tributaries.

l

In two-way antenna mode, a pair of antennas or two TX antennas (at antenna port 0A) can be configured on the same RF module. For a local cell in TX diversity mode, two RF modules are adjacent to each other.

l

In four-way demodulation mode or four-way economical demodulation mode, two pairs of antennas are configured for two RF modules, or four TX antennas (at antenna port 0A) are configured for four RF modules. For a local cell in TX diversity mode, two RF modules need to be adjacent to each other and the other two also need to be adjacent to each other.

l

The number of RF units of the cell meets the requirement.

l

In the case that the sector uses the adjacent antenna, the ULTimeDelay should be shorter than or equal to 130 ns.

Procedure

in the CME configuration object pane, and then click NodeB CM Express in Step 1 Click the configuration task pane. The NodeB CM Express window is displayed. Step 2 Click


Step 3 Select a NodeB to be checked from the right pane, and then click 7-36


. Issue 01 (2008-06-25)


7 Operating the CME

Step 4 According to the displayed information, enter the corresponding configuration dialog box for data modification. ----End

7.1.7 Closing an RNS You can close an RNS to suspend the configuration.

Prerequisite An RNS is open.

Procedure Step 1 Close all related configuration windows. Step 2 In the main window of the CME, right-click the RNS to be closed, and choose Close RNS on the shortcut menu. ----End

7.1.8 Deleting an RNS You can delete an obsolete RNS.

Prerequisite l

The RNS is closed.

l

The RNS data is obsolete.

CAUTION When the CME is integrated into the M2000, all the data changes in an RNS in the planned data area are removed if you delete this RNS.

Procedure In the main window of the CME, right-click the RNS to be deleted, and choose Delete RNS on the shortcut menu. ----End

7.1.9 Exiting the CME Client After you exit the CME client, the CME client is disconnected from the CME server.

Prerequisite l


l

The RNS data is saved.

Issue 01 (2008-06-25)


7-37


7 Operating the CME

Procedure l

In the main window of the CME, choose RAN > Exit.

l

In the main window of the CME, click

l


l

Press the shortcut keys ALT+F4, which are a common way of exiting a program.

. .

----End

7.2 Data Configuration Process in Integrated Mode This describes the process of data reconfiguration and activation on the CME that is integrated into the M2000.

Data Configuration Process Figure 7-29 shows the process of data configuration through the CME that is integrated into the M2000.

7-38


Issue 01 (2008-06-25)


7 Operating the CME

Figure 7-29 Data configuration process

Issue 01 (2008-06-25)


7-39


7 Operating the CME

Description of Data Configuration Table 7-8 Process of data configuration through the CME in integrated mode Operation

Description

Start CME client

For details, refer to 7.2.1 Starting the CME Client.

Data in the current data area consistent with data on the existing network?

The data in the current data area must be consistent with the data on the existing network.

Synchronize data from the existing network

Before reconfiguration, ensure that the data in the current data area of the CME is consistent with that on the existing network. For details, refer to 7.2.4 Synchronizing with the Data on the Existing Network. If there is no information about the NE to be synchronized in the current data area, you are required to load the RNS at first. For details, refer to 7.2.2 Loading Data from the Existing Network.

Create a planned data area

The planned data area is a workspace for data configuration. Perform this operation by referring to 7.2.5 Creating a Planned Data Area.

Data in the planned area consistent with data in the current area?

Before reconfiguration, check the data consistency between the planned data area and the current data area by referring to 7.2.10 Checking Data Consistency.

Synchronize RNS

If data inconsistency occurs, synchronize the RNS data to ensure the data consistency between the planned area and the current area.

The user can check the data consistency by referring to 7.2.3 Viewing Changed NEs.

For details, refer to 7.2.7 Synchronizing RNS Data. Reconfigure data

Through the wizards provided by the CME, reconfigure common objects in batches. For details, refer to RAN Reconfiguration Guide (CME-Based). You can check data during the reconfiguration, as listed below: Check the RNC data by referring to: l


l



Data conflict between the modified data and the data on the existing network?

7-40

l


l


Check whether the modified data in the planned area conflicts with the data on the existing network. For details, refer to 7.2.10 Checking Data Consistency.


Issue 01 (2008-06-25)


7 Operating the CME

Operation

Description

Activate data

After the reconfiguration on the CME in integrated mode, activate the modified data through the M2000. For details, refer to 7.2.12 Activating Data.

7.2.1 Starting the CME Client This describes how to start the CME client on the M2000 client when the CME is integrated into the M2000. 7.2.2 Loading Data from the Existing Network This describes how to create an RNS on the CME that is integrated into the M2000. This task is required when no RNS or not all RNSs are created in the current data area. 7.2.3 Viewing Changed NEs On the CME integrated into the M2000, multiple users can configure data in their own planned data areas. The modified data in the planned data areas does not take effect on the NEs until the data is activated. While a user performs data configuration, the CME can check whether another user modifies the NE data. 7.2.4 Synchronizing with the Data on the Existing Network If the data in the current data area is inconsistent with that on the existing network, you need to perform data synchronization. In multi-user mode, data on the existing network may be modified by any other user at any time. Therefore, you need to synchronize the data in the current data area with that on the existing network. The synchronization mode is of three types, which are manual synchronization, automatic synchronization, and periodical synchronization. 7.2.5 Creating a Planned Data Area This describes how to create a planned data area and add an RNS into this area before data configuration on the CME integrated into the M2000. RNS data can be obtained from the current data area after data synchronization. 7.2.6 Opening a Planned Data Area This describes how to open a planned data area before you configure data or resume data configuration. 7.2.7 Synchronizing RNS Data This describes how to synchronize the RNS data in a planned data area with that in the current data area on the CME that is integrated into the M2000. 7.2.8 Opening an RNS You need to open an appropriate RNS to continue an incomplete data configuration task. 7.2.9 Checking Data This describes how to check global data and Iub interface data. You need to check data integrity and redundancy after data configuration or reconfiguration. 7.2.10 Checking Data Consistency This describes how to check data consistency between the current data area and the planned data area on the CME that is integrated into the M2000. 7.2.11 Exporting a Modification Report This describes how to export a modification report on the CME that is integrated into the M2000. The report contains all the configuration data that you modify in a planned data area through the wizard. Issue 01 (2008-06-25)


7-41


7 Operating the CME

7.2.12 Activating Data This describes how to activate the modified data on the CME that is integrated into the M2000. After data configuration, the user need to activate the data on related NEs. The CME provides two ways for data activation, of which one is data activation through the script executor and the other is periodical data activation in job mode. 7.2.13 Closing a Planned Data Area This describes how to close a planned data area when you want to stop data configuration. To continue the configuration, you can open this area again. After the planned data area is closed, the data is only saved in the database rather than take effect. 7.2.14 Deleting a Planned Data Area This describes how to delete a planned data area that is obsolete. 7.2.15 Exiting the CME Client After you exit the CME client, the CME client is disconnected from the CME server.

7.2.1 Starting the CME Client This describes how to start the CME client on the M2000 client when the CME is integrated into the M2000.

Prerequisite l

The CME software is installed.

l

You are authenticated on the M2000 client and have logged in to the M2000 client.

l

Only one CME client can be started on an M2000 client.

l

If you exit or log out of the M2000 client during the CME operation, the CME client is shut down automatically after your confirmation.

Context

NOTE

The version of the CME client software must be consistent with the version of the CME Application Service, which is the CME server application software. Otherwise, a message is displayed, indicating the version mismatch, and the client is shut down forcibly.

Procedure Step 1 In the main window of the M2000 client, choose Maintenance > WRAN CMEV15 . After the system checks the CME license file, the license information dialog box is displayed. Step 2 Click OK to start the CME client. ----End

7.2.2 Loading Data from the Existing Network This describes how to create an RNS on the CME that is integrated into the M2000. This task is required when no RNS or not all RNSs are created in the current data area.

Prerequisite The CME client is started. 7-42


Issue 01 (2008-06-25)


7 Operating the CME

Procedure Step 1 In the RNS navigation tree in the main window, right-click RAN, and then choose Add RNS on the shortcut menu. The welcome dialog box is displayed. Step 2 Click Next. The Available RNS dialog box is displayed, as shown in Figure 7-30. Figure 7-30 Available RNS(s) to be created

This table lists the RNS(s) that is supported by the CME and already created on the M2000 client but not added to the current data area yet. Step 3 Click Next. The Add RNS dialog box is displayed, as shown in Figure 7-31.

Issue 01 (2008-06-25)


7-43


7 Operating the CME

Figure 7-31 Displaying the RNS creation progress

NOTE

l

The Status field indicates the current status.

l

The Progress field shows the task progress.

After the creation is finished, the Finish dialog box is displayed.

Step 4 Click Finish to return to the main window of the CME. The new RNS is displayed in the RNS navigation tree. ----End

7.2.3 Viewing Changed NEs On the CME integrated into the M2000, multiple users can configure data in their own planned data areas. The modified data in the planned data areas does not take effect on the NEs until the data is activated. While a user performs data configuration, the CME can check whether another user modifies the NE data. 7.2.3.1 Checking Changed NEs While a user performs data configuration, the CME can check whether another user modifies the NE data. 7.2.3.2 Browsing the Log This describes how to check the changed data in the current data area by browsing the log, and how to specify the filter conditions in the log.

Checking Changed NEs While a user performs data configuration, the CME can check whether another user modifies the NE data. 7-44


Issue 01 (2008-06-25)


7 Operating the CME

Prerequisite l


l

The data on the existing network changed.

Procedure In the main window of the CME, right-click an RNS, and choose Check Changed NE. l

If the current data area is set to 7.2.4.2 Automatic Synchronizing with the Data on the Existing Network, the current data area can automatically refresh the modified data on the existing network. In this case, a prompt is displayed, as shown in Figure 7-32. Figure 7-32 Checking changed NEs

l

If the current data area is set to Manual Refreshing, the current data area cannot automatically refresh the modified data on the existing network. If the data on the existing network does not change, the CME provides a prompt. If the data changes, the CME lists the changed NEs, as shown in Figure 7-33. Figure 7-33 Viewing the changed NEs

To make the data in the current data area consistent with the data on the existing network, you can reload the data of a changed NE by referring to 7.2.4.1 Manual Synchronizing with the Data on the Existing Network. ----End Issue 01 (2008-06-25)


7-45


7 Operating the CME

Browsing the Log This describes how to check the changed data in the current data area by browsing the log, and how to specify the filter conditions in the log.

Prerequisite l


l

7.2.6 Opening a Planned Data Area is complete.

l

You can filter the log records as required by type, user, command, time, result, or a combination of of these parameters.

l

The operation log occupies the server space without limitation if you do not control the size of the operation log. You can set the log capacity on the CME. The CME automatically deletes the log records that exceed the maximum record length.

Context

Procedure Step 1 In the main window of the CME, choose Planned > View Change Log. The View Log dialog box is displayed, as shown in Figure 7-34. Figure 7-34 Browsing the log

Select an RNS from the left part of the dialog box. The right part displays all the data changes in this RNS. If the StartTime and FinishedTime fields are filled, you can infer that the RNS data in the current data area is synchronized with that on the existing network. Step 2 Click Search. The Set change log filter window is displayed, as shown in Figure 7-35. 7-46


Issue 01 (2008-06-25)


7 Operating the CME

Figure 7-35 Specifying filter conditions

Step 3 Query related information by name or version of an NE, command, time, or any combination of these parameters. l

Specify a single filter condition on the Basic tab page.

l

Specify a combination filter condition on the Advanced tab page.

After the filter condition is specified, the system displays related search result. Step 4 Double-click a record to view the detailed information. Step 5 Click Save to save all the changed records about this RNS in .xls format. ----End

7.2.4 Synchronizing with the Data on the Existing Network If the data in the current data area is inconsistent with that on the existing network, you need to perform data synchronization. In multi-user mode, data on the existing network may be modified by any other user at any time. Therefore, you need to synchronize the data in the current data area with that on the existing network. The synchronization mode is of three types, which are manual synchronization, automatic synchronization, and periodical synchronization. 7.2.4.1 Manual Synchronizing with the Data on the Existing Network This describes how to manually synchronize the data in the current data area with the RNS data on the existing network when the CME is integrated in the M2000. 7.2.4.2 Automatic Synchronizing with the Data on the Existing Network You can enable the CME to automatically synchronize the data in the current data area with that on the existing network by setting the automatic synchronization mode, when the data in the current data area is inconsistent with the data on the existing network. 7.2.4.3 Scheduled Synchronizing with the Data on the Existing Network The M2000 uploads the configured data of the NE to the CME server on schedule, based on the NE selected by the user. Through scheduled synchronizing with the data on the existing network, the CME obtains the latest NE data for configuration.

Manual Synchronizing with the Data on the Existing Network This describes how to manually synchronize the data in the current data area with the RNS data on the existing network when the CME is integrated in the M2000. Issue 01 (2008-06-25)


7-47


7 Operating the CME


Context To reload the RNS data, perform this procedure to remove the data in the current data area and then reload the RNS data.

Procedure Step 1 Choose Current > Upload RNS. The welcome dialog box is displayed. Step 2 Click Next. The Available NE dialog box is displayed, as shown in Figure 7-36. This dialog box displays the RNCs and NodeBs that are already loaded into the current data area. Figure 7-36 Viewing the RNSs available for synchronization

Step 3 Select the objects to be synchronized, and then click Next. The CME starts to synchronize the data of selected RNCs and NodeBs. When the Progress reaches 100％, the data synchronization is complete. Step 4 Click Finish.

7-48


Issue 01 (2008-06-25)


7 Operating the CME

CAUTION After data synchronization, the ID of the RNC in the RNS may be changed by a tool other than the CME and then become effective on the network. In this case, if you synchronize the RNS data on the CME again, the operation fails and a prompt is displayed. ----End

Automatic Synchronizing with the Data on the Existing Network You can enable the CME to automatically synchronize the data in the current data area with that on the existing network by setting the automatic synchronization mode, when the data in the current data area is inconsistent with the data on the existing network.


Procedure Step 1 In the main window of the CME, right-click an RNS, and choose Set Refresh Mode on the shortcut menu. A dialog box is displayed for you to set the parameter. Step 2 Select AUTO refreshing. NOTE

l

Manual refreshing: When the data on the existing network changes, you are required to manually reload data in the current data area. Refer to 7.2.4.1 Manual Synchronizing with the Data on the Existing Network for details.

l

AUTO refreshing: The CME automatically refreshes data in the current data area. The auto refreshing should meet either of the following requirements: l

Two hours after RNC data modification, by default, the CME automatically performs a reload task to synchronize data of the whole RNC.

l

If 65535 or more MML commands are executed in two hours, the CME also performs a reload task automatically.

If you are performing operations in the planned data area while the data in the current data area is refreshed, you can double-click the CME icon on the bottom right corner of the interface to open the View Log window7.2.3.2 Browsing the Log.

Step 3 Click OK to end the setting. ----End

Scheduled Synchronizing with the Data on the Existing Network The M2000 uploads the configured data of the NE to the CME server on schedule, based on the NE selected by the user. Through scheduled synchronizing with the data on the existing network, the CME obtains the latest NE data for configuration.

Prerequisite l

Issue 01 (2008-06-25)

You have logged in to the M2000 client. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd

7-49


7 Operating the CME l

The RNC or NodeB exists on the current network.

l

The CME upload task is scheduled by the user.

l

The CME upload task can be performed once or periodically. The options of Period are day, week, and month.

l

The CME upload task can be performed only on the RNC and the NodeB.

Context

Procedure Step 1 Choose Maintenance > Task Management. The Task Management window is displayed. Step 2 Click New. The New Task dialog box is displayed. Step 3 Set the basic information of the task. 1.

In the Task Name box, enter the task name.

2.

In the Task Type navigation tree, select the CME upload task.

3.

In the Run Type field, click Once or Period.

Step 4 Click Next to set the execution time of the task. Step 5 Click ... and select the start time of the task in the displayed Date/Time Selection dialog box. NOTE

Start Time must be later than the current time of the server.

Step 6 Perform the corresponding operations according to the task running type, once or periodical. Task Running Type

Operation

Once

Go to Step 7.

Period

Specify Period and Run Times and then go to Step 7.

Step 7 Click Next and select the type of the target NE. The user can select All NE or select a specific NE. Step 8 Click Finish. The new CME upload task is displayed in the task list. ----End

7.2.5 Creating a Planned Data Area This describes how to create a planned data area and add an RNS into this area before data configuration on the CME integrated into the M2000. RNS data can be obtained from the current data area after data synchronization. 7-50


Issue 01 (2008-06-25)


7 Operating the CME

Prerequisite l


l

7.2.2 Loading Data from the Existing Network is complete.

Procedure Step 1 Choose Planned > Create Planned in the main window. The New Plan dialog box is displayed, as shown in Figure 7-37. Figure 7-37 Create a planned data area

Step 2 In the Plan Name box, enter the name of the planned data area to be created. You can define the area name. Different users can define different plan names. Step 3 Click OK. The planned data area is created. When the planned data area is created, the area is displayed in the drop-down list under the menu bar of the CME main window, as shown in Figure 7-38. Figure 7-38 Creating a planned data area successfully

Step 4 Load RNS data into the current data area. 1.

Issue 01 (2008-06-25)

In the navigation tree, right-click RAN and then choose Add RNS from the shortcut menu. The Select RNS dialog box is displayed, as shown in Figure 7-39.


7-51


7 Operating the CME

Figure 7-39 Loading RNS data

The dialog box displays the RNSs available in the current data area. 2.

Select the RNSs to be loaded to the planned data area, and then click OK.

----End

7.2.6 Opening a Planned Data Area This describes how to open a planned data area before you configure data or resume data configuration.

Prerequisite l


l

7.2.5 Creating a Planned Data Area is complete.

Context One user can open only one planned data area at a time.

Procedure Step 1 In the main window of the CME, choose Planned > Open Planned. The Select Plan dialog box is displayed, as shown in Figure 7-40.

7-52


Issue 01 (2008-06-25)


7 Operating the CME

Figure 7-40 Selecting a planned data area

Step 2 In the drop-down list, click the planned data area to be opened. Then click OK. The planned data area is opened. ----End

7.2.7 Synchronizing RNS Data This describes how to synchronize the RNS data in a planned data area with that in the current data area on the CME that is integrated into the M2000.

Prerequisite l


l

An RNS is created in the planned data area.

l

No RNS to be synchronized is open on the CME client.

Context Scenarios for RNS data synchronization: l

Before you configure the data in the planned data area, synchronize the data with that in the current data area.

l

If the configured data is obsolete before taking effect on the NEs, perform this operation to restore the data in the planned data area.

Issue 01 (2008-06-25)


7-53


7 Operating the CME

Procedure Step 1 In the RNS navigation tree on the left of the CME main window, select the RNS to be synchronized, and then choose Planned > Synchronize RNS on the menu bar. The Select RNS dialog box is displayed, as shown in Figure 7-41. Figure 7-41 Selecting the NEs to be synchronized

Step 2 Select the NEs to be synchronized, and then click OK. The CME starts synchronizing the planned data area with the current data area. After the synchronization, the RNS data is refreshed. ----End

7.2.8 Opening an RNS You need to open an appropriate RNS to continue an incomplete data configuration task.

Prerequisite l


l

No RNS is open on the CME client.

l

The RNS to be opened exists in the CME database.

Procedure In the main window of the CME, right-click the RNS to be opened, and choose Open RNS on the shortcut menu. ----End 7-54


Issue 01 (2008-06-25)


7 Operating the CME

7.2.9 Checking Data This describes how to check global data and Iub interface data. You need to check data integrity and redundancy after data configuration or reconfiguration. 7.2.9.1 Scheduled Data Check The CME integrated into the M2000 can check consistency and redundancy of the RNC data on schedule. This describes how to schedule a data check task and how to view the check report.

Scheduled Data Check The CME integrated into the M2000 can check consistency and redundancy of the RNC data on schedule. This describes how to schedule a data check task and how to view the check report.


Procedure Step 1 Choose System > Scheduled Sanity Check > Setting . The Timed Check dialog box is displayed, as shown in Figure 7-42. Figure 7-42 Setting the check items

Step 2 Set the check items: Issue 01 (2008-06-25)


7-55



On the CheckRNSList tab page, set the objects to be checked on schedule. The TimeCheck field indicates whether the scheduled check is enabled.

l

On the CheckTime page, set the check time.

Step 3 Click Close to return to the main window of the CME. Step 4 Choose System > Scheduled Sanity Check > History Results . The History Check Result dialog box is displayed, as shown in Figure 7-43. Figure 7-43 Viewing the check report

Step 5 Double-click a check time. The Integrity dialog box is displayed, as shown in Figure 7-44.

7-56


Issue 01 (2008-06-25)


7 Operating the CME

Figure 7-44 Data check report

Step 6 View the data conflict. l

The check result of all levels is displayed by default.

l


l


Step 7 To view the check report in .xls format, right-click in the dialog box and then select Export Data from the shortcut menu to export the report in .xls format. ----End

Checking RNC Data This describes how to check RNC data consistency and redundancy. 7.2.9.2.1 Rules of Data Consistency Check This describes how to check data integrity of a single RNC or multiple RNCs and how to check data consistency on the radio network layer. 7.2.9.2.2 Checking RNC Data Consistency This describes how to check RNC data integrity and how to check data consistency of the radio network layer. The inconsistent data can be loaded onto network elements and validated before the network elements start up and run properly. 7.2.9.2.3 Checking Data Consistency of Multiple RNCs Issue 01 (2008-06-25)


7-57


7 Operating the CME

This describes how to check data integrity of multiple RNCs and how to check data consistency on the radio network layer. The inconsistent data can be loaded onto network elements and validated before the network elements start up and run properly. 7.2.9.2.4 Checking RNC Data Redundancy The redundant data is physical bearer data that is obsolete. The redundancy check helps clear redundant data to lighten the load. It also helps you ensure that obsolete data is deleted after data modification.

?.1. Rules of Data Consistency Check This describes how to check data integrity of a single RNC or multiple RNCs and how to check data consistency on the radio network layer. The check items are as follows: l

Global location information –

l

l

l

7-58

LAC, RAC, URA, and SAC

Basic information of the RNC –

OSP

–

Clock source and working mode

–

CN domain data

Data of the transport network user plane and control plane on the Iub, Iur, Iu-CS, Iu-PS, and Iu-BC interfaces –

NCP and CCP

–

AAL2 adjacent node

–

AAL2 path

–

AAL2 route

–

MTP3b signaling link set

–

MTP3b signaling link

–

MTP3b route

–

Physical link for carrying each of the SAAL link, IPoA PVC, an AAL2 path

–

DSP of IUCS or IUCS_ALCAP type

Cell data and neighboring relation at the radio network layer, including the consistency of the cell parameters, cell names, NRNC IDs, and GSM cells and also the unidirectional or bidirectional neighboring relations Data to be checked is listed in Table 7-9.


Issue 01 (2008-06-25)


7 Operating the CME

Table 7-9 Data to be checked on the radio network layer Data

Description

NRNC Cell

l

Check Existence of NRNCCELL: After the reparenting, the NRNC cells configured by a third party may not exist on the NRNCs. In this case, the CME checks whether the involved RNCs exist and provides a wizard for changing the ownership of the NRNC cells. This wizard guides you to move the NRNC cells to other RNC and exports the modified MML script.

l

Check CellNameConflict: The CME checks whether the names of the cells and NRNC cells under the current RNC are in conflict with the names of the cells configured with the Iub interface under other RNCs. After the check, the CME provides a modification wizard and generates an MML script. To modify the name of a cell under an NRNC, you need to exit the current RNC and open the NRNC.

l

Check Consistency of NRNCCELL: Based on the cell ID, the CME checks whether the data of a cell under an RNC is consistent with the data of the same cell under another RNC. The data includes the cell name, frequency, and scrambling code. After the check, the CME provides a modification wizard and generates an MML script. If the frequency is changed, the CME can automatically adjust the neighboring relations between cells.

l

Check GSMCELL Consistency: If the MCC, MNC, CID, and LAC of each GSM cell configured on the local RNC are consistent with those configured on other RNCs, the CME checks the consistency of other data and displays the inconsistent data.

l

Check GSMCELL Frequency: The CME checks whether the frequency of a GSM cell in the current RNS adheres to the rules.

GSM Cell

The CME does not provide a modification wizard.

Issue 01 (2008-06-25)


7-59


7 Operating the CME

Data

Description

Neighborin g Relations

l

Check TwinCell Neighboring Reflexivity: The CME checks whether the cells controlled by the same NodeB are configured with the bidirectional inter-frequency neighboring relations. Through the modification wizard, the user can delete the corresponding neighboring relation and export the modified MML script.

l

Check Total Number of Intra and Inter Neighboring Links for Each Cell: The CME checks whether the number of cells that are configured with intra-frequency and inter-frequency neighboring relations to a target cell exceeds the maximum value. The user can set the maximum value. Through the modification wizard, the user can delete the corresponding neighboring relation and export the modified MML script.

l

Check Total Number of Intra Neighboring Links for Each Cell: The CME checks whether the number of cells that are configured with intra-frequency neighboring relations to a target cell exceeds the maximum value. The user can set the maximum value. Through the modification wizard, the user can delete the corresponding neighboring relation and export the modified MML script.

l

Check Total Number of Inter Neighboring Links for Each Cell: The CME checks whether the number of cells that are configured with inter-frequency neighboring relations to a target cell exceeds the maximum value. The user can set the maximum value. Through the modification wizard, the user can delete the corresponding neighboring relation and export the modified MML script.

l

Check Total Number of Intra Neighboring Links with Sib11 Usage for Each Cell: When the SIB11 delivering indication (SIB11Ind) is set to TRUE, that is, when the neighboring relation is delivered in the SIB11, the CME checks whether the number of the intra-frequency neighboring relations configured for a target cell exceeds the maximum value. The user can set the maximum value. Through the modification wizard, the user can delete the corresponding neighboring relation and export the modified MML script.

l

Check Total Number of Inter Neighboring Links with Sib11 Usage for Each Cell: When the SIB11 delivering indication (SIB11Ind) is set to TRUE, that is, when the neighboring relation is delivered in the SIB11, the CME checks whether the number of the inter-frequency neighboring relations configured for a target cell exceeds the maximum value. The user can set the maximum value. Through the modification wizard, the user can delete the corresponding neighboring relation and export the modified MML script.

l

Check Unidirectional Intra Neighboring Relations: The CME checks the cells configured with the unidirectional intra-frequency neighboring relations. Through the modification wizard, the system automatically adjusts the neighboring relation to bidirectional neighboring relation. For the inconsistent parameter configuration between cells, the system adjustment is as follows: –

7-60

If the cell frequencies are inconsistent, the system adjusts the cell frequencies based on the source cell frequency, and then determines


Issue 01 (2008-06-25)


7 Operating the CME

Data

Description whether the frequency of the neighboring cells is the same as that of the current cell. If the frequencies are the same, the neighboring relation is not changed. If the frequencies are different, the system adjusts the neighboring relation to inter-frequency neighboring relation. –

l


Check Unidirectional Inter Neighboring Relations: The CME checks the cells configured with the unidirectional inter-frequency neighboring relation. Through the modification wizard, the system automatically adjusts the neighboring relation to bidirectional neighboring relation. For the inconsistent parameter configuration between cells, the system adjustment is as follows: –

If the cell frequencies are inconsistent, the system adjusts the cell frequencies based on the source cell frequency, and then determines whether the frequency of the neighboring cells is the same as that of the current cell. If the frequencies are different, the neighboring relation is not changed. If the frequencies are the same, the system adjusts the neighboring relation to intra-frequency neighboring relation.

–


?.2. Checking RNC Data Consistency This describes how to check RNC data integrity and how to check data consistency of the radio network layer. The inconsistent data can be loaded onto network elements and validated before the network elements start up and run properly.


Context Rules of RNC data check, refer to7.2.9.2.1 Rules of Data Consistency Check.

Procedure Step 1 Choose Tools > Preferences. The Preferences dialog box is displayed, as shown in Figure 7-45.

Issue 01 (2008-06-25)


7-61


7 Operating the CME


Step 2 Set the check items: l

In the Check Categories field, select check items. In the Check Rules field, select check sub-items. Select the fault level on the right part: Major, Warning, or Error.

l

When multiple users work in different planned data areas in parallel, set the concurrence control switch in the Concurrence Setting tab page. If this switch is enabled, the CME can automatically assign IDs for some configuration objects to avoid data conflict in different planned data areas.

l

If the Neighboring Relations option is selected, set the maximum number of neighboring relations of each type in the Set Maximum of UMTS neighboring links tab page.

Step 3 Select check sub-items and then click OK to return to the main window. Step 4 Choose Tools > Sanity Check > Consistency . After the check is finished, the Check Consistency window is displayed, as shown in Figure 7-46.

7-62


Issue 01 (2008-06-25)


7 Operating the CME


Step 5 View un-configured data and inconsistent data. l

The check results of all levels are displayed by default.

l


l


l l

: displays the result of Error level. Recheck: When Auto Recheck is not selected, you should manually click this button to refresh the check results.


Issue 01 (2008-06-25)

Double-click the data item to be modified. A modification wizard is displayed, as shown in Table 7-10.


7-63


7 Operating the CME

Table 7-10 Modification wizard Check Items

Wizard Description












7-64




Issue 01 (2008-06-25)


7 Operating the CME


NOTE



Issue 01 (2008-06-25)


7-65


7 Operating the CME


NOTE



7-66


Issue 01 (2008-06-25)




2.


3.


4.


Step 7 Repeat Step 6 if you want to configure any more data. ----End

?.3. Checking Data Consistency of Multiple RNCs This describes how to check data integrity of multiple RNCs and how to check data consistency on the radio network layer. The inconsistent data can be loaded onto network elements and validated before the network elements start up and run properly.


Context For details about rules of data check for multiple RNCs, refer to 7.2.9.2.1 Rules of Data Consistency Check. Issue 01 (2008-06-25)


7-67


7 Operating the CME

Procedure Step 1 Choose System > RAN Consistency Check. The RAN Consistency Check window is displayed, as shown in Figure 7-52. Figure 7-52 Checking data consistency (1)

The left pane displays the check history, and the right pane displays the corresponding check results and related details. l

New Check: used to create a check task.

l

Delete: used to delete a historical check task selected in the left pane.

l

Auto fix: used to open the configuration dialog box corresponding to the check result selected in the right pane.

l


l


l

: displays the result of Error level.

Step 2 Click New Check. The New Check window is displayed, as shown in Figure 7-53.

7-68


Issue 01 (2008-06-25)


7 Operating the CME

Figure 7-53 Creating a check task

Step 3 Setting the check items l

In the Choose RNS, select the RNS to be checked.

l

In the Check Categories field, select check items. In the Check Rules field, select check sub-items.

l

In the Check task name box, enter the task name.

l

Click Apply To All. The CME refreshes the other selected RNSs under Choose RNS according to the selected check items under Check Catagories of the current RNS.

Step 4 Click Check. The RAN Consistency Check Progress dialog box is displayed. Step 5 After the check, the RAN Consistency Check is displayed, as shown in Figure 7-54.

Issue 01 (2008-06-25)


7-69


7 Operating the CME

Figure 7-54 Checking data consistency (2)

Step 6 (Optional) Compare the check result of an RNC at a time with the check result of the same RNC at another time.

7-70

1.

Select a history check result in History check results, and then click Choose to compare.

2.

Select another check result in History check results, and then click Compare with. The RAN Consistency Check[Compare] window is displayed, as shown in Figure 7-55.


Issue 01 (2008-06-25)


7 Operating the CME

Figure 7-55 Comparison of check results

Table 7-11 Description of result comparison Area

Description

1


2


3

Information available in the check result of both 333 and 222


Double-click the data item to be modified. A modification wizard is displayed, as shown in Table 7-12. Table 7-12 Modification wizard Check Items

Wizard Description





Issue 01 (2008-06-25)


7-71


7 Operating the CME

Check Items

Wizard Description









7-72




Issue 01 (2008-06-25)


7 Operating the CME


NOTE



Issue 01 (2008-06-25)


7-73


7 Operating the CME


NOTE



7-74


Issue 01 (2008-06-25)




2.


3.


4.


Step 8 Repeat Step 7 to configure other data items, if required. ----End

?.4. Checking RNC Data Redundancy The redundant data is physical bearer data that is obsolete. The redundancy check helps clear redundant data to lighten the load. It also helps you ensure that obsolete data is deleted after data modification.


Procedure Step 1 Choose Tools > Preferences. The Preferences dialog box is displayed, as shown in Figure 7-61. Issue 01 (2008-06-25)


7-75


7 Operating the CME


Step 2 Select the Redundancy check box in the Check Categories area, and then select the check box in the Check Rules area. Step 3 Click OK to return to the main window. Step 4 Choose Tools > Sanity Check > Redundancy. The CME starts to check data redundancy. When the check is complete, the Check Redundancy window is displayed, as shown in Figure 7-62.

7-76


Issue 01 (2008-06-25)


7 Operating the CME

Figure 7-62 Checking data redundancy

Step 5 View the redundant data in the window. To browse the related data in the corresponding configuration window, double-click the data item, or select the data item and click

.

Step 6 To delete the redundant data, select one or more entries, right-click the entries, and then choose Delete from the shortcut menu. NOTE

In data configuration, redundant data can be retained for the purpose of, for example, RAN capacity expansion. Therefore, the redundancy check is optional. The results of the redundancy check only serve as a reminder of redundant data.

----End

Checking NodeB Data This describes how to check NodeB data integrity and how to check Iub interface data consistency. 7.2.9.3.1 Checking Iub Interface Data Consistency(Optional) This describes how to check the consistency between RNC data and NodeB data on the Iub interface. Data consistency is necessary to the normal communication between RNC and NodeB. 7.2.9.3.2 Checking NodeB Data Integrity This describes how to check the data integrity of the physical layer, transport network layer, and radio network layer on the NodeB side. The purpose is to ensure that the NodeB data can be sent to the NodeB and take effect on the NodeB. Issue 01 (2008-06-25)


7-77


7 Operating the CME

?.1. Checking Iub Interface Data Consistency(Optional) This describes how to check the consistency between RNC data and NodeB data on the Iub interface. Data consistency is necessary to the normal communication between RNC and NodeB.

Prerequisite l

The Iub interface data is configured on the RNC side.

l

The Iub interface data is configured on the NodeB side.

Context When the RNC and the NodeB are connected through a switching device, the features of the physical layer of the RNC can be inconsistent with those of the NodeB. In this case, you need to check the data consistency of only the data link layer and above. Note that the check should be performed from the top layer to the data link layer in the Iub protocol stack. For ATM transport mode, the check items include NCP, CCP, ALCAP, AAL2Path, IPoA, FRAATM, IMA, and UNI. For IP transport mode, the check items include NCP, CCP, IPPath, OMIP, PPP, MLPPP, EtherIP, and IPRT. Table 7-13 and Table 7-14 describe the check rules. Table 7-13 Rules of consistency check for ATM transport mode Check Item

Rule

NCP/CCP

l

The CCP port number and link quantity configured on the RNC must be consistency with those configured on the NodeB.

l

For the same NCP and the same CCP, the following parameters must be consistent on the two ends: ServiceType, PCR, SCR, MCR, MBS (maximum burst size), CCTM (CC timer), POLLTM (POLL timer), IDLETM (IDLE timer), NRTM (NO_RESPONSE timer), KATM (KEEP_ALIVE timer), MaxCC (maximum number of retransmissions upon expiration of the connection control timer), MaxPD (maximum number of PDUs that can be transmitted during a polling period), MaxSTATLE (maximum length of the STAT PDU list), VPI, VCI, and CarrierType.

l

If the ownership attribute of the ATM address of the adjacent node on the RNC is set to yes, that is, this adjacent node is directly connected to the RNC, then this ATM address must be consistent with that on the NodeB. Otherwise, such consistency is not required.

l

For the same NodeB, the following parameters must be consistent on the two ends: NSAP, ServiceType, PCR, SCR, MCR, MBS, CCTM, POLLTM, IDLETM, NRTM, KATM, MaxCC, MaxPD, MaxSTATLE, VPI, VCI, and CarrierType.

l

The number of AAL2 paths must be consistent on the two ends.

l

For the same path, the following parameters must be consistent on the two ends: ServiceType, PCR, SCR, MCR, MBS, CDVT (cell delay variation tolerance), VPI, VCI, and CarrierType.

ALCAP

AAL2PAT H

7-78


Issue 01 (2008-06-25)


7 Operating the CME

Check Item

Rule

IPoA

l


l

The following parameters must be consistent on the two ends: ServiceType, PCR, SCR, MCR, MBS, CDVT, VPI, VCI, and CarrierType.

IMA Group

The following parameters must be consistent on the two ends: IMALinkNum (number of links, IMAVer (IMA protocol version), TxFrameLength, and MinActiveLinks.

FRAATM

TimeSlotNum (number of E1/T1 timeslots) must be consistent on the two ends.

UNI

-

Optical port

-

Others

The physical link bearers must be consistent on the two ends. Here is a counterexample. On the RNC side, the NCP and CCP0 are carried on R_UNI1 and the CCP1 and CCP2 are carried on R_UNI2; on the NodeB side, however, the NCP and CCP1 are carried on N_UNI1 and the CCP0 and CCP2 are carried on N_UNI2.

Table 7-14 Rules of consistency check for IP transport mode Check Item

Rule

NCP/CCP

l

The number of CCP ports must be consistent on the two ends.

l

For the same port, the local SCTP address on the NodeB must be consistent with one of the destination SCTP addresses on the RNC; the destination SCTP address on the NodeB must be consistent with one of the local SCTP addresses on the RNC.

l

The number of IP paths must be consistent on the two ends.

l

For the same path, the local IP address on the RNC must be consistent with the peer IP address on the NodeB; the peer IP address on the RNC must be consistent with that on the NodeB.

l

The path type, physical link type, TX bandwidth, and RX bandwidth must be consistent on the two ends.

IPPath

OMIP

Issue 01 (2008-06-25)



7-79


7 Operating the CME

Check Item

Rule

PPP

l


l

TimeSlotNum (number of timeslots) must be consistent on the two ends.

l

The following parameters must be consistent on the two ends: IPHC (IP header compression), MRU (maximum receive unit), and RestartTimer.

l


l

The number of PPP links must be consistent on the two ends.

l

IPHC must be consistent on the two ends.

MP

EtherIP

No consistency is required for the IP address and route data on the two ends.

PPPoE

No consistency is required. The NodeB side uses the PPPoE mode while the RNC uses the Ethernet mode.

Procedure

Step 1 Click in the CME configuration object pane, and then click NodeB CM Express in the configuration task pane. The NodeB CM Express window is displayed. Step 2 Click


Step 3 Select a NodeB to be checked from the right pane, and then click dialog box is displayed.

. The NodeB Selection

Step 4 ClickFilter,TheSelect NodeB dialog box is displayed. (Optional) You can also click Load to select NodeBs by loading a user-defined file in the Select NodeB window. For details, refer to 7.3.7 Managing Hot NodeBs and Cells. Step 5 Select a NodeB from the resource poor, click Add or double-click the NodeB, and then click Close. The information of the NodeB is displayed in the NodeB Selection dialog box. Step 6 click Next. The Compare Result dialog box is displayed. Step 7 The dialog box displays the number of NodeBs on which the Iub interface data is inconsistent with that on the RNC. Click Details to view the details, as shown in Figure 7-63.

7-80


Issue 01 (2008-06-25)


7 Operating the CME

Figure 7-63 Iub interface data check result

The upper part of the window displays the items that are inconsistent on the two ends. One pane in the lower part displays the already configured items, and the other pane is empty. l

APPType: checked item

l

APPNo: link number

l

ParamName: parameter name

l

RNCValue: parameter value on the RNC

l

NodeBValue: parameter value on the NodeB

Step 8 Based on the check result, manually adjust the inconsistent data. ----End

?.2. Checking NodeB Data Integrity This describes how to check the data integrity of the physical layer, transport network layer, and radio network layer on the NodeB side. The purpose is to ensure that the NodeB data can be sent to the NodeB and take effect on the NodeB.

Prerequisite The data of the physical layer, transport network layer, and radio network layer on the NodeB side is configured.

Context Check data to ensure that: Issue 01 (2008-06-25)


7-81


7 Operating the CME

Transport network layer: l

NCP, CCP, and ALCAP data are configured.

l

OMIP or IPoA data is configured, and IPPath or AAL2Path data is configured.

l

The IP routes are reachable.

l

No empty MPGroup exists.

l

The resources in an IMA group cannot be used when the minimum number of activated links in the group is greater than the number of links in the group.

Physical layer: Check data to ensure that the relations between boards are configured. Radio network layer: l

Cell data is configured.

l

On the same TRU, the frequency difference between two local cells is equal to or greater than 4.2 MHz (= 21 x 0.2 MHz) and equal to or smaller than 5 MHz (25 x 0.2 MHz). This is true for both UL and DL.

l

If the sector where the local cell is located is in TX diversity mode or 0.5/0.5 carrier mode, then two transmitting channels of the local cell cannot be the same.

l

The transmitting units of the local cell uses one tributary of the antenna channel of the sector.

l

If the sector has one, two, or four antennas, then it must have one, two, or four antenna channels respectively.

l

If the sector is in no TX diversity mode, then at least one tributary of the antenna channel is a TX and RX tributary. If the sector is in TX diversity mode, then at least two are TX and RX tributaries.

l

In two-way antenna mode, a pair of antennas or two TX antennas (at antenna port 0A) can be configured on the same RF module. For a local cell in TX diversity mode, two RF modules are adjacent to each other.

l

In four-way demodulation mode or four-way economical demodulation mode, two pairs of antennas are configured for two RF modules, or four TX antennas (at antenna port 0A) are configured for four RF modules. For a local cell in TX diversity mode, two RF modules need to be adjacent to each other and the other two also need to be adjacent to each other.

l

The number of RF units of the cell meets the requirement.

l

In the case that the sector uses the adjacent antenna, the ULTimeDelay should be shorter than or equal to 130 ns.

Procedure

in the CME configuration object pane, and then click NodeB CM Express in Step 1 Click the configuration task pane. The NodeB CM Express window is displayed. Step 2 Click


Step 3 Select a NodeB to be checked from the right pane, and then click 7-82


. Issue 01 (2008-06-25)


7 Operating the CME

Step 4 According to the displayed information, enter the corresponding configuration dialog box for data modification. ----End

7.2.10 Checking Data Consistency This describes how to check data consistency between the current data area and the planned data area on the CME that is integrated into the M2000.

Prerequisite l


l

7.2.5 Creating a Planned Data Area is complete. NOTE

Before checking data consistency, perform 7.2.4.1 Manual Synchronizing with the Data on the Existing Network to guarantee the validity of the data on the existing network.

Context This task is performed to ensure that the data before reconfiguration is consistent with the data after reconfiguration. The details are as follows: l

Before reconfiguration, check the data consistency between the planned area and the current area to ensure the validity of subsequent data configuration.

l

After reconfiguration and before activation, check whether the MML commands exported through the wizard on the CME are valid to the data on the existing network. The CME is integrated into the M2000. For example, when user A modifies the data of an RNS in a planned data area, user B may modify the data of the RNS in another planned data area and activate the data on related NEs. In this case, the data in the current data area is refreshed. Thus, the data modified by user A may become invalid. To avoid this problem, the user should check data consistency.

CAUTION Check data consistency before activation. If data conflict occurs, you should synchronize the data in the planned data area with the data in the current data area. The data conflict may result from the following operations: l

Adding an object that already exists on the network.

l

Modifying an object that is already removed from the network.

l

Removing an object that is already removed from the network.

Procedure Step 1 Choose Planned > Check Inconsistency. The Inconsistency Check dialog box is displayed, as shown in Figure 7-64. Issue 01 (2008-06-25)


7-83


7 Operating the CME


l

To view all the data in the planned data area and the current data area, click Show All at the top of the window.

l

To view only inconsistent data between the planned data area and the current data area, click Show Only Difference at the top of the window.

Step 2 Check the Level field for the inconsistency level, and check the associated data in the current data area and planned data areas. In this way, you can check whether the data configuration is valid. ----End

7.2.11 Exporting a Modification Report This describes how to export a modification report on the CME that is integrated into the M2000. The report contains all the configuration data that you modify in a planned data area through the wizard.

Prerequisite l


l

The configuration data is modified through the wizard.

Procedure Step 1 Choose Planned > Export Modification Report in the main window. The Modification Report window is displayed, as shown in Figure 7-65. You can view the report information, such as the related RNS name, RNS ID, modification time, and modification type. 7-84


Issue 01 (2008-06-25)


7 Operating the CME

Figure 7-65 Viewing the modification report

Step 2 Click Export to export and save the report. ----End

7.2.12 Activating Data This describes how to activate the modified data on the CME that is integrated into the M2000. After data configuration, the user need to activate the data on related NEs. The CME provides two ways for data activation, of which one is data activation through the script executor and the other is periodical data activation in job mode. 7.2.12.1 Data Activation Through the Script Executor This describes how to activate modified data by using the script executor after modifying and exporting data on the CME client. The script executor supports the MML command file in .txt format and the NodeB configuration file in .xml format. 7.2.12.2 Periodical Data Activation in Job Mode After the data configuration, the CME exports and saves the data as an .xml file. You can create a CME Download task on the M2000. Thus, the M2000 activates the .xml file periodically.

Data Activation Through the Script Executor This describes how to activate modified data by using the script executor after modifying and exporting data on the CME client. The script executor supports the MML command file in .txt format and the NodeB configuration file in .xml format.

Prerequisite l

Issue 01 (2008-06-25)

The data modification file is exported and saved. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd

7-85



7.2.10 Checking Data Consistency is complete.

Context

CAUTION Each modification file loaded into the script executor corresponds to a task. Multiple tasks compose a project. The CME provides the following two data activation modes: l

Manual activation: In this mode, you need to open the script executor manually by referring to Step 1. (This is the default activation mode.)

l

(Optional) Automatic activation: After the modification file is exported through the wizard, a dialog box is displayed, as shown in Figure 7-67. In the dialog box, perform Step 3. You need to manually set this activation mode.

To enable automatic activation, choose View > Options in the main window of the CME. The Options dialog box is displayed. Click the Integrated Version Properties tab, and then select Run Script Executor Wizards Finished to enable the automatic activation.

Procedure Step 1 Choose Planned > Script Management. The Script Executor window is displayed, as shown in Figure 7-66. Figure 7-66 Displaying the project state

The table lists the status of all the projects uploaded in the planned data area. 7-86


Issue 01 (2008-06-25)


7 Operating the CME

Step 2 Choose System > Load Project. Select the folder to be activated, and then click OK. The Script Executor window is displayed, as shown in Figure 7-67. Figure 7-67 Modifying task-related information

This table lists the data configuration files loaded onto the CME. You can modify these files as required. Table 7-15 Shortcut menu options Option

Description

Upload Project

Upload a project, which consists of all the data modification files exported in one task through the wizard.

Up Task

Adjust the execution sequence of the tasks.

Down Task

NOTE

l

In the NeSessionType drop-down list, you can select a task activation mode: Bluk_Configuration (batch execution) or MmlSession (step-by-step execution). The NodeB configuration files can only be activated in batch execution mode.

l

In the IsSuspend drop-down list, you can specify whether to suspend a task. A suspended task can be resumed and then activated.

Step 3 Right-click the data modification file, and then select Upload Project from the shortcut menu. The Script Executor window is displayed, as shown in Figure 7-68. Issue 01 (2008-06-25)


7-87


7 Operating the CME

Figure 7-68 Uploading a project

Step 4 Right-click the data modification file to be activated, and then select Preactive Project or Active Project from the shortcut menu to pre-activate or activate this project. NOTE

Pre-activating a project is performed by the M2000, in a simulated environment set up by the RNC, to determine whether the data modification file to be activated is valid. The NodeB does not support preactivation.

Step 5 (Optional) Check the execution result or adjust the execution. 1.

7-88

Double-click a project record. The Script Executor window is displayed, as shown in Figure 7-69.


Issue 01 (2008-06-25)


7 Operating the CME

Figure 7-69 Checking result or adjusting execution

The upper pane of the window displays the information about all the tasks in this project. The lower pane displays the details of the task being executed. NOTE

Right-click a task. The shortcut menu provides the following options:

2.

l

Preactive Project, Active Project, and Cancel Operation: respectively used to pre-activate, activate, and cancel all the tasks that are not suspended in the project.

l

Suspend Task and Resume Task: respectively used to suspend and resume a selected task in the project.

l

To activate a suspended task, select Resume Task and then perform the activation operation.

l

Delete Project: used to delete all the tasks in the project.

l

Check Result: used to check the details about the execution result of a selected task.

l

Close: used to close the current tab page.

In the Script Executor window, choose View > Close Page to close the current tab page.

Step 6 Determine whether the script task is executed successfully according to SummaryTaskResult in the displayed dialog box, as shown in Figure 7-68. ----End

Periodical Data Activation in Job Mode After the data configuration, the CME exports and saves the data as an .xml file. You can create a CME Download task on the M2000. Thus, the M2000 activates the .xml file periodically. Issue 01 (2008-06-25)


7-89


7 Operating the CME

Prerequisite l

A planned data area is open.

l

The configured data is to be activated.

Procedure Step 1 In the main window of the CME that is integrated into the M2000, choose Planned > Export Job Script. Then save the exported data configuration file as an .xml file. The file is stored in the computer where the M2000/CME client is installed. Step 2 Start task management and parameter setting on the M2000. For details, refer to Creating a CME Download Task. NOTE

This data activation mode is only applicable to the following wizard-based operations: l

Adding a cell

l

Modifying the cell frequency

l

Modifying the cell algorithm parameter

l

Modifying neighboring relations between cells

l

Deleting data

----End

7.2.13 Closing a Planned Data Area This describes how to close a planned data area when you want to stop data configuration. To continue the configuration, you can open this area again. After the planned data area is closed, the data is only saved in the database rather than take effect.

Prerequisite l


l

7.2.6 Opening a Planned Data Area is complete.

Procedure Choose Planned > Close Planned in the main window. ----End

7.2.14 Deleting a Planned Data Area This describes how to delete a planned data area that is obsolete.

Prerequisite

7-90

l


l

The planned data area to be deleted is closed. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd

Issue 01 (2008-06-25)


7 Operating the CME

Context

CAUTION Be cautious when deleting the planned data area.

Procedure Step 1 In the main window of the CME, choose Planned > Delete Planned. The Select Plan dialog box is displayed, as shown in Figure 7-70. Figure 7-70 Selecting a planned data area

Step 2 In the drop-down list, click the planned data area to be deleted. Then click OK. The CME starts deleting the area. ----End

7.2.15 Exiting the CME Client After you exit the CME client, the CME client is disconnected from the CME server.

Issue 01 (2008-06-25)


7-91


7 Operating the CME

Prerequisite l


l

The RNS data is saved.

l

In the main window of the CME, choose RAN > Exit.

l


l


l

Press the shortcut keys ALT+F4, which are a common way of exiting a program.

Procedure

. .

----End

7.3 Managing Data Files The CME supports different data sources. Importing data or files to the CME facilitates data configuration and enhances configuration flexibility. 7.3.1 Managing a Radio Network Planning Data File This describes how to import and export a radio network planning data file to/from the CME, to enable you to modify the file in .xls format. 7.3.2 Managing an Interface Negotiation Data File This describes how to import and export the transport network negotiation data file of the Iub, Iu, and Iur interfaces to/from the CME, to enable you to modify the file in .xls format. 7.3.3 Managing a NodeB Template File This describes how to import and export a NodeB template file in .xml format, to enable you to perform a quick configuration of typical NodeB data. 7.3.4 Managing an NodeB Configuration File This describes how to import and export a NodeB configuration file in .xml format, to enable you to perform a quick configuration of typical NodeB data. 7.3.5 Managing an RNC Configuration File An RNC configuration file refers to a file that can be loaded onto the RNC and take effect on the RNC. After data configuration, you can export the RNC initial configuration file or the RNC reconfiguration file. 7.3.6 Managing a Cell Template File You can save the typical cell data as a template to facilitate the data configuration of other cells. 7.3.7 Managing Hot NodeBs and Cells Hot NodeBs and cells refers to the NodeBs and cells where the traffic is heavy or the data modification is frequent. You can manage these NodeBs and cells conveniently by loading the prepared configuration files to the CME. 7.3.8 Exporting Cell Algorithm Parameters and Channel Data After you browse or modify the cell algorithm parameters and channel data, you can export the specified data in .xls format. 7-92


Issue 01 (2008-06-25)


7 Operating the CME

7.3.1 Managing a Radio Network Planning Data File This describes how to import and export a radio network planning data file to/from the CME, to enable you to modify the file in .xls format. 7.3.1.1 Importing a Radio Network Planning Data File This describes how to import a radio network planning data file to the current RNS on the CME. The file includes the NodeB data on the RNC side, cell data on the RNC side, neighboring cell data, and neighboring relations between cells. 7.3.1.2 Exporting a Radio Network Planning Data File If you need to modify radio network planning data, you can export a radio network planning data file in .xls format, modify the data, and then import the file back to the CME.

Importing a Radio Network Planning Data File This describes how to import a radio network planning data file to the current RNS on the CME. The file includes the NodeB data on the RNC side, cell data on the RNC side, neighboring cell data, and neighboring relations between cells.

Prerequisite l


l

The 4.2 Negotiation and Planning Data File to be imported is available and the data to be imported is valid. For details about how to fill in the data file, refer to Filling in Radio Network Data Sheets.

Context The rules for the import are as follows: l

When neighboring relation data is imported, an NRNC cell is automatically created. When neighboring relation data is imported, if the target cell is a cell in other RNSs under the management of the CME and if the local RNS is not configured with the NRNC cell, then the NRNC cell is automatically added to the CME during the import. The search for the NRNS aims at only the RNSs configured with the Iur interface. The search among different RNC versions is supported with some old versions not supported.

l

When GSM cell data is imported, the GSM cell index is automatically generated. The common identification of a GSM cell is CGI (MCC/MNC/LAC/CID). The GSM cell, however, is identified with the GSM cell index on the CME. As a result, the CME enables the automatic assignment of the GSM cell index function. That is, before the data is imported, manual assignment of the GSM cell index is not required. The CME preferably assigns the CID value to the GSM cell index. In this case:

l

Issue 01 (2008-06-25)

–

If the CID value to be assigned is not occupied by the GSM cell index of other GSM cells, the CID value is directly assigned to the GSM cell index.

–

If the CID value to be assigned is already occupied by the GSM cell index of other GSM cells, the CME assigns a proper value ranging from 0 in ascending order to an idle GSM cell index.

When GSM neighboring relation data is imported, the CME supports cells with the cell ID or cell name as an identification and GSM cells with the GSM cell index, GSM cell name or CGI as an identification. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd

7-93


7 Operating the CME

l

–

The cell ID takes priority over the cell name. If the cell ID is already specified, the cell name field is automatically ignored.

–

The GSM cell index takes priority over the GSM cell name. The GSM cell name takes priority over the CGI. If the field of high priority identification is specified, the identifications of low priority are automatically ignored.

When cell data is imported, the NRNC cell with the same name on the CME is automatically removed. At the network planning phase, names of cells are usually unique. During the reparenting of NodeBs from other vendors, there are cases where an imported cell has the same name, MCC, and MNC as an NRNC cell does. In this case, the CME automatically removes this NRNC cell and exports the MML commands.

Procedure Step 1 Choose Radio > Import Radio Network Planning Data. A welcome dialog box is displayed. Step 2 Click Next. The Select File dialog box is displayed, as shown in Figure 7-71. Figure 7-71 Selecting a file

Step 3 Specify the import path, and then click Next. The Import Items dialog box is displayed, as shown in Figure 7-72.

7-94


Issue 01 (2008-06-25)


7 Operating the CME

Figure 7-72 Confirming the items to be imported

Step 4 Under the items to be imported, select the Enabled check box. To import cell data, select a template in Cell Template. The system also allows the update and import of location area information (LAC/RAC/SAC/ URA). That is, the location information about an existing cell can be modified and then imported. When the Update Area Info option is selected, the import of other objects is invalid. For neighboring relations between cells, the CME provides the following operations: l

Add data only: Add neighboring relations between cells. If the neighboring relations specified in the template file do not exist on the CME, they are added to the CME.

l

Update data: Update neighboring relations between cells.

l

–

If the neighboring relations specified in the template file do not exist on the CME, they are added to the CME.

–

If the neighboring relations specified in the template file exist on the CME, no modification is performed on the CME.

–

If the neighboring relations specified on the CME do not exist in the template file, they are deleted from the CME.

Delete data only: Delete the data in the template file from the CME.

Step 5 Click Next. Select whether to export the MML script. Specify the export path if required. NOTE

If you select Cell, GSMCell, NRNCCell, NeighborCellRelation, or GSMCellRelation in the Import Items dialog box, a dialog box specifying whether to export the related MML script is displayed after you click Next.

Step 6 Click Next. The CME starts importing the data. When the import is complete, the finish dialog box is displayed. Issue 01 (2008-06-25)


7-95


7 Operating the CME

Step 7 Click Finish. The data file is imported. NOTE

The import stops if the check on the data fails during the process.

----End

Exporting a Radio Network Planning Data File If you need to modify radio network planning data, you can export a radio network planning data file in .xls format, modify the data, and then import the file back to the CME.

Prerequisite l

7.1.2 Opening the RAN is performed.

l

The data is complete and valid. The health check function is available for checking data integrity and validity. For details, refer to 7.1.6.1.2 Checking RNC Data Consistency.

Context

CAUTION If a file exported from the CME is saved on the Citrix server, you cannot modify the file at the local end. In this case, you need to configure an FTP server on the Citrix server. Thus, you can download the exported file for modification, upload the file to the Citrix server, and then import to the CME. For details on the Citrix server, refer to the M2000 Client Citrix Access Solution User Guide.

Procedure Step 1 Choose Radio > Export Radio Network Planning Data in the main window. The welcome dialog box is displayed. Step 2 Click Next. The Export Items dialog box is displayed, as shown in Figure 7-73.

7-96


Issue 01 (2008-06-25)


7 Operating the CME

Figure 7-73 Confirming the items to be exported

Step 3 Under the items to be exported, select the Enabled check box. Step 4 Click Select Cell to select target cells. If you select one or more target cells, the CME export only the following data related to these cells: NRNCCell, NeighborCellRelation, GSMCell, and GSMCellRelation. Step 5 Click Next. The Select File dialog box is displayed, as shown in Figure 7-74.

Issue 01 (2008-06-25)


7-97


7 Operating the CME

Figure 7-74 Selecting a File

Step 6 Click Next. The CME starts exporting the data. When the export is complete, the finish dialog box is displayed. Step 7 Click Finish to end the import. ----End

7.3.2 Managing an Interface Negotiation Data File This describes how to import and export the transport network negotiation data file of the Iub, Iu, and Iur interfaces to/from the CME, to enable you to modify the file in .xls format. 7.3.2.1 Importing an Interface Negotiation Data File This describes how to import an interface negotiation data file to the current RNS to simplify data configuration. The data obtained during site preparation includes the Iub data, Iu-CS data, Iu-PS data, and Iur data. 7.3.2.2 Exporting an Interface Negotiation Data File If you need to reconfigure data on the Iub, Iu, or Iur interface, you can export an interface negotiation data file in .xls format, reconfigure the data, and then import the file back to the CME.

Importing an Interface Negotiation Data File This describes how to import an interface negotiation data file to the current RNS to simplify data configuration. The data obtained during site preparation includes the Iub data, Iu-CS data, Iu-PS data, and Iur data.

7-98


Issue 01 (2008-06-25)


7 Operating the CME

Prerequisite l


l

The configuration file to be imported is available and the data to be imported is valid. For details about how to fill in the interface data file, refer to Filling in the Iub Data Sheet and Filling in the Iu and Iur Data Sheets.

l

When the file is imported, the CME provides a prompt if the data in the file is incomplete or the data fails to pass the check. You can modify the data accordingly.

l

When importing Iub interface data, you can overwrite the data in the current RNS project, if any.

l

When importing Iu or Iur interface data, the CME dose not support overwritting the data in the current RNS project, if any.

l

When exporting Iub interface data, the CME supports the export of MML scripts in .txt format.

l

Before exporting the MML scripts of the previously imported Iub interface data, ensure that the imported bearing links are not the idle links on the existing network. Otherwise, a conflict occurs during script execution. To avoid the conflict, remove these imported links first using the corresponding script and then activate other data.

Context

Procedure Step 1 Choose Advanced > Import Interface Data in the main window. The Select Interface Type dialog box is displayed, as shown in Figure 7-75. Figure 7-75 Selecting the interface type

Step 2 Select an interface data template, and then click Next. The Select Template File dialog box is displayed, as shown in Figure 7-76. Issue 01 (2008-06-25)


7-99


7 Operating the CME

Figure 7-76 Specifying an interface data file

Step 3 Click Browse. The path that stores the file is displayed. Step 4 Select the negotiated data template to be imported, and then click Next. The CME starts importing the data. When the import is complete, the finish dialog box is displayed. Step 5 Click Finish. The interface data file is imported.

CAUTION You may run the MML script generated after you import Iub negotiated data. (Ensure that the CME data is synchronized with the data on the existing network before the data import.) In such a case, if one or more cells are activated, the execution of the MML script fails. You are advised to perform the following steps before running the script: 1. Check whether the NodeB to be imported is the same as any NodeB in the current project. That is, check whether both the ID and the name of the NodeB to be imported are the same as those of any NodeB in the current project. If the NodeB to be imported is different from any NodeB, run the MML script directly. If the NodeB to be imported is the same as a NodeB, perform the following steps. 2. Deactivate all the activated cells controlled by the NodeB. 3. Manually activate the cells after the MML script is executed. ----End

7-100


Issue 01 (2008-06-25)


7 Operating the CME

Exporting an Interface Negotiation Data File If you need to reconfigure data on the Iub, Iu, or Iur interface, you can export an interface negotiation data file in .xls format, reconfigure the data, and then import the file back to the CME.


Context

CAUTION If a file exported from the CME is saved on the Citrix server, you cannot modify the file at the local end. In this case, you need to configure an FTP server on the Citrix server. Thus, you can download the exported file for modification, upload the file to the Citrix server, and then import to the CME. For details on the Citrix server, refer to the M2000 Client Citrix Access Solution User Guide.

Procedure Step 1 Choose Advanced > Export Interface Data in the main window. The Export Items dialog box is displayed, as shown in Figure 7-77. Figure 7-77 Selecting the interface type

Issue 01 (2008-06-25)


7-101


7 Operating the CME

Step 2 Select the type of interface data to be exported, and then click Next. The Select File dialog box is displayed. Step 3 In the Select File dialog box, specify the export path. If...

Then...

You select the Iu/Iur interfaces,

Go to Step 6.

You select the Iub interface,

Go to Step 4.

Step 4 Click Next. The NodeB Selection dialog box is displayed. Step 5 Click Filter, select one or more NodeBs to be exported, and then click Close to return to the NodeB Selection dialog box. Step 6 Click Next. The CME starts exporting the data. When the export is complete, the finish dialog box is displayed. ----End

7.3.3 Managing a NodeB Template File This describes how to import and export a NodeB template file in .xml format, to enable you to perform a quick configuration of typical NodeB data. 7.3.3.1 Importing a NodeB Template File To simplify the data configuration for the NodeB, you can import a template file into the current project. The template file contains a set of predefined data. The template file is of two types: default file provided with the CME and user-defined file. 7.3.3.2 Exporting a NodeB Template File This describes how to export a NodeB template file after implementing NodeB data configuration. As a typical data set, this template can be used in similar configuration.

Importing a NodeB Template File To simplify the data configuration for the NodeB, you can import a template file into the current project. The template file contains a set of predefined data. The template file is of two types: default file provided with the CME and user-defined file.

Prerequisite l


l

The basic information of the NodeB is configured.

l

The 4.3 NodeB Template File to be imported is available.

Context The template file contains the complete NodeB data, which consists of transmission layer data, physical layer data, and radio network layer data.

7-102


Issue 01 (2008-06-25)


7 Operating the CME

Procedure



Figure 7-78 Creating a physical NodeB

Step 3 In the left pane, select one or more NodeBs to be imported with the template file, and then click . The Create Physical NodeB dialog box is displayed, as shown in Figure 7-79.

Issue 01 (2008-06-25)


7-103


7 Operating the CME

Figure 7-79 Specifying NodeB information

Step 4 Specify the information of the NodeB in the Series, Version, and Template drop-down list boxes, and then click OK. The CME starts importing the data. When the import is complete, a message is displayed. Click OK. The information of the new NodeB is displayed on the right of the Physical NodeB Basic Information window. NOTE

To delete a user-defined NodeB template file, click Delete Template in the Create Physical NodeB dialog box. The template files provided with the CME software cannot be deleted.

----End

Exporting a NodeB Template File This describes how to export a NodeB template file after implementing NodeB data configuration. As a typical data set, this template can be used in similar configuration.

Prerequisite l


l

All the required parameters are set. To check it, refer to 7.1.6.2.2 Checking NodeB Data Integrity.

Procedure

in the CME configuration object pane, and then click NodeB CM Express in Step 1 Click the configuration task pane. The NodeB CM Express window is displayed. Step 2 Click 7-80.

7-104



Issue 01 (2008-06-25)


7 Operating the CME


Step 3 Select a target NodeB in the right pane, and then click is displayed.

. The Export Template dialog box

Step 4 Enter the template name, and then click OK. The CME starts exporting the data. Step 5 Check that the user-defined template file is available in the Template drop-down list in the Create Physical NodeB dialog box. The NodeB template file is exported. ----End

7.3.4 Managing an NodeB Configuration File This describes how to import and export a NodeB configuration file in .xml format, to enable you to perform a quick configuration of typical NodeB data. 7.3.4.1 Importing a NodeB Data Configuration File If the configuration data of a NodeB is typical and common, you can import the obtained NodeB data configuration file into the project on the CME. The file then serves as the data source of another NodeB to be configured. 7.3.4.2 Exporting a NodeB Configuration File If the configuration data of a NodeB is typical and common, you can export the NodeB data as a NodeB configuration file in .xml format after the configuration of the NodeB. The file then can serve as a data source for another data configuration task.

Issue 01 (2008-06-25)


7-105


7 Operating the CME

Importing a NodeB Data Configuration File If the configuration data of a NodeB is typical and common, you can import the obtained NodeB data configuration file into the project on the CME. The file then serves as the data source of another NodeB to be configured.

Prerequisite l


l

4.4 NodeB Configuration File is complete and valid.

l

The CME supports the NodeB version.

l

The NodeB data configuration file to be imported must match the logical NodeB on the RNC side in terms of the NodeB name. The logical NodeB with the name described in the NodeB data configuration file must be available.

l

You can import NodeB data configuration files repeatedly. The latter file overwrites the former one.

Context

Procedure


7-106



Issue 01 (2008-06-25)


7 Operating the CME


Step 3 Click . The Import NodeB window is displayed and the Import button in the window is unavailable, as shown in Figure 7-82. Figure 7-82 Importing a NodeB data configuration file

Issue 01 (2008-06-25)


7-107


7 Operating the CME

Step 4 Select the destination folder in the left pane, and then click Search. Both valid and invalid NodeB data configuration files are displayed in the right of the window, as shown in Figure 7-83. Figure 7-83 Viewing the NodeB list

NOTE

If no logical NodeB on the RNC side corresponds to the NodeB to be imported, a message is displayed after you click Search. You can click OK and then enter the subrack number and subsystem number on the RNC to add a logical NodeB before the data import.

Step 5 Select a NodeB data configuration file in the Valid NodeB Configuration Data Files area, and then click Import. (The Import button is available now.) The CME starts importing the data. When the import is complete, a message is displayed. Click OK. Step 6 Close the Import NodeB window. The information of the imported NodeB is displayed in the right of the Build NodeB window. ----End

Exporting a NodeB Configuration File If the configuration data of a NodeB is typical and common, you can export the NodeB data as a NodeB configuration file in .xml format after the configuration of the NodeB. The file then can serve as a data source for another data configuration task.

Prerequisite

7-108

l


l

All the required parameters are set. To check it, refer to 7.1.6.2.2 Checking NodeB Data Integrity. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd

Issue 01 (2008-06-25)


7 Operating the CME

Procedure




Step 3 Select a target NodeB in the right of the window, click , and then select the destination folder to export the file. You can also select multiple NodeBs in this step to export multiple files. Step 4 Check that the file exists in the export path. The file is exported. ----End

7.3.5 Managing an RNC Configuration File An RNC configuration file refers to a file that can be loaded onto the RNC and take effect on the RNC. After data configuration, you can export the RNC initial configuration file or the RNC reconfiguration file. 7.3.5.1 Exporting an RNC Initial Configuration File After you perform RNC initial configuration on the CME, you can export an RNC initial configuration file through the wizard. The file then can be loaded onto the network element. Issue 01 (2008-06-25)


7-109


7 Operating the CME

7.3.5.2 Exporting Iub Interface Data on the RNC Side This describes how to export Iub interface data on the RNC side, including the data of the transport network layer and the cells of the NodeB. 7.3.5.3 Exporting Cell Data on the RNC Side This describes how to export cell data on the RNC side, including the basic data, neighboring relations between cells, cell algorithm parameters. 7.3.5.4 Exporting Cell-Oriented Algorithm Data This describes how to export cell-oriented algorithm data. 7.3.5.5 Exporting RNC-Oriented Algorithm Data This describes how to export RNC-oriented algorithm data. 7.3.5.6 Exporting Cell Status Configuration Data This describes how to export cell status configuration data for activating or deactivating cells in batches. 7.3.5.7 Exporting ATM Traffic Data This describes how to export new ATM traffic data through the wizard. 7.3.5.8 Exporting Iu Interface Data After data of the Iu-CS/Iu-PS interface is configured on the CME, you can export data of the Iu interface on the RNC side through the wizard. 7.3.5.9 Exporting Iur Interface Data This describes how to export Iur interface data on the RNC side through the wizard after data configuration. 7.3.5.10 Exporting NRNC/GSM Cell Data This describes how to export NRNC or GSM cell data.

Exporting an RNC Initial Configuration File After you perform RNC initial configuration on the CME, you can export an RNC initial configuration file through the wizard. The file then can be loaded onto the network element.

Prerequisite l


l

The configured data is complete and valid. The health check function is available for checking data integrity and validity. For details, refer to 7.1.6.1.2 Checking RNC Data Consistency.

Procedure Step 1 Choose Tools > Generate MML in the main window. The welcome dialog box is displayed. Step 2 Click Next. The Content dialog box is displayed, as shown in Figure 7-85.

7-110


Issue 01 (2008-06-25)


7 Operating the CME

Figure 7-85 Selecting the type of data to be exported

Step 3 Click Setting. The Setting dialog box is displayed, as shown in Figure 7-86. Figure 7-86 Specifying the objects to be exported

l

To export the data of typical Radio Access Bearer (RAB), typical Signaling Radio Bearer (SRB), and global parameters, select the Export Type RAB, Type SRB, Global Parameters check box.

l

To export attribute data of physical ports, select the Export port attributes check box.

Issue 01 (2008-06-25)


7-111


7 Operating the CME

Step 4 Click OK to return to the Content dialog box. Step 5 Click RNC Configuration Data in the MML Category drop-down list, and then click Next. The default export path is displayed, as shown in Figure 7-87. Figure 7-87 Specifying the path for the file to be exported

Step 6 Specify the export path, and then click Next. The CME starts exporting the data. When the export is complete, the finish dialog box is displayed. To change the export path, click Browse in the path specifying dialog box. Step 7 Click Finish. Step 8 Check that the file exists in the export path. The file is exported. ----End

Exporting Iub Interface Data on the RNC Side This describes how to export Iub interface data on the RNC side, including the data of the transport network layer and the cells of the NodeB.

Prerequisite

7-112

l


l



Issue 01 (2008-06-25)


7 Operating the CME

Procedure Step 1 Choose Tools > Generate MML in the main window. The welcome dialog box is displayed. Step 2 Click Next. The Content dialog box is displayed. Step 3 Click NodeB Configuration Data in the MML Category drop-down list, and click Addition Scripts or Deletion Scripts in the list below to specify the script type, as shown in Figure 7-88. Figure 7-88 Specifying the type of script to be exported

NOTE

l

Select Addition Scripts to export a script that contains MML commands used to add NodeB data.

l

Select Deletion Scripts to export a script that contains MML commands used to delete NodeB data.

Step 4 Click Setting. The Setting dialog box is displayed, as shown in Figure 7-89.

Issue 01 (2008-06-25)


7-113


7 Operating the CME

Figure 7-89 Setting the data items to be exported

Step 5 Select the data items to be exported, and then click OK to return to the Content dialog box. l

To export the SAC data, select the Export SAC check box.

l

To export the data about the shared objects, that is, to export all data related to the NodeB, select the Export shared objects check box.

CAUTION l

The shared objects exporting option is valid only when you export the resource data for part of the NodeBs that share the resource. For example, when you need to export the data of NodeB 1 that shares a UNI link with NodeB 2, you export the shared UNI link data if you select the Export shared objects check box. In the same situation, you do not export the shared UNI link data if you do not select the Export shared objects check box.

l

If you select the Export shared objects check box, errors may occur due to data conflict when the exported MML commands are executed.

Step 6 Click Select NodeB. The Select NodeB window is displayed. (Optional) You can also click Load to select NodeBs by loading a user-defined file in the Select NodeB window. For details, refer to 7.3.7 Managing Hot NodeBs and Cells. Step 7 Select a NodeB from the resource pool, click Add or double-click the NodeB, and then click Close. The information of the NodeB is displayed in the Content dialog box, as shown in Figure 7-90.

7-114


Issue 01 (2008-06-25)


7 Operating the CME

Figure 7-90 Selecting a NodeB complete

Step 8 Click Next. The default export path is displayed. To change the export path, click Browse in the path specifying dialog box. Step 9 Click Next. The CME starts exporting the data. When the export is complete, the finish dialog box is displayed. Step 10 Click Finish. Step 11 Check that the file exists in the export path. The file is exported. ----End

Exporting Cell Data on the RNC Side This describes how to export cell data on the RNC side, including the basic data, neighboring relations between cells, cell algorithm parameters.

Prerequisite l


l


Procedure Step 1 Choose Tools > Generate MML in the main window. The welcome dialog box is displayed. Step 2 Click Next. The MML Category dialog box is displayed. Issue 01 (2008-06-25)


7-115


7 Operating the CME

Step 3 Click Cell Configuration Data in the MML Category drop-down list, and click Addition Scripts or Deletion Scripts in the list below to specify the script type, as shown in Figure 7-91. Figure 7-91 Specifying to export cell data

NOTE

l

Select Addition Scripts to export a script that contains MML commands used to add cell data.

l

Select Deletion Scripts to export a script that contains MML commands used to delete cell data.

Step 4 Click Setting. The Setting dialog box is displayed, as shown in Figure 7-92.

7-116


Issue 01 (2008-06-25)


7 Operating the CME

Figure 7-92 Setting the data items to be exported

Step 5 To export the SAC data, select the Export SAC check box, and then click OK to return to the MML Category dialog box. Step 6 Click Select Cell. The Select Cell window is displayed. (Optional) You can also click Load to select cells by loading a user-defined file in the Select Cell window. For details, refer to 7.3.7 Managing Hot NodeBs and Cells. Step 7 Select a cell from the resource pool, click Add or double-click the cell, and then click Close. The information of the cell is displayed in the Content dialog box. Step 8 Click Next. The default export path is displayed. To change the export path, click Browse in the path specifying dialog box. Step 9 Click Next. The CME starts exporting the data. When the export is complete, the finish dialog box is displayed. Step 10 Click Finish. Step 11 Check that the file exists in the export path. The file is exported. ----End

Exporting Cell-Oriented Algorithm Data This describes how to export cell-oriented algorithm data.

Prerequisite l


l


Issue 01 (2008-06-25)


7-117


7 Operating the CME

Procedure Step 1 Choose Tools > Generate MML in the main window. The welcome dialog box is displayed. Step 2 Click Next. The Content dialog box is displayed. Step 3 Click Cell Algorithm Configuration Data in the MML Category drop-down list, and click Addition Scripts, Deletion Scripts, or Modification Scripts in the list below to specify the script type, as shown in Figure 7-93. Figure 7-93 Specifying the type of script to be exported

NOTE

l

Select Addition Scripts to export a script that contains MML commands used to add cell algorithm data.

l

Select Deletion Scripts to export a script that contains MML commands used to delete cell algorithm data.

l

Select Modification Scripts to export a script that contains MML commands used to modify cell algorithm data.

Step 4 Click Setting. The Select Algorithm dialog box is displayed, as shown in Figure 7-94.

7-118


Issue 01 (2008-06-25)


7 Operating the CME

Figure 7-94 Selecting algorithms to be exported

Used to import an algorithm from the Object List area to the Selected List area Used to export an algorithm from the Selected List area to the Object List area Used to import all the algorithms from the Object List area to the Selected List area Used to export all the algorithms from the Selected List area to the Object List area Step 5 Select one or more algorithms, and then click OK to return to the Content dialog box. Step 6 Click Select Cell. The Select Cell window is displayed. (Optional) You can also click Load to select cells by loading a user-defined file in the Select Cell window. For details, refer to 7.3.7 Managing Hot NodeBs and Cells. Step 7 Select a cell from the resource pool, and then click Add or double-click the cell. Step 8 Click Close. The data of the cell is displayed in the Content dialog box. Step 9 Click Next. The default export path is displayed. To change the export path, click Browse in the path specifying dialog box. Step 10 Click Next. The CME starts exporting the data. When the export is complete, the finish dialog box is displayed. Step 11 Click Finish. Step 12 Check that the file exists in the export path. The file is exported. ----End

Exporting RNC-Oriented Algorithm Data This describes how to export RNC-oriented algorithm data. Issue 01 (2008-06-25)


7-119


7 Operating the CME

Prerequisite l


l


Procedure Step 1 Choose Tools > Generate MML in the main window. The welcome dialog box is displayed. Step 2 Click Next. The Content dialog box is displayed. Step 3 Click RNC Algorithm Configuration Data in the MML Category drop-down list, as shown in Figure 7-95. Figure 7-95 Specifying the data to be exported and cell status configuration data

NOTE

To export the cell status configuration data with the RNC-oriented algorithm data, select the Export MML of Cell status check box.

Step 4 Click Setting. The Select Algorithm dialog box is displayed, as shown in Figure 7-96.

7-120


Issue 01 (2008-06-25)


7 Operating the CME

Figure 7-96 Selecting algorithms to be exported

Used to import an algorithm from the Object List area to the Selected List area Used to export an algorithm from the Selected List area to the Object List area Used to import all the algorithms from the Object List area to the Selected List area Used to export all the algorithms from the Selected List area to the Object List area Step 5 Select one or more algorithms, and then click OK to return to the Content dialog box. Step 6 Click Next. The default export path is displayed. To change the export path, click Browse in the path specifying dialog box. Step 7 Click Next. The CME starts exporting the data. When the export is complete, the finish dialog box is displayed. Step 8 Click Finish. Step 9 Check that the file exists in the export path. The file is exported. ----End

Exporting Cell Status Configuration Data This describes how to export cell status configuration data for activating or deactivating cells in batches.

Prerequisite l


l

The cells on the CME are in an ACTIVATED state.

Issue 01 (2008-06-25)


7-121




Procedure Step 1 Choose Tools > Generate MML in the main window. The welcome dialog box is displayed. Step 2 Click Next. The MML Category dialog box is displayed. Step 3 Click Cell Status Configuration Data in the MML Category drop-down list, and click Activation Scripts or Deactivation Scripts in the list below to specify the script type, as shown in Figure 7-97. Figure 7-97 Specifying the data and the type of script to be exported

NOTE

l

Select Activation Scripts to export a script that contains MML commands used to activate cells.

l

Select Deactivation Scripts to export a script that contains MML commands used to deactivate cells.

Step 4 Click Select Cell. The Select Cell window is displayed. (Optional) You can also click Load to select cells by loading a user-defined file in the Select Cell window. For details, refer to 7.3.7 Managing Hot NodeBs and Cells. Step 5 Select a cell from the resource pool, click Add or double-click the cell, and then click Close. The information of the cell is displayed in the MML Category dialog box. Step 6 Click Next. The default export path is displayed. To change the export path, click Browse in the path specifying dialog box. 7-122


Issue 01 (2008-06-25)


7 Operating the CME

Step 7 Click Next. The CME starts exporting the data. When the export is complete, the finish dialog box is displayed. Step 8 Click Finish. Step 9 Check that the file exists in the export path. The file is exported. ----End

Exporting ATM Traffic Data This describes how to export new ATM traffic data through the wizard.


Procedure Step 1 Choose Tools > Generate MML in the main window. The welcome dialog box is displayed. Step 2 Click Next. The Content dialog box is displayed. Step 3 Click ATM Traffic Configuration Data in the MML Category drop-down list, and click Addition Scripts or Deletion Scripts in the list below to specify the script type, as shown in Figure 7-98. Figure 7-98 Specifying the data and the type of script to be exported

Issue 01 (2008-06-25)


7-123



l

Select Addition Scripts to export a script that contains MML commands used to add ATM traffic data.

l

Select Deletion Scripts to export a script that contains MML commands used to delete ATM traffic data.

Step 4 Click Select ATMTRF. The Select ATMTRF window is displayed, as shown in Figure 7-99. Figure 7-99 Selecting ATM traffic records

Step 5 Select one or more ATM traffic records from the resource pool in the lower pane, and then click Add to add them to the upper pane in the window. Step 6 Click Close to return to the Content dialog box. Step 7 Click Next. The default export path is displayed. To change the export path, click Browse in the path specifying dialog box. Step 8 Click Next. The CME starts exporting the data. When the export is complete, the finish dialog box is displayed. Step 9 Click Finish. Step 10 Check that the file exists in the export path. The file is exported. ----End

Exporting Iu Interface Data After data of the Iu-CS/Iu-PS interface is configured on the CME, you can export data of the Iu interface on the RNC side through the wizard. 7-124


Issue 01 (2008-06-25)


7 Operating the CME

Prerequisite l


l

The Iu-CS/Iu-PS interface data is configured.

l


Procedure Step 1 Select Tools > Generate MML in the main window. The welcome dialog box is displayed. Step 2 Click Next. The Content dialog box is displayed. Step 3 In the MML Category drop-down list, click IuCS Configuration Data/IuPS Configuration Data and type of the exported script, which can be Addition Scripts or Deletion Scripts, as shown in Figure 7-100. Figure 7-100 Specifying Data and Script Type

NOTE

l

Select Addition Scripts to export a script that contains MML commands used to add Iu interface data.

l

Select Deletion Scripts to export a script that contains MML commands used to delete Iu interface data.

Step 4 Click Select DPX to choose the destination signaling point. This operation exports control plane data of the Iu interface.

Issue 01 (2008-06-25)


7-125



If the current version is V200R010C01B050, follow the following rules: l

l

For the ATM transport mode, ensure that: l

IUCS: The IUCS is exported according to the DPX.

l

IUPS: Data of the signaling plane and user plane are exported separately. Data at the signaling plane is exported according to the DPX and that at the user plane is exported according to the peer IP address of the IP path.

For the IP transport mode, ensure that: l

IUCS: Data of the signaling plane and user plane are exported separately. Data at the signaling plane is exported according to the DPX and that at the user plane is exported according to the peer IP address of the IP path.

l

IUPS: Data of the signaling plane and user plane are exported separately. Data at the signaling plane is exported according to the DPX and that at the user plane is exported according to the peer IP address of the IP path.

In V100R008C01B082 of the RNC version: export the data of the whole Iu-CS interface.

Step 5 Click Select IPAdd to select the peer IP address. This operation exports user plane data of the Iu interface. Step 6 Click Setting. The Setting dialog box is displayed, as shown in Figure 7-101. Figure 7-101 Setting Data Items to be Exported

Step 7 To export the data about the shared objects, that is, to export all data related to the CN, select the Export shared objects check box. Click OK to return to the Content dialog box. NOTE

This option is valid only when you export the resource data for part of the CN nodes that share the resource. For example, when you need to export the data of CN node 1 that shares resources with CN node 2, you can select Export shared objects to export the shared data. If this check box is not selected, the CME does not export the shared data.

7-126


Issue 01 (2008-06-25)


7 Operating the CME


Exporting Iur Interface Data This describes how to export Iur interface data on the RNC side through the wizard after data configuration.

Prerequisite l


l

The Iur interface data is configured.

l


Procedure Step 1 Choose Tools > Generate MML in the main window. The welcome dialog box is displayed. Step 2 Click Next. The Content dialog box is displayed. Step 3 Click Iur Configuration Data in the MML Category drop-down list, and click Addition Scripts or Deletion Scripts in the list below to specify the script type, as shown in Figure 7-102.

Issue 01 (2008-06-25)


7-127


7 Operating the CME

Figure 7-102 Specifying the data and the type of script to be exported

NOTE

l

Select Addition Scripts to export a script that contains MML commands used to add Iur interface data.

l

Select Deletion Scripts to export a script that contains MML commands used to delete Iur interface data.

Step 4 Click Setting. The Setting dialog box is displayed, as shown in Figure 7-103. Figure 7-103 Setting the data items to be exported

7-128


Issue 01 (2008-06-25)


7 Operating the CME

Step 5 To export the data about the shared objects, that is, to export all data related to the neighboring RNC, select the Export shared objects check box. Click OK to return to the Content dialog box. NOTE

The shared objects exporting option is valid only when you export the resource data for part of the neighboring RNCs that share the resource. For example, when you need to export the data of neighboring RNC 1 that shares resources with neighboring RNC 2, you export the shared resource data if you select the Export shared objects check box. In the same situation, you do not export the shared resource data if you do not select the Export shared objects check box.

Step 6 Click Select NRNC. The Select NRNC window is displayed, as shown in Figure 7-104. Figure 7-104 Selecting a neighboring RNC

Step 7 Select a neighboring RNC from the resource pool, click Add or double-click the neighboring RNC, and then click Close. The information of the neighboring RNC is displayed in the Content dialog box, as shown in Figure 7-105.

Issue 01 (2008-06-25)


7-129


7 Operating the CME

Figure 7-105 Selecting a neighboring RNC complete


Exporting NRNC/GSM Cell Data This describes how to export NRNC or GSM cell data.

Prerequisite l


l

The neighboring cell data is configured.

l


Context This procedure takes exporting the NRNC cell data as an example.

7-130


Issue 01 (2008-06-25)


7 Operating the CME

Procedure Step 1 Choose Tools > Generate MML in the main window. The welcome dialog box is displayed. Step 2 Click Next. The MML Category dialog box is displayed. Step 3 Click NRNC Cell Configuration Data in the MML Category drop-down list, and click Addition Scripts or Deletion Scripts in the list below to specify the script type, as shown in Figure 7-106. Figure 7-106 Specifying to export NRNC cell data

NOTE

l

Select Addition Scripts to export a script that contains MML commands used to add NRNC cell data.

l

Select Deletion Scripts to export a script that contains MML commands used to delete NRNC cell data.

Step 4 Click Select NRNCCELL. The Select NRNCCell window is displayed. Step 5 Select an NRNC cell from the resource pool, click Add or double-click the cell, and then click Close. The information of the neighboring cell is displayed in the MML Category dialog box. Step 6 Click Next. The default export path is displayed. To change the export path, click Browse in the path specifying dialog box. Step 7 Click Next. The CME starts exporting the data. When the export is complete, the finish dialog box is displayed. Step 8 Click Finish. Step 9 Check that the file exists in the export path. The file is exported. ----End Issue 01 (2008-06-25)


7-131


7 Operating the CME

7.3.6 Managing a Cell Template File You can save the typical cell data as a template to facilitate the data configuration of other cells. Scenario

RNC initial configuration

Mandatory/ Optional. If required, save the typical cell data as a template. Optional

Prerequisite l

The cell data configuration is complete.

l

The cell data can be saved as a template only when the cell is in active state.

Preparation None.

Procedure Step 1 In the main window of the CME, choose Radio > Cell Template . The Show Cell Data window is displayed, as shown in Figure 7-107. Figure 7-107 Configuring a cell template

Table 7-16 Areas in the configuration interface

7-132

Area

Description

1

Displays the information about the NodeB that controls cell Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd

Issue 01 (2008-06-25)


7 Operating the CME

Area

Description

2

Displays the information about cell

3

Displays the selected level

4

Displays the cell data on the selected level

5

Displays the template data on the selected level

6

Displays the remarks related to the selected template

Step 2 In area 2, select a cell. The related information about the NodeB that controls the cell is displayed in area 1. In area 3, select a level. In area 4, select cell related information based on hierarchies. In area 5, select the template-related data based on hierarchies. In area 6, view the remarks of the selected template. NOTE

l

The default template in area 5 cannot be removed.

l

The cell template level is based on network planning, which is described as follows: l

First Level is the major level of parameters, such as AcPara (access-related parameter), HoPara (handover-related parameter), and ChPara (channel-related parameter).

l

Second Level is the sub-level of the first level parameters. For example, AcPara on the first level includes CellCChCfg, which is the parameter for cell common channels configuration.

l

Third Level is the sub-level of the second level parameters. For example, CellCChCfg on the second level includes CellPrachCfg (cell PRACH configuration), CellPrachTfc (TFC on the PRACH), and CellPrachSlotFormat (timeslot format on the PRACH).

Step 3 Click Save as Template. Enter the template name (defined by user), and then click OK. The cell data is saved as a template. Step 4 (Optional) Export a cell template. 1.

Click Export Template. Select the target cell template, and then click OK. A dialog box is displayed for specifying the saving path. NOTE

The cell template to be exported is an existing template in the CME. To add a new template, perform Step 3.

2.

Specify the saving path for the exported template and click Save. A dialog box is displayed indicating that the export is successful.

3.

Click OK. The cell template is saved to the local.

Step 5 (Optional) Import a cell template. 1.

Click Import Template. Select the target cell template, and then click Open. A dialog box is displayed for specifying the cell template name.

2.

Enter the cell template name and click OK. A dialog box is displayed indicating that the import is successful.

3.

Click OK. The cell template at the local is imported to the CME.

----End

Issue 01 (2008-06-25)


7-133


7 Operating the CME

7.3.7 Managing Hot NodeBs and Cells Hot NodeBs and cells refers to the NodeBs and cells where the traffic is heavy or the data modification is frequent. You can manage these NodeBs and cells conveniently by loading the prepared configuration files to the CME.

Prerequisite The configuration files for hot NodeBs and cells are ready.

Context The rules for the hot configuration files are as follows: The fields that can be matched in the CME are only the primary fields of NodeBs and cells. The configuration file can be in .xls or .txt format. You can define the field name in the file, such as NodeBId, NodeBName, and CellName. Ensure that the modified field names are consistent with those displayed on the CME. For the file in .xls format: l

The data must be filled in the first sheet.

l

The first row is filled with the field names. If a field is null, then the corresponding column and the following columns are not processed by the CME.

l

The rows from the second row are filled with the field values. If a row is null, then this row and the following rows are not processed by the CME.

For the file in .txt format: l

The neighbor columns are separated by a Tab key.

l

The first row is filled with the field names. If there are two consecutive Tab keys in this row, then the column corresponding to the second Tab key and the following columns are not processed by the CME.

Currently, such data filtering involves at least the following interface elements and primary operations: l

Modify cell frequency

l

Modify cell algorithm parameter

l

Delete object

l

Export MML commands

l

Compare cell algorithm parameters

l

Modify NodeB algorithm parameter

l

Reparent NodeB

l

Refresh Iub

l

Check Iub consistency

l

Accurate matching

Procedure

7-134


Issue 01 (2008-06-25)


7 Operating the CME

1.

In the batch modification dialog box where you can select the objects to be modified, click Load, as shown in Figure 7-108. Figure 7-108 Loading hot objects

2.

–

Recently selected file: used to select latest uploaded files. You can set the maximum number of files by clicking Options.

–

Select file: used to select a file to be loaded.

–

Options: used to set the menu.

Click Options. A dialog box is displayed, as shown in Figure 7-109. Figure 7-109 Setting attributes

3.

Clear the Show setting dialog check box.

4.

(Optional) Select the Show confirmation dialog check box. After the file load is finished, the CME displays the number of loaded files and the number of invalid files if you select this check box.

5.

Click Select file to select a file to be loaded. The CME starts to load the file. After the loading is finished, the CME displays the matched records in the area above the resource pool. The following figure shows an example file.

Issue 01 (2008-06-25)


7-135


7 Operating the CME

Figure 7-110 An example file for accurate matching

If multiple matching fields are used, the CME selects the intersection for matching. l

Fuzzy matching 1.

In the batch modification dialog box where you can select the objects to be modified, click Load, as shown in Figure 7-111. Figure 7-111 Loading hot objects

2.

7-136

–

Recently selected file: used to select latest uploaded files. You can set the maximum number of files by clicking Options.

–

Select file: used to select a file to be loaded.

–

Options: used to set the menu.

Click Options. A dialog box is displayed, as shown in Figure 7-112.


Issue 01 (2008-06-25)


7 Operating the CME

Figure 7-112 Setting attributes

3.

Select the Show setting dialog check box. By default, the CME performs accurate matching. Select this check box only when you require fuzzy matching.

4.

(Optional) Select the Show confirmation dialog check box. After the file load is finished, the CME displays the number of loaded files and the number of invalid files if you select this check box.

5.

Click Select file to select a file to be loaded. A dialog box is displayed, as shown in Figure 7-113. Figure 7-113 Setting the matching mode

Issue 01 (2008-06-25)


7-137


7 Operating the CME –

Fuzzy matching applies only to the string-type values. For example, to select the cells whose name includes the BX string, set CellName to BX in the file. Then, the CME can select all the cells whose name includes BX.

–

If multiple matching fields are used, the CME selects the intersection for matching.

–

The following figure shows an example file. Figure 7-114 An example file for accurate matching

----End

7.3.8 Exporting Cell Algorithm Parameters and Channel Data After you browse or modify the cell algorithm parameters and channel data, you can export the specified data in .xls format.

Prerequisite l


l

The cell algorithm parameters and channel data are configured and are valid.

Procedure

in the configuration object pane, and click Cell in the configuration task pane. Step 1 Click The Cell Basic Information window is displayed. Step 2 Click Cell Parameters. The Cell Channel window is displayed, as shown in Figure 7-115.

7-138


Issue 01 (2008-06-25)


7 Operating the CME

Figure 7-115 Browsing cell channel information

Step 3 Click Channel at the top of the window, and click Row Selection at the upper right of the window. Step 4 In the lower right pane, select one or more entries, right-click the entries, and then choose Export on the shortcut menu. The cell channel data is exported in .xls format. Step 5 Click Parameter at the top of the window, and then repeat the previous steps to export cell algorithm parameters. ----End

7.4 Comparing Radio Algorithm Parameters This describes how to compare the values of global algorithm parameters or cell algorithm parameters with the baseline values. The results of the comparison can help you identify the modified parameters. 7.4.1 Comparing RNC-Oriented Algorithm Parameters This describes how to compare the values of RNC-oriented algorithm parameters with the baseline values. The results of the comparison can help you identify the modified parameters. 7.4.2 Comparing Cell-Oriented Algorithm Parameters This describes how to compare the values of cell algorithm parameters with the baseline values. The results of the comparison can help you identify the modified parameters.

7.4.1 Comparing RNC-Oriented Algorithm Parameters This describes how to compare the values of RNC-oriented algorithm parameters with the baseline values. The results of the comparison can help you identify the modified parameters. Issue 01 (2008-06-25)


7-139


7 Operating the CME

Scenario

Routine maintenance

Impact

No impact on the current services carried on the RNC

NEs InvolvedRNC

Prerequisite l

An RNS is opened on the CME.

l

The data of the radio network layer is added.

Preparation None.

Procedure Step 1 In the main window of the CME, choose Advanced > Compare Radio Parameter > RNC Level Parameter . The Select Baseline dialog box is displayed. Step 2 If you select Use Default, the default values are used as baseline values for comparison. You can also select other RNS data as baseline values from the drop-down list. Click OK. The Global Params Compare window is displayed, as shown in Figure 7-116. Figure 7-116 Global Params Compare window

7-140


Issue 01 (2008-06-25)


7 Operating the CME

NOTE

l

Object Name: indicates the destination of an algorithm parameter.

l

Parameter Name: indicates the attribute parameter under an algorithm parameter target.

l

Current Value: indicates the current value.

l

Baseline Value: indicates the reference value. You can use the default settings of the current version or the settings of another project on the same server as the baseline values.

l

To export the data after the comparison, right-click in the blank area of the pane and then choose Export Data from the shortcut menu.

l

To browse the parameters, double-click the object record.

----End

7.4.2 Comparing Cell-Oriented Algorithm Parameters This describes how to compare the values of cell algorithm parameters with the baseline values. The results of the comparison can help you identify the modified parameters. Scenario

Routine maintenance

Impact

No impact on the current services carried on the RNC

NEs InvolvedRNC

Prerequisite l

An RNS is opened on the CME.

l

The data of the radio network layer is added.

Preparation None.

Procedure Step 1 In the main window of the CME, choose Advanced > Compare Radio Parameter > Cell Level Parameter. The Select Cell window is displayed. (Optional) You can also click Load to select cells by loading a user-defined file in the Select Cell window. For details, refer to 7.3.7 Managing Hot NodeBs and Cells. Step 2 In the resource pool, select a cell to be compared, and then select a cell template in the Template to compare drop-down list. Step 3 Click OK. The Cell Oriented Params Compare window is displayed, and the results of the comparison are shown.

Issue 01 (2008-06-25)


7-141


7 Operating the CME

Figure 7-117 Cell Oriented Params Compare window

NOTE

l

To export the data after the comparison, right-click in the blank area of the pane and then choose Export Data from the shortcut menu.

l

To browse required parameters, double-click the object record.

----End

7.5 Backing Up and Restoring an RNS This describes how to back up the RNS database by using the backup function of the CME or by importing the BCP file to the CME. In the case of data error or system failure, you can use the backup file to restore the RNS database. 7.5.1 Backing Up an RNS This describes how to back up an RNS database for data restoration on the standalone CME client. 7.5.2 Restoring an RNS This describes how to restoring the databases of an RNS by using the restoration function when the standalone CME is faulty. 7.5.3 Deleting a Backup File This describes how to delete a backup file. 7.5.4 Backing Up an RNS (bcp) When you need to back up or transfer RNS configuration data, you can export the BCP file in .zip format. 7.5.5 Storing an RNS (bcp) 7-142


Issue 01 (2008-06-25)


7 Operating the CME

This describes how to import a RNS backup file in .zip format to the CME. If the RNS data exists, it is overwritten.

7.5.1 Backing Up an RNS This describes how to back up an RNS database for data restoration on the standalone CME client.

Prerequisite l


l

The RNS to be backed up is closed.

Procedure Step 1 Choose System > Backup/Restore > Backup RNS in the main window. The Choose RNS dialog box is displayed. Step 2 Click the CME server in the RAN drop-down list. All the RNSs on the server are displayed in the dialog box, as shown in Figure 7-118. Figure 7-118 Selecting an RNS

Step 3 Select the RNS (or RNSs) to be backed up, and then click Next. The Specify File dialog box is displayed. NOTE

You cannot select an RNS that is open.

Step 4 In the File name box, enter the path where the backup file is to be stored. You can also click Browse to specify the path. The existing backup files and their paths are displayed in the dialog box, as shown in Figure 7-119. Issue 01 (2008-06-25)


7-143


7 Operating the CME

Figure 7-119 Specifying the path for the backup file

NOTE

The file path is located on the server.

Step 5 Click Next. The CME starts backing up the data. When the backup is complete, the finish dialog box is displayed. Step 6 Click Finish. The RNS is backed up. ----End

7.5.2 Restoring an RNS This describes how to restoring the databases of an RNS by using the restoration function when the standalone CME is faulty.

Prerequisite l


l

A backup file of the RNS is available.

Procedure Step 1 Choose System > Backup/Restore > Restore RNS in the main window. The Choose File dialog box is displayed. Step 2 Click the CME server in the RAN drop-down list. All the backup files of the RAN are displayed in the dialog box, as shown in Figure 7-120.

7-144


Issue 01 (2008-06-25)


7 Operating the CME

Figure 7-120 Selecting a backup file

Step 3 Select the backup file of the RNS to be restored, and then click Next. The ID and version of the RNS are displayed. The backup file may contain data of more than one RNS. Step 4 Select the check box of the RNS to be restored. Select the RNS ID, and then click the ID to edit it, as shown in Figure 7-121. Figure 7-121 Modifying the RNS ID

Issue 01 (2008-06-25)


7-145


7 Operating the CME

Step 5 Click Next. The CME starts restoring the data. When the restoration is complete, the finish dialog box is displayed. Step 6 Click Finish. The RNS is restored. ----End

7.5.3 Deleting a Backup File This describes how to delete a backup file.

Prerequisite l


l

A backup file of the RNS is available.

Procedure Step 1 Choose System > Backup/Restore > Delete Backup Files in the main window. The Choose RAN dialog box is displayed, as shown in Figure 7-122. Figure 7-122 Selecting the RAN

Step 2 Click the CME server in the RAN drop-down list, and then click Next. The Choose File dialog box is displayed, as shown in Figure 7-123.

7-146


Issue 01 (2008-06-25)


7 Operating the CME

Figure 7-123 Selecting a backup file

Step 3 In the Backuped files area, select the backup file to be deleted. The ID and version of the RNS contained in the backup file are displayed in the RNS in backuped file area. Step 4 Click Next. A message is displayed. Then click OK. The CME starts deleting the file. When the deletion is complete, the finish dialog box is displayed. Step 5 Click Finish. The backup file is deleted. ----End

7.5.4 Backing Up an RNS (bcp) When you need to back up or transfer RNS configuration data, you can export the BCP file in .zip format.

Prerequisite 7.1.7 Closing an RNS is complete.

Context bcp:A command prompt bulk copy utility that copies SQL Server data to or from an operating system file in a user-specified format. A backup file contains all the configuration data in the corresponding RNS. The data includes that of the interfaces, of the RNC equipment, and of the NodeB equipment.

Procedure Step 1 Choose System > Data Import/Export > Data Export in the main window. The Choose RNS dialog box is displayed, as shown in Figure 7-124. Issue 01 (2008-06-25)


7-147


7 Operating the CME

Figure 7-124 Selecting RNSs

Step 2 Select the RNS from which the backup file is exported, and then click Next. The Specify File dialog box is displayed. Step 3 Enter the export path, and then click Next. The CME starts exporting the data. When the export is complete, the Finish dialog box is displayed. NOTE

The data of an opened RNS cannot be exported.

----End

7.5.5 Storing an RNS (bcp) This describes how to import a RNS backup file in .zip format to the CME. If the RNS data exists, it is overwritten.

Prerequisite l

7.1.7 Closing an RNS is complete.

l

The backup file is available.

Context bcp:A command prompt bulk copy utility that copies SQL Server data to or from an operating system file in a user-specified format. A backup file contains all the configuration data in the corresponding RNS. The data includes that of the interfaces, of the RNC equipment, and of the NodeB equipment. This file can be imported into any RNC with the same version. Ensure that, however, the NodeB versions involved in this backup file exist in the RNS project on the CME. 7-148


Issue 01 (2008-06-25)


7 Operating the CME

The data in the original RNS project is overwritten by the data in the backup file.

Procedure Step 1 Choose System > Data Import/Export > Data Import in the main window. The Choose File dialog box is displayed. Step 2 Select a backup file, and then click Next. The Choose RNS dialog box is displayed, as shown in Figure 7-125. Figure 7-125 Selecting a target RNS

Step 3 Select the RNC into which the backup file is imported, and then click Next. The CME starts importing the data. When the import is complete, the Finish dialog box is displayed. ----End

7.6 Searching and Browsing Data The CME supports panorama browsing and searching of data. You can browse the configuration data of various objects, such as the NodeB status, cell status, Iub interface in different transmission modes, neighboring cell information, and neighboring relations between cells.

Prerequisite The configuration data already exists.

Issue 01 (2008-06-25)


7-149


7 Operating the CME

Context The user can search or browse data based on RAN or based on a single RNS. When the RNS is open, the CME opens the current RNS browsing window by default. When all the RNSs are closed, the CME opens the RAN browsing window by default.

Procedure Step 1 In the main window of the CME, choose View > RAN Panoramic Browser . The RAN Panorama Browser window is displayed, as shown in Figure 7-126. Figure 7-126 Panorama browser window

Step 2 From the navigation tree in the left pane, select the configuration object to be browsed. Step 3 (Optional) Sort the browsing data. 1.

7-150

Click Sort. The Multiple Fields Sort dialog box is displayed, as shown in Figure 7-127.


Issue 01 (2008-06-25)


7 Operating the CME

Figure 7-127 Specifying sorting fields (1)

2.

In the Field List sheet, select the data items to be sorted, and click . The data items are displayed in the Sorting Field List sheet, as shown in Figure 7-128. Figure 7-128 Specifying sorting fields (2)

3.

Issue 01 (2008-06-25)

Select one or more fields in the Sorting Field List area for item sorting in ascending order, or clear one or more fields for item sorting in descending order. Click OK to return to the RAN Panorama Browser window, as shown in Figure 7-129.


7-151


7 Operating the CME

Figure 7-129 Panorama browser window

In the window, the items in a blue column are sorted in ascending order, and the items in a yellow column are sorted in descending order. Step 4 (Optional) Enter a search condition in the Filter Condition field and click Filter. The filtering results are displayed. l

Enter a parameter name in format of [XXX]. The name is case insensitive.

l

Use mathematical symbols, such as >, <, >=, and <= to represent comparison.

l

Use 'and' with a space on both side to combine multiple conditions.

Step 5 (Optional) Click Locate, and then enter the locating condition in the Find dialog box displayed. The CME automatically locates the qualified records. The CME does not support a combination of locating conditions. Step 6 (Optional) Hide or display parameters. 1.

Right-click in the configuration area, and then select Column Setting from the shortcut menu. The Columns Setting dialog box is displayed.

2.

Select the items to be hidden in the Columns List area, and then click items are displayed in the Selected to hide area.

3.

Click OK. The panorama browser window only displays the unhidden items.

. The related

Step 7 (Optional) Right-click in the configuration area, and then select Export data to CSVfrom the shortcut menu. In the displayed dialog box, specify the saving path and click Save. The file is exported in .csv format. ----End

7-152


Issue 01 (2008-06-25)

Wran Cme User Guide-(v100r005_01)

Recommend Documents