Traffic Models: Szymon Nowak Icm SDC Nmr1

Traffic models
Szymon Nowak ICM SDC NMR1

07.04.2004
Agenda
General aspects of data traffic modeling
HTTP traffic model

WAP traffic model FTP traffic model MMS/SMS traffic model Summary
Page 2
Siemens, 2004

CS services vs. PS services
Voice traffic planning
General aspects - based on well known mathematical model (conventional Poisson traffic model used) - ErlangB formula for CS traffic planning HTTP traffic model WAP traffic model E-mail traffic model
ASSUMPTIONS
FTP traffic model MMS traffic model SMS traffic model Summary
Independent arrivals of calls
Exponentially distributed call durations
QoS parameter
- service blocking probability
Page 3
Siemens, 2004
Data traffic planning
- data traffic
Poisson traffic
General aspects HTTP traffic model WAP traffic model E-mail traffic model FTP traffic model
Long range correlations of packet arrival times Burstyness nature of data packet transmission
Previous assumptions concerning CS services are no longer valid. ErlangB formula must not be applied in PS traffic case. Poisson theory can not describe that type of traffic appropriately.
MMS traffic model SMS traffic model Summary
Page 4
Siemens, 2004

Data traffic quality of service parameters
General aspects
Mean throughput Peak throughput Mean delay 95%ile delay
HTTP traffic model WAP traffic model E-mail traffic model FTP traffic model MMS traffic model SMS traffic model Summary
How to dimension data traffic then?
Page 5
Siemens, 2004

The usual structure of data traffic model comprises a layered approach A number of packets building a single data request (e.g. HTTP Get Request) form a packet call A set of packet calls related to a series of connected actions of one user in turn is called a packet session A definition of traffic model: determination of applicable distributions for the number of packet calls in packet session, the packet call interarrival times and the packet length determination of parameters of specific distributions
General aspects HTTP traffic model WAP traffic model E-mail traffic model FTP traffic model MMS traffic model SMS traffic model Summary
Page 6
Siemens, 2004

A generic structure of traffic modeling (UMTS packet traffic model) Sessions Packet Calls/Downloads Read Time (Viewing Time) Packet Inter-arrival Time
Packet Size
Page 7
Siemens, 2004

Sessions a session groups a sequence of user activities to a whole the arrival of sessions is modeled as Poisson process e.g.: web surfing, downloading, e-mail reading
General aspects HTTP traffic model WAP traffic model E-mail traffic model
Packet Calls/Downloads one or several packet calls form a session (it depends on traffic type) a packet call = download of the data volume of an application e.g. e-mail with attachment
Page 8
Siemens, 2004

Read time (Viewing Time) it represents the time span between two consecutive packet call requests (when user is reading or downloading e-mail etc.)
Packet Inter-arrival Time

it denotes the time spans between the arrival of two subsequent packets within a packet call
Packet Size it denotes the data volume at the application layer
Page 9
Siemens, 2004

Typical traffic session
First datagram arrival Datagrams Last datagram arrival
General aspects HTTP traffic model WAP traffic model
A packet call
E-mail traffic model FTP traffic model MMS traffic model SMS traffic model Summary
A packet service session
Different session arrive at the system independently: therefore the arrival can be modeled as Poisson process However, arrival of packet calls within a session and arrival of packets within a call are not independent of each other Different arrival rates are modeled by different packet interarrival times. The following arrival have been adapted to (E)GPRS: 4, 8, 16, 24, 32 kbps
Page 10
Siemens, 2004

UMTS traffic model is closely related to internet traffic of HTTP sessions
It does not take into account other types of traffic like email, SMS, WAP or FTP
A further improvement in the traffic modeling is necessary in order to consider other traffic sources and mix of them
Page 11
Siemens, 2004

Packet traffic model and dimensioning
1.) Well known Erlang formula cannot be used 2.) No other general analytical approach to dimension packet data traffic General aspects HTTP traffic model WAP traffic model E-mail traffic model FTP traffic model MMS traffic model SMS traffic model Summary
Simulation necessary to obtain dimensioning data packet data of a certain mean amount of data per hour generated with a assumed data rate and sent through an air interface as a result, for each arrival rate there is a set of tables with mean delay etc. as a function of mean traffic and available air interface bandwidth
Page 12
Siemens, 2004

