System Architecture Evolution

Last updated

System Architecture Evolution (SAE) is the core network architecture of mobile communications protocol group 3GPP's LTE wireless communication standard.

Contents

SAE is the evolution of the GPRS Core Network, but with a simplified architecture; an all-IP Network (AIPN); support for higher throughput and lower latency radio access networks (RANs); and support for, and mobility between, multiple heterogeneous access networks, including E-UTRA (LTE and LTE Advanced air interface), and 3GPP legacy systems (for example GERAN or UTRAN, air interfaces of GPRS and UMTS respectively), but also non-3GPP systems (for example Wi-Fi, WiMAX or CDMA2000).

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).

Evolved Packet Core (EPC)

EPC nodes and interfaces Evolved Packet Core.svg
EPC nodes and interfaces

The subcomponents of the EPC are: [1] [2]

MME (Mobility Management Entity)

The MME is the key control-node for the LTE access-network. It is responsible for idle mode User Equipment (UE) paging and tagging procedure including retransmissions. It is involved in the bearer activation/deactivation process and is also responsible for choosing the Serving Gateway for a UE at the initial attach and at time of intra-LTE handover involving Core Network (CN) node relocation. It is responsible for authenticating the user (by interacting with the Home Subscriber Server). 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 provider's 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 HSS for roaming UEs.

SGW (Serving Gateway)

The Serving Gateway 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 Packet Data Network Gateway). For idle state User Equipment, the Serving Gateway terminates the downlink data path and triggers paging when downlink data arrives for the User Equipment. 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 (Packet Data Network Gateway)

The Packet Data Network Gateway (PDN Gateway, also PGW) provides connectivity from the User Equipment (UE) to external packet data networks (PDNs) by being its point of exit and entry of traffic. A piece of User Equipment may have simultaneous connectivity with more than one Packet Data Network Gateway for accessing multiple packet data networks. The PDN Gateway performs policy enforcement, packet filtering for each user, charging support, lawful interception and packet screening. Another key role of the Packet Data Network Gateway 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 Home Subscriber Server is a central database that contains user-related and subscription-related information. The functions of the HSS include 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 untrusted non-3GPP access, e.g. VoWi-Fi. For this purpose, the ePDG acts as a termination node of IPsec tunnels established with the UE.

Non Access Stratum (NAS) protocols

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 (Evolved Packet System) 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.

EMM (EPS Mobility Management)

The EPS (Evolved Packet System) Mobility Management (EMM) protocol provides procedures for the control of mobility when the User Equipment (UE) uses the Evolved UMTS Terrestrial Radio Access Network (E-UTRAN). It also provides control of security for the NAS protocols.

EMM involves different types of procedures such as:

The UE and the network execute the attach procedure, the default EPS bearer context activation procedure in parallel. During the EPS attach procedure the network activates a default EPS bearer context. The EPS session management messages for the default EPS bearer context activation are transmitted in an information element in the EPS mobility management messages. The UE and network complete the combined default EPS bearer context activation procedure and the attach procedure before the dedicated EPS bearer context activation procedure is completed. The success of the attach procedure is dependent on the success of the default EPS bearer context activation procedure. If the attach procedure fails, then the ESM session management procedures also fails.

ESM (EPS Session Management)

The EPS Session Management (ESM) protocol provides procedures for the handling of EPS bearer contexts. Together with the bearer control provided by the Access Stratum, it provides the control of user plane bearers. The transmission of ESM messages is suspended during EMM procedures except for the attach procedure.

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:

The MME maintains EMM context and EPS bearer context information for UEs in the ECM-IDLE, ECM CONNECTED and EMM-DEREGISTERED states.

EPC protocol stack

MME (Mobility Management Entity) protocols

The MME protocol stack consists of:

  1. S1-MME stack to support S1-MME interface with eNodeB
  2. S11 stack to support S11 interface with Serving Gateway

MME supports the S1 interface with eNodeB. The integrated S1 MME interface stack consists of IP, SCTP, S1AP.

MME supports S11 interface with Serving Gateway. The integrated S11 interface stack consists of IP, UDP, eGTP-C.

SGW (Serving Gateway) protocols

The SGW consists of

  1. S11 control plane stack to support S11 interface with MME
  2. S5/S8 control and data plane stacks to support S5/S8 interface with PGW
  3. S1 data plane stack to support S1 user plane interface with eNodeB
  4. S4 data plane stack to support S4 user plane interface between RNC of UMTS and SGW of eNodeB
  5. Sxa: since 3GPP Rel.14, the Sx interface and the associated PFCP protocol was added to the SGW, allowing for the Control User Plane Separation between SGW-C and SGW-U.

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.

Main interfaces that P-GW shares with other EPC nodes P-GW main interfaces.jpg
Main interfaces that P-GW shares with other EPC nodes

PGW (Packet Data Network Gateway) protocols

