Beruflich Dokumente
Kultur Dokumente
Course Content
KPI definition
Performance monitoring
Air interface optimization
Traffic monitoring
Capacity enhancement
Module Objectives
At the end of the module you will be able to:
Describe 3G RAN performance monitoring hierarchy
Busy hour
Paging, RRC and RAB setup and access failure
Session setup failure for NRT and HSPA
SHO, ISHO, relocation and SCC failure
RAB, DCH, radio link and HSPA drop
Performance Monitoring
KPI analysis hierarchies
Call setup (busy hour, paging, RRC, RAB, PS session)
Call drop (RAB, DCH, radio link)
Mobility (SHO, ISHO, relocation)
HSPA setup
HSPA drop
HSPA mobility (SCC, HSUPA SHO)
More details
More
understandi
ng
More
complexity
More cost
and time in
acquisition
Iub
WBTS
- Cell availability
- Failures due to Radio, BTS, transport
Soc Classification level
6
NSN Siemens Networks
Cell Availability
Failures due to Radio, to BTS, to transport
Handover Performance
Traffic
Cell Resources
Iub Signalling
Some data better analysed at RNC level
Here only time evolution and RNC comparison are useful
Cell with high failure rate might not have high priority, if
total traffic is low
Performance Monitoring
KPI analysis hierarchies
Call setup (busy hour, paging, RRC, RAB, PS session)
Call drop (RAB, DCH, radio link)
Mobility (SHO, ISHO, relocation)
HSPA setup
HSPA drop
HSPA mobility (SCC, HSUPA SHO)
1h
1h
0
Soc Classification level
12
NSN Siemens Networks
1h
BH
CSSR
CDR
12 h
24 h
Voice, GB (AF50%)
R99_DL, GB (25 % AF)
R99_UL, GB (25 % AF)
HSDPA DL, GB (100% AF)
Time / h
In unloaded networks CSSR taken at weekly BH may not yield the hour with
highest blocking (NRT traffic is taken into account as well as RT one)
Air Interface
WBTS HW Resources
Transport
RNC
UL interference
DL transmisson power
DL Codes
IuB
FSP/ WSP capacity
Soc Classification level
15
NSN Siemens Networks
BS
RNC
CN
Paging
UE in RRC idle
E.g. incoming RT or NRT call
Paging
UE in Cell_PCH or URA_PCH
E.g. inactive NRT RAB and
incoming voice call
Paging type 1
CN initiated
Paging type 1
RRC cell update
Paging
Paging type 2
UE in Cell_FACH or Cell_DCH
E.g. active NRT RAB and
incoming voice call
RNC initiated
Incoming data
Paging type 1
RRC cell update
UE in Cell_PCH or URA_PCH
NRT RAB inactive, but still data
arriving from core network
RNC pages UE to take the data
Cch,256,15
Cch,256,14
E-AGCH 2 ms
E-AGCH 10 ms
Cch,128,6
Cch,128,5
E-HICH & E-RGCH
HS-SCCH
Cch,128,4
Cch,16,0
S-CCPCH 2 PCH with 24 K
PICH
Cch,64,1
AICH
Cch,256,3
S-CCPCH 1 FACH
Cch,256,2
Cch,256,1
Cch,256,0
P-CCPCH
CPICH
Difference
Low air interface performance
Throughput / 80 Bit =
Number of pages per second
No response to paging
Check DL performance (RSCP, Ec/Io, S-CCPCH power settings) UE
might not be capable to decode page messages
Check UL performance (RTWP, RACH procedure parameter settings)
response of UE might not arrive at BTS
Access
Complete
Attempts
Setup
Complete
Access
Active
Active
Complete
Access
Phase:
Active
Release
Active
Failures
Access failures
Setup failures
(blocking)
Soc Classification level
21
NSN Siemens Networks
Success
Drop
Node B
M1001C0
RNC
Counter
AC to check to accept
or reject RRC
Connection Request
NBAP RL Setup Request
Start
Start TX/RX
TX/RX
Allocation of UTRAN
resources
M1001C1
Start TX/RX
RRC Connection
Access phase
L1 Synchronisation
NBAP Synchronization Indication
M1001C8
RRC Connection Active phase
Soc Classification level
22
NSN Siemens Networks
RNC
BTS
CN
Setup
Failure
Cause?
Sites
OK ?
RNC
BTS/TRANS/
Yes
Setup
/Access
Frozen BTS
Setup
AC
Setup
Troubleshooti
ng
UL/DL
Interferen
ce (DL
codes)
Access
Capacity
Optimisation
Access
Yes
3G cell at
inter-RNC
border ?
Relocation
troubleshootin
g
NO
RF
Optimisation
Interference
Coverage
Soc Classification level
24
NSN Siemens Networks
Setup
/Access
Coverage/
Interferen
ce
RNC problem
RNC fault
Failure of incoming relocation
BTS
Check e.g. channel cards
Soc Classification level
26
NSN Siemens Networks
RRC_CONN_STP_FAIL_BTS
Evaluate NBAP counters (radio link setup failures) for troubleshooting BTS resources (M1005)
Check BTS configuration in terms of WAM and CE allocation use channel element counters in
order to evaluate lack of channel elements (M5001)
RRC_CONN_STP_FAIL_RNC
Typically RNC fault or incoming SRNC relocation failure
Requires ICSU log tracing if no RNC fault or SRNC relocation problem
With I-phone
not possible
Quicker access
via RACH/FACH
for UE
Soc Classification level
29
NSN Siemens Networks
BS
RNC
CN
No RL setup
No CAC
No AAL setup
CM service request
Security procedures
No RL setup
No CAC
No AAL setup
Available SRB bit rate on DCH 3.4 kbps or 13.6 kbps configurable
by parameter
L1 Synchronisation
X
X
BTS
No L1 synchronization
Failure due to radio
No response from UE
Failure due to UE
Cell reselection or directed RRC
setup (no error)
L1 Synchronisation
NBAP: Synchronisation Indication
RRC Connection Setup Complete
UE
BTS
RNC
RNC
RRC_CONN_ACC_FAIL_MS
UL coverage tune cell dominance (CPICH) in order to balance UL and DL (if UL interference
not the cause
UE starts transmitting
without Post
Verification
40 ms window
40 ms window
ms window
50 ms 40
window
40 ms window
UE starts transmitting
with Post Verification
UE stops transmitting if
verification check fails
10 ms radio
frames
UE starts receiving,
mobile is listing on FACH
40 ms window
UE L1 collects 40 ms
of quality
measurements
Soc Classification level
35
NSN Siemens Networks
Post verification
check
BS
RNC
CN
CM service request
AC
RL rec. prepare
RL rec. ready
Iu CS
RNC internal
resources
AAL2
CAC
RAB_STP_ATTEMPTS
RAB_STP_COMPLETE
RAB_STP_FAIL_XXX_BTS
Evaluate NBAP counters (radio link reconfiguration failures) for troubleshooting BTS resources
(M1005)
Check BTS configuration in terms of WAM and CE allocation use channel element counters in
order to evaluate lack of channel elements (M5001)
RAB_ACC_FAIL_XXX_MS
Evaluate cell resources TCP and RTWP (for example high uplink interference)
RAB_ACC_FAIL_XXX_RNC
RAB_ACC_FAIL_XXX_RNC
Typically RNC fault or incoming SRNC relocation failure
Requires ICSU log tracing if no RNC fault or SRNC relocation problem
BS
RNC
Capacity request
AC
RL rec. prepare
RL rec. ready
AAL2 sig. ERQ
Performance Monitoring
KPI analysis hierarchies
Call setup (busy hour, paging, RRC, RAB, PS session)
Call drop (RAB, DCH, radio link)
Mobility (SHO, ISHO, relocation)
HSPA setup
HSPA drop
HSPA mobility (SCC, HSUPA SHO)
Configuration and
parameter audit
YES
SHO
Success
Rate <
90%?
SHO
3G Cell at
RNC
border?
ISHO
Failures
2G Cell Doctor
2G
Investigation
TCH blocking or
TCH seizure
failure
(interference)
Soc Classification level
45
NSN Siemens Networks
NO
YES
ISHO
Success
Rate <
90%
Iur
performance
Investigation
Iur
New site ?
Analyse last
detailed radio
measurements
NO
3G cell at
inter-RNC
border ?
YES
No cell
found
ratio >40
%
YES
YES
NO
ISHO
NO
Conf OK ?
Traffic
3G cell
covers over
a coverage
hole ?
YES
No cell
found ratio
> 90 % and
enough
ADJG
RF and IFHO
neighbour
optimisation
RF and ISHO
neighbour
optimisation
Wrong reference
clock (10MHz tuning)
3. Check SHO if success rate < 90% (leads to radio link failure)
4.
Check if cells are at RNC border (check Iur capacity and SRNC relocation problem)
Detect badly performing neighbours using SHO success rate per adjacency counters (M1013)
High incoming HO failure rate from all adjacencies check sync alarms
Check ISHO KPI if RT ISHO < 90% or NRT < 80% (leads to radio failure)
Check UE lost counters (active L1 synchronization failure) to check UL/DL path loss problem
Check active set update failure rate (with cause no response from UE)
Map radio failures with RL power and CPICH related parameters (CPICHToRefRABOffset, PTxDPCHMax)
Check for any BTS faulty alarm (e.g. 7653 cell faulty alarm)
Check physical channel reconfiguration failure rate (IFHO, ISHO, code optimization)
NRT
Interrupted communication between UE and network will not trigger
immediately RAB drop
Network tries to shift UE to Cell_FACH state, i.e. tries to keep RAB
running
RL deletion due to
synchronization failure
RL setup due to softer HO
RL setup due to initial request
RL setup due to soft HO
High number of
abnormal radio link
deletions by DRNC
Performance Monitoring
KPI analysis hierarchies
Call setup (busy hour, paging, RRC, RAB, PS session)
Call drop (RAB, DCH, radio link)
Mobility (SHO, ISHO, relocation)
HSPA setup
HSPA drop
HSPA mobility (SCC, HSUPA SHO)
BS
RNC
Measurement report 1A or 1C
AC
RL addition request
RL addition response
BTS resources
needed
But no Iub resources
(no CAC)
SETUP PHASE
ACCESS PHASE
Active set update complete
BS
RNC
Measurement report 1A or 1C
AC
RL setup request
RL setup response
AAL2 sig. ERQ
AAL2 sig. ECF
BTS resources
needed
SETUP PHASE
And Iub resources
needed (CAC)
ACCESS PHASE
Active set update complete
SHO Overhead
Concept and counters
Indicates size of SHO area
If too small, SHO might fail
If too big, capacity is wasted
SHO Overhead
Concept and counters
SHO Overhead
Cell level
E1A CPICH
E1B CPICH
Offset 4dB
Offset 6dB
SHO
area
cell
cellAA
ONE _ CELL _ IN _ ACT _ SET _ FOR _ RT / NRT
TWO _ CELL _ IN _ ACT _ SET _ RT / NRT 2
THREE _ CELL _ IN _ ACT _ SET _ RT / NRT 3
ONE _ CELL _ IN _ ACT _ SET _ RT / NRT
TWO _ CELL _ IN _ ACT _ SET _ RT / NRT
THREE _ CELL _ IN _ ACT _ SET _ RT / NRT
Total time during which all calls are
running with different AS size
60
Factors 1/2/3
= number of
radio links
Total time of
all calls
cell
cellBB
SHO Overhead
Cell level
Example: RNC area with 3 cells A, B and C
Cell A: 20 s active alone, 10 s with B, 10 s with C, 5 s with B + C
(20 s alone, 20 s with 2 cells, 5 s with 3 cells)
SHO Overhead
Cell level
Cell level formula gives too high KPI value
Reason:
If e.g. A and B are active, during this time a call is counted both in A and B,
i.e. two times
If e.g. A. B and C are active, during this time a call is counted in A, B and
C, i.e. three times
cell
cellAA
Counted in
cell A only
Counted in cell A and cell B
If cell A active together with B
than cell B also active together
with cell A
Soc Classification level
62
NSN Siemens Networks
cell
cellBB
SHO Overhead
RNC level
ONE _ CELL _ IN _ ACT _ SET _ FOR _ RT / NRT
TWO _ CELL _ IN _ ACT _ SET _ RT / NRT
cell
cellAA
63
Call belongs
to cell A only
cell
cellBB
Call belongs half to
cell A and half to cell B
SHO Overhead
RNC level
Example: RNC area with 3 cells A, B and C
Cell A: 20 s active alone, 10 s with B, 10 s with C, 5 s with B + C
Cell B: 30 s active alone, 10 s with A, 5 s with C, 5 s with A + C
Cell C: 25 s active alone. 10 s with A, 5 s with B, 5 s with A + B
RNC level results
Cell A, B and C altogether
75 s active alone
50 s with second cell
15 s with third cell
Average AS size = (75 + 50 + 15) / (75/1 + 50/2 + 15/3) = 1.33 (33% overhead)
RNC level KPI gives about half the overhead only than the cell level KPI!!
SHO Overhead
RNC level example
Very few attempts to nearby cell check user distribution and propagation
conditions
Very few attempts in general check addition window setting
Too many attempts to specific neighbor check user distribution and pilot
pollution
Too many attempts in general check addition window setting
SHO_ADJ_INTRA_FREQ_SHO_COMPL
SHO_ADJ_INTRA_FREQ_SHO_ATT
RN
C
MS
C
UE put into
compressed
mode
RxLev
measurements
NBAP: CM command
RRC: Measurement Control
BSIC verification
ISHO
execution
ISHO analysis
Flow chart
No
No action
needed
Yes
CM Start
Not
Possible?
No
Low ISHO
No
Measurement
success ?
Low ISHO
Success ?
No
Yes
Yes
Check admission
control rejection
TCP and RTWP
Yes
Missing ADJG or
Bad Neighbor
planning ?
Wrong 2G Ncell
Parameter (BSIC)
Or BSIC collision
Non-optimum
Compressed mode
parameter set
Missing or wrong 2G
parameter in 2G MSC
or SGSN (BCCH, LAC,
CellID)
Poor GSM
Coverage
2G Ncell
Congestion
Too low ISHO triggering
threshold or
Too strict ADJG
minimum threshold
Half Rate in 2G
Ncell ?
ISHO analysis
ISHO cause example
Blue = RSCP triggered
Red = Ec/Io triggered
Black = DL RL power triggered
UE power triggered = 0
UL SIR target triggered = 0
HHO mostly triggered by
event 1F
Event 1F again mostly due to
low coverage, but not quality
ISHO analysis
ISHO cause example RSCP under 1F conditions
ISHO analysis
ISHO cause example Ec/Io under 1F conditions
ISHO - analysis
ISHO failure example no target cell found
Each point represents one cell
100% target cell found
ISHO - analysis
ISHO failure example no target cell found
ISHO - analysis
ISHO failure example target cell not accessed
HO_ADJ_INTER_SYS_HHO_COMPL
HO_ADJ_INTER_SYS_HHO_ATT
Inter-RNC mobility
Relocation and anchoring
3GPP options to
use MM
SRNS relocation
CN
Iu
RNC
Iu
RNC
Iu
Iu
RNC
Iur
RNC
S-RNC
Anchoring supported in
Nokia SRNC only for CS RT
and PS NRT services within
Cell_DCH
CN
CN
CN
Iu
Iur
SRNC anchoring
Iu
Iu
Iur
D-RNC
RNC
Iu
Iur
RNC
Inter-RNC mobility
Incoming and outgoing relocation
Target RNC
Target RNC sees relocation as incoming RRC connection setup with cause SRNC
relocation
Setup, access and active counters incremented both for RRC and RAB
In case of failures, corresponding setup and access failure counters are
incremented both for RRC and RAB (failure due to RNC)
Source RNC
Source RNC starts relocation procedure and releases finally RRC connection
with cause SRNC relocation
RNC
Source
RNC
Targe
t
UE
SETUP PHASE
ACCESS PHASE
ACTIVE PHASE
RRC release due to relocation
Performance Monitoring
KPI analysis hierarchies
Call setup (busy hour, paging, RRC, RAB, PS session)
Call drop (RAB, DCH, radio link)
Mobility (SHO, ISHO, relocation)
HSPA setup
HSPA drop
HSPA mobility (SCC, HSUPA SHO)
BS
RNC
Capacity request
RL rec. prepare
RL rec. ready
No
High setup
failure rate
Top N cells
Yes
Setup Fail
BTS
Yes
No action
needed
No
Setup Fail UL
return
Channel
Yes
UL power
congestion
?
No
Check CE
resource usage
at BH
No
No
No
Setup Fail UE
Yes
Check RB
reconfiguration
Failure rate
Setup Fail
RNC internal
Yes
Check RNC
Unit load
(DMPG) and
faulty alarms
No
Check number of
simultaneous
HSDPA users
3. If due to UL DCH
Monitor UL load
4. If due to UE
Check for SHO overhead (all branches must have enough CE capacity if UE is in SHO when HS-DSCH
shall be allocated)
Check for SHO overhead (all inter-BTS branches must have enough capacity for associated DCH)
Performance Monitoring
KPI analysis hierarchies
Call setup (busy hour, paging, RRC, RAB, PS session)
Call drop (RAB, DCH, radio link)
Mobility (SHO, ISHO, relocation)
HSPA setup
HSPA drop
HSPA mobility (SCC, HSUPA SHO)
High drop
ratio
Top N cells
No action
needed
Yes
No
Pre-emption
No
Transition to
DCH due to
mobility
Yes
Yes
Normal Release
(No action
needed)
Normal Release
(No action
needed)
Transition to DCH
due to other
reason (e.g. type
of RAB)
No
No
Drop due to
radio
Yes
Yes
Normal Release
(No action
needed)
Drop due to
other reason
Yes
No
Check CQI distribution
and Ec/Io distribution for
coverage issue
Yes
Check HSDPA mobility
settings (SHO and SCC
parameter)
Performance Monitoring
KPI analysis hierarchies
Call setup (busy hour, paging, RRC, RAB, PS session)
Call drop (RAB, DCH, radio link)
Mobility (SHO, ISHO, relocation)
HSPA setup
HSPA drop
HSPA mobility (SCC, HSUPA SHO)
BTS
Targe
t
BTS
Source
RN
C
RN
C
BTS
Source
Setup of transport
resources only needed in
case of inter-WAM
mobility
HSDPAServCellWindow
EC/I0
Drop
window
6dB
Addition
window
CPICH 1 R99
CPICH 2 R5/6
4dB
Addition Time
SHO for A- Periodic
DCH initiated reports
CPICH 2 active
94
periodic reports as
long UE in SHO area
Serving cell change
initiated
time
CPICH 1 not
active anymore
HSDPASRBWindow
EC/I0
CPICH 1
CPICH 2
Addition
window
Addition Time
Just periodic
reports
periodic reports as
long UE in SHO area
Serving cell change AND
active set update initiated
95
time
No
Top N cells
No action
needed
Yes
No
SCC Fail BTS
Yes
No
SCC Fail AC
Yes
Check BTS HW
DL power
congestion
?
SCC Fail
Transmission
Yes
No
Channelization
No
code
congestion ?
Check
Maximum
number of
HSDPA users
No
No
No
SCC Fail UE
Yes
Check RB
reconfiguration
Failure rate
SCC Fail
Others
Yes
Check RNC
internal transport
resources (DMPG)
ICSU
troubleshooting
SCC Fail
Prevention
timer
Yes
Check
HSDPACellChange
MinInterval
parameter
HSPA started
Soc Classification level
97
NSN Siemens Networks
2.
Check HSDPA setup performance of target cells if SCC failure rate of source
cell is high
3.
4.
In case of power congestion check HSDPA power settings (in case of dynamic power R99
should not throw out HSDPA completely)
Usually NOT lack of CE (associated DCH already in SHO before SCC, for HSDPA CE
reserved per scheduler)
6.
7.
RNC sends pre-information about potential target cells during active set update already
Serving cell change commands transmitted both in source and target cell
UE
Source Node B
Target Node B
SRNC
cell)
After both source and target cell are prepared for serving cell change, to the UE are sent
RRC radio bearer configuration from RNC as usual (via HS-PDSCH in source cell)
HS-SCCH order from target Node B (via HS-SCCH in target cell)
If UE detects HS-SCCH order only, it still goes to target cell
The UE informs the RNC about the completion of the process with RRC radio bearer
reconfiguration complete
Source Node B
Target Node B
SRNC
SCC Evaluation
RRC: Measurement Report (event 1d, CFN)
SCC Decision
NBAP: Radio Link Reconfiguration Preparation
NBAP: Radio Link Reconfiguration Preparation
NBAP: Radio Link Reconfiguration Commit
NBAP: Radio Link Reconfiguration Commit
L1: HS-SCCH Order
RRC: Radio Bearer Reconfiguration
UE moves to Target Cell
RRC: Radio Bearer Reconfiguration Complete
set
Event 1D triggered if following equation satisfied during time interval defined by time-totrigger
Measured EC/I0
CPICH 1
Hyst / 2
Cell individual
offset CIO
CPICH 2
Time to
trigger
time
With SHO events and events 1F and 1E already maximum number of intra-frequency events
allowed by 3GPP achieved, so that event 1D cannot be offered any more
Events 1F and 1E therefore replaced by events 2D and 2F
Event 2F
One active cell acceptable again
Leave compressed mode
2F threshold
2D threshold
Event 2D
ALL active cells bad
Enter compressed mode
time
Soc Classification level
105
NSN Siemens Networks
Since RU20
First inter-RNC serving cell change, then relocation
Flow of user data over Iur, when inter-RNC neighbour becomes new serving cell
HSDPA service not interrupted by the mobility procedures
AS={A,B,C}
Normal SHO
for A-DCH
AS={C}
Trigger
relocation
AS={A,B,C}
C= best cell,
HS-DSCH data
over Iur
C
A
B
RNC
RNC