The practice of NFV decoupling test
draft-long-nfvrg-nfv-decoupling-test-01

Document Type Active Internet-Draft (individual)
Last updated 2019-06-24
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
nfvrg                                                            Y. Long
Internet-Draft                                                   Y. Song
Intended status: Informational                                   Z. Tang
Expires: December 27, 2019                                           BII
                                                           June 25, 2019

                  The practice of NFV decoupling test
                draft-long-nfvrg-nfv-decoupling-test-01

Abstract

   This document mainly introduces the practice of NFV decoupling test.
   Based on the product development situation of the current vendors,
   the decoupling test is carried out between NFVI&VIM, VNFM&VNF and
   NFVO.  Through a series of tests to explore some of the problems
   encountered in the current stage of NFV decoupling testing, provide
   ideas for the subsequent development of NFV products.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on December 27, 2019.

Copyright Notice

   Copyright (c) 2019 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (https://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of

Long, et al.            Expires December 27, 2019               [Page 1]
Internet-Draft       Network Function Virtualization           June 2019

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Decoupling test of NFV  . . . . . . . . . . . . . . . . . . .   4
     3.1.  Introduce of NFV decoupling test  . . . . . . . . . . . .   4
     3.2.  NFV decoupling test architecture  . . . . . . . . . . . .   5
   4.  Decoupling test of NFV  . . . . . . . . . . . . . . . . . . .   5
   5.  Informative References  . . . . . . . . . . . . . . . . . . .   6
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   7

1.  Introduction

   3GPP has adopted the R15 standard and the SBA (Service Based
   Architecture) architecture, which further splits multiple NFs(Network
   Functions) in the 5G core network into multiple NFS (Network Function
   Service), each NFS has the characteristics of independent autonomy.
   But the existence of multiple NFSs in the clouded NFV also brings
   compatibility problems.  Therefore, one of the key requirements of
   the 5G core network for the clouded NFV platform is open.  The cloud
   platform needs to implement decoupling deployment and network
   resource sharing, thus not only avoiding the lock-up of single-
   vendors but also can build an open ecosystem based on open source
   projects.

   But, there are still many problems in the decoupling of the clouded
   NFV platform.  The interfaces of different vendors are not
   standardized and are not unified, which makes it difficult for the
   components of the NFV platform to properly connect and provide
   complete services.  According to the [ETSI_GS_NFV_002], it divides
   the NFV into multiple modules as shown in Figure 1.

   o  Virtualized Network Function (VNF).

   o  Element Management (EM).

   o  NFV Infrastructure, including: Hardware and virtualized resources,
      and Virtualization Layer.

   o  Virtualized Infrastructure Manager(s) (VIM).

   o  NFV Orchestrator.

   o  VNF Manager(s).

Long, et al.            Expires December 27, 2019               [Page 2]
Internet-Draft       Network Function Virtualization           June 2019

   o  Service, VNF and Infrastructure Description.  Operations and
      Business Support Systems (OSS/BSS).

                                                  +--------------------+
   +-------------------------------------------+  | +--------------+   |
   |                 OSS/BSS                   |  | | NFV          |   |
   +-------------------------------------------+  | | Orchestrator +-+ |
Show full document text