counter and indicators status bssaw01b_ed02

7/28/2019 Counter and Indicators Status BSSAW01B_Ed02

1/119

ED 01 RELEASED COUNTERS AND INDICATORS STATUS BSSSAW01B Ed02RELEASE B9

EVOLIUM 3BK 13091 0133 TQZZA 1/119

Site

VELIZY

EVOLIUM SAS

Originators

Ph. CREANGE

COUNTERS AND INDICATORS STATUS

BSSSAW01B Ed02

RELEASE B9

System : ALCATEL 900/1800/BSS

Sub-system : SYS

Document Category : QUALIFICATION

ABSTRACT

This document presents the status of the different counters and indicators defined in release B9.

Approvals

NameApp.

D. Bomy

B9 BSS TPL

B. Fernier

B9 QM

D. Guidot

NPI

NameApp.

REVIEW

Ed.01 Proposal 1 November 9th

2005 Reviewed by appraisal authorities

HISTORY

Ed. 01 Proposal 1 October 27th

2005Creation of the document based on COUNTERS ANDINDICATORS STATUS BSSSAW01B Ed01 RELEASEB9Updated with latest results:

- FR 170526 concerning MC746 is closed- FR 171014 concerning C400 is closed

-FR 166762 concerning P100c is closed

- FR 171734 concerning P383a is added- FR 170423 concerning TCNARQDRN is added

Ed. 01 Proposal 2 November 15th

2005Document updated after review

Updated with latest results:- FR 172132 concerning P471 is added

Ed. 01 Released November 15th

2005Released version


2/119



TABLE OF CONTENTS

1 SCOPE.............................................................................................................................................. 42 RESULT SUMMARY ........................................................................................................................ 52.1 Inherited B8 problems................................................................................................. 5

2.1.1 Counters in restriction or with limitation .......................................................................... 52.1.2 Indicators in restriction or with limitation ......................................................................... 52.1.3 Other inherited problems................................................................................................. 5

2.2 Counters status ........................................................................................................... 52.2.1 Testing status.................................................................................................................. 52.2.2 Functional problems........................................................................................................ 62.2.3 Documentation problems................................................................................................ 62.2.4 Consistency problems..................................................................................................... 6

2.3 Indicators status.......................................................................................................... 62.4 Problem description.................................................................................................... 7

2.4.1 Problems discovered in the current release.................................................................... 82.4.2 Problems inherited from previous releases................................................................... 11

3 PERFORMANCE MANAGEMENT COUNTERS ........................................................................... 153.1 GSM Counters............................................................................................................ 153.2 GPRS Counters.......................................................................................................... 53

4 PERFORMANCE MANAGEMENT INDICATORS......................................................................... 674.1 GSM Indicators .......................................................................................................... 674.2 GPRS Indicators ........................................................................................................ 90

5 ANNEX.......................................................................................................................................... 119


3/119



INTERNAL REFERENCED DOCUMENTS

Not applicable

REFERENCED DOCUMENTS

[ 1 ] BSS Counters catalogue3BK 11203 0102 DSZZA ed 9

[ 2 ] MFS Counters catalogue3BK 11203 0101 DSZZA ed 7

[ 3 ] BSS Indicator catalogue3BK 11204 0343 DSZZA ed 9

[ 4 ] BSS RESTRICTIONS LIST BSSSAW01B RELEASE B9 Ed 023BK 13016 0932 TQZZA

RELATED DOCUMENTS

Not applicable


4/119



1 SCOPE

This document presents the status of the PM counters and indicators used in release B9.

The counter status is presented in paragraph 3. The indicator status is presented in paragraph 4. Anannex includes the file used for building the status tables.

Each counter of the B9 release is described by:

ShortName

Name Type B8 B9 Test B8 Test B9 Definition

- A short name (its number)- A (long) name- The counter type it belongs to

-Its existence in B8

- Its existence in B9- Its testing status relative to B8- Its testing status relative to B9- A description

Each indicator of the B9 release is described by:

Reference Mnemonic B8 B9 Tested B8 Tested B9 Description

- A reference- A mnemonic (its name)- Its existence in B8- Its existence in B9- Its testing status relative to B8- Its testing status relative to B9- A description

For both counters and indicators, the possible statuses are:

- OK: Test has been performed and the result is correctNote: When a counter has not been tested within the overall system tests, but only through thesub-system tests (with a correct result), the information is presented with "BSC only "or "MFSonly".

- Not tested- NOK: Test has been performed and the result is incorrect. In this case the FR number is

presented.- CR: The counter behavior is correct, its definition needs to be updated


5/119



2 RESULT SUMMARY

This chapter lists the different counters and indicators linked to a problem discovered either in B8(paragraph 2.1) or B9 (paragraphs 2.2 and 2.3).

2.1 Inherited B8 problems

2.1.1 Counters in restriction or with limitation

P10 (FR 20/161399 for B8)P27 (FR 20/164852 for B8, 20/167340 for B9)

2.1.2 Indicators in restriction or with limitation

None

2.1.3 Other inherited problems

The following problems discovered in an earlier release are still valid in B9:

- Counters are incorrect in RNO if granularity period is less than 1h (FR 20/130427)

- If the first counter reported for a day is invalid, NPA / MPM invalidates all the values for this day (FR 20/67756)

2.2 Counters status

General note: Noise present on the air interface might generate the so-called phantom RACHs.As a consequence, some counters like C08c/MC08c, MC148, P106, P107, P392b, might show valuesdifferent than 0, even if there is no traffic ongoing.

2.2.1 Testing status

All the GSM counters created in B9 have been tested except:

RMSPW3

All the GPRS counters created in B9 have been tested except:

P488, P489

The following counters (and/or types) common to B9 and earlier releases have not been tested sinceB7.

- Types 7, 8


6/119



- DER types 11

- C180c, C181a/b/c/e/f/g/h/i/j/k/l in type 18

- C257, C258 in type 25

- P2a, P2b, P2c, P2d, P383b, P3a, P3b, P41, P45, P46 in GPRS

Types 9, 10, 12, 13, 14 and 15 have been partially tested

2.2.2 Functional problems

A limitation has been found on the following counter:

- CB803 (FR 20/170995)

The following counter is under restriction in B9 due to problems found during the functional test phase:

- P471 (FR 20/172132)

2.2.3 Documentation problems

The definition of the following counters needs to be updated. There is no functional impact:

- P38e, P38f, P451a, P451b (FR 20/166037)

- P383a (FR 20/171734)

2.2.4 Consistency problems

A consistency problem has been discovered on the following counters:

- None

2.3 Indicators status

The testing of indicators consists in checking the correct implementation of the formula with respect to

the constituting counters.

The main results are:

- The following indicators use a counter that is not valid for B8 BSSs:

Counter Indicator

P10 QRDDTCGN, QRDDTCGR, TGBVCDLA

P27 QRUTECGN


7/119



- The following indicators are incorrect:

- TCNARQDRN in RNO (FR 20/170423)

- Indicators that use a counter not valid in B9:

None

- Indicators that use a counter whose definition needs to be updated:

Counter Indicator

P38e ARPDCUDBUT, NPACUDBUT

P38f ARPDCUUBUT, NPACUUBUT

P451a ARPDCTUBUT

P451b ARPDCTDBUT

P383a QAGALCTT

P471 AAGCHEXT

- Indicators built on a counter where an inconsistency has been discovered in B9:None

- Indicators built on a incorrect data provided by a configuration file:

None

- A problem has been found on the following parameters used in some indicators:

- BCCH_Band (FR 20/167453)

- Inconsistencies in the number of exported TRX (FR 20/167524)

- A problem has been found on the following alerters:

-SDCCH_CONG_RATE (FR 20/171023)

2.4 Problem description

Symbols are used to indicate visually the gravity of the fault report linked to a counter restriction:

for FR with gravity G0/G1 for FR with gravity G2 for FR with gravity G3/G4


8/119



2.4.1 Problems discovered in the current release

SMS-CB counter CB603 is reported once an hour despite the ODMC periodfor Raw type 30 is 15 minutes RESTRICTION

Even though the reporting period for the SMS-CB raw type is set to 15 minutes, counter CB603(NB_SMS_CB_FAIL_IND) is reported only once per hour from the BSC to the OMC. No data is lost

The other counters of this type are reported with the correct periodicity.

There is no problem with a granularity period of 60 minutes

Preventive actions : Not applicableWorkaround

Corrective actions : Not applicable

Unusable

