Page 1 Accounting Management in a TINA- Based Service and Network Environment Patrick Hellemans, Cliff Redmond, Koen Daenen, Dave Lewis IS&N 99 - Barcelona.

Slides:



Advertisements
Similar presentations
Page 1 Bridging The Gap - CBE Extension for MTNM …Tying up OSS/J and Layer 2 Technologies.
Advertisements

Software Reuse SEII-Lecture 28
Karolina Muszyńska Based on:
Chapters 7 & 9 System Scope
SEBGIS 2005, Agia Napa, Cyprus, October 31 - November 4, 2005 MECOSIG Adapted to the Design of Distributed GIS F. Pasquasy, F. Laplanche, J-C. Sainte &
Chapter 22 Object-Oriented Systems Analysis and Design and UML Systems Analysis and Design Kendall and Kendall Fifth Edition.
System Modelling System modelling helps the analyst to understand the functionality of the system and models are used to communicate with customers. Different.
PARLAY and the 3GPP Open Service Architecture TINA ideas and principles Dr. Lucas Klostermann chairman 3GPP-CN5 system manager PU SCSA
CELLULAR COMMUNICATIONS 11 OSS. OSS/BSS  Operations Support Systems  Maintaining network inventory  Provisioning services process of preparing and.
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 8 Slide 1 System models.
1 SYSTEM and MODULE DESIGN Elements and Definitions.
Managing the Information Technology Resource Jerry N. Luftman
Policy-based Accounting Draft Sebastian Zander, Tanja Zseby GMD FOKUS - German National Research Institute for Information Technology Competence Center.
Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 8 Slide 1 System models.
Enterprise Total Computing TECHNOLOGY SERVICES Sprint Proprietary Information 18/10/99 Slide 1 Sprint’s Early Interest in TINA-C.
Use Case Modeling. Kendall & Kendall© 2005 Pearson Prentice Hall18-2 Commonly Used UML Diagrams The most commonly used UML diagrams are: – Use case diagram,
Supplement 02CASE Tools1 Supplement 02 - Case Tools And Franchise Colleges By MANSHA NAWAZ.
Course Instructor: Aisha Azeem
Presentation Speakers: Billy Herndon Angel Dronsfield May 2001 duke.
Privacy By Design Sample Use Case Privacy Controls Insurance Application- Vehicle Data.
Consult21 Systems Work Package BT Architecture and eBusiness Derrick Evans 21CN Systems.
OSS and BSS. Telecom Operation Map (TOM) Network and Systems Management Processes Service Development and Operations Processes Customer Care Processes.
Requirements for Component Integration Technology David Lewis FlowThru Technical Co-ordinator Department of Computer Science University College London.
© Drexel University Software Engineering Research Group (SERG) 1 Based on the paper by Philippe Kruchten from Rational Software.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 7 Slide 1 System models l Abstract descriptions of systems whose requirements are being.
Chapter 4 System Models A description of the various models that can be used to specify software systems.
System models. System modelling System modelling helps the analyst to understand the functionality of the system and models are used to communicate with.
System models Abstract descriptions of systems whose requirements are being analysed Abstract descriptions of systems whose requirements are being analysed.
MSF Requirements Envisioning Phase Planning Phase.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 6 Slide 1 Requirements Engineering Processes l Processes used to discover, analyse and.
ITEC 3220M Using and Designing Database Systems
Network Resource Gateway (NRG) Application DevelopmentDSLD Unit Florin van Slingerland Rev A Slide 1 Application Development Presentation/Course Teaser.
Requirements Elicitation. Who are the stakeholders in determining system requirements, and how does their viewpoint influence the process? How are non-technical.
BTS430 Systems Analysis and Design using UML Domain Model Part 1—Finding Conceptual Classes.
AIMS Workshop Heidelberg, 9-11 March 1998 Prospect Inter-Domain Management of IP-based Multimedia Teleservices Dr. Ralf Bracht, IBM.
Page  1 A practical investigation of billing for next generation services. Name: Moses T Nkhumeleni Supervisors: Professor Alfredo Terzoli and Mr Mosiuoa.
Guidelines for Component Reuse in Service Management Vincent P. Wade Department of Computer Science Trinity College Dublin Ireland
©Ian Sommerville 1995/2000 (Modified by Spiros Mancoridis 1999) Software Engineering, 6th edition. Chapter 7 Slide 1 System models l Abstract descriptions.
USE CASE Bayu Adhi Tama, MTI Faculty of Computer Science, University of Sriwijaya Slides are adapted from Petrus Mursanto
Demand Response Use Case & Functional Requirements Development UCAIug Meeting Jan 6, 2009 Mark van den Broek.
Chapter 7 System models.
Page 1 WWRF Briefing WG2-br2 · Kellerer/Arbanowski · · 03/2005 · WWRF13, Korea Stefan Arbanowski, Olaf Droegehorn, Wolfgang.
System models l Abstract descriptions of systems whose requirements are being analysed.
® IBM Software Group © 2006 IBM Corporation Writing Good Use Cases Module 1: Introduction to Use-Case Modeling.
What to remember from Chap 13 (Logical architecture)
1 System Analysis and Design Using UML INSTRUCTOR: Jesmin Akhter Lecturer, IIT, JU.
Discovering object interaction. Use case realisation The USE CASE diagram presents an outside view of the system. The functionality of the use case is.
Mainstreaming telecom: Using IT for business Elizabeth K. Adams President and CEO, TeleManagement Forum
System Context and Domain Analysis Abbas Rasoolzadegan.
NGCWE Expert Group EU-ESA Experts Group's vision Prof. Juan Quemada NGCWE Expert Group IST Call 5 Preparatory Workshop on CWEs 13th.
1 Accounting systems design & evaluation Karen Lau 25 Feb 2002.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 8 Slide 1 System models.
AIMS Workshop Heidelberg, 9-11 March 1998 P610 Technical Presentation, J Sallros/ ST P610 - Technically speaking Johan Sallros P610/Task4 Leader Telia.
section II Analysis Systems Analysis and Design
Analysis Yaodong Bi. Introduction to Analysis Purposes of Analysis – Resolve issues related to interference, concurrency, and conflicts among use cases.
UML (Unified Modeling Language)
UML - Development Process 1 Software Development Process Using UML.
Text TCS Internal September 29, 2014 Introduction to TMN Layer.
MMNS 2000 Supporting Service Quality Assurance via Trouble Management Dr Richard Sinnott GMD Fokus Berlin, Germany.
1 FORM Consortium FORM Partners: Atos (F - admin. Coord.), Broadcom(IRL), DELTA(DK), Ericsson(DK), GMD-Fokus(D), KPN Research(NL), Tele Danmark(DK), TCD(IRL),
Chapter 7 Lecture 1 Design and Implementation. Design and implementation Software design and implementation is the stage in the software engineering process.
Modelling Management Components for Reuse using UML David Lewis (FlowThru Technical Co-ordinator) Chris Malbon Alina DaCruz University College London.
Developing an IDM Information Delivery Manual Part 1. Industry Workgroup Training, Creating IDMs Alliance NA 2010 Dianne Davis, NA-IDM Coordinator Jan.
Demand Response Use Case & Functional Requirements Development UCAIug Meeting Jan 6, 2009 Mark van den Broek.
1 BTS330 Week 4 - Lecture 1 Businesses and Business Processes.
ONAP and MEF LSO External API Framework Functional Reference Architecture 12 July 2017 Andy Mayer, Ph.D. © 2016 AT&T Intellectual Property. All rights.
TMF Information Framework
TMF Information Framework
Design and Implementation
Presentation transcript:

Page 1 Accounting Management in a TINA- Based Service and Network Environment Patrick Hellemans, Cliff Redmond, Koen Daenen, Dave Lewis IS&N 99 - Barcelona

Page 2 FlowThru Project  ACTS Project: March February 2000  Focal Point of Research = Integrated Management Solutions Reuse, Customisation and Integration of Components Across organisational domains Across technological domains  Approach Define guidelines for system analysis and design Apply guidelines to the realisation of FlowThru system demonstrator

Page 3 Development Operation Management Systems Market Context Standard Organizations Component Vendors System Developers Service Providers Network Providers Frameworks & interfaces Business Needs Business Needs Frameworks & interfaces Requirements Components & Frameworks Requirements Integrated Systems

Page 4 Guidelines for Analysis and Design  Top-down approach Management Business Process Modeling (TMF, TINA-C)  Business Actors, Roles, Business Scenarios System Design  Components, Interactions, Information Flows Component Facades  Component Boundaries, External Actors, Interfaces  Bottom-up Approach Identification and analysis of reusable software components Adaptation and re-engineering requirements

Page 5 Guidelines for Analysis and Design  UML Notations Used At All Levels Profiling according to abstraction level Paradigm Plus and Rationale ROSE Session 3B Modeling Management Components for Reuse Using UML Dave Lewis

