LTE and IMS Network Architecture

VoLTE: Evolution

CS Fallback VoIP VoIP + SRVCC

CSFB to UTRAN or GERAN via redirect EPS bearers for conversational voice Single Radio Voice Call Continuity to
(LTE562) CS fallback to UTRAN (LTE736) (LTE10) WCDMA/GSM (LTE872/873)
Inter-RAT handover/NACC to UTRAN/GERAN to handle a Standardized solution for VoIP services using IMS - (IP Handling voice calls in case of LTE coverage white
voice call with a possibility of operator-configurable list Multimedia Subsystem) defined by GSMA (GSM spots via UTRAN/GERAN. Possible only in case of
of priorities for different fallback layers. Required when Association) in PRD (Permanent Reference Document) Conversational Voice bearer support (QCI=1) on LTE
there is no Conversational Voice support on LTE side. IR.92 – and dedicated EPS bearers, described in this side. Impossible to handover non-voice bearers to
presentation. GERAN layer.
 3GPP Rel 8 Network Architecture
LTE Radio Evolved Packet Core (EPC) Services in Packet
Access Network Data Network
HSS PCRF
IMS Operator
services

SAE-GW
MME Internet

Serving PDN
eNode-B GW GW Company
intranets

Control plane
User plane
 4

Evolved Node B (eNB) eNB Functions

Radio Resource Management (RRM)

Radio Bearer Control: setup, modifications and

LTE-Uu release of Radio Resources
cell Connection Mgt. Control: UE State Mgmt. MME-UE
Connection
LTE-UE
Radio Admission Control

eNode B Measurements Collection and evaluation

eNode-B
Dynamic Resource Allocation (Scheduler)

IP Header Compression/ de-compression

• It is the only network element defined as part of EUTRAN.
• It replaces the old Node B / RNC combination from 3G. Access Layer Security: ciphering and integrity
• protection on the radio interface
It terminates the complete radio interface including physical layer.
• It provides all radio management functions MME Selection at Attach of the UE
• An eNB can handle several cells.
• To enable efficient inter-cell radio management for cells not attached to User Data Routing to the SAE GW.
the same eNB, there is a inter-eNB interface X2 specified (optional). It
will allow to coordinate inter-eNB handovers without direct Transmission of Paging Message coming from MME
involvement of EPC during this process.
Transmission of Broadcast Info (System info, MBMS)
 5

Mobility Management Entity (MME) MME Functions

Control plane NE in EPC
Evolved HSS
MME
Node B S1-MME Non-Access-Stratum (NAS)
S6a
(eNB) Signaling
S11
S1-U Idle State Mobility Handling
Serving
Gateway Tracking Area updates

Subscriber attach/detach

signaling coordination for

SAE Bearer Setup/Release & HO

Security (Authentication,
• It is a pure signaling entity inside the EPC.
Ciphering, Integrity protection)
• SAE uses tracking areas to track the position of idle UEs. The basic principle is identical to 2G/3G
LA or RA. Trigger and distribution of
• MME handles attaches and detaches to the EPS system, as well as tracking area updates. Paging Messages to eNB
• Therefore it possesses an interface towards the HSS (Home Subscriber Server) which stores the
Roaming Control (S6a interface
subscription relevant information and the currently assigned MME in its permanent data base.
to HSS)
• A second functionality of the MME is the signaling coordination to setup transport bearers (SAE
bearers) through the EPC for a UE. Inter-CN Node Signaling
• MMEs can be interconnected via the S10 interface. (S10 interface), allows efficient
• It generates and allocates temporary ids for UEs. inter-MME tracking area updates
• VLR-like functionality and handovers
 6

Serving SAE Gateway (S-GW)

PCRF
Evolved
S1-MME MME Gxc
Node B (PMIP S5/S8)
(eNB)
S11
S1-U S5/S8
Serving Gateway Functions

Serving SAE PDN Local Mobility Anchor Point:

