Bell Labs Stepwise development of ONOS controlled …...4 Bell Labs Towards Software Defined Optical...
Transcript of Bell Labs Stepwise development of ONOS controlled …...4 Bell Labs Towards Software Defined Optical...
1 Restricted © Nokia 2018 Bell Labs
Bell Labs
Stepwise development of ONOS controlled
Open Disaggregated Transport Networks
D. Verchere, Q. Pham Van, G. Atkinson, M. Thottan, A. Mayoral, O. Gonzales de Dios, V. Lopez ONF Connect’2018 Conference December 4th - 6th 2018 – Santa Clara - CA
Networks are in the middle of a massive transformation…
« Optical networking is transforming and is expanding everywhere »
Edge Metro Regional Global
METRO COLO/ DATA
CENTERS
REGIONAL CLOUD DATACENTERS
ENTERPRISE IT/DATA CENTERS
GLOBAL CLOUD DATA
CENTERS
INTERNET EXCHANGE CO/POP COLO / DC DC /EXCHANGE
Internet
Enterprise Cloud &
DC
Mobile
Business/DC
Internet of Things
Residential
CSP ICP MNO CNP DSP ENT
3 Bell Labs
… towards Automation & Abstraction Virtualization
Optical Channels controlled as Services
Hierarchical
End-to-end service-enabled relationships
Consumable
Automated deployment, fulfillment & assurance
Multi-tenant
Restricted
Optical Network Infrastructures
Transport Slice Transport Slice
E2E network slice E2E network slice E2E network slice
How can Control Platforms support Transport Network Transformation?...
4 Bell Labs
Towards Software Defined Optical Channels
Enterprise #1
Enterprise #2
Datacenters
OTN switch Flexi-rate board
SDN Controller
optical node #2
node #1 node #n « Set and Forget »
configuration
Fixed Optical Network
Configuration
optical node #2
node #1 node #n
« Set and Forget » Manual configuration
Fixed Optical Network
Configuration
TODAY COMING SOLUTIONS
Define/try and continuously adjust configuration Setting with just-required performance Fast delivery of optical channels on application demand Multi Vendor Optical Systems
Optical channel configuration never changed Guaranteed setting with large margins Deployment of services in months Single Vendor Optical Systems
« Programmable » Automatic Reconfiguration
ITU-T Fixed Grid Flexible ITU Grid
50Ghz 50Ghz
200Gbs 100Gbs 10Gbs 40Gbs 100Gbs 200Gbs
37.5Ghz 50Ghz 25Ghz 12.5Ghz 50Ghz Frequency granularity
Frequency granularity
6.25Ghz
50Ghz
50Ghz 40Gbs 10Gbs
Spectrum occupancy gain
ONOS
5 Bell Labs
Proprietary interfaces
REST
From where do Operators start … … opening and unleashing their Transport Network infrastructures?
BSS / OSS
NMS (i.e., X_NMS)
TerminalDeviceVendor_X ROADMVendor_X
Deployed (now)
No Disaggregated – Proprietary
NMS (i.e., X_NMS)
Proprietary interfaces NETCONF/OpenConfig
BSS / OSS
Orchestrator (Service)
SDN Controller (Resource) RESTCONF/TAPI
RESTCONF/TAPI
REST
REST
Brownfield deployment (short term)
TerminalDeviceVendor_Y ROADMVendor_X
Partially Disaggregated
TerminalDeviceVendor_X
6 Bell Labs
NMS (i.e., X_NMS)
Proprietary interfaces NETCONF/OpenConfig
BSS / OSS
Orchestrator (Service)
SDN Controller (Resource) RESTCONF/TAPI
RESTCONF/TAPI
REST
REST
Brownfield deployment (short term)
TerminalDeviceVendor_Y ROADMVendor_X
Partially Disaggregated
TerminalDeviceVendor_X
From Partially to Fully Disaggregated Transport Network infrastructures Open-Source SDN framework based Network Control Platforms
Greenfield deployment (mid/long term)
Fully Disaggregated
REST
BSS / OSS
Orchestrator (Service)
SDN Controller (Resource)
TerminalDeviceVendorXorVendor_Y
RESTCONF/TAPI
NETCONF/OpenConfig
REST Intent Monitoring FW
NMS
ROADMVendorXorVendor_Y
SDN Apps
Proprietary interface Streaming telemetry
7 Bell Labs
Configuration & Controlled of Pairs of Transponders – ODTN Phase 1.0 Integration and 1st demonstration at Telefónica lab completed – August 2018
© NOKIA 2018
NETCONF/OpenConfig to configure NOKIA transponders
ONOSController
Pre-configured Optical Channel (OCh)
100G 100G
Transport API 2.0.2 / RESTCONF ONOS translates Transport-API connectivity service request
into NETCONF/OpenConfig <edit-config> to
configure transponder devices
T-API based service request (Connectivity service request)
Line Port Line Port
Client Port Client Port
Transponder_2 Transponder_1
PSI-2T PSI-2T
8 Bell Labs
T-API / RESTCONF (Connectivity & Topology services) ver. 2.1
ROADM ROADM ROADM ILAMP ROADM
ROADM ROADM
Transponder_2
Partially Open Disaggregated Network Control Platform Architecture Brownfield deployment - ODTN Project Phase 1.5*
© NOKIA 2018
NETCONF/OpenConfig to configure transponder ports
ONOSController
Open Line System (OLS)
100G 100G
Transponder_1
ServiceOrchestrator
Dynamic Config
Subsystem
Transport API / RESTCONF (ver. 2.1)
Service Application
Service Application translates T-API /Connectivity service to
OLS Controller and to NETCONF/OpenConfig for terminal devices (Transponders)
Line Port Line Port
OLS Controller* Networktopologyexposurecontrol
Client Port Client Port
Provideconnectivityservice
* On going …
T-API service request (Connectivity services)
OLS Controller translates T-API service requests and
configures/controls optical devices (ROADMs, ILAs, MUX, etc.)
9 Bell Labs
Transport API / REST (ver. 2.1)
Transponder_2 Transponder_1
Fully Open Disaggregated Network Control Platform Architecture Greenfield deployment – ODTN Phase 2.0
© NOKIA 2018
ONOSController
Meshed Optical Network Domain
100G 100G
ServiceOrchestrator
Dynamic Config
Subsystem
TransportPCE translates T-API service requests to NETCONF/OpenConfig commands to configure &
control directly Optical devices: Transponders, ROADMs InLineAmplifiers, MUX/DEMUX etc.
T-API service request (Connectivity & Topology services)
Line Port Line Port
ROADM ROADM ROADM ILAMP
ExposedNetworktopologyanddeliversconnectivityservices
NETCONF/OpenConfig to configure wavelength routers Client Port Client Port
Service Application
ROADM
ROADM ROADM
PSI-2T PSI-2T
NETCONF/OpenConfig to configure transponders
10 Bell Labs
• Brownfield Deployments – ODTN Phase 1.5 - TAPI for ONOS South Bound Interface - ONOS Controller / OLS Controller exchange sequences for Optical Channel provisioning
What need to be considered/studied in ONOS Software Next steps on ODTN Phase 1.5
Confidential and Proprietary © Nokia 2018
OLS Controller
Proprietary interfaces NETCONF/OpenConfig
BSS / OSS
Orchestrator (Service)
ONOS RESTCONF/TAPI
RESTCONF/TAPI
REST
REST
TerminalDeviceVendor_Y ROADMVendor_X TerminalDevice
Vendor_X
OLS Controller
ONOS RESTCONF/TAPI
11 Bell Labs
• Greenfield Deployments – ODTN Phase 2.0 - OpenConfig model extensions
• Optical device and link discovery / auto-discovery
- Optical Channel abstraction in ONOS Topology Manager • TE attributes must be defined and then added
- From IETF/I2RS, TAPI 2.1+ extensions, etc.
- First attributes: Power, OSNR, CD, PMD, etc.
- Optical channel feasibility computation: • How are Physical impairments used?
• Which Physical Simulation Engine(s)?
- And more …
What need to be considered/studied in ONOS Software After ODTN Phase 1.5
Confidential and Proprietary © Nokia 2018
REST
BSS / OSS
Orchestrator (Service)
ONOS
TerminalDeviceVendorXorVendor_Y
RESTCONF/TAPI
NETCONF/OpenConfig
REST Intent Monitoring FW
NMS
ROADMVendorXorVendor_Y
SDN Apps
Proprietary interface Streaming telemetry
12 © Nokia 2018
Confidential
Many Thanks to:
• NOKIA Bell Labs colleagues,
• NOKIA IP/Optical Networks colleagues,
• SENDATE CELTIC-Plus Project
• ONF ODTN Project members …
This work has been partially supported by French government through SENDATE –TANDEM project
13 Bell Labs
Comprehensive Network Control approach for Open Line Systems
1. Control Agents on Devices • NETCONF, gRPC, • OpenConfig models
3. Control Apps and Orchestration • Assurance, e2e coordination • Service Management & Deployment
2. SDN Controller (Customized) • ONOS-based platform • TAPI NBI and NETCONF SBI
4. System Integration • Integration, Performance validation • Troubleshooting , management,
inventory
Orchestrator, IP, NFV
Open SBI model
Open NBI model
SDN Controller
Vendor X
Vendor Y
ROADM ROADM OT
OT
OT
OT
Control Apps
OT
OT
OT
OT
Optical Terminals
ROADM (NOKIA, 3rd party)
1
3 3
2
4
TAPI