Page Comparison

...

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

Image RemovedImage Added

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

• For the design time section on the left side,

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

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

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

    • Hybrid Service Design is also supported, as a part of a ServiceCatalogItem ServiceDescriptor can be composed of ServiceComponentCatalogItemServiceComponenDescriptor(s) and part of it can be composed of other ServiceCatalogItemServiceDescriptor(s).
  • ServcieComponentItem ServcieComponentDescriptor is used to model the design time represenation representation of a service component or network service.

    • Nested Service Component Design is supported by the association "ServiceComponentComprisedOf", as a ServiceComponentCatalogItem can as a ServiceComponentDescriptor can be composed of other ServiceComponentCatalogItemServiceComponentDescriptor(s).

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

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

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

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

• 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 ServiceCatalogItemServiceDescriptor. In particular,

• Based on 1 ServiceCatalogItemServiceDescriptor, 0 or more ServiceInstance(s) can be instantiated, which also instantiate the association "ServiceCatalogItemMadeAvailableAsServiceDescriptorMadeAvailableAs". A ServiceInstance can comprise other ServiceInstance(s) or ServiceComponentInstance(s), as modeled by the associations "ServiceComprisedOf" and "ServiceComposedOf".
• Based on 1 ServiceComponentCatalogItemServiceComponentDescriptor, 0 or more ServiceComponentInstance(s) can be instantiated, which also instantiate the association "ServiceComponentCatalogItemMadeAvailableAsServiceComponentDescriptorMadeAvailableAs". A ServiceComponentInstance can comprise other ServiceComponentInstance(s) or ResourceInstance(s), as modeled by the associations "ServiceComponentComprisedOf" and "ServiceComponentComposedOf".
• Based on 1 ResourceCatalogItemResourceDescriptor, 0 or more ResourceInstance(s) can be instantiated, which also instantiates the association "ResourceCatalogItemMadeAvailableAsResourceDescriptorMadeAvailableAs". A ResourceInstance can reference other ResourceInstance(s).

...

• Products are made up of services (ServiceCatalogItems on ServiceDescriptor 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.

...

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.

Image Removed

...

• 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.

Image Added

Attributes

• ServiceDescriptor

• ServiceInstance

...

• ServiceComponentDescriptor

...

• ServiceComponentInstance

• • Network Service Instance

Inherit from ServiceComponentInstance

...