Based on timeplan of modeling subcommittee, high level requirements need to be finished by M0/M1,
Below High Level Requirements have been agreed by modeling subcommitee with code commitment promise to Dublin release, modeling subcommittee request related to projects to approve those related submission.
...
Modeling Domain
...
Modeling Requirement
...
Modeling Requirement Description
...
Impacted
Projects
...
Use Case
Relevance
...
Modeling Spec
Commitment
...
Code
Commitment
...
Provider
Priority
...
Resource DM
...
ETSI NFV SOL001 v2.5.1
...
VNFD - the ONAP internal data model should be able to reflect ETSI SOL001 VNFDs provided for onboarding
...
SDC, VFC
...
CCVPN, vCPE
...
...
...
...
ETSI NFV SOL001 v2.5.1
PNFD - the ONAP internal data model (AID)should be able to reflect ETSI SOL001 PNFDs provided for onboarding.
(committed goal)
''''''''''''''''
Could an Onboarded PNFD also be internally mapped to the second ONAP internal model (nfv tosca types) ?
Could two internal descriptors coexist in the same internal SDC package ?
(stretch goal)
SDC
...
Ericsson.
Part of 5G UC Onboarding UC in Dublin.
...
There are other 4 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 documented only and included in the Dublin release, but no implementation promised.2implmented in R6 by code commitment to different impacted projects/components.
- 2) Will document only for the Frankfurt release.
- 3) Documentation after implemented , or implemented but not in the prior release
- 34) Lower Priority
- 45) Experimental
The first category is that those requirement will be documented only in Dublin in Frankfurt release
the second category will document the current implementation in those projects.
...
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 |
|---|
N/A
related to DM SOL001 progress
impact R4 DM?
NSD - the ONAP internal data model should be able to reflect ETSI SOL001 NSD provided for onboarding
SDC, SO, VFC
...
| Use Case Owner | ||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Service DM | Enhanced Nested and Shared Service Information Model
| SDC,SO, OOF,AAI | Network Slicing | guochuyi | guochuyi | |||||||||||||||||||||||||
| 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) | |||||||||||||||||||||||||||
Resource IM/DM | Software Versions support for PNF S/W Upgrade
| SDC | PNF S/W Upgrade (PNF Support Use Case) | |||||||||||||||||||||||||||
| Service IM, Resource DM | End to End Layer 1 Service Management. Modeling the Optical Service. | AAI
| Multi-domain Optical Service L0/L1 Orchestration | |||||||||||||||||||||||||||
| Resource IM/DM | Data type & Node type for 5G NRM. | SDC, SO, CDS
| 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 |
|---|
Service
Kevin ScaggsN/AHighguochuyi
To document the onboarding NS IM as supported by the usecase
Former user (Deleted)N/AHighHigh
| Owner | Use Case Contact | |||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Service IM | Enhanced Nested and Shared Service Information Model
| SDC,SO, OOF,AAI | Network Slicing | guochuyi | documentation only | guochuyi | ||||||||||||
| Service IM | End-to-end Network Slicing Information Model
| SDC,SO, SDN-C, OOF,DCAE, External API, | Network Slicing | guochuyi | documentation only | guochuyi | ||||||||||||
| Resource IM/DM | GeoLocation Model (and standards harmonization) | Modeling | PNF Plug and Play (PNF Support Use Case) | documentation only | ||||||||||||||
| Common | Licensing Model Refinement | SDC | Licensing Management | documentation only | ||||||||||||||
| Service IM | slice service monitoring KPI
| SDC, DCAE | Vertical Industry Oriented on-demand 5G Slice Service | guochuyi | documentation only | |||||||||||||
| Service IM | SON 'service' | SDC,DCAE,SO | 5G OOF SON use case |
To document the allotted resource IM as implemented by SDC
N/A
Below tables are not downgrade, but casablanca won't make it
| documentation only | ||||||||||
| Service IM | ORAN & 3GPP Standards Harmonization | SDC, Controller, DCAE, CDS | ORAN & 3GPP Standards Harmonization (5G Use Case) | documentation only |
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 |
|---|
Service
Common
Policy
create policy IM, reflect current policy project implementation
Policy
N/A
N/A
Infrastructure
...
| Common | VES | Add network element status report to assist run time service instance selection. | Related to: DCAE, AAI | Network Slicing | documentation only | ||||||||||||||
| Resource | A&AI reverse engineering
| create runtime information model based on current A&AI schema | Related to: A&AI | PNF Plug&Play | documentation only | ||||||||||||||
Common | policy model | create policy information model based on implementation of policy project | Related to: Policy, SDC | documentation only | |||||||||||||||
| Common | license model | create license information model based on SDC implementation | Related to: SDC | documentation only | |||||||||||||||
| Resource | allotted resource | create allotted resource information model based on SDC implementation | Related to: SDC | 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 |
|---|
Common
License
create super classes for current models
| Service IM | Service Model | Modeling (exploratory) work for creating a 5G Service | Modeling | 5G Service Model Use Case (5G) | documentation only | |||
| Service IM | To keep current composite service model align with SDC model, need a comparision and supplement. | SDC | ||||||
| Service IM, Resource IM | Network Topology Modeling. Network configuration tree structures. | SO, SDC, AAI, Controllers, ConfigDB | Network Topology Management | |||||
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:
...