page 1 accounting management in a tina- based service and network environment patrick hellemans,...

Accounting Management in a Accounting Management in a TINA-Based Service and TINA-Based Service and Network EnvironmentNetwork Environment

Patrick Hellemans, Cliff Redmond, Koen Patrick Hellemans, Cliff Redmond, Koen Daenen, Dave LewisDaenen, Dave Lewis

IS&N 99 - BarcelonaIS&N 99 - Barcelona

FlowThru Project

ACTS Project: March 1998 - 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

Development

Operation

Management Systems Market Context

StandardOrganizations

ComponentVendors

SystemDevelopers

ServiceProviders

NetworkProviders

Frameworks & interfaces

Business Needs

Business Needs

Frameworks & interfaces

Requirements

Components& Frameworks

RequirementsRequirements IntegratedSystems

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

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 UMLDave Lewis

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

TM Forum Business Process Model

Networks and Systems Management Processes

Service/Product Development and Maintenance Processes

Customer Care Processes

Physical Network and Information Technology

SalesOrder

HandlingProblemHandling

CustomerQoS Mgt

Invoicing/Collection

ServicePlanning/

Developmt

ServiceConfigu-ration

ServiceProblem

Resolution

ServiceQuality

Mgt

Rating &Discounting

NetworkPlanning/

Developmt

NetworkProvisioning

NetworkInventory

Mgt

NetworkMaintenance& Planning

NetworkDataMgt

Fulfilment Assurance Accounting

Ret

aile

r

Broker

3Pty Service Provider

ConnectivityProvider

Consumer

Mapping Onto TINA Business Model

Invoicing/Collection

Rating/Discounting

Rating/Discounting

Rating/Discounting

Data Management

Data Management

Data Management

Network Data ManagementDecomposed Into

Service and NetworkData Management

Retailer

Connectivity Provider

Consumer

FlowThru Accounting System Components

ServiceSessionComp

ServiceSessionComp

ServiceSubscriptionComponent

ATM AccountingComponent

ConnectionManagementComponent


ServiceAccountingComponent

AccessSessionComp

AccessSessionComp

Manage Secure Relationship BetweenConsumer and Retailer: service access, servicesubscription, …Implemented According to TINA SpecificationsOriginate from VITAL ProjectUsage and Operation of Specific Service:- Digital Library- Multimedia ConferenceImplemented According to TINA SpecificationsOriginate from VITAL Project

Management of Subscription ContractsImplemented According to TINA SpecificationsNewly Developped for FlowThru

Collecting and Collating Service-Level Usage Data,Generate Charges and Correlate with Network-LevelCharges, Generate Consumer Bill Implemented According to TINA SpecificationsOriginates from PROSPECT

Connection Management on Top of ATMNetworkImplemented According to TINA SpecificationsOriginate from VITAL and ReTINA Projects

Collect Usage Data at Network (ATM) Level,Generate Network-Level Charges and ForwardThese to Service Accounting ComponentNewly Defined and Developped for FlowThru

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

FlowThru Accounting System Components - Boundary Objects

Retailer


Consumer

AccessSessionComp

AccessSessionComp

ServiceSessionComp

ServiceSessionComp






Access Session Component

Provider Agent: terminationpoint of access session procedures in Consumer domain


Retailer


Consumer

AccessSessionComp

AccessSessionComp

ServiceSessionComp

ServiceSessionComp






Access Session Component

User Agent: terminationpoint of access session procedures in Retailer domain for one specific Consumer


Retailer


Consumer

AccessSessionComp

AccessSessionComp

ServiceSessionComp

ServiceSessionComp






Service Session Component

Service Session User Application:termination point of service session procedures in Consumer domain for a specificservice


Retailer


Consumer

AccessSessionComp

AccessSessionComp

ServiceSessionComp

ServiceSessionComp






Service Session Component

Service Session Manager:Implements core logic of aspecific serviceGenerates accountable eventstowards Service Accounting Component


Retailer


Consumer

AccessSessionComp

AccessSessionComp

ServiceSessionComp

ServiceSessionComp






Subscription Component

Subscription Agent: contactpoint within Subscriptioncomponent for a specificConsumerSubscription Manager: managessubscription contracts


Retailer


Consumer

AccessSessionComp

AccessSessionComp

ServiceSessionComp

ServiceSessionComp






Service Accounting Component

Account Manager: manages accounts for individualConsumersUsage Metering Data: receives, collects and collates accountable events at service-levelCharge Control: calculates charges for a specificservice sessionBill Control: calculates Consumer billsBilling Aggregation: receives and correlatescharges collected at network level


Retailer


Consumer

AccessSessionComp

AccessSessionComp

ServiceSessionComp

ServiceSessionComp






Connection Management Component

Terminal Layer Adapter: terminationpoint within Consumer domain oftechnology-specific connectivitymanagement procedures


Retailer


Consumer

AccessSessionComp

AccessSessionComp

ServiceSessionComp

ServiceSessionComp






Connection Management Component

Communication Session Manager:provides technology-independentconnectivity service interface towardsservice level

Layer Network Coordinator: coordinates technology-specific connectivity management procedureswithin a single administrative domain


Retailer


Consumer

AccessSessionComp

AccessSessionComp

ServiceSessionComp

ServiceSessionComp






ATM Accounting Component

Metering Manager: receives, collectsand collates accountable events atnetwork (ATM) level

Charge Manager: calculates chargescollected at network (ATM) level

Accounting System Realization - Status

Component and system analysis finalised

Component adaptation requirements identified

Component implementation adaptation on-going

System integration planned june-july

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)

page 1 accounting management in a tina- based service and network environment patrick hellemans,...

Documents