Gateway Gateway Switching the User plane to a new
eNB in case of Handover
Mobility anchoring for inter-3GPP
mobility. This is sometimes referred
to as the 3GPP Anchor function
Packet Buffering and notification to
MME for UEs in Idle Mode
• The S-GW and PDN Gateway provide the user plane connectivity between the access network and
the external packet data network (PDN) Packet Routing/Forwarding
• It connects towards the eNB via the S1-U interface between eNB, PDN GW and SGSN
• The S-GW has some kind of distribution and packet data anchoring function within EPC.
• It relays the packet data within EPC via the S5/S8 interface to or from the PDN gateway. It support Lawful Interception and
• A serving gateway is controlled by one or more MMEs via S11 interface. Charging functionalities
• At a given time, the UE is connected to the EPC via a single Serving-GW
 7

Packet Data Network (PDN) SAE Gateway (P-GW)

MME Gx Rx
PCRF PDN Gateway Functions
S6a
Mobility anchor for mobility between
S11 3GPP access systems and non-3GPP
S5/S8 SGi access systems. This is sometimes
IMS/PDN referred to as the SAE Anchor function
Serving PDN SAE
Policy & Charging Enforcement (PCEF)
Gateway Gateway
Per User based Packet Filtering (i.e.
deep packet inspection)

Charging Support

Lawful Interception support

• The PDN gateway (or P-GW or PDN-GW) provides the connection between the EPC and
a number of external data networks. IP Address Allocation for UE
• It is comparable to GGSN in 2G/3G networks.
• A major functionality provided by a PDN gateway is the QoS coordination between the Packet Routing/Forwarding between
external PDN and EPC. Serving GW and external Data Network
• Therefore the PDN gateway has to be connected via Gx to a PCRF (Policy & Charging
Rule Function). Packet screening (firewall functionality)
• If a UE is connected simultaneously to several PDNs this may involved connections to
more than one PDN-GW
 8

VoLTE Solution_ 3GPP Reference Architecture

CSCF-Call Session Control Function Proxy CSCF (P-CSCF)
•First contact point for the UE
•Forwarding of SIP messages
IMS Application •Generation of Charging CDRs
Servers
HSS •Integrity and Confidentiality Protection Support
•QoS Authorization Support
•SIP Header Compression
PCRF
Interogating CSCF (I-CSCF)
Cx
I-CSCF •First contact point of another operator‘s network.
Rx •Forwarding of SIP messages
•Assignment of S-CSCFs
•Generation of Charging CDRs
Gm P-CSCF S-CSCF
Mw •Topology Hiding Support

Mw
Serving CSCF (S-CSCF)
•Loads IMS User Profiles from the HSS
E-CSCF •Performs the IMS User Authentication
CSCF Signaling
Data •Performs Session & Service (AS) control
MI •Address Translation Support
•Generation of Charging CDRs
•Lawful Interception Support
Location Retrieval Function: LRF
Emergency CSCF (E-CSCF)
LRF •Establishes sessions for both registered and unregistered
subscribers.
•Selecting a proper Public Safety Answering Point (PSAP)
 10

Home Subscriber Server (HSS)

HSS
I/S-CSCF
MME
S6a Cx
HSS Functions
Permanent and central subscriber
database

Stores mobility and service data for

every subscriber

Contains the Authentication Center

(AuC) functionality.

• Define EPS PDN service and IMS subscriber service

• The HSS can be accessed by the MME via S6a interface.
• The HSS knows where the attached subscribers are located (MME accuracy)
 11

Policy and Charging Rule Function (PCRF)

MME Rx
Gxc PCRF
S6a Gx
(PMIP S5/S8)
S11
S5/S8 SGi
IMS/PDN

Serving PDN SAE PCRF: Policy & Charging Rule Function

Gateway Gateway

QoS policy negotiation with PDN

Charging Policy: determines how

packets should be accounted

PCRF to provide Policy & Charging

Control (PCC) rules every time a
• The PCRF major functionality is the Quality of Service (QoS) coordination between the external PDN new bearer has to be set up.
and EPC.
• Therefore the PCRF is connected via Rx+ interface to the external Data network (PDN)
• This function can be used to check and modify the QoS associated with a SAE bearer setup from SAE
or to request the setup of a SAE bearer from the PDN.
• This QoS management resembles the policy and charging control framework introduced for IMS with
UMTS release 6.
 AS-Application Server

