3g optimisation cookbook_v2

7/16/2019 3G Optimisation Cookbook_v2

1/93

3G Optimisation Cookbook

3G Optimisation Cookbook


2/93

Contents

Cell Selection Parameters ..............................................................................................................................4

AAL2 resources availability in RNC (M800) RNC_602a ...............................................................................4

AAL2 Resource Reservation in RAN05(M800)...............................................................................................5

Performance Measurements for Transport..................................................................................................6

ISHO vs Failures................................................................................................................................................7

ISHO Analysis ................................................................................................................................................. 11

HSDPA Retainability Analysis ...................................................................................................................... 13

HSDPA Accessibility Analysis ....................................................................................................................... 15

Optimising Iub considering CID congestion .............................................................................................. 18

Check Iub Performance................................................................................................................................ 19

High in call drop rate - WCDMA (Nokia).................................................................................................... 20

Identify CSSR ................................................................................................................................................. 22

Application throughput downlink............................................................................................................... 25

Identify CSSR 2nd.......................................................................................................................................... 26

FMCG Parameter ........................................................................................................................................... 29

Export data Nemo to Mapinfo..................................................................................................................... 33

FMCS Parameter ............................................................................................................................................ 34

HOPS Parameter............................................................................................................................................ 40

ADJS Parameter ............................................................................................................................................ 42

3G HO Basic reporting events ..................................................................................................................... 44

3G Handover Types....................................................................................................................................... 45

RRC connection request .............................................................................................................................. 46

How to avoid ping pong (3G - GSM) ........................................................................................................... 47

2G -> 3G Cell Re / Selection....................................................................................................................... 47

3G --> 2G Cell Re / selection...................................................................................................................... 49

RAB setup failures for CS voice calls ......................................................................................................... 51

RAB setup failures for PS calls.................................................................................................................... 55

RRC active failures ....................................................................................................................................... 60

RRC access failures....................................................................................................................................... 63


3/93

RRC setup failures ........................................................................................................................................ 64

NEMO - - SYSTEM INFORMATION BLOCK .................................................................................................... 67

Nemo - - Ploting ............................................................................................................................................ 71

UMTS -- SOFT HANDOVER AND COMPRESSED MODE ................................................................................ 75

UMTS -- PARAMETERS THAT REQUIRE PLANNING..................................................................................... 78

3G - Optimization - Failure analysis .......................................................................................................... 79

UMTS -- INTERFERENCE AND POWER CONTROL ....................................................................................... 80

CDMA Network............................................................................................................................................... 82

UMTS -- CELL BREATHING AND SOFT CAPACITY....................................................................................... 83

UMTS -- interface dan Architectur nya ..................................................................................................... 85

GPRS Architecture and Interfaces ............................................................................................................. 87

GPRS (General Packet Radio Service) Overview ..................................................................................... 89

GPRS -- System information messages on BCCH ...................................................................................... 90

GPRS -- Channel Types................................................................................................................................. 91

EDGE (Enhanced Data rates for Global Evolution) .................................................................................. 92


4/93

Cell Selection Parameters

QrxlevMin (A_WCEL) Description: The minimum required RX level in the cell. This parameter is also used to

create value for the parameter DeltaQrxlevmin to be sent in SIB3/4 when the usedvalue is < -115.

Default value : -115 dBm

QqualMin (A_WCEL) Description : The minimum required quality level in the cell (Ec/No) Default : -18 db

UEtxPowerMaxPRACH (A_WCEL) Maximum UE transmission power on PRACH This parameter defines the maximum transmission power level a UE can use on

PRACH. The value of the parameter also affects the cell selection and reselectionprocedures.

The value of the parameter is sent to UE in the Cell selection and re-selection ofSystem Information Blocks 3 and 4 of the serving cell.

Default : 21 dBm

AAL2 resources availability in RNC (M800)RNC_602aAAL2 resource reservation success rate [%] :

The transport resource request success ratio [%] KPI describes the average success rate of thetransport resource reservation attempts for all AAL2 type connections

AAL2_SUCCEEDED - AAL2 signaling requests which have been successfully executed in A2SP

AAL2_REJECTED - AAL2 signaling requests which have failed for any reason. E.g. signaling failed or

uplink CAC rejectRES_EXT_CAP - Transport resources requests which are rejected by downlink CAC since there is notenough capacity in the external AAL2 path.

RES_INT_CAP - Resource reservations which are rejected by downlink CAC since there are no RNC-internal AAL2 processing resources available

RES_OTHER - Resource reservations which have failed for any other reason than CAC or signaling (forexample route analysis, parameter or DSP resource allocation problem)


5/93

AAL2 Resource Reservation in RAN05(M800)

M800 is useful for monitoring success of the resource reservation requests and able to point

out different type of failures, such as

Lack of Iub bandwidth

Lack of RNC capacity

AAL2 signaling failure

M800 collects the statistics per AAL2 user plane VCC object, note that there can be several

UP VCCs!

The resource reservation is performed in such order that all CAC reservations for RNC

internal and external (AAL2 path) resources are done before signaling

If the CAC actions are successfully completed, the signaling is started and RNC asks

BTS to arrange its resources accordingly

If the CAC actions fail, the signaling phase is not started at all and the signaling

counters are not aware of the connections rejected due to RNC AAL2 layer CAC

There are also dedicated counters for HSDPA connections resource reservations

The object of the measurement is the AAL2 path selected with ATM interface ID/VPI/VCI

identifiers

The statistics for the whole RNC (sum of all configured AAL2 paths counters) are

available by selecting the measurement object as interface-0/VPI-0/VCI-0


6/93

Also some failure situations, for example digit analysis failure, are updated only for

0/0/0 object because the actual VCI is not known

Performance Measurements for TransportCounter


7/93

ISHO vs FailuresBeberapa penampakan Failure yang ada di KPI ISHO :

1. UTRAN_NOT_ABLE_EXEC_ISHHO_RT

2. UE_NOT_ABLE_EXEC_ISHHO_RT

3. UTRAN_NOT_ABLE_EXC_ISHHO_NRT

4. UE_NOT_ABLE_EXEC_ISHHO_NRT

5. UNSUCC_IS_HHO_UE_TRX_PWR_RT

6. UNSUCC_IS_HHO_CPICH_ECNO_RT

7. UNSUCC_IS_HHO_CPICH_RSCP_RT

8. UNSUC_IS_HHO_UE_TRX_PWR_NRT9. UNSUCC_IS_HHO_CPICH_ECNO_NRT

10. UNSUCC_IS_HHO_CPICH_RSCP_NRT

1. UTRAN_NOT_ABLE_EXEC_ISHHO_RT

Description: Number of inter-system handover failures for RT due to UTRAN. --- The failurecan occur, for example, due to the following reasons: relocation preparation procedurefailure in the CN, or relocation resource allocation procedure failure in the target BSC.

Updated: When the hard handover attempt fails before the serving RNC sends the handoverWhen the RNC receives an RANAP: RELOCATION PREPATION FAILURE message from the CN,or the RNC does not receive an RANAP: RELOCATION COMMAND message from the CN withina certain time period. This counter is updated only during inter-system handovers.

2. UE_NOT_ABLE_EXEC_ISHHO_RT

Description : The number of times when during inter-system handover for RT the source RNC

has ordered the UE to use a configuration which the UE does not support. --- If the sourceRNC instructs the UE to use a configuration that it does not support, the UE will send afailure message to the source RNC. The handover procedure ends and the UE resumes normaloperation as if no handover attempt had occurred.

Updated: When the source RNC receives an RRC: HANDOVER FROM UTRAN FAILURE messagefrom the UE, and the failure cause is "configuration unacceptable".


8/93

3. UTRAN_NOT_ABLE_EXC_ISHHO_NRT

Description: The number of inter-system handover failures for NRT due to UTRAN.

Updated: This counter is never updated.

4. UE_NOT_ABLE_EXEC_ISHHO_NRT

Description: The number of times when during inter-system handover for NRT the sourceRNC has ordered the UE to use a configuration which the UE does not support. --- If thesource RNC instructs the UE to use a configuration that it does not support, the UE will senda failure message to the source RNC. The handover procedure ends and the UE resume

normal operation as if no handover attempt had occurred.

Updated: When the source RNC receives an RRC: CELL CHANGE ORDER FROM UTRAN FAILUREmessage from the UE, and the failure cause is "configuration unacceptable".

5. UNSUCC_IS_HHO_UE_TRX_PWR_RT

Description: The number of unsuccessful inter-system handovers caused by UE transmissionpower for RT. --- If the UE fails to establish the physical channel(s) indicated in the handovercommand, the UE will revert to the configuration prior to the reception of the handovercommand (old configuration) and transmit a failure message to the source RNC. The hardhandover procedure ends and the UE resumes the normal operation as if no hard handoverattempt had occurred.

Updated: When the source RNC receives an RRC: HANDOVER FROM UTRAN FAILURE messagefrom the UE, and the failure cause is not "configuration unacceptable". This counter isupdated only when the trigger reason is UE transmission power.

6. UNSUCC_IS_HHO_CPICH_ECNO_RT

Description: The number of unsuccessful inter-system handovers caused by CPICH Ec/No forRT. --- If the UE fails to establish the physical channel(s) indicated in the handovercommand, the UE will revert to the configuration prior to the reception of the handovercommand (old configuration) and transmit a failure message to the source RNC. The hard


9/93

handover procedure ends and the UE resume the normal operation as if no hard handoverattempt had occurred.

Updated: When the source RNC receives an RRC: HANDOVER FROM UTRAN FAILURE messagefrom the UE, and the failure cause is not "configuration unacceptable". This counter isupdated only when the trigger reason is CPICH Ec/No.

7. UNSUCC_IS_HHO_CPICH_RSCP_RT

Description: The number of unsuccessful inter-system handovers caused by CPICH RSCP forRT. --- If the UE fails to establish the physical channel(s) indicated in the handovercommand, the UE will revert to the configuration prior to the reception of the handover

