gprs indicators

*356�,QGLFDWRUV�$OHUWHUV�'HILQLWLRQ(' �� 5HOHDVHG

0&' 0263_07.doc02/04/97 �%.��'6==$ 1/19

6LWHVELIZY 02%,/(�&20081,&$7,21�',9,6,21

2ULJLQDWRU�V�S. Guibereau

*356�,QGLFDWRUV�$OHUWHUV�'HILQLWLRQ

'RPDLQ � ALCATEL 900/BSS'LYLVLRQ � PRODUCT DEFINITION5XEULF � SYS-OAM7\SH � SYSTEM FUNCTIONAL BLOCKS'LVWULEXWLRQ�&RGHV ,QWHUQDO�� ([WHUQDO��

35(',675,%87,21�

0&'M. Tuchendler G. DaelAll B7 DPM OSY B7 members

35(',675,%87,21��'2&��&(175(6

0&'�9HOL]\B. Marliac

$%675$&7

This document describes the GPRS indicators processed by MPM/NPA for the releasesB7.1 and B7.2. It concerns the BSS releases B6.2, B7.1 and B7.2.

$SSURYDOV

Name

App.

G. DaelO&M CC-OSY

J.R. HoullierDPM MPM/NPA/RNO

S. VeretDPM OMC3

Name

App.


0&' 0263_07.doc02/04/97 �%.��'6==$ 2/19

5(9,(:

Ed1 Proposal1 04/08/00 MCD/TD/O&M/SYSTEM/2000.132/SGEd1 Proposal3 27/10/00 MCD/TD/O&M/SYSTEM/2000.169/SGEd1 Proposal4 22/11/00 MCD/TD/O&M/SYSTEM/2000.182/SG

+,6725<Ed1 Proposal1 30/07/00 Creation, based on B6.2 indicators defined in “GPRS

Counter Catalogue B6.2” (3BK 11204 0228 DSZZA,ED05, proposal 1) and B7 counters defined byWorking Group 2 (GPRS step 2)

Ed1 Proposal2 01/09/00 Updated after reviewMCD/TD/O&M/SYSTEM/2000.132/SG.Completion of B7 indicators’ definition based on“GPRS Counter Catalogue B7” (3BK 11202 0325DSZZA, ED02, released), covering GPRS step 2 andEDGE.It takes into account following CRs decided for B6.2:- CR066038 “P19 and P54 counters”,- CR073840 “GPRS counters: P23 per PVC”.

Ed1 Proposal3 06/10/00 It integrates following modifications:- indication of B7 release (B7.1 or B7.2),- introduction of new indicators to take into account

new counters (P200 -> P210) and introduction ofsub-domain “Abis interface”,

- introduction of indicators stored on hourly basisfor RNO,

- removal of indicators TRPRAE, TRPPCE,TRPAGE,

- correction of some formulas,- introduction of new indicators for cell reselection,- removal of configuration data ITMSI,- naming of indicators (based on naming rules

presented in this document),- addition of a field DataCollMechanism, indicating

the mechanism used for PM data collection.It takes into account following CRs decided for B7:- CR083538 “Removal of PM counter P328a”,- CR083539 “Removal of PM counter P328b”.It takes into account following CR decided for B6.2:- CR077250 “PM counters for GPRS traffic load”.


0&' 0263_07.doc02/04/97 �%.��'6==$ 3/19

Ed1 Proposal4 10/11/00 Updated after reviewMCD/TD/O&M/SYSTEM/2000.169/SG.Main modifications are:- fields related to warnings are no more maintained

(these ones are not used by NPA),- preventive actions are associated to alerters only

(but there is currently no alerter for GPRS !),- modification of classification into domains and

sub-domains.Ed1 Released 24/11/00 Updated after review

MCD/TD/O&M/SYSTEM/2000.182/SG.Main modifications are:- modification of indicators’ RefNames,- introduction of new indicators to compute QoS on

cells,- line up with new edition of “GPRS Counter

Catalogue B7” (ED03) and “GPRS CounterCatalogue B6.2” (ED05),

- update for B6.2 field for indicators which havebeen defined but not implemented in B6.2 (theseindicators being then supported in B7.1/B7.2only).

Ed2 Proposal 1 12/01/01 It integrates following modifications:- modification of indicators’ releases to take into

account the features removed from B7.1 (NC2,use of GPRS in inner zone ofconcentric/multiband cells),

- correction of RefName, domain, formula for someindicators,

- removal of busy hour as relevant hour forindicators defined per Sub-BSS,

- modification of relevant hours and displayoperation for some indicators (in order to reducethe number of data to be stored by NPA/MPM),

- B7.2 becoming B8.It is in line with “GPRS Counter Catalogue B7”(ED04). It takes into account following CR decided forB6.2:- CR085915 “The MFS performance indicators

TRPDDE, TRPDUE, TRPDCT, TRPADE,TRPAUE, TRPAGE, TRPPCE are in restriction forB6.2”.


0&' 0263_07.doc02/04/97 �%.��'6==$ 4/19

Ed2 Released 25/01/01 It integrates following modifications:- modification of hourly storage for some indicators

required by RNO and PCS,- introduction of a new value for the unit field of the

indicator’s name (P: percent of time, used only forindicators new in B7.1),

- addition of some new indicators to compute therate of TBF establishment failures due tocongestion (QRDTECOR and QRUTECOR) andthe rate of TBF drops (QRDDTARR andQRUDTARR).

Ed3 Released 02/03/01 It integrates following modifications:- correction of DWM storage, formula, length for

some indicators,- removal of any reference to the release B8 and

B8 features (a new database will be used for B8),- removal of indicator TGBVCULA (consequence of

CR073840 – see above -),- new query to support automatic building of

customer’s documentation.It is in line with “GPRS Counter Catalogue B7”(ED05). It takes into account following CRs decidedfor B7.1:- CR088330 “Editorial clarification of some trigger

conditions”,- CR087653 “Editorial: Alignment of definition to

implementation of PM counters P21a,b”,- CR088026 “Adjust counter length of GPU

counters (P104 and P107)”,- CR087855 “Modification of the counters used to

evaluate the PAGCH signalling load”.7KLV�HGLWLRQ�LV�XVHG�DV�UHIHUHQFH�IRU�030�13$%��

Ed4 Proposal 1 06/07/01 It integrates following modifications:- introduction of B7++ release,- correction of formula, storage/display operation

for some indicators,- removal of TRPALY3M (not relevant for B7.1/B7.2

BSS).It is in line with “GPRS Counter Catalogue B7”(ED06). It takes into account following CRs decidedfor B7.1:- CR091946 “Correction of indicators computing

load on CS logical channels due to GPRS”- CR091139 “Redefinition of counters P392a and

P392b”,- CR091767 “Editorial: Align trigger condition of

P384 to correct implementation”,- CR092186 “Editorial clarification of counter P38”,- CR093943 “Impacts of the delayed TBF feature

on PM counters”.


0&' 0263_07.doc02/04/97 �%.��'6==$ 5/19

Ed4 Proposal 2 31/08/01 It integrates following modifications:- B7++ renamed B7.2 (renaming on forms and

reports only).Ed4 Proposal 3 19/10/01 It integrates following modifications:

- modification of mnemonic and of domain/sub-domains for some indicators,

- correction of storage/display operation andformula for calculated indicators consolidated inTOT and that were using in their formulaaverages,

- removal of indicators ARPDCUSP, ARMACUSP,TRPDDCLA, TRPDUCLA,

- introduction of new configuration dataMAX_PDCH.

It is in line with “GPRS Counter Catalogue B7”(ED07). It takes into account following CRs decidedfor B7.2:- CR098883 “Impact on GPRS indicators due to

feature ‘Resource reallocation’”,- CR101979 “Impact on GPRS indicators due to

feature ‘Delayed TBF release’,- CR098574 “P98a/P98b: clarification in the trigger”- CR099630 “Impact on GPRS indicators to allow

monitoring of TBF releases due to suspendprocedure”,

- CR103032 “Enhanced GPRS traffic adaptation tocell load variation; introduction in the GPRScounters catalogue” (new indicators for feature“Smooth PDCH adaptation”),

- CR103132 “Delayed downlink TBF release;introduction of one additional counter” (newindicators for feature “Delayed TBF release”),

- CR103113 “Radio resource reallocation;introduction of missing GPRS counters andclarifications to existing counters” (new indicatorsfor feature “Radio resource reallocation”).

It takes into account following CR decided for B6.2:- CR102824 “Impact on GPRS indicators due to

modification of counters P16 and P29”.


0&' 0263_07.doc02/04/97 �%.��'6==$ 6/19

Ed4 Released 02/11/01 It integrates following modifications:- removal of configuration data not supported

neither for B6.2 BSS nor for B7.1/B7.2 BSS,- TRPCHE and TRCCHE also supported for B6.2

BSS,- correction of MPM formula for some indicators,- field ‘NpaType’ filled for all indicators,- correction of DataCollecMechanism value for

indicators corresponding to averages,- usage of ‘tdiv’ in MPM formula involving division

by configuration data (e.g. PERIOD).It is in line with “GPRS Counter Catalogue B7”(ED08).

Ed5 Proposal 1 30/11/01 It integrates following modifications:- correction of formula for QRUTEBPR,

QRDTEBPR, QRDDTPRA, QRUDTPRA,- restoration of B6.2 RefName for B6.2 indicators

which RefName had been modified (to easemigration of NPA towards B7.1/B7.2),

- usage of terminology “established” and “allocated”to differentiate between PDCH allocated only andPDCH allocated and linked to transmissionresource,

- correction of field TableName for some indicatorsand split of table GPC into two tables GPC andGPD to overcome dimensioning problem detectedby NPA team (constraint being that a calculatedindicator shall contain in its formula only counterscorresponding to stored indicators stored in sameNPA table).


0&' 0263_07.doc02/04/97 �%.��'6==$ 7/19

Ed5 Proposal 2 21/12/01 It integrates following modifications:- correction of some RefName and descriptions

(master PDCH establishment/release instead ofallocation/de-allocation),

- mnemonics shortened to have a length smaller orequal of 50 characters,

- filling of field NPA_Formula to allow handling ofcalculated indicators (i.e. indicators not stored inDWM) which formula changed between B6.2 andB7.2 (NPA_Formula representing a “multi-releases” formula referencing to RefName ofstored indicators and using RNZ function to return0 instead of NULL value for stored indicatorsdefined for B7.2 only),

- fields FormulaExpressionB6.2/B71/B7pp leftempty for calculated indicators (NPA/MPM usingnow NPA_Formula to compute calculatedindicators),

- all stored indicators (i.e. stored in DWM) whichformula changed between B6.2 and B7.2 arestored also hourly, hourly values being populatedby NPA/MPM loader which is able to apply eitherB6.2 developed formula (i.e. formula referencingto counters) or B7.2 developed formuladepending on the current GPU release(considering migration from B6.2 to B7.2,migration from to/from B7.1 being not supported),

- forms and reports updated to display alsoNPA_Formula,

- granularity period replaced bydisplay/consolidation period in FormulaText anddescription fields,

- addition of some stored indicators representingtime occupancy (used by calculated indicatorscomputing percent of time).

It takes into account following CR decided for B7.2:- CR105970 “Impact on GPRS indicators to support

CMCC computations (RFD A55/102899)”,- CR106468 “Handling of GPRS indicators which

developed formula changed between B6.2 andB7.2”.

Ed5 Released 08/02/02 It takes into account following CR decided for B7.2:- CR107762 “Support of consolidation in MIN for

some GPRS indicators”.It is in line with “GPRS Counter Catalogue B7”(ED10).


0&' 0263_07.doc02/04/97 �%.��'6==$ 8/19

Ed6 Proposal 1 08/03/02 It integrates following modifications:- counter type set to “0” for all indicators,- correction of DWM storage for some indicators,- all indicators that are used as busy hour

references are stored in DWM and hourly andtheir NPA formula is modified to use loaderformula format,

- correction of some formulas.Ed6 Released 07/06/02 No change compared to last version.

7KLV�HGLWLRQ�LV�XVHG�DV�UHIHUHQFH�IRU�030�13$%��

Ed7 Released 24/02/03 It takes into account following CR decided for B7.2:- CR122845 “Correction of some GPRS indicators”,- CR123889 “Correction of some GPRS indicators”.

,17(51$/�5()(5(1&('�'2&80(176

Not applicable

)25�,17(51$/�86(�21/<

Not applicable(1'�2)�'2&80(17


0&' 0263_07.doc02/04/97 �%.��'6==$ 9/19

6<67(0�)81&7,21$/�%/2&.6

7$%/(�2)�&217(176

HISTORY ............................................................................................................................10REFERENCED DOCUMENTS............................................................................................10RELATED DOCUMENTS....................................................................................................10PREFACE ...........................................................................................................................101 SCOPE ........................................................................................................................112 THE INDICATORS.......................................................................................................11

2.1 Definition ................................................................................................................112.2 Formula ..................................................................................................................122.3 Validity Condition....................................................................................................122.4 QoS Alarm Description ...........................................................................................122.5 Instanciation ...........................................................................................................132.6 Naming rules of the Indicator Names .....................................................................13

3 ACRONYMS ................................................................................................................19

07 24/02/03 MCD/TD/OMC-CC/OSY MCD/TD/OMC-CC/OSY06 07/06/02 MCD/TD/OMC-CC/OSY MCD/TD/OMC-CC/OSY05 08/02/02 MCD/TD/OMC-CC/OSY MCD/TD/OMC-CC/OSY04 02/11/01 MCD/TD/OMC-CC/OSY MCD/TD/OMC-CC/OSY03 02/03/01 MCD/TD/OMC-CC/OSY MCD/TD/OMC-CC/OSY02 25/01/01 MCD/TD/OMC-CC/OSY MCD/TD/OMC-CC/OSY01 24/11/00 Creation MCD/TD/OMC-CC/OSG MCD/TD/OMC-CC/OSG(' '$7( &+$1*(�127( $335$,6$/�$87+25,7< 25,*,1$725


0&' 0263_07.doc02/04/97 �%.��'6==$ 10/19

+,6725<

Ed7 24/02/03Ed6 07/06/02Ed5 08/02/02Ed4 02/11/01Ed3 02/03/01Ed2 25/01/01Ed1 24/11/00 Creation

5()(5(1&('�'2&80(176

[1] Recommendation ITU X.739[2] Recommendation ITU X.738[3] Recommendation ITU Q.822

5(/$7('�'2&80(176

[4] GPRS/EDGE O&M Functional Architecture (B7/B8) - 3BK 11203 0074 DSZZA[5] MFS/OMC PM Interface Specification (B7) - 3BK 11204 0270 DSZZA[6] OMC/MFS: PM Domain (B6.2/B7) - 3BK 11204 0224 DSZZA[7] GPRS Counter Catalogue (B7) – 3BK 11202 0325 DSZZA[8] GSM Indicators/Alerters definition (B7) – 3BK 11204 0264 DSZZA

35()$&(

This document is the catalogue of the GPRS indicators (i.e. the indicators computed fromcounters provided exclusively by the MFS) computed by MPM/NPA B7.1 (indicatorsconcerning the BSS releases B6.2 and B7.1) and by MPM/NPA B7.2 (indicators concerningthe BSS releases B6.2, B7.1 and B7.2).


0&' 0263_07.doc02/04/97 �%.��'6==$ 11/19

�� 6&23(

The document is structured as follows:

• This first part (word document) is an introduction to the second part: it gives generalinformation about GPRS indicators and alerters, some rules about naming ofindicators.

• The second part (report produced by Access) contains:- the list of indicators (for BSS B6.2, B7.1 and B7.2) sorted according to their

investigation domain (Quality of Service, Resource Availability & Usage, TrafficLoad) and their sub-domains,

- definition of the indicators (sorted per ascending reference name),- definition of the configuration data that are used in the indicators’ formulas,- definition of the corresponding basic alerters.

The definition of the indicators (for BSS B6.2, B7.1 and B7.2), alerters and configurationdata are all stored in the Access database (B7.1/B7.2 GPRS Access database). Thecontent of this database is used by MPM/NPA development team. The database structure,which is the same for GPRS database and for GSM database, is described in [8].

�� 7+(�,1',&$7256

�� 'HILQLWLRQ

The INDICATOR (Alcatel proprietary) is an algebraic formula of X721 counters / X721gauges / X721 tide-marks / averaged gauges that expresses a representative rate or apercentage. The indicators are calculated by NPA/MPM (at OMC) from the PM result report(containing the counters and part of the configuration data) built by the MFS, each time aPM result report is retrieved by the OMC-R.

The indicator may correspond to an alerter; in that case, some thresholds (DOHUWHUWKUHVKROGV) are associated to this indicator (user-defined thresholds or pre-definedthresholds – basic alerters -, the Access database storing only the basic alerters). Thesethresholds permit to generate automatically QoS alarms to warn the operator of anabnormal behaviour.

Some ZDUQLQJ� WKUHVKROGV may be also associated to an indicator; these user-definedwarning thresholds are used by NPA/MPM when producing a warning report.

Note: these warning thresholds are not given in this document; they are provided by Customer Services team toNPA team.


0&' 0263_07.doc02/04/97 �%.��'6==$ 12/19

�� )RUPXOD

An indicator is defined by its formula that uses the basic functions of a calculator (i.e.parenthesis, division, sum, subtraction, multiplication, absolute). The manipulated variablesin the formula are counters, plus possibly some logical configuration parameters (e.g.Granularity Period, BS_AGBLK_RES) provided by the OMC or the MFS to NPA.

�� 9DOLGLW\�&RQGLWLRQ

An indicator is valid providing that certain conditions are TRUE: e.g. the indicator A/Bexpressing the rate of failures of a given telecom event (=A) compared to the number ofoccurences of this event (=B) will be valid if B is greater than a certain value (e.g. B > 100),meaning that the traffic is sufficient to validate the result of the indicator. The validitycondition of the indicator is inherent of the indicator definition. When the indicator is notvalid, no QoS alarm and no warning can be generated.

Note: the validity conditions are not given in this document.

�� 4R6�$ODUP�'HVFULSWLRQ

The Alarms are made up mainly by the following fields (according to the GSMrecommendation X.733):

- event type = Quality of Service,- probable cause = Threshold crossed,- managed object class = Cell, PVC, Bearer Channel, BSC, LapD, MFS,- perceived severity = critical, major, minor, warning (customisable) upon alarm

appearance, or cleared upon alarm disappearance,- threshold information = the threshold value, and the value of the indicator at alarm

detection time,- additional text = the preventive action described for the indicator.

The alarm Id for GPRS basic alerters shall be in the range [200051, 200100].

The thresholds mechanism uses per indicator ascending thresholds (associated each with aseverity) and a stability timer. This timer starts upon threshold crossing (alarm appearance),and at expiry, a QoS alarm is generated if the indicator value still exceeds a threshold (thealarm perceived severity is the severity of the threshold), otherwise no alarm is generated. AQoS alarm per threshold can be generated. An alarm for a given threshold is generatedonly if no current alarm is already active on this threshold.

The stability timer starts also upon threshold crossing (alarm disappearance), and at expiry,a QoS alarm clearing is generated if the indicator is still under the threshold.


0&' 0263_07.doc02/04/97 �%.��'6==$ 13/19

�� ,QVWDQFLDWLRQ

The threshold values, the validity condition and the QoS alarm severity, are customisableper alerter.

�� 1DPLQJ�UXOHV�RI�WKH�,QGLFDWRU�1DPHV

Note that the prefix/interface/procedure/optional type fields usually corresponds to thedomain/sub-domain1/sub-domain2/sub-domain3, except for some exceptional cases whenthe procedure field refers to both sub-domain2 and sub-domain3, in order to limit thenumber of optional type’s values.


0&' 0263_07.doc02/04/97 �%.��'6==$ 14/19

Procedure/Resource Optional TypeAGC AGCH channel -

BCH Bearer channel AV Availability

AV Availability

DL DownlinkBVC BSSGP virtual circuit (Gb interface)

UL Uplink

CCH CCCH channel -CRX Cell reselection procedure (NC0) SU Success

AR Abnormal release

BL RLC protocol

BP BSS problem

C1 Coding scheme 1

C2 Coding scheme 2

CF Cell reselection (NC0)

CG Congestion radio

CS Coding scheme

DT Delayed TBF

DU Dummy block

GP Gb interface problem

L1 Lost block CS1

L2 Lost block CS2

LN LLC PDU not re-routed

LR LLC PDU re-routed

LS LLC bytes discarded due to suspend

NR Normal release

PR Pre-emption radio

R1 Retransmission CS1


RA Radio resource reallocation

RP Radio problem

RR Retransmission

S2 Success (TS=1,2)

SF Suspension with release triggered by RRM

SN Suspension with release triggered by RLC

SP Suspension

DDT DL data transfer procedure (TBF release, RLCblocks)

SW Stagnating window

81,7

$: Average (number)(: Erlang (channel load)I: Minimum0: Maximum value (number)1: Number2: Ratio of events3: Percent of time5: Rate of events (%)7: Timer

35(),;

$: Resource Availability & Usage4: Quality of Service7: Traffic load

,17(5)$&(

*: Gb interface$: Ater interface5: Radio interface2: OMC interface

352&('85(�5(6285&(

237,21$/�7<3(

0DQGDWRU\ 2SWLRQDO 0DQGDWRU\


0&' 0263_07.doc02/04/97 �%.��'6==$ 15/19

T1 Radio resource reallocation failure - trigger T1



TG TX efficiency

BP BSS problem

FE Failure due to external request

FP Failure during preparation phase

RP Radio problem

DR1 DL data transfer procedure (radio resourcereallocation - trigger T1)

SU Success

BP BSS problem



RP Radio problem

SU Success


V5 MS transfer

BP BSS problem



RP Radio problem


SU Success

SU Success

RQ Request



DRR DL data transfer procedure (radio resourcereallocation)


AC Active TBF duration (cumulated time)

DB Downlink biased transferDTB DL TBF resource

SE Session

BP BSS problem

CC Congestion CPU

CD Congestion GPU/DSP

CG Congestion radio

CO Congestion

CT Congestion transmission (Ater)


P3 Partial success (TS=2,3)


RP Radio problem

S1 Success (TS=1)

S2 Success (TS=1,2)

S3 Success (TS=2,3)

S4 Success (TS=3,4)

S5 Success (TS=4,5)

S8 Success (TS=5,6,7,8)

SU Success

DTE DL TBF establishment procedure

RQ Request

V1 MS idle DRX / no MPDCH

V2 MS idle no DRX / no MPDCH

V3 MS idle DRX / with MPDCH

V4 MS during T3192 timer

V5 MS transfer

DTR DL TBF establishment request

V6 MS idle no DRX / with MPDCH


V2 MS idle no DRX / no MPDCH

V3 MS idle DRX / with MPDCH

V4 MS during T3192 timer

V5 MS transfer

DTS DL TBF establishment success

V6 MS idle no DRX / with MPDCH

CT Congestion transmission (Ater)GAL GCH 16K dynamic allocation procedureSU Success

GCH GCH channel AV Availability


0&' 0263_07.doc02/04/97 �%.��'6==$ 16/19


LP LLC PDU

MC MS context

OC Overload critical

OH Overload high

OS Overload severe

GPU GPU

PB Power budget

LAP LapD (on AterMux interface) AV Availability

MAC Master channel US Usage

PM Primary master channel

SM Secondary master channel

RQ Request

MAL Master PDCH dynamic establishment procedure

SU Success

PAD PACCH channel downlink -PAG PAGCH channel -

CG Congestion radio


SA Smooth PDCH adaptation

SU Success

RQ Request

PAL PDCH dynamic allocation/establishmentprocedure

SR Success for PDCH establishment

PAM PACCH channel uplink on master channel(s) -PAU PACCH channel uplink -

CI Circuit

IA Immediate assignmentPCH PCH channel

PA Packet

PDC PDCH channel US Usage

DU Dummy block

L1 Lost block CS1

L2 Lost block CS2



C1 Coding Scheme1

C2 Coding Scheme2

PD PDCH

PDD PDTCH channel downlink

TB TBF

PDT PDTCH channel -L1 Lost block CS1

L2 Lost block CS2



C1 Coding Scheme1

C2 Coding Scheme2

PD PDCH

PDU PDTCH channel uplink

TB TBF

CI Circuit

PA PacketPPC PPCH channel

PG Packet assignement

CI CircuitPPP PPCH and PCHPA Packet

PRA PRACH channel -AV Availability

CG Congestion radioPVC Permanent Virtual Circuit (Gb interface)

G1 Congestion level1

RAC RACH channel -AR Abnormal release

BL RLC protocol

BP BSS problem

C1 Coding scheme 1

C2 Coding scheme 2

UDT UL data transfer procedure (TBF release, RLCblocks)

CF Cell reselection (NC0)


0&' 0263_07.doc02/04/97 �%.��'6==$ 17/19

CG Congestion radio

CS Coding scheme

DU Dummy block


L1 Lost block CS1

L2 Lost block CS2

NR Normal release




RA Radio resource reallocation

RP Radio problem

RR Retransmission

S2 Success (TS=1,2)

SF Suspension with release triggered by RRM

SN Suspension with release triggered by RLC

SP Suspension

SW Stagnating window




TG TX efficiency

BP BSS problem



RP Radio problem

UR1 UL data transfer procedure (radio resourcereallocation - trigger T1)

SU Success

BP BSS problem



RP Radio problem

SU Success


V5 MS transfer

BP BSS problem



RP Radio problem


SU Success

SU Success

RQ Request



URR UL data transfer procedure (radio resourcereallocation)


SE SessionUTB UL TBF resourceUB Uplink biased transfer

BP BSS problem

CC Congestion CPU


CG Congestion radio

CO Congestion

CT Congestion transmission (Ater)




RP Radio problem

S1 Success (TS=1)

S2 Success (TS=1,2)

S3 Success (TS=2,3)

S4 Success (TS=3,4)

S5 Success (TS=4,5)

S8 Success (TS=5,6,7,8)

UTE UL TBF establishment procedure

SU Success


0&' 0263_07.doc02/04/97 �%.��'6==$ 18/19

RQ Request


V3 MS idle DRX / with MPDCHUTR UL TBF establishment request

V5 MS transfer


V3 MS idle DRX / with MPDCHUTS UL TBF establishment success

V5 MS transfer

DB Downlink biased transfer

SE Session

UB Uplink biased transfer

L1 Lost block CS1

L2 Lost block CS1

XDT UL/DL data transfer procedure


SU SuccessXTE UL/DL TBF establishment procedureRQ Request


0&' 0263_07.doc02/04/97 �%.��'6==$ 19/19

�� $&521<06

%&&+ Broadcast Control Channel%6& Base Station Controller%66 Base Station Subsystem%6&*3 Base Station Controller GPRS Protocol%66*3 BSS GPRS Protocol&&&+ Control Common Channel&)6& Current File Summary Control&0,6( Common Management Information Service Element'/ Downlink*3 Granularity Period*356 General Packet Radio Service/$3' Link Access Procedure on the D-channel (AterMux interface)0$& Medium Access Control06 Mobile Station13$ Network Performance Analyser20&�5 Operations and Maintenance Centre - Radio part3%&&+ Packet Broadcast Control Channel3&&+ Packet Control Common Channel3'&+ Packet Data Channel3'8 Protocol Data Unit33&+ Packet Paging Channel35$&+ Packet Radio Access Channel36 Packet Switched39& Permanent Virtual Circuit30 Performance Management5$0 Resource Allocation Management5/& Radio Link Control512 Radio Network Optimisation53 Report period550 Radio Resource Management6'&&+ Slow Dedicated Control Channel7%) Temporary Block Flow7), Temporary Flow Identifier7' Threshold Data75; Transmitter76 Timeslot8/ Uplink86' Usage State on Demand;�� CCITT Recommendation X25

gprs indicators

Documents