Skip to end of metadata
Go to start of metadata

USE CASE

5G Use Case (R4 Dublin)

BBS Broadband Service Use Case (Dublin)

CCVPN 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"

Control Loop Requirements

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

Continuation of HPA (Dublin)

Scaling Use Case (Dublin)


SUPPORTING DOCUMENTS

DocumentFile

M3 API Impacts

Template (from Alla G.)




SERVICE PROVIDER PRIORITIES

SP priorities for Dublin

CHILD PAGES (Reference)

__________________________________________________________________________

SUPPORTING DOCUMENTS for Release 4 Use Cases

  File Modified
PNG File image2019-2-11_10-54-1.png Feb 11, 2019 by Benjamin Cheung
PNG File image2019-2-11_10-56-15.png Feb 11, 2019 by Benjamin Cheung
Microsoft Word Document M3 for use cases and functional requirements.docx Feb 28, 2019 by Benjamin Cheung
Microsoft Excel Spreadsheet ONAP-MeetingsIndex.xlsx Sep 28, 2018 by Benjamin Cheung



  • No labels

1 Comment

  1. A suggestion on how to make ONAP use cases "generic" is to ask these two questions:

    1. 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?

    2. On the Southbound, how can the use case work with Multiple Vendors network functions (and cloud infrastructures) without any modification to ONAP components?