²

1
 Contents

LTE EPC Basics

EPC IMS Interaction
EPC Mobility
EPS Bearers
IMS Basics
Interfaces
 Evolved Node B (eNb)
• The eNB hosts the following functions:
– Radio Resource Management:
• Radio Bearer Control (establishment/maintenance/release of MME
Radio Bearers).
• Radio Admission Control. S1-MME
• Connection Mobility Control
LTE-UE LTE-
• Packet scheduling.
Uu
– IP header compression and encryption of user data stream. S1-U
– Selection of an MME at Initial UE attach. This function is
enabled when S1 Flex is implemented.
SGW
– Routing of User Plane data towards SGW.
– Scheduling and transmission of paging messages (originated
from the MME). X2
– Scheduling and transmission of broadcast information
(originated from the MME or O&M).
– Measurement and measurement reporting configuration for
mobility and scheduling.
eNB
 Mobility Management Entity

The MME host functions:

– the NAS connection with the UE. SGSN
– Paging subscribers in ECM-IDLE state. MME
– Tracking Area list management. S3
– PDN GW and SGW selection. HSS
S6a
– MME selection for handovers with MME change. S10
– Inter CN node signaling and SGSN selection for mobility
between 3GPP access networks.
– Roaming control (S6a interface toward HSS). MME SGs
S1-
– User authentication and authorisation support.
MME S11
– Bearer management functions.
– Lawful Interception of signaling traffic.

eNB MSS

SGW
 Serving Gateway (SGW)
The SGW host functions:
– The local Mobility Anchor point for inter-eNodeB handover.
– Sending of one or more "end marker" to the source eNB,
source SGSN or source RNC immediately after switching the
SGSN
path during inter-eNB and inter-RAT handover, especially to
assist the reordering function in eNB. S4
– Mobility anchoring for inter-3GPP mobility. RNC
S1
– ECM-IDLE mode downlink packet buffering and initiation of S11
2
network triggered service request procedure. MME
– Lawful Interception.
Gx
– Packet routing and forwarding. c
– Transport level packet marking in the uplink and the SGW
S1-U
downlink, e.g. setting the DiffServ Code Point, based on the S5/S PCR
QCI of the associated EPS bearer. 8 F
– Accounting for inter-operator charging. For GTP-based S5/S8,
the Serving GW generates accounting data per UE and bearer. eNB
– Interfacing OFCS according to charging principles
PGW
 Packet Data Network Gateway
The PGW host functions:
PDN
– packet filtering.

– Packet screening (firewall).

– Lawful Interception. S4
– UE IP address allocation.
Gx
– Transport level packet marking in the uplink and downlink. S2a
HSGW PCR
– Accounting for inter-operator charging. F
– UL and DL service level charging.
PGW
S5/S8
– Interfacing through OFCS S2b

– UL and DL service level gating control.

– UL and DL service level rate enforcement as defined.

– UL and DL rate enforcement based on APN-AMBR.

SGW
ePDGW
– DL rate enforcement based on the accumulated MBRs of the
aggregate of SDFs with the same GBR QCI.

– DHCP functions
 Home Subscriber Server

• The HSS host functions:

• User Identification, Numbering and addressing
information;
• User Security information: Network access control
information for authentication and authorization;
• User Location information at inter-system level: the HSS
supports the user registration, and stores inter-system
location information, etc.;
• User profile information.
• HSS utilizes DIAMETER protocol to support LTE/EPC.

• The HSS can be accessed by the MME via S6a interface.

S6
a

MME
HSS
 Contents

LTE EPC Basics

EPC IMS Interaction
EPC Mobility
EPS Bearers
IMS Basics
 SGi Interface
SGi Interface

•Interface used by the PDN GW to send and receive data to and from the external
data network or Service Platform
• It is either IPv4 or IPv6 based
• This interface corresponds to the Gi interface in 2G/3G networks
• Standardized in 3GPP TS 29.061: “Interworking between the Public Land Mobile
Network (PLMN) supporting packet based services and Packet Data Networks (PDN)

