...

A VES event (CM Notify) is received by the DCAE VES collector sent from the PNF

2. VES Collector – VES Collector gets the CM Notify

VES Collector gets the CM Notify

3. Publish on DMaaP – VES Collector publishes on the event onto DMaAP

VES Collector Publishes on DMaaP with the CMNotify Topic

43. Subscription on DMaaP – DMaaP RunTime Config DB gets the Notification

RunTime Config DB gets the Event and updates subscribes to the Event.

In the initial release (R6), the RunTime Config DB will use SDN-C's DMaaP listener capability; but the goal is that RunTime Config DB is a separate independent component so it would have its own DMaaP Listener.

4. Updates DB – The RunTime Config DB is updated with the information

The RunTime Config DB is updated with the information

3.1 FLOW 2: xNF Addition/Delete A&AI Update Flow - Updates to RunTime DB

...

AAI determines a xNF has been removed/added from the network. Thus, downstream ONAP components need to be aware of this change in the network.

23. AAI publishes on DMaaP – AAI publishes on DMaAP

AAI publishes on DMaaP A&AI Notify, that a xNF status has changed.

34. Subscription on DMaaP – DMaaP gets the Notification

RunTime Config DB subscribes to that event; and so, gets the AAI updates the information.

4. Updating the RunTime Config DB – The RunTime Config DB is update.

REMOVAL - RunTime DB removes the record for that xNF

ADDITION - If AAI determines that a new xNF is added to the network, then RunTime DB needs to setup a new record for that xNF with the default data structure and configuration. Default Configuration is setup. . For a new xNF a pre-defined schema record is used for that xNF. Some information may come from A&AI. Other values will be discovered during operation. Some information data may have default values defined in the schema.

3.1 FLOW 3: mS/Controller Operational Info Update Flow - Writing to RunTime DB

...

@startuml
participant mS
participant DMaaP
participant RunTimeDB 
autonumber 

group RUNTIMEDB UPDATE
	hnote over mS : Info Update Notification
    mS -> mS : Determines xNF Update
	mS -> DMaaP : Notification 	
end

group Run Time DB Writing
	hnote over mS : Notification
	mS -> DMaaP : Update Notification 
    DMaaP -> RunTimeDB : Subscription
	hnote over RunTimeDB : Updates xNF Update
	RunTimeDB -> RunTimeDB : Updates xNF Information 
end

@enduml

...

1. Micro Service Determines Update Needed – fPackage.

There are multiple wayf system or any other conceivable way to deliver digital information.

2. PxY – Package is accepted into ONAP

the Vendor provided package is imported by a Technology Specialist/Asset manager into SDC.

4. Post Conditions

4a. Post Condition (Pre-onboarding)

The post-conditions for the pre-onboarding flow are the following. Once, pre-onboarded, the xNF is ready for onboarding.

• PACKAGE VALIDATED - VNF-SDK has successfully validated the package (as a result of pre-onboarding) and verified the content that VNF-SDK can perform validation on (See the VNF-SDK Validation section).
• Package SECURITY VALIDATION - The onboarding package is tested and validated for security.
• Artifacts SECURITY VALIDATION - The artifacts of the onboarding package are tested and validated for security.

...

The mS determines an update is necessary.

The micro service during operation determines an update is needed and action needs to be taken.

When this happens, it will publish onto the DMaaP Bus.  Composes policy guidance. When that request comes in the controller, makes a config change on the underlying xNF device, with a successful outcome, it then determines that an update to the Runtime Config DB needs to be updated.

2. mS publishes on DMaaP – Publish onto DMaaP

The mS publishes an event on to the DMaaP Bus.

3. Subscription to DMaaP – Subscription from DMaaP

The RunTime Config DB Receives the event from the DMaaP Bus.

4. Updates DB – The Database is updated

The RunTime Config DB is database is updated with the information that is needed.

4. Post Conditions

4a. Post Condition (Updated DB)

The post-conditions for the onboarding flow are the following. Once, onboarded, the xNF is ready for service creation.

...

DB:

• Database is Updated - The RunTime Config DB has been successfully updated.
• Acknowledgement - A "ACK" (Acknowledgement) success or failure is returned to the requester. When a request from policy is updated, the DMaAP is posted that request is successfully completed which includes confirmation of NetConf parameters and runTime database updates. If this eventually becomes a database API, it will just be a simple success or failure message.

...

REFERENCES

Wiki Page for RunTime Db 5G CONFIGURATION (RunTime DB)

...