Main interfaces supported by the P-GW are:

  1. S5/S8: this interface is defined between S-GW and P-GW. It is named S5 when the S-GW and the P-GW are located in the same network (non-roaming scenario) and S8 when the S-GW is located in the visited network and the P-GW in the home network (roaming scenario). eGTP-C and GTP-U protocols are used in the S5/S8 interface.
  2. Gz: this interface is used by the P-GW to communicate with the Offline Charging System (OFCS), mainly to send the Charging Data Records (CDRs) of the post-paid users via FTP.
  3. Gy: this interface is used by the P-GW to communicate with the Online Charging System (OCS). The P-GW informs the charging system about pre-paid users payload in real time. Diameter protocol is used in the Gy interface.
  4. Gx: this interface is used by the P-GW to communicate with the Policy and Charging Rules Function (PCRF) in order to handle Policy and Charging Rules (PCC) rules. These rules contain charging related information as well as quality of service (QoS) parameters that will be used in the bearer establishment. Diameter protocol is used in the Gx interface.
  5. SGi: this interface is defined between the P-GW and external networks, for example, Internet access, corporate access, etc.
  6. Sxb: since 3GPP Rel.14, the Sx interface and the associated PFCP protocol was added to the PGW, allowing for the Control User Plane Separation between PGW-C and PGW-U.

Support of voice services and SMS

The EPC is a packet-only core network. It does not have a circuit-switched domain, which is traditionally used for phone calls and SMS.

Support for Voice services in EPC

3GPP specified two solutions for voice:

Support for SMS services in EPC

3GPP specified three solutions for SMS:

CSFB and SMS over SGs are seen as interim solutions, the long term being IMS. [4]

Multiple access networks

The UE can connect to the EPC using several access technologies. These access technologies are composed of:

It is up to the network operator to decide whether a non-3GPP access technology is trusted or untrusted.

It is worth noting that these trusted/untrusted categories do not apply to 3GPP accesses.

3GPP releases

The 3GPP delivers standards in parallel releases, which compose consistent sets of specifications and features.

Version [5] Released [6] Info [7]
Release 72007 Q4Feasibility study on All-IP Network (AIPN)
Release 82008 Q4First 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.
Release 92009 Q4LCS 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).
Release 102011 Q1Network improvements for machine-type communications. Various offload mechanisms (LIPA, SIPTO, IFOM).
Release 112012 Q3Further 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.
Release 122015 Q1Enhanced Small Cells operation, Carrier Aggregation (2 uplink carriers, 3 downlink carriers, FDD/TDD carrier aggregation), MIMO (3D channel modelling, elevation beamforming, massive MIMO), MTC - UE Cat 0 introduced, D2D communication, eMBMS enhancements.
Release 132016 Q1Introduced LTE-U / LTE-LAA, LTE-M, Elevation beamforming / Full Dimension MIMO, Indoor positioning, LTE-M Cat 1.4 MHz & Cat 200 kHz
...
Release 18 https://www.3gpp.org/release18

Further reading

See also

03056876920

Related Research Articles

Non-access stratum (NAS) is a functional layer in the NR, LTE, UMTS and GSM wireless telecom protocol stacks between the core network and user equipment. This layer is used to manage the establishment of communication sessions and for maintaining continuous communications with the user equipment as it moves. The NAS is defined in contrast to the Access Stratum which is responsible for carrying information over the wireless portion of the network. A further description of NAS is that it is a protocol for messages passed between the User Equipment, also known as mobiles, and Core Nodes that is passed transparently through the radio network. Examples of NAS messages include Update or Attach messages, Authentication Messages, Service Requests and so forth. Once the User Equipment (UE) establishes a radio connection, the UE uses the radio connection to communicate with the core nodes to coordinate service. The distinction is that the Access Stratum is for dialogue explicitly between the mobile equipment and the radio network and the NAS is for dialogue between the mobile equipment and core network nodes.

The GPRS core network is the central part of the general packet radio service (GPRS) which allows 2G, 3G and WCDMA mobile networks to transmit Internet Protocol (IP) packets to external networks such as the Internet. The GPRS system is an integrated part of the GSM network switching subsystem.

The Radio Network Controller (RNC) is a governing element in the UMTS radio access network (UTRAN) and is responsible for controlling the Node Bs that are connected to it. The RNC carries out radio resource management, some of the mobility management functions and is the point where encryption is done before user data is sent to and from the mobile. The RNC connects to the Circuit Switched Core Network through Media Gateway (MGW) and to the SGSN in the Packet Switched Core Network.

Mobility management is one of the major functions of a GSM or a UMTS network that allows mobile phones to work. The aim of mobility management is to track where the subscribers are, allowing calls, SMS and other mobile phone services to be delivered to them.

The IP Multimedia Subsystem or IP Multimedia Core Network Subsystem (IMS) is a standardised architectural framework for delivering IP multimedia services. Historically, mobile phones have provided voice call services over a circuit-switched-style network, rather than strictly over an IP packet-switched network. Various voice over IP technologies are available on smartphones; IMS provides a standard protocol across vendors.