Usable with WA

Usable with limitation

Impacts

No operational impact. However, the displayed values are not in line with theoccurrence time of the event.

Occurrence Very Sporadic

Sporadic

Systematic

Existed before

Current delivery?

Likely

Yes

No

FR 3BKA20FBR170995

Sub-System BSC-SW Severity G3

Planned Delivery Under study for MR1-edx

Keywords Performance Management

Counter P471 is never resetRESTRICTION

This cumulative counter (CUMULATED_TIME_EXCESS_GCH) should be reset after each reporting atthe end of the granularity period. This reset is not performed and the counter cumulates valuesmeasured since the last reset.



Unusable

Usable with WA


Impacts

This counter cannot be used for QoS follow-up


Sporadic

Systematic

Existed before

Current delivery?

Likely

Yes

No

FR 3BKA20FBR172132

Sub-System MFS SW Severity G2

Planned Delivery MR1 ed.x



9/119



The specifications of the trigger conditions of P38e/f and P451a/b are notcomplete enough OPRATOR HINT

The trigger conditions of P38e and P38f should precise that only the active, delayed and extendedphases of the TBF are to be taken into account in the computation. The same precision needs to bebrought to P451a and P451b

The specification will be adapted to take into account the behavior

Preventive actions : Not applicableWorkaroundCorrective actions : Not applicable

Unusable

Usable with WA


Impacts

Currently, P38e and P38f are over-estimated in comparison to P451a andP451b


Sporadic

Systematic

Existed before

Current delivery?

Likely

Yes

No

FR3BKA20FBR166037

Sub-System Specifications Severity G2



The specifications of the trigger conditions of P383a are not preciseenough OPRATOR HINT

This counter (TIME_ATERMUX_CONG) counts the Atermux congestion duration (in seconds) due to alack of GCH transmission resources on the Atermux interface.

Its definition and trigger have to be adapted and shall mention free Ater nibble instead of free GCH

and shall be counted at GPU instead of DSP

The specification will be adapted to take into account the behavior



Unusable

Usable with WA


Impacts

With the current definition, the counter may not be incremented in somecases


Sporadic

Systematic

Existed before

Current delivery?

Likely

Yes

No

FR 3BKA20FBR171734

Sub-System Specifications Severity G2




10/119



Alerter SDCCH_CONG_RATE cannot be raisedRESTRICTION

The alerter SDCCH_CONG_RATE cannot be raised in the OMC

Preventive actions : Modify in convert_expression, the line 646from /alcatel/npa/mpm/alarm/bin/alarm.pl,(first line from

"if ( ! exists$hash_loadmap{$ruleset}{$BLOCK_TYPE}{$val} ) ")

$val into uc($val);

Workaround

Corrective actions : Same as preventive action

Unusable

Usable with WA


Impacts

No real time alarm on the SDCCH congestion rate can be raised in theOMC. Post-Processing in NPA / RNO of this indicator is not impacted


Sporadic

Systematic

Existed before

Current delivery?

Likely

Yes

No

FR 3BKA20FBR171023

Sub-System OMC-SW Severity G2

Planned Delivery Under study for MR1ed.x


BCCH_Band = 7 for Cells with mapped TRERESTRICTION

Sometimes, the parameter BCCH_Band is exported with value 7 (not existing in the list of possiblevalues) in the BSSConf files even if the corresponding TREs are equipped and mapped

At a later export, the correct value is exported.



Unusable

Usable with WA


Impacts

The indicators based on this value are incorrect during the period theexported value is 7.


Sporadic

Systematic

Existed before

Current delivery?

Likely

Yes

No

FR 3BKA20FBR167453


Planned Delivery Under study for MR1ed. x



11/119



Inconsistency in BSSConf files for number of TRXRESTRICTION

For a real BSC some virtual BTSs with Virtual Cells (Provisioning) are described. The Cells arecompletely defined including the planned TRX.

In the BSSConf file these Cells are listed in the "CELL SECTION" with TRX_NB = 0. In the othersections (BSC and TRX), the number is correct

There is no problem with the real cells.



Unusable

Usable with WA


Impacts

No impact has this concerns only provisioned TRXs


Sporadic

Systematic

Existed before

Current delivery?

Likely

Yes

No

FR 3BKA20FBR167524


Planned Delivery Under study for MR1ed. x


Indicator TCNARQDRN is not present in RNORESTRICTION

The indicator TCNARQDRN (RTCH_assign_requests_Included_DR) is not present in RNO even

though it exists in NPA.Preventive actions : Not applicableWorkaround


Unusable

Usable with WA


Impacts

This indicator cannot be used for QoS measurements.


Sporadic

Systematic

Existed before

Current delivery?

Likely

Yes

No

FR 3BKA20FBR170423Sub-System RNO-SW Severity G3

Planned Delivery Under study for MR1-edx


2.4.2 Problems inherited from previous releases

Counters are incorrect in RNO if granularity period is less than 1hRESTRICTION


12/119



It has been observed that, in case of counters retrieval in a permanent measurement campaign set-upwith a granularity period of 30 minutes, the values delivered by MPM/NPA counters browser arecorrect.

As the RNO, has the minimum granularity period of 1 hour, instead of reporting the maximum value ofone hour, reports the average value of two 30 minutes periods.

It is recommended, in order to avoid inconsistent data, to set-up the granularity for 1h at NPA/MPMside.

Same recommendation applies also for changing the MFS PM counters granularity. (default value =1h)

Preventive actions: Granularity to be used is 1h for NPA/MPM/MFS.

Workaround Corrective actions: The correct values of these two counters can be knownusing the MPM counter browser.

Unusable

Usable with WA


Impacts

Inconsistent data at RNO side

OccurrenceVery Sporadic

Sporadic

Systematic

Existed beforeCurrent delivery?

Likely

Yes

No

FR 3BKA20FBR130427

Sub-System RNO Severity G2

Planned Delivery No solution planned


In case of BSC network elements failures, some counters valueare missingduring one reporting period

RESTRICTION

If during a PM reporting period, some BSS counters are declared as invalid (for instancefollowing an action on the BSC such as lock/unlock DTC), NPA or MPM invalidates all countersof the same raw type for this period and display no values.

Preventive actions: Not Applicable.WorkaroundCorrective actions: Not Applicable.

Unusable

Usable with WA


Impacts

Counter values are empty.

Very Sporadic

Sporadic

Systematic

Occurrence

Whenever, In the PM files, following specific command triggered on BSCnetwork elements, some BSS counters are declared as invalid.

Existed before

current delivery?

Likely

Yes

No

FR 3BKA20FBR067756

3BKA20FBR059136

B7

B6.2

Sub-System NPA Severity G1

Planned Delivery No solutionplanned

Keywords NPA


13/119



Wrong value for counter P10 in case of reselection failureRESTRICTION

It has been observed that during a reselection, when re-routing of data from one GPU to another GPUfails abruptly for some external reason (e.g. link failure) the counter P10 is wrongly incremented.

Preventive actions : Not applicableWorkaroundCorrective actions : Not applicable

Unusable

Usable with WA


Impacts

Misleading performance measurements reports


Sporadic

Systematic

Existed before

Current delivery?

Likely

Yes

No

FR 3BKA20FBR161399

Sub-System MFS-SW Severity G2Planned Delivery Under study for B8


In some cases counter P27 is not incrementedRESTRICTION

It has been observed that during a high load period, counter P27 remains at 0.



Unusable

Usable with WA


Impacts

Misleading performance measurements reports


Sporadic

Systematic

Existed before

Current delivery?

Likely

Yes

No

FR 3BKA20FBR167340

3BKA20FBR164852

Sub-System MFS-SW Severity G2

Planned Delivery Under study for B9Keywords Performance Management


14/119




15/119



3 PERFORMANCE MANAGEMENT COUNTERS

3.1 GSM Counters

Short

Name Name Type B8 B9 Test B8 Test B9 Definition

C01 NB_IMM_ASS_SUCC_MT 1 X X X OK

Number of immediate assignment plus SDCCH normal assignment

successes for Mobile Terminating procedure.

C02 NB_IMM_ASS_SUCC_MO 1 X X X BSC only

Number of immediate assignment successes for Mobile Originatingprocedure

C02 = C02a + C02b + C02c + C02d + C02e + C02f + C02g + C02h +

C02i.The following counters C02a/b/c/d/e/f/g/h/i provide the distribution of

the MO telecom procedures on SDCCH.