GRE, L2TP, IPSEC …

TCP/UDP
PGW IP
Packet Data
Network
SGi
 Rx Interface

•Interface between PCRF and the external PDN network/operators IMS (in general, towards
the Service Domain)
•Standardized in 3GPP TS 29.214: “ Policy and Charging Control over the Rx reference point
(release 8)”

Rx Application

DIAMETER

SCTP
PCRF IP P-CSCF

Rx
 Contents

LTE EPC Basics

EPC IMS Interaction
EPC Mobility
EPS Bearers
IMS Basics
Interfaces
 Radio Resource Control (RRC)
RRC Connection Establishment

RRC_CONNECT
RRC_ IDLE

RRC Connection Release

RRC-IDLE RRC-CONNECTED
• No signalling connection between the UE and the • UE has an E-UTRAN RRC connection.
E-UTRAN. • UE has context in E-UTRAN.
• UE Receives system information and listens for • E-UTRAN knows the cell which the UE belongs to.
Paging.
• Network can transmit and/or receive data to/from UE.
• Mobility based on PLMN selection.
• Mobility based on handovers
• No RRC context stored inRACH procedure used
on RRC connection establishment. • UE reports neighbour cell measurements.
• the eNB
 EPS Mobility Management (EMM)
Attach Accept, TAU Accept

EMM_
EMM_
REGISTERED
DEREGISTERED
Detach, Attach Reject, TAU Reject

EMM-DEREGISTERED EMM-REGISTERED
•Location of UE is unknown for the MME. •MME holds location information for the UE at least to
•MME may keep some UE context when the UE the accuracy of a tracking area.
moves to this state. •In this state the UE performs TAU procedures,
•Successful TAU procedures lead to transition responds to paging messages and performs the
to EMM-REGISTERED. service request procedure if there is uplink data to be
sent.
 EPS Connection Management (ECM)
S1 Connection Establishment

ECM_CONNECTED
ECM_IDLE

S1 Connection Release

ECM-IDLE ECM-CONNECTED
•no NAS signaling and there is no context for •NAS signaling connection which is provided in the
the UE held in the E-UTRAN. form of a RRC connection and an S1 connection.
•The location of the UE is known in the tracking •The location of the UE is known in cell level.
area level •Mobility is managed by handovers.
•Mobility is managed by tracking area updates.
 EPS Session Management (ESM)

First EPS Bearer Established

ESM_INACTIVE ESM_ACTIVE

Last EPS Bearer Released

 EMM & ECM States Transitions
Registration
EMM-REGISTERED
ECM_CONNECTED

Deregistration/PLMN change

New
EMM- Inactivity traffic
DEREGISTERED or
ECM_IDLE TAU
Power ON

EMM-REGISTERED
ECM_IDLE
Timeout of PTAU
 NAS States
Registration
Service Request
TA update, paging …
EMM-Deregistered, EMM-Registered, EMM-Registered,
ECM-Idle ECM-Idle ECM-Connected
ESM-Inactive ESM-Active ESM-Active

RRC: Null RRC: IDLE RRC: CONNECTED

No RRC or EPC Context EPC Context RRC & EPC Context

Power On
IMSI Identifier S-TMSI, TA-ID, IP Address S-TMSI, TA-ID, IP Address

UE Unknown UE Known at TA Level UE Known at Cell Level

PLMN Selection TA Update Handovers

No Data Transfer DRX on DL UL/DL Data Transfer

PTAU Timeout – Inactivity
out of area
Deregistration
 Contents

LTE EPC Basics

EPC IMS Interaction
EPC Mobility
EPS Bearers
IMS Basics
Interfaces
 EPS bearer identity (EBI)

– uniquely identifies an EPS bearer for one UE accessing via E-UTRAN

– allocated by the MME

– one to one mapping between EPS RB Identity and EPS Bearer Identity is made by E-UTRAN

– E-RAB ID value is the same as the EPS Bearer ID value

– The EBI is coded in 4 bits: values from 0 to 4 are reserved for future use.
 EPS Bearer and SDF
PDN Connection
The IP Connection between a UE and a PDN
UE: represented by UE IP address
PDN: represented by APN
EPS Session
The same meaning as PDN Connection
Incorporates one or more EPS Bearers, and exists as long as UE IP address is
established
EPS Bearer
A Logical transport channel(transmission path) between the UE and the P-GW for
transporting IP traffic with a specific QoS
Each EPS Bearer is associated with a set of QoS parameters that describe the
properties of the transport channel
All EPS Bearers belonging to one PDN connection share the same UE IP address
An EPS bearer identity uniquely identifies an EPS bearer for one UE. The EPS Bearer
Identity is allocated by the MME.
 EPS Bearer and SDF
Default Bearer
The EPS Bearer Which is first established for a new PDN connection and remains
established throughout the lifetime of the PDN connection
Always Non-GBR Bearer

Dedicated Bearer
Additional EPS Bearer that may be activated for a PDN connection
May be activated on demand
Either GBR Bearer of Non-GBR Bearer

SDF(Service Data Flow)

A IP flow(packet flow) or an aggregate set of IP flows corresponding to a service, which is
identifiable using IP/TCP/UDP headers of the packets
One SDF can be given one QoS treatments in P-GW (PCC rule by PCRF)
Multiple SDFs can be multiplexed onto the same EPS Bearer by including multiple
uplink/downlink packet filters in the UL/DL TFT
EPS Bearers
 EPS Bearer sections

MME SAE-GW
LTE-Uu S1-U S5/S8 SGi PDN

End-to-End Service

EPS Bearer External Bearer

Radio Bearer S1 Bearer S5/S8 Bearer

E-UTRAN EPC PDN

 Default Bearer Concept

– A default bearer is created for each access point.

– Each UE that is attached to the LTE network has at least one bearer available, that is called the default
bearer.

– Its goal is to provide continuous IP connectivity towards the EPC

– From the QoS point of view, the default bearer is normally a quite basic bearer

– If an specific service requires more stringent QoS attributes, then a dedicated bearer should be
established.

– A UE can get 3 default bearer in the same time.

– This concept is not used in 2G/3G networks.

 QCI Concept

3G

LTE/EPS
 QoS Class Identifier (QCI)
Priorit
QCI Guarantee Delay budget Loss rate Application
y

1 GBR 2 100 ms 1e-2 Voice Packet

2 GBR 4 150 ms 1e-3 Video call

3 GBR 5 300 ms 1e-6 Streaming

4 GBR 3 50 ms 1e-3 Real time gaming

5 Non-GBR 1 100 ms 1e-6 IMS signalling

6 Non-GBR 6 100 ms 1e-3 Interactive gaming

7 Non-GBR 7 300 ms 1e-6

TCP protocols : browsing,
8 Non-GBR 8 300 ms 1e-6
email, file download
9 Non-GBR 9 300 ms 1e-6
 VoLTE Call Bearers

Default EPS Bearer with QCI 5 P-CSCF

used for SIP Signalling

IMS
Default EPS Bearer with QCI 1 BGF
used for Voice Packet
PGW
 Contents

LTE EPC Basics

EPC IMS Interaction
EPC Mobility
EPS Bearers
IMS Basics
Interfaces
IMS Basic Idea

29
IMS Basic Concept

30
 Access Support
• IMS supports different access types.
• IMS Access networks are called IP Connectivity Access Network (IP-CAN).
• IP-CAN provides the multimedia signaling connection as well as the bearer
connection.

2G/3G Core

LTE Core

WLAN/WIMAX Core
IP Multimedia
IP-CAN Subsystem
Fix Core

xDSL Core
IMS Architecture

32
 IMS Functionalities

Session management and

e.g. CSCFs …
routing functions
Databases functions e.g. HSS,SLF …

Services functions e.g. AS, MRFC, MRFP …

e.g. BGCF, MGCF, IMS-
Interworking functions
MGW, SGW …
e.g. PCRF, SEG, IBCF,
Support functions
TrGW, LRF ...
Charging functions e.g. CGF, CDF, OCS, BS …
 Proxy-CSCF
