Guilin Release Key Updates
- cl664y@att.com
- Trevor Lovett
- Zu Qiang
This table shows use case blueprints:
Use Case Blueprint | Sub-Blueprint | Key Updates | Benefits |
5G | OOF SON (PCI) | First steps towards realizing Machine Learning (ML) based SON. Offline trained ML model used to provide additional inputs for PCI optimization. Provides interface for fetching PM data to determine additional inputs for optimization related to SON. | Benefits of OOF SON use case: A modular and generic control-loop based framework to realize various SON functions. The interfaces and network models are aligned with 3GPP and O-RAN. Increment in Guilin Enables onboarding ML models to realize ML-based SON use cases. This facilitates use of ML to determine the optimization model to be used, and to provide additional inputs for the optimization engine. |
Service Modeling & Definition | This use case incorporated the 5G RAN Wireless Network Resource Model (NRM) into ONAP. The 5G NRM is defined from the 3GPP standards 3GPP TS28.540 & 3GPP TS28.541 which builds upon the FNIM, UIM specified in 3GPP TS28.620 and TS28.622 The 5G NRM is a common vendor agnostic network model inspired from the standards which provides a common basis for all wireless vendors to have a set of parameters that are in common across the vendor so that service providers have a more uniform set of objects, parameters and models to represent a wireless network. | Allows for RAN Wireless vendors to use standardized 3GPP support TS28.540/TS28.541 5G NRM parameters | |
Standards Alignment: StndDefined VES Event | Development of support for Standard Defined (stndDefined) VES Event. This new domain of a VES event would allow ONAP to support many more standards based & standards defined messages. It opens the possibility for ONAP to support a wide variety of messaging from Optical, Wireless, Core and Transport standards. "stndDefined" is a new VES domain. And it is described in the VES 7.2 specification VES 7.2 and also in the readthedocs. It also introduces a new field "namespace" to be published onto the DMaaP bus which allows for internal routing of the information coming from xNFs. For example 3GPP_Configuration would indicate a CM type information coming from an xNF. | Allows for Standards Bodies such as 3GPP (RAN Wireless) alignment and support of messaging from xNF messages defined by standards to be compatible with ONAP | |
Standards Alignment: A1 |
| CCSDK/SDNC now supports managing A1 Policies, multiple A1 targets in the RAN, multi-version support for different A1 targets, converged DMaaP & REST interfaces, and secure communication (to/from RAN and to/from ONAP functions. Functionality is now available for use in further use cases in ONAP H+. Functionality available for standalone use, or in a larger ONAP deployment. Available for use in O-RAN OSC. | |
5G NRM (CM) | (No Updates in R7) | ||
E2E Network Slicing |
|
| |
Bulk PM: PM Control | PM data collection control provides 5G network operators with a dynamic and more efficient way to configure performance measurement collection on a selected subset of PNFs/VNFs in the network and complements the existing PM data collection and processing capabilities in ONAP/DCAE. An initial version has been delivered in Rel 6 (5G / Bulk PM / PM Control - REQ-129). Planned enhancements for Rel 7 intend to further increase the capability and the dynamicity of this feature. | PM control is a critical business function because it is vital to enable the PM data collection in ONAP | |
Intent Based Network |
|
| |
PNF | PNF Plug-and-Play | Development of Building Blocks in SO to support PNF Plug and Play Flow. Migration of BPMN Workflow to Building Blocks (BB). These include the "AssignPnfBB", "WaitForPnfReadyBB", "ConfigAssignPnfBB" and "ConfigDeployPnfBB", "ActivatePnfBB". Note: that in R8 will see the development of the VID work to compliment the SO BB work completed in R7. Modeling analysis of Geolocation and Place objects driven from RFC6225 and MEF TM GB922 standards. Model contributions have been approved. | Internal SO development to streamline execution of PNF Plug and Play. Migration of BPMN Workflow to Building Blocks allows for much more streamlined management of SO workflow execution. |
Onboarding/Pre-onboarding | Enhanced package security ETSI SOL004 option 2 security implemented | Enhanced entire package security Aligned now with ETSI SOL004 standrads. | |
PNF software upgrade | A schema update in relation to a xNF software upgrades is a routine for network upgrade to support new xNF features, improve efficiency or increase xNF capacity on the field, and to eliminate bugs. This use case provides to ONAP an advantage in orchestrating and managing the Life Cycle of a Network Services in-line with business and service objectives. | Deployment and orchestration of new services over CNFs, VNFs and PNFs in a model and software driven way simplifies the network management. Enables operators and service providers to manage the Life Cycle of a Network Service. Assuring continuity of operation of services is crucial for production and carrier grade environments. The actualization or upgrades of software and in consequence required changes in the service model is a natural part of service instance life cycle. Without the support of ONAP service update with schema change, service life cycle management by ONAP can be very difficult which can impact the quality and continuity of services. | |
Configuration Persistence Service (CPS) | (Note this has been renamed to Configuration Persistence Service) CPS PROOF OF CONCEPT Proof of Concept developed in R7 to demonstrate key concepts in CPS and also to lay foundational software for CPS. The PoC has:
CPS STAND ALONE PROJECT (in R8) Presented Project proposal at architecture sub-committee and TSC: Configuration Persistence Service Project in R7 timeframe. Is has been approved to be a stand-alone project in R8 (Honolulu Release) STATE MANAGEMENT POC State Management PoC was created to store the current state of the network elements in a network. | BENEFITS OF CPS CPS introduces a data layer into ONAP to store and manage Network Element Data. CPS provides a centralized, single, persistent data across all vendors. It allows for the data to be exposed such that different upper level applications (e.g. SON, orchestration, LCM functions) can use CPS data. The CPS is real-time and up-to-date. It facilitates the push & pull of configuration data that is policy driven. CPS is an embodiment of "Golden configurations" which is a solution for an up-to-date unified configuration database sending configuration changes. Before CPS existed, service providers have to struggle with many disparate databases which begs to be harmonized and integrated. BENEFITS OF CPS PROOF OF CONCEPT Proof of Concept developed in R7 to demonstrate key concepts in CPS and also to lay foundational software for CPS. BENEFITS OF CPS AS STAND ALONE PROJECT CPS as a stand-alone project in R8 Honolulu will allow CPS to have its own stand-alone repository and facilitate component interaction to CPS. BENEFITS OF STATE MANAGEMENT POC State information facilitates the recovery of failed assets and tracking the states of elements in a service provider's network. | |
CMPv2 | CMPv2 is a standardized certificate based exchange protocol to introduced enhanced security in ONAP. It allows for intra-component security and affect many components. CMP is a protocol for X.509 digital certificate management in a PKI described in RFC4210. And is one of the protocols used for Certificate Request Message Format (CRMF) described in RFC4211. | CMPv2 introduced standardized certificate exchange security into ONAP. | |
xNF License Management | xNF Licensing Management enhancements allows for ONAP to work with an external licensing service. Link to high level description of the solution. Integrated flow into Plug and Play Use Case. 5G - PNF Plug and Play | Possibility to use external licensing service allows for greater interoperability between service providers & vendors, and enables various types of xNF commercial licensing models: simpler, more complex, vendor specific and operator specific models. | |
MDONS Extension | Improvements on MDONS use-case with additional features
| MDONS blueprint is enhanced with additional functionality that enables policy-driven automated service operations. The optimization framework facilitates improved service lifecycle management across cross-carrier optical domains enabling vendor interoperability. | |
ETSI Alignment | The following ETSI-Alignment enhancements are made:
| ONAP supports SOL007 NS design which enables hierarchical orchestration by conforming ETSI NS and VNF standards. ONAP NS and NsVirtualLink are now conforming to ETSI standards. SO NFVO enables plugin-based extension of NFVO functions on top of default NFVO functions. | |
Here is a list of a few subcommittees (use-case, architecture, security), OVP, and other activities.
Subcommittee | Key Updates | Benefits |
Arch | ||
Cloud Native | For Guilin release there are introduced key changes that deployment of CNFs with ONAP more operational and they enable Day-0/1 CNF operations. The changes include:
| The introduced changes bring the following benefits:
|
Control Loop | The Control Loop sub committee led the functional requirement to add a new Filter Guard Policy Type. In addition, the subcommittee ensured that the Native Policy Type work developed in Frankfurt was fully tested through the CLAMP interface. The sub committee continues to support the DCAE Project Self-Serve control loop enhancements Proof-of-Concept. The PoC made improvements to MOD (NiFi) and configuration for dynamic topic support. A new Proof-of-Concept was started by the subcommittee to define TOSCA-Based Control Loops. This work was demonstrated at the fall LFN Technical Conference. | The new Filter Guard Policy Type is another guard policy available for ONAP users to use in addition to the others that have been available since Dublin. This allows filters to build more flexible constraints to both whitelist and/or blacklist vnf types, specific vnf id's, services, etc. In defining a TOSCA specification for Control loops, users can now encapsulate all the details of a control loop within one specification. These specifications are re-usable. CLAMP will eventually be able to be fed a TOSCA specification, and with minimal effort be able to configure and deploy a control loop into the runtime environment. |
Modeling | The modeling subcommittee updates the ONAP VNFD model to align with ETSI NFV IFA011 v2.7.1, supporting key features like virtual ip, VNF exposed interface, etc. The subcommittee also adds a new model for location information. Taking consideration of multiple existing standards, including ETSI NFV SOL001, RFC4776 and RFC6225, the new model enables an entity to provide its geographical location information. | Update of the VNFD model to the latest ETSI NFV spec allows ONAP to incooperate new features defined in standards. The new locations model enables entity such as PNF to provide its geographical information, allowing further scheduling and optimization procedures. |
ONAP Security Coordination | The subcommittee continued efforts on upgrading packages to the SECCOM recommended versions as well as upgrading the java (v8 → v11) and python (v2.7 → 3.8) versions. CII Badging information: 1) https://wiki.onap.org/display/Meetings/PTL+2020-11-16?preview=%2F92998580%2F93000904%2FCelebrate-CII-Badging.pdf | Progress with package and Java, Python upgrades Progress with decrease of pods running as root Migration towards https and default use of https |
Open Lab | N/A | |
Requirements | The existing use cases and requirements were significantly extended and functionality was added. The major additions include PNF support extensions, cloud native support extensions, network slicing support extensions, and ETSI SOL1, SOL3, SOL5, SOL5 and SOL7 enrichment | Network slicing would be able to deploy in 5G by using ONAP, with internal nd external NSSMFs, CSMF and NSMF; any combination of PNF, VNF, CNF would be applicable for any use case deployment will be enabled by standardized ETSI SOL functionalities |
VNF Validation Subcommittee and OVP | ||
Other Activities | ||
Controller Design Studio (CDS) |
|
|
K8s Plugin |
|
|
Finally, here is a list of S3P activities (security, documentation covered above)
S3P Activity | Key Updates | Benefits |
Stability | N/A - See Guilin Release Platform Maturity | |
Scalability | N/A - See Guilin Release Platform Maturity | |
Performance | N/A - See Guilin Release Platform Maturity | |
Manageability | N/A - See Guilin Release Platform Maturity | |
Resilience | N/A - See Guilin Release Platform Maturity | |
Usability | N/A - See Guilin Release Platform Maturity | |
Code Footprint Reduction | N/A - See Guilin Release Platform Maturity |