Huawei Omc Operation Wcdma

WCDMA OMC Operation Guide Internal Open Product name

Confidentiality level

WCDMA RNP

For internal use only

Product version

Total 220 pages

3.5

WCDMA OMC Operation Guide (For internal use only)

Prepared by

Hu Mingchao

Date

Reviewed by

Hua Yunlong, Xie Zhibin, Wang Xiangxiong, Ai Hua, and Yan Lin

Date

Reviewed by

Qin Yan

Date

Approved by

2004-11-26

Date

Huawei Technologies Co., Ltd. All rights reserved.

2007-12-13

All rights reserved

Page1 , Total220

WCDMA OMC Operation Guide Internal Open

Revision Records Date 2004-11-26

Version

Description

Author

1.00

Initial transmittal.

Hu Mingchao

2005-01-29

1.10

Supplementing precautions in equipment room and routine data collection.

Chen Xin

2005-03-15

1.20

2005-05-05

1.30

2005-05-25

1.40

Supplementing alarms and revising part of traffic measurement.

Sun Daming

1.50

Adding time control of CR flow, viewing cell states executing the DSP command after cells are activated.

Zhang Youbin

2.00

Recompiling and adjusting chapters according to RNP&O equipment room operations guide of S project. Merging similar chapters, dividing sub-product to different blocks, rewriting and unifying style of the Hu Mingchao document. Revising it to common operation guidebook of WCDMA product in equipment room and adding bill extraction of core network and tracing of single subscriber

2005-06-14

2.01

Adjusting CR flow to appendix upon suggestion from Xie Zhibin, adjusting chapters about RTWP to operation and maintenance (OM) of NodeB, adjusting chapters about alarm to related operations on NodeB Hu Mingchao in M2000, and adjusting OM unit of core network to front chapters. Adding links to routine tasks in equipment room

2005-06-22

2.02

2005-11-21

3.0

2006-06-16

3.1

Supplementing IOS tracing in section 2.10 “Other Optimizations of Zhang Youbin BSC6800” of the RNC1.6 version Adding the method of updating NodeB address databases (UMSCUI files) in section 4.1 “Starting Remote OM of NodeB” Adding section 8.5.3 “Tracing and Viewing CDT” in the appendix Supplementing HSDPA-related commands in section 2.7 “BSC6800 MML Command Line” Supplementing HSDPA-related commands in section 4.3 “NodeB MML Commands” Supplementing the method of keeping code words in section 4.4 “Starting/Stopping and Querying Simulated Load on NodeB”

2006-11-10

3.1

1.Supplementing the operation guide of tracing MNCDT in RNCv1.7 2.Updating new operation procedure and operation windows (such as batch processing scripts) 3.Adding description of MML parameter change in RNCv1.7 and NodeBv1.7 4.Adding new parameter tracing in cell performance tracing Zhang Meng 5.Updating parameters in IOS tracing 6.Supplementing extraction of traffic measurement, IOS tracing, extraction of CFGMML file, and extraction of CHR logs 7. Adding introduction to equipment room

2005-06-01

2005-06-05

2007-12-13

Supplementing operation rules in equipment room, CR revision process, editing and executing batch processing scripts, and how to Yu Bingwen add performance management tasks. Updating starting and stopping simulated load on NodeB, supplementing querying alarm information, supplementing daily routine Song Xiaoli data collection, and supplementing login to M2000.

Revising chapters in detail according to suggestions from Jin Yu, Song Hu Mingchao Xiaoli, Sun Daming, Zang Liang, Li Wenhui, and Wang Dekai Supplementing loading and testing operations, collection of data for tracing calls, adding operations on electric antenna, and revising Qin Yan / Zuo according to BTS3812E V100R005C01B073 and Yanzhong BSC6800V100R005C01B063

All rights reserved

Page2 , Total220


Date

Version

Description

Author

2007-09-01

3.2

1. Supplementing HSUPA-related commands in section 2.8 “BSC5800 Zhang Hao MML Command Line” 2. Supplementing HSUPA-related commands in section 4.3 “NodeB MML Commands”

2008-12-5

3.5

1.deleting how to use Performance Browse Tool 2.deleting parts of redundance information in the Appendix 3.adding how to get the NodeB performance data 4.adding how to analysis the NodeB performance data with Nastar

2007-12-13

All rights reserved

Lichuanhai

Page3 , Total220


Table of Contents 1 Introduction ............................................................................................................................. 16 1.1 Contents ......................................................................................................................... 16 1.2 Overview of WCDMA Networking .................................................................................... 17 1.3 Introduction ..................................................................................................................... 18 1.4 Rules and Precautions in Equipment Room ..................................................................... 19 2 RNC OM System ...................................................................................................................... 19 2.1 Installing and Starting RNC ............................................................................................. 19 2.2 Tracing Signaling at Standard Interfaces of BSC6800 Single Subscriber ......................... 22 2.2.1 Background .......................................................................................................... 22 2.2.2 Procedure ............................................................................................................. 22 2.3 Tracing Connection Performance of RNC Single Subscriber............................................ 28 2.3.1 Content ................................................................................................................. 28 2.3.2 Procedure ............................................................................................................. 28 2.4 Tracing RNC Cell Performance ....................................................................................... 29 2.4.1 Content ................................................................................................................. 29 2.4.2 Procedure ............................................................................................................. 30 2.5 Tracing RNC Calls .......................................................................................................... 33 2.6 Tracing RNC Protocol Messages at Transport Network Layer ......................................... 35 2.7 Tracing RNC MNCDT...................................................................................................... 37 2.8 Tracing RNC CDT/IFTS .................................................................................................. 40 2.9 RNC MML Command Line .............................................................................................. 44 2.10 Editing and Executing RNC Batch Processing Scripts.................................................... 50 2.10.1 Editing RNC Batch Processing Scripts ................................................................ 50 2.10.2 Executing RNC Batch Processing Scripts............................................................ 53 2.11 Other Optimizations of RNC .......................................................................................... 62 2.11.1 Importing and Exporting CFGMML File................................................................ 62 2.11.2 Extracting CHR Log ............................................................................................ 66 2.11.3 Extracting Traffic Measurement Data Files .......................................................... 66 2.11.4 Tracing IOS ........................................................................................................ 67 3 M2000 OM System ................................................................................................................... 70 3.1 Starting M2000 OM System ............................................................................................ 70 3.1.1 Functions .............................................................................................................. 70 3.1.2 Procedure ............................................................................................................. 70 3.2 View MML command execution results on the M2000 ..................................................... 72 3.3 View Subsequent Packets Generated by an MML command on the M2000 ..................... 72 3.4 Start the configuration management express (CME) on the M2000.................................. 73 3.5 Extract BCP compression package through CME on the M2000. ..................................... 73 3.6 Start the LMT of NEs on the M2000................................................................................. 75 3.7 Starting Simulated Load on NodeB in M2000 .................................................................. 79 3.7.1 Background .......................................................................................................... 79 3.7.2 Procedure ............................................................................................................. 80 3.8 Stopping Simulated Load on NodeB in M2000................................................................. 81 3.9 Querying Starting Simulated Load on NodeB................................................................... 82 3.10 Editing and Executing Scripts for Starting and Stopping Simulated Load on NodeB in M2000 .................................................................................................................................. 84 3.10.1 Editing Scripts for Starting and Stopping Simulated Load on NodeB in M2000..... 84 3.10.2 Executing Batch Processing Scripts for Starting and Stopping Simulated Load on NodeB in M2000 ............................................................................................................ 84 2007-12-13

All rights reserved

Page4 , Total220


3.11 Method for Exporting NodeB Names in M2000 .............................................................. 86 3.12 Querying NodeB IP Address in M2000 .......................................................................... 91 3.13 Extracting Alarm Data in M2000 .................................................................................... 93 3.14 Extracting Traffic Measurement Data in M2000.............................................................. 95 3.14.1 Querying Traffic Measurement Data in M2000 ..................................................... 95 3.14.2 Extracting Traffic Measurement Data in M2000.................................................... 95 3.15 Method for Counter self-defining and new report setup in M2000 ................................... 97 3.15.1 Enabling of measurement switches of a customized formula on the M2000 ......... 97 3.15.2 Export and import of a customized counter in the M2000 ..................................... 99 3.15.3 Customization and generation of a query report on the M2000 .......................... 100 3.15.4 Query of measurements between two cells on the M2000 ................................. 105 3.16 Extraction of NodeB traffic measurement data on the M2000 ....................................... 107 3.16.1 Establishment of a data export task on the M2000............................................. 107 3.16.2 Obtaining of NodeB data ................................................................................... 111 4 NodeB OM System ................................................................................................................ 112 4.1 Starting Remote OM of NodeB ...................................................................................... 112 4.2 Starting Local OM of NodeB .......................................................................................... 117 4.3 NodeB MML Commands ............................................................................................... 117 4.4 Starting/Stopping and Querying Simulated Load on NodeB ........................................... 119 4.4.1 Starting Simulated Load on NodeB ..................................................................... 119 4.4.2 Stopping Simulated Load on NodeB .................................................................... 121 4.4.3 Querying Simulated Load on NodeB ................................................................... 121 4.4.4 Starting/Stopping and Querying Simulated Load on NodeBv1.7 .......................... 122 4.5 Collecting RTWP Data on NodeB .................................................................................. 125 4.5.1 Displaying NodeB Slots....................................................................................... 125 4.5.2 Querying Cells under NodeB ............................................................................... 129 4.5.3 Starting Monitoring RTWP under NodeB ............................................................. 131 4.5.4 Processing RTWP Data ...................................................................................... 138 4.6 Querying and Extracting Alarm Information on NodeB ................................................... 138 4.6.1 Querying Alarm Information on NodeB ................................................................ 138 4.6.2 Extracting Alarm Data of NodeB .......................................................................... 148 4.7 Operations of NodeB Electric Antenna .......................................................................... 150 4.7.1 Process .............................................................................................................. 150 4.7.2 Operation Commands for Electric Antenna of BTS 3812/3806/3806A .................. 151 4.7.3 Operation Commands for Electric Antenna of BTS 3812E/A, BBU, and DBS ....... 152 4.8 NodeB traffic measurement data collection and analysis ............................................... 153 4.8.1 NodeB traffic measurement data collection.......................................................... 153 4.8.2 Description of the Compatible Nastar Version ..................................................... 154 4.8.3 Querying Related Alarms on the M2000 .............................................................. 158 4.8.4 Querying the Current Fault Alarms ...................................................................... 158 5 OM at Core Network Side ...................................................................................................... 159 5.1 Tracing Subscribers at Core Network Side .................................................................... 159 5.2 Extracting Bills .............................................................................................................. 160 5.2.1 Viewing Bills ....................................................................................................... 160 5.2.2 Extracting Bills .................................................................................................... 162 6 Customized Querying Alarm Information............................................................................. 162 6.1 Querying Abnormal Cells............................................................................................... 162 6.2 Querying Alarms on BTSs and Cells in NodeB OM System ........................................... 163 6.3 Querying Alarms in M2000 ............................................................................................ 164 6.3.1 Querying Event Alarms ....................................................................................... 164 6.3.2 Querying History Fault Alarms............................................................................. 164 6.3.3 Querying Screened Alarms ................................................................................. 165 6.3.4 Setting an Alarm Query Template ....................................................................... 165 2007-12-13

All rights reserved

Page5 , Total220


7 Routine Tasks in Equipment Room ...................................................................................... 167 7.1 Extracting CFGMML System Files ................................................................................. 167 7.2 Extracting CHR ............................................................................................................. 167 7.3 Extracting Traffic Measurement Data Files .................................................................... 167 7.4 Querying Cell States ..................................................................................................... 167 7.5 Collecting and Extracting RTWP Data ........................................................................... 168 7.6 Collecting Traffic Measurement Data ............................................................................. 168 7.7 Tracing Subscribers ...................................................................................................... 168 7.8 Extracting Alarm Information ......................................................................................... 168 8 Parameter Comparison ......................................................................................................... 169 8.1 RNC parameter Acquisition ........................................................................................... 169 8.1.1 Method of obtaining the baseline script................................................................ 169 8.1.2 Method of Obtaining the RNC MML Script of the existing network ....................... 170 8.2 NodeB parameter acquisition ........................................................................................ 171 8.2.1 Method of Obtaining The Baseline Script............................................................. 171 8.2.2 Acquisition of XML script of NodeBs on the existing network ............................... 172 8.3 Installation of Relevant Programs (Software) ................................................................. 173 8.3.1 Installation of the Nastar R2 Program .................................................................. 173 8.3.2 Installation of the Relevant Programs .................................................................. 173 8.3.3 Method of Logging in to the Server Through the Nastar R2 ................................. 174 8.4 RNC parameter comparison .......................................................................................... 175 8.4.1 Comparison with the baseline parameters ........................................................... 175 8.4.2 Parameter comparison between different cells in one MML script ........................ 177 8.4.3 (RNC-level and cell-level) parameter comparison between different RNCs .......... 178 8.4.4 (RNC-Level and Cell-Level) Parameter Comparison Between different versions of an RNC ............................................................................................................................ 179 9 Appendix ............................................................................................................................... 182 9.1 CR Process for Modifying Parameters ........................................................................... 182 9.2 Division of Responsibilities for Executing BSC6800 MML Commands............................ 182 9.3 List of BSC6800 MML Batch Processing Commands..................................................... 183 9.4 Supplementation to Method for Starting DL Simulated Load .......................................... 183 9.4.1 Starting Downlink Simulated Load ....................................................................... 183 9.5 Description of Collecting Data for Tracing Calls ............................................................. 184 9.5.1 Tracing Signaling Messages ............................................................................... 184 9.5.2 Monitoring Realtime State ................................................................................... 187 9.5.3 Tracing CDT ....................................................................................................... 192 9.5.4 Viewing CHR through Insight Plus....................................................................... 194 9.6 Description of the Configuration File for the Nastar R2 Parameter Comparison Tool ...... 195 9.6.1 Script configuration for RNC MML parameter comparison ................................... 195 9.7 Parameter configuration script cmpcmd.xml of the Nastar ............................................. 199 9.8 NodeB parameter mapping table ................................................................................... 199 9.9 Script configuration used for NodeB XML parameter comparison .................................. 199 9.10 Procedure for exporting the NodeB parameter configuration script through the M2000 201 9.11 .NET Framework2.0 installation ................................................................................... 202 9.12 SQL Server2005 Express installation .......................................................................... 204 9.13 Method of obtaining NodeB baseline through the CME ................................................ 210 9.13.1 Open a project .................................................................................................. 210 9.13.2 Version configuration ........................................................................................ 210 9.13.3 Configure RNS parameters ............................................................................... 211 9.14 Concerns of RNC parameter comparison for network planning .................................... 214 9.14.1 Comparison with the baseline parameters ......................................................... 214 9.14.2 Parameter comparison between different cells in one MML script ...................... 216 9.14.3 Parameter comparison between different RNCs ................................................ 218 2007-12-13

All rights reserved

Page6 , Total220


List of Tables Table 2-1 List of tracing on BSC6800 .................................................................................. 33 Table 2-2 Traced messages at transport network layer on BSC6800 ................................... 35 Table 2-3 BSC6800 MML commands used in radio network planning and optimization ....... 45 Table 4-1 A set of MML commands used frequently on NodeB in RNP&O .......................... 118 Table 4-2 Operation commands for electric antenna of BTS3812/3806/3806A ...................151 Table 4-3 Operation commands for electric antenna of BTS 3812E/A, BBU, and DBS........152 Table 9-1 DPCH spreading code, timing offsets, and relative level settings for OCNS signal ...................................................................................................................................184 Table 9-2 Parameter mapping table ...................................................................................199 Table 9-3 Excel data format for cell group setting ...............................................................217 Table 9-4 Example of cell parameters ................................................................................218

2007-12-13

All rights reserved

Page7 , Total220


List of Figures Figure 1-1 WCDMA networking .......................................................................................... 17 Figure 2-1 Starting BSC6800 OM ....................................................................................... 20 Figure 2-2 Starting BSC6800v1.7 OM................................................................................. 21 Figure 2-3 Signalling tracing at standard interfaces of single subscriber .............................. 23 Figure 2-4 Modifying advanced parameters ........................................................................ 23 Figure 2-5 Starting TraceViewer ......................................................................................... 24 Figure 2-6 Tracing signaling at standard interfaces of BSC6800 single subscriber in RNCv1.7 .................................................................................................................................... 25 Figure 2-7 Modifying the version output format ................................................................... 26 Figure 2-8 Starting TraceViewer in RNCv1.7....................................................................... 27 Figure 2-9 Tracing connection performance of single subscriber ......................................... 29 Figure 2-10 Tracing cell performance ................................................................................. 31 Figure 2-11 Tracing cell performance with a chart in RNCv1.7 ............................................ 32 Figure 2-12 Tracing cell performance with a list in RNCv1.7 ............................................... 32 Figure 2-13 Tracing BSC6800 calls .................................................................................... 34 Figure 2-14 Tracing BSC6800 calls in RNCv1.7.................................................................. 34 Figure 2-15 Tracing B SC6800 protocol messages at transport network layer ..................... 36 Figure 2-16 Tracing B SC6800 protocol messages at transport network layer in RNCv1.7 .. 36 Figure 2-17 Tracing BSC6800 MNCDT in RNCv1.7 ............................................................ 38 Figure 2-18 Tracing BSC6800 intra-frequency MNCDT in RNCv1.7 .................................... 38 Figure 2-19 Tracing BSC6800 inter-frequency MNCDT in RNCv1.7 .................................... 39 Figure 2-20 Tracing BSC6800 inter RAT MNCDT in RNCv1.7............................................. 39 Figure 2-21 CDT startup interface in V29 (tracing based on UE ID)..................................... 40 Figure 2-22 IFTS startup interface in V29 ........................................................................... 41 Figure 2-23 User plane tracing parameter setting interface for the CDT .............................. 42 Figure 2-24 MML command client interface ........................................................................ 43 Figure 2-25 Starting BSC6800 MML ................................................................................... 44 Figure 2-26 Starting BSC6800V1.7 MML commands .......................................................... 45 Figure 2-27 Querying key words by executing BSC6800 MML command............................ 49 Figure 2-28 Querying key words by executing BSC6800v1.7 MML command ..................... 49 Figure 2-29 BSC6800 OM console ..................................................................................... 50 2007-12-13

All rights reserved

Page8 , Total220


Figure 2-30 Starting column editing function of UltraEdit software ....................................... 51 Figure 2-31 Column editing in UltraEdit software ................................................................ 52 Figure 2-32 BSC6800 OM console in RNCv1.7 .................................................................. 52 Figure 2-33 Configuring batch processing in BSC6800 OM ................................................ 53 Figure 2-34 Saving result of batch processing in BSC6800 OM .......................................... 54 Figure 2-35 Selecting execute batch commands menu in BSC6800 OM ............................. 54 Figure 2-36 Executing batch processing in BSC6800 OM ................................................... 55 Figure 2-37 Executing batch processing immediately in BSC6800 OM ............................... 56 Figure 2-38 Customized time for executing batch processing in BSC6800 OM ................... 57 Figure 2-39 Stopping saving result of executing script ........................................................ 57 Figure 2-40 Configuring batch processing in BSC6800 OM of RNCv1.7 ............................. 58 Figure 2-41 Saving result of batch processing in BSC6800 OM in RNCv1.7 ....................... 59 Figure 2-42 Selecting execute batch commands menu in BSC6800v1.7 ............................. 59 Figure 2-43 Executing batch processing in BSC6800v1.7 ................................................... 60 Figure 2-44 Executing batch processing immediately in BSC6800v1.7 OM ......................... 61 Figure 2-45 Customizing time for executing batch processing in BSC6800v1.7 OM ............ 61 Figure 2-46 Stopping saving results of script execution in BSC6800v1.7............................. 62 Figure 2-47 Uploading CFGMML file through FTP .............................................................. 64 Figure 2-48 Exporting CFGMML files in RNCv1.6 ............................................................... 64 Figure 2-49 Starting FTP client in RNCv1.7 ........................................................................ 65 Figure 2-50 Exporting CFGMML file in RNCv1.7................................................................. 65 Figure 2-51 Tracing IOS ..................................................................................................... 68 Figure 2-52 Configuring parameters for IOS tracing ............................................................ 68 Figure 2-53 Tracing IOS in RNCv1.7 .................................................................................. 69 Figure 2-54 Configuring parameters for IOS tracing in RNCv1.7 ......................................... 69 Figure 3-1 Login of M2000 OM system ............................................................................... 71 Figure 3-2 Starting M2000 OM system ............................................................................... 71 Figure 3-3 Open the management items of the counter to be customized ........................... 77 Figure 3-4 Open the related measurements........................................................................ 78 Figure 3-5 Input of the formula for customizing a counter.................................................... 79 Figure 3-6 Starting 50% simulated load on NodeB3806A in M2000 ..................................... 80 Figure 3-7 Starting 50% simulated load on NodeB 3802C ................................................... 81 Figure 3-8 Stopping simulated load on NodeB 3802C ......................................................... 82 2007-12-13

All rights reserved

Page9 , Total220


Figure 3-9 Querying downlink maximum transmit power in BSC6800 OM ........................... 83 Figure 3-10 Displaying downlink transmit power of the cell 23191 when starting 36% simulated load ............................................................................................................................. 83 Figure 3-11 M2000 OM interface ........................................................................................ 85 Figure 3-12 Importing scripts in M2000 ............................................................................... 85 Figure 3-13 Executing batch processing scripts in M2000 ................................................... 86 Figure 3-14 Exporting NodeB names in M2000................................................................... 87 Figure 3-15 Selecting data to be exported in M2000 ........................................................... 88 Figure 3-16 Saving exported data about NodeBs in M2000 ................................................ 89 Figure 3-17 Performing column-to-row conversion of NodeB names in UltraEdit ................. 90 Figure 3-18 Replacing spaces between NodeB names with commas in UltraEdit ................ 91 Figure 3-19 Physical topology window in M2000................................................................. 92 Figure 3-20 Querying IP address of a candidate NodeB in M2000 ...................................... 92 Figure 3-21 Querying alarm data in M2000 ......................................................................... 93 Figure 3-22 Setting querying alarm in M2000 ..................................................................... 94 Figure 3-23 Saving alarm data as files................................................................................ 94 Figure 3-24 Querying traffic measurement data in M2000 ................................................... 95 Figure 3-25 Setting querying traffic measurement in M2000 ............................................... 96 Figure 3-26 Displaying traffic measurement data. ............................................................... 97 Figure 3-27 Opening a customized counter ........................................................................ 98 Figure 3-28 Validating the customized counter.................................................................... 99 Figure 3-29 Importing a customized counter ......................................................................100 Figure 3-30 Customizing a query report—select a measurement object .............................101 Figure 3-31 Customizing a query report—select the corresponding counter values ............102 Figure 3-32 Customizing a query report—select a time mode and a period ........................103 Figure 3-33 Customizing a query report—save a customized query report .........................104 Figure 3-34 Generation of a customized report ..................................................................105 Figure 3-35 Enabling the measurement between two cells.................................................106 Figure 3-36 Enabling the measurement between two cells (CELL_GCELL) .......................107 Figure 3-37 Starting the centralized task management.......................................................108 Figure 3-38 Starting the performance data export function .................................................109 Figure 3-39 Modifying task attributes ................................................................................. 110 Figure 3-40 File export log................................................................................................. 111 2007-12-13

All rights reserved

Page10 , Total220


Figure 4-1 Login to NodeB ................................................................................................ 113 Figure 4-2 Adding connection with NodeB ......................................................................... 114 Figure 4-3 Starting OM of specified NodeB ........................................................................ 114 Figure 4-4 Login to NodeBv1.7 .......................................................................................... 115 Figure 4-5 Adding connection with NodeBv1.7................................................................... 116 Figure 4-6 Starting OM of specified NodeBv1.7 ................................................................. 117 Figure 4-7 Starting 50% downlink simulated load on NodeB 3812E ...................................120 Figure 4-8 Setting desensitivity strength of NodeB 3812E to 1 dB......................................121 Figure 4-9 Keeping the last code word of SF=8 on RNC ....................................................122 Figure 4-10 Starting 50% downlink simulated load on NodeBv1.7 3812E ...........................123 Figure 4-11 Setting desensitivity strength of NodeBv1.7 3812E to 1 dB .............................123 Figure 4-12 Keeping the last code word of SF=8 on RNCv1.7 ...........................................124 Figure 4-13 Physical structure of NodeB 3806A.................................................................126 Figure 4-14 Physical structure of NodeB 3812 ...................................................................127 Figure 4-15 Physical structure of NodeB 3802C ................................................................127 Figure 4-16 Physical structure of NodeB 3812E.................................................................128 Figure 4-17 Physical structure of NodeBv1.7 3812E ..........................................................128 Figure 4-18 Querying cells under a NodeB ........................................................................130 Figure 4-19 Querying cells under a NodeBv1.7..................................................................131 Figure 4-20 Saving RTWP files..........................................................................................132 Figure 4-21 Starting monitoring the second cell under the NodeB ......................................132 Figure 4-22 Saving RTWP file for the second cell under NodeB .........................................133 Figure 4-23 Querying cells of BTS3802C...........................................................................134 Figure 4-24 Starting RTWP measurement of the second cell under BTS3802C..................135 Figure 4-25 Saving RTWP files in NodeBv1.7 ....................................................................136 Figure 4-26 Starting monitoring the second cell under NodeBv1.7 .....................................137 Figure 4-27 Saving RTWP file for the second cell under NodeBv1.7 ..................................137 Figure 4-28 Abnormal login for NodeB ...............................................................................138 Figure 4-29 Querying E1T1 number in BSC6800 OM system. ...........................................139 Figure 4-30 Querying E1T1 state in BSC6800 OM system.................................................140 Figure 4-31 Viewing state of boards on NodeB3806A ........................................................141 Figure 4-32 Content of alarm on NLPA board ....................................................................141 Figure 4-33 Content of NPMU alarm..................................................................................142 2007-12-13

All rights reserved

Page11 , Total220


Figure 4-34 Current alarms in NodeB alarm management system .....................................142 Figure 4-35 Viewing configuration of NodeB alarm log .......................................................143 Figure 4-36 Querying historical alarms on NodeB ..............................................................144 Figure 4-37 Viewing state of boards on NodeB ..................................................................145 Figure 4-38 Content of alarm on MAFU board ...................................................................145 Figure 4-39 Content of alarm on NMPT board ...................................................................146 Figure 4-40 Current alarms in NodeBv1.7 alarm management system ...............................146 Figure 4-41 Viewing configuration of NodeBv1.7 alarm log ................................................147 Figure 4-42 Querying historical alarms on NodeBv1.7 .......................................................148 Figure 4-43 Saving alarm data of NodeB ...........................................................................149 Figure 4-44 Saving alarm data of NodeBv1.7 ....................................................................150 Figure 4-45 Task management on the M2000 ....................................................................153 Figure 4-46 Settings for NodeB performance data collection..............................................154 Figure 4-47 Importing a NodeB traffic measurement file ....................................................155 Figure 4-48 Selecting a proper counter query range ..........................................................155 Figure 4-49 Selecting Node-level traffic measurement .......................................................156 Figure 4-50 Selecting the NodeB to be queried..................................................................156 Figure 4-51 Selecting cell-level traffic measurement ..........................................................157 Figure 4-52 NodeB traffic measurement query result .........................................................157 Figure 5-1 Tracing MSOFTX3000 call................................................................................159 Figure 5-2 Viewing bills in iGWB Client software ................................................................160 Figure 5-3 Viewing the bill of a period ................................................................................161 Figure 5-4 Viewing bills according to calling or called number ............................................162 Figure 6-1 Importing cell states to an Excel table ...............................................................163 Figure 8-1 Obtaining the RNC baseline script from the website http://support.huawei.com .170 Figure 8-2 Parameter comparison process ........................................................................171 Figure 8-3 Obtaining a product baseline from the website at http://support.huawei.com .....172 Figure 8-4 Obtaining NodeB parameter configuration scripts in batches through the M2000 ...................................................................................................................................173 Figure 8-5 SQL server configuration manager ...................................................................174 Figure 8-6 Login interface of the Nastar R2 .......................................................................174 Figure 8-7 Settings for the SQL Server2005 Express installation .......................................175 Figure 8-8 Selection for comparison with the baseline parameters .....................................176 2007-12-13

All rights reserved

Page12 , Total220


