USE CASE
| 5G Service Modeling | REQ-320 - Getting issue details... STATUS | |
| Modeling STORY Jira | MODELING-369 - Getting issue details... STATUS | |
| Architecture Sub-committee Jira tracker | ONAPARC-575 - Getting issue details... STATUS | |
| Base 5G Svc Modeling | 5G Use Cases in R6 Frankfurt |
BUSINESS DRIVER
This section describes Business Drivers needs.
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).
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.
BUSINESS MARKETS - This project applies to any domain (wireless, transport, optical, and wireline) that ONAP may manage.
FUNDING/FINANCIAL IMPACTS - Without the groundwork laid down for information model management of a 5G Service, operators will not be able to "turn on" a real live 5G network using "live" PNF resources. No Network. No Business. High OPEX impact.
ORGANIZATION MGMT, SALES STRATEGIES - There is no additional organizational management or sales strategies for this use case outside of a service providers "normal" ONAP deployment and its attendant organizational resources from a service provider.
DEVELOPMENT STATUS
| PROJECT | PTL | User Story / Epic | Requirement |
| A&AI | NO IMPACT | ||
| AAF | NO IMPACT | ||
| APPC | NO IMPACT | ||
| CLAMP | NO IMPACT | ||
| CC-SDK | NO IMPACT | ||
| DCAE | NO IMPACT | ||
| DMaaP | NO IMPACT | ||
| External API | NO IMPACT | ||
| MODELING | EPIC #1 Modeling work to adapt 3GPP TS28.541 NRM | ||
Multi-VIM / Cloud | NO IMPACT | ||
| OOF | NO IMPACT | ||
| POLICY | NO IMPACT | ||
| PORTAL | NO IMPACT | ||
| SDN-C | NO IMPACT | ||
| SDC | NO IMPACT | ||
| SO | NO IMPACT | ||
| VID | NO IMPACT | ||
| VNFRQTS | NO IMPACT | ||
| VNF-SDK | NO IMPACT | ||
| CDS | NO IMPACT |
List of PTLs:Approved Projects
*Each Requirement should be tracked by its own User Story in JIRA
USE CASE DIAGRAM
Use cases define how different users interact with a system under design. Each use case represents an action that may be performed by a user (defined in UML as an Actor with a user persona).
USE CASE FUNCTIONAL DEFINITIONS
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 |
GENERIC INFORMATION MODEL FOR 5G SERVICE
This information is taken from this template: Generic Information Element Template
should be copied in the Parent Page (CNF Modeling Workspace) for each Information Element to be defined.
Information Element Template (one table for each Information Element)
Information Element Name | Name of the Information Element | ||||||||||||||||||||
| Points of Contact | Information Element Main Contact: Benjamin Cheung Information Modeling Contact: Benjamin Cheung 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 Components | The list of ONAP Components that are stakeholders for the Information Element | ||||||||||||||||||||
| Related JIRA | The related Modeling JIRA is here: MODELING-369 - Getting issue details... STATUS | ||||||||||||||||||||
Description | Overview and description of the Information Element. | ||||||||||||||||||||
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) | ||||||||||||||||||||
| Consumers | 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? | ||||||||||||||||||||
| Impacted APIs & Schemas | 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) |
SUPPORTING FILES
| Topic | File |
|---|---|
| 5G Service Modeling | |
| 3GPP TS28.541 5G NRM | |
3GPP TS28.541 5G NRM Parameter Analysis | |
MEETINGS
| Meetings | Attendees | Recording | Audio Only |
|---|---|---|---|
| |||
| Benjamin Cheung | ||
| Benjamin Cheung | ||
| Benjamin Cheung | ||
TESTING
Current Status
Testing Blockers
- High visibility bugs
- Other issues for testing that should be seen at a summary level
- Where possible, always include JIRA links
END TO END FLOW TO BE TESTED
TEST CASES AND STATUS
| 1 | There should be a test case for each item in the sequence diagram | NOT YET TESTED |
| 2 | create additional requirements as needed for each discreet step | COMPLETE |
| 3 | Test cases should cover entire Use Case | PARTIALLY COMPLETE |
| 4 | Test Cases should include enough detail for testing team to implement the test | FAILED |