Page History

...

@startuml
participant PNF
participant VESCollector
participant DMaaP
participant RunTimeDB 
autonumber 

group RUNTIMEDB UPDATE
	hnote over PNF : CM Notification
	PNF -> VESCollector : CM Notification 	
end

group Run Time DB Writing
	hnote over VESCollector : VES Event
	VESCollector -> DMaaP : VES Event 
    DMaaP -> RunTimeDB : Subscription
	hnote over RunTimeDB : Writes Information
	RunTimeDB -> RunTimeDB : Write Information 
end

@enduml

3.3 Flow Description: mS Information Flow

1. VES Event – VES Event Received

A VES event (CM Notify) is received from PNF

2. VES Collector – VES Collector gets the CM Notify

VES Collector gets the CM Notify

3. Publish on DMaaP – VES Collector publishes on DMaAP

VES Collector Publishes on DMaaP

4. Subscription on DMaaP – DMaaP gets the Notification

RunTime DB gets the Event and updates the information

3.1 xNF Update Flow

The following UML diagram shows the xNF Update flow from updates in A&AI for RunTimeDB

...

The describes the xNF information updates and keys based on xNF update.

3.3 Flow Description: AAI Update Information Flow

1. AAI Determines update – A xNF has been removed or added

AAI determines a xNF has been removed/added

3. AAI publishes on DMaaP – AAI publishes on DMaAP

AAI publishes on DMaaP

4. Subscription on DMaaP – DMaaP gets the Notification

RunTime DB gets the AAI updates the information

3.1 mS UPDATE Flow

The following UML diagram shows Where another ONAP component or Micro-Service updates the RunTimeDB

...

The describes the xNF information updates and keys based on xNF update.

3.2 mS Information Flow

3.3 Flow Description: mS Information Flow

1. Micro Service Determines Update Needed – fPackage.

...