ETSI GS NFV-SWA 001 V1.1.1 (2014-12)

Network Functions Virtualisation (NFV); Virtual Network Functions Architecture

DGS/NFV-SWA001

General Information

• Status: Published
• Publication Date: 22-Dec-2014
• Technical Committee: NFV SWA - Software Architecture
• Current Stage: 12 - Completion
• Due Date: 19-Jan-2015
• Completion Date: 23-Dec-2014

Standards Content (Sample)

ETSI GS NFV-SWA 001 V1.1.1 (2014-12)






GROUP SPECIFICATION
Network Functions Virtualisation (NFV);
Virtual Network Functions Architecture
Disclaimer
This document has been produced and approved by the Network Functions Virtualisation (NFV) ETSI Industry Specification
Group (ISG) and represents the views of those members who participated in this ISG.
It does not necessarily represent the views of the entire ETSI membership.

---------------------- Page: 1 ----------------------
2 ETSI GS NFV-SWA 001 V1.1.1 (2014-12)



Reference
DGS/NFV-SWA001
Keywords
architecture, functional, NFV, requirements
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88

Important notice
The present document can be downloaded from:
http://www.etsi.org
The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the only prevailing document is the
print of the Portable Document Format (PDF) version kept on a specific network drive within ETSI Secretariat.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
http://portal.etsi.org/tb/status/status.asp
If you find errors in the present document, please send your comment to one of the following services:
http://portal.etsi.org/chaircor/ETSI_support.asp
Copyright Notification
No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying
and microfilm except as authorized by written permission of ETSI.
The content of the PDF version shall not be modified without the written authorization of ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.

© European Telecommunications Standards Institute 2014.
All rights reserved.

TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members.
TM
3GPP and LTE™ are Trade Marks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
GSM® and the GSM logo are Trade Marks registered and owned by the GSM Association.
ETSI

---------------------- Page: 2 ----------------------
3 ETSI GS NFV-SWA 001 V1.1.1 (2014-12)
Contents
Intellectual Property Rights . 6
Foreword . 6
Modal verbs terminology . 6
1 Scope . 7
2 References . 7
2.1 Normative references . 7
2.2 Informative references . 7
3 Definitions and abbreviations . 9
3.1 Definitions . 9
3.2 Abbreviations . 10
4 Overview of VNF in the NFV Architecture . 12
4.1 Introduction . 12
4.2 VNF Architecture . 13
4.3 Interfaces . 15
4.3.1 VNF Interfaces and NFV Architectural Framework Reference Points . 15
4.3.2 SWA-1 Interfaces . 17
4.3.3 SWA-2 Interfaces . 18
4.3.4 SWA-3 Interfaces . 18
4.3.5 SWA-4 Interfaces . 19
4.3.6 SWA-5 Interfaces . 19
5 VNF Design Patterns and Properties . 20
5.1 VNF Design Patterns . 20
5.1.1 VNF Internal Structure . 20
5.1.2 VNF Instantiation . 21
5.1.3 VNFC States . 21
5.1.4 VNF Load Balancing Models . 22
5.1.5 VNF Scaling Models . 24
5.1.6 VNF Component Re-Use . 25
5.2 VNF Update and Upgrade . 27
5.2.1 VNF Update and Upgrade Overview . 27
5.2.2 VNF Update & Upgrade Requirements for VNF Provider . 27
5.3 VNF's Properties . 27
5.3.1 Hardware Independence . 27
5.3.2 Virtualisation and Container Awareness. 28
5.3.3 Elasticity . 28
5.3.4 Void . 29
5.3.5 VNF Policy Management . 29
5.3.6 Migration operations . 29
5.3.7 VNF State . 30
5.3.8 VNF Internal Structure . 30
5.3.9 Reliability . 30
5.3.10 Location Awareness . 30
5.3.11 Application Management . 30
5.3.12 Diversity and Evolution of VNF Properties . 31
5.4 Attributes describing VNF's Requirements . 31
5.4.1 VNF Topological Characteristics . 31
5.4.1.1 Deployment Behaviour . 32
5.4.1.1.1 Virtualisation containers . 32
5.4.1.1.2 NFVI Resources . 32
5.4.1.1.3 Components and Relationship . 32
5.4.1.1.4 Location . 32
5.4.1.1.5 Other constraints . 32
5.4.1.2 Operational Behaviour . 32
ETSI

---------------------- Page: 3 ----------------------
4 ETSI GS NFV-SWA 001 V1.1.1 (2014-12)
5.4.1.2.1 Management Operations . 32
6 VNF States and Transitions . 33
6.1 States and Transitions as Architectural Patterns . 33
6.2 VNF Instantiation Overview . 34
6.3 The VNF Descriptor's Role in VNF Instantiation . 35
6.4 VNF Instantiation . 36
6.5 VNFC Instantiation . 37
6.6 VNFC Instance Termination . 37
6.7 VNF Instance Termination . 38
6.8 VNF Instance Scaling . 38
6.8.1 General Aspects . 38
6.8.2 Scaling Triggers . 38
6.8.3 VNF Scale-out . 38
6.8.4 VNF Scale-in . 39
6.8.5 VNF Scale-up . 39
6.8.6 VNF Scale-down . 39
6.9 Start and Stop VNF . 40
6.9.1 Start VNF . 40
6.9.2 Stop VNF . 40
6.10 VNF Instance Configuration . 40
7 VNF Fault Management Overview . 41
7.1 Introduction . 41
7.2 Virtualised resource faults . 41
7.3 VNF faults . 42
8 Functional Requirements on Management and Orchestration . 42
8.1 High Level Requirements to Management and Orchestration . 42
8.1.1 General Management and Orchestration Requirements related to VNF . 42
8.1.2 Management and Orchestration Requirements Related to VNF Lifecycle . 43
8.1.3 Management and Orchestration Requirements Related to Scaling . 43
8.1.4 Management and Orchestration Requirements Related to VNF Maintenance Tasks . 44
8.2 Requirements for VNFD and VNF-FGD Template . 45
8.2.1 General Requirements Related to VNF . 45
8.2.2 General Requirements Related to VNF Forwarding Graphs . 46
8.2.3 Requirements Related to VNF Creation and Termination . 46
8.2.4 Requirements Related to Scaling . 47
9 Functional Requirements on Infrastructure . 47
9.1 Generic Domain Requirements . 47
9.2 Hypervisor Requirements . 48
9.3 Compute Resource Requirements . 49
9.4 Network Resources Requirements. 49
10 VNF Architecture Design Examples . 50
10.1 Faster VNFC . 50
10.2 VNFC to VNFC Communication . 51
10.3 VNFC Memory to VNFC Memory . 53
10.4 Faster Network Access . 53
10.5 Fast Storage Access . 54
10.6 Driver version, Software Updates . 55
10.7 Distributed VNF . 56
10.8 Generic VNFs . 56
10.8.1 Definition and Usage . 56
Annex A (informative): Relationship to SDN. 57
A.1 Introduction to SDN . 57
A.1.1 ONF and SDN . 57
A.1.2 OpenDaylight and SDN . 57
A.1.3 IETF and SDN . 57
A.1.4 ITU-T and SDN . 58
A.1.4.1 Introduction. 58
ETSI

---------------------- Page: 4 ----------------------
5 ETSI GS NFV-SWA 001 V1.1.1 (2014-12)
A.1.4.2 Protocol: SDN control . 58
A.1.5 SDN Architecture Overview . 59
A.2 SDN in NFV Architecture . 60
A.2.1 Overview . 60
A.3 ETSI NFV Use Case and SDN . . 62
A.3.1 L2 Transparent Network Service Chaining with Traffic Steering . 62
A.3.1.1 Problem Description . 62
A.3.1.1.1 L2 Transparent Network Services . 62
A.3.1.1.1.1 Physical Server Deployments . 62
A.3.1.1.1.2 Virtual Server Deployments . 64
A.3.1.2 Solution Description & Relationship to SDN/OF . 65
A.3.1.2.1 SDN/OF virtual switches . 65
A.3.1.2.2 Role of SND/OF in Service Chaining Traffic Steering . 65
A.3.1.3 Requirements to Management and Orchestration . 70
A.3.1.4 Gap Analysis with ONF . 71
Annex B (informative): De/composition Study . 72
B.1 MRF IMS Use Case . 72
B.1.1 Functional Description . 73
B.1.2 Location of FBs within the NFV Architecture . 74
B.1.3 New Interfaces . 74
B.1.4 VNF Identification . 75
B.1.4.1 MRB . 76
B.1.4.2 MRF . 77
B.1.4.3 IMS MRF Deployment . 78
B.1.5 Standardization Gap . 79
B.2 DPI Engine VNFC Use Case . 79
B.2.1 Declination of the DPI Engine . 80
B.2.2 Scalability Benefits. 81
B.2.3 Security and OpEx Benefits . 82
B.3 Virtual Enterprise Gateway Use Case . 82
B.4 TDF as VNF Use Case . 88
B.4.1 Functional Block Description . 89
B.4.2 TDF Functional Blocks within the NFV architecture . 90
B.4.3 Existing interfaces (as per ETSI TS 123 203) . 90
Annex C (informative): Authors & contributors . 91
Annex D (informative): Bibliography . 92
History . 93

ETSI

---------------------- Page: 5 ----------------------
6 ETSI GS NFV-SWA 001 V1.1.1 (2014-12)
Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (http://ipr.etsi.org).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Foreword
This Group Specification (GS) has been produced by ETSI Industry Specification Group (ISG) Network Functions
Virtualisation (NFV).
Modal verbs terminology
In the present document "shall", "shall not", "should", "should not", "may", "may not", "need", "need not", "will",
"will not", "can" and "cannot" are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms
for the expression of provisions).
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.
ETSI

---------------------- Page: 6 ----------------------
7 ETSI GS NFV-SWA 001 V1.1.1 (2014-12)
1 Scope
The present document objective is to identify the most common and relevant software architectural patterns present
when virtualising network functions and therefore to identify and specify functional requirements necessary to enable
such patterns. The information consolidated is reflecting the experience from vendors and operators going through
virtualisation of a number of network functions, with a focus on the use case list provided by the NFV Use Cases GS
document [i.7].
The present document describes the Network Function Virtualisation abstract software architecture comprising of the
following topics:
• Defining the functions, and interfaces of software architecture relative to the NFV overall architecture.
• Supporting Management and Orchestration Functional requirements.
• Supporting Infrastructure requirements.
• Describing best practices for NFV Design.
• Functional Decomposition types and use cases.
The present document does not provide any detailed specification. However, the present document makes reference to
specifications developed by other bodies, gap, and to potential specifications.
2 References
2.1 Normative references
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
referenced document (including any amendments) applies.
Referenced documents which are not found to be publicly available in the expected location might be found at
http://docbox.etsi.org/Reference.
NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee
their long term validity.
The following referenced documents are necessary for the application of the present document.
Not applicable.
2.2 Informative references
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
referenced document (including any amendments) applies.
NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee
their long
...