Geneva, Switzerland, 17 October 2011

ITU Workshop on “Service Delivery Platforms (SDP) for

Telecommunication Ecosystems: from today’s realities to requirements and

challenges of the future”

(Geneva, Switzerland, 17 October 2011 )

ITU-T Y.2240 : SDP for NGN

Marco Carugi Q3/13 RapporteurAli Ghazanfar Y.2240 Editor

ZTE Corporation

Introduction to NGN-SIDE [Y.2240]

NGN-SIDE ecosystem

NGN-SIDE functional view

NGN-SIDE capabilities

NGN-SIDE scenarios

Evolution paths

Agenda

2

SDP related activities within ITU-T SG13

ITU-T SG13 (“Future Networks including Mobile and NGN”) started around 2007 the development of specifications in the SDP area focusing on extensions to NGN, with the following major results:

Y.2234: Open service environment capabilities for NGN (approved in Sep 2008)

Liaison with OMA

Y.2020: Open service environment functional architecture for NGN (approved in May 2011) Y.2240: Requirements and capabilities for NGN service integration and delivery environment (approved in Apr 2011)

Liaison with OMA, IEEE NGSON, ATIS SON

Y.NGN-SIDE Arch: Functional architecture of NGN service integration and delivery environment (launched in Sep 2010)

This presentation will focus on Y.2240This presentation will focus on Y.2240 3

ITU-T Recommendation Y.2240

This Recommendation provides requirements and capabilities for a service integration and delivery environment in NGN (NGN-SIDE)

NGN-SIDE can be viewed as the next generation service delivery platform

Although in the context of Y.2240 NGN-SIDE is targeted for NGN, its framework can be conceptually applicable to other telecommunication environments (e.g. mobile networks)

4

NGN-SIDE work program

NGN-SIDE-Req setup in ITU-T Q3/SG13: 2009.04NGN-SIDE-Req setup in ITU-T Q3/SG13: 2009.04

NGN-SIDE-Req [ITU-T Y.2240] approval date: 2011.04NGN-SIDE-Req [ITU-T Y.2240] approval date: 2011.04

NGN-SIDE-Arch setup in ITU-T Q5/SG13: 2010.09NGN-SIDE-Arch setup in ITU-T Q5/SG13: 2010.09

NGN-SIDE-Arch approval target date: 2012.06

5

Some driving forces behind NGN-SIDE standardization

Many telecom operators are using service platforms in silos which increase CAPEX/OPEX

A unified service platform is needed integrating resources from different networks and supporting multiple applications

Telecom networks are being evolved to use IP-based infrastructure

It is essential to leverage the IP-based infrastructure to offer rich services and applications

App stores from terminal vendors support directly the developer community and allow control of whole value chain

A unified service platform allows operators to have a major role in the overall ecosystem, e.g.

exposing resources to application developersenabling integration of resources from different resource providers

6

NGN-SIDE main objectives and characteristics

NGN-SIDE aims to support a multi-fold telecommunication business model and a comprehensive eco-system for all stakeholders in the NGN value chain

NGN-SIDE puts NGN providers in the centre to control the whole NGN value chain

NGN-SIDE enables the development of applications leveraging underlying NGN and non-NGN resources such as:

taking full advantage of a variety of resources like service enablers, network capabilities, device enablers, content, other applications;providing access to a wide range of tools and technologies for the development of rich applications

7

Main functionalities of NGN-SIDE

Integration of resources from different domains (e.g. telecom domain (fixed and mobile networks), broadcast domain, internet domain, content provider domain etc.)Adaptation, including abstraction and virtualization, of resources from different domains Resource brokering for mediation among applications and resourcesApplication development environment for application developers Different service interfaces for exposure of NGN-SIDE capabilitiesMechanisms for support of diverse applications, including machine to machine apps, ubiquitous sensor network apps etc.Mechanisms for support of context-aware servicesMechanisms for content management

8

NGN-SIDE aims to support a multi-fold business model and a comprehensive ecosystem for all stakeholders in NGN value chainNGN-SIDE aims to support a multi-fold business model and a comprehensive ecosystem for all stakeholders in NGN value chain

NGN-SIDE provider

Contentproviders

Service enablerproviders

other resourceproviders

NGN-SIDE resource providers

Application developers

Application providers

Other NGN-SIDE users

NGN-SIDE users

Application providers

NGN-SIDE eco-system

Business roles

NGN-SIDE provides an open environment in NGN, with integration of resources from different domainsNGN-SIDE provides an open environment in NGN, with integration of resources from different domains

9

NGN-SIDE functional view

NGN-SIDEuserlayer

NGN-SIDElayer

Policy management

Content management

Charging

Management of role related information

Application provisioning

Context management

Applications

Service delivery management

Access control

Service executionService creation

Application development support

Service orchestration

Resource registry

Service dispatcher

Policy decision

Resource manager

Resource repository

Testing environment

NGN-SIDE integration layer

NGN-SIDE adaptation layer

Resource brokering

Adaptors for NGN Adaptors for Non-NGN

Resources offered by NGN Resources offered by Non-NGNNGN-SIDEresource

layer

Service creation functional group

11

It provides capabilities to realize an application development environment for application developersIt provides capabilities to realize an application development environment for application developers

Application development support

Application development support

Resource repositoryResource repository

Testing environment

Testing environment

Service execution functional group

12

Service orchestration

Service orchestration

Policy decisionPolicy decision

Resource registry

Resource registry

Access controlAccess control

Service dispatcherService

dispatcher

It provides capabilities to support the service execution environment:

It processes service requests received from applications It forwards the requests to the adaptation layer

It provides capabilities to support the service execution environment:

It processes service requests received from applications It forwards the requests to the adaptation layer

Service delivery management functional group

13

It provides capabilities to realize the management of different aspects:

ensuring proper functioning of service creation and service execution functional groups

providing associated delivery functionalities

It provides capabilities to realize the management of different aspects:

ensuring proper functioning of service creation and service execution functional groups

providing associated delivery functionalities

Application provisioningApplication provisioning

Content management

Content management

Context management

Context management

Roles related information management

Roles related information management

ChargingCharging

Policy management

Policy management

Adaptation capabilities

14 14

Resource brokering: mediates among resources and applications selects the appropriate resource before resource adaptation selects the appropriate application when request is sent from

resources towards applications Adaptors for NGN and Non-NGN:

perform network exposure to access capabilities from underlying networks

perform adaptation at both control and media level to hide underlying complexity and keep a horizontal service integration architecture

Resource brokering: mediates among resources and applications selects the appropriate resource before resource adaptation selects the appropriate application when request is sent from

resources towards applications Adaptors for NGN and Non-NGN:

perform network exposure to access capabilities from underlying networks

perform adaptation at both control and media level to hide underlying complexity and keep a horizontal service integration architecture

Resource brokeringResource brokering

Adaptors for NGN

Adaptors for NGN

Adaptors for Non-NGN

Adaptors for Non-NGN

NGN-SIDE business deployment scenarios

Content Provider

3rd Party Application Developer

3rd Party Application Provider

NGN ProviderNGN-SIDE provider

Contentprovider

NGN-SIDE Resource providers

Application developer

Application provider

(In-House)

NGN-SIDE users

Application provider

ResourceProvider (NGN

capabilities)

3rd Party Resource Provider

Application provider

3rd Party Resource Provider

Service enabler provider

3rd Party Application Provider

Application provider

15

This is just one example scenario [case of the “NGN provider” actor playing the role of “NGN-SIDE provider”]This is just one example scenario [case of the “NGN provider” actor playing the role of “NGN-SIDE provider”]

Actors Business roles

NGN-SIDE application scenariosThis is one of the use cases

It describes how SIDE can facilitate 3rd party apps, for ex. “Book a trip”, to access resources from different domains (i.e. Telecom and Internet)

This is one of the use cases

It describes how SIDE can facilitate 3rd party apps, for ex. “Book a trip”, to access resources from different domains (i.e. Telecom and Internet)

NGN-SIDE

CSN

Service registry

3rd party access control

MMS system

MMS capabi l i ty

User profile

Service integration

User A

1

Booking a Trip

APP logic

Travel Agency A

Applicatio Provision

adaptor

adaptor

Google

Ctrip

Meteorological Institute

Map Service

Booking & Info

Weather Info

1

1

1

adaptor

adaptor

2

3

4

677

8

5

9

16

Future SDP standardization: some evolution paths

Decentralized (distributed) SDPs

All services on demand: a Cloud-based SDP

Modular SDP architecture with common general purpose functional modules and device/service-specific functional modules

Data enhanced SDP (e.g. via data mining capabilities)

SDPs interconnection/federation for geographical pervasiveness

17

Thanks for your attention

Questions ?