170 likes | 426 Views
ISSRE04 WITUL Workshop Rennes . November 2 . 2004. Goals of our paper and talk. Overall- Goal: to possibly improve the applicability of UML and ITU Languages in large ‘modern’ time-constrained Telecommunication projects such as Daidalos to show the present usage of UML/SDL in Daidalos
E N D
ISSRE04 WITUL Workshop Rennes . November 2 . 2004
Goals of our paper and talk • Overall- Goal: to possibly improve the applicability of UML and ITU Languages in large ‘modern’ time-constrained Telecommunicationprojects such as Daidalos • to show the present usage of UML/SDL in Daidalos • to discuss Daidalos in the general and OMG context • to possibly propose contributions to the OMG and ITU concerning (testability – only in the paper- and) model driven adaptability and ‘reactive reliability’ based on Reflection
The Daidalos Visionis a world in which … • Mobile users can enjoy a diverse range of personalized services – seamlessly supported by the underlying technology and transparently provided through a pervasive interface • Mobility has been fully established through open, scalable and seamless integration of a complementary range of heterogeneous network technologies • Network and service operators are able to develop new business activities and provide profitable services in such an integrated mobile world
Daidalos Reality • IST FP6 • STRATEGIC OBJECTIVE 2.3.1.4: MOBILE AND WIRELESS SYSTEMS BEYOND 3G • Daidalos - Designing Advanced Interfaces for the Delivery and Administration of Location independent optimised personal Services. • Start 01.11.03 - Duration 24 + Duration 24 + 6 month • End 31.05.06 • 49 Partners • ~ 100 people working in parallel
3rdP SP 3rdP SP 3rdP SP WP4 Pervasiveness WP3 Service Provisioning Platform WP2 Access Networks Daidalos Overview (trivial version) • Context • Location • … • Access tech • Signal Q • … • Provider • … • Mobility • Dynamics
service discovery service QoS broker service Multimedia CallControl services Multimedia signaling services AAA, Identity, Charging Mobility services UserLocation service, etc. security services QoSB MCC MS NI security SD AAA KDC in other domain, Key Interconnection Service Provision Platform Federation/SLA KDC QoS Broker in other domain PBNMS Federation/SLA QoS broker NM Service Discovery Server CMS MMSPP server in other domain Federation/SLA MMSPP NME MS Network info broker A4C in other domain Home Agent Federation/SLA A4C Network Info In other domain AAA Federation/SLA MIP NI security QoSB QoS Mgt AAA in AN AN MMSP Proxy/CAN AN QoS Broker AR/ CR/ ER Mobile Terminal Mobile Terminal Corresp. Node AR/CR/ER/ Mobile Terminal AN QoS Broker AN Network info Example WP 3 - Service Provisioning Platform
Modelling in Daidalos so far • Convincing the non-convinced (ongoing) • Push Telelogic Tau – • license agreement, training • Detailed UML/SDL modeling in Terminal Mobility • Collect all type of input from all parties – ppt, visio, Rational, EA • Convert the input to Tau • 1st Tau integration: 1Workspace, 1project/view-element • WP-organization-view • functional-component-view • scenario-view (“Mobile University”, “Automotive”) • 2nd Tau integration: 1 Workspace 1project for all => inconsistencies become visible
High-level elements of the Daidalos service framework • Mobility • Context awareness – Pervasiveness • Service discovery and composition • Both operator- and user-orientation • Heterogeneity both in the technology and provider domain • Cope with heterogeneity in a technology independent manner
Daidalos standardization context: OMG – ISO/ITU • OMG e.g. EDOC (Enterprise Distributed Object Computing) • Joined ISO JTC 1/ITU SC 7ITU ODP, X.9xx • CORBA centric
Daidalos context: Adaptability – Reflection - Reliability • The case for Reflective Middleware – CACM June 2002 • Reflective Middleware Approach to …. Grid Middleware • Exploiting Reflection in Mobile Computing Middleware • Multi-Level Reflection for Fault Tolerant Architectures • Reflection, Self-Awareness and Self-Healing
Reliability Adaptability Proactive Reactive …………. Reflective structural behavioral Daidalos - Integrated Reliability and Adaptability Model-driven …………. …………. …………
Conclusion concerning UML and ITU Languages … • Address UML/ITU Languages applicability etc. in ‚real‘ projects: large, time constrained • A small testing and an UML/SDL etc. converged environment with improved • semantics and • treatment of time could support this goal • (see TTCN-3 below) • Continue work of Question 17 of ITU-T SG 17 and ETSI STF 250: UML profile for Communication Systems
Conclusion concerning UML and ITU Languages … • Evaluate Reflection both in the context of Reliability and Adaptability as possible extension of the UML MOF • evaluate related effort to exploit UML action semantics to provide Reflection • Compare/align(?) • TTCN-3-Testsystem_to_SUT with/to • UML/MOF-based ReflectiveArchitectures
Thank you Thank you! Questions?