TMO18373 Issue3 2 E2E Architecture-Int-Protocols

@@SECT
Do not delete this graphic elements in here:
Section @@SECTION
@@SECTIONTITLE
Module @@MODULE
@@MODULETITLE
@@MODULEPARTNUMBER Issue @@MODULEEDITION
@@PRODUCT
@@COURSENAME
@@COURSEPARTNUMBER Issue @@COURSEEDITION
All Rights Reserved © Alcatel-Lucent @@YEAR

Module Objectives
Upon completion of this module, you should be able to:
 Draw the current PURPLE LTE network architecture with the associated IP
 addressing plan
 Explain the functions of each NE
 List the various 3GPP interfaces and associated protocols
@@SECTION · @@MODULE · 3 All Rights Reserved © Alcatel-Lucent @@YEAR

@@SECTIONTITLE · @@MODULETITLE
@@PRODUCT · @@COURSENAME
1 LTE network architecture

1.1 General LTE architecture
HSS
MME
PCRF
SGW
PDN
MME Internet
PGW
PDN
services
SGW
eUTRAN ePC
1.1 General LTE architecture [cont.]
MME MME MME MME MME
Tracking Area and Tracking Area List

A tracking area (TA) or a list of tracking areas (TAL), corresponds to a
‘geographical area' composed of a set of a few contiguous cells.
MME Pool Area is an area within which a UE may be served without need to
change the serving MME.
Serving GW Service Area is an area within which a UE may be served without
need to change the Serving GW.
A SGW Service Area is served by one or more SGW in parallel (“SGW pool”).

1.2 LTE Network Elements
 eUTRAN
 eNodeB – communicates with mobile device (User Equipment, UE) and ePC (Evolved
Packet Core)
 ePC – all IP – carries all types of traffic

 SGW (Serving Gateway)
 PGW (PDN Gateway)
 MME (Mobility Management Entity)
 PCRF (Policy Charging Rules Function)

2 LTE interfaces and protocols

2.1 LTE interfaces and protocols
MME
HSS
S6a
S10
MME PCRF
S1-MME
Uu
X2 S11 Gx
PDN
S1-U S5/S8 SGi
SGW PGW
eUTRAN ePC

2.1 LTE interfaces and protocols [cont.]
GERAN/UTRAN and eUTRAN interconnection
UTRAN/GERAN
MME SGSN
S3
S12
S11
S4
PDN
S1-U S5/S8 SGi
SGW PGW
eUTRAN ePC

2.1 LTE interfaces and protocols [cont.]
The control plane consists of protocols for control and support of the user plane
functions:
•controlling the E-UTRAN access connections, such as attaching to and detaching

from E-UTRAN,
•controlling the attributes of an established network access connection, such as

activation of an IP address,
•controlling the routing path of an established network connection in order to

support user mobility,
•controlling the assignment of network resources to meet changing user demands.

2.1.1 Stream Control Transmission Protocol
SCTP protocol is defined in RFC 2960, it was Initially
designed by SIGTRAN working group for signalling
transport.
difference with TCP resides in :

• multi-homing
• Multi-streaming
An SCTP packet is composed of a header and of

chuncks that can be either
• control chuncks
• user data chuncks
An association is defined with source and
destination ports, and a verification tag.
SCTP uses 4 way handshake connection setup.

2.2 S1-MME
S1-AP S1-AP
MME
SCTP SCTP
S1-MME IP IP
L2 L2
eUTRAN ePC L1 L1
eNodeB S1-MME
MME
S1 Application Protocol (S1-AP) is the Application Layer Protocol between the eNodeB
and the MME. S1AP services are divided into two groups, corresponding to two SCTP
streams
• Non UE-associated services related to the whole S1 interface instance between the
eNB and MME.
• UE-associated services related to one UE. In this case, the messages exchanged are
“UE associated S1-AP” messages

2.3 UE-MME interface using NAS protocol
NAS NAS
MME Relay
RRC S1-AP
RRC S1-AP
S1-MME PDCP PDCP SCTP SCTP
Uu IP IP
RLC RLC
MAC MAC L2 L2
eUTRAN ePC L1 L1 L1 L1
LTE-Uu S1-MME
UE eNodeB MME
The NAS protocol supports

