Sei sulla pagina 1di 33

Slowing Down the Inter RAT Cell Reselections; Parameter Tuning & Monitoring Guide

Version 1.0 23.09.2007 Reunanen Jussi

For internal use 1 Nokia Siemens Networks

Presentation / Author / Date

Agenda
Treselection Hysteresis between 3G->2G and 2G->3G cell reselections PRACHRequiredReceivedCI and
PowerRampStepPRACHpreamble PrxAlpha PrxTarget

For internal use 2 Nokia Siemens Networks

Presentation / Author / Date

Treselection Introduction
Treselection: how long the reselection conditions must be fulfilled before reselection is triggered Impacts all cell reselections : Inter RAT, intra frequency and inter frequency The UE reselects the new cell, if the cell reselection criteria (Rcriteria, see next slide) are fulfilled during a time interval Treselection

For internal use 3 Nokia Siemens Networks

Presentation / Author / Date

Treselection Introduction
CPICH EcNo

UE starts GSM measurements if CPICH Ec/No < qQualMin + sSearchRAT First ranking of all the cells based on CPICH RSCP (WCDMA) and RSSI (GSM) Rs = CPICH RSCP + Qhyst1 Rn= Rxlev(n) - Qoffset1 Serving WCDMA cell calculation, with hysteresis parameter

SintraSearch

SinterSearch SsearchRAT qQualMin

Neighbour WCDMA or GSM cell calculation with offset parameter

No

Yes

Rn (GSM) > Rs (WCDMA) And Rxlev (GSM) >QrxlevMin Second ranking only for WCDMA cells based on CPICH Ec/No Rs = CPICH Ec/No + Qhyst2 Rn=CPICH_Ec/No(n)-Qoffset2
For internal use 4 Nokia Siemens Networks Presentation / Author / Date

Cell re-selection to GSM Cell re-selection to WCDMA cell of highest R value

Treselection Recommended Values


As this parameter impacts on all the cell reselections too long Treselection timer might cause problems in high mobility areas but too short timer causes too fast cell reselections and eventually causes also cell reselection ping pong Recommended value 1s should work in every conditions i.e. enough averaging to make sure that correct cell is selected However careful testing is needed to check the performance of different areas (Dense) Urban area, slow moving UEs with occasional need for fast and accurate (to correct cell) reselections e.g. outdoor to indoor scenarios or city highways in some cases cell by cell parameter tuning is performed to find most optimal value between 0s and 2s but typically 1s is optimal value when workload is considered as well Highways, fast moving UEs must reselect correct cell typically 1s works the best (however occasionally also 0s might be needed in fast speed outdoor to indoor cell reselections e.g. tunnels) Rural areas, slow or fast moving UEs need very often reselect between different RATs and make proper cell reselections even when the coverage is poor typically 1s works the best Location Area Borders, usually the coverage is fairly poor typically 1s works the best but sometimes to reduce location area reselection ping pong 1s is used when going from LA1 to LA2 and 2s from LA2 to LA1
For internal use 5 Nokia Siemens Networks Presentation / Author / Date

Treselection KPIs and Analysis


RRC connection request amount for inter RAT cell reselection ratio to all RRC Connection request causes When Treselection is increased this KPI should decrease
M1001C42INTR_RAT_C ELL_RE_SEL _ATTS M1001C0RRC_CONN_S TP_ATT

RRC connection request amount for registrations ratio to all RRC Connection request causes When Treselection is increased this KPI should decrease
M1001C46REGISTRATI ON_ATTS M1001C0 RRC_CONN_S TP_ATT

For internal use 6 Nokia Siemens Networks

Presentation / Author / Date

Treselection KPIs and Analysis


At the same time the CSSR and especially the RRC Connection Setup and Access Complete must be monitored The KPIs below should remain the same despite the Treselection modification or even get better If the CSSRs or RRC Connection Setup and Access Complete decrease the Treselection value should be decreased RNC_94d: RRC Setup and Access Complete Ratio from network point of view RNC_565e: CSSR CS Voice (RAS05.1) or RNC_565d : CSSR CS Voice (RAS05) The RRC Connection Setup attempts should decrease M1001C0 RRC_CONN_STP_ATT

For internal use 7 Nokia Siemens Networks

Presentation / Author / Date

Treselection KPIs and Analysis


