Niklas Blum

1
ICT OSA / Parlay Workshop Campinas/Sao Paulo,
Brazil, March 22nd, 2006

• The Importance of OSA/Parlay in the Service
  Network Evolution

• Niklas Blum
• TU Berlin / Fraunhofer FOKUS
• blum_at_fokus.fraunhofer.de
• www.fokus.fraunhofer.de/ims

2
Overview

• How to stimulate applications development?
• Service Delivery Platforms and Service Enabler
• IMS Application Server Options (combining SIP AS
  and Parlay)
• Case Study IMS-based 3rd Party Community
  services
• IMS component testing and IMS service validation
  within the IMS Playground _at_ FOKUS
• Summary

3
IMS as NGN SDP Motivation

• IP network connectivity is given (GPRS/UMTS,
  WLAN, WiMax, DSL, ...)
• Main IMS idea Use IP network for both
• Circuit-switched-like, synchronous, QoS enabled
  multimedia services
• Packet data multimedia services (like in the
  internet)
• Standards scope Provide a minimum set of
  interfaces (common denominator) for
  interoperability (PlugPlay of applications)
• Reuse as much as possible standard IP protocols
  for session control, management and bearer
  transport (SIP, AAA, RTP)
• BUT What is the difference to the internet /
  VoIP?
• ? IMS should provide a controlled, secure
  internet service environment with QoS and
  charging capabilities
• Take into account existing mobility
  infrastructure and mobile services to provide an
  evolution story ? Combinational services
• Today IMS is extended to cope with fixed access
  networks as well
• ? IMS as common SDP for Fixed Mobile Convergence!

4
The Drama of todays Service Space

• There is broad spectrum of technologies one has
  to understand in the context of Fixed Mobile
  Convergence and Next Generation Networks
  (telecoms, internet, IT)
• The converged network value chain is getting
  complex (network, portal, content, etc.)
• Big players try to cover all major layers
  resulting in non-optimum offers which are not
  appreciated
• Innovation in the telecoms field is driven by
  technology push
• Access to the new technologies is quite
  complicated for small players and most particular
  for application providers
• This is too expensive and often technology is
  promoted to early with raising wrong expectations
  resulting in frustration
• A technology pull model in which technology
  introduction will be driven by concrete demand
  and specific applications
• This means the applications developers need early
  access to the technologies ? Open testbeds are
  needed

5
Network Generation Network Vision

• Mobility and QoS enabled IP core
• Simplified service provisioning independent of
  access

Common Applications and Services
GSM EDGE
UMTS CDMA
IP Network mobility-enabled
WLAN WiMax
Access System
POTS/ ISDN
Wireline xDSL
other
6
Overview

• How to stimulate applications development?
• Service Delivery Platforms and Service Enabler
• IMS Application Server Options (combining SIP AS
  and Parlay)
• Case Study IMS-based 3rd Party Community
  services
• IMS component testing and IMS service validation
  within the IMS Playground _at_ FOKUS
• Summary

7
IMS as NGN SDP Motivation

• IP network connectivity is given (GPRS, UMTS,
  WLAN, DSL, etc.)
• Use IP network for CS-like, synchronous, QoS
  enabled MM services
• Enable an open set of innovative services (like
  in the internet)
• Provide a controlled, secure service environment
  with QoS and charging capabilities
• Provide a minimum set of interfaces (common
  denominator) for interoperability
• Reuse as much as possible standard IP protocols
  for session control, management and bearer
  transport (SIP, AAA, RTP)
• Extend these protocols to achieve security and
  managebility
• Take into account existing mobility services and
  infrastructure

8
Communications Landscape Is Changing
The IT Community Rich in Applications and
Creativity
Technical Convergence
The Telecom Community Rich in Networks and
Connectivity
OSA, Parlay and JAIN are examples of emerging
Technology Standards that facilitate the
convergence of the IT and Telecom communities
9
3GPP IP Multimedia Subsystem (IMS)

