Ims

Technology
IMS/TISPAN Overview
3FL12353AAAAWBZZA
Edition 9
TRAINING MANUAL
Technology - IMS/TISPAN Overview

All rights reserved © 2007, Alcatel-Lucent
Copyright © 2007 by Alcatel-Lucent - All rights reserved

Passing on and copying of this document, use and
communication of its contents not permitted without
written authorization from Alcatel-Lucent
All Rights Reserved © 2007, Alcatel-Lucent

IMS/TISPAN Overview - Page 1
Legal Notice
@@SECTIONTITLE - @@MODULETITLE @@SECTION - @@MODULE - 2
Switch
Warning
Safety to notes view!
Both lethal and dangerous voltages are present within the equipment. Do not wear conductive jewelry
while working on the equipment. Always observe all safety precautions and do not work on the
equipment alone.
Caution
The equipment used during this course is electrostatic sensitive. Please observe correct anti-static
precautions.
Trade Marks
Alcatel and MainStreet are trademarks of Alcatel.
All other trademarks, service marks and logos (“Marks”) are the property of their respective holders
including Alcatel-Lucent. Users are not permitted to use these Marks without the prior consent of Alcatel
or such third party owning the Mark. The absence of a Mark identifier is not a representation that a
particular product or service name is not a Mark.
Copyright
This document contains information that is proprietary to Alcatel-Lucent and may be used for training
purposes only. No other use or transmission of all or any part of this document is permitted without
Alcatel-Lucent’s
Technology
written permission, and must include all copyright and other proprietary notices. No
otherIMS/TISPAN
use or transmission
Overview of all or any partAll of
Rights Reserved © Alcatel-Lucent 2007
its contents may be used, copied, disclosed or conveyed to
any party in any manner whatsoever without prior written permission from Alcatel-Lucent.
Use or transmission of all or any part of this document in violation of any applicable Canadian or other
legislation is hereby expressly prohibited.
User obtains no rights in the information or in any product, process, technology or trademark which it
includes or describes, and is expressly prohibited from modifying the information or creating derivative
works without the express written consent of Alcatel-Lucent.
Alcatel-Lucent, The Alcatel-Lucent logo, MainStreet and Newbridge are registered trademarks of Alcatel-
Lucent. All other trademarks are the property of their respective owners. Alcatel-Lucent assumes no
responsibility for the accuracy of the information presented, which is subject to change without notice.
© 2007 Alcatel-Lucent. All rights reserved.
Disclaimer
In no event will Alcatel-Lucent be liable for any direct, indirect, special, incidental or consequential
damages, including lost profits, lost business or lost data, resulting from the use of or reliance upon the
information, whether or not Alcatel has been advised of the possibility of such damages.
Mention of non-Alcatel-Lucent products or services is for information purposes only and constitutes
neither an endorsement nor a recommendation.
Please refer to technical practices supplied by Alcatel-Lucent for current information concerning Alcatel-
Lucent equipment and its operation.

Self-Assessment of Objectives
Contract number :
At the end of each section you will be asked to fill this questionnaire
Please,
Course title : return
IMS/TISPANthis sheet
Overview to the trainer at the end of the training
Client (Company, centre) :

Switch
Language : to notes
English view! dates from : to :
Number of trainees : Location :
Surname, First name :
Did you meet the following objectives ?

Tick the corresponding box
Please, return this sheet to the trainer at the end of the training
Yes (or No (or
Instructional objectives Globally globally Comments
yes) no)
1 To be able to find and describe an example
where the PoC, IM/PM and GLMS services can
help the subscribers
2 To be able to list the IMS components and
their function.
3 To be able to determine where the protocols
Technology
All Rights Reserved © Alcatel-Lucent 2007
areIMS/TISPAN
used and what their specification are.
Overview
4 To be able to sort the steps needed to

establish a session, and the function of each
element involved
5 To be able to list the contents of an IM-HSS
database, and sort the different identities into
categories
6 To be able to describe the Alcatel-Lucent IMS
solution and establish the correlation with IMS
3GPP specification

Self-Assessment of Objectives [cont.]
Switch to notes view!
Yes (or No (or

Instructional objectives Globally globally Comments
yes) no)
Technology
IMS/TISPAN Overview
Other comments
Thank you for your answers to this questionnaire


Do not delete this graphic elements in here:
Section 1
1
End-user services offered in
IMS/TISPAN
3FL12353AAAAWBZZA Edition 9
Technology IMS/TISPAN Overview


Section 1 Page 1
Blank Page
End-user services offered in IMS/TISPAN 1 2
Technology
IMS/TISPAN Overview
This page is left blank intentionally
Document History
Edition Date Author Remarks
07 2007-02-19 DUVAL, Erwan

Section 1 Page 2
Objectives
To be able to find and describe an example where the PoC,

IM/PM and GLMS services may help the subscribers.
Technology
IMS/TISPAN Overview

Section 1 Page 3
Objectives [cont.]
Technology
IMS/TISPAN Overview

Section 1 Page 4
Table of Contents
Page
1.1 – Introduction 7
IMS/TISPAN and Working groups 8
Main added values with IMS/TISPAN services (1/2) 9
Main added values with IMS/TISPAN services (2/2) 10
Service enablers and communication services 11
1.2 – Service enablers 12
Authentication & Access Control 13
Group list management 14
Group list management 15
Presence management (1/3) 16
1.3 Communication Services 19
3GRC Video 20
Questions (1/2) 21
Questions (2/2) 22
Self-Assessment on the Objectives 23
End of Module 24
Technology
IMS/TISPAN Overview

Section 1 Page 5
Table of Contents [cont.]
Technology
IMS/TISPAN Overview This page is reserved
All rights left blank intentionally
© 2007, Alcatel-Lucent

Section 1 Page 6
1.1 – Introduction
Technology
IMS/TISPAN Overview

Section 1 Page 7
IMS/TISPAN and Working groups
The IMS/TISPAN provides a standardized architecture to offer IP-based

communication services.
The IMS/TISPAN network architecture is composed of two parts:

• Core part specified by 3GPP and ETSI
• Application part specified by the OMA for services.
Technology
IMS/TISPAN Overview
IMS/TISPAN and Working groups
3rd Generation Partnership Project (3GPP) www.3gpp.org

The original scope of 3GPP was to produce globally applicable Technical Specifications and Technical
Reports for a 3rd Generation Mobile System based on evolved GSM core networks and the radio access
technologies that they support (i.e., Universal Terrestrial Radio Access (UTRA)). The scope was
subsequently amended to include the maintenance and development of the Global System for Mobile
communications (GSM) Technical Specifications and Technical Reports including evolved radio access
technologies (e.g., General Packet Radio Service (GPRS) and Enhanced Data rates for GSM Evolution
(EDGE)).
European Telecommunication Standards Institute (ETSI) http://portal.etsi.org/docbox/TISPAN

The European Telecommunications Standards Institute (ETSI) is an independent, non-profit,
standardization organization of the telecommunications industry (equipment makers and network
operators) in Europe, with worldwide projection. ETSI has been successful in standardizing the GSM
cell phone system and the TETRA professional mobile radio system.
Open Mobile Alliance (OMA) www.openmobilealliance.org

The mission of OMA is to facilitate global user adoption of mobile data services by specifying market
driven mobile service enablers that ensure service interoperability across devices, geographies,
service providers, operators and networks, while allowing businesses to compete through innovation
and differentiation.

Section 1 Page 8
Main added values with IMS/TISPAN services (1/2)
IMS/TISPAN is focused on providing IP-based communication services

independently from end-user accesses.
IMS
Technology
IMS/TISPAN Overview
IMS/TISPAN provides the same services to different kind of subscribers

Section 1 Page 9
This IMS/TISPAN architecture provides a valuable evolution for IMS/TISPAN end-

user services compared to current end-user services.
Client-server connectivity Peer-to-peer communication
SMS text messaging Instant messaging

MMS multimedia
Push to Talk
messaging
Vocal and Video Mailbox Push to Show
Gaming
WAP browsing
Technology
IMS/TISPAN Overview
IMS/TISPAN architecture is adapted to peer to peer services

Section 1 Page 10
Service enablers and communication services
The application part embeds:

Service enablers
Communication services
ID
Service enablers:
Authentication & access control
Presence management
Group list management
Communication services:
Instant messaging
Push To Talk
Application Push To Show…
Technology
IMS/TISPAN Overview
Service enablers and communication services
A service enabler is a component that offers a standard interface to internal and external value-added
services.

Section 1 Page 11
1.2 – Service enablers
Technology
IMS/TISPAN Overview

Section 1 Page 12
1.2 Service Enablers
Authentication & Access Control
Technology
IMS/TISPAN Overview

Section 1 Page 13
Technology
IMS/TISPAN Overview
GLMS: Group List Management Service

Section 1 Page 14
Remove a contact
Block a contact
Technology
IMS/TISPAN Overview

Section 1 Page 15
Presence management (1/3)
+3329650007
Status:
Offline
Erwan
+3329650003
Status:
Offline
Christophe
Technology
IMS/TISPAN Overview
PM: Presence Management

Section 1 Page 16
+3329650007
Status:
Online
Erwan
+3329650003
Status: Away
Christophe
Technology
IMS/TISPAN Overview

Section 1 Page 17
Technology
IMS/TISPAN Overview

Section 1 Page 18
1.3 Communication Services
Technology
IMS/TISPAN Overview

Section 1 Page 19
1.3 – Communication Services
3GRC Video
Technology
IMS/TISPAN Overview
Internet and IMS/TISPAN services (1/2)
IMS/TISPAN services evolve towards existing Internet services to make a common service independent from
the access device.

Section 1 Page 20
Questions (1/2)
What are the differents terminals used in this
demonstration?
Wifi PDA
3G phone
Wimax PC
xDSL PC
What are the different services shown during this

presentation?
Push to talk
Push to show
Push to share
Time allowed: Instant Messaging
Gaming
5 minutes
Technology
IMS/TISPAN Overview

Section 1 Page 21
Questions (2/2)
According to this chapter, match each definition listed on the right with the
appropriate service on the left.
GLMS Method of conversing on half-duplex
communication lines, using a button to switch
from voice transmission mode to voice
Push To Talk reception mode.
Presence Form of electronic communication which

involves immediate correspondence between
two or more users who are all online
Push To Show simultaneously
Instant Messaging A walkie-talkie-like video communication

service
This service provides access to presence

information to be made available to other
users or services
Stores and manages groups and lists
Technology
IMS/TISPAN Overview

Section 1 Page 22
Self-Assessment on the Objectives
Please be reminded to fill in the form

for this module
The form can be found in the first part
of this course documentation
Technology
IMS/TISPAN Overview

Section 1 Page 23
End of Module
Technology
IMS/TISPAN Overview

Section 1 Page 24
Section 2
2
Evolution of an R98 network to a
IMS/TISPAN one


Section 2 Page 1
Blank Page
Evolution of an R98 network to a IMS/TISPAN one 22
Technology
IMS/TISPAN Overview
Document History
07 2007-02-19 DUVAL, Erwan

Section 2 Page 2
Objectives
To be able to list the IMS components and their function.
Technology
IMS/TISPAN Overview

Section 2 Page 3
Objectives [cont.]
Technology
IMS/TISPAN Overview

Section 2 Page 4
Table of Contents
Page
2.1 Review of an R98 network 7
Telecommunications world 8
PLMN architecture 9
PLMN architecture 10
2.2 Changes from R98 to R6 (MOBILE) 11
3GPP R98 (GSM + GPRS) 12
3GPP R99 (UMTS) 13
3GPP R4 (NGN Mobile) 14
3GPP R5 (IMS) 15
3GPP R6 (WLAN) 16
2.3 Changes from a conventional network to TISPAN (FIXED) 17
ADSL: Asymetric Digital Subscriber Line 18
NGN: Next Generation Networks (Class 4) 19
NGN: Next Generation Networks (Class 5) 20
« PSTN Emulation » + NGN Multimedia (IMS) 21
Full IMS Architecture 22
TISPAN R1/3GPP R7 - Fixed Mobile Convergence 23
2.4 Architecture of the IMS/TISPAN 24
Why IMS/TISPAN? 25
Why IMS/TISPAN? 26
What is IMS/TISPAN? 27
2.5 IMS/TISPAN functions in layers 28
IMS/TISPAN reference architecture [Simplified] 29
IMS/TISPAN reference architecture 1/2 30
Technology
IMS/TISPAN IMS/TISPAN reference architecture 2/2 © 2007, Alcatel-Lucent 31
All rights reserved
Overview
2.6 Access 32
xDSL Access 33
3G Access 34
WiMAX access 35
POTS access 36
2.7 Control Layer 37
P-CSCF: Proxy Call Session Control Function 38
AGCF : Access Gateway Control Function 39
I-CSCF: Interrogating Call Session Control Function 40
S-CSCF: Serving Call Session Control Function 41
HSS: Home Subscriber Server 42
RACS : Resource and Admission Control Subsystem 43
NASS: Network Attachment Subsystem 44
MRF: Media Resources Function 45
MGCF: Media Gateway Control Function 46
BGCF: Breakout Gateway Control Function 47
I-BCF: Interconnect Border Control Function 48
2.8 Application Layer 49
AS: Application Server 50
2.9 IMS/TISPAN Architecture 51
Complete architecture 52
2.10 Exercise 53
Exercise 1/2 54
Exercise 2/2 55
End of Module 57

Section 2 Page 5
Technology
IMS/TISPAN Overview

Section 2 Page 6
2.1 Review of an R98 network
Technology
IMS/TISPAN Overview

Section 2 Page 7
Telecommunications world
PSTN/ISDN PLMN
PDN
Technology
IMS/TISPAN Overview
Integrated Services Digital Network (ISDN) is a type of circuit switched telephone network
system,designed to allow digital transmission of voice and data over ordinary telephone copper wires.
The public switched telephone network (PSTN) is the concentration of the world's public circuit-
switched telephone networks.
Public Data Network (PDN) is a network established and operated by a telecommunications

administration for the specific purpose of providing data transmission services for the public.
A Public Land Mobile Network (PLMN) is any wireless communications system intended for use by
terrestrial subscribers in vehicles or on foot.

Section 2 Page 8
PLMN architecture
What is the function of each item of equipment in the diagram?
Circuit Switching (CS)
BTS VMSC/VLR GMSC
BSC Circuit
networks
PCU
AuC
HLR
SGSN
GGSN
Packet
GPRS
backbone
networks
Packet Switching (PS)
Technology
IMS/TISPAN Overview
AuC: Authentication Center

BTS: Base Transceiver Station
BSC: Base Station Controller
MSC: Mobile Switching Center
GMSC: Gateway MSC
VMSC: Visited MSC
HLR: Home Location Register
VLR: Visitor Location Register
GPRS: General Packet Radio Service
SGSN: Serving GPRS Support Node
GGSN: Gateway GPRS Support Node
PCU: Packet Control Unit

Section 2 Page 9
PLMN architecture
Evolution of an R98 network to a IMS/TISPAN one 2 10
GGSN
Equipment for transmitting and receiving of radio signals , antennas

SGSN
Equipment in charge of all the radio interface management
VMSC/VLR Database storing information relating to mobile network subscribers.

This static information is combined with dynamic information
concerning the subscriber's latest known location
BSC Performs mobility and data session management for GPRS mobiles
PCU
Interface between the GPRS wireless data network and other

GMSC networks such as the Internet or private networks
Provides an edge function within a PLMN. It terminates the PSTN

signalling and traffic formats and converts this to protocols employed
BTS in mobile networks
Provides switching functions for calls between mobile subscribers

and contains all subscriber data required for call handling and
mobility management for mobile subscribers currently located in the
area
AuC
HLR
Technology
IMS/TISPAN Overview
AuC: Authentication Center

BTS: Base Transceiver Station
BSC: Base Station Controller
MSC: Mobile Switching Center
GMSC: Gateway MSC
VMSC: Visited MSC
HLR: Home Location Register
VLR: Visitor Location Register
GPRS: General Packet Radio Service
SGSN: Serving GPRS Support Node
GGSN: Gateway GPRS Support Node
PCU: Packet Control Unit

Section 2 Page 10
2.2 Changes from R98 to R6 (MOBILE)
Technology
IMS/TISPAN Overview

Section 2 Page 11
2.2 Changes from R98 to R6
3GPP R98 (GSM + GPRS)
BTS VMSC/VLR GMSC
BSC Circuit
networks
PCU
AuC
HLR
SGSN
GGSN
Packet
GPRS
backbone
networks
Packet Switching (PS)
Technology
IMS/TISPAN Overview
3GPP R98 (GSM + GPRS)
The GSM network was designed to enable a mobile subscriber to make telephone calls. The
architecture is divided into two parts:
• the Base Station Subsystem (BSS) which comprises all the antenna equipment called Base
Transceiver Station (BTS) and the items of equipment controlling the BTSs, called Base
Station Controllers (BSCs).
• the Network SubSystem (NSS) which comprises the Mobile Services switching Centers (MSCs)
and a database called the Home Location Register (HLR).
Use of the Internet expanded considerably throughout the 1990s. A need to access these services from
a mobile terminal was anticipated. In 1999, it became possible to access an Internet service from a
mobile, but at low speed (9.6 kbit/s). And this handicap was further complicated by the considerable
consumption of radio resource, inappropriate to the needs of packet switching (monopolising resources
for bursty Internet traffic). To overcome the weaknesses of the GSM network with respect to Internet
services, the General Packet Radio Service (GPRS) was born. GPRS defines a packet switched network
architecture with mobility management and wireless access. The GPRS recommendations still use the
same BSS architecture, but define a different NSS architecture. The GPRS network comprises:
A Serving GPRS Support Node (SGSN), which is linked to one or more BSSs. This is a router
with mobility management functionality.
A Gateway GPRS Support Node (GGSN), which is linked to one or more data networks. This is
a gateway router between the GPRS network and the IP and X.25 based data networks.
The HLR database defined for GSM.

Section 2 Page 12
3GPP R99 (UMTS)
BTS VMSC/VLR GMSC
BSC Circuit
networks
PCU
AuC
HLR
SGSN
GGSN
Packet
GPRS
Node-B backbone
networks
RNC Packet Switching (PS)
Technology
IMS/TISPAN Overview
3GPP R99 (UMTS)
The Universal Mobile Telecommunication System (UMTS) is a third generation mobile radio network.
The UMTS architecture is subdivided into two networks:
• the Radio Access Network (UTRAN),
• the core network which is divided into two domains:
• the Circuit Switched (CS) domain which combines the third generation mobile services
switching centers.
• the Packet Switched (PS)domain which combines the same entities that emerged with
GPRS: SGSN and GGSN.
The HLR database belongs to both domains.

Section 2 Page 13
3GPP R4 (NGN Mobile)

MSC server
BTS Media Gateway Media Gateway

BSC Circuit
networks
PCU
GPRS
backbone
AuC
HLR
SGSN
GGSN
Packet
GPRS
Node-B Backbone
networks
Technology
IMS/TISPAN Overview
3GPP R4 (NGN Mobile)
The CS domain of the UMTS R4 uses the concept of NGN: there is a separation between control and
data transport.
The CS domain is composed of:
• a set of MSC servers/VLR and a set of GMSC servers which handle signaling,
• a set of CS-MGW which convert circuit data (voice, multimedia) into ATM cells or IP packets
so that they are conveyed in the backbone.
The CN R4 can be connected to the UTRAN through the Iu-CS and Iu-PS interfaces and to the BSS
through the A and Gb interfaces.
The packet domain is defined as in 3GPP R3.
The MSC Server is composed of a MGCF (Media Gateway Control Function) and the MSC / VLR call
control and mobility management functions

Section 2 Page 14
3GPP R5 (IMS)

MSC server
BTS Media Gateway Media Gateway

BSC Circuit
networks
PCU
GPRS IMS
backbone
AuC
HLR
SGSN
GGSN Packet
Node-B networks
Technology
IMS/TISPAN Overview
3GPP R5 (IMS)
IMS: IP Multimedia Subsystem
The aim of Release 5 is to:

• offer new value-added services,
• establish multimedia sessions over IP,
• transport all types of information over IP.
To be able to offer these capabilities, Release 5 provides:
Service Based Local Policy (SBLP) control.
SIP compression: content-based compression (see RFC 3320).
Robust Header Compression = RoHC (UE <-> RNC):
• compression of RTP/UDP/IP headers avoiding that single packet loss requires retransmission of
complete headers.
• non content-based compression technique (see RFCs of IETF RoHC working group).
MultiMedia codecs for audio and AMR (mandatory) for video:
• H.263 baseline (mandatory).
• H.263 version 2 Interactive and Streaming Wireless Profile (Profile 3) Level 10 (recommended,
optional).
• ISO/IEC 14496-2 [13] (MPEG-4 Visual) Simple Profile at Level 0 (recommended, optional).

Section 2 Page 15
3GPP R6 (WLAN)
WAC Circuit
3GPP AAA networks
IMS
SGSN AuC
HLR
GGSN Packet
GPRS
Node-B backbone
networks
Technology
IMS/TISPAN Overview
3GPP R6 (WLAN)
Release 6 provides:
Inter-working with CS networks (e.g., PSTN, CS PLMN).
Interworking between 3G & WLAN access.
Dynamic QoS policy and UTRAN QoS optimization for PS / IMS conversational services.
Presence/Instant Messaging.
Group management & Conferencing (SIP).
Service enablers for IMS: PoC.
Lawful interception.
Access agnostic description of IMS specifications.
Inter-working with IP multimedia networks (e.g., Internet), including IPv4 networks.
Study on inter-working aspects and migration scenarios for IPv4 based IMS implementations.
Split between work: 3GPP <-> Open Mobile Alliance (OMA). 3GPP focuses further on network &
IMS session control architecture. OMA takes up service architecture + applications. Examples:
Push over Cellular (PoC)=OMA name for Push To Talk, IMS Presence/Messaging (SIP SIMPLE
based).
UMA is connected to the IMS through a WLAN Access Gateway (WAG)
The 3GPP AAA (Authentication, Authorization and Accounting ) is involved in access and service
authentication and authorization procedures of a WLAN UE

Section 2 Page 16
2.3 Changes from a conventional

network to TISPAN (FIXED)
Technology
IMS/TISPAN Overview

Section 2 Page 17
2.3 Changes from a conventional network to TISPAN
ADSL: Asymetric Digital Subscriber Line
LEX
AN Circuit Networks
LEX TEX
AN
STP
DSLAM
Packet BRAS
LPF
Backbone Internet
Technology
IMS/TISPAN Overview
ADSL: Asymetric Digital Subscriber Line
The idea is to enable Internet calls to be routed as early as possible to a private packet network. A
DSLAM (Digital Subscriber Line Access Multiplexor) is inserted before the AN. A LPF (Low Pass Filter) is
used to separate data from analogue voice onto the wire between the subscriber and the DSLAM, and
the DSLAM separates the voice, which is sent to the AN, from the data, which is sent the the packet
backbone.

Section 2 Page 18
NGN: Next Generation Networks (Class 4)
MGC
LEX
AN Circuit Networks
TGW
TGW
LEX TGW
AN
Packet
Backbone BRAS
DSLAM
LPF
Internet
Technology
IMS/TISPAN Overview
During this first migration stage, the transit exchanges are replaced by TGWs (Trunking GateWay). The
TGWs are controlled by one or more MGCs (Media Gateway Controler).

Section 2 Page 19
MGC
AN Circuit Networks
AGW
TGW
RGW
AN AGW
Packet
Backbone BRAS
STP
DSLAM
LPF
Internet
Technology
IMS/TISPAN Overview
During the second stage of migration to NGN, the access switches will be replaced by MGWs. These
MGWs will be controlled by one or more MGCs.
There are 3 types of MGW organised in two categories:
Access category comprising AGWs (Access Gateways) and Centralized AGWs:,

The AGW equipment is located in operator’s network next to the AN (Access Node) equipment.
Its function is "packetise" the signals at the V5 interface and ISDN interfaces
RGWs (Residential Gateways).

The RGW equipment is located at the subscriber side. Its function is to "packetise" the signals on
the telephone line.
Trunk category comprising TGWs (Trunking Gateways).

The TGW equipment is located in the network. Its function is to "packetise" the speech circuits

Section 2 Page 20
« PES » + NGN Multimedia (IMS)
MGC
AN Circuit Networks
AGW
TGW
RGW
AN AGW
Packet IMS
Backbone
STP
DSLAM
BRAS
Internet
SIP Phone
Technology
IMS/TISPAN Overview
« PSTN Emulation » + NGN Multimedia (IMS)
PES: PSTN Emulation Subsystem
The NGN Multimedia (IMS) is considered as an external IP network. A special phone, called « SIP phone
», will open a session to this IP network, and then exchange signaling using the SIP protocol.
That phone is doing VoIP, and doesn’t need a gateway to "packetise" the voice.
The IMS, is interconnected with other networks, in order to be able to route calls to these networks

Section 2 Page 21
Full IMS Architecture
AN Circuit Networks
AGW
RGW
AN AGW
IMS
STP BRAS
DSLAM
Packet
Backbone
Internet
SIP Phone
Technology
IMS/TISPAN Overview
Full IMS Architecture
In that architecture, the IMS will control the gateways, and provides the « PSTN emulation service »
for analogs subscribers.
We also say, that the circuit disappears, because all phones are considered as IP phones from the IMS
point of view.

Section 2 Page 22
TISPAN R1/3GPP R7 - Fixed Mobile Convergence
Circuit Networks
AN AGW
IMS WAG 3GPP AAA

RGW
GGSN
BRAS STP
SGSN
DSLAM
UTRAN
SIP Phone
Internet
Technology
IMS/TISPAN Overview
TISPAN R1/3GPP R7 - Fixed Mobile Convergence
The TISPAN R1 and the 3GPP R7 are defining IMS as a convergent network that controls fixed and
mobile subscribers

Section 2 Page 23
2.4 Architecture of the IMS/TISPAN
Technology
IMS/TISPAN Overview

Section 2 Page 24
Why IMS/TISPAN?
Multimedia services
PSTN
IMS/TISPAN
PLMN
PDN
Technology
IMS/TISPAN Overview
Why IMS/TISPAN?
IMS: IP Multimedia Subsystem

