Beruflich Dokumente
Kultur Dokumente
System Architecture Evolution (aka SAE) is the core network architecture of 3GPP's LTE wireless communication standard. SAE is the evolution of the GPRS Core Network, with some differences: simplified architecture all-IP Network (AIPN) support for higher throughput and lower latency radio access networks (RANs) support for, and mobility between, multiple heterogeneous access networks, including E-UTRA (LTE and LTE Advanced air interface), 3GPP legacy systems (for example GERAN or UTRAN, air interfaces of GPRS and UMTS respectively), but also non-3GPP systems (for example WiMAX or cdma2000)
Contents
1 SAE Architecture 2 Non Access Stratum (NAS) protocols 2.1 EMM (EPS Mobility Management) 2.2 ESM (EPS Session Management) 3 EPC protocol stack 3.1 MME (Mobility Management Entity) protocols 3.2 SGW (Serving Gateway) protocols 3.3 PGW (Packet Data Network Gateway) protocols 4 Support of voice services and SMS 5 Multiple access networks 6 3GPP releases 7 Reading 8 References 9 External links
SAE Architecture
The SAE has a flat, all-IP architecture with separation of control plane and user plane traffic. The main component of the SAE architecture is the Evolved Packet Core (EPC), also known as SAE Core . The EPC will serve as the equivalent of GPRS networks (via the Mobility Management Entity, Serving Gateway and PDN Gateway subcomponents). The subcomponents of the EPC are:[1][2] MME (Mobility Management Entity): The MME is the key control-node for the LTE accessnetwork. It is responsible for idle mode UE (User Equipment) tracking and paging procedure including retransmissions. It is involved in the bearer activation/deactivation process and is also responsible for choosing the SGW for a UE at the initial attach and at time of intra-LTE handover involving Core
http://en.wikipedia.org/wiki/System_Architecture_Evolution 1/8
4/3/2014
Network (CN) node relocation. It is responsible for authenticating the user (by interacting with the HSS). The Non Access Stratum (NAS) signaling terminates at the MME and it is also responsible for generation and allocation of temporary identities to UEs. It checks the authorization of the UE to camp on the service providers Public Land Mobile Network (PLMN) and enforces UE roaming restrictions. The MME is the termination point in the network for ciphering/integrity protection for NAS signaling and handles the security key management. Lawful interception of signaling is also supported by the MME. The MME also provides the control plane function for mobility between LTE and 2G/3G access networks with the S3 interface terminating at the MME from the SGSN. The MME also terminates the S6a interface towards the home HSS for roaming UEs. SGW (Serving Gateway): The evolved packet core structure SGW routes and forwards user data packets, while also acting as the mobility anchor for the user plane during inter-eNodeB handovers and as the anchor for mobility between LTE and other 3GPP technologies (terminating S4 interface and relaying the traffic between 2G/3G systems and PGW). For idle state UEs, the SGW terminates the downlink data path and triggers paging when downlink data arrives for the UE. It manages and stores UE contexts, e.g. parameters of the IP bearer service, network internal routing information. It also performs replication of the user traffic in case of lawful interception. PGW (PDN Gateway): The PDN Gateway provides connectivity from the UE to external packet data networks by being the point of exit and entry of traffic for the UE. A UE may have simultaneous connectivity with more than one PGW for accessing multiple PDNs. The PGW performs policy enforcement, packet filtering for each user, charging support, lawful interception and packet screening. Another key role of the PGW is to act as the anchor for mobility between 3GPP and non-3GPP technologies such as WiMAX and 3GPP2 (CDMA 1X and EvDO). HSS (Home Subscriber Server): The HSS is a central database that contains user-related and subscription-related information. The functions of the HSS include functionalities such as mobility management, call and session establishment support, user authentication and access authorization. The HSS is based on pre-Rel-4 Home Location Register (HLR) and Authentication Center (AuC). ANDSF (Access Network Discovery and Selection Function): The ANDSF provides information to the UE about connectivity to 3GPP and non-3GPP access networks (such as Wi-Fi). The purpose of the ANDSF is to assist the UE to discover the access networks in their vicinity and to provide rules (policies) to prioritize and manage connections to these networks. ePDG (Evolved Packet Data Gateway): The main function of the ePDG is to secure the data transmission with a UE connected to the EPC over an untrusted non-3GPP access. For this purpose, the ePDG acts as a termination node of IPsec tunnels established with the UE.
4/3/2014
The Non-Access Stratum (NAS) protocols form the highest stratum of the control plane between the user equipment (UE) and MME.[3] NAS protocols support the mobility of the UE and the session management procedures to establish and maintain IP connectivity between the UE and a PDN GW. They define the rules for a mapping between parameters during inter-system mobility with 3G networks or non-3GPP access networks. They also provide the NAS security by integrity protection and ciphering of NAS signaling messages. EPS provides the subscriber with a "ready-to-use" IP connectivity and an "always-on" experience by linking between mobility management and session management procedures during the UE attach procedure. Complete NAS transactions consist of specific sequences of elementary procedures with EPS Mobility Management (EMM) and EPS Session Management (ESM) protocols.
4/3/2014
EPS Bearer: Each EPS bearer context represents an EPS bearer between the UE and a PDN. EPS bearer contexts can remain activated even if the radio and S1 bearers constituting the corresponding EPS bearers between UE and MME are temporarily released. An EPS bearer context can be either a default bearer context or a dedicated bearer context. A default EPS bearer context is activated when the UE requests a connection to a PDN. The first default EPS bearer context, is activated during the EPS attach procedure. Additionally, the network can activate one or several dedicated EPS bearer contexts in parallel. Generally, ESM procedures can be performed only if an EMM context has been established between the UE and the MME, and the secure exchange of NAS messages has been initiated by the MME by use of the EMM procedures. Once the UE is successfully attached, the UE can request the MME to set up connections to additional PDNs. For each additional connection, the MME activates a separate default EPS bearer context. A default EPS bearer context remains activated throughout the lifetime of the connection to the PDN. Types of ESM procedures: ESM involves different types of procedures such as: EPS bearer contexts procedures initiated by the network and are used for the manipulation of EPS bearer contexts, including Default EPS bearer context activation, Dedicated EPS bearer context activation, EPS bearer context modification, EPS bearer context deactivation. Transaction related procedures initiated by the UE to request for resources, i.e. a new PDN connection or dedicated bearer resources, or to release these resources. They include PDN connectivity procedure, PDN disconnect procedure, Bearer resource allocation procedure, Bearer resource modification procedure. The MME maintains EMM context and EPS bearer context information for UEs in the ECM-IDLE, ECM CONNECTED and EMM-DEREGISTERED states.
4/3/2014
transfer function, Mobility functions for UE, Paging, Reset functionality, NAS signaling transport function, Error reporting, UE context release function, Status transfer. MME supports S11 interface with Serving Gateway. The integrated S11 interface stack consists of IP, UDP, eGTP-C.
SGW supports S11 interface with MME and S5/S8 interface with PGW. The integrated control plane stack for these interfaces consists of IP, UDP, eGTP-C. SGW supports the S1-U interface with eNodeB and S5/S8 data plane interface with PGW. The integrated data plane stack for these interfaces consists of IP, UDP, eGTP-U.
4/3/2014
3GPP releases
The 3GPP delivers standards in parallel releases, which compose consistent sets of specifications and features.
http://en.wikipedia.org/wiki/System_Architecture_Evolution
6/8
4/3/2014
Version[5] Release 7
Released[6] 2007 Q4
Info[7] Feasibility study on All-IP Network (AIPN) First release of EPC. SAE specification: high level functions, support of LTE and other 3GPP accesses, support of non-3GPP accesses, inter-system mobility, Single Radio Voice Call Continuity (SRVCC), CS fallback. Earthquake and Tsunami Warning System (ETWS). Support of Home Node B / Home eNode B. LCS control plane for EPS. Support of IMS emergency calls over GPRS and EPS. Enhancements to Home Node B / Home eNode B. Public Warning System (PWS). Network improvements for machine-type communications. Various offload mechanisms (LIPA, SIPTO, IFOM). Further improvements for machine-type communications. Simulation of USSD in IMS. QoS control based on subscriber spending limits. Further improvements to LIPA and SIPTO. Single Radio Video Call Continuity (vSRVCC). Single Radio Voice Call Continuity from UTRAN/GERAN to HSPA/E-UTRAN (rSRVCC). Support of interworking with Broadband Forum accesses. Work in progress (as of October 2012). LIPA Mobility and SIPTO at the Local Network. IMS-based telepresence. Service and Media Reachability for Users over Restrictive Firewalls (SMURFs).
Release 8
2008 Q4
Release 9 Release 10
2009 Q4 2011 Q1
Release 11
2012 Q3
Release 12
2014 Q2
Reading
3GPP page on SAE (http://www.3gpp.org/The-Evolved-Packet-Core) 3GPP TS 23.401: General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access (http://www.3gpp.org/ftp/Specs/htmlinfo/23401.htm) 3GPP TS 23.402: 3GPP System Architecture Evolution (http://www.3gpp.org/ftp/Specs/htmlinfo/23402.htm) 3GPP LTE-SAE Overview, by Ulrich Barth (http://www.ikr.unistuttgart.de/Content/itg/fg524/Meetings/2006-09-29-Ulm/01-3GPP_LTE-SAE_Overview_Sep06.pdf) (SAE in 2006)
References
1. ^ 3GPP TS 23.002: Network architecture (http://www.3gpp.org/ftp/Specs/html-info/23002.htm) 2. ^ LTE White Paper 3. ^ 3GPP TS 24.301: Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 (http://www.3gpp.org/ftp/Specs/html-info/24301.htm) 4. ^ Dispelling LTE Myths (http://www.3gpp.org/Dispelling-LTE-Myths) 5. ^ 3GPP releases (http://www.3gpp.org/releases) 6. ^ 3GPP Specifications - Releases (and phases and stages) (http://www.3gpp.org/specs/releases.htm)
http://en.wikipedia.org/wiki/System_Architecture_Evolution 7/8
4/3/2014
LTE White Paper: "Long Term Evolution (LTE):A Technical Overview" (http://www.scribd.com/doc/129324781/6834-MotDoc). Motorola. Strategic White Paper: "Introduction to Evolved Packet Core" (http://downloads.lightreading.com/wplib/alcatellucent/ALU_WP_Intro_to_EPC.pdf) (PDF). AlcatelLucent. Technical White Paper: "Evolved Packet Core solution: Innovation in LTE core" (http://downloads.lightreading.com/wplib/alcatellucent/ALU_WP_EPC_Technology.pdf) (PDF). AlcatelLucent. SAE test bed: "Nomor provides SAE (System Architecture Evolution) test bed within the SEA project" (http://www.nomor.de/home/company/company-news/news/news/nomor-provides-sae-systemarchitecture-evolution-test-bed-within-the-sea-project). Nomor Research.
External links
Free and open source framework implementation of SGW/PGW and MME emulator (http://sourceforge.net/projects/nwepc) Retrieved from "http://en.wikipedia.org/w/index.php?title=System_Architecture_Evolution&oldid=570488283" Categories: Internet Protocol LTE (telecommunication) This page was last modified on 28 August 2013 at 04:12. Text is available under the Creative Commons Attribution-ShareAlike License; additional terms may apply. By using this site, you agree to the Terms of Use and Privacy Policy. Wikipedia is a registered trademark of the Wikimedia Foundation, Inc., a non-profit organization.
http://en.wikipedia.org/wiki/System_Architecture_Evolution
8/8