01 ra1736en90gls00 0002 introduction

Introduction

RA1736EN90GLS00_0002 © 2007 Nokia Siemens Networks

1

Contents 1 Goals of performance measurements 3 2 Performance measurement concepts and evaluation 11 2.1 Performance Measurement Categories 14 2.2 Performance Measurement Description 16 2.3 Quality of Service (QoS) measurements 20 2.4 Presentation of measurement results 22 2.5 SBS Key Performance Indicators (KPI) 24 3 SBS performance measurements overview 31 3.1 BR9.0 Performance Measurements Administration Groups 32 3.2 BR9.0 performance measurements logically grouped 50 4 Enhancements of performance measurements 69 4.1 Enhancements of BR 9.0 72 5 Siemens Base Station System (SBS) Overview 79 5.1 BSC hardware architecture 82 5.2 BTS hardware architecture 88

Introduction

Introduction

RA1736EN90GLS00_0002© 2007 Nokia Siemens Networks

2

Introduction


3

1 Goals of performance measurements

Introduction


4

The purpose of the process named Performance Measurements is to analyze mobile communication networks in order to evaluate various areas concerning performance issues of mobile communication networks. The process steps to be carried out include collection and analysis of data in order to verify the physical and the logical configuration of the PLMN, to localize potential problems as early as possible, to optimize the current network configuration, etc. The results are applicable in several areas. Related issues concern customer satisfaction, resource efficiency etc. The success of the process has strong impact on the competitiveness of the network operator. Different user groups are targeted by the Performance Measurement Concept. The goal of Performance measurement is mainly dependent on the tasks for network planning, network operation, network optimization and marketing.

Introduction


5

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

PM+ or ext. PM Tool

Management Marketing NetworkOptimization

NetworkOperation

NetworkPlanning

CustomerCare

BSC BSC

Radio Commander

PM PM ConceptConcept -- targettarget groupsgroups::

Fig. 1 PM target groups and relevant tools for purposes of administration and analysis of the process

Introduction


6

There are several main reasons to start performance measurements.

Error Detection and Correction Error sources, e.g. interference, are hardly foreseeable during the planning phase. Conclusions about the actual situation in the radio network can be done with performance measurements. Error detection can be done from point of view of the mobile subscriber and from technical point of view. The following performance indicators are therefore of great interest:

• Call Setup Failure Rate

• Call Drop Rate

• Handover Failure Rate

• Immediate Assignment Failure Rate

• Assignment Failure Rate Traffic Level in the Network This measurement includes the level of both user and signaling traffic in a cell (load on radio interface, usage of radio resources within a cell, user activity, usage of services) which can be used as basic information for constant improvements and expansion of the offered calls. There are the following measurements of great interest:

• TCH traffic load (traffic offered, traffic carried, traffic lost)

• SDCCH traffic load (traffic offered, traffic carried, traffic lost)

• Paging Channel Congestions

• Access Grant Channel Congestions

• CCS7 Load

• Number of call setups

• Number of Handovers

• Number of location updates

Introduction


7

Resource Availability With performance measurements it is possible to find out duration / probability of availability and unavailability of resources dependent on the defined objectives, i.e. life cycle of the system, physical and administrative conditions. E.g. if some traffic channels (TCH) are not available, then it can happen that all other available TCH of a cell are occupied simultaneously, and therefore setup of new speech connections will be unsuccessful. The following resources are mainly of great interest:

• Traffic channels (TCH)

• Slow Dedicated Control Channels (SDCCH)

• BSC, BTS, TRX

• SS7Links

• PCM connections Quality of Service, Grade of Service User of the mobile system experiences the provided quality of service like speech quality, call set-up duration, drop ratio, packet-throughput, etc. By analyzing the measurement data, it is for example possible to:

• calculate the average seizure time of signaling channels (SDCCH)

• conclude about the duration of procedures, e.g. logging into a cell, setup of a connection

• find out the dropped call rate as well as to measure the cell interference's intensity. Network Configuration By analyzing the measurement data, it is for example possible to find out:

• effectiveness of actual plan or planned changes of the network

• traffic level distribution in dependence on area, time etc. Statistic Data For the network operator's marketing department, data about participant's behavior is most interesting. If the measurements show periods of time with very low traffic, it is possible to attract the client to phone at this time of the day with special tariffs. If the measurements show regions with low radio network activity, promotion can be reinforced in these areas.

Introduction


8

Benefit and usage of the performance measurements is summarized in the following figure.

Introduction


9

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

PM Concept

Basics for PM Evaluation Tools

e.g.OTS PM*, Spots, Anatom,Metrica

Basics for PM Evaluation Tools

e.g.OTS PM*, Spots, Anatom,Metrica

Basics forImprovement of Network Quality

Basics forImprovement of Network Quality

Support forNetwork

Optimisation

Support forNetwork

Optimisation

Support forNetworkPlanning

Support forNetworkPlanning

Support forNetwork

Planning Tools

Support forNetwork

Planning Tools

Benefit & Usage

Fig. 2 Summary of benefits and usage of the performance measurement concept

Introduction


10

Introduction


11

2 Performance measurement concepts and evaluation

Introduction


12

TOP DOWN approach for CONCEPTS AND EVALUATION OF NETWORK PERFORMANCE is used. For evaluation of the network performances, first the performance measurement concept has to be defined, including the performance measurements which should run. The required performance measurements are mostly depending on the target groups which are interested in the results. The performance measurement results captured by the different network elements are input for the off line Evaluation Tools. These tools generate the values of the so called Key Performance Indicators (KPI). Note: no single KPI is defined in the GSM recommendations. The process includes several steps:

• Data is required to be produced by the Network Elements (NE),

• This data has to be collected: Performance Management (PM),

• It is further analyzed in a post-processing way,

• The result is mainly presented in form of reports.

In conclusion, the Siemens Performance Measurement Concept yields the full benefit of performance measurement. This is supported by the following criteria:

• Performance measurement will mainly be designed according to customer requirements, standardization requirements (GSM 12.04) and call-processing requirements

• It is planned to be fully compliant to standardization requirements and to enhance the performance measurement system with additional counters according customer and call-processing requirements

• A top down approach will be preferred for the PM design: Requirement => Performance Indicators => Formulas => Counters

• Common Performance Indicators and QoS Parameters are required independent on the Radio Access technology with the goal to give the operators the possibility to compare the performance, capacity and quality of different networks.

Introduction


13

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

CallprocessingRequirements

CallprocessingRequirements

UTRAN Formulas

UTRAN Formulas

UTRAN Counters

UTRAN Counters

GERANFormulas

GERANFormulas

GERANCounters

GERANCounters

PM Customer Requirements- Network Operation - Customer Care- Network Planning - Management- Network Optimisation - Marketing

PM Customer Requirements- Network Operation - Customer Care- Network Planning - Management- Network Optimisation - Marketing

Performance Indicators,QoS Parameters

Performance Indicators,QoS Parameters

CommonCommon SpecificSpecific- Measurements- Messageflows- KPIs- Use cases- Traffic Engineering- Network Planning

- Measurements- Messageflows- KPIs- Use cases- Traffic Engineering- Network Planning

StandardisationRequirements

(GSM 12.04, CWTS, 3GPP TS32.104)

StandardisationRequirements

(GSM 12.04, CWTS, 3GPP TS32.104)

Top down approach

Fig. 3 Top down approach

Introduction


14

2.1 Performance Measurement Categories The types of data to be collected are defined through corresponding measurements. Users can activate these measurements according to their needs. The range of measurements which are available from the NEs covers all of the previous mentioned areas of evaluation. However, not all of these measurements are required all of the time, from every occurrence, of every relevant NE. All SBS Performance Measurements (PM) can be classified into PM categories according to procedures (logical objects) they are oriented to. In the SBS BR9.0 three additional categories of performance measurements have been defined:

• BSC Lb Interface/LCS Related Measurements

• ATM Related Measurements

• Traffic Load Feature Related Measurements.

Introduction


15

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Radio Resource Related Measurements

Call Procedure Related Measurements

Handover Related Measurements

Circuit Switched Features Related Measurements

BSC Related and MS Radio Signal Measurements

GPRS Related Measurements

Abis Interface Measurements

A-interface/SS7 Related Measuremnts

Processor Measurements

BSC Lb_Interface/LCS Related Measurements

ATM Related Measurements

Traffic Load Feature Related Measurements

Miscellaneous Measurements

Categories of Performance Measurements

Fig. 4 Performance Measurements – categories

Introduction


16

2.2 Performance Measurement Description The following structure is used for the description:

• Measurement: indicated with short measurement name (Abbreviation -used in the result files), measurement number and full measurement name

• GSM reference: in case of the A-Interface measurements: ITU Ref.

• Latest modification: the latest release in which a measurement was modified

• Managed Object Class: a logical object such as SCANBTS, SCANBSC, SCANGPRS, SCANTRX, SCANCHAN, etc.

• Administrative Object Class: a command like CREATE, MODIFY or DELETE etc. related to exactly one Managed Object Class

• Measurement depth: a measurement performed per one Measured Object Class, like per BTS, BTSM, BSC, etc.

• Description: a compact description of the measurement

• Changes to previous release: description of the modifications; relevant only for measurements modified since the last release

• Trigger events: a description of the events which cause a measurement data to be updated (the counters update)

• Results: a measurement result (measured value(s), counter number, counter type, unit)

• Counter sequence: only if more than one counter is provided; gives the sequence in which the counters are provided on RC/LMT

• Note: optional, gives additional information about the behavior of the measurement and configuration parameters that impact the counting or that are merely of interest, restrictions, etc.

Introduction


17

Fig. 5 Description of the measurement, e.g. Normal Call Releases of Calls with Bad Radio Quality, Performance Measurement Manual

Introduction


18

2.2.1 Accumulation and assembling of raw data The processes which accumulate data and assemble it for collection and inspection are called measurement jobs. For the administration purposes they are notified as "Scanners" as well. The administration of measurement jobs comprises some actions, e.g. their creation, deletion, modification, or definition of the measurement jobs scheduling. Each measurement job collects data at a particular frequency known as the granularity of the measurement. After the collection it is possible to upload performance data into the Radio Commander system to analyze it. The management of performance measurements consists of two main phases:

• administration of the performance measurement jobs

• collection and storage of performance measurement results. Important terms are included in the scanner structure as sketched in the next figure.

Introduction


19

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Administrativeobject class

Counter

Measurement type...

Counter

Counter

Measurement type...

Counter

...

Counter

Measurement type...

Counter

Counter

Measurement type...

Counter

......

Administrative object class

Fig. 6 Scanner structure

Introduction


20

