...
Support for Containerized Network Function orchestration through ONAP service orchestrator
Key Contacts - Seshu Kumar Mudiganti Srinivasa Addepalli Lukasz Rajewski
Executive Summary - Provide CNF orchestration support through integration of K8s adapter in ONAP SO
...
Container Network Function Test Platform (CNTP): OVP 2.0 support and Enable Network Service testing
Key Contacts - user-67d6f
Executive Summary - In ONAP, as part of Container Network Function (CNF) support, its mandatory to add enable the following testing/validation to make sure the given CNF is as per the need.
...
R7 PNF PLUG & PLAY BUILDING BLOCK / WORK-FLOW MANAGEMENT
Key Contacts - Benjamin Cheung Damian Nowak
EXECUTIVE SUMMARY - This requirement will augment the work-flow to building block management within SO for Plug and Play operation. The continues the work started in R6. In R6, some of the SO work-flow to building block work was finished, and in R7 this is enhanced. The description of the "base" work which will be enhanced is shown in the wiki: PNF PLUG and PLAY in R6 Frankfurt
...
R7 PNF PRE-ONBOARDING VNF-SDK VALIDATION
Key Contacts - Benjamin Cheung Damian Nowak Zu Qiang (Ericsson)
EXECUTIVE SUMMARY - This requirement enhances the PNF (Onboarding) / Pre-onboarding use case. This requirement introduces package security Option2 improvements on Signature per artifact on the Vendor delivered package as defined in ETSI NFV SOL004 v2.7.1 section 5.2. The validation of onboarded PM dictionary data based on schema information will be done. The standard can be found here: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/004/02.07.01_60/gs_NFV-SOL004v020701p.pdf . In R4 and R6, Option 1 signature per package was developed but not Option 2.
...
R7 5G PNF SERVICE MODEL INTRODUCTION
Key Contacts - Benjamin Cheung
EXECUTIVE SUMMARY - This requirement introduces platform information model enhancements to document new ISOMII experimental classes from 3GPP TS28.541, the 5G Network Resource Model (NRM).
...
R7 HARMONIZATION: ONAP/3GPP & O-RAN ALIGNMENT–STANDARDS DEFINED NOTIFICATIONS OVER VES
Key Contacts - Marge HillisVimal BegwaniOskar Malm
EXECUTIVE SUMMARY -
-This contribution introduces a new domain in VES, stndDefined, which indicates that the event contains data that conforms to format/schema defined by a separate standards organization1. In addition we propose one new field in the VES Common Header to enable further classification of such events, e g to support routing of these events to appropriate DMaaP topics. An optional second stage validation is proposed in DCAE prior to acknowledging the event to enhance trouble shooting.
...
1) Standards organization is intended to be interpreted in a broader sense than SDO as defined by ITU, to cover also e.g. joint ventures like 3GPP and open industry fora like the O-RAN Alliance.
Intent-based Network
Key Contacts - Huang ZongHe
EXECUTIVE SUMMARY
The Intent-based Network (IBN) is available to bridge the gap between the business department and IT department. It is able to capture the intents of business sensitively, and then reconfigure the end-to-end network according to the intents momentarily. Normally, the operation of underlay network and related systems are involved when opening or reconfiguring a network service. It needs professionals of different roles to perform a series of complex operations, which also takes a long time. The target of IBN is to establish an extensible framework to identify the users' network requirements based on natural language, allocate appropriate resources with the help of preset business knowledge or self-learning intelligent engine, and then convert them into the operations of network equipment and interface automatically, so as to simplify the operations.
...