Figure 8-9 File configuration for comparison with the baseline parameters.........................176 Figure 8-10 Parameter comparison between different cells in one MML script ....................177 Figure 8-11 File configuration for parameter comparison between different cells in one MML script ..........................................................................................................................178 Figure 8-12 (RNC-level and cell-level) parameter comparison between different RNCs......178 Figure 8-13 Parameter comparison between different RNCs..............................................179 Figure 8-14 Parameter comparison between different versions of an RNC .........................180 Figure 8-15 Parameter configuration for parameter comparison between different versions of an RNC ......................................................................................................................180 Figure 9-1 Tracing BSC6800 CDT .....................................................................................193 Figure 9-2 CDT messages ................................................................................................194 Figure 9-3 Viewing CHR through Insight Plus ....................................................................195 Figure 9-4 Format of classified command parameters........................................................196 Figure 9-5 Parameter matching format ..............................................................................197 Figure 9-6 Configuration format of special command parameters.......................................197 Figure 9-7 .NET Framework2.0 installation(1) ....................................................................202 Figure 9-8 .NET Framework2.0 installation(2) ....................................................................203 Figure 9-9 .NET Framework2.0 installation(3) ....................................................................203 Figure 9-10 SQL Server2005 installation(1) .......................................................................204 Figure 9-11 SQL Server2005 installation(2) .......................................................................205 Figure 9-12 SQL Server2005 installation(3) .......................................................................205 Figure 9-13 SQL Server2005 installation(4) .......................................................................206 Figure 9-14 SQL Server2005 installation(5) .......................................................................206 Figure 9-15 SQL Server2005 installation(6) .......................................................................207 Figure 9-16 SQL Server2005 installation(7) .......................................................................207 Figure 9-17 SQL Server2005 installation(8) .......................................................................208 Figure 9-18 SQL Server2005 installation(9) .......................................................................208 Figure 9-19 SQL Server2005 installation(10) .....................................................................209 Figure 9-20 SQL Server2005 installation(11) .....................................................................209 Figure 9-21 CME server configuration information (1) ........................................................210 Figure 9-22 CME server configuration information (2) ........................................................210 Figure 9-23 Opening the RNS on the CME server .............................................................210 Figure 9-24 Version selection ............................................................................................ 211 Figure 9-25 Opening parameter configuration on the CME server ...................................... 211 2007-12-13 All rights reserved Page13 , Total220


Figure 9-26 Selecting NodeB parameters on the CME server ............................................212 Figure 9-27 NodeB parameter configuration ......................................................................212 Figure 9-28 Selecting cell parameters on the CME server..................................................212 Figure 9-29 Cell-level parameter configuration on the CME server.....................................212 Figure 9-30 NodeB configuration interface.........................................................................213 Figure 9-31 Creating a physical channel on the CME server ..............................................213 Figure 9-32 Exporting an XML script on the CME server ....................................................213 Figure 9-33 Parameter configuration of different clusters ...................................................216 Figure 9-34 NE Group for cell group setting .......................................................................217

2007-12-13

All rights reserved

Page14 , Total220


WCDMA OMC Operation Guide Key words: MML command, RTWP, starting simulated load, tracing signaling of single subscriber, and OM Abstract: The document includes the operations in equipment room for radio network planning and optimization engineers during the radio network optimization. It details operations related to RNC, NodeB, M2000, core network, including tracing signaling of single subscriber under RNC, MML command line, querying cell-related parameters, collecting and converting RTWP data, starting simulated load on NodeB, querying alarm data, tracing MSC subscribers, and extracting bill. It also describes related precautions. Acronyms and abbreviations: Acronyms and abbreviations BAM BSC6800 CHR CDL IMSI LMT MML NBAP NBBI MTRU NDTI NMPT RRM RTWP SIR TMSI UE CR AISG SPU BLER RSCP OMC

2007-12-13

Full spelling Back Administration Module Huawei RNC Model Call History Record Calling Detailed Log International Mobile Subscriber Identity Local Maintenance Terminal Man Machine Language NodeB Application Part NodeB BaseBand Interface processing Unit NodeB Multi-carrier TRansceiver Unit NodeB Digital Trunk Interface unit NodeB Main Processing & Timing unit Radio Resource Management Received Total Wideband Power Signal Interference Ratio Temporary Mobile Station Identity Subscriber Equipment Change Request Antenna interface standards group Service Process Unit Block Error Rate Received Signal Code Power Operation and Maintenance Center

All rights reserved

Page15 , Total220


1 Introduction 1.1 Contents This document describes the operations in equipment room during radio network optimization. It details operations related to RNC, NodeB, M2000, and core network. The chapters are arranged according to operations of importance sequence by engineers, including the following sections which describe the most frequently-used functions. 1)

Rules and precautions in equipment room

It describes rules and precautions to be followed by RNP&O engineers in equipment room. 2)

BSC6800 (RNC) OM

It introduces the following of BSC6800 (RNC):

l

Tracing signaling at standard interfaces of single subscriber Tracing connection performance of single subscriber Tracing cell performance Tracing call Querying cell-related parameters Editing and executing MML command line and batch processing scripts Traffic measurement Exporting and uploading CFGMML files Extracting CHR logs Extracting Profile files

3)

M2000 OM system

l l l l l l l l l

It includes the following in M2000:

l

Starting and stopping simulated load on a batch of NodeB Methods for editing scripts of starting and stopping simulated load Methods for exporting NodeB name Querying NodeB IP address in M2000 Querying and saving alarm data in M2000

4)

NodeB OM

l l l l

It includes starting and stopping simulated load on single NodeB, MML command of NodeB. It details collecting and converting RTWP data on a single NodeB, querying and extracting alarm information on NodeB. 5)

OM at core network side

It includes the following under MSC: l l l l

6)

Tracing UEs Querying bills Viewing bills Extracting bills Querying alarm

It includes: 2007-12-13

All rights reserved

Page16 , Total220

WCDMA OMC Operation Guide Internal Open l l

7)

Customized query of alarm information Querying and saving alarm information in NodeB and M2000. Routine tasks in equipment room.

It describes that equipment room operators extract related data routinely from network side during network optimization to help RNO engineers for analysis. 8)

Parameter Comparison

In view of the importance of network parameters to network optimization, this section describes how to compare the parameters of the RNC and NodeBs to serve as reference for network optimization personnel in routine parameter comparison. 9)

Appendix.

It describes the method for starting simulated load and collecting data for tracing call. In addition, it includes the follow: l l l

CR revision flow Division of responsibilities for executing BSC6800 MML commands Samples of MML batch processing commands

& Note: Based on version 1.6, the operation and maintenance part of RNC and NodeB of version 1.7 is newly added in this document.

1.2 Overview of WCDMA Networking Figure 1-1 shows the WCDMA networking.

Figure 1-1 WCDMA networking

2007-12-13

All rights reserved

Page17 , Total220


In Figure 1-1, RNP&O engineers must pay more attention to RAN network side. RNC is connected to: l l l l l

NodeB through the lub interface MSC of core network through the lu-CS interface SGSN of core network through the lu-PS interface Other RNCs through the lur interface so that RNCs exchange information with each other Cell broadcast center (CBC) through the lu-BC interface

Wherein, BSC6800 represents Huawei RNC model in the following chapters. Different IP addresses are assigned for different WCDMA network and OM clients, so user names and passwords are different. Equipment room operators manage and distribute user names and passwords uniformly, so you must follow rules in equipment room in using user names and passwords.

1.3 Introduction The document includes the operations in the equipment room for radio network planning and optimization engineers during the radio network optimization. It helps them analyze routine network optimization problems, such as call drop, handover, and pilot pollution. This document details operations related to the RNC, NodeB, and M2000, including tracing signaling of single subscriber under the RNC, MML command line, tracing signaling in both user plane and control plane, collecting and converting RTWP data, tracing real-time performance and cell performance. Different items are traced in different test tasks. The following section introduces the above-mentioned items by taking the equipment room of a site as an example. There is an RNC and a core network, and an M2000 at the site. The following table lists the IP address, user name, and password of each NE: Device

IP Address

Mask

User Name

Password

Before performing operations in the equipment room, you must identify IP address, user name, and password of each NE to avoid mistakes. For example, to telnet to NodeB, you must configure necessary routes.

& Note : Generally, the IP address of the RNC is different from that of the NodeB. To maintain the NodeB remotely, you need to run the following commands to add a BAM route to RNC: 2007-12-13 All rights reserved Page18 , Total220


For the RNC, run the command route add 12.11.0.0 mask 255.255.0.0 10.238.23.95 - p. For the M2000, run the command route add 12.11.0.0 mask 255.255.0.0 10.238.23.84 - p. If the LMT is connected with a LAN switch of RNC, the next hop is RNC. If the LMT is connected with a LAN switch of M2000, the next hop is M2000. For details about route configuration, see documents related to the BSC6800.

l

l

1.4 Rules and Precautions in Equipment Room For RNP&O engineers, follow related precautions as below: l l l

l l

l

l

l

Follow the time schedule and rules for engineer to enter and leave equipment room. Do not eat and drink in equipment room, and do not bring glasses into equipment room. Different OM clients use different user names and passwords in equipment room. Equipment room operators manage and distribute user names and passwords uniformly, so you must follow related rules when using them. Do not perform other operations except necessary RNP&O operations, such as board reset and system parameter modification. Equipment room operators must ensure usability of platform. For example, there is enough space on the server disk, and both sending RNO engineers tracing data files and deleting them on clients should be in time, otherwise, excessive data files on clients take up space. Do not privately create folders in the folder FTP on BAM server. For the convenience of management, the files are temporarily saved in FTP\logdata\ directory. Do not copy files directly from operation platforms with any storage medium, because there are more requirements on security of servers in equipment room. If you need upload script files and download operation result files onto your portable computers, you can only use network cable of internal maintenance network segment. For system security, uploading files to BAM server is prohibited without permission. In BSC6800 performance management system, if you need create a task, you need permission from equipment room operators. Otherwise, excessive tasks might affect RNC performance.

2 RNC OM System 2.1 Installing and Starting RNC RNP&O engineers use BSC6800 at RNC side most frequently in equipment room, so they can install BSC6800 OM on the clients by default.

Caution: l

Select a proper software language (English or Chinese) and make sure that the version number (BSC6800V100R005C01B068 for example) is consistent with that of the equipment room.

2007-12-13

All rights reserved

Page19 , Total220


The sequence number is BSC6800. Select the typical installation mode.

When you install the software BSC6800 OM version in RNCv1.5, you can double-click the “setup.exe”,and then select the language English or Chinese. When you install the software BSC6800 OM version in RNCv1.7, you can double-click the “setup.bat”,and then select the language English or Chinese. To start BSC6800, perform the following steps:

1)

Click

icon to start BSC6800 OM of RNC after installation is complete.

2)

Type the user name and password. Equipment room operators manage and distribute user names and passwords uniformly.

Figure 2-1 shows starting BSC6800 OM

Figure 2-1 Starting BSC6800 OM

2007-12-13

All rights reserved

Page20 , Total220


Figure 2-2 Starting BSC6800v1.7 OM In the BSC6800, the frequently-used operations include: 1)

Tracing signaling at standard interfaces of single subscriber

2)

Tracing connection performance of single subscriber

3)

Tracing cell performance

4)

Tracing calls

5)

Querying cell-related parameters

6)

Editing and executing MML command line and batch processing scripts

7)

Traffic measurement

8)

Importing and exporting CFGMML file

9)

Extracting CDL

10) Extracting Profile file

& Note: In RNCv1.6, traced items are saved at \client\output\main\BSC6800\ BSC6800V100R006C01B040\trace in the trace management directory by default. The files are saved in the format of office direction name_trace type_year-month-date-hour-minute-second.tmf. Monitored data of traced items is saved at \adaptor\clientadaptor\BSC6800\ BSC6800V100R006C01B040\output\realmonitor in the real-time performance monitor directory by def ault. The files are saved in the format of monitor type_monitor item_year-month-date-hour-minute2007-12-13

All rights reserved

Page21 , Total220


second.txt. The name of the saved BSC6800V100R006C01B040 file varies with versions. In RNCv1.7 and later version, MNCDT monitoring is newly added. It is saved at \ client\output\ main\BSC6800\BSC6800V100R007C01B061\trace. The file is saved in the format of office direction name_trace type_year-month-date-hour-minute-second. The system has the function of memorizing IMSI ID automatically.

The following sections detail the operations.

2.2 Tracing Signaling at Standard Interfaces of BSC6800 Single Subscriber 2.2.1 Background When locating problems, such as call drop, you need view signaling reported by the UE before call drop and analyze the signaling based on signaling recorded at RNC side. Provided with IMSI number, you can enable tracing signaling at standard interfaces of single subscriber under RNC.

2.2.2 Procedure To trace signaling at standard interfaces of single subscriber, perform the following steps: 1)

Double-click UE tracing (Standard Interface Message) in Maintenance Navigator.

2)

Select All standard interface in the pop-up dialog box.

3)

Type the IMSI number of UE to be traced in the IMSI text box.

& Note : You report the last four digits of IMSI to equipment room operators, because the first 11 digits are the fixed. For example, an IMSI in a WCDMA network is "45419500000****". The first 11 digits vary in different WCDMA networks.

4)

Select All standard interface during tracing signaling at standard interfaces of single subscriber or select Specify standard interface for tracing signaling at partial standard interfaces, and select one or more interfaces of lub interface, lu interface, Uu interface, and lur interface where the signaling must be traced from Select standard interface message in the right.

Figure 2-3 shows the tracing signalling at standard interfaces of single subscriber.

2007-12-13

All rights reserved

Page22 , Total220


Figure 2-3 Signalling tracing at standard interfaces of single subscriber

Figure 2-4 Modifying advanced parameters

2007-12-13

All rights reserved

Page23 , Total220


5)

Click Advanced. A dialog box Advanced for modifying parameters pops up. At this interface, you can modify the directory to save data, the maximum messages per window, flow control types, and message colour.

6)

Click OK.Tracing starts. When the tracing is complete, stop tracing by shutting down the window. Or you can stop tracing by selecting Stop tracing in the menu. You must start and read the traced signalling by using the BSC6800 TraceViewer of the same version. Otherwise, an error occurs upon tracing the signalling file. The BSC6800 TraceViewer is integrated to LMT OM system of BSC6800, with the starting interface as shown in Figure 2-5.

Figure 2-5 Starting TraceViewer On RNCv1.7, to trace the signaling of a single UE on standard interfaces, perform the following steps: 1)

Double-click UE (Standard Interface) in Maintenance.

2)

Select All standard interface message in the pop-up dialog box.

3)

Type the IMSI number of UE to be traced in the IMSI text box.

& Note : Typically, you need to report the last four digits of IMSI to equipment room operators, because the first 11 digits are always the same. For example, an IMSI in a WCDMA network is "45419500000****". The first 11 digits may vary in different WCDMA networks.

4)

Typically, select All standard interface message for the signaling tracing of a single UE on standard interfaces. You can also select Specify standard interface

2007-12-13

All rights reserved

Page24 , Total220


message for signaling tracing on some of the standard interfaces. In this case, select one or more out of the lub interface, lu interface, Uu interface, and lur interface in the Select standard interface message pane. Figure 2-6 shows signalling tracing at standard interfaces of a single subscriber.

Figure 2-6 Tracing signaling at standard interfaces of BSC6800 single subscriber in RNCv1.7

2007-12-13

All rights reserved

Page25 , Total220


Figure 2-7 Modifying the version output format 5)

Click Save as. You can modify the path where the data is to be saved.

6)

Click OK. The tracing starts.

7)

When the tracing is complete, stop the tracing by shutting down the window. You can also stop the tracing by selecting Stop tracing in the menu. You must open and read the traced signalling by using the BSC6800 TraceViewer of the same ve rsion. Otherwise, the traced result cannot be opened. The BSC6800 TraceViewer is integrated to LMT. When the LMT is started, the user interface is as shown in Fi gure 2-5.

2007-12-13

All rights reserved

Page26 , Total220


Figure 2-8 Starting TraceViewer in RNCv1.7

& Note: l

l

l l l

For the same IMSI, the system traces signaling at standard interfaces of single subscriber for one time under RNC. If you trace single subscriber on one LMT, you cannot trace the signaling of the same subscriber on another LMT. Under the same RNC, the current version of Trace Viewer supports tracing signaling at standard interfaces of six single subscribers at most at the same time. When multiple engineers start tracing signaling at standard interfaces of single subscriber at the same time for test, they need coordinate resources. During tracing signaling at standard interfaces of single subscriber, closing Trace window and clicking Stop Tracing are different. Close Trace window to export log file for tracing. Copy the file, send it to related engineers, and delete the file in time. When you click Stop Tracing, The log file to be traced is not closed. Copy the imported log file, and save it. If the file is deleted, data is missing upon next recording.

2007-12-13

All rights reserved

Page27 , Total220


2.3 Tracing Connection Performance of RNC Single Subscriber 2.3.1 Content When locating problems such as call drop, you need analysis the problems based on tracing connection performance of single subscriber recorded at RNC side. Provided with IMSI number, you can enable Tracing connection performance of single subscriber under RNC. During routine test of network optimization, you usually trace the following four connection performances: l l l l

UL SIR (measured SIR in radio uplink set) UL SIRtarget (target SIR in radio uplink set) UL BLER (BLER on uplink transmission channel) DL Tx Code Power (downlink transmit code power)

You might also trace the following connection performances: l l l l l l l l l l l

PCPICH (Ec/No&RSCP) AMR mode DL BLER (downlink block error rate) HO delay (handover delay) DL throughput & bandwidth UL throughput & bandwidth DL traffic vol (downlink traffic volume) UL traffic vol (uplink traffic volume) UL Phy BER (uplink physical channel bit error rate) UE TxPower (UE transmit power) UL SIRerror (uplink signal-to-interference ratio error)

2.3.2 Procedure To trace connection performance of single subscriber, perform the following steps: 1)

In Maintenance Navigator, double click Connection performance monitoring. In the Monitoring item drop-down menu, select UL SIR. Type IMSI number of UE to be traced in IMSI field, shown as in Figure 2-9.

2007-12-13

All rights reserved

Page28 , Total220


Figure 2-9 Tracing connection performance of single subscriber 2)

Type the IMSI of the subscriber to be traced and click OK.Tracing connection performance of single subscriber starts. The system automatically saves the tracing file in the default directory.

3)

Close the window or right click on the menu after tracing, and select Stop monitoring to stop tracing

The method for tracing Connection performance of UL SIRtarget, UL BLER, and DL Tx Code Power is similar with that of UL SIR. The difference lies in that you select UL SIRtarget, UL BLER, or DL Tx Code Power in Monitoring item drop-down menu.

2.4 Tracing RNC Cell Performance 2.4.1 Content When locating problems in a cell, you need view the performance specifications of the cell. If you have the RNC ID and cell ID, you can start tracing cell performance on BSC6800. Cell performance usually includes: 1） 2） 3） 4） 5）

PCPICH TxPower (transmit power of cell PCPICH pilot) Tx Carrier Power (transmit power of cell downlink carrier) DCH Subscriber Num (number of DCH subscribers of cell) CCH Subscriber Num (number of CCH subscribers of cell) Cell Code Tree (monitoring cell code tree)

In RNCv1.7, Cell User NUM (number of cell subscribers) and Cell Cmb UserNum (number of cell cmb subscribers) are newly added. DCH User Num (number of cell 2007-12-13

All rights reserved

Page29 , Total220


dedicated channel subscribers) and CCH User Num (number of cell common channel subscribers) are deleted. RNCv1.7 enhances the function of monitoring Cell User NUM, combines DCH User Num with CCH User Num, and adds the function of monitoring the number of HSPDA subscribers. As a result, it can monitor DCH User Num, CCH User Num, and the number of HSPDA subscribers in the same performance monitoring task. You might also trace the following cell performances: 1） 2） 3） 4） 5） 6） 7） 8）

HS-DSCH Provide Bit rate (bit rate provided by HS-DSCH) HS-DSCH Min Power Required (minimum power of HS-DSCH) DL Total Equivalent User Monitor (downlink total equivalent user monitor) UL Total Equivalent User Monitor (downlink total equivalent user monitor) DL CAC Monitor (downlink access grant judgment monitor) UL CAC Monitor (downlink access grant judgment monitor) Node Sync (node synchronization) RTWP (received total bandwidth power)

2.4.2 Procedure To trace cell performance, perform the following steps: 1)

In Maintenance Navigator, double click Cell performance monitoring. Select PCPICH TxPower in the pop-up dialog box. Type RNC ID and cell ID to be traced in RNC ID and Cell ID entry area

2)

Click OK to start tracing cell performance. The system automatically saves the tra cing file in BSC6800 LMT OM Installation Directory\Rtm by default, such as: C:\H WLMT\BSC6800V100R002ENGC03B092\Rtm.

3)

After tracing, close the window or right click on the menu to select Stop monitoring to stop tracing

4)

The method for tracing cell performance of Tx Carrier Power, DCH Subscriber Num, CCH Subscriber Num, and Cell Code Tree is similar with that of PCPICH TxPower The difference lies in that you select Tx Carrier Power, DCH User Num, CCH User Num, or Cell Code Tree in Monitoring item drop-down menu, shown in Figure 2-10.

2007-12-13

All rights reserved

Page30 , Total220


Figure 2-10 Tracing cell performance To trace cell performance on RNCv1.7, perform the following steps: 1)

In Maintenance, double click Cell performance monitoring. Select PCPICH TxPower in the pop-up dialog box. Type the cell ID to be traced in the Cell ID entry area.

2)

Click OK to start tracing cell performance. The system automatically saves the tracing file in the BSC6800 LMT installation directory \output\realmonitor by default, such as:D:\HWLMT\adaptor\clientadaptor\BSC6800\BSC6800V100R007 C01B061\output\realmonitor.

3)

After tracing, close the window or right click on the menu to select Stop monitoring to stop tracing.

4)

The method for tracing cell performance of Tx Carrier Power, DCH User Num, CCH User Num, and Cell Code Tree is similar with that of PCPICH TxPower. The difference lies in that you select Tx Carrier Power, DCH User Num, CCH User Num, or Cell Code Tree in Monitoring item drop-down menu, shown in Figure 2-11.

2007-12-13

All rights reserved

Page31 , Total220


Figure 2-11 Tracing cell performance with a chart in RNCv1.7

Figure 2-12 Tracing cell performance with a list in RNCv1.7 In RNCv1.7, you do not need to enter the RNC ID when starting tracing cell performance. Only the cells of the local RNC can be traced, so it is redundant to enter the RNC ID. In addition, an incorrect RNC ID may cause that the system cannot give 2007-12-13

All rights reserved

Page32 , Total220


any report on cell performances. Therefore, entering RNC ID is removed in RNCv1.7. LMT and the foreground processes the RNC ID automatically.

2.5 Tracing RNC Calls The BSC6800 LMT provides abundant functions of tracing subscribers, listed in Table 2-1. It can trace the messages at standard interface of UE, messages at user plane and signaling plane of UE, and even multiple calls. Operation methods and procedure are similar to that of tracing signaling at standard interfaces of single subscriber. Table 2-1 List of tracing on BSC6800 Type of traced task Tracing messages at standard interfaces of UE

Tracing messages at UE interface and signaling plane of UE during calling

Tracing IOS (multiple calls at the same time)

Tracing cells

Function description Tracing signaling messages at lu interface, lur interface, lub interface, and Uu interface of specified UE during calling. You must specify the IMSI, TMSI, P-TMSI, or IMEI of UE to start tracing. Tracing all signaling messages at four standard interfaces or tracing messages at specified interfaces. Tracing messages at UE interface and signaling interface of UE during calling. You must specify the UE (IMSI, TMSI, P-TMSI, or IMEI is also optional) to start tracing. You select messages at subscriber interface and signaling interface through selecting tracing events. Tracing messages imported in multiple callings connected consecutively to the specified cell. The number of calling connected consecutively to the cell is specified to N, If the number of current callings connected to the cell is N, the system does not trace new incoming callings. If the number of current callings connected to the cell is less than N due to calling termination, the software adds the new incoming calling to task list automatically. Through selecting traced events fro selecting traced messaged type, you select one or more cells. If no cell is added, the system traces all BSC6800 cells. Tracing NBAP common messages or USER_VOLUME events in the specified cells. Wherein, USER_VOLUME contains some customized messages which reflect the statistics information of UE in the cell. Specify a cell by typing cell ID. Select the types of messages to be traced by selecting tracing events. Cells to be traced must be already activated. The information to be traced is much, so this has little impact on system operation. You can trace 32 cells at most at the same time due to the limit by system. If you request are met by using lub interface, then use it as possible.

Figure 2-13 and Figure 2-14 show tracing BSC6800 calls.

2007-12-13

All rights reserved

Page33 , Total220


Figure 2-13 Tracing BSC6800 calls

Figure 2-14 Tracing BSC6800 calls in RNCv1.7

2007-12-13

All rights reserved

Page34 , Total220


2.6 Tracing RNC Protocol Messages at Transport Network Layer When the interface link is problematic, you can locate and analyze the problem by tracing transport network layer, including tracing the following messages: l l l l

QAAL2 protocol messages SCCP protocol messages MTP3B protocol messages SAAL protocol messages

Tracing protocol messages at transport network layer does not belong to frequently-used operations by RNP&O engineers. Table 2-2 lists the traced messages at transport network layer on BSC6800. Table 2-2 Traced messages at transport network layer on BSC6800 Type of traced tasks QAAL2 protocol message SCCP protocol message

MTP3B protocol message

SAAL protocol message

Function description It helps locate problems of AAL2 setup failure and Abnormal release of AAL2. It helps judge whether the local or the opposite is normal by whether to send ESTABLISH_REQUEST. The SCCP protocol message includes the connection-oriented and non-connection-oriented message. It helps locate problems of lu connection setup failure and abnormal release. The MTP3B protocol message includes the upper layer subscriber (QAAL2 and SCCP) message, the MTP3B signaling link test message, and MTP3B signaling network management message. It helps judge whether the target signaling point is unreachable or MTP3B link is unavailable. If the corresponding SAAL link is available, the method for locating problematic point is to check whether OPC, DPC, and SLS are matching and consistent with the negotiated data in the received and sent SLTM messages, and whether It helps judge whether the SAAL link is unavailable. If only messages are sent from RNC but not sent to RNC in the traced message, the bottom layer link (PVC) is congested or the opposite end work abnormally.

Figure 2-15 shows tracing B SC6800 protocol messages at transport network layer.

2007-12-13

All rights reserved

Page35 , Total220


Figure 2-15 Tracing B SC6800 protocol messages at transport network layer

Figure 2-16 Tracing B SC6800 protocol messages at transport network layer in RNCv1.7

2007-12-13

All rights reserved

Page36 , Total220


2.7 Tracing RNC MNCDT Missing Ncell Detect (MNCDT) means that the RNC misses configuring some neighboring cells in the neighboring cell handover list for each cell. It includes intra-frequency MNCDT (Intra Freq), inter-frequency MNCDT (Inter Freq), and inter-system MNCDT (Inter RAT). The MNCDT information reported by UEs is delivered to CHR, thus facilitating optimization of neighboring cells. To implement MNCDT, the following functions must be provided: Function 1: RNC supports inter-frequency MNCDT. To implement this function, the measurement and control information of inter-frequency hard handover based on period or event must be delivered, and RNC must receive a valid measurement report for analysis. That is to say, this function is closely related to inter-frequency handover. LMT initiates and terminates inter-frequency MNCDT, queries status, and delivers the result to CHR. Function 2: RNC supports inter-system MNCDT. To implement this function, the measurement and control information of inter-system handover based on period or event must be delivered, and RNC must receive a valid measurement report for analysis. That is to say, this function is closely related to inter-system handover. LMT initiates and terminates inter-system MNCDT, queries status, and delivers the result to CHR To trace MNCDT, perform the following steps: 1)

In Maintenance, double click MNCDT. Select the type to be traced in the pop-up dialog box.

2)

Click OK. The system automatically saves the tracing file in installation directory\ client\output\main\BSC6800\BSC6800V100R006C01B040\trace by default, in the format of office direction name_trace type_year-month-date-hour-minute-second. tmf.

3)

For inter-frequency MNCDT, enter uplink UARFCN, downlink UARFCN, start of primary scrambling code, and end of primary scrambling code. For inter RAT MNCDT, enter NCC, BCC, start of BCCH ARFCN, and end of BCCH ARFCN.

Figure 2-17 shows tracing BSC6800 MNCDT in RNCv1.7.

2007-12-13

All rights reserved

Page37 , Total220


Figure 2-17 Tracing BSC6800 MNCDT in RNCv1.7 Figure 2-18 shows tracing BSC6800 intra-frequency MNCDT in RNCv1.7.

Figure 2-18 Tracing BSC6800 intra-frequency MNCDT in RNCv1.7 Figure 2-19 shows tracing BSC6800 inter-frequency MNCDT in RNCv1.7. 2007-12-13

All rights reserved

Page38 , Total220


Figure 2-19 Tracing BSC6800 inter-frequency MNCDT in RNCv1.7 Figure 2-20 shows tracing BSC6800 inter RAT MNCDT in RNCv1.7.

Figure 2-20 Tracing BSC6800 inter RAT MNCDT in RNCv1.7

2007-12-13

All rights reserved

Page39 , Total220


2.8 Tracing RNC CDT/IFTS This task can be used to trace the standard interface messages of the UE, and the messages on the user plane and signaling plane of the UE in a call. Through the tracing task, the operator can monitor the signaling interaction process on each standard interface, signaling interaction on the user plane, and the uplink and downlink data in a call. To perform CDT tracing, the operator can specify the UE to be traced, the interface, and message type or can set a cell ID, SPUa subsystem of the cell, service type, and RRC setup cause. The powerful user plane statistics tracing function of the CDT and the printing tracing function of the CDL are sharp weapons that locate HSPA digital transmission problems, user plane problems, and internal product problems. The following takes V29 as an example to introduce the startup interface and common tracing setting interfaces of the CDT tracing function. Figure 2-1 shows the CDT startup interface, on which CDT tracing based on the UE ID is performed.

Figure 2-21 CDT startup interface in V29 (tracing based on UE ID) In addition to CDT tracing by UE ID (IMSI, TMSI, or IMEI), a cell such as the IOS can be specified; the system can then randomly select a UE to perform CDT tracing. This is called IFTS. The IFTS tracing specially applies to the case in which the fault is known but the UE ID cannot be determined.

2007-12-13

All rights reserved

Page40 , Total220


Figure 2-22 IFTS startup interface in V29 The CDT/IFTS provides a powerful user plane tracing function. We introduce the following common user plane tracing settings. To locate general network problems, select Periodically Data Report and set the period to two seconds and L2 Data Report Time to zero seconds or ten seconds. If the user plane data is required to locate a problem (for example, TRB resetting problem), set L2 Data Report Time to 100 seconds to guarantee that there is enough data for problem location.

2007-12-13

All rights reserved

Page41 , Total220


Figure 2-23 User plane tracing parameter setting interface for the CDT 1.Click the arrow next to History Command to display the previously executed command. At this time, you can modify some parameters. Repeat this step to modify other parameters. 2.Click the drop-down list next to Command Input (F5) to display the 20 recent history commands and their parameter configurations. You can selectively repeat the operation.

2007-12-13

All rights reserved

Page42 , Total220


Figure 2-24 MML command client interface NE window: The window displays the NEs that can issue MML commands, in the topological view according to the NE topology structure. MML command navigation tree window: The window displays the MML command navigation tree of the specified NE. Command output window: The window consists of the General Maintenance tab, History Command tab, and Help Information tab. The General Maintenance tab displays the issued commands and the execution results. The History Command tab lists the executed commands and their parameter configurations. The Help Information tab displays the help information about MML commands. Command display window: The window displays the commands to be executed and their parameter configurations. Executed command list window: The window displays all executed MML commands and the number of commands that each NE has executed. Command input window: The window contains History Commands, Command Input, and Command Parameters. History Commands displays the 20 recent history commands and their parameter configurations.

The M2000 may generate several packets if any of some commands are executed. When these commands are executed on the M2000, the General Maintenance tab displays only the first packet. You can query subsequent packets in the Subsequent Packet Browsing window.

2007-12-13

All rights reserved

Page43 , Total220


2.9 RNC MML Command Line During network planning and optimization, you query data, record data, and modify parameters frequently in equipment room. At RNC side, the most frequently-used method is executing MML commands and batch processing commands in BSC6800 OM system. To execute BSC6800 MML Command Line, perform the following steps: 1)

Click the icon

in BSC6800 OM to start MML Client operation interface

2)

Type commands in Command Input field and fill in with related parameters

3)

Click

for related operations

& Note: As shown in Figure 2-25, l Parameters in red are mandatory. l Parameters in black are optional.

Figure 2-25 shows starting BSC6800 MML command.

Figure 2-25 Starting BSC6800 MML

2007-12-13

All rights reserved

Page44 , Total220


4)

For RNCv1.7, click the icon BSC6800 OM to start the MML Client operation interface. Type commands in Command Input field and fill in with related parameters, and then click

to perform related operations.

& Note: As shown in Figure 2-26, l Parameters in red are mandatory. l Parameters in black are optional.

Figure 2-26 Starting BSC6800V1.7 MML commands Table 2-3 lists classified BSC6800 MML commands used in radio network planning and optimization. Complete commands in RNC are queried through Search function in BSC6800 OM help system. Table 2-3 BSC6800 MML commands used in radio network planning and optimization Equip ment

RNC

2007-12-13

Type Commands for querying cell states and parameters

Command

Command for querying cell data includes: LST CELL

Detailed operation Cell name Frequency Scramble Maximum transmit power TimeOffset Corresponding NodeB name,

All rights reserved

Remarks

–

Page45 , Total220

WCDMA OMC Operation Guide Internal Open Equip ment

Type

Command

Command for querying cell state includes: DSP CELL

Commands for querying neighbor cell information include: LST INTRAFREQCELL LST INTERFREQCELL LST GSMNCELL LST NRNCCELL

Commands for modifying cell state include: ACT/DEA CELL BLK/UBL CELL RMV CELL

Commands for modifying cell states and parameters.

Commands for adding relations between neighbor cells include: MOD INTRAFREQCELL ADD INTRAFREQCELL RMV INTRAFREQCELL

ADD/MOD CELLINTRAFREQHO ADD/MOD CELLINTERRATHOCO V Commands for modifying pilot PCPICH power include: MOD PCPICHPWR MOD CELL MOD CELLSETUP

2007-12-13

Detailed operation

Remarks

LAC. Five cell states include: Cell is setup and enabled (normal) Cell is setup and disabled (abnormal) Cell is not setup (abnormal) Cell is not active (deactivation) Cell is being blocked (blocked on RNC) Commands in the left stands for: Querying adjacent intra-frequency cells Querying adjacent inter-frequency cells Querying neighbor GSM cells Querying neighbor RNC cells Note that the parameter SRN is added in the commands in RNCv1.7, including LST GSMNCEL, LST INTRAFREQNCELL, and LST INTERFREQNCELL. Commands in the left stands for: Activating/Deactivating cell. Then logical cells and NodeB local cells are removed, the power amplifier is on, and transmit channel is closed Blocking/Unblocking cell. Then local cells and NodeB local cells exist, power amplifier is on, but transmit channel is closed Removing cell Commands about intra-frequency cells are abundant (in hundreds), executed through batch process commands. For details, see BSC6800 help. Commands in the left stands for Modifying offset parameter (CIO) of specified neighbor cells Adding intra-frequency neighbor cells Removing intra-frequency neighbor cells Adding/Modifying parameters for intra-frequency handover in cells Adding/modifying parameters for inter RAT frequency handover in cells The parameters InterRATPingPongTimer and InterRATPingPongHyst are added in this command of RNCv1.7 Commands in the left stands for: Modifying range of PCPICH power Modifying cell parameters Modifying frequency, scramble, maximum transmit power, and TimeOffset.

All rights reserved

–

–

View the cell state using DSP command. Unblock the cell if NodeB administratives tate = blocked

Use column editing function of UltraEdit

–

–

Modify transmit power of PCPICH. Modify the maximum and minimum

Page46 , Total220


Type

Command

Commands for querying and modifying algorithm parameters include: LST/SET CORRMALGOSWITCH LST/MOD CELLALGOSWITCH

2007-12-13

Detailed operation

Remarks

The BANDIND range is added in the command ADD/MOD CELLSETUP.

transmit power before executing commands, otherwise, the maximum and minimum default value of PCPICH are 34.6 dBm and 31.3 dBm.

Commands in the left stands for: Querying/Setting global algorithm parameters Querying/Modifying cell algorithm parameters

Commands for creating and modifying HSDPA configuration

Command for creating an HSDPA cell: ADD CELLHSDPA; Command for modifying HSDPA cell configuration: MOD CELLHSDPA

Commands in the left stand for: Creating parameters related to HSDPA cell configuration Modifying parameters related to HSDPA cell configuration The value range of the parameter HsPdschMPOConstEnum for the command ADD CELLHSDPA&MOD CELHSDPA changes from -4dB to 19dB.

Commands for creating and modifying HSUPA configuration

Command for creating an HSUPA cell: ADD CELLHSUPA; Command for modifying HSUPA cell configuration: MOD CELLHSUPA

Commands in the left stand for: Adding a cell HSUPA parameter Modifying a cell HSUPA parameter

All rights reserved

–

HSDPA power can be divided statically and dynamically. When you set HS-PDSCH AND HS-SCCH POWER, if the specified power is inconsistent with that of the power amplifier, the power is divided statically; otherwise the power is divided dynamically. Currently, up to 20 HSUPA subscribers can be supported. Therefore, set E-AGCH and E-RGCH/E-HI CH to 1. You must set the ratio between the power received by E-DCH not providing service and that received by the total

Page47 , Total220


Type

Command

Detailed operation

Remarks E-DCH depending on network planning

Command for exporting CFGMML script include: EXP CFGMML

Executing the command takes several minutes, so there might be expiring prompt on RNC. The default time for executing the command on RNC is 200s. Set the time longer in System Configuration upon expiration, such as 1000s

Export file CFGMML.TXT from D:\BSC6800\B AM\FTP where BAM server software is installed

Commands for exporting log include: LST LOG EXP LOG

Commands in the left stands for: Listing log in LMT window Exporting log. During exporting, the system saves the text file imported in OM on BAM. Authorized commands are recorded in log. You can use this command to query record in log.

Export log file in D:\BSC6800\B AM\FTPEXP on BAM.

Tracing signaling at standard interfaces of single subscriber

Tracing signaling at IMSI standard interfaces of single subscriber is detailed in 2.2 .

Save the file in BSC6800 LMT OM Installation Directory\Trac e.

Exporting Frequently-us ed data of NC

Interface tracing and performance monitoring (for locating problems and network optimization)

Connection performance tracing at standard interfaces of single subscriber

Tracing cell performance

Items to be traced include: UL SIR UL SIRtarget UL BLER DL TXcode power DL Throughput & Bandwidth Items to be traced include: PCPICH TxPower Tx Carrier Power DCH Subscriber Num CCH Subscriber Num Cell Code Tree Cell User Num and Cell Cmb UserNum are added in RNCv1.7; whereas DCH User Num and CCH User Num are removed from RNCv1.7

Save the file in BSC6800 LMT OM Installation Directory\Rtm

Save the file in BSC6800 LMT OM Installation Directory\Rtm

There are enough MML commands used on RNCs, so you can query them by using key words through Search function in BSC6800 OM, as shown in Figure 2-27. Type key words in Key field, enter, and the corresponding MML command is displayed.

2007-12-13

All rights reserved

Page48 , Total220


Figure 2-27 Querying key words by executing BSC6800 MML command

Figure 2-28 Querying key words by executing BSC6800v1.7 MML command

2007-12-13

All rights reserved

Page49 , Total220


& Note: The person responsible for modifying RNC MML command parameters is known. For details, see 9.2 .

2.10 Editing and Executing RNC Batch Processing Scripts 2.10.1 Editing RNC Batch Processing Scripts You can use MML command line directly to execute one or two commands on BSC6800. When repeating executing the same command (such as for adding hundreds of neighbor cells), you need not execute commands one by one by hand because it wastes time and causes mistakes. BSC6800 LMT provides powerful batch processing function. For example, if you create correct batch processing scripts for adding neighbor cells, you can use it to add hundreds of neighbor cells quickly. The following procedure introduces a method for editing scripts to add intra-frequency neighbor cells, using UltraEdit, a text file editing software. You can use multiple methods for editing scripts, or import scripts automatically by database. 1)

Click icon in BSC6800 OM, and switch to MML Client window. Type "ADD INTRAFREQCELL" in Command Input field, and enter. An interface appears as shown in Figure 2-29.

Figure 2-29 BSC6800 OM console

& Note: l l

Options in red are mandatory. Options in black are optional.

2007-12-13

All rights reserved

Page50 , Total220

WCDMA OMC Operation Guide Internal Open l

If you fill nothing in the field, you are to use the preset parameters by default.

2)

Type cell ID, RNC ID, and neighbor cell ID in corresponding fields. A complete

and executable command appears in the command line. Click icon to execute the command 3) Copy the command from editing box to a text file Use UltraEdit software, because it can easily perform column editing. For example, if you add 20 intra-frequency neighbor cells on RNC1, you must copy the command 20 times by using UltraEdit. Because you add intra-frequency neighbor cells, you use the similar command and modify the corresponding parameters. The command is as below: ADD INTRAFREQCELL: CELLID=12345, RNCID=1, NCELLID=23456, READSFNIND=NOT_READ, CELLINDIVIDALOFFSET=0, CELLSFORBIDDEN1A=AFFECT, CELLSFORBIDDEN1B=AFFECT, QOFFSET1SN=0, QOFFSET2SN=0; In the previous command line, a complete command consists of command, colon (:), parameters (separated by commas), and semicolon. In the command, you need modify parameters corresponding to CELLID, RNCID, and NCELLID. 4) Select Column > Column Mode You can edit the text file. Column editing function of UltraEdit helps you easily modify parameters corresponding to CELLID, RNCID, and NCELLID. To cancel the operation, reselect Column > Column Mode. Figure 2-30 shows starting column editing function in UltraEdit software.

Figure 2-30 Starting column editing function of UltraEdit software Use Excel file for adding list of neighbor cells because it is easy for editing and processing scripts. In the column operation mode of UltraEdit, select column field of CELLID, RNCID, and NCELLID respectively, copy corresponding field from Excel file containing neighbor cell list, and paste the field in the corresponding field area. Editing scripts is complete. Figure 2-31 shows the column editing.

2007-12-13

All rights reserved

Page51 , Total220


Figure 2-31 Column editing in UltraEdit software To batch process scripts on RNCv1.7, perform the following steps: 1)

Click icon in BSC6800 OM, and switch to MML Client window. Type "ADD INTRAFREQCELL" in Command Input field, and press Enter. An interface appears as shown in Figure 2-32.

Figure 2-32 BSC6800 OM console in RNCv1.7

& Note: l

Options in red are mandatory.

2007-12-13

All rights reserved

Page52 , Total220


2)

Options in black are optional. If you fill nothing in the field, you are to use the preset parameters by default.

Type cell ID, RNC ID, and neighbor cell ID in corresponding fields. A complete and executable command appears in the command line. Click icon to execute the command

3)

Copy the command from the editing box to a text file. Use UltraEdit because it can easily perform column editing. For example, if you add 20 intra-frequency neighbor cells on RNC1, you must copy the command 20 times by using UltraEdit. The method of editing scripts in RNCv1.7 is the same as that in RNCv1.5.

2.10.2 Executing RNC Batch Processing Scripts BSC6800 is powerful in batch processing. After editing a batch processing script, you can use the script on BSC6800 LMT, execute the batch processing, and save the executing result. To execute BSC6800 batch processing scripts, perform the following steps: 1)

Set the result of executing batch processing scripts to automatic saving. In the menu column of BSC6800 OM, select System > System Configuration and an interface appears as shown in Figure 2-33.

Figure 2-33 Configuring batch processing in BSC6800 OM 2)

Click Save as in the System Configuration dialog box. This saves the output of batch processing to be executed as a file, and in the file you can view executing of batch processing command. After executing the script, you can cancel the saving option and send result to related engineers so that the engineers check that the 2007-12-13 All rights reserved Page53 , Total220


command is executed correctly. Figure 2-34 shows saving result of batch processing in BSC6800 OM.

Figure 2-34 Saving result of batch processing in BSC6800 OM 3)

Select System > Execute Batch Commands in the BSC6800 menu bar to execute batch processing scripts. An interface appears as shown in Figure 2-35.

Figure 2-35 Selecting execute batch commands menu in BSC6800 OM

2007-12-13

All rights reserved

Page54 , Total220


4)

In the Execute Batch Commands dialog box, click Browse, select the batch processing script to be executed, and click Open The batch processing script is started, as shown in Figure 2-36.

Figure 2-36 Executing batch processing in BSC6800 OM 5)

Select different executing methods according to different requirements in the Execute Batch Commands dialog box, in Set Execute Mode, Figure 2-37 shows selecting executing methods.

2007-12-13

All rights reserved

Page55 , Total220


Figure 2-37 Executing batch processing immediately in BSC6800 OM l

l

If you execute a batch processing script at once, select Execute now and Operator Interface, then the commands are executed one by one. If an error occurs in MML command, the executing stops and the system prompts the error. Operator interference might stop executing batch processing scripts or ignore the MML command for continuous executing. If you do not select Operator Interfere, click OK directly, BSC will execute the batch processing script automatically. If an error occurs in MML command, the system executes the next command, ignoring the MML command with error. If you need modify multiple parameters and execute multiple scripts, executing scripts might affect the system greatly. Therefore you need set the system so that the system automatically starts executing the script at 0:00 and saves result. Select Execute by schedule and fill the time for executing the script.

& Note: l l l

To ensure the operation security and solve problems in time, Huawei prohibits executing customized scripts. You must select Operator Interfere when executing batch processing scripts, to avoid SPU reset. Huawei has a technique inform on this, and it is a bug of B150SP01. Executing scripts automatically is not recommended during executing batch processing scripts. If you need modify much data, do it at night.

Figure 2-38 shows customized time for executing batch processing in BSC6800 OM.

2007-12-13

All rights reserved

Page56 , Total220


Figure 2-38 Customized time for executing batch processing in BSC6800 OM 6)

Save the output file

After executing batch processing scripts, the system automatically saves the result in the file created in 1). In the BSC6800 menu bar, select System > System Configuration. An interface appears as shown in Figure 2-39.

Figure 2-39 Stopping saving result of executing script 2007-12-13

All rights reserved

Page57 , Total220


Select Stop Saving to stop saving the result of executing script, send the result file to related engineers so that they check that commands are executed correctly. Operators can directly open the text file to check the result of executing script. Errors occurring in executing batch processing include: l l l l

Wrong command word of script Error during adding neighbor cells, such as non-existent cells, conflicting scrambles of neighbor cells, and over 31 neighbor cells Improper configuration of parameters, such as parameters beyond range Improper sequence of executing script, such as modifying maximum and minimum value of pilot power before modifying pilot power

To execute BSC6800 batch processing script on RNCv1.7, perform the following steps: 1)

Configure the results of batch processing scripts to be saved automatically. In the menu column of BSC6800 OM, select System > Output Windows Setting and an interface appears as shown in Figure 2-40.

Figure 2-40 Configuring batch processing in BSC6800 OM of RNCv1.7 2)

Click Save as in the Output Windows Setting dialog box. This saves the output of batch processing to be executed as a file, and in the file you can view the exec ution of the batch processing command. After executing the script, you can cance l the saving option and send result to related engineers so that the engineers che ck that the command is executed correctly. Figure 2-41 shows saving result of batch processing in BSC6800 OM.

2007-12-13

All rights reserved

Page58 , Total220


Figure 2-41 Saving result of batch processing in BSC6800 OM in RNCv1.7 3)

Select System > Batch Commands in the BSC6800 menu bar to execute batch processing scripts An interface appears as shown in Figure 2-42.

Figure 2-42 Selecting execute batch commands menu in BSC6800v1.7 2007-12-13 All rights reserved

Page59 , Total220


4)

In the Batch Commands dialog box, click Browse, select the batch processing s cript to be executed, and click Open. The batch processing script is started, as shown in Figure 2-43.

Figure 2-43 Executing batch processing in BSC6800v1.7 5)

Select different execution methods according to different requirements in the Batch Commands dialog box, in Set Execute Mode.

l

If you execute a batch processing script at once, select Go and Manual Mode, th en the commands are executed one by one. If an error occurs in MML command, the execution stops and the system prompts the error. Operator interference migh t stop executing batch processing scripts or ignore the MML command for continu ous execution. If you do not select Manual Mode, click OK directly, BSC will exec ute the batch processing script automatically. If an error occurs in MML command, the system executes the next command, ignoring the MML command with error. If you need to modify multiple parameters and execute multiple scripts, executing scripts might affect the system greatly. Therefore you need to set the system so that the system automatically starts executing the script at 0:00 and saves the result. Select Time Batch Command and fill in the time for executing the script.

l

& Note: l l l

To ensure operational security and solve problems in time, Huawei prohibits the execution of customized scripts. You must select Manual Mode when executing batch processing scripts, to avoid SPU reset. Huawei has a technique inform on this, and it is a bug of B150SP01. Executing scripts automatically is not recommended during the execution of batch processing scripts. If you need to modify a lot of data, do it at night.

2007-12-13

All rights reserved

Page60 , Total220


Figure 2-44 shows customized time for executing batch processing in BSC6800 OM.

Figure 2-44 Executing batch processing immediately in BSC6800v1.7 OM

Figure 2-45 Customizing time for executing batch processing in BSC6800v1.7 OM 2007-12-13

All rights reserved

Page61 , Total220


6)

Save the output file. After executing batch processing scripts, the system automatically saves the result in the file created in the first step. In the BSC6800 menu bar, select System > Output Windows Setting. An interface appears as shown in Figure 2-46.

Figure 2-46 Stopping saving results of script execution in BSC6800v1.7 Select Auto Save or Timed Save to save the result of script execution, send the result file to related engineers so that they check that commands have been executed correctly. Operators can directly open the text file to check the result of script execution. Errors occurring in executing batch processing include: l l l l

Wrong command word of script Error during adding neighbor cells, such as non-existent cells, conflicting scramble of neighbor cells, and exceeding 31 neighbor cells Improper configuration of parameters, such as parameters beyond range Improper sequence of executing script, such as modifying maximum and minimum value of pilot power before modifying pilot power

2.11 Other Optimizations of RNC 2.11.1 Importing and Exporting CFGMML File RNP&O engineers need know actual parameters in RNC operation, to judge whether the actual parameters are consistent with the configured parameters, and to query data related to RNC upon solving problems. Therefore the engineers need export data configuration file CFGMML.txt from RNC, in two ways: 2007-12-13

All rights reserved

Page62 , Total220


RNC imports CFGMML files automatically at 2:00 a.m. In MML command line, generate data configuration file in time from RNC by executing EXP CFGMML command. Executing this command takes several minutes.

V1.5 RNC cannot generate CFGMML files automatically, but you can generate CFGMML file by creating scheduled tasks executing ADD SCHTSK. The data configuration file generated from RNC is named in the format of CFGMML + time.txt, such as CFGMML-20050506020425.txt. The data configuration file is saved in D:\Bsc6800\BAM\FTP. To export and upload MML file, perform the following steps: 1)

Start RNC OM, type EXP CFGMML in MML command line, and execute the command

You need wait several minutes before CFGMML file is imported. 2)

Start FTP embedded in RNC OM, and upload CFGMML file to your computer from BAM

3)

Click the icon

on toolbar in BSC6800 OM, start FTP Client

The subscriber name is "FtpUsr", and the password is "rncadmin". Different user names and passwords are used in different equipment room, so you can ask equipment room manager for them. 4)

Select CFGMML.txt file, double click to copy the file to your computer from RNC BAM

If the network in equipment room is convenient, copy it directly from BAM to your computer. An interface appears as shown in Figure 2-47.

2007-12-13

All rights reserved

Page63 , Total220


Figure 2-47 Uploading CFGMML file through FTP

Figure 2-48 Exporting CFGMML files in RNCv1.6 The method of exporting CFGMML files in RNCv1.7 is almost the same as that in RNCv1.5. The only difference lies in the mode of starting the FTP client. For RNCv1.5, 2007-12-13

All rights reserved

Page64 , Total220


you need to start the FTP embedded in RNCv1.5 OM and upload the CFGMML file to your computer from BAM. Then click the icon on the toolbar in BSC6800 OM to start the FTP client; while for RNCv1.6 and later, to start the FTP client, you can double click [Installation]:\HW LMT\client\ftpclient\bin\FTPClient.exe or select Huawei local maintenance terminal. The subscriber name is "FtpUsr", and the password is "rncadmin". Different user names and passwords are used in different equipment rooms, so you can ask for them from the equipment room manager.

Figure 2-49 Starting FTP client in RNCv1.7

Figure 2-50 Exporting CFGMML file in RNCv1.7

& Note: l l

The exported file is in the .txt format. The file name is CFGMML-time.txt by default. The file is saved in \BAM\FTP on the BAM server by default.

2007-12-13

All rights reserved

Page65 , Total220


To obtain configuration data, log in to or FTP the BAM server.

2.11.2 Extracting CHR Log CHR log is a detailed call record in RNC, helpful to call drop and access problem analysis by engineers. You can view CHR logs by using Nastar of version superior to 4.0 (you cannot view CDL of RNC of version inferior to 1.3) or by using Insight plus. For how to use Insight plus, see 8.5.4. CHR log is automatically saved by RNC: l l

l l l

In BAM installation directory of BSC6800, such as D:\Bsc6800\BAM\LoadData\FamLogFmt. In format of shelf number of RNC + Log + time.log, such as 09Log20050424000044.log. The first two digits stand for the number of the frame of NodeB configured on RNC. Digits after "Log" stand for the time when CHR log is saved. For RNCv1.5, in the format of shelf number of RNC + Log + start time_end time.log.bz2, such as 01Log20060217000017_20060217030504.log.bz2. For RNCv1.6, in the format of shelf number of RNC + Log + start time_end time.log.bz2, such as 05Log20060612000208_20060612235828.log.bz2. For RNCv1.7, in the format of shelf number of RNC + Log + start time_end time.log.bz2, such as 03Log20061026000108_20061026235711.log.bz2.

2.11.3 Extracting Traffic Measurement Data Files Traffic measurement data files are periodically saved by the RNC, one file every half an hour. You use the file for analyzing traffic measurement data through Nastar software. The traffic measurement file imported into Nastar tool is the original data file, unrelated to whether traffic measurement tasks are registered. During routine work in equipment room, extract all RNC1.3 traffic measurement data of previous day in FTP\PerfFile on BAM server of BSC, all RNC1.5 data in FTP\MeasResult. The file for one day is about 32 Mbit, too large to send by Email. Different project teams have different rules on how to obtain large traffic measurement file from equipment room. RNC1.3 traffic measurement files are saved in installation directory on BAM in BSC6800, such as D:\BSC6800\BAM\FTP\PerfFile. RNC 1.3 traffic measurement files are named by default in the format of PerfFile + data + time + RNCID.xml. RNC1.5 traffic measurement files are saved in installation directory on BAM in BSC6800, such as D:\BSC6800\BAM\FTP\MeasResult. RNC 1.3 traffic measurement files are named by default according to time, such as A20060215.0000+0800-0100+0800_EMS-NORMAL.mrf.bz2. Customizing and extracting traffic measurement data in RNCv1.6: Traffic measurement of RNCv1.6 falls into M2000 version and NASTAR version. Traffic measurement of M2000 inherits that of RNCv15, customized by M2000. You can query 2007-12-13

All rights reserved

Page66 , Total220


traffic measurement through M2000. For this version, traffic measurement files within 72 hours are saved in D:\BSC6800\BAM\FTP\MeasResult. Traffic measurement of NASTAR serves the NASTAR software. It is a full-index traffic measurement file. Usually we use this file. It is saved in D:\BSC6800\BAM\FTP\NastarResult. You can download the above-mentioned two types of traffic measurement files through FTP. The system names traffic measurement files based on time by default, such as A20060313.0000+0800-0030+0800_NASTAR.mrf.bz2. Customizing and collecting traffic measurement data in RNCv1.7: The method of extracting traffic measurement in RNCv1.7 is almost the same as that in RNCv1.6. The system names traffic measurement files based on time by default, such as A20060313.0000+0800-0030+0800_NASTAR.mrf.bz2 Traffic measurement extracted from M2000 is saved in D:\BSC6800\BAM\FTP\ MeasResult, such as A20061027.1630+0800-1700+0800_EMS-NORMAL.mrf.bz2. Traffic measurement extracted from NASTAR is saved in D:\BSC6800\BAM\FTP\ NastarResult, such as A20061027.1630+0800-1700+0800_EMS-NASTAR.mrf.bz2.

2.11.4 Tracing IOS IOS is short for intelligent optimization system. You need to start IOS tracing on RNC OM console. This function is similar to tracing a single subscriber, but you do not need to enter the subscriber IMSI. Since IOS tracing affects the system operation, you are recommended to set Max calls simultaneously traced to a smaller value and not to trace all events at the same time. The file is named in the format of .tmf, such as RNC1_IOS_2006-04-13-16-08-02.tmf. The file is saved on the local OM console where you start IOS tracing. The file path an d name can be changed. The file is saved at \HW LMT\client\output\main\BSC6800\ BSC6800 version\trace by default.

2007-12-13

All rights reserved

Page67 , Total220


Figure 2-51 Tracing IOS

Figure 2-52 Configuring parameters for IOS tracing Figure 2-53 shows the interface of tracing IOS in RNCv1.7.

2007-12-13

All rights reserved

Page68 , Total220


Figure 2-53 Tracing IOS in RNCv1.7

Figure 2-54 Configuring parameters for IOS tracing in RNCv1.7

2007-12-13

All rights reserved

Page69 , Total220


& Note: HSDPA call Trace is newly added in RNCv1.7. Three types of call messages are added: l CALLTARCE_IND_HS_DSCH_RL_ACTIVED l CALLTARCE_IND_HS_DSCH_SERVING_RL_CHANGED l CALLTARCE_IND_HS_DSCH_RL_DEACTIVED Start IOS tracing or UE (both signaling plane and user plane) on LMT.

When a UE provides HSDPA service in a cell, it reports the CALLTARCE_IND_HS_DSCH_RL_ACTIVED message; when the cell changes, the UE reports the CALLTARCE_IND_HS_DSCH_SERVING_RL_CHANGED message; when HSDPA service is deactivated, the UE reports the CALLTARCE_IND_HS_DSCH_RL_DEACTIVED message.

3 M2000 OM System 3.1 Starting M2000 OM System 3.1.1 Functions By using M2000, you can: l l l

Perform batch processing on NodeB to reduce workload through starting and stopping simulated load on a batch of NodeBs Query IP address of NodeBs to be measured in M2000, start NodeB OM, and trace RTWP Query information related to alarm in M2000

3.1.2 Procedure To start M2000 OM system, perform the following steps: 1)

Double-click M2000 icon to start M2000, and type the subscriber name and password, as shown in Figure 3-1

2007-12-13

All rights reserved

Page70 , Total220


Figure 3-1 Login of M2000 OM system You perform starting and stopping simulated load on NodeB in M2000 in equipment room, but only authorized super subscribers can use the function in M2000. Equipment room operators manage and distribute user names and passwords uniformly. The password to the super user is in the charge of specified managers in equipment room, so you must follow rules using it. 2)

Click the icon MML Command in M2000, to switch to M2000 MML command line interface, as shown in Figure 3-2

Figure 3-2 Starting M2000 OM system

2007-12-13

All rights reserved

Page71 , Total220


3.2 View MML command execution results on the M2000 After you run an MML command, you can view the list of generated packets in the MML Command window. Operation procedure: 1）

Choose Maintenance > MML Command or click shortcut icon

2）

Select an MML command on the Command tab page.

3）

In the NE tab, MML commands are classified by NE type and are displayed in a list. Select the name of the NE that has executed an MML command.

4）

View the command and the packets displayed on the General Maintenance tab page.

.

Subsequent processing: The system supports the functions of packet exporting and packet cleaning. 1）

Select an MML command on the Command or NE tab page.

2）

Right-click the command and choose Export All or Clean Packets.

l

The system allows the MML command packets in which the state is COMPLETED to be cleaned.

l

When the system is issuing an MML command, the options Export All and Clean Packets are disabled.

l

Before you clean packets, the system displays a dialog box, prompting you whether to export the packets. If you click Yes, the system saves the exported packets to the path you have selected. If you click No, the system does not save the reported packets.

3.3 View Subsequent Packets Generated by an MML command on the M2000 The MML Command window displays only one packet. Therefore, when an MML command is sent to an NE and the NE returns more than one packet, you can use this function to view the other packets. After you open the Subsequent Packet Browsing window, the system automatically generates a configuration file to buffer the subsequent packets. An information box, displayed at the lower right of the window, indicates that the subsequent packets are buffered in the configuration file. After you close the Subsequent Packet Browsing window, the system automatically deletes the buffered file. 1）

Choose Maintenance > Subsequent Packet Browsing or click the Subsequent Packet Browsing window.

2）

In the Subsequent Packet Browsing window, right-click and choose Set a Prompt for Subsequent Packets.

2007-12-13

All rights reserved

to open

Page72 , Total220


3）

Select one or more NEs in the navigation tree. When the M2000 receives the subsequent packets from the selected NEs, a prompt is displayed in the output window of the system and at the lower right side of the client.

In the Subsequent Packet Browsing window, you can perform the following operations on the displayed packets: l

Click Clear or right-click and choose Clear Packet to clear all packets from the output window.

l

Click Save or right-click and choose Save Window Text as to save the exported packets.

Right-click and choose Start Scrolling to start the scrolling display of packets. Right-click and choose Pause Scrolling to pause the scrolling display.

3.4 Start the configuration management express (CME) on the M2000. The CME is a graphic offline configuration tool for WRAN. For easy use, the M2000 provides the function of directly starting the CME of an NE on the topology. Preconditions l

Before starting the CME of the NE, the corresponding version of the CME software of the NE must be installed on the client PC of the M2000.

l

The version of the installed CME must be consistent with the software version of the NE. Otherwise, the CME cannot be started.

Background information Only the CME of RNCs and NodeBs can be started. Operation procedure On the M2000 client, choose Tools > WRAN CME to start the CME client.

3.5 Extract BCP compression package through CME on the M2000. The BCP compression package is the configuration data file of the RNC. By importing and exporting the BCP compression package, you can easily modify the data configuration of the RNC when the CME is in the offline state. The BCP synchronization method of the CME varies with the NEs. Except in the version V29072, the synchronization method of the BCP compression file of other NEs is as follows: 1）

2007-12-13

Right-click on the physical topology and choose MML Command.

All rights reserved

Page73 , Total220


2）

2007-12-13

Run the EXP CFGDATA command, with no value specified for the Viewname parameter.

All rights reserved

Page74 , Total220


3）

Log in to the FTP of the BAM and find the required CMECfgSyncView.zip file in the /BAM/VersionA/FTP/ExportCMESyncView/ directory.

The method of obtaining the BCP compression file of an NE in V29072 is slightly different. The command to be executed contains an additional parameter MOC ID. Before running the command, type All in this field. The path is the same as the one used for the preceding command.

3.6 Start the LMT of NEs on the M2000. The local maintenance terminal (LMT) is the near-end operation and maintenance system of NEs. The LMT is used when the direct connection to an NE fails owing to the improper firewall setting. The NE can be connected through the agent LMT. For easy use, the M2000 provides the function of directly starting the LMT of NEs on the topology. Preconditions l

Before starting the LMT of the NE, the corresponding version of the LMT software must be installed in the client PC of the M2000.

l

The version of the installed LMT must be consistent with the software version of the NE. Otherwise, the LMT cannot be started.

Background information 2007-12-13

All rights reserved

Page75 , Total220


On starting the LMT, if you find that the current user is bound to an NE, you can automatically log in to the LMT as the user of the NE; if no user is bound to the NE, you must specify the username and password.

l

For a NodeB, when you start the LMT, the system automatically considers the M2000 as the gateway of the LMT.

Operation procedure 1）

Right-click the NE whose LMT must be started, on the physical topology or in the physical topology navigation tree.

2）

Choose Maintenance Console to start the LMT of the NE.

Counter customization and query report creation on the M2000. This section describes how to customize a counter and create a query report. It also describes the measurement between two cells on the M2000. Customize a counter on the M2000. The original counters on the M2000 do not need to be customized and can be directly queried. Some counters, however, are not available and need to be added on the M2000. The following takes the HSDPA RLC Traffic Volume (Mbytes) as an example to describe the basic procedure for customizing a counter: 1）

Make a note of the formula of the counter to be customized, for example, HSDPA RLC Traffic Volume (Mbytes) = /(1024*1024).

2）

Log in to the M2000 and choose Performance -> User-Defined Counter Management.

2007-12-13

All rights reserved

Page76 , Total220


Figure 3-3 Open the management items of the counter to be customized 3）

2007-12-13

Select the related measurements in the left pane (HSDPA Measurement Per Cell under Measurements Related to HSDPA). The original counters are generated.

All rights reserved

Page77 , Total220


Figure 3-4 Open the related measurements 4）

Right-click in the right pane for customizing a counter and choose Add. In the displayed interface, enter a counter name (HSDPA RLC Traffic Volume in MB) and type in the formula. You do not need to enter each letter of the name of each sub-counter involved, manually. Instead, you can enter several letters (including punctuations) and the name of the corresponding sub-counter is typed automatically. In this case, you can double-click the name of the sub-counter; it is then entered in the Formula Information column automatically. You can select the operators in the formula from the operator column on the right side, instead of entering each of them manually.

Precautions: Except 100 and 1000, there is no other constant in the operator column. If you want to manually enter a constant, you must enclose it within parenthesis for example, {1024}; otherwise, a grammar error is displayed. Example: After HSDPA RLC Traffic Volume (Mbytes) =/(1024*1024) is entered in the M2000, [VS.HSDPA.MeanChThroughput.TotalBytes]/({1024}*{1024}) appears in the Formula Information column.

2007-12-13

All rights reserved

Page78 , Total220


Figure 3-5 Input of the formula for customizing a counter After entering the formula, click Apply and OK. The customized counter formula is completed.

3.7 Starting Simulated Load on NodeB in M2000 3.7.1 Background NodeBs are in large numbers. If you start simulated load on a batch of NodeBs in M2000, the workload is heavy. To avoid this, you can perform batch processing operations on NodeB by using M2000. According to the actual situation, the following section describes the method for staring and stopping simulated load on NodeB. On MML Command interface, M2000 classifies NodeB according to types of NodeB. M2000 classifies NodeB to NodeB3806A, NodeB3806, NodeB3802C, and NodeB3812. In M2000, you can select NodeBs of one type for starting simulated load in batch processing. Namely, you execute the following command to start simulated load of various NodeBs according to types: STR DLSIM: LR=50;

2007-12-13

All rights reserved

Page79 , Total220


3.7.2 Procedure To start simulated load on NodeB, perform the following steps: 1)

In M2000, click MML Command to switch M2000 window to MML Command interface

2)

Select NodeB3806A on the tree in the left pane, and click the check box BTS3806AV100R003ENGC02B075 to select all BTSs of 3806A type Ticks are displayed in the selected NodeBs.

Figure 3-6 Starting 50% simulated load on NodeB3806A in M2000 3)

Type "STR DLSIM" in the right Command Input (L), and enter Local Cell ID and Load Ratio (%) text box are displayed.

If you type nothing in Local Cell ID text box, all cells under the NodeB will be loaded. 4)

Type required ratio in Load Ratio (%) text field

Fox example, you type 50 in Load Ratio (%) text field to start 50% simulated load. 5)

Click

icon or press the shortcut key F9 to start simulated load on all NodeBs

6)

The method for starting simulated load on NodeBs of different types, such as NodeB3806, NodeB3802C, and NodeB3812 is similar to that of NodeB3806A.

& Note: During starting simulated load on NodeB of the same type, click the check box before the NodeB on which you need not start simulated load, and then no ticks are displayed in the check box before unselected NodeBs. Therefore these NodeBs with ticks are started simulated load, and those NodeBs 2007-12-13 All rights reserved Page80 , Total220 l


l

l

without ticks are not started. For example, if you need not start simulated load on 3802_pohing_B, 801310_WarwickHouse_B, 801310_WarwickHouse_C, and 801170_KingHouse_A, you unselect these four NodeBs and no ticks are displayed in the check box before them. Figure 3-7 shows starting 50% simulated load on NodeB 3802C. M2000 classifies NodeB according to NodeB types. If multiple RNCs are in the serving network, NodeBs of the same type might be controlled by different RNCs. If you need start simulated load on all NodeBs under an RNC, do not select NodeBs to be loaded one by one, start simulated load on NodeB by using batch processing scripts, detailed in 3.10.2 . If you need start simulated load and change power of command channels in a project at the same time, ensure to change power of command channels before you start simulated load. Because simulated load volume is calculated based on CPICH as a benchmark, starting simulated load before changing power of CPICH pilot causes that simulated load volume does not meet requirements.

Figure 3-7 Starting 50% simulated load on NodeB 3802C

3.8 Stopping Simulated Load on NodeB in M2000 In M2000, stopping simulated load on NodeB in M2000 is the similar to that of starting simulated load. On MML Command interface, stop simulated load on NodeB3806A, NodeB3806, NodeB3802C, and NodeB3812 respectively. Stop simulated load on NodeB of the same type in batch processing. Stop simulated load on all NodeBs according to NodeB type by executing the STP DLSIM; command as shown in Figure 3-8:

2007-12-13

All rights reserved

Page81 , Total220


Figure 3-8 Stopping simulated load on NodeB 3802C

& Note: If you have not started simulated load on a NodeB, stopping simulated load on this NodeB leads to an RL setup failure every 128 times. This problem will be solved in updated version of NodeB V100R003C02B075

3.9 Querying Starting Simulated Load on NodeB In M2000, querying starting simulated load on NodeB is similar to starting simulated load on NodeB. On MML Command interface, query starting simulated load on NodeB3806A, NodeB3806, NodeB3802C, and NodeB3812 respectively. Query starting simulated load on NodeB of the same type in batch processing. Query stopping simulated load on all NodeBs by executing the DSP DLSIM; command: If you do not use M2000 in NodeB OM, query starting simulated load on a single NodeB by executing the DSP DLSIM; command. 4.4 details this method. On RNC (BSC6800) OM interface, you can query starting simulated load on cells under a NodeB. You can query the downlink maximum transmit power of the cell by using timely monitoring cell performance function. Figure 3-9 shows querying downlink maximum transmit power in BSC6800 OM.

2007-12-13

All rights reserved

Page82 , Total220


Figure 3-9 Querying downlink maximum transmit power in BSC6800 OM In Figure 3-9, if you start 36% simulated load on the cell, bar chart of Tx Carrier Power is 36%. You can view starting simulated load on the cell by using this method. Figure 3-10 shows displaying downlink transmit power of the cell when starting 50% simulated load.

Figure 3-10 Displaying downlink transmit power of the cell 23191 when starting 36% simulated load

2007-12-13

All rights reserved

Page83 , Total220


3.10 Editing and Executing Scripts for Starting and Stopping Simulated Load on NodeB in M2000 3.10.1 Editing Scripts for Starting and Stopping Simulated Load on NodeB in M2000 In M2000, if you need start and stop simulated load on multiple NodeBs at the same time, and NodeBs are not of the same type, starting and stopping simulated load on NodeB one by one are difficult and easy to be wrong. M2000 provides batch processing function, so you can start and stop simulated load on candidate sites quickly by editing scripts in command format. In M2000: l

The script for starting simulated load is

STR DLSIM: LR=50; {NodeB 1, NodeB 2,…} l

The script for stopping simulated load is

STP DLSIM; {NodeB 1, NodeB 2,…} & Note: l l l

The commands for starting and stopping simulated load are ended with a semicolon. In the brace, the names of NodeBs on which simulated load is started and stopped are listed, including that there is only one NodeB in the brace. If multiple NodeBs on which simulated load are started and stopped can be listed in the brace in one command, or can be listed in multiple commands while a brace includes only one NodeB name, listed as below: STR DLSIM: LR=50; {NodeB 1} STR DLSIM: LR=50; {NodeB 2}

l

NodeB names must be consistent with names in M2000, otherwise M2000 cannot identify them. The NodeB names are obtainable from RNP planning database, and exporting NodeB names from M2000 is strongly recommended. The section 3.11 introduces the method for exporting NodeB names.

3.10.2 Executing Batch Processing Scripts for Starting and Stopping Simulated Load on NodeB in M2000 To execute batch processing scripts for starting and stopping simulated load on NodeB in M2000, perform the following steps: 1)

Double-click the M2000 icon to start M2000 OM system You can start and stop simulated load in M2000 only when authorized as an administrator.

Figure 3-11 shows M2000 OM interface.

2007-12-13

All rights reserved

Page84 , Total220


Figure 3-11 M2000 OM interface 2)

Click Script Command icon in toolbar in M2000 An interface as shows in Figure 3-12 is displayed.

Figure 3-12 Importing scripts in M2000 3)

Click Add button, select edited scripts for starting and stopping simulated load on NodeB, and click OK to start batch processing task1 for starting and stopping simulated load on NodeB

2007-12-13

All rights reserved

Page85 , Total220


4)

Click Activate button after correctly exporting scripts for starting and stopping simulated load on corresponding NodeBs. The system automatically executes commands for starting and stopping simulated load on NodeB, as shown in Figure 3-13.

Figure 3-13 Executing batch processing scripts in M2000

3.11 Method for Exporting NodeB Names in M2000 You must list names of corresponding NodeBs in brace { } in the scripts for starting and stopping simulated load on NodeB. The NodeB names must be consistent with names in M2000, otherwise M2000 cannot identify them. The NodeB names are obtainable from RNP planning database, and exporting NodeB names from M2000 is strongly recommended. To export NodeB names, perform the following steps: 1)

Select Configuration > Reports > NE Report Figure 3-14 shows exporting NodeB names in M2000.

2007-12-13

All rights reserved

Page86 , Total220


Figure 3-14 Exporting NodeB names in M2000 2)

Select range for data to be exported in the dialog box displayed

In a WCDMA network, two RNCs are names as RNC1 and RNC2. In network optimization test, if you need load all NodeBs under RNC1, select RNC1 directly, as shown in Figure 3-15.

2007-12-13

All rights reserved

Page87 , Total220


Figure 3-15 Selecting data to be exported in M2000 3)

Click OK after selecting RNC1. M2000 exports information about all NodeBs under RNC1.

4)

Right click on NE Report interface, and select Save menu to save exported data about NodeB as Excel format, as shown in Figure 3-16

2007-12-13

All rights reserved

Page88 , Total220


Figure 3-16 Saving exported data about NodeBs in M2000 The exported data about NodeBs from M2000 is in Excel format. In the Excel, NodeB names are listed in column, so you can perform column-to-row conversion of NodeB names in UltraEdit by selecting Format > Convert CR/LFs to Wrap. Replace spaces between NodeB names with commas, but there must be no comma after the last NodeB name. Figure 3-17 shows performing column-to-row conversion of NodeB names in UltraEdit.

2007-12-13

All rights reserved

Page89 , Total220


Figure 3-17 Performing column-to-row conversion of NodeB names in UltraEdit 5)

Copy all the NodeB names after editing, and paste them in the brace of STR DLSIM: LR=50; { }.

You complete creating batch processing scripts for starting and stopping simulated load on NodeB in M2000.

2007-12-13

All rights reserved

Page90 , Total220


Figure 3-18 Replacing spaces between NodeB names with commas in UltraEdit

& Note: l l

If multiple NodeBs on which simulated load are started and stopped are listed in multiple commands, ensure each command includes only one NodeB name Replace spaces between NodeB names with commas, but there must not be a comma before the last NodeB name.

3.12 Querying NodeB IP Address in M2000 In M2000, you can query IP addresses of all NodeBs. You do it to construct connections with NodeBs, and thus you can start NodeB OM. To start NodeB OM, perform the following steps: 1)

Start M2000, and switch to Physical Topology window, as shown in Figure 3-19

2007-12-13

All rights reserved

Page91 , Total220


Figure 3-19 Physical topology window in M2000

2)

Click icon on the interface, type site ID of NodeB to be queried, query IP address of the NodeB. You can use the output IP address in the NodeB OM.

Figure 3-20 Querying IP address of a candidate NodeB in M2000 2007-12-13 All rights reserved

Page92 , Total220


3.13 Extracting Alarm Data in M2000 To enter the querying interface, perform the following steps: 1)

Double-click M2000 icon to start M2000 OM system, and type the user name and password as required in equipment room

2)

Select Fault > Query > Current Fault Alarms to enter the following interface as shown in Figure 3-21. You can also enter the interface by click the shortcut icon marked in red in the toolbar.

Figure 3-21 Querying alarm data in M2000 To extract alarm data, perform the following steps: 3)

If you need query data of one or more NodeBs, select NE (group by NE Type) in NodeB_CUR_ALARM drop-down menu. You can see various NE types.

4)

Click before NodeB3802C, NodeB3806, and NodeB3806A in NE (group by NE Type) to extend drop-down list of the NodeB Select NodeB to be queried in the drop-down list.

5)

If you need query alarm data of all NodeBs, select NodeB_CUR_ALARM > NE TYPE, and then select NodeBs of 3802C, 3806, 3806A, and 3812.

6)

Click

7)

Click

8)

Click , and select Unacknowledged & Uncleared Fault and Acknowledged & Uncleared Fault, namely, the current alarm

to select alarm of all levels to select alarm of all types

Figure 3-22 shows setting querying alarm in M2000. 2007-12-13

All rights reserved

Page93 , Total220


Figure 3-22 Setting querying alarm in M2000 9)

Click Query button in the right corner, as shown in Figure 3-23

Figure 3-23 Saving alarm data as files 10) Click Save… button to save alarm data

2007-12-13

All rights reserved

Page94 , Total220


3.14 Extracting Traffic Measurement Data in M2000 The RNC monitors traffic measurement performance on a real-time basis. It saves traffic measurement data on RNC BAM and also reports traffic measurement data periodically to M2000. It saves traffic measurement data of about three days, but M2000 saves data for a longer time. If you query historic traffic measurement data, query and extract in M2000.

3.14.1 Querying Traffic Measurement Data in M2000 To query traffic measurement data in M2000, perform the following steps: 1)

Double-click the M2000 icon to start M2000 OM. Type the user name and password as required in equipment room.

2)

Select Performance > Query Result. An interface appears as shown in Figure 3-24.

Figure 3-24 Querying traffic measurement data in M2000

3.14.2 Extracting Traffic Measurement Data in M2000 To extract traffic measurement data in M2000, perform the following steps: 1)

Create query tasks In Figure 3-24, select New Query. The Query interface appears, as shown in Figure 3-25. Set querying traffic measurement, including:

2007-12-13

All rights reserved

Page95 , Total220

WCDMA OMC Operation Guide Internal Open l l l

Object Selection Counter Selection Other Setting

Figure 3-25 Setting querying traffic measurement in M2000 2)

After setting, click Save Template to save the setting as a template, which help query of the same tasks

3)

Click Query button in the Query interface Figure 3-26 shows the traffic measurement data.

2007-12-13

All rights reserved

Page96 , Total220


Figure 3-26 Displaying traffic measurement data. 4)

Click Save in the right lower corner to save traffic measurement data.

3.15 Method for Counter self-defining and new report setup in M2000 This chapter introduce that how to define the Counters and how to setup a new report and how to operate the cell measurements between two cells and so on.

3.15.1 Enabling of measurement switches of a customized formula on the M2000 Before querying a customized counter in the M2000, you must enable the measurement switch of the customized formula in the counter manager. 1)

Choose Performance -> Measurement Management->Measurement Settings. Select the unit to be measured from the pane on the right. For example, choose Management Related to HSDPA -> HSDPA Management Per Cell.

2007-12-13

All rights reserved

Page97 , Total220


Figure 3-27 Opening a customized counter 2)

Select the customized counter HSDPA RLC Traffic Volume (Mbytes) from the p ane displayed on the right. In the right pane, Measurement related to HSDPA is displayed in Function Set and HSDPA Measurement per cell is displayed in Fu nction Subset.

3)

Select the customized counter in the time granularity, click Apply at the lower-rig ht corner, and wait for the items of the customized counter to be displayed. (Note: There are two measurement periods for the M2000 to obtain measurements from the BAM: 5 minutes and 15 minutes. In most cases, we select the 15-minute peri od.)

2007-12-13

All rights reserved

Page98 , Total220


Figure 3-28 Validating the customized counter The counter customization is now complete and the related measurement switches are enabled to register the cells to be measured. After several measurement periods, you can query the results.

3.15.2 Export and import of a customized counter in the M2000 1)

Exporting a customized counter

After customizing a formula, select the customized counters to be exported (multiple customized counters can be exported at one time), right-click and choose Export. In the displayed interface, select a file path and a file name, and click Save (multiple customized counters can be saved in a file). 2)

Importing a customized counter

Right-click in the following window and choose Import. In the displayed interface, select the name of the counter file to be imported and click Open.

2007-12-13

All rights reserved

Page99 , Total220


Figure 3-29 Importing a customized counter You can now find the customized counter in the M2000.

3.15.3 Customization and generation of a query report on the M2000 Regardless of whether a counter in the M2000 is an original counter or a customized counter, we must customize a corresponding query report before querying the counter. The HSDPA-related query is taken as an example to describe the procedure for customizing a query report. 1)

Log in to the M2000 and choose Performance -> Query Result. Right-click in th e right pane and choose New Query. A query window is displayed. Select Netwo rk RNC in the navigation tree on the left of the window and click the measuremen t unit HDPA Measurement per cell in the measurement set Measurement relat ed to HSDPA. Select the object RNC_Name under Object Settings in the right p ane.

2007-12-13

All rights reserved

Page100 , Total220


Figure 3-30 Customizing a query report—select a measurement object 2)

From Available Counters in the Counter Settings page, select the counters to be measured and click the arrow in the middle to view the Selected Counters.

2007-12-13

All rights reserved

Page101 , Total220


Figure 3-31 Customizing a query report—select the corresponding counter values 3)

In the Other Settings page, select a time mode, period, and data range accordin g to the requirements.

2007-12-13

All rights reserved

Page102 , Total220


Figure 3-32 Customizing a query report—select a time mode and a period 4)

Click Save Template. In the displayed page, enter the name of the query report a nd the directory in which the query report is to be saved. In the example, the nam e of the query report is monthlyreport_HSDPA and the directory is Monthly-rep ort.

2007-12-13

All rights reserved

Page103 , Total220


Figure 3-33 Customizing a query report—save a customized query report 5)

Generate a customized query report. Choose Performance -> Query Result. Yo u can view the reports to be generated, for example, monthlyreport_HSDPA in t he Monthly_report directory. Right-click monthlyreport_HSDPA and select a qu ery period from Query Result options.

Right-click the corresponding report generated in the right pane, choose Export All, and select a path and file name to save the report. Now, a query report is generated.

2007-12-13

All rights reserved

Page104 , Total220


Figure 3-34 Generation of a customized report

3.15.4 Query of measurements between two cells on the M2000 1)

check whether the measurement between two cells is enabled on the LMT. If not, enable the measurement between two cells on the RNC.

MML command: ADD MEASOBJ: MOC=CELL_GCELL;

2007-12-13

All rights reserved

Page105 , Total220


Figure 3-35 Enabling the measurement between two cells 2)

Choose Performance -> Measure Management > Measure Settings.

3)

Select the unit (CELL_GCELL/NCELL) to be measured from the left pane.

CELL_GCELL: RNC >Measurement related to inter-Radio Access Technology Handover >Measurement between a cell and a intRAT cell CELL_NCELL: RNC > Measurement related to Neighbour Cell Measurement > Management between a cell and a UMTS cell For details on the other steps, see "Customization and generation of a query report on the M2000".

2007-12-13

All rights reserved

Page106 , Total220


Figure 3-36 Enabling the measurement between two cells (CELL_GCELL)

3.16 Extraction of NodeB traffic measurement data on the M2000 The R3 of the M2000 and later versions supports NodeB traffic measurement. The NodeB traffic measurement function is made available with the introduction of the RNC V17. For details on the counters in each version, refer to the corresponding document. The counters of the NodeB include hardware resource usage statistics, Iub bandwidth consumption statistics, HSDPA feature, and HSUPA feature. These counters are very important for the network performance analysis, subsequent network optimization and network maintenance. As there are many NodeB NEs, the traffic measurement of a NodeB is extracted by the M2000. That is, the M2000 automatically collects the traffic measurement data from the NodeB and saves it.

3.16.1 Establishment of a data export task on the M2000 After obtaining the traffic measurement data of a NodeB, the M2000 imports it to the database and makes relevant treatments (for example, time summarization/cell summarization) to help you query the traffic measurement indexes. On the M2000, you can query the traffic measurement indexes of a NodeB in the same way as querying 2007-12-13 All rights reserved Page107 , Total220


those of an RNC. For details, see "Customization and generation of a query report on the M2000". The M2000 does not provide the default function of backing up NodeB traffic measurement data. Therefore, the export function of the M2000 must be used. Through the export function, NodeB traffic measurement data is periodically exported and saved in a file for the Nastar to analyze. The procedure for using the data export function of the M2000 is as follows: 1)

On the M2000 client, choose Maintenance -> Centralized Task Management to start the centralized task management.

Figure 3-37 Starting the centralized task management 2)

Choose Centralized Task Management -> File Interface -> Performance Data Exp ort, and then double-click Performance Data Export to modify the task attributes.

2007-12-13

All rights reserved

Page108 , Total220


Figure 3-38 Starting the performance data export function 3)

Modify the attributes of the exported task as required.

2007-12-13

All rights reserved

Page109 , Total220


Figure 3-39 Modifying task attributes 1)

File format: The M2000 can export performance data to a .CSV, .XML, or .TXT fil e according to the requirement of the background analysis tool. Currently, the Na star supports the .CSV and .XML file formats.

2)

Export period: Set the export period to 5, 15, 30 or 60 minutes, depending on the requirements. Currently, a NodeB supports these four periods.

If a certain export period is selected but no measurement units related to a NodeB are found at the bottom of the interface, the adaptation layer of the current NodeB does not support the export period. 3)

Delay: The delay means how long after the data is prepared a request is originat ed to obtain NodeB data.

4)

Directory: The exported NodeB data is saved in the directory set in the attributes page.

5)

After the attributes of the task are modified, start the task. The traffic measureme nt file of the NodeB is automatically exported to the corresponding directory until t he task attributes are modified.

The following is an example of a log that records the export of a NodeB traffic measurement file.

2007-12-13

All rights reserved

Page110 , Total220


Figure 3-40 File export log l

In the M2000 R6B063SP03, the exported NodeB traffic measurement file supports two types: one is a file containing all measurement units for each NodeB and the other is a file containing all NodeBs for each measurement set. These two types can be set on the M2000. Usually, one file for one measurement set is adopted. How to set the export of a traffic measurement file according to NEs (namely, a file for a NodeB) is complicated and therefore a file for a NodeB is not recommended.

l

When setting the file export on the M2000, you must set the value of FileExportMode in the configuration file in the /export/home/omc/var/etc/pm/tool/PmexpParam.xml directory to 0. Thus, the Nastar can import the exported NodeB traffic measurement file containing no host name or NE type name.

3.16.2 Obtaining of NodeB data By default, the exported NodeB traffic measurement file is saved in the /export/home/omc/var/fileint/pm/ directory in the M2000. The name of the traffic measurement file indicates the data time segment. You can copy the corresponding data segments according to the analysis requirements. An example of NodeB traffic measurement file is as follows: pmresult_50331649_15_200707270030_200707270045.csv, which corresponds to a traffic measurement file within the time segment from 00:30 to 00:45 on July 27.

2007-12-13

All rights reserved

Page111 , Total220