2.3 Quality of Service (QoS) measurements Observed types are always described in terms of ratios, with a theoretical range between 0 and 100 percent. These ratios are always defined as “negative indicators:” The appropriate alarm is generated when the ratio exceeds the configured threshold.

Introduction


21

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

BSC processor load

-TDPC (BSC1)-MCP (eBSC)-APM (eBSC)-SMAC (eBSC)-LIET (eBSC)-PCU (BSC1/eBSC)

QoS Measurements

CS traffic

- Assignment Failure Rate- Call Set up Failure Rate- HO Drop Rate- HO Failure Rate- Immediate Assignment Failure Rate-SDCCH Drop Rate-SDCCH Loss Rate-TCH Drop Rate-TCH Loss Rate

PS traffic

- Network Control Cell Reselection Failure Rate- TBF Drop Rate- TBF Loss Rate- TBF Reassignment FailureRate

Fig. 7 Quality of Service measurements

Introduction


22

2.4 Presentation of measurement results For evaluation of performance measurements, first a performance measurement concept has to be defined including necessary performance measurements. These necessary performance measurements are mainly dependent on target groups with different interests.

The most important possibilities to show measurement results are:

Online Supervision Therefore a post-processing tool with graphical User Interface (GUI) having the possibility to see statistical values at any time is needed. It is useful in network operation department for fault detection and clearance, performance supervision and much more.

Alarm on Statistic The Quality of Service (QoS) Alarms feature provides the generation of alarm messages starting from specific performance measurements. Thresholds (static and dynamic) will be defined to get alarms for increasing e.g. ''TDPC Processor Load'' or "MCP Processor Load", ''PCU Processor Load'', Call Set up Failure Rate“, ''TCH Drop Rate “. This is mainly used for fault detection in the network operation department.

Performance Measurement Report This is the most common way to see the performance measurement results and is usually used by all departments, which are interested in performance measurement.

Introduction


23

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

n o t i fy H ig h 1

n o t i fy H ig h 2

n o t if y L o w 1

n o t if y L o w 2

b a s ic p e r io d s

s u p e r v i s io n p e r io d s

a la rm _ c o u n te r 1


( 0 )

( 0 )

( 0 )

+ 1 (1 )

+ 1 (1 )

+ 1 (2 )

+ 1 (2 )

+ 1 (3 )

R (0 )

( 3 )

R ( 0 )

R ( 0 )

+ 1 (1 )

+ 1 (1 )

( 1 )

( 1 )

+ 1 (2 )

+ 1 (2 )

+ 1 (3 )

+ 1 (3 )

R (0 )

( 3 )

M e a s u re d v a lu e a t th e e n d o f b a s i c p e r io dM e a n v a lu e th ro u g h s u p e rv i s io n p e r io d

( . . . ) A c c u m u la t io n v a lu e o f a la r m _ c o u n te rR R e s e t o f a la r m _ c o u n te r

A la rm p e n d in g w i th s e v e r i ty 1A la rm p e n d in g w i th s e v e r i ty 2

p e n d in g a la r m

S e v . 2 C le a rS e v . 1 S e v . 1 S e v . 2S e v . 2

p e n d in g a la r m

n o t i fy H ig h 1

n o t i fy H ig h 2

n o ti f y L o w 1

n o ti f y L o w 2

b a s i c p e r io d s

s u p e r v i s io n p e r io d s



(0 )

(0 )

( 0 )

+ 1 (1 )

+ 1 (1 )

+ 1 (2 )

+ 1 (2 )

+ 1 (3 )

R (0 )

( 3 )

R ( 0 )

R ( 0 )

+ 1 (1 )

+ 1 (1 )

( 1 )

( 1 )

+ 1 (2 )

+ 1 (2 )

+ 1 (3 )

+ 1 (3 )

R (0 )

( 3 )

M e a s u re d v a lu e a t th e e n d o f b a s i c p e r io d N = 2 M e a n v a lu e th r o u g h s u p e r v i s io n p e r io d ( . . . ) A c c u m u la t io n v a lu e o f a la rm _ c o u n te r R R e s e t o f a la r m _ c o u n te r A la r m p e n d in g w i th s e v e r i ty 1 A la r m p e n d in g w i th s e v e r i ty 2

p e n d in g a la rm

S e v . 2 C le a r S e v . 1 S e v . 1 S e v . 2 S e v . 2

p e n d in g a la rm

Online SupervisionAlarm-on-Statistics

ReportsPre-defined User- defined

Fig. 8 Common types of performance measurement presentations

Introduction


24

2.5 SBS Key Performance Indicators (KPI)

The SBS Key Performance Indicators are summarized in the Appendix 4. They can be grouped into the following main groups:

• Immediate Assignment Analysis related Performance Indicator (PI)

• SSS Procedure Analysis related PI

• Assignment Analysis related PI

• Call Setup Analysis related PI

• TCH Drop related PI

• SDDCH Drop related PI

• TCH Load related PI

• SDCCH Load related PI

• CCCH Load related PI

• PCCH Load related PI

• Service related PI

• Features related PI*

• Handover related PI

• Power and Quality Measurements related PI

• Availability related PI

• GPRS related PI

• Miscellaneous PI The Key Performance Indicators can be used in a uniform way. It is possible to compare Key Performance Indicators of different networks or to give statements about quality, performance, capacity and more. All listed formulas in the KPIs are valid for one elementary object and for one elementary measurement period. Evaluation of multiple objects and for multiple measurement periods can be done as described in the following pages. Note: * - The KPI introduced in release BR9.0.

Introduction


25

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Introduction


26

2.5.1 Definition of terms Each KPI is described by the following fields:

Long name This field contains the name of the KPI.

Short name This field contains an acronym for the KPI

Description This field contains a short explanation of the KPI.

Formula This field contains the formula for calculation of the KPI.

Counters This field contains the measurement type (job) used for calculation of the KPI. Measurement types (jobs) are described by the short name of the measurement and, in brackets, the index of the used counter. The indices are listed with the following meaning: measType[i] Counter with index #i is used measType[i,j,k] Counters with indices #i, #j, #k are summarized measType[i-j] Counters in the index range #i to #j are summarized measType[all] All counters of the measurement are summarized measType[i][j] Counter related to index #i with sub-counters index #j are used.

E.g. index[j] related to CS defined with index #i.

Elementary object This field contains the measured object class the KPI is applicable to. This is the smallest measurement object which can be used for KPI.

Unit/Range This field contains unit and/or range related to the KPI, e.g. percent, sec or none.

Remark This field contains additional information.

Introduction


27

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

This KPI is not only related to Call Setups. It is related to any TCH seizure ( e.g. incoming Handovers) . Therefore for network optimization it is recommended to use KPI ‘TCH Drops per Erlang’.

Remark

NoneUnit

CellObject

TCHDrop=NRCLRREQ[1…3,5…12,14…18]Counters

TCHDropRate=TCHDrop/SUCTCHSE[1…2]Formula

This indicator provides the rate of all drops of TCH connectionsDescription

TCHDropRateShort name

TCH Drop RateLong name

6.3 TCH Drop Rate

Fig. 9 KPI -definition example

Introduction


28

2.5.2 Aggregation Aggregation shows how to evaluate KPI for multiple objects and multiple elementary periods. Aggregation is a step of pre-processing (performance measurements yield un-processed - i.e. "raw"- data). If a scan (= performance measurement job) is active then one piece of data will be gathered for each elementary period (i.e. granularity period) and each elementary object (depends on the measurement type). Naturally this also applies for the KPIs. Aggregation can be performed in several ways:

DAILY AGGREGATION:

• MAX/min Value

• MAX/min Time

• Mean/Sum daily value (aggregation standard1)

• SPBH (Sample at Peak Busy Hour2)

• SPBH Time

SEVERAL DAYS AGGREGATION:

• MAX/MIN Value

• MAX/MIN Time

• TCMAX/TCMIN (provides time coherent Max/Min values)

• TCMAX/TCMIN Time (provides the starting time related to TCMAX/TCMIN value)

• Mean/Sum Value

• ASPBH Average Sample at Peak Busy Hour

• SPBH Sample value of the KPI at reference BH

• SPBH Time and Date (provides the starting time of the hour and the date of SPBH)

• TCSPBH Time Coherent Sample at Peak Busy Hour

• TCSPBH Time (Time Coherent Sample at Peak Busy Hour Time)

• Mean daily represents the average over a number of days of the mean daily value

• MAX daily represents the max over a number of days of the max daily value.

Introduction


29

Example: It can be required to calculate the attempted traffic channel seizure with the SPBH aggregation function referring to the BSC processor load measurement:

• KPI (Aggregation function [Reference variable])

• ATTCHSEI (SPBH [BSCPRCLD[2]])

1Standard means that the evaluation can be done by adding or averaging the counter values for single objects and single periods in the following way (standard aggregation):

∑=ti,

