Drive Test KPI and Analysis

3G RANOP 1
Module 4 – Drive Test KPIs & Analysis
Drive Test KPIs & Analysis
v. 07.07.2008 RAS06
FOR INTERNAL USE ONLY
FOR INTERNAL USE ONLY
Soc Classification level
1 © Nokia Siemens Networks Presentation / Author /15.4.2008 KTe
3G RAN Optimisation
• Cluster health checks
• Drive Test KPIs
• Parameter consistency
Cluster Drive Test • Standard Acceptance Report
• Neighbour list
Analysis • Drive Survey Analysis
Preparation verification
• System Performance (RRC
• Uplink interference as a
and RAB phases)
problem indicator
• 3G<>2G Cell reselection
• RF optimisation • Neighbour Planning
RF Optimisation • New Site Integration InterSystem • Handover Process and
and Neighbour
• Neighbour plan Working and compressed mode
Planning • 3G ISHO service
optimisation Optimisation
analysis (AMR and PS)
• GSM ISHO Optimisation
• RRC Establishment
Signalling Parameter • Use of Parameters to
• RAB Establishment
Flows optimise network
• SHO Optimisation
• ISHO performance
• HSDPA & HSUPA
2 © Nokia Siemens Networks Presentation / Author / Date
Module 4 – Drive test KPIs and Analysis
Drive test KPIs and Analysis
Objectives
•After this module the delegate shall be able to:
After this module the delegate shall be able to:
• Understand the different elements required for an effective
drive test program
• Understand the KPIs that can be obtained
• Understand how all aspects of drive data can be used to
obtain a view of network performance
• Understand the Analysis process
• Differentiate between genuine (RF) and nongenuine
Differentiate between genuine (RF) and non
(system) failures
Module 4 Content
• Test Equipment and Setup
• Network Configurations and Parameters
• KPIs for CS and PS
• Standard Acceptance Reports
• Drive test analysis
Appendix RAS06 HSPA field performance measurements in
RAS06 HSPA field performance measurements in
NTN
Drive Test Process
Cluster Data Preparation Data Analysis Trouble

Preparation and Collection • Levels of Reporting Shooting
• Define Cluster • Services to test • Failure Type • Root Cause
• Define Drive Route • KPI definitions Breakdown Analysis
• Equipment • Post Processing • Corrective Action
• Exclusions functionality • Further data
• Call Patterns • KPI Gap Analysis logging (maybe)
• OSS Alarms
• Network Stats
Why Drive the Network
• New Site Integration
• RF Tuning
• Network Optimisation
• Network Benchmarking (Golden clusters)
Network Benchmarking (Golden clusters)
• Release Testing
Drive test Performance
There could be many reason for poor Performance like
• Radio Conditions
• UE Category & Performance
• Measurements tool & Settings
– TCP/IP Settings in PC
– Nemo Script (e.g. wait time related to PDP context activation)
• Server location and settings
• HLR QoS Profile
• Network Configuration and Parameters
Network Configuration and Parameters
Radio Conditions and Coverage
In general, KPI values are valid in regions with sufficient coverage and under good
radio conditions.
• Test is to be done inside the coverage area
– In case coverage requirements is met but call fails due the coverage, these samples are to
be excluded from the analysis
Example of Call Success Criteria
RSCP Ec/No
Signal Call
above OK
Signal above
Call Call (B)
(B) Ec/No
RSCP Call
80dBm OK
NOK 5dB thresho
ld
threshold
Ó
95dBm 12dB

Signal Signal
below below
RSCP Call Ec/No
OK
threshold 110dBm
Threshold
Ó Call
20dB threshold
Call
Call(A) NOK Discard sample
Time
Drive Test Equipment
Nemo Outdoor Multi with UE’s, Scanner and GPS can be used
• The Scanner measures all used carriers/cells and their corresponding DL
scrambling codes,
• UE only measures SC signals from the cells that the system has informed/ordered
the UE through the BCH (neighbour list) or via the “measurement control” msg.
UE: Scanner:
• RSCP Active/Monitored Set • For low coverage areas
• Carrier RSSI • For Antenna Installation problems
• Ec/No Active/Monitored Set • For Missing neighbours
• UL/DL Data Throughput • For Coverage optimisation
• The BLER downlink • With Scanner you can get following info
• Pilot BER from the surrounding cells:
• Random Access Initial Tx Power – Different Scrambling codes
• Random Access Preamble Count & Step – CPICH RSCP value (dBm)
• SIR target (UE dependent) – CPICH EcNo value (dBm)
• UE Tx Power
• Call Statistic: AMR, CS and PS data calls
Important to drive with call logging equipment and 3G/2G scanner in the same van
Important to drive with call logging equipment and 3G/2G scanner in the same van
UE Performance HSDPA
UE Categories 7 and 8 (HSDPA)
• UE Category has impact for the throughput performance.
Number of HS Air Interface bit MACd flow bit
UE Cat Modulation
DSCH rate (Mbps) rate (Mbps)
6 5 16QAM 4.8 3.5

8 10 16QAM 9.6 7.2
10 15 16QAM 14.4 13.976
12 5 QPSK 2.4 1.8
Terminal Examples
Nokia N95 Merlin X950D
• HSDPA Cat 6 terminal • HSDPA Cat 8 terminal
HSDPA Cat 8 terminal
• Non HSUPA terminal • HSUPA Cat 5 terminal
HSUPA Cat 5 terminal
• 16QAM modulation • 16QAM modulation
16QAM modulation
• Support a max of 5 codes • Support a max of
Support a max of 10 codes
• Max theoretical throughput • Max theoretical throughput
Max theoretical throughput
~3.6 Mbps ~7.2 Mbps
SUPPORTED BY NEMO SUPPORTED BY NEMO
UE Performance HSUPA
• HSUPA UE category has impact for the throughput
EDCH category Maximum number Minimum Support for 10 and 2 ms Maximum number of Maximum number of bits
of EDCH codes spreading TTI EDCH bits of an EDCH of an EDCH transport
transmitted factor transport block block transmitted within
transmitted within a a 2 ms EDCH TTI
10 ms EDCH TTI
Category 1 1 SF4 10 ms TTI only 7110
Category 2 2 SF4 10 ms and 2 ms TTI 14484 2798
UE category and used packet
Technology (HSPA / HSDPA) can
be verified with Nemo
be verified with Nemo
Test Setup – Server and Laptop Settings
Server and Laptop Settings I
Measurement Laptop settings
• Use “clean” Laptop – do not use NSN build laptop
do not use NSN build laptop
• Use a highspec laptop – high CPU speed and lots of RAM
high CPU speed and lots of RAM
• Optimize TCP/IP Settings
– GlobalMaxTcpWindowSize / TCPWindowSize
TCPWindowSize (values recommended by Nemo)
§ > 128k for 7.2Mbit/s HSDPA and 256k for higher HSDPA bitrates
and 256k for higher HSDPA bitrates
§ Using unnecessarily high values should be avoided (RTT can increase)
– Tcp1323Opts = 3
§ 3 by default, and it is not recommended to change this (windows scaling)
Server location and settings
• it is recommended to use external server which is directly connected to GGSN with
following server and client settings
– MTU size = 1500 bytes,
– TCP window size =16k (Rel’99, nonHSPA); 64/256k for HSPA
HSPA); 64/256k for HSPA
– Server should support 256k win size for client (Window scaling support)
Server should support 256k win size for client (Window scaling support)
– No IP header compression
Test Setup – Server and Laptop Settings
Server and Laptop Settings II
• Never set TCP values manually by modifying registers (same parameter can be in
the several places), use ready made tools, like TCP Optimizer, to change values
• Conform e.g. by using Wireshark (Ethereal) that change is done
Select Custom
• 256k for HSPA settings
• 64k for R99
Test Setup Nemo Script
Nemo Script – PS call I
• Nemo Outdoor automatically inserts a small pause between successful attach
event and proceeding PDP context activation attempt to increase stability.
– In the worst case this pause causes RRC connection to be released at the same time
RRC connection to be released at the same time
when PDP context activation attempted.
– To avoid this happening it is wise to add Wait 2 sec between attach and PDP context
activation procedures in Nemo Outdoor script.
• Another important issue to remember is to have at least 5 sec pause between
consequent PS detach (attach > PDP activation
> PDP activation > PDP deactivation > detach)
– To facilitate the analysis it is recommended to place a Wait of 5 sec in the beginning of
To facilitate the analysis it is recommended to place a Wait of 5 sec in the beginning of
each PS measurement script.
Example of PS call
script structure
Nemo Script PS call II
PDP Context Activation Time
NOTE!! Values are between
Cumulation and Density PDP context request and PDP
100 context accept msgs.
90
Percentage (%)
80
70
60 WITH 2 sec Wait TIME between attach
50
40 and PDP context activation
30
20
10
0
0 All samples below 0,6 sec
0.2 0.4 0.6 0.8 1 1.2 1.4 1.6 1.8 2 2.2 2.4 2.6 2.8 3 3.2 3.4 3.6 3.8 4 4.2 4.4 4.6
Time (s)
Cumulation and Density
100
90
Percentage (%)
80
70
60
50
40 WITHOUT 2 sec Wait TIME
30
20
10
0
00.4
0.8
1.2
1.622.4
2.8
3.2
3.644.4
4.8
5.2
5.666.4
6.8
7.2
7.688.4
8.8
9.2
9.6
10
10.4
10.8
11.2
11.6
12
12.4
12.8
13.2
13.6
14
14.4
14.8
15.2
15.6
16
16.4
16.8
17.2
17.6
18
18.4
18.8
19.2
19.6
20
6
20.4
20.8
21.2
21.6
22
22.4
22.8
23.2
23.6
24
24.4
24.8
25.2
25.6
26
26.4
26.8
27.2
27.6
28
28.4
28.8
29.2
29.6
30
30.4
30.8
31.2
31.6
Time (s)
62% of samples between
0,40,6 sec 28% of samples between
31,431,6 sec
Nemo Script PS call III
No wait time used: Cause RRC
connection to be released at the
same time when PDP context
activation attempted.
Attach Complete
1 st activate PDP UE wait 30 sec before

