BSS S12 CS Counter Block Pics

1 © Nokia Siemens Networks CS Counter Block Pictures / Hannu Makkonen For internal use

BSS CS Counters & Formulas


BSS CS COUNTERS & FORMULAS

3/2008

NOTE:

This document is maintained by BSS GSM Performance Working Group.

This document is globally available for NSN users via Network Operations

Portal (intranet).

Bulletin link: http://nea.ntc.nokia.com/cgi-bin/bulletins

NOTE:

This document is not delivered directly to customers. Customer copies need a

price tag that needs to be agreed with BSS GSM Performance Working Group.

http://nea.ntc.nokia.com/cgi-bin/bulletins




Summary

• BSS S10 CS Counters & Formulas

• BSS S10 New CS Counters & Formulas

• BSS S10.5&S11&S11.5&12 new CS Counters & Formulas


BSS S10

CS Counters & Formulas


KEY PERFORMANCE INDICATORS (KPI)

OPERATOR’S

USER

GROUPS

MANAGEMENT

Author: J.Neva 11/96

Version: 1.0

MARKETING

PLANNING

O&M

CUSTOMER CARE

PI=Performance Indicator

(counter, formulae,

figure from MML output)

PI

zz

KPI

a

PI

a

PI b

PI c

KPI

b

KPI

xx

.

.

.

.

.

.

PI KPI REPORTS

DISTRIBUTION

GENERATION

WORK PROCESS

KNOW - HOW TOOLS

KNOW - HOW

FORMULAE

KNOW - HOW

Users finally decide what are

KPI when they define the contents

of the report

PERFORMANCE STATISTICS SERVICE OF NSN CUSTOMER SERVICES

.

.

.

.

.

.


Availability (->S9)

TCH availability %, S4 (ava_1a)

sum(ave_avail_full_TCH/res_av_denom2)

100 * ------------------------------------------------------------ %

sum(ave_avail_full_TCH/res_av_denom2)+sum(ave_non_avail_TCH)

(p_nbsc_res_avail)

Known problems:

If TRXs are locked and BTSs and BCFs are unlocked, the TCHs appear as unavailable.

=> technical / operational unavailability can not be separated

SDCCH availability %, S4 (ava_4)

sum(ave_sdcch_sub/res_av_denom3)

100 * --------------------------------------------------------- %

sum(ave_sdcch_sub/res_av_denom3)+sum(ave_non_avail_sdcch)

(p_nbsc_res_avail)

Known problems: Affected by locked TRX under unlocked BCF and BTS.

Non avail.

Avail.

Information available on BTS level.

Note: Downtime of BTS can be counted from alarm ‘7767 BCCH MISSING’.

NOTE: Includes FR and dual time slots (not pure HR time slots)

http://nea.ntc.nokia.com/formula.php?ne=BSC&formula_id=uav_14ava_1a

http://nea.ntc.nokia.com/counter.php?ne=BSC&counter_id=002002


http://nea.ntc.nokia.com/formula.php?ne=BSC&formula_id=uav_14ava_4





TCH capacity, extended TRXs considered (S9->)

Author: J.Neva 3/02

Version: 1.1 2.4.2004

PMWG approval:

Unavail.TCH tsl extended

TCH on extended TRXs (CS only)

TCH on normal TRXs (CS only)

PS dedicated territory ava_17a

Dual ava_33

HR ava_31

FR ava_35

ava_28

PS

terr

ito

ry

av

a_16a

Max.c

ap

acti

y f

or

CS

tra

ffic

on

no

rmal T

RX

s

Av

a_21a

Unavail.TCH tsl normal

uav_14

Dual ava_34

HR ava_30

FR ava_32

PS default, dynamic part

(CS traffic can downgrade) ava_26a

Extended TRXs

Normal TRXs

GPRS territory can be

established on TSLs that

are of type FCTH or DTCH. TSLs

are taken to GPRS

territory in order from the end of

TRX.

ava_29

uav_13








http://nea.ntc.nokia.com/formula.php?ne=BSC&formula_id=uav_14uav_14






http://nea.ntc.nokia.com/formula.php?ne=BSC&formula_id=uav_14uav_13


TCH capacity, no extended TRXs (S9->) Author: J.Neva 10/01

Version: 1.1 4.4.02

PMWG approval: 1.0 11.10.01

Dual

Avail. TCH tsl (CS)

ave_avail_TCH_sum/ave_avail_TCH_den

Avail. FTCH + dual tsls (ava_2)

ave_avail_full_TCH/res_av_denom2

Avail. HTCH + dual tlsl

ave_tch_avail_half/2

Avail tsl for PS territory

ave_GPRS_channels_sum/

ave_GPRS_channels_den

ave_avail_full_TCH/res_av_denom2 + ave_tch_avail_half/2 ; HR+FR+2*dual tsls

-ave_avail_TCH_sum/ave_avail_TCH_den ; all

Dedic tsl

for PS

FTCH HTCH

ava_22 ava_23 ava_24

Default PS

(default+addit.)

ava_26 ava_17

GPRS territory can be established on TSLs that

are of type FCTH or DTCH. TSLs are taken to GPRS

territory in order from the end of TRX.

ave_non_avail_TCH

Unavail. TCH tsl


-ave_avail_full_TCH/res_av_denom2


– ave_tch_avail_half/2

Note: the formulae shown work if

- info presented on BTS/trx_type level or

- there are no extended TRXs



Availability (S9->) Author: J.Neva 8/00

Version: 1.0

PMWG approval.: 1.0: 21.11.2000

TCH availability %, S9 (ava_1d)

sum(ave_avail_TCH_sum/ave_avail_TCH_den

+ ave_GPRS_channels_sum/ave_GPRS_channels_den)

100 * ------------------------------------------------------- %

sum(ave_avail_TCH_sum/ave_avail_TCH_den)

+ ave_GPRS_channels_sum/ave_GPRS_channels_den

+ ave_non_avail_TCH)

(p_nbsc_res_avail)

Known problems:

If TRXs are locked and BTSs and BCFs are unlocked, the TCHs appear as unavailable. => technical / operational unavailability can not be separated.

SDCCH availability %, S4 (ava_4)

sum(ave_sdcch_sub/res_av_denom3)

100 * --------------------------------------------------------- %

sum(ave_sdcch_sub/res_av_denom3 + ave_non_avail_sdcch)

(p_nbsc_res_avail)

Known problems: Affected by locked TRX under unlocked BCF and BTS.

Non avail.

Avail. TCH

Avail. GPRS

Information available on BTS level.


http://nea.ntc.nokia.com/formula.php?ne=BSC&formula_id=uav_14ava_1d




Random Access

Nbr of RACH slots

ave_rach_slot/res_acc_denom1

Peak RACH load

c3010

peak_rach_load

Average RACH busy

ave_rach_busy/res_acc_denom3

RACH slot is counted as busy when level is

above -100dBm estimated at the RACH slot

Capacity

Load

BTS TRX

RACH

RACH has to pass

- S/N test (pattern)

- parity test

BSC

RACH accesses

c3016

ave_rach_access


Version: 1.6 20.122002

PMWG approval.: 1.5 29.3.2000

Average value over the whole

measurement period

Higest value of

ave_rach_busy

during the meas. period

BTS sw B9.0 and DF2.0 has enhanced filtering of

ghosts

- energy level check with previous burst info

- All 41 bits of training sequence used

GHOSTS

= SDCCH seizures that do not lead to a useful benefit

- thermodynamical type of noise

- in band noise from network or environment

- MS at the limit of sensitivity

GHOSTS

or

MS

If DL signal

strenght is

weaker than

'rxlev access

min' the MS

does not camp

on the cell.

CCCH

LOAD

IND (every 28s)

After B9 around

1 ghosts per hour

to BSC

Max Number Retransmission (RET) (1,2,4,7)

defines nbr of repetition by MS

Rach_3 Rach_4 *) T3126

*) T3126: In GSM Ph.1 waiting period is not defined (e.g. a Nokia MS has 800ms) but in GSM ph.2 it is defined by algoritm (deterministic part + random part

Number_of_slots_spread_trans) and can be as long as 5 sec. GSM 44.018 says: This timer is started either after sending the maximum allowed number of CHANNEL REQUEST messages during an

immediate assignment procedure or on receipt of an IMMEDIATE ASSIGNMENT REJECT message,whichever occurs first.

It is stopped at receipt of an IMMEDIATE ASSIGNMENT message, or an IMMEDIATE ASSIGNMENT EXTENDED message.

At its expiry, the immediate assignment procedure is aborted.

Immediate Assignment

Number of Slots Spread Trans (SLO)

(3..12, 14, 16, 20, 25, 32, 50 TDMA frames between retransmissions)

MML default 10.

In BTS sw B12 and DF5 the filtering of

accesses with illegal establishment causes will be

moved to BTS

Known phenomenom:

Handover Access bursts causing SDCCH failures, blocking and Ghosts

Channel Required

NOTE: triggered related to level

based RACH detection

(not what is accepted as RACH and

passed as Channel Req)

If RACH passed

all tests

NOTE: triggered related to what is

accepted as RACH





http://nea.ntc.nokia.com/cgi-bin/cgiwrap/neva/params?103

http://nea.ntc.nokia.com/formula.php?ne=BSC&formula_id=uav_14rach_3




http://wwwmsg.ntc.nokia.com/ni/studies/studies.htm


Ghosts Author: J.Neva 12/96

Version: 1.0 5.12.96

Level

White noise

1,095067 1,275611 2,004598 1,725887 1,708461 2,095688 2,41289

1,095067 1,275611 2,004598 1,725887 1,708461 2,095688 2,41289

1,752299 1,095067 1,191375 1,82131 1,305585 1,306742 1,593095

0 1 2 3 4 5 6

0

1

2

3

4

5

6

7

8

9

1 5 9 13 17 21 25 29 33 37 41 45 49 53 57 61

In-band

Disturbances

Real Mobiles

White Noise


Access Grant capacity (S8->)

AG BLOCKING (blck_13)

sum(del_ind_msg_rec)

100 * ----------------------------------------------------%

sum(imm_assgn_rej+imm_assgn_sent)

table = p_nbsc_res_acc

BSC

c3005

del_ind_msg_rec

How many times Immediate Assignment or

Immediate Assignment Reject have been

lost due to AG buffer overflow.

MS needs to send a new Channel Request.


Version: 1.2 1/2000

PMWG approval.:1.1 11.2.98

c3001

imm_assgn_sent

c3002

imm_assgn_rej

One message can include 1 - 4


Reject -Messages

(from S6) !

Immediate

Assignment

Immediate

Assignment

Rejected

OR

MS BTS

Overflow of

AG buffer

Parameters:

AG = = Number of Blocks Reserved for Access Grant

(0..7 if combined BCCH not used , 0..2 if combined BCCH used , 1..7 if CBCH used in SDCCH/8)

NOTE:

If AG=0, Access Grant has priority over Paging

If AG<>0, Paging has priority on PCH

If AG<>0, only Access Grant is sent on AG blocks

Buffer capacity =

8 Abis messages

T3101 starts

(active until establish_ind)

Immediate Assignment Rejected

Delete indication

OR

Sent on AGCH or

alternatively on PCH

if there is free capacity

Returned for each deleted AGCH message

MS is not allowed to

attempt new RR-

Establishment i.e

channel request

until T3122 expires

(T3122 gets value

from BSC)

Channel

Request

(RACH) Channel Required

Channel Activation

Channel Activation Ack

RACH on CCCH

/c3004

ch_req_msg_rec

/c1007

sdcch_assign

Ghosts having valid establishment

cause get through even if cell was

barred.

OR Channel Activation Nack

e.g. SCCH blocking

SDCCH normally released with clear

code 500341

/c1000

sdcch_seiz_att

CCCH overload

c1155

sdcch_unsucc_i

mm_assign_att

Note: if cell is barred the MS should not

make ch.requests.

http://nea.ntc.nokia.com/formula.php?ne=BSC&formula_id=uav_14blck_13





http://essrv509ntc.ntc.nokia.com:6336/dynaweb/NED31_bsc_s7e/8070271/@Generic__BookView;pt=27101?DwebQuery=T3122



http://essrv509ntc.ntc.nokia.com:6336/dynaweb/NED31_bsc_s8e/9090313/@Generic__BookView;pt=27101?DwebQuery=T9103






SDCCH requests

SDCCH REQUESTS

/c1000

sdcch_seiz_att

IMM.ASSIGNMENTS

FOR CALLS,LU,SS,

IMSI DETACH

/c1007

sdcch_assign

BLOCKED

/blck_15

sdcch_busy_att -

tch_seiz_due_sdcch_

con

RACH on CCCH

/c3004

ch_req_msg_rec

REJECTED DUE

TO ILLEGAL

EST.CAUSE (3/8 of

ghosts in ph.1´)

/c3030

ghost_ccch_res

5/8 OF GHOSTS (ph.1) AND

OTHER FAILURES BEFORE

ESTABL. IND.:

/SD_1a

c1007- TRF_25a

/c3013 succ_seiz_orig

/c3012 succ_seiz_term

CALL RE-EST.

/c3020

sdcch_call_re_est

LOCATION UPDATE

/c3019

sdcch_loc_upd

EMERGENCY CALL

/c3021

sdcch_emerg_call

SDCCH ACCESSES REJECTED IN BSC

TRUE SDCCH SEIZURES

/TRF_25a (not updated in SDCCH HO)

SEIZURES FOR HO

/c1006

sdcch_ho_seiz

SDCCH FAILURES

/c1075

sdcch_abis_fail_call (blocked channel,

Corrupted msgs,

failed chan.act.)

Author: J.Neva 5/96

Version: 1.7 18.2.2002

PMWG approval.: v 1.7 18.2.2002

TRUE SDCCH SEIZURES FOR CALL,SMS, SS

/TRF-27

IMSI DETACH

/c3033 (S7)

imsi_detach_sdcch

TRUE SDCCH SEIZURES

FOR CALL /TRF-91

TRF-27

- succ_sdcch_sms_est

-unsucc _sdcch_sms_est

-succ_seiz_supplem_serv

TRUE SDCCH SEIZURES

FOR SMS

Sms_5

succ_sdcch_sms_est

+ unsucc_sdcch_sms_est SDCCH BLOCKING (blck_5a)

SDCCH-

SDCCH HO

other than

sdcch_abis_* failures

small part of failures

Normal LU

Periodic LU

IMSI attach

MS accessing,

noise (ghosts)

NOTE:

Triggered also in case of

HO attempt if there are no

free SDCCH

SDCCH-

SDCCH

HO

TCH

FACCH call setups

/c1099

tch_seiz_due_sdcch_

con

Distance checking

BSS5280 (S5)

REJECTED DUE TO

DISTANCE

/c3031 (S5)

rej_seiz_att_due_dist

SDCCH FAILURES

/c57020 (S7)

t3101_expired

(Ghosts)

CALL RE-EST. ASSGN.

/c57022 (S7)

sdcch_re_est_assign SUPPLEMENTARY SERVICE REQUEST

/c3044 (S9) succ_seiz_supplem_serv

T3101 adjustable by MML ZEGT:T3101..

BCSU Lower Limit =

34 unhandled reqs

/c3039 (S7)

bcsu_overload_lower_li

mit

BCSU Upper Limit =

53 unhandled reqs

/c3040 (S7)

bcsu_overload_upper_li

mit

Limit per CCCH =

20 req.per BTS (CCCH)

/c3041 (S7)

bcsu_overload_deleted_ra

ch

Call_assign_after_sms

/c3059 ( S10.5)

ND report 134

MOC SMS LS SS

MTC SMS

TRUE SDCCH SEIZURES

FOR MO SMS

/c3065 + /c30649

unsucc_mo_sms_sdcch +

succ_mo_sms_sdcch






http://nea.ntc.nokia.com/formula.php?ne=BSC&formula_id=uav_14sd_1a






http://nea.ntc.nokia.com/formula.php?ne=BSC&formula_id=uav_14trf_25a



http://nea.ntc.nokia.com/formula.php?ne=BSC&formula_id=uav_14trf_27







http://nea.ntc.nokia.com/formula.php?ne=BSC&formula_id=uav_14sms_5

http://nea.ntc.nokia.com/formula.php?ne=BSC&formula_id=uav_14blck_5a






http://essrv509ntc.ntc.nokia.com:6336/dynaweb/NED31_bsc_s8e/9090313/@Generic__BookView;pt=27101?DwebQuery=t3101




http://nea.ntc.nokia.com/cgi-bin/cgiwrap/neva/counter_list_bsc.pl?counter_id=3059

http://nea.ntc.nokia.com/cgi-bin/cgiwrap/neva/model_by_id?134




FACCH call setup (S9)

RACH on CCCH

/c3004

ch_req_msg_rec

MOC

(incl. SMS,SS)

/c3024

tch_moc

MTC

/c3023

tch_mtc

CALL RE-EST.

/c3025

tch_call_re_est

EMERGENCY CALL

/c3022

tch_emerg_call

TCH FAILURES

/c1084

tch_abis_fail_call

Author: J.Neva 1/97

Version: 1.6 1.6.01

PMWG review.: 1.5 27.3.01

TCH SEIZURES FOR FACCH CALL SETUP

MS accessing,

noise (ghosts)

TCH REQUESTS

/C1010 tch_request

SDCCH REQUESTS

/C1000 sdcch_seiz_att

BLOCKED

/C1001 sdcch_busy_att

TCH REQ FOR FCS

/C1043 tch_fast_req (S2)

TCH SEIZ ATT DUE TO SDCCH CONGEST

/C1098

tch_seiz_att_due_sdcch_con (S5)

FTCH REQ, FCS

/C1123 tch_full_req_fast_call

TCH REQ, FCS, RATE UNDEF.

/C1124 tch_fast_call_ch_rate_not_det

OR

TCH SUCC REQ FOR FCS

/C1044 tch_fast_seiz (S2)

TCH SUCC SEIZ ATT DUE TO SDCCH

CONGEST

/C1099 tch_seiz_due_sdcch_con (S5)

FTCH SUCC SEIZ FOR FCS

/C1125 tch_succ_full_seiz_fast_call

HTCH SUCC SEIZ . FOR FCS,

RATE UNDEF.

/C1126 tch_succ_half_seiz_fast_call

OR

SDCCH ACCESSES REJECTED IN BSC

IMSI DETACH TCH

/c3034 (S7)

imsi_detach_sdcch

NOTE:

Older MS types do not trigger this counter

CALL RE-EST. ASSGN

/c57032 (S7)

tch_re_est_assign

TCH FAILURES

/c57038 (S9)

tch_t3101_expired (Ghosts)

SUPPLEMETARY SERVICE

REQUEST

/c3045 (S9)

tch_supplem_serv

AND

AND

T3101 adjustable by MML ZEGT:T3101..

REJECTED DUE

TO ILLEGAL

EST.CAUSE (3/8

of ghosts in ph.1´)

/c3030

ghost_ccch_res

5/8 OF GHOSTS (ph.1)

AND OTHER FAILURES

BEFORE ESTABL. IND.

(incl.IMSI detach):

/SD_1a

c1007- TRF_25a

Distance checking

BSS5280 (S5)

REJECTED DUE TO

DISTANCE

/c3031 (S5)

rej_seiz_att_due_dist

BCSU Lower Limit =

34 unhandled reqs

/c3039 (S7)

bcsu_overload_lower_

limit

BCSU Upper Limit =

53 unhandled reqs

/c3040 (S7)

bcsu_overload_upper

_limit

Limit per CCCH =

20 req.per BTS (CCCH)

/c3041 (S7)

bcsu_overload_deleted

_rach

In FACHH call

setup signaling

uses TCH instead

SDCCH. When

signaling is over,

call uses the same

TCH.






















http://essrv509ntc.ntc.nokia.com:6336/dynaweb/NED31_bsc_s8e/9090313/@Generic__BookView;pt=27101?DwebQuery=t3101


TCH requests, call (S8->)

TCH REQUESTS

/C1010

tch_request

TCH

REQUESTS

FOR NEW

CALL (incl. Re-

establ.)

/trf_18a

tch_call_req

- trf_49

TCH SEIZURES FOR NORMAL NEW CALL

/trf_55

tch_norm_seiz-tch_succ_seiz_for_dir_acc

DR OUT SUCC

/dr_3

msc_o_sdcch_tch+bsc_o_sdcch_tch

BLOCKED CALLS

/blck_9d

tch_call_req-trf_49-trf_55a -dr_3-dr_5 TCH REQUESTS

FOR HO

/ho_14b

tch_request

-tch_call_req

-tch_fast_req

-trf_50

TCH CALL BLOCKING (blck_8d)

= 100*blck_9c/(c1026-trf_49) %

TCH

REQUESTS

FOR

FCS

/c1043

tch_fast_req

Author: J.Neva 5/96

Version: 2.6 22.5.2003 J.Neva


DR intra SUCC (IUO opt.feature)

/dr_5

cell_sdcch_tch

TO QUEUE

/c1016

tch_qd_call_att

UNSERVED QUEUED CALL REQ (timer expiry or higher priority queuer)

/c1024

unsrv_qd_call_att

MS MOVED TO TCH

/c1148 (S7)

ms_tch_succ_seiz_assign_cmplt

NOTE: If Trunk Reservation is

used then HO and Call blocking

can not be counted precisely

(there is only one counter for

Trunk Res. Invocation Refused

case)

CALL RETRIES DUE TO AIF POOL MISMATCH

/ trf_49

tch_rej_due_req_ch_a_if_crc

- (bsc_i_unsucc_a_int_circ_type+msc_controlled_in_ho+ho_unsucc_a_int_circ_type)

REMOVAL FROM Q TO DR

removal_from_que_to_dr 1173 (S8)

Ref. TCH CONGESTION TIME

cngt_1

See bulletin75 bulletin78

Note: the nbr of retries depends

on MSC. Nokia MSC makes

only one retry.

TCH RE-EST ASSIGN

c57032 (S7)

tch_re_est_assign

TCH NEW CALL ASSIGN

c57033 (S7)

tch_new_call_assign

or

TCH CALL BLOCKING

/ blck_8i (S12)

100 *(sum(tch_requests_call_attempt -

succ_tch_seiz_call_attempt)/

sum(tch_requests_call_attempt)






http://nea.ntc.nokia.com/formula.php?ne=BSC&formula_id=uav_14dr_3

http://nea.ntc.nokia.com/formula.php?ne=BSC&formula_id=uav_14blck_9d

http://nea.ntc.nokia.com/formula.php?ne=BSC&formula_id=uav_14ho_14b


http://nea.ntc.nokia.com/formula.php?ne=BSC&formula_id=uav_14blck_8d








http://nea.ntc.nokia.com/formula.php?ne=BSC&formula_id=uav_14cngt_1

http://nea.ntc.nokia.com/~neva/SE_bulletins/bullet075.txt

http://nea.ntc.nokia.com/~neva/SE_bulletins/bullet078.txt




TCH requests, HO and FCS (S6->)

TCH REQUESTS

/C1010

tch_request

TCH

REQUESTS

FOR NEW

CALL

/c1026

tch_call_req

TCH SEIZURES FOR

HO (incl. DR in)

/c1008

tch_ho_seiz

BLOCKED HO’S

/blck_10b

ho_14b- tch_ho_seiz

TCH HO BLOCKING (blck_11c)

= 100*blck_10b/ho_14b %

TCH

REQUESTS

FOR

FCS

/c1043

tch_fast_req

SUCC. QUEUED TCH HO REQ

/que_5

tch_qd_ho_att - unsrv_qd_ho_att

SUCC. NONQUEUED TCH HO REQ

/que_6

tch_ho_seiz - que_5

NOTE: If Trunk Reservation is

used then HO and Call blocking

can not be counted precisely

(there is only one counter for

Trunk Res. Invocation Refused

case)

TCH REQUESTS

FOR HO

/ho_14b

tch_request

-tch_call_req

-tch_fast_req

-trf_50

Author: J.Neva 5/96



HO RETRIES DUE TO AIF POOL MISMATCH

/ trf_50

bsc_i_unsucc_a_int_circ_type+msc_controlled_in_ho

+ho_unsucc_a_int_circ_type

TCH FCS SEIZURE

ATTEMPTS

/c1098 (S5)

tch_seiz_att_due_sdcch_con

TCH FCS SEIZURES

/c1099 (S5)

tch_seiz_due_sdcch_con

BLOCKED TCH FCS SEIZURES

/blck_18

tch_seiz_att_due_sdcch_con

-tch_seiz_due_sdcch_con

TCH

REQUESTS

FOR NEW

CALL

/trf_18a

tch_call_req

- trf_49

Note: the nbr of retries

depends on MSC. Nokia MSC

makes only one retry.

TCH RE-EST ASSIGN

c57032 (S7)

tch_re_est_assign

TCH NEW CALL ASSIGN

c57033 (S7)

tch_new_call_assign

or



http://nea.ntc.nokia.com/formula.php?ne=BSC&formula_id=uav_14blck_10b

http://nea.ntc.nokia.com/formula.php?ne=BSC&formula_id=uav_14blck_11c


http://nea.ntc.nokia.com/formula.php?ne=BSC&formula_id=uav_14que_5

http://nea.ntc.nokia.com/formula.php?ne=BSC&formula_id=uav_14que_6







http://nea.ntc.nokia.com/formula.php?ne=BSC&formula_id=uav_14blsck_18






Queueing 1/: example 1TRX, combined CCH, DR active

Signalling on SDCCH

In Queue on SDCCH of this cell

On TCH, or accessing TCH

Maximum Length Of Queue

MQL = Max Queue Length

parameter, ZEQH

DEF 50%, for 1 TRX

=> 4 places in queue

DR

In Queue for HO, the MS Is on TCH of another cell

Order in the queue:

1) by default, HO candidates served

