Competence Center NGNI

Fraunhofer FOKUS

Open EPC – A Short Overview
Prof. Dr. Thomas Magedanz, TU Berlin/Fraunhofer FOKUS Marius Corici, Fraunhofer FOKUS Dragos Vingarzan, Fraunhofer FOKUS

Email: info@openepc.net Web: www.openepc.net

Competence Center NGNI

Fraunhofer FOKUS

„ Full version of this tutorial is for IMS Workshop Track 4 Tutorial attendees only! „ We are happy to provide customized onsite tutorials „ Please contact: Prof. Dr. Thomas Magedanz thomas.magedanz@fokus.fraunhofer.de

Competence Center NGNI

Fraunhofer FOKUS

Tutorial Abstract
Originally invented in the mobile world, the 3GPP IP Multimedia Subsystem (IMS) has become over the last years the globally accepted common control platform for multimedia communication service provision in Next Generation Networks (NGNs). In parallel the internet has matured towards an innovative seamless multimedia communication, information and entertainment services environment, also referred to as Web 2.0. Driven by the hype around the planed rollout of the Long term Evolution (LTE) wireless access networks providing only packet transport capabilities, the notion of the next generation of fixed and mobile networks is emerging, which will be technically realized by the 3GPP Evolved Packet System (EPS). While LTE is forming as Evolved-UTRAN (E-UTRAN) the lower part of the EPS, a new IP connectivity control platform has been defined for the upper part of the EPS to enable wireless access networks diversity (including LTE, UMTS, WiMax, WLAN, etc) below different service platforms, comprising both IMS-based and internet service architectures. This IP connectivity control platform is called Evolved Packet Core (EPC), previously known as Service Architecture Evolution (SAE), which has a lot of common principles with IMS, such as policy based QoS and Charging, user authentication, handover support, etc. however limited to provide a seamless IP pipe to a service platform. There is little doubt, that LTE, which will be initially provided in limited locations only and thus requires handover support with other existing wireless access network technologies, will depend on the proper operation of the EPC. In addition, the provisioning of seamless voice services represents a huge challenge within this environment. Moreover, a key question will be, what future wireless broadband multimedia applications will drive the future mobile environment adoption.

opportunities as well as technical and business challenges. they will learn how IMS evolution relates to the EPC and how IMS can be utilized above the EPC for voice and other multimedia services. namely the OpenEPC and show practical demonstrations in our Future Seamless Communication (FUSECO) Playground. Here we explain the key components. More information can be found at: www.openepc. their capabilities and their main interactions.Competence Center NGNI Fraunhofer FOKUS Tutorial Abstract (cont. we will look at EPC application domains and in this context illustrate also to role of IMS.) This half day tutorial will introduce to the main concepts. architectures.net . We will also briefly illustrate LTE capabilities. Furthermore. In addition. fora and related terminology in the field of Next Generation of Fixed and Mobile Networks. Finally we will introduce the brand new TU Berlin / FOKUS next generation of fixed and mobile networks toolkit enabling EPS testbed establishment. namely the Evolved Packet Core. standards. however the main focus will be in the introduction of the all-IP control platform. Attendees will gain a basic understanding of the future mobile networks capabilities.

