Open APIs

 View Only
  • 1.  TMF 645 - Service Candidate usage

    TM Forum Member
    Posted Apr 14, 2020 08:23
    Could you please help. I have 3 questions regarding TMF 645

    1) In TMF 633, there is a concept of Service Candidate to be added under Service Category. However, in TMF 645 there is no Service Candidate. Is ServiceRestriction represent the Service Candidate? 

    2) What is the benefit of having Service Candidate under Service Catalog if at the end the Service Specification under the Service Candidate will be used in the Service Order( Service Specefication will be added to the order and provisioned)? Why not having Service Specification attached to Service Catalog directly? 
    In another way of asking the question is: Why in Service Qualification (In case ServiceRestriction represent the Service Candidate) we need to have  ServiceRestriction while we need the Service Speciation to be added to the order and not the ServiceRestriction itself?

    3) Why there is no flag for instantSyncQualification the same way as in Product Offer Qualification? Why Service Qualification is only support Async by default? Will it be in the coming release? If coming in the next release will the GET operation be optional the same way for Product Offerring Qualification? 



    ------------------------------
    Ihab Serhed
    Ericsson Inc.
    ------------------------------


  • 2.  RE: TMF 645 - Service Candidate usage

    TM Forum Member
    Posted Apr 20, 2020 09:41
    Hi Ihab

    I have suggested that Service Candidate (and Resource Candidate) be removed from the SID and the Open API model - in my opinion they give no additional semantic value.
    Unfortunately no progress has been made in this area, so we still have these entities.

    ServiceRestriction has nothing to do with candidate - ServiceRestriction is a strict subset of Service, with removal of attributes and relationships that are not relevant to a service at the time qualification is being evaluate.

    @Ludovic Robert may be able to assist with additional queries about service qualification.

    Hope it helps

    ​​

    ------------------------------
    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.
    ------------------------------



  • 3.  RE: TMF 645 - Service Candidate usage

    TM Forum Member
    Posted May 12, 2020 03:13
    Hello Ihab,

    To complete Jonathan answer
    For point 3) the instantSyncQualification will be part of this release. So yes it will support Async. Note that we also split in 2 resources the Service Qualification:
    CheckServiceQualification to perform a qualification on a service configuration (or an array) and get an eligibility result + alternate service
    QueryServiceQualification that allow you to provide some criteria(s) as input and get a list of qualified service.

    Please note also that ServiceRestriction should not be used in new release and we aligned the use of Service for all Service APIs.

    Hope it helps.

    Ludovic



    ------------------------------
    Ludovic Robert
    Orange
    My answer are my own & don't represent necessarily my company or the TMF
    ------------------------------