Creating Telecommunication Services based on Object- Oriented Frameworks and SDL Dr Richard Sinnott GMD Fokus Berlin, Germany

ISORC, St. Malo, May 1999 Introduction Service creation environments should: –reduce time to market –reduce development costs –allow for higher service quality TOSCA project is developing tools and techniques to address this based on –object-oriented frameworks –formal techniques

The TOSCA Consortium GMD Fokus BT EricssonTelelogic IONA University of Lund University of Strathclyde CSELT S3 Teltec

ISORC, St. Malo, May 1999 Overview of Presentation Outline of Service Creation inTOSCA Creation of Object-Oriented Frameworks Specialisation of Frameworks to Services Relating the Model and Implementation ConclusionsDemo(?)

ISORC, St. Malo, May 1999 Service Creation in TOSCA Object-oriented frameworks based around TINA service session components –allow for re-use of design –fixed flexibility points for specialisation Specialisation done through paradigm tool –graphical and intuitive tool that abstracts from framework complexity/representation

ISORC, St. Malo, May 1999 Overview of Approach SDL FW C++/CORBA FW Paradigm Tool SDL Service Model C++/CORBA Service Impl. SDL code generated impl. CORBA BASED SERVICE PLATFORM focus of presentation ? ? ??

ISORC, St. Malo, May 1999 Introduction to TINA ODP based architecture for developing telecommunications services ­chatline, multimedia conference, video phone, neighbourhood watch,... etc Focus mostly on computational aspects ­ objects and interfaces identified ­ ODL and IDL provided

ISORC, St. Malo, May 1999 TINA Object Definition Language Extends IDL (strict superset) –supports objects with multiple interfaces ­required and supported interfaces ­stream and operational interfaces ­initial interface ­supports object groups ­contracts ­managers

ISORC, St. Malo, May 1999 TINA Sessions Central concept to TINA is a session –access session: how to access services that have been subscribed to –service session: how to execute and control services that have been accessed –communication session: controls network resources for end to end connections

ISORC, St. Malo, May 1999 Relation between TINA Sessions

Outline of USM Structure UFSmgr USPmgr UFS USP generic objects DynamicWindow Handlers Invite Window Handler other handlers ssuapssuap ssm or other usms

ISORC, St. Malo, May 1999 Object-oriented Frameworks Mostly completed models of services –include semantics!!! –developed around TINA ODL/IDL Have predefined holes where service creators can add/refine behaviour –start, stop, suspend, resume of user sessions –start, stop, suspend, resume service sessions

ISORC, St. Malo, May 1999 IDL for USM manager interface i_UFSmgr : i_CO_lifecycle { void suspendSessionRequest(); void terminateSessionRequest(); void suspendAll(); void requestObject(inout NamedObject obj); oneway void ufsstart(); oneway void ufsstop(); oneway void ufssuspend(); oneway void ufsresume();....} ;

ISORC, St. Malo, May 1999 Mapping Rules for ODL/IDL to SDL

ISORC, St. Malo, May 1999 Mapping ODL/IDL to SDL Creates two packages –name interface with signal definitions, data types and client stubs –name definition with server skeletons Behaviour added through use-ing and inheriting packages

ISORC, St. Malo, May 1999 Example of Signal Mapping

ISORC, St. Malo, May 1999 Example of Server Mapping

ISORC, St. Malo, May 1999 Creating and Checking Framework Framework behaviour added based on –informal ODL text –use cases showing desired behaviour Simulation/animation techniques used to ensure framework has correct behaviour - possible since framework flexibility points represented as empty procedures in SDL

ISORC, St. Malo, May 1999 Example of SDL Framework

ISORC, St. Malo, May 1999 Specialising Framework Framework specialised through adding behaviour to flexibility points –start, stop, suspend, resume Typical specialisations –add buttons, windows, etc to ssUAP‘s of session members and have appropriate behaviour when pressed

ISORC, St. Malo, May 1999 Creating Videophone Service Informal Videophone Service Requirements Have two roles: caller and callee Caller invites callee (callee cannot invite!) When caller quits the service terminates When callee suspends, they must resume in thirty seconds or they are terminated

ISORC, St. Malo, May 1999 Specialising SDL for Caller Start

ISORC, St. Malo, May 1999 Specialising SDL for Suspension and Resumption of Callee

ISORC, St. Malo, May continued

Using SDL Service Model SDL model used to –explore behaviour of service in depth, e.g. to ensure certain properties always/never true Once model checked ok can use it –as basis for implementation –for validating implementation

ISORC, St. Malo, May 1999 SDL Model for Implementation Work on-going on refining code generation techniques –currently support partitioned code generation and usage of C++/CORBA wrappers –working on (and nearing completion!) of IIOP supported, partitioned code generation

ISORC, St. Malo, May 1999 SDL Model for Validation Validation based on –deriving (TTCN) abstract test cases from SDL model can generate test cases whilst animatingcan generate test cases whilst animating –converting to executable test suites –executing test cases through TTCN/CORBA gateway (TCgate)

ISORC, St. Malo, May 1999 Test Case Generation

ISORC, St. Malo, May 1999 Executing Test Cases ITEX used to convert ATS to ETS (C-code) ITEX GCI allows test cases to be adapted to particulars of environment - CORBA based! TCgate includes main, client and server parts Gateway interactions with ORB done through DII (clients) or DSI (servers) Run-time type info. based on interface repository

ISORC, St. Malo, May 1999 Conclusions Applying formal approaches to realistic and re-usable software development ODL/IDL basis supports direct relations between model and implementation Tool support crucial if formal techniques to be more widely accepted –TOSCA has tool chain for complete lifecycle of software development

ISORC, St. Malo, May 1999 Further information at: