3.required data inputs for nokia markets

Ultima Fort Required Data Inputs for Nokia Infrastructure

Ultima Fort

Required Data Inputs for

Nokia Infrastructure

(appropriate for Ultima Fort v3.9)

Copyright Notice Due to a policy of continuous product development and refinement, Schema reserves the right to alter the

specifications and descriptions outlined in this publication without giving prior notice of any kind. In addition, no part of this publication, taken as a whole or separately, shall be deemed to be part of any contract for

equipment or services.

Schema retains the sole proprietary rights to all information contained in this document. No part of this publication may be reproduced, stored in a retrieval system, transmitted in any form or by any means,

including but not limited to: electronic, mechanical, magnetic, photocopy, recording, or otherwise, in use now or in the future, without prior written consent from Schema.

Copyright 2007, Schema

Schema Confidential & Proprietary page 1 of 22


Table of Contents

1 Introduction..........................................................................................................3 2 Required Information and Data.............................................................................3

2.1 Optimization Goals and Areas.............................................................................3 2.2 Network Data ..................................................................................................4

2.2.1 Nokia BSS Network Configuration (Option A XML Format) .............................4 2.2.2 Nokia BSS Network Configuration (Option B Queries Format) ........................6 2.2.3 Sector Coordinates File ...............................................................................7 2.2.4 Traffic File ................................................................................................7

2.3 Mobile Measurements Data Recordings ................................................................8 2.3.1 BA List Creation for Data Collection ..............................................................8

2.3.1.1 Importing MP Export Files in XML Format................................................9 2.3.1.2 Activation of the XML CM Provisioner.................................................10

2.3.2 CF and DAC Recordings ............................................................................13 2.3.3 Retrieving Mobile Measurements Results .....................................................14 2.3.4 Retrieving Handover Statistics ...................................................................15

2.4 Network Performance Statistics ........................................................................16 2.4.1 Network Performance Evaluation................................................................17 2.4.2 Radio Network Performance KPIs Calculation...............................................17 2.4.3 Additional KPIs for Network Performance Evaluation.....................................18

3 Data Collection Checklist.....................................................................................20 4 Appendix.............................................................................................................21

4.1 Initial Activation of the CF feature.....................................................................21 4.2 Initial Activation of the DAC feature ..................................................................22

List of Figures Figure 1: Retrieve the Required BSS Network Configuration Files........................................................4 Figure 2: Choosing the BSCs ........................................................................................................5 Figure 3: Object Classes for Export ................................................................................................5 Figure 4: Export Target File...........................................................................................................6 Figure 5: Open the CM Plan Manager and Change Current View to Import............................................9 Figure 6: Import Target File ..........................................................................................................9 Figure 7: Import Data to New Plan ............................................................................................... 10 Figure 8: Activating the CM Provisioner......................................................................................... 10 Figure 9: Selecting Task for Activation.......................................................................................... 11 Figure 10: Select GSM Locking Allowed Feature ............................................................................. 11 Figure 11: Prompt to Activate the Operation.................................................................................. 11 Figure 12: Subplan Log .............................................................................................................. 12 Figure 13: Test Backup Feature ................................................................................................... 13 Figure 14: CF Recording ............................................................................................................. 13 Figure 15: DAC Recording........................................................................................................... 14 Figure 16: CF Feature Activated................................................................................................... 21 Figure 17: DAC Feature Activated ................................................................................................ 22



1 Introduction This document contains a list of all the required information and data that must be collected on Nokia GSM infrastructures in preparation for installation of Ultima Fort.

Required information and data include the following:

o Optimization area and optimization goals

o Nokia BSS network configuration data (XML format or SQL queries format)

o Sector coordinates data

o Mobile measurements recordings

o Performance reports

The following sections provide a more in-depth description of the required data sources and the manner in which they can be obtained.

2 Required Information and Data

2.1 Optimization Goals and Areas 1. Optimization goal/s - a general description of the optimization goals for the intended area is

required.

2. Network area:

o List of cells in the optimization area

o List of frequencies to be used as BCCH channels

o List of frequencies to be used as TCH channels

o Current frequency planning strategy (1:1, 1:2, , per site, per cell, ad-hoc, )

o Desired optimization strategy (1:1, 1:2, , per site, per cell, ad-hoc, )

o List of cells in the guard zone



2.2 Network Data

There are two possible methods for BSS network configuration data retrieval:

1. CM Plan Manager interface (depends on availability) to XML format.

2. Predefined set of SQL queries to CM database to text tab delimited tables.

BSS network configuration should be retrieved from each OMCR relevant to the optimization area.

2.2.1 Nokia BSS Network Configuration (Option A XML Format)

To retrieve the required BSS network configuration files from the Nokia OSS

1. Go to the CM Plan Manager (usually via Citirix, X-Terminal or OSS workstation)

2. Go to View Export Actuals or Ctrl+E (see figure 1 below)

Figure 1: Retrieve the Required BSS Network Configuration Files



3. Choose the BSCs in Available Objects for all cells in the optimization and guard-zone areas. See figure 2 below.

Figure 2: Choosing the BSCs

4. In the Object Classes for Export section, click the Select All icon to select all parameters.

Figure 3: Object Classes for Export



5. Click Select (figure 3 above) to select the location to save the XML file.

Figure 4: Export Target File

6. Use the Export button to start the export process.

2.2.2 Nokia BSS Network Configuration (Option B Queries Format)

The required BSS network configuration files can be retrieved from the Nokia CM database through running Perl script provided by Schema. This generated output will contain set text files with the BSS network configuration. The script automatically generates SQL queries for retrieval of the required data from Nokias Oracle database as follows:

1. Open a binary FTP session to the Nokia OSS machine.

2. Upload the script file NokiaNetConfig.pl to a directory with R/W permissions.

3. Activate the script by using the following command in Unix:

> perl NokiaNetConfig.pl

4. FTP (in binary mode) the 10 newly created text files.

Note: the Perl script uses a direct connection to the Oracle database. The user will be asked to login and provide a password on starting the process.



2.2.3 Sector Coordinates File

The sector coordinates file must be in tab delimited text file format with geographical information for all the sectors in the optimization area and the guard-zone area.

The file should contain the following columns:

o Sector

o Latitude

o Longitude

o Azimuth

The sector name is supposed to be unique per network.

2.2.4 Traffic File

The traffic file should be in the format of a tab delimited text file with traffic information for all the sectors in the optimization area and the guard-zone area.

The file should contain the following columns:

o Date (in ddmmyyy format)

o Hour (in hh format)

o Sector

o Traffic (carried traffic in Erlang)

The file should contain traffic information for 5 consecutive working days and should preferably be produced on the last day of the DAC and CF recordings.

The traffic file can be retrieved from the Nokia PM database by using an SQL query. The required SQL query can be provided by Schema Customer Support. In order to retrieve the traffic data from the Nokia Oracle database, use the following procedure:


2. Upload the traffic.sql file to a directory with R/W permissions.

3. Activate the SQL query by using the following command:

sqlplus username/password @filename (e.g. sqlplus omc/omc @traffic.sql)

4. FTP (in binary mode) the newly created text file (traffic.txt).



2.3 Mobile Measurements Data Recordings

A network freeze is strongly recommended during the recording time frame.

The following activities should be halted during data recordings:

o BSC split

o Site reparenting (BSC/site relations change)

o Changes of LAC and CI

o Site additions

o Sector mechanical changes such as tilt, azimuth and antenna changes

o Frequency changes (BCCH and BSIC)

o Neighbor additions or deletions

The following changes should be performed only during the maintenance window (not while recording is taking place):

o TRX additions

o Frequency changes (TCH)

All other parameters should not be changed.

Note: Version of BSC must be S10.5 or later.

2.3.1 BA List Creation for Data Collection

The Defined Adjacent Cell and Channel Finder measurements collect signal strength and C/I data that are reported by the mobiles in the MAHO report.

In order to collect information on BCCH channels that are not in the adjacent cell list, it is necessary to define a new BCCH allocation list, which contains all BCCHs that should be measured, and assign this BA list for each BTS.

This makes use of the Double BCCH Allocation List feature. This feature provides the mobile the user-defined frequency list for measurements. This user-defined list should contain all BCCH frequencies that belong to the defined neighbors and additional frequencies that should be measured. This will have no impact on handover performance.

The Ultima Fort Measurement Plan functionality should be used for the collection of reliable data for network modeling. The Measurement Plan functionality provides frequency allocation for each sector BA list.



2.3.1.1 Importing MP Export Files in XML Format

Browse to the MP export directory of UltimaFortNokia Measurement Plan\Day_X and import (using the CM Plan Manager) one after another all 4 files. Each file should be imported into its own plan (01_Disassociate_BAL.xml, 02_Delete_BAL.xml, 03_Create_BAL.xml, 04_Associate_BAL.xml).