QoS. etc. HSS.Competence Center NGNI Fraunhofer FOKUS Detailed Agenda Part 0: Motivation from NGN/IMS to Converged NGN/EPC Part 1: Converged NGN Overview „ Motivation for converged NGN: Mobile data increase vs.) „ Simplified EPC architecture over E-UTRAN (MME. . mobility management.EPC Motivation and Functional Overview (Security. PDNGW. mobility management. SGW. and 3GPP „ 3GPP Evolved Packet System (EPS) Architecture Overview (LTE/E-UTRAN and EPC/SAE) Part 2: Evolved Packet Core (EPC) „ Long term Evolution (LTE) / Evolved UMTS Radio Access Network (E-UTRAN) Capabilities „ Beyond LTE . PCRF) „ Full EPC architecture above multiple access networks (3GPP and trusted/untrusted non3GPP access networks) „ Component interactions for registration. roaming. etc. service access. LTSI. Charging. revenue decrease „ Mobile Network Evolution „ Key players in converged NGNs: NGMN Alliance.

CS over PS. capabilities. uses cases) „ Practical demonstrations will show the possible usage of the EPC based on the FOKUS OpenEPC platform Part 5: Summary and Q&A . and more) „ The LTE challenge: Voice over LTE Options (comparison of SRVCC. VoLGA) „ Potential LTE/EPC rollout strategies Part 4: Getting started with EPS: Introducing the new FOKUS OpenEPC testbed toolkit „ Overview of the OpenEPC toolkit (components. CS Fallback. IMS.) Part 3: Mobile Services beyond the EPC: Voice.Competence Center NGNI Fraunhofer FOKUS Detailed Agenda (cont. IMS and others „ EPS application domains (Internet.

V. editorial board member of several journals. He acts often as invited tutorial speaker at major telecom conferences and workshops around the world. Magedanz is one of the founding members of FOKUS (1988) and member of the management team. telecoms. He is the author of two books on IN standards and IN evolution. Germany. which provides toolkits for NGN/IMS as well as Next Generation of Fixed and Mobile Networks /EPC test and development tools for global operators and vendors. Magedanz is a globally recognised technology expert. a FOKUS Consulting spin off focussing on professional services. leading the chair for next generation networks (Architektur der Vermittlungsknoten – AV) supervising Master and PhD Students In addition. Magedanz is senior member of the IEEE. habil Thomas Magedanz Thomas Magedanz (PhD) is professor in the electrical engineering and computer sciences faculty at the Technical University of Berlin. strategic studies and technology coaching. Dr. Prof. and the author of more than 200 technical papers/articles. internet and entertainment). . Ing. Prof.Competence Center NGNI Fraunhofer FOKUS About the Speakers Prof.. he is director of the “NGNI” division at the Fraunhofer Institute FOKUS. based on his 18 years of practical experiences gained by managing various research and development projects in the various fields of today's convergence landscape (namely IT. Prof. Furthermore he is principal consulant of Direct Link Consult e.

-Ing.Competence Center NGNI Fraunhofer FOKUS About the Speakers (cont.) Dipl. . Romania in 2005. His research work includes multiple patent applications submitted in the area of IP network architectures and multiple publications in the area of Next Generation Networks (NGN) in collaboration with various industry partners. Marius-Iulian Corici Marius Corici received his Diploma in the Science of Systems and Computers – Computers Engineering from University “Politehnica” of Bucharest. He joined the Next Generation Network Infrastructures (NGNI) competence center of Fraunhofer FOKUS Institute in 2005.

performance benchmarking and interoperability.-Ing. with special interests in prototyping. Currently he is working on his PhD in the area of IMS core and Evolved Packet Core (EPC) networks. . Ing. open source in telecommunications.Competence Center NGNI Fraunhofer FOKUS About the Speakers (cont.) Dipl. at the “Politehnica” University of Bucharest. he continued his reseach activity at the same institute in the area of feasibility and performance studies on NGN/converged NGN architectures. Romania in February 2005. Since 2005. compilers and computer networks with a Diploma Thesis at Fraunhofer FOKUS which represented the first milestone of the Open IMS Playground. Dragos Vingarzan Dragos Vingarzan graduated as Dipl. the Computer Engineering program on base software. He is an active member of various IMS working groups.

IMS and others Part 4: Getting started with EPS: Introducing the new FOKUS OpenEPC testbed toolkit Part 5: Summary and Q&A . LTSI.Competence Center NGNI Fraunhofer FOKUS Detailed Agenda Part 0: Motivation from NGN/IMS to Converged NGN/EPC Part 1: Converged NGN Overview „ Motivation for Converged NGN: Mobile data increase vs. and 3GPP „ 3GPP Evolved Packet System (EPS) Architecture Overview (LTE/E-UTRAN and EPC/SAE) Part 2: Evolved Packet Core (EPC) Part 3: Mobile Services beyond the EPC: Voice. revenue decrease „ Mobile Network Evolution „ Key players in Converged NGN: NGMN Alliance.

e. are currently a potential show stopper „ IMS provides a lot of needed capabilities in the voice domain and value added multimedia services domain (e. 3GPP and non-3GPP access „ EPC shares a lot of concepts with IMS. incl.g. „ EPC maintains seamless IP connectivity and thus supports multiple application domains. HSS. etc) „ Early prototyping of next generation converged environments will be crucial to gain practical experiences „ Similar to Open IMS Core for NGN.Competence Center NGNI Fraunhofer FOKUS Introduction „ There is a lot of hype around Long-Term Evolution (LTE) and its commercial deployment „ LTE roll out will require interworking with other existing and emerging wireless access network technologies „ The 3GPP EPC is the new mobile core network suporting seamless mobility.g. IPTV. RCS. including IMS and internet platforms „ LTE provides IP services only. PCC. thus voice services. overlay architecture concept. representing still the operator cash cow. QoS and charging across multiple IP access networks. etc. the OpenEPC toolkit is designed for converged NGN prototyping .

PSA.0 Evolved Packet Core (EPC) Mobile IP Networks Converged NGNs Cable LTE WLAN WIMAX . Telecom Web Service APIs GSMA ONE API Open APIs Parlay X OSA/Parlay/JAIN Intelligent Network (IN) IN Services based on SIBs IN Overlay Architecture Bearer Networks PSTN GSM IP Open Service APIs Service Delivery Platform (SOA based) Network Abstraction IP Multimedia System (IMS) IP Networks NGN DSL UMTS WLAN Web 2.Competence Center NGNI Fraunhofer FOKUS From IN to IMS to EPC: Pull intelligence out of the access nets IT Impact on Telecoms OMA PIOSE.

UMTS. IM. LTE. VoIP. but enablers • IMS Core provides session control signaling based on SIP and AAA capabilities over Diameter • supports inherently multimedia over IP. presence (SIP) • IMS enables the flexibility in providing IP-based applications Group Server Content Presence Server Call Control Messaging Server SIP Server Packet Core Network Access Networks (WLAN. DSL) Transport (RTP) Access Networks (WLAN. UMTS.Competence Center NGNI Fraunhofer FOKUS IMS – Flexible & Controlled Service Provision on IP Networks • IMS does NOT standardize specific services. DSL) IMS Applications IMS Core . LTE.

. IM.0 What about other IP Applications Converged NGN (all-IP) P/ISDN Emulation Subsystem supports all IP Multimedia Subsystem IMS Streaming/IPTV Subystem VoIP/Skype Reusable Transport Support Systems Best effort Internet PSTN . Presence IPTV Web 2. FMC.Competence Center NGNI Fraunhofer FOKUS IMS is the common control platform within the NGN for many Application Domains P/ISDN Emulation VOIP. Videoconf.

Competence Center NGNI Fraunhofer FOKUS Evolution Path of 2G and 3G Technologies .

graphically intensive ones „ High quality/definition audio/video services „ Superior encoding options „ Cloud computing functions and features (all user data is in the cloud) .g. multi‐media. avoiding international roaming charges „ Video/Music on demand while mobile „ Multicast and broadcast service offerings „ Interactive gaming (graphics. twitch games) „ Downloaded applications „ Larger.Competence Center NGNI Fraunhofer FOKUS Expected mobile Broadband Services „ VoIP alternatives to expensive tariffs ƒ e..

Competence Center NGNI Fraunhofer FOKUS From NGN to Converged NGN: an important step towards the Future Internet Internet Telecommunications IPTV PES Mobile Telecommunications FMC RCS Rich Communications & Media IMS PCC Evolved Packet System P2P Internet Fixed Telecommunications Next Generation Network Next Generation Mobile Network Future Internet Evolution .

P2P. SIP. plus Mobility Management for any IP based protocol (HTTP. Security Optional IMS Fixed Mobile Cable PCC Evolved Packet Core 4G 2G GPRS 3G UMTS LTE/WiMAX Any IP Network 3GPP Release 6 WLAN 2G GPRS EPC can be seen as a more generalized „lightweight IMS“. Charging. …) 3GPP Release 8 . QoS. Providng security.Competence Center NGNI Fraunhofer FOKUS Concept Reuse: From IMS for NGN to EPC for all-IP TISPAN VCC PoC RCS IMS PES IPTV Next Generation of NGNs ICS MMtel VCC RCS Any Application Platform NGN IPTV PES Internet Other Application Platforms IMS QoS. Charging.

Competence Center NGNI Fraunhofer FOKUS Evolved Packet Core (EPC) „ is an evolution of the legacy GPRS architecture to improve performance and reducing costs „ is the new. formerly known as System Architecture Evolution (SAE) „ EPC is based on end-to-end IP only connectivity (no circuit switched connections!) ƒ ƒ ƒ Clear delineation of control plane and data plane Simplified architecture: flat IP architecture with a single core network EPC is based entirely on IETF protocols „ EPC allows the operator to realize a truly converged packet core supporting different wireless access technologies (3GPP and non-3GPP) „ EPC maintains seamless mobility . mobile core network introduced with LTE in 3GPP release 8 „ EPC is motivated by the fact that LTE is just one access network technology. QoS and unified charging and thus provides the foundation for seamless. and mobile applications have to interoperate with various access network technologies „ LTE access and EPC overlay form together the Evolved Packet System (EPS). all-IP only. consistent and optimized services provision independent of the access network type .

P2P etc.) Evolved Packet Core 3GPP Access trusted „ Important EPC functions include: ƒ ƒ ƒ NAS and security (AAA) mobility and connectivity management policy QoS control and charging (PCC) Non 3GPP Access trusted / untrusted .g. e. CDMA2000/HRPD) and untrusted networks including IMS ƒ Non-3GPP Access (WLAN) ƒ Internet „ EPC provides connection to IP service domains ƒ ƒ IMS Internet (or others. GPRS-GERAN) ƒ Non 3GPP Access (WIMAX. UMTS-UTRAN.Competence Center NGNI Fraunhofer FOKUS Evolved Packet Core (EPC) „ The EPC is a multi-access core network based on the Internet Protocol (IP) one common packet core network for both ƒ trusted networks including ƒ 3GPP Access (LTE-E-UTRAN.

Competence Center NGNI Fraunhofer FOKUS Detailed Agenda Part 1: Converged NGN Overview „ Motivation for Converged NGN: Mobile data increase vs. LTSI. IMS and others Part 4: Getting started with EPS: Introducing the new FOKUS OpenEPC testbed toolkit Part 5: Summary and Q&A . revenue decrease „ Mobile Network Evolution „ Key players in Converged NGN: NGMN Alliance. and 3GPP „ 3GPP Evolved Packet System (EPS) Architecture Overview (LTE/E-UTRAN and EPC/SAE) Part 2: Evolved Packet Core (EPC) Part 3: Mobile Services beyond the EPC: Voice.

Competence Center NGNI Fraunhofer FOKUS Content and Apps over Bitpipes – Where is the Money?? • • Network convergence based on IP has led to high competition Connectivity Services (QoS) versus Multimedia Services (Content) UMTS CDMA WLAN WiMax GSM EDGE Common Applications and Services LTE IP – based Core Network(EPC) POTS/ ISDN Wireline xDSL .

Competence Center NGNI Fraunhofer FOKUS Mobile Network Architecture Evolution 1991 2000 2004 IP PSTN 2008 IP PSTN PSTN IP PSTN IMS IMS Circuit Switched Circuit Switched Packet Switched Circuit Switched Packet Switched Packet Core Access Access Access Access 2G GSM 2G / GPRS / EDGE Evolution 3G / IMS Evolution EPS (LTE/EPC) .

but also non-3GPP systems (e. but also non-3GPP systems (e. WiMAX) ƒ ƒ . with some differences: ƒ ƒ ƒ simplified architecture all IP Network only support for higher throughput and lower latency radio access networks (RANs) support for multiple. heterogeneous RANs. „ SAE / EPC is the evolution of the GPRS Core Network.Competence Center NGNI Fraunhofer FOKUS LTE/SAE/EPC – Towards a flat architecture „ System Architecture Evolution (SAE) is the core network architecture of 3GPP's future LTE wireless communication standard. including legacy systems as GPRS. WiMAX) mobility between heterogeneous RANs. including legacy systems as GPRS.g.g.

org/SpecificationNumbering „ LTSI performs Proof of Concept / Interoperability Tests ƒ http://www.3gpp.Competence Center NGNI Fraunhofer FOKUS Who is Who in Next Generation Mobile Network context? „ NGMN Alliance defines LTE/EPC Requirements ƒ http://www.pdf .lstiforum.3gpp.org/file/news/Latest_L STI_Results_Feb09_v1.org/Highlights/LTE/LTE.org „ 3GPP developes LTE/EPC Specifications ƒ http:// www.htm ƒ http://www.ngmn.

Competence Center NGNI Fraunhofer FOKUS 3GPP Evolved Packet System = E-UTRAN + EPC Evolved Packet Core (EPC) .

The focus of this work is on the PS domain with the assumption that voice services are supported in this domain” „ The result of that study is a new simplified All-IP architecture which fulfills the requirements of NMGN: the “Evolved Packet Core” (EPC) „ The Evolved Packet System (EPS) is the term used to refer to the combination of EPC + E-UTRAN „ The EPS is an IP network and uses the standard routing and transport mechanisms of the underlying IP network.Competence Center NGNI Fraunhofer FOKUS Evolved Packet System (EPS) „ 3GPP required a network architecture able to support the characteristics of E-UTRAN „ The study point to generate such network architecture was called the “System Architecture Evolution” (SAE) „ SAE objective was: “to develop a framework for an evolution or migration of the 3GPP system to a higher-data-rate. lower-latency. . multiple RATs. packet-optimized system that supports.

user preference and access network conditions „ Realize improvements in basic system performance whilst maintaining the negotiated QoS across the whole system „ Provide capabilities for co-existence with legacy systems and migration to the Evolved Packet System „ See also 3GPP TS 22.278: Service requirements for the Evolved Packet System (EPS) .Competence Center NGNI Fraunhofer FOKUS EPS Objectives „ Provide higher data rates. lower latency. high level of security and enhanced QoS „ Support a variety of different access systems (existing and future). ensuring mobility and service continuity between these access systems „ Support access system selection based on a combination of operator policies.

session adaption to terminal capabilities. user preferences. subscriber priorities. network conditions etc.Competence Center NGNI Fraunhofer FOKUS EPS Features „ Support for IP traffic with QoS „ Support for IP multicast „ IP session control including mobility. „ Support for scalable multi-party sessions „ Support simultaneous active Packet Data Network connections for the same User Equipment „ Support for emergency calls „ Support for multi-access and seamless mobility .

401 and 3GPP TS 23.Competence Center NGNI Fraunhofer FOKUS EPS architecture (3GPP TS 23.402) „ Interconnection with UTRAN and GERAN through SGSN. MME and Serving Gw „ In roaming scenarios PDN-Gw can be in the visited (local breakout) or in the home network (home routed) „ Serving-Gw and PDN-Gw could be deployed together .

Competence Center NGNI Fraunhofer FOKUS LTE and the EPC in the near future „ The deployment of E-UTRAN requires beside the eNodeBs the MME entity that handles mobility and NAS functions (authorization. security etc) and the IP Gateways ƒ S-GW and P-GW may be combined in one box in the beginning „ The full deployment of the EPC is not needed but it provides additional advantages to the operator „ Non-3GPP networks may not be supported in the beginning ƒ Non-3GPP networks may not be supported in the beginning „ The main disadvantage is that the EPC is a complex architecture with many interfaces and options which are not needed in all scenarios .

roaming. PDNGW. mobility management.Competence Center NGNI Fraunhofer FOKUS Detailed Agenda Part 1: Converged NGN Overview Part 2: Evolved Packet Core (EPC) „ Long term Evolution (LTE) / Evolved UMTS Radio Access Network (E-UTRAN) Capabilities „ Beyond LTE .EPC Motivation and Functional Overview (Security. HSS. QoS. etc. Part 3: Mobile Services beyond the EPC: Voice. Charging. SGW. PCRF) „ Full EPC architecture above multiple access networks (3GPP and trusted/untrusted non3GPP access networks) „ Component interactions for registration. service access. mobility management. etc. IMS and others Part 4: Getting started with EPS: Introducing the new FOKUS OpenEPC testbed toolkit .) „ Simplified EPC architecture over E-UTRAN (MME.

Competence Center NGNI Fraunhofer FOKUS Evolved-UTRAN (eUTRAN) „ Simplified Radio Access Network (RAN) architecture with less nodes „ Evolved Node B (eNB) includes the functions ƒ Radio Resource Management ƒ Selection of MME ƒ Routing user plane data to S-Gw ƒ Scheduling ƒ Measurement & Reporting Source : 3GPP TS 36.8.0 (2009) .300 Stage 2 Release 8 V8.

limited and expensive Limited No true e2e guarantees LTE All VoIP Real-time. low latency.Competence Center NGNI Fraunhofer FOKUS 3G vs. LTE Existing Paradigm (3G) Voice Broadband Services Circuit Switched Best effort. classification True network wide policy control and management Visible and moved to the core Multisession Data QoS Policy Management Mobility Management Not widely adopted Hidden in the RAN . true broadband QoS All about bearers. strictly defined parameters. interactive. sessions. data flows E2e guaranteed.

service access. Charging.Competence Center NGNI Fraunhofer FOKUS Detailed Agenda Part 1: Converged NGN Overview Part 2: Evolved Packet Core (EPC) „ Long term Evolution (LTE) / Evolved UMTS Radio Access Network (E-UTRAN) Capabilities „ Beyond LTE . HSS. mobility management. Part 3: Mobile Services beyond the EPC: Voice. etc. etc. IMS and others Part 4: Getting started with EPS: Introducing the new FOKUS OpenEPC testbed toolkit . QoS.) „ Simplified EPC architecture over E-UTRAN (MME.EPC Motivation and Functional Overview (Security. SGW. roaming. PCRF) „ Full EPC architecture above multiple access networks (3GPP and trusted/untrusted non3GPP access networks) „ Component interactions for registration. mobility management. PDNGW.

EPS Bearer Control PDN-Gw IP address allocation.Competence Center NGNI Fraunhofer FOKUS EPS Functional Split between E-UTRAN and EPC „ Target was the enhancement of Packet Switched technology to cope with higher data rates. Connection Mobility Continuity. Packet Filtering. Security. Radio Admission Control. Idle State control. Radio Bearer Control. Dynamic Resource Allocation S-Gw Mobility Anchoring for intra-3GPP . lower latency. packet optimized system with support for multiple Radio Access Technologies „ This lead to a simplified IP-based overlay architecture with distributed control „ Functionality is divided between E-UTRAN (LTE radio access) and EPC (NAS and IP functionality) Evolved Packet System Evolved UTRAN (E-UTRAN) Evolved Packet Core (EPC) Mobility Management Entity (MME) NAS. inter 3GPP mobility anchoring eNodeB (eNB) Inter Cell Radio Resource Management.

. the ECM and EMM states are independent of each other. e. e.g. „ The EPS Connection Management (ECM) states describe the signalling connectivity between the UE and the EPC. to transition from EMMDEREGISTERED to EMM-REGISTERED the UE has to be in the ECMCONNECTED state. „ In general. Attach and Tracking Area Update procedures.Competence Center NGNI Fraunhofer FOKUS EPS Mobility and Connectivity Concepts „ The EPS Mobility Management (EMM) states describe the Mobility Management states that result from the mobility management procedures e. ƒ However there are some relations. „ Transition from EMM-REGISTERED to EMM-DEREGISTERED can occur regardless of the ECM state.g.g. by explicit detach signalling in ECMCONNECTED or by implicit detach locally in the MME during ECM-IDLE.

Competence Center NGNI Fraunhofer FOKUS Evolved Packet Core Logical Functions „ As defined in 3GPP TS 23. and are performed by the radio access network. authorization. Mobility Management Functions are used to keep track of the current location of a UE Security Functions comprise authentication of the UE by the network and service request validation.2. Radio Resource Management Functions are concerned with the allocation and maintenance of radio communication paths. Network Management Functions provide mechanisms to support O&M functions related to the Evolved Packet System. where the EPC is using the standard routeing and transport mechanisms of the underlying IP network. admission control. authentication. encryption. ƒ ƒ ƒ ƒ ƒ . and optionally policy control and charging (PCC) Packet Routeing and Transfer Functions.401 V9.0 the EPC supports the following logical functions: ƒ Network Access Control Functions are covering network selection. etc. lawful interception.

Home Subscriber Server MME .Policy and Charging Rules Function eNB – Evolved NodeB IP Services Application Functions PCRF PDN GW MME Serving GW QoS based Policy & Charging User Plane Mobility Management eNB E-UTRAN Authoriz & Authen Policy & Charging Mobility Mgt User Equipment .g.Mobility Management Entity SGW . IMS) Internet HSS User Authentication HSS .Competence Center NGNI Fraunhofer FOKUS Simplified EPC Architecture GSM/PSTN/ UMTS Application Function Voice Interworking Operator IP Services (e.Packet Data Network Gateway PCRF .Serving Gateway PDN GW .

etc. .Competence Center NGNI Fraunhofer FOKUS EPC Key Elements „ Home Subscriber Server (HSS) „ Mobility Management Entity (MME) „ Serving Gateway (Serving GW) „ Packet Data Network Gateway (PDN GW) „ Policy and Charging Rules Function (PCRF) „ Application Function (AF) „ User Equipment (UE) „ Additional EPC Components (see later slides): ƒ ƒ ƒ 3GPP AAA Server (for non-3GPP access networks) evolved Packet Data Gateway (ePGW) for untrusted access networks (WLAN) Trusted non-3GPP accesses (Access GW) for WiMax.

ƒ This information includes static profiles.Competence Center NGNI Fraunhofer FOKUS Home Subscriber Server (HSS) „ The Home Subscriber Server (HSS) is the main database of the EPC storing subscriber information. including identification information and dynamic information related to each Packet Data Network (PDN) context that the subscriber has established S6a MME HSS „ The HSS has interfaces towards: ƒ ƒ MME 3GPP AAA Server Wx AAA .

S-Gw and PDN-Gw selection „ MME does the mobility management and user plan bearer functions „ It also performs mobility functions between E-UTRAN and GERAN/UTRAN „ It has interfaces to ƒ ƒ ƒ ƒ S-Gw E-UTRAN (eNodeB) HSS SGSN (for GERAN Interworking) S6a S3 MME HSS S11 SGSN Serving S1c S1u eNB GW . user authentication. Terminal Attachment and ECM modes.Competence Center NGNI Fraunhofer FOKUS Mobility Management Entity (MME) „ The Mobility Management Entity (MME) is a component of the EPC which is only relevant for 3GPP accesses and key to E-UTRAN „ MME is in charge of NAS (Non-Access-Stratum).

„ PDN GW and Serving GW selection. „ Inter CN node signalling for mobility between 3GPP access networks (terminating S3). „ UE Reachability procedures. „ Lawful Interception of signalling traffic. . „ UE Reachability in ECM-IDLE state (including control and execution of paging retransmission). „ Roaming (S6a towards home HSS). „ NAS signalling security. „ Bearer management functions including dedicated bearer establishment. „ Authentication & Authorization.Competence Center NGNI Fraunhofer FOKUS MME Functions „ NAS signalling. „ Tracking Area list management. „ MME selection for handovers with MME change. „ SGSN selection for handovers to 2G or 3G 3GPP access networks.

Competence Center NGNI Fraunhofer FOKUS EPC Gateways Two logical Gateways exist: „ Serving GW (S-GW) The Serving GW is the gateway which terminates the interface towards EUTRAN. „ PDN GW (P-GW) ƒ ƒ ƒ ƒ The PDN GW is the gateway which terminates the SGi interface towards the PDN. there may be more than one PDN GW for that UE (however a mix of S5/S8 connectivity and Gn/Gp connectivity is not supported for that UE simultaneously) „ NOTE: The PDN GW and the Serving GW may be implemented in one physical node or in separated physical nodes. at a given point of time. ƒ For each UE associated with the EPS. If a UE is accessing multiple PDNs. there is a single Serving GW. .

it includes a PCEF (Policy and Charging Enforcement Function) „ performs UE IP allocation. packet filtering for each user.Competence Center NGNI Fraunhofer FOKUS Packet Data Network Gateway (PDN-Gw) „ The Packet Data Network Gateway (PDN-Gw) terminates the connection towards the IP service domains (IMS. charging support. or other) „ The PDN-Gw is the mobility anchor between 3GPP and non-3GPP accesses „ If PCC is deployed. policy enforcement. Internet. lawful interception and packet screening „ There may be several PDN-Gw per user (for different IP services) „ The PDN-Gw has interfaces to: ƒ ƒ ƒ ƒ ƒ ƒ Serving-Gw S5 Serving ePDG GW 3GPP AAA Server S2a Trusted non-3GPP access gateway PCRF (if PCC is supported) Access Services (Application Functions) GW PCRF Rx IMS / Internet Gx SGi PDN GW S6b S2b ePDG AAA WiMax WLAN .

„ Only one PCRF is assigned to all the connections of one subscriber S-Gw (BBERF) „ The PCRF has access to subscriber profiles stored in a database referred to the Subscriber Profile Repository (SPR) which is not currently standardized „ The PCRF has interfaces to: ƒ ƒ ƒ PCEF within the PDN-Gw.Competence Center NGNI Fraunhofer FOKUS Policy and Charging Rules Function (PCRF) „ The Policy and Charging Rules Function (PCRF) performs QoS control. and Bearer Binding and Event Reporting Function (BBERFs) in Gateways Subscriber Profile Repository Application Function in the service layer HSS (SPR) Sp PCRF Rx IMS / Internet SGi Gxx Gx Gxx S2b Access GW (BBERF) S5 PDN-Gw (PCEF) S2a ePDG (BBERF) . access control and charging related control in the EPC. „ The PCRF is policy based and authorizes bearer and session establishment and modification.

Competence Center NGNI Fraunhofer FOKUS Roaming Architectures in the EPC „ Two basic configurations are considered by 3GPP for roaming. the services accessed by the user are also located in the home network (PCSCF in home network in case of IMS) ƒ Local breakout: in this configuration the PDN-Gw is located in the visited network (no data packets of the user go through the home network) and the H-PCRF is connected to the V-PCRF to exchange the Policy and Charging Rules to be applied for the user „ For non-3GPP accesses the 3GPP AAA Server included in the visited network is referred as 3GPP AAA Proxy as it retrieves data from the 3GPP AAA Server in the home network ƒ . „ In both the HSS and the PCRF with access to subscriber profiles are located in the home network Home routed: in this configuration the PDN-Gw is located in the home network (all data of the user is routed towards the home network).

PCRF) „ Full EPC architecture above multiple access networks (3GPP and trusted/untrusted non3GPP access networks) „ Component interactions for registration. service access.Competence Center NGNI Fraunhofer FOKUS Detailed Agenda Part 1: Converged NGN Overview Part 2: Evolved Packet Core (EPC) „ Long term Evolution (LTE) / Evolved UMTS Radio Access Network (E-UTRAN) Capabilities „ Beyond LTE . SGW. Part 3: Mobile Services beyond the EPC: Voice. Charging. etc. mobility management. QoS. etc. HSS. PDNGW. mobility management. roaming.EPC Motivation and Functional Overview (Security.) „ Simplified EPC architecture over E-UTRAN (MME. IMS and others Part 4: Getting started with EPS: Introducing the new FOKUS OpenEPC testbed toolkit .

UMTS-UTRAN. WIMAX) „ Untrusted networks include ƒ Non-3GPP Access (WLAN) .Competence Center NGNI Fraunhofer FOKUS EPC Access Network Types „ Note that the EPC provides controlled IP connectivity. GPRS-GERAN) ƒ Non 3GPP Access (WLAN.g. IMS or any intranet) „ Trusted networks include ƒ 3GPP Access (LTE-E-UTRAN. in regard to ƒ User authentication and authorization ƒ Quality of Service and related Charging ƒ Mobility Management „ The EPC allows multiple access networks to be connected in a controlled way to the either ƒ the internet or ƒ the operator IP cloud (e.

Competence Center NGNI Fraunhofer FOKUS 3GPP AAA Server „ The 3GPP Authentication. Authorization and Accounting (AAA) Server is a database function used for non-3GPP access networks „ The 3GPP AAA Server stores information necessary to be used in the non-3GPP trusted network or in the ePDG for user authentication and authorization „ The 3GPP AAA Server communicates with the HSS to retrieve user profiles and update their content „ The 3GPP AAA Server has interfaces to: ƒ ƒ ƒ ƒ ƒ The trusted non-3GPP access network The ePDG The HSS The PDN-Gw Another AAA Server (roaming) Access GW ePDG HSS Wx PDN GW S6b STa AAA SWa WiMAX WLAN .

Competence Center NGNI Fraunhofer FOKUS Trusted non-3GPP Gateways „ Trusted non-3GPP accesses include: ƒ HRPD (High Rate Packet Data from 3GPP2) ƒ WiMAX (from WiMAX Forum) „ The HRPD Gw or the ASN-Gw perform mobility functions (if PMIP they include a PMIP MAG) and policy (QoS and charging) control (if PCC is deployed they include a BBERF) „ They are the non-3GPP equivalent from the Serving-Gw „ They have interfaces to the following ƒ ƒ ƒ ƒ PDN-Gw AAA Server PCRF (if PCC is supported) HRPD (GW) to MME for HO with optimizations Serving GW PDN GW PCRF Gxx S2a Access GW ePDG AAA WiMax WLAN .

if PCC is supported Serving GW PDN GW PCRF Gxx S2b AAA Access GW ePDG WiMax WLAN .Competence Center NGNI Fraunhofer FOKUS evolved Packet Data Gateway (ePDG) „ The evolved Packet Data Gateway (ePDG) is the gateway towards the non3GPP untrusted access networks „ The ePDG performs important security functionality tunnel authentication and authorization. IPSec encapsulation/de-capsulation of packets „ If PMIP is used the ePDG includes the functionality of the MAG „ If PCC is deployed the ePDG may include the BBERF „ The ePDG has interfaces to: ƒ ƒ ƒ PDN-Gw 3GPP AAA Server PCRF.

Competence Center NGNI Fraunhofer FOKUS Access Network Discovery and Selection Function „ The Access Network Discovery and Selection Function (ANDSF) is a new EPC element in Release 8. which performs data management and control functionality to assist the UE on the selection of the optimal access network in an heterogeneous scenario „ The ANDSF exchanges discovery information and Inter-System mobility policies with the UE „ The specific functionality of this component and its interfaces is being standardized currently in Release 9 „ The ANDSF has (for now) interfaces to: ƒ S14 to UE (OMA Device Management over HTTP over TLS over TCP) S14 ANDSF .

Competence Center NGNI Fraunhofer FOKUS Protocols used in EPC „ Network Layer Protocols ƒ IP ƒ Mobile IP (MIP) and variations ƒ Proxy Mobile IP over IPv6 (PMIPv6) ƒ GTP „ Transport Layer Protocols ƒ Strem Control Transport Protocol (SCTP) ƒ TCP/UDP „ Application Level Protocols ƒ OMA Device Management (DM) over HTTP or UDP or other ƒ Diameter ƒ S1-AP .

Policy & Charging MIP SWa DIAM S2b ePDG E-UTRAN WLAN Trusted Non-3GPP Access Trusted 3GPP Access Mobility Mgt WLAN Untusted non-3GPP Access .Competence Center NGNI Fraunhofer FOKUS Full EPC Architecture Reference Points & Protocols S10 GTP C S6a MME HSS PCRF DIAM Wx DIAM DIAM Trusted 3GPP Access Rx+ S3 GTP C S11 S1AP GTP C Gxx Gx PDN GW PMIP GTP Gxx Gxx DIAM SGi DIAM DIAM Operator IP Services (e.g. IMS) Internet GERAN SGSN S4 GTP Serving S5/S8 GW GTP U UTRAN S1MME eNB S1u X2 PMIP S6b PMIP AAA S2a MIP Access GW STa User Plane Authoriz & Authent.

etc. etc. PDNGW.EPC Motivation and Functional Overview (Security. mobility management. roaming. SGW. PCRF) „ Full EPC architecture above multiple access networks (3GPP and trusted/untrusted non3GPP access networks) „ Component interactions for registration.Competence Center NGNI Fraunhofer FOKUS Detailed Agenda Part 1: Converged NGN Overview Part 2: Evolved Packet Core (EPC) „ Long term Evolution (LTE) / Evolved UMTS Radio Access Network (E-UTRAN) Capabilities „ Beyond LTE . service access. QoS. IMS and others Part 4: Getting started with EPS: Introducing the new FOKUS OpenEPC testbed toolkit . mobility management.) „ Simplified EPC architecture over E-UTRAN (MME. Part 3: Mobile Services beyond the EPC: Voice. Charging. HSS.

Competence Center NGNI Fraunhofer FOKUS AAA in EPC „ Authorization Authentication and Accounting (AAA) in the EPC is performed by the HSS. MME and 3GPP AAA Server and partially by the ePDG and trusted non3GPP access network „ Authentication is done using the AKA procedure for 3GPP and the EAP-AKA for non3GPP access networks „ The HSS stores the secret keys and sends a derivation of them (authentication vectors) to the MME or 3GPP AAA Server to perform the AKA procedures and derivate the session keys „ The ePDG is involved in the security tunnels authorization and authentication between the UE and the EPC through the non-3GPP untrusted network .

that is. source and destination port number. where each bearer is assigned one and only one QoS class Identifier (QCI) by the network. „ The network-initiated QoS control paradigm specified in EPS is a set of signaling procedures for managing bearers and controlling their QoS assigned by the network. „ An EPS bearer uniquely identifies packet flows that receive a common QoS treatment between the terminal and the gateway.Competence Center NGNI Fraunhofer FOKUS QoS in the EPS „ The “bearer” is a central element of the EPS QoS concept and is the level of granularity for bearer-level QoS control. „ A packet flow is defined by a five-tuple-based packet filter. and protocol ID . „ The EPS QoS concept is class-based. the packet filters in the terminal (for uplink traffic) and the gateway (for downlink traffic) determine the packet flows associated with an EPS bearer. ƒ The five-tuple contains source and destination IP address.

Dedicated EPS Bearers „ An EPS bearer is either a default or a dedicated bearer „ The default bearer is the bearer that is set up when the terminal attaches to the network ƒ ƒ ƒ One default bearer exists per terminal IP address. The default bearer provides the basic connectivity. .Competence Center NGNI Fraunhofer FOKUS Default vs. The QoS level of the default bearer is assigned based on subscription data. and it is kept for as long as the terminal retains that IP address.

and ƒ Policy and Charging Enforcement Function (PCEF) „ The deployment of the PCC architecture is optional for the EPC as the operator may decide to perform profile based QoS control (static) „ In Release 8 the PCC also includes the Bearer Binding and Event Reporting Function (BBERF) and two modes of operation of the PCRF for roaming scenarios Home-PCRF and Visited-PCRF with an interface (S9) between them „ The PCRF keeps control of the bearers and sessions established by the users and the treatment the network gives to them „ The QoS control in the PCC level is independent of the access network used as a standard set of parameters is used which are later translated to specific access parameters in the gateways . ƒ Policy and Charging Rules Function (PCRF) .Competence Center NGNI Fraunhofer FOKUS QoS and Charging in EPC „ QoS control and Charging control is done in the EPC following the architecture of the Policy and Charging Control (PCC) which has been available since 3GPP Release 7 „ The PCC (Release 7) comprises the ƒ Subscriber Profile Repository (SPR).

modification or release ƒ PUSH: the Application Function informs the PCRF upon new session establishment. modification or release The Bearer Binding and Session Binding mechanisms perform the adequate matching ƒ . credit management and reporting „ The Bearer Binding and Event Reporting Function (BBERF) is located in a peripheral gateway and does QoS control and event reporting „ Two modes of operation exist: PULL: the BBERF and PCEF inform the PCRF upon bearer level establishment.Competence Center NGNI Fraunhofer FOKUS QoS and Charging in EPC (2) „ The Policy and Charging Enforcement Function (PCEF) is co-located in the PDN-Gw and does firewall control and QoS enforcement.

Competence Center NGNI Fraunhofer FOKUS Mobility Management in EPC „ Mobility Management refers to the need of the UE to change the point of attachment to the EPC as it moves „ In the EPC mobility management involves the preservation of IP address of the UE during an attachment point modification „ Tunnels are established between an anchor point and the attachment point „ A signaling protocol is used for tunnel control „ On change of attachment a new tunnel is established and the anchor forwards packets through it .

as it was used in UTRAN ƒ GTP-C controls tunnel establishment. Target eNodeB informs MME of path switch after completion (if no MME relocation is required) „ UTRAN/GERAN mobility involves communication between SGSN and MME during the handover . modification and release ƒ GTP-U encapsulates user-plane packets (tunnel) „ Intra E-UTRAN mobility is done by eNodeBs involved.Competence Center NGNI Fraunhofer FOKUS Intra 3GPP Mobility „ Mobility between E-UTRAN. UTRAN and GERAN is anchored in the ServingGw „ GPRS Tunneling Protocol (GTP) is used for intra-3GPP mobility.

Competence Center NGNI Fraunhofer FOKUS Heterogeneous Mobility „ Mobility between 3GPP accesses and non-3GPP accesses uses standard IETF protocols „ Signaling is done using protocols of the family of Mobile IP (MIP) for the signaling „ Tunneling is done using Generic Routing Encapsulation (GRE) tunnels „ Two schemes supported ƒ ƒ Network Based Mobility ƒ Based on Proxy Mobile IP Protocol (PMIP) where the UE does not need any extensions as the mobility is fully handled by the network Host Based Mobility ƒ Based on Mobile IP (MIP) Foreign Agent (FA) which requires software extensions in the UE ƒ Based on Dual Stack MIP (DSMIP) for the case of heterogeneous IPv4/IPv6 networks .

UE selects the ePDG PDN GW selects the PCRF through Diameter Routing Agent (DRA) „ Reselection as part of the management and mobility procedures ƒ ƒ The eNodeB. ePDG etc. the S-GW.Competence Center NGNI Fraunhofer FOKUS Scalability by Selection Functions – Self Organizing Networks (SON) „ Each EPC entity is selected from a pool ƒ ƒ ƒ ƒ ƒ ƒ The The The The The The eNodeB is selected by the UE upon attachment eNodeB selects the MME MME selects the S-GW PDN GW is selected by the S-GW. the PDN GW may be changed during operation PCRF and HSS are the only entities to which the UE is remotely bound during full operation „ Allows easy integration / maintenance of network entities . the MME.

VoLGA) „ Potential LTE/EPC rollout strategies Part 4: Getting started with EPS: Introducing the new FOKUS OpenEPC testbed toolkit Part 5: Summary and Q&A . CS over PS. CS Fallback. and more) „ The LTE challenge: Voice over LTE Options (comparison of SRVCC.) Part 1: Converged NGN Overview Part 2: Evolved Packet Core (EPC) Part 3: Mobile Services beyond the EPC: Voice.Competence Center NGNI Fraunhofer FOKUS Detailed Agenda (cont. IMS. IMS and others „ EPS application domains (Internet.

IMS or any intranet) ƒ the internet or others „ Note that the EPC provides controlled IP connectivity.Competence Center NGNI Fraunhofer FOKUS EPC Capabilities = Seamless IP Connectivity „ The EPC allows multiple access networks to be connected in a controlled way (secure. QoS. seamless) to either ƒ the operator IP cloud (e.g. in regard to ƒ ƒ ƒ User authentication and authorization Quality of Service and related Charging Mobility Management Internet EPC Packet GW Packet GW E-UTRAN UTRAN WiMAX User Equipment May be connected to several IP service Domain in parallel IMS WLAN .

) IMS Internet Evolved Packet Core .Competence Center NGNI Fraunhofer FOKUS EPC connects to IP Service Domains „ The EPC provides connection to IP Service Domains ƒ IMS ƒ Internet ƒ other (P2P etc.

MMTel.Competence Center NGNI Fraunhofer FOKUS Simplified EPC Architecture with IMS PSTN Voice IMS MGW AS AS AS IMS Services: ICS. VCC PCRF P/I/SCSCF HSS PDN GW User Authentication MME Serving GW QoS based Policy & Charging ICS: IMS Centralised Services MMTel: Multimedia Telefony VCC: Voice Call Continuity Mobility Management S1 eNB E-UTRAN .

Competence Center NGNI

Fraunhofer FOKUS

IMS Standards Evolution in regard to Access Network Evolution
„ IMS developed as part of 3GPP Release 5 as an application development environment based on IN/CAMEL and VoIP (IETF) concepts and protocols
ƒ ƒ ƒ ƒ ƒ ƒ ƒ ƒ Encourage new applications on top of 3G networks Greater operator policing than native SIP/SDP Home control allowing service customization Standardized multimedia suite developed (ICS, MMTel, VCC) Optimizations for QoS and Charging (PCC) Access independence Extension of Session Mobility support Integration of IMS variants and requirements from 3GPP2, TISPAN, and Cablelabs
MMTel, ICS, VCC PCC

„ IMS retargeted in Release 7 for telephony replacement

„ Common IMS specified in Release 8

Competence Center NGNI

Fraunhofer FOKUS

IMS VoIP in EPC Architecture
IMS
GSM/PSTN/ UMTS MGW AS AS AS

IMS MMTel + ICS
PCRF

P/I/SCSCF

PDN HSS
Note that VoIP in the initial LTE deployments is unrealistic due to limited initial LTE coverage

GW MME Serving GW

S1 VoIP ???
eNB

E-UTRAN

Competence Center NGNI

Fraunhofer FOKUS

Voice in LTE Options
„ LTE being packet only does not include a final solution for providing voice calls over the new network in the near future ;-( „ Several solutions have been proposed and are under discussion: ƒ
I M S

ƒ ƒ ƒ

and handover from LTE to 2G/3G via dedicated IMS AS (SCC AS) ƒ IMS Centralized Services (ICS): IMS based solution evolved from older device centric Voice Call Continuity (VCC) and MMtel, MSC has to host IMS Client and MGw ƒ MMTel: IMS based solution for providing PSTN supplementary services for VoIP plus multimedia session handling capabilities (RCS) Circuit Switched Fallback (CSFB): all incoming/outgoing voice calls are immediately handed over from LTE to 2G/3G before call setup CS over EPS: MCS replacement by special EPS AS (still a study point) Voice over LTE using Generic Access Network (VoLGA): EPS behaves like an RNC or a BSC (CS over IP re-using UMA) Î no MSC changes!

Single Radio Voice Call Continuity (SR-VCC): IMS ICS based call control

MSC. can be used by GSM mobiles as well.UE VCC is an existing method. Supplementary services Compatible with SRVCC Only defines an interoperable way to handle speech sessions for IMS ICS X SCC AS Anchor and control sessions MSC. which has been improved for Single Radio Handover to 2G.Competence Center NGNI Fraunhofer FOKUS Voice over LTE Comparison Additional Component Approach Name Function Modified Components Main Advantage Main Disadvan tage Requires IMS and improvem ents in MSC and MME Requires IMS and complex AS 3GPP X X X IMS SR-VCC X VCC AS Anchor sessions in the IMS domain MME.UE MMTel X UE IMS centric solution .

Competence Center NGNI Fraunhofer FOKUS Voice over LTE Comparison II Additional Component Name Function Approach Modified Components Main Advantage Main Disadvant age 3GPP IMS CSFB X MSC. CS over EPS X eMSC MSC with new interface towards UE and MME AS behavior towards PCRF and PDN-Gw BSC or RNC behavior (A or Iu mode) towards CS.UE No support for voice in E-UTRAN under the supposition that it coexists with GERAN/UTRAN Additional delay. Follows the structure of already existing GAN specifications of 3GPP Not yet 3GPP solution. AS behavior towards PS Handover target selection UE CS signaling encapsulated over IP towards new eMSC VANC VOLGA UE HOSF CS signaling encapsulated over IP towards VANC. Not PS native solution.MME. Not PS native solution . suboptima l option Not yet completed .

CS over PS. and more) „ The LTE challenge: Voice over LTE Options (comparison of SRVCC.Competence Center NGNI Fraunhofer FOKUS Detailed Agenda (cont. IMS and others „ EPS application domains (Internet. IMS. CS Fallback.) Part 1: Converged NGN Overview Part 2: Evolved Packet Core (EPC) Part 3: Mobile Services beyond the EPC: Voice. VoLGA) „ Potential LTE/EPC rollout strategies Part 4: Getting started with EPS: Introducing the new FOKUS OpenEPC testbed toolkit Part 5: Summary and Q&A .

KT and SK Telecom in Asia . MetroPCS Wireless and US Cellular NTT-Docomo and KDDI in Japan (2010) T-Mobile. TeliaSonera. Telenor… China Mobile.Competence Center NGNI Fraunhofer FOKUS LTE/EPC Roadmap „ In 3GPP The Evolved Packet Core standardization has been completed with the LTE standardization in Release 8 (end 2008) ƒ Some features and issues left to Release 9 and Release 10 „ Operators committed to deploy LTE/E-UTRAN: ƒ ƒ ƒ ƒ ƒ USA : Verizon Wireless (2010). Telefonica. Vodafone. Tele2.

Competence Center NGNI Fraunhofer FOKUS Detailed Agenda (cont.) Part 1: Converged NGN Overview Part 2: Evolved Packet Core (EPC) Part 3: Mobile Services beyond the EPC: Voice. uses cases) „ Practical demonstrations will show the possible usage of the EPC based on the FOKUS OpenEPC platform Part 5: Summary and Q&A . IMS and others Part 4: Getting started with EPS: Introducing the new FOKUS OpenEPC testbed toolkit „ Overview of the OpenEPC toolkit (components. capabilities.

Competence Center NGNI Fraunhofer FOKUS From Open IMS to Open EPC: an important step towards the FI P2P Internet Rich Communications & Media Telecommunications IPTV PES Mobile Telecommunications FMC RCS IMS Internet EPC Future Internet Fixed Telecommunications Next Generation Mobile Next Network Generation Network Evolution .

net “Open IMS Core made the NGN world possible. OpenEPC will bring about the future mobile application sphere” .openepc.Competence Center NGNI Fraunhofer FOKUS From the Open IMS Core to an Open EPC platform www.

cable) and multi application domain support (OTT. Mobility. Security. P2P.) will become key for multimedia service delivery „ Based on the Open IMS Core success. etc. enabling academia and industry to ƒ integrate various network technologies and ƒ integrate various application platforms „ into a single local testbed.Competence Center NGNI Fraunhofer FOKUS What is the FOKUS OpenEPC platform „ In NGN/Converged NGNs multi access network support (fixed. mobile. lowering development costs „ This platform can be used to perform R&D in the fields of ƒ QoS. FOKUS is developing a NON-OPEN SOURCE EPC platform. Management „ Open EPC is conformant to 3GPP specifications (Rel 8) ƒ ƒ ƒ ƒ High performant Adaptable to different deployments Extensible to specific research needs Configurable . IMS.

configurability and extensibility have been respected in the overall architecture and the specific components „ In its first release a subset of functionalities and features is available as depicted below .Competence Center NGNI Fraunhofer FOKUS OpenEPC Architecture „ OpenEPC includes the main functionalities of 3GPP's Evolved Packet Core „ The principles of standards conformance.

„ The components that require dynamic configuration or provisioning of parameters (like PCRF. „ For instance. .Competence Center NGNI Fraunhofer FOKUS OpenEPC Architecture (cont. „ All software components of OpenEPC except myMONSTER client modules have been developed in C based on a high modular and configurable software framework. „ OpenEPC includes different components for the network entities as well as a demonstrative client module based on myMONSTER client framework and the myMONSTER Telco Communicator Suite (TCS). Such customizations are supported by simply modifying the XML configuration file and adding or deleting the lines for such modules. With this approach. This framework allows for easy configuration of components. Heterogeneous IPv4/IPv6 scenarios will be added in the future.) „ OpenEPC has been successfully tested for IPv4 and IPv6. OpenEPC supports customized components which can include or exclude some functionality or interfaces. a deployment could include a S-Gw which performs BBERF functionality of the Policy and Charging Control architecture or a PCRF which does not include S9 interface for roaming scenarios. HSS or ANDSF) offer a web-based front-end. selecting from the library of functionalities available. In complete configurations a common front-end is used to configure all components.

Sh „ The S6a.Competence Center NGNI Fraunhofer FOKUS OpenEPC Home Subscriber System (HSS) „ OpenEPC HSS provides storage and provisioning facilities for subscriber profile as defined in the EPC technical specification. . This interface permits the support of personalization through profiles. For this. „ The definition of the OpenEPC interface has been developed based on the Open IMS Core Sh interface used between HSS and an IMS Application Server with the addition of some specific Attribute Value Pairs (AVPs). it offers an implementation of the not yet standard interface Sp. It also performs the non-standard Subscriber Profile Repository (SPR) functionality described in the Policy and Charging Control (PCC) architecture documentation. „ Interfaces provided: ƒ ƒ Sp with ANDSF or PCRF IMS Interfaces: Cx. S6b and S6c will be added in a following release of OpenEPC. Concretely. Dx. the Data-Reference AVP has been extended to include parameters which are fetched from HSS and are used for policy control and for access network discovery and selection.

DPI system etc. „ The behavior of PCRF is controlled through XML described policies which can be provisioned from a GUI dynamically as well as stored in a file. „ The PCRF also subscribes to modifications in subscriber profile that may affect the policy decision or require it to be modified. This new PCRF aligns with the Release 8 requirements on interfaces (Gxx and S9 new interfaces) and functionality. . P-CSCF. „ Towards gateways the PCRF implements Gx and Gxx interfaces to the PCEF deployed in a PDN-Gw and to BBERF of an S-Gw or an ePDG.Competence Center NGNI Fraunhofer FOKUS OpenEPC PCRF „ The Policy and Charging Rules Function (PCRF) implementation of the OpenEPC is an evolution of the PCRF included in the FOKUS PoCCA component set which was released in January 2008. to consult the subscriber profile downloaded from the HSS/SPR via Sp interface and to make the policy decision to be enforced in network gateways using Gx and Gxx interfaces. „ The PCRF permits the application function (e.) to request resources and priority treatment from OpenEPC. through Rx interface.g. The policy description language complies with OMA Policy Expression Language extending it to support the necessary tags for the functionality of PCRF.

. „ The OpenEPC PCRF is suitable of performing TISPAN Resource and Admission Control Subsystem (RACS). It provides the Gqprima interface to application function and it is planned that it will be extended for next releases to support the Ia and Rq interfaces of RACS. therefore a specific deployment of OpenEPC PCRF is not forced to include all of them. In a further extension modules to include the Re interface and the e4 interface can be deployed to complete the overall RACS functions.) „ The development of interfaces of PCRF has been done as loadable modules.Competence Center NGNI Fraunhofer FOKUS OpenEPC PCRF (cont. „ PCRF Interfaces: ƒ ƒ ƒ ƒ ƒ ƒ Rx with Application Function Gqprima (ETSI) with Application Function Gx with PCEF in PDN-Gw Gxx with BBERF in S-Gw or ePDG Sp with SPR/HSS S9 with another PCRF „ Charging functionality is not currently part of the OpenEPC PCRF and it will be supported in a future release of OpenEPC. Service based Policy Decision Function (SPDF).

there will be support for other mobility protocols specified in the 3GPP EPC: Dual Stack Mobile IP (DSMIP). „ Support for S6a interface to AAA server will also be supported in the next releases. The enforcement of these rules is done through standard Linux network tools accessed through shell scripts. „ Current interfaces offered: ƒ PMIP based S5/S8 with Serving-Gw ƒ SGi with services domain ƒ S2b with the ePDG ƒ S2c with the UE ƒ Gx from co-located PCEF to PCRF „ In future releases. . and therefore fully configurable.Competence Center NGNI Fraunhofer FOKUS OpenEPC PDN Gateway (PDN-Gw) „ OpenEPC PDN-Gw includes a PMIPv4 or PMIPv6 stack configured as a Local Mobility Anchor (LMA). It also supports Policy and Charging Enforcement Function (PCEF) module for Policy and Charging Control. It allocates IP addresses from a provisioned pool. „ PCEF module permits to allocate default QoS values upon attachment of a new subscriber to the PDN and service specific rules when a user accesses a service. Mobile IP Foreign Agent Care of Address (MIP FACoA) and GRPS Tunneling Protocol (GTP).

This function permits to request QoS and priority parameters for IP flows associated with a subscriber. „ Current interfaces offered are: ƒ PMIP based S5/S8 to PDN-Gw ƒ Gxx from co-located BBERF to PCRF „ Support for GPRS Tunnelling Protocol (GTP) will be included in subsequent releases of OpenEPC .Competence Center NGNI Fraunhofer FOKUS OpenEPC Serving Gateway (Serving-Gw) „ OpenEPC Serving-Gw includes a PMIPv4 or PMIPv6 Mobility Access Gateway (MAG) function. Resulting QoS rules are enforced in the gateway by the standard Linux network tools (e. traffic classes etc. It also includes a module integrating with a standard DHCP server. „ The OpenEPC Serving-Gw can also include a Bearer Binding and Event Reporting Function (BBERF) for policy control.g.) through shell scripts that permit customization. The attachment of the user to EPC is detected in network level through the request of IP address and configuration parameters over DHCP. iptables.

Attachment of the user to EPC is detected in network level through the request of IP address and configuration parameters over DHCP. „ Current interfaces offered: ƒ ƒ Gxx of collocated BBERF with PCRF S2b between ePDG and PDN-Gw „ Future releases will support SWu interface and IPSec requests as an attachment trigger as well as SWm interface to AAA Server for authentication. „ OpenEPC ePDG can also include a Bearer Binding and Event Reporting Function (BBERF) for policy control.) through shell scripts that permit customization. . Resulting QoS rules are enforced in the gateway by the standard Linux network tools (iptables. It includes a module integrating with a standard DHCP server.Competence Center NGNI Fraunhofer FOKUS OpenEPC evolved Packet Data Network Gateway (ePDG) „ OpenEPC ePDG includes a PMIPv4 or PMIPv6 Mobility Access Gateway (MAG) function. traffic classes etc. This function permits to request QoS and priority parameters for IP flows associated with a subscriber.

. In further releases the ANDSF will include other interfaces and features as soon as they are standardized.302 ANDSF has a S14 interface with User Equipment (UE) used to provide information on access networks available in the vicinity of the subscriber and information on operator’s preference on these access networks. the OpenEPC ANDSF includes several nonstandard functionalities necessary to provide a demonstrative usage of its functionality. On its current status the description of ANDSF is included in 3GPP TS 24.312. At this point. The OpenEPC ANDSF includes an interface with the HSS based on the Sh interface between the AS and HSS which provides personalization based on subscribers’ profiles. This information is provided in an XML format specified by 3GPP under TS 24. The interfaces offered by the OpenEPC ANDSF are: ƒ ƒ „ „ Sp to HSS S14 to UE „ „ „ „ „ A GUI is included for configuring the behavior of the ANDSF for demonstration of different Always Best Connected (ABC) scenarios.Competence Center NGNI Fraunhofer FOKUS OpenEPC Access Network Discovery and Selection Function „ Access Network Discovery and Selection Function (ANDSF) is a new Release 8 feature of 3GPP that has not yet been fully standardized.

myMONSTER TCS offers the possibility of accessing IMS/SIP or Webbased services therefore permits trying out EPC functionalities in different configurations. ƒ ƒ ƒ It is the only non C component of OpenEPC. „ Besides that.mymonster.Competence Center NGNI Fraunhofer FOKUS OPENEPC enabled Client – MyMonster TCS „ OpenEPC includes an EPC ready client. detachments and handovers. It has been done as a module of the myMONSTER Telco Communicator Suite (TCS) Î www. . trigger attachments.org „ The OpenEPC module provides S14 interface to the ANDSF and a mobility manager that calls external scripts to switch on interfaces.

Competence Center NGNI Fraunhofer FOKUS OpenEPC Capabilities „ Mobility Support „ Policy and Charging Control „ Subscriber Handling and Databases „ Interconnection with Access Networks „ Interconnection with Applications and Services „ Security Support .

.e. The subscriber creates attaches to the new access network before detaching from the previous one. vertical handovers is provided using PMIP following the concept of make-before-break. Binding Revocations etc. Several technologies are supported for this. „ IP mobility between different access technologies i. „ For the realization of the Always-Best-Connected scenario in a converged network. „ OpenEPC includes a Proxy-MIP (PMIP) stack integrated in access gateways (S-Gw. In EPC a subscriber can hand over from one access network and technology to another preserving its IP address and IP connectivity. ePDG) and PDN-Gw. creating a new context with the same IP address to which traffic is forwarded seamlessly. from the GPRS Tunnelling Protocol (GTP) used in 3GPP access networks up to three different Mobile IP (MIP) variants. EPC includes the Access Network Discovery and Selection Function (ANDSF) which exchanges information of the available and preferred access networks with the User Equipment (UE).).Competence Center NGNI Fraunhofer FOKUS Mobility Support „ Mobility is one of the main features of EPC as it provides a converged core in which several wireless access networks are connected. PMIP is the newest MIP variant standardized by IETF and used in EPC with the necessary additions of 3GPP (GRE tunneling with keying support. This function is a Release 8 addition which still is being completed in Release 9 standardization work.

0 permits policy based QoS control relaying in Linux Gateway functionality (Firewalling.0 is the Release 8 compliant prototype of the Policy and Charging Control (PCC) architecture defined by 3GPP for EPC. detachments. These new features include: Introduction of the Bearer Binding and Event Reporting Function (BBERF) which is included in access network gateways Inclusion of PCEF in the Packet Data Network Gateway (PDN-Gw) instead of GGSN or ePDG as described in Release 7 Split of the Policy and Charging Rules Function (PCRF) functionality between Home-PCRF and Visited-PCRF for support of more flexible roaming scenarios Inclusion in all scenarios of Subscriber Profile Repository (SPR) for profile storage and its interface to PCRF (Sp) which is still not standardized.0 includes a Release 8 compliant PCRF. The BBERF and PCEF are integrated as part of the OpenEPC gateways and the PCRF is a standalone component of OpenEPC. Release 8 has introduced major changes to it. PoCCAv2.). PCEF and BBERF as well as an implementation of the Sp interface towards the HSS to access subscriber profile used in policy decisions. PoCCAv2. Packet Marking etc. handovers etc.) and co-location with OpenEPC mobility and address allocation solutions for triggering of network events (attachment. Even though the PCC architecture was already present in Release 7. „ „ „ „ „ .Competence Center NGNI Fraunhofer FOKUS PCC „ PoCCA version 2. in order to cope with the requirements of EPC. modifications.

„ An implementation of the 3GPP AAA Server will be included in a next release of OpenEPC. „ For authentication and access authorization functionality for the non-3GPP accesses. the 3GPP AAA Server already described in previous 3GPP releases is being integrated in EPC. as main subscriber information repository. The 3GPP AAA Server performs two roles: Server and Proxy in roaming scenarios.Competence Center NGNI Fraunhofer FOKUS Subscriber Handling and Databases „ EPC makes use of the Home Subscriber Server (HSS) already defined in the IP Multimedia Subsystem (IMS). „ The HSS in OpenEPC acts also as a Subscribers Profile Repository (SPR) defined in the Policy and Charging Control (PCC) architecture. . permitting access to subscribers’ profile both to PCRF and ANDSF based on an extension of Sh interface (interface between HSS and IMS Application Server) although 3GPP standards only include requirements for this interfaces and do not yet include any specification of how these are realized. The HSS in Release 8 includes new interfaces to EPC elements and new stored parameters necessary for EPC functionality.

„ OpenEPC provides the ANGw to interact with current 3G networks. .. referred generic as Access Network Gateways (ANGw). All these functions.Competence Center NGNI Fraunhofer FOKUS Interconnection with Access Networks „ Being a mobile core network EPC is connected to various access networks. a DHCP server/proxy function. They permit the triggering of EPC procedures and enforcement of EPC decisions. a BBERF. QoS enforcement functions etc. constitute the interface between the access networks and EPC and perform IP address allocation. „ In OpenEPC these functions are implemented as Linux software components that support the load of different modules (a PMIP MAG. a HRPD-Gw in HRPD or ASNGw in WiMAX or ePDG for other non-3GPP technologies. independent of physical or MAC procedures.) and interact with each other. a Linux Gateway firewalling and Diffserv packet marking function etc. This is done through peripheral gateways: S-Gw in 3GPP technologies. mobility functions. Wi-Fi networks or any other access network that provides IP connectivity.

Competence Center NGNI

Fraunhofer FOKUS

Interconnection with Applications and Services
„ OpenEPC provides interconnection between the Applications and Services layer and the network layer. EPC provides IP connectivity far beyond the concept of an IP pipe by supporting extended features like QoS, resource reservation, prioritization and information on events occurring in the access network (e.g. the mobile user lost the bearer, the mobile user changed access technology etc.), which are needed in multiple converged fixed and mobile networks scenarios. „ These features are realized through two interfaces. The SGi interface is the IP interface from PDN-Gw to applications layer through which user data is sent. The Rx interface from PCRF to application layer is the signaling interface based on Diameter that allows application layer to request special treatment to certain service flows and to get notifications upon events occurring in the access network. „ OpenEPC provides both interfaces and example functionality to demonstrate the interconnection to both Internet and the 3GPP IP Multimedia Subsystem (IMS).

Competence Center NGNI

Fraunhofer FOKUS

Interconnection with Applications and Services (cont.)
„ Internet OpenEPC provides Rx and SGi interfaces towards Internet or any other Service Delivery Platform. ƒ For demonstrative applications an HTTP Proxy/Transcoder or DPI system with support for Rx interface are used. „ IMS ƒ ƒ The combination of OpenIMSCore and OpenEPC provides a complete testing environment for 3GPP converged NGN technologies. Interconnection of IMS is done through Rx interface for signaling and SGi interface for data. Rx interface between the P-CSCF and PCRF supports the QoS and resource allocation for IMS sessions. This functionality is included in the PoCCA v2.0 architecture. Also the P-CSCF is notified, upon subscription, of the network connection status of the subscriber. This feature is referred as “notification of IMS signaling path status” in the 3GPP specifications. The P-CSCF can also indicate that an IP flow is being used for IMS signaling so that it can be treated with preference within EPC. Together with OpenEPC, IMS can realize its potential to provide an adequate platform for converged NGN scenarios in which QoS, mobility and security schemes are aligned between service layer and connectivity layer.

ƒ

ƒ

Competence Center NGNI

Fraunhofer FOKUS

OpenEPC Use Cases
„ Operators are using OpenEPC to prepare for the upcoming all-IP NGN world and have an open and vendor independent test-bed infrastructure. „ Manufacturers of individual EPC components are using OpenEPC to test their products in concert with a standards based converged NGN environment. „ Manufacturers of full EPC platforms are using OpenEPC for practical research on new concepts and protocols in an easier to maintain platform. „ Application developers are using OpenEPC to certify that their applications work in converged NGNs and take advantage of the functional capabilities offered by EPC to the applications domains. „ Research institutions and universities are using OpenEPC for practical all-IP NGN research , including usage of OpenEPC as black box for applications prototyping, or extending individual or multiple EPC components and/or developing new EPC components and protocols to provide new capabilities for integrating new networks or enabling new applications.

Competence Center NGNI Fraunhofer FOKUS OpenEPC Usage Scenarios „ Handovers in Heterogeneous Networks „ Support for Always best connected (ABC) „ Subscriber profile based personalization „ QoS provisioning „ Access to IMS services throough OpenEPC „ Access to Internet through OpenEPC .

„ „ „ „ „ „ . From the various mobility protocols supported by EPC. triggering new attachment and receiving packets over the old network until the new one is ready. The myMONSTER TCS module for EPC allows selecting which access network the user is connected to and modify this during a session. the IP address is allocated and a is tunnel established. no emulation is needed as the ePDG is connected physically with a Wi-Fi access point over which the address allocation is done. PMIP is a genuine network based mobility protocol which does not require a mobility stack in the User Equipment (UE) by transferring the mobility functionality to the network gateways. To emulate an operator controlled access in the public commercial UMTS network tunneling to OpenEPC Serving Gateway (S-Gw) is performed and over this tunnel a virtual IP address used in the lab is allocated.Competence Center NGNI Fraunhofer FOKUS Handovers in Heterogeneous Networks „ OpenEPC can connect to different types of access networks providing IP connectivity and handover between them. After attachment to an access network. OpenEPC currently integrates Proxy Mobile IP (PMIP). Within the Fraunhofer FOKUS laboratories in Berlin Wi-Fi access and the public commercial UMTS network are available. When the user attaches to the other access network the same IP address is preserved and the traffic is redirected to the new tunnel. These two gateways are connected with the PDN-Gw using PMIP Protocol (either IPv4 or IPv6 depending on the configuration) to get the IP address and establish IP tunnels for the traffic from and towards the user. providing seamless mobility. Over Wi-Fi.

the SGSN (S6d) and the AAA Server (SWx). „ The Policy and Charging Control (PCC) specifications consider another entity: the Subscriber Profile Repository (SPR). subscriptions for modification. They are used for authentication and updates of the context information when a subscriber attaches or modifies its attachment characteristics. The relation between the SPR and the HSS is not part of 3GPP Release 8 or Release 9. The Sp interface between the PCRF and the SPR has not yet been described by 3GPP. The Sp interface has been implemented based on the Sh interface (from HSS to IMS Application Server) defining new values for the contained AVPs (Attribute Value Pairs) e. . which contains policy data used by the PCRF as input for decisions on the service authorization and QoS control.Competence Center NGNI Fraunhofer FOKUS Subscriber profile based personalization „ Personalization is a key feature of the future next generation of fixed and mobile networks that permits discrimination of users and mobile devices based on their different requirements. „ The standardized EPC subscriber profile includes some information tokens which are used to offer personalization to subscribers like access restriction or QoS profiles. Data-Reference AVP and re-using the AVPs of the interfaces S6a. The Sh interface was already implemented in the Open IMS Core and provides the needed operations: profile fetching and updating. S6d and SWx to carry the data stored in the subscribers’ profile.g. „ 3GPP standards define the HSS as the main profile repository in EPC. The interfaces of the HSS include the interfaces to the MME (S6a). notifications pushing. „ OpenEPC uses the HSS and the standard profile data as SPR.

QoS Profile) to decide the content of the Inter-System Mobility Policies to offer to the specific subscriber modifying per-subscriber the access reselection decisions.g.) „ The Sp interface has been re-used as well in the ANDSF to provide personalization parameters for the access network reselection decisions.Competence Center NGNI Fraunhofer FOKUS Subscriber profile based personalization (cont. . The ANDSF upon attachment of a subscriber downloads the profile from the HSS and checks the access restriction and other profile items (e.

. PCRF enforces in the gateways different QoS parameters for the connection associated with that service. „ On service establishment of EPC ready services (e. They can enforce the Diffserv class provided for the IP flows and the bandwidth limitations. „ Upon attachment a default bearer QoS profile is selected by the PCRF and provided to the gateways.Competence Center NGNI Fraunhofer FOKUS QoS provisioning „ OpenEPC includes the features of the Policy and Charging Control (PCC) architecture that permit to provide QoS provisioning. IMS services). The bandwidth limitations are performed proactively by setting limits or reactively by activating bandwidth usage monitoring and providing alerts to the PCRF upon usage exceeding the limits. the Application Function (AF) requests to the PCRF service authorization and resource reservation identifying which service its being established.g. The gateways of OpenEPC support the BBERF or PCEF functionalities that enforce the policies provided by the PCRF.

like the loss of bearer or release of bearer which are supported by the OpenEPC Policy and Charging Control architecture.org ) provides the perfect extension to the OpenEPC in this area. „ The P-CSCF can request the PCRF to inform upon events in the IP Connectivity of a subscriber that affect the service given.openimscore. IMS can be used for Voice over IP (VoIP) or other multimedia services. the PCRF supports different configurations which can give preference to that specific bearer over the others. Moreover the P-CSCF can inform OpenEPC through the Rx interface upon user registration to the IMS that a network connection is being used for IMS signaling.Competence Center NGNI Fraunhofer FOKUS Access to IMS services „ To access IP Multimedia Subsystem (IMS) services with QoS. The OpenIMSCore (www. IP mobility and security OpenEPC is used. Independent of the service being used the P-CSCF of OpenIMSCore includes the Rx interface towards the PCRF and requests service authorization and resource reservation from OpenEPC. .

this will be included in the next releases of OpenEPC. „ Such a DPI could be integrated within the PDN-Gw of OpenEPC as a module. This will require some extensions to the Gx interface which has not been designed to support this use case. video portal) through HTTP the EPC provides a better Diffserv traffic class what will offer preferential treatment in gateways upon congestion. As an example when a user requests access to a known real-time application server (e. reducing latency. when requests are identified to known Internet services. in order to make use of the advantages of the communication between the applications and the EPC providing a better control of network usage several solutions are possible. This HTTP Proxy offers several advantages. the EPC can provide improved QoS and better control.g.Competence Center NGNI Fraunhofer FOKUS Access to Internet through EPC „ OpenEPC can be used to connect to plain Internet. „ A Deep Packet Inspection (DPI) system with Rx interface can also be used to provide information from the application being used by the user to the PCRF and request preferential treatment. „ For demonstrations a HTTP Proxy enabled with the Rx interface can be used. For example a network operator that has an agreement to provide VoIP through Skype would like to guarantee preferential treatment for the Skype flows for its subscribers. .

HSS. and perform research developments in the area of next generation of fixed and mobile networks. „ The specific components that are part of the current release 1 of OpenEPC are: a S-Gw and ePDG (including a BBERF from PCC Release 8). Customizable and extensible – permitting the set-up of different environments and adapting to new requirements that may appear within standardization process Reliable – based on the know-how gained in previous component development like the Open IMS Core project Conformant to standards . and a corresponding EPCclient. ANDSF. test. PDN-Gw (including a PCEF from PCC Release 8). „ OpenEPC is both IPv4 and IPv6 compatible and its components have been developed in C under Linux for high performance. monitor.can be used for testing other commercial components as well . measure.Competence Center NGNI Fraunhofer FOKUS OpenEPC Technical Aspects „ OpenEPC is a software implementation of a set of standard EPC components which permits the cost efficient establishment of all-IP NGN testbeds to prototype. „ All these components have been designed to be: ƒ ƒ ƒ ƒ ƒ Configurable – allowing easy modification of the behavior of components and the inclusion of optional features. PCRF.

*MIP features.Competence Center NGNI Fraunhofer FOKUS Connection to the OpenEPC „ From the access networks IP connection (v6 or v4) Attachment trigger: DHCP Requests Installation of a generic ANGw with or without BBERF. AAA interface etc. „ From the Application layers ƒ ƒ ƒ ƒ ƒ IP connection (v6 or v4) Signaling to PCRF trough Rx interface for authorization. policing and QoS control .

being an independent organization and having commercial deployment out of scope constitutes a great advantage ƒ Configurability: OpenEPC can be configured to match your needs for testing only some components or use cases ƒ Extensibility: adding new functionality whether new mobility schemes or QoS protocols or other functionality added to the components is as easy as it gets with the modular. because of its: Standards conformance: OpenEPC has been done with the standards in mind. or optimizations of the architecture. like the integration of new fixed and wireless access technologies. . as well as conformance testing. namely the Evolved Packet Core architecture. new approaches to mobility and QoS. design of new seamless wireless applications. OpenEPC supports research and development of challenging aspects of upcoming all-IP NGN infrastructures and services. standard based OpenEPC architecture „ Open EPC aims to provide its users with a basic understanding and practical hands on experiences with EPC. and the investigation of new business models in the next generation of fixed and mobile networks.Competence Center NGNI Fraunhofer FOKUS OpenEPC for Research and Development „ OpenEPC enables a quick start on the heart of emerging mobile networks. With OpenEPC it is possible to develop functional extensions of individual and/or multiple EPC components and new NGNM showcases. ƒ „ In addition.

net . either with source code or as binary implementation of individual components or complete platform. interfaces and protocols. „ The software is available under license for testing and research activities.Competence Center NGNI Fraunhofer FOKUS OpenEPC Software Availability „ The OpenEPC will be demonstrated to the public at the 5th FOKUS IMS Workshop in November 2009 in Berlin. „ For more information on how to get the OpenEPC refer to: Î info@openepc. From this moment the software will be made available to selected partners. „ Subsequent OpenEPC releases will be made available in spring 2010 and end of summer 2010 adding more functionalities.

„ In the same way Fraunhofer FOKUS and TU Berlin are interested in setting up joint R&D projects based on the OpenEPC platform.Competence Center NGNI Fraunhofer FOKUS OpenEPC Releases and Roadmap „ OpenEPC is available under license either as a complete testbed or as individual components for research and development purposes. as well as extensions to OpenEPC components to meet specific customer requirements. OpenEPC integrates with various access networks and different services platforms to provide a complete all-IP networks solution. . roaming configurations support. „ The planned releases of OpenEPC are as follows: ƒ November 2009: First demonstration of OpenEPC and availability for partners at 5th FOKUS IMS Workshop ƒ Spring 2010: First Release of OpenEPC: will include more mobility options. and support for security procedures ƒ End of Summer 2010: Second Release and full OpenEPC „ We are able to provide on-site coaching. support. local deployment and integration activities.

Competence Center NGNI Fraunhofer FOKUS OpenEPC Architecture „ Conformant to the 3GPP Standards „ Highly modularized „ Configurable „ Reliable „ Customizable and extensible .

Competence Center NGNI Fraunhofer FOKUS OpenEPC Demo in our Labs „ Mobility and Personalization „ Personalization and QoS Control „ Session Adaptation – Mobility and Interaction with Applications „ Internet Based Services Integration „ IMS Based Services Integration .

Competence Center NGNI

Fraunhofer FOKUS

And we showed the prototype live … so stay tuned for more!

Competence Center NGNI

Fraunhofer FOKUS

Detailed Agenda (cont.)
Part 1: Converged NGN Overview Part 2: Evolved Packet Core (EPC) Part 3: Mobile Services beyond the EPC: Voice, IMS and others Part 4: Getting started with EPS: Introducing the new FOKUS OpenEPC testbed toolkit

Part 5: Summary and Q&A

Competence Center NGNI

Fraunhofer FOKUS

Do you want to see more? Look at our Event Minutes!

Featuring: • Four tutorials and  interactive Workshops on Day 1 related to Rich Communications, Rich Media,  Future Internet and Open NGN / IMS Testbeds • Social evening event for Networking • Full day NGN2FI Conference on Day 2 • Many Operator Talks and Vendor Exposition • FOKUS Playground Visits and Technology Demonstrations

Competence Center NGNI Fraunhofer FOKUS Current R&D Focus: NGN Evolution towards Future Internet Information Technologies (Service Oriented Architectures) Service Architectures Telecommunications PES Internet RCS Fixed and Mobile Telecommunications FMC 3/4 Play IPTV Next Generation Network IMS P2P EPC Future Internet Clean Slate Design Autonomic Communications Evolution Revolution .

e.0 applications „ Development of Open Evolved Packet Core (OpenEPC) „ Strong cooperation with TUB Chair AV „ R&D on middleware and Service Delivery Platform (SDP) implementation options above converging networks and Next Generation Networks (NGNs) „ R&D on NGN to Future Internet Evolution (NGN2FI) . FMC. manageability „ Evolution towards all-IP converged NGNs „ Provision of NGN service and related tools. efficiency. reliability.Competence Center NGNI Fraunhofer FOKUS NGNI – Next Generation Network Infrastructures From Next Generation Networks to the Future Internet „ R&D on advanced network and service control protocols and related components for multimedia services. security.g. including integration with legacy networks „ Prototyping of converged multimedia applications. 4Play & Telco 2. with special focus on: ƒ Reusability.

Competence Center NGNI Fraunhofer FOKUS NGNI – Next Generation Network Infrastructures Enabling rich multimedia communications over converging networks Key Technologies „ Open IMS Core „ Converged Open Messaging Server (COMS) „ Anubis Gate – a Telco 2.0 gateway „ XPOSER – an OSE-based service broker „ myMonster – the Convergent Client Framework „ OpenEPC „ Teagle – Testbed search tool Key Laboratories „ Open SOA Telco Playground „ FI Technologies Lab Key Projects „ Deutsche Telekom Service Broker and Integrated Service Architecture „ BMBF MAMSplus – Service composition and management for NGN/IMS „ EU Panlab II (PII) – Federation and management of distributed NGN/Future internet testbeds „ BMBF Project G-Lab_Deep „ EU PEACE – Emergency support extensions for IMS-based network „ Multimedia session continuity & policybased QoS control for NGN and LTE „ Various industry NGN testbed deployments with operators .

• Identity Management • IMS/P2P Interation • Seamless Handover Support• Testbed Security • Evolved Packet Core • Testbed Federation Tool • FI Crosslayer composition • Semantic Service Composition Reliable Networking Infrastructures (RNI) Team Evolving Infrastructure and Services (EIS) Team .Competence Center NGNI Fraunhofer FOKUS NGNI Research Teams and Testbeds & Tools • • • • • Integrative Service Architecture (ISA) Team SOA based Service Delivery Platforms Open Network API Gateways Intelligent Service Brokers Integrative Service UE Client Integrative Service prototyping • NGN Emergency Support • NGN Security extensions • SOA Network Model.

Competence Center NGNI Fraunhofer FOKUS OpenEPC is just one Toolkit out of much more … .

Competence Center NGNI Fraunhofer FOKUS OpenEPC is just one Toolkit out of much more … .

Competence Center NGNI Fraunhofer FOKUS FOKUS all-IP NGN and FI Research. Tools and Testbeds .

Competence Center NGNI Fraunhofer FOKUS Contact If you have questions about OpenEPC.net More information about OpenEPC can be found at „ www.openepc.net . contact the experts at „ info@penepc.

Sign up to vote on this title
UsefulNot useful