Handling Subscriber Applications, such as:

•TAS: Telecom Application Server HSS

re
et
am
- Handle IR.92 and IR.94 services

Di
- IP-SM-GW: IP Sort Message Gateway

,
Sh
- MRFC: Media Resource Function Control MA
P HLR
o controls media stream resources provided by the MRFP and MME
MRFC/
steers announcements, transcoding and other services
provided by the MRFP. TAS/
o MRFP: Media Resource Function Processor. XCAP
Ut Server Mp’
•XCAP Server ISC
- Subscriber can modify own service through Ut interface. Ma

•IM-AS: Instant Messaging Application Server Gm

MRFP-MGW
SAE-GW

IMS
 MGCF and IMS-MGW BCF and BGW
• Enable voice calls between the IM CN and CS CN • BCF: Border Control Function
- MGCF- Media Gateway Control Function: Signaling • BGW: Border Gateway
interworking • Function
- IMS-MGW: User Plane interworking - NAT and topology hiding
• IMS-MGW is controlled by MGCF through the Mn - DoS protection for SIP
interface. - IPV6/IPV4 interworking
- DSCP marking for QoS control
- IP connection admission control (CAC)
• Deployed on both the Access &Interconnection edges
- A-BCF control A-BGW through Iq interface
- I-BCF control I-BGW through Ix interface
 14

IMS Based VoLTE with 2G/3G Access

CS Core O&M
TAS, (NetAct/NetM/@Com/iNMC)
SCC -AS, LDAP
IP-SM - GW Server
Charging
(NVS) (One -NDS/NPS) Provisioning
(Billing System/
(SAAM)
ENUM Server Charge@once)

Interconnect
IMS Core MSC -Server,
S-/I-CSCF, GMSS, VMSS,
BGCF, MGCF, SRVCC
I-BCF HLR -FE (MSS), LI
(CFX - 5000) (DX HLR)
HSS MGW,
MRF. LI
(MGW U)

- - PSTN/PLMN
- P-CSCF I-BGF
Subscriber (ACME BG)
database

-
SIP/IMS peer Networks
IP-Net
IP -Net
-
PCRF
TLS offload Transport
-
Signaling/control
SAE GW SPDF
MME (PCS - 5000)
(Flexi NG)
(Flexi NS)

GERAN/UTRAN
E-UTRAN (CS only)

4G/LTE 2G/3G

LTE SIP clients Mobile clients

SRVCC
 15

PROXY-CSCF (P-CSCF) & FUNCTIONS

 16

E-CSCF and LRF & FUNCTIONS

Emergency CSCF (E-CSCF)

Location Retrieval Function (LRF)

 17

INTERROGATING-CSCF (I-CSCF) & FUNCTIONS

SERVING-CSCF (S-CSCF) & FUNCTIONS
 HSS AND SLF & FUNCTIONS
HSS

SLF
 20

BGCF & FUNCTIONS

 21

IBCF & FUNCTIONS

 22

IMS-ALG and TrGW & FUNCTIONS

IMS – Application Level Gateway (IMS – ALG)

Transition Gateway (TrGW)

 23

MGCF, MGW & SGW FUNCTIONS

Media Gateway Control Function

Media Gateway (MGW)

Signalling Gateway (SGW)

 24

MEDIA SERVER & FUNCTIONS

(MRF)

(MRFC)
 25

SESSION BORDER CONTROLLER (SBC)

 26

Depending on the location in the Network SBC can be

•A-SBC (Access SBC)
•I-SBC (Interconnect SBC)

Other
Network
I-CSCF
A IMS I
UA SBC SBC
P-CSCF
 27

SBC Functions:
 28

DNS, ENUM,DHCP SERVER & FUNCTIONS

DNS

ENUM Server

DHCP
 29

IMS-GW and IP-Short Message-GW

