Ultima Mentor Required Data Inputs for Huawei.pdf

Table Contents

Ultim lt ima a™ Me Mentor nt or Requir qu ire ed Data Data Inp Input uts s for f or Huawei uawei Inf Infrastr rastruct uctur ure e

i

Ultima Mentor Required Data Inputs for Huawei Infrastructure

Confidentiality, Copyright Notic e & Disclaimer Disclaimer Due to a policy of continuous product development and refinement, TEOCO Ltd. (and its affiliates, together “TEOCO”) reserves the right to alter the specifications, representation, descriptions and all other matters outlined in this publication without prior notice. No part of this document, taken as a whole or separately, shall be deemed to be part of any contract for a product or commitment of any kind. Furthermore, this document is provided “As Is” and without any warranty. This document is the property of T EOCO, which owns the sole and full r ights including copyright. TEOCO retains the sole property rights to all information contained in this document, and without the written consent of TEOCO given by contract or otherwise in writing, the document must not be copied, reprinted or reproduced in any manner or form, nor transmitted in any form or by any means: electronic, mechanical, magnetic or otherwise, either wholly or in part. The information herein is designated highly confidential and is subject to all restrictions in any law regarding such matters and the relevant confidentiality and non-disclosure clauses or agreements issued with TEOCO prior to or after the disclosure. All the information in this document is to be safeguarded and all steps must be taken to prevent it from being disclosed to any person or entity other than the direct entity that r eceived it directly from TEOCO. TEOCO and Netrac® are trademarks of TEOCO. All other company, brand or product names are trademarks or service marks marks of their respective holders. This is a legal notice and may not be removed or altered in any way. COPYRIGHT © 2013 TEOCO LTD. ALL AL L RIGHTS RESERVED. RESERVED.

Your feedback feedback is impo rtant to us: The TEOCO Documentation team takes many measures in order to ensure that our work is of the highest quality.

If you found errors or feel that information is m issing, please send your Documentation-related feedback to [email protected] Thank you, The TEOCO Documentation team

ii

Table Contents

Document Revision History Ver

Date

Author

Change Description

iii


Table of Contents 1

Intro duct io n .................................................................................................................. 1 1.1 Definitions, Acronyms, and Abbreviations ..............................................................1 2 Mentor Prelimi nary Setup Checklist .......................................................................... 2 3 Detailed Description of Required Information and Data .......................................... 3 3.1 Network Data..........................................................................................................3 3.1.1 Huawei Switch Dump – Inner Configuration MML ...........................................3 3.1.2 Antenna and Sectors Physical Location, Profiles, and Parameters in Delimited Format ........................................................................................................... 5 4 Huawei Logs and Stats ............................................................................................... 7 4.1 Logs (CHR) Files ....................................................................................................7 4.1.1 CHR/UPCHR File Paths ..................................................................................7 4.1.2 CHRs in the Inner Configuration MML File ...................................................... 7 4.2 Stats (PMs) File ......................................................................................................9 4.2.1 Retrieval Procedure.........................................................................................9 4.2.2 Performance Data Export ..............................................................................10 4.2.3 Generating RNC PMs Files using the M2000 Tool ........................................13 4.2.4 Mandatory Counters......................................................................................18

Table of Figures Figure 1: Executing scheduled INNER MML scripts .............................................................3 Figure 2: Executing one-time INNER MML scripts................................................................4 Figure 3: Executing the CHRRNCCTRL command through LMT ......................................... 8 Figure 4: Task Management command .............................................................................. 10 Figure 5: 30Minute counters tab ......................................................................................... 11 Figure 6: Selected tables in the right pane..........................................................................12 Figure 7: Common Parameters tab showing task information ............................................ 13 Figure 8: Active Measurement command ...........................................................................14 Figure 9: Active dialog box..................................................................................................15 Figure 10: Active measurement – enable counters.............................................................16

iv

Introduction

1 Introduction The following document contains a list of all the required information and data to be collected on Huawei UMTS infrastructures in preparation for the installation of the Mentor optimization tool. The information and data required includes the following: •

•

Network configuration (described in detail in section 3) o

Schema Format

o

Network Topology file (MML)

o

Network Preferences

Huawei logs and stats (described in detail in section 4) o

CHR logs

o

PMs

When preparing to set up Mentor in a network, it is usually recommended to start by creating the network configuration, followed by a sample data collection. Section 2 outlines a “setup checklist”, which should be used as a first step to facilitate efficient installation and configuration. The following sections of this document provide a more in-depth description of the required data sources, and the manner in which they can be obtained.

1.1 Defini tions , Acronyms , and Abbreviations The following definitions, acronyms, and abbreviations are u sed throughout this document: •

HO – handoff

•

HHO – hard handoff

•

NL – neighbor list