• Statfull SIP proxy server.
• Entry point to IMS cloud from any Access network.
• All the signaling messages goes through it.
• contains the AF that is a logical element for the PCC concept
• Establishes a number of IPsec security associations toward the IMS terminal, and Perform the integrity protection
• Asserts the identity of the user to the rest of the nodes in the network.
• Verifies the correctness of SIP requests
• Compression and decompression of SIP signaling messages.
• It includes a PDF that authorizes bearer resources.
• Generates charging information
• Collocated with the BCF PDF

Rx

Gm Mw
P-CSCF I/S-CSCF
IMS Client IP-CAN Ia

BGF
 Interrogating-CSCF
• Statless SIP proxy server.
• First Contact Point in home network.
HSS AS
• Performs S-CSCF and AS selection.
• Performs network topology hiding (THIG).

ISC,
Ma
Cx

Mw Mw

P-CSCF I-CSCF S-CSCF

Dx

SLF
 S-CSCF Selection
HSS

UAA
UAR (S-CSCF
Capabilities)

SIP: Register SIP: Register

I-CSCF S-CSCF

S-CSCF Capability Priority Weight Random

Set Number
S-CSCF A 1;2;3 1 100 12
Example:
S-CSCF Capabilitites: S-CSCF B 2;3 2 50 45
2;3 S-CSCF C 1;3;4 1 70 98

S-CSCF D 1;2;3;5 2 100 23

 Serving-CSCF
• The S-CSCF is the central node of the IMS cloud.
• Statefull SIP proxy providing session control.
• SIP registrar. AS MRFC
• Performs subscriber authentication
• Download user profile from HSS.
• Allocated to IMS user during one registration.
• Invokes the AS using Initial filter criteria.
Mr
BGCF
ISC
HSS Cx

Mi

Mw Mj

P/I-CSCF S-CSCF
Mg
Dx
MGCF

SLF
 Emergency-CSCF
• Handles emergency calls
• Can be collocated with S-CSCF
• Always exist in the same network as the P-CSCF
LRF PSAP
• Retrieves user location from the LRF
• can perform offline charging
• Selects the PSAP according to the user location

Le
BGCF
Ml
Cx
HSS
Mi

Mw Mj

P-CSCF E-CSCF
Mg
Dx
MGCF

SLF
 Emergency call handling
LRF

P-CSCF User Location?

User Location
Emergency
Numbers E-CSCF
911
SIP: INVITE SIP: INVITE
112
(TO:911) 110 (TO:911, PANI: User Location)
197
…
SIP: INVITE

MGCF
User Location? User Location
SIP: INVITE
PSAP

CLF
HSS Apperance

40
HSS Functionalities

41
Data in the HSS

42
 MRFC
• The Media Resource Function Control (MRFC) controls the MRFP.
• The MRFC can reside in the AS or in S-CSCF.
• The MRFC communicate with MRFP over the Mp’ (H.248) interface, as defined by 3GPP TS
23.218.
• Over the Mr’ interface, MRFC connects to any Media Server, to provide advanced MRF
services, such as video conferencing. The Mr’ interface is compliant with 3GPP TS 24.880.
• MRFC is also connected to External Ringtone Servers (ERS) to provide Customized Alerting
Tone (CAT) services.
• Complying with GSMA PRD IR.92 and IR.94, MRFC provides the following functions:
• announcements
• tones
• transcoding and conference services

MRFC SIP/
Mr SIP-I

S-CSCF
ERS
Mr’ Mp’

MRFP
MS
43
 MRFP
• Media server architecture in IMS consists of two entities MRFC and MRFP. These two entities
are connected via the Mp reference point. Over this reference point the MRFC is able to ask
MRFP to do the following things:
 play tone to user or number of users;
 play announcement to user or number of users e.g. ‘person you try to reach is
currently out of coverage or not able to receive multimedia communication’;
 generate speech output from text or annotated text input;
 record audio or multimedia stream(s) and store it into a file. The function can be used
