According to ONAP R8 Release requirement input LINK
Reporting on the R8 release to the TSC will begin nnn, so the deadline for the input of high level requirement will be M0: DATE 2020.
Prioritize & Finalize:
before M1: DATE 2020 , the requirement will be finalized.
There are other 5 categories of high level requirement,
- 1) Will be implemented in R8 by code commitment to different impacted projects/components.
- 2) Will document only for the R8 release.
- 3) Documentation after implemented in prior release
- 4) Lower Priority
- 5) Experimental
The first category is that those requirement will be documented only in R8 release
the second category will document the current implementation in those projects.
Other two categories like lower priority and experimental will not be included in the release 3, the contributor will work with best effort to influence future release.
Owners of each requirement needs to coordinate the modeling spec commitment and code commitment with PTLs of impacted project.
Below High Level Requirements have been agreed by modeling subcommitee with code commitment promise to Honolulu release, modeling subcommittee request related to projects to approve those related submission.
Category 1) will be implemented in the R8 release
Modeling Domain | Modeling Requirement | Modeling Requirement Description | Impacted Projects | Use Case Relevance | Modeling Spec Commitment | Code Commitment | Provider Priority | Mapping to M1 requirement | Owner | Use Case Owner |
|---|---|---|---|---|---|---|---|---|---|---|
| A&AI Schema DM | Place Model | Uses the Place Information Model to associate instance of it to PNF in AAI | SO (AssignpnfBB) | R8 PNF Plug and Play Use Case | Benjamin Cheung | damian.nowak | REQ-430 - Getting issue details... STATUS This is the REQ Jira for the R8 PNF Plug and Play Use Case. | Benjamin Cheung | ||
| Resource IM/DM | ETSI VNF Model | Support mapping of ETSI NFV SOL001 v3.3.1 VNF Descriptor + CNF enhancements from IFA011 v4.1.1 into AID DM | SDC, SO | REQ-400 - Getting issue details... STATUS | Fernando Oliveira | Byung-Woo Jun | ONAPMODEL-33 - Getting issue details... STATUS | |||
Service IM/DM | E2E Network Slicing – Enhanced solution of 3 domain network combination |
| OOF, SO, AAI, SDN-C | R8 E2E Network Slicing use case | @LIN MENG | MODELING-457 - Getting issue details... STATUS | guochuyi | @LIN MENG | ||
| Service IM | Configuration Persistence Service (CPS) Model | Modeling work for CPS | Modeling | Configuration Persistence Service (CPS) for R8 Honolulu | Jacqueline Beaulac [Ericsson] | (may have S/W impact / implementation - may move to Category 1) | REQ-427 - Getting issue details... STATUS Overview Slides: ConfigurationPersistenceSvcDDF_202010Oc15v12.pdf Potential Impacts to SDC and affects associated Use cases that use CPS such as E2E Network Slicing and OOF SON use cases.
| Toine Siebelink | ||
| Resource IM/DM | Update Slicing Model for ANFD | modeling work for ANFD related | Modeling | R8 E2E Network Slicing use case | ||||||
Category 2) Will document only for the R8 release
Modeling Domain | Modeling Requirement | Modeling Requirement Description | Impacted Projects | Use Case Relevance | Modeling Spec Commitment | Code Commitment | Provider Priority | Mapping to M1 requirement | Owner | Use Case Contact |
|---|---|---|---|---|---|---|---|---|---|---|
| Service IM | 5G Service Model | Modeling work for creating a 5G Service | Modeling | R8 5G Service Modeling | Benjamin Cheung | Documentation Only | Benjamin Cheung | |||
| Resource IM | 5G Resource Model | Resource Modeling Work to support a live 5G PNF | Modeling | R8 5G Service Modeling | Benjamin Cheung | Documentation Only | REQ-428 - Getting issue details... STATUS Architecture Review completed. Meetings scheduled monthly at 5G - Use Case Realization Calls | Benjamin Cheung | ||
| Resource IM | Model update for StndDefined VES | Update VES7.2 in Papyrus | Modeling | R8 ONAP/3GPP & O-RAN Alignment: Standard Defined VES | Benjamin Cheung | Documentation Only | MODELING-476 - Getting issue details... STATUS | Benjamin Cheung | Marge Hillis | |
| Resource IM | Abstract Topology Modeling | Begin development of an Abstract Topology Model | Modeling | ONAP / O-RAN Alignment | Documentation Only | ONAPMODEL-35 - Getting issue details... STATUS | Martin Skorupski | |||
Category 3) Documentation Only after implemented in prior release
Modeling Domain | Modeling Requirement | Modeling Requirement Description | Impacted Projects | Use Case Relevance | Modeling Spec Commitment | Code Commitment | Provider Priority | Mapping to M1 requirement | Owner |
|---|---|---|---|---|---|---|---|---|---|
| Common | Policy model | Update policy model based on implementation of policy project | Documentation Only | MODELING-439 - Getting issue details... STATUS | guochuyi |
Below tables are not downgrade, but Guilin won't make it
Category 4) Lower Priority:
Modeling Domain | Modeling Requirement | Modeling Requirement Description | Impacted Projects | Use Case Relevance | Modeling Spec Commitment | Code Commitment | Provider Priority | JIRA Link | Owner |
|---|---|---|---|---|---|---|---|---|---|
Category 5) Experimental:
Modeling Domain | Modeling Requirement | Modeling Requirement Description | Impacted Projects | Use Case Relevance | Modeling Spec Commitment | Code Commitment | Provider Priority | JIRA Link | Owner |
|---|---|---|---|---|---|---|---|---|---|
Requirements can be based on:
- Release / project specific needs
- Recognized 'future' needs
- Documenting existing models
Some concepts may be complex enough, if we wait for the release / project requirement, we will be too late to properly develop the concept.