SLT EPC Network

Contents

 LTE Nework Architecture

 LTE Signaling flow
 Fault Management
 Trace Management
 CDR Management
 Useful Commands
SLT LTE Core Network Architecture
HW HSS

AAA NTP

LTE enb

CG
EMS

Internet&
Sevice network

MME
DNS SAE GW

SAE GW = Serving GW+PDN GW

Control Plane
User Plane
Support 3GPP Access, EPC NE functions
MME
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
Serving GW
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
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 DHCPv6（client、
server）
DL/UL Bearer binding
UL bearer binding check
Similar to GGSN

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

Term Explanation

EPS

EPC Evolved Packet Core, refers to core network

Evolved Universal Terrestrial Radio Access Network, refers to

EUTRAN
wireless network

SAE System Architecture Evolution=EPC, refers to core network

LTE Long Term Evolution=EUTRAN,only refers to wireless network

EPC Interfaces

UTRAN

SGSN

GERAN HSS

S3

S1 - MME S6a
MME
PCRF

S12
Rx+
S11 S7
S4
" LTE - Uu " S10

Serving S5 PDN SGi

UE E - UTRAN Operator 's IP Services
Gateway Gateway
(e.g. IMS, PSS etc.)
S1 - U

 all IP structure
 flat network structure
 media and control plane separated
 interconnection with existing network
 EPC Main Interfaces
Protocol
interface protocol number Related NE Interface Function

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

Tunnel established between GW and
S1-U GTPv1 29.060 eNodeB – S-GW eNodeB to transfer data
GTP adopted to establish tunnel between
S11 GTPv2 29.274 MME – S-GW MME and GW to transfer signal
GTP adopted to establish tunnel between
S3 GTPv2 29.274 MME – SGSN MME and SGSN to transfer signal
GTP adopted to establish tunnel between
S-GW and SGSN to transfer data and
S4 GTPv2 29.274 S-GW – SGSN signal
User location information switching and
S6a Diameter 29.272 MME - HSS user profile information management
GTP adopted to establish tunnel between
S10 GTPv2 29.274 MME - MME MME to transfer signal
Establish tunnel between UTRAN and
S12 GTPv1 29.060 S-GW – UTRAN GW to transfer data
P-GW – Trusted Non-
S2a PMIPv6/MIPv4 RFC5213 3GPP IP Accesse Transfer non-3GPP service data
GTP adopted to establish tunnel between
S5/S8 GTPv2 29.274 S-GW – P-GW GW to transfer data
EPC Protocol Stack

GTP-C GTP-C
S1-AP S1-AP

SCTP SCTP UDP UDP

IP IP IP IP

L2 L2 L2 L2

L1 L1 L1 L1

S1-MME S11
eNodeB MME MME S-GW

GTP-C GTP-C Diameter Diameter

UDP UDP SCTP SCTP

IP IP IP IP

L2 L2 L2 L2

L1 L1 L1 L1

S10 S6a
MME MME MME HSS
Attached Flow
Mobility Management ---- Attach Flow
UE eNodeB new MME Old Serving GW PDN GW PCRF HSS
MME/SGSN
1. Attach Request
EIR
2. Attach
Request 3. Identification Request
3. Identification Response
4. Identity Request
4. Identity Response
5a. Authentication / Security
5b. Identity Request/Response
5b. ME Identity Check
6. PCO Request
6. PCO Response
7. Delete Bearer Request 7. PCEF Initiated IP-CAN
Session Termination
7. Delete Bearer Response
(A)
8. Update Location
9. Cancel Location
9. Cancel Location Ack

10. Delete Bearer Request 10. PCEF Initiated IP-CAN

Session Termination
10. Delete Bearer Response
(B)
11. Insert Subscriber Data
11. Insert Subscriber Data Ack.
12. Update Location Ack
13. Create Default Bearer Request
14. Create Default Bearer Request
15. PCEF Initiated IP-CAN
Session Establishment
(C)
16. Create Default Bearer Response
First Downlink Data
18. Attach Accept 17. Create Default Bearer Response

19. RRC Connection Reconfiguration

20. RRC Connection Reconfiguration Complete
21. Attach Complete
First Uplink Data
22. Update Bearer Request
23. Update Bearer Response
First Downlink Data
24. Update Location Request
25. Update Location Response