4 NodeB OM System 4.1 Starting Remote OM of NodeB RNP&O engineers can install NodeB OM software on the clients by default in equipment room.

& Note: l

l l

Select a proper software version (English version or Chinese version), consistent with that of equipment room. Otherwise, different version might lead to reset of RNC and NodeB, and consequently, version conversion occurs. The sequence number is NodeB. Select the typical installation mode.

To start remote OM of NodeB, perform the following steps: 1)

Query the NodeB IP address according to descriptions in 3.12

2)

Click

icon to start NodeB OM

You must type the user name and password, as shown in Figure 4-1. Equipment room operators distribute user names and passwords uniformly. 3)

Type the site ID directly in Office text box or view it from drop-down list l

2007-12-13

If the site ID exists, it will be shown in Figure 4-1.

All rights reserved

Page112 , Total220


Figure 4-1 Login to NodeB l

If the site ID does not exist, you need to add connection with NodeB as below:

Click Office button, and an Office Management dialog box is displayed. Click Add button, and an Office Information dialog box is displayed. Type ID or name of the NodeB, type IP address (obtainable from M2000, see 3.12 ), and click OK to return to Login interface. An interface appears as shown in Figure 4-2.

2007-12-13

All rights reserved

Page113 , Total220


Figure 4-2 Adding connection with NodeB 4)

Select ID 20690 in drop-down list or type "20690" directly in Office text box, as shown in Figure 4-3.

Figure 4-3 Starting OM of specified NodeB

5)

Type "NodeB" in Password text box, and click OK to start OM of specified NodeB.

2007-12-13

All rights reserved

Page114 , Total220


& Note: In the Office text box, select the ID of specified NodeB by typing it directly or selecting it from the drop-down menu, and otherwise you start OM of other NodeBs.

To start remote OM of NodeBv1.7, perform the following steps: 6)

Query the NodeB IP address as described in 3.12

7)

Click

to start NodeB OM.

You must type the user name and password, as shown in Figure 4-4. Equipment room operators assign user names and passwords. 8)

Type the site ID in the Office text box or view it from drop-down list. l

If the site ID exists, it will be shown in Figure 4-4.

Figure 4-4 Login to NodeBv1.7 l

If the site ID does not exist, you need to create a connection with NodeB as below:

Click Office, and the Office Management dialog box appears. Click Add, and the Office Information dialog box appears. Type ID or name of the NodeB, type IP address (obtainable from M2000, see 3.12 , or obtain it by entering LST IPOAPVC in M2000 or corresponding RNC), and click OK to return to Login interface. When M2000 fails, you cannot operate any NE through M2000. You can enter LST IPOAPVC on the corresponding RNC to obtain the IP address of NodeB. An interface appears as shown in Figure 4-5.

2007-12-13

All rights reserved

Page115 , Total220


Figure 4-5 Adding connection with NodeBv1.7

9)

Select NodeB from the drop-down menu or type "NodeB" in Office text box, and then enter NodeB in the Password text box. Then click OK to start OM of a specified NodeB.

Note: In the Office text box, select the ID of specified NodeB by typing it directly or selecting it from the drop-down menu, and otherwise you start OM of other NodeBs. Meanwhile, you must select the correct NE type (BSC6800 or NodeB) when adding an office direction because all LMTs are integrated into one LMT in RNCv1.6 and later. You can select the LMT type as required.

2007-12-13

All rights reserved

Page116 , Total220


Figure 4-6 Starting OM of specified NodeBv1.7 If you maintain NodeB using your laptop, you can copy the updated address database of the NodeB OM console to your laptop. As a result, you do not need to add NodeB one by one. To achieve this goal, overwrite the UMSCUI file in the installation directory on your laptop with that in C:\HWLMT\NodeBV100R006\Data on the computer used to maintain NodeB in the equipment room.

4.2 Starting Local OM of NodeB If remote OM is impossible due to transmission problems, engineers must check the work state and data by local NodeB OM. RNP&O seldom use local OM of NodeB, so the following describes local OM of NodeB. 1)

2) 3)

When a NodeB is delivered from the factory, the default IP address of NMPT for local OM is 17.21.2.15. Engineers can change the IP address of laptop computer to ensure that the IP address of laptop computer and the NodeB is in the same network segment. Connect interfaces of the laptop computer and main control board of NodeB with direct connection network cable. Start NodeB OM, and the following operations are the same as that in 4.1 .

4.3 NodeB MML Commands You seldom perform OM on a single NodeB during radio network planning and optimization. You perform related OM on NodeB on RNC and M2000. Though RTWP data is in a large quantity, you collect it on a single NodeB. To query data, record data, and modify parameters on NodeB, you can execute MML commands frequently in NodeB OM. Due to multiple MML commands of NodeB, you can query commands by typing keywords in Search function in NodeB OM as below: 1) 2)

Type keywords in Keyword text box Enter, and corresponding MML commands are displayed

Table 4-1 lists and classifies MML commands used on NodeB in radio network planning and optimization by taking BTS3802C as the example. 2007-12-13 All rights reserved Page117 , Total220


Table 4-1 A set of MML commands used frequently on NodeB in RNP&O Equipment NodeB

Type

Command

Detailed operation

Remarks

Querying data

Command for querying License includes: DSP LICENSE

The left command is for querying the following information related to License by executing this command: License state Maximum number of uplink and downlink CE Maximum number of local cells

Command for querying cell states includes: DSP LOCELL

The left command is for querying state of specified or all local cells, logical cell state, diversity feature, and setup time Subscribers query configured data of local cell using the left command. When subscribers specify the local cell ID, the system provides detailed configuration data of the local cell. When subscribers specify no local cell ID, the system provides simple data of all local cells Subscribers query power, scramble, channel code of common channels using the left command

The default License configuration functions if: License is not configured License is removed License number is smaller than that of system configuration –

Command for querying local cell configuration includes: LST LOCELL

Command for querying logical cell configuration includes: DSP CELLCFG Command for uploading parameters and log files on NodeB includes: ULD FILE

Modifying data

2007-12-13

Commands for modifying cell states include: BLK/UBL CELL Commands for querying or setting desensitization intensity include: DSP/SET DESENS: Commands for querying, starting, and stopping downlink simulated load include: DSP/STR/STP DLSIM:

–

–

Subscribers obtain files saved on NodeB by executing the left command, and upload the files into specified directory on specified FTP server. Subscribers can choose compressed uploading or uncompressed uploading. According to selected parameters, the left command supports uploading the following files: Operation log files Equipment archive files NMPT log files Board log files RTWP routine test log files The left command is respectively for blocking or unblocking specified cells or all existing cells.

–

For example, setting the floor noise of cell 12101 is: SET DESENS: LOCELL=12101, DI=3;

Use M2000 to perform operations on NodeB, and this reduces workload

For example, perform 50% downlink simulated load on cell 12101 by executing command: STR DLSIM: LOCELL=12101, LR=50;

All rights reserved

–

Page118 , Total220

WCDMA OMC Operation Guide Internal Open Equipment

Type

Command

Detailed operation

Remarks

Command for modifying cell radium includes: MOD LOCELL

Subscribers modify parameters of local cell by executing the command. The indexes to be modified include: Cell radium Radium of cell handover inner diameter Uplink and downlink frequency point number Maximum transmit power of cell Desensitization intensity

Enable cell HSDPA

MOD LOCELL: HSDPA=TRUE;

If you modify other parameters, you do as below: Execute RMV LOCELL command to remove the local cell. Execute ADD LOCELL command to add a local cell TRUE means that HSDPA can be supported. FALSE means that HSDPA cannot be supported.

Configure HSDPA cell parameters

Such as, configuring cell 1, setting power margin to 10%, distributing power to HS-SCCH fixedly, distributing 5% to each HS-SCCH SET MACHSPARA: LOCELL=1, PWRMGN=10, PWRFLG=FIXED, PWR=5; Configure power control mode and power offset of HSUPA downlink control channel, such as: SET MACEPARA: SEHICHPCPARA=TRUE, SEHICHPCMOD=FIXED, SEHICHPOWER=-150

Configure HSUPA cell parameters (SET MACEPARA)

4.4 Starting/Stopping and Querying Simulated Load on NodeB 4.4.1 Starting Simulated Load on NodeB If you start simulated load on a single NodeB, you can start simulated load on a single NodeB directly or perform it in M2000 OM. To start simulated load on multiple NodeBs, you can perform batch processing operations on NodeBs in M2000 to reduce workload. For details, see 3.10.2 . The command for starting 50% simulated load on a single NodeB is as below: STR DLSIM: LR=50; Figure 4-7 shows starting 50% downlink simulated load on NodeB 3812E.

2007-12-13

All rights reserved

Page119 , Total220


Figure 4-7 Starting 50% downlink simulated load on NodeB 3812E Figure 4-8 shows setting desensitivity strength of NodeB 3812E to 1 dB

2007-12-13

All rights reserved

Page120 , Total220


Figure 4-8 Setting desensitivity strength of NodeB 3812E to 1 dB

4.4.2 Stopping Simulated Load on NodeB The method for stopping simulated load on NodeB is similar to that of starting simulated load. If you stop simulated load on a single NodeB, you can directly stop simulated load on a single NodeB or perform it in M2000 OM. The command for stopping simulated load on a single NodeB is as below: STP DLSIM;

4.4.3 Querying Simulated Load on NodeB The method for querying starting simulated load on a single NodeB is similar to that of starting simulated load. The command for querying starting simulated load on a single NodeB is as below: DSP DLSIM;

2007-12-13

All rights reserved

Page121 , Total220


& Note: After HSDPA is introduced, you need to keep the last code word (Ch8, 7) of SF=8 before starting simulated load on NodeB. Therefore, you need to perform the following operation on RNC first: ADD RESERVEOVSF: CELLID=1, DLOVSFSF=SF8, DLCODENO=7

Figure 4-9 Keeping the last code word of SF=8 on RNC

4.4.4 Starting/Stopping and Querying Simulated Load on NodeBv1.7 I. Starting simulated load in NodeBv1.7 If you start simulated load on a single NodeB, you can start simulated load on a single NodeB directly or perform it in M2000 OM. To start simulated load on multiple NodeBs, you can perform batch processing operations on NodeBs in M2000 to reduce workload. For details, see 3.10.2 . The command for starting 50% simulated load on a single NodeB is as below: STR DLSIM: LR=50; Figure 4-10 shows starting 50% downlink simulated load on NodeBv1.7 3812E.

2007-12-13

All rights reserved

Page122 , Total220


Figure 4-10 Starting 50% downlink simulated load on NodeBv1.7 3812E

Figure 4-11 Setting desensitivity strength of NodeBv1.7 3812E to 1 dB II.Stopping simulated load on NodeB 2007-12-13

All rights reserved

Page123 , Total220


The method for stopping simulated load on NodeB is similar to that of starting simulated load. If you stop simulated load on a single NodeB, you can directly stop simulated load on a single NodeB or perform it in M2000 OM. To stop simulated load on multiple NodeBs, you can perform batch processing operations on NodeBs in M2000 to reduce workload. For details, see 3.10.2 . The command for stopping simulated load on a single NodeB is as below: STP DLSIM; III. Querying simulated load on NodeBv1.7 The method for querying starting simulated load on a single NodeB is similar to that of starting simulated load. The command for querying starting simulated load on a single NodeB is as below: DSP DLSIM;

& Note: After HSDPA is introduced, you need to keep the last code word (Ch8, 7) of SF=8 before starting simulated load on NodeB. Therefore, you need to perform the following operation on RNC first: ADD RESERVEOVSF: CELLID=1, DLOVSFSF=SF8, DLCODENO=7

Figure 4-12 Keeping the last code word of SF=8 on RNCv1.7

2007-12-13

All rights reserved

Page124 , Total220


4.5 Collecting RTWP Data on NodeB You can trace RTWP through RNC OM or OM of a single NodeB. The principles for tracing RTWP are as below: l l l

Trace RTWP on a new NodeB to view the ambient interference. Trace RTWP to identify problems like call drop due to uplink interference in cells during network optimization. Trace RTWP on multiple NodeBs through NodeB OM.

When you trace RTWP on multiple NodeBs through RNC OM, and the data for tracing is in a large quantity, the tracing will consume resources of RNC and affect RNC performance. Therefore trace RTWP on multiple NodeBs through NodeB OM.

4.5.1 Displaying NodeB Slots Before tracing RTWP on specified ID of NodeB, you must start NodeB OM, detailed in 4.1 . After starting NodeB OM, double click Basic Cabinet icon, and the physical structure of NodeB is displayed. The physical structure of NodeB 3806/3806A and NodeB 3802C is different. When tracing RTWP, pay attention to slot ID of radio frequency (RF) module. The slot ID is used later for starting RTWP test on different cells of a NodeB. I. NodeB 3806/3806A The NodeB 3806/3806A supports 3×1 (3 sectors, 1 carrier for each sector) configuration: l l l

The first cell corresponds to No. 2 NTRX. The second cell corresponds to No. 5 NTRX. The third cell corresponds to No. 8 NTRX.

Figure 4-13 shows the physical structure of NodeB 3806A.

2007-12-13

All rights reserved

Page125 , Total220


Figure 4-13 Physical structure of NodeB 3806A

& Note: l l

The physical structure of right part of NodeB3806A cabinet is the same as that of NodeB3806. NodeB3806A is an outdoor NodeB, and the left part of it contains power module and storage batteries.

II.NodeB 3812 The NodeB3812 is a high-capacity NodeB of Huawei, supporting 3x4 (3 sectors, 4 carriers for each sector) configuration, and 6x2 (6 sectors, 2 carriers for each sector) configuration. The NodeB consists of two symmetric half cabinets, and each half is similar to that of NodeB3806. In 6x1 (6 sectors, 1 carrier for each sector) configuration, in the left half cabinet: l l l

The first cell corresponds to No. 2 NTRX. The second cell corresponds to No. 4 NTRX. The third cell corresponds to No. 8 NTRX.

In the right half cabinet: l l l

The fourth cell corresponds to No. 10 NTRX. The fifth cell corresponds to No. 14 NTRX. The sixth cell corresponds to No. 16 NTRX.

Figure 4-14 shows the physical structure of NodeB 3812.

2007-12-13

All rights reserved

Page126 , Total220


Figure 4-14 Physical structure of NodeB 3812 III. NodeB 3802C The NodeB3802C is configured with 2 cells at most: l l

The first cell corresponds to No. 1 NDRU. The second cell corresponds to No. 2 NDRU.

Figure 4-15 shows the physical structure of NodeB 3802C.

Figure 4-15 Physical structure of NodeB 3802C IV. NodeB 3812E 2007-12-13

All rights reserved

Page127 , Total220


Figure 4-16 shows the physical structure of NodeB 3812E.

Figure 4-16 Physical structure of NodeB 3812E

Figure 4-17 Physical structure of NodeBv1.7 3812E 2007-12-13

All rights reserved

Page128 , Total220


In Figure 4-16, MAFU is the multi-carrier antenna filtering unit and MTRU is multi-carrier transmit and receiver unit (including power amplifier). l l l

The first cell corresponds to No. 0 MTRU. The second cell corresponds to No. 2 MTRU. The third cell corresponds to No. 4 MTRU

The boards stand for respectively: l l l

NBBI is the NodeB baseband interface processing unit NMPT is the NodeB main processing & timing unit NDTI is the NodeB digital trunk interface unit.

4.5.2 Querying Cells under NodeB I. Procedure To query cells under NodeB, perform the following steps:

to enter MML command line interface of NodeB.

1)

Click

2)

Type DSP CELL in Command Input text box to query cells.

3)

Click or press F9 to execute the command. The querying result is displayed in the output window.

II.Functions You query cells because: l l

You query the number of cells under the NodeB, and then start one tracing RTWP task for each cell. You save RTWP data files, with cell ID as part of the file name.

& Note: l l

Generally cells under the same NodeB are numbered in sequence. For example, a NodeB has tow cells, and cell ID of them are 58231 and 58232, as shown in Figure 4-18. Some IDs of cells under a NodeB is not displayed in sequence.

2007-12-13

All rights reserved

Page129 , Total220


Figure 4-18 Querying cells under a NodeB To query cells under NodeBv1.7, perform the following steps: 1)

Click

to enter MML command line interface of NodeB.

2)

Type DSP CELL in Command Input text box to query cells.

3)

Click or press F9 to execute the command. The querying result is displayed in the output window.

You query cells because: l l

You query the number of cells under the NodeB, and then start one tracing RTWP task for each cell. You save RTWP data files, with cell ID as part of the file name.

& Note: l l

Generally cells under the same NodeB are numbered in sequence. For example, a NodeB has two cells, and cell ID of them are 0 and 1, as shown in Figure 4-18. Some IDs of cells under a NodeB is not displayed in sequence.

2007-12-13

All rights reserved

Page130 , Total220


Figure 4-19 Querying cells under a NodeBv1.7

4.5.3 Starting Monitoring RTWP under NodeB To start Monitoring RTWP under NodeB, perform the following steps: 1)

Right click on RTWP Measurement interface and create a monitoring task The RTWP Measurement dialog box is displayed.

2)

Type directory and file name in Text FileName text box. In RTWP Measurement dialog box, meanings of each field are as below:

l

Subrack No is the Subrack number of RF shelf on NodeB, provided by NodeB OM system by default. Slot No is NTRX slot number queried in 4.5.1 . Report Period (s) is the period for reporting RTWP data to be traced. The default value is 1s. Pn (0.1 dbm) is thermal noise of receivers. The default value is 105.5 dBm. MDB FileName is the RTWP MDB files saved automatically by the system. Text FileName is the text file that data for tracing RTWP is saved as.

l l l l l

Files are named following "NxxxxxCyyyyy.txt" format (xxxxx is NodeB ID, and yyyyy is cell ID), such as N20690C58231. In this way, you can identify the NodeB ID and cell I D from the file name in post processing of RTWP files. Data files are saved in LMT def ault installation directory. Files for tracing RTWP are saved in different directories acco rding to NodeB types and versions, such as: C:\HW LMT\NodeBV100R003\BTS3806V100R003C02B075\Monitor C : \ HW L M T \ N o d e B V 1 0 0 R 0 0 3 \ B T S 3 8 0 2 C V 1 0 0 R 0 0 3 C 0 2 B 0 7 5 \ M o n i t o r Figure 4-20 shows saving RTWP files.

2007-12-13

All rights reserved

Page131 , Total220


Figure 4-20 Saving RTWP files 3)

Click Save button, and click OK. Monitoring RTWP of a cell under the NodeB is started, shown in Figure 4-21.

Figure 4-21 Starting monitoring the second cell under the NodeB 2007-12-13 All rights reserved

Page132 , Total220


Query number of cells under the NodeB by executing DSP Cell command. You need start one RTWP task for each cell. For example, the NodeB has two cells, so you must start tracing RTWP on the second cell. To use computer resources better, you add a task for monitoring RTWP in the monitoring window as below: Right click on RTWP monitoring window, select Add Task item in the displayed menu to add a task. The file is named and saved following the previous rule, such as N20690C58232.

Figure 4-22 Saving RTWP file for the second cell under NodeB

& Note: l

l

l l

l

You must not trace RTWP of over 40 NodeBs. Tracing RTWP of excessive NodeBs leads to larger consumption of computer resources. If tracing RTWP of excessive NodeBs last for a long time, the computer might runs abnormally and loses tracing data. In BTS3806/3806A, the NTRX of the second cell corresponds to No. 5 slot, and the NTRX of the third cell corresponds to No. 8 slot. If you start tracing RTWP of the second cell, change 2 to 5 in Slot No. text box. If you start tracing RTWP of the third cell, type 8 in Slot No. text box. Files are named according to the previous rules so that you can know the Node ID and cell ID. You save RTWP data as text files while NodeB save RTWP automatically as MDB files. When you process RTWP data, you do not need MDB files. Therefore you must delete MDB files saved on the computer in time to save space after RTWP text files are copied. The files are saved automatically in the default installation directory, and different types of NodeB and types. Files for tracing RTWP are saved in different directories according to NodeB types and versions, such as: C:\HWLMT\NodeBV100R003\BTS3806V100R003C02B075\Monitor C:\HWLMT\NodeBV100R003\BTS3802CV100R003C02B075\Monitor Due to problems in designing BTS3802C software, during querying some BTSs, parameters of the second cell are displayed in the first cell, and parameters of the first cell is displayed after parameters of the second cell. In Figure 4-23, cell 10042 is displayed first, and then cell 10041 is displayed later. Anyhow you must trace cell 10041 first.

2007-12-13

All rights reserved

Page133 , Total220


The first cell of BTS3802C corresponds to No. 1 NDRU. The second cell of BTS3802C corresponds to No. 3 NDRU. Type 3 in NDRU Slot No. text box during RTWP measurement of the second cell, shown in Figure 4-24.

Figure 4-23 Querying cells of BTS3802C

2007-12-13

All rights reserved

Page134 , Total220


Figure 4-24 Starting RTWP measurement of the second cell under BTS3802C To start monitoring RTWP under NodeBv1.7, perform the following steps: 1)

Right click on RTWP Measurement interface and create a monitoring task The RTWP Measurement dialog box is displayed.

2)

Type directory and file name in Text FileName text box. In RTWP Measurement dialog box, meanings of each field are as below:

l

Subrack No is the Subrack number of RF shelf on NodeB, provided by NodeB OM system by default. Slot No is NTRX slot number queried in 4.5.1 . Report Period (s) is the period for reporting RTWP data to be traced. The default value is 1s. Pn (0.1 dbm) is thermal noise of receivers. The default value is 105.5 dBm. MDB FileName is the RTWP MDB files saved automatically by the system. Text FileName is the text file that data for tracing RTWP is saved as.

l l l l l

Files are named following "RTWP measurement_year month date_time_frame numbe r_slot number" format. The ”NxxxxxCyyyyy.txt” format is recommended (xxxxx is Nod eB ID, and yyyyy is cell ID), such as N20690C58231. In this way, you can identify the NodeB ID and cell ID from the file name in post processing of RTWP files. Data files ar e saved in LMT default installation directory. Files for tracing RTWP are saved in differ ent directories according to NodeB types and versions, such as: C:\HWLMT\adaptor\clientadaptor\NodeB\BTS3812EV100R007C03B042\output\realm onitor C:\HWLMT\adaptor\clientadaptor\NodeB\BTS3802CV100R007C03B042\output\realm onitor Figure 4-25 shows saving RTWP files.

2007-12-13

All rights reserved

Page135 , Total220


Figure 4-25 Saving RTWP files in NodeBv1.7 3)

Click Save button, and click OK.

Monitoring RTWP of a cell under the NodeB is started, shown in Figure 4-26. Query number of cells under the NodeB by executing DSP Cell command. You need to start one RTWP task for each cell. For example, the NodeB has two cells, so you must start tracing RTWP on the second cell. To use computer resources better, you add a task for monitoring RTWP in the monitoring window as below: Right click on RTWP monitoring window, select Add Task item in the displayed menu to add a task. The file is named and saved following the previous rule.

2007-12-13

All rights reserved

Page136 , Total220


Figure 4-26 Starting monitoring the second cell under NodeBv1.7

Figure 4-27 Saving RTWP file for the second cell under NodeBv1.7

2007-12-13

All rights reserved

Page137 , Total220


& Note: NodeBv1.6, NodeBv1.7 and later do not save RTWP as MDB files.

4.5.4 Processing RTWP Data V400R001C02B020 Nastar support importing and analyzing RTWP data. You can start Nastar, select to import RTWP files to the project. For details, see the guide to using Nastar.

4.6 Querying and Extracting Alarm Information on NodeB 4.6.1 Querying Alarm Information on NodeB During querying cell states through RNC, if a cell is abnormal, record the name of the NodeB related to the cell. Start NodeB OM system to log in to the NodeB. Check the alarm information about the cell and the historical alarm. The causes to abnormal cell are as below. I. Alarms on Transmission If the system prompts the information shown in Figure 4-28, network connection is problematic. You can re-log in to BSC6800 OM system, and query E1T1 number of the NodeB.

Figure 4-28 Abnormal login for NodeB 2007-12-13

All rights reserved

Page138 , Total220


Figure 4-29 shows querying E1T1 number by executing LST NodeB command in BSC6800 OM system.

Figure 4-29 Querying E1T1 number in BSC6800 OM system. From previous querying, you can obtain the following information about E1T1: l l l

Subrack No. = 1 Bearing slot No. = 0 Bearing UNI link No. = 22

In BSC6800 OM system, view the E1T1 state by executing the following command: DSP E1T1: SRN=1, SN=0, PT=WBIE_EPORT, LNKN=22; Figure 4-30 shows querying E1T1 state in BSC6800 OM system.

2007-12-13

All rights reserved

Page139 , Total220


Figure 4-30 Querying E1T1 state in BSC6800 OM system From Figure 4-30, you can see "Link running state = Fault", and this means that E1T1 is in abnormal work state, so you must check the transmission of the NodeB. II.Other Alarms Start NodeB OM system, log in to the NodeB. After starting NodeB OM system, and double click Basic Cabinet icon. The physical structure of NodeB is displayed. The physical structure of NodeB 3806/3806A and NodeB 3802C is different. You can query other alarms in two ways. The first method for querying NodeB alarms is directly querying alarm on NodeB board. Figure 4-31 shows viewing board states on NodeB3806A.

2007-12-13

All rights reserved

Page140 , Total220


Figure 4-31 Viewing state of boards on NodeB3806A If problems exist in NodeB3806A hardware, yellow or red alarms appear on the corresponding boards. l l

Red indicates a critical alarm. Yellow indicates a minor alarm.

Minor alarms exist on NPMU and NLPA shown in Figure 4-31. Right click on problematic NLPA, and select Query Active Alarms. Current alarms on the board are displayed, as shown in Figure 4-32.

Figure 4-32 Content of alarm on NLPA board From Figure 4-32, temperature increase out of range and this leads to automatic shutdown of NLPA. The causes might be: l

l

The NodeB is an outdoor cabinet, with air-conditioner. If the NodeB air-conditioner works abnormally, temperature in the NodeB maybe out of range. This cause is much probable if alarms exist in three NLPAs. The NLPA fan is problematic, and this leads to temperature out of range in part of NLPA.

2007-12-13

All rights reserved

Page141 , Total220


Right click on the NPMU, and select Query Active Alarms. The NPMU alarm is displayed, as shown in Figure 4-33.

Figure 4-33 Content of NPMU alarm From Figure 4-33, you can see alarm content: air-conditioner/heat-exchanger failure and ambient temperature out of range. The second method for querying NodeB alarm is querying alarms through alarm management system. Perform the following steps: 1)

Click icon in NodeB OM system, start Alarm Management System, and query current and historical alarms on NodeB Figure 4-34 show the current alarms in NodeB alarm management system.

Figure 4-34 Current alarms in NodeB alarm management system 2)

Select Query > Query Alarm Log… on NodeB Alarm Management System interface A Query Alarm Log dialog box is displayed, as shown in Figure 4-35.

2007-12-13

All rights reserved

Page142 , Total220


Figure 4-35 Viewing configuration of NodeB alarm log 3)

In Query Alarm Log dialog box, you can configure alarm log Select…

Cleared Not Cleared Data/Time Return Numbers (1–1000)

4)

And you can View historical alarms (alarms are removed) View historical alarms (alarms still exist) Type time range for querying historical alarms Type the number of alarms to be viewed

Click OK after configuration. Historical alarms are displayed in Figure 4-36. Alarms in grey are removed.

2007-12-13

All rights reserved

Page143 , Total220


Figure 4-36 Querying historical alarms on NodeB To query and extract alarm information on NodeBv1.7, perform the following steps: Start NodeB OM system, log in to the NodeB. After starting NodeB OM system, and double click Basic Cabinet icon. The physical structure of NodeB is displayed. The physical structure of NodeB 3812E and NodeB 3802C is different. You can query other alarms in two ways. The first method for querying NodeB alarms is directly querying alarm on NodeB board. If problems exist in NodeB3812E hardware, yellow or red alarms appear on the corresponding boards. l l

Red indicates a critical alarm. Yellow indicates a minor alarm.

Figure 4-37 shows viewing board states on NodeB3812E.

2007-12-13

All rights reserved

Page144 , Total220


Figure 4-37 Viewing state of boards on NodeB Right click on problematic MAFU, and select Query Active Alarms. Current alarms on the board are displayed, as shown in Figure 4-38.

Figure 4-38 Content of alarm on MAFU board

2007-12-13

All rights reserved

Page145 , Total220


Figure 4-39 Content of alarm on NMPT board The second method for querying NodeB alarm is querying alarms through alarm management system. Perform the following steps: 5)

Click icon in NodeB OM system, start Browse Alarm, and query current and historical alarms on NodeB. Figure 4-34 shows the current alarms in NodeB alarm management system.

Figure 4-40 Current alarms in NodeBv1.7 alarm management system 2007-12-13

All rights reserved

Page146 , Total220


6)

Select Fault Management > Query Alarm Log… on NodeB Alarm Managemen t System interface. A Query Alarm Log dialog box is displayed, as shown in Figure 4-41.

Figure 4-41 Viewing configuration of NodeBv1.7 alarm log 7)

In Query Alarm Log dialog box, you can configure an alarm log: Select…

Fault Cleared Fault Not Cleared Alarm Start/End Date/Time Return Amount (1-1000)