1. Open the CM Plan Manager and change Current View to Import as shown in figure 5 below.

Figure 5: Open the CM Plan Manager and Change Current View to Import

2. Browse to the proper directory and select the .xml files to import.

Figure 6: Import Target File



3. Name your plan and click on Start.

Figure 7: Import Data to New Plan

2.3.1.2 Activation of the XML CM Provisioner

In order to activate the plan you have imported (the BA list rotation) access the Provisioner and activate it.

1. Activate CM Provisioner.

Figure 8: Activating the CM Provisioner



2. Select the proper task which you want to activate.

Figure 9: Selecting Task for Activation

3. Select GSM Locking Allowed with 10sec limit and click on Start Operation.

Figure 10: Select GSM Locking Allowed Feature

4. Click on Continue.

Figure 11: Prompt to Activate the Operation



5. The Subplan Log will appear.

Figure 12: Subplan Log

6. XML successful implementation will be terminated when the State: Finished message appears.

7. IMPORTANT NOTE: In order to roll back, an automatic back up is created and can be activated if necessary. See figure 13 below.



Figure 13: Test Backup Feature

2.3.2 CF and DAC Recordings

CF and DAC recordings should be performed over consecutive working days for the same time frame. The validation of DAC and CF features status is mentioned in the Appendix.

Use the following MML commands to view the criteria currently defined in the BSC for DAC and CF recordings:

For CF: ZTPI:MEASUR,CHAN_FIN

Figure 14: CF Recording



For DAC: ZTPI:MEASUR,DAC

Figure 15: DAC Recording

Use the following MML commands to start/modify the CF and DAC recordings:

1. ZTPM:MEASUR,CHAN_FIN:ALL,09002100,4:DB1=-12,DB2=0; - defines CF measurements to start at 09:00 and finish at 21:00 daily with 4 hours resolution.

2. ZTPS:MEASUR,CHAN_FIN; - starts the CF measurement.

3. ZTPM:MEASUR,DAC:ALL,09002100,4:DB1=-12,DB2=0; - defines the DAC measurement to start at 09:00 and finish at 21:00 daily with 4 hours resolution.

4. ZTPS:MEASUR,DAC; - starts the measurement.

Note: The thresholds used for recordings (between class 1, class 2 and class 3 measurements) should be the same thresholds to all sectors and BSCs in the DAC and CF files!

2.3.3 Retrieving Mobile Measurements Results

The required mobile measurements results can be retrieved from the Nokia PM database by running Perl script provided by Schema. This generated output will contain set text files with required data. The script automatically generates SQL queries for the data retrieval from the Nokias Oracle database:


2. Upload the script file NokiaMS.pl to a directory with R/W permissions.

3. Activate the script by using the following command in Unix: >perl NokiaMS.pl

4. FTP (in binary mode) the 3 newly created text files.



Note: the Perl script uses a direct connection to the Oracle database. The user will be asked to login and provide a password on starting the process.

The script will generate 3 files for each recording day:

o CF (Channel Finder measurements)

o DAC (Defined Adjacent Cell measurements)

o Rx Statistics (Rxlevel and RxQuality measurements)

The BSS network configuration files must be retrieved per each day of the mobile measurements recordings as described in section 2.2 above.

2.3.4 Retrieving Handover Statistics

For handover optimization purposes the handover statistics per cell-to-cell relation should be collected. The data should be aggregated over one week and provided in a tab delimited text file with the following fields:

o Serving Sector

o Target Sector

o Handover (HO) Attempts

The required handover statistics file can be retrieved from the Nokia PM database by using an SQL query. The required SQL query will be provided by Schema Customer Support. In order to retrieve handover data from the Nokia Oracle database, use the following procedure:


9. Upload the ho_adj.sql file to a directory with R/W permissions.

10. Activate the SQL files by using the following command: sqlplus username/password @filename (e.g. sqlplus omc/omc @ho_adj.sql)

11. FTP (in binary mode) the newly created text file (ho.txt).

The created ho_adj.txt file can be imported directly to Ultima Fort.



2.4 Network Performance Statistics

Network performance statistics should be collected for the purpose of network traffic modeling and post-optimization network performance benchmarking.

The following performance statistics should be collected on a per cell basis with hourly resolution over 7 consecutive days:

o SDCCH Assignments (immediate assignment attempts and failures):

sdcch_assign, t3101_expired, sdcch_req, sdcch_seiz_att, sdcch_ho_seiz, setup_succ, call_setup_failure, succ_seiz_term, succ_seiz_orig, sdcch_loc_upd, succ_emerg_call, sdcch_call_re_est, imsi_detach_sdcch, msc_i_sdcch, bsc_i_sdcch

o MSDCCH Traffic:

ave_busy_sdcch, res_av_denom15

o SDCCH Performance (drop, drop reason):

sdcch_radio_fail, sdcch_rf_old_ho, sdcch_abis_fail_call, sdcch_abis_fail_old, sdcch_a_if_fail_call, sdcch_a_if_fail_old, sdcch_lapd_fail, sdcch_bts_fail, sdcch_bcsu_reset, sdcch_user_act, sdcch_netw_act

o TCH Assignments (TCH assignment attempts and failures):

tch_norm_seiz, ms_tch_succ_seiz_assign_cmplt, tch_req_rej_lack

o TCH Traffic:

ave_busy_tch, res_av_denom14, ave_tch_busy_full, ave_tch_busy_half

o TCH Performance (drop, drop reason):

tch_radio_fail, tch_rf_old_ho, tch_abis_fail_call, tch_abis_fail_old, tch_a_if_fail_call, tch_a_if_fail_old, tch_tr_fail, tch_tr_fail_old, tch_lapd_fail, tch_bts_fail, tch_user_act, tch_bcsu_reset, tch_netw_act, tch_act_fail_call

o TCH Rx Quality Performance:

freq_dl_qual0 freq_dl_qual0, freq_ul_qual0 freq_ul_qual0

The following performance statistics should be collected on a per cell (cell relation) basis with daily resolution over 7 consecutive days.

o HO Performance (cell relation):

ho_att_to_adj, ho_succ_to_adj, ho_fail_res_to_adj, ho_att_from_adj, ho_succ_from_adj, ho_fail_res_from_adj



o HO Performance (cell):

cell_tch_tch, bsc_o_tch_tch, msc_o_sdcch_tch cause_up_qual, cause_up_level, cause_down_qual, cause_down_lev, cause_distance, cause_msc_invoc, cause_intfer_up, cause_intfer_dwn, cause_umbr, cause_pbdgt, cause_omc, cause_ch_adm, cause_traffic, cause_dir_retry, cause_pre_emption, cause_field_drop, cause_low_distance, cause_bad_ci, cause_good_ci

2.4.1 Network Performance Evaluation

Each KPI improvement rate will be calculated as:

%100__

=before

newbefore

KPIKPIKPI

ratetimprovemenKPI

For success rate KPIs (SDCCH/TCH Setup, HO) the improvement will be calculated as:

%1001

___

=

before

newbefore

KPIKPIKPI

ratetimprovemenSuccessKPI

Each KPI will be calculated for improvement rates separately over working 5 days (24 hours or a selected hours range) before and after optimization. Network performance KPIs that are not related to the BSS subsystem will be excluded from the calculation.

2.4.2 Radio Network Performance KPIs Calculation

The following calculations will be used for KPIs proposed for radio network performance evaluation:

( )

++++++

+++

+=

hbsc_i_sdcchmsc_i_sdcc_detachsdcch_imsiupdsdcch_loc_g_callsdcch_emer

_re_estsdcch_callorigsucc_seiz_termsucc_seiz_ld_hosdcch_rf_oo_failsdcch_radi

___ RadioRateDropSDCCH

( )

+=

h_tchmsc_o_sdcc-tchbsc_o_tch_-chcell_tch_t--ign_cmpltc_seiz_assms_tch_suc

_hotch_rf_oldfailtch_radio____ RadioRateDropTCH



+

