gprs alerters and indicators

SiteVELIZY MOBILE COMMUNICATION DIVISION

Originator(s)S. Guibereau

GPRS Indicators/Alerters Definition

Domain : ALCATEL 900/BSSDivision : PRODUCT DEFINITIONRubric : SYS-OAMType : SYSTEM FUNCTIONAL BLOCKSDistribution Codes Internal : External :

PREDISTRIBUTION:

MCDM. Tuchendler G. DaelAll B7 DPM OSY B7 members

PREDISTRIBUTION: DOC. CENTRES

MCD VelizyB. Marliac

ABSTRACT

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

Approvals

Name

App.

G. DaelO&M CC-OSY

J.R. HoullierDPM MPM/NPA/RNO

S. VeretDPM OMC3

Name

App.

GPRS Indicators/Alerters DefinitionED 07 Released

MCDdocument.doc

02/04/97 3BK 11204 0263 DSZZA 1/18

REVIEW

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

HISTORYEd1 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 by Working Group 2 (GPRS step 2)

Ed1 Proposal2 01/09/00 Updated after review MCD/TD/O&M/SYSTEM/2000.132/SG.Completion of B7 indicators’ definition based on “GPRS Counter Catalogue B7” (3BK 11202 0325 DSZZA, ED02, released), covering GPRS step 2 and EDGE.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 of sub-domain “Abis interface”,

- introduction of indicators stored on hourly basis for 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”.

Ed1 Proposal4 10/11/00 Updated after review MCD/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


MCDdocument.doc

02/04/97 3BK 11204 0263 DSZZA 2/18

(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 Counter Catalogue B6.2” (ED05),

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

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 of concentric/multiband cells),

- correction of RefName, domain, formula for some indicators,

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

- modification of relevant hours and display operation for some indicators (in order to reduce the 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 for B6.2:- CR085915 “The MFS performance indicators

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

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 for indicators new in B7.1),

- addition of some new indicators to compute the rate of TBF establishment failures due to congestion (QRDTECOR and QRUTECOR) and the rate of TBF drops (QRDDTARR and QRUDTARR).

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


MCDdocument.doc

02/04/97 3BK 11204 0263 DSZZA 3/18

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 decided for 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”.This edition is used as reference for MPM/NPA B7.1.

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 decided for 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”.

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 and formula for calculated indicators consolidated in TOT and that were using in their formula averages,

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

- introduction of new configuration data MAX_PDCH.


MCDdocument.doc

02/04/97 3BK 11204 0263 DSZZA 4/18

It is in line with “GPRS Counter Catalogue B7” (ED07). It takes into account following CRs decided for 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 suspend procedure”,

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

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

- CR103113 “Radio resource reallocation; introduction of missing GPRS counters and clarifications to existing counters” (new indicators for 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”.

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 ease migration of NPA towards B7.1/B7.2),

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

- correction of field TableName for some indicators


MCDdocument.doc

02/04/97 3BK 11204 0263 DSZZA 5/18

and split of table GPC into two tables GPC and GPD to overcome dimensioning problem detected by NPA team (constraint being that a calculated indicator shall contain in its formula only counters corresponding to stored indicators stored in same NPA table).

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

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

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

- filling of field NPA_Formula to allow handling of calculated indicators (i.e. indicators not stored in DWM) which formula changed between B6.2 and B7.2 (NPA_Formula representing a “multi-releases” formula referencing to RefName of stored indicators and using RNZ function to return 0 instead of NULL value for stored indicators defined for B7.2 only),

- fields FormulaExpressionB6.2/B71/B7pp left empty for calculated indicators (NPA/MPM using now NPA_Formula to compute calculated indicators),

- all stored indicators (i.e. stored in DWM) which formula changed between B6.2 and B7.2 are stored also hourly, hourly values being populated by NPA/MPM loader which is able to apply either B6.2 developed formula (i.e. formula referencing to counters) or B7.2 developed formula depending 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 also NPA_Formula,

