Network Basic Principle

EP_BT001_E1_1 EPC Network Basic Principle

1-2

Targets

Upon completing the course, you will be able to: Familiar with EPC basic theory Familiar with EPC system structure and interface Know EPC interface protocol stack Know key technologies of EPC network

1-3

Contents

LTE/EPC Evolution EPC Network Structure EPC Interfaces and protocol stack EPC Key Technologies ZTE Solution and product

EPC Network Basic Principle

1-4

Broadband Trend in Wireless Technology

Bandwidth in wireless network is increasing 10k→100k→1M→10M→100M 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

IMT-Advance

4G

CDMA2000 Evolution

2001-2005 2006

HSDPA Phase I

1.8M/3.6Mbps

HSDPA Phase II7.2/14.4Mbps

HSUPA2M/5.76Mbps

LTE

DL:100MbpsUL:50Mbps

GSM/GPRSEDGE

171/384kbps

WCDMAR99/R4

384kbps

WCDMA Evolution

2007 2008 2009

HSPA+DL >40MbpsUL >10Mbps

1xEV-DO Rev. 0DL: 2.4MbpsUL:153.6kbps

DO Rev. B(MC DO)

DL ： 46.5MbpsUL: 27Mbps

1xEV-D0 Rev. ADL: 3.1MbpsUL: 1.8Mbps

CDMA 1X153kbps

2010 2011

IEEE802.16e70Mbps

IEEE802.16mDL:100MbpsUL: 50Mbps

WiMAX Evolution

IEEE802.16d20Mbps


1-5

Unified Packet Core Network Structure

1 Two level architecture of user

plane

2 control plane and user plane

together

3 TDM /ATM adopted

2/3G Core Network

1 Flat core network

2 control and bearer separated

partially

3 ALL IP bearer

3G DTS Mode Core Network

1 Flat Core Network

2 Control and bearer separation

3 ALL IP bearer

EPC Architecture

SGSN

GGSN

SGSN

2/3G

GERAN/UTRAN

ATM/TDM

ATM/TDM

IP

IP

GGSN

SGSN

GGSN

3G-DTS

IP

IP

UTRAN

SAE-GW

MME

SAE-GW

LTE/EPC

IP

IP

Unified Core NetworkUnified Core Network

Unified IP bearer modeUnified IP bearer mode

Unified control and bearer separationUnified control and bearer separation

Unified flat networkUnified flat network

GSMGSMTDSCDMATDSCDMA

Non-3GPPNon-3GPPLTELTE

eUTRAN


1-6

Flatter Architecture

SGSN

GGSN

RNC RNC

NodeBNodeB NodeB

NodeB

RNCRNC

SGSN

GGSN

SGSN/MME

GGSN/SAE-GW

eNodeB

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+

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

MMESAE GW

Internet&Sevice network

HLR/HSS/AAA

Control Plane

User Plane

DHCP

NTP

DNS

Support network

WimaxSAE GW = Serving GW+PDN GW

LTE

GSM

SGSNGGSN

AGW

CDMA

PDSN

WCDMA

Se

rvic

e C

on

tinu

ity

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.

Unified Core Network For Multi-RATs


1-8

WiFiWiFi

WiMaxWiMax

NodeB/BTSNodeB/BTS

CDMA1X

EVDO

GPRS

EDGE

UMTS

HSPA

WiMax

WiFi

LTE

Streaming

Message

Internet

VPN

VOD

WAP

LCS

MBMSSAE-GWSAE-GW

Subscriber Control Event measurement Balance enforcement Purchase acknowledgement Account replenishment

Service Differentiation Premium Service Service authorization Filtering

Content usage collectionand enforcement Popular application Popular content User profiling

Content based and comprehensive billing L3 or L4 billing URL billing event billing

GGSNGGSNPDSNPDSN

AGWAGW

Intelligent Data Service Awareness


1-9

IMS

Circuit Core Legacy Packet Core

Evolved Packet Core

Core Network

2G

Phase Out over timeLTE Non-3GPP

Voice Service Network (PSTN etc.)

Voice Service Network (PSTN etc.)

Packet Service Network (Internet, Operator data

service)

Service Network

3G

To pure EPS

