Presentation is loading. Please wait.

Presentation is loading. Please wait.

Conceptual View of KT NGN

Similar presentations

Presentation on theme: "Conceptual View of KT NGN"— Presentation transcript:

0 KT NGN and its Management Plan Mun Jo Jung*, Sung Hak Seok**
Mun Jo Jung*, Sung Hak Seok** *Technology Laboratory **Operations Support System Laboratory Hello, Ladies and Gentlemen. I am Mun Jo Jung, KT, Korea. Today, I want to talk about KT NGN and its Mgt Plan with you. I am more than delighted and excited to have an opportunity for today’s talk at this beautiful place in Japan.

1 Conceptual View of KT NGN
Contents Introduction Conceptual View of KT NGN Development Plan for KT NGN Management System Initial KT NGN Management Closing Let me briefly go over what I will talk about during the course of this presentation. As shown on this slide, I will spend a little time on describing KT NGN in introduction part, followed by Conceptual view of KT NGN, Development Plan for KT NGN Management System and Initial KT NGN Management. And then I’ll close my presentation.

2 With Open Architecture
Introduction(1) Drivers for NGN Market Changes User Changes Business Trends : Voice to Multi-Media Wireless Service Increase Internet Application Expansion Paradigm Changes: Cyber society Wide Spread of Multimedia PC Mobile Multimedia Terminal Technology Mixed(voice + video + data) Service Need NGN Multi-service On Single Network With Open Architecture Service Logic Next Generation Network - Multi-service over Single Network Open Architecture Tera-grade traffic processing Intelligent Service PoP Business changes Technology changes So, to start off with this topic, what is NGN and why should it be required? To understand the question, we need to look into the current status of Telcos in the Telecommunication market. Most Telcos suffer from decrease in Revenue due to: ☞ Decrease in PSTN Traffic (affected by emergence of VoIP and Mobile Communication) ☞ Fierce Competition in Open Telecommunication Market And so they try to seek New Revenue Source through Multimedia by preparing for the integration of voice & data and the wired/wireless Convergence in All-IP architecture NGN has been considered as the vision of “broadcasting, information and communication anytime, anywhere, and in any form.” Many Telcos try to position themselves for radical transformation of their network and service infrastructures. It has become increasingly clear that a prerequisite for realization of such a vision is the convergence of the current multiple networks into a unified, multiservice, data-centric network, thereby offering variety of services at both different qualities and different costs on open service platforms. The evolution toward such a vision is undeniably influenced by the growing trends of deregulation in the telecommunications industry on one hand, and the rapidly evolving technological convergence between distributed computing and communications on the other hand. In a real sense, the necessary technological and environmental underpinnings exist today for next-generation service providers to start the transforming their infrastructures in ways that will enable provision of many new innovative services rapidly, economically, on a mass scale, and with improved quality control. Let’s see the drivers for NGN. We have four different views; Market changes, User changes, Technology changes and Businesses changes. In market changes, we find that the business trends move from voice centric services to multimedia services these days. We can use IMS, VoD, Video Phone service, etc. on the Internet. VoD is very important service in view of Telcos because Telcos have been focused on communication services so far. And the next one is Wireless services. They have become quite a force as more and more wireless terminals are spread among the public. New Internet Applications are being introduced and developed more than ever before to better our lives. Therefore, existing business paradigm is shifting toward Cyber World. In user changes, Multimedia PCs are widely spread into households. Users’ demands on new multimedia services are therefore dramatically increased. Under the demands, more mobile multimedia terminals are cheaply supplied and widely spread. In technology changes, High-speed optical network can be constructed with ease thanks to TSR, TES, WDM technology. Same service can be accessed through any media as Multi-Access technology is growing and service interfaces are open to any user. New services and business models can be created using open API. In business change, we need to avoid unnecessary multiple investments and cut the deployment/operation cost down. All these drivers predicate NGN’s emergence. New Service Network Architecture - Avoid Multiple Investment - Cut Deployment/Operation Cost Down New Service/ Business Model - Need Multi-Service over Single Net High-Speed Capacity Network - TSR, TES, WDM, etc Multi-Access Technology Growth - Any Media, but Same Service - Open API

