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.
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.
Enabling end-to-end service orchestration within and between providers, to deliver digital and connectivity services to the enterprise.
Customer- to service-provider interactions:
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.).
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.
The Management Interface Reference Point that provides a Customer Application Coordinator (including enterprise customers) with capabilities to manage interactions (e.g., ordering, billing, trouble ticketing, 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.
The interface that manages interactions between two network providers (e.g., Service Provider Domain and Partner Domain), such as ordering, billing, trouble management, etc..
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.
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 ticketing, etc.