Transcript 11Milham

Reference Framework for OSS Interconnection
in a de-regulated Environment
inc. case studies on
Number Portability,
Charging and Accounting
Dave Milham
BT
(EURESCOM Project P811 Leader)
Agenda





Overview of P811
D1 OSS Interconnection Framework
D2 Number Portability case Study
D3 Charging and Accounting
Conclusions
P811 Overview

OSS Interconnection Framework


Requirements
OSS Framework
•

Processes, business models, information models
Case Studies

Number Portability - Vertical study
•
•
•

Modelling Numbers and Number porting
Provisioning and Porting Processes
Information Models
Charging and Accounting - Horizontal Study and Vertical study
•
•
Linking network and OSS studies
– Internal processes
– external processes
Pricing - out of scope
Drivers: Deregulated Telecom Market
EURESCOM TMN Model (1994)

PNO
OSS
Based upon concept of
•
•
Public Network Operator (PNO)
Regulated Monopolies
Xsuper
PNO
OSS
Customer
Xuser
PNO
OSS
Xcoop
• Deregulation impacts
• More organisations able to offer Telecom Services
• Organisations can perform more than one role
• Organisation roles no longer static
Scope of P811

OSS framework




Requirements
The need for enhancement
OSS framework
Case Studies

Number Portability - Vertical study
•
•
•

Modelling Numbers and Number porting
Repair and Provisioning Processes
Information Models
Charging and Accounting - Horizontal Study and Vertical study
•
•
Real time Charging (network level and OSS level)
Linking network and OSS studies
Deliverable 1
OSS Interconnection Framework
OSS Framework Studies

Goal



Capture Regulatory Requirements



Generic European Processes/components for OSS Interconnect
Follow NMF Common Interconnection Gateway ‘Use cases’ and
Information Model Approach
European
National
Adapt/ integrate other work



EURESCOM P609 Process Modelling
TINA -C Reference Framework and Reference Points
Roles and and relationships
OSS Interconnect - What it is
Operator A
OSS
Network
OSS
Interconnect
•Billing
•Pre-order
•Ordering
•Repair
•Capacity
• Planning
•…
Interconnect Service Interface
Operator B
OSS
Network
OSS Interconnect
What
it
is
not
NOT internal
Operator B
Operator OSS interfaces
OSS
OSS
OSS
OSS
Operator A
OSS
What is an OSS interface?
Semantics
Process
& Information
Protocol
API
Mechanics
&
Plumbing
Transport
Protocol
Telco Industry Domain
Industry Groups TMF,
NICC, ITU-T
IT Industry Domain,
DCE, CORBA IDL, TP
IT Industry Domain
TCP/IP, OSI/CMIP,
CORBA IIOP,
Principles of OSS Interconnection

Seamless Service

Interconnect Service orientated

Autonomy

Electronic Interfaces

Simplicity

Technology

Internal Technology Choices

System Integrity Standards Adherence
Regulatory Requirements







Service Parity
Interconnect Services.
Notification of Change
Performance Measurement
Electronic Interfaces
System Integrity
Standards Adherence
Interconnect Service & TMN
A
BM
SM
NM
EM
B
BM
SM
NM
EM
(a) Service Management to Service Management relationship
A
BM
SM
NM
EM
B
BM
SM
NM
EM
(b) Network Management to Service Management relationship
OSS Interconnection Framework
OSS Interconnect
Processes
(Generic)
Business Models
(Generic and formal)
Specific Business Models and processes
e.g Number Portability
Specific
information systems development
by Telecom Organisations
Interconnect Process Areas
Regulatory - Industry Processes
Interconnect Service Definition and Technical Principles
Interconnect Service Establishment Processes
Interconnect
Service
Establishment
Maintenance
Processes
Interconnect
Service
Operation
Processes
Regulatory / Industry Processes
European Regulation and Directives
National Legislation
Legal Authority
National
Regulatory
Authority
Operating License
Policy e.g Pricing
Principles
Technical
Mandates
Codes of
Practice
Price
List
Operator
EU Directives
Industry/
Standards Body
Technical
Specifications
Standard
Interconnect
Agreements
Operator
Applying the OSS Framework
G en e ri c
In du st ry
B usi n es s
Service
Specific
Parameters
S p e c if ic
In du st ry
B usi n es s
P r oc e sse s
P r oc e sse s
C r oss re fe r en ce s
In t er c on ne c t io n
S p e c if ic I nt e co n ne c ti o n
B usi n es s M od e l
B usi n es s M od e l
S elec tio n o f sp e cific
B u si n ess m o d el
OSS Interconnection
Framework
Im p le m en ta tio n
S pe cifi c In form atio n
S ys te m s d e ve lo p m en t
OSS Interconnection Modelling
Business
Process
Model(s)
User Function
System Function
Business Process
Use Case model
Object model
Business Model
Development
Information System
Development
Use Case model
Analysis model
Design model
Implementation model
Priorities for Process Automation
In t e r c o n n e c t
Es t a b lis h m e
S e r v ic e
S e r v ic e
r e q u ir e d
P r in c ip le s
nt
m a in t e n a n c e
O p e r a t io n
A 2 A 2 A 2 A 3 ?N /R N /R A 2 A 3 A 1
Nu m b e r T r a n s la t io n s e r v ic e s
M
A2 M
M
M
M
A2 M
A 2 A 2 A 2 A 3 ?N /R N /R A 2 A 3 A 1
S e r v ic e s
M
A2 M
M
M
M
A2 M
M
M
M
A 3 ?N /R N /R A 2 A 3 A 1
In S p a n In t e r c o n n e c t
M
A2 M
M
M
M
A2 M
M
M
M
A ? N /R N /R A 2 A 3 A 1
C u s t o m e r S it e d In t e r c o n n e c t
M
A2 M
M
M
M
A2 M
M
M
M
A ? N /R N /R A 2 A 3 A 1
A d m in is t r a t iv e S e r v ic e s
M
A2 M
M
M
M
A2 M
N /R N /R N /R A ? N /R N /R A 2 A 3 A 1
In f o r m a tio n S y s te m /Ph o n e b o o k
M
A2 M
M
M
M
A2 M
N /R N /R N /R A ? N /R N /R A 2 A 3 A 1
O p e r a to r in f o r m a tio n A d d itio n
M
A2 M
M
M
M
A2 M
N /R N /R N /R A ? N /R N /R A 2 A 3 A 1
A s s is ta n c e S y s te m D a ta b a s e
M
A2 M
M
M
M
A2 M
N /R N /R N /R A ? N /R N /R A 2 A 3 A 1
In c u m b e n t D ir e c to r y S u p p ly
M
A2 M
M
M
M
A2 M
N /R N /R N /R A ? N /R N /R A 2 A 3 A 1
N u m b e r P o r ta b i l i ty
M
A2 M
M
M
M
A3 M
M
M
M
A1 A2 A1 A2 A3 A1
R e c ip r o c a l T r a n s f e r o f N u m b e r B lo c k s
M
A2 M
M
M
M
A2 M
M
M
M
A1 A2 A1 A2 A3 A1
( g e o g r a p h ic )
M
A2 M
M
M
M
A2 M
M
M
M
A1 A1 A1 A2 A3 A1
R e c ip r o c a l N o n G e o g r a p h ic N P
M
A2 M
M
M
M
A2 M
M
M
M
A1 A1 A1 A2 A3 A1
Billing/A ccounting
A2 M
Perf ormance
M
Repair
DataBase Build and Test
M
Ordering
Planning
M
Pre-Ordering: inquiries
Contact
A2 M
Process testing
Netw ork testing
M
Netw ork Perf omance
T e le p h o n e C o n v e y a n c e
Ma na ge m e nt Se rvice
Capacity & Traf f ic Forecasting
In t e r c o n n e c t
Traf f ic Routing
Number Range additions/routing modif ications
In t e r c o n n e c t
T e c h n ic a l
Capacity Planning - New Interconnection Link
S e r v ic e
M = M a n u a l Pr o c e s s e s N /R = N o t
Capacity Planning - New sw itch
S e r v ic e -
Capity Planning -New Point of Interconnection
K e y A 1 = A u to m a tio n Pr io r ity 1
Priority areas
for Automation of
OSS processes:
N e tw o r k S e r v i c e
A c c e s s t o in c u m b e n t S p e c ia l
En tr ie s in In c u m b e n t's n u m b e r
A c c e s s to In c u m b e n t's D ir e c to r y
C u s t o m e r S e r v ic e s
R e c ip r o c a l N u m b e r Po r ta b ility
•Billing(Real time)
•Repair
•Ordering (for some services)
•Interconnect Capacity
Planning
Deliverable 2
Number Portability Case Study
European Legislation on Number Portability

EC directive (for 1/1/2000)


Number Portability and Carrier Pre-selection 98/61/EU
From 2/1/2000,
•
•
•

European customer will be able to demand that NP is
immediately established between operators
Currently NP is established on a bi-lateral agreement based on
company readiness.
ONP 97/33/EU
Countries with NP deployed

