kpi+rules

1 © Nokia Siemens Networks Presentation / Ksu /2008For internal use

KPI- Rules

2 © Nokia Siemens Networks Presentation / Ksu / 2008For internal use

KPI list, CS

• SDCCH Blocking (blck_5a)

• SDCCH_Drop (sdr_1a, sdr_4)

• CSSR, Call Setup Success Rate ( csf_11, csf_13a, csf_15) • TCH Blocking (blck_8i)

• Interference, coverage• TCH_Drop (dcr_32a, dcr_5a)

• HO Fails (hfr_2a)


KPI list, PS

• GPRS attach success ratio (sgsn_507, sgsn_569c)

• PDP context activation success ratio MO (sgsn_535a)

• Signaling problems before TBF ( pgn_3a,pgn_10, blck_21b,rach_4,rach_9)

• TBF Failure (1-TBF Success ratio = 1 – TBF_67)

• Throughput (trf_234, trf_236, trf_233c, trf_235b,llc_3a)

• PS Blocking (TBF_16a,TBF_33a)

• Cell re-selection (TBF_64)


KPI – rules , CS


KPI- Rules, SDCCH BlockingSDCCH Blocking

>X%

Is dynamic sddch active

Is dynamic sdcch reaching max values

in some moment

Is combined sdcch used

yes

yes

Check unavailability in the cells,

averarage available sdcch

Availability OK

Check sdcch blocking. Can sdcch capacity be added

without tch blocking

SDCCH blocking is high

yes

No

Yes, remove combined sdcch

No, check parameterValues and make

corrections

No, activateDynamic sdcch

Yes, make corrections

Case closedNo

Yes, add sdcch capacity

Add TRX and add Sdcch capacity

sdcch Blocking is still high

No

Yes

Is high sdcch traffic due to Location updates. If yes, can LU area be optimized? Check also PRAU parameter, can the value

be increased?

noYes, Optimize LU

area border

no

ND_211ND_130Cngt_2Blck_5

Blck_5b

ND_139,ND_131ND_130, uav_22

csf_1a,csf_11Ava_45a

ND_211c1154

ND_211c2032

NetAct PlannerP_nbcs_cc_pm

ND_211


KPI- Rules, SDCCH Drop

SD DCR > 2% andSD DCRnum > 10

Drops due to RF Reasons

Drops due to Abis Reasons

NoDrops due to A-interface Reasons

NoDrops due to

other ReasonsNo

Case Closed

No

RF Abis A Other

Yes Yes Yes Yes

Yes

No

ND_166


KPI- Rules, SDCCH Drop (RF)

RF drops

Check RX Statistic,qquality level distribution. Any signal

level problems = samples in bad signal

leve <-100dBm

Check RX Statistic,qquality level distribution. Any Bad Quality problems = Lots of samples in

good signal level and bad quality

SDDCR still too high

Any balance problems between UL and DL.

Signal level problems. Improve signal level

TRX is broken (sample

distribution is somehow strange, for example only

quality 4 samples)

Change new frequency based on interference

matrix

Yes

Yes

Not CorrectMake

corrections

YES Check TRX, Combiners, configuarions, diversity and power parameters

No

Yes

No

YES,Change

the TRX /combiner

Yes

P_nbsc_RX_Statistics,Counter (q0...q7)ul and dl all levels

ND_204,c1003

Check that power control parameters UL / DL are correct

All Alarms are checked and abis trace is

done

Investigate alarms. If problems are not

solved, activate abis trace

Trace has been measured long enough. Any

problems found

Investigate log files. Check DX causes

Any Improvements

Make corrections

SDDCR still too high

P_nbsc_RX_Statistics,(q0..q7) <100dBm

P_nbsc_Link_balanceND_191, ND_195

No

Correct

No Yes

See doc Call related DX causes in BSC,

Activate

Yes

No

Yes

If The trace was not long enough, activate another trace

Case Closed

Add-new site-lna-new sector-more gain antenna

Optimizer, NetAct Planner

No

Trace was long enough,

not any problem

was found

No

PoC parameters


ND_204

P_nbsc_RX_Statistics,ND_204

No

alarms


KPI- Rules, SDCCH Drop (abis)

Abis>X%

Check abis drops.Is the main reason sdcch_abis_fail_call

Check RX Statistic table or ND report 204, UL/DL level distribution. Any Bad Level problems = samples in bad

signal level

Still Abis drops and problems

Any availability problems. Check sdcch availability

Check Co BSIC + BCCH problems, any site with same BSIC +

BCCH is existing < 50km

Check t3101 expired, is the value almost

same as sdcch_abis_fail_call

Check ghost reservations, c3030 values. Is this the

main reason

Check if cells are located near LA

border more sdcch traffic

Any Improvements Yes

Yes

No

No

No

No

No

Yes, Try to Reduce overlapping

Over borders etc.Tilting? Rehoming can

Sometimeshelps, if areas

Are not optimized

Yes

No

No

Yes, changebsic

Yes, unlockTRX’s

Yes, see Interference

analysis

P_nbsc_rx_statistics

Any balance problems between ul and dl. Check ND 195, ND 191 or link

balance table

Check that power control parameters UL / DL are

correct

Check RX Statistic quality/level distribution. Any Bad Quality problems = Lots of

samples in good signal level and bad quality

Signal level problems. Improve

signal level

TRX is broken (sample distribution is somehow

strange, for example only quality 4 samples)

Change new frequency based on interference

matrix

No

Yes

No

Has any parameter changes done

Yes

No

Correct

No

Yes, Check TRX,Combiners,

Configurations,Diversity and

Power settings. Make corrections

Not CorrectMake

corrections

Options:-add site, sector-add lna-change antenna type

Adjust rx_lev_access_minrx_lev_min_cell values little lower. Caution, This can increase TCH Drops.

No

Yes

Yes

Case Closed No

Optimizer, NetAct Planner

Yes,Change

TRX

P_nbsc_trafficCounters(1072-1080)

P_nbsc_service, counter

57020

NetAct Planner

ND_131,ND_139

C3030


ND_204


KPI- Rules, SDCCH Drop (A)

A>X%

A interface problems. Alarms

are checked and A interface trace is

done

Investigate alarms.If problems

are not solved, activate A trace

Any improvements

Any problems found. Trace

was long enough

Make corrections

Check ET lines in the BSC and

transcoders /TCSM. Any problems

Repair ET lines

Still A drops or problems

No

Activate

No

No

Yes

Yes

Alarms Are

Solved

Yes

Trace was not long

enough

Case Closed

Yes

No

Trace was Long enough. Not

An problem was found

Investigate log files. Check DX

causes, see document Call

related DX causes in BSC

No

alarms


KPI- Rules, SDCCH Drop (other)

Other

Lapd fails BTS failsNetw Act

FailsUser Act, bcsu,

resetsStill lots of other drops

Check all the alarms

signalling fails or PCM fails.

Check transmissio / parameters

Yes

No

TRX or BTS fails. Check

that BTS/ TRX are working

properly

Yes

No

Configuration problems,

