T.

Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

Tutorial 2006

Overview of the

IP Multimedia System (IMS) - Principles, Architecture and Applications

Prof. Dr. Thomas Magedanz Technical University of Berlin / Fraunhofer FOKUS ([email protected])

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

Abstract
This tutorial provides a technical overview of the architecture, components and protocols of the emerging 3GPP IP Multimedia Subsystem (IMS) / 3 GPP2 Multimedia Domain (MMD) which provides the technological basis for the provision of mobile multimedia services within 3G packet networks. This tutorial looks at the driving forces for the IMS architecture definition, introduces the key signalling and control protocols of all IP networks (i.e., SIP and Diameter) forming the basis for IMS component interactions, and explains the key IMS elements and their interactions. Special attention will be given to the IMS application server options, namely CAMEL, OSA/Parlay and SIP AS. The tutorial ends with an overview of the FOKUS IMS play ground (www.fokus.fraunhofer.de/ims).

Page 1

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

The Presenter
Prof. Dr. Thomas Magedanz
Thomas Magedanz (PhD) is professor in the electrical engineering and computer sciences faculty at the Technical University of Berlin, Germany, leading the chair for next generation networks (Architektur der Vermittlungsknoten AV). In addition, he is director of the 3G beyond division at the Fraunhofer Institute FOKUS, which also provides the national 3G beyond test and development centre in Germany. He is senior member of the IEEE, editorial board member of several journals, and the author of more than 200 technical papers/articles. He is the author of two books on IN standards and IN evolution. Based on his 18 years of experience in the teaching of complex IT and telecommunication technologies to different customer segments in an easy to digest way, Dr. Thomas Magedanz is a globally recognised technology coach. He regularly provides strategic and technology briefings for major operators and telecom vendors, as well he acts often as invited tutorial speaker at major telecom conferences and workshops around the world.
3

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

Contact

Prof. Dr.-Ing. habil Thomas Magedanz TUB Chair Next Generation Networks / Director FOKUS 3Gb Division [email protected] +49 171 172 70 70 +49 30 3463 7229 Kaiserin Augusta-Allee 31 14513 Berlin, Germany

Page 2

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

Overview
IMS Motivation IMS Overview IMS Key protocols (IETF SIP and Diameter) IMS Key components IMS Application Server options Sample IMS Multimedia Applications The IMS Playground @ FOKUS Summary References & Acronyms

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

Evolution towards Converged Networks

Fixed Mobile Convergence (FMC)

Voice Data Integration

Page 3

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

VoIP Impact becomes visible in the Fixed World

The traditional voice market is declining. Operators have to explore new market opportunities to fill the revenue gap!

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

War is not on networks, it is on services !

Physical networks become transparent Market entry barriers for services vanish Value Chain splits horizontally Clear & present threats
losing VAS revenues losing subscriber ownership losing control over the Mobile Value Chain

Page 4

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

Action Points for Operators

VoIP is putting significant voice revenues at risk!
Plain old VoIP services (= cheap) will become a commodity

High-end SIP-services (

beyond VoIP services) allow for compensation

Use the opportunity to fill the increasing fixed voice revenue gap by new lifestyle orientated SIP-services Rich VoIP services (including Multimedia Services) Customized VoIP (lessons learned from the mobile world, i.e. ring tones, wall papers, etc.) FMC VoIP services (enhancing VoIP to the mobile domain)

FMC is the common battle field also addressed by Mobile NOs Do we have to distinguish between fixed and mobile operators in the mid long run??
See France Telecom, Telecom Italia, Telefonica, watch out Deutsche Telekom

Selected Value added Service architecture has to be bullet proof from both angles of view (Service Integration) The IP Multimedia System represents this common ground!
9

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

Pre-FMC = 3GPP Virtual Home Environment

Lotto by WAP Football by V Restaurant xx Xx zz Call Forwarding: 08:00-18:00 -> .. 18:00-08:00 -> ..

Personal Service Environment

Virtual VirtualHome HomeEnvironment: Environment:VHE VHE System SystemConcept Conceptfor for Personalized PersonalizedService Service portability across portability acrossNetwork Networkand andTerminals Terminalsboundaries boundaries
portability across network boundaries portability across terminal boundaries

10

Page 5

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

Network Convergence

Voice Services

Seamless Services

Data Services

Uniform Service Delivery Platform

Circuit-Switched domain
Traditional CS Co-existence

IP domain
All IP World
11

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

Evolution of Service Delivery Platforms

Multimedia Services
SIP App. Server Web/Application Server Application Server Parlay X OSA/Parlay Gateway

3rd Party Application Services (Enterprises / Content)

Focus of this Talk

IMS
AAA Server

OSA / Parlay Interface IN / CAMEL Services

SIP
SIP Server

IN Platform

Diameter

INAP/CAP Interface
Stored Program Control Services

= Services

VoIP

GPRS/UMTS

GSM

PSTN

12

Page 6

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

Next Generation Network 3 Tier Architecture

Enhanced services for the next generation network will be enabled by a tiered architecture where Application Servers will provide an independent service layer for the execution of enhanced services and content Session / Call Control based on advanced signaling protocols (i.e. SIP) is performed in Softswitches, or Session Servers Transport of signaling and content (incl. Voice) data will be done by Routers in the classical IP fashion. Dedicated nodes, i.e. Media Gateways and Media Servers are in charge for processing content data controlled by the Call Servers.

Application Server

Session Servers

Media Servers Routers

13

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

Next Generation All IP Reference Architecture

Connection / call control functions Application control functions Diameter SIP Session Control Function SIP Session Control Function SIP RTP SIP Subscription Server Function Diameter Application Server Function SIP Media Server Function SIP Media Gateway Function Signaling Gateway Function

AAA: User and Appl Profiles

Service Execution Service Management Service Creation IVR Conferencing Facsimile Speech Recognition Text-to-Speech

Basic call control Signaling Resource Management CDR Generation

Bearer data Transfer

SS7/IP Signaling Conversion

Note that there are many other IETF protocols used as well, 14 e.g. SDP, Megaco, SCTP, RTCP, MSRP, XCAP, etc.

Page 7

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

Overview
IMS Motivation IMS Overview IMS Key protocols (IETF SIP and Diameter) IMS Key components IMS Application Server options Sample IMS Multimedia Applications The IMS Playground @ FOKUS Summary Q&A and IMS Playground Demos References & Acronyms

15

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

Motivation for IMS

The Hope: Compete with classic internet services at weak points:
Provide QoS, security & charging and enable real integrated multimedia services

The Solution: the IP Multimedia System (IMS) as minimum common denominator Killer applications vs. universal service delivery platform
Flexible service creation and service deployment is key Openess to third party developers / providers ( controlled enabling) Integrated services integration of existing and emerging services Provide service uniform and seamless across different fixed and mobile networks

BUT: who will provide the global IMS and owns the customer??

16

Page 8

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

IMS Idea: Try to get Control of IP Services

A
IP

A
Control
by

B
IMS

Server

Server

The IP network allows free communication between endpoints IMS is able to control S(IP) services on an IP network
17

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

IMS enabling Control of GPRS / IP services

IMS Core Idea:
- Define an IP Multimedia Overlay-Network over GPRS (for Session control based on Internet protocols!) - Data (Media) transport (as well as signaling transport) via GPRS - Provide control (QoS, security, Charging) for IP services and person-toperson communication
IP Multimedia System (IMS)

Signalling (SIP)

Transport (RTP)

Packet Net (GPRS)

Circuit Switched Net (GSM)

Note that IMS is for fixed networks applicable too

18

Page 9

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

IMS Motivation Flexible Service Provision

Provision of service enablers - Presence and Group server are considered key for the future - Example: Push to Talk, but more generally community services
Messaging Server Application Server
Signalling (SIP)

Presence Server Call / Session Server

IP Multimedia System (IMS)

Transport (RTP)

Packet Net (GPRS)

19

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

IMS Architecture Principles

IMS does NOT standardise specific services, but enablers BUT supports inherently multimedia over IP, VoIP, IM, presence (SIP) IMS enables the flexibility in providing Multimedia over IP services !!

Architecture Applications Apps

Presence Presence Horizontal Architecture Build on existing IETF and telco SDP standards Use standard service enablers (e.g. Presence, GLMS/XDMS, etc.) Modular design and open interfaces

IMS

GLMS GLMS

and HSS Enablers Service IMS

RAN

SGSN GGSN Network

20

Page 10

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

3GPP IP Multimedia Subsystem (IMS)

