Hi,
in addition to the use of Service Qualification API
(TMF 645), that for sure can be used to determine the general feasibility of the service delivery at a specified location, when it comes to the service design and resource reservation, I would propose to use also the Resource Inventory Management API (TMF639) and in particular the resource
state "Planning" and its sub-state "Designed".
Indeed, the Service Order Management system, handling an order received from the Service Order API (TMF641), could post a TMF639 CREATE RESOURCE request with lifecycleSate = Proposed (or Feasibility Checked) to the Resource Inventory system that in turn could automatically proceed with the resources allocation transiting finally the status to "Designed". The transition is notified back to the the Order Manager which can fetch the details of the allocated resources still through the TMF639 and subsequently request other transitions of the status to Ordered, etc..
Does it make sense? Comments welcome.
Best regards,
Dino
------------------------------
Dino Pellegrini
Solution Architect OSS Orchestration
Ericsson Inc.
------------------------------
Original Message:
Sent: Jun 20, 2019 13:24
From: Pasquale Rechichi
Subject: TMF OpenAPI for network service design and assign
Hello,
I'm trying to indentify the right TMF OpenAPI to be exposed by network inventory system to request the design of some network service (e.g. an FTTH service for a residential customer). The design would also imply the reservation of any resources needed to fulfill the requested service.
Such interface should be consumed by an order management system aiming to receive the list of resources (e.g. ONT, OLT, etc.) to be activated and configured on the network.
Thanks in advance for your support.
Regards,
Pasquale Rechichi
------------------------------
Pasquale Rechichi
Ericsson Inc.
------------------------------