Purpose
The Access E-Line product is included in product portfolios of wholesale connectivity service providers to provide retail service providers with MEF-standardized point to point Layer 2 connectivity service against an SLA between the retail service provider’s ENNI and the wholesale operator’s UNI.
Defined Products
- Access E-Line
- Operator UNI
- ENNI
Attributes Definition
The attributes of this service, which provide the basis for the product payload, are defined in the following standard:
MEF 26.2 External Network Network Interface (ENNI) and Operator Service Attributes
Service Definition
This service is derived from the following standard:
MEF 51.1 Operator Ethernet Service Definitions
MEF Service Model (MSM) Carrier Ethernet
The information model of this service is:
Based on:
MEF 26.2 External Network Network Interface (ENNI) and Operator Service Attributes
MEF 55.1 Lifecycle Service Orchestration (LSO): Reference Architecture and Framework
Defined in:
MEF 7.4 MEF Services Model: Information Model for Carrier Ethernet Services
MEF Product Model (MPM) Carrier Ethernet
The data model/product payload specifications of this product is:
Based on:
MEF 7.4 MEF Services Model: Information Model for Carrier Ethernet Services
Defined in:
MEF 106 LSO Sonata Access E-Line Product Schemas and Developer Guide
Product Schemas
Download the Access E-Line payload schemas for these defined products on GitHub:
Janis Release Product Schemas (ZIP)
Irene Release Product Schemas (ZIP)
Haley Release Product Schemas (ZIP)
Grace Release Product Schemas (ZIP)
Fergie Release Product Schemas (ZIP)
Ella Release Product Schemas (ZIP)
Dolly Release Product Schemas (ZIP)
Celine Release Product Schemas (ZIP)
Billie Release Product Schemas (ZIP)
Aretha Release Product Schemas (ZIP)
* Payload product schemas are publicly available on GitHub. How do I access Mplify's GitHub?
Release Notes
Current version of the schema for this product:
* Payload release notes are publicly available on GitHub. How do I access Mplify's GitHub?
Blending
LSO APIs result from blending LSO Payloads into LSO Envelopes. Choose and combine exact combinations of LSO APIs and LSO Payloads into a single zip file for download using the LSO API Blending Tool.
