Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 12 Next »

This page is used for the deposition of clean version ONAP R2+ Servcie IM.

Class Diagram

Based on the input from ECOMP Service IM input, ONAP R2+ Service IM is designed as below class diagram:


  • In this diagram, both design time and run time service related objects are depicted.

  • For the design time section on the left side,

    • ServiceCatalogItem is used to model the design time representation of a service. 

      • Nested Service Design is supported by the association "ServiceComprisedOf", as a ServiceCatalogItem can be composed of other ServiceCatalogItem(s).

      • Complicated Service Design is supported by the association "ServiceComposedOf", as a ServiceCatalogItem can be composed of  at least 1 or more ServiceComponentCatalogItem(s).

      • Hybrid Service Design is also supported, as a part of a ServiceCatalogItem can be composed of ServiceComponentCatalogItem(s) and part of it can be composed of other ServiceCatalogItem(s).
    • ServcieComponentItem is used to model the design time represenation of a service component or network service.
      • Nested Service Component Design is supported by the association "ServiceComponentComprisedOf", as a ServiceComponentCatalogItem can be composed of other ServiceComponentCatalogItem(s).

      • Complicated Service Component Design is supported by the association "ServiceComponentComposedOf", as a ServiceComponentCatalogItem can be composed of  at least 1 or more ResourceCatalogItem(s).

      • Hybrid Service Component Design is also supported, as a part of a ServiceComponenetCatalogItem can be composed of ServiceComponentCatalogItem(s) and part of it can be composed of other ResourceCatalogItem(s).

    • ResourceCatalogItem is used to model the design time representation of a resource.

      • Cross reference in resource design is supported via the association "ResourceCatalogReferences".

  • For the run time section on the right side, similiar layering from top to bottom of instance items and relationship between is modeled, as the result of the model-driven instantiation process from a given ServiceCatalogItem. In particular,

    • Based on 1 ServiceCatalogItem, 0 or more ServiceInstance(s) can be instantiated, which also instantiate the association "ServiceCatalogItemMadeAvailableAs". A ServiceInstance can comprise other ServiceInstance(s) or ServiceComponentInstance(s), as modeled by the associations "ServiceComprisedOf" and "ServiceComposedOf".
    • Based on 1 ServiceComponentCatalogItem, 0 or more ServiceComponentInstance(s) can be instantiated, which also instantiate the association "ServiceComponentCatalogItemMadeAvailableAs". A ServiceComponentInstance can comprise other ServiceComponentInstance(s) or ResourceInstance(s), as modeled by the associations "ServiceComponentComprisedOf" and "ServiceComponentComposedOf".
    • Based on 1 ResourceCatalogItem, 0 or more ResourceInstance(s) can be instantiated, which also instantiates the association "ResourceCatalogItemMadeAvailableAs". A ResourceInstance can reference other ResourceInstance(s).

Use Case Example

From the very high level, in summary,

  • Products are made up of services (ServiceCatalogItems on the design side, ServiceInstances on the runtime side).
  • Services are made up of service components. A service component is not seen or known to products like SID ResourceFacingServices are not seen by products. Services can be composed of other Services and may be referred to as complex services. Network Service, or WAN service are as the service components in the service.
  • ServiceComponents are made up of ServiceComponents or resources.  The resources include VNF, PNF, VL, etc.

VoLTE

Take the ONAP R1 VoLTE use case as an example.  The E2E VoLTE service can be designed as the service; The IMS, EPC, and WAN can be designed as the service components.  The HSS, CSCF, TAS, SBC, MME, and SPGW etc, and the link between them can be design as the resources.




Attributes

  • ServiceCatalogItem (Note from Chesla:   A&AI has a model/model-ver concept which captures the descriptor from ASDC.
    The model vertex type contains the model-invariant-id and the model-type (e.g., service or resource).  The model-ver vertex type contains the model-version-id, the model-version, the model-name, and a model-description.

  • In short, A&AI split the invariant part of the model away from the version-dependent pieces.  In this manner, you can relate ALL versions of a model to something  by using the model-invariant-id (e.g., get me all the resources for this model) or you can relate a specific version of a model (e.g., get me all resources for this version of the model) by using the model-version-id in combination with the model-invariant-id.  Recall that A&AI stores the model/model-ver elements as "JOIN" keys to the SDC descriptor world.  A&AI does not try to capture all the details of the models.

  • It's not clear whether you can equate model-name to service-name or model-description to service-description.  The model-name really names the MODEL, not necessarily the service.  The same applies to the service-description.)

R2+ AttributesDescriptionProducerConsumer

SDC(Service)

AAI(service)ECOMP IM(ServiceCatalogItem)
serviceInvariantUUIDConstant identifier of the service modelSDCSDC/SO/UUI/VIDinvariantUUID

serviceUUID

Versioned identifier of the service model (this uuid is changed for every major version of the service)

SDCSDC/SO/UUI/VIDUUIDservice-idServiceUUID 
serviceName 

The name of the service designed

SDCSDC/SO/UUI/VIDname
ServiceDisplayName 
serviceDescription

The description of the service designed

SDCSDC/SO/UUI/VIDdescriptionservice-descriptionServiceDescription 
category

A predefined list which identifies the construct's category. There is a predefined list of service categories

SDCSDC/SO/UUI/VIDCategory
Category  
serviceVersionThe service versionSDCSDC/SO/UUI/VID
service-versionVersion 
icon

The icon path of the service

SDCSDC/SO/UUI/VID

Icon 
serviceComponentUUIDThe service component UUIDs that the service includesSDCSDC/SO/UUI/VID



  • ServiceInstance

R2+ Attributes
DescriptionProducerConsumerAAI(ServiceInstance)
serviceInstanceIdUniquely identifies this instance of a serviceSOAAI/UUI/VID/SO/Policy/Holmesservice-Instance-Id
serviceInstanceNameThe name assigned to the service-instanceUUI/VID/SOAAI/UUI/VID/SOservice-instance-name
serviceInvariantUUIDConstant identifier of the service modelSDC/SOAAI/UUI/VID/SOmodel-invariant-id
ServiceUUIDVersioned identifier of the service modelSDC/SOAAI/UUI/VID/SOmodel-version-id
ServiceVersionThe service version in SDC catalogSDC/SOAAI/UUI/VID/SOpersona-Model-Version
selfLinkURL to endpoint where more details can be gottenSOAAI/UUI/VID/SOselflink
statusOrchestration status of the service instanceSOAAI/UUI/VID/SO/Policy/Holmesorchestration-status
serviceComponentInstanceIdThe service component instance ID that the service instance includesVFC/...AAI/UUI/VID/SO/Policy/Holmes


  • ServiceComponentCatalogItem

R2+ AttributesDescriptionProducerConsumerSDC(Service)

ECOMP

(ServiceComponent)

ETSIIFA014

(NetworkService)

invariantUUIDConstant identifier of the Service Component modelSDCSDC/UUI/VFCinvariantUUID
nsdInvariantId
UUIDVersioned identifier of the Service Component model (this uuid is changed for every major version of the service component)SDCSDC/UUI/VFCUUID

ServiceComponent

CatalogItem

nsdIdentifier
nameThe name of the service componentSDCSDC/UUI/VFCname
nsdName
descriptionThe description of service componentSDCSDC/UUI/VFCdescription

versionThe version of service componentSDCSDC/UUI/VFC

version
designerThe designer of service componentSDCSDC/UUI/VFC

designer


  • Network Service Descriptor

    Inherit from ServiceComponentCatalogItem

R2+ AttributesDescriptionProducerConsumerETSI IFA014(NetworkService)
vnfdid

References the VNFD of a constituent VNF.

SDCSDC/UUI/VFCvnfdid
pnfdId

References the PNFD of a constituent PNF.

SDCSDC/UUI/VFCpnfdId
virtualLinkDescProvides the constituent VLDs.SDCSDC/UUI/VFCvirtualLinkDesc



  • ServiceComponentInstance


R2+ AttributesDescripionProducerConsumerAAI(ServiceInstance)

ETSI IFA013(NS)

instanceIdUniquely identifies this instance of a service componentVFCAAI/UUI/VFC/Policy/Holmesservice-Instance-IdnsInstanceId
instanceNameThe name assigned to the service component instanceUUI/VFCAAI/UUI/VFC/Policy/Holmesservice-instance-namensName
invariantUUIDConstant identifier of the service component modelSDC/VFCAAI/UUI/VFCmodel-invariant-idnsdId
UUIDVersioned identifier of the service component model (this uuid is changed for every major version of the service component)SDC/VFCAAI/UUI/VFCmodel-version-id
versionThe service version in SDC catalogVFCAAI/UUI/VFCpersona-Model-Version
selfLinkURL to endpoint where more details can be gottenVFCAAI/UUI/VFCselflink
statusOrchestration status of the service component instanceVFCAAI/UUI/VFC/Policy/Holmesorchestration-statusnsState
descriptionThe description of service component instanceVFCAAI/UUI/VFC
description


    • Network Service Instance

Inherit from ServiceComponentInstance


R2+ AttributesDescriptionProducerConsumer

ETSI IFA013(NS)

vnfInfoIdReference to information on constituent VNFs of this NS.VFCAAI/UUI/VFCvnfInfoId
pnfInfo

Information on the PNF(s) that are part of this NS.

VFCAAI/UUI/VFCpnfInfo
virtualLinkInfo

Information on the VLs of thisNS.

VFCAAI/UUI/VFCvirtualLinkInfo




  • No labels