first (QPC > QPH, QPC > QPN,

smaller priority served first,

parameters ZEQH)

2) mobiles are ordered by mobile

priority, if no difference in priority,

first come first served

No free SDCCH, counter 1001 sdcch_busy_att

updated (had there been free TCH's, FACCH

call setup or dynamic SDCCH allocation could

have been attempted)

1

2

4

3

4

4 4 4 4 4 4 4

2 2 3 3

Author: M.Räsänen 6/98


PMWG approval.:18.9.98

Call queuing on SDCCH

On TCH

MS

4 logical places in queue

Call queuing on SDCCH

HO queuing

HO queuing

MS MS MS MS MS MS

MS

MS

4 SDCCH slots

MS

MS

In this example the TCHs are

all seized,queue is full (2 calls.

2 Hos) and SDCCH is full.

Accordingly all new call attempts

get rejected on SDCCH because

SDCCH is full.

MS

MS

7 TCH

NOTE: SDCCH resources

are used by queuing

Time limit handover (TLH)

DEF 5 seconds (max: 10sec)

MS

MS







Queueing 2/2: timers and counters example: queueing and DR activated, (direct access IUO,S7 not included)

Min time limit

directed retry

(MIDR)

DEF 0 seconds Expiry -> MS removed from the queue

Expiry -> MS removed from the queue

If TLC < MADR, and TLC expires, MS is removed from call queue but DR may still happen

1010 tch_request

1016 tch_qd_call_att

1010 tch_request

1008 tch_ho_seiz

1026 tch_call_req

Successful DR, target Successful DR, source

DR

Time limit call (TLC)

DEF 10 seconds (max: 15sec)

Max time limit directed retry

(MADR)

DEF 5 seconds

1056 que_all_ass_req

1173 rem_from_queue_due_dr

(S8 new counter ):

MS removed from queue because of

DR

1020 ave_que_time_call_att

/ 1021 queue_denom2

shows the average call setup

queueing time

1060 que_all_ass_req_fail

1011 tch_req_rej_lack

1024 unsrv_qd_call_att

4065 bsc_o_sdcch_tch

4057 bsc_i_sdcch_tch

4050 msc_o_sdcch_tch

4044 msc_i_sdcch_tch

1003 sdcch_radio_fail

1013 tch_radio_fail

1084 tch_abis_fail_call

or

or

Normal

Assignment

4053 msc_o_sdcch_tch_at

4068 bsc_o_sdcch_tch_at

DR attempt, source

4060 bsc_i_sdcch_tch_at

4047 msc_i_sdcch_tch_at

DR attempt, target

or

or

1009 tch_norm_seiz

Assignment Attempt

1 2

4

4

Author: M.Räsänen 6/98

Version: 1.0


Signalling on SDCCH

Queuing on SDCCH

TCH

TCH of other cell

Failed DR, source

X

X

X

X

X Call attempt lost and

MS goes to idle state

1148 ms_tch_succ_seiz_assign_cmplt (S7)











SDCCH call request and SDCCH HO (S9->)

SDCCH

REQUESTS

/c1000

sdcch_seiz_at

t

SEIZURES FOR

CALLS , LU s AND

IMSI DETACHES

/c1007

sdcch_assign

MTC (incl.SMS)

/c3012

succ_seiz_term

EMERG CALL

/c3021

sdcch_emerg_call

SEIZURES FOR HO

/c1006

sdcch_ho_seiz

Author: J.Neva 1/97

Version: 1.3 31.8.00

PMWG appr.: 1.3 21.11.00

SDCCH - SDCCH

INTER CELL HO

TO CELL B

Cell A (source)

Cell B (target)

SDCCH REQUESTS

/c1000

sdcch_seiz_att

one of SDCCH HO attempt

counters triggered

bsc_i_sdcch_at /c4061

or

msc_i_sdcch_at /c4048

one of SDCCH HO success

counters triggered

bsc_i_sdcch /c4058

or

msc_i_sdcch /c4045

TCH

==> SDCCH HO have to be compensated when counting SDCCH success ratio (CSF_2x) for a cell

One of these triggered

CALL RE-EST

/c3020

sdcch_call_re_est

IMSI DETACH (S7)

/c3033

imsi_detach_sdcch

LOC UPDATE

/c3019

sdcch_loc_upd

Intra cell SDCCH to SDCCH HO

attempt counter

cell_sdcch_at

/c4078

success counter

cell_sdcch

/c4075

one of SDCCH HO

attempt counters

triggered

bsc_o_sdcch_at

/c4069 or

msc_o_sdcch_at

/c4054

one of SDCCH HO

success counters

triggered

bsc_o_sdcch /c4066

or

msc_o_sdcch /c4051

Inter cell SDCCH to SDCCH HO

SUPPLEM. SERVICE REQUEST

/c3044 (S9)

succ_seiz_supplem_serv

MOC (incl.SMS,SS)

/c3013

succ_seiz_orig
























Drop on SDCCH and call re-establishment

SDCCH REQUESTS

/c1000

sdcch_seiz_att

SEIZURES FOR

CALLS AND LU

/c1007

sdcch_assign

MOC (incl.SMS)

/c3013

succ_seiz_orig

MTC (incl.SMS)

/c3012

succ_seiz_term

EMERGENCY CALL

/c3021

sdcch_emerg_call

Author: J.Neva 1/97



Cell A

one of SDCCH fail counters is triggered

SDCCH_RADIO_FAIL /c1003 or

SDCCH_USER_ACT /c1037 or

SDCCH_BCSU_RESET /c1038 or

SDCCH_NETW_ACT /c1039 or

SDCCH_BTS_FAIL /c1036 or

SDCCH_LAPD_FAIL /c1035 or

SDCCH_A_IF_FAIL_CALL /c1078 or

SDCCH_ABIS_FAIL_CALL /c1075


Call drops

SDCCH

REQUESTS

/c1000

sdcch_seiz_att

SEIZURES FOR

CALLS AND LU

/c1007

sdcch_assign

Cell A or X

TCH

CALL RE-EST.

/c3020

sdcch_call_re_est

Ghost rach accesses

or double seizures

NOTE ! Call re-establishment can be executed more than once.

RE-EST. ASSGN.

/c57022 (S7)

sdcch_re_est_assign

or in case of SDCCH congestion,

FACCH call setup is made, look at

FACCH call setup picture

RE-EST. ASSGN ON TCH

/c57032 (S7)

tch_re_est_assign

RE-EST. RELEASE

/c57026 (S7)

sdcch_re_est_release

RE-EST. RELEASE ON TCH

/c57037 (S7)

tch_re_est_release

See also: experiences

NOTE: Failed re-established calls are counted by

clear code 208H of Nokia MSC.

-can be initiated by MS for all kinds of radio link failures (e.g. SACCH count down, T200-N200 expiry and HO failure)

- proactive, MS tries to re-connect the call rather than wait and then die Call re-establishment

Tried on the best cell of

latest neighbor list or

latest serving cell.





















//NCSMSG24TR/HTDOCS/CSTRE/NOS/SE/DOCS/Jne696.doc

http://wwwmsg.ntc.nokia.com/ni/cc_www/cc_m9/0208.htm


Drop on TCH and call re-establishment

SDCCH REQUESTS

/c1000

sdcch_seiz_att

SEIZURES FOR

CALLS AND LU

/c1007

sdcch_assign

MOC (incl.SMS)

/c3013

succ_seiz_orig

MTC (incl.SMS)

/c3012

succ_seiz_term

EMERGENCY CALL

/c3021

sdcch_emerg_call

Author: J.Neva 1/97



Cell A


TCH REQUESTS

/c1010

tch_request

TCH REQUESTS

FOR NEW CALL

/c1026

tch_call_req

TCH SEIZURES FOR

NEW CALL

/c1009

tch_norm_seiz

Call drops

one of TCH fail counters is triggered TCH_RADIO_FAIL /c1013 or

TCH_USER_ACT /c1048 or

TCH_BCSU_RESET /c1049 or

TCH_NETW_ACT /c1050 or

TCH_BTS_FAIL /c1047 or

TCH_LAPD_FAIL /c1046 or

TCH_A_IF_FAIL_CALL /c1087 or

TCH_ABIS_FAIL_CALL /c1084 or

TCH_TR_FAIL /c1029 or

TCH_ACT_FAIL_CALL /c1081

NOTE ! Call re-establishment can be executed more than once.

SDCCH

REQUESTS

/c1000

sdcch_seiz_att

SEIZURES FOR

CALLS AND LU

/c1007

sdcch_assign

Cell A or X

TCH

CALL RE-EST.

/c3020

sdcch_call_re_est

RE-EST. ASSGN.

/c57022 (S7)

sdcch_re_est_assign

RE-EST. RELEASE

/c57026 (S7)

sdcch_re_est_release

or in case of SDCCH congestion,

FACCH call setup is made

See also: experiences

NOTE: Failed re-established calls are counted by

clear code 208H of Nokia MSC.

Call re-establishment

-can be initiated by MS for all kinds of radio link failures (e.g. SACCH count down, T200-N200 expiry and HO failure)

- proactive, MS tries to re-connect the call rather than wait and then die

Tried on the best cell of

latest neighbor list or

latest serving cell.

RE-EST. ASSGN ON TCH

/c57032 (S7)

tch_re_est_assign

RE-EST. RELEASE ON TCH

/c57037 (S7)

tch_re_est_release

The charging mechanism is stopped during a stopped or interrupted call and is resumed after

the successful re-establishment of the call.















http://wwwmsg.ntc.nokia.com/ni/cc_www/cc_m9/0208.htm




Drop Call ratio problematic

BSC 1 BSC 2

SDCCH

TCH #2

SDCCH

TCH #1

TCH #2

TCH #3

Drop call

and

MSC 2

TCH_RADIO_FAIL

TCH_RF_OLD_HO

TCH_ABIS_FAIL_CALL

TCH_ABIS_FAIL_OLD

TCH_A_IF_FAIL_CALL

TCH_A_IF_FAIL_OLD

TCH_TR_FAIL

TCH_TR_FAIL_OLD

TCH_LAPD_FAIL

TCH_BTS_FAIL

TCH_BCSU_RESET

TCH_USER_ACT

TCH_NETW_ACT

TCH_ACT_FAIL_CALL

TCH_NORM_SEIZ

CONVER_STARTEDTCH_NORM_SEIZ

CONVER_STARTED

DROPPED_CALL

Silence and then

busy tone after time-out

MS

A

MS

B

SUCC_SEIZ_ORIG

SUCC_SEIZ_TERM

(P_MSC_CC)

CLEAR_CODE_ID/CALLS_IN_SPEECH


Instead of Drop Call ratio it

is also possible

to talk about Drops per Erlang ratio.

TCH_HO_SEIZ

TCH_HO_SEIZ

TCH_HO_SEIZ

DOCUMENTTYPE 1 (1)

TypeUnitOrDepartmentHereTypeYourNameHere TypeDateHere

208,609,60E,610,70A,B13,B14,B16,B1B,B1C,D00,D01,D02,D03,D04,D06,D07,D08

Eg.clear codes:

Author: J.Neva 9/98

Version: 1.0 20.9.98

PMWG review.: 1.0 12.10.98

MSC 1

41 'Temp. failure'

(P_MSC_CC)

CLEAR_CODE_ID/CALLS_IN_SPEECH

BSC1:

normal clear

B13

See experiences.

TCH_NEW_CALL_ASSIGN

TCH_NEW_CALL_ASSIGN

TCH_HO_RELEASE TCH_HO_RELEASE

TCH_HO_RELEASE

TCH_NORMAL_RELEASE




TCH request and normal DR

TCH REQUESTS

/c1010

tch_request

TCH

REQUESTS

FOR NEW

CALL

/c1026

tch_call_req

TCH SEIZURES FOR

HO (incl. DR in)

/c1008

tch_ho_seiz

DR OUT SUCC

/DR_3

msc_o_sdcch_tch

/c4050 or

bsc_o_sdcch_tch

/c4065


Version: 1.3 12.10.00


Cell A (source)

TCH REQUESTS

/c1010

tch_request

Cell B (target)

DR IN ATT

/DR_2

msc_i_sdcch_tch_at

/c4047 or

bsc_i_sdcch_tch_at

/c4060

DR (SDCCH- TCH HO)

TO CELL B

TCH congestion

DR OUT ATT

/DR_1

msc_o_sdcch_tch_at

/c4053 or

bsc_o_sdcch_tch_at

/c4068

DR IN SUCC

/DR_4

msc_i_sdcch_tch

/c4044 or

bsc_i_sdcch_tch

/c4057

In case of normal DR

tch_norm_seiz (1009)

counter is not

triggered at all.

If normal DR fails,

sdcch_radio_fail_old

(1004)

is triggered.

TCH REQUESTS REJ DUE LACK

/c1011

tch_rej_lack

Or (if target cell congested) TCH NEW CALL ASSIGN

c57033 (S7)

tch_new_call_assign





















TCH REQUESTS

/c1010

tch_request

TCH

REQUESTS

FOR NEW

CALL

/c1026

tch_call_req

TCH SEIZURES FOR

HO (incl. DR in)

/c1008

tch_ho_seiz

Intra DR SUCC

/c4074

cell_sdcch_tch

Author: J.Pekkarinen 10/97



Cell A (source, regular TRX)

TCH REQUESTS

/c1010

tch_request

Cell A (target, super TRX)

DR (SDCCH-TCH HO)

TO SUPER TRX

TCH congestion

TCH request and Intra cell DR

DR ATT

/c4077

cell_sdcch_tch_at


/c1011

tch_req_rej_lack

If TCH congestion on super then request again on regular TRX.

If also regular TRX is congested then normal DR is attempted.

(FEATURE BSS6114: TCH assignment to super-reuse TRX in IUO, S6)

TCH congestion

TCH RE-EST ASSIGN

c57032 (S7)

tch_re_est_assign

TCH NEW CALL ASSIGN

c57033 (S7)

tch_new_call_assign or











TCH REQUESTS

/c1010

tch_request

TCH

REQUESTS

FOR NEW

CALL

/c1026

tch_call_req

TCH SEIZURES FOR

HO (incl. DR in)

/c1008

tch_ho_seiz

DR IN SUCC

/c4057

bsc_i_sdcch_tch





TCH REQUESTS

/c1010

tch_request

Cell B (target, super TRX)

DR (SDCCH-TCH HO)

TO SUPER TRX CELL B

TCH congestion

DR IN ATT

/c4060

bsc_i_sdcch_tch_at

TCH request and Inter cell DR

DR OUT SUCC

/c4065

bsc_o_sdcch_tch

DR OUT ATT

/c4068

bsc_o_sdcch_tch_at

(FEATURE BSS6114: TCH assignment to super-reuse TRX in IUO, S6)


/c1011

tch_rej_lack

If TCH congestion on super then request again on regular TRX.

If also regular TRX is congested then normal DR is attempted.

TCH RE-EST ASSIGN

c57032 (S7)

tch_re_est_assign

TCH NEW CALL ASSIGN

c57033 (S7)














Intra Dir Acc SUCC

/c4074

cell_sdcch_tch




TCH REQUESTS

/c1010

tch_request

Cell A (target, super TRX)

Direct Access Attempt

/c4077

cell_sdcch_tch_at

TCH request and intra cell DAC

(FEATURE BSS7057 : Direct access to super-reuse TRX, S7)

TCH SEIZURES FOR

NEW CALL

/c1009

tch_norm_seiz

TCH REQUESTS

FOR NEW CALL

/c1026

tch_call_req

DIR ACC TCH REQ REJ DUE LACK

/c1166

tch_req_dir_acc_rej_due_lack

TCH SEIZURES FOR

DIRECT ACCESS

/c1165 (S7)

tch_succ_seiz_for_dir_acc

Congestion

No Congestion

Direct Access

(SDCCH-TCH HO)

TO SUPER TRX



Normal TCH call request handling

Note:

In case of HO fails to super the tch_norm_seiz is triggered again.

This causes problem for the KPIs and a fix is planned in S10.

TCH RE-EST ASSIGN

c57032 (S7)

tch_re_est_assign

TCH NEW CALL ASSIGN

c57033 (S7)








http://nea.ntc.nokia.com/counter.php?ne=BSC&counter_id=003021http://nea.ntc.nokia.com/cgi-bin/cgiwrap/neva/counters?001165




Direct Access in success

/c4057

bsc_i_sdcch_tch


TCH REQUESTS

/c1010

tch_request

Cell B (target, super TRX)

Direct Access in att

/c4060

bsc_i_sdcch_tch_at

Direct Access OUT

SUCC /c4065

bsc_o_sdcch_tch

Direct Access OUT ATT

/c4068

bsc_o_sdcch_tch_at

TCH request and intercell DAC

TCH SEIZURES FOR

NEW CALL

/c1009

tch_norm_seiz

Direct Access

(SDCCH-TCH HO)

TO SUPER TRX

CELL B

(FEATURE BSS7057 : Direct access to super-reuse TRX, S7 )




TCH REQUESTS

FOR NEW CALL

/c1026

tch_call_req

Congestion



No Congestion

DIR ACC TCH REQ REJ DUE LACK

/c1166

tch_req_dir_acc_rej_due_lack

TCH SEIZURES FOR

DIRECT ACCESS

/c1165 (S7)

tch_succ_seiz_for_dir_acc

TCH RE-EST ASSIGN

c57032 (S7)

tch_re_est_assign

TCH NEW CALL ASSIGN

c57033 (S7)














BSC I SDCCH TCH

/c4057

bsc_i_sdcch_tch

Cell A (source,)

TCH REQUESTS

/c1010

tch_request

Cell B (target) BSC I SDCCH TCH AT

/c4060

bsc_i_sdcch_tch_at

BSC O SDCCH TCH

/c4065

bsc_o_sdcch_tch

HO ATTEMP DUE TO DADLB

/c4129

ho_att_due_to_dadlb

TCH request and inter cell DADLB

TCH SEIZURES FOR

HO

/c1008

tch_ho_seiz

DADLB

(SDCCH-TCH HO)

TO DESIRED LAYER/BAND

CELL B

(FEATURE BSS8032: Direct acess to desired layer/band, S8 )

Congestion

Cell A (source,)


No Congestion

DADLB TCH REQ REJ DUE LACK OF

RESOURCES

/c1171

tch_req_rej_dadlb_ho

TCH SEIZURES FOR

DADLB

/c1170 (S8)

tch_succ_seiz_dadlb_ho

Author: PMWG



Note:

HO to other

band requires

CM3 MS and

measurement

data

TCH REQUESTS

/c1010 tch_request

TCH REQUESTS

FOR NEW CALL

/c1026

tch_call_req

DADLB START DUE EXCEEDED

LOAD

/c1172

dadlb_start_due_exceed_load

BSC O SDCCH TCH AT

/c4068

bsc_o_sdcch_tch_at

INTER DADLB

/c51141

inter_dadlb

Note: 1) dadlb is only started when the load of the source cell is below 100%.

2) If the counter DADLB_start_due_exceeded_load is triggered but the counter ho_att_due_to_DADLB is

not then this means that there is not found any suitable ( = the signal level of the adjacent cell

exceeds HOLevelUmbrella) dadlb target cell in time between MinTimeLimitDR and MaxTimeLimitDR.

Ref. ND report 156

TCH RE-EST ASSIGN

c57032 (S7)

tch_re_est_assign

TCH NEW CALL ASSIGN

c57033 (S7)



















BSC initiated TRHO

(FEATURE BSS8123: Advanced multilayer handling, S8 )

Author: J.Kaasalainen

Version: 1.0 11.5.00


BSC I TCH TCH

/c4056

bsc_i_tch_tch

Cell A (source)

TCH REQUESTS

/c1010

tch_request

Cell B (target)

BSC I TCH TCH AT

/c4059

bsc_i_tch_tch_at

BSC O TCH TCH

/c4064

bsc_o_tch_tch

TCH SEIZURES FOR HO

/c1008

tch_ho_seiz

AMH TRHO

(TCH-TCH HO)

to CELL B

1) load < Amh Max Load Of Tgt Cell

TCH REQ REJ BSC TRHO DUE LACK

/c1169

tch_req_rej_bsc_trho_due_lack

TCH SUCC SEIZ BSC TRHO

/c1168

tch_succ_seiz_bsc_trho

HO ATT DUE TO BSC CONTR TRHO

/c4035

ho_att_due_to_bsc_contr_trho

BSC O TCH TCH AT

/c4067

bsc_o_tch_tch_at

BSC: load of BTSs is evaluated every 20s, if load > Amh Upper Load Treshold

then TRHO is started using Amh TRHO PBGT Margin

TCH REQ BSC TRHO

/c1167

tch_req_bsc_trho

TCH REQUESTS

/c1010

tch_request

2) Congestion: load 100%

TCH REQ BSC TRHO

/c1167

tch_req_bsc_trho

TCH REQ REJ BSC TRHO DUE LACK

/c1169

tch_req_rej_bsc_trho_due_lack

3) No congestion: 100%>load >= Amh Max Load Of Tgt Cell

TCH REQ REJ LACK

/c1011

tch_req_rej_lack

Clear Code PM

(MSC controlled source side)

(/c51145 ext_out_bsc_trho)

(MSC controlled target side)

(/c51078 ext_in_bsc_trho)

BSC controlled inter cell

/c51140 inter_bsc_trho

TCH REQ BSC TRHO

/c1167

tch_req_bsc_trho

2)

1)

3)

Call is first normally established

Ref. ND report 155




























Calls and drop calls on TCH, area view, S7


Version: 1.3 9.9.98

PMWG approval.: 1.3 15.9.99 Area (nn cells)

DR IN SUCC

/DR_4

msc_i_sdcch_tch

/c4044 or

bsc_i_sdcch_tch

/c4057

NEW CALLS

ON TCH NORMAL END

/c57035

tch_norm_release

TCH-TCH HO OUT

FROM AREA

(unknown)

TCH DROPS

TCH_RADIO_FAIL /c1013

+TCH_RF_OLD_HO /c1014

+TCH_ABIS_FAIL_CALL /c1084

+TCH_ABIS_FAIL_OLD /c1085

+TCH_A_IF_FAIL_CALL /c1087

+TCH_A_IF_FAIL_OLD /c1088

+TCH_TR_FAIL /c1029

+TCH_TR_FAIL_OLD /c1030

+TCH_LAPD_FAIL /c1046

+TCH_BTS_FAIL /c1047

+TCH_USER_ACT /c1048

+TCH_BCSU_RESET /c1049

+TCH_NETW_ACT /c1050

+TCH_ACT_FAIL_CALL /c1081

TCH SEIZURES FOR

NEW CALL

/trf_55

NOTE:

Drop call by pre-emption

- 1st priority call requested to be

established

- all TCH seized

- lower priority calls on

==>

p_nbsc-service.dropped_call is

triggered

(NOT TCH failure counters)

FACCH CALL SETUP

/c1099 (S5) / trf_53


DR INTRA SUCC

/c4074

cell_sdcch_tch
























Counting Erlangs (p_nbsc_res_avail) Author: J.Neva 10/98

Version: 1.0


Sampling

every 20sec (UTPFIL parameter)

Cumulative

sum

c2027

Nbr of

samples

c2028

BTS xx

TRX-nn

Counter values sent to NetAct and

stored once in

measurement period

BCCH TCH TCH TCH TCH TCH TCH Ave_busy_tch Res_av_denom14

seized seized -> 2 1 0 sec

seized seized seized seized -> 2+4 2 20 sec

seized -> 2+4+1 3 40 sec

-> … …

seized seized seized -> … +3 180 3580sec

The same principle is used in IUO measurement.

Counter 002027 AVE_BUSY_TCH counts reserved TCH channels.

S12 counter 002090 AVE_BUSY_TCH_TIMESLOT counts busy TCH

timeslots regardless of timeslot type (FR, HR or DR).




Counting avarage Erlangs per BTS (p_nbsc_res_avail) Author: J.Neva 03/2004

Version:

Average erlangs per BTS (OK if no SEG, no extended TRX) =

Sum(Ave_busy_tch)

-----------------------------------

Sum(res_av_denom14)

sum(decode(trx_type,0,ave_busy_tch))

------------------------------------------------------------

sum(decode(trx_type,0,res_av_denom14))

trf_97 (normal TRXs)

Average erlangs per BTS (OK if no SEG) = sum(decode(trx_type,1,ave_busy_tch))

------------------------------------------------------------

sum(decode(trx_type,1,res_av_denom14))

+

trf_98 (extended TRXs)

sum(decode(trx_type,0, ave_busy_tch))

------------------------------------------------------------------------------------------------

sum(decode(trx_type,0,decode(ave_busy_tch ,0,0,res_av_denom14)))

trf_97a (normal TRXs)

trf_12d =

Average erlangs per BTS =


-----------------------------------------------------------------------------------------

sum(decode(trx_type,1, decode(ave_busy_tch ,0,0 ,res_av_denom14)))

+

