sdp introduction two

Upload: parag-mahajani

Post on 14-Apr-2018

214 views

Category:

Documents


0 download

TRANSCRIPT

  • 7/27/2019 SDP Introduction Two

    1/6

    Service Delivery Platform (SDP)

    Release -1

    Abstract

    This document refers to Service Delivery Platform (SDP) which enables ServiceProviders to develop and deliver services more rapidly. It describes the overview,logical architecture and some typical SDP applications.

    1. Introduction

    SDP is an Open, Horizontal, Standards-based platform that enables ServiceProviders to create and deliver new innovative services for existing end users as wellas next generation services for SIP phones. New services for NGN are too complexand rigid to allow for the rapid creation and deployment in the network and are to bedeveloped by third party. SDP provides these services by insulating the servicedevelopers from the underlying complexities of the network, streamlining thedeployment of new services and enabling providers to respond to market needs inless time and at lower cost.

    The objectives of SDP are:

    Rapid service deployment for fastest time-to-revenue.

    Service differentiation for better customer acquisition and retention.

    Lower cost of service deployment.

    Telco grade proven, high reliability and adaptability

    To meet the above objects, SDP provides:

    A service creation environment

    A service orchestration and execution environment

    Abstractions for media control, presence/location, integration and other low-level communication capabilities service control environment

    2. Overview

    SDP at its simplest is a standards-based environment for design, deployment andmanagement of IT and network converged services. SDP opens up the network to avast community of services and developers without sacrificing the management,security and control necessary to deliver the quality of service, the telecom industrydemands. SDP has the following features:

    A Carrier grade execution environment for services that access next-generationas well as traditional networks. The explicit design of the SDP enables services towork on present as well as future networks, ensuring future proofing.

    Enablers and Enabler Framework that provide development time and run-time

    encapsulation of key components and building blocks that are critical to servicedevelopment.

    1

  • 7/27/2019 SDP Introduction Two

    2/6

    Components that bring SOA (Service Oriented Architecture) principles to aservice delivery context by enabling orchestration, policy enforcement andcomposition.

    A service gateway that allows partners controlled access to critical networkresources.

    A unified user profile that provides a unified view of user information to theservice layer and execution environment.

    Out of the box services built on the standards based platform.

    3. Logical Architecture

    Figure-1 above shows the logical architecture of SDP. Logical entities areApplications, Application Servers, Service Capability Servers (SCSs), theOSA/Parlay framework and Core Network Elements. SCSs are logicalimplementation of Enablers. Applications are deployed on Application Servers anduse the capabilities defined in OSA/Parlay and offered to the applications throughthe APIs. SCS implements the Server side and application the client side of API.Communication between the application and SCS is done using standard ITmiddleware infrastructure. Service Capability Servers (SCSs) implement the API(that is interface classes of the Service Capability Features) and potentially interactwith core network elements. Network elements may include Home Location Register(HLR), Mobile Switching Centre (MSC), Service Switching Point (SSP) etc.

    Application Servers could be either in the same business domain as the SCSs or inthe different domain.

    ApplicationServer

    e.g. Billing Servers

    InterfaceClass

    Applications

    OSA/Parlay Interface

    Frame work Call controlPresence Service Capability Servers (SCSs)(logical Implementation ofEnablers)

    SCF

    HLR MSC SSP Servers

    Figure1: Logical Architecture of Service Delivery Platform (SDP)

    SCS: Service Capability Server SCF:Service Capability Feature HLR: Home Location RegisterMSC: Mobile Switching Centre SSP: Service Switching Point OSA:Open Services Architecture

    SDP

    2

  • 7/27/2019 SDP Introduction Two

    3/6

    A service Capability Server may implement multiple SCFs. As an SCS is a logicalentity, it need not be implemented as a separate box. For example, Content basedCharging SCF might very well be directly offered by the Charging and Billing Serveritself.

    4. Enablers and Enabler FrameworkEnablers and Enabler Framework in SDP provide abstraction of complexity ofunderlying system to an application developer making possible application portabilityacross various systems that expose similar functionality, future-proofing and easingservice migration. SDP includes a common Enabler Framework as well as severalout of box Enablers built upon the enabler framework.

    4.1 Enablers

    Enablers are building blocks that expose a simple north bound API (e.g. with a Javaor a web service binding) and isolate the user from the complexities of the underlying

    network capabilities. This enables developers to develop network-centricapplications and future-proofing service development. In SDP, enablers providefollowing typical features and benefits:

    (i) Abstraction of underlying network technology choices and settings: Anenabler can expose the same capability northbound to an application developerthus stabilizing the application development API with respect to underlyingnetwork technology choices. As a result, migration at the network level andintegration with the existing and future network elements can be carried outincrementally without wholesale replacement.

    (ii) API based support for service integration: By supporting a broad range of

    APIs, enablers can permit a number of integration scenarios including in-housedevelopment as well as integration with 3rd party applications.

    (iii) Simpler OSS/BSS (Operations Support Systems/Business SupportSystems) integration: By providing enablers (such as charging) thatencapsulate common OSS/BSS integration requirements, operators canconsolidate and share OSS/BSS systems across multiple services.

    SDP includes several out of box enablers which expose common reusablefunctionality. Some out of box enablers such as SIP Servlet container, Call Control,Presence, Media Server Control and Messaging are described below briefly.

    4.1.1 SIP Servlet Container

    SIP Servlet Container is used to build SIP- specific services, whereby the applicationdeveloper need not to understand the complete signaling details of the SIP protocoland can instead program at a higher level of abstraction. SIP servlet containerintegrates with a variety of J2EE application servers.

    4.1.2 Call Control Enabler

    The Call Control Enabler provides north-bound Java and web services APIs for anumber of different call control scenarios across multiple networks. Simple exampleis click-to-dial scenario.

    3

  • 7/27/2019 SDP Introduction Two

    4/6

    4.1.3 Presence Enabler

    Presence information is central to a whole generation of next generationapplications. The presence enabler in SDP performs two major functions. First of allit aggregates presence information from a number of different sources in a persistentscalable manner. Secondly presence enabler provides ability to publish the presenceinformation to a number of different sources. Application developer can make anapplication immediately more responsive to presence information.

    4.1.4 Media Server Control Enabler

    The Media Server Control Enabler provides a set of standard north-bound APIs forcontrolling media server functionality across different control technologies hiding thedifferences in semantics between these control languages from the applicationdevelopers.

    4.1.5 Messaging Enabler

    The Messaging Enabler provides a set of north-bound Java and web service APIsthat an application can use to send and receive messages. Application developercan view messaging as an abstract service that can be implemented to connect toan arbitrary provider without having to understand or depend on what specificprotocol is used by that providers messaging gateway. As a result, the developer isable to integrate messaging into their applications in a more portable manner.

    4.2 Enabler Framework

    Enabler Framework is a general purpose enabler framework providing out of the boxenablers as well as enabling system integrators to develop additional enablers oftheir own to solve specific challenges. Enabler Framework expose north-bound APIs

    through Java or web service bindings and integrate south-bound to networkelements or west-bound to OSS/BSS systems through Java Connector Architecture.In addition, an enabler framework provides full life cycle support for enablers,including deployment, activation, upgrade, management, deactivation and un-deployment. As a result 3rd party developers can build their own enablers on thisEnabler Framework.

    5. Service Delivery Platform (SDP) Appl ications

    Service delivery applications can be classified based on network, technology orsolutions. Some example applications are shown below in Table-1.

    Table:1 SDP Applications

    S No. ClassificationBased on

    Example Applications

    1. Network i) NGN or IMS based applications:

    These applications are IP based and supportedover NGN or IMS Networks.

    ii) Legacy applications :

    These are circuit switched applications which aresupported on the legacy IN network in GSM,

    CDMA or PSTN.

    4

  • 7/27/2019 SDP Introduction Two

    5/6

    2. Technology i) Multi User Applications :

    They create a session with multiple users e.g.Audio Conferencing, Video Conferencing.

    ii) User to User Applications :

    These applications are between two users originated and destination, e.g. Voice over IP,Push to talk.

    iii) User to Server Applications :

    In these applications, originator is user and thedestination is a server in the network, e.g. SMS,MMS.

    iv) Server to User Applications :

    Here originator is server in the network and thedestination is user, e.g. Push Services, Click to

    Dial.3. Solution Type i) Entertainment & Content Delivery Solutions : e.g.

    Multi-location Presence Enabled Gaming.

    ii) Messaging Solutions:

    e.g. Short Message Service, Video Mail Solution,Video Mailbox.

    iii) Personal Convenience Solutions:

    e.g. Active Phone Book.

    iv) Personal Call Management Solutions :

    e.g. Communications Manager, Personal CallManager.

    v) Conferencing & Collaboration :

    e.g. Video Conferencing, Voice Conferencing.

    5. Conclusion

    SDP provides the platform for applications to meet customer demands for newtelecommunication services. The solution provides service creation and execution

    environment for composing enhanced services and delivering service bundles.

    Enablers are core components in the implementation of SDP. They are key buildingblocks of reusable functionality that provide standard interfaces. They bring manyfeatures of IT domain such as encapsulation, abstraction, standard APIs and reuseto the telecom Service providers domain. SDP provides both enablers as well asenabler framework that allow 3rd parties to build their own enablers.

    5

  • 7/27/2019 SDP Introduction Two

    6/6

    Abbreviat ions

    API Application Programming Interface

    BSS Business Support Systems

    CDMA Code Division Multiple Access

    GSM Global System for Mobile Communications

    HLR Home Location Register

    IMS IP Multimedia Subsystem

    J2EE Java to Enterprise Edition

    MMS Multi Media Messaging Service

    MSC Mobile Switching Centre

    NGN Next Generation Network

    OSS Operational Support Systems

    PSTN Public Switched Telephone Network

    SOA Service Oriented Architecture

    SCF Service Capability Feature

    SCS Service Capability Server

    SDP Service Delivery Platform

    SMS Short Message Service

    SSP Service Switching Point

    SIP Session Initiation Protocol

    6