t)(i, Counter m)(n,Counter t)(i, Counter m)(n, Counter =

i elementary object t elementary period n object (sum of elementary objects) m measurement period (sum of elementary periods) 2The busy hour is the hour in which the reference variable assumes the highest value within one day for a measured object for any performance indicator. When the granularity period is smaller than 1 hour, this value is calculated with the sliding window algorithm. Fig. 10 Aggregation: e.g. daily

Introduction


30

Introduction


31

3 SBS performance measurements overview

Introduction


32

3.1 BR9.0 Performance Measurements Administration Groups

For the administration of the performance measurements and also for the consideration of the kind of objects observed by the specific measurements, it is useful to group them according to so called administration groups. In the SBS BR9.0 release there are, compared to BR8.0, four new administration groups, i. e. their total number is now 18. The new administration groups are:

• SCANDPC

• SCANNSVC

• SCANATMVP

• SCANATMVC. They have associated administration group numbers 14-17, respectively. The table in the next page summarizes the PM Administration Groups. In the column ''No. of PM'' the number in bracket indicates the No of PM of the former release. The SCANDPC contains a set of 12 existing (''old'') measurement types (jobs) related to the A-interface/SS7 that were up to release BR8.0 included in the SCANBSC. The SCANBSC managed object class has been enriched with 21 new PM related to the BSC Interface Enhancements for Location Services Requirements and one new GPRS measurement replacing previously used one. The SCANNSVC contains only one PM providing the mean data throughput per NSVC on the Gb interface. The ATM Performance Monitoring (ITU-T I.610) is achieved inserting specific OAM test cells during the normal cells (user traffic, e.g. user cell) flow. The SCANATMVP and SCANATMVC contain measurements related to the OAM for ATM.

Introduction


33

Administration Group - Object class No.

No. of PM Observed objects

SCANBSC - 0 30 (20) BSC

SCANBTS - 1 74 (70) BTS

SCANBTSE - 2 15 (10) BTSE (BTS Equipment)

SCANBTSIHO - 3 2 Handover relation (BTS Incoming HandOver)

SCANBTSM - 4 2 BTSM (BTS Site Manager)

SCANBTSOHOI - 5 3 Intercell handover relation (BTS Outgoing HandOver to Internal cells)

SCANBTSOHON - 6 3 Inter-BSC handover relation (BTS Outgoing HandOver to Neighbor cells)

SCANCHAN - 7 1 CHAN (channel)

SCANCTRX - 8 5 Correlated TRX (for correlated RX level, RX quality and TA measurement)

SCANGPRS - 9 50 (39) GPRS connections

SCANSS7L - 10 3 SS7L (SS7 Links)

SCANTRX - 11 2 TRX (transceiver)

SCANBTSOHOS - 12 3 Intersystem handover relation (BTS Outgoing HandOvers)

SCANFBTSM - 13 3 (2) Abis Interface

SCANDPC - 14 12 DPC (Destination Point Code)

SCANNSVC - 15 1 NSCV (Network Service Virtual Connection)

SCANATMVP - 16 5 ATMVP (Asynchronous Transfer Mode VirtualPath)

SCANATMVC - 17 4 ATMVC(Asynchronous Transfer Mode VirtualChannel)

Introduction


34

The following figure refers to the 18 different administration groups of 218 performance measurements in BR9.0. The size of the circle’s different parts displayed in the figure corresponds to the number of performance measurements belonging to the specific administration group.

Introduction


35

SCANBSC

SCANBTS

SCANBTSE

SCANBTSIHO

SCANBTSM

SCANBTSOHOI

SCANBTSOHON

SCANCHAN

SCANCTRX

SCANGPRS

SCANSS7L

SCANTRX

SCANBTSOHOS

SCANFBTSM

SCANDPC

SCANNSVC

SCANATMVP

SCANATMVC

Fig. 11 SBS Performance Measurements (grouped according to administration groups) overview

The “Online RF Loopback Measurements” and the “Smart Carrier Allocation Measurements” have a different construction than the other measurements described in this manual. Therefore these two measurements type are not included neither in the above nor in the following tables.

Introduction


36

The Performance Measurements belonging to SCANBSC:

Measurement Abbreviation No. Successful internal handovers SINHOBSC (0,0)

BSC processor load BSCPRCLD (0,13)

Total number of handover failures intra-BSC HOFITABS (0,14)

Number of inter-BSC handover failures NRINHDFL (0,15)

Number of requested incoming intersystem handovers RQIISHDO (0,16)

Number of unsuccessful incoming intersystem handovers UNIISHDO (0,17)

Number of successful incoming intersystem handovers SUIISHDO (0,18)

Min, max, mean number of used PDTs per PCU (instead of former NPDCHPCU)

NPDTPCU (0,19)

Number of Abnormal SCCP Termination by SMLC ABSCPTSM (0,20)

Number of Attempted Location Requests ATTLOCRQ (0,21)

Number of Successful Operation Location Responses SUCLOCRS (0,22)

Number of Unsuccessful Operation Location Response per Cause

UNSLOCRS (0,23)

Number of Abnormal Condition Location Requests per Cause

ABCLOCRQ (0,24)

Number of Attempted Usage Location Requests per Positioning Method

ATTLOCRP (0,25)

Number of Unsuccessful Attempted usage Location Requests per Positioning Method

UATTLOCRP (0,26)

Number of Attempted TA / E-CITA Positioning ATTAPOS (0,27)

Number of Successful TA / E-CITA Positioning SUCTAPOS (0,28)

Number of Unsuccessful TA / E-CITA Positioning UNSTAPOS (0,29)

Number of Reset TA / E-CITA Positioning RESTAPOS (0,30)

Number of Attempted A-GPS / E-OTD RRLP Command ATTAGRRC (0,31)

Number of Successful A-GPS / E-OTD RRLP Response SUCAGRRS (0,32)

Number of Unsuccessful Abort A-GPS / E-OTD RRLP Procedure

UNSAGRRP (0,33)

Introduction


37

Measurement Abbreviation No. Number of Unsuccessful Reject A-GPS / E-OTD RRLP Procedure

UNSRGRRP (0,34)

Number of Reset A-GPS / E-OTD RRLP Procedure RESAGRRP (0,35)

Number of Attempted U-TDOA Request ATTUTREQ (0,36)

Number of Successful U-TDOA Response SUCUTDRS (0,37)

Number of Unsuccessful Abort U-TDOA Positioning UNSAUPOS (0,38)

Number of Unsuccessful Reject U-TDOA Positioning UNSRUPOS (0,39

Number of Reset U-TDOA Positioning RESUTPOS (0,40)

Central Network Service Processor Load CNSPRCLD (0,41)

Introduction


38

The Performance Measurements belonging to SCANBTS (Part 1):

Measurement Abbreviation No. Mean number of busy TCHs MEBUSTCH (1,0)

All available TCH allocated time AALTCHTI (1,1)

Number of lost radio links while using a TCH NRFLTCH (1,2)

Number of lost radio links while using an SDCCH NRFLSDCC (1,3)

Successful internal handovers intracell SINTHITA (1,4)

Total number of accesses by procedures (PCH, AGCH) TACCBPRO (1,5)

Number of accesses with a successful result by procedure (PCH, AGCH, RACH)

NACSUCPR (1,6)

Number of attempted SDCCH seizures in a period NATTSDPE (1,7)

Attempted SDCCH seizures meeting an SDCCH blocked state

ATSDCMBS (1,8)

Attempted immediate assignment procedure ATIMASCA (1,9)

Successful immediate assignment procedure SUIMASCA (1,10)

Mean number of idle TCHs per interference band MEITCHIB (1,11)

Unsuccessful internal handovers intracell UNINHOIA (1,12)

Attempted internal handovers intracell ATINHIAC (1,13)

Attempted internal handovers intercell ATINHIRC (1,14)

Number of available SDCCHs NAVSDCCH (1,15)

Number of available TCHs NAVTCH (1,16)

Total number of TCH connections TNTCHCL (1,17)

Unsuccessful internal handovers intracell with loss of MS UNIHIALC (1,18)

Unsuccessful internal handovers intercell with loss of MS UNIHIRLC (1,19)

All available SDCCHs allocated time ASDCALTI (1,20)

Mean number of busy SDCCHs MBUSYSDC (1,21)

Maximum number of busy SDCCHs MAXBUSDC (1,22)

Total number of assignment attempts TASSATT (1,23)

Total number of successful assignments TASSSUCC (1,24)

Attempted TCH seizures ATTCHSEI (1,25)

Successful TCH seizures SUCTCHSE (1,26)

Introduction


39


Measurement Abbreviation No. Attempted TCH seizures meeting a TCH blocked state ATCHSMBS (1,27)

Mean TCH busy time MTCHBUTI (1,28)

Successful internal handovers intercell SINTHINT (1,29)

Total number of assignment failures TASSFAIL (1,30)

Successful immediate assignments of signaling channels NSUCCHPC (1,31)

Total number of multislot (HSCSD) connections TNMSCNCL (1,32)

Mean TCH queue length (fullrate/halfrate) MTCHQLEN (1,33)

Mean duration a TCH is queued MDURTCRQ (1,34)

Number of messages discarded from the TCH queue NMSGDISQ (1,35)

Number of successful SDCCH seizures in a period NASUSDPE (1,36)

Number of service upgrades/downgrades for HSCSD calls

TNSUDHSC (1,37)

Total number of assignment attempts relevant to VBS/VGCS broadcast/group channels

TASSATVS (1,38)

Total number of successful assignments relevant to VBS/VGCS broadcast/group channels

TASSUCVS (1,39)

Number of new notifications to be sent on the notification channel (NCH)

NNNOTNCH (1,40)

Number of defined TCHs NRDEFTCH (1,41)

Number of defined SDCCHs NDESDCCH (1,42)

Number of handover indications not resulting in a handover attempt

NHOINRHA (1,43)

Number of available TCH/SD NAVTCHSD (1,44)

Number of TCH-SDCCH channel modifications NTCHSDCM (1,45)

Number of defined TCH/SD NDFTCHSD (1,46)

Attempted internal SDCCH handovers intracell AISHINTR (1,47)

Successful internal SDCCH handovers intracell SISHINTR (1,48)

Unsuccessful internal SDCCH handovers intracell UISHINTR (1,49)

Attempted internal SDCCH handovers intercell AISHINTE (1,50)

Successful internal SDCCH handovers intercell SISHINTE (1,51)

Introduction


40


Measurement Abbreviation No. Unsuccessful internal SDCCH handovers intercell UISHINTE (1,52)

Attempted MSC controlled SDCCH handovers AOINTESH (1,53)

Successful MSC controlled SDCCH handovers SOINTESH (1,54)

Unsuccessful MSC controlled SDCCH handovers UOINTESH (1,55)

Mean number of busy TCHs per channel type MBTCHCHT (1,56)

Mean duration a TCH/SD with TCH_SD_Pool can be used as SDCCH

MDURTCSD (1,57)

Number of clear request messages NRCLRREQ (1,58)

Number of clear command messages NRCLRCMD (1,59)

Number of admitted CS speech calls on the DMA layer ACADMCDMA (1,60)

Number of rejected CS speech calls by AC on the DMA layer due to soft blocking and/or due to too high load

ACREJCDMA (1,61)

Total number of unsuccessful SDCCH handovers from one SDCCH to another within the same cell

UISHIALC (1,62)

Number of unsuccessful SDCCH handovers from the observed cell into a different cell managed by the same BSC

UISHIRLC (1,63)

Number of unsuccessful outgoing inter-BSC SDCCH handovers from the observed cell into a different cell managed by a different BSC

UMCSHLC (1,64)

Number of channel allocation requests not served in the highest priority layer or not served at all

CHALNHLY (1,65)

Mean number of busy channels MEBUTSLY (1,66)

Wireless Priority Services (WPS) supervision WPSSUPV (1,67)

Mean number of busy SDCCHs per signaling procedure MBUSYSSP (1,68)

Number of successful SDCCH seizures for USSD signaling

NSUSDSUS (1,69)

Number of TCH Load Events on Um and Abis per cell NTCHLOEV (1,70)

Successful TCH Seizures by ARP capable MS, per cell, per channel type

SUCTCHARP (1,71)

Number of Successful Assignments related to MS with ARP

NASSARP (1,72)

Number of Lost Radio Links while using a TCH related to MS with ARP

NFLTCHARP (1,73)

Introduction


41

The Performance Measurements belonging to SCANBTSE:

Measurement Abbreviation No. Number of invalid RACH messages NINVRACH (2,0)

Number of transmitted and discarded messages on the PCH per cell

NTDMPCH (2,1)

Adaptive multirate channel type (uplink/downlink) distribution

AMRCHDIS (2,2)

Voice activity rate for adaptive multirate on uplink/downlink busy TCHs

AMRVAR (2,3)

Frame measurement for adaptive multirate on uplink busy TCHs

AMRFRMUL (2,4)

Frame measurement for adaptive multirate on downlink busy TCHs

AMRFRMDL (2,5)

SID_UPDATE adaptive multirate on uplink busy TCHs AMRSIDUL (2,6)

Number of transmitted and discarded messages on the AGCH

NTDMAGCH (2,8)

Number of defined, i.e. configured CCCH channels (uplink/downlink) per cell

NDEFCCCH (2,9)

Normal Call Releases of Calls with Bad Radio Quality NCRLBRQU (2,10)

Frame Measurements for AMR only for MS with ARP capability on Uplink Busy TCHs

NFRMULARP (2,11)

Frame Measurements for AMR only for MS with ARP capability on Downlink Busy TCHs

NFRMDLARP (2,12)

BTS Power Measurements on Downlink Busy TCHs MBTSPWR (2,13)

Quality Measurements related to MS with ARP on DL Busy TCHs

RXQUARP (2,14)

FACCH Supervision FACCHSUP (2,15)

Introduction


42

The Performance Measurements belonging to SCANBTSIHO:

Measurement Abbreviation No. Successful incoming internal intercell handovers SININIRH (3,0)

Attempted incoming internal intercell handovers AININIRH (3,1)

The Performance Measurements belonging to SCANBTSM:

Measurement Abbreviation No. BTSE processor load BTSEPRLD (4,0)

I-Frame measurements IFRMABIS (4,1)

The Performance Measurements belonging to SCANBTSOHOI:

Measurement Abbreviation No. Successful outgoing intercell handovers SOUINIRH (5,0)

Attempted outgoing intercell handovers AOUINIRH (5,1)

Unsuccessful internal handovers intercell with reconnection to old channel

UNINHOIE (5,2)

The Performance Measurements belonging to SCANBTSOHON:

Measurement Abbreviation No. Attempted outgoing inter-BSC handovers ATINBHDO (6,0)

Successful outgoing inter-BSC handovers SUINBHDO (6,1)

Number of unsuccessful outgoing inter-BSC handovers NRUNINHD (6,2)

Introduction


43

The Performance Measurements belonging to SCANCHAN:

Measurement Abbreviation No. Power and quality measurements on uplink/downlink busy TCHs

PWRUPDW (7,0)

The Performance Measurements belonging to SCANCTRX:

Measurement Abbreviation No. Correlated RXLEV to RXQUAL measurements (uplink) CRXLVQUU (8,0)

Correlated RXLEV to RXQUAL measurements (downlink) CRXLVQUD (8,1)

Correlated RXLEV to time advance measurements (uplink)

CRXLVTAU (8,2)

Correlated RXLEV to time advance measurements (downlink)

CRXLVTAD (8,3)

Correlated FER to RXQUAL measurements CFERRXQU (8,4)

The Performance Measurements belonging to SCANGPRS (Part 1):

Measurement Abbreviation No. Min, max, mean number of available PDCHs per cell NAVPDCH (9,0)

Number of rejected PDCH assignments (uplink/downlink) per cause

REJPDASS (9,1)

Number of attempted PDCH assignments (uplink/downlink) per cell

NUACATCL (9,2)

Number of successful PDCH seizures (uplink/downlink) per cell

SULACCEL (9,3)

Number of retransmitted PDUs (uplink/downlink) per coding scheme per cell on the RF interface

NRETPDU (9,4)

Number of transmitted and discarded messages on the PPCH per cell

NTDMPPCH (9,5)

Number of successful GPRS paging procedures NSUGPPAG (9,6)

Introduction


44


Measurement Abbreviation No. Mean user data throughput (uplink/downlink) per coding scheme per cell on the RF interface

MUTHRF (9,7)

Mean signaling data throughput (uplink/downlink) per cell on the RF interface

MSTHRF (9,8)

Mean user data throughput (uplink/downlink) per cell on the BSSGP layer Gb

MUTHBS (9,9)

Mean signaling data throughput (uplink/downlink) per cell on the BSSGP layer GB interface

MSTHBS (9,10)

Number of attempted packet resource reassignments (uplink/downlink) per cell

NATPRRE (9,11)

Number of successful packet resource reassignments (uplink/downlink) per cell

NSUPRRE (9,12)

Total and mean number of active TBFs (uplink/downlink) per cell

NACTTBF (9,13)

Number of attempted GPRS accesses per cell with no GPRS radio resources allocated

TANRGPRS (9,16)

Retransmitted mean user data throughput (uplink/downlink) per coding scheme per cell on the RF interface

REMUTHRF (9,18)

Number of transmitted PDUs (uplink/downlink) per coding scheme per cell on the RF interface

NTRAPDU (9,19)

Link adaption measurements (uplink/downlink) per cell LADAPTUD (9,20)

Service upgrade/downgrade measurements (uplink/downlink) per cell

SERVUGDG (9,21)

Number of transmitted LLC frames (uplink/downlink) per cell on the BSSGP layer GB interface

NTRLLCFR (9,22)

Min, max, mean number of defined (configured) PDCHs per cell

NDEFPDCH (9,23)

Min, max, mean number of activated PDCHs per cell NALIPDCH (9,24)

Min, max, mean number of used (active TBF) PDCHs (uplink/downlink) per cell

NALLPDCH (9,25)

Max, mean number of TBFs allocated per PDCH (uplink/downlink) per cell

NTBFPDC (9,26)

Introduction


45


Measurement Abbreviation No. Number of transmitted and discarded messages on the PAGCH per cell

NTDMPAGC (9,28)

Number of successful PDCH assignments (uplink/downlink) per cell

SUCPDASA (9,29)

Number of degraded PDCH seizures (uplink/downlink) per cell

UNSPDCSE (9,30)

Number of successful terminated TBFs (uplink/downlink) per cell

SUCTETBF (9,31)

Number of received FLUSH-PDUs on Gb per cell NRRFPDU (9,32)

Number of unsuccessful terminated TBFs (uplink/downlink) per cell per cause

UNSTETBF (9,33)

Number of discarded LLC PDU per cell DISCLPDU (9,35)

Cell reselection attempts ATCRORIG (9,36)

Cell reselection successful procedure SUCRORIG (9,37)

Cell reselection unsuccessful procedure UNCRORIG (9,38)

DL LLC PDU queues filling level per cell LLCQULEV (9,39)

Number of defined, i.e. statically configured, PCCCH frames (uplink/downlink) per cell

NDEFPCCC (9,40)

Number of accesses to the PRACH channel NSAPRACH (9,41)

Weighted user data throughput (uplink/downlink) per traffic class per cell on the BSSGP layer Gb interface

WUTHBS (9,42)

LLC user data throughput (uplink/downlink) per cell per traffic class

MUTLLC (9,43)

Introduction


46

The Performance Measurements belonging to SCANGPRS (Part 4, all counter introduced in BR9.0)):

Measurement Abbreviation No. Mean Outage Time between Downlink LLC Buffer Discard and Subsequent of Downlink LLC PDU

LLCSUBST (9,44)

Min, Mean and Max Access Delay of a first LLC PDU MMADFLLC (9,53)

Radio Access RTT for DL RLC PDU’s per cell MMRARTT (9,54)

Number of Attempted PDCH Assignments (Uplink/Downlink) with ARP Priority per Cell

ARPAPDAS (9,45)

Number of Successful PDCH Assignments (Uplink/Downlink) per Cell

ARPSPDAS (9,46)

Number of Attemps to Establish a DTM (UL/DL) per Cell ATDTMREQ (9,47)

Number of Successful Requests to Establish a DTM (UL/DL)

SUDTMREQ (9,48)

Number od Unsuccessful requests to establish a DTM (UL/DL)

UNSDTMREQ (9,49)

GTTP Throughput MGTTPTH (9,50)

TBF Resource Assignment Rate TBFRASSR (9,51)

Number of Real Time PFC Admitted and Rejected NUMPFCADMREJ (9,52)

Introduction


47

The Performance Measurements belonging to SCANSS7L:

Measurement Abbreviation No. Duration of link “In-Service” state DLKSERST (10,0)

Duration of signaling link unavailability DSLUNAV (10,1)

Signaling link failure - all reasons SLFAILAL (10,2)

The Performance Measurements belonging to SCANTRX:

Measurement Abbreviation No. Interference measurements on idle TCHs ILUPLKIC (11,0)

Transceiver available time TRANAVTI (11,1)

The Performance Measurements belonging to SCANBTSOHOS:

Measurement Abbreviation No. Number of attempted outgoing intersystem handovers ATOISHDO (12,0)

Number of successful outgoing intersystem handovers SUOISHDO (12,1)

Number of unsuccessful outgoing intersystem handovers UNOISHDO (12,2)

The Performance Measurements belonging to SCANFBTSM:

Measurement Abbreviation No. Abis pool distribution ABISPDIS (13,0)

Abis pool supervision ABISPSUP (13,1)

I-frame measurement on Abis-interface on BSC side IFRMABSC (13,2)

Introduction


48

The Performance Measurements belonging to SCANDPC:

Measurement Abbreviation No. Total number of messages received TMSGREC (14,0)

Total number of messages handled TMSHHDL (14,1)

Routing failure, DPC unavailable RFDBCUN (14,2)

Routing failure, subsystem unavailable RFSUBUN (14,3)

Total number of connectionless messages received

TCMSGREC (14,4)

Total number of connectionless messages sent TCMSGSND (14,5)

Number of message signal units (MSUs) transmitted

NMSUTRAS (14,6)

Number of message signal units (MSUs) received NMSUREC (14,7)

Number of locally generated automatic changeovers

LOCAUTCH (14,8)

Duration of the linkset unavailable conditions DLKUNCON (14,9)

Number of transitions of the adjacent signaling point from “Available” to “Unavailable”

NASPAVUN (14,10)

Duration of the adjacent signaling point unavailable condition

DASPUNT (14,11)

The Performance Measurements belonging to SCANNVSC:

Measurement Abbreviation No. Utilization of fame relay links on the Gb interface per NSVC

MFRLDATA (15,0)

Introduction


49

The Performance Measurements belonging to SCANATMVP:

Measurement Abbreviation No. Number of incoming cells ATMVPINCCEL (16,0)

Number of outgoing cells ATMVPOUTCEL (16,1)

Number of incoming OAM cells ATMVPINCOAM (16,2)

Number of outgoing cells ATMVPOUTOAM (16,3)

Usage Ratio of the VP ATMVPCONGES (16,6)

The Performance Measurements belonging to SCANATMVC:

Measurement Abbreviation No. Number of incoming cells ATMVCINCCEL (17,0)

Number of outgoing cells ATMVCOUTCEL (17,1)

Number of incoming OAM cells ATMVCINCOAM (17,2)

Number of outgoing cells ATMVCOUTOAM (17,3)

Introduction


50

3.2 BR9.0 performance measurements logically grouped

The following figure refers to the 13 different logical groups of the BR9.0 performance measurements. The size of the circle’s different parts displayed in the figure corresponds to the number of performance measurements belonging to the specific logical group.

Introduction


51

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1

2

3

4

5

6

7

8

9

10

11

12

13

Radio ResourceCall ProcedureHandover

BSC Related and MS SignalGPRSAbisA interface / SS7Processor LoadBSC Lb interface / LCSATMTraffic Load FeatureMiscellaneous Measurements

Circuit Switched Feature

Fig. 12 SBS Performance Measurements (logically grouped) overview

Introduction


52

The PM logical groups contain further subgroups, which are listed below:

• Radio Resource Related Performance Measurements TCH related measurements SDCCH related measurements TCH/SD related measurements CCCH/PCCCH related measurements

• Call Procedure Related Performance Measurements TCH and SDCCH assignment related measurements Release and loss of dedicated connections (TCH, SDCCH) related measurements

• Handover Related Performance Measurements Internal intracell handover related measurements Internal intercell handover related measurements MSC controlled handover related measurements Intersystem handover related measurements Other handover related measurements

• Circuit-Switched Feature Related Performance Measurements HSCSD related measurements Queuing related measurements AMR related measurements ASCI related measurements DMA related measurements Wireless Priority Service related measurement

• BSC and MS Radio Signal Measurements Related Performance Measurements Idle channel measurements related measurements Power and quality measurements related measurements Correlated radio signal measurements related measurements

• GPRS Related Performance Measurements GPRS radio resource related measurements Gb interface related measurements Cell reselection related measurements

Introduction


53

• Abis Interface Related Performance Measurements Abis pool distribution related measurements Abis I-Frames related measurements

• A Interface / SS7 Related Performance Measurements SCCP related measurements MTP related measurements

• Processor Related Performance Measurements BSC processor load related measurements BTSE processor load related measurements

• BSC Lb-Interface / LCS Related Measurements Abnormal SCCP termination by SMLC Location request procedure TA / E-CITA positioning procedures A-GPS / E-OTD RRLP procedures U-TDOA positioning procedures

• ATM Related Measurements Counters related to virtual path Counters related to virtual channel

• Traffic Load Feature Related Measurements Abis-Interface measurements

• Miscellaneous Performance Measurements Transceiver availability related measurements Counters related to service dependent channel allocation

• RF Loopback Measurements

• Smart Carrier Allocation Measurements SCA normal measurement SCA busy cumulative measurement SCA extended idle channel measurement

Introduction


54

The following tables show the Radio Resource Related Performance Measurements:

TCH related measurements

Measurement No. Administration group

NRDEFTCH (1,41) SCANBTS Counters related to TCH availability

NAVTCH (1,16) SCANBTS

MEBUSTCH (1,0) SCANBTS

MBTCHCHT (1,56) SCANBTS

Counters related to busy TCHs

MTCHBUTI (1,28) SCANBTS

ATTCHSEI (1,25) SCANBTS

SUCTCHSE (1,26) SCANBTS

ATCHSMBS (1,27) SCANBTS

Counters related to TCH seizure

TNTCHCL (1,17) SCANBTS

(Counter related to ARP capable MS TCH seizure)

SUCTCHARP (1,71) SCANBTS

Counter related to TCH blocking time AALTCHTI (1,1) SCANBTS

DCCH related measurements


NDESDCCH (1,42) SCANBTS Counters related to SDCCH availability

NAVSDCCH (1,15) SCANBTS

MBUSYSDC (1,21) SCANBTS Counters related to busy SDCCH

MAXBUSDC (1,22) SCANBTS

NATTSDPE (1,7) SCANBTS

NASUSDPE (1,36) SCANBTS

ATSDCMBS (1,8) SCANBTS

MBUSYSSP (1,68) SCANBTS

Counters related to SDCCH seizure

NSUSDSUS (1,69) SCANBTS

Counters related to SDCCH blocking time

ASDCALTI (1,20) SCANBTS

Counters related to FACCH supervision FACCHSUP (2,15) SCANBTSE

Introduction


55

TCH/SD related measurements


NDFTCHSD (1,46) SCANBTS Counters related to TCH/SD (TCH_SD_POOL) availability NAVTCHSD (1,44) SCANBTS

NTCHSDCM (1,45) SCANBTS Counters related to TCH/SD smooth channel modification MDURTCSD (1,57) SCANBTS

CCCH/PCCCH related measure-mints


TACCBPRO (1,5) SCANBTS Counters related to access and seizure of RACH, AGCH and PCH NACSUCPR (1,6) SCANBTS

Counters related to packet common control channel usage

NSUGPPAG (9,6) SCANGPRS

NTDMPCH (2,1) SCANBTSE Counters related to PCH and PPCH load and overload NTDMPPCH (9,5) SCANGPRS

NTDMAGCH (2,8) SCANBTSE Counters related to AGCH and PAGCH load and overload NTDMPAGC (9,28) SCANGPRS

Counters related to invalid RACH and PRACH accesses

NINVRACH (2,0) SCANBTSE

NDEFCCCH (2,9) SCANBTSE Counters related to define CCCH channels/PCCCH frames NDEFPCCC (9,40) SCANGPRS

Counters related to define PRACH channels

NSAPRACH (9,41) SCANGPRS

Introduction


56

The following tables show the Call Procedure Related Performance Measurements:

TCH and SDCCH assignment related measurements


ATIMASCA (1,9) SCANBTS

SUIMASCA (1,10) SCANBTS

Counters related to immediate assignment procedure

NSUCCHPC (1,31) SCANBTS

TASSATT (1,23) SCANBTS

TASSSUCC (1,24) SCANBTS

TASSFAIL (1,30) SCANBTS

Counters related to assignment procedure (Counter related to ARP capable MS assignment procedure) NASSARP (1,72) SCANBTS

Release and loss of dedicated connections (TCH, SDCCH) related measurements


NRCLRREQ (1,58) SCANBTS

NRCLRCMD (1,59) SCANBTS

Counters related to normal and abnormal BSSMAP release of connected resources

NCRLBRQU (2,10) SCANBTSE

NRFLTCH (1,2) SCANBTS Counters related to call drops indicated for TCH (Counter related to call drops indicated for TCH used by ARP capable MS)

NFLTCHARP (1,73) SCANBTS

Counters related to call drops indicated for SDCCH

NRFLSDCC (1,3) SCANBTS

UNIHIALC (1,18) SCANBTS Counters related to call drops during BSC controlled internal handover UNIHIRLC (1,19) SCANBTS

Introduction


57

The following tables show the Handover Related Performance Measurements:

Internal intracell handover related measurements


ATINHIAC (1,13) SCANBTS

SINTHITA (1,4) SCANBTS

Counters related to internal intracell handover

UNINHOIA (1,12) SCANBTS

AISHINTR (1,47) SCANBTS

SISHINTR (1,48) SCANBTS

UISHINTR (1,49) SCANBTS

Counters related to internal intracell SDCCH handover

UISHIALC (1,62) SCANBTS

Internal intercell handover related measurements


ATINHIRC (1,14) SCANBTS Counters related to internal intercell handover SINTHINT (1,29) SCANBTS

AOUINIRH (5,1) SCANBTSOHOI

SOUINIRH (5,0) SCANBTSOHOI

Counters related to outgoing internal intercell handovers per neighbor cell relationship

UNINHOIE (5,2) SCANBTSOHOI

AININIRH (3,1) SCANBTSIHO Counters related to incoming intercell handovers per neighbor cell relationship SININIRH (3,0) SCANBTSIHO

AISHINTE (1,50) SCANBTS

SISHINTE (1,51) SCANBTS

UISHINTE (1,52) SCANBTS

Counters related to internal intercell SDCCH handover

UISHIRLC (1,63) SCANBTS

Introduction


58

MSC controlled handover related measurements


ATINBHDO (6,0) SCANBTSOHON

SUINBHDO (6,1) SCANBTSOHON

Counters related to outgoing inter-BSC handovers per neighbor cell relationship

NRUNINHD (6,2) SCANBTSOHON

AOINTESH (1,53) SCANBTS

SOINTESH (1,54) SCANBTS

UOINTESH (1,55) SCANBTS

Counters related to MSC controlled SDCCH handover

UMCSHLC (1,64) SCANBTS

Counters related to unsuccessful inter-BSC HANDOVER REQUEST procedures

NRINHDFL (0,15) SCANBSC

Intersystem handover related measurements


ATOISHDO (12,0) SCANBTSOHOS

SUOISHDO (12,1) SCANBTSOHOS

Counters related to outgoing intersystem handover

UNOISHDO (12,2) SCANBTSOHOS

RQIISHDO (0,16) SCANBSC

UNIISHDO (0,17) SCANBSC

Counters related to incoming intersystem handover

SUIISHDO (0,18) SCANBSC

Other handover related measurements


Counters related to successful internal handovers in the BSC

SINHOBSC (0,0) SCANBSC

Counters related to failed internal handovers in the BSC

HOFITABS (0,14) SCANBSC

Counters related to handover indications without handover attempt

NHOINRHA (1,43) SCANBTS

Introduction


59

The following tables show the Circuit-Switched Feature Related Performance Measurements:

HSCSD related measurements Measurement No. Administration group

Counters related to HSCSD connections

TNMSCNCL (1,32) SCANBTS

Counters related to HSCSD upgrades/downgrades

TNSUDHSC (1,37) SCANBTS

Queuing related measurements Measurement No. Administration group

Counters related to queue length MTCHQLEN (1,33) SCANBTS

Counters related to queuing duration MDURTCRQ (1,34) SCANBTS

Counters related to TCH requests discarded from

NMSGDISQ (1,35) SCANBTS

AMR related measurements Measurement No. Administration group

Counters related to AMR channel type distribution

AMRCHDIS (2,2) SCANBTSE

Counters related to AMR voice activity rate

AMRVAR (2,3) SCANBTSE

AMRFRMUL (2,4) SCANBTSE

AMRFRMDL (2,5) SCANBTSE

NFRMULARP (2,11) SCANBTSE

Counters related to AMR frame measurements (Counters related to AMR frames measurements for the MS with ARP capabilities)

NFRMDLARP (2,12) SCANBTSE

Counters related to AMR uplink SID_UPDATE

AMRSIDUL (2,6) SCANBTSE

Introduction


60

ASCI related measurements Measurement No. Administration group

TASSATVS (1,38) SCANBTS Counters related to VBS/VGCS assignment TASSUCVS (1,39) SCANBTS

Counters related to notifications sent via NCH

NNNOTNCH (1,40) SCANBTS

Another Circuit-Switched Feature Related Measurements


ACADMCDMA (1,60) SCANBTS DMA admission control related measurements ACREJCDMA (1,61) SCANBTS

Wireless priority services related measurements per cell

WPSSUPV (1,67) SCANBTS

The following tables show the BSC and MS Radio Signal Measurements Related Performance Measurements:


MEITCHIB (1,11) SCANBTS Counters for idle channel measurement

ILUPLKIC (11,0) SCANTRX

Counters for power and quality measurements

PWRUPDW (7,0) SCANCHAN

CRXLVQUU (8,0) SCANCTRX

CRXLVQUD (8,1) SCANCTRX

CRXLVTAU (8,2) SCANCTRX

CRXLVTAD (8,3) SCANCTRX

Counters for correlated radio signal measurements

CFERRXQU (8,4) SCANCTRX

Introduction


61

The following tables show the GPRS Related Performance Measurements:

GPRS radio resource related measurements


NDEFPDCH (9,23) SCANGPRS

NAVPDCH (9,0) SCANGPRS

NALIPDCH (9,24) SCANGPRS

Packet channel configuration measurements

NALLPDCH (9,25) SCANGPRS

REJPDASS (9,1) SCANGPRS

NUACATCL (9,2) SCANGPRS

SUCPDASA (9,29) SCANGPRS

SULACCEL (9,3) SCANGPRS

UNSPDCSE (9,30) SCANGPRS

NATPRRE (9,11) SCANGPRS

NSUPRRE (9,12) SCANGPRS

LLCSUBST (9,44) SCANGPRS

ARPAPDAS (9,45) SCANGPRS

ARPSPDAS (9,46) SCANGPRS

TBFRASSR (9,51) SCANGPRS

Packet flow establishment measurements

NUMPFCADMREJ (9,52) SCANGPRS

MUTHRF (9,7) SCANGPRS

REMUTHRF (9,18) SCANGPRS

MSTHRF (9,8) SCANGPRS

NTRAPDU (9,19) SCANGPRS

NRETPDU (9,4) SCANGPRS

LADAPTUD (9,20) SCANGPRS

SERVUGDG (9,21) SCANGPRS

NTBFPDC (9,26) SCANGPRS

NACTTBF (9,13) SCANGPRS

MUTLLC (9,43) SCANGPRS

*NPDTPCU (0,19) SCANBSC

MMADFLLC (9,53) SCANGPRS

Active packet flow measurements

MMRARTT (9,54) SCANGPRS

Introduction


62

GPRS related measurements Measurement No. Administration group

MBTSPWR (2,13) SCANBTSE Active packet flow measurements (Counters related to Quality Measurements for the MS with ARP capabilities)

RXQUARP (2,14) SCANBTSE

SUCTETBF (9,31) SCANGPRS

NRRFPDU (9,32) SCANGPRS

UNSTETBF (9,33) SCANGPRS

Packet flow release measurement

TANRGPRS (9,16) SCANGPRS

MUTHBS (9,9) SCANGPRS

MSTHBS (9,10) SCANGPRS

NTRLLCFR (9,22) SCANGPRS

DISCLPDU (9,35) SCANGPRS

LLCQULEV (9,39) SCANGPRS

WUTHBS (9,42) SCANGPRS

Gb interface related measurements

MFRLDATA (15,0) SCANNSVC

ATCRORIG (9,36) SCANGPRS

SUCRORIG (9,37) SCANGPRS

Cell Reselection related measurements

UNCRORIG (9,38) SCANGPRS

ATDTMREQ (9,47) SCANGPRS

SUDTMREQ (9,48) SCANGPRS

UNSDTMREQ (9,49) SCANGPRS

DTM related measurements

MGTTPTH (9,50) SCANGPRS

* The counter replaces the old one, NPDCHPCU.

Introduction


63

The following tables show the Abis Interface Related Performance Measurements:

Abis pool distribution related measurements


ABISPDIS (13,0) SCANFBTSM (no subgroup)

ABISPSUP (13,1) SCANFBTSM

Abis I-Frames related measurements


IFRMABIS (4,1) SCANBTSM (no subgroup)

IFRMABSC (13,2) SCANFBTSM

Introduction


64

The following tables show the A Interface / SS7 Related Performance Measurements:

SCCP related measurements Measurement No. Administration group

TMSGREC (14,0) SCANDPC

TMSHHDL (14,1) SCANDPC

TCMSGSND (14,5) SCANDPC

Counters related to received and transmitted SCCP messages

TCMSGREC (14,4) SCANDPC

RFDBCUN (14,2) SCANDPC Counters related to SSCP message routing RFSUBUN (14,3) SCANDPC

MTP related measurements Measurement No. Administration group

NMSUREC (14,7) SCANDPC Counters related to received and transmitted SS7 MSUs NMSUTRAS (14,6) SCANDPC

Counters related to SS7 link changeover procedures

LOCAUTCH (14,8) SCANDPC

NASPAVUN (14,10) SCANDPC Counters related to adjacent signaling point (ASP) availability DASPUNT (14,11) SCANDPC

DLKSERST (10,0) SCANSS7L

DSLUNAV (10,1) SCANSS7L

DLKUNCON (14,9) SCANDPC

Counters related to SS7 link and linkset availability

SLFAILAL (10,2) SCANSS7L

Introduction


65

The following tables show the Processor Related Performance Measurements:

BSC processor load related measurements


BSC processors Load BSCPRCLD (0,13) SCANBSC

Central Network Service Functionality Load

CNSPRCLD (0,41) SCANBSC

BTSE processor load related measurements


(no subgroup) BTSEPRLD (4,0) SCANBTSM

The following tables show the BSC Lb Interface / LCS Related Measurements:

Abnormal SCCP termination by SMLC


(no subgroup) ABSCPTSM (0,20) SCANBSC

Location request procedure Measurement No. Administration group

ATTLOCRQ (0,21) SCANBSC

SUCLOCRS (0,22) SCANBSC

UNSLOCRS (0,23) SCANBSC

ABCLOCRQ (0,24) SCANBSC

ATTLOCRP (0,25) SCANBSC

UATTLOCP (0,26) SCANBSC


ATTAPOS (0,27) SCANBSC

SUCTAPOS (0,28) SCANBSC

UNSTAPOS (0,29) SCANBSC

TA / E-CITA positioning procedures

RESTAPOS (0,30) SCANBSC

Introduction


66

A-GPS / E-OTD RRLP procedures Measurement No. Administration group

ATTAGRRC (0,31) SCANBSC

SUCAGRRS (0,32) SCANBSC

UNSAGRRP (0,33) SCANBSC

UNSRGRRP (0,34) SCANBSC

RESAGRRP (0,35) SCANBSC

U-TDOA positioning procedures Measurement No. Administration group

ATTUTREQ (0,36) SCANBSC

SUCUTDRS (0,37) SCANBSC

UNSAUPOS (0,38) SCANBSC

UNSRUPOS (0,39) SCANBSC

RESUTPOS (0,40) SCANBSC

The following tables show the ATM Related Measurements Measurement No. Administration

group ATMVPINCCEL (16,0) SCANATMVP

ATMVPOUTCEL (16,1) SCANATMVP

ATMVPINCOAM (16,2) SCANATMVP

ATMVPOUTOAM (16,3) SCANATMVP

Counters related to virtual path

ATMVPCONGES (16,6) SCANATMVP

ATMVCINCCEL (17,0) SCANATMVC

ATMVCOUTCEL (17,1) SCANATMVC

ATMVCINCOAM (17,2) SCANATMVC

Counters related to virtual channel

ATMVCOUTOAM (17,3) SCANATMVC

Introduction


67

The following tables show the Traffic Load Feature Related Measurements:

Abis-Interface measurements Measurement No. Administration group

(no subgroup) NTCHLOEV (1,70) SCANBTS

The following table shows the Miscellaneous Performance Measurement: Transceiver availability related measurements


(no subgroup) TRANAVTI (11,1) SCANTRX

Counters related to service dependent channel allocation


CHALNHLY (1,65) SCANBTS (no subgroup)

MEBUTSLY (1,66) SCANBTS

Introduction


68

Introduction


69

4 Enhancements of performance measurements

Introduction


70

In the following sections the enhancements of performance measurements for the releases BR9.0 are summarized. The enhancements of a certain release are always described with respect to the previous release. In general the following principle enhancements may appear:

• Addition of new performance measurements

• Addition of new managed object classes

• Extension or modification of (already existing) performance measurements

• Renaming of (existing) performance measurements

• Replacement of performance measurements

• Deletion of performance measurements.

Introduction


71

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4

55

41

1 20

10

20

30

40

50

60

1

New Scanners

New Measurements

Modified/EnhancedMeasurementsReplacedMeasurementsDeleted Measurements

Fig. 13 The enhancement of BR9.0 Performance Measurements

Introduction


72

4.1 Enhancements of BR 9.0

4.1.1 New scan object classes There are four new scanner object classes which have been introduced in BR9.0:

• SCANDPC (Id=14) The SCANDPC contains a set of 12 existing measurement types (jobs) related to the A-interface/SS7 that were up to release BR8.0 included in the SCANBSC.

• SCANNSVC (Id=15) The SCANNSVC contains only one PM providing the mean data throughput per NSVC on Gb interface.

• SCANATMVP (Id=16)

• SCANATMVC (Id=17) ATM Performance Monitoring (ITU-T I.610) is achieved by inserting the specific OAM test cells during the normal cells (user traffic, e.g. user cell) flow. The SCANATMVP and SCANATMVC contain measurements related to the OAM for ATM.

Introduction


73

4.1.2 New measurements

Name and ID Short Description ABCLOCRQ (0,24) provides the number of abnormal condition location requests

per cause

ABSCPTSM (0,20) provides the number of abnormal signaling common control part (SCCP) termination by SMLC

ARPAPDAS (9,45) provides the number of GPRS related resource requests with ARP priority 1, 2 or 3 in both uplink and downlink direction

ARPSPDAS (9,46) provides the number of GPRS related assignments with ARP priority 1, 2 or 3 of both uplink and downlink TBF

ATDTMREQ (9,47) provides the number of attempts to establish a DTM (uplink/downlink) per cell

ATMVCINCCEL (17,0)

provides the number of incoming cells

ATMVCINCOAM (17,2)

provides the number of incoming OAM cells

ATMVCOUTCEL (17,1))