The IMS was originally standardised by 3GPP as part of UMTS Release 5
Basic VoIP, IM, Presence support on top of GPRS Adaptations to real word have been made in Release 6 (QoS, PoC support) Release 7 will look at unified IMS for all IP access networks (DSL, WLAN, etc.)

The IMS is based on the IP world protocols, namely

SIP (Session Initiation Protocol) for Session Control, and Diameter for AAA (Authentication, Authorisation & Accounting) plus many others, i.e. SDP, RTP, RTCP, MGCP, etc.

Key components of the IMS architecture are

Extended AAA Server (Home Subscriber System as evolution of the HLR) SIP servers / soft switches Media Servers & Media Gateways and Application Servers

21

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

IMS Layers: Transport, Session Control, Apps

IMS Service Framework HSS (AAA)
Application Server IMS enabler Presence IMS enabler Group Mgt Media Server
MFRC + MFRP

P-CSCF
PDF

I-CSCF

S-CSCF S-CSCF

IMS Core System

Access Networks (WLAN, UMTS, DSL)

Media Gateway
SGW, MGCF, MGF
Interworking with Legacy Networks (GSM, ISDN, DVB)

Underlying IP Core Network

Note: IMS Charging Architecture is not reflected on this slides = Diameter Interfaces to many entities

22

Page 11

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

IMS Major Components

The IMS is an Overlay Session/Service Control architecture on top of the packet domain (GPRS, UMTS, WLAN, DSL) based on IP technologies and IETF protocols (e.g. SIP, Diameter):
IMS Core S-CSCF (Serving Call Session Control Function) the IS anker point in the home network I-CSCF (Interrogating Call Session Control Function) providing topology hiding P-CSCF (Proxy Call Session Control Function) Entrypoint into IMS world MS (Media Server) Media Server hosting special resources MGF (Media Gateway) for Interworking with legacy networks PDF (Policy Decision Function) for QoS Control using Polcies (COPS) IMS Application Layer HSS (Home Subscriber System) for maintaining subscriber and AS profiles AS (Application Server Function) for hosting applications IMS enablers (e.g. Presence, Group Mgt.) are specific ASs with generic functions And the IMS end system (IMS Client) plays an important role real multimedia / IMS services
23

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

Overview
IMS Motivation IMS Overview IMS Key protocols (IETF SIP and Diameter) IMS Key components IMS Application Server options Sample IMS Multimedia Applications The IMS Playground @ FOKUS Summary Q&A and IMS Playground Demos References & Acronyms

24

Page 12

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

IMS Layers: Transport, Session Control, Apps

r ete am Di
IMS Service Framework HSS (AAA)
Application Server IMS enabler Presence IMS enabler Group Mgt Media Server
MFRC + MFRP

Di

Di

r ete am

r ete am

SIP

SIP

SIP SIP

PDF

SIP

P-CSCF

I-CSCF

S-CSCF S-CSCF

SIP

IMS Core System

Media Gateway
SGW, MGCF, MGF
Interworking with Legacy Networks (GSM, ISDN, DVB)

Access Networks (WLAN, UMTS, DSL)

Underlying IP Core Network

25

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

IETF Session Initiation Protocol (SIP)

SIP is THE VoIP protocol enabling to initiate, terminate, and modify service sessions Multimedia(!) sessions (not just voice-centric!) Point-to-point and multiparty registration and modification of multiple user location information caller and callee authentication / call authorization privacy for call signaling and media streams media path with ensured QoS support through SIP servers (located inside and outside the network) Such as for presence and instant messaging No Bearer support (RTP and RTCP are used for that) !!

Support for

Flexible service creation Extensible protocol to cover new communication aspects Used together with Session Description Protocol Developed and maintained by IETF (MMUSIC and SIP WGs) RFC 3261: www.ietf.org/html.charters/sip-charter.html
26

Page 13

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

Local SIP Architecture

sip: iptel.org

27

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

Basic SIP Requests

REGISTER: allows Clients to register their current location (one or more addresses) INVITE: is used to initiate a call. ACK: is sent by a client to confirm that it has received a final response from a server, such as 200 OK. BYE: is sent either by the calling agent or by the caller agent to abort a call CANCEL: can be sent to abort a request that was sent previously as long as the server has not yet sent a final response. OPTIONS: allows clients to learn a servers capabilities. The server will send back a list of the methods it supports.

28

Page 14

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

Additional SIP Requests

SUBSCRIBE: starts or stops session or user supervision (event monitoring) NOTIFY: informs subscribed entity about occurred events PUBLISH: enables an entity to modify presence information MESSAGE: allows to send an instant message REFER: informs an recepient to contact a dedicated SIP user (e.g. MWI) PRACK: PRovisional ACKnowledgement UPDATE: Change of media (SDP) during session setup INFO: Exchange of any application layer information (e.g. DTMF)

29

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

SIP Responses
SIP Responses defined as (HTTP-style):
SIP-Version SP Status-Code SP Reason-Phrase CRLF (SP=Space, CRLF=Carriage Return and Line Feed) Example: SIP/2.0 404 Not Found First digit gives Class of response:
Description 1xx 2xx 3xx 4xx 5xx 6xx Informational Request received, continuing to process request. Success Action was successfully received, understood and accepted. Redirection Further action needs to be taken in order to complete the request. Client Error Request contains bad syntax or cannot be fulfilled at this server. Server Error Server failed to fulfill an apparently valid request. Global Failure Request is invalid at any server. Examples 180 Ringing 181 Call is Being Forwarded 200 OK

Plus 183 Session in Progress

300 Multiple Choices 302 Moved Temporarily 401 Unauthorized 408 Request Timeout 503 Service Unavailable 505 Version Not Suported 600 Busy Everywhere 603 Decline
30

Page 15

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

SIP Message Body = SDP

Message body can be any protocol However, in most implementations it is SDP (Session Discription Protocol)

SDP - Session Description Protocol RFC 2327 4/98 by Handley and Jacobson

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

Used to specify info about a multi-media session. SDP fields have a required order For RTP - Real Time Protocol Sessions:

RTP Audio/Video Profile (RTP/AVP) payload descriptions are often used

31

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

A SIP Signalling Scenario

Alices SDP included Alice
1. INVITE 2. INVITE 3. 100 Trying 5. 100 Trying 4. INVITE

atlanta.com

biloxi.com Provisional responses Connect to Alices media Bob

Forward to outbound proxy

8. 180 Ringing

DNS Query on Request-URI

7. 180 Ringing

Bob is alerted

Bobs IP Address stored in local Registrar

6. 180 Ringing

Connect to Bobs media

11. 200 OK

Bob accepts the session 9. 200 OK

10. 200 OK 12. ACK

Bobs SDP included

Media Session

Alice hangs up

Media disconnect
13. BYE 14. 200 OK
32

Page 16

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

SIP Server Operation Models

Redirect Server
Perry Redirect Server INVITE 302 Moved ACK INVITE 200 OK ACK RTP BYE 200 OK 200 OK ACK RTP Dave Perry INVITE 180 Ringing 200 OK ACK RTP BYE INVITE SDP B 200 SDP A2 ACK SDP A2

Proxy Server
Proxy Server INVITE 180 Ringing 200 OK Dave

B2BUA Server
B2BUA Server INVITE no SDP 200 SDP A1 ACK SDP held INVITE no SDP 200 SDP B Perry Dave

Transaction-oriented, Routing, Translation Services

Call Management, Event-driven Services

Call (Leg) Creation and Manipulation Services

33

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

Application Evolution - The SIP Influence

SIP as an open communications protocol is considered a key enabler for real-time converged communications and the development of interactive services.
SIP session and SIP-enabled services SIP-Services Conferencing Messaging SIP-Services basic SIP functionality User Presence/Availability
Establishment of user presence and availability (buddy-list functionality of IM)

SIP-enabled services

Unified Messaging Chat Multimedia Conferencing Push-to-talk Online Games Distributed Virtual Realtiy Systems Push Services Interactive Entertainment IP-PBX, IVR
34

Gaming

Video

Voice

User Location&Mobility
Establishment of current IP address. Support of personal and terminal mobility

Multimedia Support SIP Session

SIP Device

Supports voice, e-mail, IM, video and any other form of application with session characteristics Invite OK
ACK SIP Device

Invite OK
ACK

IP network

Call Setup & Processing

Establishment and management of communication parameters (e.g. codec, timeframe, )

Page 17

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

IETF Diameter Protocol for AAA