Following RRC Connection Setup failure causes should decrease as the
amount of RRC Connection setup attempts is decreasing M1001C3 RRC_CONN_STP_FAIL_AC M1001C4 RRC_CONN_STP_FAIL_BTS M1001C5 RRC_CONN_STP_FAIL_TRANS M1001C530 RRC_CONN_STP_FAIL_IUB_AAL2 Above indicate saved resources and more detailed analysis can be done based on counters below BTS CE : RAS05.1 M5001C3 MAX_USED_C E_DL M5001C7 AVG_USED_C E_DL E_UL M5001C4 MAX_USED_ CE_UL M5001C8 AVG_USED_C E_DL M5001C6 MIN_USED_ CE_UL M5001C5 MIN_USED_C
Iub : AAL2 Path Average Reserved Bandwidth % : RAS05
M550C1SUM_RESER VED_CELL_R ATE 100%
For internal use 8 Nokia Siemens Networks

M550C7 NBR_SAMPLE S M550C0 AAL2_PATH_ GUAR_CELL_ RATE

Presentation / Author / Date

Hysteresis Between 3G->2G and 2G->3G Cell Reselections Introduction & Recommended Values
Parameters for cell reselections Qqualmin = -18dB Ssearch_RAT =2dB -> the 3G->2G cell reselection starts when Ec/No hits -16dB FDDQmin/GPRSfddQmin = -14dB (6) and QsearchP/Qsearch = always The cell reselection paramters 3G -> 2G and 2G -> 3G provide only 2dB hysteresis which is not enough and can been noticed from the RNC statistics as high amount of INTR_RAT_CELL_RE_SEL_ATTS from all the RRC Connection Setup Attempts Recommendation is to adjust the GFDM/FDM from -14dB to -10dB (or even up to -8dB) to provide 6 to 8 dB hysteresis between 3G to 2G cell reselection and 2G to 3G cell reselection On top of Treselection the above parameters will slow down further the 2G to 3G and 3G to 2G cell reselections

For internal use 9 Nokia Siemens Networks

Presentation / Author / Date

Hysteresis Between 3G->2G and 2G->3G Cell Reselections Introduction & Recommended Values
However careful testing is needed to check the performance of different areas UEs must reselect correct cell in case of 3G outdoor to certain 2G in these cases adjacency based parameter Adjqoffset1 can be used to prioritize certain 2G neighbor Impacts the R-criteria as shown below
First ranking of all the cells based on CPICH RSCP (WCDMA) and RSSI (GSM) Rs = CPICH RSCP + Qhyst1 Rn= Rxlev(n) - Qoffset1

For internal use 10 Nokia Siemens Networks

Presentation / Author / Date

Hysteresis Between 3G->2G and 2G->3G Cell Reselections KPIs and Analysis
RRC connection request amount for inter RAT cell reselection ratio to all RRC Connection request causes When hysteresis is increased this KPI should decrease
M1001C42INTR_RAT_C ELL_RE_SEL _ATTS M1001C0RRC_CONN_S TP_ATT

RRC connection request amount for registrations ratio to all RRC Connection request causes When hysteresis is increased this KPI should decrease
M1001C46REGISTRATI ON_ATTS M1001C0 RRC_CONN_S TP_ATT

For internal use 11 Nokia Siemens Networks

Presentation / Author / Date

Hysteresis Between 3G->2G and 2G->3G Cell Reselections KPIs and Analysis
At the same time the CSSR and especially the RRC Connection Setup and Access Complete must be monitored The KPIs below should remain the same despite the hysteresis modification or even get better If the CSSRs or RRC Connection Setup and Access Complete decrease the hysteresis value should be decreased RNC_94d: RRC Setup and Access Complete Ratio from network point of view RNC_565e: CSSR CS Voice (RAS05.1) or RNC_565d : CSSR CS Voice (RAS05) The RRC Connection Setup attempts should decrease M1001C0 RRC_CONN_STP_ATT

For internal use 12 Nokia Siemens Networks

Presentation / Author / Date