• mobility management functionality
• user plane bearer activation, modification and deactivation
• Security functions : ciphering and integrity protection of NAS signalling
The purpose of the NAS Transport procedure is to carry UE – MME signalling over the S1
Interface. The NAS messages are transported in INITIAL UE MESSAGE, DOWNLINK NAS
TRANSPORT or UPLINK NAS TRANSPORT messages
The NAS messages are not interpreted by the eNB.
• LTE-Uu is The radio protocol of E-UTRAN between the UE and the eNodeB

2.4 S10 and S11 interfaces
MME MME GTP-C GTP-C GTP-C GTP-C
S10 UDP UDP UDP UDP
IP IP IP IP
L2 L2 L2 L2
S11 L1 L1 L1 L1
S10 S11
MME MME S-GW
MME
SGW
ePC
GPRS Tunneling Protocol is used for the control plane (GTP-C). This protocol tunnels
signaling messages between MMEs (S10) and between MME and SGW (S11).
GTP-C uses User Datagram Protocol (UDP) as transport protocol.

2.5 S6a interface
S6a Diameter Diameter
MME SCTP SCTP

HSS
IP IP
L2 L2
ePC L1 L1
S6a
MME HSS
Diameter protocol supports transferring of subscription and authentication data for

authenticating/authorizing user access to the evolved system between MME and HSS
(S6a).
The transmission of data between peers is realized using Attribute Value pairs (AVPs).
Each AVP consists of a data structure containing an attribute descriptor and its value.
Two diameter peers first establish a transport connection, a TCP session or a SCTP
association. When the connection is established, application messages can be
exchanged bidirectionnally (not a simple client/server model).
Device-Watchdog-Request (DWR) and Answers (DRA) are used to maintain the connection
when no information is exchanged.

2.6 S5/S8 interfaces on control plan
GTP-C GTP-C
UDP UDP
IP IP
S5/S8 L2 L2
SGW PGW L1 L1
S5 or S8
ePC S- GW P-GW
S5 provides user plane tunnelling and tunnel management between SGW and PGW.
S8 is the Inter-PLMN reference point providing user and control plane between the
Serving GW in the Visited PLMN and the PGW in the Home PLMN. S8 is the inter PLMN
variant of S5.
The PMIP-based S5, PMIP-based S8 interfaces are also available.

These PMIP interfaces supports Generic Routing Encapsulation (GRE) (instead of GTP-U)
for user plane traffic tunneling.
These interfaces are used when 3GPP and non 3GPP networks are interconnected.

2.7 charging interfaces
OFCS OCS
Rf Gy,Ro
Rf, Gz
SGW PGW
ePC
Offline Charging System (OFCS) transforms the charging information into CDR
(Charging Data Record) that are post-processed to generate bills and/or inter-
operator accounting/statistics.
Online Charging System (OCS) performs real-time credit control. It includes

transaction handling, rating, online correlation and management of subscriber
accounts. A direct interaction of the charging mechanism with
bearer/session/service control is required
Ro,Rf and Gy interfaces are based on Diameter protocol.

Gz interface is based on GTP’ protocol. GTP’ partially reuse GTP signalling plan, but
defines additional fields and messages.

2.8 Rx and Gx interfaces
IMS
P-CSCF
PCRF
Gx
PGW
Rx
Rx is used to exchange policy and charging related
Gxc information between P-CSCF on IMS network and
SGW ePC PCRF. This interface replaces Gq reference point.
Gx is defined between the PDN GW and the PCRF. It supports the procedures for Policy
and Charging rule transfer from the PCRF to the EPC. This interface is based on the
3GPP R7 Gx deﬁnition.
Gx and Rx interfaces are based on diameter protocol.

2.9 PCRF-PCRF (S9 interface)
 Used during Local breakout in roaming scenarios
 The protocol over the S9 interface is based on diameter
PCRF Home PLMN

PCRF
Gx
PGW
S9
Gxc
SGW ePC
Visited PLMN

2.10 S3 interface
ePC UTRAN/GERAN GTP-C GTP-C

MME SGSN UDP UDP
S3 IP IP
L2 L2
L1 L1
SGSN S3
MME
S3 interface is used Between MME and 2G/3G SGSN.

It supports user and bearer information exchange for inter-system mobility in idle or
active state.

2.11 X2-AP interfaces
MME
Radio
S1-MME Network X2-AP
Layer
Uu
SCTP
X2 S11
Transport IP
Network
Layer Data link layer
Physical layer
S1-U
SGW
eUTRAN ePC
X2-AP is used to transport signalling packets between eNodeBs.

X2-AP provides procedures related to user mobility, to exchange user context
information between eNodeB.
In addition, X2-AP can provide a way to signal load condition to neighboring eNodeB.

2.12 S1-U & S5/S8 interfaces for User plan
S1-U S5/S8
SGW PGW
eUTRAN ePC
Application
IP IP
Relay Relay
PDCP GTP-U
PDCP GTP-U GTP-U
GTP-U
RLC RLC UDP/IP UDP/IP UDP/IP UDP/IP
MAC MAC L2 L2 L2 L2
L1 L1 L1 L1 L1 L1
LTE-Uu S1-U S5/S8 SGi

a
UE eNodeB Serving GW PDN GW
GPRS Tunnelling Protocol for the user plane (GTP U) tunnels user data between eNodeB
and the SGW as well as between the SGW and the PGW.
LTE-Uu between the UE and the eNodeB are specified in TS 36.300.

2.13 S4 interface
ePC
UTRAN/GERAN
S4
SGW
SGSN
Application
IP IP
Relay Relay
SNDCP GTP -U
SNDCP GTP -U GTP -U GTP -U
LLC LLC UDP UDP UDP UDP
Relay BSSGP
RLC IP IP IP IP
RLC BSSGP
MAC MAC Networ k Network L2 L2 L2 L2

Service Service
GSM RF GSM L1bis L1bis L1 L1 L1 L1

RF
Um Gb S4 S5/S8 SGi
UE BS SGSN Serving G W PDN GW
GTP-U tunnels user data between SGSN and the SGW as well as between the SGW and
the PGW in the backbone network.
Protocols on the Um and the Gb interfaces are described in TS 23.060 [7].

2.14 S12 interface
Application
IP
IP
UTRAN/GERAN ePC Relay Relay GTP -U
PDCP
PDCP GTP -U GTP -U GTP -U
RLC RLC UDP/IP UDP/IP UDP/IP UDP/IP

s12
MAC MAC L2 L2 L2 L2
RNC SGW
L1 L1 L1 L1 L1 L1
Uu Iu S5/S8 SGi
UE UTRAN Serving GW PDN GW
GTP U tunnels user data between UTRAN and the SGW as well as between the SGW and
the PGW in the backbone network.
Protocols on the Uu interface are described in TS 23.060.
SGSN controls the user plane tunnel establishment and establish a Direct Tunnel between
UTRAN and SGW.

2.15 X2-U interfaces
MME GTP-U
S1-MME UDP
Uu IPv6 (RFC 2460)

and/or
IPv4 (RFC 791)
X2 interface is used to transport
X2 S11 Data link layer user data packets between
Physical layer eNodeBs during the time a
terminal moves from one source
eNodeB to a target eNodeB.
S1-U
SGW GTP-U protocol over UDP over IP

eUTRAN transports data streams on the
ePC X2 interface
• The DL data stream is used for DL data forwarding from the source eNB to the target
eNB.
• The UL data stream is used for UL data forwarding from the source eNB to the target
eNB.
Each data stream is carried on a dedicated transport bearer. The identity of a transport
bearer signalled in the RNL control plane consists of the IP address and the TEID of
the corresponding GTP tunnel, allocated by the target eNB

3 LTE IP Architecture

3.1 LAN and VLANs basic concepts
On Ethernet, a group of hosts sharing the same broadcast domain composes a LAN.
The communciation between hosts on the same LAN are Layer 2 based.
LAN LAN
Virtual LANs (VLANs) are a way to multiplex LANs on the same physical device.
802.1Q is a method to multiplex VLANs on the same physical link : vlan information (tag)
is explicitly carried in the frame
VLAN
VLAN
T T
VLAN VLAN

3.2 Backhauling Network concept
A Backhauling network is used on eUTRAN to transport the IP traffic from eNodeB to