Page 6 FlowThru System Demonstrator - Business Scenarios  Accounting Scenario - subject of this paper  Fulfilment system pre-service phase Network planning, configuration and provisioning ATM connectivity services  Assurance system in-service phase Problem handling Adherence to Service Level Agreements Trouble Ticketing Service

Page 7 TM Forum Business Process Model Networks and Systems Management Processes Service/Product Development and Maintenance Processes Customer Care Processes Physical Network and Information Technology Sales Order Handling Problem Handling Customer QoS Mgt Invoicing/ Collection Service Planning/ Developmt Service Configu- ration Service Problem Resolution Service Quality Mgt Rating & Discounting Network Planning/ Developmt Network Provisioning Network Inventory Mgt Network Maintenance & Planning Network Data Mgt FulfilmentAssuranceAccounting

Page 8 Retailer Broker 3Pty Service Provider Connectivity Provider Consumer Mapping Onto TINA Business Model Invoicing/Collection Rating/Discounting Data Management Network Data Management Decomposed Into Service and Network Data Management

Page 9 Retailer Connectivity Provider Consumer FlowThru Accounting System Components Access Session Comp Access Session Comp Service Session Comp Service Session Comp Service Subscription Component Service Accounting Component Connection Management Component ATM Accounting Component Connection Management Component

Page 10 Retailer Connectivity Provider Consumer FlowThru Accounting System Components Service Session Comp Service Session Comp Service Subscription Component ATM Accounting Component Connection Management Component Connection Management Component Service Accounting Component Access Session Comp Access Session Comp Manage Secure Relationship Between Consumer and Retailer: service access, service subscription, … Implemented According to TINA Specifications Originate from VITAL Project Usage and Operation of Specific Service: - Digital Library - Multimedia Conference Implemented According to TINA Specifications Originate from VITAL Project Management of Subscription Contracts Implemented According to TINA Specifications Newly Developped for FlowThru Collecting and Collating Service-Level Usage Data, Generate Charges and Correlate with Network-Level Charges, Generate Consumer Bill Implemented According to TINA Specifications Originates from PROSPECT Connection Management on Top of ATM Network Implemented According to TINA Specifications Originate from VITAL and ReTINA Projects Collect Usage Data at Network (ATM) Level, Generate Network-Level Charges and Forward These to Service Accounting Component Newly Defined and Developped for FlowThru

Page 11 Accounting-Specific Use Cases  getBill Consumer Requests Bill for Certain Billing Period  getSessionCharges Consumer Requests Charges During Service Session  generateAccountableEvents Generate Accountable Events Towards Service and/or ATM Accounting Component  listAccountingSessions Request a List of Currently Active Management Accounting Sessions

Page 12 FlowThru Accounting System Components - Boundary Objects Retailer Connectivity Provider Consumer Access Session Comp Access Session Comp Service Session Comp Service Session Comp Service Subscription Component Service Accounting Component Connection Management Component ATM Accounting Component Connection Management Component Access Session Component Provider Agent: termination point of access session procedures in Consumer domain