New IETF protocol for Authentication, Authorization and Accounting (AAA) services Internet Draft DIAMETER Framework (1998) by IETF AAA WG RFC 3588 DIAMETER Base Protocol (2003) Developed based on the requirements of 3G mobile network operators, ISPs and other IETF groups since 2001 Used in the 3GPP IMS for HSS access Extends the RADIUS functionalities: Introduction of Agent roles (proxy, relay, redirect & translation agents) Enables server-initiated messages Uses UDP, TCP and new SCTP protocol for reliable message transport Is backward compatible to RADIUS infrastrutures by using translation agents Integrates vendor specific commands and AVPs Explicit modular structure = is extendible
35

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

IETF AAA Work Group

GOAL
Develop the Diameter Standard based on the requirements of other IETF WGs (NASREQ, MOBILE IP, ROAMOPS), 3GPP and 3GPP2

WG defines: message format, error messages, accounting support, IPv6 support, backward compatibility with RADIUS, data model, security framework, Management Information Base (MIB) Achievements:
RFC 3588 Diameter Base Protocol Several other AAA RFCs multiple Diameter application drafts

Web link: www.ietf.org/html.charters/aaa-charter.html

36

Page 18

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

Diameter Base Protocol

RFC 3588 approved in September 2003 (NEW) provides an AAA framework for applications works for local AAA and in roaming situations The RFC defines
agent roles sessions and connections header, AVP and data formats Command codes, AVPs, Result codes and Diamter application IDs the state machines used within Diameter error handling, failover algorithms basic accounting procedures

Web link: ftp://ftp.rfc-editor.org/in-notes/rfc3588.txt

37

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

Diameter Extensions of the Base Protocol

Diameter is designed in terms of a Base Protocol (RFC 3588) and an extensible set of applications
Standardised by 3GPP IMS Group for HSS and Charging Interfaces

EAP MIP

IMS

Base Protocol

CMS

38

Page 19

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

Overview
IMS Motivation IMS Overview IMS Key protocols (IETF SIP and Diameter) IMS Key components IMS Application Server options Sample IMS Multimedia Applications The IMS Playground @ FOKUS Summary Q&A and IMS Playground Demos References & Acronyms

39

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

IMS 3GPP Evolution

IMS brainstroming started in Release 4, without real specs. IMS Release 5 is the first complete specification of IMS finished in 2003 (but based on some unrealistic assumptions;-( ) Key features of IMS Release 5:
IMS Architecture: IMS Architecture, network entities, reference points (interfaces) between the network entities. User Identities: Public/Private User Identity, usage of the SIP-URI and TELURI, ISIM, the use of the USIM instead of the ISIM. IMS Session Control: IMS Registration, IMS Session Routing, SessionModification and Teardown, SIP Signaling Compression. IMS Service Control: invocation/control of IMS Application Servers based on Filter Criteria in the CSCF. IM-SSF and there-use of CAMEL Services. Interconnect with the OSA-GW and the use of OSA services. QoS Mechanisms: QoS Preconditions, QoS/Media Authorization based on the PDF. Security Mechanisms: IMS User Authentication, Message Integrity Protection, IMS Network Domain Security.

40

Page 20

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

IMS 3GPP Release 6

Release 6 adapted IMS to the real world (i.e. lack of IMS SIM cards, IPv6 deployment, competing PoC standards), etc.) and was finished end of 2005 Key Features defined in Rel-6 IMS:
IMS Interworking: IMS Interworking to the CS-Domain (more details for CS and PSTN), Interworking with SIP Clients in the Internet (IPv4/v6 Interworking), WLAN access to the IMS (not completed) IMS Session Control: multiple registrations, routing of group identities. Security Mechanisms: confidentiality protection of SIP messages, use of public key infrastructure, Ut-interface security, early IMS security IMS Services: Presence, Instant Messaging, Conferencing, group management.

41

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

IMS Architecture
HSS Control Plane Traffic Plane

IMS
I-CSCF Mw P-CSCF

Cx

The HSS holds the IMS I-CSCF service profile of the subscribers.

Cx S-CSCF Mm

Other IP/ IMS networks

Go

Gi

UTRAN

CSCFs are the IMS entitiesGi responsible of the call control: there are 3 types of CSCFs depending on their role: P-CSCF (Proxy CSCF) S-CSCF (Serving CSCF) I-CSCF (Interrogating CSCF)

UE

S-CSCF interconnects to external IP networks and other IMS networks. If THIG is used by the operator to hide its internal configuration, the connection to external networks goes through an I-CSCF.

SGSN

GGSN
The PS domain provides the IP bearer to access to the IMS, i.e. a PDP context.

PS Domain

42

Page 21

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

IMS Architecture (cont.)

HSS Control Plane Traffic Plane

AS

I-CSCF

IMS
I-CSCF Mw

Cx

AS are connected via ISC interface (extended SIP) to S-CSF

In Release 6, the PDF can be separated from the P-CSCF. Those two entities are then connected through the Gq interface.

Cx S-CSCF Mr MRF

ISC
Mm Mi Mk

Other IP/ IMS network

The MRF is used for multiparty call P-CSCF control

Gq Go

Gi

Mg Mj

BGCF MGCF

UTRAN

Gi PDF Go Gi GGSN

IMSMGW

SGW Mn

Those entities are responsible for interworking between IMS and CS domain/PSTN

UE

SGSN

PS Domain

Legacy/ PSTN

43

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

IMS-Session: Home Networks are always involved

Caller
ISC

Home
Value Value added added services services

Home
Value Value added added services services

Called
ISC

S-CSCF

S-CSCF

Access WireLin WireLin e e WLan WLan UTRAN UTRAN

signaling

signaling

Access WireLin WireLin e e WLan WLan GPRS GPRS

TA? UTRAN UTRAN FW? Bearer Services Bearer Services oriented oriented

FW? Bearer Services oriented

TA? GPRS GPRS

TA?

Video/Audio/Signaling

IP backbone

Video/Audio/Signaling

44

Page 22

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

IMS: Separation of Signaling and Media transport

mobile to mobile session
User A As visited network IMS GPRS GPRS Required on As home network registration, optional on Value Value added added session establish

GGSN GGSN

P-CSCF P-CSCF

S-CSCF S-CSCF

services services

I-CSCF I-CSCF I-CSCF I-CSCF

Optional

User B

I-CSCF I-CSCF

I-CSCF I-CSCF
Required on registration, optional on session establish

P-CSCF P-CSCF

GGSN GPRS GGSN

IMS

Value Value added added services services

S-CSCF S-CSCF

Bs home network

Bs visited network
45

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

IMS User Identity Concept

Each IMS User has at least one private and one or more public User Identities IMS Private User Identity:
belongs to the IMS operator is not used for routing of SIP messages uses the format defined in RFC 2486

Example: [email protected]
is stored on the ISIM card (in the mobile phone) and in the HSS (in the IMS User Profile)

IMS Public User Identity:

is public and may be subject to Number Portability is used for routing of SIP messages may use the SIP-URI format defined in RFC 3261 and/or the TEL-URI format defined in RFC 2806

Example SIP-URI: sip:[email protected] Example TEL-URI: tel:+491231234567

At least one Public User Identity is stored on the ISIM card All Public User Identities are stored in the HSS
46

Page 23

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

Public Service Identities (PSIs)

Similar to public user identities, but allocated to services (ASs) rather than users Used to identify specific applications Servers (enablers), such as presence or group list servers Typically take the form of a SIP URI or TEL URI
sip: [email protected], [email protected], [email protected] tel: +49-900-123-456

