the importance of osa/parlay in the service network...
TRANSCRIPT
1
Niklas Blum Fraunhofer FOKUS 2006
Niklas Blum
TU Berlin / Fraunhofer FOKUS
www.fokus.fraunhofer.de/ims
The Importance of OSA/Parlay in the Service Network Evolution
ICT & OSA / Parlay Workshop Campinas/Sao Paulo, Brazil, March 22nd, 2006
2
Niklas Blum Fraunhofer FOKUS 2006
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 @ FOKUS
• Summary
3
Niklas Blum Fraunhofer FOKUS 2006
The Drama of todays Service Space
• There is broad spectrum of technologies one has to understand in thecontext 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-optimumoffers which are not appreciated
• Innovation in the telecoms field is driven by technology push
• Access to the new technologies is quite complicated for small playersand most particular for application providers
• This is too expensive and often technology is promoted to early withraising wrong expectations resulting in frustration
• A technology pull model in which technology introduction will bedriven by concrete demand and specific applications
• This means the applications developers need early access to thetechnologies ���� Open testbeds are needed
4
Niklas Blum Fraunhofer FOKUS 2006
IP – Networkmobility-enabled
GSM
EDGE
GSM
EDGEUMTS
CDMA
UMTS
CDMA
WirelinexDSL
WirelinexDSL
POTS/ISDN
POTS/ISDN
otherother
CommonApplicationsand Services
WLANWiMax
WLANWiMax
Network Generation Network Vision
• Mobility and QoS enabled IP core
• Simplified service provisioning independent of access
5
Niklas Blum Fraunhofer FOKUS 2006
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 @ FOKUS
• Summary
6
Niklas Blum Fraunhofer FOKUS 2006
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) forinteroperability
• 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
7
Niklas Blum Fraunhofer FOKUS 2006
Communications Landscape Is Changing
The IT CommunityRich in Applications
and Creativity
The Telecom CommunityRich in Networks and Connectivity
Technical
Convergence
OSA, Parlay and JAIN are examples of emerging Technology Standards that facilitate the convergence
of the IT and Telecom communities
8
Niklas Blum Fraunhofer FOKUS 2006
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.
9
Niklas Blum Fraunhofer FOKUS 2006
IMS Layers: Transport, Session Control, Apps
User Plane
Application Plane
Control Plane
S-CSCF
HSS
SIP AS SIP AS
MRFC
B-GW
SIP
Diameter
PSTN
RTPI-CSCFP-CSCF
MRFP
MEGACO
10
Niklas Blum Fraunhofer FOKUS 2006
IMS Major Components
• The IMS is an Overlay Session/Service Control Architecture on top of thePacket 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 homenetwork
• 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 (IETF’s) SIP and DIAMETER (MAP and CAP are also important).
11
Niklas Blum Fraunhofer FOKUS 2006
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 @ FOKUS
• Summary
12
Niklas Blum Fraunhofer FOKUS 2006
IMS Application Server Options
User Plane
Application Plane
Control Plane
S-CSCF
HSS
SIP AS OSA GW IM-SSF
MRF B-GW
OSA/ParlayAS
SIP
Diameter
API
PSTN
RTP
Parlay API
CAMEL
CAP
Local ASI-CSCFP-CSCF
Today‘sfocus
13
Niklas Blum Fraunhofer FOKUS 2006
Online &Offline
Charging (ECF, CCF)
OSA / Parlay AS (3rd Parties)
Service Delivery Platform
(Application Server) Parlay App 1
Service Platform Trigger PointsParlay API (MPCC, MMM, Pres, Charg, ...
SIP Interface
HSS
S-CSCF
S
P
T
S
PFilter criteria
ISC
SIP
SIP-Server
Sh =
Diameter
Cx =
DiameterRo + Rf =
Diameter
Diameter
Parlay X GWParlay App 2
Parlay App 3
Parlay X App 1Parlay X App 2
Other accessnetworks
14
Niklas Blum Fraunhofer FOKUS 2006
NGN/IMS Applications
15
Niklas Blum Fraunhofer FOKUS 2006
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 @ FOKUS
• Summary
16
Niklas Blum 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 throughthe ISC interface
• OMA PoC does not consider access network issues (any access network canbe used)
• OMA PoC requires the XML Document Management (XDM) enabler for groupsession configuration
• OMA PoC may use OMA XDMS architecture for presence as a presenceenabler
• Dedicated floor control messages are used to grant access to the floor to ensure semi-duplex paradigm
17
Niklas Blum Fraunhofer FOKUS 2006
OMA PoC Architecture Rel. 1 (2005)
• Introduction of OMA Enablerarchitecture forPoC
• XML Dokument Management Enabler
• Alignment of PoCArchitecture to OMA enablerconcept
• Presence Enabler
• DeviceManagement Enabler
• NNI
Used Protocols:
• SIP
• RTP/RTCP
• RTCP
• XCAP
Source: OMA/PoC Candidate Version 1.0
18
Niklas Blum Fraunhofer FOKUS 2006
From PTT to Community-Support
• PoC/PTT basically defines a specific service based on genericenablers (Presence, GLMS/XDMS, FOTA)
• Infact PoC/PTT could be regarded as a specific instantiation of a groupcommunication 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 appreciatethis!
19
Niklas Blum Fraunhofer FOKUS 2006
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
20
Niklas Blum Fraunhofer FOKUS 2006
Community Services across different Networks
Community Service Providers
Community Framework
WS ClientsOSA ASSIP AS
Service Enabler
Presence GLMS Messaging
IMS CoreP/I/S-CSCF,MS,MG
IdentityManagement
…
HSS
WLAN
UMTSDSL GSM ISDN
FrameworkUDDI
IN Platforms
SIP
XCAP
HTTP
RTP
GUI
Community Client
CommunityFeature
CommunityFeature
CommunityFeature
Policy Enforcement (OMA OSE)
OSA/Parlay Parlay XISC
JAIN SLEE
RA
Media
Server
21
Niklas Blum Fraunhofer FOKUS 2006
Community Example: Push-to-Share
ParlayX Interfaces
22
Niklas Blum Fraunhofer FOKUS 2006
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 @ FOKUS
• Summary
23
Niklas Blum Fraunhofer FOKUS 2006
Fraunhofer FOKUS Facts
– FOKUS has been founded 1988 in Berlin, Germany
– 220 employees: scientists, students, techniciansoriginating from 30 nations
– FOKUS is THE Telecoms R&D institute within theFraunhofer 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 homeentertainment and performs applied research and development projects
• Performs strategic studies, solution concepts, system integration and prototypdevelopments
• 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“
24
Niklas Blum Fraunhofer FOKUS 2006
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
Applications
UMTSFDD/TDD
GSM /GPRS
WLANa/b/x
DVB-S/T
weitere
3Gb Network Technologies
Service Platforms& Middleware
mGov
OtherNetws
Parlay
3Gb Roaming
SIPAAAIMS
weitere
Web services
Otherplatforms
mHealth mXXX. weitereweitereOtherApps
Engineering Tools,Conform
ance
Testing,
Measurm
ents, and M
anagement
European 3Gb R&D Projects
National 3Gb R&D Projects
3G beyond Testbed @ Fraunhofer FOKUS
Parlay Playground
IMS Playground
www.fokus.fraunhofer.de/national_host
25
Niklas Blum Fraunhofer FOKUS 2006
IMS Playground @ FOKUS
• forms a globally unique state of the art IMS infrastructure featuring all majorIMS 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, applicationplatform extensions and IMS mobility, QoS and security reasearch
• Contact: www.fokus.fraunhofer.de/ims
26
Niklas Blum Fraunhofer FOKUS 2006
OPEN IMS Playground Overview
Goals:
– Provision of an open IMS platform and plannedinterconnection to otherIMS testbeds
– Interoperability and compliance testing of IMS components (S-CSCFs, Media Gateways, SIP AS, etc.)
– Environment fordevelopment of new MM applications, applicationplatform extensions and IMS mobility, QoS and security research
27
Niklas Blum Fraunhofer FOKUS 2006
FOKUS – Components in the IMS Playground
SEMSSEMS
FHoSSFHoSS
SERSER
SIPSEESIPSEEOCS / OCS /
OCS XOCS X
OSCOSC
28
Niklas Blum Fraunhofer FOKUS 2006
Integration of Partner Components @ FOKUS IMS PG
Note: This is not a complete Partner List!
29
Niklas Blum Fraunhofer FOKUS 2006
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 R&D projects on Feature Interaction andService composition
30
Niklas Blum Fraunhofer FOKUS 2006
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 @ FOKUS
• Summary
31
Niklas Blum 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)
– can be considered as THE universal Service Delivery Platform for NGNssupporting also Fixed Mobile Convergence (FMC)
• IMS should be mainly considered as a service enabler (i.e. no real IMS services are standardised!)
– but OMA defines services to be mapped onto IMS
– Push to Talk / PoC can be regarded as first IMS real life proof-of-concept
– Service implementation is flexible (CAMEL, SIP AS, OSA/Parlay) and requires probably more investigations
– Open testbeds are needed to test and validate IMS components and applications
• ���� More information at www.fokus.fraunhofer.de/ims
32
Niklas Blum Fraunhofer FOKUS 2006
Any Questions?
33
Niklas Blum Fraunhofer FOKUS 2006
The Presenter
Niklas Blum
Niklas Blum is a senior research scientist at the “3G beyond” division at the FraunhoferInstitute FOKUS, which also provides the national 3G beyond test and development centre in Germany.
His major research topics are applications and application provisioning for NextGeneration Networks (NGN) using the IP Multimedia Subsystem. He is the author of several technical papers/articles.
34
Niklas Blum Fraunhofer FOKUS 2006
For more Information ...
If you need further consultancy or onsite technical coaching, pleasecontact:
Prof. Dr. 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