Page 13 FlowThru Accounting System Components - Boundary Objects Retailer Connectivity Provider Consumer Access Session Comp Access Session Comp Service Session Comp Service Session Comp Service Subscription Component Service Accounting Component Connection Management Component ATM Accounting Component Connection Management Component Access Session Component User Agent: termination point of access session procedures in Retailer domain for one specific Consumer

Page 14 FlowThru Accounting System Components - Boundary Objects Retailer Connectivity Provider Consumer Access Session Comp Access Session Comp Service Session Comp Service Session Comp Service Subscription Component Service Accounting Component Connection Management Component ATM Accounting Component Connection Management Component Service Session Component Service Session User Application: termination point of service session procedures in Consumer domain for a specific service

Page 15 FlowThru Accounting System Components - Boundary Objects Retailer Connectivity Provider Consumer Access Session Comp Access Session Comp Service Session Comp Service Session Comp Service Subscription Component Service Accounting Component Connection Management Component ATM Accounting Component Connection Management Component Service Session Component Service Session Manager: Implements core logic of a specific service Generates accountable events towards Service Accounting Component

Page 16 FlowThru Accounting System Components - Boundary Objects Retailer Connectivity Provider Consumer Access Session Comp Access Session Comp Service Session Comp Service Session Comp Service Subscription Component Service Accounting Component Connection Management Component ATM Accounting Component Connection Management Component Subscription Component Subscription Agent: contact point within Subscription component for a specific Consumer Subscription Manager: manages subscription contracts

Page 17 FlowThru Accounting System Components - Boundary Objects Retailer Connectivity Provider Consumer Access Session Comp Access Session Comp Service Session Comp Service Session Comp Service Subscription Component Service Accounting Component Connection Management Component ATM Accounting Component Connection Management Component Service Accounting Component Account Manager: manages accounts for individual Consumers Usage Metering Data: receives, collects and collates accountable events at service-level Charge Control: calculates charges for a specific service session Bill Control: calculates Consumer bills Billing Aggregation: receives and correlates charges collected at network level

Page 18 FlowThru Accounting System Components - Boundary Objects Retailer Connectivity Provider Consumer Access Session Comp Access Session Comp Service Session Comp Service Session Comp Service Subscription Component Service Accounting Component Connection Management Component ATM Accounting Component Connection Management Component Connection Management Component Terminal Layer Adapter: termination point within Consumer domain of technology-specific connectivity management procedures

Page 19 FlowThru Accounting System Components - Boundary Objects Retailer Connectivity Provider Consumer Access Session Comp Access Session Comp Service Session Comp Service Session Comp Service Subscription Component Service Accounting Component Connection Management Component ATM Accounting Component Connection Management Component Connection Management Component Communication Session Manager: provides technology-independent connectivity service interface towards service level Layer Network Coordinator: coordinates technology-specific connectivity management procedures within a single administrative domain

Page 20 FlowThru Accounting System Components - Boundary Objects Retailer Connectivity Provider Consumer Access Session Comp Access Session Comp Service Session Comp Service Session Comp Service Subscription Component Service Accounting Component Connection Management Component ATM Accounting Component Connection Management Component ATM Accounting Component Metering Manager: receives, collects and collates accountable events at network (ATM) level Charge Manager: calculates charges collected at network (ATM) level

Page 21 Accounting System Realization - Status  Component and system analysis finalised  Component adaptation requirements identified  Component implementation adaptation on-going  System integration planned june-july

Page 22 Conclusions  FlowThru Guidelines Promote Reuse At Both Design and Implementation Level  Use of One Single Standard Notation (UML) At Different Abstraction Levels Eases Information Exchange, but More In-Depth Profiling of UML Notations Required  Component Facades Descriptions Ease Process of Building Management Systems by Reusing Existing Software Components Fitting components together to realize business scenarios Identifying required adaptations to reused components  TINA Specifications Sufficiently Detailed To Allow Component Integration Originated By Different Projects  FlowThru Guidelines and Demonstrator Results Will Be Presented to Teams of Experts During FlowThru Trial Phase (November 99)