SAMSUNG EPC System SAMSUNG EPC System O iO i
SAMSUNG EPC System SAMSUNG EPC System O iO iOverviewOverviewOverviewOverview
Contents
LTE Network Configuration
LTE/EPC structural features and functionsLTE/EPC structural features and functions
MME, S-GW, P-GW Functions
SAMSUNG EPC ifi i d l hSAMSUNG EPC specifications and structural shapes
Redundancy
2
LTE Network Architecture eNB: E-UTRAN Node B ePDG: evolved Packet Data Gateway GGSN: Gateway GPRS Support Node GTP: GPRS Tunneling Protocol SGSN: Serving GPRS Support NodePDN
PCRFGGSN
SGi
Gx
RxGi
SGSN: Serving GPRS Support Node MME: Mobility Management Entity PDN: Packet Data Network
PDNGateway
PCRF
Pre-R8 SGSN
GGSN
S5
Gx
Gn/Gp S2b
Gn/Gp GxbIu Gx
ServingGateway
HSS
SGSN
MSC Server S11
S5
SGs
ePDG
Sv
Gs
S4
S2a Gxa
AAAS d
S6b
MMEHSS
R8 SGSN
S6a
S1-U
S1-MME
SGs
Trusted Non-3GPP IP Access
S3
WCDMAIu-C
S12AAA
SWd
SWx
SWnSTb SWa
eNodeB eNodeB
LTE-Uu
X2
LTEWCDMA Non-3GPP
UntrustedNon-3GPP IP Access
WCDMA/HSPA
3
UE
LTE/EPC Structural Features
and Functions
4
EPC Session/bearer establishmentAlways-on
UE Authentication, IP address allocation(session establishment), default bearer establishment
Dedicated bearer can be set or release by UE or PCRF
There is no exist UE context in E-UTRAN for UE in the ECM-IDLE statebut session and bearer context in MME, S-GW, P-GW is maintained., ,
UE state is switched to active when paging by service request or network
MME< Active State> MME
eNB S GW P GW
UE
2 or more IP
session can be
set by UEeNB S-GW P-GW
1 IP Session (1default bearer + 0 or more dedicated bearer)
set by UE
request.
MME< Idle State> MME
UESession
between S-Gw
< Idle State>
5
eNB S-GW P-GW
1 IP Session
and P-GW is
maintained.
Connection Configuration between Access and Core
Original Access – Core connection
Hierarchical structure (1 : N connection)
Access in LTE – Core connection
Core system is connected by pool structure, N:M
M d ibili f NB i ll d di ib d diManagement and responsibility of eNB is allocated to core system distributed according
to UE.
MME pool 1 MME pool 2< Previous Access-Core system> < Access-Core configuration in LTE >
Core system
MME
BSC/RNC
● ● ●
Pool Area 1 Pool Area 2● ● ●
BSC/RNC
6
BTS/NodeB eNodeB
Mobility Management for LTEUE1 TA list
TA2RA1
RNC1MMETA1
UE1 TA list
NB2
SGSNNB1
eNB2
eNB1
TA3* TA (Tracking Area)• Minimum unit : cell
RA2
RNC2eNB4
TA3• possible to make more than one cell in one eNB• the number of cell per one eNB : minimum one, maximum 256개• one TA is consisted of n cells.TA i ll t d b t
NB4NB3
eNB3
dl bili
UE2 TA list
dl bili
• TA is allocated by operator.* TA list • TA list is allocated by MME considering current location of UE.• one TA list is consisted of n TAs.
3G Idle mobility
All UE performed location update on Fixed RA.
EPS Idle mobility
Location update occurred when allocated each UE is outside TA list.
Paging performed in RA which UE updated location.
TA area is maintained fixed area.
TA list allocation to give UE is possible
When UE initiated Attach and TAU, MME
7
,can be allocated TA list.
paging by TA list area allocated to UE
ISR function
ISR (Idle mode Signaling Reduction) to limit signalling during inter-RAT cell-reselection in idle mode
C ll l i TAU/RAU i d dCell-reselection, TAU/RAU count is reduced.
E-UTRAN UE (GERAN/UTRAN supported) is mandatory function.
R8 SGSN supported ISRpp
Pre-R8 SGSN does not supported ISR.
UE registered
HSS
Run periodic update timer.If timer expires, detach implicitly
If UE cannot perform periodic update, deactivate ISR
TAU
S-GW PDN-GW PDN
MMEE-UTRANHSSGUTI, TA
Session Information
TAU
SGSNUTRAN/GERANP-TMSI, RA
UE registeredRun periodic update timer.
If timer expires, detach implicitly If UE cannot perform periodic update,
RAU
8
deactivate ISR
CSFB (Circuit Switch Fall Back)MSC transmit Paging request to MME. Then It sends to UE through eNB.Paging response is transmitted to CS domain. It provides voice service in CS domain.MSC needs 3GPP Rel.8 support for interworking with MME.
SGs interface (SGsAP/SCTP/IP)
NodeB/RNC SG
MSC GMSCCS call paging response is sent through RNC in 3G IuCS Voice service
MME
NodeB/RNC SGs
HSSS6a
Dual-modeSingle radio terminal
(Radio mode Transition)
S5
S11S1‐MME
S1‐U
(Radio mode Transition)
S‐GW P‐GW/GGSNeNB
9
SRVCC (Single Radio Voice Call Continuity)
Possible to handover between LTE and 3G Network during VoIP Call.
MSC needs a 3GPP Rel.8 support for interworking with MME.Sv interface (GTP-C/UDP/IP)
MSC
Nc
Sv
eMSCBICC/RTP
CS voice in 3GIuCS
Voice service
Nc
MME HSS
Sv
Dual-modeSingle radio terminal
(Radio mode Transition)
NodeB/RNC
S6a SGi
S5VoIP in LTE
S11S1‐MME
S1‐U
10S‐GW P‐GW/GGSN
eNB
Charging FunctionOffline Charging
Support P-GW and S-GW
Volume/time based charging
ApplicationFunction (AF) / g g
Interworking with OFCS (Gz interface: GTP’)
Interworking with AAA(SGi interface: Radius)
CDR generation for each EPC bearer
Policy And Charging
Rule Function
SubscriptionProfile
Repository(SPR)
Online Charging
Rx
Sp
3GPP Specific Charging
(P-GW: PGW-CDR, S-GW: SGW-CDR)
Online Charging
(PCRF) System(OCS)
Service Data Flow Based
Credit Control
GxGy
Support P-GW
Real-time charging by Credit control
Interworking with OCS (Gy interface: Diameter)P-GW
Policy And Charging Enforceme
nt Function (PCEF)
Offline ChargingSystem(OFCS)Gz
SGi
Radius Accounting
(Offline)
S-GW
Ga
참고: S-GW charging– charging for roaming users– Interworking with OFCS and GTP’ protocol
11
Interworking with OFCS and GTP protocol(not interworking with AAA)
– support charging per bearer, not support FBC
DPI-based differentiated QoS & Charging
Off-line/on-line charging
Advanced QoS Control Advanced Charging Feature
Packet flow based bandwidth control Off line/on line charging
Service aware charging per packet flow
PCC based charging
Packet flow based bandwidth control
Application based bandwidth control
PCC based QoS control
Offline / Online charging / PCC rules operation for various tariffs
Gz interface for Offline charging
Gy interface for Online charging
P-GW(GGSN functionality)
PCRFGx
(GTP-C/U)E-UTRAN/UTRANPDN
Gy interface for Online charging
Gx interface for PCC rules operation
S-GW/SGSNOffline Charging System
PDN
Online Charging System
GyGz
Skype
HTTP, Download
FTP
Default bearerBehavior, Heuristic Analysis
Pattern Matching
12
Dedicated bearer
Real-time game
SAMSUNG EPC
Specification & Structurep
13
MME Function
S1-AP 및 NAS signalling
NAS signaling security
Inter CN node signaling for mobility between 3GPP access networks (S3)
Location registration and Paging for Idle mode UE
TA list management, Paging retransmission
NE selection
PDN GW, Serving GW selection
MME selection for handovers with MME change
SGSN selection for handovers to 2G or 3G access network
Roaming for interworking HSS (S6a interface)
UE Authentication
Interworking for Non-3GPP network
14
HRPD interworking (S101 interface) :
- Signaling for HRPD network and Optimized Handover
S-GW Function
Interfacing E-UTRAN for bearer
Local Mobility anchor point for inter-eNodeB Handovery p
Mobility anchor point for inter-3GPP (2G/3G/P-GW)
Packet routing & forwarding
Paging to ECM-Idle mode UE for incoming call
Accounting for inter-operator changing
UL/DL transport level packet marking
15
P-GW FunctionInterfacing external PDN
Mobility anchor point between Non-3GPP and 3GPP
Packet routing & forwarding
UE IP address allocation
Per-user based packet filtering
PCEF (Policy and Charging Enforcement Function) function
UL/DL bearer binding and UL bearer binding verification
Service level charging, gate control, rate enforcement
PCRF interworking and Policy / Charging control
DL rate enforcement based on APN-AMBR, MBR
l l k kUL/DL transport level packet marking
16
HSS / PCRF Function
HSS (Home Subscriber Server)
User id, numbering, addressing storedUser id, numbering, addressing stored
User security information generation
- mutual authentication and encryption for between UE and network
User location information storage
User profile information storage
PCRF (Policy and charging rule function)
S di Q S d h i l G C f S S i l dSending QoS and charging rule to P-GW(PCEF) for SDF (Service Data Flow) and
IP-CAN Session
P-GW (PCEF) is performed QoS and Charging functions according to PCCP GW (PCEF) is performed QoS and Charging functions according to PCC
rule
17
Flexible to allocate CPU Core
MPP #1C lC t l
MPP #2CoreCore CoreCore CoreCore CoreCore
CoreCore CoreCore CoreCore CoreCore
CoreCore CoreCore CoreCore CoreCoreData Data
ControlPlane
Control Plane
CoreCore CoreCore CoreCore CoreCore
CoreCore CoreCore CoreCore CoreCore
CoreCore CoreCore CoreCore CoreCore
CoreCore CoreCore CoreCore CoreCorePlane PlaneCoreCore CoreCore CoreCore CoreCore
Optimization according to control & data plane usage
CoreCore CoreCore CoreCore CoreCore
CC CC CC CC
MPP #1
Control PlaneControl Plane CoreCore CoreCore CoreCore CoreCore
CC CC CC CC
MPP #2
CCoreore CoreCore CoreCore CoreCore
CoreCore CoreCore CoreCore CoreCore
CoreCore CoreCore CoreCore CoreCore
Data Plane
DataPlane
CoreCore CoreCore CoreCore CoreCore
CoreCore CoreCore CoreCore CoreCore
CoreCore CoreCore CoreCore CoreCore
Support 16core per MPP (Multi-core Packet Processor)
Core of MPP performs Signaling processing(Control Plane) and Packet processing(Data Plane).
18
It will be optimized system according to traffic pattern change (M2M, video streaming) in the future. (It can be optimized the number of Core allocation.)
MME SpecificationItem Description
Product MME (Mobility Management Entity)
Rack Dimension (H x W x D) 2 000 x 600 x 800 mmRack Dimension (H x W x D) 2,000 x 600 x 800 mm
Shelf Dimension (H x W x D) 483 x 468 x 577 mm
Subscriber 2M
EPS bearer 6MEPS bearer 6M
call processing performance 6K CPS (attach )
- eNB : 32,000- S-GW : 1,024
allowable number of Nodes- HSS : 300- EIR : 100- WCDMA SGSN : 1,024- WCDMA MSC server : 100
RAID
Number of external interfaces4 x 10G ports and 4 x GE ports
( or Total GE : 8 ports)
R d dLESA : 2:1 LENA 1 1Redundancy LENA : 1:1LEMA : 1:1
Available System configuration- 1Rack 1 shelf 1 system- 1Rack 2 shelf 1 system
19
- 1 Rack 2 shelf 2 system
S-GW SpecificationItem Description
Product S-GW (Serving Gateway)
Rack Dimension (H x W x D) 2 000 x 600 x 800 mmRack Dimension (H x W x D) 2,000 x 600 x 800 mm
Shelf Dimension (H x W x D) 483 x 468 x 577 mm
Throughput 33Gbps
call processing performance 5K CPS (bearer activation / deactivation )call processing performance 5K CPS (bearer activation / deactivation )
EPS bearer 4.5M
allowable number of Nodes
- eNB : 32,000- MME : 4,000
allowable number of Nodes- WCDMA SGSN : 4,000 - P-GW : 4,000
Number of external interfaces12 x 10G ports & 12 x GE ports
(or Total GE : 24 ports)RAID
RedundancyLEDA : 2:1LENA : 1:1 LEMA : 1:1
1Rack 1 shelf 1 systemAvailable System configuration
- 1Rack 1 shelf 1 system- 1 Rack 2 shelf 2 system
20
P-GW SpecificationItem Description
Product P-GW (PDN Gateway)
Rack Dimension (H x W x D) 2 000 x 600 x 800 mmRack Dimension (H x W x D) 2,000 x 600 x 800 mm
Shelf Dimension (H x W x D) 483 x 468 x 577 mm
Throughput 23Gbps (with PCC*)
call processing performance 5K CPScall processing performance 5K CPS
EPS bearer 4.5M
allowable number of Nodes- S-GW : 4,000 - APN : 2,000
Number of external interfaces12 x 10G ports & 12 x GE ports
(or Total GE : 24 ports)
RedundancyLEDA : 2:1 LENA : 1:1
RAID
Redundancy LENA : 1:1 LEMA : 1:1
Available System configuration- 1Rack 1 shelf 1 system- 1 Rack 2 shelf 2 system
* PCC: SDF level QoS, FBC function support
21
Board Types and Functions
Category Function
LESALTE EPC Signaling interface board Assembly- Call processing in the MME- Control of mobility and session
LEMALTE EPC Management board Assembly- 200-Gbps packet switch- System Management
LENALTE EPC Network interface board Assembly- Packet interface- Packet processing (10 GE, 1 XGE (10-Gbps I/F))
LEDALTE EPC Data processing board Assembly- Packet processing and control in the S-GW and P-GW- Software-based packet control using the multi-core packet processor
DPBB-4Data Processing shelf Backplane Board assembly-version 4- Inter-board packet interface- Alarm channel within a shelf backplane
22
MME System ArchitectureMME System ArchitectureEMS
Pkt SwitchMain OAM
LEMA
IPRS
LENA0 LENA1 LESA0 LESA3 LESA6
Call Processing
Call Processing
DIAMETER ALG
DNS Proxy
DIAMETER ALG
DNS Proxy
Call Processing
Subscriber DB
SubscriberDB
SubscriberDB
Pkt I/F Pkt I/F
y y
S1-AP ALG S1-AP ALG S1-AP ALG
GTP-C ALG GTP-C ALG GTP-C ALG
MME/S GW/• IPRS : IP Routing Subsystem
DiameterS1-APGTP-C, DNS
23
MME/S-GW/ DNSHSS/EIR eNB
S-GW System ArchitectureS-GW System ArchitectureEMS
Pkt SwitchMain OAM
LEMA
IPRS
LENA0 LENA4LENA2 LEDA0 LEDA3LENA2 LEDA0
Call Processing
LEDA3
PacketF di
PacketPacketF di
Load Distribution
Load Distribution Protocol
Proxy (GTP’)Call
Processing
Packet Processing
Forwarding
Pkt I/F
Forwarding
Pkt I/F
Forwarding
Pkt I/F
Packet Processing
MME
GaS1-UGTP-C, GTP-U
• IPRS : IP Routing Subsystem
24
MME,P-GW E-UTRAN OFCS
P-GW System ArchitectureP-GW System ArchitectureEMS
Pkt SwitchMain OAM
LEMA
IPRS
LENA0 LENA4LENA2 LEDA0 LEDA3LENA2 LEDA0
Call Processing
LEDA3
Protocol Proxy (DHCP)
Load Distribution
Load Distribution
ProtocolProxy (Diameter)
ProtocolProxy (GTP’)
Call Processing
Packet Processing
PacketForwarding
Pkt I/F
PacketForwarding
Pkt I/F
PacketForwarding
Pkt I/F
Packet Processing
Gx, Gz, Gy, Radius, DHCP
SGi
• IPRS : IP Routing Subsystem
GTP-C, GTP-U
PCRF/ OFCS/
25
S-GWS-GWPCRF/ OFCS/ OCS AAA/
DHCPPDN
26
redundant configuration
The EPC supports redundancy of the board, process, interface, power supply, and
fan to enhance reliability and availability for the consistent and reliable servicefan to enhance reliability and availability for the consistent and reliable service.
Target Fault description Redundancy method
Board Board power supply failureOther devices failure
redundancy
N:1 redundancy
Interface Physical link failurePhysical port failure
Active/standby
Link aggregation (Link redundancy)
Equal Cost Multi-Path (ECMP)
Internal path Physical link failure -
Power supply Power short circuit power supply redundancyPower supply Power short circuit power supply redundancy
Fan Fan operation failure Redundant fan configuration
27
Redundant structure of LESA, LEDA
Redundancy : LESA, LEDA (2:1)
1) The fault detection block of the LEMA board periodically monitors the1) The fault detection block of the LEMA board periodically monitors the status of all boards in a shelf using the hardware device information.
2) When an active board fails, a standby board detects the fault and switches to the active boardto the active board.
3) After fault is recovered, Active board is performed into Standby mode.(Backup board changed)
Normal Operation Switch Over Non-Revertive mode
LESA0or
Failure A S A AS AActive Active Standby
X
AAfter Recovery
Standby
LESA1or
LESA2or
LESA0or
LESA1or
LESA2or
LESA0or
LESA1or
LESA2or
Backup
or LEDA0
Take over
XBackup
or LEDA1
or LEDA2
or LEDA0
or LEDA1
or LEDA2
or LEDA0
or LEDA1
or LEDA2
28
Redundant structure of LEMA
Redundancy : LEMA (1:1)
1) The two duplicated boards exchange the data required for the redundancy1) The two duplicated boards exchange the data required for the redundancy through the redundant path between the boards.
2) When an active board fails, a standby board detects the fault and switches to the active boardto the active board.
3) After fault is recovered, Active board is performed into Standby mode.(Backup board changed)
Normal Operation Backup
Switchover
Fail
Active Standby Standby -> Active
Recovery
LEMA0 LEMA1
ActiveBackupStandby
LEMA0 LEMA1OAM OAM
LEMA0 LEMA1OAM OAMX
Fail LEMA0 LEMA1OAM OAM
LESA0 or LEDA0
LESA1 or LEDA1 LENA0 LENA1 LENA0 LENA1 LENA0 LENA1LESA0 or
LEDA0
LESA1 or LEDA1
LESA0 or LEDA0
LESA1 or LEDA1
29
Redundant structure of LENA
Redundancy : LENA (Board : Dual Active, Interface :)
1) The fault detection block of the LEMA board periodically monitors the1) The fault detection block of the LEMA board periodically monitors the status of all boards in a shelf using the hardware device information.
2) When an active board fails, a standby board detects the fault and switches to the active boardto the active board.
3) After fault is recovered, Active board is performed into Standby mode.(Backup board changed)
Normal Operation Switchover Normal Operation
LESA0 LESA1
Active Standby
Back p
LEMA1LEMA0
LESA0 LESA1 or
Active
LEMA1LEMA0
XFail
LESA0 LESA1
ActiveStandby
LEMA1LEMA0
LESA0 or LEDA0
LESA1 or LEDA1
LENA0 LENA1
BackupCP CP
LESA0 or LEDA0
LESA1 or LEDA1
LENA0 LENA1
CP CPX LESA0 or LEDA0
LESA1 or LEDA1
LENA0 LENA1
BackupCPCP
30
Interface RedundancyActive
Active/Standby LEMA
L2-S/W #2
L2-S/W #1
LESA 1
LESA 2
LESA 3 LENA 1
LENA 0Active
Standby
Standby
Active
Active
Backup
Router #1
LEMAL2-S/W #1
LESA 1
LESA 2 LENA 0Active
Active
Active
Active/Standby
Router #1
Link Aggregation
L2-S/W #2LESA 3 LENA 1Active
StandbyBackup
LEMAL2-S/W
LESA 1
LESA 2 LENA 0Active
Active
Active
Router #1
Link Aggregation
gg gLESA 3 LENA 1
Active
StandbyBackup
LEMA
LESA 1
LESA 2 LENA 0Active
Active
ActiveLink Aggregation
Router #1
ECMP
LEMAL2-S/W
LESA 3 LENA 1
Active
Active
StandbyBackup
Router #1
LESA 1
LESA 2 LENA0
Active
ActiveECMPECMP
(Equal Cost Multi-Path)LEMA
LESA 2
LESA 3 LENA 1
LENA 0
StandbyBackup
Router #1
Router #2
Active
Active
LESA 1Active
ECMP Routing table
31
LEMALESA 2
LESA 3 LENA 1
LENA 0
Standby
Active
Backup
Router #1
Router #2
ECMP
Active
Active
Routing tableupdate