- granularity period replaced by display/consolidation period in FormulaText and description fields,

- addition of some stored indicators representing time occupancy (used by calculated indicators computing 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 and B7.2”.

Ed5 Released 08/02/02 It takes into account following CR decided for B7.2:


MCDdocument.doc

02/04/97 3BK 11204 0263 DSZZA 6/18

- CR107762 “Support of consolidation in MIN for some GPRS indicators”.

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

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 and their NPA formula is modified to use loader formula format,

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

This edition is used as reference for MPM/NPA B7.2.

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”.

INTERNAL REFERENCED DOCUMENTS

Not applicable

FOR INTERNAL USE ONLY

Not applicableEND OF DOCUMENT


MCDdocument.doc

02/04/97 3BK 11204 0263 DSZZA 7/18

SYSTEM FUNCTIONAL BLOCKS

TABLE OF CONTENTS

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/OSGED DATE CHANGE NOTE APPRAISAL AUTHORITY ORIGINATOR


MCDdocument.doc

02/04/97 3BK 11204 0263 DSZZA 8/18

HISTORY

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

REFERENCED DOCUMENTS

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

RELATED DOCUMENTS

[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

PREFACE

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


MCDdocument.doc

02/04/97 3BK 11204 0263 DSZZA 9/18

1 SCOPE

The document is structured as follows:

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

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, Traffic Load) 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 configuration data are all stored in the Access database (B7.1/B7.2 GPRS Access database). The content 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].

2 THE INDICATORS

2.1 Definition

The INDICATOR (Alcatel proprietary) is an algebraic formula of X721 counters / X721 gauges / X721 tide-marks / averaged gauges that expresses a representative rate or a percentage. 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 a PM result report is retrieved by the OMC-R.

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

Some warning thresholds may be also associated to an indicator; these user-defined warning 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 to NPA team.


MCDdocument.doc

02/04/97 3BK 11204 0263 DSZZA 10/18

2.2 Formula

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 variables in 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.

2.3 Validity Condition

An indicator is valid providing that certain conditions are TRUE: e.g. the indicator A/B expressing the rate of failures of a given telecom event (=A) compared to the number of occurences 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 validity condition of the indicator is inherent of the indicator definition. When the indicator is not valid, no QoS alarm and no warning can be generated.

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

2.4 QoS Alarm Description

The Alarms are made up mainly by the following fields (according to the GSM recommendation 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 a severity) 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 (the alarm perceived severity is the severity of the threshold), otherwise no alarm is generated. A QoS alarm per threshold can be generated. An alarm for a given threshold is generated only 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.


MCDdocument.doc

02/04/97 3BK 11204 0263 DSZZA 11/18

2.5 Instanciation

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

2.6 Naming rules of the Indicator Names

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


MCDdocument.doc

02/04/97 3BK 11204 0263 DSZZA 12/18

Procedure/Resource Optional TypeAGC AGCH channel -

BCH Bearer channel AV AvailabilityBVC BSSGP virtual circuit (Gb interface) AV Availability

DL DownlinkUL Uplink

CCH CCCH channel -CRX Cell reselection procedure (NC0) SU SuccessDDT DL data transfer procedure (TBF release, RLC

blocks)AR Abnormal releaseBL RLC protocolBP BSS problemC1 Coding scheme 1C2 Coding scheme 2CF Cell reselection (NC0)CG Congestion radioCS Coding schemeDT Delayed TBFDU Dummy blockGP Gb interface problemL1 Lost block CS1L2 Lost block CS2LN LLC PDU not re-routedLR LLC PDU re-routedLS LLC bytes discarded due to suspendNR Normal releasePR Pre-emption radioR1 Retransmission CS1R2 Retransmission CS2RA Radio resource reallocationRP Radio problemRR RetransmissionS2 Success (TS=1,2)SF Suspension with release triggered by RRMSN Suspension with release triggered by RLCSP SuspensionSW Stagnating windowT1 Radio resource reallocation failure - trigger T1T2 Radio resource reallocation failure - trigger T2


