Description

5G RAN physical/logical topology information (SDN-R) Core & RAN elements. 5G Configuration, provisioning of a 5G Network. SDN-R should contain the 5G Network Topology. CM Audit. CM Mediation. CM run-time storage / data persistency (MariaDB)

Nov 15, 2019 - it was decided that the RunTime Config DB will be part of CCSDK in R6. The new project proposal as RunTime Config DB will be for R7, but it is being worked on in the R6 timeframe.

BUSINESS DRIVER

This section describes Business Drivers needs.

Executive Summary - 5G RAN physical/logical topology information (SDN-R) Core & RAN elements. 5G Configuration, provisioning of a 5G Network. SDN-R should contain the 5G Network Topology. CM Audit. CM Mediation. CM run-time storage / data persistency (MariaDB). Configuration Management is a major LCM/OAM function with many operations. This use case will be a multi-release effort.

• Data Persistency - Storage of run-Time data storage. A configuration database (such as Maria DB) for data persistency and access to configuration information.

Business Impact - The ability to configure a RAN network (CU/DU) PNF and VNF with ONAP is a critical business function because configuration management is a core LCM/OAM operation.

Business Markets - This use case applies to any domain (wireless, transport, optical, wireline) that ONAP will manage. It is not a market specific function.

Funding/Financial Impacts - This use case represents a large potential OPEX savings for operators because of the ability to configure networks saving time and expenses.

Organization Mgmt, Sales Strategies - There is no additional organizational management or sales strategies for this use case outside of a service providers "normal" ONAP deployment and its attendant organizational resources from a service provider.

Other CM Topics (future releases)

• CM Audit - Auditing configuration parameters for consistency, accuracy.

• CM Mediation - Configuration functions to correct and mediate settings.

• Data Persistency - Storage of run-Time data storage. A configuration database (such as Maria DB) for data persistency and access to configuration information.

• Topology Management - the configuration and view of a RAN network topology.

• Standardizing - Harmonizing management between vendors, and alignment to standards bodies such as 3GPP for CM topics.

• Golden Standard - Managing CM with Golden "Templates" and base-lined parameters.

DEVELOPMENT IMPACTS

The REQ (requirements) epic for this Use Case is 

https://lf-onap.atlassian.net/browse/REQ-267

NOTE: 1. Collect Configuration data via Netconf with VES CM notify notification.descoped from R6

2. Support all vendor specific Configuration Information Model ( CIM/Yang) descoped from R6

List of PTLs:Approved Projects

ARCHITECTURE DISCUSSION

The architecture discussion held on Sept 10, 2019 and Sept 3, 2019 centered around the discussion about where the RunTime DB should architecturally live.

some choices are: (1) have RunTime DB as a platform component (2) have it was a part of a controller (3) have it as part of the common services (4) have it as part of CC-SDK (as part of common services).

See the supporting files which has the slides & discussion notes

The WIKI page for ARC RunTime DB Component is at:

ARC RunTime DB Component Description - R6 Frankfurt

MEETINGS

 - 

SUPPORTING FILES:

INTEGRATION & TESTING

This section discusses the Testing & Integration for R6 PnP

1. WHO IS TESTING - what company, team, and people will be doing the testing & responsibilities for testing.

2. TEST ENVIRONMENT - which does the lab & test environment.

3. RESOURCES NEEDED - what resources are needed.

4. WHO IS CONTRIBUTING RESOURCES - what resources will be provided and by whom/what company.

5. NETWORK CONNECTIVITY - Network connectivity

6. TEST/INTEGRATION LEADER -  @Sandeep Shah , @Dongho Kim

7. INTEGRATION LEAD DEFINITION - ONAP "Use Case/Requirement" Integration Lead

RunTime Config DB Integration Test Cases. These can be navigated to from the Integration team page hierarchy.