Release 4 (Dublin) Use Cases and functional requirements
USE CASE
BBS Broadband Service Use Case (Dublin)
OpenSource Access Manager (OSAM) Use Case
Distributed Analytics as a Service (Dublin Summary) - Edge Automation
DEFERRED USE CASES
SD-WAN over 5G Use Case (El Alto) [MOVE TO EL ALTO]
REQUIREMENTS & FEATURES
A Feature is applicable across many use cases. "Requirements" on this wiki page is synonymous with "Feature"
K8S based Cloud Region Support
Fine Grain Placement Service (F-GPS) Edge Automation (Dublin) (F-GPS)
Consistent ID of a Cloud Region (Dublin)
Change Management Dublin Extensions
SUPPORTING DOCUMENTS
Document | File |
|---|---|
M3 API Impacts Template (from Alla G.) |  |
|
|
SERVICE PROVIDER PRIORITIES
CHILD PAGES (Reference)
- 5G Use Case (R4 Dublin)
- BBS Broadband Service Use Case (Dublin)
- CCVPN Use Case (Dublin)
- Change Management Dublin Extensions
- Consistent ID of a Cloud Region (Dublin)
- Continuation of HPA (Dublin)
- Control Loop Requirements
- Fine Grain Placement Service (F-GPS) Edge Automation (Dublin)
- OpenSource Access Manager (OSAM) Use Case
- Scaling Use Case (Dublin)
- SP priorities for Dublin
- K8S based Cloud Region Support
- SD-WAN over 5G Use Case (El Alto)
- Distributed Analytics as a Service (Dublin Summary) - Edge Automation
- SO Plug-in Support Requirements and Use Cases (ETSI SOL003 and SOL001/SOL004)
__________________________________________________________________________
SUPPORTING DOCUMENTS for Release 4 Use Cases
Comments
Dec 17, 2018
A suggestion on how to make ONAP use cases "generic" is to ask these two questions:
On the Northbound, how can the use case be effectively managed (created, configured, monitored, deleted) by an external BSS system via the External API without having to know anything about the internal components of ONAP?
On the Southbound, how can the use case work with Multiple Vendors network functions (and cloud infrastructures) without any modification to ONAP components?