WCDMA Service Performance: Nokia Expert Club

WCDMA Service
Performance
Nokia Expert Club
Atte Artamo and Martin Kristensson,
Strategy & Technology,
Nokia Networks,
April 4-5, 2006.
NOKIA 2006 WCDMA Service Performance.ppt/ AAr & MKr

Outline
1. Introduction
2. Setup times
Bearer/Application setup times
Packet round trip times
3. Seamless mobility
4. Bit rates
Sustainable bitrates
UL/DL coverage and bitrates
5. Application & terminal aspects
6. Summary

Introduction
-Study items in service performance
- Important service performance
properties

How Is Application Performance
Studied?
How to make it work in
How to make it work at the network at low load!
high network load? Application
Performance -Requirements
- Multiple users -Single user/appl.
- QoS Differentiation - Network bottlenecks
- Cost efficient deployment - Lower layer dependence
Network
Performance
Quality of Service
Monitoring
And Capacity
Does the network and applications

perform as planned?

How to Improve the Application
Performance?
1. Short bearer and application setup times
2. Low end-to-end packet round trip time
3G
3. Seamless mobility 2
G
4. Sustainable bit rates and end-user

throughput also in loaded networks
5. Uplink and downlink coverage
6. Terminal processing power, application

intelligence, power consumption

Bearer/Application Setup
Times
-How is the browsing application launched
e2e?
- How to speed up browsing?

What Happens During the First Page
Download?
Typical web page (100kB) with 384 kbit/s WCDMA

connection
PDP
GPRS TCP
(RAB TCP steady state Rendering
attach synch.TCP
setup)
slow
start
2-3s 2-3s 0.4s 0.6s 2s 1-2s Time

Setup Times: RAN 1.5 vs RAN04 for
RAB setup
Measured benefits
A 30% decrease in download
times for the first page 1st XHTML measured
Improvement obtained page
12
without increasing bit rates (100 kB) download time
10 [s] ~ 30%
or transport capacity! faster
8 download
How are the improvements
gained? 6
Improvements are part of 4
RAN04 operating software 2
Faster bearer setup times
0
Seamless bearer upgrades
RAN1.5 RAN04
Shorter packet round trip
times
KEY RAN 04 improvements:
New SRB sets, AAL2 reconfiguration, 10 ms TTI

Setup times: Time to setup a PS RAB 64/128 in
RAN04
KEY settings:
~3s gain Always on

PDP context
CELL PCH
No Attach Attach Attach Attach

No PDP No PDP PDP PDP
Cell IDLE Cell IDLE Cell IDLE Cell PCH

Packet Round Trip Times
Packet round trip time and bit rate
-
evolution
- What round trip times are needed?
- How do round trip times affect to TCP?
- What can WCDMA achieve?

Why Is Packet Round Trip Time
Important?
TCP slow
Bit rate start: 2-5 RTTs Max bit rate
used only after
Download with TCP slow start
long round trip
time
1 2 3 4 Time
Download with Faster download

short round trip even if the
time 1 2 3 4 maximum bit rate is
not increased
1 DNS query 3 TCP slow start

2 TCP 4 Max bit rate
establishment

Packet Round Trip Time and Bit Rate
Evolution
3.9G
5-20 Mbps
<30ms
End user bit
rate
[kbps]
HSPA
3 1-2 Mbps ADSL
Mbps <50ms 1-2 Mbps
<50ms
1
Mbps WCDMA, R99
200-300kbps
300 EGPRS, Rel. 99 150-200ms
kbps EDGE Evolution
100-200kbps
500-700ms 200-300kbps
100 <100ms
kbps EGPRS, Rel. 4
GPRS 100-200kbps
30 500-700ms 200-500ms
kbps 40kbps
600 500 400 300 200 100 0

Round trip time [ms]