TISPAN: Telecoms & Internet converged Services & Protocols for Advanced Networks
The new communication paradigm is about networking Internet Protocol (IP)-based mobile devices.
These devices have large, high-precision displays. They have built-in cameras and a lot of resources for
applications. They are always-on-always-connected application devices. This redefines applications.
Applications are no longer isolated entities exchanging information only with the user interface. The
next generation of more exciting applications are peer-to-peer entities which facilitate sharing: shared
browsing, shared whiteboard, shared game experience, shared two-way radio session (i.e., push to
talk). The concept of being connected will be redefined. Dialing a number and talking will soon be
seen as a narrow subset of networking. The ability to establish a peer-to-peer connection between the
new IP-based mobile devices is the key required ingredient.
This new paradigm of communications reaches far beyond the capabilities of good old telephony. It
can be built on current General Packet Radio Service (GPRS) networks.
In order to communicate, the IP-based applications must have a mechanism to reach the
correspondent. We need a global system, TISPAN. It enables applications in mobile devices to establish
peer-to-peer connections.
True integration of voice and data services increases productivity and overall effectiveness, while the
development of innovative applications integrating voice, data and multimedia will create demands
for new services, such as presence, multimedia chat, push to talk and conferencing. The skill to
combine mobility and the IP network will be crucial to service success in the future.

Section 2 Page 25
Why IMS/TISPAN?
IMS/TISPAN
IM/PM,
IM/PM,
Pre-IMS Gaming,
Gaming,
Audio/Voice,
Audio/Voice,
IM/PM,
IM/PM, Video
Video
Gaming,P2S,
Gaming,P2S, Telephony,
Telephony,
Packet
Packet
IM/PM
IM/PM PoC
PoC Conferencing
Conferencing
PoC
PoC
IM/PM
IM/PM
Non- / Near Real-Time Services

NRT IMS Real Time Services
SMS,
SMS, MMS,
MMS, SMS,
SMS, MMS,
MMS, SMS,
SMS, MMS,
MMS, SMS,
SMS, MMS,
MMS,
Web
Web Web
Web Web
Web Web
Web
2.5 G 3G 3G 3G
GSM/GPRS Rel99/Rel4 Rel5 Rel6/Rel7
Audio
Audio Audio
Audio Audio
Audio Audio
Circuit
Circuit
Video-
Video- Video-
Video- Video-
Telephony
Telephony Telephony
Telephony telephony
Technology
IMS/TISPAN Overview
Why IMS/TISPAN?
With Releases 5 and 6 of 3GPP, near real time services as Push to talk over Cellular and real time
services as voice and video telephony, gaming and conferencing (in release 6) will be available over
packet and completely managed by the IMS/TISPAN.

Section 2 Page 26
What is IMS/TISPAN?
Access layer
Application PDN
Applicationlayer
layer
3G
3Gmobile
mobile
WLAN
WLAN Control
Controllayer
layer
WiMAX
WiMAX
DSL
DSL Media Gateway
Fiber P
Fiber S
Ethernet
Ethernet Transport
Transportlayer
T
layer N
/
P
L
M
User data IMS/TISPAN N
Signaling
Technology
IMS/TISPAN Overview
Why IMS/TISPAN ?
3GPP has decided to use a layered approach to architectural design. This means that transport and
bearer are separated from the IMS signaling network and the session management service.
Application layer:
Service Capabilities (no more standardization of every service as in 2G).
Standardized access to telco service capabilities for 3rd party developers: open Interfaces.
IMS User Profile stored in a central database, not statically configured in every switch.
Control layer:
Manages multimedia sessions using only one multimedia protocol (SIP) for session and service
control.
Assumes the authentication of an IMS subscriber.
Only IPv6 is specified inside the IMS (inter-working with IPv4 defined).
Is responsible for Home Service Control (no dependencies on roaming partners).
Transport layer:
Assumes the independence (as long as it is IP) with the access: fixed, mobile, wireless.
Nomadic service access (R5) and session continuity between access types are standardized
(R6).
Quality of Service enabled (policed by control plane).
Combination with charging package for data and IMS services is possible.
Inter-working with circuit switched (fixed/mobile) is supported thanks to gateway.
Access layer:
Represents all the possible broadband access technologies: UTRAN, CDMA2000, xDSL, WLAN,
cable networks.

Section 2 Page 27
2.5 IMS/TISPAN functions in layers
Technology
IMS/TISPAN Overview

Section 2 Page 28
2.5 IMS/TISPAN functions in layers
IMS/TISPAN reference architecture [Simplified]
Application Layer
AS AS AS
Control Layer HSS CSCF

SLF (S/I/P)
I-BCF
MRFC
MGCF
BGCF
AGCF SGW
Transport Layer
MRFP I-BGF
IP network Others Networks
MGW
PSTN/PLMN
Technology
IMS/TISPAN Overview
AGCF Access Gateway Control Function

AS Application Server
BGCF Breakout Gateway Control Function
CSCF Call Session Control Function
HSS Home Subscriber Server
I-BCF Interconnect Border Control Function
I-CSCF Interrogating-CSCF
MGCF Media Gateway Function
MGW Media Gateway
MRF Multimedia Resource Function
P-CSCF Proxy-CSCF
S-CSCF Serving-CSCF
SGW Signalling GateWay
SLF Subscription Locator Function

Section 2 Page 29
2.6 Access
Technology
IMS/TISPAN Overview

Section 2 Page 30
2.6 Access
xDSL Access
Control Layer
RACS TISPAN Core

NASS
P-CSCF
Transport Layer
DSLAM
BRAS
Access Transport RCEF
Network
SIP Phone
Technology
IMS/TISPAN Overview
DSLAM: Digital Subscriber Line Access Multiplexor

BRAS: BroadBand Remote Access Server
NASS: Network Attachment Subsystem
RACS: Resource and Admission Control Subsystem

Section 2 Page 31
2.6 Access
3G Access
Control Layer
IMS Core
P-CSCF PDF
Transport Layer
PEF
Access Transport
Network
Node-B
RNC SGSN GGSN
Technology
IMS/TISPAN Overview

Section 2 Page 32
2.6 Access
WiMAX access
Control Layer
IMS Core
P-CSCF
Transport Layer
PDF
PEF Access Transport

Network
BS WAC
Technology
IMS/TISPAN Overview
BS: Base Station

WAC:WiMAX Access Controller

Section 2 Page 33
2.6 Access
POTS access
Control Layer
TISPAN Core
NASS RACS
AGCF
Transport Layer
H.248
AN AGW
Access Transport
Network
RGW
Technology
IMS/TISPAN Overview
POTS: Plain Old Telephone Service

AGCF: Access Gateway Control Function

Section 2 Page 34
2.7 Control Layer
Technology
IMS/TISPAN Overview

Section 2 Page 35
2.7 Control Layer
P-CSCF: Proxy Call Session Control Function
Entry point of
the IMS
IMS
network for UE
P-CSCF
Access Network
Internet
Alcatel LAN
Proxy
Technology
IMS/TISPAN Overview
P-CSCF: Proxy Call Session Control Function
Has the following functions in the IMS and TISPAN :

Entry Point into the IMS for a UE
SIP Proxy
QoS management

Section 2 Page 36
2.7 Control Layer
AGCF : Access Gateway Control Function
AGCF
CSCFs
Mw
NASS MGC UA
e2
Gq’
H.248 RACS
P1 P1
AN AGW
RGW
Technology
IMS/TISPAN Overview
The AGCF entity encompasses the functionality of the Media Gateway Controller (MGC) and of a SIP
User Agent.The MGC functionality is involved in registration and session processing, and interacts with
the NASS.The SIP UA functionality provides the interface to the others components of the IMS based
architecture and the RACS.

Section 2 Page 37
2.7 Control Layer
I-CSCF: Interrogating Call Session Control Function
Entry point of the IMS network for

HSS
Other IMS I-CSCF
other IMS networks
Network Similar to the GMSC function
P-CSCF
AuC
Access Network HLR
VMSC/VLR GMSC
Circuit
networks
BTS
BSC
Technology
IMS/TISPAN Overview
I-CSCF: Interrogating Call Session Control Function
Has the following functions in the IMS :
Entry point into the IMS from an external IMS network

Assignment of an S-CSCF at UE registration

Section 2 Page 38
2.7 Control Layer
S-CSCF: Serving Call Session Control Function
HSS
Server that downloads the subscriber profile in a
Other IMS I-CSCF local database, and controls the subscriber
Network S-CSCF Similar to the VMSC/VLR function
P-CSCF
AuC
Access Network HLR
VMSC/VLR GMSC
Circuit
networks
BTS
BSC
Technology
IMS/TISPAN Overview
S-CSCF: Serving Call Session Control Function
Has the following functions in the IMS :
Registrar and UE authentication (HSS interaction).

Service Control
Routing

Section 2 Page 39
2.7 Control Layer
HSS: Home Subscriber Server
Database which contains the multimedia

HSS
Other IMS I-CSCF subscription.
Network S-CSCF Similar to the HLR function
P-CSCF
AuC
Access Network HLR
VMSC/VLR GMSC
Circuit
networks
BTS
BSC
Technology
IMS/TISPAN Overview
HSS: Home Subscriber Server

UPSF: User Profile Server Function
The UPSF is equivalent to the HSS in the IP Multimedia Subsystem
The HSS is responsible for holding the following user related information:
• Service-level user identification, numbering and addressing information.
• Service-level user security information: access control information for authentication and
authorization.
• Service-level user location information at inter-system level: the HSS supports the user registration,
and stores inter-system location information, etc.
• Service-level user profile information.
The HSS may store user profile information related to one or more service control subsystems and
applications.
SLF: Subscription Locator Function
The Subscription Locator Function (SLF) is a functional entity that can be accessed by service control
subsystems and
Application Server Functions to retrieve the identity of the HSS containing the service-level user
profile of a particular subscriber.

Section 2 Page 40
2.7 Control Layer
RACS : Resource and Admission Control Subsystem
RACS
P-CSCF
e4 Rq Gq’ Or AGCF
NASS A-RACF SPDF
Ra Re Ia
Border Node
RCEF
BGF
DSLAM BRAS
Technology
IMS/TISPAN Overview
SPDF: Service Policy Decision Function

The SPDF makes policy decisions using policy rules defined by the network operator.
A-RACF: Access-Resource and Admission Control Function

The A-RACF receives requests for QoS resources from the SPDF.The NASS informs to the A-RACF when a
subscriber attaches to the network (the A-RACF receives the subscriber access profile, Id,Physical and
Logical access Id, IP@).
The A-RACF requests the RCEF to install traffic policies.
RCEF: Resource Control Enforcement Function

The RCEF performs policy enforcement functions under control of the A-RACF (Open/Close gates,
Packet marking).
BGF: Border Gateway Function

The BGF is a packet to packet gateway for user plane media traffic.The BGF performs both policy
enforcement functions and NAT (Network Address Translation) functions under the control of the SPDF.

Section 2 Page 41
2.7 Control Layer
NASS: Network Attachment SubSystem
P-CSCF e4
NASS
Or AGCF
e4
CLF RACS
a2
a4
NACF UAAF PDBF
e5
a1 a3
BRAS
AMF
Technology
IMS/TISPAN Overview
NACF: Network Access Configuration Function

The NACF is responsible for the IP address allocation to the UE (ie DHCP server) and the P-CSCF address
allocation.
AMF: Access Management Function

AMF translates network access requests issued by the UE, forwards requests to the UAAF to
authenticate the user.
CLF: Connectivity Session Location and Repository Function

CLF registers the association between the IP address of the UE and the network location information
( Physical access ID, Logical access ID (VP/VC), terminal type).
UAAF: User Access Authorization Function

The UAAF performs user authentication (ie Radius Proxy)
PDBF: Profile Database Function

The PDBF is the functional entity that contains user authentication data (user identities,
authentication keys, user network profile…)

Section 2 Page 42
2.7 Control Layer
MRF: Media Resources Function
AS
HSS
Other IMS I-CSCF
Network S-CSCF
MRF
P-CSCF
MRFC
Access Network
MRFP
Servers which play films and announcement

SCP
Similar to the SRP function LEX
AN
SRP
Technology
IMS/TISPAN Overview
MRF: Media Resources Function
MRFC: Multimedia Resource Function Controller

Controls the media stream resources in the MRFP.
Interprets information coming from an AS and S-CSCF (e.g., session identifier) and controls the
user part accordingly.
MRFP: Multimedia Resource Function Processor

Controls bearers.
Mixes incoming media streams (e.g., for multiple parties).
Sources media streams (for multimedia announcements).
Processes media streams (e.g., audio transcoding, media analysis).

Section 2 Page 43
2.7 Control Layer
MGCF: Media Gateway Control Function
AS
HSS
I-CSCF
S-CSCF
MGCF
P-CSCF SGW
Access Network TDM
MGW
MGC
Servers that controls the media gateway using the
MEGACO Protocols, and communicates with external AN LEX
network using ISUP (if TDM) or BICC/SIP-I (if NGN)
TGW
Similar to the MGC function Packet
Backbone
Technology
IMS/TISPAN Overview
MGCF: Media Gateway Control Function
Communicates with CSCF.

Selects the CSCF depending on the routing number for incoming calls from legacy networks.
Performs protocol conversion between ISUP and the IM subsystem call control protocols.
The out-of-band information is assumed to be received in the MGCF and may be forwarded to
the CSCF/IMS-MGW.
SGW: Signaling Gateway

Section 2 Page 44
2.7 Control Layer
BGCF: Breakout Gateway Control Function
P-CSCF
MGCF
S-CSCF MGCF France Telecom

BGCF
A FT_IMS.fr
MGCF
MGCF British Telecom

BGCF
The BGCF decides where the BT_IMS.uk

break to go out of the IMS will
be performed B
Technology
IMS/TISPAN Overview
BGCF: Breakout Gateway Control Function
The Breakout Gateway Control Function (BGCF) selects the network in which PSTN/PLMN
breakout is to occur and - within the network where the breakout is to occur - selects the MGCF.

Section 2 Page 45
2.7 Control Layer
I-BCF: Interconnect Border Control Function
I-BCF Other IMS

Networks
S-CSCF
I-CSCF
P-CSCF
I-BGF
The I-BCF provides NAT and Firewall functions in order to connects the IMS
network with other IMS networks.
The Interconnect Border Gateway Function (I-BGF) is similar to the I-BCF
function but at the media level.
Technology
IMS/TISPAN Overview
I-BCF: Interconnect Border Control Function
Interconnection with other IP-based subsystems is performed via the IBCF at the signalling level
Controls of I-BGF, performed through the H248 protocol
Interconnect Border GateWay (BGF)

Interconnection with other IP-based subsystems is performed via the I-BGF at the transport level
Performs both policy enforcement functions and NAT functions under the control of the RACS
Provides Firewall function

Section 2 Page 46
2.8 Application Layer
Technology
IMS/TISPAN Overview

Section 2 Page 47
AS: Application Server
AS
HSS
Other IMS I-CSCF
Network S-CSCF
P-CSCF
Access Network
Servers which host applications such as presence

SCP
Similar to the SCP function LEX
AN
SRP
Technology
IMS/TISPAN Overview
AS: Application Server
An Application Server (AS) offers value-added IM services and resides either in the user's home
network or in a third party location. The third party could be a network or simply a standalone
AS.
The AS can communicate with the HSS.
The Serving-CSCF to the AS interface is used to provide services residing in an AS.
An Application Server may influence and impact the SIP session on behalf of the services
supported by the operator’s network. An AS may host and execute services.

Section 2 Page 48
2.9 IMS/TISPAN Architecture
Technology
IMS/TISPAN Overview

Section 2 Page 49
2.9 IMS/TISPAN Architecture
Complete architecture
Application
GW AS
Core
BRAS HSS
NASS AGCF S-CSCF
I-CSCF BGCF
RACS MGCF
I-BCF MRFC
P-CSCF
RTP (IP backbone) MRFP

MGW
GGSN I-BGF
TDM
IP networks
Technology
IMS/TISPAN Overview
Serving-Call Session Control Function (S-CSCF)

Proxy-Call Session Control Function (P-CSCF)
Interrogating-Call Session Control Function (I-CSCF)
Media Gateway Control Function (MGCF)
Home Subscriber Server (HSS)
Media Resource Function Controller (MRFC)
Media Resource Function Processor (MRFP)
Application Server (AS)
Access Gateway Control Function (AGCF)
Interconnection Border Control Function (I-BCF)
Interconnect Border GateWay Function (I-BGF)
Breakout Gateway Control Function (BGCF)

Section 2 Page 50
2.10 Exercise
Technology
IMS/TISPAN Overview

Section 2 Page 51
2 Evolution of an R98 network to a TISPAN one
Exercise 1/2
• In the following table, place correctly the main IMS/TISPAN functional entities
Transport Control Application
AS
UPSF
I-CSCF
AGCF
MRF
DSLAM
I-BCF
Technology
IMS/TISPAN Overview

Section 2 Page 52
2 Evolution of an R98 network to a TISPAN one
Exercise 2/2
According to this chapter, match each definition listed on the right with the
appropriate equipment on the left.
S-CSCF Authorises appropriate transport resources
and implements Admission Control to the
access
MGW
Entry point into the IMS for a UE (User

RACS Equipment)
P-CSCF Provides registration at access level of UE.It

manages the IP address space of the Access
Network.
NASS
Registrar and UE authentication, Service

Control and Routing
Equipment terminates bearer channels from

a circuit network and media streams from a
packet network
Technology
IMS/TISPAN Overview

Section 2 Page 53

for this module
Technology
IMS/TISPAN Overview

Section 2 Page 54
End of Module
Technology
IMS/TISPAN Overview

Section 2 Page 55
3
Section 3
Protocols used in IMS/TISPAN


Section 3 Page 1
Blank Page
Protocols used in IMS/TISPAN 3 2
Technology
IMS/TISPAN Overview
Document History
07 2007-02-19 DUVAL, Erwan

Section 3 Page 2
Objectives
To be able to determine where the protocols are used,

and what their specifications are.
Technology
IMS/TISPAN Overview

Section 3 Page 3
Objectives [cont.]
Technology
IMS/TISPAN Overview

Section 3 Page 4
Table of Contents
Page
3.1 Which protocols in IMS/TISPAN? 7
3.2 Session Initiation Protocol 9
3.3 Where is DIAMETER used? 17
3.4 Real time Transport Protocol 24
3.5 H.248/MEGACO 30
3.6 Exercise 33
3.6 Exercise 34
Technology
IMS/TISPAN Overview

Section 3 Page 5
Technology
IMS/TISPAN Overview This page isreserved

Section 3 Page 6
3.1 Which protocols in IMS/TISPAN?
Technology
IMS/TISPAN Overview

Section 3 Page 7
3.1 Which protocols in IMS/TISPAN?
IMS/TISPAN Architecture
SIP
AS Diameter
HSS
RTP
MEGACO
COPS
AGCF S-CSCF
P-CSCF
I-CSCF MGCF
BGCF
SGW
PDF
NASS RACS MRFC I-BCF
MGW
PSTN/PLMN
RGW MRFP
BRAS
I-BGF Others Networks
PEF
DSLAM
GGSN
SGSN
IP Backbone
Technology
IMS/TISPAN Overview
Reference point Involved entities Purpose Protocol

Gm UE, P-CSCF to exchange messages between UE and CSCFs SIP
Mw P-CSCF, I-CSCF, S-CSCF to exchange messages between CSCFs SIP
ISC S-CSCF, I-CSCF, AS to exchange messages between CSCF and AS SIP
Cx I-CSCF, S-CSCF. HSS to communicate between I-CSCF/ S-CSCF and HSS Diameter
Dx I-CSCF, S-CSCF, SLF by I-CSCF/S-CSCF to find a correct HSS Diameter
in a multi-HSS environment
Sri AS, OSA SCS, HSS to exchange information between SIP AS/OSA SCS and HSS Diameter
Dh AS, HSS used by AS to find a correct HSS in a multi-HSS environment Diameter
Mm I-CSCF. S-CSCF, external IP network used for exchanging messages between IMS/TISPAN and Not specified
external IP networks
Mg MGCF->I-CSCF MGCF converts ISUP signaling to SIP signaling SIP
and forwards SIP signaling to l-CSCF
Mi S-CSCF -> BGCF used to exchange messages between S-CSCF SIP
and BGCF
Mj BGGF -> MGCF to exchange messages between BGCF and MGCF SIP
in the Same IMS/TISPAN network
Mk BGCF -> BGCF to exchange messages between BGCFs in different SIP
IMS/TISPAN networks
Mr S-CSCF, MRFC to exchange messages between S-CSCF and MRFC SIP
Mp MRFC, MRFP to exchange messages between MRFC and MRFP H.248
Mn MGCF, IM-MGW allows control of user-plane resources H.248
Ut UE, AS Enables UE to manage info. related to his services HTTP
Go PDF, PEF allows operators to control QoS in a user plane COPS
and exchange charging correlation information
between IMS/TISPAN and GPRS network
Gq P-CSCF, PDF to exchange policy decisions-related information Diameter
between P-CSCF and PDF

Section 3 Page 8
3.2 Session Initiation Protocol
Technology
IMS/TISPAN Overview

Section 3 Page 9
Location of SIP in IMS/TISPAN
SIP
AS Diameter
HSS
RTP
MEGACO
COPS
AGCF S-CSCF
P-CSCF
I-CSCF MGCF
BGCF
SGW
PDF
MGW
PSTN/PLMN
RGW MRFP
BRAS
PEF
DSLAM
GGSN
SGSN
IP Backbone
Technology
IMS/TISPAN Overview

Section 3 Page 10
Architecture
Here is a simplified IMS/TISPAN plateform.

According to the following diagram, which entity generates the SIP messages
for a new session to establish?
CSCF
UE
CSCF CSCF CSCF

UE UE
IMS/TISPAN
Technology
IMS/TISPAN Overview

Section 3 Page 11
SIP architecture
SIP
Diameter
RTP (media)
HSS HSS
CSCF CSCF
User Agent
User Agent
Technology
IMS/TISPAN Overview
SIP architecture
The SIP (Session Initiation Protocol) signaling protocol was developed by the IETF (Internet Engineering
Task Force) to set up, modify or close Multimedia sessions in a TCP, UDP, IP, DNS or other protocol
environment; in other words, in the context of a multimedia, multicast architecture. A first version (1.0)
was released as early as 1997 and successive changes have led to the version (2.0) studied here and
described in RFC (Request For Comments) 3261 dated June 2002.
The SIP signaling messages can be linked to a "descriptor body" specifying the specific features of the
media to be used for the sessions to be set up. This descriptor body is encoded in SDP (Session
Description Protocol) format. This information directly follows the data of the SIP signal itself.
The users of an SIP network exchange signals on a rational client/server basis. For this, they use the User
Agent function of their equipment; this equipment can be both Client and SIP Server.
To set up a "media" relationship, user 1 must send an SIP invitation message to user 2. This message must
necessarily contain the address information concerning the calling and called parties. For the calling
party, the SIP and/or IP specific addresses could be programmed, if not they can be obtained by a DHCP
/ DNS type request for example to a database; The Location Service.
Once this information is obtained, the invitation can be propagated in the IP / SIP network to the SIP
server (Proxy Server) responsible for the called party's domain.
This end-point server can also apply the search for connection information for user 2 in a Location
Service database and finally retransmit the invitation to the user 2.
Finally, the media relation (RTP for example) can be created when all the setup signals for the SIP call
have been exchanged.
An invitation request can also be transmitted to a Redirect Server when the user 2 has signaled its
change of location to the Location Service.
The Redirect Server can thus supply the new address to which the request can be retransmitted in the
SIP network to user 2, who can respond to it.

Section 3 Page 12
E-mail structure versus SIP structure
Please find the headers in the message on the right corresponding to the different fields on the
e-mail picture.
From: "ip-multimedia.subsystem"
To: christophe.gerard@alcatel.fr
Cc: christophe.cottel@alcatel.fr
Message-ID: 186883672419382@lycos-europe.com
…
Mime-Version: 1.0
Subject: IMS solution overwiew
Date: Wed, 22 Jun 2005 09:17:31 +0000 (GMT)
…
X-MIMETrack: Itemize by SMTP Server on FRMAIL27/FR/ALCATEL
Content-Type: multipart/mixed;
Content-Transfer-Encoding: 7bit
Content-Type: text/html; charset="windows-1252"
…
<html><head><style type="text/css">body{font:12px Arial;margin:3px;overflow-y:auto;overflow-
x:auto}p{margin:0px;}blockquote, ol, ul{margin-top:0px;margin-bottom:0px;}</style></head>
<body><div style="DISPLAY: block; FONT-SIZE: 12px; FONT-FAMILY: Arial">Here is a test to see SMTP
source and to compare with SIP.</br><p style="margin-top:11px;padding-top:3px;
Technology
IMS/TISPAN Overview
Please find the headers in the message on the right corresponding to the different fields on the e-mail
picture.
From: "ip-multimedia.subsystem" <ip-multimedia.subsystem@caramail.com>

To: christophe.gerard@alcatel.fr
Cc: christophe.cottel@alcatel.fr
Message-ID: 186883672419382@lycos-europe.com
X-Mailer: LycosMail
X-Priority: 3 (Normal)
X-Originating-IP: 64.208.49.60
Mime-Version: 1.0
Subject: IMS solution overwiew
Date: Wed, 22 Jun 2005 09:17:31 +0000 (GMT)
X-Virus-Scanned: by amavisd-new at spray.net
X-Scanned-By: '' on 155.132.188.92
X-Alcanet-MTA-scanned-and-authorized: yes
X-MIMETrack: Itemize by SMTP Server on FRMAIL27/FR/ALCATEL(Release 5.0.12HF788 | September 23,
2004) at 06/22/2005 11:17:34,
Content-Type: multipart/mixed; boundary="=_NextPart_Lycos_193821868836725_ID«
--=_NextPart_Lycos_193821868836725_ID
Content-Transfer-Encoding: 7bit
Content-Type: text/html; charset="windows-1252"
<html><head><style type="text/css">body{font:12px Arial;margin:3px;overflow-y:auto;overflow-

x:auto}p{margin:0px;}blockquote, ol, ul{margin-top:0px;margin-bottom:0px;}</style></head>
<body><div style="DISPLAY: block; FONT-SIZE: 12px; FONT-FAMILY: Arial">Here is a test to see SMTP
source and to compare with SIP.</br><p style="margin-top:11px;padding-top:3px;