Hysteresis Between 3G->2G and 2G->3G Cell Reselections KPIs and Analysis
Following RRC Connection Setup failure causes should decrease as the
amount of RRC Connection setup attempts is decreasing M1001C3 RRC_CONN_STP_FAIL_AC M1001C4 RRC_CONN_STP_FAIL_BTS M1001C5 RRC_CONN_STP_FAIL_TRANS M1001C530 RRC_CONN_STP_FAIL_IUB_AAL2 Above indicate saved resources and more detailed analysis can be done based on counters below BTS CE : RAS05.1 M5001C3 MAX_USED_C E_DL M5001C7 AVG_USED_C E_DL E_UL M5001C4 MAX_USED_ CE_UL M5001C8 AVG_USED_C E_DL M5001C6 MIN_USED_ CE_UL M5001C5 MIN_USED_C
Iub : AAL2 Path Average Reserved Bandwidth % : RAS05
M550C1SUM_RESER VED_CELL_R ATE 100%
For internal use 13 Nokia Siemens Networks

M550C7 NBR_SAMPLE S M550C0 AAL2_PATH_ GUAR_CELL_ RATE

Presentation / Author / Date

Cluster JBK09

Hysteresis Between 3G->2G and 2G->3G Cell Reselections KPI Analysis Example
CLUSTER JBK09

Before 25% of Cells having >50% of all RRC


setups for inter RAT cell reselection
85-100%

Hysteresis from 2dB -> 6dB


100% 80% 60% 40% 20% 0%

Grouping1 <50% 50-70% 70-85%

After 12% of cells having >50% of all RRC


setups for Inter RAT cell reselection

Count of % INTR_RAT_CELL_RESEL

6/19/2007 1 3 12 41

6/20/2007 BEFORE 1 7 10 39

6/21/2007

7/10/2007

7/11/2007 AFTER

7/12/2007

85-100% 70-85% 50-70% <50%

1 9 47 7 50 6 51

1 8 48

Decreasing

Comparison Cluster JBK09 Percentage Distribution afterDate implementation:

Decreasing black and red colour as high percentage of Inter Rat Cell Reselection Increasing green colour as low percentage of Inter Rat Cell Reselection
For internal use 14 Nokia Siemens Networks Presentation / Author / Date

PRACHRequiredReceivedCI and PowerRampStepPRACHpreamble Introduction


During drive testing it is usually noted that there are call setup failures where the
network does not seem to respond to RRC Connection Requests with RRC Connection Setup message These are problems due to the spiky UL noise and due to that the power ramping is not aggressive enough to provide high enough Tx power for the terminal during open loop PC

MAJOR ROADS INNER & OUTER BLOCKED COUNT BREAKDOWN


RRC Connection Reject, 3 No Immediate Assignment, 1 No Setup, 1

No Radio Bearer Setup Complete, 2

No Alerting or Connect, 1
Presentation / Author / Date

N-300 and T300 expiry, 4

For internal use 15 Nokia Siemens Networks

PRACHRequiredReceivedCI and PowerRampStepPRACHpreamble Introduction


The parameters affecting to open loop power control are, in brackets are the recommended values: PRACH_preamble_retrans (7) RACH_tx_Max (16) PowerOffsetLastPreamblePRACHmessage (2 dB) PowerRampStepPRACHpreamble (2dB)

Ptx = CPICHtransmissionPower-RSCP(CPICH) +RSSI(BS) + PRACHRequiredReceivedCI (-20dB)


Downlink Not detected BS
UEtxPowerMaxPRACH PowerRampStepPRACHpreamble

L1 ACK / AICH

Uplink Preamble MS Preamble 1 2


Preamble PRACH_preamble_retrans # PRACH preambles transmitted during one PRACH cycle without receiving AICH response
RACH_tx_Max # preamble power ramping cycles that can be Presentation / Author / Date done before RACH transmission failure is

PowerOffsetLastPreamblePRACHmessage

Message part

For internal use 16 Nokia Siemens Networks

PRACHRequiredReceivedCI and PowerRampStepPRACHpreamble Recommended Values


Typically the parameter PRACHRequiredReceivedCI is set to -18-20dB
instead of the default -25dB (typically -20dB is enough) Also the parameter PowerRampStepPRACHpreamble is adjusted in case the problem of missed MT calls or call setup failures due to missing RRC Connection Setup still persists (default 2dB usually works the best but in some networks also 3dB is used) Check also the values for RACH_tx_Max and PRACH_preamble_retrans They should be set accordingly as: PRACH_preamble_retrans (7) RACH_tx_Max (16) Also the parameters should all be set in line as below: PowerOffsetLastPreamblePRACHmessage (2 dB) PowerRampStepPRACHpreamble (2dB) PRACHRequiredReceivedCI (-20dB) PRACH_preamble_retrans (7) RACH_tx_Max (16)
For internal use 17 Nokia Siemens Networks Presentation / Author / Date

