IMS Presentation V0.3 2008-10-28

An overview of the IP Multimedia Subsystem (IMS)
Orange Labs
Based on IMS training courses given by R&D/Core/NAS 28/10/2008
France Telecom Group restricted
Agenda
Introduction IMS Architecture Access to the IMS PSTN/ISDN Simulation/Emulation Business Communications
IPTV over IMS

Voice Call Continuity Combined CS and IMS
Orange Labs - Research & Development IMS Architecture June 2008
Mobile context and drivers for IMS introduction
Circuit-Switched (CS) Domain

Inherently contains the call control components for the Voice service
Voice CC
CS
Introduction of Packet-Switched (PS) Domain

Internet access service only
Voice CC
CS
PS
Drivers for IMS introduction: Leverage the PS Domain

Defined by the 3GPP (part of UMTS R5) "on top" of the PS Domain Seen as an extension of the CS Domain in the 1st step (Replacement of the CS domain is not a priority and is postponed to a later stage)
Voice CC
IMS PS
CS
GPRS-only
Network operators provide a pure transport service (pipes)
with no control of the actual usage of these pipes

Signalling path Bearer path
Content /Application Server
End-to-End Signalling and media

Public Internet
SGSN
4
GGSN
GGSN
SGSN
IMS on the top of GPRS
IMS - IP Multimedia Subsystem:

A SIP-based multimedia architecture, above the Packet Switched (PS) domain.
Signalling path Bearer path Content /Application Server
IMS
Core Managed Network
SGSN
5
GGSN
media
GGSN
SGSN
IMS at a glance
A control architecture above the PS domain to fulfil network operators needs

Basic mechanisms for multimedia session control and access a wide range of multimedia services including identification/authentication, QoS control, security, charging Packet-based network Choice of SIP (Session Initiation Protocol) as session control protocol Completed by Diameter and H.248 for other interfaces
Clear functional separation between entities for :

Session control (CSCF Call Session Control Function) User profile storage (HSS Home Subscriber Server) Service logic execution (AS Application Server)
Separation between transport and control

eg: Entities that handle RTP flow are split into two functional entities (controller processor)
IMS in fixed environments
History
2003: ETSI TISPAN adopts the IMS as the cornerstone of its NGN architecture and start defining extensions required to make it suitable for use in xDSL-based environements 2005: PacketCable adopts the IMS
Benefits to all parties: vendors and operators

Saves specification and development time/effort Enables fixed and mobile convergence Increases the market size for IMS-based network solutions and IMS applications development Enables sharing of investment (CAPEX) and operational costs (OPEX) between fixed and mobile networks.
Different initial priorities and schedules for Fixed and Mobile operators
Mobile operators were primarily looking to the IMS as a extension to the Circuit-Switched (CS) domain Fixed operators were looking to the IMS as an immediate replacement solution for their CS domain (i.e. PSTN)
Silos vs. Convergence
Service #n Service #n Service #1

Service-specific features Authentication Authentication QoS / Resource management Charging
Service #1
Service-specific features
QoS / Resource management

Charging
I M S
Session Control User profile management
Session Control User profile management
Multi-services, access, devices

Business Communications PSTN Emulation Push To Talk Killer Application?. Multimedia Messaging Multimedia Telehony Presence
IP Multimedia Sub-System IMS Backhaul/Backbone

UTRAN/GERAN WIMAX xDSL/FTTx Cable/Docsis WLAN
IPTV
...
IMS: a component of an overall NGN architecture
The coverage of a complete NGN architecture is wider than IMS:

IMS does not cover IP connectivity
IMS covers only SIP applications
To make up a complete NGN architecture (as defined by ITU-T), IMS has to be surrounded by other components:
Access dependant components dealing with specific tasks. Eg: Network attachment Resources and admission control
Components providing alternative service control environments
IMS
Full scope of an NGN architecture
Common IMS, but different NGN architectures in the standardization bodies (3GPP, ETSI/TISPAN, PacketCable)
10
An over simplistic view of the IMS
A unified multidevice, multiaccess, multiservice SIP-based control architecture over an IP transport. IMS
IP Transport
UTRAN I-WLAN WIMAX
xDSL FTTH Cable
PSTN/ISDN GSM CS
11
An more realistic view of the IMS
An extended SIP-based multidevice, multiaccess, multiservice control architecture over a QoS enabled IP transport.
IMS
IP Transport
SIP is used for session control, mobility management and access to services DIAMETER is used for managing and accessing service profiles, traffic policies and charging data. H.248 is used for controlling media gateways
UTRAN I-WLAN WIMAX xDSL FTTH Cable PSTN/ISDN GSM CS
12
The truth on the IMS?
A sophisticated multidevice, multiaccess, multiservice control architecture combining a range of ITU-T, IETF and OMA technologies over a QoS enabled IP transport.
SIP (about 70 extensions on top the base SIP)
IMS
OSA APIs OMA BCAST OMA SIP PUSH
DIAMETER (multiple profiles) H.248 (multiple profiles) RTP/RTCP, IPSec, TLS , DHCP, DNS STUN,ICE,
13
INAP / CAP
SDP, BFCP, MSRP, RTSP, XCAP, FLUTE, IGMP, MLD

