The Network eAcademy team initially focused on identifying a service architecture that could allow the creation of new services and workflows and that could be shared within the community in a multi-domain fashion with a corresponding orchestration process, in order to use it as a blueprint for a common framework.
In order to select suitable architecture candidates that could fit the community needs, and investigation on available architectures that aimed to solve all or some of the aspects of OAV was performed and commonalities in terms of module functionalities, APIs and data models were identified. This work was followed by a cross comparison with existing proprietary solutions in the community that could lead to harmonisation in the multi-domain environment. The initial list of analysed architectures, together with the links to their respective websites can be find below.
The work ended up with the selection of the TM Forum Open Digital Architecture (ODA, (link to the “ODA - Open Digital Architecture (TM Forum)” section)) as the functional architecture to be used as blueprint where other architectures are being mapped (link to the “Mapping Use Cases” section).
Initial list of identified architectures related to OAV
For more information on investigated architectures please also refer to the WP6 White Paper: OAV Architectures (May 26, 2021).
Standardisation body, organisations, associations based | ||||||
Aspects covered by architecture | ||||||
|---|---|---|---|---|---|---|
| Aligned/w | Proposer | Name | Orchestration | Automation | Virtualisation | Link to general info |
| ETSI ZSM | Architectural Framework for End-to-End Service and Network Automation | next-generation management and ops system | fully automated (zero-touch) | NFV + SDN | https://www.etsi.org/technologies/zero-touch-network-service-management |
| ONAP | Platform Architecture Dublin Release (blueprints for key use cases) | synchronously orchestrate physical and virtual network functions | closed-loop automation | VNF / SDN / VM / Cloud | https://www.onap.org/architecture |
| MEF LSO | Architecture for Lifecycle Service Automation | orchestrated multi-domain services | APIs to automate the entire service lifecycle | NFV, SDN | https://www.mef.net/lso/lifecycle-service-orchestration |
| ETSI | OSM (MANO) | Management and Orchestration (MANO) software stack aligned with ETSI NFV | closed-loop automation, policy driven automation | NFV, layering, abstraction | |
| GNA | GVM / GTS, overlap with ETSI-NFV, uses OGF NSI | orchestration through intelligent software agents | automated agents to manipulate standardized service objects | virtualisation through abstracted service objects | https://resources.geant.org/wp-content/uploads/2022/07/D8.9_GE%CC%81ANT-Testbeds-Service-6.0.pdf |
| ONF aligned | CONTENT | service orchestration above the control layer | automation support in processes for different stakeholders | virtualisation of wireless and optical resources, common virtualisation framework, VNF | https://nitlab.inf.uth.gr/NITlab/papers/katsalis-multi-domainSDN.pdf |
| based on extensions of Network Markup Language (NML) standard developed by the Open GridForum (OGF) | SENSE (Software-defined network for End-to-end Networked Science at Exascale (SENSE)) | SENSE orchestration architecture, software orchestrator | end-to-end automation (provisioning), SENSE enabled DTNs | virtualisation, service abstraction | http://es.net/assets/Uploads/76kkEi9wqPrVdrGK4bSFdg.pdf http://hpcc.umd.edu/hpcc/sc18/lehman-yang.html |
| TM FORUM | ODA | ZOOM zero-touch orchestration & management | APIs + AI | NFV | https://www.tmforum.org/resources/whitepapers/open-digital-architecture/ |
| TM FORUM | ODF | coming up in future efforts, very early stage, 5G use case | https://www.tmforum.org/opendigitalframework/ | ||
| 5G | 5G PPP 5G Architecture White Paper Revision 3.0 – For Public Consultation. (June 2019) | multi-tier orchestration | closed-loop automation for the lifecycle management of network slice instances automation enablers study | NFV, SDN | https://5g-ppp.eu/white-papers/ |
| ETSI | GANA - Generic Autonomic Networking Architecture | relies on an outside service orchestrator | autonomic management and control | NFV, SDN | https://www.etsi.org/images/files/ETSIWhitePapers/etsi_wp16_gana_Ed1_20161011.pdf |
| ETSI | NFV | in conjunction with ETSI OSM | https://www.etsi.org/committee/nfv | ||
| Efforts towards Industry harmonisation for Unified Standards on Autonomic Management & Control (AMC) of Networks and Services, SDN and NFV | ||||||
Commercial solutions | |||||
Aspects covered by architecture | |||||
|---|---|---|---|---|---|
| Proposer | Name | Orchestration | Automation | Virtualisation | Link to general info |
| Anuta Networks | AN NSO | Vendor-supplied Orchestration | network automation workflow, closed-loop network automation, API integrations with IP infrastructure | SDN, VNF and Cloud | https://www.anutanetworks.com/network-service-orchestration/ |
| Oracle | SNO | https://docs.oracle.com/en/industries/communications/network-service-orchestration/index.html | |||
| Ciena | Multi-Domain Service Orchestration | Orchestrates technologically diverse domains: cloud, multi-layer WAN, NFV, IP/MPLS | Does not automate any domain in particular. | Does not address, except as the orchestration. | https://www.ciena.com/insights/what-is/what-is-service-orchestration.html |
| AT&T | ECOMP (Enhanced Control, Orchestration, Management & Policy) Architecture | End-to-end service orchestration | Closed-loop automation | Compute, Network and Storage | https://about.att.com/content/dam/snrdocs/ecomp.pdf |
| i2CAT | TALENT - Terrestrial and Satellite Resource Coordination Framework | Provide E2E service orchestration through MANO frameworks, e.g. OSM | End-to-end service provisioning and resource coordination | Abstraction (API, information and data model) | https://ieeexplore.ieee.org/document/8802047 |