MEF APIs

Frictionless, end-to-end service automation, within and between providers, direct to the enterprise.

Software-Defined Digital Services with LSO

The alignment of business and technology within a service provider’s domain is critical for both maximizing the enterprise customer experience as well as driving operational excellence. The value of this alignment is multiplied when delivering enterprise digital and connectivity services across multiple providers.

When an enterprise’s needs are seamlessly communicated and fully realized across the technology infrastructure, covering multiple service provider domains, the result is much like that of an orchestra performing a symphony: the complexities of each part, played on many instruments, fade into the unified experience of the music. Analogously, the automation and orchestration of both business and technology—both within, and between service providers, intersecting with cloud providers—should deliver a seamless, unified experience for the digital enterprise.

MEF members recognized that, with the arrival of SDN/NFV and cloud-computing, enterprises needed agility, assuredness, and automation from their networks. Thus, was born Lifecycle Service Orchestration (LSO), a reference architecture and framework for enabling end-to-end automation and orchestration, across multiple provider networks. This LSO framework forms the basis for enabling software-defined digital services, from commercial interactions to operational level inter-provider automation, as well as intra-provider automation from orchestrator, to controller, to infrastructure.


Understanding the LSO Framework

The LSO Reference Architecture incorporates Seven reference points:

  • Two focus on customer- to service-provider interactions.
  • Two focus on inter-provider interactions (East-West APIs).
  • Three focus on intra-provider interactions (North-South APIs).

Together, the interface reference points enable the full orchestration of enterprise digital services across service providers, their partners, cloud providers, and the Internet.

MEF 3.0 LSO Reference Architecture

Enabling end-to-end service orchestration within and between providers, to deliver digital and connectivity services to the enterprise.

MEF 3.0 LSO Reference Architecture
Cantata Allegro Sonata Interlude Legato Presto Adagio Legato Presto Adagio

Cantata

The interface that manages interactions between the Customer Application Coordinator (e.g. the enterprise customer via a web portal) and the Service Provider, such as ordering, billing, trouble management, etc.).

Allegro

The interface that allows Customer Application Coordinator supervision and control of dynamic service behavior of the LSO service capabilities under its purview, through interactions with the Service Orchestration Functionality.

Sonata

The interface that manages interactions between two network providers (e.g., Service Provider Domain and Partner Domain), such as ordering, billing, trouble management, etc..

Interlude

The interface that provides for the coordination of a portion of digital LSO services within the partner domain that are managed by a Service Provider’s Service Orchestration Functionality, within the bounds and policies defined for the service.

Legato

The interface between the Business Applications and the Service Orchestration Functionality, that manages interactions supporting digital LSO connectivity services.

Presto

The resource management interface needed to manage the network infrastructure, including network- and topology-view-related management functions.

Adagio

The element management interface needed to manage the network resources, including element-view-related management functions.

Legato

The interface between the Business Applications and the Service Orchestration Functionality, that manages interactions supporting digital LSO connectivity services.

Presto

The resource management interface needed to manage the network infrastructure, including network- and topology-view-related management functions.

Adagio

The element management interface needed to manage the network resources, including element-view-related management functions.


The Seven LSO Interface Reference Points

Enterprise APIs

Customer- to service-provider interactions:

Enterprise APIs
Cantata Allegro

Cantata

The interface that manages interactions between the Customer Application Coordinator (e.g. the enterprise customer via a web portal) and the Service Provider, such as ordering, billing, trouble management, etc.).

Allegro

The interface that allows Customer Application Coordinator supervision and control of dynamic service behavior of the LSO service capabilities under its purview, through interactions with the Service Orchestration Functionality.

1LSO CANTATA

The Management Interface Reference Point that provides a Customer Application Coordinator (including enterprise Customers) with capabilities to manage interactions (e.g., ordering, billing, trouble management, etc.) with the Service Provider’s Business Applications, for a portion of the Service Provider service capabilities related to the Customer’s Products and Services.

Example: An enterprise customer orders a service from a Service Provider using a web portal that interfaces to the service provider using Cantata. The same interface is later used to instantiate and communicate a service interruption (i.e. trouble-ticket).
2LSO ALLEGRO

The Management Interface Reference Point that allows Customer Application Coordinator supervision and control of dynamic service behavior of the LSO service capabilities under its purview, through interactions with the Service Orchestration Functionality.