PSIs are treated as PUIs, i.e. easy routing of SIP requests to ASs (as end user systems also called service routing Public Service Identities are not authenticated
i.e., there is no corresponding private user (service) identity

47

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

How the IMS differs from RFC 3261 SIP Servers

The IMS was designed based on RFC 3261 (the CSCF is basically also a SIP Server) but includes much more! Additional functions were added to the IMS:
Subscriber Management, Service Control, Single-Sign-On User Authentication, QoS/Media Authorization, Charging and Charging Correlation, Resource Management, Interworking, Compression, Conferencing Support, Regulatory Service Support, etc.

Most of the IMS functions were taken from the IETF or were afterwards defined in the IETF:
Update (RFC331), Preconditions (RFC3312), PRACK (RFC3262), Offer/Answer (RFC 3264), QoS/Media Authorization (RFC 3313), Event Notification (RFC 3265), Tel-URIs (RFC 2806), 3GPP P-Headers (RFC3455), Service-Route (RFC3608), Asserted ID (RFC3325), DNS-Support (RFC 3263), SigComp (RFC3320, RFC3485, RFC 3486), ENUM (RFC2916, RFC2915), SIP Refer (RFC3515), Digest AKA (RFC 3310), Path-Header (RFC 3327), Security-Mechanism-Agreement (RFC3329), etc.

A Service Infrastructure Network could also be built up starting with a standard RFC 3261 SIP Server. When extended to support the same Support Functions, then such a solution becomes similar to the IMS.
48

Page 24

User Registration and Authentication

UE SGSN HLR GGSN CSCFs HSS IMS-AS Bearer Level Authentication IP Transport setup

GPRS Attach

PDP Context Activation IMS Registration and User Authentication

IMS Registration

IMS Service Access

IMS Service Access
49

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

IMS Session Setup & Control

This happens after User Registration (and Authentication!) Why do we need the IMS Session Setup ?
1. Capability Negotiation (e.g. negotiation of session components, codecs, port numbers, addresses, etc.) 2. Network Resource Reservation and the support of QoS Preconditions

Additional Functions performed by the IMS during the IMS Session Setup:
Routing to the Terminating IMS (= the IMS of the B-Party) Routing / Breakout to the PSTN / CS-Domain when the B-Party is not in the IMS, but in the PSTN / CS-Domain Service Control / Invocation of Application Servers to trigger the execution of Originating- and/or Terminating IMS Services Integrity/Confidentiality Protection of SIP Messages QoS/Media Authorization SIP Signaling Compression
50

Page 25

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

IMS QoS Support

The actual Network QoS for IMS services is provided by the Access Network (e.g. based on UMTS QoS) and the IMS network infrastructure (e.g. based on Diff-Serv support in routers and switches). The IMS provides a correlation and control mechanism based on the use of the Policy-Decision-Function (PDF). Key functions of the PDF:
acts as Policy Decision Point (PDP): the GGSN is the corresponding Policy Enforcement Point (PEP). authorizes and controls the resource usage for each bearer (e.g. GPRS/UMTS PDP-Context): this prevents the misuse of Network QoS and the theft of service. this allows to limit the resource consumption. exchanges Charging Correlation Identifiers with the GGSN (ICID, GPRS Charging ID): this allows the correlation of charging information generated in the PSDomain (SGSN, GGSN) and in the IMS (e.g. CSCF, AS).
51

IMS Session Control Complex Scenario

UE-A GGSN P-CSCF S-CSCF I-CSCF S-CSCF P-CSCF GGSN UE-B User A Registered User B Registered

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

S 3 RR
Go

INVITE 183 PR PRACK 200 OK

1 2

B
180 Ringing

Go

RR

200 OK 200 OK Go 200 OK

Go

O
ACK

Media Transport (RTP)

S 1
Service Control Token generation

2 RR

Resource Authorization Resource Reservation

3 B

Same as 1,2 Verify binding

O
Open gate
52

Page 26

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

IMS Session Binding and QoS Bearer Control

The Media/QoS Authorisation is performed on a per-session basis using the Go-interface and an IMS Authorisation Token used for the IMS Session Binding.
enables the IMS to: authorise/open/close/modify the IMS Bearer Path (e.g. for Voice/Video Traffic).

IMS Application Servers are not involved in the IMS Session Binding Procedure.

53

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

Session Initiation - 1
Originating Visited Originating Home Network Network Terminating Home Network Terminating Visited Network

IMS Terminal #1

P-CSCF

S-CSCF

I-CSCF

HSS

S-CSCF

P-CSCF

IMS Terminal #2

(1) INVITE (2) 100 Trying

(3) INVITE (4) 100 Trying Evaluation of initial filter criteria (5) INVITE (6) 100 Trying

Provisional responses to avoid retransmissions

DNS query on Request-URI Locating S-CSCF where the called-party is registered

AS Services for caller

(7) Diameter LIR (8) Diameter LIA (9) INVITE (10) 100 Trying

AS Services for callee

Evaluation of initial filter criteria (11) INVITE (12) 100 Trying

Local registrar look-up for callees address

(13) INVITE (14) 100 Trying (15) 183 Session Progress

Pre-alert user

Authorize QoS resources (PDF)

(20) 183 Session Progress (19) 183 Session Progress

(17) 183 Session Progress (18) 183 Session Progress

(16) 183 Session Progress

Authorize QoS resources (PDF)

Callee is reachable, begin resource reservation

54

Page 27

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

Session Initiation - 2
Originating Visited Originating Home Network Network Terminating Home Network Terminating Visited Network

IMS Terminal #1

P-CSCF

S-CSCF Authorize QoS resources (PDF)

I-CSCF

HSS

S-CSCF

P-CSCF

IMS Terminal #2
Resource Reservation

(20) 183 Session Progress (21) PRACK Resource Reservation

(22) PRACK (23) PRACK (24) PRACK (25) PRACK (26) 200 OK (27) 200 OK (28) 200 OK (29) 200 OK

PDP context activation

(30) 200 OK (31) UPDATE (32) UPDATE (33) UPDATE (34) UPDATE (35) UPDATE

PDP context activation QoS use enabled

(38) 200 OK (39) 200 OK (40) 200 OK

(36) 200 OK (37) 200 OK

Alert user

QoS use enabled

55

Originating Leg Terminating Leg

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

Session Initiation - 3
Originating Visited Originating Home Network Network Terminating Home Network Terminating Visited Network

IMS Terminal #1

P-CSCF

S-CSCF

I-CSCF

HSS

S-CSCF

P-CSCF

IMS Terminal #2
Alert user

(41) 180 Ringing (42) 180 Ringing

Aknoledges phone ring

(46) 180 Ringing (47) PRACK

(43) 180 Ringing (44) 180 Ringing (45) 180 Ringing

Phone starts ringing

(49) PRACK

(48) PRACK

(50) PRACK

(51) PRACK (52) 200 OK

(53) 200 OK (54) 200 OK (56) 200 OK (55) 200 OK (58) 200 OK (61) 200 OK (60) 200 OK (59) 200 OK (57) 200 OK Accept session

(62) 200 OK (63) ACK

Starts media flow

(65) ACK

Answer the call

(64) ACK

Starts media flow

(66) ACK

(67) ACK

Media Transport (RTP)

56

Page 28

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

IMS charging and operator strategy

Pricing based on transport
Mobile Operator
1 per MByte Instant Messaging Chat Sessions Voice Communication Video Communication

GGSN

Pricing based on services

IMS
Mobile Operator
0,02 per Instant Message 0,10 per Minute for 128 kbit/s Video

GGSN

2 per Month for Presence

IMS charging provides operators to be more than bit pipe provider

57

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

IMS Charging Architecture

The IMS is designed to satisfy multiple business models The IMS charging model provides high flexibility Examples:
Charging based on time, bandwidth (AMR vs. G711), media stream (audio, video), services (e.g. instant message, content, etc.), events (presence, warnings etc.)

IMS supports two charging architectures

Offline Charging (e.g. for post paid contracts) Online Charging (e.g. for prepaid contracts)

Main protocol used for charging is Diameter

With addition of a few AVPs in the Diameter base protocol With the addition of a credit control application to support offline charging (Rf interface)
58

Page 29

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

IMS Charging Architecture

Diameter File Transfer CAP

Billing System

SIP-AS (Supplementary Services)

P-CSCF

S-CSCF

Offline Charging

Messaging Server

IMS Elements Bearer Elements

Online Charging

59

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

Offline Accounting Principles

Charging Trigger Function (CTF)
watches for accountable events sends them
CN Domain C Service element T Subsyst em F C Rf D F Ga C G F Bx Billing Domai 3GPP net work

Charging Data Function (CDF)

construct CDRs from events received via Rf reference point events may be of several types

Charging Gateway Function (CGF)

collect, validate and (persistantly) store CDRs (in files) forward batch files to Billing domain
60

Page 30

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

Online Accounting Principles

Charging Trigger Function
Sends events for authorization to OCF Must delay resource usage until permission is granted Must support quota supervision during resource usage/consumption
CN Domain C Service element Subsystem T F Ro CAP O C F Re
RF

3GPP network OCS Rc

ABMF

Online Charging Function has 2 modules

Session based Charging
charges network / user sessions (e.g. voice calls, GPRS PDP contexts or IMS sessions)

Event based Charging

event-based online charging (also referred to as content charging) in conjunction with any application server (e.g. SIP) or service NE

Account Balance Management Function Rating function (for data volume, session time & service events)
61

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

IMS Security
Two security solutions are proposed Full IMS security
Standardized in Release 5 and 6 with full features Defines security in the network and the terminals Requires ISIM and rich features in the terminal, P-CSCF and S-CSCF

Early IMS Security

Standardised in Release 6 Idea: Reuse GPRS authentication (and IP address) for IMS authentication Developed for early IMS deployment without existance of all security enablers Not stringend as the full IMS security solution Intended to have minimal impact on existing terminals Offers less security but good enough for early deployment
62

Page 31

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

Complete IMS Security Solution

Divided into:
Network Domain Security (already existing for GPRS) Access Domain Security (linked to SIP and CSCFs / HSS)

SIP Security is provided on a hop-by-hop fashion

End-to-end security is not supported !

Terminals accept a UICC (Universal Intergraded Circuit Card) that contains an ISIM (IMS Subscriber Identity Module) application The ISIM stores identities (public, private), home domain, and long term security keys The S-CSCF authenticates the user at SIP registration time The security mechanism is negotiated (but only IPSec is supported so far) Authentication scheme based on the UMTS AKA (Authentication and Key Agreement) called IMS AKA Delegate identity enforcement to the P-CSCF P-CSCF and UE establish an IPSec connection for integrity protection (Release 5 onwards) and confidentiality (Release 6 onwards)
63

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

Complete IMS Security

IMS Security

Authentication & Key Agreement (AKA)

IMS Home

Security Mechanism Agreement

Network Domain Security

SIP UA

IMS Visited
Integrity Protection

Secure Secure Apps Apps Non-secure Apps

64

GPRS Domain
Existing GPRS Access Security

Page 32

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

Overview
IMS Motivation IMS Overview IMS Key protocols (IETF SIP and Diameter) IMS Key components IMS Application Server options Sample IMS Multimedia Applications The IMS Playground @ FOKUS Summary Q&A and IMS Playground Demos References & Acronyms

65

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

IMS Service Invocation and Interaction

Service triggers on initial SIP requests at SIP Proxy (S-CSCF) Service Proxy proxies request to corresponding AS based on triggers and Filters AS acts as user agents, proxy server, 3PCC or B2BUA AS may Record-Route SIP request to stay in signalling path Service Proxy maintains the states between dialogs sent to/from applications

App Server
SIP Initial Req SIP Request

SIP Initial Request

Triggered!

SIP Request

S-CSCF
66

Page 33

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

SIP enables different AS Modes of Operation

Four modes of operation are distinguished: Application Server acting as terminating UA, or redirect server Application Server acting as originating UA Application Server acting as a SIP proxy Application Server performing third party call control/ B2BUA mode

AS (Content Server)

AS (Wake up Svr)

AS (Call Forw.)

AS (Click2Dial)

SIP
CSCF

RTP
CSCF CSCF CSCF

B A B A B
67

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

How does a SIP AS Provide Enhanced Services

S-CSCF determines that a call requires enhanced service processing
Filtering may be based on calling / called party or other mechanism (defined by filtering criteria) eg. SIP message type, header fields, etc.

Based on filtering criteria, the S-CSCF determines the address of the Application server and relays the call to the AS function. The Application Server receives the call and invokes the appropriate service logic taking one of the following actions:
Redirects the call to a new destination Send the call back through the S-CSCF in order to monitor subsequent call events (ie act as a SIP Proxy)

The Application Server (based on some other input) can also set-up calls between other entities in the network (ie. act as a B2BUA)

68

Page 34

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

Major Service Platform Interfaces

Application Data (Filter Information) Note: Cloning of IN principles! User status changes

Service Delivery Platform (Application Server) Value Added Services

HSS Sh = Diameter
User Cx = Authentication User locationDiameter User Profile (Filter Information)

Service Platform Trigger Points Service Platform Adaptor SIP B2BUA Interface

ISC = Ext. Session Initiation Protocol

Application specific service control

S-CSCF
SIP Proxy Server

SIP

S Filter criteria 2 SPT Mapping P T Detection Points: DP Criteria:

Methods / Responses, Headers, SDP info, etc

SIP

AS-Specific Methods / Responses, Headers, SDP info, etc set by AS/HSS

69

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

Cx (and Dx) Interface

Cx - Interface supports information transfer between S-CSCF and HSS
Diameter application for user profile handling & user authentication to exchange location information

to authorize a user to access the IMS

to exchange authentication information to download and handle changes in the user data stored in the server

Dx Interface between I-CSCF and the Subscription Locator Function (SLF) in case of HSS look-up
Diameter redirect agent functionality to retrieve an HSS address

Both RPs are pecified in 3GPP TS 29.228 and TS.29.229

TS 29.228 IM Cx and Dx interfaces; Signalling flows and message contents TS 29.229 IM Cx and Dx interfaces based on the Diameter protocol; Protocol details
(http://www.3gpp.org/ftp/Specs/archive/2x_series/2x.xxx)
70

Page 35

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

Sh Interface
Interface between HSS and Application Server (AS) Diameter application that allows a Diameter server and a Diameter client:
to download and update transparent and non-transparent user data to request and send notifications on changes on user data

Further information on the Sh reference point is provided in

TS 29.328 IM Sh interface; Signalling flows and message contents TS 29.329 IM Sh interface based on the Diameter protocol; Protocol details

71

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

IMS Filter Criteria

IFC Details: - the IFC contents: 1) Trigger Point 2) Service/AS Identifier - Trigger Point contains one or more Service Triggers linked via the logical expressions (AND, OR, NOT, EQUAL ) - Service Trigger includes: 1) Request URI content 2) SIP Method, eg. INVITE, REGISTER ... 3) SIP Header content 4) Session Mode (originating, terminating) 5) SDP content AS Identifier have SIP URI format e.g. sip:[email protected]

