AIMS Workshop Heidelberg, 9-11 March 1998 P610 Technical Presentation, J Sallros/ ST P610 - Technically speaking Johan Sallros P610/Task4 Leader Telia

P610 Technical Presentation, J

Sallros/ STAIMS Workshop

Heidelberg, 9-11 March 1998

P610 - Technically speaking

Johan Sallros

P610/Task4 LeaderTelia Research

[email protected]

Tel: +46 8 713 8490 Fax: + 46 8 713 8484




Outline

• Observations

• The Mission (Impossible?)

• Technical Foundations

• Current Landmarks and Updates

– Architecture– Methodology

• What will be?

• Conclusion




What will management look like?

• Impact of the Internet boom

• Breakthrough of distributed systems

• Deregulation

• Cooperation

• Integration of service and management

• Customer in charge

• New payment paradigms

• ...




The Mission

• Refining state-of-the-art to provide means to:

– Design and provide appropriateappropriate management for contemporary and future multimedia services

• at lowlow (no?) costcost• in in no timeno time at all




Applied Technology

• TINA, CORBA, TMN and NMF for Architecture

– FCAPS + Customer Care– Actor Profile Management– Multi Domain Management– Service Trading– UML for structuring the architecture (using packages)

• TINA, ORDIT, UML and … P610! for the Methodology

– and the good old OO!

• All of the above for the Framework

– to provide a context for multimedia service management




P610 Architecture

Configuration MaintenanceCharging &Billing

Performance

Multimedia Service Management

ServiceAbstraction

Functional Package

Actor Support PackageService Support Package

Security

NetworkAbstraction Profiles

Mobility(P)Customer Query & Control




P610 Architecture - VIP´s

• Charging/Billing incl. e-payment

• Service Trading

• Naming

• Content Management

• Subscription Management

• Service Composition

• Multi-domain Management

• Customer Query & Control




Current Landmarks - Methodology (1)

Stage 1

Stage 2

Stage 3

Requirements capture

Object oriented analysis

Architecture mapping




Methodology Stage 1

Service description

Business modelling Use Case modelling




Business modelling

Responsibilities/ AX

Obligations/ AX

Responsibilities/ BY

Obligations/ BY

Contract AX/BY

Capabilities/AX

Rights/ AX

Authorisation

Actor A Role X

Capabilities/BY

Rights/ BY

Actor BRole Y




The P610 Business Model

Customer

Content/Information

ProviderServiceProvider

User

ServiceProvider

Transport networkProvider

Contractual agreement

AccessProvider




Use Case modellingRefine the Use Case Actorsbeing modelled

Determine Use Cases

11

2

Prioritise Use CasesDescribe Use Cases

Describe User Interface etc.

Optional




Methodology Stage 2

Input from e.g.Std org/fora:- Info models- Patterns

Domain ClassModell

Domainexperience

Application ClassModell

Sequence diagramsState diagrams

Collaboration diagr.

attributes & operations




What will be?

• Optimistic view:

– Increasingly refined architecture and domain models– Incremental cost and time reduction in development

• Pessimistic view:

– YASMP!




Conclusion

• State-of-the-Art Multimedia Service Management, revised

• Architecture - ready-to-use

• Methodology supporting reuse and efficiency

• Now it´s time to use it!

Documents

AIMS Workshop Heidelberg, 9-11 March 1998 P610 Technical Presentation, J Sallros/ ST P610 - Technically speaking Johan Sallros P610/Task4 Leader Telia