MCDdocument.doc

02/04/97 3BK 11204 0263 DSZZA 13/18

UNIT

A: Average (number)E: Erlang (channel load)I: MinimumM: Maximum value (number)N: NumberO: Ratio of eventsP: Percent of timeR: Rate of events (%)T: Timer

PREFIX

A: Resource Availability & UsageQ: Quality of ServiceT: Traffic load

INTERFACE

G: Gb interfaceA: Ater interfaceR: Radio interfaceO: OMC interface

PROCEDURE/RESOURCE

OPTIONAL TYPE

Mandatory Optional Mandatory

T3 Radio resource reallocation failure - trigger T3TG TX efficiency

DR1 DL data transfer procedure (radio resource reallocation - trigger T1)

BP BSS problemFE Failure due to external requestFP Failure during preparation phaseRP Radio problemSU Success


BP BSS problemFE Failure due to external requestFP Failure during preparation phaseRP Radio problemSU SuccessV5 MS transfer



DRR DL data transfer procedure (radio resource reallocation)

SU SuccessRQ RequestT1 Radio resource reallocation failure - trigger T1T2 Radio resource reallocation failure - trigger T2T3 Radio resource reallocation failure - trigger T3

DTB DL TBF resource AC Active TBF duration (cumulated time)DB Downlink biased transferSE Session

DTE DL TBF establishment procedure BP BSS problemCC Congestion CPUCD Congestion GPU/DSPCG Congestion radioCO CongestionCT Congestion transmission (Ater)GP Gb interface problemP3 Partial success (TS=2,3)P5 Partial success (TS=4,5)RP Radio problemS1 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 SuccessRQ Request

DTR DL TBF establishment request V1 MS idle DRX / no MPDCHV2 MS idle no DRX / no MPDCHV3 MS idle DRX / with MPDCHV4 MS during T3192 timerV5 MS transferV6 MS idle no DRX / with MPDCH

DTS DL TBF establishment success V1 MS idle DRX / no MPDCHV2 MS idle no DRX / no MPDCHV3 MS idle DRX / with MPDCHV4 MS during T3192 timerV5 MS transferV6 MS idle no DRX / with MPDCH

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

GCH GCH channel AV AvailabilityGPU GPU CD Congestion GPU/DSP

LP LLC PDUMC MS contextOC Overload criticalOH Overload highOS Overload severePB Power budget


MCDdocument.doc

02/04/97 3BK 11204 0263 DSZZA 14/18

LAP LapD (on AterMux interface) AV AvailabilityMAC Master channel US UsageMAL Master PDCH dynamic establishment procedure PM Primary master channel

SM Secondary master channelRQ RequestSU Success

PAD PACCH channel downlink -PAG PAGCH channel -PAL PDCH dynamic allocation/establishment

procedureCG Congestion radioPR Pre-emption radioSA Smooth PDCH adaptationSU SuccessRQ RequestSR Success for PDCH establishment

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

PCH PCH channel CI CircuitIA Immediate assignmentPA Packet

PDC PDCH channel US UsagePDD PDTCH channel downlink DU Dummy block

L1 Lost block CS1L2 Lost block CS2R1 Retransmission CS1R2 Retransmission CS2C1 Coding Scheme1C2 Coding Scheme2PD PDCHTB TBF

PDT PDTCH channel -PDU PDTCH channel uplink L1 Lost block CS1

L2 Lost block CS2R1 Retransmission CS1R2 Retransmission CS2C1 Coding Scheme1C2 Coding Scheme2PD PDCHTB TBF

PPC PPCH channel CI CircuitPA PacketPG Packet assignement

PPP PPCH and PCH CI CircuitPA Packet

PRA PRACH channel -PVC Permanent Virtual Circuit (Gb interface) AV Availability

CG Congestion radioG1 Congestion level1

