Presentation on theme: "APNOMS 2003 A New Operations Support System Architecture for Broadband IP Networks October 2003 Jong-Rak Lee"— Presentation transcript:
APNOMS 2003 A New Operations Support System Architecture for Broadband IP Networks October 2003 Jong-Rak Lee
KT Operations Support Systems Lab KT 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
KT Operations Support Systems Lab KT IP network is evolving so fast … Core : faster, traffic engineered Edge : focus on QoS management RAS PSTN, ISDN GSR KORNET Core AP-Hub KIX GES NAS Router DSLAM DU/IS DN xDSL K-LL IP xDSL M-Ethernet S/W M-Ethernet S/W Best Effort MPLS QoS/Security DiffServIPsec
KT Operations Support Systems Lab KT 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 Internet Customer ISP provisioning Self-control usage count real-time configuration receive order processing Inventory query provisioning request Customer Self-control user profile resource allocated Billing completed Current Billing order processing Inventory New
KT Operations Support Systems Lab KT 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 security management Management of anomalous traffic Separation of management network from service network
KT Operations Support Systems Lab KT 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 NML SML EML NELPSTN/Power/EnvDataTransmission/LL BML OMASSENSE TEMS HiNet NMS CO- LAN NMS Access DELMONS ANSWERSTIMS RIMS HiTS ACOAM COAM EOCMS EMOS ATM NMS SA 1.0 MOAM FLC -EMS WLL -EMS RNMSNetSolver CTMS ITOS SIGNOSSIGNOS SNMSSNMS PMS ELITE MOST DMAS DXC-CON B-DCS NMS DXC-13 NMS MASTER DSLAM -EMS TOMS CATMS SO 1.0 CNM KOSMOSKOSMOS Disaster Mgmt NetIS IP- xDSL NMS NesPot NMS NAS NMS ATM EMS PubNet NMS FM 1.0 ICIS current major KT OSSs current major KT OSSs
KT Operations Support Systems Lab KT 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
KT Operations Support Systems Lab KT New OSS (NeOSS) platform Socket I/F Provision Receive Order Resource Alloc Report Facility Subscriber XML/RPC Test Receive TT Query Information Report Facility Subscriber SNMP DB load GUI StatusConfig SNMP/CLI GUI StatusConfig xDSL Porvisioning OSS Leased Line Porvisioning OSS IP Traffic Management System Metro Ethernet Management System Common DB Common Interfaces Configuration DB Loading TP monitor ConfigurationManagement Work order ProcessingPerformanceManagementEtc. Scheduling NetworkTopologyNetworkStatusMgmtPolicy Standard GUI /Single sign On Management Specific Applications Common Applications …
KT Operations Support Systems Lab KT New OSS (NeOSS) common data model ABCSDF ASDF Legacy OSS A Legacy OSS B Data conversion New OSS C New OSS A New OSS B Integritycheck Human error Common DB DB mediator Legacy OSS C
KT Operations Support Systems Lab KT SO BMS Layer SMS Layer NMS Layer NetIS WM ICIS SLA ETC SA MOSTTOMS ADM IP-NMS CNM PUBNetFR-NMS ATM-NMS FM New OSS (NeOSS) interworking architecture EAI/WorkFlow EAI Common interfaces EAI/Message bus Workflow engine Web services (XML/SOAP) externalized process control Business Process Manager 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 Web services 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 IP-NMS
KT Operations Support Systems Lab KT Concluding remarks New operational environment requires a new (next generation) OSS which will enable Reduced time to market Faster system development speed Flexibility in a changing business environment Improved service 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.
KT Operations Support Systems Lab KT Next generation is just around the corner. Now is the right time to start the development of a New (next generation) OSS.