MEF LSO LEGATO MIRP -> In relation to TM Forum APIs Adrian O’Sullivan / Adrian.osullivan@huawei.com Emmanuel Sarris / Emmanuel.sarris@vodafone.com Davide Cherubini / Davide.Cherubini@vodafone.com

MEF 56 LEGATO SCA -> TMF 641 Service Order Mapping MEF defined separate createService and activateService Interfaces, which is supported via 2 separate TMF 641 ServiceOrderItems where MEF LEGATO createService Interface = TMF 641 ServiceOrder.ServiceOrderItem.action = “add” & ServiceOrder.ServiceOrderItem.service.serviceState = “inactive” MEF LEGATO activateService = TMF 641 ServiceOrder.ServiceOrderItem.action = “modify” & ServiceOrder.ServiceOrderItem.service.serviceState = “active” where the ServiceOrder.ServiceOrderItem.service.id is the id returned from the original createService request MEF defined a createAndActivateService Interface, which can be mapped to the Service Order TMF 641 with ServiceOrder.ServiceOrderItem.action = “add” and ServiceOrder.ServiceOrderItem.service.serviceState = “active

Service Configuration and Activation Service Order to Service Configuration and Activation Service Order Site A Attributes Physical-interface Attributes Physical-link Attributes Site B Attributes Physical-interface Attributes Physical-link Attributes UNI A Site Attributes UNI B Site Attributes UNI A Attributes EVC Attributes UNI B Attributes Customer Site A UNI A Site EP-Line (EVC) UNI B Site Customer Site B Service Configuration and Activation Customer Site CE L2 NID MPLS-TP / OTN UNI-N (C-VLAN ID) (QinQ) S-AG S-TAG MEF3.0 EP-LINE - P2P EVC (CFS) UNI-C

MEF LEGATO Service Characteristics – Without Complex Data Types apiSchema ServiceCatalog As Planned in JIRA EXTAPI-105 & EXTAPI-108 ServiceOrder Referenced In Populated In

Service Order API Schema driven by MEF LEGATO Yang/Swagger definitions – With Complex Data Types MEF 58 Swagger for mef-legato-services mef-legato-services Yang tree API Schema

MEF LEGATO Service Characteristics – With Complex Data Types continued

E-Line EPLService[EVC] E-Line EPL Service - P2P TOSCA Skeleton – ref MEF 55.0.2 End Point per UNI [UNICEEndPoint] E-Line EPLService[EVC] [EPL] Requires CEP Requires CEP End Point per UNI [UNICEEndPoint] C R R C LCM Interfaces(CRUD) EP-LINE EVC Customer Site CE L2 NID MPLS-TP / OTN UNI-N (C-VLAN ID) (QinQ) S-AG S-TAG MEF3.0 EP-LINE - P2P EVC (CFS) UNI-C

TOSCA Definitions using Complex InputTypes- Not Supported in ONAP yet The TOSCA Service Topology is made up of the main Template which defines the Topology ( or Graph ) of Node Templates and their relationships which make up the EPL Network Service ( see EPLTOSCA.zip): The node templates that make up the Topology use the node_types definitions: The following data types are defined for the EPL complex data types: