ETSI GR NFV-EVE 020 V5.1.1 (2022-10)

Network Functions Virtualisation (NFV) Release 5; Evolution and Ecosystem; Report on NFV support for Network Function Connectivity eXtensions

DGR/NFV-EVE020

General Information

• Status: Not Published
• Technical Committee: NFV EVE - Evolution and Ecosystem
• Current Stage: 12 - Completion
• Due Date: 21-Oct-2022
• Completion Date: 05-Oct-2022

Standards Content (Sample)

GROUP REPORT
Network Functions Virtualisation (NFV) Release 5;
Evolution and Ecosystem;
Report on NFV support for Network Function
Connectivity eXtensions
Disclaimer
The present 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.

2 ETSI GR NFV-EVE 020 V5.1.1 (2022-10)

Reference
DGR/NFV-EVE020
Keywords
MANO, network, NFV, virtualisation

ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

Siret N° 348 623 562 00017 - APE 7112B
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° w061004871

Important notice
The present document can be downloaded from:
http://www.etsi.org/standards-search
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 prevailing version of an ETSI
deliverable is the one made publicly available in PDF format at www.etsi.org/deliver.
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
https://portal.etsi.org/TB/ETSIDeliverableStatus.aspx
If you find errors in the present document, please send your comment to one of the following services:
https://portal.etsi.org/People/CommiteeSupportStaff.aspx
If you find a security vulnerability in the present document, please report it through our
Coordinated Vulnerability Disclosure Program:
https://www.etsi.org/standards/coordinated-vulnerability-disclosure
Notice of disclaimer & limitation of liability
The information provided in the present deliverable is directed solely to professionals who have the appropriate degree of
experience to understand and interpret its content in accordance with generally accepted engineering or
other professional standard and applicable regulations.
No recommendation as to products and services or vendors is made or should be implied.
No representation or warranty is made that this deliverable is technically accurate or sufficient or conforms to any law
rule and/or regulation and further, no representation or warranty is made of merchantability or fitness
and/or governmental
for any particular purpose or against infringement of intellectual property rights.
In no event shall ETSI be held liable for loss of profits or any other incidental or consequential damages.

Any software contained in this deliverable is provided "AS IS" with no warranties, express or implied, including but not
limited to, the warranties of merchantability, fitness for a particular purpose and non-infringement of intellectual property
rights and ETSI shall not be held liable in any event for any damages whatsoever (including, without limitation, damages
for loss of profits, business interruption, loss of information, or any other pecuniary loss) arising out of or related to the use
of or inability to use the software.
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.

© ETSI 2022.
All rights reserved.
ETSI
3 ETSI GR NFV-EVE 020 V5.1.1 (2022-10)
Contents
Intellectual Property Rights . 4
Foreword . 4
Modal verbs terminology . 4
1 Scope . 5
2 References . 5
2.1 Normative references . 5
2.2 Informative references . 5
3 Definition of terms, symbols and abbreviations . 5
3.1 Terms . 5
3.2 Symbols . 5
3.3 Abbreviations . 5
4 Overview . 6
5 Use Cases . 6
5.1 Inter-Site Multiple VNFs/VNFCs Connectivity via Dyncast . 6
5.1.1 Motivation. 6
5.1.2 Detailed User Story . 7
5.1.2.1 Summary . 7
5.1.2.2 Actor(s) . 7
5.1.2.3 Pre-Conditions . 7
5.1.2.4 Description . 8
5.1.2.5 Post-Conditions . 8
5.1.3 Analysis . 9
5.2 Intra-Site Multiple VNFs/VNFCs Connectivity via Dyncast . 9
5.2.1 Motivation. 9
5.2.2 Detailed User Story . 10
5.2.2.1 Summary . 10
5.2.2.2 Actor(s) . 10
5.2.2.3 Pre-Conditions . 11
5.2.2.4 Description . 11
5.2.2.5 Post-Conditions . 12
5.2.3 Analysis . 12
6 Analysis . 13
7 Recommendations . 13
8 Conclusions . 13
History . 14