context request trying again – T3380
2 nd Activate PDP
context request 30sec
later
QoS Profile I
QOS PROFILE INFORMATION:
INDEX..QOS PROFILE INDEX ................... 187 QoS profile Settings can impact
NAME...QOS PROFILE NAME .................... B8M4M
CLASS..TRAFFIC CLASS ....................... B for the throughput
ORDER..DELIVERY ORDER ...................... N
DELERR.DELIVERY OF ERRONEOUS SDU ........... N • Make sure that QoS profile
SDUMAX.MAXIMUM SDU SIZE .................... 1500 settings are not limiting throughput
DWNMAX.MAXIMUM BIT RATE FOR DOWNLINK ....... 8640
UPMAX..MAXIMUM BIT RATE FOR UPLINK ......... 4352
BER....RESIDUAL BER ........................ 7
SDUERR.SDU ERROR RATIO ..................... 5
SDUERR.SDU ERROR RATIO ..................... 5
DELAY..TRANSFER DELAY ......................
UPBR...GUARANTEED BIT RATE FOR UPLINK ......
DWNBR..GUARANTEED BIT RATE FOR DOWNLINK ....
PRIOR..TRAFFIC HANDLING PRIORITY ...........
“subscribed” means
that settings in HLR
• Tools like Nemo Outdoor can “overwrite” HLR QoS are used
QoS profile as long as values requested are not
tighter than in HLR QoS profile
Implementation depends on modem type
•USB modems (Nokia phones) require ATZ
string in modem advances settings
Lower bitrate than in
• Datacards don’t require ATZ, and functionality HLR QoS profile can be
is always on (and cannot be turned off) requested
=> Check tool QoS profile settings
QoS Profile II
“Activate PDP context Request” Message contains information about requested QoS
Message contains information about requested QoS
• “subscribed” means using HLR QoS profile settings
“subscribed” means using HLR QoS profile settings
“Activate PDP Context Accept” message contains information about Negotiated QoS
message contains information about Negotiated QoS
Module 4 Content
NTN
Optional Network features and configurations influence the result of Field KPI
measurements.
• Activated features (e.g. HSDPA and HSUPA optional features)
• Iub configuration
• RAN Parameters
• Core Network (SW level etc)
UE
Iub Iu
WBT RNC Core NW
S
Network Configuration and Parameters HSDPA
• RAS06 optional HSDPA features are impacting for throughput depending if
activated or not
• Max User bit rate with different RAS06 features
bit rate with different RAS06 features
• Higher bit rates can be achieved in very good network conditions only
Features QPSK 16QAM + 15 code + 10 Mbps 14.4 Mbps 14.4 Mbps 14.4Mbps

user 1 user 2 Total
Modulation QPSK 16QAM 16QAM 16QAM 16QAM 16QAM
UE category Cat 1112 Cat 6 Cat 78 Cat 910 Cat 910 Cat 910
Number of HSPDSCH codes 5 5 10 15 8 7
Air interface bit rate (Mbps) 2,4 4,8 9,6 14,4 7,68 6,72 14,4
Max. transport block size (bits) 3630 7298 14155 20251 14936 13177
Max. transport channel (MACd flow) bit rate (Mbps) 1,815 3,649 7,0775 10,1255 7,468 6,5885 14,0565
RLC PDU (bits) 336 336 336 336 336 336
RLC blocks/TTI 10 21 42 60 44 39
RLC bit rate (Mbps) 1,68 3,528 7,056 10,08 7,392 6,552 13,944