8)

And you can View historical alarms (alarms are removed) View historical alarms (alarms still exist) Type time range for querying historical alarms Type the number of alarms to be viewed

Click OK after configuration. Historical alarms are displayed in Figure 4-42. Alarms in grey are removed. You can see settings of other advanced options, such as Alarm Severity, Detailed Option, and Physical Option.

2007-12-13

All rights reserved

Page147 , Total220


Figure 4-42 Querying historical alarms on NodeBv1.7

4.6.2 Extracting Alarm Data of NodeB You can save alarm data of NodeB in text files by following steps below: 1)

Right click on the selected alarm, and select Save the Selected Alarms

2)

Select the directory, type name of the selected in File Name text box

You can also save all alarms in text files by selecting Save all Alarms…. Figure 4-43 shows saving alarm data of NodeB.

2007-12-13

All rights reserved

Page148 , Total220


Figure 4-43 Saving alarm data of NodeB To extract alarm data of NodeBv1.7, perform the following steps: You can save alarm data of NodeB in text files by following steps below: 1)

Right click on the selected alarm, and select Save the Selected Alarms…

2)

Select the directory, type name of the selected in File Name text box

You can also save all alarms in text files by selecting Save all Alarms…. Figure 4-44 shows saving alarm data of NodeB.

2007-12-13

All rights reserved

Page149 , Total220


Figure 4-44 Saving alarm data of NodeBv1.7

4.7 Operations of NodeB Electric Antenna You must prepare for adjustment of electric antenna. The preparations include obtaining the following information of electric antenna: l l l l

Vendor Type Configuration files Down tilt

4.7.1 Process The following paragraphs are based on BTS3812E as an example. For the operation commands, see Table 4-3. After preparations, use the antenna by following the steps below: 1)

Configure an ALD switch to ON state. By default, the ALD power supply switch is in OFF state. When using an electric antenna and tower mounted amplifier (TMA), you must configure the ALD power supply switch to ON state and configure an electricity alarm threshold.

2)

Add ALD-related equipment. If you need add electric antennas or TMAs to the NodeB, you must add ALD-related equipment by configuring NodeB data. The ALD-related equipment consists of electric antenna supporting AISG protocol (AISG_RET) and TMA supporting AISG protocol (AISG_TMA). You might not configure AISG_TAM to the electric antenna system, but you must configure AISG_RET.

2007-12-13

All rights reserved

Page150 , Total220


3)

Download configuration files of electric antenna. You need download configuration files of electric antenna on NodeB so that the electric antenna functions. The configuration data is obtainable from antenna vendors. Antennas of different types vary in different configuration data.

4)

Calibrate the electric antenna. By calibrating the electric antenna, you can ensure that the range of all RET down tilt is properly set. You can restore RET to normal state in case of RET equipment failure.

5)

Check whether the down tilt of electric antenna is valid by querying the current down tilt of the electric antenna

Operations commands of different electric antenna is not necessarily the same, but similar. Table 4-2 and Table 4-3 list the frequently-used operation commands for different electric antenna. For detailed descriptions of antennas, see online help.

4.7.2 Operation Commands for Electric Antenna of BTS 3812/3806/3806A Table 4-2 lists the operations commands for electric antenna of BTS3812/3806/3806A. Table 4-2 Operation commands for electric antenna of BTS3812/3806/3806A Type

Adding

Command

Function

ADD BRD

Adding CCU

LST ANTDATATBL

Querying CCU antenna data table

DSP SCANDEV

Querying scanned result of antenna equipment

ADD CCURTBL

Adding list of CCU relations

CAL ANT

Calibrating antenna

SET ANTTILT

Setting antenna tilt

LST ANTTILTRNG Querying and setting

LST ANTTILT DSP RCU

2007-12-13

Querying range of antenna down tilt Querying current down tilt of antenna Querying current work state of RCU

All rights reserved

Remarks Adding CCU is the same as adding a common board. If the adding succeeds, the CCU is reset within a minute. You can obtain the type of RCU supported by CCU The system displays the sequence number of connected RCU and the vendor code The SECID (sector ID) and ANTID (antenna ID) only identify an RCU. MODEL is the antenna model supported by CCU. It is obtainable by executing LST ANTDATATBL. FB is the three selected frequency band at most. SERIAL (motor serial number) and VENDOR (vendor code) are antenna attribution field, marked on cover label of antenna. In addition, you can obtain them by executing DSP SCANDEV command. Actually this command is for calibrating RCU after installation of all RCUs. Executing this command takes a long time (within four minutes). After execution, the tilt returns to 0. Setting antenna tilt is divided by an entire sector or a single antenna, and it takes a long time (within one minute) – – –

Page151 , Total220

WCDMA OMC Operation Guide Internal Open Type

Command

RST RCU

Querying version information of RCU Querying current work state of CCU Querying version information of CCU Resetting RCU

RST BRD

Resetting CCU

DSP RCUVER DSP CCU DSP BRDVER

LST CCURTBL MOD CCURTBL Removing

Function

RMV CCURTBL RMV BRD

Remarks – – Querying version of CCU is the same as querying command boards – Resetting CCU is the same as resetting common boards

Querying list of CCU relations Modifying list of CCU relations Removing list of CCU relations

Parameters are equivalent to Adding list of CCU relations

Removing CCU

Before removing CCU, remove all lists of CCU relations manually

See Adding list of CCU relations

–

4.7.3 Operation Commands for Electric Antenna of BTS 3812E/A, BBU, and DBS Table 4-3 Operation commands for electric antenna of BTS 3812E/A, BBU, and DBS Command

Function

SET ALDPWRSW

Switch on ALD power supply

ADD ALD

Adding ALD equipment

DLD ALDSWCFG

Loading configuration files

CLB ANT

Calibrating antenna

SET ANTTILT

Setting down tilt

DSP ANTTILT LST ANTTILTRNG RMV ALD

2007-12-13

Querying RET down tilt Querying range of RET down tilt Removing a piece of

Remarks – Device Type indicates whether it is the RET equipment or TMA equipment. File Type indicates the file type. For loading configuration, select CONFIGDATA File Path indicates the directory of configuration files and file names IP Address indicates the IP address of FTP server, usually referring to the local server User Name indicates the user name for logging in to FTP server Password indicates the corresponding password Cabinet No indicates the cabinet No.. Subrack No indicates the subrack No.. For BTS3812E, it indicates the subrack No. of MAFU. For BBU, it indicates the subrack No. of RRU Antenna Connector No indicates the RF port of electric antenna Calibrating antenna takes 2–4 minutes. After calibration, you must reset the down tilt of antenna Site No indicates the site No. of antenna Sector No indicates the sector No. of antenna Antenna Tilt indicates the antenna tilt in the unit of 0.1 degree – – –

All rights reserved

Page152 , Total220

WCDMA OMC Operation Guide Internal Open Command RST ALD SCN ALD DSP ALDVER LST ALD

Function ALD equipment Resetting ALD equipment Scanning ALD equipment Querying ALD version Querying configured ALD equipment

Remarks – – – –

4.8 NodeB traffic measurement data collection and analysis 4.8.1 NodeB traffic measurement data collection To obtain the original NodeB traffic measurement data, do as follows: Step 1: Log in to the M2000 and choose Maintenance -> Task Management.

Figure 4-45 Task management on the M2000 Step2: Select Performance Data Output.

2007-12-13

All rights reserved

Page153 , Total220


Figure 4-46 Settings for NodeB performance data collection Step3: Click the Extended Parameters page and set the following parameters: 1)

File format: CSV

2)

Export period: It is the same as the traffic measurement data period of an RNC.

3)

Delay: To avoid too many tasks on the M2000, the output time should be later than the task start time.

4)

Export all NodeB measurement units.

Step4: Apply the preceding configurations.

4.8.2 Description of the Compatible Nastar Version The Nastar V400R001C01B053 to the Nastar V400R001C01B055 support the analysis of a NodeB traffic measurement file in the .CSV format. The Nastar V400R001C01B056 and later versions supports the analysis of a NodeB traffic measurement file in .CSV and .XML formats. The following takes the Nastar V400R001C01B056 as an example to describe the import and analysis of NodeB traffic measurement data.

Data Import You must import the configuration file of the RNC before importing NodeB traffic measurement data. Only a local cell ID and a NodeB name exist in the NodeB traffic measurement data; you must establish the association between the local cell and the cell ID through the configuration file. Import the configuration data, and then import the NodeB traffic measurement data as shown in Figure 2-17. The procedure is the same as that of importing RNC traffic measurement data. For details, refer to the Nastar Operation Guide.

2007-12-13

All rights reserved

Page154 , Total220


Figure 4-47 Importing a NodeB traffic measurement file

Data Query The operations for querying after data import are the same as those for querying the RNC traffic measurement data. When you select an index query range, however, you must select the cell level or NodeB level. Select the query range of the traffic measurement data. All counters of a NodeB exist in NodeB Measurement and Cell Measurement as shown in Figure 4-48. The measurement object of the NodeB-level counters is NodeB or Iub; the measurement object of the cell-level counters is cell.

Figure 4-48 Selecting a proper counter query range

2007-12-13

All rights reserved

Page155 , Total220


For the NodeB-level traffic measurement, select NodeB, as shown in Figure 4-49.

Figure 4-49 Selecting Node-level traffic measurement Select the NodeB to be queried.

Figure 4-50 Selecting the NodeB to be queried 2007-12-13

All rights reserved

Page156 , Total220


If you want to query the local-cell-level traffic measurement, select Cell Measurement and traffic measurement counters of NodeB, as shown in Figure 4-51.

Figure 4-51 Selecting cell-level traffic measurement The other items, for example, time and query object, are consistent with those for RNC traffic measurement query. For details, refer to the Nastar Operation Guide. The query results are shown in Figure 4-52.

Figure 4-52 NodeB traffic measurement query result

2007-12-13

All rights reserved

Page157 , Total220


4.8.3 Querying Related Alarms on the M2000 On the M2000, you can query the alarms of all NodeBs and extract the alarm data. For details on the related operations, see "Querying Related Alarms on the M2000". On the M2000, you can set different query conditions to query the current fault alarms, event alarms, history alarms, and screened alarms. You can also configure the common query conditions in an alarm query template to facilitate alarm query.

4.8.4 Querying the Current Fault Alarms By setting multiple query conditions, you can quickly find the current fault alarms. 1)

Choose Monitor > Query > Current Fault Alarms or click the shortcut icon in the toolbar.

2)

In the Alarm Browse and Query Statistics window, click the Current Fault Alarm Query tab and set the alarm query conditions.

3)

Click Query. The query results are displayed in the result pane under the tab.

l

Click Save to save the results in a file. The file can be in the *.txt, *.html, or *.csv format.

l

Click Print to print the query results.

4)

Right-click an alarm and choose Detailed Information or double-click an alarm in the browse window. From the displayed dialog box, you can obtain the relevant alarm, such as related alarms and alarm level redefinition.

5)

To open different Current Fault Alarm Query tabs, repeat Step 1, Step 2, and Step 3 for each alarm query

l

The M2000 automatically names the opened tabs as Current Fault Alarm Query 1, Current Fault Alarm Query 2, and Current Fault Alarm Query 3 in sequence.

l

The maximum number of Browse Alarms tabs, Query Alarms tabs, and Manual Statistics of Alarms tabs that can be opened in the Alarm Browse and Query Statistics window is nine.

2007-12-13

All rights reserved

Page158 , Total220


5 OM at Core Network Side You can install MSC (MSOFTX3000) OM software on clients in equipment room by default, for tracing MSC subscribers.

5.1 Tracing Subscribers at Core Network Side To trace subscribers at core network side, perform the following steps: 1)

Start MSOFTX3000, and enter OM System

2)

Type the user name and password Equipment room operators manage and distribute user names and passwords uniformly, so you must follows related rules in equipment room.

Figure 5-1 Tracing MSOFTX3000 call 3)

Click Management icon to switch to System Navigator interface

Click Trace Management > User Trace Task > User Interface. A User Trace interfac e appears, and you can configure on the interface. In User Input drop-down list, you have following choices:

2007-12-13

All rights reserved

Page159 , Total220

WCDMA OMC Operation Guide Internal Open To… Trace subscribers in local network Trace subscribers in local network Trace subscribers in other network

4)

Select… IMSI MSISDN PSTN

Then… Type IMSI number of the subscriber, perform related calls, and trace at interfaces Type subscriber MS number, perform related calls, and trace at interfaces Type subscriber MS number or fixed phone number, perform related calls, and trace messages between the local network and other networks at interfaces (seldom used).

Select one or more interfaces in Combination option, and click Auto Save to File to save result as a file. Select all for ordinary users.

5.2 Extracting Bills 5.2.1 Viewing Bills To view bills, perform the following steps: 1)

Start iGWB Client software

2)

Type the subscriber name and password Equipment room operators manage and distribute user names and passwords uniformly, so you must follow related rules. Figure 5-2 shows viewing bills in iGWB Client software.

Figure 5-2 Viewing bills in iGWB Client software 3)

Click Final Bill > Normal, locate the data for generating the bill, and double click the date All bills imported on the day are displayed in the right window. For example, if you view bill for 21 Feb, 2005, as shown in Figure 5-2, bills imported by hours are displayed on the right window.

2007-12-13

All rights reserved

Page160 , Total220


I. Viewing Bill of a Period You can view the bill of a period as below: 1)

Select a bill file in the right window as shown in Figure 5-3

2)

Double-click the file to view the bill

Figure 5-3 Viewing the bill of a period II. Viewing Bills According to Calling or Called Number To view bills according to calling or called number, perform the following steps: 1)

Right click on a file in the right window.

2)

Select Bill Query in the displayed dialog box as shown in Figure 5-4.

2007-12-13

All rights reserved

Page161 , Total220


Figure 5-4 Viewing bills according to calling or called number You can query bills according to calling or called number. l Type calling number to be queried in CallingNumber text box, and click OK. The bill for the calling number is displayed. l Type called number to be queried in CalledNumber text box, and click OK. The bill for the called number is displayed.

5.2.2 Extracting Bills The system saves bills automatically. Extract bills on the iGWB server. The default directory for saving bills is E:\backsave\second\x3km\normal. You can extract and view bills as required.

6 Customized Querying Alarm Information Excessive alarm information is in BSC6800 Operation & Maintenance System, so locating the needed alarm is difficult. You need check work state of all cells in the network, if states of some cells are abnormal, then you check alarm information about the NodeB related to the cells. By doing this, you can be more efficient.

6.1 Querying Abnormal Cells To query abnormal cells, perform the following steps: 1)

Start BSC6800 OM system

2)

Execute DSP CELL command to query abnormal cells under the RNC

2007-12-13

All rights reserved

Page162 , Total220


3)

Save cell states as a log file

4)

Import cell states from the log file to an Excel table. You edit and process the data in the Excel table for easier querying. Figure 6-1 shows importing cells states to an Excel table.

Figure 6-1 Importing cell states to an Excel table From Figure 6-1, five abnormal states of cell include: Cell state Cell is being blocked Cell is not active Cell is not setup Cell is setup and enabled Cell is setup and but disabled

Meaning The cell is being blocked artificially. The cell is not activated artificially Data is loaded. The cell is not set up, but after setup, the cell is normal The cell is set up The cell is set up and enabled The cell is set up but disabled

Whether to query alarm No No No Yes No Yes

6.2 Querying Alarms on BTSs and Cells in NodeB OM System To query alarms on BTSs and cell in NodeB OM system, perform the following steps: 1)

If the state of a cell is abnormal (detailed in 6.1 ), record the name of NodeB related to the cell

2)

Start the NodeB OM system, and log in to the NodeB

3)

Check the current and historical alarm information of the cell 4.6 details querying alarms of NodeB.

2007-12-13

All rights reserved

Page163 , Total220


6.3 Querying Alarms in M2000 You can query alarms of all NodeB and extract alarm data, detailed in 3.13 .

6.3.1 Querying Event Alarms By setting different query conditions, you can quickly find the event alarms you are concerned about. in the

1)

Choose Monitor > Query > Event Alarms or click the shortcut icon toolbar.

2)

In the Alarm Browse and Query Statistics window, click the Event Alarm Query tab and set the alarm query conditions.

3)


l


l


4)

Right-click an alarm and choose Detailed Information or double-click an alarm in the browse window.

5)

From the displayed dialog box, you can obtain the relevant alarm information, such as related alarms and alarm level redefinition.

6)

To open different Event Alarm Query tabs, repeat Step 1.

l

The M2000 automatically names the opened tabs as Event Alarm Query 1, Event Alarm Query 2, and Event Alarm Query 3 in sequence.

l


6.3.2 Querying History Fault Alarms By setting different query conditions, you can quickly find the history fault alarms you are concerned about. 1)

Choose Monitor > Query > History Fault Alarms.

2)

In the Alarm Browse and Query Statistics window, click the History Fault Alarm Query tab and set the alarm query conditions.

3)


l


l


4) To open different History Fault Alarm Query tabs, repeat Step 1. 2007-12-13 All rights reserved Page164 , Total220


l

The M2000 automatically names the opened tabs as History Fault Alarm Query 1, History Fault Alarm Query 2, and History Fault Alarm Query 3 in sequence.

l


5)


From the displayed dialog box, you can obtain the relevant alarm information, such as related alarms and alarm level redefinition.

6.3.3 Querying Screened Alarms By setting different query conditions, you can quickly find the screened alarms you are concerned about. 1)

Choose Monitor > Query > Screened Alarms.

2)

In the Alarm Browse and Query Statistics window, click the Screened Alarm Query tab and set the alarm query conditions.

3)


l


l


4)


From the displayed dialog box, you can obtain the relevant alarm information, such as related alarms and alarm level redefinition. 5)

To open different Screened Alarm Query tabs, repeat Step 1.

l

The M2000 automatically names the opened tabs as Screened Alarm Query 1, Screened Alarm Query 2, and Screened Alarm Query 3 in sequence.

l


6.3.4 Setting an Alarm Query Template You can save the common alarm query conditions in an alarm query template. When the same query conditions are used, you can use the template to query alarms, without the necessity of setting query conditions. l

The number of templates that can be automatically loaded must not exceed five.

l

Click or in the Alarm Browse and Query Statistics window to display or hide the template tree.

2007-12-13

All rights reserved

Page165 , Total220


In the template tree, the default icon for a template is , the icon for the default , and the icon for an automatically loaded template is .When a template is template is both the default template and the automatically loaded template, the icon is .

1)

Choose Monitor > Query. Select the type of alarms, and set the alarm query conditions in the Alarm Browse and Query Statistics window.

2)

Click Template and select Save the current conditions as a template.

3)

In the Please enter a template name dialog box, enter the template name. You can determine whether to set the current template to an automatically loaded template or the default template according to the requirements.

4)

Click OK.

2007-12-13

All rights reserved

Page166 , Total220


7 Routine Tasks in Equipment Room To cooperate with RNP&O engineers to obtain network data and to know the network operation state, equipment room operators must collect routine data, including: l l l l l l l

CHR CFGMML PerfFile CellStatus Traffic measurement Single subscriber tracing Alarm information

PerfFile and RTWP are obtainable only in equipment room. CFGMML is obtainable through FTP, detailed in 2.11.1 .

7.1 Extracting CFGMML System Files You can know related parameters configured on RNC through CFGMML system files in time. l l l l

Each RNC system imports a CFGMML system file at 2:00 a.m. everyday. The file is saved and extracted as detailed in 2.11.1 . It is about 10 Mbit. It is about several hundred kbit after compression, easy to be sent by Email.

7.2 Extracting CHR Equipment room operators must extract CHR files everyday, and send the files to related engineers in the project team. For extraction method, see 0.

7.3 Extracting Traffic Measurement Data Files The RNC saves traffic measurement data periodically. The data is for analyzing traffic measurement data in Nastar software. Extract all traffic measurement data of the previous day as a routine task in equipment room. The file for one day is about 32 Mbit, too large to send by Email. Different project teams have different rules on how to obtain traffic measurement files in large size. For example, a project team downloads traffic measurement files online through a server in equipment room. For details, see 2.11.3 .

7.4 Querying Cell States Query state of all cells under RNC by executing DSP CELL command. 2007-12-13 All rights reserved Page167 , Total220


If you need query state of multiple cells, you must query the state respectively. During network optimization, regional engineers must pay attention to cell states in their areas. Cell state tables are sent to all in the project team. For details, see 6.1 .

7.5 Collecting and Extracting RTWP Data Trace RTWP of a new NodeB to view the interference around the NodeB. Trace RTWP to identify problems like call drop due to uplink interference in cells during network optimization. Start RTWP test, convert data, and send result to related engineers. For details, see 4.5 . In RNC1.5, to collect and extract RTWP data, perform the following steps: 1)

Start RTWP abnormal record by executing STR RTWPRTTST on NodeB LMT

2)

Start FTP server of the target computer

3)

In M2000 system, on the MML Command window, execute MML commands, such as ULD FILE: DSTF="c:/bin/RtwpLog_NodeBxxx", FLAG=RTWPLOG, IP=" 10.161.209.251", USR="FTP authorized user name", PWD="FTP password", CF= UNCOMPRESSED, [ SD=2005&11&16, ST=15&30&50,ED=2005&11&16, ET=15&40&50]The file is transferred to c:/bin directory, and named RtwpLog_ NodeBxxx.

4)

In the import interface of Nastar, select to import RTWP file to the new project.

7.6 Collecting Traffic Measurement Data Collecting and feeding back traffic measurement data satisfy customers with solving problems by Huawei. Determine the time for creating traffic measurement tasks and extracting data according to different networks and projects. For details, see 错误！未找到引用源。.

7.7 Tracing Subscribers If you need tracing single subscriber everyday during network optimization, list the tracing as a routine task in equipment room. For details, see 2.2 .

7.8 Extracting Alarm Information RNP&O engineers must pay attention to alarm information of the system. For extracting alarm information, see 3.13 and 4.6 . 2007-12-13

All rights reserved

Page168 , Total220


8 Parameter Comparison This section describes the parameter script acquisition and specific parameter comparison method in detail, and presents the concerns in network planning during parameter comparison. Parameter comparison involves two parts: RNC parameter comparison implemented by the Nastar R2 and NodeB parameter comparison implemented by the CME. For details on the NodeB parameter comparison implemented by the CME, refer to the documents related to the CME. The RNC parameter comparison implemented by the Nastar is still in the planning stage.

8.1 RNC parameter Acquisition Briefly, the RNC parameter comparison is divided into three steps: 1)

Take a certain RNC in the network as a reference RNC to compare the product baseline and analyze the differences between the existing network parameters and the product baseline.

2)

Take a cell from the reference RNC as a reference cell to compare it with other cells and ensure that all cell-level parameters in the reference RNC are consistent.

3)

Compare other RNCs with the reference RNC. The RNC parameters can be directly compared. The cell-level parameters should be compared with those of the reference cell in the reference RNC to ensure that the parameter configurations in the whole network are consistent.

8.1.1 Method of obtaining the baseline script The RNC baseline script can be obtained from the data package of the RNC upgrade guide at http://support.huawei.com. Usually, the data package contains the file name of the baseline script. For example, the RNC baseline script is contained in the last page of 08-Appendix1-5 Description of the Modification to BSC6810 V200R009C01B061 Parameters and External MML Commands.doc. The figure below shows how to obtain a document containing the baseline script from the website http://support.huawei.com.

2007-12-13

All rights reserved

Page169 , Total220


Figure 8-1 Obtaining the RNC baseline script from the website http://support.huawei.com

The RNC version is taken an example to illustrate how to obtain the RNC baseline script from the website http://support.huawei.com. No product baseline is available for the versions earlier than V18071 on the website. A product baseline is released for related versions later than V18081 on the website. If a project requires the baseline script of a version earlier than V18071, contact the regional owner for assistance.

8.1.2 Method of Obtaining the RNC MML Script of the existing network For details, refer to Generation and Export of a GFGMML File.

If an M2000 is configured in the network, you can obtain the MML scripts in batches through the M2000 in the following manner: The MML script in the recent period (this period varies with projects) exists on the M2000, usually in the /export/home/sysm/Nastar/RNCXXX/CFGMML directory. After logging in to the VPN, you can log in to the M2000 through the FTP Cute software and download the MML script. If the system automatically deletes the required MML script because its storage duration exceeds the time limit, you can telnet the BAM to obtain the script. Data is usually saved on the BAM for more than seven days (this period may be different, depending on the actual condition). The figure below shows the parameter comparison process.

2007-12-13

All rights reserved

Page170 , Total220


Figure 8-2 Parameter comparison process

8.2 NodeB parameter acquisition In the version later than RAN6.0 (corresponding to V18), the scheduling function of the HSPA is set on the NodeB. The settings mainly involve Mac-hs and Mac-e parameters of the HSDPA. The NodeB parameters greatly affect the radio network performance. You must therefore, pay attention to these parameters during network planning. As the network scale becomes large, NodeB parameters also become more important. How to effectively compare NodeB parameters is a problem we face. The Nastar version implemented NodeB parameter comparison in August 2008. To this end, the network planning department developed a NodeB parameter comparison tool that implements the NodeB configuration parameter comparison function. This function is used to compare NodeB configuration parameter scripts.

8.2.1 Method of Obtaining The Baseline Script 1)

Export the NodeB baseline XML script through the CME.

A new CME version is released together with a new NodeB version. The new CME version contains the default parameter configuration template of the NodeB. You can configure the 2007-12-13 All rights reserved Page171 , Total220


corresponding parameters in the CME and select the corresponding NodeB parameter configuration template to export the NodeB baseline XML script. For details on the specific operations, see Appendix 13 Method of Obtaining the NodeB Baseline Through the CME. 2)

Obtain the NodeB baseline script from the website http://support.huawei.com.

Since the version V18063, a NodeB parameter configuration baseline script is released together with a new NodeB version. You can obtain the NodeB baseline script from the website http://support.huawei.com. The baseline is presented in the Excel format. For example, a file named WCDMA NodeB Release Notes (DBS3800 V100R008C01B063). doc is obtained from the website, as shown in the figure below.

Figure 8-3 Obtaining a product baseline from the website at http://support.huawei.com

8.2.2 Acquisition of XML script of NodeBs on the existing network You can obtain the parameter configuration scripts of the other Nodes in batches through the M2000 in the following manner: 1)

Select multiple NodeBs on the M2000 and perform an NE data backup operation. After the backup is successful, you can view these files (stored in the M2000 server) in the backup file list.

2)

On the backup interface, select the required file list and click Download to Client. The local client can obtain the XML files of NodeBs in batches.

The figure below shows the detailed operation method.

2007-12-13

All rights reserved

Page172 , Total220


Figure 8-4 Obtaining NodeB parameter configuration scripts in batches through the M2000

8.3 Installation of Relevant Programs (Software) 8.3.1 Installation of the Nastar R2 Program Currently, the Nastar R2 is formally released on the website http://support.huawei.com A license is, however, required for the application of the Nastar R2.

8.3.2 Installation of the Relevant Programs The Nastar R2 requires the support of two types of software, namely, .NET Framework2.0 and SQL Server2005. Install the SQL Server2005 server version if the Nastar R2 is a server version; install the SQL Server2005 Express version if the Nastar R2 is a stand-alone version. The following takes the stand-alone version as an example to describe the software installation. Install .NET Framework2.0 and SQL Server2005 Express in sequence.

2007-12-13

All rights reserved

Page173 , Total220


1)

Install NET Framework2.0. For details about the installation method, see Appendix 6 .NET Framework2.0 Program Installation Method

2)

Install the SQL Server2005 Express. For details about the installation method, see Appendix 7 SQL Server2005 Express Program Installation Method.

8.3.3 Method of Logging in to the Server Through the Nastar R2 After installing the SQL Server2005 Express, check the running of the SQL Server2005 Express. Choose Start -> All Programs -> Microsoft SQL Server 2005 -> Configuration Tools -> SQL Server Configuration Manager to open the SQL server configuration manager. Ensure that the SQL server and the SQL server browser work normally, as shown in the figure below. If the start mode is set to Automatic, the system automatically runs the SQL Server2005 Express at next boot.

Figure 8-5 SQL server configuration manager Open the login interface of the Nastar R2, as shown in the figure below.

Figure 8-6 Login interface of the Nastar R2 By default, the username is sa and the login password is the one entered when the SQL Server2005 Express is installed. Note: If you select Mixed Mode during the 2007-12-13

All rights reserved

Page174 , Total220


installation of the SQL Server2005 Express, the program prompts for a password. This password is only the login password. You should pay special attention to the options of the SQL Server2005 Express during the installation, as shown in the figure below.

Figure 8-7 Settings for the SQL Server2005 Express installation Selection of the SQL server. If the SQL server is used as the default server in the SQL Server2005Express installation, the server name is SQL Express. If you have changed the server instance, log in to the server as the instance you have installed. The username used to log in to the default SQL server is (local)\SQLExpress. If a server instance is created, the login username is (local)\XXX. Here XXX is the created server instance.

Here the personal domain account can be substituted for (local), but the following cases should be distinguished: If the network is connected through the domain account and the domain account is displayed during the installation of the SQL Server2005 Express, you can use domain account + \ + server instance as the server name to log in to the SQL server. Otherwise, you fail to log in to the SQL server in this mode. It is common to use (local) + \ + server instance as the server name to log in to the SQL server.