ePC. The Network device installed on site to connect eNodeB to the network is called
a Cell Site Aggregator CSA
P-GW S-GW
MME PCRF
IP Endpoints
EPC
CSA Aggregator Applications
IMS
T1 HLR/HSS
2G Ethernet AAA
3G BS
Backhaul PoC
PoC
4G (Eth & T1 transport)
CSA
3G RNC Internet
Aggregator
BSC SGSN
BS 2G/3G/4G
CSA Core
Radio Access Backhaul Transport Core Domain

Domain Domain

3.2 Backhauling Network concept [cont.]
The traffic exchanged between eUTRAN and ePC will be carried over virtual lines called
pseudowires, as if a direct connection exists between the eNodeB and the Aggregator
network device.
IP Endpoints P-GW S-GW

MME PCRF EPC
CSA Aggregator Applications
IMS
T1 HLR/HSS
Ethernet AAA
PoC Backhaul PoC
(Eth & T1 transport)
CSA
Internet
CSA

3.3 LTE IP network overview
The eNodeB is physically connected on the CSA through a gigabit link, using 802.1Q. This
Ethernet connection carries Telecom VLAN and OAM VLAN. The eNodeB has one IP
address on each VLAN. NM
1 IP@ on subnet OAM
SGW
OAM TEL CSA POC
1 IP@ on subnet TELECOM
Agg.
The MME is connected to the ePC using 3 pairs of physical links

for redundancy purposes. One pair is dedicated to OAM, one PGW
S6a/s10
to S11/S1 interfaces and one to S6a/S10 interfaces.
OAM
S11/1
The MME has 1 IP address per interface.
SGW, PGW have dedicated interconnection links and one

loopback per interface. MME PCRF

3.4 GTP-U tunneling
Userplane traffic is tunneled between eNodeB and SGW, and between SGW and PGW
using GTP-U protocol.
TEID used is the SGW TEID provided by SGW

to MME during attach procedure.
UE IP srv IP | payload eNB IP SGW IP | TEID = 693
UE IP srv IP | payload
PDN
SRV
UE SGW PGW
SGW IP PGW IP | TEID = 261
SGW maintains EPS bearer context for the
UE that maps S1-U and S5 TEIDs.
Bearer-context :
S1U eNB data TEID : 1409

S1U SGW data TEID : 693
S5 PGW data TEID : 261
S5 SGW data TEID : 661

3.4 GTP-U tunneling [cont.]
Tunnels are unidirectionnal. TEID are different on Downlink and on Uplink.
Bearer-context :
S1U eNB data TEID : 1409

S1U SGW data TEID : 693
S5 PGW data TEID : 261
srv IP  UE IP | payload S5 SGW data TEID : 661
srv IP  UE IP | payload
SRV
PDN
UE
SGW PGW
SGW IP eNB IP | TEID = 1409 PGW IP SGW IP | TEID = 661

4 Purple example

4 Purple example
4.1 IP Architecture
10.10.10.1/30 port 1/1/1

10.10.10.5/30 port 1/1/2
NM
S1 10.10.10.81/28 S1 s11 loopback 10.10.10.20/32
OAM 10.10. S5 loopback 10.10.10.21/32
10.97/28 interface "system” 10.10.30.1/32
SGW
10.10.10.2/30 port 1/1/1

10.10.10.13/27 port 1/1/2
10.10.10.17/30 port 1/1/3
CSA Agg.
Gx loopback 10.10.10.23/32
S5 loopback 10.10.10.24/32
Sgi loopback 10.10.10.25/32
interface "system” 10.10.30.2/32
PGW
S6a/s10
OAM
S11/1
S1-MME 10.10.10.33/28 Address 10.10.10.65/28

S11 10.10.10.34/28
S6a 10.10.10.49/28
S10 10.10.10.50/28
Oam slot2 10.10.20.6/24 MME PCRF

Oam slot1 10.10.20.5/24
OAM Floating IP 10.10.20.7/24
CNFG Floating IP 10.10.20.8/24

Self-assessment on the Objectives
 Please be reminded to fill in the form

Self-Assessment on the Objectives
for this module
 The form can be found in the first part
of this course documentation

End of Module
@@MODULETITLE


TMO18373 Issue3 2 E2E Architecture-Int-Protocols

Uploaded by

Copyright:

Available Formats

You might also like