RLC payload (Mbps) 1,6 3,36 6,72 9,6 7,04 6,24 13,28
• 656 PDU size cab used for some the higher CQIs
656 PDU size cab used for some the higher CQIs
Testing of HSDPA 15 codes
HSDPA 15 codes is RAS06 Optional Feature
• Testing of HSDPA 15 codes require Cat9 UE, or two Cat 78 UEs in case
Testing of HSDPA 15 codes require Cat9 UE, or
Cat9 UE is not available
– Cat 7 8 UE supports 10 codes only
– The peak cell rate for a single user is 7.0Mbps. For two users is 6.5Mbps and
7.0Mbps respectively for code allocations of 7 and 8 codes. Peak BTS cell level
7.0Mbps respectively for code allocations of 7 and 8 codes. Peak BTS cell level
throughput is close to 13.66Mbps.
Network Configuration and Parameters HSUPA
• If HSUPA 2M feature is activated, the throughput is higher than with basic
If HSUPA 2M feature is activated, the throughput is higher than with basic
HSUPA
Iub Demand for HSDPA High Bit rates In RAS06 – theoretical
max thput per cell is
14.4 Mbps
5 x E1
7 x E1
Iub Capacity can be checked
from the COCO
16400 cps => 6.9 Mbps=> 4x E1
Above RLC = 5.3 Mbps
Check also
VCC bundle
23 © Nokia Siemens Networks Presentation / Author / Date peak cell rate
Parameters
• Parameter HSDPAPeakRateLimitRABMax
HSDPAPeakRateLimitRABMax defines the peak rate of MACd flow,
peak rate of NRT RB mapped to HSDSCH and peak rate of UL return channel
DSCH and peak rate of UL return channel
limited to RAB attribute maximum bit rate received from RANAP or not.
– Easiest way to avoid the HLR profile to limit the throughput is set this to 0 (not limit)
• Parameter MaxBitRateNRTMACDFlow should be set to 6784 for 7.2
should be set to 6784 for 7.2
• Parameter MaxTotalUplinkSymbolRate should be set to 3840 kbps if HSUPA 2.0 is
should be set to
activated
• Parameter FactorEDCHMaxBitRate should be set to 5 if HSUPA2.0 is activated and
should be set to 5 if HSUPA2.0 is activated and
subscriber HLR QoS profile is set to 384kbps. FactorEDCHMaxBitRate multiplied by
subscriber HLR QoS profile is set to 384kbps.
UL QoS should be superior to target UL throughput.
UL QoS should be superior to target UL throughput.
Field Measurement KPIs
Field Measurement KPIs – RAS06
NOTE!! Some of the KPI targets & Results are based on NTN* measurements (lab
Some of the KPI targets & Results are based on NTN* measurements (lab
or field) as there is not enough RAS06 project level results available yet.
or field) as there is not enough RAS06 project level results available yet.
*NTN = Nokia Test Network
Module 4 Content
– CS KPIs
– PS KPIs
§ Setup success & time, Retainability and mobility
§ RTT
§ R99 and HSPA Throughput
NTN
All Mobility
KPIs for CS RAS06 I Measurements
SRB rate 13.6
• No new RAS06 KPIs related to CS Domain kbit/s assumed
Maximum Normal
PI # FPI Name Triggering Test Setup
Results Results
MOC setup time is the interval between the submission
Call Setup Time 1 UE MOC to test
FPI_6a of the "RRC CONNECTION REQUEST"
"RRC CONNECTION REQUEST" message and 2.1 sec 3.5 sec
Voice MOC @ 95% number:
the reception of the L3 msg "CC ALERTING" at a UE.
Ratio between successfully established CS voice calls
Call Setup Success compared to the overall number of voice call 1 UE MOC to test
FPI_7 99%
Rate Voice (%) establishment attempts “DL direct transfer (CC:
“DL direct transfer (CC: number:
alerting)” message is received by UE
Ratio between successfully established CS voice calls
Call Setup Success compared to the overall number of voice call 2 UE (MOC+ MTC) from
FPI_8 99%
Rate Video (%) establishment attempts “DL direct transfer (CC:
“DL direct transfer (CC: moving UE to stationary
alerting)” message is received by UE
Ratio between abnormally released voice calls and the
Drop Call Rate Voice overall number of established voice calls (e.g. “RRC 1 UE MOC to test
FPI_9 1%
(%) Connection Release” message is received before number:
“UL/DL CC: disconnect” )
Ratio between abnormally released video calls and the
Drop Call Rate Video overall number of established video calls (e.g. “RRC 2 UE (MOC+ MTC) from
FPI_10 1%
(%) Connection Release” message is received before moving UE to stationary
“UL/DL CC: disconnect” )
Call Setup Time “RRC Connection request” message to “DL direct 2 UE (MOC+ MTC) – from
FPI_6b 3.8 sec* 6.5 sec
Voice MMC (sec) transfer (CC: alerting)” msg. moving UE to stationary
Call Setup Time “RRC Connection request” message to “DL direct 2 UE (MOC+ MTC) – from
FPI_11 4.4 sec* 6,5 sec
Video MMC (sec) transfer (CC: alerting)” msg. moving UE to stationary
27 © Nokia Siemens Networks * Feature PDC04675 improves M2M call setup times
* Feature PDC04675 improves M2M call setup times
Presentation / Author / Date
KPIs for CS RAS06 II

Maximum Normal
Results Results
FPI_12 SHO Overhead 100*(Ave AS Size 1)%. N/A N/A *
SHO success is defined as the ratio of
FPI_13 SHO Success Rate 99%
successful Active set updates and Active
set update attempts
From HandoverFromUTRANCommand
1 dual mode UE MOC
FPI_14 ISHO Success for Voice 3G> 2G (%) to Handover Complete to GMS (or 98%
to test number
continue successfully in 3G ?)
From RR Inter System From UTRAN 1 dual mode UE MOC
FPI_15 ISHO Success for Voice 2G> 3G (%) 98%
Handover Command to to test number
HandoverToUTRANComplete message.
•* SHO overhead may change heavily depending on dominance plan and used
* SHO overhead may change heavily depending on dominance plan and used
SHO parameters.
•Typical targets for area level could be 40
60%
KPIs for CS Test Setup
• Typically a few different type of call scenarios is used to measure CS KPIs.
• Call length have impact for the drop call rate, at least 90 sec call should be used to
measure drop call rate. Shorter call can be used to measure CSSR.
• Call length has no impact for the call setup times.
• ISHO measurement require dual mode UE, but for 3G KPIs UE is typically locked to
3G.
Below some possible call scenarios that can be used to measure CS KPIs
– 90 sec call with 15 sec idle from UE to PSTN – UE locked to 3G
90 sec call with 15 sec idle from UE to PSTN
§ Drop call rate
§ MOC call setup time
§ SHO success and overhead
– 30 sec call with 15 sec idle from 3G to 3G – UE locked to 3G (Bparty stationary)
30 sec call with 15 sec idle from 3G to 3G
§ CSSR (voice or video)
§ MMC call setup time
– 30 min long call – UE in dual mode
§ ISHO success
KPIs for CS Signalling
Call Setup success and Call setup time
UE Node B RNC CN
RRC Connection Request (RACH)
RRC Connection Setup (FACH)
RRC Connection Setup Complete (DCH)
Initial Direct Transfer (CM Service Request)
RANAP: Initial UE msg.
DIRECT TRANSFER (CM service Accept)
DIRECT TRANSFER (CM service Accept)
Call Setup Success
DIRECT TRANSFER (Setup) & Time
DIRECT TRANSFER (Call Proceeding)
RANAP: RAB Assignment Request
RRC: Radio Bearer Setup
RRC: Radio Bearer Setup Complete
RANAP: RAB Assignment Response
DIRECT TRANSFER (Alerting)
DIRECT TRANSFER (connect)
DIRECT TRANSFER (connect Acknowledge)
KPIs for CS Signalling
Drop call rate
Node B RNC CN
UE
DIRECT TRANSFER (Alerting)
DIRECT TRANSFER (connect)
DIRECT TRANSFER (connect Acknowledge)
Call Established
DIRECT TRANSFER (Disconnect)
DIRECT TRANSFER (Release) Call drop rate
DIRECT TRANSFER (Release Complete)
Iu Release Command
Iu Release Complete
RRC Connection Release
RRC Connection Release Complete
Radio Link Deletion Request

Radio Link Deletion Response
ALCAP: Release Request
ALCAP: Release Response
ALCAP: Release Request
ALCAP: Release Response
Call Released
Voice Call Setup Time – Example from NTN
Example from NTN NTN
results
• The AMR voice call setup time was tested with UE to PSTN, PSTN to UE and UE
to UE calls. The call setup time was measured between RRC Connection Request
to UE calls. The call setup time was measured between
and Alerting messages for Asubscriber. In MTC case between
subscriber. In MTC case between Paging type 1 and
Alerting.
• The performance figures are based on timestamps in the UE logs.
RAS06 Call setup time (s) SRB 3.4 SRB 13.6 SRB 3.4 SRB 13.6
target result target result RAS51 RAS51
Mobile originating call 4.0 3.3 3.0 2.1 3.5 2.5
MOC with mobility 4.6 3.2 3.3 2.1 3.7 2.6
Mobile terminating call 4.4 3.0 3.4 1.8 3.4 2.2
MTC with mobility 5.0 3.1 3.7 1.9 3.8 2.2
Mobile to mobile call 8.4 5.5 6.4 3.7 7.5 5.1
M2M with mobility 9.0 6.0 6.7 3.8 Feature PDC04675 8.2 5.5
improves M2M call
setup times
Note: The parallel RB setup for calling UE and paging of terminating UE in CS core
(feature PDC04675) was in use which improved the M2M results as compared to
previous releases.
Video Call Setup Time – Example from NTN
results
• The UDI data call was tested with realtime video call.
time video call.
• The network setup delay was measured between RRC Connection Request and
The network setup delay was measured between
ALERTING messages.
CS video Call setup time (s) SRB3.4 SRB13.6

target result target result
M2M CS video call 8.0 5.1 6.4 3.6
With mobility 9.2 5.9 7.0 4.4
• Note that these tests show only the network setup delay while major part of the
endtoend delay is caused by the UE application. Application level negotiation time
end delay is caused by the UE application. Application level negotiation time
was not measured.
Module 4 Content
– CS KPIs
– PS KPIs
§ RTT
NTN
KPIs for PS – Success and Drop ratios
Success and Drop ratios
• In PS side, HSUPA setup success and Retainability are RAS06 new KPIs
In PS side, HSUPA setup success and Retainability are RAS06 new KPIs
Maximum Normal
Results Results
Average GPRS Attach Time “RRC Connection request” message to “
” message to “Attach
FPI_20 1 PS MOC UE
(sec) Accept” message 1.5 sec 2 sec
Between the "RRC CONNECTION REQUEST" msg.
Between the "RRC CONNECTION REQUEST"
Average PDP Context
FPI_21a and the reception of the L3 message "ACTIVATE PDP
and the reception of the L3 message 1 PS MOC UE
Activation time CONTEXT ACCEPT" at a UE. 1.4 sec 2 sec
Activate PDP Context Success “RRC Connection request” message to “
” message to “Activate
FPI_22 99% 1 PS MOC UE
Rate (%) PDP context Accept” message
Number of successful PS setups number of lost
Number of successful PS setups
FPI_27 PS Retainability ratio (%) 99% 1 PS MOC UE
PS sessions/Number of established PS sessions.
HSDPA setup success ratio “ULDCCH Measurement Report (e4A)”
Measurement Report (e4A)” message
FPI_28 98% 1 HSDPA MOC UE
(%) to “Radio Bearer Reconfiguration complete
Radio Bearer Reconfiguration complete” msg.
“ULDCCH Measurement Report (e4A)”
Measurement Report (e4A)” message
FPI_29 HSPA setup success ratio (%) to “Radio Bearer Reconfiguration
Radio Bearer Reconfiguration” complete msg. 98% 1 HSPA MOC UE
(HSPA allocated)
(Number of Successful HSPA Setups” – “Number
FPI_30 HSDPA Retainability (%) of lost HSPA Sessions”)/”Number of Successful 98% 1 HSDPA MOC UE
HSPA Setups
(Number of Successful HSPA Setups” – “Number
FPI_31 HSPA Retainability (%) of lost HSPA Sessions”)/”Number of Successful 98% 1 HSPA MOC UE
HSPA Setups
“Radio Bearer Reconfiguration” message
Radio Bearer Reconfiguration” message to “Radio 1 HSDPA/HSPA MOC
FPI_32 HSPA SCC Success (%) 98%
Bearer Reconfiguration complete” msg.
Bearer Reconfiguration complete” UE
KPIs for PS Signalling
GPRS Attach Time
UE Node B RNC CN
RRC Connection Setup Complete (DCH)

Initial Direct Transfer GPRS Attach Request (DCH)
RANAP: Initial UE msg.
DIRECT TRANSFER (Authentication and ciphering request)
DIRECT TRANSFER (authentication and ciphering response) PS attach time
Security mode command

Security mode complete
Downlink direct transfer: common id

Uplink Direct transfer: identity response
Downlink direct transfer: Attach Accept
direct transfer: Attach Accept
Uplink Direct transfer: Attach Complete
PDP Context Activation time and Success
UE Node B RNC CN
GPRS Attach

PDP context activation
RRC Connection Setup Complete (DCH) time and success
Service Request
Security mode command

Security mode complete
Activate PDP context request (DCH)
RANAP: RAB Assignment Request
RRC: Radio Bearer Setup
RRC: Radio Bearer Setup Complete
RANAP: RAB Assignment Response
Measurement Control
Activate PDP Context Accept (DCH)
Call Established
HSPA Setup
HSUPA cannot be established without HSDPA, HSDPA UL return channel is HSUPA
instead of R99
– High level procedure is the same as that for an NRT DCH
– RNC starts by allocation a 0/0kbps connection
– Selection between DCH and EDCH is then completed when RNC receives the uplink or
DCH is then completed when RNC receives the uplink or
downlink capacity request
UE Node B RNC
PDP Established
Measurement Report : e4a
NBAP: Radio Link Reconfigure Prepare
Radio Link Reconfigure Ready
AAL2SIG:ERQ
AAL2SIG:ECF
AAL2SIG:ERQ
HSUPA setup AAL2SIG:ECF
Radio Link Reconfiguration Commit
RRC: Radio Bearer Reconfiguration (DCH)
RRC: Radio Bearer Reconfiguration Complete (DCH)
HSUPA Call Established
HSUPA Call Established
Attach and PDP context activation Time NTN
results
NTN Example
Attach Time
• GPRS attach time was measured between messages
GPRS attach time was measured between messages RRC Connection Request
and ATTACH_ACCEPT
GPRS attach time (s) SRB 3.4 SRB 13.6
Stationary 3.0 1.9 2.0 1.2
With mobility 3.9 2.1 3.9 1.5
• The UE was registered in the HLR and IMSI attached. The measurements were
performed with mobile and stationary users.
performed with mobile and stationary users. The time needed for GPRS attach
is included in the these results.
• The accept time was measured between messages
The accept time was measured between messages RRC Connection Request
and Activate PDP Context Accept
PDP context accept time (s) SRB 3.4 SRB 13.6
Stationary 4.3 3.0 3.3 1.7
With mobility 3.1 1.7
PDP context activation Time
Result from Customer
• The measurements were performed in static conditions
• The accept time was measured between messages
The accept time was measured between messages RRC Connection Request and
Activate PDP Context Accept
• The results presented here are average of 20 samples for Huawei data card (Cat 8)
The results presented here are average of 20 samples for Huawei data card (Cat 8)
PDP context accept time (s) SRB 13.6
target result
Stationary 4.0s 1.48s
HSDPA Serving Cell Change
HSDPA Serving Cell Change
HSDPA SCC
Active Set Update to add new
target cell to AS
Physical Channel Reconf. to
Reconfigure the HSDPCCH in
the new target cell for UL
signaling (not happening in case
Intra BTSSCC)
SCC is triggered
After receiving the first HSDSCH
After reserving resources in the packet from the target cell the UE
new target cell RNC sends the send the Radio bearer
Radio bearer reconfiguration reconfiguration complete message to
Soc Classification
message level to the UE
the RNC, which can release
resources from the source cell
HSPA InterRNC Cell Change
Cell Change
RAS06 NEW
• Users located in RNC HSPA Inter
RNC cell
Application layer HSDPA throughput
border areas and users
change
crossing them will have triggered
seamless HSPA.
• Feature uses interRNC 2.5 Mbps
hard handover (SRNS
relocation) directly from
HSPA to HSPA.
• No fallback to R99.
• No HSPA established
over Iur, no HSPA load
on Iur.
Application layer
data break ~ 1.5
seconds
Module 4 Content
– CS KPIs
– PS KPIs
§ RTT
NTN
KPIs for PS – RTT
Cell state at start of transfer should be CELL_DCH and the RAB with desired bit rates
should be already allocated
• 32 byte ping is not big enough to perform capacity upgrade
Stationary – Under
ONE cell!!
Maximum Normal
RTT @ 95% Stationary (UL/DL) Result Result Test Setup
PS RTT FACH 224 ms 300 ms 1 PS MOC UE
PS RTT 64/64 32 Byte 155 ms 170 ms 1 PS MOC UE
PS RTT 384/ 384 32 Byte 111 ms 140 ms 1 PS MOC UE
PS RTT 64 / HSDSCH 32 Byte 88 ms 115 ms 1 HSDPA 16QAM CAT 8 MOC UE
PS RTT 384 / HSDSCH 32 Byte 73 ms 90 ms 1 HSDPA 16QAM CAT 8 MOC UE
PS RTT EDCH / HSDSCH 32 Byte 50 ms 90 ms 1 HSPA CAT 8/5 MOC UE
RTT can be measured either by using Nemo Ping Script or with Command line, for example
• ping xx.xx.xxx.xxx (–w 3000) n 200 –l 32 >C:\temp
temp\Ping32B_B_HSPA.txt
When measuring ping RTT from FACH, note that scheduling period has an impact on 1 st RTT
• When measuring ping RTT from FACH, note that scheduling period has an impact on 1
(worst case ping as extended by a full RRI scheduling period)
(worst case ping as extended by a full RRI scheduling period)
KPIs for PS RTT
When starting Ping, the cell state at start of transfer should be CELL_DCH
and the RAB with desired bit rates should be already allocated
• 32 byte ping is not big enough to perform capacity upgrade
– Send first few bigger ping packet (or use e.g. FTP) to perform capacity upgrade
to required bearer, and then start ping with 32 byte before transfer to cell FACH
• Some optional features like throughput based optimisation (TBO) can
downgrade bearer due the low utilizations until minimum bitrate.
– This will happen with 32 byte ping if TBO enabled
– Either deactivate TBO or change minimum bitrate parameter = maximum bitrate
parameter during testing
• TBO and flexible upgrade can be also activated for HSDPA associated UL
return channel with parameter DynUsageHSDPAReturnChannel
DynUsageHSDPAReturnChannel
– This parameter is used to switch "On" and "Off" the Flexible Upgrade of NRT
Data Rate and Throughput Based Optimisation of the PS Algorithm
Data Rate and Throughput Based Optimisation of the PS Algorithm
KPIs for PS RTT
32 byte 1400 byte
350
HSDPA RTT result with 314
295
300
different UL bitrates
250
• 64/384/HSUPA
200
150 148
150
100 105
100 88
72 73
50
50
0
64 / HSDPA QPSK 64 / HSDPA 16QAM 384 / HSDPA QPSK 384 / HSDPA 16QAM HSPA
32 byte 1400 byte
800
701
700
RTT with different vendor UEs
600
542
• 64/64 bearer 525 519
500
400
300
180
200 159 150 159
100
0
Soc Classification level Nokia 6630 Motorola RAZR V3x Samsung SGHZ500 SonyEricsson K800i
KPIs for PS RTT
Cell load and coverage conditions has also impact on RTT
600
64 Byte Ping
500 512 Byte Ping
1024 Byte Ping
Round Trip Time (ms)
400
unloaded
loaded
300
200
100
0
70 80 90 100 105 110
CPICH RSCP (dBm)
RTT – Example from NTN NTN
results
Cell state at start of transfer was CELL_DCH and the RAB with desired bit rates was
already allocated
Round Trip Time ICMP payload size (Bytes)
1 32 1400
result
Bearer (UL/ DL kbps) target (ms) target (ms) result (ms) target (ms) result (ms)
(ms)
FACH 270 175 300 224
64 / 64 160 153 170 155 540 524
64 / 384 160 134 160 150 390 353
128 / 128 150 138 150 139 340 308
256 / 256 140 112 140 119 260 215
384 / 384 140 109 140 111 210 181
64 / HSDPA QPSK 115 96 115 100 360 314
64 / HSDPA 16QAM 115 83 115 88 360 295
384 / HSDPA QPSK 90 72 90 72 185 150
384 / HSDPA 16QAM 90 70 90 73 185 148
HSPA 100 54 110 50 185 105
Module 4 Content
– CS KPIs
– PS KPIs
§ RTT
NTN
KPIs for PS – NRT DCH (R99) Throughput
NRT DCH (R99) Throughput
• DCH Throughput test can be either stationary or mobility
• Besides of mobility, the File size and network parameters (e.g. Initial/Maximum
Bitrate) impact for the throughput
PS Release 99 throughput UL/DL
FPI_23 Average DL throughput Target Moving Target Stationary
PS 64 kbps 53 55
PS 128 kbps 115 118
PS 384 kbps 330 355
FPI_24 Average UL throughput Target Moving Target Stationary
PS 64 kbps 53 55
PS 128 kbps 115 118
PS 384 kbps 338 355
PS (I/B) – throughput – Example from NTN
results
FTP traffic was measured with different DCH bearers
• Cell state at start of transfer was Cell_DCH and desired bit rate was allocated.
Cell state at start of transfer was Cell_DCH
• Interactive traffic class was used.
– In an empty cell there was no difference between background and interactive
bit rate (kbit/s) test file size target (kbit/s) UL results (kbit/s) DL results (kbit/s)
8 100kB 7 7.1 7.4 Stationary

16 200kB 15 15.4 15.0
32 500kB 30 31.0 30.0
64 1MB 60 60.7 60.5
128 2MB 120 120.7 122.1
256 4MB 240 241.9 244.8
384 10MB 360 361.7 367.2
bit rate (kbit/s) test file size target (kbit/s) UL results (kbit/s) DL results (kbit/s)
64 1MB 58 60.9 60.2 Mobility

128 2MB 117 120.4 121.5
384 10MB 348 365.1 362.4
PS (I/B) – throughput – Result from Customer
Result from Customer
• Cell state at start of transfer was IDLE.
• Test performed in mobility, there are around 14 live sites along the mobility
routeincluding Flexi’s.
• The route covers motorway, A and B roads
• 10M file downloaded
bit rate test file target UL results DL results (kbit/s)
(kbit/s) size (kbit/s) (kbit/s)
Mobility
347.4 (90.47% of
384 10MB 345.6 N/A the bearer)
Main parameters:
InitialBitRateDL = 128kbps, InitialBitRateUL = 64kbps
MaxBitRateDLPSNRT = 384kbps , MaxBitRateULPSNRT = 384kbps
TrafVolTimeToTriggerDL= 5s, TrafVolTimeToTriggerUL
TrafVolTimeToTriggerUL= 1.2s
TrafVolPendingTimeDL= 800ms, MinAllowedBitRateDL= 32kbps
MinAllowedBitRateUL= 32kbps, ActivationTimeOffset = 600ms
KPIs for PS – HSPA Throughput
HSPA Throughput
Stationary
measurements
HSDPA throughput targets with different UE cats and with different network conditions
FPI_25 Average HSPA DL Throughput ; 15 HS
FPI_25 Average HSPA DL Throughput ; 15 HSDSCH codes, RLC size 336
Worst case scenario Normal scenario Best Scenario
Average CQI 10 14 26
EcNo 13 dB 11 dB 4 dB
RSCP 90..100 dBm 80..90 dBm 60..70 dBm
BLER 10% 10% 4 %
UE Type throughput targets for different scenarios (Stationary)
Cat 6 420 kbps 980 kbps 3,1 Mbps
HSUPA throughput targets (HSUPA 2M feature activated)
KPI Target
PS UL FTP throughput for Cat 4 6: Avg:>= 1.6 Mbps
6: Avg:>= 1.6 Mbps
EcNo 3..5 dB
HSUPA, 2 codes (Stationary)
HSPA Application level throughput
HSPA Application level throughput NTN
• During stationary measurements in NTN the CPICH Ec/No was
approximately between 3 dB and 5dB and CPICH RSCP between
5dB and CPICH RSCP between 60dBm
and 70 dBm.
UE type File size stationary mobile
Mbyte Result Result
QPSK, Cat. 12, 384 UL 25 1544
16QAM. Cat. 6, 384 UL 50 3242
16QAM. Cat. 8, EDCH UL 100 6453 3188
EDCH, Cat. 5 25 1612 1565
Mobility decrease the
throughput
HSPA throughput measurement with different
vendor UEs – NTN Measurements
NTN Measurements
Selected UE can impact for the throughput measurements.
Different vendor UEs behave differently
UE type forward channel return test file throughput

channel size (kbit/s)
HSDPA
Option Nozomi QPSK, 5 codes 384 25MB 1514
Sierra AC850 QPSK, 5 codes 384 25MB 1544
NoRM6 16QAM, 5 codes 384 50MB 3242
Novatel XU870 16QAM, 5 codes 384 50MB 3156
NoRM6 16QAM, 10 codes 384 100MB 6348
NoRM6 16QAM, 10 codes EDCH
DCH 100MB 6453
Option GT max 16QAM, 10 codes 384 100MB 6290
Option GT max 16QAM, 10 codes EDCH
DCH 100MB 6243
HSUPA
NoRM6 EDCH HSDSCH
DSCH 25MB 1612
Option GT max EDCH HSDSCH
DSCH 25MB 1621
HSPA throughput Result from Customer
Mono User Cell Centre Stationary
measurements
• Mono user cell centre HSDPA throughput results for different UE cats and
with different network conditions
• These tests are performed on a site which has 8E1s
• 20 samples are performed, the results presented are average values
PS DL Avg. FTP throughput for HSDPA; 15 HS
PS DL Avg. FTP throughput for HSDPA; 15 HSDSCH codes, Mono user, Cell Centre
Test Environment Target throughput / Throughput /
UE Type CQI Success Rate Success Rate
Stationary Cell
Cat 6 Nokia N95 Centre CQI=21.78 2800kbps / 98% 3123 kbps / 100%
Cat 8 Option GTMax / Stationary Cell
Non HSUPA data card Centre 5800kbps / 98% 5827kbps / 100%
Cat 8 Huawei HSUPA Stationary Cell
data card Centre CQI=24.19 5800kbps / 98% 5849kbps / 100%
Stationary Cell
Cat 12 Samsung Z630 Centre CQI=19 1300kbps / 98% 1506kbps / 100%
Packet session
Soc Classification level download success
Mono User Cell Border Stationary
measurements
• Mono user cell border HSDPA throughput results for different UE cats and
with different network conditions
PS DL Avg. FTP throughput for HSDPA; 15 HSDSCH codes, Mono user, Cell Border
Stationary Cell Border
Cat 6Nokia N95 CQI=13.24 900kbps / 98% 1287kbps / 100%
Cat 8Huawei HSUPA Stationary Cell Border
data card CQI=13.90 900kbps / 98% 2159kbps / 100%
Packet session
download success
HSPA Data + AMR User Cell Centre Stationary
measurements
• HSPA Data + AMR cell centre HSDPA throughput results for Cat 6 UE
• AMRWithHSDSCH is enabled
PS DL Avg. FTP throughput for HSDPA Data + AMR; 15 HS
PS DL Avg. FTP throughput for HSDPA Data + AMR; 15 HSDSCH codes, Cell Centre
Stationary Cell Centre 2800kbps/98% 2897 kbps / 100%
Cat 6Nokia N95 CQI=21 Call set
Call setup time<11s CST=6.07seconds
AMR call setup time with
simultaneous HSPA call
Multi User Cell Centre Stationary
measurements
• Multiuser cell centre HSDPA throughput results for different UE cats and with
user cell centre HSDPA throughput results for different UE cats and with
different network conditions
• 20 samples are performed
PS DL Avg. FTP throughput for HSDPA; 15 HSDSCH codes, Multi user, Cell Centre
Target throughput Throughput
UE Type Test Environment CQI Success Rate Success Rate
Stationary Cell Centre
Cat 6Nokia N95 CQI=24.65 2200kbps/98% 2252 kbps/100%
Cat 8Option GTMax Non Stationary Cell Centre
HSUPA data card CQI = 23.25 2200kbps/98% 2207kbps/100%
Cat 8Huawei HSUPA Stationary Cell Centre
data card CQI=23.82 2200kbps/98% 2227kbps/100%
Cat 12Samsung Z630 CQI=18.77 1100kbps/98% 1118kbps/100%
• MaxNbrOfHSSCCHCodes parameter is set to 3 to enable code multiplexing
• Code multiplexing is essential is to meet the committed targets
• PtxMaxHSDPA is set to 43dBm (NSN default = 37.8dBm and Orange UK default=39dBm)
• HSDPAinitialBitRateUL is set to 128kbps to minimise the initial delays
to minimise the initial delays
• SharedHSDPAFlowControlAllocation is set to 14Mbps
Multi User Cell Border Stationary
measurements
• Multiuser cell border HSDPA throughput results for Cat6 UE
user cell border HSDPA throughput results for Cat6 UE
• These tests are performed on two sites with 8E1s
• 20 samples are performed
PS DL Avg. FTP throughput for HSDPA; 15 HSDSCH codes, Multi user, Cell Border
Test Environment / Target throughput / Throughput /
Cat 6Nokia N95 CQI= 14.56 900kbps / 98% 1086 kbps / 100%
• PtxMaxHSDPA is set to 43dBm (NSN default=37.8dBm and Orange UK
is set to 43dBm (NSN default=37.8dBm and Orange UK
default=39dBm)
• HSDPAinitialBitRateUL is set to 128kbps to minimize the initial delays
• SharedHSDPAFlowControlAllocation is set to 14Mbps
Stationary
HSPA throughput Result from Customer measurements
HSUPA Mono & Multi User Upload Cell Centre
User Upload Cell Centre
• Mono and Multi user cell centre HSUPA throughput results for Cat 8 data
user cell centre HSUPA throughput results for Cat 8 data
card
PS UL Avg. FTP throughput for HSUPA; Mono & Multi user, Cell Centre
Target throughput / Throughput/
UE Type Test Environment Success Rate Success Rate
Cat 8Huawei Stationary Cell Centre
HSPA data card Mono User 1150kbps / 98% 1182kbps / 100%
Main user: 661kbps /100%
Stationary Cell Centre Load user 1: 670kbps
Cat 8Huawei Multi User Load user 2: 656kbps
HSPA data card 500kbps/98% Load user 3: 659kbps
•MaxTotalUplinkSymbolRate is set to 1920kbps
is set to 1920kbps
HSDPA > HSDPA Mobility Throughput
> HSDPA Mobility Throughput Mobility
measurements
• HSDPA>HSDPA mobility throughput and packet interruption time KPIs are
>HSDPA mobility throughput and packet interruption time KPIs are
measured
• 20 serving cell change samples are performed, the results presented are
average values
PS DL Avg. FTP throughput for HSDPA; 15 HSDSCH codes, Mobility measurement
Throughput/
Target throughput/ Success Rate/
UE Type Conditions / CQI Success Rate Mean IP Interruption
Cat 6Nokia N95 Mobility / CQI=15.7 1250kbps / 100%
Terminal (covering 2 sites) 1050kbps / 98% 738ms
Cat 8Huawei data Mobility/ CQI = 20.16 4472kbps / 100%
card (covering 2 sites) 1050kbps / 98% 762ms
• PtxMaxHSDPA is set to 43dBm (NSN default=37.8dBm and Orange UK
is set to 43dBm (NSN default=37.8dBm and Orange UK
default=39dBm)
HSPA throughput vs. CPICH RSCP
HSPA throughput vs. CPICH RSCP Lab
results
• In throughput vs. CPICH RSCP measurements the HSDPA channel initial CPICH
Ec/No ≥ 5 dB (Ec/No measured before HS
5 dB (Ec/No measured before HSDSCH allocation) and CPICH RSCP
level was controlled with attenuators from
level was controlled with attenuators from 55 dBm to 110 dBm, step size 5dB.
• The Shannon limit curve assumes 6 dB UE noise figure and includes 5 dB margin
for coding, receiver estimation and for link adaptation
FTP throughput vs CPICH RSCP HSUPA
QPSK 5 codes
7000 QAM 5 codes
QAM 10 codes
6000 Shannon limit
FTP throughput
5000
4000
3000
2000
1000
0
55 60 65 70 75 80 85 90 95 100 105 110
CPICH RSCP
HSPA throughput vs. CPICH Ec/No
HSPA throughput vs. CPICH Ec/No Lab
results
• In throughput vs. CPICH Ec/No measurements the HSDPA channel
CPICH Ec/No was controlled with PROPSim internal interferer from 5 dB
CPICH Ec/No was controlled with PROPSim internal interferer from
to 15 dB, step size 2dB.
Throughput vs CPICH Ec/No
7000
6000
HSUPA
5000
QPSK 5 codes
4000
kbit/s
3000 QAM 5 codes
2000 QAM 10 codes
1000
0
3 5 7 9 11 13 15
Ec/No dB
Lab/NTN
Throughput comparisons results
Field measurement result and from NTN under very good network conditions
• Average CPICH RSCP 68.4 dBm and Average CPICH Ec/No
68.4 dBm and Average CPICH Ec/No 4.9 dB (unloaded)
Lab results are from RAS06 KPI measurements (very high CQI and stationary)
HSDPA performance is much more HSUPA results are marginally worse than those
affected by mobility than HSUPA from laboratory measurements (note that field
measurement done in very good conditions also)
HSDPA throughput comparison HSUPA throughput comparison
7
6.45 1.8
1.58 1.62
6 1.6
1.4
5
1.15 1.18
1.2
4
Mbps
Mbps
3.51 Field 1
3.24 Field
Lab
3 0.8 Lab
2.25
0.6
2 1.54
1.27 0.4
1 0.2
0 0
HSDPA Cat.12 HSDPA Cat.6 HSDPA Cat.8 HSUPA Cat.3 HSUPA Cat.5
HSDPA Cat. 8 – Throughput vs. CQI (NTN)
Throughput vs. CQI (NTN) NTN
results
T hroughput vs CQI
6000000
5000000
4000000
bps
3000000
2000000
1000000
0
11 13 15 17 19 21 23 25 27
CQI
HSUPA in Microcell
ETFCI (119)
Serving grant
AG used when
RSCP ~ 26 dBm AS>1
UE tx pwr
Relative Grant
•Blue hold
Thput OK
•Yellow – up
•Red Down
when “too” close to the
BTS UL power control
cannot always decrease
power enough, so HSUPA
scheduler try to increase
and decrease thput
HSUPA – Absolute Grants vs. UE Tx Power
Absolute Grants vs. UE Tx Power
When UE tx power increase Limited by UE tx power
and start to limit thput there
is more Absolute Grants
given to the UE. BTS
reduce aggressively the
throughput and therefore
AG are used
RED= AG
Yellow =ETFCI
68
BLUE= SG
© Nokia Siemens Networks Presentation / Author / Date
Module 4 Content
NTN
Standard Acceptance Reports
Ready made and standardised Actix and Nemo Analyzer reports can be
used to analyse Field measurement results and KPIs
• No need to create own reports for each projects
• Results are comparable between the projects
Following Reports available for Actix (Nemo Analyzer reports available later)
• CS Reports
• PS R99 Reports
• HSPA Reports
Standard Acceptance reports can be found
https://sharenetims.inside.nokiasiemensnetworks.com/Open/362255054
ims.inside.nokiasiemensnetworks.com/Open/362255054
HSDPA Report Example
Actix and Nemo Analyzer
• Current Actix version GA11 has limited support for HSUPA, so it is
recommended to use Nemo Analyze instead for basic optimization work.
• Also using Actix Analyzer requires ALWAYS dedicated/modified
workbooks. The default analysis in Actix doesn’t provide reliable results.
• Existing and evolving analysis for Actix can be found from:
https://sharenetims.inside.nokiasiemensnetworks.com/Open/362255054
ims.inside.nokiasiemensnetworks.com/Open/362255054
• NSN specific customized analysis for Nemo Analyze are to provided during
2H/2008. Already today it is possible to customize KPIs in Nemo Analyze,
but in larger scale (NSN standard reports) it should be possible with the
but in larger scale (NSN standard reports) it should be possible with the
release of version 5.11.
Detail failure analysis
Using acceptance reports, failure type and locations can be identified
• Based on filename and failure time, detail failure analysis can be done
Based on filename and failure time, detail failure analysis can be done
Measurement file
name and time of
the failure
Module 4 Content
– Call Setup Failure Analysis
– Drop Call Analysis
Appendix RAS06 HSPA field measurements in NTN
RAS06 HSPA field measurements in NTN
Drive test Analysis Process
Drive test Analysis Process
NonGenuine Call Setup Failures
Genuine Call Setup Failures
Measurement systems are often not perfect and may introduce errors in data
collection or analysis.
• Examples of nongenuine failures seen:
genuine failures seen:
•Drive Test tool
– Uplink: CM Service Abort within milliseconds from
within milliseconds from CM Service Request
– Call attempt during Location Area update (‘LA clash’)
Call attempt during Location Area update (
– User initiated “UL CC Disconnect”
• Analysis Workbook
– Location Area update interpreted as call setup failure
– Cell reselection back to 3G from 2G interpreted as call setup failure
Cell reselection back to 3G from 2G interpreted as call setup failure
NonGenuine Drop call failures
Genuine Drop call failures
Measurement system failure examples:
• Drive test tool
– User initiated “UL CC Disconnect” ”
• Analysis Workbook
– InterRat cell reselection from 2G to 3G interpreted as drop call
Rat cell reselection from 2G to 3G interpreted as drop call
– Complete (e.g. 90 seconds) call on either 3G or 2G
– No drop in the log file / same drop listed twice
No drop in the log file / same drop listed twice
Genuine Call Setup Failure Scenarios
• RF issue
– Interference / Dominance / Coverage
– Missing neighbour
• System Issue BTS
– No response to “RRC Connection Request”
– “RRC Connection Reject” to “RRC Connection Request”
to “RRC Connection Request”
• System issue RNC
– “CC Disconnect” after “Call Proceeding” due to “DL RRC Connection
“CC Disconnect” after “Call Proceeding”
Release”
• Core NW
– “CM Service Abort” after “CM Service Request”
• System issue (test number)
– “CC Disconnect” after “CC Progress”
“CC Disconnect” after “CC Progress”
Genuine Drop Call Scenarios
RF issue
• Interference / Dominance / Coverage
• Missing Neighbours
System issue BTS
• Sudden “CC Disconnect” due to “DL RRC Connection Release”
due to “DL RRC Connection Release”
• Sudden drop to idle, no disconnect messaging
System issue RNC
• Sudden “CC Disconnect” due to “DL RRC Connection Release”
due to “DL RRC Connection Release”
Failure Location
• Analyse the
signalling
flow to find
the location
of failure and
potential
cause
• UE log may
only capture
some of the
messages
Module 4 Content
AMR CS Call Phases
UE BTS DRNC SRNC CN
1. Cell search, BCCH
decoding & RACH access
2. RRC Connection Setup
3. UE <> CSCN signalling
4. RAB Setup
5. UE <> CSCN signalling
6. Service Established
7. Branch addition/deletion & active set update
7. Branch addition/deletion & active set update
8. Service Released
Call Setup Failure Start
Analysis Process Best server’s Coverage Optimization

No
RSCP>102dBm
102dBm
Missing No
Yes Dominance Optimization
Neighbour ?
Best server’s
Ec/No>12dB
12dB
No
A Yes
Neighbour list Optimization
Yes
UL coverage & RACH
B parameter. Optimization
(changing serving cell)
AICH(ACK)
received?
No
Report & Finish
(Check failure cause)
Yes
“RRC Connection
Setup” received?
No “RRC Setup
Reject” received? C
Yes
Yes Yes AC optimization
(check PrxNoise&
Report & Finish “RRC Connection interferer around BTS)
D (Reason of problem:
L1 sync fail)
No
Setup Completed” sent
from UE?
Report & Finish
Yes
Report & Finish “Radio Bearer setup
Radio Bearer setup Yes Report & Finish
No
(Check failure cause) Check failure cause
failure”Received?
(Not radio problem/cell update)
E
Call Setup Failures – RF issues
RF issues A
• RF issue? Coverage/Interference/Dominance problems
Coverage/Interference/Dominance problems
• Search failures related to missing neighbour Missing 2G or 3G neighbour
Search failures related to missing neighbour
analysis over the whole route
See the example in Module 3
See the example in Module 3 – RF Optimisation
Call Setup Failures – Random Access Process
Random Access Process B
UE WBTS RNC
Random Access process is working
adequately if AI (Acquisition indicator) Preamble/RACH
has been received through DL AICH
Acquisition Indicator/AICH
If AICH was not received by UE, the
cause of the problem can be classified
RRC: RRC Connection Request/PRACH
into:
NBAP: RADIO LINK SETUP REQUEST
•Inadequate RAN parameter related to NBAP: RADIO LINK SETUP RESPONSE
Random Access: RAN parameter settings
for preamble transmission or open loop RRC: RRC CONNECTION SETUP/FACH
power control information is not correct.
L1 Synchronisation
•UL Coverage limit: UL coverage of UE is
smaller compared to serving cells DL NBAP: SYNCHRONISATION INDICATOR
coverage so that UE’s Tx power cannot
reach serving cell. RRC: RRC CONNECTION SETUP COMPLETE/DCH
UE in CELL_DCH state
Solutions for RACH optimisation
Max UE Tx power hit No To increase PRACH_Preamble_retrans

the UE_P_MAX(24dBm)? Or PowerRampStepPRACHPreamble
Yes
Is UL Interference Yes Report there might be an interfering

abnormally HIGH? source Nearby the serving cell
No
Change the Serving cell to cover the problem Area
=> UE is too far to reach the serving cell
The Basic theory for RACH setup procedure and planning parameters can
Soc Classification level be found in Module 6 – Parameter Optimisation
Parameter Optimisation
Open loop Power Control
parameters from RACH Info
message
RACH Info
Call Setup Failures – System Issue BTS
System Issue BTS C
No response to “RRC Connection Request
RRC Connection Request”
• Good RF conditions
• Wrong MHA settings or cable loss settings can cause the site not to “hear” the UE
Wrong MHA settings or cable loss settings can cause the site not to
• PrxNoise statistics, receive link parameters and HW units to be checked (faulty
MHA, wrong MHA parameters, wrong cable / feeder loss parameters, faulty units)
Call Setup Failures – System Issue BTS
System Issue BTS C
“RRC Connection Reject” after “RRC Connection Request
RRC Connection Request”
• Admission Control can reject too many (or admit too many) connection
requests due to wrong PrxNoise measurements.
• PrxNoise statistics, receive link parameters and HW units to be checked
Call Setup Failures – Radio Capacity
Radio Capacity C
UE has the appropriate DL/UL coverage but if RNC does not allow to set up
the RRC connection of the requested RAB (Radio Access Bearer), Call
setup will fail.
• Admission Control (AC) is involved in RRC connection setup.
• AC can reject RRC reject RRC connection Setup due the DL load, UL load or DL
Spreading codes
• During the preoptimization phase it is unlikely that AC will stop an RRC
optimization phase it is unlikely that AC will stop an RRC
connection setup during the drive testing because there are normally very few UEs
in the network. (Traffic loading is trivial)
However, it should be checked that measured PtxTotal and PrxTotal are less
than PtxTarget (e.g. 40dBm) and PrxTarget (e.g. 4dB, 60% loading)
respectively.
• If DL AC does not allow RRC setup check the Tx power of WBTS, # of channels
does not allow RRC setup check the Tx power of WBTS, # of channels
transmitted, Signaling messages.
• If UL AC does not allow RRC setup: Check out if there is an interfering source
does not allow RRC setup: Check out if there is an interfering source
nearby the serving cell.
Call Setup Failures – L1 sync
L1 sync D
To check if Layer 1 Synchronization (slot/frame sync) has failed
• If “RRC Connection Setup” was received by UE but UE does not send
“RRC Connection Setup Completed”, we will report “L1 synchronization
failure” and have to check L1 system messages.
UE receive RRC
Connection setup
message but is not
sending RRC
Connection Setup
complete message
Call Setup Failures – System Issues RNC
System Issues RNC E
“CC Disconnect” after “Call
Proceeding”
• Failures in RAB setup
occur between the “RAB
Assignment Request”
being received from Core
Network and the RAN
sending out Radio Bearer
Setup. Therefore the
failure is between BTS and
Core Network.
Call Setup Failures – System Issues RNC
System Issues RNC E
“CC Disconnect” after “Call
Proceeding” (cont.)
Site shows high values on counter
“RAB_STP_FAIL_CS_VOICE_BTS”
during the drive test, in the recent
check the counter showed no failures
check the counter showed no failures
Call Setup Failures – Core NW
Core NW E
• “CM Service Abort” after “CM
Service Request”
• “Security Mode Command”
message not received by UE,
thus the failure is believed to
be at Core Network.
UE Node B RNC MGW
RRC Connection Establishment
Initial Direct Transfer (CM Service Request) SCCP: Connection Request
SCCP: Connection Confirm
Location Reporting Control
Common ID
Security Mode Command
Call Setup Failures – System issues (test Number)
System issues (test Number) E
“CC Disconnect” after “CC Progress”
• Cause: recovery on timer expiry
• The call goes via IN SCP to a
recording.
• A static test was done by Nokia
Customer Care and in few instances
the call dropped after 30 seconds of
recording passed. Hence the problem is
associated with the test number not the
RAN
Cause: recovery
on timer expiry
Module 4 Content
Call drop analysis process
Start
SHO
Failure Yes SHO Failed
Analysis
No
ISHO Yes
Failure ISHO Failed
Analysis No
No
Best server’s No
Coverage Optimization
RSCP> 102dBm
Missing No
Dominance Optimization
Neighbour
Best server’s
Ec/No> 12dB Yes Neighbour list
B
Investigate possible
BTS or RNC
A Optimization
problem
Call Drop Analysis process
Call Drop Analysis process – SHO Analysis
Start
Check Iur Yes
Inter RNC HO
Check neighbor definition parameters
No
Yes No DL ASU

Fix SC Clash SC Clash
C No
received
Yes
Load Yes Congestion No

UE Tx
Optimisation on target cell Check RF Levels
Power Max
No Yes
DL Tx No Load Optimisation/

Uplink Yes
Power Max Interference External Interferer
Yes No
D
CPICH Optimisation
Link Yes
Unbalanced
No
Drop call failures – RF issue
RF issue A
RF drops mostly due to poor
dominance or interference
Poor coverage could lead to ISHO,
although poor dominance or
interference can cause ISHO to fail.
Rapid field drop can cause drop due
to coverage
Poor dominance or interference can
cause Compressed Mode (CM) to
start even if RSCP is still good.
In CM UE transmits with higher
power (more interference) and
spends less time on 3G (less
accurate measurement reporting)
Poor dominance or interference can
lead to Active Set update failures Poor dominance
and eventually to drop call. causes Active Set
update failures
RF issue A
DL synchronisation is lost >
UE has stopped transmitting
TrChAgg and DL
DPCCH BER high
RF issue A
Fairly good
CPICH Pilot
EcNo
Transport Channel
BER. Btw UE<
BER. Btw UE<
>RNC (MAC layer)
Sometimes DPCCH BER (btw UE<>WBTS)
can be a better indicator of what's happening to
the dedicated channel than the CPICH EcNo, in
particular in the case that power control may not
be tracking well
Drop Call Failures – System issue BTS
System issue BTS B
Sudden drop to idle, no disconnect messaging
• Site malfunctions to be checked
• In the example below site had faulty unit (WTR)
Drop to IDLE
Drop Call Failures – System Issues RNC
System Issues RNC B
DPCCH
“CC Disconnect” due to BER
“DL RRC Connection
Release”
No response to UL
Measurement Reports
In the example site had no
alarms, good RF & BER
Not able to add SC265 to
Active Set, next call on the
same cell => no failure.
Difficult to troubleshoot if
the failure does not
happen systematically =>
follow up in the next
weeks drive / do a
separate drive test in the Sudden “RRC
area Connection Release”
Drop call failures (SC conflict) C
Sudden drop to idle Transport
mode (no disconnect channel
messaging) BLER 100%
Cause of the failure:
overshooting site and
SC reuse
Short term solution to
add overshooting
neighbour in ADJS
definitions
Cell ABC, SC258
Drop call failures – Uplink Interference
Uplink Interference D
UL interference from the
SIB7 message
Drop call failures – Link Balance
Link Balance D
UL & DL Power Control commands can UE RX power control
help indicating problems in link balance. message: DL reception
weak > UE is ordering
PC frequency is 1500 Hz, thus ideally the WBTS to increase power.
sum of PC commands to increase or
decrease power is 1500
E.g. if the sum of UL PC commands is <
1500, this would indicate UE is starting to
loose synchronization
in Compressed Mode there is less PC
commands, UE spends time on 2G
Sum of UL PC commands
< 1500, UE not receiving
all the PC commands.
Drop call failures – System issue RNC or BTS ?
System issue RNC or BTS ?
“CC Disconnect” due to “DL RRC Connection Release
DL RRC Connection Release” is just a
consequence of failure which can be due to different reasons
• From UE point of view L3messaging does not identify the point of failure
messaging does not identify the point of failure
distinctly
• BTS or RNC failure? => Suspect BTS first, then RNC
Rule out BTS failures
• Check the site performance from Counters (Iub, Service level, cell resources SHO,
etc) and that site is carrying traffic
• PrxNoise, receive link parameters, alarms
• SC–reuse
• UE performance ?
Identified causes for Active Set Update failure
Identified causes for Active Set Update failure
• “Deaf” sites (PrxNoise)
• Faulty HW
• SCreuse
Appendix
RAS06 HSPA field performance
Measurement results from Nokia Test Network
Measurement results from Nokia Test Network
Kirsi Teräväinen
Network Configuration
HSDPA and HSUPA mobility measurement were done in NTN under RNC 4 and 8
• all sites HSPA enabled
2 x 4 x 1 x 4 x
• Makkyla is 2+2, HSPA enabled in the E1 E1 E1 E1
Kilonkallio IBM Perkkaa Sello
second layer only WBTS WBTS WBTS WBTS
– DRRC used to redirect UEs to the F2 2 x 4 x

E1 E1
InterRNC Hanover included Mäkkylä Hippos
Flexi Flexi
WBTS WBTS
SäPo
WBTS
STM1
STM
Note ! There was very little other SAXC
1
RNC8
RNC
traffic in the network during SäPo 2 x STM1 4
SäPo
measurements
2*STM1
MGW
SAXC SD
H SAXC
SGSN
Measurement setup
Nemo Outdoor with Merlin X950 data card was used
• HSDPA 4M Download
• HSDPA 100M download
• HSUPA 2M Upload
Merlin X950D
• Same measurement route used • HSDPA Cat 8 terminal
• HSUPA Cat 5 terminal
• 16QAM modulation
• Support a max of 10 codes
• Max theoretical throughput
~7.2 Mbps
SUPPORTED BY NEMO
CPICH EcNo and RSCP statistic 4M HSDPA
download
Best Active Ec
Best Active Ec/No
100
90
Percentage (%)
80
70
60
50
Average CPICH Ec/No 6.2 dB
40
30
20
10
0
25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
Ec/No (dB
dB)
RSCP during
Average CPICH RSCP
Average CPICH RSCP 73.3 dBm
measurement route
RNC 8 RNC 4 RNC 8
HSDPA Results
HSDPA Cat. 8 CQI statistics
CQI statistics 4M HSDPA
download
Channel Quality Indicator
Channel Quality Indicator (CQI)
100
90
Percentage (%)
80
70
60
50
40
30
20
10
0
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30
CQI
HSDPA – Throughput 4M Download
Throughput 4M Download
Cat 8. 16QAM, 10 codes, 7.2 Mbps
HSDPA 4M
Modulation
100%
80%
60%
40%
20%
0%
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0

00
50
00
50
00
50
00
50
00
50
30
35
40
95
10
15
20
25
45
50
55
60
65
70
75
80
85
90
12
12
13
10
10
11
11
13
14
s
16QA M QPSK N/A
HSDPA – Throughput 100M Download
Throughput 100M Download
Inter
RNC
HSPA on
Inter second
RNC layer
Between
the calls Between
Modulation
the calls
100%
80%
60%
40%
20%
0%
0 50 100 150 200 250 300 350 400 450 500 550 600 650 700 750 800 850 900 950 1000
s
16QA M QPSK N/A

HSDPA – Throughput statistic (4M & 100M)
Throughput statistic (4M & 100M)
Downlink Application Throughput
100
90
HSDPA 4M
Percentage (% )
80
70
Average 2034,3
60
50 Maximum 4215,5
40 Threshold >=400 90.6%
30
20
10
0
0 20 0 400 600 800 10 00 1 200 1400 1600 1800 2000 2200 240
240 0
0 26 00 2800 3000 3200 3400 3600 3800 400 0 4 200 4 400 4600 4800
Throughput (kbps)
Downlink Application Throughput
100
90
HSDPA 100M
Percentage (% )
80
70
60 Average 1872,1
50
Maximum 4365,7
40
30 Threshold >=400 85.6%
20
10
0
0 20 0 400 600 800 10 00 1 200 1400 1600 1800 2000 2200 240
2200 0 26 00 2800 3000 3200 3400 3600 3800 400 0 4 200 4 400 4600 4800
Throughput (kbps)
Application thput vs. RSCP
Application thput vs. RSCP
HSDPA 4M
HSDPA 100M
HSDPA – Link Adaptation 4M HSDPA
Cat 8. 16QAM, 10 codes, 7.2 Mbps download
HSDPA Number Of Multicodes
HSDPA Number Of Multicodes
4 5 6 8
1 2
1 0,0 0,0%
2 14,7 4,1%
4 9,4 2,6%
5 1,6 0,4%
6 12,4 3,5%
8 11,8 3,3%
10 306,0 86,0%
10
Total
Total: 355,7 100,0%
HSDPA Transport Block Size
100
90
TBS average = 7984
Percentage (%)
80
70 TBS Maximum= 13904
60
50
40
30
20
10
0
0 800 1600 2400 3200 4000 4800 5600 6400 7200 8000 8800 9600 10400 11200 12000 12800 13600
Block size (bits
bits)
HSUPA Results
HSUPA – throughput & Tx Power
throughput & Tx Power
Cat 5 QPSK, 2 x SF2, 2 Mbps
QPSK, 2 x SF2, 2 Mbps
Tx Power average = 7 dBm
Tx Power Maximum=23 dBm
HSUPA – data rate limitations
data rate limitations
• HSUPA data rate can be limited by
– UE Tx Power – UE is already using its maximum Tx power
UE is already using its maximum Tx power
– Serving Grant – Maximum grant is used already
Maximum grant is used already
– Data – UE buffer is empty – no new data to send
no new data to send
Limitation of HSUPA data rate
100%
80%
60%
40%
20%
0%
0 50 100 150 200 250 300 350 400 450 500 550 600 650 700 750 800 850 900 950
s
Pow er Grant Data
HSUPA Performance
HSUPA – Throughput statistics
Throughput statistics
Average
throughput
1.38 Mbps
Average 1375,3
Maximum 1926,8
HSUPA – Link adaptation
Elapsed time 5min 38s
Spreading code(s) Percentage of total time
Percentage of total time
SF 256 0.5%
SF 32 6.7%
SF 16 2.3%
SF 8 0.8%
SF 4 3.9%
2 * SF 4 6.6%
2 * SF 2 79.3.0%
Module 4 – Drive Test KPIs and Analysis
Drive Test KPIs and Analysis
Summary
• Services to be measured and KPIs to be calculated need to
be clearly defined
• Various call patterns exist to exercise the KPIs
• Reporting Levels should be understood
• Define and agree exceptions in advance
Define and agree exceptions in advance
Version control
Version Date Status Owner
RAN04 2006 Base version Mike Roche, Steve

Hunt, Gareth Davies,
Pekka Ranta
RAS051_v1.0 24. 04. 2007 Example case available Kirsi Teräväinen
Minor changes checked for
RAS051 level
RAS06_v1.0 7.7.2008 Overall content changed Kirsi Teräväinen
• RAS06 KPI targets/results and
definitions added
•Test Equipment and setup
added + Network configuration
and parameters

Drive Test KPI and Analysis

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Drive Test KPI and Analysis

Hochgeladen von

Copyright:

Verfügbare Formate

3G RANOP 1

Cluster Data Preparation Data Analysis Trouble

6 5 16­QAM 4.8 3.5

1 st activate PDP UE wait 30 sec before

Features QPSK 16­QAM + 15 code + 10 Mbps 14.4 Mbps 14.4 Mbps 14.4Mbps

Modulation QPSK 16­QAM 16­QAM 16­QAM 16­QAM 16­QAM

UE category Cat 11­12 Cat 6 Cat 7­8 Cat 9­10 Cat 9­10 Cat 9­10

Number of HS­PDSCH codes 5 5 10 15 8 7

Air interface bit rate (Mbps) 2,4 4,8 9,6 14,4 7,68 6,72 14,4

Max. transport block size (bits) 3630 7298 14155 20251 14936 13177

Max. transport channel (MAC­d flow) bit rate (Mbps) 1,815 3,649 7,0775 10,1255 7,468 6,5885 14,0565

RLC PDU (bits) 336 336 336 336 336 336

RLC blocks/TTI 10 21 42 60 44 39

RLC bit rate (Mbps) 1,68 3,528 7,056 10,08 7,392 6,552 13,944

PI # FPI Name Triggering Test Setup

FPI_12 SHO Overhead 100*(Ave AS Size ­1)%. N/A N/A *

UE Node B RNC CN

Radio Link Deletion Request

CS video Call setup time (s) SRB3.4 SRB13.6

UE Node B RNC CN

RRC Connection Setup (FACH)

RRC Connection Setup Complete (DCH)

DIRECT TRANSFER (authentication and ciphering response) PS attach time

Security mode command

Downlink direct transfer: common id

UE Node B RNC CN

RRC Connection Setup (FACH)

Security mode command

RRC: Radio Bearer Setup Complete

PS RTT FACH 224 ms 300 ms 1 PS MOC UE

PS RTT 64/64 ­­32 Byte 155 ms 170 ms 1 PS MOC UE

PS RTT 384/ 384 ­­32 Byte 111 ms 140 ms 1 PS MOC UE

PS RTT 64 / HS­DSCH ­­ 32 Byte 88 ms 115 ms 1 HSDPA 16QAM CAT 8 MOC UE

PS RTT 384 / HS­DSCH ­­32 Byte 73 ms 90 ms 1 HSDPA 16QAM CAT 8 MOC UE

PS RTT E­DCH / HS­DSCH ­­32 Byte 50 ms 90 ms 1 HSPA CAT 8/5 MOC UE

8 100kB 7 7.1 7.4 Stationary

32 500kB 30 31.0 30.0

64 1MB 60 60.7 60.5

128 2MB 120 120.7 122.1

256 4MB 240 241.9 244.8

384 10MB 360 361.7 367.2

bit rate (kbit/s) test file size target (kbit/s) UL results (kbit/s) DL results (kbit/s)

64 1MB 58 60.9 60.2 Mobility

384 10MB 348 365.1 362.4

UE type File size stationary mobile

Mbyte Result Result

QPSK, Cat. 12, 384 UL 25 1544 ­

16­QAM. Cat. 6, 384 UL 50 3242 ­

16­QAM. Cat. 8, E­DCH UL 100 6453 3188

E­DCH, Cat. 5 25 1612 1565

UE type forward channel return test file throughput

UE BTS DRNC SRNC CN

Analysis Process Best server’s Coverage Optimization

Max UE Tx power hit No To increase PRACH_Preamble_retrans

Is UL Interference Yes Report there might be an interfering

UE Node B RNC MGW

Yes No DL ASU

Load Yes Congestion No

DL Tx No Load Optimisation/

– DRRC used to redirect UEs to the F2 2 x 4 x

RNC 8 RNC 4 RNC 8

16QA M QPSK N/A

16QA M QPSK N/A

Pow er Grant Data

6 5 16QAM 4.8 3.5

Features QPSK 16QAM + 15 code + 10 Mbps 14.4 Mbps 14.4 Mbps 14.4Mbps

Modulation QPSK 16QAM 16QAM 16QAM 16QAM 16QAM

UE category Cat 1112 Cat 6 Cat 78 Cat 910 Cat 910 Cat 910

Number of HSPDSCH codes 5 5 10 15 8 7

Max. transport channel (MACd flow) bit rate (Mbps) 1,815 3,649 7,0775 10,1255 7,468 6,5885 14,0565

FPI_12 SHO Overhead 100(Ave AS Size 1)%. N/A N/A

PS RTT 64/64 32 Byte 155 ms 170 ms 1 PS MOC UE

PS RTT 384/ 384 32 Byte 111 ms 140 ms 1 PS MOC UE

PS RTT 64 / HSDSCH 32 Byte 88 ms 115 ms 1 HSDPA 16QAM CAT 8 MOC UE

PS RTT 384 / HSDSCH 32 Byte 73 ms 90 ms 1 HSDPA 16QAM CAT 8 MOC UE

PS RTT EDCH / HSDSCH 32 Byte 50 ms 90 ms 1 HSPA CAT 8/5 MOC UE

QPSK, Cat. 12, 384 UL 25 1544

16QAM. Cat. 6, 384 UL 50 3242

16QAM. Cat. 8, EDCH UL 100 6453 3188

EDCH, Cat. 5 25 1612 1565