MEF Object Models

The foundation of MEF LSO APIs.

MEF Object Models (MOM)

Our suite of object models supporting MEF’s LSO APIs, lovingly referred to as ‘MOM,’ are composed of five information model groups:

  1. MEF Core Model (MCM)
  2. MEF Policy Model (MPM)
  3. MEF Services Model (MSM)
  4. MEF Resources Model (MRM)
  5. MEF Business Model (MBM)

Business Requirements and Use Cases (BRUC)

With the information models in-hand, MEF then defines and documents the business requirements and use cases (BRUC). The models are generic, whereas the BRUC takes the information and applies it to the specific LSO reference points (e.g. LSO Presto, LSO Sonata, LSO Interlude, etc.). Thus a formal definition of the requirements and use cases is defined for each LSO reference point.

MEF Dots Pattern

Data Models and APIs

With the BRUC, the data models and APIs are developed. The APIs use the UML information from the models, plus the requirements and use cases, and maps these to specific data schemas. Using tooling and/or manual effort, MEF, in collaboration with other industry bodies, develops reference implementations. 

For example, the industry has adopted NETCONF/YANG at the LSO Presto reference point. In the case of LSO Presto, the APIs are built using ONF transport APIs (ONF-TAPI), adding the MEF-specific value-added elements to these existing APIs. This collaboration accelerates development and enhances adoption—a key element of our MEF 3.0 Global Services Framework’s community pillar.

The Models

MEF Core Model (MCM)

The MEF Core Model (MCM) is the information model describing the base set of object definitions and relationships supporting the concepts defined in the LSO Reference Architecture (MEF 55). MCM formalizes the diverse concepts in the LSO Reference Architecture into a coherent, object-oriented information model, which acts as the source of key concepts and functions that can be reused or refined across all MEF definition projects.

MCM uses Unified Modeling Language (UML) to describe the salient characteristics and behaviors of entities that are important in a managed environment and acts as a common lexicon for all MEF models.

MEF Policy Model (MPM)

The MEF Policy Model (MPM) standardizes the object-oriented technology-neutral information model for representing different types of policies used in the MEF LSO Architecture. Currently, the focus is on imperative and intent policies.

Many service providers and technology vendors implement policy management solutions. However, the standards-based approach encapsulated in MPM that specifies an architecture with an associated information model is essential to ensure interoperability.

This unified and standardized approach to policies will be even more important with the emergence and growth of policy-oriented services like SD-WAN, SASE and Zero Trust Network Access.

MEF Services Model (MSM)

The MEF Services Model (MSM) is the collection of service models, which generally map one-to-one to the service standards (e.g. MEF 3.0 SD-WAN, Carrier Ethernet) defined by MEF in the context of the MCM. MSM is designed to be leveraged at multiple LSO Reference Points (e.g. LSO Sonata, LSO Legato, LSO Interlude, LSO Allegro) to develop APIs at each of these reference points with common objects, attributes, and relationships.

MEF Service Models are also key to the development of the MEF product payloads used in the East-West APIs (e.g. LSO Cantata, LSO Sonata).

MEF Resources Model (MRM)

The MEF Resources Model (MRM) is a collection of resource models that leverage the common constructs of MCM, adding information relevant to how you provision the resources (e.g. provision a Carrier Ethernet EVC). It also includes Operations, Administration, and Maintenance (OAM), and other elements related to the various MEF 3.0 services.

MRM provides a resource-oriented view at the network level, and can be used as the basis for LSO Presto interface profiles defining LSO Presto APIs.

MEF Business Model (MBM)

The MEF Business Model is the collection of object-oriented information models identifying the commercial attributes and characteristics needed to order products and exchange business-level information between providers as well as with the subscriber or customer.

 

MEF API Development

How does MEF facilitate the development of APIs?

1To facilitate automation, MEF begins with the definition and standardization of MEF 3.0 services.

2From these service definitions, information or object models are developed. These include common MEF types and constructs and a common taxonomy and behavior that span all MEF 3.0 services.Specific resource, service, policy, and business model representations are developed for each MEF 3.0 service. Some of these models relate to more than one LSO interface reference points (e.g. There is a significant overlap of product models applied at LSO Sonata and Cantata).

3The Business Requirements and Use Cases (BRUC) are specific to each LSO interface reference point and they define the functional requirements, use cases, business process flows, state transitions, etc., related to the specific LSO interface (e.g. LSO Sonata).

