Hi all
I've been looking at this, and it is really not that simple.
As Kannan writes, a new (provide) Service will likely be passed
by value in the Service Order sent by BSS (ODA core commerce) to OSS (ODA production).
The BSS layer needs to listen to events from OSS layer that will contain the ID of the Service when created in the inventory. But that's not enough, since the BSS layer needs additional information in the event that will allow correlation to the Product and Product Order. It probably needs to be as follows:
- BSS calls POST Service Order - the return from POST includes the ID of Service Order. BSS stores this ID on the Product Order (where else?)
- Eventually (if all goes well) the Service is created in the inventory by OSS
- BSS listens to ServiceCreate event, when event occurs BSS extracts the Service Order ID from the Service model and uses it to correlate to the originating Product Order
The above assumes that the Open API models support these correlations, I'm not convinced that we are there yet.
@Kamal Maghsoudlou and
@Ludovic Robert and
@Johanne Mayer your thoughts on this please?
------------------------------
Jonathan Goldberg
Amdocs Management Limited
Any opinions and statements made by me on this forum are purely personal, and do not necessarily reflect the position of the TM Forum or my employer.
------------------------------
Original Message:
Sent: Aug 12, 2021 07:19
From: Koen Peeters
Subject: TMF 641 Service Order management - How is the service id obtained?
Hi,
It must be clear that TM-Forum describes the API but not necessarily the implementation.
One implementation approach could be as follows:
- POST Service Order
- syntax validation
- generate id, name, href for order
- generate creationDate
- emit ServiceOrderCreateNotification
- return service order with generated fields added
- ServiceOrderCreateNotification received
- for each orderItem
- semantic validation of services using catalogue & inventory
- rules differ depending on action
- if validation fails set status of orderItem to Acknowledged or Rejected
- If any of the orderItems is Rejected
- set order status to Rejected
- else
- for each orderitem
- create/update/delete service using TMF638
- TMF638 return id, name, href, creationDate
- update reference to Inventory in orderItem
- set order status to Acknowledged
- emit ServiceOrderStateChangeNotification
As you can see the serviceOrder contained within the notifications is not a simple copy of the input but has addtional information such as service id.
Regards
------------------------------
Koen Peeters
Ciminko Luxembourg
Original Message:
Sent: Aug 11, 2021 09:23
From: Kinshuk Kulshreshtha
Subject: TMF 641 Service Order management - How is the service id obtained?
Please see my response on this thread that explains how Service Order creates the Service Inventory using TMF638 API. When the Service gets creates, the Service Order will get the Service ID and href as part of TMF638 payloads and gets updated to the fields I mentioned above to be passed back to the consumer.
------------------------------
Kinshuk Kulshreshtha
Oracle Corporation
My views posted on this forum are personal, and do not reflect the position of my employer or TM Forum.
Original Message:
Sent: Aug 11, 2021 08:59
From: Kannan Jayaprakasam
Subject: TMF 641 Service Order management - How is the service id obtained?
I get how it works if the service is referenced by id and href. What happens when the CreateServiceOrder provides a service by value like in the example in page 49 in the doc by providing the service characteristics but not the service id. In this case it looks like the api implementation should create a service and then fulfill the order. How is the service id in this case made known to the caller?
Original Message:
Sent: 8/11/2021 8:10:00 AM
From: Kinshuk Kulshreshtha
Subject: RE: TMF 641 Service Order management - How is the service id obtained?
Hi Kannan,
Service Order entity has a ServiceRefOrValue sub-resource that contains the following parameters that can be used to send the Service details back to the Consumer of TMF641.
href | A string. Reference of the service. |
id | A string. Unique identifier of the service. |
------------------------------
Kinshuk Kulshreshtha
Oracle Corporation
My views posted on this forum are personal, and do not reflect the position of my employer or TM Forum.
Original Message:
Sent: Aug 11, 2021 05:23
From: Kannan Jayaprakasam
Subject: TMF 641 Service Order management - How is the service id obtained?
When a Service is created by a ServiceOrder ServiceOrderItem with type "add", how is the service id and href communicated to the Service consumer? The Notification events all only reference the Service Order. For instance there is no Notification event that references a Service Order and also provides the Service id that got created, atleast not an explicit event for Service creation completion that would provide the service id.
------------------------------
Kannan Jayaprakasam
TO BE VERIFIED
------------------------------