Next Generation Networks Service Oriented Architectures

Page 1

Understanding the IP Multimedia System (IMS) in Face of

First HUT – FOKUS IMS Workshop, Hanoi, Vietnam, June 2, 2008

Prof. Dr. Thomas Magedanz

g y ( )

Next Generation Networks, Service Oriented Architectures, and the Web 2.0

1

TU Berlin / Fraunhofer Institute FOKUS, Germany

Internet: www.fokus.fraunhofer.de/ngniEmail: [email protected]

Mobile: +49 171 172 70 70

Agenda1. Motivation for IMS as common control platform for converging networks

– Business drivers: PSTN Emulation, FMC, Tripe Play, IPTV, Web 2.0 Telco Integration– The new value chain of convergence: Netcos, Service Cos, SalesCos– IMS Basics: Control (Intelligent Networks) + Internet (SIP) = the better Internet = IMS

IMS Architecture and Standards review

T. Magedanz / N.Blum, Fraunhofer FOKUS, 2007

– IMS Architecture and Standards review– IMS vs. Service Delivery Platforms vs. Web 2.0

2. The need for open / independent IMS technology testbeds and toolkits– IMS Show stoppers - missing applications– Challenges of the telecommunications world– Lessons learned from the Internet

3. Fraunhofer FOKUS Overview– Fraunhofer Mission - high quality communications in face of convergence– The FOKUS R&D ecosystem - strategic cooperation is key

2

y g p y– FOKUS R&D topics– The FOKUS open technology playground concept

4. FOKUS expertise and components for testbed set up around the globe– Getting started with IMS - The Open Source IMS Core and the Open IMS Playground– Integration of IMS with Web 2.0 - The Open SOA Telco Playground– Integration of IMS with IPTV = interactive TV - The Media Interoperability Lab– Integration of IMS with eGovernment - Towards innovative services for Citizens– Q&A

Page 2


About the Speakers

Prof. Dr. Ing. habil 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)generation networks (Architektur der Vermittlungsknoten AV) supervising Master and PhD StudentsIn addition, he is director of the “NGNI” division at the Fraunhofer Institute FOKUS, which also provides the national NGN/IMS test and development centre in Germany. Prof. Magedanz is one of the founding members of FOKUS (1988) and member of the management team.Furthermore he is principal consulant of Direct Link Consult e. V., a FOKUS Consulting spin off focussing on professional services, strategic studies and technology coaching.Prof. Magedanz is a globally recognised technology expert, based on his 18 years of practical experiences gained by managing various research and development projects in the

3

managing various research and development projects in the various fields of today´´s convergence landscape (namely IT, telecoms, internet and entertainment).He acts often as invited tutorial speaker at major telecom conferences and workshops around the world.Prof. Magedanz 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. Since 2006 he is also extraordinary professor at the University of Pretoria and University of Cape Town in South Africa.

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

Contact

Prof. Dr.-Ing. habil Thomas Magedanz

TUB Chair Next Generation Networks / Director FOKUS NGN Division [email protected]

4

+49 171 172 70 70+49 30 3463 7229 Kaiserin Augusta-Allee 31

14513 Berlin, Germany

Page 3








5




Evolution towards Converged NetworksFixed

NetworksPSTN

ISDN

DSL

Information Technologies

ConvergedNGN

FMCGSM

MobileNetworks

AnalogueGPRS UMTS HSDPA

UMA

WiFi WiMax

Internet

FTP email WWWIMP2P

PortalsIPTVVoIP

SMS WAP

TriplePlay

Web 2.0

Quad

6

HomeNetworks

CableNetworks

ContentSharing

VoD

Broadcast

iTVPlay

Page 4


The Internet has changed the Telco World

• Network technology impacts Circuit switched evolution towards All-IP networks

• Service technology impacts• Service technology impacts SIP-centered service platforms (IMS), Web 2.0 / SOA

• Business Modeling impacts open services market, Subscription vs. Advertisment payments

• Communication services in the future will be strongly integrated with information services – traditional boundaries will blurrSt hift f t i ti t d

7

• Strong shift from person to person communications towards group communications Communities

• Combinational services centered around presence information and contexts of live I-centric Communications / human-centric communications

• The result is a Convergence of formerly different domains into one


Fixed Mobile Convergence

8

Page 5


Triple Play brings new Players in the Market

• Among traditional network operators (CATV / Telco) new players (i.e. equipment manufacturers and service providers) have joined the race for multimedia / triple play revenues.

• Purpose of value creation around basic communication services is mostly to maintain