72

Page 36

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

IMS Initial Filter Criteria

The IFC is the key point for service provisioning in IMS and specified in 3GPP TS 23.218 and 29.228 The S-CSCF downloads the IFCs for a particular user from HSS and has the ability to forward SIP messages to an appropriate Application Server (SIP AS, OSA SCS) AS application/service invocation is triggered as a result of a pattern matching on any SIP header or body

AS 1

Application Application

AS 2 3 INVITE

Application Application

AS 3

Application Application

2 INVITE
iFc 1 met

4 INVITE
iFc 3 met

5 INVITE 6 INVITE

1 INVITE

Filter Criteria 2 SPT Processing Prio 1 = AS1, Prio 2 = AS2, Prio 3 = AS 3, etc.

S-CSCF

IM User Profile(s)

Cx - User Profile download/update HSS

IM User Profiles storage
73

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

Scalability of the IMS

Sh SIP AS 1 SIP AS 2 SIP AS X

HSS

ISC

S-CSCF 1 Cx

S-CSCF 2

S-CSCF Y

74

Page 37

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

Requirements for an Application Server

Same as the definition for application servers it is hard to set the boundaries of the requirements for application servers. There are must have requirements for application servers.
Same requirements on scalability, fauth tolerance, security and so on as for any other entity in an IMS environment. An Application Server must have at least one Application Programming Interface (ISC). An Application Server must have at least one standard compliant network interface.

There are may have requirements for application servers.

Certain applications require multiple standard compliant network interfaces. Certain applications require multiple Application Programming Interfaces.

75

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

Network Interfaces and APIs of a SIP AS

Within this Part of the tutorial we have a close look into all parts of an application server!

76

Page 38

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

IMS Application Server Options

Diameter SIP

Application Servers
SIP AS

OSA AS OSA GTW

SIP
Local AS

CAMEL IM-SSF

HSS (AAA)

P/I/S-CSCF (SIP Proxy)

Media Server

PDF

SIP Server
RTP

IMS Core Server

77 78

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

Different AS Alternatives
CAMEL Services via Camel Support Environment (CSE):
intended for the support of existing IN Services (provides service continuation).

OSA Services via Open Service Access Service Capability Server:

intended for the support of 3rd Party Application Providers. OSA SCS provides access and resource control.

IMS services on SIP-Application Server:

intended for new services. A multitude of widely known APIs (CGI, CPL, SIP Servlets) is available.

IMS services directly on the CSCF (similar to SIP AS):

SIP-AS co-located on the CSCF seems to be useful for simple services. May be beneficial for the Service Availability and the Service Performance.

Page 39

Application Server

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

CAMEL Reuse within IMS

SIP 2 CAP mapping needed! IN SCP S h
Sh = Diameter Cx = Diameter S-CSCF
SIP-Server

IN App 1 CAP

CAMEL Support Env. (Application Server)

HSS

CAP Interface
Service Platform Trigger Points IM SSF (SIP2CAP)

IM SSF

SIP Interface

Diameter
Ro + Rf = Diameter

ISC

Online &Offline Charging (ECF, CCF)

SIP

S P T

Filter criteria

79

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

OSA / Parlay AS within IMS

Service Delivery Platform (Application Server)

Parlay App 1 Parlay App 2 Parlay AS (API)