in some services, such as the voice mail box service, conference service, etc;
 collect and report dialed DTMF digits e.g. to get PIN code for voice mail box;
 perform automatic speech recognition and report the results;
 play synchronized audio and video media streams to the user. The function can be
used in the services, such as multimedia announcement, multimedia mail box service,
etc;
 provide conferencing transport plane capabilities for audio and multimedia
conferencing service;
 transcoding of audio and video streams.

Mp
H.248
MRFC MRFP
 Application Server
• The main IMS application server roles
 Multimedia Telephony Application Server (MMTEL-AS)
 Service Centralization and Continuity Application Server (SCC-AS)
 IP Short Message Gateway (IP-SM-GW)
 IP Multimedia Service Switching Function (IM-SSF)
 Media Resource Function Controller (MRFC)

HSS

Sh

ISC ISC,
Ma
S-CSCF AS I-CSCF
Ut

UAC
 MMTel AS Functions
• MMTel AS role manages IMS sessions for voice and video.
• MMTel AS is involved in executing a bundle of services, including supplementary services, network
services, and regulatory services.
• MMTel AS is also responsible for the management of subscriber data and subscriber services.
• MMTel AS triggers the integrated IM-SSF role to:
 communicate with the SCP to provide intelligent network (IN) services.
 generate session and event based online charging data.
• MMTel supports also offline charging.
• User controlled service management is also realized in the MMTel AS: the MMTel AS’s in-built XCAP Server
function allows subscriber service modification to centralized repository from Ut/XCAP capable terminals.

Supplementary services
•
•
Calling Line Identity Presentation & Restriction
Connected Line Identity Presentation & Restriction
MMTel AS
• Call Forwarding Unconditional
•
•
Call Forwarding on Not Reachable, No Reply, Busy
Call Deflection
SCC AS
• Subscriber Controlled Barring categories
• Operator Determined Barring categories IP-SM-GW
• Supplementary Service control with facility codes and Ut interface
• Anonymous Call Rejection
• Private Numbering Plan IM SSF
• Malicious Call Identifier
• Call Hold, Call Resume and Call Switching
• Call Transfer (Explicit, Attended) MRFC
• Call Waiting (client)
•
•
Do not disturb (client)
Multiparty/3-Party voice call Application Server
 MMTel AS Functions
Network services IN services from existing SCP
• Attribute analysis (charging, routing, end of selection, pre-analysis etc.) • Originating prepaid service
• Operator Controlled Call Forwarding (OCCF) • Terminating prepaid service
• Charging related functions including different tariffs that will be applied for the call • Group prepaid service
• Dynamic charging based on call detail records (CDRs) • Virtual private network service
• National and operator-specific numbering plans • A-validation service
• Freephone service
• Hunting group service
Supplementary services • Originating call screening service
• Originating call announcement service
• Calling Line Identity Presentation & Restriction • Premium rate service
• Connected Line Identity Presentation & Restriction
•
•
Call Forwarding Unconditional
Call Forwarding on Not Reachable, No Reply, Busy
Other services
• Call Deflection
• E.164 and SIP URI addressing
• Subscriber Controlled Barring categories
• Family number / Multi-SIM (Sequential/Parallel alert)
• Operator Determined Barring categories
• Single/Dual numbering
• Supplementary Service control with facility codes and Ut interface
• Mobility Management
• Anonymous Call Rejection
• Voice & Video Mail Interworking
• Private Numbering Plan
• Tones & Announcements
• Malicious Call Identifier
• Selective Ringback Tone
• Call Hold, Call Resume and Call Switching
• Missed Call Log
• Call Transfer (Explicit, Attended)
• Data/modem call
• Call Waiting (client)
• T.30 / T.38 FAX
• Do not disturb (client)
• DTMF
• Multiparty/3-Party voice call
• CNAP/CNAM
• Music on Hold
Regulatory services • Video Telephony
• HD Voice & Video
• Number portability • MMTel services
• Carrier Pre-selection  Voice (IR.92)
• Lawful Interception  Video (IR.94)
 Video & image share
 P-2-P chat, file transfer (MSRP)
 MMTel AS interfaces