RAC RACH channel -UDT UL data transfer procedure (TBF release, RLC

blocks)AR Abnormal releaseBL RLC protocolBP BSS problemC1 Coding scheme 1C2 Coding scheme 2CF Cell reselection (NC0)CG Congestion radioCS Coding schemeDU Dummy blockGP Gb interface problemL1 Lost block CS1L2 Lost block CS2NR Normal releasePR Pre-emption radioR1 Retransmission CS1R2 Retransmission CS2RA Radio resource reallocation


MCDdocument.doc

02/04/97 3BK 11204 0263 DSZZA 15/18

RP Radio problemRR RetransmissionS2 Success (TS=1,2)SF Suspension with release triggered by RRMSN Suspension with release triggered by RLCSP SuspensionSW Stagnating windowT1 Radio resource reallocation failure - trigger T1T2 Radio resource reallocation failure - trigger T2T3 Radio resource reallocation failure - trigger T3TG TX efficiency

UR1 UL data transfer procedure (radio resource reallocation - trigger T1)



BP BSS problemFE Failure due to external requestFP Failure during preparation phaseRP Radio problemSU SuccessV5 MS transfer



URR UL data transfer procedure (radio resource reallocation)

SU SuccessRQ RequestT1 Radio resource reallocation failure - trigger T1T2 Radio resource reallocation failure - trigger T2T3 Radio resource reallocation failure - trigger T3

UTB UL TBF resource SE SessionUB Uplink biased transfer

UTE UL TBF establishment procedure BP BSS problemCC Congestion CPUCD Congestion GPU/DSPCG Congestion radioCO CongestionCT Congestion transmission (Ater)GP Gb interface problemP3 Partial success (TS=2,3)P5 Partial success (TS=4,5)RP Radio problemS1 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 SuccessRQ Request

UTR UL TBF establishment request V1 MS idle DRX / no MPDCHV3 MS idle DRX / with MPDCHV5 MS transfer

UTS UL TBF establishment success V1 MS idle DRX / no MPDCHV3 MS idle DRX / with MPDCHV5 MS transfer

XDT UL/DL data transfer procedure DB Downlink biased transferSE SessionUB Uplink biased transferL1 Lost block CS1L2 Lost block CS1PR Pre-emption radio

XTE UL/DL TBF establishment procedure SU SuccessRQ Request


MCDdocument.doc

02/04/97 3BK 11204 0263 DSZZA 16/18


MCDdocument.doc

02/04/97 3BK 11204 0263 DSZZA 17/18

3 ACRONYMS

BCCH Broadcast Control ChannelBSC Base Station ControllerBSS Base Station SubsystemBSCGP Base Station Controller GPRS ProtocolBSSGP BSS GPRS ProtocolCCCH Control Common ChannelCFSC Current File Summary ControlCMISE Common Management Information Service ElementDL DownlinkGP Granularity PeriodGPRS General Packet Radio ServiceLAPD Link Access Procedure on the D-channel (AterMux interface)MAC Medium Access ControlMS Mobile StationNPA Network Performance AnalyserOMC-R Operations and Maintenance Centre - Radio partPBCCH Packet Broadcast Control ChannelPCCH Packet Control Common ChannelPDCH Packet Data ChannelPDU Protocol Data UnitPPCH Packet Paging ChannelPRACH Packet Radio Access ChannelPS Packet SwitchedPVC Permanent Virtual CircuitPM Performance ManagementRAM Resource Allocation ManagementRLC Radio Link ControlRNO Radio Network OptimisationRP Report periodRRM Radio Resource ManagementSDCCH Slow Dedicated Control ChannelTBF Temporary Block FlowTFI Temporary Flow IdentifierTD Threshold DataTRX TransmitterTS TimeslotUL UplinkUSD Usage State on DemandX.25 CCITT Recommendation X25


MCDdocument.doc

02/04/97 3BK 11204 0263 DSZZA 18/18

gprs alerters and indicators

Documents