Presentation on theme: "A New Operations Support System Architecture for Broadband IP Networks"— Presentation transcript:
1A New Operations Support System Architecture for Broadband IP Networks Jong-Rak LeeOctober 2003
2Changes in telecom operational environment Explosive expansion of Internet and increase of usersAdvent of many CLECs and ISPs in Internet business areasCompetitionSophiscated customer requirementsVarious IP networks and servicesVarious OSSs were developed to meet the needs for individual networks and services management, which resulted inProliferation of independent legacy OSSsIncreased OPEX
3IP network is evolving so fast … DU/ISDNPSTN,ISDNRASAP-HubxDSLGSRNASKIXDSLAMGESKORNETCoreK-LLBest EffortRouterM-EthernetS/WQoS/SecurityMPLSIP xDSLM-Ethernet S/WDiffServIPsecCore : faster, traffic engineeredEdge : focus on QoS management
4Managing new IP networks (1) Increased requirements for service managementQoS/SLA managementCustomer self-controlTop down provisioning Need for bottom-up data updatingcompletedCustomerSelf-controlreceiveorderBillingorderprocessingInventoryBillingInventoryorderprocessinguser profileresourceallocatedqueryrequestSelf-controlprovisioningusage countCurrentprovisioningCustomerNewreal-time configurationInternetISP
5Managing new IP networks (2) Increased requirements for network managementDiffServ + MPLS managementTraffic volume management End-to-end flow management using NetFlow and/or sFlowIntegration of network and server managementIncreased requirements for security managementManagement of anomalous trafficSeparation of management network from service network
6Why should current OSS be redesigned ? Current Systems areunable to support new IP servicesCan not deliver premium services such as BoD, QoS/SLA guarantee and security servicesSo many OSSs developed on different platforms and different data modelsData integrity and maintenance problems existSystem development/Integration takes relatively longer time and is very expensive and risky Can not meet time to market requirementBMLSENSEOMASNetISICISSO 1.0SA 1.0DELMONSANSWERSTIMSRIMSSMLKOSMFM 1.0CNMRNMSNetSolverHiTSATMNMSNMLCTMSITOSHiNetNMSPubNetNMSMOSTDisaster MgmtSIGNOSNMIP-xDSLNMSNesPotNMSNASNMSTEMSCO-LANNMSEOCMSEMOSDXC-CONFLC-EMSDSLAM-EMSWLL-EMSEMLDMASB-DCS NMSACOAMATMEMSDXC-13 NMSPMSCOAMCATMSTOMSELITEMOAMMASTERNELPSTN/Power/EnvDataTransmission/LLAccess<Fig> current major KT OSSs
7Our goal to a New OSS (NeOSS) Reduced time to market byApplying a common platformImproved data integrity byApplying a common data modelSingle data entry but multiple usesProviding new functionalities to customers and operatorsSingle sign-onPre-orderingOrder trackingSLA managementEnhanced work force managementOn-line management of field informationOne-stop handling of customer service requestsSingle point of contactReduction of service provisioning and fault handling time
11Concluding remarksNew operational environment requires a new (next generation) OSS which will enableReduced time to marketFaster system development speedFlexibility in a changing business environmentImproved service provisioning and maintenance accuracyEnsured data integrityAutomated work order processingKeeping customers satisfiedMore information for customers on performance and usageEnsured customer service level by pre-ordering, order tracking and trouble tracking, etc.
12Next generation is just around the corner. Now is the right time to start the developmentof a New (next generation) OSS.