OpenAirInterface.

org Radio Network

Modeling
Florian Kaltenberger
July 6, 2011
Overview
1
Channel modeling basics
2
Implementation on OpenAirInterface.org platform
3
PHY Layer Abstraction basics
4
Implementation on OpenAirInterface.org platform
1. Channel Characterization Basics
Path loss and Fading (1)
Path loss is the attenuation of the signal between transmitter and
receiver.
P
RX
=
P
TX
PL
P
RX
|
dB
= P
TX
|
dB
PL|
dB
It contains the following factors
PL = PL(d) SF SSF
PL|
dB
= PL(d)|
dB
+ SF|
dB
+ SSF|
dB
PL(d) deterministic path loss
SF large-scale (shadow) fading
SSF small scale fading
Path loss and Fading (2)
Deterministic path loss
distance dependent loss in signal energy
proportional to d
n
, where d is the distance and n is the path loss
exponent
typicall values n [2, 6], depending on terrain and foilage
Large-scale (shadow) fading
Deviation of received signal energy from path loss
Caused by obstruction
Small scale fading
Rest of constructive and destructive combination of multipaths
Path loss and Fading (3)
Received power of a terminal in a rural area
1
.
1
Measurements were taken with OpenAirInterface.org platform at 859.5MHz close to
Ambialet, France in collaboration with the CNES
Deterministic Path Loss
PL(d) =

4d

2
0 d d
break
PL(d) = PL(d
break
)

d
d
break

n
d > d
break
distance dependent loss in signal energy
proportional to d
n
, where d is the distance and n is the path loss
exponent
typicall values n [2, 6], depending on terrain and foilage
Other more sophisticated models:
Okumura-Hata
Walsh-Ikegami
Motley-Keenan (indoor)
Large Scale fading
Deviation of average received signal energy from deterministic
path loss
Averaging done over a small area (a few wavelengths)
Is usually attributed to multiple interactions of the signal with the
enviroment
A large number of these interactions results in a log-normal
distribution
pdf(L|
dB
) =
1

2
F
|
dB
exp

L
2
|
dB
2
2
F
|
dB

(1)
This distribution matches measurements very well with

F
|
dB
4. . . 10 dB.
Small Scale Fading
Small scale fading results from constructive and destructive
combination of multipaths
No dominant component Rayleigh Fading
Dominant component (LOS) Ricean fading
Other distributions also possible
Wideband channel models
WSS-US channels can be simulated using a tapped delay line
model
h(t , ) =
N1

l =0
a
l
(t )e
j
l
(t )
(
l
)
Each tap iself can be characterized by a Rayleigh or Ricean
distribution
Mean tap power determined by power delay prole
z
-1
s
m
H
m,0
z
-1
H
m,1
z
-1
H
m,2
H
m,N-1
r
m
Standardized MIMO models (3GPP)
Different channel models for different purposes spread over
several 3GPP docs
The full 3GPP MIMO channel model is specied in TS 25.996
Simplied 3GPP model for link level simulations (SCM-A,B,C,D)
in TS 25.814
Radio frequency (RF) system scenarios (pathloss models) in TR
36.942
LTE specic test cases for system simulation: TS 36.814
LTE specic link level channel models (EVA, EVB, ETU) for UE
testing (TS 36.101) and eNB testing (TS 36.104)
OpenAirInterface Channel Models
Currently OpenAirInterface provides
Pathloss model: Generic L = P
0
+ 10n log
10
(d), where d is the
distance between eNb and UE (given by the mobility model)
Antenna models for sectorized eNBs from 3GPP TR 36.942
Small scale fading models:
Generic tapped delay line with Rayleigh fading (rst tap can be
Ricean)
First order AR model to model time variation
Generic Kronecker correlation model for MIMO channels
SCM-A,B,C,D from TS 25.814 and EVA, EVB, ETU from TS
36.101/TS 36.104
In progress
Shadow fading (incl correlation)
Channel Modeling in OpenAirInterface
Important data structures
Top-level config structure for all channel/RF
parameters: environment_system_config
Linked list of eNBs and UEs (node_list_struct)
Channel descriptor (chan_desc_t)
Channel Modeling in OpenAirInterface
environment_system_config
Node_struct
Channel_desc_t
Node_struct
...
Channel_desc_t
...
N
N*M
Node_list_struct
OpenAirInterface Emulator
Node_struct
Node_struct
...
Node_list_struct
M
eNB
UE
2. PHY layer abstraction
Motivation
What is PHY abstraction?
Prediction model for modem performance (BLER) based on current
channel state (per subcarrier SINR)
Why PHY abstraction
Enables fast simulation of PHY layer performance for system level
simulation
Can be used to compute terminal feedback (CSI)
Basic idea
Predict performance of modulation and coding from the channel
Multi-state channel characterized by SINR
j
, j = 1, . . . , J
Compress
j
, j = 1, . . . , J into one effective SINR
eff
Use
eff
to look up performance from pre-calculated performance
curves
Abstraction Methods
In other words

eff
=
1
I
1

1
J
J

j =1
I

where
I(
j
) is a mapping function from the SINR to some information
measure

1
and
2
are calibration factors
Mapping functions
Exponential effective SINR: derived from the Union-Chernof
bound of error probabilities
I(
j
) = 1 exp(
j
)
Mutual information effective SINR:
I
M
1
(
j
) =
logM
1

1
M
1

x
1

1
E
z
1
log

1
exp

x
1
x

+ z
1

exp

|z
1
|
2

where
1
is the set of the QAM constellation points with
|
1
| = M
1
and z
1
CN(0, 1)
Quality mapping
Based on link-level AWGN results
Effective SINR can used to look up
BLER for a particular MCS
10 5 0 5 10 15 20 25
10
3
10
2
10
1
10
0
effective SINR
B
L
E
R


mcs0(QPSK)
mcs1(QPSK)
mcs2(QPSK)
mcs3(QPSK)
mcs4(QPSK)
mcs5(QPSK)
mcs6(QPSK)
mcs7(QPSK)
mcs8(QPSK)
mcs9(QPSK)
mcs10(16QAM)
mcs11(16QAM)
mcs12(16QAM)
mcs13(16QAM)
mcs14(16QAM)
mcs15(16QAM)
mcs16(16QAM)
mcs17(64QAM)
mcs18(64QAM)
mcs19(64QAM)
mcs20(64QAM)
mcs21(64QAM)
mcs22(64QAM)
mcs23(64QAM)
mcs24(64QAM)
Quality mapping
Based on link-level AWGN results
Effective SINR can used to look up
Troughput
20 10 0 10 20 30 40
0
1
2
3
4
5
6
7
8
9
x 10
6
SNR [dB]
T
h
r
o
u
g
h
p
u
t