How Do End Users Experience
Different RTTs?
How Is End User Experience Dependent on Round Trip
Time for and 128 kbit/s and 1 Mbit/s connection?
5 Not noticeable
EDGE R4
HSDPA
4 OK, but
noticeable
MO EDGE R99
S 3
Slightly annoying
2 Annoying
128 kbit/s
1 Mbit/s
1 Very annoying
0 200 400 600

Round Trip Time [ms]
What is the Round Trip Time in a Real
Network?
WCDMA/DC
H WCDMA/HS-
DCSH
128/384
kbps
Pinging 10.20.143.142 with 32 bytes of data:
Pinging 212.213.204.98 with 32 bytes of data: Reply from 10.20.143.142: bytes=32 time=69ms TTL=62
Reply from 10.20.143.142: bytes=32 time=78ms TTL=62
Reply from 212.213.204.98: bytes=32 time=139ms TTL=253 Reply from 10.20.143.142: bytes=32 time=67ms TTL=62
Reply
Reply
from
from
212.213.204.98:
212.213.204.98:
bytes=32
bytes=32
Fastest
time=126ms
time=135ms
TTL=253
TTL=253
Reply
Reply
from
from
10.20.143.142:
10.20.143.142:
bytes=32
bytes=32
time=75ms
time=73ms
TTL=62
TTL=62
Reply
Reply
from
from
212.213.204.98:
212.213.204.98:
bytes=32
bytes=32 individual
time=134ms
time=133ms
TTL=253
TTL=253
Reply
Reply
from
from
10.20.143.142:
10.20.143.142:
bytes=32
bytes=32
time=82ms
time=70ms
TTL=62
TTL=62
Fastest
Reply
Reply
from
from
212.213.204.98:
212.213.204.98:
bytes=32
bytes=32
time=132ms
time=130ms
TTL=253
sample 125 ms
TTL=253
Reply
Reply
from
from
10.20.143.142:
10.20.143.142:
bytes=32
bytes=32
time=79ms
time=67ms individual
TTL=62
TTL=62
Reply
Reply
from
from
212.213.204.98:
212.213.204.98:
bytes=32
bytes=32
time=128ms
time=127ms
TTL=253
TTL=253
Reply
Reply
from
from
10.20.143.142:
10.20.143.142:
bytes=32
bytes=32
time=78ms
time=76ms
sample 67 ms
TTL=62
TTL=62
Reply
Reply
from
from
212.213.204.98:
212.213.204.98:
bytes=32
bytes=32
time=129ms
time=128ms
TTL=253
TTL=253
Average Reply
Reply
from
from
10.20.143.142:
10.20.143.142:
bytes=32
bytes=32
time=73ms
time=72ms
TTL=62
TTL=62
Reply from 212.213.204.98: bytes=32 time=127ms TTL=253 RTT 132 Reply from 10.20.143.142: bytes=32 time=70ms TTL=62
Average RTT
74 ms
Ping statistics for 10.20.143.142:
Ping statistics for 212.213.204.98:

Packets: Sent = 25, Received = 25, Lost = 0 (0% loss), ms

Packets: Sent = 29, Received = 29, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Approximate round trip times in milli-seconds: Minimum = 67ms, Maximum = 87ms, Average = 74ms
Minimum = 125ms, Maximum = 151ms, Average = 132ms

Seamless Mobility
- Inter system application requirements
- Mobility performance evolution

Application Requirements for Inter and Intra
System Mobility
Inter
Laptop/TC Intra
P
Inter WCDMA/GSM
Mobile Inter
browsing
Intra WCDMA
Intra
Inter
Streaming Intra
Inter
Push-to-Talk Intra
Video Inter
Sharin Intra
g
Voice
0 2 4 6 8 12 14 16 [s]
Inter System Cell Reselection Times:
3G to 2G
Description
Features are added Cell re-selection time for UDP traffic
from left to right [s]
RAN release has
minor impact
Performance
features
Gs interface vs no Gs
interface
Inter system NACC
Tuning of TBF
Packet switched
handover
Target delay is less than 5s with todays features

