12 Traffic Model RU10-NSN

UTRAN Traffic Modelling RAS – RU - UMRFor internal use
* © Nokia Siemens Networks RU10 UTRAN Dimensioning Training / NPO Capability Development
For internal use
NSN Standard traffic model: What’s new for RU10
NSN Standard traffic model: Basic application mix and frame data
NSN Standard traffic model: Rel’99 Traffic (CS + PS)
NSN Standard traffic model: Rel’5 and Rel’6 Traffic (HSxPA)
New: I-HSPA (no direct RU10 feature)
New for RU10: VoiP
Summary: Marketing Traffic Information
For internal use
For internal use
Introduction and Motivation
Default traffic model for network dimensioning
Not in every case the customer provides in a tender detailed traffic information
Quite often our sales and network planning colleagues in the regions are asked about our NSN view of traffic mix and increase, in particular from new operators in 3G/HSPA
In order to have some information in hand which
reflects the estimated traffic service mix and increase
suits to the NSN product performance (BTS, RNC, …)
a default traffic model has been introduced as a basis for tenders and projects
The default traffic is regularly adapted to project feedback and marketing forecasts
SN MN PG NT NE
For internal use
Introduction and Motivation
Traffic modeling is the first step in the network dimensioning.
Usually, for W-CDMA radio/access networks, the following work flow is applied in the dimensioning:
Air interface dimensioning
For internal use
For internal use
Traffic model
I-HSPA (no specific RU10 feature)
General topics regarding Speech Service
General topics regarding Data Services
VoiP
Table with different Codec rates
Slightly changed input figures for Utran Dim Tool v6.0.x
Mean rate per user during HS-DSCH session
Mean rate per user during E-DCH session
These topics are treated in some of the following chapters.
SN MN PG NT NE
For internal use
SN MN PG NT NE
For internal use
CS Conversational Applications
PS Interactive/Background Applications
PS Interactive/Background Release 5 HSDPA DCH/HS-DSCH or
PS Interactive/Background Release 6 HSxPA E-DCH/HS-DSCH
Streaming QoS for HSxPA – new in RU10
SN MN PG NT NE
For internal use
Default Traffic Model
RU10 Basic Recommendations
In addition: CS UDI 64
BHCA 0,05; traffic demand: 2,5 mErlang; call duration: 180s
PS Interactive/Background (differentiated between Rel’99 & HSxPA)
BHCA 0.30; traffic demand (DL): 575 bps
Release 99 traffic demand per subscriber: 250 bps
HSxPA traffic demand per subscriber: 325 bps
BHCA Split Release 99 – HSxPA (Release 5/6): 70% : 30%
BHCA Split HSxPA: Rel’5: 20% - Rel’6: 10%
Asymmetry:
Release 99 (UL : DL): 1 : 5
HSDPA Rel’5 (UL Rel’99 : DL HSDPA): 1 : 4,3
HSxPA Rel’6 (UL HSUPA : DL HSDPA): 1 : 4,3
SN MN PG NT NE
For internal use
NSN Standard Traffic Model
RAS06 – RU10 – UMR7.0: Example / Traffic Mix Assumptions and Frame Data (1/4)
See Excel Sheet
Info
History:
V0.1
Voice
The traffic demand per subscriber is adjusted to the assumptions made for CS traffic in PTS
Video
in addition to pure voice centric approach for CS in PTS
PS
The PS services include File Download, Web Access, Email etc.
The traffic demand per subscriber is adjusted to the assumptions made for PS in PTS
Streaming
See optional services: PS streaming service as real-time application in addition to the assumptions for CS and PS (note: optional feature)
See optional services: PS conversational as real-time application in addition to the assumptions for CS and PS (note: optional feature, check if released)
Changes are highlighted using
50
bps
20%
25
bps
10%
DL
BHCA
Traffic volume per user [kByte]
Sum traffic
BHCA
Sum traffic
Application
0.210
250.0
Note: The data volume and the asymmetry of the resulting traffic demand needs to be checked to match to the overall demand of 250 bps per subscriber in the busy hour and to the asymmetry of 1:5 (1:5.2) (UL:DL) for Release 99.
b) Rel. 5 (DCH/HS-DSCH) traffic demand
PS NRT Rel 99/HSDPA: HSDPA/Rel. 99 UL demand
Application
Traffic volume [kbit]
UL
100.0%
0.060
93.75
160.0
0.20
1.6
50.0
180.0
Application
mErl/Subscriber
DL
100.0%
0.060
93.75
138.7
1.6
216.7
780.2
0.060
216.7
Note: In the above table, the traffic demand for all services mapped to HSDPA and all UE categories was summed up, e.g. category 6, 8, and 12. A mean HSDPA throughput of 325 bps in the busy hour per subscriber is assumed, out of which 2/3 are assumed to be release 5 traffic resulting in 216.7 bps.
c) Rel. 6 (HSUPA/HSDPA) traffic demand
PS NRT HSUPA/HSDPA: HSUPA traffic demand (UL)
Application
mErl/Subscriber
UL
100%
0.030
93.75
32.0
0.78
25.0
90.1
Application
mErl/Subscriber
DL
0.030
93.75
138.7
0.78
108.4
390.1
VoIP split
-> defines a portion of speech offered traffic served by VoIP
Data split
-> defines a portion of HS data traffic served by I-HSPA
CS Traffic
CS Conversational
Application
mErl/Subscriber
UL
100%
0.030
93.75
32.0
0.78
25.0
90.0
Application
mErl/Subscriber
DL
0.030
93.75
138.7
0.78
108.3
390.0
0.0
Note: 29,4kbps is a default assumption on the VoIP codec rate (no ROHC).
Traffic Model Example
Application
Application
Application
PS NRT HSUPA/HSDPA: HSUPA traffic demand (UL)
Application
Application
Application
DL
0.0
0.0
0.0
Note the above table sums of the DL traffic demand for HSDPA (DCH/HS-DSCH + E-DCH/HS-DSCH)
Speech service including VoIP split
VoIP split
CS Traffic
CS Conversational
UL
0.01
300
128
0.8
106.7
384.0
384000000.0
106666.7
833.3
DL
0.01
300
10
0.8
8.3
30.0
30000000.0
8333.3
833.3
Mean Rate per active user (UL) [kbps]
Mean Rate per active user (DL) [kbps]
Mean Rate per subscriber (UL) [kbps]
Mean Rate per subscriber (DL) [kbps]
Speech
Conversational
0.6
108
12.20
12.20
0.5
30
18
For internal use
NSN Default Traffic Assumptions in Detail
CS traffic demand
325
bps
30%
For internal use
Resulting PS I/B traffic per subscriber:
BHCA obtained on base of the split
Default traffic assumptions
For internal use
detail
DL
BHCA
Σ Sum traffic
BHCA
Σ Sum traffic
90%
0,270
100
45,00
166,67
For internal use
For internal use
Detailed traffic model including proposed RAB split (CS example):
Throughput_per_CS_subscriber [bps] = = bhca * call_duration[s] * activity * bearer_rate[kbps] / 3600s *1000
Traffic_per_CS_subscriber[mErl/subscr.] = call_duration[s] / 3600s * BHCA * 1000
SN MN PG NT NE
For internal use
Detailed traffic model including proposed RAB split (PS example):
Additional assumptions
SN MN PG NT NE
For internal use
SN MN PG NT NE
For internal use
Rel’5 and Rel’6 Traffic (HSxPA): HSDPA and HSUPA (1/8)
HSDPA applies for Release 5 UEs and Release 6 UEs
In HSDPA capable and configured (licensed) cells demanding PS Interactive/Background services (single RAB) or in combination with AMR Speech or CS UDI calls (multi RAB).
Release 5 terminals use only Rel’99 UL bearer
Release 6 terminals can use either Rel’99 UL or HSUPA (if HSUPA is available)
HSUPA applies for Release 6 UEs
In HSUPA capable and configured (licensed) cells demanding PS Interactive/Background services (single RAB) or in combination with AMR Speech or CS UDI calls (multi RAB).
Release 5 terminals can use only Rel’99 UL bearer
Focus on PS Interactive/Background single calls
Multi calls recommended to be treated separately as several individual RABs for traffic demand calculation unless traffic demand assumptions from operator are available.
For more details wrt. Rel’99 UL traffic in case of HSDPA only (no HSUPA) please refer to the slide of the previous section Rel’99 traffic (PS I/B traffic).
SN MN PG NT NE
For internal use
NSN Standard Traffic Model - HSxPA Traffic: HS-DSCH and E-DCH (2/8)
E-DCH (nominal peak rate = max rate over session
time
HS
Data rate
mean rate over RAB life or session
UL HSUPA
RACH
FACH
HS-DSCH
HS-DSCH
For internal use
Parameters for HSUPA and HSDPA:
Number of subscribers [ ]
E-DCH/HS-DSCH activity [ ]
HSDPA:
HSUPA:
HSUPA Traffic Demand is calculated in the same way: HS-DSCH is replaced with E-DCH!!!
E-DCH session duration corresponds to HS-DSCH session duration.
referring to BH
For internal use
HSxPA Traffic: Mean Throughput per User during Packet Session: Downlink (4/8)
Since in the default Traffic Model we already have given the assumption for HSxPA Throughput per subscriber, Mean Throughput during Rel’99/E-DCH and HS-DSCH sessions might be easily calculated out of it.
Commonly DL and UL share is 4.3:1
Formula to estimate mean throughput:
Assumptions for Rel’5 and Rel’6 are partly different:
one important issue is the different terminal penetration (Rel’5 > Rel’6)
NSN Traffic Model Target values Release 6 (year 2008):
DL: 108,35 bps
UL: 25 bps
DL: 216,7 bps
UL: 50 bps
DL/HSDPA
SN MN PG NT NE
For internal use
UL/PS Rel’99
UL PS Rel’99 has fixed bit rates via bearers 16, 64, 128 and 384 kbps
Since in the default Traffic Model we already have the assumption for Rel’5 UL Throughput,
Mean Throughput during HS-DSCH session can be calculated by using Rel’99 user throughput:
UL/HSUPA
HSUPA is calculated similarly as HSDPA
Mean Throughput during E-DCH session can be calculated by using following formulas:
Please note: E_DCH_SessionDuration corresponds to HS_DSCH_SessonDuration (HSUPA connection needs always HSDPA in DL)
referring to BH
SN MN PG NT NE
For internal use
Traffic model default values for Input in Utran Dim Tool v6.0.x Downlink HSDPA with Rel’99 UL and HSUPA (6/8)
Currently only one HSDPA UE category is assumed (UE cat 6)
Rel’5 terminal, thus Rel’99 UL bearer (16, 64, 128 or 384 kbps)
Rel’6 terminal, thus HSUPA UL bearer
Example in Utran Dim Tool:
Utran DimTool v6.0.x input
Rel’5 > Rel’6
DL / HSDPA
mErl / Subs
Traffic volume in BH [kbit]
HS-DSCH UE Category 6
mErl / Subs
HS-DSCH UE Category 6
For internal use
Uplink Rel’99 UL and HSUPA (7/8)
Rel’99 UL bearer (16, 64, 128 or 384 kbps)
16 kbps not used in default traffic model
HSUPA UL bearer
PS Radio Bearer Split
On-ratio
PS Traffic volume in BH [kbit]
PS 64/0
mErl / Subscriber
E-DCH UE Category 3
For internal use
Calculation from Customer’s Traffic model*
Mean Rate per User During HS_DSCH session for Input in Utran Dim Tool v6.0.x & Mean Rate per User During E_DCH session if required (8/8)
Mean_throughput_per_PS_Rel’99_subscriber [bps] =
DL/HSDPA & UL/HSUPA
UL/PS Rel’99
UL traffic: Same formulae apply as for PS Rel’99 traffic (UL) !
I
II
III
* Please note: BHCA plus HSDPA TrafficVolume_in_BH or HSDPA MeanThroughputperSubscriber_in_BH must be given in Customer’s Traffic model
HSUPA Traffic Demand is calculated in the same way: - HS-DSCH is replaced with E-DCH
- E-DCH session duration corresponds to HS-DSCH session duration
NSN Traffic Model Target values Release 5 & Release 6 (year 2008):
DL : UL ≈ 4,3 : 1
factor 4.3 applies
either given by customer or known from NSN Standard traffic model
SN MN PG NT NE
For internal use
Calculation from Customer’s Traffic model*
Mean Rate per User During HS_DSCH session for Input in Utran Dim Tool v6.0.x & Mean Rate per User During E_DCH session if required (8/8)
DL/HSDPA & UL/HSUPA
UL/PS Rel’99
UL traffic: Same formulae apply as for PS Rel’99 traffic (UL) !
I
II
III
* Please note: BHCA plus HSDPA TrafficVolume_in_BH or HSDPA MeanThroughputperSubscriber_in_BH must be given in Customer’s Traffic model
HSUPA Traffic Demand is calculated in the same way: - HS-DSCH is replaced with E-DCH
- E-DCH session duration corresponds to HS-DSCH session duration
NSN Traffic Model Target values Release 5 & Release 6 (year 2008):
DL : UL ≈ 4,3 : 1
factor 4.3 applies
either given by customer or known from NSN Standard traffic model
SN MN PG NT NE
For internal use
SN MN PG NT NE
For internal use
I-HSPA Services (No direct RU10 feature) Speech and Data Services No difference in calculation wrt. “normal” HSxPA and “normal” PS services
No CS services available in the I-HSPA network, VoIP is the only speech service in I-HSPA.
VoIP (Voice over IP) is mapped to one of the available PS/HSxPA bearers.
Traffic generated by speech services and the split into CS and VoIP depends on the availability of VoIP capable UEs and network capabilities (e.g. I-HSPA or ‘normal’ UMTS network) to treat speech service either as former CS or as VoIP.
In I-HSPA Rel’1, it is recommended that speech calls are treated as CS and redirected to WCDMA/GSM network.
I-HSPA Rel’2 is supposed to introduce a more sophisticated way to handle VoIP calls, especially with respect to an increased level of QoS, reached via the following features:
- QoS aware scheduling and admission control
- Conversational and Streaming QoS class for HSPA
Emergency VoIP calls
Data services: In I-HSPA Rel’1, it is assumed that whole HSDPA (DCH/HS-DSCH) and HSxPA (E-DCH/HS-DSCH) traffic will be handled by I-HSPA.
Data services: In I-HSPA Rel’2, due to resource sharing, HSPA traffic will be split among WCDMA and I-HSPA architecture.
* Note, that speech service via VoIP might be also realized by traditional 3G network. It is recommended then to be mapped to HSxPA bearers using Streaming QoS for HSxPA RU10 feature, in order to guarantee a certain level of QoS.
Traffic Volume for I-HSPA services
There is no difference in calculation wrt. “normal” HSxPA services and “normal” PS services!!
SN MN PG NT NE
For internal use
SN MN PG NT NE
For internal use
VoiP
Under the assumption that VoIP is mapped to HSxPA bearers, the following calculation might be applied in order to calculate additional HSxPA Traffic Volume generated by VoIP:
VoiP_Traffic_volume = number_of_subscribers * bhca * * call_duration * channel_activity * voip_codec_rate [kbit]
Voice_Traffic_volume = number_of_subscribers * bhca * * call_duration * channel_activity * information_rate [kbit]
90%
10%
Channel
Channel
New in Utran Dim Tool v6.0.x
Note: 29,4kbps is a default assumption of the VoiP codec rate (no ROHC)
Defines a portion of speech offered traffic served by VoiP
Resulting Traffic Volume
For internal use
Activity (DCH-activity) [ ]
Traffic Volume:
referring to BH
For internal use
VoiP vs. CS voice traffic calculation comparison
Relevant parameters for calculation of the Traffic Volume for CS services are:
Number of subscribers []
Busy-hour-call-attempts (bhca)
Call duration [s]
Channel (Voice) Activity []
The traffic volume (or offered traffic) per service in busy hour is then given by:
Traffic_volume in busy hour [kbit in BH] = number_of_subscribers * bhca * call_duration * channel_activity * information_rate
Traffic_volume_per_subscriber in busy hour [bps] = bhca * call_duration * channel_activity * information_rate / 3600s * 1000
Relevant parameters for calculation of the Traffic Volume for VoiP services are:
Number of subscribers []
Busy-hour-call-attempts (bhca)
Call duration [s]
Channel (Voice) Activity []
The traffic volume (or offered traffic) per service in busy hour is then given by:
Traffic_volume in busy hour [kbit in BH] = number_of_subscribers * bhca * call_duration * channel_activity * voip_codec_rate
Traffic_volume_per_subscriber in busy hour [bps] = bhca * call_duration * channel_activity * voip_codec_rate / 3600s * 1000
New in Utran Dim Tool v6.0.x
SN MN PG NT NE
For internal use
For internal use
Marketing Information (1/4)
Speech telephony: 20 – 23 mErl
Video telephony: 2,5 – 3.0 mErl
SMS 0.3
Source: Mobile Networks: Subscription Tool - Market Compendium Summer 2006 [Subscriber Number & Speech traffic]
Marketing data predict “Minutes of use per subscriber per month (MoU)”
Mapping of MoU values to traffic demand per subscriber in busy hour
“High” customer segment: 0.68% of monthly traffic in busy hour
- Considering 22 days and 15% daily traffic in BH
“Medium” customer segment: 0.5 % of monthly traffic in busy hour
“Low” customer segment: 0.33% of monthly traffic in busy hour
SN MN PG NT NE
For internal use
SN MN PG NT NE
For internal use
Marketing Information (3/4)
SN MN PG NT NE
For internal use
Marketing Information (4/4) : Data traffic evolution (2006 – 2011)
PS data traffic demand [bps] per subscriber in busy hour: 2006 – 2011
High – medium – low
For internal use
Basic Traffic Model

12 Traffic Model RU10-NSN

Documents

Transcript of 12 Traffic Model RU10-NSN