performance measurements rel_s12

8/2/2019 Performance Measurements Rel_S12

1/22

Performance Measurements

DN9813612Issue 10-0 en

# Nokia Corporation 1 (22)

BSC3119

Nokia BSC/TCSM, Rel. S12, Product

Documentation, v.1


2/22

The information in this document is subject to change without notice and describes only theproduct defined in the introduction of this documentation. This document is intended for the useof Nokia's customers only for the purposes of the agreement under which the document issubmitted, and no part of it may be reproduced or transmitted in any form or means without the

prior written permission of Nokia. The document has been prepared to be used by professionaland properly trained personnel, and the customer assumes full responsibility when using it.Nokia welcomes customer comments as part of the process of continuous development andimprovement of the documentation.

The information or statements given in this document concerning the suitability, capacity, orperformance of the mentioned hardware or software products cannot be considered binding butshall be defined in the agreement made between Nokia and the customer. However, Nokia hasmade all reasonable efforts to ensure that the instructions contained in the document areadequate and free of material errors and omissions. Nokia will, if necessary, explain issueswhich may not be covered by the document.

Nokia's liability for any errors in the document is limited to the documentary correction of errors.NOKIA WILL NOT BE RESPONSIBLE IN ANY EVENT FOR ERRORS IN THIS DOCUMENTOR FOR ANY DAMAGES, INCIDENTAL OR CONSEQUENTIAL (INCLUDING MONETARYLOSSES), that might arise from the use of this document or the information in it.

This document and the product it describes are considered protected by copyright according tothe applicable laws.

NOKIA logo is a registered trademark of Nokia Corporation.

Other product names mentioned in this document may be trademarks of their respectivecompanies, and they are mentioned for identification purposes only.

Copyright Nokia Corporation 2007. All rights reserved.

2 (22) # Nokia Corporation DN9813612Issue 10-0 en



3/22

Contents

Contents 3

List of tables 4

List of figures 5

Summary of changes 7

1 Performance measurements 91.1 Call control measurements (CSW) 111.2 GPRS measurements (PSW) 171.3 Transmission measurements 181.4 Observations 20



Contents


4/22

List of tables

Table 1. Example of a counter table 9

Table 2. Transmission measurement and equipment types 19




5/22

List of figures



List of figures


6/22




7/22

Summary of changes

Changes between document issues are cumulative. Therefore, the latest document

issue contains all changes made to previous issues.

Changes made between issues 10 and 91

Information on the counter numbering of 21 Radio Measurement Report, 24

Dropped Call Observation, and 50 BSC Level Clear Code Measurement has been

added.

New fields Trigger type and Sampling interval have been added to the table

Example of a counter table, and the description of the Unitfield has been revised.

Information on spare counters and a reference to NOLS Documentation Center's

Reference Information Service has been added.

Three new call control measurement types have been added: 106 CS DTMMeasurement, 107 AMR RX Quality Measurement, and 108 DFCA SAIC

Measurement.

One new GPRS measurement type has been added: 105 PS DTM Measurement.

One observation type has been removed because it is no longer supported: 23

ISDN Abis Observation.

26 Position Based Services Observation has been changed into 30 Position Based

Services Observation.

References to online observations have been removed because online

observations are no longer supported.

Reference to TCSM2 has been removed.

Editorial changes have been made.



Summary of changes


8/22


The description of Drop Call Breakdown Observation has been updated.


A new call control measurement, 109 Soft Channel Capacity Measurement, has

been added.




9/22

1 Performance measurementsCounters are numbered according to the measurement type XXXYYY, where

XXX is the measurement type and YYY is the counter number of the

measurement. 21 Radio Measurement Report, 24 Dropped Call Observation, and

50 BSC Level Clear Code Measurement are exceptions: their numbering is

XXXYYYY.

Information about each counter, including its name, number, description, and

other details are presented in a table. The table fields are explained in the table

Example of a counter table.

Table 1. Example of a counter table

Number

Name

Release

Definition updated

Number of the counter

Name of the counter

Original release. For spare counters,indicates the release where the spare

counter was created in the BSC.

Release where the counter was updated. For

spare counters, this field may include

several entries. The release where the spare

counter was made official is followed by the

explanation (Name changed).

Trigger points Includes references to signalling charts if the

measurement has signalling charts.

Description Explains what the counter is for.

Updated Informs when the counter is updated.

Trigger type Specifies the type of events that trigger the counter:

event, sample, or duration.

Dependencies with other counters/PI(s) Informs if the counter is interdependent with other

counters.

Feature Specifies the software product the counter is related

to.



Performance measurements


10/22

Table 1. Example of a counter table (cont.)

Number

Name

Release

Definition updated

Number of the counter

Name of the counter

Original release. For spare counters,

indicates the release where the spare

counter was created in the BSC.

Release where the counter was updated. For

spare counters, this field may include

several entries. The release where the spare

counter was made official is followed by the

explanation (Name changed).

Example values Shows examples of the values the counter can

receive.

Impact Explains the impact, for example, call cleared.

Reason for the impact Explains the reason for the impact.

Logical type Can be, for example, average or peak. If the logical

type has not been defined in the table, the counter is

a basic counter.

Note! The denominator counter value is always >0.

Unit Unit in which the values of the counter are given.

Most often the unit is an integer number. It can also

be, for example, per cent, kB, ms.

Range Limits to the values the counter can receive.

Sampling interval If the trigger type is sample, specifies the interval at

which the samples are taken.

The fields of the counter tables are filled in by taking into account the different

nature of each measurement and observation. For this reason, the tables may vary

in size and content. For example, if example values are not given for a counter,

the field Example values is not included in the actual counter table.

In some cases there can be counter tables with the same counter number. In such

cases, all the information is technically coded in one counter, but separated in the

documentation to improve readability.

Measurements may also include spare counters. They are used for implementing

new counters in the BSC and Nokia NetAct for temporary use between main

releases. When a new counter is needed between main releases, the chosen spare

counter is put into use in the BSC and it starts collecting data to NetAct. In the

BSC documentation, the counter receives a definition, but its name remains as

SPARExxxxxx. In the next NetAct main release, the counter is made official, that

is, it receives a proper name. After this it is included also in the BSC

documentation with a proper name.




11/22

Measurements and observations are divided into the following groups according

to their function:

.

Call control measurements (CSW). GPRS measurements (PSW)

. Transmission measurements

. Observations

In general, measurements consist of several counters that measure various

matters.

Counters essential for the operation of the network are so-called public counters,

whereas counters for special situations are so-called expert counters. Public

counters are documented with the accuracy of signalling charts and trigger points.Measurements that include signalling charts are marked with the text (incl.

signalling charts) after the name of the document.

Optional measurements are marked with (optional) after the name of the

document.

BSC counter information is also directly available and accessible via the

Reference Information Service in NOLS Documentation Center. The information

in the Reference Information Service is updated more frequently than the BSC

NED browser environment.

1.1 Call control measurements (CSW)

Call control measurements measure call-related issues, such as congestion on a

specific channel or area.

Call control measurements can be divided into two groups:

. circuit-switched (CSW) measurements

. packet-switched (PSW) measurements

The packet-switched measurements are referred to as GPRS measurements. For

more information, see 1.2 GPRS measurements (PSW).





12/22

No Measurement/optionality Purpose/function Level/role/

application

1 Traffic Measurement (incl. signalling

charts)

Registers information related to the

SDCCH and TCHs. Provides informationon, for example, seizure attempts and

successful seizures for the SDCCH and

the TCH.

BTS-level

2 Resource Availability Measurement Registers information on the availability

of TCH and SDCCH. Provides

information on, for example, TCH

congestion time and the peak number of

busy TCHs and SDCCHs.

BTS-level

3 Resource Access Measurement (incl.

signalling charts)

Registers information on all CCCHs of

the BSC. Indicates the number of paging

messages sent to the BTS, and

successful seizures for mobile-originated

(MO) and mobile-terminated (MT) calls.

BTS+TRX -level

4 Handover Measurement (incl.

signalling charts)

Registers information on the number of

handovers (HO) controlled by the MSC

or the BSC. Records the number of the

incoming, outgoing, or intra-cell HOs,

and the number of successful and

unsuccessful attempts, seizures, and

HOs. The HOs are sorted according to

direction, where appropriate.

BTS-level

5 Power Control Measurement Registers information on how the BSC

controls the power level and signal

quality of the MS and the BTS. Provides

information, for example, on the qualityand strength of the signals both in uplink

and downlink directions.

BTS+TRX -level

6 Load Measurement Registers information on the peak and

the average load rate of the computer

units.

BSC-level

7 Availability Measurement Registers information on the restart and

the disconnection times of the computer

units. Used for field reporting.

BSC-level

