Title of the Use Case5G Service Modling

The list of Actors and System Components that participate in the Use Case

Short overview of the Use Case

Authors and maintainers of the Use Case.

Use Case Lead, Key Use Case members and code contributors.

A list of conditions that are assumed to be true before the Use Case is invoked

Includes description of Information Consumed

Describes the trigger for beginning the Use Case

Describes the sequence of steps and interactions that occur during the Use Case (may include: description, data exchanges, functionality, state changes)

Interaction diagrams may be included or referenced

The expected results of the execution of the Use Case

Includes description of Information Produced

Description of any exceptions or special process that could occur during Use Case

List of the Use Cases referenced by this Use Case

Describes any assumptions that are made for this use case

List of any tools or reference material associated with this Use Case as well as any JIRA trace-ability.

List of any associated diagrams or modelling artifacts associated with the Use Case

N/A, Modeling work

This use case will lay the groundwork to introduce and open the discussion with the modeling sub-committee for the platform information modeling work to allow ONAP to integrate with a real "live" 5G DU Base station (PNF)

The RAN (wireless) 5G base station network resource model is driven by the 3GPP standard: TS28.540 and TS28.541, the 5G NRM.

This standard is used by all 5G vendors for their PNFs (DUs) which serves as a starting point to think about modeling work as it is common to all vendors.

ONAP will not necessarily need to know or work with all of the ~300 parameters described in the standard, but rather should introduce a common "core" model into the ONAP platform release information model, so that other future use cases and applications can introduce model information in an orderly fashion.

In R7, the OOF/SON/PCI and End-to-End Network Slicing use cases will leverage the work to introduce this common "core" model. Note that, these use cases ARE domain specific, to network wireless / radio access networks. So some thought should be given as to how to introduce domain-specific modeling into ONAP such that it can still serve many other domains with full functionality given to each of those domains.

N/A - this use case is modeling work only

N/A - this use case is modeling work only

N/A - this use case is modeling work only

N/A - this use case is modeling work only

N/A - this use case is modeling work only

End-to-End Network Slicing Use Case: E2E Network Slicing Use Case in R7 Guilin

OOF/SON/PCI Use Case:

N/A - this use case is modeling work only

Information Element Name

Name of the Information Element (to be determined) (Discuss with Modeling Team)

The E2E Network Slicing Use Case

WIKI: E2E Network Slicing Use Case in R7 Guilin

and OOF SON PCI Use Case are related use cases that all use the 3GPP TS28.541 5G NRM:

WIKI: R7 OOF SON Use Case

Participating ONAP Components

OOF SON PCI Handler Micro-Service, End to End Network Slicing (Micro services)

(With the Generic Application Model) in CDS

Description

The purpose of this use case is to introduce the necessary changes into the ONAP platform architecture so that it can be prepared to accept and work with a real live 5G RAN DU (for a gNB). Presently, this may mean introducing a generic application model defined in CDS. This model would then integrate the 3GPP 5G NRM so that ONAP components and micro-services could access the information in a 3GPP format without needing to overhaul the Platform Information Model.

Related Standards & Industry Activities

Related Industry Standards are here:

Attributes

Relationships

RUN TIME - (SO, CDS, PRH). PNFs that need to be instantiated in 5G Services (associated resources for a service).

RUN TIME - (OOF SON PCI Use Case) - The PCI Micro-service will need the PCI values in the 5G NRM.

Originator

Producers

Who updates this information inside of ONAP? ANSWER: A user would load the Generic Application Model. CDS would update this information inside of ONAP. A user would specify a domain specific model to use.

Under what conditions do they update it? ANSWER: In design time, if the designer determined that a resource will be using the Generic Application Model, they can choose to update it with a domain specific model. The detailed description of information (classes, attributes) can be obtained in the 3GPP TS28.541 standards that can be retrieved from the links above.

Steward

Where will this information stored and maintained? ANSWER: This model information would become a part of the CDS repository. During design time, CDS would be used to load a domain specific model

ANSWER: With the Generic Application Model Solution, CDS Platform component will need to be updated and its APIs may be impacted.

CDS would load the Generic Application Model and populate it with a standard defined model, for example, the 3GPP 5G NRM.

CDS would have an impacted ONAP schemas & API updated

Information Modeling Status

Schema Definition Status

What is the status of ONAP Schema Definition activities associated with this Information Element.

Please provide links to relevant wiki pages & JIRA.

ONAP Release Priority

This use case is in the R7 Release planning. The Wiki Page is at: Guilin Release Requirements

It has a TSC Priority of 0 (Go)

Modeling Sub-Committee call & discussion in Wiki:

ONAP R7 Resource IM Call 2020-7-20