...
EXECUTIVE SUMMARY - This requirement introduces platform information model enhancements to document new ISOMII experimental classes from 3GPP TS28.541, the 5G Network Resource Model (NRM). 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.
BUSINESS IMPACT - The requirement, is a critical because it will serve to lay the ground-work for actually "turning on" a real 5G DU (PNF) that might be installed by a Vendor.
...
Use Case Title | 5G Service Modling |
Actors (and System Components) | N/A, Modeling work |
Description | 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. |
Points of Contact | |
Preconditions | N/A - this use case is modeling work only |
Triggers / Begins when | N/A - this use case is modeling work only |
Steps / Flows (success) | N/A - this use case is modeling work only |
Post-conditions | N/A - this use case is modeling work only |
Alternate / Exception Paths | N/A - this use case is modeling work only |
Related Use Cases | End-to-End Network Slicing Use Case: E2E Network Slicing Use Case in R7 Guilin OOF/SON/PCI Use Case: |
Assumptions | N/A - this use case is modeling work only |
Tools / References / Artifacts | N/A - this use case is modeling work only |
3GPP MODELS
GENERIC INFORMATION MODEL FOR 5G SERVICE
...
Information Element Name | Name of the Information Element (to be determined) (Discuss with Modeling Team) | ||||||||||||||||||||
Points of Contact | Information Element Main Contact: Benjamin Cheung Information Modeling Contact: Benjamin Cheung Chuyi Guo Swaminathan Seetharaman Schema Definition Contact: Benjamin Cheung | ||||||||||||||||||||
Related Use Cases | 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 ComponentsThe list of ONAP Components that are stakeholders for the Information Element | OOF SON PCI Handler Micro-Service, End to End Network Slicing (Micro services) (With the Generic Application Model) in CDS | ||||||||||||||||||||
Related JIRA | The related Modeling JIRA is here:
| ||||||||||||||||||||
Description | Overview and description of the Information ElementThe 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 | 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? | There are hundreds of parameters in the 5G NRM from the above standards. A spreadsheet of all of the parameters are compiled in this spreadsheet:
| |||||||||||||||||||
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 | 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) The PNF or VNF will generate (and own) the information. This information is created outside of ONAP. The information is used by the micro-services. For example the OOF SON PCI Micro-service will use the repository of 5G Data from the C&PS Database. | ||||||||||||||||||||
Consumers | Who uses this information inside & outside of ONAP? How do they use it? RUN TIME - (OOF SON PCI Use Case) - The PCI Micro-service will need the PCI values in the 5G NRM. RUN TIME - (E2E Network Slicing Use Case) - Slicing models, objects and parameters from 5G NRM (TS28.541) Includes description of information consumed (whole class, specific attributes, etc ) The following table shows the E2E NS parameters & classes needed: | ||||||||||||||||||||
Producers | Who updates this information inside & outside 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? Includes 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 produced (whole classclasses, specific attributes, etc.)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 in ONAP? ? 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 | ||||||||||||||||||||
Impacted APIs & Schemas | 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 Identify impacted ONAP schemas & APIs Are there existing schemas be used or extended? API updated | ||||||||||||||||||||
Information Modeling StatusWhat | This is scheduled in the R7 Modeling planning page. The Wiki page: ONAP R7 Modeling High Level Requirements It is being tracked by the Modeling-369 Jira which can be found here:
Status: It is active for the current release, this use case has been accepted. The model is being developed. | ||||||||||||||||||||
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) |
PRESENTATIONS & RECORDINGS
The following are presentations made for the 5G Service Model
Presentation & Date | Recording | Forum |
---|---|---|
R8 Presentation | Honolulu release - functional requirements proposed list | |
R8 Presentation | Honolulu release - functional requirements proposed list | |
Slides for R8 | Honolulu release - functional requirements proposed list | |
SUPPORTING FILES
Topic | File | |||||||
---|---|---|---|---|---|---|---|---|
5G Service Modeling (April 2020) | ||||||||
5G Service Modeling Slides Updated view-file | name | R7-5GServiceCreation_2020Jy20v2.pptxheight | 250 | PDF Version:
name | R7-5GServiceCreation_2020Jy20v2.pdfheight | 250 | | |
3GPP TS28.541 5G NRM | ||||||||
5G Service Modeling Slides Updated | ||||||||
3GPP TS28.541 5G NRM Parameter Analysis View file | | |||||||
5G Service Modeling Slides updated from call and C&PS call | ||||||||
slides from Sept 14 | ||||||||
MEETINGS
Meetings | Attendees | Recording | Audio Only |
---|---|---|---|
| |||
| Modeling Sub-Committee call & discussion in Wiki: | (recording at Wiki) | (recording at Wiki) |
| |||
| |||
AGENDA:
| |||
| Benjamin Cheung | ||
...