Dave Milham BT (EURESCOM Project P811 Leader)

1. Reference Framework for OSS Inter-connectionin a de-regulated Environmentinc. case studies on Number Portability,Charging and Accounting Dave Milham BT (EURESCOM Project P811 Leader)

2. Agenda • Overview of P811 • D1 OSS Interconnection Framework • D2 Number Portability case Study • D3 Charging and Accounting • Conclusions

3. 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

4. Drivers: Deregulated Telecom Market PNO OSS EURESCOM TMN Model (1994) • Based upon concept of • Public Network Operator (PNO) • Regulated Monopolies Xsuper Customer PNO OSS PNO OSS Xcoop Xuser • Deregulation impacts • More organisations able to offer Telecom Services • Organisations can perform more than one role • Organisation roles no longer static

5. 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

6. Deliverable 1 OSS Interconnection Framework

7. OSS Framework Studies • Goal • Generic European Processes/components for OSS Interconnect • Follow NMF Common Interconnection Gateway ‘Use cases’ and Information Model Approach • Capture Regulatory Requirements • European • National • Adapt/ integrate other work • EURESCOM P609 Process Modelling • TINA -C Reference Framework and Reference Points • Roles and and relationships

8. OSS Interconnect OSS Interconnect - What it is Operator A Operator B OSS OSS • Billing • Pre-order • Ordering • Repair • Capacity • Planning • … Network Network Interconnect Service Interface

9. OSS Interconnect - What it is not NOT internal Operator OSS interfaces Operator A Operator B OSS OSS OSS OSS OSS

10. API What is an OSS interface? Process & Information Protocol Telco Industry Domain Industry Groups TMF, NICC, ITU-T Semantics IT Industry Domain, DCE, CORBA IDL, TP Transport Protocol Mechanics & Plumbing IT Industry Domain TCP/IP, OSI/CMIP, CORBA IIOP,

11. Principles of OSS Interconnection • Seamless Service • Interconnect Service orientated • Autonomy • Electronic Interfaces • Simplicity • Technology • Internal Technology Choices • System IntegrityStandards Adherence

12. Regulatory Requirements • Service Parity • Interconnect Services. • Notification of Change • Performance Measurement • Electronic Interfaces • System Integrity • Standards Adherence

13. NM A BM SM B NM BM EM SM EM (a) Service Management to Service Management relationship NM A BM SM B NM BM EM SM EM (b) Network Management to Service Management relationship Interconnect Service & TMN

14. 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 OSS Interconnection Framework

15. Regulatory - Industry Processes Interconnect Service Definition and Technical Principles Interconnect Service Establishment Processes Interconnect Service Operation Processes Interconnect Service Establishment Maintenance Processes Interconnect Process Areas

16. Regulatory / Industry Processes European Regulation and Directives National Legislation EU Directives Legal Authority National Regulatory Authority Technical Mandates Industry/ Standards Body Codes of Practice Technical Specifications Policy e.g Pricing Principles Standard Interconnect Agreements Operating License Price List Operator Operator

17. Applying the OSS Framework

18. OSS Interconnection Modelling

19. Priorities for Process Automation • Priority areas • for Automation of • OSS processes: • Billing(Real time) • Repair • Ordering (for some services) • Interconnect Capacity • Planning

20. Deliverable 2 Number Portability Case Study

21. 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,….

22. Number Portability • ETSI Number Portability Task Force • Networking solutions • Approx. 9 variants of network solutions • Types of Numbers • Geographic • Non Geographic • Types of Number Portability • Service Provider • Service Portability

23. Impact Of Number Portability OSS Billing Systems Billing changes Electronic Service Management System Operator Services OA/999/Directory changes Network prefixes Network routing Network Manager Network Manual new order-handling mechanism Maintenance Services new Fault & Repair processes

24. Key Number Portability Processes • Ordering • Porting Provisioning • Porting Notifications • NP Number Administration Processes can be Bilateral and /or Between Operators and Trusted Third Parties

25. Customer Interaction Models

26. Operator Interaction Models

27. Bilateral Ordering & Porting

28. Bilateral Ordering & Centralised PNRDB

29. Centralised Porting

30. Centralised Porting and Number Admin

31. Roles

32. Changing Semantics of Directory Numbers

33. Deployment of Roles - Bilateral model

34. 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

35. Deliverable 3 Charging and Accounting Case Study

36. 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

37. 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

38. 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)

39. Centralised model example A possible variation, where a NO collects data from another NO via a mediation device (e.g. Billing subcontracting).

40. Centralised model example A possible variation, where a NO collects data from another NO via the signalling protocol

41. Centralised model example Interconnection will modify this internal scheme

42. 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

43. 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

44. 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.

45. 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

46. Deliverable 3 Contents • Mobility aspects • Impacts on Recommendations focus on location NP • introduction to mobility with an IN service (VHE) • Centralised Tariff Server Concept • 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 real-time topics)

47. 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

48. 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)

49. 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