Ultima Fort Required Data Inputs for Motorola Infrastructure

Ultima Fort
Required Data Inputs
for

Motorola 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 24

Ultima Fort Required Data Inputs for Motorola Infrastructure

Table of Contents
1
Introduction.......................................................................................................... 3
1.1 Definitions, Acronyms and Abbreviations ....................................................................3
2
Required Information and Data............................................................................. 4
2.1 Optimization Area and Goals.....................................................................................4
2.2 Network Data .........................................................................................................4
2.2.1 Motorola BSS Network Configuration ........................................................................4
2.2.2 Sector Coordinates File ..........................................................................................5
2.3 Mobile Measurements Data Collection ........................................................................6
2.3.1 Motorola CPT Recordings ........................................................................................6
2.3.2 Traffic Data ........................................................................................................ 12
2.3.3 RxQual Data ....................................................................................................... 12
2.3.4 BSC Index Data .................................................................................................. 15
2.4 Network Performance Statistics............................................................................... 18
2.4.1 Network Performance Evaluation ........................................................................... 18
2.4.2 Radio Network Performance KPIs Calculation .......................................................... 19
2.4.3 Additional KPIs for Network Performance Evaluation................................................. 20
2.4.4 Collecting KPI Data.............................................................................................. 21
3
Data Collection Checklist..................................................................................... 22
4
Appendix A Switch Dump Script Example......................................................... 23
5
Appendix B Move Script Example ..................................................................... 23
6
Appendix C Trace Call Command ...................................................................... 24

List of Figures
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure

1: BSS Configuration Dump Retrieval through Telnet............................................................... 5

2: Checking the Limit of Trace Files ...................................................................................... 7
3: Changing the Variable Limit = 100000 ............................................................................. 8
4: Copying File to Directory ................................................................................................. 9
5: Type from Outside chmod 777 Directory .......................................................................... 9
6: Verify That rwxrwxr Exists for All Files and Folders ............................................................ 9
7: Type to See Scheduled Cron Commands.......................................................................... 10
8: Scheduled Cron Commands ........................................................................................... 10
9: Crontab-r.................................................................................................................... 11
10: Can't Open the Crontab File ......................................................................................... 11
11: Checking Operating System Version Type ...................................................................... 11
12: Log Files Analysis ....................................................................................................... 12
13: Performance Management Window................................................................................ 13
14: Report Template Window............................................................................................. 13
15: Selecting the Appropriate Items ................................................................................... 14
16: Activating the RxQual Data Collection Process................................................................. 15
17: Click on the Config Mgt Icon ....................................................................................... 15
18: Expanding the BSS Menu............................................................................................. 16
19: BSS Monitor Window................................................................................................... 16
20: BSS Window .............................................................................................................. 17
21: Collecting KPI Data ..................................................................................................... 21

Schema Confidential & Proprietary

page 2 of 24

Ultima Fort Required Data Inputs for Motorola Infrastructure

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

Optimization area and optimization goals

Motorola BSS network configuration data

Sector coordinates file

Motorola CTR recordings

Traffic data

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

1.1 Definitions, Acronyms and Abbreviations

The following terms are used throughout this document:
o

CPT Call Path Trace

BSSCD BSS Configuration Dump

BH Busy Hour

RTF Radio Transceiver Function equivalent to TRX

LCF Link Control Function controls links in and out of BSC

MP Measurement Plan

HO - Handover

BQ Bad Quality

KPI Key Performance Indicator

PERL - Interpreted language optimized for string manipulation and used on UNIX
machines

Schema Confidential & Proprietary

page 3 of 24

Ultima Fort Required Data Inputs for Motorola Infrastructure

2 Required Information and Data

2.1 Optimization Area and Goals
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 and surrounding areas

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

List of cells in the guard zone (if any)

2.2 Network Data

2.2.1

Motorola BSS Network Configuration