Section 3 Page 13
E-mail structure versus SIP structure (2/2)
Method INVITE sip: christophe.gerard@sfr.fr;user=phone SIP/2.0
Headers Via: SIP/2.0/UDP 192.168.10.131:5060;branch=z9hG4bK-8d38b1j6uwyg

From: <sip:erwan.duval@orange.fr>;tag=nenzdztxkn
To: <sip:christophe.gerard@sfr.fr;user=phone>
Call-ID: 3c29150fa867-ts10rppd4oht@caramail.com
CSeq: 1 INVITE
Max-Forwards: 70
Contact: <sip: erwan.duval@orange.fr :5060;line=1>
User-Agent: snom200-2.00n
Accept-Language: en
Accept: application/sdp
Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, NOTIFY,
SUBSCRIBE, PRACK, MESSAGE, INFO
Supported: timer, 100rel, replaces
Content-Type: application/sdp
Content-Length: 267
.../... followed by SDP fields

Body
Technology
IMS/TISPAN Overview

Section 3 Page 14
SDP - Information fields
Field Meaning Type

Example
v=0 v= SDP protocol version M
o=IMS 2284358400 2284358400 IN IP4 o= Origin M
s=Session test s= Session name M
i=Conference i= Session description O
c=IN IP4 168.11.5.2 u= URI (universal Resource Identifier) O
b=CT : 144 e= e-mail address O
t=0 0 p= Telephone number O
m=audio 49172 RTP/AVP 0 8 c= Connection data M
a=rtpmap:0 PCMU/8000 b= Bit rate data O
a=rtpmap:8 PCMA/8000 t= Start / end of session M
m=video 23422 RTP/AVP 31 34 r= Session repetition information O
a= rtpmap:31 H261/9000 z= Time zone adjustment (offset) O
a= rtpmap:34 H263/9000 k= Encryption key O
a= Session attributes O
m= Media description M
a= Media attributes O
Technology
IMS/TISPAN Overview
SDP - Information fields
In the table on the right, all the possible fields are output bearing in mind that an M (Mandatory) signifies
that the field must be present in the message and that an O (Optional) signifies that its presence is not
necessary. It should be noted that the syntax, for example v=, is conventional.
More details about the codecs :

http://www.ietf.org/rfc/rfc3551.txt

Section 3 Page 15
3.3 Where is DIAMETER used?
Technology
IMS/TISPAN Overview

Section 3 Page 16
DIAMETER for accessing HSS
SIP
AS Diameter
HSS
RTP
MEGACO
COPS
AGCF S-CSCF
P-CSCF
I-CSCF MGCF
BGCF
SGW
PDF
MGW
PSTN/PLMN
RGW MRFP
BRAS
PEF
DSLAM
GGSN
SGSN
IP Backbone
Technology
IMS/TISPAN Overview
DIAMETER for accessing HSS
Diameter is defined in the RFC3588 and in the RFC3589 for 3GPP command Codes (informational).
• The IANA has allocated Diameter Command Codes 300 through 313, for use in 3GPP Release 5.
These command codes are intended to be used for 3GPP Release 5 only [29.228], [29.229].
Future 3GPP releases are expected to make use of alternate mechanisms.
• Command codes for 3GPP Release 6 are expected to be allocated from the standard command
space, with IETF documentation. The current intent as agreed with 3GPP is to develop a
standards track application addressing the needs of AAA for SIP/SDP and encompassing the
requirements of the cellular community.
Between HSS or SLF and AS (Sh or Dh interfaces) TS 29.328 and TS 29.329

Between HSS or SLF and I or S CSCF (Cx and Dx interfaces) TS 29.228 and TS 29.229
Note that the Subscription Location Function (SLF) is only present in the case of a network using multiple
HSSs. Before the correct HSS can be accessed, the I-CSCF, the S-CSCF and the applicaton server need to
contact the SLF to get the name or address of the appropriate HSS.
Between P-CSCF and PDF (Gq interface) TS 29.209

Note that the Gq interface can be an inter-operator interface, while the Go is always an intra-operator
interface (COPS). In the specifications, the entity making use of the Gq (i.e. P-CSCF) is generally referred
to as “application”.

Section 3 Page 17
DIAMETER for charging
Charging
Ro Service nodes Rf Trigger
TS 32.299 (CTF) TS 32.299 Function
OCF CCF
(Online Charging Function) (Charging Collection Function)
Bi Bi
Billing
Billing Domain
Domain
Technology
IMS/TISPAN Overview
DIAMETER for charging
Here, the usage of Diameter is shown for charging purposes. The Ro and Rf Diameter interfaces are
specified in TS 32.299.
The Service nodes box is a generalisation of all functional blocks in the network that contain a charging
trigger function, e.g. CSCFs, BGCFs, MGCFs…
The Ro interface is used for online charging, while the Rf interface is for offline charging.

Section 3 Page 18
Without Diameter
How old are you ?
John
21 Betty
How long it take you

to come here ?
Technology
IMS/TISPAN Overview

Section 3 Page 19
With Diameter
The first question is

how old are you ?
John The answer to your second question

is 21 minutes, and she does not
want to answer your first question
because it is rude to ask the age of Betty
a lady.
The second question is

how long it take you to
come here ?»
Technology
IMS/TISPAN Overview

Section 3 Page 20
Peer-to-Peer model
S or I-CSCF or AS
Request HSS or Charging Node
Answer
Request
Answer
As an example :
UAR – UAA : User Authorization Request – Answer

SAR – SAA : Server Assignment Request – Answer
LIR – LIA : Location Info Request – Answer
MAR – MAA : Multimedia Authentication Request – Answer
RTR – RTA : Registration Termination Request – Answer
ACR – ACA : Accounting Request - Answer
Technology
IMS/TISPAN Overview
Peer-to-Peer model
Diameter is a peer-to-peer protocol, allowing the server to initiate requests as well. Two servers
initiated messages are defined by the base protocol:
One requesting that the Diameter client terminates a specific user session;
Another requesting that the Diameter client re-authenticates and/or re-authorises a specific
user.
In IMS/TISPAN, the capability of server initiated messages is used to download profile data from the HSS
in the event that the data has changed.
AAA : Authentication, authorization, Accounting
The Diameter protocol is used to provide AAA services for a range of access technologies. Diameter is
loosely based on an existing AAA protocol called RADIUS, which has been used widely for dial-up and
terminal server access.
The Diameter protocol uses a binary header format and is capable of transporting a range of data units
called AVPs. The Diameter base protocol specifies the delivery mechanisms, capability negotiation, error
handling and extensibility of the protocol, whereas individual Diameter applications specify service-
specific functions and AVPs.

Section 3 Page 21
In addition to the base protocol which includes accounting, the ETSI IMS/TISPAN currently makes use of two
other Diameter applications: namely:
the Diameter SIP application defines

• a Diameter application that can be used by a SIP server to authenticate users and to
authorize usage of different SIP resources. The Diameter SIP application is closed to the
3GPP IMS Cx interface in functionality, but it is designed to be generic enough for other SIP
deployment scenarios to be able to benefit from it.
• a set of Command-Codes that are an extension to the Diameter base protocol. These
Command-Codes perform the following functions :
- UAR/UAA—determines whether a user is authorized to receive a certain service and,
if so, indicates the local server capable of providing that service.
- SAR/SAA—assigns a specific SIP server for a particular user and delivers the user
profile to it in a synchronous way.
- LIR/LIA—determines the next-hop SIP entity at an edge proxy.
- MAR/MAA—authenticates and authorizes a user for a specific SIP service (e.g., SIP
registration). Authentication can either be performed in the Diameter server or
delegated to the SIP server.
- RTR/RTA—de-registration initiated by the Diameter server.
- PPR/PPA—asynchronously delivers the user profile to the SIP server from the
Diameter server.
the Diameter credit control application

• The Diameter credit control application is used for realtime credit and cost control for a
variety of different services. As opposed to nonreal-time accounting, which is post-paid,
this is the pre-paid mode of operation . The credit control application specifies a pair of
new Diameter Command-Codes for credit control requests. The application has two main
parts:
- Cost and credit control—services need to be rated in real time, which means that
the cost of a given service needs to be assessed in real time. The user's account also
needs to be debited or credited in real time, based on the accrued service cost.
- Credit authorization—the user's account may also need to be inspected to see that
her balance is sufficient to cover the service. Credit needs to be reserved and
unused reservations need to be refunded. If the user's balance is insufficient to
cover the service charges, the service element needs to be able to deny the service
altogether.
• As in Diameter base protocol accounting, the credit control sessions have two distinct
models: credit authorization with credit reservation and credit authorization with direct
debiting. The first is similar to accounting measurable length services and consists of an
initial interrogation where the credit control server rates the service request and reserves
a sufficient amount of credit from the user's account. This may optionally be followed by
any number of intermediary interrogations, in which the server deducts used credit from
the user's account, and may involve the server performing service rating and credit
reservation to accommodate a service that is continuing. A final interrogation reports back
to the credit control server that the service has been terminated, whereupon the user's
account is debited for the used amount.
• The second model is similar to accounting one-time events. On receiving a credit
authorization request, the server deducts a suitable amount of credit from the user's
account. This model can also be seen as a credit control session, except that the start and
end of the session happen to coincide. The stateless mode also supports operations, such
as service price queries, user account balance checks and credit refunds.
Section 3 Page 22
3.4 Real time Transport Protocol
Technology
IMS/TISPAN Overview

Section 3 Page 23
Introduction - Audio
John IP@ & Betty IP@ &

UDP ports UDP ports
RTP Audio session
RTCP Audio
Technology
IMS/TISPAN Overview
Introduction
RTP provides end-to-end network transport functions suitable for applications transmitting real-time
data, such as audio, video or simulation data, over multicast or unicast network services. RTP does not
address resource reservation and does not guarantee quality-of-service for real-time services. The data
transport is augmented by a control protocol (RTCP) to allow monitoring of the data delivery in a manner
scalable to large multicast networks, and to provide minimal control and identification functionality. RTP
and RTCP are designed to be independent of the underlying transport and network layers. The protocol
supports the use of RTP-level translators and mixers.
Mixer is defined to be able to mixe streams of the same nature all together in one session
In RFC3550 compared to RFC1889, changes occure only to the rules and algorithms governing how the
protocol is used. The biggest change is an enhancement to the scalable timer algorithm for calculating
when to send RTCP packets in order to minimize transmission in excess of the intended rate when many
participants join a session simultaneously.

Section 3 Page 24
Introduction - Video
John IP@ & Betty IP@ &

UDP ports UDP ports
RTP Audio session
RTCP Audio
RTP Video session
RTCP Video
Technology
IMS/TISPAN Overview
Introduction
RTP provides end-to-end network transport functions suitable for applications transmitting real-time
data, such as audio, video or simulation data, over multicast or unicast network services. RTP does not
address resource reservation and does not guarantee quality-of-service for real-time services. The data
transport is augmented by a control protocol (RTCP) to allow monitoring of the data delivery in a manner
scalable to large multicast networks, and to provide minimal control and identification functionality. RTP
and RTCP are designed to be independent of the underlying transport and network layers. The protocol
supports the use of RTP-level translators and mixers.
Mixer is defined to be able to mixe streams of the same nature all together in one session
In RFC3550 compared to RFC1889, changes occure only to the rules and algorithms governing how the
protocol is used. The biggest change is an enhancement to the scalable timer algorithm for calculating
when to send RTCP packets in order to minimize transmission in excess of the intended rate when many
participants join a session simultaneously.

Section 3 Page 25
Role of RTP
Without RTP protocol…
see Bob,
see see
Bob,
see you
you
see
Bob, Bob, Bob,
you at the
Bob, see you
forum.
you at Bob,
you
Bob, TISPAN
the you
TISPAN
PDN
PDN
forum.
Technology
IMS/TISPAN Overview

Section 3 Page 26
Role of RTP
1. Segmentation/reassembly
2 1
see Bob,
3
Bob, see you
you at 4
the
at the
6
TISPAN forum.
1 PDN
forum. Bob, 5
4 3
TISPAN
2
at the you see
Sequence
6 5
forum. TISPAN number
Technology
IMS/TISPAN Overview

Section 3 Page 27
Role of RTP
2. Use of the Timestamp
Bob, see see Bob,

you at
the
you
TISPAN at the
forum. PDN
forum.
T=0000 T=0005 T=00010 T=00015
TISPAN
Bob, see you at the
Timestamp
T=00020 T=00025
TISPAN forum.
Technology
IMS/TISPAN Overview

Section 3 Page 28
3.5 H.248/MEGACO
Technology
IMS/TISPAN Overview

Section 3 Page 29
3.5 H.248/MEGACO
Location of MEGACO in IMS/TISPAN
SIP
AS Diameter
HSS
RTP
MEGACO
COPS
AGCF S-CSCF
P-CSCF
I-CSCF MGCF
BGCF
SGW
PDF
MGW
PSTN/PLMN
RGW MRFP
BRAS
PEF
DSLAM
GGSN
SGSN
IP Backbone
Technology
IMS/TISPAN Overview
Location of MEGACO in IMS/TISPAN
MEGACO is the protocol used between elements of a physically decomposed multimedia gateway.
The MEGACO (RFC 3525) protocol definition is common with ITU-T Recommendation H.248.1.
The Multimedia Resource Function Controller (MRFC) is needed to support bearer-related services, such
as conferencing, announcements to a user or bearer transcoding. The MRFC interprets SIP signalling
received via S-CSCF and uses Media Gateway Control Protocol (MEGACO) instructions to control the
Multimedia Resource Function Processor (MRFP).

Section 3 Page 30
3.5 H.248/MEGACO
Model
Termination t2 -> CIC n°y

IAM
INVITE
BGCF MGCF
Reserve in a new context, one RTP termination

Add the termination t2 in the context x
OK, the termination t1 is reserved in context x

OK, t2 reserved in context x
with infos as IP address, UDP port, CODECs
UE
IMS-MGW
CS Networks
RTP session RTP
RTP TDM
TDM CIC n°y (PSTN, CS PLMN)
IP
termination
termination
* termination
termination
Context x
Technology
IMS/TISPAN Overview
Model
MEGACO is used between a media gateway and the media gateway controller to handle signalling and
session management during a multimedia conference. The media gateway controller and the media
gateway share a master/slave relationship. The connection model for the protocol describes the main
objects within a media gateway as terminations and contexts that can be controlled by the media
gateway controller. A termination sources or sinks one or more streams, and each termination holds
information about the actual media streams.
Different terminations are linked together by a context. The set of terminations that are not associated
with other terminations are defined as being represented by the null context. A context describes the
topology of terminations associated with it.
The protocol contains a set of commands that are used to manipulate the logical entities described in
the connection model (terminations and contexts).
Specifically, the set of commands offered by MEGACO are:
Add : adds a termination to a context. It is also used to implicitly create a context (a context is
created as soon as the first termination is added to it).
Modify : modifies the state properties of a termination and properties specific to media
streams.
Subtract : removes a termination from a context. It is also used to implicitly delete a context.
Similar to creating one, subtracting the last termination of a context deletes the context.
Move : moves a specific termination from one context to another.
AuditValue : returns the current termination properties as well as the events,2 signals3 and
statistics of a termination.
AuditCapabilities : returns all possible values for the termination properties as well as the
signals and events allowed by a particular media gateway.
Notify : used by the media gateway to report to the media gateway controller when certain
events occur.
ServiceChange : used by the media gateway to inform the media gateway controller of specific
changes in service (e.g., when a particular termination has been taken out of service or is
returned to service).
Each command can carry a number of parameters, called descriptors.

Section 3 Page 31
3.6 Exercise
Technology
IMS/TISPAN Overview

Section 3 Page 32
3.6 Exercise
According to what you understood in this second chapter about IMS/TISPAN

protocols, please associate the key words in the column with a protocol.
Real time Transaction Control/Media Session

relation
SIP
RTP
H.248/MEGACO
DIAMETER
Technology
IMS/TISPAN Overview

Section 3 Page 33

for this module
Technology
IMS/TISPAN Overview

Section 3 Page 34
End of Module
Technology
IMS/TISPAN Overview

Section 3 Page 35
Section 4
4
Description of an IMS/TISPAN
system


Section 4 Page 1
Blank Page
Description of an IMS/TISPAN system 4 2
Technology
IMS/TISPAN Overview
Document History
07 2007-02-19 DUVAL, Erwan

Section 4 Page 2
Objectives
To be able to sort the steps needed to establish a session

and the function of each element involved.
Technology
IMS/TISPAN Overview

Section 4 Page 3
Objectives [cont.]
Technology
IMS/TISPAN Overview

Section 4 Page 4
Table of Contents
Page
4.1 User point of view 7
John wants to call Betty 8
4.2 Access Network 12
Switch on your UE 13
Switch on your SIP Phone 14
4.3 IMS/TISPAN registration procedure 17
Warning 18
Basics 19
Registration (1/11) 20
Data stored after a register 31
4.4 Functions performed during the registration 32
Functions 33
initial Filter Criteria (iFC) 34
4.5 Session initiation 35
TechnologyWarning 36
IMS/TISPANHow
Overview
does the network find an IMS/TISPAN subscriber? 37
UMTS to xDSL subscribers (1/19) 38
4.6 Functions performed during the session initiation 57
Functions 58
4.7 Roaming in the IMS/TISPAN 59
Subscriber in another IMS/TISPAN network 60
IMS/TISPAN Subscriber in a visited network 61
Register without Topology Hiding(THIG) 62
Register with Topology Hiding (THIG) 63
Session flow example when subscribers are roaming 64
4.8 Exercises 65
Order the IMS/TISPAN elements 66
Order the IMS/TISPAN elements 67
Functions of the IMS/TISPAN elements 68
Functions of the IMS/TISPAN elements 69
End of Module 71
Section 4 Page 5
Technology
IMS/TISPAN Overview

Section 4 Page 6
4.1 User point of view
Technology
IMS/TISPAN Overview

Section 4 Page 7
John wants to call Betty
John
Betty
In order to call Betty, John must register his
account onto his User Equipment (UE)
John Off hooks, then enters Betty’s address
Technology
IMS/TISPAN Overview
Steps to communicate with Betty
In order to communicate with Betty, John must, at least once, register his identity onto his User
Equipment (UE).
This action is linked to the model of IMS/TISPAN subscription and may be really useful, if for example,
John is calling from an hotel.
Therefore, this public phone becomes John’s phone. If, later, Betty wants to call John back, she will not
need to know where John is, because the network will find the location of “his” UE.
In the IMS/TISPAN, subscribers are defined using addresses, in opposition with a UE number in a classic
network.

Section 4 Page 8
In order to call Betty, John must:

• Switch on his UE
• (Log in to the network)
into the
p lea se login
ou
Could y t
sy em
t : me.ne
s
.du pont@ho
Login John ** ** *******
******
rd
Passwo
Technology
IMS/TISPAN Overview
REGISTER step
To register his identity onto a UE, a subscriber must log in, and a security procedure as enter a password,
may be used to validate the registration.
The login is an optional step, but in the chapter 5, you will see that this option can become mandatory if
the subscriber has more than one identity in his subscription.

Section 4 Page 9

o n d o nt o
p
e lco m e Mr Du twork • Switch on his UE
W . n e t n e
e
the Hom
ill find
qu e st , you w k
your re s of the wee
ing to ie
Accord he best mov
he re t
Technology
IMS/TISPAN Overview
Services activated when login

The IMS/TISPAN introduces the possibility to access services after the registration procedure.
In this example, you can imagine that John has subscribed to services such as the list of the best movies
of the week, and these services are available whatever the access point that John uses.

Section 4 Page 10

ss o f the
t e r t e addre Resource Identifier
hUniversal • Switch on his UE
En d par t y
calle (URI)
SIP-URI
Betty.durand@othernetwork.net
or
TEL-URI
+33620210000
Technology
IMS/TISPAN Overview
Session initiation
With an SIP UE, the notion of call disappears and is replaced by the notion of session.
A session is a multimedia call, where a medium such as video, voice or data can be added or dropped
during a session (of course, one medium must stay. Otherwise the session will be dropped).
This session initiation may be activated using different kinds of called party addresses:
• SIP-URI address, if the subscriber is from another IMS/TISPAN network,
• TEL-URI address, if for instance, the called party is a PSTN subscriber.
Theses addresses will be described later, in the chapter 5.

Section 4 Page 11
4.2 Access Network
Technology
IMS/TISPAN Overview

Section 4 Page 12
4.2 Access Network
Switch on your UE
HSS
IMS/TISPAN
BRAS
DSLAM
Access Network
What may happen when a

subscriber switches on his
UE?
Technology
IMS/TISPAN Overview
Switch on your UE
The IMS/TISPAN is a network which is accessible through the packet side of a xDSL network or UMTS
network.
In this example, we will consider that the subscriber has only one public identity and that this identity is
already set up in the UE to be used automatically.
According to you, which steps must be done before any communication with an IMS/TISPAN network?

Section 4 Page 13
4.2 Access Network
Switch on your SIP Phone
First step : Authentication

IMS Core
NASS RACS
2.Authentication
DSLAM
BRAS
1. PPP
Access Transport
DSL modem
Network
Border Node
Core Transport
Network
Technology
IMS/TISPAN Overview
UE AMF NACF UAAF CLF RACS
1.PPP setup
2.Access Request
2.Access Response
BRAS NASS

Section 4 Page 14
4.2 Access Network
Second step : IP address allocation and

P-CSCF discovery
IMS Core
NASS RACS
3. @IP + P-CSCF address
DSLAM
BRAS
Access Transport
DSL modem
Network
Border Node
Core Transport
Network
Technology
IMS/TISPAN Overview
UE AMF NACF UAAF CLF RACS
1.PPP setup
2.Access Request
2.Access Response
4.Network location info
3.Configuration request
3.IP address + config info
5.PPP IPCP extension for P-CSCF
BRAS NASS

Section 4 Page 15
4.2 Access Network
And then , IMS/TISPAN

Registration IMS/TISPAN
Core
HSS
AS
I-CSCF
P-CSCF S-CSCF
REGISTER
DSLAM BRAS
DSL modem Access Transport

Network
Technology
IMS/TISPAN Overview
This step will be detailled in the section related to TISPAN registration

Section 4 Page 16
4.3 IMS/TISPAN registration procedure
Technology
IMS/TISPAN Overview

Section 4 Page 17
Warning
This section contains simplified procedures:

The authentication phase is missing.
Message contents are simplified.
The subscriber is in his home network.
!
The objective of this section is to introduce the function of each item
of equipment through the procedures, but is not to describe each
message.
Technology
IMS/TISPAN Overview
For all the session flows that follow, the topology hiding (THIG) function will not be used.
The concept of THIG will be explained later in this chapter.

Section 4 Page 18
Basics
AS
7
HSS
IMS/TISPAN 6
4 8
5
S-CSCF
I-CSCF 8
3
8
List of the registration steps DNS
DNS 2
P-CSCF
DSLAM
1
BRAS
UE
Technology
IMS/TISPAN Overview
List of the registration steps
This diagram presents the signalling exchanges during the registration phase.
The registration procedure is in fact used to update databases in the network, in order to allow future
sessions.
An SIP REGISTER message is sent from the UE to the P-CSCF.

The P-CSCF contacts a DNS server to resolve the home domain name of the subscriber, in order to
communicate with the I-CSCF.
The P-CSCF transfers the REGISTER message created by the UE, (with some additional information) to the
I-CSCF of the subscriber’s home network.
The I-CSCF contacts the HSS of the subscriber, to determine the addresses of the S-CSCF available in the
network and their capabilities.
The I-CSCF selects one S-CSCF and forwards the REGISTER message to this S-CSCF.
The S-CSCF contacts the HSS in order to download the subscriber profile. In this profile, initial Filter
Criteria (iFC) are defined.
If some iFC must be activated, the S-CSCF will contact the Application Servers (ASs) before answering the
UE.
The S-CSCF receives an answer from the ASs and responds to the UE using the 200 OK message.

Section 4 Page 19
Registration (1/11)
IMS
UE
Access NASS P-CSCF DNS I-CSCF S-CSCF HSS
1. P-CSCF DISCOVERY
This signaling flow represents the:

•Authentication,
•IP allocation,
•P-CSCF discovery
Technology
IMS/TISPAN Overview
First step
This step is used to initialize a connection from the access network to the TISPAN home network.
During this step, the UE performs:
Authentication: UE initiates a PPP request to apply for an IP address.AMF relay translates PPP
request to an ACCESS request to the UAAF.
IP address allocation and P-CSCF Discovery: AMF sends the configuration request to NACF to obtain
IP address and other parameters including the IP address of a P-CSCF.

Section 4 Page 20
Registration (2/11)
IMS
UE
1. P-CSCF DISCOVERY
2. REGISTER
The UE sends the REGISTER message to the proxy, with:

-Private user identity
Corresponds to an identity stored in the terminal
-Public user identity
In URI format
-Home network domain name
Request-URI
-Terminal IP address
Technology
IMS/TISPAN Overview
Next step
A connection is now available between the UE and the TISPAN network.

The UE generates a REGISTER message and sends it to the entry point of the network: the P-CSCF.
In this message, the home network domain name is present and will be used to determine where to send
the REGISTER message.

Section 4 Page 21
Registration (3/11)
IMS
UE
1. P-CSCF DISCOVERY
2. REGISTER
3. DNS: DNS-Q
4. REGISTER
The P-CSCF examines the home network domain name to

discover the entry point (I-CSCF) in the home network
(DNS look up) and sends the REGISTER message with:
-P-CSCF address/name
-P-CSCF network identifier
Technology
IMS/TISPAN Overview
Next step
The P-CSCF uses a DNS request to translate the home network domain name into the IP address of the I-
CSCF.
Then the P-CSCF adds its own address into the REGISTER message and sends the message to the I-CSCF.

Section 4 Page 22
Registration (4/11)
IMS
UE
1. P-CSCF DISCOVERY
2. REGISTER
3. DNS: DNS-Q
4. REGISTER
5a. User Authorization Request
The I-CSCF requests information related to

the subscriber registration status. The
message contains the following data:
The HSS checks:

-Registered status
-Register allowed from P-CSCF network
Technology
IMS/TISPAN Overview
Next step
The I-CSCF requests information related to the subscriber registration status. It sends a User
Authorization Request (UAR) diameter message to the HSS.
The HSS checks the status of the subscriber, and if the subscription is not locked, the HSS checks the
roaming right, using the address of the P-CSCF from which the request is coming.

Section 4 Page 23
Registration (5/11)
IMS
UE
1. P-CSCF DISCOVERY
2. REGISTER
3. DNS: DNS-Q
4. REGISTER
5b. User Authorization Answer
The HSS sends a response with:

-S-CSCF names
-S-CSCF capabilities
Technology
IMS/TISPAN Overview
Next step
The HSS sends a User Authorization Answer (UAA) diameter message to the I-CSCF and gives a list of S-
CSCFs available in the network with their capabilities.

Section 4 Page 24
Registration (6/11)
IMS
UE
1. P-CSCF DISCOVERY
2. REGISTER
3. DNS: DNS-Q
4. REGISTER
The I-CSCF selects one S-CSCF, does a DNS lookup to find the S-CSCF
6. REGISTER
address and sends the REGISTER message with:
The S-CSCF stores the P-CSCF address/name and the network ID.
Technology
IMS/TISPAN Overview
Next step
The I-CSCF selects one S-CSCF according to the capabilities of the UE and then forwards the REGISTER
message to the S-CSCF.

Section 4 Page 25
Registration (7/11)
IMS
UE
1. P-CSCF DISCOVERY
2. REGISTER
3. DNS: DNS-Q
4. REGISTER
6. REGISTER
7a. Server assignment Request
The S-CSCF sends (SIP registrar action):
-S-CSCF name
Technology
IMS/TISPAN Overview
Next step
The S-CSCF sends a Server Assignment Request (SAR) diameter message in order to inform the HSS that it
will be in charge of the subscriber and to request the subscriber profile.

Section 4 Page 26
Registration (8/11)
IMS
UE
1. P-CSCF DISCOVERY
2. REGISTER
3. DNS: DNS-Q
4. REGISTER
6. REGISTER
7b. Server assignment Answer
The HSS stores the S-CSCF name for that user and
returns the user information. The S-CSCF stores this
information.
Technology
IMS/TISPAN Overview
Next step
The HSS answers using the Server Assignment Answer (SAA) diameter message. This message contains the
subscriber profile and especially the initial filter Criteria (iFC) that define a set of triggers and ASs, in an
ordered list, that the S-CSCF must contact.
These Filter Criteria are called initial because they are defined in the HSS subscriber profile, but they
define triggers to link any action of the mobile, not always the registration.
Other Filter Criteria can be added to the S-CSCF by the AS: they are called subsequent Filter Criteria
(sFC).

Section 4 Page 27
Registration (9/11)
IMS
UE
1. P-CSCF DISCOVERY
2. REGISTER
3. DNS: DNS-Q
4. REGISTER
6. REGISTER
Based on iFC, the S-CSCF sends the 7b. Server assignment Answer
REGISTER message to the service control
platform (AS).
8. Service Control
To AS
Technology
IMS/TISPAN Overview
Next step
The S-CSCF checks the iFC conditions. If any of them match, the S-CSCF contact by order the ASs.
Each AS returns a result in the body of the SIP 200 OK message.

Then the S-CSCF is able to generate the answer according to the result it receives from ASs.

Section 4 Page 28
Registration (10/11)
IMS
UE
1. P-CSCF DISCOVERY
2. REGISTER
3. DNS: DNS-Q
4. REGISTER
6. REGISTER
7b. Server assignment Answer

The response follows the same path as the
REGISTER request, as described in the Via 8. Service Control
list.
9. 200 OK
10. 200 OK
Technology
IMS/TISPAN Overview
Next step
The S-CSCF sends a 200 OK message to the UE and fills in the SIP message with a VIA parameter, to define
which item of equipment the message must pass through.
Example (simplified):
SIP/2.0 200 OK
Via: SIP/2.0/UDP I-CSCF.home1.net, SIP/2.0/UDP P-CSCF.home1.net, SIP/2.0/UDP
[192:233:001:002]
Where 192:233:001:002 represents the IP address of the destination UE.

Section 4 Page 29
Registration (11/11)
IMS
UE
1. P-CSCF DISCOVERY
2. REGISTER
3. DNS: DNS-Q
4. REGISTER
6. REGISTER
The P-CSCF stores the contact 7a. Server assignment Request

information (S-CSCF address) and 7b. Server assignment Answer
associates it with the terminal.
8. Service Control
9. 200 OK
10. 200 OK
11. 200 OK
Technology
IMS/TISPAN Overview
Final step
The P-CSCF receives a 200 OK message. It stores the address of the S-CSCF in charge of the UE and
forwards the message to the UE.

Section 4 Page 30
Data stored after a register
Before registration
AS
-Subscriber profile
-Opaque data
- S-CSCF address/name
HSS S-CSCF
I-CSCF -Subscriber profile
After registration
P-CSCF
DNS
DNS -Public user identity
UE -Private user identity -S-CSCF address/name
-Terminal IP address BRAS
-P-CSCF address
DSLAM
Technology
IMS/TISPAN Overview
Data stored after a registration
Node Before Registration During Registration After Registration

UE – in local Credentials Same as before Credentials
network Home Domain registration Home Domain
Proxy Name/Address Proxy Name/Address
P-CSCF – in Routing Function I-CSCF address S-CSCF address
Home or Visited UE address UE address
network Public and Private User IDs Public and Private User IDs
I-CSCF – in HSS or SLF Address S-CSCF address/name No State Information

Home network P-CSCF Network ID Because THIG is not used
Home Network contact
information
HSS User Service Profile P-CSCF Network ID S-CSCF address/name

May have session state
S-CSCF (Home) No state information HSS address/name
User profile information
Proxy address/name Same as during
P-CSCF Network ID registration
Public/Private User ID
UE IP Address

Section 4 Page 31
4.4 Functions performed during the

registration
Technology
IMS/TISPAN Overview

Section 4 Page 32
4.4 Functions performed during the registration
Functions
According to the registration procedure, match each function on the right with
the appropriate equipment on the left.
P-CSCF Entry point of a UE into the IMS/TISPAN
Assignment of an S-CSCF at UE registration

HSS
Service control (Filter Criteria)
S-CSCF
Download the IMS/TISPAN user profile from the HSS

I-CSCF
Database containing IMS/TISPAN subscriptions

UE
Generate an SIP REGISTER message
Technology
IMS/TISPAN Overview
According to the registration procedure, match each function on the right with the appropriate
equipment on the left.

Section 4 Page 33
4.4 Functions performed during the registration
initial Filter Criteria (iFC)
Why do we use iFC during registration?
Remember the example in part 4.1 when John wanted to call Betty.
After he registered his public identity, he received a welcome message

and the list of the best movies of the week….
the
d o nto
Mr Dupon rk
Welco me t netwo
Ho me.ne
you
requ est, es
to your movi
Accor ding here the best
will find of the we ek
The IMS/TISPAN allows to trigger a service during the registration and also
to trigger more than one service, with a notion of priority.
Technology
IMS/TISPAN Overview
initial Filter Criteria (iFC)
As you will see in chapter 5, Filter Criteria define when an AS must be used.
They are composed of the following elements:
AS address: address of the AS which the S-CSCF needs to contact when this particular iFC is
met. Only 1 address since iFC are defined per AS.
Trigger Point: defines when the AS must be contacted. Elements that composed the filter may
be linked by means of logical expressions (AND, OR, NOT, etc.).
iFC Priority: describes the order in which the S-CSCF should contact the ASs matching the iFC
(only needed when multiple iFC/user).
Service Information: (optional) information, transparent to the HSS and S-CSCF, which the S-
CSCF has to add to the SIP message body before sending / proxying it to the AS.
Default Handling: what the S-CSCF should do if the AS is not reachable: continue matching
lower priority triggers or release dialog.

Section 4 Page 34
4.5 Session initiation
Technology
IMS/TISPAN Overview

Section 4 Page 35
Warning
This section contains simplified procedures:

The authentication phase is missing.
Message contents are simplified.
The subscriber is in his home network.
!
The objective of this section is to introduce the function of each
equipment through the procedures, but is not to describe each
message.
Technology
IMS/TISPAN Overview
For all the session flows that follow, the topology hiding (THIG) function will not be used.
The concept of THIG will be explained later in this chapter.

Section 4 Page 36
How does the network find an IMS/TISPAN subscriber?
AS -Public
-Public user
user identity
identity
-Private
-Private user
user identity
identity (UE2)
(UE2)
IMS -Subscriber
-Subscriber profile
profile
-Opaque
-Opaque datadata
-S-CSCF2 address/name
-P-CSCF1
-P-CSCF1 address/name
address/name
-P-CSCF1
-P-CSCF1 network
network identifier
identifier
-Public
-Public user
user identity
identity S-CSCF2
-Private
-Private user
user identity
identity (UE1)
(UE1) 3 4
-Terminal
-Terminal IPIP address
address -P-CSCF2 address/name
-P-CSCF2 address/name
-Subscriber
HSS -P-CSCF2 network
-P-CSCF2 network identifier
identifier
-Subscriber profile
profile
-Public
-Public user
user identity
identity
DNS
DNS -Private
-Private user
user identity
identity (UE2)
(UE2)
5 7 -Terminal
address
S-CSCF1 8 -Subscriber
-Subscriber profile
profile
6 9
-Public
-Public user
user identity
identity
-Private
-Private user
user identity
identity (UE2)
(UE2)
2
I-CSCF -Terminal IP
address
P-CSCF2 -S-CSCF2
address/name
P-CSCF1
10 DSLAM
SGSN
1 UE 2
UE 1
-Public
-Public user
user identity
identity BRAS
GGSN -Private
-Private user
user identity
identity (UE1)
(UE1)
-Terminal
address
Technology
IMS/TISPAN Overview
In this example, we will consider that UE 1 and UE 2 are from the same network. UE 1 has services that
must be activated on the outgoing session, UE 2 has not subscribed to services.
An SIP INVITE message is sent from UE 1 to the P-CSCF.

The P-CSCF of UE 1 has stored the S-CSCF address during the registration phase, so it is able to forward
this message to the S-CSCF.
The S-CSCF triggers an AS, according to the definition of the iFC downloaded during the registration
phase of UE 1.
The AS answers using the INVITE message and may modify any fields of this message.
The S-CSCF contacts a DNS server to translate the home domain name of UE 2 in order to communicate
with the I-CSCF of his network (in our case, the I-CSCF of the same network).
The S-CSCF forwards the INVITE message to the I-CSCF.
The I-CSCF requests the address of the S-CSCF in charge of UE 2, from the HSS.
The I-CSCF forwards the INVITE message to the S-CSCF of the destination subscriber.
The S-CSCF has stored the P-CSCF address of UE 2 during the registration phase, so it is able to forward
this message to the P-CSCF.
The P-CSCF of UE 2 has stored its terminal address, so it is able to forward it the message.

Section 4 Page 37
UMTS to xDSL subscribers (1/19)
IMS
UE1 P-CSCF1 S-CSCF1 I-CSCF HSS S-CSCF2 P-CSCF2 UE2
1. INVITE
The UE determines the complete set of codecs that it is
2. 100 Trying capable of supporting for this session. It builds the message
body and sends an INVITE to the P-CSCF:
-Public user identity (from)
-Destination subscriber (to)
-UE IP address (via)
Technology
IMS/TISPAN Overview
First step
The originating User Equipment generates an INVITE message and inserts in the body of the message all
the codecs that the mobile supports.
It sends it to the P-CSCF registered during the registration phase.
A 100 Trying message is sent back to the mobile, to indicate that the network is processing the session.

Section 4 Page 38
IMS
1. INVITE
2. 100 Trying
3. INVITE
The P-CSCF adds itself to the via headers to make sure it

receives the responses. The P-CSCF sends the message to the
next hop:
-Charging parameters, ICID (P-Charging-Vector)
-P-CSCF address (record-route)
-Public user identity (from)
Technology
IMS/TISPAN Overview
Next step
The P-CSCF transfers the message to the S-CSCF associated to the subscriber in its local database.
In the INVITE message, the P-CSCF adds its own address in the record-route header, in order to receive
the answers. It also adds charging parameters which will be discussed in chapter 5.

Section 4 Page 39
IMS
1. INVITE
2. 100 Trying
3. INVITE
4. 100 Trying
5. Evaluation of iFC
To AS
The S-CSCF validates the service profile

of this subscriber and invokes any
applicable origination service logic.
Technology
IMS/TISPAN Overview
Next step
The S-CSCF analyzes the message and evaluates the iFC. If a trigger to the AS is required, it forwards the
INVITE message to the AS.

Section 4 Page 40
IMS
1. INVITE
2. 100 Trying
3. INVITE
4. 100 Trying
6. INVITE
The S-CSCF determines the network operator to whom the destination subscriber
belongs. Using a DNS query, it determines the address of the I-CSCF in charge of the
destination network.
-Charging parameters, ICID & ID of the own network, IOI (P-Charging-Vector)
-P-CSCF address & S-CSCF address (record-route)
-Public user identity (From)
Technology
IMS/TISPAN Overview
Next step
The S-CSCF requests a DNS to determine the TISPAN network in charge of the subscriber and then sends
the INVITE message to the I-CSCF of this network.
In the INVITE message, the S-CSCF adds its own address in the via header, in order to receive the
answers. It also adds charging parameters which will be discussed in chapter 5.

Section 4 Page 41
IMS
1. INVITE
2. 100 Trying
The I-CSCF queries the HSS to find out the S-CSCF of the
3. INVITE called user.
4. 100 Trying
The HSS responds with the address of the current S-CSCF
for the destination subscriber.
6. INVITE
7. 100 Trying
8 Location Info
Request/Answer
Technology
IMS/TISPAN Overview
Next step
The I-CSCF requests the address of the S-CSCF assigned to the destination subscriber, from the HSS.

Section 4 Page 42
IMS
1. INVITE
2. 100 Trying
3. INVITE
4. 100 Trying The I-CSCF forwards the INVITE message to the
S-CSCF that will handle the session termination
5. Evaluation of iFC and adds its address in the via header.
6. INVITE
7. 100 Trying
8 Location Info
Request/Answer
9. INVITE
10. 100 Trying
Technology
IMS/TISPAN Overview
Next step
The I-CSCF transfers the message to the S-CSCF associated to the subscriber. In the INVITE message, the
P-CSCF adds its own address in the via header, in order to receive the answers. It also adds charging
parameters which will be discussed in chapter 5.

Section 4 Page 43
IMS
1. INVITE
2. 100 Trying
3. INVITE
4. 100 Trying
5. Evaluation of iFC The S-CSCF forwards the INVITE message to

the next hopand adds its address in the via
6. INVITE
header.
7. 100 Trying
8 Location Info
Request/Answer
9. INVITE
10. 100 Trying

11. INVITE
12. 100 Trying
Technology
IMS/TISPAN Overview
Next step
The S-CSCF transfers the message to the P-CSCF associated to the subscriber in its local database. The S-
CSCF adds its own address in the via header, in order to receive the answers.

Section 4 Page 44
IMS
1. INVITE
2. 100 Trying
3. INVITE
4. 100 Trying
The P-CSCF determines the address of the
6. INVITE destination subscriber and forwards the
INVITE message.
7. 100 Trying
8 Location Info
Request/Answer
9. INVITE
10. 100 Trying

11. INVITE
12. 100 Trying
13. INVITE
14. 100 Trying
Technology
IMS/TISPAN Overview
Next step
The P-CSCF transfers the message to the subscriber for whom it has registered the address of his terminal
in its local database.

Section 4 Page 45
IMS
15. 183 Session Progress
The UE2 determines the complete set of

codecs that it is capable of supporting for this
session. It determines the intersection with
those appearing in the body of the INVITE
message and sends back to the originator
the resulting codecs in the message body.
Technology
IMS/TISPAN Overview
Next step
The destination UE receives the INVITE message. This message contains the list of all supported codecs
by the originating UE, in its body. The destination UE compares this list with the list of codecs it supports
and generates the SESSION PROGRESS message. It puts the common codecs that both UE supports in the
body of this message.

Section 4 Page 46
IMS
The P-CSCF authorizes the

resources necessary for this 15. 183 Session Progress
session. It requests from the RACS
to set the QoS needed for this
16. Authorise QoS
session.
Resources
Technology
IMS/TISPAN Overview
Next step
The P-CSCF receives the SESSION PROGRESS message and requests to authorize the QoS requested by the
UE from the Service Policy Decision Function (SPDF).
Then the P-CSCF transfers the message to the next hop defined in the via header and removes its address
from the via header.

Section 4 Page 47
IMS
The response is forwarded up to the P-CSCF, passing 15. 183 Session Progress
through all the items of equipment defined in the
via header. 16. Authorise QoS
Resources
Technology
IMS/TISPAN Overview
Next step
All the IMS/TISPAN items of equipment transfer the message to the next hop defined in the via header.

Section 4 Page 48
IMS
16. Authorise QoS

The P-CSCF authorizes the Resources
resources necessary for this session
and requests a QoS authorization 17. 183 Session Progress
token from the PDF. 18. 183 Session Progress
21. Authorise QoS

Resources
Technology
IMS/TISPAN Overview
Next step
The P-CSCF receives the SESSION PROGRESS message and requests the Policy Decision Function (PDF) in
order to authorize the QoS requested by the UE. The PDF gives back an authorization token, in order to
correlate the GPRS QoS with the IMS/TISPAN QoS.

Section 4 Page 49
IMS
16. Authorise QoS

The P-CSCF adds the authorisation-
Resources
token and forwards the response to
the UE. 17. 183 Session Progress
21. Authorise QoS

Resources
Technology
IMS/TISPAN Overview
Next step
The P-CSCF transfers the message to the UE in which the authorization token is placed.

Section 4 Page 50
IMS
23. PRACK
24. Resource 25. PRACK

Reservation 26. PRACK
27. PRACK
28. PRACK
The UE determines which media flows and associated codecs

should be used for this session. Then the UE1 generates a new
message’s body to include the offer in the PRACK message.
The PRACK is forwarded up to UE2 using the contexts present

in each CSCF for this session.
Technology
IMS/TISPAN Overview
Next step
The UE receives the SESSION PROGRESS message that contains the list of common codecs between the 2
UEs and also the QoS needed for this session.
The UE selects one codec and sets the QoS by doing a resource reservation. It includes the selected
codec in the PRACK message body.
The PRACK message is transferred to the destination UE using the session contexts present is each CSCF.
You can notice that the I-CSCF is not involved anymore in the session initiation.

Section 4 Page 51
IMS
23. PRACK

27. PRACK
28. PRACK
29. 200 OK
31. 200 OK 30. Resource
32. 200 OK Reservation
33. 200 OK
34. 200 OK
The PRACK message is acknowledged with a 200 OK

response. The 200 OK message will also contain a
message body response, that will correpond to an
acknowledgement of the codec selected for this
session
Then the response is forwarded up to UE1. ?
Technology
IMS/TISPAN Overview
Next step
The UE receives the PRACK message and acknowledges with a 200 OK message.
In this message, the codec that must be used for the session is acknowledged and the resource
reservation is done.

Section 4 Page 52
IMS
23. PRACK

27. PRACK
28. PRACK
29. 200 OK
31. 200 OK 30. Resource
32. 200 OK Reservation
33. 200 OK
34. 200 OK
When the resource reservation is successfully
35. UPDATE completed, the UE1 sends an UPDATE request to
the terminating endpoint to acknowledge.
36. UPDATE The UPDATE is forwarded, up to UE2.
37. UPDATE
Technology
IMS/TISPAN Overview
Next step
When the resource reservation is completed (PDP context opened with an acknowledgement of the
authorization token), the UE sends an UPDATE message to the destination UE.

Section 4 Page 53
IMS
38. UPDATE
39. UPDATE
The UPDATE request is 40. Alerting

acknowledged.
41. 200 OK
42. 200 OK
43. 200 OK 46. 180 Ringing
44. 200 OK 47. 180 Ringing
48. 180 Ringing
45. 200 OK
49. 180 Ringing
50. 180 Ringing
51. 180 Ringing
The PRACK on the 180 Ringing and the 200 OK on the PRACK are
not explicitly shown here.
Technology
IMS/TISPAN Overview
Next step
The UE receives the UPDATE message and then it starts ringing. It sends a 200 OK message to the
originating UE in order to confirm that its resources reservation is completed.
The UE sends by the way a 180 Ringing message to notify the originating UE that it must generate a ring
back tone.
PRACK and 200 OK messages are exchanged in order to confirm that the 180 Ringing message has been
received.

Section 4 Page 54
IMS
UE1 P-CSCF1 S-CSCF1 I-CSCF2
I-CSCF HSS S-CSCF2 P-CSCF2 UE2
52. 200 OK
The destination answers and sends a 200 OK to
acknowledge the INVITE message. 53. Approval of
The P-CSCF indicates that the resources QoS commit 54. Start
reserved for this session should now be Media
committed.
Technology
IMS/TISPAN Overview
Next step
When the destination subscriber off hooks his phone, the UE generates a 200 OK message.
The P-CSCF applies the QoS negotiated previously and the UE starts the media flow.

Section 4 Page 55
IMS
UE1 P-CSCF1 S-CSCF1 I-CSCF2
I-CSCF HSS S-CSCF2 P-CSCF2 UE2
52. 200 OK
The final response is forwarded to the
originating endpoint. 53. Approval of
QoS commit 54. Start
Media
55. 200 OK
56. 200 OK
57. 200 OK
58. 200 OK
59. Approval of
QoS commit
60. 200 OK
61. Start
Media
62. ACK
63. ACK
64. ACK
65. ACK
66. ACK
Technology
IMS/TISPAN Overview
Final step
The 200 OK message is forwarded to the originating UE. The P-CSCF of this subscriber sets the QoS
negotiated.
The P-CSCF applies the QoS negotiated previously and the UE starts the media flow.
It sends an ACK message, in order to respond to the 200 OK message.

Section 4 Page 56
4.6 Functions performed during the

session initiation
Technology
IMS/TISPAN Overview

Section 4 Page 57
4.6 Functions performed during the session initiation
Functions
According to the session initiation procedure, match each function listed on

the right with the appropriate equipment on the left.
P-CSCF
Negotiation
Negotiation of
of session
session
characteristics
characteristics (codecs)
(codecs)
Manages
Manages QoS
QoS
HSS
Service
Service control
control (Filter
(Filter Criteria)
Criteria)
S-CSCF CSCF
CSCF used
used to
to determine
determine thethe S-CSCF
S-CSCF in
in
charge
charge of
of aa subscriber
subscriber
I-CSCF
Database
Database which
which stores,
stores, for
for each
each subscriber,
subscriber,
the address of the S-CSCF assigned
the address of the S-CSCF assigned
UE
Reserves
Reserves resources/Starts
resources/Starts media
media
Technology
IMS/TISPAN Overview
According to the session initiation procedure, match each function listed on the right with the
appropriate equipment on the left.

Section 4 Page 58
4.7 Roaming in the IMS/TISPAN
Technology
IMS/TISPAN Overview

Section 4 Page 59
Subscriber in another IMS/TISPAN network
Service
Platform
Visited
network Mw
P-CSCF Serving
UE Gm
CSCF
Service
Home Platform
network
Visited Service Control:
Ideal architecture for I-CSCF Serving
CSCF
visited network
provided services
P-CSCF Home Service Control:
Ideal architecture for
UE Gm home network
Visited provided services
network
(local or not)
Technology
IMS/TISPAN Overview
Decision for Home Service Control was a dilemma:

For Home Network Provided services: the S-CSCF in the home network is optimal.
To eliminate dependency on visited networks for the support of the most advanced service control
features.
Because today with CAMEL (IN for mobile), users can’t get access to advanced home services in all
roaming partner networks unless all partners support the same CAMEL release as the home operator.
Note: The home network can also provide local services (services relevant to the location/position of the
user).

Section 4 Page 60
IMS/TISPAN Subscriber in a visited network

Home Service
Platform
network Service Home
Platform
P-CSCF network
Serving GGSN
CSCF Serving
CSCF I-CSCF
PDP context Border IPX

Gateway
SGSN
P-CSCF
GRX SGSN Visited
Border network
Gateway
GGSN
Proxy CSCF Proxy CSCF

in home network in visited network
Technology
IMS/TISPAN Overview
Two possible cases specified (P-CSCF in home/visited)

P-CSCF in home: roaming is solved at GPRS level (In case of 3GPP IMS). GPRS roaming
agreements already exist. Inter-operator backbones (GRX=GPRS Roaming Exchange)
interconnect all GPRS operators in the world (GRX also supports QoS).
P-CSCF in visited: roaming is solved at SIP level. GSM Association (GSMA) is extending the GRX
spec to become an IMS/TISPAN IP Exchange (IPX). The IPX also delivers SIP inter-operator
interconnect services (SIP interworking, DNS, IP version interworking, etc.). The IPX would
also interconnect mobile with fixed IMS/TISPAN operators.
Fixed operators may prefer P-CSCF/BRAS in visited-domain.

Easier to deliver QoS.
Avoid Tromboning of RTP.

Section 4 Page 61
Session flow example when subscribers are roaming
BT.com Vodafone.com
AS AS
HSS 3 HSS
DNS I-CSCF
8
(THIG)
6
4
S-CSCF 5 7 S-CSCF
2 Home 9 Home
DNS DNS
P-CSCF P-CSCF
INVITE
Bearer 10
SGSN 1 BRAS DSLAM

GGSN
orange.fr Visited dialog.lk Visited
Technology
IMS/TISPAN Overview
Roaming with IMS/TISPAN

The originating subscriber is from BT.com and is roaming in France in orange.fr.
The destination subscriber is from Vodafone.com and is roaming in Sri-Lanka in dialog.lk.
1. The user sends the INVITE message to the P-CSCF discovered during the registration.
2. The P-CSCF sends the INVITE message to the S-CSCF address stored during the registration.
3. The S-CSCF triggers to the AS if the filter criteria of the subscriber required it.
4. The S-CSCF sends a request to a DNS to resolve the address of the home destination user
network.
5. The S-CSCF sends the INVITE message to the I-CSCF (Because of THIG Function),
6. The I-CSCF contacts the HSS to determine which S-CSCF is in charge of the destination user.
7. The I-CSCF sends INVITE message to the S-CSCF.
9. The S-CSCF sends the INVITE message to the P-CSCF address stored during the registration.
10. The P-CSCF sends the INVITE message up to the destination user.

