...
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 |
|---|
Provider
Priority
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 | 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. |
| ||||||||||||||||||||||||
| Service IM/DM | ETSI Network Service | Support mapping of ETSI NFV SOL001 v2.7.1 Network Service Descriptor into AID DM | SDC | 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. |
| ||||||||||||||||||||||||
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 | 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 | Done Modeling work for R7 has finished, Jira has been closed. |
| guochuyi | |||||||||||||||||||||||
Service IM/DM | Transport Slice Definition Model | Define the TN NSSI data model in AAI | OOF, SO, AAI, SDN-C | CCVPN - Transport Slicing | Done Related changes for AAI have been delivered. |
| 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 | Move to R8 |
| Adrian OSullivan |
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 |
|---|
Provider
PriorityEnd of Release Status | Mapping to M1 requirement | Owner | Use Case Contact | |||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Service IM | 5G Service Model | Modeling work for creating a 5G service
| Modeling | R7 5G Service Modeling | Benjamin Cheung | Documentation Only | Continue to R8 |
| Benjamin Cheung | |||||||||||||||||
| Resource IM | 5G Resource Model | Resource Modeling work to support a PNF creation
| Modeling | R7 5G Service Modeling | Benjamin Cheung | Documentation Only | Continue to R8 |
| ||||||||||||||||||
| Resource IM/DM | Geolocation Model | Geolocation Model (and standards harmonization)
| Modeling | PNF Plug and Play (PNF Support Use Case) |
| Documentation Only | Completed |
| Benjamin Cheung |
| Core/Resource IM | Model Driven Model introduction in relation to C&PS | Introduction of Model Driven Application Data
| Modeling | Configuration & Persistency Service R7 | Documentation only |
| Jacqueline Beaulac [Ericsson] | |||||||||||||||||||||||||||
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
End of Release Status | Mapping to M1 requirement | Owner | |||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Common | Policy model
| Update policy model based on implementation of policy project | Documentation Only | Move to R8 | 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
PriorityEnd of Release Status | JIRA Link | Owner | |||||||
|---|---|---|---|---|---|---|---|---|---|
Category 5) Experimental:
Modeling Domain | Modeling Requirement | Modeling Requirement Description | Impacted Projects | Use Case Relevance | Modeling Spec Commitment | Code Commitment |
|---|
Provider
PriorityEnd of Release Status | 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 | Initial proposal aligned with ETSI v4.1.1 IFA011 for the changes to the resource IM are available. ETSI IFA011 v3.3.1 & v4.1.1 Changes to ONAP Resource Model. Continue to R8 with a possible PoC | 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 | CNF Modeling Task Force group is awaiting Use Case input to help scope the modeling. Will continue this activity in R8 release. | Seshu Kumar Mudiganti |
Per discussion in Paris, requirements can be based on:
...