8.4 RNC parameter comparison 8.4.1 Comparison with the baseline parameters The comparison with the baseline parameters is used to compare the existing network parameters with the product baseline and find out the differences between the 2007-12-13

All rights reserved

Page175 , Total220


parameter configurations of the existing network and the baseline parameter configuration. The specific operation method is as follows: Open the Nastar and select the Trouble Shooting view and the Compare Configuration with Baseline option.

Figure 8-8 Selection for comparison with the baseline parameters Double-click Compare Configuration with Baseline. The main interface for comparison with the baseline parameters shown in the figure below is displayed.

Figure 8-9 File configuration for comparison with the baseline parameters

The preceding figure shows the following key items: Report Path: Path in which the parameter comparison results are saved. It is set by the user. MML file1: Baseline script. MML file2: MML script of the existing network, compared with the baseline. 2007-12-13

All rights reserved

Page176 , Total220


Compare mode: Option for hierarchical networking. If the hierarchical networking does not apply, set the option to one base cell. Baseline file: Baseline. Base cell ID: Reference cell ID.

8.4.2 Parameter comparison between different cells in one MML script The parameter comparison between different cells in one MML script is used to check the parameter configurations between different cells in one RNC for inconsistency. The reference cell is a specified cell in the existing network. The specific operation method is as follows: Open the Nastar and select the Trouble Shooting view and the Compare Configuration with Baseline option.

Figure 8-10 Parameter comparison between different cells in one MML script Double-click Compare Configuration with Baseline. The main interface for parameter comparison between different cells in one MML script is displayed. The operation method is similar to that of the baseline parameter comparison. You can import only one MML script, MML file1 or MML file2, consider it as a baseline file, and set Base Cell ID to the ID of the reference cell, as shown in the figure below.

2007-12-13

All rights reserved

Page177 , Total220


Figure 8-11 File configuration for parameter comparison between different cells in one MML script

8.4.3 (RNC-level and cell-level) parameter comparison between different RNCs The parameter comparison between different RNCs is used to compare the parameter scripts between two RNCs in the existing network and check the parameter configurations in the whole network for inconsistency. The specific operation method is as follows: Open the Nastar and select the Trouble Shooting view and the Compare Configuration with Baseline option.

Figure 8-12 (RNC-level and cell-level) parameter comparison between different RNCs Double-click Compare Configurations with Baseline. The main interface for parameter comparison between different RNCs is displayed. Here, the MML script of 2007-12-13

All rights reserved

Page178 , Total220


the reference RNC is imported to the Nastar as the baseline MML script, as shown in the figure below.

Figure 8-13 Parameter comparison between different RNCs The preceding figure shows a case of hierarchical networking. In this case, the parameters of R99 cells and H cells at the radio layer differ greatly. Therefore, R99 cells and H cells should be distinguished during parameter comparison.

8.4.4 (RNC-Level and Cell-Level) Parameter Comparison Between different versions of an RNC This function is applied to the scenario in which a product version is upgraded. It is used to check the parameter change before and after a product version upgrade, without starting the parameter comparison process. This function is implemented through the MML File Compare function. The specific operation method is as follows: Open the Nastar and select the Trouble Shooting view and the MML File Compare option.

2007-12-13

All rights reserved

Page179 , Total220


Figure 8-14 Parameter comparison between different versions of an RNC Double-click MML File Compare. The main interface for parameter comparison between different versions of an RNC is displayed, as shown in the figure below.

Figure 8-15 Parameter configuration for parameter comparison between different versions of an RNC

If the MML script to be compared is imported to the Nastar through TransData, you can select Project for the MML file from option; if the MML script to be compared needs to be imported on site, you can select Disk for the MML file from option. For the Cell option, you can select the required cells from the cells in the MML script to be compared to improve the comparison efficiency. For the Command option, you can select certain parameter commands in the configuration file to improve the comparison efficiency. 2007-12-13

All rights reserved

Page180 , Total220


You can select the cells and commands to be compared from the Cell and Command options. You must configure these options in the XML script (namely, RNC parameter configuration file) in advance. For details, see Appendix 2 Configuration File for the Nastar Parameter Comparison Tool.

2007-12-13

All rights reserved

Page181 , Total220


9 Appendix 9.1 CR Process for Modifying Parameters RNP&O engineers must not randomly modify parameters related to the system in equipment room. In a commercial network, to implement suggestions on modifying parameters, you must follow related flow to avoid casualties in case of inconsiderate situations. Each project of WCDMA network must have management rules and process, so equipment OM operators and RNO engineers must follow them together with equipment room operators. Wherein, modifying RNP parameters must be approved by project managers. A suggested process for modifying parameters is as below: 1)

RNO engineers propose a request for modifying parameters, and sent it to project managers for approval

2)

Project managers approve it, and then send CR to equipment room operators

3)

Equipment room operators back up scripts, modify parameters, execute related commands, record and update record list for modifying parameters. They check the result for executing commands, and feed back the result to RNO engineers and related engineers. If equipment room operators fail to execute some MML commands, the RNO engineers must analyze the result.

4)

If you modify parameters temporarily in a test project, you must restore the parameters after test.

5)

To determine the time for modifying parameters, you must pay attention to parameter importance, parameter level, and parameter impact on the system You must select the right time to avoid artificial accidents. You must modify the parameters at midnight, and otherwise modifying them will have great impact on the system. You might use customized script, detailed in 2.10 . Huawei forbids using customized scripts, so you must modify parameters during midnight.

9.2 Division of Responsibilities for Executing BSC6800 MML Commands The attachment RNC MML Command Responsibility Division clarifies the owner for modifying parameters of RNC MML commands. It also provides the MML commands corresponding to the parameters that concern on-site RNO engineers. The following operations must be approved by RNP technical support engineers before modification: l l l

Modifying parameters of level 2 and 3 Modifying parameters of RNC-level Executing commands related to adding, removing, and deactivating object (part of the MML commands marked in red have great impact on RNCs and cells)

2007-12-13

All rights reserved

Page182 , Total220


Commands related to adding, removing, and deactivating object must be executed under cooperation of on-site technical support engineers. Adding and removing cells must be operated by on-site technical support engineers.

RNC MML Command Responsibility Divisioni V1.0 (simply issued version of 0831 revision)

9.3 List of BSC6800 MML Batch Processing Commands The attachment below lists BSC6800 MML batch processing commands and 1–2 samples. You can query MML commands of RNC by search function in BSC6800 OM system.

List of BSC6800 MML Batch Processing Commands

9.4 Supplementation to Method for Starting DL Simulated Load At early stage of network, there is no subscriber or few subscribers.This supplementation simulates actual network by simulating uplink and downlink load. The value of downlink load is relative to total power and the value of downlink load is relative to noise increment. A popular method for starting downlink load in the industry is starting simulated load by OCNS. For detailed methods, see 3.7 and 3.9 .

9.4.1 Starting Downlink Simulated Load I. Introduction to OCNS The protocol 25.101 defines OCNS as follow: OCNS is the necessary power so that total transmit power spectral density of NodeB (lor) adds to one.

& Note: For dynamic power correction required to compensate for the presence of transient channels, e.g. control channels, a subset of the DPCH channels may be used.

Set up a fictitious load under NodeB so that the transmit power of the local cell reaches 100%. Namely, the total power of tested link and fake line is the downlink total power of the cell. If the traffic measurement of tested link is adjustable (the downlink power control is enabled), then the transmit power of other links must be adjusted so that the total power of all links is the total power of the cell. The following section provides the major parameters of 16 fake links when the power of tested link is fixed in the protocol. 2007-12-13 All rights reserved Page183 , Total220


II. DPCH Spreading Code, Timing Offsets, and Relative Level Settings for OCNS Signal Table 9-1 lists the DPCH spreading code, timing offsets, and relative level settings for OCNS signal. Table 9-1 DPCH spreading code, timing offsets, and relative level settings for OCNS signal Channelization code 2 11 17 23 31 38 47 55 62 69 78 85 94 125 113 119

Timing offset (x256Tchip) 86 134 52 45 143 112 59 23 1 88 30 18 30 61 128 143

Level setting (dB) –1 –3 –3 –5 –2 –4 –8 –7 –4 –6 –5 –9 –10 –8 –6 0

9.5 Description of Collecting Data for Tracing Calls In RNO tests, engineers collect data for tracing calls on RNC LMT or M2000, including tracing signaling messages and monitoring realtime state. During calls, engineers collect downlink radio link performance data and signaling by using front DT software. Collecting data for tracing calls helps analyze coverage, capacity, traffic measurement indexes, radio performance of the network.

9.5.1 Tracing Signaling Messages Signaling messages to be traced include the following messages: l l l l

Subscriber signaling messages Cell signaling messages Signaling messages at standard interfaces Signaling messages in protocol of transport network layer

Before tracing signaling, you are recommended to adjust the BAM time and time on the test computer. I. Tracing Subscriber Signaling Messages Subscriber signaling messages include the following messages: l l l

1)

Single subscriber signaling messages at standard interface Single subscriber signaling messages at subscriber and signaling plane IOS messages Tracing single subscriber signaling messages at standard interfaces. The interfaces include lu, lur, lub, Uu interface. After typing the UE identity (IMSI, TMSI,

2007-12-13

All rights reserved

Page184 , Total220


P-TMSI, or IMEI) and selecting the standard interface, you can trace the single subscriber signaling messages at standard interfaces. You can obtain UE IMSI by consulting the customer service center of the carrier or querying it from HLR. In addition, you can confirm IMSI by RANAP COMMON ID message. TMSI and P-TMSI change after TMSI relocation. If you need trace them, you can obtain them from RRC CONN REQUEST message. After UE reset and expiration of TMSI reconfiguration timer, TMSI or P-TMSI change. Therefore you must retrace them. You can obtain IMEI from UE vendor. You can trace emergency subscriber without SIM module by it. In case of RAB assignment failure, RAB release failure, paging failure, lu release failure, safety mode control failure, initial UE message failure, and transition failure, you can locate the obstacle and solve the problem by analyzing messages at lu interface. In case of radio link setup failure, radio link adding failure, radio link removal, common transmission channel resource release failure, downlink power control failure, and paging failure, you can locate the obstacle and solve the problem by analyzing messages at lub or lur interface. In case of RRC connection setup failure, RB setup failure, PCH reallocation failure, and cell update failure, you can locate the obstacle and solve the problem by analyzing messages at Uu interface. The lu interface messages (RANAP protocol messages) and lur interface messages (RANSAP protocol message) of the task UE tracing (standard interface messages) are connection-oriented messages, not non-connection messages. The lub interface messages (NBAP protocol message) of the task UE tracing (standard interface messages) are dedicated NBAP messages, but not common NBAP messages. If you trace single subscriber by using IMSI, and the RRC CONNECT REQUEST message includes the consistent IMSI when UE is accessing the network, you can trace the single subscriber by tracing messages after RRC CONN REQUEST message. If you trace single subscriber by using IMSI, the RANAP COMMON ID message, but not RRC CONNECT REQUEST, include the IMSI when UE is accessing the network, you can trace the single subscriber by tracing messages after RANAP COMMON ID message. The messages before RANAP COMMON ID message are dropped. The index USER on the traced result displayed in the UE Tracing (Standard Interface Messages) task view window means differently to different interfaces. For lu and lur interface messages, USER is DPC ID. For lub interface messages, USER is NodeB ID. For Uu interface messages, USER is invalid (oxFFFFFFFF). On the message view window, right click. In the displayed menu, you can select Board Response List, and can view all WSPU information of unreceived response messages and received response messages. 2)

Tracing single subscriber signaling messages at subscriber and signaling plane The messages are at signaling and user plane at standard interfaces related to specific tracing event during calling by specified UE. You can type the UE identity (IMSI, TMSI, P-TMSI, or IMEI) and select the specific events. Tracing this type of messages has something in common with the task UE tracing (standard interface messages): the messages to be traced are related and triggered in tracing specified UE in calling. Yet they are different. The task UE tracing (standard interface messages) involves signaling messages at four standard interfaces. The task UE tracing (subscriber and signaling plane) involves standard messages at signaling plane, self-defined information at signaling plane, and reported data at user plane. It divides the traced messages according to report information content. Namely, you can select different traced messages by selecting different events. The task UE tracing (subscriber and signaling plane) involves much information, which impacts system operation. Therefore, reduce the traced events as possible. The RNC can trace 6 UEs at most. If the task UE tracing (standard interface messages) can meet the requirements, use this task as possible.

2007-12-13

All rights reserved

Page185 , Total220


3)

IOS tracing. IOS tracing is tracing all subscribers meeting default conditions. By IOS tracing, you continuously traced the calls of specified number (the number is specified at beginning of the task) which access the network in specified cell. The content to be traced is the messages generated during calling. Select the types of traced messages by selecting traced events. Only the subscribers access the cell by RRC or migrate (including inter-system handover) to the cell. Stopping tracing is triggered when RRC is released or the subscribers migrate out of the cell. Type the number of continuous calls to be traced, sampling standard, and tracing time. The sampling standard is defined according to RAB parameter restriction. The RAB parameter restriction is valid only when tracing a new call starts. If a call meets the sampling standard, the call keeps being traced despite that the RAB parameters are modified after starting the call. If the RAB parameters does not meet sampling standard at the beginning but meet sampling standard after modification, the call will not be traced. The task IOS tracing involves much information, which impacts system operation. The index of the upper limit of number of calls traced simultaneously must be smaller than 6. Tracing all events at a time is not recommended. In addition, use the task as less frequently as possible.

II. Tracing Cell Signaling Messages Tracing cell signaling messages is tracing NBAP common messages or USER_VOLUMN events in specified cells. The USER_VOLUMN events include self-defined messages, reflecting statistics information of UE in the cell. Specify the cell by typing cell ID. Select the type of messages to be traced by selecting traced events. The cells to be traced must be activated first. The task cell tracing involves much information, which impacts system operation. The system supports tracing 32 cells at most simultaneously. If lub interface tracing meets requirements, use it as possible. III. Tracing Signaling Messages at Standard Interfaces The interfaces include Uu, lub, lur, and lu interface. When the subscribers are in a large number, the signaling to be traced at standard interfaces is much. This impacts system operation. Solve the problem by using testability log and tracing single subscriber. 1)

Tracing Uu interface messages. This traces all or partial signaling messages at Uu interface in the selected cell. The USER displayed in the traced result on the message view window is the cell that tr ansmits or receives the message.

2)

Tracing lub interface messages. This traces standard messages at lub interface, including NBAP dedicated messages and common messages. The USER displayed in the traced result on the task message view window is the opposite NodeB ID. The NodeB ID is queried by executing LST NODEB command. The NCP and CCP port number are queried by executing LST IUBP command.

3)

Tracing lur interface messages. This traces standard messages at lur interface, including connection-oriented and non-connection messages. The USER in the traced result displayed task message view window is the DPC ID of opposite RNC. Query DPC ID by executing LST N7DPC command.

4)

Tracing lu interface messages This traces standard messages at lu interface, including connection-oriented and non-connection messages. The USER in the traced result displayed task message

2007-12-13

All rights reserved

Page186 , Total220


view window is the DPC ID of opposite CN. Query DPC ID by executing LST N7DPC command. IV. Signaling Messages in Protocol of Transport Network Layer The messages include QAAL2, SCCP, MTP3B, and SAAL protocol messages. Tracing these messages helps analyze failure at interface link. In case of RAB assignment failure, RRC setup failure, and cell setup failure, you can locate the obstacle and solve the problem by tracing QAAL2 protocol messages. When the CN side cannot receive direct transmission messages and the RNC cannot receive paging messages sent by CN: l l l

If the target signaling point is reachable, you can locate the obstacle and solve the problem by tracing SCCP protocol messages. If the target signaling point is unreachable or MTP3B link is unavailable, you can locate the obstacle and solve the problem by tracing MTP3B protocol messages. If the SAAL link is unavailable, you can locate the obstacle and solve the problem by tracing SAAL protocol messages.

9.5.2 Monitoring Realtime State Monitoring realtime state involves the following indexes: l l l l

CPU utilization Connection performance Cell performance Link performance

Monitor the states of current system equipment and service operation by using figures and data. During monitoring, analyze the abnormalities to help maintain the equipment and solve problems. The following sections describe monitoring connection performance and monitoring cell performance. I. Monitoring Connection Performance By monitoring connection performance, you can obtain the connection state of physical link during calling. A connection performance monitoring task monitors one or more indexes of one or more UEs. Usually monitoring connection of one UE simultaneously is recommended based on consideration of system cost. Over high utilization of the system triggers flow control. Upon flow control, the system stops interior tasks and forbidding starting interior tasks again. 1)

Cell SIR and RSCP By monitoring it, you can obtain the DCH connection and realtime data of active set cells of the current connection without reporting data of other cells. Therefore the monitored result reflects the variation of active sets. The upper limit that you can report is 6. If the monitored connection is released or migrates from DCH to CCH, the task stops. If the monitored connection returns from CCH to DCH, the task restarts. The monitored data is reported at Uu interface periodically.

2)

AMR mode In AMR mode, you can obtain variation of configured rate of subscribers with AMR service.

3)

Measured SIR of uplink radio link set By monitoring it, you can obtain the DCH connection and realtime state of SIR quality of radio link, so the monitored result reflects the variation of radio link active sets. If the monitored connection is released or migrates from DCH to CCH,

2007-12-13

All rights reserved

Page187 , Total220


the task stops. If the monitored connection returns from CCH to DCH, the task restarts. The monitored data is submitted in a NodeB-specific measurement report periodically. 4)

SIR target value of uplink radio link set By monitoring it, you can obtain realtime state of SIR quality target value required by radio link set connected on DCH. It reflects requirements on uplink radio link quality and variation of requirements. The monitored data is reported inside RNC periodically.

5)

Measured SIR error of uplink radio link set By monitoring it, you can obtain realtime state of measured SIR error of radio link set connected on DCH. In addition, you can observe whether the radio link set SIR matches the variation of SIR target value and can evaluate function of uplink inner loop power control. If the measured SIR error of uplink radio link set change s all the time but remains convergent to 0 dB, the uplink inner loop power control is convergent. Otherwise, the uplink inner loop power control is divergent. The monitored data is reported inside RNC periodically.

6)

Uplink transport channel BLER By monitoring it, you can monitor the BLER variation of the signaling transport channel and major service transport channels connected to DCH. It helps analyze uplink radio link quality. If the uplink transport channel BLER increases, the uplink radio link quality declines. Otherwise, the uplink radio link quality increases. If the uplink radio link BLER keeps great, especially with an over great BLER of signaling transport channel, the uplink link quality is over poor. This might cause uplink asynchronization which consequently causes release of entire connection. The monitored data is submitted in a NodeB-specific measurement period report.

7)

Downlink code transmit power By monitoring it, you can obtain the variation of code transmit power of each downlink radio link connected on DCH. It reflects the number variation of radio links involved in the current connection. In addition, it helps analyze downlink power consumption. If the measured downlink code transmit power increases, even approaching the maximum downlink code transmit power configured in signaling messages, the downlink radio link quality declines. The monitored data is submitted in NodeB-specific measurement period report.

8)

UE transmit power By monitoring it, you can obtain the realtime variation of uplink UE transmit power on DCH. It helps analyze uplink radio link quality. If the UE transmit power keeps increasing, even approaching the upper limit to UE capacity, the uplink radio link quality declines. The monitored data is reported at Uu interface periodically.

9)

Uplink PCH BER By monitoring it, you can obtain the realtime variation of uplink physical channel (PCH) BER connected DCH. It helps analyze uplink radio link quality. If the uplink PCH BER increases, the uplink radio link quality declines. Otherwise the uplink radio link quality increases. If the uplink PCH BER keeps high, the uplink quality is poor. This causes uplink asynchronization, which consequently causes release of entire connection. The monitored data is reported inside RNC periodically.

10) Uplink traffic By monitoring it, you can obtain the realtime variation of uplink traffic (cache data amount at UE side) of PS interactive or background services. It helps analyze tra nsmission performance of uplink traffic. If the uplink traffic keeps approximately e 2007-12-13

All rights reserved

Page188 , Total220


qual to cache capacity at UE side, the uplink transmission bandwidth is inadequat e. The monitored data is reported at Uu interface periodically. 11) Downlink traffic By monitoring it, you can obtain the realtime variation of downlink traffic (cache d ata amount at UE side) of PS interactive or background services. It helps analyze transmission performance of downlink traffic. If the downlink traffic keeps approxi mately equal to cache capacity at UE side, the downlink transmission bandwidth i s inadequate. The monitored data is reported inside RNC periodically. 12) Uplink throughput and bandwidth By monitoring it, you can obtain the realtime rate variation of uplink data access l ayer and non-access layer of PS interactive and background services. It helps an alyze dynamic channel configuration function and rate variation feature of service sou rce. T h e m oni t or ed dat a i s re po rt e d i n si de R NC peri o di cal l y. While verifying functions of dynamic channel configuration, observe the variation of uplink throughput and bandwidth. If the uplink throughput increases, the uplink bandwidth increases accordingly. If the uplink throughput decreases to 0, the upli nk bandwidth decreases to the minimum rate accordingly, the dynamic channel fu nctions normally. If the dynamic channel configuration function is disabled, obtain the rate feature of uplink service source by observing variation of uplink throughp ut. 13) Downlink throughput and bandwidth By monitoring it, you can obtain the realtime rate variation of downlink data acces s layer and non-access layer of PS interactive and background services. It helps analyze dynamic channel configuration function and rate variation feature of servi ce source. The monitored data is reported inside RNC periodically. While verifying functions of dynamic channel configuration, observe the variation of downlink throughput and bandwidth. If the downlink throughput increases, the downlink bandwidth increases accordingly. If the downlink throughput decreases t o 0, the downlink bandwidth decreases to the minimum rate accordingly, the dyna mic channel functions normally. If the dynamic channel configuration function is di sabled, obtain the rate feature of downlink service source by observing variation of downlink throughput. 14) Handover delay By monitoring it, you can monitor the connection on DCH and the period of every handover (intra-RNC, inter-RNC soft handover, intra-frequency hard handover, an d i nt er-f requency hard han dov er) of t he current conn ect i on. For example, the point for UE to report 1A event of joining radio links T1. The poi nt for UE to send the ACTIVE SET UPDATE COMPLETE message is T2. The dif ference between T2 and T1 is the soft handover delay to be added in radio links. The monitoring period is unnecessary upon starting the task. 15) Downlink transport channel BLER By monitoring it, you can obtain the BLER variation of all transport channels conn ected to DCH. It reflects the realtime variation of number of service transport cha nnels. In addition, it helps analyze downlink radio link quality. If the downlink trans port channel BLER increases, the downlink radio link quality declines. Otherwise, the downlink radio link quality increases. The monitored data is submitted in UU-s pecific measurement period report. II. Monitoring Cell Performance By monitoring cell performance, you can obtain the cell performance conditions (such as common measured values and CCH subscribers). Monitoring cell performance 2007-12-13

All rights reserved

Page189 , Total220


increases the data flow between the host device and BAM. Monitoring excessive cells is not recommended and monitoring period must not be over small. Otherwise the system performance is affected. Activate the cells before monitoring. Query activated cells by executing the DSP CELL command. Query parameters of monitored cells by executing the LST CELL command. Over high system utilization triggers flow control, and then the system stops inferior tasks and prohibits starting inferior tasks. 1)

Transmit power of cell PIPICH pilot By monitoring it, you can observe and judge whether the pilot power of a specifie d cell is normal. Query the automatic adjustment range of cell PCPICH pilot powe r by executing LST PCPICH and cell PCPICH.

2)

Received power of cell uplink total bandwidth By monitoring it, you can the uplink load level of a specified cell. The NodeB mea sures and reports the uplink total bandwidth received power. You can perform co mmon measurement on cells to be monitored. Before activation of cell, equipmen t room operators query by executing the LST CELLALGOSWITCH command an d ensure the LDM (load monitoring algorithm) of cell algorithm switch is enabled (modifying the switch by executing the MOD CELLALGOSWITCH command). Aft er activation of cell, the system constructs the common measurement process, wi th the COMMON MEASUREMENT REPORTING message at lu interface. The uplink load factor (the ratio of uplink total bandwidth received power of cell to cell background noise) measures the cell uplink load in admission process. The c ell background noise is a constant (setting it by executing the ADD CELLCAC or MOD CELLCAC command), so the uplink total bandwidth received power of cell decides relative level of cell uplink load.

3)

Transport power of cell downlink carrier By monitoring it, you can obtain the realtime level of cell downlink load. The Node B measures and reports transmit power of cell downlink carrier. You can perform common measurement on the cells to be monitored. Before activation of cell, equ ipment room operators query by executing the LST CELLALGOSWITCH comma nd and ensure the LDM (load monitoring algorithm) of cell algorithm switch is ena bled (modifying the switch by executing the MOD CELLALGOSWITCH comman d). After activation of cell, the system constructs the common measurement proce ss, with the COMMON MEASUREMENT REPORTING message at lu interface. The ratio of downlink carrier transmit power to maximum transmit power of cell m easures cell downlink load in admission process. Set the maximum transmit powe r of cell by executing the ADD CELLSETUP command upon cell setup. After cell setup, modify the maximum transmit power of cell by executing the MOD CELLS ETUP command.

When HSDPA is used, NodeB can monitor cell carrier power and non-HSDPA carrier power at the same time. To do so, you need to enable cell measurement on CELLALG OSWITCH by using the MOD CELLALGOSWITCH: NBMSwitch=HSDPA_MEAS-1 co mmand. 4)

Number of cell CCH subscribers By monitoring it, you can obtain the realtime number of CCH subscribers in the c ell.

5)

Number of cell DCH subscribers By monitoring it, you can obtain the realtime number of DCH subscribers in the c ell.

6)

Node synchronization By monitoring it, you can obtain the time difference between RNC frame number

2007-12-13

All rights reserved

Page190 , Total220


(RFN) and NodeB Frame Number (BFN), as well as the time for completing node synchronization. If the difference changes sharply, the transmission between RNC and NodeB is problematic. 7)

Uplink admission judgment By monitoring it, you can obtain the predicted value of uplink load factor in admis sion judgment and the variation of measured load factor. Therefore, you can mea sure the accuracy of uplink admission load. You can perform common measurem ent on the cells to be monitored. Before activation of cell, equipment room operat ors query by executing the LST CELLALGOSWITCH command and ensure the LDM (load monitoring algorithm) of cell algorithm switch is enabled (modifying the switch by executing the MOD CELLALGOSWITCH command). After activation o f cell, the system constructs the common measurement process, with the COMM ON MEASUREMENT REPORTING m essage at l u i nterf ace. Monitoring uplink admission judgment is effective only when the uplink admission control algorithm switch is set to load prediction algorithm. Configure the switch by executing the MOD CELLALGOSWITCH command. Query the switch state b y executing the LST CELLALGOSWITCH command. The uplink load factor (the ratio of uplink total bandwidth received power of cell to cell background noise) measures the cell uplink load in admission process. Confi gure cell background noise by the ADD CELLCAC or MOD CELLCAC command.

8)

Downlink admission judgment monitoring By monitoring it, you can obtain the predicted value of downlink load factor in ad mission judgment and the variation of measured load factor. Therefore, you can measure the accuracy of downlink admission load. You can perform common me asurement on the cells to be monitored. Before activation of cell, equipment room operators query by executing the LST CELLALGOSWITCH command and ensur e the LDM (load monitoring algorithm) of cell algorithm switch is enabled (modifyi ng the switch by executing the MOD CELLALGOSWITCH command). After activ ation of cell, the system constructs the common measurement process, with the CO MMO N MEASUREMENT REPO RT I NG message at l u i nt erf ace. Monitoring downlink admission judgment is effective only when the downlink admi ssion control algorithm switch is set to load prediction algorithm. Configure the switch by executing the MOD CELLALGOSWITCH command. Query the switch state by ex ecuti ng the LST CELLALGOSWIT CH comm and. The ratio of downlink carrier transmit power to maximum transmit power of cell m easures the cell downlink load in admission control process. The maximum trans mit power of cell is a constant (setting it by executing the ADD CELLSETUP com mand upon cell setup), so the downlink carrier transmit power of cell decides relat ive level of cell downlink load.

9)

Uplink equivalent subscribers By monitoring normalized factor of uplink total services in the specified cell, you c an obtain the variation of uplink equivalent subscribers based on cell subscribers (cell CCH subscribers and cell DCH subscribers). Monitoring uplink equivalent su bscribers is effective only when the uplink admission control algorithm switch is s et to total service normalized factor algorithm (configuring it by executing the MOD CELLALGOSWITCH command and querying it by executing the LST CEL LALGOSWITCH command). During the admission control process using total ser vice normalized factor algorithm, select a service and a rate (12.2k AMR voice ser vice) as a standard service. The normalized factor for a service is the ratio of the system capacity used by the service to that of the standard service. The normaliz ed f actors are different for uplink and downlink of the same service. The normalized factor of cell uplink total service is the sum of all normalized facto

2007-12-13

All rights reserved

Page191 , Total220


