IP Multimedia Subsystem (IMS)

Introduction

The IP Multimedia Subsystem or IP Multimedia Core Network Subsystem (IMS) is a

standardized architectural framework for delivering IP multimedia services. Historically,
mobile phones have provided voice call services over a circuit-switched-style network,
rather than strictly over an IP packet-switched network. Alternative methods of
delivering voice (VoIP) or other multimedia services have become available on
smartphones, but they have not become standardized across the industry. IMS is an
architectural framework that provides such standardization.

IMS was initially developed by the wireless standards organization 3GPP as a

component of the strategy for developing mobile networks beyond GSM. In its first
incarnation (3GPP Rel-5), it was a method for providing Internet services over GPRS.
Later, 3GPP, 3GPP2, and ETSI TISPAN enhanced this idea by demanding compatibility
for networks than GPRS, like Wireless LAN, CDMA2000, and fixed lines.

Whenever possible, IMS uses IETF standards, such as the Session Initiation Protocol
(SIP). IMS is designed to facilitate access to multimedia and voice applications from
wireless and wireline terminals, or to provide a form of fixed-mobile convergence (FMC),
rather than to standardize applications, according to the 3GPP.[1] This is accomplished
by separating the access network from the service layer with a horizontal control layer.
As the control layer is a shared horizontal layer, services do not necessarily need to
have their own control functions from the perspective of logical architecture. However,
this does not always translate into greater reductions in cost and complexity during
implementation.
Combinations of Generic Access Network, softswitches, and "naked" SIP are alternative
and overlapping technologies enabling service provisioning and access across wired
and wireless networks.
The interest of IMS is being questioned because it is getting simpler to access material
and contacts through methods that are not under the authority of conventional
wireless/fixed operators.

MMTel, the foundation for Voice over LTE (VoLTE), Wi-Fi Calling (VoWIFI), Video over
LTE (ViLTE), SMS/MMS over WiFi and LTE, USSD over LTE, and Rich Communication
Services (RCS), also known as joyn or Advanced Messaging, are examples of
international standards based on IMS. At present, operators are implementing RCS.
Additional Presence/EAB (improved address book) capabilities was added by RCS.
Architecture

Fig1: 3GPP / TISPAN IMS architectural overview

 Fig2: 3GPP / TISPAN IMS architectural overview – HSS in IMS layer (as by standard)

The diagram's various components are described in detail below.

The IMS administration network is made up of a number of distinct functions connected
by standardized interfaces that make up the IP multimedia core network subsystem.
Node (hardware box) is not the same as function: An implementer is free to break a
single function into two or more nodes, or to combine two functions into a single node.
Each node may appear more than once in a single network due to challenges with
dimensioning, load balancing, or organizational structure.

Access network

IMS can be accessed in a number of methods, the majority of which make use of
traditional IP. Even when they are roaming in another network or nation (the visited
network), IMS terminals (such as mobile phones, personal digital assistants (PDAs), and
laptops) can register immediately on IMS. The sole prerequisite is that they be able to
run SIP user agents and use IP. All types of access are supported, including fixed
access (such as DSL, cable modems, Ethernet, and FTTx), mobile access (such as 5G
NR, LTE, W-CDMA, CDMA2000, GSM, and GPRS), and wireless access (such as
WLAN and WiMAX). Gateways can support several phone systems, including plain old
telephone service (POTS—the ancient analogue telephones), H.323 and non-IMS
compatible systems.

Core network

HSS – Home subscriber server:

The IMS network entities that actually handle calls are supported by the home
subscriber server (HSS), also known as the user profile server function (UPSF), which
is a master user database. It manages user authentication and authorisation, stores
information about the subscriber's location and IP address, and holds subscription-
related data (subscriber profiles). It resembles GSM's home location registration (HLR)
and authentication center (AuC).
To map user addresses when using several HSSs, a subscriber location function (SLF)
is required.

User identities:

IMS may be connected to a number of identities, including wildcarded public user

identities, worldwide routable user agent URIs, IP multimedia private identities, and IP
multimedia public identities. Both IMPI and IMPU are uniform resource identifiers
(URIs), which can be either digits or alphanumeric identifiers. They are not phone
numbers or other series of digits.

IP Multimedia Private Identity:

The home network operator assigns a singular, permanently allotted worldwide

identification known as the IP Multimedia Private identification (IMPI). It is used, for
instance, for registration, authorization, administration, and accounting purposes. It
 takes the form of a Network Access Identifier (NAI), i.e. user.name@domain. Each IMS