• The IMS has been originally defined by the 3rd
  Generation Partnership Project (3GPP) as part of
  UMTS Release 5 / IMT2000
• Extensions have been made in release 6 to adapt
  to real world (e.g. IPv4)
• 3GPP2 has adopted the IMS architecture on top of
  Multimedia Domain (MMD)
• ETSI TISPAN is defining Next Generation Network
  SDP for all IP Networks based on IMS
• Open Mobile Alliance (OMA) defines IMS Enablers
  Services
• The IMS represents an overlay network on top of
  GPRS networks and provides an all IP service
  delivery environment for mobile multmedia service
  provision (VoIP, Videotelephony, MM Conferencing,
  Mobile Content, 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.

10
IMS Layers Transport, Session Control, Apps
Application Plane
SIP AS
SIP AS
Control Plane
HSS
S-CSCF
SIP
I-CSCF
P-CSCF
RTP
Diameter
MRFC
MEGACO
User Plane
MRFP
B-GW
PSTN
11
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
• MRF (Media Resource Function) Media Server
  hosting special resources
• MGCF (Media Gateway Control Function) for
  Interworking with legacy networks
• PDF (Policy Decision Function) for QoS Control
  using Polícies (COPS)
• IMS Application Layer
• HSS (Home Subscriber System) for maintaining
  subscriber and AS profiles
• AS (Application Server Function) for hosting
  applications
• The main new protocols used are (IETFs) SIP and
  DIAMETER (MAP and CAP are also important).

12
Overview

• How to stimulate applications development?
• Service Delivery Platforms and Service Enabler
• IMS Application Server Options (combining SIP AS
  and Parlay)
• Case Study IMS-based 3rd Party Community
  services
• IMS component testing and IMS service validation
  within the IMS Playground _at_ FOKUS
• Summary

13
IMS Application Server Options
Todays focus
Application Plane
OSA/Parlay AS
CAMEL
API
Parlay API
CAP
SIP AS
OSA GW
IM-SSF
Control Plane
HSS
SIP
RTP
S-CSCF
Local AS
I-CSCF
P-CSCF
Diameter
User Plane
MRF
B-GW
PSTN
14
OSA / Parlay AS (3rd Parties)
Parlay X App 1
Service Delivery Platform (Application Server)
Parlay X App 2
Parlay App 1
Parlay App 2
Parlay App 3
Parlay X GW
HSS
Service
Platform Trigger Points
Parlay API (MPCC, MMM, Pres, Charg, ...
Sh Diameter
Other access networks
SIP Interface
Diameter
Cx Diameter
Ro Rf Diameter
ISC
Online Offline Charging (ECF, CCF)
S-CSCF
SIP-Server
S
S
Filter criteria
SIP
P
P
T
15
NGN/IMS Applications
16
Overview

• How to stimulate applications development?
• Service Delivery Platforms and Service Enabler
• IMS Application Server Options (combining SIP AS
  and Parlay)
• Case Study IMS-based 3rd Party Community
  services
• IMS component testing and IMS service validation
  within the IMS Playground _at_ FOKUS
• Summary

17
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, ATT
  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

18
The full OMA Picture

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

19
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!

20
From PTT to Community-Support

• But how to link these enablers with the legacy
  services
• IMS is defined for all-IP!
• Solution 1 implement PTT on top of OSA/Parlay
  APIs
• Provides reuse of enablers for different network
  services
• Solution 2 Provide third party interfaces with
  OSA/Parlay APIs (i.e. Parlay X) to the existing
  communities

21
Community Services across different Networks
Community Service Providers
JAIN SLEE
SIP AS
WS Clients
OSA AS
Community Framework
Community Feature
RA
Community Feature
Community Feature
ISC
OSA/Parlay
Parlay X
Community Client
GUI
HTTP
Policy Enforcement (OMA OSE)
XCAP
Service Enabler

SIP
Presence
GLMS
Messaging
Identity Management
Framework UDDI
Media Server
RTP
IMS Core P/I/S-CSCF,MS,MG
HSS
IN Platforms
WLAN
DSL
GSM
ISDN
UMTS
22
Community Example Push-to-Share
ParlayX Interfaces
23
Overview

• How to stimulate IMS applications development?
• IMS as SDP and Service Enabler
• IMS Application Server Options (combining SIP AS
  and Parlay)
• Case Study IMS-based 3rd Party Community
  services
• IMS component testing and IMS service validation
  within the IMS Playground _at_ FOKUS
• Summary

24
Fraunhofer FOKUS Facts

• FOKUS has been founded 1988 in Berlin, Germany
• 220 employees scientists, students, technicians
  originating from 30 nations
• FOKUS is THE Telecoms RD institute within the
  Fraunhofer Society
• Fraunhofer Society is the biggest German RD
  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 RD
  projects
• Key to success Strategic Partnerships with big
  players (DTAG, NTT, etc)
• Main RD Vision I-centric communications and
  autonomic communications

25
3G beyond Testbed _at_ Fraunhofer FOKUS

• Nat. Open 3Gb Test Development Center
• Provision of a unique 3Gb Testbed covering all
  three 3G beyond layers
• Foundation for industrial and academic projects
• Applications development support
• Applications validation
• Service Platform prototyping
• Infrastructure component testing
• Network Technologies integration
• ....
• Officially supported by

Parlay Playground
IMS Playground
www.fokus.fraunhofer.de/national_host
26
IMS Playground _at_ 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

27
OPEN IMS Playground Overview

• Goals
• Provision of an open IMS platform and planned
  interconnection to other IMS testbeds
• Interoperability and compliance testing 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 research

28
FOKUS Components in the IMS Playground
FHoSS
SIPSEE
OCS / OCS X
Presence
XDMS
SER
SEMS
OSC
29
Integration of Partner Components _at_ FOKUS IMS PG
XDMS
Note This is not a complete Partner List!
30
IMS Playground - Use Cases

• 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 RD projects on Feature
  Interaction and Service composition

31
Overview

• How to stimulate IMS applications development?
• IMS as SDP and Service Enabler
• IMS Application Server Options (combining SIP AS
  and Parlay)
• Case Study IMS-based 3rd Party Community
  services
• IMS component testing and IMS service validation
  within the IMS Playground _at_ FOKUS
• Summary

32
Summary

• Telecommunications is at crossroads
• The internet and related IP-based technologies
  will change dramatically the service world
• IMS is in the center of converging networks
• IMS is a service platform framework harmonising
  the architectural thinking of different actors
  and forms the basis for NGN realisation
• IMS as platform is not defining services (OMA
  does it partially by defining service enablers)
• IMS killer applications remain unclear
• but without IMS classic fixed and mobile
  operators will have a hard time competing against
  internet services and emerging VNOs
• OSA/Parlay and ParlayX can act as the bridge
  towards the internet developer community and 3rd
  party service providers
• ? More information at www.fokus.fraunhofer.de/ims

33
Any Questions?
34
The Presenter

• Niklas Blum
• Niklas Blum is a senior research scientist at the
  3G beyond division at the Fraunhofer Institute
  FOKUS, which also provides the national 3G beyond
  test and development centre in Germany.
• His major research topics are applications and
  application provisioning for Next Generation
  Networks (NGN) using the IP Multimedia Subsystem.
  He is the author of several technical
  papers/articles.

35
For more Information ...

• If you need further consultancy or onsite
  technical coaching, please contact

Prof. Dr. Thomas Magedanz TUB Chair Next
Generation Networks / Director FOKUS 3Gb
Division magedanz_at_fokus.fraunhofer.de 49
171 172 70 70 ( 49 30 3463 7229 Kaiserin
Augusta-Allee 31 14513 Berlin, Germany