Training - Evolved Packet Core


Not only does 3GPP define a completely new air interface referred to as Evolved UMTS Terrestrial Radio Access Network (E-UTRAN) but also an Evolved Packet Core (EPC) as part of the System Architecture Evolution. The latter represents the framework for an evolution or migration of the 3GPP system to a higher-data rate, lower-latency, packet-optimized system that supports multiple radio access technologies (RATs). It is based on a flat, simplified all IP-based architecture with a reduced number of network entities, a new Quality of Service concept, and the support of seamless mobility between heterogeneous access networks. 3GPP has completed the standardization and first EPC networks are already in operation.


This training course will provide participants with a detailed understanding of the general EPC architecture and protocols that form part of the latest version of 3GPP specifications. In detail, the course covers the architectural layout and the newly-defined network nodes in the Evolved Packet Core (EPC) network. All relevant interfaces between these nodes and the Enhanced UMTS Terrestrial Radio Access Network (E-UTRAN) as well as the underlying protocol stack will be explained. A special focus will be on Non-Access Stratum (NAS) signaling between User Equipment (UE) in the E-UTRAN and EPC network, as well as on the overall Quality-of-Service (QoS) concept. Moreover, authentication, addressing, security and location management within the service area will be treated. One final aspect will be coupling of the EPC network with previously standardized 3GPP radio access networks (e.g. the UTRAN) and other potential non-3GPP IP-based access networks (e.g. WiMAX).

Day1 – Evolved Packet Core architecture and entities

Introduction to Evolved Packet Core
•    Recapitulating existing 3GPP GPRS Core network architecture
•    Overview of the new 3GPP Evolved Packet Core (EPC) network architecture
•    Possible coupling of EPC with various IP-based (radio) access networks
•    Extending to roaming case

Voice over IP and IMS Service Architecture
•    Recapitulating TCP/IP protocol suite and DiffServ
•    Circuit and packet switched voice
•    IMS architecture and nodes
•    IMS protocols: SIP, SDP, RTP and RTCP

Mobility Management within SAE
•    Functionality of Mobility Management Entity (MME) node
•    Mobility Management (MM) and Session Management (SM)  
•    S1-MME interface with E-UTRAN and corresponding protocol stack  
•    S11 interface with gateway and corresponding protocol stack
•    EPS Security Management

Gateway Functionality within SAE
•    Functionality of Serving Gateway (S-GW) node
•    S1-U interface with E-UTRAN and the corresponding protocol stack
•    Functionality of Packet Data Network Gateway (P-GW) node
•    S5/S8 interface with S-GW and the corresponding protocol stack
•    IP address allocation issues
•    SGi interface with external IP-based network

Information Storage and Addressing within SAE
•    Context stored inside MME, S-GW, P-GW, and HSS node
•    Hierarchical network node and UE addressing scheme

Day2 – QoS and EPC Procedures as well as multi-radio access

QoS Concept within SAE
•    SAE QoS concept and bearer level parameters
•    Functionality of Policy Control and Charging Rules Function (PCRF) node
•    S7 interface with S-GW and P-GW

Selected NAS Signalling Procedures  
•    Initial Attach
•    Tracking Area Update
•    Service Request
•    S1 Release and Detach
•    Session Management and QoS
•    Intra E-UTRAN Handover

Coupling of EPC Network with GPRS Core Network
•    S3 interface between MME and SGSN and the corresponding protocol stack
•    S4 interface between S-GW and SGSG and the corresponding protocol stack
•    S12-interface for direct tunnel between S-GW and UTRAN and corresponding protocol stack
•    Selected NAS signalling: Routing Area Update, E-UTRAN to UTRAN handover

Brief Overview: Coupling of EPC Network with Trusted non-3GPP Access Network (e.g. WiMAX)
•    S2a interface and the corresponding protocol stack
•    S2c interface and the corresponding protocol stack