trf_98a (extended TRXs)

trf_12b =

trf_12c =


Counting average Erlangs over AREA (p_nbsc_res_avail) Author: J.Neva 03/2004

Version:

Average erlangs per area (SEG and extended TRXs used) = trf_171 =

trf_169 (normal TRXs)


----------------------------------------------------------------------------------------------------------

avg(decode(trx_type,1,res_av_denom14)) * count(distinct period_start_time)


--------------------------------------------------------------------------------------------------

avg(decode(trx_type,0, res_av_denom14)) * count(distinct period_start_time)

trf_170 (extended TRXs)

+


Counting average Erlangs per SEG (p_nbsc_res_avail) Author: J.Neva 03/2004

Version:

1) Use trf_171 for counting first the average erlangs per SEG (group by SEG_ID)

then

2) count average


Counting Erlangs (p_nbsc_dual_band)

Author: Markku Räsänen 11/98

Version: 1.0


BTS xx

TRX-nn

one TCH TSL

Call on this TCH

TCH seized (measurement starts from the estab_ind, i.e. MS is on TCH)

Measurement Period 2

TCH released (measurement stops from the release of the TCH)

TCH reservation length 3000 sec

59000 tch_single_band_hold_time

59001 tch_dual_band_hold_time

or

At release of TCH:

In the BSC, the length of the reservation (unit 0.48 sec) is added to

Also, one of the following counters is increased by one:

59002 tch_single_band_hold_reserv

59003 tch_dual_band_hold_reserv

or

NOTE: In the above example, the TCH reservation will not cause any call seconds to Measurement Period 1, and the reservation counter is also updated only at Measurement Period 2.

Measurement Period 1

At the end of the measurement period, the values of the measurement counters are transmitted to the NetAct






Counting Erlangs differencies between dual band and 20 sec sampling methods

Author: Markku Räsänen 11/98

Version: 1.0


SDCCH

TCH

When BSC receives Establish Indication,the RCS process is started and TCH reservation

time for Dual Band measurement is started

MS releases call or HO to another TCH

Resource availability starts at the start of the TCH reservation

Dual Band

Resource Availability (20s sampling)

RCS process and the DB measurement is stopped when BSC receives Release Indication

Resource Availability measurement is stopped when BSC receives rf channel release ack from the BTS

TCH

TCH

CALL SETUP

HO

Dual Band

Resource Availability

Dual Band

Resource Availability


Counting Erlangs impact of scope to formula Author: Juhani Neva

Version: 10.1

PMWG approval.:

BTS 1

BTS 2

BTS 3

SEG A

BTS 1

BTS 2

BTS 3

SEG B

AREA X

169 170

trf_171

172 173

trf_185

average BTS CS traffic

average CS traffic,

averaged over time,

summed up to

selected area

average SEG CS traffic

??


Counting Erlangs / RxQuality

Author: Juhani Neva

Version:

sum(freq_ul_qual0

+ freq_ul_qual1

+ freq_ul_qual2

+ freq_ul_qual3

+ freq_ul_qual4

+ freq_ul_qual5

+ freq_ul_qual6

+ freq_ul_qual7)/60

0.48 * ------------------------

sum(period_duration)

Can be used on TRX level and up.


Codec type related counters (S5->) Author: J.Neva 11/98

Version: 1.2 13.8.2002


V1 CODEC FTCH SEIZURES

/C1108

tch_full_seiz_speech_ver1

V2 CODEC FTCH SEIZURES (EFR)

/C1109


V3 CODEC FTCH SEIZURES

/C1110


V1 CODEC FTCH FAILURES

/C1127

tch_ended_due_transc_fr_rate1


/C1128



/C1129


NOTE: Codec counters are triggered in channel release (even if the call drops). Data calls do not trigger codec counters.

V3 CODEC HTCH SEIZURES

/C1113

tch_half_seiz_speech_ver3

V3 CODEC HTCH FAILURES

/C1132

tch_ended_due_transc_hr_rate3


/C1112



/C1131

tch_ended_due_transc_hr_rate2

Enhanced Full rate (v2, EFR)

EFR would provide speech quality

comparable to landline for GSM.

EFR speech codec has been specified

by Nokia with university of Sherbrooke

co-operation.

EFR codec was initially specified for ANSI.

ETSI selected the same codec in SMG#16.

TCH SEIZURES FOR

NEW CALL

/c1009

tch_norm_seiz

TCH SEIZURES FOR

HO (incl. DR in)

/c1008

tch_ho_seiz

TCH FCS SEIZURES

/c1099 (S5)


TCH SEIZURES FOR DATA CALLS

S p e e c h

Codec seizure counters

AMR HR

AMR FR

AMR HR

Codec failure counters

EFR EFR

AMR FR

FR FR

TRANSCODING FAILURE

ON NEW CH. IN HO

/C1031

tch_tr_fail_new

TRANSCODING FAILURE

ON OLD CH. IN HO

/C1030

tch_tr_fail_old

TRANSCODING FAILURE

CALL

/C1029

tch_tr_fail Call drops Call drops

NOTE1


/C1111



/C1130

tch_ended_due_transch_hr_rate1 HR HR

NOTE1

NOTE1 Speech ver2 is not implemented for HTCH.




















Aif circuit pool related counters Author: J.Neva 1/99

Version: 1.0


BSC O HO UNSUCC

/C4096

bsc_o_unsucc_a_int_circ_type

BSC I HO UNSUCC

/C4097

bsc_i_unsucc_a_int_circ_type

MSC O .HO UNSUCC

/C4102

msc_controlled_out_ho

MSC I HO UNSUCC

/C4101

msc_controlled_in_ho

MSC OUT SUCC HO

/C51097

ext_out_switch_crc_pool

MSC IN SUCC HO

/C51076

ext_in_switch_circ_pool

INTRA CELL HO UNSUCC

/C4098

ho_unsucc_a_int_circ_type

MSC I HO SUCCESSES

/C4093

msc_i_succ_switch_circ_pool

MSC I HO ATTEMPTS

/C4092

msc_i_att_switch_circ_pool

MSC O HO SUCCESSES

/C4095

msc_o_switch_circ_pool

MSC O HO ATTEMPTS

/C4094

msc_o_att_switch_circ_pool

HO ATT DUE TO AIF CIRCUIT TYPE

CHANGE

/C4099

ho_att_due_switch_pool

p_nbsc_ho

REJECTIONS DUE TO MISMATCH IN

CALL SETUP

/C1208

a_if_crc_mismatch_call_setup

p_nbsc_cc

p_nbsc_traffic

POOL AVAILABLE, RETRY

/C500934

m_switch_crc_pool

POOL NOT AVAILABLE

/C500935

m_speech_version_unavail

MSC IN SUCC ESTABLISHMENT

/C51061

estab_ext_in_switch_circ_pool

REJECTIONS DUE TO MISMATCH

/C1122

tch_rej_due_req_ch_aif_crc



















Handover enabling

‘Disable internal HO’


Version: 0.2 5.4.98

=Yes All HOs are MSC controlled (used only for test purposes!)

When "YES" the load between MSC and BSC is increased strongly, since all the

handovers are signalled via MSC. =No

Candidate

= serving cell

Yes

BSC controlled intra cell HO

No

First candidate

belongs to own BSC

No MSC controlled HO

Yes

‘Ext HO if other BSS’ =No

BSC controlled inter cell HO

=Yes

Cells belonging to

another BSC in the list

No BSC controlled inter cell HO

Yes

MSC controlled HO

(Source of info:Tarja Hiltunen)


Handover basics Author: J.Neva 10/2001

Version: 1.3 19.92002

PMWG : 1.3 19.92002 Note

cell_* mean intra-BTS

BTS

A

BTS

B

BTS

C

BTS

D

= Adjacency

For source cell one

of these is triggered

at an attempt:

msc_o_tch_tch_at

msc_o_ sdcch_tch _at

msc_o_sdcch_at

bsc_o_tch_tch_at

bsc_o_ sdcch_tch _at

bsc_o_sdcch_at

Inter-BTS HO

For target cell one


at success:

msc_i_tch_tch

msc_i_ sdcch_tch

msc_i_sdcch

bsc_i_tch_tch

bsc_i_ sdcch_tch

bsc_i_sdcch

HO attempt:

The BSC receives measurements from

the BTS. It processes the measurements

and decides on the handover algorithm.

If thresholds have been triggered for the

handover, the BSC generates

a candidate (target) cell list and starts the

handover attempt.

If candidate list is not generated for some

reason then HO is not attempted.

Intra-BTS HO

At an attempt one

of these is triggered:

cell_sdcch_at

cell_ sdcch_tch _at

cell_tch_tch_at

At a success one

of these is triggered:

cell_sdcch

cell_ sdcch_tch

cell_tch_tch

bsc_i_drop_calls

msc i_drop_calls

bsc_o_drop_calls

msc o_drop_calls

cell_drop_calls

For source cell one of

these is triggered if

target cell is

congested:

Bsc_o_fail_lack

Msc_o_fail_lack

For target cell one


If target is congested:

Bsc_i_fail_lack

Msc_i_fail_lack

If target is congested:

Cell_fail_lack

HO attempt & congestion:

If first cell in the candidate list occurs

congested the blocking counter is

triggered and the next cell is attempted.

HO success

Handover complete message

is the triggering point

for the successful handover counters.

Started HOs

001197 BTS_HO_ASSGN

001196 BSC_O_HO_CMD_ASSGN

001195 MSC_O_HO_CMD

004154 MSC_GEN_SYS_WCDMA_RAN_HO_COM

To make a difference between HO attempt and started HO.


Handovers by channel types

HO attempts

TCH-TCH

HO attempts

/ho_16

msc_o_tch_tch_at

+ msc_i_tch_tch_at

+ bsc_o_tch_tch_at

+ bsc_i_tch_tch_at

+ cell_tch_tch_at

SDCCH-TCH

HO attempts

/ho_17

msc_o_sdcch_tch_at

+ msc_i_ sdcch_tch _at

+ bsc_o_ sdcch_tch _at

+ bsc_i_ sdcch_tch _at

+ cell_ sdcch_tch _at

SDCCH-SDCCH

HO attempts

/ho_18

msc_o_sdcch_at

+ msc_i_sdcch_at

+ bsc_o_sdcch_at

+ bsc_i_sdcch_at

+ cell_sdcch_at

TCH-TCH

HO successes

/ho_19

msc_o_tch_tch

+ msc_i_tch_tch

+ bsc_o_tch_tch

+ bsc_i_tch_tch

+ cell_tch_tch

TCH-TCH

HO failures

= ho_16 - ho_19

SDCCH-TCH

HO successes

/ho_20

msc_o_ sdcch_tch

+ msc_i_ sdcch_tch

+ bsc_o_ sdcch_tch

+ bsc_i_ sdcch_tch

+ cell_ sdcch_tch

SDCCH-TCH

HO failures

= ho_17 - ho_20

SDCCHSDCCH

HO successes

/ho_21

msc_o_sdcch

+ msc_i_sdcch

+ bsc_o_sdcch

+ bsc_i_sdcch

+ cell_sdcch

SDCCH

HO failures

= ho_18 - ho_21

Author: J.Neva 8/96

Version: 1.2 19.9.2002

PMWG:1.2 19.9.2002

http://nea.ntc.nokia.com/formula.php?ne=BSC&formula_id=uav_14ho_16













Handovers by control

HO attempts

MSC controlled

HO attempts

/ho_22

msc_o_tch_tch_at

+ msc_i_tch_tch_at

+ msc_o_ sdcch_tch _at

+ msc_i_ sdcch_tch _at

+ msc_o_sdcch_at

+ msc_i_sdcch_at

MSC controlled

HO failures

= ho_22 - ho_25

BSC controlled

HO attempts

/ho_23

bsc_o_tch_tch_at

+ bsc_i_tch_tch_at

+ bsc_o_ sdcch_tch _at

+ bsc_i_ sdcch_tch _at

+ bsc_o_sdcch_at

+ bsc_i_sdcch_at

Intra cell

HO attempts

/ho_24

cell_tch_tch_at

+ cell_sdcch_tch_at

+ cell_sdcch_at

MSC controlled

HO successes

/ho_25

msc_o_tch_tch

+ msc_i_tch_tch

+ msc_o_ sdcch_tch

+ msc_i_ sdcch_tch

+ msc_o_sdcch

+ msc_i_sdcch

BSC controlled

HO successes

/ho_26

bsc_o_tch_tch

+ bsc_i_tch_tch

+ bsc_o_ sdcch_tch

+ bsc_i_ sdcch_tch

+ bsc_o_sdcch

+ bsc_i_sdcch

BSC controlled

HO failures

= ho_23 - ho_26

intra cell

HO successes

/ho_27

cell_tch_tch

+ cell_sdcch_tch

+ cell_sdcch

BSC controlled

HO failures

= ho_24 - ho_27

Author: J.Neva 8/96

Version: 1.0 6.9.96















BSC controlled outgoing handovers

Outgoing BSC ctrl

HO attempts

/ho_11

bsc_o_tch_tch_at

+ bsc_o_sdcch_tch_at

+ bsc_o_sdcch_at

Outgoing BSC ctrl

HO failures

/hof_8a

= ho_11

- bsc_o_succ_ho

Outgoing BSC ctrl

HO successes

/c4014

bsc_o_succ_ho

BSC outgoing HO,

drop call

/dcf_3

/c4084

bsc_o_drop_calls

Author: J.Neva 8/96

Version: 1.3 15.9.99


Blocked

/ c4072

bsc_o_fail_lack *

end of HO

/c4016

bsc_o_end_of_ho

return to old

/c4015

bsc_o_fail_ret

Not allowed

/c4038

bsc _o_not_allwd *

Call clear

/c4042

bsc_o_call_clr

wrong A-if circuit type

/ c4096 (S5)

bsc_o_unsucc_a_int_circ_type *

HO iterrupted and call

may drop

end of HO BSS

/c4017

bsc_o_end_ho_bss

HO iterrupted and call drops

Call drops after conn_ack

*) always before

HO command


http://nea.ntc.nokia.com/formula.php?ne=BSC&formula_id=uav_14hof_8a


http://nea.ntc.nokia.com/formula.php?ne=BSC&formula_id=uav_14dcf_3










MSC controlled outgoing handovers

Outgoing MSC ctrl

HO attempts

/ho_9

msc_o_tch_tch_at

+ msc_o_sdcch_tch_at

+ msc_o_sdcch_at

Outgoing MSC ctrl

HO failures

/hof_6a

=ho_9

- msc_o_succ_ho

Outgoing MSC ctrl

HO successes

/c4004

msc_o_succ_ho

MSC outgoing HO,

drop call

/c4107

= msc_o_call_drop_ho (S7)

Author: J.Neva 8/96

Version: 1.3 15.9.99


blocked

/c 4055

msc_o_fail_lack *

end of HO

/c4007

msc_o_end_of_ho

return to old

/c4006

msc_o_fail_ret

Not allowed

/c4037

msc_o_not_allwd *

Call clear

/c4041

msc_o_call_clear


/ c4102 (S5)

msc_controlled_out_ho *

adj.cell error

/c4100 (S5)

msc_o_adj_cell_id_err_c

HO interrupted and call

may drop

end of HO BSS

/c4008

msc_o_end_ho_bss

*) always before

HO command


http://nea.ntc.nokia.com/formula.php?ne=BSC&formula_id=uav_14ho_6a












BSC controlled incoming handover

Incoming BSC ctrld

HO successes

/c4010

bsc_i_succ_ho

Incoming BSC ctrld

HO failures

/hof_7a

ho_10-

bsc_i_succ_ho

Incoming BSC ctrld

HO attempts

/ho_10

bsc_i_tch_tch_at

+ bsc_i_sdcch_tch_at

+ bsc_i_sdcch_at


Version: 1.2 15.9.99


blocking

/ c4011

bsc_i_fail_lack *

connection failure

/c4012

bsc_i_fail_conn

end of HO

/c4081

bsc_i_end_of_ho


/c4097 (S5)

bsc_i_unsucc_a_int_circ_type *

BSS fail

/c4013

bsc_i_fail_BSS


may drop

Drop calls

/c4083

=bsc_i_drop_calls *) always before

HO command


http://nea.ntc.nokia.com/formula.php?ne=BSC&formula_id=uav_14hof_7a









MSC controlled incoming handover

Incoming

HO successes

/ho_32=

msc_i_succ_ho

Incoming

HO failures

/hof_15=

ho_35- ho_32

Incoming

HO attempts

/ho_35

msc_i_tch_tch_at

+ msc_i_sdcch_tch_at

+ msc_i_sdcch_at


Version: 1.1 15.9.99


blocking

/ 4001

msc_i_fail_lack *

connection failure

/c4002

msc_i_fail_conn

end of HO

/c4080

msc_i_end_of_ho


/ c4101 (S5)

msc_controlled_in_ho *

BSS fail

/c4003

msc_i_fail_BSS


may drop

HO interrupted

Drop calls (possible)

/c4108

=msc_i_call_poss_drop_ho *) always before

HO command


http://nea.ntc.nokia.com/formula.php?ne=BSC&formula_id=uav_14hof_15









Intracell handovers

Intra cell

HO attempts

/ho_24

cell_tch_tch_at

+ cell_sdcch_tch_at

+ cell_sdcch_at

intra cell

HO successes

/ho_27=

cell_tch_tch

+ cell_sdcch_tch

+ cell_sdcch

Intra cell

HO failures

/hof_9 =

ho_24 - ho_27

BSS fail

/c4021

cell_fail_BSS

MS lost

/c4020

cell_fail_move

Author: J.Neva 8/96

Version: 1.3 15.9.99


Blocked

/c4019

cell_fail_lack *

Return to old

/c4022

cell_fail_ret

Intracell HO not allowed

/c4036

cell_not_allwd *

Call clear or chn.blocking started

/c4039

cell_call_clr

Drop calls

/c4085

=cell_drop_calls

Incremented if failure occurs

after HO command

HO interrupted

and call

may drop

Wrong A-interface circuit type

/c4098

ho_unsucc_a_int_crct_type * *) always before

HO command

Note: these counter in S10.5 apply for radio cell (SEG) and thus

include intraBTS HOs




http://nea.ntc.nokia.com/formula.php?ne=BSC&formula_id=uav_14hof_9












Handover causes

Author: J.Neva 9/96

Version: 1.5 7.3.2001


High distance

/c4027

cause_distance

MSC invocation

(Traffic reason HO)

/c4028

cause_msc_invoc

Umbrella

/c4031

cause_umbr

OMC

(Forced HO by user)

/c4033

cause_omc

Directed Retry and Intelligent

Directed Retry

/c4079 (S2)

cause_dir_retry

Pre-emption

/c4086 (S3)

cause_pre_emption

Rapid field drop

/c4087 (S4)

cause_field_drop

Low distance

/c4088 (S4)

cause_low_distance

Bad CI

/c4089 (S4)

cause_bad_CI

Good CI

/c4090 (S4)

cause_good_CI

Slow moving MS

/c4091 (S5)

cause_ho_due_slow_mov_

ms

Switch circuit pool

/c4099 (S5)

ho_att_due_switch_crc_p

ool

Bad Rxlev on super

/c4109 (S7)

ho_att_due_bad_super_rxlev

Good Rxlev on regular

/c4110 (S7)

ho_att_due_good_regular_rxlev

Direct Access

/c4128 (S7)

ho_att_due_direct_access

MS slow speed

/c4105 (S6)

ho_due_ms_slow_speed

MS high speed

/c4106 (S6)

ho_due_ms_high_speed

ERFD HO

/c4111 (S7)

ho_att_due_ erfd

Channel administration

/c4034 NOT IN USE

cause_ch_adm

Traffic Reason (AMH)

/c4035 (S8)

ho_att_due_to_bsc_contr_trho

NOT IN USE

UL quality

/c 4023

cause_up_qual

eg.20%

UL level

/c4024

cause_up_lev eg.10-15%

UL interference

/c4029

cause_interf_up

prefer. 0%

Pbdgt

/c4032

cause_pbdgt

20-30%

DL quality

/c4025

cause_down_qual

eg.20%

DL level

/c4026

cause_down_lev eg.10-15%

DL interference

/c4030

cause_interf_down

prefer. 0%

Handover Support for

Coverage Enhancement (HSCE)

DADLB

/c4129 (S8)

ho_att_due_to_dadlb

Upgrade of GPRS territory

/c4130 (S9)

ho_att_due_to_gprs

Upgrade of HSCSD area

/c4141 (S10)

Note: counters only triggered when a valid neigbouring cell is identified after BSC has received averaged measurement report from MS





























http://essrv509ntc.ntc.nokia.com/dynaweb/NED31_bsc_s7e/8070271/@Generic__BookView;pt=26211?DwebQuery=HSCE







Handover Causes per Handover Types Author: J.Pekkarinen 12/97

PMWG appr.: NOK (see HO algoritm

&PC Description)

Intra Cell TCH HO

UL interference /c4029

OMC (forced ho) /c4033

DL quality /c4025

DL interference /c4030

Pre-emption /c4085

Low distance /c4088

Distance /c4027

Bad CI /c4089

Good CI /c4090

Bad Rxlev on super /c4109

Good Rxlev on reg /c4110

Inter Cell TCH HO

UL quality /c4023

UL level /c4024



DL quality /c4025

DL level /c4026


Pre-emption /c4085

Low distance /c4088

Distance /c4027

Bad CI /c4089

Good CI /c4090

Direct Access /c4128

Pbdgt /c4032

Umbrella /c4031

MSC invoc (traffic ho) /c4028

Slow moving MS /c4091

Rapid field drop /c4087

MS slow speed /c4105

MS high speed /c4106

ERFD HO /c4111


External TCH HO (source)

UL quality /c4023

UL level /c4024


Pbdgt /c4032


DL quality /c4025

DL level /c4026


Pre-emption /c4085

Low distance /c4088

Distance /c4027

Umbrella /c4031






ERFD HO /c4111

Switch circuit pool /c4099

Intra Cell SDCCH HO



DL quality /c4025


Pre-emption /c4085

Low distance /c4088

Distance /c4027

Bad CI /c4089

Good CI /c4090

Bad Rxlev on super /c4109

Good Rxlev on reg /c4110

Inter Cell SDCCH HO

UL quality /c4023

UL level /c4024



DL quality /c4025

DL level /c4026


Pre-emption /c4085

Low distance /c4088

Distance /c4027

Bad CI /c4089

Good CI /c4090


Pbdgt /c4032

Umbrella /c4031






ERFD HO /c4111

Ext.SDCCH HO (source)

UL quality /c4023

UL level /c4024


Pbdgt /c4032


DL quality /c4025

DL level /c4026


Pre-emption /c4085

Low distance /c4088

Distance /c4027

Umbrella /c4031






ERFD HO /c4111

Switch circuit pool /c4099

Directed Retry

Intra Cell SDCCH to TCH HO

Inter Cell SDCCH to TCH HO

External SDCCH to TCH HO

Directed retry /c4079

TCH to TCH HOs SDCCH to

SDCCH HOs

SDCCH to

TCH HOs

(DRs)

Direct Access (DAC) (S7)

Intra Cell SDCCH to TCH DAC

Inter Cell SDCCH to TCH DAC


SDCCH to

TCH HOs

(Direct Accesses)

(Intra / Inter cell)

NOTE: THIS PICTURE IS NOT

UPDATED











































































































BTS

CS paging on system level (S10,M10)

MFR = Number of Multiframes between Paging (2..9, typical e.g.5 or 6)

Number of multiframes between two transmissions of the same paging message to the MS’s

of the same paging group. Values 2 to 9 Multiframes corresponds to procedure length from

0 up to 0.47 - 2.2 seconds. NSN recommends value 5.

The effect on the Call Setup depends at which point of the paging cycle the BTS receives the

paging message from BSC/MSC, that is to be sent on the Air interface.

PRACTICAL MEANING:

- AFFECTS BATTERY LIFE TIME (MS listens paging periodically: smaller value -> shorter lifetime)

- DEFINES HOW MUCH PAGING MESSAGE SENDING TO AIR INTERFACE MAY BE DELAYED

Author: J.Neva 8/99



MS

LA

BSC

MSC

Ref: Sys.Technical note 1/98,

NSS stats advanced guide

INT= Repaging interval (0.1-10s, typical 3,5sec)

Value not recommended to be smaller than the default value

(should be >= 3s), repaging always IMSI

AT= Repaging attempts (0-50, typical 0 or 1)

Max.value 1 recommended if TMSI used (0 is recmnd).

Max.value 3 recommended if IMSI used.

LA specific parameters in MSC (MML ZELP):

BTS specific parameters in BSC:

BSC specific parameters in MSC (MML ZEDP):

Paging method (LAC recommended)

All BTS in LA are paged.

BTS

BTS BTS

Paging response (MTC or SMS, signalling on SDCCH)

/c3012 (S1) succ_seiz_term

Paging response (MTC or SMS, signalling on TCH, FACCH)

/c3023 (S3) tch_mtc

Only one (or none) replies.

Average paging time of succ.MTC and SMS

- start is the 1st page, B-busy excluded

- end is SCCP_establisment_req from BSC

p_msc_cell.ave_page_time (1/100 sec)

Pagings via Aif

p_msc_vlr.succ_page

p_msc_vlr.fail_page

AT applied to all 2

paging methods

=> big impact to paging time

