ONOS OPTICAL SERVICE – ODU CROSS CONNECT PROPOSAL Aliza Nagauker Rimon Ashkenazy (19/01/2016)

2 AGENDA Optical Use Case support of ODU-Cross Connect General Topology OTN Device & OTU ports Intent Resource Management ONOS Tasks Breakdown Procedures and Open Issues

ONOS OPTICAL SERVICE – ODU CROSS CONNECT

4 OPTICAL SERVICE WITH ODU-CC - GENERAL Optical service configuration with ODU Cross Connect Based on current onos-optical-app Optical service which already supports ODU-Multiplexing on Edges Optical Extension (for flows and port description) Service with ODU CROSS CONNECT assumes PATH with OTN Devices only All OTN devices has ODU Cross Connect Capabilities ODUCLT can be mapped to any OTU port on Device Tested with ECI Optical Equipment

5 TOPOLOGY: GENERAL USE CASE TOPOLOGY Following elements are considered in this use case SW - ETH NEs OTN – Optical NE with ODU CC capabilities Optical Links The different optical links types are identified by the type of the ports

6 TOPOLOGY: DEVICE & PORTS NE with ODU Cross Connect Capabilities are reported to ONOS CORE as OTN DEVICES OFOpticalDriver13 is used for the Handshake with these elements Function deviceType() returns ROADM/OTN based on “hw-version” field hw-version == “Optical-ROADM”  ROADM hw-version == “Optical-OTN”  OTN This NE has the following port types ODUCLT port Reported as ETH ports and forwarded to ONOS Core as ODUCLT ports (same behavior as in ROADM) OTU port (New) Reported as part of Experimenter Multipart Request/Reply (Optical Transport Protocol Extensions 1.0) Port Signal Type = OTU2/OTU4, Layer Class = ODU, Layer Signal Type = ODU2/ODU4 Note: OTU port in ONOS model is similar to ODUCLT (includes only SIGNAL Type)

7 TOPOLOGY: LINKS OTU Links LINKS between OTN NEs SRC & DEST Port types are - OTU OTU Links are configured through topo file Link.type=OPTICAL Applications identifies this link as OTU link according to the ports types Same behavior is in any other optical links (oms  oms, eth  oduclt) Link between SW to Optical Devices (previously known as cross- connect links) LINKS that are connecting ETH NEs with OPTICAL NEs (either ROADM, OTN) The port connected to the Optical NE is considered as ODUCLT

8 OPTICAL APP & INTENTS (1) Service configuration is based on optical app & optical intents OpticalODUIntent – New Intent Creates ODU CC Optical application creates this new intent if the oduClts ports on OTN Device OpticalODUIntent Find paths (srcNE, dstNE, Weight) over OTN Links (Source and Dest are OTU ports) Weight Function per ODU Signal Type (ODU0/ODU2/ODU4): Link.state = active, link.type=optical Allocate TS over OTU Ports in PATH If there are no available resources over PATH, go to the next path

9 OPTICAL APP & INTENTS (2) OpticalODUIntent – Cont’ Configure rules Source Edge NE Match: In port, Odu SigType Action: Odu SigID, output port (oduSigID according to the TS allocation of the “output port”) Transition NE Match: In port, Odu SigType, Odu SigID (oduSigID according to the TS allocation of the “In port”) Action: Odu SigID, output port (oduSigID according to the TS allocation of the “output port”) Dest Edge NE Match: In port, Odu SigType, ODU SigID (oduSigID according to the TS allocation of the “In port”) Action: Output port NOTE: if the whole OTU port is used no TS are indicated in the action/match

10 RESOURCE MANAGEMENT – TS OVER OTU PORT Use New Resource Management For OTU Port Query and register TributarySlots for OTU ports Resource allocation – over path Returns TS Allocation for each PORT in the path Different TS may be returned for each Port

ONOS TASK BREADOWN

12 ONOS: TASK BREADOWN OTU port ONOS-OF-DEVICE PROVIDER ONOS OTU Data model OTU Port Resource Management NEW RESOURCE MANAGEMENT ONOS INTENTS OpticalODUIntent CLI – AddOpticalIntent is modified to support creation of OpticalODUIntent Optical Application – Create OpticalODUIntent if the “cross- connect” ports are on OTN devices

THANK YOU!