According to ONAP Frankfurt Release requirement input Frankfurt Release Requirements
Gather requirement: July 1-31
Refine requirement: Aug. 1-31
Reporting on the Frankfurt release to the TSC will begin Aug 22, so the deadline for the input of high level reuiqrement will be Aug 22.
Prioritize & Finalize: Sep. 1-23
before M1: Sep. 23rd , the requirement will be finalized.
Below High Level Requirements have been agreed by modeling subcommitee with code commitment promise to Frankfurt release, modeling subcommittee request related to projects to approve those related submission.
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 |
|---|---|---|---|---|---|---|---|---|---|---|
| Service IM | Enhanced Nested and Shared Service Information Model | SDC,SO, OOF,AAI | Network Slicing | Chuyi Guo | Chuyi Guo | |||||
| Service IM | Slicing Information Model | SDC, SO,External API, SDN-C | Network Slicing | Chuyi Guo | Chuyi Guo | |||||
| Service DM | Enhanced Nested and Shared Service Information Model | SDC,SO, OOF,AAI | Network Slicing | Chuyi Guo | Chuyi Guo | |||||
| Resource IM/DM | VES Model relations, VES CM (Config managment), Maria DB Data Model | SDC, SO, AAI, Controller | ConfigDB (5G Use Case) | |||||||
| Service IM, Resource IM | Network Topology Modeling. Network configuration tree structures. | SO, SDC, AAI, Controllers, ConfigDB | Network Topology Management | Joanne Liu Rudel | ||||||
| Resource IM/DM | GeoLocation Model (and standards harmonization) | AAI, PRH, DCAE | PNF Plug and Play (PNF Support Use Case) | |||||||
Resource IM/DM | Software Versions support for PNF S/W Upgrade | SDC, VID, SO, Controllers, CDS | PNF S/W Upgrade (PNF Support Use Case) | |||||||
| Service IM | ORAN & 3GPP Standards Harmonization | SDC, Controller, DCAE, CDS | ORAN & 3GPP Standards Harmonization (5G Use Case) | |||||||
| Common | Licensing Model Refinement ( *) No changes expected in R6 as an outcome of the proposed UC | SDC ( *) No changes expected in R6 as an outcome of the proposed UC | Licensing Management | |||||||
| Service IM, Resource DM | End to End Layer 1 Service Management. Modeling the Optical Service. | SDC, SO, AAI, Controller, DCAE, Policy | Multi-domain Optical Service L0/L1 Orchestration | Raghavan Subramanian | ||||||
| Resource IM/DM | Data type & Node type for 5G NRM. | SDC, SO, CDS | 5G NRM Configuration | yaoguang wang | yaoguang wang | |||||
| Service IM | SON 'service' | SDC,DCAE,SO | 5G OOF SON use case |
There are other 4 categories of high level requirement,
- 1) Will be documented only and included in the Frankfurt release, but no implementation promised.
- 2) Documentation after implemented, or implemented but not in the release
- 3) Lower Priority
- 4) Experimental
The first category is that those requirement will be documented only in Frankfurt 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.
1) Will be documented only and included in the Frankfurt 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 | End-to-End Slicing Management | SDC,SO, SDN-C, OOF,DCAE | Network Slicing | Chuyi Guo | Chuyi Guo | |||||
| Service IM | To keep current composite service model align with SDC model, need a comparision and supplement. | SDC | Kevin Scaggs | Kevin Scaggs | ||||||
2) Documentation after implemented, or implemented but not in the 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 | VES | Add network element status report to assist run time service instance selection. | DCAE, AAI | Network Slicing | |||||
| Resource | A&AI reverse engineering | create runtime information model based on current A&AI schema | A&AI | PNF Plug&Play | |||||
Common | policy model | create policy information model based on implementation of policy project | Policy, SDC | ||||||
| Common | license model | create license information model based on SDC implementation | SDC | ||||||
| Resource | allotted resource | create allotted resource information model based on SDC implementation | SDC |
Below tables are not downgrade, but Frankfurt won't make it
3) Lower Priority:
Modeling Domain | Modeling Requirement | Modeling Requirement Description | Impacted Projects | Use Case Relevance | Modeling Spec Commitment | Code Commitment | Provider Priority | Owner |
|---|---|---|---|---|---|---|---|---|
4) Experimental:
Modeling Domain | Modeling Requirement | Modeling Requirement Description | Impacted Projects | Use Case Relevance | Modeling Spec Commitment | Code Commitment | Provider Priority | Owner |
|---|---|---|---|---|---|---|---|---|
Per discussion in Paris, 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.