user must have a single IMPI.

IP Multimedia Public Identity:

Any user can seek communications from other users by using the IP Multimedia Public
Identity (IMPU), which could be printed on a business card, for example. also referred to
as the Address of Record (AOR). Per IMPI, there may be more than one IMPU.
Additionally, the IMPU can be linked to another phone so that both can be contacted
using the same identity (for instance, one phone number for the whole family).

Globally Routable User Agent URI:

An identifier known as the Globally Routable User Agent URI (GRUU) identifies a
particular IMPU and UE instance combination. Public-GRUU (P-GRUU) and Temporary-
GRUU (T-GRUU) are the two different types of GRUU.

· P-GRUU are quite enduring and reveal the IMPU.

· T-GRUU are valid until the contact is explicitly de-registered or the present registration
expires and do not divulge the IMPU.

Wildcarded Public User Identity:

A wildcarded Public User Identity expresses a set of IMPU grouped together.
The HSS subscriber database contains the IMPU, IMPI, IMSI, MSISDN, subscriber
service profiles, service triggers, and other information.

Call Session Control Function (CSCF)

The Call Session Control Function (CSCF), a group of SIP servers or proxies, is used to
process SIP signaling packets in the IMS.

The SIP proxy that initiates communication with the IMS terminal is known as a Proxy-
CSCF (P-CSCF). It can be found in the home network (when the visited network is not
yet IMS compatible) or the visited network (in full IMS networks). A Session Border
Controller (SBC) may be utilized by some networks to carry out this task. At its core, the
P-CSCF is a specialized SBC for the user-network interface that safeguards both the
network and the IMS terminal.

Since the signaling on this leg is encrypted, using an extra SBC between the IMS
terminal and the P-CSCF is unnecessary and impractical. The P-CSCF of the terminal
is either discovered by DHCP, configured (for example, during initial provisioning or via
a 3GPP IMS Management Object (MO)), or assigned in the PDP Context (in the case of
General Packet Radio Service (GPRS)).

· Prior to registration, it is assigned to an IMS terminal, and during registration, that

assignment remains constant.
· The IMS terminal must disregard any additional unencrypted communication since it is
in the route of all signals and may check every signal.
· It offers subscriber authentication and has the potential to link the IMS terminal to an
IPsec or TLS security association. This safeguards the subscriber's privacy and stops
replay and spoofing attempts.
· It examines the signaling and makes sure the IMS terminals are not acting
inappropriately (e.g., altering standard signaling pathways or disobeying home network
routing policies).
· By employing SigComp to compress and decompress SIP messages, it can shorten
round-trip times over slow radio networks.
· A Policy Decision Function (PDF) that approves media plane resources, such as quality
of service (QoS), may be present. It is employed for managing bandwidth and policies,
among other things. The PDF can also be used independently.
· It also produces records of charges.
· An Interrogating-CSCF (I-CSCF) is another SIP function located at the edge of an
administrative domain. Its IP address is published in the Domain Name System (DNS)
of the domain (using NAPTR and SRV type of DNS records), so that remote servers can
find it, and use it as a forwarding point (e.g., registering) for SIP packets to this domain.
· When a user registers for SIP, it asks the HSS to obtain the S-CSCF's address and
assigns it to that user.
· It also sends SIP requests and responses to the S-CSCF.
· It can also be used to conceal the internal network from the outside world (by encrypting
portions of the SIP message), in which case it is known as a Topology Hiding Inter-
network Gateway (THIG). This capability was available up until Release 6. This "entry
point" function is no longer a part of the I-CSCF and is instead a part of the
Interconnection Border Control Function (IBCF) as of Release 7. The IBCF performs
NAT and firewall (pinholing) functions and serves as a gateway to external networks. A
session border controller with a focus on the network-to-network interface is known as
the IBCF.
· The signaling plane's core node is a Serving-CSCF (S-CSCF). Although it is a SIP
server, it also handles session control. It is constantly found within the domestic
network. User profiles are downloaded and uploaded via Diameter Cx and Dx interfaces
to the HSS (the user profile is merely cached locally for processing purposes and is not
modified). The HSS has loaded the essential subscriber profile data.
· It manages SIP registrations, enabling it to connect the user's location (for example, the
terminal's IP address) and SIP address.
· It sits on the path of all signaling messages sent by locally registered users, and it can
examine each message. It chooses which application server(s) the SIP message will be
forwarded to in order to offer their services.
· In most cases, it uses Electronic Numbering (ENUM) lookups to provide routing
services.
· Multiple S-CSCFs may be present in the network for load balancing and high availability
purposes, which it enforces.
· When the I-CSCF queries the HSS, the HSS determines which user will get the S-
CSCF. There are other solutions available for this purpose, such as matching
subscribers' optional and required skills and S-CSCFs.
 Application servers

