TMF TINA-C Liaison Collaboration with Flow Thru Dave

TMF/TINA-C Liaison & Collaboration with Flow. Thru Dave Lewis Flow. Thru Technical Co-ordinator Department of Computer Science University College London D. Lewis@cs. ucl. ac. uk

Outline • Introduce TINA-C & ACTS project Flow. Thru • Review draft TMF/TINA-C liaison agreement • Review further Flow. Thru/TMF collaboration possibilities

TINA Scope and Mission • TINA defines an all-encompassing open distributed software architecture for future telecommunication systems: – Rapid introduction of new advanced services – Integrated Management of the services and supporting infrastructure (network, computing equipment) • Service intelligence lies completely “outside” the network • Uses object-oriented specification and design principles • Long-term architecture integrating connection control, IN and TMN and through Open Distributed Processing (ODP) principles: – Portability, interoperability, reusability

The TINA Consortium (TINA-C) • Created in 1992 by telecom operators, telecom suppliers and computer vendors • Core Team (~30 researchers) was co-located at Bellcore, U. S. - different model to ITU-T and IETF standardisation • Work continues through “workgroups” • Various auxiliary projects world-wide are complementing, enhancing and validating the TINA architecture and specs through design, implementation and demonstration

TINA-C Members 3 Telecom operators AT&T Bellcore BNR BT Cable & Wireless Deutsche Telecom Eurescom France Telecom KDD Korea Telecom Telenor NTT KPN Portugal Telecom Stentor Sprint Telecom Italia Tele Danmark Telefonica Telia Research Telstra MCI CSELT Swiss PTT Telecom 3 Telecom Vendors Alcatel Telecom Ericsson / Ellemtel Fujitsu GPT Hitachi NEC Nokia Northern Telecom OKI Siemens 3 Computer - IT vendors 3 DEC HP IBM Isis Distributed Systems IONA Technologies Samsung Stratus Computer SUN Microsystems Unisys

TMF/TINA: The Major Differences • TMF addresses only mgmt, TINA has mostly focussed on service and network control • TMF covers general business processes, TINA focuses on automated DPE-based interactions • TMF aims at technology integration, TINA assumes DPE • TMF is member driven, addressing wide range of current services, TINA aimed at broadband, multimedia services • TMF focussed on process interactions and interface agreements, TINA more architecture and component driven

TMF/TINA Liaison • Aim: to avoid duplication and misalignment and take advantage of each other’s results where appropriate • Suggested Work Items: – Business Model mapping: TMF processes to TINA roles – TINA to benefit from TMF experience in move to UML (currently OMT+ IDL/ODL) – Component Engineering: TMF ACT may benefit from TINA experience in component-based modelling – Specific TINA solutions may aid TMF working groups: subscription mgmt for order handling, broadband config mgmt – OMG’s TINA-based Session Control/Subscription Mgmt RFP • Flow. Thru is using experience from integrating TINA and TMF models to facilitate the drafting of the liaison agreement.

TMF Business Process to TINA Business Role Mapping

Example: Multi-Domain Trouble Ticketting User/Customer Domain Retailer. Domain Connectivity Problem Reported by Customer Service Problem Reported by Customer Qo. S Degradation Reported by Customer Service User Connectivity Problem Detected by Provider 3 rd Party Service Provider Service Problem Service Quality Detected by Provider Manager Srv. Problem Service Quality Manager Service Problem Reported by Customer Service Problem Detected by Provider discount SLA violation detected by Provider Account Manager Request Bill with SLA Violation Discount Account Manager

Example: Business Model Mapping

Flow. Thru Overview • EU funded- started Mar’ 98, ends Feb’ 00 • Partners: – Waterford Institute of Technology(IRL), STS(UK), Algo. Systems(GR), GMD-Fokus(DE), TCD (IRL), UHC (DK), Alcatel Bell (BE), UCL (UK), Surrey University (UK), Alcatel Corporate Research (FR) • Input from: – Previous ACTS projects implementing advanced (often-TINA based) management systems – EURESCOM: methodology, trouble ticketting – Standards from TINA, TMF, ITU-T, OMG

Flow. Thru Goals • To provide validated Guidelines on how to build management system from Reusable Components, that satisfy Business Process requirements • Disseminate results to industry via Guidelines: – Development Methodology: UML, OOSE, use cases, facades – Component Integration Technology: CORBA Components, Workflow, technology gateways • Integrate existing components from ACTS projects and demonstrate working integrated management systems – Similar to catalyst projects built from research implementations – Separate demonstrators for fulfilment, assurance and accounting

Flow. Thru Development Methodology • Promote use of general OO techniques and UML for management system and component development • Approach is: – Business modelling through responsibility modelling, use cases and activity diagrams – Component modelling based on facades which traceably packages requirements, analysis and design models – Use OOSE Analysis Model to trace use cases to detailed design – Published component facades on web using paradigm Plus and customer scripts

Business Process Modelling

Tracing Use Cases via Analysis Model

Conventional Component Modelling Requirements Capture Component framework Component Design model Requirements Analysis model part of Design exports i/f exports Software Requirement s model trace i/f trace Design model Implementatio n trace Software Testing Deploy

Component Modelling with Facades Component Use case model Analysis model Requirements Capture exports i/f Requirements Analysis exports i/f exports Software i/f trace Analysis model i/f Design model Requirement s model trace Design model Implementatio n trace Software facade Testing Deploy

Further TMF/TINA/Flow. Thru Collaborations • Applying ACT requirements to CORBA Components, Workflow, EJB TINA • Design Assurance: – Facades and requirements tracability – Using XML with UML, using XML for CIF – XML DTD for propagating GDMO model, also IDL, ODL, SDL? • Management of IP Qo. S: SLAs, billing etc • Management of CORBAised IN based on TINA models