Per BTS

TMSI page

+repages IMSI page

+repages

Parameters in MSC (MML ZMXM):

TMSIusage

TMSIpagerepetiton

1st page& AT timesrepage

2nd page& AT timesrepage

Yes Yes with TMSI with IMSI

Yes No with TMSI no

No Yes with IMSI no

No No with IMSI noSee also reports: Traffica

See reports: ND 632, 600

See reports: ND186, 222

Per MSC

No paging response

p_msc_cc cc=012 See reports: ND 015

+Search if

defined

Nbr of CS paging messages sent on PCCCH

/c72083 (S9) pac_pag_req_for_cs_pag

SGSN

CS paging msgs from Gb on CCCH

/c3058 (S9) cs_paging_msg_sent

Gb Aif

CS paging msgs from Aif on CCCH

/c3000 (S1) paging_msg_sent

SGSN is

alternative

route for

pagings (MSC

controls)

Pgn via SGSN

p_msc_vlr.succ_sgsn

p_msc_vlr.fail_sgsn

Search

p_msc_vlr.succ_ms

p_msc_vlr.fail_ms

Failed pagings&repagings

Incl. B-busy in M8-9

Call could not be delivered

Paging refused, big load

/c500627 (S9)

aiv_paging_refused_big_load

Per BSC

http://essrv509ntc.ntc.nokia.com:6336/dynaweb/NED31_bsc_s8e/9090312/@Generic__BookView;pt=16233?DwebQuery=MFR



//NCSMSG24TR/HTDOCS/CSTRE/NOS/SE/DOCS/jne703.txt

http://nea.ntc.nokia.com/~neva/CD_development/rpp632mx.mdl




http://wwwmsg.ntc.nokia.com/ni/cc_www/cc_m9/0012.HTM









Paging capacity, air interface (until S7)

Paging and access grant channels use the same DL physical channel (Nokia uses timeslot 0) of BCCH carrier.

Paging has priority if AG=0. AG is sent also on PCH if there is no paging to send.

combined capacity =

12 slots per multiframe (combined control channel)

36 slots per multiframe (noncombined control channel)

message sent on paging or access grant channel takes 4 slots

3 messages per multiframe (combined control channel)

= 12 messages per second

9 messages per multiframe (noncombined control channel)


MFR = Number of Multiframes between Paging (2..9)

AG = Number of Blocks Reserved for Access Grant

(0..7 if noncombined, 0..2 if combined, 1..7 if SBCH used in SDCCH/8)

(3-AG)*MFR (combined control channel)

(9-AG)*MFR (noncombined control channel)

Nbr of Paging Groups =

Each paging group has separate buffer of 8 Abis commands. MS defines it’s group from IMSI.

Buffering delay can take 2..16sec Max.paging buffer size = 8* Nbr of Paging Groups

Paging buffer space (BTS) = free buffers (max 8) * Nbr of Paging Groups /2

one paging message can contain

- max. 2 IMSI

- max. 4 TMSI

Final choise is on BTS.

Min Paging buffer space (BSC) = min_paging_buf (counter 3018)

MBCCHC and MBCCB are combined control channels

MBCCH is non-combined control channel

BSC stores the smallest value per BTS over the measurement period.

If the value = 0 paging messages have been lost (paging may still be succesfull thanks to repaging)

Sent in CCCH_Load_Ind from BTS to BSC. 1/2 is is an additional safety margin to give an early

warning of potential paging capacity problems.

Author: J.Neva 8/96

Version: 1.1 18.2.97


Average Paging buffer space (BSC) = ave_pch_load / res_acc_denom2 When 3018 is less than Paging_Buffer_Limit

(it is defined in BSC; >EGO, default = 1, threshold = 0...16). then BSC sends an overload message

to MSC. There is no automatic reallocation of the channel structure in case of overload.

Nokia MSC does not use the overload message because paging is by LAs not by BTS.

NOTE: After S7 SCCCH imrovements

3018 does not get to 0 anymore





Version: 1.0

PMWG appr.: 11.10.98

Deleted Paging Commands

delete_paging_command

/c3038 (S7)

Average Paging Buffer Occupancy %

/c3036/c3037 (S7)

Average PCH Load on CCCH (S1)

/c3008/c3009

Minimum Paging Buffer on CCCH

/c3018

Maximum Paging Buffer Occupancy %

/c3035 (S7)

Paging Buffer Load, new

counters in S7

Paging Buffer Load

(before S7)

CCCH load (S7)

Each time a paging multiframe cycle ends

the occupancy percentage

(occupied buffer space versus maximum space)

of each paging queue is calculated

Some group specific paging queue becomes full

so that a paging command cannot be stored to the

buffer and the paging command is deleted.

Indicates the remaining space for

Paging Commands.

The smaller the value, the greater the load

on the PCH.

Minimum size of the paging buffer

on a CCCH.

The smaller the value, the greater the load

on the PCH.

NOTE the way BTS counts:

free buffers (max 8) * Nbr of Paging Groups /2









Author: J.Neva

Version: 1.5 2.11.2001

PMWG appr.: 1.0 16.8.00

Average Occupancy %

c3048/c3049

pgn_6 (S9)

Average free space

/c3046/c3047 pgn_10 (S9)

CCCH Load (S9)

Max.

Occupancy %

/c3050 (S9)

Average

occupancy %

due to paging

pgn_7 (S9)

Average

occupancy %

due to DRX AG

pgn_8 (S9)

Average occupancy % due to non-DRX AG

pgn_9 (S9)

PS-paging_command

sent to BTS

/c3057 (S9) CS paging msg sent

/c3087 (S9)

Doc.Ref:

1) Nokia GPRS Abis L3 Interface,Interface specifications

2) GPRS requirement specification, BTS SW

DRX (discontinuous reception) Buffer (former called 'paging buffer')

Non-DRX Buffer (new in S9)

Radio Air-interface load

Ref: CCCH Load Ind

Supplementary Load Info 2

BTS reports the % as

occupied radio blocks vs.

all radio blocks

Ref: CCCH Load Ind

Radio Interface CCCH

Load

(9.3.15c)

GPRS buffer area (Gb-Interface)

Deleted Paging Commands

delete_paging_command

/c3038 (S7)

Average Occupancy %

c3036/c3037

pgn_5 (S7)

Average free space

/c3008/c3009 pgn_3 (S1)

Min. Paging Buffer on CCCH

/c3018 (S1)

Max.

Occupancy %

/c3035 (S7) Each time a paging

multiframe cycle ends

the occupancy percentage

(occupied buffer space

versus maximum space)

of each paging queue is

calculated

Some group specific paging

queue becomes full

so that a paging command

cannot be stored to the

buffer and the paging

command is deleted.

Note that there can deleted

pagings even

if the paging buffer is not full

(Imm.Ass. Lead time exp.)

Minimum size of the paging

Buffer on a CCCH.The smaller

the value, the greater the load

on the PCH.

GSM buffer area (A-Interface)

CS-paging_command

sent to BTS

/c3058 (S9)

max.lead time for paging message = 64*51 frames= 15s Max_lead_ time for paging message = 5s

Paging_command (CS) to BTS

/c3000 (S1)

The smaller the value,

the greater the load

on the PCH.

NOTE:

In order ot make occup.%

work correctly the

min. reporting period

for CCCH_LOAD_INDmust be

longer than the max.duration

of four 51-multiframes,

i.e. 4*51*4,615ms=0,94sec

MS needs to paged only when

it is in MM-idle state.

SGSN (and MS) has ready timer.

SGSN stores the MS location

after last PDU transmission.

Timer is reset if new transmission

occurs. Default ready timer

value is 20 s (?)

See ND reports:

186, 213, 216,

See ND reports 186 , 216

All msgs that are sent in DRX cycle (MFR defined).

Lead time 4s

All msgs that are sent immediately:

CS Imm.Ass. and UL TBF I.e.

all Imm.Ass. sent as answer to RACH

Imm.Ass.for DL TBF establ.

Nbr of CS paging

messages sent on

PACCH

/c72083

If Imm.Ass. msg lead time

expires it will be sent via

paging buffer (paging deleted)

CS or PS paging cmds ,

DRX AG from Gb

incl. also

CS pges

from Gb

if GENA=N

CS paging cmnds

from A-if

Air if

Lead time 2+2s

First 2 sec Paging Reqs have priority

Last 2 sec Imm.Ass.msgs have priority

Pagings lost on Aif (max 53

pagings in BCSU unhandled)

/c500627

CS pagings via SGSN come when

Gs interface is used in the system

and MS is GPRS attached.



http://nea.ntc.nokia.com/formula.php?ne=BSC&formula_id=uav_14pgn_6













//NCSMSG24TR/HTDOCS/CSTRE/NOS/SE/DOCS/Jne738.html

























Paging capacity, air interface (S7 and DF4/B11) 1/4

combined capacity =

12 slots per multiframe (combined control channel)

36 slots per multiframe (noncombined control channel)

message sent on paging or access grant channel takes 4 slots

3 messages per multiframe (combined control channel)


9 messages per multiframe (noncombined control channel)


MFR = Number of Multiframes between Paging (2..9)

AG = Number of Blocks Reserved for Access Grant

(0..7 if noncombined, 0..2 if combined, 1..7 if SBCH used in SDCCH/8)

(3-AG)*MFR (combined control channel)

(9-AG)*MFR (noncombined control channel)

Nbr of Paging Groups =

one paging message can contain

- max. 2 IMSI

- max. 4 TMSI

Final choise is on BTS.

MBCCHC and MBCCB are combined control channels

MBCCH is non-combined control channel

Author: Markku Räsänen10/98

Version: 1.0 21.10.98

PMWG approval.: 9.3.99

Calculation of the amount of Paging Groups

Paging and access grant channels use the same DL physical channel (Nokia uses timeslot 0) of BCCH carrier.

Access Grant has priority if AG=0. If AG<> 0, paging has priority on paging blocks. If AG<>0, Access Grant is sent also on PCH

if there is no paging to send. If AG=0, Access Grant is sent on PCH with priority.

NOTE: Calculation of the amount of paging groups is the as same prior to S7/DF4


Paging capacity, air interface (S7 and DF4/B11) 2/4 Author: Markku Räsänen 10/98

Version: 1.0 21.10.98


Calculation of the amount of Paging Groups

Each paging group has a separate buffer. The depth of the buffer (Paging Group

Queue Depth) depends on BS-PA-MFRMS parameter. Max_lead_time = 5, not

modifiable. The Queue Depth indicates how many radio interface Paging Requests

it is possible to store in the buffer.

Paging Group Queue Depth= MAX(ROUND(max_lead_time * 1000 / (BS-PA-MFRMS * 51 * 4.615)),1)

Counter N: N(New) = N(current) + 1 for TMSI paging commands

Paging Buffer Space = The current value is sent in the the CCCH_Load_Ind from BTS to BSC. BSC stores the smallest value.

When PBS < 1, BSC sends an overload message to MSC. There is no automatic reallocation of the

channel structure in case of overload. Nokia MSC does not use the overload message because

paging is by LAs not by BTS.

MS defines it’s group from IMSI

Example values of Paging Group Queue Depth

BS-PA-MFRMS Paging Group Queue Depth

4 5

6 4

8 3

Counter N: N(New) = N(current) + 2 + (N(current) mod 4) div 3 for IMSI paging command For each Paging Group, there is a Counter N to follow up the usage of the buffer.

Counter N: N(Max) = 4*(Paging Group Queue Depth)

Amount of deleted paging commands is reported to the BSC in CCCH_Load_ind, and BSC

adds this amount to counter 3038 delete_paging_command.

Each time a Paging Request is sent to the Radio Interface, N is decremented according to

formula N(new) = max{N(current) - 4, 0}

Free Space Total (IMSI)

= Free SpaceTotal (TMSI) / 2

TMSI paging command = Abis Paging Command with TMSI identity

IMSI paging command = Abis Paging Command with IMSI identity

Free Space (TMSI)= N(max) - N(current)

Free Space Total (TMSI)= Sum of Free Space (TMSI) in all queues

Free Space available in the Paging Group Queue for TMSI pages

N(new) > N(Max) ? If N(new) > N(max), the paging command is deleted and

N(current) remains the same as before

Average Buffer Occupancy = For each paging group, and each paging multiframe, occupancy % = 100 *(N/N(max)) %

AVERAGE(occupancy%) over all paging groups for each paging multiframe is reported from BTS to BSC in CCCH_Load_Ind

Average Buffer Occupancy ( BSC) = Ave_paging_buffer (c3036) / res_acc_denom5 (c3037)

Maximum Buffer Occupancy

Percentage =

Peak value of all Average Buffer Occupancy values in the

CCCH_Load_Ind within the period is stored in BSC is a separate

counter max_paging_buffer_capa (counter 3035)

Min Paging buffer space (BSC) = min_paging_buf (counter 3018)

nbr of additional paging commands with IMSI that is possible to store to the BTS.









Counter N and the formation of Radio Interface Paging Requests from Abis Paging Commands:

in this example, one Paging Group Queue is described

1. msg

2. msg

3. msg

4. msg

5. msg

6. msg

1 2 3 4

9 8

12 13 14

5 6

7

10 11

15

IMSI TMSI empty

Nnew = Nold + 1 for TMSI paging command Nnew = Nold + 2 + (Nold mod 4) div 3 for IMSI paging command Buffer full when Nnew > Nmax

1 2 3 4 5 6 9 8 7 10 11 12 13 14 15

1. msg 2. msg 3. msg 4. msg 5. msg 6. msg

1 2 3 4 5 7 10 11 12 14 16 17 18 19 22 N Paging Request Type

Formula for N for IMSI paging command works out as follows. Nnew = Nold +2 always but the case when the new IMSI paging command forces us to leave an "empty" spot to the Paging Request - this is the case if the paging request has earlier either 1 TMSI page and 1 IMSI page (2. Msg above), or 3 TMSI pages (5 msg above) - then Nnew = Nold+3. There is no passing lane in the paging buffers - Paging Commands are put to messages in the order in which they come to the BTS. So, in the above example, it is not possible to take mobile identity 8 from 3.msg, and put it before mobile identity 7 so that we could include it in 2.msg where there is an empty space for one TMSI mobile identity

3

1

2

1

2

1

Author: Jukka Peltola 10/98

Version: 1.0




Calculation and reporting of the maximum and average buffer occupancy percentages

PMF_average

maximum

load-%

Paging group index

load-%

time

average

One CCCH reporting period

BSC stores the maximum value received during the measurement period (e.g. 60 min) c3035 max_paging_buffer_capa

BSC adds the values received during the measurement period (e.g. 60 min) c3036 ave_paging_buffer_capa and the number of CCCH_load_ind messages c3037 res_acc_denominator_5

Paging Multiframe PMF

After each reporting period, CCCH Load Ind is sent to the BSC with the deleted page, maximum and average buffer occupancy information CCCH reporting period is a HW data parameter at the BTS, the default period is 30*4*51*4.615ms = appr. 28 sec.

At the end of each Paging Multiframe Cycle (Paging Multiframe Cycle = each Paging Group sent once), the load (or occupancy) is calculated as 100*(N/N(max)) %. From this, the ABO = PMF_average = AVERAGE(occupancy-%) is calculated

The ABOs are then collected over the CCCH reporting period, the average over the CCCH reporting period is calculated and the maximum selected

Author: Jukka Peltola 10/98

Version: 1.0


AB O= Average Buffer Occupancy





BCSU Overload (S7) Author: J.Pekkarinen 12/97

Version: 1.1 11.1.2001

PMWG appr.: 1.0 11.2.98

V. 1.2 3.7.2002 J.Neva

BCSU Overload Number of refused accesses, when overload

lower limit (34 unhandled messages) has occured.

Other accesses are refused

except emergency calls, MOC and MTC.

Number of refused calls, when overload

upper limit (53 unhandled messages)

has occured. All calls are refused.

Number of deleted RACHs on a CCCH,

when RACH load is too high.

Max.20 simultaneous requests per CCCH

to MCMU

Lower Limit

/c3039 (S7)

bcsu_overload_lower_limit

Upper Limit

/c3040 (S7)

bcsu_overload_upper_limit

Deleted RACH

/c3041 (S7)

bcsu_overload_deleted_rach

BCSU protection. Impact to all cells attached to the BCSU

Protection for highly loading cells

See ND report 134






Short Messages

SMS successful

/c3028

succ_sdcch_sms_est

SMS unsuccessful

/c3029

unsucc _sdcch_sms_est

SMS

SMS successful

/c3026

succ_tch_sms_est

SMS unsuccessful

/c3027

unsucc _tch_sms_est

SDCCH

TCH

SMS

MS idle

No call on

MS Active

Call on

SMS failure %

Sms_3

SMS MO failure %

Sms_7

SMS MT failure %

Sms_8

SMS failure %

Sms_2

FACCH call

setup

MO SDCCH SMS successful

/c3064

succ_mo_sms_sdcch

MO SDCCH SMS unsuccessful

/c3065

unsucc _mo_sms_sdcch

http://nea.ntc.nokia.com/cgi-bin/cgiwrap/neva/counters?003028




http://nea.ntc.nokia.com/cgi-bin/cgiwrap/neva/frmls?sms_3









Congestion & blocking

BTS

TRX

RACH


Version: 1.3 10.1.2004

BSC

RACH/NOISE COLLISION

Abis link

Alarm 2720

‘Telecom Link overload’

(030)

SDCCH congestion time (130,216) c2033 = sdcch_cong_time

Blocked SDCCH seiz att (216) c1001 = sdcch_busy_att

Blocking (204,204, 130,216) , csf_1a

Aif TC

Processor unit

load (605,614)

avg.70% critical

(avg. 50% for MB)

HLR

TCH congestion time (138, 216), c2027 = tch_cong_time

Blocked TCH call att (216) blck_9c

Blocking (204,200,138,216) , csf_3m,csf_3i,csf_3l

No direct counter but

affects csf_2j

(200, 204, 250)

Aif

Circuit group blocking (602,604)

M058, M026: Max. 1% in BH

Signalling link (SS7) traffic

(524)

Add link if traffic > 200mErl

NOTE: In MSC terminology

instead of term ‘blocking’

there is term ‘call congestion'

RACH load

rach_3, rach_4

(188, 216)

MS

Paging

AG blocking (229,204, 200, 216) (blck_13)

AG blocking, GPRS (229) (blck_21)

Access

grant

MSC

Processor unit

load (184,212)

avg.70% critical

avg.60% max. is

recommended by R&D

(avg. 50% for MB)

Processor unit

load (606,615)

avg.70% critical

(avg. 50% for MB)

Paging buffer

occupancy

pagings deleted

(186)

SGSN

Bearer channel /NSVC (240)

Alarm '7746'

‘Ch congestion in BTS above defined threshold'

NOTE:The lines indicate logical source of the info,

the actual genereation of the info can be in the above

standing object

500627 AIV PAGING REFUSED BIG

LOAD (BSCU overload )

0026 SIGNALLING LINK LOAD

OVER THRESHOLD (>0.2erl)

3164 PCU PROCESSOR OVERLOAD




http://nea.ntc.nokia.com/formula.php?ne=BSC&formula_id=uav_14csf_1a





http://nea.ntc.nokia.com/formula.php?ne=BSC&formula_id=uav_14blck_9c

http://nea.ntc.nokia.com/formula.php?ne=BSC&formula_id=uav_14csf_3m

http://nea.ntc.nokia.com/formula.php?ne=BSC&formula_id=uav_14csf_3i

http://nea.ntc.nokia.com/formula.php?ne=BSC&formula_id=uav_14csf_3l

http://nea.ntc.nokia.com/formula.php?ne=BSC&formula_id=uav_14csf_2j



















Call Success Factors

SDCCH success

ratio

SDCCH access

probability

TCH access

probability

TCH success

ratio

Improvement

by FACCH

call setup

Improvement

by Call Re-establishment

Improvement

by Directed Retry,

Queuing

Call

success

ratio

Author: J.Neva 6/97

Version: 1.2 12/2001


Improvement

by Dynamic

SDCCH

Allocation (S7)

See: experiences

Call setup

Call completion

/ retainability

Call drops Call drops Blocking Blocking

Critical parameter: Rx Lev Access Min (RXP) Critical parameter: Radio Link Timeout (RLT)



Call Success Factors , S6 (area)

SDCCH success

ratio

CSF_2xx

SDCCH access

probability

CSF_1a

TCH access

probability

CSF_3k

TCH success

ratio

CSF_4p

CSF_1a

SDCCH_busy_att - tch_seiz_due_sdcch_con

100-(100* ----------------------------------------) %

SDCCH_seiz_att

All counters from p_nbsc_traffic.

CSF_2a

sum(SDCCH_RADIO_FAIL+SDCCH_RF_OLD_HO+SDCCH_USER_ACT+SDCCH_BCSU_RESET+

SDCCH_NETW_ACT +SDCCH_BTS_FAIL+

SDCCH_LAPD_FAIL+SDCCH_A_IF_FAIL_CALL+SDCCH_A_IF_FAIL_OLD)

100- 100*----------------------------------------------------------------- %

sum(sdcch_assign+sdcch_ho_seiz)

- sum(SDCCH_ABIS_CALL+SDCCH_ABIS_FAIL_OLD)

All counters from p_nbsc_traffic table.

Note: 1) Experience has shown that A-if blocking is not included.

2) Includes not only calls but LUs

CSF_3k = 100_blck_8c =

sum(a.tch_call_req-a.tch_norm_seiz)

- sum(b.msc_o_sdcch_tch+b.bsc_o_sdcch_tch+c.cell_sdcch_tch); DR

- sum(a.tch_rej_due_req_ch_a_if_crc ; Aif type mismatch or congestion

-(b.bsc_i_unsucc_a_int_circ_type ; Aif circuit pool handover failures

+b.msc_controlled_in_ho

+b.ho_unsucc_a_int_circ_type))

100- 100* ---------------------------------------------------- %

sum(a.tch_call_req)




+b.ho_unsucc_a_int_ciric_type))

a = p_nbsc_traffic

b = p_nbsc_handover

csf_4p = 100-dcr_3f

sum(a.TCH_RADIO_FAIL+a.TCH_RF_OLD_HO+a.TCH_ABIS_FAIL_CALL+a.TCH_ABIS_FAIL_OLD+

a.TCH_A_IF_FAIL_CALL+ a.TCH_A_IF_FAIL_OLD+ a.TCH_TR_FAIL+ a.TCH_TR_FAIL_OLD+

a.TCH_LAPD_FAIL+ a.TCH_BTS_FAIL+ a.TCH_USER_ACT+ a.TCH_BCSU_RESET+

a.TCH_NETW_ACT+a.TCH_ACT_FAIL_CALL)

- sum(b.sdcch_call_re_est + b.tch_call_re_est) ;(call re-establishments)

100 -100* ------------------------------------------------------------------------------ %

sum(a.TCH_NORM_SEIZ) ;normal new calls

+ sum(c.msc_i_sdcch_tch+c.bsc_i_sdcch_tch +c.cell_sdcch_tch) ;DR calls

+ sum(a.tch_seiz_due_sdcch_con) ; FACCH call setup


a = p_nbsc_traffic

b = p_nbsc_res_access

c = p_nbsc_ho

Call success ratio

100* csf_1a/100 * csf_2xx/100 * csf_3k/100 * csf_4p/100

CSF_2f

sum(a.tch_norm_seiz)

=100* ------------------------------------------------------------------------- %

sum(b.succ_seiz_term+b.succ_seiz_orig+b.sdcch_emerg_call+b.sdcch_call_re_est

-b.succ_sdcch_sms_est- b.unsucc_sdcch_sms_est)

- sum(a.tch_call_req-a.tch_norm_seiz-msc_o_sdcch_tch-bsc_o_sdcch_tch) ;blocked

- supplem.serv.requests (unknown factor )

- call clears before TCH (unknown factor)

+ netto impact of SDCCH-SDCCH ho (unknown factor)

+ netto icoming DR (unknown factor)

a = p_nbsc_traffic, b = p_nbsc_res_access, c = p_nbsc_ho

Note: 1) Includes also A-if blocking.

2) Works for call re-est. if drop on TCH.

3) If drop on SDCCH and call re-est. then double count in dividor

OR

good:>99,5%

(good:>99,9%)

good:>97%, (best seen: 98,5%)

good:> 95% (best seen: 96%)

SDCCH TCH

Author: J.Neva 4/97

Version: 1.3 16.3.98


good:> 98% (best seen: 98,9%)

Related problems!!!:

csf_2f shows over 100%



http://nea.ntc.nokia.com/formula.php?ne=BSC&formula_id=uav_14csf_3k

http://nea.ntc.nokia.com/formula.php?ne=BSC&formula_id=uav_14csf_4p


http://nea.ntc.nokia.com/formula.php?ne=BSC&formula_id=uav_14csf_2xx


http://nea.ntc.nokia.com/formula.php?ne=BSC&formula_id=uav_14csf_4p

http://nea.ntc.nokia.com/formula.php?ne=BSC&formula_id=uav_14csf_2f

http://nea.ntc.nokia.com/~neva/SE_bulletins/bullet089.htm


CSF_3k


- sum(b.msc_o_sdcch_tch+ b.bsc_o_sdcch_tch +c.cell_sdcch_tch)





100- 100* ---------------------------------------------------------- %

sum(a.tch_call_req)





