According to ONAP Frankfurt Release requirement input Frankfurt Release Requirements
Gather requirement: July 1-31
...
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 | IMDM | Service DM | Enhanced Nested and Shared Service Information Model | Enhanced Nested and Shared Service Information Model | SDC,SO, OOF,AAI | Network Slicing | guochuyi | guochuyi | Service IM | Slicing Information Model | SDC, SO,External API, SDN-C | Network Slicing | guochuyi | guochuyi |
| SDC,SO, OOF,AAI | Network Slicing | guochuyi | guochuyi | ||||||||||||||||||
| Resource IM/DM | RunTime DB U/C: VES Model relations, VES CM model ( | SDC?, SO, AAI, Controller | ConfigDB CM Notify).
| AAI, Controller (RunTime DB component), DCAE | RunTime DB (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 | Software Versions support for PNF S/W Upgrade
| SDC | PNF S/W Upgrade (PNF Support Use Case) | Zu Qiangwangyaoguang (Huawei) | |||||||||||||||||||||||||||||||||
| Service IM | ORAN & 3GPP Standards Harmonization | SDC, | Controller, DCAE, CDSORAN & 3GPP Standards Harmonization (5G Use Case) | Service IM, | Resource DM | End to End Layer 1 Service Management. Modeling the Optical Service. | SDC, SO, AAI, Controller, DCAE, PolicyAAI
| Multi-domain Optical Service L0/L1 Orchestration | Fujitsu who?Fujitsu | who? | |||||||||||||||||||||||||||
| Resource IM/DM | Data type & Node type for 5G NRM. | SDC, SO, CDS
| wangyaoguang | 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.
| 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
| SDC,SO, OOF,AAI | Network Slicing | guochuyi | documentation only | guochuyi | |||||||||||||||||
| Service IM | End-to- end Network Slicing Information Model
| SDC,SO, SDN-C, OOF,DCAE, External API, | Network Slicing | guochuyi | documentation only | guochuyi | Service IM | To keep current composite service model align with SDC model, need a comparision and supplement. | SDC | Kevin Scaggs | Kevin Scaggs | ||||||||||||
| Resource IM/DM | GeoLocation Model (and standards harmonization) | AAI, PRH, DCAEModeling | PNF Plug and Play (PNF Support Use Case) | documentation only | |||||||||||||||||||
| 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 | documentation only | |||||||||||||||||||
| Service IM | slice service monitoring KPI
| SDC, DCAE | Vertical Industry Oriented on-demand 5G Slice Service | guochuyi |
...
| documentation only | ||||||||||
| Service IM | SON 'service' | SDC,DCAE,SO | 5G OOF SON use case | documentation only | ||||||
| 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. | Related to: DCAE, AAI | Network Slicing | documentation only | ||||||||||||||
| Resource | A&AI reverse engineering
| create runtime information model based on current A&AI schema | Related to: A&AI | PNF Plug&Play | documentation only | ||||||||||||||
Common | policy model | create policy information model based on implementation of policy project | Related to: Policy, SDC | documentation only | |||||||||||||||
| Common | license model | create license information model based on SDC implementation | Related to: SDC | documentation only | |||||||||||||||
| Resource | allotted resource | create allotted resource information model based on SDC implementation | Related to: SDC | documentation only |
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) | documentation only | |||
| 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 | |||||
Category 5) Experimental:
Modeling Domain | Modeling Requirement | Modeling Requirement Description | Impacted Projects | Use Case Relevance | Modeling Spec Commitment | Code Commitment | Provider Priority | Owner |
|---|---|---|---|---|---|---|---|---|
...