•

RNC - Radio Network Controller

•

RAB – Radio Access Bearer

1


2 M en t o r Pr e l i m i n a r y S et u p Ch e c k l i s t The following table summarizes the minimal data required for the kickoff of a Mentor installation. This table should be used as a reference to expedite the installation process. These files can be collected by TEOCO professional services on site, or by the customer point of contact. Mandatory files and definitions: Description -

Data source

Reference

Huawei RNC

Section 3.1.1

1

Huawei Switch Dump MML script

2

Antenna file

Planning tool, Internal database

Section 3.1.2.1

3

Terrain file

TAB, GRD, GeoTiff

Section 3.1.2.2

4

Antenna profiles

Planet format

Section 3.1.2.3

and others 5

CHR log files

LMT tool

Section 4.1

6

Huawei Counter tool

M2000 tool

Section 4.2

2

Check

Detailed Description of Required Information and Data

3 D et a i l e d D es c r i p t i o n o f R eq u i r e d I n f o r m a t i o n a n d Data 3.1 Netw ork Data The sources for network configuration data are: •

•

Schema Format files, including complete information required for physical sites and soft parameter configuration (depending on availability) in text format. A predefined set of Network Topology files exp orted from the Huawei switch dump.

3.1.1

Huawei Switc h Dump – Inner Config urati on MML

The MML file is a configuration file that contains all the NodeB parameters per RNC.

3.1.1.1 Retri eval Proc edure The MML script is generate by the LMT tool every day. The default path for the MML file is: BAM/Version/FTP 3.1.1.1.1

Using the LMT Tool to Schedul e Subtask s that Generate INNER Confi gur atio n MML Scrip ts

Figure 1: Executing sch eduled INNER MML scrip ts

3


1. In the LMT tool, execute the command ADD SUBTSK in the Command Input field. 2. Enter the information in the relevant fields. Note that fields in red are mandatory, and must be filled in. a. In the Command String field, enter EXP INNERCFGMML to execute the MML script. b. Choose the start date c. Choose the time mode - DAILY_T (day_based_scheduling) d. Choose the execute time – the t ime when the MML script is generated. 3. You can also run a command through a batch file: ADD SUBTSK: ID=1, TSKN="INNERMML", SUBID=1, ENF=ENABLED, SCMD="EXP INNERCFGMML", FREQ=DAILY_T, SD=2009&02&19, RFT=1; 3.1.1.1.2

Using the LMT Tool to Generate One-Time MML Scrip ts

Figure 2: Executing one-time INNER MML scri pts

1. In the LMT tool, execute the command EXP INNERCFGMML in the Command Input field. 2. Enter the path in which to store the MML file in the Export file path field. If you do not enter a value, the default value is used: BAM/Version/FTP 3. Enter a name for the exported file in the Export file name field. The following name should be used: INNERCFGMML-20090212120000.txt

4

Detailed Description of Required Information and Data

3.1.2

Antenna and Secto rs Physi cal Location , Profi les, and Parameters in Deli mit ed Format

The physical parameters of the network, such as the sector and antenna location, and the antenna profiles, may not be available through the configuration dump. Most of the required physical configuration of the network can be derived from network planning tools or from customer-self-maintained databases with the most updated network configuration. Mentor defines a set of textual files that should be available. These files are: •

Antenna file - includes the physical configuration of each sector. See section 3.1.2.1 below for the file format.

•

Antenna profiles – antenna-pattern data files

•

Mentor also requires an updated Terrain file

In contrast to planning tools or other configuration sources, Mentor requires only active sector-carriers. Sectors that are inactive during an analyzed period should be marked as “inactive” in the antenna files. All soft parameters may be defined in this file, but will be overridden by the Network Topology files. It is recommended that the latest Network Topology files be used to update the Schema Format file and to identify any i nconsistencies, such as missing or unnecessary sectors.

3.1.2.1 Ant enna Fil e The antenna file (in tab-delimited text format) includes the physical configuration of each sector, including: •

Location data (i.e., coordinates, height, and so forth)

•

Antenna characteristics (i.e., height, azimuth, and so forth)

•

Physical constraints

•

Network topology

The antenna file must include all sectors selected for optimization and all sectors in the guard-zone area – where optimization is not performed. It is recommended that all sectors within two tiers of the selected sectors be included.

5


The Antenna file fields are described below. Field

Mandatory?

Description

Default value

RNC Name

TRUE

Unique in the network RNC display name

RNC ID

TRUE

Unique in the network

Vendor

TRUE

The vendor of the RNC

NodeB Name

TRUE

Site display name

NodeB Id

TRUE

Unique under the same RNC

NodeB Longitude

TRUE

NodeB Latitude

TRUE

Sector Name

TRUE

Active

TRUE

TRUE

