A Minimum Feature Set of Ims Is Required To Support Voip Over Lte
A Minimum Feature Set of Ims Is Required To Support Voip Over Lte
7.0 Introduction
The idea of IMS is old, but after it’s deployment with LTE users and operators can harness the true
power of IMS. VoIP call support over an LTE network requires IMS support. When a UE with an
active VoIP call leaves LTE coverage to an area with only 1xRTT coverage, the call can be
seamlessly handed over from the LTE-IMS to the 1xRTT CS domain. Call continuity from IMS to the
CS domain is maintained with the help of Single Radio Voice Call Continuity (SRVCC) anchoring.
IMS – IP Multimedia Subsystem is a standalone system. It resides out of the LTE network and
connected to PDN Gateway through SGi interface.
The first one is Mobility Management Entity (MME). MME is the single most control point in
the EPC and responsible for most of the control plane functions.
The second in the list is Serving Gateway (S-GW). All IP packets in uplink and downlink flow
through S-GW. S-GW is also responsible for handling handovers.
The last in the list is P-GW or PDN Gateway. P-GW allocates IP addresses to UEs. It also
provides interfaces towards internet and IMS.
The following architecture diagram shows EPC, IMS and the interface between them.
User Equipment (UE)
Each UE must contain one UICC and each UICC may have one or more of the following modules.
Let’s look into ISIM which is important when UE wants to use IMS resources in the network. ISIM
contains the following:
SIP User Agent resides in the UE to send and receive SIP messages. SIP-UA provides basic
telephony functionality. It can act in two different roles:
For VoLTE and IMS prospective two nodes are important in the Evolved Packet Core.
PDN Gateway allocates IP addresses to UEs. PDN-GW is also the point of communication between
EUTRA and non-3GPP services like the internet.
When IMS is available, there can be more that one PDN-GW in the EPC, one for internet and one for
IMS.
The PCRF determines the allowed traffic types in real-time. It also checks how to account for the
traffic. Operators use this information for billing purpose.
Based on requests for IMS services, the PCRF also initiates the appropriate bearers.
When a UE starts a VoLTE call, the PCRF checks if the UE has a subscription to start VoLTE call. If
the UE has VoLTE subscription, PCRF setup dedicated bearer for IMS services.
IMS Core
CSCF establishes monitors, supports, and releases multimedia sessions. It has three different
functional elements. These may or may not be separate physical entities.
Proxy CSCF: P-CSCF acts as the initial point of contact from any SIP User Agent. It handles
all requests from the UE and is, from the UE’s point of view, the “SIP proxy” to the entire
subsystem.
Serving CSCF: S-CSCF has knowledge about the user and what applications are available
to the user. It acts as a decision point. S-CSCF’s main job is to decide whether the user’s SIP
messages will be forwarded to the application servers.
Interrogating CSCF: I-CSCF is the entity that initiates the assignment of a user to an S-
CSCF (by querying the HSS) during registration.
HSS is a database that maintains user profiles and location information. It handles name and address
resolution. HSS is also responsible for authentication and authorization.
SLF assigns HSS to a user in the home network. To achieve this function SLF keeps track of all HSS.
Media Gateways
Media Gateway resides at the interface between SIP-based IMS network and traditional PSTN
network.
RFC 3372 – Session Initiation Protocol for Telephones (SIP-T): Context and Architectures
MGCF controls media gateways and converts codecs where necessary. Also, it may serve as a
breakout to a circuit-switched network.
When MGCF works as a breakout to CS network, it is also responsible for:
When MGCF does not include breakout to CS network, BGCF takes care of this functionality.
IMS Core Network. The IMS Core Network within the VoLTE architecture
provides the service layer for providing Multimedia Telephony.
IMS :
A default bearer is set up for IMS signaling streams when the UE attaches to the network.
After the UE initiates a call, SIP signaling streams for call connection is transmitted over the
default bearer through the P-GW to the IMS Core.
A dedicated bearer for IMS voice media streams is set up during call connection.
Voice media streams of the calling and called parties are transmitted over the dedicated bearer
The P-CSCF is the initial point of contact for session signalling for the IMS-enabled VoLTE UE.
The P-CSCF behaves as a SIP proxy by forwarding SIP messages between the UE and the IMS Core
Network, maintains the security associations between itself and the VoLTE UE, and incorporates
the Application Function aspect of PCC to enable binding of the IMS session with the bearer for
applying dynamic policy and receiving notifications of bearer level events.
The P-CSCF may be implemented in an Access Session Border Controller which may also
incorporate the IMS-ALG/IMS-AGW.
I-CSCF (Interrogating Call Session Control Function):
The I-CSCF is the contact point within an operator’s network for all connections destined to a
user of that network.
On IMS registration, it interrogates the HSS to determine which suitable S-CSCF to route the
request for registration.
For mobile terminating calls, it interrogates the HSS to determine which S-CSCF the user is
registered on.
S-CSCF (Serving Call Session Control Function):
The S-CSCF provides session set-up, session tear-down, session control and routing functions.
It generates records for billing purposes for all sessions under its control, and invokes Application
Servers based on IFCs received from the HSS.
The S-CSCF acts as SIP registrar for VoLTE UEs that the HSS and I-CSCF assign to it.
It queries the HSS for the applicable subscriber profiles and handles calls involving these end
points once they have been registered.
Telephony Application Server (TAS):
The TAS is an IMS Application Server providing support for a minimum set of mandatory
MultiMedia Telephony (MMTel) services as defined by 3GPP e.g. supplementary service
functionality, and profiled within GSMA PRD IR.92
MRF (Media Resource Function)
The MRF is a common media resource function, for use by IMS Application Servers and I/SCSCFs,
to provide media plane processing independent of application types,
IBCF/TrGW (Interconnection Border Control Function/Transition Gateway)
The IBCF/TrGW is responsible for the control/media plane at the network interconnect point to
other PMNs.
The IBCF/TrGW may be implemented in an Interconnect Session Border Controller.
BGCF (Breakout Gateway Control Function
The BGCF is responsible for determining the next hop for routing of SIP
messages.
This determination is based on information received within the SIP/SDP and
routing configuration data (which can be internal configuration data or ENUM/DNS
lookup).
For CS Domain terminations, the BGCF determines the network in which CS
domain breakout is to occur and selects the appropriate MGCF.
For terminations in peer IMS networks, the BGCF selects the appropriate IBCF to
handle the interconnect to the peer IMS domain.
The BGCF may also provide directives to the MGCF/IBCF on which Interconnect
or next network to select.
Such directives may be given by the inclusion of a routeing header pointing to the
next network ingress node.