3 Introduction(2) Network Provider  Service Provider
Technical Goal for NGN Construct Multi-Service Converged Network Integrated Wired and Wireless Services Differentiated QoS Support Easy and Fast Service Creation, Provisioning and Administration Open Architecture Supply Reusable Common Service Building Blocks Business Goal for NGN New Service Infrastructure for More Profits Cost-down in Network and Service Deployment and Operation Leading Edge in Competitive Telecom Market For More Business Opportunities Enlarge Business Area from Network to Service Draw More Customers Create More Services Enterprise Service Operator Other Network Operator Service Developer Now Let’s talk about goals for NGN. I’ll talk specifically about technical goal for NGN first. Old telecommunication networks have been usually designed for a specific service before. When new services required new features of the network, service deployment took more time to construct new network for them. In NGN, we will construct multi-service converged network to avoid them. Secondly, we need to integrate wired and wireless services for a unified service environment. The third goal is that the converged network should have control-mechanism on end-to-end quality of services to support differentiated QoS on each service. The fourth is to design NGN to support easy and fast service creation, provisioning and administration. The fifth is NGN should embrace open-architecture for easy deployment of new services. The sixth is to supply reusable common service building blocks. There are many reusable common functions such as subscription management, charging, connection control, etc. In a unified multiservice network, these functions help us develop new services fast with no trouble. Let’s move on to the business goal now. The primary goal for NGN in business perspective is to create a new service infrastructure for more profit. Single converged network can cut down the cost in network operation and construction. And it also gives great advantage in competitive telecommunication market to network providers. One more goal is to create more business opportunities. NGN can broaden Telcos’ business area. Network centric services like ADSL, VDSL, etc. can be transferred to new application services. NGN can draw more customers because new customer groups such as Enterprise Service Operators and Developers can use open APIs in NGN. Open architecture of NGN will help to create more services more easily. End User Network Provider  Service Provider

4 Conceptual View of KT NGN(1)
Service Layer DPE (Distributed Processing Environment) Service Coordination Layer Service Access Service Coordination Functionality Service Administration Network Layer Now let’s talk about Conceptual View of KT NGN. When we design the network, this kind of conceptual view helps us classify many network functions into several functional groups. And so we can work them out in details based on Group activities. We have three different layers in vertical view. They are Network Layer, Service Coordination Layer and Service Layer. We have three domains defined horizontally. These are Access Domain, Core Network Domain and Service Supporting Domain. Network Operation & Management Network Access Network Functionality Access Domain Core Network Domain Service Supporting Domain

5 Conceptual View of KT NGN(2)
For Easy Functional Grouping Three Layer Service Layer Service Coordination Layer and DPE Network Layer Three Domain Access Domain Functionality to be enriched Web-based Customer Portal Service Access Differentiated from Network Access Intelligent Terminal Capability Core Network Domain Functionality to be added Guarantee QoS Dynamic Resource Reconfiguration Manage Topology of Service Network Service Supporting Domain Functionality to be built in Service and Resource Administration QoS Management and Network OAM Let’s see a little more about Layers.   Service layer includes various applications like UMS, Voice conference and so on. Service Coordination Layer has many functions like mapping network resource in order to link network layer to service layer at desired service quality as well as service creation and administration function. Distributed Processing Environment will facilitate communication among servers. Access Domain can handle the process related to service subscription and access as well as network access. Different access types in both wired and wireless access, can be controlled and managed. Access speeds are also provisioned at different rate to meet the different demands of users. Web portal service for customers can be assigned to this domain. Secondly, Core Network Domain covers many functions to control and manage the core network to support various services. Policy management, bandwidth control and access aggregation are some examples. Thirdly, Service Supporting Domain is to support network management and service administration like service configuration, service registration, service deployment and so on, and also covers traditional network management functionalities as well.

