Taming Monsters like Daidalos UML and ITU Languages in large Telecommunication projects – including Reliability aspects ISSRE04 WITUL Workshop Rennes .
Download ReportTranscript Taming Monsters like Daidalos UML and ITU Languages in large Telecommunication projects – including Reliability aspects ISSRE04 WITUL Workshop Rennes .
Taming Monsters like Daidalos UML and ITU Languages in large Telecommunication projects – including Reliability aspects ISSRE04 WITUL Workshop Rennes . November 2 . 2004 Yongzheng.Liang | Juergen.Jaehnert | Paul.Christ @ rus.uni-stuttgart.de Telemaco.Melia | [email protected] RUS Communication Systems 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 • 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 RUS Communication Systems WITUL 2004 . November 2 . 2004 . 2 The Daidalos Vision is 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 RUS Communication Systems WITUL 2004 . November 2 . 2004 . 3 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 RUS Communication Systems WITUL 2004 . November 2 . 2004 . 4 Daidalos Overview (trivial version) 3rdP SP 3rdP SP WP4 Pervasiveness WP3 Service Provisioning Platform WP2 Access Networks RUS Communication Systems 3rdP SP Context • Location •… • Access tech • Signal Q •… • Provider •… Mobility Dynamics WITUL 2004 . November 2 . 2004 . 5 Daidalos Overview (confusing version) RUS Communication Systems WITUL 2004 . November 2 . 2004 . 6 Example WP 4 - Pervasive Services Enabling Platform SERVICE PERVASIVE SERVICE PLATFORM Security Config. User Service Requests and Advertisements SC Rules & Commands RC USRA user service context Personalization P Federation/SLA Security & Pervasive Service Platform Personalization Privacy Manag. Federation/SLA Rules Manag. Federation/SLA Federation/SLA Event Manag. Pervasive Service Management SEC Security Services USC ICAPM Identity, Charging AAA. & Personal Mobility Services RUS Communication Systems SRD Service & Resource Discovery Services Context Manag. MCCS QoSB Multimedia Call QoS Broker Control Signaling & Services Session Mobility Services NM Network Monitoring Inerface Federation/SLA LNI Location & Network Information Services WITUL 2004 . November 2 . 2004 . 7 Example WP 3 - Service Provisioning Platform service discovery UserLocation service, etc. service QoS MultimediaMultimedia AAA, Identity, security broker CallControl signaling Charging Mobility services service services services services KDC in other domain, Key Federation/SLA Interconnection QoS Broker in other domain MMSPP server in other domain A4C in other domain Federation/SLA security QoSB MCC MS AAA KDC PBNMS QoS broker Service Discovery Server CMS Federation/SLA Federation/SLA Network Info Federation/SLA In other domain MMSPP AAA in AN RUS Communication Systems Network info broker Home Agent A4C AAA NI SD Service Provision Platform MS QoSB QoS Mgt security MIP NME NM NI AN MMSP AN QoS AR/ Mobile Mobile AR/CR/ER/ AN QoS AN Network Proxy/CAN Broker CR/ Terminal Terminal Mobile Broker info Corresp. Terminal ER Node WITUL 2004 . November 2 . 2004 . 8 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 RUS Communication Systems WITUL 2004 . November 2 . 2004 . 9 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 RUS Communication Systems WITUL 2004 . November 2 . 2004 . 10 Daidalos standardization context: OMG – ISO/ITU • OMG e.g. EDOC (Enterprise Distributed Object Computing) • Joined ISO JTC 1/ITU SC 7 ITU ODP, X.9xx • CORBA centric RUS Communication Systems WITUL 2004 . November 2 . 2004 . 11 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 RUS Communication Systems WITUL 2004 . November 2 . 2004 . 12 Daidalos - Integrated Reliability and Adaptability Reliability Proactive ………… Model-driven Adaptability Reactive …………. …………. …………. Reflective structural behavioral RUS Communication Systems WITUL 2004 . November 2 . 2004 . 13 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 RUS Communication Systems WITUL 2004 . November 2 . 2004 . 14 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 Reflective Architectures RUS Communication Systems WITUL 2004 . November 2 . 2004 . 15 Thank you Thank you! Questions? RUS Communication Systems WITUL 2004 . November 2 . 2004 . 16 UML Reflections RUS Communication Systems WITUL 2004 . November 2 . 2004 . 17