API Catalog

A UCS is connected to a UCS UNI by a UCS End Point. Some service architectures support multiple UCSs at the same UCS UNI. The UCS End Point captures Service Attributes at the UCS UNI whose value can differ between UCSs. Reference MEF 70.1 Section 14 UCS End Point Service Attributes.

Access to an Underlay Connectivity Service is provided at the SD-WAN Edge via the UCS UNI. Reference MEF W70.2 Section 12.2 SD-WAN UCS UNI Service Attributes.

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 [...]

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.

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. This Product is used to model information needed by Service Provider to establish a Layer 2 Partner Interconntect.

The Service Catalog API provides a standardized mechanism for retrieving ServiceSpecifications. Using these APIs Business Applications (BUS) systems query the Service Catalog for ServiceSpecifications supported by the Service Orchestration Function (SOF).

Additionally, the APIs also allow the BUS to register listeners to be notified of the changes to the ServiceSpecifications.

• [...]

The Service Inventory API provides a standardized mechanism for retrieving ServiceInstances. Using these APIs Business Applications (BUS) systems query the Service Inventory system for ServiceInstances that were created by the Service Order Management system in the Service Orchestration Function (SOF).

Additionally, the APIs also allow the BUS to register listeners to be notified [...]

The Service Order API provides a standardized mechanism for managing ServiceOrders. Using these APIs Business Applications (BUS) systems post ServiceOrder requests to the Service Order Management system within the Service Orchestration Function (SOF).

Additionally, the APIs also allow the BUS to query and retrieve ServiceOrders in SOF and to register listeners to be notified of [...]

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 existing [...]

This file forms part of MEF 116 LSO Cantata and LSO Sonata Product Inventory API

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:

• Retrieve Product List
• Retrieve Product by Identifier

Copyright 2022 MEF Forum and its [...]

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
• Update Product Order by Product Order Identifier
• Retrieve List of Product [...]