ZTE Evolved Packet Core
ZTE Evolved Packet Core
ZTE Evolved Packet Core
Agenda
Key Note # 1. We analyze that users want: Rich Experience Multi-media Services Geographical Mobility Higher data rates (BB) Always Connected Less Haste with Unified Billing One Device Smart Phone H2M friendly environment
Source: Company reports from Vodafone, Telstra, Verizon and AT&T. Qualcomm
LTE
HSPA+ HSPA HSDPA EDGE/R4 GSM/GPRS 16K~144K (bps) 1999-2002 UL: 384K DL:384K (bps) 2003-2005 2006-2007 UL:384K DL:2.8M (bps) 2008-2009 UL:2.2M DL:.19.8M (bps) UL:10M DL:40M (bps) DL:100M UL:50M (bps)
Content
Apps
Devices
2009-2010
>2010
Agenda
HSS S6a
S1-MME
S1-U
LTE/ENodeB
LTE/ENodeB
Compatible
2200
Capacity
Signaling
2Mbps links Signaling points FE interface GE interface E1/T1 interface (Frame Relay) STM interface
Interface
600X 800
ZXUN uMAC
60000 160Gbps
60000
54Mpps
4096
Performance
2200600800(mm)
< 5736W (36W/Gpbs) -48 V DC (-57 -40V) 210 kg (437kg/m2)
uMACMME
xGW(SAE-GW)
Capacity:
LTE: 15M SAU
Capacity:
160G bps 24M PDP
Power Consuming:
420W/M PDP
Power Consuming:
36 W/G bps
Footprint:
3 Shelves
Footprint:
1 Shelves
Flatter Architecture
GGSN
GGSN
GGSN/ SAE-GW
SGSN SGSN
SGSN /MME
RNC
RNC
RNC
RNC
eNodeB
NodeB
Step 1 DT is introduced in PCN: SGSN is in charge of signaling processing only, packets are transferred from RNC to GGSN directly. Step 2 Flatter architecture in RAN: RNC and NodeB is integrated to eNodeB for LTE and HSPA+
Full service
-All service, including voice
- Broadband internet access data only - Rapid provision of DSL type services -Data card/PC - No need for2/3G inter-working -Static, in door - Network size dependant on market,
Hot Spot
Metro
Urban
Challenges on Evolution
Phase
Phase-1 How to introduce EPC for LTE
Phase-2 EPC deployed for broadband data service Phase-3 Full service operation in LTE
Challenges
Migration from legacy CN or built new EPC? Key technology deployed at initial stage
LTE 3G 2G
To pure EPS
No
Yes
No
Yes
SRVCC
CS Fall Back
Dump CS
Dump CS Ready to dump CS Another migration opportunities for vendors. Handsets can not be changed over night. Overlay of various technologies are required
SGSN GGSN
Main Consideration for Evolution 1 provision of LTE service 2 Less impact on existing service 3 simplify the network
2G/3G EUTRAN
GERAN /UTRAN
IP
ATM/ TDM
IP
SGSN
4 Lower TCO
2/3G
Legacy GSN should support LTE access Legacy GSN should provide huge capacity for LTE Legacy GSN should support the all IP networking Lower CAPEX at initial stage Higher OPEX, because of GSN s lower capacity and integration Upgrading from GSN may impact the legacy network
EPC has the Huge capacity for LTE access EPC should support All IP networking EPC should support 2/3G access Higher CAPEX at initial stage Lower OPEX, because of huge capacity and higher integration Built new EPC has no impact on the legacy network
INTRENET
CSCF
SGs
MME
SAE-GW MGW
MSCS
CS
Sv
MGW
MME
SAE-GW
CS
SGs
MGW MGW
EPC
EPC
RAN/GERAN
eNodeB
RAN/GERAN
eNodeB
handover
PSTN/PLMN
MGCF
SCC AS
IMS
CSCF
INTRENET
HSS
MGW
MSCS
MME SGs
SAE-PGW
MGW
MSCS
MME
SAE-PGW
CS
EPC
CS
Sv
EPC
RAN/GERAN
eNodeB
RAN/GERAN
eNodeB
CS fallback
1
CS Fallback
SRVCC
2
SRVCC
ITEM
Need IMS UE
No, service is controlled by MSC 1) Support EPS/IMSI Combined procedures 2) CS fallback and SMS procedures. 1) Upgrade MSCs overlapped by LTE coverage to support SGs; 2) Upgrade MME to support SGs Software upgrade
Yes, service is controlled by IMS Need to support SRVCC Capability 1) IMS system deployed for UTRAN/ GERAN reuses the session transfer function defined for IMS; 2) Upgrade MME to support Sv; 3) Upgrade MSC to support Sv IMS client Installation
CS
EPC
MME UE CS UE
UE need to support LTE access. User feeling is same as CS domain short message. MME and MSCS support SGs association, SMS message transfer on SGs. No special requirement to other nodes MSCS for SMS over SGs can be newly deployed to avoid existing MSC update.
SMS over IP
IP-SM-GW
MAP
SMSC
IM AS
ISC MAP/Diameter
CS
MSC
IMS
CS UE
UE need to support IMS instant message service and user can send multiple content as text, picture, flash or other document. Normally IMS instant message is integrated with buddy list and their presence state to promote good user feeling. A new node named IP-SM-GW is need to deployed for SMS interworking with CS domain. IP-SM-GW supports message domain selection, message format transformation and large message fragment. No special requirement to other network node.
SRVCC
Vodafone, Verizon
CS fallback
NTT, DOCOMO, KDDI,AT&T, Rogers, Teliasonera
Vendors
Terminals
1
UTRAN/GERAN UTRAN/GERAN
2
CS Domain
CS Domain
E-MSC Server SV EUTRAN EPS Domain MME IMS Domain VCC Server EUTRAN SV
E-MSC Server
IMS Domain VCC Server EPS Domain
MME
Phase 1: CS FALLBACK is introduced, voice service falls back to legacy CS domain Phase 2: IMS based VoIP Phase 3: SRVCC is introducedsingle direction LTE to CS Voice continuity is supported Phase 4: Bi-directional SRVCC handover is provided for Voice continuity
3G
LTE No 2G No 3G
Unified Packet Core L T E L T E L T E L T E L T E L T E
Unified Packet Core U L G U U G Same Hardware For Multiple RATS L T U L L U E Dynamically Configured By Software EPC
CS/HLR
PS
CS/IMS/HSS
IMS/USPP
EPC
Iu
S1
Iu
S1
S1
Hot Spot
indoor
Metro
outdoor
Urban
indoor
Software Defined Resource for CS, PS & IMS CS & NG-HLR realize smooth upgrade xGW supports SGW/PGW, GGSN & non-3GPP access
Dynamic Capacity Transfer by Software Hardware fully shared & reused during the migration Realize Fully Convergent Core Nodes for Voice & Data
Agenda
Thanks!