command (old configuration) and transmit a failure message to the source RNC. The hardhandover procedure ends and the UE resume the normal operation as if no hard handoverattempt had occurred.

Updated: When the source RNC receives an RRC: HANDOVER FROM UTRAN FAILURE messagefrom the UE, and the failure cause is not "configuration unacceptable". This counter isupdated only when the trigger reason is CPICH RSCP.

8. UNSUC_IS_HHO_UE_TRX_PWR_NRT

Description: The number of unsuccessful inter-system handovers caused by UE transmissionpower for NRT. --- If the UE fails to establish the physical channel(s) indicated in thehandover command, the UE will revert to the configuration prior to the reception of thehandover command (old configuration) and transmit a failure message to the source RNC.The hard handover procedure ends and the UE resumes the normal operation as if no hardhandover attempt had occurred.

Updated: When the source RNC receives an RRC: CELL CHANGE ORDER FROM UTRAN FAILUREmessage from the UE, and the failure cause is not "configuration unacceptable".

9. UNSUCC_IS_HHO_CPICH_ECNO_NRT

Description: The number of unsuccessful inter-system handovers caused by CPICH Ec/No forNRT. --- If the UE fails to establish the physical channel(s) indicated in the handovercommand, the UE will revert to the configuration prior to the reception of the handover


10/93

command (old configuration) and transmit a failure message to the source RNC. The hardhandover procedure ends and the UE resumes the normal operation as if no hard handoverattempt had occurred.

Updated: When the source RNC receives an RRC: CELL CHANGE ORDER FROM UTRAN FAILUREmessage from the UE, and the failure cause is not "configuration unacceptable". This counteris updated only when the trigger reason is CPICH Ec/No.

10. UNSUCC_IS_HHO_CPICH_RSCP_NRT

Description: The number of unsuccessful inter-system handovers caused by CPICH RSCP forNRT. --- If the UE fails to establish the physical channel(s) indicated in the handover

command, the UE will revert to the configuration prior to the reception of the handovercommand (old configuration) and transmit a failure message to the source RNC. The hardhandover procedure ends and the UE resumes the normal operation as if no hard handoverattempt had occurred.

Updated: When the source RNC receives an RRC: CELL CHANGE ORDER FROM UTRAN FAILUREfrom the UE, and the failure cause is not "configuration unacceptable". This counter isupdated only when the trigger reason is CPICH RSCP.


11/93

ISHO AnalysisBreakdown ISHO analysis into three phases:

Compressed mode performance (RNC_294c/RNC_295c)

Inter-system measurement success (RNC_573c/RNC_574c)

Inter-system handover success (RNC_300e / RNC_301d)

If high ISHO compressed mode start not possible

Check busy hour data of PrxTotal , PtxTotal and M1000C22 AVE_PTXTOT_CLASS_4 andM1000C20 AVE_PTXTOT_CLASS_3 for AC rejection

If Low ISHO Measurement Success Rate (RNC_573c/RNC_574c)

Check ADJG neighbour list for missing neighbours or existing neighbour performance(RNC_905a/RNC_902a)

Check parameter discrepancy (BSIC) or BSIC collision due to too tight reuse

Check Compressed mode parameter set

Check ISHO triggering Threshold too slow triggering

Check EcNo Distribution (M1007C38-M1007C47) or propagation delay counters (M1006)to indicate low coverage / interference problem