rs of each service. It reflects the uplink load level of cell and increases as the cell subscriber increase. 10) Downlink equivalent subscribers By monitoring normalized factor of downlink total services in the specified cell, yo u can obtain the variation of downlink equivalent subscribers based on cell subscr ibers (cell CCH subscribers and cell DCH subscribers). Monitoring downlink equi valent subscribers is effective only when the downlink admission control algorithm switch is set to total service normalized factor algorithm (configuring it by exe cuting the MOD CELLALGOSWITCH command and querying it by executing the LST CELLALGOSWITCH command). During the admission control process usin g total service normalized factor algorithm, select a service and a rate (12.2k AMR voice service) as a standard service. The normalized factor for a service is the ra tio of the system capacity used by the service to that of the standard service. The normalized factors are different for downlink and downlink of the same service. The normalized factor of cell downlink total service is the sum of all normalized fa ctors of each service. It reflects the downlink load level of cell and increases as th e cell subscriber increase. 11) Cell code tree usage By monitoring downlink channel orthogonal variable spreading factor (OVSF) cod e tree, you can obtain the realtime usage of cell downlink channel code. When th e mouse pointer stops on a code table, the system prompts the spreading factor of the code, code number, and state. 12) Minimum power requirements on HS-DSCH channel To minimize the bit rate for HSDPA subscribers, you can reserve part of the powe r for HS-DSCH. You can perform real-time monitoring using this item. 13) Bit rate provided by HS-DSCH This performance varies with subscriber bit rates in real time.

9.5.3 Tracing CDT CDT tracing is similar to CDL tracing. It combines signaling tracing with L2 user plane information. To trace CDT, perform the following steps: Select Service > Trace Management > Interface Trace Task, and then enter the IMSI number of the UE. Because there is a lot to be traced, you should trace fewer than two subscribers on th e same computer. The file is saved at C:\HWLMT\BSC6800V100R005ENG\BSC6800 V100R005ENGC01B068\Trace by default.

2007-12-13

All rights reserved

Page192 , Total220


Figure 9-1 Tracing BSC6800 CDT To view CDT file, you need to perform the following configuration: Configure the RncTestConfig file in C:\HWLMT\adaptor\clientadaptor\BSC6800\BSC 6800V100R006C01B061\style\defaultstyle\locale\zh_CN\rnctest:

& Note: Like RNCv1.5 OM, RNCv1.6 LMT also provides CDRs. Use 0 or 1 to disable or enable this feature.

2007-12-13

All rights reserved

Page193 , Total220


By default, the function of viewing CDT is disabled. To view the information on the user plane, you must change value in the file.

Figure 9-2 CDT messages

& Note: You must back up the RncTestConfig file in advance. When you use Trace viewer, you find that the RncTestConfig file contains all information on both signaling plane and user plane. If you need to view information only on the signaling plane, you do not need to change configuration according to the above-mentioned procedure.

9.5.4 Viewing CHR through Insight Plus For V16C01B082, V17C01B030 and later, Insight Plus is integrated into LMT. After installing RNC LMT, you need to configure the configuration file manually and enable debugging to switch to the interval version. Then you can view the collected CHR file through Insight Plus. To change the configuration file, perform the following steps: 1)

Open the configuration file InsightPlus.ini. By default, this file is saved at $:\HW LMT\adaptor\clientadaptor\BSC6800\BSC6800V100R006C01B082\Insight Plus\chs\data\.

2)

Change the value of VersionType: VersionType=InsightPlus

2007-12-13

All rights reserved

Page194 , Total220


Internal version: [System] HelpFile=InsightPlus.chm VersionType=InsightPlus StaticTree=FALSE HideTreeNumber=FALSE RecordAllLog=FALSE LogNumberPerPage=2000 LogFileTypeList=log, log file| CodeExplainShowSingleLine=FALSE CodeExplainSelectFirstLine=FALSE

3)

Open the Insight tool again. You can view the internal information, such as project tree.

Figure 9-3 Viewing CHR through Insight Plus

9.6 Description of the Configuration File for the Nastar R2 Parameter Comparison Tool 9.6.1 Script configuration for RNC MML parameter comparison Parameter configuration is the key to the MML script comparison function. The parameter configuration, parameters to be compared, and parameter display are an integrity. The parameters that the Nastar compares must be preset in the parameter configuration template. The Nastar does not compare those parameters that are not preset. Only the parameters with different comparison results are displayed. The configuration file directory (add instance description) is WCDMA\TEMPLATE FILES\WCDMA\ConfigurationCommand. There are three XML script files in the 2007-12-13 All rights reserved Page195 , Total220


directory: cmdtype.xml, cmpcmd.xml, and EspecialCommand.xml. The three files are described as follows:

cmdtype.xml The cmdtype.xml file is used for parameter classification. The parameter format is shown in the figure below.

Figure 9-4 Format of classified command parameters You can obtain the required parameter by performing configurations shown in the preceding figure. For example, RNC parameters are divided into air interface parameters and parameters oriented to the transport layer of NodeB. The parameter configuration in the file is used by the R&D personnel for program implementation. Therefore, the network planning personnel do not need to pay special attention.

cmpcmd.xml The cmpcmd.xml file is used for parameter matching. Different commands match different parameters. Therefore, relevant matching parameters must be configured for comparison. Otherwise, the comparison results cannot meet the customer's requirement. The network planning personnel must pay attention to this part of the parameter configuration. The figure below shows the parameter matching format.

2007-12-13

All rights reserved

Page196 , Total220


Figure 9-5 Parameter matching format The parameter configuration items are as follows: l

Command Type distinguishes RNC-level parameters from cell-level parameters.

l

Traffic Type indicates the parameter category. The value is consistent with the classification configuration in the cmdtype.xml file.

l

Name indicates a command.

l

Cfgindex Param indicates the name of a specific parameter.

l

Value is a reserved item and is used for index display. If Value is set to 1, the index is displayed; if Value is set to 0, the index is not displayed.

l

Match indicates whether a baseline parameter is compared.

EspecialCommand.xml The EspecialCommand.xml file is used for the configuration of special command parameters, for example, switch parameters to be analyzed. The figure below shows the parameter format.

Figure 9-6 Configuration format of special command parameters

Network planning concerns 1)

Configuration of neglected items

The indexes of certain RNC-level and cell-level parameters need to be neglected because parameters such as RABINDEX and CELLID are not what network planning personnel are concerned about. There is no point in comparing these parameters. The negligence of these parameters is implemented through parameter configuration. 2007-12-13 All rights reserved Page197 , Total220


Configuration method: If you want to neglect the CELLID parameter, the configuration command is as follows: The item to be neglected is configured in the cmpcmd.xml file. Here, the value 0 of Match indicates that the parameter is not compared; the value 0 of Value indicates that the parameter is not displayed. CELLID is the neglected parameter and is not processed. 2)

Contradiction between parameter matching and parameter mismatching

When the parameters of different RNCs are compared, certain RNC-level parameters (including some cell-level parameters) such as RNCID and CELLID do not need to be compared. When the parameters of one RNC before and after an upgrade are compared, the parameters should completely match. Thus, a contradiction between parameter matching and parameter mismatching occurs. Currently, one parameter configuration script cannot satisfy the requirements of two types of parameter comparison. The current solution is to add another parameter configuration script in the next version so that the requirements of the two types of parameter comparison can be satisfied. 3)

Problem about the comprehensiveness of parameters

As the transport layer parameters cannot be compared, the problem about the comprehensiveness of parameters arises. The existence of parameter configuration items for Nastar's parameter configuration gives us such a hint: When configuring parameters, we can add or delete some parameters to meet different requirements. Before the parameter comparison module is widely applied, the parameter configuration must be reviewed and a reference parameter configuration script is required. Some parameters cannot be compared. This results in a contradiction between parameter display and parameter comparison comprehensiveness. Therefore, parameter configuration is more crucial.

At present, there is no accurate method for comparing the transport layer parameters. Therefore, these parameters are directly neglected. In addition, some parameters are not configured because they are insignificant. Therefore, you should distinguish the problem about the comprehensiveness of parameter comparison all by yourself. 4)

Problem about parameters not configured

The MML script parameter comparison module compares only the parameters configured in the parameter configuration script. In this case, the parameter commands are different between different versions of one RNC or between two MML scripts compared with the baseline. As the new parameters are not configured in the parameter configuration script, they cannot be compared and displayed. Therefore, it is recommended that the function of querying the parameter change be added. This function involves two steps. First, the parameter change between the two MML scripts for parameter comparison is queried. Then, these new parameters are searched in the parameter configuration scripts to check whether they are configured; if they are not configured, they are listed in an Excel file, prompting for configuration.

It is confirmed that the parameters that have been compared and that have not been compared are listed. You can configure the parameters that are not configured in the parameter configuration script according to requirements. The program is unable to distinguish new parameters from those that are not configured (for example, transport layer parameters). This function is implemented in the version released on January 2008. 2007-12-13

All rights reserved

Page198 , Total220


9.7 Parameter configuration script cmpcmd.xml of the Nastar cmpcmd.xml

9.8 NodeB parameter mapping table cfg.rar

9.9 Script configuration used for NodeB XML parameter comparison The configuration file used for NodeB parameter comparison is a parameter mapping table. Similar to the RNC, a NodeB also is equipped with an LMT on which you can set relevant parameters of the NodeB. These parameters are common but may be inconsistent with those in the NodeB parameter configuration script. There is a corresponding relation between the parameters on the LMT of the NodeB and those in the parameter configuration script. The RAN maintenance department implements maintenance of a NodeB through the parameter configuration script. It is confirmed that a correspondence exists between the parameters on the LMT and those in the parameter configuration script. The table below lists the parameter mapping. Table 9-2 Parameter mapping table Para Command Command Index SET HSDPAFLOWCTRLPARA PARAV18CLASS SET HSDPAFLOWCTRLPARA PARAV18CLASS SET HSDPAFLOWCTRLPARA PARAV18CLASS

Para Item

DR

wDiscardRate

SET MACHSPARA

HSDPAPARA_V18

RSCALLOCM

RSCALLOCMETHOD

SET MACHSPARA

HSDPAPARA_V18

SM

SCHEDULMETHOD

SET MACHSPARA

HSDPAPARA_V18

MXRETRAN

MAXRETRANSCNT

SET MACHSPARA

HSDPAPARA_V18

PWRMGN

POWERMARGIN

SET MACHSPARA

HSDPAPARA_V18

SCCHPWRCM

SCCHPWRCM

2007-12-13

Item Index

HSDPAFLOWCTRL SWITCH

bSwitch

HSDPAFLOWCTRL TD

bDelay

HSDPAFLOWCTRL

All rights reserved

Page199 , Total220

WCDMA OMC Operation Guide Internal Open Para Command SET MACHSPARA

HSDPAPARA_V18

SCCHPWR

SCCHPWR

SET MACHSPARA

HSDPAPARA_V18

SCCHFER

SCCHFER

SET MACHSPARA

HSDPAPARA_V18

IBLER

INITBLER

SET MACHSPARA

HSDPAPARA_V18

RSCLMSW

RSCLMTINGSW

SET MACHSPARA

HSDPAPARA_V18

DYNCODESW

DYNCODESW

SET MACHSPARA

HSDPAPARA_V18

16QAMSW

SIXTEENQAMSW

SET MACHSPARA

HSDPAPARA_V18

ADJCOEOFPF

ADJCOEOFPF

SET MACHSPARA

HSDPAPARA_V18

MXPWRPHUSR

MXPWRPHUSR

SET MACHSPARA

HSDPAPARA_V18

CQIFA

CQIFILTERALPHA

SET MACHSSPIPARA

HSDPASPIPARA

SPIGBR

SPIGBR

SET MACHSSPIPARA

HSDPASPIPARA

SPIWEIGHT

SPIWEIGHT

SET MACHSSPIPARA

HSDPASPIPARA

SPIRSCRATIO

SPIRSCRATIO

SET MACEPARA

HSUPAMACEPARA

AGTHRESHOLD

AGTHRESHOLD

SET MACEPARA

HSUPAMACEPARA

WSPI

WSPI

SET MACEPARA

HSUPAMACEPARA

CELLNOISEFUNDUS

CELLNOISEFUNDUS

SET MACEPARA

HSUPAMACEPARA

GBRSWITCH

GBRSWITCH

SET MACEPARA

HSUPAMACEPARA

EAGCHPCMOD

HPCMODE

SET MACEPARA

HSUPAMACEPARA

EAGCHPWROFFSET

HPCPWROFFSET

SET MACEPARA

HSUPAMACEPARA

EAGCHPOWER

HPCFIXPWR

SET MACEPARA

HSUPAMACEPARA

SERGCHPCMOD

HPCMODE

SET MACEPARA

HSUPAMACEPARA

SERGCHPWROFFSET

HPCPWROFFSET

SET MACEPARA

HSUPAMACEPARA

SERGCHPOWER

HPCFIXPWR

SET MACEPARA

HSUPAMACEPARA

NSERGCHPCMOD

HPCMODE

SET MACEPARA

HSUPAMACEPARA

NSERGCHPWROFFSET

HPCPWROFFSET

SET MACEPARA

HSUPAMACEPARA

NSERGCHPOWER

HPCFIXPWR

SET MACEPARA

HSUPAMACEPARA

SEHICHPCMOD

HPCMODE

SET MACEPARA

HSUPAMACEPARA

SEHICHPWROFFSET

HPCPWROFFSET

SET MACEPARA

HSUPAMACEPARA

SEHICHPOWER

HPCFIXPWR

SET MACEPARA

HSUPAMACEPARA

NSEHICHPCMOD

HPCMODE

SET MACEPARA

HSUPAMACEPARA

NSEHICHPWROFFSET

HPCPWROFFSET

SET MACEPARA

HSUPAMACEPARA

NSEHICHPOWER

HPCFIXPWR

SET MACEPARA

HSUPAMACEPARA

BUFCONGTHD

BUFCONGTHD

SET MACEPARA

HSUPAMACEPARA

BUFCONGTHDHYS

BUFCONGTHDHYS

SET MACEPARA

HSUPAMACEPARA

RNCFLUXENABLE

RNCFLUXENABLE

SET SMTHPWRSWTCH

SMTHPWRSWTCH

SWITCH

SWITCH

SET CLSPATIMER

CLOSEPATIME

LOWERLIMIT

LOWERLIMIT

SET CLSPATIMER

CLOSEPATIME

UPPERLIMIT

UPPERLIMIT

SET RESALLOCRULE

DLRESALLOCRULE

RULE

RULE

2007-12-13

All rights reserved

Page200 , Total220

WCDMA OMC Operation Guide Internal Open Para Command ADD SEC

SECTOR_V18

SECT

SECTORTYPE

ADD SEC

SECTOR_V18

DIVM

DIVMODE

ADD LOCELL

LOCALCELL_V18

RADIUS

RADIUS

ADD LOCELL

LOCALCELL_V18

HORAD

HORAD

ADD LOCELL

LOCALCELL_V18

DEFPWRLVL

DEFPWRLVL

ADD LOCELL

LOCALCELL_V18

DLRESMODE

DLRESALLOCMODE

ADD LOCELL

LOCALCELL_V18

DI

ULNI

ADD LOCELL

LOCALCELL_V18

HISPM

HISPM

NODEBSOM

NODEBSOM

NODEBSRCID

NODEBSRCID

LOCALCELL_V18

LOCALCELL_V18

LOCELLID

LOCELLID

The first column lists the parameter commands of the NodeB LMT. The second column is the mapping of the command parameters of the NodeB LMT in the XML script. The third column is the specific parameters in the commands of the NodeB LMT. The fourth column is the mapping of the parameters in the XML script. The parameter table is the parameter mapping table, namely, the parameter configuration script. For easy program implementation, two parameters are added: NODEBSCRID and LOCELLID. In this way, after NodeB parameters are obtained in batches, these two parameters can distinguish Node Bs from cells. The parameters highlighted in colors in the table are SPI parameters and MAC-E parameters. You should pay attention to these two parts of parameters.

9.10 Procedure for exporting the NodeB parameter configuration script through the M2000 1)

Enter the System Backup interface.

2)

Choose NE Backup List and the corresponding RNC. The backup configuration files of all NodeBs under the RNC are displayed on the right. One NodeB may have multiple backup configuration files. Click Filter to filter the backup files by time.

3)

It is recommended that you select all the backup files created recently so that each NodeB has one backup file but no repeated backup file.

4)

After the backup files are filtered based on time, each NodeB should have one backup file. Note that the first backup file is the database backup of the RNC.

5)

Select a local directory to save the configuration file.

6)

Check the downloading progress.

7)

Check the backup configuration file downloaded to the local directory.

2007-12-13

All rights reserved

Page201 , Total220


9.11 .NET Framework2.0 installation The Nastar R2 version setup requires the .NET framework2.0. Therefore, you must install this program first.

Figure 9-7 .NET Framework2.0 installation(1)

2007-12-13

All rights reserved

Page202 , Total220


Figure 9-8 .NET Framework2.0 installation(2)

Figure 9-9 .NET Framework2.0 installation(3) 2007-12-13

All rights reserved

Page203 , Total220


9.12 SQL Server2005 Express installation The SQL Server2005 program is required to support the Nastar R2. The installation method is described in detail. You can adopt the default configurations as shown in the corresponding figures.

Figure 9-10 SQL Server2005 installation(1)

2007-12-13

All rights reserved

Page204 , Total220




2007-12-13

All rights reserved

Page205 , Total220




2007-12-13

All rights reserved

Page206 , Total220


Figure 9-15 SQL Server2005 installation(6) Use the program installation path as the default installation path. Otherwise, the Nastar cannot be opened.

Figure 9-16 SQL Server2005 installation(7) 2007-12-13

All rights reserved

Page207 , Total220


You must select the Mixed Mode option, and then enter the password. The default username used to log in to the Nastar is sa.


Figure 9-18 SQL Server2005 installation(9) 2007-12-13

All rights reserved

Page208 , Total220




2007-12-13

All rights reserved

Page209 , Total220


9.13 Method of obtaining NodeB baseline through the CME 9.13.1 Open a project Open Project interface on the CME server If no project is available for selection, you can click Configuration to configure a project. In the figure below, 127.0.0.1 is a local IP address.

Figure 9-21 CME server configuration information (1)

Figure 9-22 CME server configuration information (2) After configuring the CME server information, you can log in to the CME server and open the CME operation interface.

9.13.2 Version configuration Add an RNS, as shown in the figure below.

Figure 9-23 Opening the RNS on the CME server Enter the RNC ID, and select an RNC version and NodeB version.

2007-12-13

All rights reserved

Page210 , Total220


Figure 9-24 Version selection

As we are concerned only with the radio parameters in the corresponding NodeB version during network planning, the negotiation planning data and the RNC-level parameters are not configured. After the parameters of a cell are configured, the parameter configuration script of the NodeB is exported. The parameter configuration script is only the NodeB baseline script that should be given importance in network planning. The radio layer parameters configured on the NodeB are the parameters in the default NodeB version. Therefore, the NodeB version here must be the one that the customer requires. After the parameter configuration, the corresponding parameters of the selected NodeB version are stored in the exported XML script.

9.13.3 Configure RNS parameters l

Open the RNS.

Figure 9-25 Opening parameter configuration on the CME server l

2007-12-13

Add a NodeB and configure related parameters.

All rights reserved

Page211 , Total220


Figure 9-26 Selecting NodeB parameters on the CME server

Figure 9-27 NodeB parameter configuration l

Add a cell and configure related cell-level parameters, such as cellID.

Figure 9-28 Selecting cell parameters on the CME server

Figure 9-29 Cell-level parameter configuration on the CME server

In this case, the network planning personnel must configure one cell for each NodeB, but need not configure any negotiation data (including transport layer parameters and neighborhood) because only the default configuration items at the radio layer are considered important. l

2007-12-13

Enter the NodeB configuration interface.

All rights reserved

Page212 , Total220


Figure 9-30 NodeB configuration interface

On this interface, you can click the MML button to export the RNC MML baseline script directly. You can directly obtain the RNC baseline script from the website http://support.huawei.com. Therefore, the method of obtaining MML baseline script through the CME is not recommended. You can also obtain the RNC baseline script through the CME. l

Click Physical Node B Basic Info to create physical channel information.

Figure 9-31 Creating a physical channel on the CME server

This operation is required because an XML script can be exported only after the physical channel information is configured. Export an XML script.

Figure 9-32 Exporting an XML script on the CME server

2007-12-13

All rights reserved

Page213 , Total220


Here we can see that we can directly import an existing XML script through the CME. After the XML script is imported using the CME, you can view the related configuration information. It is confirmed that the NodeB parameter comparison is not implemented in the CME. However, this function is ready to be added to the CME. The specific implementation time needs to be confirmed and the function is now at the requirement submission phase. The actual requirement is not discussed with the R&D personnel. The XML script we eventually see is the NodeB reference parameter configuration script that we concern.

9.14 Concerns of RNC parameter comparison for network planning 9.14.1 Comparison with the baseline parameters

Selection of the Reference Cell ID Since the reference cell ID in the product baseline is 0, the cell ID for baseline comparison can be only 0. However, if the reference MML script is not the product baseline MML script, after the existing network MML script is imported, the Base cell ID (reference cell ID) is an optional Cell ID in the MML script and the cell to which a Cell ID corresponds can be selected as the reference cell.

Parameter Change Record A product baseline is always provided when a product is upgraded. The parameters in the baseline script are set to the default values. There are no recommended values for these parameters, and they must be configured according to the actual network condition. For easy network parameter management and version upgrade, a parameter change record is provided to serve as a monitoring point. The parameter change resulting from each version upgrade is recorded, with the reasons for the change.

It is confirmed that the reasons for the parameter differences in the parameter change record are as follows: 1) The customer's network parameters are reused. 2) Parameters are modified for the purpose of KPI acceptance. 3) Parameters are modified on site. 4) The version upgrade causes parameter change but parameters are not modified on site. 5) The precaution items are released at the website http://support.huawei.com.

The parameters that are changed in the parameter template should be confirmed one by one on site. Reasons for the parameter difference should be given in the parameter change record so that subsequent problems can be traced and referenced. Instance of a network parameter change record 2007-12-13

All rights reserved

Page214 , Total220


Report_与基线比较 .rar

Parameter Script Configuration Currently, the parameter comparison module of the Nastar only compares the parameters configured in the script, instead of those not configured. Therefore, the parameters not configured in the script are not displayed in a report. The parameters in the parameter configuration script must be preset.

Problem About Hierarchical Networking Generally, only one reference cell is configured in the baseline script and the ID of the reference cell is 0. In the case of hierarchical networking, R99 cells and H cells need to be distinguished. The configuration of a single cell in the baseline is unable to satisfy the actual requirements. Network planning personnel needs to configure another reference cell in the baseline to distinguish between different types of cells. The next section describes the division of cluster in the case of hierarchical networking.

Customized Sheet Entries Currently, the baseline parameter comparison function displays only two sheet entries, namely, RNC-level parameter comparison results and cell-level parameter comparison results. In the parameter configuration script, different parameters are classified and some parameters are of the same type but are RNC-level parameters and cell-level parameters, respectively. Currently, the two parameter-display sheet entries cannot meet this requirement. To solve this problem, the sheet-entry customization function is adopted. The function allows the customer to customize a sheet entry name and display the comparison results of the required parameters. It is confirmed that this function is implemented in the version released in January 2008.

Inconsistency of the Imported MML Script In the case of hierarchical networking, you need to configure different clusters. Before configuring clusters, you must first import the MML script into the project, and then utilize the NE Group in the Nastar to set the cluster. After the MML script is imported, parameters are compared and another MML script is imported. The case happens that the two MML scripts are different. If the data imported for the second time is different from the data imported for the first time, the comparison results may be different. As a result, the inconsistency between the cluster and the information in the MML script to be compared causes parameter comparison errors. Network planning personnel must ensure that the clusters set in the Nastar are consistent with the information in the MML script to be compared.

2007-12-13

All rights reserved

Page215 , Total220


9.14.2 Parameter comparison between different cells in one MML script

Problem about Hierarchical Networking Different networks have different networking modes, which gives rise to the problem of hierarchical networking. Such is the case with the network of the project in Singapore. R99 cells utilize one frequency and H cells utilize another frequency. The hierarchical networking problem affects the cell-level parameter comparison. At the time of cell-level parameter comparison, the cell cluster to which the reference cell belongs should be considered. R99 cells and H cells in the network in Singapore follow certain naming rules. Cells whose IDs end with 0, 8, or 9 are R99 cells while cells whose IDs end with 5, 6, or 7 are H cells. The naming rules for Cell ID are different in different offices. The division of clusters depends on the actual division rules. The figure below shows the parameter configuration.

Figure 9-33 Parameter configuration of different clusters

Cluster-To-Cell indicates the cell group to be selected. The name of this option is blurred. The R&D department is already recommended to change the name to Group Cell Select. As shown in the preceding figure, different cells belong to different cell groups. Select a cell from a different cell group to serve as a reference cell. You can set a cell group through the NE Group option or by importing the cell group into an Excel file. l

2007-12-13

Set the cell group type through the NE Group option on the Nastar. All rights reserved

Page216 , Total220


Figure 9-34 NE Group for cell group setting

The method of setting the cell group through the NE Group option is the same as that of configuring a swapped cell group. A cell group is set on the WCDMA (the Nastar consists of two parts: WCDMA and Transdata). You should use Transdata to import the MML script of the cell group to be configured to the Nastar project in advance. Otherwise, the cell group cannot be configured. l

Import the cell group into an Excel file.

The table below shows the Excel data format. Table 9-3 Excel data format for cell group setting Type:

Cell Group

RNCId

CellId

402

29040

402

20160

402

20430

402

20950

402

20990

402

21270

2007-12-13

All rights reserved

Page217 , Total220


The Excel data format must strictly follow the data format shown in the preceding table. The cells in the configured cell group must correspond to the MML script that is imported in the Nastar project in advance. That is, the imported cell must exist in the Nastar database. Otherwise, the cell group cannot be set. In this sense, the two methods of configuring a cell group are consistent.

Change of Cell-Level Parameters Certain cell parameters, for example, some parameters in the ADD CELLSETUP command, should be different. The NodeB name and LOCELL vary with cells (see the figure below). The parameter differences must be distinguished or the parameters should be screened at the time of script configuration. For details on the parameter configuration of script comparison, see the section "Parameter Configuration". Table 9-4 Example of cell parameters ADD CELLSETUP ADD CELLSETUP

LOCELL NODEBNAME

7 "1230_PCOSTAA_D"

5 "1029_PCLRKQY_D"

The implementation of such parameters can be avoided through parameter configuration.

Reference Cell Selection and Maintenance Here a cell in the existing network is selected to serve as a reference cell. Other cells are compared with the reference cell. The parameters of the reference cell should be as complete as possible because the setting of RNC-level parameters involves the setting of cell-level parameters and parameters are reserved for RNC-level parameter comparison and cell-level parameter comparison. In the case of hierarchical networking, the reference cell in each cell group must be maintained.

9.14.3 Parameter comparison between different RNCs

RNC-Level Parameter Comparison Transport layer parameters are RNC-level parameters. The configuration of the transport layer parameters is very flexible. The indexes of the transport layer parameters of different RNCs are different. The transport layer parameters cannot be compared and the comparison results cannot satisfy the requirement. The transport layer parameter comparison will be implemented in later versions. The specific implementation time is to be determined.

Change of RNC-Level Parameters RNC-level parameter change occurs between different RNCs. This attribute is, however, specific to each RNC. For example, the parameter RNCID is not what we 2007-12-13

All rights reserved

Page218 , Total220


concern. Here, you should determine the parameter change by yourself or avoid parameter change in the configuration file for parameter comparison.

Problem about Hierarchical Networking The problem about hierarchical networking also exists in cell-level parameter comparison. For details about the specific method, see the section "Parameter Comparison Between Different Cells in One MML Script".

Problem about Different RNC Versions The RNC versions to be compared between two MML scripts should be consistent. If the versions are inconsistent, the configurations of many parameters are different, and may cause problems in parameter addition or deletion. This function can be applied only when the RNC versions are the same.

Parameter Comparison Between Different Versions of an RNC For the parameter comparison between different versions of an RNC, parameters can generally be matched completely. However, certain parameters cannot be matched, for example, when the transmission bandwidth is changed. If new parameters cannot be matched, they are displayed in the comparison results, with a value displayed for a configured parameter but no value for a parameter that is not matched. You should pay attention to the parameters that cannot be matched completely.

2007-12-13

All rights reserved

Page219 , Total220


List of Reference 1)

HUAWEI BSC6800 WCDMA RNC Operation Manual Data Configuration

2)

Subject S RNO Equipment Room Operation Guide

3)

WCDMA NodeB V100R003 BTS3812-3806-3806A Electric Antenna Operation Guide-209050919-A-1.1

4)

WCDMA NodeB V100R005 BTS3812E-DBS3800 Electric Antenna Installation and Operation Guide-20050919-A-1.0

5)

WCDMA RNO Load and Test Operations Guide

6)

WCDMA RNO Call Tracing Data Collection Guide

7)

Huawei BSC6800 RNCV100R007C01B061 Release Notes

8)

Guide to NodeB Traffic Measurement by the UMTS&GSM Radio Performance R&D Department

2007-12-13

All rights reserved

Page220 , Total220

Huawei Omc Operation Wcdma

Recommend Documents