• MMTel AS connects to the S-CSCF over ISC interface. ISC interface connectivity uses the SIP
protocol.
• Over the Lightweight Directory Access Protocol (LDAP) interface, the MMTel AS, as an LDAP
client, connects to any external LDAP Directory server, to access VoLTE subscriber profile.
• Ut interface used between UAC and XCAP Server. The XCAP server runs on the MMTel.
• Over the Sh interface The MMTel AS connects to the HSS-FEs.
• The MMTel AS role of the AS connects to the HLR over the MAP-D interface.
• Ma interface used between MMTel AS and I-CSCF.

HLR HSS
UDR

Sh
MAP-D LDAP

ISC,
MMTel AS Ut
Ma
I/S-CSCF Application Server UAC
 SCC AS
• 3GPP defined the Service Centralization and Continuity Application Server (SCC AS) role, in
order to :
- Manage continuous services across LTE and CS domain (SRVCC (R8) / eSRVCC (R10).
- Centralize service execution in the IMS (T-ADS/Homing).
• The SCC AS role follows and fulfills the principles to offer IMS Centralized Services (ICS), as
outlined in GSMA PRD IR.64, and enables service continuity and service centralization, as
specified respectively in 3GPP TS 24.237 and 3GPP TS 24.292.

MMTel AS
• Session Continuity
SCC AS
• Service Centralization
IP-SM-GW
IM SSF
MRFC
Application Server
49
 SCC AS interfaces
• The Bi interface used to connect SCC AS to IP billing domains in order to generate SIP
charging data for offline purposes, in a non-Diameter charging architecture. Bi uses FTP pull
or GTP (immediate CDR) push interfaces.
• The SCC AS uses the Bc interface to connect to CS billing domains in order to generate CS
charging data for online purposes, in a non-Diameter charging architecture.
• Over the Rf interface, the SCC AS as Charging Trigger Function (CTF), connects to Charging
Data Function (CDF), to provide diameter based IMS offline charging.
• Over the Ro interface, , the SCC AS as CTF, connects to Online Charging System, to provide
diameter based IMS online charging.

BC HSS CDF

Sh
Bi, Bc Rf
OCS
ISC,
SCC AS Ro
Ma
I/S-CSCF Application Server

50
 IP-SM-GW
• The IP-SM-GW role of the AS delivers the SMS over IP solution, as specified by
3GPP.
• This AS role enables centralized service execution by acting as a “router” for
homing terminating messages in a central location, which is the IP-SM-GW.
• It also functions as gateway for the purposes of handling terminating domain
selection, performing the hunting logic, and executing message delivery across the
various access domains.

SMSC
MAP-E or Gd
IP-SM-GW SMS-GMSC
SMS-IWMSC
51
 IM-SSF
• The AS implements the Call Control Function (CCF) and the Service Switching Function (SSF)
functional entities in the IM-SSF, which enable the IN service logic by connecting to the
Service Control (SCF) function of the Service Control Point (SCP).
• The AS IM-SSF supports connectivity to the SCP over the CAP and the vendor specific INAP
interfaces, and support the following protocols:
 CAMEL Phase 4 (including all previous CAMEL phases)
 INAP

IMS-SSF SCP
CAP or INAP

CCF SSF SCF

52
 AS interfaces summury
SCC AS – DNS
OCS
VMSC/GMSS
AS – HLR DNS P-LIG
CAP/
INAP X1; X2
SCC AS – MAP IMS HSS
HLR
Sh

IP-SM-GW
– HLR AS DIAMETER
Ro
OCS

IP-SM-GW OFCS
– SMSC
SIP Mp
Ut (H,248)
(XCAP) Mr Ma ISC
SCC AS – SCC AS – MRFP
UE MRFC
I-CSCF S-CSCF
53
 Breakout Gateway Control
Function
• BGCF or Break Out Gateway Control Function
• The BGCF is necessary for the establishment of multimedia session between the IMS
and the CS domain.
• In case the S-CSCF is unable to route the SIP Invite message to a terminating I-CSCF, it
forwards it for a session setup to the BGCF. The BGCF than selects a media gateway
control function.
S-CSCF BGCF

BGCF Mx
Mi

Mg Mj

Mj

MGCF
 Breakout Gateway Control
Function
If the breakout happens in the same network, then the BGCF selects a Media Gateway
Control Function (MGCF) to handle the session further. If the breakout takes place in
another network, then the BGCF forwards the session to another BGCF in a selected
network.

S-CSCF ENUM

SIP INVITE (IMPU: sip:[email protected]

Or IMPU: tel:E.164)

ENUM: SIP:[email protected]
 MGCF
• The MGCF provides the control plane for the interconnection point between the packet and
circuit switched networks. It is the signaling unit of the MGW to control this unit and to
convert signaling messages between circuit switched and packet switched networks.
• MGCF convert SIP signalling to ISUP/BICC signalling and control the IMS-MGW.
• The controlling of the MGW is done via MEGACO the media gateway control protocol.
• The MGCF acts as an end point for SIP signaling. so, it negotiates media parameters together
with the IMS UE and, similarly, negotiates media parameters together with the CS entity (e.g.,
with an MSC server)

BGCF
Mj
MGCF SGW MSS
S-CSCF
Mj
Mg
SIP, ISUP or BICC

Mn Mc
H.248 H.248

IMS-MGW MGW
 Signalling Gateway
When a SIP session request hits the MGCF it performs protocol conversion between SIP and ISUP,
or BICC and sends a converted request via the Signalling Gateway (SGW) to the CS CN. The SGW
performs signalling conversion (both ways) at the transport level between
the IP-based transport of signalling (SIGTRAN) and SS7 based transport of signalling.
The SGW does not interpret application layer (e.g., BICC, ISUP) messages.

SIP or ISUP over ISUP over TDM

SIGTRAN
MGCF MSS
SGW
Mj
SIP, ISUP or BICC

SIP ISUP ISUP

M3UA MTP3
TCP/UDP M3UA MTP3
SCTP MTP2
SCTP MTP2
IP IP IP L1 MTP1
MGCF SGW MSS
 IMS-MGW
• The IMS-MGW provides the user-plane link between CS CN networks and the IMS.
• It is controlled by a MGCF. MGW can also be used to connect IMS with ISDN/PSTN networks
• A MGW provides functionality and resources to perform:
 switching
 Routing
 transport layer conversion
 media stream processing (e.g. codec conversion)
BGCF

BCF Mj
MGCF SGW MSS
S-CSCF Mj
Mg
SIP, ISUP or BICC

Ia Mn Mc
H.248 H.248 H.248

BGF IMS-MGW MGW

 Session Border Controller
In general, SBC components are not incorporated in a single piece of equipment but are
distributed. The signaling controller is collocated with the P-CSCF and controls a media proxy at
the edge of the access network.
SBC is divided to two main functions:
• BCF: controls the access of signaling messages to the IMS core network, and manipulates the
contents of these messages.
• BGF: controls the access of media packets to the network.

BCF
SBC
BGF
 ENUM
ENUM (E.164 Number to URI Mapping) translates telephone numbers into Internet
addresses. You can dial a telephone number and reach a SIP, H.323 or any other
Internet Telephony user.
In IMS, ENUM translates an IMPU containing a telephone number into an IMPU that
don’t contain a telephone number.

ENUM: SIP:[email protected] ENUM: TEL:E164

ENUM: SIP:[email protected] ENUM: SIP:[email protected]

ENUM ENUM
 IBCF
The Interconnection Border Control Function (IBCF) provides application specific functions at the
SIP/SDP protocol layer to perform interconnection between two operator domains, e.g. it:
 enables communication between IPv6 and IPv4 SIP applications,
 network topology hiding
 controlls transport plane functions,
 screens of SIP signalling information,
 selecting the appropriate signaling interconnect (TrGW)
 generation of charging data records.

I-CSCF
IBCF
IBCF

P-CSCF
IBCF
S-CSCF
Visited network Home network Other network
 Diameter Routing Agent
• Diameter Routing Agent The DRA consists of 2 functions:
 the Edge Agent, which protects the operator’s NNI (Network-Network Interface) in case
of roaming subscribers
 the Diameter Load Balancer, which balances the Diameter traffic, e.g. between different
HSS-FEs according to their performance capabilities. It also simplifies the network
architecture (not requiring a fully meshed network) thus improving the scalability and
manageability of the network.
AS
AS

HSS
HSS I/S-CSCF
I/S-CSCF

Fully meshed
network
 DRA-Edge Agent
• The Edge Agent is used to secure the traffic between different peer networks. A common way
to connect peer networks makes use of the IPX (IP eXchange) network. IPX is an isolated
network offered by several IPX operators. The Edge Agent operates at the edge to the IPX and
supports the following functions:
 Network Security (IPsec, DoS Protection, Traffic separation, Topology Hiding,
 Roaming Agreement Support.
 Admission Control.
 Service Level Agreement (SLA)
 Accounting
I/S-CSCF
AS
HSS

I/S-CSCF
IPX Peering
DRA-LB
Operator
HSS DRA-EA

I/S-CSCF
PCRF
 DRA-Load Balancer
• The DRA can be used in the operator’s network as Diameter Load Balancer to simplify the
network topology. It improves the network scalability, availability and maintainability. For
example, HSS-FEs can be included and taken out of operation without impacting other network
components. In the geo-redundant mated pair configuration the DRA achieves > 99.999%
availability.
• Due to its flexibility to configure the protocols (IPv4v6 dual stack; TCP, SCTP) that are to be
applied on the link level, the DRA is able to simplify the multi-vendor deployments as well as
the network upgrades.

•Destination Realm
•Destination Host DRA-LB
•Origination Realm
•Origin Host Weighted
•Application ID Load-balancing
•IMSI range
•Session-ID
 Policy and Charging Rule
Function
• The PCRF hosts the following functions:
– Binding mechanism, associates a service data flow
to the EPS bearer deemed to transport the service
PCRF
data flow. Rx
Gx
– Reporting or
S7
– Credit Management
SGi IMS/PDN
– Event Trigger

– Policy Control PGW

– Service (data flow) prioritisation and conflict

handling

– Standardised QoS characteristics

– Termination Action

– Handling of packet filters.

65
 Contents

LTE EPC Basics

EPC IMS Interaction
EPC Mobility
EPS Bearers
IMS Basics
Interfaces
 EPC Interfaces
Interface Entities Protocol
S1-MME eNB – MME S1-AP

S1-U eNB – S-GW GTP-U

S11 MME – S-GW GTP2

S5 S-GW – P-GW GTPv2-C/GTP-U; PMIP

S10 MME - MME GTP-C

S6a MME - HSS Diameter

Gx P-GW - PCRF Diameter

SGi P-GW – External PDN GTP; Diameter; Radius

 IMS Interfaces

Interface Entities Protocol

Gm UE – P-CSCF SIP

Rx P-CSCF – PCRF Diameter

Cx S-CSCF - HSS Diameter

Mw CSCF – CSCF SIP

Mm I/S-CSCF – External PDN SIP

 CS Interfaces

Interface Entities Protocol

Mc MSS-MGW H.248

Nc MSS-MSS ISUP/BICC/SIP-I

Nb MGW-MGW TDM/AAL2/RTP/RTCP

Mn MGCF-IMS-MGW H.248

Mp MRFC-MRFP H.248
 IMS Interfaces
Interface Entities Protocol
SGs MME – MSS (CSFB) SGsAP

Sv MSS – MME (SRVCC) GTPv2-C

Ut UE - AS XCAP
Sh AS - HSS Diameter

IMS U-Plane
Mb P-GW, MRFP, MGW, ATGW
Transport

ISC S-CSCF - AS SIP

I2 MSS – I/S-CSCF SIP
I3 MSS – AS XCAP
Iq* P-CSCF - ATGW H.248