check configurations

Yes

No

Resets or act fail channel

failures

Yes

No

Case Closed No

Yes


KPI- Rules, CSSR, Call Setup Success Rate

•SDCCH access ( csf_11)

•SDCCH success(csf_13a, csf_13b)

•TCH access(csf_15)

getservice

getSDCCH

establishSDCCH

connection

getTCH

establishTCH

connection

callphase

releasephase

Call Completion Rate (CCR) orDropped Call Rate (DCR)

Call Setup Success Rate CSSR orCall Setup Failure (CSF)

SDCCHBlocking(system)

and

SDCCH call

Blocking

TCHBlocking(system)

and

TCH CallBlocking

SDCCHSuccess Rate

Overall Call Success Rate (OCSR) orOverall Call Failure (OCF)


057019 SERVED_SDCCH_REQ Number of served SDCCH requests.

• UPDATED: When an SDCCH channel is successfully reserved. This counter is updated with all SDCCH requests, except in handovers.

057018 SERVED_FACCH_REQ Number of served FACCH call requests.

• UPDATED: When a TCH channel is successfully reserved for an FACCH call set-up. A TCH is reserved, because there is a congestion situation on the SDCCH.

057017 SDCCH_REQNumber of SDCCH requests. When an SDCCH channel is requested from the RRM.

• This counter is updated with all SDCCH requests, except in handovers.

KPI- Rules, CSSR : csf_11 (Probability of having an available SDCCH when needed)


MS BTS BSC MSC

Paging_CommandPaging

Paging

Paging_Request

To all BTS in LA

INTAT

Radio access part (CCCH)Channel_Request

Channel_Required

Channel_Activation

Channel_Activation_Ack

Immediate_Assign_CommandImmediate_Assign

DDCH establishment partSabm

Establish_Indication

Paging_Response

Ua

57017 SDCCH_REQ, 57018 SERVED_FACCH_REQ, 57019 SERVED_SDCCH_REQ

csf_11

KPI- Rules, CSSR : csf_11 (Probability of having an available SDCCH when needed)


Counter explanation:

057028 TCH_CALL_REQ Number of TCH call requests.

• UPDATED: When the TCH channel is requested from the RRM. This counter includes all TCH requests, except TCH to TCH handovers.

057023 SDCCH_NEW_CALL_ASSIGN Number of SDCCH new call assignments.

• UPDATED: When an ESTABLISH_INDICATION message is received on the SDCCH from the BTS in a case of a new call (including MOC, MTC, and emergency call). This counter is not updated in case of an IMSI detach or location update.

057024 SDCCH_HO_CALL_ASSIGN Number of SDCCH handover call assignments.

• UPDATED: When an ASSIGNMENT_COMPLETE or a HANDOVER_COMPLETE message is received on the SDCCH from the BTS in case of an SDCCH to SDCCH handover (including only calls: MOC, MTC, emergency call and re-establishments). In case of anexternal SDCCH to SDCCH handover or after an external handover, this counter is updated with all SDCCH assignments.

057022 SDCCH_RE_EST_ASSIGN Number of SDCCH re-establishment assignments.

•UPDATED: When an ESTABLISH_INDICATION message for a call re-establishment is received on the SDCCH from the BTS.

057026 SDCCH_RE_EST_RELEASE Number of SDCCH re-establishment releases.

•UPDATED: When the SDCCH is released (after a RF_CHANNEL_RELEASE message) without any problems and the SDCCH channel is reserved for a re-establishment. This counter is not updated after an external SDCCH to SDCCH handover.

057025 SDCCH_SMS_ASSIGN Number of SDCCH SMS assignments.

•UPDATED: MS originated: When an ESTABLISH_INDICATION message is received on the SDCCH from the BTS in case of an SMS. MS terminated: When an ESTABLISH_CONFIRM message is received on the SDCCH from the BTS in case of an SMS.

057027 SDCCH_HO_RELEASE Number of SDCCH handover releases.

•UPDATED: When the SDCCH is released without any problems and the SDCCH channel is reserved for a handover.

003059 CALL_ASSIGN_AFTER_SMS Number of calls started directly after an SMS on the already reserved SDCCH.

UPDATED: When an ASSIGNMENT REQUEST message is received directly after a successful SMS on SDCCH from the MSC.

KPI- Rules, CSSR : csf_13a (Probability of completing all the SDCCH signalling without drop)


MS BTS BSC MSC

PagingRadio access part (CCCH)

Channel_RequestChannel_Required

Channel_Activation

Channel_Activation_Ack

Immediate_Assign_CommandImmediate_Assign

DDCH establishment partSabm

Establish_Indication

Paging_Response

Ua 57021 SDCCH_ASSIGN, 57022 SDCCH_RE_EST_ASSIGN[in re-establishment], 57023 SDCCH_NEW_CALL_ASSIGN,

57025 SDCCH_SMS_ASSIGN 57033 TCH_NEW_CALL_ASSIGN [in FACCH call setup]

csf_13a

csf_11

Assignment_Request

Start T9108Physical_Context_Request

Physical_Context_ConfirmationStop T9108

SDCCH signalling up to TCH seizureAuthentication_RequestAuthentication_Request

Authentication_Response Authentication_Response

Identification_RequestIdentification_Request

Identification_Response Identification_Response

Ciphering_Mode_CommandEncryption_CommandCiphering_Mode_CommandCiphering_Mode_Complete Ciphering_Mode_Complete

SetupSetup

Call_Proceeding Call_Proceeding

57028 TCH_CALL_REQ, 57030 SERVED_TCH_CALL_REQ, 57031 SERVED_DR_REQ

3059 TCH_ASSIGN_AFTER_SMS

KPI- Rules,CSSR


Counter explanation:

057018 SERVED_FACCH_REQ Number of served FACCH call requests.

• UPDATED: When a TCH channel is successfully reserved for an FACCH call set-up. A TCH is reserved, because there is a congestion situation on the SDCCH.

057031 SERVED_DR_REQ Number of served DR requests.

• UPDATED: When the TCH channel is successfully reserved in case of a normal directed retry. This counter is also updated with S6 feature TCH Assignment to Super-reuse TRX in IUO (intra-cell/inter-cell directed retry). This counter is not updated with S7 feature Direct Access to Super-reuse TRX in IUO.

057030 SERVED_TCH_CALL_REQ Number of served TCH call requests.

• UPDATED: When the TCH channel is successfully reserved for a normal call. This counter is also updated with S7 feature Direct Access to Super-reuse TRX in IUO. This counter is not updated in a case of TCH to TCH handover, normal directed retry or S6 feature TCH Assignment to Super-reuse TRX in IUO (intra-cell/inter-cell directed retry).

057033 TCH_NEW_CALL_ASSIGN Number of TCH new call assignments.