SIP Application servers (AS) host and run services and use SIP to communicate with
the S-CSCF. The Voice Call Continuity Function (VCC Server) is an example of an
application server being developed by the 3GPP. The AS can function in SIP proxy
mode, SIP UA (user agent) mode, or SIP B2BUA mode depending on the actual service.
An AS may be situated within the personal network or within a network owned by a third
party. It can use the Diameter Sh or Si interfaces (for a SIP-AS) to query the HSS if it is
connected to the home network.

· SIP AS: Host and execute IMS specific services

· IP Multimedia Service Switching Function (IM-SSF): Interfaces SIP to CAP to
communicate with CAMEL Application Servers
· OSA service capability server (OSA SCS): Interfaces SIP to the OSA framework;

Functional model
Depending on the particular service being used, the AS-ILCM (Application Server -
Incoming Leg Control Model) and AS-OLCM (Application Server - Outgoing Leg Control
Model) may also save session state. For an incoming leg, the AS-ILCM interacts with
the S-CSCF (ILCM), and for an outgoing leg, the AS-OLCM interfaces with the S-CSCF
(OLCM). The service(s) are offered by Application Logic, who also works with the AS-
OLCM and AS-ILCM.

Public Service Identity

Public Service Identities (PSI) are identities that identify services, which are hosted by
application servers. As user identities, PSI takes the form of either a SIP or Tel URI.
PSIs are stored in the HSS either as a distinct PSI or as a wildcarded PSI:
· a distinct PSI contains the PSI that is used in routing
· a wildcarded PSI represents a collection of PSIs.

Media servers
The Media Resource Function (MRF) performs media-related tasks like playing
announcements and tones and manipulating media (for example, voice stream mixing).
A media resource function controller (MRFC) and a media resource function processor
(MRFP) are further subdivided into each MRF.
· The MRFC is a signaling plane node that controls the MRFP by interpreting data from
the AS and S-CSCF.
· A media plane node called the MRFP is used to combine, source, or process media
streams. It can control who has access to shared resources.

A functional entity called the Media Resource Broker (MRB) is in charge of gathering
suitable published MRF information and providing that information to entities that
consume it, such the AS. MRB has two modes of operation:

· Query mode: AS asks the MRB for media and places the call based on the MRB's
response.
· Linear Mode: The MRB receives a SIP INVITE from AS. The call is setup by the MRB.
Breakout gateway

A Breakout Gateway Control Function (BGCF) is a SIP proxy which processes requests
for routing from an S-CSCF when the S-CSCF has determined that the session cannot
be routed using DNS or ENUM/DNS. It includes routing functionality based on
telephone numbers.

PSTN gateways

An interface for PSTN circuit switched (CS) networks is a PSTN/CS gateway. IMS
employs SIP over IP for signaling while CS networks use ISDN User Part (ISUP) (or
BICC) over Message Transfer Part (MTP). IMS employs Real-time Transport Protocol
(RTP), whereas CS networks use Pulse-code modulation (PCM) for media.

· The signaling plane of the CS is connected by a signalling gateway (SGW). In order to

transmit ISDN User Part (ISUP) from the MGCF to the CS network, it converts lower
layer protocols like Stream Control Transmission Protocol (SCTP, an IP protocol), into
Message Transfer Part (MTP, a Signalling System 7 (SS7) protocol). Under the direction
of the MGCF, the SGW converts calls between SIP and ISUP/BICC.
· The SIP endpoint known as a media gateway controller function (MGCF) communicates
with the SGW using SCTP. Additionally, it manages resources via an H.248 interface in
a Media Gateway (MGW).
· By converting between RTP and PCM, a media gateway (MGW) establishes a
connection with the media plane of the CS network. When the codecs are incompatible
(for instance, IMS may utilize AMR while PSTN may use G.711), it can additionally
transcode.
Media resources
Media Resources are those components that operate on the media plane and are under
the control of IMS core functions. Specifically, Media Server (MS) and Media gateway
(MGW)

NGN interconnection
 There are two types of next-generation networking interconnection:
