SmarTECH Overview

Radio Performance Optimisation
RAN network in process
Key Performance
Nominal planning
RAN optimisation
1 issue 11/09 TECHCOM Consulting  TECHCOM.DE Copyright © All rights reserved

Service trace process for: Mobile Operator Network
Agilent/TECHCOM successfully perform a 3G RAN

workshop in South Africa, November 2009. The operator
Network bought in the past already the Agilent DNA and SART
application to be able to troubleshoot 3G RAN related
service problems.
Target of the workshop was to present the additional Agilent
3G RAN troubleshooting application – data mining database
– to analyze high level KPI and drill down quickly to the root
• Iub/Iu data problems and RF Optimization application from smartTECH
capturing
by Agilent DNA/SART Following Performance KPI where seen in the network base
on the 3 days Call Data Record generation for customers
only at one RNC:
• Air interface
Vendor feature activation
analysis  Auto tuning enabled UL (max. range 20dB)
 Noise PwR-105 dBm default enabled
by TECHtrace  UL Interference limitation deactivated
 EcNo Filter coefficient is default 600 ms
RRM Reports)* TCP PWR is related to Release 99

Content
 Monitoring during Call Setup (RRC connection request)

 Quality Analysis EC/I0 (all calls, RT, NRT)
 Interference Analysis Little i (all calls, RT, NRT)
 Propagation Delay (all calls, RT, NRT - call setup versus distance)
 Monitoring during SHO (Event 1A – best active cell)

 SHO Window (all calls, RT, NRT)
 Cell Matrix
 Monitoring of RSCP (all calls, RT, NRT)
 Monitoring of load
 Transmitted Carrier Power
 Received Total Wideband Power
 Conclusions
 quality Key Performance
 Suggestions
Nominal planning
RAN optimisation
Node
B
Service architecture
RAN
analyzing
Tracing
• Data filtering
• analyzing
• Benchmark
Monitoring Service
GIS
process UE analyzing
Agilent
RAN Monitoring with DNA/SART
Route cause trouble shooting
CDR/CSSR diagnostics
Signalling analysis UTRAN
RPO/KPI

SW tools
We used…
 SmartTECH solutions 3G RAN/UTRAN
performance
 DNA/SART
smartRadio
Interference
Cell/GIS MAP
Benchmark with… performance
monitoring
 OSS KPI (tools)

smartRAN
 RANPAR (vendor) smartInfo RANPAR-library
GIS/MAP & QoS OSS/RANPAR
smartCount
KPI -library
OSS/counter
Protocol analysis SART