Section 4 Page 62
Register without Topology Hiding (THIG)
IMS
AS
-IMPU/IMPI
-Opaque data
-Profile
-S-CSCF address 7
HSS
6
4 8
5
S-CSCF -IP address
I-CSCF 9 -IMPU/IMPI
3
-P-CSCF address
10 -Profile
DNS
DNS 2
-IP address
P-CSCF
DSLAM -IMPU/IMPI
1
BRAS
-S-CSCF address
UE
Technology
IMS/TISPAN Overview

Section 4 Page 63
Register with Topology Hiding (THIG)
200 OK sip:registrar.home1.net SIP/2.0
Record-route: UE,P-CSCF,I-CSCF,S-CSCF
IMS
Max-Forwards: 70
From: <sip:user1_public1@home1.net>; AS
To: <sip:user1_public1@home1.net> -IMPU/IMPI
-Opaque data
Call-ID: apb03a0s09dkjdfglkj49111 -Profile
CSeq: 1 REGISTER
-S-CSCF address 7
Supported: path
Content-Length: 0
HSS
6
4 8
THIG
5
200 OK sip:registrar.home1.net SIP/2.0 S-CSCF -IP address
Record-route: I-CSCF I-CSCF 9 -IMPU/IMPI
Max-Forwards: 70
3
-P-CSCF address
From: <sip:user1_public1@home1.net>;
To: <sip:user1_public1@home1.net> 10 -Profile
DNS
DNS 2
Call-ID: apb03a0s09dkjdfglkj49111
-IP address
CSeq: 1 REGISTER P-CSCF
Supported: path DSLAM -IMPU/IMPI
1
Content-Length: 0 BRAS
- I-CSCF address
UE
Technology
IMS/TISPAN Overview

Section 4 Page 64
Session flow example when subscribers are roaming
BT.com AS Vodafone.com
AS
HSS DNS 4
HSS
10
5 I-CSCF I-CSCF
(THIG) (THIG) 8
S-CSCF S-CSCF
6
3 7 9
11
I-CSCF I-CSCF
(THIG) Home (THIG) Home
2 12
DNS DNS
P-CSCF P-CSCF
INVITE
Bearer 13
SGSN 1 BRAS DSLAM

GGSN
Technology
IMS/TISPAN Overview
Roaming with IMS/TISPAN

The originating subscriber is from BT.com and is roaming in France in orange.fr.
The destination subscriber is from Vodafone.com and is roaming in Sri-Lanka in dialog.lk.
There is no agreement between BT.com and Vodafone.com. So, BT.com and Vodafone.com use the
Topology HIdinG (THIG) function in his I-CSCF in order to protect and mask its network element.
1. The user sends the INVITE message to the P-CSCF discovered during the registration.
2. The P-CSCF sends the INVITE message to the I-CSCF address stored during the registration
(Because of THIG Function), .
3. The I-CSCF sends the INVITE message to the S-CSCF.
5. The S-CSCF sends a request to a DNS to resolve the address of the home destination user
network.
6. The S-CSCF sends the INVITE message to the I-CSCF (Because of THIG Function),
7. The I-CSCF sends the INVITE message to the destination user network
8. The I-CSCF contacts the HSS to determine which S-CSCF is in charge of the destination user.
9. The I-CSCF sends INVITE message to the S-CSCF.
11. The S-CSCF sends the INVITE message to the I-CSCF address (Because of THIG Function), .
12. The I-CSCF sends the INVITE message to the P-CSCF address.
13. The P-CSCF sends the INVITE message up to the destination user.

Section 4 Page 65
Section 4 Page 66
4.8 Exercises
Technology
IMS/TISPAN Overview

Section 4 Page 67
4.8 Exercises
Order the IMS/TISPAN elements
During a session initiation, the INVITE message is sent

over different elements before being transferred to the
destination UE.
In this example, UE1 is from network 1 and it wants to

communicate with UE2 from network 2. The THIG function
is not used. Only UE1 has subscribed to added-value
services.
Each element routes an INVITE message to the next hop.

Place each element according to its function, in the empty
boxes, in order to route the INVITE message.
Time allowed:
10 minutes
Technology
IMS/TISPAN Overview
DSLAM
Network1.net
UE 2
BRAS
AS1
HSS1
DNS
DNS
P-CSCF2
AS2
S-CSCF1
I-CSCF1 S-CSCF2
I-CSCF2
P-CSCF1 HSS2
Network2.net
SGSN
UE 1
GGSN
Section 4 Page 68
UE 1
S-CSCF1
HSS1
P-CSCF1
AS1
I-CSCF1
S-CSCF2
AS2
INVITE
HSS2
P-CSCF2
I-CSCF2
P-CSCF2
UE 2

Section 4 Page 69
4.8 Exercises
Functions of the IMS/TISPAN elements
If you consider the registration and the session initiation,

match each function to the element that performs it.
Time allowed:
10 minutes
Technology
IMS/TISPAN Overview
1 Manages
Manages QoS
QoS
2 Topology
Topology Hiding
Hiding 3 Manages
Manages services
services such
such as
as PoC,
PoC, IM/PM
IM/PM or
or GLMS
GLMS
4 Negotiation
Negotiation of
of session
session characteristics
characteristics (codecs)
(codecs) 5 Reserves
Reserves resources/Starts
resources/Starts media
media
6 Manages
Manages roaming
roaming rights
rights
7 Service
Service control
control (Filter
(Filter Criteria)
Criteria) Assignment
8 Assignment of
of an
an S-CSCF
S-CSCF at
at UE
UE registration
registration
9 CSCF
CSCF used
used to
to determine
determine the
the S-CSCF
S-CSCF in
in charge
charge of
of aa
subscriber
subscriber
10 Database
Database which
which stores,
stores, for
for each
each subscriber,
subscriber, the
the address
address
of
of the
the S-CSCF
S-CSCF assigned
assigned
11 Generates
Generates an
an SIP
SIP REGISTER
REGISTER message
message
Downloads 13 Database
Database containing
containing IMS/TISPAN
IMS/TISPAN subscriptions
subscriptions
12 Downloads the
the IMS/TISPAN
IMS/TISPAN user
user
profile from the HSS
profile from the HSS
14 Entry
Entry point
point of
of other
other IMS/TISPAN
IMS/TISPAN networks
networks into
into
the
the IMS/TISPAN
IMS/TISPAN
15 Entry
Entry point
point of
of aa UE
UE into
into the
the IMS/TISPAN
IMS/TISPAN
Section 4 Page 70
UE
P-CSCF
S-CSCF
HSS
AS
I-CSCF

Section 4 Page 71

for this module
Technology
IMS/TISPAN Overview

Section 4 Page 72
End of Module
Technology
IMS/TISPAN Overview

Section 4 Page 73
Section 5
5
IMS/TISPAN subscription and
charging


Section 5 Page 1
Blank Page
IMS/TISPAN subscription and charging 5 2
Technology
IMS/TISPAN Overview
Document History
07 2007-02-19 DUVAL, Erwan

Section 5 Page 2
Objectives
To be able to list the content of an IM-HSS database and to

sort the different identities into categories.
Technology
IMS/TISPAN Overview

Section 5 Page 3
Objectives [cont.]
Technology
IMS/TISPAN Overview

Section 5 Page 4
Table of Contents
Page
5.1 Subscription in an IMS/TISPAN network 7
IMS/TISPAN and the Wayne family 8
IMS/TISPAN and the Wayne family 9
5.2 IM-HSS content 10
HSS functional architecture 11
UPSF functional architecture 12
Data provided by HSS / SLF 13
IMS private identity 14
IMS public identity 15
Implicit registration set 16
Authentication and authorization data 17
User subscription profile 18
User location data 19
Opaque data 20
Recap 21
5.3 AS triggering 22
Initial Filter Criteria 23
Service Point Trigger 24
Trigger Point 25
Application Server 26
Initial Filter Criteria 27
5.4 Authentication in the IMS/TISPAN 29
Authentication Key Agreement (AKA) 30
Why an agreement? 31
TechnologyAKA in the IMS/TISPAN (1/3) 32
IMS/TISPANAKA
Overview
in the IMS/TISPAN (2/3) 33
AKA in the IMS/TISPAN (3/3) 34
5.4 SIP Digest 35
Digest 36
How it works? 37
Digest in the IMS/TISPAN (1/3) 38
5.5 Charging in IMS/TISPAN 41
2 ways to perform charging 42
OFF line charging 43
ON line charging (1/2) 44
ON line charging (2/2) 45
5.6 Charging identifiers 46
IMS Charging IDentifier (ICID) 47
GPRS Charging ID (GCID) 48
Inter Operator Identifiers (IOI) 49
5.7 Charging and roaming 50
Charging when roaming 51
5.8 Exercise 52
Exercise 53
End of Module 56

Section 5 Page 5
Technology
IMS/TISPAN Overview This page is reserved

Section 5 Page 6
5.1 Subscription in an IMS/TISPAN network
Technology
IMS/TISPAN Overview

Section 5 Page 7
IMS/TISPAN and the Wayne family
John, the father wayne.business@operator.fr
john.wayne@operator.fr
Betty, the mother
betty.wayne@operator.fr
Bruce, the son
family.wayne@operator.fr
bruce.wayne@operator.fr Tel:+331233445
Technology
IMS/TISPAN Overview
The Wayne family
The Wayne family is composed of the father, the mother and their child.
Each of them has a mobile SIP phone. The father uses his phone for private and business purposes.
Onto his business subscription, he has a specific subscription, allowing roaming and discount price.
In the Wayne’s home, a fixed SIP phone is available for all the family.

Section 5 Page 8
IMS/TISPAN and the Wayne family
IMPU Business
Business profile
profile
IMPI
IMPI wayne.business@operator.fr
Mobile1@operator.fr
Mobile1@operator.fr
IMPU
John.wayne@operator.fr
IMPI
IMPI
IMPU
Mobile2@operator.fr
Mobile2@operator.fr betty.wayne@operator.fr
IMS
IMS
subscription
subscription
Wayne
Wayne profile
profile
Wayne
Wayne
family
family IMPI IMPU
IMPI
bruce.wayne@operator.fr
Mobile3@operator.fr
Mobile3@operator.fr
IMPU
+3312345678
IMPI
IMPI
fixe@operator.fr
fixe@operator.fr IMPU
family.wayne@operator.fr
Technology
IMS/TISPAN Overview
IMS subscription
This model represents a “Functional” model close to the business model.
An IMS Subscription defines a “contract” between a subscriber and the network operator / service
provider; a subscriber may be a user (single person or family) or a complex organization.
An IMS Private Identity (IMPI) is a name given by the Network Operator which has the format of a
Network Access Identifier (RFC2486) and which is used for registration, authorization, administration and
accounting (name@domain). It is stored on the ISIM as well as on the HSS.
An IMS Public Identity (IMPU) is an address used for the routing of SIP messages.
It has either the format of an SIP-URI (RFC 3261 [26]) or the formatof a TEL-URI (RFC 3966 [22]) and may
be shared by multiple IMS users of the same IMS subscription.
E.g., to reach all IMS users of the same IMS subscription (e.g., a family) on a unique Public User Identity.
A Service Profile is composed of services-related data of the IM-HSS, Application Server Triggering data
(IFC) and Core Network Service Authorization Data

Section 5 Page 9
5.2 IM-HSS content
Technology
IMS/TISPAN Overview

Section 5 Page 10
5.2 IM-HSS content
HSS functional architecture
AS
IMS
HSS S-CSCF2
HSS
IM-HSS
S-CSCF1
HLR-AuC AAA
I-CSCF
P-CSCF2
P-CSCF1
SGSN
UE 1
GGSN
Technology
IMS/TISPAN Overview
HSS functional architecture
The HSS is composed of different entities:

The HLR-AuC more related to the Access Network.
AAA Database more related to the Access Network (Optional)
The IM HSS related to the IMS platform layer and to the AS layer. (UPSF in case of TISPAN)

Section 5 Page 11
5.2 IM-HSS content
UPSF functional architecture
AS
IMS
UPSF S-CSCF2
HSS
IM-HSS
S-CSCF1
AAA
I-CSCF
P-CSCF2
DSLAM
P-CSCF1
UE 2
BRAS
Technology
IMS/TISPAN Overview
UPSF : User Profile Server Function

Section 5 Page 12
5.2 IM-HSS content
Data provided by HSS / SLF
Applications
Applications maymay host
host the
the user’s
user’s services-related
services-related
data
data into
into the
the opaque
opaque data
data storage
storage area.
area.
Opaque
DATA
Home
Opaque Profile
DATA AAA HLR DATA
IM-HSS
Home
Profile HSS
AAA HLR DATA
IM-HSS
HSS
SLF
Subscription
Subscription for
for circuit
circuit •Naming
•Naming and
and Addressing
Addressing data
data (IMPI
(IMPI // IMPU)
IMPU)
and
and packet
packet access
access •Authentication
•Authentication and
and Authorisztion
Authorisztion data
data (e.g.,
(e.g., roaming)
roaming)
•User
•User Subscription
Subscription Profile
Profile (e.g.,
(e.g., service
service triggers)
triggers)
•User
•User Location
Location Data
Data (e.g.,
(e.g., dynamic
dynamic S-CSCF
S-CSCF address)
address)
Technology
IMS/TISPAN Overview
Data provided by HSS / SLF
Subscription Locator Function (SLF)

Operators having more than one independently addressable HSS, use an SLF to find the HSS for a given
subscriber. The SLF is not needed in case of single HSS environment (HSS server farm) or preconfigured
HSS in the AS.
Home Subscriber Server (HSS)

The HSS extends the concept of the HLR/AuC with the user profile data for IMS => IM-HSS.
The IMS-HSS is independent from the access and can be used for mobile as well as for fixed subscribers:
The Home Profile Data provides all user profile data related to call/session control:
- Naming and addressing data (e.g., SIP-URI).
- Authentication and authorization data (e.g., password).
- User subscription profile (e.g., service triggers).
- User location data (e.g., dynamic S-CSCF address).
The Opaque data is a storage area provided by the HSS towards the Application Servers:
• Applications may host the user’s services-related data into the opaque data
storage area.
• The HSS is not aware about the structure of this data.

Section 5 Page 13
5.2 IM-HSS content
IMS private identity
Home
•Naming and addressing data (IMPI / IMPU)
Profile •Authentication and authorization data (e.g., roaming)
DATA
•User subscription profile (e.g., service triggers)
•User location data (e.g., dynamic S-CSCF address)
is used for registration, authorization, administration and accounting

and has the format of a Network Access Identifier (RFC2486)
(name@domain)
May be created from the IMSI:

234150999999999@ims.mnc015.mcc234.3gppnetwork.org
Technology
IMS/TISPAN Overview
Data provided by the HSS / SLF
The private user identity shall take the form of a Network Address Identifier (NAI) and shall have the
username@domain form as specified in clause 3 of RFC 2486 [25].
NOTE:
It is possible for a representation of the IMSI to be contained within the NAI for the private identity.
If there is no ISIM application, the private user identity is not known.
If the private user identity is not known, the private user identity shall be derived from the IMSI.
The following steps show how to build the private user identity out of the IMSI:
The result will be a private user identity of the form

"<IMSI>@ims.mnc<MNC>.mcc<MCC>.3gppnetwork.org". For example, if the IMSI is 234150999999999 (MCC
= 234, MNC = 15), then the private user identity takes the form
234150999999999@ims.mnc015.mcc234.3gppnetwork.org

Section 5 Page 14
5.2 IM-HSS content
IMS public identity
Home
Profile •Authentication and Authorization data (e.g., roaming)
DATA
is used to route SIP messages and is defined in two formats:

•SIP-URI (name@domain)
•TEL-URI (E.164: CC NDC SN)
May be created from the IMSI and may be equal to the private
Identity.
Technology
IMS/TISPAN Overview
Data provided by the HSS / SLF
The public user identity shall take the form of either an SIP-URI (RFC 3261) or a TEL-URI (RFC 2806):
An SIP-URI for a public user identity shall take the form "sip:user@domain".
A TEL-URI for a public user identity shall take the E.164 format: CC NDC SN.
If there is no ISIM application to host the public user identity, a temporary public user identity shall be
derived, based on the IMSI. The temporary public user identity shall be of the form "user@domain" and
shall therefore be equal to the private user identity.
EXAMPLE: "sip:234150999999999@ims.mnc015.mcc234.3gppnetwork.org"

Section 5 Page 15
5.2 IM-HSS content
Implicit registration set
IMS
IMS
subscription
subscription
Wayne
Wayne Registration of one IMPU of an « implicit registration
family
family
set » means that all IMPUs are registered
IMPI
IMPI
IMPU Business
Mobile1@operator.fr Business profile
profile
Mobile1@operator.fr wayne.business@operator.fr
IMPU
John.wayne@operator.fr
Wayne
Wayne profile
profile
Implicit Registration Set
John the father wayne.business@operator.fr
john.wayne@operator.fr
Technology
IMS/TISPAN Overview
Implicit registration set
The implicit registration set provides the IMS user with the possibility to register a set of public user
identities in one registration request.
When an IMS user registers one public user identity belonging to an implicit registration set, all other
public user identities belonging to this implicit registration set will be registered as well.
When an IMS user removes one public user identity from an implicit registration set, all other public user
identities belonging to this implicit registration set will be removed as well.
An implicit registration set may be shared by multiple IMS users. If, for instance, two fixed phones are in
one house with for each its own IMPU. An implicit registration set may be composed of these 2 IMPUs.
The registration of one phone implies automatically the registration of the other phone.

Section 5 Page 16
5.2 IM-HSS content
Authentication and authorization data
Home
DATA
•User location data (e.g. dynamic S-CSCF address)
Barring indication
List of authorized visited network identifiers
Data related to authentication and ciphering
Subscribed media profile identifier
Technology
IMS/TISPAN Overview
Authentication and Authorization data
Barring indication
Flag associated to each public identity to indicate that the identity is barred from any IMS
communication.
List of authorized visited network identifiers

The list of authorized visited network identifiers is associated with the public user identity of IMS
subscribers to indicate which visited network identifiers are allowed for roaming.
Data related to authentication and ciphering

For contents of Random Challenge (RAND), Expected Response (XRES), Cipher Key (CK), Integrity Key(IK)
and Authentication Token (AUTN), see the "UMTS authentication procedure" later in this chapter.
Subscribed media profile identifier

The subscribed media profile identifier identifies a set of session description parameters that the
subscriber is authorized to request. The translation of the profile identifier into the set of subscribed
media is performed in the S-CSCF based on the operator configuration.

Section 5 Page 17
5.2 IM-HSS content
User subscription profile
Home
DATA
Initial Filter Criteria

Service indication
Shared iFC set identifier
CAMEL marks (IM-SSF)
Technology
IMS/TISPAN Overview

A set of Initial Filter Criteria are stored for each user, for each application or service that the user
request may invoke (see 3GPP TS 23.218).
Each set of filter criteria includes the Application Server address, AS priority, Default Handling,
Subscribed media, trigger points and optional service information.
Service indication
Identifier of one set of services-related opaque data, which is stored in an HSS in an operator network. It
shall be unique within an operator network. The HSS may allocate, per user and value of service
indication, memory space to implement a data repository to store transparent data (see 3GPP TS
29.328).
Shared iFC set identifier
A Shared iFC set identifier identifies sets of Initial Filter Criteria that may be shared by more than one
subscriber. The translation of a Shared iFC set identifier into the set of initial Filter Criteria is performed
in the S-CSCF based on operator configuration.
Customized Applications for Mobile network Enhanced Logic (CAMEL) marks
This feature provides the mechanisms to support services for the IP Multimedia Core Network (IM CN)
Subsystem. An additional equipment called IM-SSF is added in the IMS network, in order to perform a
gateway function between the S-CSCF and the CAMEL Service Environment (CSE). For the S-CSCF, the CSE
is considered as an AS and the access to the CSE is defined using iFC.

Section 5 Page 18
5.2 IM-HSS content
User location data
Home
DATA
Registration status
S-CSCF name
Diameter client address of the S-CSCF
Technology
IMS/TISPAN Overview
User location data
Registration Status
The Registration Status, specified in 3GPP TS 29.228, contains the status of registration of a public user
identity
Not Registered State: the user is not Registered and has no S-CSCF assigned.
Registered State: the user is Registered at the request of the user and has an S-CSCF assigned.
Unregistered State: the user is not Registered but has a serving S-CSCF assigned to execute
Unregistered state services.
S-CSCF Name
The S-CSCF Name identifies the S-CSCF allocated to the subscriber when the subscriber is registered to IP
multimedia services. It is used during mobile terminated sessions set-up and re-registrations. The S-CSCF
Name shall be in the form of an SIP URL as defined in IETF RFC 3261 and RFC 2396.
Diameter client address of the S-CSCF
The diameter client address of the S-CSCF identifies the diameter client in the S-CSCF when the
subscriber is registered to IP multimedia services. It is used in requests sent by the HSS to the S-CSCF.
The format of the diameter client address is the diameter identity defined in draft-ietf-aaa-diameter-08.
The diameter identity is a URL-syntax string, the ports are used to listen to incoming connections.
E.g., aaa://host.abc.com:1812;transport=tcp;protocol=diameter

Section 5 Page 19
5.2 IM-HSS content
Opaque data
Opaque
DATA
Repository Data
This information element contains
transparent data. A data repository may be
shared by more than one AS implementing
the same service.
Technology
IMS/TISPAN Overview
Opaque data (also called transparent data)
Data that is understood syntactically but not semantically by the HSS. It is a data that an AS may store in
the HSS to support its service logic.
One example is a data that an AS stores in the HSS, using it as a repository.

Section 5 Page 20
5.2 IM-HSS content
Recap
IM-HSS
Home profile data
IMS subscription
Private user Naming and

identity addressing data Opaque data
Public user Implicit

Public user
identity registration set
identity
Service profile
Opaque data
Authentication and Authorization data

User location data
Technology
IMS/TISPAN Overview
Recap

Section 5 Page 21
5.3 AS triggering
Technology
IMS/TISPAN Overview

Section 5 Page 22
5.3 AS triggering
<Priority>:
integer
Application
Service Information
Server
Trigger Point WHAT?
Service Point Trigger
WHEN?
Technology
IMS/TISPAN Overview
Initial Filter Criteria (iFC)

iFC are stored in the HSS as part of the user profile and are downloaded to the S-CSCF upon user
registration, or upon a terminating initial request for an unregistered user if unavailable. They represent
a provisioned subscription of a user to an application. After downloading the User Profile from the HSS,
the S-CSCF assesses the filter criteria. Initial Filter Criteria are valid throughout the registration lifetime
of a user or until the User Profile is changed.
Application Server: Address to be used to access the Application Server for a particular
subscriber. The Service Information is optionally part of an initial Filter Criteria. If it is
available from the initial Filter Criteria the S-CSCF shall include it into the body of the SIP
request which is sent from the S-CSCF to the AS.
Trigger Point: Trigger Points are the information the S-CSCF receives from the HSS that defines
the relevant Service Point Trigger (SPT) for a particular application. They define the subset of
initial SIP requests received by the S-CSCF that should be sent or proxied to a particular
application server. When the S-CSCF receives an initial SIP request, it evaluates the filter
criteria one by one. If the initial SIP request matches the filter criteria, the S-CSCF proxies the
SIP request to the corresponding SIP AS/IM-SSF/OSA SCS.
Priority indicates the priority of the Filter Criteria. A Filter Criteria with a higher value of
Priority Number shall be assessed after the Filter Criteria with a smaller Priority Number have
been assessed. The same priority shall not be assigned to more than one initial Filter Criterion.

Section 5 Page 23
5.3 AS triggering
<ConditionNegative>: boolean
Session
<Group>: list of integer
Description
Request URI
<SessionDescription>
<RequestURI>: string
<line>:string
Condition?
<Content>:string
SIP Method Session Case

<Method>: string <SessionCase>:
SIP Header 0 (ORIGINATING_SESSION)
<SIPHeader> 1 (TERMINATING_SESSION)
<Header>: string 2 (TERMINATING_UNREGISTERED)
<Content>: string
Technology
IMS/TISPAN Overview
Service Point Trigger (SPT)

The attribute ConditionNegative of the class Service Point Trigger defines whether the individual SPT
instance is negated:
<ConditionNegative>: 0 means SPT positive
<ConditionNegative>: 1 means NOT logical expression
The attribute Group is used in trigger point to group SPT (see next slide).
The condition is constructed according to one of the following possibilities:
Request-URI defines SPT for the Request-URI. Ex:
<RequestURI>sip:bruce.wayne@operator.fr</RequestURI>
SIP Method defines SPT for the SIP method.

Ex: <Method>INVITE</Method>
SIP Header defines SPT for the presence or absence of any SIP header. The attribute Header
identifies the SIP Header, and the Content attribute defines the value of the SIP Header if
required.
Session Case class represents an enumerated type, with possible values indicating if the filter
should be used by the S-CSCF handling the Originating, Terminating for a registered end user or
Terminating for an unregistered end-user services.
Session Description Information class defines SPT for the content of any SDP field within the
body of an SIP method. The Line attribute identifies the line inside the session description.
Content is a string defining the content of the line identified by Line.

Section 5 Page 24
5.3 AS triggering
Trigger Point
•Trigger Point = A AND B AND (C OR D)

Trigger Point CNF
•Trigger Point DNF = A OR B OR (C AND D)
<ConditionTypeCNF>: 0
1 to n
SPT
Service Point Trigger (Method=”INVITE”) OR

(Method=” MESSAGE”) OR
{ Method = “SUBSCRIBE”
(NOT Header = “from” Content = “joe”)
AND
} Group attribute in SPT
Technology
IMS/TISPAN Overview
Trigger Point
A Trigger Point expression is constructed out of atomic expressions (called Service Point Trigger) linked
by Boolean operators AND, OR and NOT. Any logical expression constructed that way can be transformed
into forms called Conjunctive Normal Form (CNF) and Disjunctive Normal Form (DNF).
If <ConditionTypeCNF>: 1 it is an AND of STP in a different group and an OR of SPT within the

same group.
If <ConditionTypeCNF>: 0 it is an OR of STP in a different group and an AND of SPT within the

same group.
Let's take the following example of trigger:

Method = “INVITE” OR Method = “MESSAGE” OR (Method=”SUBSCRIBE” AND NOT Header = “from” Content
= “joe”)
The trigger can be split into the following atomic expressions with <ConditionTypeCNF>= 0:
Method=”INVITE” group 0
Method=”MESSAGE” group 1
Method=”SUBSCRIBE” group 2
NOT header=”from” Content =”joe” group 2

Section 5 Page 25
5.3 AS triggering
Application Server
Application Server
<ServerName>: SIP URI

<DefaultHandling>:
0 (SESSION_CONTINUED)
1 (SESSION_TERMINATED)
Optional additional
information
Service Information
<ServiceInfo>: string
Technology
IMS/TISPAN Overview
Application Server
The Application Server defines the application server which is contacted, if the trigger points are met.
ServerName is the SIP URL of the application server to contact.
Default Handling determines whether the dialog should be released if the Application Server
could be reached or not.
The service information class allows to download the S-CSCF information that is to be transferred
transparently to an Application Server when the trigger points of a filter criterion are satisfied.
ServiceInformation is a string conveying information.
The Application Server class contains zero or one instance of the service information class.

Section 5 Page 26
5.3 AS triggering
According to the XML code present on the next page, answer the following
questions:
• Write down the condition when the iFC will be used in the form:
(A and/or B) or/and (C and/or D)
•What is the address that will be used to contact the application server?
• What will happen if the AS is not reachable?
• If an iFC with priority 1 is added to a subscriber profile, which IFC will be

activated first, the IFC with priority 1 or the one listed on the next page?
Technology
IMS/TISPAN Overview

Write down the condition when the iFC will be used in the form: (A and/or B) or/and (C and/or D)
What is the address that will be used to contact the application server?
What will happen if the AS is not reachable?
If an iFC with priority 1 is added to a subscriber profile, which IFC will be activated first, the IFC with
priority 1 or the one listed on the next page?

Section 5 Page 27
<InitialFilterCriteria>
<Priority>0</Priority>
<TriggerPoint>
<ConditionTypeCNF>0</ConditionTypeCNF>
<SPT>
<ConditionNegated>0</ConditionNegated>
<Group>0</Group>
<Method>INVITE</Method>
</SPT>
<SPT>
<Group>0</Group>
<SessionCase>0</SessionCase>
</SPT>
<SPT>
<Group>1</Group>
<Method>REGISTER</Method>
</SPT>
</TriggerPoint>
<ApplicationServer>
<ServerName>sip:prepaid@homedomain.com</ServerName>
<DefaultHandling>1</DefaultHandling>
</ApplicationServer>
</InitialFilterCriteria>

Section 5 Page 28
5.4 Authentication in the IMS/TISPAN
Technology
IMS/TISPAN Overview

Section 5 Page 29
Authentication Key Agreement (AKA)
RAND
HSS
f5 AK Where AK ⊕ (AK ⊕ anything )= anything
K
K
AUTN
f1 MAC
RAND
SQN ( SQN ⊕ AK ) || AMF ||MAC
AMF
K
RAND
f2 f3 f4
XRES CK IK
AV5 := RAND ||XRES ||CK|| IK|| AUTN
Technology
IMS/TISPAN Overview
Review: UMTS authentication
The quintets are used for the authentication and ciphering procedures in the UMTS network.
An algorithm, called f5, is applied to the RAND number associated with an authentication Key (K) to
obtain an Authentication Key (AK). This Key is special because:
(AK xor anything) xor AK = anything
A SeQuence Number (SQN) and the Authentication Management Field (AMF) are used to generate the
AUthentication TokeN (AUTN) which is added to complete the quintet.
An algorithm, called f2, is applied to the RAND number associated with an authentication Key (K) to
obtain an eXpected RESponse (XRES).
This same RANDom number (RAND) is combined with the same key K and subjected to another algorithm,
f3, to obtain the Ciphering Key (CK).
The Integrity Key (IK) is calculated from the K key and the RAND subjected to the algorithm f4.
The Authentication vector 5 is composed of the RAND, the XRES, the CK, the IK and the AUthentication
TokeN (AUTN).

Section 5 Page 30
Why an agreement?
UE RAND AUTN AUTN

Start
Start
RAND
RAND
f5 AK
K
( SQN ⊕ AK ) || AMF || MAC XRES
( SQN ⊕ AK ) Å AK } SQN IK
No
Network CK
SQN – SQN-1 < ∆
K
f1
AV5
MAC
RAND
Authentication
SQN
refused
AMF
MAC = MAC No
No
RAND
XRES
XRES XRES
K
f2 XRES = Ok
Technology
IMS/TISPAN Overview
Why an agreement?
Because both the UE or the network may refuse each other.
The UE will first compare the sequence number receives from the network, to the one stored onto the
SIM card during the previous authentication. If they are different too much, the UE refuses the network.
Then the UE computes information to find the identity of the network, and it compares the identity
found, with the one it received in the AUTN. Again, if they are different the UE refuses the network.
After all, if the mobile accepts the network, it sends back the XRES, the network receives it and
compares it with the one it has. If they are different, the network refuses the UE.

