sjzl20092866-netnumen m31 (ran) (v3[1].10.420) centralized management operation guide

NetNumen M31(RAN)Mobile Network Element Management System

Centralized Management Operation Guide

Version 3.10.420

ZTE CORPORATIONZTE Plaza, Keji Road South,Hi-Tech Industrial Park,Nanshan District, Shenzhen,P. R. China518057Tel: (86) 755 26771900Fax: (86) 755 26770801URL: http://ensupport.zte.com.cnE-mail: [email protected]

LEGAL INFORMATION

Copyright 2006 ZTE CORPORATION.

The contents of this document are protected by copyright laws and international treaties. Any reproduction or distribution ofthis document or any portion of this document, in any form by any means, without the prior written consent of ZTE CORPO-RATION is prohibited. Additionally, the contents of this document are protected by contractual confidentiality obligations.

All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE CORPORATIONor of their respective owners.

This document is provided as is, and all express, implied, or statutory warranties, representations or conditions are dis-claimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose, title or non-in-fringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the use of or reliance on theinformation contained herein.

ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications covering the subjectmatter of this document. Except as expressly provided in any written license between ZTE CORPORATION and its licensee,the user of this document shall not acquire any license to the subject matter herein.

ZTE CORPORATION reserves the right to upgrade or make technical change to this product without further notice.

Users may visit ZTE technical support website http://ensupport.zte.com.cn to inquire related information.

The ultimate right to interpret this product resides in ZTE CORPORATION.

Revision History

Revision No. Revision Date Revision Reason

R1.1 July 20, 2009 Review and Test Comments Modification

R1.0 June 29, 2009 First Edition

Serial Number: sjzl20092866

Contents

Preface............................................................... i

Centralized Config-uration Management

Overview...........................................................1Centralized Configuration Management Introduction ............ 1

Centralized Configuration Management Operations .............. 1

Centralized Configuration Management

Operations ........................................................3Inventory Unit Management............................................. 3

Importing Inventory Unit Data...................................... 3

Exporting Inventory Unit Data ...................................... 5

Synchronizing Inventory Unit Data................................ 6

Exporting Inventory Unit Data Based on Condition .......... 8

Adding Data in Inventory Unit .....................................10

Updating Inventory Unit Data......................................12

Modifying Inventory Data ...........................................14

Base Station Data Transfer Operation Platform ..................15

Transferring Base Station Data Online ..........................16

Transferring Base Station Data Offline ..........................18

Transferring Base Station Data Directly.........................20

Inter NEs Batch Comparing.............................................21

Exporting BTS Owner File ...........................................22

Importing BTS Owner File ...........................................24

Comparing Inter NEs..................................................26

Maintenance Status Retrieving and Setting .......................28

Kinds of Maintenance Status .......................................28

Displaying Maintenance Status of NodeB.......................29

Setting Maintenance Status ........................................31

NodeB ID Uniqueness Check ...........................................32

Exporting Configuration Data Statistics Report...................35

Adjacent Cell Relationship Consistency Checking................38

Figures ............................................................41

Tables .............................................................43

Glossary ..........................................................45

Preface

Purpose This manual explains the NetNumen M31(RAN)Centralized Config-uration Management operations like Inventory unit management,Base Station data transfer, Inter NEs batch compare, Maintenancestatus retrieving and setting, NodeB ID uniqueness check, export-ing configuration data statistics operations and adjacent cell rela-tionship checking.

IntendedAudience

This manual is intended for technical managers, engineers andtechnicians who perform different operations on NetNumenM31(RAN) Mobile Network Element Management System.

Prerequisite Skilland Knowledge

To use this document effectively, users should have a general un-derstanding of wireless telecommunications technology. Familiar-ity with the following is helpful:

ZXG10 BSS and/or ZXWR RAN and/or ZXTR RAN system andits various components

What Is in ThisManual

This manual contains the following chapters:

TABLE 1 CHAPTER SUMMARY

Chapter Summary

Chapter 1, CentralizedConfigurationManagement Overview

Provides general information of thecentralized configuration management.

Chapter 2, CentralizedConfigurationManagement Operations

Explains Inventory Unit Managementoperations, Base Station data transferoperation, Inter NEs batch comparison,Maintenance Status Retrieving and Setting,NodeB ID uniqueness check, exportingconfiguration data statistics operations andchecking adjacent cell relationship.

Confidential and Proprietary Information of ZTE CORPORATION i

NetNumen M31(RAN) Centralized Management Operation Guide

This page is intentionally blank.

ii Confidential and Proprietary Information of ZTE CORPORATION

C h a p t e r 1

Centralized Config-uration ManagementOverview

Table of ContentsCentralized Configuration Management Introduction................ 1Centralized Configuration Management Operations.................. 1

Centralized ConfigurationManagement IntroductionNetNumenM31 (RAN) provides centralized configuration manage-ment operations to configure or maintain one or more lower levelnetwork elements simultaneously. Centralized Configuration Man-agement can perform some operations that cannot be handle byOMM alone.

Centralized ConfigurationManagement OperationsCentralized configuration management operations are explained inTable 2.

Confidential and Proprietary Information of ZTE CORPORATION 1


TABLE 2 CENTRALIZED CONFIGURATION MANAGEMENT OPERATIONS

Operations Description

Inventory Unit Management Inventory Unit Managementmanages some boards data whichare uploaded by low level OMMs.

Base Station Transfer OperationPlatform

While shifting BS from one RNCto another RNC, user can use thisfeature to transfer BS data fromone RNC to another RNC.

NodeB ID Uniqueness Check For checking NodeB ID uniquenessin TD-SCDMA network.

Inter NEs Batch Comparison For comparing link parametersbetween RNC-NodeB, RNC-SDR inWCDMA network and iBSC- SDRin GSM network.

Maintain Status Search & Setting Retrieving, checking and Settingthe BS status in WCDMA network.

Adjacent Relation Checking Tool Checking and modifying adjacentcell relationship parameters.

NE data Batch Operation Uploading and synchronizing NEdata in WCDMA network.

Export Configuration Data StatisticReport

Exporting configuration data staticreport from low level NEs.

2 Confidential and Proprietary Information of ZTE CORPORATION

C h a p t e r 2

Centralized Configuration ManagementOperations

Table of ContentsInventory Unit Management................................................. 3Base Station Data Transfer Operation Platform ......................15Inter NEs Batch Comparing.................................................21Maintenance Status Retrieving and Setting ...........................28NodeB ID Uniqueness Check ...............................................32Exporting Configuration Data Statistics Report.......................35Adjacent Cell Relationship Consistency Checking....................38

Inventory Unit ManagementInventory Unit Management manages some boards data, which isuploaded by OMM. Normally NE uploads data to OMM, then OMMuploads data to NetNumen. In this situation some data cannot beuploaded by OMM because these data might not be received fromnetwork element. Missing data can be added or deleted in Net-NumenM31 manually for user reference. After data modification,during NetNumen data synchronization with OMM, the modifieddata, which is uploaded from OMM will be overwritten. InventoryUnit Management also checks the connection between OMM andNetNumenM31.

Importing Inventory Unit Data

Short Description To import inventory unit data

Prerequisites Ensure the following:

The NetNumenM31 server is started, connected to the client,and the system is running normally.

Topology Management interface is open.

Context Perform the following steps to import inventory data:



Steps 1. On menu bar, click Topology > InventoryUnitManage-ment, as shown in Figure 1.

FIGURE 1 NAVIGATING TO INVENTORY UNIT MANAGEMENT

2. InventoryUnitManagement window pops up, as shown inFigure 2.

FIGURE 2 INVENTORY UNIT MANAGEMENT INTERFACE (IMPORT)

3. In InventoryUnit Management window, on menu bar, clickFile > Import, and then select the file from local drive to


Chapter 2 Centralized Configuration Management Operations

import. Format the file before importing. Currently systemsupports .csv format.

END OF STEPS

Result Inventory Unit Data is imported successfully.

Exporting Inventory Unit Data

Short Description To export inventory unit data.




Inventory unit data should exist.

Context Perform the following steps to export inventory unit data.



2. InventoryUnit Management interface displays. Select thefile from InventoryUnit Management window and then clickExport button, or on menu bar, click File > Export, as shownin Figure 4.



FIGURE 4 INVENTORYUNIT MANAGEMENT INTERFACE (EXPORT)-II

3. Save dialog box appears, as shown in Figure 5. Select direc-tory, enter filename and then click Save button. Files can beexported only in .csv format.

FIGURE 5 SAVE DIALOG BOX

END OF STEPS

Result Exporting Inventory unit data is completed successfully.

Synchronizing Inventory Unit Data

Short Description To synchronize all OMMs inventory unit data with NetNumenM31.






Context Perform the following steps to synchronize inventory unit data:



2. InventoryUnit Management interface displays, on Inven-toryUnit Management menu bar, click Operation > Inven-toryUnit Synchronise, as shown in Figure 7.

FIGURE 7 INVENTORY UNIT MANAGEMENT INTERFACE (SYNCHRONISE)



3. After synchronizing with OMM , data displays, as shown in Fig-ure 8

FIGURE 8 DATA AFTER SYNCHRONIZATION

END OF STEPS

Result All OMMs inventory unit data is synchronized successfully withNetNumenM31.

Exporting Inventory Unit Data Basedon Condition

Short Description Setting parameters in inventory unit management interface for ex-porting data. This operation can be done in TD-SCDMA, GSM andWCDMA networks.




Context Perform the following steps to set conditions for exporting data.





2. InventoryUnitManagement window pops-up, as shown inFigure 10.

FIGURE 10 INVENTORY UNIT MANAGEMENT INTERFACE (EXPORT ONTIME)

3. On InventoryUnit Management menu bar, click Operation> Export_On_Time, Export File Task window appears. Setthe parameters of Export_time, File Type (NetNumen supportonly .xml and .csv formats), Data Type (select network typeTD-SCDMA, GSM or WCDMA), and then click OK to save thesettings, as shown in Figure 11.



FIGURE 11 EXPORT FILE TASK

END OF STEPS

Result Conditions are set successfully to export data.

Adding Data in Inventory Unit

Short Description To add data to inventory unit.




Note:

All the data from OMM cannot be uploaded to NetNumenM31server, the data, which is not exported from OMM to server canbe entered in NetNUmenM31 server manually.

Context Perform the following steps to add data to Inventory Unit:





2. Inventory Unit Management Interface appears, on Inven-tory Unit Management interface menu bar, click Operation> Add, as shown in Figure 13.

FIGURE 13 INVENTORY UNIT MANAGEMENT INTERFACE (ADD)

3. Add a InventoryUnit window appears. Add the inventoryunits, as shown in Figure 14. Click OK. In Add a Inven-tory Unit window Inventory Unit Type, Venodr Unit TypeNumber, , Vendor Name, Venodr Number, Serial Num-ber, Version Number, Unit Position, and NE parametersare mandatory to fill, rest are optional.



FIGURE 14 ADDING INVENTORY UNIT

END OF STEPS

Result Data is added successfully in Inventory Unit.

Updating Inventory Unit Data

Short Description To synchronize the NetNumen server with particular OMM.




Context Perform the following steps to Update Inventory unit data:





2. InventoryUnitManagement window pops up. Select the re-quired OMM and then click Update button, successful Mes-sage window appears as shown in Figure 16. Selected OMMsynchronizes with NetNumenM31 server.

FIGURE 16 UPDATING INVENTORY UNIT DATA

END OF STEPS

Result NetNumenM31 server is synchronized successfully with requiredOMM.



Modifying Inventory Data

Short Description To modify existing data in inventory unit.




Context Perform the following steps to modify inventory unit data:



2. InventoryUnitManagement window pops-up, as shown inFigure 18. Change one or several required data and then clickChange button to save changes.



FIGURE 18 MODIFYING INVENTORY UNIT DATA

3. Save dialog box appears. Click OK, as shown in Figure 19.


END OF STEPS

Result Inventory Unit data is modified successfully.

Base Station Data TransferOperation PlatformWhile shifting Base Station from one RNC to another RNC withinthe same kind of network, user can use this feature to transfer



Base Station data from one RNC to another RNC. Data transfercan be online, offline or directly.

Transferring Base Station DataOnline

Short Description To transfer configuration data from one Base Station to anotherBase Station in online mode.



Server, OMM and Base Station are interconnected.

Source Base Stations configuration data exists.

Target RNCs information exists.


Base Station Transfer interface is open.

Note:

In online mode, before shifting base station from one RNC to an-other RNC, user can modify the source base stations configurationdata.