PRACHRequiredReceivedCI and PowerRampStepPRACHpreamble Recommended Values


If for example PowerRampStepPRACHpreamble is set to 3dB then other
parameters should be adjusted with extra care to avoid unnecessary UL noise spikes Current defaults are tested to work properly without excessive increase in UL noise

For internal use 18 Nokia Siemens Networks

Presentation / Author / Date

PRACHRequiredReceivedCI and PowerRampStepPRACHpreamble KPIs and Analysis


The impact of this parameter has to be tested with drive testing (as in case the
PRACH preambles are not heard and therefore the RRC Connection Request is not heard by the BTS/RNC no RRC connection setup attempt counter is incremented) From the network statistics following should be monitored RNC_177b Noise Floor of the System RNC_101b Average Uplink load
Related to above the M1001C3 RRC_CONN_STP_FAIL_AC should not increase (if do then load
level reduction actions are needed, explained in PrxAlpha tuning section)

Secondary KPIs to follow


If the CSSRs or RRC Connection Setup and Access Complete decrease the hysteresis
value should be decreased RNC_94d: RRC Setup and Access Complete Ratio from network point of view RNC_565e: CSSR CS Voice (RAS05.1) or RNC_565d : CSSR CS Voice (RAS05) The RRC Connection Setup attempts should increase but the failures should not increase (especially AC rejections which are related to UL noise increase / Average UL load)

M1001C0 RRC_CONN_STP_ATT M1001C4 RRC_CONN_STP_FAIL_BTS M1001C5 RRC_CONN_STP_FAIL_TRANS M1001C530 RRC_CONN_STP_FAIL_IUB_AAL2

For internal use 19 Nokia Siemens Networks

Presentation / Author / Date

PRACHRequiredReceivedCI and PowerRampStepPRACHpreamble KPI Analysis Example Two values for PRACHRequiredReceivedCI tested (drive testing)
-20dB & -25dB : UL interference conditions are at the same level (reported
in SIB 7 for both cases)
PRACH req. C/I = -25dB
PRACH req. C/I = -20dB 100% 80% 100% 88% PRACH req. C/I = -25dB

PRACH req. C/I = -20dB

60% 40% 20% 0% 1 2 3 4 # RRC Connection Request Messages per call setup 0% 2% 0% 5% 0% 6%

100% 90% 80% 70% 60% 50% 40% 30% 20% 10% 0% 1 2 3 4 5 6 7 8

Clear improvement in number of needed RRC Connection Request messages per call. For 20dB 100% of established calls are setup with only 1 RRC Connection Request message

Clear improvement number of sent preambles per RRC Connection Request for 20dB case. For 20dB 50% of cases the needed number of preambles is <=4 where as for 25dB it is ~6.5 There should be significant improvement also for call setup delay

For internal use 20 Nokia Siemens Networks

Presentation / Author / Date

PRACHRequiredReceivedCI and PowerRampStepPRACHpreamble KPI Analysis Example

Two values for PRACHRequiredReceivedCI tested (drive testing)


-20dB -25dB UL interference conditions are at the same level
(reported in SIB 7 for both cases)
PRACH req. C/I = -25 PRACH req. C/I = -20

120.0% 100.0%
100% 99% 98% 97% 96% 95% 94% -25dB Call Setup Success Rate -20dB 96.2% 100.0%

80.0% 60.0% 40.0% 20.0%

3.5s - 3.7s

3.7s - 3.9s

3.9s - 4.1s

4.1s-4.3s

4.3s-4.5s

4.5s-4.7s

4.7s-4.9s

4.9s-5.1s

5.1s-5.3s

5.3s-5.5s

0.0%

<3.5s

Call Setup Delay (seconds) RRC Conn. Req. to Alerting

For internal use 21 Nokia Siemens Networks

Clear improvement in call setup delay for 20dB case. ~65% of the established calls are through with only 3.5 3.7s delay and the >5.5s delay tail disappears (in this case).
Presentation / Author / Date

>5.5s

PRACHRequiredReceivedCI and PowerRampStepPRACHpreamble KPI Analysis Example


AMR Voice Average Preamble Counts Average RACH_TX_Pwr average UL interference Video Average preamble count Average RACH_TX_Pwr average UL interference
1.

Before 2.40 -9.11 -102.42 Before 2.84 -6.95 -102.46

