You are on page 1of 138

Module 2 Performance Monitoring & Data Analysis

3G RANOP RU20
Soc Classification level
1 NSN Siemens Networks Presentation / Author / Date
Module 2 Performance Monitoring & Data Analysis
Course Content
KPI overview
Performance monitoring
Air interface and neighbor optimization
Capacity & traffic optimization
Paging and inter-RNC optimization
Soc Classification level
2 NSN Siemens Networks Presentation / Author / Date
Module Objectives
At the end of the module you will be able to:
Describe 3G RAN performance monitoring process
within R99/R5/6
High level KPIs -> PIs -> Counters
Busy Hour problematic & reporting periods
Describe the mechanism for call analysis related to
RRC/RAB setup/access failure
Session setup failure (NRT, HSDPA, HSUPA)
Soc Classification level
3 NSN Siemens Networks Presentation / Author / Date
Session setup failure (NRT, HSDPA, HSUPA)
SHO/ISHO session/event failures
HSDPA setup & throughput and their failures
List possible reasons for failures & improvement activities
KPI analysis hierarchies
Call/Session setup monitoring & analysis by tools
Release 99: call setup (RRC/RAB)
R99: Call Drop
- Radio link failure rate
- Radio link success rate
R99: Mobility (SHO, HHO, ISHO)
Performance monitoring
Soc Classification level
4 NSN Siemens Networks Presentation / Author / Date
R99: Mobility (SHO, HHO, ISHO)
HSPA setup
HSPA mobility
- Serving Cell Change
RRC states
Appendix
- failure events
issues
KPI analysis hierarchy - performance layers
Call/Session setup monitoring
& analysis by tools
Performance indicator strategy
Release 99: HSPA
call setup call setup
Define tools, interfaces, counters,
and indicators to monitor the NW
performance. Therefore detect at
different phases KPIs.
Tune RAN parameters and optimize
Soc Classification level
5 NSN Siemens Networks Presentation / Author / Date
Iub
WBTS
RRC states
call setup
call drop
Mobility (HOs)
call setup
call drop
mobility
the quality of the NW
KPI analysis hierarchy of evaluation levels
The available data could be classified as in the figure below
There is no point looking at detailed data if the bigger picture is not clear
More details
More
understanding
KPIs (OCSR, CSSR, CCR) Traffica data
Service Level
Traffic
Performance data hierarchy
Soc Classification level
6 NSN Siemens Networks Presentation / Author / Date
understanding
More
complexity
More cost &
time in
acquisition
Traffic
SHO
Signalling (RRC, Iub, Iu, Iur, Relocation)
PMI Tickets NSRP (internal)
ICSU logs (internal)
Interface trace
Cell Resource
IFHO HHO
Subscriber trace
Probe statistics
ISHO
What is cell-specific, what is not
Monitor Cell/Neighbour cells Availability
- missing cell has impact to neighbouring
cells performance also
KPI analysis hierarchy layers
Indicators, counters and parameters Indicators, counters and parameters
detect faults at different layers detect faults at different layers
- Handover Performance
- Traffic
- Cell Resources
- Iub Signalling
Soc Classification level
7 NSN Siemens Networks Presentation / Author / Date
Iub
WBTS
- Cell Availability
- Failures due to Radio, to BTS, to transport
KPI analysis - RAN parameter RU10 objectives
RNC
WBTS
RRM optimisation
RAN parameter and performance strategy
Soc Classification level
8 NSN Siemens Networks Presentation / Author / Date
WBTS
WCEL
RRM optimisation
and tuning at different levels/
NW - elements
What is cell-specific, what is not
The Complexity of the performance data increase with
the number of cells in the network, if it is not properly
summarized. Almost all data has to be analysed at
WCELL or WBTS level for the worst cells -> Evaluation
over time and comparison between large areas (Cities,
RNCs) is still required
Cell Availability
Failures due to Radio, to BTS, to transport
KPI analysis hierarchy of cell layer
Monitor Cell/Neighbour cells Availability -
missing cell has impact to neighbouring
Soc Classification level
9 NSN Siemens Networks Presentation / Author / Date
Failures due to Radio, to BTS, to transport
Handover Performance
Traffic
Cell Resources
Iub Signalling
Some data is better analysed at RNC level->
Here only the time evolution and RNC comparison is
useful
Failures due the RNC, Iu, Iur
Iur, Iu, Relocation Signalling
missing cell has impact to neighbouring
cells performance also
How to Prioritize Analysis ?
Site ID CI RNC Cell Name
Number of
drops
Drop ratio
(%)
Ongoing actions WHO ? WHEN ?
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
611150 64662 31 Berlin 22 13.84 Neighbour sites ? Analyse last field measurements Ramstein W45
370037 43109 21 Bern 20 3.33
200089 45091 11 Athens 19 10.80 Terminal testing ? Pistopoulos W46
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
WEEK 43
TOP 10 Number of
drops RAB Voice+CS
Conv
KPI analysis hierarchy
Soc Classification level
10 NSN Siemens Networks Presentation / Author / Date
Too big lists of results will irritate
consultants.
Main impacts must be visible and
manageable for hands on tasks
Different tables of different data
warehouse must be verifiable
Data/KPI benchmark should be
easy
List top 10-20 worst cells
Because of the large number of cells in the network, it is
not feasible to analyse all the cells. Analyses has to focus
on manageable list of elements.
Exception to this is the handling of customer VIP
complaints, where detailed analysis of specific cells
(otherwise irrelevant) is needed
Good methodology is to list top 10-20 worst cells per
region and to build and follow an action plan on those
How to Prioritize Analysis ?
KPI analysis hierarchy
Soc Classification level
11 NSN Siemens Networks Presentation / Author / Date
region and to build and follow an action plan on those
This required a part-time or dedicated tracking role
Interaction with Operations is required to open relevant
HW/SW tickets and follow changes.
Prioritizing cell with the highest number of failures
KPI analysis hierarchy
Cells order by nb of drops
60%
70%
80%
90%
100%
C
u
m
u
l
a
t
i
v
e

p
e
r
c
e
n
t
a
g
e

o
f

d
r
o
p
s10 worst cells (1% of the area)
cause 14% of the drops
Quick fault diagnostics due to worst cells causes
Soc Classification level
12 NSN Siemens Networks Presentation / Author / Date
0%
10%
20%
30%
40%
50%
1 56 111 166 221 276 331 386 441 496 551 606 661 716 771 826 881 936 991 1046 1101
Nb of cells
C
u
m
u
l
a
t
i
v
e

p
e
r
c
e
n
t
a
g
e

o
f

d
r
o
p
s
Cells order by nb of drops
Either total number of failures or failure rate (%)
could be used
Coverage hole, missing neighbour or capacity
problem
It may be required with some periodicity (e.g. one
month) to reach a more uniform performance, in
Prioritizing cell with the highest number of failures
KPI analysis hierarchy
The prioritization based on the highest
number of failures is preferred:
-Matches with customer experience
Soc Classification level
13 NSN Siemens Networks Presentation / Author / Date
month) to reach a more uniform performance, in
addition with the top number of failures
Larger time periods are preferable, together with a
filter an minimum number of attempts/failures per
cell (depending on network traffic)
-Matches with customer experience
BUT: it is dependent on the traffic -> hotspot
cells may come back every week
Prioritization based on failure rate is
optional:
-Highlights worst performance areas (like
coverage exit points, missing neighbors)
Performance monitoring
KPI analysis - hierarchies
The Key I got The Key I got

Soc Classification level


14 NSN Siemens Networks Presentation / Author / Date
Thank You !

for performance for performance


Indicator I still Indicator I still
improve improve
KPI analysis hierarchies
Call/Session monitoring & analysis
Release 99: call setup (RRC/RAB)
R99: Call Drop
- Radio link failure rate
- Radio link success rate
R99: Mobility (SHO, HHO, ISHO)
Performance monitoring
Soc Classification level
15 NSN Siemens Networks Presentation / Author / Date
R99: Mobility (SHO, HHO, ISHO)
HSPA setup
HSPA mobility
- Serving Cell Change
RRC states
Appendix
- failure events
issues
Performance layers
Call/Session setup monitoring
& analysis by tools
Performance indicator strategy
Release 99: HSPA
call setup call setup
There are several tools for
detecting of NW faults. Related to
sessions, call setup, or RAB
establishments, signalling flows
can indicate NW performance.
Soc Classification level
16 NSN Siemens Networks Presentation / Author / Date
Iub
WBTS
RRC states
call setup
call drop
Mobility (HOs)
call setup
call drop
mobility
MAX (CS_VOICE_CALL_DL + CS_DATA_CALL_CONV_DL +
CS_DATA_CALL_STREAM_DL + PS_DATA_CALL_CONV_DL +
PS_DATA_STREAM_DL + PS_DATA_CALL_INTERA_DL +
PS_DATA_CALL_BACKG_DL)
Daily, Weekly or Busy Hour ?
Call/Session monitoring with tools
NetAct Busy Hour NetAct Busy Hour
definition: RT and NRT is summed every hour
The hour with maximum value is taken for BH
NetAct
Traffic sum:
RT/NRT
*Where xxx_DL= SUM
i
( Bit_Rate
i
* Allocation_Duration
i
)
Soc Classification level
17 NSN Siemens Networks Presentation / Author / Date
0 24 h 12 h
by NetAct
1 h
1 h
1 h
1 h
BH
CDR
CSSR
BH = Busy Hour
CDR = Call Drop Rate
CSSR = Call Setup Success Rate
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
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
Daily, Weekly or Busy Hour ?
Call/Session monitoring
Soc Classification level
18 NSN Siemens Networks Presentation / Author / Date
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.)
3
4
5
6
Voice, GB (AF50%)
R99_DL, GB (25 % AF)
Hourly traffic example, RNC level
Call/Session monitoring & analysis
Soc Classification level
19 NSN Siemens Networks Presentation / Author / Date
0
1
2
3
1
6
/
1
1
/
2
0
0
7

0
0
1
6
/
1
1
/
2
0
0
7

0
1
1
6
/
1
1
/
2
0
0
7

0
2
1
6
/
1
1
/
2
0
0
7

0
3
1
6
/
1
1
/
2
0
0
7

0
4
1
6
/
1
1
/
2
0
0
7

0
5
1
6
/
1
1
/
2
0
0
7

0
6
1
6
/
1
1
/
2
0
0
7

0
7
1
6
/
1
1
/
2
0
0
7

0
8
1
6
/
1
1
/
2
0
0
7

0
9
1
6
/
1
1
/
2
0
0
7

1
0
1
6
/
1
1
/
2
0
0
7

1
1
1
6
/
1
1
/
2
0
0
7

1
2
1
6
/
1
1
/
2
0
0
7

1
3
1
6
/
1
1
/
2
0
0
7

1
4
1
6
/
1
1
/
2
0
0
7

1
5
1
6
/
1
1
/
2
0
0
7

1
6
1
6
/
1
1
/
2
0
0
7

1
7
1
6
/
1
1
/
2
0
0
7

1
8
1
6
/
1
1
/
2
0
0
7

1
9
1
6
/
1
1
/
2
0
0
7

2
0
1
6
/
1
1
/
2
0
0
7

2
1
1
6
/
1
1
/
2
0
0
7

2
2
1
6
/
1
1
/
2
0
0
7

2
3
R99_UL, GB (25 % AF)
HSDPA DL, GB (100% AF)
GB = Giga Byte
AF activity factor
0
0.2
0.4
0.6
0.8
1.0
15 16 17 18 19 20 21 22 23 24
Time / h
L
o
a
d
Cell 1
0
0.2
0.4
0.6
0.8
1.0
15 16 17 18 19 20 21 22 23 24
Time / h
L
o
a
d
Cell 2
Hourly traffic example, cell level
Call/Session monitoring & analysis
Soc Classification level
20 NSN Siemens Networks Presentation / Author / Date
Time / h
Time / h
0
0.2
0.4
0.6
0.8
1.0
15 16 17 18 19 20 21 22 23 24
Time / h
L
o
a
d
Cell 3
0
0.2
0.4
0.6
0.8
1.0
15 16 17 18 19 20 21 22 23 24
Time / h
L
o
a
d
Cell 4
Alternative measure for traffic on DL
Load = TCP / maximum power
*TCP= Transmitted Carrier Power
NSN NetAct contains variety of tools which can be used for
Performance monitoring and data analysis:
NetAct Reporting tools NetAct Reporting tools KPI/Report Browser, Reporting Suite KPI/Report Browser, Reporting Suite
Traffica Tools Traffica Tools Real Time Traffic Monitoring and Troubleshooting Real Time Traffic Monitoring and Troubleshooting
NetAct Monitoring NetAct Monitoring -- Subscriber and equipment trace Subscriber and equipment trace
Reporting Tools
NSN NetAct tools
Call/Session monitoring & analysis with NetAct
Soc Classification level
21 NSN Siemens Networks Presentation / Author / Date
Reporting Tools
Report Builder & Browser Report Builder & Browser
-with default Report Sets
-Reports created with Report builder can be
accessed from web via the Report Browser
Network Doctor for BSS Network Doctor for BSS
- incl. Network Doctor Browser
Reporting Suites Reporting Suites
-With enhanced Report Set
-2G BSS Reporting suite
Reporting In NSN NetAct
Call/Session monitoring & analysis with NetAct
Soc Classification level
22 NSN Siemens Networks Presentation / Author / Date
NetAct
PM DB
Contains ready made reports for analysing network
performance. Most of the reports are based on collected PM
data and NSN-defined KPIs. Some reports also include radio
network parameters and alarm information
User can also create own customized report with own KPI
definitions for Reporting Suite.
Ready made
reports
NetAct reporting suite
Call/Session monitoring & analysis with NetAct
Soc Classification level
23 NSN Siemens Networks Presentation / Author / Date
Export To
excel
NetAct reporting suite
Call/Session monitoring & analysis with NetAct
Soc Classification level
24 NSN Siemens Networks Presentation / Author / Date
NetAct reporting suite
Call/Session monitoring & analysis with NetAct
Soc Classification level
25 NSN Siemens Networks Presentation / Author / Date
Ready made report definitions as well as KPI/PI
formulas can be found from help menu
Real-time traffic monitoring and troubleshooting tool for Multi-
vendor networks
Analysis of subscriber behaviour, roaming, mobile types, used
services. Receives and stores a record of each:
Call & Call attempt
sent or received SMS,
PDP context event etc.
Traffica Real-Time traffic monitoring and troubleshooting
Call/Session monitoring & analysis with NetAct
Soc Classification level
26 NSN Siemens Networks Presentation / Author / Date
Updates counters and present the traffic in real-time graphs:
Number of events
Number of failures
Clear Codes etc.
Traffica can be used monitoring, for example, congestion,
dropped calls, setup failures, RNCs/BSCs, RACs/LACs,
SACs/cells and CGRs. They can also verify the effect of
changes in the configuration in real-time.
RNC monitoring (clear codes) in RAS06 !!
Subscriber and Equipment Trace
Call/Session monitoring & analysis with NetAct
Soc Classification level
27 NSN Siemens Networks Presentation / Author / Date
Trace viewer is tool to start/stop traces
Monitor results by using graph or textual reports
Trace data can be exported to CSV.
Subscriber and Equipment Trace Provide detailed
radio interface data from GSM, GPRS and 3G
networks. Call can be traced by using subscriber's
IMSI, MS-ISDN or equipments IMEI number
Subscriber trace can be used for: Subscriber trace can be used for:
In system testing and provisioning phase for
Subscriber and equipment trace
Call/Session monitoring & analysis with NetAct
Soc Classification level
28 NSN Siemens Networks Presentation / Author / Date
In system testing and provisioning phase for
trouble shooting and network optimisation. E.g.
Ascertain cell coverage, network integrity & QoS
Limited multi Limited multi--vendor support vendor support
Trace data is collected only from NSN elements
and viewed by TraceViewer
Thank You !
Performance monitoring
Call/Session setup monitoring & analysis by tools
Why KPIs do not smell like Why KPIs do not smell like
these sausages? these sausages?
than I would detect than I would detect
them more easily them more easily
Soc Classification level
29 NSN Siemens Networks Presentation / Author / Date
Thank You !
them more easily them more easily
KPI analysis hierarchies
Call/Session setup monitoring & analysis by tools
Release 99: call setup (RRC/RAB)
R99: Call Drop
- Radio link failure rate
- Radio link success rate
R99: Mobility (SHO, HHO, ISHO)
Performance monitoring
Soc Classification level
30 NSN Siemens Networks Presentation / Author / Date
R99: Mobility (SHO, HHO, ISHO)
HSPA setup
HSPA mobility
- Serving Cell Change
RRC states
Appendix
- failure events
issues
Performance layers
Call/Session setup monitoring
& analysis by tools
Performance indicator strategy
Release 99: HSPA
call setup call setup
WW--CDMA specific issues: CDMA specific issues:
There are several phases to allocate
call performance/quality: Starting at
RRC connection setup, connection
access and RRC active & mobility
states
Soc Classification level
31 NSN Siemens Networks Presentation / Author / Date
Iub
WBTS
RRC states
call setup
call drop
Mobility (HOs)
call setup
call drop
mobility
states
Air Interface WBTS HW Resources Transport
UL interference
DL transmisson power
DL Codes
Call setup (RRC/RAB)
RNC
RRC Connection Set-up recourse allocation
During call set-up [RRC, RAB] several
resource areas are checked and
Soc Classification level
32 NSN Siemens Networks Presentation / Author / Date
I uB
FSP/ WSP capacity
(N*) E1 capacity / AAL2
RLC/MAC
DSP processing
resource areas are checked and
physical/ logical resources allocated.
Using Reporting Suite 3G RAN Reports or MS
Access KPI Queries
Weekly KPI
( PLMN)
< X %
No action
needed
No
Yes
No
System Program (PLMN)
Weekly KPI
(RNC)
< X % ?
System Program (RNC)
Mataching failure
distribution into
network topology
Solution Proposal
Mapinfo
call setup (RRC/RAB)
High level PM data analysis and assessment
success ratio > threshold
bad areas nevertheless can exist !!
Soc Classification level
33 NSN Siemens Networks Presentation / Author / Date
Yes
Daily KPI
(WCEL)
< X%
Identify Call failure
phases of bad
performing KPIs, for
example CSSR
Identify failures root-
causes and failure
distribution of bad KPIs
Identify Top50 Worst
Cells based on
highest number of root
causes failures
System Program (WCEL)
Others 3G RAN Reports
Others 3G RAN Reports
Yes
System Program (WCEL)
success ratio < threshold
clearly bad areas present
RRC connection setup
RAN resources are reserved for
signaling connection between UE
and RNC
RRC access
Connection between UE and RRC
RRC active
UE has RRC connection. If
dropped, also active RAB is
dropped.
RAB setup
Attempts to start the call
RAB setup access
Setup
Complete
Access
Complete
Active
Complete
Setup Setup Access Access Active Active
A
c
c
e
s
s
Active
S
u
c
c
e
s
s
Phase:
call setup failures
RRC and RAB phases
Soc Classification level
34 NSN Siemens Networks Presentation / Author / Date
RAB setup access
RAB active phase
UE has RAB connection
CSSR affected if any of the followings
take place:
RRC Conn. Setup Fail
RRC Conn. Access Fail
RAB Setup Fail
RAB Setup Access Fail
A
t
t
e
m
p
t
s
Setup failures
(blocking)
Access failures
A
c
c
e
s
s
Release
Active
Failures
RRC
Drop
1. Assess weekly average PLMN KPI performance to identify KPIs below targets
Start from bigger picture assessment (PLNM -> RNC -> Cluster -> WCEL )
Weekly average will smooth the performance and gives better accuracy of performance
assessment as daily performance varies a lot especially in unloaded network
2. Assess network performance at RNC/Area level to check if bad performance
happens across network or only particular RNC/Area
Compare different RNC/Regions performance
3. Apply drill down approach to assess bad performing KPIs in WCEL level
call setup (RRC/RAB)
PM Data analysis process
Soc Classification level
35 NSN Siemens Networks Presentation / Author / Date
3. Apply drill down approach to assess bad performing KPIs in WCEL level
Identify the failure call phases
Categorizing failure ratio or distribution of each counters (radio, AC, transmission, BTS,
RNC)
Identify main cause of underperforming KPIs
4. Prioritize analysis
Filter using high number of failures or high number failure ratio (weighting)
Identify top 50 worst cells
5. Matching failure distribution in the network topology (rural, RNC border,
expressway)
6. Solution proposal of network KPIs below KPI targets
[RACH] RRC:RRC Connection Request RACH] RRC:RRC Connection Request
UE Node B
RNC
ALCAP:ERQ
NBAP: RL Setup Request
Start TX/RX
NBAP: RL Setup Response
AC to check to accept
or reject RRC
Connection Request
RRC Connection Setup
phase
Allocation of UTRAN
resources
M1001C0
Counter
Three phase for RRC
call setup (RRC/RAB)
RRC Connection set-up: Signaling & trigger
Soc Classification level
36 NSN Siemens Networks Presentation / Author / Date
[DCH] RRC: RRC Connection [DCH] RRC: RRC Connection
Setup Complete Setup Complete
L1 Synchronisation
Start TX/RX
[FACH] RRC: RRC Connection Setup
ALCAP:ECF
NBAP: Synchronisation Indication
RRC Connection Access
phase
RRC Connection Active phase
Waiting for UE reply
RRC active complete Pre-Emption SRNS Relocation
drop
M1001C1
M1001C8
M1001C0
M1001C1
1. KPI
New New
improvement improvement
within RU20 within RU20
Node B starts transmitting
The total delay before UE starts UL The total delay before UE starts UL
transmission is reduced by 70 ms. transmission is reduced by 70 ms.
40 ms window
50 ms window
UE starts transmitting
without
Post Verification
Fast L1 Synchronisation
Quicker access due to post verification of QoS
If CPHY-Sync-IND primitive quality is
sufficiently good, UE starts 70 ms quicker
40 ms window
40 ms window
40 ms window
call setup (RRC/RAB) new within RU20
RRC Connection Access Access phase phase
[DCH] RRC Setup Complete
Soc Classification level
37 NSN Siemens Networks Presentation / Author / Date
Node B starts transmitting
Post verification
check
40 ms window
UE starts transmitting
with Post with Post Verification
UE starts receiving,
mobile is listing on FACH
UE stops transmitting if
verification check fails
10 ms radio
frames
UE L1 collects 40 ms UE L1 collects 40 ms
of quality of quality
measurements measurements
40 ms window
[FACH]: RRC Connection Setup
*N312 = 4 IN_SYNC
Indicators
RRC/RAB Setup & Access Analysis Process Flow Chart RRC/RAB Setup & Access Analysis Process Flow Chart
Sites OK
?
Cell and Neighbour
Cells availability
Alarms/Tickets
Setup
Yes
Setup
/Access
Setup
Failure
Cause?
BTS/TRANS/FROZBS
UL/DL
Interference
AC
Troubleshooting
RNC
Top (N) RRC Setup
and Access failures
Top (N) RAB Setup/Access
or PS Setup failures
Setup
setup
Access
call setup failures
RRC and RAB phases
Soc Classification level
38 NSN Siemens Networks Presentation / Author / Date
Setup
/Access
Capacity
Optimisation
Interference
(DL codes)
RF Optimisation
Coverage/Int
erference
Interference
Coverage
3G cell at
inter-RNC
border ?
SRNS Relocation
troubleshooting
Yes
NO
Access
Access
Admission Control and Admission Control and
BTS are the dominant BTS are the dominant
failure reasons here failure reasons here
RRC Setup Failure Distribution Example - RAS51
0%
50%
45%
2%
2%0% 0% 1%
HC
AC
BTS
TRANS
RNC
FROBTS
RNTI Allo
IUB AAL2 TRANS
RRC Connection & Access Fail - Analysis
BTS
Soc Classification level
39 NSN Siemens Networks Presentation / Author / Date
Example
RAS 5.1
KPI ID example RNC_94c
Radio Interface Synchronisation is Radio Interface Synchronisation is
dominant failure reason here dominant failure reason here
Example
RAS51
RRC Access Fail - Analysis
Soc Classification level
40 NSN Siemens Networks Presentation / Author / Date
Setup and Access Complete ratio is ~ Setup and Access Complete ratio is ~99.5 % 99.5 %
RAS51
NBAP: Synchronisation Indication
L1 Synchronisation
RRC: RRC Connection Setup Complete (DCH)
NBAP: Synchronisation Indication
L1 Synchronisation
RRC: RRC Connection Setup Complete (DCH)
X
UE
BTS
RNC
X
RRC Access Failures for L1 synchronization
RRC Access Fail - Analysis
RRC Access Failure reasons
Soc Classification level
41 NSN Siemens Networks Presentation / Author / Date
RRC Access Failures for L1 synchronization
NBAP: Synchronisation Indication
L1 Synchronisation
RRC: RRC Connection Setup Complete (DCH)
NBAP: Synchronisation Indication
L1 Synchronisation
RRC: RRC Connection Setup Complete (DCH)
X
UE
BTS
RNC
RRC Access Failures due to MS (QoS)
Cell reselections
(no error)
RAB setup fails if some of the needed resources (RNC, BTS, Radio, transport) are not available.
BUT RNC does not reserve radio interface resources in RAB setup phase for NRT
Example
RAS51
A
C
TRAN
S
call setup RAB for NRT
RAB setup failures
Soc Classification level
42 NSN Siemens Networks Presentation / Author / Date
RAB Setup Complete success ratio is close to ~100 %
RAS51
Counters for RAB and DCH Setups and Failure Cases
RAB setup fails for CS Voice due to
Iu-cs/Iur or transport failures
fails/rel due to AMR capacity license
exceeded (for new RNC2600)
RAB setup fails for UDI* & CS
streaming due to Iu-cs/Iur or transport
failures
RAB setup fails for PS streaming due
to Iur transport
M1001C625 ServiceLevel RAB_STP_FAIL_CS_VOICE_IU_CS
M1001C621 ServiceLevel RAB_STP_FAIL_CS_VOICE_IUR_TR
M1001C619 ServiceLevel RAB_STP_FAIL_CS_VOICE_LIC
M1001C622 ServiceLevel RAB_STP_FAIL_CS_CONV_IUR_TR
M1001C623 ServiceLevel RAB_STP_FAIL_CS_STRE_IUR_TR
M1001C626 ServiceLevel RAB_STP_FAIL_CS_CONV_IU_CS
M1001C627 ServiceLevel RAB_STP_FAIL_CS_STRE_IU_CS
M1001C620 ServiceLevel RAB_ACT_REL_CS_VOICE_PRE_LIC
M1001C624 ServiceLevel RAB_STP_FAIL_PS_STRE_IUR_TR
Soc Classification level
43 NSN Siemens Networks Presentation / Author / Date
RRC active release after successful
Directed Retry DR (RAN 928)
M1001C640 ServiceLevel RRC_ACT_REL_DIRECTED_RETRY
*UDI = CS conversational calls no voice calls
M1001C619 RAB setup failures caused by AMR capacity
license for CS voice exceeded
Feature RAN 1198: SW License Key controlled RNC (for
RNC 2600 from RU10)
M1001C620 RAB active release due to pre-emption due
to capacity license exceeded for CS voice
M1001C625 & M1001C621 Voice setup failure due to
lack of AAL2 resources on Iucs/Iur interfaces
RAN 1126: Counters for RAB and DCH Setups and
Failure Cases
New counters to Initial DCH request
(from RAB(0/0) or cell_fach/PCH to
cell_DCH) and success counters
DCH user plane upgrade request &
success counters (to the target bitrate)
M1022C83 Packet_call INIT_DCH_REQ_64_UL
M1022C84 Packet_call INIT_DCH_REQ_64_DL
M1022C85 Packet_call INIT_DCH_REQ_128_UL
M1022C86 Packet_call INIT_DCH_REQ_128_DL
M1022C87 Packet_call INIT_DCH_REQ_256_UL
M1022C88 Packet_call INIT_DCH_REQ_256_DL
M1022C89 Packet_call INIT_DCH_REQ_384_UL
M1022C90 Packet_call INIT_DCH_REQ_384_DL
M1022C99 Packet_call SUCC_INIT_ALLO_64_UL
M1022C100 Packet_call SUCC_INIT_ALLO_64_DL
M1022C101 Packet_call SUCC_INIT_ALLO_128_UL
M1022C102 Packet_call SUCC_INIT_ALLO_128_DL
M1022C103 Packet_call SUCC_INIT_ALLO_256_UL
M1022C104 Packet_call SUCC_INIT_ALLO_256_DL
M1022C105 Packet_call SUCC_INIT_ALLO_384_UL
M1022C106 Packet_call SUCC_INIT_ALLO_384_DL
Soc Classification level
44 NSN Siemens Networks Presentation / Author / Date
M1022C91 Packet_call DCH_UPGR_REQ_64_UL
M1022C92 Packet_call DCH_UPGR_REQ_64_DL
M1022C93 Packet_call DCH_UPGR_REQ_128_UL
M1022C94 Packet_call DCH_UPGR_REQ_128_DL
M1022C95 Packet_call DCH_UPGR_REQ_256_UL
M1022C96 Packet_call DCH_UPGR_REQ_256_DL
M1022C97 Packet_call DCH_UPGR_REQ_384_UL
M1022C98 Packet_call DCH_UPGR_REQ_384_DL
M1022C115 Packet_call SUCC_UPG_NRT_DCH_64_UL
M1022C116 Packet_call SUCC_UPG_NRT_DCH_64_DL
M1022C117 Packet_call SUCC_UPG_NRT_DCH_128_UL
M1022C118 Packet_call SUCC_UPG_NRT_DCH_128_DL
M1022C119 Packet_call SUCC_UPG_NRT_DCH_256_UL
M1022C120 Packet_call SUCC_UPG_NRT_DCH_256_DL
M1022C121 Packet_call SUCC_UPG_NRT_DCH_384_UL
M1022C122 Packet_call SUCC_UPG_NRT_DCH_384_DL
* Counters available from RU10
Thank You !
Performance monitoring
Release 99: call setup (RRC/RAB)
Not every successful setup is Not every successful setup is
that important that important
but easier but easier
Soc Classification level
45 NSN Siemens Networks Presentation / Author / Date
Thank You !
but easier but easier
KPI analysis hierarchies
Call/Session setup monitoring & analysis by tools
Release 99: call setup (RRC/RAB)
R99: Call Drop
- Radio link failure rate
- Radio link success rate
R99: Mobility (SHO, HHO, ISHO)
Performance monitoring
Soc Classification level
46 NSN Siemens Networks Presentation / Author / Date
R99: Mobility (SHO, HHO, ISHO)
HSPA setup
HSPA mobility
- Serving Cell Change
RRC states
Appendix
- failure events
Call Drop analysis
Top (N) drops
Cell and its Neighbour
Cells availability
Alarms/Tickets
Configuration &
Parameter audit
SHO
Success
Rate < 90%?
Conf OK ?
Site OK ?
Iur
performance
Investigation Iur
Audit adjacent sites for alarms,
Availability, configuration and
capacity
Traffic
Neighbours Performance
(use SHO success per adjs
counters to identify badly
performing neighbours) & Map
3G Cell at RNC
border?
NO
YES
YES
YES
YES
SHO
Soc Classification level
47 NSN Siemens Networks Presentation / Author / Date
ISHO
Failures
New site ?
Analyse last detailed
radio measurements
RF and IFHO neighbour
optimisation
No cell
found ratio
>40 %
ISHO
Success
Rate < 90%
RF and ISHO neighbour
optimisation
3G cell covers
over a coverage
hole ?
3G cell at inter-
RNC border ?
Wrong reference clock
(10MHz tuning)
No cell found
ratio > 90 %
and enough
ADJG
2G Cell Doctor
2G Investigation :
TCH blocking or
TCH seizure failure
(interference)
NO
YES
NO
NO
YES
YES
ISHO
Top
issu
es
Radio Link Failure
Iub Counter table (M1005 counters) measurements can be used to detect Radio
Link Deletion rate due the active L1 synchronisation failure
The KPI measures the percentage of radio link deletions to the total number of
radio links that were successfully established i.e. initial, soft and softer handover.
Use raw counters for following KPI to detect cells with high synchronisation failure
Compare Cell Level KPI to RNC Level KPI
Soc Classification level
48 NSN Siemens Networks Presentation / Author / Date
RL SHO FOR SUCC SETUP RL
RL FIRST FOR SUCC SETUP RL
SRNC SHO SUCC ADD BRANCH RL
FAIL SYN RL ACT SRNC SHO DEL
ACT LOST UL
_ _ _ _ _
_ _ _ _ _
_ _ _ _ _
_ _ _ _ _ _
_ _
+
+
=
NUMBER OF ACTIVE RADIO
LINKS IN THE IUB
NUMBER OF RADIO LINK
DELETION FOR ACTIVE
SYN FAILURE
Downlink radio link failure results in
an UL synchronization loss since
the UE stops transmitting.
The synchronization failure may happen due
to:
-UL/DL coverage or interference problems
-UE not answering to ASU = active set update
-> see next slide
RAS06 new SHO counters
It is possible to see the ASU = Active set update performance counters:
M1006C121 ACTIVE SET UPDATE RL ADD ATTEMPTS
M1006C122 ACTIVE SET UPDATE RL ADD SUCCESS
M1006C123 ACTIVE SET UPDATE RL ADD FAILURE UE
M1006C124 ACTIVE SET UPDATE RL ADD FAIL NO REPLY
M1006C125 ACTIVE SET UPDATE RL DEL ATTEMPTS
M1006C126 AS_UPDATE_RL_DEL_SUCC
Soc Classification level
49 NSN Siemens Networks Presentation / Author / Date
Possible Scenarios:
1. UL coverage <<DL coverage: SHO decision is based on
DL Ec/No while synchronisation is UL (high number of cell
addition fail)
2. Crossing spot coverage: while moving the UE enters in
small coverage area for a short period (If there is not
enough time to get UL initial synchronisation)
Thank You !
Performance monitoring
R99: Call Drop
Huauwei E 870
Soc Classification level
50 NSN Siemens Networks Presentation / Author / Date
Thank You !
CDR can have several CDR can have several
reasons reasons
but sometimes only but sometimes only
specific handsets gives specific handsets gives
response at Iub response at Iub
KPI analysis hierarchy
Call/Session setup monitoring & analysis by tools
Release 99: call setup (RRC/RAB)
R99: Call Drop
- Radio link failure rate
- Radio link success rate
R99: Mobility (SHO, HHO, ISHO)
Performance monitoring
Soc Classification level
51 NSN Siemens Networks Presentation / Author / Date
R99: Mobility (SHO, HHO, ISHO)
HSPA setup
HSPA mobility
- Serving Cell Change
RRC states
Appendix
- failure events
R99: Mobility - SHO Overhead
Check SHO Overhead to see how big is SHO area, if it is too small SHO may
fails and if too big capacity is wasted (see calculations)
) 1 ) _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _ _ _ _ _ (
) 3 * ) _ _ _ _ _ _ _ _ _ _ _ _ (
2 * ) _ _ _ _ _ _ _ _ _ _ _ _ (
1 * ) _ _ _ _ _ _ _ _ _ _ _ _ (( ( * 100
_
+ +
+ +
+
+ +
+ +
+
=
NRT FOR SET ACT IN CELL THREE RT FOR SET ACT IN CELLS THREE
NRT FOR SET ACT IN CELL TWO RT FOR SET ACT IN CELLS TWO
NRT FOR SET ACT IN CELL ONE RT FOR SET ACT IN CELL ONE sum
NRT FOR SET ACT IN CELL THREE RT FOR SET ACT IN CELLS THREE
NRT FOR SET ACT IN CELL TWO RT FOR SET ACT IN CELLS TWO
NRT FOR SET ACT IN CELL ONE RT FOR SET ACT IN CELL ONE sum
Overhead SHO
Soc Classification level
52 NSN Siemens Networks Presentation / Author / Date
) _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _ _ _ _ _ (
) _ _ _ _ _ _ _ _ _ _ ( * 100
_ _
NRT FOR SHO ON REQ DEL CELL NRT FOR SHO ON REQ REPL CELL
NRT FOR SHO ON REQ ADD CELL RT FOR SHO ON REQ DEL CELL
RT FOR SHO ON REQ REPL CELL RT FOR SHO ON REQ ADD CELL sum
NRT FOR SHO ON UPDATES SUCC RT FOR SHO ON UPDATES SUCC sum
ratio Success SHO
+ +
+ +
+
+
=
SHO success (RNC_195a)
SHO success and SHO OH can be calculated separately for
RT & NRT these examples contains both
cell 1
# radio links
# users
R99: Mobility - SHO Overhead on RNC level (1/4)
E1A CPICH E1B CPICH
Offset 4dB Offset 6dB
SHO SHO
area area
53 Nokia Siemens Networks RANKPI /BAs / 05.05.2009
cell 1
cell 2
NRT RT SET ACT IN CELL THREE
NRT RT SET ACT IN CELL TWO
NRT RT SET ACT IN CELL ONE
NRT RT SET ACT IN CELL THREE
NRT RT SET ACT IN CELL TWO
NRT RT FOR SET ACT IN CELL ONE
/ _ _ _ _ _
/ _ _ _ _ _
/ _ _ _ _ _
3 / _ _ _ _ _
2 / _ _ _ _ _
/ _ _ _ _ _ _
+
+

+
+
Factors are
RL (1, 2 ,3 )
of users
# of users
Users
who stays
within
different
AS size
R99: Mobility - SHO Overhead on RNC level (2/4)
AS 1 AS 1
AS 2 AS 2
AS 3 AS 3
+
+
1 2
3
# of UE within AS 1 # of UE within AS 2 # of UE within AS 3
+ +
Total # of links
UE's within AS 3 (3 cells)
3 links 3 links per UE per UE
UE's within AS 2 (2 cells)
2 links per UE 2 links per UE
UE's within AS 1(1 cell)
1 link per UE 1 link per UE
Reminder: Reminder:
Low # of UE's
within AS 3 (5-8%)
Soc Classification level
54 NSN Siemens Networks Presentation / Author / Date
NRT RT SET ACT IN CELL THREE
NRT RT SET ACT IN CELL TWO
NRT RT SET ACT IN CELL ONE
NRT RT SET ACT IN CELL THREE
NRT RT SET ACT IN CELL TWO
NRT RT FOR SET ACT IN CELL ONE
/ _ _ _ _ _
/ _ _ _ _ _
/ _ _ _ _ _
3 / _ _ _ _ _
2 / _ _ _ _ _
/ _ _ _ _ _ _
+
+

+
+
AS 1 AS 1
AS 2 AS 2
AS 3 AS 3
+ +
# of UE linked
within AS 1+2+3
Total # of
links within
cluster
=
SHO overhead
within cluster
Total #
UE's within
cluster
# UE # UE # UE
NRT RT SET ACT IN CELL THREE
NRT RT SET ACT IN CELL TWO
NRT RT SET ACT IN CELL ONE
NRT RT SET ACT IN CELL THREE
NRT RT SET ACT IN CELL TWO
NRT RT FOR SET ACT IN CELL ONE
/ _ _ _ _ _
/ _ _ _ _ _
/ _ _ _ _ _
3 / _ _ _ _ _
2 / _ _ _ _ _
/ _ _ _ _ _ _
+
+

+
+
Simple example
R99: Mobility - SHO Overhead on RNC level (3/4)
cell 1
cell 2
1 link,
AS1
2 links, AS2
1.5 SHO
Soc Classification level
55 NSN Siemens Networks Presentation / Author / Date
Cell 1
Cell 2
1 cell in
Active Set
2 cells in
Active Set
1
0
1
1
NRT RT SET ACT IN CELL THREE / _ _ _ _ _
AS 1 AS 1
AS 2 AS 2
+
1 2
1 UE within AS 1 1 UE within AS 2
AS 1 AS 1
AS 2 AS 2
+
Total: 3
links
within
cluster
(1UE within AS1) (1UE within AS2)
2 UE's
within
cluster
=
R99: Mobility - SHO Overhead on RNC level (4/4)
cell 1
cell 2
1 link,
AS1
2 links, AS2
Simple example
Attempt to apply formula on cell level
AS 1 AS 1
AS 2 AS 2
+
1 2
1 UE within AS 1 1 UE within AS 2
+
= 1.5 for cell 1
Soc Classification level
56 NSN Siemens Networks Presentation / Author / Date
AS 1 AS 1
AS 2 AS 2
+
(1UE within AS1) (1UE within AS2)
AS 2 AS 2
2
0 UE within AS 1 1 UE within AS 2
AS 2 AS 2
(0UE within AS1) (1UE within AS2)
= 2.0 for cell 2
Average 1.75
deviates strongly from result
1.5 on RNC level
3 / / _ _ _ _ _
2 / / _ _ _ _ _
/ _ _ _ _ _
/ _ _ _ _ _
/ _ _ _ _ _
/ _ _ _ _ _ _
NRT RT SET ACT IN CELL THREE
NRT RT SET ACT IN CELL TWO
NRT RT SET ACT IN CELL ONE
NRT RT SET ACT IN CELL THREE
NRT RT SET ACT IN CELL TWO
NRT RT FOR SET ACT IN CELL ONE
+
+
+
+
# Users
# cell
R99: Mobility - SHO Overhead on cell level (1/4)
Fair calculation of Average AS size at (RNC 192b) cell specific
Total #
UE's within
cells
Total effective
# of cells
=
57 Nokia Siemens Networks RANKPI /BAs / 05.05.2009
cell 1
cell 2
TIMEa cell belongs to an active set with size 1, 2 or 3
NOTnumber of UEs with 1, 2 or 3 radio links
M1007C0 ONE_CELL_IN_ACTIVE_SET_FOR_RT
M1007C19 ONE_CELL_IN_ACTIVE_SET_FOR_NRT
M1007C1 TWO_CELL_IN_ACTIVE_SET_FOR_RT
M1007C20 TWO_CELL_IN_ACTIVE_SET_FOR_NRT
M1007C2 THREE_CELL_IN_ACTIVE_SET_FOR_RT
M1007C21 THREE_CELL_IN_ACTIVE_SET_FOR_NRT
Calculation of UE link performance at cell level
R99: Mobility - SHO Overhead on cell level (2/4)
AS 1 AS 1
AS 2 AS 2
AS 3 AS 3
+ +
3 cells
+ +
AS 3 AS 3
Total effective
# of cells
(# of UE; AS1) (# of UE; AS2) (# of UE; AS3)
# UE # UE # UE
Total # UEs
within cells
2 cells
1 UE
1 cell
1 UE
Soc Classification level
58 NSN Siemens Networks Presentation / Author / Date
Total # of
cells
=
SHO
overhead
per cell
3 / / _ _ _ _ _
2 / / _ _ _ _ _
/ _ _ _ _ _
/ _ _ _ _ _
/ _ _ _ _ _
/ _ _ _ _ _ _
NRT RT SET ACT IN CELL THREE
NRT RT SET ACT IN CELL TWO
NRT RT SET ACT IN CELL ONE
NRT RT SET ACT IN CELL THREE
NRT RT SET ACT IN CELL TWO
NRT RT FOR SET ACT IN CELL ONE
+
+
+
+
# of cells
Averaged cell
area/user
Total #
UE's within
cells
AS 2 AS 2 AS 1 AS 1
With # of UE's With # of UE's
100% sharing of cell 100% sharing of cell
With # of UE's With # of UE's
50% sharing of cell 50% sharing of cell
With # of UE's With # of UE's
33% sharing of cell 33% sharing of cell
3 / / _ _ _ _ _
2 / / _ _ _ _ _
/ _ _ _ _ _
/ _ _ _ _ _
/ _ _ _ _ _
/ _ _ _ _ _ _
NRT RT SET ACT IN CELL THREE
NRT RT SET ACT IN CELL TWO
NRT RT SET ACT IN CELL ONE
NRT RT SET ACT IN CELL THREE
NRT RT SET ACT IN CELL TWO
NRT RT FOR SET ACT IN CELL ONE
+
+
+
+
R99: Mobility - SHO Overhead on cell level (3/4)
Simple example
cell A
cell B
user A
user B
Soc Classification level
59 NSN Siemens Networks Presentation / Author / Date
Cell A
Cell B
1 in Active
Set
2 in Active
Set
1
0
1
1
Sum
(Cell)
1
2
AS 1 AS 1
AS 2 AS 2
+
+
(1UE; AS1) (1UE; AS2)
=
50% of cell
area B is
related to
User B
2 cells
AS 2 AS 2
1 UE
Total effective
# of cells
Total # UE
within cells
2
1.5
1 cell
AS 1 AS 1
1 UE
100% of
cell area A
is related
to User A
R99: Mobility - SHO Overhead on cell level (4/4)
Simple example
Average 1.67
AS 1 AS 1
AS 2 AS 2
+
+
(1UE; AS1) (1UE; AS2)
=
50% of cell
area B is
related to
User B
2 cells
AS 2 AS 2
1 UE
1 cell
AS 1 AS 1
1 UE
100% of
cell area A
is related
to User A
1.33 for cell 1
Soc Classification level
60 NSN Siemens Networks Presentation / Author / Date
AS 2 AS 2
(0 UE; AS1) (1UE; AS2)
=
50% of cell
area B is
related to
User B
2 cells
AS 2 AS 2
1 UE
2.00 for cell 2
Agrees better with result 1.5
on RNC level
AS 2 AS 2
AS 1 AS 1
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)
IFHO Success per Adjacency (M1014 AutoDef IFHO)
) _ _ _ _ _ (
) _ _ _ _ _ ( * 100
900 _ _ _ _ _
ATT SHO FREQ INTRA ADJ SHO sum
COMPL SHO FREQ INTRA ADJ SHO sum
a RNC ADJS per success SHO =
Soc Classification level
61 NSN Siemens Networks Presentation / Author / Date
IFHO Success per Adjacency (M1014 AutoDef IFHO)
ISHO Success per Adjacency (M1015 AutoDef ISHO)
) _ _ _ _ _ (
) _ _ _ _ _ ( * 100
901 _ _ _ _ _
ATT HHO FREQ INTER ADJ HHO sum
COMP HHO FREQ INTER ADJ HHO sum
a RNC ADJI per success IFHO =
) _ _ _ _ _ (
) _ _ _ _ _ ( * 100
902 _ _ _ _ _
ATT HHO SYS INTER ADJ HO sum
COMPL HHO SYS INTER ADJ HO sum
a RNC ADJG per success ISHO =
R99: Mobility - ISHO analysis Flow Chart
ISHO Success Rate RT
Top N cells
RNC_300c < X
%
No action
needed
No
No
No
Low ISHO
Success ?
Low ISHO
Measurement
success ?
CM Start Not
Possible?
Yes
No
Handover -> Report RSRAN018
Handover -> Report RSRAN019
Handover-> Report RSRAN023
Soc Classification level
62 NSN Siemens Networks Presentation / Author / Date
Missing ADJG or
Bad Neighbour
planning ?
Wrong 2G Ncell
Parameter (BSIC)
Or BSIC collision
Yes
Yes
Too low ISHO
triggering threshold or
Strict ADJG minimum
threshold
(ADJGRxLevMinHO)
Non-optimum
Compressed mode
parameter set
Missing or wrong
2G parameter in 2G
MSC or SGSN
(BCCH, LAC,
CellID)
2G Ncell
Congestion
Missing neighbour
list after re-
selection after cell
change order
occured
Half Rate in 2G
Ncell ?
Poor GSM
Coverage
Check admission
control rejection ->
PrxTotal & PtxTotal
Yes
R99: Mobility ISHO analysis
1. Analysis should be performed for each service (i.e. AMR, PS etc.)
2. Breakdown ISHO analysis into three phases:
Compressed mode performance
Inter-system measurement success
Inter-system handover success
50
60
70
IS_COM_MOD_STA_NOT_P
samples
Soc Classification level
63 NSN Siemens Networks Presentation / Author / Date
0
10
20
30
40
2
0
0
4
0
9
0
6
2
0
0
4
0
9
0
7
2
0
0
4
0
9
0
8
2
0
0
4
0
9
0
9
2
0
0
4
0
9
1
0
2
0
0
4
0
9
1
1
2
0
0
4
0
9
1
2
2
0
0
4
0
9
1
3
IS_COM_MOD_STA_NOT_P
OS_RT
UE_PWR_RT
ISHO compressed mode not possible
R99: Mobility ISHO analysis
3. If high ISHO compressed mode start not possible
Check busy hour data of PrxTotal , PtxTotal and M1000C22 AVE_PTXTOT_CLASS_4 and
M1000C20 AVE_PTXTOT_CLASS_3 for AC rejection
-85
-80
-75
Average_PrxTotal_excl_0 Average_PrxTotal_class_0 AVG_PRX_PWR
Soc Classification level
64 NSN Siemens Networks Presentation / Author / Date
-110
-105
-100
-95
-90
-85
2
0
0
4
0
9
0
9
0
0
2
0
0
4
0
9
0
9
0
1
2
0
0
4
0
9
0
9
0
2
2
0
0
4
0
9
0
9
0
3
2
0
0
4
0
9
0
9
0
4
2
0
0
4
0
9
0
9
0
5
2
0
0
4
0
9
0
9
0
6
2
0
0
4
0
9
0
9
0
7
2
0
0
4
0
9
0
9
0
8
2
0
0
4
0
9
0
9
0
9
2
0
0
4
0
9
0
9
1
0
2
0
0
4
0
9
0
9
1
1
2
0
0
4
0
9
0
9
1
2
2
0
0
4
0
9
0
9
1
3
2
0
0
4
0
9
0
9
1
4
2
0
0
4
0
9
0
9
1
5
2
0
0
4
0
9
0
9
1
6
2
0
0
4
0
9
0
9
1
7
2
0
0
4
0
9
0
9
1
8
2
0
0
4
0
9
0
9
1
9
2
0
0
4
0
9
0
9
2
0
2
0
0
4
0
9
0
9
2
1
2
0
0
4
0
9
0
9
2
2
2
0
0
4
0
9
0
9
2
3
hour
d
B
m
Thank You !
Performance monitoring
R99: Mobility (SHO, HHO, ISHO)
You see not only mobiles can stay in SHO You see not only mobiles can stay in SHO
Soc Classification level
65 NSN Siemens Networks Presentation / Author / Date
Thank You !
just married and static HO just married and static HO
KPI analysis hierarchy
Call/Session setup monitoring & analysis by tools
Release 99: call setup (RRC/RAB)
R99: Call Drop
- Radio link failure rate
- Radio link success rate
R99: Mobility (SHO, HHO, ISHO)
Performance monitoring
Soc Classification level
66 NSN Siemens Networks Presentation / Author / Date
R99: Mobility (SHO, HHO, ISHO)
HSPA setup
HSPA mobility
- Serving Cell Change
RRC states
Appendix
- failure events
issues
Performance layers
Call/Session setup monitoring
& analysis by tools
Performance indicator strategy
Release 99: HSPA
call setup call setup
HSPA specific issues: HSPA specific issues:
There are several phases to allocate
call performance/quality: Starting at
RRC connection setup, connection
access and RRC active & mobility
states
Soc Classification level
67 NSN Siemens Networks Presentation / Author / Date
Iub
WBTS
RRC states
call setup
call drop
Mobility (HOs)
call setup
call drop
mobility
states
HSDPA Accessibility failure analysis
HSDPA Accessibility User Point of View Ratio
Top X cells
RNC_605a< X %
Setup Fail UL Setup Fail Iub
Setup Fail RNC
Setup Fail Too
No action
needed
No
Yes
No No No No
No
Soc Classification level
68 NSN Siemens Networks Presentation / Author / Date
Setup Fail BTS
Setup Fail UL
return Channel
Setup Fail Iub
Transport
Setup Fail UE
Setup Fail RNC
internal
Many Users
Check CE
resource usage
at BH
UL power
congestion
BH ?
Check AAL2 Iub
resource
congestion at BH
Check RB
reconfiguration
Failure rate
Check RNC Unit
load (DMPG)
and faulty alarms
Check number of
simultaneous
HSDPA users
Yes
Yes
Yes
Yes Yes
Yes
No
HSDPA Accessibility analysis
1. Identify root cause of failure distribution and main failure contributor
Soc Classification level
69 NSN Siemens Networks Presentation / Author / Date
2. If high HSDPA Access Failure _too many HSDPA users
Check simultaneous HSDPA users (RNC_646a to RNC_654a)
DCH selected due to too many HSDPA users, rnc_660a
3. If high HSDPA Access Failure_UL DCH (RNC_662a)
Rejected HS-DSCH return channel due to lack of radio (lack of power resource)
Monitor UL load
Increase PrxTarget
4. If high HSDPA Access Failure_UE
Check RB reconfiguration failure rate
ICSU log for UE types troubleshooting ?
M1002C401 REJ_HS_DSCH_RET_INT
M1002C402 REJ_HS_DSCH_RET_BGR
M1002C577 REJ_HS-DSCH_STRE
M1002C476 DCH_SEL_MAX_HSDPA_USERS_BGR
M1002C477 DCH_SEL_MAX_HSDPA_USERS_INT
M1002C591 DCH_SEL_MAX_HSDPA_USERS_STRE
M1002C415 SETUP_FAIL_UE_HS_DSCH_INT
M1002C423 SETUP_FAIL_UE_HS_DSCH_BGR
HSDPA Accessibility analysis
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
800
1000
1200
20
25
30
(%)
Failures (BH)
M1002C416 SETUP_FAIL_BTS_HS_DSCH_INT or
M1002C424 SETUP_FAIL_BTS_HS_DSCH_BGR
Soc Classification level
70 NSN Siemens Networks Presentation / Author / Date
0
200
400
600
800
1 14 27 40 53 66 79 92 105 118 131 144 157 170 183 196 209 222 235 248 261 274 287
0
5
10
15
20
SETUP_FAIL_BTS_HS_DSCH_BGR (Traffic)
AVE_AVAIL_PERC_POOL_CAPA_UL (Cellres)
# cells
HSDPA Accessibility analysis
6. HS-DSCH return channel setup fail due to Iub transport (AAL2)
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
Return channel setup failure due to transport
M1002C505 SETUP_FAIL_16_IUB_HSDSCH_INT or
M1002C506 SETUP_FAIL_16_IUB_HSDSCH_BGR
M1002C418 SETUP_FAIL_64_IUB_HSDSCH_INT or
M1002C426 SETUP_FAIL_64_IUB_HSDSCH_BGR,
Soc Classification level
71 NSN Siemens Networks Presentation / Author / Date
M1002C426 SETUP_FAIL_64_IUB_HSDSCH_BGR,
M1002C419 SETUP_FAIL_128_IUB_HSDSCH_IN or
M1002C427 SETUP_FAIL_128_IUB_HSDSCH_BG,
M1002C420 SETUP_FAIL_384_IUB_HSDSCH_IN or
M1002C428 SETUP_FAIL_384_IUB_HSDSCH_BG,
MAC-d flow setup failure due to Iub transport (AAL2)
M1002C414 SETUP_FAIL_IUB_MAC_D_INT
M1002C422 SETUP_FAIL_IUB_MAC_D_BGR
HSUPA Accessibility Analysis
In case of congestion with Iub or RNC: In case of congestion with Iub or RNC:
RNC sends HSUPA Congestion Control indications to the BTS based on detected
received Iub FP frame delay build up or RNC HW overload. Following counters
count those messages:
M1022C69 IUB_DELAY_CC_DELAY_IND
M1022C70 HW_OVERL_CC_DELAY_IND
RNC sends HSUPA Congestion Control indications to the BTS based on detected
Soc Classification level
72 NSN Siemens Networks Presentation / Author / Date
received Iub FP frame frame loss due to Iub delay, traffic loss or RNC HW overload.
Following counters count those messages:
M1022C71 IUB_LOSS_CC_FRAME_LOSS_IND
M1022C72 IUB_DELAY_CC_FRAME_LOSS_IND
M1022C73 HW_OVERL_CC_FRAME_LOSS_IND
M1022 packet call measurements
M1022 C69 M1022C73 counters related to the feature RAN
992: HSUPA Congestion Control
M1022C69 congestion control detected by Frame Protocol
Entity
M1022C70 congestion detected by the HW overload
congestion control unit
M1022C71 Iub traffic loss indicated by the frame protocol
Thank You !
Performance monitoring
HSPA setup
Soc Classification level
73 NSN Siemens Networks Presentation / Author / Date
Thank You !
Please consider Please consider
Release 99 users will partly suffer Release 99 users will partly suffer
due to HSPA speed and capability due to HSPA speed and capability
KPI analysis hierarchy
Call/Session setup monitoring & analysis by tools
Release 99: call setup (RRC/RAB)
R99: Call Drop
- Radio link failure rate
- Radio link success rate
R99: Mobility (SHO, HHO, ISHO)
Performance monitoring
Soc Classification level
74 NSN Siemens Networks Presentation / Author / Date
R99: Mobility (SHO, HHO, ISHO)
HSPA setup
HSPA mobility
- Serving Cell Change
RRC states
Appendix
- failure events
Active Set Update and Serving Cell Change (A-DCH)
Addition
window
4dB
CPICH 1 R99
CPICH 2 R5/6
E
C
/I
0
periodic reports as
HSDPAServCellWindow
RNC; 0..6; 0.5; 2 dB
Active set update and serving cell change with associated DCH
Drop
window
6dB
75 Nokia Siemens Networks RN30095EN20GLA0
time
SHO for A-
DCH initiated
Periodic
reports
Serving cell change
initiated CPICH 2 active
periodic reports as
long UE in SHO area
Addition Time
R 99 R 5/6 One RL only
Inter-BTS serving cell change
1. Serving cell change started due to ASU update
2. Serving cell change started due to CPICH Ec/No
3. Serving cell change started due to UL SIR Error
4. Serving cell change started due to other reason
(e.g. RL Failure, event 6F)
5. Serving cell change prevented due to timer
Soc Classification level
76 NSN Siemens Networks Presentation / Author / Date
6. Serving cell change failure due to AC
7. Serving cell change failure due to BTS
8. Serving cell change failure due to transport
9. Serving cell change failure due to UE
10. Number of successful inter-BTS serving cell
changes
Intra-BTS serving cell change
1. Serving cell change started due to active set update
2. Serving cell change started due to CPICH Ec/No
3. Serving cell change started due to UL SIR Error
4. Serving cell change started due to other reason (e.g. RL
Failure, event 6F)
5. Serving cell change prevented due to timer
6. Serving cell change failure due to AC
Soc Classification level
77 NSN Siemens Networks Presentation / Author / Date
6. Serving cell change failure due to AC
7. Serving cell change failure due to BTS
8. Serving cell change failure due to transport
9. Serving cell change failure due to UE
10. Number of successful intra-BTS serving cell changes
Attempt and failure counters are updated to the current
serving cell. Successful counters are updated to the new
serving cell
HSDPA SCC Analysis
HSDPA SCC Success Rate
Top N cells
SCC Fail BTS
RNC_733a < X %
SCC Fail AC
SCC Fail
Transmission
SCC Fail UE
SCC Fail
Others
No action
needed
No
Yes
Yes
Yes
Yes
Yes
Yes
No No
No
No
SCC Fail
Prevention
timer
No
Ye
Soc Classification level
78 NSN Siemens Networks Presentation / Author / Date
Check CE
resource usage
at BH
scrambling code
congestion BH
DL power
congestion
BH ?
Check AAL2 Iub
resource
congestion at BH
Check RB
reconfiguration
Failure rate
Check RNC
internal transport
resources
(DMPG) ICSU
troubleshooting
Yes
Yes
Yes
Yes
Yes
No
Check
HSDPACellChan
geMinInterval
parameter
Check Maximum
number of
HSDPA users
No
Ye
s
HSDPACellChange
MinInterval
RNC; k = 0..10; 1; 3 s
HSDPA SCC analysis
1. Determine SCC success rate, SCC failure rate and failure cause distribution
2. Check target cells HSDPA Setup performance (M1002C401 M1002C428) if source
cells SCC failure rate is high
To find out which target cells are causing the SCC failure
3. If high SCC_FAILED_due_to_AC
Check target cells M1000C22 AVE_PTXTOT_CLASS_4 and M1000C20 AVE_PTXTOT_CLASS_3 if SCC
failures due to the lack of DL power (SCC_Failed_due_to_AC) this is not visible in HSDPA accessibility
KPI- Check target cells number of simultaneous active HSDPA users
Soc Classification level
79 NSN Siemens Networks Presentation / Author / Date
HSPA started
HSDPA SCC Analysis
4. If high SCC_FAILED_due_to_BTS
Check target cells M1002C416/424 SETUP_FAIL_BTS_HS_DSCH_XXX
Check target cells CE resource utilisation at BH using M5001 counters for lack of UL return channel
resource
Check NBAP Radio Link Reconfiguration Failure rate
Check SHO overhead all branches must have enough CE capacity if UE is in SHO when HS-DSCH
allocation is started
5. If high SCC_FAILED_due_to_UE
Check target cells M1002C415/423 SETUP_FAIL_UE_HS_DSCH_XXX
Check RB reconfiguration Failure rate
Soc Classification level
80 NSN Siemens Networks Presentation / Author / Date
Require ICSU troubleshooting for UE types monitoring
6. If high SCC_FAILED_due_to_TRANS
Check target cells of M1002C414 SETUP_FAIL_IUB_MAC_D_INT or M1002C422
SETUP_FAIL_IUB_MAC_D_BGR
Evaluate number of reconfiguration failure due the transmission
Check M1005C128 CANC_ADD_SRNC_TRAN_STP_FAIL
Check M1001C531-C533 RAB_STP_FAIL_XXX_IUB_AAL2
7. If high SCC_FAILED_due_to_Others
Check RNC internal transport resources usage (DMPG)
Require ICSU troubleshooting
HSDPA SCC upgrade within RU20
Fractional DPCH
Rel. 6: Fractional DPCH: F-DPCH
Node
B
RNC
Iub
H
S
-
S
C
C
H
H
S
-
S
C
C
H
H
S
-
D
S
C
H
H
S
-
D
S
C
H
F
-
D
P
C
H
F
-
D
P
C
H
H
S
-
D
P
C
C
H
H
S
-
D
P
C
C
H
DPDCH
F-PDCH
HS - DSCH
Deactivation of R99
- F-DPCH replaces the downlink DPCCH
- SRB on HSPA capabilities
Soc Classification level
81 NSN Siemens Networks Presentation / Author / Date
Iub
F-DPCH:
Fractional Dedicated Physical Channel
Rel. 6 DL channel
in case of pure HSDPA & HSUPA
data transmission (without a-DCH)
carries only L1 TPCs
TPCs for up to 10 users
users TPCs are time-multiplexed
SF = 256 15 ksymb/s
1user: 1 TPC (= 2 bit) information/slot
SRBs on HS-DSCH if no a-DCH
F-DPCH:
Fractional Dedicated Physical Channel
Rel. 6 DL channel
in case of pure HSDPA & HSUPA
data transmission (without a-DCH)
carries only L1 TPCs
TPCs for up to 10 users
users TPCs are time-multiplexed
SF = 256 15 ksymb/s
1user: 1 TPC (= 2 bit) information/slot
SRBs on HS-DSCH if no a-DCH
H
S
U
P
A

c
h
a
n
n
e
l
s
H
S
U
P
A

c
h
a
n
n
e
l
s
H
S
-
D
P
C
C
H
H
S
-
D
P
C
C
H
Data block 1 TPC
TFCI
optional
Data block 2 Pilot Data block 1 TPC
TFCI
optional
Data block 2 Pilot
1 Slot = 2/3 ms = 2560 chip
TPC
F-DPCH slot
DPCH slot
TX OFF TX OFF
Allocating F-DPCH & HSPA SRB (I) RU20
F-DPCH shall be allocated whenever possible, i.e. not only if 'CPC' or 'CS voice over
HSPA' requires it
The RNC shall allocate the F-DPCH if:
UE supports Release 7 F-DPCH
Release 7 F-DPCH is enabled in all cells of the current DCH active set
E-DCH active set is equal to DCH active set
F-DPCH is allowed for the used service as defined by the
All cells activated All cells activated
82 Nokia Siemens Networks RN30095EN20GLA0
F-DPCH is allowed for the used service as defined by the
FDPCHAndSRBOnHSPATC parameter
Any services which requires DCH do not exist (AMR on DCH)
HS-DSCH is allocated or is possible to allocate for the UE
E-DCH is allocated or is possible to allocate for the UE
SRB can be mapped to HS-DSCH
SRB can be mapped to E-DCH
Free F-DPCH slot format is available
FDPCHAndSRBOnHSPATC
Define the traffic classes that can use
f-DPCH
Bit 0: Background (1)
Bit 1: Interactive THP=3 (1)
Bit 2: Interactive THP=2 (1)
Bit 3: Interactive THP=1 (1)
Bit 4: PS Streaming (1)
Bit 5: PS Conversational (1)
Bit 6: CS Conversational (0)
Allocating F-DPCH & HSPA SRB (II) RU20
SRB can only be allocated HSUPA with 10 ms TTI if HSDPA is allocated in the downlink
If HSDPA is not allocated in the downlink, SRB can be allocated HSUPA with 2 ms TTI,
i.e. HSUPA/DCH configuration is possible
SRB can only be allocated HSDPA if F-DPCH can be allocated
If the UE is in soft handover, the CPICH Ec/Io of the HSDPA serving cell must be
relatively strong compared to the active set cell with the highest CPICH Ec/Io
The CPICH Ec/Io of the HSDPA serving cell must be at least equal to CPICH Ec/Io The CPICH Ec/Io of the HSDPA serving cell must be at least equal to CPICH Ec/Io
of the active set cell with the highest CPICH Ec/Io of the active set cell with the highest CPICH Ec/Io - - HSDPASRBWindow HSDPASRBWindow
83 Nokia Siemens Networks RN30095EN20GLA0
HSDPASRBWindow
(RNC)
Name
Range Description
0 to 6 dB, step
0.5 dB
Default
1 dB The parameter determines the maximum allowed difference
between the best cell and the SRB on HS-DSCH cell. The
window is relative to the best cell in the active set. If the SRB
on HS-DSCH cell change is outside the window, SRBs on HS-
DSCH cell change procedure is initiated. If the SRBs on HS If the SRBs on HS--
DSCH cell change fails, it triggers SRBs on HS DSCH cell change fails, it triggers SRBs on HS--DSCH DSCH
transport channel type switch to DCH transport channel type switch to DCH. The measured
quantity is CPICH Ec/No, which is received periodically from
the UE.
Window for best active cell Window for best active cell -- HSDPA HSDPA
serving cell. If adjacent cell is (1dB) serving cell. If adjacent cell is (1dB)
stronger, than no F stronger, than no F--DPCH allocated DPCH allocated
Allocating F-DPCH & HSPA SRB (III) RU20
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
Name
Range Description Default
84 Nokia Siemens Networks RN30095EN20GLA0
CPICHRSCPThreSRBHSDPA
(RNC)
-115 to -25,
step 1 dBm
-103
dBm
This parameter defines the coverage area of the
SRBs on HS-DSCH within the HSPA serving cell.
Min. coverage Min. coverage
required for F required for F--DPCH DPCH
Default Ec/Io is Default Ec/Io is --6dB 6dB
required for F required for F--DPCH DPCH
Conclusion: Conclusion:
Traffic and cell Traffic and cell
overlap interference overlap interference
limits F limits F--DPCH most ! DPCH most !
Allocating F-DPCH & HSPA SRB (IV) RU20
The RNC continuously monitors the rules for F-DPCH allocation
Channel type switching from F-DPCH to DPCH is triggered if any of them are not
satisfied while a F-DPCH is allocated
Likewise, channel type switching from DPCH to F-DPCH is triggered if they are all
satisfied while a DPCH is allocated
The minimum interval between two consecutive F-DPCH allocations for a specific UE is
defined by the FDPCHAllocMinInterval parameter
A timer is started for this minimum interval after F minimum interval after F- -DPCH to DPCH switching DPCH to DPCH switching
85 Nokia Siemens Networks RN30095EN20GLA0
The timer is stopped if a RAB establishment procedure is initiated, i.e. F-DPCH
allocation is not restricted during RAB establishment
FDPCHAllocMinInterval
(RNC)
Name
Range Description
0 to 10 s,
step 1 s
Default
3 sec
The parameter determines the minimum interval
between two consecutive Fractional DPCH (F-DPCH)
allocations of the certain UE. Timer is started after every
successfully executed F executed F--DPCH to DPCH DPCH to DPCH
reconfiguration. During the time period, F-DPCH
allocation is forbidden. If the value of the parameter is
set to 0, consecutive F-DPCH allocations are not
restricted. Timer should be stopped when new RAB is
set up, i.e. F-DPCH allocation is not restricted in RAB
setup phase.
interval between two interval between two
consecutive F consecutive F--DPCH DPCH
allocations of UE, allocations of UE, time time
hysteresis F hysteresis F--DPCH off / on DPCH off / on -- UE UE
reports interval reports interval
Mobility RU20
Combined ASU and Serving Cell Change is supported to avoid L3 signaling and /
or SRB - detection errors in downlink
HSPA serving cell
other (non AS cell) HSPA cell gets stronger
86 Nokia Siemens Networks RN30095EN20GLA0
HSPA serving cell
ASU & SCC in one procedure
EcN0 criteria: CPICH_ECNOADD >= CPICH_ECNObest_cell - HSDPASRBWindow
Window for F Window for F--DPCH allocation DPCH allocation
has same value as SCC window has same value as SCC window
Therefore we consider smaller Therefore we consider smaller
SCC window (1dB instead of 2dB SCC window (1dB instead of 2dB
for HSDPA than with A for HSDPA than with A--DCH) DCH)
Active Set Update and SCC (F-DPCH) RU20
Addition
window
CPICH 1
CPICH 2
E
C
/I
0
periodic reports as
HSDPASRBWindow
RNC; 0..6; 0.5; 1 dB
Active set update and serving cell change with fractional DPCH
87 Nokia Siemens Networks RN30095EN20GLA0
time
Just periodic
reports
Serving cell change AND
active set update initiated
periodic reports as
long UE in SHO area
Addition Time
CPICH 2 not CPICH 2 not
active yet active yet
Thank You !
Performance monitoring
HSPA mobility
High Ec/No High Ec/No
or CQI or CQI
HSPA HSPA
Soc Classification level
88 NSN Siemens Networks Presentation / Author / Date
Thank You !
low Ec/No or CQI low Ec/No or CQI
Serving Cell Serving Cell
change change no no
HSPA HSPA
KPI analysis hierarchy
Call/Session setup monitoring & analysis by tools
Release 99: call setup (RRC/RAB)
R99: Call Drop
- Radio link failure rate
- Radio link success rate
R99: Mobility (SHO, HHO, ISHO)
Performance monitoring
Soc Classification level
89 NSN Siemens Networks Presentation / Author / Date
R99: Mobility (SHO, HHO, ISHO)
HSPA setup
HSPA mobility
- Serving Cell Change
RRC states
Appendix
- failure events
issues
Performance layers
Call/Session setup monitoring
& analysis by tools
Performance indicator strategy
Release 99: HSPA
call setup call setup
RRM specific issues: RRM specific issues:
To manage maximum capacity we
consider advanced connection states.
Therefore counters indicates UE
performance at different states e.g.
FACH, Cell_DCH, Cell_PCH, URA.
Soc Classification level
90 NSN Siemens Networks Presentation / Author / Date
Iub
WBTS
RRC states
call setup
call drop
Mobility (HOs)
call setup
call drop
mobility
FACH, Cell_DCH, Cell_PCH, URA.
Common Channel Setup
UE setup via CELL FACH implemented within RU20
NW access of UE via Cell FACH
RACH and FACH transport channels are used for call setup
Call setup on CCH is faster than DCH
All time consuming procedures moves to Cell DCH
Depending on Ec/Io and CCH load/PwR calculation, UE moves to Cell DCH
RRC Idle RRC Idle
Cell_PCH
Performance state upgrade within RU20
Soc Classification level
91 NSN Siemens Networks Presentation / Author / Date
RRC Idle RRC Idle
no UE Location
Information
in UTRAN
only LAI / RAI
in CN
no data transfer
possible
RRC Connection
establishment via
RACH/FACH
signaling
New
Establish
/ Release
RRC
Connection
Cell_PCH
UEs cell known
UE to be paged
(DRX functionality
PICH)
Cell_FACH
common channel
allocated (FACH,
RACH, CPCH, DSCH)
UEs cell known
Cell_DCH
DCH allocated
UEs cell known
URA_PCH
similar to Cell_PCH
no Cell Update,
but URA Update
Connection mode Connection mode
With i With i-- phone phone
Not possible Not possible
Quicker access Quicker access
via RACH/FACH via RACH/FACH
for UE for UE
Common Channel Setup
Allocation of RACH and FACH or DCH is based on establishment
cause received from UE (22 causes)
Available SRB DCH bitrates are 3.4 kbps or 13.6 kbps
Parameter to set appropriate bit-rate per establishment cause
Extra slide
92 Nokia Siemens Networks RN30094EN20GLA0
RACH and FACH load is continuously monitored in RNC
Common channel setup increases load to RACH-FACH channels
Air interface quality (CPICH EcNo) criteria has impact on CCH
allocation
Algorithm checks minimum required EcNo when triggered
Direct Resource Allocation for HSPA
Prior for a NRT service without "wasting time" for CR (RU20)
UE must support HSDPA and HSUPA transport channels
DRA is always used when UE has F-DPCH allocated
HSDPA and HSUPA must be enabled in the cell
Prior to RU20 for NRT user allocation of 0/0 DCH 0/0 DCH by AC
If a Capacity Request (CR) was received, RNC made channel type selection
If no Capacity Request received by RNC, UE was moved to Cell FACH
DRA - performance improvement - RU 20
Soc Classification level
93 NSN Siemens Networks Presentation / Author / Date
RRC Idle RRC Idle
no UE Location
Information
in UTRAN
only LAI / RAI
in CN
no data transfer
possible
RRC Connection
establishment via
RACH/FACH
signaling
New
Establish
/ Release
RRC
Connection
Cell_PCH
UEs cell known
UE to be paged
(DRX functionality
PICH)
Cell_FACH
common channel
allocated (FACH,
RACH, CPCH, DSCH)
UEs cell known
Cell_DCH
DCH allocated
UEs cell known
URA_PCH
similar to Cell_PCH
no Cell Update,
but URA Update
Connection mode Connection mode
DRA DRA
In RU20 HSPA transport channels
can be allocated directly in Cell DCH
or
Cell FACH (Common Channel
Setup), without waiting for without waiting for
capacity request CR capacity request CR
3GPP Release 7 Continuous Packet Connectivity - CPC
Main target is the reduction of UE power consumption
Leads to increased packet connection time and on-line availability
Reduces the power overhead in the cell / system
Introduction
Continuous Packet Connectivity - CPC - RU 20
Soc Classification level
94 NSN Siemens Networks Presentation / Author / Date
Faster data transfer after data inactivity
WCDMA control channel (Rel99, 4, 5, 6) need to be on-air continuously
UL transmission & DL reception
Eating UE battery power therefore less battery lifetime experienced
CPC eliminates the requirement for continuous transmission and reception during
periods when data is not transferred
Exploits discontinuities in packet data services
Designed to work with VoIP
HS-SCCH Less
Operation
Uplink DTX
Downlink
DRX
Reduced CQI
Reporting
New Uplink DPCCH
Slot Format
Uplink
DRX
Continuous Packet Connectivity - new within RU 20
Soc Classification level
95 NSN Siemens Networks Presentation / Author / Date
UE Power Saving
Inactive HSPA UE
require less resource
Increased talk
time
USER GAIN SYSTEM GAIN
Reduced delay for
re-starting data
transfer
Increased
Capacity
Potential to keep
more inactive UE in
CELL_DCH
Uplink DTX
UE
Node B
RNC
RRC Re-Establishment for RT (RRC signaling)
MGW
M1006C186RRC_RE_EST_SUCC_RT : The number of successful RRC
connection re-establishments for UEs with at least one RT RAB. Updated
when the RNC receives RRC: RADIO BEARER RECONFIGURATION
COMPLETE message from the UE after an RRC connection re-
establishment procedure and the UE has got at least one RT RAB
[RACH] RRC:Cell Update (Cause: RL Failure)
[FACH] RRC: Cell Update Confirm
[FACH] RRC: RB Reconfiguration
NBAP: RL Reconfiguration Prepare
ALCAP:ERQ
ALCAP:ECF
M1006C187RRC_RE_EST_FAIL_UE_RT : The number of failed RRC
connection re-establishments due to the UE replying with a new RRC:
CELL UPDATE message, for UEs with at least one RT RAB. Updated
when the RNC receives RRC: CELL UPDATE message from the UE after
an attempted RRC connection re-establishment procedure and the UE has
got at least one RT RAB
[RACH] Utran Mobility Information Confirm
Soc Classification level
96 NSN Siemens Networks Presentation / Author / Date
NBAP: Radio Link Reconfiguration Commit
[DCH] RRC: RB Reconfiguration Complete
[RACH] RRC:Cell Update (Cause: RL Failure)
M1006C188RRC_RE_EST_FAIL_NOREPLY_RT : The number of failed
RRC connection re-establishments due to the UE not replying to an RRC:
CELL UPDATE CONFIRM message sent by the RNC, for UEs with at
least one RT RAB. Updated when the RNC does not receive a reply to
RRC: CELL UPDATE CONFIRM message initiated by the RRC
connection re-establishment procedure and the UE has got at least one
RT RAB.
T314 parameter tells when Cell update message should be coming after RL failure, def 4s
Re-establishment can be done to different cell also
UE
Node B
RNC
Multi RAB Re-Establishment
MGW
[RACH] RRC:Cell Update (Cause: RL Failure)
[FACH] RRC: Cell Update Confirm
[FACH] RRC: RB Reconfiguration
NBAP: RL Reconfiguration Prepare
ALCAP:ERQ
ALCAP:ECF
M1006C190RRC_RE_EST_FAIL_UE_MR : The number of failed RRC
connection re-establishments due to the UE replying with a new RRC:
CELL UPDATE message, for UEs with at least two RABs. Updated when
the RNC receives RRC: CELL UPDATE message from the UE after an
attempted RRC connection re-establishment procedure and the UE has
got at least two RABs
.
[RACH] Utran Mobility Information Confirm
M1006C189RRC_RE_EST_SUCC_MR : The number of successful RRC
connection re-establishments for UEs with at least two RABs. When the
RNC receives RRC: RADIO BEARER RECONFIGURATION COMPLETE
message from the UE after an RRC connection re-establishment
procedure and the UE has got at least two RABs.
Soc Classification level
97 NSN Siemens Networks Presentation / Author / Date
NBAP: Radio Link Reconfiguration Commit
[DCH] RRC: RB Reconfiguration Complete
got at least two RABs
.
[RACH] RRC:Cell Update (Cause: RL Failure)
M1006C191RRC_RE_EST_FAIL_NOREPLY_MR : The number of failed
RRC connection re-establishments due to the UE not replying to an RRC:
CELL UPDATE CONFIRM message sent by the RNC, for UEs with at
least two RABs. Updated when the RNC does not receive a reply to RRC:
CELL UPDATE CONFIRM message initiated by the RRC connection re-
establishment procedure and the UE has got at least two RABs.
RAS06 Packet Session failures
Release due to RL Failure counters:
M1022C57 PS_REL_RL_FAIL_HS_E_INT
M1022C58 PS_REL_RL_FAIL_HS_E_BGR
M1022C59 PS_REL_RL_FAIL_HS_D_INT
M1022C60 PS_REL_RL_FAIL_HS_D_BGR
M1022C61 PS_REL_RL_FAIL_D_D_INT
M1022C62 PS_REL_RL_FAIL_D_D_BGR
are incremented in case RL Failure is received from BTS and cannot be acquired
back during specific time (see Dropped RAB analysis in coming slides for further
info)
Release due to Other Failure counters:
M1022C63 PS_REL_OTH_FAIL_HS_E_INT
Failures are divided into
RL fail
Pre_emption
Other
Soc Classification level
98 NSN Siemens Networks Presentation / Author / Date
Release due to Pre-Emption counters:
M1022C51 PS_REL_PRE_EMP_HS_E_INT
M1022C52 PS_REL_PRE_EMP_HS_E_BGR
M1022C53 PS_REL_PRE_EMP_HS_D_INT
M1022C54 PS_REL_PRE_EMP_HS_D_BGR
M1022C55 PS_REL_PRE_EMP_D_D_INT
M1022C56 PS_REL_PRE_EMP_D_D_BGR
are incremented in case higher priority call pre-empts the existing connection i.e.
RT over NRT
M1022C64 PS_REL_OTH_FAIL_HS_E_BGR
M1022C65 PS_REL_OTH_FAIL_HS_D_INT
M1022C66 PS_REL_OTH_FAIL_HS_D_BGR
M1022C67 PS_REL_OTH_FAIL_D_D_INT
M1022C68 PS_REL_OTH_FAIL_D_D_BGR
are incremented in case the PS allocation is released due to any other reason
expect normal, pre-emption or RL failure
RAN 1601:Complementary Counters in RU10
RAN 1601: Complementary Counters
in RU10,Radio Access Bearer
Services
RAN 1601: Complementary Counters
in RU10,MS Connection Establishment
AAL2 setup time
M1001C632 ServiceLevel SUCC_RRC_SETUP_INTERA
M1001C634 ServiceLevel SUCC_RRC_SETUP_OTHER
M1001C631 ServiceLevel SUCC_RRC_SETUP_STREA
M1001C633 ServiceLevel SUCC_RRC_SETUP_BACKG
M1001C630 ServiceLevel SUCC_RRC_SETUP_CONV
M1001C639 ServiceLevel SRB_ACT_FAIL_OTHER
M1001C636 ServiceLevel SRB_ACT_FAIL_STREA
M1001C638 ServiceLevel SRB_ACT_FAIL_BACKG
M1001C635 ServiceLevel SRB_ACT_FAIL_CONV
M1001C637 ServiceLevel SRB_ACT_FAIL_INTERA
Soc Classification level
99 NSN Siemens Networks Presentation / Author / Date
RRC connection request-setup time
M1006C194 RRC SUM_TIME_AAL2_SETUP
M1006C195 RRC DENOM_TIME_AAL2_SETUP
M1006C182 RRC SUM_RES_ALLO_TIME_RRC_SETUP
M1006C183 RRC DENOM_RES_ALLO_TM_RRC_SETUP
Thank You !
Performance monitoring
RRC states
Soc Classification level
100 NSN Siemens Networks Presentation / Author / Date
Thank You !
finally finished finally finished
KPI analysis hierarchy
Call/Session setup monitoring & analysis by tools
Release 99: call setup (RRC/RAB)
R99: Call Drop
- Radio link failure rate
- Radio link success rate
R99: Mobility (SHO, HHO, ISHO)
Performance monitoring
Soc Classification level
101 NSN Siemens Networks Presentation / Author / Date
R99: Mobility (SHO, HHO, ISHO)
HSPA setup
HSPA mobility
- Serving Cell Change
RRC states
Appendix
RRC or RAB setup failures could be due issues related to
Coverage or interference
Inter RNC problem
Capacity
Capacity issues could results to the RRC/RAB setup failures related to
BTS for Channel Element (WSP & FSM) capacity issues, TRANS for Iub
call setup failures
Starting criteria for setup failure analysis
Soc Classification level
102 NSN Siemens Networks Presentation / Author / Date
BTS for Channel Element (WSP & FSM) capacity issues, TRANS for Iub
capacity issues or AC for radio capacity issues (UL Load, DL Load and DL
spreading codes)
Some type of RRC/RAB failures should NOT be present
RRC_CONN_ACT_FAIL_RNC
RAB_ACT_FAIL_xxx_RNC
SRNC relocation issues will also cause RRC/RAB failures
See more info in RRC access failure scenario (at the end of this module)
RF optimization (+drive testing) may be needed also
RRC_CONN_STP_FAIL_AC RRC_CONN_STP_FAIL_AC
Check UL Interference, DL Power & Code occupancy if there is need to upgrade radio capacity
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 Problem
RRC_CONN_STP_FAIL_BTS RRC_CONN_STP_FAIL_BTS
Evaluate NBAP counters (radio link reconf. Failures) and KPIs for troubleshooting BTS resources
M1002C2 CH_REQ_LINK_REJ_DL_SRNC ----->Evaluate Ptx Resource Problem
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
RRC Connection & Access Fail - Analysis
Soc Classification level
103 NSN Siemens Networks Presentation / Author / Date
In case BTS is not responding delete and re-create COCO
RRC_CONN_STP_FAIL_TRANS 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
RRC_CONN_STP_FAIL_RNC 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
RRC_CONN_STP_FAIL_RNTI ALLO FAIL RRC_CONN_STP_FAIL_RNTI ALLO FAIL
RNC decides to reject RRC connection request due to RNTI allocation failure caused by RRMU
overload
RRC_CONN_STP_FAIL_IUB_AAL2_TRANS RRC_CONN_STP_FAIL_IUB_AAL2_TRANS
Updated when there is shortage or blocking of AAL2 resource
A subset of RRC_CONN_FAIL_TRANS which include ERQ/ECF fail due to some reason such as
DMPG problem in RNC + ERQ/ECF fail due to transport resource needed in RNC between RNC/MGW
RRC_CONN_ACC_FAIL_RADIO RRC_CONN_ACC_FAIL_RADIO
Dominant failure causes
Perform drive test to detect if UL or DL coverage
RRC Connection & Access Fail - Analysis
Soc Classification level
104 NSN Siemens Networks Presentation / Author / Date
Perform drive test to detect if UL or DL coverage
UL 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)
RRC_CONN_ACC_FAIL_MS 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)
Check the problem cells and its neighbouring cells of any faulty alarms
Identify root cause failure distribution and main failure
RAB_STP_FAIL_XXX_AC 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
call setup - RAB
RAB setup failures - Root Cause Analysis
Soc Classification level
105 NSN Siemens Networks Presentation / Author / Date
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 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 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 RAB_ACC_FAIL_XXX_MS
Evaluate Cell resource Prx and Ptx (for example high uplink interference)
call setup - RAB
RAB setup failures - Root Cause Analysis
Soc Classification level
106 NSN Siemens Networks Presentation / Author / Date
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 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
Note: RNC does not reserve radio interface
resources in RAB setup phase for NRT
RAB_ACC_FAIL_XXX_MS 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 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
call setup - RAB
RAB setup failures - Root Cause Analysis
Soc Classification level
107 NSN Siemens Networks Presentation / Author / Date
RAS06 Packet Calls
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
Soc Classification level
108 NSN Siemens Networks Presentation / Author / Date
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
PS RAB Upgrade or HSDPA/HSUPA Activation
If RNC receives RRC: Measurement Report indicating event 4a
when UE has been allocated DCH0/0 or in cell_PCH state
RNC receives Cell Update indicating need for dedicated
channel (i.e. cause UPLINK DATA TRANSMISSION), following
counter is incremented:
M1022C0 PS_SESSION_REQ_UL
If the network wants to initiate any downlink activity and the UE
is in Cell_PCH state, it needs to make a paging request.
Counter M1022C1 PS_SESSION_REQ_DL is incremented
when RNC receives RRC: CELL UPDATE message with the
cause PAGING RESPONSE
In case of inter RNC HHO or SRNC relocation counter
M1022C2 PS_SESSION_REQ_OTHER is incremented when
RANAP: RELOCATION REQUEST message request is
RANAP: RAB Assignment Request
UE Node B
RNC
AC to check to accept
or reject RAB
Assignment Request
SGSN
[DCH] RRC: Radio Bearer Setup
[DCH] RRC: Radio Bearer Setup Complete
RANAP: RAB Assignment Response:
Success
[DCH] RRC: Measurement Control
[DCH] RRC: Measurement Control
Soc Classification level
109 NSN Siemens Networks Presentation / Author / Date
NOTE: These counters are NOT incremented when resources
(DMPG) are re-allocated due to: Direct switching from DCH
xx/yy to HS-DSCH/E-DCH or HS-DSCH/DCH
RANAP: RELOCATION REQUEST message request is
received
Note: PS ISHO do not use relocation signaling as it is a normal
PS call setup where the resources are reserved by UL/DL
capacity request
Direct Transfer : Activate PDP Context Accept
[DCH] RRC: Measurement Report
[DCH] RRC: Measurement Control
NBAP: RL Reconfiguration Prepare
NBAP: RL Reconfiguration Failure
AC to check to accept
or reject Capacity
request
RAS06 Packet Call failures
Initial Setup fail procedure
AC failure : lack of DL power or high interference
BTS failure: lack of HW capacity
DMCU failure: lack of DSP resources in RNC
TRANS failure: lack of Iub capacity (COCO parameters)
UE failure: UE internal problem (not capability issue)
Separate Packet SSSR for R99 NRT, HSDPA and HSUPA to see the main failure
type
Reguests vs. allocations
Soc Classification level
110 NSN Siemens Networks Presentation / Author / Date
Reguests vs. allocations
It is possible to see whether HSPA was not allocated DL/UL, but DCH instead
(capacity issue)
Separate PS release fail for R99 NRT, HSDPA and HSUPA to see the main failure
source
RANAP: RAB Assignment Request
UE Node B
RNC
AC to check to accept or
reject RAB Assignment
Request
SGSN
[DCH] RRC: Radio Bearer Setup
[DCH] RRC: Radio Bearer Setup Complete
RANAP: RAB Assignment Response:
Success
PS Call Counter failure - AC
Resource reservation happens during PS
user plane allocation.
If user plane allocation is rejected by the
admission control. RAS06 new PS call
counters
M1022C9 Packet Call Setup Fail due to
AC for Interactive
M1022C10 Packet Call Setup Fail due to
AC for Background
are updated
Soc Classification level
111 NSN Siemens Networks Presentation / Author / Date
[DCH] RRC: Measurement Control
Direct Transfer : Activate PDP Context Accept
[DCH] RRC: Measurement Report
[DCH] RRC: Measurement Control
AC to check to accept or
reject Capacity request
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.
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
are updated
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)
3. Check SHO KPI if performance < 90% ( leads to radio failure)
Soc Classification level
112 NSN Siemens Networks Presentation / Author / Date
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)
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
Call Drop analysis
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)
Soc Classification level
113 NSN Siemens Networks Presentation / Author / Date
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)
RAS06 PS setup fail comparison with RAS5.1 PS RAB
setup, RNC level
0.040
0.050
0.060
RNC_376a RAB setup failures for PS caused by
the AC
RNC_378a RAB setup failures for PS caused by
transmission
RNC_379a RAB setup failures for PS caused by
RNC's internal reasons
RNC_380a RAB setup failures for PS caused by
anchoring RNC reject.
RNC_381a RAB setup failures for PS due to a
frozen BTS
Soc Classification level
114 NSN Siemens Networks Presentation / Author / Date
0.000
0.010
0.020
0.030
0
8
.
0
3
.
2
0
0
8
1
5
.
0
3
.
2
0
0
8
2
2
.
0
3
.
2
0
0
8
2
9
.
0
3
.
2
0
0
8
0
5
.
0
4
.
2
0
0
8
1
2
.
0
4
.
2
0
0
8
1
9
.
0
4
.
2
0
0
8
2
6
.
0
4
.
2
0
0
8
0
3
.
0
5
.
2
0
0
8
PS_SETUP_FAIL_AC_p
PS_SETUP_FAIL_AC_p
PS_SETUP_FAIL_BTS_p
PS_SETUP_FAIL_BTS_p
PS_SETUP_FAIL_DMCU_p
PS_SETUP_FAIL_DMCU_p
PS_SETUP_FAIL_TRANS_p
PS_SETUP_FAIL_TRANS_p
PS_SETUP_FAIL_UE_p
PS_SETUP_FAIL_UE_p
PS_SETUP_FAIL_OTHER_p
PS_SETUP_FAIL_OTHER_p
RAS06 PS setup fail comparison with RAS5.1- HSDPA
setup, RNC level
0.100
0.120
0.140
0.160
0.180
RNC_661a HSDPA Access failures due to UL
DCH
RNC_663a HSDPA Access failures due to RNC
RNC_665a HSDPA Access failures due to Iub
RNC_667a HSDPA Access failures due to UE
RNC_669a HSDPA Access failures due to too
many HSDPA users
RNC_671a HSDPA Access failures due to Multi-
RAB
RNC_673a HSDPA Access failures due to BTS
Soc Classification level
115 NSN Siemens Networks Presentation / Author / Date
0.000
0.020
0.040
0.060
0.080
0
8
.
0
3
.
2
0
0
8
1
5
.
0
3
.
2
0
0
8
2
2
.
0
3
.
2
0
0
8
2
9
.
0
3
.
2
0
0
8
0
5
.
0
4
.
2
0
0
8
1
2
.
0
4
.
2
0
0
8
1
9
.
0
4
.
2
0
0
8
2
6
.
0
4
.
2
0
0
8
0
3
.
0
5
.
2
0
0
8
RNC_673a HSDPA Access failures due to BTS
PS_SETUP_FAIL_AC_p
PS_SETUP_FAIL_AC_p
PS_SETUP_FAIL_BTS_p
PS_SETUP_FAIL_BTS_p
PS_SETUP_FAIL_DMCU_p
PS_SETUP_FAIL_DMCU_p
PS_SETUP_FAIL_TRANS_p
PS_SETUP_FAIL_TRANS_p
PS_SETUP_FAIL_UE_p
PS_SETUP_FAIL_UE_p
PS_SETUP_FAIL_OTHER_p
PS_SETUP_FAIL_OTHER_p
R
L
_
S
E
T
U
P
_
A
T
T
_
F
O
R
_
S
H
O
_
O
N
_
S
R
N
C
R
L
_
B
R
A
N
C
H
_
A
D
D
_
S
U
C
C
_
S
H
O
_
S
R
N
C
D
E
L
_
S
H
O
_
S
R
N
C
_
A
C
T
_
R
L
_
S
Y
N
_
F
A
I
L
Radio Link Failure
The counter DEL_SHO_SRNC_ACT_RL_SYNC_ FAIL measure the number of
Radio link deletions on SRNC side due to an active radio link synchronisation
failure.
Counter is updated when a BTS loses synchronisation on an active RL and is not
able to re-establish synchronisation during the allowed time.
Soc Classification level
116 NSN Siemens Networks Presentation / Author / Date
R
N
C
_
I
D
C
E
L
L
_
I
D
R
N
C
-
C
I
T
T
A
D
A
Y
R
L
_
S
E
T
U
P
_
A
T
T
_
F
O
R
_
F
I
R
S
T
_
R
L
R
L
_
S
E
T
U
P
_
A
T
T
_
F
O
R
_
S
H
O
_
O
N
_
S
R
N
C
R
L
_
B
R
A
N
C
H
_
A
D
D
_
S
U
C
C
_
S
H
O
_
S
R
N
C
D
E
L
_
S
H
O
_
S
R
N
C
_
A
C
T
_
R
L
_
S
Y
N
_
F
A
I
L
U
L
_
L
O
S
T
_
A
C
T
I
V
E
NE-RNC-2 62272 MILANO1 20050117 770 401 206 295 21.4%
NE-RNC-2 62272 MILANO1 20050118 606 363 241 267 22.1%
NE-RNC-2 62272 MILANO1 20050119 669 493 161 308 23.3%
NE-RNC-2 62272 MILANO1 20050120 777 460 166 357 25.4%
NE-RNC-2 62272 MILANO1 20050121 1215 672 265 464 21.6%
R
N
C
_
I
D
R
N
C
-
C
I
T
T
A
D
A
Y
U
L
_
L
O
S
T
_
A
C
T
I
V
E
NE-RNC-2 MILANO1 20050117 10.0%
NE-RNC-2 MILANO1 20050118 10.3%
NE-RNC-2 MILANO1 20050119 10.1%
NE-RNC-2 MILANO1 20050120 9.8%
RNC2
average:
10%
RAB Active Phase Failures
Cells having high RAB drop ratio due the Radio or UE can be identified by service
level counters
Formula below count CS voice RAB drop ratio due the radio from network
perspective.
[ ] %
_ _ _ _
_ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _ _ _
_ _ _ _ _
* 100
_