Typical packet traffic (one session scenario)
General aspects HTTP traffic model
Packet Size (kbit)
Session
WAP traffic model E-mail traffic model FTP traffic model
WWW-Page
Packet
Time (s)
Radio Planning and Traffic Engineering for GSM Phase 2+ Data Services, S.Weisgerber, 1999
Page 13
Siemens, 2004

Sessions of several subscribers multiplexed during BH
General aspects air interface bandwidth HTTP traffic model WAP traffic model E-mail traffic model FTP traffic model
Delay (s)
BH (Busy Hour)
Mean delay simulation results

(k bp s)
Source: Dr. S. Weisgerber
Radio Planning and Traffic Engineering for GSM Phase 2+ Data Services, S.Weisgerber, 1999
Page 14
D at
Traffic
(Mbit/h
R at
on
U m
Siemens, 2004
HTTP traffic model

WWW browser displays WWW pages that are composed of one or more WWW objects
WWW page contains: - several different objects such as text and images - links connected to an identifier of a WWW resource, an Unified Resource Locator (URL)
When the user chooses a link, a new object or page is displayed By the direct specification of a URL in the text field of the WWW browser, a specific page or object can be chosen by the user Every object of the WWW has a unique URL
Szymon Nowak ICM SDC NMR1 Page 15 Siemens, 2004
HTTP traffic model

WWW is characterized by client-server architecture - a WWW browser represents a client that poses requests to a WWW server concerning the transmission of WWW objects that are stored on the server - the communication between client and server is controlled by the Hypertext Transfer Protocol (HTTP) HTTP protocol is an application-oriented protocol that uses the Transport Control Protocol (TCP) for end-toend transport In the initial version of HTTP a new TCP connection is set up for each requested object
Page 16
Siemens, 2004
HTTP traffic model

The way how it works 1.) The client transmits a request for a certain object to the server 2.) The request contains the URL of the object, data format parameters and parameters for access control
General aspects HTTP traffic model WAP traffic model E-mail traffic model FTP traffic model MMS traffic model SMS traffic model
3.) The server processes the request and transmits the requested object to the client
4.) TCP connection is released
Summary
Page 17
Siemens, 2004
HTTP traffic model

Newer HTTP versions (e.g. 1.1)
General aspects HTTP traffic model - TCP connections can be reused by the following objects - several TCP connections can be set up in parallel to be used for the pipelined transmission of several different objects WAP traffic model E-mail traffic model FTP traffic model MMS traffic model SMS traffic model Summary
persistent TCP connections
pipelined TCP connections
Page 18
Siemens, 2004
HTTP traffic model

Structure of WWW page
uhsdiuhfsuh ijfsfdsifijs kflokokokof ko uhsdiuhfsuh ijfsfdsifijs kflokokokof ko
General aspects HTTP traffic model WAP traffic model E-mail traffic model FTP traffic model MMS traffic model
uhsdiuhfsuh ijfsfdsifijs kflokokokofko
read time
uhsdiuhfsuh ijfsfdsifijs kflokokokofko
page 1
page n
picture links text
t OBJECT
object1 object2 objectm
size m
SMS traffic model Summary
page 2
Page 19
Siemens, 2004
HTTP traffic model

The most known traffic models
Adapted Mosaic WWW mode

- it describes HTTP traffic with a large number of objects - objects size quite large
Chois Behavioral Model of Web Traffic

- newer than adapted model -ON/OFF model with alternating phases of packet generation and silence
WAP traffic model E-mail traffic model FTP traffic model MMS traffic model
Not suitable for mobile applications
Page 20
Siemens, 2004
HTTP traffic model