9

competitiveness and profitability• Increasing competitive pressure

drives the transformation of the Telco industry.


Triple Play + Mobile = Quadruple Play

10

Page 6


Seamless Services – The Net doesn’t Matter• Network diversity and network innovation pace has lead to

network abstraction based on IP as common denominator• Connectivity Services versus Multimedia Services

GSMEDGEGSMEDGE

UMTSCDMAUMTSCDMA

CommonApplicationsand Services

• Users are interested in services – thus end systems and Service Platforms matter

11

IP – based NGNmobility-enabled

CDMACDMA

WirelinexDSL

WirelinexDSL

POTS/ISDN

POTS/ISDN

otherother

WLANWiMaxWLANWiMax

Network Diversity is not a problem anymore due toAll-IP evolution


Who owns the customer? Service Providers !!!

• IPTV and Quadruple Play can be provided on different broadband networks

• Physical networks become transparent due to y pdecreasing IP connectivity (i.e. flat rates)

Market entry barriers for service providers are vanishing

• Users are interested in content and services irrespective of the network access

The Value Chain splits horizontally

• The roles of the fixed mobile and cable operators is

12

• The roles of the fixed, mobile and cable operators is changing

Who will own the subscriber?

For what services users will pay in the future?

Is there a life for operators besides bit pipe provisioning?

Page 7


The Emerging Split of Operator Roles

So far Operators offered network specific services, but in the future they need to focus their business activities as- NetCos = Bitpipe Providers

ServiceCos = Platform Providers / Enablers / Brokers- ServiceCos = Platform Providers / Enablers / Brokers- Sales Cos = Customized Application Providers with direct Market Access

ISPFixed TV Mobile

Convergence ondevice level

Convergence ontariff level

Convergence on marketing level (Bundling, Cross-selling)

Customer Care/Billing

Devices

CRM/POS-Management

Sale

sCos

.

SalesCos.SalesCos.

SalesCos.SalesCos.

SalesCos. SalesCos.SalesCos.

SalesCos.

13

Convergence onnetwork level

DSL WLAN WiMAX Cellular

AccessNetworks

TransportNetworks

Basic Applications

Net

Cos

.

NetCos.NetCos.

NetCos.

Convergence onservice levelValue-added

Services

Content

Serv

Co.

ServCo.


ServiceCos: enabling Services over Bipipes

• Today: Service Offers are linked to network technologies and thus have a limited reach (compare with over the top providers, i.e. Google)

• Tomorrow Operators have to focus their business activities as eitherTomorrow Operators have to focus their business activities as either– NetCos: Bitpipe Business

• Efficient provision of Bitpipes• Enablement of several ServCos

– ServicCos: the „middleman“• Operate on top of many different NetCos

14

• Provision of service enablers to various SalesCos– SalesCos: facing the customer

• Make use of ServiceCo enabling services for high eficiency• Concentrates on Content and Customers

Page 8


Internet impact on Telecoms: Service DiversityDifferentiation and Efficiency is needed to surviveNGN Service platforms / IMS has the potential to link Internet / web 2.0 and telecommunications

Strategy of the broadening „T(elecoms)“: Broad top, sleek bottom

MNEBig nterprisesSMEsSmallRetiredFamiliesYouthKids

Differentiation!

ModularFast

Segment specific

Communities

Web 2.0Marketing and Sales

Services and Contents

Consumers Business Customers

Open Interfaces and APIs

S C

SalesCos. SalesCos.

SalesCos.SalesCos.

SalesCos. SalesCos.

15

Efficiency!

Telco2.0

Segment specific

One PlatformOperations optimized

Infrastructur(operations)partialy outsourcedNet

Effective ConnectivityControl

Service Control (IMS)ServCo.

NetCos.NetCos.

NetCos.


From Separate Networks To Converged Networks

TodaySingle-service networks

Services

FutureMulti-service network

Service EnablerServices

llula

r Mob

ileP

Net

wor

ks

PLM

N

TN/IS

DN

ellu

lar M

obile

CAT

V

Content Service Network

S

S SS

Content

API

Se ce ab e

16Access, Transport & Switching Networks

Cel

Dat

a/IPP

PST Ce

Connectivity/Connectivity/Backbone NetworkBackbone Network

Access NetworksMGWMGWMGWMGW

MGWMGW MGWMGW

Page 9


Convergence requires ONE Service Platform

• Technically convergence means to unite the currently still seperated fixed and mobile network operator domains into a single one