TMO18373 Issue3 2 E2E Architecture-Int-Protocols

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

TMO18373 Issue3 2 E2E Architecture-Int-Protocols

Uploaded by

Copyright:

Available Formats

@@SECT

Do not delete this graphic elements in here:

All Rights Reserved © Alcatel-Lucent @@YEAR

Upon completion of this module, you should be able to:

@@SECTION · @@MODULE · 3 All Rights Reserved © Alcatel-Lucent @@YEAR

@@SECTION · @@MODULE · 7 All Rights Reserved © Alcatel-Lucent @@YEAR

MME MME MME MME MME

Tracking Area and Tracking Area List

@@SECTION · @@MODULE · 9 All Rights Reserved © Alcatel-Lucent @@YEAR

 ePC – all IP – carries all types of traffic

@@SECTION · @@MODULE · 10 All Rights Reserved © Alcatel-Lucent @@YEAR

@@SECTION · @@MODULE · 11 All Rights Reserved © Alcatel-Lucent @@YEAR

@@SECTION · @@MODULE · 12 All Rights Reserved © Alcatel-Lucent @@YEAR

@@SECTION · @@MODULE · 13 All Rights Reserved © Alcatel-Lucent @@YEAR

•controlling the E-UTRAN access connections, such as attaching to and detaching

•controlling the attributes of an established network access connection, such as

•controlling the routing path of an established network connection in order to

•controlling the assignment of network resources to meet changing user demands.

@@SECTION · @@MODULE · 14 All Rights Reserved © Alcatel-Lucent @@YEAR

difference with TCP resides in :

An SCTP packet is composed of a header and of

@@SECTION · @@MODULE · 15 All Rights Reserved © Alcatel-Lucent @@YEAR

@@SECTION · @@MODULE · 16 All Rights Reserved © Alcatel-Lucent @@YEAR

The NAS protocol supports

The NAS messages are not interpreted by the eNB.

@@SECTION · @@MODULE · 17 All Rights Reserved © Alcatel-Lucent @@YEAR

MME MME GTP-C GTP-C GTP-C GTP-C

S10 UDP UDP UDP UDP

GTP-C uses User Datagram Protocol (UDP) as transport protocol.

@@SECTION · @@MODULE · 18 All Rights Reserved © Alcatel-Lucent @@YEAR

S6a Diameter Diameter

MME SCTP SCTP

Diameter protocol supports transferring of subscription and authentication data for

@@SECTION · @@MODULE · 19 All Rights Reserved © Alcatel-Lucent @@YEAR

The PMIP-based S5, PMIP-based S8 interfaces are also available.

@@SECTION · @@MODULE · 20 All Rights Reserved © Alcatel-Lucent @@YEAR

Online Charging System (OCS) performs real-time credit control. It includes

Ro,Rf and Gy interfaces are based on Diameter protocol.

@@SECTION · @@MODULE · 21 All Rights Reserved © Alcatel-Lucent @@YEAR

Gx and Rx interfaces are based on diameter protocol.

@@SECTION · @@MODULE · 22 All Rights Reserved © Alcatel-Lucent @@YEAR

 Used during Local breakout in roaming scenarios

 The protocol over the S9 interface is based on diameter

PCRF Home PLMN

@@SECTION · @@MODULE · 23 All Rights Reserved © Alcatel-Lucent @@YEAR

ePC UTRAN/GERAN GTP-C GTP-C

S3 interface is used Between MME and 2G/3G SGSN.

@@SECTION · @@MODULE · 24 All Rights Reserved © Alcatel-Lucent @@YEAR

X2-AP is used to transport signalling packets between eNodeBs.

@@SECTION · @@MODULE · 25 All Rights Reserved © Alcatel-Lucent @@YEAR

RLC RLC UDP/IP UDP/IP UDP/IP UDP/IP

LTE-Uu S1-U S5/S8 SGi

LTE-Uu between the UE and the eNodeB are specified in TS 36.300.

@@SECTION · @@MODULE · 26 All Rights Reserved © Alcatel-Lucent @@YEAR

LLC LLC UDP UDP UDP UDP

MAC MAC Networ k Network L2 L2 L2 L2

GSM RF GSM L1bis L1bis L1 L1 L1 L1

UE BS SGSN Serving G W PDN GW