Page History

...

Contributors

Overview

ACTN refers to the set of virtual network operations needed to
orchestrate, control and manage large-scale multi-domain TE networks
so as to facilitate network programmability, automation, efficient
resource sharing, and end-to-end virtual service aware connectivity
and network function virtualization services.

...

      . CNC - Customer Network Controller - 
      . MDSC - Multi Domain Service Coordinator -  
      . PNC - Physical Network Controller - 

Customer Network Controller

A Virtual Network Service is instantiated by the Customer Network
Controller via the CMI (CNC-MDSC Interface). As the Customer Network
Controller directly interfaces the application stratum, it
understands multiple application requirements and their service
needs. It is assumed that the Customer Network Controller and the
MDSC have a common knowledge on the end-point interfaces based on
their business negotiation prior to service instantiation. End-point
interfaces refer to customer-network physical interfaces that
connect customer premise equipment to network provider equipment.
In addition to abstract networks, ACTN allows to provide the CNC
with services. Example of services include connectivity between one
of the customer's end points with a given set of resources in a data
center from the service provider.

...

Physical Network Controller

The PhysicalNetworkController is PhysicalNetworkControlleris the one in charge of configuring
the network elements, monitoring the physical topology of the
networkandpassing it, either raworabstracted, to the MDSC.

The PNC, in addition to being in charge of controlling thephysical
network, is able to implement two of the four ACTN main
functionalities: multi domain coordination function and
virtualization/abstraction function
A hierarchy of PNCs can be foreseen for scalability and
administrative choicesadministrativechoices.

IETF ACTN architecture, YANG models and PCE-P protocols for NBI

• ACTN Requirements https://datatracker.ietf.org/doc/draft-ietf-teas-actn-requirements/
• ACTN Framework https://datatracker.ietf.org/doc/draft-ceccarelliietf-teas-actn-framework/
  

Implementing ACTN in ONOS

via Yang (RestConf / gRPC etc)

• framework/
  
  
• TE Topology YANG model Generic Info ModelforACTN-https://datatracker.ietf.org/doc/draft-leebelottiietf-teas-yang-actnte-infotopo/
• TE Topology based on Tunnel YANG model https://datatracker.ietf.org/doc/draft-ietf-teas-yang-te-topo/TE Tunnel based on
• Service YANG model https://datatracker.ietf.org/doc/draft-ietfzhang-teas-transport-yangservice-te/

  ACTN extension are needed to extend/augement these models

via PCEP

Image Removed

Image Removed

Image Removed

Supporting VN operations in PCEP for ACTN

Image Removed

• model/
• OTN Service YANG model https://datatracker.ietf.org/doc/draft-sharma-ccamp-otn-service-model/
• WSON YANG model https://datatracker.ietf.org/doc/draft-ietf-ccamp-wson-yang/
  
  
• Stateful PCE https://datatracker.ietf.org/doc/draft-ietf-pce-stateful-pce/
• LSP State Synchronization for Stateful PCE https://datatracker.ietf.org/doc/draft-ietf-pce-stateful-sync-optimizations/
• Hierarchical PCE https://datatracker.ietf.org/doc/draft-ietf-pce-hierarchy-extensions/
• PCEP-LS extensions Stateful H-PCE https://datatracker.ietf.org/doc/draft-dhodylee-pce-statefulpcep-hpcels/
• PCEP-VN Association extensions https://datatracker.ietf.org/doc/draft-leedhody-pce-vn-association/
  
  

ACTN Project Development Overview

Image Added

Hierarchical Topology Abstractions via Standard NBIs

Image Added

VN (Virtual Network) Creation via PCEP

Image Added

Image Added

Image Added

Supporting VN operations in PCEP 

Image Added

JIRA Tickets

IETF YANG NBI/SBI       

ACTN MDSC Controller