• Ths convergence is not about a NEW MARKET, but just theThs convergence is not about a NEW MARKET, but just the combination / migration of several previously existing markets into one common (and probably one smaller market)!

• Anyhow, convergence is a chance (or a war) for operators to expand their coverage

• Technical prerequisite is a common service delivery platform on top of fixed, mobile and IP-based networks

17

• The IP Multimedia System (IMS) is defined for that• Started in 3GPP and 3GPP2 for the mobile domain, IMS today is also

considered by ETSI, ITU-T, ATIS for the future (IP-based) fixed network as well (under the banner of NGN)

• Thus IMS represents the common denominator service platform


Evolution of Service Delivery Platforms

Web/ApplicationServer

ApplicationMultimediaServices

3rd PartyApplication

Services

Web 2.0SOA

AAAServer

IN / CAMEL Services

Server

OSA / Parlay Interface

INAP/CAP

OSA/Parlay/JAIN Gateway

IN Platform

Parlay X

SIP App.Server

Services

SIP

(Enterprises / Content)

SIP Server

NGN / IMS

18

INAP/CAPInterface

StoredProgram Control

ServicesPSTNGSMGPRS/UMTSVoIP= Services

DiameterSe e

Page 10


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 IP based applications !!

• Horizontal Architecture defining a “docking station” for applications

• Defines service enabler capabilities• Build on existing IETF and telco SDP

ArchitectureArchitecture

Presence

Apps

GLMS

• IMS enables the flexibility in providing IP-based applications !!

IMS

MM Applications

19

gstandards

• Provides compared to standard internet

• Better security, Service based QoS, flexible charging and single sign on

GGSNSGSNRAN

HSS IMS

IP (!) Networks

IMSand

Service Enablers


Stand alone vs. IMS Approach

20

Page 11


IMS Service Differentiation / QoS preposition

21


IMS Charging value preposition

€ 1 per MByteMobileInstant MessagingChat Sessions

Pricing based on transport

IMS

GGSN€ 1 per MByteMobile

OperatorChat SessionsVoice CommunicationVideo Communication

€ 0,02 per Instant Message

Pricing based on services

22

GGSNMobile Operator

€ 0,10 per Minute for 128 kbit/s Video

€ 2 per Month for Presence

IMS charging provides operators to be more than “bit pipe” provider

Page 12


Complete IMS Security

IMS HomeAuthentication & Key Agreement (AKA)ur

ity

SIP UAISIM

IMS Visited(P-CSCF)

(S-CSCF / HSS)

Security Mechanism Agreement

Network Domain Security

IMS

Secu

SecureApps

SecureApps

23

GPRS DomainExisting GPRS Access Security

Integrity Protection

pp

Non-secureApps


Internet Control vs. Telecommunications Control

ElectiveServer

ElectiveServer User has control of all

applications and choice f

All services enabled by protocols: From ftp to web

No single point of failure

ITU Intelligent Network Control: POTS, ISDN, BISDN, FR, ATM, H.323, MEGACO/H.248, GSM

Services supported by interfaces and central

USER USERInternet

“Dumb Network”

R

R

Rof serversprotocols: From ftp to web

R

24

CentralControl

USER USER

CentralControl

CentralControl

SW SW SWSW SW SW

UNI NNI NNI UNI

controllersUser has little control

Page 13


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 Applicationp pservice 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”

SessionServers

ppServer

25

• 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.

Media ServersRouters


IMS Core Infrastructure Functionality


• Implementing generic functionality in the infrastructure is most economical !!

SIP Session-/Service Control


Presence

PoC

GLMS

HSS IMS

IMSand

Enabling Services

Applications

Messaging support

Single-Sign-On User-Authentication

Subscription Handling

QoS/Media Authorization

Signaling Compression

Charging Support and Correlation

Routing/Addressing Support

26

GGSNSGSNRAN Network

g Routing/Addressing Support

Regulatory Service Support (e.g. LI)

Conferencing Support

PSTN Interworking Support

Docking Station for Service Enablers

Docking Station for Applications

Page 14


IMS Motivation – Flexible Service ProvisionProvision of service enablers and dynamic service portfolio extension- Presence and Group server are considered key for the future- Application Servers can be control and/or content serverspp

IP MultimediaSystem (IMS)Signalling (SIP)

Transport (RTP)

Call / Session ServerPresence ServerMessaging ServerAny new Application

ServersContent Server

27

Packet Network (Core)Transport (RTP)

Access Networks(WLAN, UMTS, DSL)



3GPP IMS Architecture: IMS Core and Applications

HSS(AAA)