If Low ISHO Success Rate (RNC_300e


12/93


13/93

HSDPA Retainability Analysis1. Identify root cause failure distribution and main contributor of low retainability -

RSRAN079

2. If high HSDPA Radio Link Failures (NRT)

dominant cause

Compare to Cell Update ATT due to Radio link Failure (M1006C39) and Cell Update

ATT due to RLC Recoverable Error (M1006C40)

Check Serving Cell Change failure rate (KPI RNC_733a) - high SCC failures lead to radio

link failure -------> RSRAN079

Check CQI distribution (M5000C8-M5000C39) or EcNo distribution for bad coverageissue (M1007C38-M1007C47) --> RSRAN039


14/93

Check HSDPA FMCS Mobility Control Parameter (handover or SCC too late)

Check call re-establishment T315 timer due to radio link failure

3. If high HSDPA Non- Radio Link Failures (NRL)

UE responding with some failure message or not responding to some message but no

RL failure (timer expiry) --> RSRAN038

Check RB reconfiguration, physical channel reconfiguration, NBAP RL reconfiguration

failure rate

Required ICSU log for further troubleshooting


15/93

HSDPA Retainability Failure Cause Analysis Flowchart

HSDPA Accessibility Analysis1. Identify root cause of failure distribution and main failure contributor in Services

RSRAN073


16/93

2. If high HSDPA Access Failure _max user fails --> check RSRAN067

3. If high HSDPA Access Failure_UL DCH checkRejected HS-DSCH return channel due to lack of radio power resource

Check M1002C521 or M1002C522 or M1000C144 (RAS06) only when HSDPA static

allocation

Check Cell resource PrxTotal, PtxTotal

Check scrambling code congestion


17/93

4. If high HSDPA Access Failure_UE

Check RB reconfiguration failure rate ICSU log for UE types troubleshooting

5. If high HSDPA Access Failure_BTS

Lack of UL channel resources (check CE resource utilisation using M5001 counters at

BH)

Too high SHO overhead all branches must have enough CE capacity if UE is in SHO

when HS-DSCH allocation is started

6. HS-DSCH return channel setup fail due to Iub transport

Breakdown the failure distribution (64,128,384,MAC-d)

Evaluate number of reconfiguration failure due the transmission

Check M1005C128 CANC_ADD_SRNC_TRAN_STP_FAIL

Check RAB_STP_FAIL_XXX_IUB_AAL2, M1001C531-C533

Check Iub Utilisation / max CID / avg CID


18/93

Optimising Iub considering CID congestionFollowing performance indicators are proposed:

M550: Average utilization of AAL2 connections - includes R99, SRB, HSDPA and returnchannels

SUM_AAL2_CONNECTIONS / NBR_SAMPLES/ CID MAX = C4/C7/248

M550: Max utilization of AAL2 connections during measurement period

MAX_AAL2_CONNECTIONS/CID MAX = C6/248

CID Utilization Monitoring Process

The maximum CID utilisation is followed and forecasted to future so that there isenough time to introduce the new configuration before CID congestion occurs.

Average CID utilisation helps in interpreting if a peak in the maximum value is normalgrowth or just load variation.

CID congestion is usually a problem of special events when there are a lot of voicecalls and SMS

CID congestion is probable in DCH&HSDPA, DCH and RT_DCH VCCs

Unlikely in others

CID Optimisation Actions and RU10 Features

The CID congestion needs to be solved by adding a VCC DCH&HSDPA (former shared) UP VCC

Likely to cause performance degradation to HSDPA if transmission capacity is not increase- HSDPA rates are limited to VCC PCR- UBR+ is not recommended with DCH&HSDPA VCC

Path Selection CID congestion in RT VCC

- Introduce a 2nd RT VCC- If additional capacity is not available then each VCC will get PCR_RT_NEW =PCR_RT_OLD/2- Capacity fragmentation may cause increased probability for AAL2 CAC blocking, with

AMR the impact should not be big


19/93

Check Iub Performance

# counter yg diambil m550 (reservasi- atm), 530 (utilisasi-atm), m800(aal2 resservasi)

# data2 tsb yg aslinya per 15 minit diubah jadi perjam, ditampilin jd grafik (utilisasi, CACreservasi, CID utilisasi)

# nah kasus yg biasa terjadi, kalo di rf ada masalah accesibility terus due to nya iub,biasanya kalo kita lihat cid utilisasi dah full (max 248) -- MAX_AAL2_CONNECTIONS (M550C6)--> M550

# kasus yg lain biasanya seputar descrapensy N2N xconnectnya (no vc, no vp) dari setting di

node-b kemudian tellabs dan coco/rnc, utk yg satu ini biasanya ceknya masih manual ketikaada laporan node b misal hsdpa gk ada trafik kita cek di node b, lalu dari coco dump cek,kemudian cek di tellabs, biasanya kita minta berupa showrunning config, bentuknyaberupa txt

Nah itu tadi di atas utk iub yg masih atm & hybrid, kalo yg sudah nativeIP,monitorutilisasinya ngandelin reporting suite RSRAN98 & 99 utk cek reservasi, utilisasi, truoghput,dan utk yg native ini masigh rada ngambang, paling masalahnya ada laporan perfomace nodeb jatuh kita liaht utilisasi & reservasi dah mentok kita propose upgrade ajeh


20/93

High in call drop rate - WCDMA (Nokia)

1. Check high call drop cells and its neighbouring cells of any faulty alarms

2. Identify call drop root cause failure distribution and main failure contributor (radio, Iu,

BTS, Iur, MS, RNC) Services -> RSRAN079

3. Check SHO KPI if performance < 90% ( leads to radio failure)

Check if cells are at RNC border (check Iur capacity and SRNC relocation problem)

Detect badly performing neighbours using HO success rate per adjacency counters

(M1013)

High incoming HO failure rate in all adjs check sync alarms

Assessing neighbor list plan and visualization check with map

Evaluate HO control parameters and trigger threshold

4. Check ISHO KPI if RT ISHO < 90% or NRT < 80% (leads to radio failure)


21/93

Check missing neighbour (M1015), GSM frequency plan neighbour RNC and MSC

database consistency audit, check alarm of reference clock in 3G or in 2G, check 2G

TCH congestion Check RRC Drop ISHO RT / NRT

5. Detecting DL or UL path loss problem if RAB drop due to radio (dominant call

drop cause > 50%)

Check UL Lost Active KPI from Iub counters (active L1 synchronization failure) to

check UL/DL path loss problem

Check ASU failure rate (UNSUC_ASU) which link to NO RESPONSE FROM RLC

Mapping radio failures with Tx power and CPICH related parameters ->CPICHToRefRABOffset, PTXDPCH MAX

Check Call reestablishment timer -> T315

EcNo distribution for bad coverage issue (M1007C38-M1007C47)

6. Check core network parameter setting if RAB_ACT_FAIL_XXX_IU

Check SCCP SGSN/RNC IuPS Tias/Tiar if RAB_ACT_FAIL_BACKG_IU

7. If high RAB_ACT_FAIL_XXX_BTS

Check if any BTS faulty alarm (7653 cell faulty alarm)

If no alarms, COCO detach/attach

8. If high RAB_ACT_FAIL_XXX_MS

Check physical channel reconfiguration failure rate (IFHO, ISHO, code optimisation)


22/93

Identify CSSR

CSSR affected if any of the followings take place :

RRC Conn. Setup Fail

RRC Conn. Access Fail

RAB Setup Fail

RAB Setup Access FailRRC/RAB Setup & Access Analysis Process Flow Chart

1. Check the problem cells and its neighbouring cells of any faulty alarms

2. Identify root cause failure distribution using Service Report -> RSRAN073

3. RRC_CONN_STP_FAIL_AC

Check UL Interference, DL Power & Code occupancy if there is need to upgrade radio

capacity


23/93

UL Power Spikes -> Disable UL Admission Control to if the number of failures is critical

M1002C1 CH_REQ_LINK_REJ_UL_SRNC ----> Evaluate Prx Resource ProblemM1002C2 CH_REQ_LINK_REJ_DL_SRNC ----->Evaluate Ptx Resource Problem

4. RRC_CONN_STP_FAIL_BTS

Evaluate NBAP counters (radio link reconf. Failures) and KPIs for troubleshooting BTS

resources

Check BTS configuration in terms of WAM and CE allocation Use Channel Element

(5001) Counters in order to

evaluate lack of Channel Elements Expand the Capacity or decrease the traffic offered to the site

In case BTS is not responding delete and re-create COCO

5. RRC_CONN_STP_FAIL_TRANS

Evaluate Number of reconfiguration failure due the transmission

Check COCO Configuration

Use AAL2 Mux in case of two WAM

Expand the capacity or decrease the traffic offered to the site

6. RRC_CONN_STP_FAIL_RNC

Typically RNC fault or Incoming SRNC Relocation Failure (inter-RNC border)

Required ICSU log tracing if no RNC fault or SRNC relocation problem

7. RRC_CONN_STP_FAIL_RNTI ALLO FAIL

RNC decides to reject RRC connection request due to RNTI allocation failure caused by RRMU

overload

8. RRC_CONN_STP_FAIL_IUB_AAL2_TRANS

Updated when there is shortage or blocking of AAL2 resourceA subset of RRC_CONN_FAIL_TRANS which include ERQ/ECF fail due to some reason such asDMPGproblem in RNC + ERQ/ECF fail due to transport resource needed in RNC between RNC/MGW


24/93

9. RRC_CONN_ACC_FAIL_RADIO

Dominant failure causes

Perform drive test to detect if UL or DL coverageUL Coverage -> Tune Cell Dominance if the cause is UL interference

DL Coverage -> Tune SCCPCH Power if UE does not receive the RRC Setup Message

-> If UE does not synchronize, reduce N312 from 2 to 1 (depends on UE model) or tune

CPICHToRefRABOffset vs Qqualmin (or Qrxlevmin)

10. RRC_CONN_ACC_FAIL_MS

UL Coverage -> Tune Cell Dominance (or CPICH) in order to balance UL and DL (if UL

interference if not the cause)

11. If RRC setup/access failure due to Radio/MS, it is also possible to check whether UEs

are located at distance area or close to cell edge area

Propagate delay counters from RRC measurement M1006C128-C148 reports call setup

distance during RRC connection request or cell update

This give hints that either cells has large coverage area (tall sites with over-shooting) or non-

optimum cell coverage from neighbouring cells

RAB setup & Access Fail - Root CauseAnalysis

1. Check the problem cells and its neighbouring cells of any faulty alarms

2. Identify root cause failure distribution and main failure contributor using

Services ->RSRAN073

3. RAB_STP_FAIL_XXX_AC

Check UL Interference, DL Power & Code occupancy if there is need to upgrade radio

capacity

REQ_CS_VOICE_REJ_UL_SRNC -> Evaluate Prx cell resource

REQ_CS_VOICE_REJ_DL_SRNC -> Evaluate Ptx cell resource

NO_CODES_AVAILABLE_SF128/SF32 -> Evaluate AMR voice / PS64 code

congestion


25/93

4. RAB_STP_FAIL_XXX_BTS

Evaluate NBAP counters (radio link reconf. Add failures) and KPIs for troubleshootingBTS resources

Check BTS configuration in terms of WAM and CE allocation Use Channel Element

(5001) Counters in order to evaluate lack of Channel Elements

Expand the Capacity or decrease the traffic offered to the site

In case BTS is not responding delete and re-create COCO

5. RAB_STP_FAIL_XXX_TRANS

Evaluate Number of reconfiguration failure due the transmission

Check M1005C128 CANC_ADD_SRNC_TRAN_STP_FAIL

Check RAB_STP_FAIL_XXX_IUB_AAL2, M1001C531-C533

Check COCO Configuration

6. RAB_ACC_FAIL_XXX_UE

Evaluate Cell resource Prx and Ptx (for example high uplink interference)

Check RB reconfiguration failure ration ( If ATO setting is insufficient recommmended is

500ms )

7. RAB_ACC_FAIL_XXX_RNC

Typically RNC fault or Incoming SRNC Relocation Failure (inter-RNC border)

Required ICSU log tracing if no RNC fault or SRNC relocation problem

Application throughput downlink1. Open logfile STATIONERY, biasanya menggunakan MS 3 (.3)2. Join ke folder PS3. di window folder contents -- klik kanan folder PS -- Statistics -- Packet data statistics

4. dari hasil dilihat sheet "Application throughput downlink" dan bisa dilihat data average PS


26/93

Identify CSSR 2ndBerikut beberapa measurement yang diperlukan untuk analisis CSSR


27/93


28/93


29/93

FMCG ParameterGSMcauseCPICHEcNo : This parameter indicates whether a handover to GSM caused by low

measured absolute CPICH Ec/No of the serving cell is enabled.

When the handover to GSM is enabled, the RNC shall set up an intra-frequency CPICH Ec/Nomeasurement in order to monitor the absolute CPICH Ec/No of the serving cell.

The measurement reporting criteria of the intra-frequency CPICH Ec/No measurement aredefined by the Intra-frequency Measurement Control parameters (FMCS object).Rec: Enabled (1)

GSMcauseCPICHrscp : This parameter indicates whether a handover to GSM caused by lowmeasured absolute CPICH RSCP of the serving cell is enabled.

When the handover to GSM is enabled, the RNC shall set up an intra-frequency CPICH RSCPmeasurement in order to monitor the absolute CPICH RSCP of the serving cell.

The measurement reporting criteria of the intra-frequency CPICH RSCP measurement aredefined by the Intra-frequency Measurement Control parameters (FMCS object).Rec: Enabled (1)

GSMcauseTxPwrDL : This parameter indicates whether a handover to GSM caused by highdownlink DPCH TX power is enabled.

Downlink DPCH TX power threshold for the handover to GSM is determined on service-by-service basis.Rec: Disabled (0)

GSMcauseTxPwrUL : This parameter indicates whether a handover to GSM caused by high UETX power level is enabled.

UE TX power threshold for the handover to GSM is determined on service-by-service basis.Rec: Disabled (0)

GSMcauseUplinkQuality : This parameter indicates whether a handover to GSM caused bybad uplink DCH quality is enabled.Rec: Disabled (0)

GsmDLTxPwrThrAMR : This parameter determines the downlink DPCH TX power thresholdfor a CS voice connection.

When the handover to GSM caused by high DL DPCH TX power is enabled, the RNC starts


30/93

inter-RAT (GSM) measurements in compressed mode if the DPCH TX power of a single radiolink reaches the threshold. The DL DPCH TX power threshold is relative to the allocatedmaximum transmission power of the DPCH.

Rec : '-3 dB, internal_value = gui_value * 2

GsmDLTxPwrThrCS : This parameter determines the downlink DPCH TX power threshold fora CS data connection.

When the handover to GSM caused by high DL DPCH TX power is enabled, the RNC startsinter-RAT (GSM) measurements in compressed mode if the DPCH TX power of a single radiolink reaches the threshold. The DL DPCH TX power threshold is relative to the allocatedmaximum transmission power of the DPCH.Rec : '-3 dB, internal_value = gui_value * 2

GsmDLTxPwrThrNrtPS : This parameter determines the downlink DPCH TX power thresholdfor a non-real time PS data connection.


GsmDLTxPwrThrRtPS : This parameter determines the downlink DPCH TX power thresholdfor a real time PS data connection.


GsmMaxMeasPeriod : The maximum number of periodical inter-RAT (GSM) measurementreports determines the maximum allowed duration of the GSM measurement. If the RNC isnot able to execute the handover to GSM, it stops the GSM measurement after the UE hassent the predefined number of measurement reports to the RNC.Rec : 20, internal_value = gui_value

GsmMeasAveWindow : This parameter determines the maximum number of periodical inter-RAT (GSM) measurement reports (maximum size of the sliding averaging window) from whichthe RNC calculates the averaged GSM RSSI values for the handover decision algorithm.Rec : 6, internal_value = gui_value


31/93

GsmMeasRepInterval : This parameter determines the measurement reporting interval forperiodical inter-RAT (GSM) measurements.Rec : 0.5 s, range 0.5 s (2) | 1 s (3) | 2 s (4) | 3 s (5) | 4 s (6)

GsmMinHoInterval : This parameter determines the minimum interval between a successfulinter-RAT handover from GSM to UTRAN and the following inter-RAT handover attempt backto GSM related to the same RRC connection.Rec : 10 s, internal_value = gui_value

GsmMinMeasInterval : This parameter determines the minimum interval between anunsuccessful inter-RAT (GSM) measurement or handover procedure, and the following GSMmeasurement procedure related to the same RRC connection.Rec : 2 s, internal_value = gui_value

GsmNcellSearchPeriod : This parameter determines the number of periodical inter-RAT(GSM) measurement reports, starting from the first report after the measurement setup,during which a handover to GSM is not possible. This period allows the UE to find and reportall potential GSM neighbour cells before the handover decision.Rec : 0, internal_value = gui_value

GsmUETxPwrFilterCoeff : In the CELL_DCH state the UE physical layer measurement periodfor UE TX power measurements is 1 slot. The Filter Coefficient parameter controls thehigher layer filtering of physical layer UE TX power measurements before the eventevaluation and measurement reporting is performed by the UE.Rec : 10 ms (8), range : Filtering period approximates 10 ms (8) | Filtering periodapproximates 15 ms (9) | Filtering period approximates 30 ms (10) | Filtering periodapproximates 60 ms (11) | Filtering period approximates 120 ms (12) | Filtering periodapproximates 240 ms (13) | Filtering period approximates 480 ms (14)

GsmUETxPwrThrAMR : This parameter determines the UE TX power threshold for a CS voiceconnection. If the handover to GSM caused by high UE TX power level is enabled, the RNCstarts inter-RAT (GSM) measurements in compressed mode when the UE TX power reachesthis threshold. The UE TX power threshold is relative to the maximum TX power level an UEcan use on the DPCH in the cell (or the maximum RF output power capability of the UE,whichever is lower).Rec : '-3dB as default , -60dB only on 3G congested site defined by TSEL to force AMR to 2G,internal_value = gui_value

GsmUETxPwrThrCS : This parameter determines the UE TX power threshold for a CS dataconnection. If the handover to GSM caused by high UE TX power level is enabled, the RNCstarts inter-RAT (GSM) measurements in compressed mode when the UE TX power reachesthis threshold. The UE TX power threshold is relative to the maximum TX power level an UEcan use on the DPCH in the cell (or the maximum RF output power capability of the UE,


32/93

whichever is lower).Rec : '-3 dB, internal_value = gui_value

GsmUETxPwrThrNrtPS : This parameter determines the UE TX power threshold for a non-real time PS data connection. If the handover to GSM caused by high UE TX power level isenabled, the RNC starts inter-RAT (GSM) measurements in compressed mode when the UE TXpower reaches this threshold. The UE TX power threshold is relative to the maximum TXpower level an UE can use on the DPCH in the cell (or the maximum RF output powercapability of the UE, whichever is lower).Rec : '-1 dB, internal_value = gui_value

GsmUETxPwrThrRtPS : This parameter determines the UE TX power threshold for a realtime PS data connection. If the handover to GSM caused by high UE TX power level isenabled, the RNC starts inter-RAT (GSM) measurements in compressed mode when the UE TX

power reaches this threshold. The UE TX power threshold is relative to the maximum TXpower level an UE can use on the DPCH in the cell (or the maximum RF output powercapability of the UE, whichever is lower).Rec : '-3 dB, internal_value = gui_value

GsmUETxPwrTimeHyst : If the handover to GSM caused by high UE TX power is enabled, theRNC starts inter-RAT (GSM) measurements in compressed mode when the UE TX powerreaches a predefined threshold. If the UE TX power goes down again (after the UE TX powerthreshold has once triggered), the UE TX Power Time Hysteresis determines the time periodduring which the UE TX power must stay below the UE TX power threshold before the RNCcalls off the GSM measurements caused by the high UE TX power.Rec : 320 ms (11)

GsmMinSLHOInterval : This parameter defines the minimum interval between a successfulservice- or load-based inter-RAT handover from GSM to UTRAN and the next service- or load-based inter-RAT handover attempt back to GSM, related to the same RRC connection.

This parameter is effective if the original handover reason is known to be a service- or load-based one.Rec : 30, internal_value = gui_value, unit s, Recommeded value is only applicable if GSM ==>UTRAN IRAT HO is available

AMRDirReCell : This parameter enables and disables the use of Directed Retry of AMR callInter-system Handover. If the value is 'Enabled', then AMR calls are directed to the GSMnetwork in case of UTRAN congestion, in order to improve the setup of AMR calls. If thevalue is 'Disabled', then AMR calls are rejected in case of UTRAN congestion.Range : Disabled (0), Enabled (1)


33/93

DLDPCHTxPwrClOffset : This parameter defines the cancellation threshold(DL_DPCH_TXPWR_THRESHOLD+DLDPCHTxPwrClOffset) for the DL DPCH TX Pwr.

Def : -3 dB

ISHOClcauseCPICHEcNo : This parameter indicates whether an inter-system handovercancellation caused by a CPICH Ec/No exceeding the cancellation threshold is enabled ornot. If the value is '0', the ISHO cancellation due to CPICH Ec/No is disabled. If the value is'1', the ISHO cancellation due to CPICH Ec/No is enabled.

ISHOClcauseCPICHrscp : This parameter indicates whether an inter-system handovercancellation caused by a CPICH RSCP exceeding the cancellation threshold is enabled or not.If the value is '0', the ISHO cancellation due to CPICH RSCP exceeding the cancellationthreshold is disabled. If the value is '1', the ISHO cancellation due to CPICH RSCP exceeding

the cancellation threshold is enabled.

ISHOClcauseTxPwrDL : This parameter indicates whether an inter-system handovercancellation caused by a low measured Downlink DPCH Transmission power level is enabledor not. If the value is '0', the ISHO cancellation due to low measured Downlink DPCHTransmission power level is disabled. If the value is '1', the ISHO cancellation due to lowmeasured Downlink DPCH Transmission power level is enabled.

ISHOClcauseTxPwrUL : This parameter indicates whether an inter-system handovercancellation caused by UE Transmission power decreasing below the reporting threshold isenabled or not. If the value is '0', the ISHO cancellation due to UE Transmission power isdisabled. If the value is '1', the ISHO cancellation due to UE Transmission power is enabled.

Export data Nemo to MapinfoCara export data Nemo ke Mapinfo adalah sebagai berikut :

Setelah kumpulan logfile (idle atau dedicated) di UMTS --> UMTS Map Sumary, alangkahenaknya kalau kita bekerjanya di Mapinfo, krn lbh mudah untuk proses plot.

di sheet Ec/No atau RSCP atau SC, klik kanan di window layers pilih export to MapInfo.


34/93

FMCS ParameterActiveSetWeightingCoefficient : Active Set Weighting Coefficient (W) is used to weighteither the measurement result of the best active set cell (M_best) or the sum ofmeasurement results of all active set cells (M_sum) when the UE calculates the reportingrange for the events 1A (cell addition) and 1B (dropping of cell).The formula is: W * M_sum + ( 1 - W )* M_best.Def : 0

AdditionReportingInterval :When a monitored cell enters the reporting range and triggersevent 1A (cell addition), the UE transmits a Measurement Report to the RNC. If the RNC is

not able to add the monitored cell to the active set, the UE continues reporting after theinitial report by reverting to periodical measurement reporting.

The parameter Addition Reporting Interval determines the interval between periodicalmeasurement reports when such reporting is triggered by the event 1A.Def : 2 --> 0.5 s

AdditionTime : When a monitored cell enters the reporting range (addition window), thecell must continuously stay within the reporting range for a given period of time before theUE can send a Measurement Report to the RNC in order to add the cell into the active set(event 1A).

The length of this period is controlled by the parameter Addition Time.Rec : (11) 320 ms ==>RT, (11) 320 ms ==> NRT, (13) 1280 ms ==>HSDPA

AdditionWindow : Addition Window determines the relative threshold (A_Win) used by theUE to calculate the reporting range of event 1A. The threshold is either relative to the CPICHEc/No measurement result of the best active set cell (M_best), or to the sum of active setmeasurement results (M_sum), depending on the value of the parameter Active Set


35/93

Weighting Coefficient (W).

When the CPICH Ec/No measurement result of a monitored cell (M_new) enters the reporting

range, the UE transmits a Measurement Report to the RNC in order to add the monitored cellinto the active set:M_new >= W * M_sum + ( 1 - W )* M_best - A_WinRec : (8) 4dB ==> RT, (5) 2.5dB ==> NRT, (0) 0dB ==> HSDPA

DropTime : When an active set cell leaves the reporting range (drop window), the cell mustcontinuously stay outside the reporting range for a given period of time before the UE cansend a Measurement Report to the RNC in order to remove the cell from the active set(event 1B).

The length of this period is controlled by the parameter Drop Time.

Def : 640 ms (12)

DropWindow : Drop Window determines the relative threshold (D_Win) which is used by theUE to calculate the reporting range of event 1B. The threshold is either relative to the CPICHEc/No measurement result of the best active set cell (M_best) or to the sum of active setmeasurement results (M_sum), depending on the value of the parameter Active SetWeighting Coefficient (W).

When the CPICH Ec/No measurement result of an active set cell (M_old) leaves the reportingrange, the UE transmits a Measurement Report to the RNC in order to remove the cell fromthe active set:

M_old RT, (8) 4dB ==> NRT, (8) 4dB ==> HSDPA

EcNoFilterCoefficient : In the CELL_DCH state the UE physical layer measurement period forintra-frequency CPICH Ec/No measurements is 200 ms. The Filter Coefficient parametercontrols the higher layer filtering of physical layer CPICH Ec/No measurements before theevent evaluation and measurement reporting is performed by the UE.Def : 3 (600 ms)

HHoEcNoCancel : If the inter-frequency or inter-RAT (GSM) handover caused by lowmeasured absolute CPICH Ec/No is enabled, the RNC starts the inter-frequency or GSMmeasurement in compressed mode when all active set cells have triggered the reportingevent 1F for CPICH Ec/No.

The RNC cancels the event 1F of an active set cell if the CPICH Ec/No measurement result ofthe active set cell becomes better than or equal to the threshold HHoEcNoCancel and the UEtransmits the corresponding event 1E triggered Measurement Report to the RNC.


36/93

Note that once the RNC has started the inter-frequency or inter-RAT (GSM) measurement forthe purpose of hard handover due to low measured absolute CPICH Ec/No, the RNC does not

break off the ongoing measurement, even if one or more active set cells trigger thereporting event 1E for CPICH Ec/No.Rec : -11dB ==> RT, -12dB ==> NRT, -15dB ==> HSDPA

MaxActiveSetSize : This parameter determines the maximum number of cells which canparticipate in a soft/softer handover.

Reporting deactivation threshold indicates the maximum number of cells allowed in theactive set in order for the event 1A to trigger. The RNC calculates the deactivation thresholdfrom the parameter MaxActiveSetSize: Reporting Deactivation Threshold = MaxActiveSetSize- 1

Reporting Deactivation Threshold parameter is part of System Information Block 11/12.

Replacement activation threshold information element indicates the minimum number ofcells allowed in the active set in order for the event 1C to trigger. The threshold equals tothe maximum size of the active set which is controlled with the parameterMaxActiveSetSize.Replacement Activation Threshold parameter is part of System Information Block 11/12.Def : 3

HHoEcNoCancelTime : If the inter-frequency or inter-RAT (GSM) handover caused by lowmeasured absolute CPICH Ec/No is enabled, the RNC starts the inter-frequency or GSMmeasurement in compressed mode when all active set cells have triggered the reportingevent 1F for CPICH Ec/No.

The RNC cancels the event 1F of an active set cell if the CPICH Ec/No measurement result ofthe active set cell becomes better than or equal to the threshold HHoEcNoCancel and the UEtransmits the corresponding event 1E triggered Measurement Report to the RNC.

The parameter HHoEcNoCancelTime determines the time period during which the CPICHEc/No of the active set cell must stay better than the threshold HHoEcNoCancel before theUE can trigger the reporting event 1E.

Note that once the RNC has started the inter-frequency or inter-RAT (GSM) measurement forthe purpose of hard handover due to low measured absolute CPICH Ec/No, the RNC does notbreak off the ongoing measurement, even if one or more active set cells trigger thereporting event 1E for CPICH Ec/No.Rec : (6) 100 ms ==> RT, (6) 100 ms ==> NRT, (6) 100 ms ==> HSDPA


37/93

ReplacementReportingInterval: When the number of cells in the active set has reached themaximum, and a monitored cell becomes better than an active set cell, the UE transmits aMeasurement Report to the RNC in order to replace the active cell with the monitored cell

(event 1C).

If the RNC is not able to replace the active cell with the monitored cell, the UE continuesreporting after the initial report by reverting to periodical measurement reporting. Theparameter Replacement Reporting Interval determines the interval of periodicalmeasurement reports when such reporting is triggered by the event 1C.Def : 2 (0.5s)

HHoEcNoThreshold : If the inter-frequency or inter-RAT (GSM) handover caused by lowmeasured absolute CPICH Ec/No is enabled, the UE transmits an event 1F triggeredmeasurement report to the RNC when the CPICH Ec/No measurement result of an active set

cell becomes worse than or equal to an absolute CPICH Ec/No threshold.

The parameter HHoEcNoThreshold determines the absolute CPICH Ec/No threshold which isused by the UE to trigger the reporting event 1F. When the measured CPICH Ec/No of allactive set cells has become worse than or equal to the threshold in question, the RNC startsinter-frequency or inter-RAT (GSM) measurements in compressed mode for the purpose ofhard handover.Rec : -14dB ==> RT, -15dB ==> NRT, -18dB ==> HSDPA

ReplacementTime : When the number of cells in the active set has reached the maximum,and a monitored cell enters the reporting range (replacement window), the monitored cellmust continuously stay within the reporting range for a given period of time before the UEcan send a Measurement Report to the RNC in order to replace an active set cell with themonitored cell (event 1C). The length of this period is controlled by the parameterReplacement Time.Def : 320 ms (11)

HHoEcNoTimeHysteresis : If the inter-frequency or inter-RAT (GSM) handover caused by lowmeasured absolute CPICH Ec/No is enabled, the UE transmits an event 1F triggeredmeasurement report to the RNC when the CPICH Ec/No measurement result of an active setcell becomes worse than the threshold HHoEcNoThreshold.

The parameter HHoEcNoTimeHysteresis determines the time period during which the CPICHEc/No of the active set cell must stay worse than the threshold HHoEcNoThreshold beforethe UE can trigger the reporting event 1F. When the measured CPICH Ec/No of all active setcells has become worse than the threshold in question, the RNC starts inter-frequency orinter-RAT (GSM) measurements in compressed mode for the purpose of hard handover.Rec : (6) 100 ms ==> RT, (6) 100 ms ==> NRT, (6) 100 ms ==> HSDPA


38/93

ReplacementWindow : When the number of cells in the active set has reached themaximum specified by the parameter MaxActiveSetSize and a monitored cell becomes betterthan an active set cell, the UE transmits a Measurement Report to the RNC in order to

replace the active cell with the monitored cell (event 1C). The parameter ReplacementWindow determines the margin by which the CPICH Ec/No measurement result of themonitored cell (MNew) must exceed the CPICH Ec/No measurement result of the an activeset cell (MInAS) before the UE can send the event 1C triggered Measurement Report to theRNC:

MNew >= MInAs + ReplacementWindow / 2Def : 4 (2dB)

HHoRscpCancel : If the inter-frequency or inter-RAT (GSM) handover caused by lowmeasured absolute CPICH RSCP is enabled, the RNC starts the inter-frequency or GSM

measurement in compressed mode when all active set cells have triggered the reportingevent 1F for CPICH RSCP. The RNC cancels the event 1F of an active set cell, if the CPICHRSCP measurement result of the active set cell becomes better than or equal to thethreshold HHoRscpCancel and the UE transmits the corresponding event 1E triggeredmeasurement report to the RNC.

Note, that once the RNC has started the inter-frequency or inter-RAT (GSM) measurementfor the purpose of hard handover due to low measured absolute CPICH RSCP, the RNC doesnot break off the ongoing measurement, even if one or more active set cells trigger thereporting event 1E for CPICH RSCP.Rec : -102dBm ==> RT, -105dBm ==> NRT, -105dBm ==> HSDPA

HHoRscpCancelTime : If the inter-frequency or inter-RAT (GSM) handover caused by lowmeasured absolute CPICH RSCP is enabled, the RNC starts the inter-frequency or GSMmeasurement in compressed mode when all active set cells have triggered the reportingevent 1F for CPICH RSCP. The RNC cancels the event 1F of an active set cell, if the CPICHRSCP measurement result of the active set cell becomes better than or equal to thethreshold HHoRscpCancel and the UE transmits the corresponding event 1E triggeredmeasurement report to the RNC.

The parameter HHoRscpCancelTime determines the time period during which the CPICHRSCP of the active set cell must stay better than the threshold HHoRscpCancel before the UEcan trigger the reporting event 1E.

Note, that once the RNC has started the inter-frequency or inter-RAT (GSM) measurementfor the purpose of hard handover due to low measured absolute CPICH RSCP, the RNC doesnot break off the ongoing measurement, even if one or more active set cells trigger thereporting event 1E for CPICH RSCP.Rec : (6) 100 ms ==> RT, (6) 100 ms ==> NRT, (6) 100 ms ==> HSDPA


39/93

HHoRscpFilterCoefficient : In the CELL_DCH state the UE physical layer measurementperiod for intra-frequency CPICH RSCP measurements is 200 ms. The Filter Coefficientparameter controls the higher layer filtering of physical layer CPICH RSCP measurements

before the event evaluation and measurement reporting is performed by the UE.

The CPICH RSCP measurement reports can be used to trigger off inter-frequency or inter-RAT(GSM) measurements for the purpose of hard handover.Def : 200 ms (0)

HHoRscpThreshold : If the inter-frequency or inter-RAT (GSM) handover caused by a lowmeasured CPICH RSCP is enabled, the UE transmits an event 1F triggered measurementreport to the RNC when the CPICH RSCP measurement result of an active set cell becomesworse than or equal to an absolute CPICH RSCP threshold.

The parameter HHoRscpThreshold determines the absolute CPICH RSCP threshold which isused by the UE to trigger the reporting event 1F. When the measured CPICH RSCP of allactive set cells has become worse than or equal to the threshold in question, the RNC startsinter-frequency or inter-RAT (GSM) measurements in compressed mode for the purpose ofhard handover.Rec : -105dBm ==> RT, -110dBm ==> NRT, -110dBm ==> HSDPA

HHoRscpTimeHysteresis : If the inter-frequency or inter-RAT (GSM) handover caused by lowmeasured CPICH RSCP is enabled, the UE transmits an event 1F triggered measurementreport to the RNC when the CPICH RSCP measurement result of an active set cell becomesworse than the threshold HHoRscpThreshold.

The parameter HHoRscpTimeHysteresis determines the time period during which the CPICHRSCP of the active set cell must stay worse than the threshold HHoRscpThreshold before theUE can trigger the reporting event 1F. When the measured CPICH RSCP of all active set cellshas become worse than the threshold in question, the RNC starts inter-frequency or inter-RAT (GSM) measurements in compressed mode for the purpose of hard handover.Rec : (6) 100 ms ==> RT, (6) 100 ms ==> NRT, (6) 100 ms ==> HSDPA

DropReportingInterval : When an active cell enters the reporting range and triggers event1B (cell deletion), the UE transmits a Measurement Report to the RNC. If the RNC is not ableto remove the active cell from the active set, the UE continues reporting after the initialreport by reverting to periodical measurement reporting.

The parameter Drop Reporting Interval determines the interval between periodicalmeasurement reports when such reporting is triggered by the event 1B. This parameter ispart of System Information Block 11/12.Def : 0.5 s (2)


40/93

HOPS ParameterEcNoAveragingWindow : This parameter determines the number of event triggered periodic

intra-frequency measurement reports from which the RNC calculates the averaged CPICHEc/No values.|Def : 8

EnableInterRNCsho : Parameter indicates whether the neighbouring cell can participate in asoft handover, if it is controlled by a RNC other than the local RNC.|Range : No (0) Yes(1).|Def:Yes (1)

EnableRRCRelease : When the intra-frequency neighbour cell in question enters thereporting range and triggers either event 1A (cell addition) or event 1C (cell replacement),the UE shall transmit a Measurement Report to the RNC in order to add the neighbouring cellto the active set. If the RNC is not able to add the neighbouring cell to the active set, the

parameter Enable RRC Connection Release indicates whether a RRC connection release(excluding emergency calls) is required in order to avoid excessive uplink interference dueto non-optimum fast closed loop power control.|Range :No (0) Yes (1). |Rec: No ==> RT, No==> NRT, Yes ==> HSDPA

HHOMarginAverageEcNo : This parameter determines the maximum allowed differencebetween the averaged CPICH Ec/No of the neighbouring cell and the averaged CPICH Ec/Noof the best active cell in situations when an inter-RNC soft handover is not possible betweenthese cells. If the difference between the averaged CPICH Ec/No values exceeds the value ofthe parameter, the RNC performs an intra-frequency hard handover in order to avoidexcessive uplink interference due to non-optimum fast closed loop power control.|Def: 10

HHOMarginPeakEcNo : This parameter determines the maximum allowed differencebetween the CPICH Ec/No of the neighbour cell and the CPICH Ec/No of the best active cellin situations when an inter-RNC soft handover is not possible between these cells. If thedifference in CPICH Ec/No values exceeds the value of the parameter, the RNC performs anintra-frequency hard handover in order to avoid excessive uplink interference due to non-optimum fast closed loop power control.|Def : 4

AdjsHCSpriority : Defines the priority level of the neighbouring cell in the hierarchical cellre-selection procedure. 0 indicates the lowest HCS priority and 7 indicates the highest HCSpriority. Lower HCS priority values are meant for larger macro cells and higher HCS priorityvalues are meant for smaller pico/micro cells.| Def : 0

AdjsHCSthreshold : Defines the threshold level which must be exceeded by the CPICH Ec/Noof the neighbouring cell before the hierarchical cell re-selection becomes possible.|Def : 0

AdjsPenaltyTime : Defines the time period during which the Temporary Offset 1/2 is appliedin the cell re-selection procedure for the neighbour cell in question.|Def : 0


41/93

AdjsQoffset1 : This parameter is used in the cell re-selection and ranking between WCDMAcells. The value of this parameter is subtracted from the measured CPICH RSCP of theneighbour cell before the UE compares the quality measure with the cell re-

selection/ranking criteria.|Def :0

AdjsQoffset2 : This parameter is used in the cell re-selection and ranking between WCDMAcells. The value of this parameter is subtracted from the measured CPICH Ec/No of theneighbour cell before the UE compares the quality measure with the cell re-selection/ranking criteria.|Def : 0

AdjsQqualMin : Determines the minimum required CPICH Ec/No level which must beexceeded by the measurement result of the neighbouring cell before the cell re-selectionbecomes possible.|Def: -20

AdjsQrxlevMin : Determines the minimum required CPICH RSCP level which must beexceeded by the measurement result of the neighbouring cell before the cell re-selectionbecomes possible.|Def : -58

AdjsTempOffset1 : This parameter is used in the cell ranking between GSM and WCDMA cellswhen the neighbour cell has the same HCS priority level as the serving cell.

If the neighbour cell has a different HCS priority level, the offset value is applied for the HCScell re-selection between GSM and WCDMA cells. The offset is subtracted (during PenaltyTime) from the measured CPICH RSCP of the neighbour cell.The alternative values are the following: 3 dB, 6 dB, 9 dB, 12 dB, 15 dB, 18 dB, 21 dB and'Infinity'.|Def : 0

AdjsTempOffset2 : This parameter is used in the cell ranking between WCDMA cells whenthe neighbour cell has the same HCS priority level as the serving cell.

If the neighbour cell has a different HCS priority level, the offset value is applied for the HCScell re-selection between WCDMA cells. The offset is subtracted (during Penalty Time) fromthe measured CPICH Ec/No of the neighbour cell.The alternative values are the following: 2 dB, 3 dB, 4 dB, 6 dB, 8 dB, 10 dB, 12 dB and'Infinity'.|Def : 0

ReleaseMarginAverageEcNo : This parameter determines the maximum allowed differencebetween the averaged CPICH Ec/No of the neighbouring cell and the averaged CPICH Ec/Noof the best active cell in situations when the RNC is not able to perform a soft handoverbetween these cells.

If the difference between the averaged CPICH Ec/No values exceeds the value of theparameter, the RNC releases the RRC connection in order to avoid excessive uplink


42/93

interference due to non-optimum fast closed loop power control.|Def : 25

ReleaseMarginPeakEcNo : This parameter determines the maximum allowed difference

between the CPICH Ec/No of the neighbour cell and the CPICH Ec/No of the best active cellin situations when the RNC is not able to perform a soft handover between these cells.

If the difference between CPICH Ec/No values exceeds the value of the parameter, the RNCreleases the RRC connection in order to avoid excessive uplink interference due to non-optimum fast closed loop power control.|Def : 7

ADJS ParameterAdjsScrCode: The downlink scrambling code of the Primary CPICH (Common Pilot Channel)

of the intra-frequency neighbour cell.

NrtHopsIdentifier : This parameter defines the parameter set (HOPS object) which controlsthe intra-frequency handover of a non-real time (NRT) radio bearer to the neighbouring cell.

RtHopsIdentifier : This parameter defines the parameter set (HOPS object) which controlsthe intra-frequency handover of a real time (RT) radio bearer to the neighbouring cell.

HSDPAHopsIdentifier : The parameter identifies the parameter set (HOPS object)controlling the intra-frequency handovers of a user having HS-DSCH allocated.

RTWithHSDPAHopsIdentifier : This parameter identifies the parameter set (HOPS object)controlling intra-frequency handovers of a user having HS-DSCH allocated simultaneouslywith AMR speech CS RAB.

AdjsDERR : This parameter indicates whether the neighbouring cell is forbidden to affectthe reporting range (addition/drop window) calculation, if it belongs to the active set. |Range and Step : No (0) Yes (1) | Def : 0

AdjsEcNoOffset : The CPICH Ec/No Offset determines an offset value, which the UE adds tothe CPICH Ec/No measurement result of the neighbouring cell before it compares the Ec/Novalue with the reporting criteria. | Default : 0 dB, -> nilai ditambah (+) berimpact attempt

ke neighbor tersebut bertambah

AdjsTxDiv : This parameter indicates whether the Primary CPICH of the intra-frequencyneighbour cell is broadcast from two antennas. If the Primary CPICH is broadcast from twoantennas, the UE measures the received code power from each antenna separately and sumsthe measurement results together in order to get the total received code power on thePrimary CPICH. | Range and Step : Tx Diversity not used (0), Tx Diversity in use (1) | Def : 0


43/93

AdjsTxPwrRACH : This parameter indicates the maximum transmission power level that a UEcan use when accessing the neighbouring cell on the RACH. The UE uses the parameter inthe cell re-selection procedure. If the maximum output power of the UE is lower than the

value of the parameter, the UE adds the power difference (dB value) to the minimumrequired CPICH Ec/No level, which the measurement result of the neighbouring cell mustexceed before the cell re-selection is possible. | Def : 21

AdjsCPICHTxPwr : This parameter indicates the transmission power level of the PrimaryCPICH (Common Pilot Channel) of the intra-frequency neighbour cell. | Def : 330

AdjsSIB : The parameter indicates whether the intra-frequency neighbour cell is included inthe System Information Block 11&12&18 for the cell selection and re-selection procedures.

The intra-frequency neighbour cell is included in the system information when the value of

the parameter is "SIB".

The intra-frequency neighbour cell is included in the extended system information when thevalue of the parameter is "SIBbis".

The total number of intra-frequency, inter-frequency and GSM neighbour cells, which can beincluded in the System Information Block type 11 (SIB11), is 47. When HCS is used, thecapacity is limited to 35 cells.

System Information Block type 11bis (SIB11bis) increases the maximum number ofadjacencies to 96. SIB11bis can only be decoded by the UEs which support 3GPP R6. If thetotal number of intra-frequency, inter-frequency and GSM neighbour cells, which areincluded in the System Information, exceeds the physical size of SIB data, the NBAPinterface is not able to pack the neighbour cell information into the SIB data and thescheduling of the system information blocks fails.

The cell is blocked by the system and an alarm 7771 WCDMA CELL OUT OF USE (BCCHscheduling error) is reported for the cell.Note: The parameter AdjsSIB does not affect intra-frequency measurements in CELL_DCHstate of connected mode. That is, all intra-frequency neighbour cells are monitored for thesoft(er) handover regardless of the value of the parameter AdjsSIB.

| No (0), SIB (1), SIBbis (2) | Def : SIB (1)


44/93

3G HO Basic reporting eventsIntra frequency events

1A: Primary CPICH enters the reporting range (Ncell addition), If active set of UE is full, UEstops reporting 1A event1B: P-CPICH leaves the reporting range (Ncell deletion)1C: Non-active P-CPICH becomes better than an active PCPICH1D: Change of current best cell with new P-CPICH

1E : The measurement value of a primary pilot channel exceeds the absolute threshold

1F : The measurement value of a primary pilot channel is lower than the absolute threshold

Inter frequency events

2A : The best frequency changes2B : The quality of the current cell frequency is lower than a certain threshold, but that ofthe non-used frequency is higher than a certain threshold2C : The estimated quality of the non-used frequency is higher than a certain threshold2D : The estimated quality of the used frequency is lower than a certain threshold2E : The estimated quality of the non-used frequency is lower than a certain threshold2F : The estimated quality of the used frequency is higher than a certain threshold

Inter system events

3A: The estimated quality value of the used UTRAN frequency is lower than a certainthreshold, and that of the other system is higher than a certain threshold3B : The estimated quality value of the other system is lower than a certain threshold3C : The estimated quality value of the other system is higher than a certain threshold3D : The best cell in the other system changes


45/93

3G Handover TypesIntra-Frequency Handovers

1. Softer Handover

Handover between sectors of the same Node B (handled by BTS)

No extra transmissions across Iub interface

Maximum Ratio Combining (MRC) is occurring in both the UL & DL

2. Soft Handover

UE simultaneously connected to multiple cells (from different Node Bs)

Extra transmission across Iub, more channel cards are needed (compared to non-SHO)

Mobile Evaluated Handover (MEHO)

DL/UE: MRC & UL/RNC: Frame selection combining

3. Hard Handover

Arises when inter-RNC SHO is not possible (Iur not supported or Iur congestion

Decision procedure is the same as SHO (MEHO and RNC controlled)

Causes temporary disconnection of the (RT) user


46/93

Inter-Frequency Handover

Can be intra-BS, intra-RNC, inter-RNC

Network Evaluated Handover (NEHO)

Decision algorithm located in RNC

Inter-RAT Handover

Handovers between WCDMA and GSM (NEHO) or GAN (WLAN)

RRC connection request

If admission control rejects the RRC connection request, the RNC sends the RRC: RRC

Connection Reject message to the UE. The message includes mandatory IE Wait time.

The user equipment waits at least the time stated in the parameter before sending a new

RRC: RRC Connection Request message. The value of the Wait time is defined with the Wait

time in RRC connection request rejection (WaitTimeRRC) management parameter


47/93

How to avoid ping pong (3G - GSM)When UE is camped on 3G -> GSM measurements start when CPICH Ec/Io of serving cell is

below Ssearch_RAT + QqualMin

When UE is camped on GSM -> cell reselection to 3G is possible if CPICH Ec/Io of thecandidate is above FDD_Qmin

FDD_Qmin >= QqualMin+Ssearch_RAT

2G -> 3G Cell Re / SelectionQsearchI (A_BTS)

With this parameter you define the threshold for dual mode mobiles in idle state to searchfor and to measure UTRAN neighbour cells introduced in 3G Cell Reselection list when arunning average of the received downlink signal level (RLA_C) of the serving cell is below (0-7) or above (8-15) the threshold. This parameter is broadcast only on BCCH.

If the parameter value is 7, dual mode mobiles in idle state measure always neighbourUTRAN cell(s). If the parameter value is 15, dual mode mobiles in idle state do not measureany of the neighbour UTRAN cells.

GPRS-capable mobiles do not use this parameter if NCCR is active in the serving cell

QsearchP (A_BTS)

With this parameter you define the threshold for GPRS capable dual mode mobiles to searchfor and to measure UTRAN neighbour cells introduced in 3G Cell Reselection list when arunning average of the received downlink signal level (RLA_C) of the serving cell is below (0-7) or above (8-15) the threshold.

This parameter is broadcast on BCCH.

In case this parameter is broadcast on BCCH it shall be used only if GPRS cell re-selectionparameters for one or more cells are sent to the MS in a Packet Cell Change Order or PacketMeasurement Order message

If the parameter value is 7, GPRS-capable multi-RAT MSs measure always neighbour UTRANcell(s). If the parameter value is 15, GPRS-capable multi-RAT MSs do not measure any ofneighbour UTRAN cells.


48/93

GPRS-capable mobiles use this parameter only if NCCR is active in the serving cell

fddQOffset (A_BTS)

With this parameter you define a UTRAN cell reselection offset for non-GPRS capable dualmode mobiles which are in the idle state.

The mobiles add the offset to the running average (RLA_C) of the received signal level of theserving GSM cell and non-serving GSM cells. After that the mobiles compare the measuredRSCP values of UTRAN cells with signal levels of the GSM cells.

-32 db = minus infinity dB

range: -28..28 dB, step 4 dB

FDD_GPRS_Offset

FDDQmin (A_BTS)

This parameter defines a minimum Ec/Io threshold which must be exceeded before a non-GPRS capable dual mode mobile is allowed to make a reselection from the serving GSM cellto an adjacent WCDMA RAN cell that is using frequency division duplex (FDD) type accesstechnology/mode

FDD_REP_QUANT

defines the reporting quantity for UTRAN cell

3G_Search_PRIO

Is used to inidicate to the MS if 3G cells can be looked for when BSIC decoding is required.(0=no, 1=yes, default: 1)


49/93

3G --> 2G Cell Re / selectionCell Re / selection Criteria S di define sbb :

Squal = Qqualmeas Qqualmin

Srxlev = Qrxlevmeas - Qrxlevmin - Pcompensation

where :

Squal : Cell Selection quality (dB)Qqualmeas : Measured cell quality valueQqualmin : Minimum required quality level in the cell (dB)

Srxlev : Cell Selection RX level value (dB)

Qrxlevmeas : Measured cell RX level valueQrxlevmin : Minimum required RX level in the cell (dBm)

Pcompensation : max(UE_TXPWR_MAX_RACH P_MAX, 0) in dB"UE_TXPWR_MAX_RACH" : Maximum TX power level an UE may use when accessing the cellon RACH (dBm)P_MAX : Maximum RF output power of the UE (dBm)

Cell Re / selection Criteria S akan terpenuhi jika :Squal > 0Srxlev > 0

Asumsi tidak menggunakan HCS maka :

If Squal > Sintrasearch, UE need not perform intra-frequency measurementsIf Squal Sintersearch, UE need not perform inter-frequency measurementIf Squal SsearchRAT m, UE need not perform measurements on cells of RAT "m"If Squal 2G adalah :HCS_PRIO : Defines the HCS priority level for a cell (def:0) (A_WCEL)


50/93

NCr : Defines the maximum number of cell reselections (def:8) (A_WCEL)

QHCS : Quality threshold level for applying prioritised hierarchical cell re-selection for a cell(def:WCDMA : -24) (A_WCEL)

Qhyst1 : Qhyst1 is used for TDD and GSM cells, and for FDD cells when cell selection and re-selection quality measure is set to CPICH RSCP (def:4) (A_WCEL)

Qhyst2 : Qhyst2 is used for FDD cells when cell selection and re-selection quality measure isset to CPICH Ec/No (def:4) (A_WCEL)

QqualMin : The minimum required quality level in the cell (Ec/No) (def:-20) (A_WCEL)

QrxlevMin : The minimum required RX level in the cell (def: WCDMA -115, GSM -105) (A_WCEL)

SHCS_RAT : The RAT specific threshold for inter-RAT measurement rules (def:1) (A_WCEL)

Sintersearch : The threshold for inter-frequency measurements, and for the HCSmeasurement rules (def:2)(A_WCEL)

Sintrasearch : The threshold for intra-frequency measurements, and for the HCSmeasurement rules (def:4)(A_WCEL)

Slimit_SearchRAT : Threshold for skipping inter-RAT measurement rules in HCS(def:2) (A_WCEL)

Ssearch_RAT : The RAT-specific threshold for inter-RAT measurement rules (def:0) (A_WCEL)

SsearchHCS : Threshold for intra- and interfrequency measurement rules in HCS(def:1) (A_WCEL)

TCrmax : The duration for evaluating the allowed amount of cell reselections(def:60sec) (A_WCEL)

TCrmaxHyst : Cell reselection hysteresis for reverting from UE high-mobility measurements(def:0sec)(A_WCEL)

Treselection : The UE triggers the reselection of a new cell if the cell reselection criteria arefulfilled during the time interval Treselection (def:0) (A_WCEL)UseOfHCS : Indicates whether the serving cell belongs to a Hierarchical Cell Structure (HCS),or not (def:0)(A_WCEL)


51/93

RAB setup failures for CS voice calls

RAB SETUP FAILURES DUE TO AC FOR CS VOICE

NetAct name: RAB_STP_FAIL_CS_VOICE_AC

Description: The number of RAB setup failures caused by admission control for CS voice.When the RNC decides to reject the CS voice RAB request because the admission control

entity reports a failure (excluding frozen BTS reason). This happens before the RRC: RADIO

BEARER SETUP message would be sent to the UE

RAB SETUP FAILURES DUE TO BTS FOR CS VOICE

NetAct name: RAB_STP_FAIL_CS_VOICE_BTS

Description: The number of RAB setup failures caused by BTS for CS voice.

When the RAB assignment fails due to radio link setup or reconfiguration failure. The failure

can happen either in the Iub or in the Iur interface.

RAB SETUP FAILURES DUE TO TRANSPORT FOR CS VOICE

NetAct name: RAB_STP_FAIL_CS_VOICE_TRANS

Description: The number of RAB setup failures caused by transport for CS voice.


52/93

When the RNC decides to reject the CS voice RAB request due to transport failure. This

happens before the RRC: RADIO BEARER SETUP message would be sent to the UE

RAB SETUP FAILURES DUE TO RNC FOR CS VOICE

NetAct name: RAB_STP_FAIL_CS_VOICE_RNC

Description: The number of RAB setup failures caused by RNC for CS voice.

When the RNC decides to reject the CS voice RAB request due to RNC internal failure. This

happens before the RRC: RADIO BEARER SETUP message would be sent to the UE

RAB SETUP FAILURES DUE TO FROZEN BTS FOR CS VOICE

NetAct name: RAB_STP_FAIL_CS_VOICE_FROZBS

Description: The number of RAB setup failures caused by frozen BTS for CS voice.

When the RNC decides to reject the CS voice RAB request because the admission control

entity blocks the radio link establishment to ensure the setup of high priority calls. This

happens before the RRC: RADIO BEARER SETUP message would be sent to the UE.

RAB SETUP FAILURES DUE TO IUB AAL2 TRANS FOR CS VOICE

NetAct name: RAB_STP_FAIL_CS_V_IUB_AAL2

Description: The number of RAB setup failures caused by Iub AAL2 transport resource

shortage for CS voice.


53/93

When the RNC decides to reject the CS voice RAB request due to Iub transport resource

shortage between RNC and WBTS. This happens before the RRC: RADIO BEARER SETUP

message is sent to the UE

RAB SETUP FAILURE CS VOICE WPS

NetAct name: RAB_STP_FAIL_CS_VOICE_WPS

Description: The number of RAB setup failures for CS voice calls using Wireless Priority

Service. Also some other RAB SETUP FAILURE counter is updated along with this counter.

When allocating resources for Wireless Priority Service CS Voice RAB fails and blind Inter-

System handover to GSM is not possible for example due to no neighbour cell available. In

this case RNC responds to CN with RANAP: RAB ASSIGNMENT RESPONSE("No Resource

Available").

RAB SETUP FAILURES DUE TO LICENCE FOR CS VOICE

NetAct name: RAB_STP_FAIL_CS_VOICE_LIC

Description: The number of RAB setup failures caused by AMR capacity license exceeded for

CS voice.

When the RNC rejects a CS Voice RAB request due to AMR capacity license exceeded.


54/93

RAB SETUP FAILURES DUE TO IUR TRANSPORT FOR CS VOICE

NetAct name: RAB_STP_FAIL_CS_VOICE_IUR_TR

Description: The number of failed CS voice RAB setups due to Iur transport resources. Also

counter M1001C82 is updated with this counter

When a CS voice traffic class RAB setup fails due to Iur transport resources.

RAB SETUP FAILURES DUE TO IU-CS TRANSPORT FOR CS VOICE

NetAct name: RAB_STP_FAIL_CS_VOICE_IU_CS

Description: The number of failed CS voice RAB setups due to Iu-CS transport resources. Also

counter M1001C82 is updated with this counter

Updated: When a CS voice traffic class RAB setup fails due to Iu-CS transport resources.


55/93

RAB setup failures for PS callsRAB SETUP FAILURES DUE TO AC FOR PS DATA CONV

NetAct name: RAB_STP_FAIL_PS_CONV_ACDescription: The number of RAB setup failures caused by admission control for PS dataconversational.

When the RNC decides to reject the PS data conversational RAB request because theadmission control entity reports a failure (excluding frozen BTS reason). This happens beforethe RRC: RADIO BEARER SETUP message would be sent to the UE

RAB SETUP FAILURES DUE TO BTS FOR PS DATA CONV

NetAct name: RAB_STP_FAIL_PS_CONV_BTSDescription: The number of RAB setup failures caused by BTS for PS data conversational.

When the RAB assignment fails due to radio link setup or reconfiguration failure. The failurecan happen either in the Iub or in the Iur interface

RAB SETUP FAILURES DUE TO TRANSPORT FOR PS DATA CONV

NetAct name: RAB_STP_FAIL_PS_CONV_TRANSDescription: The number of RAB setup failures caused by transport for PS dataconversational.

When the RNC decides to reject the PS data conversational RAB request due to transportfailure. This happens before the RRC: RADIO BEARER SETUP message would be sent to theUE.

RAB SETUP FAILURES DUE TO RNC FOR PS DATA CONV

NetAct name: RAB_STP_FAIL_PS_CONV_RNCDescription: The number of RAB setup failures caused by RNC for PS data conversational.

When the RNC decides to reject the PS data conversational RAB request due to RNC internalfailure. This happens before the RRC: RADIO BEARER SETUP message would be sent to theUE.


56/93

RAB SETUP FAILURES DUE TO FROZEN BTS FOR PS DATA CONV

NetAct name: RAB_STP_FAIL_PS_CONV_FROZBS

Description: The number of RAB setup failures caused by frozen BTS for PS dataconversational.

When the RNC decides to reject the PS data conversational RAB request because theadmission control entity blocks the radio link establishment to ensure the setup of highpriority calls. This happens before the RRC: RADIO BEARER SETUP message would be sent tothe UE

RAB SETUP FAILURES DUE TO AC FOR PS DATA STREAM

NetAct name: RAB_STP_FAIL_PS_STREA_ACDescription: The number of RAB setup failures caused by admission control for PS datastreaming.

When the RNC decides to reject the PS data streaming RAB request because the admissioncontrol entity reports a failure (excluding frozen BTS reason). This happens before the RRC:RADIO BEARER SETUP message would be sent to the UE

RAB SETUP FAILURES DUE TO BTS FOR PS DATA STREAM

NetAct name: RAB_STP_FAIL_PS_STREA_BTSDescription: The number of RAB setup failures caused by BTS for PS data streaming.

When the RAB assignment fails due to radio link setup or reconfiguration failure. The failurecan happen either in the Iub or in the Iur interface.

RAB SETUP FAILURES DUE TO TRANSPORT FOR PS DATA STREAM

NetAct name: RAB_STP_FAIL_PS_STREA_TRANSDescription: The number of RAB setup failures caused by transport for PS data streaming.

When the RNC decides to reject the PS data streaming RAB request due to transport failure.This happens before the RRC: RADIO BEARER SETUP message would be sent to the UE

RAB SETUP FAILURES DUE TO RNC FOR PS DATA STREAM


57/93

NetAct name: RAB_STP_FAIL_PS_STREA_RNCDescription: The number of RAB setup failures caused by RNC for PS data streaming.

When the RNC decides to reject the PS data streaming RAB request due to RNC internalfailure. This happens before the RRC: RADIO BEARER SETUP message would be sent to the UE

RAB SETUP FAILURES DUE TO FROZEN BTS FOR PS DATA STREAM

NetAct name: RAB_STP_FAIL_PS_STREA_FROZBSDescription: The number of RAB setup failures caused by frozen BTS for PS data streaming.

When the RNC decides to reject the PS data streaming RAB request because the admissioncontrol entity blocks the radio link establishment to ensure the setup of high priority calls.

This happens before the RRC: RADIO BEARER SETUP message would be sent to the UE

RAB SETUP FAILURES DUE TO AC FOR PS DATA INTERA

NetAct name: RAB_STP_FAIL_PS_INTER_ACDescription: The number of RAB setup failures caused by admission control for PS datainteractive.

When the RNC decides to reject the PS data interactive RAB request because the admissioncontrol entity reports a failure (excluding frozen BTS reason). This happens before the RRC:RADIO BEARER SETUP message would be sent to the UE.

RAB SETUP FAILURES DUE TO RNC FOR PS DATA INTERA

NetAct name: RAB_STP_FAIL_PS_INTER_RNCDescription: The number of RAB setup failures caused by RNC for PS data interactive.

When the RNC decides to reject the PS data interactive RAB request due to RNC internalfailure. This happens before the RRC: RADIO BEARER SETUP message would be sent to the UE

RAB SETUP FAILURES DUE TO ANCHORING FOR PS DATA INTERA

NetAct name: RAB_STP_FAIL_PS_INTER_ANCHDescription: The number of RAB setup failures caused by ongoing relocation or hardhandover for PS data interactive.When the RNC rejects the PS data interactive RAB assignment request due to ongoing


58/93

relocation or hard handover.

RAB SETUP FAILURES DUE TO FROZEN BTS FOR PS DATA INTERA

NetAct name: RAB_STP_FAIL_PS_INTER_FROZBSDescription: The number of RAB setup failures caused by frozen BTS for PS data interactive.

When the RNC decides to reject the PS data interactive RAB request because the admissioncontrol entity blocks the radio link establishment to ensure the setup of emergency calls.This happens before the RRC: RADIO BEARER SETUP message would be sent to the UE.

RAB SETUP FAILURES DUE TO AC FOR PS DATA BACKG

NetAct name: RAB_STP_FAIL_PS_BACKG_ACDescription: The number of RAB setup failures caused by admission control for PS databackground.

When the RNC decides to reject the PS data background RAB request because the admissioncontrol entity reports a failure (excluding frozen BTS reason). This happens before the RRC:RADIO BEARER SETUP message would be sent to the UE

RAB SETUP FAILURES DUE TO RNC FOR PS DATA BACKG

NetAct name: RAB_STP_FAIL_PS_BACKG_RNCDescription: The number of RAB setup failures caused by RNC for PS data background.

When the RNC decides to reject the PS data background RAB request due to RNC internalfailure. This happens before the RRC: RADIO BEARER SETUP message would be sent to theUE.

RAB SETUP FAILURES DUE TO ANCHORING FOR PS DATA BACKG

NetAct name: RAB_STP_FAIL_PS_BACKG_ANCHDescription: The number of RAB setup failures caused by ongoing relocation or hardhandover for PS data background.

When the RNC rejects the PS data background RAB assignment request due to ongoingrelocation or hard handover


59/93

RAB SETUP FAILURES DUE TO FROZEN BTS FOR PS DATA BACKG

NetAct name: RAB_STP_FAIL_PS_BACKG_FROZBS

Description: The number of RAB setup failures caused by frozen BTS for PS data background.

When the RNC decides to reject the PS data background RAB request because the admissioncontrol entity blocks the radio link establishment to ensure the setup of emergency calls.This happens before the RRC: RADIO BEARER SETUP message would be sent to the UE

RAB SETUP NOT STARTED DUE TO NOT SUPPORTED PARAMETERS FOR PS

NetAct name: RAB_STP_FAIL_PS_NOT_SUPP_PARDescript

3g optimisation cookbook_v2

Documents

fmcg parameter

fmcs parameter

hops parameter

adjs parameter

g handover types

hsdpa retainability

hsdpa accessibility

g ho basic reporting