HSDPA cell reselection via cell_FACH in
RAS05
Serving Cell Change switches the user from HS-
DSCH to Cell_FACH then back to HS-DSCH
Cell A Switching to Cell B

Service Cell_FACH UE on HS-
in within the DSCH
HSDPA SHO area
HS-DSCH coverage HS-DSCH coverage
Throughput
HSDPA
128kbps or 384kbps according to parameter settings

DCH
64kbps

HSDPA cell reselection via cell_FACH in
RAS05
1600 kbps
1 Mbps
800 kbps
Measured
HSDPA data
break ~ 2.5 s

Sustainable Bit Rates
Radio resource management in WCDMA
Evolution with Nokia WCDMA

Technology comparison
GPRS/EDG R99 WCDMA HSDPA
E
RNC RNC
BSC
Packet scheduling Channel scheduling in Data scheduling over

over shared dedicated channels shared channels
channels Stable bit rates by Variable bit rates by
Variable bit rates by default default
default QoS-differentiation via QoS-differentiation
QoS-differentiation dedicated channel through access control
through access scheduling and/or priorities in
control and/or packet scheduling
priorities
~1 to 12sincell
packet
re- Seamless < 3s break
scheduling
selection breaks mobility with soft
HO
~ 5-12s break

RRM evolution With Nokia WCDMA
RAN04
Guaranteed bit rate supported for WCDMA/DCH bearers
End user bit rate is constant except for overload scenarios
Limited means for differentiating different services
RAS05
Enhanced priority based scheduling & overload control for
WCDMA/DCH
Best effort scheduling for WCDMA/HSDPA
WCDMA/DCH rate may be flexibly upgraded/downgraded based
on QoS
High priority WCDMA/DCH Fairly constant bit rates even in
Moving high load

from fairly stable bit rates from an end user point of view to
WCDMA/HSDPA
an environmentuser withbit ratesvarying
more vary based
bit on loadand
rates andpossibility
radio
conditions to have QoS differentiation
-
This emphasizes the need for application adaptation like in Internet

UL/DL Coverage and Bit
Rates
-Downlink coverage
- Uplink bit rates

Downlink Coverage
HSDPA
Includes multiple modulation schemes can exploit good radio conditions
Layer 1 retransmission scheme improves sensitivity
Rule of thumbs
Doubling carrier frequency halfs cell range
Doubling carrier frequency requires 10 dB gain to LB for same coverage
2000 kbps
Average
HSDPA850 s
EDGE900 140 kbps
HSDPA2100
WCDMA85 270 kbps
0
1000 kbps HSDPA850 750 kbps
500 kbps WCDMA850/2100

(E)GPRS900
200 kbps
100 kbps
0.25 km 0.5 km 1 km 2 km
Uplink Bit Rate for HSDPA
Uplink 384 kbps is required with downlink 3.6 Mbps
Needed for TCP acknowledgements and application requirements
UL/DL balance not worse than 1 to 10 for TCP
Available in Nokia RAN & in for example Sony-Ericsson GC95 data
card
All HSDPA terminals have 384 kbps uplink
Nokia RAN supports fast link adaptation with 20 ms period
Uplink speed is important for sending emails for example!!
UE hits max
power data rate
reduced Conditions improve
data rate
increased back to
384 kbps
384 384 384 384
kbps kbps kbps kbps
128 128 64 64
DPCCH DPCCH DPCCH DPCCH DPCCH DPCCH DPCCH DPCCH
20 ms 20 ms 20 ms 20 ms
DPCCH = dedicated physical control channel

Application/Terminal
Aspects
- Battery consumption with push-email

What Is Push Email?
Open and read instead of fetch and read
A copy of the email received by mail server is provided to mobile

phone
Most of the currently available services use proprietary protocols
Push email requires an always on data connection i.e. PDP context
Mobile
Network
Mobile email
Email client Email server
gateway
Mobile optimised Internet email

