Upload
vuongkhanh
View
216
Download
0
Embed Size (px)
Citation preview
Carrier/WAN SDN Commercially Deployed Transport SDN Platform in Action
Features Open Source SDN Software
Carrier/WAN SDN
Challenges & Solution
• [challenge] Complex transport network
environment having multi-
vendor/domain/layer devices
– Controls are closed and distributed over
vendor specific EMSs
• [Solution] Centralize device control and
PCE over multi-vendor devices
Features Open Source SDN Software
T-SDN EMS EMS
MSPP
(A vendor)
MSPP
(B vendor)
OXC
(C vendor)
PTN
(D vendor)
EMS EMS
MSPP
(A vendor)
MSPP
(B vendor)
OXC
(C vendor)
PTN
(D vendor)
EMS EMS EMS
Centralized
Control
E2E Service Provisioning
30% OPEX saving
Carrier/WAN SDN
Challenges & Solution
• [challenge] OPEX increase by
segmented operations
– For E2E service configuration, many
domain operators should participate
– Delayed service deployment
because of manual planning &
provisioning
• [Solution] Simplify and automate
provisioning processes using T-SDN
Receive Order
Path Planning
Provisioning
Svc. Order
Completion
T-SDN
One-Stop
One-Control Receive Order
Path Planning
BSS
Send Work Order to
each domain
Provisioning
Order
Completion
Provisioning
Order
Completion
Svc. Order
Completion
Sys#1
(Order Mgr.)
Sys#2
(Facility Mgr.)
Sys#3
(Work Mgr.)
Sys#4
(EMS)
Sys#3
(Work Mgr.)
Sys#3
(Work Mgr.)
95% Time reduction
Carrier/WAN SDN
Our Architecture
MD-SAL
OSGi Framework
Karaf runtime Data Store
(In-Memory)
Data Broker Clustering Mgr.
PCE Provisioning Path
Designer Topology Mgr.
Inventory Mgr.
Service Functions Service Mgr.
OpenFlow NetConf Corba
SB Protocol Plugins
Northbound API(RESTfull)
Resource
DB
(SQL)
Event Mgr.
Fault Mgr.
GUI
RCA
Statistics
Web Browser Client
Socket
TL-1 SNMP
Client Mgr.
Fault Manager(Legacy NMS) T-SDN Platform
GW Server
AP Server
Client
Controller
3rd Party App • Adopted open source SDN controller
(OpenDaylight Helium Release) – To reduce time and cost for
development
• Integrated with legacy transport NMS – share inventory, topology, and fault
information
• Define Yang Model and use in-memory DataStore for fast path computation – Real-time synchronization for resource
changes
• Adopted MSPP, OXC, and PTN plugins
Carrier/WAN SDN
Demo Scenario I
• Mutually Exclusive Ethernet Path Computation with Service ID
– Using existing service ID, PCE can compute new path for survivability of customer service
Existing Path
New Path MSPP
(A vendor)
MSPP
(B vendor)
MSPP
(B vendor)
MSPP
(A vendor)
OXC
(C vendor)
OXC
(C vendor)
OXC
(C vendor) OXC
(C vendor)
Carrier/WAN SDN
• PTN E-LAN Path Computation over multi-administrative domain
– Automatically compute tree-like optimal PseudoWire Path considering PCE conditions such as
hop count, resource availability, load balancing, etc.
A Domain B Domain
LH LH
C Domain
VSI(Virtual Switching Instance)
PW Path
ROADM
PTN
Demo Scenario II
Thanks for your interest!
Peter Park, kt ([email protected])
JungHyo Lee, kt ([email protected])
ChanKyu Hwang, kt ([email protected])
Carrier/WAN SDN
About Korea Telecom
• KT is leading the development of the information and communications industries of Korea since its
foundation in 1981.
• Providing the fastest and most innovative ICT-based telecommunications and convergence services
such as Cloud, IPTV, VoIP, 4G LTE, Broadband, and Fixed Lines.
• Having the largest network infrastructure including Fixed, Mobile, Broadband, Cloud, and etc.
Telephone
20 Million
Broadband
8.2 Million
IPTV
6.3 Million
Biz Ucloud Home Giga WiFi
Mobile
18 Million
Carrier/WAN SDN
Our Solution
• Adopted open source SDN controller (OpenDaylight Helium Release)
– To reduce time and cost for development
– Could get valuable ideas from open source community
– But, why OpenDaylight?
• Stable code started from 2013 and applied to over 34 solution providers
• Many contributors from dominant vendors that can help our plugin adoption for their system
• Simplified and automated E2E service provisioning process
– Optimal Path Calculation over multi-vendor devices
– Visualized Service Planning with map
– Process Automation with BSS/OSS
Carrier/WAN SDN
Concluding Remarks
• T-SDN architecture should be hybrid approach
– cannot avoid dependencies on vendors to cover legacy network
– need vendors’ support for southbound plugins
• Open source SDN controller is helpful for fast and low-cost implementation
– From our views, OpenDaylight is more appropriate for T-SDN
• But, need to develop domain specific applications considering business requirements
– For example, extension of Yang Model for fast PCE
• KT T-SDN will be commercialized in Nov. 2015
– Nationwide deployment in Jan. 2016