MEF Interface Profile Specification (IPS) is a MEF specification for an LSO Reference Point that includes the following artifacts (some may be optional depending on the LSO Reference Point)

 

There is one IPS for each LSO Reference Point.

Examples:

  • LSO Sonata IPS (MEF 77)
  • LSO Interlude IPS (MEF 76)
  • LSO Legato IPS (MEF 73)
  • LSO Presto IPS (MEF 86)

An IPS is ultimately used for the development of APIs at the specified LSO Reference Point.



Requirements

This section captures the business requirements of the users of the APIs that are derived from the IPS. The requirements are formatted as shown in the example with a unique ID, description and source. These business requirements are an important foundation for developing data models and APIs at the LSO Reference Point because they describe the consensus of the representatives of the actors in the MEF, and clarify for current and future APIs the assumptions that underpin those APIs. Agreement on both the language and the importance of the business requirements is facilitated by the MEF in the context of the IPS project.

 

Requirements Examples

R_SONATA_ORDER_0001

The interface shall support sellers who have product offerings in product catalogs, and those that are not catalog driven.

Source

 

R_PRESTO_NRP_0001

The PRESTO NRP Interface MUST support creating and activating a new network resource Connectivity Service.

Source

 

 

Use Cases

Use Case is a list of actions or event steps, typically defining the interactions between a role (known in the Unified Modeling Language as an actor) and a system, to achieve a goal.

 

Use Case Example

Use Case Id

UC_"PRESTO_NRP"_0001

Use Case Name

Create and Activate ConnectivityService

Summary

  • Causes the creation and activation of a ConnectivityService connecting two or more ServiceEndPoints.
  • Returns Service ID to be used as a reference for future actions.

Actor(s)

Service Orchestration Functionality

Pre-Conditions

  • Requestor/Client has visibility of two or more ServiceEndPoints are ServiceEndPoint/NrpCgEthUniSpec.
  • Requestor/Client has information about the attribution and constraints it can specify at network resource layer.
  • Requestor/Client may be aware of other existing ConnectivityServices and their IDs.

Begins When/Inputs

  • Client sends create and activation request forConnectivityService.
  • ServiceEndPoints and corresponding ExtensionSpecification are determined and applied.
  • ConnectivityService and corresponding ExtensionSpecification are determined and applied.
  • ConnectivityServicePort and corresponding ExtensionSpecification are determined and applied.

Description

The creation and activation of a ConnectivityService with ServiceEndPoints under the control of a single Domain Controller. Upon successful completion the bearer plane is active.

Ends When

ConnectivityService is created and activated with bearer plane segment operation active.

Unique ConnectivityService ID is returned.

Resources are allocated and activated to support bearer plane segment operation.

If Asynchronous API operation – return SHOULD indicate successful resource creation. Return message SHOULD contain a resource representation and a Location header with create resource location (i.e., URI). Reference TMF630.

Post-Conditions

Active bearer plane segment and allocated resource on physical and/or virtual device(s).

Notification/Event

If Asynchronous API operation - Resource representation and a Location header with create resource location (i.e., URI).

Exceptions

  • ConnectivityServiceNot Supported.
  • ServiceEndPointNot Available.
  • ServiceEndPointNotRecognized.
  • InvalidInput
  • NotInValidState
  • InternalError
  • NotImplemented
  • CommLoss
  • AccessDenied
  • UnableToComply

Business Process

 

Requirement

R_PRESTO_NRP_008



Traceability Matrices

These are tables in the IPS that map the use cases to requirements and, conversely, from the requirements to the use cases to identify relationships that are missing, and overly complex relationships.


 


 



IPS Development

Each IPS is developed as a project in the MEF Technical and Operations Committee**. It is required to pass at least one Call for Comments (CfC) Ballot and at least one Letter Ballot (LB) in order to be approved by the MEF Board of Directors for publication into the public domain.

IPS Format

The MEF IPS template** is used by the MEF projects to create and populate an IPS. The UML models are reviewed by the project participants by generation of a Word document using the Gendoc tool from Eclipse.

 





** Available to MEF members only

Sources and References