Ultima Forte Required Data Inputs For Nokia Infrastructure

Ultima Forte Required Data Inputs for Nokia Infrastructure
Schema Confidential & Proprietary February 2011 Page 1 of 61

Ultima Forte

Required Data Inputs for Nokia
Infrastructure
(for Version 4.0 and above)

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 2011 Schema

Table of Contents
1 Introduction .............................................................................................. 4
2 Required Information and Data ................................................................. 5
2.1 Optimization Area ............................................................................................ 5
2.2 Network Data .................................................................................................. 5
2.2.1 Nokia BSS Network Configuration (Option A XML Format) ........................ 5
2.2.2 Nokia BSS Network Configuration (Option B Queries Format) ................. 11
2.3 Sector Coordinates File ................................................................................... 12
2.4 Mobile Measurements Data Recordings ............................................................. 13
2.4.1 BA List Creation for Data Collection ........................................................ 13
2.4.2 Recording Mobile Measurement Statistics ................................................ 26
2.4.3 Retrieving Mobile Measurements Results................................................. 28
2.4.4 Traffic File ........................................................................................... 29
2.4.5 GPRS/EDGE Traffic File ......................................................................... 30
2.4.6 Retrieving Handover Statistics ............................................................... 30
2.4.7 Retrieving TA data ............................................................................... 31
2.5 Network Performance Statistics ....................................................................... 32
2.5.1 Network Performance Evaluation ........................................................... 33
2.5.2 Radio Network Performance KPI Calculations ........................................... 34
2.5.3 Additional KPI Calculations for Network Performance Evaluation ................ 35
3 Data Collection Checklist ......................................................................... 37
4 Appendix A: Initial Activiation ................................................................ 38
4.1 Initial Activation of the CF Feature ................................................................... 38
4.2 Initial Activation of the DAC Feature ................................................................. 39
4.3 Initial Activation of the RxStatistics Feature ...................................................... 40
5 Appendix B: Step-by-Step 3G Update Implementation ............................ 41
5.1.1 3G Update for NSN Networks ................................................................ 41
5.1.2 3G Update for Ericsson Networks ........................................................... 46
5.1.3 3G Update for Huawei Networks ............................................................ 54

Table of Figures
Figure 1: Retrieval of Required BSS Network Configuration Files ........................................... 6
Figure 2: Available Objects Selection ................................................................................. 7
Figure 3: Object Classes for Export Selection ..................................................................... 7
Figure 4: Export Target File Screen ................................................................................... 8
Figure 5: CM Operations Manager Screen .......................................................................... 9
Figure 6: Export: Actual Configuration Screen .................................................................. 10
Figure 7: Export Target File Screen ................................................................................. 11
Figure 8: CM Plan Manager - Current View - Import .......................................................... 14
Figure 9: Import Target File ........................................................................................... 15
Figure 10: Import Data to New Plan ................................................................................ 16
Figure 11: CM Provisioner Activation ............................................................................... 17
Figure 12: Select a Task for Activation ............................................................................ 18
Figure 13: Select GSM Locking Allowed Feature ................................................................ 18
Figure 14: Confirmation of Activation .............................................................................. 19
Figure 15: Sub Plan Log ................................................................................................ 19
Figure 16: Test Backup Feature ...................................................................................... 20
Figure 17: CM Operations Manager Screen ....................................................................... 21
Figure 18: Empty Import Screen ..................................................................................... 22
Figure 19: Import Source File Screen .............................................................................. 22
Figure 20: Filled in Import Screen ................................................................................... 23
Figure 21: CM Operations Manager - Provisioning ............................................................. 24
Figure 22: Provision-Fix_Me Screen ................................................................................ 25
Figure 23: Plan Verification Screen.................................................................................. 26
Figure 24: CF Recording ................................................................................................ 27
Figure 25: DAC Recording .............................................................................................. 27
Figure 26: CF Feature Activation ..................................................................................... 38
Figure 27: DAC Feature Activation .................................................................................. 39

1 In t r o d u c t io n
This document contains a list of the information and data to be collected for Nokia GSM
infrastructures in order to perform an optimization cycle using Ultima Forte.
The following information is required:
Optimization area and optimization goals
Nokia BSS network configuration data
Sector coordinate data
Mobile measurement recordings
Performance reports
This document not only identifies the required sources of data, but also explains how to obtain
the data.

