Virtual Transport Network Service
SDN-Based Optical Network Virtualization
Lyndon Ong
OIF MA&E Committee Co-Chair
Ciena, USA
Layer 123 NFV World Congress
Santa Clara, CA, USA
April 22, 2016
About the OIF
The Optical Internetworking Forum:
• Represents an end-to-end ecosystem
membership base of 100+ members
• Accelerating market adoption and
ROI for new technologies
• OIF 100G DWDM work united the industry
around a 100G framework and IAs for
photonics, FEC and module MSA
• Electrical work defines critical backplane,
chip and module interfaces for 100-400G
• Open and agile workplan
• Find gaps obstructing deployment and fill
them internally or working with other SDOs
• Distributed Control, Centralized Control –
whatever best fits operator needs!
www.oiforum.com
Network
Operators
System
Suppliers
Transceiver
Suppliers
Component
Suppliers
OIF’s Goals:
Transport SDN Toolkit
Essential tools for Transport SDN deployment
• Address carrier operations environment
• Brownfield as well as Greenfield
• Enable differentiated services
• Speed service development through standard network APIs
• Deliver scalability, security and high performance
• Hierarchical structure with mix of local and central functions
APIs
Services
SDN Architecture for Transport
Interoperability demos
Carrier Requirements
Transport Network Virtualization
Network resources dynamically allocated for high utilization
Resources can be partitioned into slices for service or user
Control exposed through open interfaces
→ Proprietary, vendor-specific silos
→ Complex to operate, integrate across
vendors/technologies
→ Logically centralized, vendor-agnostic
control and service orchestration
→ Virtualization of physical network resources
OSS Platform
Proprietary OS
Vendor X HW
Proprietary OS
Vendor Y HW
Proprietary OS
Vendor Z HW
Current Networks Software-Defined Networks
OSS Platform/SDN Apps
Virtualized Multi-vendor Multi-
domain Network
SDN SW
SDN-enabled
HW
Open APIs
Vendor EMS
SDN Control Infrastructure
OIF Virtual Network Service
Decomposition
Virtual networking service evolution
Each service type offers greater control
Fixed
Connection
Dynamic
Connection
Dynamic
Connection
Client
site A
Client
site B
Client site A
Client site B
Client site D
Client site C
Client site A
Client site B
Client site D
Client site C
Virtual network
with vNE & vLink
Client
controller
Ctrl of
virtual XC
Connection controlled
by network providers
Leased Line
Endpoints Only
Fixed virtual
network topology
Static
Dynamic Dynamic
Connection
Virtual network
with vNE & vLink
Client
controller Rent virtual network
resources from provider
Client site
Virtual network
recursive
creation
Client site
Client site
Client site
Client site
Client siteClient site
Dynamic/recursive virtual
network topology
OIF Service Definition
• Service Attributes
• Service Capabilities
• Recovery Requirements
• OAM Requirements
Harmonize Services Definitions for all players, i.e.
Transport Network Services
- Providers
- Users
- Equipment/SW Vendors
Working Protection
Request On Line
Real-time planning
Real-time setup
Autonomous Control
Dynamic expansion
Optimization
• Multi-level SLA
• Recovery
• Network migration
Seconds
Online
Goal: Network Slicing
Real Time
Open APIs
Robust Data Plane
Physical Optical Network
Virtual Network Topology
Network as a Service
Online Slicing
Path Computation
Survivability Analysis
Global Optimization
Tenants
T-SDN
Controller
SDN Virtualization Model
Multiple Client Contexts – resources and service endpoints
Controller does orchestration and virtualization of actual data plane
• https://www.opennetworking.org/images/stories/downloads/sdn-resources/technical-
reports/SDN_Architecture_for_Transport_Networks_TR522.pdf
• ONF Transport SDN Architecture – TR-522
7
SDN Parent Controller/App (Green)
Resource
Group 1
SDN Controller B
Server
Context
Server
Context
Client Context
CC m
NE1
Resource
Group 2
Server
Context
CC n
NE2
RG
B2
RG
B4
RG
B5
RG
B3
RG
B1
Data Plane
SDN Controller B
Client Context
NE NE NE
NE
NE
NE NE
NE
Orchestration and
Virtualization
SDN Controller C
Server
Context
Client Context
RG
B2
RG
B4
RG
B5
RG
B3
RG
B1
Transport API Development
• ONF Project closely coordinated with OIF work on VTNS
• Interface to a Transport Network Controller allowing access to Topology,
Connectivity, Virtualization and other services
• Functional Requirements in review, UML/YANG/JSON drafts available
• See https://github.com/OpenNetworkingFoundation/ONFOpenTransport
8
Topology
Service
Connectivity
Service
Path Computation
Service
Shared Network Information Context
Virtual Network
Service
Notification
Service
NENetwork Resource Groups
NENESDN Controller
NENESDN Controller
NENEApplication
Transport API
Transport API
SBIs (e.g. Openflow Optical)
Englewood Open
Source Project
• Bi-weekly Conference calls on
Wednesday at 6am California time
• OSSDN Englewood community web
page
• https://groups.opensourcesdn.org/wg/ENGL
EWOOD/dashboard
• Mailing list
(englewood@community.opensourcesdn.org)
• Documents
• Tasks
• Code submission on Englewood GitHub
https://github.com/OpenNetworkingFoundation/En
glewood
9
Participation is open to anyone, not only to ONF/OIF Members
Instance (e.g., ONOS, ODL)
T-API
PAL
APP1
Controller
3
Mapping
T-API interface
adapter
Restful
Handler 3
APP2
Demonstration Plans
Implementation Experience
• OIF/ONF Interop Demonstration
• 2016/17 Interop in planning
• Multiple carriers and vendors
expressing interest
• Equipment in carrier labs
• Optical and Ethernet switch
domains
• Variety of controllers
• Heterogeneous network
• Higher level orchestration
across domains
• Common T-API between
orchestration and controller
2014 Demonstration
Summary
• Virtualization of the Optical/Transport Network
• Standardized APIs to access transport services
• Cooperating SDOs and Open Source development
• Demonstration(s) planned

