Open APIs

Expand all | Collapse all

TMF640 R18.5.0 Service Activation

  • 1.  TMF640 R18.5.0 Service Activation

    TM Forum Member
    Posted Jun 12, 2019 06:19
    Hi there,

    I have a couple of questions on the document:

    TMF640_Service_Activation_and_Configuration_API_REST_Specification_R18.5.0

    1. Under the Service_Create schema, Is there a need for inclusion of an attribute like  service " provisioning code" ? If it already present, please guide me.

    2. On HTTP return codes , Is there any specific reason why 3XX (301, 302) is missed? I believe that it is necessary for redirection in case of transition to update API without service disruption.

    Thank you.

    Regards,
    Nahfees



    ------------------------------
    Mohamed Nahfees Najumudeen
    SingTel Optus
    ------------------------------


  • 2.  RE: TMF640 R18.5.0 Service Activation

    TM Forum Member
    Posted Jun 19, 2019 12:14
    Regarding provisioning code:

    I am not sure that every service provisioning scenario for every service provider would need such a provisioning code, so it is understandable why it is not in the model. And you could argue that the code is implied by the identity of the service specification.

    But if it is needed, you could extend the model in your implementation of the API to add a provisioningCode attribute to ServiceSpecification. Or, you could make it part of catalog implementation, defining an invariant serviceSpecCharacteristic called provisioningCode and setting the serviceSpecCharacteristicValue to the code.

    Regarding 3xx HTTP response codes, I have raised the issue informally in the Open API team, I cannot make any promises regarding potential fixes or enhancements.

    Hope it helps

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