=)_hotch_rf_oldfailtch_radio_(

om14res_av_denchave_busy_t

____ RadioDroptoErlangTCH

=

== 7

0

7

5

alXfreq_dl_qu

alXfreq_dl_qu___

x

xDLQualityBadTCH

=

== 7

0

7

5

alXfreq_ul_qu

alXfreq_ul_qu___

x

xULQualityBadTCH

=

s_to_adj)ho_fail_re -_adj(ho_att_too_adj)(ho_succ_t

___ RateSuccessHOOutgoing

Notes:

The calculations mentioned above do not include drops that occur due to BSS problems such as transmission, BSC, TRAU, MSC.

2.4.3 Additional KPIs for Network Performance Evaluation

The following calculations provide additional KPIs for network performance evaluation:

=

)_attsdcch_seiz()gnsdcch_assi(

__ SuccessAssignmentSDCCH



++++++

+++

++++++

+++++++

=

hbsc_i_sdcchmsc_i_sdcc_detachsdcch_imsiupdsdcch_loc_g_callsdcch_emer

_re_estsdcch_callorigsucc_seiz_termsucc_seiz__actsdcch_netw_actsdcch_user

_resetsdcch_bcsufailsdcch_bts__failsdcch_lapd_fail_oldsdcch_a_if_fail_callsdcch_a_if_fail_oldsdcch_abis

_fail_callsdcch_abisld_hosdcch_rf_oo_failsdcch_radi

__ RateDropSDCCH

+++++++

+++++++++

=

h_tchmsc_o_sdcc-tchbsc_o_tch_-chcell_tch_t--ign_cmpltc_seiz_assms_tch_suc

il_calltch_act_facttch_netw_areset tch_bcsu_cttch_user_ailtch_bts_fa ailtch_lapd_f

il_old tch_tr_faltch_tr_faifail_old tch_a_if_ail_calltch_a_if_fail_oldtch_abis_fail_calltch_abis_f_hotch_rf_oldfailtch_radio_

__ RateDropTCH

++++++++++

+++

=

il_calltch_act_facttch_netw_areset tch_bcsu_cttch_user_aail tch_bts_failtch_lapd_fil_old tch_tr_faltch_tr_fai

fail_old tch_a_if_ail_calltch_a_if_fail_oldtch_abis_fail_calltch_abis_f_hotch_rf_oldfailtch_radio_

om14res_av_denchave_busy_t

___ DroptoErlangTCH

=

om15res_av_dendcchave_busy_s_ TrafficSDCCH

=

om14res_av_denchave_busy_t_ TrafficTCH

= )sy_fullave_tch_bu(__ FRTrafficTCH

= )sy_halfave_tch_bu(__ HRTrafficTCH

+++++++

++++++++++++

++++=

_CIcause_goodCIcause_bad_distancecause_low_d_dropcause_fielemptioncause_pre_retrycause_dir_

ficcause_trafdmcause_ch_acause_omctcause_pbdgcause_umbrer_dwncause_intfer_upcause_intfinvoccause_msc_ancecause_dist_levcause_down_qualcause_downevelcause_up_lualcause_up_q

)cause_X(_ CauseHO



3 Data Collection Checklist SOURCE COMMENTS CHECK

Network Data

BSS Network Configuration (XML)

BSS Network Configuration (SQL)

Sector Coordinates File

Traffic File

Mobile Measurements Recordings

Day 1 Day 2 Day 3 Day 4 Day 5

CF Files

DAC Files

RxStatistics Files

BSS Network Configuration (XML)

BSS Network Configuration (SQL)

Network Performance Statistics

SDCCH Assignments Immediate assignments attempts Immediate assignments failures

SDCCH Traffic SDCCH traffic per cell SDCCH congestion

SDCCH Performance SDCCH drop SDCCH drop reason

TCH Assignments TCH assignment attempts TCH assignment failures

TCH Traffic Traffic per cell Traffic FR/HR

TCH Performance Drops Drops per reason

TCH Rx Quality Rx Quality DL Rx Quality UL

Handover (HO) Performance per Cell Relation

HO attempts HO success

HO Performance per Cell HO types HO reasons



4 Appendix

4.1 Initial Activation of the CF feature The first step is to log into the BSC. The CF feature should be activated on each BSC to be measured.

Use the following command from the OSS/NMS to login to a BSC:

C7xtermx n bsc_name

In order to verify that the CF feature is activated on the BSC perform the following MML command:

ZWOI:10,65

The printout will show whether the CF feature is activated or not. 00FF means the feature is activated (as displayed in figure 16 below), while 0000 means it is disabled.

Figure 16: CF Feature Activated

Use the following command for CF activation in case it is not active:

ZWOC:10,65,FF



4.2 Initial Activation of the DAC feature

The first step is to log into the BSC. The DAC feature should be activated on each BSC to be measured.

Use the following command from the OSS/NMS to login to a BSC:

C7xtermx n bsc_name

In order to verify that the DAC feature is activated on BSC, perform the following MML command:

ZWOS:2,626

The printout will show whether the DAC feature is activated or not.

When the Activation Status equals to Activated, the DAC feature is activated as in figure 17 below.

Figure 17: DAC Feature Activated

Use the following command for DAC activation in case it is not active:

ZWOA:2,626,A


IntroductionThis document contains a list of all the required informatioRequired information and data include the following:Optimization area and optimization goalsNokia BSS network configuration data (XML format or SQL querSector coordinates dataMobile measurements recordingsPerformance reportsThe following sections provide a more in-depth description oRequired Information and DataOptimization Goals and Areas

Optimization goal/s - a general description of the optimizatNetwork area:List of cells in the optimization areaList of frequencies to be used as BCCH channelsList of frequencies to be used as TCH channelsCurrent frequency planning strategy (1:1, 1:2, , per site, Desired optimization strategy (1:1, 1:2, , per site, per ceList of cells in the guard zoneNetwork Data

There are two possible methods for BSS network configurationCM Plan Manager interface (depends on availability) to XML fPredefined set of SQL queries to CM database to text tab delBSS network configuration should be retrieved from each OMCRNokia BSS Network Configuration (Option A XML Format)

To retrieve the required BSS network configuration files froGo to the CM Plan Manager (usually via Citirix, X-Terminal oGo to View(Export Actuals or Ctrl+E (see figure 1 below)3. Choose the BSCs in Available Objects for all cells in th4. In the Object Classes for Export section, click the SelecUse the Export button to start the export process.Nokia BSS Network Configuration (Option B Queries Format)

The required BSS network configuration files can be retrieveOpen a binary FTP session to the Nokia OSS machine.Upload the script file NokiaNetConfig.pl to a directory withActivate the script by using the following command in Unix:> perl NokiaNetConfig.plFTP (in binary mode) the 10 newly created text files.Note: the Perl script uses a direct connection to the OracleSector Coordinates File

The sector coordinates file must be in tab delimited text fiThe file should contain the following columns:SectorLatitudeLongitudeAzimuthThe sector name is supposed to be unique per network.Traffic File

The traffic file should be in the format of a tab delimited The file should contain the following columns:Date (in ddmmyyy format)Hour (in hh format)SectorTraffic (carried traffic in Erlang)The file should contain traffic information for 5 consecutivThe traffic file can be retrieved from the Nokia PM databaseOpen a binary FTP session to the Nokia OSS machine.Upload the traffic.sql file to a directory with R/W permissiActivate the SQL query by using the following command:sqlplus username/password @filename (e.g. sqlplus omc/omc @tFTP (in binary mode) the newly created text file (traffic.txMobile Measurements Data Recordings

A network freeze is strongly recommended during the recordinThe following activities should be halted during data recordBSC splitSite reparenting (BSC/site relations change)Changes of LAC and CISite additionsSector mechanical changes such as tilt, azimuth and antenna Frequency changes (BCCH and BSIC)Neighbor additions or deletionsThe following changes should be performed only during the maTRX additionsFrequency changes (TCH)All other parameters should not be changed.Note: Version of BSC must be S10.5 or later.BA List Creation for Data Collection

The Defined Adjacent Cell and Channel Finder measurements coIn order to collect information on BCCH channels that are noThis makes use of the Double BCCH Allocation List feature. TThe Ultima Fort Measurement Plan functionality should be uImporting MP Export Files in XML Format

Browse to the MP export directory of UltimaFortNokia MeasurOpen the CM Plan Manager and change Current View to Import aBrowse to the proper directory and select the .xml files to Name your plan and click on Start.Activation of the XML CM Provisioner

In order to activate the plan you have imported (the BA listActivate CM Provisioner.Select the proper task which you want to activate.Select GSM Locking Allowed with 10sec limit and click on StaClick on Continue.The Subplan Log will appear.XML successful implementation will be terminated when the StIMPORTANT NOTE: In order to roll back, an automatic back up CF and DAC Recordings

CF and DAC recordings should be performed over consecutive wUse the following MML commands to view the criteria currentlFor CF: ZTPI:MEASUR,CHAN_FINFor DAC: ZTPI:MEASUR,DACUse the following MML commands to start/modify the CF and DAZTPM:MEASUR,CHAN_FIN:ALL,09002100,4:DB1=-12,DB2=0; - defiZTPS:MEASUR,CHAN_FIN; - starts the CF measurement.ZTPM:MEASUR,DAC:ALL,09002100,4:DB1=-12,DB2=0; - defines tZTPS:MEASUR,DAC; - starts the measurement.Note: The thresholds used for recordings (between class 1, cRetrieving Mobile Measurements Results

The required mobile measurements results can be retrieved frOpen a binary FTP session to the Nokia OSS machine.Upload the script file NokiaMS.pl to a directory with R/W peActivate the script by using the following command in Unix: FTP (in binary mode) the 3 newly created text files.Note: the Perl script uses a direct connection to the OracleThe script will generate 3 files for each recording day:CF (Channel Finder measurements)DAC (Defined Adjacent Cell measurements)Rx Statistics (Rxlevel and RxQuality measurements)The BSS network configuration files must be retrieved per eaRetrieving Handover Statistics

For handover optimization purposes the handover statistics pServing SectorTarget SectorHandover (HO) AttemptsThe required handover statistics file can be retrieved from Open a binary FTP session to the Nokia OSS machine.Upload the ho_adj.sql file to a directory with R/W permissioActivate the SQL files by using the following command:sqlplus username/password @filename (e.g. sqlplus omc/omc @FTP (in binary mode) the newly created text file (ho.txt).The created ho_adj.txt file can be imported directly to UltiNetwork Performance Statistics

Network performance statistics should be collected for the pThe following performance statistics should be collected on SDCCH Assignments (immediate assignment attempts and failuresdcch_assign, t3101_expired, sdcch_req, sdcch_seiz_att, sdccMSDCCH Traffic:ave_busy_sdcch, res_av_denom15SDCCH Performance (drop, drop reason):sdcch_radio_fail, sdcch_rf_old_ho, sdcch_abis_fail_call, sdcTCH Assignments (TCH assignment attempts and failures):tch_norm_seiz, ms_tch_succ_seiz_assign_cmplt, tch_req_rej_laTCH Traffic:ave_busy_tch, res_av_denom14, ave_tch_busy_full, ave_tch_busTCH Performance (drop, drop reason):tch_radio_fail, tch_rf_old_ho, tch_abis_fail_call, tch_abis_TCH Rx Quality Performance:freq_dl_qual0 freq_dl_qual0, freq_ul_qual0 freq_ul_qual0The following performance statistics should be collected on HO Performance (cell relation):ho_att_to_adj, ho_succ_to_adj, ho_fail_res_to_adj, ho_att_frHO Performance (cell):cell_tch_tch, bsc_o_tch_tch, msc_o_sdcch_tchcause_up_qual, Network Performance Evaluation

Each KPI improvement rate will be calculated as:For success rate KPIs (SDCCH/TCH Setup, HO) the improvement Each KPI will be calculated for improvement rates separatelyRadio Network Performance KPIs Calculation

The following calculations will be used for KPIs proposed fNotes:The calculations mentioned above do not include drops that oAdditional KPIs for Network Performance Evaluation

The following calculations provide additional KPIs for netwData Collection ChecklistSOURCECOMMENTSCHECKNetwork DataBSS Network Configuration (XML)BSS Network Configuration (SQL)Sector Coordinates FileTraffic FileMobile Measurements RecordingsDay 1Day 2Day 3Day 4Day 5CF FilesDAC FilesRxStatistics FilesBSS Network Configuration (XML)BSS Network Configuration (SQL)Network Performance StatisticsSDCCH AssignmentsSDCCH TrafficSDCCH PerformanceTCH AssignmentsTCH TrafficTCH PerformanceTCH Rx QualityHandover (HO) Performance per Cell RelationHO Performance per CellHHAppendixInitial Activation of the CF feature

The first step is to log into the BSC. The CF feature shouldUse the following command from the OSS/NMS to login to a BSCC7xtermx n bsc_nameIn order to verify that the CF feature is activated on the BZWOI:10,65The printout will show whether the CF feature is activated oUse the following command for CF activation in case it is noZWOC:10,65,FFInitial Activation of the DAC feature

The first step is to log into the BSC. The DAC feature shoulUse the following command from the OSS/NMS to login to a BSCC7xtermx n bsc_nameIn order to verify that the DAC feature is activated on BSC,ZWOS:2,626The printout will show whether the DAC feature is activated When the Activation Status equals to Activated, the DAC featUse the following command for DAC activation in case it is nZWOA:2,626,A

3.required data inputs for nokia markets

Documents

network data

data inputs

network performance

network performance

data collection checklist

ultima fort v3

xml format

copyright notice