provides the number of outgoing cells

ATMVCOUTOAM (17,3)

provides the number of outgoing OAM cells

ATMVPCONGES (16,6)

provides the usage ratio of the VP (virtual path)

ATMVPINCCEL (16,0)

provides the number of incoming cells

ATMVPINCOAM (16,2)

provides the number of incoming OAM cells

ATMVPOUTCEL (16,1)

provides the number of outgoing cells

ATMVPOUTOAM (16,3)

provides the number of outgoing OAM cells

ATTAGRRC (0,31) provides the number of attempted A-GPS/E-OTD RRLP commands

ATTLOCRQ (0,21) provides the number of attempted location requests

ATTLOCRP (0,25) provides the number of attempted usage location requests per positioning method

Introduction


74

Name and ID Short description ATTAPOS (0,27) provides the number of attempted timing advance/enhanced cell

ID/TA (TA/E-CITA) positioning requests

ATTUTREQ (0,36) provides the number of attempted U-TDOA requests

FACCHSUP (2,15) provides the number of transmitted I, UI and UA frames and the number of the belonging transmitted FACCH blocks

CNSPRCLD (0,41) provides the prime time, the total time and the maximum total time information for the CNS functionality

IFRMABSC (13,2) provides information about the transmission of I-Frames on the Abis-Interface on BSC side