Virtual Transport Network Service SDN-Based Optical Network Virtualization

  • 1.
    Virtual Transport NetworkService SDN-Based Optical Network Virtualization Lyndon Ong OIF MA&E Committee Co-Chair Ciena, USA Layer 123 NFV World Congress Santa Clara, CA, USA April 22, 2016
  • 2.
    About the OIF TheOptical Internetworking Forum: • Represents an end-to-end ecosystem membership base of 100+ members • Accelerating market adoption and ROI for new technologies • OIF 100G DWDM work united the industry around a 100G framework and IAs for photonics, FEC and module MSA • Electrical work defines critical backplane, chip and module interfaces for 100-400G • Open and agile workplan • Find gaps obstructing deployment and fill them internally or working with other SDOs • Distributed Control, Centralized Control – whatever best fits operator needs! www.oiforum.com Network Operators System Suppliers Transceiver Suppliers Component Suppliers
  • 3.
    OIF’s Goals: Transport SDNToolkit Essential tools for Transport SDN deployment • Address carrier operations environment • Brownfield as well as Greenfield • Enable differentiated services • Speed service development through standard network APIs • Deliver scalability, security and high performance • Hierarchical structure with mix of local and central functions APIs Services SDN Architecture for Transport Interoperability demos Carrier Requirements
  • 4.
    Transport Network Virtualization Networkresources dynamically allocated for high utilization Resources can be partitioned into slices for service or user Control exposed through open interfaces → Proprietary, vendor-specific silos → Complex to operate, integrate across vendors/technologies → Logically centralized, vendor-agnostic control and service orchestration → Virtualization of physical network resources OSS Platform Proprietary OS Vendor X HW Proprietary OS Vendor Y HW Proprietary OS Vendor Z HW Current Networks Software-Defined Networks OSS Platform/SDN Apps Virtualized Multi-vendor Multi- domain Network SDN SW SDN-enabled HW Open APIs Vendor EMS SDN Control Infrastructure
  • 5.
    OIF Virtual NetworkService Decomposition Virtual networking service evolution Each service type offers greater control Fixed Connection Dynamic Connection Dynamic Connection Client site A Client site B Client site A Client site B Client site D Client site C Client site A Client site B Client site D Client site C Virtual network with vNE & vLink Client controller Ctrl of virtual XC Connection controlled by network providers Leased Line Endpoints Only Fixed virtual network topology Static Dynamic Dynamic Connection Virtual network with vNE & vLink Client controller Rent virtual network resources from provider Client site Virtual network recursive creation Client site Client site Client site Client site Client siteClient site Dynamic/recursive virtual network topology
  • 6.
    OIF Service Definition •Service Attributes • Service Capabilities • Recovery Requirements • OAM Requirements Harmonize Services Definitions for all players, i.e. Transport Network Services - Providers - Users - Equipment/SW Vendors
  • 7.
    Working Protection Request OnLine Real-time planning Real-time setup Autonomous Control Dynamic expansion Optimization • Multi-level SLA • Recovery • Network migration Seconds Online Goal: Network Slicing Real Time Open APIs Robust Data Plane Physical Optical Network Virtual Network Topology Network as a Service Online Slicing Path Computation Survivability Analysis Global Optimization Tenants T-SDN Controller
  • 8.
    SDN Virtualization Model MultipleClient Contexts – resources and service endpoints Controller does orchestration and virtualization of actual data plane • https://www.opennetworking.org/images/stories/downloads/sdn-resources/technical- reports/SDN_Architecture_for_Transport_Networks_TR522.pdf • ONF Transport SDN Architecture – TR-522 7 SDN Parent Controller/App (Green) Resource Group 1 SDN Controller B Server Context Server Context Client Context CC m NE1 Resource Group 2 Server Context CC n NE2 RG B2 RG B4 RG B5 RG B3 RG B1 Data Plane SDN Controller B Client Context NE NE NE NE NE NE NE NE Orchestration and Virtualization SDN Controller C Server Context Client Context RG B2 RG B4 RG B5 RG B3 RG B1
  • 9.
    Transport API Development •ONF Project closely coordinated with OIF work on VTNS • Interface to a Transport Network Controller allowing access to Topology, Connectivity, Virtualization and other services • Functional Requirements in review, UML/YANG/JSON drafts available • See https://github.com/OpenNetworkingFoundation/ONFOpenTransport 8 Topology Service Connectivity Service Path Computation Service Shared Network Information Context Virtual Network Service Notification Service NENetwork Resource Groups NENESDN Controller NENESDN Controller NENEApplication Transport API Transport API SBIs (e.g. Openflow Optical)
  • 10.
    Englewood Open Source Project •Bi-weekly Conference calls on Wednesday at 6am California time • OSSDN Englewood community web page • https://groups.opensourcesdn.org/wg/ENGL EWOOD/dashboard • Mailing list ([email protected]) • Documents • Tasks • Code submission on Englewood GitHub https://github.com/OpenNetworkingFoundation/En glewood 9 Participation is open to anyone, not only to ONF/OIF Members Instance (e.g., ONOS, ODL) T-API PAL APP1 Controller 3 Mapping T-API interface adapter Restful Handler 3 APP2
  • 11.
    Demonstration Plans Implementation Experience •OIF/ONF Interop Demonstration • 2016/17 Interop in planning • Multiple carriers and vendors expressing interest • Equipment in carrier labs • Optical and Ethernet switch domains • Variety of controllers • Heterogeneous network • Higher level orchestration across domains • Common T-API between orchestration and controller 2014 Demonstration
  • 12.
    Summary • Virtualization ofthe Optical/Transport Network • Standardized APIs to access transport services • Cooperating SDOs and Open Source development • Demonstration(s) planned