2 Re q u ir e d In fo r ma t io n a n d Da t a
2. 1 Op t imiza t io n Ar e a
The following information is required to analyze a network:
List of cells in the optimization and surrounding areas (optimization set and guard zone)
Available spectrum for all bands
List of frequencies to be used as BCCH channels
List of frequencies to be used as TCH channels
Current frequency planning strategy (BB,1:1, 1:2, , per site, per cell, ad-hoc, )
Desired optimization strategy (BB, 1:1, 1:2, , per site, per cell, ad-hoc, )
2. 2 Ne t wo r k Da t a
The current methods for retrieving BSS network configuration data are:
CM Plan Manager interface (depending on availability) to XML format.
Predefined set of SQL queries to the CM database in text tab-delimited tables.
The BSS network configuration should be retrieved from each OMCR, relevant to the
optimization area.
2. 2. 1 No kia BS S Ne t wo r k Co n fig u r a t io n (Op t io n A XML
Fo r ma t )
The required BSS network configuration files should be retrieved from the Nokia OSS, which
has the following two software versions:
The CM Plan Manager
The CM Operations Manager (a newer version of Nokia OSS).
The XML export file can be retrieved in the same format from each of these versions.
2.2.1.1 Export with the CM Plan Manager
1. Go to the CM Plan Manager (via Citrix, X-Terminal, or the OSS workstation).
2. Go to ViewExport Actuals or press Ctrl+E.

Figure 1: Retrieval of Required BSS Network Configuration Files
3. Select the BSCs in Available Objects, in the CM Plan Manager, for all cells from the
Forte-defined optimization and guard-zone areas.

Figure 2: Available Objects Selection
4. Click the Select All icon to select all parameters in the Object Classes for Export
section of the CM Plan Manager.

Figure 3: Object Classes for Export Selection
5. Click the Select button to select a location in which to save the XML file.
6. Click the Export button to start the export process.

Figure 4: Export Target File Screen

2.2.1.2 Export with the CM Operations Manager

1. Go to the CM Operations Manager (via Citrix, X-Terminal, or the OSS workstation).
2. Go to FileExport Actual Configuration.
3. Choose the BSCs in Actual Configuration for all cells in the optimization and guard-
zone areas.

Figure 5: CM Operations Manager Screen
1. Click the icon to select all parameters in the Object Classes for Export section.
2. Click "" to select a location in which to save the XML file.
3. Enter a name for the exported file and click OK.
4. Click the Start button to start the export process.

Figure 6: Export: Actual Configuration Screen

Figure 7: Export Target File Screen
2. 2. 2 No kia BS S Ne t wo r k Co n fig u r a t io n (Op t io n B Qu e r ie s
Fo r ma t )
The required BSS network configuration files can be retrieved from the Nokia CM database by
running the Perl script provided by Schema. The generated output will contain a set of text files
with the BSS network configuration. The script automatically generates SQL queries to retrieve
the required data from Nokias Oracle database as follows:
1. Open a binary FTP session in the Nokia OSS machine.
2. Upload the script file NokiaNetConfig.pl to a directory with R/W permissions (chmod
755).
3. Activate the script by using the following command in UNIX:
> perl NokiaNetConfig.pl
4. FTP (in binary mode) the sixteen new text files.
Note: Since the Perl script directly connects to the Oracle database, the user must log in and
provide a password to begin the process.
2. 3 S e c t o r Co o r d in a t e s File
The sector coordinates file should be in tab-delimited text file format, and should include
geographical information for all of the network sectors, including the following columns:
Sector
Latitude
Longitude
Azimuth
LAC (optional)
CI (optional)
Keywords (optional)
The latitude and longitude values should be expressed in decimal-degree format, with up to six
digits following the decimal point.
2. 4 Mo b ile Me a s u r e me n t s Da t a Re c o r d in g s
The following network activities should stop while data is being recorded:
BSC split
Site re-homing (BSC/site relations change)
Changes in LAC and CI
Sector mechanical changes, such as tilt, azimuth, and antenna
The following changes should be made only during maintenance (but not while recording):
TRX additions
Frequency changes (TCH)
Frequency changes (BCCH and BSIC)
Neighbor additions or deletions
Site additions
No other parameters should be changed.
Note: BSC Version S10.5 (or later) should be used.
2. 4. 1 BA Lis t Cr e a t io n fo r Da t a Co lle c t io n
The Defined Adjacent Cell and Channel Finder measurements collect signal strength and C/I
data for mobiles in the MAHO report.
In order to collect information on BCCH channels that are not in the adjacent cell list, a new
BCCH allocation list should be defined to include all BCCHs to be measured. This BA list should
then be assigned to each BTS.
This makes use of The Double BCCH Allocation List feature, which provides the mobile with a
user-defined frequency list for measurements, containing (a) all BCCH frequencies belonging to
defined neighbors and (b) any additional frequencies to be measured. Handover performance is
not affected when this list is generated.
The Forte Measurement Plan, used to collect reliable data for network modeling, and allocates
frequencies to each sector BA list.
The process involved in importing and exporting the Measurement Plan depends upon whether
the CM Plan Manager, the CM Provisioner, or the CM Operations Manager is used.
2.4.1.1 Using the CM Plan Manager to Import MP Export Files in XML Format
Browse to the Forte Nokia Measurement Plan\Day_X MP export directory and import each
file in 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 the Current View to Import as shown in Figure
8.