C02aNB_IMM_ASS_SUCC_MO_LOC_UPD 1 X X X case: Location Update request (except the "follow on" procedure)

C02bNB_IMM_ASS_SUCC_MO_SMS 1 X X X case: SMS procedure on SDCCH

C02c

NB_IMM_ASS_SUCC_MO_SU

P_SERV 1 X X X case: Supplementary Service

C02d

NB_IMM_ASS_SUCC_MO_FO

LLOW_ON 1 X X X case: Location Update request ("follow on" procedure)

C02e

NB_IMM_ASS_SUCC_MO_CM

_REEST 1 X X X case: CM Re-establishment procedure

C02f

NB_IMM_ASS_SUCC_MO_L3I

NFO_UNKNOW 1 X X X

MC02f=C02f, number of immediate assignment successes for MobileOriginating procedure, in case of L3 Info (within 48.058 ESTABLISH

INDICATION) unknown by the BSC but transferred to the MSC.

C02g

NB_IMM_ASS_SUCC_MO_IM

SI_DETACH 1 X X X

MC02g=C02g, number of immediate assignment successes for

Mobile Originating procedure, in case of IMSI Detach Indication.

C02h

NB_IMM_ASS_SUCC_MO_CA

LL_EST 1 X X X OK case: normal or emergency call establishment

C02iNB_IMM_ASS_SUCC_MO_LCS 1 X X X case: Mobile originated LCS procedure on SDCCH

C03 NB_OUT_SDCCH_HO_SUCC 1 X X X OKMC03=C03, Number of outgoing SDCCH handover (any kind)successes.

C04NB_IMM_ASS_PREP_FAIL_CONG 1 X X X

MC04=C04, number of immediate assignment preparation failuresdue to congestion.

C07 NB_SDCCH_DROP_OUT_HO 1 X XMC07=C07, Number of SDCCH drops during any outgoing SDCCHhandover.

C10 NB_INC_SDCCH_HO_SUCC 1 X X X OK

MC10=C10, Number of incoming SDCCH handover (any kind)

successes.

C137

NB_SDCCH_DROP_EST_PHA

S_BSS_PB 1 X X X

MC137=C137, Number of SDCCH drops in SDCCH established

phase due to BSS problem. It may happen that several causes offailures mentioned below are detected consecutively. In that case, the

counter will only be incremented once, as soon as the call is released.

C138NB_SDCCH_DROP_EST_PHAS_RLF 1 X X X

Number of SDCCH drops on SDCCH established phase due to radiolink failure (radio link timeout or Lapdm timer expiry).

C13aNB_TCH_NOR_ASS_QUEUED 1 X X X BSC only

Number of TCH (in HR or FR usage) normal assignment requeststhat are put in BSC queue.

C13bNB_INC_EXT_TCH_HO_QUEUED 1 X X X BSC only

Number of TCH (in HR or FR usage) incoming external handoverrequests that are put in BSC queue

C147 NB_INC_SDCCH_HO_ALLOC 1 X X X OK

MC147=C147, Number of incoming internal or external SDCCH

handovers -whose target SDCCH channel is allocated by the BSC.

C148 NB_IMM_ASS_ALLOC 1 X X X OK

Number of immediate assignment plus SDCCH normal assignments -

whose SDCCH channel is allocated by the BSC.

C149NB_IMM_ASS_EXEC_FAIL_R

ADIO 1 X XNumber of immediate assignment -execution failures due to MSaccess problem.

C14aNB_TCH_DROP_HO_PREP_EXEC_FAIL_BSS_PB 1 X X X

Number of TCH (in HR or FR usage) drops due to BSS problemduring any TCH handover preparation and execution phases.

This counter is incremented on the cell on which the problemoccurs(In the case of internal inter-cell handovers, it is not

incremented on both serving and target cell). For problems that are

not related to a specific cell, the counter related to the serving cell willbe incremented.

It may happen that several causes of failures mentioned below aredetected consecutively. In that case, the counter will only be

incremented once, as soon as the handover procedure fails.

This counter takes into account handovers from TCH in traffic or insignaling mode.

C14c NB_TCH_DROP_EST_PHAS_ 1 X X Number of TCH (in HR or FR usage) drops in TCH established phase


16/119



Short


BSS_PB due to BSS problem.

It may happen that several causes of failures mentioned below aredetected consecutively. In that case, the counter will only be

incremented once, as soon as the call is released.This counter takes into account TCH in traffic or in signaling mode. It

is not incremented in case of TCH drop during a normal assignment,

a handover or a DTM assignment.

C15a NB_INC_IDR_ALLOC 1 X X X OK

MC15a=C15a, Number of incoming internal directed retry (towards aTCH channel in HR or FR usage) whose target channel is allocated

by the BSC.

C15b NB_INC_TCH_HO_ALLOC 1 X X X OK

Number of incoming TCH (in HR or FR usage) handover (internal or

external) -whose target channel is allocated by the BSC.Since there are no reliable means at the target BSC to distinguish

external directed retry from external handover, the external directedretries are counted by this counter.

C161aNB_DTAP_MO_NOR_ASS_SUCC 1 X X X BSC only Number of mobile originating normal assignment - DTAP successes.

C161b

NB_DTAP_MT_NOR_ASS_SU

CC 1 X X X BSC only Number of mobile terminating normal assignment - DTAP successes.

C162a

NB_TCH_DROP_DTAP_EST_

PHAS_RLF 1 X X

Number of TCH (in HR or FR usage) drops in TCH DTAP established

phase due to radio link failure (radio link timeout or Lapdm timerexpiry).

After an external handover, the target BSC considers that the

CONNECT ACK has not already been received.

C162bNB_TCH_DROP_DTAP_EST_PHAS_BSS_PB 1 X X

Number of TCH (in HR or FR usage) drops in TCH DTAP establishedphase due to BSS problem.

It may happen that several causes of failures mentioned below are

detected consecutively. In that case, the counterwill only be incremented once, as soon as the call is released.

After an external handover, the target BSC considers that theCONNECT ACK has not already been received.

C162c

NB_TCH_DROP_DTAP_EST_

PHAS_REM_TRANS_FAIL 1 X X

Number of TCH (in HR or FR usage) drops in TCH DTAP establishedphase due to remote transcoder failure. This counter is not

concerned by the channel change procedure.

C170 NB_CALL_TFO 1 X X X

Number of TCHs assigned in the serving cell for which TFO has been

successfully established.

C171 NB_TFO_CODEC_REQ 1 X X XNumber of codec mismatch resolutions or codec optimizationsrequested to the BSC.

C442

NB_TIMES_TRAF_DETECTED

_HIGH 1 X X X

Number of times the traffic_load is "high", i.e. when a certain number

(N_TRAFFIC_LOAD) of traffic averages (AV_LOAD) verify each:AV_LOAD > HIGH_THRESHOLD. The traffic_load is evaluated percell at each A_TRAFFIC_LOAD period.

This counter permits to tune the following parameters:A_TRAFFIC_LOAD, N_TRAFFIC_LOAD and HIGH_THRESHOLD.

This counter relates to the number of free TCH timeslots.

C443

NB_TIMES_TRAF_DETECTED

_LOW 1 X X X

Number of times the traffic_load is "low", i.e. when a certain number

(N_TRAFFIC_LOAD) of traffic averages (AV_LOAD) verify each:AV_LOAD < LOW_THRESHOLD. The traffic_load is evaluated per

cell at each A_TRAFFIC_LOAD period.

This counter permits to tune the following parameters:A_TRAFFIC_LOAD, N_TRAFFIC_LOAD and LOW_THRESHOLD.

This counter relates to the number of free TCH timeslots.

C612aNB_TCH_NOR_ASS_PREP_F

AIL_NO_QUEUE 1 X X OK

Number of TCH (in HR or FR usage) normal assignment preparation

failures because of the non-queuing of the ASSIGNMENT REQUESTmessage.

Case: 48.008ASSIGNMENT REQUEST on TCH (in HR or FR usage)is received when no TCH is available in the cell. The request is

rejected (by 48.008ASSIGNMENT FAILURE, cause: "no radioresource available"), because the queuing procedure is either:

1) disabled within the BSC (i.e. (T11=0 and

QUEUE_ANYWAY=0), OR (T11_forced=0 andQUEUE_ANYWAY=1)), or

2) enabled within the BSC, i.e. T11 0, but not requestedby the MSC when QUEUE_ANYWAY=0.

C612b

NB_TCH_NOR_ASS_PREP_F