ApplicationServer IMS enabler

Group Mgt

IMS Service Framework

IMS enablerPresence

S-CSCFP-CSCF S-CSCFI-CSCF

MediaG t

Group Mgt

PDF

IMS Core

MediaServer

MFRC + MFRP

28

GatewaySGW, MGCF, MGF


Interworking withLegacy Networks(GSM, ISDN, DVB)Underlying IP Core Network

IMS Core System

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

Page 15


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 C– 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 Polícies (COPS)

29

– 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


IMS Enablers = Reusable IMS Application Servers

• IMS did not address the standardisation of specific application by purpose• Only major AS interfaces are defined = IMS is a „docking station“ for ASs!• Open Mobile Alliance (OMA) is supposed to do service specificOpen Mobile Alliance (OMA) is supposed to do service specific

standardistaion on top of IMS• Examples include Presence, Group Management, Instant Messaging (IM),

Push to Talk over Cellular (PoC), etc.• Over time it become clear that there is a set of common servers, i.e. enabling

servers IMS Enablers, which can be used in the implementation of more complex IMS services

• Major enablers today to be used in IM, PoC and Group Video Calls, etc.:

30

Major enablers today to be used in IM, PoC and Group Video Calls, etc.:– XML Document Management System (XDMS) enabler for group configuration– Presence Server (PS) enabler for maintaining presence information– Device Management (DM) enabler is used for client system configuration,as ASs

and enablers may need specific software on the client system!

Page 16


IMS integrates different Communication Services

Pre-IMS Communication(“Service Islands”)

IMS Communication(“Combinational Services”)

Voice

SMS

Instant Messaging

MMS

Voice / VideoSMS

Instant Messaging

MMSPoC

TV

31

From the usage of specificindividual communication services ... ... to the integrated usage of different

communication services centered around presence information and

within groups ( communities)


Overall NGN Architecture (ITU-T)

ConvergedNGN

(all-IP)

32

Page 17


NGN – An extensible Control Platform for IPP/ISDN

EmulationVOIP, Videoconf., IM, FMC, Presence

IPTV Web 2.0

What about

ConvergedNGN

(all-IP)

P/ISDN EmulationSubsystem

IP MultimediaSubsystem

Streaming/IPTVSubystem

other IP Applications

VoIP/Skype

Reusable TransportBest effort

33

pSupport Systems Internet

PSTN


NGN – An extensible Control Platform for IPP/ISDN


IPTV Web 2.0

What about

ConvergedNGN

(all-IP)




Reusable Transport

IMS supports all


VoIP/Skype

Best effort

?

34

pSupport Systems

Internet

PSTN

Page 18


NGN Global Standards Cooperation

Open Mobile AllianceOpen Mobile AllianceDefining IMS services, e.g. Instant Messaging, Push-to-TalkNot strictly mobile oriented, driving wireline services also

The Parlay Group / Java Community ProcessThe Parlay Group / Java Community ProcessIntegral to IMS architecture, define standard API frameworks

TISPA

N

TISPA

N ––

Ag

ree

me

nt

Allia

nce

Allia

nce

Ne

ar

CJK

Ch

inC

JK C

hin

Sta

rting

Foc

ITUITU

--T NG

T NG

Lev

era

gin

g

33rd Generation Partnership Projectrd Generation Partnership Project33rd Generation Partnership Projectrd Generation Partnership Project22Define IMS network elements and infrastructure

g ,

American National Standards InstituteAmerican National Standards InstituteT1.679 covers interworking between ANSI ISUP and SIP

International Telecommunication UnionInternational Telecommunication UnionQ.1912.SIP covers interworking between ITU-T ISUP and SIPH.248 for media control

––ETS

I bo

dy o

n N

ext G

en

eETS

I bo

dy o

n N

ext G

en

eo

n re

use

of 3

GP

P/3

GP

P2

IMS

in co

e fo

r Tele

com

mu

nica

tion

e fo

r Tele

com

mu

nica

tion

ring

ag

ree

me

nt to

use

3G

PP

/3G

PP

na Ja

pan

Ko

rea

na Ja

pan

Ko

rea

cus G

rou

p o

n N

GN

GN

Focu

s Gro

up

GN

Focu

s Gro

up

IMS

in w

irelin

e

35

Internet Engineering Task ForceInternet Engineering Task ForceDefines SIP, SDP and other protocols underlying IMSIMS is driving some of the work in IETF

Define IMS network elements and infrastructure for mobile environments

era

tion

Netw

ork

era

tion

Netw

ork

om

pre

he