[
b
p
s
]


Modem performance
Mutual information
L2 Protocols
PHY Procedures
OAI Network Interface
L3 Protocols
PHY
Mod.
Coding Decoding
Demod.
Convolution
Signal
Uncoded msg
Channel Realization
Channel Trace
Mobility Gen
EMOS
C
h
a
n
n
e
l

M
o
d
e
l
P
a
t
h

L
o
s
s
PHY Abstraction for Emulation
Coded msg
PHY Abstraction
UE MAC / PHY Interfaces
SI/RA
Proc
Measurement
Procedures
ULSCH/DLSCH
MUX/SCHED
MAC (36-311)
PHY Proc.
(36-213)
Abstraction
And Emulation
Medium
u
e
_
s
e
n
d
_
s
d
u
u
e
_
d
e
c
o
d
e
_
S
I
u
e
_
g
e
t
_
s
d
u
f
i
l
l
_
r
a
r
To be
abstracted
g
e
n
e
r
a
t
e
_
p
r
a
c
h
_
e
m
u
l
r
x
_
p
h
i
c
h
_
e
m
u
l
d
c
i
_
d
e
c
o
d
i
n
g
_
p
r
o
c
e
d
u
r
e
s
_
t
o
p
_
e
m
u
l
u
l
s
c
h
_
e
n
c
o
d
i
n
g
_
e
m
u
l
d
l
s
c
h
_
d
e
c
o
i
d
n
g
_
e
m
u
l
l
t
e
_
u
e
_
m
e
a
s
u
r
e
m
e
n
t
s
_
e
m
u
l
l
t
e
_
s
y
n
c
_
t
i
m
e
_
e
m
u
l
u
e
_
o
u
t
_
o
f
_
s
y
n
c
h
_
i
n
d
u
e
_
p
r
o
c
e
s
s
_
r
a
r
u
e
_
g
e
t
_
r
a
c
h
p
h
y
_
s
y
n
c
h
_
s
u
c
c
e
s
s
g
e
n
e
r
a
t
e
_
s
r
s
_
e
m
u
l
r
x
_
p
b
c
h
_
e
m
u
l
Already
abstracted
eNB MAC / PHY Interfaces
RA
Proc
Measurement
Procedures
ULSCH/DLSCH
Scheduling
MAC (36-311)
PHY Proc.
(36-213)
Abstraction
And Emulation
Medium
u
l
s
c
h
_
d
l
s
c
h
_
e
N
B
_
s
c
h
e
d
u
l
e
r
i
n
i
t
i
a
t
e
_
r
a
t
e
r
m
i
n
a
t
e
_
r
a
g
e
t
_
D
C
I
_
s
d
u
f
i
l
l
_
r
a
r
g
e
t
_
d
l
s
c
h
_
s
d
u
r
x
_
s
d
u
To be
abstracted
g
e
n
e
r
a
t
e
_
p
s
s
_
e
m
u
l
g
e
n
e
r
a
t
e
_
p
h
i
c
h
_
e
m
u
l
g
e
n
e
r
a
t
e
_
d
c
i
_
t
o
p
_
e
m
u
l
d
l
s
c
h
_
e
n
c
o
d
i
n
g
_
e
m
u
l
l
t
e
_
I
O
_
m
e
a
s
u
r
e
m
e
n
t
s
_
e
m
u
l
l
t
e
_
s
y
n
c
_
t
i
m
e
_
e
m
u
l
g
e
n
e
r
a
t
e
_
p
b
c
h
_
e
m
u
l
u
l
s
c
h
_
d
e
c
o
d
i
n
g
_
e
m
u
l
r
x
_
u
l
s
c
h
_
e
m
u
l
\frame{
\frametitle{OpenAirInterface Channel models}
Navid.nikaein@eurecom.fr
Openairinterface Emulation
Platform and Methodology
This work is licensed under a CC attribution
Share-Alike 3.0 Unported license.
Attribution: You must attribute this work to the author(s).
Commercial: You may use this work for commercial purposes.
Derivative Works: If you alter, transform, or build upon this work, you may distribute the resulting work only under the same,
similar or a compatible license.
GNU GPL License
Agenda
Introduction
OAI Emulation methodology
Experiment design
Architectural design
Hardware platforms
OAI Emulation process and usage
Additional tools
OAI Web tools and development area
Case study
MESH: CHORIST, and HNPS
LTE: LOLA, CONECT
Reference
7-8/07/2011
Introduction
Next generation wireless systems are becoming
complex
Evolving cellular network (LTE/LTE-A)
Adhoc/mesh networks
Need a reliable performance evaluation
Analytical approach is difficult
Stochastic factors from channel/mobility/traffic
Experimental approach
Simulation
Emulation
Real testbeds
7-8/07/2011
A brief Comparison
Simulation
No interaction with the external entities (closed environment)
Part or all of the elements of a network/system is modeled or abstracted
Emulation
Bring the external elements with their I/O streams (open environment)
Decision on which element is real or modeled depends on the use case
and purpose of the experiments
At least one thing is modeled
Real testbed
All the elements are real
Part of the testbed maybe controlled
7-8/07/2011
Classification of Validation Platforms
Analytical
UML
FreeMat
IDL
Matlab
SciLab
Octave
Simulation
Sinalgo
NetSim
GloMoSim/Qualnet
NS-3
Opnet
Omnet++
Emulation
NistNEt
CORE
USPR2
WARP
CMU-DSR
ORBIT
OAI
Real Testbed
PlanetLab/OneLab
NITOS
GnuRadio
WARP
ORBIT
Sundance, BEE2,
WiTestLab
OAI
Scalability Reproducibility Applicability
Abstraction Level Realism Level
7-8/07/2011
A brief Comparison
Experiment Scenario
Setup
Abstraction /
Modeling
Reproducibility Scalability /
Costs
Limitation Net Traffic &
Mobility
Analytical +++ - +++ +++ CPU/
Abstracted/
Modeled
Simulation ++ + +++ ++ Abstraction Modeled
Emulation + ++ ++ ++ CPU/Cost
Modeled
/ Real
Real
Testbed
- NA - - Cost Real
7-8/07/2011
Purpose of an Experimentation
Examine properties of an existing, planned and/or
non-ideal network
Validation and integration
Performance evaluation (app and proto)
System testing and optimization
7-8/07/2011
OAI NETWORK EMULATION
METHODOLOGY
7-8/07/2011
OAI Emulation platform
An open HW/SW platform for innovations in emerging
air interface technologies as well as wireless
networking
Complete system including layer 1/2/3 platform
interconnected to Linux IP protocol stack in a controlled
laboratory environment
This work is licensed under a CC attribution
Share-Alike 3.0 Unported license.
GNU GPL License
7-8/07/2011
OAI Emulation Methodology
Specify experiment and architectural design with the
following properties
Reproducibility
repeat the experiment in the controlled environment
Scalability
run medium-to-large scale networking experimentations
Applicability
represent a set of realistic scenarios and use-cases
Simulation
Soft Realtime
Emulation
Hard Realtime
Emulation
Real Testbed
Scalability Reproducibility Applicability
Abstraction Level Realism Level
7-8/07/2011
Key Features
Real time distributed validation environment with a real
setting with/without RF equipments
Real protocol stack implementation
End-to-end IPv4/IPv6 packet transition with QoS support
Repeat the experiment and compare the results in fair and
realistic conditions
Emulate a medium-to-large scale networks on one or more
machines
7-8/07/2011
Building Blocks
Linux IP network interface
Real L1/L2/L3 protocol stack (not modeled)
PHY Abstraction
Modem, physical channels, along with propagation
Emu transport mechanism (or combination)
Direct memory transfer for realtime behavior with virtualized
protocol stack
Ethernet (ip multicast) not realtime
ECOS and RTNET support realtime Ethernet
A set of tools
L2 Protocols
PHY Procedures
Emulation Medium
OAI Network Interface
L3 Protocols
PHY Abstraction
7-8/07/2011
OAI Emulation Workflow
UE 0
UE 1
UE 2
eNB 0
Emulation Platform
Web Interface
Results
DB
NOT SYNCHED
ATTACHED
CONNECTED
SYNCHED
7-8/07/2011
Use Cases
Protocol implementation validation
Enables developers of L2/L3 and applications to test their
implementation in a real-time setting without the need for RF
equipment
Repeatable and scalable real-time experiments (hundreds of nodes)
System performance evaluation
For L2/L3 protocol and application assessment
Use of accurate and fast PHY abstraction models
Possibility of using / combining
Real channel measurement traces as simulation stimulus (input
from EMOS)
Real live network with RF equipment interconnected with the
emulation platform
7-8/07/2011
EXPERIMENT DESIGN
7-8/07/2011
Experiment Design
Allow reproducibility of the experiment
Concept of sequential experiment workflow
the output of each step will be the input of the next
OAI defines five consecutive steps, and each step is
split into several sub-steps function of data nature
Scenario descriptor
Configuration
Execution
Monitoring
Analysis
7-8/07/2011
Experiment Design
Analysis
Performance Evaluation Protocol Validation System Testing
Monitoring
Execution Logs Packet Traces
Execution
Debug Mode Soft Realtime Mode Hard Realtime Mode Realtime RF
Configuration
Network Interface Traffic/Mobility Protocol Stack PHY/RF Abstraction
Scenario Description
Environment/System Network Topology Application EMU IO Parameters
7-8/07/2011
Basic Scenario Descriptor
build the layout of an experiment
Environment / System
Pathloss model
Channel Model
SCM (3GPP 36.384)
Antenna description
System bandwidth
System frequency
Network Topology
Area
Nodes descriptors
ENB/CH vs. UE/MR
Distribution
Static, random, grid
Average distance
Mobility model
Static, RWP, Rwalk, Grid
Moving dynamics
Speed, pause time, journey
time
7-8/07/2011
Basic Scenario Descriptor
build the layout of an experiment
Traffic
Type
VoIP, M2M, Gaming
Packet size and Inter-
arrival time
Constant
Uniform
Exponential
Poisson
ON-OFF
Emu I/O Params
Emu time
Log level / Layer
Packet trace / Layer
Wireshark Interface
Performance metrics /
Layer
Seed
Random, user-specific
7-8/07/2011
Configuration
define a sequence of component s initialization
XML Gen
scenario is translated / defined in xml format
Config Gen (OCG)
Process xml file
Compute config parameters
Initialize and configure operation of all components
Example: when to generate traffic? Which mobility model?
Config Gen
Pkt Tracer
Mobility Gen
Traffic Gen
Log Gen
Env/sys
Net
App
Emu I/O
Scenario Descriptor
XML Gen
L2 Protocols
PHY Procedures
Emulation Medium
OAI Network Interface
L3 Protocols
PHY Abstraction
RB Conf. Gen.
7-8/07/2011
Execution
synchronize nodes and run the experiment
Mode
1. Debug Mode
Access stratum user space + no IP driver an
2. Soft Realtime mode
Access stratum user space + Driver in Kernel
3. Hard Realtime Mode
Access stratum RTAI kernel + Driver in kernel
4. Realtime RF Mode
Hard Realtime Mode + HW + Attenuator
Type
1. One instance / machine
IP multicast through Ethernet
2. Several instances / machine (Virtualization)
Shared memory
7-8/07/2011
Monitoring
watch the experiment in real time
Passive monitoring (sniffer)
Execution and performance logs
Active monitoring
Check and control performance metrics and protocol
signaling during the experiment
Online and offline capabilities
Command line interface
Label and archive raw data
7-8/07/2011
Analysis
process raw data and produce statistics
Raw data Processing
Correlating and examining user plane traffics
Filtering and extracting protocol signaling
Results Generation and archiving
Key performance indicators (KPI)
Statistics
Design and implementation validation
7-8/07/2011
ARCHITECTURAL DESIGN
7-8/07/2011
Architectural Design
Scalability of the experiment
Protocol vitalization and parallelism
Optimized emulated data transport
Offloading capabilities depending on Hardware
Applicability of the experiment
Real protocol stack (not modeled) interconnected with Linux
TCP/IP network stack
Hard realtime and soft realtime operations (RTAI)
Attach real applications (emulate the remaining traffic)
Feed real channel traces
Interconnection with a live network
7-8/07/2011
Building Blocks
Scenario
Descriptor
XML format
Scenario
Results
External
Application
Dispatcher
Result Gen Console
External
Traffic Gen
Config Gen
Pkt Tracer
Mobility Gen
Traffic Gen
Log Gen
L2 Protocols
PHY Procedures
Emulation Medium
OAI Network Interface
L3 Protocols
PHY Abstraction
OAISIM - OAIEMU
RB Conf. Gen.
7-8/07/2011
Virtualization of Protocol Stack
Share the host kernel between
different emulated nodes /
instance
Parallelism : logical and useful
Logical: Each Node on separate
thread
Useful: Dynamic allocation of PHY
abstraction and channel modelling
on multiple thread
Other parallelism:
Compilation directives
Physical Machine
Application
Host OS

Hardware
Shared Kernel
(Host+ virtual instances)
Emulation Medium
Phy Abstraction
7-8/07/2011
Emulated Medium
Emulated data are exchanged through two techniques
Shared memory
IP multicast over Ethernet (or any other medium)
IP Multicast
Channel realization
Shared memory

Inst0
Inst1 Inst K
Physical Machine K
Inst 2
Channel realization
Shared memory

Inst0
Inst1 Inst K
Physical Machine 0
Inst 2

7-8/07/2011
Emulated Medium: IP Multicast Case
Requires barrier synchronization to achieve frame
synchronization among multiple instances / machines
Proceed per subframe, where the next subframe cannot start
until all nodes complete the previous subframe
Coordinated by the primary master (typically the first
machine in the emulation)
Limitation:
Dynamic join/leave of a physical machine in the multicast
group at anytime is not supported
7-8/07/2011
Emulation Medium
10.0.3.3.
10.0.2.2
10.0.1.2
10.0.1.1
Multicast Group
224.0.0.161
224.0.0.162
224.0.0.163
224.0.0.164
Primary Master
Secondary Master
7-8/07/2011
PHY Abstraction
Prediction model for modem performance (BLER) based on
current channel state (per subcarrier SINR)
Modem performnce: modulation and coding
Enables fast simulation of PHY layer performance for
system level simulation
Inject simulated error patterns for each transport
channel block traversing the MAC/PHY interface
PHY Abstraction is done at the receiver
Wideband SINR are computed on every subframe
Network topology
Pre-defined propagation model
7-8/07/2011
PHY Abstraction: 2 Modes
L2 Protocols
PHY Procedures
OAI Network Interface
L3 Protocols
PHY Abstraction
F(SNR, MCS)=P(BLER)
Channel Descriptor
L2 Protocols
PHY Procedures
OAI Network Interface
L3 Protocols
PHY
Mod.
Coding Decodin
g
Demod.
Convolution
Signal
Channel Trace
Mobility Gen
EMOS
Channel
Realization:
ENB2UE
UE2ENB
Same IF
Same IF as
with RF
Uncoded msg
Uncoded msg
C
h
a
n
n
e
l

M
o
d
e
l
P
a
t
h

L
o
s
s
7-8/07/2011
Radio Resource Control
System Information
RRC Connection management
Resource Configuration
QoS
Measurements reporting
Mobility management
Packet Data Convergence Layer
Header (De)Compression (ROHC)
Ciphering/Deciphering, Integrity
Data Transfer Procedures, Re-
establishment Procedure
In-sequence delivery
Radio Link Control
Segmentation and reassembly
Reliable data transfer
In sequence delivery
PHY
L2 Protocol Stack
Medium Access Control
Random Access
HARQ
Scheduling
DL/UL SCH Data Transmission
MUX/DEMUX, DRX
C
o
n
t
r
o
l

P
l
a
n
e
U
s
e
r

P
l
a
n
e
7-8/07/2011
L2 Protocol Stack
Signalling
Radio Bearers
(BCCH, CCCH)
Radio Resource
Control
(RRC)
PDCP
RLC-TM RLC-UM RLC-AM
RLC
Config.
PDCP
Config.
Unacknowledged
Radio Bearers
Acknowledged
Radio Bearers
MAC Scheduling Unit
(ULSCH/DLSCH)
SI/RA/MP
Procedures
MAC
Config.
Logical
Channels
PHY Procedures
Transparent
Mode
Data Plane Control Plane
7-8/07/2011
L2 Protocol Stack
RRC
System Information broadcast
RRC connection establishment
signalling data transfer
connection reconfiguration (addition and
removal of radio bearers, connection
release)
measurement collection and reporting at
UE and eNB
RLC - TM
RLC- UM
Segmentation, concatenation, and
reassembly
RLC- AM
Segmentation, concatenation, and
reassembly
Padding
Data transfer to the user
Error control and correction
NAS
middleware for interfacing IPv4/IPv6-
based mechanisms for signalling and user
traffic with 3GPP-specific mechanisms for
the access network
PDCP
IP-interconnection facilities with the RLC
MAC eNB
RRC interface for SI and CCCH
Schedulers
DCI generation
HARQ Support
RA procedures and RNTI management
RLC interface (AM, UM)
MAC UE
PDU and header formats
RLC interface (AM,UM)
RRC interface for SI and CCCH
7-8/07/2011
OAI Network Interface
Netlink socket for soft real time
mode: user spaceKernel Space
RTFIFOfor Hard realtime mode
using RTAI : kernel spcae
PHY Procedures
L2 Protocols
RTAI
Non-Access Stratum Driver
NAS Control Plane IP Packet Classification
IP
Kernel
7-8/07/2011
L3 Protocol Stack
PHY Procedures
L2 Protocols
Non-Access Stratum Driver
RTAI
Kernel
IP
Radio Resource Management
Topology & Connectivity Management
Local Routing
Forwarding
Routing /Multicasting
MIP
Data Plane
User
Control Plane
7-8/07/2011
E2E Validation
Real Application
Channel realization
Shared memory

Inst0
Inst1 Inst K
Real Application
Channel realization
Shared memory

Inst0
Inst1 Inst K
IP Multicast
Physical Machine 0 Physical Machine k

Emulated or True Core Network

Real Application
L2 Protocols
PHY Procedures
Emulation Medium
OAI Network Interface
PHY Abstraction
L2 Protocols
PHY Procedures
Emulation Medium
OAI Network Interface
PHY Abstraction
L2 Protocols
PHY Procedures
Emulation Medium
OAI Network Interface
PHY Abstraction
L2 Protocols
PHY Procedures
Emulation Medium
OAI Network Interface
PHY Abstraction
L2 Protocols
PHY Procedures
Emulation Medium
OAI Network Interface
PHY Abstraction
L2 Protocols
PHY Procedures
Emulation Medium
OAI Network Interface
PHY Abstraction
7-8/07/2011
Hard Real Time Operation
Designed to emulate the wireless
behavior in a real network
With real app and proto
Respects L2 frame timing strictly
sync wrt sample stream
L1/L2 protocols run using the
real-time kernel
RT Threads under RTAI
L3 networking makes use of
Linux networking stack
7-8/07/2011
Soft Real Time Operation
Designed to enable realistic large
scale emulation inside one or series
of machine(s)
Performance evaluation
Debugging protocol stack
Calibrated to respect L2 frame
timing on average
10us scheduling accuracy
MAC/PHY is a regular Linux process
With multi-threading
L3 networking makes use of Linux
networking stack
7-8/07/2011
eNB/CH Interface
RA
Proc
Measurement
Procedures
ULSCH/DLSCH
Scheduling
PHY Proc
Abstraction
u
l
s
c
h
_
d
l
s
c
h
_
e
N
B
_
s
c
h
e
d
u
l
e
r
i
n
i
t
i
a
t
e
_
r
a
t
e
r
m
i
n
a
t
e
_
r
a
g
e
t
_
D
C
I
_
s
d
u
f
i
l
l
_
r
a
r
g
e
t
_
d
l
s
c
h
_
s
d
u
r
x
_
s
d
u
g
e
n
e
r
a
t
e
_
p
s
s
_
e
m
u
l
g
e
n
e
r
a
t
e
_
p
h
i
c
h
_
e
m
u
l
d
l
s
c
h
_
e
n
c
o
d
i
n
g
_
e
m
u
l
l
t
e
_
m
e
a
s
u
r
e
m
e
n
t
s
_
e
m
u
l
l
t
e
_
s
y
n
c
_
t
i
m
e
_
e
m
u
l
g
e
n
e
r
a
t
e
_
p
b
c
h
_
e
m
u
l
u
l
s
c
h
_
d
e
c
o
d
i
n
g
_
e
m
u
l
r
x
_
u
l
s
c
h
_
e
m
u
l
RLC
m
a
c
_
r
l
c
_
d
a
t
a
_
r
e
q
m
a
c
_
r
l
c
_
d
a
t
a
_
i
n
d
m
a
c
_
r
l
c
_
s
t
a
t
u
s
_
i
n
d
c
a
n
c
e
l
_
r
a
PDCP
TM UM AM
RRC
p
d
c
p
_
d
a
t
a
_
i
n
d
p
d
c
p
_
d
a
t
a
_
r
e
q
p
d
c
p
_
c
o
n
f
i
g
_
r
e
q
rrc_rlc_config_req
rrc_rlc_data_req
rrc_data_ind
rrc_data_conf p
d
c
p
_
c
o
n
f
i
g
_
r
e
q
mac_rrc_lite_data_req
mac_rrc_lite_data_ind
7-8/07/2011
UE/MR Interface
Phy Proc
Abstraction
u
e
_
s
e
n
d
_
s
d
u
u
e
_
d
e
c
o
d
e
_
S
I
u
e
_
g
e
t
_
s
d
u
f
i
l
l
_
r
a
r
g
e
n
e
r
a
t
e
_
p
r
a
c
h
_
e
m
u
l
r
x
_
p
h
i
c
h
_
e
m
u
l
d
c
i
_
d
e
c
o
d
i
n
g
_
p
r
o
c
e
d
u
r
e
s
_
t
o
p
_
e
m
u
l
u
l
s
c
h
_
e
n
c
o
d
i
n
g
_
e
m
u
l
d
l
s
c
h
_
d
e
c
o
i
d
n
g
_
e
m
u
l
l
t
e
_
u
e
_
m
e
a
s
u
r
e
m
e
n
t
s
_
e
m
u
l
l
t
e
_
s
y
n
c
_
t
i
m
e
_
e
m
u
l
u
e
_
o
u
t
_
o
f
_
s
y
n
c
h
_
i
n
d
u
e
_
p
r
o
c
e
s
s
_
r
a
r
u
e
_
g
e
t
_
r
a
c
h
p
h
y
_
s
y
n
c
h
_
s
u
c
c
e
s
s
g
e
n
e
r
a
t
e
_
s
r
s
_
e
m
u
l
r
x
_
p
b
c
h
_
e
m
u
l
RA
Proc
Measurement
Procedures
ULSCH/DLSCH
Scheduling
RLC
PDCP
TM UM AM
RRC
p
d
c
p
_
d
a
t
a
_
i
n
d
p
d
c
p
_
d
a
t
a
_
r
e
q
p
d
c
p
_
c
o
n
f
i
g
_
r
e
q
rrc_rlc_config_req
rrc_rlc_data_req
rrc_data_ind
rrc_data_conf p
d
c
p
_
c
o
n
f
i
g
_
r
e
q
mac_rrc_lite_data_req
mac_rrc_lite_data_ind
m
a
c
_
r
l
c
_
d
a
t
a
_
r
e
q
m
a
c
_
r
l
c
_
d
a
t
a
_
i
n
d
m
a
c
_
r
l
c
_
s
t
a
t
u
s
_
i
n
d
7-8/07/2011
HARDWARE PLATFORMS
7-8/07/2011
Hardware Emulation Platforms
Standard PC Workstation PC Cluster ARMmodules GPU Workstation
Scalability vs. Cost
Processing Capability
Network Link Speed
RAM Latency
7-8/07/2011
L2
RF Emulation
Measurements, PHY Error
RTAI
L2
L2
L1/L2
IPv6, NAS Driver
Possible Hardware Platform
Gigabit Ethernet Switch
Machine 0
Frontend
Machine n-1 Machine 1 Machine 3
Machine 2 Machine 4 Machine n
V
L
A
N

E
X
P
Transport Emulated Data
Application Data
IPv4
IPv6

Software/Hardware Co-Design
CPU mono-thread vs. CPU multi-thread
QPI Channel
Core
&
Core2 Core 3
Core 0
C
a
c
h
e
RAM DDR3
(Dual or 3
channels)
QPI Channel
Core 1
Core 2 Core 3
Core 0
RAM DDR3
(Dual or 3
channels)
Bottleneck
C
a
c
h
e
7-8/07/2011
Software/Hardware Co-Design
GPU threading
GPU
PCI Express
RAM GDR5
I
n
t
e
r
n
a
l
B
u
s
GDR5 time faster than DDR3
PCI express speed = QPI
Channel speed
7-8/07/2011
OAI EMULATION PROCESS AND
USAGE
7-8/07/2011
OAISIM Emulation Process
Step 1: Generate/edit an xml configuration file
Step 2: OAISIMinitiates
All MAC/PHY structure
Log generation per sub-layer
Config generation for automatic detection/parsing of the XML
configuration file
Packet tracer for monitoring usre-plane and data-plane singling
Mobility generation for different node mobility pattern
Channel Modeling to calculate the propagation and fading
Traffic generator for user plane
Step 3: OAISIM runs the emulation
PHY procedures, layer 2 protocols, traffic generator, and packet tracer
PHY abstraction, channel modeling, and mobility generator
Emulation medium
Step 4: OAISIM outputs to Result Generation & Display.
7-8/07/2011
OAISIM Emulation Process
7-8/07/2011
Makefile
Support for -mmmx -msse -msse2 -m32 -msse4
Compilation Options:
DEBUG_PHY
NAS_NETLINK
OCG
Make
all, oaisim
rrc_cellular (cellular/mesh)
clean, cleanl1, cleanl2
Nasmesh, nasmesh_fix, install_nasmesh
printvars
archive
Documentation:
openair1 Ready, openair2/3 comming soon
Run doxygen in OPENAIRX_DIR/DOCS/DOXYGEN
7-8/07/2011
Usage
Command line using options
Command line using xml scenario descriptor with OCG
Web interface using html scenario descriptor with OCG
localhost/OpenAirEmu
EURECOM Portal
emu.openairinterface.org
7-8/07/2011
Command line
Usage:
oaisim-h -a -F -C tdd_config -R N_RB_DL -e x transmission_mod e -m target_dl_mcs -
r(ate_adaptation) -n n_frames -s snr_dB -k ricean_factor t max_delay -f forgetting factor -z
cooperation_flag -u nb_local_ue -U omg_model_ue -b nb_local_enb -B omg_model_enb -M
ethernet_flag p nb_master -g multicast_group -l log_level -c ocg_enable
Options
-F: enable FDD mode
-C: TDD configuration
-R: set number of RB DL
-e : activate extended prefix
-n: set the number of frames
-s : set a fixed SNR
-k: ricean factor
-t: delay spread
-f: forgetting factor
-x: set the transmission mode
-z: cooperation flag
-a: abstraction flag
-u: number of local UE/MR
-U: mobility model of UE/MR
-b: number of local eNB/CH
-B: mobility model of eNB/CH
-M: activate the distributed emulation
-p: set the number of physical machines
-g : set the multicast group id
-l: set the global log level
-c: activate the OCG
7-8/07/2011
Command line with OCG
Usage (make OCG=1):
Oaisim c template_1.xml
give the template manually with the following format: xxx_n.xml
oaisim c 1/2/3/4//n
Use/edit the existing templates in
target/SIMU/EXAMPLES/OSD/WEBXML OR
Add a new template template_k.xml k in
target/SIMU/EXAMPLES/OSD/WEBXML and run oaisim c k
7-8/07/2011
<OAI_EMULATION>
<TOPOLOGY_CONFIG>
<MOBILITY>
<UE_MOBILITY>
<UE_INITIAL_DISTRIBUTION>random</UE_INITIAL_DISTRIBUTION>
<RANDOM_UE_DISTRIBUTION>
<NUMBER_OF_NODES>2</NUMBER_OF_NODES>
</RANDOM_UE_DISTRIBUTION>
<UE_MOBILITY_TYPE>fixed</UE_MOBILITY_TYPE>
</UE_MOBILITY>
<eNB_MOBILITY>
<eNB_INITIAL_DISTRIBUTION>random</eNB_INITIAL_DISTRIBUTION>
<RANDOM_eNB_DISTRIBUTION>
<NUMBER_OF_CELLS>1</NUMBER_OF_CELLS>
</RANDOM_eNB_DISTRIBUTION>
<eNB_MOBILITY_TYPE>fixed</eNB_MOBILITY_TYPE>
</eNB_MOBILITY>
</MOBILITY>
</TOPOLOGY_CONFIG>
<EMULATION_CONFIG>
<EMULATION_TIME>40</EMULATION_TIME>
</EMULATION_CONFIG>
</OAI_EMULATION>
XML Scenario Descriptor (template_1.xml)
7-8/07/2011
Require XAMPP (http://www.apachefriends.org/)
Add OpenAirEmu web interface to htdocs
Configure OpenAirEmu.conf
<?
$OPENAIR_HOME = ""; // set the absolute Path
// DO NOT CHANGE THESE VARIABLES
$OPENAIR1_DIR = "$OPENAIR_HOME/openair1";
$OPENAIR2_DIR = "$OPENAIR_HOME/openair2";
$OPENAIR3_DIR = "$OPENAIR_HOME/openair3";
$OPENAIR_TARGETS = "$OPENAIR_HOME/targets";
$WEBXML_PATH = "$OPENAIR_TARGETS/SIMU/EXAMPLES/OSD/WEBXML";
$RESULTS_PATH = "$OPENAIR_TARGETS/SIMU/EXAMPLES/OSD/RESULTS";
?>
Currently does not support distributed emulation
Web Interface
7-8/07/2011
Basic Scenario Descriptor
7-8/07/2011
Basic Scenario Descriptor
7-8/07/2011
IP Connectivity Script
Several instance within the same physical machine
TARGETS/SIMU/EXAMPLES/VIRT_*
Compile with NAS_NETLINK=1
Insmod nasmesh.ko
route add -net 224.0.0.0 netmask 240.0.0.0 dev eth0
ifconfig oai0 10.0.1.1 netmask 255.255.255.0 broadcast
10.0.1.255
ifconfig oai1 10.0.2.2 netmask 255.255.255.0 broadcast
10.0.2.255
rb_tool -a -c0 -i0 -z0 -s 10.0.1.1 -t 10.0.1.2 -r 3
rb_tool -a -c0 -i1 -z0 -s 10.0.2.2 -t 10.0.2.1 -r 3
7-8/07/2011
IP Addressing of Virtualized Instances
When transmitting data among the
virtualized protocol instances, the
third and fourth byte of IPv4
address represents who is the
source and destination
10.0.1.2 (10.0.1.110.0.2.2)
Oai network device at the receiver
side changes the address so that
the local IP stack accepts the
packet
make the third byte of both the source
and destination equal to the fourth of
the destination
10.0.2.1 10.0.2.2
Physical Machine
Host OS

Hardware
Shared Kernel
(Host+ virtual instances)
Emulation Medium
Phy Abstraction
10.0.1.1 10.0.2.2
7-8/07/2011
OAI Network Device
7-8/07/2011
Output
Execution Log files per component
Currently only not all the components support different log
level
Packet trace for MAC
Monitor/profile the execution
gprof
7-8/07/2011
ADDITIONAL TOOLS
7-8/07/2011
OCG: Openair Config Generator
7-8/07/2011
OPT: Openair Packet Tracer
7-8/07/2011
OLG: Openair LOG Generator
7-8/07/2011
OTG: Openair Traffic Generator
7-8/07/2011
OMG: Openair Mobility Generator
7-8/07/2011
OMG: Openair Mobility Generator
7-8/07/2011
OMG Roadmap
Embedded Approach
Both worlds integrated in a single product
Advantage
Native and fast interaction, including feedback
Disadvantage
Complex extension / cannot get the best of both worlds
Isolated Approach:
One simulator providing traces for the other
Advantage:
Separate development
Disadvantage
No feedback
Access delay
Federated Approach
Both worlds interact through sockets API and are synchronized by an interface
Advantage:
Independent development/ can use different simulators
Disadvantage:
Synchronization and data management
OpenAir Emu contains basic
random models
(RWP, RWALK,GRID)
OpenAir Emu loads trace files
provided by SUMO
OpenAir Emu connects to
SUMO via sockets
7-8/07/2011
OAI WEB TOOLS &
DEVELOPMENT AREA
7-8/07/2011
Collaborative Web Tools
SVN Repositories containing
OPENAIR1 : base band processing, channel sounder,
OPENAIR2 : medium access control, L2 protocol stack
OPENAIR3 : wireless networking
TARGETS : simulation, emulation, real experiments
TWIKI
Quick access by partners to our development via a collaborative HOW-TO
phpBB Forum
external support services
Bugzilla
Internal / external bug reporting
BSCW
Internal/ external CMS for document sharing
Soon
Sourceforge distribution of stable code
7-8/07/2011
Collaborative Web Tools
Revision Control System SVN and WEBSVN
Repository: https://svn.eurecom.fr/openairsvn/openair4G/trunk/
Web interface: https://svn.eurecom.fr/openairwebsvn/
Snapshot: http://svn.eurecom.fr/openairinterface/
Documentation Doxygen, Graphviz, Readme/howto
OPENAIRX_DIR/DOCS/TEMPLATES
CMS https://bscw.eurecom.fr
Wiki https://twiki.eurecom.fr
Forum http://forums.eurecom.fr/openairinterface
Bug reporting http://bugzilla.eurecom.fr
7-8/07/2011
Development Area
OPENAIR1: Baseband/PHY
Advanced PHY (LTE/LTE-A), Propagation Measurement
and Modelling, Sensing and Localization Techniques,
PHY Modeling Tools
OPENAIR0: Wireless Embedded System Design
Agile RF design, Reconfigurable High-end Transceiver
Architectures, FPGA prototyping, Simulation Methodologies,
Software development tools, low-power chip design
Cognitive
Technologies
Wideband RF,
Agile Spectrum
Management,
Interference
Management and
Control,
Distributed/Collabo
rative techniques,
Spectrum Sensing,
Cognitive and
Flexible Radio
Architectures,
Ambient
Networking
OPENAIR2: Medium-Access Protocols
Cellular/Mesh topologies, resource allocation, cross-layer
wideband scheduling, distributed resource control,
cooperation, low latency signalling
OPENAIR3 : Wireless Networking
All-IP, Mobility Management, 802.21, Cellular/Mesh
Routing Protocols, Mesh Topology Management, Radio
Resource Management, multicasting, QoS
Targets:
Simulation &
Emulation & Real
experimentation
Field trial,
measurement
campaign, Large
scale real-time
system emulation,
protocol / algorithm
validation,
performance
evaluation, SW/HW
architecture,
software defined
radio, traffic and
mobility generators
7-8/07/2011
OAI Users and Projects
Several labs have acquired OAI equipment
Thales Communications (Paris)
Alcatel-Lucent (Paris)
Technical University of Berlin (2 labs)
Bilkent University
Aalborg University
University of Nice Sophia-Antipolis
EPFL
CNES (French Space Agency)
Several labs contribute to SW development through
collaborative projects
Related FP7 projects:
SENDORA,WHERE,NEWCOM++, LOLA, CONECT, SAMURAI, SACRA,
MEDIEVAL
7-8/07/2011
Development Methodology
Versioning and release
trunk : target new release
Require dev and bug fix
tagging : stable / specific release
no dev just bug fix
branches: new features
merging to trunk when validated
Status can be seen on
http://svn.eurecom.fr/openairwebsvn
7-8/07/2011
Important Points
Document your code using doxygen and Readme
Only .h files
Add .h files to Doxyfile in DOCS/
Check the generated html
svn update : get the latest version
make check and run examples: validate your modification
With/without abstraction flag and IP interface+traffic
svn status (-qu): to check your modifications
svn add : add new files if any
svn ci files m add your comment
commit ONLY the source files and not the generated files
7-8/07/2011
CASE STUDY
7-8/07/2011
Usage of OAI Experimental Platform
Platforms are designed to offer open access pooled
resources
Usage:
Carry out research and development projects sometimes up
to the industrialization phase
tests, and develop prototypes and/or pre-production series.
They can even serve as usage labs.
7-8/07/2011
OAI Network Topologies
Cellular Topology Mesh Topology
7-8/07/2011
Rapidly Deployable Networks
A field trial (underground and medium-range outdoor) was
carried out
near Barcelona (Spain) in February 2009
near Paris (France) in November 2010
Goals:
Validation and Integration of rapidly-deployable mesh technologies
into multi-standard systems for rapidly deployable networks
PHY/MAC (rapidly-deployable WiMAX/LTE-like radio access) 1.9 GHz, 5
MHz channelization TDD, 2x2 MIMO-OFDMA, 23dBm
L3 (routing protocols + QoS management)
Public-safety applications (video sensing, group comms)
7-8/07/2011
CHORIST Trials
(Barcelona Feb 2009)
Single Cluster Deployment
Cluster
Head
Router 1
Router 2
Cluster
Head
Router 1
Router 2
630 meters
230 meters
Cluster
Head 1
Router 2
Router 1
Cluster
Head 2
Router 3
Dual Cluster Deployment
7-8/07/2011
CHORIST Trials in Detail
7-8/07/2011
HNPS Trial
Deploy-
able
WiMAX
Wireless
Mesh
Network
UMTS
&
LTE
SatCom
(NoSaCo)
Wi-Fi
Ethernet
Gateway
Fixed
High
Speed
Network
Ethernet Internet
IAN
WAN
7-8/07/2011
The Implemented Network
Mobile Command
Centre
(Black Logan)
Mobile Unit 1
(Yellow Clio)
Mobile Unit 2
(simulated
vehicle)
Crisis Centre
(HITEC -
Luxembourg)
Crisis Centre
(Alcatel / Lucent - Paris)
WAN
Satellite Link
IAN
WiMAX/
WMN
Voice Service
TETRAPOL
TETRA Network
Crisis Centre
Redundancy
(Luxembourg)
7-8/07/2011
HNPS Scenario: Terrorist Attack in a Building
Storage area
Hostages
Headquarters
MU 1 MU 2
Video Analytics 1
Video Analytics 2
WMN
TETR
APOL
7-8/07/2011
Network Used in the HNPS Scenario
Fixed Radio Networks
TETRAPOL
National PMR for public security exterior
TETRA
Private PMR, for private security - exterior
WiFi
Exterior et interior with localisation service
WiMAX
Wide band 4G radio network private
UMTS
Wide band 3G radio network public Access granted to
public security agents
SatCom
Long distance connection with backhaul
Fast Deployable Networks
WiMAX
Wide band network limited to the
intervention site
Wireless Meshed Network (WMN)
Deployed in areas where other
networks unavailable e.g. basements
connected to the WAN via WiMAX
Wireless Sensor Network (WSN)
Deployed on demand to connect
sensors may use the WMN or
WiMAX
7-8/07/2011
REFERENCES
OTHER SLIDES
7-8/07/2011
References
freemat.sourceforge.net/
www.mathworks.fr/
www.gnu.org/software/octave/
www.scilab.org/
tetcos.com/software.html
pcl.cs.ucla.edu/projects/glomosim/
www.nsnam.org
www.opnet.com
www.omnetpp.org
http://nitlab.inf.uth.gr/NITlab/
www.openairinterface.org
7-8/07/2011
Realtime Distrubuted Emulation with RTNET
7-8/07/2011
Wide Area Network Emulator WANEM
Delay emulation tool allowing applications to
experience wide area network delays,
bandwidth and error ratios.
7-8/07/2011
Contacts Information
URL:
www.openairinterface.org
Partnership and collaboration :
openair_admin@eurecom.fr
Technical Support:
openair_tech@eurecom.fr
7-8/07/2011
Hardware / Software requirements and
installation procedures
06/07/2011 - EURECOM GENERAL - p 1
Philippe.Foubert@eurecom.fr
OAI Configuration and Requirements
OAI actual software configuration
EMULATION in USER-SPACE LINUX (Not RealTime)
EMULATION in KERNEL-SPACE (RealTime)
RADIO FREQUENCY mode (RealTime)
OAI future software configuration
OAI Hardware requirements
06/07/2011 - EURECOM GENERAL - p 2
06/07/2011 - EURECOM GENERAL - p 3
OAI actual software configuration for EMULATION
EMULATION in USER-SPACE LINUX (Not RealTime)
UBUNTU 9.04
GCC 4.3.3
GENERIC UBUNTU KERNEL (2.6.28-generic)
IPv6 features enabled (OPTIONAL. Only if IPv6 is required)
EMULATION in KERNEL-SPACE LINUX (RealTime)
UBUNTU 9.04
GCC 4.3.3
KERNEL 2.6.29.4
VANILLA KERNEL (from www.kernel.org)
Patched with OpenAirInterface Driver
Patched with RTAI 3.8
Twiki: HOW-TO create the 2.6.29.4 OpenAirInterface kernel
on a Ubuntu 9.04
06/07/2011 - EURECOM GENERAL - p 4
OAI actual software configuration for RADIO
RADIO mode (RealTime)
UBUNTU 9.04
GCC 4.3.3
KERNEL 2.6.29.4
VANILLA KERNEL (from www.kernel.org)
Patched with OpenAirInterface Driver
Patched with RTAI 3.8
Patched with BIGPHYSAREA
Twiki: HOW-TO create the 2.6.29.4 OpenAirInterface kernel on a
Ubuntu 9.04
06/07/2011 - EURECOM GENERAL - p 5
OAI future software configuration
For RADIO and EMULATION (Realtime)
UBUNTU 9.04 UBUNTU 10.04 LTS version (3 years support)
GCC 4.3.3 GCC 4.4.3
KERNEL 2.6.29.4 2.6.32.2 (ONLY for REALTIME mode)
VANILLA KERNEL (from www.kernel.org)
Patched with OpenAirInterface Driver (ONLY if using IPv6)
Patched with RTAI 3.8
Patched with BIGPHYSAREA (ONLY for RADIO)
06/07/2011 - EURECOM GENERAL - p 6
OAI Hardware requirements
Hardware requirements for OAI in RADIO mode
On a desktop machine
A powerful machine (Quad-core CPU)
E.g: MINI-PC: QuadCore 2.83Ghz, 3GB RAM, INTEL MotherBoard, PCI slot
A free PCI slot with a PCI to CARDBUS adapter
Compatible with RTAI (SMI disabled)
On a laptop machine
A powerful machine (Quad-core CPU)
E.g: DELL M4500: Intel Core i7 QuadCore 2.83Ghz, 4GB RAM, INTEL
ICH architecture, ExpressCard slot
Compatible with RTAI (SMI disabled)
EXPRESS-CARD free slot with EXPRESS-CARD to CARDBUS adapter
06/07/2011 - EURECOM GENERAL - p 7
OAI Hardware requirements
Hardware requirements for OAI in EMULATION mode
Gigabit Ethernet Switch
For a Small scale emulation = Normal laptop (Core 2 duo CPU)
E.g : DELL PRECISION M2300, Core 2 duo 2.2Ghz, 2GB of RAM
For a large scale emulation = Cluster machine (Quad-core CPU)
E.g : DELL POWEREDGE 1950, QuadCore 2.2Ghz, 8GB of RAM