ETSI
4 ETSI GR NFV-EVE 020 V5.1.1 (2022-10)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The declarations
pertaining to these essential IPRs, if any, are 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 (https://ipr.etsi.org/).
Pursuant to the ETSI Directives including the ETSI IPR Policy, no investigation regarding the essentiality of IPRs,
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.
Trademarks
The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners.
ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no
right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does
not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks.
DECT™, PLUGTESTS™, UMTS™ and the ETSI logo are trademarks of ETSI registered for the benefit of its

Members. 3GPP™ and LTE™ are trademarks of ETSI registered for the benefit of its Members and of the 3GPP
Organizational Partners. oneM2M™ logo is a trademark of ETSI registered for the benefit of its Members and of the ®
oneM2M Partners. GSM and the GSM logo are trademarks registered and owned by the GSM Association.
Foreword
This Group Report (GR) has been produced by ETSI Industry Specification Group (ISG) Network Functions
Virtualisation (NFV).
Modal verbs terminology
In the present document "should", "should not", "may", "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
5 ETSI GR NFV-EVE 020 V5.1.1 (2022-10)
1 Scope
The present document studies the integration of Dyncast in the NFV architectural framework. Dyncast despatches data
flows according to network status and computing resources. The impact on NFV such as necessary extensions of
NFV-MANO components is analysed.
2 References
2.1 Normative references
Normative references are not applicable in the present document.
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 term validity.
The following referenced documents are not necessary for the application of the present document but they assist the
user with regard to a particular subject area.
[i.1] ETSI GS NFV-IFA 011 (V3.3.1): "Network Functions Virtualisation (NFV) Release 3;
Management and Orchestration; VNF Descriptor and Packaging Specification".
[i.2] ETSI GR NFV 003: "Network Functions Virtualisation (NFV); Terminology for Main Concepts in
NFV".
[i.3] ETSI GS NFV-TST 008 (V3.3.1): "Network Functions Virtualisation (NFV) Release 3; Testing;
NFVI Compute and Network Metrics Specification".
3 Definition of terms, symbols and abbreviations
3.1 Terms
For the purposes of the present document, the terms given in ETSI GR NFV 003 [i.2] apply.
3.2 Symbols
Void
3.3 Abbreviations
For the purposes of the present document, the abbreviations given in ETSI GR NFV 003 [i.2] and the following apply:
NOTE: An abbreviation defined in the present document takes precedence over the definition of the same
abbreviation, if any, in ETSI GR NFV 003 [i.2].
NFCX Network Function Connectivity eXtensions
ETSI
6 ETSI GR NFV-EVE 020 V5.1.1 (2022-10)
4 Overview
The present document presents Dyncast in order to improve resource optimization, which dynamically dispatches
packets based on computing resources and network status.
Traditional networks provide unicast, multicast, and broadcast, which are widely used. Network Function Connectivity
eXtensions (NFCX) introduces the extension of network connectivity capabilities to benefit distributed computing
systems. The NFCX can be regarded as a new communication model by combining computing and network resources
to efficiently convey the multi-point-to-multi-point traffic model. The typical examples include the Dyncast,
Convergecast and Collectivecast.
Dyncast assumes there are multiple equivalent VNF instances which provide the same service. These VNF instances are
deployed on different NFVI-PoPs or the same NFVI-PoP. Meanwhile, these instances are interconnected and
collaborate with each other to achieve a holistic objective. When a service request arrives, the first packet of this data
flow is delivered to the proper VNF instance according to computing resource consumption and network status. The
subsequent packets from the same flow follow the first one.
Clause 5 gives details of use cases, where clause 5.1 introduces the use case that VNF instances are deployed on
different NFVI-PoPs and clause 5.2 describes the use case that VNF instances are on the same NFVI-PoP. Clause 6
presents analysis of use cases. Clauses 7 and 8 show recommendations and conclusions of the present document
respectively.
5 Use Cases
5.1 Inter-Site Multiple VNFs/VNFCs Connectivity via Dyncast
5.1.1 Motivation
This use case describes that Dyncast performs inter-site dynamic network connectivity between multiple equivalent
VNFs. It is assumed that the multiple VNFs are deployed in different NFV-PoPs.
Figure 5.1.1-1 illustrates a high-level architecture for inter-site VNFs connectivity via Dyncast.

Figure 5.1.1-1: Inter-site VNFs connectivity via Dyncast
In this case, multiple equivalent VNF instances deployed in different NFV-PoPs are abstracted and virtualised into one
group to provide a unified virtual interface for users. Dyncast performs dynamic connectivity, optimal selection and
dispatching between different VNF instances which form a pool of virtual network functions.
ETSI
7 ETSI GR NFV-EVE 020 V5.1.1 (2022-10)
In this case, using Dyncast is close to introducing a load balancer implemented at the NFVI level. Dyncast directs traffic
between different NFVI-PoPs to support cross-site VNFs collaboration, which means that a proper site can be selected
through Dyncast during session establishment, and/or a session of one site can be shifted to other sites through Dyncast
during the session duration phase in case the original site fails to work properly, e.g. network congestion.
Therefore, multiple equivalent VNF/VNFC instances distributed across multiple sites and interconnected via Dyncast
can achieve better scalability, utilization efficiency of system resources and service performance through collaboration.
5.1.2 Detailed User Story
5.1.2.1 Summary
In this case, multiple equivalent VNF instances are deployed in different NFVI-PoPs and considered as one group to
provide one kind of service for clients. Dyncast performs dynamic connectivity between clients and different VNF
instances according to computing resources and network status.
5.1.2.2 Actor(s)
Table 5.1.2.2-1 describes the use case actors and roles.
Table 5.1.2.2-1: Use case #1, actors and roles
# Actor Description
1 NFV-MANO1 NFV-MANO1 managing the NFVI (site1) hosting all resources involved
2 NFV-MANO2 NFV-MANO2 managing the NFVI (site2) hosting all resources involved
3 VNF instance1 VNF instance1 is the first possible target
4 VNF instance2 VNF instance2 is the second possible target
5 Dyncast function instance1 Dyncast function instance1 implementing Dyncast functionality at site 1. See note
6 Dyncast function instance2 Dyncast function instance2 implementing Dyncast functionality at site 2
7 Client The user who sends a request of network function, and a client can be a network
function connected to an NFV environment
NOTE: The Dyncast function instance1 performs dynamic and anycast network connectivity, which dynamically direct
flows coming from client to a suitable instance of the VNF.

5.1.2.3 Pre-Conditions
Table 5.1.2.3-1 describes the pre-conditions.
Table 5.1.2.3-1: Use case #1, pre-conditions
# Pre-condition Description
1 VNF instance1 and VNF instance2 implementing the same function
are instantiated at site1 and site2 respectively.
2 Dyncast function instance1 and Dyncast function instance2 are
deployed and running at site1 and site2 respectively.
3 NFV-MANO1 and NFV-MANO2 are both running.
4 NFV-MANO1 notify Dyncast function instance1 about the network
function information when VNF instance1 is instantiated.
...