nsiv

e N

GN

pla

ns

ns In

du

stry S

olu

tion

sn

s Ind

ustry

So

lutio

ns

P2

IMS

Cablelabs / PacketCableCablelabs / PacketCableDefine IMS network elements andinfrastructure for IPTV and Triple Play


Overall TISPAN NGN Architecture

Based on3GPP IMS

IP ConnectivityAccess Network

Applications

Data OOther Multimedia C t

Resource and Admission Control FunctionalityRACS

Access NetworkAnd related functionality

Network AttachmentFunctionalityNASS

LegacyTerminals

Base

Other N

etworks“Gq”

interface

“Go”

PS

TN / IS

ICF

GW

GW

LegacyTerminals

L

Components …

PSTN / ISDN Emulation(SIP-I based)

IP Multimedia Component (Core IMS)(SIP based)

IPTV Streaming Subsystem

36

Core transport Network

3GPP IP-CAN

Access Transport Network

IP

3GPP Terminals

NGN Terminals

CustomerNetworks

“Go”interface

SD

N

MBG

TGWGW

NGN Terminals

LegacyTerminals

HGW

Page 19


NGN Application Layer – IMS as docking stationSOA-based Seamless Multimedia Communication & Content Applications

Web 2.0 APIsMesh ups

OMAOSE

CORBA / C++ / JavaOSA / Parlay / JAIN

Web ServicesParlay X

Web 2.0

IP Core NetworkBearer Control with QoS

Service Enablers

Session Control

IntelligentNetworks/ CAMEL

Plain VoIPSIP ServersAAA Servers

p

Unified NGNsession control

system

NGN

SDP

37

Mobile Access Networks

(GSM, GPRS)

Fixed Access Networks

(PSTN/ISDN)

Cable / TV Networks

Fixed and Mobile Internet Access

IP Core NetworkBearer Control with QoS

NGN

NGNStreaming SS


SOA, Telecommunications and Web 2.0

• Service Oriented Architecture (SOA) approach for the integration of– NGN architecture (IMS-based core network)– Application Enablers (OMA Service Environment)– Application Enablers (OMA Service Environment)– 3rd party interfaces (Parlay X)– Web 2.0 Applications

SOASOA

Web 2.0Web 2.0

OSEOSEParlay XParlay X

38

SOASOA OSEOSE

IMSIMS

Parlay XParlay X

Page 20


A Service Delivery Platform enables Seamless Services

DB

App1App1App1VASP

LBSContentDelivery

MRF Service Execution Environment

App1 App2 App3 ExposureOSA

Parlay /XOMA

SDPSDP

Abstraction Layer

Internetwwwwww

GoogleGoogle

blogsblogs

PortalsPortals

SkypeSkype

GamingGaming

33rdrd Party ASPParty ASPlling

CR

M

ExposureLayer

Service Execution Environment

Service CreationEnablers(incl. Content

Delivery)SOA

Public networkPublic network Private networkPrivate network

IPIP--BackboneBackbone

DB

Control Layer(MSC-Server, CSCF, AAA,..)

HLRHSSSMSC

USSD GwIVR

MMSC

OTADelivery

MediaGW

MRFPresence

Abstraction Layer ypypicqicq

Pro

visi

onin

gB

itio

n &

Mai

nten

ance Connectivity Layer

Control LayerAbstraction Layer

IMS fits here

39

GSM

GPRSEDGE

UMTSIMS

CDMA

WiFi

SatellitSatellite

Mobile AccessMobile Access Fix Access Fix Access

PSTNCable

xDSL

DECT

WiFi

Mobile AccessMobile Access Fix Access Fix Access

LAN

PBXSup

ervi

sion

Ope

rat

Access Network Layer

The Role of SOA in Telecommunications

• Unifying Architecture– Strategic enterprise alignment– Cost reduction, agile delivery, innovation

• Service Delivery for IMS– IMS provides the session control infrastructure and network enables– In addition it needs the service delivery, service assembly – it needs applications.

• IMS is being deployed incrementally – the reality is a mix of 2G/PSTN service control and IMS parts

– The challenge for operators is to use their suite of intelligent service infrastructure.– SOA provides a solution to integrate the old with the new and compose applications across the

infrastructure

40

infrastructure.

• Open platforms changes the delivery model for applications– Applications traditionally were provided by NEPs with limited internal development– SOA enables applications to be used along side operator driven developments.

• OSS/BSS needs to be part of the application development– SOA promotes the inclusion of billing, provisioning and services management as an integral

part of the application development

Page 21