Context Perform the following steps to transfer configuration data in onlinemode:

Steps 1. From Topology Management window, select Topology >Basestation Trasfer Operation Platform, as shown in Fig-ure 20



FIGURE 20 NAVIGATING TO BASE STATION TRANSFER WINDOW

2. On Base Station Transfer window, select Source Amo,Source Subnetwork, Source ME, Base Station and thenclick Transfer button, as shown in Figure 21.

FIGURE 21 BASE STATION TRANSFER

3. Transfer window appears for confirmation, click Yes button,as shown in Figure 22



FIGURE 22 TRANSFER WINDOW

4. Modify the Basestaion Attributes window appears, user canmodify the attributes and then select Destination Amo, Des-tination Subnetwork and Destination ME. Click Save but-ton to save the attributes in local disk andOK button to transferthe configuration data to destination Base Station, as shown inFigure 23

FIGURE 23 MODIFY THE BASE SSTATIONS ATTRIBUTES

END OF STEPS

Result Base Stations configuration data is transferred successfully in on-line mode.

Transferring Base Station DataOffline

Short Description To transfer configuration data from one Base Station to anotherBase Station in offline mode.






Source Base Stations Transfer data exists.




Note:

In offline mode, user can modify the source Base Stations config-uration data before transferring to destination Base Station

Context Perform the following steps to transfer configuration data in offlinemode:

Steps 1. On Base Station Transfer window, select Transfer Offlinebutton, Open window appears. Select configuration data fileand then click Open button, as shown in Figure 24

FIGURE 24 BASE STATION TRANSFER WINDOW

2. Choose the file window appears for confirmation. Click Yes,as shown in Figure 25.

FIGURE 25 CHOOSING FILE

3. Modify the baseStations Attributes window appears. Se-lect Destination Amo, Destinations Subnetwork, Desti-nation ME and BaseStation and then click OK, as shown inFigure 26.



FIGURE 26 MODIFY THE BASESTATIONS ATTRIBUTE

END OF STEPS

Result In offline mode, configuration data transferred successfully.

Transferring Base Station DataDirectly

Short Description To transfer configuration data from one Base Station to anotherBase Station directly without any modification.




Source Base Stations transfer data exists.




Note:

In direct mode, use can transfer unmodified configuration datafrom one Base Station to another Base Station directly.

Context Perform the following steps to transfer configuration data directly:

Steps 1. On Base Station Transfer window, select Direct Transferbutton, thenOpen window appears. Select configuration datafile and then click Open button, as shown in Figure 27.



FIGURE 27 BASE STATION TRANSFER WINDOW

2. Choose the file window appears. Click Yes, as shown in Fig-ure 28.

FIGURE 28 CHOOSING FILE WINDOW

3. Direct Transfer window appears. Select Aim Amo, AimSubnetwork, Aim ManageElement and then click OKbutton, as shown in Figure 29.

FIGURE 29 DIRECT TRANSFER

END OF STEPS

Result Unmodified configuration data is transferred directly to destinationBase Station.

Inter NEs Batch ComparingComparing the link parameters between RNC-NodeB, RNC-SDR inWCDMA network and SDR-iBSC in GSM network.



Before comparing two NEs, engineer should import the link rela-tionship owner file, as shown in Table 3

TABLE 3 OWNER FILE OF PARTICULAR NE

SUBNETWOR-KID:SDRID (SDR)

RNCID (3G) SUBNETWOR-KID:BSCID (2G)

1234:0 1234

1234:1 1234

1234:1234 1234

Table 3 shows, subnetwork ID 1234s link relationship with 0 , 1SDRIDs and RNCID 1234.

Contents of the owner file should be in text format, before upload-ing, as shown in Figure 30.

FIGURE 30 OWNER FILE FORMAT

Exporting BTS Owner File

Short Description To export BTS owner file.



NetNumen, Client and NEs are interconnected.


Context Perform the following steps to export owner file:

Steps 1. Select the NE and then on menu bar, click Topology > OutputBTS owner file, as shown in Figure 31.



FIGURE 31 NAVIGATING TO OUTPUT BTS OWNER FILE

2. Save window appears. Enter the path name, file name andthen click Save button, as shown in Figure 32. NetNumensupports only .xml file format.