Chois behavioral model of Web Traffic
General aspects HTTP traffic model WAP traffic model E-mail traffic model FTP traffic model
ON phase
-it starts after the arrival and acceptance of a web request -during the phase, the objects of a WWW page are requested PAGE LOADING TIMES
OFF phase
- it represents a silence period after all objects have been retrieved PAGE VIEWING TIMES
Page 21
Siemens, 2004
HTTP traffic model

General aspects
WWW activity WWW activity
HTTP traffic model t WAP traffic model E-mail traffic model FTP traffic model
Main Object
ON phase
OFF phase
read time
Inline Object Inline Object Main Object Inline Object Inline Object
MMS traffic model t SMS traffic model Summary
The pages objects are downloaded
Page 22
Siemens, 2004
HTTP traffic model

Main Object
the file containing an HTML document
Inline Object
linked objects, images or JAVA applets; to fetch all those inline objects modern browsers open several TCP connections in parallel
WAP traffic model E-mail traffic model FTP traffic model MMS traffic model SMS traffic model Summary
Choi WWW traffic model parameters

WWW parameter viewing time [s] No. of inline objects per page Size of main object [kbyte] Size of inline object [kbyte] Distribution Weibull Gamma Log-Normal Log-Normal
Page 23
Siemens, 2004
WAP traffic model

Why is WAP necessary? - once the graphic-enhanced web services could not be brought to and displayed on thin clients, e.g. GSM mobile phones - IP was not applicable in some environments (e.g. WAP over SMS)
General aspects HTTP traffic model WAP traffic model E-mail traffic model
WAP 1.x/2.0 - WAP 1.2.1 still used in many mobile terminals - in 2001 WAP 2.0 has been released, however WAP 1.2.1 hasnt been eradicated yet
Page 24
Siemens, 2004
WAP traffic model

WAP 1.x/2.0 - WAP 2.0 converges with widely used Internet protocols like TCP and HTTP - as WAP 1.2.1 is still commonly used the traffic model presented is based on this protocol Difference between WAP and other Internet protocols
WDP (Wireless Datagram Protocol) provides an unacknowledged datagram transport only In-order delivery and retransmission are handled by a separate transport layer WAP works in a transaction-oriented way It avoids overhead and delay for services that operate on a connectionless basis It provides these functions only if they are requested by a higher-layer service The amount of data that can be transferred by one transaction defaults to 1400 byte. It can be negotiated at WSP (Wireless Session Protocol) session setup time
WSP implements all feature of HTTP 1.1 and enhances these by a binary encoding aiming at greater efficiency over the air.
Page 25
Siemens, 2004
WAP traffic model

WAP architecture (WAP 1.2.1)
Content
Encoded Response
CLIENT
Encoded Request
GATEWAY
Request
ORIGIN SERVER
CGI scripts, etc.
WAE
Encoders and Decoders
Response (Content)
Page 26
Siemens, 2004
WAP traffic model

Why WAP gateway is necessary?
- it is not possible to run WAP end-to-end to regular Internet sites due to some optimization and different protocols - instead WAP Gateway must be used - main service a WAP Gateway provides is a protocol relay function between WAP stack and Internet stack
WAP traffic model E-mail traffic model FTP traffic model MMS traffic model SMS traffic model Summary General aspects HTTP traffic model
WAP traffic model [Stuckmann]
as same as HTTP model of Choi and Limbs, but other probability and parameter values
Szymon Nowak ICM SDC NMR1 Page 27 Siemens, 2004
WAP traffic model

Main characteristic of the model very small packet sizes (following gamma distribution) a limited value of the packet size (1400 byte) a WAP session = several requests for a deck (performed by user) - the model of the session can be seen as general for WAP sessions but the parameters depend on the content - the parameters taken here are typical for WAP applications directly after introduction of WAP - the parameters of the model are subject to future updates
Page 28
Siemens, 2004
WAP traffic model

WAP session sequence chart
General aspects
Deck 1
tread
Deck 2
Deck n
HTTP traffic model WAP traffic model E-mail traffic model FTP traffic model MMS traffic model
tresponse
Client to Gateway (Request for Decks) Size x
Gateway to Client Size y
Page 29
Siemens, 2004
WAP traffic model