LLCSUBST (9,44) provides the mean outage time between downlink LLC buffer discard and subsequent start of a downlink LLC PDU transmission towards the same MS

MBTSPWR (2,13) provides the mean BTS power used to operate DL busy TCHs

MFRLDATA (15,0) provides the mean data throughput per NSVC on the Gb interface

MGTTPTH (9,50) provides the GTTP throughput

MMADFLLC (9,53) provides the minimum, mean and maximum access delay for a first LLC PDU (DL) per traffic class

MMRARTT (9,54) provides the minimum, mean and maximum radio access round trip time (RA RTT) for DL RLC PDUs

NASSARP (1,72) provides the total number of successful assignments of traffic and signaling channels by the BSC related to MS with ARP capability

NCRLBRQU (2,10) provides the number of normal call releases of calls with bad radio quality

NFRLTCHARP (1,73)

provides the total number of lost connections related to MS with ARP capability, which were using a TCH

NFRMDLARP (2,12)

provides the true downlink FER distribution for AMR only for MS with ARP capability

NFRMULARP (2,11)

provides the true uplink FER distribution for AMR only for MS with ARP capability

NPDTPCU (0,19) former NPDCHPCU) provides the number of used PDTs per PCU

NTCHLOEV (1,70) provides the number of times a high load situation on TCH or Abis subchannel (SUBTSLB) caused a specific system reaction