Figure 8: CM Plan Manager - Current View - Import

2. Browse to the relevant directory, select the XML files to import, and then click OK.

Figure 9: Import Target File
3. Name the plan and click Start.

Figure 10: Import Data to New Plan

2.4.1.2 Using the CM Provisioner to Activate XML
Access the CM Provisioner to activate the imported plan (a process referred to as BA list
rotation).
1. Activate CM Provisioner.

Figure 11: CM Provisioner Activation

2. Select a task for activation.

Figure 12: Select a Task for Activation

3. Select GSM Locking Allowed with a 10-second limit, and click Start Operation.

Figure 13: Select GSM Locking Allowed Feature

4. Click Continue.

Figure 14: Confirmation of Activation
5. The Sub Plan Log is displayed.

Figure 15: Sub Plan Log
6. Successful XML implementation will be terminated when the State: Finished message
is displayed.
7. Important Note: An automatic backup is created when rollbacks are activated.

Figure 16: Test Backup Feature

2.4.1.3 Using the CM Operations Manager to Import and Activate MP Export Files in
XML Format
Browse to the MP export directory of Forte Nokia Measurement Plan\Day_X and import
each file in its own plan (01_Disassociate_BAL.xml, 02_Delete_BAL.xml, 03_Create_BAL.xml,
04_Associate_BAL.xml).

1. Open the CM Operations Manager and select File->Import.

Figure 17: CM Operations Manager Screen

2. Click "" to browse to the relevant directory, select the XML files to import, and then
click OK.

Figure 18: Empty Import Screen

Figure 19: Import Source File Screen
3. Name the plan and click Start.

Figure 20: Filled in Import Screen

4. Return to the Plans tab in the main window of the CM Operations Manager, where the
imported plan will be in the list of plans. Click on the plan once, and then right click
Provision. Provisioning can also be selected by going to PlanProvision.

Figure 21: CM Operations Manager - Provisioning
5. Select GSM Locking Allowed, a GSM forced Handover time limit of 10 seconds, Entire
Plan, and Activate. It is optional to type in the provision name and a description in the
upper left portion of the window.
6. Click Start.

Figure 22: Provision-Fix_Me Screen
7. Verify that the plan is displayed (without errors) in the window showing all planned
objects. A green check mark indicates detail types, while a red X indicates errors.

Figure 23: Plan Verification Screen

2. 4. 2 Re c o r d in g Mo b ile Me a s u r e me n t S t a t is t ic s
CF and DAC recordings should be performed within the same time frame on consecutive
working days. The Appendix contains additional information on the validation of DAC and CF
features.
Use the following MML commands to view criteria currently defined in the BSC for DAC and CF
recordings:
For CF Recording: ZTPI:MEASUR,CHAN_FIN;

Figure 24: CF Recording

For DAC Recording: ZTPI:MEASUR,DAC;