WAP session can be described by
General aspects 1.) request for a number of decks 2.) packet size in up- downlink, size x and size y 3.) a reading time the user takes before requesting the next deck, 4.) a response time of the network, response HTTP traffic model WAP traffic model E-mail traffic model FTP traffic model Again, two state model (ON/OFF) can be considered, alternating between an activity phase and an idle phase. MMS traffic model SMS traffic model Summary
tread
Page 30
Siemens, 2004
WAP traffic model

Similarity to HTTP traffic
General aspects
DECK
- it can be considered as a web page

- it comprises several cards that can perform certain actions like a choice menu, linking between cards etc.
MAIN OBJECTS
A DECK can be compared to a packet call at HTTP

INLINE OBJECTS
Difference between HTTP and WAP

- the structure and size of viewed page; WAP page will be smaller due to its binary encoding and additionally no or less and smaller inline objects
Page 31
Siemens, 2004
WAP traffic model

WAP traffic model parameters
General aspects
WAP parameter decks per session intervals between decks [s] size of Get Request packet [s] size of Get Request packet [s]
Distribution geometric negative exponential log2-normal log2-normal
Page 32
Siemens, 2004
E-mail traffic model

The most popular protocols to transmit e-mails are: SMTP, POP3 and IMAP
POP3 and IMAP are widely used to download e-mail from a so-called mail-drop service (store-and-forward concept) TCP protocol is used for e-mail transfer as the end-toend transport protocol
CRUCIAL PARAMETER
size of the e-mail
Page 33
Siemens, 2004

Paxsons e-mail model - it describes load arising with the transfer of messages performed by a user - the only parameter: e-mail size
E-mail parameter
E-mail size (lower 80%) [byte]
Distribution Log2-normal Log2-normal constant
E-mail (upper 20%) [byte] Base quota [byte]
the base quota is assumed to be a fixed overhead the lower 80% - text-based mails the lower 20% - mails with attached files
Page 34
Siemens, 2004

ON/OFF model
General aspects
Assumptions: - arrival of messages is following Poisson process - two phases can be distinguished: ON phase and OFF phase - an ON period time during the message is being downloaded - an OFF period time when user is reading a message
Message arrivals to Inbox (Poisson distribution)
Message downloading
ON OFF ON OFF ON
Start of reading phase

Start of message downloading
Page 35
Siemens, 2004

ON/OFF model - e-mail message size follows Weibull distribution (empirical analyses) - based on two-stage Weibull distribution:
mean volume of an email without attachment is 5044 bytes (GEPARD)
mean volume of an email with attachment is 72257 bytes (GEPARD)
- the length of the OFF period follows Pareto distribution - the number of e-mail messages to be downloaded (no. of ON periods) during a session depends on:
number of messages arrived at the e-mail server since the last e-mail session number of messages that the user selects to read during the e-mail session
Page 36
Siemens, 2004
FTP traffic model

FTP (File Transfer Protocol) - developed to enable the safe, secure and efficient file transfers between computers - an unidirectional transfer (from FTP server to FTP client) - downlink represents the bottleneck in cellular networks FTP session can be described by
the total bulk of data per session
- it characterizes the duration of session
the size of each transferred object the interval between two object transmissions
Page 37
Siemens, 2004
FTP traffic model

FTP traffic model parameters FTP parameter Total amount of data [byte] Interval between connections [s] Distribution Log2-normal Log10-normal
Amount of data per file [byte] Log2-normal
The importance of FTP is decreasing with the upcoming of HTTP downloads! For this reason
FTP user models available in the literature are rather old!
Page 38
Siemens, 2004
MMS traffic model

The Multimedia Messaging Service (MMS) intended to provide a rich set of content. e.g. images, photos in combination with voice or text MMS notifications inform the MS about a received message (only MMS header)
The purpose of the notification is to allow the client to directly fetch a multimedia message from the location indicated in the notification
MMS presentation is done by means of ordering, layout, sequencing and timing of multimedia objects on the terminal screen
Page 39
Siemens, 2004
MMS traffic model