IMS – GW

IP – SM – GW (IP Short Message Gateway)

 30

IMS-GW and IP-Short Message-GW

Functions:
 31

IDENTIFICATION OF USERS
 32

Public User Identity (IMPU)

 33

Private User Identity

 34

Private User Identity

• The home network authenticates the private user identity only during registration of the Subscriber
• The home network verifies that a public user identity is allocated to a private user identity.
• Private User Identity is not used for routing of SIP Messages.
• Private User Identity used only for Subscription Identification and Authentication.
• The HSS and S-CSCF used to obtain and store the Private User Identity.
• Private User Identity is permanently allocated to a User and stored at the IMS Subscriber Identity
Module (ISIM) card.
• One ISIM card includes only one Private User Identity.
 35

Relationship Of Private & Public User Identities

Registration set 1
Service profile 1
Private
Filter criteria 11
Private User id 1
Filter criteria 12
User id 1
Private
User id 2

IMS Service profile 2

Subscription Filter criteria 21
Filter criteria 22
Registration set 2
Private
Private User id 1
User id 2
Private Service profile 3
User id 2 Filter criteria 31
Filter criteria 32
 36

VoLTE Implementation
 37

Volte deployment
The initial deployments of LTE and indeed VoLTE will likely be self-contained within a single MNO's
domain, serving its own subscribers only (no inter-operator VoLTE interconnect or roaming capability).

The VoLTE architecture for a single PMN deployment

 38
IMS Core

Volte implementation-roaming Sh
Telephony
Application
Server
Mr’ MRF
BGCF

I Mx
Mr
Cx S Mi
C
P- IBCF/
HSS IMS-ALG/
CSCF/ Mw I/S- CSCF Mx IBCF/
TrGW
IMS- TrGW
AGW
S6a Sh
eNodeB S6a Cx Ici/Izi
ENUM Ici/Izi
X2 Rx Rx

SGi
MME H- PCRF S9 Diameter
VoLTE UE Agent (DRA/
(Home) LTE-Uu
S1-MME Gx DEA)
SEG S11
Gx
S1-U
eNodeB SGW S5 PGW
HPLMN

ENUM / IPX
Service ENUM
Diameter App
Provider ID=0 Server ENUM IPX
Network

ENUM

Mw
Mw

VPLMN Mw
P- CSCF/
S6a Diameter Mw I-CSCF IBCF/
S9 Rx IMS- ALG/
Agent ( DRA/ IMS- TrGW
DEA) AGW
a Mi
Mx

MME V- PCRF Rx
S1- MME BGCF
Gx
VoLTE UE SEG S11
(Roaming) LTE-Uu Gx
S1-U
SGW S5 PGW SGi
eNodeB IMS Core
 39

Roaming VoLTE UE Attachment PCRF PCRF HSS

VoLTE UE eNB MME SGW PGW (V) (H) (H)

RRC Connection Request RRC

Connection Setup
Attach Req Attach req - Uplink NAS Transport
RRC Connection Setup complete [ NAS PDU ]
[ Dedicated NAS ] [ EPS SM: PDN Connectivity Request ]
[ PDN Connectivity Request]
Authentication/Security
Update Location Request

Update Location Answer

IMS-APN; QCI:5;
Create ARP;
Session Request Create Session Request
APN AMBR IMS-APN; QCI:5; ARP;
APN AMBR CCR CCR
IP@; QCI:5; ARP; APN IP@; QCI:5; ARP; APN
AMBR AMBR
CCA CCA
E-RAB Setup
E-RAB Setup Request QCI:5; Create Session Response QCI:5; ARP; APN QCI:5; ARP; APN
ARP; AMBR; AMBR;
UE AMBR IP@; QCI:5; ARP; APN IP default rule TFT IP default rule TFT
RRC Connection Reconfiguraton Create Session Response
AMBR
[ NAS PDU ] [ NAS PDU ] IP@; QCI:5; ARP; APN
[ Activate Default Bearer Request ] [IMS-APN;
[ EPS SM: Activate Default Bearer IP@; ] AMBR
[ QCI:5; APN AMBR]
Request ]

