Statement of Compliance towards ETSI GS NFV-MAN 001
Ericsson Service-Aware Policy Controller

Contents

1Introduction

2

General Considerations

3

Scope, References and Abbreviations
3.1Scope
3.2References
3.3Definitions and Abbreviations
3.3.1Definitions
3.3.2Abbreviations

4

NFV Management and Orchestration: objectives and concepts
4.1Overview
4.2Management and Orchestration aspects of Network Functions Virtualisation Infrastructure
4.3Management and Orchestration aspects of Virtualised Network Functions
4.4Management and Orchestration aspects of Network Services
4.5Other management and orchestration aspects of NFV framework
4.6Relation of NFV management and orchestration with existing operations and management systems
4.7Administrative Domains

5

Management and Orchestration architectural framework
5.1Overview
5.2Principles of NFV-MANO
5.3NFV-MANO architectural framework overview
5.4NFV-MANO architectural framework functional blocks
5.5Other functional blocks
5.6Network Controllers
5.7NFV-MANO reference points
5.8Interfaces description approach

6

NFV management and orchestration information elements
6.1Introduction
6.2Network Service information elements
6.3Virtualised Network Function information elements
6.3.1VNF Descriptor (vnfd)
6.3.2VNF Record (vnfr)
6.4Virtual Link information elements
6.5Virtualised Network Function Forwarding Graph information elements
6.6Physical Network Function information elements
6.7VNF Instantiation input parameter
6.8Network Service Instantiation Input Parameters

7

NFV-MANO interfaces
7.1Interfaces concerning Network Services
7.2Interfaces concerning Virtualised Network Functions
7.3Interfaces concerning virtualised resources
7.4Policy administration interface
7.5Network Forwarding Path management interface
7.6NFVI hypervisor management interface
7.7NFVI compute management interface
7.8NFVI networking management interface
7.9Interfaces exposed between different service providers

8

Annex A (informative): VNF Instance management and orchestration case study
8.1A.1 IMS MRF management and orchestration case study
8.2A.2 Network Service fault Management case study

9

Annex B (informative): VNF lifecycle management
9.1B.1 Introduction
9.2B.2 VNF Package on-boarding flows
9.3B.3 VNF instantiation flows
9.4B.4 VNF instance scaling flows
9.5B.5 VNF instance termination flows
9.6B.6 NFV fault management

10

Annex C (informative): Network Service lifecycle management flows
10.1C.1 Introduction
10.2C.2 Network Service on-boarding flows
10.3C.3 Network Service instantiation flows
10.4C.4 Network Service instance scaling
10.5C.5 Network Service instance update flows due to VNF instance modification
10.6C.6 Network Service instance termination flows
10.7C.7 VNF Forwarding Graph lifecycle management flows

11

Annex D (informative): Orchestration flows
11.1D.1 Introduction
11.2D.2 NFVI-PoP setup and configuration
11.3D.3 Resources provisioning/de-provisioning

12

Annex E (informative): VNFD/NSD representations using TOSCA
12.1E.1 Describing IMS MRF with TOSCA

13

Annex F (informative): YANG/XML VNFD & NSD model
13.1F.1 Use Cases of Network Service with Physical Network Functions
13.2F.2 Examples
13.3F.3 YANG schema

14

Annex G (informative): TM Forum SID service model

15

Annex H (informative): Open Virtualisation Format

16

Annex I (informative): Other information
16.1I.1 OpenStack

17

Annex J (informative): Authors & contributors

1   Introduction

This document describes to what extent the SAPC implementation of Network Functions Virtualisation (NFV) role conforms with the ETSI GS NFV-MAN 001 V1.1.1 (2014-12) standard with the exemptions or additions stated in this document.

2   General Considerations

This document is structured following the chapters of the ETSI GS NFV-MAN 001 V1.1.1 (2014-12) standard.

Please note that the compliance statements for the specifications referenced in the Group Specification (GS) are not in the scope of this SoC.

The following terms explain the columns in the fill-in tables in the document:

Qualifier Defines whether the implementation of a certain entity is Mandatory (M), Optional (Op) or Conditional (C).
Compliance Defines whether the implementation of a certain entity is Compliant by the system.
Comment It may contain additional information.
No requirement (NR) The GS statement contains general information for the understanding of other statements not applicable to the SAPC (the statements may be applicable for other nodes).

One of the following statements (with the associated interpretation) is given to each of the requirements of the Group Specification:

Not compliant (NC) The GS statement is not fulfilled.
Compliant (C) All of the GS statements are fulfilled.
Partially compliant (PC) Not completely all of the GS statements are fulfilled, the exceptions are described.