Missing Data

TRUE

FALSE

Noise Figure

TRUE

AntennaID

TRUE

Unique under the same cell

Antenna Model

TRUE

Lookup from antenna DB

Sector Keywords

FALSE

Comma-separated list of keywords, if any

Antenna Longitude

TRUE

Antenna Latitude

TRUE

Height

TRUE

Height of the antenna above ground

Mechanical DownTilt

TRUE

Mechanical tilt

Azimuth

TRUE

Downlink Loss

TRUE

0

Uplink Loss

TRUE

0

RTT fix A Coefficient

TRUE

1

RTT fix B Coefficient

TRUE

0

RET ID

FALSE

In Building

TRUE

In Use

Parent of cell

FALSE Table 1: Antenna File Parameters

Note: If UTM coordinates are used, the rel evant column headers should be different: NodeB X, NodeB Y, Antenna X and Antenna Y

3.1.2.2 Terrain File The terrain map should be in GeoTif data format. It is recommended that the map resolution be at least 50m. Mentor can support additional terrain file formats, such as TAB, GRD, etc.

3.1.2.3 Antenna Profi les Antenna-pattern data files are in Planet format.

6

Huawei Logs and Stats

4 Huaw ei Log s and Stats 4.1 Log s (CHR) Files From Mentor v7.0, the IOS traces are no l onger used as the log data is collected from CHRs.

4.1.1

CHR/UPCHR Fil e Paths

4.1.1.1 Huawei R10 From Huawei R10, the CHRs are generated automatically and stored under the BAM in the following path: - /BAM/VersionA/LoadData/FamLofFmt 4.1.1.2 Huawei R12 From Huawei R12, UPCHR or PCHR log files are collected instead of CHRs. They are generated automatically and stored under the BAM in the following path: - /BAM/VersionA/LoadData/FamLofFmt Or - /bam/common/fam/famlogfmt/

4.1.2

CHRs in the Inner Configu ratio n MML File

Before running a model, check that the CHRs field is enabled in the INNER MML file. 1. Check table “SET CHRRNCCTRL:” 2. Check if all fields are enabled (set to 1), for example: a. STATETYPE=ABNORMAL_ONLY-1&NORMAL_ONLY-1 meaning that the CHRs log abnormal and normal calls 3. (In R14 and above systems only): In table “SET URRCTRLSWITCH:”, make sure the parameter RNC_PCHR_OUTPUT_CTRL_SWITCH is disabled (set to 0). If it is enabled, disable it by running the command: SET URRCTRLSWITCH: PROCESSSWITCH2=RNC_PCHR_OUTPUT_CTRL_SWITCH-0;

7


4.1.2.1 Usin g the LMT to Enable the CHRs Field If one of the fields is not enabled in the CHRs, use the following command to enable it: 1. In the LMT tool, execute the command SET CHRRNCCTRL in the Command Input field. 2. In the Type option drop down lists, click the SELECT ALL check box. 3. In Huawei R10 and above, you can run the command through a batch file only: SET CHRRNCCTRL:STATETYPE=ABNORMAL_ONLY-1&NORMAL_ONLY-1, DOMAINTYPE=CS_ONLY1&PS_ONLY-1, FLOWTYPE=CONN_SETUP-1&RAB-1&DCCC-1&SHO-1&HHO-1&SYS_HO_OUT1&RRC_RELEASE-1&STAT-1&NET_OPT-1, RRCCAUSE=ORIGINATING_CONVERSATIONAL_CALL1&ORIGINATING_STREAMING_CALL-1&ORIGINATING_INTERACTIVE_CALL1&ORIGINATING_BACKGROUND_CALL-1&ORIGINATING_SUBSCRIBED_TRAFFIC_CALL1&TERMNT_CONVERSATIONAL_CALL-1&TERMNT_STREAMING_CALL-1&TERMNT_INTERACTIVE_CALL1&TERMNT_BACKGROUND_CALL-1&EMERGENCY_CALL-1&INTER_RAT_CELL_RESELECTION1&INTER_RAT_CELL_CHG_ORDER-1®ISTRATION-1&DETACH-1&ORIGINATING_HIGH_PRIOR_SIG1&ORIGINATING_LOW_PRIOR_SIG-1&CALL_RE_ESTAB-1&TERMNT_HIGH_PRIOR_SIG1&TERMNT_LOW_PRIOR_SIG-1&TERMNT_CAUSE_UNKNOWN-1&MBMS_RECEPTION1&MBMS_PTP_RB_REQ-1;

Figure 3: Executing the CHRRNCCTRL command t hrough LMT

8


4.1.2.2 Mandatory Fields to be Enabled in the CHRs The following fields are mandatory fields to be enabled by the LMT: Field name ABNORMAL_ONLY NORMAL_ONLY CS_ONLY PS_ONLY CONN_SETUP RAB NET_OPT SHO HHO RRC_RELEASE