Monitoring during Call Setup - Busy hour - RRC Connection set-up RAN
analyzing
 Quality Analysis EC/I0 (all calls, RT, NRT
 Interference Analysis Little i (all calls, RT, NRT)
 Propagation Delay (all calls, RT, NRT - call setup versus distance)
RNC
[RACH] RRC:RRC Connection Request
RRC Connection Setup NBAP: RL Setup Request

phase Start TX/RX
AC to check to accept NBAP: RL Setup Response

or reject RRC ALCAP:ERQ
Connection Request
ALCAP:ECF
[FACH] RRC: RRC Connection Setup

EC/I0 map – from trouble shooting at Iub GIS
UE analyzing
Break point
Ec/Io
Ec/Io to initiate HO events
RSCP

Monitoring during Call Setup - Busy hour - RRC Connection set-up
 Quality Analysis EC/I0 (all calls, RT, NRT) RAN
analyzing
Number of cells versus median Ec/Io, for RT calls

Medium
Ec/Io of cells
for RT
Reference RAN Parameter range for good/acceptable quality: Ec/Io = -3 dB …-8 dB
Busy hours
In general, during RRC connection request statistics describes acceptable median Ec/Io
conditions, which are similar both for RT and NRT calls.
RAN
 Quality Analysis EC/I0 (all calls, RT, NRT)
analyzing
Number of cells versus median Ec/Io, for NRT calls Ec/Io of cells
for NRT less
good then RT
Reference RAN Parameter range for good/acceptable quality: Ec/Io = -3 dB …-8 dB
Busy hours
In general, during RRC connection request statistics describes acceptable median Ec/Io
conditions. Some cells show a median Ec/Io below the good quality threshold of -8 dB.
The worst cells for all calls are (both cell ID and SC is indicated):
Monitoring during SHO (Event 1A – best active cell)
P-RACH:
Out of Synchronization, Conclusions
high UL RTWP
Open loop Power control, • P-RACH - Ec/Io
initial PwR, analyzing
Ec/Io offset -20 dB
(required SIR - operator parameter)
Timer for P-RACH PwR ramping
C1 (UL/DL in-balance - CCCH > PwR max MS)
Initial RACH power = 33 – (-95 dBm) – 105 dBm – 17 = 6 dBm correct with normal UL- interference level
Initial RACH power = 33 – (-100 dBm) – 97 dBm – 17 = 19 dBm
For PS NRT = too low coverage - too high PwR for RACH necessary, Pmax UE= 21 dBm.
Initial RACH power:

CPICH Tx power – RSCP + RTWP + Required Received C/I
DPCCH_Initial PwR:
TxCPICH – CPICH_RSCP + RTWP + SIRDPCCH – 10 • log (SF DPCCH)

Little i map – from trouble shooting at Iub GIS
UE analyzing
CELL A
CELL C other cell interference Total _ Rx _ powerother

i 
CELL B own cell interference Total _ Rx _ powerown

 Interference Analysis Little i (all calls, RT, NRT) RAN
analyzing
Number of cells versus median little i, for RT calls
The strongest interfered cells during RT
call setup with median little i > 1 are …
Little i of cells
for RT
Number of cells versus median little i, for NRT calls
Little i of cells
for NRT less
good then RT
A huge fraction of the cells shows a median little i

of 1 and higher (this means, that the adjacent cell
interference exceeds the own cell one).
Propagation Delay (all calls, RT, NRT - call setup versus distance) RAN
analyzing
Number of cells versus median propagation delay, for RT calls
For RT calls, the median propagation

PD distribution delay ranges typically from 6-24 chips,
corresponding to about 0.5 to 1.9 km.
of cells Some cells, however, show a very large
max 7.5 km/RT median extension of up to 96 chips
(about 7.5 km).
Number of cells versus median propagation delay, for NRT calls
For NRT a higher median propagation

delay is indicated than for RT calls, typically
PD distribution of cells ranging from 9-30 chips.
max 5.5 km/NRT
Much more cells now show a median
propagation delay of 18 chips and higher.
The more distance access explains the
higher adjacent cell interference for NRT
calls.

Conclusions
• Little i
Little i is too much • PD
analyzing
More Antenna tilting
Less CPICH overshooting
Change/downgrade service request on cell
edge for NRT
Cell range:
Some cells show a very large median extension of up
to 96 chips (about 7.5 km).
The more distance access explains the higher adjacent

cell interference for NRT calls.

Monitoring during SHO (Event 1A – best active cell) RAN
analyzing
 Cell Matrix
 RSCP (all calls, RT, NRT)
Drift Serving
New
Node B RNC RNC
Event 1A,C
event-triggered
RRC: Measurement Report
RNSAP: RL Setup Request
NBAP: RL Setup
NBAP: RL Setup Response

RNSAP: RL Setup Response
Iub Bearer Setup
UP FP: Downlink Synch.

UP FP: Uplink Synch.
RRC: Active Set Update (RL Addition, Deletion, Replacement)

RRC: Active Set Update Complete
DCH DL RLC AMD rrcMeasurementControl

analyzing
SHO addition Window E1A is too late trigged :
• UE is often released, due to too late E1A and CDR goes up

• Low add. Window offset < 4 dB (serving cell – adjacent cell) reduce SHO
overhead KPI – at least no overlap of cells – coverage gaps are produced.
Ec/Io/RSCP
Ec/Io/RSCP
• The consequence of the delayed SHO
process decrease the coverage area.
Too late trigger from cell A-

A- B
+ 4 dB offset
SHO area
CELL B
CELL A Serving
Neighbour

 SHO Window (all calls, RT, NRT) analyzing
Number of cells versus median event 1a window, for RT calls
Too late active update Too early active set update

– too small SHO overhead – enlarge SHO overhead
For RT calls the SHO performance is consistent with an addition window of 4 dB. dB
In most cells the median EC/I0 difference between server and best neighbor indicated
by the first event 1A report is not much lower than this threshold. The SHO process is
initiated in time, when the server still is clearly dominating.

 SHO Window (all calls, RT, NRT) analyzing
Number of cells versus median event 1a window, for NRT calls
Too early active set update

Too late active update – enlarge SHO overhead
– too small SHO overhead
Very late active set update of controllable service comparing with RT
For NRT calls the first event 1A report indicates a lower median quality
difference between server and best neighbor in comparison to RT calls. The
SHO process is initiated with delay, the dominance of the server is already
weak in comparison to the neighbor.

analyzing
SHO overhead - trace results at NW/cell layer (example)
If SHO E1A window < 4 dB – than too
early E1A trigger, small SHO area
low
Interference
E1A in small Coverage holes/no cell overlap),
SHO areas, by averaging of filter coefficient,
caused E1A trigger
high interference
Release margin
High
Interference
Too late E1A trigger, big “SHO/power

