OPENSIG Spring ’97, 17-18 April 1997 Cambridge, UK Service Execution Environment for Digital Multimedia Helsinki University of Technology / TCM Lab Service

OPENSIG Spring ’97, 17-18 April 1997Cambridge, UK

Service Execution Environment for Digital Multimedia

Helsinki University of Technology / TCM Lab


OPENSIG Spring ’97

Juhana Räsänen

Helsinki University of Technology

Laboratory of Telecommunications Software and Multimedia




Background

• Research team lead by prof. Olli Martikainen• ATM studied in TOVE project

– A prototype of an ITU-T compliant (Q.2931) ATM switch controller completed during 1996

– Development continues on NNI and IN– OO-methods in telecommunications software– Working knowledge of ATM

• So what: what is ATM used for?




B-ISDN scenario

Backbone network

STB

?

Access networkDomestic customer




Broadband access network

• Integration of the Internet-like services and stream-based services

• Open platform for easy service introduction

• Lightweight signalling: 100’s of users / switch

• Should utilize existing telephone wires– ATM over xDSL?

• Separation of switching and control




Standard ATM / B-ISDN?

• Several traffic classes and QoS: good support and performance for stream data transport

• Opening of the streams: Heavyweight signalling!

• Service concept unclear due to the standardisation lagging behind

• Troublesome IP support

SAAL

Q.2931

MTP-3

BISUP

Call Control

SCCPTCAPBINAP

SCP

SDP

SSP




IP switching?

• Good support for IP traffic, but no guaranteed streams

• Everything must be IP• Service concept?

– Authentication

– Billing & tariffing

– User profile, service portfolio

Flow analysis

IP routing




Layered control model

SCL

FCLNCL

SCL

FCLNCL

User STB

Service clientNCL

Service agent

1

1

22

3

1 Fabric control

2 Connection control

3 Service control

NCLService

2

3




Calypso architecture

• Based on the layered control model

• Service-oriented: aim is to create an environment in which service creation and deployment is as easy and flexible as possible

• Services are managed by Service Agents (SA) that are able to control the network directly

• A Service Execution Environment is needed




Service Execution Environment

• A standard environment for SA development– Class framework– Runtime environment– Helper services (authentication, billing, etc.)

• The interface between the network operator and service providers

• Also management functions can be integrated




Calypso bits and pieces• Service Execution Point

– A Linux workstation

• Service Execution Environment– Implementation in Java because

of mobile code and IP support

• Network Control Layer– Linux IP stack + path reservation

protocol based on RSVP

• Fabric Control Layer– VE (Virtual Exchange) of TOVE

SI

User 1Terminal

SI

User 2Terminal

Service

SEEIP protocols

SA

TOVE VE

SEP

SISI

SA




Future work

• The goal is to have a simple demo running in the end of 1997

• Further application and service experimenting in MediaPoli project

Documents

OPENSIG Spring ’97, 17-18 April 1997 Cambridge, UK Service Execution Environment for Digital Multimedia Helsinki University of Technology / TCM Lab Service