Figure 25: DAC Recording
Use the following MML commands to start/modify the CF, DAC, and RxStatistics recordings:
ZTPM:MEASUR,CHAN_FIN:ALL,09002100,12:DB1=-12,DB2=0 defines CF
measurements, beginning at 09:00 and finishing at 21:00, daily, with a 12-hour resolution.
ZTPS:MEASUR,CHAN_FIN begins the CF measurement.
ZTPM:MEASUR,DAC:ALL,09002100,12:DB1=-12,DB2=0 defines DAC
measurement, beginning at 09:00 and finishing at 21:00, daily, with a 12-hour resolution.
ZTPS:MEASUR,DAC begins the DAC measurement.
ZTPM:MEASUR,RXLEVEL:ALL,09002100,12:RX1=10,RX2=15,RX3=20,RX4=30,RX5=40;
defines the RxStatistics measurement, beginning at 09:00 and finishing at 21:00, daily, with
a 12-hour resolution.
ZTPS: MEASUR,RXLEVEL starts the RxStatistics measurement.

Note: The thresholds for recordings (between Class 1, Class 2, and Class 3 measurements)
should be the same thresholds for all sectors and BSCs in the DAC and CF files.
To change the recording time on the DAC, CHAN_FIN and RXLEVEL, use the following MML
commands: (Example commands for CHAN_FIN)
ZTPI:MEASUR,CHAN_FIN; - CHECK STATUS
ZTPE:MEASUR,CHAN_FIN::; - FORCED TO STOP TO DISABLE AND LOCKED
ZTPM:MESASUR,CHAN_FIN:ALL,18-00-22-00,4:DB1=-12,DB2=0:; - SCHEDULE IT
ZTPS:MEASUR,CHAN_FIN,; - DEFAULT START NOW
Repeat the same for DAC and RXLEVEL measurements, and assure that they are scheduled for
the same time period. Once the measurements are set, the recording will start and end only at
the scheduled time period. However, to continue to record twenty-four hour measurements, the
commands listed above should be used to restore the original recording.
2. 4. 3 Re t r ie vin g Mo b ile Me a s u r e me n t s Re s u lt s
The required mobile measurement results can be retrieved from the Nokia PM database by
running Schemas Perl script. This generated output will include set text files with required
data. The script automatically generates SQL queries for data retrieved from the Nokia Oracle
database:
1. Open a binary FTP session on Nokia OSS.
2. Upload the script file NokiaMS.pl to a directory with R/W permissions (chmod 755).
3. Activate the script by using the >perl NokiaMS.pl command in UNIX.
4. FTP (in binary mode) the three new text files.
Note: Since the Perl script directly connects to the Oracle database, the user must log in and
provide a password to begin the process.
The script generates three files for each recording day:
CF (Channel Finder measurements)
DAC (Defined Adjacent Cell measurements)
RxStatistics (Rxlevel and RxQuality measurements)
The BSS network configuration files must be retrieved for each day of mobile measurement
recordings.

2. 4. 4 Tr a ffic File
The traffic file should be in tab-delimited text file format with traffic information for all sectors
in the optimization and simulation areas (the guard-zone area), and should include the
following columns:
Sector
Traffic (carried traffic in Erlang)
AMR penetration (optional)

Since the Traffic file complies with Schemas format, these columns can be in any order.
The Traffic file should contain information during a three- to four-hour period, including the
network peak hour, for five consecutive working days, and should be generated on the last
recording day.
The required traffic file can be prepared with raw traffic data from the Performance
Management system. This file can be retrieved from the Nokia PM database with an SQL query,
provided by Schema Customer Support.
To retrieve traffic data from the Nokia Oracle database:
1. Open a binary FTP session in Nokia OSS.
2. Upload the traffic.sql file to a directory with R/W permissions.
3. Activate the SQL query, using the following command: sqlplus
username/password@filename (e.g. sqlplus omc/omc @traffic.sql).
4. FTP (in binary mode) the new text file (traffic.txt).
2. 4. 5 GP RS /EDGE Tr a ffic File
The GPRS/EDGE traffic file should be in tab-delimited text file format with information for all
sectors in the optimization and simulation areas (the guard-zone area), and should include the
following columns:
Sector
GPRS Traffic (in Erlang)
EDGE Traffic (in Erlang)
The required traffic file can be prepared with raw traffic data from the Performance
1. Open a binary FTP session in the Nokia OSS.
2. Upload the NokiaDataCounters.sql file to a directory with R/W permissions.
username/password@filename (e.g. sqlplus omc/omc @ NokiaDataCounters.sql).
4. FTP (in binary mode) the new text file (VoiceControlGPRSTraffic.txt and
EDGETraffic.txt).
The output files should be placed under the Model folder and will be identified by Forte during
Model Creation.
2. 4. 6 Re t r ie vin g Ha n d o ve r S t a t is t ic s
Handover statistics for each cell-to-cell relation should be collected for handover optimization.
This data should be aggregated over one week for each cell-to-cell relation, and provided in a
tab-delimited text file with the following fields:
Serving Sector
Target Sector
Handover Attempts