overlap” area - Release margin will drop UE
Most significant causes at Cell layer e.g neighbor cell 18dB stronger than serving cell
Conclusions
• Event 1A
analyzing
Results:
In most cells the median Ec/Io
difference between server and best
neighbor indicated by the first event 1A
report is not much lower than
recommended threshold 2 dB…3 dB.
But please change shift Ec/Io filter
coefficient from 600 ms to 400 ms.

Cell matrix evaluations and improvements (description) RAN
 Cell Matrix analyzing
(CPICH SC)
Example to add a cell –

to become active set
enhancements,
e.g. 153 times of E1a
reports indicating in ADJ
Cell Matrix report show adjacent cell 1a/SC 25 (adjacent cell
properties in particular serving cell: update) and the addition
• N (number) - Serving cell visibility =
window offset is
Number of 1a reports indicating serving cell measured only by 1.24
• ADJ N (number) - Adjacent cell visibility = dB, recommended
Number of 1a reports indicating adjacent cell parameter 4 dB – too
• ADJ WIN_E1A - Average adjacent cell Visibility = late access for new cell
window offset (dB) Number of reports
• ADJ i - Adjacent cell Little i * visibility indicating cell n /
• INTRA - Adjacent DL SC (cell) is from same Total number of reports
site (Node B)
 Cell Matrix
Conclusions
• Cell matrix
analyzing
Results:
As example the cell matrix of cell
14683 is shown - see cell matrix
analysis.
We consider too long list of

neighbors.
CPICH over-shooting

Monitoring of RSCP (all calls, RT, NRT) RAN
 RSCP (all calls, RT, NRT) analyzing
Busy Hours
Even in SHO, for RT calls in many cases an acceptable median coverage is indicated.
Number of cells versus median RSCP, for RT calls
Reference RAN Parameter range for good/acceptable coverage: RSCP = -85 dBm …-95 dBm

Monitoring of RSCP (all calls, RT, NRT) RAN
 RSCP (all calls, RT, NRT) analyzing
Busy Hours
Even in SHO, for NRT calls the median coverage is lower than for RT ones, much more cells
now are below the acceptable RSCP threshold of -95 dBm. This is a consequence of the
delayed SHO process.
Number of cells versus median RSCP, for NRT calls
Reference RAN Parameter range for good/acceptable coverage: RSCP = -85 dBm …-95 dBm

RSCP map – from trouble shooting at Iub GIS
UE analyzing
PwR
(dBm)
dBm)
RSSI
Ec/Io
Ec/Io
RSCP
distance

Too late
Conclusions
Conclusion: E1a
Shift filter values for E1A Ec/Io requirements
(see also chapter SHO) This will improve RSCP • Event 1A/
(coverage due to MDC/MRC & SHO gain) coverage RSCP
DYLO already impacts too early NRT service
activation at cell edge (feature) – down grades
service request at cell edge – decrease
coverage & improve capacity, but due to high Too early entering trigger offset threshold
little i values (RT > 1) especially for NRT 1 …2,
we consider too much overshooting of PtxRL
adjacencies at cell level power. Ptxmax
Offset
Summery:
Small SHO areas (too late E1A activation) and
high neighbor cell PwR overshooting (little i for
NRT) decrease services, therefore total Triggering of DyLO
interference will increase and coverage will
decrease but DYLO can not compensate all Time/
Ptxave distance
negative impacts of interference.

Monitoring of load RAN
analyzing
 Monitoring of load
 Received Total Wideband Power
Drift Serving
New
Node B RNC RNC
Event 1A,C
event-triggered
RRC: Measurement Report
RNSAP: RL Setup Request
NBAP: RL Setup
NBAP: RL Setup Response

RNSAP: RL Setup Response
Iub Bearer Setup
UP FP: Downlink Synch.

UP FP: Uplink Synch.
RRC: Active Set Update (RL Addition, Deletion, Replacement)

RRC: Active Set Update Complete
DCH DL RLC AMD rrcMeasurementControl

analyzing
DL performance (Tx PwR)
total transmitted power Ptx Total area [dBm] 43 dBm
Overloaded area for 20 W

41dBm Ptx Target [dBm] + PtxOffset [dB]
40 dBm Marginal Load Area 1