Section 5 Page 31
AKA in the IMS/TISPAN (1/3)
IMS/TISPAN
UE
RAN GPRS/DHCP P-CSCF DNS I-CSCF S-CSCF HSS
1. P-CSCF DISCOVERY
2. REGISTER
3. DNS: DNS-Q
IMPI / IMPU 4. REGISTER
5a. Cx-Query/Cx-Select-Pull
IMPI / IMPU 5b. Cx-Query Resp/Cx-Select-Pull Resp
6. REGISTER
IMPI / IMPU 7a. Cx-Put/Cx-Pull
7b. Cx-Put Resp/Cx-Pull Resp
AV55
8. Authentication
vector selection
Technology
IMS/TISPAN Overview
First step
The mobile sends a REGISTER message and includes its private and public identity. The S-CSCF checks the
status of the public identity and determines that the subscriber has not been authenticated.
The HSS returns n Authentication Vectors 5 for future authentications.

Section 5 Page 32
IMS/TISPAN
UE
IK / CK XRES
8. Authentication
Vector Selection
9. 401 Unauthorised
10. 401 Unauthorised RAND
RAND // AUTN
AUTN // IK
IK // CK
CK
11. 401 Unauthorised
RAND
RAND // AUTN
AUTN // IK
IK // CK
CK
12. Generation
of response and
RAND / AUTN
session keys
13. REGISTER
14. DNS: DNS-Q
XRES
15. REGISTER
XRES 16. Cx: User registration status query
Technology
IMS/TISPAN Overview
Next step
The S-CSCF keeps the XRES from the AV5 and sends the rest of the vector up to the P-CSCF.
The P-CSCF keeps the IK and CK to cipher the communication between the UE and the
P-CSCF using the IPSec protocol.
Then the P-CSCF sends the AUTN and the RAND to the UE. It computes data and sends back the XRES into
a new REGISTER message.

Section 5 Page 33
IMS/TISPAN
UE
17. REGISTER
XRES
18.
Authentication
19. Cx: S-CSCF registration
notification
20. Service Control
21. 200 OK
22. 200 OK
23. 200 OK
Technology
IMS/TISPAN Overview
Final step
The S-CSCF receives the REGISTER message back and authenticates the subscriber. Then, it updates the
status of the subscriber in the HSS and downloads the iFC.

Section 5 Page 34
5.4 SIP Digest
Technology
IMS/TISPAN Overview

Section 5 Page 35
Digest
Realm
Nonce
Algorithm Response
Password
MD5
IMPI
Cnonce UE
IMPU
Realm
Nonce
Algorithm
HSS
Password Response
IMPI MD5
Cnonce
IMPU
Technology
IMS/TISPAN Overview
Realm : Part of the Public Identity (ie alcatel.com).

Nonce : Unique random string generated by the HSS.
Cnonce : Unique random string generated by the UE.

Section 5 Page 36
How it works?
UE
Network
Request
HSS
Challenge (Nonce) IMPI
IMPU
Realm
Nonce
IMPI
IMPU Request with credentials (Cnonce, Response) IMPI
Realm IMPU
Nonce Realm
Cnonce Nonce
Response Cnonce
Response
Technology
IMS/TISPAN Overview

Section 5 Page 37
5.4 Authentication in the IMS/TISPÄN
Digest in the IMS/TISPAN (1/3)
IMS
UE
1. P-CSCF DISCOVERY
2. REGISTER
3. DNS: DNS-Q
IMPI / IMPU 4. REGISTER
5a. Cx-Query/Cx-Select-Pull
IMPI / IMPU 5b. Cx-Query Resp/Cx-Select-Pull Resp
6. REGISTER
IMPI / IMPU 7a. Cx-Put/Cx-Pull
7b. Cx-Put Resp/Cx-Pull Resp
Nonce
Nonce
Technology
IMS/TISPAN Overview
First step
The mobile sends a REGISTER message and includes its private and public identity. The S-CSCF checks the
status of the public identity and determines that the subscriber has not been authenticated.
The HSS returns a nonce for the authentication.
Session Initiation Protocol

Request-Line: REGISTER sip:home1.net SIP/2.0
Message Header
Call-ID: h7ql8b@192.168.210.15
CSeq: 1000 REGISTER
From: <sip:erwan.duval@home1.net>;tag=tkigud
To: <sip: erwan.duval@home1.net>
Max-Forwards: 70
Authorization: Digest username=" erwan.duval@home1.net",realm="home1.net",uri="sip:home1.net",nonce="",response=""
P-Preferred-Identity: <sip: erwan.duval@home1.net>
Security-Client: ipsec-3gpp; alg=hmac-sha-1-96; spi-c=23456789;spi-s=12345678;port-c=2468; port-s=5060
Contact: <sip:192.168.210.15:5062>
Route: <sip:192.168.210.20:5060;transport=udp;lr>
Expires: 3600
Via: SIP/2.0/UDP 192.168.210.15:5062;branch=z9hG4bKefb882972a2daa85bea52af52a064310
Content-Length: 0

Section 5 Page 38
IMS
UE
8. 401 Unauthorised
9. 401 Unauthorised Nonce
Nonce
10. 401 Unauthorised
Nonce
Nonce
11. Generation
of response
Nonce
12. REGISTER
13. DNS: DNS-Q
Response,Cnonce
14. REGISTER
15. Cx: User registration status query

Response,
Response, Cnonce
Cnonce
Technology
IMS/TISPAN Overview
Next step
The S-CSCF keeps the Nonce.The UE computes data and sends back the Response into a new REGISTER
message.
Status-Line: SIP/2.0 401 Unauthorized

Message Header
From: <sip:erwan.duval@home1.net>;tag=tkigud
To: <sip: erwan.duval@home1.net>;tag=b72e12N2643f682dd-2847
Call-ID: h7ql8b@192.168.210.15
CSeq: 1000 REGISTER
WWW-Authenticate: Digest
realm="home1.net",domain="",nonce="3d8ce9fd067e70fefd3df91377a3577e",opaque="",stale=FALSE,algorithm=MD5,qop="auth“
Content-Length: 0
Request-Line: REGISTER sip:home1.net SIP/2.0

Message Header
Call-ID: h7ql8b@192.168.210.15
From: <sip: erwan.duval @home1.net>;tag=9z9g5m
To: <sip:erwan.duval@home1.net>
CSeq: 1001 REGISTER
Authorization: Digest username="
erwan.duval@home1.net",realm="home1.net",uri="sip:home1.net",nonce="3d8ce9fd067e70fefd3df91377a3577e",qop=auth,nc=0000
0001,cnonce="d067e70fefde1e0",response="97577ddd5774ae5aa51eec318b21f566",algo
P-Preferred-Identity: <sip: erwan.duval@home1.net>
Security-Client: ipsec-3gpp; alg=hmac-sha-1-96; spi-c=23456789;spi-s=12345678;port-c=2468; port-s=5060
Contact: <sip:192.168.210.15:5062>
Content-Length: 0

Section 5 Page 39
IMS
UE
16. REGISTER
Response,
Response, Cnonce
Cnonce
17. Authentication
18. Cx: S-CSCF registration

notification
19. Service Control
20. 200 OK
21. 200 OK
22. 200 OK
Technology
IMS/TISPAN Overview
Final step
The S-CSCF receives the REGISTER message back and authenticates the subscriber. Then, it updates the
status of the subscriber in the HSS and downloads the iFC.

Section 5 Page 40
5.5 Charging in IMS/TISPAN
Technology
IMS/TISPAN Overview

Section 5 Page 41
5.5 Charging in the IMS/TISPAN
2 ways to perform charging
OFF Line
A charging process where charging information
does not affect, in real-time, the service
rendered.
ON Line
A charging process where charging information can

affect, in real-time, the service rendered and
therefore directly interacts with the session/service
control.
Technology
IMS/TISPAN Overview
2 ways to perform charging
Billing is the function whereby charging data are transformed into bills requiring payment.
Pre-paid and post-paid are different payment methods for the subscribers.
These payment methods could be based on both on-line and off-line charging mechanisms.
To get full credit control, pre-paid should be built on on-line charging.
If the operator would like to have post-paid subscribers on credit control, these subscribers
should be charged with the off-line charging mechanism.
How do NEs know whether they must apply off-line or on-line charging?
At registration info downloaded from HSS contains off-line charging or on-line charging addresses or both.
Charging Function addresses are only distributed by the S-CSCF to IMS/TISPAN network elements within
its own home network (not to the other networks or UEs) via SIP.

Section 5 Page 42
OFF line charging
Billing domain
Bp Bi
Charging Collection Function

Charging Gateway Function
Rf
Ga
AS
MRFC
MRFC
MGCF
SGSN GGSN
MGCF
P-CSCF S-CSCF
I-CSCF
Technology
IMS/TISPAN Overview
OFF line Charging
It is based on the existing GSM & GPRS off-line charging systems with a Charging Gateway Function (CGF)
which collects Call Data Records (CDRs) and sends them to the billing domain.
Each IMS/TISPAN element contains an off-line Charging Triggering Function (CTF) capable of generating
off-line charging events based on observation of network usage.
The Charging Collection Function (CCF) uses and may aggregate charging events from every CTF to
generate CDRs.
Ga, Bp and Bi interfaces are based on the TCP/IP protocol, where the Rf interface is in diameter.

Section 5 Page 43
ON line charging (1/2)
Correlation
Billing domain
Session Bearer
ISC Charging Function
Charging
Function Function
Account Bi
S-CSCF
AS Rating
Function
MRFC
MGCF Ro
Event
Charging
MRFC Ro Function
SCCF
CPCF
CAP
SGSN
Online Charging System
Technology
IMS/TISPAN Overview
ON line Charging
Access Charging is performed using the CAP interface from the SGSN to the Bearer Charging Function.
Session Charging is performed using the ISC interface between the IMS/TISPAN Session Charging Function
and the S-CSCF.
Event-based charging between an AS or MRFC and the Event Charging Function (ECF) is performed using
the Ro reference point.
Session Charging Function

The Session Charging Function (SCF) is responsible for Session Charging including the session control such
as session termination.
Bearer Charging Function

The Bearer Charging Function performs the Bearer Charging.
Correlation Function
For a session comprising several media components (such as audio and video), charging data is generated
for each media component and needs to be correlated between network elements. The correlation of
charging information for an IMS/TISPAN session is based on the use of IMS/TISPAN Charging Identifiers
(see later in this chapter).

Section 5 Page 44
Rating Function
The rating function calculates for the ECF and SCF, the price of the resource usage (based on volume,
connection / session time, service events / content, etc.).
Event Charging Function

The Event Charging Function (ECF) performs event-based charging (content charging). It makes use of
the rating function. The ECF communicates with the Account. The ECF may correlate several event-
based charging requests. It communicates with the Correlation Function to correlate Event Charging
with Bearer Charging and Session Charging.
The Subscriber Content Charging Function (SCCF) is located in the operator network where the
account of the subscriber is located.
The SCCF has the following responsibilities:
- to handle charging requests from the CPCF
- to find the account of the subscriber. The account may be either a prepaid account or a
postpaid account.
- to initiate a procedure to get a charging confirmation from the subscriber, if such a
confirmation is needed.
- to debit or to credit a certain amount from/to the account of the subscriber.
The Content Provider Charging Function (CPCF) is located in the operator network and/or in
another network such as for example a Service Provider network that supports the content
server.
The CPCF receives content charging requests from the content server, processes them and relays
them to the Subscriber Content Charging Function (SCCF).
The CPCF has the following responsibilities:
- to handle charging requests from the content server.
- to communicate with the SCCF that manages the subscriber’s account. This may imply a
request from the SCCF to charge or to credit the account of the subscriber.

Section 5 Page 45
5.6 Charging identifiers
Technology
IMS/TISPAN Overview

Section 5 Page 46
IMS Charging IDentifier (ICID)
ICIDs are used to correlate events generated during a registration or a

session.
Billing domain
event
event event event
event event
event AS
event
event event
event
MRFC event MRFC
MGCF
MGCF
P-CSCF S-CSCF
I-CSCF
Technology
IMS/TISPAN Overview
IMS Charging IDentifier (ICID)
Several NEs generate charging events for the same event/session. Correlation has then to occur in the
Billing Domain, not in the network.
The correlation information is built up at session establishment. The correlation information includes,
but it is not limited to, a globally unique charging identifier that makes easy the billing effort: The ICID
The ICID is collected in a Charging Correlation Vector which is transferable via SIP (P-Charging Vector
header). The information inside the charging vector may be filled in and retrieved by multiple network
entities (incl. SIP proxies).

Section 5 Page 47
GPRS Charging ID (GCID)
GCIDs are used to correlate the charging process between the PS domain
and the IMS.
Billing domain
CDR event
event event event
CDR event event
CDR
CDR
event
event
AS
event event
event
MRFC event MRFC
MGCF
SGSN GGSN
MGCF
P-CSCF S-CSCF
I-CSCF
Technology
IMS/TISPAN Overview
GPRS Charging ID (GCID)
The charging correlation principles outlined above shall be applicable to other types of access networks.
For instance, it shall be possible to use, instead of "GPRS charging ID " an equivalent term of the
associated access network (Access Network Charging Identifier).
The GCID:
identifies the media flows in PDP context used by a user.
is used to correlate the access network charging data with the IMS charging data.
is created as soon as resources are allocated, updated each time media are
added/removed/modified.
Shared among the IMS network elements (CSCFs & operator AS) for one side of the session
(originating or terminting side). Originating and terminating sides generate their own Access
Network Charging ID.
The GPRS charging information is passed up by the GGSN to the P-CSCF via the PDF. The P-CSCF includes
it in the SIP signaling.

Section 5 Page 48
Inter Operator Identifiers (IOI)
Orig-ioi=home1.net
Service Home Term-ioi=home2.net
Platform
Network 1 S-CSCF
S-CSCF I-CSCF
Home
Network 2
Orig-ioi=home1.net
P-CSCF
P-CSCF
SGSN
GGSN
SGSN
GGSN
Technology
IMS/TISPAN Overview
Inter Operator Identifiers (IOI)
The following requirements relate to the Inter Operator Identification concept:

The Inter Operator Identification concept shall allow operators to uniquely identify each other
for the SIP based requests; for example between A’s HPLMN and B’s HPLMN.
Inter Operator identities shall be included within SIP signalling:

• When an SIP request is passed out of a network, the Inter Operator identity of that
network shall be included in the SIP signaling.
• When an SIP response is returned, the Inter Operator identity of that responding
network shall be included in the SIP signaling.
Each network is responsible for including its own unique Inter Operator Identity into the SIP
signaling. The Inter Operator Identity shall be unique for each operator (for example, the Inter
Operator Identity of home operator A is different from home operator B).
Inter Operator Identities received in the session signalling shall be incorporated into the CDRs
produced by the IMS network elements. The operator identification information may be used
for inter operator accounting purposes.
The allocation of the IOI values for the operators is outside the scope of 3GPP standardization.

Section 5 Page 49
5.7 Charging and roaming
Technology
IMS/TISPAN Overview

Section 5 Page 50
5.7 Charging and roaming
Charging when roaming
BT.com Vodafone.com
AS AS
HSS 3 HSS
DNS I-CSCF I-CSCF
9
(THIG) (THIG)
7
4 6
S-CSCF 5 8 S-CSCF
2 Home 10 Home
DNS DNS
P-CSCF P-CSCF
INVITE Bearer 11
SGSN 1 BRAS DSLAM

GGSN
Technology
IMS/TISPAN Overview
Charging when roaming
When subscribers are roaming abroad, the charging process is realized by the home network.
So, the home network is able to perform either on-line or off-line and is independent from the visited
network, where the subscriber is.
You can notice onto this diagram, that an optimal routing process is implicit with IMS, because the UE
controls itself the RTP connection to the destination address.

Section 5 Page 51
Section 5 Page 52
5.8 Exercise
Technology
IMS/TISPAN Overview

Section 5 Page 53
Place the IMS/TISPAN identities
Exercise
On the following diagram, place the following identities

in the appropriate database where they are stored.
Time allowed:
5 minutes
Technology
IMS/TISPAN Overview
1 GCID
GCID
2 RAND
3 KK
RAND
4 IMPU
IMPU
5 S-CSCF
S-CSCF Name
Name
6 iFC
iFC
7 CAMEL
CAMEL MARKS
MARKS 8 IMPI
IMPI
9 XRES
XRES
10 IOI
IOI
11 ICID
ICID

Section 5 Page 54
ISIM
HSS
HSS
Billing Domain

Section 5 Page 55

for this module
Technology
IMS/TISPAN Overview

Section 5 Page 56
End of Module
Technology
IMS/TISPAN Overview

Section 5 Page 57
6
Section 6
Alcatel–Lucent IMS solution: IMS 6.1


Section 6 Page 1
Blank Page
Alcatel–Lucent IMS solution: IMS 6.0 6 2
Technology
IMS/TISPAN Overview
Document History
07 2007-02-19 DUVAL, Erwan

Section 6 Page 2
Objectives
To be able to describe the Alcatel-Lucent IMS solution and

establish the correlation with IMS / TISPAN specification.
Technology
IMS/TISPAN Overview

Section 6 Page 3
Objectives [cont.]
Technology
IMS/TISPAN Overview

Section 6 Page 4
Table of Contents
Page
6.1 Introduction 7
Network Overview 8
6.2 Access Layer 9
Location 10
A7720 Access Border Node (ABN) 11
A5020 Access Gateway Control Function (AGCF) 13
A5750 Subscriber Services Controller (SSC) 14
ACME Packet net net SD 17
A5430 Session Resource Broker (SRB) 19
6.3 Session Control Layer 21
Location 22
Lucent Session Manager (LSM) 23
Unified Subscriber Data Server (USDS) 25
A8688 MRF * 27
Vital QIP 29
Solutions for MGCF 30
A5020 Wireless Call Server (WCS) 31
A5020 MGC-10 32
A5020 MGC-12 33
Lucent Network Controller 34
6.4 Application layer 35
Network Overview 36
A5350 IAS 37
A5350 IAS Architecture 39
TechnologyA5350 Smart Communication Routing (SCR) 40
IMS/TISPANA8640
OverviewCorporate Mobility Manager (CMM) 41
Feature Server 5000 44
A8680 Video-voice MailboX (VMX) 46
A8680 Video-voice MailboX (VMX) [continued] 47
Handsets [Mobile] 48
Handsets [Fixed ] 49
Windows Mobile Clients 50
Intellivic VCC Client 51
PCTEL DMS Client 52
6.5 Support Systems 53
Location 54
A8965 C3S 55
A8610 Instant Convergent Charging (ICC) 57
A1390 Generic User Profile (GUP) 59
Lucent Communication Manager 61
A1300 XMC 62
Others OMC 64
6.6 Recap 65
TISPAN/3GPPP Functional mapping 66

Section 6 Page 5
Page
Technology
IMS/TISPAN Overview

Section 6 Page 6
6.1 Introduction
Technology
IMS/TISPAN Overview

Section 6 Page 7
6.1 History
Network Overview
A5350 SCR A5350 IAS A8640CMM OMC-H OMC-CN
Mobile
Access Presence V-PBX OMC for OMC for
VCC IM, PtX IP Centrex USDS LSM
FS5000 A8680 VMX LCM A1300 XMC

WIMAX
IMS Web Network
PES VMX
Portal Mgmt
3G A1390 GUP SS8 / A1357

A7720 ABN GUP LIG
p-CSCF
i-CSCF
2,5G
USDS Vital QIP A8965 C3S A8610 ICC
PCRF
HSS
USPF ENUM CCF/CDF OCS
Wifi
LSM
i/s-CSCF
BGCF
E-CSCF xxx
A5020 AGCF SCIM MGCF
AGCF
I-CSCF
A8688 MRF
A5750 SSC MGW
NACF MRF
Fixed CLF
PDBF Core Network
ACME ACME
Access UAAF
P-CSCF IBCF
SPDF SPDF
A5430 SRB
RACF
C-BGF IP Backbone I-BGF
Technology
IMS/TISPAN Overview

Section 6 Page 8
6.2 Access Layer
Technology
IMS/TISPAN Overview

Section 6 Page 9
6.2 Access Layer
Location
Mobile

WIMAX
IMS Web Network
PES VMX
Portal Mgmt
3G A1390 GUP SS8 / A1357

A7720 ABN GUP LIG
p-CSCF
i-CSCF
2,5G
PCRF
HSS
Wifi
LSM
i/s-CSCF
BGCF
E-CSCF xxx
AGCF
I-CSCF
Audiocodes
A5750 SSC MGW
NACF MRF
Fixed CLF
PDBF Core Network
ACME ACME
Access UAAF
P-CSCF IBCF
SPDF SPDF
A5430 SRB
RACF
Technology
IMS/TISPAN Overview

Section 6 Page 10
6.2 Access Layer
A7720 Access Border Node (ABN)
IMS functions included:

7720 ABN
P-CSCF,I-CSCF, PCRF iQ4000 based
Capacity :
Scales up to 500K IPSec tunnels and 500 tunnels / sec.
Up to 1M stateful Firewall sessions per system.
960 CAPS (or equivalent) per system.
350K Sub / system for a typical Fixed IMS traffic model.
1K Diameter req/s/Ghz
No performance penalty when new
services are switched on (LI, security, etc.)
7720 ABN
Excellent overload management
iQ8000 based
Hardware platform:
Reefpoint iQ4000 or iQ8000
Technology
IMS/TISPAN Overview