Service-oriented interconnection (SoIx):
The control, signaling (i.e., session-based), and connection of the NGN domains that
enables carriers and service providers to offer services over NGN (i.e., IMS and PES)
platforms with defined levels of interoperability. For instance, "carrier grade" phone
and/or multimedia services over IP connectivity are an example of this. "Defined levels
of interoperability" rely on the service, the quality of service, the level of security, etc.

Connectivity-oriented interconnection (CoIx):

regardless of interoperability standards, the physical and logical connection of carriers

and service providers using only basic IP connections. An IP interconnection of this
type, for instance, is not aware of the unique end-to-end service, therefore network
performance, QoS, and security needs relevant to the service are not always
guaranteed. The possibility that some services might offer a specific degree of
interoperability is not disallowed by this definition. But only SoIx completely satisfies the
requirements for NGN interoperability.

Direct or indirect connections between NGNs are both possible. Direct interconnection is
the joining of two network domains without the use of a middle network domain. When
two network domains are connected indirectly at a single layer, one or more
intermediate network domains serve as the transit networks. The two other network
domains receive transit functionality from the intermediary network domain(s). Media
traffic and service layer signaling may be transported using several connecting
techniques.

IMS-based PES architecture

IMS-based PES (PSTN Emulation System) provides IP networks services to analog

devices. IMS-based PES allows non-IMS devices to appear to IMS as normal SIP
users. Analog terminal using standard analog interfaces can connect to IMS-based PES
in two ways:

· via the Access Media Gateway (A-MGW), which is connected to and managed by
AGCF. Located within the operators' network, AGCF manages several A-MGW. Using
H.248.1 (Megaco) across the P1 reference point, A-MGW and AGCF communicate with
one other. POTS phones use the z interface to connect to the A-MGW. The A-MGW
converts the signaling to H.248 before sending it to AGCF. The H.248 signal and other
inputs from the A-MGW are interpreted by AGCF, which then formats the H.248
messages into the proper SIP messages. When passing generated SIP messages to
the S-CSCF or to the IP border via IBCF (Interconnection Border Control Function),
AGCF poses as the P-CSCF to the S-CSCF. PES AS is triggered by services presented
to S-CSCF in SIP messages. AGCF has also certain service independent logic, for
example on receipt of off-hook event from A-MGW, the AGCF requests the A-MGW to
play dial tone.
· via a SIP Gateway/Adapter or a VGW (VoIP-Gateway) on the client's premises. Through
a VOIP gateway, POTS phones can connect directly to P-CSCF. Between VoIP
gateways and P-CSCFs, operators typically utilize session border controllers for security
and to conceal network topology. SIP over Gm reference point used for VoIP gateway
connection to IMS. The customer premises VoIP gateway is where the POTS service
over the z interface is converted to SIP. Signaling from POTS is translated to SIP and
sent to P-CSCF. As a SIP user agent, VGW represents a SIP terminal to P-CSCF.
Both A-MGW and VGW are unaware of the services. They only relay call control
signaling to and from the PSTN terminal. Session control and handling is done by IMS
components.

Interfaces description

Fig3: TISPAN IMS architecture with interfaces

Interface Technical
IMS entities Description Protocol
name specification

Used by MRFC to
fetch documents
(e.g. scripts,
announcement files,
TCP/SCTP
Cr MRFC, AS and other resources)
channels
from an AS. Also
used for media
control related
commands.

Used to send
subscriber data to
the S-CSCF;
including filter
(I-CSCF, S- TS29.229,
Cx criteria and their Diameter
CSCF), HSS TS29.212
priority. Also used
to furnish CDF
and/or OCF
addresses.
 Used by AS to find
the HSS holding the
user profile
information in a
AS (SIP AS, multi-HSS
Dh OSA, IM- environment. Diameter
SSF) <-> SLF DH_SLF_QUERY
indicates an IMPU
and DX_SLF_RESP
return the HSS
name.

Used by I-CSCF or
S-CSCF to find a
correct HSS in a
multi-HSS
(I-CSCF or S-
environment. TS29.229,
Dx CSCF) <-> Diameter
DX_SLF_QUERY TS29.212
SLF
indicates an IMPU
and DX_SLF_RESP
return the HSS
name.
 Used to exchange
messages between
SIP user equipment
Gm UE, P-CSCF SIP
(UE) or Voip
gateway and P-
CSCF

Allows operators to
control QoS in a
user plane and
exchange charging COPS (Rel5),
Go PDF, GGSN
correlation diameter (Rel6+)
information
between IMS and
GPRS network