AIL_QUEUE_FULL 1 X X X OK

MC612b=C612b, Case: 48.008ASSIGNMENT REQUEST on TCH (inFR or HR usage) is received when no TCH is available in the cell.

The queuing is enabled within the BSC, but the request is rejected (by48.008ASSIGNMENT FAILURE, cause: "no radio resource

available"), because the queue is full and no request of lower priority

can be dequeued from the BSC queue.

C612c


AIL_T11_EXP 1 X X X OK

Case: 48.008ASSIGNMENT REQUEST is queued because no TCH

(in HR or FR usage) is available in the cell, timer T11 (case MSC


17/119



Short


requests for queuing whatever QUEUE_ANYWAY value may be) or

timer T11_forced (case QUEUE_ANYWAY=1, i.e. the queuing isforced within the BSC) is started, and no free TCH can be found

before timer expiry, consequently the request is rejected (by 48.008CLEAR REQUEST cause: "no radio resource available").

Remark: If an internal directed retry is attempted and failed while

T11/T11_forced is running, the request is un-holded and the BSC

waits for the expiry of the relevant timer. Consequently, this countermust not be incremented upon the failure of an internal directed retry.

C612dNB_TCH_NOR_ASS_PREP_F

AIL_QUEUE_REJ 1 X X X OK

Case: 48.008ASSIGNMENT REQUEST is queued because no TCH(in HR or FR usage) is available in the cell, timer T11 (case MSC

requests for queuing whatever QUEUE_ANYWAY value may be) or

timer T11_forced (case QUEUE_ANYWAY=1, i.e. the queuing isforced within the BSC) is started, and before the timer expiry, the

request is dequeued due to the receipt of a higher priority request (i.e.48.008ASSIGNMENT REQUEST) : the BSC sends

48.008ASSIGNMENT FAILURE (cause: "no radio resource

available") for the first transaction.Remark: As soon as an internal directed retry is attempted, the

request is blocked within the BSC and cannot be dequeued by ahigher priority request.

C621

NB_TCH_DROP_OUT_HO_EX

EC_TRX 1 X X X

Number of TCH drops during the execution of any TCH outgoinghandover, per TRX.


MC621 = C621

C701a NB_TCH_FR_REQ 1 X X X BSC only Number of TCH normal assignments requests from FR only mobiles.

C701b NB_TCH_DR_REQ 1 X X X Number of TCH normal assignments requests from dual rate mobiles.

C701c NB_TCH_DR_EFR_REQ 1 X XNumber of TCH normal assignment requests from mobiles supportingFR, HR and EFR.

C701d NB_TCH_AMR_REQ 1 X X X Number of TCH normal assignment requests from AMR mobiles.

C701e NB_TCH_DATA_REQ 1 X X X Number of TCH normal assignment requests for data calls.

C702a NB_TCH_NOR_FR_ALLOC 1 X X X BSC only

number of TCH normal assignment/mode modify in FR usage -whose channel is allocated in the BSC.

This counter takes into account mode modify from TCH signaling to

TCH traffic (following a DTM assignment with a TCH in signalingmode).

C702b NB_TCH_NOR_HR_ALLOC 1 X X

number of TCH normal assignment/mode modify in HR usage -

whose channel is allocated in the BSC.

C702c NB_TCH_NOR_EFR_ALLOC 1 X X X

number of TCH normal assignment/mode modify in EFR usage -whose channel is allocated in the BSC.This counter takes into account mode modify from TCH signaling to


C703

NB_TCH_NOR_ASS_ALLOC_

TRX 1 X X X BSC only

Number of TCH (in HR or FR usage) normal assignment -whoseRTCH channel is allocated in the BSC, per TRX.

This counter also takes into account normal assignment whoseRTCH channel is allocated in the BSC in signaling mode (FR usage

only), for DTM.

MC703 = C703

C704aNB_TCH_NOR_AMR_FR_ALLOC 1 X X X

number of TCH normal assignment/mode modify in FR AMR usage -whose channel is allocated in the BSC.

This counter takes into account mode modify from TCH signaling to


C704bNB_TCH_NOR_AMR_HR_ALLOC 1 X X X

number of TCH normal assignment/mode modify in HR AMR usage -whose channel is allocated in the BSC.

C705 NB_TCH_NOR_DATA_ALLOC 1 X X X

number of TCH normal assignment/mode modify for data - whose

channel is allocated in the BSC.This counter takes into account mode modify from TCH signaling to


C706

NB_EGSM_MS_ACCESS_EX

CEPT_LU 1 X X

Number of initial accesses for call establishments (except locationupdate) of MS supporting the E-GSM band, on a CELL basis.

MC706 = C706

C710 NB_TCH_OUT_HO_REQ_TRX 1 X X X BSC only

Nb of TCH outgoing handover requests, per TRX. Intracell, internal

intercell and external handovers are counted together.This counter takes into account handovers from TCH in traffic or in

signaling mode. It does not take into account DTM Assignments.MC710 = C710

C711

NB_TCH_OUT_HO_PREP_FAI

L_CONG_TRX 1 X X X

Nb of outgoing TCH handover -preparation failures due to congestion,

per TRX. Intracell, internal intercell and external handovers are


18/119



Short


counted together.

This counter takes into account handovers from TCH in traffic or insignaling mode. It does not take into account DTM Assignments,

MC711 = C711

C712 NB_TCH_OUT_HO_SUCC_TRX 1 X X X BSC only

Nb of outgoing TCH handover successes, per TRX. Intracell, internal

intercell and external handovers are counted together.This counter takes into account handovers from TCH in traffic or in


C713NB_TCH_OUT_HO_FAIL_REV

_TRX 1 X X X

Nb of outgoing TCH handover -execution failures due to MS accessproblem with reversion of the mobile to the old channel. Intracell,

internal intercell and external handovers are counted together.This counter takes into account handovers from TCH in traffic or in


C714NB_TCH_OUT_HO_FAIL_NO_REV_TRX 1 X X

Nb of outgoing TCH handover -execution failures due to MS accessproblem without reversion of the mobile to the old channel (call drop).

Intracell, internal intercell and external handovers are countedtogether.

This counter takes into account handovers from TCH in traffic or in


C717a NB_INC_IDR_SUCC_TRX 1 X X X OK

Number of incoming directed retry (towards a TCH channel in HR or

FR usage) successes, per TRX.MC717a = C717a

C717b

NB_INC_TCH_HO_SUCC_TR

X 1 X X X OK

Number of incoming internal and external TCH (in HR or FR usage)handover successes per TRX;

since there are no reliable means at the target BSC to distinguish

external directed retry from external handover, the external directedretries are counted by this counter.

MC717b = C717b

C718NB_TCH_NOR_ASS_SUCC_TRX 1 X X X BSC only

Number of TCH (in HR or FR usage) normal assignment successes,per TRX. This counter also takes into account normal assignment

successes for TCH establishment in signaling mode (FR usage only),

for DTM.MC718 = C718

C736 NB_TCH_DROP_EST_PHAS_RLF_TRX 1 X X

Number of TCH (in HR or FR usage) drops in TCH established phase

due to radio link failure (radio link timeout or Lapdm timer expiry), per

TRX.

This counter takes into account TCH in traffic or in signaling mode.MC736 = C736

C739

NB_TCH_DROP_EST_PHAS_

REM_TRANS_FAIL_TRX 1 X X

Number of TCH (in HR or FR usage) drops in TCH established phase

due to remote transcoder failures (per TRX).

C746bNB_TCH_NOR_ASS_EXEC_F

AIL_RADIO_TRX 1 X X X OK

Number of TCH (in HR or FR usage) normal assignment -executionfailures due to MS access problem, per TRX. This counter also takes

into account DTM assignment -execution failures due to MS access

problem for TCH establishment in signaling mode (FR usage only).MC746b = C746b

C812


AIL_CONG_R_ABIS 1 X X X OK C812 = C612a + C612b + C612c + C612d

C850

NB_MULTIBAND_MS_ACCES

S_EXCEPT_LU_CELL 1 X X X

Number of initial accesses for call establishments (location update

apart) initiated by multiband mobile stations. The counter is definedon a per cell basis.

A MS is considered as multiband if it supports:

- the P-GSM (or E-GSM or R-GSM) and the DCS1800 bands if the

PLMN_FREQUENCY_BANDS parameter is set to "GSM900 andDCS1800 bands", or,- the GSM850 and the DCS1800 bands if the

PLMN_FREQUENCY_BANDS parameter is set to "GSM850 andDCS1800 bands", or,

- the GSM850 and the DCS1900 bands if the


- the P-GSM (or E-GSM or R-GSM) and the DCS1900 bands if thePLMN_FREQUENCY_BANDS parameter is set to "GSM900 and

DCS1900 bands".

C901 NB_Suspend_req 1 X X OK

Number of suspend requests.

A request could lead to a success, a failure or a stop.

C902 Nb_Suspend_fail 1 X X Number of suspend/resume procedure failures.

C903 Nb_Suspend_succ 1 X X OK Number of suspensions successes.

C141 AV_NB_TCH_QUEUED 2 X X

Average number of queued TCH (in HR or FR usage) normal

assignment or external handover requests.


19/119



Short


C24 AV_NB_NOT_AVAIL_TRX_TS 2 X X X BSC only Average number of not available radio timeslots (TRX_TS).

C250 AV_NB_AVAIL_TCH 2 X X X BSC only

Average number of available TCH/PDCH timeslots for traffic usage

(i.e. TCH (for HR or FR usage) or PDCH).

C26 AV_NB_AVAIL_SDCCH 2 X X X BSC only

Average number of available static SDCCH sub-channels (i.e. on

static SDCCH timeslots).

C27 AV_NB_AVAIL_CCCH 2 X X X Average number of available CCCH channels.

C28a AV_NB_BUSY_CS_TS 2 X X X OK

Average number of busy TCH radio timeslot (in FR or HR usage, in

traffic or in signaling mode) and busy dynamic SDCCH/8 radiotimeslot allocated as TCH.

C29a

NB_MAX_SIMUL_BUSY_CS_T

S 2 X X X OK

Maximum number of simultaneously busy TCH radio timeslots (in HR

or FR usage, in traffic or in signaling mode) and simultaneously busy

dynamic SDCCH/8 radio timeslots allocated as TCH.

C30 AV_NB_BUSY_SDCCH 2 X X X BSC only

Average number of busy SDCCH subchannels, taking into accountthe following SDCCH sub-channels: 1) Static SDCCH/x sub-channels,

2) Dynamic SDCCH sub-channels which are dynamically allocated on

