2015
DOI: 10.1109/jlt.2015.2393634
|View full text |Cite
|
Sign up to set email alerts
|

Transport Network Orchestration for End-to-End Multilayer Provisioning Across Heterogeneous SDN/OpenFlow and GMPLS/PCE Control Domains

Abstract: A multidomain optical transport network composed of heterogeneous optical transport technologies (e.g., flexi/fixedgrid optical circuit switching and optical packet switching) and control plane technologies (e.g., centralized OpenFlow or distributed GMPLS) does not naturally interoperate, and a network orchestration mechanism is required. A network orchestrator allows the composition of end-to-end network service provisioning across multidomain optical networks comprising different transport and control plane … Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1

Citation Types

0
26
0

Year Published

2016
2016
2023
2023

Publication Types

Select...
7
2
1

Relationship

2
8

Authors

Journals

citations
Cited by 56 publications
(26 citation statements)
references
References 14 publications
(15 reference statements)
0
26
0
Order By: Relevance
“…23. The application-based network operations (ABNO) based SDN multilayer orchestrator [436] receives the physical topology information from the OpenFlow/GMPLS controllers. The orchestrator centrally computes paths and sends the path information to the lower level controllers for path provisioning.…”
Section: B Multidomain Orchestrationmentioning
confidence: 99%
“…23. The application-based network operations (ABNO) based SDN multilayer orchestrator [436] receives the physical topology information from the OpenFlow/GMPLS controllers. The orchestrator centrally computes paths and sends the path information to the lower level controllers for path provisioning.…”
Section: B Multidomain Orchestrationmentioning
confidence: 99%
“…3, follows the open network foundation (ONF) architecture using three main interfaces [16]: the application-controller plane interface (A-CPI) between the control plane and the application (a user portal in this case); the intermediate-controller plane interface (I-CPI) between the network orchestrator (NetO) [17] and the node controller (NC) and core network controller (OF); and the device-controller plane interface (D-CPI) between the controllers and the physical devices [4].…”
Section: Sdn Architecture and Pon Protocolmentioning
confidence: 99%
“…The southbound interface takes care of the intent installation by translating the installable operations into protocol procedures sent to the network. We leverage OpenFlow, OVSDB and YANG descriptions, [5] in combination with HTTP as a REST protocol and extensions to support encryption when available. Fig.…”
Section: Architecturementioning
confidence: 99%