The Importance of Standard IMS

Architecture
Rakesh Khandelwal
Consultant
TATA Consultancy Services
Introduction
This paper considers the Internet protocol multimedia subsystem (IMS) technical architecture and
its importance in adapting to various applications (e.g., push to talk over cellular, session
initiation protocol [SIP] instant messaging presence leverages extension [SIMPLE], streaming,
multiplayer games).
The third-generation partnership project (3GPP) has proposed IMS in Release 5 on Internet
protocol version 6 (IPv6), but it is negotiated for IPv4 because the industry is not ready to migrate
to IPv6 now.
IMS is a person-to-person service that enriches the way people communicate with each other by
combining voice, image, and video into a single session. IMS uses SIP and session description
protocol (SDP) underneath architecture to communicate between various IMS components.
3GPP IMS Release 6, target phase 2, calls for IMS enhancement for POC, group management,
conferencing, messaging, interworking with CS network, and lawful intercept.
3GPP IMS Release 7, target phase 3, calls for further IMS enhancement for emergency calls,
system enhancement for fixed broadband access to IMS, multimedia telephony, and combination
of CS bearer with IMS.
Open Mobile Alliance (OMA) is developing IMS application-enabler specifications and
certifying the enabler with the Global Certification Forum (GCF) while providing conformance
and interoperability test cases.
IMS Overview
IMS is defined by 3GPP as a new subsystem, i.e., a new mobile network infrastructure that
enables the convergence of data, speech, and mobile network technology over an IPbased
infrastructure.
IMS was designed to fill the gap between the existing traditional telecommunications technology
and Internet technology, which increased bandwidth alone cannot do. This will allow operators to
offer new, innovative services that shareholders and end users are expecting.
The architecture of IMS specifically helps enable and enhance real-time multimedia mobile
services such as rich voice services, video telephony, messaging, conferencing, and push services.
1

IMS enables these user-to-user communication services via a number of key mechanisms such as
session negotiation and management, quality of service (QoS) and mobility management.
However, IMS enables much more than just real-time user-to-user services.
Architecture and Features
IMS is designed to provide a number of key functionalities required to enable new IP services via
mobile networks. This new realm of IP services must take into account the complexity of
multimedia, constraints of the underlying network, management of mobility, and management of
the multitude of emerging applications.
Although IMS was designed for mobile networks, it can also be used to provide services for fixed
networks at the same time, providing unique mixtures of services with transparency for the end
user.
Figure 1 gives a diagrammatic view of the IMS architecture in the context of the radio network
and its importance for application server. It also shows the interworking possibility with public
switched telephone networks (PSTNs).
Application Servers
Push to Talk
over
Cellular

Streaming
SIMPLE
Multi Player
Games

XDM

Home Network

Visited Network

ISC Interface

ISC Interface
PDF

PDF
I-BCF

I-BCF

HSS

HSS

I-CSCF

I-CSCF

P-CSCF

S-CSCF

BGCF

S-CSCF

P-CSCF

MRFC

MGCF

UE1

PSTN

UE2

Figure 1: IMS Architecture

Proxy Call Session Control Function (PCSCF)
This is the first point of contact in the IMS for a user element (UE). The PCSCF may be in the
home or visited network. SIP register/invite methods are initially terminated to PCSCF, and it
ensures that registration/session requests are passed to the correct home network or that SIP
messages are passed to the correct serving CSCF (SCSCF).
2

The major role of PCSCF is to route information to the correct SCSCF so it can support the
path and service-route headers. PCSCF will maintain two route header lists. The first header list
is created during the registration procedure. It is used only to validate the routing information in
the initial request. This list is valid during the entire registration. The second header list is created
from the record-route headers in the initial invite and associated responses. This list is valid
during the call. Once the call is terminated, the second route list is discarded.
Interrogating Call Session Control Function (ICSCF)
ICSCF is the entity of the home network that is able to determine the SCSCF from which users
should register. ICSCF queries a home subscriber server (HSS) to get the name and capability of
the SCSCF. Once SCSCF begins identifying, ICSCF could be removed from the signaling.
The exception to this is as follows: if the topology hiding internetwork gateway (THIG) of I
CSCF is being used, ICSCF shall apply topology hiding to all headers, which reveal topology
information (e.g., via, route, record-route, service-route, P-charging-function-addresses headers).
Serving Call Session Control Function (SCSCF)
The SCSCF is the function that registers the users and provides service to them. The SCSCF is
acting as the SIP registrar for all UEs of IMS. It performs routing and translation, provides billing
information to mediation systems, maintains session timers, and interrogates the HSS to retrieve
authorization.
Media Gateway Control Function (MGCF)
IMS is designed to integrate with PSTNs and traditional telephony services such as 800 numbers,
caller ID, and local number portability. MGCF is used to transfer nonSIP packetized voice to
SIP user agent (UA) and vice versa.
If the calls are originating or terminating on the PSTN, the MGCF converts the PSTN time
division multiplex (TDM) voice bit stream to an IP real-time transport protocol (RTP) stream and
direct it to the IP address of the corresponding IP phone.
Media Resource Function (MRF)
MRF is divided into two parts: multimedia resource function controller (MRFC) and multimedia
resource function processor (MRFP).
Tasks of MRFC are as follows:

Control the media stream resources in the MRFP

Interpret information coming from an application server (AS) and S-CSCF (e.g., session
identifier) and control MRFP accordingly
Generate charging data records (CDR)

Tasks of MRFP are as follows:

Control the bearer on the Mb reference point

Provide resources to be controlled by the MRFC

Mix incoming media streams (e.g., for multiple parties)
Determine media stream source (e.g., for multimedia announcements)
Handle media stream processing (e.g., audio transcoding, media analysis)
Floor control (i.e., manage access rights to shared resources in a conferencing
environment)

Interconnect Border Control Function (IBCF)

IBCF functionality includes the provision of network address port translation (NAPT) and
firewalls. It also provides conversion between IPv4 and IPv6. IBCF controls media exchange,
signaling, and policies across the operator boundary.
Home Subscriber Server
HSS is a master database for users subscription-related information. It supports the IMS entity to
establish the registration/call control. HSS is the superset of the home location register (HLR) and
provides users physical location. HSS is operated in IP core networks and can be contacted
through diameter protocol.
It is connected to IMS network via Sh (AS) and Cx (SCSCF) interfaces.
SIP AS
When processing SIP requests, SIP AS acts as follows:

AS acts as a terminating UA or redirect server for SIP requests

AS acts as an originating UA for SIP requests
AS acts as a SIP proxy for SIP requests
AS acts as a call control/back-to-back UA (B2BUA)
AS does not act at all for particular SIP requests

As such, a SIP AS is connected to SCSCF through an IMS service control (ISC) interface. The
ISC interface is also connected to IP multimedia service switching function (IMSSF) and open
service access service capability server (OSASCS). IMSSF provides interworking for SIP
messages to a corresponding customized application of mobile enhanced logic (CAMEL),
American National Standards Institute (ANSI)41, intelligent network application part (INAP)
and transactional capabilities application part (TCAP). OSASCS acts as a secure gateway
between an underlying network and an application with OSA architecture.
IMS Registration Scenarios
Figure 2 shows a message sequence flow during the IMS registration procedure for any UE IMS
client.

Packet Switch
Domain

UE

P-CSCF

S-CSCF

POWER

PS Attach

Establish PDP Context

REGISTER
REGISTER
401
Unauthorised

401 Unauthorised
REGISTER

REGISTER
200 OK
200 OK

Figure 2: IMS Registration Sequence Diagram

IMS Session Setup Scenario

MSC Session Initiation

UE 1

P-CSCF

IMS B S-CSCF or P-CSCF

(if same network)

S-CSCF

1) INVITE
Store INVITE
info for User

2) 100 Trying
3) INVITE
Store INVITE
info for User

4) 100 Trying

5) INVITE
6) 100 Trying

9) 183 Session
Progress
10) 183 Session
Progress
11) PRACK
12) PRACK

15) 200 OK

7) INVITE

8) 183 Session Progress

UE 2

13) PRACK
14) 200 OK

16) 200 OK
17) UPDATE

22) 200 OK
25) 180 Ringing
26) PRACK

31) 200 OK
32) ACK

18) UPDATE
21) 200 OK
24) 180 Ringing
27) PRACK
30) 200 OK

19) UPDATE
20) 200 OK
23) 180 Ringing

28) PRACK
29) 200 OK

33) ACK

34) ACK

Figure 3: Session Setup Sequence Diagram

Conclusion
In this paper, a detailed description of IMS architecture and its ISC interface, as well as its
importance to run various applications, are given.
An IPbased service architecture would be a key element for future cellular networks, and SIP
will be a standard protocol to cater to all 3GPP multimedia applications beyond Release 5. It
ensures that future multimedia services will be truly IPbased.
All the key components for IP convergence are commercially available today, and IMS
infrastructure equipment is also available.
IMSbased enabler POCv1.0 has been approved by OMA, and some of the conformance test
cases are certified by GCF. Service providers have the opportunity to deploy POC on their
networks.
References

[1] 3GPP TS 24.229 IP Multimedia Call Control Protocol Based on Session Initiation
Protocol (SIP) and Session Description Protocol (SDP)
[2] 3GPP TS 23.228 Technical Specification Group Services and System Aspects IP
Multimedia Subsystem (IMS)
[3] 3GPP TS 23.981 Interworking Aspects and Migration Scenarios for IPv4Based IMS
Implementations