the dynamic SDCCH/8 timeslots.

C31

NB_MAX_SIMUL_BUSY_SDC

CH 2 X X X BSC only

Maximum number of simultaneously busy SDCCH subchannels,taking into account the following SDCCH sub-channels: 1) Static

SDCCH/x sub-channels, 2) Dynamic SDCCH sub-channels which are

dynamically allocated on the dynamic SDCCH/8 timeslots.

C320a

AV_NB_IDLE_TCH_INTERF_B

AND1 2 X X X BSC only

Average number of free TCH and free dynamic SDCCH/8 radiotimeslots belonging to the interference band 1. This number is

updated upon the receipt of 48.058 RF RESOURCE INDICATION.

C320bAV_NB_IDLE_TCH_INTERF_BAND2 2 X X X BSC only

Average number of free TCH and free dynamic SDCCH/8 radiotimeslots belonging to the interference band 2. This number isupdated upon the receipt of 48.058 RF RESOURCE INDICATION.

C320c





C320d



Average number of free TCH and free dynamic SDCCH/8 radio

timeslots in FR or HR usage belonging to the interference band 4.This number is updated upon the receipt of 48.058 RF RESOURCE

INDICATION.

C320e





C34TIME_ALL_AVAIL_TRX_TS_BUSY 2 X X X BSC only

Cumulated time (in seconds) during which there is no free FR TCH

sub-channel to serve an incoming FR TCH request.A TCH sub-channel is seen as busy:

i) if the TCH sub-channel is occupied by a HR or FR CS call (inparticular if it is occupied by the CS part of a DTM call), orii) if the TCH sub-channel is allocated to the MFS to carry PS traffic.

C803 TIME_SDCCH_CONGESTION 2 X X X BSC only

Cumulated time (in seconds) during which the SDCCH request(s) are

not served because no SDCCH sub-channel is available.

C8a NB_PAGING_CMD 3 X X X OK

PCH load: number of 48.058 PAGING COMMAND messages sent

either for PS traffic or for CS traffic on Abis towards the selected cell.

C8b NB_IMM_ASS_CMD 3 X X X OK

AGCH load: number of 48.058 IMMEDIATE ASSIGN COMMAND

messages sent for CS traffic on Abis to the MS.

C8c NB_CHAN_REQD 3 X X X OK

RACH load: number of 48.058 CHANNEL REQUIRED received viathe selected cell.

All the CHANNEL REQUIRED messages are counted whatever the

Establishment Cause is.

C8d NB_IMM_ASS_REJ 3 X X X

Number of 48.058 CHANNEL REQUIRED received while no SDCCHcan be allocated by the BSC (congestion), i.e. the number of

44.018IMMEDIATE ASSIGNMENT REJECT sent to the MS via the

selected cell.

C39 NB_TIMES_SDCCH_BUSY 4 X X X OKNumber of times the SDCCH sub-channels belonging to the radiotimeslot are busy.

C40 TIME_SDCCH_BUSY 4 X X X OKCumulated time during which the SDCCH sub-channels belonging tothe related static or dynamic SDCCH timeslot are busy.

C370a NB_TCH_FR_ALLOC 5 X X X OK

Number of times a TCH radio timeslot or a dynamic SDCCH/8

timeslot is allocated in FR usage, for normal assignment, for DTM

assignment or handover, in traffic or in signaling mode.

C370b NB_TCH_HR_ALLOC 5 X X X OK

Number of times a TCH radio timeslot or a dynamic SDCCH/8timeslot is allocated in HR usage (i.e. the upper or lower HR sub-

channel of the radio timeslot is allocated), for normal assignment or

handover.

C380a TIME_FR_TCH_BUSY 5 X X X OK

Time (in seconds) during which a TCH radio timeslot or a dynamicSDCCH/8 timeslot in FR usage (in traffic or in signaling mode) is

busy.

C380b TIME_HR_TCH_BUSY 5 X X X OK

Time during which a TCH radio timeslot or a dynamic SDCCH/8

timeslot in HR usage is busy.


20/119



Short


C381a

TIME_FR_TCH_BUSY_BY_MU

LTIBAND_MS 5 X X X OK

Time (in seconds) during which the TCH radio timeslot or the dynamic

SDCCH/8 timeslot in FR usage (in traffic or in signaling mode) is busyby a multiband mobile station.

A MS is considered as multiband if it supports:- the P-GSM (or E-GSM or R-GSM) and the DCS1800 bands if the

PLMN_FREQUENCY_BANDS parameter is set to "GSM900 and

DCS1800 bands", or,

- the GSM850 and the DCS1800 bands if thePLMN_FREQUENCY_BANDS parameter is set to "GSM850 andDCS1800 bands", or,

- the GSM850 and the DCS1900 bands if thePLMN_FREQUENCY_BANDS parameter is set to "GSM850 and

DCS1900 bands", or,


DCS1900 bands".

C381b

TIME_HR_TCH_BUSY_BY_M

ULTIBAND_MS 5 X X X OK

Time during which the TCH radio timeslot or the dynamic SDCCH/8

timeslot in HR usage is busy by a multiband mobile station. A TCHradio timeslot (or a dynamic SDCCH/8 timeslot) in HR usage is said

busy by a multiband mobile station when one or two HR sub-channelsare busy by a multiband mobile station.

A MS is considered as multiband if it supports:- the P-GSM (or E-GSM or R-GSM) and the DCS1800 bands if the

PLMN_FREQUENCY_BANDS parameter is set to "GSM900 and

DCS1800 bands", or,- the GSM850 and the DCS1800 bands if the


- the GSM850 and the DCS1900 bands if the



DCS1900 bands".

C220 NB_INC_EXT_TCH_HO_REQ 6 X X X BSC only

Number of incoming external TCH (in HR or FR usage) handover

requests.

C221 NB_INC_EXT_TCH_HO_ATPT 6 X X X BSC onlyNumber of incoming external TCH (in HR or FR usage) handoverattempts.

C230 NB_INC_INT_TCH_HO_REQ 6 X X XNumber of incoming internal inter cell TCH (in HR or FR usage)handover requests.

C231 NB_INC_INT_TCH_HO_ATPT 6 X X XNumber of incoming internal inter cell TCH (in HR or FR usage)handover attempts.

C270 NB_INTRA_TCH_HO_REQ 6 X X OK