a = p_nbsc_traffic

b = p_nbsc_handover

Call Success Factors, S6 (BTS)

SDCCH success

ratio

CSF_2xx

SDCCH access

probability

CSF_1a

TCH access

probability

CSF_3d

TCH success

ratio

CSF_4r

CSF_2a




100- 100*----------------------------------------------------------------- %




Note: 1) Experience has shown that A-if blocking is NOT included.


CSF_4r






100 -100* ------------------------------------------------------------------------------ %

sum(a.tch_norm_seiz) ;(normal calls)

+ sum(c.msc_i_sdcch_tch+c.bsc_i_sdcch_tch +c.cell_sdcch_tch) ;(DR calls)


+ sum(c.msc_i_tch_tch+c.bsc.bsc_i_tch_tch) ;(TCH-TCH Ho in)


a = p_nbsc_traffic


c = p_nbsc_ho

Call success ratio

100* csf_1a/100 * csf_2xx/100 * csf_3d/100 * csf_4r/100

CSF_2g

sum(a.tch_norm_seiz) ;(all TCH seiz.for new call)

=100* -------------------------------------------------------------------- %

sum(b.succ_seiz_term+b.succ_seiz_orig

+b.sdcch_call_re_est+b.sdcch_emerg_call) ;(calls,sms, ss reqs)

- sum(b.succ_sdcch_sms_est

+ b.unsucc_sdcch_sms_est) ;(sms attempts)

+ sum(c.msc_i_sdcch + c.bsc_i_sdcch ;(netto SDCCH HO in)

-c.msc_o_sdcch - c.bsc_o_sdcch) ;(unknown how big part calls

- sum(a.tch_call_req-a.tch_norm_seiz) ;(DR and air itf blocking)

- supplem.serv. requests ;(unknown factor)

- call clears before TCH ;(unknown factor)



Note: Includes also A-if blocking. If call re-establ. occurs already on SDCCH

the formula is not correct but if re-est. on TCH it is correct.


OR

CSF_1a


100-(100* ----------------------------------------) %

SDCCH_seiz_att

All counters from p_nbsc_traffic. Author: J.Neva 4/97

Version: 1.3 16.3.98








http://nea.ntc.nokia.com/formula.php?ne=BSC&formula_id=uav_14csf_2xx

http://nea.ntc.nokia.com/formula.php?ne=BSC&formula_id=uav_14csf_3d

http://nea.ntc.nokia.com/formula.php?ne=BSC&formula_id=uav_14csf_4r

http://nea.ntc.nokia.com/formula.php?ne=BSC&formula_id=uav_14csf_2g




SDCCH success

ratio

CSF_2xx

SDCCH access

probability

CSF_1a

TCH access

probability

CSF_3l

TCH success

ratio

CSF_4v

CSF_1a


100-(100* ----------------------------------------) %

SDCCH_seiz_att


CSF_2b

sum(SDCCH_RADIO_FAIL+SDCCH_RF_OLD_HO+SDCCH_USER_ACT+SDCCH_BCSU_RESET

+SDCCH_NETW_ACT +SDCCH_BTS_FAIL+SDCCH_LAPD_FAIL

+SDCCH_A_IF_FAIL_CALL+SDCCH_A_IF_FAIL_OLD+SDCCH_ABIS_FAIL_OLD)

100- 100*----------------------------------------------------------------- %

sum(b.succ_seiz_term+b.succ_seiz_orig+b.sdcch_emerg_call

+b.sdcch_call_re_est-b.succ_sdcch_sms_est- b.unsucc_sdcch_sms_est)

+sum(c.msc_i_sdcch + c.bsc_i_sdcch)

a= p_nbsc_traffic table, b= p_nbsc_res_access, c= p_nbsc_ho



CSF_3l =100-blck_8d



+ sum(a.tch_succ_seiz_for_dir_acc)





100- 100* ---------------------------------------------------- %

sum(a.tch_call_req)





a = p_nbsc_traffic

b = p_nbsc_handover

CSF_4v = 100-dcr_3j





- sum(b.tch_re_est_assign) ;(call re-establishments)

100 -100* ------------------------------------------------------------------------------ %

sum(a.tch_norm_seiz) ;normal new calls


- sum(a.tch_succ_seiz_for_dir_acc); direct access related correction



a = p_nbsc_traffic

b = p_nbsc_service

c = p_nbsc_ho

Call success ratio

100* csf_1a/100 * csf_2xx/100 * csf_3l/100 * csf_4v/100

CSF_2h


=100* ------------------------------------------------------------------------- %



- sum(a.tch_call_req-a.tch_norm_seiz

-c.msc_o_sdcch_tch - c.bsc_o_sdcch_tch - c.cell_sdcch_tch) ;blocked

+ sum(a.tch_succ_seiz_for_dir_acc); direct access related correction









OR

good:>99,5%

(good:>99,9%)



SDCCH TCH

Author: J.Neva 8/97

Version: 1.7 8.12.99


csf_2a: good:> 98% (best seen: 98,9%)


http://nea.ntc.nokia.com/formula.php?ne=BSC&formula_id=uav_14csf_2b




http://nea.ntc.nokia.com/formula.php?ne=BSC&formula_id=uav_14csf_4v



http://nea.ntc.nokia.com/formula.php?ne=BSC&formula_id=uav_14csf_2h


CSF_3l








100- 100* ---------------------------------------------------- %

sum(a.tch_call_req)





a = p_nbsc_traffic

b = p_nbsc_handover

Call Success Factors, S7 (BTS)

SDCCH success

ratio

CSF_2xx

SDCCH access

probability

CSF_1a

TCH access

probability

CSF_3l

TCH success

ratio

CSF_4x

CSF_2a




100- 100*----------------------------------------------------------------- %




Note: 1) Experience has shown that A-if blocking is NOT included.


CSF_4x






100 -100* ------------------------------------------------------------------------------ %







a = p_nbsc_traffic

b = p_nbsc_service

c = p_nbsc_ho

Call success ratio

100* csf_1a/100 * csf_2xx/100 * csf_3d/100 * csf_4x/100

CSF_2i


=100* -------------------------------------------------------------------- %






-c.msc_o_sdcch - c.bsc_o_sdcch) ;(unknown how big part is calls

- c.cell_sdcch_tch










OR

CSF_1a


100-(100* ----------------------------------------) %

SDCCH_seiz_att

All counters from p_nbsc_traffic. Author: J.Neva 4/97

Version: 1.4 31.3.99


SDCCH TCH




http://nea.ntc.nokia.com/formula.php?ne=BSC&formula_id=uav_14csf_4x





SDCCH success

ratio

CSF_2xx

SDCCH access

probability

CSF_1a

TCH access

probability

CSF_3l

TCH success

ratio

CSF_4v

CSF_1a


100-(100* ----------------------------------------) %

SDCCH_seiz_att


CSF_2b

sum(SDCCH_RADIO_FAIL+SDCCH_RF_OLD_HO+SDCCH_USER_ACT+SDCCH_BCSU_RESET

+SDCCH_NETW_ACT +SDCCH_BTS_FAIL+SDCCH_LAPD_FAIL

+SDCCH_A_IF_FAIL_CALL+SDCCH_A_IF_FAIL_OLD+SDCCH_ABIS_FAIL_OLD)

100- 100*----------------------------------------------------------------- %

sum(b.succ_seiz_term+b.succ_seiz_orig+b.sdcch_emerg_call

+b.sdcch_call_re_est-b.succ_sdcch_sms_est- b.unsucc_sdcch_sms_est)


a= p_nbsc_traffic table, b= p_nbsc_res_access, c= p_nbsc_ho



CSF_3l =100-blck_8c



+ sum(a.tch_succ_seiz_for_dir_acc) ; DAC correction





100- 100* ---------------------------------------------------- %

sum(a.tch_call_req)





a = p_nbsc_traffic

b = p_nbsc_handover

CSF_4v = 100-dcr_3j






100 -100* ------------------------------------------------------------------------------ %



- sum(a.tch_succ_seiz_for_dir_acc);DAC correction



a = p_nbsc_traffic

b = p_nbsc_service

c = p_nbsc_ho

Call success ratio

100* csf_1a/100 * csf_2xx/100 * csf_3n/100 * csf_4z/100

CSF_2h


=100* ------------------------------------------------------------------------- %














OR

good:>99,5%

(good:>99,9%)



SDCCH TCH

Author: J.Neva

Version: 1.8 29.3.2000

PMWG review.: 1.8 29.3.2000

csf_2a: good:> 98% (best seen: 98,9%)


http://nea.ntc.nokia.com/formula.php?ne=BSC&formula_id=uav_14csf_2b







http://nea.ntc.nokia.com/formula.php?ne=BSC&formula_id=uav_14csf_2h



SDCCH success

ratio

CSF_2xx

SDCCH access

probability

CSF_1a

TCH access

probability

CSF_3l

TCH success

ratio

CSF_4v

CSF_1a


100-(100* ----------------------------------------) %

SDCCH_seiz_att


CSF_3l =100-blck_8c








100- 100* ---------------------------------------------------- %

sum(a.tch_call_req)





a = p_nbsc_traffic

b = p_nbsc_handover

CSF_4v = 100-dcr_3j






100 -100* ------------------------------------------------------------------------------ %






a = p_nbsc_traffic

b = p_nbsc_service

c = p_nbsc_ho

Call success ratio


CSF_2j


=100* ------------------------------------------------------------------------- %






- succ_seiz_supplem_serv ; supplem.serv.requests (S9)








OR

good:>99,5%

(good:>99,9%)



SDCCH TCH

Author: J.Neva

Version: 1.3 27.11.2001

PMWG review.:

csf_2c: good:> 98

CSF_2e

sum(a.sdcch_radio_fail+a.sdcch_rf_old_ho+ a.sdcch_user_act

+a.sdcch_bcsu_reset

+ sdcch_netw_act + a.sdcch_bts_fail+ a.sdcch_lapd_fail

+ a.sdcch_a_if_fail_call + a.sdcch_a_if_fail_old+ a.sdcch_abis_fail_old

+ (a.sdcch_abis_fail_call- C))

100- 100*---------------------------------------------------------------------- %

sum(b.succ_seiz_term+b.succ_seiz_orig+b.sdcch_call_re_est

+b.sdcch_loc_upd+b.imsi_detach_sdcch+b.sdcch_emerg_call

C= part of sdcch_abis_fail_call that happens before establishment indication =

a.sdcch_assign- (b.succ_seiz_term+b.succ_seiz_orig+b.sdcch_call_re_est

+b.sdcch_loc_upd+b.imsi_detach_sdcch+b.sdcch_emerg_call)

Counters from table(s):

a = p_nbsc_traffic


c = p_nbsc_ho









http://nea.ntc.nokia.com/formula.php?ne=BSC&formula_id=uav_14csf_2e


Call Success Factors, S8-9-> (BTS)

SDCCH success

ratio

CSF_2xx

SDCCH access

probability

CSF_1a

TCH access

probability

CSF_3l

TCH success

ratio

CSF_4w

CSF_4x






100 -100* ------------------------------------------------------------------------------ %



- sum(a.tch_succ_seiz_for_dir_acc); DAC correction




a = p_nbsc_traffic

b = p_nbsc_service

c = p_nbsc_ho

Call success ratio

100* csf_1a/100 * csf_2xx/100 * csf_3n/100 * csf_4w/100

CSF_2i


=100* -------------------------------------------------------------------- %






-c.msc_o_sdcch - c.bsc_o_sdcch) ;(unknown how big part is calls

- c.cell_sdcch_tch










OR

CSF_1a


100-(100* ----------------------------------------) %

SDCCH_seiz_att

All counters from p_nbsc_traffic. Author: J.Neva

Version: 1.7 27.11.2001

PMWG review.: 1.5 29.3.2000

SDCCH TCH

CSF_3l =100-blck_8c








100- 100* ---------------------------------------------------- %

sum(a.tch_call_req)





a = p_nbsc_traffic

b = p_nbsc_handover

CSF_2l


+a.sdcch_bcsu_reset



+ (a.sdcch_abis_fail_call- C)) 100- 100*---------------------------------------------------------------------- %



/* successful incoming intercell SDCCH-SDCCH HOs */


C= part of sdcch_abis_fail_call that happens before establishment indication = a.sdcch_assign- (b.succ_seiz_term+b.succ_seiz_orig+b.sdcch_call_re_est



a = p_nbsc_traffic


c = p_nbsc_ho









Call Success Factors , S10.5 (area)

SDCCH success

ratio

CSF_2xx

SDCCH access

probability

CSF_1a

TCH access

probability

CSF_3l

TCH success

ratio

CSF_4v

CSF_1a


100-(100* ----------------------------------------) %

SDCCH_seiz_att


CSF_3l =100-blck_8c








100- 100* ---------------------------------------------------- %

sum(a.tch_call_req)





a = p_nbsc_traffic

b = p_nbsc_handover

CSF_4v = 100-dcr_3j






100 -100* ------------------------------------------------------------------------------ %






a = p_nbsc_traffic

b = p_nbsc_service

c = p_nbsc_ho

Call success ratio


CSF_2m


=100* ------------------------------------------------------------------------- %


+b.call_assign_after_sms-b.succ_sdcch_sms_est- b.unsucc_sdcch_sms_est)




- succ_seiz_supplem_serv ; supplem.serv.requests (S9)








OR

good:>99,5%

(good:>99,9%)



SDCCH TCH

Author: J.Neva

Version: 1.0 2.1.2003

PMWG review.:

csf_2c: good:> 98

CSF_2e


+a.sdcch_bcsu_reset



+ (a.sdcch_abis_fail_call- C))

100- 100*---------------------------------------------------------------------- %


+b.sdcch_loc_upd+b.imsi_detach_sdcch+b.sdcch_emerg_call

C= part of sdcch_abis_fail_call that happens before establishment indication =

a.sdcch_assign- (b.succ_seiz_term+b.succ_seiz_orig+b.sdcch_call_re_est



a = p_nbsc_traffic


c = p_nbsc_ho









http://nea.ntc.nokia.com/formula.php?ne=BSC&formula_id=uav_14csf_2e


Call Success Factors, S10.5 (BTS)

SDCCH success

ratio

CSF_2xx

SDCCH access

probability

CSF_1a

TCH access

probability

CSF_3l

TCH success

ratio

CSF_4w

CSF_4x






100 -100* ------------------------------------------------------------------------------ %



- sum(a.tch_succ_seiz_for_dir_acc); DAC correction




a = p_nbsc_traffic

b = p_nbsc_service

c = p_nbsc_ho

Call success ratio

100* csf_1a/100 * csf_2xx/100 * csf_3n/100 * csf_4w/100

CSF_2n


=100* -------------------------------------------------------------------- %

sum(b.succ_seiz_term+b.succ_seiz_orig +b.sdcch_call_re_est

+b.sdcch_emerg_call+b.call_assign_after_sms)

;(calls,sms, ss reqs)




-c.msc_o_sdcch - c.bsc_o_sdcch) ;(unknown how big part calls

- sum(c.cell_sdcch_tch)



- sum(b.succ_seiz_supplem_serv) ;supplem.serv. requests (S9)







OR

CSF_1a


100-(100* ----------------------------------------) %

SDCCH_seiz_att

All counters from p_nbsc_traffic. Author: J.Neva

Version: 1.0 2.1.2003

PMWG review.:

SDCCH TCH

CSF_3l =100-blck_8c








100- 100* ---------------------------------------------------- %

sum(a.tch_call_req)





a = p_nbsc_traffic

b = p_nbsc_handover

CSF_2l


+a.sdcch_bcsu_reset



+ (a.sdcch_abis_fail_call- C)) 100- 100*---------------------------------------------------------------------- %



/* successful incoming intercell SDCCH-SDCCH HOs */