Ptx Target [dBm]
Decrease power to
More feasible
perform more capacity by load and
less neighbour coverage with
interference in RSSI part
more PwR … Ptx _ total
More coverage
DL 
37.5 dBm Causes of DL interference: Ptx _ BTS , max
Fixed • Too much common Ch PwR
but much more
PwR. • User down link service allocation interference in
• TX IMP (3rd order) received part
• CPICH over shouting
CCCH capacity load ()

More visible capacity and coverage, but more inter cell interference
analyzing
Raw TCP versus time for cell 10873
Busy Hours
The median TCP within the network is low. The highest load is indicated for cell 10873, with a
median TCP of 27.5 % of the maximum cell power. The median TCP, however, is not very
informative, as the load undergoes very strong short term fluctuations. On the other side the raw
TCP measurements indicate, that even the cell with highest load seldom is in overload state.

Monitoring of load
Conclusions
• DL Tx PwR
analyzing
Results/conclusion:
No congestions due to low overload situations.
The highest load is indicated for cell 10873
(< 30% median max. load)

analyzing
Received Total Wideband Power
PwR rise
(dBm)
• High interference level due
to IMP and traffic load limits
service and throughput in
the cell per user PrxOffset
• It limits also coverage area
PrxTarget
of cells I own cell
I other cells
LRT  UnloadedRT (2%)

and LNRT  UnloadedNRT
(1%) Sum (3%)
Thermal noise -108 dBm + Io
3% 25 % 30 %
60 % load

analyzing
Received Total Wideband Power
Raw RTWP versus time for cell 16822
Busy Hours
The median RTWP within the network is very high, ranking from about -97 to -95 dBm for all
cells, which is far above the default overload threshold. There is also a considerable fluctuation,
as shown here for cell 16822, the cell with highest instability.
Monitoring of load
Received Total Wideband Power Conclusions
• UL RTWP
analyzing
Results/conclusion:
 Too much interference within UL direction

 Little i within UL direction is too high and/or out of band IM (e.g. video cameras)
 RRC performance can suffer.
 In-balance of UL/DL path loss
 auto tuning saves capacity within cell, already enabled, but too much little i
 Auto tuning can perform high UL sensitivity and save need of services within
cells. But it will reduce cell coverage too
 Use GIS analysis to detect UE faults and interference causes

Geo data map & user allocation (GIS) GIS
UE analyzing
t5
t4
t3
Broadcast
t1 Mobility and
pilot
Events
t2
UE specific
Evaluations by …
 Drive testing reduction Movement of UE
 Use probing, make analysis more quick
 Benchmark with OSS - RANPAR/KPI

Call trace – no simulations – from trouble shooting at Iub GIS
UE analyzing
Only about 50-100 m

offset from correct
course of the roads due
to prediction error

Service trace process
3G RPO Agilent/TECHCOM successfully perform 3G RAN

diagnostic systems.
service The new applications can optimize the radio & signaling
performance of RNC areas.
• GIS - profile • GIS service management (PoP/PoS)

• OSS counter /KPI improvements
service management
• RANPAR tuning and radio monitoring without drive test
• Cell Service Agilent 3G RAN troubleshooting application – using data

mining database – to analyze high level KPI and drill down
capability quickly to the root problems and RF optimization application
RNC benchmark from smartTECH

Cell service capability
smartRadio •UTRAN benchmark

Interference
monitoring
RANPAR,KPI,GIS
advanced service:
smartRAN
RANPAR-library
OSS/RANPAR
 Detecting of user service utilisation within cells
 Overall NW throughput performance detection
smartCount  Design of service MAP with data rate capability
KPI -library  Traffic analysis within networks
OSS/counter  BLER optimization by RANPAR calibration
 Drive test substitution and fault detection
smartInfo
GIS/MAP & QoS
RNC analysis by SART

Cell/GIS MAP
performance
smartRadio
Interference
monitoring
Detection of
RANPAR values
• Little i (PwR overlap)
• PDU credit delivery
• Cell orthogonality
• RSCP, Ec/Io etc.
smartInfo
• Cell Service capability GIS/MAP & QoS
e.g. BLER/SIR – target improvements
Protocol analysis SART
2MB/area 2
CELL A
throughput
CELL C performance
CELL B
0.5 MB/area 1
Cell Service capability

Cell throughput & capacity improvement
Vendor feature
Eb/No parameters can be configured by operator
• Eb/No flexible adjustable
(parameter object). Final DCH Eb/No must be • Service-specific,
determined for throughput & power estimations. • Quality-Target
• on Rx-Diversity
• Streaming Service on DCH or HSPA
• Orthogonality adjustable

Geo information system (GIS)
•UE – service management

