MEF 60 Network Resource Provisioning – Interface Profile Specification

2018 Jan

Summary:

This Interface Profile Specification defines the Presto Management Interface for the network control and management domain in support of [MEF 6.2] and [MEF 51] Services and is a specialization of relevant classes from the MEF NRM (Network Resource Model).

Product Portfolio: Carrier Ethernet, LSO Presto

Standard Type: Information and Data Models

Tags: MRM (MEF Resource Models)

Abstract:

This Interface Profile Specification defines the Presto Management Interface for the network control and management domain in support of [MEF 6.2] and [MEF 51] Services and is a specialization of relevant classes from the MEF NRM (Network Resource Model). The Presto NRP (Network Resource Provisioning) Interface is for use by a Service Orchestration Functionality (SOF) as described in [MEF 55] and in support of processes for Service Configuration and Activation [MEF 56] at the network resource layer. 

The Presto NRP requests ICM to create connectivity or functionality associated with specific Service Components of an end-to-end Connectivity Service within the domain managed by each ICM. Presto may also allow the ICM to describe Resources and capabilities it can instantiate. 

This document normatively includes the content of the following files as if they were contained within this document: 

  • NRP_Interface.di
  • NRP_Interface.notation 
  • NRP_Interface.uml 

These files are available in the Technical Specifications area of MEF.net alongside this specification. 


Standards published by MEF are intended for general distribution to the public and may be downloaded from this site and reproduced without charge. Any reproduction of MEF documents shall contain the following statement: “Reproduced with permission of MEF Forum.” All rights granted to MEF under applicable copyright laws are expressly reserved. No permission is granted to any recipient or user of MEF publications to modify any of the information contained therein and MEF disclaims all responsibility and liability for such modifications.

Be In the Industry—Join with industry peers to advance digital service & API standards.

Join MEF