Introduction


75

Name and ID Short Description NUMPFCADMREJ (9,52)

provides the number of admitted and rejected real time packet flow contexts (RT PFCs)

RESAGRRP (0,35) provides the number of reset A-GPS/E-OTD RRLP procedures

RESTAPOS (0,30) provides the number of reset timing advance/enhanced cell ID/TA (TA/E-CITA) positioning

RESUTPOS (0,40) provides the number of reset U-TDOA positioning

RXQUARP (2,14) provides the number of times when a certain received bit error rate (RXQUAL value) was reported for a specific TCH

SUCAGRRS (0,32) provides the number of successful A-GPS/E-OTD RRLP responses

SUCLOCRS (0,22) provides the number of successful operation location responses

SUCTAPOS (0,28) provides the number of successful timing advance/enhanced cell ID/TA (TA/E-CITA) positioning

SUCTCHARP (1,71)

provides the total number of successful TCH assignments within a cell related to MS with downlink ARP capability set

SUCUTDRS (0,37) provides the number of successful U-TDOA responses

SUDTMREQ (9,48) provides the number of successful requests to establish a DTM (uplink/downlink)

TBFRASSR (9,51) provides the TBF resource assignment rate related for uplink and downlink direction and per traffic class (interactive, background)

UATTLOCP (0,26) provides the number of unsuccessful attempted usage location requests per positioning method

