Session VIIa Service Platforms - TINA-C · PDF fileTCon TCon Consumer IA SSM USM CSM F SF USM...
Transcript of Session VIIa Service Platforms - TINA-C · PDF fileTCon TCon Consumer IA SSM USM CSM F SF USM...
1
Session VIIa: Service Platforms
Chair: Gerd Schuermann, GMD Fokus
1
Design and Implementation ofthe MESH Services Platform
Harold BatteramJohn-Luc BakkerJack VerhooselNikolay Diakov
Outline
vIntroduction.vMESH platform overview.vDistributed Software Component
Framework.vLessons learned.vFuture work.
2
MESH objectives
vTo accelerate the introduction ofadvanced telematics services for theESH.vTo study and explore new telematics
services possibilities.vTo design, implement and validate a
service platform for the ESH.
MESH partners
vLucent Technologies
vSURFnet
vKPN Research
vTelematics Institute
vCentre for Telematics andInformation Technology (CTIT)
(http://www.mesh.nl/extern/english.htm)
3
MESH users
vAcademic Hospital UniversityAmsterdam.vRoessingh Research and Development.vDelft University of Technology.vUniversity of Twente.
MESH business model
Service Provider
4
Retailer
MESH business model
NetworkProvider
MESH business model
5
ContentProvider
MESH business model
Service Designerand Developer
MESH business model
6
Service User
MESH business model
TINA Reference points
Co
nsu
mer
Co
nsu
mer
RetailerRetaileroror
Service ProviderService Provider
Co
nsu
mer
Co
nsu
mer
Connectivity ProviderConnectivity Provider
ConSConS
Ret
Ret
Ret
Ret
TC
onT
Con
TC
onT
Con
7
MESH infrastructure
ConSConS
Ret
Ret
Ret
Ret
TC
onT
Con
TC
onT
Con
Consumer Consumer
IAIA
SSMSSM
USMUSM
CSMCSMFF
SFSFUSMUSM
IAIA
PAPA
asUAPasUAP
ssUAPssUAP
TCSMTCSM
TLATLACCCC
RetailerRetaileroror
Service ProviderService Provider
ConnectivityConnectivityProviderProvider
CSMCSM
Consumer Consumer
PAPA
asUAPasUAP
ssUAPssUAP
TCSMTCSM
TLATLACCFCCF FCCFCC
TINA Service components
UAUA UAUA
SUBSUB
LNBMLNBMLNCLNC
MRMR MRMR
8
Problem description
vHow to realize a working system basedon the TINA specifications in a shorttime!
Approach
vCreate a Distributed SoftwareComponent FrameworkvTo accelerate the design, implementation
and testing of the MESH platform.vTo shield developers from system level
concerns.vTo create a highly modular system.
9
What is a component?
From Szyperski: Component Software, beyond objectoriented programming
A software component is a unit of composition withcontractually specified interfaces and explicit contextdependencies only.
A software component can be deployedindependently and is subject to composition by thirdparties.
Why components?
All other engineering discipline introducedcomponents as they became mature -and still use them!
Software engineering is becoming matureComponent standards and markets are
starting to emerge.
10
DSC features (1)
vComputationalviewpoint frameworkvencapsulation of
data and behaviorvsupports IDL
interfaces forinteraction
vsupport for multipleinterfaces
vEngineeringviewpointimplementationvlocation
transparencyvconcurrency
transparencyvruntime environmentvORB
DSC features (2)
vComponentinterfacevspecialization
through aggregationvdynamic compositionvlifecycle servicesvconfiguration
vDynamic and staticinterfaces
vEvent services
vDynamicdownloading
vTest & debugsupport
vDSC developmenttools
11
component 1
i_A
i_B
i_Component
i_Operational
component 1
i_A
i_B
i_Component
i_Operational
component 2
i_AA
i_BB
i_Component
i_Operational
i_BB
exported interface
12
container
component
i_Container
i_A
i_B
i_Component
i_Component
i_Operational
i_Operational
Component specification
component myComponent {
interface i_Interface {
fires interfaceEvent as octet
accepts acceptedEvent as string
}
contains mySubComp { i_Exported }
contains anotherComp { i_A, I_B }
}
13
IDLfiles
Componentspec. file
SkeletonGeneration
ComponentSkeleton files
Compiler
Component jar files
Developer modifies
ComponentComponentrepositoryrepository
IDLfiles
Componentspec. file
SkeletonGeneration
ComponentSkeleton files
Compiler
Component jar files
Developer modifies
ComponentComponentrepositoryrepository
14
IDLfiles
Componentspec. file
SkeletonGeneration
ComponentSkeleton files
Compiler
Component jar files
Developer modifies
ComponentComponentrepositoryrepository
IDLfiles
Componentspec. file
SkeletonGeneration
ComponentSkeleton files
Compiler
Component jar files
Developer modifies
ComponentComponentrepositoryrepository
15
IDLfiles
Componentspec. file
SkeletonGeneration
ComponentSkeleton files
Compiler
Component jar files
Developer modifies
ComponentComponentrepositoryrepository
component containerLocal
repository loadJar
createComponent()
instantiate Providerrepository
downloadComponent() repository server
User domain Provider domain
16
Component level diagnostics
v Interception perinterface.
v Shows IDL method calland parameter values.
v Allows method calltrace through thesystem.
Interface tester
vOne generated actorcomponent perinterface
vUseful for behaviorand regressiontesting
Operation_AOperation_BOperation_COperation_B
Actor
17
Call flow diagram
vDynamic generationof call flow diagrams
vVerification of actualbehavior withmessage sequencediagrams
Component A Component B Component C
ConsumerService ProviderConsumer
accesssession
Connectivity P rovider
IASUBIA
USM
CSMF
CCF CC
LNC
AS-UAP
USM
LNMBTLA
SS-UAP
PA
TCSM
AS-UAP
TLA
SS-UAP
PA
TCSM
UA UA
SF
SSM
CSM
FCC
usagesession
communicationsession
connectivitysession
18
ConsumerService ProviderConsumer
usagesession
Connectivity P rovider
IASUBIA
USM
CSMF
CCF CC
LNC
AS-UAP
USM
LNMBTLA
SS-UAP
PA
TCSM
AS-UAP
TLA
SS-UAP
PA
TCSM
UA UA
SF
SSM
CSM
FCC
accesssession
communicationsession
connectivitysession
ConsumerService ProviderConsumer
communicationsession
Connectivity P rovider
IASUBIA
USM
CSMF
CCF CC
LNC
AS-UAP
USM
LNMBTLA
SS-UAP
PA
TCSM
AS-UAP
TLA
SS-UAP
PA
TCSM
UA UA
SF
SSM
CSM
FCC
usagesession
accesssession
connectivitysession
19
Consumer
Connectivity P rovider
Consumer
connectivitysession
Service Provider
IASUBIA
USM
CSMF
CCF CC
LNC
AS-UAP
USM
LNMBTLA
SS-UAP
PA
TCSM
AS-UAP
TLA
SS-UAP
PA
TCSM
UA UA
SF
SSM
CSM
FCC
usagesession
accesssession
communicationsession
Conclusion
vTINA is complex but conceptuallysound and useful to us.vIDL specifications must be improved.vThe DSC framework enabled us to
create a working system based on theTINA specifications.
20
Future work
vNew project FRIENDS.vFocus on service creation and
deployment at a larger scale.vBased on the TINA and MESH
experiences.
Questions?
1
s98xxx
1
EURESCOM Services Platform
Aart van Halteren, 15 April 1999Aart van Halteren, 15 April 1999
s98xxx
2
Pan European Infrastructure for Service Experiments
EURESCOM: European Institute For Research and StrategicEURESCOM: European Institute For Research and StrategicStudies in TelecommunicationsStudies in Telecommunications
EURESCOM Services Platform: P715EURESCOM Services Platform: P715
Research topicsResearch topics-- Platform BuildingPlatform Building-- Service ManagementService Management-- Stream ManagementStream Management-- End-User ServicesEnd-User Services
2
s98xxx
3
EURESCOM P+T Iceland Telenor AS Tele Danmark A/S Telia AB, Sweden Telecom Finland Ltd. ATC Finland Telecom Eireann BT BELGACOM PTT Nederland P+T Luxembourg Deutsche Telekom AG Czech Telecom Slovak Telecom France Telecom Swiss Telecom PTT PTT Austria Hungarian Telecom. Portugal Telecom S.A. Telefonica de Espana STET, Itlay CPRM Portugal OTE Greece
European Institute forEuropean Institute forResearch and StrategicResearch and StrategicStudiesStudieson Telecommunicationson Telecommunications
s98xxx
4
EURESCOM Project 715
Helsinki Helsinki Telephone Telephone Company Company
Deutsche Deutsche TelekomTelekom FranceFrance
TlcomTlcom
KPNKPN