Number of intra cell TCH (in HR or FR usage) handover requests

This counter takes into account handovers from TCH in traffic or insignaling mode. It does not take into account DTM Assignments.

C271 NB_INTRA_TCH_HO_ATPT 6 X X OK

Number of intra cell TCH (in HR or FR usage) handover attempts.This counter takes into account handovers from TCH in traffic or in

signaling mode. It does not take into account DTM Assignments,

C411NB_OUT_INT_TCH_HO_IDR_IN_ZONE_REQ 6 X X X OK

Number of outgoing internal inter-cell TCH (in HR or FR usage)

handover requests, plus the number of internal directed retriesrequests, towards the inner zone of a target concentric cell.

C412

NB_OUT_INT_TCH_HO_IDR_I

N_ZONE_EXEC_FAIL 6 X X OK

Number of outgoing internal inter-cell TCH (in HR or FR usage)

handover -executions failures, plus the number of internal directed

retries -execution failures due to MS access problem, towards theinner zone of a target concentric cell.

This counter permits to tune the EN_BETTER_ZONE_HO parameter.

C413NB_TCH_NOR_ASS_INNER_ZONE_ALLOC 6 X X X OK

Number of TCH (in HR or FR usage) normal assignment -whose

resource is allocated in the BSC, in the inner zone of a concentriccell.

C41b

NB_INC_EXT_TCH_HO_PREP

_FAIL_NO_TTCH 6 X X

Number of incoming external TCH (in HR or FR usage) handover -

preparation failures due to A-traffic-channel status mismatch between

the BSC and the MSC.

C42NB_INC_EXT_TCH_HO_SUCC 6 X X X BSC only

Number of incoming external TCH (in HR or FR usage) handoversuccesses.

C43NB_INC_EXT_TCH_HO_EXEC

_FAIL_MS_ACCESS 6 X X XMC43=C43, Number of incoming external TCH (in HR or FR usage)handover -execution failures due to MS access problem.

C440

NB_TCH_HO_ATPT_23_TrafH

andover 6 X X X OK

MC440=C440, Number of inter-cell internal or external handover

attempts, with the cause 23: "traffic handover" on a TCH channel (in

HR or FR usage).

C444

NB_TCH_HO_ATPT_24_GenC

aptureHandover 6 X X X

Number of inter-cell internal or external handover attempts, with thecause 24: "general capture handover" on a TCH channel (in HR or FR

usage).


21/119



Short


C447

NB_TCH_HO_ATPT_26_BadQ

ualHR 6 X X X

Number of intracell handover attempts, with the cause 26: "HR to FR

channel adaptation due to bad radio quality" on a TCH channel.

C448NB_TCH_HO_ATPT_27_GoodQualFR 6 X X X

Number of intracell handover attempts, with the cause 27: "FR to HRchannel adaptation due to good radio quality" on a TCH channel.

C449NB_TCH_HO_ATPT_28_FastTraffic 6 X X X

Number of handover attempts, with the cause 28 (Fast TrafficHandover).

C450NB_TCH_HO_ATPT_22_TooShortDistance 6 X X X OK

Number of inter-cell internal or external handovers attempts, with

cause 22: "too short MS-BTS distance" on a TCH channel (in HR orFR usage). Only the outer zones of extended cells are concerned bythis counter.

C45aNB_OUT_EXT_TCH_REAL_HO_REQ 6 X X X BSC only

Number of outgoing external TCH (in HR or FR usage) handover

requests.


C46NB_OUT_EXT_TCH_HO_SUCC 6 X X X BSC only

MC46=C46, Number of outgoing external TCH (in HR or FR usage)

handover successes.


C460

NB_TCH_HO_ALLOC_EMERG

ENCY_PRES 6 X X X BSC only

Number of high priority TCH requests served when the number of free

TCH timeslots is less than or equal to NUM_TCH_EGNCY_HO.

C461 NB_TCH_HO_ATPT_29_TFO 6 X X X

Number of intra-cell handover - attempts, with the cause 29 (TFO

mismatch resolution, TFO optimization).MC461 = C461

C47

NB_OUT_EXT_TCH_HO_EXE

C_FAIL_REV 6 X X

MC47=C47, Number of outgoing external TCH (in HR or FR usage)handover -execution failures due to MS access problem with

reversion of the mobile to the old channel.This counter takes into account handovers from TCH in traffic or in

signaling mode.

C470NB_TCH_HO_ATPT_2_TooLo

wQualUp 6 X X

Number of inter-cell internal or external handover attempts, with

cause 2: "uplink quality too low" on a TCH channel (in HR or FRusage).


C471

NB_TCH_HO_ATPT_3_TooLo

wLevUp 6 X X X BSC only

Number of inter-cell internal or external handovers attempts, withcause 3: "uplink level too low" on a TCH channel (in HR or FR

usage).This counter takes into account handovers from TCH in traffic or in

signaling mode.

C472


wQualDown 6 X X X


cause 4: "downlink quality too low" on a TCH channel (in HR or FRusage).


signaling mode.

C473


wLevDown 6 X X

Number of inter-cell internal or external handover attempts, withcause 5: "downlink level too low" on a TCH channel (in HR or FR

usage).This counter takes into account handovers from TCH in traffic or in

signaling mode.

C474


ngDistance 6 X X OK


cause 6: "MS-BTS distance too long" on a TCH channel (in HR or FRusage).


signaling mode.

C476NB_TCH_HO_ATPT_15_TooHighLevInterfUp 6 X X

Number of intra-cell handover attempts, with cause 15: "too high levelinterference on uplink" on a TCH channel (in HR or FR usage).


C477

NB_TCH_HO_ATPT_16_TooHi

ghLevInterfDown 6 X X

Number of intra-cell handover attempts, with cause 16: "too high levelinterference on downlink" on a TCH channel (in HR or FR usage).


signaling mode.

C478NB_TCH_HO_ATPT_12_TooLowPowBudg 6 X X X

Number of inter-cell internal or external handover attempts, withcause 12: "too low power budget" on a TCH channel (in FR or FR

usage).


C479NB_TCH_HO_ATPT_21_HighLevNeigCellPrefBand 6 X X X OK


cause 21: "high level in neighbor cell in the preferred band" on a TCHchannel (in HR or FR usage). This counter is related to multiband.

C48

NB_OUT_EXT_TCH_HO_EXE

C_FAIL_NO_REV 6 X X

MC48=C48, Number of outgoing external TCH (in HR or FR usage)handover execution failures due to MS access problem without

reversion of the mobile to the old channel (call drop).


22/119



Short



signaling mode.

C50

NB_OUT_EXT_TCH_HO_ATP

T 6 X X X BSC only

MC50=C50, Number of outgoing external TCH (in HR or FR usage)handover attempts.


signaling mode.

C52 NB_INC_INT_TCH_HO_SUCC 6 X X X OK

MC52=C52, Number of incoming internal inter-cell TCH (in HR or FR

usage) handover successes.

C53

NB_INC_INT_TCH_HO_EXEC

_FAIL_MS_ACCESS 6 X X X

MC53=C53, Number of incoming internal inter-cell TCH (in HR or FRusage) handover -execution failures due to MS access problem; the

mobile either reverts or does not to the old channel.

C541NB_INC_EXT_TCH_HO_PREP

_FAIL_R_ABIS 6 X X


preparation failures due to congestion (C541a), or A-traffic-channelstatus mismatch between the BSC and the MSC (C41b).

C541a

NB_INC_EXT_TCH_HO_PREP

_FAIL_CONG_R_ABIS 6 X X


preparation failures due to congestion.

C551

NB_INC_INT_TCH_HO_PREP

_FAIL_CONG_R_ABIS 6 X X

Number of incoming internal inter-cell TCH (in HR or FR usage)

handover -preparation failures due to congestion.

C55a NB_OUT_INT_TCH_HO_REQ 6 X X X

MC55a=C55a, Number of outgoing internal inter-cell TCH (in HR or

FR usage) handover requests.This counter takes into account handovers from TCH in traffic or in

signaling mode.

C56

NB_OUT_INT_TCH_HO_SUC

C 6 X X X

MC56=C56, Number of outgoing internal inter-cell TCH (in HR or FR

usage) handover successes.This counter takes into account handovers from TCH in traffic or in

signaling mode.

C561

NB_INTRA_TCH_HO_PREP_F

AIL_CONG_R_ABIS 6 X X

Number of intra-cell TCH (in HR or FR usage) handover -preparationfailures due to congestion.


signaling mode. It does not take into account DTM Assignments.

C57NB_OUT_INT_TCH_HO_EXEC_FAIL_REV 6 X X

Number of outgoing internal inter-cell TCH (in HR or FR usage)handover -execution failures due to MS access problem with

reversion of the mobile to the old channel.


C58

NB_OUT_INT_TCH_HO_EXE

C_FAIL_NO_REV 6 X X

MC58=C58, Number of outgoing internal inter-cell TCH (in HR or FR

usage) handover -execution failures due to MS access problem

without reversion of the mobile to the old channel (call drop).This counter takes into account handovers from TCH in traffic or in

signaling mode.

C585a

NB_TCH_HO_ATPT_7_ConsB

adSACCHmicroCell 6 X X


cause 7: "several consecutive bad SACCH frames received in a microcell" on a TCH channel (in HR or FR usage).


This counter is related to micro cell environment.

C585d

NB_TCH_HO_ATPT_17_TooL

owLevUpMicroCell 6 X X


cause 17: "too low level on the uplink in a microcell compared to ahigh threshold" on a TCH channel (in HR or FR usage).


This counter is related to micro cell environment.

C585eNB_TCH_HO_ATPT_18_TooLowLevDownMicroCell 6 X X


cause 18: "too low level on the downlink in a microcell compared to ahigh threshold" on a TCH channel (in HR or FR usage).

This counter takes into account handovers from TCH in traffic or insignaling mode.This counter is related to micro cell environment.

C585fNB_TCH_HO_ATPT_14_HighLevNeigLowCellSlowMS 6 X X X


cause 14: "high level in neighbour lower layer for slow mobile" on a

TCH channel (in HR or FR usage). This counter is related to microcell environment.

C586a


owLevUpInZone 6 X X X OK

Number of intra-cell handover attempts, with cause 10 "Inner zone

uplink level too low" on TCH channel (in HR or FR usage). This

counter is related to concentric cell environment.

C586b


owLevDownInZone 6 X X X OK

Number of intra-cell handover attempts, with cause 11: "Inner zonedownlink level too low" on TCH channel (in HR or FR usage). This

counter is related to concentric cell environment.

C586cNB_TCH_HO_ATPT_13_TooHighLevUpDownOutZone 6 X X X OK

Number of intra-cell handover attempts, with cause 13: "Outer zone

uplink and downlink levels too high" on TCH channel (in HR or FRusage). This counter is related to concentric cell environment.

C60 NB_OUT_INT_TCH_HO_ATPT 6 X X X MC60=C60, Number of outgoing internal inter-cell TCH (in HR or FR


23/119



Short


usage) handover attempts.


C62 NB_INTRA_TCH_HO_SUCC 6 X X X

MC62=C62, Number of intra-cell TCH (in HR or FR usage) handover

successes.

This counter takes into account handovers from TCH in traffic or insignaling mode. It does not take into account DTM Assignments,

C63NB_INTRA_TCH_HO_EXEC_F

AIL_NO_REV 6 X X X

MC63=C63, Number of intra-cell TCH (in HR or FR usage) handoverexecution failures due MS access problem; the mobile is lost.

This counter takes into account handovers from TCH in traffic or insignaling mode. It does not take into account DTM Assignments.

C67

NB_INTRA_TCH_HO_EXEC_F

AIL_REV 6 X X X

MC67=C67, Number of intra-cell TCH (in HR or FR usage) handover -

execution failures due to MS access problem with reversion of themobile to the old channel.


signaling mode. It does not take into account DTM Assignments.

C75 NB_TCH_HO_MSC_TRIG 6 X XMC75=C75, Number of external handovers triggered by the MSC butnot required by the BSS.

L1.1NB_LAPD_INFO_FRAME_SENT 7 X X

Number of Information frames transmitted on the LapD link, excludingthe re-transmissions.

L1.12 NB_LAPD_CRC_ERROR 7 X X Number of frames received with CRC error on the LapD link.

L1.15NB_LAPD_INFO_FRAME_RESENT 7 X X Number of Information frames re-transmitted on the LapD link.

L1.16 TIME_LAPD_UNAVAIL 7 X XTime (in seconds) during which the LapD link is unavailable for anycause.

L1.17 NB_LAPD_EST 7 X X

Number of data link establishment, re-establishment and reset on the

LapD link.

L1.18 TIME_LAPD_CONG 7 X X

Time in seconds during which the LapD link is congested in

transmission in the BSC.

L1.2

NB_LAPD_INFO_FRAME_RE

C 7 X X

Number of Information frames received on the LapD link, excluding

the re-transmissions.

L1.5 NB_LAPD_RNR_SENT 7 X XNumber of Receive Not Ready (RNR) frames transmitted on the LapDlink.

L1.6 NB_LAPD_RNR_REC 7 X XNumber of Receive Not Ready (RNR) frames received on the LapDlink.

X3.20

NB_X25_INC_CALL_SUCC_C

LOSED 8 X X

Number of incoming X.25 calls that are successfully closed by the

BSC.

X3.21

NB_X25_OUT_CALL_SUCC_C

LOSED 8 X X

Number of outgoing X.25 calls that are successfully closed by the

BSC.

X3.22NB_X25_INC_CALL_ABNORM

_CLOSED 8 X XNumber of incoming X.25 calls that are closed in an abnormal way, asseen by the BSC.

X3.23NB_X25_OUT_CALL_ABNORM_CLOSED 8 X X

Number of outgoing X.25 calls that are closed in an abnormal way, asseen by the BSC.

N1.1 TIME_N7_ALIGNED 9 X X Time (in seconds) during which the N7 SL is correctly aligned.

N1.10 NB_N7_CHANGEOVER 9 X XNumber of changeovers from the primary (observed) N7 SL toanother secondary one.

N1.11 NB_N7_CHANGEBACK 9 X XNumber of change backs from the secondary (observed) N7 SL to theprimary one.

N1.12 NB_N7_RESTORATION 9 X X X BSC only Number of N7 SL restorations (i.e. correctly aligned after a failure).

N1.2NB_N7_LINK_FAIL_ANY_CAUSE 9 X X X BSC only Number of N7 SL failures (any reason).

N1.3 NB_N7_LINK_FAIL_FIB_BSN 9 X X

Number of Forward Indicator Bits (FIB) and Backward Sequence

Number (BSN) on the N7 SL.

N1.4 NB_N7_LINK_FAIL_T7_EXP 9 X X Number of N7 SL failures due to non acknowledgment in time.

N1.5

NB_N7_LINK_FAIL_SU_ERRO

R_RATE 9 X X Number of N7 SL failures due to excessive signal unit error rate.

N1.6 NB_N7_LINK_FAIL_CONG 9 X X

Number of N7 SL failures due to congestion during an extended

period of time.

N1.7

NB_N7_LINK_FAIL_ALIGNME

NT 9 X X X BSC only

Number of N7 SL failures due to expiry of timer supervising the

alignment.

N1.8NB_N7_SU_REC_WITH_ERROR 9 X X Number of Signaling Units received with errors on the N7 SL.

N1.9 NB_N7_NEG_ACK_REC 9 X X Number of Negative Acknowledgment received on the N7 SL.

N2.7TIME_N7_UNAVAIL_ERROR_SL 9 X X X BSC only

Time (in seconds) during which the N7 SL is not correctly aligned dueto a fault on the N7 SL.

N2.9TIME_N7_UNAVAIL_MSC_PROC_OUTAGE 9 X X

Time (in seconds) during which the N7 SL is not available due to aremote MSC processor outage.

N3.1 NB_N7_SIF_SIO_SENT 9 X X X BSC only

Number of octets of Signaling Information (SIF) and Service

Information Octets (SIO) transmitted on the N7 SL.

N3.10

NB_N7_MSU_DISC_DUE_CO

NG 9 X X

Number Message Signaling Units (MSU) discarded due to a message

buffer overflow caused by an extended period of Signaling Link


24/119


25/119



Short


9 : MO : IMSI detach indication

10: MO : Emergency Call

S06 MS_POWER 10 X X X BSC only

Indicates the last commanded MS Power Level on the SACCHChannel to the Mobile.

This counter corresponds to the MS_POWER field of the 48.058

PHYSICAL CONTEXT CONFIRM message.

S07 BS_POWER 10 X X X BSC only

Indicates the last commanded BS Power Level to the encoder.

