Targets
Familiar with EPC basic theory Familiar with EPC system structure and interface Know EPC interface protocol stack Know key technologies of EPC network
1-2
Contents
LTE/EPC Evolution EPC Network Structure EPC Interfaces and protocol stack EPC Key Technologies ZTE Solution and product
1-3
HSPA+
DL >40Mbps UL >10Mbps
LTE
DL:100Mbps UL:50Mbps
HSUPA
2M/5.76Mbps
1xEV-D0 Rev. A
DL: 3.1Mbps UL: 1.8Mbps
DO Rev. B
(MC DO) DL46.5Mbps UL: 27Mbps
IMT -Advance
4G
IEEE802.16m DL:100Mbps UL: 50Mbps
WiMAX Evolution
IEEE802.16d 20Mbps IEEE802.16e 70Mbps
2001-2005
2006
2007
2008
2009
2010
2011
Bandwidth in wireless network is increasing 10k100k1M10M100M The increasing in system capacity and frequency spectrum decreases the bearer cost of packet service every bit Many kinds of wireless technology co-exists at the same time
1-4
EPC Architecture
1 Flat Core Network 2 Control and bearer separation 3 ALL IP bearer
ATM /TDM
GGSN
SAE-GW MME
eUTRAN
I P
ATM/ TDM
UTRAN
I P
SGSN
I P
SAE-GW LTE/EPC
Unified IP bearer mode Unified flat network Unified control and bearer separation
GSM
Non-3GPP
TDSCDMA LTE
1-5
Flatter Architecture
GGSN GGSN GGSN/ SAE-GW
SGSN SGSN
SGSN /MME
RNC
RNC RNC
RNC
eNodeB
Step 1 DTS is introduced in PCN: SGSN is in charge of signaling processing only, packets are transferred from GGSN to RNC directly. Step 2 Flatter architecture in RAN: RNC and NodeB is integrated to eNodeB for LTE and HSPA+
1-6
Service Continuity
SAE GW
Control Plane
CDMA
User Plane
Core network should support multiple access technology. Core network should support seamless mobility and service continuity across RATs. Core network should bridge the current to the future.
1-7
WiFi
WiMax
NodeB/BTS
AGW
PDSN
GGSN
VOD
WAP LCS
SAE-GW
MBMS
Content usage collection and enforcement Popular application Popular content User profiling
Content based and comprehensive billing L3 or L4 billing URL billing event billing
1-8
IMS
Core Network
Circuit Core
2G
3G
LTE
Non-3GPP
To pure EPS
1-9
1
Feasibility study 2004.12~2006.6 network structure optimization feasibility study Export these protocols:
TR 23.882: "3GPP system architecture evolution (SAE): Report on technical options and conclusions"
2
Stage1 (requirement phase) Define SAE requirement. Finish at 2006.12 Export these protocols: 3GPP TS 22.278: "Service requirements for evolution of the system architecture:"
3
Stage2 (technique implementation Define SAE network structure, functional entity and interfaces. Finish at 2008. 6 Export these protocols
3GPP TS 23.401: "General Packet Radio Service (GPRS) enhancements for Long Term Evolution (LTE) access 3GPP TS 23.402: "3GPP System Architecture Evolution (SAE): Architecture enhancements for non-3GPP accesses"
4
Stage3 (protocol implementation) Define interface protocols. Finish at 2009.3 Current protocols are
3GPP TR 24.801: "3GPP System Architecture Evolution (SAE); CT WG1 aspects" 3GPP TR 29.803: "3GPP System Architecture Evolution (SAE): CT WG4 aspects" 3GPP TR 29.804: "3GPP System Architecture Evolution (SAE): CT WG3 aspects"
1-10
Members
PCG
1-11
Rel-8 Mar 09
Rel-10 Mar 11
LTE/LTE-A Mbps
DL
UL
160
50
1000
500
Main Function
BICC, TDSCDMA
HSDPA, IMS
LTE-Adv
1-12
EPC Features(1)
EPS provide access for various system Support roaming between different systems and within the same system Support IP based broadband access network beside 3GPP Higher performance including low latency, low link establish time and high quality Support roaming between EPS and between EPS and existing network Support 3GPP R7 and earlier PS network service, support communication between EPC and 3GPP R7 and earlier CS network
1-13
EPC Features(2)
Support service continuity between different 3GPP access network, and between 3GPP and non3GPP system Support interconnection between fixed access system and support service continuity Support various service provided by operators such as voice ,video, message and file transfer Fully usage of system resources including frequency, terminal and power supply etc
1-14
Contents
LTE/EPC Evolution EPC Network Structure EPC Interfaces and protocol stack EPC Key Technologies ZTE Solution and product
1-15
Term Explanation
EPS EPC EUTRAN SAE LTE
Evolved Packet Core, refers to core network Evolved Universal Terrestrial Radio Access Network, refers to wireless network System Architecture Evolution=EPC, refers to core network Long Term Evolution=EUTRAN, only refers to wireless network
1-16
EPC Network
1-17
TS 23.401 Non-roaming
UTRAN SGSN GERAN S3 S1 - MME MME PCRF S12 S11 S4 " LTE - Uu " S10 Serving S5 PDN Gateway SGi Operator ' s IP Services (e.g. IMS, PSS etc.) S7 Rx+ S6a HSS
UE
E - UTRAN S1 - U
Gateway
all IP structure flat network structure media and control plane separated interconnection with existing network 1-18
1-19
Serving GW
PDN GW
Filtering based on user Lawful monitoring IP address assignment UL/DL transport layer data labeling PCC non-GBR DL rate control based on AMBR GBR DL rate control based on MBR DHCPv4 and DHCPv6client server DL/UL Bearer binding UL bearer binding check
Anchor point for hand off process between NAS signaling processing eNodeB NAS signaling security E-UTRAN data cache protection under idle mode and Mobility management triggering of network between different 3GPP side Service Request nodes process Tracing and reaching of Lawful monitoring idle mobile terminal Packets routing and TA List management forwarding Selection of PDN GW and UL/DL transport layer Serving GW data labeling Selection of MME and Statistics based on SGSN user and QCI (used for Lawful monitoring billing between Roaming control operators) Security authentication DL/UL billing based on Bearer management user, PDN and QCI Similar to control plane of SGSN Similar to user plane of SGSN
Similar to GGSN
1-20
VPLMN
S8
1-21
H-PCRF
Rx
S9
SGSN
S3 S4 S12 Gx S11
V-PCRF
MME
S10
"LTE-Uu"
UE
E-UTRAN
S1- U
Serving Gateway
S5
1-22
SWa
STa
PGW support S2a/S2b interface to implement non-3GPP access S2a support access from trusted non-3GPP, S2b support access from untrusted non-3GPP network S2a is based on PMIP and MIPv4, S2b is based on PMIPv6
1-23
S6b Gxb SWm ePDG HPLMN Non-3GPP Networks SWn Gxa Trusted Non3GPP IP Access S2c S2c Untrusted Non -3GPP IP Access 3GPP AAA Server
SWa
STa
UE
S2c
PGW support S2c interface for the access of non-3GPP network S2c is the interface between UE and PGW, UE can get accessed from any network, no need to add new function on roaming network S2c is based on DSMIPv6 protocol
1-24
Contents
LTE/EPC Evolution EPC Network Structure EPC Interfaces and protocol stack EPC Key Technologies ZTE Solution and product
1-25
protocol
S1AP GTPv1 GTPv2 GTPv2 GTPv2 Diameter GTPv2 GTPv1 PMIPv6/MIPv4 GTPv2
Protocol number
36.413 29.060 29.274 29.274 29.274 29.272 29.274 29.060 RFC5213 29.274
Related NE
eNodeB - MME eNodeB S-GW MME S-GW MME SGSN S-GW SGSN MME - HSS MME - MME S-GW UTRAN P-GW Trusted Non3GPP IP Accesse S-GW P-GW
Interface Function
SM and MM info transfer Tunnel established between GW and eNodeB to transfer data GTP adopted to establish tunnel between MME and GW to transfer signal GTP adopted to establish tunnel between MME and SGSN to transfer signal GTP adopted to establish tunnel between S-GW and SGSN to transfer data and signal User location information switching and user profile information management GTP adopted to establish tunnel between MME to transfer signal Establish tunnel between UTRAN and GW to transfer data Transfer non-3GPP service data GTP adopted to establish tunnel between GW to transfer data
1-26
GTP-C UDP IP L2 L1
Diameter SCTP IP L2 L1
MME
MME
HSS
1-27
Contents
LTE/EPC Evolution EPC Network Structure EPC Interfaces and protocol stack EPC Key Technologies ZTE Solution and product
1-28
TA List1
MME
TA 2 TA 4
TA 3 TA 1
TA 5
The Tracking Area Identity is constructed from the MCC (Mobile Country Code), MNC (Mobile Network Code) and TAC (Tracking Area Code).
Idea of TA List
All the tracking areas in a Tracking Area List to which a UE is registered are served by the same serving MME.
The MME may initiate the GUTI Reallocation procedure to reallocate TAI list at any time when a signaling association is established between UE and MME. The TAI list may also be reallocated by the Attach or the Tracking Area Update procedures The UE doesnt need trigger TA update procedure when the UE moves in the same TA List. 1-29
TA2
ISR
RA1
Combined area
RA3
RA2
RA4
ISR is not recommended to deploy in commercial phase because of its complexity and less benefits. 1-30
UE doesnt need trigger TA update procedure when it moves in the combined area.
Terminal
SGSN/MME
MME/SGSN send request to PGW to identify Dual Stack Flag on following conditions
PDN-GW
Bearer Type is decided by terminal capabilities IPv6 and IPv4 supported terminal ask for IPv4v6 IPv4 supported terminal ask for IPv4 IPv6 supported terminal ask for IPv6
PGW check the following conditions to judge if Dual Stack request can be accepted If this APN is not allowed to use two IP addresses, then only one IP address is assigned and return network preference to UE If this APN is allowed to use two IP addresses then assign IPv4 address and IPv6 address and accept the request
if UE signed Dual Stack return deny, otherwise return subscription limitation to UE whether UE can switch to network not support IPv4v6, if yes return single address bearers only to UE
1-31
eNB Xu UE Xu
Security layer 1
S 1- C S 1 -U S 1- C S 1 -U
MME SAE GW
Evolved Packet Core ( EPC )
X2
eNB E - UTRAN
EPS access authentication: AKA EPS security layers ASAccess Stratum security Security between UE and eNB E-UTRAN, including RRC signaling confidentiality, RRC signaling integrity and UP (User Plane) confidentiality NAS Non Access Stratumsecurity Security between UE and MME, including NAS signaling confidentiality and NAS signaling integrity Network Domain Security Security between layer 1 and layer 2, adopting NDS/IPsec
SNOW3G AES ZTE support the above algorithms according to 3GPP 33series.
1-32
Advantage
Less modification to legacy GPRS network Not much modification to legacy 2/3G user service flow and feeling to the service Network structure is simple
Disadvanta ge
GnGp SGSN can not get user attribute and is unable to select GGSN and PGW Two sets of contracted data management: HLR and HSS Support of Pre-R8 DNS(GPRS DNS) and R8 DNS(EPC DNS) is needed Support of GPRS and EPC billing is needed ISR is not supported, it is implemented between S3/S4 SGSN and MME Not good for the extension of following new functions Problem in communication with non 3GPP network: the basic requirement in communication with non 3GPP network is PGW address should be anchored for non optimization switching, but the anchoring of PGW address is reached by inform HSS , but because Gn/Gp SGSN use HLR , it is impossible to inform HSS and save PGW in HSS
More modification to legacy GPRS network, it is required to upgrade the Pre-R8 SGSN to S3/S4 SGSN Network is complicated due to the introducing of S3/S4 SGSN especially because the communication with legacy GPRS network. Service flow and feeling for old 2/3G user is changed Service flow for 2/3G access is changed compared to legacy service flow in these two points:
It is requested that UE support network side initiation process, the initiation process is changed from UE initiate to network side initiate process; QoS negotiation is canceled, if wireless network can not meet the QoS requirement bearer will be deleted directly
Conclusion
1-33
Service Continuity
Iu-PS
SGi S12 S1-U S3 S-GW S10 S5/S8 P-GW Internet& Sevice network
LTE
S1-MME MME
EPC
1-34
Service Continuity
Gn/Gp Gn/Gp Iu-PS UTRAN S12 S-GW S1-U LTE MME S1-MME S10 S5/S8
S6a
SGi P-GW
EPC
Via S4 SGSN
To support GERAN/UTRAN handover from GERAN/UTRAN to LTE, the SGSN must be upgraded to R8 LTE to GERAN/UTRAN supported on pre R8 SGSN Does not support of R8 feature ISR Many protocols: GTPv0, V1 and V2, Diameter, MAP 1-35
Need upgrading on SGSN Support of R8 feature as ISR Fewer protocols in the network: GTPv2, Diameter
Stock
Traffic Class ARPGBRMBR Traffic Handling Priority Signalling Indication Source Statistics Descriptor Packet Delay Budget Packet Loss Rate
GERAN/UTRAN
EUTRAN
Principle for QoS parameters mapping according 23.401 Mapping of Bearer context, ARP, GBR,MBR is 1 by 1 Mapping of QCI to Traffic Class, Traffic Handling Priority, Signaling Indication, and Source Statistics Descriptor based on configuration and operators requirements More flexible mapping control could be supported Based on APN, subscriber type, IMSI mask
1-36
Resource Type
GBR
Priority
2 4 3 5 1 6
Example Services
Conversational Voice Conversational Video (Live Streaming) Real Time Gaming Non-Conversational Video (Buffered Streaming) IMS Signalling Video (Buffered Streaming) TCP-based (e.g., www, e-mail, chat, ftp, p2p file sharing, progressive video, etc.) Voice, Video (Live Streaming) Interactive Gaming Video (Buffered Streaming) TCP-based (e.g., www, e-mail, chat, ftp, p2p file sharing, progressive video, etc.)
100 ms
10-3
8 9
8 9
300 ms
10-6
This QCI is typically associated with an operator controlled service, i.e., a service where the SDF aggregate's uplink / downlink packet filters are known at the point in time when the SDF aggregate is authorized.
1-37
INTRENET
HSS
HSS
MGW
MSCS
MME SGs
SAE-PGW
MGW
MSCS
MME Sv
SAE-PGW
CS
EPC
CS
EPC
RAN/GERAN
eNodeB
RAN/GERAN
eNodeB
CS fallback
IMS+SRVCC
Voice over 2/3G, data over LTE/EPC in LTE area Upgrade on MSC/MSCS Overlapped coverage of 2/3G and LTE No IMS Defined in 3GPP R8
All service over LTE/EPC in LTE area IMS needed Upgrade on MSC/MSCS Defined in 3GPP R8 (LTE->CS only)
1-38
4 Handover
GERAN Voice Service Continuity IMS Domain UTRAN MME SV EPS Domain
GTP UDP IP L2 L1
SAE-GW
GTP UDP IP L2 L1
MME
Sv
MSC Server
EUTRAN Voice service continuity initiated by PS handoverMSC-MSC handover and domain switch 2G/3G and E-UTRAN overlap in border area SV interface between MME and enhanced MSC develop based on S3 interface
Related NE modification
MSC
Support handover request sent from MME, and initiate CS bearer establishment and domain switch process Support IMS to CS domain switch explained in TS23.237 Can negotiate CS handover and domain switch Initiate MAP location update process on behalf of UE Divide voice and non-voice from PS bearer, for voice bearer initiate SRVCC handover, for non-voice initiate PS handover Negotiate PS handover and SRVCC handover Insert SRVCC VDN to MME during UE attach flow Need to inform network whether SRVCC is supported or not
1-40
HSS
UE
SGsAP
GERAN
E-MSC Server
SGsAP SCTP IP L2 L1
SCTP IP
UTRAN
SGs
EPS Domain
L2 L1
MME EUTRAN
MME
SGs
MSC Server
Voice service implemented by using CS lower layer architecture 2G/3G full coverage, that is E-UTRAN coverate area already covered by 2G/3G SGs interface supporting SGsAP based on SCTP developed upon Gs interface SMS service handled specially, NAS message forwarded by EPSamong which SMS related message encapsulatedimplement SMS communication between MSC and UE
1-41
Related NE modification
UE
EPS/CS mobility management SMS special handling SMS special handling SGs interface protocol stack SGs interface special handling SMS special handling
MSC
MME
E-UTRAN
Contents
LTE/EPC Evolution EPC Network Structure EPC Interfaces and protocol stack EPC Key Technologies ZTE Solution and product
1-43
Features
6 unification
ZEPS
HLR/HSS/AAA/SPR
Service Platform
PCRF
Unified user data management Unified service control and billing policy Unified network management Unified mobility management node --- uMAC Unified gateway -- xGW Unified access network SDR merged network Support multiple network access, including mobile and fixed network access Flat structure Control and beaer seperation
uMAC
SGSN
GGSN
HA
SAE-GW
MME
AC/SR/BRAS
AGW
ePDG
LTE
UTRAN/GERAN
WiMax / WiFi
xDSL/xPON
support at most 5000,000 user 99.999% reliability, complete redundancy backup mechanism high density processor, powerful service processing capability
New generation of high end SR platform 1.92T switching capacity, 64.8Mpps packer forwarding speed, 160G throughput Support 10GE interface, at most 40G by cascade Hardware QoS, support HQoS, support Qos management for single user per service 99.999% reliability, complete redundancy backup mechanism Powerful RoHC, DPI capability Embedded Firewall, complete security mechanism
AGW HA
1-45
1-46
Build-in Firewall
Dedicated
ZXUN xGW
real time backup on subscriber data in service module. 1+1 backup for FW module
Site A
xGW1
Heart beat
Data synch
FW FW FW
Site B
Geographical
xGW2
backup on subscriber data, guarantee the session wont be disconnected. No extra support from other NE.
1-47
High Integration
80 60 40 20
63 52 60 41
ZTE
Service Board
Smart Power Control of Service Board Switch off un-used service boards in free time Switch off unused CPU within
service board
Smart Power Control of Switch Board Power on/off control on switch board according to traffic load
1-48
UBAS
Analyze
PCC
Control
UBAS
Report
Broadband Access
Content-based charging Bandwidth Management Subscriber Behavior Awareness Access Control Service Awareness Routing Management
Internet
P2P Upload P2P Download VoIP WebTV Video Conferencing Gaming email
1-49
ETCA is the new generation unified all IP platform that designed for ZTE control and service layer products.
RCP (RACS/PCC
HSS/AAA/SPR
uMAC
Open and standard architecture: Comply with PICMG3.0 R2.0 and IPMI 1.5 Good expansibility: Support performance expansion, memory expansion and I/O expansion High availability: Redundancy mechanism, fault tolerance function and trouble management function Efficiency, lower TCO: Energy saving, highly integrated design, board reuse, protect investment Easy maintenance: IPMI intelligent management platform, which provide equipment management, resource sharing, remote maintenance, system information backup, software online upgrade
1-50
CSCF P-CSCF
AS SIP P-CSCF Gq
Session control plane Resource Authorization Request Resource control plane ZXUN RCP Gx(x) Service Resource QoS Control ZXUN RCP Ia Re
Rx
PS-GW
SR
Mobile access
Fixed access
Special policy control equipment (ZXUN RCP) is introduced to guarantee IMS service QoS 1-51
AF
Reporting-Level
Online Offline Metering-Method AF-Charging-Identifier
SPR
ZXUN RCP
OCS/OFCS
Charging correlation for both control plane and media plane to avoid repeated charging
Service flow based charging, which ensures more flexible and accurate charging.
1-52
AF
Binding-Information
IP NAPT (IP_termination)
CLF
ZXUN RCP
Internet
DSLAM
BGF
BRAS
Policy System
DPI
DPI
DPI
Internet Voice
DPI
DPI
Terminate
Transform from pipe provider to service based subdivided operation Network resource utilization optimization
1-54
AF
VoIP/Centrex
IM
PS Core
OFCS
OCS
ZXUN RCP &ZXUN SPR were deployed on the existing PS network to implement the subdivided operation and management 3.5M subscribers supported Include both prepaid and postpaid subscribers Phase 1 was already commercially launched 1-55
AF
VoIP/Centrex
IM
PS Core
OFCS
OCS
A database to store PS domain profile policies Providing PCRF with subscriber profile policy information Providing profile policy query Providing profile policy notification Providing dynamic-usage access and update Providing operators with a service handling interface 1-56