Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: update table format

...

Will be implemented and included in the release 3


Modeling Domain

Modeling Requirement

Modeling Requirement Description

Impacted

Projects

Use Case

Relevance

Modeling Spec

Commitment

Code

Commitment

Provider

Priority

Mapping to M1
requirement 
requirement
 Owner
Owner

Resource

ResourceComposite

?SDC need further detail solution

The ResourceComposite includes several sub-requirements:

  • support composite relationship between different resource objects, e.g., a NS can be composed of VNF, VL, etc. (need to support TOSCA substitution mapping)
  • support nested resource concept, e.g., a NS can be composed of several NSs (called nested NS in ETSI spec)
  • support semantics validation during onboarding and design time. For example, during design time, checking a NS can be composed of VNF, VL, nested NS, etc., but no irrelevant resources; during onboarding time, checking a VNFD doesn't contain more than one VNF node

SDC(->)

VNFSDK(y)

VoLTE

CCVPN

CMCC

Huawei

ZTE

Vodafone

AT&T

Verizon

Intel

CMCC

Huawei

ZTE
Intel

CMCC: High

Vodafone: High

AT&T:  High

Verizon-High


VNFD & Alloted resource

(Andy needed)

ONAP Resource Data Model for Design and Runtime

SDC

A&AI

OOF

SO

MultiVIM

 All

AT&T

Intel

AT&T

Intel

 AT&T: High
 PNF for 5G

 software version


SDC

SO

 5G
 Nokia

Network Service

Network service is already modeled in R2 but is now moved as a Resource Composite.

  1. In R3, NSD can be composed of VNFD, VLD in design time at least to support VOLTE usecase.
  2. In R3, NSD can be composed of nested NSD, and other resources(VNFD, PNFD,VLD, etc) in design time if possible

Networkservice IM

Networkservice DM

SDC(->)

VoLTE

CCVPN

5G

CMCC

Huawei

ZTE

AT&T

CMCC

Huawei

ZTE

CMCC: High

Vodafone: High

AT&T:  Medium



Documentation after implemented, or implemented but not in the release

...