5G Service Modling

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

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

(With the Generic Application Model)

Description

Related Standards & Industry Activities

Related Industry Standards are here:

Attributes

Attributes: Name and describe each attribute of this Information Element. Please include the datatype of the attribute if possible. Is this attribute read-only, read-write? Are there any default values?

Relationships

Relationships: Describe how this Information Element is related to other Information Elements. Also describe nature of the relationship: association, inheritance, dependency, etc. and multiplicity.

Originator

Where does this information come from? (What component initially creates it)

Who uses this information inside & outside of ONAP?  How do they use it?

Includes description of information consumed (whole class, specific attributes, etc.)

Producers

Who updates this information inside & outside of ONAP? Under what conditions do they update it?

Includes description of information produced (whole class, specific attributes, etc.)

Steward

Where will this information stored and maintained in ONAP?

Identify impacted ONAP schemas & APIs

Are there existing schemas be used or extended?

Information Modeling Status

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

Please provide links to relevant wiki pages & JIRA.

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