Evolution of SOA Concepts in Telecoms

OMAPolicy Evaluation &

Enforcement Mgt

Service Brokering(SCIM)

Open APIs OSA/Parlay/JAIN IP Multimedia

S t (IMS)

TelecomWeb Service APIs

Parlay X

Enforcement Mgt ( )

Web 2.0

41

InternetProtocols

IntelligentNetwork (IN)

System (IMS)

ServletsCAMEL(IN in Mobile)


Telco 2.0 – with IMS ?Web 2.0f

Telcoms vs. Internet - IMS and Web 2.0 ?The Internet / Web 2.0 will recieve increasingly acceptance. Telcos have to learn.

User generated contendPeer to peer trafficExtreme market segmentation

Social networksCommunities„Long Tail“

Speed:Instant

Provisioning

Telcos have to learn from internetDifferentiation based on customer expectationsFast innovation at service level3rd Party Enabling, Service Brokerage

Efficient and low cost „Production“Additional Differentiation by:

Always best connectedSingle User Identity (Identity Broker)Si l i

1Creator

10 Synthesizer

42

gFast innovations

Single sign onReal Presence Information Billing, cash collection, clearing

100 Consumer

Many more services, but much less revenues per servicesMore customers, but less ARPU

Plus: inreasing M2M communicationsGrid Computing“Communicating Cars”…

Page 22

Import and Export of „Services Enablers“T. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2007

Web 2.0 World Players and Services(Google Maps, YouTube, RSS Feeds, etc.)

Importof

Web APIsExportof Telco Enablers

• Re-use what is publicly available• Create recognised user interfaces

• Resell available capabilities• Enable value added services

43

Telco 2.0 Enablers(Calls, Messaging, QoS, Charging, Identity Mgt., Security)

Service Brokering

Network Abstraction

Web-based Telco Enabler Exposure Examples