RRC Connection Reconfiguration E-RAB Setup

Complete E-RAB Setup Response

Uplink Direct Transfer [ NAS PDU ]

[ EPS SM: Activate Default Bearer Accept ]

Attach complete - Uplink NAS Transport [ NAS[PDU ] Default Bearer Accept ]

Activate
Modify Bearer Request

Modify Bearer Response

Default Bearer Established for IMS Signalling IMS Signalling over IP

 40

VoLTE Basic Call Flows

The basic call flows cover the following scenarios:-

 attachment and IMS Registration
detachment and IMS de-registration,
IMS voice call establishment and teardown,
IMS multimedia (voice/video) call establishment and
teardown,
Adding video to an established voice call,
Removing video from an established multi-media call.
 41

VoLTE UE Attachment and IMS Registration

VoLTE UE eNB MME SGW PGW PCRF HSS P-CSCF I-CSCF S-CSCF TAS

RRC Connection Request

RRC Connection Setup

Attach Req Attach req - Uplink NAS Transport
RRC Connection Setup complete
[ NAS PDU ]
[ Dedicated NAS ] [ EPS SM: PDN Connectivity Request ]
[ PDN Connectivity Request]
Authentication/
Security Update Location Request

Update Location Answer

Create SessionCreate
IMS-APN; QCI:5; Session Request
Request
IMS-APN; QCI:5; IP@; QCI:5; ARP;
ARP; APN AMBR
APN AMBR
E-RAB Setup ARP; APN AMBR
CCR
CCA
E-RAB Setup Request Create Session Response
Create Session Response QCI:5; ARP; APN
QCI:5; ARP; IP@; QCI:5; ARP;
[UE AMBR
NAS PDU ] IP@; QCI:5; ARP; AMBR;
RRC Connection Reconfiguraton APN AMBR
[ NAS PDU ] [ Activate Default Bearer Request ] APN AMBR IP default rule
[IMS-APN; IP@; ] TFT
[ EPS SM: Activate Default [ QCI:5; APN AMBR]
Bearer Request ]
RRC Connection E-RAB Setup
Uplink Direct Transfer
Reconfiguration Complete E-RAB Setup Response
[ NAS PDU ]
[ EPS SM: Activate Default Bearer Accept ]
Attach complete - Uplink NAS Transport
[ NAS PDU ] Modify Bearer Request
[ Activate Default Bearer
Accept ] Modify Bearer Response

Default Bearer Established for IMS Signalling IMS Signalling over IP

SIP Register SIP Register
UAR
UAA
SIP Register

MAR MAA
401 Unauthorised 401 Unauthorised 401 Unauthorised
SIP Register SIP Register
UAR
UAA SIP Register
SAR
SAA
200 OK 200 OK 200 OK
AAR
AAA SIP Register
UDR
UDA
200 OK
SIP Subscribe 200
SIP Subscribe OKSIP
(Subscribe)
Subscribe
200 OK (Subscribe) 200 OK (Subscribe)
SIP Subscribe
SIP Notify 200 OK (Subscribe)
SIP Notify 200 OK (Notify)
SIP Notify SIP Notify 200
200 OK (Notify) 200 OK (Notify) OK (Notify)

VoLTE UE Attachment and IMS Registration message sequence

 42

The VoLTE UE initiates a SIP REGISTER to the P-CSCF, using the P-CSCF IP Address that was
made available during the LTE Attach. The registration request contains:-
oWithin the Contact header, the IMS Communication Service Identifier's (ICSI) for IMS Multimedia
Telephony:-
 urn:urn-7:3gpp-service.ims.icsi.mmtel, or urn:urn-7:3gpp-
service.ims.icsi.mmtel;video
 “+sip.instance” containing an IMEI URN
oThe feature tag for SMS over IP:- +g.3gpp.smsip

o The IMS Public User Identity (as derived above) in one of the forms below:-
 Alphanumeric SIP-URI: e.g. [email protected]
 MSISDN as a SIP-URI: e.g. sip:
[email protected];user=phone
 MSISDN as Tel-URI: e.g. tel:+447700900123
o The IMS Private User Identity as an NAI: e.g. username@realm
o P-Access-Network-Info with:-
 access-type= 3GPP-E-UTRAN-FDD or 3GPP-E-UTRAN-TDD
 UTRAN-cell-id-3gpp parameter
o Request-URI set to the SIP-URI of the domain name of the home network
o Related headers for IMS AKA parameters
o etc.
 43

Message Sequence
VoLTE UE eNB MME SGW PGW PCRF HSS P-CSCF I-CSCF S-CSCF TAS

Default Bearer for IMS Signalling IMS Signalling over IP

SIP Register
SIP Register (expires = 0) (expires = 0)
UAR
SIP Register
UAA
(expires = 0)
SAR

SAA

Notify (reg event) Notify (reg event) Notify (reg event)

200 OK 200 OK

STR Notify (reg event)

200 OK
200 OK
STA
200 OK 200 OK 200 OK

UE is not IMS Registered

Detach Request Delete Session Request

Delete Session Response

Delete Session Request

Detach Accept Delete Session Response

Release Access Bearers Request CCR

Release Access Bearers Response

CCA
UE Context Release Command
RRC Connection Release

UE Context Release Complete

Default Bearer is Deleted and UE is not LTE Attached

VoLTE UE Initiated Detach and IMS Deregistration message sequence

 P-CSCF/ IMS- ALG/ IMS-
VoLTE UE SGW PGW PCRF S-CSCF TAS
eNB MME AGW
44

IMS Signalling via Default Bearer IMS Signalling over IP

SIP Invite (SDP)
SIP Invite (SDP) SIP Invite (SDP)
SIP 100 Trying SIP 100 Trying SIP 100 Trying

SIP Invite (SDP) SIP 100

Trying

SIP Invite (SDP) SIP 100 Trying

E-RAB Setup
E-RAB Setup Request SIP 183 Progress (SDP)

QCI:1; ARP}; SIP 183 Progress (SDP)

RRC Conn Reconfiguraton MBR&GBR Create Bearer Request
Create Bearer
RAR QCI:1; AAR SIP 183 Progress(SDP)
Request
[Activate Dedicated Bearer Req] QCI:1; ARP; TFT, codec AMR
[ Activate Dedicated Bearer Request ] QCI:1; MBR&GBR ARP; TFT
ARP; TFT,
[ IP@; QCI:1; ] MBR&GBR
RRC Conn Reconfiguraton Complete[ TFT; MBR&GBR ]
RAA
[ Activate Dedicated Bearer Accept ] E-RAB Setup Create Bearer E-RAB
Setup Reponse Response Create Bearer Response AAA

[ Activate Dedicated Bearer Res ]

SIP 183 Progress( (SDP)

SIP PRACK SIP PRACK SIP PRACK

SIP 200 OK (PRACK) SIP 200 OK (PRACK) SIP 200 OK (PRACK)

SIP UPDATE (SDP) SIP UPDATE (SDP)

SIP UPDATE (SDP)

SIP UPDATE (SDP)
SIP 200 OK (UPDATE) (SDP) SIP 200
OK (UPDATE) (SDP)
SIP 200 OK (UPDATE) (SDP) SIP 200 OK (UPDATE) (SDP)

SIP 180 Ringing

SIP 180 Ringing SIP 180 Ringing

SIP 180 Ringing
SIP 200 OK IINV)
SIP 200 OK (INV) SIP 200 OK (INV) SIP 200 OK (INV)

RAR AAR

RAA AAA
SIP ACK SIP ACK
SIP ACK
SIP ACK

VoLTE voice traffic via dedicated bearer VoLTE voice traffic over RTP via IMS media plans elements

Basic VoLTE UE to VoLTE UE Voice Call Establishment - Originating Side message sequence
45
 46

