Expand all | Collapse all

MANO | Task of Service Orchestration

  • 1.  MANO | Task of Service Orchestration

    TM Forum Member
    Posted 13 days ago

    We hear a lot of service providers asking for MANO use-cases/solutions in their landscape.
    In NFV MANO architecture, what role does exactly OSS will play.

    Many OSS vendors provide service catalog, Workflow engine, Inventory & Activation functionalities as part of their OSS software.

    I am writing this post to understand,
    1. What exact role/functionalities are required by OSS systems.
    2. Could you please list some use-cases where OSS system is involved in MANO architecture.

    Srinivas Kancharla

  • 2.  RE: MANO | Task of Service Orchestration

    TM Forum Member
    Posted 12 days ago


    In IG1167 ODA Functional Architecture you find a description of the functional blocks:

    MANO would be wholly within the Production block as well as most OSS functions including those you listed as well as those of Service Assurance.

    IETF MANO leaves Fault and Performance Management (FM & PM) out of scope. OSS is responsible for monitoring Network Services (NS), Virtual Network Functions (VNF), MANO and ODA Components. This requires Service and Resource Inventory Management (IM) for alarm and metric information enhancement and correlation. ODA functions in the Intelligence Management block concerned with Autonomous Networks (AN) also need IM topology. These are all examples where a unified architecture supporting TM Forum's Information Framework (SID) and Open APIs would be greatly beneficial.

    Vance Shipley

  • 3.  RE: MANO | Task of Service Orchestration

    TM Forum Member
    Posted 12 days ago
    My understanding of MANO based on reading the architecture document ETSI GS NFV 002  is that  strictly limited to the management  of virtualisation i.e.  taking software images packaging them into  VNF Packages and deploying onto a virtualisation infrastructure  Specifically excluded are the current OSS Functional interfaces/ services  to configure Element Management Systems.

    There are a few paradoxes that arise :
    • Some interpret the MANO architecture as functional as some as a literal implementation architecture  reinforced by defining concrete SOL interfaces.
    • the Os-Ma interface provides virtualisation management capabilities to OSS  whereas most legacy OSS systems do not have the capability to manage So actual this needs new OSS functionality or new OSS systems
    • the Element Management interfaces for configuring network infrastructure and individual instances of services are actually the  major integration complexity and cost for service providers.
    • as the EMS interface are out of scope the integration of visualised network applications  with legacy Network Appliances is unclear.
    We did a more detailed analysis in  IG1161C Technical Overview: Agile Intent-based Resource Management (Orchestration) in Hybrid Environments with ETSI MANO exemplar

    TM Forum also created related use stories in TR229 ZOOM/NFV User Stories Suite R17.0.0
    TM Forum  studied  the management of Hybrid solutions published in   TR262 Management Platform Blueprint and Application to Hybrid Infrastructure R17.5.1
    This addresses the EMS challenge of managing hybrid Infrastructure ( legacy and virtualized) and managing the network functionality as well as the virtualization aspects.

    A set of requirements and solutions were developed in the TR255 Resource Function Activation and Configuration Suite  .
    This introduced the notion of:
    •  intent based management to simplify the EMS services together with generalised view of resources called Resource Functions ( with features) now incorporated into the SID and has significant flexibility advantage over use of RFS based models
    • Defining interfaces support the use of hybrid internet and detailed ( traditional ) EMS Management services

    TMF664  Resource Function Activation and  Configuration API support sthese TR 255 requirements   and was demonstrated in a couple of PoC Catalyst (Real Virtuality). The  latest schematised version on   Open API Table - Pre-production (Beta)  ( you need to be registers on a core collaboration project to access) .  T
    his covers most of the functions of Os-Ma SOL 5 but is designed to support the  EMS servicese as well in a single interface design. The interfaces is dynamically extensible using a concept of polymorphic behaviour defined in
    TMF630 API Design Guidelines 3.0 R17.5.1.

    Dave Milham
    TM Forum chief architect