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.
There are other 5 categories of high level requirement,
- 1) Will be implmented in R6 by code commitment to different impacted projects/components.
- 2) Will document only for the Frankfurt 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 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.
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.
Category 1) will be implemented in R6
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 DM | Enhanced Nested and Shared Service Information Model REQ-60 - Getting issue details... STATUS | SDC,SO, OOF,AAI | Network Slicing | guochuyi | guochuyi | |||||
| Resource IM/DM | RunTime DB U/C: VES Model relations, VES CM model (CM Notify). REQ-133 - Getting issue details... STATUS | AAI, Controller (RunTime DB component), DCAE | RunTime DB (5G Use Case) | |||||||
Resource IM/DM | SDC, VID, SO, Controllers, CDS | PNF S/W Upgrade (PNF Support Use Case) | wangyaoguang (Huawei) | |||||||
| Service IM, Resource DM | End to End Layer 1 Service Management. Modeling the Optical Service. | Multi-domain Optical Service L0/L1 Orchestration | ||||||||
| Resource IM/DM | Data type & Node type for 5G NRM. | SDC, SO, CDS REQ-49 - Getting issue details... STATUS | 5G NRM Configuration | wangyaoguang | wangyaoguang | wangyaoguang |
Category 2) Will document only for 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 | Enhanced Nested and Shared Service Information Model REQ-60 - Getting issue details... STATUS | SDC,SO, OOF,AAI | Network Slicing | guochuyi | guochuyi | |||||
| Service IM | End-to-end Network Slicing Information Model REQ-60 - Getting issue details... STATUS | SDC,SO, SDN-C, OOF,DCAE, External API, | Network Slicing | guochuyi | guochuyi | |||||
| Resource IM/DM | GeoLocation Model (and standards harmonization) | Modeling | PNF Plug and Play (PNF Support Use Case) | |||||||
| Common | Licensing Model Refinement | SDC | Licensing Management | |||||||
| Service IM | SDC, DCAE | Vertical Industry Oriented on-demand 5G Slice Service | guochuyi | |||||||
| Service IM | SON 'service' | SDC,DCAE,SO | 5G OOF SON use case | |||||||
| Service IM | ORAN & 3GPP Standards Harmonization | SDC, Controller, DCAE, CDS | ORAN & 3GPP Standards Harmonization (5G Use Case) | documentation only |
Category 3) Documentation 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 | VES | Add network element status report to assist run time service instance selection. | DCAE, AAI | Network Slicing | |||||
| Resource | A&AI reverse engineering REQ-170 - Getting issue details... STATUS | 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
Category 4) Lower Priority:
Modeling Domain | Modeling Requirement | Modeling Requirement Description | Impacted Projects | Use Case Relevance | Modeling Spec Commitment | Code Commitment | Provider Priority | Owner |
|---|---|---|---|---|---|---|---|---|
| Service IM | Service Model | Modeling (exploratory) work for creating a 5G Service | Modeling | 5G Service Model Use Case (5G) | ||||
| Service IM | To keep current composite service model align with SDC model, need a comparision and supplement. | SDC | ||||||
| Service IM, Resource IM | Network Topology Modeling. Network configuration tree structures. | SO, SDC, AAI, Controllers, ConfigDB | Network Topology Management | Lower priority move to | ||||
Category 5) 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.