I hspa traffic-model_version5

1 (21) <Document ID> IHSPA Rel 1.00.4 System Performance Specification2008-05-11Owner: <Content Owner> For internal use only

IHSPA Rel 1.0Radio Access

Traffic Model

Nokia Siemens Networks

Copyright © 2007 Nokia Siemens Networks. All rights reserved.

No part of this publication may be copied, distributed, transmitted, transcribed, stored in a retrieval system, or translated into any human or computer language without the prior written permission of Nokia Siemens Networks.

The manufacturer has made every effort to ensure that the instructions contained in the documents are adequate and free of errors and omissions. The manufacturer will, if necessary, explain issues, which may not be covered by the documents. The manufacturer's liability for any errors in the documents is limited to the correction of errors and the aforementioned advisory services.

The documents have been prepared to be used by professional and properly trained personnel, and the customer assumes full responsibility when using them. The manufacturer welcomes customer comments as part of the process of continual development and improvement of the documentation in the best way possible from the user's viewpoint. Please submit your comments to the nearest Nokia Siemens Networks sales representative.

Nokia Siemens Networks and the wave logo are registered trademarks of Nokia Siemens Networks. Other company and product names mentioned herein may be trademarks or trade names of their respective owners.



Table of contents

1 Introduction.........................................................................................3

2 Traffic Definition..................................................................................42.1 General.............................................................................................................................42.2 Open Points......................................................................................................................52.3 Subscriber mix configurations...........................................................................................62.4 Service Definitions..........................................................................................................762.4.1 CS Calls............................................................................................................................72.4.2 SMS.................................................................................................................................982.4.3 MMS................................................................................................................................982.4.4 HTTP/ Web Browsing....................................................................................................1092.4.5 FTP..............................................................................................................................11102.4.6 VoIP.............................................................................................................................1211

3 Traffic Load...................................................................................13123.1 Packet data profiles.....................................................................................................13123.2 System Load...............................................................................................................14133.2.1 Subscriber Mix “Terrestar Specific I-HSPA”,...............................................................14133.2.2 Subscriber Mix “Laptop dominat I-HSPA”...............Fehler! Textmarke nicht definiert.133.2.3 Subscriber Mix “I-HSPA as HSPA extension”.........Fehler! Textmarke nicht definiert.14

4 Signaling Load..............................................................................16154.1 Signaling Procedures on Iub, Iur and Iu Interfaces.....................................................16154.2 Paging Load................................................................................................................1920

5 References...................................................................................2221

6 Definitions and Abbreviations...........................................................22

7 Annex...............................................................................................22

8 Document Revision History..............................................................22



1 IntroductionThis document describes the Traffic Model for I-HSPA Rel1.0. I-HSPA NW is optimized for PS only

(HSDPA/DCH or HSDPA/HSUPA) type of services and CS Services are handed over to the

overlaying 3G or 2G Networks. More description of I-HSPA System can be found on [SyDe].

Figure 1: I-HSPA Network Deployment

I-HSPA NodeB is consisting of two elements: Nokia WDMA NodeB (or just ‘NodeB’) and I-HSPA Adapter (or just ‘Adapter’). Relevant NodeB generations are UltraSite and FlexiBTS. Rel1 implementation is targeted only for FlexiBTS based configuration.

The logical interface in between NodeB and adapter is NodeB internal Iub with no or minimal modification due to I-HSPA.

The NodeB uses BTS internal Iub between System module and transport module (FTM). The adapter could more easily use standard Iub over IP (this would ensure more reuse between RNC and I-HSPA adapter). See more information [IPA_TR]. I-HSPA System release 1 will use BTS internal Iub.



Figure 2. NodeB Internal Iub over IP

2 Traffic Definition

2.1 GeneralFor the first version of the Traffic Model for I-HSPA the Traffic Models for RU10 and Femto were used as

template [TM RU10] [TM Femto].

The Traffic Model bases on following assumptions:

Value Remarks

Maximum number of

subscriber in RRC

connected state per I-

HSPA Adapter

5000

Maximum number of

subscriber (Subscriber in

RRC connected state +

idle state)

50000 Thumb Rule:

Number of subscriber in

connected state are 10% of all

subscriber.

Maximum number of 10000 Thumb Rule:



HSPA subscriber Number of subscriber in

connected state are 50% of all

