Transport PCE


Transport PCE is an application running on top of the OpenDaylight controller. Its primary function is to control an optical transport infrastructure using a non-proprietary South Bound Interface (SBI).

The controlled transport infrastructure includes a WDM (Wave Division Multiplexing) layer and an OTN (optical transport network) layer. The WDM layer is built from ROADMs (reconfigurable optical add-drop multiplexer) with colorless, directionless and contention-less features. The OTN layer is built from transponders, muxponders or switchponders which include OTN switching functionalities.

Transport PCE leverages OpenROADM Multi-Source-Agreement (MSA), which defines interoperability specifications, consisting of both optical interoperability and YANG data models.

The TransportPCE implementation includes:

Transport PCE implementation



Northbound API

These APIs are for higher level applications, implemented in the Service Handler bundle. It relies on the service model defined in the MSA. A minimal experimental support of TAPI topology is also proposed but is not installed by default.

Renderer and OLM

The renderer and OLM (Optical Line Management) bundles allow configuring OpenROADM devices through a southbound NETCONF/YANG interface (based on the MSA device models). This release supports the OpenROADM devices version 1.2.1 version 2.2.1.

Topology Management

This feature is based on the defined MSA network model.

Path Calculation Engine (PCE)

PCE here has a different meaning than the BGPCEP project since it is not based on (G)MPLS. This bundle allows to compute path across the topology to create services. Impairment aware path computation can be delegated to a GNPy server (hardcoded server address configuration and limited support at that time)


This feature is not installed by default. It proposes an experimental support for an external inventory DB currently limited to 1.2.1 OpenROADM devices.

The internal RPCs between those modules are defined in the Transport Service Path models.

Behavior/Feature Changes

This release introduces the following behavior changes:

New Features

This release provides the following new features:

  • OTN end-to-end service creation directly from the NorthBound API.

  • experimental introduction of Flex-Grid (TRNSPRTPCE-253).

Resolved Issues

The following table lists the resolved issues fixed this release.




Adding SAPI/DAPI to Renderer


UUID stabilization in TAPI Topology abstractio


Fix TAPI execution NPE


SpanLoss uses now BigDecimal and is better handled


OTN link update issue


Missing modulation format for 2.2.1 OCH interface

Known Issues

The following table lists the known issues that exist in this release.




Handling Port capabilities in topology


TAPI Karaf feature can cause heap memory size issues. The heap memory size can be increased at Karaf start-up to palliate this problem.