Used to exchange
policy decisions-
Gq P-CSCF, PDF related information Diameter
between P-CSCF
and PDF
 Used to exchange
policy decisions-
TS29.211,
Gx PCEF, PCRF related information Diameter
TS29.212
between PCEF and
PCRF

Used for online

flow-based bearer
charging. TS23.203,
Gy PCEF, OCS Diameter
Functionally TS32.299
equivalent to Ro
interface
Reference point
· Notify the AS
of the registered
IMPU, registration
state and UE
capabilities
Interface Technical
IMS entities Description Protocol
name specification

· Supply the
AS with information
to allow it to
execute multiple
services
Interface Technical
IMS entities Description Protocol
name specification

· Convey
charging function
addresses
Interface Technical
IMS entities Description Protocol
name specification

Used to exchange
messages between
an IBCF and
Ici IBCFs another IBCF SIP
belonging to a
different IMS
network.

Used to forward
media streams from
a TrGW to another
Izi TrGWs RTP
TrGW belonging to
a different IMS
network.
Interface Technical
IMS entities Description Protocol
name specification
Interface Technical
IMS entities Description Protocol
name specification

· Forward SIP
requests which are
destined to a public
service identity
hosted by the AS
Interface Technical
IMS entities Description Protocol
name specification

· Originate a
session on behalf of
a user or public
service identity, if
the AS has no
knowledge of a S-
CSCF assigned to
that user or public
service identity
Interface Technical
IMS entities Description Protocol
name specification

· Convey
charging function
addresses

ISUP signalling to
SIP signalling and
MGCF -> I,S-
Mg forwards SIP SIP
CSCF
signalling to I-
CSCF
Interface Technical
IMS entities Description Protocol
name specification

Used to exchange
S-CSCF ->
Mi messages between SIP
BGCF
S-CSCF and BGCF

Used for the

interworking with
the PSTN/CS
domain, when the
BGCF has
BGCF -> determined that a
Mj SIP
MGCF breakout should
occur in the same
IMS network to
send SIP message
from BGCF to
MGCF
Interface Technical
IMS entities Description Protocol
name specification

Used for the

interworking with
the PSTN/CS
domain, when the
BGCF has
determined that a
BGCF ->
Mk breakout should SIP
BGCF
occur in another
IMS network to
send SIP message
from BGCF to the
BGCF in the other
network

Used for
I-CSCF, S-
exchanging
CSCF,
Mm messages between SIP
external IP
IMS and external IP
network
networks
Interface Technical
IMS entities Description Protocol
name specification

MGCF, IM- Allows control of

Mn H.248
MGW user-plane resources

Allows an MRFC to
control media
Mp MRFC, MRFP stream resources H.248
provided by an
MRFP.
Interface Technical
IMS entities Description Protocol
name specification

Application
server sends SIP
message to
MRFC to play
tone and
Used to exchange announcement.
S-CSCF, information This SIP
Mr
MRFC between S-CSCF message
and MRFC contains
sufficient
information to SIP
play tone and
announcement
or provide
information to
MRFC, so that it
can ask more
information
from application
server through
Cr Interface.

Used to exchange
session controls
Mr' AS, MRFC
between AS and
MRFC
Interface Technical
IMS entities Description Protocol
name specification

Used to exchange
messages between
P-CSCF, I-
CSCFs. AGCF
Mw CSCF, S- SIP
appears as a P-
CSCF, AGCF
CSCF to the other
CSCFs

Used for the

interworking with
another IMS
network, when the
BGCF has
determined that a
BGCF/CSCF,
Mx breakout should SIP
IBCF
occur in the other
IMS network to
send SIP message
from BGCF to the
IBCF in the other
network
Interface Technical
IMS entities Description Protocol
name specification

Used for call control

services by AGCF
AGCF, A-
P1 to control H.248 A- H.248
MGW
MGW and
residential gateways

Reference point
P2 AGCF, CSCF between AGCF and SIP
CSCF.

Used by the AS to
request that media
resources be SIP, in query
Rc MRB, AS assigned to a call mode (not
when using MRB specified)
in-line mode or in
query mode
Interface Technical
IMS entities Description Protocol
name specification

P-CSCF, I-
Used to exchange
CSCF, S-
offline charging
Rf CSCF, BGCF, Diameter TS32.299
information with
MRFC,
CDF
MGCF, AS