UK, Netherlands, Denmark, Germany, France,….
Number Portability

ETSI Number Portability Task Force



Types of Numbers



Networking solutions
Approx. 9 variants of network solutions
Geographic
Non Geographic
Types of Number Portability


Service Provider
Service Portability
Impact Of Number Portability
OSS
Electronic
Service
Management
System
Billing
Systems
Billing changes
Operator
Services
OA/999/Directory changes
Network
Manager
Network prefixes
Network Network routing
Manual
new order-handling
mechanism
Maintenance
Services
new Fault & Repair
processes
Key Number Portability Processes




Ordering
Porting Provisioning
Porting Notifications
NP Number Administration
Processes can be Bilateral and /or
Between Operators and Trusted Third Parties
Customer Interaction Models
Customer
Recipient
Donor
“One stop shop”
MODEL
Customer
Other Operators
Recipient
Donor
“Do it yourself”
MODEL
Other Operators
Other Operators
Operator Interaction Models
mgt.
i/f
Operator
Operator
BILATERAL
AGREEMENT
mgt.
i/f
mgt.
i/f
Trusted
Third Party
Operator
mgt. i/f
Operator
CENTRALISED
CENTRALISED
MODEL
MODEL
Operator
Operator
Bilateral Ordering & Porting
•ORDERING
•PORTING
PROVISIONING (a)
•NUMBER
ADMINISTRATION
OP1
OP3
(Subsequent Porting)
•ORDERING
•PORTING
•NUMBER
ADMINISTRATION
•ORDERING
•PORTING
PROVISIONING (b)
•NUMBER
ADMINISTRATION
OP2
Bilateral Ordering & Centralised PNRDB
PNRDB
OP1
•ORDERING
•PORTING
PROVISIONING
•NUMBER
ADMINISTRATION
NL Model
PORTING
NOTIFICATION
(Broadcast)
OP2
Centralised Porting
PORTING NOTIFICATION
(Broadcast)
NPAC
PORTING
PROVISIONING
OP1
PORTING
PROVISIONING
•ORDERING
•NUMBER
ADMINISTRATION
OP2
Possible Swedish and Danish Model
US Model minus Number Range and Pooling info
Centralised Porting and Number Admin
PORTING NOTIFICATION
(Broadcast)
NUMBER
ADMINISTRATION
NUMBER
PORTING
•NUMBER ADMIN
•PORTING
PROVISIONING
•NUMBER ADMIN
•PORTING
PROVISIONING
ORDERING (a)
OP1
OP2
ORDERING (b)
Possible long term European solution
NA Serving Administration
Roles
Service Owner Number
Service Owner/
Customer
Retailer Service
Number
Administration
Number Admin Reservation
Retailer
Number Administration
Porting Provisioning
Service Provider
Porting Provisioning
Porting Provisioning
(Activation)
Number
Porting
Network Operator
Porting Notification
Porting Notification
Network Operators
Porting Administration
Changing Semantics of Directory Numbers
OOrga
rganisa
nisattion
ion
Holds
account
with
NNatio
ationnalal
RReg
egulato
ulatory
ry
AAuutho
thority
rity
SServi
ervice
ce OOwwne
nerr
Ho ld s
acco un t w ith
RRetetaiailelerr
A s s i gn s
Num
Numbe
ber r
RRaange
nge
SServi
ervice
ce PProvid
roviderer
D ef i ne s
NNuumb
mberer
RRan
ange
ge
Hol
Holde
der r
A d m in is ter s
1+
CCus
ustotomer
mer
NNuumb
mberer
BBloc
lockk
C on s t ra in t:
C NB
R an g e H o l de r m u s t be N O
n eed e d fo r
P A BX s ,
et c.
1+
NNeetw
twork
ork OOppera
erator
tor
DDire
irecctory
tory NNum
umbe
berr
Deployment of Roles - Bilateral model
Number
Administration
Number
Administration
Number Ranges
OP1-XXX, OP1-YXX
OP1-ZXX
Exported numbers
Retailer
NA
DB
SP Ordering
NA
DB
NW
DB
Number
Porting
NW
DB
Porting Provisioning
(Activation)
Number
Porting
Number Ranges
OP1-XXX, OP1-YXX
OP1-ZXX
Exported numbers
Porting Notification
NP
DB
Donor Op (OP1)
Number Ranges
OP2-MXX, OP2-NXX
OP2-PXX
Imported numbers
Other
Operators
Number Ranges
OP2-MXX, OP2-NXX
OP2-PXX
Imported numbers
NP
DB
Recipient Op (OP2)
Summary of D2 results