+
+ +
+ +
failures all
VOICE CS FAIL ACT RAB
CELL REF OUT VOICE CS RAB CELL REF IN VOICE CS RAB
CN ER UNSPE V CS REL ACTIVE RAB SRNC VOICE CS REL ACT RAB
EMP P VOICE CS REL ACT RAB VOICE CS COMP ACT RAB
RADIO VOICE CS FAIL ACT RAB
RAB Drop ratio can
per RAB type or RAB
drop rate containing
all RABs
Soc Classification level
117 NSN Siemens Networks Presentation / Author / Date
The counters RAB_Active_Fail_XXX_Radio/UE can be used to measure air interface
. Following failures are related to counters
_ failures all
Active_Fail_UE timer_expired_c radio_conn_lost_c ms_c
Active_Fail_UE timer_expired_c physical_ch_reconf_fail_c ms_c
Active_Fail_Radio default_c no_resp_from_rlc_c radio_interface_c
Active_Fail_Radio radio_conn_lost_c radio_link_failure_c radio_interface_c
Counter Service Level OUT DETAILED REASON OUT REASON OUT FAIL SOURCE
Active_Fail_UE timer_expired_c radio_conn_lost_c ms_c
Active_Fail_UE timer_expired_c physical_ch_reconf_fail_c ms_c
Active_Fail_Radio default_c no_resp_from_rlc_c radio_interface_c
Active_Fail_Radio radio_conn_lost_c radio_link_failure_c radio_interface_c
Counter Service Level OUT DETAILED REASON OUT REASON OUT FAIL SOURCE
Radio Connection Lost- RAB Reconfiguration fail
RAB Reconfiguration Success Rate KPI is ~2% lower than at RNC level
cell has other kind of radio failures
Drop voice is 3%
[ ] %
RB_RECONF
COMPLETE RB_RECONF_
* 100
R
B
_
R
E
C
O
N
F
_
C
O
M
P
L
E
T
E
R
B
_
R
E
C
O
N
F
_
S
U
C
C
E
S
S
_
R
A
T
E
R
B
_
R
E
C
O
N
F
_
C
O
M
P
L
E
T
E
R
B
_
R
E
C
O
N
F
_
S
U
C
C
E
S
S
_
R
A
T
E
CELL level
RNC level
Soc Classification level
118 NSN Siemens Networks Presentation / Author / Date
C
E
L
L
D
A
Y
R
B
_
R
E
C
O
N
F
R
B
_
R
E
C
O
N
F
_
C
O
M
P
L
E
T
E
R
B
_
R
E
C
O
N
F
_
S
U
C
C
E
S
S
_
R
A
T
E
62542 20050117 284 283 99.6%
62542 20050118 1619 1570 97.0%
62542 20050119 2169 2102 96.9%
62542 20050120 1857 1787 96.2%
62542 20050121 1168 1132 96.9%
R
N
C
-
C
I
T
T
A
D
A
Y
R
B
_
R
E
C
O
N
F
R
B
_
R
E
C
O
N
F
_
C
O
M
P
L
E
T
E
R
B
_
R
E
C
O
N
F
_
S
U
C
C
E
S
S
_
R
A
T
E
MILANO1 20050117 128890 127617 99.0%
MILANO1 20050118 138597 137227 99.0%
MILANO1 20050119 142997 141604 99.0%
MILANO1 20050120 136753 135481 99.1%
MILANO1 20050121 118625 117340 98.9%
R99: Mobility - RRC Drop during ISHO RT
When the source RCC Connection drops (and the RNC sends the RANAP : Iu
Release Request to the CN) during the ISHO, one of the following counter is
triggered:
RNC UE
RRC: Measurement Report (3,4,5)
RRC: Measurement Control
BTS
AC check for CM
NBAP: Radio Link Reconfiguration Prepare
NBAP: Radio Link Reconfiguration Ready
CN
M1010C21 CON_DRPS_IS_HHO_UL_DCH_Q_RT
M1010C25 CON_DRPS_IS_HHO_UE_PWR_RT
M1010C29 CON_DRPS _IS _HHO_DL_DPCH_RT
M1010C33 CON_DRPS _IS _HHO_RSCP_RT
Soc Classification level
119 NSN Siemens Networks Presentation / Author / Date
NBAP: Radio Link Reconfiguration Ready
NBAP: Radio Link Reconfiguration Commit
RRC: Physical Channel Reconfiguration
RRC: Physical Channel Reconfiguration Complete
NBAP: Compressed Mode Command
RRC: Measurement Control
RRC: Measurement Report
NBAP: Compressed Mode Command
RRC: Measurement Control
RRC: Measurement Report
BSIC verification phase for target cell
RX Level measurement phase for
all ISHO neighbours
RANAP: Relocation Required
RRC: Handover from UTRAN Command
RANAP: Relocation Command
RANAP: IU Release Request
M1010C33 CON_DRPS _IS _HHO_RSCP_RT
M1010C37 CON_DRPS _IS _HHO_ECNO_RT
M1010Cxxx
CON_DRPS_IS_HHO_LSHO_triggers_RT*
If neither the target BSC has received the HO complete
message nor the source RNC has received a failure from the
mobile, the source RNC sends the IU RELEASE REQUEST
message to the CN.
For RT: TRelocOverall (def. 8s, from Relocation
Command to Iu Release Command) expires.
R99: Mobility RRC Drop - SHO NRT
RNC UE
RRC: Measurement Report (3,4,5)
RRC: Measurement Control
BTS
AC check for CM
NBAP: Radio Link Reconfiguration Prepare
NBAP: Radio Link Reconfiguration Ready
NBAP: Radio Link Reconfiguration Commit
CN
When the source RCC Connection drops (and the RNC sends the RANAP : Iu Release
Request to the CN) during the ISHO, one of the following counter is triggered:
M1010C21 CON_DRPS_IS_HHO_UL_DCH_Q_NRT
M1010C25 CON_DRPS_IS_HHO_UE_PWR_NRT
M1010C29 CON_DRPS _IS _HHO_DL_DPCH_NRT
M1010C33 CON_DRPS _IS _HHO_RSCP_NRT
Iu Radio Link Failure
Soc Classification level
120 NSN Siemens Networks Presentation / Author / Date
NBAP: Radio Link Reconfiguration Commit
RRC: Physical Channel Reconfiguration
RRC: Physical Channel Reconfiguration Complete
NBAP: Compressed Mode Command
RRC: Measurement Control
RRC: Measurement Report
NBAP: Compressed Mode Command
RRC: Measurement Control
RRC: Measurement Report
BSIC verification phase for target cell
RX Level measurement phase for
all ISHO neighbours
RRC: Cell Change Order from UTRAN
RANAP: SRNS Context Request
RANAP: IU Release Request
RANAP: SRNS Data Forward Command
RANAP: SRNS Context Response
M1010C33 CON_DRPS _IS _HHO_RSCP_NRT
M1010C37 CON_DRPS _IS _HHO_ECNO_NRT
M1010Cxxx
CON_DRPS_IS_HHO_LSHO_triggers_NRT*
If neither the target BSC has received the HO complete
message nor the source RNC has received a failure from the
mobile, the source RNC sends the IU RELEASE REQUEST
message to the CN.
For NRT: IU release request is sent after 8s from
sending Cell Change Order.
R99: Mobility ISHO Analysis
4. If Low ISHO Measurement Success Rate
Check ADJG neighbour list for missing neighbours
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) to indicate low coverage /
interference problem
5. If Low ISHO Success Rate (RT <95% & NRT < 80%)
Check missing or wrong 2G parameter in MSC/SGSN (LAC, CellId, BCCH)
Soc Classification level
121 NSN Siemens Networks Presentation / Author / Date
Check missing or wrong 2G parameter in MSC/SGSN (LAC, CellId, BCCH)
Check discrepancy of Cell information in RNC
Check 2G cell GPRS/EGPRS data congestion
6. May require further troubleshooting with ICSU logging to determine root cause of failure
Handover -> Report RSRAN018
Handover -> Report RSRAN019
Handover-> Report RSRAN023
HSDPA Retainability Failure Cause Analysis
HSDPA Retainability for NRT Traffic
Top N cells
HS_DSCH_
PRE_EMP
RNC_609a < X %
HS_DSCH_
MOB_DCH
HS_DSCH_
OTH_DCH
RL_FAIL_
HS_DSCH
No action
needed
No
Yes
Yes
Yes
Yes
Yes
No No
No
OTH_FAIL_
HS_DSCH
No
Yes
Soc Classification level
122 NSN Siemens Networks Presentation / Author / Date
Normal Release
(No action
needed)
Normal Release
(No action
needed)
Normal Release
(No action
needed)
Check SCC
Failure Rate
Radio, Iub, CE
resource
congestion
Yes
Check CQI
distribution and
Ecno distribution
for coverage
issue
Check HSDPA mobility
parameter Add/Drop
window, SCC parameter
No
No
Check RB
reconfiguration failure
rate UE responsed with
failure or no response at
all
Yes
HSDPA Retainability analysis
1. Identify root cause failure distribution and main contributor of low retainability
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
Soc Classification level
123 NSN Siemens Networks Presentation / Author / Date
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 (RAN_KPI_0048) - high SCC failures lead to radio link failure
Check CQI distribution (M5000C8-M5000C39) or Ecno distribution for bad coverage issue (M1007C38-
M1007C47)
Check HSDPA FMCS Mobility Control Parameter (handover or SCC too late)
Check call re-establishment T315 timer due to radio link failure
HSDPA Retainability analysis
3. If high HSDPA Non- Radio Link Failures (NRT)
UE responding with some failure message or not responding to some message but no RL failure (timer
expiry)
Check RB reconfiguration, physical channel reconfiguration, NBAP RL reconfiguration failure rate
Required ICSU log for further troubleshooting ?
Soc Classification level
124 NSN Siemens Networks Presentation / Author / Date
Complementaty counters: RRC Setup Time
[RACH] RRC:RRC Connection
Request
UE
Node B
RNC
ALCAP:ERQ
NBAP: RL Setup Request
Start
TX/RX
NBAP: RL Setup
Response
AC to check to accept
or reject RRC
Connection Request
ALCAP:ECF
M1001C630SUCC_RRC_SETUP_CONV 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 either Originating Conversational Call or Terminating Conversational Call.
M1006C182SUM_RES_ALLO_TIME_RRC_SETUP : Sum of HW, Transmission
and Radio resource allocation time in the RRC Connection Establishment
procedure, defined as the time between
RRC: RRC CONNECTION REQUEST received by RNC and
RRC:RRC CONNECTION SETUP sent to UE.
This counter, divided by the denominator, provides the average resource allocation
time. Updated when the RNC sends RRC: RRC CONNECTION SETUP to the UE
M1006C183DENOM_RES_ALLO_TM_RRC_SETUP : Denominator for
M1006C182, used for average calculation. Updated by value 1, then the measured
time is updated to counter M1006C182.
Soc Classification level
125 NSN Siemens Networks Presentation / Author / Date
[DCH] RRC: RRC Connection Setup Complete
L1 Synchronisation
Start TX/RX
[FACH] RRC: RRC Connection Setup
ALCAP:ECF
NBAP: Synchronisation Indication
RAB Setup & Access
been either Originating Conversational Call or Terminating Conversational Call.
M1001C631SUCC_RRC_SETUP_STREA 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 either Originating Streaming Call or Terminating Streaming Call
M1001C632SUCC_RRC_SETUP_INTERA 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 either Originating Interactive Call or Terminating Interactive Call.
M1001C633SUCC_RRC_SETUP_BACKG 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 either Originating Background Call or Terminating Background 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.
Complementaty counters: SRB Active fail
[RACH] RRC:RRC Connection
Request
UE
Node B
RNC
ALCAP:ERQ
NBAP: RL Setup Request
Start
TX/RX
NBAP: RL Setup Response
AC to check to accept
or reject RRC
Connection Request
ALCAP:ECF
M1001C635SRB_ACT_FAIL_CONV 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 counter is
updated when the establishment cause in RRC: RRC CONNECTION REQUEST is either Originating
Conversational Call or Terminating Conversational Call.
M1001C636SRB_ACT_FAIL_STREA 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
counter is updated when the establishment cause in RRC: RRC CONNECTION REQUEST is either
Originating Streaming Call or Terminating Streaming Call.
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
counter is updated when the establishment cause in RRC: RRC CONNECTION REQUEST is either
Originating Interactive Call or Terminating Interactive Call.
M1001C638SRB_ACT_FAIL_BACKG 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
Soc Classification level
126 NSN Siemens Networks Presentation / Author / Date
[DCH] RRC: RRC Connection Setup Complete
L1 Synchronisation
Start TX/RX
[FACH] RRC: RRC Connection Setup
ALCAP:ECF
NBAP: Synchronisation Indication
RAB Setup & Access
[DCH] RRC: RRC Connection Release
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
Originating Background Call or Terminating Background Call
M1001C639SRB_ACT_FAIL_OTHER 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
counter is updated when the establishment cause in RRC: RRC CONNECTION REQUEST is some
other cause not covered by counters M1001C635-M1001C638.
RANAP: RAB Assignment Request
UE
Node B
RNC
NBAP: RL Reconfiguration Prepare
AC to check to accept
or reject RAB
Assignment Request
RAB Establishment- AAL2 setup time
ALCAP:ERQ
NBAP: RL Reconfiguration Ready
ALCAP:ECF
MGW
M1006C194SUM_TIME_AAL2_SETUP : Sum of Iub
AAL2 Setup time, defined as the difference between
ALCAP: Establishment Request (ERQ) and
ALCAP: Establishment Confirm (ECF). This counter,
divided by the denominator, provides the average
AAL2 setup time.
M1006C195DENOM_TIME_AAL2_SETUP :
Denominator for M1006C194, used for average
calculation. Updated by value 1, then the measured
Soc Classification level
127 NSN Siemens Networks Presentation / Author / Date
ALCAP:ECF
NBAP: Radio Link Reconfiguration Commit
calculation. Updated by value 1, then the measured
time is updated to counter M1006C194.
RAN 1232: Fast Call Setup from Cell_PCH State
Packet data state transition
Sum of state transition times from
Cell-FACH state to Cell-DCH/Cell-FACH
state
Cell-PCH state to Cell-FACH/Cel_DCH
Cell-DCH state to Cell-FACH/Cell-PCH
Unit ms
Resource allocation time: cell_fach
M1006C170 RRC SUM_ST_TRANS_TIME_PCH_FACH
M1006C171 RRC DENOM_ST_TRANS_TIME_PCH_FACH
M1006C172 RRC SUM_ST_TRANS_TIME_FACH_DCH
M1006C173 RRC DENOM_ST_TRANS_TIME_FACH_DCH
M1006C174 RRC SUM_ST_TRANS_TIME_PCH_DCH
M1006C175 RRC DENOM_ST_TRANS_TIME_PCH_DCH
M1006C176 RRC SUM_ST_TRANS_TIME_DCH_FACH
M1006C177 RRC DENOM_ST_TRANS_TIME_DCH_FACH
M1006C178 RRC SUM_ST_TRANS_TIME_DCH_PCH
M1006C179 RRC DENOM_ST_TRANS_TIME_DCH_PCH
M1006C180 RRC SUM_ST_TRANS_TIME_FACH_PCH
M1006C181 RRC DENOM_ST_TRANS_TIME_FACH_PCH
Soc Classification level
128 NSN Siemens Networks Presentation / Author / Date
M1006C184 RRC SUM_RES_ALLO_TIME_FACH
M1006C185 RRC DENOM_RES_ALLO_TM_FACH
[FACH] RRC: Cell Update (paging response or
UL data transmission )
UE
Node B
RNC
[FACH] RRC: Cell Update Confirm
[RACH] UTRAN Mobility Information Confirm
[FACH] RRC: Radio Bearer Reconfiguration
NBAP: Radio Link Setup
NBAP: Radio Link Setup Response
ALCAP: ERQ
ALCAP: ECF
[DCH] RRC: Measurement Control
[DCH] RRC: Radio Bearer Reconfiguration Complete
RRC State Changes from Cell_PCH/URA_PCH to
Cell_FACH/Cell_DCH & Time
M1006C174SUM_ST_TRANS_TIME_PCH_DCH: Sum of state transition times from
Cell-PCH or URA-PCH state to Cell-DCH state, defined as the time between:
RRC: Cell Update (cause: UL Data Transmission or Paging response) - RRC: Radio
Bearer Reconfiguration Complete.
This counter, divided by the denominator, provides the average state transition time.
M1006C199CELL_UPDATE_ATT_DATA_TR_TVM : The number of Cell Update
messages received with cause "uplink data transmission" and "traffic volume indicator"
IE set as true.
Also M1006C36 is updated along with this counter. Updated when the RNC receives
RRC: CELL UPDATE message with cause "uplink data transmission" and "traffic
volume indicator" set as true.
Soc Classification level
129 NSN Siemens Networks Presentation / Author / Date
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.
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.
This counter, divided by the denominator, provides the average state transition time.
M1006C175DENOM_ST_TRANS_TIME_PCH_DCH: Updated by value 1, then the
measured time is updated to counter M1006C174
RRC State Changes from Cell_DCH to Cell_FACH &
Time
[DCH] RRC: Radio Bearer Reconfiguration
UE
Node B
RNC
ALCAP:Rel Req
NBAP: RL Deletion Request
NBAP: RL Deletion Response
ALCAP:Rel Conf
[RACH] RRC: Cell Update (Cell Reselection)
[FACH] RRC: Cell Update Confirm
[RACH] UTRAN Mobility Information Confirm
[RACH] RRC: Radio Bearer Reconfiguration Complete
[FACH] RRC: Measurement Control
M1006C154SUCC_HS_DSCH_TO_FACH : number of successful
state transitions from HS-DSCH to DCH. Updated when the RNC
receives RRC: RADIO BEARER RECONFIGURATION COMPLETE
message from the UE after a successful channel switch from HS-
DSCH to FACH
Soc Classification level
130 NSN Siemens Networks Presentation / Author / Date
ALCAP:Rel Conf
M1006C176SUM_ST_TRANS_TIME_DCH_FACH: Sum of state transition times from Cell-DCH state to Cell-FACH
state, defined as the time between: When RNC decides to initiate Cell_DCH to Cell_FACH transition -
RRC: Radio Bearer Reconfiguration Complete or Radio Bearer Release Complete.
This counter, divided by the denominator, provides the average state transition time.
M1006C177DENOM_ST_TRANS_TIME_DCH_FACH: Denominator for M1006C176 used for average calculation
RRC State Change time from Cell_DCH to Cell_PCH
[DCH] RRC: Radio Bearer Reconfiguration
UE
Node B
RNC
[RACH] RRC: Radio Bearer Reconfiguration
Complete
M1006C178SUM_ST_TRANS_TIME_DCH_PCH:Sum of state transition times from Cell-DCH state to Cell-PCH or
URA-PCH state, defined as the time between: When RNC decides to initiate Cell_DCH to Cell_PCH transition -
Soc Classification level
131 NSN Siemens Networks Presentation / Author / Date
URA-PCH state, defined as the time between: When RNC decides to initiate Cell_DCH to Cell_PCH transition -
RRC: Radio Bearer Reconfiguration Complete or Radio Bearer Release Complete.
This counter, divided by the denominator, provides the average state transition time.
M1006C179DENOM_ST_TRANS_TIME_DCH_PCH: Denominator for M1006C178 used for average calculation
RRC State Change time from Cell_FACH to Cell_PCH
[FACH] RRC: Physical Channel Reconfiguration
UE
Node B
RNC
[RACH] RRC: Cell Update (Cell Reselection)
[FACH] RRC: Cell Update Confirm
[RACH] UTRAN Mobility Information Confirm
[RACH] RRC: Physical Channel Reconfiguration
Complete
Soc Classification level
132 NSN Siemens Networks Presentation / Author / Date
M1006C180SUM_ST_TRANS_TIME_FACH_PCH Sum of state transition times from Cell-FACH state to Cell-PCH
or URA-PCH state, defined as the time between: When RNC decides to initiate Cell_FACH to Cell_PCH transition -
RRC: Physical Channel Reconfiguration Complete.
This counter, divided by the denominator, provides the average state transition time
M1006C181DENOM_ST_TRANS_TIME_FACH_PCH: Denominator for M1006C180 used for average calculation
Resource allocation time from Cell_FACH to Cell_DCH
UE
Node B
RNC
M1006C184SUM_RES_ALLO_TIME_FACH : Sum of HW and Radio
resource allocation time between UL/DL capacity request or RT-RAB
Assignment Request received and
NBAP: RADIO LINK SETUP sent to NodeB.
This counter, divided by the denominator, provides the average
resource allocation time.
Updated : when the RNC sends NBAP: RADIO LINK SETUP to the
NodeB
M1006C185DENOM_RES_ALLO_TM_FACH : Denominator for
M1006C184, used for average calculation. Updated by value 1, then
the measured time is updated to counter M1006C184
[RACH] RRC: Measurement Report (e4a)
NBAP: Radio Link Setup
Soc Classification level
133 NSN Siemens Networks Presentation / Author / Date
Hard Handover Counters(Inter RNC, GAN)
The number of RRC active releases
due to intra-frequency inter-RNC hard
handover
The number of RRC active releases
due to inter-frequency inter-RNC hard
handover/ISHO to GSM
The number of RRC active releases
due to inter-system handover to Generic
Access Network (GAN).
M1001C642 ServiceLevel RRC_CONN_ACT_REL_INTRA_HHO
M1001C643 ServiceLevel RRC_CONN_ACT_REL_GANHO
M1001C800 ServiceLevel RRC_CONN_ACT_REL_HHO
M1001C803 ServiceLevel RRC_CONN_ACT_REL_ISHO
Soc Classification level
134 NSN Siemens Networks Presentation / Author / Date
RRC active releases due to HHO
UE
RNC
RAB Assignment Request (setup)
CORE
RRC: Handover from UTRAN Command
RANAP: Relocation Required
RANAP: Relocation Command
RANAP: IU Release Command
RANAP: IU Release Complete
M1001C642 RRC_CONN_ACT_REL_INTRA_HHO:
The number of RRC active releases due to intra-
frequency inter-RNC hard handover. Updated when the
RNC receives RANAP: IU RELEASE COMMAND with
cause "successful relocation" from the CN.
M1001C643 RRC_CONN_ACT_REL_GANHO: The
number of RRC active releases due to inter-system
handover to Generic Access Network (GAN). Updated
when the RNC receives RANAP: IU RELEASE
COMMAND with cause "successful relocation" from the
CN.
Soc Classification level
135 NSN Siemens Networks Presentation / Author / Date
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.
RRC Connection release due to Inactivity/RNC
HW resource
M1001C628RRC_CONN_REL_DUE_INACTIVITY: The number of
RRC connection releases due to user inactivity in Cell-PCH or URA-
PCH state. When the RNC releases the RRC/Iu-PS connection based
on the MSActivitySupervision timer using release cause 'User Inactivity'
Also counter M1001C12 RRC_CONN_ACT_COMP is updated along
with this counter.
UE RNC Node B
UE in Cell_PCH/URA_PCH
RRC: Cell Update (RACH)
RRC: Cell Update Confirm (FACH)
RRC: UTRAN Mobility Information Confirm (RACH)
RRC: RRC Connection Release (FACH)
RRC: RRC Connection Release Complete (RACH)
M1001C629RRC_CONN_REL_DUE_HW_RES: The number of RRC
connection releases due to RNC HW resources.
Also counter M1001C12 is updated along with this counter. When the
RNC releases the RRC/Iu-PS connection due to the HW-resource
shortage in ICSU-units (amount of simultaneous RRC-connections) or
Soc Classification level
136 NSN Siemens Networks Presentation / Author / Date
shortage in ICSU-units (amount of simultaneous RRC-connections) or
in DMCU-units (no L2 processing resources available for UE
DCCH/DTCH).
RRC connection release due to MSLOST_URA_PCH
[FACH] RRC: Physical Channel Reconfiguration
UE
Node B
RNC
[RACH] RRC: Cell Update (Cell Reselection)
[FACH] RRC: Cell Update Confirm
[RACH] UTRAN Mobility Information Confirm
[RACH] RRC: Physical Channel Reconfiguration
Complete
M1006C110RRC_REL_MSLOST_URA_PCH : The number of
RRC connection releases due to 'MS is lost' in URA_PCH state.
Updated when a UE in URA_PCH state does not respond to
paging or does not make a periodic URA update within URA_PCH
supervision timer period and RNC releases the RRC Connection
resources
Soc Classification level
137 NSN Siemens Networks Presentation / Author / Date
Comments
Sevaral failure scenarios could be imagined and presented in several
points of this chapter especially when showing the flow charts
- How can I see the problem?
- Issues :
- HW related
- Software upgrade
- License missing
Soc Classification level
138 NSN Siemens Networks
- License missing
- Particular interference cases like Greenland
Presentation / Author / Date

You might also like