4From these BRUCs, MEF maps the applicable information models to relevant data schemas which are then packaged into SDKs along with related documentation, code samples, and developer guides, to support the development of MEF APIs for each of the LSO interface reference points.

MEF incorporates industry work, in a collaborative manner, to leverage ongoing projects in specific domains, e.g TMF Open APIs, ONF TAPI, that facilitate rapid and frictionless adoption with industry stakeholders.

MEF’s Approach to Standard APIs

To support automation within and between providers, both the services and the information models need to be standardized.

From Service Standards to Standard APIs

Model

To facilitate automation, MEF begins with the definition and standardization of MEF 3.0 services. 

From these service definitions, information or object models are developed. These include common MEF types and constructs and a common taxonomy and behavior that span all MEF 3.0 services.Specific resource, service, policy, and business model representations are developed for each MEF 3.0 service. Some of these models relate to more than one LSO interface reference points (e.g. There is a significant overlap of product models applied at LSO Sonata and Cantata).

The Business Requirements and Use Cases (BRUC) are specific to each LSO interface reference point and they define the functional requirements, use cases, business process flows, state transitions, etc., related to the specific LSO interface (e.g. LSO Sonata).

From these BRUCs, MEF maps the applicable information models to relevant data schemas which are then packaged into SDKs along with related documentation, code samples, and developer guides, to support the development of MEF APIs for each of the LSO interface reference points.

Learn More about Models

Technical Standards & SDKs

MEF 82 MEF Services Model – Information Model for SD-WAN Services — 2020 Jul

Product Portfolio: Models, SD-WAN
Standard Type: Information and Data Models

The MEF Services Model (MSM) is an information model representation of the constructs used to define MEF services (e.g., Carrier Ethernet, IP, Layer 1 and SD-WAN service).

Learn More

MEF 78.1 MEF Core Model (MCM) — 2020 Jul

Product Portfolio: Models
Standard Type: Information and Data Models

This specification defines the MEF Core Information Model (MCM), which is an information model describing the base set of object definitions and relationships supporting the concepts de-fined in the MEF Lifecycle Service Orchestration (LSO) Reference Architecture (RA)

Learn More

MEF 83 Network Resource Model – OAM — 2019 Sep

Product Portfolio: Carrier Ethernet, Models
Standard Type: Information and Data Models

This specification describes the MEF Network Resource Management Information Model (NRM IM), specifically for Carrier Ethernet Operations, Administration and Maintenance (OAM) related management features.

Learn More

MEF 72 Network Resource Model – Subscriber Layer 1 — 2019 May

Product Portfolio: Models, Optical Transport
Standard Type: Information and Data Models

This specification describes the MEF Network Resource Management Information Model (NRM IM), specifically for Layer 1 Connectivity related management features.

Learn More

MEF 59 Network Resource Management – Information Model: Connectivity — 2018 Jan

Product Portfolio: Models
Standard Type: Information and Data Models

Lifecycle Service Orchestration Reference Architecture (LSO RA, MEF 55) extends the traditional MEF scope concerning Service Modeling, from a pure view “from outside the network” to cover a range of Operational, Orchestration, and Network Management behaviors, including SDN and NFV paradigms.

Learn More

I want to investigate further. See all Models resources:

What Can I Achieve with MEF Object Models?

MEF’s Object Models (MOM) provide the foundation for software architects and developers that need to understand MEF LSO APIs and successfully implement the relevant APIs for their business.

MEF Object Model advantages:

  • Achieve a consistent software architecture for delivery of MEF services.
  • Leverage East-West LSO API work for non-MEF services.
  • Participate in the modelling of future MEF services.

Be In the Standard

Engage with MEF Object Models

We invite software architects and professionals in related fields to advance the foundation of our industry’s automation by joining MEF’s on-going modelling projects. Join a call, comment on draft work or launch a new initiative that supports your company objectives and the industry. As a MEF member, you can access the latest projects in the MEF 3.0 Object Models Hub on the MEF Members’ Wiki.


All employees of active MEF-member companies are authorized to access MEF Members’ Wiki. Don’t have a login? Register. Not a member? Join MEF. Not sure? Contact Us.

Go to the Member Wiki
Woman with pink jacket

Be In the Know—Dig into the foundation of industry automation.

Become a MEF Member