ONAP R7 Modeling High Level Requirements

According to ONAP Guilin Release requirement input Guilin Release Requirements

Reporting on the Guilin release to the TSC will begin nnn, so the deadline for the input of high level reuiqrement will be M0: Apr. 23rd. 2020.

Prioritize & Finalize: 

before M1: May th 2020 , the requirement will be finalized.



There are other 5 categories of high level requirement,

  • 1) Will be implemented in R7 by code commitment to different impacted projects/components. 

  • 2) Will document only for the Guilin 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 Guilin 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 the Guilin release

Modeling Domain

Modeling Requirement

Modeling Requirement Description

Impacted

Projects

Use Case

Relevance

Modeling Spec

Commitment

Code

Commitment

End of Release Status

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

End of Release Status

Mapping to M1 requirement

Owner

Use Case Owner

Resource IM/DM

ETSI VNF Model

Support mapping of ETSI NFV SOL001 v2.7.1 VNF Descriptor into AID DM

SDC



@Fernando Oliveira  @Byung-Woo Jun

@Byung-Woo Jun

2.7.1 IM changes were accepted and merged. Initial proposal for mapping to SDC AID DM in review. Continue to R8 with possible move to v3.3.1 of ETSI SOL001.

REQ-334: ETSI-Alignment for GuilinDone

@Fernando Oliveira  @Byung-Woo Jun

@Fernando Oliveira @Byung-Woo Jun

Service IM/DM

ETSI Network Service

Support mapping of ETSI NFV SOL001 v2.7.1 Network Service Descriptor into AID DM

SDC



@Fernando Oliveira @Byung-Woo Jun

@Byung-Woo Jun

2.7.1 IM changes were accepted and merged. Initial proposal for mapping to SDC AID DM in review. Initial support for NS and Virtual Link mapping were introduced in R7. Continue to R8 with possible move to v3.3.1 of ETSI SOL001.

REQ-334: ETSI-Alignment for GuilinDone

@Fernando Oliveira @Byung-Woo Jun

@Fernando Oliveira @Byung-Woo Jun

VES IM

VES DM Spec

StndDefined VES Notification Model Update

ONAP/3GPP & O-RAN Alignment: Standards Defined Notifications over VEShttps://lf-onap.atlassian.net/browse/MODELING-370

DCAE

VNF-REQT

ONAP/3GPP & O-RAN Alignment-Standards Defined Notifications over VES

@Vimal Begwani

@marge.hillis

@damian.nowak





Update this model: VES 7.1

REQ-327: ONAP/3GPP & O-RAN Alignment-Standards Defined Notifications over VES (Guilin)Done





Service

IM/DM



E2E Network Slicing Model Enhancement

Extend E2E Slicing design to support RAN,  Transport and Core slice subnet

OOF, SO, AAI, SDN-C

E2E Network Slicing Use Case in R7 Guilin

@Borislav Glozman

@guochuyi

@Fei Zhang (Ericsson)



@Swaminathan Seetharaman

@LIN MENG

Done

Modeling work for R7 has finished, Jira has been closed. 

REQ-342: E2E Network Slicing requirements for Guilin releaseDone

MODELING-367: E2E Network Slicing: Network SlicingClosed



@guochuyi

@LIN MENG

@Swaminathan Seetharaman



Service

IM/DM

Transport Slice Definition Model

Define the TN NSSI data model in AAI

OOF, SO, AAI, SDN-C

CCVPN - Transport Slicing

@Henry Yu

@guochuyi

@Henry Yu

@LIN MENG

Done

Related changes for AAI have been delivered.

REQ-347: CCVPN-Transport Slicing for Guilin ReleaseDone

AAI-2920: CCVPN - Transport Slicing: AAI schema for TN NSSIClosed

@Henry Yu

@LIN MENG

@Henry Yu

Service IM

Service Monitoring and Reporting

Define information model for External API Service Monitoring and Reporting based on TM Forum 628

Modeling

ExtAPI

E2E Network Slicing

@Adrian OSullivan



@Priyadharshini B

@Swaminathan Seetharaman

Move to R8

EXTAPI-450: EXT-API impacts for support of TMF 628 APIs for KPI monitoringClosed

EXTAPI-453: E2E Network Slicing: KPI monitoring Information ModelingClosed

@Adrian OSullivan

@Priyadharshini B

@Swaminathan Seetharaman



Category 2) Will document only for the Guilin release



Modeling Domain

Modeling Requirement

Modeling Requirement Description

Impacted

Projects

Use Case

Relevance

Modeling Spec

Commitment

Code

Commitment

End of Release Status

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

End of Release Status

Mapping to M1 requirement