4.2 Stats (PMs) File 4.2.1

Retri eval Procedure

The Counter files are generated through the Huawei OSS per RNC. The PMs files, per RNC, are located in: /export/home/omc/var/fileint/pm/ Or /export/home/omc/var/fileint/pmneexport

File format: pmresult___.csv or or pmresult___.xml

9


For example, pmresult_67109395_30_200902010000_200902010030.csv / \_ export \_ home \_ omc \_ var \_ fileint \_ pmneexport \+ neexport_20110429 \+ neexport_20110430 \+ neexport_20110501 \+ neexport_20110502 \+ neexport_20110503 \+ neexport_20110504 \+ neexport_20110505 \_ neexport_20110506 \+ BNSRNC3511 \+ BNSRNC3512 \_ BNSRNC3513 \_ A20110506.1600-0400-1630-0400_BNSRNC3513.xml \_ …………

4.2.2

Perfo rm ance Data Export

If the default location is empty, proceed as follows: 1. On the M2000 tool, go to Maintenance

Task Management.

Figure 4: Task Management comm and

2. In the Task Management tab, select Performance Data Export.

10


3. In the Attribute window, select the Extended Parameters tab, and then the 30Minute counters tab.

Figure 5: 30Minute coun ters tab

11

Ultima Mentor Required Data Inputs for Huawei Infrastructure •

In the Extended Parameters tab, select which tables of counters you would like to export and move them to the right-hand pane.

Figure 6: Selected tables in the right pane

4. Press Apply. Note: •

File Path – Export location.

•

File Format – CSV all releases; XML all releases

•

If not all the tables are shown under the 30Minute tab, select the 15Minute tab and export the relevant tables.

12


5. In the Common Parameters tab (which shows the task information), keep the default parameters.

Figure 7: Common Parameters tab showing t ask information

4.2.3

Generatin g RNC PMs Files using the M2000 Tool 1. In the M2000 tool, click the Measure Management tab. 2. In the Organization Style check object Type. 3. Choose RNC to activate the RNC PMs. 4. Choose NodeB to activate the RBS counters. A list of tables will be displayed for each selection.

13


4.2.3.1 Acti vating RNC PMs (Counters) 1. Right-click the list of tables and select Active Measurement.

Figure 8: Active Measurement comm and

14


The Active dialog box is displayed.

Figure 9: Activ e dialog box

2. Select the tables you want to activate. The following tables must be activated: i.

Measurement between a cell and a neighbor interRAT cell

ii.

Measurement between a cell and a neighbor UMTS cell

iii.

Measurement of Radio Cell Performance

iv.

Measurement of RNC performance

3. In the Period area, select 30 Minutes. 4. Click OK, and then select the Measurement Settings tab.

15


5. Enable all the counters.

Figure 10: Act ive measurement – enable count ers

All counters will be generated every 30 minutes and will be stored under the RNC in the following path: /export/home/omc/var/fileint/pm/ Or /export/home/omc/var/fileint/pmneexport

16


4.2.3.2 Acti vating NodeB PMs (Counters) 1. After selecting NodeB in the Measure Management tab, right-click the list of tables and select Active Measurement, as shown in Figure 8. The Active dialog box is displayed, as shown in Figure 9. 2. Select the tables you want to activate. The following tables must be activated: i.

HSDPA measurements per local cell – 50331648

ii.

Traffic measurements per local cell - 50331650

iii.

IUB measurements per NodeB - 50331649

iv.

HSUPA measurements per local cell - 50331651

3. In the Period area, select 30 Minutes. 4. Click OK, and then select the Measurement Settings tab. 5. Enable all the counters. All counters will be generated every 30 mi nutes and will be stored under the RNC in the following path: /export/home/omc/var/fileint/pm/ Or /export/home/omc/var/fileint/pmneexport

17


4.2.4

Mandatory Counters

In order to run a model or a power optimization, there several mandatory counters. All other counters are for KPI analysis only.

4.2.4.1 Mandatory Counters for Model Optimi zati on Counter Name

Version

Table Name

Counter Number

VS.CellDCHUEs

V200R09,10,11

RRC connection setup measurement

67199662

per cell V900R11,12,13

RRC connection setup measurement

73410490

per cell (RRC.Setup.Cell)

4.2.4.2 Mandatory Counters for Power Optimi zati on Counter Name

Version

Table Name

Counter Number

18

VS.MeanTCP.NonHS

All

Cell TX and RX Power Measurement per cell

67202902

VS.MeanTCP

All


67199618

VS.MinTCP

All


67199683

Ultima Mentor Required Data Inputs for Huawei.pdf

Recommend Documents