C= part of sdcch_abis_fail_call that happens before establishment indication = a.sdcch_assign- (b.succ_seiz_term+b.succ_seiz_orig+b.sdcch_call_re_est



a = p_nbsc_traffic


c = p_nbsc_ho


http://nea.ntc.nokia.com/formula.php?ne=BSC&formula_id=uav_14csf_2n







TCH ACCESS PROBABILITY, BEFORE DR, (CSF_3i)

sum(a.tch_call_req - a.tch_norm_seiz)





100-100* ------------------------------------- %

sum(a.tch_call_req)





a = p_nbsc_traffic , b = p_nbsc_ho

TCH ACCESS PROBABILITY, REAL, (CSF_3l)

sum(a.tch_call_req-a.tch_norm_seiz);calls that could be blocked







;calls that are saved by DR

100- 100* -------------------------------------------- %

sum(a.tch_call_req)





a = p_nbsc_traffic, b = p_nbsc_ho

Call Success Factors (area), TCH access, S7 Author: J.Neva 4/97

Version: 1.5

PMWG review.: 1.5 19.8.1999

TCH ACCESS PROBABILITY, BEFORE DR&Q, (CSF_3j)


+ sum(a.tch_qd_call_att - XX1 -a.unsrv_qd_call_att);calls that succeeded via queuing





100-100*------------------------------------------- %

sum(a.tch_call_req)





a = p_nbsc_traffic, b=p_nbsc_ho, XX1=attempts taken from queue to DR (unknown)

TCH ACCESS

tue

sun fri

wed

mo

n

sat

thu

tue

sun fri

wed

mo

n

S1

S395,50

96,00

96,50

97,00

97,50

98,00

98,50

99,00

99,50

100,00

Series1

Series2

Series3

Queuing and DR work in parallel. Call is taken out from que of cell A

when the cell list is created and HO is attempted to cell B.

This means that the HO still may fail after call is taken out from queue.

If queuing is succeeded then DR is not tried.

Note error due to XX1!!





TCH ACCESS PROBABILITY, BEFORE DR&Q, (CSF_3m)


+ sum(a.tch_qd_call_att - a.removal_from_que_to_dr -a.unsrv_qd_call_att)

;calls that succeeded via queuing





100-100*------------------------------------------- %

sum(a.tch_call_req)





a = p_nbsc_traffic, b=p_nbsc_ho,

TCH ACCESS PROBABILITY, BEFORE DR, (CSF_3i)






100-100* ------------------------------------- %

sum(a.tch_call_req)





a = p_nbsc_traffic , b = p_nbsc_ho

TCH ACCESS PROBABILITY, REAL, (CSF_3l)

sum(a.tch_call_req-a.tch_norm_seiz);calls that could be blocked







;calls that are saved by DR

100- 100* -------------------------------------------- %

sum(a.tch_call_req)





a = p_nbsc_traffic, b = p_nbsc_ho

Call Success Factors (area), TCH access, S8-9 Author: J.Neva

Version: 1.0

PMWG review.: OPEN

TCH ACCESS

tue

sun fri

wed

mo

n

sat

thu

tue

sun fri

wed

mo

n

S1

S395,50

96,00

96,50

97,00

97,50

98,00

98,50

99,00

99,50

100,00

Series1

Series2

Series3

Queuing and DR work in parallel. Call is taken out from que of cell A

when the cell list is created and HO is attempted to cell B.

This means that the HO still may fail after call is taken out from queue.

If queuing is succeeded then DR is not tried.





Call Success Factors (area), TCH success, S8-9 Author: J.Neva 4/97

Version: 1.0


TCH SUCCESS RATIO, REAL (CSF_4p)





- sum(b.sdcch_re_est_assign + b.tch_re_est_assign) ;(call re-establishments)

100 -100* ------------------------------------------------------------------------------ %





- sum(b.sdcch_re_est_assign + b.tch_re_est_assign) ;call re-establishments


TCH SUCCESS RATIO, REAL (CSF_4u)





100 -100* ------------------------------------------------------------------------------ %


+ sum(c.msc_i_sdcch_tch+c.bsc_i_sdcch_tch +c.cell_sdcch_tch +c.cell_sdcch_tch)

;(DR calls)

- sum(a.tch_succ_seiz_for_dir_acc);

+ sum(a.tch_seiz_due_sdcch_con) ; FACCH call setup calls

a = p_nbsc_traffic, c = p_nbsc_ho

Improvement by


TCH SUCCESS (S6/T10)

94,00

94,50

95,00

95,50

96,00

96,50

97,00

97,50

98,00

98,50

99,00

tue

sun fri

wed

mo

n

sat

thu

tue

sun fri

wed

mo

nSeries1

Series2

CSF_4v






100 -100* ------------------------------------------------------------------------------ %






a = p_nbsc_traffic

b = p_nbsc_service

c = p_nbsc_ho

Improvement by


TCH SUCCESS (S7-S9/T11)

TCH SUCCESS RATIO, REAL (CSF_4o)





100 -100* ------------------------------------------------------------------------------ %


+ sum(c.msc_i_sdcch_tch+c.bsc_i_sdcch_tch +c.cell_sdcch_tch +c.cell_sdcch_tch)

;(DR calls)

+ sum(a.tch_seiz_due_sdcch_con) ; FACCH call setup calls

a = p_nbsc_traffic,c = p_nbsc_ho

../../../NEVA_PRV/JNE_DOCS/jne701.ppt





Call Success Factors (area), SDCCH access Author: J.Neva 6/97

Version: 1.3 12.10.00

PMWG review.: 1.3 12.10.00

SDCCH ACCESS PROBABILITY, AFTER DYNAMIC SDCCH ALLOCATION,(CSF_1)

SDCCH_busy_att

100*(1- --------------) %

SDCCH_seiz_att

a = p_nbsc_traffic

SDCCH ACCESS PROBABILITY, BEFORE DYNAMIC SDCCH ALLOCATION, (CSF_1)

SDCCH_busy_att

100*(1- --------------) %

SDCCH_seiz_att

a = p_nbsc_traffic

SDCCH ACCESS

Improvement by

Dynamic SDCCH

Allocation

This is smaller

after Dynamic

SDCCH Conf.

Feature (S7) is

activated !

Counters for

Dynamic SDCCH

Allocation

SUCCESS

UNSUCC

DYNAMIC SDCCH

RECONF ATTEMPT

/c1154 (S7)

dyn_sdcch_reconf_att

SDCCH ACCESS PROBABILITY, BEFORE FACCH call setup, (CSF_1)

SDCCH_busy_att

100*(1- --------------) %

SDCCH_seiz_att

a = p_nbsc_traffic

SDCCH ACCESS PROBABILITY, AFTER FACCH call setup, (CSF_1a)

SDCCH_busy_att- tch_seiz_due_sdcch_con

100-(100* ----------------------------------------) %

SDCCH_seiz_att

a = p_nbsc_traffic

Improvement by

FACCH call setup

SDCCH ACCESS

UNSUCC IMM ASSIGN

SDCCH ATTEMPT

/c1155 (S7)

SDCCH_UNSUCC_IMM_

ASSIGN_ATT


http://nea.ntc.nokia.com/formula.php?ne=BSC&formula_id=uav_14csf_1




Conversation Success (area)

SDCCH success SDCCH access

TCH access TCH success

SDCCH

TCH

Cell A

TCH access TCH success

TCH Cell B

Handover

(connect_ack message)

conversation_started

dropped_call

Dropped conversation ratio

dcr_5a

sum(b.dropped_calls)

100* -------------------------------------------------- %

sum(b.conver_started) - sum(a.msc_i_tch_tch)

a = p_nbsc_ho, b = p_nbsc_service

Author: J.Neva 6/97

Version: 1.1 27.1.98


triggered when call started

triggered if inter BSC HO Drop call

Note: applicable on large area where

no MSC controlled HOs over areal border.

NOT applicable on BTS level.

Note: not triggered in call re-establishment

http://nea.ntc.nokia.com/formula.php?ne=BSC&formula_id=uav_14dcr_5a


High Speed Circuit Swithed Data (S7 option BSS7003)

SDCCH

REQUESTS

/c1000 (S1)

sdcch_seiz_at

t

SEIZURES FOR

CALLS , LU s AND

IMSI DETACHES

/c1007 (S1)

sdcch_assign

MOC (incl.SMS)

/c3013 (S1)

succ_seiz_orig

MTC (incl.SMS)

/c3012 (S1)

succ_seiz_term




PMWG appr.: 1.0 3.2.2000

TCH Request

SDCCH

HSCSD_REQ_CALL_SETUP

/c1160 (S7)

TCH

HSCSD_TCH_SUCC_SEIZ_CA

LL_SETUP

/c1162 (S7)

Assignment Request message received to

the BSC from the MSC

Non transp. TCH succ. seizures

/xx

HSCSD_TRANSP_TCH_SUCC_SEIZ

/c1159 (S7)

OR OR

HSCSD_TRANSP_TCH_REQ

/c1158 (S7)

HSCSD_CON_REL_DUE_FAIL

/c1164 conversation

Non transp. TCH requests

/xx











HSCSD: Intra cell HO (S7 option BSS7003)


Version: 1.0

PMWG appr.: 1.0 3.2.2000

INTRA_ATT_HSCSD

/c4124 (S7)

SOURCE

INTRA_SUCC_HSCSD

/c4125 (S7)

CELL_SUCC_HO

/c4018 (S1) INTRA_SUCC_DEC_HSCSD

/c4127 (S7)

INTRA_SUCC_INC_HSCSD

/c4126 (S7)

If Upgrade (increment)

or Downgrade (decrease)

HSCSD_TCH_REQ_HO

/c1161 (S7)

HSCSD_TCH_SUCC_SEIZ_HO

/c1163 (S7)

OR









HSCSD: Inter cell HO (S7 option BSS7003)


Version: 1.0

PMWG appr.: 1.0 3.2.2000

TARGET

BSC_I_ATT_HSCSD

/c4120 (S7)

BSC_O_ATT_HSCSD

/c4118 (S7)

SOURCE

BSC_O_SUCC_HO

/c4014 (S1)

BSC_O_SUCC_HSCSD

/c4119 (S7)

BSC_I_SUCC_HO

/c4010 (S1)

BSC_I_SUCC_HSCSD

/c4121 (S7)

IBSC_I_SUCC_DEC_HSCSD

/c4123 (S7)

BSC_I_SUCC_INC_HSCSD

/c4122 (S7)

BSC Inter Cell Handover

HSCSD_TCH_REQ_HO

/c1161 (S7) HSCSD_TCH_SUCC_SEIZ_HO

/c1163 (S7)

OR

















HSCSD: Inter BSC HO (S7 option BSS7003)


Version: 1.0

PMWG appr.: 1.0 3.2.2000

TARGET

MSC_I_ATT_HSCSD

/c4114 (S7)

MSC_O_ATT_HSCSD

/c4112 (S7)

SOURCE

MSC_O_SUCC_HO

/c4004 (S1)

MSC_O_SUCC_HSCSD

/c4113 (S7)

MSC_I_SUCC_HO

/c4000 (S1)

MSC_I_SUCC_HSCSD

/c4115 (S7)

MSC_I_SUCC_DEC_HSCSD

/c4117 (S7)

MSC_I_SUCC_INC _HSCSD

/c4116 (S7)

External Handover

HSCSD_TCH_REQ_HO

/c1161 (S7) HSCSD_TCH_SUCC_SEIZ_HO

/c1163 (S7)

OR



















HSCSD: BSC clear codes (S7 option BSS7003)

Author: J.Neva 16.5.2000

Version: 1.0

PMWG appr.:

DOWNGRADES

downgrade_with_hscsd

/c500361 (S7)

HO NOT STARTED

ho_not_started

/c500362 (S7)

CONFIGURATION CHANGE NOT ALLOWED

conf_change_not_allowed

/c500363 (S7)

CONFIGURATION CHANGE FAILED DUE TO BTS

conf_change_BTS_fail

/c500364 (S7)

CONFIGURATION CHANGE FAILED DUE TO MS

conf_change_MS_fail

/c500365 (S7)

CHANNEL REALEASE DUE TO OTHER CHN.FAILURE

HSCSD_copro_fail

/c500366 (S7)

TIMER EXPIRED DUE TO SUBCHN.NOT RESPONDING

sub_timer

/c500367 (S7)

NUMBER OF BLOCKED TCH AFTER FORCED HO

forced_ho_block

/c500368 (S7)

UPGRADE FAILED

upgrade_fail

/c500369 (S7)

REQUESTS NOT SUPPORTED BY BTS

rrm_bts_not_supporting

/c500403 (S7)

REQUESTS NOT SUPPORTED BY BTS

rrm_ms_not_supporting

/c500404 (S7)
























HSCSD: Coding (S7 option BSS7003)


Version: 1.0

PMWG appr.:

one_tch_req_hscsd

/c67000 (S7)

two_tch_req_hscsd

/c67001 (S7)

three_tch_req_hscsd

/c67002 (S7)

four_tch_req_hscsd

/c67003 (S7)

one_tch_seiz_hscsd

/c67004 (S7)

two_tch_seiz_hscsd

/c67005 (S7)

three_tch_seiz_hscsd

/c67006 (S7)

four_tch_seiz_hscsd

/c67007 (S7)

one_tch_req_time_14400

/c67009 (S7)

two_tch_req_time_14400

/c67010 (S7)

three_tch_req_time_14400

/c67011 (S7)

four_tch_req_time_14400

/c67012 (S7)

one_tch_seiz_time_14400

/c67013 (S7)

two_tch_seiz_time_14400

/c67014 (S7)

three_tch_seiz_time_14400

/c67015 (S7)

four_tch_seiz_time_14400

/c67016 (S7)

one_tch_req_time_9600

/c67017 (S7)

two_tch_req_time_9600

/c67018 (S7)

three_tch_req_time_9600

/c67019 (S7)

four_tch_req_time_9600

/c67020 (S7)

one_tch_seiz_time_9600

/c67021 (S7)

two_tch_seiz_time_9600

/c67022 (S7)

three_tch_seiz_time_9600

/c67023 (S7)

four_tch_seiz_time_9600

/c67024 (S7)

ala_from_14400_to_9600

/c67031 (S7)

ala_from_9600_to_ 14400

/c67032 (S7)

multi_tch_req_rej_hscsd

/c67008 (S7)
























































HSCSD: Other counters (S7 option BSS7003)


Version: 1.0

PMWG appr.:

PEAK BUSY TCH FOR HSCSD

peak_busy_hscsd

/c2056 (S7)

AVERAGE TCH HOLDING TIME FOR HSCSD

trf_58 (S7)

AVERAGE BUSY TCH FOR HSCSD

trf_59 (S7)

AVERAGE NBR OF HSCSD USERS

trf_60 (S7) TOTAL HSCSD CALL TIME ON TCH

trf_61 (S7)

AVERAGE UPGRADE PENDING TIME

trf_62 (S7)

14.4 DATA POWER INCREASE DUE TO DL QUALITY

bs_pwr_inc_qual_14400

/c5033 (S7)

tch_seiz_in_upgrade

/c67025 (S7)

tch_rel_due_unsucc_upgrade

/c67026 (S7)

tch_seiz_in_downgrade

/c67027 (S7)

tch_rel_due_succ_downgrade

/c67028 (S7)

req_pended_slots_in_upgrade

/c67029 (S7)

served_pended_slots_in_upgrade

/c67030 (S7)

AVERAGE PENDING TIME DUE TO

CONGESTION

trf_63 (S7)
























Dynamic SDCCH allocation (S7 option BSS7036)

ASSIGNMENTS FOR

CALLS,LU,SS

/c1007 sdcch_assign

/c57019 served_sdcch_req


Version: 1.2 17.1.2002

PMWG appr.: 17.1.2002

TCH TCH TCH TCH TCH TCH TCH TCH

SDCCH /8

TCH TCH TCH TCH TCH TCH TCH

Reconfiguration attempt

from TCH to SDCCH

DYNAMIC SDCCH

RECONF ATTEMPT

/c1154 (S7)

dyn_sdcch_reconf_att

UNSUCC IMM ASSIGN

SDCCH ATTEMPT

/c1155 (S7)

unsucc_imm_ass_sdcch_att

SDCCH BUSY ATTEMPT

/c1001

sdcch_busy_att

TCH TCH TCH TCH TCH TCH TCH TCH

SDCCH /8

TCH TCH TCH TCH TCH TCH TCH

• When SDDCH/8 is not needed anymore it is changed dynamically back to TCH

TCH

FAILS NONE OF COUNTER IS

UPDATED !!!

FACCH Call Setup

•In case of the congestion in SDCCH, one free traffic channel can be allocated dynamically to SDCCH/8

•max. 2 TCH can be allocated to SDCCH if 64kbps TRX signaling used (for 16kbps max. is 12SDCCH)

•In IUO case, SDCCH/8 from the regular TRX

•FACCH call setup is used only in true SDCCH congestion, when no more dynamic SDCCH possible to be configured

RACH on CCCH

/c3004

ch_req_msg_rec

SDCCH REQUESTS

/c1000 sdcch_seiz_att

/c57017 sdcch_req

Feature activation on

BSC level.










Interference counters Author: J.Neva 3.3.99

Version: 1.1 6.5.99

PMWG review: 1.0 9.3.99

DOCUMENTTYPE 1 (1)

TypeUnitOrDepartmentHereTypeYourNameHere TypeDateHere

------------------ boundary 0 (value fixed: -110dBm)

band 1 (FTCH 1)

------------------ boundary 1 (value eg.: -105dBm, critical for the report)

band 2 (FTCH 2)

------------------ boundary 2 (value e.g.: -100dBm)

band 3 (FTCH 3)


band 4 (FTCH 4)


band 5 (FTCH 5)

------------------ boundary 5 (value fixed: -47dBm)

BTS level TRX level

• BTS sends interference value 0..4

• BSC sums the values per TRX

• Each idle FTCH is sampled for level

• average nbr of idle FTCH is counted for each band

• Boundaries can be set as cell parameters

• Note: Mast Head Amplifier for 1800 and 1900 networks brings constant 12dB gain. MHA for GSM has adjustable gain.

Avg nbr of idle FTCH in band 1 /c2006/c2007

ave_idle_f_tch_1/res_av_denom4







Avg interference band sum

/c5027 (S6)

ave_sum_idle_ch_interf


ave_idle_f_tch_5/res_av_denom8 Avg interference band samples c5029 (S6)

ave_sum_idle_tch_per_trx

Avg nbr of idle HTCH in band 1 /c2016/c2017

ave_idle_h_tch_1/res_av_denom9






ave_idle_h_tch_3/res_av_deno11



• ‘itf_1 UL interference’ for FTCH

• ‘itf_x UL interference’ for HTCH
























Interference formulas Author: J.Neva 3.3.99

Version: 1.0


BTS level TRX level

Idle FTCH time out from band 1

itf_1

sum(ave_idle_f_tch_1)/sum(res_av_denom4)

1- ---------------------------------------------------------------- %

sum(ave_idle_f_tch_1)/sum(res_av_denom4)

+ sum(ave_idle_f_tch_2)/sum(res_av_denom5)

+sum(ave_idle_f_tch_3)/sum(res_av_denom6)



Avg interference band

itf_4

sum(ave_sum_idle_ch_interf)

--------------------------- + 1

ave_sum_idle_tch_per_trx

Idle HTCH time out from band 1

itf_x

sum(ave_idle_h_tch_1)/sum(res_av_denom9)

1- ---------------------------------------------------------------- %

sum(ave_idle_h_tch_1)/sum(res_av_denom9)

+ sum(ave_idle_h_tch_2)/sum(res_av_denom10)

+sum(ave_idle_h_tch_3)/sum(res_av_denom11)



New formula itf_x needed!!

http://nea.ntc.nokia.com/formula.php?ne=BSC&formula_id=uav_14itf_1




Power & Level (SDCCH,TCH) Author: J.Neva 10/2001

Version: 0.1

PMWG review:

TRX level

MS max pwr 43 dBm (GSM900)

30 dBm (GSM1800,1900)

BS power attenuation (dB) Lb_12 2*sum(ave_BS_power)/sum(power_denom2)

UL Signal strength (dBm)

Lb_9 sum(ave_ul_sig_str)/sum(power_denom4)

DL Signal strength (dBm)

Lb_10 sum(ave_dl_sig_str)/sum(power_denom3)

Measurements are received from BTS in every SACCH frame (0,48s).

BSC samples the values from the latest measurements every 20s (set by a parameter in UTPFIL)

BSC ignores values >= 29 (denom not incremented).

Signal strength values as defined by GSM 5.08

(0..63: 0 =less than -110dBm,

1= -110 to -109 dBm,

3= -109 to -108dBm ...

62 = -49 to -48,

63=greater than -48).

MS power attenuation (dB) Lb_11 2*sum(ave_MS_power)/sum(power_denom1) - = MS Power level (pwr_1b)

BS max pwr TRX dependent - = BS Power level (pwr_2)

Average link balance (lb_13) =

2*sum(ave_BS_power)/sum(power_denom2)+sum(ave_dl_sig_str)/sum(power_denom3)

-2*sum(ave_MS_power)/sum(power_denom1)-sum(ave_ul_sig_str)/sum(power_denom4)

MS reported value ranges:

0-19 in GSM900

29-31,0-15 in GSM1800

30-31,0-15 in GSM1900

http://nea.ntc.nokia.com/formula.php?ne=BSC&formula_id=uav_14lb_12






Quality Author: J.Neva 3.10.98

Version: 1.1

PMWG review: 1.0. 12.10.98

UL and DL are sampled every 480ms.

Every sample is ranked to a quality class:

Class corresponds to BER:

Class BER (GSM 05.08)

***** ******************

qua 0 (BER < 0.2%)

qua 1 (BER 0.2 - 0.4%)

qua 2 (BER 0.4 - 0.8%)

qua 3 (BER 0.8 - 1.6%)

qua 4 (BER 1.6 - 3.2%)

qua 5 (BER 3.2 - 6.4%)

qua 6 (BER 6.4 - 12.8%)

qua 7 (BER >12.8%) slightly

degradiated

Good

degradiated

useless Results are available per TRX in

p_nbsc_rx_qual or p_nbsc_rx_statistics.

Impact of UL DTX:

An investigation showed that UL DTX makes UL quality to show worse.

The impact was about one 1% unit (1% of samples more in classes 6 and 7).

When investigated with field tests no real degradiation of quality could be found.

The BER reported by the mobiles is the figure measured

before the decoding process, whereas the FER is associated

with the corrected BER after the decoder.


Quality formulas Author: J.Neva 0.1.3.3.99

Version: 1.0


Counters fromp_nbsc_rx_quality or p_nbsc_rx_statistics.

Cumulative quality, UL, classes 0..X (X<=7)

sum(freq_ul_qual0 + … + freq_ul_qualX)

100 * -------------------------------------- %

sum(freq_ul_qual0 + … + freq_ul_qual7)

Cumulative quality, DL, classes 0..X (X<=7)

sum(freq_dl_qual0 + … + freq_dl_qualX)

100 * -------------------------------------- %

sum(freq_dl_qual0 + … + freq_dl_qual7)

Calls on TCH are sampled every 0.48sec.

Total nbr of samples

Total nbr of samples


FH effect on quality Author: 5/98

Version: 1.1

PMWG appr.: 1.1 1.7.98

Quality classes evolution with FH

0 %

100 %

10 32 54 76

Not hopping

Hopping with 2-3 TRX/cell

Hopping with 4 or + TRX/cell

Note: TRX numbers for BB FH only. In RF FH case the TRX numbers = MA list lenghts.

This picture is a rough example of the trend and should not be shown to customers as

an offical statement.

Note that

- classes 0-5 do not cause audible problems

- BER is not good for measuring audio quality. FER would be better but is not available

Experiments in hopping network have shown that even if quality 5-6 share (BER) increased

FER did not, i.e. MS user perceived quality is not worse. The advantage comes in that the

speech coder works much better

under the single burst errors you

get with hopping.

With more freqs these get spaced

enough that the coding can handle

all the errors.

However, more TRXs (or frequencies)

in a hopping sequence usually

means the reuse has got tighter

and soon this will start to introduce

more errors than you are saving.


High speed data S7

See new document:

High Speed Circuit Switched Data

Key Performance Indicators

http://wwwalltr.ntc.nokia.com/BSC/ORG/BSCTRE/DMSME/HSCSDKPI.DOC

http://wwwalltr.ntc.nokia.com/BSC/ORG/BSCTRE/DMSME/document.htm


Trunk reservation

See description:

TCH service request

001010 TCH REQUEST SUCCESS AND UNSUCCESS

TR in use Yes

TCH found

No

Yes

No

TR refuse

No

001008 SUCCESS TCH SEIZURE FOR HO 001009 SUCCESS TCH SEIZURE FOR NORMAL ASSIGNMENT

Yes

001011 TCH REQUEST REJECTED DUE TO LACK

Author: J.Kaasalainen 8/1999

Version: 1.0

PMWG appr.: 1.0 27.11.00

Trunk reservation invocation

trunk_res_invoc

/c1040

Trunk reserv. invocation refused

trunk_res_invoc_refused

/c1042

Trunk reserv. invocation succesful

trunk_res_invoc_succ

/c1041

Only inter-cell HO.

Improved Trunk Reservation Option

=================================

BSC

Assignment/Handover Request

Priority Level (PR) : Subscriber Type

1 : GSM

2 : GSM

3 : GSM

4 : GSM

5 : GSM

6 : GSM

7 : GSM

8 : GSM

9 : GSM

10 : GSM

11 : GSM

12 : GSM

13 : GSM

14 : GSM

BTS

Trunk Res. Algorithm Used (TR): No

Limit for Free TCHs (LIMIT): 10

Reservation Method (REM): Dynamic

Table Id. for GSM Call Setup (TBL): 0

Table Id. for MCN Call Setup (TBL): 0

Table Id. for GSM Handover (TBL): 0

Table Id. for MCN Handover (TBL): 0

Table Id. for Priority Call Setup (TBL): 0

Table Id. for Priority Handover (TBL): 0

Note: Trunk tables are managed in BSC.

BSS5190

http://essrv509ntc.ntc.nokia.com/dynaweb/NED31_bsc_s7e/8070271/@Generic__BookView;pt=26211?DwebQuery=trunk+reservation





Dynamic Hot Spot S8

TCH SUCC SEIZURES WHEN GOOD

QUALITY IN ADJACENT CELLS

/c1150 (S8)

tch_succ_seiz_good_qual_adj

REJECTED TCH REQUESTS WHEN BAD


/c1151 (S8)

tch_req_rej_bad_qual_adj

TCH SUCC SEIZURES WHEN QUALITY IN

ADJACENT CELLS BETWEEN GOOD AND

BAD

/c1152 (S8)

tch_succ_seiz_betw_qual_adj

REJECTED TCH REQUESTS WHEN


BETWEEN GOOD AND BAD

/c1153 (S8)

tch_req_rej_betw_qual_adj

Feature BSS7019


Version: 1.0 4.1.2000

PMWG appr.: 1.0 4.1.2000

Soft Blocking Start Reg 0..255

Interference level of ANY adj.cell >= Bad Qual Limit 0..100 % TCH can not be seized due to interference on one or more adj.cells.

Interference level of ALL adj.cells < Good Qual Limit 0..100 % TCH can be seized without disturbing any of the adj.cells.

Soft Blocking Start Sup 0..255

Traffic intensity threshold (nbr of seized time slots) If exceeded the interference level of all adjacent cells is calculated (DHS algorithm activated).

Ref: DHS support in NPS/x. Feasibility study. Capacity solutions in Nokia BSS.

NOTE: - DHS is used only in FH networks - in Rf-hopping does not affect BCCH TRX - does not need IUO

For each adj. cell that has (Good Qual Limit < interference level < Bad Qual Limit) a TCH seizure probability is calculated in the following way: Good Qual Limit <= interference < Sig Qual Limit 2 probability =TCH Probability 3 Sig Qual Limit 2 < = interference < Sig Qual Limit 1 probability = TCH Probability 2 Sig Qual Limit 1 < =interference < Bad Qual Limit probability = TCH Probability 1

Probabilities of all cells multiplied together > 50

Probabilities of all cells multiplied together = < 50





http://essrv509ntc.ntc.nokia.com:6336/dynaweb/NED31_bsc_s8e/9090311/@Generic__BookView;pt=4?DwebQuery=STR

http://essrv509ntc.ntc.nokia.com:6336/dynaweb/NED31_bsc_s8e/9090311/@Generic__BookView;pt=4?DwebQuery=BQL

http://essrv509ntc.ntc.nokia.com:6336/dynaweb/NED31_bsc_s8e/9090311/@Generic__BookView;pt=4?DwebQuery=GQL

http://essrv509ntc.ntc.nokia.com:6336/dynaweb/NED31_bsc_s8e/9090311/@Generic__BookView;pt=4?DwebQuery=STS

http://www.ntc.nokia.com/ras/sd/Programs/E0/DHS_fs.doc

http://www.ntc.nokia.com/NTC/RAS/RASGSS.NSF/234c93b5af5cf825422566aa00700d62/98feb2701528dc9ac22567cf003512ed/$FILE/Capafea.ppt





http://essrv509ntc.ntc.nokia.com:6336/dynaweb/NED31_bsc_s8e/9090311/@Generic__BookView;pt=4?DwebQuery=SQL2

http://essrv509ntc.ntc.nokia.com:6336/dynaweb/NED31_bsc_s8e/9090311/@Generic__BookView;pt=4?DwebQuery=TCP3








‘001204 DROP TCH ASSCOMPL TO RFCH REL’ [S11.5 counter]

DROP CALL RATIO FORMULAS

TCH DROPS AFTER SEIZURE TCH_RADIO_FAIL /c1013

+TCH_RF_OLD_HO /c1014

+TCH_ABIS_FAIL_CALL /c1084

+TCH_ABIS_FAIL_OLD /c1085

+TCH_A_IF_FAIL_CALL /c1087

+TCH_A_IF_FAIL_OLD /c1088

+TCH_TR_FAIL /c1029

+TCH_TR_FAIL_OLD /c1030

+TCH_LAPD_FAIL /c1046

+TCH_BTS_FAIL /c1047

+TCH_USER_ACT /c1048

+TCH_BCSU_RESET /c1049

+TCH_NETW_ACT /c1050

+TCH_ACT_FAIL_CALL /c1081

-tch_re_est_assign /c57032

------------------------------------

CONVERSATION DROPS dropped_calls /c57007

----------------------------------------------

TCH DROPS AFTER ASSIGNMENT

tch_new_call_assign /c57033

+tch_ho_assign /c57034

-tch_norm_release /c57035

-tch_ho_release /c57036


-----------------------------

TCH ASSIGNMENTS FOR NEW

CALL tch_new_call_assign /c57033

CONVERSATION STARTED conn_ack to BTS

TCH ASSIGNED (alert followed) Assignment_complete from BTS

TCH SEIZED BSC allocates a TCH as a response to TCH request (Channel Activation)

TCH SEIZURES FOR NEW CALL

tch_norm_seiz /c1009

+tch_seiz_due_sdcch_con /c1099

+msc_i_sdcch_tch /c4044

+bsc_i_sdcch_tch /c4057

+cell_sdcch_tch /c4074

-tch_succ_seiz_for_dir_acc /c1165


S11 dcr_8h:

STARTED CONVERSATIONS conver_started /c57015

- msc_i_tch_tch /c4043

CLEAR COMMAND from MSC


spare057044 /c57044


-----------------------------




drop_after_tch_assign /c1202


-----------------------------



TCH RELEASE Disconnect from MS (A) Disconnect. from MSC (B)

S10.5 dcr_8g

S7 dcr_3j

S11 dcr_8h

S7 dcr_8b

RF CHN RELEASE Rf_channel_release_ack from BTS

S4 dcr_5a



































http://nea.ntc.nokia.com/cgi-bin/cgiwrap/neva/counters?003021http://nea.ntc.nokia.com/cgi-bin/cgiwrap/neva/counters?001165













DROP CALL on TCH / RE-ESTABLISHMENT S10.5


Version: 0.1

tch_new_call_assign

DROP_AFTER_TCH_ASSIGN

tch_re_est_assign

DROP_AFTER_TCH_ASSIGN

tch_re_est_assign

tch_re_est_release

Cell A

Cell B served_tch_call_req or served_dr_req or served_facch_req

Tch_new_call_assign and Tch_normal_release not updated if SDCCH is established with establishment cause location_update or other_procedures

and a CS call uses the same SDCCH


DCR_3 DCR_5

DCR_8

Layer 3 timeline

Author: E.Lipponen 1.4.2003


New Call Success Factors S7

SDCCH call

success

ratio

CSF_13

Congestion

related

SDCCH access

probability

CSF_11

Congestion

related

TCH access

probability

CSF_14

TCH success

ratio

CSF_16c

Call success ratio

CSF_10 =

Author: J.Neva 1/97

Version: 0.3 30.9.2002

PMWG approval.:

Activation

related

SDCCH access

probability

CSF_12

sd

cch

_serv

_re

q

9379

ch

an

nel_

rele

ase

sd

cch

_serv

_ack 9

396

esta

bli

sh

_in

d

tch

_serv

_re

q_

ack

tch

_serv

_re

q

Activation

related

TCH access

probability

CSF_15

assig

nm

en

t_co

mp

lete

esta

bli

sh

_in

d (

FA

CC

H)

ho

_co

mp

lete

d

rf_ch

_re

lease

sam

e p

rob

ab

ilit

y f

or

call

s a

nd

LU

MO

C, M

TC

, in

cl,

SM

S, L

S,S

S,

Excl.

LU

real

blo

cked

call

s

(su

cc.

DR

n

ot

co

un

ted

as b

loc

ked

)

New

call

s

New

call

s a

nd

HO

cases

(so

urc

e)

TC

H_N

OR

M_R

EL

EA

SE

SD

CC

H_R

EQ

SE

RV

ED

_S

DC

CH

_R

EQ

SD

CC

H_A

SS

IGN

SD

CC

H_N

EW

_C

AL

L_

AS

SIG

N

SD

CC

H_H

O_C

AL

L_

AS

SIG

N

TC

H_C

AL

L_

RE

Q

SE

RV

ED

_T

CH

_C

AL

L_

RE

Q

SE

RV

ED

_D

R_R

EQ

TC

H_N

EW

_C

AL

L_

AS

SIG

N

TC

H_H

O_A

SS

IGN

% %

% %

% %

T3101_E

XP

IRE

D

SE

RV

ED

_F

AC

CH

_R

EQ

sam

e p

rob

ab

ilit

y f

or

call

s a

nd

LU

- S

DC

CH

_S

MS

_A

SS

IGN

SD

CC

H_R

E_E

ST

_A

SS

IGN

SD

CC

H_R

E_E

ST

_R

EL

EA

SE

SD

CC

H_H

O_R

EL

EA

SE

TC

H_H

O_R

EL

EA

SE

TC

H_R

E_E

ST

_R

EL

EA

SE

End of call

End of seizure

TC

H_R

E_E

ST

_A

SS

IGN

SE

RV

ED

_F

AC

CH

_R

EQ

Note: these KPIs are not used in Network Doctor due to incosistency with the other CSF KPIs.




http://nea.ntc.nokia.com/formula.php?ne=BSC&formula_id=uav_14csf_16c




MTC Call Success Factors


Data calls, S10 Author: J.Neva 31.7.00

Version: 1.3 16.4.2002

PMWG appr.: 1.2 22.5.2001

14.4 kbit/s 1 tsl data call requests

hscsd_tch_req_14400

/c1156 (S7)

14.4 kbit/s 1 tsl data call seizures

hscsd_tch_succ_seiz_14400

/c1157 (S7)

9.6 kbit/s 1 tsl data call requests

/c1189 (S10)

9.6 kbit/s 1 tsl data call seizures

/c1190 (S10)

14,4 kbit/s data:

S7 option BSS7037

Successful MO data calls

basic_mo_data_calls

/c51045 (S3)

Successful MT data calls

basic_mt_data_calls

/c51047 (S4)

BSC level

BTS level

Note: In Nokia M9 MSC the Circuit Group measurement can be

defined for internal data circuits. More detailed data in M10

HSCSD call

Erlangs for 14,4kbit/s

(S11 planned)

New call or HO

Erlangs for 9,6kbit/s

(not planned)













Transmission quality Author: J.Neva 1.6.01

Version: 1.0

PMWG appr.:

ERRORED SECONDS (err_sec)

When during a one second period one or more bits

are in error.

SEVERE ERRORED SECONDS (err_sec_severe)

When during a one second period the bit error ratio is

greater than or equal to 1*(1/1000).

For a connection of 64 kbit/s this means that a

severely errored second is registered when there are

64 or more

errors in the one second period.

DEGRADED MINUTES (degraded_min)

When a bit error ratio is greater

than 1*(1/1000000) during one minute.

NOTE! If there are severely errored seconds during

the minute, those seconds are not calculated for the

one minute period. It means that the measured time

can be more than one minute.

c62002

c62003

c62004

DMR

c63002

c63003

c63003

DN2

c65002

c65003

c65003

BSC

ET

c66002

c66003

c66003

TCSM

ET

c69002

c69003

c69004

TRE

SEL

BACKGROUND BLOCK ERRORS BBE

(NetAct200 dbase name = degraded_min)

BBE is updated when observed an errored block (EB) not

occurring as part of an severely errored seconds (SES). Errored

block is a block in which one or more bits are in error

c64002

c64003

TRU

c68002

c68003

c68004

TRE


‘71 MS Capability Indication Measurement’ – (updated in slide 134)

Measurement info:

MS Capability Indication measurement provides cell-specific

information on the capabilities of the mobile stations. The

counters of this measurement are updated on TCH only.

Ph1

71000 (S9)

Measurement data:

MS reporting time by MS categories :

Object info: Measurement object level is BTS

Single GSM900

71004 (S9)

Single GSM1800

71006 (S9)

Tri Band

71008 (S9)

Ph2

71001 (S9)

Single EGSM900

71005 (S9)

Dual Band

71007 (S9)

GSM 850

71033 (S10)

Single GSM1900

71035 (S10.5)

DTM

71038 (S12)

SAIC

71039 (S12)

Single GSM900

71009(S9)

Measurement data:

TCH seizures by MS categories :

Single GSM1800

71011(S9)

Tri Band

71013(S9)

GSM 850

71034(S10)

Single EGSM900

71010(S9)

Dual Band

71012(S9)

Mslot incabable

71014(S9)

Single GSM1900

71036(S10.5)

DTM

71037 (S12)

SAIC

71040 (S12)

MultiS Class 1

71015(S9)

MultiS Class 2

71016(S9) MultiS Class 18

71032(S9)) ….