In telecommunications networks, RANAP is a protocol specified by 3GPP in TS 25.413 and used in UMTS for signaling between the Core Network, which can be a MSC or SGSN, and the UTRAN. RANAP is carried over Iu-interface.

An Access Point Name (APN) is the name of a gateway between a mobile network and another computer network, frequently the public Internet.

GPRS Tunnelling Protocol (GTP) is a group of IP-based communications protocols used to carry general packet radio service (GPRS) within GSM, UMTS, LTE and 5G NR radio networks. In 3GPP architectures, GTP and Proxy Mobile IPv6 based interfaces are specified on various interface points.

<span class="mw-page-title-main">E-UTRA</span> 3GPP interface

E-UTRA is the air interface of 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) upgrade path for mobile networks. It is an acronym for Evolved UMTS Terrestrial Radio Access, also known as the Evolved Universal Terrestrial Radio Access in early drafts of the 3GPP LTE specification. E-UTRAN is the combination of E-UTRA, user equipment (UE), and a Node B.

Packet Data Convergence Protocol (PDCP) is specified by 3GPP in TS 25.323 for UMTS, TS 36.323 for LTE and TS 38.323 for 5G. PDCP is located in the Radio Protocol Stack in the UMTS/LTE/5G air interface on top of the RLC layer.

The Radio Resource Control (RRC) protocol is used in UMTS, LTE and 5G on the Air interface. It is a layer 3 protocol used between UE and Base Station. This protocol is specified by 3GPP in TS 25.331 for UMTS, in TS 36.331 for LTE and in TS 38.331 for 5G New Radio. RRC messages are transported via the PDCP-Protocol.

The 3GPP/NGN IP Multimedia Subsystem (IMS) multimedia telephony service (MMTel) is a global standard based on the IMS, offering converged, fixed and mobile real-time multimedia communication using the media capabilities such as voice, real-time video, text, file transfer and sharing of pictures, audio and video clips. With MMTel, users have the capability to add and drop media during a session. You can start with chat, add voice, add another caller, add video, share media and transfer files, and drop any of these without losing or having to end the session. MMTel is one of the registered ICSI feature tags.

Proxy Mobile IPv6 is a network-based mobility management protocol standardized by IETF and is specified in RFC 5213. It is a protocol for building a common and access technology independent of mobile core networks, accommodating various access technologies such as WiMAX, 3GPP, 3GPP2 and WLAN based access architectures. Proxy Mobile IPv6 is the only network-based mobility management protocol standardized by IETF.

Access network discovery and selection function (ANDSF) is an entity within an evolved packet core (EPC) of the system architecture evolution (SAE) for 3GPP compliant mobile networks. The purpose of the ANDSF is to assist user equipment (UE) to discover non-3GPP access networks – such as Wi-Fi or WIMAX – that can be used for data communications in addition to 3GPP access networks and to provide the UE with rules policing the connection to these networks.

A Home eNodeB, or HeNB, is the 3GPP's term for an LTE femtocell or Small Cell.

eNodeB Mobile phone network element

E-UTRAN Node B, also known as Evolved Node B, is the element in E-UTRA of LTE that is the evolution of the element Node B in UTRA of UMTS. It is the hardware that is connected to the mobile phone network that communicates directly wirelessly with mobile handsets (UEs), like a base transceiver station (BTS) in GSM networks.

LTE-Sim is an open source framework to simulate LTE networks mainly developed by G. Piro and F. Capozzi at "Politecnico di Bari". The simulator was first presented by means of a scientific article.

QoS Class Identifier (QCI) is a mechanism used in 3GPP Long Term Evolution (LTE) networks to ensure carrier traffic is allocated appropriate Quality of Service (QoS). Different carrier traffic requires different QoS and therefore different QCI values. QCI value 9 is typically used for the default carrier of a UE/PDN for non privileged subscribers.

LTE-WLAN aggregation (LWA) is a technology defined by the 3GPP. In LWA, a mobile handset supporting both LTE and Wi-Fi may be configured by the network to utilize both links simultaneously. It provides an alternative method of using LTE in unlicensed spectrum, which unlike LAA/LTE-U can be deployed without hardware changes to the network infrastructure equipment and mobile devices, while providing similar performance to that of LAA. Unlike other methods of using LTE and WLAN simultaneously, LWA allows using both links for a single traffic flow and is generally more efficient, due to coordination at lower protocol stack layers.

Packet Forwarding Control Protocol (PFCP) is a 3GPP protocol used on the Sx/N4 interface between the control plane and the user plane function, specified in TS 29.244. It is one of the main protocols introduced in the 5G Next Generation Mobile Core Network, but also used in the 4G/LTE EPC to implement the Control and User Plane Separation (CUPS). PFCP and the associated interfaces seek to formalize the interactions between different types of functional elements used in the Mobile Core Networks as deployed by most operators providing 4G, as well as 5G, services to mobile subscribers. These 2 types of components are:

  1. The Control Plane (CP) functional elements, handling mostly signaling procedures
  2. The User-data Plane (UP) functional elements, handling mostly packet forwarding, based on rules set by the CP elements.

References