Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
8 Mai 2012 Dr. Ing. Titus Constantin Blan SIEMENS CMT titus.balan@siemens.com
3GPP releases
Next step for
GSM/WCDMA/HSPA and cdma2000
Specification:
IMS HSDPA UMTS Rel 99/4 2000 UMTS Rel 5 2003 MBMS WLAN IW HSUPA UMTS Rel 6 2005 IMS Evolution LTE Studies UMTS Rel 7 2007 LTE & EPC
year
3GPP started working on System Architecture Evolution (SAE) in the end of 2004 Feasibility of technical options was studied in 2005-2006 Actual standardisation started after the feasibility study in the beginning of 2007 Nowadays, the system is called Evolved Packet System (EPS) instead of SAE The PS core part is called Evolved Packet Core (EPC) LTE have been developed by the same standardization organization 3GPP. The target has been simple multimode implementation and backwards compatibility.
MME
IMS
HLR/HSS
Internet
Evolved Node B GateWay
Mbps
20
40
60
80
100
120
140
160
180
200 ms
GGSN MSC
Iu-CS
PGW
SGSN
Iu-PS S1-U
SGW
MME
S1-MME
RNC
Iub
Iur
NB
NB NB
eNB
X2
eNB
eNB
eUTRAN
eNB MME SGW PGW evolved NodeB Mobility Management Entity Serving Gateway PDN Gateway
UTRAN
MSC NB RNC SGSN GGSN
7
Mobile Switching Center NodeB Radio Network Controller Serving GPRS Support Node Gateway GPRS Support Node
2G
NodeB RNC
3G
SGi
LTE
eNodeB
S1-U S1-MME
Non 3GPP
S10
S6a
S2c
ePDG
S2b
SWx HSS
S2a
From IP point of view the LTE network can be split in three parts: Access Network and Transport Network Evolved Packet Core Applications
Mobility Management Entity It is a pure signaling entity inside the EPC; P-GW & S-GW selection SAE uses tracking areas to track the position of idle UEs. The basic principle is identical to location or routing areas from 2G/3G. MME handles attaches and detaches to the SAE system, as well as tracking area updates NAS signaling & security - The Non-Access Stratum (NAS) signaling terminates at the MME and it is also responsible for generation and allocation of temporary identities to UEs Interface towards the HSS which stores the subscription relevant information and the currently assigned MME in its permanent data base.
10
MME
Packet Data Network Gateway The PDN gateway provides the connection between EPC and a number of external data networks. PDN Gateway is comparable to GGSN in 2G/3G networks. Mobility anchor for mobility between 3GPP access systems and non-3GPP access systems. Policy Enforcement (PCEF) Per User based Packet Filtering (i.e. deep packet inspection) Charging & Lawful Interception support IP Address Allocation for UE Packet screening (firewall functionality)
SAE GW
11
Policy and Charging Rule Function The PCRF major functionality is the Quality of Service (QoS) coordination Home Subcriber Server Permanent and central subscriber database Stores mobility and service data for every subscriber Contains the Authentication Center (AuC) functionality.
HSS AAA PCRF
PDN
SAE GW
12
S6a: used by the MME to retrieve subscriber data from home subscriber server (HSS) S5: a signaling interface for establishing bearers between the serving gateway and the PDN gateway
or between serving gateways, for serving gateway change
Gx:
used by the PCRF to convey policy enforcement to the P-GW, and also used to retrieve traffic flow data. the interface into the IP PDN. This is where the IP visibility into the UE IP address(es) is exposed.
SGi:
S8: analogous to the S5 except that it is used in roaming scenarios. Rx: used by application functions, such as the IMS P-CSCF, to convey policy data to the PCRF.
13
14
LTE network design goals implies coexistence, interoperability, roaming, and handover between LTE and existing 2G/3G networks and services. The expected goal of service providers is to backhaul 2G/3G/LTE mobile traffic through a converged IP/MPLS core network for cost efficiency. Solutions used in the backhaul IP transport network layer (TNL) for 2G, 3G, and LTE should be similar to use and unify operational tasks such as provisioning, monitoring, and OAM procedures.
15
The eNB can be configured with separate IP addresses for User, Control, Management and Synchronization Plane applications. All applications can share the same IP address, the eNB features a single IP address.
In real world the preferred deployment is to separate management plane form other planes using L2 VLAN traffic separation.
16
IPsec Transport
17
LTE synchronization
2G/3G methods to synchronize the base stations clock reference provision by BSC/RNC over T1/E1 connections external source such as GPS LTE synchronization Timing-over-Packet is a solution based on IEEE 1588v2 Precision Time Protocol (PTP) Synchronization over Packet Network via Ethernet Interface, eliminates the need for TDM link or GPS
18
Microwave technology
19
Protocol Stacks
UE eNB PDCP GTP-U S-GW GTP-U UDP IP L2 L1
S1-U
GTP-U/GRE
PDN-GW
GTP-U/GRE
User Plane
UDP IP L2 L1
S5/S8
UDP IP L2 L1
L2
L1
UE
eNB NAS RRC PDCP RLC MAC S1AP SCTP IP L2 S1AP SCTP IP L2 L1
S1-MME
MME
GTP-Cv2
S-GW
P-GW
Control Plane
GTP-Cv2 PMIP
GTP-Cv2 PMIP
UDP IP L2 L1
S11
UDP IP L2 L1
S5/S8
UDP IP L2 L1
PHY
L1
20
LTE brings the incorporation of a flexible architecture The S1 Flex concept or MME Pooling provides network redundancy and traffic load sharing With S1 Flex the eNB is allowed to connect to a maximum of sixteen MMEs The operator can increase the overall network availability In practice geographical redundancy is desired, connecting each eNB to two MMEs, in different locations. The equivalent feature in 3G is Iu Multipoint of SGSN Pooling.
21
The MOCN enables the service providers to have separate core networks (MME, SGW, PDN GW) while the E-UTRAN (eNBs) is jointly shared by them.
This is enabled by the S1-flex mechanism by enabling each eNB to be connected to multiple core networks entities. Options to design the transport between eNB and core networks when MOCN is in use Shared Access & Aggregation Network, Separate IP Core Networks VLAN Based Traffic Differentiation for Network Separation
22
S6a interface
In 3G networks the Gr interface between SGSN and HLR is used to fetch the subscriber profile. Gr is based on E1 lines and SS7 protocols SIGTRAN (SS7 over IP) implementation brings IP on this interface.
In LTE the MME is using S6a interface, pure IP interface, with SCTP as transport protocol and Diameter as application protocol.
HSS is implemented using a frontend/backend architecture. The design of S6a interface is recommended to be done in such a way that MME maintains Diameter connections to several HSS-FE in parallel (pre-configured Primary and Secondary SCTP paths).
23
A fully meshed Diameter network is regarded as quite complex in administration and configuration To optimize the network architecture Diameter Relay Agents are introduced Diameter Relay Agent is used to forward protocol messages to appropriate Diameter Server. DRA plays similar role as STP in SS7 networks
24
Diameter Proxies
In roaming case the visited MME has to contact the home HSS in order to fetch the profile of the subscriber. S6a is pure IP interface with Diameter protocol at application layer Diameter Based Protocol defines the function of Proxying: The operator will use edge proxies to connect to GRX provider Edge Proxy Agent is the only point of contact into and out of an operator network at Diameter application layer Multiple edge-proxies are recommended for resilience and scalability.
A Diameter Proxy Agent has similar function as Diameter Relay Agent but it can modify the content of the message in order to address routing of diameter messages between different domains.
Diameter Proxy Agent can modify messages to enable policy enforcement, resource usage control, admission and provisioning, functions that cannot be done by Diameter Relay Agent.
25
The main change between 3G gateway (GGSN) and LTE gateway is that LTE gateway functionality is spilt in two elements: S-GW and P-GW.
The interface between S-GW and PGW is called S5 and has two variants: GTP and PMIP.
S5-PMIP interface CP is based on Proxy Mobile IPv6 and UP is based on GRE S5-GTP interface CP is based on GTPv2 and UP is based on GTPv1
26
Roaming in LTE
Roaming for home routed traffic is the similar scenario used at the moment in 3G data networks
Subscriber traffic is routed from Visited PLMN to Home PLMN via the GRX provider
The S8 interface is the reference point between visited S-GW and home P-GW S8-GTP is a natural choice for roaming as many operators are using GTP for roaming in 2G/3G
27
Connection to other PDN networks is managed trough different types of interfaces (S2a/b/c) that also imply different logic for IP address preservation in case of handover. Most frequent PMIP roles (depending on roaming scenario, roles can be changed):
S-GW takes the role of a Mobile Access Gateway (MAG), if PMIP-based S5 or S8 is used
PGW represents the Local Mobility Anchor (LMA) if PMIP-based S5 or S8, or if S2a or S2b is used
28
29
30
----------HSS/AAA | ----------| S6 |------------------------------| ----------| | | MME | | ---------------- S1 | ----------- S5 ----------- | SGi | UE |--+--| eNodeB |--+-|--| UPE |--+--|LTE Anchor|-|--+----------------| | (MAG) | | (LMA) | | | --------------------- | | <----------------> | | routing management by NETLMM | -------------------------------Evolved Packet Core |
31
Mobility Management
Mobility Management MME IDLE Mobility and Handovers S-GW LTE and 3GPP user plane mobility P-GW Mobility for non 3GPP interworking Mobility Management states EMM-DEREGISTERED - The UE is not reachable by a MME EMM-REGISTERED - The UE location is known and UE has at least one PDN connection ECM-IDLE - No NAS signaling connection between UE and network ECM-CONNECTED Signaling connection between the UE and the MME Mobility Management Procedures IDLE mobility TAU inside of LTE Handover X2 and S1 handover for different scenarios Intersystem Mobility For Idle mobility TAU/RAU
and for handover Relocation/PS handover
32
MME
Tracking area 1 Tracking area 2
33
GW for downlink S1 handover The S1-based handover procedure is used when the X2-based handover cannot be used. No X2 interface or MME change MME handle handover signalling and update S-GW Inter RAT handover Relocation used in UTRAN PS handover used in GERAN
Forwarding of Data
Downlink Data Uplink Data Path Switch Request UP Update Request UP Update Response Downlink Data End Marker Path Switch Ack Release Recourse HO Completion
Source
Target
MME
SAE GW
X2 HO as an example Procedure
34
Connection management GPRS attached PDP context Radio access bearer EMM registered EPS bearer Radio bearer + S1 bearer
Mobility management Location area Routing area Handovers (DCH) when RRC connected RNC hides mobility from core network
35
Not relevant (no CS core) Tracking area Handovers when RRC connected Core network sees every handover
Voice solutions
IMS provides: service info via Rx interface SIP session control for VoIP Voice application server (CS compatible) QoS and policy control (Gx, Rx interface) VoIP emergency call Gm over Gi (SIP) for voice data transfer Voice solutions over EPS: IMS based VoIP Single Radio Voice Call Continuity (SRVCC) Circuit Switched Fallback (CSFB) NVS VoIP over EPS
36
EPC
PCRF MME Gx+ Rx+
IMS
S1-MME S11
Gateway Serving PDN
LTE
S1-U
Operator Services
SGi
37
Auto-configurare : integrarea automat n reea a noilor staii de baz LTE cu ajutorul procedurilor de auto-conectare i auto-configurare Auto-optimizare : reglarea parametrilor reelei pentru funcionare optim cu ajutorul msurtorilor Auto-vindecare : detecie automat, localizarea i eliminarea erorilor Auto-planificare : recalcularea dinamic a planului de reea
38
Procedura de autoconfigurare Relaii de vecintate automate procedura ANR Economisirea energiei Optimizarea acoperirii si a capacitatii Adaptarea schemelor multi-anten (SIMO, MIMO) Optimizarea robust a mobilitii (Mobility Robust Optimization) Optimizarea distribuiei sarcinilor la mobilitate
39
Examples of virtualization of telecom elements: Nokia Siemens Networks Open Core System concept Virtualization achieves extreme flexibility and efficiency in open core networks Open Core software application runs on legacy equipment, on the latest state-of-the-art Commercial off-the-shelf ATCA platforms and on other generic multi-purpose hardware. Alcatel Lucent CloudBand concept Using CloudBand, service providers can virtualize many of the critical elements of their networks by converting them into software which is run in the cloud and accessed on demand Ericsson Network-enabled Cloud concept The Network-Enabled Cloud builds on computing power in today's telecom assets to both embed enhanced functionality and to expose network capabilities for new service creation
40
References
http://www.3gpp.org/specs/numbering.htm http://www.3gpp.org/ftp/Specs/html-info/23401.htm http://www.3gpp.org/ftp/Specs/html-info/23402.htm http://www.3gpp.org/ftp/Specs/html-info/23060.htm
41