ENUM/DNS
ENUM is a telephone look up or number resolution technology, standardised by the Internet Engineering
Task Force (IETF) and Carrier ENUM is further specified by the GSMA in PRD IR.67 [52]. It enables number
registries to be queried and return lists of end point information relating to a telephone number via a
standard ENUM API.
ENUM registries can:
Provide IP routable information against a E.164 phone number
Provide a list of service/platform information against an E.164 number
Provide the correct destination correcting for number portability

Benefits
ENUM is an open standard to enable routing of IP/IMS services using telephone numbers.
ENUM can be applied to any/every IP service, e.g. Voice, Text, MMS, IM, and Video, etc. and so is
architecturally efficient.
The ENUM is an API within the IP family of protocols (an extension of DNS) and fits well with IP
infrastructure.
Number Resolution is required for internal and external routing. Using a standard is essential for
interoperability where queries will take place to external ENUM data sources on a global basis.
ENUM is agnostic of the type of network or interconnect medium an operator chooses to use.
 47

ENUM based routing

1. Query: +447777123456
ENUM
Cloud
2. Result: Voice, SIP,
[email protected]
Call
+447777123456 3. Obtain IP address:
[email protected]
Originating DNS
Cloud
Application 4. IP address: 212.43.25.107
Originating IMS SP
5. Route session
gateway
212.43.25.107

+447777123456

Destination IMS
SP
 48

Diameter Signalling
1. General
The VoLTE architecture utilises Diameter interfaces between components of the EPC, PCC, and IMS core network. 3GPP has defined a number of Diameter Applications based on the Diameter
Base Protocol is defined within IETF RFC 3588 [59].

2. Diameter Agents
In order to support scalability, resilience and maintainability of the Diameter interfaces, the usage of a Diameter Agent is recommended. The Diameter Agent reduces the mesh of different
diameter connections within the network to aid in routing of Diameter messages, provides load-balancing functionality for handling of signalling congestion, and provides protocol
interworking functionality (e.g. Diameter application AVP's, transport protocol, etc.).

3. Diameter Transport
The Diameter Base protocol defines the clients must support either TCP or SCTP as the transport protocol, and that the servers and agents must support both TCP and SCTP.
A number of the Diameter interfaces defined by 3GPP (i.e. Cx, Sh, S6a, S9) have profiled this further by stating that SCTP must be supported by the relevant nodes. Whilst other Diameter
interfaces defined by 3GPP (i.e. Gx, Rx) allow support of SCTP or TCP.
It is recommended that SCTP is utilised as the transport protocol across all Diameter interfaces utilised in the VoLTE architecture, or that a Diameter Agent is deployed to perform the
interworking between SCTP and TCP.

4. Diameter Peer Discovery

To enable Diameter routing within the home network, a Diameter node needs to discover which peer to route messages to for a specific application. This may be performed by using manual
configuration of Diameter nodes within each node. However by allowing for a dynamic discovery mechanism (NAPTR query), it allows for a simpler, scalable, and robust deployment.
Note that the dynamic discovery mechanism becomes more necessary, as the scale of the connections increases and topology hiding becomes more important.

5. Diameter Capability Exchange

As the Diameter Agent acts as a proxy for the network elements supporting a Diameter interface, it must perform a Capability Exchange
 49

QCI
QCI Resource Priority Packet Delay Packet Error Example Services
Type Budget
Loss Rate

1 2 100 ms 10-2 Conversational Voice

2 4 150 ms 10-3 Conversational Video (Live Streaming)
GBR -3
3 3 50 ms 10 Real Time Gaming

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

Streaming)
5 1 100 ms 10 -6 IMS Signalling

6 Video (Buffered Streaming) TCP-based (e.g.,

6 300 ms 10-6 www, e-mail, chat, ftp, p2p file sharing,
progressive video, etc.)
7 Voice,
7 100 ms -3
10
Video (Live Streaming) Interactive
Non- GBR Gaming
8
8 Video (Buffered Streaming) TCP-based (e.g.,
300 ms -6
10 www, e-mail, chat, ftp, p2p file sharing,
9 9 progressive video, etc.)

Standard QCI Values and related QoS Parameters