Used to exchange
AS, MRFC, online charging
Ro Diameter TS32.299
S-CSCF information with
OCF

Used to exchange
policy and charging
related information
between P-CSCF
P-CSCF, and PCRF
Rx Diameter TS29.214
PCRF

Replacement for the

Gq reference point.
Interface Technical
IMS entities Description Protocol
name specification

Used to exchange
User Profile
information (e.g.,
user-related data,
group lists, user-
service-related
information or user
location information
or charging function
addresses (used
AS (SIP AS,
when the AS has not
Sh OSA SCS), Diameter
received the third-
HSS
party REGISTER
for a user)) between
an AS (SIP AS or
OSA SCS) and
HSS. Also allow AS
to
activate/deactivate
filter criteria stored
in the HSS on a per-
subscriber basis
Interface Technical
IMS entities Description Protocol
name specification

Transports CAMEL
subscription
information,
including triggers
Si IM-SSF, HSS MAP
for use by CAMEL-
based application
services
information.

Used by MRFC to
fetch documents
Sr MRFC, AS (scripts and other HTTP
resources) from an
AS

Facilitates the
UE and SIP
management of
AS (SIP AS,
subscriber
Ut OSA SCS, HTTP(s), XCAP
information related
IM-SSF) PES
to services and
AS and AGCF
settings
 Interface Technical
IMS entities Description Protocol
name specification

POTS, Analog Conversion of

z phones and POTS services to
VoIP gateways SIP messages

Session handling

The S-CSCF implements a filter-and-redirect signaling system, one of IMS's most

crucial features, which enables a SIP application to be dynamically and differentially
(depending on the user's profile) triggered.

The S-CSCF may use filter criteria to decide if SIP requests need to be forwarded to
AS. It's vital to note that, in each of the corresponding S-CSCFs, services for the
originating party will be implemented in the originating network and services for the
terminating party will be applied in the terminating network.

Initial filter criteria

An XML-based structure called an initial filter criteria (iFC) is used to describe control
logic. IFCs stand for a user's supplied subscription to an application. They are
downloaded to the S-CSCF upon user registration (for registered users) or on
processing demand (for services, acting as unregistered users).

They are stored in the HSS as part of the IMS Subscription Profile. Until the user profile
is altered or until the end of the registration lifetime, iFCs are still valid.
The iFC is composed of:
· Priority - determines the order of checking the trigger.
· Trigger point - logical condition(s) which is verified against initial dialog creating SIP
requests or stand-alone SIP requests.
· Application server URI - specifies the application server to be forwarded to when the
trigger point matches.

There are two types of iFCs:

· Shared - When provisioning, only a reference number (the shared iFC number) is
assigned to the subscriber. During registration, only the number is sent to the CSCF, not
the entire XML description. The complete XML will have previously been stored on the
CSCF.
· Non-shared - when provisioning, the entire XML description of the iFC is assigned to the
subscriber. During registration, the entire XML description is sent to the CSCF.
Security aspects of early IMS and non-3GPP systems
It is anticipated that the security described in TS 33.203 may not be available for some
time, in particular due to the dearth of USIM/ISIM interfaces and the preponderance of
IPv4-compatible devices. In this case, the 3GPP defines various security methods,
which are often referred to as "early IMS security," in TR33.978 to offer some protection
against the most serious threats. This process is dependent on the network attachment
procedures' authentication, which establishes a connection between the user's profile
and IP address. The signaling on the user-network interface is not safeguarded, which
makes this technique more weaker.

CableLabs provided deltas to the 3GPP specifications where the Digest-MD5 is a

legitimate authentication option in PacketCable 2.0, which likewise adopts the IMS
architecture but does not have USIM/ISIM capabilities in their terminals. Later, TISPAN
made a similar endeavor given the scale of its fixed networks, even though the methods
were different. TLS has been added as a choice for protecting the Gm interface in order
to make up for the absence of IPsec capabilities. The Digest-MD5 methodology has
been included in later 3GPP releases as part of the Common-IMS platform, however
each release takes a unique and different approach. The implementations on the Cx
interface between the S-CSCF and the HSS are different, despite the fact that all 3
Digest-MD5 authentication types have the same functionality and are identical from the
standpoint of the IMS terminal.

Thanks for reading.

Regards,
BABAR BASHIR
Like (17) Dislike (0) Favorite (0)
Share
Report
<Previous:Huawei's Vision for the Future of ICT: Building a Fully Connected, Intelligent World.
Next:What is the estimated time for the rewards shipment to reach me?>