HSPA subscriber.

This number is used for the

max. BHCA calculation

Maximum Load per

subscriber per Month

500 Mbytes This value bases on the Femto

Traffic Model:

Femto: 500 MB/Month

RU10: 50 MB/Month

LTE: 1 G70MB/Month

Number of iNodeBs per

Location/Routing Area

Max. 3600 Further calculations are done for

400 and 100, iNodeBs.

2.2 Open Points-



2.3 Subscriber mix configurationsFor further calculations different subscriber mix configurations are defined, which should be interpreted in the way, that a certain percentage of subscribers is using either http, ftp, VoIP or CS Voice.

Following subscriber mix configurations are considered for I-HSPA Rel1:

1) “Terrestar specific I-HSPAPS only Deployment” subscriber

HTTP 36 % Web browsing

FTP 14 % Downloading

VoIP 50%

This configuration is used for Terrestar

2) “Laptop dominant I-HSPA” subscriber

HTTP 71 % web browsing


3) “I-HSPA as HSPA extension” subscriber

HTTP 32 % web browsing


VoIP 3%

CS Voice 47%

Note: Subscriber Configurations “Terrestar specific I-HSPAPS only Deployment” and “Laptop dominant I-HSPA” do not comprise CS Services (CS Voice, CS UDI, CS Data).

SMS: For configurations “PS only DeploymentTerrestar” and “Laptop” SMS is provided via PS Core, for configuration “I-HSPA as HSPA extension” both by CS and PS core. The number of SMS MT per BH is 0.66, the number of SMS MO 0.33.

2.3 Number of SubscriberThe estimation of the total number of subscribers bases on the number of subscriber in RRC connected state.

Following thumb rule applies:



The total number of HSPA subscribers is 2 times the number of subscriber in RRC connected state total #HSPA subscriber = #HSPA subscriber (RRC connected state) * 2

= 5000 * 2 = 10000

2.4 Service DefinitionsIn following chapters the effect on traffic load for most common user services is described. Typical RAB level behaviour is described for each service.

Typical service parameters are listed based on the described sequence and default or average values are given for each case. Other parameters which may influence the behaviour may also be listed for reference but it is assumed that default values are used.

These parameters base on the RU10 Traffic Model.

Parameter adaptations due to I-HSPA are marked bold.

2.4.1 CS Calls

When UE requests for CS calls, I-HSPA system redirects UE to traditional WCDMA or 2G networks. I-HSPA Adapter has an IuCS signaling connection to the MSC to ensure that Paging can be supported for CS services. Via the new feature “CS service enabling HO” the redirections are done. In the attached documents message flows for MOC and MTC can be found.

MOC:

MTC:

CS services have to be considered for the system signaling load. For this the number and volume of messages for CS Call Setup Part and CS service enabling Handover are combined.In a first step all CS calls will be considered for the signaling load, even if some of the redirected calls will remain at 3G or 2G networks (worst case estimation).

Parameter value

MTC 640%



MOC 4 60%

BHCA/user 0,88



2.4.2 SMS

Mobile Originated, Mobile Terminated and Mobile-to-Mobile SMS transfer. Message is relayed through SMSC so M2M = MOC + MTC.

Transfer routing is possible via CS core or PS core.

Typical transfer phases:

Parameter Info value Notes

Message size characters 160 length not relevant, >160 character messages are split into several SMS

Transfer time 2-10s depends on call type

Idle time between SMS 40min 5s for testing use

SMS/user Busy Hour 1.5/h

SMS MO MO-SMS/subs/BH 0,33

SMS MT MT-SMS/subs/BG 0,66

2.4.3 MMS

Mobile originated, Mobile Terminated and Mobile-to-Mobile MMS transfer. Message is relayed through SMSC so M2M = MOC + MTC.

Typical transfer phases are similar to HTTP.


SRB

Idle

SRB

Idle

Message Transfer time

Parameter info value notes

Message size video clip ~100KiB

Transfer time 20-30s

Idle time between MMS 240min 10s for testing use

MMS/user Busy Hour 0.25/h


Other parameters affecting service performance: initial / max bit rate, HSPA use.

Note: Transfer via UDP or TCP causes 2-3% overhead and an additional notification message (<100B).

2.4.4 HTTP/ Web Browsing

Download HTTP pages from server. Typical transfer phases and RRC state transfers:

Transfer time and reconfiguration rate depend on QoS setting (initial/maximum bit rate), actual Radio Bearer throughput, use of DCH/HSPA, always on (makes UE stay on PCH),


Parameter info value Notes

HTTP page size 50KB distribution e.g. 10/50/200KB

Number of pages/session

5

Object size 1-50 KB

Objects/page 1-5

Idle time between page downloads

12s Think Time / Reading Time

Transfer time see below

RAB reconfigurations

0/0 -> initial -> maximum -> minimum

18 / session 2.5 / page init/upgrade(50%)/release + 1.5 / session (average downgrades)

Average duration 98s Download time * pages/call + reading time * (pages/call-1)

UL / DL Ratio 1 : 4


RRC/HSDPA timers, TCP slow start (~ 0.7s) etc. These kinds of parameters are not defined here.

2.4.5 FTP

Files are downloaded from or uploaded to an external server. Mainly used for testing purposes. Music downloads etc. may also be implemented with FTP.

Typical transfer phases are similar to HTTP.

2.4.6 VoIP

Mobile originated, Mobile Terminated and Mobile-to-Mobile calls with a VoIP client using TCP

and UDP transfer. Typical transfer phases and RRC state transfers are shown below for UL direction.





3 Traffic LoadThe following chapters describe higher level traffic issues and give some suggested values for traffic distribution and parameters.

3.1 Packet data profilesThe packet data user profile defines the average offered data load and distribution over services and transfer rates. Separate profiles are estimated for low, average and high load users. The average I-HSPA user is estimated to transfer 500 MB/Month of data.

Average Data transfer speed profiles:


Data Service kbit/s

HTTP 0,6

FTP 0,6

Streaming 0,064

VoIP 0,032


3.2 System LoadBelow are the estimated load level figures together with the relevant subscriber traffic values. Further details can be found in the Excel-Sheet in the annex.

For the calculation of the NAS BHCA a factor of 3.8 was used. This factor considers Location Update, Routing Area Update, SMS, Attach and Detach Procedure.

PS pnly Deployment Laptop I-HSPA

Service Call BHCA Call BHCA Call BHCA

HTTP 3600 7100 3200

ftp 1400 2900 1800

VoIP 440 - 264

∑Call BHCA 9400 10000 5264

NAS BHCA 38000



4 Signaling Load

4.1 Signaling Procedures on Iub, Iur and Iu InterfacesFor the signaling load per adapter following procedures were considered, see [TD RU10]:- PDP Context Activation,- Routing Area Update,- CTS (HSDPA/DCH),- SCC + Relocation + Role Switch,- Soft HO (66%), Softer HO (33%),- Bearer Rate Adaptation,- SMS MO, - SMS MT,- Location Update,- CS MOC(60%)/CS Service enabling HO, CS MTC(40%)/CS Service enabling HO

HO:In I-HSPA Rel1 Soft HO over Iur is only possible in case of DCH.This means for HSDPA/HSUPA SRNS Relocation is used instead of Soft HO.20% of the PS services are done with HSDPA/HSUPA, 80% with HSDPA/DCH.Therefore the above mention Soft HO part of 66% is divided up to 53% Soft HO and 13% SRNS Relocation.

SMS: In a first step for Subcriber Configuration “Terrestar” and “Laptop” it was assumed that SMS transfer is routed via PS core. For Subscriber Configuration “I-HSPA as HSPA extension” for the SMS transfer it is assumed that 47% is routed via CS core and 53% via PS core. (B.t.w. the number of messages and the messages lengths are the same there is no difference for SMS via PS and SMS via CS Core!)

CS Voice: CS services have to be considered only in case of “I-HSPA as HSAPA extension” subscriber configuration and only for the system signaling load. For this the number and volume of messages for CS Call Setup Part and CS service enabling Handover are combined. In a first step all CS calls will be considered for the signaling load, even if some of the redirected calls will remain at 3G or 2G networks (worst case scenario).

For I-HSPA Adapter on internal Iub, Iur and Iu Interface calculated signaling load can be found in the table below. These calculations base on [TMod RU10] .

Note: - NAS signaling is included in the calculations for Iub and Iu interface.- RRC signaling is included in the system load: mean traffic per DCH session = 7.5%

(see section 3.1)

The total signaling has to be summed up separately for each interface.