Section 6 Page 11
6.2 Access Layer
A7720 Access Border Node (ABN)
The 7720 ABN can be plugged on top of all the access defined in IMS standard
(GPRS, CDMA, CDMA 2000,Wifi, Wimax and xDSL)
Page 3
Border
Node
7720 ABN
Alcatel-Lucent 7720 ABN

ABC
P-CSCF/
I-CSCF ABG
PCRF
Common Middleware
Open IT Platform
Technology
IMS/TISPAN Overview
The 7720 ABN is composed of 2 main modules:
•An Access Border Control element (also called 7720 ABC) : link of the IMS control network towards the
terminals and the externals networks.. This element is considered as the master control part of the 7720
ABN
•An Access Border Gateway: link of the IMS media network towards the terminals and the externals
networks. Security Gateway, which protects both the IMS subscriber’s link into the IMS network as well as
the IMS core elements, including the Call and Session Control Function (CSCF) Servers, Application
Servers and the Home Subscriber Server

Section 6 Page 12
6.2 Access Layer
ACME Packet net net SD
The Acme Packet SD provides the following key characteristics:
Edge router providing security, IP services, and QoS & bearer control
Capable of handling up to 32,000 concurrent VoIP calls
VoIP NAT/NAPT
NAT traversal
Topology hiding
Lawful interception replication and routing
Session Director (front view)
Session Director (rear view)
Technology
IMS/TISPAN Overview

Section 6 Page 13
6.2 Access Layer
ACME Packet net net SD

P-CSCF, SPDF, C-BGF,
IP Peering
I-BCF, I-BGF.
IP Access
Technology
IMS/TISPAN Overview
Acme Packet is the company name. Product is Net-Net Session Director

Section 6 Page 14
6.2 Access Layer
A5020 Access Gateway Control Function (AGCF)

AGCF
Platform:
Sun Fire V240/V440
7302 iSAM- V
Sun Fire V440

AGW HSS
AGCF
AGW
1540 IP-LiteSpan
Technology
IMS/TISPAN Overview

Section 6 Page 15
6.2 Access Layer
A5750 Subscriber Services Controller (SSC)
5750
5750 SSC
SSC
Service control subsystems and applications P-CSCF
e2 Gq’
NASS Rq RACS
CLF e4 SPDF
A-RACF
a2 a4
NACF UAAF PDBF
a1 a3
CPECF Ia
e3 AMF Re
e1
ARF RCEF C-BGF Core transport
Home Network Access Network
Access Node IP-Edge Border Node network
Technology
IMS/TISPAN Overview

Section 6 Page 16
6.2 Access Layer
Overview
Extension packages
ISSO Billing Interface Web Portal •Metering and triggering
•Service Admission Control
Accounting
Module External
External Subscriber Service
LDAP
LDAP
SQL
Database profiles profiles

Access Server
and and Access
subscriptions policies
5750 SSC
External 802.1x EAP Subscriber Services External
Radius
RADIUS ctrl DHCP
DHCP
RADIUS DHCP
Server Controller Service Server
Access AAA RADIUS Controller Access
Service Controller
RG, WiFi RADIUS SH/SSH TL1/CLI XML SNMP ‘Plug In’ DHCP
WiMAX RADIUS TPSDA
DHCP
Client Access Client Access IPoE/DHCP
Multi-vendor
EMS and Network Device Interfacing
Legacy BRAS (Network Policy Control)
Technology
IMS/TISPAN Overview

Section 6 Page 17
6.2 Access Layer

UAAF, PDBF, CLF, NACF included at the NASS function
Platform:
SunFire V440
5750 SSC
Technology
IMS/TISPAN Overview

Section 6 Page 18
6.2 Access Layer
A5430 Session Resource Broker (SRB)
5430
5430 SRB
SRB
Service control subsystems and applications P-CSCF
e2 Gq’
NASS Rq RACS
CLF e4 SPDF
A-RACF
a2 a4
NACF UAAF PDBF
a1 a3
CPECF Ia
e3 AMF Re
e1
ARF RCEF C-BGF Core transport
Home Network Access Network
Access Node IP-Edge Border Node network
Technology
IMS/TISPAN Overview

Section 6 Page 19
6.2 Access Layer
A5430 Session Resource Broker (SRB)

A-RACF
Platform:
SunFire V440 cluster (4CPU)
diskarray Sun3310 (5 disks) 5430 SRB
Sun Solaris 9
Oracle 9
Technology
IMS/TISPAN Overview

Section 6 Page 20
6.3 Session Control Layer
Technology
IMS/TISPAN Overview

Section 6 Page 21
Location
Mobile

WIMAX
IMS Web Network
PES VMX
Portal Mgmt
3G A1390 GUP SS8 / A1357

A7720 ABN GUP LIG
p-CSCF
i-CSCF
2,5G USDS Vital QIP A8965 C3S A8610 ICC
PCRF HSS
Wifi LSM
i/s-CSCF
BGCF
E-CSCF xxx
AGCF
I-CSCF A8688 MRF
A5750 SSC MGW
NACF MRF
Fixed CLF
PDBF Core Network
ACME ACME
Access UAAF
P-CSCF IBCF
SPDF SPDF
A5430 SRB
RACF
Technology
IMS/TISPAN Overview

Section 6 Page 22
Lucent Session Manager (LSM)

P-CSCF,I-CSCF,S-CSCF, Service broker
(enhanced SCIM), PDF and BGCF)
Protocols:
Diameter, SIP
Physical interfaces:
10/100/1000 Base-TX, four pair of connections per
cabinet
Capacity:
10+ M session/hr. each session executing a complete
suit of IMS components (S/I/P-CSCF, SCIM, BGCF
and charging function)
Hardware platform:
Compact PCI PSB (PICMG 2.16 compliant)
Technology
IMS/TISPAN Overview

Section 6 Page 23
Lucent Session Manager (LSM) [cont.]
Common board hardware
1 or more IMS element per board

S-CSCF
E-CSCF
Allows for large scale deployment
Alarm
Ethernet
Ethernet
BGCF
Alarm
Geographic redundancy
Alarm
Ethernet
Ethernet
Alarm
Ethernet Switch Card – 2 per shelf
Technology
IMS/TISPAN Overview

Section 6 Page 24
Unified Subscriber Data Server (USDS)

HSS
“Distributed” ---high availability and scalability.

The system availability is targeted at 99.999%.
The system may eventually
support from as small as 100K, to as large as 50M.
Platform: Sun Netra t1400
Redundancy:
Mated pair for the back end DB side, and N+K strategy for the front-end side
Technology
IMS/TISPAN Overview

Section 6 Page 25
Unified Subscriber Data Server (USDS) [cont.]
HLR Data Function
HDF HDF HDF
OMC-H USDS
LAN/WAN
HCF HCF HCF HCF
HLR Control Function
CSCFs
Technology
IMS/TISPAN Overview
The HLR Data Functions (HDF) and HLR Control Functions (HCF) of the USDS are separated/distributed on
separate servers (could be
geographically separated), enhancing reliability and allowing access to data from multiple network
elements.
The subscriber data on the HDFs is distributed, using the concept of Index Server (IS) on the HCFs to find
the appropriate HDF for a
specific subscriber record.
Even though the HCFs are distributed, the USDS appears as a single Point Code (PC) to the rest of the
network. Geographical and logical
diversity of control and data results in more reliability, open architecture and scalability.

Section 6 Page 26
A8688 MRF *
Alcatel 8688 MRF 6.0 features
Out-band DTMF detection suitable for the most networks

RFC 2833
SIP INFO (dtmf-relay, telephone-event)
VoiceXML for audio interactions
Codec G.711 A-law µ-law, AMR-NB
Available configurations from 100 channels
Video (H.263 profile 0 level 10 QCIF, level 30 QCIF/CIF)
Announcement
Interaction with a streaming server within a scope of a specific project (video
content and video on demand services, streaming from the webcams, live TV)
Scalability and redundancy thanks to MRFC / MRFP separation
Technology
IMS/TISPAN Overview
*AudioCodes (IPM5000) used as B plan
A8688 MRF :
•Voice and video 100% software processing allowing important lowering of the costs
•The Alcatel 8688 MRF can send, receive and record speech and video, enabling a service to manage the
interaction with the caller, play back fixed and variable announcements (audio or video) and collect the
user Dual Tone Multi-Frequency (DTMF) input transmitted as a data (out-band DTMF).

Section 6 Page 27
A8688 MRF * [cont.]
HP DL 380
Technology
IMS/TISPAN Overview
As specified in 3GPP, the MRF is split in 2 functions: the MRFC and the MRFP, which, in Alcatel-Lucent
solution, can operate on the same server (one-box configuration) or can operate on separate servers
giving the scalable solution and providing the redundancy. Alcatel-Lucentl is using the SIP protocol
between MRFC and MRFP. For a signaling point of view, the MRFC acts as a SIP proxy. It provides
following capabilities:
· Load-balancing of the SIP INVITE requests towards the different MRFP; a simple round-robin load-
balancing is performed taking into account the status of the MRFP and following the capabilities required
(see next points).
· Management of the status “in service”/”out of service” of each MRFP and the dynamic addition of
new MRFP in the configuration. Periodically, each MRFP registers itself to the MRFC: if no registration is
made after a configurable period (default: 10s), the MRFC is considering this MRFP out of service.
· Management of the MRFP capabilities: within its registration, each MRFP is able to give its
capabilities for media processing. With such information, the MRFC is able to route the first INVITE
request to a MRFP according the capabilities requested. New features such as management of number of
available resources available on each server, codecs available per server, … will be introduced in the
MRF 6.x program.

Section 6 Page 28
Vital QIP

DNS ENUM + DNS
Technology
IMS/TISPAN Overview

Section 6 Page 29
Solutions for MGCF
Multiple solutions for MGCF function

A5020 WCS
A5020 MGC (MGC-10 or MGC-12)
LNC
Technology
IMS/TISPAN Overview

Section 6 Page 30
A5020 Wireless Call Server (WCS)

MGCF
Associated MGW:
7570 MGW
Type of network:
Mobile Network
Hardware platform:
Sun Netra
Wireless
Soft Switch
SS7 PLMN
TDM/ATM
SIP
SIP
IMS RTP/IP
Megaco
Wireless
Media
Gateway
Technology
IMS/TISPAN Overview

Section 6 Page 31
A5020 MGC-10

MGCF
Protocols:
SIP
Associated MGW:
7510 , 7515
Type of network:
Fixed Network (E10 based)
Hardware platform:
ATCA TOMIX
Technology
IMS/TISPAN Overview

Section 6 Page 32
A5020 MGC-12

MGCF
Protocols:
Diameter, SIP
Associated MGW:
7510 , 7515
Type of network:
Fixed Network (S12 based)
Hardware platform:
cTCA (Compact TCA)
Technology
IMS/TISPAN Overview

Section 6 Page 33
Lucent Network Controller

MGCF Compact
Compact Switch
Switch
MG
MG
Control Signaling Media
Signaling Media
Control Gateway
Gateway Gateway
Gateway
Function
Function
Network
Network
Associated MGW: Controller
Controller Network
Network
MG
MG Gateway
Gateway
Signaling
Signaling
Control
Plexus MGW Control Gateway
Function
Function
Gateway Media
Media
Gateway
Gateway
Type of network:
Fixed Network (ANSI)
Hardware platform:
Lucent Gateway Platform (LGP)
Technology
IMS/TISPAN Overview

Section 6 Page 34
6.4 Application layer
Technology
IMS/TISPAN Overview

Section 6 Page 35
Network Overview
Mobile

WIMAX
IMS Web Network
PES VMX
Portal Mgmt
3G A1390 GUP SS8 / A1357

A7720 ABN GUP LIG
p-CSCF
i-CSCF
2,5G
PCRF
HSS
Wifi
LSM
i/s-CSCF
BGCF
E-CSCF xxx
AGCF
I-CSCF
A8688 MRF
A5750 SSC MGW
NACF MRF
Fixed CLF
PDBF Core Network
ACME ACME
Access UAAF
P-CSCF IBCF
SPDF SPDF
A5430 SRB
RACF
Technology
IMS/TISPAN Overview

Section 6 Page 36
A5350 IAS
A set of fixed and mobile Services

Presence enhanced phone book
XML document management (XDMS)
Push to Talk / Show / Share
Instant Messaging
PC/Mobile Messaging
PC/Mobile VoIP & V2oIP comm.
Conferencing
A global environment for fast creation and deployment of services
SCE
Your Application
xxx
SIP XCAP other
Technology
IMS/TISPAN Overview

Section 6 Page 37
A5350 IAS [cont.]
Alcatel 5350 IAS 3.x
Language Runtime : SUN JSDK JAVA 5

Java Applications
Middleware: Proxy Platform
Application Middleware Stacks
OS: Linux Red Hat Advanced Server 4.0
Carrier Grade Linux
Hardware: Base Line HP DL 380 G5
Xeon 5130 Dual Core Hardware: HP G5
HP DL 380
Technology
IMS/TISPAN Overview

Section 6 Page 38
A5350 IAS Architecture
“IO Handler”:
A Linux C coded process handling: IP socket management, flow regulation
and load-balancing
Agent (JVM) Agent (JVM) Agent (JVM) Agent (JVM)
Generic Container Generic Container Generic Container Generic Container
Servlet Servlet Servlet Servlet
SIP SIP SIP SIP

Servlet Servlet Servlet Servlet
Container Container Container Container
“Agent”: Load
Balancer
Java
container(s) SIP IO Handler
Following protocols are handled:
HTTP, SIP, SMPP, SMTP, RADIUS, DIAMETER…
For each protocol, a specific
java container is provided
Technology
IMS/TISPAN Overview
Stacks
• 100 000 simultaneous TCP conn.
• 7000 req/s/GHz (Pentium Xeon)
Agents : depends on the protocol

• HTTP: 1000 req/s/GHz
• SMTP: 100 req/s/GHz
• WAP: 500 req/s/GHz
• RADIUS: 1000 req/s/GHz
• DIAMETER: 1500 req/s/Ghz
• SMS: 1000 req/s/GHz
• MMS: 300 MM/s (6 boards)
• SIP proxy in HA mode1: 50 IETF CAPS/GHz= 350 req/s/GHz, <15 ms latency
• SIP ua/server in HA mode: 100 IETF CAPS/GHz= 700 req/s/GHz

Section 6 Page 39
A5350 Smart Communication Routing (SCR)
Camel
GSMC

VCC (Voice Continuity Call)
Platform: MGCF VCC/DMS
A5350 IAS
ISC
Features : Gm
Converged voice is the integration of cellular, S-CSCF
WiFi or Bluetooth and IP broadband technologies
Converged voice provides access to wireless

voice and data services using the cellular
network outside and unlicensed Bluetooth
or WiFi spectrum technology through
an IP broadband connection when inside
the home or small office/home office
Technology
IMS/TISPAN Overview
Stacks
• 100 000 simultaneous TCP conn.
• 7000 req/s/GHz (Pentium Xeon)
Agents : depends on the protocol

• HTTP: 1000 req/s/GHz
• SMTP: 100 req/s/GHz
• WAP: 500 req/s/GHz
• RADIUS: 1000 req/s/GHz
• DIAMETER: 1500 req/s/Ghz
• SMS: 1000 req/s/GHz
• MMS: 300 MM/s (6 boards)
• SIP proxy in HA mode1: 50 IETF CAPS/GHz= 350 req/s/GHz, <15 ms latency
• SIP ua/server in HA mode: 100 IETF CAPS/GHz= 700 req/s/GHz

Section 6 Page 40
A8640 Corporate Mobility Manager (CMM)
CMM stands for Corporate Mobility Manager
CMM 4.2.1.2 services offers

PSTN/PLMN/NGN Voice/Multimedia VPN services,
advanced V-PBX services,
IMR dual phone (fixed/mobile) services and transversal management
provisioning facilities.
CMM 4.2.1.2 services run on the OSP 2.3 application server.
The CMM architecture consists in a set of mandatory services and optional ones
(see next slides) that will work together to process many types of call :
Voice (Protocols : INAP, CAP V2, SIP)
Data (Protocols : Radius, CAPV3, SIP)
Web (Protocols : SOAP/HTTP)
Technology
IMS/TISPAN Overview

Section 6 Page 41
CMM 4.1.2 Core Management PC Management PC &

Company users & Trusted Untrusted
Applications Applications
Internet/
Intranet
SCP SMP
SIP HTTPS
IMS OSP 2.3 SOAP/HTTP
WEB
Firewall
Server
Secure proxy
INAP CAMEL RADIUS
SSP
LDAP
MSC
SMS-C
MSC Proxy Internet Directory
PSTN Radius / Server
HPLMN Intranet
RADIUS
VPLMN
VPN
GPRS
Company users
Company users in
HPLMN Company
users abroad
GPRS CMM
users
Technology
IMS/TISPAN Overview

Section 6 Page 42

IP-centrex, V-PBX
Platform:
8690 Open Services Platform (OSP )
HW & SW
Unix Compaq & SUN / Oracle 8.1 / NT, Windows 2000 / GUI JAVA Applet
Technology
IMS/TISPAN Overview

Section 6 Page 43
Feature Server 5000
FS5000 is an IMS based Telephony Application Server

IMS PSTN/ISDN Emulation Subsystem (PES)
Protocols:
SIP
Platform:
Lucent Control Platform (LCP )
Capacity:
Lucent Control Platform 1000
300k BHCA per LCP1000 chassis
1.5M BHCA (750k subs) per cabinet with LCP2
Technology
IMS/TISPAN Overview

Section 6 Page 44
Feature Server 5000 [cont.]
Services Offered
Call Barring
Call Blocking – Incoming/ Int’l
Call Forwarding: Busy, Local, No Answer, Unregistered User, Variable
(Always)
Call Hold – Consultation
Call Transfer Variations: With Consultation, Blind, From 3-Way, w/ Ring-
back Timer
Call Waiting
Calling Line ID Features (CLIP/ CLIR/ CLIRO/ CLIR Edit Allowed/ CLIR Per
Call)
…
Web Portal Services via Lucent Communication Manager:

Click to Dial
Click to Transfer
Click to Drop
Click to Conference
Technology
IMS/TISPAN Overview

Section 6 Page 45
A8680 Video-voice MailboX (VMX)
Alcatel 8680 Architecture Design
Alcatel 8680 Voice/Video Messaging Service
Technology
IMS/TISPAN Overview

Section 6 Page 46
A8680 Video-voice MailboX (VMX) [continued]
Main Services Features

Voice/Video Call Answering
Voice/Video Message Recording
Message Notification (Video outcall, SMS, MMS, e-mail)
Audio Reader (voice access to video messages)
Plain Audio Pack (convergent Voice and Video messaging service)
Intentional deposit (explicit access to mailbox)
Missed called
Mailbox customization (notification control,personal greeting…)
Interfaces
Voice/Circuit switched: H324M (SS7/ISUP transport)
Packet switched: H.323, SIP
H.450.7 for H.323 notification HP DL 380
Video: H263 profile 0, level 10/30, MEPG4 SP (option)
Audio: AMR, G.723.1, G.711
SMS notification (SMPP v3.4)
MMS (3GPP MM7 R5)
SMTP (RFC 2821), IMAP4 (RFC 2045-2049)
Technology
IMS/TISPAN Overview

Section 6 Page 47
Handsets [Mobile]
5350 Windows Mobile Client - so called AIMC

Platform: Based on Windows Mobile OS (v5.0)
Availability: available for field trials on QTEK9000 and QTEK 9600
5350 Symbian Mobile Client

Platform: Based on s60 Ed2 and Ed3 platform (Symbian OS)
Ownership: Developed by an Alcatel’s partner (OEM) – Teleca
Availability: Nokia 6630, 6680, N70 and N90 are already supported
5350 J2ME Mobile Client

Platform: Java enabled devices e.g. s60 Ed3 platform (Symbian OS),
Windows Mobile Platforms
Availability: Nokia E61, N80 and N91 are already supported
Technology
IMS/TISPAN Overview

Section 6 Page 48
Handsets [Fixed ]
Thomson ST2030
Eyebeam
Cisco 7960 Polycom 601
Technology
IMS/TISPAN Overview

Section 6 Page 49
Windows Mobile Clients
Features Devices
Network Address Book
•Presence Enabled (OMA)
Windows Mobile
•XDMS based (OMA) 5.0
•Group and Contact Management
•Media Capability Management
Community services
•Instant Messaging (IETF and OMA)
•One-to-many, chat etc…
•Push-To-Talk (OMA)
•Ad-hoc groups Qtek
•Push-To-Show (OMA) 9600
Legacy Service Management

•CS Call handling
•CS Call enrichment
•Video Sharing
•Picture Sharing
•SMS handling Qtek 3600
Peer-To-Peer services
•VoIP
•Full duplex video session
Qtek 9000
Technology
IMS/TISPAN Overview

Section 6 Page 50
Intellivic VCC Client
Dual mode (GSM/WiFi) multimedia

communication for Smartphones and PDAs
Multimedia communication
(audio,video and IM)
Network handover (GSM/WiFi)
Presence
Intuitive user interface
Reliability
Easy to install and configure: auto- provisioning
Technology
IMS/TISPAN Overview

Section 6 Page 51
PCTEL DMS Client
Dual mode (CDMA/GSM/WiFi) IMS ready customizable

and extensible for Feature phones, Smartphones and
PDAs
SMS communication
E911 Service
Voicemail integration
Network handover (CDMA/GSM<->WiFi)
Intuitive user interface
Voice Call Continuity
Easy to install and configure: auto- provisioning
Technology
IMS/TISPAN Overview
Dual GSM/CDMA/WiFi VoIP client

Seamless voice handover:
WiFi <-> WiFi & WiFi<-> GSM/CDMA
Call Management:
Maintain Simultaneous Calls (2)
Call Swapping
Call Hold/Call Resume,Call Mute,Call Transfer,3-way Calling
Codec Support
VoWi-Fi, G.711a/u, Enhanced G.711a/u, G.729a,b , iLBC, iPCM
Dynamic Codec Negotiation(IETF RFC 3264)
Regulatory
NAR E911
SMS (SIP or CDMA)
SMS over Wi- Fi/EVDO (SIP-based),SMS to Contact from Contact List ,Message Waiting Indicator Visual
& Audible
Other:
Call History
Phone address book integration
• Realtime sync
• Click2call
Voice Mail (SIP or GSM/CDMA)
Single Click to Call Voice Mail
Message Waiting Indicator

Section 6 Page 52
6.5 Support Systems
Technology
IMS/TISPAN Overview

Section 6 Page 53
6.5 Support Systems
Location
Mobile

WIMAX
IMS Web Network
PES VMX
Portal Mgmt
3G A1390 GUP SS8 / A1357

A7720 ABN GUP LIG
p-CSCF
i-CSCF
2,5G
PCRF
HSS
Wifi
LSM
i/s-CSCF
BGCF
E-CSCF xxx
AGCF
I-CSCF
A8688 MRF
A5750 SSC MGW
NACF MRF
Fixed CLF
PDBF Core Network
ACME ACME
Access UAAF
P-CSCF IBCF
SPDF SPDF
A5430 SRB
RACF
Technology
IMS/TISPAN Overview

Section 6 Page 54
6.5 Support Systems
A8965 C3S

Offline Charging Billing Domain
SIP AS
Bi
Rf
Rf
MGCF
Rf
BGCF
A8965 C3S
Rf P- CSCF
I- CSCF
Rf
S - CSCF
Ga
SGSN
Ga
GGSN
Rf: Diameter
Wf: Diameter
Ga: GTP’
Bi: FTP etc
OFFLINE CHARGING
Rf, Ga, Bi
interfaces
Technology
IMS/TISPAN Overview

Section 6 Page 55
6.5 Support Systems
A8965 C3S
Server Software Client Software

PStudio C3S C3S Application client part
Studio Entry Studio output Pclient C3S
WinSCP
C3S Application server part PServer C3S JRE
PSystemclient C3S
SFTP server Oracle Discoverer
JSDK PSystemserver C3S Windows XP Pwindows

JBOSS
OWB Server
& Client OWF Server
Oracle Enterprise edition Server
Linux Red Hat Advanced Server Plinux

Server Hardware
HP DL 380
Technology
IMS/TISPAN Overview

Section 6 Page 56
6.5 Support Systems
A8610 Instant Convergent Charging (ICC)

Online Charging
To be charged Capture history
Legacy
Service Management, Provisioning,

PSTN Storage
Voice Engine
Product
Mobile Catalogue Promotion Top up
IMS-Gw
Engine
Network Layer
Community
IMS/NGN/IP Engine Voucher
CCBS
Notification Manager
NGN session
Rating Manager
IMS Reseller
Event, data Engine
Scheduler Manager
content Balance Manager
Internet
Manager Consult, update
Offline Event
Generators Instant Rating
WLAN Convergent Rating Engine User Self Care
Mediation
IP
Alcatel Instant Convergent Charging Suite
Technology
IMS/TISPAN Overview

Section 6 Page 57
6.5 Support Systems
A8610 Instant Convergent Charging (ICC)
The 8690 Open Service