Business interaction model based on roles
Cover Geographic and Non Geographic Numbers
Model of Numbers, Number Ranges and Regulators
Demise of Number ranges
Model ‘Number’





Allocation processes
State model
Access users, processes and access/security rules
Model Number Porting Processes
NPAC a Physical instantiation of
•
•
Number porting administration / agency
Number reservation agent role
Deliverable 3
Charging and Accounting Case
Study
Scope of Deliverable 3

Charging mechanisms in a multi-network
operator and service-provider environment




Too much disparities between European countries on
regulatory issues or too general (only Cost representative)
Competitiveness requires more flexibility and automation in
processes
Externalisation of sensible information, which is traditionally
for internal use
BAC domain is essential and underlying all activities
 It needs a feed-back on internal processes
Scope of Deliverable 3

Billing processes are studied for two areas


Network Elements
• Data Generation
• Parameters and Protocols for Charging information
transport related to calls
• services related to Charging information (AoC,
prepayment, …)
Operation Support Systems (OSS)
• Scheduled process (Revenue Accounting)
• Unscheduled events (Audit, sampling, ...)

In both domain, there is a Real-time notion
Scope of Deliverable 3

Charging Process mechanisms

for collection of charging data
•
•

Distributed model
Centralised model
to transfer data between network operators and/or service
providers.
•
•
•
Depending of bilateral agreements authorised by the regulators
(this relationship has only to be faced on bilateral way)
An externalisation of sensible Data (security, accuracy)
Automation for the balancing mechanism used for Accounting
 it has to be tackled as a whole within the Charging centre
(combining complementary views for customers and end-users)
Centralised model example
charging centre
mediation device
PSTN/ISDN terminal
mediation device
Local switch point
Q3-interface
Transit switch point
Q3-interface
A
Service provider
A possible variation, where a NO collects data from
another NO via a mediation device (e.g. Billing
subcontracting).
B
Centralised model example
charging centre
PSTN/ISDN terminal
Local switch point
Transit switch point or
International gateway
Mediation device
Q3-interface
A
Data link for transfer of usage metering data
B
Service provider
A possible variation, where a NO collects data from
another NO via the signalling protocol
Centralised model example
PSTN/ ISDN terminal
charging centre
Local switch point
mediation device
Q3-interface
Transit switch point
Q3-interface
A
Service provider
Interconnection will modify this internal scheme
B
Deliverable 3 Main Results



An overview of the results from main
standardisation groups and international
project groups in this domain.
It identifies areas where there are still open
issues.
The problems addressed are relevant for all
players in the telecommunication market
Deliverable 3 Contents


Billing & Accounting Scenarios, data formats
On-line (during calls) exchange mechanisms




Proprietary and specific implementation in protocols
new requirements in signalling protocols (APM in ISUP and
INAP)
Real-time requirements
Off-line exchange mechanisms


Batch processes for accounting automation
Real-time requirements for unscheduled events
Deliverable 3 Part 1




Clarification of definitions used in BAC,
Synthesis of data formats and identification of
differences between standards and forums,
Overview of existing work and identification of
open issues,
Analysis of relations between functions at
network level and functions required at OSS
level.
Deliverable 3 Part 2






use cases for modelling interacting OSSs
 NP Use cases
 User Profile Use Cases – Billing profile
use cases for a Tariff server in an IN
environment (included UML model)
VHE case study configurations
IN call treatment model
Generic Accounting Model – PRISM Model
Location number – Danish example
Deliverable 3 Contents

Mobility aspects



Centralised Tariff Server Concept




Impacts on Recommendations focus on location NP
introduction to mobility with an IN service (VHE)
only for real-time aspects at network level
externalisation of switch function (easy administration of
dynamic tariff data)
distribution of dynamic tariff data (domain of interconnection)
Communication gateways and security
aspects

Billing Profile for OSS interconnection (also usable for realtime topics)
Project conclusions

OSS interconnection





need to take full life-cycle process viewpoint
essential to clearly define Interconnection Services
not all processes need to be automated
Identified priorities for automation
Use cases and OMT suitable basis for modelling
Number Portability



Common set of roles
Several organisational deployment options
Processes are mostly related to roles not
actors


more or less invariant across organisational deployments
independent of networking solutions ( 9 identified in ETSI
NP Task Force)
Project Conclusions

Charging and Accounting




New business models
Increasing complexity and diversity of relationships
No longer simply Networking an CC7 Issues
Need to model processes
•
•



Internal and external processes
Complementary TMN
Security of information a major and increasing concern
Development different across Europe (regulatory dependant)
Next step to focus on specific subsets of this study