Академический Документы
Профессиональный Документы
Культура Документы
RRC states
Iub
WBTS
- Handover Performance
- Traffic
- Cell Resources
- Iub Signalling
Monitor Cell/Neighbour cells
Indicators, counters and parameters Availability - missing cell has impact
detect faults at different layers to neighbouring cells performance also
Iub
WBTS
- Cell Availability
- Failures due to Radio, to BTS, to transport
Soc Classification level
7 © NSN Siemens Networks Presentation / Author / Date
KPI analysis - RAN parameter RU10 objectives
RAN parameter and performance strategy
RNC
WBTS
RRM optimisation
and tuning at different levels/
NW - elements
WCEL
WEEK 43
Number of Drop ratio
Site ID CI RNC Cell Name Ongoing actions WHO ? WHEN ?
drops (%)
610003 44451 21 London 26 33.77 WAM changed 26/10. MHA fault => Intervention Operations W44
611349 64743 21 Paris 25 62.50 WAM counters activated Lavoix W44
611105 64541 31 Helsinki 24 12.12 Decrease coverage (tilt 0°) Radiolainen W46
TOP 10 Number of 611150 64662 31 Berlin 22 13.84 Neighbour sites ? Analyse last field measurements Ramstein W45
370037 43109 21 Bern 20 3.33
drops RAB Voice+CS 200089 45091 11 Athens 19 10.80 Terminal testing ? Pistopoulos W46
Conv 940028 41796 31 Rome 18 22.50 Some Iur drop => Check inter-RNC neighbour definition, monitor Iur performance
610078 50686 31 Madrid 18 32.14 Updated neighbour list Sanchez W44
611346 64736 31 Brussels 17 1.27
610297 44220 31 Den Haag 17 7.46 Decrease coverage (tilt 2°) van den Hoop W46
100%
90%
Quick fault diagnostics due to worst cells causes
80%
70%
cause 14% of the drops
60%
40%
30%
20%
10%
0%
1 56 111 166 221 276 331 386 441 496 551 606 661 716 771 826 881 936 991 1046 1101
Nb of cells
… for performance
Indicator I still
improve
Thank You !
Soc Classification level
14 © NSN Siemens Networks Presentation / Author / Date
Performance monitoring
KPI analysis hierarchies
Call/Session monitoring & analysis
Release 99: call setup (RRC/RAB)
R99: Call Drop
- Radio link failure rate
- Radio link success rate
RRC states
Iub
WBTS
1h
1h
BH
1h CDR
CSSR
0 12 h 24 h
Soc Classification level
17 © NSN Siemens Networks Presentation / Author / Date
Call/Session monitoring
Daily, Weekly or Busy Hour ?
Voice, R99NRT and HSDPA peak traffic can happen at different times
Blocking is not necessarily happening during the BH
NetAct Busy Hour definition is that the RT and NRT is summed every hour and
the hour with maximum value is taken for BH
• Where xxx_DL= SUMi ( Bit_Ratei * Allocation_Durationi). In Loaded
networks the Weekly Busy Hour CSSR is relevant
• The failures originate mostly from congestions (Iub, BTS HW (CEs), radio)
• The call blocking probability is designed for the BH
In Unloaded networks the Weekly Busy Hour CSSR may not yield the hour
with highest blocking as NRT traffic is taken in the account as well as RT traffic
In cell level it is needed to compute BH statistic based on absolute time period
(e.g. 16-18h every day). Daily data may not be accurate enough due to big
variations of results (due to ongoing operatios, system failures, sleeping cells,
alarms etc.)
0
1
2
3
4
5
6
/1 07
1 0
16 /20 0
/1 07
1 0
1 71
16 /20 2
/1 07
1 1
16 /20 3
/1 07
1 1
16 /20 4
/1 0
1 71
16 /20 5
/1 07
1 1
16 /20 6
/1 07
1 1
16 /20 7
/1 0
1 71
16 /20 8
/1 07
1 1
Call/Session monitoring & analysis
16 /20 9
/1 07
1 2
16 /20 0
/1 07
1 2
16 /20 1
/1 07
1/
20 22
07
23
Voice, GB (AF50%)
GB = Giga Byte
HSDPA DL, GB (100% AF)
AF activity factor
Call/Session monitoring & analysis
Hourly traffic example, cell level
1.0
0.8
0.6
Load
Load
0.4
0.2
Cell 1 Cell 2
0
15 16 17 18 19 20 21 22 23 24
Cell 3 Cell 4
Reporting Tools
NetAct
PM DB
Soc Classification level
22 © NSN Siemens Networks Presentation / Author / Date
Call/Session monitoring & analysis with NetAct
NetAct reporting suite
Export To
excel
RRC states
Iub
WBTS
UL interference
DL transmisson power
DL Codes During call set-up [RRC, RAB] several
resource areas are checked and
physical/ logical resources allocated.
DSP processing
RLC/MAC
IuB
FSP/ WSP capacity (N*) E1 capacity / AAL2
Yes
Weekly KPI
No Mapinfo
(RNC) Matching failure
<X%? distribution into
network topology Solution Proposal
Yes
Success
Setup Access Complete dropped.
Setup Access Complete
Complete Complete RAB setup
Complete Complete Attempts to start the call
Access
Active
Active
RAB setup access
Release
Release
RAB active phase
RRC UE has RAB connection
Attempts
Active
Active Drop
Failures
Failures CSSR affected if any of the followings
take
place.
Access failures
• RRC Conn. Setup Fail
• RRC Conn. Access Fail
Setup failures • RAB Setup Fail
(blocking) • RAB Setup Access Fail
40 ms window
[DCH] RRC Setup Complete
40 ms window
RRC Connection Access phase
40 ms window
50 ms window
Node B starts transmitting 40 ms window
10 ms radio
frames
40 ms window
UE starts receiving,
mobile is listing on FACH Post verification
UE L1 collects 40 ms
check
of quality
measurements
Setup
Failure
Cause? setup Setup
Sites OK ? /Access
RNC
Cell and Neighbour Troubleshooting
Cells availability Yes BTS/TRANS/FROZBS
Alarms/Tickets AC UL/DL
setup Access
Setup Interference
/Access (DL codes)
Capacity
Optimisation
Access
Yes
3G cell at
SRNS Relocation
inter-RNC
troubleshooting
border ?
NO
Interference
Coverage/Inte
RF Optimisation
rference
Coverage
Soc Classification level
38 © NSN Siemens Networks Presentation / Author / Date
RRC Connection & Access Fail - Analysis
Admission Control and RRC Setup Failure Distribution Example - RAS51
TRANS
50%
RNC
45%
FROBTS
RNTI Allo
IUB AAL2 TRANS
Example
RAS 5.1
L1 Synchronisation
UE BTS
X RNC
UE BTS
X RNC
Example
RAS51
failures M 10 01 C62 6
M 10 01 C62 7
S erviceL evel
S erviceL evel
RA B _S TP_ FAI L_ CS_ CO NV _I U_CS
RA B _S TP_ FAI L_ CS_ S TRE _ IU_CS
• RAB setup fails for PS streaming due M 10 01 C62 4 S erviceL evel RA B _S TP_ FAI L_ PS _ STRE _IUR _TR
to Iur transport
NO New site ?
YES
3G cell covers
3G cell at inter-
over a coverage
RNC border ?
Top issues hole ?
Hu”auwei” E 870
Thank You !
CDR can have several
reasons …
but sometimes only
specific handsets gives
response at Iub
100 * ( sum((ONE _ CELL _ IN _ ACT _ SET _ FOR _ RT + ONE _ CELL _ IN _ ACT _ SET _ FOR _ NRT )
+ (TWO _ CELLS _ IN _ ACT _ SET _ FOR _ RT + TWO _ CELL _ IN _ ACT _ SET _ FOR _ NRT )
+ (THREE _ CELLS _ IN _ ACT _ SET _ FOR _ RT + THREE _ CELL _ IN _ ACT _ SET _ FOR _ NRT ))
SHO _ Overhead =
sum((ONE _ CELL _ IN _ ACT _ SET _ FOR _ RT + ONE _ CELL _ IN _ ACT _ SET _ FOR _ NRT )
+ (TWO _ CELLS _ IN _ ACT _ SET _ FOR _ RT + TWO _ CELL _ IN _ ACT _ SET _ FOR _ NRT ) / 2
+ (THREE _ CELLS _ IN _ ACT _ SET _ FOR _ RT + THREE _ CELL _ IN _ ACT _ SET _ FOR _ NRT ) / 3 − 1)
# radio links
E1A CPICH E1B CPICH
# users
Offset 4dB Offset 6dB
SHO
area
cell
cell11
Factors are
ONE _ CELL _ IN _ ACT _ SET _ FOR _ RT / NRT + RL (1, 2 ,3 ) cell
cell22
TWO _ CELL _ IN _ ACT _ SET _ RT / NRT × 2 + of users
THREE _ CELL _ IN _ ACT _ SET _ RT / NRT × 3
ONE _ CELL _ IN _ ACT _ SET _ RT / NRT + # of users
TWO _ CELL _ IN _ ACT _ SET _ RT / NRT +
Users THREE _ CELL _ IN _ ACT _ SET _ RT / NRT
who stays
within
different
AS size
53 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009
R99: Mobility - SHO Overhead on RNC level (2/4)
Reminder:
Low # of UE's
UE's within AS 1(1 cell) UE's within AS 2 (2 cells) UE's within AS 3 (3 cells) within AS 3 (5-8%)
1 link per UE 2 links per UE 3 links per UE
Total # of links
1 AS 1 + 2 AS 2 + 3 AS 3
# UE AS 1 + # UE AS 2 + # UE AS 3
# of UE linked
within AS 1+2+3
Cell 2 0 1
Soc Classification level
55 © NSN Siemens Networks Presentation / Author / Date
R99: Mobility - SHO Overhead on RNC level (4/4)
Simple example
Attempt to apply formula on cell level
1 UE within AS 1 1 UE within AS 2
cell
cell11
1 AS 1 + 2 AS 2
= 1.5 for cell 1 cell
cell22
AS 1 + AS 2
(1UE within AS1) (1UE within AS2) Average 1.75
0 UE within AS 1 1 UE within AS 2
deviates strongly from
result 1.5 on RNC level
2 AS 2
= 2.0 for cell 2
AS 2
(0UE within AS1) (1UE within AS2)
Soc Classification level
56 © NSN Siemens Networks Presentation / Author / Date
R99: Mobility - SHO Overhead on cell level (1/4)
Fair calculation of Average AS size at (RNC 192b) cell specific
cell
cell11
cell
cell22
AS 3
# UE AS 1 + # UE AS 2 + # UE
1 UE 1 UE AS 3
AS 1 + AS 2
= 1.33 for cell 1
100% of 1 UE 50% of cell 1 UE
cell area A
is related + area B is
related to
to User A 1 cell 2 cells
User B
Average 1.67
AS 1 AS 2
Agrees better with result 1.5
on RNC level
(0 UE; AS1) (1UE; AS2)
AS 2
= 2.00 for cell 2
50% of cell 1 UE
area B is
related to 2 cells
User B
AS 2
Soc Classification level
60 © NSN Siemens Networks Presentation / Author / Date
R99: Mobility - SHO Success per Adjacency
The HO success rate per adjacency can be used to detect badly performing neighbours
• can be calculated by using formulas below
SHO Success per Adjacency (M1013 AutoDef SHO)
100 * sum(SHO _ ADJ _ INTRA _ FREQ _ SHO _ COMPL)
SHO _ success _ per _ ADJS _ RNC _ 900a =
sum(SHO _ ADJ _ INTRA _ FREQ _ SHO _ ATT)
Low ISHO
CM Start Not No No
Measuremen No Low ISHO
Possible? t Success ?
success ?
Yes
Yes
Yes
Missing ADJG or Missing or wrong Half Rate in 2G
Check admission Bad Neighbour 2G parameters in Ncell ?
control rejection -> planning ? 2G MSC or SGSN
PrxTotal & PtxTotal (BCCH, LAC,
Poor GSM
CellID)
Coverage
Wrong 2G Ncell
Parameter (BSIC) Missing neighbour
Or BSIC collision 2G Ncell list after re-
Congestion selection after cell
change order
Too low ISHO occured
triggering threshold or
Non-optimum
Strict ADJG minimum
Compressed mode threshold
parameter set (ADJGRxLevMinHO)
60
50
IS_ C O M _ M O D _ S T A _ NO T _ P
40 O S_RT
samples
30 UE _ P W R _ R T
20
ISHO compressed mode not possible
10
0
20040908
20040909
20040910
20040911
20040912
20040913
20040906
20040907
Thank You !
RRC states
Iub
WBTS
No No action
RNC_605b< X %
needed
Check CE Check AAL2 Iub Check RB Check RNC Unit Check number of
resource usage UL power resource reconfiguration load (DMPG) and simultaneous
at BH congestion congestion at BH Failure rate faulty alarms HSDPA users
BH ?
No
1000 25
800 20
SETUP_FAIL_BTS_HS_DSCH_BGR (Traffic)
600 15
AVE_AVAIL_PERC_POOL_CAPA_UL (Cellres)
400 10
200 5
0 0
1 14 27 40 53 66 79 92 105 118 131 144 157 170 183 196 209 222 235 248 261 274 287 # cells
• RNC sends HSUPA Congestion Control indications to the BTS based on detected
received Iub FP frame frame loss due to Iub delay, traffic loss or RNC HW overload.
Thank You !
Please consider
Release 99 users will partly suffer
due to HSPA speed and capability
EC/I0 HSDPAServCellWindow
RNC; 0..6; 0.5; 2 dB CPICH 1 R99
Drop
CPICH 2 R5/6
window
Addition 6dB
window
4dB
periodic reports as
Addition Time long UE in SHO area
SHO for A- Periodic Serving cell change
time
DCH initiated reports initiated CPICH 2 active
No
RNC_733a < X % No action
needed
Top N cells
Yes
No No No No No
SCC Fail SCC Fail
SCC Fail Prevention
SCC Fail BTS SCC Fail AC SCC Fail UE Others
Transmission timer
No
HSPA started
• There must be at least one cell in the active set with a CPICH RSCP greater than the
threshold defined by CPICHRSCPThreSRBHSDPA
• If HSPDA is already allocated then the serving cell must have a CPICH RSCP which is
greater than the threshold defined by CPICHRSCPThreSRBHSDPA
Active set update and serving cell change with fractional DPCH
EC/I0 HSDPASRBWindow
RNC; 0..6; 0.5; 1 dB CPICH 1
CPICH 2
Addition
window
periodic reports as
Addition Time long UE in SHO area
Just periodic Serving cell change AND time
reports active set update initiated
CPICH 2 not
active yet
High Ec/No
or CQI
HSPA
Thank You !
RRC states
Iub
WBTS
• T314 parameter tells when Cell update message should be coming after RL failure, def 4s
• Re-establishment can be done to different cell also
[RACH] RRC:Cell Update (Cause: RL Failure) M1006C189RRC_RE_EST_SUCC_MR : The number of successful RRC
connection re-establishments for UEs with at least two RABs. When the
[FACH] RRC: Cell Update Confirm RNC receives RRC: RADIO BEARER RECONFIGURATION COMPLETE
[RACH] Utran Mobility Information Confirm message from the UE after an RRC connection re-establishment
procedure and the UE has got at least two RABs.
NBAP: RL Reconfiguration Prepare
Thank You !
– finally finished
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
RAB_STP_FAIL_XXX_BTS
• Evaluate NBAP counters (radio link reconf. Add 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
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
RAB_ACC_FAIL_XXX_MS
• Evaluate Cell resource Prx and Ptx (for example high uplink interference)
• Check RB reconfiguration failure ration ( If ATO setting is insufficient )
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
Separate Packet call counters could be used in UL/DL to see the accessibility/re-tainability
of DCH radio bearers (R99 NRT, HSDPA, HSUPA)
• There could be multiple packets inside single RAB
Packet calls starts with user plane capacity allocation (transfer from FACH/PCH, DCH 0/0)
and ends with dedicated resource release (transfer back to FACH/PCH, DCH 0/0, RAB
release, outgoing relocation, HHO, ISHO)
There are counters for the following channel combinations
• Rel99 DL = DCH UL = DCH
• HSDPA DL = HS-DSCH UL = DCH
• HSUPA DL = HS-DSCH UL = E-DCH
There are counters for the following events
• Attempts,Allocations,Channel switches,Setup failures,Normal and abnormal releases
[DCH] RRC: Radio Bearer Setup If the network wants to initiate any downlink activity and the UE
is in Cell_PCH state, it needs to make a paging request.
[DCH] RRC: Radio Bearer Setup Complete Counter M1022C1 PS_SESSION_REQ_DL is incremented
RANAP: RAB Assignment Response:
when RNC receives RRC: CELL UPDATE message with the
Success cause PAGING RESPONSE
[DCH] RRC: Measurement Control In case of inter RNC HHO or SRNC relocation counter
[DCH] RRC: Measurement Control M1022C2 PS_SESSION_REQ_OTHER is incremented when
RANAP: RELOCATION REQUEST message request is
Direct Transfer : Activate PDP Context Accept
received
[DCH] RRC: Measurement Report Note: PS ISHO do not use relocation signaling as it is a normal
PS call setup where the resources are reserved by UL/DL
AC to check to accept
or reject Capacity capacity request
request
AC to check to accept or
reject Capacity request
In case the starting state of the terminal is Cell_FACH (Cell_PCH) or DCH 0/0
and AC rejects the bit rate allocation and terminal stays at Cell_FACH or
DCH0/0, following counters are incremented:
M1022C9 PS_SETUP_FAIL_AC_INT
M1022C10 PS_SETUP_FAIL_AC_BGR
Note: These counters are only incremented in case of initial allocation for
terminal has been Cell_FACH (Cell_PCH) or DCH0/0.
Successful Packet Call setup allocations and allocation attempts due to
Incoming relocation or Inter-RNC HHOs are not counted separately.
Soc Classification level
111 © NSN Siemens Networks Presentation / Author / Date
Call Drop analysis
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)
0.000
08
08
08
08
08
08
08
08
08
20
20
20
20
20
20
20
20
20
3.
3.
3.
3.
4.
4.
4.
4.
5.
.0
.0
.0
.0
.0
.0
.0
.0
.0
08
15
22
29
05
12
19
26
03
0.080 PS_SETUP_FAIL_AC_p
PS_SETUP_FAIL_AC_p
PS_SETUP_FAIL_BTS_p
0.060 PS_SETUP_FAIL_BTS_p
PS_SETUP_FAIL_DMCU_p
PS_SETUP_FAIL_DMCU_p
0.040 PS_SETUP_FAIL_TRANS_p
PS_SETUP_FAIL_TRANS_p
PS_SETUP_FAIL_UE_p
PS_SETUP_FAIL_UE_p
0.020
PS_SETUP_FAIL_OTHER_p
PS_SETUP_FAIL_OTHER_p
0.000
08
08
08
08
08
08
08
08
08
20
20
20
20
20
20
20
20
20
3.
3.
3.
3.
4.
4.
4.
4.
5.
.0
.0
.0
.0
.0
.0
.0
.0
.0
08
15
22
29
05
12
19
26
03
RL_SETUP_ATT_FOR_SHO_ON_SRNC
RL_BRANCH_ADD_SUCC_SHO_SRNC
DEL_SHO_SRNC_ACT_RL_SYN_FAIL
RL_SETUP_ATT_FOR_FIRST_RL
R N C _ID
D AY
RNC-CITTA
RNC2
CELL_ID
RNC_ID
RB_RECONF_SUCCESS_RATE
RB_RECONF_SUCCESS_RAT
RB_RECONF_COMPLETE
RB_RECONF_COMPLETE
RB_RECONF
RB_RECONF
RNC-CITTA
DAY
CELL
DAY
BSIC verification phase for target cell NBAP: Compressed Mode Command • For RT: TRelocOverall (def. 8s, from Relocation
RRC: Measurement Control Command to Iu Release Command) expires.
RRC: Measurement Report
No
RNC_609a < X % No action
needed
Top N cells
Yes
No No No No
HS_DSCH_ HS_DSCH_ HS_DSCH_ RL_FAIL_ OTH_FAIL_
PRE_EMP MOB_DCH OTH_DCH HS_DSCH HS_DSCH
Normal Release
Normal Release Normal Release Check SCC
(No action Check RB
(No action (No action Failure Rate –
needed) reconfiguration failure
needed) needed) Radio, Iub, CE
resource rate – UE responsed
congestion with failure or no
response at all
No
Check CQI
distribution and Check HSDPA mobility
Ecno distribution No parameter – Add/Drop
for coverage window, SCC parameter
issue
M1001C632SUCC_RRC_SETUP_INTERA is incremented
L1 Synchronisation When the RRC connection is set up successfully, i.e. RNC receives RRC: RRC CONNECTION SETUP
COMPLETE and the establishment cause in the preceding RRC: RRC CONNECTION REQUEST has
NBAP: Synchronisation Indication been either Originating Interactive Call or Terminating Interactive Call.
M1001C634SUCC_RRC_SETUP_OTHER is incremented
When the RRC connection is set up successfully, i.e. RNC receives RRC: RRC CONNECTION SETUP
COMPLETE and the establishment cause in the preceding RRC: RRC CONNECTION REQUEST has
been some other cause.
Soc Classification level
125 © NSN Siemens Networks Presentation / Author / Date
Complementaty counters: SRB Active fail
UE Node B M1001C635SRB_ACT_FAIL_CONV is incremented When a standalone SRB is released due to some
RNC failure, i.e. when it is counted as RRC Active Failure in the old Service Level counters. The counter is
[RACH] RRC:RRC Connection updated when the establishment cause in RRC: RRC CONNECTION REQUEST is either Originating
Conversational Call or Terminating Conversational Call.
Request
AC to check to accept M1001C636SRB_ACT_FAIL_STREA is incremented When a standalone SRB is released due to
or reject RRC some failure, i.e. when it is counted as RRC Active Failure in the old Service Level counters. The
Connection Request counter is updated when the establishment cause in RRC: RRC CONNECTION REQUEST is either
Originating Streaming Call or Terminating Streaming Call.
NBAP: RL Setup Request
M1001C637SRB_ACT_FAIL_INTERA is incremented When a standalone SRB is released due to
some failure, i.e. when it is counted as RRC Active Failure in the old Service Level counters. The
Start counter is updated when the establishment cause in RRC: RRC CONNECTION REQUEST is either
TX/RX Originating Interactive Call or Terminating Interactive Call.
NBAP: RL Setup Response
ALCAP:ERQ M1001C638SRB_ACT_FAIL_BACKG is incremented When a standalone SRB is released due to
ALCAP:ECF some failure, i.e. when it is counted as RRC Active Failure in the old Service Level counters. The
counter is updated when the establishment cause in RRC: RRC CONNECTION REQUEST is either
[FACH] RRC: RRC Connection Setup Originating Background Call or Terminating Background Call
M1006C172SUM_ST_TRANS_TIME_FACH_DCH: Sum of state transition times from Cell-FACH state to Cell-DCH state, defined as
the time between: UL/DL capacity request, RAB Setup - RRC: Radio Bearer Reconfiguration Complete or RRC: Radio Bearer Setup
Complete.
This counter, divided by the denominator, provides the average state transition time.
M1006C173DENOM_ST_TRANS_TIME_FACH_DCH: Denominator for M1006C172 used for average calculation.
M1006C170SUM_ST_TRANS_TIME_PCH_FACH: Sum of state transition times from Cell-PCH or URA-PCH state to Cell-FACH state,
defined as the time between:
RRC: Cell Update (cause: UL Data Transmission or Paging response) and RRC: Utran Mobility Information Confirm (or any other UL-
DCCH message before UMIC). This counter, divided by the denominator, provides the average state transition time.
M1006C171DENOM_ST_TRANS_TIME_PCH_FACH: Denominator for M1006C170 used for average calculation.
M1001C800 RRC_CONN_ACT_REL_HHO: The number of RRC active releases due to inter-frequency inter-RNC hard handover. Updated
when the RNC receives RANAP: IU RELEASE COMMAND with cause "successful relocation" from the CN.
M1001C803 RRC_CONN_ACT_REL_ISHO: The number of RRC active releases due to inter system handover to GSM. Updated when the
RNC receives RANAP: IU RELEASE COMMAND with cause "successful relocation" from the CN.