ONAP R6 Modeling High Level Requirements
- Hui Deng
- Zu Qiang
- Andy Mayer
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 | SDC,SO, OOF,AAI
| Network Slicing | @guochuyi | @Borislav Glozman @Shankaranarayanan Puzhavakath Narayanan @Swaminathan Seetharaman | @guochuyi | @Borislav Glozman @Shankaranarayanan Puzhavakath Narayanan @Swaminathan Seetharaman | |||
Resource IM/DM | RunTime DB U/C: VES Model relations, VES CM model (CM Notify). | AAI, Controller (RunTime DB component), DCAE | RunTime DB (5G Use Case) | @Kevin Scaggs | @N.K. Shankaranarayanan @Sandeep Shah | @Joanne Liu Rudel @Benjamin Cheung | ||||
Resource IM/DM | Software Versions support for PNF S/W Upgrade REQ-88: Enable PNF software version at onboardingDone | SDC | PNF S/W Upgrade (PNF Support Use Case) | @Fei Zhang (Ericsson) | @Zu Qiang | @Zu Qiang | ||||
Service IM, Resource DM | End to End Layer 1 Service Management. Modeling the Optical Service. | Multi-domain Optical Service L0/L1 Orchestration | @Xin Miao (Unlicensed) | @Xin Miao (Unlicensed) | @Raghavan Subramanian | |||||
Resource IM/DM | Data type & Node type for 5G NRM. | SDC, SO, CDS REQ-49: 5G NRM Configuration Management with RESTFul protocolDone | 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 | @Borislav Glozman @Shankaranarayanan Puzhavakath Narayanan @Swaminathan Seetharaman | |||
Service IM | End-to-end Network Slicing Information Model | SDC,SO, SDN-C, OOF,DCAE, External API, | Network Slicing | @guochuyi | documentation only | @guochuyi | @Swaminathan Seetharaman @Shankaranarayanan Puzhavakath Narayanan @Borislav Glozman | |||
Resource IM/DM | GeoLocation Model (and standards harmonization) | Modeling | PNF Plug and Play (PNF Support Use Case) | @Kevin Scaggs @Jacqueline Beaulac [Ericsson] | documentation only | @Jacqueline Beaulac [Ericsson] @Benjamin Cheung | ||||
Common | Licensing Model Refinement | SDC | Licensing Management | @Kevin Scaggs @Jacqueline Beaulac [Ericsson] | documentation only | @Samuli Kuusela @Timo Perala | ||||
Service IM | slice service monitoring KPI REQ-146: Vertical Industry Oriented On-demand 5G Slice ServiceDone | SDC, DCAE | Vertical Industry Oriented on-demand 5G Slice Service | @guochuyi | documentation only | @LIN MENG | ||||
Service IM | SON 'service' | SDC,DCAE,SO | 5G OOF SON use case | @Swaminathan Seetharaman @Former user (Deleted) | documentation only | @N.K. Shankaranarayanan @Swaminathan Seetharaman | ||||
Service IM | ORAN & 3GPP Standards Harmonization | SDC, Controller, DCAE, CDS | ORAN & 3GPP Standards Harmonization (5G Use Case) | @Kevin Scaggs | documentation only | @Vimal Begwani @marge.hillis |
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 | @Kevin Scaggs @guochuyi | documentation only | |||
Resource | A&AI reverse engineering REQ-170: Reverse Engineering of the AAI data model into Papyrus UMLDone | create runtime information model based on current A&AI schema | Related to: A&AI | PNF Plug&Play | @Jacqueline Beaulac [Ericsson] @Xu Yang | documentation only | |||
Common | policy model | create policy information model based on implementation of policy project | Related to: Policy, SDC | @Kevin Scaggs | documentation only | ||||
Common | license model | create license information model based on SDC implementation | Related to: SDC | @Kevin Scaggs | documentation only | ||||
Resource | allotted resource | create allotted resource information model based on SDC implementation | Related to: SDC | @Kevin Scaggs | 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) | @Benjamin Cheung | documentation only | @Benjamin Cheung @Kevin Scaggs | |
Service IM | To keep current composite service model align with SDC model, need a comparision and supplement. | SDC | @Kevin Scaggs | |||||
Service IM, Resource IM | Network Topology Modeling. Network configuration tree structures. | SO, SDC, AAI, Controllers, ConfigDB | Network Topology Management | @Joanne Liu Rudel | ||||
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.