Default bearer is established when get attached, IP address is allocated to UE from network side
Bearer Concept Introduction

 Default Bearer
 a permanent valid bearer, this bearer is established when user get attached
 use the default APN contracted in HSS, PCC rule is the default rule configured on
PGW or assigned by PCRF, user address is assigned by P-GW
 it must be non GBR (Guaranteed Bearer Rate)bearer
 it is usually low bandwidth, low latency, and can be used to visit DHCP server and
IMS registration etc.
 Dedicated Bearer
 established according to the need of user layer or application layer after the
establishment of default bearer, can be initiated from network side or MS
 established on the base of default bearer, it is the bearer to the same PDN with
different QoS
 can be GBR or non GBR bearer
MME Fault Management
URL - http://65.1.11.65:2323/mme_51/client/#
 Function
 Fault management : deals with current NE alarm and related
functions.
 Real-time alarm monitor : monitor current alarms and history
alarms, at the same time, it has confirm, unconfirme, clearing and
query detail information functions
 History alarm query : query one day to three days history alarms.
 Notification query : query one day to three days notification.
 Custom query : query current alarms, history alarms and
notifications according to your setting conditions.
 Alarm rules setting : define alarm filtering rules and notification
filtering rules according to system type, location, alarm code, alarm
type and level etc.
MME Trace Management

 Trace management includes two parts:

 Signal trace

 Fail observation
Signal Trace

 Subscriber signal trace

Signal Trace

 Diameter Link Signal Trace

Fail Observer
Dynamic User Data Query

Login to EMS then go to Maintenance\CN Maintenance and click on PS then

click MME Subscribe Management to query user data.
EPS Mobility Management Status Introduction
EMM state model in UE EMM Deregistered Status
Detach,
MM context is not saved in MME
Attach Reject,
TAU reject, (unless to avoid AKA service flow
E-UTRAN interface switched off due to Non-3GPP handover, when attached)
All bearers deactivated
UE is not reachable, MME has no
position or route information of UE
EMM-DEREGISTERED EMM-REGISTERED

Attach accept
EMM Registered Status
EMM state model in MME
UE is reachable, MME know the
Detach,
position of UE ( position is located
Attach Reject,
TAU reject, to TA List)
All bearers deactivated UE has at least one activated PDN
connection( at least one default
EMM-DEREGISTERED EMM-REGISTERED
bearer context）
Attach accept UE has security context to save
TAU accept for a UE selecting
E-UTRAN from GERAN/UTRAN security information
EPS Connection Management Status Introduction

ECM state model in UE ECM state model in MME

RRC connection S1 connection

released released
ECM-IDLE ECM-CONNECTED ECM-IDLE ECM-CONNECTED

RRC connection S1 connection

established established

ECM-IDLE status ECM-CONNECTED Status

 There is no NAS signal connection between UE  There is signal connection between UE and
and MME； MME including RRC connection and S1-
 MME keep the TA List position information of MME connection;
UE；  MME keep the cell ID of UE;
 The context between UE and MME is not  The context between UE and MME is
synchronized synchronized
SAEGW Trace Management

Login to EMS client portal and click on CN Signal Trace to view trace management
window
SAEGW Trace Management

 Trace management includes three major parts:

 Subscriber Trace

 Data Trace

 Fail Observer
Signal Trace

 Subscriber signal trace

Signal Trace

 Data trace
Signal Trace

 Fail Observer
EMS Fault Management

Login to EMS client go to Fault\Alarm Monitoring

CDR Management

Login to EMS Client go to Maintenance\CN Maintenance and click

PSCG1CMB . Then click on CDR File Management to CDR management
window.
Basic Useful Commands

 MME:
 SHOW SVRSCTPSTAT ( show all established sctp link
status)
 SHOW USERDATA ( query user attached status)
 DETACH USER ( detach user manually from mme)
 SHOW MMEUSER STATS( show attached all users)
 SHOW ENODEBS ( show all Enodeb Informations)
 SHOW TA ( show all TA added in mme)
 SHOW EPC APN( show all apn added in mme)
 SHOW EPCHOST ( show epc host configuration)
Basic Useful Commands

 SAEGW:
 SHOW PGW AP ( show all configured apn)
 Show pgw basic-info test-d ( show basic apn
configuration)
 show pgw ipv4-pool-all ( show all ipv4 ip pools)
 show pgw service-ip-address ( show pgw service
interface ip address)
 show pgw subscriber-dynamic-info imsi
413120182000004 ( show pgw attached user status
infromation)