FIGURE 32 SAVE WINDOW

3. Hint window appears. Click OK, as shown in Figure 33.



FIGURE 33 HINT WINDOW

END OF STEPS

Result BTS Owner file is exported successfully.

Importing BTS Owner File

Short Description To import BTS owner file.



NetNumen, Client and NEs are interconnected.


Context Perform the following steps to import owner file:

Steps 1. Select the NE and then on menu bar, click Topology > InputBTS owner file, as shown in Figure 34.

FIGURE 34 NAVIGATING TO INPUT BTS OWNER FILE



2. Input BTS owner file window appears. Click on button,as shown in Figure 35.

FIGURE 35 INPUT BTS OWNER FILE

3. Open window appears. Select file and then click Open button,as shown in Figure 36. Contents of .xml file should be in textformat.

FIGURE 36 OPEN WINODW

4. Click OK, as shown in Figure 37.

FIGURE 37 INPUT BTS OWNER FILE



END OF STEPS

Result Owner file is imported successfully.

Comparing Inter NEs

Short Description To compare inter NEs link parameters.



NetNumen Sever, Client and NEs are interconnected.


Context Perform the following steps to compare inter NEs parameters:

Steps 1. On NE, right click and then select InterNEs Batch Compare,as shown in Figure 38.

FIGURE 38 NAVIGATING TO INTERNES BATCH



2. InterNEs Batch Compare window displays. Select the NEand click Compare button, as shown in Figure 39.

FIGURE 39 INTERNES BATCH COMPARISON

3. InterNEs Batch Compare window displays. User can com-pare the link parameters. If link parameters are different withsource NE and destination NE , then system highlights with dif-ferent colors, as shown in Figure 40.



FIGURE 40 INTERNES BATCH COMPARE

END OF STEPS

Result Inter NEs link parameters are compared successfully.

Maintenance StatusRetrieving and SettingUsing this feature user can check and set Base Station status. Cur-rently NetNumenM31 support only WCDMA NodeBs.

Kinds of Maintenance Status

There are three kinds of NodeB status:

Normal

Testing

NodeB is not configured or the link between OMM and NetNu-men may be down



Displaying Maintenance Status ofNodeB

Short Description To display maintenance status of NodeBs.

Prerequisites Ensure the followings:




Context Perform the following steps to get maintenance status of NodeBs:

Steps 1. Right click subnetwork and then select Maintain StatusSearch and Set, as shown in Figure 41.



FIGURE 41 NAVIGATING TO MAINTAIN STATUS SEARCH AND SET

2. Maintain Status Search and Set window appears. ClickSearch button to get the maintenance status of all NodeBs,as shown in Figure 42.



FIGURE 42 MAINTAIN STATUS SEARCH AND SET WINDOW

END OF STEPS

Result Maintenance status is displayed successfully.

Setting Maintenance Status

Short Description To set NodeB status.





Maintain Status Search and Set window is open.

Context Perform the following steps to set status of NodeB:

Steps 1. For setting allNodeBs Maintenance Element Status toNor-mal, click SetAllNormal button.

2. For setting all NodeBs Maintenance Element Status toTesting, click SetAllTesting button.

3. For setting selected NodeBs Maintenance Element Statusto Normal, click SetCurCellNormal button.

4. For setting selected NodeBs Maintenance Element Statusto Testing, click SetCurCellTesting button.

5. Set All Normal, Set All Testing, Set cur Cell Normal, SetCur Cell Testing, Search, and Cancel buttons are, as shownin Figure 43.



FIGURE 43 MAINTENANCE STATUS SEARCH AND SET

END OF STEPS

Result Maintenance status is set successfully.

NodeB ID UniquenessCheck

Short Description To Check NodeB ID uniqueness.





Note:

Currently, this feature supports only TD-SCDMA Network.

Context Perform the following steps to check NodeB ID uniqueness:



Steps 1. On menu bar, click Topology > NodeB ID UniquenessCheck, as shown in Figure 44.

FIGURE 44 NAVIGATING TO NODEB ID UNIQUENESS CHECK

2. If there are no repeated NodeB IDs, Message dialog box ap-pears, as shown in Figure 45 . Click OK.

FIGURE 45 MESSAGE DIALOG BOX

3. If there are repeated NodeB IDs,Message dialog box appears,as shown in Figure 46 . Click OK.