In this context, 'is/shall/will' statements are considered as mandatory, 'may' statements are considered as optional, and 'can' statements are considered as conditional.

3   Scope, References and Abbreviations

3.1   Scope

No requirement

3.2   References

No requirement

3.3   Definitions and Abbreviations

3.3.1   Definitions

No requirement

3.3.2   Abbreviations

No requirement

4   NFV Management and Orchestration: objectives and concepts

4.1   Overview

No requirement

4.2   Management and Orchestration aspects of Network Functions Virtualisation Infrastructure

No requirement

4.3   Management and Orchestration aspects of Virtualised Network Functions

No requirement

4.4   Management and Orchestration aspects of Network Services

No requirement

4.5   Other management and orchestration aspects of NFV framework

No requirement

4.6   Relation of NFV management and orchestration with existing operations and management systems

No requirement

4.7   Administrative Domains

No requirement

5   Management and Orchestration architectural framework

5.1   Overview

No requirement

5.2   Principles of NFV-MANO

No requirement

5.3   NFV-MANO architectural framework overview

No requirement

5.4   NFV-MANO architectural framework functional blocks

No requirement

5.5   Other functional blocks

No requirement

5.6   Network Controllers

No requirement

5.7   NFV-MANO reference points

No requirement

5.8   Interfaces description approach

No requirement

6   NFV management and orchestration information elements

6.1   Introduction

No requirement

6.2   Network Service information elements

No requirement

6.3   Virtualised Network Function information elements

No requirement

6.3.1   VNF Descriptor (vnfd)

Not compliant

The SAPC VNF descriptor provided is not aligned to the information elements that are described in this section of the document. Currently, the SAPC provides a descriptor used by the Ericsson Cloud Manager.

TOSCA for NFV is aligned to the descriptor shown in this document. The SAPC is planning to provide a descriptor based on TOSCA for NFV.

6.3.2   VNF Record (vnfr)

No requirement

6.4   Virtual Link information elements

No requirement

6.5   Virtualised Network Function Forwarding Graph information elements

No requirement

6.6   Physical Network Function information elements

No requirement

6.7   VNF Instantiation input parameter

No requirement

6.8   Network Service Instantiation Input Parameters

No requirement

7   NFV-MANO interfaces

No requirement

7.1   Interfaces concerning Network Services

No requirement

7.2   Interfaces concerning Virtualised Network Functions

No requirement

7.3   Interfaces concerning virtualised resources

No requirement

7.4   Policy administration interface

No requirement

7.5   Network Forwarding Path management interface

No requirement

7.6   NFVI hypervisor management interface

No requirement

7.7   NFVI compute management interface

No requirement

7.8   NFVI networking management interface

No requirement

7.9   Interfaces exposed between different service providers

No requirement

8   Annex A (informative): VNF Instance management and orchestration case study

8.1   A.1 IMS MRF management and orchestration case study

No requirement

8.2   A.2 Network Service fault Management case study

No requirement

9   Annex B (informative): VNF lifecycle management

9.1   B.1 Introduction

No requirement

9.2   B.2 VNF Package on-boarding flows

No requirement

9.3   B.3 VNF instantiation flows

No requirement

9.4   B.4 VNF instance scaling flows

No requirement

9.5   B.5 VNF instance termination flows

No requirement

9.6   B.6 NFV fault management

No requirement

10   Annex C (informative): Network Service lifecycle management flows

10.1   C.1 Introduction

No requirement

10.2   C.2 Network Service on-boarding flows

No requirement

10.3   C.3 Network Service instantiation flows

No requirement

10.4   C.4 Network Service instance scaling

No requirement

10.5   C.5 Network Service instance update flows due to VNF instance modification

No requirement

10.6   C.6 Network Service instance termination flows

No requirement

10.7   C.7 VNF Forwarding Graph lifecycle management flows

No requirement

11   Annex D (informative): Orchestration flows

11.1   D.1 Introduction

No requirement

11.2   D.2 NFVI-PoP setup and configuration

No requirement

11.3   D.3 Resources provisioning/de-provisioning

No requirement

12   Annex E (informative): VNFD/NSD representations using TOSCA

12.1   E.1 Describing IMS MRF with TOSCA

No requirement

13   Annex F (informative): YANG/XML VNFD & NSD model

13.1   F.1 Use Cases of Network Service with Physical Network Functions

No requirement

13.2   F.2 Examples

No requirement

13.3   F.3 YANG schema

No requirement

14   Annex G (informative): TM Forum SID service model

No requirement

15   Annex H (informative): Open Virtualisation Format

No requirement

16   Annex I (informative): Other information

16.1   I.1 OpenStack

No requirement

17   Annex J (informative): Authors & contributors

No requirement