Lifecycle Service Orchestration, or LSO, is a set of specifications which is part of MEF 3.0. Its aim is to standardize orchestration of connectivity services, such as MPLS and Carrier Ethernet. The LSO APIs are a platform-neutral way of automating and managing a service’s full lifecycle, from making it available through installation, maintenance, and end of life.
Many of these actions have previously required constant human intervention to deliver and manage services. LSO aims to automate the process as much as possible. The APIs span provider and customer networks. Customers can identify, order, and maintain services without having to wait for human assistance, except in the most unusual cases.
LSO defines seven Management Interface Reference Points, which are logical points of interaction. Each of them has one or more APIs associated with it, specifying how to access the reference point’s functionality.
MEF LSO APIs
LSO Cantata defines the reference point for business interactions between a service provider and a customer. The interactions it covers include viewing product offerings, placing product orders, submitting problem reports, and viewing billing information. In LSO terminology, the applications which handle these services are called Business Applications. Cantata doesn’t include control-related functionality; that falls under Allegro.
The functionality under Cantata and Allegro is in the scope of the Customer Application Coordinator, a person or group that the customer designates to manage application service needs.
LSO Allegro covers control-related interactions between a provider’s Service Orchestration Functionality (SOF) and a customer. It applies to services which the customer already has installed. In most cases, the customer initiates interactions under Allegro. The possible interactions include service administration, status queries, and customization of parameters. Service-related alerts come through Allegro.
LSO Sonata handles non-control interactions between a service provider and a partner. The interactions are similar in some ways to those provided under Cantata, except that a customer isn’t involved. One of its chief aims is to reduce service setup time through automation of order management. A service provider can use Interlude to browse a partner’s product catalog, place product orders, exchange usage and billing information, and submit problem reports.
LSO Interlude deals with control-related interactions between a service provider and a partner. It has some similarities to Allegro but between the provider’s SOF and the partner’s SOF rather than between the customer and provider. The information exchanged includes service inventory, operational status, event notifications, and test results. The provider can set parameters on the customer’s behalf, create a connection between service interfaces, and change a service’s administrative state.
LSO Adagio defines the reference point to manage network resources. It is considered a “north-south” interface, operating between levels within a domain. The Infrastructure Control and Management (ICM) layer uses Adagio to communicate with the Element Control and Management (ECM) layer. An element is a unit which provides functionality, such as a physical or virtual server. Both service providers and partners use Adagio. It is independent of any particular protocol but could work with OpenFlow or NETCONF/YANG. Examples of interactions include implementation of cross-connections, acquisition of element configuration data, and obtaining performance and status information from elements.
MEF currently isn’t doing any definition work on Adagio.
LSO Legato defines the reference point for communication between a provider’s or partner’s Business Applications and the SOF layer. Like Adagio, it is a “north-south” interface. Business Applications will often use Legato in carrying out customer requests which they received over Cantata.
Requests by Business Applications can include determining the feasibility of services, activating services and service components, and reserving resources. Business Applications may receive requests to place a product order, usage events, information on service quality and usage, and test results from service activation.
LSO Presto deals with management and viewing of the network infrastructure. It is a “north-south” interface, connecting the SOF to the ICM layer. Service providers and partners both use Presto. The first of the APIs to be defined for it is the LSO Presto Network Resource Provisioning API (NRP). Detailed information on NRP is currently available only to MEF members.
Presto lets the SOF obtain information on topology, connectivity, routing, and performance from the ICM. SOF can query the ICM on resource inventory and capabilities.
Contact us if you have questions or would like to learn more.