Parlay X App Parlay X App

Parlay X GW
MMM PRES CHARG

HSS
Sh = Diameter Cx = Diameter S-CSCF
SIP-Server

Sh

FW

MPCC

Parlay GTW

SIP Interface

Diameter
Ro + Rf = Diameter

ISC

Online &Offline Charging (ECF, CCF)

SIP

S P T

Filter criteria

80

Page 40

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

SIP Application Server (Servlets)

HSS
Sh = Diameter Cx = Diameter S-CSCF
SIP-Server

S h

SIP Service Servlets SIP Service Servlets

Service Points SIP Platform Servlet Trigger Engine

SIP Interface

Diameter
Ro + Rf = Diameter

ISC

Online &Offline Charging (ECF, CCF)

SIP

S P T

Filter criteria

81

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

SIP AS vs. CAMEL vs. OSA/Parlay

CAMEL supports:
legacy IN services in 2G and 3G networks Services based on proven and reliable IN technology (reuse!) But CAMEL is expensive and limited in evolution

SIP AS supports:
Multimedia conferencing services, integrated with HTTP Exploitation of cheaper internet technology Easier service creation, but not yet proven for carrier grade services

OSA is an API (!!) which could be mapped to boh CAMEL and SIP
OSA is enabling EAI in Telecoms Proven technology (reuse of existing services in NGN) Support implementation of different business model (walled vs. open garden) Best support of 3rd parties
82

Page 41

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

Relating OSA/Parlay vs. CAMEL vs. SIP AS

Seamless NGN Services (opt. by 3rd Parties)

OSA/Parlay FMC Services (Apps Servers)

Parlay (X) API

Build new MM Services

OSA OSAGateway Gateway HSS SIP AS (AAA) SIP CAP S-CSCF PDF PDF

OSA OSAGateway Gateway Camel CSE

Reuse CAMEL Services

3GPP IMS WLAN / WAG DSL

CAP

CAP GSM /

GPRS
GGSN SGSN MSC
83

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

Overview
IMS Motivation IMS Overview IMS Key protocols (IETF SIP and Diameter) IMS Key components IMS Application Server options Sample IMS Multimedia Applications The IMS Playground @ FOKUS Summary Q&A and IMS Playground Demos References & Acronyms

84

Page 42

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

IMS integrates different Communication Services

Pre-IMS Communication (Service Islands)
Voice Voice / Video SMS Instant Messaging MMS SMS Instant Messaging MMS

IMS Communication (Combinational Services)

From the usage of specific individual communication services ...

... to the integrated usage of different communication services centered around presence information and within groups ( communities)
85

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

IMS Applications

86

Page 43

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

IMS for VoIP Supplementary Services

Example IMS Service Architecture for an IMS Voice/Video/Data telephony service:
the SIP-AS provides Supplementary Services such as e.g. Call-Forwarding, Call-Barring, Simultaneous-Ringing, etc.

Applications

Applications
87

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

IMS for Presence, Push 2 Talk, IM

Example IMS Service Architecture for the IMS services:
Presence, Push-to-Talk (PTT), Instant Messaging (IM)

Applications

Applications
88

Page 44

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

OMA Service Enablers and IMS

IMS provides the following:
Routing and reachability Authentication and transitive trust Signaling compression Privacy User profile storage Charging, accounting Interface to the access network OMA for Application Enablers Standards

OMA SIP-based service enablers are specified on top of IMS as common platform, e.g.
Presence, Group Management, etc.

3GPP for Network Architecture

89

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

OMA Service Enablers and IMS

OMA service enablers
PoC Messaging Other enablers

ISC

Registration

Session Control

Charging

IP Transport IMS

90

Page 45

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

Push to Talk over Cellular (PoC)

PoC is standardised in the Open Mobile Alliance (OMA), Rel. 1 in 2005 First specification process was initiated by the MENSA (Motorola, Ericsson, Nokia, Siemens, AT&T Wireless) consortium in 2002, 2003 PoC is a way of communication that uses half-duplex connections
similar to walkie-talkie functionality allows to deliver a talk burst to a collection of users

PoC client is (usually) in the handset as a soft client PoC server has ambiguous functionality: It manages both the signalling and also the media
By definition the PoC server is acting as a SIP AS, connecting to IMS CN through the ISC interface

OMA PoC does not consider access network issues (any access network can be used) OMA PoC requires the XML Document Management (XDM) enabler for group session configuration OMA PoC may use OMA XDMS architecture for presence as a presence enabler Dedicated floor control messages are used to grant access to the floor to ensure semi-duplex paradigm

91

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

MENSA PoC Architecture Rel. 1 (2002)

Im

GLMS
Ipl

Ik

Introduction of Group List and Management Server No presence functionality required

PoC Server

ACCESS

Presence Server
Ips If

No Network-Network Interworking (NNI) No automated device configuration

UE

IMS Core (CSCF/HSS)

It (talk)

If

Source: PoC MENSA Rel. 1.1

92

Page 46

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

OMA PoC Architecture Rel. 1 (2005)

DM Client
Presence Source Watcher DM-1

DM Server
PRS-3

PRS-1 Presence Server

Used Protocols: SIP RTP/RTCP RTCP XCAP Remote PoC Network Remote PoC Network
PRS-5 Shared XDMS

PRS-2

ACCESS NETWORK

XDM-2 XDM-3

Aggregation XDM-4 Proxy PoC-6 PoC-7 PoC XDMS PoC-8 PoC-5 PoC Server XDM-3 XDMC

XDMC

XDM-1

PoC-1 PoC-3

PoC-2

PoC Client

PoC-4

UE

Introduction of OMA Enabler architecture for PoC XML Document Management Enabler Alignment of PoC Architecture to OMA enabler concept Presence Enabler Device Management Enabler NNI
93

SIP / IP Core

IP-1
Source: OMA/PoC Candidate Version 1.0

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

3GPP2 Multimedia Domain (MMD)

3GPP2 MMD is a reference architecture model for cdma2000 family based wireless core network Main specifications: - All-IP Core Network Multimedia Domain: Overview
http://3gpp2.org/Public_html/specs/X.S0013-000-0_v1.0_022604.pdf

- IP Network Architecture Model for cdma2000 Spread Spectrum Systemshttp://3gpp2.org/Public_html/specs/S.R0037 http://3gpp2.org/Public_html/specs/S.R0037-0_v3.0_111303.pdf

based on IP protocols, elements and principles Main protocols are (IETFs) SIP, DIAMETER and Mobile IP Consists of:
Packet Data Subsystem (PDS): supports general packet data service IP Multimedia Subsystem (IMS): provides multimedia session capabilities
94

Page 47

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

3GPP2 vs. 3GPP

Feature
Mobility management IP version HSS Speech codec P-CSCF discovery Si interface Smart card GPRS tunneling IPv4 and IPv6 Database and AAA AMR Through PDP context activation and DHCP Between HSS and IM-SSF (CAMEL) Defined a UCC (USIM or ISIM)

3GPP
Mobile IP IPv6

3GPP2

Database only, separated AAA EVRC and SMV No support of PDP context Not defined, since there is no CAMEL Configuration and security stored in the IMS terminal or in R-UIM (Removable User Identity Module) P-CSCF and PDSN (Packet Data Service Node == GGSN) may be in different network May change even during a session Not defined yet Through a Position Server and Position Determining Entity (PDE)

P-CSCF location

P-CSCF and GGSN are in the same network Allocated prior to registration Defined between PDF & GGSN Through Sh interface

Anchored GGSN/PDSN Go interface Location information

95

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

The NGN Definition

96

Page 48

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

NGN Global standards cooperation

s ce rvi e S
Open Mobile Alliance
Defining IMS services, e.g. Instant Messaging, Push-to-Talk Not strictly mobile oriented, driving wireline services also

The Parlay Group

Integral to IMS architecture, define standard API frameworks

& line Wire rged e v n res Co ectu rchit A N NG

Alliance for Telecommunications Industry Solutions

Agreement on reuse of 3GPP/3GPP2 IMS in comprehensive NGN plans

TISPAN ETSI body on Next Generation Network

cy ga Le re ctu n ites Drive h c s ArWirele

American National Standards Institute

T1.679 covers interworking between ANSI ISUP and SIP Leveraging IMS in wireline

Nearing agreement to use 3GPP/3GPP2 IMS

ITU-T NGN Focus Group ITU-

CJK China Japan Korea

Starting Focus Group on NGN

International Telecommunication Union

Q.1912.SIP covers interworking between ITU-T ISUP and SIP H.248 for media control

3rd Generation Partnership Project 3rd Generation Partnership Project2