Total signaling load = sum (data-rates) ( 1 + M) / link_load * n

Sum (data-rates) = data-rates separate for each interface * factor



Factor = frequency of a procedure during BH * % of subscriber

M: Margin introduced, since not all procedures are included (IMSI/GPRS Detach Attach, ..)link_load: Load of signalling link = 40%n: Number of signaling links

Iub Interface: M = 10%, n= 1Iur Interface: M = 10%, n=2Iu Interface: n = 2, M(CS) = 25%, M(PS) = 17%

In the tables below following parameters are shown:- frequency of a procedure during BH- relevant percentage of the procedures- total signaling load in UL and DL for Iub, Iur and Iu interface.

Further calculation details and volume of data can be found in the annex.

Subscriber Configurations “TerrestarPS only Deployment”

Iub DL Iub UL Iur DL Iur UL PS Iu DL PS Iu UL

low kbps 253,7 158,7 30,9 29,3 166 165

average kbps 700,9 357,9 121,2 115,2 300,8 316,4

high kbps 1060,3 517,9 193,8 184,1 409,1 438



Subscriber Configurations “Laptop”


low kbps 171,6 122,1 14,3 13,6 141,1 137,3

average Kbps 444,1 237,5 71,6 68 212,9 219,4

high kbps 817,4 409,7 144,8 137,5 335,9 355,8



Subscriber Configurations “I-HSPA as HSPA extension”


low kbps 164 121,8 16,4 15,5 88 66,2

average kbps 361,3 200,3 64,3 61 159,4 68,3

high kbps 519,8 263,3 102,7 97,6 216,8 232,1

CS Iu DL CS Iu UL

68,3 58,4

4.2 Paging LoadIn Rel1 for every MT connection (Voice, SMS) the CN sends Paging messages to all adapters within a Location Area or Routing Area. Adapter forwards the paging message to the BTS via (internal) Iub.

The maximum number of Adapters per RA/LA is 300.

Following formulas are used to calculate the required bandwidth per Adapter:

Data Rate:Number of Paging messages (CS Voice/ VoIP/SMS CS/SMS PS) on Iux/ s =number of (CS Voice/VoIP/SMS CS/SMS PS) Subscriber * % MTC * BHCA (CSVoice/VoIP/SMS CS/SMS PS) * (number of adapters per LA/RA) * 8 / 3600 (Mbytes / s)

Required Bandwidth:B = data_rate * 100 / link_load * n * (1 + M/100)where link_load = maximum link utilization = 40%n = number of signaling links = 2M = additional Margin = 17%

Detail can be found in [TD RU10].

The Paging messages take 50 bytes on Iub and 200 bytes on Iur/Iu Interface.



In the tables below the calculations for the paging load in case of average load can be found.

”PS only Deployment”

# I-BTS per LA/RA = 300 # I-BTS per LA/RA = 60

Iub Iu-PS Iub Iu-PS

VoIP 88 352 18 70

SMS PS 220 880 44 176

B (kbps) 450 1802 90 360

”Laptop”


Iub Iu-PS Iub Iu-PS

SMS PS 220 880 44 176

B (kbps) 322 1287 64 257

”I-HSPA”


Iub Iu-PS Iu-CS Iub Iu-PS Iu-CS

VoIP 5 21 1 4

CS Voice 83 33 16 66

SMS PS 117 466 23 93

SMS CS 103 414 21 83

B (kbps) 272 713 1089 32 127 218



5 References[SyDe] I-HSPA System Description for E2

[TM RU10] Traffic Model RU10

[TM Femto] Traffic Model femto 0.1

[TD RU10] Signaling Traffic Dimensioning RU10

[PTS UMRHSU] Performance Target Specification UMR HSU

[TMod RU10] Traffic Modeling RU10

6 Definitions and Abbreviations

7 AnnexSignaling Load details :

Calculation of System Load and, Signaling Load and Paging Load

8 Document Revision HistoryVersion Author Remarks Date

0.1 Claudia Vallentin


08.04.08


Review Comments added 18.04.08




Max HSPA subscr. = 10000/AdaCorrection of BHCA

14.05.08


Correction of Paging Load 27.07.08


I hspa traffic-model_version5

Documents

ihspa rel

internal use

correction of errors

free of errors

traffic load

traffic definition

customer comments

retrieval system