Ph1

71002(S9)

Ph2

71003(S9)


BSS S10 New CS

COUNTERS & FORMULAS


New Measurements in S10

•Defined Adjacent Cell Measurement (for Automated Planning) •FER Measurement •Reversed Hunting Measurement (A-if statistics) •Non-BCCH Layer Offset Measurement (for Common BCCH)

(E)GPRS, EDGE: •Coding Scheme Measurement (EGPRS) •Quality of Service Measurement •PBCCH Availability Measurement •Dynamic Abis Measurement (for GPRS) •System Level Trace for GPRS

POSITION BASED SERVICES: •PBS Measurement •PBS Observation

Supported in

ND BSS

since v12.5

Support open


BCF-1 BCF-2

TRX-1 TRX-1

BTS-2 BTS-1

SEG-1

BTS-3

TRX-2

TRX-1

BTS-4

SEG-2

= GSM900

= GSM1800

BCCH

BCCH

SEG = telecom cell , 1 BCCH

(one or more BTSs from

one BSC)

CELL a

CELL b

Multi-BCF can chain max.6 BTS

max.32 BTS/SEG,

All BTS from same BSC

Version: 1.1 5.2.2002

PMWG: 1.0 18.6.01

Note1:

BSC still sends

the measurements

to NetAct on BTS

level (or TRX level).

NetAct adds to

measurement table

a column for

segment

and fills up that info

based on the

configuration

data stored in

NetAct database

(segment is defined

in c_bts table).

In traffic measurement the request is updated to BCCH BTS, successfull call set up to BTS where the channel was allocated. Unsuccessful dual band call set up with sufficient measurement results is updated to non BCCH BTS and unsuccessful single band or dual band without measurement results are updated to BCCH BTS.

Master BTS is defined in c_bts table (’master_bts’-field). Parameters of master BTS are copied to slave BTS.

First SDCCH has to

be in the same BTS

as BCCH. Different

BCF in SEG need to

use same clock

(sync cable)

e.g. Ultra e.g. Prime

Segment, multi-BCF (S10)


’77 FER Measurement’ (updated in slide 135)

BTS id

77000

TRX id

77001

Codec type

77002

FH type

77006

TRX freq

77005

Ext.area

77003

Freq.grp.id

77004

Averaging window size

(1-32 SACCH frames)

77014

Estimated

samples

77031

Class0

77015

Class1

77016

Class5

77020

Class4

77019

Class3

77018

Class2

77017

Class7

77022

Class6

77021

B1

77007

UL FER

Class0

77023

Class1

77024

Class5

77028

Class4

77027

Class3

77026

Class2

77025

Class7

77030

Class6

77029

DL FEP

B2

77008

B3

77009

B4

77010

B5

77011

B6

77012

B7

77013

Boundaries of frame erasure ratio (%), modifiable as meas.parameters

2% 4% 6% 8% 10% 12% 14% Default values

0% 100%

Class0

77032

Class1

77033

Class5

77037

Class4

77036

Class3

77035

Class2

77034

Class7

77039

Class6

77038

DL FER

Measurement data:

Parameter data:

Codec types: 1 = HR 2 = FR 3 = EFR 4 = AMR HR 7.95 . . . 9 = AMR HR 4.75 10=AMR FR 12.2 . . . 17=AMR FR 4.75

Class0

77040

Class1

77041

Class5

77045

Class4

77044

Class3

77043

Class2

77042

Class7

77047

Class6

77046 SAIC DL FER (S12)

Object data:

Measurement info:

Frame Erasure Rate is the best available indicator in a GSM system to assess the Voice Quality provided in a network.

It represents the percentage of frames being dropped due to high number of non corrected bit errors in the frame.

The correlation of BER (reported by the MS) and FER (Voice Quality indicator) is not constant as the efficiency of the

error correction mechanism varies with different techniques. The BER reported by the mobiles is the figure measured

before the decoding process, whereas the FER is associated with the corrected BER after the decoder.

MSs that do not support ‘Enhanced Measurement Report’ are not able to report downlink FER. Downlink FER can be

estimated by using correlation counted for each channels profile. FER value replace BER value in handover and power

control algorithms in the frequency hopping systems.


BTS id

High limit

/c75002

Object info

Average DL signal

strength

/c75003 /c75004

DL

Low limit

/c75001

Sum of squares of

DL signal

/c75005

Average DL signal

strength

/c75006

BCCH1

/c75007

Samples

/c75009

.

.

.

Average DL signal

strength

Measurement data

Parameter info

(setup in measurement creation)

NCC1 BCC1

BCCH32 NCC32 BCC32

C/I class 1 C/I class 2 C/I class 3

Samples

/c75010

Samples

/c75011

Samples Samples Samples

.

.

.

.

.

.

.

.

.

Adjacent cell 1

Adjacent cell 32

Serving cell

6dBm Initial default values,

last values used as

new default

0dBm

Serves the needs of automated adjacency management.

Sum of squares of

signals

/c75008

.

.

.

Sum of squares of

signals

Nbr of

adj.cells

/c75000

Reporting

possibilities:

- Adjacency

list

Version: 1.0

PMWG: 18.6.01

Defined adjacent cell (S10 opt.)

http://nop-i.nokia.com/counter.phpne=BSC&counter_id=75002













Non-BCCH layer offset (S10 stand.)

Object info

Offset counters (number of samples)

-1dB

c92082

S10.5

Measurement data

BTS

0dB

c92001

S10

+1dB

c92002

S10

…….. +40dB

c92041

S10

>40dB

c92042

S10

BCCH signal level is 40dB stronger

than the reported MS level on GSM1800 TCH

BTSs that are on the

GSM 1800 band of

a segment utilizing

Common BCCH control

feature (BSS10016)

Helps to define the ‘non BCCH layer offset’- parameter when using common BCCH feature.

Reporting

possibilities:

- BTS list

Int_id SEGMENT Bts_int_id

Version: 1.0

PMWG: 18.6.01

-40dB

c92043

S10.5

<-40dB

c92000

S10

……..

BCCH signal level is more than 40dB weaker

than the reported MS level on GSM1800 TCH









Position based services (S10 opt.)

Object level:

BTS

Measurement data

SUCC

c78003

REQ

c78004

SUCC

c78005

REQ

c78029

NO RIT

COVERAGE

c78011

INSUFF. BTS

INFO

c78012

SUCC

c78014

SUCC

c78016

REJECTED, FEATURE

NOT SUPPORTED

C78017

Reporting

possibilities:

-overview

-Problem finding

EMERGENCY

c78002

MS

c78013

OPERATOR

c78015

E_OTD METHOD

NO MS

SUPPORT

c78009

NOT ENOUGH

VALUES

c78010

CellId+TA STANDALONE

GPS

SUCC

c78008

CALCULATIONS

REJECTED

FAIL

FAIL

FAIL

FAIL

REQ

c78007

Version: 1.2

PMWG: 9.8.2002

See ND reports: 260

SUCC

c78001

FAIL

LOCATION SERVICE REQUESTS

c78000

pbs_7 =c78000+c78017

= SDCCH seizures due to PBS

UNSPECIFIED

pbs_8

LOCATION SERVICE REQUESTS BY CLIENT TYPE

c78000-c78002-c78013-c78015

NBR OF LOC REQ REJ

BY LIC

C78024

NBR OF POS CMD REJ

BY LIC

C78027

NBR OF UTDOA REQ

REJ BY LIC

C78028

NBR OF INTERNAL

SMLC PLR REJ BY LIC

C78030

SUCC

c78006

REQ

c78031

CellId

SUCC

c78032

STANDALONE

SMLC

REQ SEND

c78022

SUCC

RECEIVED

c78023




















http://nea.ntc.nokia.com/formula.php?ne=BSC&formula_id=pbs_7

http://nea.ntc.nokia.com/formula.php?ne=BSC&formula_id=pbs_8











Reversed hunting (S10 option)

Object level:

BSC/pool_id

Measurement data

Number of

circuits

c89000

Avg.available

C89001/

C89002

Avg. reserved

C89003/

C89004

FR

c89005

EFR

c89006

FR/AMR

c89007

HR

c89008

HR2

c89007

HR/AMR

c89010

Mslot 1

c89012

Mslot 2

c89013

Mslot 3

c89014

Mslot 4

c89015

Single slot

c89011

The route between MSC

and BSS may not

support all types of

traffic.

With reversed A-

interface Circuit

Allocation the BSS

allocates the

circuit needed based on

the call type.

There are some more counters in

BSC level Clear code measurement.

Reporting

possibilities:

- pool list (obviously for testing purposes)

CIRCUITS availability

CALLS attempts

DATA CALLS

Version: 1.0

PMWG: 18.6.01

















Feature: Adaptive Multirate Codec (S10)

Object info

Measurement data

Counters are related to BSS1004: Adaptive Multirate Codec.

Measurement: Traffic, HO

TCH

Requests

c1184

SUCC

c1185

UNSUCC

c1186

SUCC

c1187

UNSUCC

c1188

FR->HR (packing)

AMR CODEC SET MODIFY

DOWNGRADE UPGRADE


AMR packing / unpacking handovers

INTRA-CELL

AMR

Call or HO HR->FR (unpacking)

AMR codec selects in real

time the type of channel

(HR,FR)

and for each channel type one

of several (about 10) codec

bit-rates varying from 4.75 to

12kbps.

-Improves connection's

robustness against

interference.

-Adds capacity (HR benefit).

ATT

c4143

SUCC

c1183

SUCC

c1182

INTRA-CELL

ATT

c4142

Version: 1.2 3.6.2002

PMWG: 18.6.01

See ND reports: 213, 248

HO

FR->HR

SUCC

c4205

IN

SUCC

c4204

SUCC in ext HOs

originally BSC-

controlled intra-cell

HR->FR

SUCC

c4206

IN

SUCC

c4202

SUCC in/out ext

HOs originally BSC-

controlled inter-cell

OUT

SUCC

c4203


Feature: Adaptive Multirate Codec (S10)

Object info

Counters are related to BSS1004: Adaptive Multirate Codec.

Measurment:Rx Quality


There are 130 new

counters in RxQual related to

Mode 1..4 per HR/ FR

,per UL/DL , per RxQual,

per quality class 0…7:

(4*2*2*8).

Version: 1.1 8.5.2002

PMWG:

AMR_FR_CODEC_MODE_SET

AMR_HR_CODEC_MODE_SET

TRX

These indicate the actual bit rates of codec mode sets 1-4 (smallest

bitrate is M1).

Codec mode set is BTS specific setting but usually the same values are

used in whole network.

q0 q1 q2 q3 q4 q5 q6 q7

Non AMR xx xx xx xx xx xx xx xx

FR M1 xx xx xx xx xx xx xx xx




HR M1 xx xx xx xx xx xx xx xx




UL

q0 q1 q2 q3 q4 q5 q6 q7

Non AMR xx xx xx xx xx xx xx xx









DL

Old

counters

(S9) count

both AMR

and nonAMR

call samples

12.2 10.2 7.95 7.5 6.7 5.9 5.15 4.74

Bitmap decoding (varchar)

kbps (4 bitrates in a set), e.g. 10101010 means 12.2, 7.95, 6.7,5.15

- - 7.95 7.5 6.7 5.9 5.15 4.74 kbps (4 bitrates in a set)

call samples

Meaning of bitrate

M1…M4 is as

explained below

See ND reports: 204, 244, 246

Note: Different first and last codecs in

a measurment report caused multiple

countig. Fix: CN 6.0 delivered. S10

CD 2.3 FEA CN- S10_083. Only the

last codec related counter triggered.


Intra segment HOs (S10)

Object level: BTS

Measurement data

Measurement: HO, Clear Code

BCCH->nonBCCH

due to load

BTW TYPES

ATT

(srce)

c4139

TCH -TCH SDCCH -SDCCH

HO BETWEEN BTS IN SEGMENT

BTW BANDS

SUCC

(tgt)

c4134

BTW TYPES

ATT

(srce)

c4133

SUCC

(tgt)

c4131

BSS10046 Multi BCF Control

BSS10016 Common BCCH Control

Related to:

ATT

(srce)

c4135

SUCC

(tgt)

c4136

BTW BANDS

Due to load SUCC

(tgt)

c4140

SUCC

(tgt)

c4132 ATT

(srce)

c4137

SUCC

(tgt)

c4138

SUCC

(tgt)

c51136 SUCC

(tgt)

c51135

SUCC

(tgt)

c51148 SUCC

(tgt)

c51147

Version: 1.0

PMWG: 18.6.01 Status open

51xxx =clear code measurement

tgt= target, src=source

Object level: BSC


BSS S10.5&S11&S11.5&12

New CS Counters & Formulas


S10.5 BSS CS Measurements Counter Block Pictures

S10.5 BSS CS Measurements

• ‘93 UTRAN HO Adjacent Cell Measurement’[BSS10101 ISHO]


UNDEFINED WCDMA NEIGBOUR CELL

‘93 UTRAN HO Adjacent Cell Measurement’

WCDMA NEIGBOUR CELL 1

WCDMA NEIGBOUR CELL 32

SERVING GSM CELL

.

.

.

093002 HO_ATT_WCDMA_RAN_CELL 093003

HO_SUCC_WCDMA_RAN_CELL 093004

HO_FAIL_DUE_RES_WCDMA_RAN

093005 HO_ATT_FROM_WCDMA_RAN 093006 HO_SUCC_FROM_WCDMA_RAN

093007 HO_FAIL_DUE_RES_WCDMA_RAN_CELL

093250 HO_ATT_WCDMA_RAN_CELL 093251

HO_SUCC_WCDMA_RAN_CELL 093252

HO_FAIL_DUE_RES_WCDMA_RAN

093253 HO_ATT_FROM_WCDMA_RAN 093254 HO_SUCC_FROM_WCDMA_RAN

093255 HO_FAIL_DUE_RES_WCDMA_RAN_CELL

093256 HO_ATT_FROM_UNDEF_WCELLS 093257 HO_SUCC_FROM_UNDEF_WCELLS

093258 HO_FAIL_RES_FROM_UNDEF_WCELLS

093000 LACSAC

093001 MCCMNC

093259 RNC_ID CI

093248 LACSAC

093249 MCCMNC

093290 RNC_ID CI

.

.

.

.

.

.

.

.

.

.

Note! In shifting from 3G to 2G inter-

system handover cell level statistics is

not possible because of 3GPP standards,

which recognize only the

PLMN(MCCMNC)+ LAC +SAC

identification of the 3G source cell. That

is why the counters 093259 -093290 are

not valid when shifting from 3G to 2G

inter-system handover. ND report 159.

Measurement info:

The UTRAN Handover Adjacent

Cell measurement of the BSC

collects statistics about the

distribution of Inter-System

Handovers between different

cells. Counters are collected

separately for each serving cell

on the GSM side.

Measurement data:

Object info: UTRAN HO Adjacent Cell

Measurement object level is

serving GSM cell


S11 BSS CS Measurements Counter Block/Signaling Charts

S11 BSS CS Measurements

• ‘99 Total FEP Measurement’ [BSS11085 APE]

• ‘100 DFCA Measurement’ [BSS11052 DFCA]

• ‘101 DFCA Assignment Measurement’ [BSS11052 DFCA]

• ‘102 BSC-BSC Measurement’ [BSS11052 DFCA]

• ‘103 WPS Measurement’ [BSS11149 WPS in BSC]


’99 Total FEP Measurement’

Measurement data:

Total FEP CO

Channel 1

99004 (S11)

Object info: Total FEP Measurement object level is serving BTS.

BA LIST

CHANGED

99000 (S11) NUMBER OF

SAMPLES

99001 (S11)

TOTAL

INTERFERENCE

99002 (S11)

Total FEP

ADJ Channel

1

99005 (S11)

Total FEP CO

Channel 2

99007 (S11)

Total FEP

ADJ Channel

2

99008 (S11)

Total FEP CO

Channel 100

99301 (S11)

Total FEP

ADJ Channel

100

99302 (S11)

Serving cell

BTS_id

Measurement info:

The Total FEP Measurement provides Total Frame Erasure Probability values of each serving cell and neighbouring cell

pair. In the measurement the C/I ratio between the serving cell and adjacent cell is mapped to FEP values by a predefined

correlation table. The Total FEP value is sum of the FEP values for each serving cell during the measurement period. For each

BTS there is a set of counters, which are collecting the cumulated sum of FEP values during the measurement period for a

certain serving cell – neighbouring cell pair. Information is collected by BSC from MMR-messages, which are received in 0.48 s

period during the call. Separate Total FEP values are provided for co-channel and adjacent channel interference. Using these

counters, an interference matrix can be formed telling the cost of putting any group of cells on same frequency.

Adjacent cells 1 to 100

ADJ CELL ID 1

99003 (S11)

ADJ CELL ID 2

99006 (S11)

ADJ CELL ID 100

99300 (S11)


BSC specific user definable values

‘100 DFCA Measurement’ The number of DFCA assigments per C/I group. One counter in each group updated in one succesful DFCA assignment.

C/I TARGET VALUE FOR THE CONNECTION

TYPE (FR/EFR, HR, 14.4, AMR or AMR HR):

C/I TARGET 100000 (S11)

Object info: DFCA Measurement measurement object level is BTS and Connection Type (FR,AMR FR, HR, AMR HR and 14K4). Max object count 248*5=1240 (S11)

Measurement data: The number of succ/unsucc DFCA Assignments

SUCC DFCA ASS

100154 (S11)

SOFT BLOCKED DFCA

ASS DUE TO C/N

100157(S11)

SOFT BLOCKED DFCA

ASS DUE TO C/I

100156(S11)

DFCA ASS HIGH LOAD

100155 (S11)

THE UL OFFSET THAT IS ADDED TO THE C/I

TARGETS AND SOFT BLOCKING C/I LIMIT OF

ALL CONNECTION TYPES:

C/I TARGET UL OFFSET 100001 (S11)

Incoming DL C/I of the DFCA assignment

DFCA_C_I_OVER_TG_PLUS_20_DL 100045(S11)

DFCA_C_I_TG_PLUS_20_DL 100043(S11)

DFCA_C_I_TG_PLUS_19_DL 100041(S11)

… DFCA_C_I_TG_PLUS_4_DL 100011(S11) DFCA_C_I_TG_PLUS_3_DL 100009(S11) DFCA_C_I_TG_PLUS_2_DL 100007(S11) DFCA_C_I_TG_PLUS_1_DL 100005(S11) DFCA_C_I_TG_DL_I_TARGET 100003(S11) DFCA_C_I_TG_MINUS_1_DL 100047(S11) DFCA_C_I_TG_MINUS_2_DL 100049(S11) DFCA_C_I_TG_MINUS_3_DL 100051(S11) … DFCA_C_I_TG_MINUS_15_DL 100075(S11) DFCA_C_I_LOW_TG_MINUS_15_DL 100077(S11)

Outgoing DL C/I of the DFCA assignment

WORST_INTERF_C_I_OVER_TG_PLUS_20_DL 100121(S11)

WORST_INTERF_C_I_TG_PLUS_20_DL 100119(S11)

WORST_INTERF_C_I_TG_PLUS_19_DL 100117(S11)

… WORST_INTERF_C_I_TG_PLUS_4_DL 100087(S11) WORST_INTERF_C_I_TG_PLUS_3_DL 100085(S11) WORST_INTERF_C_I_TG_PLUS_2_DL 100083(S11) WORST_INTERF_C_I_TG_PLUS_1_DL 100081(S11) WORST_INTERF_C_I_TG_DL 100079(S11) WORST_INTERF_CI_TG_MINUS_1_DL 100123(S11) WORST_INTERF_CI_TG_MINUS_1_DL 100125(S11) WORST_INTERF_CI_TG_MINUS_1_DL 100127(S11) … WORST_INTERF_CI_TG_MINUS_15_DL 100151(S11) INTERF_CI_LOW_TG_MINUS_15_DL 100153(S11) Incoming UL C/I of the DFCA assignment

DFCA_C_I_OVER_TG_PLUS_20_UL 100044(S11)

DFCA_C_I_TG_PLUS_20_UL 100042(S11) DFCA_C_I_TG_PLUS_19_UL 100040(S11)

… DFCA_C_I_TG_PLUS_4_UL 100010(S11) DFCA_C_I_TG_PLUS_3_UL 100008(S11) DFCA_C_I_TG_PLUS_2_UL 100006(S11) DFCA_C_I_TG_PLUS_1_UL 100004(S11) DFCA_C_I_TG_UL_I_TARGET 100002(S11) DFCA_C_I_TG_MINUS_1_UL 100046(S11) DFCA_C_I_TG_MINUS_2_UL 100048(S11) DFCA_C_I_TG_MINUS_3_UL 100050(S11) … DFCA_C_I_TG_MINUS_15_UL 100074(S11) DFCA_C_I_LOW_TG_MINUS_15_UL 100076(S11)

Outgoing UL C/I of the DFCA assignment

WORST_INTERF_C_I_OVER_TG_PLUS_20_UL 100120(S11) WORST_INTERF_C_I_TG_PLUS_20_UL 100118(S11) WORST_INTERF_C_I_TG_PLUS_19_UL 100116(S11)