email protocol protocol

Push Email Power Consumption
Receive new mail Receive mail
IDCH DCH/HS-DSC
tmail+t1 tmail+t1
Keep alive
IFACH FACH
t2 talive+t2 t2
IPCH PCH
tmail = mail notification reception time = 2 s assumed

t1 = DCH release timer = 2..10 s assumed
t2 = FACH timer = 2..10 s assumed
IDCH = mobile current consumption in DCH state = 250 mA assumed
IFACH = mobile current consumption in FACH state = 125 mA assumed
IPCH = mobile current consumption in PCH state = 3 mA assumed
Cell_PCH is not used
Keep alive message on DCH
Cell_PCH is used
Keep alive message on FACH
Typical keep alive frequency 4 min
Terminal power consumption [mA]
120
Cell_PCH disabled
100
Cell_PCH enabled
80
60
40
20
0
2 5 10
FACH inactivity timer [s]
Push email standby-time: 4 minutes keep alive
200 period
180
2 s inactivity timers
160 Short inactivity
5 s inactivity timers
timers allow long
140 standby times 10 s inactivity timers
120
Hours
100
80
60
40
20
0
0 5 10 15 20 25 30 35 40 45 50
Messages per hour
Push Email Working Solution Today
Settings
Keep alive frequency at least 4 min
Cell_PCH
Relatively short DCH release timer
Relatively short FACH release timer
DRX cycle 1.28 s or 2.56 s
Products
Nokia push email gateway
Nokia push email client which is
supported e.g. 6680, N70 (Also
Motorola, Samsung, LG, Sony
Ericsson)

Summary

Summary
Properties affecting the end user experience
Setup times
Packet round trip time
Mobility
Sustainable bit rates
Coverage
Terminal challenges
All these can be improved in future WCDMA release, but
already today all services up to real time VoIP is possible to
support in WCDMA/DCH
WCDMA/HSDPA brings higher bit rates and shorter round trip
times improving efficiency and end user experience
Higher capacity for VoIP
Better utilization of high bit rates with lower RTT

Thank You
Questions?

Extra slides

What is streaming?
Streaming is the transmission of real-time data (commonly audio and
video) from a server to a client (terminal), where the client decodes and
"plays" the data as it is received.
Streaming lets the viewer see the content immediately after a buffering
period.
No data is permanently stored in mobile client.
The end user is not able to forward or send the content to another user.
SW Tools for
Mobile Streaming
Network Content
Creation
Terminal Player Streaming
Solution
Decoding &
Transmissi Encoding
Playback
on

Streaming Key Functionalities
Web Device
server 4. Get profile
capabilit server
2. y profile
1. Describe Session
5. Capability
descripti
profile
3. Setup on
RTSP/TCP
The key standardized
6. Ok RTSP/TCP
(IETF/3GPP)
functionalities:
7. Play RTSP/TCP
8. Ok RTSP/TCP Session establishment

Streamin Streamin
g client 9. Streaming Media g server
RTP/UDP
Capability exchange
Receiver reports RTP/UDP
Session setup and control
Sender reports RTP/UDP
10. Teardown RTSP/TCP

Data transport
8. Ok RTSP/TCP

Why Rate Adaptation?
Content rate adaptation:
Is needed to adapt the content rate to the achievable bit rates
of the access technology in question.
Transmission rate adaptation:
Is needed refill client buffer after transmission breaks due to
mobility events or instantaneous channel congestion
User experience and

Example coverage network utilization go
with current roll-out hand in hand and
status
WCDMA
GSM/EDGE
GSM/GPRS

Typical Rate Adaptation
Implementation
The transmission rate adaptation module calculates based on the clients
receiver reports the available bandwidth and the transmission rate for the
server. This is estimated based on reported RTT, packet loss and received rate
The content rate adaptation module maintains the estimate of the client
buffer status.
If the estimate hits high water mark an up shift in content rate is made.
If the estimate hits low water mark a downshift in content rate is made.
High
water
mark
Servers
Client estimat
buffer Should be the same! e of Low
half client water
full buffer mark
half
full
Mobile
Network

