OpenEPC-Whitepaper Nov2012
OpenEPC-Whitepaper Nov2012
OpenEPC-Whitepaper Nov2012
Table of content
Open Core Network Testbeds meet
the R&D demands
The R&D Community Faces Intense
Complexity in Realizing Meaningful
Testbeds
Why Open Testbeds
A Realistic Testbed answers the
Challenges
The Fraunhofer FOKUS OpenEPC
(Rel. 4)
OpenEPC highly reduces R&D
duration
p 2
p 3
p 4
p 6
p 8
p 10
WLAN
2G RAN
PDNGW
HSS
OFCS
on understanding, demonstration,
and further customization. A testbed environment, which achieves
openness and simplicity of usage,
while containing a large amount of
standard features, will enable the
easy deployment in the laboratories
all around the world. It will accelerate the understanding and the
testing of new technologies.
It will also support the evaluation of
new applications or standard core
network components on realistic
environments.
3G RAN
SGSN
LTE RAN
IMS
PCRF
ANGW
MME
SGW
ePDG
AAA
ANDSF
MSC
Three key issues that increase the costs of deploying a realistic operator network testbed:
high complexity, reduced customization and closed environments
Complexity Limits
Testbed
Deployments
Today, a realistic operator network
testbed is very complex. It should
support one of the 3GPP access technologies LTE, HSPA or EDGE along
with non 3GPP accesses, such as
WiFi, core network mobility support,
subscriber based authentication, and
authorization. Other features employed in the 3GPP EPC architecture
should be considered, such as policy
and charging control, accounting,
access network discovery and selection, and multiple APN realization,
together with off-the-shelf mobile
devices and common IP based service
platforms, such as IMS or M2M.
Developing or gathering such functionality from multiple sources and
orchestrating it in a single testbed
is highly time-consuming. A single
toolkit that manages core network
complexity in an integrated manner
will allow minimizing the time required for testbed establishment and
customization.
Proprietary Systems
make Innovation difficult
One of the main factors deterring
innovation in the area of operator
core networks is related to the prototype equipment, which is usually
delivered in closed boxes with prop-
No easy Replication
of Standard Components
Especially for equipment and application developers, a testbed should
implement the internal and external
interfaces in a standard manner. For
R&D laboratories, which already employ part of the components, a core
network testbed should be able to
provide the missing pieces and thus,
to realize fast a complete working
environment. Otherwise, the means
to evaluate equipment in early phases of prototyping are strenuous.
From this perspective, a testbed
toolkit should provide a reference
implementation of the latest version
of the standards, enabling the
inter-working with current available
and future components, as well as
flexible adaptation towards novel
features.
Easy configurable
software toolkit
implementation
Standard inspired components bring
trust in the new functionality and
Interoperability:
Providing the
Missing Pieces
A standard based, open testbed
allows the selection of specific
components to be integrated and to
interwork with vendor equipment.
An open testbed can be adapted
and employed with third party
equipment, enabling its gradual
transformation with adding real
components, while being able to run
and test at each introduction of new
equipment.
The development of a new functionality can be greatly reduced,
through prototyping against the
standard components offered by the
testbed.
OpenEPC includes all the components and a major part of the functionality of the 3GPP Evolved Packet
Core standards, along with own
Fraunhofer FOKUS features, enabling
all-IP connectivity over LTE, HSPA,
EDGE and other non-3GPP accesses,
such as WiFi.
Control
PCRF
l.
4
Re
PC
Data
ANDSF
OFCS
HSS
AAA
pe
nE
PGW
SGW
SGSN
2G BTS/BSC
SGSN
3G NodeB/RNC
ePDG
DSL,
FTTx,
WiMAX
MME
LTE eNodeB
ANGw
WiFi
Designed for
enabling complex
testbeds
The OpenEPC software is based on
its own flexible and powerful programming framework, designed for
developing software-based operator
core network functionality and components in a time efficient manner.
Featuring high modularity, OpenEPC
enables the easy deployment of
customized testbeds. Each communication protocol, interface, function and component has a separate
module, allowing the reshaping of
the core network, through multiplication, aggregation and split of the
specific functionality.
Each of the modules exports its own
API, enabling the toolkit to interact
with external components at different communication levels. These
APIs allow for cost efficient building
of non-standard interfaces.
For handling the large number of
modules, a simple set of configuration files are provided for each
component, enabling the definition
of parameters, device interfaces, and
behaviors, with no modification of
the OpenEPC modules.
Dynamic configuration during
runtime can be achieved by using a
special console, listening on each of
the components to external commands. These commands allow the
testbed operator to artificially reproduce experiments conditions, like an
extended number of subscribers.
OpenEPC components can be split
on a large number of computing
devices using Linux OS, according to
the specific scenario needs.
Additionally, OpenEPC can be completely virtualized in a single server.
Then, the testbed can be ported to
different demonstration sites and
as replicated for each interested
developer, highly reducing the cost
of equipment required for R&D.
Another option is to run all the OpenEPC components in a single machine as different parallel programs,
further optimizing the operations
for micro-operator scenarios.
Through its 3GPP inspired interfaces, OpenEPC can interwork with
standard equipment, as validated
ANDSF
S14
MSC
BTS
BSC
GPRS
Sp
Gb
NodeB
RNC
UMTS
Sp
SWx
HSS/SPR
S6d
SGSN
AF
S6a
S1-MME
eNodeB
S1-U
S4
S11 S12
Gxx
Gxx
S-GW
LTE
Charging
System
PCRF
Iu-PS
MME
Rx
Sp
Gxx
Gx
PDN GW
S5/S8
S2b
AAA
Server
STa
Trusted
Non-3GPP
Untrusted
Non-3GPP
SGi
S6b
S2a
ANGw
UE
Gy/Gz
ePDG
SWm
SWa
10
Acronyms
3GPP
PMIP
Proxy Mobile IP
AAA
PS
Packet Switched
ANDSF
QoS
Quality of Service
R&D
ANGw
RAN
API
RCS
APN
RNC
BSC
SGSN
CS
Circuit Switched
SGW
Serving Gateway
EDGE
SON
Self-Organizing Networks
EPC
VoLTE
ePDG
WLAN
GPRS
GSM
GTP
GUI
HSPA
HSS
IMS
IP Multimedia Subsystem
IP
Internet Protocol
LTE
M2M
Machine-to-Machine
MME
MSC
MTC
OFCS
OS
Operating System
OTT
PCC
PCRF
PGW
Diameter
RANAP
RADIUS
SCCP
GTP
M3UA
Mobile IP
SNDCP
Proxy Mobile IP
LLC
IPv4-in-IPv4
BSSGP
IPv4-in-IPv6
NS
IPv6-in-IPv4
SyncML
IPv6-in-IPv6
SNMP
GRE
OMA NGSI
GTPv2-C
GTP-U
NAS
GSM Layer 3 / DTAP
S1AP
X2AP
11