GIS, PoP, PoS
smartInfo
GIS/MAP & QoS
advanced service:
 User service providing platform 7/24

 Google application without GPS/MS
 New services (security, Point of Present)
 New dedicated LBS flat rates
 Virtual shopping market placement
Always on by SART/DNA

Flexible - experienced - quick
We bring
technologies
and learning
products in time to
markets made by …
Please contact:
TECHCOM Consulting
D-82041 Oberhaching / Munich
phone: +49-89-638-488-0
fax: +49-89-638-488-99
e mail: TRAINING@techcom.de

SmarTECH Overview

Caricato da

Informazioni sul documento

Descrizione originale:

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

SmarTECH Overview

Caricato da

Copyright:

Formati disponibili

Radio Performance Optimisation

RAN network in process

1 issue 11/09 TECHCOM Consulting  TECHCOM.DE Copyright © All rights reserved

Agilent/TECHCOM successfully perform a 3G RAN

2 issue 11/09 TECHCOM Consulting  TECHCOM.DE Copyright © All rights reserved

 Monitoring during Call Setup (RRC connection request)

 Monitoring during SHO (Event 1A – best active cell)

 Monitoring of RSCP (all calls, RT, NRT)

4 issue 11/09 TECHCOM Consulting  TECHCOM.DE Copyright © All rights reserved

 OSS KPI (tools)

Protocol analysis SART

[RACH] RRC:RRC Connection Request

RRC Connection Setup NBAP: RL Setup Request

AC to check to accept NBAP: RL Setup Response

[FACH] RRC: RRC Connection Setup

6 issue 11/09 TECHCOM Consulting  TECHCOM.DE Copyright © All rights reserved

7 issue 11/09 TECHCOM Consulting  TECHCOM.DE Copyright © All rights reserved

Number of cells versus median Ec/Io, for RT calls

Reference RAN Parameter range for good/acceptable quality: Ec/Io = -3 dB …-8 dB

Reference RAN Parameter range for good/acceptable quality: Ec/Io = -3 dB …-8 dB

Initial RACH power:

10 issue 11/09 TECHCOM Consulting  TECHCOM.DE Copyright © All rights reserved

CELL C other cell interference Total _ Rx _ powerother

11 issue 11/09 TECHCOM Consulting  TECHCOM.DE Copyright © All rights reserved

Number of cells versus median little i, for NRT calls

A huge fraction of the cells shows a median little i

For RT calls, the median propagation

Number of cells versus median propagation delay, for NRT calls

For NRT a higher median propagation

13 issue 11/09 TECHCOM Consulting  TECHCOM.DE Copyright © All rights reserved

The more distance access explains the higher adjacent

14 issue 11/09 TECHCOM Consulting  TECHCOM.DE Copyright © All rights reserved

NBAP: RL Setup Response

Iub Bearer Setup

UP FP: Downlink Synch.

RRC: Active Set Update (RL Addition, Deletion, Replacement)

15 issue 11/09 TECHCOM Consulting  TECHCOM.DE Copyright © All rights reserved

SHO addition Window E1A is too late trigged :

• UE is often released, due to too late E1A and CDR goes up

Too late trigger from cell A-

16 issue 11/09 TECHCOM Consulting  TECHCOM.DE Copyright © All rights reserved

Number of cells versus median event 1a window, for RT calls

Too late active update Too early active set update

17 issue 11/09 TECHCOM Consulting  TECHCOM.DE Copyright © All rights reserved

Too early active set update

Very late active set update of controllable service comparing with RT

18 issue 11/09 TECHCOM Consulting  TECHCOM.DE Copyright © All rights reserved

Too late E1A trigger, big “SHO/power

20 issue 11/09 TECHCOM Consulting  TECHCOM.DE Copyright © All rights reserved

Example to add a cell –

We consider too long list of

22 issue 11/09 TECHCOM Consulting  TECHCOM.DE Copyright © All rights reserved

Number of cells versus median RSCP, for RT calls

23 issue 11/09 TECHCOM Consulting  TECHCOM.DE Copyright © All rights reserved

Number of cells versus median RSCP, for NRT calls

24 issue 11/09 TECHCOM Consulting  TECHCOM.DE Copyright © All rights reserved

25 issue 11/09 TECHCOM Consulting  TECHCOM.DE Copyright © All rights reserved

26 issue 11/09 TECHCOM Consulting  TECHCOM.DE Copyright © All rights reserved

NBAP: RL Setup Response

Iub Bearer Setup

UP FP: Downlink Synch.

RRC: Active Set Update (RL Addition, Deletion, Replacement)