Define IMS network elements and infrastructure Harmonization effort has kept definitions as similar as possible

ols To

Internet Engineering Task Force

Defines SIP, SDP and other protocols underlying IMS IMS is driving some of the work in IETF

Building the NGN through Cooperation between many Standards players (incl. DSL, MSF, TMF ): leading to convergence

97

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

ETSI TISPAN

98

Page 49

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

TISPAN NGN Functional Entities

S e r v ic e S tr a tu m

A p p lic a tio n F u n c tio n s

U ser P ro file F u n c tio n s O th e r M u ltim e d ia C o m p o n e n ts S tre a m in g S e r v ic e s P S T N / IS D N E m u la tio n IP M u ltim e d ia C om ponent

S e rv ic e and C o n tro l F u n c tio n s

Other Networks

GW
Legacy T e r m in a ls

N e tw o rk A c c e ss A tta c h m e n t F u n c tio n s NAAF

R e s o u rc e a n d A d m is s io n C o n tro l F u n c tio n s RACF

C u s to m e r N e tw o r k s A cc ess F u n c tio n s

A c c e s s T ra n s p o rt F u n c tio n s

NGN T e r m in a ls

E dge F u n c tio n s

C o re tra n s p o rt F u n c tio n s
T r a n s p o r t S tr a tu m
NNI
99

C u s to m e r a n d T e rm in a l F u n c tio n s

UNI

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

IMS Architecture in the NGN setting

Rf / Ro Ut Sh

AS
Dh ISC Cx Mw Dx

Ch ar gi n g Fun ct i on s
SLF
Rf / Ro Ib M w /M k/ M m Mi Mk

UPSF Network Attachm ent Subsystem Core IM S

If

IW F
Ic

Ia

I/S-CSCF
Mw Mr

IBCF

BGCF
Mj Mg

Mk

Other IP Networks

Id

P-CSCF
Gq

M RFC

M GCF

Ie

SGF PSTN/ISDN

Gm

Mp

Mn

Resou rce an d Adm i ssi on Con t rol Su bsy st em MRFP

T-M GF I-BGF

UE

IP Transport (Access and Core)

Network Interconnections

100

Page 50

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

TISPAN PES - Functional Architecture

Ut Ut

Application Servers
Other types of service logic PSTN/ISDN Emulation logic
ISC/Ma Cx Dh Dx

Rf/Ro Rf/Ro

Charging Funct ions

Rf/Ro

Network Attachment Subsystem

e2 e2

Sh

UPSF

SLF
P3

Ib

IWF
Ic

Iw

IMS-based PES

AGCF

Mw

Mx

Mw P1 Mw Gm

I/S-CSCF
Mr Mx

Mi

Mx

IBCF

BGCF

Mk

Other IP Networks

Mj Mg

Gq' Ie

P-CSCF

MRFC

MGCF

SGF PSTN/ISDN

Gq' Ut

Gq' Mp Mn

Resource and Admission Cont rol Subsyst em VGW Z MRFP T-MGF

MG

IP Transport (Access and Core)

I-BGF
101

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

3GPP R6 and TISPAN R1 NGN: R6 comparison

Network Attachment System 3GPP: TISPAN: GPRS entities + HLR (PS part) NASS entities

Resource Admission Control 3GPP: TISPAN: PDF and GGSN RACS entities + RCEF and BGF entities

MM Session Control 3GPP: TISPAN (R1) IMS (R6) IMS (R6)

TISPAN Documentation: http://portal.etsi.org/docbox/tispan/Open/NGN-R1/Stable_Drafts/

102

Page 51

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

Upcoming IMS Release 7

Emergency calls in PS and IMS
TR 23.867 - Two building blocks: IMS and PS side. IMS side is given priority to meet TISPAN Rel1 schedule. TISPAN inputs and requirements will be taken into account

End-to-end QoS
TR 23.802 provides various scenarios and mechanisms to manage and guarantee e2e QoS

Policy Control Evolution and Charging

TS 23.803 - Evolution of the Policy Control and IP Flow Based Charging addition of subscription profile to Policy Control Merging of Go and Gx interface

Mp (MRFC - MRFP) interface protocol definition

103

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

Overview
IMS Motivation IMS Overview IMS Key protocols (IETF SIP and Diameter) IMS Key components IMS Application Server options Sample IMS Multimedia Applications The IMS Playground @ FOKUS Summary Q&A and IMS Playground Demos References & Acronyms

104

Page 52

Joseph von Fraunhofer (1787 - 1826)

The person who has given the name is a good example for what we do!
Scientist Discovery of Fraunhofer-Lines within the sun light spectrum Inventor New processing methods for lense crafting Entrepreneur Director of a glass works factory

105

Fraunhofer Society: Profile

58 Institutes
7 Alliances Microelectronics Production

12 750 Employees 1 Billion Budget

Information and Communication Technology

Materials and Components Life Sciences Surface Technology and Photonics Defence and Security

106

Page 53

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

Fraunhofer FOKUS Facts

FOKUS has been founded 1988 in Berlin, Germany 220 employees: scientists, students, technicians originating from 30 nations FOKUS is THE Telecoms R&D institute within the Fraunhofer Society Fraunhofer Society is the biggest German R&D organisation, total # of 12.000 employees) 60 institutes in total, 15 institutes in ICT FOKUS works since 17 years on convergence of IT, telecoms, internet and home entertainment and performs applied research and development projects Performs strategic studies, solution concepts, system integration and prototyp developments Strong cooperation with universities & Establishment of spin offs (e.g. iptelorg.com) FOKUS fundung: 20% state, 80% industry R&D projects Key to success: Strategic Partnerships with big players (DTAG, NTT, etc) Main R&D Vision: I-centric communications and autonomic communications
107

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

NGN Testbed @ Fraunhofer FOKUS

National 3Gb R&D Projects European 3Gb R&D Projects

Nat. Open 3Gb Test & Development Center Provision of a unique 3Gb Testbed covering all three 3G beyond layers Foundation for industrial and academic projects

mHealth

mGov

mXXX.

weitere Other weitere Apps

Engineering Tools,Conformance Testing, Measurments, and Management

Applications

Applications development support Applications validation Service Platform prototyping Infrastructure component testing Network Technologies integration ....
Officially supported by

Parlay Playground
Web services Parlay IMS AAA SIP Other weitere platforms 3Gb Roaming Service Platforms & Middleware

IMS Playground

UMTS FDD/ TDD

GSM / GPRS

WLAN a/b/x

DVBS/T

Other weitere Netws

3Gb Network Technologies

www.fokus.fraunhofer.de/national_host
108

Page 54

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

IMS playground @ FOKUS

forms a globally unique state of the art IMS infrastructure featuring all major IMS componentsand interfaces is a key infrastructure of the FOKUS NGN Service Delivery Platform test and development center comprises a full IMS based on own developments additional best of bread carrier grade components from partners Goals: Provision of an open IMS platform and planned interconnection to Operator IMS test beds Interoperability test of IMS components (S-CSCFs, Media Gateways, SIP AS, etc.) Environment for development of new MM applications, application platform extensions and IMS mobility, QoS and security reasearch Contact: www.fokus.fraunhofer.de/ims
109

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

OPEN IMS Playground Overview

110

Page 55

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

FOKUS Components in the IMS Playground

FHoSS SIPSEE

OCS / OCS X

SER

OSC

SEMS

111

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

FOKUS developed IMS Components

IMS Core
Call Session Control Functions

SIP proxy with 3GPP features - SER

Home Subscriber Server

Diameter based AAA Server- FHoSS

Media Server

Media Streaming SEMS

IMS Application Layer

IMS compliant SIP Clients OSC Application Server

SIP Servlet AS SIPSEE Parlay X Gateway OCS-X Parlay Gateway OCS

112

Page 56

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

Integration of Partner Components @ FOKUS IMS PG

XDMS

Presence

Note: This is not a complete Partner List!

113

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

Reference Customers
Consulting on IMS development strategies for major vendors Consulting on bids and gap analysis of commercial products for key global integrator Extensions (Interfaces/Reference Points) of commercial solutions of various vendors Implementation of prototypes for vendors and operators Integration and Compliancy testing of commercial solutions Consulting on IMS integration strategies for major German Operator Interoperability testing for major European vendors IMS Load- /Perfomance testing for key global hardware vendor Application Service development for major German operator Consulting for establishing IMS Testbeds at remote sites Plus German and European R&D projects on Feature Interaction and Service composition
114

Page 57

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