4. If there are no repeated NodeB IDs, NodeB ID UniquenessCheck window appears, as shown in Figure 47.

FIGURE 47 SINGLE RNC NODEB ID UNIQUENESS CHECK

5. If there are repeated NodeB IDs, NodeB ID UniquenessCheck window appears, as shown in Figure 48. In Figure 48NodeB ID 111 exists both under RNC ID 3 and RNC ID 20.



FIGURE 48 MULTIPLE RNCS NODEB ID UNIQUENESS CHECK

END OF STEPS

Result NodeB ID Uniqueness is checked successfully.

Exporting ConfigurationData Statistics Report

Short Description To export configuration data statistic report.





Context Perform the following steps to export configuration data statisticsreport:

Steps 1. On menu bar, click Topology > Export Config Data StatisticReport, as shown in Figure 49.



FIGURE 49 NAVIGATING TO EXPORT CONFIG DATA STATISTIC REPORT

2. Job starts to run on background, Message dialog box ap-pears and then click OK, as shown in Figure 50.


3. Choose the destination path to store exported file and thenclick Open, as show in Figure 51.




4. Enter File Name and then click Save, as shown in Figure 52.


5. Successful export Message dialog box appears. Click OK, asshown in Figure 53.




6. GSM, TD-SCDMA and WCDMA Configuration Data Report inthree different sheets displays, as shown in Figure 54.

FIGURE 54 CONFIG DATA REPORT

END OF STEPS

Result Configuration data is exported successfully.

Adjacent Cell RelationshipConsistency Checking

Short Description To check adjacent cell relationships. (This feature needs the coop-eration between OMM and NetNUmen, so required OMM must beconnected with NetNumen).




Context Adjacent cell relationship checking is mainly in command mode,some of the commands are explained below:minos cmd:type= " CheakCell ", ATTRIB= " TD " & " Compare " & " RelationSingle ";minos cmd:type= " CheakCell ", ATTRIB= " TD " & " Compare " & " Attribute ";minos cmd:type= " CheakCell ", ATTRIB= " TD " & " Compare " & " All ";minos cmd:type= " CheakCell ", ATTRIB= " TD " & " Modify " & " RelationSingle ";minos cmd:type= " CheakCell ", ATTRIB= " TD " & " Modify " & " Attribute ";minos cmd:type= " CheakCell ", ATTRIB= " TD " & " Modify " & " All ";

Commands Explanation

Mino comd:type = CheakCell means to check adjacent rela-tionship of cell.



ATTRIB is kind of network (GSM/W/TD) to compare/modify withutrancell or along with extranal utran cell.

RelationSingle means, check single adjacent cell relationship

Attribute checks whether the properties of Utrancell has the samevalue with its corresponding external adjacent linked Utrancel.

All means, check both RelationSingle and Attribute

Compare means, get the comparison result from NetNumen andOMM

Modify means, partner up the single adjacent cell relationship ormake the attribute of Utrancells same with this corresponding ex-ternal Utrancell or both

Perform the following steps to check adjacent cell relationship:

Steps 1. In command mode, connect to NetNumenM31 server port2121, as shown in Figure 55.

FIGURE 55 CONNECTING TO SERVER

2. Enter username and password, as shown in Figure 56.

FIGURE 56 ENTERING USERNAME AND PASSWORD

3. Set NE type=minos, as shown in Figure 57.



FIGURE 57 SETTING NE TYPE

4. Enter the MML command to get adjacent cell relationships, asshown in Figure 58.

FIGURE 58 ENTERING MML COMMAND

5. After executing MML command, system generates files in csvformat. User can open this file using Excel.

END OF STEPS

Result Adjacent cell relationship parameters are checked successfully.


Figures

Figure 1 Navigating to Inventory Unit Management ................. 4

Figure 2 Inventory Unit Management Interface (Import) .......... 4


Figure 4 InventoryUnit Management Interface (Export)-II ........ 6

Figure 5 Save Dialog Box..................................................... 6


Figure 7 Inventory Unit Management Interface (Synchronise)... 7

Figure 8 Data After synchronization ...................................... 8


Figure 10 Inventory Unit Management Interface (Export On

Time)................................................................ 9

Figure 11 Export File Task...................................................10