• UPDATED: When an ASSIGNMENT_COMPLETE message is received on TCH from the BTS in a case of a new call. In a case of FACCH call set-up due to SDCCH congestion, this counter is updated, when an ESTABLISH_INDICATION message is received on the TCH from the BTS. In case of normal directed retry (inter-cell directed retry), this counter is updated, when a HANDOVER_COMPLETE message is received on the TCH from the BTS. This counter is also updated with S6 feature TCH Assignment to Super-reuse TRX in IUO (intra-cell/inter-cell directed retry) and with S7 feature Direct Access to Super-reuse TRX in IUO. If external SDCCH to SDCCH handover is made after a re-establishment, this counter is also updated.

KPI- Rules, CSSR : csf_15 (Probability of successfully getting the MS on the TCH


MS BTS BSC MSC

Assignment_Request

Start T9108

Physical_Context_RequestPhysical_Context_Confirmation

Stop T9108

Start T9103Channel_Activation

Stop T9103Channel_Activation_Ack

Assignment_Command Start T10,T3107

TCH seized

SDCCH signalling up to TCH seizureAuthentication_RequestAuthentication_Request

Authentication_Response Authentication_Response

Identification_RequestIdentification_Request

Identification_Response Identification_Response

Ciphering_Mode_CommandEncryption_CommandCiphering_Mode_Command

Ciphering_Mode_Complete Ciphering_Mode_Complete

SetupSetup

Call_Proceeding Call_Proceeding

(TA info)

TCH DROPS AFTER SEIZURETCH_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

57028 TCH_CALL_REQ, 57030 SERVED_TCH_CALL_REQ, 57031 SERVED_DR_REQcsf_14drops after this point

Assignment_Command (SDCCH)

Start T200 SABM (FACCH)Establish_Indication

UA (FACCH)Stop T200

Assignment_Complete (FACCH)Assignment_Complete

Stop T10,T3107

Assignment_Complete

SDCCH signalling: MS moves on TCH, SDCCH released

MS on TCH TCH DROPS AFTER ASSIGNMENT

(Connection Failure from BTS, DX cause >= 300)spare057044 /c57044 (S10.5)drop_after_TCH_assign c1202 (S11)

drops after this point

csf_15

csf_13

Dcr_8e


KPI- Rules, TCH Blocking

TCH Blocking>X%

Are there some broken cells, check

alarms, also Adjacent cells

Check RX statistics if there are cells with

broken TRX. Alarms are not always sent

Are POC parameter correct, check also

adjacent cells

No

No broken components

Check unavailability in the cells, also from

adjacent cells

Availability OK

Check if there are some missing

neighbours

TCH blocking is high

yes

All correct

Make corrections

Yes,Changebroken

components

Yes, corrections

Yes, make corrections

Case closedNo

Yes, add neighboursAdd TRX

Tch Blocking is still high

No

Have you checked all capacity features

No

Is Half Rate used and parameter optimized

No

yes

Yes

Yes

No. active HR and adjust parameters

Uav_15aND_139

Planner, OptmizerND_072

P_nbsc_rx_statisticsCounter (q0..q7)ul

and dl

NetAct,POC

Blck_8iTrf_1d

ND_135ND_138ND_139ND_211

ND_211

alarms

Block due to any events

near ?

No

Yes. Check blockTrend if it will drop

after event


KPI- Rules, coverage problems (dlq_2a and ulq_2a)

Here are some examples how different kind of problems can be found

Like Normal distribution HW Problem, TRX/combiner etc is brokenQ0 Q1 Q2 Q3 Q4 Q5 Q6 Q7 Q0 Q1 Q2 Q3 Q4 Q5 Q6 Q7

CL10 10645 8516 6813 5450 4360 3488 2791 2232 CL10 5323 4258 3406 2725 2180 1744 4563 9765CL15 47043 37634 30108 24086 9865 7543 5643 2345 CL15 11761 9409 7527 6022 9383 1886 65432 7675CL20 56204 44963 35971 28776 6574 10324 345 65 CL20 14051 11241 8993 7194 18271 2581 65438 63562CL30 200863 160690 128552 102842 17654 9876 145 28 CL30 33772 27017 21614 17291 75037 2469 18765 14523CL40 12785 10228 8182 6546 456 112 24 23 CL40 3196 2557 2046 1636 4938 28 3659 2648CL63 4583 1123 583 452 261 76 26 2 CL63 1146 281 146 113 3378 19 100 174

HW problem, Q4 amount of samples is strange Interference problemQ0 Q1 Q2 Q3 Q4 Q5 Q6 Q7 Q0 Q1 Q2 Q3 Q4 Q5 Q6 Q7

CL10 5323 4258 3406 2725 2180 1744 1395 1116 CL10 5323 4258 3406 2725 2180 1744 1395 1116CL15 23522 18817 15054 12043 18765 3772 2822 1173 CL15 23522 13234 10588 8470 13234 10588 8470 6776CL20 28102 22482 17985 14388 36542 5162 173 33 CL20 28102 2123 1699 1359 2123 1699 1359 1087CL30 67544 54035 43228 34582 150073 4938 73 14 CL30 67544 3634 2908 2326 3634 2908 2326 1861CL40 6393 5114 4091 3273 9876 56 12 12 CL40 6393 4091 3273 2618 4091 3273 2618 4532CL63 2292 562 292 226 6756 38 13 1 CL63 9987 7543 4323 3454 2275 1187 876 654

HW Problem, TRX/combiner etc is brokenQ0 Q1 Q2 Q3 Q4 Q5 Q6 Q7

CL10 200863 160690 128552 102842 17654 9876 7865 6543CL15 16543 13234 10588 8470 6776 2822 1173 234CL20 2654 2123 1699 1359 1087 173 33 65CL30 4543 3634 2908 2326 1861 73 14 28CL40 5114 4091 3273 2618 2095 12 12 23CL63 24 54 8 87 7 0 0 0

1

2

3

1. Lots of Q4 samples. Distribution is not OK HW problem. Site reset will help

2. Lots of bad signal level samples. TRX/Combiner is broken. If no HW problem Site is totally in wrong place, site is like transferring traffic to another cell ( cause level HO). Typically a HW problem

3. Lots of Q6 and Q7 samples. Distribution is not OK, no Q5 samples HW problems. Site reset or broken TRX

4. Typical normal interference problem.

Here are some examples how different kind of HW problems can be found

4


KPI- Rules, Interference analysis DL /UL

Rx Quality x Rx Level

Coverage Problem:Bad quality and Low Rx Level

Interference Problem:Bad quality and

High Rx Level

Good Quality

High Rv Level

HW Problem:

Bad Quality

for all Rx Levels

NWD report 204 model

HW Problem

All samples below -100dBm

CL10 <-100dBm

Same level – quality distribution for both UL and DL


KPI- Rules, Interference, UL

q0 q1 q2 q3 q4 q5 q6 q7-100dBm 10645 8516 6813 5450 4360 3488 2791 2232-95dBm 47043 37634 30108 24086 9865 7543 5643 2345-90dBm 56204 44963 35971 28776 16574 5676 845 65-80dBm 200863 160690 128552 102842 17654 3653 145 28-70dBm 1234 987 790 632 505 404 323 259-47dBm 24 19 15 12 10 8 6 5

MS power control can be seen here. If Power is reduced → no bad UL problems. BSC border is increasing good level samples


Bad interference problems. By POC parameter interference can be decreased, how power is adjusted etc. Also optimum MS power feature improves UL interference, no full power is sent after HO.


Bad quality sample due to signal level problems. Diversity should be checked, also possibilities to use LNA to improve UL signal level. Antenna place should be also checked if there are some obstacles near the antenna.


KPI- Rules, Interference, UL, examples

UL_q0 UL_q1 UL_q2 UL_q3 UL_q4 UL_q5 UL_q6 UL_q7 DL_q0 DL_q1 DL_q2 DL_q3 DL_q4 DL_q5 DL_q6 DL_q7-100dBm 251992 30668 20552 18417 18156 18286 16983 12478 27862 5537 5529 6069 6109 6107 5389 4119-95dBm 123653 1151 403 692 519 351 221 72 89094 4236 3853 3576 2893 2264 1372 584-90dBm 62938 247 144 288 353 129 62 29 142228 2732 2550 2356 1510 1114 774 404-80dBm 27005 51 65 149 177 82 40 16 222462 1523 1355 1552 716 812 1081 343-70dBm 2831 3 9 28 87 10 6 0 44504 91 123 151 81 101 191 88-47dBm 751 0 4 10 25 1 0 0 5994 49 17 17 12 29 65 10

Huge amount of UL bad samples. Cells is not working properly, it is like transferring traffic, UL quality/ UL level HO’s are triggering immediately. These kind of cells must be investigated.

UL_q0 UL_q1 UL_q2 UL_q3 UL_q4 UL_q5 UL_q6 UL_q7-100dBm 490 137 368 605 1014 1378 1830 2586-95dBm 8410 3768 3225 3023 2767 2304 1561 1859-90dBm 38512 5249 3066 2323 1692 1570 1191 1268-80dBm 219137 4600 2453 2311 1470 1724 1864 1221-70dBm 509591 2504 1812 3050 1271 1465 1649 337-47dBm 244302 582 711 1363 1713 873 671 87

UL_q0 UL_q1 UL_q2 UL_q3 UL_q4 UL_q5 UL_q6 UL_q7-100dBm 70004 5020 3500 2564 2232 1946 2190 2579-95dBm 80339 392 286 461 328 250 275 92-90dBm 106883 233 318 602 199 146 234 64-80dBm 246892 227 314 860 298 338 395 60-70dBm 254875 155 298 935 203 135 166 15-47dBm 23288 21 27 103 109 11 41 0

Some UL interference in good signal level. UL power control is not working properly. Ul power control is good indicator, if power is adjusted, there are no big problems in UL direction

There is no UL interference, or just a little. MS is adjusting power properly, there are only little samples in good UL signal level.



KPI- Rules, Interference, DL

Bad interference problem → signal level good (<-80dBm) and sometimes no better cell available. If better cell available and quality samples are 4 or worse → HO (reason quality or interference, depends on the parameter) Interference is causing drops.

Really bad interference problem → signal level is really good (<-70dBm) and usually no better cell available → no HO → samples can be seen in the table. Interference is causing drops.

Situation is “network is working properly” If there are quality 4 or worse samples → quality HO. Most of the samples are q4 samples. If lots of q5..q7 samples → interference problem and interference must be analyzed / removed. If quality HOs but no q5..q7 samples → better cell is available → no interference problems. In these signal levels overlapping exists and if handover reason is no PBGT, it will be quality HO. By parameter amount of quality HOs can be adjusted




Bad quality samples due to signal level problems. If PBGT overlapping is not existing → lots of quality HOs + level HOs (margin are lower than in PBGT).

Not interference problem, more signal level problem.

Check how much samples vs. HOs → are better cells available or not.


KPI- Rules, Interference, DL, examples

DL_q0 DL_q1 DL_q2 DL_q3 DL_q4 DL_q5 DL_q6 DL_q7-100dBm 12057 2827 3108 3952 4783 6200 7013 8156-95dBm 44818 4811 5041 5866 6587 7223 7259 6781-90dBm 98587 7107 7400 8334 8470 8781 7825 6162-80dBm 225919 7450 7731 8445 7726 7441 5695 3369-70dBm 88708 1014 971 998 751 688 689 367-47dBm 15881 84 109 122 104 167 199 184


There are almost as much samples Q5 and Q7 samples as Q 4 samples → even interference is really bad or there is no better cell available ( no ho’s after bad quality samples). These kind of interference cells should be optimized, otherwise there are lots of drops etc

There are no as much Q5…Q7 samples as Q4 samples → after interference samples Quality HO is done or the interference situation is not so bad, for example sampling is Q0,Q2,Q4,Q2,Q5,Q0,Q2,Q3,Q4,Q2 → quality HO is not triggering


There are bad quality samples only due to signal level problems.


KPI- Rules, Interference (internal / external)

•Internal Interference– Interference can be seen from stats or can be measured by scanner.

– Neighbor cells (DL) or mobiles (UL) are causing interference.

– By frequency / network planning interference can be decreased.

•External Interference– Interference can be seen from stats or can be measured by scanner.

– External radio frequencies are causing interference▪ Military use

▪ In the border area, interference is coming from other country.

▪ Some external wireless system (for example some wireless industry system) is causing interference

▪ Increased I level can be also due to external interference


TCH SEIZURES FOR NEW CALLtch_norm_seiz /c1009+tch_seiz_due_sdcch_con /c1099 (S5)+msc_i_sdcch_tch /c4044 +bsc_i_sdcch_tch /c4057+cell_sdcch_tch /c4074-tch_succ_seiz_for_dir_acc /c1165 (S7)

-tch_re_est_assign /c57032 (S7)

TCH DROPS AFTER SEIZURETCH_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 (S7)DROPS

CALLS

100 * %

STARTED CONVERSATIONSconver_started /c57015- msc_i_tch_tch /c4043

CONVERSATION DROPSdropped_calls /c57007

TCH DROPS AFTER ASSIGNMENTtch_new_call_assign /c57033+tch_ho_assign /c57034

-tch_norm_release /c57035-tch_ho_release /c57036

-tch_re_est_assign /c57032

TCH ASSIGNMENTS FOR NEW CALLtch_new_call_assign /c57033

-tch_re_est_assign /c57032

TCH RELEASEDisconnect from MS

RF CHN RELEASERf_channel_release_ack from BTS

CONVERSATION STARTED conn_ack to BTS

TCH ASSIGNED Assignment_complete from BTS

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

Dcr_8hDcr_5a

Dcr_3j

KPI- Rules, TCH Drop Call Ratios


KPI- Rules, TCH Drop

DCR > X% andDCRnum > XX

Drops due to RF Reasons

Drops due to Abis Reasons

NoDrops due to A-interface Reasons

NoDrops due to Transcoder

ReasonsNo

Drops due to other Reasons

No

Case Closed No

RF Abis A TR Other

Yes Yes Yes Yes Yes

Yes

No

ND_163


KPI- Rules, TCH Drop (RF)

RF drops>X%>X count

Check quality/level distribution. Any Bad

Quality problems = Lots of samples in good signal level and bad

quality

Check quality/level distribution. Any Bad

Level problems = Lots of samples in bad

signal level

Check cell parameters,

discrepancies?

DCR still too high


TRX is broken (sample distribution is somehow strange, for example only quality 4 samples)

Change new frequency based on interference matrix

TRX / combiner is broken, for

example only <-100dBm level

samples

Signal level problems. Improve coverage

Check TA statistics and Check all Neighbors. If lots of long distance samples and only nearest cells are neighbors, may be some neighbor cells are missing

Neighbors are missing

Check all HO parameters, any HOC parameter problems?

Check blocking in target cells. If blocking, add capacity to blocked cells

Check if HO fails are due to MSC/ BSC border. If bad values, check borders. OptimizeMSC/BSC borders

Make parameter corrections

Yes

Yes

No

Yes, change -TRX-Combiner-broken antenna

No

Yes

No

Yes, Change TRX /

Combiner

Check HOs to adjacent cells, Any bad HO problems to any adjacent

cells?

No

No

No

No Blocking

Yes, Add neighbors

Yes, Change

parameters

Yes, add capacity

No

YesYes

No

Case Closed No

Yes

P_nbsc_RX_StatisticsCounters(ul0..ul7,dl0..dl8)

ND_204

P_nbsc_HO_adjHfr_58,hfr_59

P_nbsc_power,Timing advanceND_232

OSS, Hoc parameters

P_nbsc_HO_adjBlck_19,blck_20

ND_150

OSS, BTS,Cell parameters

NetAct Planner, Optimizer


ND_204

-Add LNA -Add new site-Add new sector

alarms


KPI- Rules, TCH Drop (abis)

Abis>X%

>X count

All Alarms are checked and abis trace is done

Drops are happening in the release phase

Still high drops in Abis

interface

Check CC table, which phase

drops are happening

Investigate alarms. If problems are not solved, activate abis trace

Trace has been measured long enough. Any problems found

Any improvements

Make corrections

Investigate log files.

No

activate

Yes

Yes

Yes

No

AlarmsAre solved

If not long enough, activate another

trace

Yes

No

Yes

check the BTS release and the

timer 3109 expired values. >BTS

version 6.1 3109 expires in a BSC while waiting for

the Release indication.These are seen as abis drops.These are not real drop not

real abis problems

Check the parameters related to abis. BSC parameters

No

Case ClosedNo

Drops are checked andNot real Abis problems

P_nbsc_CC_PMAll counters

BTS configurations,

Pafile

OSS, BSC parameters

alarms

alarms


KPI- Rules, TCH Drop (A)

A>X%

>X count

A interface problems. Alarms

are checked and A interface trace is

done

Investigate alarms.If problems

are not solved, activate A trace

Any improvements

Investigate log files.

Check if there are errors, when MSC assign some pools

Any protocol error unspecified? Check

bug possibility

Any problems found. Trace

was long enough

Make corrections

Check ET lines in the BSC and

transcoders /TCSM. Any problems

Repair ET lines

Are parameters and timers

checked

Still A drops or problems

Check that A parameter values

are correct

Check that A timer values are correct

Check that sccp counter values are

correct

Make corrections

No

Activate

No

No

Yes No Yes

Yes

Alarms Are

Solved

Yes

Trace was not long

enough

Case Closed

Yes

No

No

Trace was Long enough. Not

An problem was found

ZNRI:NA0;ZNNI:1,C;

ZNMI:C;

ZOCI:1;

AlarmsMML commandsP_nbsc_et_bscP_nbsc_et_tcsm

All counters


KPI- Rules, TCH Drop (TR)

TR>X%

>Xcount

TR problems. Alarms are checked

Check CC table, in which phase TR drops

are happening

Still TR drops or problems

Investigate alarms.If problems are not

solved, activate abis trace (remote TR

failures

Any Improvements

Any problems found

Make corrections

Investigate log files.Check if failures are following some PCM either in Abis or A and

fix accordingly. Before Implementing HR in the BSC

& cells it is must to reconfigure the A

interfacelinks to support Dual Rate. Otherwise it will give

rise to high call failures mainly TCH_TR_fail due to

mismatch of coding between TCH in Radio & "A" interface.

NoIf release

phase, not real drops

If drops are happening in some specific codec HR/FR

issue investigate or is it more like

individual TR problem

If there some problems with

TCSM investigate. ICTF, how many fails are

ignored

Check that TR parameters are correct. If not, correct these

InvestigateNo

In release phase

Done

Not doneNot done

Trace Was not

Long enough

Yes

Alarms are solved

Check TR codec specific fails, run

Check TCSM statistics

Yes

NotIn

Release Phase

P_nbsc_CC_PMAll counters

Alarms

Done

Case Closed

No

Yes

Trace was long

enough, NoAny problem was found

ND_247ND_523,

ICTF parameter


KPI- Rules, TCH Drop (Other)

Other

Lapd fails BTS failsNetw Act

FailsUser Act, bcsu,

act failsStill lots of other drops


signalling fails or PCM fails.

Check transmissio / parameters

Yes

No

TRX or BTS fails. Check

that BTS/ TRX are working

properly

Yes

No

Configuration problems,

check configurations

Yes

No

Resets or act fail channel

failures

Yes

No

Case Closed No

Yes


KPI- Rules, HO failHO Fail

Any Bad interference in adjacent cells

Any bad signal level problems

No interfer

Check if HO fails are due to blocking

Ho fail is high

yes

Yes, add Capacity, TRX

Case closedNo No

ND_150ND_153ND_157


Check if fails are MSC incoming or

MSC outgoing fails

Check if fails are BSC incoming or

BSC outgoing fails

Check if fails are Intra HO Fails

ND_150ND_153

ND_150ND_153

ND_150ND_153ND_157

Check if adjacent with high fail% are working properly

No blocking

Yes, change Frequency or Tilt interferer

cells

Any broken components

No

No, all cells are OK

Yes, changeThese brokencomponents

Yes, improve coverage

-new site or LNA-New sector-More gain antenna


P_nbsc_rx_statisticsalarms

Are HO parameters

correct

No

No, optimize

parameters

Yes

Optimize MSC / BSC borders

No

Are HO parameters

correct

Yes

No, optimize

HO parameters

No

Check if HO fails are due to missing

neighbours

No

Yes, add neighbours

NetAct PlannerOptimizer

Optimize dominance areas,

overlapping, overshooting

Yes

There are interference in

some Frequency

yes

YesChange

Frequency

HOC HOC

P_nbsc_power_control

NetAct Planner

NetAct Planner

There are interference in some TSL’s

P_nbsc_RX_statistics

Ho fail is still high

No

Yes


KPI- Rules, HO fail

sum(msc_o_succ_ho + bsc_o_succ_ho + cell_succ_ho) Total HO success ratio = 100 * (-------------------------------------------------------------------------------- ) (ho_65)

sum(msc_o_ho_cmd + bsc_o_ho_cmd_assgn + bts_ho_assgn)

sum(a.msc_o_succ_ho + a.bsc_o_succ_ho + a.cell_succ_ho + a.msc_to_wcdma_ran_succ_tch_ho)

Total HO failure ratio = 100 * (1- -------------------------------------------------------------------------------------) (hfr_2b) sum(b.msc_o_ho_cmd + b.bsc_o_ho_cmd_assgn +

b.bts_ho_assgn+a.msc_gen_sys_wcdma_ran_ho_com)

/* handovers failing due to blocking */ sum(a.msc_o_fail_lack + a.bsc_o_fail_lack + a.cell_fail_lack

+ a.msc_to_wcdma_ran_fail_lack) HO failure ratio due to RF blocking = 100 * --------------------------------------------------------------------------------------- /* all HO attempts */ sum(b.msc_o_ho_cmd + b.bsc_o_ho_cmd_assgn +

b.bts_ho_assgn + a.msc_gen_sys_wcdma_ran_ho_com)

(hfr_55a)


KPI – rules , PS


KPI list, PS

• GPRS attach success ratio (sgsn_507, sgsn_569c)

• PDP context activation success ratio MO (sgsn_535a)

• Signaling problems before TBF ( pgn_3a,pgn_10, blck_21b,rach_4,rach_9)

• TBF Failure (1-TBF Success ratio = 1 – TBF_67)

• Throughput (trf_234, trf_236, trf_233c, trf_235b,llc_3a)

• PS Blocking (TBF_16a,TBF_33a)

• Cell re-selection (TBF_64)


KPI-rules, GPRS attach

GPRS attach

KPI taken only from SGSN counters

KPI taken from Drive test tool

GPRS attach, SGSN

yes

no

GPRS attach, test tool

yes

Check alsoCounter data



GPRS attach, SGSN

Problems with gprs attach

Is failure code #3, FAIL_GPRS_ATTACH_ILLEGAL_MS /

FAIL_COMB_ATTACH_ILLEGAL_MS:

Is failure code #6, FAIL_GPRS_ATTACH_ILLEGAL_ME /

FAIL_COMB_ATTACH_ILLEGAL_ME:

Is failure code #7, FAIL_GPRS_ATTACH_SIM_NOT_PROV / FAIL_COMB_ATTACH_SIM_NOT_PROV

SIM is not provisionedFor GPRS service

(For example 2G subscr are using 3G phones)-activate the service

MS is illegal-check MS

ME is illegal-check ME

Is failure code #8, FAIL_GPRS_ATTACH_ILLEGAL_ME /

FAIL_COMB_ATTACH_ILLEGAL_ME:

Is failure code #15, FAIL_GPRS_ATTACH_NO_CELL_IN_LA /

FAIL_COMB_ATTACH_NO_CELL_IN_LA:

Is failure code #12, GPRS_ATTACH_FAIL_LA_NA /

COMB_ATTACH_FAIL_LA_NA:

Is failure code #13, GPRS_ATTACH_FAIL_ROAMING_NA /

COMB_ATTACH_FAIL_ROAMING_NA:

Is failure code #11, GPRS_ATTACH_FAIL_PLMN_NA / COMB_ATTACH_FAIL_PLMN_NA:

SIM is not provisionedFor GPRS service

-activate the service

LA is not allowed-check LA

because roaming is not allowed in this LA

-check LA settings

Is failure code #96,99,100,111, GPRS_ATTACH_FAIL_PROT_ERROR /

COMB_ATTACH_FAIL_PROT_ERROR:

Other codes than previous codes orStill attach problems

GPRS services and the non-GPRS

services are not allowed-activate services

no suitable cells in the LA.

(For example 2G subscr are using 3G phones)

-check cells

Is failure code #14, FAIL_GPRS_ATTACH_SER_NA_PLMN /

FAIL_COMB_ATTACH_SER_NA_PLMN:

GPRS services are not allowed in this PLMN

-activate services

no

no

no

no

no

Get the GPRS attach failures statistic based on cause code from the Netact Tools (KPI Browser / Report

Browser) or Analyzer (e.g. Nethawk Analyzer) SGSN counters

Protocol error,Check c1072 à Radio

condition errors->improve radio conditions,

Interference, coverageCheck also these counters,

These are sub group of c1072

(1006, 1011,1012,1017,1018,1289,1290, 1291,

1292, 1293)

no

Case Closed

No

Yes, Trace is neededGn,Gb trace.

Analyze log files

Is failure code #17, Network failure

no

no

no

no

Check -home or roaming subs (IMSI)

-check HLR connectivity-check RAN if reject after RANAP

Is NMO1 in use

yes

No, Activate NMO1

No



GPRS attach, test tool

Problems with gprs attach

Are radio conditions good, signal level,

interference

Are there lack of gprs resources or signalling

resources

Are all attach failed > 10 requests

GPRS attach, SGSNYes,PS core

Problems-check statistics

noP_nbsc_RX_Statistics

Counters(ul0..ul7,dl0..dl8)ND_204

ND_135ND_138ND_139ND_211ND_130ND_802ND_290

Still problems with attach

Options-reduce interference, tilting, change freq-Improve coverage, site,secror, lna, Antenna type

Add signaling capacityAdd gprs territory capacity

no

PC/ MS settings are correct

Case closedno

no

No, correctsettings

yes


KPI-rules, PDP context activations

PDP context activation

Problems with PDP context activation

Is failure code #26, FAIL_MO_PDP_ACT_INSUF_RES /

MO_SEC_PDP_ACT_F_INSUF_RES:

Is failure code #27,

FAIL_MO_PDP_ACT_MIS_UNK_APN:

Is failure code #95…#101, #111, FAIL_MO_PDP_ACT_INV_PDP_ACTMSG /

MO_SEC_PDP_ACT_F_PROT_ERROR:

insufficient resources

Missing or unknown APN-change correct APN-Check #33

Is failure code #28, FAIL_MO_PDP_ACT_UNK_ADDR_TYPE:

Is failure code #30, FAIL_MO_PDP_ACT_ACT_RE_GGSN /

MO_SEC_PDP_ACT_F_REJ_BY_GGSN:

Is failure code #32, FAIL_MO_PDP_ACT_SERV_OPT_NS / MO_SEC_PDP_ACT_F_SER_OP_NS:

Is failure code #33, FAIL_MO_PDP_ACT_REQ_SE_OP_NS / MO_SEC_PDP_ACT_F_SER_OP_NSS:

Is failure code #31, FAIL_MO_PDP_ACT_REJ_UNSPEC /

MO_SEC_PDP_ACT_F_REJ_UNSPEC:

unspecified reasonGn,Gb trace needed.

Analyze log files

unsupported service option-check service options

unsubscribed service option-normally due to incorrect APN

à correct APN-implement OTA

Is failure code #35 FAIL_MO_PDP_ACT_NSAPI_USED:

Other codes than previous codes or

Still attach problems

unknown PDP address or PDP type

-check PDP adresses-implement OTA

activation has been rejected by the GGSN-check GGSN stats-check GGSN alarms-Check firewalls-trace Gi

Is failure code #29, FAIL_MO_PDP_ACT_WRONG_PASSWORD:

authentication failures-check settings

no

no

no

no

no

Get the session management (SM) attach failures statistic based on cause code from the Netact Tools (KPI Browser / Report Browser) or Analyzer (e.g.

Nethawk Analyzer)

NSAPI already in used-check settings

no

Case Closed

Yes, Trace is neededGn,Gb trace.

Analyze log files

Is failure code #41 MO_SEC_PDP_ACT_F_SEM_ERR_TFT

no

no

no

a semantic error in the TFT operation

No

Is failure code #34 MO_PDP_ACT_FAIL_SO_OUT_OF_ORD /

MO_SEC_PDP_ACT_F_SER_OP_OUT:

service option was temporary out of order

Is failure code #42 MO_SEC_PDP_ACT_F_SYN_ERR_TFT

syntactical error in the TFT operation

Is failure code #43 MO_SEC_PDP_ACT_F_UNK_PDP_CONT:

no

unknown PDP context

Is failure code #44 MO_SEC_PDP_ACT_F_

SEM_ERR_PF

no

no


SYN_ERR_PF:

semantic error in

the Packet Filter(s)

no


WITHOUT_TFT:

syntactical error in the

Packet Filter(s)

the PDP context is already activated

without TFT

no

no

no

invalid message content

or protocol error.-Gb,Gn traces are

neededGn,Gb trace.

Analyze log files


KPI-rules, Signaling problems before TBF

Signaling problems before TBF

PCH problems

Case Closed

AGCH problems RACH problems SDCCH problemsno

CS:-pgn_3a-pgn_6….pgn_9PS:-pgn_10….pgn_12-pgn_14

Blck_21b Rach_4,rach_9 no

PCH

yes

AGCH

yes

RACH

yes

SDCCH

yes

no


KPI-rules, Signaling problems before TBF(PCH paging)

PCH

Problems with paging

Problems with paging from

Aif.Check amount of ss7 links

yes

Problems with paging from Gb

Pgn_3ass7 links

Pgn_6,pgn_10..pgn_12

no

Problems with paging in Air

interface

noPgn,_7..pgn_9Pgn_14

Options:-CS immediate assign expiresà (check sdcch drops).-activate NMO1-Increase TRXSIG capacity 16->32 kbits/sec if lots of paging requests

Optimize Gb buffer size

Optimize capacity on Aif-If ss7 load >0.2Erl, à add ss7 links

Case Closedno

no

CS:-pgn_3a-pgn_6….pgn_9PS:-pgn_10….pgn_12


KPI-rules, Signaling problems before TBF(AGCH)

AGCHBlck_21b

NACK ratio of p-immediate

assignment requests is high

Is EGPRS traffic hifg

Trf_237byes

Yes, options:-implement PBCCH

Parameters are optimized

no, optimize-CALC-AG

BTS parameters

Case Closedno

Lack of signaling capacity

Problems with signal level, Interference,

link balance

Yes

Decrease LU updates-LA area size- periodic LU timer

Optimize RF:-improve imbalance-improve signal level-reduce interference, Tilting,freq change- rx_lev_access_min parameter

No


KPI-rules, Signaling problems before TBF(RACH)

RACH

Rach rejections or load are high

Ratio of PS RACH retries is high

Rach_9 yes

Reduce Interfernce:

-freq change-tilting

Is EGPRS traffic high

Trf_237b

Yes, options:-implement PBCCH

no

Parameters are optimized

BTS parametersno

no, optimize-RET

Case Closedno

Lack of signaling capacity

Problems with signal level, Interference,

link balance

Yes

Decrease LU updates-LA area size- periodic LU timer

Optimize RF:-improve imbalance-improve signal level-reduce interference, Tilting,freq change- rx_lev_access_min parameter

No


KPI-rules, Signaling problems before TBF(SDDCH)

• Check SDCCH Blocking earlier (CS)


KPI-rules, TBF Failure

TBF failure>X%

Check if there are signal level problems in the cell

yes

TBF failure problems

Check if there are interference problems in

the cells

No problems

Are ul Power control parameters correct?

IF EGPRS TBF establishment failures

are high, are GPRS TBF failures low

Yes, these are lowCheck MCA parameter Setting (8-PSK back – off

effect)

No, make corrections

Yes, reduce Interference (change freq,

Tilting etc)

YES Improve Signal level, add-new site/sector

.lna.more gain antenna

yes

Case Closed

TBF failure % is still high

no

No

no

P_nbsc_rx_statistics(q0...q7) ul and dl

P_nbsc_rx_statistics(q0...q7) ul and dl

EGPRS BTS parameters

ND_235, ND_216

Check that there is no congestions in the target

cells

no

Yes, there are Congestions. Reduce

congestions

Check that parameters IFP, TFP are correct

yes

Not correct.Make corrections

Improve dominance areas,

tilting, etc

no

ND_211

GPRS_POC

Check that SGSN is working

-Session_management-Mobility_management, --All counters-SGSN_KPIs

Not working,Gb,Gn traces are needed


KPI-rules, Throughput

Throughput

Case closed

Is there a signal level problem in

the cell

Is there an interference

problem in the cell

Throughput / TSL is low

Are there some EDAP congestions

No

yes

no

no

Are there some PCU congestions

Are there some Gb congestions

no

YES Improve Signal levels, add-new site/sector

.lna.more gain antenna

YesChange frequencyTilt interferer cell

Add EDAP capacity

YES,Add capacity

No

YES, add capacity

Is volume weighted throughput also

low.

no

Are link adaptation parameters correct

Is BS_CV_MAX parameter value

correct

yes

yes

Are BSSGP Flow control parameters

correct

Are there still throughput problems

yes

No

No, low tp /TSL is due

To bursty traffic

Is the throughput still low

No

NoMake

corrections

No, make corrections

yes

NoMake

corrections

Are there lots of GPRS users. More

than EDGE

Yes, low tp is due multi-Plexing withGPRS users

yes

Is the throughput still low

Yes

No

Yes, still problems

P_nbsc_RX_statistics(q0...q7) ul and dl

P_nbsc_RX_statistics(q0...q7) ul and dl

P_nbsc_dynamic abisND_280

P_nbsc_dynamic abis,ND_280

P_nbsc_frame relayND_284, ND_243

ND_802

EGPRS_BTS_parame

BS_CV_MAX

PRFILE,FIFILE

ND_226

Are EGPRS Power control parameters

correct

noEGPRS_BTS_parame

NoMake

corrections

yes

Check if problems with server data is

transferred or application data is

transferred

yes

Make Corrections


Maximize Throughput – Optimization Flowcharts

RLC/MAC TSL Data Rate Maximization

Multislot Usage Maximization

E2E Data Rate Maximization



trf_235b < 10 kbps or

trf_236 < 30 kbps GSM audit (list1)

yes

GSM optimization (list2)

GSM Network

Maximize multislot usage


trf_236 < 30 kbps

yes

no

Maximize TSL data rate

no


List1

•Signal level, C/I level, capacity audit

•Parameter and feature setup audit

•Neighbor audit

•Site arrangement audit

List2

•Signal level, C/I level, capacity optimization

•Parameter and feature setup optimization

•Neighbor and Location area optimization

•Site arrangement optimization (antenna tilt,

effective antenna height, etc)




trf_236 < 30 kbps

EDAP and PCU connectivity capacity optimization

(Refer to slide 9 and 10)

yes



trf_236 < 30 kbps

yes

no


no


Connectivity


RLC/MAC TSL Data Rate Maximization Resource allocation


trf_236 < 30 kbps Cell (re)-selection parameter optimization (list1)

yes

BTS selection parameter optimization (list2)


trf_236 < 30 kbps

yes

no



trf_236 < 30 kbps

yes

no


no


List1

•Deployment strategy optimization

•C1 and HYS parameter optimization

•C2 parameter optimization

•NCCR feature optimization

List2

•Deployment strategy optimization

•NBL and DIRE parameter optimization

•LSEG, GPL and GPU parameter optimization




trf_236 < 30 kbps

Uplink Penalty and

Uplink Threshold parameter audit / changing to recommended set

yes

TBF release and BS_CV_Max parameter audit / changing to recommended set


trf_236 < 30 kbps

yes

no



trf_236 < 30 kbps

yes

no


no


Feature parameterization




trf_236 < 30 kbps

LA (MCA) optimization and

PC parameter audit / changing to recommended set

yes

Multiplexing usage audit and optimization (list1)


trf_236 < 30 kbps

yes

no



trf_236 < 30 kbps

yes

no

Maximized TSL data rate

no


Feature parameterization

List1

•Reduce TSL sharing

•Avoid GPRS and EGPRS multiplexing on the same RTSL



CMAX=CDEF OR

0.75*CMAX < peak_gprs_territory

check list1CDEF > ava_44

List1

• If AMR and/or HR is used add Dual rate TSL

• If Dual rate not possible add TRX (need to check the PCU, A-bis and Gb capacity)

• CS traffic management (change HO parameters, resource management parameters)

• Increase nbr of dedicated PS timeslots

Increase CMAX

(or add/enable TRXs with GTRX=y)

check territory upgrade reasons Ho_61 = “big”

PS triggers

Trf_241

Increase CDEF

CS triggers

Trf_240

Decrease CDEF if PS traffic is small,

otherwise check the listed items

max(tbf_37c, tbf_38c) >1.2

AND

max(tbf_15, tbf_16) > 0.5% AND

blck_33 > 10%

Check list1

yes

yes

yes

yes



PSW Territory



EDAP and PCU connectivity capacity optimization

(Refer to slide 9 and 10)

yes

Maximized multislot usage


dap_7a > 150 min/GB

blck_32 > 0.1%

dap_9 > 30 min/GB

no

Connectivity



C_076007=“big” AND

C_076004 = 100%

C_076007=“big” AND

C_076004 < 100%

Blck_32 > Th3

Increase EDAP if Gb link size supports

and llc_3=smaller than BSC average in cells

PCU re-planning if llc_3=smaller than average

in BSC for cells connected to EDAP

Add new PCUs or PCU re-planning

Next EDAP/Cell

Yes

Yes

Yes


Connectivity



Dap_7a (or Dap_13) > Th1

Dap_9, Dap_10 > Th2

(Dap_15(DL), Dap_14(UL))

Blck_32 > Th3

Increase EDAP if Gb link size supports

and llc_3=smaller than average in BSC for

cells connected to EDAP

PCU re-planning if llc_3=smaller than average

in BSC for cells connected to EDAP

Add new PCUs or PCU re-planning

Next EDAP/Cell

Yes

Yes

Yes

Connectivity



E2E Data Rate Maximization (limited)

llc_3 < x kbps


trf_236 < 30 kbps

Flow control capacity (Refer to slide 12)

and parameter audit / changing to

recommended set (refer to TN819)

yes

HLR parameter audit / changing to

recommended set for different HLR profiles (list1)

yes

Maximized multislot usage

no

Maximize E2E data rate

llc_3 < x kbps

no

List1

•Delivery order

•Residual BER

•SDU error rate

•Delivery of erroneous SDUs


Gb Performance Analysis – FR for EGPRS

Frl_8a> utilization threshold

Yes

Increase Gb capacity

Frl_8a : Maximum received load % ( DL)

Gb bandwidth [kbps]

Restricting Gb link

utilization [%]

128 25

256 61

384 68

512 68

640 70

768 75

896 85

1024 90

Note: Maximum received load threshold depend on used application!


KPI-rules, PS Blocking

PS_Blocking>X%

Soft or Hard_Blocking. If hard, then it is more important to reduce

blocking

Are parameter correct (CDED,CDEF,CMAX, GTRX,MNDL,MNUL)

Check that timers are correct .(TRP,BFG)

Are there possibilities to increase dedicated territory, see also upgrade requests rejected due to CSW traffic

Is it possible to active / increase amount of HR

timeslots

Check if there are possibilities to reduce TBF

delayed release timers. Note impact on end user

performance

Still PS_blocking problems Still PS_blocking problems

Yes, blocking

correct

correct

no

Case Closed

no

no no

Yes, increaseSize of theDedicated

territory

No, makecorrections

No, makecorrections

no

yes

Yes, activeIncrease Half rate

ND_802,ND_290

GPRS BTS parameters

GPRS BTS parameters

ND_239,

PAFILE

Yes, adjusttimers

No

Add TRX / size of dedicated territory

yes

Is dual transferred mode used. This

can increase blocking.

Yes,DTM is Used and if

can not removed,

this is more capacity problems

No


KPI-rules, Cell re-selection

Cell reselection

Lots of cell re-selections

TBF_35a, TBF_36aTBF_64,TBF_63

c_95017c_72187

Check that there is no any broken components

Are there lots of overlapping and overshooting in the area.

Bad overlapping should be reduced

yes

Drive_testsND_232,ND_211


ND_204

Are there bad link balance problems. Links should be balanced to create better

dominance areas

no

Optimize imbalance:-power settings-add lna-add boosters

Reduce overlapping:-tilting-power settings-antenna place selection-antenna type, elektr tilt

Cell re-selection parameters are correct and optimized

No

Yes. Change broken components

-TRX, antenna, combiner

no

Case closedNo

optimize

C1,C2,C31/32 -parameters,

IFP,TFP

Are cell reselection features used and parameters

optimizedNote! Be careful with

parameters, dominance areas will be changed

All correctNACC,NCCR,- parameters

Optimize -features-parameters

Are BSC/ PCU areas optimized?

These will affect to the delay time of cell -reselection.

NetAct Planner,P_nbsc_ho_to_adj

ZEEI,ZESI

All correct

Optimize-BSC area-PCU area

Still lots of cell reselectios

yes

no

yes

kpi+rules

Documents

failgprsattachillegalme

analyze log

maximize multislot

normal directed

investigate

periodic lu

good signal

improve signal