MEF LSO Cross Connection Type-0
- LSO Sonata
- Payload
Product Specification schema of Cross Connection Type-0
- A Type-0 Cross-Connection MUST transport the signal received at the ingress External Interface transparently (i.e., bit identical) to the egress External Interface.
- For a Type-0 Cross-Connection the values of the CableType parameters of the Cross-Connection External Interface Type Service Attribute MUST be the same at each Cross [...]
MEF LSO Cross Connection Type-1
- LSO Sonata
- Payload
Product Specification schema of Cross Connection Type-1 A Type-1 Cross-Connection MUST terminate the incoming signal (received from the ingress External Interface) below the PCS layer, pass the PCS codewords transparently (i.e., bit identical), and source another PHY below the PCS layer to the egress External Interface.
Cross-Connection Type 2
- LSO Sonata
- Payload
Product Specification schema of Layer 2 Cross-Connection A Type-2 Cross-Connection MUST terminate the Ethernet PHY and perform MAC Bridging (i.e., support a MAC Relay Entity) as defined in IEEE 802.1Q
Google Layer 2 Partner Interconnect
- LSO Sonata
- Payload
Google Layer 2 Partner Interconnect. This Product is used to model information needed by Service Provider to establish a Layer 2 Partner Interconntect.
Product Ordering Management
- LSO Sonata
- API
This file forms part of MEF W123 LSO Cantata and LSO Sonata Product Order Management API
This specification represents MEF work in progress and is subject to change.
This API implements Business Requirements that are defined in MEF Draft Standard: MEF W57.2
Supported use cases:
- Create Product Order
- Retrieve List of Product Orders
- Retrieve Product Order by Product Order [...]
Product Inventory Management
- LSO Sonata
- API
This file forms part of MEF 116 LSO Cantata and LSO Sonata Product Inventory API
This specification represents MEF work in progress and is subject to change.
This API implements Business Requirements that are defined in MEF Standard: MEF 81
It allows the Buyer to retrieve the information about existing Product instances from Seller's Product Inventory.
Supported use cases:
- [...]
Quote Management
- LSO Sonata
- API
This file forms part of MEF 115 LSO Cantata and LSO Sonata Quote Management API
This specification represents MEF work in progress and is subject to change.
This API implements Business Requirements that are defined in MEF Standard: MEF 80
Quote API allows the Buyer to submit a request to find out how much the installation of an instance of a Product Offering, an update to an [...]
Geographic Address Management
- LSO Sonata
- API
This file forms part of MEF 121 LSO Cantata and LSO Sonata Address Management API
This specification represents MEF work in progress and is subject to change.
This API implements Business Requirements that are defined in MEF Standard: MEF 79
It allows the Buyer to retrieve address information from the Seller, including exact formats, for addresses known to the Seller.
Supported use [...]
Product Offering Qualification Management
- LSO Sonata
- API
This file forms part of MEF 87 LSO Cantata and LSO Sonata Product Offering Qualification API
This specification represents MEF work in progress and is subject to change.
This API implements Business Requirements that are defined in MEF Standard: MEF 79
The Product Offering Qualification (POQ) Management API allows a Buyer to check whether the Seller can deliver a product or set of [...]
Geographic Site Management
- LSO Sonata
- API
This file forms part of MEF 122 LSO Cantata and LSO Sonata Site Management API
This specification represents MEF work in progress and is subject to change.
This API implements Business Requirements that are defined in MEF Standard: MEF 79
It allows to retrieve a list of Geographic Sites and to get all information for one geographic site.
Supported use cases:
- Retrieve [...]
Access Eline OVC
- LSO Sonata
- Payload
Product Specification schema of Access Eline OVC OVC Service Attributes control the behavior observable at and between External Interfaces to the Carrier Ethernet Network (CEN). The behaviors are achieved by the Network Operator and the Operator's client (the Service Provider in this case) agreeing on the value for each of the Service Attributes.