UNSAGRRP (0,33) provides the number of unsuccessful abort A-GPS/E-OTD RRLP procedures

UNSAUPOS (0,38) provides the number of unsuccessful abort U-TDOA positioning

UNSDTMREQ (9,49)

provides the number of unsuccessful requests to establish a DTM (uplink/downlink)

UNSLOCRS (0,23) provides the number of unsuccessful operation location responses per cause

UNSRGRRP (0,34) provides the number of unsuccessful reject A-GPS/E-OTD RRLP procedures

UNSRUPOS (0,39) provides the number of unsuccessful reject U-TDOA positioning

UNSTAPOS (0,29) provides the number of unsuccessful timing advance/enhanced cell ID/TA (TA/E-CITA) positioning

Introduction


76

4.1.3 Extended or modified measurements

Name and ID Short Description AININIRH (3,1) extended by 4 new counters for DTM forced handover

AOUINIRH (5,1) extended by 4 new counters for DTM forced handover

ATCHSMBS (1,27) extended by 2 new counters for blocked TCH seizures due to lack of free Abis subchannels (SUBTSLB)

ATINBHDO (6,0) extended by 1 new counters for DTM forced handover

ATINHIRC (1,14 extended by 1 new counters for DTM forced handover

ATOISHDO (12,0) extended by 1 new counters for DTM forced handover

BSCPRCLD (0,13) extended by several counters to provide information about other boards load

DASPUNT (14,11) measurement was moved from the scanner class SCANBSC to the new scanner class SCANDPC and the number of counters was decreased by 1 to now 1 counter

DISCLPDU (9,35) three counters related to the Gb interface congestion (uplink) were deleted because they are not provided anymore

DLKUNCON (14,9) measurement was moved from the scanner class SCANBSC to the new scanner class SCANDPC and the number of counters was decreased by 1 to now 1 counter

IFRMABIS (4,1) measurement was extended by 1 counter for discarded I-Frames on BTSE side

LOCAUTCH (14,8) measurement was moved from the scanner class SCANBSC to the new scanner class SCANDPC and the number of counters was decreased by 1 to now 1 counter

NACTTBF (9,13) extended by 12 new counters due to the splitting of the result in traffic classes

NASPAVUN (14,10)

measurement was moved from the scanner class SCANBSC to the new scanner class SCANDPC and the number of counters was decreased by 1 to now 1 counter

NHOINRHA (1,43) support of DTM forced handover

NMSUREC (14,7) measurement was moved from the scanner class SCANBSC to the new scanner class SCANDPC and the number of counters was decreased by 1 to now 1 counter

NMSUTRAS (14,6) measurement was moved from the scanner class SCANBSC to the new scanner class SCANDPC and the number of counters was decreased by 1 to now 1 counter

Introduction


77

Name and ID Short Description NRRFPDU (9,32) extended by 2 new counters to distinguish between different

traffic classes

NRUNINHD (6,2) extended by 1 new counter for DTM forced handover

NUACATCL (9,2) extended by 4 new counters to distinguish between different traffic classes

REJPDASS (9,1) extended by 4 new counters to distinguish between several reasons

RFDBCUN (14,2) measurement was moved from the scanner class SCANBSC to the new scanner class SCANDPC and the number of counters was decreased by 1 to now 1 counter

RFSUBUN (14,3) measurement was moved from the scanner class SCANBSC to the new scanner class SCANDPC and the number of counters was decreased by 1 to now 1 counter

SERVUGDG (9,21) extended by 1 new counter for PDCH preemption

SINHOBSC (0,0) support of DTM forced handover

SININIRH (3,0) extended by 4 new counters for DTM forced handover

SINTHINT (1,29) extended by 1 new counters for DTM forced handover

SOUINIRH (5,0) extended by 4 new counters for DTM forced handover

SUCPDASA (9,29) extended by 4 new counters to distinguish between different traffic classes

SUCTETBF (9,31) extended by 2 new counters to distinguish between different traffic classes.

SUINBHDO (6,1) extended by 1 new counter for DTM forced handover

SULACCEL (9,3) extended by 4 new counters to distinguish between different traffic classes

SUOISHDO (12,1) extended by 1 new counter for DTM forced handover

TCMSGREC (14,4) measurement was moved from the scanner class SCANBSC to the new scanner class SCANDPC and the number of counters was decreased by 1 to now 1 counter

TCMSGSND (14,5) measurement was moved from the scanner class SCANBSC to the new scanner class SCANDPC and the number of counters was decreased by 1 to now 1 counter

TMSGREC (14,0) measurement was moved from the scanner class SCANBSC to the new scanner class SCANDPC and the number of counters was decreased by 1 to now 1 counter

Introduction


78

Name and ID Short Description TMSHHDL (14,1) measurement was moved from the scanner class SCANBSC to

the new scanner class SCANDPC and the number of counters was decreased by 1 to now 1 counter

UNINHOIE (5,2) extended by 1 new counter for DTM forced handover

UNOISHDO (12,2) extended by 1 new counter for DTM forced handover

UNSPDCSE (9,30) extended by 6 new counters to distinguish between several reasons

UNSTETBF (9,33) counters for preemption due to different priority classes were deleted and counters for preemption in case of CS calls and counters for DTM establishing were added

4.1.4 Replaced and deleted measurements

Old name and ID Replaced by the new measurement: new name and ID NPDCHPCU (0,19) NPDTPCU (0,19) Min, max, mean number of used PDTs per

PCU

The following measurements have been deleted:

• MEANTBFL (9,27)

• NINVPRACH (2,7)

Introduction


79

5 Siemens Base Station System (SBS) Overview

Introduction


80

The figure below shows the general structure of the SBS (Siemens Base Station Subsystem), which is the Siemens implementation of the Base Station Subsystem (BSS). The SBS includes:

• Base Transceiver Station Equipment (BTSE)

• Base Station Controller (BSC)

• Transcoding and Rate Adaptation Unit (TRAU) Further components are:

• Local Maintenance Terminal (LMT)

• Radio Commander (RC)

• CCU, PCU, SGSN, GGSN and GR

• LMU, SMLC and GMLC

• MSC, VLR, HLR, AC, EIR Base Transceiver Station Equipment (BTSE) The BTSE comprises the entire radio equipment in a given site for a single cell or a group of cells, each of which (as a BTS) is characterized by its own particular Base Station Identification Code (BSIC). In the case of sector cells, each cell refers to its own BTS, although all BTS are physically grouped together in the same site (BTSE). The BTSE performs functions such as speech and channel encoding/decoding, transmission and reception, etc. Base Station Controller (BSC) The BSC is the central control entity of the SBS and provides the interfaces to BTSE, TRAU, RC and LMT. All vital parts of the BSC are duplicated in order to ensure fault tolerant operation. The BSC administers the radio resources, maps radio channels to terrestrial network channels and performs handovers among the controlled cells. Transcoding and Rate Adaptation Unit (TRAU) For each traffic channel, the TRAU adapts the different transmission rates for speech and data calls on the radio side to the PCM standard 64 kbit/s transmission rate on the MSC side. It also performs transcoding between the different speech coding algorithms used on the radio interface (full rate, half rate, enhanced full rate) and the interface (PCM A ) used within the terrestrial network.

Introduction


81

Local Maintenance Terminal (LMT) The LMT is a portable terminal, e.g. a laptop computer used for local or remote operation and maintenance functions. The same LMT is used for the maintenance of all the SBS entities.

GPRS/EGPRS For GPRS support the BSC has to be completed with the Packet Control Unit (PCU), in the BTS software called the Channel Coding Unit (CCU) has to be installed. The introduction of EDGE requires EDGE capable carrier units (ECU).

Fig. 14 SBS system interfaces

Introduction


82

5.1 BSC hardware architecture An overview of the BSC hardware architecture is displayed in the following figure. With the SBS scanners it is possible to perform processor load measurements for:

• Administrative Processor (MPCC: Main Processor Control Board)

• Telephony Processor (TDPC Telephone and Distributor Processor Board)

• Packet Control Unit Processors (PCU) in case of the BSC1 configuration, and

• Switching Module and Clock (SMAC)

• Main Central Processor (MCP)

• Application Processor (AP)

• Line modules type LIET or LISO

• User Plane Module (UPM) in case of the eBSC configuration. These processors have the following tasks:

Administrative Processor (MPCC, UBEX)

• controls the connections to the switching network on the basis of the telephony processor messages,

• handles traffic and performance measurements,

• it is responsible for: – status administration & audit – database administration – hardware configuration – diagnostic and maintenance management – mass storage control – software downloading – O&M interface control – TRAU control

Introduction


83

Line TerminationSTLP

Line Termination

Line TerminationSwitchingNetwork

SNAP

ClockPLLH

Line Termination

Line Termination

Line Termination

BSSGP

PPXX

BSSGP

PPXX

BSSGP

PPXX

LAP D

PPXX

CCS 7

PPXX

MEMT TDPC

Telephony Processors

O&MInterface

IXLT

AdministrativeProcessor

UBEX

MPCC

to OMC

to LMT

. . . PeripheralProcessors

STLP

STLP

STLP

STLP

STLP

ESAM/CPEX

Fig. 15 BSC1 Architecture

Fig. 16 eBSC Architecture

Introduction


84

Telephony Processor (TDPC, MEMT)

• is responsible for message exchange with the other network entities via the peripheral pre-processors,

• handles all signaling functions above MTP layer 2 (except for measurement preprocessing, which is performed in the BTSE) and all application processes related to call control, radio resource management, mobility management and IMSI Tracing

• is connected via an internal bus (Telephony System Bus) to the preprocessors.

Switching Module and Clock (SMAC)

• supports the transport functions of user, control and management data between the blades of the shelf and between the shelves inserted in the rack via Gigabit Ethernet Switching (GES)

• provides the central clock functionality via Main Clock Generator Module (MCG)

• manages and supervises the status of GES and MCG components via General Purpose Peripheral Processor (GPP) RAM

• manages up to 21 External Alarms, open door alarm included

Main Control Processor (MCP) is the central O&M controller providing the following:

• RC (X.25, Ethernet) and CBC connections

• 1 port for 10/100 BASE-T Ethernet for Ethernet- IP based O&M, 2 ports for X.25-based connection

• LMT (Ethernet only) connection

• Central O&M controller interaction with the ShMC (Shelf Manager)

• HDD (Hard Disk Driver) for DBMS data persistency

• Hard Disk to store software, performance measurement data, etc.

Application Processor (AP) is responsible for the call processing application as well as for:

• processing the Radio Resource Management (RRM) and all SS7 signaling (AP/M Application Processor Main)

• additional processing the RMM for a number of cells (AP/D optional).

Introduction


85

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SS7

RRM

AP/M

RRM

AP/D

RRM

AP/D

RRM

AP/D

MSCSS7 signalling links

Cell 1

Cell 2

Cell 3 Cell 40

Cell 42

Cell 41

BTSM:11BTSM:21

BTSM:1BTSM:10

Fig. 17 Application Processor

Introduction


86

Line Modules type LIET / LISO Line Module E1/T1 (LIET) The LIET Modules provide the connections to the

• BTSE (PCMB)

• TRAU (PCMS)

• SGSN (PCMG)

• SMLC (Lb interface) via standard 2Mbit/s digital lines (coaxial or 4-wire copper). The LM-E1/T1 function is implemented on two separate physical modules within the shelf:

• The LM-E1/T1 blade performs most of the typical functions of a line module.

• The I/O-E1/T1 (Input/Output) modules are used for physical connection of the E1/T1 interfaces.

Line Module STM-1/OC3 (LISO) provides 2 optical links to/from Abis/Asub/Gb interfaces, which can be configured in:

• Channelized mode

• Unchannelized mode The first one supports an optical interface channelized STM1/OC3 (VC-12) that provides the Abis/Asub interface for TDM traffic for the connection towards the BTS and TRAU. The second configuration mode supports an optical interface unchannelized STM1/OC3 (VC-4) traffic for the Gb interface with classical IP over ATM.

User Plane Module (UPM) realizes one PCU required for packet switched data handling (GPRS / EGPRS) in eBSC.

Introduction


87

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

eBSC

SMAC

MCP

LAPDMTP2

FR

Gb IP

LISO:0

LISO:1

LISO:2

LISO:3

OPTLINE:0

OPTLINE:1

IP over ATMfor Gb

Unstructured

Structured

E1/T1 via optical line for

Abis, FR Gb, Asub

Fig. 18 Line Module STM1

Introduction


88

5.2 BTS hardware architecture The BS24x serves both GSM900 and its variants (GSM1800 / GSM1900). Moreover, the BS24x is the basis from which the Enhanced-Micro BS82 II and the BS288 and the BS289 are derived (BTSplus family). The main BTSplus components are:

• carrier-oriented boards called single or double carrier units (CU/FCU respectively)

• core boards (COBA/COSA), and

• combining equipment [(F)DUAMCO, FICOM, and DIAMCO]. In the following figure you can see as an example an overview of the BS24x hardware architecture.

Introduction


89

COBA

OVPT

OVPT

4 x Abis

4 x Abis

48 Site Inputs

CC-Links

-48 V

ACTP

LE 0 LE 1

230 V AC

CAN-BUS

Alarms

TXRX

RXDIV

TMA

TMA

RX

RXDIV

DUAMCO

DIAMCO

FICOM

CU 0 CC

CU 7 CC

CU 0

CU 7

2 PCM

2 PCM

4 PCM

RXCA 0

DIAMCO

RXCA 1

FICOM

RX

RXDIV

TXRX

RXDIV

ANT 0

Cascading

tonext

Ext. Rack

CC-Links

ANT 1

ANT 0

ANT 1

ANT 1

Cell 0

Cell 1

Cell 1

Cell 1

COSA

1 x Ext. Sync. CLK

FAN DCP

ACTM

-48 V

16 AL

TempDoor

ACTCDoor

Temp

FAN-48 V

ACTP

DCP

DCB-CTRL

DCB-CTRL Alarms

ACTCDoor

Temp

AC/DC AC/DC

ACP

FAN

Fan

-48 V

230 V AC

DCP

Fan

CAN-BUS

CAN-BUS

Extension Rack / Shelter

Service Rack / Shelter

Base Rack / Shelter

ACTC

Alarms

Battery Battery

Ext. Sync.

HPDU

ANT 0

Fig. 19 Overview of the BS24x hardware architecture

Introduction


90

The Carrier Unit (CU): contains all analog and digital signal processing units (including a RF power stage) to provide a single GSM / GPRS carrier. The carrier unit CU is composed of the following units:

• Power Amplifier and Transceiver Unit PATRX provides the main analogue functions of the CU.

• Power Supply Unit PSU: Is the DC/DC converter for the CU.

• The SIPRO performs the digital to analogue conversion (and back), provides the local clock supply, performs some signal processing tasks (encoding, ciphering, interleaving, burst formation), controls the RF of the PATRX, etc.

Flexible Carrier Unit (FCU) provides single or double EDGE carrier. It is composed of the following units: FCUTR (Flexible Carrier Unit TRansceiver) is a carrier specific part of a FCU also providing main analogue functions. FCUMAIN (Flexible Carrier Unit Main Part) which is common to both carriers and is actually FSIPRO.

Introduction


91

PATRX SIPRO

PSU

RX input

TX outputCC Link

-48V

CU

Fig. 20 Overview of the single CU hardware architecture

TX-0TX-0

RX-a

RX-b

TX-1

RX-c

RX-d

FlexCU

RX-N

RX-DIV

TX-1

RX-N1

RX-DIV1

FSIPRO(dual

ESIPRO)CTRL

CC-link

Fig. 21 Flexible (double) Carrier Unit Structure

Introduction


92

The Core Base (COBA) / Core Satellite (COSA) is responsible for:

• local control of entire BTSE

• generation of system clock

• provision of max 8 Abis interfaces to BSC and other BTSE

• routing of Abis data to max 24 CU

• provision of T-interface to LMT

• handling and processing of O&M messages. The COBA stores the BTSE SW on Flash-EPROM, supervises the SW download and terminates all internal system alarms. Beside the O&M functions (LPDLM) the COBA handles the signaling messages between BSC (Abis) and CU (LPDLR). The COBA can be expanded with the COSA board. Two variants of Core modules are possible:

• The COBA2P8 supports 8 CC links and 2 Abis links. This COBA can be used together with COSA6P16 that supports additional 6 Abis links and 16 CC links. This is the optimized solution for BS240.

• The COBA4P12 supports 12 CC links and 4 Abis links. Standalone the COBA4P12 supports 2 Abis links. To provide the 2 additional Abis links the COBA4P12 Extension board (COREXT) has to be used. The COBA4P12 can be used together with COSA4P12 that supports 12 additional CC links and 4 additional Abis links (in this case the COREXT is not needed).

With the SBS Scanner it is possible to perform measurements for the COBA processor load and for the Transceiver (TRX) Available Time.

Introduction


93

8 CUs

COBA4P12 COSA4P12

CU LinkInterfaceController

MainController

PCM LineInterface

Alarms

2 Abis

12 CUs


4 CUs

PCM LineInterface

4 Abis2 Abis

LMT

Connection viaback plane

Since BR8.0

Fig. 22 COBA4P12 and COSA4P12

8 CUs

COBA2P8 COSA6P16


MainController

PCM LineInterface

Alarms

2 Abis

16 CUs


PCM LineInterface

6 Abis

LMT

Connection viaback plane

Fig. 23 COBA2P8 and COSA6P16

Introduction


94

01 ra1736en90gls00 0002 introduction

Documents

nokia siemens networks

radio network

network planning

network operation

network optimization

network operator

setup failure rate

current network configuration