Runtime Config DB 

(1) Contain the instance/presentation of the real time 5G RAN network for Configuration Database (Runtime DB)

(2) Contain Configuration data including logical objects, logical/physical connection as well as  exo-inventory data

(3) Provide operation view for 5G network

(4) Support the existing use cases e. g  OOF/PCI/SON and Network Slicing, 

(5)  Collect Configuration data via Netconf with VES CM notify notification.

Notes: Runtime Config DB is not duplicate A&AI. A&AI contains the virtual objects /virtual services (VNF, VFC/VF module, P-Server).

Requirements:

SDC: Test Only 

• SDC shall provide the CSAR file and post it to DMaaP as BAU.  

A&AI:  Test Only

• A&AI shall provide initial PNF objects to RunTime Config DB.
• A&AI shall add RunTime Config DB 'mechID to A&AI topic subscriber Role in AAF instances.  

DCAE: Code Impact 

• VES Collector shall add new CM notify event (new CM domain) to VES collector. 
• VES collector shall receive CM notificaiton via O1 notify (Jason interface)
• VES Collector shall post a new CM event to DMaaP 

SDN-R (Code Impact) 

• SND-R shall get CM Event fortification from DMaaP when VES collector posts the CM event to DMaap 
• SDN-R shall get configuration and Yang model from the network device via Netconf and O1 interface.
• SDN-R shall update RunTime DB with configuration data change via an existing rest interface. 

RunTime Config DB: Code Impact

• Leverage Maria DB as mS Runtime Config DB to support the logical data model/devise model.
• Build the data model for real time presentation of 5G network and store the data to the database
• Get All PNFs objects from A&AI
• Receive Config information updates from SDN-R via Nectconf and with VES notification.
• Support all vendor specific Configuration Information Model ( CIM/Yang)