MMS traffic model
General aspects several components of an MMS correspond to different applications, like e-mail or WWW browsing
HENCE
existing traffic models can be applied for an MMS traffic model (e.g. e-mail)
Typical sizes of first multimedia messages are predicted to 20 kbyte and the maximum size because of memory restrictions is expected to be 100 kbyte
Page 40
Siemens, 2004
SMS traffic model

Analogous to the e-mail model
General aspects
Following assumptions have to be taken: - short arrival messages is described by Poisson process - a GPRS/EGPRS terminal is always in one of the states: ON/OFF - in OFF state the messages are queued on the SMS server - a number of short messages during a reading phase can be neglected
Page 41
Siemens, 2004
Summary
In order to packet data traffic simulations need to be carry out Different services like HTTP, WAP etc. are represented by specific traffic models UMTS specification (30.03) proposes a general model of packet data traffic Each service has to be considered separately due to different traffic characteristics caused by user behavior and application properties
Page 42
Siemens, 2004
Thank You for Your Attention
Siemens Information and Communication Mobile Networks and Solutions
Office Address: Siemens ICM SDC NMR1 ul. Strzegomska 54A PL 53-611 Wroclaw
Phone: 7992 - 373 Fax: 7992 - 320 Szymon Nowak ICM SDC NMR1 e-mail: szymon.nowak@siemens.com +48 71 +48 71
Page 43
Siemens, 2004

Traffic Models: Szymon Nowak Icm SDC Nmr1

Caricato da

Informazioni sul documento

Descrizione originale:

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Traffic Models: Szymon Nowak Icm SDC Nmr1

Caricato da

Copyright:

Formati disponibili

Traffic models

Szymon Nowak ICM SDC NMR1

General aspects of data traffic modeling

HTTP traffic model

Szymon Nowak ICM SDC NMR1

General aspects of data traffic modeling

Independent arrivals of calls

Exponentially distributed call durations

- service blocking probability

Szymon Nowak ICM SDC NMR1

General aspects of data traffic modeling

Data traffic planning

MMS traffic model SMS traffic model Summary

Szymon Nowak ICM SDC NMR1

General aspects of data traffic modeling

Mean throughput Peak throughput Mean delay 95%ile delay

How to dimension data traffic then?

Szymon Nowak ICM SDC NMR1

General aspects of data traffic modeling

Szymon Nowak ICM SDC NMR1

General aspects of data traffic modeling

Szymon Nowak ICM SDC NMR1

General aspects of data traffic modeling

Szymon Nowak ICM SDC NMR1

General aspects of data traffic modeling

Packet Inter-arrival Time

Packet Size it denotes the data volume at the application layer

Szymon Nowak ICM SDC NMR1

General aspects of data traffic modeling

General aspects HTTP traffic model WAP traffic model

A packet service session

Szymon Nowak ICM SDC NMR1

General aspects of data traffic modeling

Szymon Nowak ICM SDC NMR1

General aspects of data traffic modeling

Szymon Nowak ICM SDC NMR1

General aspects of data traffic modeling

WAP traffic model E-mail traffic model FTP traffic model

MMS traffic model SMS traffic model Summary

Szymon Nowak ICM SDC NMR1

General aspects of data traffic modeling

Mean delay simulation results

MMS traffic model SMS traffic model Summary

Source: Dr. S. Weisgerber

Szymon Nowak ICM SDC NMR1

HTTP traffic model

HTTP traffic model

Szymon Nowak ICM SDC NMR1

HTTP traffic model

4.) TCP connection is released

Szymon Nowak ICM SDC NMR1

HTTP traffic model

persistent TCP connections

pipelined TCP connections

Szymon Nowak ICM SDC NMR1

HTTP traffic model

uhsdiuhfsuh ijfsfdsifijs kflokokokofko

uhsdiuhfsuh ijfsfdsifijs kflokokokofko

picture links text

SMS traffic model Summary

Szymon Nowak ICM SDC NMR1

HTTP traffic model