LSO (Lifecycle Service Orchestration) is the set of MEF-defined specifications enabling standardized service orchestration based on standardized lifecycles of end-to-end connectivity services across one or more network service domains. LSO, in combination with SDN and NFV, is designed to enable the Third Network vision.

LSO is an agile approach to streamlining and automating the service lifecycle in a sustainable fashion for coordinated management and control across all network domains responsible for delivering an end-to-end Connectivity Service (e.g., Carrier Ethernet, IP VPN, MPLS, etc.). This document describes a Reference Architecture and Framework for orchestrating the service lifecycle. It includes a set of functional management entities that enable cooperative service lifecycle orchestration for Third Network Connectivity Services. The framework also provides high level functional requirements and outlines high level operational threads describing orchestrated Connectivity Service behavior as well as interactions among management and control entities. The Management Interface Reference Points that characterize interactions between LSO functional management entities are identified in the reference architecture. These Management Interface Reference Points are described such that they can be realized by Interface Profiles and further by APIs, which can be used to enable automated and orchestrated Connectivity Services.

  • The services in The Third Network will be orchestrated among all the participating service providers, operators, enterprises, and subscribers supplying or consuming components of the service in order to provide coordinated end to end management and control.
  • Orchestration capabilities are the backbone of the Lifecycle Services provided by The Third Network; not only to dramatically decrease the time to establish and modify the characteristics of the end to end service, but will also assure the overall service quality and security guarantees for these services
  • New Lifecycle Service Orchestration Vision White Paper (February 2015)

Lifecycle Service Orchestration Capabilities

The following is a summary of the principle capabilites of Lifecycle Service Orchestration consisting of Fulfillment, Control, Performance, Assurance, Usage and Analytics

  • Fulfillment
    • Query product catalog
    • Order exchange, management, and tracking
    • Design, provisioning and assignment of resources
    • Verification, test, and turn-up
    • Discovery and reconciliation of service and network resources, topology, and connectivity
  • Control
    • Actively control the elastic behavior of their service instances (both connections and interfaces)
    • Managed connections as well as managed interfaces may be turned on and off either instantaneously or as the result of actions tied to defined triggering events (e.g., schedule)
    • Throttle up or back the bandwidth associated with specific connections (or per CoS)
    • Add or remove endpoints in accordance with their specified dynamic service policies
    • Discovery of service capabilities
    • Migration of services to different resources
  • Performance
    • Collect service performance related information across the Network
    • Gather customer provided quality feedback
    • Service Quality is analyzed by comparing the service performance metrics with the service quality objectives described in the SLS
    • Provide the results of the service quality analysis to as well as information about known events that may impact the overall service quality (e.g., maintenance events, congestion, relevant known troubles, demand peaks, etc.)
    • Perform capacity analysis and traffic engineering
    • Perform service quality improvement
    • Management of aggregate traffic flows though the network based on projected demands

Making the Vision a Reality

The MEF's Strategy to implement the Third Network vision is to use Network as a Services principles, the solution is to develop a layered approach to break down complex problems, domain by domain or layer by layer


Lifecycle Service Orchestration Capabilities (Continued)

  • Assurance
    • Alarm surveillance: detect errors and faults
    • Perform fault verification, isolation, and testing
    • Reports correlated alarms, performance events, trouble reports, etc. to including the potential root cause of a trouble and identified impact on services
    • Control filtering of notifications
    • Provide trouble related information allowing the Orchestrator to track the status of trouble resolution
    • Fault recovery
  • Usage
    • Allows the Provider to provide usage reports describing the usage of service capabilities and associated resources to the E2E Orchestrator
    • Collection and correlation
    • Capture Service Events (change in BW, etc.)
    • Exception reports may also be generated to describe where service resources have been used beyond the commitments as described in the SLS
    • Usage and traffic measurements
  • Analytics
    • Prediction and trending of service growth
    • Plus much more

Public Resources