ONAP R8 Modeling High Level Requirements

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

Modeling Domain	Modeling Requirement	Modeling Requirement Description	Impacted Projects	Use Case Relevance	Modeling Spec Commitment	Code Commitment	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: PNF Plug & Play in R8Done This is the REQ Jira for the R8 PNF Plug and Play Use Case. R8-PnP_IPv4v6_CMPv2_StndDefVES-202010Oc12.pdf	@Benjamin Cheung	@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	R8 ETSI Alignment REQ-400: ETSI-Alignment Requirements for the Honolulu releaseDone	@Fernando Oliveira	@Byung-Woo Jun	ONAPMODEL-33: Modeling enhancements for ETSI Alignment in Honolulu releaseClosed	@Fernando Oliveira @Byung-Woo Jun	@Fernando Oliveira @Byung-Woo Jun
Service IM/DM	E2E Network Slicing – Enhanced solution of 3 domain network combination	Enhanced EP design TN Modeling to support NSSI reusing, isolation level and etc. Profile updates to support R8 close-loop requirements	OOF, SO, AAI, SDN-C	R8 E2E Network Slicing use case REQ-440: E2E Network Slicing use case requirements for Honolulu releaseDone	@guochuyi @Borislav Glozman @Henry Yu @Fei Zhang (Ericsson)	@Swaminathan Seetharaman @LIN MENG	ONAPMODEL-32: Modeling enhancements for E2E Network Slicing in Honolulu releaseClosed	@guochuyi	@LIN MENG @Swaminathan Seetharaman
Service IM	Configuration Persistence Service (CPS) Model	Modeling work for CPS	Modeling	Configuration Persistence Service (CPS) for R8 Honolulu	@Jacqueline Beaulac [Ericsson]	@Toine Siebelink (may have S/W impact / implementation - may move to Category 1)	REQ-427: Configuration Persistence Service in R8Done 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. UML modeling for interface to represent information elements provided on the CPS APIs ( @Toine Siebelink )	@Toine Siebelink	@Tony Finnerty @Benjamin Cheung @Jacqueline Beaulac [Ericsson]
Resource IM/DM	Update Slicing Model for ANFD	modeling work for ANFD related	Modeling	R8 E2E Network Slicing use case	@Fei Zhang (Ericsson)	@Fei Zhang (Ericsson)	REQ-440: E2E Network Slicing use case requirements for Honolulu releaseDone Related discussion Allotted Resource for Network Slicing	@Fei Zhang (Ericsson)	@Fei Zhang (Ericsson) @Michela Bevilacqua

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

Modeling Domain	Modeling Requirement	Modeling Requirement Description	Impacted Projects	Use Case Relevance	Modeling Spec Commitment	Code Commitment	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	REQ-428: 5G Service Modeling in R8 - Modeling WorkDone Overview slides: R8-5GServiceCreation_2020Sp14v5.pdf	@Benjamin Cheung	@Benjamin Cheung @guochuyi
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: 5G Service Modeling in R8 - Modeling WorkDone Architecture Review completed. Meetings scheduled monthly at 5G - Use Case Realization Calls	@Benjamin Cheung	@Benjamin Cheung @guochuyi
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: Standard Defined VES 7.2 Model Update in PapyrusClosed	@Benjamin Cheung	Marge Hillis
Resource IM	Abstract Topology Modeling	Begin development of an Abstract Topology Model	Modeling	ONAP / O-RAN Alignment	@Martin Skorupski @Andy Mayer	Documentation Only	ONAPMODEL-35: ONAP internal topology modelOpen	@Andy Mayer	@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

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			@guochuyi @Michela Bevilacqua	Documentation Only		MODELING-439: Policy Model Closed	@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

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

Modeling Domain	Modeling Requirement	Modeling Requirement Description	Impacted Projects	Use Case Relevance	Modeling Spec Commitment	Code Commitment	Provider Priority	JIRA Link	Owner
IM / DM		(in R8 Istanbul release) Vertical Industry Use Case will investigate E2E NS & CPS modeling interactions		Vertical Industry Use Case		Proof of Concept in R8	PoC	REQ-468: Support for vertical industry scenariosDone	@Cheng Huang

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.