Platform is Alcatel’s Service
platform deployed within more Alcatel OSP
than 200 mobile & fixed
Management framework
operators Any
PPT
> A ‘must’ for real time application
> Welcome several applications
> Scalable, flexible, reliable
Payment Capabilities
> Online configuration
> Open to third party platforms Rating Account
Voucher …
Engine Server
> Multiple environments: SS7, IP,
IT Services execution env. (SEP)
> Multi protocols (INAP, SIP, DPE BUS
Radius, HTTP…) Protocol legs (FEP's)
> NGN, IMS
INAP Diameter CAMEL SIP/ISC HTTP
> Integration success, with high
level of performance
Micro
SSP MGC S-CSCF MSC xGSN AAA
Payment
Technology
IMS/TISPAN Overview

Section 6 Page 58
6.5 Support Systems
A1390 Generic User Profile (GUP)
OSS/BSS Subscriber provisioning & selfcare Network management Billing
A1390 Network management

Provisioning &
GUP OMC
of other components Network
Subscriber
Provisioning Center SOAP-XML/HTTP HTTPS/SFTP/SNMP- Management
v3
external SIP Services CDF Application
i.e. Presence, VMS/UMS, IMR, MuM, … i.e. Offline charging, Online rating, … layer
SIP
HSS
Control
Lawful layer
PSTN
N7 SIP Diameter Intercept
Wireless/Wireline
X1,X2 External
Softswitc
CSCF X3
MGCF h
IP
SIP SIP
H248/MGCP SIP SIP Other operators
IMT IP network
IMT MGW Network
P-CSCF
Border Node
- ISDN PRI SIP MRFC
- 3G 324M - ISDN MGW
- 3G MGW
Fixed and mobile
access networks
SIP SIP SIP SIP Transport/Media

RGW/IAD layer
IP Softphones IP Hardphones
Analog ISDN 3G 3G (PCs, PDAs, …) Black Fixed
Fixed Fixed Mobile Mobile Phones IP
audio audio/video audio/video audio/video audio/video
equipment equipment equipment equipment equipment
Technology
IMS/TISPAN Overview

Section 6 Page 59
6.5 Support Systems
A1390 Generic User Profile (GUP)

GUP Server
Platform:
Sun Fire V240 or V440
Applications
High Watch Super Communi …

Availability dog vision cation
Platform independent layer(Tru64, Solaris, Linux, Win32) A1390 GUP
Cluster Cluster Cluster file OCI

lock IP@ system Std Pos
OCI
C/C++ ix
SUN Cluster
SUN Cluster libs Oracle Rac
Oracle
Solaris
Solaris
SUNClustered
SUN Clustered HW
HW
Technology
IMS/TISPAN Overview

Section 6 Page 60
6.5 Support Systems
Lucent Communication Manager
Lucent Communication Manager (CM) is the End User Web Portal for the
FS 5000. XML interface supports:
Call management
Personal Settings
Integration with IM
Self sign-up
Personal Address Book
Outlook integration
Option selection within feature packages
Branding
Technology
IMS/TISPAN Overview

Section 6 Page 61
6.5 Support Systems
A1300 XMC
Alcatel
OSS Partners & Operations and Business Support Systems WEB portal
Integration Services
OSS Interfaces Assurance: QoS / Billing data

(SNMP, Corba, WebServices, Inventory Fault Mgmt Provisioning
Performance / Traffic collection
SOA oriented, legacy, …)
Network Management Service Management
Alcatel Network Configuration & Supervision

Domain Application
OMC-R/W AWS OMC-CN CMC XMC Platforms
Managers
IAS
OSP
Other
End-User
Mobile Web Portal
Radio 2G/3G FMC GUP
Network
BBW Access Subscr
DBs
CDRs
BB Access Mobile Core Fixed
Packet / NGN/PSTN
Circuit / NGN
Technology
IMS/TISPAN Overview

Section 6 Page 62
6.5 Support Systems
A1300 XMC
Networks elements managed by A1300 XMC :
7720 ABN
1430 IM-HSS
5020 AGCF
5350 AS
8688 MRF
5020 WCS
7570 MG
ACME
Single server Configuration – HP based server
8640 CMM, PA-Risc or Proliant
5430 SRB
5750 SSC
7510 TGW
5020 MGC
8610 ICC
Technology
IMS/TISPAN Overview

Section 6 Page 63
6.5 Support Systems
Others OMC
Network elements managed by OMC-CN :

LSM,FS5000, VitalQIP, LNC
Network elements managed by OMC-H :

USDS
Multimedia
Session Controller Operation & Maintenance
(Call/Session
Control) LSM OMC-CN
Home Operation & Maintenance

Subscriber
Server OMC-H
(Database) USDS
Technology
IMS/TISPAN Overview

Section 6 Page 64
6.6 Recap
Technology
IMS/TISPAN Overview

Section 6 Page 65
6.6 Recap
TISPAN/3GPPP Functional mapping
IMS Functional Element Alcatel-Lucent IMS Solution Component

Serving Call Session Control Function (S-CSCF) Lucent Session Manager (LSM)
Interrogating Call Session Control Function (I-CSCF) LSM,7720 ABN
Proxy Call Session Control Function (P-CSCF) LSM,ACME Packet,7720 ABN
Access Gateway Control Function (AGCF) 5020 AGCF
5750 SSC
Network Attachment Subsystem (NASS)
Resource and Admission Control Subsystem (RACS) 5430 SRB
SCIM (Service Capability Interaction Manager ) Lucent Control Platform – Service Broker (SCIM)
Border Gateway Control Function (BGCF) Lucent Session Manager (LSM)
Policy Decision Function (PDF) Lucent Session Manager (LSM)
Media Gateway Control Function (MGCF) 5020 MGC 10, Plexus or 5020 WCS
Media Gateway (MGW) 75xx Media Gateway/Plexus Network Gateway
Media Resource Function (MRF) 8688 Media Resource Function, AudioCodes
I-BCF, C-BCF, C-BGF 7720 Access Border Node, ACME Packet
Home Subscriber Server (HSS) Unified Subscriber Data Server (USDS)
Authentication,Authorization, Accounting (AAA) Unified Subscriber Data Server (USDS)
DNS/ENUM VitalQIP
PES Application Server Lucent Feature Server 5000 (on LCP)
Multimedia Application Server 5350 IAS
User Web Portal 5350 IAS , LCM
Billing 8965 C3S, 8610 ICC
Lawful Interception (LI) SS8 , A1357
Voice Continuity Call (VCC) 5350 SCR
Element Management OMC-CN, OMC-H, 1300 XMC
Technology
IMS/TISPAN Overview

Section 6 Page 66

for this module
Technology
IMS/TISPAN Overview

Section 6 Page 67
End of Module
Technology
IMS/TISPAN Overview

Section 6 Page 68
7
Section 7
Appendix and Glossaries


Section 7 Page 1
Blank Page
Appendix and Glossaries 7 2
Technology
IMS/TISPAN Overview
Document History
07 2007-12-19 DUVAL, Erwan

Section 7 Page 2
7.1 Appendix
Technology
IMS/TISPAN Overview

Section 7 Page 3
7.1 Appendix
IMS/TISPAN reference architecture 1/2
Application Servers Rf/Ro
Ut
Rf/Ro
Ut Other types of service logic Charging
NASS Functions
PSTN/ISDN Emulation logic
(Network Sh Rf/Ro
Attachment ISC/Ma Dh
UPSF Iw
Subsystem) Cx SLF IWF
Dx Ib
P3
e2 IMS-based PES
e2 AGCF Mw Mx
IBCF Ic
Mw I/S-CSCF Mi Mx
BGCF Mk
P1
Mw Mr
Other IP Networks
Mj Gq'
Gm Mx
Mg
P-CSCF SGF
MRFC MGCF Ie
PSTN/ISDN
Gq' Gq'
Ut
Mp Mn
RACS (Resource and Admission Control Subsystem)
VGW
Z MRFP T-MGF
IP Transport (Access and Core) I-BGF

MG
Z
Technology
IMS/TISPAN Overview

Section 7 Page 4
7.1 Appendix
IMS/TISPAN reference architecture 2/2
Application Server Rf/Ro

(SIP, OSA, IN) Charging
Function
Ut Ut Sh ISC Dh
C ha Rf/Ro
rging
PDBF User UPSF SLF Info
rma
Data ti on
IWF Iw
Dx
CNGCF Cx
Ib
Terminals
Gq‘
Mx Ic
Legacy
Other IP Networks
e3 I/S-CSCF IBCF
e2
AGCF Mi Mx
Mw Gq‘
(Home Network)
User Equipment
Mw BGCF Mx
Gq‘ SPDF
P-CSCF SGF
Mg Mj
PSTN / ISDN
e2 e2 Mr
CLF Gq‘ Gq
e4 MRFC MGCF
A-RACF SPDF
a3 a4 Rq
IP-CAN
3GPP
e1 e5 UAAF NACF
Ia
a1 a2
Re Ia Mp Mn
ARF AMF
e1 Ra
RCEF C-BGF MRPF T-MGF I-BGF

Access
L2TP
Node
Transport Layer
Technology
IMS/TISPAN Overview

Section 7 Page 5
7.1 Appendix
RoHC Robust Header Compression
Header Bigger than Payload
Media Media Media
RTP RTP Media RTP
UDP UDP RTP Media UDP
IP IP UDP RTP Media IP

20 bytes 8 bytes 12 bytes 10 bytes
RoHC RoHC
Physical 40 bytes
Physical
Technology
IMS/TISPAN Overview
Payload Data Sampling Payload bandwidth bandwidth

format rate size with RoHC
AMR 8kb/s 10 ms 10 bytes 40 kb/s 9,6 kb/s
The RoHC allows to replace the legacy header by a reference code of 2 bytes.
The full header is sent once, and then only a reference to the header is sent.

Section 7 Page 6
7.1 Appendix
QoS Authorization and verification
AS
IP media flow HSS S-CSCF to other network

serving user B
SIP signalling
GPRS PDP signalling
P-CSCF
Diameter Gq
UMTS network
PDF
COPS Go
GPRS PDP context
UE (incl auth token) IP
User A
network
GGSN
Step 1: Session layer signaling (SIP)
Step 2:Bearer layer signaling (PDP context activation)
Step 3: Session layer signaling
Step 4: Bearer Layer -> Data can start flowing (RTP streams)
Technology
IMS/TISPAN Overview
Step 1: Session layer signaling (e.g. SIP)

End-users negotiate via SIP the media characteristics (codecs, media
components...) they want to use for that session
A->B: service control possible via hooks in S-CSCF to application layer
B->A: P-CSCF contacts PDF to get QoS authorization token to insert in SIP to A
Step 2:Bearer layer signaling (PDP context activation)

Each end-user sets up bearer(s) to other end-user with the QoS he wants
GGSN checks auth token auth QoS with the PDF, and performs admission control
GGSN confirms to A that GPRS PDP context can be successfully setup
SIP UPDATE messages confirm successful bearer setup (before ringing)
Gates are opened - charging is ready - so that data can start flowing

Section 7 Page 7
7.1 Appendix
QoS Authorization and verification
AS
HSS S-CSCF to S-CSCF in other network

serving user B
P-CSCF
Diameter Gq’
IP media flow xDSL network
UE SPDF +A-RACF
User A
SIP signalling
???
no explicit user initiated IP
QoS signalling in fixed network
DSLAM BRAS

Step 2:Resource allocation
Technology
IMS/TISPAN Overview

End-users negotiate via SIP the media characteristics (codecs, media
components...) they want to use for that session
A->B: service control possible via hooks in S-CSCF to application layer
Step 2: Resource allocation
B->A: P-CSCF contacts SPDF (Service Policy Decision Function) to get QoS
authorization
SPDF contacts A-RACF (Access-Resource Admission Control Function ) to to really
reserve the authorized resources
A-RACF performs admission control & sends QoS policies to BRAS (& DSLAM)
A-RACF reports successful resource reservation to SPDF and to P-CSCF
SIP UPDATE messages confirm successful bearer setup (before ringing)
Gates are opened - charging is ready - so that data can start flowing

Section 7 Page 8
7.2 IMS References
Technology
IMS/TISPAN Overview

Section 7 Page 9
3GPP Specs
They can be downloaded from http://www.3gpp.org/specs/numbering.htm. The list below is a small selection
related to the IMS.
TS 21.905 Vocabulary for 3GPP Specifications

TS 22.066 Support of Mobile Number Portability (MNP); Stage 1
TS 22.101 Service Aspects; Service Principles
TS 22.141 Presence Service; Stage 1
TS 22.228 Service requirements for the IP multimedia core network subsystem; Stage 1
TS 22.250 IMS Group Management; Stage 1
TS 22.340 IMS Messaging; Stage 1
TS 22.800 IMS Subscription and access scenarios
TS 23.002 Network Architecture
TS 23.003 Numbering, Addressing and Identification
TS 23.008 Organisation of Subscriber Data
TS 23.107 Quality of Service (QoS) principles
TS 23.125 Overall high level functionality and architecture impacts of flow based charging; Stage 2
TS 23.141 Presence Service; Architecture and functional description; Stage 2
TS 23.207 End-to-end QoS concept and architecture
TS 23.218 IMS session handling; IM call model; Stage 2
TS 23.221 Architectural Requirements
TS 23.228 IMS stage 2
TS 23.229 WLAN interworking
TS 23.271 Location Services (LCS); Functional description; Stage 2
TS 23.278 Customized Applications for Mobile network Enhanced Logic (CAMEL) - IMS interworking; Stage 2
TS 23.864 Commonality and interoperability between IMS core networks
TS 23.867 IMS emergency sessions
TS 23.917 Dynamic policy control enhancements for end-to-end QoS, Feasibility study
TS 23.979 3GPP enablers for Push-to-Talk over Cellular (PoC) services; Stage 2
TR 23.981 Interworking aspects and migration scenarios for IPv4-based IMS implementations (early IMS)
TS 24.141 Presence Service using the IMS Core Network subsystem; Stage 3
TS 24.147 Conferencing using the IMS Core Network subsystem
TS 24.228 Signalling flows for the IMS call control based on SIP and SDP; Stage 3
TS 24.229 IMS call control protocol based on SIP and SDP; Stage 3
TS 24.247 Messaging using the IMS Core Network subsystem; Stage 3
TS 26.235 Packet switched conversational multimedia applications; Default codecs
TS 26.236 Packet switched conversational multimedia applications; Transport protocols
TS 29.162 Interworking between the IMS and IP networks
TS 29.163 Interworking between the IMS and Circuit Switched (CS) networks

Section 7 Page 10
TS 29.198 Open Service Architecture (OSA)
TS 29.207 Policy control over Go interface
TS 29.208 End-to-end QoS signalling flows
TS 29.209 Policy control over Gq interface
TS 29.228 IMS Cx and Dx interfaces : signalling flows and message contents
TS 29.229 IMS Cx and Dx interfaces based on the Diameter protocol; Protocol details
TS 29.278 CAMEL Application Part (CAP) specification for IMS
TS 29.328 IMS Sh interface : signalling flows and message content
TS 29.329 IMS Sh interface based on the Diameter protocol; Protocol details
TS 29.962 Signalling interworking between the 3GPP SIP profile and non-3GPP SIP usage
TS 31.103 Characteristics of the IMS Identity Module (ISIM) application
TS 32.240 Telecommunications management; Charging management; Charging architecture and Principles
TS 32.260 Telecommunications management; Charging management; IMS charging
TS 32.421 Telecommunications management; Subscriber and equipment trace: Trace concepts and
equirements
TS 33.102 3G security; Security architecture
TS 33.108 3G security; Handover interface for Lawful Interception (LI)
TS 33.141 Presence service; security
TS 33.203 3G security; Access security for IP-based services
TS 33.210 3G security; Network Domain Security (NDS); IP network layer security
IETF Specs
RFC 1889 Real-time Transport Protocol (RTP)
RFC 2327 Session Description Protocol (SDP)
RFC 2748 Common Open Policy Server protocol (COPS)
RFC 2782 a DNS RR for specifying the location of services (SRV)
RFC 2806 URLs for telephone calls (TEL)
RFC 2915 the naming authority pointer DNS resource record (NAPTR)
RFC 2916 E.164 number and DNS
RFC 3261 Session Initiation Protocol (SIP)
RFC 3262 reliability of provisional responses (PRACK)
RFC 3263 locating SIP servers
RFC 3264 an offer/answer model with the Session Description Protocol
RFC 3310 HTTP Digest Authentication using Authentication and Key Agreement (AKA)
RFC 3311 update method
RFC 3312 integration of resource management and SIP
RFC 3319 DHCPv6 options for SIP servers
RFC 3320 signalling compression (SIGCOMP)
RFC 3323 a privacy mechanism for SIP

Section 7 Page 11
RFC 3324 short term requirements for network asserted identity
RFC 3325 private extensions to SIP for asserted identity withing trusted networks
RFC 3326 the reason header field
RFC 3327 extension header field for registering non-adjacent contacts (path header)
RFC 3329 security mechanism agreement
RFC 3455 private header extensions for SIP
RFC 3485 SIP and SDP static dictionary for signaling compression
RFC 3588 DIAMETER base protocol
RFC 3589 DIAMETER command codes for 3GPP release 5 (informational)
RFC 3608 extension header field for service route discovery during registration
RFC 3680 SIP event package for registrations
RFC 3824 using E164 numbers with SIP

Section 7 Page 12
7.3 Glossaries
Technology
IMS/TISPAN Overview

Section 7 Page 13
3GPP Third Generation Partnership Project
AAA Authentication, Authorization, and Accounting
ACID Access Charging IDentifier
ADSL Asymetric Digital Subscriber Line
AGCF Access Gateway Control Function
AGW Access GateWay
AK Authentication Key
AKA Authentication Key Agreement
ALG Application Level Gateway
AMF Access Management Function
AMF Authentication Management Field
AMR Adaptive Multi-rate
AN Access Node
API Application Program Interface
A-RACF Access-Resource and Admission Control Function (RACS)
AS Application Server
ATM Asynchronous Transfer Mode
aTCA Advanced Telecommunications Computing Architecture
AuC Authentication Center
AUTN AUthentication TokeN
AV Authentication Vector
AVP Attribute Value Pair (DIAMETER)
BCSM Basic Call State Model
BG Border Gateway
BGCF Breakout Gateway Control Function
BGF Border Gateway Function
BRAS Broadband Remote Access Server
BS Bearer Service
BSC Base Station Controller
BTS Base Transceiver Station
CAMEL Customised Application Mobile Enhanced Logic
CAP Camel Application Part
CCF Charging Collection Function
CDR Charging Data Record
CK Cipher Key
CLF Connectivity Session Location and Repository Function (NASS)
CN Core Network
COPS Common Open Policy Service
CS Circuit Switched
CSCF Call Session Control Function
CSE CAMEL Service Environment
CTF Charging Triggering Function
DHCP Dynamic Host Configuration Protocol
DNS Domain Name System

Section 7 Page 14
DSLAM Digital Subscriber Line Access Multiplexor
EDGE Enhanced Data Rates for Global Evolution
ENUM tElephone NUmber Mapping
ETSI European Telecommunications Standards Institute
FTTH Fiber To The Home
FTTU Fiber To The User
GCID GPRS Charging ID
GERAN GSM/EDGE Radio Access Network
GGSN Gateway GPRS Support Node
GLMS Group and List Management Server
GMLC Gateway Mobile Location Centre
GMSC Gateway Mobile Switching Center
GPRS General Packet Radio Service
GUP Generic User Profile
GRX GPRS Roaming eXchange
HLR Home Location Register
HNT Hosted Nat Traversal
HSDPA High Speed Downlink Packet Access
HSUPA High Speed Uplink Packet Access
HSS Home Subscriber Server
IAD Integrated Access Device
I-BCF Interconnect Border Control Function
I-CSCF Interrogating-CSCF
ICID IMS Charging Identifier
IETF Internet Engineering Task Force
IFC Initial Filter Criteria
iFS Internal Feature Server (Alcatel)
IGMP Internet Group Management Protocol
IK Integrity Key
IM Instant Messaging
IM-HSS IP Multimedia HSS
IM-SSF IP Multimedia Service Switching Function
IMPI IMS Private Identity
IMPU IMS Public Identity
IMS IP Multimedia Core Network Subsystem
IMSI International Mobile Subscriber Identifier
IOI Inter Operator Identifier
IP Internet Protocol
IP-CAN IP-Connectivity Access Network
IPv4 Internet Protocol version 4
IPv6 Internet Protocol version 6
IPX IP eXchange
ISDN Integrated Services Digital Network
ISIM IMS SIM
ISP Internet Service Provider

Section 7 Page 15
ISUP ISDN User Part
LEX Local Exchange
LPF Low Pass Filter
MAP Mobile Application Part
MMD MultiMedia Domain
MGC Media Gateway Controller
MGCF Media Gateway Control Function
MGF Media Gateway Function
MGW Media GateWay
MRF Multimedia Resource Function
MRFC Multimedia Resource Function Controller
MS Mobile Station
MSC Mobile Switching Center
NA(P)T-PT Network Address (Port-Multiplexing) Translation-Protocol Translation
NGN Next Generation Network
NACF Network Access Configuration Function (NASS)
NAI Network Access Identifier
NASS Network Attachment SubSystem
OCS Online Charging System
OMA Open Mobile Alliance
OSA Open Services Architecture
P-CSCF Proxy-CSCF
PCU Packet Control Unit
PDBF Profile Database Function (NASS)
PDF Policy Decision Function
PDN Packet Data Network
PDP Packet Data Protocol e.g., IP
PEF Policy Enforcement Function
PES PSTN Emulation Subsystem
PLMN Public Land Mobile Network
PM Presence Manager
POC Push to Talk Over Cellular
PSI Public Service Identity
PSTN Public Switched Telephone Network
QoS Quality of Service
RAB Radio Access Bearer
RACS Resource Admission Control Subsystem
RADIUS Remote Authentication Dial In User Service
RAND RANDom Challenge
RAS Remote Access Server
RCEF Resource Control Enforcement Function
RFC Request for Comments
RGW Residential Gateway
RNC Radio Network Controller
SBLP Service Based Local Policy
SCP Service Control Point

Section 7 Page 16
SCS Service Capability Server
S-CSCF Serving-CSCF
SDP Session Description Protocol
SDSL Symetric Digital Subscriber Line
SFC Subsequent Filter Criteria
SGSN Serving GPRS Support Node
SGW Signalling GateWay
SHDSL Single-pair High-speed Digital Subscriber Line
SIM Subscriber Identity Module
SIP Session Initiation Protocol
SLF Subscription Locator Function
SPDF Service Policy Decision Function (RACS)
SPT Service Point Trigger
SRP Specialised Resource Point
SS7 Signalling System 7
SSF Service Switching Function
STB SetupBox
TEX Transit Exchange
TGW Trunking Gateway
THIG Topology Hiding Inter-network Gateway
TISPAN Telecommunications and Internet converged Services
and Protocols for Advanced Networking
TrGW Translation Gateway
UAAF User Access Authorization Function (NASS)
UE User Equipment
UICC Universal Integrated Circuit Card
UMA Unlicenced Mobile Access
UMAN Unlicenced Mobile Access Network
UMTS Universal Mobile Telecommunications System
UNC UMA Network Controller
UPSF User Profile Server Function
URI Universal Resource Identifier
URL Universal Resource Locator
USIM UMTS SIM
UTRAN UMTS Terrestrial Radio Access Network
VDSL Very high bit-rate DSL
VLR Visited Location Register
VMSC Visited Mobile Switching Center
VOD Video On Demand
WAC Wireless Access Controller
WAG Wireless Access Gateway
WAP Wireless Application Protocol
WLAN Wireless Local Area Network
XRES eXpected RESponse

Section 7 Page 17
End of Module
Technology
IMS/TISPAN Overview

Section 7 Page 18
TECHNOLOGY
IMS/TISPAN Overview This page is left blank intentionally
Copyright © 2007 by Alcatel-Lucent - All rights reserved
Passing on and copying of this document, use and communication of its
contents not permitted without written authorization from Alcatel

Ims

Încărcat de

Informații document

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Ims

Încărcat de

Drepturi de autor:

Formate disponibile

Technology

Technology - IMS/TISPAN Overview

Copyright © 2007 by Alcatel-Lucent - All rights reserved

All Rights Reserved © 2007, Alcatel-Lucent

All Rights Reserved © 2007, Alcatel-Lucent

Did you meet the following objectives ?

4 To be able to sort the steps needed to

All Rights Reserved © 2007, Alcatel-Lucent

Switch to notes view!

Yes (or No (or

Thank you for your answers to this questionnaire

All Rights Reserved © 2007, Alcatel-Lucent

Technology  IMS/TISPAN Overview

All rights reserved © 2007, Alcatel-Lucent

Edition Date Author Remarks

07 2007-02-19 DUVAL, Erwan

All rights reserved © 2007, Alcatel-Lucent

To be able to find and describe an example where the PoC,

All rights reserved © 2007, Alcatel-Lucent

All rights reserved © 2007, Alcatel-Lucent

All rights reserved © 2007, Alcatel-Lucent

Switch to notes view!

All rights reserved © 2007, Alcatel-Lucent

All rights reserved © 2007, Alcatel-Lucent

The IMS/TISPAN provides a standardized architecture to offer IP-based

The IMS/TISPAN network architecture is composed of two parts:

• Application part specified by the OMA for services.

IMS/TISPAN and Working groups

3rd Generation Partnership Project (3GPP) www.3gpp.org

European Telecommunication Standards Institute (ETSI) http://portal.etsi.org/docbox/TISPAN

Open Mobile Alliance (OMA) www.openmobilealliance.org

All rights reserved © 2007, Alcatel-Lucent

IMS/TISPAN is focused on providing IP-based communication services

Main added values with IMS/TISPAN services (1/2)

IMS/TISPAN provides the same services to different kind of subscribers

All rights reserved © 2007, Alcatel-Lucent

This IMS/TISPAN architecture provides a valuable evolution for IMS/TISPAN end-

Client-server connectivity Peer-to-peer communication

SMS text messaging Instant messaging

Main added values with IMS/TISPAN services (2/2)

IMS/TISPAN architecture is adapted to peer to peer services

All rights reserved © 2007, Alcatel-Lucent

The application part embeds:

Service enablers and communication services

All rights reserved © 2007, Alcatel-Lucent

1.2 – Service enablers

All rights reserved © 2007, Alcatel-Lucent

All rights reserved © 2007, Alcatel-Lucent

GLMS: Group List Management Service

All rights reserved © 2007, Alcatel-Lucent

All rights reserved © 2007, Alcatel-Lucent

PM: Presence Management

All rights reserved © 2007, Alcatel-Lucent

All rights reserved © 2007, Alcatel-Lucent

All rights reserved © 2007, Alcatel-Lucent

1.3 Communication Services

All rights reserved © 2007, Alcatel-Lucent

Internet and IMS/TISPAN services (1/2)

All rights reserved © 2007, Alcatel-Lucent

What are the different services shown during this

All rights reserved © 2007, Alcatel-Lucent

Presence Form of electronic communication which

Instant Messaging A walkie-talkie-like video communication

This service provides access to presence

Technology IMS/TISPAN Overview

Technology IMS/TISPAN Overview