LTE

3G

2G

Smooth Evolution of Mobile Network


1-10

1Feasibility study2004.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"

2Stage1 (requirement phase)Define SAE requirement. Finish at 2006.12Export these protocols: 3GPP TS 22.278: "Service requirements for evolution of the system architecture:"

3Stage2 (technique implementation ）Define SAE network structure, functional entity and interfaces. Finish at 2008. 6Export 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"

4Stage3 (protocol implementation)Define interface protocols. Finish at 2009.3Current 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"

EPC standard Evolution


1-11

Organizations Leading in LTE/EPC Ecosystem

Functional Requirements

Standards Establishment

LTE/SAE Trial Initiative

TSG RAN

TSG SA

TSG CT

PCG

TSG GERAN

Members

Sponsors


1-12

3GPP Versions Released Records

* HSPA+ = 42 Mbps @ 64QAM + MIMO, 82 Mbps @ DC-HSDPA

LTE-Adv

LTE/SAE Enhance,

LTE-Adv Feasibility Study

HSPA+ Phase II, LTE/SAE

HSPA+ Phase I,

LTE/SAE Feasibility

HSUPA,MBMS,

WiLAN-UMTS IWK

HSDPA,

IMS

BICC, TD-SCDMA

CS & PS, R99 Radio Bearers

Main Function

50050UL

1000160　

DLLTE/LTE-A

Mbps

11 or 2211.525.760.3840.3840.384UL

42 or 82*28.814.414.40.3840.384DLWCDMA

Mbps

Mar 11Mar 10Mar 09Dec 07Mar 05Mar 02Mar 01Dec 99Frozen Time

Rel-10Rel-9Rel-8Rel-7Rel-6Rel-5Rel-4R993GPP


1-13

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-14

EPC Features(2)

Support service continuity between different 3GPP access network, and between 3GPP and non-3GPP 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-15

Contents



1-16

Term Explanation

EUTRAN Evolved Universal Terrestrial Radio Access Network,

refers to wireless network

EPC Evolved Packet Core, refers to core network

EPS

LTE Long Term Evolution=EUTRAN, only refers to wireless

network

SAE System Architecture Evolution=EPC, refers to core

network


1-17

EPC Network


1-18

all IP structure flat network structure media and control plane separated interconnection with existing network

SGi

S12

S3

S1 - MME

PCRF

S7

S6a

HSS

Operator 's IP Services

(e.g. IMS, PSS etc.)

Rx+

S10

UE

SGSN

" LTE - Uu "

E - UTRAN

MME

S11

S5 Serving

Gateway

PDN

Gateway

S1 - U

S4

UTRAN

GERAN

EPS interconnecting with S4 SGSN network －－3GPP non-roaming scenario TS 23.401 Non-roaming


1-19

EPS interconnection with Gn/Gp GSN network ----- 3GPP non-roaming scenario

SGi

Gn

Gn S1-MME

PCRF

Gx

S6a

HSS

S10

UE

GERAN

UTRAN

Gn/Gp

SGSN

E-UTRAN

MME

S11

S5 SGW PGW Operator 's IP Services


Rx

Gr

S1u

• PGW provide Gn/Gp interface• MME provide Gn/Gp interface• PGW provide Gn/Gp interface• MME provide Gn/Gp interface


1-20

Support 3GPP access, EPC NE functions

MME Serving GW PDN GW

NAS signaling processing

NAS signaling security protection

Mobility management between different 3GPP nodes

Tracing and reaching of idle mobile terminal

TA List management Selection of PDN GW

and Serving GW Selection of MME and

SGSN Lawful monitoring Roaming control Security authentication Bearer management

Anchor point for hand off process between eNodeB

E-UTRAN data cache under idle mode and triggering of network side Service Request process

Lawful monitoring Packets routing and

forwarding UL/DL transport layer

data labeling Statistics based on

user and QCI (used for billing between operators)

DL/UL billing based on user, PDN and QCI

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

DHCPv6 （ client 、 server ）

DL/UL Bearer binding UL bearer binding check

Similar to control plane of SGSN Similar to user plane of SGSN Similar to GGSN


1-21

3GPP access structure (home routed)

S6a

HSS

S8

S3

S1 - MME

S10

UTRAN

GERAN

SGSN

MME

S11

Serving Gateway UE

“ LTE

- Uu ”

E - UTRAN

S12

HPLMN

VPLMN

PCRF

Gx Rx

SGi Operator’s IP

Services (e.g. IMS, PSS etc.)

PDN Gateway

S 1 - U

S4


1-22

3GPP access structure (Local Break Out)

S6a

HSS

S 5

S3 S1 - MME

S10

GERAN

UTRAN

S G SN

MME

S11

Serving G ateway UE

" LTE - Uu" E - UTRAN

S4

HPLMN

VPLMN

V - PCRF

Gx

SGi

PDN G ateway

S1 - U

H - PCRF

S9

Home Operator’s IP

Services

Rx

Visited Oper ator PDN

S12


1-23

Non-3GPP Access Structure (S2a/S2b)

SGi

PCRF

Gx

HSS

S2b

SWn

Operator's IP Services


SWm

SWx

Untrusted Non-3GPP IP

Access SWa

HPLMN

Non-3GPP Networks

S6b

Rx

PDN Gateway

ePDG 3GPP AAA Server

Gxb

S2a

Gxa

Trusted Non-3GPP IP

Access STa

Gxc

S5

S6a

3GPP Access

Serving Gateway

UE

SWu

• 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

• 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-24

Non-3GPP Access Structure (S2c)

SGi

PCRF

Gx

HSS

SWn

Operator's IP Services (e.g. IMS, PSS, etc.)

SWm

SWx

Untrusted Non - 3GPP IP

Access SWa

HPLMN

Non-3GPP Networks

S6b

Rx

PDN Gateway

Trusted Non-3GPP IP Access

STa

S2c S2c

ePDG 3GPP AAA Server

UE

Gxa

Gxb

Gxc

S5

S6a

S2c

3GPP Access

Serving Gateway

• 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

• 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-25

Contents



1-26

EPC Main Interfacesinterface protocol

Protocol number Related NE Interface Function

S1-MME S1AP 36.413 eNodeB - MME SM and MM info transfer

S1-U GTPv1 29.060 eNodeB – S-GWTunnel established between GW and eNodeB

to transfer data

S11 GTPv2 29.274 MME – S-GWGTP adopted to establish tunnel between MME

and GW to transfer signal

S3 GTPv2 29.274 MME – SGSNGTP adopted to establish tunnel between MME

and SGSN to transfer signal

S4 GTPv2 29.274 S-GW – SGSNGTP adopted to establish tunnel between S-GW

and SGSN to transfer data and signal

S6a Diameter 29.272 MME - HSSUser location information switching and user

profile information management

S10 GTPv2 29.274 MME - MMEGTP adopted to establish tunnel between MME

to transfer signal

S12 GTPv1 29.060 S-GW – UTRANEstablish tunnel between UTRAN and GW to

transfer data

S2a PMIPv6/MIPv4 RFC5213P-GW – Trusted Non-

3GPP IP Accesse Transfer non-3GPP service data

S5/S8 GTPv2 29.274 S-GW – P-GWGTP adopted to establish tunnel between GW

to transfer data


1-27

EPC Main Protocol Stack

SCTP

L2

L1

IP

L2

L1

IP

SCTP

S1-MME eNodeB MME

S1-AP S1-AP

UDP

L2

L1

IP

L2

L1

IP

UDP

S10 MME MME

GTP-C GTP-C

UDP

L2

L1

IP

L2

L1

IP

UDP

S11 MME S-GW

GTP-C GTP-C

SCTP

L2

L1

IP

L2

L1

IP

S6a MME HSS

Diameter Diameter

SCTP

1-28

Contents



1-29

TA List1TA List1

TA List2TA List2

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 doesn’t need trigger TA update procedure when the UE moves in the same TA List.

The Tracking Area Identity is constructed from the MCC (Mobile Country

Code), MNC (Mobile Network Code) and TAC (Tracking Area Code).

The Tracking Area Identity is constructed from the MCC (Mobile Country

Code), MNC (Mobile Network Code) and TAC (Tracking Area Code).

TA 1TA 1

TA 2TA 2

TA 5TA 5

TA 4TA 4

TA 3TA 3

MMEMME

TA (Tracking Area) List ---- Optimization of Mobility Management


1-30

ISR (Idle Signaling Reduction) ---- Optimization of Mobility Management

TA1TA3

RA3

TA2TA4

TA5

RA1

RA2

TA List1TA List1

TA List2TA List2

ISR

Combined Area= TA List + RAThe UE doesn’t need trigger TA update procedure when it moves in the combined area.ISR is not recommended to deploy in commercial phase because of

its complexity and less benefits.

Combined areaCombined area

RA4


1-31

IPv4v6 Dual Stack EPS Bearer HandlingIPv4v6 Bearer AdvantageIPv4v6 Bearer AdvantageBearer

TypeLTE 2/3G Note

IPv4 Y Y UE gets IPv4 address and forward IPv4 packet

Ipv6 Y Y UE getsIPv6 address and forward IPv6 packet

IPv4v6 Y Y/N UE gets IPv4 and v6 addresses and forward IPv4 and IPv6 packets

Solve the problem of forwarding IPv4 and IPv6 addresses within user data in one PDP context, reduce the bearer context numbers needed

Terminal SGSN/MME 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

Unclear of the capability of terminal ask for IPv4v6

MME/SGSN send request to PGW to identify Dual Stack Flag on following conditions

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

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

R8 network IPv4v6 Dual Stack Bearer Processing Method

LTE and 2/3G bearer is one to one mapping


1-32

EPC Network Security Optimization

UE

eNB

eNB

Xu

Xu

MMES 1 - C

S 1 - CX 2

Evolved Packet Core ( EPC )

E - UTRAN

SAE GW

S 1 -U

S 1 -U

Security layer 1 Security layer 2

Security layer 1

EPS Security and UMTS Security in Common EPS access authentication: AKA

EPS Security and UMTS Security in Difference EPS security layers

AS （ Access Stratum ） security–Security between UE and eNB （ E-UTRAN ） , including RRC signaling confidentiality, RRC signaling integrity and UP (User Plane) confidentiality

NAS （ Non Access Stratum ） security–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.

AS and NAS algorithms


1-33

Analysis of SGSN type in EPC Network

SGSN is GnGp SGSN SGSN is S4 SGSN

Advantage

Less modification to legacy GPRS networkNot much modification to legacy 2/3G user service flow and feeling to the serviceNetwork structure is simple

There is only one network that is EPC network;Only one set of contracted data is needed in operator network : HSS ；Only one set of DNS is needed in operator network : R8 DNS(EPC DNS);No problem in communication with non-3GPP network;There is only one set of billing system: EPC billing;Support ISRGood for extension of new functions

Disadvantage

GnGp SGSN can not get user attribute and is unable to select GGSN and PGWTwo sets of contracted data management: HLR and HSSSupport of Pre-R8 DNS(GPRS DNS) and R8 DNS(EPC DNS) is neededSupport of GPRS and EPC billing is neededISR is not supported, it is implemented between S3/S4 SGSN and MMENot good for the extension of following new functionsProblem 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 SGSNNetwork 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 changedService 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 For the long term development, S4 SGSN is preferred


1-34

Choice 1: Interworking With S4 SGSNHSSGSM

UTRAN

Se

rvic

e C

on

tinu

ity

Gb

Iu-PS

S4 SGSN

S4

S-GW

MME

P-GW


LTE

S1-MME

S1-US10

SGi

S5/S8S12

S6d

S6a

EPC

S3

GTPv2

UDP

IP

L2

L1

GTPv2

UDP

IP

L2

L1

S4 SGSN MME/SGWS3/S4

Diameter

SCTP/TCP

IP

L2

L1

Diameter

SCTP/TCP

IP

L2

L1

S4 SGSN HSSS6d


1-35

Choice 2: Interworking With Gn/Gp SGSN

HSSGSM

UTRAN

Se

rvic

e C

on

tinu

ity

Gb

Iu-PS

S-GW

MME

P-GW


LTE

S1-MME

S1-US10

SGi

S5/S8

Gn/Gp SGSN

S12

Gn/Gp S6a

Gr

EPC

Gn/Gp

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

Via Gn/Gp SGSN Via S4 SGSN

Need upgrading on SGSN Support of R8 feature as ISR Fewer protocols in the network: GTPv2,

Diameter


1-36

Mapping between R8 QoS and Pre R8 QoS

GERAN/UTRAN EUTRAN

SGSN

GGSN

MME

SAE-GW

Pre R8 PCN R8 EPC

MusicTV StockWEB

R7 Main QoS Profile

Traffic Class ARP 、 GBR 、 MBR Traffic Handling

Priority Signalling Indication Source Statistics

Descriptor Packet Delay Budget Packet Loss Rate

R8 Main QoS Profile

QoS Class Identifier, QCI

ARP 、 GBR 、 MBR UE AMBR APN AMBR

• 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-37

Standardized QCI Characteristics

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.

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.

QCI Resource Type

Priority Packet Delay Budget Packet Error Loss

Rate

Example Services

1 GBR 2 100 ms 10-2 Conversational Voice

2 4 150 ms 10-3 Conversational Video (Live Streaming)

3 3 50 ms 10-3 Real Time Gaming

4 5 300 ms 10-6 Non-Conversational Video (Buffered Streaming)

5 Non-GBR 1 100 ms 10-6 IMS Signalling

6 6 300 ms 10-6 Video (Buffered Streaming)TCP-based (e.g., www, e-mail, chat, ftp, p2p file sharing, progressive video, etc.)

7 7 100 ms 10-3 Voice,Video (Live Streaming)Interactive Gaming

8 8 300 ms 10-6 Video (Buffered Streaming)TCP-based (e.g., www, e-mail, chat, ftp, p2p file

sharing, progressive video, etc.)9 9


1-38

CS fallbackCS fallback

Voice Solutions for LTE

EPC

PSTN/PLMN

RAN/GERAN

MSCSMGW MME SAE-PGW

HSS

CS

INTRENET

SGs

eNodeB

EPC

PSTN/PLMN

RAN/GERAN

MSCSMGW MME SAE-PGW

HSS

CS

INTRENET

Sv

eNodeB

MGCF

SCC AS

IMS

CSCF

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

IMS+SRVCCIMS+SRVCC

All service over LTE/EPC in LTE

area

IMS needed

Upgrade on MSC/MSCS

Defined in 3GPP R8 (LTE->CS

only)

2211


1-39

LTE Voice Solution——SRVCC

UDP

L2

L1

IP

L2

L1

IP

UDP

Sv MSC Server MME

GTP GTPGERANGERAN

UTRANUTRAN

EUTRANEUTRAN

MMEMMEEPS DomainEPS Domain

E-MSC ServerE-MSC ServerCS DomainCS Domain

SVSV

Voice service continuity initiated by PS handover ， MSC-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 Mature IMS network is deployed HSPA/IMS to 2G/3G CS SRVCC solution is similar

IMS DomainIMS Domain

SAE-GWSAE-GW

1 Han

dove

r

Requi

red

2 For

ward

Reloc

atio

n

Reque

st 3 Session transfer

4 Handover

Vo

ice S

ervice C

on

tinu

ity


1-40

LTE Voice Solution——SRVCC

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

MME （ SGSN HSPA/IMS to 2G/3G occasion） 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

HSS Insert SRVCC VDN to MME during UE attach flow

UE Need to inform network whether SRVCC is supported or not


1-41

LTE Voice Solution—— CS Fallback

SCTP

L2

L1

IP

L2

L1

IP

SCTP

SGs MSC Server MME

SGsAP SGsAPGERANGERAN

UTRANUTRAN

EUTRANEUTRANMMEMME

EPS DomainEPS Domain

E-MSC ServerE-MSC Server

CS DomainCS Domain

SGsSGs

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 EPS （ among which SMS related

message encapsulated ） implement SMS communication between MSC and UE


1-42

LTE Voice Solution—— CS Fallback

Related NE modification： UE

EPS/CS mobility management SMS special handling

MSC SMS special handling SGs interface protocol stack

MME SGs interface special handling SMS special handling

E-UTRAN SMS ， CS paging handling

1-43

Contents



1-44

ZTE Solution for broadband network

LTE WiMax / WiFiUTRAN/GERAN xDSL/xPON

OSA-OSA-SCSSCS

SCPSCPIM-SSFIM-SSF

SIPSIPASAS

SS

S

SS

S

SS

S

SS

S

Service Platform

GGSN HA SAE-GWSGSN

MME AGW ePDGAC/SR/BRAS

Features

6 unification

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

HLR/HSS/AAA/SPR PCRF

ZEPS (ZTE Evolved Packet Solution)

Unified gateway

xGW

Unified policy mgmtRAC

Unified user mgmtUSPP

Unified network mgmtNetNuman

统一移动性管理uMAC

Unified access networkSDR

ZEPSZEPS


1-45

SAE GW

BRAS

GGSN

SGSN

MME

HSSZXUN uMAC

ZXUN xGW

AGW

HA

PDSN

support at most 5000,000 user

99.999% reliability, complete redundancy backup

mechanism

high density processor, powerful service processing

capability

support at most 5000,000 user


mechanism

high density processor, powerful service processing

capability

AAA

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


mechanism

Powerful RoHC, DPI capability

Embedded Firewall, complete security mechanism

Control plane platform

User Plane Platform

PCRF

ZEPS Advanced Platform


1-46

Large Capacity: Tbps level packet GW, 1.92Tbps per cabinet Serialization: 18/72/160G serial products.

Convergence & Evolution: seamlessly convergent for Fix &

Mobile access.

Intelligence: Intelligent service awareness and management

with embedded DPI engine.

Reliability: >99.999% reliability, multi redundancy mechanisms

September 2009BBWF InfoVision Awards

T8000 Router Platform

ZTE Convergent Broadband Packet GW—ZXUN xGW


1-47

Geographical Hot Spare Protection

Geographical backup on subscriber data, guarantee the session won’t be disconnected.

No extra support from other NE.

Geographical backup on subscriber data, guarantee the session won’t be disconnected.

No extra support from other NE.

Build-in Firewall

Dedicated FW module10Gbps per boardMulti-FW load share

Dedicated FW module10Gbps per boardMulti-FW load share

Hot Spare Protection

N+1 real time backup on subscriber data in service module.

1+1 backup for FW module

N+1 real time backup on subscriber data in service module.

1+1 backup for FW module

Firewall UnitFirewall Unit 11

22

33Site A

xGW1

Site B

xGW2

Heartbeat

Data synch

GS

U

FW

FW

PF

U

PF

U

GS

U

GS

U

GS

U

FW

FW

ZXUN xGW

ZXUN xGW provides telecom-grade Reliability


1-48

20

40

60

80

Av

a P

ow

er

(W/G

bp

s)

5260

63

41

C ZTE E H

•Switch off un-used service

boards in free time

•Switch off unused CPU within

service board

•Power on/off control on switch

board according to traffic load

Smart Power Control of Service Board

Smart Power Control of Switch Board

•Monitoring system

temperature in real time

•Speed adaptation according to

system temperature

Smart Fan Adaptation

•Monitoring power

consumption in real time

•Adaptation of output power via

automatic control module

Smart Power Supply

线卡

风扇电源

进程

业务

业务

线卡风扇

电源

进程

进程

业务线卡

风扇

电源

电源

进程业务

线卡

风扇

Fan

Power High Integration

ServiceBoard

Switch Board

High Integration

Green EPC Making Greener Earth


1-49

Broadband Access

Broadband Access

InternetInternet

IdentifyIdentify AnalyzeAnalyze ControlControl ReportReport

Intelligence: Easy Traffic Control and Management for Mobile Data

Access ControlAccess Control

Bandwidth ManagementBandwidth

Management

Content-based charging

Content-based charging

Routing Management

Routing Management

Security Management

Security Management

Subscriber Service Analysis-UBAS

Subscriber Service Analysis-UBAS

Subscriber Behavior Awareness

Subscriber Behavior Awareness

Service Awareness

Service Awareness

disorder, disorder, unknown, unknown, uncontrollable uncontrollable traffic flow traffic flow

manageable, manageable, visible and visible and profit-driven profit-driven traffic flowtraffic flow

P2P UploadP2P UploadP2P DownloadP2P Download

VoIPVoIPWebTVWebTVVideo ConferencingVideo Conferencing

GamingGamingemailemail

Each bit generates profit for operators

DPI UBASUBASUBASUBAS PCCPCC


1-50

ETCA Platform for ZTE RCP Products

ZIMS Series Products

CSCF

MSCS

HSS/AAA/SPR

RCP(RACS/PCC ）

uMAC

ETCA Platform

Advantage

ETCA Platform

Advantage

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

ETCA is the new generation unified all IP

platform that designed for ZTE control

and service layer products.

ETCA is based on ATCA architecture, which fully meet the operators requirement of high performance, good reliability and expansibility.


1-51

Special policy control equipment (ZXUN RCP) is introduced to guarantee IMS service QoS

Deployed in IMS System—Service QoS Policy Control

SDF-filter

QoS-Class-Identifier

Max-Requested-Bandwidth-UL

Max-Requested-Bandwidth-DL

Guaranteed-Bitrate-UL

Guaranteed-Bitrate-DL

Bearer-Identifier

Allocation-Retention-Priority

Resource

Authorization Request

Service Resource

QoS Control

AF-application-identifier

Service-info-status

Reservation-priority

Media-Type

Max-request-bandwidth-UL

Max-request-bandwidth-DL

Mobile access

Bear plane SR

Fixed access

Resource control plane

Session control plane

SIP S

IP

SIPAS

ZXUN RCP

CSCF

PS-GW

BRAS

Rx

Gx(x)

Gq’

Ia Re

C-BGF

P-CSCF P-CSCF

ZXUN RCP


1-52

SDF-filter

Service-Identifier

Rating-Group

Reporting-Level

Online

Offline

Metering-Method

AF-Charging-Identifier


Service-info-status

AF-Charging-Identifier

OCS/OFCS

PS Core

AF

SPR

Conditions Actions

IMS +Video Conf Online + Volume….

IMS + VoIP …. Online + Duration….

IMS + MMS…. Offline + Event….

…… ……

PS-GW

ZXUN RCP

Internet

Charging correlation for both control plane and media plane to avoid repeated charging Service flow based charging, which ensures more flexible and accurate charging.

Deployed in IMS System—Charging Correlation and Charging Rules Control


1-53

BRASBGF

IP NAPT

(IP_termination)


Service-info-status

Media‑Component

‑Description

Reservation-priority

Binding‑Information AF

CLF ZXUN RCP

DSLAM

NAT Mapping Relation

10.0.1.1/2001 <-> 202.93.2.1/4400

10.0.1.2/2002 <-> 202.93.3.1/4301

10.0.1.0/24 202.93.0.0/16

Private network Public network

Internet

Network topology hiding, enhance network security; Solve public/private network interconnection problem;

Deployed in IMS System—NAT Control


1-54

Internet

Video

Voice

Terminate Access Network

L2 Aggregation IP Service Edge

Service Networks

Bearing Control/Service ControlLayer

Bearing NetworkLayer

NMS/EMS

Policy SystemBOSS

DPI

DPI

DPIDPI

DPI

ZXUN RCP

SPR

Transform from pipe provider to service based subdivided operation Network resource utilization optimization

Service QoS and Charging Policy Control Interface

Deployed in Fixed/Wireless Broadband Data Network—DPI Based Service Differential Control


1-55

ZXUN SPR

ZXUN RCP

OCSOFCS

PS Core

GGSN

CE/PE PE

PCC domain

Video conference

VoIP/Centrex

OA

IM

meeting

AF

Music download

TVstock

web

Portal Server

Service domain (VAS)

• 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

• 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

ZXUN RCP Deployment in HK CSL


1-56

ZXUN SPR

ZXUN RCP

OCSOFCS

PS Core

GGSN

CE/PE PE

PCC domain

Video conference

VoIP/Centrex

OA

IM

meeting

AF

Music download

TVstock

web

Portal Server

Service domain (VAS)

• 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

• 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

ZXUN SPR Deployment in HK CSL

Network Basic Principle

Documents

p2p file sharing

evolved packet core

3gpp access structure

unified core network

legacy gprs network

related ne modification

mobile access

zxun xgw