Hi,
indeed a possible modelling option is usign the "serviceSpecCharRelationship" i.e. starting from the "serviceSpecification", add one or more "serviceSpecCharRelationship" referencing the "serviceSpecification" the ordered service depends on.
The referenced service specification can include 0 or more "serviceSpecCharacteristic" in turn including 0 or more "serviceSpecCharacteristicValue" at the detail needed.
Just I want to add that the dependencies model between services is normally maintained in the service catalog and is supported by the Catalog Management API (TMF 633).
Example in JSON:
{
"id": "7655",
"href": "https://host:port/catalogManagement/serviceSpecification/7655",
"name": "Firewall Service",
"description": "This service specification ...",
"@type": "ResourceFacingServiceSpec",
....
"serviceSpecCharacteristic": [
{
"name": "Supported throughput",
.....
"serviceSpecCharRelationship": [
{
"type": "dependency",
"name": "connectivity",
"id": "4690",
"href": "https://host:port/catalogManagement/serviceSpecification/4690",
}
}
],
....
}
{
"id": "4690",
"href": "https://host:port/catalogManagement/serviceSpecification/4690",
"name": "P2P EVC",
"description": "Connectivity service",
"@type": "ResourceFacingServiceSpec",
....
"serviceSpecCharacteristic": [
{
"name": "Bandwidth profile",
"description": "This service bandwidth",
"valueType": "Committed Information Rate",
.....
"serviceSpecCharacteristicValue": [
{
"isDefault": true,
"value": "10Mbps",
.....
}
}
]
]
}
Hope it helps.
Best regards,
------------------------------
Dino Pellegrini
Ericsson Inc.
------------------------------
Original Message:
Sent: Jun 29, 2018 10:15
From: Jeroen Van der Laan
Subject: Service ordering API - Define attributes/characteristics of ServiceRelationships
Hi Michel,
Thanks for this helpful information. I wasn't aware of this modelling on the most low level (RootEntity). Will definitely have a look at this approach. I now modelled it in this API via a way that might just match this part of SID, and otherwise I might have to move it to an actual instance of RootEntity.
Regards,
------------------------------
Jeroen Van der Laan
Eurofiber Group
Original Message:
Sent: Jun 27, 2018 03:31
From: Michel Besson
Subject: Service ordering API - Define attributes/characteristics of ServiceRelationships
Hi Jeroen,
From a pure SID perspective, RootEntityRelationship may help you:
"A RootEntitiyRelationship describes a relationship between two instances of RootEntities. The type of relationship might be very different such as requires, incompatibility, equivalent"
Have a look at the SID GB922_Root section 1.2.2. There are several examples illustrating this concept.
However, at the API level this kind of relationship is not expressed.
Michel
------------------------------
Michel Besson , PhD
Lead Architect
TM Forum
Original Message:
Sent: Jun 20, 2018 04:16
From: Jeroen Van der Laan
Subject: Service ordering API - Define attributes/characteristics of ServiceRelationships
Hi Jonathan,
Indeed the ServiceSpecCharRelationship would work when I want to model dependencies between characteristics of one service specification (e.g. one service). This will not solve our situation which is more as you described the bandwidth/technology relationship). As I would probably model it is the fact that a service (within a service order) can have a serviceRelationship (relies_on) to another service which can hold something like a list of serviceRelationshipCharacteristics (that are valid serviceSpecCharacteristics of the service I depend on). In fact in my opinion the serviceRelationship entity needs a little more depth to define the specifics of the related service that are impacted by this service relationship.
Regards,
------------------------------
Jeroen Van der Laan
Eurofiber Group
Original Message:
Sent: Jun 19, 2018 04:36
From: Jonathan Goldberg
Subject: Service ordering API - Define attributes/characteristics of ServiceRelationships
The SID includes a relationship between ServiceSpecCharacteristics, which could be what you are looking for. See for example figure SO.22 in the Service Overview guidebook from the SID.
But as pointed out by previous posters, this appears to be missing from the Open API, you could submit an improvement request on the Open API JIRA https://projects.tmforum.org/jira/projects/AP/i.
But even this might not be sufficient, you may need to have a relationship at the level of characteristic value (e.g. a specific bandwidth value in one service could be dependent on a technology attribute in another service). We discovered a similar lack in the area of product-to-service decomposition, here also the relationship appears to be missing.
------------------------------
Jonathan Goldberg
Amdocs Management Limited
Original Message:
Sent: Jun 19, 2018 02:46
From: Jeroen Van der Laan
Subject: Service ordering API - Define attributes/characteristics of ServiceRelationships
Hi Stephen,
Thank you for this update.
This would work when I would have multiple OrderItems in one batch (both the depending and the dependent service). This would not work in my opinion when I would order a service (via an OrderItem) that relies on something on an already existing service. So either I would have to make this existing service be in the service order as an order item (which I think isn't the right approach) or try the ServiceRelationship approach instead. But then it becomes hard to model the attributes/characteristics of the existing service.
Regards,
Jeroen
------------------------------
Jeroen Van der Laan
Eurofiber Group
Original Message:
Sent: Jun 18, 2018 17:54
From: Stephen Fratini
Subject: Service ordering API - Define attributes/characteristics of ServiceRelationships
Hi Jeroen
A similar question arose in a discussion today.
It turns out that you can state dependencies among order items. See the following text from the service order API (TMF641):
OrderItemRelationship
Linked order item to the one containing this attribute.
Field
|
Description
|
type
|
A string. The type of relation to another order item, as example it can be:
o "dependency" if the order item needs to be "not started" until another order item is complete
o "reliesOn" if the service needs another service to rely on
o ...
|
id
|
A service order item id - It could be any order item from this order.
|
Steve
------------------------------
Stephen Fratini
TM Forum
Original Message:
Sent: Jun 08, 2018 16:28
From: Jeroen Van der Laan
Subject: Service ordering API - Define attributes/characteristics of ServiceRelationships
Hi,
While evaluating the Open API for service ordering for a project I am working on I found the principle of modelling a service relationship for one of the services I am instantiating in a Service Order. In this relationship (as I see it) I can define a dependency of the service I am creating. For instance, for service A I need an instance of service B.
Now I actually want to link a specific characteristic of Service B to Service A. Example would be a allocation of some kind of resource on a service (vlan). There is, in my opinion, no way of modelling this properly. But I wanted to check if I miss something here.
Thanks in advance!
Regards,
------------------------------
Jeroen Van der Laan
Eurofiber Group
------------------------------