The impact of 3GPP rel. 5 to rate
adaptation (26.234)
3GPP rel. 5 and its Annex G specify the capability exchange process
which enables:
1. The server to know the available buffer size in the client
2. The server to know the maximum content rate decoding
capability of the client
3. The buffer consists of pre-decoder buffer and of post-decoder
buffer
The status with 3GPP rel. 5 rate adaptation

1. Nokia series s60 phones published after 6630 implement the
standard fully with others the situation is not so clear
2. In the absence of receiver reports server can not estimate the
client buffer level accurately

The impact of 3GPP rel. 6 to rate
adaptation (26.234)
The 3GPP rel. 6 specifies the 3GPP-link-char header. This enables:
The client to tell the server explicitly the guaranteed bit rate of its
PDP context in the RTSP PLAY message
The 3GPP rel. 6 specifies a new header to the receiver reports. In the
NADU (Next Application Data Unit) header the client will tell explicitly its
remaining free buffer space to the server. Thus:
1. The server will have continuously an exact (not estimated)
knowledge of the clients buffer status.
2. The buffer over runs and under runs can be avoided
The status with 3GPP rel. 6 rate adaptation

1. Nokia phones are just about to come out with 3GPP rel. 6 support
6280 ?
2. The server vendors Real Networks and Packet Video have indicated
to launch a 3GPP rel. 6 capable server product in 2Q/2006

Media Rate Adaptation: Working
Solution Today
Solution requirements
3GPP Release 5 streaming
Nokia 6630 or 6680
Real Networks server version 11 6630 6680
How to make initial media rate selection?

EDGE and WCDMA initial rates the same
Per phone model in the streaming server ~ 60
Reasonable starting bit rate could be 60 kbpskbit/s
How continuous media rate selection works?
128 kbps RAB in WCDMA
3-4 files
1. Initial media rate for example 60 kbps
2. Upgrade to next media rate ~90 kbps happens after ~10
seconds
3. Upgrade to final media rate ~120 kbps happens after ~20
seconds
Settings and choices depend on the network!

Nokia Terminal Support For 3GPP Rel. 5 Rate
Adaptation
WCDMA/EDGE,
Interactive QoS,
Full 3GPP rel. 5
+ Annex G 6630 6680 6681 6682 N70 DTM N71 DTM
support MSC-10 MSC-10 MSC-10 MSC-10 MSC-10 MSC-10
N90 N91 DTM N92 DTM N80 DTM

MSC- MSC-10 MSC-11 MSC-11
10
WCMA/EDGE,
Streaming QoS,
Partial 3GPP rel.
5 support
6280 6233
MSC-10 MSC-10

Nokia Push Email Supported
Terminals
Current Nokia Phones: 3230; 6620; 6680;

6681; 6630; 7610; 9300; 9500; N70; 9300i
& 6708 are coming soon
Other supported vendors: LG, Sony

Ericsson, Motorola, Samsung, Palm, Treo,
Audiovox, Dell, HP , iPAQ

= AAL2
reserved, but
not usedused
DCH Upgrade in Iub
= AAL2 Break ~700 ms
Double 2 1 3 4
reservatio
n ED2 : Break in user plane,
384 kbps Iub double reservation
ED2 32 kbps
Break ~900 ms
1 2 3 4
RAN04: Longer break in
user plane than in ED2 but
32 kbps 384 kbps
RAN04 no Iub double reservation
2 3 4 1
384 kbps RAN04 September05: No

RAN04 32 kbps break in user plane, no Iub
double reservation
Septembe (CR#641)
r 1 Release AAL2 (32 kbps)
2 Establish AAL2 (384 kbps)
3 Send RB reconfiguration message
4 New RB taken into use after activation timer

WCDMA Service Performance: Nokia Expert Club

Enviado por

Dados do documento

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

WCDMA Service Performance: Nokia Expert Club

Enviado por

Direitos autorais:

Formatos disponíveis

WCDMA Service

NOKIA 2006 WCDMA Service Performance.ppt/ AAr & MKr

NOKIA 2006 WCDMA Service Performance.ppt/ AAr & MKr

NOKIA 2006 WCDMA Service Performance.ppt/ AAr & MKr

Does the network and applications

NOKIA 2006 WCDMA Service Performance.ppt/ AAr & MKr

2. Low end-to-end packet round trip time

4. Sustainable bit rates and end-user

5. Uplink and downlink coverage

6. Terminal processing power, application

NOKIA 2006 WCDMA Service Performance.ppt/ AAr & MKr

NOKIA 2006 WCDMA Service Performance.ppt/ AAr & MKr

Typical web page (100kB) with 384 kbit/s WCDMA

2-3s 2-3s 0.4s 0.6s 2s 1-2s Time

NOKIA 2006 WCDMA Service Performance.ppt/ AAr & MKr

NOKIA 2006 WCDMA Service Performance.ppt/ AAr & MKr

~3s gain Always on

No Attach Attach Attach Attach

NOKIA 2006 WCDMA Service Performance.ppt/ AAr & MKr

NOKIA 2006 WCDMA Service Performance.ppt/ AAr & MKr

Download with Faster download

1 DNS query 3 TCP slow start

NOKIA 2006 WCDMA Service Performance.ppt/ AAr & MKr

600 500 400 300 200 100 0

NOKIA 2006 WCDMA Service Performance.ppt/ AAr & MKr

0 200 400 600

Ping statistics for 212.213.204.98:

NOKIA 2006 WCDMA Service Performance.ppt/ AAr & MKr

NOKIA 2006 WCDMA Service Performance.ppt/ AAr & MKr

Target delay is less than 5s with todays features

NOKIA 2006 WCDMA Service Performance.ppt/ AAr & MKr

Cell A Switching to Cell B

HS-DSCH coverage HS-DSCH coverage

128kbps or 384kbps according to parameter settings

NOKIA 2006 WCDMA Service Performance.ppt/ AAr & MKr

NOKIA 2006 WCDMA Service Performance.ppt/ AAr & MKr

NOKIA 2006 WCDMA Service Performance.ppt/ AAr & MKr

Packet scheduling Channel scheduling in Data scheduling over

NOKIA 2006 WCDMA Service Performance.ppt/ AAr & MKr

Moving high load

NOKIA 2006 WCDMA Service Performance.ppt/ AAr & MKr

NOKIA 2006 WCDMA Service Performance.ppt/ AAr & MKr

500 kbps WCDMA850/2100

DPCCH = dedicated physical control channel

- Battery consumption with push-email

NOKIA 2006 WCDMA Service Performance.ppt/ AAr & MKr

A copy of the email received by mail server is provided to mobile

Most of the currently available services use proprietary protocols

Push email requires an always on data connection i.e. PDP context

Mobile optimised Internet email

NOKIA 2006 WCDMA Service Performance.ppt/ AAr & MKr

tmail = mail notification reception time = 2 s assumed

NOKIA 2006 WCDMA Service Performance.ppt/ AAr & MKr

NOKIA 2006 WCDMA Service Performance.ppt/ AAr & MKr

NOKIA 2006 WCDMA Service Performance.ppt/ AAr & MKr

NOKIA 2006 WCDMA Service Performance.ppt/ AAr & MKr

NOKIA 2006 WCDMA Service Performance.ppt/ AAr & MKr

No data is permanently stored in mobile client.

NOKIA 2006 WCDMA Service Performance.ppt/ AAr & MKr

8. Ok RTSP/TCP Session establishment

10. Teardown RTSP/TCP

NOKIA 2006 WCDMA Service Performance.ppt/ AAr & MKr

User experience and