• British Telecom´s 21c Web SDK based on extended Parlay X Web Services based interfaces (http://web21c.bt.com/)– New possibility of defining user-specific call flows in XML for


New possibility of defining user specific call flows in XML for enabler orchestration

– Authentication, conference call, inbound SMS, messaging, voice call

• Orange Partner API based on Web Services (French market only) and XML-RPC (http://www.orangepartner.com)

44

( p g p )– Authentication, Personal Calendar, Personal Contacts, Personal

Messages, Personal Photos, Personal Profile– SMS, Email, – Web-based widgets (bubbletop dev platform)

Page 23

Web-based Telco Enabler Exposure Examples 2

• T-Online Open Developer Forum based on Web Services and XML-RPC (http://developer.telekom.de) – official start in Q3/4 2008– Voice Call, send SMS


Voice Call, send SMS

• Sipgate API based on XML-RPC (http://www.sipgate.de/user/download_api.php) – German VoIP ISP– Voice call, send SMS, send Fax– Billing data, call lists

45

SOA Service BrokerT. Magedanz (TU Berlin / Fraunhofer FOKUS) - 2005

Workflow based Telco / Web 2.0 service compositon and simulataneousintegration of composed services into the B/OSS infrastructure with the aim of

– reduction of time to market through automation of the service lifecycle:• service creation / composition• service deployment• service activation• service fulfillment• service assurance• service billing

– reduction of opex through:

46

reduction of opex through:• autonomic mechanisms• closed control loops• Policy based Management

Page 24

Putting IMS in the SOA/SDP contextSebastian Wahle – Fraunhofer FOKUS – 2008

47


How should Operators use IMS and NGN ? The Question of how to survive: Efficiency vs. Innovation

PSTN Reloaded vs. Programmable Secure Multimedia InternetTraditional PSTN “PSTN l d d”

Carrier controls complete PSTN

One dominant business model

Carrier definesbusiness model

Traditional PSTN business model

Proprietary(IMS) Control

CarrierIntranet/VPN

Closed SDP +DeviceArchitecture

Carrier controls value chainNGN with „IMS“ inside –monolithic outsideInstable balance, high sensitivity against disruptions and business model shifts

“PSTN reloaded”closed productexperience

hiddencapabilities

48

Call Handling Signaling & IN

TDM-Transport

Value AddedServices

Open IMS(Control)

Internet

Open SDP +DeviceArchitecture

Competition on content & service areas, new entrants

Exploitation of innovation

Robust eco system, basedupon partnering

“Programmable Internet”open productexperience

exposure ofcapabilities

Page 25


Any Questions?Any Questions?

49








50



Page 26


IMS - One Language but different Dialects

51

The scope of 3GPP should be extended to include the requirements coming from other communities.A mechanism should be put in place to ensure efficient requirements capture. 3GPP should be responsible for producing one set of IMS specifications that satisfies these requirements. It is expected that these new arrangements will be put in place during 2007.


IMS Adoption Inhibitors

52

Page 27


IMS Show Stopper No.1 Today – The IMS Client

53


Show Stopper No.2: IMS Development Kits

54

Page 28


IMS Introduction Challenges

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

System

ChargingSystem

OSS /BSS ?

Applications SCE and SDPInfrastructure

?

? IMS

55

SystemBSS

Core Network Infrastructure

?


Problem: IMS fells onto segmented Organisations

56

Page 29


How competes IMS with the Web2.0P/ISDN


IPTV Web 2.0

What about

ConvergedNGN

(all-IP)




Reusable Transport

IMS supports all


VoIP/Skype

Best effort

Interne

?

57

pSupport Systems

Internet

PSTN


IMS vs NON-IMS Applications

58

Page 30


Web 2.0 = Communities and new User Experience

59

Porter´s Five Major Market Forces

60

Michael E. Porter: "How competitive forces shape strategy”, Harvard Business Review, Vol. 57, Issue 2, pp.137-145, March-April 1979

Page 31

M. Porter´s Five Forces within the Telco Market

Threat of New Entrants:

Bargaining Power of Suppliers:

Consolidation in the vendor market -Consolidation in the operator market -Vendor lock vanishes -

Absolute barriers:low investment costs of ISPs -

Exclusionary barriers:deregulation -

Strategic barriers: large customer base +high potential of incumbents to build strategic barriers +

61


Open Source in Telecommunications

• Lessons learned from the Internet: Open Source software is good andbrings innovation as the developer base is huge compared to closedsoftware developments– Examples: Linux, Tomcat, Eclipse, MySQL …

• In face of decreasing ARPUs and increasing customer demands open source software becomes attractive in the telecommunications field aswell

• VoIP and open standards are an excellent starting point:– for PBXes (FOKUS SIP Express Router (www.sip-router.org),

62

( p ( p g)Asterisk (www.asterisk.org), SIPX (www.sipfoundry.org/sipX))

– SIP Servlets (JSR 116)– JAIN SLEE platform (Mobicent project)

Page 32


While the VoIP lists many Open Source Projects …

– General directories• PJSIP.org (www.pjsip.org/links.htm)

SIPf d ( i f d )• SIPfoundry (www.sipfoundry.org)– SIP Proxies (SER, OpenSER, sipX …)– SIP user agents

• Windows (SIP Communicator, …)• Linux (Kphone, Linphone, Ekiga …)• MacOS X (FreeSWITCH …)

63

( )– Test tools (SIPp, SIPbomber …)

• …there are NO IMS specific Open Source projects so far


SER – Facts and Usage– Each CSCF implemented as a SER module– SER = SIP Express Router

• a high-performance, carrier-grade, open source, configurable SIP server written in Cserver written in C

• ported to Linux (PC, iPaq) and Solaris (Sun)• throughput thousands of CPS (calls per second) on a dual-CPU PC

(capacity needed to cover San Francisco’s Bay Area) and hundreds of CPS on Compaq iPaq

• support for both IPv4 and IPv6• small footprint size: 300k core, all common modules around 600k• extended flexibility through script-like configuration

64

if (method==“INVITE” || method==“SUBSCRIBE” || method==“MESSAGE”) {

if (!P_is_registered(“open-ims.org”)){

sl_send_reply(“403”,”Forbidden – You must register first”);

break;

}

P_add_P_Charging_Vector();

P_add_P_Visited_Network_ID(“Visited Network Number 1”);

}

• Usage example:– Excerpt from the

Proxy-CSCF configuration file

– steps are applied in order in the routing script:

Page 33


Beyond SER – What is needed for IMS

• The SIP sessions in IMS need various 3GPP specific extensionscompared to todays VoIP infrastructure– P-Charging headers (e.g for charging, asserting identities, …)P Charging headers (e.g for charging, asserting identities, …)– subscription to registration events in other SIP routers

• set-up of IPsec secured up and downstream channels based on authentication keying material

• Ability to communicate with a centralized user repository via theDiameter protocol– tight integration of a Diameter stack

65

– tight integration of a Diameter stack– perform DB look-up

• Ability to dynamically apply filter rules for SIP traffic on a per-userbasis– Application of initial Filter criteria in the Serving Call Session

Control Function


Beyond SER - The FOKUS OPEN SOURCE IMS Core

• A version of the Open IMS Core (OSIMS) is currently being developed and was already successfully tested with commercial IMS products.

– provides first time implementations of core IMS components• Call Session Control Functions• Home Subscriber Server

– offers an Open Source IMS platform to make use of the ISC interface

66

– can act as a tool for IMS services proof-of-concept – allows to test alpha/beta versions of commercial IMS products– does not intend to compete with carrier grade developments but wants to create an

Open IMS community and to accelerates IMS adoption– This software is for establishing IMS testbeds only, not for implementing

commercial IMS systems!– Note: Users have to check potential IMS patents and standards licenses!

Page 34


FOKUS OSIMS Download …

• > 40.000 visits• > 13.000 unique

visitorsvisitors• Approx. 150

visitors/day• Region breakdown

AsiaAmericas

67

Europe

Americas


The Role of Open Testbeds

• Network convergence and the new multimedia servce world is a subject of huge complexity

• Required infrastrucutre is expensive• The IP Multimedia System (IMS) becomes of fundamental importance for• The IP Multimedia System (IMS) becomes of fundamental importance for

unifying the seamless multimedia applications delivery above several network types

• Operator specific or vendor specific testbeds are not sufficient for addressing this complex market, as they are limited in technology exploitation and business models and likely will not address the needs of end users adequately ( technology push model)

• Learning from the internet, a huge number of application developers acting on an open infrastructure (the internet) is needed to enable succesful market driven services ( technology pull model)

68

( gy p )• Thus open testbeds are key for exposing the network variety and complex

service platforms to an open set of developers and to provide a • Adequate software toolkits are of help to start working without a testbed first• The testbed infrastructure provides the technological basis for early platform

component testing and applications prototyping and thus interoperable solutions and vendor independence

Page 35


Getting started with IMS – An IMS Testbed

• Operators and vendors are challenged strongly by the ongoing convergence (VoIP, FMC, Triple Play, Internet multimedia / web 2.0)

• IMS is a complicated subject due to convergence domainsIMS is a complicated subject due to convergence domains• Success of IMS will depend strongly on open / interoperably solutions

and many niche market services• Instead of deciding for one or two vendors and/or integrators the

establishment of a local IMS/NGN testbed enables all players to gain early insight into the IMS

• Currently many international testbeds are under development

69

y y p• Testbeds and related tools allow to engage all players of the emerging

convergence ecosystem at an early stage to develop many and really demanded services

• Universities could be part of this approach to educate staff as soon as possible


Distributing the IMS Playground

• Since ist opening in 2004, there has been huge interest in the IMS Playground concept

• Many operators, integrators, and vendors around the world have usedMany operators, integrators, and vendors around the world have used the IMS playground facilities (infrastructure and staff expertise)

• As this demand is increasing, FOKUS has decided to distribute the Open Source IMS core system for free, allowing operators, integrators, vendors as well as research organisations and universities to setup their own IMS testbed

• Open Source Core can be enhanced by local partner components and d l t

70

own developments• Optionally, FOKUS add on components and professional services

allow for fast testbed set up

Page 36

FOKUS Open IMS Playground Concept

Platform

Free Download1

Universities& R&D C t

Sebastian Wahle – Fraunhofer FOKUS – 2008

+ Industry IMSComponents

FOKUS IMSComponents

NGN OpenTestbedsNGN Open

TestbedsNGN OpenTestbeds

Cooperation

2Operators& Vendors

& R&D Centers

71

IndustryTestbedsIndustry

TestbedsIndustryTestbeds

IMS Testbed

Local Operator–specific Testbeds at FOKUS

IMS TestbedIMS Testbed

IMS Testbed

Remote Testbeds


Towards your own IMS Testbed – we can help!

• Train the relevant staff on general IMS concepts and technologies– 2-3 day onsite tutorial for all people

• Install Open Source IMS Core SystemInstall Open Source IMS Core System – Train the related technical staff onsite and optionally at FOKUS– Obtain remote support for 12 month and more

• Optionally extend the IMS Core by additional components (IMS Client, Application Server, demo applications, add on modules, etc.)

• Optionally interconnect the IMS testbed with the FOKUS IMS playground to get access to the most recent demos and vendor

t

72

components• Optionally setup remote testbeds at relevant local Universities to start

innovation from there• Optionally obtain customisation of components from FOKUS• Develop own extensions and components locally• Develop a common roadmap of developments with FOKUS

Page 37








73



Documents

Next Generation Networks Service Oriented Architectures