The required BSS Network Configuration Dump files are retrieved by executing command script for
each BSC on each OMCR. The command script generates a complete set of files required for BSS
configuration handling. Multiple BSS configuration dumps can be retrieved simultaneously. This
process can take up to 2-3 hours per BSC.
Schema provides required PERL script for BSS configuration dump retrieval. The script name is
MotorolaBSSDump.pl. The tables created include the BSC name and number in the filename as
well as the set creation date as described below:
o

BSS list of sites and LAC/CI in each site (this file is used as the source for all the following
files)

CELL parameters per cell

NEIGHBORS neighbor information per cell

EQUIPMENT RTF information per TRX

RTF lists the RTFs per cell (this file is not needed for import purposes but is used for
EQUIPMENT table retrieval)

LCF lists the sites per LCF

Schema Confidential & Proprietary

page 4 of 24

Ultima Fort Required Data Inputs for Motorola Infrastructure

OPTIONS lists all the features that have unrestricted use (this file is not required for any
of the UltimaFort processes, but may provide useful information about the active
features in the network).

1. BSS configuration dump data will automatically be collected at the beginning of each day
without any special user intervention when the Measurement Plan provided by Ultima Fort is
activated.
2. The following command should be performed in order to retrieve the required BSS configuration
data for a specific BSC:
perl MotorolaSwitchDump.pl <BSC_NAME> <OUTPUT_DIR>
where:
o

<BSC_NAME> is the complete BSC name, example: BSC07_ABC

<OUTPUT_DIR> is the directory to which the output files will be dumped (this directory
will be created if it does not exist)

3. The user must login onto the specific BSC for which data is required (this can be done through
X-Term, Telnet or through the OMC GUI).
4. The script must be run from the same location where the MotorolaSwitchDump.pl file is.

Figure 1: BSS Configuration Dump Retrieval through Telnet

2.2.2

Sector Coordinates File

The sector coordinates file must be in tab-delimited text file format with geographical information
for all sectors in the network.
The file should contain the following columns:
o Sector
o Latitude
o Longitude
o Azimuth
The Latitude and Longitude values should be in decimal format.

Schema Confidential & Proprietary

page 5 of 24

Ultima Fort Required Data Inputs for Motorola Infrastructure

2.3 Mobile Measurements Data Collection

A network freeze is strongly recommended during the recording time frame.
The following activities should be halted during data recordings:
o

BSC split

Site rehoming (BSC/site relations change)

Changes of LAC and CI

Site additions

Sector mechanical changes such as tilt, azimuth and antenna changes

Frequency changes (BCCH and BSIC)

Neighbor additions or deletions

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

TRX additions

Frequency changes (TCH)

All other parameters should not be changed.

Note: the version of BSS and OSS must be GSR7.
It is imperative that all Call Trace activities invoked in this OMC by other users be halted. This is
the limiting factor in mobile measurements collection per OMC and must be stopped to reach
allowable recording constraints.

2.3.1

Motorola CPT Recordings

CPT recordings should be performed for several consecutive working days. A recording plan should
be created by the Measurements Plan functionality in Ultima Fort. This functionality will create
several command files. Those files will be scheduled to run through the Cron. It is important that
these are not deleted or changed in any way. During this period no major changes should occur in
the network. The commands must be run one day before the expected beginning of recording, i.e.
before 24:00, the day before the expected recording start date.
To run Motorola Measurement Plan commands, please follow the instructions below:
1. Login to the system using Telnet or X-Term.
o

You should have access permission to carry certain operations on the BSC, such as adding
or deleting neighbors for a certain cell.

You should have permission to add system commands through Cron. If you do not know
what Cron is, please consult your system administrator.

Important note: old contents of the users Cron file will be removed upon execution of the
script. Please verify that this is OK before running the script.

Schema Confidential & Proprietary

page 6 of 24

Ultima Fort Required Data Inputs for Motorola Infrastructure

From the system Administrator - get an OMCR user from which to run the Cron. DO NOT
use the Root or OMC Admin users! Make sure this user has permissions to add a cron
table. In order to ascertain if the user has such permission or not, do the following:

Run crontab l to see any crons that are already defined. In case there is no
cron defined simply try to add Schemas cron (crontab scmCrontab). Then
run crontab l again and see if the cron was successfully added. In case the
cron was not added, make sure that the users name appears in the cron.allow
file, and that it does not appear in the cron.deny list in the /usr/lib/cron
directory. Preferably, use a user name which does not have a cron defined
already.

If you cannot use a user name which does not have a cron defined already and
in case crontab l shows there is already a cron defined (and obviously, this
user has permission to define crons), do the following:

Save the existing cron (crontab > cron_backup_file).

Append the content of cron_backup_file to the beginning of the

scmCrontab.

Load scmCrontab (crontab scmCrontab). This will erase the existing

cron and replace it with a cron that includes both the old one and
Schemas cron.

2. The limit of trace files created in the /usr/gsm/ne_data/ct_logs folder should be checked
and should be at least 200 MB (400,000 blocks) but 800 MB is recommended. This can be
checked and edited in the monitor_ct_logs file in the /usr/omc/sbin directory by the omc
admin only. In order to change this value simply modify the file and change Limit=100000
to Limit=800000 through vi (the text editor of UNIX). Use the following command: cat
monitor_ct_logs in /usr/omc/sbin directory to check the limit as shown below:

Figure 2: Checking the Limit of Trace Files

Schema Confidential & Proprietary

page 7 of 24

Ultima Fort Required Data Inputs for Motorola Infrastructure

The same configuration should be applied in the following files:

1. Hashed line in omcadmin Cron (...../maintain_ct.sh)
2. maintain_script
(set
Call
trace
configurable
diskspace
CT_1208DISKSPACE=800000) launched through the Cron of omcadmin.

variable

3. /usr/omc/current/config/Common.sh
CT_1208DISKSPACE=800000)

variable