6 Conceptual View of KT NGN(3)
Two-Step Approach for Sophisticated Services Authentication in Network Level in Service Level  from Per-Household to Per-Person Charging on Network Access on Service  Various Billing Strategies: Bundling Services, One Click As Service Coordination Layer supports many functions to map service requirements to the network requirements, we can single out many service instances from network. These functions enable us to handle a specific service independently from network access service and take two-step approach per-household and per-service. We have broadband access service, named MEGAPASS and NESPOT in Korea. These services are focused mainly on network access speed rather than service speed or service quality. The competitive market in network access speed as its own merit appears saturated already in Korea. And so they try to create new business models and deploy them on NGN. Competition in network access has progressed to that in service access and quality of more sophisticated services for user. For this, two-step approach in authentication and charging will be adopted to provide more differentiated and personalized services. From this approach, Authentication service moves from per-household to per-person. Charging capability allows us more flexibility in devising new charging plan for a bundling service.

7 Conceptual View of KT NGN(4)
Technical Trends Service Layer Unified Msg. Ser. VoD Ser. Cof. Ser. Medea Ser. Presence Ser. E-Commerce DPE(Distributed Processing Environment Service Access Service Coordination Functionality Service Administration Policy Service AAA Server Service Map User Profile Service Profile Terminal Capability Service Subscription Service Contract Service Invocation Service Bundling Customized Service One Stop Service Shop Service Driven Resource Management Service Mapping Function QoS Class aggregation Authentication Service Component Inventory Function Route/Topology Management Service Creation Service Provisioning Service Location Service Configuration Service Registration Policy Administration Profile Administration Service Assurance QoS Mgr Res. Mgr Ser. Cord. Terminal Intelligence Network Intelligence Ser. Call Control PG Accounting Network Access Network Functionalities Connectivity Transport with QoS Media Conversion Network Operation & Management MPLS Mobility Let’s review the technical trends before going into KT’s construction plan. First, let’s start off with quick reviews on each group of Layers and Domains we defined. In network access, user id/pwd in general is required in order to access network and its services. But enhanced capability in terminal’s end requires more information to access and use the service. Setting the terminal mode and optimal terminal configuration for a specific service is an example. Wire and wireless access are likely to be integrated as the technology becomes available. Next, let’s talk about some current tendencies in network functionality. One of them is that monolithic network elements are divided into component based network elements. TGW, AGW and SSW are examples of component based network elements. Wired network or wireless network tends to be unified. And best efforts IP network is enhanced to support QoS and user mobility. Diffser, MPLS, HLR and VLR for mobility service are the technologies for them. In network operation and management, new EMSs for SGW, AGW, TGW, SSW etc. may be introduced as well as NGN NMS. One of the most important layers is Service Coordination Layer between network layer and service layer. This layer offers many functions in guaranteeing QoS, mapping service requirements into network requirements, and administrating differentiated services. In Service Access, many customer services will be handled on one stop service portal and integrated customer portal. The access paradigm has taken a big leap from old office based service access and subscription. Now the big improvement lies in user profile and service profile handling, service subscription and invocation, terminal configuration, new service announcement. Many researches are being conducted on Service Coordination Functionalities, these days. QoS and resource mapping, policy generation, service level authentication, service session control and binding, service security and SLA processing are a few examples. Service creation, configuration, provisioning service assurance, and management functions are grouped in Service Administration. AGW SGW User ID/Pwd Terminal Registration Wired Access Wireless Access SSW Diff. Ser . TGW VPN NMS EMS EMS Monoliths Best Effort IP Network Wired Network Wireless Network Component-Based Network Elements IP Network with QoS Unified Network EMS

8 Development Plan for KT NGN Management
Service Coordination Layer Management: ~ 2006 Dynamic and Personalized Service Access Integrated Customer Portal One Stop Service Portal Advanced Service Administration Common Service Manager Common Network Resource Manager Easy Communication of Profiles Shared Information Base Network Layer Management: ~ 2005 For the Management of New NGN Components SoftSwitch Management System(SSEMS) NGN-NMS We have an active development plan for KT NGN Management in both Service Coordination Layer and Network Layer. Our study will be focused more on Service Coordination Layer Management. This is an emerging area to be settled down because of inexperience in the field. Basically, we categorized this layer into three functional groups for our convenience. They are Service Access for dynamic and personalized service with Integrated Customer Portal and One Stop Service Portal, and Advanced Service Administration with Common Service Manager, Common Network Resource Manager. To make easy communication between Service Access group and Service Administration group, we will build a Shared Information base for the profiles of services and subscribers. To support all these functions, we will develop two management systems in Network Layer. They are SSEMS and NGN-NMS. We will develop management systems for network layer first. It’s because we have more experience in Network Layer than Service Coordination Layer.

9 Service Coordination Layer Management(1)
Shared Information Integrated Customer Portal User Profiles & Security Unified Directory Operational Data Common Data Model BSS One Stop Service Portal Services Profiles Common Communication Bus (Java, CORBA, LDAP, SOAP/XML, SQL) Common Service Manager (QOS, Security, Resource) Policy Manager Security Manager Parlay Framework Common Network Resource Manager You can see the logical management architecture of Service Coordination Layer. I mentioned just before we have two portals deal with customer and service related date processing. And shared information stores common data related to user and service profiles, operational data and additional information. Common Service Manager handles QoS, Security, and Policy of Service. Common Network Resource Manager controls the resource allocation. Resource Allocation Manager Route / Topology Manager Common communication Bus (SIP, MGCP, SS7, LDAP, COPS, RADIUS, DIAMETER) Gateways Terminals NGN Network Equipment Application Server

10 Service Coordination Layer Management(2)
Integrated Customer Portal Enables End Users to Personalize Profiles and Subscribed Services Activates Selected Services Enables User or Group to Manage Others’ Roles under Security Policy Provides Single Sign-On Service to Access to Multiple Applications One Stop Service Portal Enables Service Operator to Announce Available Application Services Enables End Users to Purchase Application Services Let’s see the details on each functional component a little more. Integrated Customer Portal enables end users to personalize the profiles and subscribed services. It may also activate the selected service, It enables user or group to manage the role of group member under a security policy It may provide single sign-on service to access to multiple applications. One Stop Service Portal enables service operators to announce available services on the network. And also it enables end users to purchase the services they like.

11 Service Coordination Layer Management(3)
Common Service Manager Policy Manager Allows Creating, Checking, Storing and Querying Policy Rules Security Manager Handles Overall Security Capabilities for Service Environment. Parlay Framework Provides Service Creation and Administration Capabilities Common Network Resource Manager Resource Allocation Manager Provides Real-Time Activation Capabilities of Network, Application and Server Based on User Behavior, Profile and Quality of Service Manages Static/Dynamic Assignment of IP Addresses Route/Topology Manager Determines The Most Efficient Route for The Services. These Routes May Be Altered based on Current Network and Service State Common Service Manager has three components that consist of Policy Manager, Security Manager, and Parlay Framework. Policy manager allows creating, checking, storing and querying policy rules. It has the same role of policy server in general. Security Manager handles all the security functions for service environment. Parlay Framework provides service creation and administration capabilities. Common Network Resource Manager has two components, Resource Allocation Manager and Route/Topology Manager. Resource Allocation Manager provides real-time activation capabilities of network and service resources with quality of service. And it also manages static/dynamic assignment of IP addresses. Route/Topology Manager determines the most efficient route for the services. These routes may be altered based on current network and service state.

12 Network Layer Management(1)
Network Level Management Systems SoftSwitch Operation and Management Functions Management Functions within SoftSwitch FCAPS System Management, Operator Administration, EMS Communication Function Charging Function SSEMS Functions Manage Several SoftSwitches in A Region SoftSwitch Management Function: Configuration, Alarm, Performance, Statistics Resource Management of Managed Network Element: AGW, TGW, SGW etc. Subscriber Profile Management System/Operator Administration Interworking function b.w. SSEMS and SoftSwitch or NGN-NMS NGN-NMS Functions National wide NGN Management Function: Network Topology and so on Communicate to Multiple SSEMSes Network Resource Management: AGW, TGW, SGW and so on Interworking Function with Service Management Systems Let me proceed to Network Level Management Systems from now on. We are developing KT SoftSwitch and its management functions within SoftSwitch. Fault, configuration, account, performance and security functions are currently being developed. And many functions for system management and operator administration are being developed as well. We are also implementing SSEMS. This system manages multiple SoftSwiches and the network configuration data of many gateways in a region. NGN-NMS covers nationwide NGN management function. It communicates to multiple SSEMSes to share and control the managed information. It has the network resource control and management functions for AGW, TGW, SGW, etc. It has kinds of mediation function for interworking with service management systems in northbound of NGN-NMS.

13 Network Layer Management(2)
Zone 1 NGN NMS SSEMS SoftSwitch SoftSwitch AGW AGW-EMS Zone 2 미디어서버 TGW TGW-EMS SGW-EMS SGW SSEMS You can see the physical configuration of management systems in Network Layer. In a given management region, we have multiple EMSes like SSEMS, AGW-EMS, TGW-EMS, SGW-EMS and their managed components and one NGN-NMS to manage countrywide KT NGN. Interface b.w. SSEMS and NGN NMS Interface b.w. Gateway and its EMS Control Message b.w. SoftSwitch and Network Element Interface b.w. SoftSwitch and SSEMS Interface b.w. Gateway EMS and NGN NMS

14 Initial KT NGN Management: 2004 - 2005
Current Running Management Systems ICIS TIMS ANSWERS etc. BS Old Management Network Purchasing EMSs NGN-NMS SSEMS AGW-EMS TGW-EMS SGW-EMS KT development Management Network for NGN POTS AGW or AN MEGACO xDSL Access Network SIP IP-Phone This slide shows you initial KT NGN management architecture. We may reuse the current management systems such as ICIS, TIMS, ANSWERS, BS etc. to handle the subscription, the initial installation for customer access, the fault management in access network and billing related processing. AGW-EMS, TGW-EMS, and SGW-EMS are purchased and properly customized for the management of KT NGN. NGN-NMS and SSEMS are currently being developed to manage KT NGN and SoftSwitches The development of NGN-NMS, SSW, and SSEMS will be completed by the end of this year. MEGACO Control Network TGW PSTN Bearer KT SoftSwitch PSTN Interworking No. 7 Network SGW SIGTRAN Application Server Media Serve, etc. Servers AS, MS … AS, MS … AS, MS …

15 Initial KT NGN Management: 2004 - 2005
Initial NGN Management Access Domain One Stop Management from Subscription to Access Line Installation Using ICIS and TIMS TIMS Covers Access Line Installation Core Network Domain Automatic Profile Transfer to SoftSwitches Using ICIS, TIMS, NGN-NMS and SSEMS Partially Regional Management Based on TGW-EMS, SGW-EMS Service Coordination Layer Server or Component Based Management No Integrated Management among Servers or Components At initial NGN management, one stop management form subscription to access line installation with ICIS and TIMS will be possible. TIMS handles access line installation in Access Domain. Subscriber and service profiles will be automatically transferred to SoftSwitches from SSEMS through NGN-NMS. Although many studies are focused on Service Coordination Layer, it is likely to take more time to draw an optimal management solution out for this layer. Server-based, local management will be done at initial phase.

16 KT-NGN and Physical Configuration

17 Roadmap of KT-NGN Solution

18 Closing Why KT Chooses NGN?
Enlarging Business Areas More Business Opportunities Multi-Service Converged Network with QoS Easy and Fast Service Creation and Deployment Dynamic and Personalized Service Access  Less Investment More Return  Cost-Down in Network Operation Development Plan for KT NGN management System Service Coordination Layer Management: under Design Network Layer Management: under Development  Deploy Network Layer Management First  Sequentially Integrate Service Coordination Layer Management Systems Now I’d like to wrap up my presentation. We had a review on “Why KT chooses NGN?” It’s because we want to enlarge business areas to create more business opportunities to construct multi-service converged network with QoS to make service creation and deployment easy and fast to get dynamic and personalized service access. With NGN, we want to invest less for more return and to bring down the cost in network operation and construction. We are currently developing SSEMS and NGN-NMS. We are supposed to complete the development by the end of this year. And we’re also concentrating on our research on the design of Service Coordination Layer Management System now. After we deploy network layer management systems first, we’ll sequentially integrate Service Coordination Layer Management Systems. Thank you for your attention.

Download ppt "Conceptual View of KT NGN"

Similar presentations

Ads by Google