When a Customer exercises dynamic service behavior via Allegro, the Service Orchestration Functionality must validate each request using the Service specific policies that govern such dynamic behavior. Such dynamic behavior and associated constraints are defined based on the Product Specification implemented by the Service.

Example: A Service-specific dynamic service policy may describe the range of bandwidth in which the Customer is permitted to throttle. Allegro may also be used to share service-level fault information with the Customer.

East-West APIs

Inter-provider interactions:

East-West APIs
Sonata Interlude

Sonata

The interface that manages interactions between two network providers (e.g., Service Provider Domain and Partner Domain), such as ordering, billing, trouble management, etc..

Interlude

The interface that provides for the coordination of a portion of digital LSO services within the partner domain that are managed by a Service Provider’s Service Orchestration Functionality, within the bounds and policies defined for the service.

Example: The Service Provider Business Applications may use Sonata to place an order to a Partner provider for an access service that is needed as part of an end-to-end Connectivity Service.

3LSO SONATA

The Management Interface Reference Point that manages interactions between two network providers (e.g., Service Provider Domain and Partner Domain), such as ordering, billing, trouble management, etc.

4LSO INTERLUDE

The Management Interface Reference Point that coordinates a portion of digital LSO services within the partner domain that are managed by a Service Provider’s Service Orchestration Functionality, within the bounds and policies defined for the service.

Through Interlude, the Service Orchestration Functionality may request initiation of technical operations or dynamic control behavior associated with a Service with a partner network domain. Such requests must be within the constraints set forth in the policies associated with established Services and performed, without impacting business applications.

Example: To satisfy a Customer request, the Service Orchestration Functionality may request changes to a CE-VLAN ID mapping at a UNI that resides in a partner domain. Interlude may also be used to share service-level fault information with the partner domain.

North-South APIs

Intra-provider interactions:

Service Provider and Partner Domains

SP and Partners Domains
Legato Presto Adagio

Legato

The interface between the Business Applications and the Service Orchestration Functionality, that manages interactions supporting digital LSO connectivity services.

Presto

The resource management interface needed to manage the network infrastructure, including network- and topology-view-related management functions.

Adagio

The element management interface needed to manage the network resources, including element-view-related management functions.

5LSO LEGATO

The Management Interface Reference Point between the Business Applications and the Service Orchestration Functionality that manages interactions supporting digital LSO connectivity services.

Example: The Business Applications may, based on a Customer order, use Legato to request the instantiation of a Connectivity Service. Legato may also allow the SOF to describe Services and capabilities it is able to instantiate. Also, the Service Orchestration Function may use Legato to ask the Business Applications to place an order to a Partner provider for the access service needed as a Service Component of an end-to-end Connectivity Service.

6LSO ALLEGRO

The Resource Management Interface Reference Point needed to manage the network infrastructure, including network- and topology-view-related management functions.

Example: The Service Orchestration Function will use Presto to request ICM to create connectivity or functionality associated with specific Service Components of an end-to-end Connectivity Service within the domain managed by each ICM. Presto may also allow the ICM to describe Resources and capabilities it is able to instantiate.

7LSO ADAGIO

The Element Management Interface Reference Point needed to manage the network resources, including element-view-related management functions.

Example: ICM will use Adagio to implement cross-connections or network functions on specific elements via the ECM functionality responsible for managing the element.

Explore MEF APIs

East-West LSO APIs

Inter-provider service automation accelerates software-defined digital services by enabling providers to drastically reduce provisioning time with partner operators and manual effort. Understand how to deliver the agility and customer experience enterprises demand.

Explore MEF's East-West LSO APIs

North-South LSO APIs

From service OAM, to lean NFV, orchestrators to controllers and EMSs, intra-provider service automation is critical to transforming into a digital service provider. Understand how to stop ballooning costs caused from implementing multiple vendor APIs and get to market faster.

Explore MEF's North-South LSO APIs

Models for LSO APIs

Information models are the bedrock of automation. MEF uses a hierarchy of information models to ensure reusability, and consistency, to fully enable automation within a single provider and between providers.

Explore MEF's Models for LSO APIs

Be In the Industry—Open opportunities to connect with partners and customers.

Join MEF