… WORST_INTERF_C_I_TG_PLUS_4_UL 100086(S11) WORST_INTERF_C_I_TG_PLUS_3_UL 100084(S11) WORST_INTERF_C_I_TG_PLUS_2_UL 100082(S11) WORST_INTERF_C_I_TG_PLUS_1_UL 100080(S11) WORST_INTERF_C_I_TG_UL 100078(S11) WORST_INTERF_CI_TG_MINUS_1_UL 100122(S11) WORST_INTERF_CI_TG_MINUS_1_UL 100124(S11) WORST_INTERF_CI_TG_MINUS_1_UL 100126(S11) … WORST_INTERF_CI_TG_MINUS_15_UL 100150(S11) INTERF_CI_LOW_TG_MINUS_15_UL 100152(S11)

BTS_id

&

Connection Type

MCMU load

Measurement data:

PRIMARY DFCA

ALGORITHM ATT

100158 (S11.5)

SECONDARY DFCA

ALGORITHM ATT

100159 (S11.5)

The DFCA Algorithm has chosen the DFCA to be searched before the regular layer

The DFCA Algorithm has chosen the regular layer to be searched before the DFCA layer but due to congestion in regular area DFCA area is searched


‘DFCA’ counter triggering in call setup

TCH REQUESTS

/c1010

TCH service request

SOFT_BLOCKED_DFCA_ASS_DUE_TO_CI

/c100156

DFCA_C_I_TG_PLUS_1_UL /c 100004

Calculate C/I and choice

Ma, Maio and tsl

Regular/ DFCA

Regular search

DFCA_C_I_TG_PLUS_6_DL /c100015

WORST_INTERF_CI_TG_MINUS_4_UL c/100128

WORST_INTERF_C_I_TG_DL /c100079

Channel found.

C/N blocked res.

SUCC_DFCA_ASS_DFCA

/c100154

MA MAIO 1 /c 101000 or

MA MAIO 2 /c 101002 or…

MA MAIO 150 /c 101298

(E.g. Incoming DL +6dB, Outgoing DL 0dB,

Incoming UL+1dB, Outgoing UL-4dB)


/c1009

TCH REQUESTS FOR NEW CALL

/c1026

Yes No

Channel found


/c1009

C/I blocked res.

SOFT_BLOCKED_DFCA_ASS_DUE_TO_CN

/c100157

No

Yes Yes

Yes

No

TCH SEIZURES REJ DUE LACK

/c1011

PRIMARY DFCA ALGORITHM ATT

/c 100158 (S11.5!)

Or

SECONDARY DFCA ALGORITHM ATT

/c 100159 (S11.5)

DFCA Attempts (S11.5)




’101 DFCA Assignment Measurement’

Measurement info:

The DFCA Assignment measurement

collects statistics on usage of DFCA and

MAIO and the corresponding assignment

counters. The assignment counters are

updated whenever the corresponding MA

list and MAIO are used in a DFCA

assignment.

Identification of the used combination of DFCA

MA list and MAIO value:

MA MAIO 1 I 101000 (S11.5)



MA MAIO 150 I 101298 (S11.5)

The number of DFCA assignments using the

combination of MA list and the MAIO specified in

the corresponding MA_MAIO counter:

DFCA ASS 1 I 101001 (S11.5)




DFCA ASS 150 I 101299 (S11.5)

Measurement data:

.

.

.

.



MA MAIO 2 I 101002 (S11.5)




DFCA ASS 2 I 101003 (S11.5)

.

.

.

.

.

.

.

.

Object info:

DFCA Assignment Measurement

object level is BTS id.


‘102 BSC-BSC Measurement’

Average and peak delays between BSCs Radio Resource Managers

Average delay between Radio Resource

Managers of the BSCs:

BSC-BSC DELAY 102000(S11)/

BSC-BSC DENOMINATOR 102001(S11)

Peak delay between Radio Resource Managers

of the BSCs :

BSC-BSC PEAK DELAY 102002(S11)

Object info: BSC-BSC Measurement object level is SPC, Signaling Point Code. Object amount 10.

SPC

Measurement data:

Measurement info: BSC-BSC measurement collects statistics on the

inter-BSC communication related to DFCA

functionality. The measurement level is BSC, and the

measurement objects are identified with a signaling

point code (SPC). The counters of this measurement

record information on average and peak delay

between the Radio Resource Managers in separate

BSCs.


TCH requests for new call/c 001026

Successful DFCA Assignment

MS BTS BSC MSC

Paging part

Radio access part on CCCH

DDCH establishmnet part

SDCCH signalling part

Physical context confirm

TCH requests/c 001010

‘Incoming DL C/I of the DFCA assignment’

and

‘Outgoing DL C/I of the DFCA assignment’

and

‘Incoming UL C/I of the DFCA assignment’

and

‘Outgoing UL C/I of the DFCA assignment’

counters triggered

Succ DFCA Ass/c 100154

or/and

Succ DFCA Ass in High Load/c 100155

MA MAIO 1 /c 101000 or

MA MAIO 2 /c 101002 or…

MA MAIO 150 /c 101298

TCH Seizures for New Call/c 001009

Channel activation


TCH requests for new call/c 001026

Un-successful DFCA Assignment

MS BTS BSC MSC

Paging part

Radio access part on CCCH

DDCH establishmnet part

SDCCH signalling part

Physical context confirm

TCH requests/c 001010

Soft Blocked DFCA Ass Due to C/I. /c 100156 (S11)

or

Soft Blocked DFCA Ass Due to C/N. /c 100157 (S11)

Regular search continues


‘103 WPS Measurement’

TCH occupancy by WPS users during measurement period

AVERAGE NUMBER OF FTCH s OCCUPIED BY

WPS USERS:

WPS AVE OCCU FTCH COUNT 103000(S11)/

WPS DENOM 1 103001 (S11)

AVERAGE NUMBER OF HTCH s OCCUPIED BY

WPS USERS:

WPS AVE OCCU HTCH COUNT 103002(S11)/

WPS DENOM 2 103003(S11)

WPS PEAK BUSY FTCH

COUNT 103004(S11)

WPS PEAK BUSY HTCH

COUNT 103005(S11)

PEAK WPS QUEUE

COUNT 103006(S11)

AVERAGE SUCCESSFUL QUEUING TIME FOR

WPS USER:

AVE SUCC WPS QUEUE TIME 103007(S11)/

WPS DENOM 3 103008(S11)

QUEUED PRI 1 WPS

USERS 103009(S11)

QUEUED PRI 5 WPS

USERS 103013(S11)

QUEUED PRI 4 WPS

USERS 103012(S11)

QUEUED PRI 3 WPS

USERS 103011(S11)

QUEUED PRI 2 WPS

USERS 103010(S11)

SUCCESSFUL TRAFFIC

CHANNEL ALLOCATION

FOR PUBLIC USER

WHILE WPS USERS IN

QUEUE 103014(S11)

QUEUING NOT

ALLOWED PRI 1 WPS

USERS 103015(S11)

QUEUING NOT

ALLOWED PRI 4 WPS

USERS 103018(S11)

QUEUING NOT

ALLOWED PRI 5 WPS

USERS 103019(S11)

QUEUING NOT

ALLOWED PRI 3 WPS

USERS 103017(S11)

QUEUING NOT

ALLOWED PRI 2 WPS

USERS 103016(S11)

PRI 1 WPS USERS

REMOVED FROM QUEUE

DUE TIMER 103020(S11)

PRI 4 WPS USERS

REMOVED FROM QUEUE


PRI 5 WPS USERS

REMOVED FROM QUEUE


PRI 3 WPS USERS

REMOVED FROM QUEUE


PRI 2 WPS USERS

REMOVED FROM QUEUE


Object info: WPS Measurement object level is BTS id and TRX type (normal/extended)

BTS_id & TRX type

Measurement data:

WPS queuing counters

Measurement data:

Measurement info: With the counters of WPS Measurement, the user can

monitor the performance of traffic channel allocation

and queuing algorithms in granting priority access to

WPS users. WPS calls are given priority access to the

next available radio traffic channel in congestion

situation.


Successful ‘WPS’ call establishment

MS

BSC MSC/ VLR PSTN BTS HLR

CM Service Request

Channel Request

CM Service Accept


Setup

Call Proceeding

Assignment Request

Assignment Command

Assignment Complete

IAM (Initial Address Message)

ACM (Address Complete Message)

Alerting

ANM (Answer Message)

Connect

Connect Acknowledge

Assignment Complete


Successful ‘WPS’ call via queuing

MS

BSC MSC/ VLR PSTN

QUEUED PRI 1 WPS USERS 103009 or




QUEUED PRI 5 WPS USERS 103013

BTS HLR

Setup

Call Proceeding

Assignment Request

Queuing Indication

Paging and signaling part

Assignment Command

Stop all call

rel. timers

Progress

TCH seized, FACCH signalling part

Also in a case of full queue for WPS user:

QUEUING NOT ALLOWED PRI 2 WPS USERS 103016 or



QUEUING NOT ALLOWED PRI 5 WPS USERS 103019

Start timer T11


Unsuccessful ‘WPS’ call due to full queue

MS

BSC MSC/ VLR PSTN BTS HLR

Setup

Call Proceeding

Assignment Request

Assignment failure

Start timer T305

Paging and signaling part

Release Complete

Stop all CC

timers Disconnect





QUEUING NOT ALLOWED PRI 5 WPS USERS 103019

Release

Stop all CC

timers

Start timer T308

Stop all CC

timers Clear Command

Channel Release

Assignment failure


S11.5 BSS CS Measurements Counter Block Pictures

S11.5 BSS CS Measurements

• ‘104 IMSI Based Handover Measurement’ [BSS12158 IBHO]

• ‘109 Soft Channel Capacity Measurement’ [BSS20577]

• ’29 Drop Call Breakdown Observation’ [BSS20028 DCBO]


‘104 IMSI Based HO Measurement’

IBHO to Default ANE

Attempt Unsuccessful

UTRAN IBHO_ATT_TO_UTRAN_DEFAULT_ANE IBHO_UNS_TO_UTRAN_DEFAULT_ANE

104000 104001

GSM IBHO_ATT_TO_GSM_DEFAULT_ANE IBHO_UNS_TO_GSM_DEFAULT_ANE 104002 104003

IBHO to All ANE


UTRAN IBHO ATT TO UTRAN ALL IBHO UNS TO UTRAN ALL

104004 104005

GSM IBHO ATT TO GSM ALL IBHO UNS TO GSM ALL 104006 104007

IBHO to ANE01


UTRAN IBHO_ATT_TO_UTRAN_ANE01 IBHO_UNS_TO_UTRAN_ANE01

104008 104009

GSM IBHO_ATT_TO_GSM_ANE01 IBHO_UNS_TO_GSM_ANE01 104010 104011

IBHO to ANE10


UTRAN IBHO_ATT_TO_UTRAN_ANE10 IBHO_UNS_TO_UTRAN_ANE10

104044 104045

GSM IBHO_ATT_TO_GSM_ANE10 IBHO_UNS_TO_GSM_ANE10 104046 104047

Authorized Network (ANE): A group of network PLMN identifiers which have similar access rights. Default ANE: Default authorized network is used for unidentified subscriber. All ANE: All ANE counters are updated for subscribers having access to all neighboring UTRAN and/or GSM Networks. KPIs: ND reports 285 and 286. Note! Total IBHO attempts is the summary of all GSM&UTRAN IBHO attempts to ‘Default ANE’, ‘ALL ANE’ and ‘ANE01…ANE10’.

or

or

or

.

.

.

.

.

Measurement info:

The IMSI Based Handover

Measurement is a cell level

measurement collecting

statistics on the IMSI based

HO attempts and failures for

each Authorized Network

(ANE). There are separate

counters for GSM and

UTRAN networks.

Object info: IMSI Based HO Measurement

object level is BTS ID & TRX Type

(normal/extended)

Measurement data:


‘109 Soft Channel Capacity Measurement’

Measurement info:

Soft Channel Capacity increases the traffic channel (TCH)

limit on the BSC. You are allowed to configure all the radio

traffic time slots of all the half rate (HR) capable TRXs to

dual rate (DR) support. The overall traffic processing

capacity of the BSC is not increased.

With the counters of Soft Channel Capacity measurement

the user is able to get measurement data about the

utilization and availability of the TCHs in BCSU level.

PEAK BUSY TCH PER BCSU

109000 (S11.5)

AVE BUSY TCH PER BCSU

109001 (S11.5)

AVE BUSY TCH PER BCSU DENOMINATOR

109002 (S11.5)

TOTAL TCH BUSY TIME PER BCSU

109003 (S11.5)

Measurement data:

Object info: SCC Measurement object level is

BCSU logical address

TCH REQ REJ DUE TO LACK OF RES PER

BCSU

001216(S11.5)

Feature related counter in Traffic Measurement:


Measurement data:

’29 Drop Call Breakdown Observation’

029016 SUDDEN DROP

029017 ADJ CELL PLMN ID 1

029018 ADJ CELL LAC 1

029019 ADJ CELL ID 1

029020 RX LEVEL ADJ 1

.

.

.

029037 ADJ CELL PLMN ID 6

029038 ADJ CELL LAC 6

029039 ADJ CELL ID 6

029040 RX LEVEL ADJ 6

029041 FOCUS OF BREAKDOWN

Counter # Counter name

029000 BTS ID

029001 RELEASE TIME

029002 PHASE OUT

029003 CAUSE OUT

029004 TRX ID

029005 PHASE IN

029006 CAUSE IN

029007 TIMING ADVANCE

029008 DL RX LEVEL

029009 UL RX LEVEL

029010 DL RX QUALITY

029011 UL RX QUALITY

029012 DL FER

029013 UL FER

029014 DL LAST USED BITRATE

029015 UL LAST USED BITRATE

Observation info:

S11.5 Drop Breakdown Observation collects data of conditions in the event of

dropped calls. The observation is activated for each TRX under BSC.

BSC counter ‘057044/001202 DROP AFTER TCH ASSIGN‘ is updated at the

same time with observed drop. The other option is to set the focus of

breakdown to counter ‘002071 CLEAR REQUEST SENT BY BSC ON TCH’

BSC counter ‘057044/001202 Drop After TCH Assignment‘ triggering

scenarios:

•‘Basic Call’:Every call dropping TCH failure that happens between

‘Assignment Complete’ received from BTS and ‘Disconnect’ triggers the

counter. ‘Disconnect’ for A subscriber is received from MS. ‘Disconnect’ for B

subscriber is received from MSC.

•‘FACCH Call Setup’:Every call dropping TCH failure that happens between

‘Channel Mode Modify Act’ received from BTS and ‘Disconnect’ triggers the

counter. ‘Disconnect’ for A subscriber is received from MS. ‘Disconnect’ for B

subscriber is received from MSC.

•‘TCH Handover’:

Source side: Every call dropping TCH failure that happens between

‘Assignment Complete’ received from BTS and release of the old channel

triggers the counter.

Target side: Every call dropping TCH failure that happens between handover

is completed and ‘Disconnect’ triggers the counter.

‘Disconnect’ for A subscriber is received from MS. ‘Disconnect’ for B

subscriber is received from MSC. The counter triggering is the same in

source and target sides for ‘Internal intra-cell’, ‘Internal inter-cell’ and

‘External handover’ handovers Note! Option to set the breakdown focus to

counter 002071 requires S11.5 CD5.1


S12 BSS CS Measurements Counter Block Pictures

S12 BSS CS Measurements

• ‘71 MS Capability Indication Measurement’ updated slide

• ‘77 FER Measurement’ updated slide

• ’107 AMR RX Quality Measurement’

• ‘108 DFCA SAIC measurement’


‘71 MS Capability Indication Measurement’ updated slide

Measurement info:

MS Capability Indication measurement provides

cell-specific information on the capabilities of the

mobile stations. The counters of this measurement

are updated on TCH only.

Ph1

71000 (S9)

Measurement data:

MS reporting time by MS categories :

Object info: Measurement object level is BTS

Single GSM900

71004 (S9)

Single GSM1800

71006 (S9)

Tri Band

71008 (S9)

Ph2

71001 (S9)

Single EGSM900

71005 (S9)

Dual Band

71007 (S9)

GSM 850

71033 (S10)

Single GSM1900

71035 (S10.5)

DTM

71038 (S12)

SAIC

71039 (S12)

Single GSM900

71009(S9)

Measurement data:

TCH seizures by MS categories :

Single GSM1800

71011(S9)

Tri Band

71013(S9)

GSM 850

71034(S10)

Single EGSM900

71010(S9)

Dual Band

71012(S9)

Multislot incabable

71014(S9)

Single GSM1900

71036(S10.5)

DTM

71037 (S12)

SAIC

71040 (S12)

MultiS Class 1

71015(S9)

MultiS Class 2

71016(S9)

MultiS Class

18

71032(S9))

….

Ph1

71002(S9)

Ph2

71003(S9)


’77 FER Measurement’ updated slide

BTS id

77000

TRX id

77001

Codec type

77002

FH type

77006

TRX freq

77005

Ext.area

77003

Freq.grp.id

77004

Averaging window size

(1-32 SACCH frames)

77014

Estimated

samples

77031

Class0

77015

Class1

77016

Class5

77020

Class4

77019

Class3

77018

Class2

77017

Class7

77022

Class6

77021

B1

77007

UL FER

Class0

77023

Class1

77024

Class5

77028

Class4

77027

Class3

77026

Class2

77025

Class7

77030

Class6

77029

DL FEP

B2

77008

B3

77009

B4

77010

B5

77011

B6

77012

B7

77013

Boundaries of frame erasure ratio (%), modifiable as meas.parameters

2% 4% 6% 8% 10% 12% 14% Default values

0% 100%

Class0

77032

Class1

77033

Class5

77037

Class4

77036

Class3

77035

Class2

77034

Class7

77039

Class6

77038

DL FER

Measurement data:

Parameter data:

Codec types: 1 = HR 2 = FR 3 = EFR 4 = AMR HR 7.95 . . . 9 = AMR HR 4.75 10=AMR FR 12.2 . . . 17=AMR FR 4.75 Class0

77040

Class1

77041

Class5

77045

Class4

77044

Class3

77043

Class2

77042

Class7

77047

Class6

77046 SAIC DL FER (S12)

Object data:

Measurement info:

Frame Erasure Rate is the best available indicator in a GSM system to assess the Voice Quality provided in a network.

It represents the percentage of frames being dropped due to high number of non corrected bit errors in the frame.

The correlation of BER (reported by the MS) and FER (Voice Quality indicator) is not constant as the efficiency of the

error correction mechanism varies with different techniques. The BER reported by the mobiles is the figure measured

before the decoding process, whereas the FER is associated with the corrected BER after the decoder.

MSs that do not support ‘Enhanced Measurement Report’ are not able to report downlink FER. Downlink FER can be

estimated by using correlation counted for each channels profile. FER value replace BER value in handover and power

control algorithms in the frequency hopping systems.


Object data:

BTS_ID 107000

TRX_ID 107001

ID_OF_FREQUENCY_GROUP107002

TRX_FREQUENCY 107003

TRX_TYPE 107004

’107 AMR RX Quality Measurement’

Measurement info: The AMR RX Quality Measurement (12) collects statistics of received ber BASED signal quality both in uplink

and downlink directions for each AMR bitrate. The Bit Error Ratio (BER) based signal quality counters correspond to the eight RX Quality

bands. The counters are updated by the RX Quality values as measured by the MS (downlink) and BTS (uplink) and reported in the radio

link measurement messages. There are separate UL and DL counters for each quality band and FR as well as for HR. There are also DL

quality counters for Single Antenna Interference Cancelation (SAIC) capable MSs.

FR_475_UL_RXQ_0 107005 FR_740_UL_RXQ_0 107069

FR_475_DL_RXQ_0 107006 FR_740_DL_RXQ_0 107070

… …

FR_475_UL_RXQ_7 107019 FR_740_UL_RXQ_7 107083

FR_475_DL_RXQ_7 107020 FR_740_DL_RXQ_7 107084

FR_515_UL_RXQ_0 107021 FR_795_UL_RXQ_0 107085

FR_515_DL_RXQ_0 107022 FR_795_DL_RXQ_0 107086

… …

FR_515_UL_RXQ_7 107035 FR_795_UL_RXQ_7 107099

FR_515_DL_RXQ_7 107036 FR_795_DL_RXQ_7 107100

FR_590_UL_RXQ_0 107037 FR_102_UL_RXQ_0 107101

FR_590_DL_RXQ_0 107038 FR_102_DL_RXQ_0 107102

… …

FR_590_UL_RXQ_7 107051 FR_102_UL_RXQ_7 107115

FR_590_DL_RXQ_7 107052 FR_102_DL_RXQ_7 107116

FR_670_UL_RXQ_0 107053 FR_122_UL_RXQ_0 107117

FR_670_DL_RXQ_0 107054 FR_122_DL_RXQ_0 107118

… …

FR_670_UL_RXQ_7 107067 FR_122_UL_RXQ_7 107131

FR_670_DL_RXQ_7 107068 FR_122_DL_RXQ_7 107132

HR_475_UL_RXQ_0 107133

HR_475_DL_RXQ_0 107134

…

HR_475_UL_RXQ_7 107147

HR_475_DL_RXQ_7 107148

HR_515_UL_RXQ_0 107149

HR_515_DL_RXQ_0 107150

…

HR_515_UL_RXQ_7 107163

HR_515_DL_RXQ_7 107164

HR_590_UL_RXQ_0 107165

HR_590_DL_RXQ_0 107166

…

HR_590_UL_RXQ_7 107179

HR_590_DL_RXQ_7 107180

HR_670_UL_RXQ_0 107181

HR_670_DL_RXQ_0 107182

…

HR_670_UL_RXQ_7 107195

HR_670_DL_RXQ_7 107196

HR_740_UL_RXQ_0 107197

HR_740_DL_RXQ_0 107198

…

HR_740_UL_RXQ_7 107211

HR_740_DL_RXQ_7 107212

SAIC_FR_475_DL_RXQ_0 107213

…



…



…



…



…



…



…



…


SAIC_HR_475_DL_RXQ_0 107277

…



…



…



…



…


FR RX Quality data: HR RX Quality data:

SAIC RX Quality data:


‘108 DFCA SAIC measurement’

Measurement info:

DFCA SAIC measurement (S12) collects DFCA

assignment information related to SAIC target C/I.

Object info: Data is reported for connection types

FR/EFR, 14.4 Data, HR, AMR and

AMR HR for each BTS.

108000 SAIC_CI_TARGET

108001DFCA_SAIC_CI_TG_DL 108002 DFCA_SAIC_CI_1_OVER_TG_DL 108003 DFCA_SAIC_CI_2_OVER_TG_DL 108004 DFCA_SAIC_CI_3_OVER_TG_DL … 1080019 DFCA_SAIC_CI_18_OVER_TG_DL 1080020 DFCA_SAIC_CI_19_OVER_TG_DL 1080021 DFCA_SAIC_CI_20_OVER_TG_DL 108022 DFCA_SAIC_CI_OVER_20_DL 108023 DFCA_SAIC_CI_1_BELOW_TG_DL 108024 DFCA_SAIC_CI_2_BELOW_TG_DL 108025 DFCA_SAIC_CI_3_BELOW_TG_DL … 108035 DFCA_SAIC_CI_13_BELOW_TG_DL 108036 DFCA_SAIC_CI_14_BELOW_TG_DL 108037 DFCA_SAIC_CI_15_BELOW_TG_DL 108038 DFCA_SAIC_CI_BELOW_15_DL

108039 SAIC_INTRF_CI_TG_DL 108040 SAIC_INTRF_CI_1_OVER_TG_DL 108041 SAIC_INTRF_CI_2_OVER_TG_DL 108042 SAIC_INTRF_CI_3_OVER_TG_DL … 108057 SAIC_INTRF_CI_18_OVER_TG_DL 108058 SAIC_INTRF_CI_19_OVER_TG_DL 108059 SAIC_INTRF_CI_20_OVER_TG_DL 108060 SAIC_INTRF_CI_OVER_20_DL 108061 SAIC_INTRF_CI_1_BELOW_TG_DL 108062 SAIC_INTRF_CI_2_BELOW_TG_DL 108063 SAIC_INTRF_CI_3_BELOW_TG_DL … 108073 SAIC_INTRF_CI_13_BELOW_TG_DL 108074 SAIC_INTRF_CI_14_BELOW_TG_DL 108075 SAIC_INTRF_CI_15_BELOW_TG_DL

108076 SAIC_INTRF_CI_BELOW_15_DL

The SAIC C/I target value

The number of DFCA

assignments where the

downlink C/I level for the

connection equals the target

SAIC C/I + 1 dB

The number of DFCA



connection is higher than

the target SAIC C/I + 20 dB

The number of DFCA



connection equals the

target SAIC C/I -2 dB

The number of DFCA



connection is lower than the

target SAIC C/I -15 dB

The number of DFCA



connection equals the target

SAIC C/I

The number of DFCA


downlink C/I value of the

most restrictive


target SAIC C/I value

The number of DFCA


downlink C/I level of the

most interfered


SAIC C/I target + 1 dB

The number of DFCA



most interfered

connection is higher than

the SAIC C/I target + 20

dB

The number of DFCA



most interfered


SAIC C/I target -2 dB

The number of DFCA



most interfered

connection is lower than

the SAIC C/I target -15 dB

One of these is updated

in a successful DFCA

assignment One of these is updated in a successful

DFCA assignment

Updated once in a measurement

period

Measurement data:

Date post:	19-Jan-2016
Category:	Documents
Upload:	stainohlechelamokoena
View:	193 times
Download:	23 times

BSS S12 CS Counter Block Pics

Documents