Open APIs

Hi,

As part of Rel 18.5, there is an introduction of "serviceLevelSpecification" in TMF633.

We are trying to understand how to pass this information in TMF640 so that the instance data can be associated with serviceLevelSpecification.

Any inputs around this will be appreciated.

------------------------------
Abdul Majid Hussain
Telstra Corporation
------------------------------

Hi Abdul

You will note that the reference is to a ServiceLevelSpecification, but there is no such entity (yet) in the Open API - you can take a look at Service Level Spec ABE in the SID to get an idea of how it might look. Clearly there is scope here for a domain expert to contribute a Service Level Specification Management API.

Regarding TMF640 (service activation), I understand from your question that the implementation of this API (in terms of POST) should not depend on any external references, i.e. all the relevant information needed for activation is part of the POST payload. If this correct, perhaps the mode of operation of this API needs to be reconsidered - and refactored as a TASK API where the TASK resource would include the Service instance but also other required information that is not directly in the Service model but indirectly referenced, such as Service Level Specification. An alternative would be to expand the Service model to explicitly include this information, but I am not so keen on that..

Worth discussion with @Pierre Gauthier, I think, and also with @Ludovic Robert .

Hope it helps.
​

------------------------------
Jonathan Goldberg
Amdocs Management Limited
------------------------------

Hi @Pierre Gauthier, @Ludovic Robert,

Can you please provide some input here?​

​

------------------------------
Abdul Majid Hussain
Telstra Corporation
------------------------------

Original Message:
Sent: Jul 17, 2019 02:06
From: Jonathan Goldberg
Subject: TMF633 - Rel 18.5 - Introduction of serviceLevelSpecification

Hi Abdul

You will note that the reference is to a ServiceLevelSpecification, but there is no such entity (yet) in the Open API - you can take a look at Service Level Spec ABE in the SID to get an idea of how it might look. Clearly there is scope here for a domain expert to contribute a Service Level Specification Management API.

Regarding TMF640 (service activation), I understand from your question that the implementation of this API (in terms of POST) should not depend on any external references, i.e. all the relevant information needed for activation is part of the POST payload. If this correct, perhaps the mode of operation of this API needs to be reconsidered - and refactored as a TASK API where the TASK resource would include the Service instance but also other required information that is not directly in the Service model but indirectly referenced, such as Service Level Specification. An alternative would be to expand the Service model to explicitly include this information, but I am not so keen on that..

Worth discussion with @Pierre Gauthier, I think, and also with @Ludovic Robert .

Hope it helps.
​

------------------------------
Jonathan Goldberg
Amdocs Management Limited
------------------------------