...
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,
ServiceDescriptor is used to model the design time representation of a service.
Nested Service Design is supported by the association "ServiceComprisedOf", as a ServiceDescriptor can be composed of other ServiceDescriptor(s).
Complicated Service Design is supported by the association "ServiceComposedOf", as a ServiceDescriptor can be composed of at least 1 or more ServiceComponentDescriptor(s).
- Hybrid Service Design is also supported, as a part of a ServiceDescriptor can be composed of ServiceComponenDescriptor(s) and part of it can be composed of other ServiceDescriptor(s).
- ServcieComponentDescriptor is used to model the design time representation of a service component or network service.
Nested Service Component Design is supported by the association "ServiceComponentComprisedOf", as a ServiceComponentDescriptor can be composed of other ServiceComponentDescriptor(s).
Complicated Service Component Design is supported by the association "ServiceComponentComposedOf", as a ServiceComponentDescriptor can be composed of at least 1 or more ResourceDescriptor(s).
Hybrid Service Component Design is also supported, as a part of a ServiceComponenetDescriptor can be composed of ServiceComponentDescriptor(s) and part of it can be composed of other ResourceDescriptor(s).
ResourceDescriptor is used to model the design time representation of a resource.
Cross reference in resource design is supported via the association "ResourceReferences".
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 ServiceDescriptor. In particular,
- Based on 1 ServiceDescriptor, 0 or more ServiceInstance(s) can be instantiated, which also instantiate the association "ServiceDescriptorMadeAvailableAs". A ServiceInstance can comprise other ServiceInstance(s) or ServiceComponentInstance(s), as modeled by the associations "ServiceComprisedOf" and "ServiceComposedOf".
- Based on 1 ServiceComponentDescriptor, 0 or more ServiceComponentInstance(s) can be instantiated, which also instantiate the association "ServiceComponentDescriptorMadeAvailableAs". A ServiceComponentInstance can comprise other ServiceComponentInstance(s) or ResourceInstance(s), as modeled by the associations "ServiceComponentComprisedOf" and "ServiceComponentComposedOf".
- Based on 1 ResourceDescriptor, 0 or more ResourceInstance(s) can be instantiated, which also instantiates the association "ResourceDescriptorMadeAvailableAs". A ResourceInstance can reference other ResourceInstance(s).
...