8 OSI/X.25 Measurements Provides information on the four lowest

layers of the OSI stack, that is,

information on how the connection

between the BSC and Nokia NetActfunctions.

OSI-channel+Unit nbr

-level

13 Undefined Adjacent Cell Measurement Registers statistics on cells, which have

not been defined as adjacent cells but

are among those six neighbouring cells

that the MS receives best. Provides

information on the signal strength of

those cells.

BTS-level


http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-


13/22


application

14 RX Quality Statistics Measurement

(optional)

Registers information both in uplink and

downlink directions on the TRXs.Provides information on the RX quality

band frequencies with the accuracy of

one TRX, BTS or BSC. The RX quality

frequencies are collected only of the

TCHs.

BTS+TRX -level

15 Handover Adjacent Cell Measurement

(incl. signalling charts) (optional)

Registers information on handover

attempts, successful handovers and

failed handovers due to lack of radio

resources. Provides information on how

handovers between different cells are

divided.

BTS-level (+HO

category level

optionally

50 BSC Level Clear Code Measurement Collects statistics on clear codes for the

BSC during calls. Registers failures thathave occurred during a call (signalling or

conversation). Provides information on

the quality of service in the BSC with the

accuracy of a cell.

BSC-level

51 BSC Level Clear Code (PM)

Measurement(incl. signalling charts)

Provides information on transactions in

the BSC, for example, location update

and failure sum counters. The

information is especially relevant from

the point of view of determining the

service level.

BSC-level

52 Underlay Overlay Statistics

Measurement (incl. signalling charts)(optional)

Registers information on the performance

of the Intelligent Underlay-Overlayprocedure. Provides information with the

accuracy of one TRX.

BTS+TRX -level

(+freg. group)

53 RX Level Statistics Measurement

(optional)

Registers information on the level and

quality of RX signal on both uplink and

downlink direction. Provides the

information in six classes per RX quality

band in both uplink and downlink

directions.

BTS+TRX -level

54 Link Balance per MS Classmark

Measurement (optional)

Registers information on the link balance

in the network, that is, the difference

between the uplink and downlink signal

levels. The link balance difference is

divided into 11 subclasses: 6 classes for

negative imbalance, one class for

balance and 5 classes for positive

imbalance. The measurement provides

the information with the accuracy of one

cell.

BTS-level



http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-


14/22


application

55 Timing Advance Statistics


Registers information on the timing

advance during calls. With thisinformation you can estimate the

distribution of the subscribers within a

cell area. The measurement provides the

information with the accuracy of either

one BTS or one BSC.

The timing advance values are divided

into ten subclasses. The user sets the

ranges for the classes, for example, the

range can be denser in a micro cell than

in a macro cell.

BTS-level

56 Resource Availability per BSC

Measurement

Registers information on the availability

of the TRXs on the BSC level. The

number of the TRXs which are notavailable is divided into three categories

according to what causes the

unavailability: the user, internal reasons,

and external reasons.

BSC-level

57 BSC Level Clear Code (SERLEV)

Measurement (incl. signalling charts)

Registers statistics about clear codes in

a BSC during calls. Provides general

information on transactions in the BSC.

BTS-level

58 MS Speed Detection Measurement

(optional)

Collects information on the speed of MS.

Provides information on slow moving and

fast moving MSs. The information is

collected for each cell. The MS speed

statistics is collected only from the TCHs.There are three MS speed classes.

BTS-level

59 Dual Band Measurement (optional) Provides information on the traffic

distribution, that is, on TCH holding times

and reservations of single and dual band

subscribers. The information is collected

for each cell.

BTS-level

60 C/I Ratio Measurement (optional) Collects statistics on the degree of the

interference by measuring traffic intensity

(Erlang) on a specified C/I (carrier/

interference) ratio band. Estimates the

level of the potential co- and adjacent

channel interference in the radio network.

BTS-level (LAC-CI)

61 Hot Spot Measurement (optional) Registers information on the adjacent cell

RX levels and on timing advance

distribution. Finds out the highest traffic

distribution spots in the mobile network.

With this measurement you can retrieve

information that indicates the places in

the network where more capacity is

needed.

BTS+TRX -level

(LAC-CI)


http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-


15/22


application

67 High Speed Data Measurement

(optional)

Collects statistics about radio resources

used for fulfilling High Speed CircuitSwitched Data (HSCSD) requests.

Measures the functioning of the HSCSD

and 14.4 kbit/s Data Services software

products.

BTS-level

70 Channel Finder Measurement

(optional)

Registers statistics on cells which have

not been defined as adjacent cells, but

are among those six neighbouring cells

that the MS receives best. Provides

information on the signal strength

standard deviation, and class boundaries

of those cells.

BTS-level

71 MS Capability Indication Measurement

(incl. signalling charts) (optional)

Provides cell-specific information on the

capabilities of the MSs.

BTS-level

75 Defined Adjacent Cell Measurement

(optional)

Registers statistics on defined cells. This

measurement data is collected in cell

level.

BTS-level

77 FER Measurement (optional) Registers information both in uplink and

downlink directions on the TRXs.

BTS+TRX+codec -

level

78 Position Based Services


Registers location requests grouped by

LCS QoS, location responses grouped

by accuracy, and error cases.

BTS-level (LAC-CI)

89 Reversed Hunting Measurement

(optional)

Registers information on the BSS, which

allocates the circuit needed directly

based on the radio interface resources.

A interface pool-level

92 Non-BCCH Layer Offset Measurement

(optional)

Registers link budget differences in the

serving cell.

BTS-level

93 UTRAN Handover Adjacent Cell

Measurement (incl. signalling charts)

(optional)

Registers statistics about the distribution

of inter-system handovers between

different cells.

BTS-level

94 UTRAN Neighbouring Cell Signal

Level Measurement (optional)

Registers information on signal levels of

WCDMA RAN cell in the neighbourhood

of a GSM serving cell.

BTS-level

99 Total FEP Measurement (optional) Collects statistics on the cumulated sum

of frame erasure probability (FEP) values

for a certain serving cell - neighbouringcell pair. Includes separate counters for

co-channel and adjacent channel

interference.

BTS-level

100 DFCA Measurement (optional) Collects statistics on the performance of

the DFCA application software. The data

is collected at cell level separately for

each connection type (FR/EFR, HR,

14.4, AMR FR, and AMR HR).

BTS-level +

connection type



http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-


16/22


application

101 DFCA Assignment Measurement

(optional)

Collects statistics on the usage of DFCA

channels at cell level. The assignmentcounters are updated whenever the

corresponding MA list and MAIO are

used in a DFCA assignment.

BTS-level

102 BSC-BSC Measurement (optional) Collects statistics on the inter-BSC

communication related to the DFCA

application software. The counters of this

measurement record information on

average and peak delay between the

Radio Resource Managers in separate

BSCs.

Signalling point code

103 WPS Measurement (optional) Registers information on the performance

of traffic channel allocation and queuing

algorithms in granting priority access toWPS users.

BTS-level

104 IMSI Based Handover Measurement

(optional)

Collects statistics on the IMSI-based

handover attempts and failures for each

Authorised Network (ANE). There are

separate counters for GSM and UTRAN

networks.

BTS-level

106 CS DTM Measurement (incl. signalling

charts) (optional)

Collects statistics on Dual Transfer Mode

(DTM). Mainly collects MS-initiated DTM

call establishment information and CS

connection-related information of a DTM

call.

BTS-level

107 AMR RX Quality Measurement

(optional)

Collects statistics on uplink and downlink

RX quality for each AMR bitrate. The

information is collected from each

transceiver (TRX) separately.

BTS+TRX -level

108 DFCA SAIC Measurement(optional) Collects statistics on the performance of

the DFCA application software for

connections of SAIC-capable mobiles.

The data is collected at cell level

separately for each connection type (FR/

EFR, HR, 14.4, AMR FR, and AMR HR).

BTS-level +

connection type

109 Soft Channel Capacity Measurement

(optional)

Collects statistics on the availability of

traffic channels (TCH) in the BCSU

object level. The time congestion ofTCHs and the average and peak

numbers of busy TCHs are measured.

BCSU Logical

Address


http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-


17/22

1.2 GPRS measurements (PSW)

GPRS measurements are packet-switched (PSW) call control measurements.

GPRS measurements measure call-related issues, such as congestion on a specificchannel or area. For circuit-switched (CSW) measurements, see 1.1 Call control

measurements (CSW).


application

72 Packet Control Unit Measurement

(incl. signalling charts)

Provides cell-level information on the

functions in charge of the Packet

Control Unit (PCU). The counters

concentrate on the amount of packet-

traffic related transactions, data

throughput quality of provided service(failed/passed transactions), and the

availability of service (for example,

congestion, load of interfaces). The

need to get more capacity is indicated

well in advance.

BTS-level

73 RLC Blocks per TRX Measurement Provides TRX-specific information on

data throughput quality based on the

RLC/MAC blocks. The information can

be used for parameterisation of TRX

capacity.

BTS+TRX -level

74 Frame Relay Measurement Provides bearer channel and PVC

(Permanent Virtual Connection) specificinformation on the proper working of the

frame relay between the PCU and the

SGSN.

Bearer-level

76 Dynamic Abis Measurement (optional) Registers information on the

unsuccessful call establishment and

peak and average usage of dynamic

abis pool.

Abis pool-level

79 Coding Scheme Measurement

(optional)

Registers information about the amount

of data transferred to uplink and

downlink directions in the radio interface

using the different EGPRS modulation

and coding schemes (MCS) and GPRS

coding schemes CS-3 and CS-4.

BTS+coding scheme -

level

90 Quality of Service Measurement Registers information related to priority.

Provides information on, for example,

the number of RLC blocks and TBFs.

Segment+QoS priority

class -level

91 PBCCH Availability Measurement Registers availability of packet control

channels.

BTS-level



http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-


18/22


application

95 GPRS Cell Reselection Measurement

(optional)

Registers information about the source

and target cell, the number of cellreselection attempts for various causes,

the number of successful NCCR

procedures, and the number of failures

for various failure reasons.

BTS-level + LAC-CI

96 GPRS RX Level and Quality


Collects RX quality levels per each RX

class, and quality information per coding

scheme.

BTS + TRX + coding

scheme

97 Enhanced Quality of Service

Measurement

Records information about PFC

procedures, transferred data, and quality

control.

SEG + TC-THP-PFI+

ARP

98 Gb Over IP Measurement (optional) Registers the data related to Gb over IP.

IP provides an alternative to FrameRelay (FR) as a transport layer for the

Gb interface. The information is

collected from every Network Service

Virtual Connection (NS-VC) identified

with NS-VC id and NSE (Network

Service Entity) id.

NS-VCI + NSEI

105 PS DTM Measurement (incl. signalling

charts) (optional)

Collects statistics on Dual Transfer

Mode (DTM). Mainly collects network-

initiated DTM call establishment

information and PS connection-related

information of a DTM call.

BTS-level

1.3 Transmission measurements

Transmission measurements measure transmission and network quality.

The measurements collect data from counters in every working transmission

equipment and exchange terminal (ET). The transmission equipment increment

some of the counters all the time and some only when transmission errors happen.

They register the availability of the connection and the time during which there

are errored bits in the transferred data. They also register information on

functional disturbances, frame errors, and slips. This information is used indowntime statistics.

The information is collected from the transmission equipment, which is divided

into suitable groups. The division is made based on the equipment type and

generation. Table Transmission measurement and equipment types describes this

division.


http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-


19/22

Table 2. Transmission measurement and equipment types

Measurement type Equipment type Equipment generation

DMR DMR TMS4

DN2 DN2 TMS4

TRU/BIE TRU, BIE TMS4

Not supported TRE TMS4

TRE TRE, DMR Nokia Q1

TRE_SEL TRE, DMR Nokia Q1

In practice, the Nokia Q1 generation equipment comprise the Nokia MetroSite

transmission equipment. Transmission Equipment Measurement (TRE) collects

information from all the equipment in the network, while Selective TransmissionEquipment Measurement (TRE_SEL) collects information from a selected part of

the network.

The connection between the BSC and the managed equipment is established

either through a BSC-BTS O&M link or a Q1 service channel. The possible

equipment types at a Base Transceiver Station (BTS) site are: Base Station

Interface Equipment (BIE), Transmission Unit (TRU), and Digital Microwave

Radio Link (DMR). Other transmission equipment types at the BTS site, such as

optical line equipment, are handled in the BSC with the common name

Transmission Equipment (TRE).

With the QWL command you can list the equipment type and generation of all the

equipment in the network. With the MML commands in the QU command group

you can select and interrogate the equipment for Selective Transmission

Equipment Measurement.

In general, a measurement collects data from all equipment defined in the

measurement type. Therefore, it is not possible to collect statistics from specific

equipment of a measurement type. With Selective Transmission Equipment

Measurement you can only define the part of the MetroSite transmission system

you want to measure.


application

62 DMR Measurement Registers information on the signal

quality and frequency input level of radio

hopping, controlled by a DMR. The

measurement collects information from

the radio relay equipment.

PCM-level





20/22


application

63 DN2 Measurement Registers information on the signal

quality of the PCM wire connected to aDN2. The measurement provides

information on transmission quality in

used PCM connection between a DN2

and the BSC or another transmission

equipment.

PCM-level

64 TRU/BIE Measurement Registers information on the signal

quality of the PCM wire connected to the

transmission unit (TRUA/TRUB) and/or

the base station interface equipment

(BIE). The measurement provides

information about transmission quality in

used PCM connection between a TRU/

BIE and the BSC or anothertransmission equipment.

PCM-level

65 ET BSC Measurement Provides information on the signal quality

of the PCM wire, which is connected to

the exchange terminal (ET) equipment

controlled by a BSC.

PCM-level

66 ET TCSM Measurement Provides information on the signal quality

of the PCM wire, which is connected to

the ET equipment controlled by a TCSM.

PCM-level

68 TRE Measurement Registers information on the signal

quality of the MetroSite transmission

system.

PCM-level

69 Selective TRE Measurement Registers information on the signal

quality and frequency input level (only

from radio relay equipment) of the

selected part of the MetroSite

transmission system.

PCM-level

1.4 Observations

Observations are useful in the BSC status monitoring as they give exact, almost

real time information on the network's performance: its traffic situation, handoversuccess, and handover problems. With the aid of the observations, you can

examine, for example, abnormal function or traffic pattern of calls on a specific

cell or channel, why several calls have ended prematurely without any obvious

reason, or why it is not possible to establish calls from some location area. This

information is useful in system maintenance and system testing.


http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-


21/22

Basically, all observations have the same function: they generate records on

specific occasions. However, they have a different observation record format, and

they differ in the triggering conditions for generating an observation record. For

example, activity on the chosen channel creates channel observation records,

handovers occurring in the observing cell create handover records, and a clear

code observed during a call in the observed cell creates clear code observation

records.

The observation records are stored on disk files either when the observation

buffer is full or at user-defined intervals. The disk files are then transferred to

Nokia NetAct for post-processing.

You can activate the appropriate observation to a desired object and define a

schedule for that observation. When needed, you can also start the observations

immediately without a schedule.

No Observation/optionality Purpose/function

16 SDCCH Observation Provides information on activity on the SDCCH. An

observation report is generated every time the

SDCCH is released.

17 TCH Observation Provides information on the use of the TCH. An

observation report is generated every time the TCH

is released.

18 Handover Observations (including internal,

incoming and outgoing handover observations)

Provides information on handovers made in the

BSC, from some other BSC to the observing BSC,

and from the observing BSC to some other BSC. Anobservation report is generated every time such an

HO occurs.

21 Radio Measurement Report Provides information on handovers made during the

call as well as levels and qualities of the uplink and

downlink signals and the signal levels received by 6

adjacent cells.

22 Clear Code Observation Provides information on dropped calls or handover

problems. There are two possible ways to use this

observation: to observe all failure clear codes under

one BTS or one failure code under the whole BSC.

An observation report is generated every time a

specific clear code occurs, or a clear code occurs in

the observed BTS.

24 Dropped Call Observation (optional) Provides information on dropped calls. An

observation report is generated every time a call is

dropped.

25 TBF Observation for GPRS Trace Collects information on allocations, reallocations,

and releases of Temporary Block Flows (TBF) as

well as changes in the used coding scheme and MS

flow control.





22/22

No Observation/optionality Purpose/function

27 GPRS Cell Reselection Report Trace report for GPRS trace that contains

information about NCCR triggering, NACC usage,

and possible failures.

28 GPRS RX Level and Quality Report Report type needed to record the serving and

neighbour cell measurements and quality data.

29 Drop Call Breakdown Observation (optional) Dissolves the updates of the counters 057044/

001202 DROP AFTER TCH ASSIGN and 002071

CLEAR REQUEST SENT BY BSC ON TCH to get

more accurate data on dropped calls.

30 Position Based Services Observation (optional) Collects detailed information on the positioning

calculation procedure in the BSC. The observation

report is collected for each location procedure of the

ME located in the target cell for the observation.

Related topics

. BSC Statistics Administration

. BSC Measurement Counters Displaying Program (FOXMEA)

. PCU2 Service Terminal Commands

22 (22) N ki C ti DN9813612


performance measurements rel_s12

Documents