1 / 30

Niklas Blum TU Berlin / Fraunhofer FOKUS blum@fokus.fraunhofer.de fokus.fraunhofer.de/ims

ICT & OSA / Parlay Workshop Campinas/Sao Paulo, Brazil, March 22nd, 2006. Niklas Blum TU Berlin / Fraunhofer FOKUS blum@fokus.fraunhofer.de www.fokus.fraunhofer.de/ims. The Importance of OSA/Parlay in the Service Network Evolution. Overview. How to stimulate applications development?

london
Download Presentation

Niklas Blum TU Berlin / Fraunhofer FOKUS blum@fokus.fraunhofer.de fokus.fraunhofer.de/ims

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Niklas Blum Fraunhofer FOKUS 2006 ICT & OSA / Parlay Workshop Campinas/Sao Paulo, Brazil, March 22nd, 2006 Niklas Blum TU Berlin / Fraunhofer FOKUS blum@fokus.fraunhofer.de www.fokus.fraunhofer.de/ims The Importance of OSA/Parlay in the Service Network Evolution

  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 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 (Plug&Play 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. Niklas Blum Fraunhofer FOKUS 2006 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. Niklas Blum Fraunhofer FOKUS 2006 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. 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

  7. 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) 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. Niklas Blum Fraunhofer FOKUS 2006 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. 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.

  10. Niklas Blum Fraunhofer FOKUS 2006 IMS Layers: Transport, Session Control, Apps Application Plane SIP AS SIP AS Control Plane HSS I-CSCF S-CSCF SIP P-CSCF RTP Diameter MRFC MEGACO User Plane MRFP B-GW PSTN

  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 Today‘s 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

  13. Niklas Blum Fraunhofer FOKUS 2006 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 S-CSCF Online &Offline Charging (ECF, CCF) SIP-Server S S SIP Filter criteria P P T

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

  17. Niklas Blum Fraunhofer FOKUS 2006 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

  18. Niklas Blum 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!

  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 JAIN SLEE SIP AS OSA AS WS Clients Community Framework Community Feature RA Community Feature Community Feature ISC Parlay X OSA/Parlay Community Client GUI HTTP Policy Enforcement (OMA OSE) XCAP Service Enabler … SIP Media Server Framework UDDI Identity Management Presence GLMS Messaging RTP HSS IMS Core P/I/S-CSCF,MS,MG IN Platforms WLAN DSL GSM ISDN UMTS

  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, 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“

  24. National 3Gb R&D Projects European 3Gb R&D Projects Applications mHealth mGov mXXX. weitere weitere Other Apps Service Platforms & Middleware Web services Parlay IMS AAA SIP Engineering Tools,Conformance Testing, Measurments, and Management 3Gb Roaming weitere Other platforms UMTS FDD/ TDD GSM / GPRS WLAN a/b/x DVB- S/T weitere Other Netws 3Gb Network Technologies Niklas Blum Fraunhofer FOKUS 2006 3G beyond Testbed @ 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

  25. Niklas Blum 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

  26. Niklas Blum Fraunhofer FOKUS 2006 FOKUS – Components in the IMS Playground FHoSS SIPSEE OCS / OCS X Presence XDMS SER OSC SEMS

  27. Niklas Blum Fraunhofer FOKUS 2006 Integration of Partner Components @ FOKUS IMS PG XDMS Note: This is not a complete Partner List!

  28. 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 and Service composition

  29. Niklas Blum Fraunhofer FOKUS 2006 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

  30. Niklas Blum Fraunhofer FOKUS 2006 Any Questions?

More Related