W OMC Operation Guide 20081208 a 3_5

WCDMA OMC Operation Guide Internal Open Product name WCDMA RNP Product version 3.5 Confidentiality level For internal use only Total 220 pages

WCDMA OMC Operation Guide(For internal use only)

Prepared by Reviewed by Reviewed by Approved by

Hu Mingchao Hua Yunlong, Xie Zhibin, Wang Xiangxiong, Ai Hua, and Yan Lin Qin Yan

Date Date Date Date

2004-11-26

Huawei Technologies Co., Ltd.All rights reserved.

2007-12-13

All rights reserved

Page1 , Total220

WCDMA OMC Operation Guide Internal Open

Revision RecordsDate 2004-11-26 2005-01-29 2005-03-15 Version 1.00 1.10 1.20 Initial transmittal. Supplementing precautions in equipment room and routine data collection. Description Author Hu Mingchao Chen Xin

2005-05-05 2005-05-25 2005-06-01

1.30 1.40 1.50

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. Supplementing alarms and revising part of traffic measurement. Adding time control of CR flow, viewing cell states executing the DSP command after cells are activated. Sun Daming Zhang Youbin

2005-06-05

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 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 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 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 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-14

2.01

2005-06-22

2.02

2005-11-21 2006-06-16

3.0 3.1

2006-11-10

3.1

2007-12-13

All rights reserved

Page2 , Total220


Date 2007-09-01 3.2

Version

Description

Author

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 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 Lichuanhai

2008-12-5

3.5

2007-12-13

All rights reserved

Page3 , Total220


Table of Contents1 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 TablesTable 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 FiguresFigure 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 reportselect a measurement object .............................101 Figure 3-31 Customizing a query reportselect the corresponding counter values ............102 Figure 3-32 Customizing a query reportselect a time mode and a period ........................103 Figure 3-33 Customizing a query reportsave 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 GuideKey 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 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

2007-12-13

All rights reserved

Page15 , Total220


1 Introduction1.1 ContentsThis 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 l l l l l l l l 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 M2000 OM system

3)

It includes the following in M2000:l l l l 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 NodeB OM

4)

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)l l l l

OM at core network side Tracing UEs Querying bills Viewing bills Extracting bills Querying alarm All rights reserved Page16 , Total220

It includes the following under MSC:

6)

It includes: 2007-12-13

WCDMA OMC Operation Guide Internal Openl 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 NetworkingFigure 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 IntroductionThe 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

WCDMA OMC Operation Guide Internal Openl

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

1.4 Rules and Precautions in Equipment RoomFor 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 System2.1 Installing and Starting RNCRNP&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. All rights reserved Page19 , Total220

2007-12-13

WCDMA OMC Operation Guide Internal Openl l

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) 2)

Click

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

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) 2) 3) 4) 5) 6) 7) 8) 9) Tracing signaling at standard interfaces of single subscriber Tracing connection performance of single subscriber Tracing cell performance Tracing calls Querying cell-related parameters Editing and executing MML command line and batch processing scripts Traffic measurement Importing and exporting CFGMML file 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 Subscriber2.2.1 BackgroundWhen 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 ProcedureTo trace signaling at standard interfaces of single subscriber, perform the following steps: 1) 2) 3) Double-click UE tracing (Standard Interface Message) in Maintenance Navigator. Select All standard interface in the pop-up dialog box. 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. 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.

6)

Figure 2-5 Starting TraceViewer On RNCv1.7, to trace the signaling of a single UE on standard interfaces, perform the following steps: 1) 2) 3) Double-click UE (Standard Interface) in Maintenance. Select All standard interface message in the pop-up dialog box. 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 All rights reserved Page24 , Total220

2007-12-13


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) 6) 7) Click Save as. You can modify the path where the data is to be saved. Click OK. The tracing starts. 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 Subscriber2.3.1 ContentWhen 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) 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)

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

2.3.2 ProcedureTo 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. Close the window or right click on the menu after tracing, and select Stop monitoring to stop tracing

3)

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 Performance2.4.1 ContentWhen 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 ProcedureTo 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 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. After tracing, close the window or right click on the menu to select Stop monitoring to stop tracing 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.

2)

3) 4)

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. 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. After tracing, close the window or right click on the menu to select Stop monitoring to stop tracing. 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.

2)

3) 4)

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 CallsThe 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 BSC6800Type of traced task Tracing messages at standard interfaces of UE 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.

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

Tracing IOS (multiple calls at the same time)

Tracing cells

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 LayerWhen 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 BSC6800Type of traced tasks QAAL2 protocol message SCCP 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.

MTP3B protocol message

SAAL protocol message

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 MNCDTMissing 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) 2) In Maintenance, double click MNCDT. Select the type to be traced in the pop-up dialog box. 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. 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.

3)

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/IFTSThis 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 LineDuring 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) 2) 3) Click the icon in BSC6800 OM to start MML Client operation interface

Type commands in Command Input field and fill in with related parameters 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 optimizationEquip ment Type Commands for querying cell states and parameters Command Detailed operation Cell name Frequency Scramble Maximum transmit power TimeOffset Corresponding NodeB name, Remarks

RNC

Command for querying cell data includes: LST CELL

2007-12-13

All rights reserved

Page45 , Total220

WCDMA OMC Operation Guide Internal Open Equip ment

Type

Command

Detailed operation 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.

Remarks

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

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

Commands for modifying cell states and parameters.

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

Use column editing function of UltraEdit

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

Modify transmit power of PCPICH. Modify the maximum and minimum

2007-12-13

All rights reserved

Page46 , Total220


Type

Command

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

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

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

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

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

2007-12-13

All rights reserved

Page47 , Total220


Type

Command

Detailed operation

Remarks E-DCH depending on network planning

Command for exporting CFGMML script include: EXP CFGMML Exporting Frequently-us ed data of NC Commands for exporting log include: LST LOG EXP LOG

Exe

Documents

W OMC Operation Guide 20081208 a 3_5