...
For more information and details you can visit the RunTime DB Use Case Wiki at: 5G CONFIGURATION (RunTime DB) CONFIGURATION PERSISTENCE SERVICE R6
OVERVIEW RUNTIME CONFIG DB
...
PlantUML Macro | ||
---|---|---|
| ||
@startuml
participant Controller
participant DMaaP
participant RunTimeDB
participant xNF
autonumber
group RUNTIMEDB UPDATE
hnote over Controller : Config Update Notification
Controller -> Controller : xNF Config Update Needed
end
group Run Time DB Writing
hnote over Controller : DMaaP Notification
Controller -> DMaaP : Update Notification
DMaaP -> RunTimeDB : Subscription
hnote over RunTimeDB : Updates xNF Update
RunTimeDB -> RunTimeDB : Updates xNF Information
hnote over Controller: Send to xNF
Controller -> xNF : Sends config update to xNF
hnote over xNF: Updates Configuration
end
@enduml |
3.3 Flow 4 Description: Controller writes to RunTime Config DB Information Flow
...
The RunTime Config DB is database is updated with the updated configuration parameter that is needed.
4. Post Conditions
4a. Post Condition (Updated DB)
The post-conditions for the DB:
5. Controller sends to xNF – The Controller sends to xNF
The controller of the xNF updates the xNF with the configuration information. The xNF updates its internal storage.
3.1 FLOW 5: Reading from RunTime Config DB Info Flow
The following UML diagram shows reading information from the RunTime Config DB.
PlantUML Macro | ||
---|---|---|
| ||
@startuml
participant RunTimeConfigDB
participant DMaaP
participant ONAPComponent
autonumber
group Run Time DB Reading
hnote over RunTimeConfigDB : Update Occurred
RunTimeConfigDB -> DMaaP : Publishes Notification
DMaaP -> ONAPComponent : Publishes Notification
hnote over ONAPComponent : Subscribes to Notification
ONAPComponent -> ONAPComponent : Updates Information
end
@enduml |
3.3 Flow 5 Description: Controller reads from RunTime Config DB Information Flow
1. RunTime Config DB has Update Needed – The Controller determines an update is necessary.
The RunTime Config DB determines a configuration (parameter) update is needed and action needs to be taken.
2. RunTime Config DB publishes on DMaaP – Publish onto DMaaP
The RunTime Config DB publishes an event on to the DMaaP Bus.
3. Subscription to DMaaP – The interested ONAP component Subscribes to updates from RunTime Config DB from DMaaP
The ONAP Component Receives the update event RunTime Config DB from the DMaaP Bus.
4. ONAP Component updates info – The ONAP Component is updated
The ONAP Component is database is updated with the updated configuration parameter that is needed.
4. Post Conditions
4a. Post Condition (Updated DB)
The post-conditions for the DB:
- Database is Updated - 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) CONFIGURATION PERSISTENCE SERVICE R6
Architecture component Description ARC RunTime DB Component Description - R6 Frankfurt
...