5G NaaS Self-Service Portal/API/Interface - Draft

Owned by LJ Illuzzi
Last updated: Feb 21, 2023
2 min read

Use this template to submit Use Cases for submission to the 5G Super Blueprint Use Case & Requirements Advisory Group. All input marked Mandatory is required for the blueprint use case proposal to be deemed ready for review by the Use Case & Requirements Advisory Group.

 

Use Case Name:

(Mandatory)

5G Network as-a-Service

Use Case Name:

(Mandatory)

5G Network as-a-Service

Use Case Description:

(Mandatory)

A self-service portal on which where users can self-order 5G services, components, and subcomponents. The portal fulfills Day 0, Day 1, Day 2.

Who values from the development?- Data Center automation vendors, professional services providers (ex. IBM, Aarna, Equinix)

Who benefits from the end product?- Large enterprise, goverment, MNOs

Problem Statement and how is the problem solved:

(Mandatory)

What are the current tools MNOs are using for provisioning? How is 5G plugged into those tools?

Blueprint Owner

(Mandatory)

enter name

Users Stories

(at least one (1) User Story is Mandatory)

  • Customer needs 5G services for a new XXX service. Customer visits Mobile Network Operator (MNO) order fulfillment self- service portal to order, configure, and deploy new services. (Day 0, Day 1, Day 2 fulfillment)

Requirements

(at least one high level system requirement)

  • Ability to provide the following services/components:

    • RAN/Transport(backhaul)/IP Core

    • Cloud/virtualization

    • Slicing

    • edge compute facitlities

    • intelligent data sharing

    • fronthaul/backhaul

    • Automation

    • How are services consumed? (catalog, Self-service, API)

    • Usage-based metric for a billing model

    • Telemetry and observability

    • varying SLAs

Interaction with other open source projects and components

(Mandatory)

Resources -people

(Mandatory)

Resources (people) to execute on the blueprint:

  • enter name 1

  • enter name 2

  • ...

 

High-level architecture diagram

(Mandatory)

 

High level lab topology diagram

(Mandatory)

 

Dependencies - list of any dependencies that rely of future releases of a specfic component.

(Mandatory)

Yes

  •  

    • Enter details:

or

No

High-level timeline

(Mandatory)

  • Month that build can begin: enter month/year

  • Approximate duration of build: enter number of weeks or months

  • Approximate completion of outputs: enter month/year

Upstreaming Opportunities

(Mandatory)

  • enter project(s) and details

Blueprint Outputs 

(Mandatory)

check all that apply:

Code repository
Configuration files (e.g. Helm charts, etc.)
Upstreaming to relevant projects 
Continuous Integration
Test requirements and test results (if applicable)
Documentation:
Overview and Theory of Operation (i.e., what does it do?)
Deployment and setup
Videos
demo
lab setup/behind the scenes
other

High-level timeline

(Mandatory)

  • Month that build can begin: enter month/year

  • Approximate duration of build: enter number of weeks or months

  • Approximate completion of all outputs: enter month/year

Links to existing documentation (Build Guide, Slideware, etc), if available (optional).

 

Links to existing demo/video, if available (optional).

 

Links to existing code/repos, if available (optional).