Versions Compared

Old Version 94

changes.mady.by.user Chesla Wechsler

Saved on

compared with

New Version 95

changes.mady.by.user maopeng zhang

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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

 

Service Order

It includes the definition of the managed objects that allows a BSS system to create/delete/update/get an order of a service to a ONAP instance. The Service Order Modeling provided by Ext API R2 team must be reviewed to become part of the ONAP common service IM

(Service Order - Information Model View)

Ext API(y)

VoLTE

CCVPN

Change Mgt


CMCC

Huawei

ZTE

Vodafone

AT&T

Verizon

Orange

CMCC

Huawei

ZTE

Vodafone

Orange

CMCC: High

Vodafone: High

AT&T:  High

Verizon-High

ExtAPI

(y)

Andy Mayer (AT&T)

 Service Catalog A Service Catalog is a group of ServiceDescriptors that an organization provides to the consumers via ONAP.

https://wiki.mef.net/display/CESG/Service+Catalog

Ext API VoLTE

CCVPN

CMCC

Huawei

ZTE

Vodafone

AT&T

Verizon

Orange

CMCC

Huawei

ZTE

Orange

CMCC: High

Vodafone: High

AT&T:  High

Verizon-High

ExtAPI

(y)

 Kevin Scaggs (AT&T)

 Service DescriptorDesign time model: service descriptor model

correlating with the service instance in run time

A&AI

Ext API (thumbs up)

SO(y)

SDC(->)

(All)

VoLTE

CCVPN

5G

vCPE

CMCC

Huawei

ZTE

Vodafone

AT&T

Verizon

Orange

CMCC

Huawei

ZTE

Orange

CMCC: High

Vodafone: High

AT&T: High

Verizon-High


LIN MENG

(CMCC)

Resource  License Presently modeled and used in SDC

(ONAP license model)

SDC
 AT&T

Verizon


 AT&T:  Medium

Verizon-Medium

SDC Kevin Scaggs(AT&T)
Alloted resource SDCs current implementation SDC AllAT&T

Intel

AT&T

Intel

AT&T: High SDC

Andy Mayer (AT&T)

Scaling (HEAT template) Scaling Use Case Extension .

Casablanca focus: Document the Policy Model that is being implemented by the ONAP Policy Framework.

SDC (no impact)

A&AI (no impact)

SO (no impact)

Policy

Clamp (no impact)

 vDNS (Scaling)CMCC

Huawei

ZTE

AT&T


CMCC: Medium

Vodafone: Medium

AT&T:  High

SDC (no impact)

A&AI (no impact)

SO (no impact)

Policy (Y)

Clamp (no impact)

 Andy Mayer (AT&T)

Gil Bullard ((AT&T)

ResourceCompositeThe 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 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

SDC ()

VNFSDK

(y)

Xu Yang

maopeng zhang

Network Service

(modeling subcommitee  DM approve firstly)

Context:

  1. In R2 VoLTE case, SDC support VoLTE service composed of IMS/EPC service as VNF. IMS/EPC Service can be composed of VNF, and VLD resources.

    In service layer, VOLTE service should focus on the IMS/EPC/... service composition, not coupled with the specific IMS resource composition. In the different scenes, IMS service can be implemented in different resources layer, for example, small capacity or large capacity, VNF in one DC or VNF on multiDC, even all PNFs or PNFs/VNFs, etc
    The multiple resource composition should not affected the service design. So network service is introduced, which is in charge of different IMS resource composition and let the service design not coupled with the resource composition design in detail.

  2. TMF support service and resource, and also in resource layer, there is resource composite. and Network service
is already modeled in R2 but is now moved as a Resource Composite.
  1. from ETSI can be mapping to the resource composite

  2. model subcommittee progress:

Network service is agreed in resource IM group. Networkservice IM
Network service Descriptor has been discussed in DM group. Networkservice DM


SDC requiremnets in R3:

  1. In service design, service descriptor can be composed of NS node and NS node can be associated to the NSD via tosca SubstitutionMapping.
  2. In resource design, NS descriptor
In R3, NSD
  1. can be composed of VNFD, and VLD
in design time
  1. at least to support
VOLTE usecase.In R3, NSD
  1. VoLTE
    If possible, NS descriptor can be composed of
nested NSDNetworkservice DM
  1. VNFD,
and other resources(VNFD, PNFD,VLD, etc) in design time if possible

Networkservice IM

  1. PND and VLD to support 5G
  2. SDC design UI, catalog(FE,BE,Database, API) should support NS and related NS package


 SDCVoLTE

CCVPN

5G

CMCC

Huawei

ZTE

AT&T

CMCC

Huawei

ZTE

CMCC: High

Vodafone: High

AT&T:  Medium

SDCChuyi Guo

maopeng zhang

Telemetry

Events & VES

VES Event Descriptor Model according to VES spec v6.0

DCAE

SDC


AT&T

Verizon


AT&T:  High

Verizon-High

DCAE(Y)

SDC

Kevin Scaggs(AT&T)

Jessie S Jewitt

(ARM)

Michela Bevilacqua


...