(set

Call

trace

configurable

diskspace

If you do not want to change the limit, the workaround in Appendix B below can be used.

Figure 3: Changing the Variable Limit = 100000

3. Only one user host should run the crontab at all times from the same server. The server IP can
be checked with the ifconfig-a command.
4. Create a directory under the logged-in directory, which matches that which was defined in Step
2 of the MP Wizard during the command creations.
5. Use FTP to transfer the created command folders and files to a selected folder on your system.
These folders should be copied as is with the directory structure into the directory mentioned
above.
6. Copy the MotorolaSwitchDump.pl file to that directory as well.

Schema Confidential & Proprietary

page 8 of 24

Ultima Fort Required Data Inputs for Motorola Infrastructure

Figure 4: Copying File to Directory

7. Type from outside the <directory>: chmod 777 <directory> and chmod 777
<directory>/* to change permissions on all files in <directory>. Verify that rwxrwxr exists
for all files and folders when typing Is.

Figure 5: Type from Outside chmod 777 Directory

Figure 6: Verify That rwxrwxr Exists for All Files and Folders

Schema Confidential & Proprietary

page 9 of 24

Ultima Fort Required Data Inputs for Motorola Infrastructure

8. Run the crontab by typing: crontab scmCrontab on the command line. You can then type
crontabl to see the scheduled Cron commands that will be run, though this is not essential.

Figure 7: Type to See Scheduled Cron Commands

Figure 8: Scheduled Cron Commands

9. Once the recordings begin, the following day you should check on the recordings that are taking
place throughout the day to make sure that they are not interrupted in any way. This can be
easily monitored in the OMC GUI by selecting the BSC from the tree structure and selecting
View Call Traces. Be sure not to delete any traces. One file is created per call.
10. Once all traces have been completed, the call traces of each day should be tared and then
zipped into a single file per BSC (by RDN) and named: <RDN>_<year><month><day>.zip.
The <day> of the recorded file is the first 2 digits in the binary files extension. The RDN is the
number after the MMI_ e.g. ct_MMI_0000000013_00031_2717760.10115056_10101
was recorded on the 10th of the month at 11:50:56 for RDN 13. The files can be found in the
/usr/gsm/ne_data/ct_logs/ directory. The RDN number, which signifies the BSSID, can be
checked in the OMC-BSC properties manually for each BSC, by right-clicking on the BSC object.

Schema Confidential & Proprietary

page 10 of 24

Ultima Fort Required Data Inputs for Motorola Infrastructure

11. If at any time it is necessary to stop the process and clear the trace commands and neighbors,
then the following commands should be entered manually in the order mentioned for each
recorded BSS after logging in.
o
o
o
o

chg_l
trace_stop all
del_neighbor all test *
crontab r

Figure 9: Crontab-r

crontab l to make sure the crontab table has been removed when the following
command is displayed: crontab: cant open your crontab file

Figure 10: Can't Open the Crontab File

Notes:
o

for Solaris 8 6/00 s28s_u1wos_08 SPARC (Solaris 8 Maintenance Update 6 applied):

replace 'MSGDIR=/usr/gsm/current/config' with 'set

MSGDIR=/usr/gsm/current/config'

replace 'OMC_TOP=/usr/gsm' with 'set OMC_TOP=/usr/gsm'

to check operating system version type: cat /etc/release.

Figure 11: Checking Operating System Version Type

Schema Confidential & Proprietary

page 11 of 24

Ultima Fort Required Data Inputs for Motorola Infrastructure

to check cron logs and see which crons have been run, check log files in /var/cron. All the
files in this directory are ONLY readable by the root user. You should get permission for
reading log files for analysis purposes. The analysis should be concentrated on
monitor_ct_logs or maintain_ct.sh commands.

Figure 12: Log Files Analysis

2.3.2

there may be a monitor_ct_logs or maintain_ct.sh script which cleans the

/usr/gsm/ne_data/ct_logs directory and may be found in the /usr/omc/sbin
directory. This is usually run by the omc cron user. In this case, increase the folder
size in the monitor_ct_logs file in the /usr/omc/sbin folder to 400,000 blocks or
300MB.

you may find omcaudit<date> files in the /usr/omc/logs directory to check which OMC
commands have been performed.

Traffic Data

The generic Schema format for traffic can be used. The columns should be in tabular ASCII format
with the headers: Sector and Traffic. It is recommended that the traffic be a 3-4 hour average
around a network busy hour to the BSC being recorded.

2.3.3

RxQual Data

RxQual data should be collected within the OMC-R Performance Management System. There are 16
files in all, 8 for downlink and 8 for uplink, one file for each RxQual value. Each file contains data
for all cells in the BSC per TRX per hour. The files can be retrieved by following the procedure
below:
1. From the OMCR, click on the Performance icon to open the Performance Management
window as shown in figure 13 below:

Schema Confidential & Proprietary

page 12 of 24

Ultima Fort Required Data Inputs for Motorola Infrastructure

Figure 13: Performance Management Window

2. Select Report Template and click on OK to open the Report Template window as shown in
figure 14 below:

Figure 14: Report Template Window

3. Select TJ (Statistics) Cell to open the Report Template:[TJ_cell] window.

4. Select the appropriate items as shown (boxed in Red) in figure 15 below and click Run:

Schema Confidential & Proprietary

page 13 of 24

Ultima Fort Required Data Inputs for Motorola Infrastructure

Figure 15: Selecting the Appropriate Items

5. Select the CARRIER device type in the top left-hand corner of the window.
6. Find the item titled Downlink RxQual (BER). Double-click on it and the item will expand to 8
sub-items: Bit Error Rate Bin0.....Bin7.
7. Check and select the desired sub-item.
8. Type the file name and click on OK (figure 16 below). This will activate the RxQual data
collection process.

Schema Confidential & Proprietary

page 14 of 24

Ultima Fort Required Data Inputs for Motorola Infrastructure

Figure 16: Activating the RxQual Data Collection Process

9. Repeat the above steps for Downlink and Uplink Bit Error Rate for Bin0 Bin7.
Note: RxQual can alternatively be imported from the CPT files. Note that the BER and UBER files
are the recommended ones to use.

2.3.4

BSC Index Data

The BSC Index Data can be obtained within the OMC-R Configuration Management System as
follows:
1. From the OMCR, click on the Config Mgt icon to launch it. See figure 17 below.

Figure 17: Click on the Config Mgt Icon

2. Click on BSS to expand the BSS menu as in figure 18 below.

Schema Confidential & Proprietary

page 15 of 24

Ultima Fort Required Data Inputs for Motorola Infrastructure

Figure 18: Expanding the BSS Menu

3. Select the relevant BSS for your project (example: TLBSC21) and click on it to launch the BSS
Monitor window as in figure 19 below.

Figure 19: BSS Monitor Window

4. The BSC Index number is the RDN Instance number (example: TLBSC21 is 3).

Schema Confidential & Proprietary

page 16 of 24

Ultima Fort Required Data Inputs for Motorola Infrastructure

Figure 20: BSS Window

5. Repeat this procedure for all BSCs related to the optimization project in order to obtain the
BSC Index number.
The retrieved BSC indices should be placed in the predefined text table format with tab separation.
An example of a bscIndex.txt file structure is shown in the table below:
BSC Name

BSC Index

TLBSC23

22

TLBSC21

TLBSC22

TLBSC24

43

This file should be located in the root directory where the daily recordings are placed prior to
importing this data into UltimaFort.

Schema Confidential & Proprietary

page 17 of 24

Ultima Fort Required Data Inputs for Motorola Infrastructure

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 network performance statistics should be collected on a per cell basis with hourly
resolution over 5 business days prior to retune and 5 business days after retune:
1.

SDCCH Traffic:
BUSY_SDCCH_MEAN

2.

SDCCH Performance:
ALLOC_SDCCH, CHAN_REQ_MS_FAIL, RF_LOSSES_SD

3.

TCH Traffic:
BUSY_TCH_MEAN, BUSY_TCH_HR_AMR_MEAN, TOTAL CALLS, ASSIGNMENT_REDIRECTION
[DIRECTED_RETRY], ASSIGNMENT_REDIRECTION [DURING_ASSIGNMENTS],
ASSIGNMENT_REDIRECTION [MULTIBAND_BAND]

4.

TCH Performance:
RF_LOSSES_TCH, RF_LOSSES_TCH_HR_AMR, INTRA_CELL_HO [INTRA_CELL_HO_LOSTMS],
OUT_INTRA_BSS_HO [OUT_INTRA_BSS_HO_LOSTMS], OUT_INTER_BSS_HO
[OUT_INTER_BSS_ CLEARED] (OUT_INTER_BSS_HO [OUT_INTER_BSS_HO_CLEARED]),
DROP_CALL_RATE (not in formulas)

5.

Rx Quality Performance:
BER_BIN0 BER_BIN7 files (8 total files, 1 per RxQual)
UBER_BIN0 UBER_BIN7 files (8 total files, 1 per RxQual)

6.

HO Performance:
INTRA_CELL_HO [INTRA_CELL_HO_ATMPT_FR_FR], INTRA_CELL_HO
[INTRA_CELL_HO_ATMPT_HR_HR], INTRA_CELL_HO [INTRA_CELL_HO_ATMPT_FR_HR],
INTRA_CELL_HO [INTRA_CELL_HO_ATMPT_HR_FR], OUT_INTRA_BSS_HO
[OUT_INTRA_BSS_HO_ATMPT], OUT_INTER_BSS_HO [ OUT_INTER_BSS_HO_SUC],
OUT_INTRA_BSS_HO [ OUT_INTRA_BSS_HO_SUC], INTRA_CELL_HO [ INTRA_CELL_HO_SUC]

2.4.1

Network Performance Evaluation

Each KPI improvement rate will be calculated as:

KPI _ improvemen t _ rate =

KPI before KPI new

KPI before

100%

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

KPI _ Success _ improvemen t _ rate =

Schema Confidential & Proprietary

KPI before KPI new

1 KPI before

100%

page 18 of 24

Ultima Fort Required Data Inputs for Motorola Infrastructure

Each KPI will be calculated for improvement rate separately over 5 business days (24 hours or a
selected hours range) before and after optimization.
Network performance KPIs that are not related to the optimization should 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:
SDCCH _ Drop _ Rate =

(RF_LOSSES_SD )

(ALLOC_SDCCH - CHAN_REQ_MS_FAIL)

(RF_LOSSES_TCH + RF_LOSSES_TCH_HR_AMR )

TCH _ Drop _ Rate _ Radio =

TOTAL_CALLS +

+ ASSIGNMENT_REDIRECTION [DIRECTED_RETRY] +
+ ASSIGNMENT_REDIRECTION [DURING_ASSIGNMENTS] +

+ ASSIGNMENT_REDIRECTION [MULTIBAND_BAND]

TCH _ Erlang _ to _ Drop _ Radio =

(BUSY_TCH_M EAN + BUSY_TCH_H R_AMR_MEAN )

(RF_LOSSES_ TCH + RF_LOSSES_ TCH_HR_AMR )

TCH _ Bad _ Quality _ DL =

BER_BIN[x]
x =5
7

BER_BIN[x]
x =0

TCH _ Bad _ Quality _ UL =

UBER_BIN[x]
x =5
7

UBER_BIN[x]
x =0

HO _ Success _ Rate =

OUT_INTRA_BSS_HO [OUT_INTRA_BSS_HO_SUC]

+ OUT_INTER_BSS_HO [OUT_INTER_BSS_HO_SUC]
+ INTRA_CELL_HO [INTRA_CELL_HO_SUC]

OUT_INTER_BSS_HO [OUT_INTER_BSS_HO_ATMPT]

+ OUT_INTRA_BSS_HO [OUT_INTRA_BSS_HO_ATMPT]
+ INTRA_CELL_HO [INTRA_CELL_HO_ATMPT_FR_FR]
+ INTRA_CELL_HO [INTRA_CELL_HO_ATMPT_HR_HR]
+ INTRA_CELL_HO [INTRA_CELL_HO_ATMPT_FR_HR]

+ INTRA_CELL_HO [INTRA_CELL_HO_ATMPT_HR_FR]

Schema Confidential & Proprietary

page 19 of 24

Ultima Fort Required Data Inputs for Motorola Infrastructure

Note:
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 providing additional KPIs for network performance evaluation:

RF_LOSSES_TCH + RF_LOSSES_TCH_HR_AMR +

+ INTRA_CELL_HO[INTRA_CELL_HO_LOSTMS] +
+ OUT_INTRA_BSS_HO [OUT_INTRA_BSS_HO_LOSTMS] +

+ OUT_INTER_BSS_HO [OUT_INTER_BSS_HO_CLEARED]

TCH _ Drop _ Rate =

TOTAL_CALLS +

+
+
ASSIGNMENT
_REDIRECTI
ON
[DIRECTED_
RETRY]

+ ASSIGNMENT_REDIRECTION [DURING_ASSIGNMENTS] +

+ ASSIGNMENT_REDIRECTION [MULTIBAND_BAND]

TCH _ Erlang _ to _ Drop =

(BUSY_TCH_MEAN + BUSY_TCH_HR_AMR_MEAN)
RF_LOSSES_TCH + RF_LOSSES_TCH_HR_AMR +

+ INTRA_CELL_HO[INTRA_CELL_HO_LOSTMS] +

+ OUT_INTRA_BSS_HO [OUT_INTRA_BSS_HO_LOSTMS] +

+ OUT_INTER_BSS_HO [OUT_INTER_BSS_HO_CLEARED]

SDCCH _ Traffic = (BUSY_SDCCH _MEAN )

TCH _Traffic = (BUSY_TCH_MEAN + BUSY_TCH_HR_AMR_MEAN)

Call _ Setup _ Success _ Rate =

(TOTAL _ CALLS + ASSIGNMENT_REDIRECTION )

OK_ACC_PROC[CM_SERV_REQ_CALL]

+ OK_ACC_PROC[CM_REESTABLISH]

+ OK_ACC_PROC[PAGE_RESPONSE]

+ OK_ACC_PROC[CM_SERV_REQ_SMS]
+ OK_ACC_PROC[CM_SERV_REQ_EMERG]

+ OK_ACC_PROC[LOC_FLW_ON_REQ_NORMAL]

+ OK_ACC_PROC[LOC_FLW_ON_REQ_SMS]
+ SMS_INIT_ON_SDCCH - MT_LCS_ON_SDCCH

Schema Confidential & Proprietary

page 20 of 24

Ultima Fort Required Data Inputs for Motorola Infrastructure

2.4.4

Collecting KPI Data

KPI data should be collected within the OMC-R Performance Management System.
Each counter mentioned in section 2.4 above should be retrieved.
Each file (table) can contain up to 14 counters (columns). Therefore 2 tables are required to collect
all the required counters. This data is required for all cells, for 24 hours with hourly resolution. The
files can be retrieved by using the same procedure as for RxQual Data in section 2.3.3 above.

Figure 21: Collecting KPI Data

Schema Confidential & Proprietary

page 21 of 24

Ultima Fort Required Data Inputs for Motorola Infrastructure

3 Data Collection Checklist

SOURCE

COMMENTS

CHECK

Network Data
BSS Dump Files
BSC Index File
Sector Coordinates File
Traffic File
Mobile Measurements Recordings
Day 1

Day 2

Day 3

Day 4

Day 5

BSS Dump Files

CPT Recordings
Network Performance Statistics
SDCCH Traffic
SDCCH Performance
TCH Traffic
TCH Performance
Rx Quality Performance
Handover (HO)
Performance

Schema Confidential & Proprietary

page 22 of 24

Ultima Fort Required Data Inputs for Motorola Infrastructure

4 Appendix A Switch Dump Script Example

See the embedded file below:

D:\R&D\OpenIssues\
Motorola\Kazakhstan\

5 Appendix B Move Script Example

Run the script which moves all call traces files from the /usr/gsm/ne_data/ct_logs/ directory
to a temporary directory before midnight to avoid being removed by the monitor_ct_logs scripts
which are normally scheduled to run right after midnight. You can modify the "move" scripts to suit
your local path directory and include it in the scmCrontab file.
Example of a "move" script is as follows:
mv/usr/gsm/ne_data/ct_logs/ct_MMI*
/export/home/wangyou/schema/20060523_ct_logs/.
tarcvf/export/home/wangyou/schema/20060523_ct_logs/20060523.tar
/export/home/wangyou/schema/20060523_ct_logs/ct_MMI*
gzip /export/home/wangyou/schema/20060523_ct_logs/20060523.tar
An example of a "move" script exists in the scmCrontab file generated by UltimaFort.
Insert the above "move" script in a file called scmCronCmd_MOV_20060523 and then add it to
the scmCrontab file as follows:
07 23 23 05 * schema/scmCronCmd_MOV_20060523

Schema Confidential & Proprietary

page 23 of 24

Ultima Fort Required Data Inputs for Motorola Infrastructure

6 Appendix C Trace Call Command

Following is the trace call command, and the questions it corresponds to from the OMCR:

chg_l
trace_stop all
trace_call cell= 4 0 1 0 1 3230 57142
Enter trigger event: all
Enter additional data types (basic included): rss
Collect during handover only?: no
Enter measurement report interval (x480ms):1
Enter call selector type and value: nth= 1
Enter maximum simultaneous calls traced per LCF: 4
Trigger enabled time: 10:30
Trigger disabled time: 11:00
Enter total number of calls to be traced: (no data entered)
Trace calls beyond scope?: no
Enter destination for trace data: omc

Schema Confidential & Proprietary

page 24 of 24