This counter corresponds to the BS_POWER field of the 48.058PHYSICAL CONTEXT CONFIRM message.

S08 TIMING_ADVANCE 10 X X X BSC only

Indicates the last commanded Timing Advance on the SACCH

Channel to the Mobile.This counter corresponds to the TIMING_ADVANCE field of the

48.058 PHYSICAL CONTEXT CONFIRM message.

S09NB_FRAMES_NOT_REPEATED 10 X X X BSC only

Indicates the number of SAPI 0 frames that were not repeated.

This counter corresponds to the CNT_I_TX field of the 48.058PHYSICAL CONTEXT CONFIRM message.

S16 NB_FRAMES_REPEATED 10 X X X BSC only

Indicates the number of SAPI 0 frames that were repeated at leastonce.

This counter corresponds to the CNT_I_RETX field of the 48.058PHYSICAL CONTEXT CONFIRM message.

S17 NB_SABM_AFTER_UA_SENT 10 X X X BSC only

Indicates the number of SABM received on SAPI 0 when UA has

already been sent (i.e. SABM received in established or timer

recovery state).

This counter corresponds to the CNT_SABM_RX field of the 48.058PHYSICAL CONTEXT CONFIRM message.

S18 NB_PHYSICAL_INFO_SENT 10 X X X BSC only

Indicates the number of times 44.018 PHYSICAL INFORMATION

message has been sent in case of asynchronous handover.This counter corresponds to the CNT_PHY_INFO_TX field of the


S19NB_ERRONEOUS_FRAMES_SENT 10 X X X BSC only

Indicates the number of erroneous frames that were received.

This counter corresponds to the CNT_ERR_RX field of the 48.058PHYSICAL CONTEXT CONFIRM message.

S20 NB_REJ_FRAMES_SENT 10 X X X BSC only

Indicates the number of Reject (REJ) frames that were transmitted.

This counter corresponds to the CNT_REJ_TX field of the 48.058


S21

NB_REJ_FRAMES_RECEIVE

D 10 X X X BSC only

Indicates the number of Reject (REJ) frames that were received.This counter corresponds to the CNT_REJ_RX field of the 48.058


S22 NB_MS_TX_PWR_MAX_SENT 10 X X X BSC only

This counter indicates the number of 48.058 CONNECTION

FAILURE INDICATION messages that were sent to the BSS with acause value of "set YY_TXPWR_M".

This counter corresponds to the CNT_MS_TXPWR_MAX field of the


S23

RADIO_LINK_FAILURE_INDIC

ATION 10 X X X BSC only

Indicates whether or not a Radio Link Failure was detected or not.0: No connection failure occurred on the SDCCH Sub-channel

1: A 48.058 CONNECTION FAILURE INDICATION message wasreceived with a cause value of "radio link failure".

This counter corresponds to the RL_FAILURE_INDICATOR field of

the 48.058 PHYSICAL CONTEXT CONFIRM message.

S24

PERC_INCOR_SACCH_FRAM

ES_REC 10 X X X BSC only

Indicates the percentage of SACCH frames that could not bedecoded.

This counter corresponds to the CNT_SA_BFI_RX/CNT_SA_RX field

of the 48.058 PHYSICAL CONTEXT CONFIRM message.

S25PERC_INCOR_SDCCH_FRAMES_REC 10 X X X BSC only

Indicates the percentage of SDCCH frames that could not bedecoded.

This counter corresponds to the CNT_SD_BFI_RX/CNT_SD_RX fieldof the 48.058 PHYSICAL CONTEXT CONFIRM message.

S26 SAMPLE_RATE 10 X X X BSC onlyIndicates the sample rate value at the time the observation iscollected.

R01 CHANNEL_ID (TCH) 11 X X

The RTCH channel identity to which the Observation relates,including BTS Number, Sector Number, TRX Number, TRX Timeslot

and Sub-channel which is only significant in case of an half rate TCHchannel.

Note : The sub-channel field may take a value contained between 0

and 1 in case of an half rate TCH channel. In case of a full rate TCHchannel the sub-channel field which is not significant is set to zero.

R01a RTCH_TYPE 11 X X

The RTCH channel type to which the Observation relates :

0: for a full rate RTCH channel1: for an half rate RTCH channel.

R03 RECEIVED_TIMESTAMP 11 X X

The Absolute Date and Time at which the measurement resultmessage was received from the CELL by the BSS. The time is

accurate to tenths of a second.


26/119



Short


R04 AV_RXLEV_UL_HO (11) 11 X X

Indicates the average receive uplink level of the serving cell, as used

by the handover algorithm.

R04a AV_RXLEV_UL_MCHO (11) 11 X X

This observation data is only related to microcellular environment. Itindicates the average receive uplink level of the serving cell, as used

by the handover algorithm.

R05 AV_RXLEV_DL_HO (11) 11 X X

Indicates the average receive downlink level of the serving cell, as

used by the handover algorithm.

R05a AV_RXLEV_DL_MCHO (11) 11 X X

This observation data is only related to microcellular environment. Itindicates the average receive downlink level of the serving cll, asused by the handover algorithm.

R06 AV_RXLEV_PBGT_HO (11) 11 X X

Indicates the average received Downlink Level of the serving cell, as

used by the Power Budget algorithm.

R07 AV_RXQUAL_UL_HO (11) 11 X X

Indicates the average receive uplink quality of the serving cell, as


R08 AV_RXQUAL_DL_HO (11) 11 X X

Indicates the average receive downlink quality of the serving cell, as


R09 AV_RANGE_HO (11) 11 X XIndicates the average distanc between Mobile and Base station, asused by the handover algorithm.

R10 MS_TXPWR 11 X X Transmit power at the Mobile.

R1013 BSIC 11 X X The Base Station Identity Code (BSIC) of a neighboring cell.

R1014 BCCH_FREQ 11 X X The Absolute BCCH Radio Frequency Number of a neighboring cell.

R1015 AV_RXLEV_NCELL 11 X X The average receive level of a neighboring cell as seen by the Mobile.

R1016 PBGT 11 X X

The Power Budget evaluation of reception of a neighboring cell

related to the serving cell.R11 BS_TXPWR 11 X X Transmit power at the BTS.




R1116 PBGT 11 X X


related to the serving cell.




R116 PBGT 11 X XThe Power Budget evaluation of reception of a neighboring cellrelated to the serving cell.

R12 BTSNUM 11 X X

Indicates the number of neighboring cells for which measurements

made by the Mobile are available during the averaging interval.

Measurements of up to 32 Neighboring cells can be provided.








R1316 PBGT 11 X X






R1416 PBGT 11 X X




R1514 BCCH_FREQ 11 X X The Absolute BCCH Radio Frequency Number of a neighboring cell.R1515 AV_RXLEV_NCELL 11 X X The average receive level of a neighboring cell as seen by the Mobile.





R1616 PBGT 11 X X



R17 SAMPLE_RATE 11 X X

Indicates the sample rate value at the time the observation is

collected.







27/119



Short




R1816 PBGT 11 X X










R2016 PBGT 11 X X










R216 PBGT 11 X X










R2316 PBGT 11 X X






R2416 PBGT 11 X X


related to the serving cell.R2513 BSIC 11 X X The Base Station Identity Code (BSIC) of a neighboring cell.



R2516 PBGT 11 X X










R2716 PBGT 11 X X










R2916 PBGT 11 X X









28/119



Short




R3116 PBGT 11 X X










R3216 PBGT 11 X X










R516 PBGT 11 X X










R716 PBGT 11 X X






R816 PBGT 11 X X


related to the serving cell.R913 BSIC 11 X X The Base Station Identity Code (BSIC) of a neighboring cell.



R916 PBGT 11 X X



HO1 SIGNALLING_TRAFFIC_IND 12 X X X BSC only

Indicates whether or not the observation record relates to an SDCCH

handover or RTCH handover attempt. Valid coding is provided below,all other codings are invalid.

0: handover was for an SDCCH Sub-channel1: handover was for an RTCH channel.

HO1047 BSIC 12 X X The Base Station Identity Code (BSIC) of a neighboring cell.

HO1048 FREQ 12 X X The Absolute Radio Frequency Number of a neighboring cell.

HO1049 RXLEV 12 X X

The last 4 a Receive Levels of a neighboring cell as seen by the

Mobile.

HO11 HO_CAUSE 12 X X X Indicates the reason for the external handover attempt.

HO1147 BSIC 12

counter and indicators status bssaw01b_ed02

Documents