Figure 12 Navigating to Inventory Unit Management ..............11

Figure 13 Inventory Unit Management Interface (Add)............11

Figure 14 Adding Inventory Unit ..........................................12


Figure 16 Updating Inventory Unit Data................................13


Figure 18 Modifying Inventory Unit Data...............................15

Figure 19 Save Dialog Box ..................................................15

Figure 20 Navigating to Base Station Transfer Window............17

Figure 21 Base Station Transfer ...........................................17

Figure 22 Transfer Window..................................................18

Figure 23 Modify the Base Sstations Attributes......................18

Figure 24 Base Station Transfer Window ...............................19

Figure 25 Choosing File ......................................................19

Figure 26 Modify the BaseStations Attribute .........................20

Figure 27 Base Station Transfer Window ...............................21

Figure 28 Choosing File Window ..........................................21

Figure 29 Direct Transfer ....................................................21

Figure 30 Owner file format ................................................22

Figure 31 Navigating to Output BTS Owner File......................23

Figure 32 Save Window......................................................23

Figure 33 Hint Window .......................................................24



Figure 34 Navigating to Input BTS Owner File........................24

Figure 35 Input BTS Owner File ...........................................25

Figure 36 Open Winodw .....................................................25

Figure 37 Input BTS owner file ............................................25

Figure 38 Navigating to InterNEs Batch ................................26

Figure 39 InterNEs Batch Comparison ..................................27

Figure 40 InterNEs Batch Compare ......................................28

Figure 41 Navigating to Maintain Status Search and Set .........30

Figure 42 Maintain Status Search and Set Window .................31

Figure 43 Maintenance Status Search and Set .......................32

Figure 44 Navigating to NodeB ID Uniqueness Check..............33

Figure 45 Message Dialog Box .............................................33

Figure 46 Message Dialog Box .............................................33

Figure 47 Single RNC NodeB ID Uniqueness Check.................34

Figure 48 Multiple RNCs NodeB ID Uniqueness Check .............35

Figure 49 Navigating to Export Config Data Statistic Report.....36

Figure 50 Message dialog box..............................................36

Figure 51 Save Dialog box ..................................................37

Figure 52 Save Dialog Box ..................................................37

Figure 53 Message dialog box..............................................37

Figure 54 Config Data Report ..............................................38

Figure 55 Connecting to server............................................39

Figure 56 Entering username and password ..........................39

Figure 57 Setting NE Type ..................................................40

Figure 58 Entering MML Command.......................................40


Tables

Table 1 Chapter Summary .................................................... i

Table 2 Centralized Configuration Management Operations ....... 2

Table 3 Owner file of particular NE .......................................22



This page is intentionally blank.


Glossary

BSC - Base Station Controller

BTS - Base Transceiver Station

GSM - Global System for Mobile communication

NE - Network Element

OMM - Operation & Maintenance Module

RNC - Radio Network Controller

SDR - Software Defined Radio

TD-SCDMA - Time Division Synchronous CDMA

WCDMA - Wideband Code Division Multiple Access


Preface1 Centralized Config-uration Management OverviewCentralized Configuration Management IntroductionCentralized Configuration Management Operations

2 Centralized Configuration Management OperationsInventory Unit ManagementImporting Inventory Unit DataExporting Inventory Unit DataSynchronizing Inventory Unit DataExporting Inventory Unit Data Based on ConditionAdding Data in Inventory UnitUpdating Inventory Unit DataModifying Inventory Data

Base Station Data Transfer Operation PlatformTransferring Base Station Data OnlineTransferring Base Station Data OfflineTransferring Base Station Data Directly

Inter NEs Batch ComparingExporting BTS Owner FileImporting BTS Owner FileComparing Inter NEs

Maintenance Status Retrieving and SettingKinds of Maintenance StatusDisplaying Maintenance Status of NodeBSetting Maintenance Status

NodeB ID Uniqueness CheckExporting Configuration Data Statistics ReportAdjacent Cell Relationship Consistency Checking

FiguresTablesGlossary

sjzl20092866-netnumen m31 (ran) (v3[1].10.420) centralized management operation guide

Documents

inventory data

exporting inventory

zte corporationor

transferring base station

invento unit management

zte corporationzte plaza

distribution ofthis

revision historyrevision