Overview
IMS Motivation IMS Overview IMS Key protocols (IETF SIP and Diameter) IMS Key components IMS Application Server options Sample IMS Multimedia Applications The IMS Playground @ FOKUS Summary Q&A and IMS Playground Demos References & Acronyms

115

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

Service Layer technology maturity

Commercial deployments Market acceptance Mature technology Massive deployments

OSA/ Parlay
Growing commercial deployments Limited commercial deployments Limited trials and technology evaluation

IN

Web Services

IMS

Introduction

Growth

Maturity

Decline

116

Page 58

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

Legacy Services leveraged for Combi. Services

117

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

IMS Introduction Challenges

IMS Integration Challenges Core Network, SCE&SDP, OSS/BSS, Charging System

Applications SCE and SDP Infrastructure ? OSS / BSS ?

IMS
? Core Network Infrastructure

Charging System

118

Page 59

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

Single Vendor versus Multiple Vendor Strategie

Single Vendor Strategy Pros: Probably faster Integration Cons: Vendor lock, potentially limited innovation, no vendor is good in all aspects! Multi Vendor Strategy Pros: Choose best of bread vendors, competition (lower prices), more innovation Cons: More complex integration, Whom to blam in case of problems? Realistic Scenario IMS Core likely to come from one vendor assuring basic operation Applications layer based on multiple vendors servce innovation & flexibility
119

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

Wireline IMS Introduction

120

Page 60

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

Wireless IMS Introduction

121

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

IMS Deployment Contexts

Project capex

Platform for migration to nextgeneration network Platform for fixed-mobile convergence Platform for specific service(s)
Project timescale
122

Page 61

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

Ovums view of the 3 phases of IMS adoption

Caught between substantial long term pay-offs and short term business case requirements
1 20052007 2 20062009 3 2010+

The bandwagon rolls M arket state Em erging; first-m over advantage being sought

IM S becom es real Early; som e benefits are dem onstrated

Towards the 4G vision Stable; full IM S benefits becom e realisable

W hat?

Som e initial m obile deploym ents, but services lim ited in subscriber reach. Likely initial focus on business custom ers Lim ited handset availability. Initial technology supplier directions and partnerships are enterprise-focused. Sim plest IM S services are m ore of value to businesses.

Operator interworking and significant IM S-capable service deploym ents. Broader range of agreem ents spanning fixed and m obile Billing, custom er care and user inform ation issues start to be dealt with consistently. Solution m aturity brings m ainstream m arket online

Broad interconnection and availability of IM S services across all fixed and m obile networks for voice and data. VoIP over m obile brings all services into IP dom ain M obile VoIP QoS issues dealt with. Now two distinct horizontal propositions in both fixed and m obile: one based on services, the other on access

W hy?

Source: Ovum

123

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

IMS Deployment Worldwide

Source: visiongain

124

Page 62

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

NGN Service Platforms

Seamless Applications & Content (FMC) CORBA / C++ OSA / Parlay SOA Web Services Java JAIN Internet Web Servers

Service Enablers

Intelligent Networks / CAMEL

IP Multimedia System

VoIP SIP Servers AAA Servers

SDP

Session Control Bearer Cotrol (QoS) Mobile Access Networks (GSM, GPRS)

NGN

IP Core Network

Fixed Access Networks (PSTN/ISDN) NGN

Fixed and Mobile Internet Access

Cable / TV Networks

125

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

IMS to unglue the value chain

GSM value chain
Network Transport Value Added Services

Tight vertical integration of network and services Limited access for 3rd Parties (MVNO, Service Provider)

IMS value chain

Network Transport NG Service Network Provider
wholesale

Operators struggle to offer attractive service portfolio

Service/Application Provider
retail

Loose vertical integration of networks, services and applications Standardized interfaces allow easy integration of partners

Focus on core competencies and economies of scale Enriched service offerings for target communities

126

Page 63

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

SKYPE - Shows demand for Community Services

51 million registered users IMS functionality at a fraction of cost Client: PCs, WLAN/DECT/BT phones Cross Operator community On net calls free off net calls pay Standardized APIs. Lots of apps 30% of users are SMEs

However Skype is limited as Group and presence management is limited and integration with Click to Talk, Click to SMS, Location awareness, etc. is missing This is the operator opportunity!!!

127

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

From PTT to Community-Support

PoC/PTT basically defines a specific service based on generic enablers (Presence, GLMS/XDMS, FOTA) Infact PoC/PTT could be regarded as a specific instantiation of a group communication framework Making money with PoC/PTT is unclear Making money with SMS and voice calls is clear Idea:
Reuse PoC/PTT enablers for other communication services as well Integrated Presence driven IM, email, SMS, MMS, VoIP, CS-Calls, Video calls, etc. Provide group communication to those who really need it well established Communities (Sports, Work, health, fun) will appreciate this!
128

Page 64

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

IMS is a perfect basis for eCommunity services

IMS is today considered as the common platform for FMC and NGNs A convergent community-service can ideally be based on the IMS platform granting: convergence and compatibility between fixed/mobile networks multi-media and converged services support providing key community service enablers, such as Group Management Presence IM / PoC generic VoIP/MMoIP support, etc.
129

IMS IMS All-IP Network Cellular Networks Fixed Networks 3GPP Domain NGN Domain

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

Mapping of eCommunity Features to IMS Enablers

Support of various end user systems (PC from home, Notebook/Phone on the go) for seamless communications everywhere an any time Dynamic group management (open vs. closed groups) Presence information of community members Location information of community members and navigation support Click to communicate functionality (voice calls, video calls, SMS, MMS, email, IM, PoC, etc) Common multimedia archives and shared White Boards IMS is designed as an overlay to various access networks and also defines Gateways to legacy technologies (CS networks) XDMS enabler supports Group management Presence enaler supports presence Location information can be optained from dediacted Location servers (Le interface) or from HSS/SIP registrars SIP Servlet application server can provide Click to serivces via HTML service page or dedicated client application in end systems IMS Push to functionality e.g. via INFO method
130

Page 65

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

Mapping of eCommunity Features to IMS Enablers (cont.)

Automated appointment scheduling & logistical support Optional profile matching capabilities for bringing people together In the future: Virtual reality support Communities are third party driven! Support of third party services targeted towards specific communities Application server integration with corporate databases/outlook Application Server and optional HSS interrogation IMS supports any media (here interactive dynamic rendered video) and application server control (VR server) Usage of OSA/Parlay and later OMA OSE will enable controlled 3rd party services in IMS

131

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

Prototyping eCommunities within the FOKUS IMS Playground

Real Communities

COSIMS Development Toolkits

FOKUS IMS Playground

Together with T-Systems, HP and T-Labs eCommunity services are trialed with real life users

WLAN

UMTS

DSL

GSM/ ISDN

132

Page 66

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

FOKUS NGN R&D Reference Architecture

Development of necessary Services Client Software
IMS Management + AAA IMS Conformance Tests Scalability & Performance NGN Application Servers / APIs MM Content Delivery Single Sign On (HSS) Service Orchestration Model Driven Architecture (MDA)
Content & Services

Integration of different Access Networks QoS Provision & Security

IP Multimedia System (IMS)

Contribution To Standards

3GPP ETSI OMA IETF ITU-T

Different Access Networks (WLAN, UMTS, DSL)

NGN All IP Core Network

Interworking with Legacy Networks (GSM, ISDN, DVB)

Interworking with other networks

www.fokus.fraunhofer.de/IMS
133

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

Summary
IMS
is an overlay service network architecture applicable to any IP network (GPRS, UMTS, WLAN, DSL, ..) based on internet standards (IETF) is a global standard (supported by 3GPP, 3GPP2, ETSI, OMA, IETF) can be considered as THE universal Service Delivery Platform for NGNs supporting also Fixed Mobile Convergence (FMC)

IMS should be mainly considered as a service enabler (i.e. no real IMS services are standardised!) Push to Talk / PoC can be regarded as first IMS real life proof of concept But biggest service potential is in Community-based services FOKUS provides knowhow and a powerful infrastructure for testing IMS components and prototyping IMS / NGN services
134

Page 67

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

Overview
IMS Motivation IMS Overview IMS Key protocols (IETF SIP and Diameter) IMS Key components IMS Application Server options Sample IMS Multimedia Applications IMS Playground @ FOKUS Summary Q&A References & Acronyms

135

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

Any Questions?

136

Page 68

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

Overview
IMS Motivation IMS Overview IMS Key protocols (IETF SIP and Diameter) IMS Key components IMS Application Server options Sample IMS Multimedia Applications IMS Playground @ FOKUS Summary Q&A References & Acronyms

137

T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2006

Recommended IMS Books

138

Page 69