The required handover statistics file can be retrieved from the Nokia PM database, using an SQL
query provided by Schema Customer Support.
To retrieve handover data from the Nokia Oracle database:
2. Upload the ho_adj.sql file to a directory with R/W permissions.
3. Activate the SQL files by using the following command: sqlplus username/password
@filename (e.g. sqlplus omc/omc @ho_adj.sql).
4. FTP (in binary mode) the new text file (ho.txt).
The ho_adj.txt file can be imported directly to Ultima Forte.
2. 4. 7 Re t r ie vin g TA d a t a
The required TA data file can be prepared with raw traffic data from the Performance
2. Upload the traffic.sql file to a directory with R/W permissions.
username/password@filename (e.g. sqlplus omc/omc @ TAquery.sql).
4. FTP (in binary mode) the new text file (ta.txt).
2. 5 Ne t wo r k P e r fo r ma n c e S t a t is t ic s
Network performance statistics should be collected for network traffic modeling and post-
optimization network performance benchmarking.
The following network performance statistics should be collected per cell, and calculated hourly
over seven consecutive days:

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

MSDCCH Traffic:
ave_busy_sdcch, res_av_denom15

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

TCH Assignments (TCH assignment attempts and failures):
tch_norm_seiz, ms_tch_succ_seiz_assign_cmplt, tch_req_rej_lack

TCH Traffic:
ave_busy_tch, res_av_denom14, ave_tch_busy_full, ave_tch_busy_half

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

TCH Rx Quality Performance:
freq_dl_qual0 freq_dl_qual0, freq_ul_qual0 freq_ul_qual0

The following performance statistics should be collected and calculated daily for seven
consecutive days, for each cell relation:

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

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. 5. 1 Ne t wo r k P e r fo r ma n c e Eva lu a t io n
Each KPI improvement rate will be calculated as:
% 100 _ _
=
before
after before
KPI
KPI KPI
rate t improvemen KPI

For the handover success rate the improvement will be calculated as:
% 100
1
_ _

=
before
before after
KPI
KPI KPI
rate t improvemen Success

Each KPI improvement ratio can be calculated separately over a period of five working days
before and after the optimization cycle (during each days network busy hour).
Any network performance KPIs that are not related to the BSS subsystem should be excluded
from the calculation.
2. 5. 2 Ra d io Ne t wo r k P e r fo r ma n c e KP I Ca lc u la t io n s
The following calculations will be used for KPIs that are proposed for the radio network
performance evaluation:
( )
+ +
+ + + +
+ + +
+
=
h bsc_i_sdcc h msc_i_sdcc
_detach sdcch_imsi upd sdcch_loc_ g_call sdcch_emer
_re_est sdcch_call orig succ_seiz_ term succ_seiz_
ld_ho sdcch_rf_o o_fail sdcch_radi
_ _ _ Radio Rate Drop SDCCH

( )
+
=
h_tch msc_o_sdcc - tch bsc_o_tch_ - ch cell_tch_t -
- ign_cmplt c_seiz_ass ms_tch_suc
_ho tch_rf_old fail tch_radio_
_ _ _ Radio Rate Drop TCH

