A New Operations Support System Architecture for Broadband IP Networks

1. A New Operations Support System Architecture for Broadband IP Networks Jong-Rak Lee leejr@kt.co.kr October 2003

2. Changes in telecom operational environment • Explosive expansion of Internet and increase of users • Advent of many CLECs and ISPs in Internet business areas • Competition • Sophiscated customer requirements • Various IP networks and services • Various OSSs were developed to meet the needs for individual networks and services management, which resulted in • Proliferation of independent legacy OSSs • Increased OPEX

3. IP network is evolving so fast … DU/ISDN PSTN, ISDN RAS AP-Hub xDSL GSR KIX NAS DSLAM GES KORNET Core K-LL Best Effort Router M-Ethernet S/W QoS/Security MPLS IP xDSL M-Ethernet S/W DiffServ IPsec • Core : faster, traffic engineered • Edge : focus on QoS management

4. Managing new IP networks (1) • Increased requirements for service management • QoS/SLA management • Customer self-control • Top down provisioning  Need for bottom-up data updating completed Customer Self-control receive order order processing Inventory Billing Billing Inventory order processing user profile resource allocated query request Self-control provisioning usage count Current provisioning New Customer real-time configuration Internet ISP

5. Managing new IP networks (2) • Increased requirements for network management • DiffServ + MPLS management • Traffic volume management  End-to-end flow management using NetFlow and/or sFlow • Integration of network and server management • Increased requirements for securitymanagement • Management of anomalous traffic • Separation of management network from service network

6. Why should current OSS be redesigned ? • Current Systems are • unable to support new IP services • Can not deliver premium services such as BoD, QoS/SLA guarantee and security services • So many OSSs developed on different platforms and different data models • Data integrity and maintenance problems exist • System development/Integration takes relatively longer time and is very expensive and risky  Can not meet time to market requirement BML SENSE OMAS NetIS ICIS SA 1.0 SO 1.0 RIMS ANSWERS TIMS DELMONS SML FM 1.0 K O S M O S CNM HiTS RNMS NetSolver ATM NMS MOST HiNet NMS PubNet NMS NML CTMS ITOS Disaster Mgmt IP- xDSL NMS NesPot NMS NAS NMS TEMS S I G N O S S N M S CO- LAN NMS DXC-CON FLC -EMS DSLAM -EMS WLL -EMS EOCMS EMOS DMAS B-DCS NMS EML ACOAM ATM EMS DXC-13 NMS COAM PMS TOMS CATMS MOAM ELITE MASTER NEL PSTN/Power/Env Data Transmission/LL Access <Fig> current major KT OSSs

7. Our goal to a New OSS (NeOSS) • Reduced time to market by • Applying a common platform • Improved data integrity by • Applying a common data model • Single data entry but multiple uses • Providing new functionalities to customers and operators • Single sign-on • Pre-ordering • Order tracking • SLA management • Enhanced work force management • On-line management of field information • One-stop handling of customer service requests • Single point of contact • Reduction of service provisioning and fault handling time

8. Receive Order Report Resource Alloc Provision Subscriber Facility Socket I/F Standard GUI /Single sign On Work order Processing Configuration Management Performance Management Etc. Network Topology Network Status Mgmt Policy TP monitor Scheduling Configuration DB Loading Common Interfaces New OSS (NeOSS) platform IP Traffic Management System Metro Ethernet Management System Leased Line Porvisioning OSS xDSL Porvisioning OSS Receive TT Report GUI GUI Query Information Status Config Status Config Test Subscriber DB load … DB load Facility XML/RPC SNMP SNMP/CLI Management Specific Applications Common DB Common Applications

9. New OSS (NeOSS) common data model Legacy OSS A ABC SDF Data conversion Legacy OSS C Human error ASDF Integrity check ㄱㄴㄷ ㄴㅇㄹ New OSS A Legacy OSS B Common DB New OSS B New OSS C DB mediator

10. New OSS (NeOSS) interworking architecture NetIS ICIS BMS Layer • Common interfaces • EAI/Message bus • Workflow engine • Web services (XML/SOAP) EAI SMS Layer SO SA SLA FM Business EAI/WorkFlow Process Manager WM ADM TOMS CNM MOST NMS Layer ETC Web services externalized process control IP-NMS ATM-NMS PUBNet FR-NMS IP-NMS IP-NMS ICIS : Integrated Customer Information Systtem NetIS : Network Information System SO : Service Ordeing System SA : Service Assurance System SLA : SLA Management System ADM : Access Domain Manager WM : Workforce Management System TOMS : Telecom Outside plant Management System CNM : Customer Network Management System MOST : Transmission NMS IP-NMS : Internet(Kornat) NMS ATM-NMS : ATM NMS PUBNet : Goverment Internet NMS FR-NMS : Frame Relay NMS

11. Concluding remarks • New operational environment requires a new (next generation) OSS which will enable • Reduced time to market • Fastersystem development speed • Flexibility in a changing business environment • Improvedservice provisioning and maintenance accuracy • Ensured data integrity • Automated work order processing • Keeping customers satisfied • More information for customers on performance and usage • Ensured customer service level by pre-ordering, order tracking and trouble tracking, etc.

12. Next generation is just around the corner. • Now is the right time to start the development of a New (next generation) OSS.