According to ONAP Guilin R8 Release requirement input Guilin Release RequirementsLINK
Reporting on the Guilin R8 release to the TSC will begin nnn, so the deadline for the input of high level reuiqrement will requirement will be M0: Apr. 23rd. DATE 2020.
Prioritize & Finalize:
before M1: May th DATE 2020 , the requirement will be finalized.
...
- 1) Will be implemented in R8 + by code commitment to different impacted projects/components.
- 2) Will document only for the Guilin 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 Guilin in R8 release
the second category will document the current implementation in those projects.
...
Below High Level Requirements have been agreed by modeling subcommitee with code commitment promise to Frankfurt to Honolulu release, modeling subcommittee request related to projects to approve those related submission.
Category 1) will be implemented in the Guilin 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 | ||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Resource IM/A&AI Schema DM | ETSI VNF Place Model | Support mapping of ETSI NFV SOL001 v2.7.1 VNF Descriptor into AID DM | SDC | 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 NowakByung-Woo Jun |
| Service DM |
This is the REQ Jira for the R8 PNF Plug and Play Use Case. | Benjamin Cheung | ||||||||||||||||||||||||||||||||
| Resource IM/DM | ETSI VNF ModelETSI Network Service | Support mapping of ETSI NFV SOL001 v2v3.73.1 Network Service Descriptor VNF Descriptor + CNF enhancements from IFA011 v4.1.1 into AID DM | SDC | , SO | Byung-Woo Jun
| Fernando Oliveira Byung-Woo JunFernando Oliveira | Byung-Woo Jun | VES IM VES DM Spec | StndDefined VES Notification Model Update | ONAP/3GPP & O-RAN Alignment: Standards Defined Notifications over VES |
| DCAE VNF-REQT |
| |||||||||||||||||||||||||||||||
| ONAP/3GPP & O-RAN Alignment-Standards Defined Notifications over VES | Damian Nowak | Update this model: VES 7.1
Service IM/DM | E2E Network Slicing Model Enhancement– Enhanced solution of 3 domain network combination |
| OOF, SO, AAI, SDN-C | Use Case in R7 Guilin |
| @LIN MENG |
| Chuyi Guo | LIN @LIN MENG | |||||||||||||||||||||||||||||||||
| Service IM/DM | Transport Slice Definition Model | Define the TN NSSI data model in AAI | OOF, SO, AAI, SDN-C | CCVPN - Transport Slicing | Configuration Persistence Service (CPS) Model | Modeling work for CPS | Modeling | Configuration Persistence Service (CPS) for R8 Honolulu | Jacqueline Beaulac |
| 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 | 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.
| Toine Siebelink | ||||||||||||||||||||||||||
| Resource IM/DM | Update Slicing Model for ANFD | modeling work for ANFD related | Modeling | R8 E2E Network Slicing use case |
|
| Adrian OSullivan | Related discussion | ||||||||||||||||||||||||||||||||||||
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 | |||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Service IM | 5G Service Model | Modeling work for creating a 5G service| Jira | | ||||||||||||||||||||||||||||||||||||
| server | ONAP JIRA | ||||||||||||||||||||||||||||||||||||||
| serverId | 425b2b0a-557c-3c0c-b515-579789cceedb | key | MODELING-369ServiceModeling | R7 R8 5G Service Modeling | Benjamin Cheung | Documentation Only |
Overview slides: | Benjamin Cheung | |||||||||||||||||||||||||||||||
| Resource IM | 5G Resource Model | Resource Modeling work Work to support a live 5G PNF creation |
| R7 R8 5G Service Modeling | Benjamin Cheung | Documentation Only |
Architecture Review completed. Meetings scheduled monthly at 5G - Use Case Realization Calls | Benjamin Cheung | |||||||||||||||||||||||||||||||
| Resource IM/DM | Geolocation Model | Geolocation Model (and standards harmonization)
| Modeling | PNF Plug and Play (PNF Support Use Case) | update for StndDefined VES | Update VES7.2 in Papyrus | Modeling | R8 ONAP/3GPP & O-RAN Alignment: Standard Defined VES | Benjamin Cheung | Documentation Only |
| Benjamin Cheung | Marge Hillis | ||||||||||||||||||||||||||
| Core/Resource IM | Model Driven Model introduction in relation to C&PS | Introduction of Model Driven Application Data
| Modeling | Configuration & Persistency Service R7 | Abstract Topology Modeling | Begin development of an Abstract Topology Model | Modeling | ONAP / O-RAN Alignment | Documentation OnlyDocumentation only |
|
| Jacqueline Beaulac | 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 | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Common | Policy model | Update policy model based on implementation of policy project | Documentation Only |
| Update policy model based on implementation of policy project | Documentation Only |
| Chuyi Guo |
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 |
|---|---|---|---|---|---|---|---|---|---|
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 | ||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Resource IM / DM | Information and Data Model to support CNF | Add new information elements in the information model for MCIOP, container Descriptor, container image, ... | SDC, A&AI, SO, DCAE | Fernando Oliveira | Resource IM/DM | CNF Inventory Information Model and AAI Schema Definition | Define a logical information model supporting CNF Inventory and develop the supporting AAI Schema Definition | AAI | CNFO | Seshu Kumar Mudiganti | (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 |
| Cheng Huang | |||||||||||||
Requirements Per discussion in Paris, requirements can be based on:
- Release / project specific needs
- Recognized 'future' needs
- Documenting existing models
...