Agenda
Introduction
IMS Architecture
Access to the IMS PSTN/ISDN Simulation/Emulation Business Communications IPTV over IMS Voice Call Continuity Combined CS and IMS
14
The IMS architecture: Basic components

CSCF: Call Session Control Function AS: Application Server UE: User Equipment
Provides applications Queries user database
IMS proxy, controls access to the IMS and to transport resources
AS AS AS
SIP
ISC
Triggers services, handles user and sessions states
Mw Gm
I-CSCF
Mw Mw
Mw
15
User Equipment
P-CSCF
S-CSCF
SIP
E-CSCF
P-CSCF (proxy) I-CSCF (interrogating) S-CSCF (serving) E-CSCF (emergency) Media Flows
The IMS architecture: subscriber data bases
DIAMETER
AS
ISC
Dh
Sh
Home Subscriber Server (HSS)

Authentication and Authorization User Profile Repository (push and pull) User Location Repository
HSS SLF
SIP Mw Gm SIP Dx DIAMETER
HSS
User Equipment
16
Cx
CSCF
Media Flows
Subscriber Locator Function (SLF)

Enable a CSCF to find the address of the HSS holding the profile of a particular user. DIAMETER Redirect server
The IMS architecture: Interconnect components

IBCF: Interconnect Border Control Function MGCF: Media Gateway Control Function BGCF: Breakout Gateway Control Function MGW/MGF: Media Gateway function SGF: Signalling Gateway Function PSTN
Interworking
IP-IP Border control
Mw
SIP
CSCF
Mi
Mx Mx Mj BGCF Mk Mn
H.248
IBCF
Other IP Networks
MGCF
ISUP Over SIGTRAN
Mg Decides whether a session will exit the network in IP or TDM mode
SGF MGW Media Flows
To/from PSTN/CS
17
The IMS architecture: Media Resource Function
The Media Resource Function (MRF) provides

Media sourcing (tones, announcements DTMF collection, TTS & ASR, Media mixing (conference), Floor control (conference), Media transcoding, and Media recording,
Sh AS ISC
SIP
HSS
Cx
User Equipment
18
Mw Gm SIP Mp
H.248
CSCF
Mr
MRFC
under the control of an Application Server
The MRF is further decomposed into

MRF-Controller MRF-Processor
Media Flows
MRFP MRF
One MRFC may control one or more MRFPs.
The IMS architecture: the full picture

DIAMETER Dh AS ISC SLF Dx SIP DIAMETER Cx Sh
HSS
HSS
User Equipment
19
Mw Gm
SIP
Other IP Networks
P-CSCF
Mr
CSCF
Mi
Mx
Mx
IBCF
BGCF
Mg
Mj Mk
MRFC
Mp
MGCF
H.248
H.248
Mn To/from PSTN/CS
MRFP
Media Flows
MGW
Typical signaling path for a session

A's profile
AS HSS HSS AS
B's profile
S-CSCF
IBCF
IBCF
I-CSCF
S-CSCF
IBCF
Home IMS
Home IMS
IBCF
IBCF
IBCF Visited IMS
Visited IMS P-CSCF
P-CSCF
A
20
B
Key IMS identities

Primarily used for authentication username@realm Private User Identity) Public User Identity(s) Home Domain Name Hint for routeing initial registration messages to the home domain domainname Primarily used user to user communications SIP URI or tel URI
Public User Identity Service Profile IMS Subscription Private User Identity Public User Identity
Public User Identity
Service Profile
21
Authentication options
Mechanism Authentication Integrity protection IPsec ESP Support
IMS AKA plus IPsec ESP
IMS AKA
Mandatory for all UEs containing a UICC, else optional. Mandatory for CSCFs Optional for UEs Optional for CSCFs Optional for UEs Optional for CSCFs Optional for UEs Optional for CSCFs Optional for GPRSbased UEs Optional for CSCFs Optional for "fixed" UEs Optional for CSCFs
SIP digest plus IP address check SIP digest plus Proxy Authentication SIP digest with TLS Early IMS
SIP digest SIP digest
None None
SIP digest Trust GPRS authentication Trust-by-wire
TLS session None
NBA
None
22
IMS Service Access: Architectural options
AS AS
Sessions are routed to Application Servers because:

The initial request matches certain filter criteria
SCIM
SIP SIPApplication Application Server Server
Sh ISC
OSA OSAservice service capability capabilityserver server (SCS) (SCS)
OSA API
HSS HSS
S-CSCF S-CSCF Cx Si ISC
ISC
OSA OSA application application server server
The destination is a Public Service Identity (PSI)
Mr IM-SSF IM-SSF
MAP
CAP
Camel CamelService Service Environment Environment
MRFC MRFC
PSI: Similar to public uder identities but allocated to services (AS) rather than users.
tel: +33 800 22 22 11 sip: wheaterforcast@orange.com
23
Filter criteria processing (simplified view)

service logic SIP driver
3
Y N AS2
service logic
AS-1
SIP driver
2a
Y
4a
Incoming INVITE 1
iFC#1?
iFC#2? N
2b
4b
SIP routeing
S-CSCF iFCs are stored in the HSS and downloaded to S-CSCF as part of the user profile during registration
24
IMS Service Access: Initial Filter Criteria

Public User Identity Service Profile
Registered /Non Registered
Initial Filter Criteria Priority
Trigger Point
Default handling Service Point Trigger Application Server
Example: Method = "INVITE" AND (Header = "from" Content = francis.faller")
25
IMS Registration
After 5, the S-CSCF knows the terminating P-CSCF for the UE (Path header) After 7, the S-CSCF knows the UE's Service Profile
REGISTER sip: scscf1.ims.orange.fr SIP/2.0 To: Bruno Chatras <sip:bruno.chatras@orange.fr> From: sip:bruno.chatras@orange.fr> Contact: <sip:p-xzzpujo@192.0.2.4> Path: <sip:term@pcscf1.ims.orange.fr;lr>
HSS
7 4 6
REGISTER sip: ims.orange.fr SIP/2.0 To: Bruno Chatras <sip:bruno.chatras@orange.fr> From: Bruno Chatras <sip:bruno.chatras@orange.fr> Contact: <sip:p-xzzpujo@192.0.2.4> Path: <sip:term@pcscf1.ims.orange.fr;lr>
S-CSCF
5 8
200 OK Path: <sip:term@pcscf1.ims.orange.frr;lr> Service-Route: <sip:orig@scscf1.orange.fr;lr> To: Bruno Chatras <sip:bruno.chatras@orange.fr> From: Bruno Chatras <sip:bruno.chatras@orange.fr> Contact: <sip:p-xzzpujo@192.0.2.4> P-Associated-URI: tel:+336738951317;sip:bruno.chatras@orange.fr
I-CSCF
2 9
P-CSCF
REGISTER sip: ims.orange.fr SIP/2.0 To: Bruno Chatras <sip:bruno.chatras@orange.fr> From: Bruno Chatras <sip:bruno.chatras@orange.fr> Contact: <sip:p-xzzpujo@192.0.2.4>
10
1 After 10, the P-CSCF knows the S-CSCF (serviceroute) and the list of public user identities.
UE
26
Originating session
HSS Applications
S-CSCF
INVITE tel:+31161255678 From: Bruno Chatras <sip:bruno.chatras@orange.fr> To: Francis Faller < tel:+31161255678> Route: <sip:orig@scscf1.orange.fr;lr> P-Asserted-Identity: tel:+33673895317
IBCF
orange
IBCF
teliasonera
I-CSCF
5
ENUM lookup
The P-Preferred-Identity matches the implicit registration set, therefore the P-CSCF can assert this identity.
INVITE sip:+31161255678@telia.com;user=phone From: Bruno Chatras <sip:bruno.chatras@orange.fr> To: Francis Faller < tel:+31161255678> Route: <sip:ibcf1.orange.fr;lr> P-Asserted-Identity: tel:+33673895317
P-CSCF
INVITE tel:+31161255678 From: Bruno Chatras <sip:bruno.chatras@orange.fr> To: Francis Faller < tel:+31161255678> P-Preferred-Identity: tel:+33673895317
UE
27
Terminating session
HSS
- LIR Location Information Request - LIA Location Information Answer LIR
Applications
3 LIA
S-CSCF
Operator.com
IBCF
operator.com
IBCF
orange
I-CSCF
S-CSCF
7
INVITE sip:+33673895317@orange.com;user=phone From: Francis <tel:+31161241234> To: Bruno Chatras < tel:+33673895317 > P-Asserted-Id: tel:+31161241234
INVITE tel:+33673895317 From: Francis <tel:+31161241234> To: Bruno Chatras < tel:+33673895317 > P-Asserted-Id: tel:+31161241234 Route: scscf1.ims.orange.fr
P-CSCF
8
INVITE sip:p-xzzpujo@192.0.2.4 From: Francis <tel:+31161241234> To: Bruno Chatras < tel:+33673895317 > P-Asserted-Id: tel:+31161241234 Route: term@pcscf1.ims.orange.fr P-Called-Party-Id: tel:+33673895317
UE
Ext. 5678
28
Agenda
Introduction
IMS Architecture
29
Differences between Fixed and Mobile access
Inherent differences between wireless/ wireline access

Different constraints in terms of bandwidth scarcity, security, transmission delay..
Different assumptions/constraints on user equipment types and behaviour

Supported codecs, authentication schemes, IP version, hosted NAT in customer premises, location awareness, ability to request transport ressources
Differences in the provision of IP connectivity

Different admission control procedures in the access/aggregation network Different network attachment procedures
30
UTRAN/GPRS access to the IMS
Prior to communication with the IMS subsystem, the UE shall:

perform a GPRS attach procedure and ensure that a PDP context used for SIP signalling is available (dedicated or general-purpose) acquire a P-CSCF address(es). using DHCP or PDP context signalling procedures
Media streams are carried using the same or additional PDP contexts (secondary) IMS
SIP
GPRS SGSN GGSN
IP Backbone
31
UTRAN/GPRS access to the IMS

AS HSS
HLR UPSF Cx
SLF
Dx
ISC
Policy and Charging control Dynamic configuration of transport nodes

Gm
S-CSCF P-CSCF
ALG/NAT Mw
IMS
Rx (DIAMETER) Dynamic NAPT/Firewall Iq
PCRF
Go
GPRS SGSN GGSN
IP Backbone
32
DSL Transport resource for accessing the IMS
Transport Functions are provided by a DSL segment and an aggregation segment. The aggregation segment is usually based on ATM or Giga Ethernet Static layer 2 resources (VLAN and/or ATM VC). Usually Layer 2 resources are dedicated to IMS traffic and both signalling and media share the same resources.
IMS
ATM VC IP
SIP
IP Backbone
DSLAM/MSAN BRAS / BNG NAT/FW
DSL Segment
Aggregation Segment
ATM VP or VLAN GE
IP-Connectivity Access Network (IP-CAN)

33
DSL access to the IMS

Network Attachment (IP@allocation, Authentication, Authorisation, Location Repository)
AS HSS
HLR
UPSF Cx
SLF
Dx
ISC
S-CSCF
e2 (DIAMETER)
NASS
CLF
Gm
P-CSCF
ALG/NAT
Mw
IMS
Admission Control Dynamic configuration of transport nodes Gq' (DIAMETER)
RACS
Re (DIAMETER) Ia (H.248)
Dynamic NAPT/Firewall
HGW
DSL Modem GW
ATM or GE aggregation
DSLAM BRAS/BNG
IP Backbone
Router With NAPT/FW

34
Agenda
Introduction
IMS Architecture
PSTN/ISDN Simulation: Provides PSTN/ISDN-like service capabilities using session control over IP interfaces and infrastructure. PSTN/ISDN Emulation: Provides PSTN/ISDN service capabilities and interfaces using adaptation to an IP infrastructure.
35
The IMS Architecture vs CS architectures
ISUP TDM TE
LE
TE
LE
Class 5 (Telephony) logic

AS AS
Mw
SIP S-CSCF S-CSCF
Mw
P-CSCF
P-CSCF SIP
SIP Media Flows (RTP)
36
Simulated PSTN/ISDN Supplementary services
TS 183 004 Communication diversion
Each document includes a specification of
TS 183 005 NGN CONF/3PTY

TS 183 006 NGN MWI TS 183 007 OIP/OIR TS 183 008 NGN TIP/TIR TS 183 010 NGN HOLD TS 183 011 ACR & CB Stage 3 TS 183 015 Call Waiting TS 183 016 NGN MCID TS 183 029 NGN ECT
the UE and AS behavior and rules for populating SIP headers an XML schema for use in service configuration procedures any other XML schema that may be used in SIP bodies (e.g. AoC information in TS 183 047)
TS 183 042 CCBS

TS 183 047 Advice of Charge TS 183 054 CUG
37
PSTN/ISDN Emulation architectures
Two flavours
IMS-based: IMS architecture extended with adaptation functions at the edge (TS 183 012). Softswitch based: A wrapper around vendor-specific implementations based on re-using the call control software of a legacy switching centre (ES 282 002 and TS 183 043).
IMS architectural extension: Access Gateway Control Function (AGCF) acting as:
a combined UE/P-CSCF with regards to the S-CSCF an MGC with regards to media gateway functions.
Type of access supported

Support of Analogue access Support of ISDN access
38
DSL access to the IMS (baseband) Option 1

AS HSS SLF NASS
HLR
UPSF Cx Dx
e2 Gm ISDN p1(H.248 + Q.931/SCTP) Z
P-CSCF
ALG/NAT
Mw
S-CSCF
Mw (SIP +XML)
AGCF
Gq'
RACS
HGW
DSL Modem GW
A-MGF
Ia
IP Backbone
DSLAM BRAS/BNG
Routeur With NAPT/FW

39
DSL access to the IMS (baseband): Option 2

AS HSS SLF NASS
HLR
UPSF Cx Dx
e2 Gm ISDN Gm (SIP+XML) Z
P-CSCF
ALG/NAT
Mw
S-CSCF
Mw (SIP +XML)
Gq'
RACS
HGW
DSL Modem GW
VGW
Ia
IP Backbone
DSLAM BRAS/BNG
Routeur With NAPT/FW

40
PSTN/ISDN Emulation: analog access
Tight Coupling: No feature logic available in the AGCF

e.g. Register Recall
PSTN service logic
AS
events are reported by the AGCF to an Application Server
Core IMS
SIP
Loose Coupling: Limited feature logic resides in the AGCF

e.g. delivery of dialtone upon detection of a Register Recall event The AGCF appears to the AS almost as a "normal" SIP phone or "Box".
Line events/signals
AGCF
H.248
Events/Signals Switching and Transcoding
MGF
41
PSTN/ISDN Emulation: ISDN access
DSS.1 encapsulation
DSS.1 information converted to XML format if cannot be mapped to any SIP header. Palliative to the shortcomings of SIP in terms of signalling information transported.
ISDN service logic
AS
SIP (+XML)
Core IMS
SIP (+XML)
AGCF
H.248
Not to be confused with SIP-I (Q.1912.5) or NSS (Q.1980).
switching and transcoding
D-Channel. B-Channel.
MGF
RTP
42
Agenda
Introduction
IMS Architecture
43
Business Communications Scenarios
Virtual leased line: NGCN sites are interconnected through the NGN using IP VPN tunnels; Business Trunking: The NGN hosts transit capabilities between NGCNs, break-in and break-out capabilities from NGN to NGCN and possibly additional services; Hosted Enterprise Services: The NGN acts as a virtual PBX with regards to a distributed collection of users.
Commonly known in the industry as "IP Centrex".
Next Generation Corporate Networks (NGCN) NGCN Site ~1 or more IP PBX

44
Hosted Enterprise Services
ETSI TS 182 024 specifies the realisation of Hosted Enterprise Services using the IMS.
Endpoints are connected to the IMS at the Gm reference point and appear as normal User Equipment.
Application Servers provide the logic of a Virtual IP PBX.

Private Numbering Plans can be used
Virtual PBX Logic PSTN/ISDN services, Messaging, Presence Conferencing, Abbreviated dialling, Unified Voice mail, Operator assisted calls, Hot Line Calling, Line Hunting, Attended/Blind Communication Transfer, Communication Pickup, Manager / Secretary filtering,
IMS
Basic Endpoint
45
Basic Endpoint
Business Trunking
ETSI TS 182 025 specifies the realisation of a business trunking solution using the IMS. Two variants are identified:
Subscription-based: The PBXs are connected to the NGN at the UNI (i.e. they are seen as a particular type of User Equipment). Peering-based: Corporate Networks are seen as peers of public networks and are therefore connected at the NNI.
Supported features
Transit, Break-in, Break-out Private numbering Bulk re-routeing (e.g. all calls to a particular NGCN site are rerouted to a configured destination during closed hours) Service-level communications Admission-Control (e.g. maximum number of sessions per PBX) Barring of all communications to a PBX
46
Business Trunking
PBX profiles UPSF AS
Business Trunking Logic
Legacy Endpoints
IP-PBX
Core IMS
Access Node
Edge Node
CNG DSL Access
Enterprise Domain / User Equipment
IP Endpoints
Aggregation Segment
Operator's Domain
Core Transport
IP-PBX
Legacy Endpoints
Corporate LAN
Access Node
Edge Node
IP Endpoints
CNG
LAN Access
Aggregation Segment
Enterprise Domain / User Equipment
Opertor's domain
47
Subscription-based Business Trunking
Each site of the NGCN has a service subscription to the IMS and must support SIP registration. Private extensions behind the NGCN do not need their own service subscription, since they are owned and managed by the NGCN.
Each NGCN site is allocated

a pair of private and public user identities for use at registration time. one or more Wildcarded Public User Identity. NOTE: A wildcarded public user identity expresses a set of public user identities grouped together (e.g. tel: +3314529!****!) and can be included in an implicit registration set.
48
IMS PBX Registration

Subscription for PBX Identity, implicit registration set contains a wildcard PUI
- Normal IMS Level Registration Flow (first round-trip not represented) - PBX Identity is provisioned in the HSS - PBX is registered with this PBX Identity - Number range is asscoiated to PBX identity by means an implicitly registered wildcard PUI - PBX indicates support of ua-loose in the REGISTER request or this indication is received from the HSS (part of the user profile)
After 5, the S-CSCF knows the terminating P-CSCF for the PBX (Path header) After 7, the S-CSCF knows the PBX's Service Profile
REGISTER sip: scscf1.ims.orange.fr SIP/2.0 To: pbx1@orangebusiness.com From:pbxsite1@orangebusiness.com Contact: <sip:pbx1@192.0.2.4> Path: <sip:term@pcscf1.ims.orange.fr;lr>
HSS
7 4 6
REGISTER sip: ims.orange.fr SIP/2.0 To: pbx1@orangebusiness.com From:pbxsite1@orangebusiness.com Contact: <sip:pbx1@192.0.2.4> Path: <sip:term@pcscf1.ims.orange.fr;lr>
S-CSCF
5 8
I-CSCF
2 9
P-CSCF
REGISTER sip: ims.orange.fr SIP/2.0 To: pbx1@orangebusiness.com From:pbxsite1@orangebusiness.com Contact: <sip:pbx1@192.0.2.4>
10
1
200 OK Path: <sip:term@pcscf1.ims.orange.frr;lr> Service-Route: <orig@scscf1.orange.fr;lr> To: pbx1@orangebusiness.com From:pbxsite1@orangebusiness.com Contact: <sip:pbx1@192.0.2.4> P-Associated-URI: tel:+33145294444; tel:+3314529!****!;sip:pb1@orangebusiness.com
PBX
After 10, the P-CSCF knows the S-CSCF (serviceroute) and the list of public user identities (including the wildcarded range).
49
Terminating session
Service profile PBX Identity, matches Wildcarded PUI in Implicit Registration set
- LIR Location Information Request - LIA Location Information Answer LIR
HSS
Business Trunking Applications
3 LIA
Optionally trigger on IFC from PBX Identity 4
S-CSCF
Operator.com
IBCF
operator.com
IBCF
orange
I-CSCF
S-CSCF
7
INVITE sip:+33145294148@orange.com;user=phone From: Francis <tel:+31161241234> To: Bruno Chatras < tel:+33145294148 > P-Asserted-Id: tel:+31161241234
INVITE tel:+33145294148 From: Francis <tel:+31161241234> To: Bruno Chatras < tel:+33145294148 > P-Asserted-Id: tel:+31161241234 Route: scscf1.ims.orange.fr
Applies "loose route" procedure as a result of havin received a "ua-loose" route indication from the UA or the HSS at registration time.
INVITE tel:+33145294148 From: Francis <tel:+31161241234> To: Bruno Chatras < tel:+33673895317 > P-Asserted-Id: tel:+31161241234 Route: <sip:term@pcscf1.ims.orange.fr> Route: <sip:pbx1@192.0.2.4> P-Called-Party-Id: tel:+33145294148
P-CSCF
8
PBX
50
Agenda
Introduction
IMS Architecture
51
IPTV
IPTV services: Content on Demand (CoD), Live Media Broadcast (BC) with and without trick mode and time shitfing, Network-based recording (PVR) Two solutions under standardisation
Integration in NGN: Wrapper around legacy systems Integration in IMS
Rationale for using the IMS

Leverage the IMS platform by adding one more service on top of it! Unified framework for authentication, identification, charging and profile management for both communication services and content delivery services Easy integration of communication services and content delivery services, through standard IMS inter-AS communication procedures. Call Forwarding (to Mailbox) when watching TV/VOD, Virtual Living Room, See what I See, Caller ID on TV with or without TV Pause services, Automatic TV/VoD Pause on Incoming Call Acceptance,
52
High Level Architecture for IMS-based IPTV

Other NGN Applications IP-TV Service User Equipment
53
TS 182 027
Discovery Selection Control
User Profile
Management
Core IMS (CSCF)
Media Functions
Content Functions
Resource Allocation
Network Attachment
NASS
RACS
Media Control Media Delivery
Transport Processing
IPTV High Level procedural steps (CoD)

UE AN NASS SSF IMS
SDF (AS)
SCF (AS)
MF
Network Attachment IMS Registration (SIP/IMS)
Service Discovery (SIP/IMS)
Service Selection (HTTP) Session Management (SIP/IMS)
Content Control (RTSP) Content Delivery (RTP)

54
IPTV High Level procedural steps (Broadcast)

UE AN NASS SSF IMS
SDF (AS)
SCF (AS)
MF
Network Attachment IMS Registration (SIP/IMS)
Service Discovery (SIP/IMS)
Service Selection (HTTP) Session Management (SIP/IMS)
IGMP Unicast content

55
Multicast control Multicast content

SIP procedures for IPTV CoD
Work in Progress
UE
RACS
INVITE (R-URI = Content Id)
IMS
MF
MF
SDP Offer for a control channel (RTSP) and one or more content channels
Resource resevation INVITE INVITE
SDP Answer
200 OK(INVITE) Resource Reservation andCommit 200 OK(INVITE)
200 OK(INVITE)
Final decision + firewall opening
RTSP PLAY
Content
56
SIP procedures for IPTV Broadcast
Work in Progress
SDP Offer for multicast traffic

UE RACS
AN
IMS
SCF
INVITE (R-URI = BC Service)
Resource Reservation INVITE
SDP Answer with authorised list of multicast channels
200 OK(INVITE)
Resource Reservation and Commit 200 OK(INVITE)
Final decision (based on user access) + firewall opening for all channels
IGMP Join
Resource Control
Contents
MF
Fine tuning of bandwidth reservations Admission control for resources beyond the AN (in case of zapping to a channel that is not already received)
57
Agenda
Introduction
IMS Architecture
58
Voice Call Continuity
Allows to transfer a CS voice call to a VoIP call

Can be used to provide subscribers services like UNIK
Solution based on IMS

A specific IMS AS is defined for this: VCC AS This VCC AS is connected to both CS domain and IMS domain Typical scenario is to swith a voice call initiated under WLAN coverage to a mobile CS access
59
Voice Call Continuity
Architecture principles:
Application Servers VCC AS
Anchor Point for call establishment, associated to
feature for Network selection
Camel triggering ISUP/BICC Signalling flow
MGCF
MSC
Mobile circuit domain (eg. GSM)
IMS domain Fixed Access Network
SIP Signalling flow
60
Agenda
Introduction
IMS Architecture
61
Combined CS and IMS
Goal:
Handling of real-time services such as VoIP with IMS will be an issue on mobile access
CSI Phase1:
Short Term solution with main impacts on terminal Voice call are kept in the CS domain IMS sessions are used for non real-time services like IM
CSI Phase2:
Long Term solution where CS Bearers are controlled by IMS
62
Combined CS and IMS
CSI Phase1 Architecture:

CSI UE
non real-time services PS e.g. messaging
CSI UE
IMS
PS
CS
Voice component
CS
CS
User sees a call with combined voice and messaging services
CSI Phase2 Architecture:

CSI UE
non real-time services PS e.g. messaging
Pure VoIP UE
IMS
PS
Voice component
CS
CS
63
Conclusion
64
People like criticizing the IMS

From Heavy Reading (based on comments received on their web site)
"IMS is unnecessary for many services, particularly non-SIP services. Even for services that do need SIP, much can be done without using IMS." "IMS has a dated, backward looking view of services and applications. We are now living in a world of Web 2.0, Web services, mash-ups, and SOA, after all." "IMS propagates a telco-oriented view of the network, where services are provided by network intelligence, rather than by edge-device intelligence the intelligent-network/dumbnetwork argument."
"IMS is costly, bloated, overcomplex, overambitious, and will either never work properly or never be fully implemented. "
65
but vendors and operators seem to believe in it!

From Heavy Reading (What's up with IMS)
Terms like IMS-based, IMS-enabled, and IMS-ready abound in vendor product pitches
By September 2007, Ericsson, for example, was citing 39 IMS system contracts for commercial launch and more than 80 trials. Alcatel-Lucent had, as of September, more than 20 full IMS references ("full" meaning the implementation of a CSCF, HSS, AS, and two or more SIP applications) in various stages of deployment, trials, and commercial rollout; and more than 50 customers using IMS application servers and services supplied by the company. Nortel cites 20 IMS contracts and pilots completed or ongoing with carriers worldwide. Nokia Siemens Networks claims more than 30 commercial references for its IMS core in wireless and wireline networks worldwide, and more than 155 references for the IMS core and applications combined.
A Heavy Reading survey in 2006 found that most service providers still consider IMS an essential part of their strategy, "though a significant minority 30 percent of respondents remains unconvinced about it."
66
what about the analysts views?

Gartner 2006
Gartner 2008
In 2010, 77 percent of all investment for call control layers is forecast to be based on IP Multimedia Subsystem (IMS) architecture, while 23 percent will continue to go into enhanced softswitch technologies)
The IMS technology forecast has been pushed back by approximately two years due to a lack of carrier belief in immediate real-world deployability of the architecture in a true fixed-mobile converged, mass-market service environment.
67
Conclusion
IMS opens new opportunities for operators

Converged architecture Development of new enhanced services
BUT
Still at the beginning of IMS, maturity not reach in live networks First step: to be able to recreate the same level of services offer with IMS Second step: create more and more Enriched Services
68
More Information
69
More Information
Where to find Latest Drafts and Published Standards?

http://portal.etsi.org/docbox/tispan/Open/ http://www.tech-invite.com/Ti-tispan-standards.html http://p-xllesandelys.rd.francetelecom.fr or I:\NORMALISATION\Etsi_Tispan (R&D shared directory)
Internal Web Resources (OGSR)

https://ogsr.rd.francetelecom.com/wikidraft/index.php?title=TISPAN https://ogsr.rd.francetelecom.com/wikidraft/index.php?title=Introduction_to_NGN https://ogsr.rd.francetelecom.com/wikidraft/index.php?title=Corporate Networks
External Web Resources

http://www.lightreading.com/document.asp?doc_id=95511&page_number=5
http://www.lightreading.com/document.asp?doc_id=70728 http://portal.etsi.org/docbox/tispan/Open/Information/NGN_Presentations/ TISPAN_Overview_by_Cisco_Tazz.pdf

70
thank you
http://www.tispan.org
Orange, the Orange mark and any other Orange product or service names referred to in this material are trade marks of Orange Personal Communications Services Limited. Orange Personal Communications Services Limited. France Telecom Group restricted. France Telecom Group restricted
Annex
72
User controls on simulated services
Services can be configured by the end user, by uploading XML documents into the network, using the XCAP protocol.
XCAP (http) Ut
DIAMETER
AS
ISC
Dh
Sh
HSS SLF
SIP Mw Gm Dx DIAMETER
<?xml version="1.0" encoding="UTF-8"?> <simservs xmlns= http://uri.etsi.org/ngn/params/xml/simservs/xcap xmlns:cp="urn:ietf:params:xml:ns:common-policy" xmlns:ocp="urn:oma:xml:xdm:common-policy"> <communication-diversion active="true"> <cp:ruleset> <cp:rule id="rule66"> <cp:conditions> condition1 condition2 </cp:conditions> <cp:actions> <forward-to> <target> targetAddress1 </target> <notify-caller>true</notify-caller> </forward-to> </cp:actions> </cp:rule> r </cp:ruleset> </communication-diversion> </simservs>
User Equipment
73
CSCF
SIP
Media Flows

IMS Presentation V0.3 2008-10-28

Î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 Presentation V0.3 2008-10-28

Încărcat de

Drepturi de autor:

Formate disponibile

An overview of the IP Multimedia Subsystem (IMS)

France Telecom Group restricted

IPTV over IMS

Orange Labs - Research & Development IMS Architecture June 2008

France Telecom Group restricted

Mobile context and drivers for IMS introduction

Circuit-Switched (CS) Domain

Introduction of Packet-Switched (PS) Domain

Drivers for IMS introduction: Leverage the PS Domain

Orange Labs - Research & Development IMS Architecture June 2008

France Telecom Group restricted

Network operators provide a pure transport service (pipes)

with no control of the actual usage of these pipes

Content /Application Server

End-to-End Signalling and media

Orange Labs - Research & Development IMS Architecture June 2008

IMS on the top of GPRS

IMS - IP Multimedia Subsystem:

Core Managed Network

Orange Labs - Research & Development IMS Architecture June 2008

A control architecture above the PS domain to fulfil network operators needs

Clear functional separation between entities for :

Separation between transport and control

Orange Labs - Research & Development IMS Architecture June 2008

France Telecom Group restricted

IMS in fixed environments

Benefits to all parties: vendors and operators

Orange Labs - Research & Development IMS Architecture June 2008

France Telecom Group restricted

Silos vs. Convergence

Service #n Service #n Service #1

QoS / Resource management

Session Control User profile management

Session Control User profile management

Orange Labs - Research & Development IMS Architecture June 2008

France Telecom Group restricted

Multi-services, access, devices

IP Multimedia Sub-System IMS Backhaul/Backbone

Orange Labs - Research & Development IMS Architecture June 2008

France Telecom Group restricted

IMS: a component of an overall NGN architecture

The coverage of a complete NGN architecture is wider than IMS:

IMS covers only SIP applications

Components providing alternative service control environments

Orange Labs - Research & Development IMS Architecture June 2008

An over simplistic view of the IMS

UTRAN I-WLAN WIMAX

xDSL FTTH Cable

Orange Labs - Research & Development IMS Architecture June 2008

France Telecom Group restricted

An more realistic view of the IMS

Orange Labs - Research & Development IMS Architecture June 2008

France Telecom Group restricted

The truth on the IMS?

OSA APIs OMA BCAST OMA SIP PUSH

SDP, BFCP, MSRP, RTSP, XCAP, FLUTE, IGMP, MLD

Orange Labs - Research & Development IMS Architecture June 2008

Orange Labs - Research & Development IMS Architecture June 2008

France Telecom Group restricted

The IMS architecture: Basic components

Provides applications Queries user database

IMS proxy, controls access to the IMS and to transport resources

Triggers services, handles user and sessions states

Orange Labs - Research & Development IMS Architecture June 2008