=
) _ho tch_rf_old fail tch_radio_ (
om14 res_av_den
ch ave_busy_t
_ _ _ _ Radio Drop to Erlang TCH

=
=
=
7
0
7
5
alX freq_dl_qu
alX freq_dl_qu
_ _ _
x
x
DL Quality Bad TCH

=
=
=
7
0
7
5
alX freq_ul_qu
alX freq_ul_qu
_ _ _
x
x
UL Quality Bad TCH

=
s_to_adj) ho_fail_re - _adj (ho_att_to
o_adj) (ho_succ_t
_ _ _ Rate Success HO Outgoing
Note: These calculations do not include any drops that may occur due to BSS problems, such
as transmission, BSC, TRAU, or MSC.
2. 5. 3 Ad d it io n a l KP I Ca lc u la t io n s fo r Ne t wo r k P e r fo r ma n c e
Eva lu a t io n
The following calculations provide additional KPIs for network performance evaluation:

=
) _att sdcch_seiz (
) gn sdcch_assi (
_ _ Success Assignment SDCCH

+ +
+ + + +
+ + +

+ +
+ + + +
+ + + +
+ + +
=
h bsc_i_sdcc h msc_i_sdcc
_detach sdcch_imsi upd sdcch_loc_ g_call sdcch_emer
_re_est sdcch_call orig succ_seiz_ term succ_seiz_
_act sdcch_netw _act sdcch_user
_reset sdcch_bcsu fail sdcch_bts_ _fail sdcch_lapd
_fail_old sdcch_a_if _fail_call sdcch_a_if _fail_old sdcch_abis
_fail_call sdcch_abis ld_ho sdcch_rf_o o_fail sdcch_radi
_ _ Rate Drop SDCCH

+ +
+ + + + +
+ + + + +
+ + + +
=
h_tch msc_o_sdcc - tch bsc_o_tch_ - ch cell_tch_t -
- ign_cmplt c_seiz_ass ms_tch_suc
il_call tch_act_fa ct tch_netw_a
reset tch_bcsu_ ct tch_user_a il tch_bts_fa ail tch_lapd_f
il_old tch_tr_fa l tch_tr_fai fail_old tch_a_if_ ail_call tch_a_if_f
ail_old tch_abis_f ail_call tch_abis_f _ho tch_rf_old fail tch_radio_
_ _ Rate Drop TCH

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

=
il_call tch_act_fa ct tch_netw_a reset tch_bcsu_ ct tch_user_a
ail tch_bts_f ail tch_lapd_f il_old tch_tr_fa l tch_tr_fai
fail_old tch_a_if_ ail_call tch_a_if_f ail_old tch_abis_f
ail_call tch_abis_f _ho tch_rf_old fail tch_radio_
om14 res_av_den
ch ave_busy_t
_ _ _ Drop to Erlang TCH

=
om15 res_av_den
dcch ave_busy_s
_Traffic SDCCH

=
om14 res_av_den
ch ave_busy_t
_Traffic TCH

= ) sy_full ave_tch_bu ( _ _ FR Traffic TCH
= ) sy_half ave_tch_bu ( _ _ HR Traffic TCH
+ + +
+ + + +
+ + + + + +
+ + + + + +
+ + + +
=
_CI cause_good CI cause_bad_ distance cause_low_
d_drop cause_fiel emption cause_pre_ retry cause_dir_
fic cause_traf dm cause_ch_a cause_omc t cause_pbdg cause_umbr
er_dwn cause_intf er_up cause_intf invoc cause_msc_ ance cause_dist
_lev cause_down _qual cause_down evel cause_up_l ual cause_up_q
) cause_X (
_ Cause HO

3 Da t a Co lle c t io n Ch e c klis t
SOURCE COMMENTS CHECK
Network Data
BSS Network Configuration
(XML)

(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
(XML)

(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 Ap p e n d ix A: In it ia l Ac t ivia t io n
4. 1 In it ia l Ac t iva t io n o f t h e CF Fe a t u r e
The CF feature should be activated on each BSC to be measured.
First, log in to the BSC, using the following command from the OSS/NMS:
C7xtermx n bsc_name
To verify activation of the CF feature on the BSC, run the following MML command:
ZWOI:10,65;
The printout will show whether or not the CF feature is activated. 00FF means the feature is
activated; 0000 means it is disabled.

Figure 26: CF Feature Activation

Use the following command for CF activation in case it is not active:
ZWOC:10,65,FF;

4. 2 In it ia l Ac t iva t io n o f t h e DAC Fe a t u r e
The DAC feature should be activated on each BSC to be measured.
C7xtermx n bsc_name
To verify activation of the DAC feature on the BSC, run the following MML command:
ZWOS:2,626;
The printout will show whether or not the DAC feature is activated.
When the DAC is activated, its status will be displayed as shown in the figure below.

Figure 27: DAC Feature Activation

Use the following command to activate an inactive DAC:
ZWOA:2,626,A;
4. 3 In it ia l Ac t iva t io n o f t h e RxS t a t is t ic s Fe a t u r e
The RxStatistics feature should be activated on each BSC to be measured.
C7xtermx n bsc_name
To verify activation of the RxStatistics feature on the BSC, run the following MML command:
ZWOI:10,27;
The printout will show whether or not the RxStatistics feature is activated.
Use the following command to activate an inactive RxStatistics feature:
ZWOC:10,27,FF;

5 Ap p e n d ix B: St e p -b y-St e p 3G Upd a t e
Imp le me n t a t io n

5. 1. 1 3G Up d a t e fo r NS N Ne t wo r ks
1. The update will require Netact CM Operations Manager and CM Editor.

IMPORTANT: Modifications to different Network Elements should be implemented
depending on which OSS the 2G cells are located in.
a) If the ADJGs are from one OSS to another (Nokia or another vendor), the modifications
should be made to the Virtual Cells located in the OSS where 3G is (The VCs are under the
BSC-0/BCF-0).

The notation of the VCs is BTS-(LAC+CI) . Where LAC takes 5 spaces, for example:
BTS-91 _ _ _ 2081. The maximum allowed is 10 spaces, 5 for LAC and 5 for the CI.
b) If the ADJGs are from one OSS (3G Network) to the same OSS (2G Network also), the
modifications should be to the 3G Cells.

XML Examples for both cases:
Scenario A:


Scenario B:
The XML Script of option b is the FP generated by Forte (Set_FP.xml).

2. Prepare the XML script with CM Operations Manager.

Important: Do NOT Provision yet! (Uncheck the Provision option), and click Start.
The Prepare Plan Option checks the plan and whether all the ADJx defined for the site are
actualized in the XML plan (if our plan will modify a parameter related to the ADJxs, the CM
will automatically add the XML code in the plan to update the ADJxs)
3. When the plan preparations are finished, open the plan with CM Editor to check if the ADJGs
are correct.

In the above example, the planned and actual values are identical because the plan was
already successfully provisioned. Repeat this step after the Plan Provision finalization to
check if the ADJGs were actualized correctly
4. Open the Plan with CM Editor to check if the ADJGs are ready to actualize.

Now you have the MO ADJGs in your plan.
5. For Scenario A, start the Provision. For Scenario B, if the FP has already been executed in
MML, uncheck the Entire Plan scope and check only the RNCs of your ADJGs. For both
Scenarios, there is no need to prepare the plans again.


5. 1. 2 3G Up d a t e fo r Er ic s s o n Ne t wo r ks
1. Copy Fortes .xml export on the Ericsson UMTS import directory.

2. Go to OSS WCDMA Common Explorer.

3. Create a New Planned Configuration.

The New Planned Configuration dialog box is displayed.

4. Import Fortes UMTS update file (.xml)

A dialog box is displayed enabling you to select the update file to import.

The progress of the import is displayed.

5. Activate the planned configuration.

A dialog box is displayed.

Planned Configuration Activation complete.

6. UMTS Network Update successful

5. 1. 3 3G Up d a t e fo r Hu a we i Ne t wo r ks
1. Connect to the Local Management Terminal (LMT).

2. Execute FOC CMCTRL to obtain the Configuration Control Right.

3. Open the Batch Commands to execute Fortes update file.

4. Open the Forte update file


5. Choose where you will save the output file.

6. Execute Fortes update file.


7. Close the LMT and release the Configuration Control.


Ultima Forte Required Data Inputs For Nokia Infrastructure

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Ultima Forte Required Data Inputs For Nokia Infrastructure

Uploaded by

Copyright:

Available Formats

Ultima Forte Required Data Inputs for Nokia Infrastructure

Schema Confidential & Proprietary February 2011 Page 1 of 61

= ) sy_full ave_tch_bu ( _ _ FR Traffic TCH

= ) sy_half ave_tch_bu ( _ _ HR Traffic TCH

You might also like