1st drive 2.01 -7.09 -102.07 1st drive 1.77 -6.45 -102.15

2nd drive 1.617 -6.581 -101.53 2nd drive 1.933 -6.888 -101.33

The number of resend for PRACH (Preamble Count) has reduced after the parameters changing, that mean shorter time to build the radio link. 1st drive is after PRACHRequiredReceivedCI been changed (-25dB -> -20dB), while 2nd drive is after RACH_tx_max been changed (8 -> 16) Meanwhile the RACH_TX_Pwr for both AMR and Video services is increased, which mean more power is consumed by the UE . The slighlty increased UL interference can be tried to be reduced by taking the alpha trimmed mean filter into use to filter the Prx measurements in BTS
Presentation / Author / Date

2. 3.

For internal use 22 Nokia Siemens Networks

PRACHRequiredReceivedCI and PowerRampStepPRACHpreamble KPI Analysis Example


AMR (MOC) Average CS call setup time (MOC) Call Setup Success Rate Before 2.36s 97.87% 1st drive 2.44s 99.30% 2nd drive 2.38s 100.00%

For internal use 23 Nokia Siemens Networks

Presentation / Author / Date

PrxAlpha Introduction
In case the indicators below have increased due to the open loop PC parameter modifications RNC_177b Noise Floor of the System RNC_101b Average Uplink load Or in generally if there are high amount of rejections due to following rasons M1001C3 RRC_CONN_STP_FAIL_AC M1001C80 RAB_STP_FAIL_CS_VOICE_AC M1001C85 RAB_STP_FAIL_CS_CONV_AC The BTS PrxTotal filtering parameters can be modified i.e. how the BTS averages the PrxTotal measurements before sending the results to the RNC in Radio Resource Indication messages

For internal use 24 Nokia Siemens Networks

Presentation / Author / Date

PrxAlpha Introduction
Frame mean of Prx_total is pre-calculated using arithmetic mean of the slot values (15 slots) Averaged frames are sorted based on PrxMeasAveWindow frames Filtered values are calculated by taking arithmetic frame mean values which are between ALPHA and (1-APLHA) defined by PrxAlpha N x lowest and highest measurements removed N x (1- 2) measurements remain
PrxMeasAveWindow = 10 & PrxAlpha = 0.2 Frame averages are calculated for 10 frames
Prx

2 max. & 2 min. values excluded : 6 values remaining


Final average Prx_total is calculated on the 6 values For internal use
25 Nokia Siemens Networks Presentation / Author / Date

Av. Frame measurements

PrxAlpha Introduction

The BTS is measuring : Prx Total

RADIO RESOURCE INDICATION (RRI) message Prx Total is reported to the RNC for LC, AC and PS usage, on every RRIindicationperiod (200 ms)

BTS uses ALPHA TRIMMED MEAN FILTER

PrxAlpha PrxMeasAvWindow Prx

BTS sends the LASTEST averaged measurement result to RNC every RRI period

Frame measurements

RRIx RRIx+1 RRIx+2 RRIx+n


Sliding window average result on every RRI period

RNC is calculating a sliding window averaged value over the values given by RRI messages

P rx _ total

1 m Pr x _ Totaln j m j 1

WinAcRabSetupUI
For internal use 26 Nokia Siemens Networks Presentation / Author / Date

PrxAlpha Recommended Values & Example


The PrxAlpha parameter value should be adjusted in 0.1 step intervals and KPIs monitored for each parameter value

PrxAlpha=0 PrxMeasAveWindow=10

RRIPeriod=200ms

PrxAlpha=0.1 Clearly some impact when changing the PrxAlpha -> suggests that the interference conditions are somewhat spiky and the PrxTotal values could be further reduced adjusting the PrxAlpha
For internal use 27 Nokia Siemens Networks Presentation / Author / Date

PrxMeasAveWindow=10 RRIPeriod=200ms

PrxAlpha KPIs and Analysis


Following indicators should be monitored for each PrxAlpha value RNC_177b Noise Floor of the System RNC_101b Average Uplink load M1001C3 RRC_CONN_STP_FAIL_AC M1001C80 RAB_STP_FAIL_CS_VOICE_AC M1001C85 RAB_STP_FAIL_CS_CONV_AC

For internal use 28 Nokia Siemens Networks

Presentation / Author / Date

PrxTarget Introduction
If the received Non-controllable power (RT) + the estimated power increase caused by the to be established RAB is above the PrxTarget, the RT RAB setup is rejected If the received Non-controllable power (RT) is above the PrxTarget limit then the RRC Connection Setup is rejected However note that for the following RRC Connection Request cause values the AC limits are not used (in UL nor in DL)
Emergency call Registration Detach Originating High Priority Signaling Terminating High Priority Signalling Inter-RAT cell re-selection Inter-RAT cell change order
For internal use 29 Nokia Siemens Networks

Presentation / Author / Date

PrxTarget Recommended Values & Example


In case the PrxAlpha tuning does not reduce the AC rejections then WCELL Name (All) Batch 4th Batch the PrxTarget can be increased to reduce the AC rejections TOTAL NUMBER OF RRC CONN STP FAIL AC Typically just 2dB increase provides significant reduction on the AC rejections Total Moving Avg
6000 5000 4000 3000 2000 1000 0 Sum of RRC_CONN_STP_FAIL_AC

Starting 16 June 2007 PtxTarget modified 4dB -> 6dB

6/1/2007

6/2/2007

6/3/2007

6/4/2007

6/5/2007

6/6/2007

6/7/2007

6/8/2007

6/9/2007

6/10/2007

6/11/2007

6/12/2007

6/13/2007

6/14/2007

6/15/2007

6/16/2007

6/17/2007

6/18/2007

6/19/2007

6/20/2007

6/21/2007

6/22/2007

6/23/2007

6/26/2007

6/27/2007

6/28/2007

6/29/2007

For internal use 30 Nokia Siemens Networks

Presentation / Author / Date

Date

6/30/2007

7/1/2007

PrxTarget Recommended Values


First the following counters should be checked
RNC_177b Noise Floor of the System
The above should be compared with the parameter value PrxNoise (WCEL) Max(RNC_177b, PrxNoise) = A RNC_101b Average Uplink load M1000C0 AVE_PRXTOT_CLASS_0, M1000C1 PRXTOT_DENOM_0 M1000C2 AVE_PRXTOT_CLASS_1, M1000C3 PRXTOT_DENOM_1 M1000C4 AVE_PRXTOT_CLASS_2, M1000C5 PRXTOT_DENOM_2 M1000C6 AVE_PRXTOT_CLASS_3, M1000C7 PRXTOT_DENOM_3 M1000C8 AVE_PRXTOT_CLASS_4, M1000C9 PRXTOT_DENOM_4

For internal use 31 Nokia Siemens Networks

Presentation / Author / Date

PrxTarget Recommended Values


First the following counters should be checked
The PrxTotal distribution should be calculated from above and the needed
PrxTarget distribution and average Average needed PrxTarget; A RNC101b Distribution can be calculated the same way A-AVE_PRXTOT_CLASS_X and the %
of samples for each class PRXTOT_DENOM_X/(PRXTOT_DENOM_1+ PRXTOT_DENOM_2+ PRXTOT_DENOM_3+ PRXTOT_DENOM_4+ PRXTOT_DENOM_5)

Then the PrxTarget parameter tuning should be performed in steps of 2dB


towards the highest calculated PrxTotal value Max PrxTarget value should not exceed 10dB (in normal conditions without any special interferer)

For internal use 32 Nokia Siemens Networks

Presentation / Author / Date

PrxTarget KPIs and Analysis


When the PrxTarget is modified following KPIs should be monitored

RNC_177b Noise Floor of the System RNC_101b Average Uplink load M1001C3 RRC_CONN_STP_FAIL_AC M1001C80 RAB_STP_FAIL_CS_VOICE_AC M1001C85 RAB_STP_FAIL_CS_CONV_AC M1000C0 AVE_PRXTOT_CLASS_0, M1000C1 PRXTOT_DENOM_0 M1000C2 AVE_PRXTOT_CLASS_1, M1000C3 PRXTOT_DENOM_1 M1000C4 AVE_PRXTOT_CLASS_2, M1000C5 PRXTOT_DENOM_2 M1000C6 AVE_PRXTOT_CLASS_3, M1000C7 PRXTOT_DENOM_3 M1000C8 AVE_PRXTOT_CLASS_4, M1000C9 PRXTOT_DENOM_4 RNC_94d: RRC Setup and Access Complete Ratio from network point of view RNC_565e: CSSR CS Voice (RAS05.1) or RNC_565d : CSSR CS Voice (RAS05)

For internal use 33 Nokia Siemens Networks

Presentation / Author / Date