...
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
- ServiceDesc
ServiceDescriptor
| R2+ Attributes | Description | Producer | Consumer | SDC(Service) | AAI(model+model-ver) | ECOMP IM(ServiceCatalogItem) |
| serviceInvariantUUID | Constant identifier of the service model | SDC | SDC/SO/UUI/VID | invariantUUID | model.model-invariant-id for that service model | |
| serviceUUID | Versioned identifier of the service model (this uuid is changed for every major version of the service) | SDC | SDC/SO/UUI/VID | UUID | model-ver.model-version-id for that service model | ServiceUUID |
| serviceName | The name of the service model designed | SDC | SDC/SO/UUI/VID | name | model-ver.model-name for that service model | ServiceDisplayName |
| serviceDescription | The description of the service model designed | SDC | SDC/SO/UUI/VID | description | model-ver.model-description for that service model | ServiceDescription |
| category | A predefined list which identifies the construct's category. There is a predefined list of service categories | SDC | SDC/SO/UUI/VID | Category | n/a | Category |
| serviceVersion | The service model version | SDC | SDC/SO/UUI/VID | model-ver.model-version for that service model | Version | |
| icon | The icon path of the service | SDC | SDC/SO/UUI/VID | n/a | Icon | |
| serviceComponentUUID | The service component descriptor UUIDs that the service includes (relationhip to Service Component) | SDC | SDC/SO/UUI/VID |
...